***The Official LG Nexus 4 Thread***

I use shakecalc here.but stock calc on N4 4.4.2 looks fine here....in landscape mode anyway :D
Just got the update to4.4.2.damn lost root again,that's about 3 times now in less than a month
 
If anyone's OTA update failed, you got to sideload.

If your sideload failed with Error 7, you need to flash the system img again to remove root, then sideload.

Nightmare :(
 
DarkShadow said:
If anyone's OTA update failed, you got to sideload.

If your sideload failed with Error 7, you need to flash the system img again to remove root, then sideload.

Nightmare :(
Click to expand...

Since KitKat this phone and OS has fast become the most annoying thing ever.

Don't even get me started on the useless Nexus 7 2012 I got a few months ago. It's next to useless :(
 
Nothing wrong with either my N4 or N7 (2013), or the pair of N7 (2012) I maintain for my nieces, all of which are running KitKat. All of which are much improved on 4.4.

Possible case of PEBKAC.
 
Not user error thank you very much! I've run custom roms on phones since I owned a HTC Desire. These last few rom updates have been a pain to update.

My Nexus 7 has run slow since I bought it before KitKat. Slow to unlock, slow to browse app drawer and an age to open certain apps. It just seems noticeably worst now.

I appreciate some people have no issues with devices and others do no need to PEBKAC
 
Why not just let them OTA as normal? This + restoring to factory settings every major update has never given me any problems on any of my nexus devices.
 
Had a very weird thing happen to my Nexus 4 twice this week.
Basically, when i was scrolling through the gallery there was like an electric buzz coming from the back of the phone, i could even feel it vibrate the phone when it did it, the phone them locked up and i had to restart it (holding the power button down).
Today i took a pic and pinched to zoom to look at the pic and the same thing happened electric buzzing and the phone vibrating from the back, the phone didnt lock up but it rebooted anyway :/

Has anyone else had this happen?
 
Has anyone had their device replaced through Google before? I'm having a problem with the screen staying black when I finish a call, it doesn't re-activate and therefore I can't hang up.

I requested a call from their support team today, I got a call back in less than a minute which was very impressive, however the impressive service stopped there. The guy I spoke to was useless, he didn't seem to know anything at all and took an age to respond to my questions, it was so annoying, like there was some sort of time delay of 3 seconds in his brain!

Anyway, after putting me on hold and speaking to others he came back and immediately offered a replacement, great I thought, however he then told me it was refurbished... Now I wasn't particularly happy about this, I only bought the phone 6 months ago so is still under warranty, is it unreasonable to expect a new replacement?

Anyone else had this? Do I have any rights here, or is a refurb my only option? Should I even be bothered about a refurb?
 
I suspect there are no new ones left as they cleared their stock so the only option is a refurbished or request a refund and hope the sales of goods act gives you enough for them to do the refund. I'm assuming you aren't using a screen protector which could be covering the sensor.
 
tals said:
I suspect there are no new ones left as they cleared their stock so the only option is a refurbished or request a refund and hope the sales of goods act gives you enough for them to do the refund. I'm assuming you aren't using a screen protector which could be covering the sensor.
Click to expand...

No screen protector.

Yes, this was the reason he gave. The phone is 'decommissioned', which is fair enough, but I don't fancy a refurb tbh. Underlying faults could still be there if they couldn't find an issue. Will the screen be pristine? Is the battery like new?

I could request a refund I guess, not sure I would get one back after 6 months though would I? Perhaps I could request play store credit.

Castor said:
Are you sure its not grease/dirt over the proximity sensor as ive had this before albeit on a different phone. holding it to your face for periods seems to get grime in that area and the phone stays black till i hit the power button.
Click to expand...

Could be I guess, can try it and see, but I do periodically clean the screen.
 
The Sale of Goods Act states that the company need only repair the device at the very least, so I am afraid you don't have any right to ask for a brand new one.

If it's a refurb, the battery should be brand new, as should the casing. There should be no issues whatsoever. If there are, send it right back and ask politely for a refund.

It's your call really: you can be polite, but firm and try and get a refund so you can buy an N5 (seems like the logical phone to switch to) or you can accept the refurb.
 
The refurb is more likely to work properly than the phone you have now, so I don't really see an issue. Are you hoping they'd send you an N5 instead or something?
 
Grrrrr

Still cannot update this phone to 4.4.2

It tells me there's a system update ready to install. It reboots the phone and it goes in to TWRP recovery to run the install. Then fails but no idea why.

Do I need to unroot? Hope I don't have to flash it back to stock. Fed up of reinstalling all my apps all the time.
 
Download the factory image: https://dl.google.com/dl/android/aosp/occam-kot49h-factory-02e344de.tgz

Open the flash-all.bat file and remove -w from the "flash zip", line and run the .bat. You will flash back to stock 4.4.2 without losing your data.

If you want to be cool, open the .zip and replace the recovery image with TWRP so you don't have to flash it yourself to re-root. Might as well remove userdata.img while you're there as well if you want to be extra safe.
 
Not good at all :(


Flash Stock + Unroot...
------------------------------------------------------------------


erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.031s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.452s]
finished. total time: 0.452s

sending 'bootloader' (3911 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: invalid bootloader image
)
finished. total time: 0.140s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s

archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.97
Serial Number........: 00796d05d292a9c5
--------------------------------------------
checking product...
FAILED

Device product is 'mako'.
Update requires 'grouper'.

finished. total time: -0.000s



Booting up your freshly flashed stock device...
------------------------------------------------------------------

Wait for your device to finish booting up...

- It may appear to be boot looping; just wait...

- It could take 5-10 minutes; please be patient...

When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.

NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.



Press any key to exit...
 
You must log in or register to reply here.
Back
Top Bottom