yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] topgeardave:
If you mean by OTA, let the OTA release. Using titanium backup, backup your phone and backup all your texts etc and nandroid. Copy all the contents of your sd card to your pc and flash the stock factory image. That way your radio and bootloader are flashed cleanly and you won't have any problems in the future.

Flash your recovery once you boot the rom, then use titanium backup and nandroid manager to recover your stuff, but seeing as L uses the new ART not all apps will work until they are updated so I recommend you wait for apps to be updated then just restore the app data. By starting from scratch it removes any errors and troubleshooting.

If you're on stock rom, just flash stock recovery and a stock rom without root. You should be able to OTA just fine unless you've flashed other mods which will need removing.

If you're on a total custom rom like pa, slim or cm, then just wait for them to update the rom with latest sources and flash the latest bootloader and radio before flashing the new ROM.
[Nexus 5 Original Android Development] blackt5:
Flashing with system images are the way to go, especially with major updates. Starting with a clean slate makes sure nothing stuck around from tinkering. Ive dirty flashed imagies on minor updates by flashing individual partitions excluding data and its fine. Id say its a big no no going to 5.0.
[Nexus 5 Original Android Development] supersain08:
anyone?
[Nexus 5 Original Android Development] silvan g:
Try clearing the FKU app data

Sent from bacon
[Nexus 5 Original Android Development] franciscofranco:
Did you buy the app from the Play Store?
[Nexus 5 Original Android Development] russlowe73:
Are you on kk or the dev L preview. You can only ota from kk, if your on L preview you have to either flash kk, then grab ota, or just flash the L images when they are released.
[Nexus 5 Original Android Development] supersain08:
Yes, I deleted app data and then uninstalled it. Then installed it again from Playstore. Working fine now, not sure what happened
[Nexus 5 Original Android Development] franciscofranco:
Weird... glad its sorted.
[Nexus 5 Original Android Development] tylerdurden83:
Your suggestions are surely excellent, but I wanted to add my experience. In the previous kitkat updates from stock 4.4 to 4.4.1, 4.4.2 and 4.4.4, what I did was download the OTA file on my device and flash it via CWM. Note that when I flashed the OTA via CWM I was rooted, on franco kernel, and using other devices bionic and dalvik, yet the OTA update succeeded just fine (clearly though, all those modifications were lost and had to be reapplied). So imo while it's probably true that you won't receive the OTA unless you are full stock, you can definitely flash it via recovery without having to rollback all system changes first. This has worked for me 3 / 3 times on my N5 and even more often on my N10, so I'm pretty sure about it.
[Nexus 5 Original Android Development] topgeardave:
Manually flashing the OTA you could get away with it. However seeing as android L has massive underlying changes such as file system mount points, I'd go with stock recovery as just flashing it could result in reading data issues. All 3 iterations of kitkat were quite similar so that's why you got away with it. However you could try manually flashing the OTA but there's a chance in data reading issues.
[Nexus 5 Original Android Development] Ltdrev:
Reading previous post I can't understand why ppl still don't backup (if they dont want to lose the nudies) get a factory img and then hook their precious devices to their computers to make good use of fastboot.

Flash-all still better than any toolkit and/or dirty flashing. I doubt anybody (sane) would say the opposite!

same old, same old...
[Nexus 5 Original Android Development] duffymm:
Actually I'm on latest 4.4.4 Stock + cwm recovery + Franco Kernel

I'm going to flash using fastboot recovery and boot to go back "full stock" and receive OTA.

Do i have to restore also system.img from the full stock or recovery+boot img are enought ?

Thx a lot - i know this is a bit offtopic
[Nexus 5 Original Android Development] WettbackMartyr:
Flash boot system and recovery
[Nexus 5 Original Android Development] Flyview:
Well here's a problem I've encountered with doing that. When you copy all of your media back to the phone, the Date Modified is changed, and apparently the Date Created doesn't exist in Linux so all of your media ends up being out of order if you just copy the files back onto the internal storage. Anyone know a good way around this?
[Nexus 5 Original Android Development] Ltdrev:
How do you "copy" out and "copy" back your files, with adb ? And what folder are you pulling ?

Please define "media being out of order"
[Nexus 5 Original Android Development] Flyview:
Yes, I used adb to pull all of the files from the data partition. Then I copied them back with adb as well. When pictures are ordered by date, they are not in the order taken, since as far as the phone can now tell, they were taken when you copied them back.
[Nexus 5 Original Android Development] Ltdrev:
I was afraid it was deeper of a problem! :fingers-crossed:

You can manually edit the date of pictures or do it by batches with apps on the playstore... OR if you trust Google with your nudies you can use the very nice Google Photo voila problem solved until Google or the earth goes kaboom.
[Nexus 5 Original Android Development] kevtrysmoddin:
It does using super su here
[Nexus 5 Original Android Development] Ryrynz:
Wow. The **** storm is amazinnng. Glad it all got worked out though.. The bait was bad though and it hooked a ton of nubs.
[Nexus 5 Original Android Development] treehugger38294:
My issue was fixed by doing a wipe of internal storage. Factory resets did nothing.
[Nexus 5 Original Android Development] Ltdrev:
That guy (MrMobli) didn't measures his words and used a tone that look a lot like talksh** free bashing. He his responsible for his demise, when something's not right in your view you should try to start a debate in private with the concerned peoples if possible, take the time to cool down and start the conversation in good faith, with that done the initiator should be able to listen to the answers the other party has to offer before acting like a duche and bash something because he's frustrated.

Hope this story won't show the way to the regiments of parasitic trolls looking for some kind of exposure.
[Nexus 5 Original Android Development] el_smurfo:
Well I for one found Kenyans post rather enlightening. I have been trying our FK on my N5 for both KK and now LP, but I was not aware of the system changes and requirement to fully dirty flash to restore system. I am running stick LP, so there's really not a flashable zip...am I supposed to fulls wipe my whole device just to change a kernel? As with xposed and other major mods, this kernel needs a recovery flashable uninstall of any system mods.
[Nexus 5 Original Android Development] sjknight413:
That post was specific to the one plus one, the files he mentions aren't even part of the nexus 5's system. Quit your whining.

Also, nobody needs to create a flashable revert zip for you just so you don't have to reflash. If you are that bothered and want to revert REFLASH YOUR ROM OR BACKUP /SYSTEM AND BOOT BEFORE FLASHING IN THE FIRST PLACE.

it really isn't rocket science.

Sent from my Android 5.0 Lollipop + ElementalX powered Nexus 5
[Nexus 5 Original Android Development] akash3656:
Don't be like that ridiculous guy. Just find the downloaded fastboot images on your PC, extract them and then.

fastboot flash system system.img

Nandroid your system and boot partition then flash what you want. Wanna try a different kernel? Cool. Just restore the system and boot partitions from the backup you made earlier. Then flash away.

Even if there were zips that magically reverted the changes, this is XDA. Nobody reads OP anyway.

By the way: Wrong device to worry about. This is a N5 and not a 1+1 where CM pushes changes in an unpredictable manner that causes all the drama on that G+ post.
[Nexus 5 Original Android Development] el_smurfo:
Thanks for bringing all the vitriol of the G+ post back over here. I simply was stating that I was alarmed by the potential for system changes. Since apparently the OPO FK OP doesn't mention these system level changes, it is completely rational for me to think that the N5 kernel might be doing the same thing.
[Nexus 5 Original Android Development] sordna:
Agreed, no flashable revert zip is needed.

However I will say that the OP or the 2nd post after the OP should have uninstallation instructions. Such as rename /system/lib/x to /system/lib/y ... flash stock boot.img and reboot. Alternatively a list of shell commands that we can run as a shell script to revert system changes. This info is buried in these kernel threads, it should be up front, and it should be updated any time a new kernel version touches a new part of the system.
[Nexus 5 Original Android Development] el_smurfo:
Thanks for not losing the important message in a shouting tantrum again. A lot of folks make plenty of system level mods to their own phones...cerberus, build prop, host files, etc. Telling a user in post 36,501 that they should back up their /system partition to flash a kernel is completely ridiculous. There are a lot of nice tools like Flashify that make kernel comparison easy, but they likely don't revert these other changes either, leading to instability later on that cannot be traced back here. Perhaps rename this "kernel" to "Franco Mod" or something would also help explain things that are not readily apparent to those that actually do read the OP.
[Nexus 5 Original Android Development] fredfox_uk:
This post details how to revert http://xdaforums.com/showpost.php?p=49836372&postcount=15486 for the N5 and it was mentioned again a few weeks ago here http://xdaforums.com/showpost.php?p=55734566&postcount=35762 It's also in the FAQ here http://xdaforums.com/showthread.php?t=2532422

I do find it a little sad that XDA has become "dumbed down" recently. If you're going to try something as fundamental as replace the kernel, why not find out how to revert first ? Or is the expectation now that everything is a simple push button process ? It would be nice I guess for those that don't want to or can't figure it out or know where to look or ask.

If I was Franco though, and Android dev work was my main source of income, I'd provide a non-technical revert process, much easier to sell FKU if people know that they don't have to use fastboot or mess around in recovery or rename files (lol, how hard is that !!). Unfortunately I'm not that gifted, so I'll leave that to those far better than me :)
[Nexus 5 Original Android Development] simonarturo:
People just want things handed down to them on a silver tray.

Had they bothered to read the FAQ thread, they would have found that the process to revert to stock is explicitly stated and explained in there, system changes and all.

Unlocking the bootloader should come with a disclaimer: "Not for lazy people that do not want to read and understand how flashing affects their devices"
[Nexus 5 Original Android Development] el_smurfo:
I agree that xda is dumber than in it's prime, and I've been around here for quite a while, but when I flash a kernel, I expect to flash a kernel, not a bunch of other mods without that being very prominently highlighted in the OP, not at post #15,486. I have always found kernel mods to be mainly placebos or worse, so the only kernel I have flashed and stuck with for more than a few days is Franco. This whole episode has me questioning that decision, which is not what I should be doing with the most popular kernel available.
[Nexus 5 Original Android Development] Tzfardaya:
While I understand the argument for the information to be placed prominently in the op, the information is available through the op already, in the faq linked from it.

Although the wifi issue is specific to the opo, system files are changed on the n5 as well.. namely the 2 files renamed to the bak extension. This is so Franco can use his own thermal system rather than the stock system.

Even if it's not featured in the op, or linked to in a faq, it is easy enough to find with a quick search...

Since this is a developers site, people should expect to have to do at least that much.
[Nexus 5 Original Android Development] fredfox_uk:
I suspect it was posted much sooner than 15,486, but that's the one I book marked as I knew I would need it at some point :) if I could be bothered to search ( :) ) I'm sure I could find it sooner in the thread.

This kernel is popular for reason, and there's enough normal, non-fan junkies using it that to give a fair indication that's success is beyond placebo or fan junkie blinkers. Some like it, some don't - thankfully, and often those that don't like it offer suggestions to improve it, maybe that's what'll come out of this debacle / spat / argument / tiff.

FRANCO FOREVER !!!!

(sorry)

---------- Post added at 05:41 PM ---------- Previous post was at 05:38 PM ----------

stop posting before I can reply. You keep doing it to me and it's annoying. Work keeps getting in the way of me posting. not fair.

:p
[Nexus 5 Original Android Development] shreddintyres:
Has anyone noticed that the android L version of FK (r66) seems to have lost the ability to read exfat volumes? I understand that the L preview is just that and the kernel for it should be regarded as such as well. If others are experiencing this and for some reason it was removed or not included in r66 (i understand it was a large merge things could have gotten lost in the noise) Could exfat drivers be included again? if not a work around exists just rather have it in FKU. (im not talking about auto mount, ive been using stickmount to mount drives for a while now)

sorry if this is kinda ... scatterbrained (one of those days)
[MENTION=3292224]franciscofranco[/MENTION] [MENTION=4860519]Tzfardaya[/MENTION]

Thank you in Advance

Cheers.
[Nexus 5 Original Android Development] Degrated Shadow:
I have flashed many kernels since flashing full android l image. Never needed anytging to revert to anything. I have went even stock then franco then elemental x then franco again with no reverts needed. Although i did backup kernel images. No revert was needed for me doing all that. So people please stop posting this pointless stuff in a original development thread. I may be wrong but there is a dedicated discussion thread for this.
[Nexus 5 Original Android Development] Tzfardaya:
Okay, I'll turn Tapatalk notifications off for my Pebble... That should help a bit..

I could be wrong, but I don't think Franco has ever had the fuse files baked into his kernel for exfat... (although now that I think about it, I do recall a conversation here about adding them... Can't remember which way it went.) Check the stickmount thread here for links to the exfat and ntfs fuse support files and see if they work for you...
[Nexus 5 Original Android Development] sordna:
Not sure if the FAQ covers revert instructions for all devices (there are almost 10 different devices that have Franco Kernel). For example I am on a nexus 4. Another person may be on a One Plus One, another on a Nexus 7, Galaxy Nexus, etc.

So it scales better for each kernel thread to have the device specific file renaming instructions in the respective OP.

The other problem about searching is you may land on a post that says rename these 2 files but in the mean time another kernel version may have introduced a 3rd file.

So this info should be in a prominent place and kept up to date.

I've been using FK since early Jelly Bean and have successfully done OTAs many times, so I know my way, but every time I have to dig and research when it is so easy to post the 2-3 filenames to be renamed in the OP for each device thread.
[Nexus 5 Original Android Development] Tzfardaya:
Same files in the same place on all the devices... Only the opo (temporarily) has an extra change...
[Nexus 5 Original Android Development] shreddintyres:
Hmm I think it might have been something on slim ROM when i was running it previously I completely forgot that might have been the case. I know about the fuse binaries but thank you for the information.

You're always very helpful .

Cheers
[Nexus 5 Original Android Development] numb_:
last_kmseg

Hi [MENTION=3292224]franciscofranco[/MENTION]

I'm running the last L preview and FK r66. My FKU settings are all stock and i was using the power-saving profile when a self reboot occurred.

I hope this last kmseg can help you.

I wasn't able to upload the complete last_kmseg, so it's cut :(

I added the complete file at this post, maybe it can be helpful..

Sorry for my bad English..
[Nexus 5 Original Android Development] sordna:
Nope. FK in N5 renames a file that in the N4 does not. These kind of general assumptions is what we need to avoid.
[Nexus 5 Original Android Development] el_smurfo:
Assumptions? Its clearly documented in post 17,075...
[Nexus 5 Original Android Development] blackt5:
I keep getting super user toast messages from FKU while browsing the web with Chrome Beta. Maybe one every 5 to 10 minutes. Don't see this behavior in other apps.. Anyone else seeing anything odd like that?

How would i even troubleshoot this one?

Using FKU beta on l preview with no per app modes.
[Nexus 5 Original Android Development] sordna:
Use detailed logging in your Super SU app and report exactly what commands FKU is repeating when this happens.
[Nexus 5 Original Android Development] blackt5:
Will do and report back.
[Nexus 5 Original Android Development] franciscofranco:
I was reading last pages about OTAs and file renaming etc, I agree that I should do a better job documenting those changes for all my supported devices and I'll work towards improving that.
[Nexus 5 Original Android Development] OGroteKoning:
Great attitude after that G+ thread. Great attitude...
[Nexus 5 Original Android Development] mazubo:
Anyone have issues after flashing the r66 zip? After I flashed it, my n5 hangs at the 'Google' screen...

TIA =-D
[Nexus 5 Original Android Development] franciscofranco:
Depends, did you flash it on L or KitKat?
[Nexus 5 Original Android Development] mazubo:
Thanks for the reply. I'm on stock 4.4.4.

I am rooted,
[Nexus 5 Original Android Development] franciscofranco:
In the OP it says:

Android 5.0 Lollipop

boot image:

Doesn't seem that hard to miss.
[Nexus 5 Original Android Development] mazubo:
My bad. Thanks for being decent about it.. Cheers!
[Nexus 5 Original Android Development] franciscofranco:
Just curious, did you flash without reading or you searched in the OP/headline/whatever and you couldn't find the info?
[Nexus 5 Original Android Development] mazubo:
I was speed reading... And for the record, I'm not a very good speed reader..:p
[Nexus 5 Original Android Development] franciscofranco:
Hm alright. Maybe if the info was more explicit you would've seen it on your poor speed reading. I'll work on that, and you should be a bit more careful next time ;)
[Nexus 5 Original Android Development] mazubo:
Helvetica is especially difficult... However lesson learned. Thanks Fransisco!
[Nexus 5 Original Android Development] franciscofranco:
Added better warning about the latest builds being only for Lollipop and explanation on how to prepare for the next OTA due to the changes on the /system partition.
[Nexus 5 Original Android Development] Koragg618:
Great work as always man! :good:

I was wondering, are there any significant changes from the preview and AOSP sources that make it worth making a new IMG?

Thanks as always!
[Nexus 5 Original Android Development] franciscofranco:
They haven't pushed the updated Kernel sources.
[Nexus 5 Original Android Development] el_smurfo:
Interestingly, I went to revert the changes listed in your new op and the post previously linked to me, but my system files were unmodified. I am running the latest L build, originally rooted with Chainfire kernel and I flashed Chainfire over FK before seeking out the files, so maybe it fixes these mods?
[Nexus 5 Original Android Development] galakanokis:
That portion of the post is specific to running KitKat and wanting to upgrade to L, reverting the files to get the OTA. Since your anyway on L...

If you are wondering if the L kernel also has some system modifications that's an entirely different question.
[Nexus 5 Original Android Development] el_smurfo:
I am absolutely wondering that, and continually frustrated that the information is not clearly presented. I have been linked to multiple posts, FAQs and have been called a whiner and lazy, but the fact is, changes that this mod makes are not well and clearly documented and it is leading to a lot of unnecessary frustration for users that are working hard to be good android citizens
[Nexus 5 Original Android Development] galakanokis:
Might want to actually read them then. In the updated op it clearly states KitKat, not L. Not much to figure out there. That's on you.

Also, in the second post of the fax linked in the op it talks about returning to stock and OTA's and points you where to go. Again, not overly difficult but you have to read and not be spoon feed.

All that took me less than 30 seconds to discover. Also by reading I deduced that the L kernel hasn't made system changes the way others have because full source isn't out and these are test kernels and he doesn't have to worry about CM crap to get around since CM has nothing L related.

I could be wrong about the system changes on L but I would just ask a simple question rather than passive aggressively trying to prove a point.

Bloody hell my phone is being a ***** tonight...
[Nexus 5 Original Android Development] el_smurfo:
Thanks. Your deductive reasoning powers are far greater than mine. I prefer clear documentation in the OP (you know, like we always berate people for not reading)....BTW, I have been asking the question about whether the r66 kernel makes system mods for the last 24 hours with only incorrect responses so far. I guess I just need better spoon feeding, but I'll try to deduce better.
[Nexus 5 Original Android Development] galakanokis:
It's in the op, just in a link to more info. Not sure how that is hard to follow. OP is clean and easy to read, if I want more detail great I will follow the link, if not I don't have to scroll on and on.

Does every ROM/kernel clearly label in the op what they changed? Or do they provide links to websites with more info or change logs? Someone can confirm but isn't the system file changes documented in the change logs?

What version of L are you running? Most of the zips are pretty hacked up right now and the fully permissive kernels for root? Are all the changes clearly labeled in those op's?
[Nexus 5 Original Android Development] el_smurfo:
Every kernel I've ever tried is exactly that...a kernel...this is the first one I've experienced with the potential for changes to the system files that remain when the kernel is reflashed. I don't run hacked up code... Fastboot install of Google preview image.

The whole reason the question came up is because the OPO kernel rewrites system files, even when booted temporarily from fastboot. Since that is not disclosed in that thread, I would like to know if similar things are being done undisclosed in this kernel. I have been shown multiple links and comments, but those don't apply to the L kernel, so I am asking if system modifications are made when the L kernel is installed. Its really not complicated and scrolling change logs to find out that your kernel is doing something it really shouldn't is hardly well documented. I'm not trying to make this an issue, but since folks here seen intent on responding to legitimate questions with angry retorts.
[Nexus 5 Original Android Development] neobuddy89:
This: https://github.com/franciscofranco/ramdisk_hammerhead/blob/master/boot.img-ramdisk/init.fk.sh
[Nexus 5 Original Android Development] el_smurfo:
Thanks man, but none of that happened with the r66 kernel flash... None of those files were modified (perhaps a problem in itself)... I'm just trying to find out if anything was