Database Users

[Q] Nexus 4 rooting and oem updates after

Hi,
I know there is a lot of comments about why root nexus 4. The reason for me is that I know there is a lot of small fixes which i can install (battery kernel... I think i can install just to rooted phpne) but for me the main thing is that I know in time I will get very lazy about installing new roms. I have htc desire and last time i installed new rom year ago. The same with my xoom.
So my question is, if i root my phone, will i be abble to update original rom just by going to settings-about-update? It doesnt work on my desire and xoom. But i installed unoficial roms there. But if i just want to unlock the phone for little fixes and still be able to get updates from google... Is that possible?
Sorry if it is stupud question,...
Thx

milos797 said:
Hi,
I know there is a lot of comments about why root nexus 4. The reason for me is that I know there is a lot of small fixes which i can install (battery kernel... I think i can install just to rooted phpne) but for me the main thing is that I know in time I will get very lazy about installing new roms. I have htc desire and last time i installed new rom year ago. The same with my xoom.
So my question is, if i root my phone, will i be abble to update original rom just by going to settings-about-update? It doesnt work on my desire and xoom. But i installed unoficial roms there. But if i just want to unlock the phone for little fixes and still be able to get updates from google... Is that possible?
Sorry if it is stupud question,...
Thx
Click to expand...
Click to collapse
I believe that OTA updates just flash the stock kernel again, so you could unlock, root and flash a different kernel without fear of losing OTA updates. However, OTA updates will force you to lose root and you will have to flash the custom kernel again. You will continue to get notifications that say that there is a new update as long as you aren't also on a custom ROM

If you are running the stock ROM you will still get and ota notification. However if you've made any modifications such as a custom kernel, build.prop edit, system.ui edit, etc. The ota will fail upon installation.
If all you do is get root access it will install fine. You'll just have to flash the su binaries again.
Sent from my Nexus 7 using xda premium

Actually, SU has a survival mode that will preserve root even after OTA. CWM will also protect ropt so you don't have to reroot it. My Nexus 7 has been stock rooted and went thru 2 OTAs without losing root.
Skickat från min Nexus 4

Sorry to hijack,
My question is, I am rooted with stock rom but have CWR and a different kernel.
When the next OTA comes, I would need to download the whole rom because of CWR and kernel.
Question I have is that if I want to flash the OTA, would I need to wipe my device or can I just flash the ROM ontop. I know my old device (DHD) I had to wipe everything before I install the ROM. The reason why I am asking is because can I get away with just flashing on top therefore keeping all my data on my device so I no need to restore it via titanium backup (I am lazy)

NEW OTA UPDATE- MF9.. Questions thread.

Who knew a MONDAY would be such an awesome day! New OTA Update MF9 as 1st reported HERE by @jonathanhtc . Any questions can go here guys....
I'll start off with a question I have: Does this mean that all of our mods will have to be re-done to be able to be flashed on the new update? ie: Hotspot mod, 4 in 1 reboot mod, etc. all have to be re-done to be able to work on the new software update?!

Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.

xonone said:
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
Click to expand...
Click to collapse
That's why I'm definitely waiting till the devs take a look at it before I download it. It definitely wasn't there with MDC and MDL.
Sent from my SPH-L720 using xda app-developers app

Yes same here. BUT some new things that were reported are: Transparent notification bar with any wallpaper, new smart pause toggle, smoother UI (less lag), move apps to SD card, and KNOX is finally deployed along with Briefing and SPDclient.

First things first. Let's see what partitions got an update.
And someone should put a bug in Agat's ear to patch his kernel with the latest updates.

garwynn said:
First things first. Let's see what partitions got an update.
And someone should put a bug in Agat's ear to patch his kernel with the latest updates.
Click to expand...
Click to collapse
I already posted in his thread about an hour ago that source is up
Sent from my SPH-L720 using Tapatalk 4 Beta

I wonder if this is basically the same update that the international version got. Hopefully it is, and it fixes the "smearing issue" and also we get the HDR video recording!

I heard people were unable to unlock to use internationally. Some said sprint unlocked but software restrictions remained. Do you think this update might fix that? And im not talking for use withing the U.S. mainly outside (Europe)
Sent from my SPH-L720 using Tapatalk 2

Okay, new bootloader, modem, kernel.
2 secondary bootloaders updated as well as rpm and tz.
Interesting that everything backs up to mmcblk0p22 before writing the new one.
Don't recall seeing that in updates for other devices.
New Fingerprint is just swap out MDL with MF9.
As mentioned, Knox is there. Makes me wonder what else was locked down with it.
Updated OCR among many updated binaries.
A lot of the binaries - in particular, vendor blobs - have an update.
I'll need someone to dump the system partition once it's patched for the new vendor files.
Hopefully good news for AOSP builds.
I'm asking to see if the previous sources have any info - but they've already stated not to expect anything.
There are a few questions that need to be figured out:
1) What is in the new bootloader? Are we locked like most of the others?
2) Can we revert bootloaders after flashing - and if so, what does it take to do so?
3) Root on new build?
All of this is going to require a test device, which sadly at the moment I am now without.
All the problems with the N2 left me with a Spare N2 and now without an S4.

xonone said:
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
Click to expand...
Click to collapse
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us

shabbypenguin said:
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
Click to expand...
Click to collapse
Could you post the steps you used to update & restore root please?

illdini said:
Could you post the steps you used to update & restore root please?
Click to expand...
Click to collapse
you apply the ota, flash recovery via odin and then flash supersu. if youd rather skip a step im pretty sure you can use ota root keeper

shabbypenguin said:
you apply the ota, flash recovery via odin and then flash supersu. if youd rather skip a step im pretty sure you can use ota root keeper
Click to expand...
Click to collapse
When applying the OTA, were you rooted and flashed with a Custom Recovery (i.e.-CWM or TWRP)? Or were you completely stock?

chenry944 said:
When applying the OTA, were you rooted and flashed with a Custom Recovery (i.e.-CWM or TWRP)? Or were you completely stock?
Click to expand...
Click to collapse
Judging by his earlier post I'm guessing custom recovery is probably not the best way to flash.
I have the same question BTW I'm rooted, with TWRP recovery, but stock ROM. Have installed a few mods (hotspot, camera shutter sound disabled. Had XPosed framework installed with a couple of mods, but removed those later).
What would be the safe way for me to install the new update? I actually like some of the features that Samsung added, so not looking to switch away from stock ROM for now.
I'm hoping that knowledgeable developers will provide guidance in the next few days

jj14 said:
Judging by his earlier post I'm guessing custom recovery is probably not the best way to flash
Click to expand...
Click to collapse
Yea I read that post I am just trying to get clarification for myself and everyone else in which way he did flash it.

shabbypenguin said:
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
Click to expand...
Click to collapse
Best news of this thread! Thanks for taking the chance!
Sent from my SPH-L720 using Tapatalk 4 Beta

yea i was stock odex from crawj and i hit errors while flashing it twrp, i flashed stock kernel and stock recovery and tried and it still failed so i modded teh zip to forcibly install, i now have no mobile data and my modem isnt updated. so my suggestion, dont follow my lead
im currently flashing MDC stock tar to fully update all the way.

Got the Modem Updated to MF9 using Odin without going back to Stock, uploading the odin package now, and will be updating the thread here -> http://forum.xda-developers.com/showthread.php?t=2338919

Does this include the security update Google announced would be coming to OEMs?

Now if i update to mf9, will it affect custom roms that are built around MDL, or AOSP?

[Q] Does rooting my Nexus causes OTA updates to fail?

Hi all,
I've been searching this forum (and the rest of the internet) for this question but there are not really similar answers.
I would like to root my nexus 4 just to be able to change the host file in the system folder. The rest if the phone I would like to remain stock (for now). But since android 4.4 is coming up I was wondering if it is still possible to receive the OTA update after performing this action.
Anyone knows an answer to this question?
Verstuurd van mijn Nexus 4

Mr. Tijntje said:
Hi all,
I've been searching this forum (and the rest of the internet) for this question but there are not really similar answers.
I would like to root my nexus 4 just to be able to change the host file in the system folder. The rest if the phone I would like to remain stock (for now). But since android 4.4 is coming up I was wondering if it is still possible to receive the OTA update after performing this action.
Anyone knows an answer to this question?
Verstuurd van mijn Nexus 4
Click to expand...
Click to collapse
edit: I am checking on something for you... you will receive OTA updates but checking to see if host file is one of the files it checks before it upgrades.
More than likely any changes to your system folder will cause it too fail
http://forum.xda-developers.com/showthread.php?t=2417810

In my experience you still receive OTA updates, but you lose root while updating. I'm not sure if the hosts file is changed though.

If you're rooted and you've stock recovery then you'll be able to Upgrade but if you've rooted n installed 3rd party recovery then you'll receive update but it won't install. It will fail.

meZQureshi said:
If you're rooted and you've stock recovery then you'll be able to Upgrade but if you've rooted n installed 3rd party recovery then you'll receive update but it won't install. It will fail.
Click to expand...
Click to collapse
Are you sure about that? I've been running cwm recovery ever since 4.2.0. Every ota update was received and installed without issues, but I always simply lost root until a new method for the new android release appeared.

You can still receive OTA but I would suggest not accepting it and flash it manually using a "safe" method. The OTA update from 4.2 to 4.3 caused problems on rooted phones. Usually it is fine but 4.3 changed the file system which caused the problem, so better be safe than sorry.
Sent from my Nexus 4 using Tapatalk

Thank you all for your replies, this tells me again that it is quite difficult to say what happens. Since KitKat is probably coming to the Nexus 4 one of these days I will stay stock for now and decide later if I want to root my phone.

I used superSU Pro, and turned on "survival mode" when I did the OTA update to 4.3, and didn't have any problems losing root. Sometimes I'll get a message say I may have lost root access, but I've never had any problems with apps that require root.
Sent from my Nexus 4 using XDA Premium 4 mobile app

on the last update.. I wasn't getting the OTA until I unrooted. I think you have to unlock the bootloader too.. then I immediately received the OTA. I didn't have stock recovery. I was glad that I didn't have to wipe everything.. I then re-rooted.. was good to go.

ROM and clockwork question

hey everyone, Im a newbie when It comes to roms and flashing, I currently have clockwork mod and stock 4.4.4 and wanted to ask will I get the official lollipop? Even if I have clockwork mod? But stock KitKat? Thank you for reading

michalziom29 said:
hey everyone, Im a newbie when It comes to roms and flashing, I currently have clockwork mod and stock 4.4.4 and wanted to ask will I get the official lollipop? Even if I have clockwork mod? But stock KitKat? Thank you for reading
Click to expand...
Click to collapse
as far as i know, and that can be wrong, if your android is untouched (no root or anything else (like xposes framwork)) you will get the update over the air.
BUT if you don't there are factory images that you can download and flash your phone quite easily
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
or a toolkit to do it automatically
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
i would recommend to do it with the first method. if something goes wrong you will know what is it and you can ask for help. with the toolkit if something goes wrong things are more complicated to find the error.
P.S. if you decide installing the factory images via console (first option), it is highly recommended to read the entire process first and after do the procedure.

My phone is rooted, but i dont have any custom ROMs or framework , will this affect it? Or when I get the update my root will simply be gone?

michalziom29 said:
My phone is rooted, but i dont have any custom ROMs or framework , will this affect it? Or when I get the update my root will simply be gone?
Click to expand...
Click to collapse
You'll lose root and the custom recovery with the ota. But if you haven't modified / deleted any system files you should get the ota.
Sent from my Nexus 5 using XDA Free mobile app

I've searched some threads and some said you don't get ota if you have clockwork mod (I have it) and I really don't know what to do...should I go back to stock? I'm not good with that stuff and afraid I will brick it, any ideas or advice?

michalziom29 said:
I've searched some threads and some said you don't get ota if you have clockwork mod (I have it) and I really don't know what to do...should I go back to stock? I'm not good with that stuff and afraid I will brick it, any ideas or advice?
Click to expand...
Click to collapse
You should be ok. If you're really worried about cwm you could flash the stock recovery image in fastboot. But I wouldn't unless the ota fails, which it shouldn't
Sent from my Nexus 5 using XDA Free mobile app

Thank you one more question, will I still get ota notification ? As in, it might fail but will I still receive like I would normally?

michalziom29 said:
Thank you one more question, will I still get ota notification ? As in, it might fail but will I still receive like I would normally?
Click to expand...
Click to collapse
Yes, you'll get it and it will download
Sent from my Nexus 5 using XDA Free mobile app

Thank you, I was happy that android L is so close but then I saw people say those with clockwork won't get it, thank you for the answers and clearing it up!

michalziom29 said:
Thank you, I was happy that android L is so close but then I saw people say those with clockwork won't get it, thank you for the answers and clearing it up!
Click to expand...
Click to collapse
No problem
Sent from my Nexus 5 using XDA Free mobile app

Do you by any chance know if android L Is releasing today? I've heard many people say Nov 3 rd for nexus devices

michalziom29 said:
Do you by any chance know if android L Is releasing today? I've heard many people say Nov 3 rd for nexus devices
Click to expand...
Click to collapse
I think you'll see it in the next couple of weeks, not today. The n4 may be even longer
Sent from my Nexus 5 using XDA Free mobile app

Alright, thank you again for clearing things up!

It's also worth noting that Google pushes update at different times depending on which area you live in, so even if you read on the news that Lollypop is released on the Nexus 4, it may take a while for your phone to receive the OTA.

Personally, I advice you to install TWRP recovery, its safe and easy to install kernels and roms

Please help upgrading Nexus 7 stock 4.4.4

About a year ago I was going to upgrade my nieces stock Nexus 7 wi-fi tablet on 4.4.4 but come to find out there was some bug in the OTA update that would brick the tablet. You had to jump through a bunch of hoops to update it like factory reset. Once my niece heard erase she didn't want any part of that. Fast forward to now and she got a fitbit type device and the software isn't compatible with the current version of the OS. So my question is...Is that bug fixed so I can take the OTA update now or do I still have to jump through all those hoops to do it? If I do have to jump through the hoops then how do I do it? Thanks in advance for any help you can give.

BoDontKnowDiddley said:
About a year ago I was going to upgrade my nieces stock Nexus 7 wi-fi tablet on 4.4.4 but come to find out there was some bug in the OTA update that would brick the tablet. You had to jump through a bunch of hoops to update it like factory reset. Once my niece heard erase she didn't want any part of that. Fast forward to now and she got a fitbit type device and the software isn't compatible with the current version of the OS. So my question is...Is that bug fixed so I can take the OTA update now or do I still have to jump through all those hoops to do it? If I do have to jump through the hoops then how do I do it? Thanks in advance for any help you can give.
Click to expand...
Click to collapse
I did update a few days ago and it was ok untill it was time of the 5.1.1 update - brick, so I downloaded nexus root toolkit to get it quickly done.
Make backup using gmail or just root using nexus tool, backup with titanium backup and update to 5.1.1 or custom without worry

yaro666 said:
I did update a few days ago and it was ok untill it was time of the 5.1.1 update - brick, so I downloaded nexus root toolkit to get it quickly done.
Make backup using gmail or just root using nexus tool, backup with titanium backup and update to 5.1.1 or custom without worry
Click to expand...
Click to collapse
Ok so I root with the tool and then flash the 5.1.1 rom or do I have to go up in order?

Go to settings, about device, updates and install all the way up to 5.1.1, it might be a few updates. If the error shows then just use toolkit to recover nexus from soft brick and that's it

yaro666 said:
Go to settings, about device, updates and install all the way up to 5.1.1, it might be a few updates. If the error shows then just use toolkit to recover nexus from soft brick and that's it
Click to expand...
Click to collapse
Ok I used the tool and flashed the 5.1.1 stock image on it and relocked the bootloader. Now it is very laggy. Anyway to fix this?

BoDontKnowDiddley said:
Ok I used the tool and flashed the 5.1.1 stock image on it and relocked the bootloader. Now it is very laggy. Anyway to fix this?
Click to expand...
Click to collapse
The stock 5.1.1 image makes the Nexus 7 really laggy, even when running the ParrotMod fix found in another thread.
My recommendation would be to run Pure Nexus ROM by GtrCraft (links are in the Download section for ROM and GApps, which you need for Google App Store and services). Of course, use the Nexus Toolkit or TWRP as the easiest ways to flash.
Then, flash the ParrotMod fix by parrotgeek1 to help speed it up.
Once all done, it should be as fast as it will get and you won't have any updates or OTA updates to install. Pure Nexus ROM has SuperSU in it, so it will be rooted. Some apps will not work when rooted, so keep that in mind (mainly banking and some streaming apps).

PutoFace said:
The stock 5.1.1 image makes the Nexus 7 really laggy, even when running the ParrotMod fix found in another thread.
My recommendation would be to run Pure Nexus ROM by GtrCraft (links are in the Download section for ROM and GApps, which you need for Google App Store and services). Of course, use the Nexus Toolkit or TWRP as the easiest ways to flash.
Then, flash the ParrotMod fix by parrotgeek1 to help speed it up.
Once all done, it should be as fast as it will get and you won't have any updates or OTA updates to install. Pure Nexus ROM has SuperSU in it, so it will be rooted. Some apps will not work when rooted, so keep that in mind (mainly banking and some streaming apps).
Click to expand...
Click to collapse
Well I would rather not have it rooted if I can help it. I don't want my niece getting into anything a messing it up. I have read that the marshmallow pure aosp is much smoother or was that what you were talking about? Can I flash that with the nexus tool? I want to keep everything buttoned up for her.

You can use tool to flash recovery TWRP, then boot recovery copy rom aosp or slim or whatever you like, flash it and you're good to go. It'll take up to 15min.
Just read rom description and follow install instruction

yaro666 said:
You can use tool to flash recovery TWRP, then boot recovery copy rom aosp or slim or whatever you like, flash it and you're good to go. It'll take up to 15min.
Just read rom description and follow install instruction
Click to expand...
Click to collapse
Sorry for my ignorance but if I use the aosp rom I would have to keep it rooted or no? When I updated to 5.1.1 I just unlocked the BL and then flashed 5.1.1 and then relocked it. Should I have installed a recovery? I didn't think I should since I didn't want to keep it rooted.

BoDontKnowDiddley said:
Well I would rather not have it rooted if I can help it. I don't want my niece getting into anything a messing it up. I have read that the marshmallow pure aosp is much smoother or was that what you were talking about? Can I flash that with the nexus tool? I want to keep everything buttoned up for her.
Click to expand...
Click to collapse
There really isn't anything to mess up when the tablet is rooted. It mainly just gives you access to more settings and more customization.
If you are dead-set on using a non-rooted ROM, you could also use CyanogenMod, which is updated regularly.