Database Users

Help!!! Problem Updating to 2.340

I am having problem updating to 2.340.
I just got a replacement DX from Verizon few days ago. As soon as I received it, I tried to do an update but the system said that I was up to date even though my software showed 2.315 so I decided to mod my DX right away since most people did not have problem updating with rooted DX.
Initially, I rooted my phone with Z4ROOT, reinstalled all the apps using Titanium Backup which i had on previous phone since I all the backups on my
SD card than I back up the stock ROM with Rom Manager. After that, I installed Bazinga2.1 Rom. Installed my apps again using titanium back up and back it up again using ROM Manager. After this, I installed BigDX blue theme. Couple a days ago, I got a notification that I have an update from Verizon which was 2.34 so I went back to recovery, restored back the Stock, using Z4Root, unrooted and download the 2.34 update and tried to install but the update failed. So I did a factory reset and put every thing back to stock and tried to update again and it still fails.
Once the update is down loaded, I try to install and its turns off the phone, than it shows a box with android next to it and it shows triangle with Exclamation and just reboots. Than it goes to clockwork mod recovery.
Why does my phone go to clockwork recovery even though I am UNROOTED?
Any help or input will be greatly appreciate it.
Thanks

johann718 said:
I am having problem updating to 2.340.
I just got a replacement DX from Verizon few days ago. As soon as I received it, I tried to do an update but the system said that I was up to date even though my software showed 2.315 so I decided to mod my DX right away since most people did not have problem updating with rooted DX.
Initially, I rooted my phone with Z4ROOT, reinstalled all the apps using Titanium Backup which i had on previous phone since I all the backups on my
SD card than I back up the stock ROM with Rom Manager. After that, I installed Bazinga2.1 Rom. Installed my apps again using titanium back up and back it up again using ROM Manager. After this, I installed BigDX blue theme. Couple a days ago, I got a notification that I have an update from Verizon which was 2.34 so I went back to recovery, restored back the Stock, using Z4Root, unrooted and download the 2.34 update and tried to install but the update failed. So I did a factory reset and put every thing back to stock and tried to update again and it still fails.
Once the update is down loaded, I try to install and its turns off the phone, than it shows a box with android next to it and it shows triangle with Exclamation and just reboots. Than it goes to clockwork mod recovery.
Why does my phone go to clockwork recovery even though I am UNROOTED?
Any help or input will be greatly appreciate it.
Thanks
Click to expand...
Click to collapse
Root and the bootstrapper are separate entities. Removing root, and removing the boostrapper manually (by renaming files in the system) will not fix your issue either.
The reason I know this is because I went through a number of ways to try to get the OTA, but could not.
I would suggest you hit MDW and get all of the latest files for the update, and do it that way.
You'll sbf, flash the leak for .320, then sbf .320, then flash the system for .340, then update the kernel, and radio afterwards. After that, you'll be back on the normal track.
It's a lot of steps, I guess, but it really doesn't take long.
Go grab the files ASAP, in case they get pulled, and follow all of the instructions carefully.

Whats MDW and why am I having this problem when everyone else is not. also, I removed Boostraper and it still go into recoverymod? I am just going to SBF reflash to 2.315 and see if it will work.
Here we go again!!!

Lots of people had that issue.
Mdw is mydroidworld.com
Sbf all you like. I stand behind the advice I gave.
Also, if you had actually removed the bootstrap correctly, you couldn't possibly still end up in clockwork.
Either way, in about the time it took you to post, you could have used the steps I suggested and have been done.
Sent from my DROIDX using Tapatalk

I'm in a bit of a hurry so I haven't read the whole thread thoroughly, but if you're just trying to get it to stop booting into CWM, go to terminal emulator
Run "su"
Run "mount -o remount,rw /dev/block/mmcblk1p21 /system"
Run "cp /system/bin/logwrapper.bin /system/bin/logwrapper"
Reboot

bladebarrier said:
Lots of people had that issue.
Mdw is mydroidworld.com
Sbf all you like. I stand behind the advice I gave.
Also, if you had actually removed the bootstrap correctly, you couldn't possibly still end up in clockwork.
Either way, in about the time it took you to post, you could have used the steps I suggested and have been done.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice but I SBF my phone back to 2.315, than tried to do update again and it worked.

Rom: Issue with tranquility and titanium backup

Ok so I have an issue where i was flashing the ROM Tranquility for my droid x and it was difficult to get it running but now it seems to be going ok. But now I'm trying to restore all my apps using Titanium and for some reason as soon as i try to restore even one, the phone quick reboots. PLEASE HELP, becuz i have a TON of apps that i just dont really wanna go reinstall every single one

I had the same issue with tranquility...
Not sure what went wrong.
I was also unable to install apps from the market.
Buuut...I personally wasn't all that thrilled with it anyway...and went back to Apex rather than bothering with it.
I hope you find a fix though!
EDIT:
I found our problem...with a quick search.
I haven't tried yet (I prefer apex anyway) but the install is this...
SBF 2.3.320
Then SBF 2.3.340.
The .340 isn't a full sbf and merely updates the files that are intended to be updated by...the update.
We were essentially installing over mock stock.
Then, I heard you must wipe your phone 2-4 times. Not just once. As an added precaution.

[Q] Getting from .340 to latest GB build

Okay, I need some help. I'm not unfamiliar with rooting/flashing/adb. I'm running CM7 Nightlies on my Droid Incredible. However, I am unfamiliar with flashing the DroidX. My wife wants some Gingerbread love, so I am trying to help.
She's rooted, running everything else stock 2.3.340. Baseband BP_C_01.09.07P
I have d/l'd the two files as referenced from MyDroidWorld by p3droid. Installed the Droid 2 Bootstrap. I boot into recovery and when I attempt to install the first file, I get an Status 7 error, specifically:
assert failed: apply_patch_check("system/app/VoiceSearch.apk"....
I've used Titanium BU to uninstall VoiceSearch and reinstall it from the market. I'm not sure what else to do. She REALLY doesn't want to have to reinstall everything if she can help it.
Any assistance would be greatly appreciated. Thanks!

I could be way off here, but it sounds like one of two things: either the Voice Search app in the zip is corrupted (did you check the md5 sums?), or it's expecting Voice Search to be a system app (and if you re-installed Voice Search from the market, it's probably installed as a user app instead).
Check the md5 sums, if that's not the issue, try using Titanium Backup to convert it into a system app.
If nothing else, you could back up everything with TB, sbf back to .340 stock, then take the OTA to .602, re-root using the Droid 3 easy root script, and then restore all data and user apps with TB.

[Q] R2 GB update on R2 running D2 Froyo?

So this is a total longshot...but I have an R2 that's running stock D2 Froyo (because I'm an idiot and lost R2 Froyo), which has been fine, but now that the R2 GB has been released I'd like to get back where I need to be.
I know there's still no R2 SBF, but is there any other way to get my phone to recognize the R2 update?
I assume the OTA is based on the build.prop, and not the MEID or I'd be able to pull it already. Can I modify my build.prop to match the R2's, and then Blur will pull the correct OTA? Any other ideas? Thanks.....

If you search you'll find a nandroid for the r2. I used that to recover my wife's and then push the update. I'm at work or I would post the link
Sent from my DROID2 GLOBAL using Tapatalk

abalsor said:
If you search you'll find a nandroid for the r2. I used that to recover my wife's and then push the update. I'm at work or I would post the link
Sent from my DROID2 GLOBAL using Tapatalk
Click to expand...
Click to collapse
I guess I'm useless, lol....I've been searching for two hours and can't find an R2 nandroid? Do you remember where it was?

I'm in a similar boat. I rooted my R2-D2 for a while and then un-rooted it. Now I can not apply OTA Gingerbread update. I'm trying to find the R2-D2 SBF as well, but it seems that the majority of the links that I find are no longer up. As well as IIRC, in order to apply the OTA update from VZW, the entire phone has to be running stock, including the boot loader. This means no Nandroid or CWM.

I too have had no luck in finding a R2D2 Rom/SBF download that works.
I was running the leaked GB on my R2 since May and now cant get official. I SBF'd to stock D2 2.2 and flashed a backup i made with clockwork but i guess something isnt right because it only gets about 25% of unpacking the update before it stops and says it failed. I download some bloatware and put it back in the system folder and then unrooted with z4root.
I guess ill just sit here in the boat with you guys.

Is z4root the one click root method? If so, that's what I used and used only. I never flashed a different ROM on my R2-D2. My guess is is that the one-click root modified some other files that are interfering with the OTA update. Just my $0.02.
I think to successfully get the OTA update from VZW, RSDLite and an SBF will be needed. IIRC, for an OTA update to work from VZW, the boot loader can not be modified (no CWM or Nandroid).

Well my bootloader is now on 2.37 not 2.35 because i SBF'd to stock 2.2. if this is true that i cant update than this really bites.

Stock 2.2 for R2-D2 or D2? Two different builds there. R2-D2 GB build will not load if you're running a D2 ROM on your R2-D2. Clear as mud?

I was running stock R2D2 2.2, i SBF'd to stock D2 2.2, i installed leaked D2 2.3, now i SBF'd back to Stock D2 2.2, flashed R2D2 2.2 backup.

chasehammer said:
I was running stock R2D2 2.2, i SBF'd to stock D2 2.2, i installed leaked D2 2.3, now i SBF'd back to Stock D2 2.2, flashed R2D2 2.2 backup.
Click to expand...
Click to collapse
That's exactly what I did....except somewhere along the way I lost my R2 backup. I've been looking all day, but I can't find a stock R2 nandroid that abalsor mentioned anywhere.
My original thought was trying to figure out how to trick Blur into pulling the R2 update, even though I'm running the D2 software. I know they're different releases, but it's the only other option I can think of. It seems like updates should be based on your MEID, but obviously they're not. Do you think it's just the bootloader? I wonder if there's a bootloader SBF out there I could flash then?
I guess I'm just grasping at straws, I even tried calling Motorola to see if they'd push the R2 GB update manually, (if they even can?), but they told me there is no R2 update....

ive pretty much given up at this point. Only option is what you said go back to stock Droid 2 and pull the update but would lose R2D2 stuff. I guess better than nothing. Every forums ive asked no one responds or make stupid comments like "someone actually has a R2D2?"
and dont ask Verizon or Motorola, you wont get anywhere.

Do you think VZW has an SBF?
Hypothetically speaking, if my phone was to be stuck in a boot loop, and I took it to a VZW store, I wonder if they could/would re-flash it?
Hypothetically, of course......

sorry it took a while to get back to you. I've been trying to get my wifes r2d2 to take the GB update. here is the link R2D2 nandroid backup..
Do a standard nandroi recovery with the file. You'll have to start the phone in safe mode ( hold ok button and power up , hold till r2 goes away ) and then start the DL . It may take a while between the download and the install but it worked for me...

abalsor said:
sorry it took a while to get back to you. I've been trying to get my wifes r2d2 to take the GB update. here is the link R2D2 nandroid backup..
Do a standard nandroi recovery with the file. You'll have to start the phone in safe mode ( hold ok button and power up , hold till r2 goes away ) and then start the DL . It may take a while between the download and the install but it worked for me...
Click to expand...
Click to collapse
DUDE YOU ARE AWESOME! The download got me back to stock. However i got into Safe Mode by holding OK down while booting but when i check for Updates it says "Check for update was not available at this time. Try again later." how did you get the update to download?

abalsor said:
sorry it took a while to get back to you. I've been trying to get my wifes r2d2 to take the GB update. here is the link R2D2 nandroid backup..
Do a standard nandroi recovery with the file. You'll have to start the phone in safe mode ( hold ok button and power up , hold till r2 goes away ) and then start the DL . It may take a while between the download and the install but it worked for me...
Click to expand...
Click to collapse
Just to confirm, this is the stock Froyo nandroid, not the GB nandroid, right? After restoring this nandroid still need to do the upgrade?

ehrune said:
Just to confirm, this is the stock Froyo nandroid, not the GB nandroid, right? After restoring this nandroid still need to do the upgrade?
Click to expand...
Click to collapse
this is the stock froyo nandroid.. and i did the update the same way as before just pulling it from the about phone tab...

Thanks!!! You're gonna have about a million new friends....well, maybe not quite that many.
I used Z4 to unroot, and got it to recognize/download the update, but it keeps failing. I'm assuming because of the bootstrap? When it reboots it goes into clockworkmod....did you mess with that at all, or did you not bootstrap?
Seriously though, thanks again for posting this.

unfortunately this did not work
it flashed but still would not update. I noticed it still had Superuser, Root Explorer and others. But still fails at the same point as before.

Tried factory reset, booting into recovery and wiping data/cache, rooting/unrooting, even deleting the Superuser.apk.....still gets about 1/4 of the way through installation before it reboots and says "Installation Failed". Same for everyone else?
At least I'm on the right version now though....

not sure why the updates failed. I only flashed this nandroid and did the update. I did see it was rooted before i did so. Sorry guys, wish i knew more...

Tried to install Liberty on my Droid X, messed up, stuck in a hole, plz dig me out

Up until today I never did anything to my droid x as far as rooting and roms. I kept everything completely factory and android was at its latest version which is gingerbread 2.3.3 and system version 4.5.605.MB810.Verizon.en.US.
My goal today was to finally experiment this and install Liberty Rom. I completely failed because of all the version complications and plenty of other errors. Before I describe my final problem I should backtrack and let you know exactly what I did today so you can possibly get me out of this mess.
1. The very first thing I did was follow all of the steps at a forum on droid-life "How To: Get Rooted Gingerbread On DROID X" sorry it won't let me post the link.
After all of this I ended up with gingerbread again, but I guess a rooted version. No idea why this was the tutorial I followed when trying to install liberty. Throughout the tutorial I ended up buying "Droid X BootStrapper" because the tutorial had me use it.
Right after this tutorial I bought an app called Rom Toolbox for $5.00 downloaded Liberty through it and was trying to install through it. Every time it rebooted I would get a black screen. Never worked so many issues probably because I flashed the wrong sbf or something.
Here are the programs that I ended up buying today:
z4root (free), DroidXBootStrapper ($2.00), Rom Toolbox ($5.00).
That is everything I have done and all of the apps I own. Can someone please start fresh and give me short instructions to start from scratch on how to get the latest and greatest version of Liberty on my droidx from where I'm stuck at now. I want to completely start over and I am willing to do anything. I hope the apps I bought help and I also want to assume 2 of them probably do the same thing and I didn't need them.

Buying those tools will at least help support 2 members of the community (Koush & JRummy).
I'm pretty sure Z4Root does not work on the GB versions of DX firmware. That's probably why nothing is working. You aren't actually getting root.
you are on the .605 version of GB (when you see references to .602, .605, etc ...)
To get root, start here:
http://forum.xda-developers.com/showthread.php?t=1258599
You may also want to download the Droid2 recovery rather than the DX. The D2 version is a little newer and I think avoids a slight bug on later kernels when Debug is on. The D2 version works just fine on the DX. It can be downloaded free from here:
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Once you are rooted and have recover properly working, you should be able to use the Rom Toolbox to download and install Liberty. Just make sure you read carefully about the 'version' requirements on any ROM.

Oh ok so I was rooting it wrong.
I easily rooted the phone using Pete's Motorola Root Tools. I realized that Rom Toolbox Pro accesses clockwork recovery when the phone is rebooted instead of the phone just restarting fully. But, I still want to start fresh and do everything from the start again. Please let me know if you have any suggestions in the way or order I am doing things. My phone is currently up rooted at 4.5.596 and rooted by Pete's Motorola Root Tools but I want to start over from the beginning so here is what I am going to do:
Note: Before I do anything I am going to format my SD card for a fresh start.
1. Use RSD_Lite 4.9 to Flash my phone back to 2.3.340 using a file called VRZ_MB810_2.3.34_1FF_01.sbf. I always do this part with no problem.
2. Do a hold power+home then search and do a system wipe/restore. Then Activate service, sign into gmail etc.
3. Now that the OS is loaded (the old version with the grey bars 2.3.340) I am going to root my phone using Petes Root Tools. (I hope I can root it with this tool when the firmware is this version.)
4. Put the 3 zip files I have on my SD card to upgrade to GB 588. Also put my GB 596 file on here.
5. I will download 1 app. D2BootStrapper. Bootstrap recovery, reboot into recovery. Install all 3 zip files from SD card. Now I boot up in GB 588.
6. Now I go right back into D2BootStrapper. Bootstrap recovery, reboot into recovery. Install GB 596. Now I have GB 596 rooted and loaded.
7. After this, shouldn't I be able to download Rom Manager Premium and Rom Toolbox Pro and test as many roms as I want? always reverting back to my original backup.
I noticed after installing liberty I was getting all kind of force close popups. And the phone wouldn't connect to service. But then I just held power + home then hit the up/down arrows and did a wipe/restore and it loaded liberty and everything works. Is this normally what has to be done when installing roms?
If there is anything wrong with my process please let me know. Whew I can't believe all that I learned in 1 day.

You've got a lot of steps there that really aren't necessary. When you install a ROM like Liberty, it replaces EVERYTHING in /system. Thus, about all that is left from a .596, .588, .602, etc install is the kernel. The Kernel doesn't change very often in Motorola builds. The last change was on .602. Thus, for your purposes there is no difference between .602 and .605 (FYI, .605 was just a keyboard fix over .602).
So, if you search around, you should find an SBF or AIO flash file to get you to .602.
Or you can simply take the OTA update from VZW after SBF'ing to .340
Once you've flashed your Rom, be sure to clear data/factory reset. You should then start with a clean system.

Alright, if you don't mind can you please let me know what steps I can avoid.
I didn't think it was possible to have a rooted .605 but I guess I was wrong.
So my goal should be to get to .605, then root it. Then install roms from there?

On your first post you said you were on .605. I'm assuming that is still the case.
If so, then root it with pete's tool (I think you've already done that).
Install D2bootstrap, then ROM Toolbox and install your rom from there.
I have to be honest, in that I've not used Liberty in a while, nor have I used Rom Toolbox. It shouldn't be a problem, just make sure that the version of Liberty you are using is for the GB kernel. Some of the older versions of Liberty (Which I did use, and like) were for the Froyo kernel (in that case, stay on .340 and do your upgrades).
Make sure you wipe data in recovery after installing the ROM. Lots of 'Boot Loops' are due to not wiping data after flashing a new rom.

Yeah
Yeah I read up on all of that. I actually might not end up going with Liberty. Going to try others like ICX. But before I do any of this I need to get to .605.
No I am not at .605 I believe that's where my phone was before I started all of this.
Right now I am flashing back to 2.3.34
Once I am back up and running there. Can you please recommend the easiest way to get to .605 and that will be my final question.

.605 should update automatic. If not you can disable the updater using titanium backup by freezing system updater.
1. Use petes tools install cwm as well
A. Droid x bootstrap get this
B. Titanium backup. Backup your apps
2. Make a backup using cwm and backup apps with tb
3. Put the rom zip files on the sd card.
4. Reboot to recovery. Reformat system data etc
DO NOT REFORMAT THE SD CARD.
5. Wipe cache davik etc.
6 flash rom. And reboot.
7 run tb for your apps
Should be a smooth and clean install. The roms are already rooted so no need to worry about that. Hope this helps
Sent from my MyTouch 4G Slide using xda premium

We aren't supposed to link to other forums, so expect this link to get removed.
http://rootzwiki.com/showthread.php?399-UPDATED-GUIDE-LINKS-DX-SBF-s
I would point you to a link here, but couldn't find a quick/easy link to what I wanted.
In this list is an SBF file for .602. Since you seem comfortable with doing SBF's, I would just SBF straight to .602 and root it from there.
Don't know much about ICX, but would encourage you to look at the CM7DXGB thread over at Rootzwiki as well.

ohh, well I just went to Settings > About Phone and its auto updating to .605
Am I not going to be able to root it after this update or should it be fine.

HunterT said:
ohh, well I just went to Settings > About Phone and its auto updating to .605
Am I not going to be able to root it after this update or should it be fine.
Click to expand...
Click to collapse
Pete's Root tool should root .605 just fine.

One last thing
As far as Clockwork recovery goes.
Should I always be in the latest version 5.0.2.0 (the blue version)
Or the old version 2.something (the green version)
Why is there 2 version and why would I ever want to flash back to the old version 2.something?

Zaphod-Beeblebrox said:
Pete's Root tool should root .605 just fine.
Click to expand...
Click to collapse
Pete's will work on .605 I did two the other day
Sent from my MyTouch 4G Slide using xda premium

HunterT said:
As far as Clockwork recovery goes.
Should I always be in the latest version 5.0.2.0 (the blue version)
Or the old version 2.something (the green version)
Why is there 2 version and why would I ever want to flash back to the old version 2.something?
Click to expand...
Click to collapse
Couple things most of the updates are to add support fix minor bugs etc.
I run the one from petes all the time I forget which version. I haven't had problems.
On my mt4g slide I had to flash a modified verson of clockwork due to my phone being newer and not as much support
With that said its not a difficult process to get a new recovery image. You would need terminal emulator and root explorer. Couple of great guides on here on how to do so. Also other methods as well.
All in all the ones that pete's give you should suffice. Unless your one of the extreame types of people who want the newest or like messing around.
Just remember backups can make the process and hassle of soft bricking your phone much easier to fix and takes a few mins to do.
Look around the forums lots of great information from the devs, experts, etc
Sent from my MyTouch 4G Slide using xda premium

HunterT said:
As far as Clockwork recovery goes.
Should I always be in the latest version 5.0.2.0 (the blue version)
Or the old version 2.something (the green version)
Why is there 2 version and why would I ever want to flash back to the old version 2.something?
Click to expand...
Click to collapse
The newer version changes the way backups are stored. The new format is smaller and quicker.
Among other issues/bug fixes as mentioned before, but the backup issue is important as the new version will not restore the old style backups.