[INFO] Nexus 4 OTA Help-Desk

Search This thread

heat361

Senior Member
Dec 27, 2011
1,122
356
New York City
I'm not sure what the beats mod modifies. If it mods both /system and kernel files you'll have to flash both system and boot images.

When I tried to install the 4.2.2 it gave me a error with the music fx libs
So it modifies the libs

Unless someone could give me all the libs in that folder I wouldn't have toflash the image
 

ultimul

Senior Member
Jul 22, 2012
201
40
stock, rooted with TWRP, flashed the zip and successfully update to 4.2.2;

thanks for the link
 

TheHeeyyy

Senior Member
Apr 3, 2012
54
25
Are you using the latest ADB? I mentioned it in section A. It's attached at the end of the post.

I replaced those files with the new files, and the same results:

C:\Android\sdk\platform-tools>adb devices
List of devices attached
0038df544a8ceba5 sideload

C:\Android\sdk\platform-tools>adb sideload update.zip
* cannot read 'sideload' *

C:\Android\sdk\platform-tools>adb sideload update
* cannot read 'sideload' *

Any other ideas?
 

kyogoku

Senior Member
Sep 15, 2011
155
6
Hi, i'm ready to do the Section B. before continuing, can anyone tell what's the md5sum for the 4.2.2 zip?
I would like to confirm first just to make sure.

thx in advance.
 

lowrider262

Senior Member
Jan 26, 2011
1,391
553
Racine, WI
?

everytime i try to flash this i get a bunch of text popping up. i updated to the latest sdk and im fully stock unrooted w/ locked boot. what the heck am i doing wrong? (yes im somewhat of a noob to adb:()

.

C:\Windows\system32>cd C:\adb

C:\adb>adb sideload update.zip
Android Debug Bridge version 1.0.26

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments

will disconnect from all connected TCP/IP devic
es.

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb help - show this help message
adb version - show version num

DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.

C:\adb>
 

Girn

Senior Member
Dec 20, 2009
999
115
Re: [INFO] Nexus OTA Help-Desk

I'm on stock ROM on faux kernel with xlouder.. In order to successfully flash 4.2.2 update. Does this seem right?

Fastboot devices
Fastboot flash system.IMG
Fastboot flash boot.IMG
Fastboot reboot

I know that's not exactly the commands but does the procedure seem right? Am I missing anything??

Sent from my Nexus 4 using xda premium
 

Top Liked Posts

  • There are no posts matching your filters.
  • 279
    Nexus 4 OTA Help-Desk



    **4.4.4 KTU84P Available**


    You want the latest OTA? You don’t want to wait? You received the OTA but it fails? You need help with the installation process? If any of those questions are yes, then this thread is for you.

    First, let's talk about what an OTA is:

    An OTA (Over the Air) update is the method of updating your phone's software. When the OTA is downloaded to your phone it will prompt you to reboot and install. It is not a complete image, but a series of patches to the OS. Patches in the OTA can include: bootloader, radio, system, recovery and kernel. While it's installing, the script checks the files it is patching to make sure the original files are correct. If everything is correct, the update will finish successfully. If it's not, the process will stop. That's why it is critical to make sure everything is in its "out of the box" state. Don't worry though. It is easy to get your phone back to a state where you will have your phone up and running, with the latest software.

    We are also able to manually flash this file. When the URL of the OTA is discovered, you can download it and use adb or a custom recovery to apply it.


    Now that you have read the important info above, Let's update your Nexus 4!



    In order for the OTA to apply successfully, without intervention, you must be completely stock:

    4.4.3 KTU84L
    Current Bootloader - makoz30d
    Current Radio - 2.0.1701.02
    Stock Kernel - 3.4.0-perf-ga6edd5e
    All system apps are present
    No Modifications. AT ALL.

    If you meet the criteria above the OTA will complete.
    If you don’t meet the criteria or don’t want to wait for the OTA to hit your device then see below.

    Current OTA's

    4.4.4-KTU84P-from-4.4.3-KTU844L: http://android.clients.google.com/p....signed-occam-KTU84P-from-KTU84L.50b64331.zip Thanks @oldblue910

    Legacy OTA's

    All legacy OTA links can be found here: http://xdaforums.com/showpost.php?p=33631631&postcount=1 Thanks @oldblue910


    These are the 4 most popular scenarios. If you aren't sure where you fit, feel free to ask.


    Scenario #1
    You are completely stock. Unlocked/locked bootloader. No root
    Continue to Section A

    Scenario #2
    You are stock, with root. Custom Recovery without any modifications or deletions.
    Continue to Section B

    Scenario #3
    You are stock, with custom kernel, any modifications or removed system apk(s)
    Continue to Section C

    Scenario #4
    You are running a Custom ROM
    Continue to Section C


    Section A: adb sideload

    NOTE:Make sure you have the latest version of adb. It's attached at the bottom.

    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 power then immediately 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.


    Section B: Flashing in a custom recovery

    1) Download the OTA.zip and copy to your phone.
    2) Boot into recovery.
    3) Flash the OTA just like you would a ROM.
    4) Reboot.


    Section C: Let’s get back to stock

    There are a few ways to do this:

    Option #1) Flash the complete KTU84L image. Follow efrant’s guide: http://xdaforums.com/showpost.php?p=34552123&postcount=1
    a) If you want to keep your data & settings and are running the stock rom; only flash boot.img, system.img, and recovery.img (optional) with fastboot.​


    OR

    Option #2) Replace the stock images or .apk(s) you removed or modified.


    After completing the steps needed to return to “stock” make sure you meet all the criteria at the top of the page then revert to:

    Section A if you are running stock recovery.
    Section B if you are running a custom recovery.


    OR

    Option #3) Forgo the OTA entirely and flash the KTU84P Factory Image in fastboot. https://developers.google.com/android/nexus/images#occam

    If you need help with this follow efrant's guide


    Feel free to ask any questions you may have. I’ll do my best to answer them as quickly as possible. Perhaps others may answer them as well. Please read to see if your question has been answered before asking.


    Q&A Section:

    Q #1: I'm seeing a kernel related status 7 error when trying to apply the OTA
    A: Flash the system image along with the boot image. Some kernels (like franco for example) change a file or two in /system. So easiest way would be to re-flash the system. -Thanks efrant

    Q #2: The ota applied successfully but I lost my custom recovery and I want to re-root. How do I get root back?
    A: Flash the custom recovery of your choice in fastboot, then flash the SU.zip in recovery linked in Section B4.

    Q #3: I've tried everything but I'm still getting status 7 errors.
    A: Unfortunately you may have to start from scratch. Follow Section C1.


    Thanks to these members for adding additional info and helping add things I forgot. :)
    TheManii
    zim2dive
    davdigs
    eskeyy
    daverup
    xaueious
    Spaceman860
    efrant


    Updated: 4/17/14
    14
    Hey guys,
    Here is the download link for the OTA update courtesy of my sister's Nexus 4.

    It's from JWR66Y to KRT16S


    c7d8660af65b878835d5248252f51dcbf53c2001.signed-two-step.signed-occam-KRT16S-from-JWR66Y.d1b99704.zip

    http://android.clients.google.com/p....signed-occam-KRT16S-from-JWR66Y.d1b99704.zip

    Cheers!
    11
    android.clients.google. com/ packages/ota/google_mako/ebc8bad23772b5fd6e2907e48b4c74ba0ed58f21.signed-occam-JWR66V-from-JDQ39.ebc8bad2.zip



    Didn't downloaded yet

    Sent from my Nexus 4 using xda app-developers app