I didn't upload. @unchoney over at droid hive uploaded to here.
http://www.megashare.com/4392491
josdad00 said:
I didn't upload. @unchoney over at droid hive uploaded to here.
http://www.megashare.com/4392491
Click to expand...
Click to collapse
If you install this you CANNOT go back to GB ever.
mattlgroff said:
If you install this you CANNOT go back to GB ever.
Click to expand...
Click to collapse
And why is that? I've been running SamauriHL's script to keep my data and update since .2233
zoompastu said:
And why is that? I've been running SamauriHL's script to keep my data and update since .2233
Click to expand...
Click to collapse
Because the FXZ back to .902 is BLOCKED on the new release.
Worse yet, you can't go forward without a full 905 or ICS FXZ, either. If you do this leak, you WILL be stuck. If you attempt to FXZ to 902, you will soft brick your phone. You have been warned.
Dumb. You would think that our feedback on the leaks might help MOTO's development. It's as if they locked this one down as some form of revenge...
Glad I didn't update yet. I'lda gone nuclear.
It's the same thing they did on the D4 and RAZR. Except they had an FXZ for the version they were updating to ICS from. We don't. If we had a full 905 FXZ we could make this work to go forward. Once on 235+, however, there's NO going back to GB ever. And right now without an FXZ for 905 or the OTA ICS, 235 ain't going forward, either. That's what I call BAD.
Does someone have some method of completely obliterating data and dropping back the FXZ or some other form of information? Even if it's just some sort thing that only they can do.
Man, I don't get this one.
I'm not doing this one, that's for sure. Is ANYONE going to do that?
Thanks for the warning though!
and I feel bad for the poor fool who had to find out the hard way that it was a finality.
No one HAD to install it to find out. We ran the security checker on it and it showed us what we were dealing with. The person who posted the initial link did get impatient and installed it before we were able to check it. Now he's stuck.
BasPilot said:
...and I feel bad for the poor fool who had to find out the hard way that it was a finality.
Click to expand...
Click to collapse
I almost was that fool. I downloaded the file and hit the refresh button to see if there were anymore posts before updating my phone. Glad I did!
zoompastu said:
I almost was that fool. I downloaded the file and hit the refresh button to see if there were anymore posts before updating my phone. Glad I did!
Click to expand...
Click to collapse
Same here but I was lurking Droidhive and found out there was no going back lol
SamuriHL said:
No one HAD to install it to find out. We ran the security checker on it and it showed us what we were dealing with. The person who posted the initial link did get impatient and installed it before we were able to check it. Now he's stuck.
Click to expand...
Click to collapse
Well that's good for most people, and good that it was able to be spotted before too much damage was done over all...
I am just failing to see the logic of putting out an open source piece of software that locks you into it. The only thing I can see is that the leaks have bothered the OS builder and this is their way of stopping us from using them.
By the way Thank you SamuraiHL for that Awesome script you wrote to update with these leaks. Works GREAT!!
BasPilot said:
Well that's good for most people, and good that it was able to be spotted before too much damage was done over all...
I am just failing to see the logic of putting out an open source piece of software that locks you into it. The only thing I can see is that the leaks have bothered the OS builder and this is their way of stopping us from using them.
Click to expand...
Click to collapse
I can give you the logic. 235 is most likely a release candidate that they feel strongly will be the OTA. And moto has put a frack ton of effort into getting all the ICS builds on the different devices to be the same. This is less of a support headache for them. By locking devices to ICS only, the support costs go down for both moto and VZW because the builds are functionally identical. That's my guess.
---------- Post added at 02:13 PM ---------- Previous post was at 02:12 PM ----------
zoompastu said:
By the way Thank you SamuraiHL for that Awesome script you wrote to update with these leaks. Works GREAT!!
Click to expand...
Click to collapse
You're very welcome.
SamuriHL said:
I can give you the logic. 235 is most likely a release candidate that they feel strongly will be the OTA. And moto has put a frack ton of effort into getting all the ICS builds on the different devices to be the same. This is less of a support headache for them. By locking devices to ICS only, the support costs go down for both moto and VZW because the builds are functionally identical. That's my guess.
Click to expand...
Click to collapse
Can't they just end support for that saying you need to upgrade to our latest software and this will fix most of your problems if not all?
Either way, correct or incorrect on your part, it'll be fun to watch ideas thrown around by people and it will REALLY be fun to see one of you geniuses come up with a way around it. You know you will. 24 hours and one of you will crack the nut.
Don't look at me! I'm not one of those geniuses. You're talking about people like mattigroff, cellzealot, p3droid, dhacker, etc. Those are the guys who will crack this issue. What we REALLY need to solve this is the damn 905 FXZ. I've put out a request for it but I have no idea if I'll hear back from the person I asked or even if they have it. If we had that, we have a way forward.
BasPilot said:
I am just failing to see the logic of putting out an open source piece of software that locks you into it. The only thing I can see is that the leaks have bothered the OS builder and this is their way of stopping us from using them.
Click to expand...
Click to collapse
Agreed.
Open source doesn't mean that you can change the finished builds of the software or roll back after you install an update, it just means that you can make your own version using the source. The OS itself is open source, but the phones don't have to be fully open, and none of Motorola's since the DROID have been, at least on VZW.
BasPilot said:
Well that's good for most people, and good that it was able to be spotted before too much damage was done over all...
I am just failing to see the logic of putting out an open source piece of software that locks you into it. The only thing I can see is that the leaks have bothered the OS builder and this is their way of stopping us from using them.
Click to expand...
Click to collapse
The problem is your trying to talk logic while talking about Moto. Experience shows the two don't play well, people have been warning this would probably happen sooner or later throughout the ICS leak cycle.
Well, some of us theorize this marks the end of the ICS leak cycle and represents what's likely to be the soak candidate, but, we'll have to wait and see.
Related
Update #4: I previously thought Motorola would OTA to 2.3.4 instead of 2.3.3 now that I'm seeing 2.3.4 builds. But, it looks like my initial projections were probably right. We'll be looking at 2.3.3 for the Atrix on OTA. Then, there will be a separate update to 2.3.4.
I was recently updated to a newer build: 4.5.47. This build was finalized on 05/24/2011 04:46:02. We've got a month more of builds already, which means the Atrix Gingerbread update should be nearing completion.
Read more about the Atrix Gingerbread update in July here: http://briefmobile.com/atrix-4g-headed-for-july-gingerbread-update
Update #3: Some more video showing the new Blur interface in action. http://briefmobile.com/motorola-blur-on-atrix-with-gingerbread
Update #2: Netflix works flawlessly on the Atrix with Gingerbread! Check it out: http://briefmobile.com/netflix-on-the-motorola-atrix-gingerbread
Update: Looking into three new root possibilities. Progress communication may be limited for certain reasons. Also, I posted new pictures on Facebook.
Here's a preview of Android 2.3.3 for the Atrix 4G!
http://briefmobile.com/motorola-atrix-gingerbread-android-2-3
Details
Code:
Android 2.3.3
Webtop: wt-1.2.0-76_OLY-1
Build: 4.5.40
A nice guy gave me this to see if we can get root and such. He requested that no one have access to the files, and I'll be keeping my promises. Sorry, guys!
Anyways, we can test out root exploits. All of the traditional ones seem blocked, including Gingerbreak. I haven't tried beforeupdate/afterupdate yet. I'll be trying that later.
too good to be true! haha!
Thanks Kenneth!
Just saw this on your website! Very exciting! I can't believe they managed to break gingerbreak on it though. Typical Moto. Is it an update or an SBF that you have?
EDIT: Someone brought this up on IRC. What about webtop?
I was given a service file that doesn't wipe data when it updates. I was pretty sad when I saw that Gingerbreak was borked.
Hope this comes soon. However i won't update anyways. Not unless you can flash back to 1.26.
no disrespect but we all knew it was coming....now a real surprize would be a download link
martyotaku said:
no disrespect but we all knew it was coming....now a real surprize would be a download link
Click to expand...
Click to collapse
Fair enough. Can't give that to you. I'm sure a beta program through Moto will be announced soon. Then everyone can get their hands dirty.
Wow, this version of blur actually looks pretty good
Hey Ken. Any idea on when it will be available for non att users? (i.e Bell, Testra)
kennethpenn said:
I was given a service file that doesn't wipe data when it updates. I was pretty sad when I saw that Gingerbreak was borked.
Click to expand...
Click to collapse
I do worry about something though. Everytime I have flashed an SBF file my phone goes back to stock and I have to go through motoblur account setup and all that again.
However, with 1.83 when I flashed the sbf, it didn't really go back to stock. In fact, my fingerprint, go launcher settings, wall paper etc were all still the same.
Did this mean the flashing process didn't work alright?
I ask b/c i wouldn't want to miss a FOTA update of gingerbead.
Finally
Looks dope ! Can't wait
Vigneshd said:
I do worry about something though. Everytime I have flashed an SBF file my phone goes back to stock and I have to go through motoblur account setup and all that again.
However, with 1.83 when I flashed the sbf, it didn't really go back to stock. In fact, my fingerprint, go launcher settings, wall paper etc were all still the same.
Did this mean the flashing process didn't work alright?
I ask b/c i wouldn't want to miss a FOTA update of gingerbead.
Click to expand...
Click to collapse
No. There are two kinds of SBF files. Service SBF files and regular ones. "Service" ones don't wipe the data partition on your device. You're fine!
Ratchet556 said:
Hey Ken. Any idea on when it will be available for non att users? (i.e Bell, Testra)
Click to expand...
Click to collapse
http://briefmobile.com/motorola-atrix-gingerbread-international-simultaneous-update
Hopefully Gingerbread comes out roughly the same time for users on all carriers. We'll see, though. I wouldn't get my hopes up for a simultaneous update.
kennethpenn said:
A nice guy gave me this to see if we can get root and such. He requested that no one have access to the files, and I'll be keeping my promises. Sorry, guys!
Anyways, we can test out root exploits. All of the traditional ones seem blocked, including Gingerbreak. I haven't tried beforeupdate/afterupdate yet. I'll be trying that later.
Click to expand...
Click to collapse
Kennethpenn: Please do be careful. It would be a bummer if you found a small tweak to gain root, which your nice friend relayed to the big M. You know this, of course.
Thank you for having the class to not simply leak the files. Restores some of my faith in XDA! ;-)
Sent from my MB860 using XDA Premium App
Best news I heard in a long while!
Any chance of benchmarking this sucker?
Looks great! Kinda wish it came with the stock Gbread keyboard though...Oh well, can't hurt to try out an updated Moto keyboard
Kenn, as far as you can tell are we finally able to customize the double-tap home feature, or is Moto still making us use their select apps?
i can't connect to anything on the domain briefmobile.com? lol fail
thebeardedchild said:
Looks great! Kinda wish it came with the stock Gbread keyboard though...Oh well, can't hurt to try out an updated Moto keyboard
Kenn, as far as you can tell are we finally able to customize the double-tap home feature, or is Moto still making us use their select apps?
Click to expand...
Click to collapse
Still limited to about ten. Looks like a longer list, though. And, you can now select "none."
raybond25 said:
i can't connect to anything on the domain briefmobile.com? lol fail
Click to expand...
Click to collapse
Back online. Traffic killed it for a second!
kennethpenn said:
Still limited to about ten. Looks like a longer list, though. And, you can now select "none."
Click to expand...
Click to collapse
Fair enough. The 'none' feature is actually all I really need. The app quickdesk could probably work with the double tap now if none is selected on the Motoblur end. Thanks!
It will perhaps coincide with a lot of new content available for those that are unrooted or are on rooted stock within a couple weeks.
I don't know if you people ever figured out the OTA mechanism for B&N updates for certain. Everytime someone claims they know the answer it ends up like how people who present the definite answer on how LI batteries truly act.
Given that, if you are on rooted stock its probably best to keep your nook off wifi. Unfortunately, it does not act like the original nook which indicates that a software update is being downloaded. It is all done in the background. If you need to connect online, you should be fine as long the connection is broken before a nearly 200 meg file is downloaded to your device. If you are on CM or HC, this obviously doesn't apply to you.
I don't have hard evidence to give you that this is certain because I don't know myself, but I'd advise you to pay attention. If its a nonissue I'll have the mods kill the thread. Good backup habits are highly advised. Mods that don't know how to talk to me quickly probably shouldn't be mods.
I'm curious as to why you believe this. Though it doesn't really apply to me. Also do you have any additional information in which what the update will contain?
feel free to PM me
Any word on what new features will be in 1.3?
cabbieBot said:
feel free to PM me
Click to expand...
Click to collapse
If you really have any information why not post it here?
Sent from my NookColor using Tapatalk
Possibly this has something to do with it? http://www.barnesandnoble.com/nook/container/standard_bothnavs.asp?PID=35681
Skip that.... it is for the new Nook......
cabbieBot said:
I don't know if you people ever figured out the OTA mechanism for B&N updates for certain. Everytime someone claims they know the answer it ends up like how people who present the definite answer on how LI batteries truly act.
Click to expand...
Click to collapse
Nope, changing the build prop just works. Wife's NC has been at 1.0.1 since December. When 1.1.0 (?) came out I updated her build prop and it's never updated since.
http://forum.xda-developers.com/showthread.php?t=930382
told ya'll so
khaytus good lord update that womans nook!
cabbieBot said:
told ya'll so
khaytus good lord update that womans nook!
Click to expand...
Click to collapse
She doesn't want me messing with what works ;-) although she is preoccupied with her new toy, Touchpad.
So i flashed 5.7.893 to solve my data issues knowing the consequences. I also assumed that some smart dev would eventually formulate a fix to make everything peachy again when the time came. The way I understand it now is this though.
Locked boot loader makes it necessary to have signed files to update via ota path.
OTA files are designed to only update from a certain version. Ex 5.5.893 update can only be applied from 5.5.886 stock install.
So if I upgraded to 5.7.893 no official update is going to ever work because I can't flash my radio to anything official now.
I'm sure I left out or have some details wrong. But if someone has a better understanding ans cares to share it that would be great. Stop the forever speculation about getting on path again and we can all just wait for the actual fix.
The way I'm understanding it now, we need an official release from moto that specifically addresses this problem to fix it. Something I wouldn't think they are inclined to do because they don't want anyone doing it in the first place.
Sent from my DROID BIONIC using XDA App
a replacement phone. Everything else is speculation at this point.
Irony.....
1) Verizon releases a phone with very problematic data problems. For me doesn't really do much to address the issue. Still paid 30$/month for "unlimited" data.
2) Motorola lets files "leak" that could potentially fix these problems.
3) Motorola does not support these files and will tell you your wrong for using them.
Let's think about this for a second. If you put a hot dog in front of a starving man and walk away, do you really have cause to be pissed when you return to see the hot dog gone?
I have owned a wide range of "smart" phones now and come to realize that they all have shortcomings, but they all need to do a few things without fail. Make phone calls, send text messages, and connect to data services. If you are going to charge me 30$ a month for unlimited data, I should have unlimited data.
Where we wrong by using an update that wasn't official? Nah, I was starving and that hot dog had my name written all over it.
Motorola did not "let the file leak", they were pulled from their test servers by very deliberate acts of altering the firmware of the device and then scanning the servers for files and downloading them.
This is akin to stealing them and was no fault of Motorola's other than perhaps a lax cloud server security regime.
The problem comes when such methods are proliferated and made into simple tools and users are encouraged to avail themselves without sufficient warnings about the risks and responsibilities associated with that act.
Nonetheless, these are clearly our own choices and we cannot expect Motorola to even publicly acknowledge the issue, even while we hope for a solution to be provided by whatever means.
cellzealot said:
Motorola did not "let the file leak", they were pulled from their test servers by very deliberate acts of altering the firmware of the device and then scanning the servers for files and downloading them.
This is akin to stealing them and was no fault of Motorola's other than perhaps a lax cloud server security regime.
The problem comes when such methods are proliferated and made into simple tools and users are encouraged to avail themselves without sufficient warnings about the risks and responsibilities associated with that act.
Nonetheless, these are clearly our own choices and we cannot expect Motorola to even publicly acknowledge the issue, even while we hope for a solution to be provided by whatever means.
Click to expand...
Click to collapse
I call B/S. Anyone that doesn't believe that Moto could have sequestered those files is dead wrong. They were there for a purpose. And they served their purpose.
Their refusal by inaction, to support those of us who "tested" their OTA's for them is at the very least unethical.
That is the way business works in 2011. Screw the consumer, let's make more money.
RMD
cellzealot said:
Motorola did not "let the file leak", they were pulled from their test servers by very deliberate acts of altering the firmware of the device and then scanning the servers for files and downloading them.
This is akin to stealing them and was no fault of Motorola's other than perhaps a lax cloud server security regime.
The problem comes when such methods are proliferated and made into simple tools and users are encouraged to avail themselves without sufficient warnings about the risks and responsibilities associated with that act.
Nonetheless, these are clearly our own choices and we cannot expect Motorola to even publicly acknowledge the issue, even while we hope for a solution to be provided by whatever means.
Click to expand...
Click to collapse
I have read quite a bit of the hard work you've done for us sir, and I would like to say its much appreciated!
A company such as Motorola has the resources to guard the things they don't want others to have. Otherwise HTC, Samsung, LG etc. etc. etc. would always be a step ahead of them. If it was lax security on their part, they still set the hot dog in front of us...
1) The next official OTA is the leaked 5.7.893
2) An OTA down the road doesn't check the boot.img md5 and installs a full boot.img instead of just patching (I think the reason behind the requirement of having the previous version, not to spite the leak installers but to create a smaller download with just a patch).
3) Release singed zips of official OTA radio and boot (not sure why not, its not like anyone could hack these)
I would hope that at least the ICS release will require a new kernel that can't be just a patch but a full install. In that case I would also hope they would take out the md5 check.
How about the 5.9.901 OTA update that Motorola "mistakenly" pushed to users before testing was complete? They are going to have to fix that for those who received the update.
Sent from my DROID BIONIC using Tapatalk
The general thinking I have read is that the 5.9.901 update is a test for an Emergency Notification system that Moto is working on. It was rolled out to random phones for testing and wasn't intended for general release.
---------- Post added at 02:42 PM ---------- Previous post was at 02:36 PM ----------
rduckwor said:
I call B/S. Anyone that doesn't believe that Moto could have sequestered those files is dead wrong. They were there for a purpose. And they served their purpose.
Their refusal by inaction, to support those of us who "tested" their OTA's for them is at the very least unethical.
That is the way business works in 2011. Screw the consumer, let's make more money.
RMD
Click to expand...
Click to collapse
That's kind of a warped way of looking at it. What were people doing poking around in their servers? Are you one of those guys that feels like anything is yours for the taking if the door wasn't locked?
While annoying moto told me that if you applied the leaks it didn't void the warranty so you can send it to them and they will get it back on the update path. Def annoying but there is a way back
Sent from my DROID BIONIC using XDA App
dagostin said:
While annoying moto told me that if you applied the leaks it didn't void the warranty so you can send it to them and they will get it back on the update path. Def annoying but there is a way back
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Very bizarre and impressive that they support this.
Some people in this thread claiming they were able to get back to the upgrade path. From 5.7.893 to .886 stock then ota to 5.5.893
It's alot to read through.
http://rootzwiki.com/topic/12749-getting-back-on-the-ota-update-path/
dagostin said:
While annoying moto told me that if you applied the leaks it didn't void the warranty so you can send it to them and they will get it back on the update path. Def annoying but there is a way back
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Well this is good news if the Moto rep is correct!
Method works. I myself am backon update path now.
Sent from my DROID BIONIC using XDA App
I just got off the phone with VZW. Apparently, they've stopped rolling out the OTA because of "software issues," though he didn't specify beyond that. So, for all of you who have been waiting for the OTA over the past few days, off the top of his head, the tech guesstimated it'll be around a month before they begin rolling it out again. Lame.
Edit: You can still install the .217 leak...but if the update has been pulled for software issues, that obviously means .217 is no longer the official OTA.
What? thats BS! even though im on Eclipse ICS 1.2, its still BS for anyone still on GB!
alex94kumar said:
What? thats BS! even though im on Eclipse ICS 1.2, its still BS for anyone still on GB!
Click to expand...
Click to collapse
Yeah, I've been mashing the "systems update" option habitually now for a couple days, but also avoided just manually updating to the .217 leak for this very reason. Either way, it is kind of disappointing.
honestly, if I were you, I would jump on either the 217 leak, or if you want a custom rom that's slightly themed and has extra features/no bloat, go with Eclipse
It wasn't supposed to be released for the general OTA, they did that on accident, only people who were signed up for the motorola feedback network test were supposed to get it, but for some reason they pushed it to all devices. It should be officially pushed in a week or so, because it appears the soak test isn't showing up any major issues.
Sent from my DROID4 using xda premium
EDIT: Did NOT work
I called VZW tech support earlier today because it was not working and they did not mention anything about it being halted, but it probably depends on which tech you speak with.
I am not sure if this works or not but the guy I spoke with did tell me that performing a factory reset can sometimes trigger the upgrade. I don't have anything on there that I can't live without or easily re-install so I am going to go ahead and give it a shot.
EDIT: Just tried above. Did NOT work
Rafterman414 said:
EDIT: Did NOT work
I called VZW tech support earlier today because it was not working and they did not mention anything about it being halted, but it probably depends on which tech you speak with.
I am not sure if this works or not but the guy I spoke with did tell me that performing a factory reset can sometimes trigger the upgrade. I don't have anything on there that I can't live without or easily re-install so I am going to go ahead and give it a shot.
EDIT: Just tried above. Did NOT work
Click to expand...
Click to collapse
As mentioned above, there was no planned general release yet. Moto did a release for "a few thousand" phones, of which only a small portion are official MFN soak testers. The test will end soon, and it looks like no show-stopper issues have been found, so, if things go as usual, the general release will roll out, probably in groups, over the next several days.
Sounds like the OP spoke to someone in VZ who really didn't know why the release wasn't available and made something up. (And I bet you never thought a VzW rep would do that!)
Keep in mind, even if they had decided to halt it due to a showstopper bug, they've already released it to several thousand owners. Which means they're obligated to provide anyone on .217 with a way to get back onto the upgrade path, if they decide to release a newer update down the road.
All in all - if you're impatient, just install the current .217 files - you'll still be able to upgrade again later if you need to.
Btw: I'm on it now, and I ABSOLUTELY HATE the Dialer and Contacts being split apart into totally separate apps. I always hit the Dialer icon first, and then if I can't remember a person's phone number, I now have to back out of it and look up the contact first. Whereas on GB I just had to select the Contacts tab and go on. So from a human interface perspective, this new design sucks.
highlandsun said:
Keep in mind, even if they had decided to halt it due to a showstopper bug, they've already released it to several thousand owners. Which means they're obligated to provide anyone on .217 with a way to get back onto the upgrade path, if they decide to release a newer update down the road.
All in all - if you're impatient, just install the current .217 files - you'll still be able to upgrade again later if you need to.
Btw: I'm on it now, and I ABSOLUTELY HATE the Dialer and Contacts being split apart into totally separate apps. I always hit the Dialer icon first, and then if I can't remember a person's phone number, I now have to back out of it and look up the contact first. Whereas on GB I just had to select the Contacts tab and go on. So from a human interface perspective, this new design sucks.
Click to expand...
Click to collapse
When your in at the dialer screen just push menu then search it goes to your contact list. So its a matter of hitting 2 buttons but you can get to it from dialer. I also miss the other way but im getting used to this and it doesnt bother me anymore
Sent from my DROID4 using xda premium
It's happened to me twice now in the last two days that I was unable to hear the people calling me. Switching to speaker mode or rebooting the phone fixed this. Actually only rebooting. Alternating between speaker and normal mode is just a temporary fix as long as I'm in speaker mode. Plug in the headset and it works. Take it out en again no sound... I think it happens after I use BT.
Maybe people who are on this update officially could raise a bit of fuss about this and ask to be put back onto Gingerbread?
As we all know this currently can't be done due to the highly restrictive bootloader, perhaps we could wangle a better bootloader out of this?
Lum_UK said:
Maybe people who are on this update officially could raise a bit of fuss about this and ask to be put back onto Gingerbread?
As we all know this currently can't be done due to the highly restrictive bootloader, perhaps we could wangle a better bootloader out of this?
Click to expand...
Click to collapse
Well, we can certainly dream, but given a choice between unlocking the bootloader and shrugging apologetically and insisting nothing can be done, I'm dead sure Verizon will require Motorola to do the latter. :crying:
Installing OTA right now on my wife's D4
Sent from my DROID BIONIC using xda premium
Seems like more people are getting it now. I just got too antsy and went ahead and installed the .217 leak floating around, I bet if I had waited another day I could have gotten the OTA. Hopefully I did not ruin my ability to get future OTA updates.
Sent from my DROID4 using xda app-developers app
Rafterman414 said:
Seems like more people are getting it now. I just got too antsy and went ahead and installed the .217 leak floating around, I bet if I had waited another day I could have gotten the OTA. Hopefully I did not ruin my ability to get future OTA updates.
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
You didn't. .217 is .217 no matter how you got it. Anyone on the "leaked" .217 is on the official update path as that is what was pushed as OTA.
tcrews said:
You didn't. .217 is .217 no matter how you got it. Anyone on the "leaked" .217 is on the official update path as that is what was pushed as OTA.
Click to expand...
Click to collapse
If you had a nickel for every time you had to tell somebody that you could probably retire! LOL
Droid 4 - AOKP K1L0
Update fails anyway
I received the update this morning, and after attempting to install, it fails within 30 seconds and reboots. I factory reset, erasing everything, downloaded the update again, and same result. Anybody have any information on this? I pressed the volume up button and it says:
Verifying current system...
assert failed: apply_patch_check("/system/app/music2.apk", "cbb199983ab1cb9beee6b20ec4db659ccd49d757", "25d8789a15715fdd931ef2a2ee93b637bfef06b0")
E:Error in /cache/Blur_Version 6.13.219.XT894.Verizon.en.US.zip
(Status 7)
Installation aborted.
Saloobian said:
I received the update this morning, and after attempting to install, it fails within 30 seconds and reboots. I factory reset, erasing everything, downloaded the update again, and same result. Anybody have any information on this?
Click to expand...
Click to collapse
Just install from a PC via FastBoot.
ROM: http://sbf.droid-developers.org/cdma_maserati/list.php
Instructions: http://www.droidforums.net/forum/dr...otorola-droid-4-xt894-stock-windows-only.html
Note. Do not download one of the two ROMs that post suggests, use the 217 ROM from my link above. Do not attempt to downgrade via this method either, it will not work. You might also want to skip steps 6-9 if you don't want to reset your data. Not sure how well this will work after an upgrade.
The soak test is over and "the software is officially released and will be rolling out in stages"....
Sent from my DROID4
:good:
Fantastic! I restored to stock and downloaded the update again, and it's currently installing without a hitch! Thanks!
RELEVANT TO US BECAUSE WHEN WE GET THE UPDATE, IT LOCKS THE BOOTLOADER.
IF THEY LOCK IT FOR THE S6 EDGE, THEY'LL LOCK IT FOR THE S6!
DO NOT TAKE THE OTA IF YOU DON'T WANT A LOCKED BOOTLOADER.
Unassuming Galaxy S6 edge users are in for a surprise, as T-Mobile appears to be rolling out a freshly cooked OTA based on Android version 5.1.1 Lollipop for the device. The catch, however, it is so far reported only on the T-Mobile network.
XDA forums user Sunderwear mentioned about the OTA a couple of hours back (at the time of writing this story). Urged by other users of the device, the poster also uploaded a video of his Galaxy S6 edge running the latest firmware. The video can be found at the end of this article.
As noted from the narration, the update also locks the bootloader on the device.
So, how many of you have already received the update? What do you think of it?
Source: http://www.sammobile.com/2015/04/29/android-5-1-1-ota-being-rolled-out-on-t-mobile-for-the-s6-edge/
Looks like someone in the Edge forum was able to downgrade the bootloader and flash TWRP but still, tread carefully.
Sunderwear said:
ok I downgraded the Bootloader ONLY and I was able to flash TWRP...dumping a system.img copy..
Click to expand...
Click to collapse
Honestly I'm caring less and less about roms but I like the option. Here is some possible good news from a trustworthy guy
jcase said:
Korean variants seem to be getting an app that unlocks the bootloader, I bet we start seeing that for other variants as well (except verizon/att).
This is a good thing, not a bad thing people!
Click to expand...
Click to collapse
ThePagel said:
Honestly I'm caring less and less about roms but I like the option. Here is some possible good news from a trustworthy guy
Click to expand...
Click to collapse
Coming from the ROM Flashing mecca of HTC and finding a place in Samsung is.. weird to say the least. I find that there are only minor things I need that require root but I no-longer need the overhaul that I needed with HTC. It's too weird.
nolimit78 said:
Coming from the ROM Flashing mecca of HTC and finding a place in Samsung is.. weird to say the least. I find that there are only minor things I need that require root but I no-longer need the overhaul that I needed with HTC. It's too weird.
Click to expand...
Click to collapse
I see you edited your signature!
If/when anyone gets this update try to grab the update before taking it. Also, the bootloader Doesn't actually get locked.
mikeyinid said:
If/when anyone gets this update try to grab the update before taking it. Also, the bootloader Doesn't actually get locked.
Click to expand...
Click to collapse
BOOM. Bootloader news is great news
Isn't it odd that just one guy has gotten the update? T-mobile has sold hundreds of thousands of these units and only one guy got an OTA?
I'll believe it when I see it.
Is it possible to do the update if we are rooted? And I mean UPDATE not flash the entire new release.
ipaq_101 said:
Isn't it odd that just one guy has gotten the update? T-mobile has sold hundreds of thousands of these units and only one guy got an OTA?
I'll believe it when I see it.
Click to expand...
Click to collapse
This type of thing might happen with a lot of updates. You need to remember the rooting/moding community is very small compared to the people who just use their phone as is. So if anything I think its weird that someone in this community got the update.
Hey I hope it's true, I for one hope it fixes the memory management and battery issues.
According to this guy, it looks like the XDA member was part of a "Soak Test", or he is a guinea pig. Hopefully it doesn't take months to test it.
http://www.forbes.com/sites/gordonk...5-1-1/?utm_campaign=yahootix&partner=yahootix
ipaq_101 said:
Isn't it odd that just one guy has gotten the update? T-mobile has sold hundreds of thousands of these units and only one guy got an OTA?
I'll believe it when I see it.
Click to expand...
Click to collapse
it's a leak...also camera is buggy...not a final version
ipaq_101 said:
Hey I hope it's true, I for one hope it fixes the memory management and battery issues.
According to this guy, it looks like the XDA member was part of a "Soak Test", or he is a guinea pig. Hopefully it doesn't take months to test it.
http://www.forbes.com/sites/gordonk...5-1-1/?utm_campaign=yahootix&partner=yahootix
Click to expand...
Click to collapse
Never.... EVER... take anything from that website serious.
JoeFCaputo113 said:
Never.... EVER... take anything from that website serious.
Click to expand...
Click to collapse
Haha yeah, tech reporters are a bunch of iMorons as it is and love iCrap over everything else. I was shocked that they even knew what xda was.
Someone has the balls to try it on the non-edge S6?
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/development/5-1-1-blck-tw-t3096994
timeToy said:
Someone has the balls to try it on the non-edge S6?
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/development/5-1-1-blck-tw-t3096994
Click to expand...
Click to collapse
I hope no one tries this. Both devices are TOTALLY different.
J-Hop2o6 said:
I hope no one tries this. Both devices are TOTALLY different.
Click to expand...
Click to collapse
They're really not, actually. I imagine it would boot. My guess is touch screen wouldn't work though.
mikeyinid said:
They're really not, actually. I imagine it would boot. My guess is touch screen wouldn't work though.
Click to expand...
Click to collapse
Yea, I remember reading about the touch screen not working or working in reverse.
J-Hop2o6 said:
Yea, I remember reading about the touch screen not working or working in reverse.
Click to expand...
Click to collapse
Really? So it might work but register touches opposite of our phone?
nolimit78 said:
I find that there are only minor things I need that require root but I no-longer need the overhaul that I needed with HTC. It's too weird.
Click to expand...
Click to collapse
This
Damn I wish this would leak for AT&T. 5.0.1 TW has a bigger memory leak than stock 5.0.1 on my Nexus. This needs to be rolled out ASAP, but I know it won't.