Volume down and power?
Just done that and still wont see it
List of devices is blank.
4.2.2 Update ??
- Thread starter IamIrene
- Start date
- Status
Volume down and power?
Just done that and still wont see it
List of devices is blank.
Yep tried that but it wont see the phone. I've reinstalled the drivers etc and still nothing.
Anyway, im off to bed. i'll try later!!
Update done via the toolkit
Used OTA root keeper to save and restore root.
First thing: data drops seems NOT fixed in my case.
Sent from my Nexus 4 using xda premium
Used OTA root keeper to save and restore root.
First thing: data drops seems NOT fixed in my case.
Sent from my Nexus 4 using xda premium
Connect the phone to the pc with the usb cable and look in device manager for the nexus 4. Remove the device and diconnect and reconnect the usb cable and force the naked usb driver to be the installed usb driver instead of windows looking for it and installing it.
Naked usb driver 0.72 is here http://forum.xda-developers.com/showthread.php?t=1998650.
Last edited:
Thats the one i have installed. I used it just last week to root the phone and flash a custom rom. I disliked it so chucked the stock software on and relocked the bootloader. Now it just wont work lol
It works fine for me, then i can`t help you and i hope someone with more knowledge can. Good luck mate
I renabled location settings with GPS just to try battery life.
Has the same issue...with N4 and N7 and latest Google drivers.
Finally used OS X where you don't need drivers.
Sent from my Nexus 4 using Tapatalk 2
Has the same issue...with N4 and N7 and latest Google drivers.
Finally used OS X where you don't need drivers.
Sent from my Nexus 4 using Tapatalk 2
Last edited:
I did exactly that and it worked.
Thank you.
ot: I love Portsmouth, been there for my Masters. :good:
Grrr i cant get this computer to see the phone in recovery mode
Installed the drivers again to make sure, it sees it before i adb reboot recovery to sideload this update then refuses to see the phone.
Any ideas?
EDIT:- i have usb debugging turned on as well but still wont see it
This is maybe not the simplest way to do it, but this works:
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode
It let's you use sideload and is very quick if you already have the SDK in place. I spent a long time with the same issue before I found this.
eagleeyetom
Retired Senior Mod & DC Lead - Active Pole Dancer
Please use this thread to discuss 4.2.2 update.
http://forum.xda-developers.com/showthread.php?t=2145848
http://forum.xda-developers.com/showthread.php?t=2145848
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
261) OTA Update are not delayed by the fact that the Nexus 4 is not "fully AOSP supported"
2) The Nexus 4 isn't FULLY supported by AOSP. Why ? Blame Qualcomm/LG. If you don't know how the stock kernel on Mako works, you'll learn something. The freq of the CPU is changed when you touch the screen. max_freq is still at 1.5Ghz but the min_freq is pushed to 1Ghz when you touch the screen and goes down to 384Mhz if you don't touch it for x milliseconde and the load is low.
How does this work ? mpdecision. What's this ? Can you eat it ?
Nope. Well, I wouldn't try ! mpdecision is a binay closed source by Qualcomm. Why is it closed ? because Qualcomm don't want someone steal their fantastic idea (DERP RAMP THE MIN FREQ TO 1GHZ WE ARE GENIUS).
So what ? So. Mpdecision is NOT a part of the source for Nexus 4 (obivously, it's closed sauce) BUT this binary is pulled from the Nexus 4 by developpers.
Which means : The official source of Google for Nexus 4 is 99.9% complete, few binaries like this one aren't open. OTA will come no matter what (this has nothing to do with Google update). Also this is not a problem for developpers. Obviously look at all the ROM we have but, for exemple, we couldn't change the mpdecision binary to "hey, it's alright to bump the freq when screen is touched, but go only to 912Mhz, not 1Ghz". Hence why many kernel dev like Franco or Faux did their own way of changing freq/pluggin cores in their kernel
Damn, wish I'm clear, already drunk too many beers bloody lord25Here's what I got:
W/RecoverySystem( 1007): !!! REBOOTING TO INSTALL /cache/de8b8d101614.signed-occam-JDQ39-from-JOP40D.de8b8d10.zip !!!
Update: I'm in CA and got my Nexus on Dec 13th.17Not sure if Google will OTA 4.2.2, given the 100 or so devices they have shipped, they might just send an intern to your house to update it for you
or we'll get an ota notification, but when when we click to download it'll say the update is on backorder and should ship in 6-7 weeks:banghead:
Sent from my Nexus 4 using xda app-developers app17I think it's become pretty evident what's going on here: the Illuminati don't want us to have this update on the Nexus 4 because it would make our phones TOO powerful and then we would be able to pick up the frequencies of the cloaked alien vessels that hover in the upper-atmosphere as they bombard our brains with radiation in an attempt to prepare us for their arrival and our enslavement. The Illuminati (of course) will become the "chosen leaders" of humanity as we are forced into our new roles.
(I mean, if we're going to go with a conspiracy theory, why not at least make it an interesting one?)
