[Q] Rooted Nexus 4 Can Get Android 4.3 Updates ? - Nexus 4 Q&A, Help & Troubleshooting

Hi There,
I have rooted my Nexus 4 Few Days ago and Still I didn't got my Android 4.3 Update. I want to know after rooting is my device getting automatically update or do I need to install it manually after downloading image from Google ?
Thanks

http://forum.xda-developers.com/showthread.php?t=2378413
Sent from my Nexus 4 using Tapatalk 4 Beta

konfidential said:
http://forum.xda-developers.com/showthread.php?t=2378413
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I know I can install it manually. I need to know whether I will get Automatic Push Up Update or Not

You're rooted... So no
Sent from my Nexus 4 using Tapatalk 4 Beta

konfidential said:
You're rooted... So no
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks Buddy.So after I Installed Image from Google Developers is it unroot again ?

Yes.. You'll lose root
Sent from my Nexus 4 using Tapatalk 4 Beta

konfidential said:
You're rooted... So no
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Actually, if your device is rooted but still running stock, you can still receive OTA updates.
AnjulaMalshan said:
Thanks Buddy.So after I Installed Image from Google Developers is it unroot again ?
Click to expand...
Click to collapse
Yes, you'll need to re-root your device.
Sent from my Nexus 4

Hi,
My Nexus 4 is rooted running stock, but with the faux kernel. Will I still get 4.3 pushed to my phone?
Either way once I install 4.3, will I have to unlock the bootloader again in order to root the phone?
Thanks, I'm new to all this business

Theonew said:
Actually, if your device is rooted but still running stock, you can still receive OTA updates.
Yes, you'll need to re-root your device.
Sent from my Nexus 4
Click to expand...
Click to collapse
I received update notification, my Nexus 4 is rooted and running stock. So if I update would I lose root? and when I root again would I lose my data unless I backup and restore it later?
Thank you.

kannaiah said:
I received update notification, my Nexus 4 is rooted and running stock. So if I update would I lose root? and when I root again would I lose my data unless I backup and restore it later?
Thank you.
Click to expand...
Click to collapse
You will lose root. once you re-root it you will not lose any data. just to be safe create a backup before upgrading to 4.3

I received my Nexus 4 on March 2 2013.
It was running Jelly Bean 4.2 out of the box but, soon after I connected to my wifi, the phone automatically downloaded 4.2.2 and was ready to install. I upgraded to 4.2.2 without making any modifications or added any apps to the phone.
I then rooted my phone using Nexus Root Toolkit v1.6.3 by Wug. It used SuperSU and BusyBox Free, and installed the TWRP custom recovery.
A week later I installed the faux123 kernel. I have not installed any custom ROM at all.
On July 31 2013 I noticed the 4.3 update had been automatically downloaded and ready to install (there was a persistent notification in the status bar as well as a "Restart & Install" message in About phone -> System updates).
Just now (yes I know it has been a week but I had been rather busy so I did my backups in parts) I tried to install the 4.3 update. After the restart I was dumped into TWRP's recovery screen. Not knowing what to do I chose Reboot -> System. The phone started up as normal, but once the boot has completed, I found that I am still on 4.2.2, still rooted, and still running the faux123 kernel. But now - even after reboots and rechecks - About phone -> System updates tells me that "Your system is up to date"!?!?
STRANGE...

xdakewie said:
I received my Nexus 4 on March 2 2013.
It was running Jelly Bean 4.2 out of the box but, soon after I connected to my wifi, the phone automatically downloaded 4.2.2 and was ready to install. I upgraded to 4.2.2 without making any modifications or added any apps to the phone.
I then rooted my phone using Nexus Root Toolkit v1.6.3 by Wug. It used SuperSU and BusyBox Free, and installed the TWRP custom recovery.
A week later I installed the faux123 kernel. I have not installed any custom ROM at all.
On July 31 2013 I noticed the 4.3 update had been automatically downloaded and ready to install (there was a persistent notification in the status bar as well as a "Restart & Install" message in About phone -> System updates).
Just now (yes I know it has been a week but I had been rather busy so I did my backups in parts) I tried to install the 4.3 update. After the restart I was dumped into TWRP's recovery screen. Not knowing what to do I chose Reboot -> System. The phone started up as normal, but once the boot has completed, I found that I am still on 4.2.2, still rooted, and still running the faux123 kernel. But now - even after reboots and rechecks - About phone -> System updates tells me that "Your system is up to date"!?!?
STRANGE...
Click to expand...
Click to collapse
I also get the same thing. I rooted my official jellybean 4.2.2 to with nexus 4 tool kit. I have teamwin recovery mode . I get on my phn there is an update 4.3 when i press restart and install its restarting to teamwin recovery mode and nothings updated when i boot back to system still get 4.2.2 ver. How do I update the official firmware?

crashzonecz said:
I also get the same thing. I rooted my official jellybean 4.2.2 to with nexus 4 tool kit. I have teamwin recovery mode . I get on my phn there is an update 4.3 when i press restart and install its restarting to teamwin recovery mode and nothings updated when i boot back to system still get 4.2.2 ver. How do I update the official firmware?
Click to expand...
Click to collapse
hi there!
after 3-4 days of telling me my "system is up to date", i got another auto-download and prompt to update yesterday. this time i tried to look for the downloaded update file on my emulated SD card when in TWRP but i couldn't find it; so i chose Restart->System like i did before and again (naturally) nothing was updated (and thank goodness at least nothing broke as far as i could see).
from what i've read i believe we will all get such OTA update notices. however, to successfully update using the downloaded file, we would need our phones to be in stock condition (no root, no custom ROM or kernel, etc.). now this 4.3 update as compared to 4.2.2 isn't all that appealing to me, so i think i will wait for a few months to see there are no bugs before attempting to update again.
if you would like to update now, i suggest you read this thread http://forum.xda-developers.com/showthread.php?t=2390127 in which a member advised on using TWRP to handle the updating and not having to re-root your phone after that. hope it helps, and good luck to you!

just do it manually! It's soo simple..
follow these great instructions:
http://forum.xda-developers.com/showthread.php?t=2145848
Look out with flashing userdata userdata.img, dependent on the instructions you choose you have to remove/skip this one because it will erase all your data!
If you want root, install the latest SuperSU 1.5 after you're done.
I also would make a nandroid (full backup) with CWM/TWRP before you start.. if something goes wrong you can always revert all steps.

Related

[Q] Problem with OTA 4.3

Hey guys, got a problem here.
My nexus 4 is rooted running team win recovery. running 4.2.2
just got the notification about OTA update 4.3, really excited about it and clicked install.
phone rebooted, went to teamwin, and it looked to me trying to flash something. left it there and suddenly when back to the team win recovery home page. clicked reboot to system and don't know why i'm still in 4.2.2. checked for updates but says system is up to date.
can anyone help me with the solution?
thanks a lot
You need the stock recovery, as said in a thousand other threads. If u want 4.3 flash the system image and re-root
Sent from my Nexus 4 using xda premium
EddyOS said:
You need the stock recovery, as said in a thousand other threads. If u want 4.3 flash the system image and re-root
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Or he could just get any 4.3 ROM and flash it through TWRP.
Sent from my Nexus 4 using xda app-developers app
Aaaaand i am still waiting for my update :/
My two friends with Samsung GNex got the Update, but ME with the Latest Nexus 4 still using 4.2.2 and on stock how beautiful the feeling is haha
Thibaultvw said:
Or he could just get any 4.3 ROM and flash it through TWRP.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Or CWM
If you want it that bad. Just download the factory image from Google devs and flash it.
Then you also have stock ROM running.
Send from my Nexus 4
EddyOS said:
Or CWM
Click to expand...
Click to collapse
He uses TWRP.
Sent from my Nexus 4 using xda app-developers app
Is there any way to revert back to stock recovery in order to get the update?
Further more, is there an option to do so without re-flashing stock all together?
wizardwiz said:
Is there any way to revert back to stock recovery in order to get the update?
Further more, is there an option to do so without re-flashing stock all together?
Click to expand...
Click to collapse
You can extract the stock recovery from the factory image and flash through fastboot.
Hit thanks if I helped.
Sent from my Nexus 4 using xda app-developers app
You can get the stock 4.2.2 recovery from the 4.2.2 factory image. I did have it but as I only keep the current factory image I only have the 4.3 recovery to hand
EddyOS said:
You can get the stock 4.2.2 recovery from the 4.2.2 factory image. I did have it but as I only keep the current factory image I only have the 4.3 recovery to hand
Click to expand...
Click to collapse
OK, did some further investigations and here are my findings
1. If you have it, you can use Wugfresh's toolkit (V1.6.4 for now) and it has a utility that can simply restore stock recovery and if you want it, stock kernel as well.
2. The Toolkit will download all necessary files and prompted you before each step.
3. It will revert back permissions for the stock recovery as well
I'll give it a try later on at home.
Thanks guys
Ziv
I am a bit confused. According to the “Nexus OTA Help-Desk” thread, the way to do this is as follows:
Scenario #2
You are stock, with root. Custom Recovery without any modifications or deletions.
Continue to Section B
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
4) Flash Su.zip: (SU is being updated often so check Chainfire's G+ for the latest) https://plus.google.com/+Chainfire/posts
NOTE: Root on 4.3 is not stable. Your mileage may vary.
5) Reboot
So, what is different about using this method to install the OTA and just running the OTA from the notification, and is this the incorrect method?
Is returning to the stock recovery the preferred and more or less foolproof method?
I'm not sure why there's people saying otherwise, but from my experience you don't need stock recovery to take on an OTA...
I've updated my N7 several times now from when I first bought it to 4.3 currently, all the time with a custom recovery. Unless you've changed some other files which causes an error during the OTA update, I don't believe there is a need to re-flash stock recovery at all.
@mlj11, lots of people have the OTA failing on them, even if they are on rooted factory image 4.2.2.
Why the OTA fails on rooted 4.2.2 is still unclear.
My N4 with rooted factory image 4.2.2 also updated like it should without error.
Maybe the unlocked bootloader is the issue letting the 4.3 OTA fail.
Send from my Nexus 4
@DecypherT
I'm not saying that rooted users will have no problems updating. My post was in response to people on this thread saying that a custom recovery will stop the OTA. This is false.
It can't be the unlocked bootloader (and it has never been) causing the problem otherwise you or I wouldn't have been able to take the OTA, for example. More likely it's something else.
If any of a user's system files have been altered, there's a good chance the OTA will fail. In the past that happened to me because the Stickmount app changed one of the system files. Once I replaced it though, I could update without any problems.
Ok, good points you're proving here.
Still, it looks like the (OTA) android 4.3 is very unstable.
I'm on rooted 4.3 and experience no big bugs or flaws though.
I do see a very large decrease of battery life when using the phone (screen on) and a big increase when in deep sleep. When the phone is off I almost use no battery.
Send from my Nexus 4

[Q] OTA Updates with Root

I have a stock rooted Nexus 4 running Android 4.3 (JWR66V) and a custom recovery. Recently, the JWR66Y update showed up on my phone and I turned on OTA survival mode in SuperSU and proceeded to install the update. It booted into TWRP and proceeded to install up until a certain point but then it froze. I cancelled the installation and rebooted my device and I even got the "Updating Applications" indicator on the first boot. However, I checked the version and it was still on JWR66V and my device no longer shows an update available. I did the exact same thing with my Nexus 7 (2013) with the JWR66Q update and the same thing happened. Is there any way I can install an OTA update on a rooted device? Every time an update is available for one of my devices, I end up doing a full factory reset of my device to install an update. I have only been able to find things like Clean ROM and Shiny ROM and while I do appreciate the work these developers are doing for the community, I would prefer to be able to either download a fully stock and non-deodexed flashable zip for my device or find a way to install the OTA update without losing root. It would also be great if I could do so without a computer because I currently only have a Chromebook. Thank you very much.
Are you sure it was the update to the Y version? What did the file size show as in the system update notification? There have been 2 very small (1.8mb) updates which don't change the build number, maybe that's what you installed.
I am also stock rooted and have received each system update as usual, remember they take time to roll out world wide.
Sent from my Nexus 4 using Tapatalk 2
Nathanation said:
Are you sure it was the update to the Y version? What did the file size show as in the system update notification? There have been 2 very small (1.8mb) updates which don't change the build number, maybe that's what you installed.
I am also stock rooted and have received each system update as usual, remember they take time to roll out world wide.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Now that you mention it, I'm actually not sure. However the update didn't complete either way. It froze on a step involving the boot.img (sorry I can't remember exactly what it was doing). I don't really need a fix for it anymore as I have already manually installed the updates using a friends computer but I only know how to do so by flashing the factory image and losing all of my data along the way. But just so I know for future updates, do you use OTA Survival mode or OTA Rootkeeper or anything like that or do you simply install the update as you would on a non-rooted device? Thanks for your reply.
KeanuKe said:
Now that you mention it, I'm actually not sure. However the update didn't complete either way. It froze on a step involving the boot.img (sorry I can't remember exactly what it was doing). I don't really need a fix for it anymore as I have already manually installed the updates using a friends computer but I only know how to do so by flashing the factory image and losing all of my data along the way. But just so I know for future updates, do you use OTA Survival mode or OTA Rootkeeper or anything like that or do you simply install the update as you would on a non-rooted device? Thanks for your reply.
Click to expand...
Click to collapse
The root isn't the problem. The custom recovery is. You need to be on stock recovery for the update.
xda6969 said:
The root isn't the problem. The custom recovery is. You need to be on stock recovery for the update.
Click to expand...
Click to collapse
Can I fastboot flash the stock recovery after I've already flashed a custom recovery and still have root? And if the answer to that is "yes" will I still be rooted after the next OTA update?
I am having the same problem. Both my nexus 4 and 7 recieved an update (1.8MB) but it seems that i cannot get the update to install. Both devices were rooted using the Nexus Root Tool kit.
When i got the update the devices booted in recovery mode with TWRP. Do not know what to do. I saw no update in the baseband or build number.
I am running stock android.
Please advise

[Q] Nexus 7 Jellybean 4.3 update

hi,
apologies if this has been asked before but my searches have not found a clear answer. i have a 2012 nexus 7 Rooted and running JB 4.2.2.
the OTA update to JB 4.3 fails everytime. it gets so far and then shows the android logo with a red triangle exclamation and just "error"
it reboots back to home screen after a minute or two.
my device was rooted using WUGS toolkit and TWRP recovery. i just did the basic rooting so i could use stickmount and have done nothing funny with the device since.
i have seen many guides about flashing 4.3 update that will wipe the device which i really want to avoid.
will it work if i just un-root and re-lock the device with the toolkit and then run the OTA update or is it more complicated than that.
Lemegeton300 said:
hi,
apologies if this has been asked before but my searches have not found a clear answer. i have a 2012 nexus 7 Rooted and running JB 4.2.2.
the OTA update to JB 4.3 fails everytime. it gets so far and then shows the android logo with a red triangle exclamation and just "error"
it reboots back to home screen after a minute or two.
my device was rooted using WUGS toolkit and TWRP recovery. i just did the basic rooting so i could use stickmount and have done nothing funny with the device since.
i have seen many guides about flashing 4.3 update that will wipe the device which i really want to avoid.
will it work if i just un-root and re-lock the device with the toolkit and then run the OTA update or is it more complicated than that.
Click to expand...
Click to collapse
Same Here!, I had TWRP recovery and I'm rooted, so Just Flashed stock recovery and I though I can update easily. But now I can't!
-By the way, I did not change any system file.
Since you have Stickmount did your error message reference a bad file check on 'debuggerd' in the /system/bin folder? It seems Stickmount may replace or alter that file and you have to put back an original for 4.2.2 to successfully flash the update with TWRP. After replacing 'debuggerd', the update flashed just fine for me. Are you sure you didn't get any text other than 'Error'? Are you sure you didn't freeze or delete any system apps?
It also happened to my nexus 4, they recommended to use this way: (It won't erase the data)
http://forum.xda-developers.com/showthread.php?t=2377307
hey, the error has no message or info. it literally says the word "error" with red exclamation and thats it. i have not touched any of the system apps or done anything that could upset the system files.
i will try the suggestion from alipashang77, thanks
sorry but those instructions are for the samsung galaxy nexus phone.
does not apply to my nexus 7 tablet.
any suggestions
Lemegeton300 said:
sorry but those instructions are for the samsung galaxy nexus phone.
does not apply to my nexus 7 tablet.
any suggestions
Click to expand...
Click to collapse
There's tonnes of older posts with all the info you'll need. Gotta just search more.
Ota will erase everything except your internal/external sd cards. Plus ota wont work if anything system wise had been altered. You'd have to Odin stock 4.2.2 then do ota.
No reason why you can't just flash a 4.3 rom like anything else tho.
And in all cases, wiping your data and apps is best. You gotta back it up. Restore after. Apps and their data anyway. Restoring system app data is never ever a good idea.
Sent from my cellular telephone
Device won't update via OTA with a custom recovery. And 4.3 OTA will fail if you're rooted. So in order to get OTA make sure you have stock recovery and unroot, then as long as you haven't modified anything system wise it should update successfully. And no, OTA updates will not wipe any data.
Sent from my Nexus 7 using xda premium
thanks everyone. its finally updated to 4.3. i backed up my data and then flashed the stock 4.3 image and that failed and the device would not boot. i thought it was bricked but it let me flash the 4.2.2. image and then the 4.3 OTA update worked.
:good::good::good::good::good:
hi guys i know that the previous reply was that flashing to the 4.2.2 worked then the OTA worked, however i have an explaination for people that were stuck like me
i JUST managed to upgrade my nexus 7 to 4.3 (JWR66Y)
i found a helpful link to upgrade from http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
after following all the steps, my i wasnt able to flash the bootloader (bootloader-grouper-4.23.img).
after doing some googling today, i found that it is the bootloader in the 4.3 update that is different (according to http://forum.xda-developers.com/showthread.php?t=2417097&page=2) and that you need the JWR66V bootloader img file (which is also the bootloader-grouper-4.23.img) they explain it in the link above, and have a download link for it there.
so in order to do the update, what you need to do is follow the steps from the 1st link (extract all the files etc in place), but before flashing, copy the bootloader from the 2nd link into your platform-tools folder, then follow the steps to flash.
as long as you follow the steps, and skip step 10, you will keep your data also
hope that helped
95Z28 said:
Device won't update via OTA with a custom recovery. And 4.3 OTA will fail if you're rooted. So in order to get OTA make sure you have stock recovery and unroot, then as long as you haven't modified anything system wise it should update successfully. And no, OTA updates will not wipe any data.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Per WugFresh's advice, if you're rooted and using stock reovery, you still can OTA update.
Link: http://www.wugfresh.com/nrt/faqs/
vndnguyen said:
Per WugFresh's advice, if you're rooted and using stock reovery, you still can OTA update.
Link: http://www.wugfresh.com/nrt/faqs/
Click to expand...
Click to collapse
Past OTAs would be successful when rooted, you would usually just lose root access. But the 4.3 OTA won't work while rooted, you'll just keep getting the failed message.
Sent from my Galaxy Nexus using xda premium
95Z28 said:
Past OTAs would be successful when rooted, you would usually just lose root access. But the 4.3 OTA won't work while rooted, you'll just keep getting the failed message.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
ok thanks. I'm on 4.3 and only root with stock recovery. So if the 4.4 available I will unroot and then OTA. Thanks!

Nexus 7 2013 Android Update 4.3 to 4.4.2

Do you have problems updating Nexus 7 from Jelly Bean to Kitkat? Well I did, since the day got my hands of N7 device, it was unlocked and rooted.
Somewhere is Sep the News of Kitkat has been rolling out. In Oct my N7 device notified on the new Kit Kat upgrade. I have been trying using OTA update but each time came to "FAILED" installation and so decided to give up the idea since JB 4.3 was working fine.
Now Kit Kat rolled out 4.4.2 version and still I had the same problem, did some researched on XDA forum and tried each of their suggestion but still did not work out. I was always stuck with "KoreanIME.apk" error on recovery, perhaps something I deleted earlier on.
Using Nexus Root Toolkit Ver 1.8
Finally decided to use the Nexus Root Toolkit (NRT). The last time used it was rooting the brand new N7. Run NRT and it started gathered information and upgraded to latest NRT ver 1.8.
With the new NRT version I decided to Flash Stock + Unroot, hoping I can do the update by going back to stock. To my surprise NRT found the latest Kitkat 4.4.2 and installed on Nexus 7. Most of the data was lost but had earlier done a backup. After which just like a brand new device, log in my account and immediately all the previous Apps started to download back to the device.
Once that was done, Root the device using NRT included Custom Recovery check, the rest just follow NRT instructions to install BusyBox and all is Done!!
Apps like Watsapp had to be installed manually since it does not support tablet version. Other data were also done manually.
I would not recommend this method unless you are prepared to wipe everything clean, so do a backup first. There were no other options and this was the only method.
Hope this helps and if anyone can point out the mistake I have done, do share for others.
OTA update doesn't work with custom recovery if I'm not mistaken
OTA can work with custom recovery, I've done it several times, though the custom recovery was overwritten by the update.
Sent from my SGH-I747M using xda app-developers app
Yes, OTA in the form of .zip file can be flashed via custom recovery.
But it seems that OP's problem occurs when he's trying to update from official OTA notification, from my understanding if you try to update from official OTA notification with custom recovery installed it will fail.
Please correct me if I'm wrong since mine was done through adb sideload
I did it through the official OTA (not a zip file) with a custom recovery. There seems to be a myth out there that it's not possible, but I can say from experience that it is possible.
Sent from my SGH-I747M using xda app-developers app
clienttrace said:
Yes, OTA in the form of .zip file can be flashed via custom recovery.
But it seems that OP's problem occurs when he's trying to update from official OTA notification, from my understanding if you try to update from official OTA notification with custom recovery installed it will fail.
Please correct me if I'm wrong since mine was done through adb sideload
Click to expand...
Click to collapse
Just for clarification, besides using auto OTA update, I did tried it manually using razor and SuperSu zip files. Also as you mentioned ADB sideload. It did not work out.
Somehow using NRT was much easier, just sit back and let NRT do all the job. The only setback were the missing data. Not a big issue, anyway was nice to see the file structure cleaned up.
gc84245 said:
I did it through the official OTA (not a zip file) with a custom recovery. There seems to be a myth out there that it's not possible, but I can say from experience that it is possible.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
thanks, that's clear it up for me

[Q] No Lollipop OTA

Hi all
By now, I would assume that Google has finished the rollout of the lollipop OTA for the Nexus 4 (mako)
but I have a problem
Short Story
I still don't have lollipop OTA because Google thinks I'm rooted
Long Story
My brand new Nexus 4 (arrived 3 days ago) came with 4.2.2
I opened the box and immediately unlocked the bootloader (fastboot oem unlock) and then installed twrp (fastboot flash recovery openrecovery............img)
After that, I went into twrp to check if it was flashed correctly, and it worked fine BUT as I was about to reboot, twrp asked if i wanted to install SuperSU and I accidentally pressed "yes".
after the phone booted, I found it wasn't acually rooted but it installed an app called "SuperSU Installer"
I ignored it, and went through 4 ota updates (from 4.2.2 to 4.4.2) and the otas stopped (there was not updates available after 4.4.2)
After the updates, I found that the ota have removed twrp and was overwritten by stock recovery SO I went back to bootloader and flashed twrp again (which worked just fine).
Then I done some seaching on Google and found that I'm not getting lollipop becasue I have some traces of rooting (the "SuperSu Installer" that somehow managed to survive 4 OTA's)
I went no to flash the full root (the actual SuperSu) and then do a "Full Unroot" from there (worked fine) and the phone is now unrooted.
BUT still not Lollipop OTA
I gave up and tried to do the update manually (Downloaded flashalbe ZIP from Android Police) but TWRP refuses to flash it
The question is, what to do now?
http://forum.xda-developers.com/showthread.php?t=2807446
Don't wait for Google. I have been running L for months now.
Sent from my Nexus 4 using Tapatalk
AgEnT x19 said:
Hi all
By now, I would assume that Google has finished the rollout of the lollipop OTA for the Nexus 4 (mako)
but I have a problem
Short Story
I still don't have lollipop OTA because Google thinks I'm rooted
Long Story
My brand new Nexus 4 (arrived 3 days ago) came with 4.2.2
I opened the box and immediately unlocked the bootloader (fastboot oem unlock) and then installed twrp (fastboot flash recovery openrecovery............img)
After that, I went into twrp to check if it was flashed correctly, and it worked fine BUT as I was about to reboot, twrp asked if i wanted to install SuperSU and I accidentally pressed "yes".
after the phone booted, I found it wasn't acually rooted but it installed an app called "SuperSU Installer"
I ignored it, and went through 4 ota updates (from 4.2.2 to 4.4.2) and the otas stopped (there was not updates available after 4.4.2)
After the updates, I found that the ota have removed twrp and was overwritten by stock recovery SO I went back to bootloader and flashed twrp again (which worked just fine).
Then I done some seaching on Google and found that I'm not getting lollipop becasue I have some traces of rooting (the "SuperSu Installer" that somehow managed to survive 4 OTA's)
I went no to flash the full root (the actual SuperSu) and then do a "Full Unroot" from there (worked fine) and the phone is now unrooted.
BUT still not Lollipop OTA
I gave up and tried to do the update manually (Downloaded flashalbe ZIP from Android Police) but TWRP refuses to flash it
The question is, what to do now?
Click to expand...
Click to collapse
A couple of things, you'll get the ota if your rooted, it just won't flash. The other is you can't flash the ota update zip in twrp. You need to sideload it in the stock recovery. You have to 100% stock and not rooted for it to flash. Otherwise it will fail
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
A couple of things, you'll get the ota if your rooted, it just won't flash. The other is you can't flash the ota update zip in twrp. You need to sideload it in the stock recovery. You have to 100% stock and not rooted for it to flash. Otherwise it will fail
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your reply
I think I will wipe everything and install factory image since I didn't install anything on it yet
I assume it will make the phone 100% stock (just like it was in its box)
right?
AgEnT x19 said:
Thanks for your reply
I think I will wipe everything and install factory image since I didn't install anything on it yet
I assume it will make the phone 100% stock (just like it was in its box)
right?
Click to expand...
Click to collapse
Yep. Just flash the 5.0.1 factory image. You should be able to use the flash-all.bat in the factory image. It will wipe your device but since you haven't set anything up that shouldn't be a problem
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Yep. Just flash the 5.0.1 factory image. You should be able to use the flash-all.bat in the factory image. It will wipe your device but since you haven't set anything up that shouldn't be a problem
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
you mean flash-all.sh
I mainly use Linux
Anyway, thanks for your help
AgEnT x19 said:
you mean flash-all.sh
I mainly use Linux
Anyway, thanks for your help
Click to expand...
Click to collapse
That'll work too
Sent from my Nexus 9 using XDA Free mobile app
So I just got my mako few days ago....came with JB stock immediately updated to kk but nothing since. Its been 6 days without a notification for lp. Any ideas besides flashing factory.IMG and I tried the play services trick also.
aaronrw said:
So I just got my mako few days ago....came with JB stock immediately updated to kk but nothing since. Its been 6 days without a notification for lp. Any ideas besides flashing factory.IMG and I tried the play services trick also.
Click to expand...
Click to collapse
You have two choices
1. Wait for the OTA (you will eventually get lollipop)
2. Update manually by following this great guide
http://www.reddit.com/r/Android/comments/2mgh8o/nexus_4_lollipop_ota_link_and_update_guide/
Note: The above method is exactly like updating from Setting>About Phone>System Updates (i.e. All your apps, data, files....etc will be kept)
BUT is different from flashing factory image (which completely wipes the phone making it just like it was in its box)

Categories

Resources