Software Uptdare 07/09/13
- Thread starter its_dale
- Start date
still downloading. it took forever to "check for update". Some apps have updates (like Facebook) that give option to add the app to an SD card. This is probably what it is. Im a noob to android btw.. just letting people know an update is out.
I do not think this is wise, but I think the update is a patch that blocks the loki unlock the devs achieved. need to be careful with these updates as the devs have warned us about. I could be wrong here.
Oh well. let us know the outcome if you don't mind.
The Ax says that this is MY OPINION ONLY!
Oh well. let us know the outcome if you don't mind.
The Ax says that this is MY OPINION ONLY!
You are correct - it's usually a good idea to hold off on taking any OTA updates before knowing what they do. To keep from getting OTA updates, use something like Titanium backup to freeze or otherwise disable three specific apps:
I got an upgrade too and it started downloading when I checked but I quickly bought the titanium pro version to freeze the upgrade apps to stop the download until we know if this is some kind of security update
Sent from my SGH-I337 using xda app-developers app
Sent from my SGH-I337 using xda app-developers app
Any other way to stop it? I'm not rooted, but been tempted too lately. If not, can't change what I've done so no worries.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Edited:
I turned off my wifi and it interrupted the update and stopped downloading it. I am not updating till something is released about it.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Edited:
I turned off my wifi and it interrupted the update and stopped downloading it. I am not updating till something is released about it.
Last edited:
DroidLife has some info on it
http://www.droid-life.com/2013/07/0...eed&utm_campaign=Feed:+DroidLife+(Droid+Life)
Mainly a update to KNOX.
Have to see if theres a modem update. If there is thats all thats important for me. And if they patched Loki.
http://www.droid-life.com/2013/07/0...eed&utm_campaign=Feed:+DroidLife+(Droid+Life)
Mainly a update to KNOX.
Have to see if theres a modem update. If there is thats all thats important for me. And if they patched Loki.
Talked to ATT, app2sd, audio clipping issue with headphones fix, removed a wallpaper and added 2 back, and some msging fix. I think there was a few other things as well, he said a security patch as well, but no real information on what.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Well, plenty of warning has been given about waiting to apply this update until it is cleared as safe, so if anyone decides to ignore the warnings, too bad. If it's safe, it'll be known soon enough. I'm just wondering how many other threads will be made about it...anyone taking bets?
Yea I would definitely hold off on this update considering how long AT&T has had time now to play with it. Even an above post said the ATT rep said it was also a security update with no other info. Seems suspicious...
Be wise in your choices gentlemen; that's all I have to say
Be wise in your choices gentlemen; that's all I have to say
Yeah I got the update but disconnected from wifi. Don't want to download it until I know what it is
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
28Taken straight from \cache\fota\2400258.cfg, here is the I337UCUAMF3 OTA update:
http://d-h.st/vBt
Simply rename the file with a .zip extension to open it.
If someone would like to mirror this to a more permanent location, that would be appreciated.
EDIT: Uploaded to Dev-Host, so link has changed.13Here's a flashable zip of the MF3 modem ONLY. The zip should work, but I can't attest to the anything that may happen to your device as a result of the new modem.
http://www.mediafire.com/?67m2wlhukg7c8vj
Gonna assume everyone has the common sense to read through this thread BEFORE flashing, as this kind of stuff can mess up your phone pretty bad if done wrong.12Nothing is "uncrackable", people. There might be some misunderstanding here about what it means to blow a qfuse/efuse. It's been stated around the forums plenty of times before, but usually only deep within Dev conversations about hacking bootloaders, etc.
If I'm wrong in any of this, please feel free to correct me (that's what the internet is for, right?).
It's simple - an e-fuse is designed to do one thing: increment. When the bootloader is flashed to a new major version (often correcting numerous exploits, along with some bug fixing or improvements), the manufacturer or carrier will often decide they don't want anyone going back to earlier versions. In the case of the S4 with KNOX expectations of security, this makes total sense (how could a government agency or large corporation guarantee that their employees are not rooting their phones and bypassing security measures set in place by the company? Or even malware that applies the root exploit for itself?).
When the newer firmware is flashed, the e-fuse gets incremented (to a "2" in this case, it appears). Any firmware with a "1" will be refused by Odin on the phone. These e-fuses are again designed to only increment, never decrement - meaning if you're at a "2", there's no hope that you can ever get your e-fuse back to a "1" again.
In terms of hacking, bootloaders, root, etc.: This just means that whatever exploits and bug fixes have been made are now permanent. That doesn't mean that new exploits cannot be made.
One of the biggest questions I will have: Does the refusal to apply an older firmware (through Odin) also imply the refusal to boot said firmware (if somehow loaded by another means - via dd or JTAG for example)?
I'm hoping to find out sometime this week.
EDIT/ADD:
And yes, jeboo is correct. They could always release a new firmware, and increment the e-fuse again to a "3" whilst still unlocking the bootloaders. The bootloaders are only "locked" because they are currently programmed not to load "whatever we want". Just remember the chain:
PBL -> SBL1 -> SBL2 -> SBL3 -> ABOOT. The PBL is physical and can't be changed without hardware modification. But the rest of those can be changed. Usually custom bootloaders would be loaded in the later stages (aboot for example). But with sbl2 and sbl3 checking for signatures and such, there's no hope to do this without bricking instantly. If AT&T were to push an unlocked version of SBL2 and SBL3 in a future patch, these new pieces of the bootloader could be designed to be successfully loaded by PBL/SB1, but also not check for signatures on ABOOT.9Update on neutered OTA:
Complete! Uploading shortly. I will be starting a new thread with a full write-up on how to install MF3 on your own device while keeping your current recovery and rooting the new MF3. Also, I've zipped up my modified MF3 SecSettings.apk to remove SysScope. That means you'll have the option to get MF3 without the "Custom" status or logo.
(To those wondering if it is possible to root the new MF3 if you were forced to get it, I cannot help you, I'm sorry. The method involves simply flashing a zip from recovery. If you've taken the full, unaltered MF3 OTA update, you will notice you no longer have a custom recovery!)
I need to go upload a lot of files and finish the write-up. Once complete, I'll run my device through the instructions one last time as a final test.
As usual, "Stay tuned." I'll post a link her ein this thread to the new thread when it is created.
