Hi,
as anybody knows the bootloader of the the Motorola Milestone is signed so no custom ROMs can be loaded. As far as i know the bootloader of the original Droid isn't signed and can run custom ROMs like CyanogenMOD for example.
Anyway... yesterday were on "http : // and-developers.com/sbf:milestone" and saw the SBF files for all Milestone bootloader versions. They can be flashed with RDSLight just like normal SBF files.
The question now is: Is it possible to flash the the Droid bootloader on a Milestone device? If this is possible the Milestone should also be able to run any ROM like the original Doid.
No.
This was tried at the start of the year, it ended up bricking the phone.
Droid is CDMA phone, Milestone is GSM. So they're not compatible with each other.
This question has been asked many times already. Don't you think an idea like yours would have already been tried out by now?
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.
Hi all, I need help.
I have an XT1053 developer edition, gsm. In the past I've unlocked bootloader just to use Xposed on Kitkat, I've never flashed custom roms. Only once an XT1052 stock rom to have italian as language, but since it had a bad radio behaviour I went back to XT1053 stock rom. I've had root but not for long. I have tried also to re-lock the bootloader, but I was never successful since (FAIL: Please run fastboot oem lock begin first!)
With the 5.1 OTA, now I have the right build but with VZW written at the end. In the boot animation, I have the Verizon logo. Thanks to Mark of Motorola Forum Manager, I've had the stock XT1053 5.1 DE software to flash through fastboot, but even if the procedure is successful I cannot get rid of the VERIZON thing. I would like to use RSD Lite but I can't since it doesn't recognize the phone as connected, even if Motorola Device Manager does recognize it and the drivers are installed.
How can I do? Is there a way to really clean completely the phone and install the right software more "deeply"?
Any help will be much appreciate.
Thanks,
Luca
I heard lollipop drains battery fast so I tried stopping update midway now my stock kitakat is corrupt. Please advice how to install stock Kitkat in my motorola droid turbo xt1254.
Note my usb debbuging is off in phone settings and the device is not being recognised by RDS Lite even though i tried reinstalling motorola device manager. It says update is N/A.
Thanks in advance
Crunch7
At the very least, you have a lollipop recovery on the phone and will not accept KitKat reinstallation. It is likely that you bricked the phone, but not totally certain. Try putting the phone in fastboot for RSDlite. If you can't do that, you may be SOOL. Once you do get a stock ROM on, unlock the bootloader with 'Sunshine', then you can do about anything you want.
Sent from my XT1254 using Tapatalk
There's three versions of Verizon firmware that can be bootloader unlocked via Sunshine. Make sure you do NOT update to the very latest, which cannot be unlocked. Once bootloader is unlocked you can then downgrade back to Kitkat if you wish.
You can't downgrade bootloader, but with unlocked bootloader you can downgrade firmware. With a locked bootloader you can't downgrade anything.