Database Users

[Q] Unable to finish flashing phone

Okay, so here is what happened:
I got a Droid 2, and I am almost positive I had the latest OTA. I was trying to flash the Fussion rom, but some how ended up with two rom managers. Anyways, I tried to reset my phone to complete stock, because I want a clean start to install a rom from.
I read the tutorial, but when I got to the part when I am supposed to flash "BL_D235...HSPart.sbf", the Start button is grayed out.
I'm guessing that trying to install 2.2.20 over 2.3.20 has caused some issues. I tried to flash the .spb I found of 2.3.20, but I get an error, "Failed flashing process. Failed flashing process. (0x7100); phone connected."
My phone is currently stuck at the default bootloader I believe. Black screen that says:
Bootloader
D2.37
Err:A6,70,70,00,1F
MEM_MAP Blank
Service Req'd
...
If I pull the battery and restart, I come right back to that screen.
Am I stuck, unable to finish flashing 2.2.20, but unable to flash 2.3.20?
Any help is greatly appreciated, my phone is just an over priced paper weight right now. Thanks a lot.

rhannahs19 said:
I got a Droid 2, and I am almost positive I had the latest OTA. I was trying to flash the Fission rom, but some how ended up with two rom managers.
I'm guessing that trying to install 2.2.20 over 2.3.20 has caused some issues. I tried to flash the .sbf I found of 2.3.20, but I get an error, "Failed flashing process. Failed flashing process. (0x7100); phone connected."
If I pull the battery and restart, I come right back to that screen.
Am I stuck, unable to finish flashing 2.2.20, but unable to flash 2.3.20?
Click to expand...
Click to collapse
There should be no problem flashing an SBF of 2.3.2 over 2.2.0 I did it and I didn't have any trouble at all. You just can't flash 2.3.2 over 2.2.0 because the bootloader changed and won't accept the old SBF.
If you are having trouble flashing the SBF in windows then try it with THIS method. Make sure you download the SBF I provided in the tutorial because the one you have might be corrupt or not complete.
It's not a good idea to use ROM manager's for the D2 just yet afaik. If you don't have koush's bootstrap for the D2 than you are missing a vital piece of software for backing up and restoring your phone. If you came from the D1 forget (almost) everything you know. The D2 doesn't have an unlocked bootloader and thus has to be bootstrapped in order to work around this fact.
ROM managers might be useful for downloading but if you are going to install a ROM on the D2 I'd stick with Koush's bootstrapped clockwork recovery. I've never downloaded or even seen a ROM manager so if my info on them is completely wrong please correct me. But I have flashed plenty of ROMs on my D2 via koush's bootstrap and I have SBF'd about twice using linux and it's been easy sailing and I've never had any big problems.
Sorry if I'm rambling it's almost 2 in the morning and I have to be up for class at 8.

thanks, maybe its not a rom manager, but i installed clockworkmod, i guess maybe thats another bootstrap loader? i was very good at flashing winmo roms, this is a whole new game

newk8600 said:
There should be no problem flashing an SBF of 2.3.2 over 2.2.0 I did it and I didn't have any trouble at all. You just can't flash 2.3.2 over 2.2.0
Click to expand...
Click to collapse
You mean you cant flash 2.2.0 over 2.3.2 right?

burkechrs1 said:
You mean you cant flash 2.2.0 over 2.3.2 right?
Click to expand...
Click to collapse
Yes sorry I reread my post but I didn't catch that. You can't flash 2.2.0 after flashing 2.3.20 correct.

S.O.S. I may have just created a really expensive paper weight

I was flashing the 2.3.340 sbf to go to gingerbread. I was to flashing the RAM at 99% done and it froze there for a while then it failed. Now I can't get it to work.
Now my Bootloader says
Code Corrupt
ANY help or ideas are welcome. But as of now I'm in the market for a new phone....
EDIT: Holy Crap. Persistence may have just paid off...Yup sure did. the only change I made was a few battery pulls in between and added a p to end of file name.

Reflash it I have to do it 3 or 4 times before it will actually pass. If it still fails try to do it on another OS.

Yeah, it can take a couple tries, although generally it's a one shot deal for me. Are you sure you were using the full sbf and not the system only sbf?
Sent from my DROIDX using XDA Premium App

I had the same issue. I was on GB and trying to go back to froyo to get the rooted GB. After 3 unsuccessful tries with the full SBF the system only SBF did the trick.

I has that happen
Make darn sure your battery has a good charge if you try flashing with a low battery it will boink the phone. I had to call VZW and get a new one, had no way of charging the battery, it will only charge if there is an OS present on the phone. Once I got a new phone charged the battery and flashed both.

If flashing through RSD does not work successfully (make sure you have 4.9) then the alternative process I sometimes have to do is through command prompt and manually flash the. Sbf. For various reasons, Rsd lite not recognzing the sbf, failed to re-enumerate....Soo
If your on a windows 7 machine I've had success with this
Flash. .sbf through command prompt in Windows 7

[Q] Did I brick my phone? Liberty GB Leak, lost recovery mode somehow, had to SBF...

I was on Liberty GB v0.3.
So after installing a ROM via flashing with clockwork recovery (DSPmanager specifically, didn't work obviously). When I rebooted, I got stuck in a boot loop, nothing special... problem was I couldn't even get into recovery, no matter what I tried. The only thing I could get to was the bootloader, so I SBF'd to full 2.3.340. Didn't work. Tried flashing 2.3.340 system only, also didn't work.
This is the bootloader error:
Code:
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
...
How screwed am I? Is there any way I can fix this?

Are you using a Windows' machine to SBF the phone, via RSD Lite? If so, try using a Linux (Ubuntu) machine to SBF your phone. I got an error message myself while trying to SBF my phone on a Windows 7 machine. Tried updating drivers like 7 times to no avail. However, when I SBF'd using Ubuntu, BAM!, no issues. Here's a video to help you out.
http://www.youtube.com/watch?v=jswEsHJ8GdU

theres almost no way you can actually brick a dx since we cant flash radios or kernals, but only "soft" brick. nothing a sbf cant fix, but as the post above suggests try it on ubuntu, its so easy to get

I've gotten that error a few times using Win7 as well. I just unplug the usb and try again, usually the second or third try works fine for me.

That error occurred when I flashed an older system version. Redownload the file and make sure it is for bootloader 30.04

I have SBFed using a Linux machine before, but don't have one handy. Is is possible to SBF from Ubuntu if I just boot the OS off a disc or do I need to do a full install of the OS?

[Q] Milestone 2 in bootloop

Hey all there,
i just bought for some cheap money a milestone 2 on the bay with bootloop problems.
it startsup like this:
just power on with the power button:
red m logo, after some seconds it turns for about a half second to a black screen, again red m logo, and again and again and again
enter the bootloader works fine - 70.13
enter the system recovery works on charger, wiping out didn't help
flashing with rsd lite worked, but didn't change the situation with the bootloop. even after flashing, and wipe out after that.
i'm using windows 7 32bit and x64 on another computer in combination with rsd-lite 5.6
with rsd-lite 4.9 or earlier my device isn't recognized. admin and compitibility is on at all versions of rsd-lite.
anone an idea how to get this stone working again?
i'm a little confused, cause i saw so many posts, of people getting the stone back after flashing with rsd...hmm any help is pleased
greetz

Download rom GingerBread of UK
http://www.multiupload.com/TUZHXCGLMZ
Flash with RSD Lite 5.6... reboot
make wipes (POWER and X....... Vol + and Vol -)... reboot
has to boot normally ...

Just tried several versions of firmware. nothing did work.
i'm thinking about getting the 70.13 bootloader file and flash the bootloader once more.
or give it a try and flash the phone with an update.zip over recovery mode.
but first problem is: i don't have the booloader and the only mirror was megaload, at second i don't have any oem update.zip files. well i will look forward. can't understand why the phone is still looping.
would be happy about any other good suggestions.
greetz

Bootloader 70.13

thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz

MKSilver said:
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
Click to expand...
Click to collapse
Don't use a 2 ou 2.2 android..I think it's on GB so you can't downgrade..
Charge your battery to 100%
Folow the step here with a 2.3.4 SBF take here
Have a nice day.

Hey all there,
i already tried to flash GB 2.3.4 Firmware for: Germany, DACH, UK - didn't work out.
of course i did a wipe after installing.
also i tried a rebuilt by renaming CG66.img into CG37img - didn't work out.
just saw, that when i rebuilt the firmware after changing cg66.img to cg37.img, the cg37.img file doesn't appear in the new built SBF.
any reason for that? hmm...
while depacking and rebuilt a SBF i saw, that the RAMDLD.img (ramdownloader) in the 2.3.4 GB DE retail SBF is in version 70.12. i'm no expert in built SBF files, just did this the first time, but could this have an incompatibility with the 70.13 bootloader?
well cause the phone was quite cheap, i will go on trying. may be some more of you guys have any ideas.
the standing now is:
reflash 70.13 bootloader - didn't work out,
flash any 2.3.4 GB SBF and wiping out data after flash - didn't work out
flash update.zip from recovery mode - haven't tried yet - need update.zip file or instruction how to built one.
the last point is my next step i think. i will now go reading how to get this manage.
any help is welcome!
greetz

Okay just learned, that flashing an update.zip with system recovery, doesn't erase any data on the phone, so will look forward, trying flash the phone with sbf under linux live cd.
may be this will help.
does anyone of you know some hardware testing tools for the milestone 2?
to test the ram/rom hardware...
i'm starting to think, that some of the hardware chips may be damaged.
hmm i always thought, that it is not possible to brick a stone with original bootloader/rom-image/firmware. just starting to learn, that it is possible although.
any help is welcome guys! my ideas are going to end.
greetz

Got still no luck and tried to flash it with sfb about 16 times now. RSD-Lite tells me it was everything okay, but still bootloop.
Any good ideas?
Greetz

You have no real idea of the phones history, so you may have to accept the possibilty that it could be a hardware issue. Perhaps it has taken some water damage (the indicators do not always end up going off btw - I fell into a pool fully clothed and the nokia i had at the time wouldn't ever recognize a sim again, yet no water damage indicators get wet somehow . Yet the rest was soaking)
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
A thought occurs.... does it actually have a sim card slot? Like... is it possibly a Droid 2? :S
---------- Post added at 10:25 AM ---------- Previous post was at 10:20 AM ----------
Mikevhl said:
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file
Click to expand...
Click to collapse
Got that from the recovery thread.
I dug up this guide to using ubuntu live cd to flash sbf's for the droid 2, hopefully you are switched on enough to workout what you need to do differently for the MS2
http://forum.xda-developers.com/showthread.php?t=804088
I'd try that and see what happen

Hey guys,
first: thx to DreadPirateDan. you're right, i don't know enough about the phone. So i sat down after work and startet to read and with all the basic information i know about the phone. While analysing all the things i just saw a special thing in the bootloader:
When the phone is switched on into bootloader, the screen shows:
"Bootloader Fastboot mode
70.13
Battery OK
OK to Program
Transfer Mode:
USB"
So it seems that i've got the fastboot script active. So i should do everything with the phone i want to do, right?
i will go on reading. maybe i will find any way to check all the files.
Is it possible, that the phone loops because of fastboot mode and a secret saftyissue which bans all phones booting with active fastboot?
May any of u check on a not rooted and for difference rooted milestone 2, if the fastboot notify is standard?
Btw - got a Sim-Slot, so it seems to be a Milestone 2.
greetz

This ones a long shot - but if you have another USB cable available, try using that. Perhaps the one you are using is somewhat damaged - not enough to cause errors flashing, but enough to corrupt data? I don't know but i'd certainly give it a try! .
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
Yeah that's the screen of bootloader saying it's all sweet to flash with rsd-lite
So that's a good sign
I'm concerned perhaps it's had some physical damage to the system storage.
I'm just confused, your steps appear to be all correct, what you've done allready, and it should have worked allready!

How did u get into Bootloader Fastboot mode???
Are you sure it says 'Fastboot' coz Fastboot could mean unlockable bootloader?
May be some developer could throw some more light on this.

When we first got the Chinese GB link I remember there were a couple of guys who had deceloper phones.. They never explained how they'd got them though lol
Sent from my MotoA953 using xda premium

Fastboot confirmed
Hey Guys,
well its definitly Fastboot. I installed Android SDK yesterday and tested a little bit.
I can flash images through fastboot and all those things.
Poblem is, i'm not so familiar with all those things. I know a little bit of electronics but not so much about how software and specially android works with the hardware. Just started yesterday to read about this.
Attached are some pics of my phone during bootloader and how it looks.
Now it would be first nice, to get this thing work!
Because at the moment it hangs still during booting, cause i don't know so much about how to flash from fastboot.
When it is true, that this could help this forum here, i won't sell it anymore. But i need help to work all this out.
I contated parallely the customer service of motorola at my country, to ask, if this device has still waranty via IMEI, but they don't have this IMEI in their database.
So come on guys, more information, how get the phone work again, may be with any rom we wish someday without hacking anything
greetz

I have the same problem. tried to bootstrap after ive installed cyanogen 7 and now im stuck on the M logo. wiping cache or factory reset won't work
thing is the links for sbf files at and-developers won't work :\ so now i cant flash anything
plz help

Alot of file sharing stuff got shut down just recently that's why all the links are dead
if you had previously upgraded to gingerbread, that is your problem - cm7 doesn't work with it. Have a crack at the dowgrade method endless7 has and then you can flash cm7 with CWM.

ok, i figured it out. just searched google for one of the builds. flashed it and it turned out to be a french retail version of froyo. installed MIUI rom. works fine

I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.

Nikunj3xP said:
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Click to expand...
Click to collapse
hi,
Can you please explain clearly if you are able to boot CWM recovery or are you just getting a boot loop and unable to boot to recovery? As far as I know you won't be able to flash clockwork mod recovery for the Milestone 2 using ROMManager .You need to use Droid 2 bootstrap recovery.

Need bootloader .sbf so I can clear cache

I think I flashed the wrong bootloader and messed everything up.
Phone has been bricked for about a week now.
Been doing research and tried a lot of .sbf's.
Nothing is working.
I think I need to clear my cache and/or wipe data, factory reset.
However I cannot get into stock recovery, just goes straight into bootloader.
This is the bootloader error code.
Bootloader
D2.35
Err:A5,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to program
Tranfer Mode: USB
I was on Gingerbread.
Flashing
sbf 1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keys-signed-Verizon-US.sbf.gz
doesn't work.
The only links that were good and I can use for reference are these, which are down.
http://and-developers.com/sbf:droid2
http://forum.xda-developers.com/showpost.php?p=9445568&postcount=2
Can someone help me out?
Also this should be included in the Recover Droid 2 sticky
Thanks in advance.

Have you tried using a newer version of rsdlite? I used to get all kinds of ****ty errors using the older version of rsdlite 4.8 then i tried the newer 5.6 and everything worked perfectly every time.

[1up] said:
Have you tried using a newer version of rsdlite? I used to get all kinds of ****ty errors using the older version of rsdlite 4.8 then i tried the newer 5.6 and everything worked perfectly every time.
Click to expand...
Click to collapse
I'm using 5.6
Even tried running RSD with admin rights.
No go. =/
Like I said, I think I need to clear my cache and factory erase
and perhaps try another .sbf

or go ezSBF iso file burn to disc or usb drive
boots to linux, http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html

sd_shadow said:
or go ezSBF iso file burn to disc or usb drive
boots to linux, http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html
Click to expand...
Click to collapse
I tried one linux disk and it didn't work.
I forgot what version.
I'll give this link a shot later today.
Thank you

I didn't realize you had a thread going in the general section.
I managed to find a copy of the 2.37 bootloader sbf.
It was a pain. Google translate got it's workout, thank goodness I didn't have to register on a forum in a language I can't read/understand.
Here it is:
BL_D237_cdma_droid2_Consumer_replacer_HSPart.zip
Hope this works.

newk8600 said:
I didn't realize you had a thread going in the general section.
I managed to find a copy of the 2.37 bootloader sbf.
It was a pain. Google translate got it's workout, thank goodness I didn't have to register on a forum in a language I can't read/understand.
Here it is:
BL_D237_cdma_droid2_Consumer_replacer_HSPart.zip
Hope this works.
Click to expand...
Click to collapse
I just tried this and i'm still left with the same error.
I cannot get into the stock recovery.
I think I need to get into the recovery so I can wipe the cache and clear data.
Then hopefully a .sbf will stick.

the stubborn 2.3.4
I was on 2.3.4 and got the same error when I tried flashing to 2.3.3
2.3.4 is currently still locked up tight and wont allow backwards flashing. I ended up flashing back to 2.3.4 and everything worked out fine, except the fact that i can't even root, of course.