Database Users

[Q] code corrupt..bricked??

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.

[Q] Where Can I Get a Non Deodexed Stock Droid 2 Rom

Can someone please point me in the direction a stock, non deodexed, factory Droid 2 ROM. SBF isn't an option because that app doesn't play nice with my 64 bit version of Win7.

I meant to post this in the dev forum. Sorry mods.

Natty_lite said:
I meant to post this in the dev forum. Sorry mods.
Click to expand...
Click to collapse
No problem, I just moved it general to keep the forum order

Oh ok, guess I'm not crazy after all. Good deal.

FWIW, I had issues with the sbf from vista 64. Not sure which of these three things made it work, but I placed the sbf on my c: path, installed the very latest motorola connection app (and rebooted), and set the RSDLite executable to run as administrator. I used the version 4.8 of rsdlite. Might be worth another try...
Sent from my DROID2 using XDA App

You can also use this method which doesn't have the hassle with any drivers and can be used on any computer with a disk drive.

I have had no problems flashing my D2 on Win7 x64. You sure you have the correct drivers installed?

Yea, my drivers are fine. RSD sees my phone, but selecting the .sbf file doesn't give me the option to start, as if it is an invalid file. I can only assume its an Win7 64 problem, since it seems to be source of all of my issues.

newk8600 said:
You can also use this method which doesn't have the hassle with any drivers and can be used on any computer with a disk drive.
Click to expand...
Click to collapse
I have a Linux CD laying around somewhere. I may try that as a last resort. Is a plain jane, non deodexed ROM that hard to come by though??

Natty_lite said:
I have a Linux CD laying around somewhere. I may try that as a last resort. Is a plain jane, non deodexed ROM that hard to come by though??
Click to expand...
Click to collapse
Many see it as just stock with no adjustments. Why would you flash what you already started with or can "easily" .sbf back to?
I have Windows 7 Home Premium 64-bit and I have few issues flashing a .sbf file.
Please don't take offense - I only ask because it's orderly and even the smartest people have, admitted or not, missed some of these at one time.
Did you unzip the file you downloaded for the .sbf?
Have you tried uninstalling and reinstalling RSD Lite (Version 9)?
Where did your drivers come from?
Have you tried uninstalling and reinstalling your drivers?

Natty_lite said:
Yea, my drivers are fine. RSD sees my phone, but selecting the .sbf file doesn't give me the option to start, as if it is an invalid file. I can only assume its an Win7 64 problem, since it seems to be source of all of my issues.
Click to expand...
Click to collapse
Are you trying to flash while the phone is booted or while its in bootloader? The instructions around here recommend while it's booted, but really sbfs should be done from the bootloader.
Natty_lite said:
I have a Linux CD laying around somewhere. I may try that as a last resort. Is a plain jane, non deodexed ROM that hard to come by though??
Click to expand...
Click to collapse
ROM flashing on the D2 doesn't clear the system so you'll still have remnants from prior ROMs if they added anything.

@event121
I've installed the drivers several times. I don't think the drivers are the issue, because if they were, I doubt RSD would see my phone at all.
I've used 7,8, and 9

I just tried to do it while in the bootloader, RSD sees that the phone is connected, but I don't get the option to start after selectiong my DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf file.
I had no issue doing this on my Droid 1 (using a 32 bit Win7)
**UPDATE**
The other file that's there: BL_D235_cdma_droid2_Consumer_replacer_HSPart.sbf DOES in fact give me the option to fllash. Should I go ahead and do it?

I fixed my problem for those who were interested. My solution was to use another computer. Win 7 64 bit is a crap shoot, and I'm far from the only person who has experienced difficulties.
That's what I would suggest to anyone else having problems using SBF

Reverting From GB to a 340 Based Rom

Just to clarify for several out there new to leaks. Correct me if I'm wrong anyone:
Going from "unrooted" GB leak:
1. unstall RSD Lite and Drivers, Run RSD Lite
2. Hold volume down+camera+power until screen flickers and release and you should have the white lettered bootloader screen.
3. plug phone in and RSD will see it and run the full .340 sbf
4. Phone will reboot when done into old .340 stock
5. Run z4root and then bootstrap in to install new rom.
Going from "rooted/deodexed" GB:
1. Use droid 2 bootstrap (or dx bootstrap with usb debugging disabled) to boot into clockwork.
2. For good measure clear data/cache, dalvik cache, battery stats.
3. flash maderstock or monster 340.zip
4. Immediately reboot only as to not brick
5. Run z4root and then dx bootstrap in to install new rom
**No you can not install a .340 rom directly from GB rooted or otherwise. You must flash back to .340 first**
Thats what I understand is that RSD was only used for the unrooted GB leak due to the fact we couldn't access clockwork. Hope this is correct and helps out.

Hm. It seems that it is easier to get back from deodexed GB than I thought. Yesterday I did it via RSD Lite – it was a REAL PAIN.

Sorry for noob question, my camera doesn't work and I can't play any MP3 file
anybody could help me, please

why wont it show up in rsd lite
my phone isnt being detected in rsd lite any suggestions. i have every possible driver i can think of installed no errors just not working.
please need help asap. trying to fix a friends phones before he goes out of town.

zz0122 said:
Sorry for noob question, my camera doesn't work and I can't play any MP3 file
anybody could help me, please[/QUOTE
You need to update your system. Sbf to the correct bootloader version and the get an OTA update
Click to expand...
Click to collapse

still no luck in getting the phone to be detected by rsd lite and ive tried everything i can find through searching google. any help would be greatly appreciated. thanks.

MahaVoodoo said:
Hm. It seems that it is easier to get back from deodexed GB than I thought. Yesterday I did it via RSD Lite – it was a REAL PAIN.
Click to expand...
Click to collapse
How did you rsd yours back to .340. I cant get mine to be detected by rsd. all appropiate drivers have been installed and have recieved no errors of any sort phone just not being detected by rsd.

Not sure if I answered this in the other thread or my browser didnt update. To get my rsd lite to see phone in bootloader go config >device id>first come first serve.

Make sure you have all the needed Motorola Drivers. rsdLite would not see mine untill i installed all the latest drivers...then a piece of cake

[Q] Having trouble with RSD

Hello everybody, I have an Atrix running Gingerblur 4.5 and was trying to flash back to stock 1.2.6. I've flashed to stock before when I went from greyblur to gingerblur so I had an idea of what to do yet I still used the Guide thread on how to flash.
I've updated my drivers and installed rsd 5.0
My problem is that my phone will not appear in rsd (yes my phone is in rsd mode when connecting). I tried to use an older version of rsd and my phone appeared immediately, however, the flashing process fails and says that chipset type 53 is not supported.
Can anybody help me with this issue? I searched and could not find a solution other than "install the latest rsd," I have done this and reinstalled the program and drivers multiple times.
I am on a 64 bit windows 7 dell by the way.

nickstachio said:
Hello everybody, I have an Atrix running Gingerblur 4.5 and was trying to flash back to stock 1.2.6. I've flashed to stock before when I went from greyblur to gingerblur so I had an idea of what to do yet I still used the Guide thread on how to flash.
I've updated my drivers and installed rsd 5.0
My problem is that my phone will not appear in rsd (yes my phone is in rsd mode when connecting). I tried to use an older version of rsd and my phone appeared immediately, however, the flashing process fails and says that chipset type 53 is not supported.
Can anybody help me with this issue? I searched and could not find a solution other than "install the latest rsd," I have done this and reinstalled the program and drivers multiple times.
I am on a 64 bit windows 7 dell by the way.
Click to expand...
Click to collapse
this happens to me too. couldnt fix it so i fastboot everything

Thanks for that, I was worried that I'd just be stuck with gingerblur. Gonna have to do some research for fastbooting.
EDIT: Can anybody point me in the direction of some fastboot instruction for my particular problem here?
2nd EDIT: My problem was solved by downloading RSD 5.3.1, you'll have to search to find it as it isn't in the flash guide here on xda. I hope anybody with my problem can just refer to this.

Bricked my phone trying to root-Need help getting it back to stock

Hey guys, let me just preface this by saying that this was my first time trying to root, and that I am still very unfamiliar with many of the things involved in rooting. That said, here is my problem and almost exactly what I did to get there.
Alright, so I chose last night to be the night when I finally rooted my Droid 2. I had android 2.3.4 gingerbread .621 version when I started. I ran through the easy windows install instructions first on this page: well, since I can't post links, the page is http: //rootzwiki . com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/ (just remove the spaces in the web address). This didn't work because being the noob that I am, I didn't realize how to flash the .sbf file using rsd lite (now I know how to do that I guess, just a little too late).
So I said screw that, I will just run the cd. I downloaded the .iso, burned it to cd, booted to cd, and ran the program. The first time, I tried using the "Root Only" option. This ran, but didn't seem to work. So once that didn't work, I ran the first option that let you have the option to root (I have forgotten the exact wording). This worked and I got to the screen where I had to factory reset the phone. However, instead of being able to do this, I was stuck in bootloader with the error message "Err: A5,70,70,00,1F." So at this point I kind of realized that I was screwed so I tried to flash stock android 2.3.4 back to my phone using RSD Lite. I did this, and ended up changing the error message from the previously mentioned one to "Err:A5,70,70,00,00." So at this point I figured that I had a bad .sbf file and downloaded a new one and used RSD Lite to flash it. After I did this and it failed, I now am stuck in bootloader with a "Code Corrupt" message.
So basically, rooted or not, I would like to be able to use my phone again. I have seen in a couple places that the problem could be due to low battery, but I have switched to a fully charged one with no luck still.
This was my first attempt at rooting, and I am fully hating my first experience, but I'm already this far so I am willing to do the work to learn and get my phone back. If anyone can provide me with some pretty detailed instructions (remember, I'm a total noob and bricked my phone on something everyone else seems to have had no trouble with), that would be incredible.
Thank you in advance!

Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http://droid.koumakan.jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?

bhigham said:
Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http ://droid. koumakan.jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?
Click to expand...
Click to collapse
Yes, it is the droid 2.

bhigham said:
Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http ://droid.koumakan. jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?
Click to expand...
Click to collapse
Quick question though, when I am looking for an SBF to flash, do I want to flash on 2.3.4 like I had on, or a previous version, or does it matter?

xwsxlogan said:
Quick question though, when I am looking for an SBF to flash, do I want to flash on 2.3.4 like I had on, or a previous version, or does it matter?
Click to expand...
Click to collapse
Problem with Droid 2 on 2.3.4, is that once on that version, you can never go back to an earlier one.
That error message you mentioned first, sounds like the error message you get when trying to flash an older SBF.
Incidentally, where did you download the CD that you tried to flash from? Was it the one linked in the first post of the thread?

bhigham said:
Problem with Droid 2 on 2.3.4, is that once on that version, you can never go back to an earlier one.
That error message you mentioned first, sounds like the error message you get when trying to flash an older SBF.
Incidentally, where did you download the CD that you tried to flash from? Was it the one linked in the first post of the thread?
Click to expand...
Click to collapse
Yes, it was in the link listed before. The method had been cross posted on this site and on their site.

Ok, above the err message, what does the top line say?

bhigham said:
Ok, above the err message, what does the top line say?
Click to expand...
Click to collapse
The only screen that I can get reads as follows:
Bootloader
D2.37
Code Corrupt
Battery OK
OK to Program
Connect USB
Data Cable
Someone suggested that by holding up and power would bypass the "code corrupt" message, but that does not work. Also, the X+Power to try and wipe the phone clean doesn't work either.

When you flash stock 2.3.4 with rsdlite, does rsdlite give you any error messages?
One of the most common errors with rsdlite is when it has the drivers for the regular bootloader mode, but not the drivers for the radio flash mode.
If this happens, you will get that code corrupt error message.
Also, what OS are you using? XP, Vista, 7, 64bit,

bhigham said:
When you flash stock 2.3.4 with rsdlite, does rsdlite give you any error messages?
One of the most common errors with rsdlite is when it has the drivers for the regular bootloader mode, but not the drivers for the radio flash mode.
If this happens, you will get that code corrupt error message.
Also, what OS are you using? XP, Vista, 7, 64bit,
Click to expand...
Click to collapse
I did get an error message when trying to flash the stock 2.3.4 and it was something to do with RAM, but unfortunately this was 5AM this morning and I was beyond exhausted so I don't remember exactly.
I am using Windows 8 x64, but have access to XP, Vista, 7, and server if I need to.

I would definitely try XP if I were you, and if you have access to another USB cable, I would try that.
To use XP, install the motorola drivers first, then use rsdlite.
I have used RSDlite 5.6 and 5.7 on my D2G, and both have worked fine with XP

bhigham said:
I would definitely try XP if I were you, and if you have access to another USB cable, I would try that.
To use XP, install the motorola drivers first, then use rsdlite.
I have used RSDlite 5.6 and 5.7 on my D2G, and both have worked fine with XP
Click to expand...
Click to collapse
Alright, I will go ahead and get XP installed along with the drivers. Do you think that I should use a version previous to 2.3.4 then so that I have a better chance to root?
I am charging up my battery now using another phone, so I will start on it in a bit. Thank you again for answering all of my stupid questions and helping me out, I really appreciate you taking the time to do it.

It would be nice if you were able to go back to an earlier version, but that isn't an option. Once on 2.3.4, no going back.

bhigham said:
It would be nice if you were able to go back to an earlier version, but that isn't an option. Once on 2.3.4, no going back.
Click to expand...
Click to collapse
So you're saying that the only thing I will be able to flash is the 2.3.4?

xwsxlogan said:
So you're saying that the only thing I will be able to flash is the 2.3.4?
Click to expand...
Click to collapse
exactly

bhigham said:
exactly
Click to expand...
Click to collapse
Alright, I will try again tonight with a charged battery and XP and let you know how it goes.

This link here http://www.google.com/url?sa=t&sour...rICoBg&usg=AFQjCNHht4SU69VoDkBnMBCA_0uf9WYpyw. Will take you to the download for the correct sbf.
Correct sbf should read: 1ff-p2a_droid2_cdma_droid2-user-2.3.4-4.5.1_57_dr4-51-120117-release-keys-signed-Verizon-US.sbf.gz
Sent from my DROID2 using Tapatalk 2

Alright Update after flashing the .sbf file that was given in the previous post.
I used XP, running RSD Lite 5.6, with Motorola drivers installed. I charged a second battery up to around 70% or so to use during the process. I also changed USB cords from the previous one that I was using. I loaded the .sbf into RSD Lite, started it, and it ran flawlessly, skipping right over the RAM step in which it failed last night. Had to remove the battery and reinstall to do the manual reboot, and all of my phone settings were exactly as I had left them when I started. I had to dial *228 +1 to get the phone back on the network, but that was no problem.
So after all of this, I'm back to where I started last night haha. Special thanks to bhigham for all of the support and walking me through this today and also slogar25 for confirming that I had downloaded the right .sbf file.
So I guess my problem is solved...until I try and root it again!

glad your phone is working again.
If you want to try to root again, you might have better luck with a freshly wiped phone, but if you prefer not to risk it, I don't blame you.
It is possible a cord issue, but just guessing here.

bhigham said:
glad your phone is working again.
If you want to try to root again, you might have better luck with a freshly wiped phone, but if you prefer not to risk it, I don't blame you.
It is possible a cord issue, but just guessing here.
Click to expand...
Click to collapse
Yep, I've noticed you have been following the cross post on this site for the methods that I tried last night when I really didn't have a clue what I was doing. Do you think that I should just try the CD method again? I mean worst case I would do the same thing I did last night, but now I know how to flash it back to the stock 2.3.4. I don't mind wiping my phone, but after it survived everything I did last night, I feel more attached to my data haha.
Also, how do I mark this post as solved?