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.

[Q] Q> How to install Argen2Stone?

ive tried to install the Argen2Stone 2.7RE on my milestone 2 UK retail running on stock GB 2.3.4!
the funny thing is it always end up on black screen after i restore the argen2stone nandroid and applying the FixedSBF before rebooting my MS2.. i cant access the recovery because after the red motorola logo its already black screen.
Did i do something wrong about it? in the thread of Argen2Stone it say its for any ROM so assuming it should work on UK GB stock!.. Hope anyone can help thanks!
Edit: Got it working using the fixed SBF provided by endless7 CM7.. the thing is the FixedSBF.zip provided in argen2stone is not compatible with UK GB 2.3.4 so after i installed the argen2stone 2.7RE, reboot and gone on a black screen then flashed the fixedSBF using RSD lite then recovery, factory reset..

try entering motorola recovery by holding x when powering on. If it will let you get that far, do factory reset from there an see how that goes. Also make sure you are trying to flash the right sbf, because even group users have to flash a fixed sbf. So you didn't recesarily flash the right one just cause you flashed one
I cant be screwed to find the direct link now as I‘m on my tablet, so please refer to my guide here: http://forum.xda-developers.com/showthread.php?t=1464507
Around halfway down you will find a section titled install instructions (gingerbread users). There I have the correct link for the fixed sbf you need (this one needs to be flashed with rsd lite btw)
Edit: now that I think about it, your mistake was flashing the fixed sbf. All it does is chanew your kernel, and you were already on the one you needed. So flashing the sbf changed it to a kernel no longer compatible with your phone since you updated to 2.3.6 (non downgradable).
Flashing the sbf I'm referring to earlier should fix you up

DreadPirateDan said:
try entering motorola recovery by holding x when powering on. If it will let you get that far, do factory reset from there an see how that goes. Also make sure you are trying to flash the right sbf, because even group users have to flash a fixed sbf. So you didn't recesarily flash the right one just cause you flashed one
I cant be screwed to find the direct link now as I‘m on my tablet, so please refer to my guide here: http://forum.xda-developers.com/showthread.php?t=1464507
Around halfway down you will find a section titled install instructions (gingerbread users). There I have the correct link for the fixed sbf you need (this one needs to be flashed with rsd lite btw)
Edit: now that I think about it, your mistake was flashing the fixed sbf. All it does is chanew your kernel, and you were already on the one you needed. So flashing the sbf changed it to a kernel no longer compatible with your phone since you updated to 2.3.6 (non downgradable).
Flashing the sbf I'm referring to earlier should fix you up
Click to expand...
Click to collapse
thanks for the reply.. well even the stock recovery is not accessible the option i did was reflash all over again.. thankfully i got it working using fixedSBF from endless7 CM7.
Edit: revert back to stock GB rom.. this rom eats up too much RAM >.<...
in stock rom i can manage a 220mb free ram on standby but this rom when on standby for too long manage 175-185mb free rom.. maybe ill try CM9 next!

hi guys, someone could use the FMRadio??

americogiovani said:
hi guys, someone could use the FMRadio??
Click to expand...
Click to collapse
Unfortunately, it's not possible to use the FM radio in our Milestone 2, no matter with which app and rom.

[Q] Am i Bricked?

got an error while flashing atrix 2.3.4 stock to 2.3.6 using RSD lite, can anyone help me getting out of this? will be much appericiated tnx in advance
error is:
failed to boot 4
starting rsd mode

soft brick, you can still get your phone working. there's various threads around here with instructions on how to bring your phone back to life...easier if you have a locked bootloader vs unlocked bootloader. To get help from others it would be good if you posted the state of your phone prior to flashing it:
1) locked or unlocked bootloader
2) rooted or not
3) ROMs installed?
4) exactly what were you trying to do? i.e. links to the files you were trying to flash, which version of RSDlite, etc.

gnahc79 said:
soft brick, you can still get your phone working. there's various threads around here with instructions on how to bring your phone back to life...easier if you have a locked bootloader vs unlocked bootloader. To get help from others it would be good if you posted the state of your phone prior to flashing it:
1) locked or unlocked bootloader
2) rooted or not
3) ROMs installed?
4) exactly what were you trying to do? i.e. links to the files you were trying to flash, which version of RSDlite, etc.
Click to expand...
Click to collapse
unlocked bootloader
rooted
had tried 2 roms earlier cm7
had got back to stock from cm7, so i can upgrade to 2.3.6
I tried flashing it with RSDlite 5.4.4 and i was flashing this particular sbf file from here:
http://forum.xda-developers.com/showpost.php?p=22379866&postcount=393

sunny1119 said:
unlocked bootloader
rooted
had tried 2 roms earlier cm7
had got back to stock from cm7, so i can upgrade to 2.3.6
I tried flashing it with RSDlite 5.4.4 and i was flashing this particular sbf file from here:
http://forum.xda-developers.com/showpost.php?p=22379866&postcount=393
Click to expand...
Click to collapse
That thingy thing is causing a lot of troubles, you better go to http://forum.xda-developers.com/showthread.php?t=1136261 and use the 4.91 SBF and then install Nottachtrix version: http://www.nottachtrix.com/
EDIT:
Try always to find a better solution like flashing thru CWM and not SBF like for Example you can use 2.3.6 with Nottachtrix without do the SBF.

TravisAntonio said:
That thingy thing is causing a lot of troubles, you better go to http://forum.xda-developers.com/showthread.php?t=1136261 and use the 4.91 SBF and then install Nottachtrix version: http://www.nottachtrix.com/
EDIT:
Try always to find a better solution like flashing thru CWM and not SBF like for Example you can use 2.3.6 with Nottachtrix without do the SBF.
Click to expand...
Click to collapse
The reason for this is because flashing thru SBF is what bricks the phones. CWM flash files are a MUCH safer alternative. Good luck with your Atrix!

DJHile said:
The reason for this is because flashing thru SBF is what bricks the phones. CWM flash files are a MUCH safer alternative. Good luck with your Atrix!
Click to expand...
Click to collapse
Flashing SBF's only bricks devices when people dont research what they're doing and they flash the wrong SBF or downgrade from 2.3.4 gingerbread to froyo etc etc... I flashed the 2.3.6 sbf from 2.3.4 just fine.... People just tend to want to run and dive into this stuff without getting the proper information first.

i almost did the same mistake as you ... But i read more and ask users beffore doing something . Try to use Search button and ask don't do any thing on your own .

[Q] Bricked Moto Defy

HI there. First i want to excuse for my bad english.
So, right into the question. Week ago i tried to flash CM9 on my moto defy. I flashed it, it ran well, when suddenly, after 2-3 days the trebuchet luncher crashed. I reboot my phone and all i got is boot loop. So, i'm a noob , but i tried to fix the problem whit installing one of the SBF's for moto defy+ (didn't notice that, the sbf is for Defy+ not for Defy). Actually the rom ran great, but the camera don't work. So i have a NANDROID backup but the moto defy original recovery, doesn't flash it (it says: "E: failed to verify whole-file signature"). I can't instal clockworkmod, couse i can't root the rom. So, the question is: is there any chance to root my rom and instal clockworkmod or can i fix the original recovery error, so i can apply my backup and downgrade to 2.2 froyo.
The rom that i flashed is ->
4.5.1-134-DFP-231 - retail, vodafon, tmobile, O2, full Blur
I tried to flash other SBF's but they dont work, or can't root either.
I tried to root the rom with everyone possible root exploits posted in this forum... but they doesen't work. I noticed that, there are some SBF's wich are rootable, but the download links doesen't work.
So, what is the exit of this ****ty situation?

no way out

No way at all???

wait for a miracle.

meanwhile read this :
http://forum.xda-developers.com/showthread.php?t=1542956
DFP-188, DFP-231, DFP-2311 BL7 Root

novaproject said:
HI there. First i want to excuse for my bad english.
So, right into the question. Week ago i tried to flash CM9 on my moto defy. I flashed it, it ran well, when suddenly, after 2-3 days the trebuchet luncher crashed. I reboot my phone and all i got is boot loop. So, i'm a noob , but i tried to fix the problem whit installing one of the SBF's for moto defy+ (didn't notice that, the sbf is for Defy+ not for Defy). Actually the rom ran great, but the camera don't work. So i have a NANDROID backup but the moto defy original recovery, doesn't flash it (it says: "E: failed to verify whole-file signature"). I can't instal clockworkmod, couse i can't root the rom. So, the question is: is there any chance to root my rom and instal clockworkmod or can i fix the original recovery error, so i can apply my backup and downgrade to 2.2 froyo.
The rom that i flashed is ->
4.5.1-134-DFP-231 - retail, vodafon, tmobile, O2, full Blur
I tried to flash other SBF's but they dont work, or can't root either.
I tried to root the rom with everyone possible root exploits posted in this forum... but they doesen't work. I noticed that, there are some SBF's wich are rootable, but the download links doesen't work.
So, what is the exit of this ****ty situation?
Click to expand...
Click to collapse
Okay dude. First thing:
Calm down. If you already are then read on!
Since Defy and Defy+ are more than 90% similar in hardware flashing SBF should not be a problem until you don't want downgradability! So from the name of the SBF I guess its for 2.3.6(GB) So now no way can you downgrade to Froyo kernel or for that matter any ROM using Froyo kernel. Am not sure about your ROM but I use the Asia retail SBF (4.5.1-134-DFP-1321 - retail-asia full Blur multilanguage) and I have rooted it using latest superoneclick and modded, rooted and installed CWM recovery umpteen times! So, what you can do is:
1.) Find out version of Android(2.3.4 or 2.3.6) in your phone at present.
2.) Case a:If it is 2.3.4: You can get any kernel and downgradeability is
preserved. There should be no prob faced!
Case b: If you have 2.3.6: You should try the SBF I have since it is rootable.
3.) Now I presume your phone should be working fine with Android 2.3.6.
Let me know if it works and than we can proceed further..
You can also give a try with Walter's fixed SBF and Nandroid backup
PS: A Defy as I understand is almost impossible to Brick!!! Y? Since its bootloader is locked

HI there, thx for the help
Yes, the installed rom is 2.3.6. I want to change it, couse the battery drain too fast (one day and it's gone) and there's no camera.
I flashed the rom that you said me (4.5.1-134-DFP-1321 - retail-asia full Blur multilanguage), but it's not working.. Doesn't boot at all. After the rom is flashed, the phone reboot and nothing, black screen. Only the white LED light on the upper left corner is activated. I'm giving a try with Walter's fixed SBF now.

Walter's fixed SBF doesen't work too. Same blackscreen...

novaproject said:
Walter's fixed SBF doesen't work too. Same blackscreen...
Click to expand...
Click to collapse
Oh! I think similar thing happened with me once when I installed CM9 kernel! This is what I did:
1.) Flash SBF. (Full)
2.) Boot to stock android recovery.
3.) Wipe data and wipe cache.
4.) Reboot.
Well since you already installed a full SBF of 2.3.6 you cannot downgrade! And from what I have seen till now from users experience(and mine) 2.3.6 gives much better battery life. So from now on whenever u use a nightly or ROM use the one for GB(Defy+) builds

This means, that i cannot change the rom anymore?

novaproject said:
This means, that i cannot change the rom anymore?
Click to expand...
Click to collapse
You can change ROMs. But you can't go back to an old or downgraded ROM(like froyo). That means you will always have to use ROMs made for Defy+ (GB). There are many CM7 nightlies by Quarx for Defy+ and the latest one for me worked great.
However, should you want to go to Froyo again there is a workaround:
A chinese sbf of froyo was found to have an updated bootloader! So the workaround is:
1.) Flash the chinese SBF(Never use the flash as it will burn your flash)
2.) Root, install 2nd init and CWM.
3.) Now you can flash CM and ROMs for Defy(Froyo) since you got a froyo
kernel(And use your flash now )
This is something I gave a try and it worked for me. I am sorry don't remember which thread it was with this tutorial. May be you can give it a search...

Thanx again.
I tried the chineese sbf but it didn't work. Same black screen...
Is there any way to instal .zip rom (like CM7) with program like RSD lite?

novaproject said:
Thanx again.
I tried the chineese sbf but it didn't work. Same black screen...
Is there any way to instal .zip rom (like CM7) with program like RSD lite?
Click to expand...
Click to collapse
Did you do a data wipe from stock recovery after installing the chinese SBF?
I dint quite get your second question! If you asked :
a.) Can zip be flashed using RSD lite.. No!! You cant. RSD lite understand only proper SBF files with correct checksum!
b.) Can zip be installed from stock recovery: No!! To instal a zip from stock you need the zip to be signed by motorola. That is why the whole concept of 2nd init comes up! It is a recovery menu which comes before the system boots up

It was the first question
Yes, i did the data wipe, and nothing... I think, no other SBF works except mine... I don't know what to do now.

novaproject said:
It was the first question
Yes, i did the data wipe, and nothing... I think, no other SBF works except mine... I don't know what to do now.
Click to expand...
Click to collapse
Sorry dint see that! I am afraid i think the SBF you flashed has BL7 as someone in the thread mentioned earlier! just to be sure:
1.) Download this .
2.) Extract the sbf and check the cmg versions. Check the version for cmg39.
3.) If it is 7. I am afraid there is no way out yet!! For the time being you are stuck with that SBF!! You are unable to boot because the SBF I gave you and most others has BL6 !!
Sorry again as I dint thought of this possibility earlier! And don't worry much. For now reflash the SBF that is working for you and wait till a way to root it is found!!

And speaking of it I welcome myself to the group!!
Just got back my Defy+ from service center and after I switched it ON I saw the lockscreen interface was different! A quick check told me that it is the latest SBF they flashed. I kept my fingers crossed. Once back home I checked and found this phone is not rootable!!! Now I am stuck too!!

Wooow, they flashed you BL7??
OK, man, im gonna donate you one AK47!

novaproject said:
Wooow, they flashed you BL7??
OK, man, im gonna donate you one AK47!
Click to expand...
Click to collapse
Oh that is so very nice of u!!!!
Sent from my MB526 using XDA

[Q] Stuck. Anybody have T-mo Froyo SBF and/or advice?

Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?

richdaley said:
Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?
Click to expand...
Click to collapse
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.

richdaley said:
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.
Click to expand...
Click to collapse
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.

hotdog125 said:
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.
Click to expand...
Click to collapse
Beautiful. It worked perfectly.