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.
Does anyone have an sbf for the R2D2 Edition? I got a little too tweaky.
Thanks!
Lol.. not yet.. next time boostrap and make a back up
See if you can recover with the r2d2 rom from mydroidworld
http://www.4shared.com/file/rePStgcF/VZW_24_Full_ROM.html
I've got a nandroid backup on my SD card I jsut can't seem to get back to the bootstrapper.
Try booting up and then pull your battery and then try booting up again. See if that puts you into bootstrap.
Sent from my R2-D2 using XDA App
Thanks for the advice, I've been yanking the batt, pressing volume buttons and everything the only thing I can get to is the stock reset screen (android with !) and the boot loader. At this point I've probably done more harm than good resetting memory and clearing cache and stuff.
Oh, in case anyone wondered, the sbf fro the regular Droid 2 does not work on this bad boy. That'll teach me to mess wiht things I don;t know about. Looks like what I have is Bootloader and a copy of my backup from clockworkmod.... is there a way to build an sbf from your .img files?
Try powering down the phone then plugging it in and boot it up. That often loads clockwork revovery on mine.
Try going back into bootstrap recovery and pushing the bootstrap recovery button again. Then the reboot recovery button. That should work. I had the same thing happen to me and that worked.
Sent from my DROID2 using Tapatalk
hyatari said:
Try powering down the phone then plugging it in and boot it up. That often loads clockwork revovery on mine.
Click to expand...
Click to collapse
Yeah, for whatever reason that often does cause my d2 to boot into cwm.. I think it replaces that weird battery startup thing, did anyone else get that when they first used their d2?
Sent from my DROID2 using XDA App
rexit1982 said:
Thanks for the advice, I've been yanking the batt, pressing volume buttons and everything the only thing I can get to is the stock reset screen (android with !) and the boot loader. At this point I've probably done more harm than good resetting memory and clearing cache and stuff.
Click to expand...
Click to collapse
If your D2 won't boot all the way up (which is what it sounds like), you may be able to get into CW Recovery by one of the methods below:
1. This is the most reliable way I've found: Boot up and pull battery when the boot animation starts (after the M logo disappears). Then reinsert battery and start up...should go to CW Recovery then. Thought I spell it out just in case you hadn't tried it that way specifically.
2. Make sure there is no 'update.zip' file in the root of your SD card - again make sure NO 'update.zip' file. Then boot into stock recovery, choose the apply update.zip option, and after it aborts, pull the battery and boot up again.
3. Another set of steps that might work:
-Boot into stock recovery by holding X while powering up
-Hit the magnifying glass on the keyboard to open recovery menu
-Highlight reboot and hit "ok" on the keyboard
-When you get the "M" screen pull the battery
-Power back up and it will go to Clockwork recovery
Good luck on that....
rexit1982 said:
Oh, in case anyone wondered, the sbf fro the regular Droid 2 does not work on this bad boy. That'll teach me to mess wiht things I don;t know about. Looks like what I have is Bootloader and a copy of my backup from clockworkmod.... is there a way to build an sbf from your .img files?
Click to expand...
Click to collapse
What makes you say that...what did you try and what happened? What version of RSD Lite did you use, and what was the failure/results, etc. This is a pretty surprising thing to hear.
R2D2 and D2 are the same HW as far as anyone has seen from specs, etc., the 2.2.20 SBF not working seems odd.
Thanks.
I used RSDlite 4.7. the flash get tot he reboot point and then a bootloader error thaT said "bootloader err:A5,70,70,00,1f".
rexit1982 said:
I used RSDlite 4.7. the flash get tot he reboot point and then a bootloader error thaT said "bootloader err:A5,70,70,00,1f".
Click to expand...
Click to collapse
You're two versions behind...RSD Lite 4.8 and 4.9 are out. I'd suggest you get at least 4.8 and try again. I don't have the links, but should be google-able.
When you used 4.7 you added the RSD patch on top of RSD 4.7 after you installed it, right?
What does the phone do now when you boot it up? Just sit on M logo, get to boot animation, or ?
Redflea said:
You're two versions behind...RSD Lite 4.8 and 4.9 are out. I'd suggest you get at least 4.8 and try again. I don't have the links, but should be google-able.
When you used 4.7 you added the RSD patch on top of RSD 4.7 after you installed it, right?
What does the phone do now when you boot it up? Just sit on M logo, get to boot animation, or ?
Click to expand...
Click to collapse
Yes I did drop the patch on. The phone goes straight to a black screen with white writing that says
Bootloader
D2.35##
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
##Updated code
I googled the error, I found this was the same error that DroidX users who OTA'd to their 2.2 update and then tried to SBF back to 2.1.
I have a new device now but I am keeping hold of the old one for the next couple days to try anything anyone ahs any ideas on. When I get to my other phoe I'll try a new rdslite.
If you don't have a linux computer I'm working on a livecd with adb and the sbf_flash script so that anybody with a computer can flash there phone in linux. I have one version so far but I'm trying to cut down the size because it's too big for a CD.
newk8600 said:
If you don't have a linux computer I'm working on a livecd with adb and the sbf_flash script so that anybody with a computer can flash there phone in linux. I have one version so far but I'm trying to cut down the size because it's too big for a CD.
Click to expand...
Click to collapse
Sounds like a good project...
rexit1982 said:
Yes I did drop the patch on. The phone goes straight to a black screen with white writing that says
Bootloader
30.03**********
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
***I am not sure if these were the same numbers but the rest of the message is exact match
I googled the error, I found this was the same error that DroidX users who OTA'd to their 2.2 update and then tried to SBF back to 2.1.
I have a new device now but I am keeping hold of the old one for the next couple days to try anything anyone ahs any ideas on. When I get to my other phoe I'll try a new rdslite.
Click to expand...
Click to collapse
You mean you're going to try the newer RSD Lite on the new phone or the old phone?
Interesting that it's the same error the Droid X users were getting...that does change the game a little, doesn't it. Thanks for the additional information - a relevant "news" post is here:
http://www.mydroidworld.com/forums/...-1-any-reason-after-official-upgrade-2-2.html
So it seems like VZW may have made the same change to the bootloader w/2.4.x on the D2 that they made w/2.2 on the DX.
Redflea said:
You mean you're going to try the newer RSD Lite on the new phone or the old phone?
Interesting that it's the same error the Droid X users were getting...that does change the game a little, doesn't it. Thanks for the additional information - a relevant "news" post is here:
http://www.mydroidworld.com/forums/...-1-any-reason-after-official-upgrade-2-2.html
So it seems like VZW may have made the same change to the bootloader w/2.4.x on the D2 that they made w/2.2 on the DX.
Click to expand...
Click to collapse
I am running RDS lite 4.9 against my "old" device right now. I'll let you know how it works out. What is the current official SW version on the D2?
The VERY first time I tried this I did get a success message when it was done
I get an error now, Error sending RAM download to bootloader ... I am trying to attach pictures of the full message.
Actually, the mem_map blank and the bootloader messages are pretty common across all motorola phones, I've seen similar error messages on the older p2k (v300, razr, etc) type phones when you have a flash fail out at certain points. It's generally recoverable (in most cases, anyway) as long as you have a full flash (.sbf or .shx)
rexit1982 said:
I am running RDS lite 4.9 against my "old" device right now. I'll let you know how it works out. What is the current official SW version on the D2?
The VERY first time I tried this I did get a success message when it was done
I get an error now, Error sending RAM download to bootloader ... I am trying to attach pictures of the full message.
Click to expand...
Click to collapse
For the D2 (non-R2D2) it's 2.2.20, which is what the avaialable D2 SBF is...
bladearronwey said:
Actually, the mem_map blank and the bootloader messages are pretty common across all motorola phones, I've seen similar error messages on the older p2k (v300, razr, etc) type phones when you have a flash fail out at certain points. It's generally recoverable (in most cases, anyway) as long as you have a full flash (.sbf or .shx)
Click to expand...
Click to collapse
Thanks...
I believe I've also seen some comments that when flashing via a Windows box fails, that trying from a Linux setup can be more likely to be successful, but don't remember the details, so I may be garbling that info...
newk8600 said:
If you don't have a linux computer I'm working on a livecd with adb and the sbf_flash script so that anybody with a computer can flash there phone in linux. I have one version so far but I'm trying to cut down the size because it's too big for a CD.
Click to expand...
Click to collapse
Please let me know when you have this livecd available. I too had the same response on my Droid 2. I wound up having to buy a new D2, but I'm still holding onto my old one...hoping one day I might be able to revive ut. LOL
Sent from my DROID2 using XDA App
Hey Guys,
I need some help! I used RSD lite 4.8 and the new sbf (2.3.15) and I get all the way to the end and then it fails....Here is the error log:
Failed flashing process. Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x18F000 Command ADDR (0xE0231009); phone connected.
Any ideas?
I am using the OTA 2.2 update and was rooted using BigDX theme.
I have tried the sbf 2x, and both times, would up in the same spot...
When the phone reboots, I have all my contacts and apps...
The reason I wanted to use the sbf is gmail keeps force closing so I'm not getting my emails over push...
So you didnt do a nandroid backup before you installed themes/roms?
I know this is a stupid question so sorry in advance- did you enable USB debugging on your phone? If so- have you tried it in different modes? Media Sync or USB mass storage?
I have heard reports of having to be in a different mode.
And you are sure it was the new sbf...
VRZ_MB810_2.3.15_1FF_01
Not the system sbf...
SHADO_X6_2.3.13_SYSTEM-ONLY
thepolishguy said:
I know this is a stupid question so sorry in advance- did you enable USB debugging on your phone? If so- have you tried it in different modes? Media Sync or USB mass storage?
I have heard reports of having to be in a different mode.
And you are sure it was the new sbf...
VRZ_MB810_2.3.15_1FF_01
Not the system sbf...
SHADO_X6_2.3.13_SYSTEM-ONLY
Click to expand...
Click to collapse
To SysadmNJ,
Yes I did a nandroid backup, so I have a place to go back to...but gmail was still force closed... So that is why I wanted to do the SBF.
Polishguy,
yes I have USB debugging enabled, and had thrown the phone in PC mode so it was detected. I'm stumped as to why it is failing at the end. Yes, I grabbed the SBF from rootz wiki. Would like to have a full SBF work so I can get the gmail service working again.
did you place the patch in rsd lite folder?
mob87 said:
did you place the patch in rsd lite folder?
Click to expand...
Click to collapse
Yes, the patched pst_flash.ini file?
Is there a new one for RSD 4.8?
Just trying to figure out what else might be going wrong...
there isnt a new one just wanted to make sure. maybe you got a bad download of the sbf.
mob87 said:
there isnt a new one just wanted to make sure. maybe you got a bad download of the sbf.
Click to expand...
Click to collapse
Tried the original that was hosted here before it got pulled by the mods, and also grabbed the one from rootz wiki as well. Got the same result with both. I will try putting the phone in charge only mode as well as media sync mode later and retry the sbf.
If anyone has done this successfully, can you please list the steps you took?
Thanks
SysAdmin-X said:
Tried the original that was hosted here before it got pulled by the mods, and also grabbed the one from rootz wiki as well. Got the same result with both. I will try putting the phone in charge only mode as well as media sync mode later and retry the sbf.
If anyone has done this successfully, can you please list the steps you took?
Thanks
Click to expand...
Click to collapse
You are suppose to be in bootloader when you flash the sbf.
mob87 said:
You are suppose to be in bootloader when you flash the sbf.
Click to expand...
Click to collapse
Ok. Will give this a try. I read you could do it with the phone on or off.... That it would put the phone into bootloader...which it looks like it did.
I will try putting it into bootloader prior to running the sbf.
EDIT:
I put the phone into bootloader mode, and have run the sbf 2 more times...still with the same error. Just wind up with different values on the error codes....
Yes holding the volume down, camera, and power button for a few seconds will make the screen flash then release the buttons and you will be in bootloader mode.
Sent from my DROIDX using XDA App
Try a different USB port or even a different PC.
Have tried the above suggestions.... I noticced each time it would make it slightly farther (or so it seemed) that there were device druvers being installed along the way.
Anyone have the driver p package they used if they got the sbf to work?
I'm using the 4.7 drivers
Sent from my DROIDX using XDA App
I recently got the same error message, I asked a few developers and P3 told me its the radio that is not being changed. he said it is not a problem unless you are not happy with the radio. This was about a week agao and i have been flashing Rom's/Themes all week and my phone is running great. I wouldn't worry much about it.
Just an FYI I am on the leak and used the first sbf.
FSRBIKER said:
I recently got the same error message, I asked a few developers and P3 told me its the radio that is not being changed. he said it is not a problem unless you are not happy with the radio. This was about a week agao and i have been flashing Rom's/Themes all week and my phone is running great. I wouldn't worry much about it.
Just an FYI I am on the leak and used the first sbf.
Click to expand...
Click to collapse
Hm...interesting. So the radio doesn't really matter unless its already messed up... I guess I should have thought of that...
ON ur x, it does look like everything else is back to stock tho?
did you do a battery pull ; and/or clear data/cache and do a factory reset after the process seemingly completes (never mind the error) - coz I got some error when I tried flashing using sbf - but I was on the 1st leak - and used the original (2.1) sbf - rsdlite said 100% - but error - mentioned somethin abt bootloader - I did a battery pull - phone went into loop of death - I cleared data/cache and also did a factory reset by going into recovery - and my phone was as good as new... just a thought..
EDIT: Actually, all your questions seem to be answered in the other thread in this very forum by name " Droid X Full SBF Release" posted by catalystsupreme2 - read through all the posts - esp. abt the radio etc which someone here also mentioned in this thread
chiaroscuro7 said:
did you do a battery pull ; and/or clear data/cache and do a factory reset after the process seemingly completes (never mind the error) - coz I got some error when I tried flashing using sbf - but I was on the 1st leak - and used the original (2.1) sbf - rsdlite said 100% - but error - mentioned somethin abt bootloader - I did a battery pull - phone went into loop of death - I cleared data/cache and also did a factory reset by going into recovery - and my phone was as good as new... just a thought..
EDIT: Actually, all your questions seem to be answered in the other thread in this very forum by name " Droid X Full SBF Release" posted by catalystsupreme2 - read through all the posts - esp. abt the radio etc which someone here also mentioned in this thread
Click to expand...
Click to collapse
I read through this, and I haven't done the battery pull, or clear..... trying to avoid it if possible...but will if needed.
As for the answer about the BP, it didn't seem like the post really answered the question per say...just gave an explanation about it overall
thank you for the help
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
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?