Database Users

[Q] Updating Nexus 4 once 4.2.2. is released

Just wanted to get a few pointers on the update process once 4.2.2. factory images are released.
I'm currently running CM 10.1 latest nightly complete with Faux's custom kernel. When the factory images are released, i want to take advantage of the new radio and bootloader, that hopefully will be shipping, along with anything else without having to fully wipe and start from fresh.
Please correct me if i'm wrong on any of my thoughts about how to update below, or if i've missed anything
Bootloader - extract from factory image and flash in fastboot with
fastboot flash bootloader bootloaderxxxx.img
Radio - extract from factory image and flash in fastboot with
fastboot flash radio radioxxxx.img
Kernel - hopefully faux will update once source drops and can be flashed via recovery
ROM - hopefully CM will update with 4.2.2 is AOSP and can be flashed in recovery, along with updated GAAPS
Am i missing anything else??
Thanks

That will do it.
You just have to hope they work with CM10.1 though...

peedub said:
That will do it.
You just have to hope they work with CM10.1 though...
Click to expand...
Click to collapse
Yeah I'll check that out before I do anything, fingers crossed it will be good!
I haven't missed anything out then, bootloader, radio, kernel, ROM is all there is to update?
Sent from my Nexus 10 using Tapatalk HD

Just not to start a new thread. Can anyone conform for me this: currently stock everything - except running CWM recovery.
I'll have to flash the stock recovery before trying to get the OTA update?

chrisastrous said:
Just not to start a new thread. Can anyone conform for me this: currently stock everything - except running CWM recovery.
I'll have to flash the stock recovery before trying to get the OTA update?
Click to expand...
Click to collapse
Yes...u wont be able to apply the OTA update with a custom recovery...but u can flash the update through CWM...

Stock everything, never been rooted.. will the OTA update erase any data whatsoever? When can we expect it?

dralways said:
Stock everything, never been rooted.. will the OTA update erase any data whatsoever? When can we expect it?
Click to expand...
Click to collapse
No the OTA will not erase anything. As for when you will get it? It should be soon. If you're impatient you can flash it manually buuuut i'd hold off on that becuase of all of the" help trouble after updating to 4.2.2" threads popping up recently.

I just received the update downloaded notification on my Nexus 7 but still nothing on the N4.

uploder said:
No the OTA will not erase anything. As for when you will get it? It should be soon. If you're impatient you can flash it manually buuuut i'd hold off on that becuase of all of the" help trouble after updating to 4.2.2" threads popping up recently.
Click to expand...
Click to collapse
Will the stock 4.2.2 wipe my apps? I know it will damaged the internal SD.
What about my apps adn corporate data? Pls advise
Ramu

darkkid85 said:
Will the stock 4.2.2 wipe my apps? I know it will damaged the internal SD.
What about my apps adn corporate data? Pls advise
Ramu
Click to expand...
Click to collapse
Just ran the update my phone is in exactly the same state as before. Nothing got deleted

chrisastrous said:
Just ran the update my phone is in exactly the same state as before. Nothing got deleted
Click to expand...
Click to collapse
Thanks dude,
i just did too, all info reimained intact
ramu

darkkid85 said:
Thanks dude,
i just did too, all info reimained intact
ramu
Click to expand...
Click to collapse
Well how about giving me a thanks lol
Apparently superuser remains but you still lose root! Will get back to you when I find out more info.

[Q] 4.3 update annoyance

My rooted, but otherwise standard N4 has been telling me it has downloaded the 4.3 update every couple of days since last week, but it won't install. All I get is a dead Android with a red triangle and the word Error! written above him. The phone then starts playing up, re-booting etc and I have to go into recovery and clear the cache for it to work properly again, still on 4.2.2 (obviously).
Now I'm not overly fussed about this update, but I do take issue with something that won't work taking up space in my phone (I'm tight and bought the 8GB one!), so my question is; can I get into where this duff download is being stored in my phone and delete it?

You should find it in /cache

yes, my ota update was in /cache folder; just use root manager or something similar.
Or un-root it, apply update, then re-root again. Win win.
Sent from my Nexus 4 using Tapatalk 4 Beta

Thanks for that, I deleted it!
I never even considered unrooting the phone first, to be honest, but it looks quite long winded to do. I assume there will soon be 4.3 ROM builds where that won't be necessary?

simonali68 said:
Thanks for that, I deleted it!
I never even considered unrooting the phone first, to be honest, but it looks quite long winded to do. I assume there will soon be 4.3 ROM builds where that won't be necessary?
Click to expand...
Click to collapse
You need the OTA to flash the new boot loader, but you can do it manually too so....not a big deal
Nexus 4+ Franco + LTE

Right, it has now downloaded for the 3rd time, so I'm not gonna bother deleting it again. Does anyone know a method of removing the notification?

joshuab227 said:
Finally managed to stop the update from downloading though ...
Heres what I did :
Installed Autorun Manager from the Play store.
Then entered its recommended advanced mode.
Went into the settings and enabled system entries and system app disable.
Disabled com.android.gsf.update.SystemUpdateService$Reciever under Google Service Framework
Hope this helps everyone else facing this problem and thanks to mikebz5 for the original post.
Sent from my Nexus 4
Click to expand...
Click to collapse
this is from another thread. Worked for me

That did the trick. Ta very muchly!

Uhh, system update to 4.3 downloaded today. I'm scared . . .

What. In. The. World. Got the "System update downloaded" notification this afternoon, and was puzzled since I got this a little over three weeks ago for 4.3, an experience that soft bricked my phone and ruined by life for a few days:
http://forum.xda-developers.com/showthread.php?t=2387196&page=3
Well, lo and behold, today's system update claims to be for 4.3 again:
Only I'm already ON 4.3.
Finally got everything rooted again and set up the way I want, and it's like Google knows it's time to come in and bork my phone again. I did a little poking and saw that this is no doubt the update from JWR66V to JWR66Y:
http://www.droid-life.com/2013/08/2...ta-updates-for-the-nexus-7-hspa-galaxy-nexus/
Only after the last experience, I'm friggin terrified to mess with this and possibly end up in a bootloop or stuck at the X screen forever again. (I'm rooted, no custom ROM, just custom launcher.) EDIT: I should add that, since the last update, I've updated my radios to be able to use 4G LTE, installed the Android browser and all my bookmarks, and made a slew of other customizations, so I'm annoyed that this update comes three weeks on the heels of everything I set up.
Should I try the OTA install or flash the OTA zip files in CWM recovery like the article suggests? Most pain-free ways to ensure my current setup is reinstated without too many gray hairs? Any suggestions welcome. Thanks in advance!

It won't install because your rooted. The new root method relies on the recovery from boot.p file in system that SU changes.
You can flash this update zip file that has been modified not to check that file http://forum.xda-developers.com/showthread.php?p=44886292
BLACKED OUT LTE N4

The update is occurring because there is a new OTA that is build JWR66Y whereas yours is the V build.
Sent from my Nexus 4 using Tapatalk 4

zephiK said:
The update is occurring because there is a new OTA that is build JWR66Y whereas yours is the V build.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, thanks--I noted that. My question at the bottom of my post is, what's the best way to ensure I can back up/capture all the customizations I made since so I don't have to go through the nightmare of trying to take three weeks to set everything up again?

spaceman860 said:
It won't install because your rooted. The new root method relies on the recovery from boot.p file in system that SU changes.
You can flash this update zip file that has been modified not to check that file http://forum.xda-developers.com/showthread.php?p=44886292
BLACKED OUT LTE N4
Click to expand...
Click to collapse
OK...I'm guessing that notification will go away once I've flashed that ZIP? My real question is whether once that's done if I have to re-set everything up all over again or if there's a way to backup my new radios/browser/etc.

nikonjunkie said:
OK...I'm guessing that notification will go away once I've flashed that ZIP? My real question is whether once that's done if I have to re-set everything up all over again or if there's a way to backup my new radios/browser/etc.
Click to expand...
Click to collapse
I have read your edits to the OP and you have changed system files so the update won't install. You modified the build prop for lte and browser app maybe other stuff too. With this update your OK with not having the correct radio.
BLACKED OUT LTE N4

Weird issues after kitkat upgrade

Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,

Riimez said:
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Click to expand...
Click to collapse
Let's start from the beginning.
Can you describe your method of flashing in case you are doing something wrong? Please describe as much information as possible.
What is your phone model?

y2kkingboy said:
Let's start from the beginning.
Can you describe your method of flashing in case you are doing something wrong? Please describe as much information as possible.
What is your phone model?
Click to expand...
Click to collapse
9005. sorry it was a couple of days ago so I dont really remember. I flashed a 4.4 bootloader (standalone) then tried flashing a 4.4 rom i believe it was sweetrom.

Riimez said:
9005. sorry it was a couple of days ago so I dont really remember. I flashed a 4.4 bootloader (standalone) then tried flashing a 4.4 rom i believe it was sweetrom.
Click to expand...
Click to collapse
I believe the best thing to do now is to flash stock ROM and make sure to full wipe everything even internal memory.
If you have external memory, back up what ever you think necessary to it, the remove it from the device and keep it out.
That clean start well give you a good indication whether the problem is based on a bad flash or there is something wrong with the device.
If everything is running smoothly, we will see about flashing custom ROM.

y2kkingboy said:
I believe the best thing to do now is to flash stock ROM and make sure to full wipe everything even internal memory.
If you have external memory, back up what ever you think necessary to it, the remove it from the device and keep it out.
That clean start well give you a good indication whether the problem is based on a bad flash or there is something wrong with the device.
If everything is running smoothly, we will see about flashing custom ROM.
Click to expand...
Click to collapse
Yep its what ive done, reflashed stock completly and removed sd card. Still no dice - running complete stock 4.4 still with this problem.
Could this be an EFS problem?

If it were an efs problem you wouldn't even boot in most cases.
Can you describe how you flashed stock ROM? Maybe you did it wrong.
Sent from my SM-N9005 using Tapatalk

Sorry to hear that..base on my experienced happened also on my S4..luckily still under warranty..have to wait for 2 weeks...company says faulty mother board and speaker. Hope this helps....
Sent from my SM-N900 using xda premium

Riimez said:
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Click to expand...
Click to collapse
NEE region? - if so it has issues with 4.4.2, @nex7er had the same issues, and if you're using SweetROM I believe he pm'd not-i the fix for it. -- It can be fixed though.

Maybe completely wipe it (System, Data and all) and then Flash stock with Odin?

After kitkat upgrade.. if i use camera app such as camera 360 Or picsart, i can't save my photo to sdcard. It's error, Has anyone had or know how to resolve this problem???

Blancos4Lyf said:
Maybe completely wipe it (System, Data and all) and then Flash stock with Odin?
Click to expand...
Click to collapse
Yep. Still no dice.

Riimez said:
Yep. Still no dice.
Click to expand...
Click to collapse
I did post the reason on the last page what I think it might be...... if you're in a Nordic region or even have a nordic model it's a common problem, if you search around you'll see others that have the same issue (notably ne7xer). -- If it's not that, then it's a warranty job due to faulty HW
EDIT: you could try a complete wipe including re-partitioning, but that's a bigger job that you'd want to do in all honesty.

radicalisto said:
I did post the reason on the last page what I think it might be...... if you're in a Nordic region or even have a nordic model it's a common problem, if you search around you'll see others that have the same issue (notably ne7xer). -- If it's not that, then it's a warranty job due to faulty HW
EDIT: you could try a complete wipe including re-partitioning, but that's a bigger job that you'd want to do in all honesty.
Click to expand...
Click to collapse
Could be my last option considering knox is tripped..
Got a link to a tutorial for re-partitioning?

Grab a PIT file for your device; - then you flash firmware with Odin / PIT file. - I have never done it, nor do I fancy doing it, but have a read (journeyman posted asking how and done it, it's in this section Q+A) - I can never remember whether you flash the PIT first then the firmware or both together. I wouldn't want to hazard a guess just in case though.
But if you've tripped KNOX, then yes, seems like it could be your last option, unless you have tried some various custom ROMs? ( I know sweetROM seems to be the master fix for any issues peple have on KK atm) could just be a stock issue currently that will more than likely get a fix at some point.
EDIT As yours is an AU phone, possible it could be a HK model? - from KOGAN? I know some AU users have had HK models from them.
EDIT2: When I flashed HAL ROM, @theresident stated in his how to OP that we needed to format /system during install - It's possible this may also fix it, but that wipes your entire system obviously and *IF* it doesn't boot up you then have issues
EDIT3 : quote from HAL ROM OP
Instalation:
1. Copy the zip to the phone
2. Reboot to Recovery/CWM
3. Wipe Data/Factory Reset
4. Wipe Cache
5. Wipe Dalvik Cache
6. Mounts and Storage then click "Format /System" (This won't delete any of your data)
7. Install.. wait one minute and ROCK !!!
Click to expand...
Click to collapse

crazy_777 said:
After kitkat upgrade.. if i use camera app such as camera 360 Or picsart, i can't save my photo to sdcard. It's error, Has anyone had or know how to resolve this problem???
Click to expand...
Click to collapse
You are hijacking.
Anyway,
1. Install es file manager or any file reader with root.
2. navigate to /System/etc/permissions
3. open "platform.xml" file to edit
4. look for the stack that has "WRITE_EXTERNAL_STORAGE"
you will find something like <group gid="sdcard_r" />
5. make sure these lines are there, if not, add them
<group gid="sdcard_rw" />
<group gid="media_rw" />
That's it

Android is starting... Optimising app xx of xx on every boot

Hi all,
Have had my Nexus 10 with a few years now and rooted it not long after I got it, stuck with stock rom though.
All was fine until I updated to the latest LMY49H Build using NRT (Nexus Root Toolkit) which I always do and it has never let me down.
But with this update I get the swirling balls, Android boot screen then about 10 minutes of "Android is starting... Optimising app xx of xx". I have wiped via settings, via recovery (TWRP and stock), Flash Stock and Unroot (NRT), Root (NRT which wipes data), cleared cache, dalvik, data using TWRP but every time I end up with this optimising apps screen.
I have tried restoring previous versions at setup (apps, wallpapers etc.) and I have skipped all setup options for a clean fresh copy but always with the same result.
I have been looking around but didn't find someone running stock rom with the same problem, If I missed it then I'm sorry.
Please someone help me as I'm going on a trip soon and will need my tablet!

Could be your flash memory is wearing out. When you are using TWRP try copying a file then reboot into TWRP and see if the file is still there. If it is gone it is bad flash memory and you need a new motherboard...
Sent from my LGLS991 using Tapatalk

psiphi said:
Could be your flash memory is wearing out. When you are using TWRP try copying a file then reboot into TWRP and see if the file is still there. If it is gone it is bad flash memory and you need a new motherboard...
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
Sorry I don't get what you mean. do you mean to flash a file? (or at least see if TWRP finds the file?)
e.g. copy a file, supersu.zip or something in downloads folder, then boot into TWRP to see if its in the folder ready to flash?
Oh I hope its not the motherboard, the tablet has hardly been used compared to others I know of.
Do you know if its safe to revert to a previous version of android using NRT? LMY49H or even G? I was happy enough with those versions and only updated thinking it would clear the security update (7.2mb) which I ended up doing manually anyway (Unroot & Update, install security update, Root).
I had a problem like this years ago when I flashed a ROM to my old Galaxy S4, flashing a different ROM fixed the problem then, I'm hoping it will now too!
Thanks for your help

fado5ster said:
Sorry I don't get what you mean. do you mean to flash a file? (or at least see if TWRP finds the file?)
e.g. copy a file, supersu.zip or something in downloads folder, then boot into TWRP to see if its in the folder ready to flash?
Oh I hope its not the motherboard, the tablet has hardly been used compared to others I know of.
Do you know if its safe to revert to a previous version of android using NRT? LMY49H or even G? I was happy enough with those versions and only updated thinking it would clear the security update (7.2mb) which I ended up doing manually anyway (Unroot & Update, install security update, Root).
I had a problem like this years ago when I flashed a ROM to my old Galaxy S4, flashing a different ROM fixed the problem then, I'm hoping it will now too!
Thanks for your help
Click to expand...
Click to collapse
Not flash your memory but check your: https://simple.wikipedia.org/wiki/Flash_memory
And yes it is safe to restock (another) ROM.

fado5ster said:
Sorry I don't get what you mean. do you mean to flash a file? (or at least see if TWRP finds the file?)
e.g. copy a file, supersu.zip or something in downloads folder, then boot into TWRP to see if its in the folder ready to flash?
Oh I hope its not the motherboard, the tablet has hardly been used compared to others I know of.
Do you know if its safe to revert to a previous version of android using NRT? LMY49H or even G? I was happy enough with those versions and only updated thinking it would clear the security update (7.2mb) which I ended up doing manually anyway (Unroot & Update, install security update, Root).
I had a problem like this years ago when I flashed a ROM to my old Galaxy S4, flashing a different ROM fixed the problem then, I'm hoping it will now too!
Thanks for your help
Click to expand...
Click to collapse
Right, I mean just copy a file to it that is not already there and rebooting it and seeing if the file is still there.
If it works then you probably don't have a hardware issue.
It is always worth trying to flash a known working rom, though you may need to hard reset to get it working.
Sent from my LGLS991 using Tapatalk

mr.natural said:
Not flash your memory but check your: https://simple.wikipedia.org/wiki/Flash_memory
And yes it is safe to restock (another) ROM.
Click to expand...
Click to collapse
Sorry, I know what flash memory is, I mean I didn't know what he meant by copy using TWRP.
I may try flash the previous LMY49H ROM then
psiphi said:
Right, I mean just copy a file to it that is not already there and rebooting it and seeing if the file is still there.
If it works then you probably don't have a hardware issue.
It is always worth trying to flash a known working rom, though you may need to hard reset to get it working.
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
OK cool, thanks for clearing that up..
This literally just started when I updated to the new ROM (LMY49J). I have done a full wipe already so hard reset shouldn't be a problem, nothing left on it now anyway. Think I may have done it already tho
Before the update I had a full TV series and a few movies saved into it and it had no problems playing/saving anything. Think I may try stock flash & unroot with LMY49H and see how that goes.. I'm away from it at the moment so hopefully will try tomorrow.
I have a feeling it is saving files though, displayed my old wallpaper when I restored from previous tablet option on setup. Must be saving this picture somewhere after initial download at setup. It is booting up eventually like, just after it optimizes the apps, maybe 5-10min.
What other issues could I be having?

You really have to create or copy something new and reboot the tablet to test. Files and setting will stay in the cache and so give the illusion working unless you reboot.
Also are you doing a clean shutdown via the menu after hitting the power button for no more than 2 seconds? Doing power off without going through menu can cause your behavior.
Sent from my LGLS991 using Tapatalk

psiphi said:
You really have to create or copy something new and reboot the tablet to test. Files and setting will stay in the cache and so give the illusion working unless you reboot.
Also are you doing a clean shutdown via the menu after hitting the power button for no more than 2 seconds? Doing power off without going through menu can cause your behavior.
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
OK I will try copy something tomorrow.. A TV show or something..
Yes I always hit power button and select "Power Off" and let it shut down, have since day 1!
Will keep you updated,
Thanks again

fado5ster said:
OK I will try copy something tomorrow.. A TV show or something..
Yes I always hit power button and select "Power Off" and let it shut down, have since day 1!
Will keep you updated,
Thanks again
Click to expand...
Click to collapse
You have to copy something in recovery mode with twrp. From a different directory (or usb stick to your device) and then reboot to see if it is still there.