Related
Below are a list of all known Nexus 4 OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file on my website, http://randomphantasmagoria.com, in case Google pulls it down in the future.
OTA updates - occam (Worldwide GSM/HSPA+)
Current firmware: Android 5.1.1, Build LMY48T
LMY48T from LMY48M - https://android.googleapis.com/pack...ac2c8b445.signed-occam-LMY48T-from-LMY48M.zip
----------------------------------------------------
LMY48M from LMY48I - https://android.googleapis.com/pack....signed-occam-LMY48M-from-LMY48I.b84572d4.zip
----------------------------------------------------
LMY48I from LMY47V - https://android.googleapis.com/pack....signed-occam-LMY48I-from-LMY47V.d49d67c5.zip
----------------------------------------------------
LMY47V from LMY47O - http://android.clients.google.com/p....signed-occam-LMY47V-from-LMY47O.050356b6.zip
----------------------------------------------------
LMY47O from LRX21T - http://android.clients.google.com/p....signed-occam-LMY47O-from-LRX21T.37c27ea7.zip
LMY47O from LRX22C - http://android.clients.google.com/p....signed-occam-LMY47O-from-LRX22C.e6789b4e.zip
----------------------------------------------------
LRX22C from KTU84P - http://android.clients.google.com/p....signed-occam-LRX22C-from-KTU84P.eef0995e.zip
LRX22C from LRX21T - http://android.clients.google.com/p....signed-occam-LRX22C-from-LRX21T.e93b20be.zip
----------------------------------------------------
LRX21T from KTU84P - http://android.clients.google.com/p....signed-occam-LRX21T-from-KTU84P.1c6f10c3.zip
----------------------------------------------------
KTU84P from KTU84L - http://android.clients.google.com/p....signed-occam-KTU84P-from-KTU84L.50b64331.zip
----------------------------------------------------
KTU84L from KOT49H - http://android.clients.google.com/p....signed-occam-KTU84L-from-KOT49H.61a9ce8d.zip
----------------------------------------------------
KOT49H from KRT16O - http://android.clients.google.com/p....signed-occam-KOT49H-from-KRT16O.250326d3.zip
KOT49H from KRT16S - http://android.clients.google.com/p....signed-occam-KOT49H-from-KRT16S.4f6d2fc7.zip
KOT49H from KOT49E - http://android.clients.google.com/p....signed-occam-KOT49H-from-KOT49E.0ec632f5.zip
----------------------------------------------------
KOT49E from KRT16S - http://android.clients.google.com/p....signed-occam-KOT49E-from-KRT16S.0896df95.zip
----------------------------------------------------
KRT16S from JWR66Y - http://android.clients.google.com/p....signed-occam-KRT16S-from-JWR66Y.d1b99704.zip
KRT16S from KRT16O - http://android.clients.google.com/p....signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
----------------------------------------------------
JWR66Y from JOP40C - http://android.clients.google.com/p....signed-occam-JWR66Y-from-JOP40C.3b0cb3ad.zip
JWR66Y from JOP40G - http://android.clients.google.com/p....signed-occam-JWR66Y-from-JOP40G.bc81f98c.zip
JWR66Y from JDQ39 - http://android.clients.google.com/p...2.signed-occam-JWR66Y-from-JDQ39.c4df9c73.zip
JWR66Y from JDQ39E - http://android.clients.google.com/p....signed-occam-JWR66Y-from-JDQ39E.0327fb70.zip
JWR66Y from JWR66N* - http://android.clients.google.com/p....signed-occam-JWR66Y-from-JWR66N.a33d7c5b.zip
JWR66Y from JWR66V - http://android.clients.google.com/p....signed-occam-JWR66Y-from-JWR66V.6136cbe0.zip
----------------------------------------------------
JWR66V from JOP40C - http://android.clients.google.com/p....signed-occam-JWR66V-from-JOP40C.f6938a0e.zip
JWR66V from JOP40G - http://android.clients.google.com/p....signed-occam-JWR66V-from-JOP40G.fad3efe5.zip
JWR66V from JDQ39 - http://android.clients.google.com/p...1.signed-occam-JWR66V-from-JDQ39.ebc8bad2.zip
JWR66V from JDQ39E - http://android.clients.google.com/p....signed-occam-JWR66V-from-JDQ39E.7e768b10.zip
JWR66V from JWR66N* - http://android.clients.google.com/p....signed-occam-JWR66V-from-JWR66N.fe92fc9f.zip
----------------------------------------------------
JDQ39 from JOP40C - http://android.clients.google.com/p...4.signed-occam-JDQ39-from-JOP40C.ebd2f14a.zip
JDQ39 from JOP40D - http://android.clients.google.com/p...4.signed-occam-JDQ39-from-JOP40D.de8b8d10.zip
JDQ39 from JOP40G - http://android.clients.google.com/p...d.signed-occam-JDQ39-from-JOP40G.82917390.zip
JDQ39 from JDQ23* - http://android.clients.google.com/p...99.signed-occam-JDQ39-from-JDQ23.831bb496.zip
----------------------------------------------------
JOP40D from JVP15L* - http://android.clients.google.com/p....signed-occam-JOP40D-from-JVP15L.8c8adc7f.zip
JOP40D from JVP15Q - http://android.clients.google.com/p....signed-occam-JOP40D-from-JVP15Q.405bebc7.zip
JOP40D from JOP24G* - http://android.clients.google.com/p....signed-occam-JOP40D-from-JOP24G.ae1e42c5.zip
JOP40D from JOP40C - http://android.clients.google.com/p....signed-occam-JOP40D-from-JOP40C.625f5f7c.zip
----------------------------------------------------
JOP40C from JVP15Q - http://android.clients.google.com/p....signed-occam-JOP40C-from-JVP15Q.609c838b.zip
* JVP15L, JOP24G, JDQ23, and JWR66N were prerelease or testing builds that never appeared on devices sold to the general public.
SPECIAL THANKS
deathpod
[email protected]
xdatastic
bongostl
thephantom
drmclove69
efrant
GreenSGS
VivaErBetis
TheManii
qorron
El Daddy
^ms
EthanFirst
dpjohnston
Displaxx
Tang034
Thanks
Glad to have you here
So basically were just need to provide the new build number and About Phone info right?
Jamal Ahmed said:
Thanks
Glad to have you here
So basically were just need to provide the new build number and About Phone info right?
Click to expand...
Click to collapse
And the new baseband version, bootloader version, and the filename to the OTA (which you'll need to get before you install it).
Sent from my Galaxy Nexus using Tapatalk 2
Glad to see oldblue here. Very helpful person indeed in every way. Let's pull efrant in as well.
Request for sticky as well since this will be a very useful thread when the time comes
Sent from my Nexus 7 using Tapatalk 2
thephantom said:
Let's pull efrant in as well.
Click to expand...
Click to collapse
why dont use official google website..? https://developers.google.com/android/nexus/images?hl=sk
ingbrzy said:
why dont use official google website..? https://developers.google.com/android/nexus/images?hl=sk
Click to expand...
Click to collapse
That site doesn't have links to the OTA packages but yes, that would work for the factory images (though I guess it's not direct link to the zip file).
Unlawful said:
That site doesn't have links to the OTA packages but yes, that would work for the factory images (though I guess it's not direct link to the zip file).
Click to expand...
Click to collapse
Plus, I mirror the files. Every time there's an OTA, Google removes the old factory images and replaces them with the new ones. My website doubles as an archive.
Sent from my Galaxy Nexus using Tapatalk 2
Hi everyone. Since the N4 goes on sale tomorrow, I need someone to volunteer to grab some info for me from a brand new N4. This info will need to be obtained as soon as you power up the device, before you apply any OTA updates or anything else. Here's what I'll need from the device:
1. The bootloader version. (Found only on the main bootloader screen, you'll have to reboot into the bootloader to see it)
2. Android version and build # (From settings)
3. Baseband version (From settings)
4. Firmware and device name. To get these two pieces of info, open /system/build.prop in a text editor and post the values of ro.product.name and ro.product.device.
Again, please do this as soon as you power on the device, before applying any OTA that may be available out of the box! Thanks much for your help!
If I get mine before you have the info I am happy to help. I will be ordering as soon as available and will be shipping next day if possible. I live on the east coast though so you may already have it by then..
Sent from my Nexus 7 using xda app-developers app
Richieboy67 said:
If I get mine before you have the info I am happy to help. I will be ordering as soon as available and will be shipping next day if possible. I live on the east coast though so you may already have it by then..
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I appreciate it!
oldblue910 said:
Hi everyone. Since the N4 goes on sale tomorrow, I need someone to volunteer to grab some info for me from a brand new N4. This info will need to be obtained as soon as you power up the device, before you apply any OTA updates or anything else. Here's what I'll need from the device:
1. The bootloader version. (Found only on the main bootloader screen, you'll have to reboot into the bootloader to see it)
2. Android version and build # (From settings)
3. Baseband version (From settings)
4. Firmware and device name. To get these two pieces of info, open /system/build.prop in a text editor and post the values of ro.product.name and ro.product.device.
Again, please do this as soon as you power on the device, before applying any OTA that may be available out of the box! Thanks much for your help!
Click to expand...
Click to collapse
Just a reminder. If any of you guys in the UK can provide this information before applying any OTA updates, I'd really appreciate it. Also, if you get an OTA to JOP40C, if you could get the link for it, that'd be awesome too!
Anyone? At this point, all I need to know is this: Did your phone come pre-loaded with JOP40C? Or did it come with JOP24G and then you had to OTA to JOP40C?
oldblue910 said:
Anyone?
Click to expand...
Click to collapse
The images are already posted here. You should easily be able to download them and see what the radio and bootloader version are, and extract the build.prop.
efrant said:
The images are already posted here. You should easily be able to download them and see what the radio and bootloader version are, and extract the build.prop.
Click to expand...
Click to collapse
Yes, but I have reason to believe that the phone actually ships with JOP24G, not JOP40C. I want the information from JOP24G if the phone indeed ships with it. I have most of the information for JOP24G...the only thing I don't know is the bootloader version. Also, if the phone ships with JOP24G, I'm hoping someone will be able to provide the OTA link for JOP40C from JOP24G.
Anyone get a Nexus 4 yet? Can anyone tell me if it shipped with JOP24G or JOP40C out of the box?
OK, judging by YouTube unboxing videos, I can definitely verify that it does NOT ship with JOP40C out of the box. It ships with some earlier build. Nobody seems to scroll down so I can see the build number, but I can tell it's an older build by the baseband. It ships with 1700.24, but JOP40C uses 1700.33.
So, when somebody gets their N4, if you wouldn't mind, please (before installing any OTAs) do the following for me:
1. Reboot the phone into bootloader mode and tell me the bootloader version. It may be MAKOZ10L but I'm not sure so I'd like confirmation.
2. Android build number.
3. When you get the OTA notification to update to JOP40C, could you check logcat before applying the update and get the URL to the OTA file?
I would normally do this myself, except I won't be owning a Nexus 4 straight away since I'm on Verizon.
Thanks!
Bootlader version. makoz10f
Build # JVP15Q
Baseband M9615A-CEFWMAZM-2.0.1700.24
Phone already had OTA update ready to install by the time I logged in and got this info, but it won't reboot and install update. How can I get the URL it downloaded from?
Sent from my Nexus 4 using xda premium
thatguyitsme said:
Bootlader version. makoz10f
Build # JVP15Q
Baseband M9615A-CEFWMAZM-2.0.1700.24
Phone already had OTA update ready to install by the time I logged in and got this info, but it won't reboot and install update. How can I get the URL it downloaded from?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
THANK YOU!!
as far as the OTA, not sure what's up there, but if you want to work with me on getting the filename for the OTA, I'd really appreciate it. Are you familiar with ADB and the developer options (sorry if that's an insulting question, but I need to know what instructions to give you.
Basically, you'll need to turn on developer options on your phone by going into Settings | About Phone and tapping the build number a few times.
Once that's done, go to Settings | Developer Options and turn on USB debugging.
Once that's done, hook the phone up to your computer via USB, open a command prompt. Do the following command:
adb logcat >logcat.txt
After about 10 seconds, hit Control C to exit out. Open that file (logcat.txt) that you just created in a text editor and search it for ".zip" (without the quotes). You should find the name of a zip file in there. Give me the name of that file (or the full URL if it's in there).
For most up-to-date information on optimized libraries, please carefully read @osm0sis's post: http://forum.xda-developers.com/showpost.php?p=53963337&postcount=1287
You should also read @Lethargy's post in the Nexus 5 thread: http://forum.xda-developers.com/showpost.php?p=56038135&postcount=2918.
The outdated flashable ZIPs from this post have been deleted. Head over to post linked above for the latest libraries.
Have you ever wondered why your Nexus 4 performs worse than other flagship devices with the same quad-core CPU in benchmarks? Not any more! I present you with a very simple patch that will boost your performance to what other APQ8064-based devices offer.
Before using, please read the following Q&A.
Q: Will this void my warranty?
A: Yes. Flash at your own risk.
Q: Can I use it?
A: Yes, if you're on any 4.4/4.4.x ROM.
Q: How does this work?
A: This patch consists of two files that include optimized bionic and Dalvik libraries for any KitKat ROM.
Q: What is bionic?
A: It is a vital system library that provides i.a. basic math and memory access functions to every other library and application in Android.
Q: What is Dalvik?
A: In short, Dalvik is a virtual machine in which every not-native-code app runs. You can read more about it in a Wikipedia article.
Q: How do I benefit from this patch?
A: In two ways: bionic patch provides faster memory access and optimized some of the math operations, dalvik provides optimized Dalvik Virtual Machine library that allows faster code execution.
Q: Do I need this patch?
A: It depends on what ROM you are using:
if you're on stock ROM, you'll benefit from flashing both bionic and dalvik patches,
if you're using a custom ROM, you most probably don't need bionic patch, as these are already included in most custom ROMs. You'd benefit only from flashing dalvik patch (if it's not already included by your ROM maintainer, of course),
don't use the bionic patch on CyanogenMod, PSX and probably others, because they already have more optimized versions!
Q: Why aren't these patches included in stock ROM?
A: As for bionic - I don't know. Maybe that's because Google didn't want to include vendor-specific optimizations in AOSP or maybe simply because Qualcomm never posted them in Android Code Review to be merged. As for dalvik - because they are closed-source. Here'a a good explanation by @xboxfanj:
xboxfanj said:
Part of the point of Nexus devices is that AOSP can produce nearly identical images minus GApps. Google would not use a proprietary dalvik as that is one of the core libraries. Using a proprietary dalvik would undermine AOSP. Although, an open libqc-dalvik or even just giving us that binary would be nice. Google could have a device specific extension similar to the adreno extensions onto renderscript and egl for dalvik. Proprietary dalvik won't happen, but an adreno extension could be cool.
Click to expand...
Click to collapse
Q: Where do these patches come from?
A: These have been authored by Qualcomm. Bionic patch comes from Code Aurora Forum, Dalvik library has been extracted from Moto X 4.4. ROM. Another good read by @xboxfanj:
xboxfanj said:
CAF has all Qualcomm's bionic patches and slight dalvik tweaks, however, the dalvik patches that are used here in the Moto X and any QCOM (non-Nexus) device, are mostly closed source. If you look at the change here: https://www.codeaurora.org/cgit/qui...0&id=337a595d746d34ade52e3aba2c739455dfd3cf57
You will see that most of that change is supporting other libraries (libqc-opt and libqc-dalvik), which is where their optimizations are. Unfortunately, both of those are closed source. libqc-opt is included in QCOM ROM zips as a shared library, so we can use that, however, libqc-dalvik is a static library, so we can't pull that from anywhere, as it is included in the libraries themselves and not put in system. This means that our only option to get all of Qualcomm's dalvik optimizations is to use their binaries rather than building from source, since building from source would mean missing any optimizations brought by libqc-dalvik, libqc-sqlite, and libqc-skia (the last two haven't been included in any patch, but are QCOM static libraries).
TLDR: QCOM's dalvik optimizations are closed source, so we are forced to use their binaries.
Click to expand...
Click to collapse
Remember to thank @xboxfanj for his very useful posts!
Q: What is the reason for including installd file?
A: The installd binary is from stock Nexus 4 ROM and is included for compatibility with CyanogenMod and CM-based ROMs. This is because CyanogenMod changed installd to work with their dexopt-on-cache (see here: https://github.com/CyanogenMod/android_frameworks_native/commits/cm-11.0/cmds/installd) and it you don't flash stock installd you'd get hundreds of FCs and unusable ROM.
Q: How do I use this patch?
A: Simple flash it over your current ROM in recovery. Remember to wipe Dalvik Cache after flashing. Full wipe is not needed.
Q: How do I revert?
A: Simply flash over your current ROM and wipe Dalvik Cache afterwards. Full wipe is not needed.
Q: Can I flash it over an ODEXed ROM?
A: Yes, but it is strongly recommended to use a deodexed ROM if you want to use Dalvik patch.
Q: How will this affect my battery life?
A: It will be at least the same, if not better. Better performance = less CPU time spent on calculations = better battery life.
Q: I don't see any performance gains in some app, why is that?
A: The dalvik patch doesn't affect apps that use native libraries, i.e. you won't see much performance gain in Chrome etc.
Q: I'm on X kernel, can I use it?
A: Yes, use it with any kernel you like.
Q: Can I use it on other devices?
A: Yes, you can use this patch on every Krait device that uses AOSP-based ROM (examples: Nexus 5, Nexus 7 2013). Don't flash it on stock ROM on non-Nexus devices, as they already include these optimizations (that includes Galaxy S4 and HTC One Google Play editions!).
Q: What if I use it on stock ROM and OTA arrives? Can I install the OTA straight away?
A: You can't. You have to revert to stock libraries first. Keep in mind that every modification to stock ROM can mean problems when installing an OTA. You should revert to fully stock ROM to properly apply an OTA. For your courtesy, there's a revert ZIP attached for KRT15S and KOT49E ROMs. Remember that the safest way it to flash system.img from a factory image before applying an OTA once you made modifications to your /system partition!
Q: Can I use these patches on 4.4.1/4.4.2 stock ROM (KOT49E/KOT49H)?
A: Yes, you can.
Q: Can I use ART with this patch installed?
A: Yes, but you won't see any performance gains. In fact, with this patch Dalvik is faster than ART. I suppose ART will supersede Dalvik in performance in the future, but not yet.
Q: Where can I see some benchmark results before I flash?
A: Head over to Nexus 4 Benchmarks thread.
Q: Do I need to be rooted to flash this?
A: No. The only thing you need is custom recovery (CWM, TWRP etc.).
Q: Do I have to flash these patches every time I install an update/new ROM?
A: Yes.
Don't replace these files on a running system (i.e. via a file explorer or adb)! If you do this, your phone will stop working and you'd have to reflash your ROM to make it work again. And you'll probably loose some data by doing so. Always use recovery to replace these libraries.
If you're running CM11 released after 1 March 2014 or any other ROM that includes fixes to DVM, please flash 4.4_qc-optimized_dalvik-cm11.zip. This is the only file you need, don't flash anything else from this thread!
Nice job on the new thread!
Pure Speed X? ~ ViPER4Android ? [n⁴]
Yep, good to have a dedicated thread.
I did notice a slight change, with there being no more dexopt file, just checking that this is correct?
In the benchmarks thread, I saw a comment that it probably won't work on CyanogenMod ROMs. Is that true?
Sent from my SCH-I535 using Tapatalk
i got bootloop !
with 4.4 stock.
-----------------------------------------------
I tested the patches on my custom ROM and it seemed to me that I didn't need to replace dexopt binary anymore yet from your bootloops it looks like we have to replace it anyhow. Thank for noticing! I've uploaded an updated dalvik patch, please try it now.
Click to expand...
Click to collapse
now it's working , my apps is upgrading now
it's boring (289 apps .... :| )
Another bootloop in Stock 4.4.
And if like me, you didn't make a whole system backup, I've attached the original files.
i have no bootloop flashed both files, after install, i did wipe cache and dalvik cache. But previously i already did patch motoX_4.4_qcoptimized.zip from kszaq posted at Nexus 4 Benchmark thread. I have Stock ROM + Kernel.
i see you change the dalvik file( "4.4_qc-optimized_dalvik.zip") !
i'm testing your new file .
meangreenie said:
Yep, good to have a dedicated thread.
I did notice a slight change, with there being no more dexopt file, just checking that this is correct?
Click to expand...
Click to collapse
max4wdc said:
i got bootloop !
with 4.4 stock.
Click to expand...
Click to collapse
I tested the patches on my custom ROM and it seemed to me that I didn't need to replace dexopt binary anymore yet from your bootloops it looks like we have to replace it anyhow. Thank for noticing! I've uploaded an updated dalvik patch, please try it now.
LudicrousPeed said:
In the benchmarks thread, I saw a comment that it probably won't work on CyanogenMod ROMs. Is that true?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It works for me on CyanogenMod. I figured out that the reason for it not having worked before was that CyanogenMod uses a modified installd binary (they patched it for Dexroot on Cache). As this is the only change they made I included stock installd binary (from stock Nexus 4 ROM) to make dalvik patch work with CM and any ROM that uses their base.
kszaq said:
I tested the patches on my custom ROM and it seemed to me that I didn't need to replace dexopt binary anymore yet from your bootloops it looks like we have to replace it anyhow. Thank for noticing! I've uploaded an updated dalvik patch, please try it now.
It works for me on CyanogenMod. I figured out that the reason for it not having worked before was that CyanogenMod uses a modified installd binary (they patched it for Dexroot on Cache). As this is the only change they made I included stock installd binary (from stock Nexus 4 ROM) to make dalvik patch work with CM and any ROM that uses their base.
Click to expand...
Click to collapse
now work on 4.4 stock .:good:
Working for me on Stock 4.4 with Franco's 194 nightly kernel
Just wanted to say thank you! For this.
Doubled benchmark performance, which I don't care about but makes a lot of apps faster.
Very interesting stuff, I never knew the other devices had Qualcomm optimized bionic and dalvik libraries.
Working perfectly fine on stock KRT16S on Nexus 7 (2013)
Thanks again!
PS. I was interested in why initially you said this would only work on deodexd ROMs? Almost all production shipped firmware's are odex, are they not? Or is the MotoX a deodexd ROM/firmware?
Just curious.
Sent from my Nexus 7 using Tapatalk 4
Not sure if you have already have, but may want to git pull Linaro bionic
http://android.git.linaro.org/gitwe...it;a=shortlog;h=refs/heads/linaro_android_4.4
It merges cleanly, so no big deal.
Thanks made Dalvic quicker. Added 10 to antutu but phone was not set up for testing. Seems snappier which begs the question why is this not in official builds? Insane
Sent from my Nokia 3210
Deleted
howard bamber said:
Thanks made Dalvic quicker. Added 10 to antutu but phone was not set up for testing. Seems snappier which begs the question why is this not in official builds? Insane
Sent from my Nokia 3210
Click to expand...
Click to collapse
Qualcomm won't open source their libqc-dalvik optimizations and Google won't use a proprietary dalvik as dalvik is such a core part of Android. The goal of the AOSP is to keep as much open source as they can, sometimes at the cost of proprietary optimization.
Using the old zip from the benchmark thread, my atuntu jumped to 20000. With the 2 new zips I'm back to 17000. Tried the old zip again and back up to 20000. Any ideas why?
Sent from my Nexus 4 using xda app-developers app
I've tried both patches above on my Nexus 4 with Brainmaster's KRT16S ROM and Semaphore 1.8.0 kernel, after applied both patch I'm wiped the dalvik cache too, but my N4 cannot boot into OS, it just bootlooped to CWM recovery again and again.
Working well on stock. If you have issues and you're odexed, wipe cache and dalvik.
motherninja said:
I've tried both patches above on my Nexus 4 with Brainmaster's KRT16S ROM and Semaphore 1.8.0 kernel, after applied both patch I'm wiped the dalvik cache too, but my N4 cannot boot into OS, it just bootlooped to CWM recovery again and again.
Click to expand...
Click to collapse
Have you re-downloaded the dalvik patch after I re-uploaded it yesterday? The first version missed dexopt binary and it caused bootloops.
purpse said:
Using the old zip from the benchmark thread, my atuntu jumped to 20000. With the 2 new zips I'm back to 17000. Tried the old zip again and back up to 20000. Any ideas why?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What is your Dalvik score in AnTuTu? If it's about 1800, then the patch it working as it should and the lower score may be due the thermal throttling.
FYI, the march update dropped. the experience was a little different than in the past. plus, i flashed the Nougat update from here, so i was concerned if i would even get future updates. the concern is over, i can !
After i accepted the update, it rebooted to the Death Star logo and a progress bar went across the bottom, after it got to 100%, it flashed some text in green screen, rebooted again now just showing the AT&T logo. no please wait, no preparing to load, no animation , nothing. Sat like that for about 5 minutes, and then boom, ready to go. overall, seemed alot quicker than previous M updates.
I updated it just now, can anyone provide the changelog on the new update?
vineet381 said:
I updated it just now[. C]an anyone provide the changelog on the new update?
Click to expand...
Click to collapse
AT&T should update their software-update info page within a few days. Meanwhile, we have:
Samsung Mobile Security Blog
Android Security Bulletin—March 2017
Android patched three critical vulnerabilities. However, another eight critical vulnerabilities were addressed in Android's 2017-03-05 security patch level, which we do not yet have.
Thanks for posting this. Is this 7.1? What version number is it?
It's still 7.0
The change log only said security patches and the patch level is indeed now March 1.
Start to finish update took 10 minutes - I have never had an Android update run that quickly from my Captivate to S3 to Note 4 to my S7e - biggest visual change in addition to what was said before was that I didn't see the % decrypted that I normally see after entering my PIN at boot, just a circle with a padlock (similar to what mixxxk saw - unclear whether this was an initial upgrade activity). After finishing boot, there was an updating Nougat notification in the shade for another ~2 minutes)
evisser4 said:
Thanks for posting this. Is this 7.1? What version number is it?
Click to expand...
Click to collapse
Here is the current update: Android 7.0 Nougat
The details
Release date: March 27, 2017
Android version: 7.0
Security patch level (SPL): March 1, 2017
Baseband version: G935AUCS4BQC2
Kernel version: 3.18.31-10280464
Build number: NRD90M.G935AUCS4BQC2
File size: 50MB
Previous version required: G935AUCU4BQA6
The updates
What's changing: Android device security updates
I was on QA4, the unreleased AT&T nougat build. I updated to QA6 using the files from this thread:
https://forum.xda-developers.com/att-s7-edge/how-to/sm-g935a-stock-odin-files-g935aucu4bqa6-t3569832
I had some trouble with Odin, but I got it to work using the latest version, 3.12.3. I had to re-extract the AP file, and run Odin as an administrator. But it got me to QA6, and I got the OTA for the March security patch the first time I checked.
So for some reason, even though I'm on BAQ6 I'm not able to OTA to BQC2. Either OTA or thru Smart Switch.
Any thoughts?
kangi26 said:
So for some reason, even though I'm on BAQ6 I'm not able to OTA to BQC2. Either OTA or thru Smart Switch.
Any thoughts?
Click to expand...
Click to collapse
Smart switch do not support AT&t phones
norbarb said:
Smart switch do not support AT&t phones
Click to expand...
Click to collapse
Ah yes... well that explains things
Thanks
kangi26 said:
So for some reason, even though I'm on BAQ6 I'm not able to OTA to BQC2. Either OTA or thru Smart Switch.
Any thoughts?
Click to expand...
Click to collapse
use an offical odin not custom odin and u can flash back full wipe ot any version of android aka downgrading
Hi!
To update to OTA B608 you need to be in 2 Specific versions with his 2 fingerprint in build prop:
Android 6
Code:
hi6210sft/hi6210sft/hi6210sft:6.0/MRA58K/jenkins08021733:user/test-keys
or
Android 5
Code:
hi6210sft/hi6210sft/hi6210sft:5.0/LRX21M/jenkins02151221:user/test-keys
Huawei is getting smart...
Who have this versions????
Forget this... In HWFF page one link is OTA and the other is Default update.app
They write wrong ... lol
.
What? What this means?
D1stRU3T0R said:
What? What this means?
Click to expand...
Click to collapse
forget it.
They write wrong the id from rom.
One is full ROM (update.app) and the other is OTA ( patch + update.app), they write the 2 as FullOTA...
The ( patch + update.app) you can install but the full update.app you can!
So, they have write the same in the 2 and i download the 2x the ( patch + update.app) and i start to think that need to be in sopme proper rom to install...
but i try again and download the right one ...
lol
Is the B608 a rebuild of an older version? I mean sure it has August patches like B604 but the changelog is old, from when EMUI 4 first showed up...
JpegXguy said:
Is the B608 a rebuild of an older version? I mean sure it has August patches like B604 but the changelog is old, from when EMUI 4 first showed up...
Click to expand...
Click to collapse
Is the best version i crossed! The changelog can be old but all file are updated. It have the best battery usage from all roms i had.
Some times when you change to much you can make a mess up, so you pick the best of all and insert in the most stable version!
Is what i do! ::silly: :laugh:
.
Stock Unmodified OTA Firmware
UL-ASUS_X00T-WW-15.2016.1902.340 FOTA: 432MB
Google Drive Mirror: https://drive.google.com/file/d/1x6W_--0a6cb_ptPgKcaC3qqJlS311EQ9
AndroidFileHost Mirror: https://www.androidfilehost.com/?fid=1395089523397902556
Firmware required: UL-ASUS_X00T-WW-15.2016.1901.339.
Tested on my own Zenfone max pro m1, found no bug yet.
Warning for unmodified firmware link
Code:
These are unmodified files, so don't blame me if anything goes wrong
Stock Unmodified Full Firmware
UL-ASUS_X00T-WW-15.2016.1902.340:
Direct Asus Link: N/A
Google Drive Mirror: N/A
UL-ASUS_X00T-WW-15.2016.1901.339:
Direct Asus Link: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZB601KL/UL-ASUS_X00T-WW-15.2016.1901.339-user.zip
Google Drive Mirror: https://drive.google.com/open?id=1Q-jlaC8zSSWA0vhh3xTYOICnbLxlRtuo
Warning for unmodified firmware link
Code:
These are unmodified files, so don't blame me if anything goes wrong
TWRP Flashable Full Firmware
UL-ASUS_X00T-WW-15.2016.1902.340:
Google Drive Link: N/A
UL-ASUS_X00T-WW-15.2016.1901.339:
Google Drive Link: https://drive.google.com/open?id=1OducGK2PKedvrnkh3vt_GkvxUzTOcxiO New tested and working link
WARNING for TWRP Flashable
Code:
Make a backup before flashing these zips, these are not fully tested. I am not responsible if your phone blast, it gets bricked or a nuclear war started by using these files.
Note: If you found any bug then please report.
[27-Feb-2019] UL-ASUS_X00T-WW-15.2016.1902.340:
Changelog:
Update GMS 8.1_201812.
Update Google security patch (2019.Feb)
Improve camera app translation issue
[19-Jan-2019] UL-ASUS_X00T-WW-15.2016.1901.339:
Changelog:
Update Google Security Patch.
Optimize system stability.
Fix Garmin watch pairing issue.
any feedback on system improvements / glitches in new software, or problems faced while/after flashing twrp modified zip file?
I am on locked stock firmware, so I can't test TWRP flashable zips but because the only difference is updater_script, so It is same as unmodified stock firmware.
I didn't encounter any bug on the new update, but surely it's premature to say this when the update is rolled out only hours ago.
BTW I am too waiting for feedback from fellow users.
I'm on 338 update twrp flashable by avinash s. Can i flash this over the current rom?
I'm getting error 6
trijesh313 said:
I'm getting error 6
Click to expand...
Click to collapse
Can you explain what you did and where you get this error? Which zip is used and what recovery you used to flash?
farhanshaikh671 said:
I'm on 338 update twrp flashable by avinash s. Can i flash this over the current rom?
Click to expand...
Click to collapse
Avinash s zips are same as mine, It should not be a problem.
I am also getting error 6. Twrp 3.2.3.0.
trijesh313 said:
I'm getting error 6
Click to expand...
Click to collapse
mrayzrocks said:
I am also getting error 6. Twrp 3.2.3.0.
Click to expand...
Click to collapse
It seems I found the issue, wait for it, update the thread soon.
navjottomer said:
It seems I found the issue, wait for it, update the thread soon.
Click to expand...
Click to collapse
Too bad I already used my consumable data for this. What's wrong? Is it in the updater script? If so then can you please tell me what files to replace in the zip so I can compile myself. I have very limited data. Thank you
mrayzrocks said:
Too bad I already used my consumable data for this. What's wrong? Is it in the updater script? If so then can you please tell me what files to replace in the zip so I can compile myself. I have very limited data. Thank you
Click to expand...
Click to collapse
Don't worry I will upload the patch too.
navjottomer said:
Don't worry I will upload the patch too.
Click to expand...
Click to collapse
Ok I will wait. Thank you
mrayzrocks said:
Ok I will wait. Thank you
Click to expand...
Click to collapse
Attached is an updated META-INF directory, extract it and replace the content.
Only needed to whom who have downloaded the flashable zip earlier. I have updated the twrp-flashable link to a new file which is working fine.
the 'twrp+decrypt' script is still giving me an error, I have removed the link from OP, will update the thread when it is fixed.
Can I dirty flash it?
Sent from my ASUS_X00TD using Tapatalk
I am facing Bluetooth issue, the connection is no longer stable after updating to 339, I'm on stock with bootloader locked. Anyone else having this issue?
Mine is working fine. I didn't get any issue yet.
navjottomer said:
Mine is working fine. I didn't get any issue yet.
Click to expand...
Click to collapse
how do you install it??
New 27/02/2019 340 OTA update
【Version】
15.2016.1902.340
【Model Name】
ZenFone Max Pro(ZB601KL)
【Release Date】
2019/02/27
Since the server pushes update notice to different serial numbers by batches, it may take some days for you to receive the FOTA notice. Thanks for your patience. You may tap “System updates” in [Settings] >[System] to check if there is new firmware available. Or, you can also try to manually update firmware by referring to the following link.
How to update the firmware on my phone?
【Release Note】
1. Update GMS 8.1_201812.
2. Update Google security patch (2019.Feb)
3. Improve camera app translation issue
Download link is available in OP. Download it and copy it to your root directory. Currently, only OTA has been captured no full stock firmware, so you have to be updated to January update (WW-15.2016.1902.340).
navjottomer said:
【Version】
15.2016.1902.340
【Model Name】
ZenFone Max Pro(ZB601KL)
【Release Date】
2019/02/27
Since the server pushes update notice to different serial numbers by batches, it may take some days for you to receive the FOTA notice. Thanks for your patience. You may tap “System updates” in [Settings] >[System] to check if there is new firmware available. Or, you can also try to manually update firmware by referring to the following link.
How to update the firmware on my phone?
【Release Note】
1. Update GMS 8.1_201812.
2. Update Google security patch (2019.Feb)
3. Improve camera app translation issue
Download link is available in OP. Download it and copy it to your root directory. Currently, only OTA has been captured no full stock firmware, so you have to be updated to January update (WW-15.2016.1902.340).
Click to expand...
Click to collapse
Is it twrp flashable ota?