Looks like custom roms might finally be here for the xt860 (and possibly me863, read Update4 below for more info). Thanks to Hashcode for all the work he's done for all of us building safestrap, porting cm7 and everything, daywalker04 for uploading the Brazil Retail sbf, Endroid for being the first to try it with a normal bootstrap and now I'm confirming it working with Hashcodes newest safestrap(as well as his old ones, I originally tested w/v0.92 and worked my way up to current). I Just booted cm7 off /preinstall.
As usualy, please keep in mind that neither I or anyone else will take any responsibility for anything that happens to your phone through use of these files.
IF/When you enable and disable safestrap remember to format data/cache, causes bootlooping for me if I don't.
Warning, if you do this the way things are now you will not be able to get back to your bell software!! Only do this is you are absolutely sure you know what you're doing!!!!!!!!
You may have to be on the brazillian retail rom for this to work! You can find it in This Thread. You're looking for Fastboot package for UMTS XT860 Retail Brasil. At this point in time you can't get back to bell stock so again, it's at you're own risk!!
UPDATE: Thanks Rick2 for the recovery fix that allows us to swap between safestrap on the fly. Now when I need data I can get it anywhere. Works with Hashcodes newest safestrap (1.06). Go here to thank him and get the patch!
Update2: I've attached a CWM flashable zip that I've used to successfully get 3g working on Liberty and Mavs Rom, it does not work on cm7 but will hopefully work on other verizon based roms. It pushes the stock libmoto_ril.so(from the brazil retail), a new apns-xml.conf and a slightly edited build.prop(just made it en/US). I've had it cause the phone to fc loop if I installed it on an existing rom and didn't factory reset.
Update3: Watching this thread for info about me863 I think but according to that thread a user has flashed the brazil retail to his me863 and is trying to get data working
Update4: I've reworked the data patch to make it more universal. It should work on me863 providing safestrap runs on your phone. The patch will now copy files from /systemorig so you'll be using matching kernel/libs etc rather than using generic xt860 files. It also makes backups of the original files in the same location (just adds a .bak extension). This new patch IS SAFESTRAP ONLY. Huge huge thanks to Adamogle!!! If it weren't for him I'd still be banging my head up against the wall and no one would be using this patch. You may have to format data/cache, I left it out of the patch so everyone can test (if you phone goes into a force-crash loop then reboot and clear data/cache). Once I get confirmation of this working (or not) on the me863 I'll fix the thread again. I've left the old data patch(renamed as fit) as well in case anyone runs into troubles. Still not a cm7/9 patch, if one comes about it will get it's own thread but it works on all other custom roms based on motorola firmware.
if you see this and you're like "yes, finally some progress on the xt860!! Where do I donate???!?!!" You do that on Hashcodes website, it's ALL his hard work, I just basically wrote you a little story and pooled some files together. He really deserves it, he's working around the clock right now on cm9, seriously around the clock. Of course you can feel free to click the "Thank" button on this post if you like using my data patch
1./ Flash Brazil retail sbf from this thread
2./ root with Zerg from this thread. For some reason v3 kept tossing errors, v2 worked first try.
3./ install safestrap or whatever bootstrap (safestrap from Hashcodes site http://hash-of-codes.blogspot.com/
4./ profit (follow the directions to install a safestrap rom
boot recovery
Enable safestrap in options
Factory reset (formats data & cache)
Mounts > format system
Install your rom
Install my 3gfix
Reboot and profit
)
Again, my patch doesn't work on cm7 at the moment. Sorry Hashcode and everyone but I figured we'd be better off shooting for a known working rom. I'll update the post as I and other users test more roms. Thx thing on a spring for providing the patch "template", every time I threw one together and put it on my phone it turned out to be corrupt somehow so I just removed the files from your data fix and shoved in my own.
does it work with me863?
Thanks Willis I'll try that fix tonight. I'll try some of the other custom roms too see if any work. Probably give safestrap a whirl too
Beamed by invisible waves from my rooted xt860
I gotta say after months of watching customs roms and dev for the xt862 this is pretty exciting. Does wifi data work on cm7? I would assume if the issue is just with apn. I know its not the intended purpose but I may use safestrap as a dual boot, run custom roms at home in safe mode and switch back to Brazil retail when I need 3g
Beamed by invisible waves from my rooted xt860
This is awesome.
Great work guys. As soon as this gets a little more stable I'm going to flash it onto my gf's phone, work around these bugs that came in the stock FW.
Awesome. Been looking forward to this day. Not jumping on the train just yet, but I'm sure that once the 3G bug is ironed out, I'll be flashing.
emprize said:
does it work with me863?
Click to expand...
Click to collapse
Try it out, you can always sbf back to stock if it doesn't work.
Endoroid said:
I gotta say after months of watching customs roms and dev for the xt862 this is pretty exciting. Does wifi data work on cm7? I would assume if the issue is just with apn. I know its not the intended purpose but I may use safestrap as a dual boot, run custom roms at home in safe mode and switch back to Brazil retail when I need 3g
Beamed by invisible waves from my rooted xt860
Click to expand...
Click to collapse
Wifi works, I'm pretty sure it is an apn issue. Think I need to find my old framework-res.
From the bell rom? I have that at home if you need
Beamed by invisible waves from my rooted xt860
Did you try this http://forum.xda-developers.com/showthread.php?p=19981520
Beamed by invisible waves from my rooted xt860
Endoroid said:
Did you try this http://forum.xda-developers.com/showthread.php?p=19981520
Beamed by invisible waves from my rooted xt860
Click to expand...
Click to collapse
Yeah, I tried that and the gsm data patch. I'm having trouble adding/editing apns etc, can't join networks because "Your SIM card does not allow a connection to this network" etc. This is with cm7 and liberty. I have liberty on my safestrap now, running. I can get sms, make calls etc, wifi works. I'll firgure the rest out. If I want to go back to stock for data or something I just turn safestrap off and do an advanced restore of my /data partition to my backup from after installing the brazil retail.
I can't seem to make this work willis, i adb pushed those files to /preinstall but i still get constant FC of com.android.phone the only thing that makes it not do that is removing the sim. i'm confused
Endoroid said:
I can't seem to make this work willis, i adb pushed those files to /preinstall but i still get constant FC of com.android.phone the only thing that makes it not do that is removing the sim. i'm confused
Click to expand...
Click to collapse
I was gonna put together a flashable patch earlier but had some things come up and ended up in a hospital waiting room all night(next time I'll bring my laptop >.<). I'll toss it together asap and update the first post as long as I can flash it/it works. I should have mentioned (this is the confusing part) I pushed those files before enabling safestrap so /preinstall was /system if you get what I mean.
For CM7 to work correctly on GSM, I need to edit the init.mapphone_umts.rc file to setup all of the services the right way.
TBH, I never even looked twice at that file because I thought there wasn't anyone using it.
*blush*
Glad to see the XT860 crowd finally get some fun. )
Thanks Hashcode for putting so much effort into it, it's highly appreciated.
We were feeling a little bit left out.
Well, if you can get a version of CM7 working before I start having to study for exams, would be greatly appreciated.
But, if not, I'm sure I'll just divert time from studying to testing.
Sent from my Nexus S using xda premium
Accophox said:
Well, if you can get a version of CM7 working before I start having to study for exams, would be greatly appreciated.
But, if not, I'm sure I'll just divert time from studying to testing.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Changing your phone's firmware before exams is a bad thing... Trust me, I know Mine are starting next week!
Willis, I wondered if such was the case, I had safe system enabled and tried adb push to both /preinstall and /system as I wasn't sure how adb would recognize them in safe system. I also was pushing while in recovery
Beamed by invisible waves from my rooted xt860
danifunker said:
Changing your phone's firmware before exams is a bad thing... Trust me, I know Mine are starting next week!
Click to expand...
Click to collapse
Which is why I have a trusty nexus s
Sent from my Nexus S using xda premium
Hashcode said:
For CM7 to work correctly on GSM, I need to edit the init.mapphone_umts.rc file to setup all of the services the right way.
TBH, I never even looked twice at that file because I thought there wasn't anyone using it.
*blush*
Glad to see the XT860 crowd finally get some fun. )
Click to expand...
Click to collapse
After the little bit of testing I've done over the last day or two with different custom roms it looks like we're(xt860 and me863 users I image) going to have to have (or really really want) a patch we can flash against any custom rom to get our data and sometimes maybe phone up(or to keep it from crashing). Haven't been able to get 3g up (though the 1 method I did not try was to crash the phone through the dev tools in cm7 as was mentioned in another thread) on any rom yet. Phone/text works right off the bat w/liberty, mavs etc etc.
Narrowed down why Safestrap Recovery would only boot if a USB cable was connected on the XT860; it had to do with a line in the init.rc file executed when booting into recovery:
Code:
write /dev/usb_device_mode msc_adb
As well as a line in the postbootrecovery.sh script which accomplishes essentially the same thing, except via an echo command.
Obviously, we could just comment those lines out, but then we're left without adb in recovery without messy changes each time we want it. So, I whipped up a little script that checks if there is a USB connection and if so, run the previous necessary commands to enable adb and if not, then leave them out. End result: Safestrap Recovery is working like a charm now. No more need to worry about tinkering with my phone without a computer nearby to get into the recovery...
I attached the modified recovery.zip, just replace the original one located at /system/etc/safestrap/recovery.zip with the attached one and you should be good to go.
Related
This is a post I wrote for my personal forums nTelosDroid.com, but noticing there isn't a dedicated how to for CDMA Milestones, here it is!
So I posted how to root your Milestone using z4root a few days ago, which can be found here [link]. Now, with this post, I'm going to show you how to Root, ROM, and Restore back to the normal nTelos firmware. So heres the tools you'll need to begin. NOTE: These tools are all available for free! I'll host them for you on my DropBox as well as this server.
:!: WARNING: THIS CAN BRICK YOUR DEVICE MAKING IT COMPLETELY AND UTTERLY USELESS! I, MY SITE, OR MY STAFF, CANNOT BE HELD RESPONSIBLE FOR ANYTHING YOU DO TO YOUR DEVICE! :!:
So, first thing we have to do before ANYTHING else is root or "open" your device. How we achieve this is by installing z4root or Universal Androot. Install the app, follow the directions for z4root from this thread. If you install Universal Androot, once it's installed:
Open Universal Androot
Select Superuser for Android 2.0 ~ 2.2
Don't tick Root Temporary or it'll root until next reboot
Then click Root
If you just want root, stop here. If you want to make a backup and rom your device, continue.
Once you're rooted, exit to your Home screen, check to see if SuperUser was added to your list of apps. If it hasn't try to reroot. Once you see SuperUser, go to the Marketplace and download "ROM Manager" by clockworkmod. This is the tool we need to make a backup and rom the device. Once ROM Manager is installed, run it. You'll be prompted to enable SuperUser permissions. Click Allow.
Scroll all the way down to "Flash Alternate Recovery" which should say SPRecovery 0.99.3b
It'll go through a download process and after that it'll Flash your recovery.
DO NOT PULL THE BATTERY OUT OR SHUT THE PHONE DOWN! YOU'LL BRICK YOUR DEVICE!
Scroll all the way back to the top and Flash the ClockworkMod Recovery 2.5.0.1
It'll go through a download process and after that it'll Flash your recovery.
DO NOT PULL THE BATTERY OUT OR SHUT THE PHONE DOWN! YOU'LL BRICK YOUR DEVICE!
Once everything is flashed and finished, you are now ready to perform a nandroid backup.
Scroll to Backup Current Rom
A Window will pop up and you'll be able to name your new backup.
Once it's named to your liking, click ok. Your device will reboot.
After it reboots into recovery, it'll do a backup process. This shouldn't take more than 5 minutes.
It should make a backup and reboot.
If this doesn't happen, something has failed, pull the battery, reboot into recovery.
Perform a nandroid backup. If that doesn't work, Congratulations! You'll have to sbf! (Google how to do this)
Once this process is finished, you'll have a full backup of your current OS! Now, you can completely stop here and enjoy your nTelos Milestone as "Stock" or continue on to ROM your device.
Open ROM Manager again, and scroll down to Download ROM. Now here's where you have to make a choice. If you don't want to make it a simple easy process, use the free version. You'll have to clear your cache and data in recovery by yourself. This tutorial will not get into that.
Roming is one of those things that if you do it, you will need to know EXACTLY what you're getting into. You're gonna have to setup settings that are hidden in the phone to make things like MMS and Data work. I'm merely showing how to ROM the device, another tutorial will show you how to setup things that aren't working. If you take it upon yourself to write one, please let me know, I'll link to it here.
Once you've downloaded the ROM of your choice, before you do ANYTHING make sure you have a BACKUP!!! Once you have that done, you find the ROM from the downloads section that you want, I chose Bugless Beast (but Cyanogen Mod is another ROM of choice). Once it's done downloading, it'll give you the option to backup your current rom and wipe the data/cache. Select both regardless if you have a backup. It'll go through the backup/install process. Your device will ask you to go through the basic initial setup. If it doesn't, click on the Market and sign in. Once that's done, your data, voice, and sms will be completely ready! If you want to enable MMS (Picture/Video Messages), follow these steps.
Open Voice Dial (NOT Voice Search)
Say in a clear voice "Open APN's". This may take several tries.
Once it's gives you that choice, click it.
You'll see Verizon, tab it, change the name from Verizon to nTelos first
Scroll down to MMSC and enter http://mms.ntelospcs.net
Hit the Menu button (the Four bars next to the House on your device) and click Save
Send a MMS to yourself to test the settings work!
And that's it! You have Rooted, Backed Up, and ROMed your device in under 1 hour! :lol: CONGRATS! :lol: If any thing messes up, you always have your back up. Boot into recovery by pressing and holding X then hitting the power button while keeping X pressed. Go to nandroid and recover from your SD card! Hope this helps!
z4root
Universal Androot
ROM Manager
I hope that this is a help for ANYONE on ANY Forum! Please, feel free to copy/paste this anywhere you feel necessary!
EDIT: For those with LOCKED Bootloaders, there was a post deep in the thread for unlocking them. Here's the quote:
meltwater said:
I have the same issue.
Could the OP of this sticky be updated for Milestone users which have locked bootloaders to point them to:
http://forum.xda-developers.com/showthread.php?p=17569718
Spent ages going in the wrong direction when all I needed was to use OpenRecovery instead.
Click to expand...
Click to collapse
Very Nice
Great job and all of us CDMA a854 milestones thank you. We need more CDMA stuff!
The Apns part didnt work for me. It either won't save or goes blank and reverts to Verizon on reboot. *tried APN manager as well* Also I noticed the marketplace usually says My Apps, but will switch to Verizon if you flash to say Cyanogen 6.1.2., Bugless ,or LFY.It would be great IF we could get developers to have ROM with no APN's so we can add our own.
Thanks again for the guide, nicely done.
icemanak said:
Great job and all of us CDMA a854 milestones thank you. We need more CDMA stuff!
The Apns part didnt work for me. It either won't save or goes blank and reverts to Verizon on reboot. *tried APN manager as well* Also I noticed the marketplace usually says My Apps, but will switch to Verizon if you flash to say Cyanogen 6.1.2., Bugless ,or LFY.It would be great IF we could get developers to have ROM with no APN's so we can add our own.
Thanks again for the guide, nicely done.
Click to expand...
Click to collapse
Yeah man! No problem! As far as APN Manager/APN Backup & Restore. If you just edit the MMSC, do you have the same problem?
Oh I tried APN manager and a slew of others. Still didnt work, editing the MMSC either. There is a way to drop APNs into the Rom before installing.Ipfreelytech made one for me. But if I want to run other ROms it would be nice to have a real fix.
Nice work wish I had it before I began...
icemanak said:
Oh I tried APN manager and a slew of others. Still didnt work, editing the MMSC either. There is a way to drop APNs into the Rom before installing.Ipfreelytech made one for me. But if I want to run other ROms it would be nice to have a real fix.
Click to expand...
Click to collapse
I was actually thinking of making a rom for cdma non vzw milestones
stevgunt said:
Nice work wish I had it before I began...
Click to expand...
Click to collapse
I saw that thread and someone asked for one, figured I'd make one
Tappin' and a Talkin' from my Milestone
Yay Non -verizon Rom!! please make one I'd help test it out
I'm getting the website built at the moment. Started looking at how to's today, but I'll PM you to let you know what's up. Thanks for your interest!
I would be interested in testing as well....
AWESOME
Glad I found this post. I live in Roanoke, VA & my carrier is nTelos. I have been looking for WEEKS on an Android Sense 2.2 rom. I mainly want to just have to option of saving my apps on my SD card. I love Android but WinMo has 1 up on Android with being able to install apps to the SD card.
Good luck & I can't wait to see what you come up with!
I am in Roanoke as well
Will this work for an Alltel Milestone.
As far as I know, this should work on most cdma a854's
From the Milestone
It works with Alltel. I just need to know if I can flash back to my stock 2.1 update 1 nandroid backup from CyanigenMod 6.1.2 without running into problems with the kernel not being compatible. I heard that if you flash between Froyo and Eclair you'll brick your phone because the kernels aren't compatible. Is this true?
Alltel Motorola Milestone A854 / Droid CyanogenMod 6.1.2.
Can't find the sbf for Ntelos
I need help returning my phone to the stock sbf. I rooted my phone, all was well until I started playing with Titanium Backup. I deleted Google talk, and as a result I would get this error "process Google.process.gapps has stopped unexpectedly" I tried several different things to fix it but finally decided to just flash back to the stock ROM/sbf. I used the MILER_X1-00.26.1 (I now know that my build is 00.26.0) that and-developers.com sites for use. The problem is that now I have the Verizon stock info on my phone. It changed the MIN, PRL MEID AND phone number. I get an error on start up that my phone needs to be activated, it places a call that starts off "welcome to verizon, to activate your phone......" So now I have no phone service. I can use the wifi so I have access to everything that has been backed up via Titanium Back up, but as you know that will not contain any system data from the stock sbf. Does anyone have any ideas or am I just prolonging the insurance call for replacement?
Conner85 said:
It works with Alltel. I just need to know if I can flash back to my stock 2.1 update 1 nandroid backup from CyanigenMod 6.1.2 without running into problems with the kernel not being compatible. I heard that if you flash between Froyo and Eclair you'll brick your phone because the kernels aren't compatible. Is this true?
Alltel Motorola Milestone A854 / Droid CyanogenMod 6.1.2.
Click to expand...
Click to collapse
I've flashed from Froyo to Eclair with no issues
Tappin' and a Talkin' from my Milestone
smb1966 said:
I need help returning my phone to the stock sbf. I rooted my phone, all was well until I started playing with Titanium Backup. I deleted Google talk, and as a result I would get this error "process Google.process.gapps has stopped unexpectedly" I tried several different things to fix it but finally decided to just flash back to the stock ROM/sbf. I used the MILER_X1-00.26.1 (I now know that my build is 00.26.0) that and-developers.com sites for use. The problem is that now I have the Verizon stock info on my phone. It changed the MIN, PRL MEID AND phone number. I get an error on start up that my phone needs to be activated, it places a call that starts off "welcome to verizon, to activate your phone......" So now I have no phone service. I can use the wifi so I have access to everything that has been backed up via Titanium Back up, but as you know that will not contain any system data from the stock sbf. Does anyone have any ideas or am I just prolonging the insurance call for replacement?
Click to expand...
Click to collapse
Call customer support. The EXACT same thing happened to.my first Milestone. Tell them you don't know what happened and you want it fixed.
Tappin' and a Talkin' from my Milestone
Moved and stuck.
Root+Overlock rapid method
Android by O2 :
tested today:
UniversalAndroot 1.6beta + Milestone Overlocking 1.48 from Market (free) and rulez
@ cfultz
Is there a chance you could put a brief description of the Sbf wipe / restore method, or maybe a link you know of? I've been digging for a week and all I find are droid 2 & X references. ROM manager decided to not get me back to a recovery / boot loader screen and I am really stuck.
Sent from my Droid using XDA Premium App
**Edit**
Really not trying to be lazy, but all the .sbf methods I've read so far seem require you getting to a boot loader. If I could get to a boot loader this wouldn't be a problem, as I made a back up of my stock ROM. I have a functioning bugless beast ROM, just no recovery / boot loader, and no way to flash back to my recovery.
**Edit**
Problem fixed, sorry for the interruption.
Hey guys,
I finally got 3G data working in Hashcode's port of ICS to the Droid 3/XT860. I'm currently using the isuacell (Mexico) revision on a Bell XT860; I wasn't able to get ICS to boot up on the current Bell update, although I'm sure it's something simple I've overlooked. I'm fairly certain it'll work on other software updates such as the ones from Argentina/Brazil, and possibly the ME863 but I don't have the time to test it myself, let me know if it works for you if you're running any of these updates.
Nevertheless, I got it working pretty easily. I don't have time to do a full writeup right now but it was exactly what I suspected earlier, a minor issue in the Android framework causing an exception that would disconnect 3G data a few seconds after a connection to the APN was successfully made. That, combined with Motorola's RIL library from the isuacell firmware and a few build.prop tweaks were all it took, and so far it is running pretty good.
Only major thing I've noticed so far is that the cell status indicator only seems to indicate either perfect reception or none, no in between, but for now I'm pretty stoked this is working as I can finally use ICS on a daily basis instead of switching back and forth a dozen times a day.
Here's a link to a .zip to be installed via Safestrap. Be sure to perform a factory reset and to be safe, mount system and format it in the "mounts and storage" area before installing the zip to ensure a clean install. Also, as Hashcode had mentioned in his release thread, don't let it restore your old settings when you run through the Setup Wizard on the first boot. Enjoy, and be sure to thank Hashcode for all the effort he's put into making our phones even better!
http://dl.dropbox.com/u/22632665/CM9_XT860.zip
md5=6302b1733777ad5d7e3d5483d9291591
176820984 bytes
---------------------------------------
EDIT: I was lazy earlier and just posted the link to the full update, I finally got around to releasing a significantly smaller, more sensible patch:
http://db.tt/HEbusNM3
xt860_ics_patch_01_30_2012-safe_system-signed.zip
md5=60dc2db347c7310d0f5e51b0e02b9952
4231015 bytes
I recommend flashing Hashcode's Alpha 5 release, then doing a factory reset before installing this update in Safestrap. I can make one for the non-safe system users out there too, just didn't bother but it'd take two seconds.
Also, check out my github repos for the changes I made to get 3G data working. (You'll probably laugh when you see the change to android_frameworks_base):
http://github.com/buddyrich
I've kind of mimicked Hashcode to keep things simple; my changes are in the branch "ics-xt860". The easiest way to compile it all from scratch is like this: (Assuming you're in your working directory)
1) repo init -u git://github.com/CyanogenMod/android.git -b ics
2) cd .repo
3) git clone git://github.com/buddyrich/android_local_solana.git
4) cd android_local_solana
5) git checkout ics-xt860
5) cp local_manifest.xml ../
6) rm -f -r android_local_solana
7) repo sync -j24
8) Place this file in the root of your working directory, eg: ~/android/system/ : http://db.tt/1HpM2m6r
9) vendor/cm/get-prebuilts
10) . build/envsetup.sh
11) brunch solana
nice, it works!
Rick#2 said:
Also, as Hashcode had mentioned in his release thread, don't let it restore your old settings when you run through the Setup Wizard on the first boot.
Click to expand...
Click to collapse
I see this mentioned everywhere, and now I just have to ask. What happens if you do let it restore your old settings?
funny....i got 3G, but i cant make a call nor receive a call......
is that my problem or known problem?
That is strange, I can make and receive calls without any issues. What software/baseband are you using?
albatorsk said:
I see this mentioned everywhere, and now I just have to ask. What happens if you do let it restore your old settings?
Click to expand...
Click to collapse
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.
Rick#2 said:
That is strange, I can make and receive calls without any issues. What software/baseband are you using?
Click to expand...
Click to collapse
kinda strange, i wipe and try now, sometimes clean install but got phone.apk freeze, my latest try is ok....
emprize said:
kinda strange, i wipe and try now, sometimes clean install but got phone.apk freeze, my latest try is ok....
Click to expand...
Click to collapse
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.
nice ill try later
Enviado desde mi XT860 usando Tapatalk
goalando said:
nice ill try later
Enviado desde mi XT860 usando Tapatalk
Click to expand...
Click to collapse
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.
So far so good. Thanks a lot
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
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!
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
Is anyone else finding that touch events take longer to register?
Sent from my XT862 using xda premium
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
Edited the first post with a much smaller patch and some more info on what's going on.
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");
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...
Rick#2 said:
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...
Click to expand...
Click to collapse
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.
My phone has come a long way... from stock Bell to Chinese ME863 stock to Brazilian XT860 stock, to Mexican XT860 stock, to bootstrap, to safestrap, back to bootstrap, and onto Liberty ROM (great rom!)
What bothers me is when "Pay Phone" appears when some people call me (research seems to indicate that these people have a name attached to their phone number, and also if the provider allows you (your plan?) to see these).
Anyway, I don't recall the Chinese stock rom behaving in this way, and I'd like to flash back to it, but I can't (RSD lite and even moto-fastboot methods give up at the first flash... the CDT).
Am I stuck in the world of Brazil/Argentina/Mexico stock roms? That's not a bad thing, of course, as they open up other avenues... but the Pay Phone thing is killing me!
Any help/info would be appreciated. Thank You
LaZiODROID said:
My phone has come a long way... from stock Bell to Chinese ME863 stock to Brazilian XT860 stock, to Mexican XT860 stock, to bootstrap, to safestrap, back to bootstrap, and onto Liberty ROM (great rom!)
What bothers me is when "Pay Phone" appears when some people call me (research seems to indicate that these people have a name attached to their phone number, and also if the provider allows you (your plan?) to see these).
Anyway, I don't recall the Chinese stock rom behaving in this way, and I'd like to flash back to it, but I can't (RSD lite and even moto-fastboot methods give up at the first flash... the CDT).
Am I stuck in the world of Brazil/Argentina/Mexico stock roms? That's not a bad thing, of course, as they open up other avenues... but the Pay Phone thing is killing me!
Any help/info would be appreciated. Thank You
Click to expand...
Click to collapse
Do you need to flash all the partitions to fix that issue? I would think either radio.img or system.img would be responsible for this as caller id is network transmitted. Perhaps try motofastboot flash just one or the other of these
I've also heard that some 3rd party apps can fix this issue. Try poking around the market see what you can find. I have heard that this is a rogers issue with unlocked devices, not just the xt860
Sent from my XT860 using xda premium
Flashing radios and testing sounds more fun
Thanks Endo
To fix "pay phone" just call up rogers and have them remove the name display feature that is packaged with call display.
That's it! Btw why not try using the willis111 bell 2.3.6 deodexed on it? The stock 2.3.6 is pretty awesome, good performance and all.
Sent from my XT860 using xda premium
Because I'm stubborn and dont want to call Rogers to remove the feature, I flashed the ME863 radio to my phone (running eclipse rom right now), copied the ME863 libmoto over (thanks dove0rz for dropping that in the forum!) and noticed that i wasnt getting signal.
I then copied dove0rz's ME863 build.prop (but it was made for cm9)... got signal, did the test.. and voila.. no more Pay Phone. Problem is nothing else really works on my phone. LOL.. (i.e. almost all apps FC).
I expected issues, just wanted to see it working.
My question now is... could minor modifications to the original build.prop (of eclipse rom) get my signal up and running? I wish I knew more about the settings in build.prop. I plan on comparing the original build.prop and me863 cm9 build.prop side-by-side to see if there is a magical line or two that needs adjusting. But any input/help by you experts out there would be appreciated.
This issue's been around for a while and is not specific to the XT860, it also exists on other Moto devices, some HTC and LG devices.
I can't test it because I'm not on Rogers... so I don't have the "Pay Phone" issue..
But I know for sure that using a build.prop from a diff device is usually bad.
So try taking the one that comes from whatever ROM you are on, and look for these lines, that's what I need to get CM9 running with signal on my XT860:
rild.libpath=/system/lib/libmoto_ril.so
ro.telephony.disable.globalnwswitch=true
umts.apn_authentication.enable=1
ro.telephony.default_network=3
ro.telephony.ignore.linkiperror=true #note sure if this one is absolutely necessary
Obviously YMMV as I'm on CM9..
But to get signal on anything other than stock, or Brazil or Latam..
I'd start by making sure it's a freshly flashed working ROM then copying the stock libmoto_ril.so and adding/changing the above lines to your build.prop file
And when you say
could minor modifications to the original build.prop (of eclipse rom) get my signal up and running?
Click to expand...
Click to collapse
Do you mean Voice or 3G or both ?
Also here's a quick list of the available SBF files for our phone:
http://sbf.droid-developers.org/umts_solana/list.php
Thanks PM. I updated/added the lines you suggested to a fresh installed Eclipse ROM's build.prop. Also replaced the libmoto_ril.so (and set 644 permissions to both build.prop and libmoto_ril.so of course). Rebooted and didn't seem to work (No signal at all.) Wifi seems to be working OK.
And yes, what I meant for signal was both voice and 3g.
Thanks for your help. I'm still comparing the original build.prop with the me863 cm9 build.prop to see what got it going by simply dropping the cm9 build.prop in... will update if any progress. Not sure if I'll get far because a lot of this is new to me still.
Upload both the build.props? Or search "web diff tool" in google and paste your files in there, that might help isolate the modified lines
And.. Does it even detect the sim card?
I recall seeing the SIM icon at the top of the screen, if for a few seconds. I can't quite recall if/when it went away. I'm going to try again and keep an eye on that. I was staring at the signal bar and crossing my fingers. Haha
Attached is dove0rz's me863 build.prop for cm9, and the me863 libmoto.
Also attached is the Eclipse 2.0 (for D3) original build.prop.
Thanks
So.. just to recap..
You're on Eclipse ROM.. get no signal.. and when you copy the attached cm9 build.prop, this gets you signal.. but everything FCloses?
Do you only have connection issues in Eclipse after flashing the Chinese radio?
PS: To spot the differences between 2 files, try this: www.aldram.com/Diff.aspx
There's also notepad++ with the compare plugin that achieves a similar diff..
You're on Eclipse ROM.. get no signal.. and when you copy the attached cm9 build.prop
Click to expand...
Click to collapse
PLUS the me863 libmoto_ril.so
this gets you signal.. but everything FCloses?
Click to expand...
Click to collapse
Every app I try to run FC's. Things are pretty good if I use Phone or text (only). I had it running like that for a full day because I wanted to check the caller ID. Saw 3 numbers/contacts appear (that would - on the Mexican/Brazil radio say Pay Phone)
Do you only have connection issues in Eclipse after flashing the Chinese radio?
Click to expand...
Click to collapse
Yes. Normally (on the Mexican radio - p2b_solana_umts_solana_iusacell_mx-user-2.3.6-5.5.1-112_SLU-57M-111107-release-keys-Latam-01.xml.zip) what I'd do for my Eclipse install (a fresh wipe/install) is push my Bell stock limoto_ril.so to /system/lib and set permission to 644 - which allows me to add my APN's.
PS: To spot the differences between 2 files, try this: www.aldram.com/Diff.aspx
There's also notepad++ with the compare plugin that achieves a similar diff..
Click to expand...
Click to collapse
I didn't know notepad++ had a compare plugin. Neat. Thanks!
LaZiODROID said:
PLUS the me863 libmoto_ril.so
Every app I try to run FC's. Things are pretty good if I use Phone or text (only). I had it running like that for a full day because I wanted to check the caller ID. Saw 3 numbers/contacts appear (that would - on the Mexican/Brazil radio say Pay Phone)
Yes. Normally (on the Mexican radio - p2b_solana_umts_solana_iusacell_mx-user-2.3.6-5.5.1-112_SLU-57M-111107-release-keys-Latam-01.xml.zip) what I'd do for my Eclipse install (a fresh wipe/install) is push my Bell stock limoto_ril.so to /system/lib and set permission to 644 - which allows me to add my APN's.
I didn't know notepad++ had a compare plugin. Neat. Thanks!
Click to expand...
Click to collapse
Hey, I'm having the same issues you were having. I started with stock Chinese on ME863 flashed to the Canada XT860 (and tried Brasil to) stock, but can't get data of any kind working. No data not 2g not anything. What did you end up doing for a solution.
Likewise, tried to downgrade back to original china retail stock but have the cdt problem.
Thanks, Sorry I know its been a long time since this post.
It might be the build.prop
Sent from my xt862 using xda app-developers app
As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? I got confused with that.
Afterwards, I dl safestrap once I'm rooted? or should I just dl it and put it onto my phone all at once?
Apologies for the noobness. I'd rather be a noob asking questions than a retard who goes ahead and does things and finds out he screwed up too late.
Rooting is done to get superuser permissions within Android so you can install some advanced apps and modify system files which can all be done from within the stock ROM. Rooting then flashing an unofficial ROM is a little more advanced and something I haven't done yet so I can't help you much there. I'm waiting for something a little more stable since my Droid 3 is my main phone. You can read Hash of Codes site (the developer of ICS/JB for the Droid 3) on how to safestrap:
http://blog.hash-of-codes.com/how-to-safestrap/
To root use Motofail. I know it says its for the Droid 4 but the original Droid 3 root exploit was patched with the latest OTA so we have to use the Droid 4 method called Motofail:
http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
DróidScìon said:
As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
.
Click to expand...
Click to collapse
My D3 has Maverick as non-safe for daily driver and the latest Hashcode for fun. I find that to be the best combination. Once Hash finishes the camera and JB is working reasonable well, JB will be my DD.
I also have an SGS3, TF300T, and a Spica, all of them rooted.
once rooted, make sure you use safe strap. It makes roms easy to try out before having to settle
Sent from my DROID3 using Tapatalk
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
DróidScìon said:
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
Click to expand...
Click to collapse
Safestrap 1.08 is the 'normal' ssafestrap
Safestrap 1.08e/f/g is an advanced safestrap with extra features like touch etc but not by hashcode
Safestrap 2.10 is the latest which allows the new kernel with the kexec ICS/JB to be used.
2.10 It appears to also work fine with normal roms so i'd use that
DróidScìon said:
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? .
Click to expand...
Click to collapse
If you were stock 906, there was no reason to run the 1-click.exe - that's only for people who rooted their phones and deleted bloatware to get the phone back to stock, or people whose phones are bricked somehow. Coming from stock, just running Motofail was enough to root.
I will concur with everyone here that running rooting, installing and running Safestrap, and installing a custom ROM - and leaving your rooted stock alone - is the best way to go. It will be a lot easier to unroot later on if you want to sell the phone, etc.
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It doesn't matter. Choose which has enough space.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It's asking where to backup TO, like the post above me, choose wherever has space. Backups are about 1GB. You may wish to move it to your computer after if you don't have much space on your device. You can always stick it back on your external sd via card reader if needed, but it's really hard to brick while using safestrap
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Sent from my XT860 using xda premium
I saw that, and before I rooted, I did a Factory Reset on the phone and formatted my SD card. So I have 11+gig free on Internal and 15+gigs on External.
Now, I just need to learn to Flash RoMs (probably more to it than just hitting a button that says flash .zip) and find some info on the "must-have" apps for a rooted phone.
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
DróidScìon said:
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
Click to expand...
Click to collapse
If your contacts are on your google account they will show up.
What other account info do you mean?
You should go ahead and restore contacts. just go to Settings>Accounts and Sync>Google, then turn contacts sync on.
Endoroid said:
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Click to expand...
Click to collapse
I must have made another noob mistake. Everything went well, up until my first startup with the new OS (cyanogenmod9). It has been at the startup screen for over 15minutes right now. I must say, it is one awesome startup screen, with the blue effects and all, but I would love to get to the desktop/homescreen, haha.
If you guys have any advice I would greatly appreciate it. This is a Droid 3, it was rooted a couple hours ago, I did the safestrap as described, created a backup file, etc. My only guess is I jumped the gun by trying this OS on my Droid3 and it may still be under development? FWIW to you, this is the first I've rooted or modded a smartphone in my life, from 0-full speed in a couple hours is what I was shooting for using everyone elses experience.
thanks
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Phibernaut said:
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Click to expand...
Click to collapse
thanks. since my last post I used a more detailed how-to, and wiped 3 different areas for data. Now, i had only a black screen (with power, barely lit) and it never even got to the cool blue screen.
I'm currently in safestrap after pulling my battery again, just trying to figure out how to revert back to my standard OS (rooted) and try a ROM like MavRom since it's suppoedly fully capable and stable. I'd love ICS, but I just want a working phone right now
---------- Post added at 10:25 PM ---------- Previous post was at 10:14 PM ----------
good news is, I did enough steps correctly, that I was able to startup in my unsafe mode, and my normal rooted system is functioning fine. That makes me very happy.
This duel boot thing is pretty cool, reminds me of having bootable thumb drives on my old linux system with different OS's. I hope i can get a seperate OS working, however, that fits my needs for a day to day functional phone, without all of Verizon's crap on it
Once rooted use titanium backup to back up apps and data.
Only restore with the same ROM though, the following is in increasing order of risk
restore app only to exact same ROM+version
restore app+data to same ROM+ver
restore app only to update of same ROM
restore app+data to updated ROM version
play chicken with a bus on a highway
restore apps to different kernel e.g. CM7 backup => restore to CM9
check to see what a gun firing looks like down the barrel
restore app+data to different kernel
restore app+data to an older ROM or kernel
do anything at all with system apps+data if you don't know what you're doing
Okay, looking to get more involved and learn a lot more in hopes of contributing someday but for now I'm stuck. I picked up a very used Droid 3 on Ebay and rooted it with MotoFail, then installed SafeStrap 3.05 & everything seemed fine. Problem is I can't boot into any "safe" ROM slots, it just gives me a blank black screen & I have to remove the battery to restart. My original D3 has CWM on it, but I was always too scared to flash anything too drastic so this is my test toy. It is running on the 906 with SS version 3.05.
I downloaded a bunch of ROMs and none work. I tried restoring my backup which I'm sure I saw somebody do on Youtube but I have since read that won't work anyway but I'd still like a "stock" rom in a safe slot. I also tried the official 906 zip, but also read somewhere that that only works on the stock partition. I tried aokp_toroplus_nightly_2013-08-20.zip, D3-Eclipse-v3.0_NON.zip, minimoto_v1.7.zip, & the afore mentioned VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.XML.zip but none would even flash, just gave errors. Also tried KEXEC-cm-9-20120905-UNOFFICIAL-solana-SS2.zip, Liquid-JB-v2.9-OFFICIAL-solana.zip, & something small called phablet-20130327-cm_solana.zip. That last one, tried usually in slot 4, is the only one that does something other than give a black blank screen - it eventually shuts the phone off. I read that Liquid had to be in slot 3 so that's where I put it every time.
I DID discover that I don't think Busybox was installed during the root this time, when I rooted my original D3 it was already there. So I installed a BB from Market, then went into SS & uninstalled, then reinstalled. Rebooted into recovery and re-wiped all the slots (except stock of course) with all 4 options (cache, dalvik, system, & uh, something else I forget now) & re-installed the ROMs but nothing changed.
More possible helpful info: When this BB installed it gave me an option of normal install or more thorough "smart" install, I did the smart install, also installed CWM ROM Manager to try something but that didn't work either, and downloading official ROMs through that always gives an error. Data sizes of slots are all 2GB except #4 which is only 1GB. Under the "Mount" tab, system & (either data or cache, can't remember) are unchecked, and the 3 "unmount" boxes below are checked. Using a root explorer, I can confirm that SS did "install" the roms & each slot contains a cache.img, system.img, & a userdata.img.
So, what am I doing wrong guys? Any help or ideas would be greatly appreciated! Sorry for being such a noob here, Thanks in advance!
I think I would just start over. FXZ the phone back to stock and re-root with Motofail. Make sure that you unzip the Motofail download and disable any virus checker you have. It does sound possible that the lack of busybox may be the cause of your flash failures. I can tell you for 100%, absolute, certain that Minimoto will flash on any ROM slot in Safestrap 3.0.5.
Eclipse 3.0 as you download will not install in Safestrap, but I created a Safestrap-enabled version. You can find it here: http://www.droidforums.net/forum/teamhaters/210971-eclipse-v3-0-droid-3-port-11.html#post2414744
I think that the Dropbox link is still live. Let me know if it's not there...
All of the KEXEC ROMs, if I am not mistaken, have to be installed in ROM Slot 1. (I never used them, beyond just seeing what it looked like, and it's been a while since I tried.)
Get Motofail here: http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
It says it's for the D4, but it's what the D3 will be rooted with as well.
Success!!! Thank you!!! I am now up & running with all 4 slots filled, currently with Avatar, Maverick, Dark Droid, and a generic non-VZW stock. The Eclipse links were down (Dev Host) but if you still have an Eclipse for SS I would love to take a look at it. Already tried the Ubuntu Touch one too, "Phablet" or something, but couldn't get at a menu to connect to my WiFi. And, since you are so helpful... I was wondering if you could point me to some stuff to read & research. There are plenty of guys (& a few girls I'm sure too) making great ROMs but they need to be ported to different devices. So I would like to eventually learn how to port SS to different devices and ROMs to SS. It seems there are really only a few people working on that stuff and that is where the help would be needed. Working my way through the XDA University thing too. Thanks again for your help!
I'm glad you got that figured out.
Lobstercat said:
The Eclipse links were down (Dev Host) but if you still have an Eclipse for SS I would love to take a look at it.
Click to expand...
Click to collapse
The Eclipse that you were trying to download isn't Safestrap ready anyway, but I created one that's on my Dropbox: https://www.dropbox.com/s/hyl3gzurgh8bvdw/Eclipse3.0-SS3-signed.zip
doogald said:
I'm glad you got that figured out.
The Eclipse that you were trying to download isn't Safestrap ready anyway, but I created one that's on my Dropbox: https://www.dropbox.com/s/hyl3gzurgh8bvdw/Eclipse3.0-SS3-signed.zip
Click to expand...
Click to collapse
uploaded copy to http://d-h.st/xFd