Important Info for .621 Update!

[shawn]

its been awhile since ive messed with my x whats better for .621 the x recovery or the droid2 recovery

[Ads]

[Aptiva]

its been awhile since ive messed with my x whats better for .621 the x recovery or the droid2 recovery

As far as bootstrap? DX one won't work on GB flavors. D2 Bootstrap will work on GB. As far as updating in Rom Manager, I usually use the Droid X 2nd Init personally usually without fail.

[spex921]

I'm not a staffer, but I was curious about the new method, and wanted to see it work. And it is easy and it does work!

On Monday I took the .iso and used unetbootin to create a usb boot drive. I sbf'd with RSD Lite, activated, then booted my computer with my usb stick and followed the instructions. It is pretty straight forward and it worked perfectly. I loaded Droid2Recovery (to answer the question about which recovery), and flashed the .621 version of VXL 1.0 and I'm not looking back...

[Aptiva]

I just used it myself and it went flawlessly. Exactly as it is supposed to work. I'm going to do a few more runs on it to see if I can narrow down the CWM issues people are having. I managed to get D2 Bootstrap to install CWM and updated it through RM to the DX Recovery (not 2nd init) and CWM booted fine. I did do the recommended NFS nuke with Rom Toolbox's built in Root Browser. Doing another SBF as I type this so I can try it without deleting NFS from preinstall to see if it truly is an issue, but it really was just as fast as the normal 1kds SBF method with rooting scripts built in. It does flash a new preinstall folder when you use this root method, but after you root if you have issues with CWM, just use a root browser to nuke the NFS apk in /preinstall and CWM does in fact work. I haven't flashed any roms yet, but I just set off in testing this, so when I flash back to CM9, I will post more findings.

[Goose306]

I just used it myself and it went flawlessly. Exactly as it is supposed to work. I'm going to do a few more runs on it to see if I can narrow down the CWM issues people are having. I managed to get D2 Bootstrap to install CWM and updated it through RM to the DX Recovery (not 2nd init) and CWM booted fine. I did do the recommended NFS nuke with Rom Toolbox's built in Root Browser. Doing another SBF as I type this so I can try it without deleting NFS from preinstall to see if it truly is an issue, but it really was just as fast as the normal 1kds SBF method with rooting scripts built in. It does flash a new preinstall folder when you use this root method, but after you root if you have issues with CWM, just use a root browser to nuke the NFS apk in /preinstall and CWM does in fact work. I haven't flashed any roms yet, but I just set off in testing this, so when I flash back to CM9, I will post more findings.

So is it faster then than the 1KDS SBF? I know the download is obviously smaller, I would assume faster as well as its flashing less CG (code groups)?

I would try seeing if you can go from a bone-fresh .621 base; flash that SBF/root package, install D2 Bootstrap, and then update via CWM to Droid X (2nd-init) that would be the most common route and path of least resistance. (Without nuking NFS if possible)

Oh, and thanks for testing as well!

[Aptiva]

That's what I'm doing right now as a matter of fact... Yes it's faster, but less automation. No biggie imo since it's so far easier than the MX method.


EDIT:
CWM booted no problems without nuking nfs from preinstall. Using both d2 bootstrap and rm to boot to recovery. I used dx 2nd init cwm.

EDIT 2:
I did this 3 different ways as far as mediums go. I used the standard burn to CD method, USB thumb drive(more SD Card/Reader but process and function is the same), and using VMWare Player in Windows. All 3 ways went flawlessly. Started each time with a fresh SBF to .621, rooted, and flashed CWM via d2 bootstrap and rom manager. Hasn't failed once. Haven't stripped NFS out once since the first time. I completed the process 6 times total for testing. Will make the video this afternoon if I find time.

[shawn]

I was looking around the interwebz for more info on my X and researching whether I should finally take the .621 and I found this on Rootz... Apparently a root method similar to one being used on the D2, D2G, and R2D2 is also working for the DX and DX2. Luckily it simplifies the process of rooting the .621 as you no longer have to do the Milestone X sbf. Worth taking a look at if you're on the .621

[Root] Droid X root method for 2.3.4/ 4.5.621 (does not require Milestone SBF) - Droid X - RootzWiki

Just tried this method works great no issues making and restoring backups or flashing zips in recovery


Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2

[Aptiva]

So I never did come across what the cause of the other people's problems with CWM. I've done this 10 times over the last 2 days without any issues.

I did flash CM9 as well as my usual hijacked boot menu, gapps, and my own custom built zip for ringtones and it went without a hitch. I only have the 1 DX atm (hopefully will have a 2nd not long from now) so if it's a phone to phone issue, I haven't come across it with my current one.



Side note:
CM9 is much more responsive and works 100x better on the .621 kernel in my experience so far, but that doesn't mean you should just take the OTA if you haven't. Make sure to do the research before you do it and make a well informed decision like I did. I was on .605 until this root method was found and honestly I think it was the only thing that was truly stopping me because I'm not a fan of flashing software for other phones on one they're not designed for, not that the Milestone X SBF method wasn't tried and true.

[sd_shadow]

I've posted the new root method here on this site, with detailed instructions
[How To] Root 4.5.621 with magic md5 (does not require Milestone SBF)

[Goose306]

I've posted the new root method here on this site, with detailed instructions
[How To] Root 4.5.621 with magic md5 (does not require Milestone SBF)

Thanks bud. I've been meaning to integrate that into the OP here but was waiting on a DX tester then when we got one its been about a week so haven't had much time. I'll see about pushing that update through

Sent from my jellybeaned AOKP GSIII