Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

I'm aware of that but the link shows the ota files. Not the factory images.

I at least answered your question, though, didn't I?

 

 If you flash an OTA zip file (or most flashable zips from XDA), you also won't lose any data. Edit: Flashing an OTA zip file will make your recovery stock, though, if your recovery is custom like TWRP or CWM.

 

I was just trying to cover all bases since you weren't specific on which way you your trying to sideload the update.

Link to comment
Share on other sites

Flashed the factory image last night. Wow this thing still has that issue where you have to update prl to get mms to download. Was hoping that would get patched up for the final release.

every time or just the first time after flashing?

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

you can flash factory images and keep data by removing the "-w" from the flashall.bat file.

 

or manually flashing each partition.

 

you must still be oem unlocked (which does wipe all data).

Link to comment
Share on other sites

When trying to flash the OTA from TWRP it gave me an error.  I have done it this way with kitkat.  With this update I had to put the stock recovery on and then ADB sideload the OTA zip to not have it error out.

 

This is the OTA zip for anyone completely stock and not wanting to wait for the OTA.  It does not wipe data but you do have to use ADB to sideload it.

 

http://android.clients.google.com/packages/ota/google_hammerhead/c1a33561be84a8a6a7d5a4c8e3463c4db9352ce6.signed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip

 

 

Link to comment
Share on other sites

When trying to flash the OTA from TWRP it gave me an error.  I have done it this way with kitkat.  With this update I had to put the stock recovery on and then ADB sideload the OTA zip to not have it error out.

 

This is the OTA zip for anyone completely stock and not wanting to wait for the OTA.  It does not wipe data but you do have to use ADB to sideload it.

 

http://android.clients.google.com/packages/ota/google_hammerhead/c1a33561be84a8a6a7d5a4c8e3463c4db9352ce6.signed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip

 

Is there a step by step guide for how to use this somewhere?

Link to comment
Share on other sites

Is there a step by step guide for how to use this somewhere?

XDA has numerous guides in the section for the n5. I'd link one but I'm lazy and searching is easy: P.
Link to comment
Share on other sites

 

Is there a step by step guide for how to use this somewhere?

 

 

 

 

1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press volume up and release. The menu will appear. Select “apply update from adb”
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.

 

 

http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217

Link to comment
Share on other sites

Is there a step by step guide for how to use this somewhere?

 

 

 

 
 

 

 

 

1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.

2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.

3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'

4) When in recovery, you’ll see an android laying down. Press volume up and release. The menu will appear. Select “apply update from adb”

5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.

6) When completed, select reboot.

 

 

http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217

 

Make sure to have the latest version of adb as well, or else you won't be able to do it. A copy of it is attached to the bottom of the first post in the XDA link that liveToCheck posted.

Link to comment
Share on other sites

These instructions are doing a good job of making me feel dumb, lol. I'm confused just trying to figure out how to download the sdk and fastboot tool

Go onto XDA, they have a bare essentials version of the SDK thats a lot simpler. And literally a guide for everything you could want.
Link to comment
Share on other sites

well, this didn't work out so well. I got into fastboot somehow and accidentally hit wipe cache, then panicked and shut down the phone real quick because that wasn't what I meant to hit.

 

Upon rebooting my phone it came back on but with no service and showing no provider. It wouldn't let me get it and update prl or anything because under 'about phone' it was showing no provider/no service.

 

someone help me get back to normal and I'll just wait for the OTA, lol

Link to comment
Share on other sites

well, this didn't work out so well. I got into fastboot somehow and accidentally hit wipe cache, then panicked and shut down the phone real quick because that wasn't what I meant to hit.

 

Upon rebooting my phone it came back on but with no service and showing no provider. It wouldn't let me get it and update prl or anything because under 'about phone' it was showing no provider/no service.

 

someone help me get back to normal and I'll just wait for the OTA, lol

I'm surprised wiping the cache had that effect on your phone.

 

I don't know if this will work since you have "no provider/no service", but it should be worth a try.

Go into your phone app, then type *#*#72786#*#* and your phone should try reactivating itself on Sprint.

 

Edit: Actually, rereading your post, it was probably not the wiping cache that cause this, but the fact that you shut down the phone in the middle of wiping the cache. Hopefully, you didn't accidentally erase something in the flash memory that was holding your phone information. That might be unfixable unless you happened to have your EFS backed up.

Link to comment
Share on other sites

Wiping the cache is harmless. I just did it to my phone. When it came back up it said "no service" as well, but after about it minute it was back on Sprint.   

 

Go into recovery, wipe cache, let it finish, reboot, and let it sit for a few minutes .

Link to comment
Share on other sites

yeah, didn't work... maybe just factory reset?

 

google play services errors and everything popping up, along with no service.

Oh no... Good luck. I hope something works. The 72786 code is usually the one thing that fixes all telephony related issues with my smartphones, but I've been doing a lot less modifications to my Nexus 5 compared to my Galaxy S 3 from a long time ago, so I haven't had to do that ever since I switched.

Link to comment
Share on other sites

that did it, thanks! Now I'll just wait for the OTA, lol. I swear I used to be smarter with computers than this.... I think at some point over the last 5-6 years, this stuff just passed me by.

yea forget it i keep getting cmd.exe and java are blocking installation,  OTA i will wait.  I miss update from sdcard 

Link to comment
Share on other sites

Band 25 can be disabled now with 5.0. I don't remember being able to do that on kit kat, makes finding b41/b26 easier. The radio band select menu also doesn't crash anymore with several options. USA band, Japan band, band mode 6 and band mode 7.

  • Like 1
Link to comment
Share on other sites

Band 25 can be disabled now with 5.0. I don't remember being able to do that on kit kat, makes finding b41/b26 easier. The radio band select menu also doesn't crash anymore with several options. USA band, Japan band, band mode 6 and band mode 7.

Band 25 can be disabled while leaving 26 and 41 on? Previously disabling B25 would turn off all LTE.

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...