Database Users

DK28 is posted NOT 100% its final Sorry

http://android.clients.google.com/p...0/1506bdf2e04b.update-SPH-D700_DI18ToDK28.zip
Thats the raw file from Sprint and Google this is not rooted and will break recovery

isn't this the same as the one that being posted everywhere else?

Yes.. Lol...
Sent from my SPH-D700 using XDA App

Exactly which there is a 99 % chance of it being a RC since it's still very buggy and flawed, nevermind the fact google is hosting it.
Sent from my SPH-D700 using Tapatalk

of course sprint is calling this a leaked experimental release. But i give them credit for at least making moves in the right direction for froyo. I see alot of happy users so far with minor issues.

styckx said:
Exactly which there is a 99 % chance of it being a RC since it's still very buggy and flawed, nevermind the fact google is hosting it.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
'thats right from SPRINT people jeez IT IS THE FINAL release goto your sprint account then to your phone support see what it says!!!

rjmjr69 said:
'thats right from SPRINT people jeez IT IS THE FINAL release goto your sprint account then to your phone support see what it says!!!
Click to expand...
Click to collapse
And what does it say for you?
The only things I can find on Sprint's site -- the most recent posts from Sprint admin as of last night -- expressly deny that there has been an offical update:
The official Sprint version of the upgrade has not been released. When it is, I will post a thread to the Samsung Epic forum and update the Samsung Epic Maintenance Release blog. If you want to receive a notification when it's available, subscribe to the blog.
Click to expand...
Click to collapse

This is what my sprint account says:
Version
Date released
Description of enhancements/fixes
S700.05S.DI18 9/30/2010 This update fixes:
- Device not going into sleep mode when using Wi-Fi
- Amazon MP3 not downloading in 4G
- Bluetooth root issue
- Large email lag in upload speeds
- Code to enable faster 3G upload speeds
S700.05S.DI07 9/16/2010
This update:
- Adds Samsung Media Hub
- Fixes 4G de-registration when activating mobile hotspot
S700.0.5S.DG27
8/30/2010
Initial Release
Click to expand...
Click to collapse
Nothing at all about dk28

no more GPS?
I don't see anything at all on my Sprint page about this update or even anything specific to the version of software on my phone.
I installed this update earlier today and the GPS on my phone no longer works. It worked before and I never noticed any problems or delays that others reported. I've tried wiping the data and cache numerous times and even re-installing the upgrade but nothing seems to work.
Does anyone have any other suggestions on what I might try? At this point I question whether or not this is the same update we'll receive OTA...
Thanks,
Scott

scott47 said:
I don't see anything at all on my Sprint page about this update or even anything specific to the version of software on my phone.
I installed this update earlier today and the GPS on my phone no longer works. It worked before and I never noticed any problems or delays that others reported. I've tried wiping the data and cache numerous times and even re-installing the upgrade but nothing seems to work.
Does anyone have any other suggestions on what I might try? At this point I question whether or not this is the same update we'll receive OTA...
Thanks,
Scott
Click to expand...
Click to collapse
PEople have had this issue including myself. The update is rolling out state by state units hardware 4 first then 5 should be started later today.
I had to ODIN back to di18 to get my GPS to lock now its amazingly accurate

rjmjr69 said:
PEople have had this issue including myself. The update is rolling out state by state units hardware 4 first then 5 should be started later today.
I had to ODIN back to di18 to get my GPS to lock now its amazingly accurate
Click to expand...
Click to collapse
Can you please write the exact steps to follow and give links to the files you used?? ie pit/odin/.md5
Also did you do a complete wipe or not? if not complete wipe.. which .md5 file you used. Thanks !

rjmjr69 said:
PEople have had this issue including myself. The update is rolling out state by state units hardware 4 first then 5 should be started later today.
I had to ODIN back to di18 to get my GPS to lock now its amazingly accurate
Click to expand...
Click to collapse
So you think Sprint's plan is to push this update to everyone OTA and then have all the end-users install Odin and fix it? Even while denying that there is such a release? Hilarious!
This is not an official rollout. It is a leak. Those who install it, and are comfortable with some level of hacking, may proceed at their own risk, as usual.
But no one should believe this is an official release from Sprint.

hardrock121 said:
Can you please write the exact steps to follow and give links to the files you used?? ie pit/odin/.md5
Also did you do a complete wipe or not? if not complete wipe.. which .md5 file you used. Thanks !
Click to expand...
Click to collapse
That would be great.

Is it actually worthwhile to update from dk17 to dk29? I'm not really having any issues on dk17. Might just wait to confirm its final before going through the reinstall process.

boomerbubba said:
So you think Sprint's plan is to push this update to everyone OTA and then have all the end-users install Odin and fix it? Even while denying that there is such a release? Hilarious!
This is not an official rollout. It is a leak. Those who install it, and are comfortable with some level of hacking, may proceed at their own risk, as usual.
But no one should believe this is an official release from Sprint.
Click to expand...
Click to collapse
Um.. That makes no since..
He had to odin BACK to di18 because he installed a leak..
the official is based off the knowledge of the user never hacking the phone and leaving it stock.
Therefore; no the average user will not need to use odin.. infact won't even know about it.
But those who have come to xda WILL need to odin back to stock di18 in order for the official Froyo to work when it is launched.

boomerbubba said:
So you think Sprint's plan is to push this update to everyone OTA and then have all the end-users install Odin and fix it? Even while denying that there is such a release? Hilarious!
This is not an official rollout. It is a leak. Those who install it, and are comfortable with some level of hacking, may proceed at their own risk, as usual.
But no one should believe this is an official release from Sprint.
Click to expand...
Click to collapse
Why did you edit your post and remove the link? and what proof do you have to say its not final?
Why did you remove your links and??? this is your original post below
And what does it say for you?
*The only things I can find on Sprint's site* -- the most recent posts from Sprint admin as of last night (http://community.sprint.com/baw/message/237583#237583) -- *expressly deny that there has been an offical update*:
"The official Sprint version of the upgrade has not been released. When it is, I will post a thread to the Samsung Epic forum and update the Samsung Epic Maintenance Release blog (http://community.sprint.com/baw/com.../2010/11/08/samsung-epic-maintenance-releases). If you want to receive a notification when it's available, subscribe to the blog.

boomerbubba said:
So you think Sprint's plan is to push this update to everyone OTA and then have all the end-users install Odin and fix it? Even while denying that there is such a release? Hilarious!
This is not an official rollout. It is a leak. Those who install it, and are comfortable with some level of hacking, may proceed at their own risk, as usual.
But no one should believe this is an official release from Sprint.
Click to expand...
Click to collapse
Suppose you got an update OTA. Wouldn't you consider it official?
If you have followed the original thread (which has been closed), the update happened OTA to a non-Sprint person. That is why many people claim it's official.

Why would Samsung release DK28 as official Froyo full of bugs when their Eclair builds were flawless? It doesn't make any sense. I sure wish people would stop saying that this is the official release and confusing new people. This is NOT the official release. There is NO evidence for that. Its NOT a finished product at this point.

acegolfer said:
Suppose you got an update OTA. Wouldn't you consider it official?
If you have followed the original thread (which has been closed), the update happened OTA to a non-Sprint person. That is why many people claim it's official.
Click to expand...
Click to collapse
UGH. How many times does this need to be explained? He had a .4 hardware revision. .4 hardware revisions are for TESTERS. He received the update OTA because SOMEHOW he got ahold of a hardware revision that only TESTERS should have. This has all been discussed a thousand times.
Also, if this WAS the official release it would be a disaster for sprint.

rjmjr69 said:
Why did you edit your post and remove the link? and what proof do you have to say its not final?
Why did you remove your links and??? this is your original post below
And what does it say for you?
*The only things I can find on Sprint's site* -- the most recent posts from Sprint admin as of last night (http://community.sprint.com/baw/message/237583#237583) -- *expressly deny that there has been an offical update*:
"The official Sprint version of the upgrade has not been released. When it is, I will post a thread to the Samsung Epic forum and update the Samsung Epic Maintenance Release blog (http://community.sprint.com/baw/com.../2010/11/08/samsung-epic-maintenance-releases). If you want to receive a notification when it's available, subscribe to the blog.
Click to expand...
Click to collapse
I didn't remove the link. It still works. But the Sprint site is very slow today. If you manage to get through, you will see that the quote above is accurate.

2.2.1 OTA Status thread

Okay, this was just an idea I had, but lets see if it works... assuming everyone can keep it civil here.
Post here when you receive the update, and put in the following information:
Date/Time Updated
Previous build (DI18, DG27, etc)
Geographic location
Months/Years with Sprint
With that information, maybe we can build a pattern and have an idea of when everyone's updates are scheduled.
Edit to add: Apparently release has been pushed to 9PM PST/12A EST-2/22/11

Good idea
Sent from my SPH-D700 using XDA App

nice job bro was just going on here to make a thread like this. im guess its going to start after 9 am est. thats just my guess.

Good ideal. I was about to start the same thread.
Superbovine said:
Okay, this was just an idea I had, but lets see if it works... assuming everyone can keep it civil here.
Post here when you receive the update, and put in the following information:
Date/Time Updated
Previous build (DI18, DG27, etc)
Geographic location
Months/Years with Sprint
With that information, maybe we can build a pattern and have an idea of when everyone's updates are scheduled.
Click to expand...
Click to collapse

Superbovine said:
Geographic location
Click to expand...
Click to collapse
You do know that this has nothing to do with you getting the update, right?

Don't the Android phones have some sort of internal identifier??? Kind of like Blackberry having PIN numbers. I thought Android had an internal identifier unique to each unit.
If so, they could be enabling a block of identifiers at a time.

If nobody on this forum has received the update yet, I would have to imagine it has not begun. However, androinica.com is reporting that it has begun.

the que goes by ESN lowest numbers get it before higher numbers. someone will post it on the net as soon as someone with half a brain gets the update.

I just checked my phone.... nothing YET and I'm in California near S.F. area.

There is someone in the sprint community forums who says they received it already.
http://community.sprint.com/baw/thread/62611?start=45&tstart=0&reqsorting=dec

Milkman00 said:
Don't the Android phones have some sort of internal identifier??? Kind of like Blackberry having PIN numbers. I thought Android had an internal identifier unique to each unit.
If so, they could be enabling a block of identifiers at a time.
Click to expand...
Click to collapse
that issue us irrelevant we just pull the update zip out of the system cache and then the devs will package it pre rooted and then with odin you can get official froyo rooted

ajac said:
the que goes by ESN lowest numbers get it before higher numbers. someone will post it on the net as soon as someone with half a brain gets the update.
Click to expand...
Click to collapse
I was curious about that as well, but obviously no one wants to post their esn here. If that is all it is, then bummer. But I don't know, I don't work for Sprint or anything, that was the point of the thread
Based on the previous information, it sounded like current build had more to do with it than ESN, but again, I don't know, that's the purpose of the thread

Yeah, best we can do is just wait until somebody gets it.
It's like trying to find the Golden Ticket.

Could you guys all stop rambling BS, this thread is going to be 10 pages long before anyone even gets the first OTA. If you guys wanna talk BS why not use this sites chat feature.

I like this thread. Will possibly come in handy for future Sprint updates.
I am flashing back to DI18 now and will post the update.zip if I get it before its posted here.

Guys if you get the update DO NOT INSTALL OR REBOOT. PM one of the developers and we will help you dump the cache. I have heard of several people getting the update but failing during the install process... It hopefully won't be long.

I assume that we'll need to be on the stock rom to get the update. Is that the case? I'm about to flash it back right now...

hysonmb said:
I assume that we'll need to be on the stock rom to get the update. Is that the case? I'm about to flash it back right now...
Click to expand...
Click to collapse
Yes. You will need to be on Stock DI18 with all of the bloat apps installed.

I'm sure someone will release a streamlined update.zip nixing the verification.
Sent from my SPH-D700 using Tapatalk

Those of you flashing back, make sure you don't install it as we don't know if we can even root it yet with current methods.

4.5.91 Upgrade - Is there a "no flash back" warning?

Since I am on KP's 4.5.91 I have not flashed the released OTA.
I see many people already bricking after installing the upgrade, then trying to flash back.
Do you get a warning either before downloading the OTA, or before installing the OTA that you cannot flash to a previous version afterwards?
If not, it's possible you could return your phone, blaming AT&T/Moto for not warning you about backwards flashing.
If there was a warning, sorry, but you will probably be SOL, and it's your own fault for trying to downgrade after installing the OTA.
A bricked device will display 0x1000 on the screen when trying to boot up.
If you see this, go here ---> http://forum.xda-developers.com/showthread.php?t=1160408

Of course not, why would Motorola put in a warning like that. Motorola never excepts you to flash back to an older firmware.
Sent from my MB860 using XDA App

CaelanT,
I updated to gingerbread on rooted atrix 4.1.83. I did not notice any warning as you are hoping. Though the phone's root privilege is no more, Motorola has enabled the sideloading and I am happy with that.
Sent from my MB860 using XDA App

Are you serious?
Why would AT&T or Motorola be to blame for you bricking your device?
There doesn't need to be a "no flash back" warning... If you're 'flashing back' you are most likely using software you're not technically supposed to have to flash firmware you're not technically supposed to have.
It's really tiring reading these forums where people blame everyone but themselves for their bricked device. (Even after the "THIS WILL BRICK YOUR DEVICE" warnings..)

Technically, people shouldn't be able to flash back... we're not supposed to have RSD software or SBFs to flash in the first place.

ebaychuck said:
Why would AT&T or Motorola be to blame for you bricking your device?
There doesn't need to be a "no flash back" warning... If you're 'flashing back' you are most likely using software you're not technically supposed to have to flash firmware you're not technically supposed to have.
It's really tiring reading these forums where people blame everyone but themselves for their bricked device. (Even after the "THIS WILL BRICK YOUR DEVICE" warnings..)
Click to expand...
Click to collapse
Because technically, if they do not warn you that you can ruin your device by flashing to an earlier version, you have a case to sue them if you so choose to go that route. It's their failure to secure the software, updates, and upgrades they have which allows people to flash something you say they should not have, but is freely available to download through software update. Please do not spout what you hear from other people and think this makes you knowledgeable in any way. There are many legal implications with Moto and AT&T not disclosing what their updates/upgrades will or will not do, especially when they say "you will have unlock ability", then switch that at release with no warning, or for any number of reasons.
I can see you have a large contribution to this community by the grand sum of 5 posts which you have.
Now, I am trying to help some of the people out here who were obviously stupid enough to blindly flash an update released to them without first consulting XDA, because of course when you buy the Atrix it tells you to consult XDA on any matters relating to the Atrix!
Go back to ebay where you belong chuck!
BTW..........yes, I am very serious!

So the boot loader on the OTA is still Locked?!!!

yeah you could try that argument. they could give you the run around that you flashed using stuff not from their site or from their customer service portal and there could be some line in the warranty that would cover their ass from that stuff. but hey, worth a shot.

I updated to ota 4.5.9.1 during the soak and there was a big warning on the website, but nothing that I remember seeing when I downloaded and installed the software. They know the risk obviously. Surprised they wouldn't cover their behind during the install.
Sent from my MB860 using XDA Premium App

sservati said:
So the boot loader on the OTA is still Locked?!!!
Click to expand...
Click to collapse
Yes it is.
Beamed from WinBorg 4G via XDA Premium

CaelanT said:
Because technically, if they do not warn you that you can ruin your device by flashing to an earlier version, you have a case to sue them if you so choose to go that route. It's their failure to secure the software, updates, and upgrades they have which allows people to flash something you say they should not have, but is freely available to download through software update. Please do not spout what you hear from other people and think this makes you knowledgeable in any way. There are many legal implications with Moto and AT&T not disclosing what their updates/upgrades will or will not do, especially when they say "you will have unlock ability", then switch that at release with no warning, or for any number of reasons.
I can see you have a large contribution to this community by the grand sum of 5 posts which you have.
Now, I am trying to help some of the people out here who were obviously stupid enough to blindly flash an update released to them without first consulting XDA, because of course when you buy the Atrix it tells you to consult XDA on any matters relating to the Atrix!
Go back to ebay where you belong chuck!
BTW..........yes, I am very serious!
Click to expand...
Click to collapse
As many people have said.. Motorola does not give you any offical path to unlock your bootloader and flash a previous version. People like XDA do.
I have no problem with putting a custom Rom on my phone. I've hacked every device since my first Windows CE pda. The problem I have is with people like you that want to Sue Motorola because they... What? Told you to unlock your bootloader and try to flash unsupported software? No, they didn't.
Oh, and by the way please show me where you got the Official Motorola Atrix Unlock from.

ebaychuck said:
As many people have said.. Motorola does not give you any offical path to unlock your bootloader and flash a previous version. People like XDA do.
I have no problem with putting a custom Rom on my phone. I've hacked every device since my first Windows CE pda. The problem I have is with people like you that want to Sue Motorola because they... What? Told you to unlock your bootloader and try to flash unsupported software? No, they didn't.
Oh, and by the way please show me where you got the Official Motorola Atrix Unlock from.
Click to expand...
Click to collapse
The unlocked Bootloader is one thing, the fact that some users are bricking their phones after using OTA's is another.
Granted the 0X1000 is coming more from XDA users who have flashed, but Motorola needs to embrace the Android community better.
I'm not a fanboy of any company by any means, currently I own both a SGS and an Atrix.
^ With that said, Motorola needs to be a little more like Samsung.
* Paying attention to forums like XDA would be a start. Giving phones for free to developers would be another. (Samsung had no problem doing this).
*Getting rid of the bootloader FOREVER would also be in their best interest.
* Finally not forcing MotoBlur accounts down people's throats would be a friendlier approach as well.
Android consumers have helped Motorola get back in the game.
It's time for Motorola to repay the favor and start treating Android like "Android", and not like an iPhone...

sservati said:
So the boot loader on the OTA is still Locked?!!!
Click to expand...
Click to collapse
From what I've been reading, yes...

ccrows said:
The unlocked Bootloader is one thing, the fact that some users are bricking their phones after using OTA's is another.
Granted the 0X1000 is coming more from XDA users who have flashed, but Motorola needs to embrace the Android community better.
I'm not a fanboy of any company by any means, currently I own both a SGS and an Atrix.
^ With that said, Motorola needs to be a little more like Samsung.
* Paying attention to forums like XDA would be a start. Giving phones for free to developers would be another. (Samsung had no problem doing this).
*Getting rid of the bootloader FOREVER would also be in their best interest.
* Finally not forcing MotoBlur accounts down people's throats would be a friendlier approach as well.
Android consumers have helped Motorola get back in the game.
It's time for Motorola to repay the favor and start treating Android like "Android", and not like an iPhone...
Click to expand...
Click to collapse
Yeah, it would be nice if they'd support their more advanced users like Samsung and HTC have been doing. It seems like they are about to make some kind of change with Motoblur so maybe they'll ease up on the requirement to use it.

ebaychuck said:
Yeah, it would be nice if they'd support their more advanced users like Samsung and HTC have been doing. It seems like they are about to make some kind of change with Motoblur so maybe they'll ease up on the requirement to use it.
Click to expand...
Click to collapse
I've seen the Motoblur "improvements", but you still need an account, which is BS. Plus its a waste of time to freeze things in TiBU.
Between the last OTA that bricked many phones and the current Motoblur BS, I hope we can get Vanilla Gingerbread on this device more than ever. This will definitely be my last Motoblur phone I ever purchase.
Don't get me wrong I like Motorola a lot, but I also like to have a drama free phone...

I have a question for everyone that upgraded to GB.
After reading about the bugs in GB (like the "battery jumping issue" for instance) -
If you "could" go back to Froyo's latest build, would you do it or are you happier with the current GB?...

Nah.
ccrows said:
I have a question for everyone that upgraded to GB.
After reading about the bugs in GB (like the "battery jumping issue" for instance) -
If you "could" go back to Froyo's latest build, would you do it or are you happier with the current GB?...
Click to expand...
Click to collapse
Even with the few problems i'm enjoying having GB.. I guess I just like something new to look at.
I only miss a few things.
- The Happenings page that used to be attached to contacts. It was nice to be able to see the last post a friend made when calling them.
- Access control in Wireless Tether. (I can't remember if it worked on the Atrix or just my previous phone)
- Working Wired Tether..
- Setting review time on the camera.

CaelanT said:
Since I am on KP's 4.5.91 I have not flashed the released OTA.
I see many people already bricking after installing the upgrade, then trying to flash back.
Do you get a warning either before downloading the OTA, or before installing the OTA that you cannot flash to a previous version afterwards?
If not, it's possible you could return your phone, blaming AT&T/Moto for not warning you about backwards flashing.
If there was a warning, sorry, but you will probably be SOL, and it's your own fault for trying to downgrade after installing the OTA.
A bricked device will display 0x1000 on the screen when trying to boot up.
If you see this, go here ---> http://forum.xda-developers.com/showthread.php?t=1160408
Click to expand...
Click to collapse
"Hi Motorola, I'm using non-public tools that have been leaked, and non-public SBF files that have been gotten in an unofficial capacity to downgrade my phone after the latest update. I'm not breaking my warranty, am I?"

Has Samsung given us a reason to quit rooting>

When OF5 came out on Kies I flashed it and waited because I knew that 5.1.1 would be out in just a few weeks and I could live with stock for that long. Then all the tech blogs started breaking stories about new android vulnerabilities. If I'm not mistaken there were 3 new vulnerabilities in the last week, two of which seem like a pretty big deal. Thankfully both Google and Samsung seem to be stepping up to the plate and announced a new monthly update schedule to address these issues. That's a good thing. Now the dilemma:
As we know, you can't get an OTA update on a rooted phone. And Samsung is a bit slow to post updates to Kies and the public. It usually takes 10 days to 2 weeks after an OTA for it to appear, if it does at all. Here's the question:
In this new paradigm do we stay stock to keep current with bug fixes? I know for me it's a tough question. The latest OG5 rom is really good. The only reason I want root at this point is to block ads. Maybe it's time to for me to live with the ads and quit tinkering with the rom. Did I mention OG5 is REALLY good?
Discuss amongst yourselves.

Og5 is rooted now
Sent from my SM-N910P using XDA Premium HD app
---------- Post added at 08:46 PM ---------- Previous post was at 08:46 PM ----------
Thanks to freeza
Sent from my SM-N910P using XDA Premium HD app

pbedard said:
Og5 is rooted now
Sent from my SM-N910P using XDA Premium HD app
---------- Post added at 08:46 PM ---------- Previous post was at 08:46 PM ----------
Thanks to freeza
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
I see that, but that's not my point. Once rooted, you can't take the monthly bug fixes without reflashing totally stock rom. It makes keeping up with monthly patches more difficult.

Not always true and theres no fixes to be done
Sent from my SM-N910P using XDA Premium HD app

poit said:
When OF5 came out on Kies I flashed it and waited because I knew that 5.1.1 would be out in just a few weeks and I could live with stock for that long. Then all the tech blogs started breaking stories about new android vulnerabilities. If I'm not mistaken there were 3 new vulnerabilities in the last week, two of which seem like a pretty big deal. Thankfully both Google and Samsung seem to be stepping up to the plate and announced a new monthly update schedule to address these issues. That's a good thing. Now the dilemma:
As we know, you can't get an OTA update on a rooted phone. And Samsung is a bit slow to post updates to Kies and the public. It usually takes 10 days to 2 weeks after an OTA for it to appear, if it does at all. Here's the question:
In this new paradigm do we stay stock to keep current with bug fixes? I know for me it's a tough question. The latest OG5 rom is really good. The only reason I want root at this point is to block ads. Maybe it's time to for me to live with the ads and quit tinkering with the rom. Did I mention OG5 is REALLY good?
Discuss amongst yourselves.
Click to expand...
Click to collapse
I enjoy tinkering. And putting your security in the basket of "Monthly" updates is a hail mary in the first place.
The only reason Samsung could ever give me to stop rooting would be to give us the devices already rooted.

Amen to that

poit said:
When OF5 came out on Kies I flashed it and waited because I knew that 5.1.1 would be out in just a few weeks and I could live with stock for that long. Then all the tech blogs started breaking stories about new android vulnerabilities. If I'm not mistaken there were 3 new vulnerabilities in the last week, two of which seem like a pretty big deal. Thankfully both Google and Samsung seem to be stepping up to the plate and announced a new monthly update schedule to address these issues. That's a good thing. Now the dilemma:
As we know, you can't get an OTA update on a rooted phone. And Samsung is a bit slow to post updates to Kies and the public. It usually takes 10 days to 2 weeks after an OTA for it to appear, if it does at all. Here's the question:
In this new paradigm do we stay stock to keep current with bug fixes? I know for me it's a tough question. The latest OG5 rom is really good. The only reason I want root at this point is to block ads. Maybe it's time to for me to live with the ads and quit tinkering with the rom. Did I mention OG5 is REALLY good?
Discuss amongst yourselves.
Click to expand...
Click to collapse
I don't have an answer to that, yet, but it is a good question.

poit said:
I see that, but that's not my point. Once rooted, you can't take the monthly bug fixes without reflashing totally stock rom. It makes keeping up with monthly patches more difficult.
Click to expand...
Click to collapse
But it has always been this way. Your choices to get updates were either return to stock or use a custom ROM where the developer incorporated all the latest patches. I think this started either on the S2 or S3.

The OP makes a good point and it's a very good question. Blocking ads is a huge part of the decision to root. I'm the kind of guy that even though ads are blocked in my favorite apps I'll still pay for the full version to support the dev. However, blocking ads on websites saves me bandwidth, loads the pages faster, produces a cleaner web page for which I feel no guilt in blocking those ads. Beyond ad blocking, titanium backup still remains such a huge part of root for me. I know there are non root ways to back up my data but root is still needed to freeze/uninstal bloat ware, restore old versions of apps that got ruined with newer updates, and other such things. Also, being able to tinker with other "preference" type things such as removing the camera shutter sound still makes rooting necessary for me although the gap is closing.

flyhighx said:
The OP makes a good point and it's a very good question. Blocking ads is a huge part of the decision to root. I'm the kind of guy that even though ads are blocked in my favorite apps I'll still pay for the full version to support the dev. However, blocking ads on websites saves me bandwidth, loads the pages faster, produces a cleaner web page for which I feel no guilt in blocking those ads. Beyond ad blocking, titanium backup still remains such a huge part of root for me. I know there are non root ways to back up my data but root is still needed to freeze/uninstal bloat ware, restore old versions of apps that got ruined with newer updates, and other such things. Also, being able to tinker with other "preference" type things such as removing the camera shutter sound still makes rooting necessary for me although the gap is closing.
Click to expand...
Click to collapse
You might already know but if your stock phone is on vibrate there is no shutter sound. All very good points on reason to root btw. Ads probably annoy me the most. My note 2 running cm12 loads pages faster than this thing lol. Overclocked as well though.
Sent from my SM-N910P using XDA Free mobile app

KennyG123 said:
But it has always been this way. Your choices to get updates were either return to stock or use a custom ROM where the developer incorporated all the latest patches. I think this started either on the S2 or S3.
Click to expand...
Click to collapse
I think what he means is that those patches will now arrive every month. When they arrived every 6 months or more, it wasn't such a big deal. Now, you'd have to flash stock, take the patch OTA, and do whatever you need to once again in order to get the phone back to where you want it -- every month.
So it's tempting not to mess with root now. I already rooted my OG5, so I made my decision. But it's a good question.

DaggettBeaver said:
I think what he means is that those patches will now arrive every month. When they arrived every 6 months or more, it wasn't such a big deal. Now, you'd have to flash stock, take the patch OTA, and do whatever you need to once again in order to get the phone back to where you want it -- every month.
So it's tempting not to mess with root now. I already rooted my OG5, so I made my decision. But it's a good question.
Click to expand...
Click to collapse
I see what you both mean. Of course one option is to skip a month or two and get a few updates at a time. Not sure if there are ROMs that will update with every OTA but if so that is another option.

logikzzz said:
I enjoy tinkering. And putting your security in the basket of "Monthly" updates is a hail mary in the first place.
The only reason Samsung could ever give me to stop rooting would be to give us the devices already rooted.
Click to expand...
Click to collapse
what he said...
---------- Post added at 07:50 PM ---------- Previous post was at 07:43 PM ----------
poit said:
When OF5 came out on Kies I flashed it and waited because I knew that 5.1.1 would be out in just a few weeks and I could live with stock for that long. Then all the tech blogs started breaking stories about new android vulnerabilities. If I'm not mistaken there were 3 new vulnerabilities in the last week, two of which seem like a pretty big deal. Thankfully both Google and Samsung seem to be stepping up to the plate and announced a new monthly update schedule to address these issues. That's a good thing. Now the dilemma:
As we know, you can't get an OTA update on a rooted phone. And Samsung is a bit slow to post updates to Kies and the public. It usually takes 10 days to 2 weeks after an OTA for it to appear, if it does at all. Here's the question:
In this new paradigm do we stay stock to keep current with bug fixes? I know for me it's a tough question. The latest OG5 rom is really good. The only reason I want root at this point is to block ads. Maybe it's time to for me to live with the ads and quit tinkering with the rom. Did I mention OG5 is REALLY good?
Discuss amongst yourselves.
Click to expand...
Click to collapse
great discussion subject and start, poit, and great points everybody!!!... thumbz_up!!! ...

I think it's purely a personal decision to take the monthly updates. Almost always I wait for that one person who has to take the update as soon as it comes out and then hear about the issues they have . For instance when OE1 hit, there were many people having big problems. I'm still on OB7 atm and will be doing 2 updated this week now that we have root. I don't see an issue with staying rooted for a while and then just upgraded when you know things are ok. I truly felt for the people having issues on OE1 and wish I could have helped. I too enjoy tinkering and am a flashaholic at heart. Even if the devs don't update every time there is one, I know there will always be something to flash.

pbedard said:
Og5 is rooted now
Sent from my SM-N910P using XDA Premium HD app
---------- Post added at 08:46 PM ---------- Previous post was at 08:46 PM ----------
Thanks to freeza
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
How can I root my N910P?? I've just upgraded to 5.1.1 via official server of Samsung (by S/W Depart ment of Samsung Vietnam)

Honestly I feel like theres close to no reason to root anymore. All the reason I used to root are now baked into stock roms. I'm going to stay unrooted for a while.
Sent from my SM-N910P using Tapatalk

Rooting is about me having the freedom to control the hardware I paid for.
Personally this means control over privacy, resources and security.
After all the issues with carrier and manufacturer spyware and bloat why would I trust them to completely control my freaking phone?
/not a sheep

mr_binthoi said:
How can I root my N910P?? I've just upgraded to 5.1.1 via official server of Samsung (by S/W Depart ment of Samsung Vietnam)
Click to expand...
Click to collapse
Check out the "Hello 5.1.1 Root" root thread. It's in the Sprint note 4 General area as is this thread.

poit said:
When OF5 came out on Kies I flashed it and waited because I knew that 5.1.1 would be out in just a few weeks and I could live with stock for that long. Then all the tech blogs started breaking stories about new android vulnerabilities. If I'm not mistaken there were 3 new vulnerabilities in the last week, two of which seem like a pretty big deal. Thankfully both Google and Samsung seem to be stepping up to the plate and announced a new monthly update schedule to address these issues. That's a good thing. Now the dilemma:
As we know, you can't get an OTA update on a rooted phone. And Samsung is a bit slow to post updates to Kies and the public. It usually takes 10 days to 2 weeks after an OTA for it to appear, if it does at all. Here's the question:
In this new paradigm do we stay stock to keep current with bug fixes? I know for me it's a tough question. The latest OG5 rom is really good. The only reason I want root at this point is to block ads. Maybe it's time to for me to live with the ads and quit tinkering with the rom. Did I mention OG5 is REALLY good?
Discuss amongst yourselves.
Click to expand...
Click to collapse
poit said:
I see that, but that's not my point. Once rooted, you can't take the monthly bug fixes without reflashing totally stock rom. It makes keeping up with monthly patches more difficult.
Click to expand...
Click to collapse
Samsung has agreed to monthly updates, but has Sprint? How long does it take Sprint to push the updates after Samsung has finished them? Months. Even if Samsung builds new systems every week, the choke point is still your carrier.

Every method of gaining root access relies on exploiting vulnerabilities - those monthly patches are designed, at least in part, to make it even more difficult for us to root our devices. I'd be all for that if we already had a way to get root permissions out of the box, but since those vulnerabilities are our only option...
And being unable to get automatic OTA updates is more of a feature than a problem - it gives you the control to choose when to update, and that you can make sure that update won't break more than it fixes (removing root access, for example)
Sent from my SM-N910P using XDA Free mobile app

Haven't received the update for XT1607

Can someone please confirm that you received this Nougat update from Motorola, for this model ( XT1607 )

kurdacrunch said:
Can someone please confirm that you received this update from Motorola, for this model ( XT1607 )
Click to expand...
Click to collapse
Err...what update?

Davey126 said:
Err...what update?
Click to expand...
Click to collapse
Sorry I didn't specify, thought it was obvious that I am taking about the update to nougat. My bad...

kurdacrunch said:
Sorry I didn't specify, thought it was obvious that I am taking about the update to nougat. My bad...
Click to expand...
Click to collapse
I never received an OTA update notification on two XT1607s (US). Not that it would have done any good as both are bootloader unlocked with a custom recovery (stock recovery and an untouched system partition are two of many prerequisites required to process OTAs). Eventually updated both via TWRP flashable build from this thread. Worked a treat. Encourage reading posts from March 1st forward before deciding your path. Good luck.

kurdacrunch said:
Can someone please confirm that you received this Nougat update from Motorola, for this model ( XT1607 )
Click to expand...
Click to collapse
Spouse's US retail xt1607 is factory stock, boot loader still locked, etc. I hasn't received Nougat yet.

n76 said:
Spouse's US retail xt1607 is factory stock, boot loader still locked, etc. I hasn't received Nougat yet.
Click to expand...
Click to collapse
Me neither and the bootloader is locked, stock firmware, and never rooted, damn...
Thank you.

kurdacrunch said:
Me neither and the bootloader is locked, stock firmware, and never rooted, damn...
Click to expand...
Click to collapse
Speculation: Moto isn't pushing updates to XT1607s (why would they) leaving the decision to carriers who could care less about unbranded G4P variants. At some point you will probably have to unlock the bootloader and apply updates manually.
Note this does NOT require replacing stock recovery as booting TWRP will get the job done. Or install directly from fastboot (harder with no benefit IMHO).

Davey126 said:
Speculation: Moto isn't pushing updates to XT1607s (why would they) leaving the decision to carriers who could care less about unbranded G4P variants. At some point you will probably have to unlock the bootloader and apply updates manually.
Note this does NOT require replacing stock recovery as booting TWRP will get the job done. Or install directly from fastboot (harder with no benefit IMHO).
Click to expand...
Click to collapse
My main concern is to use a rom that may be potentially dangerous. Still I guess I'll have to do it in the future. Also, I think Moto should have a desktop app so the people can update it painless, but anyway, I agree with you.
Thank you to all of you, you were great.
Thumbs up for the community!

kurdacrunch said:
My main concern is to use a rom that may be potentially dangerous. Still I guess I'll have to do it in the future. Also, I think Moto should have a desktop app so the people can update it painless, but anyway, I agree with you.
Thank you to all of you, you were great.
Thumbs up for the community!
Click to expand...
Click to collapse
Thanks for the kind words.
I wouldn't be too concerned with stock Marshmallow. Overall security profile will be slightly diminished but can be effectively offset through good hygiene: avoid extensive use of public WiFi, surf responsibly, careful with clicks, don't download 'crapware', only use trusted stores, etc. Google Play Services also offers a layer of protection that remains current regardless of ROM status.
Still, should you be worried given all the media drama about the latest exploit impacting tens of millions of devices? Depends on behaviors that are entirely within your control. I sleep well at night regardless of patch status on my varied devices. Update when it is convenient and for refinements in Nougat that may improve your overall productivity and enjoyment.

Davey126 said:
Thanks for the kind words.
I wouldn't be too concerned with stock Marshmallow. Overall security profile will be slightly diminished but can be effectively offset through good hygiene: avoid extensive use of public WiFi, surf responsibly, careful with clicks, don't download 'crapware', only use trusted stores, etc. Google Play Services also offers a layer of protection that remains current regardless of ROM status.
Still, should you be worried given all the media drama about the latest exploit impacting tens of millions of devices? Depends on behaviors that are entirely within your control. I sleep well at night regardless of patch status on my varied devices. Update when it is convenient and for refinements in Nougat that may improve your overall productivity and enjoyment.
Click to expand...
Click to collapse
Agree, but what I am afraid is how this rom is really untouched. Is there a safe download somewhere?

kurdacrunch said:
Agree, but what I am afraid is how this rom is really untouched. Is there a safe download somewhere?
Click to expand...
Click to collapse
Provided link in a previous post (few days back).

Davey126 said:
Provided link in a previous post (few days back).
Click to expand...
Click to collapse
Thank you!

Davey126 said:
Provided link in a previous post (few days back).
Click to expand...
Click to collapse
Sorry to bother you again, but I have some doubts, I did check out the link, the date of this have more than a year, are you sure this is not the soak test?
Also I would like to keep my phone as pristine as possible, and I have a while since I am not messing with roms, my question is what do I need to make this work?
PD: Using the console is not an issue

kurdacrunch said:
Sorry to bother you again, but I have some doubts, I did check out the link, the date of this have more than a year, are you sure this is not the soak test?
Also I would like to keep my phone as pristine as possible, and I have a while since I am not messing with roms, my question is what do I need to make this work?
PD: Using the console is not an issue
Click to expand...
Click to collapse
Lastest upload is from a few months back (NPI26.48.36) and yields the Nov 1st 2017 patch level. Unfortunately, OP does not exercise any form of formal change control; you'd have to read through the thread to know there were updates. On that note you can read through this thread again and the linked thread (especially from March 1st forward) to gain confidence the upload is legit.
Bigger issue is getting over the pristine hurdle. You will need to unlock the bootloader which immediately voids the warranty and yields an ugly boot screen (which can be remedied). You'll then need to learn TWRP which isn't difficult but not geared toward the average Facebook user. You probably will NOT have to root either the old or new ROM. If any of that feels significantly uncomfortable then the wiser path may status-quo. There are tens of millions of mobiles running Lollipop, KitKat and older ROMs that date back three or more years. The version of Android on you two G4Ps isn't nearly as outdated as you might think.

Davey126 said:
Lastest upload is from a few months back (NPI26.48.36) and yields the Nov 1st 2017 patch level. Unfortunately, OP does not exercise any form of formal change control; you'd have to read through the thread to know there were updates. On that note you can read through this thread again and the linked thread (especially from March 1st forward) to gain confidence the upload is legit.
Bigger issue is getting over the pristine hurdle. You will need to unlock the bootloader which immediately voids the warranty and yields an ugly boot screen (which can be remedied). You'll then need to learn TWRP which isn't difficult but not geared toward the average Facebook user. You probably will NOT have to root either the old or new ROM. If any of that feels significantly uncomfortable then the wiser path may status-quo. There are tens of millions of mobiles running Lollipop, KitKat and older ROMs that date back three or more years. The version of Android on you two G4Ps isn't nearly as outdated as you might think.
Click to expand...
Click to collapse
Thanks again, can't see any reason to rush myself into nougat, anyway is a matter of development and marketing; that we'll see more candies in the near future (not for this smartphone) it's kinda sad we are obliged to buy a new smartphone if you want the security patches, even if it's a very expensive one, but even worse is the incompetence of Lenovo sharing an update through OTA.