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 ?
Related
Hi all, I've rooted,unlocked and installed clockwork mod using mskips nexus toolkit (which worked brilliantly by the way) and the other night I recieved the 4.0.2 update request. Stupidly, in my moment of joy at a new update, I hit go without thinking about my newly unlocked and rooted phone. It hung on the android man/ exclammation mark screen and I had to do a battery pull. Thankfully it booted up fine and as far as my limited knowledge can tell its still rooted,still has clockwork recovery and is still 4.0.1. Having battered the search box I've discovered the problems lies at having clockwork recovery and not standard recovery.
I've yet to install a custom ROM (but probably will shortly) but I keep getting the 'Update available' thing pop up and even when I hit 'remind later' it seems to pop up every 30 mins or so.
So, my question is if I put a custom ROM with 4.0.3 will I still get the update notifications or will they realise I'm running 4.0.3 and leave me alone?
How does the google servers know what version I'm running - does it just go on their history of what updates they have sent you ?
Thanks in advance for anyone who can enlighten me......
Once you install a custom rom you won't get any OTA updates anymore. Even if they'd push 4.0.4.
Not sure how to fix your issue without installing a CR, but since you're saying you'll do it shortly your issue should be resolved soon I guess.
I thought that would be the case but having never installed a custom ROM I wasn't sure, kind of forces my hand into a custom rom now I've got clockwork recovery..... Need to do it ASAP cos every time I pick up the phone its got that damn update screen !
Cheers Tanith
To make sure you don't get the OTA update notification in a stock ROM, change the ro.build.fingerprint line in your build.prop file to the following:
ro.build.fingerprint=google/yakju/maguro:4.0.2/ICL53F/235179:user/release-keys
efrant said:
To make sure you don't get the OTA update notification in a stock ROM, change the ro.build.fingerprint line in your build.prop file to the following:
ro.build.fingerprint=google/yakju/maguro:4.0.2/ICL53F/235179:user/release-keys
Click to expand...
Click to collapse
Thanks for that tip, I'm keen to flash my first ROM now(got the XDA bug hard !) so won't be needing to worry about that now, just flashed up my radio to XXKK6 and will be sticking bigxie's ROM on shortly.......
cheers anyway efrant.
I'm just wondering when us SGN owners in Denmark will get the OTA..
Sent from my Galaxy Nexus using xda premium
efrant said:
To make sure you don't get the OTA update notification in a stock ROM, change the ro.build.fingerprint line in your build.prop file to the following:
ro.build.fingerprint=google/yakju/maguro:4.0.2/ICL53F/235179:user/release-keys
Click to expand...
Click to collapse
Hello, this is exactly what I need..
Kan you maybe explain how I can do this taking into account I am a total noob?
Do I need a program or something to do this?
Thanks for any help!!
John
If you don't know how to do it then don't even try until you've read up on it...Google 'edit build.prop Android' and see what you get
efrant said:
To make sure you don't get the OTA update notification in a stock ROM, change the ro.build.fingerprint line in your build.prop file to the following:
ro.build.fingerprint=google/yakju/maguro:4.0.2/ICL53F/235179:user/release-keys
Click to expand...
Click to collapse
I'm on a 4.1 ROM and it's popping up an update over and over for 4.1............. yeah....wtf?
Anyways, can I edit my build.prop the same way as above? (but I change 4.0.2 to... I dunno, 4.1.1 so it stops asking?)
MitchRapp said:
I'm on a 4.1 ROM and it's popping up an update over and over for 4.1............. yeah....wtf?
Anyways, can I edit my build.prop the same way as above? (but I change 4.0.2 to... I dunno, 4.1.1 so it stops asking?)
Click to expand...
Click to collapse
See here.
thanks dude (and +thanks to your post heh)
rebooting phone now.... 4.1 is just so smooth and I've seen bad posts about 4.1.1 so I won't bother yet!
I guess it's because of different build fingerprints, but I'm also being offered the 4.1 update although I'm already on 4.1 (according to About System).
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
Hi, i have some kind of problem with my nexus 7 2013.. I already have lollipop 5.1.1 official on my tablet and have root and unlocked bootloader (root with king root, yes it works and is rooted.. And bootloader unlocked with boot unlocker.. I know you might think that this are not the best way of rooting or unloking the bootloader but it worked for me and im happy) and since yesterday the tablet keeps telling me to update via OTA the 5.1.1 update witch i already have..i press update to install it as normal, it reboot as normal too and when it shows me the parte where it suppose to be installing the update (you know, with the android with the chest open part) the only thing that says is "error" it doesn't install anything..i did this like 3 times now and every one of them says error.. The annoying part is that it keeps showing me the notification to update it..so any solutions? Thanks!
Sorry for bad english blah blah...
You can't take ota updates if you modify system files, you did that with root. Don't know why it's showing you 5.1.1 when you already have it.
Just flash the factory image with fastboot (probably no need to wipe, just flash boot.img and system.img and format cache).
That should fix the problem. It will also remove root. I'd recommend not using that king root **** but whatever. Probably better to just flash the su zip in twrp or use CF-Auto-Root.
When the next update comes remember you won't be able to take the ota. But that doesn't matter since google posts factory images and all you need to do is flash it with fastboot, then root again.
yosmokinman said:
YDon't know why it's showing you 5.1.1 when you already have it.
Click to expand...
Click to collapse
There's a new 5.1.1 = LMY48G
Original 5.1.1 is LMY47V
^Oh yeah, lol.
Still the rest of my post will get it installed for op.
I just tried to update via downloading and then letting the phone install it, but it just rebooted me into recovery and when I clicked reboot and the phone turned back on, it said the update was corrupted.
Or do I not need to worry about OTA's anymore? Going to be flashing CM13 whenever it becomes available anyway.
Interested in the response to this, my strategy will be to stay stock for a week or two to get OTA updates, then root when good custom rom is available, on the assumption the dev will update rom with OTA updates. I'm new to HTC so please let me know if this approach is flawed
Sent from my LG-D855 using XDA-Developers mobile app
noahjk said:
I just tried to update via downloading and then letting the phone install it, but it just rebooted me into recovery and when I clicked reboot and the phone turned back on, it said the update was corrupted.
Or do I not need to worry about OTA's anymore? Going to be flashing CM13 whenever it becomes available anyway.
Click to expand...
Click to collapse
Hello guys
You can't use OTA's when you change the original recovery. You need to reflash it to HTC version to complete the update.
All explanations can be find there :
http://forum.xda-developers.com/htc-10/development/psa-htc-policy-unlocking-bootloader-t3365986
gsw5700 said:
Interested in the response to this, my strategy will be to stay stock for a week or two to get OTA updates, then root when good custom rom is available, on the assumption the dev will update rom with OTA updates. I'm new to HTC so please let me know if this approach is flawed
Sent from my LG-D855 using XDA-Developers mobile app
Click to expand...
Click to collapse
Haha, One of the best roms you will ever see is already released, Leedroid, don't wait for OTA's or you'll grow old. Just unlock and flash, soff and firmware update later lol.
Sent from my HTC 10 using XDA Free mobile app
gsw5700 said:
Interested in the response to this, my strategy will be to stay stock for a week or two to get OTA updates, then root when good custom rom is available, on the assumption the dev will update rom with OTA updates. I'm new to HTC so please let me know if this approach is flawed
Click to expand...
Click to collapse
purple patch said:
Haha, One of the best roms you will ever see is already released, Leedroid, don't wait for OTA's or you'll grow old. Just unlock and flash, soff and firmware update later lol.
Click to expand...
Click to collapse
+1 on this. Just great. Enjoyed it on M9 already and now in my 10.
Sent from my HTC 10 using XDA Labs
http://forum.xda-developers.com/showpost.php?p=66347165&postcount=2
Step 8 is your answer.
Hi guys I'm having same problem. I rooted my HTC10 and now I can't install official updates. My question is: it's really a problem that? Never Upgrading anymore my smartphone I'm going to loose something important?
And when this device will be upgraded to Android N what happens?
Rooting it I blocked forever my device? Never more official updates?
Please let me know
last_nooby said:
Hi guys I'm having same problem. I rooted my HTC10 and now I can't install official updates. My question is: it's really a problem that? Never Upgrading anymore my smartphone I'm going to loose something important?
And when this device will be upgraded to Android N what happens?
Rooting it I blocked forever my device? Never more official updates?
Please let me know
Click to expand...
Click to collapse
It is a problem you should always be up to date with your firmware. This problem can be resolved BY flashing the RUU for your device.
Excuse me yldlj, what RUU means?
Read this : http://forum.xda-developers.com/htc-10/help/updating-via-ota-modified-t3440340
Read this : (second post) http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139
Thank you CoCrop18 for your post.
I read links and now I've an answer for the community:
Someone is considering to have a workaround that allow to install OTA updates (original or modified by community) in rooted htc10?
Or can we stress HTC to release OTA for rooted devices too because they allow us officially to root it?
I watched a few videos on YouTube on how to upgrade the Android O/S but none of them mentioned that it needs to unlock the bootloader 1st.
So before I found out that I need to unlock it I tried installing ROM before I knew that.
The phone came with Android Kitkat 4.4.2 and there is an official Lollipop for it that I want to install.
The device is rooted with Kingroot.
I tried the installations two times and the phone still works but I can no longer boot into recovery mode or fastboot mode. It just hangs and then I need to remove the battery to get it to work again.
I just want to restore it back to what it was before and then I will work on unlocking the bootloader.
I prefer to use tools that are free of cost.
Issue has been resolved.
I flashed the device with a pac file using SPD upgrade tool and now all is back to default.
Johncoool said:
Issue has been resolved.
I flashed the device with a pac file using SPD upgrade tool and now all is back to default.
Click to expand...
Click to collapse
Hi. I recently messed up my phone (Y560-U02)! Please help me.
Can you please tell me where I can find the "pac file" and "SPD upgrade tool"?
Johncoool said:
there is an official Lollipop for it that I want to install.
Click to expand...
Click to collapse
You meant un-official, right?
Sorry for the delay. I check the linked email once per month.
Do you still need help on this?
I thought that it was official Lollipop. But it does not exist for this phone.
Yes I can help you get it to what ever you need but it is not easy if you want to do more than just resorted it back to default.
I will tell you more if you still need it.