Related
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
Deleted by user
I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse
Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App
Guess what, it works!!!
Deleted by user
Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse
I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure
Deleted by user
got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable
To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...
Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd
I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do
Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave
Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder
I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.
Long story short, I think I'm soft bricked.
I've tried wading through DG's soft brick recovery thread and ADB is just kinda beyond me.
As well, I cannot enter fast boot. I've tried holding both volume up + power and volume down + power, and both flash the white letters "Failed to boot 4" then the next line reads "Starting RSD mode"
Honestly, I'm just looking for help that I can understand, or a pretty forgiving walkthrough.
Thanks in advance to anybody who can help.
xyrovice said:
Long story short, I think I'm soft bricked.
I've tried wading through DG's soft brick recovery thread and ADB is just kinda beyond me.
As well, I cannot enter fast boot. I've tried holding both volume up + power and volume down + power, and both flash the white letters "Failed to boot 4" then the next line reads "Starting RSD mode"
Honestly, I'm just looking for help that I can understand, or a pretty forgiving walkthrough.
Thanks in advance to anybody who can help.
Click to expand...
Click to collapse
If you get the starting RSD mode you might have a chance. Put your phone back into that mode and try flash back to stock SBF using rsd lite. Follow this guide: http://forum.xda-developers.com/showthread.php?t=991072&highlight=flash+sbf
What version of software were you running before the brick? 1.26, 1.57 or 1.83? You will need RSD Lite - Download As well as the sbf for your version of software. Post back your version and I can give more guidance.
You may not need to flash all the way back to 1.26, I soft bricked today - as in can't get past the initial Moto screen with a flashing red light, and flashed 1.83 sbf.
I've actually tried to flash some of the SBFs- well, all of them, now that I think of it.
It always ends up in an error, though, and stops.
If you give me a sec, I'll try and recreate it. Off the top of my head, I remember it saying something about "Bypassing BP" or something like that.
Thanks for the fast responses. Lemme try and RSD flash here right quick.
PS (EDIT): I was on 1.5.7 running GladiAtrix 4.2.3 (if that makes any difference). I just started flashing 1.2.6 via RSD. I'll let it sit and see where it sinks.
Thanks again guys.
EDIT #2: So it gets to "Interface AP-OS: Flashing Code Group 57" - 13%, then it just chills for a few minutes, then says [Phone 0000]: Switching device to BP passthrough mode" - still at 13%, then it stops and says "Flashing Process Failed" and, if it hadn't stopped responding, it looks like it would go on to say something about "Interface A..." and the ellipses is where it's cut off. I'm sorry about that.
Any thoughts?
If you were on 1.57 I would try flashing the 1.57 SBF - this will retain a lot of your info, whereas the 1.26 will wipe your phone clean and take more work.
1.57 SBF Thread
You will need to root with gingerbreak to regain root if you flash the 1.57 SBF, Gingerbreak Thread. Make sure to copy the contents of mnt/sdcard and mnt/sdcard-ext to your computer so you can replace them after gingerbreak cleans them out.
xyrovice said:
EDIT #2: So it gets to "Interface AP-OS: Flashing Code Group 57" - 13%, then it just chills for a few minutes, then says [Phone 0000]: Switching device to BP passthrough mode" - still at 13%, then it stops and says "Flashing Process Failed" and, if it hadn't stopped responding, it looks like it would go on to say something about "Interface A..." and the ellipses is where it's cut off. I'm sorry about that.
Any thoughts?
Click to expand...
Click to collapse
Just putting that up there.
Also, I was in the process of trying to wipe my phone for a clean 1.8.3 flash, so a 1.57 flash to retain info isn't a big deal.
I went straight to 1.2.6 in the hopes that the retail version would be more likely to go through (for whatever reason).
Thanks for bearing with me.
Take out your SIM card and SD card if you have one, restart your computer and don't start any other programs besides RSD Lite to allow it the most resources (I've had it fail a few times without enough resources). Start RSD Lite and load up the SBF, turn on the phone and boot to RSD mode with the volume up button, once in RSD mode plug the phone in and start the flash. I don't know if any of this will work for sure but these are all steps to help the process.
try multiple cables, computers, OS's, and USB ports. Sometimes any combination of things helps
Got it. Rebooting now and starting nothing but RSD Lite. Also gonna change the USB port. (SIM and SD gone as of awhile ago, so no worries there. Thanks for checking though)
Well.
I. Will. Be.
I never thought I'd be happy to see that Motoblur login screen.
Phone's up and running. Looks like the reboot + USB port swap did the trick.
And you bros, no matter how simple your advice may have been, are pure gods right now.
Thank you thank you thank you a million times (little girl style- yet there is no shame in prostrating myself before you pros).
Seriously though, I owe you guys a lot. Thanks a ton.
xyrovice said:
Well.
I. Will. Be.
I never thought I'd be happy to see that Motoblur login screen.
Phone's up and running. Looks like the reboot + USB port swap did the trick.
And you bros, no matter how simple your advice may have been, are pure gods right now.
Thank you thank you thank you a million times (little girl style- yet there is no shame in prostrating myself before you pros).
Seriously though, I owe you guys a lot. Thanks a ton.
Click to expand...
Click to collapse
Glad to hear it worked for you, I know what its like to sh*t bricks over a phone snafu so congrats and welcome back to the land of the living.
Bricks? That may have happened when I flashed Adeo and got the red lights.
This time, I sh*t absolute trains.
And I'm beginning to like the Atrix more and more. I didn't lay down all that I had already done trying to recover my phone when I realized things had gone awry, but I'm sure that, on a software level, it was equivalent to repeatedly napalming a small Hawaiian tiki hut.
Thank you again, my friend. I'm almost done flashing 1.83 at this point, and I couldn't have done it without you guys.
Message to delete
I would think your problem lies in trying to flash US At&t software to your French Orange phone. Go to: http://forum.xda-developers.com/showthread.php?t=1125944 and find the French Orange firmware (there are two of them) and download them. If those don't work, try starting your own thread either here or in Q&A. Good luck!
Tim
It works
Happy
Thanks you
I am currently unable to boot into anything, no RSD, no Fastboot nothing. I try holding down up volume and down volume. Here's what it says when i try to power up.
SVF 105:1:2
Failed to boot 0x1000
Here's what i did.
I followed the steps exactly to install the stock 2.3.4 ATT update. Everything was fine. Then i decided to start over and install kennethpenn's custom rom. So i tried to flash the 1.8.3 sbf.
i foolishly started surfing other websites and didn't pay any attention to my phone. then when i looked back it was completely black screen and RSD lite said:
Failed flashing process. Failed flashing process. Phone {0000}: Error switching phone to BP Pass through mode (0x70BE); phone disconnected
Thats it. now i can't do anything. Please help.
It's called "bricked". Now search for that term and you'll find answers!
Yeah, I think you're screwed their man... Kennethpenn had the same issue with his Atrix I think.... $600 brick
doesnt sound good...
where in the process exactly did you decide to start over and install kenneths custom rom?
i know its bricked. i'm just wondering how bricked...
i was in the process of starting over to install kennethpenn's ROM. i was flashing the full 1.8.3 sbf.
do you think ATT will take it back under warranty if i play dumb?
b3nman said:
i know its bricked. i'm just wondering how bricked...
i was in the process of starting over to install kennethpenn's ROM. i was flashing the full 1.8.3 sbf.
do you think ATT will take it back under warranty if i play dumb?
Click to expand...
Click to collapse
Well you got nothing to lose.
i
i have the same problem gonna play dumb and get a new one today under warranty
yokozuna82 said:
i have the same problem gonna play dumb and get a new one today under warranty
Click to expand...
Click to collapse
Nice. Tell us how it works out, good luck!
yokozuna82 said:
i have the same problem gonna play dumb and get a new one today under warranty
Click to expand...
Click to collapse
What did you do to cause it? Same thing as OP?
I'm tellin ya I think there is something wrong with that damn 1.83 sbf itself! The older ones never had any problems! I'm done with it!
LayzeeEyez said:
What did you do to cause it? Same thing as OP?
Click to expand...
Click to collapse
yeah, has anyone else tried to flash back to 1.83?
b3nman said:
i know its bricked. i'm just wondering how bricked...
Click to expand...
Click to collapse
If it does not go to the moto logo screen that means something messed up your IPL/Bootloader, which means you are pretty screwed.
b3nman said:
i was in the process of starting over to install kennethpenn's ROM. i was flashing the full 1.8.3 sbf.
do you think ATT will take it back under warranty if i play dumb?
Click to expand...
Click to collapse
You could just say that you never got around to updating to 1.8.3 (kind of a long shot since it reminds you every hour), and when you installed the update it would not restart. If you have a backup phone, you could just wait till the new update releases and use the same excuse.
If you hard bricked, there is most likely no way they can check if you were messing around with anything. It is worth a shot, but like you said just play dumb
http://forum.xda-developers.com/showthread.php?t=1160408 <- For future reference
im sorry this happend to you guys, i hope everything goes well with insurance and what not. i made a warning on the guide for people not to flash back until a safe method is found!
i had ur problem a few seconds ago!
rsd stoped at " switching phone to BP Pass through mode " at 33%.
and after a hour nothing happend!
i decided to disconnect the phone but after that i lost RSD,fastboot,.....
i removed the battery for a while and after that i powerd the phone up but it was the same as before.
i left it on moto red logo and after a few second it said:
failed to boot 4
starting RSD mode
and now its working!
but i didnt get " Failed flashing process " like you!
i got one coming through warranty be here no later then tuesday
i guess i didn't understand the warnings. now i see them, only too late. it seems like att will send me a new one.
b3nman said:
i guess i didn't understand the warnings. now i see them, only too late. it seems like att will send me a new one.
Click to expand...
Click to collapse
anyone have a cwm backup pre 2.3.4 they can try?
att is sending a new one. it was easy since i'm still within the 30 days of opening my account. lesson learned:
THOROUGHLY READ ALL WARNINGS!!! I hope my fail can prevent others from going through it. THANKS EVERYONE!
is this 4.5.91 specific? I flashed between 4.5.40 and 1.83 sbf a few times without problem.
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?