Step by step .320-.340 update

Discussion in 'Drod2169 - X' started by mcp770, Dec 11, 2010.

  1. mcp770

    mcp770 Member

    Joined:
    Nov 21, 2010
    Messages:
    596
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Nashville
    Ratings:
    +0
    Here was my process call it overkill but I don't care...I have an updated working device and everything went like clockwork. Purposely didn't post links to rsd lite or any files. If you can't find them or don't know what I'm talking about don't do any of this. Also do yourself a favor and go ahead and put the Z4Root.apk on your SD card now as it will save you time later. Each SBF removed root for me so it will be used.

    ***BACKUP DATA OR WHATEVER AND CHARGE YOUR PHONE***

    1. Downloaded all the files and made sure I had newest rsd lite (used 4.8 I think) know all my drivers are up to par also.
    a. CHARGED BATTERY COMPLETELY

    2. rebooted into recovery to and cleared all caches and did a data wipe for good measure.

    3. Opened RSD lite and booted phone into loader (power off... hold volume down+camera+home then power)

    4. SBF the phone using the full .320 sbf VRZ_MB810_2.3.32_1FF_01.sbf....for some reason rsd never shows "pass" after the reboot but if it boots up corrected it probably did. If you are cautious and want to check anyways with rsd still open and waiting shut down and boot back into loader, rsd will immediately say "passed". You are now on 2.3.320 full sbf.

    5. rebooted normally and activated phone (not sure if everyone has to or what but I did). SKIP EVERYTHING AFTER ACTIVATION, NOT YET...SLOW DOWN. Now a note: I had installed the files posted by P3 yesterday on my .340 sbf and had issues minor and corrected with data wipes but anyways wanted to go clean for this stuff. Now after SBF back to .320 that we just did I noted my Version is 2.3.320MB810, Baseband is BP_C_01.09.07P, and Kernel is 2.6.32.9-gca645b6...not worried about boot loader because via past leak install I am 30.04 and if yours isn't it will be later. SO system is now .320, MBM is now 30.04, Kernel reverted to older version, and baseband remains unchanged for me anyway because like I said already updated it installing these files yesterday.

    6. Now for the 2.3.340 upgrade. I chose to use the 2.3.34_SYSTEM-ONLY sbf rather than P3's posted update.zip because I find RSD easy (it's still open from step 4) and I can skip re-rooting my phone and getting all the clockwork stuff downloaded and reinstalled for right now when we will just be erasing it all again. But, if that’s your deal go for it....but yes you are unrooted now. Shut her down and boot into loader (hold down volume+home+camera then power). SDK should see your phone again and load up the 2.3.34_SYSTEM-ONLY.sbf and repeat steps 1-5. Again if phone boots into the OS you passed but shut down to boot into loader for confirmation if you must. Anyways WE are now on system version 2.3.340.MB810, still baseband BP_C_01.09.07P, Kernel 2.6.32.9-gca645b6.....welcome to the .340 update! DON'T LOG IN YET! SKIP EVERYTHING AGAIN WE HAVE ANOTHER QUICK REBOOT TO GO....ALMOST THERE!!

    8. I chose this point to load all the P3droid files on the original post to my SD card minus the bootloader and 340 system updater because I'm good to go there and you should be as well after the above steps. If when you were in boot you noticed that you were still on a lower MBM version go ahead and move that one on there too......LETS ROOT!

    9. Go ahead and launch the z4root.apk we put on the sd card and permanent root the phone. When it reboots go ahead and log in this time to get the market rolling on your apps and get recovery apps up and running because next we are headed to clockwork recovery! Hours of tinkering goodness don't you think? Oh and remember you got to unplug for a minute to see the SD card and use the basic "files" app since we haven’t bothered to log the phone into Google yet, I know YOU know but someone is bound to forget. If you haven't already (I didn't) turned on install apps from unknown sources and USB debugging z4root will prompt you when you try to install so no worries.

    10. OK, so you should now be rebooted following z4root and have a nice rooted x with the superuser app present....I DO! Now log into your Google account and get the market crapping out your apps or it may be constipated after these updates so be prepared to manually get them later. Just hit the market icon and you will be prompted to log in. Now is a good time to get on wifi...I have zero patience. Honestly you may or may not see your free apps at this point for some reason but the paids ARE there and right now I only care about Droid X Recovery Bootstrap app anyway.

    11. Reboot into clockwork recovery via your app of choice.
    A. for anal retentive good measure wipes all the caches again...may not matter but definitely didn't hurt.
    b. DO WHAT P3 SAYS EXACTLY!!

    Install instructions for each of the files below.

    1) Download
    2) Restart phone with bootstrap recovery
    3) Select install update.zip and then select the zip you downloaded
    4) Restart the phone

    *** When performing the baseband update you will need to reactive using *228 ***

    12. If you b. DID WHAT P3 SAID EXACTLY!! You should now have all the updated modules and for all intents and purposes be on the same system as those no fun OTA guys as follows: Version 2.3.340 MB810, Baseband BP_C_01.09.07P, and Kernel 2.6.32.9-g55626e1

    13. **optional** reboot recovery one last time wipe caches and this time data as well. If you are confident another data wipe is pointless---->that’s it folks you are done! Go get your favorite .340 supported ROM and Theme and restore your data however you do what you do.

    NOTES: TBH may eventually have all this stuff compiled into one snazzy sbf or update.zip but for now the above is what I did to update everything without a single hiccup or reboot one. Actually wrote this out in real time as I was performing the steps myself. Seems lengthy but really only takes about 15 minutes or less of your time.

    If at any point you get boot loops from the droid eye you simply need to wipe your data/caches again and it will fix it right up. Happened to me the first time thus my optional last wipe in 13.

    I installed Rubix 1.90, the 1.90 patch for .340 and Juicemane's v4 all at the same time at the end and rebooted flawlessly but did have to activate again. oddly enough on the base updates market didn't download my apps....installed Rubix and all free and paid apps magically appeared proving once again Drod is the sh!t. Thanks to all you guys for keeping me busy figuring out my Rubix cube and making it run great!
     
  2. theidoctor

    theidoctor Member

    Joined:
    Nov 8, 2010
    Messages:
    122
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
  3. Greg_droid

    Greg_droid New Member

    Joined:
    Oct 19, 2010
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Since you are using Rubix, is there a reason to bother with the "2.3.34_SYSTEM-ONLY sbf"? I decided not to touch it after reading this: http://www.droidforums.net/forum/drod2169-x/104111-rubix-1-90-320-leak-rubix-1-90-340-a.html

    These are the steps I took this week as they became available, and my Bootloader, BaseBand & Kernel are all matching the OTA.

    DAY 1:
    1: Revert back to 2.3.15 OTA update. Fully Charge Phone

    2: Download "Froyo 2.2.1 - (Blur_2.3.320_System_2.2.1) (2.3.320 Deodexed)(Update.zip format only) (DROIDX) from TBH app, and install via Clockwork. Followed instructions in TBH app to install this.

    3: Made backup of my phone via ROM Manager.

    4: Download Rubix 1.9.0 for leak and install via clockwork, following Drod's instructions to wipe data/cache. (reboot)

    DAY 2:
    5: Download 1.9.0 Patch, and install via clockwork. (reboot)

    6: Download 2.3.340 Kernel Updater and install via clockwork (reboot)

    I never lost root, never had to hook my phone up to a PC, never experienced a boot loop, etc. Does anyone know if I'm missing something? It all seemed to go peachy.

    edit: I am not advocating anyone use this method. I only posted it to see if I was missing something.
     
    #3 Greg_droid, Dec 11, 2010
    Last edited: Dec 17, 2010
  4. mcp770

    mcp770 Member

    Joined:
    Nov 21, 2010
    Messages:
    596
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Nashville
    Ratings:
    +0
    I did everything the way I posted simply because the "theory" at this point is by doing everything I did we should be back in line for the next ota same as everyone that didn't use the leak. That said you may have all the modules correct and that's great but as I said above I did it the EXTREMELY cautious and by the numbers way things have been released by TBH and in their order of release as they are the ones working to get us back on track. Most efficient way to do it maybe not but definitely the order TBH used and as a result I too am operating flawlessly. This is also geared for those more comfortable with using instructions not the advanced users.
     
  5. Greg_droid

    Greg_droid New Member

    Joined:
    Oct 19, 2010
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Gotcha, thanks.

    This is my first time updating the phone after rooting, so I'm a little concerned if I'm missing anything.
     
    #5 Greg_droid, Dec 11, 2010
    Last edited: Dec 11, 2010
Search tags for this page
descargar update.zip para droid x mb810
,
how to fix kyocera echo boot loop
,

kyocera echo boot loop fix

,
kyocera echo boot loop reset
,
kyocera echo hacks
,

mbm 30.04 updater

,

vrz mb810 2.3.32 1ff 01.sbf download