Database Users

please help with sfb

ive got the rsd and the file i need and im pluged in and i looks like it reconizes my phone i think and i hit the " ...." and it show my sfb file but i cant start the prosess. the start button is not hilighted pleas help me.

It may be that the file name is incorrect. here is the file name for the 2.3.340 full sbf that I have:
VRZ_MB810_2.3.34_1FF_01.sbf

thats the same as i have. I even made sure that rsd is running in admin and ive moved the sbf file to my c drive like ive read on some other posts. im getting kinda worried here .

What version of RSDlite are you using? Did you put the phone in Bootloader mode?

im runningh 4.8 and yes im in bootloader mode. Im also on windows 7 . Im going to try it on my laptop to see if that helps just waiting the the sfb file to download.

It worked on my laptop. Just didn't like my new dell computer
Sent from my DROIDX using XDA App

spacecasespiff said:
It worked on my laptop. Just didn't like my new dell computer
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Glad to hear you got it working

My artix RSD/SBF Story

hi The Atrix has been my first official Android phone, i had a HTC TILT 2, which i flashed to 2.3. But this Atrix is very confusing. The first thing i haven't been able to flash any sbf file since i have gotten the phone. I wanted to go back to stock because my webtop hack wasn't working through adb or gingerblur bloatware.zip in cwm. So extracted the SBF to the root of my c: drive,unzipped, renamed SBF, waited for connection, then it extracts 100%then fails and gives and error but it never restarted. But last night i ran rsd with the sbf from this link http://bandbinnovations.com/xda/OLYF..._1g_1FF.sbf.g[/url], and ran the sbf properly, but after it executed 100%, then started running the phone commands, but while running commands it stopped @86% and gave a error "switching device to bp pass error", i tried to flash this same file a second time but each time it stopped and gave the same error at 86%, and RDS completely stopped. so i unplugged the usb from my computer, and it was stuck at the M logo screen(all night). So i freaked out and thought it was bricked, because no sbf i have tried has worked for me, and my battery was getting low flashing SBF so many times. and almost called att warranty this morning. But this morning i turned my Atrix on and boom it was back to stock 1.2.6?Dont know how i did it,or how do it again properly, but glad im back to stock. But that was extremly confusing and frustrating!

Nice! What are the odds you and someone else have the same story and posted at the same time with the same login name? Musta been excited to post this story.

Clienterror said:
Nice! What are the odds you and someone else have the same story and posted at the same time with the same login name? Musta been excited to post this story.
Click to expand...
Click to collapse
Gotta raise post count somehow! Lol
Sent from WinBorg 4G using XDA Premium App

CaelanT said:
Gotta raise post count somehow! Lol
Ya that's it man. Sorry if I kinda in a hurry to get my phone working again. And I don't know how delete the other post or how I did it 2 times.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse

which VERSION of RSD were you used?
RSD 5.0 or RSD 5.3.1 is OK for flash AT&T 1.26 or 1.5.7 or 1.8.3 SBF.
I flashed my ATT Atrix with RSD 5.0 many times, there's no issue every time.

jenhore said:
which VERSION of RSD were you used?u
RSD 5.0 or RSD 5.3.1 is OK for flash AT&T 1.26 or 1.5.7 or 1.8.3 SBF.
I flashed my ATT Atrix with RSD 5.0 many times, there's no issue every time.
Click to expand...
Click to collapse
I was using RSD 5.0 and trying to flash 1.2.6. On att. I don't know if its my computer or what, but I have tries it on 4 different sbf files on 3 computers. It finally went back to stock but I don't know how because it was bricked the night before.
Sent from my MB860 using XDA Premium App

[Q] Tried everything. Cannot reroot!

So I bricked my phone. This time couldn't recover. Warranty replaced it, got my replacement the next day. I've never had a problem rooting before, but this time I can't seem to get anything to work. I'm wondering if they sent me a phone with some type of root protection, if that's even possible. Please help, this really sucks. Tried Superoneclick repeatedly, different versions. Univ Androot doesn't support Sammies (at least not ours). Z4Root doesn't work. Tried Oclf and in the recovery menu I get E:signature verification failed Installation aborted. What do I do?

Last resort (well, actually first resort too): flash adrynalyne's clean rom... That has root built in...
of course you need cwm working to do so....
Sent from my SCH-I400 using XDA Premium App

Hmmm
Ok, I have only previously installed CWmod (once rooted) via Rom manager. Now, not having root, I dl'd cwmod_v08 and dropped the recovery and update.zip on my sdcard. I reboot, holding volume up/volume down. I select apply sdcard:update.zip, and I'm still getting a signature verification error, just like I got when I attempted this via OCLF. I read online that it is a problem with Android System Recovery <3e>, and to revert to 2e to remove the signature verification, but I already show 2e. WTF? I'm about to retrieve my hammer and root this piece Thor-style!

Haven't used Odin, but I guess it's time...

First off, lol @ the Thor thing.. haha
Second, yeah it is definitely time... just make sure you are flashing just the adryn_cwm_recovery4 ( something like that) file in the guide in this thread xP
And make sure you use pda, not phone....
If you still can't get it working, just ask here....
Also, before I'm done... i highly suggest not flashing a full dump in Odin.... just saying xP there is a corrupt version out there ( not on purpose)
Sent from my SCH-I400 using XDA Premium App

Ok, I'm using Odin 4.28 and it looks different than all the vid tutorials I'm finding...cwm_recovery_test4_adryn.tar is on my desktop, but when I hit PDA and try to select it (the tar file) it says "Invalid Image Type"...

Newer definitely doesn't always mean better xP i suggest downloading another, older, version...
Sent from my SCH-I400 using XDA Premium App

Ok, DL'd Odin3, it seems to be working better...What did you mean by you recommend not flashing a full dump? Sorry, still learning this stuff...I appreciate the help...

The link is bad for the update.zip file in the *Official* Clockwork Recovery thread. I flashed using odin3 and it seemed to work but when I attempt to apply the update.zip My little android turns into a caution sign-holding android error screen. Don't know if I did something wrong with Odin or if the update.zip files I am able to find online are wrong for loading clockwork with this particular recovery image (the tar is the image, correct? lmao) Help! Please! I'll send you good vibes and spiritual cookies!

Lmao, i love you xP
I would say first trying to push all of the soft keys and see if it pops up then...
That has happened to me before, and I didn't know what was going on either xP
Try that though... If not, then yeah... Your Zip is bad... I'll upload mine
Sent from my SCH-I400 using XDA Premium App

[recovery] clockwork Mod recovery....
Download from that thread... XD
Sent from my SCH-I400 using XDA Premium App

HLK75D for Verizon 4g posted at motor dev!!

I believe this is what everyone is looking for.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
Sent from my Xoom using xda premium

It says it's for MZ602. Will this still work with our current XOOMs.
Furthermore, will it work with a 3G XOOM that has yet to be upgraded?

It says Verizon. It is the same file we updated to. Ours was the mz600, but after the upgrade it became mz602. You know of any other Verizon xoom with 4g? They are going to sell the same xoom, just has the lte card in it this time.
Sent from my Xoom using xda premium

Well, I'm having trouble with it.
I'm using RSDLite and trying to flash the .SBF and it's saying:
"Error validating image files" under status, before I even hit start.
Then afterwards, I get:
"Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI..."

Thanks... Anybody knows if I flash one of the latinamerican image into a US 4G would brick the Xoom?

I think you have to extract it or unzip it.
Sent from my Xoom using xda premium

hammer4203 said:
I think you have to extract it or unzip it.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Extracted the .SBF from the .GZ file. It's just like.. RSDLite (v5.0) won't read some kind of .ini file. I have all the updated drivers, etc.

Great. After using this, my Xoom won't go past the boot screen.
It won't even boot into recovery. I can still access Fastboot and RSD.
Even after trying different unbrick solutions. Even after flashing back to HRI66.
Can't even get my Xoom to turn off now.

You may need the other cable to flash it in rsd mode. There is a special cable that looks exactly like the normal usb cable. It's wired different.
Sent from my ADR6400L using xda premium

You may need rsd lite on your PC and USB drivers to do it with the stock cable.
Sent from my Xoom using xda premium

hammer4203 said:
You may need rsd lite on your PC and USB drivers to do it with the stock cable.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Yeah.. That's what I'm doing it with. The stock USB cable included with the Xoom and RSDLite v5.4.4 with all the updated drivers.
My Xoom just sits there at the boot screen now, like I said, even after trying to flash back down to HRI66 afterwards to fix it.
I can still boot into Fastboot and RSD mode, but my Xoom stalls and doesn't enter recovery, even after trying another recovery img.
I thought I read something about needing a proper boot.img to go with the SBF file, but I even tried flashing AceXMachine's boot img and nothing.

So you guys haven't gotten this to work or are you just the lucky ones who had problems?

There is a stock version of sbf floating around that has 2 files in it one sbf and I can't remeber what the other one is. This is how they flashed ours for the 4g upgrade. It may be missing something. Can't the sbf be unpacked to the boot, system, recovery imgs? I read something along those linea in one of the dev forums. Not sure about that cable though. That's what worries me. It is suppose to activate something in the xoom so you can flash on rsd mode.
Sent from my ADR6400L using xda premium

dethrok said:
Well, I'm having trouble with it.
I'm using RSDLite and trying to flash the .SBF and it's saying:
"Error validating image files" under status, before I even hit start.
Then afterwards, I get:
"Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI..."
Click to expand...
Click to collapse
This is the issue I have. I do not have the official Xoom cable my dog ate it. Really it did. Looks like I will make a trip to Verizon and get one if necessary.

hammer4203 said:
There is a stock version of sbf floating around that has 2 files in it one sbf and I can't remeber what the other one is. This is how they flashed ours for the 4g upgrade. It may be missing something. Can't the sbf be unpacked to the boot, system, recovery imgs? I read something along those linea in one of the dev forums. Not sure about that cable though. That's what worries me. It is suppose to activate something in the xoom so you can flash on rsd mode.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Yeah, I think you're talking about this one. I downloaded that (from a mirror, as that link doesn't work) and everything I read said the smaller file (the one you're talking about) wasn't necessary.
And I haven't seen anything about using a special cable to flash your Xoom with RSDLite. Everything I've read just says the stock USB cable with updated drivers, so I have no idea.
zone23 said:
This is the issue I have. I do not have the official Xoom cable my dog ate it. Really it did. Looks like I will make a trip to Verizon and get one if necessary.
Click to expand...
Click to collapse
Find and download RSDLite 5.4.4. That's what fixed it for me.

dethrok said:
Extracted the .SBF from the .GZ file. It's just like.. RSDLite (v5.0) won't read some kind of .ini file. I have all the updated drivers, etc.
Click to expand...
Click to collapse
dethrok, you've got most of it right >extract the .SBF (I've had issues on 64 bit Win 7 machine, unless I've place the file at either the root of C: or else under c:\users\<my username>\ (??-weird??))
> make sure you have the latest drivers
> (this is the gotcha) you need to use RSDLite v5.4.4
>>Note: Yes the HLK75D SBF works and was designed with the original MZ600
Hardware, since the MZ602 is just the MZ600 w/ LTE
This should do it for you, however for good measure, I aways run a short script that unlocks, erases (boot/sys/rec/uda & cache partitions), flashes HR166 back onto the device & then relocks it. I know this is probably a waste of time; it just seems to SBF with less issues.
Here's the text out of the .bat I wrote:
(!!!Please bear in mind this will erase/format your device, so please make sure you have all personal data backed up.!!!)
If your system is already powered up and has USB debugging enabled you can remove the 1st REM statement & just execute the .bat file, otherwise reboot the device by holding down the volume up and power button > release both and then hold down the volume down button until the "fastboot" screen appears.
Copy the below text into notepad and save as a .bat file
REM adb reboot bootloader
fastboot oem unlock
REM Press and hold the volume down button
pause
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot -w
pause
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you want to use this, you need to d/l the HRI66 build .img files from MotoDEV as well as having the
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
* you can also just REM out the fastboot commands that flash the HR166 image, so the device is completely blank and you can just load the HLK75D sbf via RSDLite, either way works........
** Remember after any OS flash, you should launch “Android recovery Mode” (press & release the down volume button after the red Motorola symbol appears when the device powers on) and reset the device to factory defaults.
Cheers,
Hat

That is the build number for our xoom. Why load the file if it can't be used to flash the xoom? There is something missing as to how it's done. I mean when the xoom came out they leaked an sbf file and it worked. This one just has to be unzipped first. Or does it?
Sent from my Xoom using xda premium

hammer4203 said:
That is the build number for our xoom. Why load the file if it can't be used to flash the xoom? There is something missing as to how it's done. I mean when the xoom came out they leaked an sbf file and it worked. This one just has to be unzipped first. Or does it?
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Now see, someone mentioned the other file included in that old .SBF, but no one ever answered as to what to do with it:
janjan said:
Do we need to flash both of these following?
1: 1.35-everest.reflash.sbf
2: VZW_MZ600_Signed_HRI39_Signed_MDM600BP_C_02.0F.00R_SW.combo.sbf
And what is 1.35-everest.reflash.sbf is for?
thanks
Click to expand...
Click to collapse
Actually, another person in that thread said they flashed the file first, rebooted, then flashed the .SBF. So I'm not sure anymore.

dethrok said:
Yeah, I think you're talking about this one. I downloaded that (from a mirror, as that link doesn't work) and everything I read said the smaller file (the one you're talking about) wasn't necessary.
And I haven't seen anything about using a special cable to flash your Xoom with RSDLite. Everything I've read just says the stock USB cable with updated drivers, so I have no idea.
Find and download RSDLite 5.4.4. That's what fixed it for me.
Click to expand...
Click to collapse
Thanks a lot guy that worked and I'm now back in business. Meaning my 3G is now operational. Don't have 4G in my area but I assume it works now as well. My device was unlocked and when I go into network now it shows CDMA/LTE.
Edit:
I did not have the official Xoom cable either.

Zone, did you flash the HLK75D SBF?

[Q] Motorola XPRT stuck at Motorola Logo

Motorola XPRT stuck at Motorola Logo.
I'm trying to flash it with this firmwares:
1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf
1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf
If I use RSDLite, I get error (with any firmware):
and Code Corrupt in bootloader.
When I use sbf_flash on linux,
1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf - bootloader error(Mem Map Blank)
1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf - stuck at Motorola Logo.
Any suggestions?

Simple but always good to check. Make sure the sbf checksums are correct to ensure they were downloaded correctly.
Sent from my MB612 using xda app-developers app

Checksums of my files:
CRC32
1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf 7A4A4AF2
1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf 74A272C6
MD5
517739312695ec87e0668c50987dccdd *1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf
315d553a44a058ef6b662fa59280020e *1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf
SHA1
34197f6aee01746a4993017f9763166fa2e68bf0 *1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf
6b7657609e29323c38ee68401977b1618c855582 *1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf
Where i can find correct checksums for comparison?

Hmm. I thought I saw them on the download pages. When I get home today I will check the checksum of my boost sbf. Just to compare. I don't have the sprint one though.
Sent from my MB612 using xda app-developers app

I have the same problem, please help me!

After falshing, Turn off your mobile. press R + M + Power key. you will get into motorola recovery. Do a data wipe/factory reset and reboot again... It always bootloop whenever i flash the sbf also. It should fix it.

just flash bootloader BL_0402_cdma_kronous_HS_generic_signed_Consumer_replacer.sbf
https://docs.google.com/file/d/0BwQkFb0zEZ3iRUMwLTFtdXJSX28/edit?usp=sharing
it always helps

rongsang said:
After falshing, Turn off your mobile. press R + M + Power key. you will get into motorola recovery. Do a data wipe/factory reset and reboot again... It always bootloop whenever i flash the sbf also. It should fix it.
Click to expand...
Click to collapse
nonono666 said:
just flash bootloader BL_0402_cdma_kronous_HS_generic_signed_Consumer_replacer.sbf
https://docs.google.com/file/d/0BwQkFb0zEZ3iRUMwLTFtdXJSX28/edit?usp=sharing
it always helps
Click to expand...
Click to collapse
I've been doing it all, but in result i get after few minutes logo M error in bootloader
Bootloader
04.02
Err:1B,00,02,00,00
Battery OK
OK to Programm
Connect USB
Data Cable
Click to expand...
Click to collapse

Janushkevich said:
I've been doing it all, but in result i get after few minutes logo M error in bootloader
Click to expand...
Click to collapse
You cannot flash 2.2.2 after you have flashed 2.3.5.
After flashing 2.3.5 get into recovery and do a data/factory reset.
Sent from my MB612 using xda app-developers app

http://www.mediafire.com/?077aa2bbe3kxg63
1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-110-KNS-46-49-test-keys-signed-Sprint-US.sbf
yes, always do full wipe from recovery
then get root and flash rongsangs cm7

Janushkevich said:
I have the same problem, please help me!
Click to expand...
Click to collapse
today i had a bootloop
but when i insert microsd back, it worked

I had the same boot load error. You have to use 2.3.5 since you have already flashed to it once, you cannot back up to froyo.
Is your phone a boost or sprint?
Sprint can be flashed with either the sprint sbf or the boost sbf, But Boost can only be used with the boost mobile.
Reflash 2.3.5 and do a full wipe on the phone and it should fix the problem.