Root Read before taking .621 Soak Test

Easy to retain root. Run ota rootkeeper before to back up root and then again after to restore root.

Worked perfectly for me.

I had this problem on Saturday and almost gave up. Couldn't get it to SBF. I found that it would only take if I restarted while pressing power, down volume and camera buttons.

sounds like the same sequence for gb

lexluthor said:

Easy to retain root. Run ota rootkeeper before to back up root and then again after to restore root.

Worked perfectly for me.

Click to expand...

I received the notice of the 621 update last night. I had already installed ota rootkeeper so I backed up with titanium. I protected root and then did the Temp un-root. I thought I was all ready to accept the update but it failed to install after the download. Do I need to do anything more?

bhavlo said:

I received the notice of the 621 update last night. I had already installed ota rootkeeper so I backed up with titanium. I protected root and then did the Temp un-root. I thought I was all ready to accept the update but it failed to install after the download. Do I need to do anything more?

Click to expand...

No need to have temp unrooted. Do you have any frozen/renamed apps? Those need to be restored before you can update.

lexluthor said:

No need to have temp unrooted. Do you have any frozen/renamed apps? Those need to be restored before you can update.

Click to expand...

Thanks, I did have a couple apps frozen but after the thaw I tried the update again and it still failed. Any other ideas?

You gotta love Moto and VZW. not only do they not come through with their promise of an unloacked bootloader, They find a way to lock it down even further. Jackwaggons.

cougar214 said:

You gotta love Moto and VZW. not only do they not come through with their promise of an unloacked bootloader, They find a way to lock it down even further. Jackwaggons.

Click to expand...

im curious...can you show me where Motorola or VZW ever specifically said that the DroidX would have its bootloader unlocked?

bhavlo said:

Thanks, I did have a couple apps frozen but after the thaw I tried the update again and it still failed. Any other ideas?

Click to expand...

I am working through the same issue right now on my DX 605->621, mine was getting ! about 1/3 through update. I also unfroze apps but I just remembered that I had manually blocked updates and messed with databases as well. Here are the list of things that I did that I missed:

/system/app:
vzw_vnav_DROIDX_rel_PROD_signed.apk
BlurUpdater_VZW.apk
amazonmp3_1.8.32_signed_zipligned.apk

/data/app:
com.motorola.blockbuster-1.apk

/data/data/com.motorola.android.datamanager/databases/DataManager.db
/data/data/com.motorola.blur.providers.contacts/databases/contacts2.db
/data/emt/emt.bak

Once I put all of those things back the update succeeded. I had run rootkeeper before the update and I was able to get root back after update.

speedyhawk said:

I am working through the same issue right now on my DX 605->621, mine was getting ! about 1/3 through update. I also unfroze apps but I just remembered that I had manually blocked updates and messed with databases as well. Here are the list of things that I did that I missed:

/system/app:
vzw_vnav_DROIDX_rel_PROD_signed.apk
BlurUpdater_VZW.apk
amazonmp3_1.8.32_signed_zipligned.apk

/data/app:
com.motorola.blockbuster-1.apk

/data/data/com.motorola.android.datamanager/databases/DataManager.db
/data/data/com.motorola.blur.providers.contacts/databases/contacts2.db
/data/emt/emt.bak

Once I put all of those things back the update succeeded. I had run rootkeeper before the update and I was able to get root back after update.

Click to expand...

Im sorry I see your list but don't understand what you mean or what you actually did to fix the problem. If you could explain in more detail I would appreciate it.

Well, it sounds like my rom flashing days may be over.. although I am really a novice. To be honest, I feel forced into it by owning a really cool phone, that just got worse and worse with every ota update. When I first got my phone, I believe it was on froyo... not really even sure. The mp3 music player had nice graphical images while playing music (none after update), it ran smoothly, don't really remember the word "pull out the battery", the camera stayed set on the pixel size of choice... just seemed fine. Then, the updates to GB. Camera started having issues, not holding pixel setting, would corrupt video at priceless irreplacible moments like my step dads Marine burial... UUUGGGHHH!! nothing like taking your 40 dollar Otter box off in the middle of something like that to just manage to salvage any remaining footage. I will never forget that... and other countless times it failed me. Going to answer a smple text with "ok"... but never made it that far because the stupid thing would re boot... I about chucked it out the window a few times, but was in fear of hitting a pedestrian or basically because I dont like to litter... lol Ok, now that thats off my chest... I taught my self to SBF... and flash roms due to shear desperation. So far, my feeling on this new update, are pretty good. I took it out and did a little camera work... holds the setting, takes pics at 8 mp just about as fast as an Iphone... I mean fast. I was hitting the button on the screen before the pic was even off the screen I had just taken. I have been using and enjoying very much Launcher Pro. It allows for landscape view in all desk top screens... something I never understood was not an option.... unless it was in a cradle. I made my own with a kitchen magnet, some tape velcro, and a 25 dollar gps window mount suction cup holder. It "tricks" the droid into thinking its in it 50 dollar cradle, which will not accompany my 40 dollar otter box... another huge design flaw. All in all, I still want the option to flash roms, and SBF, so I hope the geniuses figure it out, but in the mean time, I do like this update, and that means a lot coming from a guy who really uses just about every feature of this phone, every day, for work and play. Thanks to those responsible and smart enough to have kept me sane with other workable roms in the meantime. Cheers..

As of today, I can say the battery and memory managment have improved significantly. It honestly feels like a new phone. I actually SBF'd back to .605 before I took this update. It took the one before it, the immediatley this one came on. If I had read all this prior I probably would not have taken the step, because I like flashing the roms, but I must admit, it is still running very stable.

Metfanant said:

im curious...can you show me where Motorola or VZW ever specifically said that the DroidX would have its bootloader unlocked?

Click to expand...

I wasn't refering to nessesarily the DX. I was refering to Moto's claim of giving in and unlocking device bootloaders. Ya had to know we we gonna get ripped even further in the end.....lol.

speedyhawk said:

I am working through the same issue right now on my DX 605->621, mine was getting ! about 1/3 through update. I also unfroze apps but I just remembered that I had manually blocked updates and messed with databases as well. Here are the list of things that I did that I missed:

/system/app:
vzw_vnav_DROIDX_rel_PROD_signed.apk
BlurUpdater_VZW.apk
amazonmp3_1.8.32_signed_zipligned.apk

/data/app:
com.motorola.blockbuster-1.apk

/data/data/com.motorola.android.datamanager/databases/DataManager.db
/data/data/com.motorola.blur.providers.contacts/databases/contacts2.db
/data/emt/emt.bak

Once I put all of those things back the update succeeded. I had run rootkeeper before the update and I was able to get root back after update.

Click to expand...

I finally got the 621 update to take so I thought I would let others know what I had to do. No matter what I tried I couldn't get the OTA of .621 to work, I thawed apps and even tried to restore a nandroid backup but still the OTA failed.

I ended up SBF'ing .602, which also failed a couple times itself so I downloaded the SBF file and used a different USB cable and then it passed. Then I rooted .602, accepted the OTA .605, installed OTA RootKeeper, protected root and finally accepted .621 OTA. After it was all completed I restored root and everything seems to be ok.

There is now a .621 SBF, may want to update the OP, original leak was on XDA if you wanted to track it there or its also been posted a few places over @Rootz.

It is also no longer a Soak Test.

ylexot said:

It is also no longer a Soak Test.

Click to expand...

LOL I question if it was ever a soak test, the very first day it was released as a soak people were reporting on the Moto Owner's Forums of receiving the OTA even though they were not part of the soak and did not receive the email. And the "soak" lasted a total of 2 days before Matt @ the Moto Owner's Forum acknowledged that it was regional and rolling out fully nationwide and was available on a pull as well...

bhavlo said:

I finally got the 621 update to take so I thought I would let others know what I had to do. No matter what I tried I couldn't get the OTA of .621 to work, I thawed apps and even tried to restore a nandroid backup but still the OTA failed.

I ended up SBF'ing .602, which also failed a couple times itself so I downloaded the SBF file and used a different USB cable and then it passed. Then I rooted .602, accepted the OTA .605, installed OTA RootKeeper, protected root and finally accepted .621 OTA. After it was all completed I restored root and everything seems to be ok.

Click to expand...

Same thing worked for me. On .621 rooted, just waiting on some ROMs.

Well, I have givin it a few more days. So far, I have had 2 random reboots. The memory slowly creeps up like before, just not as bad. The camera works splendid, as well as other things, but the bloat is still there. It runs nice, but I am very disapointed in myself for jumping the gun on the new update. I am currrently shopping for another x that may not be updated yet to the .621 so I may still be in the rom club.. lol The random re boots are what really tick me off, and it sure is funny that they boasted to have fixed this issue, and it's still evident they did'nt. All they have really done is screw everyone once again.

cougar214 said:

I wasn't refering to nessesarily the DX. I was refering to Moto's claim of giving in and unlocking device bootloaders. Ya had to know we we gonna get ripped even further in the end.....lol.

Click to expand...

exactly...Moto has NEVER said that the DX was going to have its bootloader...or even hinted at it...so the reason anyone expected it to happen boggles my mind...

When I bought the MOTO Droid X I did my due diligence to make sure that I was getting an open source system that I could make changes to. This was an expensive phone initially 600$ without contract. If I wanted an IPhone I would have bought one. Please note that .621 update does not Brick phones. You have to download the .621 SBF from XDA and SBF (due to the changes they've made to the bootloader) back to it in order to get your phone working again. I am due for an upgrade soon and plan to go with the I Phone instead. If I cannot make the changes I want to make to MY PHONE THAT I PAID FOR than I'd rather have a better phone. See ya MOTO!!!