The DROID would not be able to use the radio of the myTouch since that is a GSM device and uses different frequencies than the CDMA DROID would. But the overall idea is correct in that you can manually update to a different radio when its released by Motorola.
We don't even know how the Droid is really setup yet. There's a good bet that it's similar, but we're still learning about it. There's not much point in looking at all the stuff for the G1/Magic. It's all going to change.
Just relax and let people play. The G1 has been out for quite some time. It has been analyzed and understood. We've only had our devices for a week.
Early indications are that bricking this thing will be difficult (by playing with the software). There are many options to boot from. But the first step is getting ourselves to the point of being able to reverse any changes made (such as an nandroid backup on the G1). If you screw something up, you're able to fall back on a backup.
In theory, it shouldn't be possible to brick this phone because of the boot features available in the OMAP3 processor. These chips are designed to be 'unbrickable' and easily recoverable without the use of advanced tools like a JTAG.
A better analogy comparing the phone to a PC is the bootloader on the phone is just like the bootloader on your computer - it's a piece of software that sits at the beginning of a disk (MBR) and is executed by the BIOS to handle loading the OS. If you manage to destroy the MBR on your PC's hard disk and the BIOS can no longer find the bootloader, you simply pop in a CD or flash drive and set the BIOS to boot from that instead. BAM problem solved.
The OMAP has a BIOS of sorts called a bootrom and you cannot flash this as it is a hardcoded part of the chip. When the chip powers up, the bootrom checks the state of a number of pins to determine where it should boot from - NAND, UART, USB, or SD. When Motorola designed the PCB in the phone, they configured the default state of these pins to boot from NAND. The usual design practice though is to make these pins available to allow the boot order to be changed in case the default boot location gets botched up.
The question now is are these pins available and if so, where are they? Yevar, over at alldroid.org has offered to reverse engineer his phone if we can donate enough money to cover the cost of the phone. This is one of the many important questions that he can answer by doing so.
Last edited by DougDroid; 11-18-2009 at 11:06 AM. Reason: Forum Promotion
I have no idea why by phone is a paper weight. I did everything according to what I thought was correct and when I booted it, it would load the Motorola Logo and freeze. I have loaded the recovery thing, reinstalled, and every other option on the menu and it still freezes on the logo screen.
So, beware, it is possible to ruin your phone.
PM me if you need more help. I am by no means an expert but I see you having issues in a few threads and I want to help.
Also - somebody mentioned "installing a rom" is where most bricking happens. Probably true for other phones. So far, the biggest cause for near-bricking seems to be people getting root and then just jumping right in to modify files without first installing SPRecovery. A ROM is typically tested and packaged and won't cause major problems. Also, they tend to REQUIRE that the recovery console already be installed. Some (sholes) even performs an automatic system backup right before installing to make SURE you don't brick. Of course, their installer app has CAUSED a number of unbootable phones in the last week, but I digress...
Last edited by Se7enLC; 02-08-2010 at 12:28 PM.
Cool CM Tricks
custom_backup_list.txt - make a list of files in /system that will survive a nightly install (ringtones, notifications, system apps, wallpapers, whatever)
in Terminal Emulator, set this as your shell command: "/system/xbin/su -c /system/xbin/bash". You get all the features of bash, root access, and you can still use the initial command field for whatever you want (default is adding /data/local/bin to your path)