Source:: I've decided to make a separate thread for all of my releases on account of also deciding to release some modded .621 ROM's and want a single point of support / availability. Feel free to use my work however you want, just send some credit my way in your notes Also, please do not link DIRECTLY to files, instead link to this post as I will be updating / fixing anything that may not be 100% and the links WILL change if / when I do this. I've tested these updates as much as possible, but you never know Thank you for your cooperation.

I created the ROM's because I was running TBH .605 stock deodexed modded and found myself without options to go to .621 and keep all the awesomeness that made my phone so much more than it was on regular stock .605. The update I really focused on to replace TBH's .605 update on my phone was easily the most complicated, so it seemed fairly silly to not release the two stepping stones that are the first two ROM's. Especially since I know a lot of people like to run these two versions for various reasons anyhow.

I also created a small collection of updates along the way while I was messing with getting my .621 modded update polished and shiny, they have been released previously in various threads but not all in one place and none in the following form...

ALL updates have new / updated comments in the updater-script and ALL updates have been signed, which means you can (and should) turn ON (it's off by default) signature verification in ClockworkMod Recovery BEFORE you install any of these to rule out download / SD card issues.

ALL ROM's are FULL updates to 4.5.621. They've been made this way to try and simplify the previously convoluted (but still annoying) path you are forced to take if you break your phone and have to SBF. This has a few benefits as well as down sides:

2. They WILL also flash ALL non-filesystem images (just like the SBF) if you are currently on a Froyo kernel, they will flash everything BUT the radio if you are not.

3. Flashing ANY of these ROM's will LOCK you into running either the 4.5.604 Milestone X (2.6.32.9-geadffa3mcbk83@il93lnxdroid08 #1) or the arguably better 4.5.621 Droid X (2.6.32.9-g1282440mcbk83@il93lnxdroid08 #1) kernels. SBF / update.zip downgrading to previous versions has been DISABLED by Motorola's use of new signatures.

4. You CAN flash ANY of these ROM's directly from a fresh ezSBF with 1KDStaz_MX_4.5.604.iso (Milestone X 4.5.604 Gingerbread) and they will take you COMPLETELY to fresh rooted 4.5.621 (kernel, stock recovery, etc.) with the exception of the radio, which only needs to be flashed ONCE anyhow. See radio update notes below for more info.

5.You CAN flash ANY of these ROM's directly from ANY already rooted ROM, stock or otherwise. If coming from a non-stock ROM, a factory reset will almost certainly be required.

6. EVERYTHING was pulled from the stock SBF file and NOT copied from someone's CWM backup, so these are CLEAN updates with NO leftover files from OTA updates, etc.

The donate widget link is a widget that shows all donations in real time so everyone can see what has been donated so far. There are two people who donated before I made the widget that will not appear on it, so I am giving them credit here:

Special thanks to:schneid for $10mopartonyg for $5

All this flashing / restoring / SBF'ing and I'm sure the age of my Droid X (2+ years and counting) has finished off my poor battery . I could get about 20 minutes of screen on use out of a full charge. I have had to order a new one so PLEASE donate below (old donate widget) if my work has made your phone / life better

Update: After many months, it seems I have reached my $35 goal to cover my extended battery, yay! Lol. I am leaving the old donate widget link up for a history of contributors, I couldn't thank you enough. And, I am creating a general donate link for future contributions.

As almost any open source / free software dev will tell you, I have never worked harder or longer hours for less money (or even for free) in my life, but I wouldn't trade a single second of it for the world. I've learned an incredible amount about Android and Linux, I've gotten to know some incredible people, and above all I've created something incredible by doing something better than anyone else had up to this point. We don't do this for the money, we do this because we love it.

That being said, any amount is always much appreciated and will always be put to good use.

*** If you are updating any Modded ROM release OLDER than 1.5, you must first uninstall updates for 3 removed system applications (Titanium Backup, ROM Manager, BusyBox Installer). After installing the new update you can reinstall these applications from the market and restore their settings from Titanium Backup (TB will auto-restore its settings from your SD card).

*** Notes ***- Restores removed system apps. Original Google apps will be restored to /system/app/Gapps.orig/ to avoid overwriting newer versions already in place.

You can either flash this update from ClockworkMod Recovery to restore absolutely everything removed from the system partition (essentially bringing you back to a stock rooted deodexed state with some tweaks left over). Or (my preference if you want your phone to keep running fast) individually extract files to their original locations on a per app basis using Root Explorer or a similar file manager. For example if you want to add back in only Blur Flickr support, just extract those files from the .zip to system/app (do NOT forget to reset permissions / owner / group for ALL manually restored files).

This installer is SAFE to be installed over top of or upgrade an already working BootMenu installation. Use this installer to get new features that have been added since the last Modded ROM release. Also use this installer in the event that you need to restore any BootMenu components to their defaults because you or another application has altered them in any way.

OTHERWISE:

This installer assumes you already have Droid 2 Bootstrap installed, that you have used it to install recovery mode, and that you have used it to boot into recovery mode to install this update. If you have not done all 3 of these things, this installer probably will not work correctly as it relies on files that Droid 2 Bootstrap puts in place. If you are coming from another ROM to one of the 4.5.621 stock ROM's, you MUST leave recovery, install Droid 2 Bootstrap, then use it to install this update.

You can use this installer for ANY Droid X 4.5.621 ROM (stock / deodexed / modded / whatever). It will REMOVE Droid 2 Bootstrap and the app's associated data. Do NOT re-install Droid 2 Boostrap unless you want to break Bootmenu and possibly your phone.

TO ENTER BOOTMENU / RECOVERY FROM NOW ON: After powering on your phone, simply press the VOL - (vol down) key when you see the notification light turn blue while the red "M" is on the screen.

*** Notes ***- All scripts do exactly what the file name says.- They were created to give people an easy way to do these things without having modifying the Android shutdown menu java code.

New: Added "BootMenu on Reboot.sh" script which sets the flag to enter BootMenu next boot, but does not reboot the device. Very useful in situations where you need a full device power-off & battery pull, like Modded update installs or EXT3 filesystem fix utility runs, but don't particularly enjoy having to sit on pins and needles waiting to catch that damn blue light

** To create homescreen shortcuts to these scripts simply download GScript Lite from the market, save these scripts to your sdcard (make sure you keep the gscript folder name), import them into GScript Lite and add them to your homescreen as a GScript Lite shortcut.

* Included some very nice icons to use for these shortcuts from here and here.

Make sure you do a full power off & battery pull before running this utility. Doing so will force a system date / time reset, allowing the e2fsck utility to properly check & repair unmounted partitions.

What's New: Completely overhauled check & repair script. Previsouly I was running this utility up to 3 times in a row to completely fix all EXT3 errors on all partitions, now the utility simply runs 3 check & repair passes. This is the exact same filesystem check script that is executed at the beginning and end of every Modded ROM installer since 1.7.

I made this utility because I was getting bad (MD5 mismatch) CWMR backups of my /data partition and was trying to determine the cause by process of elimination. After the fact I realized this utility could be very useful in many different situations.

2. If you are NOT on .604/.621 you can revert to any Froyo based ROM either by SBF or with an update.zip that also flashes the Froyo kernel (You CANNOT use this method if you are already running either 4.5.604 OR 4.5.621).

*** Notes ***- This update flashes all images (excluding the radio) ONLY from 4.5.621- You must SBF stock .621 first if you want the 15P radio as it cannot be flashed on the Gingerbread kernel

I made this update again to cover all the bases. I have been getting odd CWMR nandroid MD5's and thought maybe some images weren't being flashed perfectly by Linux sbf_flash. This gives you a way to reflash them all directly from recovery mode (instead of ONLY flashing the one's that changed between the Milestone X SBF and Droid X 4.5.621).

*** Notes ***- This update ONLY flashes images that are not exactly the same as the images flashed by the Milestone X 4.5.604 ezSBF by 1KDS- You must SBF stock .621 first if you want the 15P radio as it cannot be flashed on the Gingerbread kernel

OP
ky41083

Can't much blame you at this point. When my Modded update passes my testing you may have a reason to update Also, running your .605 backup on the new kernel is always an option if you want to CWM restore your .605 after trying .621. Honestly I'm still using .605 that exact same way as my daily driver while I work out the last few bugs in my .621 Modded.

OP
ky41083

hey ky would love to test the modded version if u need another guinea pig. thanks for your 621 work

For sure. As soon as I figure out this last little boot-loop bug (I've found a way around it, just trying to decide how to handle it or find a better way around it.) I'd like to run it as beta for about a week on my phone before I call it stable, but for that week it definitely wouldn't hurt to have a few other people testing it as well. I'll get at you as soon as I decide which method I want to use for avoiding the boot-loop

mopartonyg

For sure. As soon as I figure out this last little boot-loop bug (I've found a way around it, just trying to decide how to handle it or find a better way around it.) I'd like to run it as beta for about a week on my phone before I call it stable, but for that week it definitely wouldn't hurt to have a few other people testing it as well. I'll get at you as soon as I decide which method I want to use for avoiding the boot-loop

greedj

Could I Flash the deodexed .621 over me being on m5 of AOKP? I am on .605.

Sent from my DROIDX using Tapatalk 2

I have a similar question.Is 621_Stock_Rooted_kY-Signed.zip an AIO?I assume it is an AIO because of the following statement:"2. They WILL also flash ALL non-filesystem images (just like the SBF) if you are currently on a Froyo kernel, they will flash everything BUT the radio if you are not."I just want to verify and be extra clear. :-)

Goose306

Could I Flash the deodexed .621 over me being on m5 of AOKP? I am on .605.

Sent from my DROIDX using Tapatalk 2

I have a similar question.Is 621_Stock_Rooted_kY-Signed.zip an AIO?I assume it is an AIO because of the following statement:"2. They WILL also flash ALL non-filesystem images (just like the SBF) if you are currently on a Froyo kernel, they will flash everything BUT the radio if you are not."I just want to verify and be extra clear. :-)

I am running 4.5.605 rooted with the 15p Radio.

And I want to add, GREAT JOB!!!!!

Yeah its an AIO. I just downloaded and checked the archive and it has the kernel, cdt, recoveries, etc. included. So if you flash this on non - .621 you will then be ON .621 (no reversion). You should be able to flash across with no problems, but keep in mind the repercussions of doing so...