Database Develop

[SBF] Gingerbread - 4.5.91 AT&T USA Only [SBF]

Official Gingerbread SBF release for AT&T
Android 2.3.4 --- Blur_Version.4.5.91.MB860.ATT.en.US
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
WARNING : FLASH THIS SBF ONLY IF YOU ARE STILL RUNNING STOCK AT&T 2.2.2 WITH A LOCKED BOOTLOADER. ONCE YOU FLASH THIS ANY ATTEMPT AT A DOWNGRADE TO A PREVIOUS VERSION WILL BRICK YOUR PHONE.
If you are running anything else using this could increase your chances of bricking. Read the thread before flashing !!!!
This SBF is intended for people who don't want to deal with rooting and unlocking and OTA's and blur removal and fastboot and recovery and blah, blah blah I'm going to brick my phone regardless of what I do stuff.
It's also meant for people who have patience and want to upgrade safely who don't want to deal with Motorola Software Update because of the OS they're running.
It's an original SBF plain and simple.
Compression MD5 - 37D7E7D002B921F98D47BAD85DB55532
SBF MD5 - 56721D893E43B814E95683A00B165555

Read eval-s post below to clear up the confusion.
Would not use if you've unlocked with pudding. Will probably soft brick or worse.
Locked phones should be safe.
http://forum.xda-developers.com/showthread.php?t=1138204 (see post #2) for an unlocked version (with root).

I am complete noob in atrix,But i want to know that i have unlocked my atrix but if i flash New Firmware GB,Will it make my atrix again locked plz tell me.

is this the final version?

If i flash back to 1.8.3 will it be locked again? And update to official from there

I dont know about this sbf, but the service sbf i got from the motorola software update tool worked fine with the leaked ota (which is apparently the same as the official ota) and i was unlocked before i flashed it
edit: the compressed md5sum from the op is the same as the one i got from the motorola server which i flashed via rsd 5.3.1 with an unlocked bootloader. so apparently it is a sirvice sbf
edit: i also flashed zomgunlock-lite.sbf after i flashed the sbf

So is it safe to update if ur unlocked already...is this update unlockable? Im currently rooted and bl unlocked....
Sent from my MB860 using XDA App

rjayflo said:
So is it safe to update if ur unlocked already...is this update unlockable? Im currently rooted and bl unlocked....
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Read the second post, or try and post your brick results!

I also recommend not using. I used the 4.5.91 SBF a long time ago and bricked my phone shortly thereafter.

No, this .sbf is safe. It will just burn your fuse, just like the OTA, and make downgrading to anything impossible. To downgrade, you will have to use something that includes pudding, and you will have to 'oem unlock' ...that's all.
The .sbf is no more unsafe than the OTA. And once you've OTA'd, if you see "Failed to boot 4" this .sbf is the ONLY thing you can flash if you want to stay locked. Basically, if you have even started the OTA process, or have ever flashed this .sbf, you burned a fuse in ReservedOdm and have only two types of .sbfs you can flash. This one, or any+Pudding. Only this one will let you stay locked and still boot.
If you flash anything with Pudding after the OTA and you are still locked, you will see 0x1000. But it will be a soft-brick, and then your only choice will be to:
a) 'fastboot oem unlock' to continue.
or
b) flash this .sbf instead, and stay locked.
An AT&T user should never see 0x1000 from flashing this .sbf.
But afterwards, downgrades are dangerous. 'Official' AT&T 4.5.91 users will hard-brick their phones with 0x1000, stuck in nvflash mode, if they ever try to use any .sbf except this one, or the very special non-motorola version of 1.8.3 (found in the Pudding thread) or Pudding itself. In the later case, you can still escape the 0x1000 by unlocking. If you flashed stock 1.8.3 or below after running GB 4.5.91 officially, your phone is a paperweight. Be warned.
the2dcour said:
Would not use if you've unlocked with pudding. Will probably soft brick or worse.
Locked phones should be safe.
http://forum.xda-developers.com/showthread.php?t=1138204 (see post #2) for an unlocked-safe version (with root).
Click to expand...
Click to collapse

Does this flash a new radio too?
Sent from my Atrix

martyotaku said:
Does this flash a new radio too?
Sent from my Atrix
Click to expand...
Click to collapse
Yes, it does, but its the same radio that has been available for awhile now.
Baseband version
N_01_77_30P
Sent from my MB860 using XDA App

Does this official update has differences from the leaked?
Fixed bugs/better battery life, etc..
If it does, will somebody make a safe cwm zip to install it?
(for unlocked users)
Sent from my MB860 using XDA App

Paschalis said:
Does this official update has differences from the leaked?
Fixed bugs/better battery life, etc..
If it does, will somebody make a safe cwm zip to install it?
(for unlocked users)
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
You already have 2.3.4 CWMs.

the2dcour said:
You already have 2.3.4 CWMs.
Click to expand...
Click to collapse
Yes, but these cwm`s were based on the leaked(beta?) att version.. Not on the official..
So I m asking, if the official(today's update) has improved battery life/performance etc?
Thanx!
Sent from my MB860 using XDA App

Paschalis said:
Yes, but these cwm`s were based on the leaked(beta?) att version.. Not on the official..
So I m asking, if the official(today's update) has improved battery life/performance etc?
Click to expand...
Click to collapse
As far as can be determined, the beta (from Moto dev servers) is the same as the "official" release now being pushed out.

so this include at&t stock GB kernel ( already posted by faux) and the well known .30P radio rigth?
Enviado desde mi MB860 usando XDA Premium App

eval- said:
The .sbf is no more unsafe than the OTA. And once you've OTA'd, if you see "Failed to boot 4" this .sbf is the ONLY thing you can flash if you want to stay locked. Basically, if you have even started the OTA process, or have ever flashed this .sbf, you burned a fuse in ReservedOdm and have only two .sbfs you can flash. This one, or 1.8.3+Pudding. Only this one will let you stay locked and still boot.
Click to expand...
Click to collapse
Eval, can you give us the path to cat eFuse status again and the comparison against which we can tell whether we've passed the point of no return with bootloaders? I would like to see where I'm at. Thanks.

So is this a service or full sbf for 4.5.91?

I am currently running locked and stock At&t 1.8.3. I want to update to this new OTA sbf. I read eval's post.
However, can someone confirm (break it down for me) that it is possible and probably safe to unlock the phone later using pudding or some other means. I am not an advanced user but will like to flash CM7 once its available.

[Q] Help Unlocked Bootloader Message

Someone have the logo_signed for Retail EU JB? I just want it to quit this message "Warning Unlocked"
Thanks in advance...

AW: [Q] Help Unlocked Bootloader Message
There's no logo.bmp for jb. We have to life with it. Moto isn't stupid > They upgraded the secure Level of the unlocked Logo and doesn't give us the ability to change it anymore.
Sent from my XT890

HSD-Pilot said:
There's no logo.bmp for jb. We have to life with it. Moto isn't stupid > They upgraded the secure Level of the unlocked Logo and doesn't give us the ability to change it anymore.
Sent from my XT890
Click to expand...
Click to collapse
Yup
Only thing I can think of is downgrading the boot loader... But Motorola stated the radio and boot loader cannot be flashed away from the current required signature, this would include secure version checks I'd assume. Which explains why people bricked trying to RSD back to ICS after doing the full ota update.
Sent from my Galaxy Nexus using Tapatalk 2

So.. I have to live with this horrible message? its sad...

AW: [Q] Help Unlocked Bootloader Message
We can downgrade with RSD if the Bootloader is unlocked. But we have to delete the line gpt.bin and motoboot.
I had to do it by myself today, because my i won't boot into the System or recovery anymore. I tried some stuff today. Switching between the full OTA's.
I was able to switch from EU JB OTA to O2 JB with the Homemades. But after i tried to revert back to EU JB with the same method the OTA aborted by setting simlinks and permissions. No Recovery was working (CWM or Stock) and it stucked @ the warning Logo.
RSD saved my ass and i did an Backup of my Retail EU JB before i started to mess around. So i'm back on track :thumbup:
Sent from my XT890

HSD-Pilot said:
We can downgrade with RSD if the Bootloader is unlocked. But we have to delete the line gpt.bin and motoboot.
I had to do it by myself today, because my i won't boot into the System or recovery anymore. I tried some stuff today. Switching between the full OTA's.
I was able to switch from EU JB OTA to O2 JB with the Homemades. But after i tried to revert back to EU JB with the same method the OTA aborted by setting simlinks and permissions. No Recovery was working (CWM or Stock) and it stucked @ the warning Logo.
RSD saved my ass and i did an Backup of my Retail EU JB before i started to mess around. So i'm back on track :thumbup:
Sent from my XT890
Click to expand...
Click to collapse
do i have to downgrade to ICS and quit this message?

Don't know how exactly but i'm bootloader unlocked and currently running the EU jelly bean (installed via the homemade fastboot) and I don't have the warning message.

crunchie-uk said:
Don't know how exactly but i'm bootloader unlocked and currently running the EU jelly bean (installed via the homemade fastboot) and I don't have the warning message.
Click to expand...
Click to collapse
>installed via the homemade fastboot
There ya go.
Sent from my Galaxy Nexus using Tapatalk 2

mattlgroff said:
>installed via the homemade fastboot
There ya go.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So, with JB, who used homemade fastboot AND DON'T USED OTA (capital to alert others), can still change the logo the same way?

diogo.sena said:
So, with JB, who used homemade fastboot AND DON'T USED OTA (capital to alert others), can still change the logo the same way?
Click to expand...
Click to collapse
Homemade doesn't increase the secure version or use partition tables that the ota update does.
Sent from my Galaxy Nexus using Tapatalk 2

M logo on JB
mattlgroff said:
Homemade doesn't increase the secure version or use partition tables that the ota update does.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So Matt there's no way to change the logo on devices unlocked with OTA JB Retail.EU that have the Unlock Warning Message?
It shows that message coming from a particular sector of the kernel? The BMP code is embedded?
Thx in advance

Help restoring back to stock

Well I need to go swap my phone :banghead: just realized my phones speakers are making crackling and popping noises.. problem is I've unlocked my bootloader and I'm currently on vipers rom.. so how would I go about getting back to stock?
Sent from my HTCONE using Tapatalk 2

Your best bet is to restore a nandroid of stock or flash the odex stock ROM. You won't be able to fully return to stock. Next, grab the stock recovery IMG and fast boot flash that. Relock your boot loader with the AIO toolkit. At that point you are mostly back to stock but not completely. You cannot completely return to stock until an RUU is released. Even then your boot loader will say relocked and not locked.
Sent from my HTCONE using xda app-developers app

youkosnake said:
Your best bet is to restore a nandroid of stock or flash the odex stock ROM. You won't be able to fully return to stock. Next, grab the stock recovery IMG and fast boot flash that. Relock your boot loader with the AIO toolkit. At that point you are mostly back to stock but not completely. You cannot completely return to stock until an RUU is released. Even then your boot loader will say relocked and not locked.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
One small edit, RUUs reflash the bootloader so it would say "LOCKED".

CNexus said:
One small edit, RUUs reflash the bootloader so it would say "LOCKED".
Click to expand...
Click to collapse
Oh, thank you. My apologies. I haven't run HTC since OGEvo.
Sent from my HTCONE using xda app-developers app

If you unlock your bootloader then relock it, it will say Relocked.......even after a ruu.
Sent from my HTCONE using Tapatalk 2

We need true root, not HTC's dev-unlock if I'm not mistaken to go back to compete stock. One of the reasons I'm waiting to root.
Sent from my soon to be rooted HTC One.

youkosnake said:
Your best bet is to restore a nandroid of stock or flash the odex stock ROM. You won't be able to fully return to stock. Next, grab the stock recovery IMG and fast boot flash that. Relock your boot loader with the AIO toolkit. At that point you are mostly back to stock but not completely. You cannot completely return to stock until an RUU is released. Even then your boot loader will say relocked and not locked.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Would i also flash the stock boot img?

I would, myself, I would flash every stock image I could find. Just in case they go perusing through the phone. Technically they aren't supposed to take it, but normally they don't look that deep if everything seems normal. I would also hunt down the apks that are deleted during the boot loader unlock just in case
Sent from my HTCONE using xda app-developers app

youkosnake said:
I would, myself, I would flash every stock image I could find. Just in case they go perusing through the phone. Technically they aren't supposed to take it, but normally they don't look that deep if everything seems normal. I would also hunt down the apks that are deleted during the boot loader unlock just in case
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
would you know how to get rid of that red warning message at the htc bootscreen?

That's caused by unlocking the boot loader I do believe. Won't go away until it is changed back to LOCKED
Sent from my HTCONE using xda app-developers app

youkosnake said:
That's caused by unlocking the boot loader I do believe. Won't go away until it is changed back to LOCKED
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
okay so i flashed the stock odex rom from viper but whenever i try to relock my bootloader it won't boot into the rom just straight back to the bootloader

Once you re lock you have to run the ruu. You have a custom boot.img and recovery that isn't signed thus it won't boot unsecured partitions with a locked bootloader

Verizon Moto X 4.4 return to 4.2.2

I was under the impression that once I accepted the KitKat update, I would no longer be able to return to 4.2.2 and root/all that.
Is this true? Can I still use RSDLite to go back?

I was wondering the same thing on the AT&T variant
Sent from my XT1058 using XDA Premium 4 mobile app

You can downgrade to 4.2.2 using RSDlite after the 4.4 upgrade. I have the VZW version, not the AT&T version, but I assume it's the same.

ZaneKaminski said:
I was under the impression that once I accepted the KitKat update, I would no longer be able to return to 4.2.2 and root/all that.
Is this true? Can I still use RSDLite to go back?
Click to expand...
Click to collapse
As of now you can use RSD Lite to go back to 4.2.2. In fact if you want root in 4.4 you need to go back to 4.2.2 to start the process.
http://forum.xda-developers.com/showthread.php?t=2446515

mpw3000 said:
As of now you can use RSD Lite to go back to 4.2.2. In fact if you want root in 4.4 you need to go back to 4.2.2 to start the process.
http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
If your boot loader is unlocked just flash the recovery in fastboot and after doing that it will ask you if you want root, just hit yes and bam you got custom recovery plus root. http://forum.xda-developers.com/showthread.php?t=2534850
[RECOVERY UNLOCKED] TWRP 2.6.3.1 for Android 4.4 [2013-11-19]
Sent from my XT1060 using Tapatalk

4.4.2 unlocked downgrade

Hi, tried searching my answer, but still not clear as to the answer for my situation, im about to purchase the unlock code for my non DE verizon moto x , code is from someone from china. If i upgrade to 4.4.2 while unlocked bootloader, any way back to 4.2.2 post camera update. Thanks

ericizzy1 said:
Hi, tried searching my answer, but still not clear as to the answer for my situation, im about to purchase the unlock code for my non DE verizon moto x , code is from someone from china. If i upgrade to 4.4.2 while unlocked bootloader, any way back to 4.2.2 post camera update. Thanks
Click to expand...
Click to collapse
Yes and No
No you can not flash the complete 4.2.2 PCU package it will fail because you can't downgrade the bootloader
Yes because you can flash everything but the bootloader and it will take but if you accidentally take a OTA. you will brick your device.
but if you are able to unlock your bootloader then why would you want to downgrade. with a unlocked bootloader you will be able to root 4.4.2 with no issues

because when I was on 4.4, I had some battery consumption and heating issues also bluetooth was not perfect, I just wanted to make sure I have a way back To 4.2.2
also, not being able to downgrade the bootloader, in which way does this affect me going back to four point 4.2.2?

Your phone will work fine but like i said if you ever take a ota it will brick your phone
Sent from my XT1056 using XDA Premium 4 mobile app

dray_jr said:
Your phone will work fine but like i said if you ever take a ota it will brick your phone
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ota will brick, will be able to rsd to 4.4 or 4.4.2 if wanted?

Yup that is correct
Sent from my XT1056 using XDA Premium 4 mobile app

ericizzy1 said:
ota will brick, will be able to rsd to 4.4 or 4.4.2 if wanted?
Click to expand...
Click to collapse
No. Once you start mixing bootloader versions with system file versions (i.e. 4.4.2 bootloader with 4.2.2 system files), RSD Lite won't work. You will have to use a command line and mfastboot.exe to manually flash each partition.
And I actually tried to run 4.2.2 (post camera update) system files with a 4.4.2 bootloader and it would not boot; however, 4.4 system files do work with a 4.4.2 bootloader.
This has actually been discussed at great length and detail in this forum and A LOT of people were bricking their phones playing around with bootloader versions, just like you are talking about doing. At one point there was a sticky dedicated to it, but its since disappeared from the board for some reason.
To put it simply, please don't start mixing bootloader versions with system files. If you like 4.2.2, don't upgrade to 4.4.2. If you are on 4.4, then you can still downgrade to 4.2.2 (post camera update version). Do that and stay there. But if you upgrade to 4.4.2, don't fool around with it and start trying to downgrade. There is no point, and you will likely end up bricking your phone.
It's your phone, so do what you want, but you have been warned (by someone with personal experience by the way). If you do brick it, please don't start another "OMG! HELP ME!! I BRICKED MY PHONE!!" thread. There's plenty of those already floating around here. :good: