droid 3

All posts tagged droid 3

How CM7 fell onto my Droid 3 (and possibly yours too)

Posted by hashcode0f on October 18, 2011
Posted in: Android. Tagged: , , , , .

It’s been a while since I had a real update regarding CM7 …

** [UPDATE 10/18 PM] Phone now works in the newest build.  And I included the missing Usb file so charging and SD share work as well.   See download link below. **

I’m not sure I would call this a beta.. it’s more of an alpha and very untested.

As long as you know that there are still critical features of the phone which don’t work (read as: making a phone call), then I think it’s safe to open up beta testing and let whoever wants have a bit of fun on their Droid 3.

I recommend that before you start, take a gander at this post on the installation process in Safestrap: Beta testing CM7 w/ Safestrap

Take a look in the files section for the latest builds: Android Files and for GB-based GApps go here.

For open items / bugs please use the Bug Tracker

Now that I’ve lost the crack-flashers, let’s talk about what is working in this build:

  • Phone, Wifi, Internal SD Card, Audio, GPS, etc.  Feel free to flash gapps and test away.

What isn’t working:

  • Camera app will blow you back to the Boot Animation
  • Phone app will FC on the boot, just close the notification and continue.  3G service restarts immediately.
  • Only 1 SD card for now (internal).  I have some code to fix in the MountService.  It’s trying to mount the external card with the options that are added in the vold.fstab (“/mnt/sdcard:none:lun1″ has a funny smell to it)

Why did this take so long?  In theory you an scan the changelog for good night-time reading.. but here’s a summary:

  • To keep it short: I’m a noob.  I’ve never ported a phone or coded any lower level stuff for Android till September when I got my Droid 3.  So in several cases I had to do things 2-3 times to get it right.
  • OMAP4 code for Android devices is in a huge state of flux for Gingerbread.  It’s like trying to break into the “cool club” that’s guarded by a 7 foot bouncer who has crazy eye.
    • CM7′s hardware code was added about 7 days ago.
    • the matching OMAP4 code for the framework is still being patched, but available via review.cyanogenmod.com for those that know about it.
    • And then it still needs to be updated and tweaked.
  • I didn’t want this to be a BAD CM7.  So, taking the time to make sure it was optimized correctly for the phone was important (see above about OMAP4)
  • Motorola is doing some odd things with their official GB builds.  They added users/groups which aren’t stock.  Those users are sprinkled throughout some of the binaries for which I don’t have source.  “battd” for example starts out with root permissions and drops to mot_pwirc (user 9000).  So after days of troubleshooting and banging my head against various hard objects, I added these special users to my init and system to make this build work.
  • I did get some HUGE help from several devs and want to make sure they’re called out:
    • Arcee has been the lone ranger for OMAP4 stuff for about 3-4 months (LG Optimus 3D).  You can thank him for the majority of the CM7 frameworks/base code which has been optimized. (I actually tried doing what he did for the framework initially, and ended up ditching it in favor of his work because it’s much more complete).
    • the “cyanogenmod-dev” IRC channel (Turl, Epsylon3, et al) had some helpful hints at times when I was sort of lost.
    • I used the Droid2WE board config as a starting point (RevNumbers, jbirdvegas)
    • And I pulled some initial config stuff from CVPCS’s Bionic board as well.

Enjoy the AOSP ROM goodness and have fun.

Hashcode

CM7 for the Droid 3 and Sandbox Bootstrap

Posted by hashcode0f on September 28, 2011
Posted in: Android. Tagged: , , .

Late last night after several days of strace hell, much gnashing of teeth, and a bit of coffee; I finally booted up to the grassy wallpaper lockscreen of Gingerbread CM7 goodness.

I’ll be honest, I had no idea what it would take to get it running when I started.

My Droid 3 alpha port of CM, relied on several things:

  • Right off the bat, I was lucky and was able to use cvpcs’s Bionic device board as an initial reference.  Note that while the device board settings help get you started, it’s not a full working config.   I’m guessing he has commits on his drive that aren’t at GitHub.  And I had to make several alterations for the Sandbox configuration that I’m running (more later on this)
  • Persistence.
  • Persistence and oh some troubleshooting skills.

For the last week my nights have been:

  1. Boot into recovery
  2. Play with init* files via adb.  (mainly setup tracing and or make config changes)
  3. Attempt a boot, get stuck at “Dual Core”
  4. Reboot recovery, grab logs.  See errors.
  5. Try and fix errors.  Goto step 1.

Part of what made the process more difficult was that I’m running a non-standard Bootstrap and a modified version of Koush’s recovery to bring the system up.  I call it the “Sandbox Bootstrap” for the moment.

As a programmer I like to understand how things work, and one of the reasons I didn’t use the stock CM hijack was to get a feel for how locked bootloader phones get other versions of Android to run.

The idea for operating in a “sandbox” is simple:

  • We have a locked bootloader, and if we play around with /system too much, we’re stuck with a fastboot recovery. (Didn’t your mother warn you about that?)
  • Also, I’m not really a “developer”.  My phone is actually a phone.  On Monday morning, I need to make phone calls with it.  I needed a way to “flip” back to a working state fairly easily and reliably.
  • If you want to be a tester for one of my ROMs, then I want you to have the same smooth process for swapping into a testing environment and back out to a usable phone.  Because god knows, I’m going to fuck this ROM all up as I go along.  And your phone will be broke.

Enter the Sandbox Bootstrap (or 2nd-system).   There are 3 main portions to it (just like any other Bootstrap):

  • It does a “boot to recovery” check (booting from “BP Tools” mode)
  • It then checks for file called “alt_system_mode” in /system/etc/recovery/flags.  If that file is present, it 2nd-init’s.  And resets the OS to boot from the /preinstall partition.
  • If it doesn’t find either, then it lets the system boot normally.

I make use of a slightly customized version of Clockwork Recovery to help with this process.  Right now, I’m working on smoothing out the transition from system #1 to system #2.  The end result will be a “Swap Systems” option which does the following:

  • adds/removes that alt_system_mode file under the original /system
  • makes a backup of the current userdata
  • restores an alternate set of userdata depending on which system you’re turning on
  • and wipes the /cache.

All via 1 option (with a confirmation of course).

So, I can debug CM7 till I’m blue in the face till 3am, then swap back to MotoBlur and go to work at 7am with a working phone.

The other issue for the recovery is applying .zip updates.  Normally, anytime a .zip makes changes to /system, it has the chance to break recovery and you’re left with a fastboot restore (again).

In my option, this is unacceptable for a phone that I like to “play” with.   In my  customized recovery it applies .zip updates to the /preinstall partition like it was /system.  Now the caveat is if the .zip file mounts the block device for the original system (mmcblk1p21), then it will make changes to your main system.  Beware these .zip files. :P

Hopefully, I’ll wrap a bow on all of this and put it out in the wild over the next day or so.  Check back here for updates / downloads.

NOTE: Using my Sandbox Bootstrap will remove the files that the stock Bootstrap puts in place.   Something to consider before choosing to use it (and the ROMs I will be putting out.)  If there’s enough interest may also release ROMs with a more stock configuration to use with Koush’s standard hijack.  We’ll see.

Stock CM Bootstrap for Droid 3

Posted by hashcode0f on September 23, 2011
Posted in: Android. Tagged: , , .

NOTE: ** This is not for use w/ CM7 alpha for Droid 3.  Use “Safestrap” instead found here. **

Over the last few days I’ve gotten a lot of questions about “When will ROM booting” be supported, etc.  And I’ve been working on a separate project to make that happen in a somewhat safer environment for us locked bootloader commoners.  But, I realize that might take longer than some really want it to.

So, since the demand seemed to be there for it.  I went ahead and threw together the stock hijack recovery Bootstrap for ClockworkMod Recovery.

Notes:

  • Yes, it will support ROM loading (using the CM hijack/logwrapper per the source).
  • Yes, I am immediately handing this off to Koush so he can do what he wants with it for ClockworkMod support.
  • Don’t hate me if you manage to brick your phone installing this.
  • The APK was based off Koush’s Droid 2 Bootstrap code with updated binaries.
  • This CWM Recovery is version 5.0.2.3
  • This APK contains a rather large busybox build (1.9M).
  • If you wait, I’m sure Koush will put up the official version in the market.

[UPDATE: 9/30] I added BP Tools boot support as well as fixed the boot loop into recovery issue.  You’ll need to re-use the “Bootstrap Recovery” button anytime you flash a ROM to re-update your hijack binary.

[UPDATE: 3/7/2012] Link removed — out of date

(Original Non-Stock) Droid 3 Bootstrap

Posted by hashcode0f on September 16, 2011
Posted in: Android. Tagged: , , , .

Today, I put the finishing touches on the Droid 3 Bootstrap application.

Once installed on your Droid 3, you can use it to install a ClockworkMod-based Recovery that I talked about a few days ago.  Where you can make backups, perform restores and apply .zip files (though you better know that the update.zip is safe for the Droid 3).

[ NOTE: This requires that your phone be rooted.  And, this is not a REAL recovery.  Read as: If you "reboot recovery" you will still end up at the stock recovery.   If you mess the /system up so that it doesn't get passed line 104 in the init.rc: YOU WILL NOT ENTER RECOVERY and probably bootloop.  Be aware and know that you still may need to fastboot recover if you can't get into the recovery. ]

That being said, it is also very good.

(Link Removed as there is an “official” Bootstrap now – Click Here)

Tested successfully on XT862(Droid 3), and XT860(Motorola XT860 4G)

Features:

  • /boot and /recovery partitions are disabled while we have a locked bootloader
  • /pds is disabled for privacy reasons
  • /preinstall contains the actual recovery files so I’ve disabled that as well — no messing with /preinstall
  • Supports dual SD cards by offering a choice on most backup/restore/zip options (thanks Romracer and Atrix devs)
  • Verify option added to backup menu (thanks Romracer and Atrix devs)
  • Accessing recovery should live through a “wipe data” as all of the files are on /preinstall partition
  • Boot into recovery by using the “Boot Menu” (power + the ‘m’ key) and select “BP Tools”
  • The “Droid 3 Bootstrap” app allows for removing the recovery from your system if you want to go back to stock.
  • Supports ADB access in the recovery. [Linux only as reported currently.]

Demo Video by kshen1: http://www.youtube.com/watch?v=grL-xOPOEHo&feature=player_embedded

Known Issues:

  • The recovery currently requires a “busybox” with the “which” applet.  I’ll be removing this requirement in future versions.  But you’ll know when you don’t have it, if you get a “Installation complete.” message and the Status shows “Not installed”
  • I think the qHD launcher has an issue with 1 of the permissions of the APK.  If you use that launcher and get “Application is not installed” when clicking on the icon, try changing launchers and installing the APK, then going back to qHD. [This may also be fixed -- need confirmation.]
  • Occassionally, the checkbox for “Recovery Active” isn’t selected after clicking on the “Install Recovery” button.  If this happens, checkmark it manually.   THIS MUST BE CHECKED TO BOOT INTO RECOVERY.
  • USB Mount won’t work because we are booting “BP Tools” mode.  This deallocates the USB LUN devices in the OS.  [Possibly change the boot mode selection later to allow for this.]

There are quite a few people who contributed in some way to get this made:

  • The Atrix devs were very helpful getting this rolling: Edgan with 2nd-init, Romracer for his recovery mods and fix for the graphics issues.
  • I “borrowed” some settings from cvpcs’s bionic setup while troubleshooting some issues that cropped up later.
  • The IRC folks in #KrazyK helped test this backwards and forwards.  All the way to having to fastboot reinstall.  Thanks guys.  (Screenshots were done by TheDeathly)
  • The icon was designed by b16a2smith from RootzWiki
  • P3droid contributed some disclaimer code for the APK

Enjoy the recovery and please if you have any issues: Check the support forum on RootzWiki (coming soon) OR email me directly: hashcode0f@gmail.com.

What’s in a Word: Recovery

Posted by hashcode0f on September 13, 2011
Posted in: Android. Tagged: , , , .

One of the biggest challenges I’ve noticed while playing with a rooted phone is: not having a good recovery method.  It affects every decision you make.  Whether it’s testing a script or trying a new Framework-UI.

You always ask yourself:  Should I do this?  Do I have a way of backing out of it.

So I guess the best way to answer that would be: Yes.  If you’re using a Droid 3 and you are rooted, as of now there is a way out of most issues you might encounter and get all your stuff back.

I’m currently testing Clockwork Recovery for the Droid 3., and expect to have it in a state where it’s release ready in a day or 2.

UPDATE: The first release of the Bootstrap APK is out.  Read here.