Develop Bugs

[Q] OTA update 3.26.605.1

I recently started getting system update notices for 3.26.605.1 on my D-Inc.
I'm running the "standard" clockworkmod recovery that flashed when I rooted the phone. As I understand it, I can not install the update because I'm rooted so is there a way that I can stop the notices (without unrooting and going stock)?
I've also read chatter on other forums about a fix or "root version" on the way from unrevoked, but I haven't been able to find anything official.
Can anyone confirm an update from unrevoked?
Thanks.

Hey Dude,
I figured I would get to you before the wolves do lol you'll probably get a better response to your questions in the "General" section. To answer you directly there is already rooted versions of this OTA such as (shameless plug) both my Roms Redemptive rEVOlution (Evo hybrid) and Redemption Rom.

OK. Thanks.

RuLEoF2 said:
OK. Thanks.
Click to expand...
Click to collapse
Not a problem enjoy Rom hunting.

RuLEoF2 said:
I recently started getting system update notices for 3.26.605.1 on my D-Inc.
I'm running the "standard" clockworkmod recovery that flashed when I rooted the phone. As I understand it, I can not install the update because I'm rooted so is there a way that I can stop the notices (without unrooting and going stock)?
I've also read chatter on other forums about a fix or "root version" on the way from unrevoked, but I haven't been able to find anything official.
Can anyone confirm an update from unrevoked?
Thanks.
Click to expand...
Click to collapse
I've been hitting Cancel on that update message for the last 2 weeks. Today I read about it a bit, and finally just gave in and ran the update. I don't know if it actually updated, but the message is gone, it says my system is up to date, and I still have S-OFF/root. FWIW.

jrocket said:
I've been hitting Cancel on that update message for the last 2 weeks. Today I read about it a bit, and finally just gave in and ran the update. I don't know if it actually updated, but the message is gone, it says my system is up to date, and I still have S-OFF/root. FWIW.
Click to expand...
Click to collapse
you can edit the build prop to make it stop search the skyraider thread i think its in there.

ACD168 said:
you can edit the build prop to make it stop search the skyraider thread i think its in there.
Click to expand...
Click to collapse
I saw that, thanks. I wanted the update, I just couldn't find any solid answers on whether it disabled root or not. It sounded like it disabled root but left S-OFF alone, so I did ran the update, thinking I could root it again later. But now I still have root, so I don't know if the update was actually applied or not.
I'm not worried either way, it was just an experience relevant to the OP's question.

jrocket said:
I saw that, thanks. I wanted the update, I just couldn't find any solid answers on whether it disabled root or not. It sounded like it disabled root but left S-OFF alone, so I did ran the update, thinking I could root it again later. But now I still have root, so I don't know if the update was actually applied or not.
I'm not worried either way, it was just an experience relevant to the OP's question.
Click to expand...
Click to collapse
Go into Settings/About Phone and see what firmware version you have, if it's 26 your updated, if it's still 21, it didn't update.
If you don't know if it's updated, it's prolly not. You would've known as it would've rebooted and then had run the update. If you don't recall any of that, your not updated.
Like was posted previously, you'd be better off finding which ROM has the update and then just flash that, be sure to do a backup 1st and foremost in case you screw up, you can always flash back to what you had and start over.
The only way that update will take is if you have stock with just root and no changes, I did this initially though and you will loose root, which is why I recommend you backup before trying, this way you don't have to root over again.

Edit build.prop. Here is the configuration you'll need to change to stop the OTA updates. This will also help save your battery if it frequently tries to download on 3G.
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys

RuLEoF2 said:
I recently started getting system update notices for 3.26.605.1 on my D-Inc.
I'm running the "standard" clockworkmod recovery that flashed when I rooted the phone. As I understand it, I can not install the update because I'm rooted so is there a way that I can stop the notices (without unrooting and going stock)?
Click to expand...
Click to collapse
If you want to stay put on the version you have now, not accept the update, not be bothered by it again, then following bsdbytes's info for editing the build.prop is what you need to do.
If you want to accept and the NOV OTA update and still have clockworkmod recovery and root after... see -> http://solo.dc3.com/dinc/ (If you have an SLCD incredible, be carefull of which CWM Recovery version you use).
RuLEoF2 said:
I've also read chatter on other forums about a fix or "root version" on the way from unrevoked, but I haven't been able to find anything official.
Can anyone confirm an update from unrevoked?
Thanks.
Click to expand...
Click to collapse
The current Unrevoked3 (ver 3.21) does not work to root the Nov OTA, nor install a custom recovery. There were tweets about an update coming, but delays due to thanksgiving, finals, etc. I haven't seen an ETA posted yet.

joelcableguy said:
Go into Settings/About Phone and see what firmware version you have, if it's 26 your updated, if it's still 21, it didn't update.
If you don't know if it's updated, it's prolly not. You would've known as it would've rebooted and then had run the update. If you don't recall any of that, your not updated.
The only way that update will take is if you have stock with just root and no changes, I did this initially though and you will loose root, which is why I recommend you backup before trying, this way you don't have to root over again.
Click to expand...
Click to collapse
thanks for the info. you're right, it didn't update, i'm still at 21. when i clicked update a window came up saying it was going to reboot, but it never did. must be due to change i had on the device.
KidJoe said:
If you want to stay put on the version you have now, not accept the update, not be bothered by it again, then following bsdbytes's info for editing the build.prop is what you need to do.
If you want to accept and the NOV OTA update and still have clockworkmod recovery and root after... see -> LINK (If you have an SLCD incredible, be carefull of which CWM Recovery version you use).
Click to expand...
Click to collapse
thanks for that link - i'll try to go through that when i get a chance.

Yakju not getting OTA update

Hi guys,
I used the GNEX toolkit to unlock my bootloader and then flash to 4.0.2 yakju. I'm just wondering why I'm not getting an OTA for 4.0.4 or 4.0.3. I've tried clearing the data in GoogleFrameWorkServices. I've also flashed stock recovery.
Did I do something wrong, or is there actually no update?. P.S I'm in Australia.
Any help would be greatly appreciated.

Im in the same boat.
I have flashed the completely stock 4.0.4 ROM from Google Code. I have not received the IMM76I update yet.
I have cleared the framework cache too and still nothing.
I live in Melbourne (australia) and I am assuming that the update to yakju devices works on a country-by-country basis.
IF I don't receive it soon, I am just going to hope Google Code gets updated and I will just reflash a the newer version.
I do not want to root the phone or using work-around methods to install an update. I like having a completely stock phone with a locked bootloader.
(Marshallaw.. Why not just download the 4.0.4 update from Google Code and flash using Fastboot? Atleast that way, you know your on the latest Android version and have a better chance of receiving the IMM76I update, or if worst comes to worst, just wait until Google Code is updated to the latest version and flash that?)
The way Google updates their devices is pretty pathetic. You would think they would push the update to every stock YAKJU device everywhere and not be so selective. My old Nexus S received 4.0.4 update and my stock Galaxy Nexus never received it, so I had to manually flash. Very stupid.

Simmo3D said:
[snip]
IF I don't receive it soon, I am just going to hope Google Code gets updated and I will just reflash a the newer version.
I do not want to root the phone or using work-around methods to install an update. I like having a completely stock phone with a locked bootloader.
Click to expand...
Click to collapse
I think you are confusing a few things:
1) What is posted on Google Code (as you put it), are NOT updates -- they are complete, full ROMs.
2) What is posted here are incremental update that UPDATE your existing ROM.
There is a difference between the two, despite the end result being the same.
3) Having an unlocked bootloader or a locked bootloader does not mean you are stock or are not stock -- it has nothing to do with it at all. You are not adding or taking away anything from the firmware on the device...
4) You say you do not want to use a work around to flash the update, but you are using a work around to flash a full ROM? Something there doesn't compute for me.
5) Flashing a stock update file does not make you any less/more stock than flashing a full ROM.

I don't think you understand what I meant.. Im hoping Google updated their full ROM with the IMM76I kernel and bug fixes...
hence, I am waiting for an updated full ROM that 'includes' the latest kernel update.
e.g. Google Code features :
4.0.1 (ITL41D) and 4.0.1 (ITL41F). I am waiting for
4.0.4 (IMM76D) and 4.0.4 (IMM76I) to be posted on their site.
I also know that having a locked bootloader does not make it stock, but my point was I am on stock 4.0.4 with a locked bootloader, so I am waiting for an OTA so I don't need to re-install all my files/apps.
But if I don't receive the OTA update, I will be reflashing the entire ROM once its available on Google Code.

Simmo3D said:
I don't think you understand what I meant.. Im hoping Google updated their full ROM with the IMM76I kernel and bug fixes...
hence, I am waiting for an updated full ROM that 'includes' the latest kernel update.
e.g. Google Code features :
4.0.1 (ITL41D) and 4.0.1 (ITL41F). I am waiting for
4.0.4 (IMM76D) and 4.0.4 (IMM76I) to be posted on their site.
I also know that having a locked bootloader does not make it stock, but my point was I am on stock 4.0.4 with a locked bootloader, so I am waiting for an OTA so I don't need to re-install all my files/apps.
But if I don't receive the OTA update, I will be reflashing the entire ROM once its available on Google Code.
Click to expand...
Click to collapse
Well, I'm not sure if this is it but here's the OTA package for IMM76I from IMM76D. It might just be a test build which was only pushed to small portion of users to test it which would explain not everyone getting it.
And Marshalllaw, you've already begun to flash things and mess around, why not just flash the stock build of 4.0.4 straight away rather than relying on an OTA?

Simmo3D said:
[snip]
I also know that having a locked bootloader does not make it stock, but my point was I am on stock 4.0.4 with a locked bootloader, so I am waiting for an OTA so I don't need to re-install all my files/apps.
But if I don't receive the OTA update, I will be reflashing the entire ROM once its available on Google Code.
Click to expand...
Click to collapse
Ok, but you do realize that manually installing the IMM76I update (which you can do right now, although requires an unlocked bootloader) ends you up at the exact same place the flashing the IMM76I image when it comes out (and it will still require an unlocked bootloader). So whether you install the update, or what for the full image, you will still wipe, and you will end up at the same place -- you will just get there sooner with the update.

OK but how do you flash this with fastboot once I unlock my boot loader. I need to boot with CWM don't I?
Sent from my Galaxy Nexus using xda premium

Simmo3D said:
OK but how do you flash this with fastboot once I unlock my boot loader. I need to boot with CWM don't I?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Correct, you do. But booting CWM is different from flashing CWM. When you boot it, you are not "writing" anything to your device - you are only loading the kernel and ramdisk into your device's RAM. It only boots CWM one time - as soon as you reboot, it is no longer there, as it was never flashed - it just existed in RAM.
Additionally, even if you did flash it, it still wouldn't be there when you rebooted, because EVERY OTA update adds two files to your device that automatically re-flash the stock recovery on EVERY boot of your device.

Unlawful said:
Well, I'm not sure if this is it but here's the OTA package for IMM76I from IMM76D. It might just be a test build which was only pushed to small portion of users to test it which would explain not everyone getting it.
And Marshalllaw, you've already begun to flash things and mess around, why not just flash the stock build of 4.0.4 straight away rather than relying on an OTA?
Click to expand...
Click to collapse
Hi Unlawful. Yeah I can always flash it directly to 4.0.4, its more that this is my first Android phone / first experience messing with bootloaders and roms. I was more so just wondering if the lack of OTA update to either 4.0.3 or 4.0.4 was that i've screwed something up or that the update has not been pushed to all devices.
My device info is: 19250XXKK6, ICL35F. Its basically the same as when I first bought it but not Yakjuwx. I more or less flashed to Yakju because people were saying that you could get OTA updates faster or something.
Thanks for the help, sorry if this is a noob question.

I wouldn't be too sure though I would really doubt it's something that you did. Have you pressed 'Check Now' somewhere in settings to check whether there's an update?

Unlawful said:
I wouldn't be too sure though I would really doubt it's something that you did. Have you pressed 'Check Now' somewhere in settings to check whether there's an update?
Click to expand...
Click to collapse
Yeah I hit check now and it always says I'm the most up to date. I tried clearing data in google services framework and then hitting check now. Nothing changed.
I just find it odd that I wouldn't get an OTA for 4.0.3.
I used the GNEX toolkit to flash the stock rom which I got from developers.google.com/android/nexus/images. I read online that someone thought that 4.0.4 was pulled from OTA, but I would have thought I would get 4.0.3. I'm nervous that I've messed something up lol

marshalllaw said:
Yeah I hit check now and it always says I'm the most up to date. I tried clearing data in google services framework and then hitting check now. Nothing changed.
I just find it odd that I wouldn't get an OTA for 4.0.3.
I used the GNEX toolkit to flash the stock rom which I got from developers.google.com/android/nexus/images. I read online that someone thought that 4.0.4 was pulled from OTA, but I would have thought I would get 4.0.3. I'm nervous that I've messed something up lol
Click to expand...
Click to collapse
4.0.3 was never released in OTA form.

Unlawful said:
I wouldn't be too sure though I would really doubt it's something that you did. Have you pressed 'Check Now' somewhere in settings to check whether there's an update?
Click to expand...
Click to collapse
That does not work. You will have to wait until Google decides it's time for your IMEI to receive it...
marshalllaw said:
Yeah I hit check now and it always says I'm the most up to date. I tried clearing data in google services framework and then hitting check now. Nothing changed.
I just find it odd that I wouldn't get an OTA for 4.0.3.
I used the GNEX toolkit to flash the stock rom which I got from developers.google.com/android/nexus/images. I read online that someone thought that 4.0.4 was pulled from OTA, but I would have thought I would get 4.0.3. I'm nervous that I've messed something up lol
Click to expand...
Click to collapse
You did not mess anything up. As martonikaj said, there was never any 4.0.3 update.
Updates are not rolled out to everyone all at once. It could take seconds or MONTHS before you get the OTA, after the first person gets it.

Awesome . Thanks for the help guys.
Having an Android is great for all the exploring you can do, finding out how it works though can be a bit daunting.
Sorry for the noob question!.

[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.

upgrading from Yakju to Jelly bean... how?

hey all, I noticed that jelly bean is out, sort of.
i would like to put it on my nexus but am sofar unable to make sense of the development forums pertaining to this so hopefully someone here can help me understand this.
I used the efrant's post:
http://forum.xda-developers.com/showthread.php?p=21113773#post21113773
to take my yakjuux nexus to yakju (4.0.4) using fastboot and the stock image provided from google...
I would like to upgrade further, though from what i can figure out JB is only available on takju (yakju with google wallet (works in US only)).
can someone here help me?

batkinson001 said:
hey all, I noticed that jelly bean is out, sort of.
i would like to put it on my nexus but am sofar unable to make sense of the development forums pertaining to this so hopefully someone here can help me understand this.
I used the efrant's post:
http://forum.xda-developers.com/showthread.php?p=21113773#post21113773
to take my yakjuux nexus to yakju (4.0.4) using fastboot and the stock image provided from google...
I would like to upgrade further, though from what i can figure out JB is only available on takju (yakju with google wallet (works in US only)).
can someone here help me?
Click to expand...
Click to collapse
If you're running stock yakju you don't really need to switch to takju. Just install CWM (The Galaxy Nexus Toolkit is an awesome tool to help you do that) and flash this.

You can go from any rom (custom or stock) to jb as far as you have cwm and xxla2 radios..
Cheers
Sent from my Galaxy Nexus using xda premium

Camazza said:
If you're running stock yakju you don't really need to switch to takju. Just install CWM (The Galaxy Nexus Toolkit is an awesome tool to help you do that) and flash this.
Click to expand...
Click to collapse
got some troubleshooting to do... phone wont show up in fastboot... cant use the toolkit until i figure this out.
edit: reinstalled the naked universal driver... shows up in fastboot now.

Does this method wipe everything?

Camazza said:
If you're running stock yakju you don't really need to switch to takju. Just install CWM (The Galaxy Nexus Toolkit is an awesome tool to help you do that) and flash this.
Click to expand...
Click to collapse
i think it worked, used option 6 for my build of android, then selectedthe option to install cwm touch, followed the instructions in section 3 on:
http://forum.xda-developers.com/showthread.php?t=1614827
Hopefully this will fix the issue i was having with my nexus where the radio would lose all connection to the network... usually have to reboot the phone to get it to work again... a minor annoyance for an awesome phone. Atleast it doesn't take 3-5 min to boot up like my blackberry playbook tablet (that's not cool RIM, please fix)...

nipcarlover said:
Does this method wipe everything?
Click to expand...
Click to collapse
it didn't on my nexus... though i didn't use the 7th option which does steps 3-6 (unlock bootloader, root phone, flash recovery) which would wipe the phone.
I just hope i can still send messages on it, last time i flashed it i had to get telus to resend the info to the phone.

another question, I don't think I got the full JB os, as my phone is still using the xxla2 radio... if i wanted to go back to yakju for the full stock OTA update, supposedly coming next month sometime, and keep my warranty, I would just reflash everything back to yakju, including recovery (CWM - stock)?
I assume I would have to do this with the fastboot in the DOS window since I don't think that I can revert everything back to 4.0.4 with the toolkit.
also how do I tell if the phone is rooted? I don't think i did this but would like to know anyways.

batkinson001 said:
another question, I don't think I got the full JB os, as my phone is still using the xxla2 radio... if i wanted to go back to yakju for the full stock OTA update, supposedly coming next month sometime, and keep my warranty, I would just reflash everything back to yakju, including recovery (CWM - stock)?
I assume I would have to do this with the fastboot in the DOS window since I don't think that I can revert everything back to 4.0.4 with the toolkit.
also how do I tell if the phone is rooted? I don't think i did this but would like to know anyways.
Click to expand...
Click to collapse
Yes, for stock, use adb+fastboot and Nexus Factory Images for everything stock 100%. And to check for superuser, just download an app that requires it and see if you get a command prompt. But even easier than that, SuperUser or SuperSU should be in your app drawer if you have it installed, and also in your /system/app

anton2009 said:
Yes, for stock, use adb+fastboot and Nexus Factory Images for everything stock 100%. And to check for superuser, just download an app that requires it and see if you get a command prompt. But even easier than that, SuperUser or SuperSU should be in your app drawer if you have it installed, and also in your /system/app
Click to expand...
Click to collapse
I don't have those apps installed, guess I am not rooted. Good to know.
Also it should be noted that I no longer have any input lag using poweramp, with ICS 4.0.4 there was always a 1 second (seemed like it anyways) delay between the button press and the phone doing what I want. I hope this extends to using my bluetooth headset as well.

hmmm figured i would try downgrading to takju using the toolkit... it did everything which is nice however i noticed that it still uses the radio from yakju...
is there a way to check what it didn't add to the phone when it downgraded?
edit: I should add that it wiped my phone when I loaded takju...
looking forward to getting the official JB update next month...

batkinson001 said:
hmmm figured i would try downgrading to takju using the toolkit... it did everything which is nice however i noticed that it still uses the radio from yakju...
is there a way to check what it didn't add to the phone when it downgraded?
edit: I should add that it wiped my phone when I loaded takju...
looking forward to getting the official JB update next month...
Click to expand...
Click to collapse
I already had bootloader unlocked, so I just had to install CWM recovery and flash the jb-takju image mentioned earlier. Once the phone has rebooted the CWM was gone, so had to reflash that. Afterwards I downloaded the XLFF1 radios (you can search for radio-i9250-xxlf1.zip) and flashed them as well. Now my phone shows all the same versions as the takju phones passed out at Google I/O. All my settings, etc. were preserved.

dmapr said:
I already had bootloader unlocked, so I just had to install CWM recovery and flash the jb-takju image mentioned earlier. Once the phone has rebooted the CWM was gone, so had to reflash that. Afterwards I downloaded the XLFF1 radios (you can search for radio-i9250-xxlf1.zip) and flashed them as well. Now my phone shows all the same versions as the takju phones passed out at Google I/O. All my settings, etc. were preserved.
Click to expand...
Click to collapse
i really would like to remain stock but get JB as well, what would I need besides that radio to make the takju image from the google site to be prompted to dl the OTA JB update if it is still available to download from google...?
edit: screw that, found efrant's post:
http://forum.xda-developers.com/showpost.php?p=28178320&postcount=2
hopefully the jb-takju.zip linked earlier in this thread is the same as the one in efrants' post....
if not, is it possible to reflash with the newer zip without setting everything up again?

batkinson001 said:
i really would like to remain stock but get JB as well, what would I need besides that radio to make the takju image from the google site to be prompted to dl the OTA JB update if it is still available to download from google...?
edit: screw that, found efrant's post:
http://forum.xda-developers.com/showpost.php?p=28178320&postcount=2
hopefully the jb-takju.zip linked earlier in this thread is the same as the one in efrants' post....
if not, is it possible to reflash with the newer zip without setting everything up again?
Click to expand...
Click to collapse
The linked one produced the same build number (JRN84D) on my phone as the one on the phone that came from Google I/O, which is the same as the one in efrants' post.

dmapr said:
The linked one produced the same build number (JRN84D) on my phone as the one on the phone that came from Google I/O, which is the same as the one in efrants' post.
Click to expand...
Click to collapse
good to know, i compared the url's for both links, the one in efrant's post is missing the ) at the end. I ended up wiping the cache's (except for the one that sounds like some guys name) and flashed the zip from it. working great so far.
at the moment I am reinstalling my apps, and i do not think that all of the apps that were in the google folder last time i reinstalled the os, are there. anyone know what the default apps that are supposed to come with the OS are in that folder? I can only remember Layer which I installed manually...

batkinson001 said:
good to know, i compared the url's for both links, the one in efrant's post is missing the ) at the end. I ended up wiping the cache's (except for the one that sounds like some guys name) and flashed the zip from it. working great so far.
at the moment I am reinstalling my apps, and i do not think that all of the apps that were in the google folder last time i reinstalled the os, are there. anyone know what the default apps that are supposed to come with the OS are in that folder? I can only remember Layer which I installed manually...
Click to expand...
Click to collapse
Sorry, I didn't have to reinstall anything, so the apps in my Google folder are the same as before the update. I do however have Currents in the main app drawer which I don't remember having before.

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 ?