Database Users

[Q] Use ClockworkMod Recovery to get back to stock and out of boot loop??

I have a HKT75D xoom that I was trying to re-lock and unroot. Something along the way obviously went wrong. I think I may have used the wrong stock files to return it to stock and then locked it, but I am unsure. I do know that I am stuck in a boot loop now. If I turn the Xoom off...it just turns itself back on and sits and the M. I can get to fastboot, clockworkmod recovery, and rdp? (i forget the name, but its the other option under Android Recovery at startup.)
Is there any way I can use clockworkmod recovery or another method to restore my xoom to stock or have I bricked it? I have a 3G/Wifi xoom that is currently nothing more than an expensive paperweight so any help would be appreciated!

Its really really really hard to brick these things. With motorola devices, you just need to get RSD Lite running (a PC program), get into RSD mode on the device and then connect to the computer. You can then flash a stock sbf file and that will bring you back to stock firmware.
I can't provide links right now but if you look around/wait for someone, you'll be just fine. The fact that you can get into CWM, fastboot and **** is a good sign. The key is to not panic and do plenty of reading on how to troubleshoot this.

Thanks for the reply. I have done a ton of reading and became a bit overwhelmed so I knew posting would be the good thing to do. I just need some guidance here. I went and snagged RSDLite 5.6 from: http://forum.xda-developers.com/showthread.php?t=1348587
I believe that is the latest version. My question is where do I find a stock sbf file for my 3G/WiFi motorola xoom?
Edit: I got my xoom connected to RSD Lite and get the following in device properties if it helps any:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x001050
DRM Version: N / A
Phone Type: Engineering (0288504140C00557000000000000)
Click to expand...
Click to collapse

What region is your device from?

My Xoom is US.

Ok, in order to have your xoom seen in RSD you need to be in RSD mode on the Xoom. In order to get there, turn it off. Then hold power and volume up and it'll get you into rsd mode. Once it says something like "starting RSD support protocol" you can plug it in and RSD lite should recognize it.
Now you need the sbf file. I'll have a look around but I swear the file was posted on these boards somewhere before.
Edit: Found a thread with a ton of different SBF files for various regions. There is a VZW 3.2.2 sbf file toward the bottom of the OP. Make sure to charge up before you flash and as per usual, I am not responsible for anything that happens from flashing. Best of luck to you!

Thanks again for the help...unfortunately the filesharing sites linked no longer allow downloads.
I will keep an eye out for the file but if anyone knows a place then please let me know !

oh damn
I'm sorry
I found this. I don't know about legitimacy but perhaps its worth testing.

Hacktually said:
I have a HKT75D xoom that I was trying to re-lock and unroot. Something along the way obviously went wrong. I think I may have used the wrong stock files to return it to stock and then locked it, but I am unsure. I do know that I am stuck in a boot loop now. If I turn the Xoom off...it just turns itself back on and sits and the M. I can get to fastboot, clockworkmod recovery, and rdp? (i forget the name, but its the other option under Android Recovery at startup.)
Is there any way I can use clockworkmod recovery or another method to restore my xoom to stock or have I bricked it? I have a 3G/Wifi xoom that is currently nothing more than an expensive paperweight so any help would be appreciated!
Click to expand...
Click to collapse
Are you locked or not? I don't know if your stock restoration project was successful since you say you can boot into CWM recovery (stock would overwrite the recovery). Just make sure that you have a flashable rom zip file on your sdcard and then boot into CWM recovery and flash it. You're rooted so you know how to do that. FYI, you should probably do a complete data wipe/factory reset, cache wipe and dalvik cache wipe.
Why did you want to revert to stock/re-lock? Are you selling your Xoom or sending it to be fixed? If you wanted to upgrade to ICS, there a CWM flashable stock ICS rom available in the Development section.

I figured out that I was using the wrong stock img's from motorola dev. Used the right ones and now running Ice Cream!!!!!
ty for all the answers and help

[Q] Droid X Bricked

So a Droid X is stuck at the dreaded "mem_map blank" bootloader screen. Everywhere I can find says its bricked, but there seems to be some hope. The DX was running the most recent OTA from Verizon, but was rooted before the update. After the update it still had SU, but it wasn't functional.
On another DX, I had the same issue. I used the 2.3.3 System Version 4.5.605 SBF and took it back to stock, rerooted, and installed a custom ROM just fine. This time things blew up.
The error I get after I flash ANY SBF is:
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Click to expand...
Click to collapse
I know there's rules against going from the OTA to 2.2/2.1 or something, but from 2.3 to 2.3? Anyway, any help is GREATLY appreciated. Is there any way to fix it?
EDIT: I'm getting "Unable to retrieve RAM Downloader for Flash Bootloader checksum." at the end of my SBF.

The person that owned the Droid X told me they didn't take the OTA. I believed them. Lesson learned.
I used the most recent SBF I could find (1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-VERIZON.sbf) and it came right out of the bootloader.

I am getting the same error when trying to SBF to Android 2.3.3 System Version 4.5.605 (VRZ_MB810_4.5.605_1FF_01). The user told me they did not take the OTA update.
Bootloader 30.04
Err: A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
I am downloading the newest SBF as suggested by iamz3r0. Will report my findings.
---------- Post added at 10:19 AM ---------- Previous post was at 09:39 AM ----------
Well, my reason for wanting to SBF the user's Droid X was because he reported to me that his phone was stuck at the Motorola Logo. I confirmed this and thought it would just be a simple SBF.
With the latest SBF (1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-VERIZON.sbf) the flash works but the phone gets stuck at the Motorola logo again.
I do believe the original error was in regards to the OTA update the user took, but my issue of the device being stuck at the Motorola logo must be due to a device problem.
I will try to flash a few more time just to make sure there wasn't any issues with the flash of the newer sbf.

Boot into recovery and do a factory reset.

I'm getting this error too (stupid me for not reading enough about the new OTA update before trying to SBF) but now the phone won't charge and it says the battery is low and it cannot connect.
If i plug the phone into the wall, it won't charge, it just goes straight to the bootloader screen and this error message, so i can't sbf back to the right version.
Any idea how to get it to take a charge?

find someone else with an X to charge it for you, or get a Verizon store to charge it for you.
Sent from my Transformer Prime TF201 using Tapatalk 2

I was at the same point you were my friend flashed the ntelos rom then I sbfed without knowing this and bricked it but he sbfed back to 1FF–p3a_shadow_cdma etc.... And it booted right up btw if you stuck at Motorola logo just do a factory reset and it should boot plz thanks
Sent from my DROIDX using xda premium

[Q] I've Bricked another one!

Night before last my Droid X was upgraded via OTA from Froyo 2.2.1 to Gingerbread 2.3.4 , at which I lost my Root. So I started searching YouTube for videos on taking my phone back to Froyo. And I found just what I was looking for. Return your Droid back to Froyo. So I followed the instructions to the letter, I downloaded - RDS Lite 4.9 - Motorola Helper_2.1.40_5.5.0 - VRZ_M810_2.3.34_IFF_01 . According to RSD Lite the flash was successful. Droid X reboots, and this is what I was left with.
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program'Transfer Mode:
USB
I have tried SBFing twice and RSD Lite sees the phone, goes thru the flash, reboots the phone but I get the same responce on the phone as stated above. Although in my computer, the Droid is not detected.
In your opinions, have I done an unrecoverable bricking to my Droid?
Go ahead, I can take it.
TIA

I used 4.5.621 SBF file, and was able to bring my phone back to the way it was before I got in a bind (Droid X SBF Files - Motorola SBF Files). It is alive with all of my Apps, so I'm not sure just what happened to it. But to whoever is responsible for the web site, I think P3 Thanks

Great job on getting back to .621.
Unfortunately, being on .621 makes it impossible to flash back to Froyo.
However, you can root and install custom roms.
Sent from my DROIDX using Tapatalk 2

yeah I know, but at this point I'm just happy to have my phone back in good working order. I had just bricked my Droid X2 @ 2 weeks ago, so now I don't have to face my wife with another $200.00 paper weight.

I have the same issue. Someone pointed me to this forum so I'll just include my text.
So I just got my first droid yesterday, it's a droidx from motorola. I initially factory reset it and cache cleared and it was working like a charm. Anyways, today I got the idea after reading over cyanogenmod following these instructions. Since I didn't have much on it I didn't backup. I remember vaguely updating the system previous to this, I think I was at 2.34. Anyways, I get done with flashing it- as far as I know it was successful- rdslite said it was complete. I try to do another factory reset, can't get into it. Just the bootloader comes up saying : Bootloader30.04 Err:A5,70,70,00,1F and a few things about to plug usb in and that it needs service...
I see something on cyanogen's page that I overlooked before:
WARNING: The 2.3.4 OTA release, the bootloader was patched to version 30.04. If an attempt is made to downgrade to an earlier version through the SBF method below, the bootloader will throw an error and the phone will not boot.
FLICK.
I tried the 1kds cd and it says it installed properly, I turn it on only to see same bootloader issue. I tried another rom and same thing. The last one I used was apparantly a 2.34 one and now my phone says code corrupt on the bootloader screen.
I need to find a way to charge the battery. I feel bad because it was a present to me from my girlfriends sister, and I don't want to see her and tell her I broke it already
But, can you guys help me with this? I don't really know where to go from here.

Sbf

Sbf is the only way. And from what I understand if you did the. 621, you won't be able to do previous releases.
I could be wrong.
When it comes yo moto flashing, donkey skip reading anything lol
Sent from my DROIDX using xda premium

[Q] Defy near death or worse. Please help!

Hi guys, you are my last hope!
Bought my Defy early 2011 and regularily updated with custom ROMs, so you could say I know a thing about rooting, RSD Lite, fixed sbfs, ...
Or at least I though I knew, but I still managed to kill my phone I think.
Here's what happend:
I tried to install Epsylon3s nightly from may 8th (http://defy.wdscript.fr/defy-cm9/). Before that, I was on CM 7.1
After installing the zip and rebooting, I saw the bootlogo, then i was asked for my pin code. As soon as i entered it, again to the bootlogo, again the pin, and so on.
So i realized something was wrong.
Could not get into recovery, so I flashed
JORDN_U3_97.21.51.sbf
as this often helped me in the past.
I then tried this one:
http://forum.xda-developers.com/showthread.php?t=1498843
Also didn't start.
So back to
JORDN_U3_97.21.51.sbf
But here it might be, that I misclicked (I have quite some SBFs in that folder, cause I wanted to be prepared in case something went wrong), as after that, I never got my Defy to work again.
I was stuck at the Motorola M logo.
Coudln't get into recovery, so no zips for me anymore, only flashing of sfb.
That's basically when I entered panic mode. As I didn't know what I just flashed, I could only guess the problem. So I tried the Ginger2Froyo (http://forum.xda-developers.com/showthread.php?t=1486731) in case I went to BL6. Also tried http://forum.xda-developers.com/showthread.php?t=1552152
But in this process, my RSD Lite started to behave strange:
when flashing, it's building the image, uploads it, checks checksum. But once it says "rebooting" it immediately jumps to 100% and pass. Phone how ever stays black and white LED.
Of course I can still flash other SBFs, and I tried various (JRDNEM_U3_3.4.3-36-1.7. sbf for example). But I either get the instant PASS, which tells me something didn't work, or sometimes I get the neverending bootlogo and RSD telling me to start the phone manually.
So... that's my story.
I can't seem to find a single SBF that would work for me. I screwed up big time.
To make this clear: at this point I don't care about downgradeability or anything thelike. Whatever makes my Defy work again, is fine. Froyo, Ginger, ICS, or whatever.
So if anybody still has any advice for me, I'll love you forever! Promise!
Thanks a lot in advance for any help you sure will offer,
Clock

Try this if you haven't :
Go into stock recovery and make a factory reset
Sent from my MB526 using XDA App

As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.

Have u tried this thread:
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade

Clock1999 said:
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Click to expand...
Click to collapse
Im sorry , thought you mean custom recovery when you say you can't enter recovery.
I was in the nearly same situation but i never changed my bootloader...., by me out works to power up my phone with pressed volume button down to enter stock recovery ...
So I'm sorry i couldn't help you
Sent from my MB526 using XDA App

You just like to play with your defy, don't ya
Have you tried the suggestions under Common problems/questions in this guide?

Thanks for all the responses.
However all the guides seem to point to two options only:
1) Flash this one Eclair (which I already mentioned that I did, that it used to work, but since the "instant 100% on rebooting" doesn't anymore.
2) Factory Reset/Wipe. Which I cannot, as I don't get into Recovery Mode. All I can do atm, is flash SBFs. Defy won't enter Recovery Mode (which I guess is a pretty bad sign)
But the way I always understood it, was that you only need to be careful what you install, so you don't lose downgradeability. And that, once lost, you wouldn't be able to flash "older" roms, but newer ones would always be possible.
So shouldn't there always be a rom, that saves me?
What about Defy+ roms? Any advice on that? Which best to try first? So far, I haven't touched Defy+ roms at all.
Thanks for the support!

Did you try this:
When Off, press Vol. down and power.
You'll get an exclamation mark inside a triangle.
Press both Vol. up and down at the same time.
Now you suppose to be in stock recovery and you can do factory reset.
Do the above after flashing stock SBF.

Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock

If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2

Clock1999 said:
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
Click to expand...
Click to collapse
If you flash any of the defy+ roms, camera won't work..there isn't a fix or patch for that..
Doesn't matter from where I send it, what matters is written above

corrinti said:
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Click to expand...
Click to collapse
Hi,
as I mentioned above, I already tried this ROM but it gives me the same result as all the others: stuck at bootlogo.
Maybe there is a special trick on which ROM I should flash before flashing this one?

Sorry, I do not know how to help. Just no idea now, try to dig the forum.
Once I had very similar problem - whatever I flashed I was stuck at bootlogo. And in my case I found out that just before flash my internal memory had been filled with some mess, which was not removed by any wipes (cache, dalvik cache, cache partition) and after any flash memory was too filled to start the system.
But finally I could flash Chinese eclair (CG5), which at last started horribly laggy, and I could wipe private data from a system - it gave me more than 1GB of internal memory back (from 40MB after all wipes and clean system install) and a way to flash whatever I wanted without a problem.
So even if it is also your problem, my way is not available to you now. Maybe you can find as small sbf file as possible and try then.

I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!

Clock1999 said:
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Click to expand...
Click to collapse
I could use CG5 full sbf which will not boot for you as you put BL6 and maybe BL7.
To boot from flashed sbf it cannot be lower BL version.
I suppose that now you have a memory problem - flashing sbf do not wipe the memory.
At first I would try getting into stock recovery (even several times, just pull battery out, wait a minute, power, vol -, battery in) - if successful then do a factory reset and reboot.
If not I would try to find out a smallest sbf with proper BL version - just to give it more chance to boot with small memory available, if not then again try to get into stock recovery.

I'm the happiest guy around, as I finally revitalized my Defy.
For all you guys, who already tried everything: here's what worked for me.
Just let it rest a few days.
After I hadn't touched my phone for a couple of days, I thought about giving it one last try. So I flashed the Defy+ SBF (4th in this list: http://sbf.droid-developers.org/umts_jordanplus/list.php), like I've done multiple times before.
But this time, when rebooting, I wasn't stuck at the M-logo, but in a bootloop. And that gave me the smiles as I knew, that now I should be able to enter Stock Recovery again. From there on, it was no problem to get to a stable base again. After flashing the BL6 Froyo, I'm now on CM9 and everything is fine.
Thanks for all you help.
Sometimes, you just have to give it a rest...
Clock

It is a next such case I see in moto forums ;-) but it is really hard to give a tip: leave it for few days and check again

Use the sbf_flash for Linux
Sent from my MB526 using Tapatalk 2

[Q] Can't find rooted SBF for Australian Defy+ (MB526)

Hi Everyone,
I am trying to load a rooted SBF file onto my Motorola Defy+ (MB526). Basically I had some issues with installing CM10, and decided to revert back to CM9, however I received some Encryption Unsuccessful messages. The specific message that I received lead me down the track of flashing SBFs to the phone (as per the link above). My challenge is that if I use the rooted SBF provided then the phone keeps returning to the Bootloader window which displays Err:A5,69,35,00,27!
The only SBF that will restore my phone back to healthy operation is the DEFYPLUS_U3_4.5.1-134_DFP-231_AU_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRANZ_P021_A030_Service1FF.sbf.gz, which is the retail version for Australian's like myself! There doesn't seem to be any rooted version for Australian phones.
If anybody can suggest a rooted SBF that will work with an Australian MB526 (originally from the Telstra network) it will be greatly appreciated.
Kind Regards,
David

Howdy mate, i just flash this on my mates simlocked telstra defy+
DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
it booted fine and rooted. didnt have to wipe and format either. may have to google sbf.

DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf Not working
Hello Whatrom,
Thanks for your input. Unfortunately I have not been as fortunate as you. Previously I have flashed this ROM, and my situation did not improve. However it has been a few weeks since my first attempt(s), so I decided to try again today. Whilst the ROM flash appears to work fine, with "Finish" clearly displayed in the RSD Lite Program (on Windows), the Motorola Defy still shows error data on it's screen.
Here is what I see on the Motorola Defy's screen -
Bootloader
09.10
Err:A5,69,35,00,27
Click to expand...
Click to collapse
If you have any further recommendations please let me know.
Kind Regards,
Davo

That's not possible. Are you sure you are flashing dfp231 sbf? It's bootloader version 7(max known), so it cannot give you the boot loader error
Sent from my MB526 using Tapatalk 2

Definitely using the stated SBF, and definitely have version 9 of the boot loader!
Hi thekguy,
Yes I am definitely using the SBF file that I stated, however it is not the only SBF file that I have used whilst trying to get the phone going. Given that you don't believe that the SBF can co-exist with the boot loader version maybe I can look at downgrading the boot loader (from version 9 to version 7). If you think that this is worth trying can you provide any further advice before I start off on my new quest?
Thanks very much for your valuable input.
Kind Regards,
Davo

Mr Davo said:
Hi thekguy,
Yes I am definitely using the SBF file that I stated, however it is not the only SBF file that I have used whilst trying to get the phone going. Given that you don't believe that the SBF can co-exist with the boot loader version maybe I can look at downgrading the boot loader (from version 9 to version 7). If you think that this is worth trying can you provide any further advice before I start off on my new quest?
Thanks very much for your valuable input.
Kind Regards,
Davo
Click to expand...
Click to collapse
No, you cannot downgrade bootloader:laugh:.

Mr Davo said:
Hi thekguy,
Yes I am definitely using the SBF file that I stated, however it is not the only SBF file that I have used whilst trying to get the phone going. Given that you don't believe that the SBF can co-exist with the boot loader version maybe I can look at downgrading the boot loader (from version 9 to version 7). If you think that this is worth trying can you provide any further advice before I start off on my new quest?
Thanks very much for your valuable input.
Kind Regards,
Davo
Click to expand...
Click to collapse
The version which appears at the boot loader screen does not correspond to the actual bl version(surprisingly). So that 9 which you're referring to is not the boot loader version. The sbf you're using has the highest possible such version(7), which implies that no one should face this issue while trying to flash this sbf, because the device cannot have a version higher than the one in this sbf(7).
It's possible that due to eMMC failure, the sbf is never flashed properly, and so the boot loader error occurs
That's only my guess though
Also, sorry but boot loader version can only be upgraded, not downgraded. You can't upgrade since you're at the maximum value already.
But if your phone works with a specific sbf, flash it and root using framaroot(search on Google). It is an android application which can be simply installed and run to root the phone. Then try to fix your network using baseband switcher.
Sent from my MB526 using Tapatalk 2

I have just had to do this today.
I followed the steps provided here http://forum.xda-developers.com/showthread.php?t=1542956 (use the first SBF for each step) and the phone appears to be working fine and http://forum.xda-developers.com/showthread.php?p=12837303 installed fine.
About to try some custom ROMs now to see if this what this little phone can handle