Related
OK so I was using the RSD 4.7 w/patch. I was trying again since it failed last time. I knocked the usb cable out now. It reads "code corrupt" I am trying one last time to see if the sbf file goes through. Anyone get any ideas?
slseale said:
OK so I was using the RSD 4.7 w/patch. I was trying again since it failed last time. I knocked the usb cable out now. It reads "code corrupt" I am trying one last time to see if the sbf file goes through. Anyone get any ideas?
Click to expand...
Click to collapse
Doesn't sound good. If the sbf procedure is interrupted before it finishes then only the manufacturer can fix it.
ok i had the same situation but i unbricked my phone.
initially i borked my services.jar file and got endless bootloop.
so i then attempt the sbf on win7 64bit.
1st attempt says it fails on the uploading RAM to bootloader.
phone reboots but is still in bootloop.
2nd attempt says failed at same part so i unplug the phone and im stuck with
code corrupt. At this point pressing power makes the phone go straight to the bootloader with code corrupt message.
Ok so i call verizon and ask if they got any Droid x in stock lol. They of course tell me nope so i try again but this time i switch to a different computer using
Win XP 32bit. i download rsdlite with patch , drivers and of course the sbf file.
3rd attempt i get through phone is back to working order, and the /data partition is untouched so all my apps are still intact.
just had to re-root the phone.
close call i must say but at least i know it does work now. Think its the 64 bit OS
that messed it up.
the only other thing i noticed is that when i installed rsdlite on winxp and started it up my firewall asked for permission to unblock rsd from the net.
when i installed on my win7 64 bit the firewall nvr asked for this permission so im guessing the program contacts outside sources for something?
only thing i can think of for the intial failure 64bit or firewall.
hope this helps anyone else having problems
slseale said:
OK so I was using the RSD 4.7 w/patch. I was trying again since it failed last time. I knocked the usb cable out now. It reads "code corrupt" I am trying one last time to see if the sbf file goes through. Anyone get any ideas?
Click to expand...
Click to collapse
who can help me ,waiting .................
liliu said:
who can help me ,waiting .................
Click to expand...
Click to collapse
Try downloading a later version of RSD Lite, such as 4.8. Or even better, use Linux.
But the 'code corrupt' issue is common and you need only SBF to fix it.
Sent from my DROIDX using XDA App
dont worry about it. Ive had this show up on my bootloader plenty of times.
What u wanna do is .sbf back to a working copy of .340 (VRZ_MB810_2.3.34_1FF_01.sbf) and start over again
There is also a bootable linux iso image available for download. Fully automated and totally painless way to SBF back to Froyo 2.3.340.
My DroidX Thrives on the DarkSlide!!
liliu said:
who can help me ,waiting .................
Click to expand...
Click to collapse
use the linux sbf solution.
after a failed windows flash for any reason i resort to linux. but thats just me and i have never had a bad flash using linux....ever. i have brought many dead devices back to life
read and re-read the instructions. then proceed at you own risk.
Droid X SBF with Linux
+1 on linux.
It takes way more time to get RSD working on Win7 than when I use XP. For some reason the drivers just don't seem as robust.
http://www.multiupload.com/ZUK28IEYAU
download this linux based disc image.... burn the iso with a program such as nero or even the windows image burning software
boot from cd.... all you need to do is start your phone up in bootloader already hooked up to your computer and run this disk
Just wanted to +1 the Linux boot disc suggestions. When you get the CODE CORRUPT error message it means the SBF flash failed in some way. The linux method should get you up and running again. It's never failed for me.
SaurusX said:
Just wanted to +1 the Linux boot disc suggestions. When you get the CODE CORRUPT error message it means the SBF flash failed in some way. The linux method should get you up and running again. It's never failed for me.
Click to expand...
Click to collapse
+1 for any Linux sbf method, works ten times better than using RSD Lite.
Sent from my DROIDX using XDA App
I also will +1 the Linux method to sbf, has worked flawlessly for me, never longer that 15 from insertation of CD into comp. It's great.
Enjoy. Terry
Sent from my DROIDX using XDA App
No Megaupload
I am looking for solutions to sbf'ing my phone and I keep running into links to download from megaupload...wait...I think it just worked. I updated to the most recent rsd lite and it worked while I was writing this. I was going to try the method above, which has a link to megaupload, but I guess I don't need to.
I did find the sbf files here: It won't let me post a sites.google.com/site/motosbf/
I had to do a lot of digging to find that. Is there somewhere else that people are putting files like these and files like the Linux one mentioned above?
weekscorp said:
I am looking for solutions to sbf'ing my phone and I keep running into links to download from megaupload...wait...I think it just worked. I updated to the most recent rsd lite and it worked while I was writing this. I was going to try the method above, which has a link to megaupload, but I guess I don't need to.
I did find the sbf files here: It won't let me post a sites.google.com/site/motosbf/
I had to do a lot of digging to find that. Is there somewhere else that people are putting files like these and files like the Linux one mentioned above?
Click to expand...
Click to collapse
Google "1kds Droid x" it should turn up everything you need.
Sent from my Transformer TF101 using Tapatalk
I posted a step by step method with links (including .621 sbf) here
obviously, you don't want to sbf to .621 unless you already took the OTA....
Anyone around that used this thread?
My screen says 'service required, code corrupt'. RSD does not show the phone, it may not be able to get into fastboot. I am using Win 7 64 bit and I see some people say they had trouble with that? Should I try on a fresh win 7 32 bit?
Thanks
There is no fastboot. Just bootloader.
sd_shadow posted an in depth on how to sbf your phone and gain root. Go read it. Download the files. Make a boot disc/usb. And do it.
There is no reason to use RSD with the ezsbf method. You can do whatever you want. But the ezsbf/root method is the easiest even if it looks difficult.
RSD Lite on Windows 7 64 bit
SharpnShiny said:
Anyone around that used this thread?
My screen says 'service required, code corrupt'. RSD does not show the phone, it may not be able to get into fastboot. I am using Win 7 64 bit and I see some people say they had trouble with that? Should I try on a fresh win 7 32 bit?
Thanks
Click to expand...
Click to collapse
I have also had trouble with Windows 7 64 bit. It was much easier when I went back to my old XP machine. It also works really well on Linux, I didn't even have to worry about drivers.
I can't use any more thanks today (reached the limit) but thanks!
I'm going to put 32 bit windows on a spare partition just to be sure.
I recently tried to upgrade to the new OTA gingerbread and it said that it installed okay, but after I reboot the phone it went straight to the bootloader with these errors: bootloader 30.04 err: a5,69,35,00,27. I then tried SBFing back to VRZ_MB810_2.3.34_1FF_01, but then it got through 97% of the flashing and got this error:: interface BP: loading RAM Downloader for Bootloader
failed flashing process. failed flashing process. interface BP: Error sending RAM Download for bootloader.
I have tried reinstalling the moto drivers with no luck. And it is also not charging. now when it boots into the bootloader it is flashing "battery low, cannot program" I searched all over the Internet and tried all of the recommended solutions like pulling the battery for a few minutes, I tried flashing four or five times, tried using older sbf, all with no luck. I would appreciate the help, thanks
You are going to need to charge your battery before you can sbf again. You might want to redownload the sbf again. If you go to droidxforums there is a linux distro that you download and burn as an iso to a cd that is really easy to run. First get your battery above 80 percent before you flash again. When I get to my computer I willingly post the link.
Sent from my DROIDX using XDA App
update: here is the link for the linux distro......http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
It sounds like you are missing a driver that installs towards the end of the flash. Sorry I can't post the link, but you can google moto driver download. It's the 4.90 drivers.
Sent from my DROID X in Western Illinois
Xodus83 said:
I recently tried to upgrade to the new OTA gingerbread and it said that it installed okay, but after I reboot the phone it went straight to the bootloader with these errors: bootloader 30.04 err: a5,69,35,00,27. I then tried SBFing back to VRZ_MB810_2.3.34_1FF_01, but then it got through 97% of the flashing and got this error:: interface BP: loading RAM Downloader for Bootloader
failed flashing process. failed flashing process. interface BP: Error sending RAM Download for bootloader.
I have tried reinstalling the moto drivers with no luck. And it is also not charging. now when it boots into the bootloader it is flashing "battery low, cannot program" I searched all over the Internet and tried all of the recommended solutions like pulling the battery for a few minutes, I tried flashing four or five times, tried using older sbf, all with no luck. I would appreciate the help, thanks
Click to expand...
Click to collapse
When you get your battery charged SBF again, when it fails do the "SYSTEM" only SBF and it will work. I believe the error (err: a5,69,35,00,27) you are getting has to do with the stock GB recovery. I had that problem but I was still able to boot into CWR and install a recovery patch by TBH. Let me know if this works for you.
I was wondering if there was a resolution to this issue. I am getting the exact same issue, Err:A5,69,35,00,27 and I have done everything but stand on my head. Previous to reading bigshotrob22's post, I had re-SBF'd from multiple computers, using different SBF versions, driver versions, and RSD Lite versions. All resulted in getting the darn ERR:A5,69,35,00,27.
The only way I ever got anything different was to flash 1.13.604 and then I got an error message Err:A5,70,70,00,1F.
Again, I goto a new version and I go right back to original error though.
I tried bigshotrob22's suggestion and downloaded the system and full sbf files for 340. I flashed the full, got error... Then flashed system, still get error.
I am using RSD Lite 5.4 on Vista 32 with UAC disabled (full admin mode), latest Moto drivers as of this post. Again, I have tried all of the versions of bootable linux SBF's as well. All yield the same result.
Wife's phone, she is very unhappy with me, and if I don't get her back up and running, I guess I will be dropping $500 on a new phone, as she is still under contract. If Mama ain't happy, I sure ain't getting any! LOL!
You could try taking it to a VZ store and telling them that this happened after the OTA. Seems to me that this is their fault and they should fix it.
So i was trying to get Gingerblur on my Atrix, because Orange has not released it yet and are being very slow at it, but anyway I followed the instructions on a site I visited quite carefully, but when I tried to turn the phone on it just came up with the Motorola start up picture and the red light starts blinking, I have tried a few methods, but I really need the phone working.
Please help.
Thanks in advance...
Sorry if I didn't explain it fully enough, please feel free to ask for a better explanation.
Tomn4569 said:
So i was trying to get Gingerblur on my Atrix, because Orange has not released it yet and are being very slow at it, but anyway I followed the instructions on a site I visited quite carefully, but when I tried to turn the phone on it just came up with the Motorola start up picture and the red light starts blinking, I have tried a few methods, but I really need the phone working.
Please help.
Thanks in advance...
Sorry if I didn't explain it fully enough, please feel free to ask for a better explanation.
Click to expand...
Click to collapse
Does it say anything? Does it power off after? Can you get into fastboot or android recovery?
Sent from my MB860 using xda premium
Yeah I can get into fastboot, and android recovery and all that stuff, but i'm not sure but I think I may have deleted the OS(or something like that) and it does turn off after a few minutes
Have you unlocked the phone? Can you get into rsd flash protocol? Might just flash the bootloader unlock and unlock it, after that flash a custom rom. Search for pudding or ihop to unlock.
I can get into RSD protocol, I tried a method on here last night which used RSDLite (this one http://forum.xda-developers.com/showthread.php?t=991072&highlight=flash+sbf )
it didn't work though it got to a certain point the said flash failed
Try the script I made here.
Is it suppose to take a while to boot up after flashing a new ROM?
Never mind it failed again...
matthew5025 said:
Try the script I made here.
Click to expand...
Click to collapse
I tried that but now on the phone is just says:
"Failed to boot 2
Starting RSD mode"
If your phone is unlocked. Flash the same exact version u had with this link. http://forum.xda-developers.com/showthread.php?t=1125944
This is an sbf. Download the correct version, install Motorola drivers, place in folder with least file paths ( ie: C:>atrix4g>sbf file ) use latest version of rsdlite or recommended. Follow sbf procedures. I am not responsible blah blah, but this should fix it. Don't panic. I have actually used this when I failed to unlock my bootloader. So in essence, it worked for my locked bootloader. Still, there is risk, try only if u feel comfortable.
Sent from my MB860 using xda premium
I think I flashed the wrong bootloader and messed everything up.
Phone has been bricked for about a week now.
Been doing research and tried a lot of .sbf's.
Nothing is working.
I think I need to clear my cache and/or wipe data, factory reset.
However I cannot get into stock recovery, just goes straight into bootloader.
This is the bootloader error code.
Bootloader
D2.35
Err:A5,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to program
Tranfer Mode: USB
I was on Gingerbread.
Flashing
sbf 1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keys-signed-Verizon-US.sbf.gz
doesn't work.
The only links that were good and I can use for reference are these, which are down.
http://and-developers.com/sbf:droid2
http://forum.xda-developers.com/showpost.php?p=9445568&postcount=2
Can someone help me out?
Also this should be included in the Recover Droid 2 sticky
Thanks in advance.
Have you tried using a newer version of rsdlite? I used to get all kinds of ****ty errors using the older version of rsdlite 4.8 then i tried the newer 5.6 and everything worked perfectly every time.
[1up] said:
Have you tried using a newer version of rsdlite? I used to get all kinds of ****ty errors using the older version of rsdlite 4.8 then i tried the newer 5.6 and everything worked perfectly every time.
Click to expand...
Click to collapse
I'm using 5.6
Even tried running RSD with admin rights.
No go. =/
Like I said, I think I need to clear my cache and factory erase
and perhaps try another .sbf
or go ezSBF iso file burn to disc or usb drive
boots to linux, http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html
sd_shadow said:
or go ezSBF iso file burn to disc or usb drive
boots to linux, http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html
Click to expand...
Click to collapse
I tried one linux disk and it didn't work.
I forgot what version.
I'll give this link a shot later today.
Thank you
I didn't realize you had a thread going in the general section.
I managed to find a copy of the 2.37 bootloader sbf.
It was a pain. Google translate got it's workout, thank goodness I didn't have to register on a forum in a language I can't read/understand.
Here it is:
BL_D237_cdma_droid2_Consumer_replacer_HSPart.zip
Hope this works.
newk8600 said:
I didn't realize you had a thread going in the general section.
I managed to find a copy of the 2.37 bootloader sbf.
It was a pain. Google translate got it's workout, thank goodness I didn't have to register on a forum in a language I can't read/understand.
Here it is:
BL_D237_cdma_droid2_Consumer_replacer_HSPart.zip
Hope this works.
Click to expand...
Click to collapse
I just tried this and i'm still left with the same error.
I cannot get into the stock recovery.
I think I need to get into the recovery so I can wipe the cache and clear data.
Then hopefully a .sbf will stick.
the stubborn 2.3.4
I was on 2.3.4 and got the same error when I tried flashing to 2.3.3
2.3.4 is currently still locked up tight and wont allow backwards flashing. I ended up flashing back to 2.3.4 and everything worked out fine, except the fact that i can't even root, of course.
I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.
cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?
Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!
More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.
Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.
Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:
Edit : Sorry I asked stupid question!
Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.
Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick