Develop Bugs

[Q] 4.04 update will not install on rooted Galaxy nexus help

So I am running the stock rom but have root access. the update pops up every 5 minutes to remind me to install it. I let it install and about 3 second in i get a yeild sign with an exclamation point in it. and the phone stops there. I waited for about 3 hours and nothing happened. Anybody know what I need to do here? I used Galaxy Nexus root toolkit v1.3 to root my phone. BTW i am with verizon

For as far as i now you cant update a rooted device. i sugest unrooting an try to update agian.

reply
yea that's what I thought I was going to have to do. but wanted to see if there was an update package someone had made for rooted devices like some others had.

nvm i think im going to trade the phone

So no one has an answer on this?

jordi97 said:
For as far as i now you cant update a rooted device. i sugest unrooting an try to update agian.
Click to expand...
Click to collapse
Yes you can. You can't update a phone with CWM recovery though.
Sent from my Galaxy Nexus using xda premium

Correct a rooted phone can update but not with any custom recovery. You need to flash back to the factory stock recovery.
Sent from a phone...

OK so looks like everyone is here was incorrect. The 4.04 rooted update is here in the XDA forums all i needed to do was flash it and the new antenna and everything is working fine now. here are the links.
4.04 http://forum.xda-developers.com/showthread.php?t=1631796
radio http://forum.xda-developers.com/showthread.php?t=1630438
Thank you Brandon for helping me out with this.
There are no stupid questions only stupid answers.

Sdalton19 said:
OK so looks like everyone is here was incorrect. The 4.04 rooted update is here in the XDA forums all i needed to do was flash it and the new antenna and everything is working fine now. here are the links.
4.04 http://forum.xda-developers.com/showthread.php?t=1631796
radio http://forum.xda-developers.com/showthread.php?t=1630438
Thank you Brandon for helping me out with this.
There are no stupid questions only stupid answers.
Click to expand...
Click to collapse
Your right, stupid answers, that's not an ota update you did. That was pulled from a phone which was updated and packaged into a flashable file to use on a rooted device. But a carrier ota update as your device was asking you to update will not work without stock recovery.
Sent from a phone...

Isn't that exactly what i asked for second post in? Point is if you knew that, why didn't you say so? Look there's nothing wrong with being wrong every once in a while but be graceful about it. And if your going to give advice make sure you fully read the question and offer decent advice. You were saying there was no way to update it without unrooting and flashing back to stock. That was after I asked "yea that's what I thought I was going to have to do. but wanted to see if there was an update package someone had made for rooted devices like some others had." Is that not exactly what I asked for????

Sdalton19 said:
Isn't that exactly what i asked for second post in? Point is if you knew that, why didn't you say so? Look there's nothing wrong with being wrong every once in a while but be graceful about it. And if your going to give advice make sure you fully read the question and offer decent advice. You were saying there was no way to update it without unrooting and flashing back to stock. That was after I asked "yea that's what I thought I was going to have to do. but wanted to see if there was an update package someone had made for rooted devices like some others had." Is that not exactly what I asked for????
Click to expand...
Click to collapse
Well, you are right that there are a lot of partially right and partially wrong answers in this thread. But what are you saying is not exactly right either.
1) There is a difference between updating your existing build (like what you had asked to do in the first post) and flashing an entirely new build.
2) There is a difference between running a stock ROM (like what you were running before) and running a ROM that looks like it's stock, but is not (like what you are running now).
3) Root has NO impact whatsoever on your ability to install OTA updates on your stock ROM.
4) An OTA update will NOT install with a stock recovery UNLESS you are using the stock recovery version that came with the build you are using. (It seems like a lot of toolkits are flashing non-matching stock recoveries).
5) An OTA update file can EASILY be installed if you have CWM installed. See here.
6) Your phrase "unrooting and flashing back to stock" is silly, as flashing back to stock replaces your ROM, so why would you need to "unroot" your current ROM only to flash a stock ROM overtop? You don't root a device - you root an Android OS build. The phrase "root my device" does not make any sense.

[question] OTA QUESTION??

I am currently using N7 FHD (2013) with JWR66N 4.3 jellybean. I have just UNLOCKED BOOTLOADER but NOT ROOT or install any RECOVERY.
ALL ARE STOCK ROM, STOCK RECOVERY JUST BOOTLOADER UNLOCKED.
After that I got a CLEAN (Wiped) nexus. and I got a 5X MB OTA from google and I reboot. but after that, the android robot lied down and showing a RED ! icon and "ERROR".
I rebooted my device, it starts up normally.
IS THAT I CANNOT USE OTA AFTER UNLOCKED THE BOOTLOADER????
WHAT IS THE CURRENT NEWEST BUILD NUMBER FOR NEXIS 7 2013 FHD 32GB??
how can I get that OTA again???

If you really didn't modify or remove any of the stock files, then you are probably suffering from the JWR66N won't update to JSS15J problem mystery we are trying to figure out here:
http://forum.xda-developers.com/showthread.php?t=2380258
We know that it is caused by a file on your tablet being different than what is expected and we know how to workaround the problem. We just don't know why it is happening in the first place.
If you want to help solve the mystery, post on that thread.
If you just want to get JSS15J it may be quicker to just use the JSS15J factory restore here:
http://developers.google.com/android/nexus/images#razor
(factory restore will wipe your data so back up first)

Thanks for your info.
I think i can re unlock my bootloader again.
I am afraid that BL unlocked cant enjoy OTA and now i understand thats the OTA file error from google and not mine.
But google is still so stupid that they cant reconize my OLD (non full HD 2012) nexus and new 2013 nexus. They both have same names in google play store. Thats weird
Sent from my Nexus 4 using xda app-developers app

I think you understood properly, but I didn't answer your question directly, so to be clear, the OTA, under normal circumstances, would work fine on a tablet with unlocked bootloader (unless files were modified or removed)
What we are trying to figure out is why for some tablets there is a rare occurrence of a file not matching the shipped set of files that everyone else has. It is usually just one file, /system/app/PrebuiltGmsCore.apk, but there was one example of someone having the same issue with /system/lib/libchromeview.so

Nexus 7 4.3 JWR66N OTA update error

My NEXUS 7 (2013) is running on Android 4.3 with the build version JWR66N
The Problem is that i get an OTA update notification for Android 4,3 System Update which is of appx (56 MB).
When i try to install it the Tab reboots and the update fails and it restarts again with the same build version ie. JWR66N.
Again after 2-3 days i get the same notification for that 4.3 System update and again it fails. PLEASE HELP !!!
How will i update to android 4.4 ???
I dont want to sideload or root.... Please suggest a normal fix !!!

Have you done any modifications to your n7 usually that borks any ota update

church said:
Have you done any modifications to your n7 usually that borks any ota update
Click to expand...
Click to collapse
No... I have not done any change.... After booting for the very first time i got an update which worked fine.... Then this OTA update message keeps coming but it never gets installed as it gives an error

red_ferrari007 said:
My NEXUS 7 (2013) is running on Android 4.3 with the build version JWR66N
The Problem is that i get an OTA update notification for Android 4,3 System Update which is of appx (56 MB).
When i try to install it the Tab reboots and the update fails and it restarts again with the same build version ie. JWR66N.
Again after 2-3 days i get the same notification for that 4.3 System update and again it fails. PLEASE HELP !!!
How will i update to android 4.4 ???
I dont want to sideload or root.... Please suggest a normal fix !!!
Click to expand...
Click to collapse
You likely have the problem that some system files got corrupted because of bad EMMC.
When the update fails and you have the fallen android, press/hold Power, then press/release VolUp, then release Power.
This will show you the error and can confirm or refute this diagnosis.
If you want to get past it in the more efficient manner, you'll probably need to unlock the bootloader, then flash one of the factory images.

I will see that when the OTA notification comes again..... But how can I solve the problem.... is anyone else facing it ?
Will I get an Android 4.4 update ?
Sent from my Nexus 7 using xda app-developers app

red_ferrari007 said:
I will see that when the OTA notification comes again..... But how can I solve the problem.... is anyone else facing it ?
Will I get an Android 4.4 update ?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
As I mentioned you'll probably need to flash a factory image to get around it, or you'll have to identify each file that is corrupted and replace it.
If you don't resolve the problem you won't get the 4.4 update automatically, but you can manually install the 4.4 factory image.

sfhub said:
As I mentioned you'll probably need to flash a factory image to get around it, or you'll have to identify each file that is corrupted and replace it.
If you don't resolve the problem you won't get the 4.4 update automatically, but you can manually install the 4.4 factory image.
Click to expand...
Click to collapse
see i found this link which apparently is talking about the same problem and a fix
http://forum.xda-developers.com/showthread.php?t=2380258
but i dont know anything about rooting and flashing.... Thats why i am afraid to do anything

red_ferrari007 said:
see i found this link which apparently is talking about the same problem and a fix
http://forum.xda-developers.com/showthread.php?t=2380258
but i dont know anything about rooting and flashing.... Thats why i am afraid to do anything
Click to expand...
Click to collapse
I and the op posted extensively in that thread. All the solutions there require unlocking your bootloader. If you are going to do that you might as well just flash the factory image.

Ya see that's what the problem is I don't know what's unlocking boot loader and flashing stock ram etc
Sent from my Nexus 7 using xda app-developers app

sfhub said:
I and the op posted extensively in that thread. All the solutions there require unlocking your bootloader. If you are going to do that you might as well just flash the factory image.
Click to expand...
Click to collapse
So if i flash STOCK ROM of a next version would everything be fine ???
I found this video which shows the tutorial
Is it correct ?
http://www.youtube.com/watch?v=bsss9e71bKo&feature=youtube_gdata

red_ferrari007 said:
So if i flash STOCK ROM of a next version would everything be fine ???
I found this video which shows the tutorial
Is it correct ?
http://www.youtube.com/watch?v=bsss9e71bKo&feature=youtube_gdata
Click to expand...
Click to collapse
Person on the other thread mentioned they got a JWR66N->KRT16S OTA update.
Previously we had only seen JSS15R->KRT16S updates, which would mean you would need to get from JWR66N->JSS15R first. The JWR66N->JSS15R update would fail for you, but there is a chance a JWR66N->KRT16S update would work because more files are shipped whole and not as patches.
Regarding the youtube video, it should get your where you need to be. I would skip the relocking of your device though to keep future flexibility in case something like this happens again.
If you want to be on KRT16S(4.4), then just flash the KRT16S factory image. If you want to be on the latest 4.3 then flash JSS15R.
Keep in mind unlocking the bootloader will erase your use data (including your virtual sdcard) so backup anything important and move it off the tablet to your PC or the cloud.

GOT 4.4 UPDATE...Facing Problems
Today Morning I Finally Got Android 4.4 Update OTA. I installed it..... Installation went smooth...
The Tablet Workded fine for 5-6 Hours.... Now I am getting all types of touch screen issues...
1)Non Responsive
2)Ghost Touch
3)Lagging
Please Help

sfhub said:
Person on the other thread mentioned they got a JWR66N->KRT16S OTA update.
Previously we had only seen JSS15R->KRT16S updates, which would mean you would need to get from JWR66N->JSS15R first. The JWR66N->JSS15R update would fail for you, but there is a chance a JWR66N->KRT16S update would work because more files are shipped whole and not as patches.
Regarding the youtube video, it should get your where you need to be. I would skip the relocking of your device though to keep future flexibility in case something like this happens again.
If you want to be on KRT16S(4.4), then just flash the KRT16S factory image. If you want to be on the latest 4.3 then flash JSS15R.
Keep in mind unlocking the bootloader will erase your use data (including your virtual sdcard) so backup anything important and move it off the tablet to your PC or the cloud.
Click to expand...
Click to collapse
Hi, i was that guy on the other thread,i was wondering why i receive different size of ota of kit kat 253.1mb...others almost receiving 242.5 here on our forum of nexus 7.2 philippines wifi version,just wondring why different file size?
Sent from my Nexus 7 using xda premium

Touchsreen Dead
and2nckiko said:
Hi, i was that guy on the other thread,i was wondering why i receive different size of ota of kit kat 253.1mb...others almost receiving 242.5 here on our forum of nexus 7.2 philippines wifi version,just wondring why different file size?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
SOMETHING HAS GONE HORRIBLY WRONG MAN !!!!
My Entire Screen is dead !!! I mean the TAB is Working but My screen is Not Responding !!!! I am Screwed !!!!!
How Can I chat with u contact u ?

Which of these two possibilities is better for installing updates on a rooted phone?

Hello. I'm coming from a old windows mobile phone and just got my first Android device "Samsung Galaxy S4 mini GT-i9195" and obviously i'm loving it.
Still being a newbie to Android i already did a bit of advanced stuff (at least for a novice android user) like installing CWM Recovery and rooting the phone in order to be able to install apps on and external SD card.
But a new question arose: What about new Android updates, can i still install them without loosing root or even worse, damaging the phone?
After searching a bit on google i came up with two possible and contraditory possibilities which are:
-Yes, and afterwards i would only need to restart the phone in CWM mode and reapply the zip root file i used previously;
-No, it will likely mess the phone and i should wait 1 or 2 weeks for a updated rooted rom and "install" that instead.
So, i'm a bit confused here, what would be more advisable?

I suggest to make a nandroid backup, then try a custom rom from the dev forum.
There are 4.4.4 kikat roms for our beloved S4 mini, and i dont think samsung will go further.
Envoyé de mon GT-I9190

rick6 said:
-Yes, and afterwards i would only need to restart the phone in CWM mode and reapply the zip root file i used previously;
Click to expand...
Click to collapse
...... if, as has been said, you ever get an update. An update certainly will not damage the phone.
You certainly won't have to wait for anything. I agree with zlaz, flash a new ROM such as Carbon - you get regular updates and great support here on XDA (whichever ROM you try).

Custom ROMs like CarbonRom (see the development section) is the way to go for this phone I would say. But if you wanna stay on stock and if we would get an update, Samsung probably wont let you install it via the usual OTA or Kies method, because your device is flagged as "Modified" after flashing a custom recovery (you can see this in the about this device section in the settings). You would still be able to flash the update manually with Odin, but you will then probably have to reroot it.

LanderN said:
Custom ROMs like CarbonRom (see the development section) is the way to go for this phone I would say. But if you wanna stay on stock and if we would get an update, Samsung probably wont let you install it via the usual OTA or Kies method, because your device is flagged as "Modified" after flashing a custom recovery (you can see this in the about this device section in the settings). You would still be able to flash the update manually with Odin, but you will then probably have to reroot it.
Click to expand...
Click to collapse
That's 100% true, I don't remember now exactly when your phone say, that it is modified and you can't update - moment you search for update in it or moment you try to download update that it has find.
Samsung oryginal software is not that greate anyways

Thank you all for the replies.
I think i got what i wanted with your awnsers, i just need to dig a bit more about the avaiable roms what what i can get from them. At the moment i'll keep my s4 mini as it is for a while longer i guess.
As for warranty i get something while booting up saying "Set warranty Bit: Kernel", but that seems to be what you normaly get when root a stock rom.

New Nexus Owner Seeking Advice

Hi folks! Just received a 2013 Nexus 7 from my fiancé as a birthday gift. I wanted it for quite specific purposes so was hoping I could ask a few questions here and get pointed in the right direction before I start using this thing
I intend to mainly use the tablet for remote play with my PS4 and emulating old console games. Since I want to connect a PS4 controller to it wirelessly I'm told I need to root the device. I'm guessing this is an easy process and there are some guides on the site here?
The main thing I was after advice about is firmware updates. The system came on 4.3 and has already downloaded an update for 4.4.2 but I haven't installed that yet. Is this firmware fine to upgrade to? Any performance issues? I've heard people saying that upgrading their Nexus to 5+ (Lollipop?) has created a load of performance issues and this should be avoided? Also, if I upgrade to a certain firmware version can I lock myself out of being able to root the device? I'm pretty sure all of the apps I was planning on using work no 4.3 so I have no reason to upgrade at all but if I can go safely to a higher firmware that is reliable with no performance issues I may as well?
First time using an Android device so sorry if my questions come off as a little stupid. Also, wasn't sure if I should post this here or if it should be on the Q&A board so sorry if I've got that wrong!

As far as I know, the problems with lollipop were the standard number of complaints that come with any new release. Well, I'm not really positive, but lollipop seems fine to me and I think most people have upgraded by now. I would go for it because I think it's really fun to use.... Plus you can always revert if you choose.
As far as rooting, you never need to worry about not being able to do it... Rooting your Nexus 7 will always be easy. The by-hand method is fun and relatively simple, or you can just use the toolkit in the forum to do it even easier.

^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip

Personally, I'd stick go for 4.4.4, as 5, 5.0.1 & 5.0.2 all have a memory leak issue. You may also find more emulator compatability as Kit Kat has been around a year longer than Lollipop. The only downside to KK over L is the battery life is a little worse IMO.
I dont think the memory leak issue is a result of someone not knowing what they are doing etc.

Thanks for all the advice everyone
yosmokinman said:
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Click to expand...
Click to collapse
I'm fairly competent with computers (as I should be with a degree in computer science!) but this is all like a foreign language to me. I guess I'm better sticking with the toolkit for now until I'm familiar with all the lingo?
Masteryates said:
Personally, I'd stick go for 4.4.4, as 5, 5.0.1 & 5.0.2 all have a memory leak issue. You may also find more emulator compatability as Kit Kat has been around a year longer than Lollipop. The only downside to KK over L is the battery life is a little worse IMO.
I dont think the memory leak issue is a result of someone not knowing what they are doing etc.
Click to expand...
Click to collapse
Thanks. This is the sort of advice I was after and is why I mentioned what I was planning on using it for. The device has already downloaded 4.4.2 and wants to update to that. Is there a way I can manually go to 4.4.4? I'm worried it will just request an update from the Google server and try to jump straight to a version of 5

chunk3rvd said:
Thanks. This is the sort of advice I was after and is why I mentioned what I was planning on using it for. The device has already downloaded 4.4.2 and wants to update to that. Is there a way I can manually go to 4.4.4? I'm worried it will just request an update from the Google server and try to jump straight to a version of 5
Click to expand...
Click to collapse
If you unlock the bootloader then familiarise yourself with ADB and flashing factory images, you can manually flash any version of Android (That has been availible for your device,) manually. You dont need to be rooted to do this.
It also allows you to go back when you've made the mistake of updating, (but does wipe all of your data!)

It ended up offering me the updates incrementally anyway. I went from 4.3 > 4.4.2 > 4.4.3 > 4.4.4 which I'm currently on and will leave it there for now. It's downloaded 5.0.2 but I've skipped the install for the time being
Think I need to do a little reading up before I root the device as I haven't got a clue what some of you are talking about haha. Thanks for all the advice so far though

No problems.
I've had a few Nexus devices and never felt the need to root them. :angel:

yosmokinman said:
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Click to expand...
Click to collapse
The majority of problems stem from Qualcomms crappy broken mess Adreno gpu drivers, hence the delayed
rollouts of Android for the Nexus 4 and 7 that both use the Adreno 320, don't be suprised if the Nexus 4 and 7 get a
Android 5.1.1 release instead.

For ppl new to nexus devices, wugfresh nexus root toolkit is a great tool until you get the hang of adb and fastboot. With a nexus you can always switch between android versions. You can always root, or go back to older versions of android. Updating to newer versions never hurts anything because you can always go back. Its a developers device so its very versatile. Try lollipop if you like, (I love it) and if its not your thing, just flash back to 4.4.4. I love this tablet.

madbat99 said:
For ppl new to nexus devices, wugfresh nexus root toolkit is a great tool until you get the hang of adb and fastboot. With a nexus you can always switch between android versions. You can always root, or go back to older versions of android. Updating to newer versions never hurts anything because you can always go back. Its a developers device so its very versatile. Try lollipop if you like, (I love it) and if its not your thing, just flash back to 4.4.4. I love this tablet.
Click to expand...
Click to collapse
You for got to mention the disclaimer if your tab came with 5.x.x out of box you cant go back to KK. Also a lot of us who recently bought Nexus 7, I have 3 that I have acquired, came with 5.0.1 installed are having issues with partitions/memory mounting in recovery. Some sort of revision done in the latest batch sent out. If his tab came with 5.0.1 or higher and has his bootloader at FLO 4.04 he may have problems trying to go back with either bootloops and what not.

masterchiefb117 said:
... with 5.0.1 installed are having issues with partitions/memory mounting in recovery...
Click to expand...
Click to collapse
Seems to be solved in TWRP_multirom_(flo|deb)_20150328 (updated to 2.8.6.0)
See http://forum.xda-developers.com/showpost.php?p=45886569&postcount=1