yashsingh1/xdaforums huggingface dataset:
[Nexus 7 General] Letitride:
UPDATE: CWM 6.0.4.3 works - will restore ROOT !!!!

The update from KRT16O to 16S was simply, I took the OTA and restart to install. System came up & CWM 6.0.4.5 was there, I thought - everything look good - except for lost of root. Shut down & restart into Bootloader - select Recovery & sure enough, it was gone this time (Android on the side with the triangle)

No luck in flashing CWM at all, won't take. Switch over to TWRP and fastboot fash recovery .... finished in about 2 seconds, good. NOT - nothing happened, just sit there doing nothing. Oh, well - at least system is up-to-date & running, going to try 1 more time and then call it the night. Came back on XDA and find company with this - hate to roll back & start all over with the latest factory image, etc. etc.

Now, I can go get some zzzz's - I got ROOT again on 2012 Nexus 7 Wifi 32G with KRT16S. CWM 6.0.4.5 won't flash at all. TWRP will flash but won't boot into & just hang, flash CWM 6.0.4.3 on a what the heck, and got into Reoovery ( Happy Dance :cyclops: ) so flash SU 1.69 - restart SYSTEM. It's all good, everything seemed to be smooth & no FC' yet - knock on woods.

Sidenote - Stickmount is working too, I can connect OTG cable to read external 32GB USB drive, woo hoo !!
[Nexus 7 General] gsmyth:
I had received the OTA and moved it from /cache to sdcard, then flashed it in CWM touch recovery. Followed by cwm touch recovery and the latest supersu zip. Cleared cache and dalvik and rebooted, everything was fine.
[Nexus 7 General] shezzuk1:
How annoying. This morning I upgraded my n7 2012 wifi from 4.2.2 JDQ39 to 4.4 KRT16o using the brilliant WugFresh toolkit, and as soon as it boots up there's another OTA KRT16S.

I'd love to know exactly what changes it makes and whether Wug's toolkit can root and boot it.
[Nexus 7 General] gsmyth:
See my post above, just download a flashable version of your recovery and superuser/su, flash the OTA file in recovery then your recovery and superuser/su. No major changes, just some bug fixes for KRT16O build. See the changelog below:

https://funkyandroid.com/aosp-KRT16O-KRT16S.html
[Nexus 7 General] pedrolmota:
What are the steps to safely flash the update?
[Nexus 7 General] ianmedina:
There's something wrong with bluetooth.apk when im flashing it thru twrp. =(
[Nexus 7 General] bobbytomorow:
I keep getting "installation aborted [status 7]" when trying to install via latest cwm
[Nexus 7 General] khaytsus:
This typically indicates you changed something on the ROM. Build prop, framework, renamed/deleted a system file, something like that.

I was 100% stock with TWRP, I got the OTA, let it flash itself. Had to reinstall TWRP and flash su of course, but no problems. I imagine CWM would work fine as well, but in this case, I suspect you've modified the ROM.

Or you're not on Grouper?
[Nexus 7 General] JavaJunkay:
Interesting. I got the OTA notification really soon, I could bet I was in the first group of those who got it. It's strange because I live in Bosnia.

What are the changes? Just bugfixes I pressume.
[Nexus 7 General] bobbytomorow:
Yes I have changed some system files...know of a way to flash this update without having to revert everything?
[Nexus 7 General] riot1031:
I ended up grabbing the full ROM from Google and then used fastboot to flash the boot.img and system.img. Worked great and I'm now on the latest version!
[Nexus 7 General] Longi94:
flashed stock recovery, unrooted, and slashed the update using ADB sideload, reflashed cwm touch and rerooted. cwm recovery didn't disappear, everything went fine.
[Nexus 7 General] khaytsus:
You get an error during the flash? And you haven't modified it? Maybe you need to pull down the full image from the Nexus Binaries page and fastboot flash the whole system, that'll fix it for sure ;)
[Nexus 7 General] issak42:
I OTA updated and it wiped root and recovery.
[Nexus 7 General] bobbytomorow:
but this way will wipe me won't it? Or can I do this dirty (without wiping anything) and retain my data and setup?
[Nexus 7 General] Dmtalon:
I put the full google image for 4.4 on my 2012 nexus last weekend. Got the update notification sometime last night. I tried to update (fully stock/unrooted straight from google images). and it failed. After rebooting I no longer got the update notice. even when checking. I was not planning to root this one (primarily my son's) but said "screw it" after the fail.

Decided to push TWRP to it, rebooted to recovery and tried flashing manually. Its failing because:

"/system/app/Gallery/Google.apk" has unexpected contents.

Ironically, I got the update on my rooted 2013 nexus and just accidentally clicked install and it booted into twrp and flashed fine (had to reflash root). Go figure.
[Nexus 7 General] -Liam-:
Side loaded KitKat a few days ago. Working perfectly. Just turned the device on and there's as notification of an ota update. Let it get on with it and it's no different. Think I'm just surprised that it didn't figure out the device was already up to date.

Still working fine.
[Nexus 7 General] voyteckst:
I'm using CWM and the updated flashed fine. Had problems with TWRP while flashing original OTA's KitKat...
[Nexus 7 General] CatThief:
If you sideloaded KitKat a few days ago it was KRT16O. Your version should have changed from KRT16O to KRT16S after installing this OTA.

Sent from my rooted GSM Galaxy Nexus
[Nexus 7 General] JavaJunkay:
I flashed factory image with NRT, and as soon as I booted I got the notification for update. But still, in stock recovery, I get Status 7. Any help?
[Nexus 7 General] rcsrich:
I'm an Android guy through & through, but I have to say that iOS upgrades seem to roll out quickly en masse (though they are not without their own issues). I expect this kind of wonkiness from a manufacturer or carrier upgrade, but not from Google on their Nexus devices...
[Nexus 7 General] Letitride:
Go back into NRT - run the drivers check, uninstall - reboot - install universal adb drivers, then, root & install custom recovery (TWRP as default)

It should give you back root once everything is done, and, optional, flash to CWM if desired - happy running mine on NRT16S.
[Nexus 7 General] Fredro:
I had latest CWM recovery, root and stock rom. When I got the OTA I clicked restart, CWM booted up and installed the OTA with no problems. When it was done I flashed the supersu zip and everything was back to normal.

The CWM recovery is still there after reboot without any changes.

So to fix all your problems I suggest get latest CWM
[Nexus 7 General] CatThief:
There's really nothing dirty about it if you are coming from KRT16O. You won't lose your data, apps, customizations, or anything like that as long as you don't flash userdata.img. Just flash boot.img and system.img, and don't wipe or reset anything. Dalvik cache will be rebuilt after you reboot. Letting it sit about 10 minutes after that never hurts either.
[Nexus 7 General] JavaJunkay:
Thanks for the advice but flashing in TWRP gives me the same error. I guess I should just flash factory of S build
[Nexus 7 General] bobbytomorow:
Worked brilliantly, thank you :good:
[Nexus 7 General] usefulidiot127:
So I had the original nexus 7 4.4 OTA (rooted) as my primary rom with Multi-Rom/TWRP installed. I had flashed the Oxydo kernel.

I got the OTA notification and decided to roll the dice and let it install (knowing it would probably do something bad to my custom multirom/recovery/kernel setup.) It actually restarted and installed no problem in TWRP and the build version checks out as KRT16S now. I retained root, multi-rom, Oxydo and TWRP with seemingly no adverse affects.

Is that normal?
[Nexus 7 General] khaytsus:
TWRP might automatically remove the recovery-from-boot.p script, dunno. Otherwise, your TWRP is probably not there anymore. Retaining root, dunno, not sure why that was the case unless TWRP handles that as well, or you had the Chainfire 1.72 beta that was supposed to be OTA resistant.

As for custom kernel, sure, this update didn't touch the kernel.
[Nexus 7 General] Kushalized:
Hi i am facing a soft brick on nexus 4, while i was flashing kitkat krt160 .

I unlocked the bootloader. And then i forgot to turn onn the usb debugging and flash the package via 'flash-all' command in cmd. While flashing the krt160 radio got flash and after that there was no progress. Now the device doesn't start into 4.3 .

Please help me to fix it..
[Nexus 7 General] GedBlake:
Hi, all...

Not been doing much Android related stuff this past few days... had to deal with some real world (financial:() issues. But that's all now been happily resolved:). But I still kept an eye on these forums/threads.

I noticed that [MENTION=925627]khaytsus[/MENTION] had started this thread, and had made available the KRT16S OTA.zip (thanks, khaytsus). Downloaded it, but decided not to bother doing anything with it at the time. My mind was preoccupied with other matters... but I knew some weird sh!# was going on, because XDA's resident archiver-in-chief, [MENTION=3423169]oldblue910[/MENTION] had started a

thread

about the full factory images being 'silently updated' a couple of days before... but without a new build name.

Anyway, I turned on my Nexus 7 for the first time in a few days this morning (UK time)... and I received an official OTA notification in the status bar. I accepted it, it downloaded, and it updated my system from KRT16O to KRT16S via TWRP v2.6.3.1... without problems.

This is the first time I've EVER updated my Nexus 7 through official channels, since I got it in November of last year, when it originally shipped with Jellybean 4.1... and it went through several OTA updates straight out of the box.

Of course, and as I expected with the KRT16S OTA, I lost TWRP and root... but it was a simple matter to fastboot flash TWRP again, and re-acquire root.

Interestingly, I didn't have to bother deleting (or renaming) /system/recovery-from-boot.p. (It was already renamed to recovery-from-boot.bak) - I'm not sure how though, because I didn't explicitly rename it myself... maybe TWRP did it automatically??:confused:.. Anyway, TWRP just 'stuck' after fastboot flashing it.

So, my 'grouper' N7 is now running the latest KK build, with TWRP installed, and rooted via Chainfire.

Incidentally, there's a new version of Chainfire's SuperSU (v1.75) root updater .zip...

Details here...

https://plus.google.com/app/basic/stream/z12xfxshytjiuthiq04cjl1aoor5ezninhc

XDA discussion thread here...

http://xdaforums.com/showthread.php?t=1538053

Direct download here...

http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip

----------------------------------------

Well... I hope that's it for this iteration of Android (v4.4 KitKat KRT16S).

I'm as big a fan as the next guy for getting the latest version of Android on our devices, but these piddling little updates (KRT16S OTA is just 1.4Mb !) really are a bit of nuisance, particularly when you're rooted and you have to re-root all over again. Not a crippling issue to be sure, but still a case of "oh no, not again".

One wonders why Google can't get it right the first time with their updates:):).

Rgrds,

Ged.
[Nexus 7 General] oldblue910:
I love that title. I'm going to put it in my signature. haha :good:
[Nexus 7 General] bobbytomorow:
Can you get into bootloader? If you can you can flash factory image via adb
[Nexus 7 General] GedBlake:
Hi, Kushalized...

Given you state you have a Nexus 4, you might have better luck posting this question on the correct forum (this particular forum pertains to the first gen. Nexus 7). So, I would recommend you post somewhere

here

.

Erm... you actually flash (ie., fastboot flash) full factory images with the fastboot tool. ADB is effectively useless, whilst the device is booted into the bootloader.

Rgrds,

Ged.
[Nexus 7 General] Skrazz:
Kernel update?

Sent from my SCH-I545
[Nexus 7 General] RedsFan75:
Ok, quick question. I was already on KRT16O. I'd been on a custom ROM, flashed factory image zip of KRT160, re-added CWM touch, Super SU, etc... When the update came out I just dirty flashed system.img. I didn't flash boot.img or userdata.img. My question is basically what do I miss by not flashing boot.img? I've not noticed any issues so far, but do I really know what I'm looking for???

Thanks
[Nexus 7 General] khaytsus:
Nope, as per the OP ;)
[Nexus 7 General] rcsrich:
OTA hadn't shown up by this morning in Central VA, finally gave up after I tried clearing data for framework services & hosed Play store. I used the opportunity to use the NRT Updater to flash both the KRT6O and then the tiny KRT6S updates via ADB, followed by a factory reset.

Only real issue was setting up the drivers in NRT- I had forgotten that I used this PC to apply an OTA to my GS3 using the disease that is Kies- once I got rid of all those drivers, she was good to go. :)
[Nexus 7 General] xateeq:
Any one after applying the update have root issue but have flashed latest supersu then open supersu and forget all apps and let app ask for root access again. It worked for me on adaway and other without any issue.
[Nexus 7 General] CatThief:
boot.img contains a ramdisk image.
[Nexus 7 General] AKross:
<deleted>
[Nexus 7 General] RedsFan75:
Right. Flashed it now.
[Nexus 7 General] mvi57:
deleted
[Nexus 7 General] handassa:
Error updating !

Got this error when tried to update to 4.2.2 : /system/app/Gallery/Google.apk" has unexpected contents

My HTC One is Unlocked, Rooted, S-Off'ed, Kitkat 4.4 inside
[Nexus 7 General] khaytsus:
First off: Wrong forum. Second: You've modified your ROM, you'll need to fix the Gallery or return to stock/flash the full new ROM.
[Nexus 7 (2013) General] stefan.buddle:
Got a 3.4mb updaten just awhile ago, on a unlocked Nexus 7 16gb wifi, it's optimizing apps and what not right now.

Not sure if there's a thread for this already or it's just some bugfix update...

Just a heads up

Build number:

KRT16S

Kernel Version

3.4.0-gb0-eacf3

android-build@vpbs1.mtvmcorp.google.com #1

Wed Oct 23 17:41:58 PDT 2013
[Nexus 7 (2013) General] princeplanet:
Ah, man...you beat me to it!
[Nexus 7 (2013) General] Spyr0s:
Just got it too :good:
[Nexus 7 (2013) General] habylab:
I got it too. Haven't got the updated build number with an S though?
[Nexus 7 (2013) General] Matrix_19:
Maybe because your battery is too low ;)
[Nexus 7 (2013) General] angelriathica:
Got it too..
[Nexus 7 (2013) General] lenrek:
Same here, just received. I am using a rooted ROM. Root is lost after update, but easily gain back after flash su via recovery.
[Nexus 7 (2013) General] ruggie0:
Did the same thing to me, too..and lost TWRP. Thank god I have Wug's Toolkit! :D
[Nexus 7 (2013) General] dobbs3x:
I didn't get the S build either after updating this. I to also used the official image to get 4.4 when it was released.

Good, then we shall fight in the shade!
[Nexus 7 (2013) General] habylab:
Nope. Plugged in and restarted. Threw some error.

Same here. Used the odexed ROM on here.
[Nexus 7 (2013) General] desmondso99:
Do those on 4.4 receive it? Or is it for 4.3 users? as it says this update will upgrade your system to 4.4 but I already sideloaded it.
[Nexus 7 (2013) General] RicardoSul:
Yes
[Nexus 7 (2013) General] fkfs9:
how do u guys update via OTA? i click restart and install when i see the prompt, and it brought me to TWRP straight with no install.
[Nexus 7 (2013) General] lenrek:
It will upgrade the KitKat 4.4 build KRT160 (do we have other KitKit build?) to KitKat build KRT16S.

---------- Post added at 09:54 AM ---------- Previous post was at 09:53 AM ----------

I using TWRP, it install the update just fine. I am using TWRP 2.6.0.0. However, I lost root and need to flash su.zip again.
[Nexus 7 (2013) General] ruggie0:
It'll say that even if you sideloaded or bootloader flashed factory. It's fine......

But...if you are rooted, better make a nandroid backup (which I did NOT do....*doh*)...you WILL lose root and have stock recovery flashed again.
[Nexus 7 (2013) General] hohoxu_hao115:
Factory image of krt16s is available too
[Nexus 7 (2013) General] lenrek:
I only lost root. My recovery is still TWRP.
[Nexus 7 (2013) General] Dr0iD9:
Only thing i can think is some older versions of twrp must survive the ota :confused:
[Nexus 7 (2013) General] fkfs9:
im on 2.6.3.1 TWRP. i just tried it again.

Click into restart and install, it brings me to TWRP. What next?
[Nexus 7 (2013) General] lenrek:
I am using TWRP 2.6.0.0
[Upgrading, Modifying and Unlocking] climou:
Hi guys,

I wanna know whixh is the best update to do for my Qtek 9090, i mean which ROM, radio...

Actually i wanna get a nice windows interface but i'm obviously not an expert...

If someone can advise me...it should be fine

Cheers
[Verizon Samsung Galaxy S 4] dragonice81:
Just a dumb question, but what makes an OTA update different from a ROM? More specifically, why can OTAs flash fine while retaining user data while installing a ROM generally requires data to be wiped?

Thanks
[Verizon Samsung Galaxy S 4] prstorero:
It's never required, but is recommended. It can cause issues with a new ROM and it's also been known to sometimes cause issues with ota updates as well. Some people would have to wipe data after doing an update to fix strange issues.

I know in the past when coming from a 4.0 ROM and going to 4.1 or higher almost always needed data wipes. Some data gets associated with an older os and when that data is copied to a newer one, that app may not be compatible with the newer os version, causing issues.

prshosting.org
[Verizon Samsung Galaxy S 4] JeeperDon:
I've only got my S4 four days ago, but I've been ROMing before then for years. Things are a LOT tighter here in S4 land, as you can read all over. ROMing started in the old non-locked down phone days, and is still heavy on Nexus devices. Nexus devices are the ones that are first out the door with a new Android OS. The 'Nexus 5' by LG is out now to introduce KitKat (4.4). As soon as the new Android OS is released on Google's Open Source servers, ROM devs grab it and adapt it to a zillion other phones. Up until last Friday I had a custom ROM 4.4 KitKat on my Galaxy Nexus (got it from VZW on day1 Dec 2011) using full CWM recovery mode to swap ROMS in and out any time.

Answer to your question... an OTA OS is what they want you to have, with all the Samsung/VZW add-ons, a nice safe for them package. A custom ROM you load can be anything else, super clean AOSP Android, or heavily modified with all sorts of cool add-ons various developers have created. Since these S4's are so locked down, devs are really restricted in what they can do to a ROM, and it a real headache to get them loaded after that.

My phone came with MI1 and I rooted it an hour after getting home with it last weekend. I played with Safestrap, but decided there wasn't anything worth ROMing out there for an S4 compared to what I knew on my old open phone. I took the MK7 load 2 days ago, still rooted thanks to the write-ups here. The Samsung/VZW 4.3 is actually pretty nice in my opinion (once you 'Turn OFF' some things or 'Freeze' them with Titanium Backup). I don't plan on any ROMS for the S4. I'm actually relieved with that. ROMing becomes an addiction. My dog is happier with the new phone too, as we get to go on more walks with my new found non-ROMing time.
[One (M7) Accessories] onefasttreopro:
Hello all, figured I'd pop in and do a short review/first impression post of some Halo screen protectors I bought on amazon. since buying something for the first time and being nervous on quality can make it hard for someone to make a decision I hope this helps to make it easier. I highly recommend them for affordability, fit, clarity and durability. I've used Halo screen protectors on my precious phone (Evo LTE)) and was also impressed with them. I work in a dusty/grimey shop and my fingers definately put the protector to the test...for roughly 6 bux for a 3 pack they are a great deal too. They are made of a stiffer style plastic that is easy to apply once you verify edge fit and align before releasing the plastic and it sucks itself to the screen. If anyone has any questions feel free to ask and I will try to help/answer as best I can.
[One (M7) Accessories] Jimmy2u:
I have not used this brand ever but after viewing your reviews would like to try it...well I would say you have a nice case...buddy...:)
[One (M7) Accessories] onefasttreopro:
Yea give them a shot...I never heard of the brand until buying for my ego ltd and now for my HTC one. amazon is where I usually get them with free shipping (if you spend a certain amount). In my case they are cut so accurately that you don't have a screen protector edge, they go right to the very edge...
[Galaxy Note 3 Q&A, Help & Troubleshooting] zuuus:
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)

That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.

Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.

This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.

I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ultramag69:
What was the last version of firmware flashed?

You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.

You might also need to use Megawipe to clear any errors that stay on your device after flash.
[Galaxy Note 3 Q&A, Help & Troubleshooting] zuuus:
Hey mate, last version of firmware was the Stock Telstra SM-N9005 / TEL ROM I found on www . sammobile . com/firmwares/2/

I have tried at least 10 different ROMs with no luck, every single one does the same thing.

I did send it off to Telstra to try for a repair, they sent it back to me unrepaired due to nothing to do with the software but a 1/4mm scratch my keys made in the chrome plastic around the edge with the words "unable to be repaired due to physical damage" with a little sticker pointing to the scratch. ****ing ridiculous if you ask me.

Honestly I don't know all that much to do with the modems and csc's so it might be that causing my problems but I have tried a bunch of different ones without any change.

At my wits end here, phone is just over 30 days old and I can't use the damn thing.
[Galaxy Note 3 Q&A, Help & Troubleshooting] polish_pat:
try odin back to stock, then use kies to "emergency firmware restoore" Kies can be a life saver in some situation, make sure you use beta 3 version