Official - the 4.X.X update - discussion thread
- Thread starter Naddict
- Start date
If you don't like what you have, go away or make it yourself.
Entitlement is why developers don't so stuff.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Lucky you !!!
Getting the same error every time:
"/system/bin/app_process" has unexpected contents.
Error in /tmp/update.zip
(Status 7)
Hey hey hey, relax. Not all of us are as aware of the various social and political underpinings of the devs and sometimes we say things not out of disrespect, but out of, I admit, ignorance. We still appreciate everything the devs do. We just aren't always as aware of the limitations or difficulties devs face when working with these challenges. Cut this guy some slack, it looks like he just doesn't understand the full ramifications of what he's asking.
For me personally, there's a lot I never understood about Android from my first time flashing a Gingerbread ROM over a Froyo one. And since then, the OEM's and the carriers have become very clever at trying to keep us out (which to me is highly unethical but what's new right?), so the methods devs and amateur tinkerers have devised to counteract and understand the newer Android challenges escapes me these days. I can follow along with just enough to (carefully) reproduce results via listed steps, but I also can follow along enough to screw things up quickly if I'm not careful, and maybe accidentally frustrate a dev or amateur tinkerer via misspoken questions. So relax. Nobody needs your wrath, just be patient with us novices. REMEMBER: for a lot of us, this isn't just a toy, it's our daily use phone.
That said, I am seeing this thread has focused more on those who are failing to install the update and how to resolve their issues. My interest is more about the various changes once the update works.... the obvious ones, and the not-so-obvious ones. Therefore, I started this thread:
http://forum.xda-developers.com/showthread.php?p=51457774
If your update WORKED, and you want to start discussing CHANGES, go there please and let's give these people with issues updating some room to work here.
A little off-topic, but I feel the community here as a whole has gotten a lot more entitled over the years. And it's not a good thing.
A lot of whining and complaining going on about why we don't have certain things, or why someone's device is messed up and can't take an OTA, or just basic 'AT&T sucks for doing this, this should be completely open to us, this is ALL their fault!'
I'm not addressing anyone in particular. But it's been awhile since I've been an overly active member here. When I had the G1, I learned all about obtaining root and flashing over to CM. When I upgraded to the Vibrant, it was all about fixing their dumb, outdated file system to fix the lag. Everyone in the community during those times helped each other, never demanded anything, never complained about why things were the way they were. There was an understanding that we're performing functions that consumers shouldn't be doing, and when something got messed up, when we bricked our devices, we didn't curse Samsung or HTC or the carriers, we took it as a learning experience with an understanding that with each bootloader exploit or flash of a ROM, we could sometimes permanently mess something up.
It's a totally different atmosphere. The people that come here looking to root don't even know WHY they want root privileges. They're only told that "rooting is always better", so they follow some One-Click program with no knowledge of what they are doing and no care that they are messing with the system partition, which might make taking future OTAs a useless endeavor. Some delete bloatware .apks altogether, not realizing that without them, there's no updating via official means. And no one ever backs them up, of course.
And that's all well and good. Like I said, it's all a learning experience. You learn by messing up, and not making the same mistakes. Cool. But, don't come here and complain that it's everyone else's fault but your own, and then get mad when the people who donate their time and efforts to provide for this community don't have an answer or a fix.
Well you do make some good points. I agree that a lot of people want to run blindly into tinkering with their phone without really understanding any of the process or motivations that should be for it. But there are also a lot of dev topics that are way above the heads of some of us. There needs to be a middle ground, and regardless of what that middle ground is, we need to keep it *civil*. XDA has a great reputation for keeping things civil compared to other forums, that's my point. Let's keep it like that 
Now, as far as I can tell, the problem IS carrier-related, as other OTA's aren't having this issue. Should root cause this? No, you'd think. But... AT&T is one of the meanest when it comes to nutjob ways of shafting customizers. So this doesn't surprise me one bit. Either it's just poorly executed as some have suggested, or downright intended. Either way, it does feel like a carrier blame scenario from what I've been reading (and I've read every page closely).
Now, as far as I can tell, the problem IS carrier-related, as other OTA's aren't having this issue. Should root cause this? No, you'd think. But... AT&T is one of the meanest when it comes to nutjob ways of shafting customizers. So this doesn't surprise me one bit. Either it's just poorly executed as some have suggested, or downright intended. Either way, it does feel like a carrier blame scenario from what I've been reading (and I've read every page closely).
Dummies Steps
I am on MJ5 and then downloaded the small update at& OTA some 38Mb.
Need dummies step to get kk as OTA fails to update my device like everyone else.
Kindly advise
I am on MJ5 and then downloaded the small update at& OTA some 38Mb.
Need dummies step to get kk as OTA fails to update my device like everyone else.
Kindly advise
Rooted on NB4, no custom roms or anything. Update failed. Now when I want to try and continue update it has to check again and says I can't for 24 hours. It downloaded the update, any idea where that downloads to so I can pull it with root explorer or do I really need to download this again?
Assuming you've already got the OTA file, you just need to install or extract the adb files from the Android SDK. Nice thing about using this method is it doesn't wipe the phone.
Once you have everything in a folder, you reboot your phone into Recovery and select Apply Update from ADB (versus from External Storage).. it then tells you the command, but you just type, "adb sideload update.zip" (without quotes).
Here's a link for a walk through with a Nexus, same process.
http://www.androidauthority.com/nexus-4-android-4-2-2-ota-update-rolling-out-now-156097/
You make valid points to have your opinion, and I respect it.Well you do make some good points. I agree that a lot of people want to run blindly into tinkering with their phone without really understanding any of the process or motivations that should be for it. But there are also a lot of dev topics that are way above the heads of some of us. There needs to be a middle ground, and regardless of what that middle ground is, we need to keep it *civil*. XDA has a great reputation for keeping things civil compared to other forums, that's my point. Let's keep it like that
Now, as far as I can tell, the problem IS carrier-related, as other OTA's aren't having this issue. Should root cause this? No, you'd think. But... AT&T is one of the meanest when it comes to nutjob ways of shafting customizers. So this doesn't surprise me one bit. Either it's just poorly executed as some have suggested, or downright intended. Either way, it does feel like a carrier blame scenario from what I've been reading (and I've read every page closely).
And this is where a lot of people will disagree with me completely about things...Sure, you can be irked that AT&T or Verizon or whoever locked down their variant harder than the other guy. But I also think that a lot of people don't play devil's advocate enough and look at it from their end. And when you do, you realize that they aren't doing it to be the bad guy and punish you, they have very valid reasons for doing what they do.
First of all, it's a support nightmare for both Samsung and AT&T. With how easy it is to mess something up, even on the most "open" carrier devices, it takes a lot of time and money to provide provide customer service and technical support to people who mess their devices up doing something that was not intended to be done. ATT/Samsung are businesses looking at profit margins, and they certainly don't want to spend what they don't have to providing support for modified devices. Yes, there should be an understanding that if you do something to mess it up, the fault is your own and you can't go looking to ATT/Sammy for a claim. But yet, how many people in this thread alone just said, "Screw it, I'm calling ATT, I'm going to Best Buy, I'm going to get them to reflash official software." Now imagine how many more people would be doing this if it were "easy" to exploit this device? How much time do you think you're taking away from the 55 year old mother who has legit issues with her cellphone that she didn't cause?
Secondly, it's a security nightmare. Rooting your phone is a very insecure, risky thing to do. So is leaving the bootloader unlocked (in fact, Google's own documentation for the Nexus devices implores you to never leave your bootloader in an unlocked state). Maybe this didn't matter much in the era of the G1 and the first Galaxy S. But as the smartphone market grew to the size it is now, and as people rely more and more on their devices to be secure and private places to store information, that stuff is super important. And the more people that come in here not knowing the real risks of having root access, flashing ROMs that contain unofficial or hacked software, or exploits for bootloaders and Knox, and trying to circumvent it, the more the nasty stuff has a chance at ruining someone's life. Banking information, tax information, credit cards, phone numbers, addresses, etc.
I've posted all of this before, and I was immediately called out for being a shill for the carriers. It seems that if you don't have the theory that ATT is purposefully harming us, you're against the community. I'm not. I love this community. But they have very valid, very important reasons for doing what they do. And you know, if it's not for you, if you want to be able to do all of this stuff without huge risks to your device being bricked....you know, get the Note on T-Mobile. Buy the unlocked version from Samsung. Or get a Nexus device. There are so many options out there for people who like to tinker and don't want the burden of possibly destroying their device. In the days of the G1 and the Vibrant, we didn't have such choices (aside from the N1, of course).
Last edited:
No I get it completely. AT&T, Verizon, etc.... they are a business. It's not good business to have devices that can be screwed with easily to the point of bricking them with novices who will then complain and blame the phone (and the carrier that sold it to them). It's easier to lock it down for the masses and let Play provide customizations that are still quite advanced even without root.
And XDA used to be a smaller community where this wasn't as big an issue, and the novices numbered less in ratio to the amateurs and devs. Where do things go from here? hard to say.
Still... it sucks that OTA doesn't work for some. But really, does that mean that they can't sideload KK? KK isn't *impossible* for those having OTA troubles, right?
And XDA used to be a smaller community where this wasn't as big an issue, and the novices numbered less in ratio to the amateurs and devs. Where do things go from here? hard to say.
Still... it sucks that OTA doesn't work for some. But really, does that mean that they can't sideload KK? KK isn't *impossible* for those having OTA troubles, right?
This just keeps getting better. Tried renaming the cfg to zip. Boot to stock recovery, try to update from external storage Failed to mount.
I have seen that user post with the same attitude before. This is where I had enough of it. Most of the noobs come in without reading the rules, without having any inkling to learn, etc, then they expect stuff to just be done for them. This is a development site. Not a support site. That is only added to help take the weight off of the devs, RCs, RTs, and mods. But first this is development. People are too selfish these days and way too damn demanding. I honestly think we should implement a sort of test on the rules during sign up to hammer the rules into the thick skulls of the masses that flood this site expecting stuff.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Sent from my SM-N9005 using XDA Premium 4 mobile app
You received the failed to mount error while having the external SD card in your phone?This just keeps getting better. Tried renaming the cfg to zip. Boot to stock recovery, try to update from external storage Failed to mount.
Anyways. Back on topic, guys.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Sent from my SM-N9005 using XDA Premium 4 mobile app
Yes. SD Card is in my phone
---------- Post added at 10:00 PM ---------- Previous post was at 09:55 PM ----------
Is there a way to use internal? I try to copy this update to /cache and it fails because of space? This is annoying
All I got to say is the phone is a alot better than before, very smooth and the gps finally works right. I just wish there was a way to hack the tether again.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Sent from my SAMSUNG-SM-N900A using Tapatalk
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone