Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

I just DLed the OTA on my laptop. There is a new /system/framework/telephony-common.jar

 

No new radio image. But maybe there was a bug between the two and the new radio needed a new telephony framework to get proper signal?

 

Who knows, I'll wait until it is pushed to my phone.

 

Anyone reporting signal strength on 4.4.2, please specify whether you are using the 4.4 radio image or the 4.4.1 radio image.

Link to comment
Share on other sites

I just DLed the OTA on my laptop. There is a new /system/framework/telephony-common.jar

 

No new radio image. But maybe there was a bug between the two and the new radio needed a new telephony framework to get proper signal?

 

If the previous update was completely pulled (containing the 'new' radio image) and this is meant to be the actual update, wouldnt those who never got last weeks update end up staying on the original radio?....and possibly this is what they want?

Link to comment
Share on other sites

My signal seems slightly worse, by 2 or 3dBm, nothing too drastic like some people have been reporting. I'm willing to give this radio a go considering the phone holds onto LTE longer than it probably should with original radio.

Link to comment
Share on other sites

My signal seems slightly worse, by 2 or 3dBm, nothing too drastic like some people have been reporting. I'm willing to give this radio a go considering the phone holds onto LTE longer than it probably should with original radio.

 

Which radio? Do you have the 4.4 or 4.4.1 radio? There is no new radio in 4.4.2

Link to comment
Share on other sites

If the previous update was completely pulled (containing the 'new' radio image) and this is meant to be the actual update, wouldnt those who never got last weeks update end up staying on the original radio?....and possibly this is what they want?

 

If this was the case, you would assume they would put the 4.4 radio in the 4.4.2 update to roll everyone back. But who knows.

Link to comment
Share on other sites

The 4.4.2 software update is KOT49H. Baseband and kernel version are the same in 4.4.1 and 4.4.2, but some of the telephony files have changed so they did something to the radio, as well as other fixes. Looks like 4.4.1 was only officially pushed out as an OTA for some users, and now 4.4.2 is rolling out for far more users on the Nexus 4, 5, and 7; someone on XDA mentioned that 4.4.1 was a "beta" only pushed out as an OTA to approximately 1% of users.

 

Here are the .zips you can flash in custom recovery if you do not want to wait for the OTA:

 

4.4 (KRT16M) -> 4.4.2 (53.9 MB)

 

4.4.1 (KOT49E) -> 4.4.2 (1.66 MB)

 

I updated from 4.4.1 to 4.4.2; root was lost, but custom recovery remained intact (TWRP) so it was an easy fix. Baseband was not touched (makes sense). Cache rebuild was forced on startup. Haven't noticed any major changes from 4.4.1.

 

-Mike

  • Like 1
Link to comment
Share on other sites

Can this update be applied directly from the phone using the download link you just provided? I did the 4.4.1 update using the adb sideload procedure but I am not going to be in front of a computer for the rest of the week. Just wondering if I can get this installed somehow? I am stock and not rooted.

Link to comment
Share on other sites

The original 4.4 > 4.4.1 update was not pulled, maybe from Sprint side if they had it up but not from Google. You can still download it from Google:

 

http://android.clients.google.com/packages/ota/google_hammerhead/7ed504f678cea49ecf0974e8cd956e2974e3f943.signed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip

Link to comment
Share on other sites

I just updated using the OTA zip file. I use Xposed framework along with flashing SuperSU, so, to get a clean /system, I just reflashed the stock odexed KRT16M zip file from XDA, flashed the KOT49E OTA update zip, and then flashed the KOT49H OTA update zip, reflashed SuperSU, rebooted, then did a fastboot flash recovery again to get my CWM recovery, and now I'm on the latest update. Man, I love how easy it is to update Nexus phones. No need to wait for someone to make a pre-rooted stock flashable zip or a pre-rooted Odin update in the case of Samsung phones.

 

In any case, looks like a small update. I checked the *#*#DATA#*#* menu just to see if they enabled triband early, but no dice as expected. Looks like we have to wait for 4.4.3 or maybe even later for triband.

  • Like 1
Link to comment
Share on other sites

Can this update be applied directly from the phone using the download link you just provided? I did the 4.4.1 update using the adb sideload procedure but I am not going to be in front of a computer for the rest of the week. Just wondering if I can get this installed somehow? I am stock and not rooted.

 

it can be applied via TWRP as any other zip file, otherwise if your completely stock you must use fastboot sideload...

 

... or simply wait until it gets pushed to your device.

Link to comment
Share on other sites

 

In any case, looks like a small update. I checked the *#*#DATA#*#* menu just to see if they enabled triband early, but no dice as expected. Looks like we have to wait for 4.4.3 or maybe even later for triband.

 

 

I am betting that triband enablement will come from a profile update, although I concede that there may very well be needed radio updates too.

Link to comment
Share on other sites

I was able to flash 4.4.2 over a custom kernel, the zip from 4.4.1 to 4.4.2 is 1.66MB.

 

Just had to reflash the SuperSU binary and was all set.

 

According to XDA

 

Originally Posted by cmstlist viewpost.png
Glancing at the zip, most patch files are only 1- 2 KB which suggests a minor change like version number. Files larger than 2 KB are patches for:

/system/app/FaceLock.apk
/system/app/GoogleCamera.apk and .odex
/system/app/GalleryGoogle.apk

/system/bin/sensors.qcom

/system/framework/telephony-common.odex
/system/framework/ext.jar
/system/framework/framework-res.apk

/system/lib/libpatts_engine_jin.api.so
/system/lib/libwebviewchromium.so
/system/lib/libpac.so
/system/lib/libnfc-nci.so
/system/lib/libnfc_nci_jni.so
/system/lib/libfacelock_jni.so

/system/priv-app/GoogleLoginService.apk and .odex
/system/priv-app/Settings.apk and .odex
A number of other files in here are 3 KB

/vendor/lib/libmmcamera2_isp_modules.so
/vendor/lib/libmmcamera2_stats_modules.so
/vendor/lib/libmmcamera2_imglib_modules.so
and a few others ranging 3-6 KB.

 

 

http://forum.xda-developers.com/showpost.php?p=48314033&postcount=51

Link to comment
Share on other sites

did the OTA update just now.  was on 4.4.1 but with the 4.4 radio.  It really screwed something up.  Unable to use data when not on Wifi.  Cant use Google Play store on Wifi or 3G and i cant seem to send / receive text or MMS.  Wondering if I need to install the 4.4.1 radio.

 

oh, and also lost root.

Link to comment
Share on other sites

did the OTA update just now.  was on 4.4.1 but with the 4.4 radio.  It really screwed something up.  Unable to use data when not on Wifi.  Cant use Google Play store on Wifi or 3G and i cant seem to send / receive text or MMS.  Wondering if I need to install the 4.4.1 radio.

 

oh, and also lost root.

 

No issues here at all.  I'm on the 4.4 radio with 4.4.2

Link to comment
Share on other sites

did the OTA update just now.  was on 4.4.1 but with the 4.4 radio.  It really screwed something up.  Unable to use data when not on Wifi.  Cant use Google Play store on Wifi or 3G and i cant seem to send / receive text or MMS.  Wondering if I need to install the 4.4.1 radio.

 

oh, and also lost root.

 

I was also on 4.4.1 with the 4.4 radio (.17) and just flashed to 4.4.2.. I also lost root, but wi-fi, 3G, and LTE all work fine. No issues with Play Store or SMS either. Try updating your data profile.

 

-Mike

 

EDIT: I did not lose custom recovery (TWRP) either.

  • Like 3
Link to comment
Share on other sites

to flash root without a custom recovery,

 

download supersu zip to your phone

http://download.chainfire.eu/supersu

 

download twrp2 for your device to your ADB directory, in this case n5, but you can d/l the twrp for whichever supported device you have

http://www.teamw.in/project/twrp2/205

 

adb reboot-bootloader

fastboot boot openrecovery-twrp-2.6.3.2-hammerhead.img

 

this will boot twrp without flashing it

from here you can flash superuser (or any other flashable zips/mods/etc)

reboot, open supersu and update binary if prompted

 

you can still take any ota, although almost every ota will remove root thus requiring you to repeat this process

Link to comment
Share on other sites

I was also on 4.4.1 with the 4.4 radio (.17) and just flashed to 4.4.2.. I also lost root, but wi-fi, 3G, and LTE all work fine. No issues with Play Store or SMS either. Try updating your data profile.

 

-Mike

 

Lost TWRP as well but just added it back and rooted again.  Will see what happens.

Link to comment
Share on other sites

I updated my earlier post here, with links to both flashable zips and my first impressions of 4.4.2. Basically, you'll lose root (easily regained), but nothing else breaks.

 

Going to stay with the original 4.4 radio (baseband .17) for now, as it has been working awesome for me and I see no need to mess with it. Curious if any changes in 4.4.2 affected it though.

 

-Mike

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...