OTA for KRT16O from JWR66Y failed on my Nexus. It bootlooped, and I had to reflash stock. I haven't yet decided to try updating again, but today I got a notification that an update was ready to install. I checked it out, and the file says (in part) signed-nakasi-KRT16S-from-JWR66Y.
I've searched the Nexus forums for KRT16S and can't find mention of it. Anyone else have it?
What's the difference between that and KRT16O?
Inquiring minds want to know.
Serial_Noob said:
OTA for KRT16O from JWR66Y failed on my Nexus. It bootlooped, and I had to reflash stock. I haven't yet decided to try updating again, but today I got a notification that an update was ready to install. I checked it out, and the file says (in part) signed-nakasi-KRT16S-from-JWR66Y.
I've searched the Nexus forums for KRT16S and can't find mention of it. Anyone else have it?
What's the difference between that and KRT16O?
Inquiring minds want to know.
Click to expand...
Click to collapse
Coming from 4.3.1 myself, was running 16O myself for a week+ and then got the OTA for 16S, it's a minor update, bug fixed and newer apps, etc. and seemed to run smoother, and has the GEL, etc. - running quite smoothly for me to the point where I decided to wipe & deep clean and start fresh.
Then, I saw this & decided to flash it instead, keep my CWM & root, but essentially just like factory fresh rom, with SUv1.75 and busybox, odexed and starting off with plenty of internal storage space. Got lazy instead & opted for it instead of flashing image, running ADB & unlock routine all over.
http://forum.xda-developers.com/showthread.php?t=2533035
As always, backup via TB & custom recovery, and save it offline to portable storage first, just in case. I was fully prepared this past weekend to start from scratch - too many posts about problems downloading, upgrading, bootlooping and freezing, etc.
Related
Hello,
I will try to keep this short. Was running 4.1.1 and rooted with moto2fail and installed safestrap recovery then I made a stock backup.
One day, my camera quit working (camera screen loads then a box pops up saying unfortunately, the camera has stopped) Anyways, I cleared data, rebooted same results. I didn't want to mess around with any files, so I decided to update to 4.1.2.
After the update, i get message that the update failed but everything seemed to be fine. AND the camera started working again.. Ending up losing root in the process, motochopper appears to install fine, but I get an error message when trying to update supersu. So, I reverted back to my 4.1.1 backup through the rp(?) tools in the stock recovery.
So now I'm back to 4.1.1 with full root, but no working camera. I can update to 4.1.2, but I think I'm gonna have problems with rooting again.
I did try reinstalling the stock MotCamera.apk from a stock razr m 4.1.1 rip. but it still fails. How can I fix the camera issues without having to mess around rsd lite?
Sorry about the confusion, just trying to lay out my issues and I will answer questions as I can.
i'm having the exact same issue, after failing to update to 4.1.2, i restored to 4.1.1 backup i had, but the camera just force closes. i'm on stock room.
bobross82 said:
Hello,
I will try to keep this short. Was running 4.1.1 and rooted with moto2fail and installed safestrap recovery then I made a stock backup.
One day, my camera quit working (camera screen loads then a box pops up saying unfortunately, the camera has stopped) Anyways, I cleared data, rebooted same results. I didn't want to mess around with any files, so I decided to update to 4.1.2.
After the update, i get message that the update failed but everything seemed to be fine. AND the camera started working again.. Ending up losing root in the process, motochopper appears to install fine, but I get an error message when trying to update supersu. So, I reverted back to my 4.1.1 backup through the rp(?) tools in the stock recovery.
So now I'm back to 4.1.1 with full root, but no working camera. I can update to 4.1.2, but I think I'm gonna have problems with rooting again.
I did try reinstalling the stock MotCamera.apk from a stock razr m 4.1.1 rip. but it still fails. How can I fix the camera issues without having to mess around rsd lite?
Sorry about the confusion, just trying to lay out my issues and I will answer questions as I can.
Click to expand...
Click to collapse
It could be that the Update has updated the firmware of the Camera itself, causing it to now be incompatible with the older 4.1.1 drivers baked in.
Typically when I get into these types of scenarios, I always feel best doing something along the lines of an RSDlite wipe and start fresh. Do the update straight, then customize afterwards.
I would unlock your bootloader prior to guarantee you have a back door into the phone afterwards.
I can't rsd back to 4.1.1, i get a preflash verification error, the only thing that works is matt's new utility that flashes to 4.1.2, the camera works after that, but i want the camera to work on the backup I did when i was on 4.1.1 before the update.
cybrnook said:
It could be that the Update has updated the firmware of the Camera itself, causing it to now be incompatible with the older 4.1.1 drivers baked in.
Typically when I get into these types of scenarios, I always feel best doing something along the lines of an RSDlite wipe and start fresh. Do the update straight, then customize afterwards.
I would unlock your bootloader prior to guarantee you have a back door into the phone afterwards.
Click to expand...
Click to collapse
I ended up booting in stock recovery by trying to get into fast boot, then selecting ap or rp tools(can't remember which). Truthfully, didn't even realize what it was. It loaded up what to me looked like the recovery menu with safestrap. Which I thought I uninstalled. From there, i restored the 4.1.1 backup I had. Then updated superuser and supersu from the play store. read in another thread to check and uncheck temp unroot in voodoo ota. twice.
Then I took the 4.1.2 update, was then able to install the supersu binary once it was finished and checked, and it kept root through the update. Camera works also. I still received a update fail message afterwards. But all appears to be okay, camera works, root checker says I have root, so all appears to be good.
I did make a backup of this in safestrap, and updated my backups in titanium, and froze a bunch of apps. Everything seems to be working just fine. I haven't unlocked the bootloader because I don't really feel like flashing any roms to this phone. Stock rom and rooted seems to be be good enough for me. For now.
If you still have a locked bootloader, you can't revert back without having issues. Once you've installed 4.1.2 and its boot.img, you shouldn't be able to restore a 4.1.1 ROM. If you are unlocked, then it's a different story.
For the OP, the best solution is to use Matt's Utility 1.20 and fastboot flash to 4.1.2. This utility does not require the use of RSD. After you flash, boot up the phone and just do basic setup, then use the Motochopper function in the utility to get root access. After you get root, then continue set up on the phone.
Hi there,
I have a rooted 3G Nexus 7. I ran the notification to run an OTA update for 4.3 Jellybean, it rebooted into TWRP, and I blindly said yes. Eventually I confirmed TWRP to allow it to fix root permission. I tried rebooting, but I ended up getting stuck at the X screen. Tried a few resets, but that didn't work. I Googled a bit, cleared the cache and the dalvik cache on TWRP, and came across this.
I got lazy, and probably shouldn't have done most of what I had done, so I'd like to know if there is a way to fix this without having to reflash the ROM.
Fix
I got impatient waiting for a response, so I just flashed Cyanogen on it, thinking this would be the most opportune time to try it out hehe. To anyone else who runs into the issue and sees this, I'm 99% sure that you could just flash stock on too, but I wanted to try out a custom ROM.
Hi Everyone,
I am currently running android 4.3(JWR66v) I flashed it using fastboot, so it is clean.
After that I rooted it and installed CWM v6.3.6 and BusyBox pro.
That is the only changes I did to my device,everything else is stock.
2 day ago I got a system update notification, looking in the cache folder I found this :
"8b2531d9d9a686c7dcf347513ce8141d59a251c6.signed-nakasi-JWR66Y-from-JWR66V.8b2531d9.zip"
I confirmed the reboot/Install but it failed with the classic (Status 7) I do not understand what is going on ?
Do I need flash my device again with a factory to get the update to install ?
I had the same setup since I bough this device last year and It had no trouble what so ever upgrading before(Unlocked+rooted+CWM)
This is supposed to be a nexus device but it sure doesn't act like one,
Can some one please help ?
Had the same problem going from 4.2.2 to 4.3. Same as you, stock rooted, but had TWRP as my recovery. I did go back to stock recovery, but no go. Ended up doing clean install. However, going from JWR66V to JWR66Y, I had no problem. Took OTA without even having to install stock recovery.
You must not be as stock as you think. My guess is you must have altered something in system that they are checking on. Hope someone with more knowledge is able to help you out because it is a PITA to have to clean install for every update. Good luck.
My N7 16GB WiFi, rooted but stock, updated successfully to 4.3 some time ago. Basically, I used Voodoo OTA to save the root, let the OTA do its work, then restored root using Voodoo OTA. It's worked flawlessly since then.
Suddenly, after weeks with no issue, it started insisting it had to install 4.3 from a downloaded file. It nags constantly, which makes it hard to use the tablet. I've got CWM as the recovery so whatever file it's trying to install won't work from there. The only way I can find to go back to stock recovery involves wiping the tablet. I don't want to do that, unless there's no other alternative.
I looked for the update.zip file in the location that the tablet insists its stored at (root of SD card), but there's no file there by that name that I can find. It only shows up if I allow the nag screen to try and install it. Of course, CWM says that it can't verify the file and aborts the install. Which puts me right back at the ever-present nag screen.
Just to be clear, I am already running 4.3. This whole situation came up months after I'd upgraded. Is there anything I can do to stop the upgrade notices, short of running a factory reset and having to set up the tablet again from scratch?
May have found an answer. Used Wug's toolkit to force-restore the standard recovery. Had to do some old ADB driver removal for a bunch of other Android devices first. Appears to have deleted the unnecessary update file as part of the process. Will keep an eye on it going forwards, but think it's good.
Nope -- didn't work. Had to do a full factory reset/restore to out-of-the-box condition to get it to stop constantly trying to re-upgrade to 4.3. Annoying.
I am all stock on my nexus 7 wifi, updated to kitkat using OTA. But the tablet has become laggy and unresponsive. SD card read write has slowed down, There used to be more apps loaded in memory while on 4.3 but only a few are there now. I wanted to know what are my options other than rooting and installing custom rom??
Sent from my Nexus 7 2012 wifi
I had the exact opposite from my N7 wifi. It had become barely usable before the update. Apps taking forever to load, apps hanging or crashing, real laggy. It's stock, just rooted.
The OTA update made a huge difference for the better. That's what I've been hearing from others too.
It can be a PITA but I would make note of the apps you want and get your saved stuff off (pics and docs etc) and wipe it with the factory kitkat image from Google.
You shouldn't be experiencing what you are.
Sent from my SCH-I535 using xda app-developers app
Reflash or just factory reset??
Sent from my Nexus 7
I have the same problem. KitKat has has made my nexus 7 so slow. When I looked on the net some people say a factory reset sorted this out but some say there was no change. Think its so bad Google put this update out without testing it properly. As there seems to be lots and lots of people with this problem.
like skrusrnmz said, i m beginning to think incremental updates break something about apps and system slows down. flashing fresh stock from scratch might solve it...lets see.
XperiaMT27 said:
like skrusrnmz said, i m beginning to think incremental updates break something about apps and system slows down. flashing fresh stock from scratch might solve it...lets see.
Click to expand...
Click to collapse
+1 Before the KitKat 4.4 OTA, the N7 2012 WiFi was already running on a series of patches and updated Apps via Play Store, getting sluggish & running low on space. For anyone that's on XDA, you know how easy it is to unlock the bootloader & get root after flashing custom recovery via ADB (try not to use toolkits - as a last resort or for the lazy ones, LOL)
If you have custom recovery already (and, I recommend & recommend TWRP over my long favorite - CWM) just reset, wipe cache & dalvik and use one of the flashable zip - after doing the proper TB backup & TWRP backup to a secured storage media. Push recovery again if necessary, along with Busy Box & SU v1.75) - reboot & setup the basics - then restore TB (w/o data to avoid errors) and let it stabilize with any newer update, finalize tuned settings. End result - a smooth rooted stock rom & kernel on 4.4 which is what I'm running for the last 2 weeks ... until developers can do their magics on both odexed & deodexed roms with their tweaks.
If you aren't happy with the results, you can always restore your saved images from custom recovery & go back to 4.3.1 or what now - but, IMO, you will appreciate & learn to like KitKat.
My 2012 Nexus 7 was slow before the KitKat update. Afterwards it was dog slow. So I did a factory reset. It's now back to being buttery smooth.
Sent from my Nexus 7 using Tapatalk 4
Yeah I think it's an issue with updating and not wiping. I just flashed the image myself and yeah it's smoother
Sent from my Nexus 4 using Tapatalk
i think it may be you have too many file on your device. try to delete some file. it should go faster
I had the same problem when upgraded from 4.2.2 to 4.3 and never resolved with stock firmwares.
Try a factory reset, but it's not guaranteed that it will work.
I have factory reset my device before installing fresh stock, its better than before. will test a few days, otherwise fresh installation.