Database Users

Stuck in bootloader after 3.40

Used Boot Straper from Market flashed .320 from .315 everything went correctly verified update in settings. Booted with bootstraper again cleared all the partitions like cache installed
2.3.340 Kernel Updater (2.6.32.9-g55626e1) .zip
BP_C_1.09.07P Baseband Updater .zip
2.3.340 System Updater .zip
ApeX 1.3.1 .zip
note none where sbf files rebooted the system and im stuck in bootleader and reads
Bootloader
30.04
err:A5,69,35,00,27
Battery OK
OK to Program
USB connected
Data Cable
Nothing I do can avoid botloader. After Finaly getting RSD Loader 4.9 to reconize my device I tried to cure it by flashing Droid Life 2.3.340 .sbf file and RSD give err 0x700

Try the .320 SBF, then .340 SBF. If that fails you will have to wait until you can get a hold of the next full SBF.

I went to a new computer and I flashed .15 SBF I belive full bc it was like 400mb with success on flash but my cute little android man pissing on craple is gone and boots immedieately into BL saying no system. So Now flashing .340 SBF and see what happens. If this don't work I am fresh out of ideas

That won't work. Flash the full .320 SBF then the system only .340 SBF and you'll be fine.

mlclm said:
That won't work. Flash the full .320 SBF then the system only .340 SBF and you'll be fine.
Click to expand...
Click to collapse
This worked for me. You should do it this way.
Sent from my DROIDX using XDA App

iceblue11 said:
I went to a new computer and I flashed .15 SBF I belive full bc it was like 400mb with success on flash but my cute little android man pissing on craple is gone and boots immedieately into BL saying no system. So Now flashing .340 SBF and see what happens. If this don't work I am fresh out of ideas
Click to expand...
Click to collapse
If you are on stock 2.3.15 now, then just go to Settings>About Phone>System Updates. This should do the OTA update and bring you to 2.3.340. No Need to flash the 2.3.320 full sbf and then the 2.3.340 sbf.

Your right that won't work. Its stuck in loader so no system will boot. So I need to go find the 320 sbf in order to get out of this. I'm asuming its the 30.04 bootloader preventing the 315 sbf from bringing me out and why the 340 system sbf won't rescue me. Ok ill try it thanks

iceblue11 said:
Your right that won't work. Its stuck in loader so no system will boot. So I need to go find the 320 sbf in order to get out of this. I'm asuming its the 3040 bootloader preventing the 315 sbf from bringing me out and why the 340 system sbf won't rescue me. Ok ill try it thanks
Click to expand...
Click to collapse
Yeah, I think I remember reading if you have 30.04 bootloader, the 2.3.15 sbf will not work, but I can't remember for sure.
To check what bootloader you have, power off your phone. Now press and hold both volume keys; keep pressing the volume keys as you power the phone back up. The phone will proceed to enter bootloader mode and show you what bootloader you have.

Sorry for the pore responses and spelling. I was sneaking posts at the Verizon store while fighting with the manager to please charge my battery so I could flash my phone. Battery died on me apparently it will not accept any type of charge from the phone when stuck in boot loader.
bouchigo - Thanks you been a big help bud, Finally! Someone says how to put the X into that bootloader I couldn't figure it out so went with the clockworks .zip 340 system flash instead of the sbf. Had to google for the 320.sbf couldn't find much on here for this so it is downloading now and see what happens after that. I did find during my search that if the bootload was 30.04 the phone would not accept a 315 system so that is indeed accurate.
mlclm - Thank you

w00t phone just booted out of the dead with the 320.sbf!
Curious thing is what in my method caused the phone to do this?
Well no matter if im on 320 or 340 the phone wont activate over air programming and thus cant go anywhere past that damn droid icon, coincidence of bad timing was an outage in service on my area life is peachy now

iceblue11 said:
w00t phone just booted out of the dead with the 320.sbf!
Curious thing is what in my method caused the phone to do this?
Well no matter if im on 320 or 340 the phone wont activate over air programming and thus cant go anywhere past that damn droid icon
Click to expand...
Click to collapse
Strange. I have had the ota programming fail and I had the option to skip. Then open dialer and do *22899 to program.
Sent from my DROIDX using XDA App

iceblue11 said:
w00t phone just booted out of the dead with the 320.sbf!
Curious thing is what in my method caused the phone to do this?
Well no matter if im on 320 or 340 the phone wont activate over air programming and thus cant go anywhere past that damn droid icon
Click to expand...
Click to collapse
Try doing a "data/factory reset" and "wipe cache", after that reboot and see if fixes your problem.
1. Power off your phone
2. Press and hold the home key (the button with the little house on it).
3. While holding the home button down, power up the phone. Once phone starts to power up, you can let go of the power button, but keep holding the home button until you see a triangle with an exclamation mark in the middle with a little android underneath the triangle.
4. Now, press the search button (the magnifying glass button).
5. Scroll to "wipe data/factory reset" (with the volume up and down buttons) and select it with the camera button.
6. Now scroll to "wipe cache partition" and do the same as you did previously.
7. Reboot and hope it solved your problem.

Yeah I did all that to try and skip the programming. I could do emergency dial and do *22898 and get to customer rep who found a outage in my area after that was fixer the phone programmed like it should and all was good.
Im about to post on Apex thread about a small issue. But all together the setup is working so much better faster cleaner then the old setup so 5 *'s.
For some reason if you hold power button and select restart the phone will boot into clockworks recovery every time. Uninstalled clockworks app and still does it. And currently have 2 SMS apps and wont let me uninstall any of them and its causing all SMS to be duplicated. Only bugs so far

iceblue11 said:
Yeah I did all that to try and skip the programming. I could do emergency dial and do *22898 and get to customer rep who found a outage in my area after that was fixer the phone programmed like it should and all was good.
Im about to post on Apex thread about a small issue. But all together the setup is working so much better faster cleaner then the old setup so 5 *'s.
For some reason if you hold power button and select restart the phone will boot into clockworks recovery every time. Uninstalled clockworks app and still does it. And currently have 2 SMS apps and wont let me uninstall any of them and its causing all SMS to be duplicated. Only bugs so far
Click to expand...
Click to collapse
I had that service problem too when I SBF'd. When I was on .15 I tried to use the
system updater on droid world (stupidly) to .340 and the patches. So after I got
stuck on the bootloader like you did, I just SBF'd to .320 and then went back
to droid world and then installed the system updater (.340) with bootstrap and
then the following patches. I had to go outside to get at least one bar of service
in order to activate the phone. After about 20 minutes or so I started getting
signal back the way it was before. I *228 again a few times to get rid of the
roaming icon. Sometimes it takes a few programs to get you to the correct towers.
Here's the droid world thread.
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
Note: I of course activated the phone before using the system updater and patches.
Gain your signal back first before you get onto .340

iceblue11 said:
Yeah I did all that to try and skip the programming. I could do emergency dial and do *22898 and get to customer rep who found a outage in my area after that was fixer the phone programmed like it should and all was good.
Im about to post on Apex thread about a small issue. But all together the setup is working so much better faster cleaner then the old setup so 5 *'s.
For some reason if you hold power button and select restart the phone will boot into clockworks recovery every time. Uninstalled clockworks app and still does it. And currently have 2 SMS apps and wont let me uninstall any of them and its causing all SMS to be duplicated. Only bugs so far
Click to expand...
Click to collapse
Open droid x bootstrapper and hit the bootstrap recovery button. This should stop you booting to ce everytime you restart.
Sent from my DROIDX using XDA App

[Q] I messed up my boss's Droid X. Please help.

Okay, so I messed up my boss's phone today. I tried to do the flash player mod to watch Hulu found here: http://androidforums.com/droid-x-all-things-root/219288-modified-flash-hulu-droid-x.html (which I did SUCCESSFULLY on my phone). Anyway, I didn't realize that he had NOT made a backup of his Stock ROM (he just rooted his phone 2 days ago). When I did the Flashplayer mod not only did Hulu not work, but any time he opened his browser to the google hompepage it would kick him out of the browser. We tried pulling the battery, clearing cache (on the browser), force stop (on the browser), and nothing worked. I swear I did EXACTLY the same method that I did with my own and mine works fine. It's odd bc the google homepage shouldn't have anything to do with flashplayer. Btw, every other page I've seen seems to work okay with his browser. Anyway, do you guys know what might have happened?

Never really messed with the hulu hack myself... worst case scenario he will need to backup his apparently and data using titanium backup. Then I would make a nandroid backup of the current state as a place to get back to as a worst case scenario. Then sbf the phone and create a clean nandroid right away... then mess with the hulu hack in the event that it doesnt work again.
Sent from my DROIDX using XDA App

Try this
Try installing Dolphin Browser HD off of the market, and choose "on Demand" when starting the first time for flash plugin. See if it works then

lulz.......

You can't reinstall flash player from the market by uninstalling updates then reinstalling?

Everyone keeps saying to do a sfb (which I wanna do for myself) and I've asked in 2 other threads how to do that and asked exactgly what it does. No one has respinded. What is it and how do I do it?
Sent from my DROIDX using XDA App

It returns the phone robots original out of the box state.
Sent from my DROIDX using XDA App

There are instructions online.. i think everyone needs to know how to sbf if they flash new roms, etc
Sent from my DROIDX using XDA App

Can you provide me with a direct link? And wouldn't a simple factory data reset work instead?
Sent from my DROIDX using XDA App

mj23kb08 said:
Can you provide me with a direct link? And wouldn't a simple factory data reset work instead?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No, a factory reset only affects /data and /cache portion of the phone OS I believe. An sbf can be found here:
http://www.mydroidworld.com/forums/droid-x-discussion/5633-droid-x-2-3-32-full-sbf.html
This is the 2.3.32 full sbf that you will need to flash first. Next you will need the 2.3.34 system only sbf:
http://www.megaupload.com/?d=OXK9Q1ZG
Make sure after you do each sbf to do a battery pull, then boot into Moto recovery (hold down home button while pressing power, then when the droid comes up, press search button), then do a factory reset. This will help to ensure a clean sbf process without issues.
Good luck, and post back if you have questions.
PS make sure to use at least RSDlite 4.8 for flashing these files.

SysAdmin-X said:
No, a factory reset only affects /data and /cache portion of the phone OS I believe. An sbf can be found here:
http://www.mydroidworld.com/forums/droid-x-discussion/5633-droid-x-2-3-32-full-sbf.html
This is the 2.3.32 full sbf that you will need to flash first. Next you will need the 2.3.34 system only sbf:
http://www.megaupload.com/?d=OXK9Q1ZG
Make sure after you do each sbf to do a battery pull, then boot into Moto recovery (hold down home button while pressing power, then when the droid comes up, press search button), then do a factory reset. This will help to ensure a clean sbf process without issues.
Good luck, and post back if you have questions.
PS make sure to use at least RSDlite 4.8 for flashing these files.
Click to expand...
Click to collapse
Thank you for the links. However, I'm not familiar with RSD Lite, so I don't know how to use it or how to flash these sbf files. I clicked on the first link and the instructions seemed vague and geared more towards people who already know what they are doing. I've only tried flashing 1 custom ROM (Fission) and I've flashed various states of the stock ROM several times. So, when it comes to this sbf stuff I'm very much a noob. I'm scared to death of bricking my phone or my boss's phone for that matter, so would you mind giving me step by step instructions on how to flash these two sbf's? Or at least send a link to a site with "noob" instructions? Thanks in advance.

mj23kb08 said:
Thank you for the links. However, I'm not familiar with RSD Lite, so I don't know how to use it or how to flash these sbf files. I clicked on the first link and the instructions seemed vague and geared more towards people who already know what they are doing. I've only tried flashing 1 custom ROM (Fission) and I've flashed various states of the stock ROM several times. So, when it comes to this sbf stuff I'm very much a noob. I'm scared to death of bricking my phone or my boss's phone for that matter, so would you mind giving me step by step instructions on how to flash these two sbf's? Or at least send a link to a site with "noob" instructions? Thanks in advance.
Click to expand...
Click to collapse
RSD Lite was originally used for old Motorola dumbphones like the Razr and some early smartphones. I have an Evo now but I remember how to use it from back when I had a Razr. Just select the SBF file and after it sees the phone hit Flash. Make sure to get a second opinion from an actual Droid X user first since I'm not sure if there's anything extra that needs to be done.

mj23kb08 said:
Thank you for the links. However, I'm not familiar with RSD Lite, so I don't know how to use it or how to flash these sbf files. I clicked on the first link and the instructions seemed vague and geared more towards people who already know what they are doing. I've only tried flashing 1 custom ROM (Fission) and I've flashed various states of the stock ROM several times. So, when it comes to this sbf stuff I'm very much a noob. I'm scared to death of bricking my phone or my boss's phone for that matter, so would you mind giving me step by step instructions on how to flash these two sbf's? Or at least send a link to a site with "noob" instructions? Thanks in advance.
Click to expand...
Click to collapse
Here is the link to download RSDlite 4.8.
http://www.multiupload.com/HL0ZAL9GK8
You will want to download this, and then install it on a windows machine. Then in order to use the SFB files (use 2.3.32 first, then 2.3.34), plug in your phone to your computer. I'm pretty sure you need the Android SDK installed, and the correct moto drivers installed as well (not sure.. i've had this set up on my computer forever...). Next, turn off your phone and press and hold "volume down + camera button + power button" and this will boot your phone into bootloader. It will say 30.03 (if you are on 2.3.15 OTA update) or 30.04 (if you are on 2.3.32 or 2.3.34 releases).
Then open up RSDlite on your computer which you installed it. With the phone plugged in, choose the "..." button in RSD lite and browse to the SBF file that you downloaded (remember 2.3.32 first) and then it should show your phone as a device listed below in RSDlite. If it recognizes your phone, you can click the start button in RSDlite. It will then start doing its thing.
My recommendation is to make a nandroid backup before doing this as a last resort if something goes wrong. The first time that you run the SBF file, it may get to like 98 or 99% and then say fail (something about passing BP baseband or something similar, and your phone will reboot). Don't worry, this has happened to me a couple times when I first started using the SBF files and scared me to death. After the phone reboots, pull out the battery and replace it back in. Then hold down the "home" button while pressing the power button. Then when the picture of the little green android dude shows up, press the search button (this is the motorola recovery screen). Then go to "factory reset/wipe data" (or something similarly titled). You can navigate the menus by using the volume up/down buttons. You will make your selections by pressing the camera button.
If you dont get the little android guy to show up, then turn the phone off and try again. After you have wiped data/factory reset, you may need to activate your phone. If it doesn't automatically prompt you to do this, from the dialer app, type *228 and then call. Then choose the option to program your phone, and you will be back in business.
After an SBF, your phone is completely wiped clean, so you will need to re-root, and install bootstrap/any other mods you need.
Hope this helps. Let us know if you have more questions.

Here is a great how to guide. Great forum with lots a smart helpful people.
http://www.droidxforums.com/forum/droid-x-rs-guides/12015-complete-droid-x-sbf-flashing-guide.html
Sent from my DROIDX using XDA App

[Q] Help to Uninstall ver. 2.3.3

I had the Liberty 1.5 ROM on my Droid Rooted with Rom Manager Clock Work recovery and everything was fine until..
I found a file on the web called Monster_D2_2.3.2_4.5.153 I used Clock Work recovery and installed it.
Now my phone says I have Android Version 2.3.3 Build Number STAB
Kernal Version: 2.6.32.9-gd72dc5da20523
It's running fine but I have lost ClockWork Recovery. I can not root the phone after trying several different methods. I can not install anything on it with its stock recovery without getting a signiture failure in the stock recovery and worst of all I can not uninstall it or overwrite it with anything I have loaded on the SD card.
I would be happy to remove this build and re-install Liberty.
I would be even more happy If I could just get this rooted and have my clockwork recovery back.
can anyone help me by pointing me to a thread or link that can help?
Thanks SO much
Gingerbread Dead :0

The problem is that there isn't a known process for rooting Gingerbread (except for installing a pre-rooted ROM)
SBF back to stock, and then you should be able to root, install clockworkmod, and then reinstall Liberty.
pcwebiz said:
I had the Liberty 1.5 ROM on my Droid Rooted with Rom Manager Clock Work recovery and everything was fine until..
I found a file on the web called Monster_D2_2.3.2_4.5.153 I used Clock Work recovery and installed it.
Now my phone says I have Android Version 2.3.3 Build Number STAB
Kernal Version: 2.6.32.9-gd72dc5da20523
It's running fine but I have lost ClockWork Recovery. I can not root the phone after trying several different methods. I can not install anything on it with its stock recovery without getting a signiture failure in the stock recovery and worst of all I can not uninstall it or overwrite it with anything I have loaded on the SD card.
I would be happy to remove this build and re-install Liberty.
I would be even more happy If I could just get this rooted and have my clockwork recovery back.
can anyone help me by pointing me to a thread or link that can help?
Thanks SO much
Gingerbread Dead :0
Click to expand...
Click to collapse

Yup, SBF is the way to go.
SBF Guide:
http://forum.xda-developers.com/showthread.php?t=770224 (be sure to use RSDlite 4.9)
SBF Download:
h t t p://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html
If you made a backup of liberty before you installed 2.3.3, after you root and put clockwork on, you should be able to just restore it.
It's always good to do as much research as you can before trying anything like that.

I installed VRZ_A955_2.3.20_1FF_01.sbf
Then I was able to root the phone and use my root applications. The device is very slow and too sketchy to complete anyone task so it was a failure.
Now with your advice I should get back on the right track. Thank You very much for the response. I thought for a moment I might have to drop my phone on the pavement and go to phoneclaim dot com. But you cant learn anything taking the easy way out. lol I'll post the outcome.

pcwebiz said:
I installed VRZ_A955_2.3.20_1FF_01.sbf
Then I was able to root the phone and use my root applications. The device is very slow and too sketchy to complete anyone task so it was a failure.
Now with your advice I should get back on the right track. Thank You very much for the response. I thought for a moment I might have to drop my phone on the pavement and go to phoneclaim dot com. But you cant learn anything taking the easy way out. lol I'll post the outcome.
Click to expand...
Click to collapse
Yup, as long as you can get the phone into bootloader mode, the phone isn't bricked.
Hope everything works out!
Sent from my Liberated DROID 2

I've had that performance problem after SBF'ing as well. I think I cleared data and rebooted a couple times to address the issue...

Complete Recovery!
Thank You SO much!

I began having a black screen.after a few weeks on gingerbread so I decided to sbf back to froyo but it failed now my phone gives the MOTO logo and goes directly to a black screen. I can't get it into flash mode even with holding the arrow up key. I'm out of ideas here so I'm really hoping to find a way to get this working again without being worried that its truly bricked. Any help would be greatly appreciative.

Have you been able to boot into anything else, such as the stock recovery?

[Q]Just plain lost

Ok so as my previous post stated I just got my droid x and rooted it. I am in the process of installing a rom but have failed at this point.
For starters I have the droid x bootstrap installed and "running". Buy "running" I mean I can get to the clockwork recovery but only buy the bootstrap button or battery pull for 1min then boot. Booting while holding the home button stops at the exclamation android guy. I cant get past it no matter how hard I push the search button . So thats one of my problems but not a big one.
When I went to install liberty 1.5 I did a data factory reset and catch wipe then installed the rom. It got stuck on the liberty logo. So I tried again this time following the guide on these forms on how to install a rom correctly. Same thing. I tried three more times following three different guides and still was stuck at the liberty logo. So I gave up and followed the install guide on these forms again, but just restored from my backup. I am good and running again but I still have the liberty logo, which from what I read is normal.
When I got home from work I started digging into why it didn't work and found several things that may cause it. Now this is where I get lost. I have read the sometimes it just fails and you need to try again. But I also read the doing a SBF will also fix this. So I dug into what a SBF is and how to do it since this seams to be the #1 fix for everything. WHAT, UHH, MMMMM, K. So I read you will need to flash 2 files to SBF successfully. I have no problems with the RSD lite as it is only one file and you cant screw that up. But then I comes to choosing the right SBF file for your phone I get lost. All the versions listed are WAY below what I have. I am currently on 4.5.588. So I jumped over to androidforms to see if theirs anything their. They list x.x.596 as the most recent OTA but when I go to check for updates it says there are none.
SO, my questions are:
Is the reason I cant flash the liberty rom because I am running 4.5.588?
What do I flash if I need to SBF?
What am I missing about this OTA update? Is it being rolled out now or is my rom the most recent OTA?
Is their anything else I need to know that might help me in the future? Like I said I am new to this area of the forms and have not clew whats being released, changed, rooted, or what ever else.
I came from a rooted eris so Im not root dumb. But their is a big difference between the eris and the X.
ANY HELP WOULD BE AWESOME THANKS!!!!!!!!

BrownEye02 said:
Ok so as my previous post stated I just got my droid x and rooted it. I am in the process of installing a rom but have failed at this point.
For starters I have the droid x bootstrap installed and "running". Buy "running" I mean I can get to the clockwork recovery but only buy the bootstrap button or battery pull for 1min then boot. Booting while holding the home button stops at the exclamation android guy. I cant get past it no matter how hard I push the search button . So thats one of my problems but not a big one.
When I went to install liberty 1.5 I did a data factory reset and catch wipe then installed the rom. It got stuck on the liberty logo. So I tried again this time following the guide on these forms on how to install a rom correctly. Same thing. I tried three more times following three different guides and still was stuck at the liberty logo. So I gave up and followed the install guide on these forms again, but just restored from my backup. I am good and running again but I still have the liberty logo, which from what I read is normal.
When I got home from work I started digging into why it didn't work and found several things that may cause it. Now this is where I get lost. I have read the sometimes it just fails and you need to try again. But I also read the doing a SBF will also fix this. So I dug into what a SBF is and how to do it since this seams to be the #1 fix for everything. WHAT, UHH, MMMMM, K. So I read you will need to flash 2 files to SBF successfully. I have no problems with the RSD lite as it is only one file and you cant screw that up. But then I comes to choosing the right SBF file for your phone I get lost. All the versions listed are WAY below what I have. I am currently on 4.5.588. So I jumped over to androidforms to see if theirs anything their. They list x.x.596 as the most recent OTA but when I go to check for updates it says there are none.
SO, my questions are:
Is the reason I cant flash the liberty rom because I am running 4.5.588?
What do I flash if I need to SBF?
What am I missing about this OTA update? Is it being rolled out now or is my rom the most recent OTA?
Is their anything else I need to know that might help me in the future? Like I said I am new to this area of the forms and have not clew whats being released, changed, rooted, or what ever else.
I came from a rooted eris so Im not root dumb. But their is a big difference between the eris and the X.
ANY HELP WOULD BE AWESOME THANKS!!!!!!!!
Click to expand...
Click to collapse
im no pro but hopefully this info will help you, it did me.
http://forum.xda-developers.com/showthread.php?t=1073841 liberty info
http://forum.xda-developers.com/showthread.php?t=1085323 sbf'ing
The new 2.3.3 OTA is stable and very nice looking on my DX, OTA not rootable yet but give it time.
Biggest life saver about the DX is the the part of the phone that ppl mess up and turn their phones to bricks is extremely safe on the X, not bulletproof but all the info in these forums I believe can bring them back regardless of what happens. I was very overwhelmed at first with my X but very comfortable now that ive successfully managed the sbf.

Yeah that's one of the things I really noticed. If you brick your phone it seams its not the end. So im still a little confused with your explanation on SBFing. You say that 2.3.3 is the latest OTA but its not rootable. So am I looking at the wrong number when I say my version is 4.5.588.
Sent from my Rooted DROIDX.

Reading the noobs guide to droid x allowed me to figure out that I have the 30.04 bootloader and I will need to flash the 2.3.34 file. But I would still like to know why my version is so much higher then 2.3.34.

By far, this is the easiest way to sbf back to stock froyo
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Sent from my Xoom using XDA Premium App

chbennett said:
By far, this is the easiest way to sbf back to stock froyo
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
WOW that is easy. To bad you cant select what version it flashes. But still EASY. Ill keep that in mind if I need to SBF. THANKS!

http://droidmodderx.wordpress.com/how-to-sbf-your-droid-x-full-2-3-340/
Good video tutorial there... It also has files there as well
Sent from my DROIDX using XDA App

Well I gave liberty 1.5 another try and it still got stuck on the liberty screen. Any ideas?
Sent from my Rooted DROIDX.

Was able to flash the liberty gingerbread rom tonight! I am kind of wondering if the version of ota/bootloader I have is the reason liberty 1.5 wouldn't work for me.

BrownEye02 said:
Reading the noobs guide to droid x allowed me to figure out that I have the 30.04 bootloader and I will need to flash the 2.3.34 file. But I would still like to know why my version is so much higher then 2.3.34.
Click to expand...
Click to collapse
your looking at the version of the software build, complete jargon here but say your on android 2.2.1 version blah blah blah, what i was referring to was although you may have a higher version of 2.2.1 than what you are reading, a lower version of a higher android software such as 2.3.3 is better than a higher version of 2.2.1 same page?

[Q] How To Needed - update from 2.2.1

I've been running Liberty on my Droid X for some time now and love it compared to the stock Blur interface. But it's gotten to the point where I'd like to update from Froyo to one of the more modern versions and see if that can liven up the phone again. So my question is this - from what I've read before I can update Liberty (or any other ROM for that matter) from a Froyo based version I need to restore the phone to a semi-stock state, update via an official OTA release, re-root and go from there. Is that true? If so, any convenient guide on how to do so? I did a bit of searching and couldn't find much and while I'm pretty technically inclined my skills do not extend into the phone region and back when I originally modified the phone there were many handy guides and videos to walk me through it.
Any help would be greatly appreciated.
Nate

If your bootloader version is 30.04, SBF to 4.5.602. From there you can flash any Gingerbread or ICS rom of your choice.
If your bootloader version is 30.03, SBF to 2.3.15 and take the OTA update.
Sent from my Transformer TF101 using Tapatalk

Let the stupid questions begin...
Ok, I confirmed that I'm running 30.04 and I found a site that maintains the correct 4.5.602 file so I downloaded that. Is there anything that I need to back up before installing? Also, I read that a special program is required to install the SBF files so any assistance there would be appreciated as well.
Thanks!

Ok, so I managed to track down RSD-Lite and got it to recognize the device and start loading the sbf file however the phone couldn't get past the "manually power up the phone" phase (or something like that). It just kept showing the boot animation over and over again regardless of what I did - it would cycle between the red eye and the DROID text. I tried pushing and holding the power button, no good and none of the other buttons did anything either. Nothing worked. So I'm rerunning it again and we'll see if the second time is a charm...

Well crap, I got through the SBF install process and got the pass message from RSD but now my phone is stuck at the animation and won't go any further. I've left it running for the better part of 10 minutes and it just hangs. I'm now performing a manual factory data wipe to see if that will help.
EDIT: It appears that the factory data wipe got me through the locked animation. Still having minor issues getting through the programing and setup phase but I think it'll work eventually.
Thanks again for the help.

infazzdar said:
If your bootloader version is 30.04, SBF to 4.5.602. From there you can flash any Gingerbread or ICS rom of your choice.
If your bootloader version is 30.03, SBF to 2.3.15 and take the OTA update.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Minor question/problem for you, sir.
Wouldn't the OTA take you all the way to .621?
Wonderful...yet another thing we need to worry about that damn update <_<
OP:
Glad you got it worked out.

Well, it's sort of worked out.
Everything is up and running but ROM Toolbox isn't able to load any ROMs. It gets granted Superuser permission so I'm pretty sure that I've got the X rooted correctly but when it tries to boot into Clockwork it appears to get an error (icon with an exclamation point) and reboots into the regular Blur interface. I'm going to have a go at loading something like Liberty Gingerbread or 3.0 via zip file but it makes me nervous that the Toolbox Pro App can't get this done.

After determining that the Toolbox App was not booting into Clockwork I downloaded and installed the Droid X Bootstrapper App and got that running. It was able to correctly boot into recovery from which allowed me to install the Liberty 3 ROM. I'm now going back through the process of setting the phone up with the new ROM so we'll see how that goes. It appears to be working, but only time will tell if it's stable. One thing is for sure, a few hours on Blur'd Gingerbread and I was ready for something else again.

Jubakuba said:
Minor question/problem for you, sir.
Wouldn't the OTA take you all the way to .621?
Wonderful...yet another thing we need to worry about that damn update <_<
OP:
Glad you got it worked out.
Click to expand...
Click to collapse
I was actually wondering whether it would or not, but I can't think of another way to update the bootloader.
Sent from my DROIDX using Tapatalk

Ok, so here's an issue that I'd appreciate some guidance on. After installing Liberty 3.0 it appears as if the phone can't fully charge. It was plugged in for 10hrs last night and yet this morning the battery only reads 61%. I don't know if it would be best to boot into recovery and wipe the battery stats not knowing if it's fully charged or not.
Thoughts?