Database Info

[4.4.4][ktu84p]STOCK Rooted with busybox for tilapia[6/19/14]

It is cooked from the Google stock image for tilpia and is NOT deodexed
This is the first time i am posting a ROM on XDA.
Been cooking ROM's for a while for my old Samsung devices.
The whole reason for this thread is to have a flashable zip for any Nexus 7(2012) 3g user who wishes to stay stock.
I have tested it on my Nexus 7, if anyone has any issues do let me and please bear with me as im not a developer and just sharing what i personally use.
Will try and help with what ever i can.​
************** For some Reason the boot logo does not show up, dont worry, wait for sometime, the ROM will boot up***********
Note:
1. Works with multirom.
2. Odexed for my personal use, if anyone wishes to de-odex it, do let me know.
3. This includes the stock kernel. I also tested the latest stable mkernel which is for 4.4.2 and works fine.(works with the new kitkat 4.4.4 too)
Screenshot attached
Downloads:
4.4.4:
tilapia.v2
Mirror
Radio for 4.4.4
md5 for Radio: 64920d406852d92b478c3ab17383ecce
4.4.3:
tilapia.v1
md5 : 5c4d3b47274000cf6d5326d14ab7cc81
Click to expand...
Click to collapse
Installation:
1. Reboot to recovery
2. Do a factory reset.
3. Go to advanced wipe settings and select system, dalvik and cache and format them.
4. Flash Rom
First boot takes time, wait patiently. There wont be any boot animation, so wait on that black screen for sometime
Profit :good:
Click to expand...
Click to collapse
credits: @JustArchi

Let me know guys if there is any issue. Im little busy this weekend, will take little time to add things like Advanced reboot menu, battery % and debloat.

phanitej said:
Let me know guys if there is any issue. Im little busy this weekend, will take little time to add things like Advanced reboot menu, battery % and debloat.
Click to expand...
Click to collapse
Hi, Can I flash this over 4.4 [KRT16O]? Please advise. Thanks.

gwong76 said:
Hi, Can I flash this over 4.4 [KRT16O]? Please advise. Thanks.
Click to expand...
Click to collapse
Update your bootloader and radio first. And clean flash is recommended though there are not much of changes from 4.4.2 but as you mentioned you are using 4.4 clean wipe and installing is preferred.

thank you very much! stock rocks! :good::good:
PS: root & bbox?

Thanks alot
Hi!
First of all - thanks for your clean/xposed ROM.
I only have one question. Would it still be possible to send SMS from my Tilapia-tablet (Nexus 7-2012/3G) after flashing your ROM?
BTW : @RomerGG - The threads' header should already have answered your question...
Regards,
Roy

roygaard said:
Hi!
First of all - thanks for your clean/xposed ROM.
I only have one question. Would it still be possible to send SMS from my Tilapia-tablet (Nexus 7-2012/3G) after flashing your ROM?
BTW : @RomerGG - The threads' header should already have answered your question...
Regards,
Roy
Click to expand...
Click to collapse
Haven't tried that. Unfortunately i have a pure data plan, so my provider restricts sms by default. And i cant take out the sim and replace as i was once trying to break open my sim slot and take out the sim, during that crazy struggle i guess i broke that sim holder. so once the sim comes out, i have to struggle a lot to get the network back on by replacing it
Edit: dont think hangouts will give the sms sending option by any chance. So try with a third party app and let us know

Thanks for the stock rooted rom. FYI, I had flashed CF SuperSU v1.99r4 and also MKernel a67, looks okay so far. I'm updating the Google apps from Play store now. Once done, I'll be installing TB to restore my apps.
One word of caution to those flashing this rom. Note that there seems to be no bootanimation, so don't be mistaken that the rom is not working. Give it time to boot up. :good:
Edit:
One thing I noticed strange is in TB, System ROM is showing 670MB (8.45 MB free). Before this, I was on 4.4.2 stock rooted, before I manually flashed boot.img and system.img. It was showing same results, but 9.XX MB free. Is this correct? I vaguely remembered that it should be almost 900 plus MB. Can anyone confirm?

phanitej said:
Update your bootloader and radio first. And clean flash is recommended though there are not much of changes from 4.4.2 but as you mentioned you are using 4.4 clean wipe and installing is preferred.
Click to expand...
Click to collapse
Sorry for this stupid question. How can I updated these .img files ?

Thank you for this work!! I had the slimkat, I did a wipe recovery and then I installed. Where is the menu button?
Art is not activated?

apinun_po said:
Sorry for this stupid question. How can I updated these .img files ?
Click to expand...
Click to collapse
To flash them you need to enable USB debugging and then reboot to bootloader. Here use the following fastboot commands.
For Updating bootloader:
fastboot flash bootloader name_of_the_bootloader_file.img
For radio:
fastboot flash radio name_of_the_radio_file.img
If you want a detailed instruction, go here and follow Method 2.

sbarrett said:
Thank you for this work!! I had the slimkat, I did a wipe recovery and then I installed. Where is the menu button?
Art is not activated?
Click to expand...
Click to collapse
It is the same file as the one google pushes for Nexus 7 device. So what ever is present in the original stock image, will be there.
Menu button is only active in apps that give it by default, there is an xposed module which can activate menu button in every app.
For ART, not sure why google misses the option to switch to ART every time on Nexus 7 devices. Will check and see how to add that option.

phanitej said:
To flash them you need to enable USB debugging
Click to expand...
Click to collapse
Thank you very much.

Kitkat 4.4.4 is out and the stock rooted version is tested and :good:uploaded.

One quick question my all friend here. 4.4.4 still dalvik or run as ART
Sent from my GT-I9205 using Tapatalk

yusopa said:
One quick question my all friend here. 4.4.4 still dalvik or run as ART
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
It is dalvik. Google does not seem to want including ART for the nexus 7. Read somewhere on google forums that it might be a hardware issue cos of which they are not including it.

flashing aborted
Version tilapia2 flashing aborted, version tilapia 1 ok. Do you know where is the problem? Using the latest version of the recovery v6.0.4.3.

Good work! I maintain BSZKitKat for grouper (ODEX and DEODEX). Awesome job getting right in front of the 4.4.4 update!
---------- Post added at 05:30 PM ---------- Previous post was at 05:29 PM ----------
phanitej said:
It is dalvik. Google does not seem to want including ART for the nexus 7. Read somewhere on google forums that it might be a hardware issue cos of which they are not including it.
Click to expand...
Click to collapse
Correct - we lack sufficient space on the /system partition for the binaries required for switching to ART

Cant' flash this rom, i get an error and the message FAILED.
I'm using TWRP recovery 2.7.

Can we have a flashable zip please?
It is much easier to deal with!
Thanks

Trying to update Nexus 7 2013 from 4.3 to 4.4.2

I did not want to update my nexus 7 at the time I obtained it due to kitkat being new and not having a 1 click root. So I disabled the notifications. Recently I found a 1click app for kitkat and decided I would just restore to factory and then update. I was told to just clear google framework data but that did nothing and only restarted the download..... Problem is even after the restore I am getting verification errors via the manual update via system updates. I am currently sitting here with a full 25Xmb download of the update and am trying to in the nexus recovery mode to load the abt from sideload in cmd but at first i got error 7 and used winrar to repair the zip which got rid of the error 7
Now I am getting
failed to verify whole file signature
signature verification failue (which is what manual update would say when it finished downloading on the system updates screen)

AndroidObsession said:
I did not want to update my nexus 7 at the time I obtained it due to kitkat being new and not having a 1 click root. So I disabled the notifications. Recently I found a 1click app for kitkat and decided I would just restore to factory and then update. I was told to just clear google framework data but that did nothing and only restarted the download..... Problem is even after the restore I am getting verification errors via the manual update via system updates. I am currently sitting here with a full 25Xmb download of the update and am trying to in the nexus recovery mode to load the abt from sideload in cmd but at first i got error 7 and used winrar to repair the zip which got rid of the error 7
Now I am getting
failed to verify whole file signature
signature verification failue (which is what manual update would say when it finished downloading on the system updates screen)
Click to expand...
Click to collapse
i dont know what genius told you that clearing framework data would do what you want, but thats not even close to the right answer.
use this tool to installl the latest factory firmware.
also, this is a nexus device. you dont need to wait for one click root methods. after you unlock and put on a custom recovery, all you need to do is flash the su zip file and install a su managing app then you will be rooted on any version of firmware.
its been a while since i used that tool (i have a 2012 n7) but im thinking it will help you with the recovery and root too if you need it.
wug makes some good scripts.

bweN diorD said:
i dont know what genius told you that clearing framework data would do what you want, but thats not even close to the right answer.
use this tool to installl the latest factory firmware.
also, this is a nexus device. you dont need to wait for one click root methods. after you unlock and put on a custom recovery, all you need to do is flash the su zip file and install a su managing app then you will be rooted on any version of firmware.
its been a while since i used that tool (i have a 2012 n7) but im thinking it will help you with the recovery and root too if you need it.
wug makes some good scripts.
Click to expand...
Click to collapse
updated:

AndroidObsession said:
can't thank you enough for the help in the right direction... Spent all last night frustrated cause no matter how many times i tried to sideload it either was error 7 or error in whole file verify. i will give this a try and get back to you with an update if all goes well... one question though... if there a way to switch the built in 4.3 restore with the 4.4.2 once its installed fresh? that way if i wipe again ill at least be back at fresh 4.4.2 instead of going thru 4.3 issues again
Click to expand...
Click to collapse
Last time I used it there was no default file, you could choose whatever one you wanted, I'm assuming up to current unless he hasn't made those files available.
I don't know if you can insert your own file if he doesn't have it current.
I know it used to download the file you choose, so you may not be able to add alternatives.
Sent from my G2 running SlimKat

bweN diorD said:
Last time I used it there was no default file, you could choose whatever one you wanted, I'm assuming up to current unless he hasn't made those files available.
I don't know if you can insert your own file if he doesn't have it current.
I know it used to download the file you choose, so you may not be able to add alternatives.
Sent from my G2 running SlimKat
Click to expand...
Click to collapse
@bweN diorD
so far i have
flashed stock and unrooted then unlocked 4.3. not sure where to go from there atm... keep getting that error.... Thanks again for the assistance
I also tried doing adb sideload via toolkit but the zip i have keeps giving error 7 verification failed/aborted when trying to update the os from jwr66n to JSS15R so i could manual update to 4.4.2
or even if i try skipping jss15r it will give whole file verification failed when just trying to go straight to 4.4.2

AndroidObsession said:
@bweN diorD
so far i have
flashed stock and unrooted then unlocked 4.3. not sure where to go from there atm... keep getting that error.... Thanks again for the assistance
I also tried doing adb sideload via toolkit but the zip i have keeps giving error 7 verification failed/aborted when trying to update the os from jwr66n to JSS15R so i could manual update to 4.4.2
or even if i try skipping jss15r it will give whole file verification failed when just trying to go straight to 4.4.2
Click to expand...
Click to collapse
im not sure what else to tell you, maybe try and do the update normally ota.

bweN diorD said:
im not sure what else to tell you, maybe try and do the update normally ota.
Click to expand...
Click to collapse
edit: OH.... i think i figured it out now.... i found the firmware selection now

The toolkit had a bad hash apparently for 4.4.2 but i did manual and went to the google page to grab the factory and manually flashed.
tablets now 4.4.2 unlocked and as far as i know rooted. ty for guiding me.
issue is now resolved.

[How-To] Update to G900V_OC4 - 5.0 and KeepRoot (3/30/2015)

**You can begin the following process from any Build/ROM but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app.
**Caution!** The following process is only for the G900V Verizon S5 variant. Use on any other device may result in a hardbrick!
Download:
- G900V_OC4_Stock_Rooted_ROM
- G900V_OC4_Stock_DeOdexed_ROM
Set your screen timeout setting to 10 mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and use default "Reboot" setting.
6. Last, press the lightning bolt then "Ok" to begin the flash .
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the Verizon splash screen for 1 - 2 minutes (10 - 15 mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
Optional - Enable Native Tethering:
- G900V_OC4_TetherAddOn (Flash using FlashFire's "Flash zip or ota" option).
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, Stock Recovery, and Bootloader to OC4.
3. No need to wipe prior to flashing, the ROM will automatically perform a factory data reset. If you prefer not to wipe User Data replace the Updater-Script in the ROM's META-INF/com/google/android folder with the version attached to this post (remove ".txt" extension before placing in folder). Bear in mind that carrying over incompatible User Data from a prior Android version may cause issues.
4. If you do not already have root access (or to unbrick) you must flash the G900VVRU1ANCG_Full_Odin.tar (flash in Odin's PDA slot(AP in Odin v3.09+)), root with Towelroot (this version does not require internet access), then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Credits:
@ChadH42 - for capturing the ota update.
@Chainfire

What is new in this update? I saw your other thread was closing and I'm confused

xdnax said:
What is new in this update? I saw your other thread was closing and I'm confused
Click to expand...
Click to collapse
Let's just say the initial 5.0 release had a few bugs. Let's hope this release works better.

Thanks. I did your previous update with this method, and it worked great. Can you give the steps that are needed to get to where you need to be to now install this update? I think I know, but I'm not sure. Also, what about apps and settings? It does not seem they are preserved. It looks like the previous write up has been edited and no longer includes these steps. I had no problems with this part. Is it still an option to do that? Thanks for the awesome work!

update
So this will work fine updating if on rooted 0A8?

I would assume we could do a data backup, then restore data after flashing is done

So there's no need to flash a firmware or kernel in Odin after flashing the rom? Are we still going to be on 0A8 baseband? Or should we flash the OC4 kernel?
Sent from my SM-G900V using XDA Free mobile app

killa408shark said:
So there's no need to flash a firmware or kernel in Odin after flashing the rom? Are we still going to be on 0A8 baseband? Or should we flash the OC4 kernel?
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Correct, all necessary OC4 partitions including the kernel, modem, etc are included in the ROM.

Mr. Boom said:
I would assume we could do a data backup, then restore data after flashing is done
Click to expand...
Click to collapse
Only recommended if your Data backup is from 5.0. Those updating from 4.4 should not restore Data for compatibility reasons.

jake20fc said:
So this will work fine updating if on rooted 0A8?
Click to expand...
Click to collapse
Yes

mkitchin said:
Thanks. I did your previous update with this method, and it worked great. Can you give the steps that are needed to get to where you need to be to now install this update? I think I know, but I'm not sure. Also, what about apps and settings? It does not seem they are preserved. It looks like the previous write up has been edited and no longer includes these steps. I had no problems with this part. Is it still an option to do that? Thanks for the awesome work!
Click to expand...
Click to collapse
See Notes section #3.

awesome @muniz_ri ! was just helping a family member update to the new lollipop and i saw this. gonna do some tinkering with safestrap and try and see if i can see whats breaking it on lollipop.. fingers crossed

muniz_ri said:
Only recommended if your Data backup is from 5.0. Those updating from 4.4 should not restore Data for compatibility reasons.
Click to expand...
Click to collapse
How did it work going 4.4.4 to 5.0?

BeansTown106 said:
awesome @muniz_ri ! was just helping a family member update to the new lollipop and i saw this. gonna do some tinkering with safestrap and try and see if i can see whats breaking it on lollipop.. fingers crossed
Click to expand...
Click to collapse
No worries, good luck with SS.
Also fyi.....there is a guy in the N900V forum that has developed a safestrap replacement called multisystem. He is waiting for 5.0 before releasing and claims it will work on 5.0. If so, it can likely be easily ported to the S5.

Got it. I did see that. I guess it is just that simple. I thought there might be a little more detail needed, but I will give it a shot. Hopefully safestrap comes to lollipop one day to make it a little easier!

mkitchin said:
Got it. I did see that. I guess it is just that simple. I thought there might be a little more detail needed, but I will give it a shot. Hopefully safestrap comes to lollipop one day to make it a little easier!
Click to expand...
Click to collapse
After flashing the ROM you can just reboot, no need to re-flash the OC4 kernel since the new ROM already flashed it.

Does anyone know if the Alarm clock works on silent now? I think they got rid of the interruption settings did they not?

I have run into a problem i can't figure out. When i try to run safestrap it just wont boot into it when i boot from the app. Have tried it many times. Thinking back wasn't safestrap broken when you are on 5.0? I went from kit kat, rooted and did the keep root tutorial to have it in 5.0. Not really sure what to do.

jake20fc said:
I have run into a problem i can't figure out. When i try to run safestrap it just wont boot into it when i boot from the app. Have tried it many times. Thinking back wasn't safestrap broken when you are on 5.0? I went from kit kat, rooted and did the keep root tutorial to have it in 5.0. Not really sure what to do.
Click to expand...
Click to collapse
Safe-strap doesn't work on 5.0. You have to flash G900V_NK2_Stock_Kernel to access it.

ejc1214 said:
Safe-strap doesn't work on 5.0. You have to flash G900V_NK2_Stock_Kernel to access it.
Click to expand...
Click to collapse
Ty. I'm not new to flashing but i was just wondering what the hell i was doing that it wouldn't boot. Appreciate it.

Latest OTA update unable to install - produced "Error" screen on reboot

A few days ago, I received a notification on my N5 for a new system update of size 10.1 MB. When I choose to install the update, the phone reboots as expected, shows the "Google" startup logo, shows a screen that indicates that it is installing the update for a few seconds, and then finally ends at an "Error" screen (please see the attached image).
The phone stays on this screen for quite a while (more than a minute), then finally the device restarts and the system update notification is still present.
I've tried rebooting the phone manually and installing the update again, both when charging and when off the charger, but this has not helped. I've also searched to see if others have been having this problem, but I haven't been able to find anything. Has anyone else been experiencing this issue with the latest update, or are there any suggestions for how I can go about getting the update to install properly?

I would suggest you flash the system.img and boot.img using fastboot. The latest factory image ends in 48i, Google nexus factory image and download that image, extract it and inside is another zip file, in there you'll find the system and boot images.
Sent from my Nexus 9 using XDA Free mobile app

Thank you for your speedy reply! I will do as you've suggested and respond with my results.

I get the same error when trying to update the OTA Update (from LMY48 to LMY48I). Is it possible to install the next update ignoring this one or will I only be able to install it after sucessfully updated this update?

Why don't you just do what jd1639 suggested?
Sent from my Nexus 5 using Tapatalk

So, I'm coming back to admit that I still haven't attempted the solution proposed by jd1639, with the reason being that I don't quite have the time to deal with flashing and clean-wiping my phone, then setting everything up again. I know it's a simple process, but right now I don't want to do anything that could jeopardize my having a working phone. I doubt there's any better option than flashing the latest update, however, so I'm waiting until I have the time and the patience to do so.
I must say that I'm still curious as to why something like this would happen. I'm inclined to assume that it is a problem with my phone in particular, since I haven't been able to find any other complaints about this problem with this particular OTA update (although cj182 seems to be having the same problem as I am). I suppose anything can go wrong with a system update, especially on a Linux-based system, but I would like to figure out why such a small and seemingly inconsequential update would fail to install on my phone when past updates of much larger sizes and complexity seemed to install without issue.
cj182 said:
I get the same error when trying to update the OTA Update (from LMY48 to LMY48I). Is it possible to install the next update ignoring this one or will I only be able to install it after sucessfully updated this update?
Click to expand...
Click to collapse
I must admit that I'm interested in the answer to this question, as well, though my intuition tells me that the answer is no because I would think that Google releases each OTA update assuming that the device is on the latest version of Android up until that point. I do not know if Google releases separate updates that would allow one to "skip" a version in between a previous version and the latest, though I may certainly be incorrect.

TomCatullo said:
So, I'm coming back to admit that I still haven't attempted the solution proposed by jd1639, with the reason being that I don't quite have the time to deal with flashing and clean-wiping my phone, then setting everything up again. I know it's a simple process, but right now I don't want to do anything that could jeopardize my having a working phone. I doubt there's any better option than flashing the latest update, however, so I'm waiting until I have the time and the patience to do so.
I must say that I'm still curious as to why something like this would happen. I'm inclined to assume that it is a problem with my phone in particular, since I haven't been able to find any other complaints about this problem with this particular OTA update (although cj182 seems to be having the same problem as I am). I suppose anything can go wrong with a system update, especially on a Linux-based system, but I would like to figure out why such a small and seemingly inconsequential update would fail to install on my phone when past updates of much larger sizes and complexity seemed to install without issue.
I must admit that I'm interested in the answer to this question, as well, though my intuition tells me that the answer is no because I would think that Google releases each OTA update assuming that the device is on the latest version of Android up until that point. I do not know if Google releases separate updates that would allow one to "skip" a version in between a previous version and the latest, though I may certainly be incorrect.
Click to expand...
Click to collapse
If your bootloader is unlocked just flashing the system and boot images does not wipe your device. If everything goes right there will be no re-setting up required, you will have to re-root if you're rooted but that's just a matter of flashing supersu in a custom recovery.
Sent from my Nexus 5 using XDA Free mobile app

Or try recovery (stock) and find the flash update from cache (might work)
Sent from my LG-D722 using XDA Free mobile app

That doesn't work. The update checks for changes to the system (root, etc.) and needs stock recovery to install.

I'm also having the same exact problem!
jd1639: Are you sure that will not wipe the data?

It doesn't wipe your data... many of us have done it.

jrosado said:
I'm also having the same exact problem!
jd1639: Are you sure that will not wipe the data?
Click to expand...
Click to collapse
It does wipe your data. However,I strongly suggest you backup first in case something goes wrong, that's just good practice.
Sent from my Nexus 9 using XDA Free mobile app

Telyx said:
It doesn't wipe your data... many of us have done it.
Click to expand...
Click to collapse
jd1639 said:
It does wipe your data. However,I strongly suggest you backup first in case something goes wrong, that's just good practice.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Now i'm confused...it wipes or not? I'm referering to just flashing the boot and system files.

jrosado said:
Now i'm confused...it wipes or not? I'm referering to just flashing the boot and system files.
Click to expand...
Click to collapse
Sorry about that, I meant it DOES NOT wipe the device.
Sent from my Nexus 9 using XDA Free mobile app

I'm sorry to say that it wipes all data and applications

jrosado said:
I'm sorry to say that it wipes all data and applications
Click to expand...
Click to collapse
Did you flash just the system.img and boot.img? Just doing that will not wipe your data. I do that with every update. If you flashed other images, userdata.img, then you device will be wiped
Sent from my Nexus 9 using XDA Free mobile app

Only system and boot..don't know why, but it wiped all

jrosado said:
Only system and boot..don't know why, but it wiped all
Click to expand...
Click to collapse
You didn't have to unlock the bootloader did you? That's the only other reason I can think of that would have wiped your device.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
You didn't have to unlock the bootloader did you? That's the only other reason I can think of that would have wiped your device.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, i had to do it..otherwise it would not write the firmware..is there any way to do it without unlock the bootloader?

This is why the first thing you should do when you get a nexus is unlock the bootloader...

How to upgrade to LP 5.01 (Stage Fright Patch) w/o wiping data or reflashing recovery

This is an upgrade pathway that worked well for me in upgrading to 5.0.1 originally from KK as I described in THIS post. All the same thanks go out for the original ideas and guidance to: dottat, Dees Troy, and Darth.
The same method works. Even if you're S-OFF, the trick is following the S-ON instructions...that's it.
Find the latest S-ON RUU and instructions HERE.
The latest TWRP (for the HTC One M8) HERE.
The latest SuperSU per the instructions HERE.
Install the S-on 5.0.1 RUU by whatever method you chose from the link above. I used the fastboot method and it did a great job upgrading the stystem. Most importantly, it did NOT wipe my data. You can also use the htc_fastboot.exe in it's extraction directory for all subsequent fastboot operations [highly recommended]. It will reboot and take at least 5 minutes to update all of your applications. At first, it looks like it hangs on the Verizon splash for a minute or three, then it shows you the upgrade of your applications with a count up. How long it takes depends on how many applications you have and how large they are.
Follow the guides to install TWRP and reinstall SuperSU for root. (step 5) I went to the new TWRP page (step 2) and loaded mine by fastboot, then used the new TWRP to flash SuperSU as described.
If you haven't taken the OTA, that should take care of the upgrade nag screens and keep your data intact. If you have, keep reading.
REMINDER: to reflash any tweaks. My favorite package is HERE at the bottom of the links list. It has just about everything I like.
ADDITIONAL INFO FROM dotatt
You also would be wise to note if the user was already getting nagged for the ota they will still be nagged about it even after upgrading this way. Couple more steps needed
Click to expand...
Click to collapse
AND HIS DESCRIPTION VIA PM
If the user doesn't download the OTA and defer it they might be able to get away with it. Once the file is downloaded (and it goes in /cache) the user will need to wipe cache to delete the actual file as well as go into app manager and clear data on the htcdm app. When they enter the software update screen again it should check and show no updates available instead of asking when to install the deferred update.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you need to get rid of the nag screen, the update files, and clear htcdm data, you may be able to use THIS (M8vzw OTA Killer updated for Lollipop) tool.

I have a problem and need help, maybe you can help. I was stock but was s-off and took the stage fright update and phone did all the update and when the phone booted it did not go past the Verizon bootup screen, can anybody help me with this? Thanks you.
Sent from my Nexus 6 using Tapatalk

luvtorev01 said:
I have a problem and need help, maybe you can help. I was stock but was s-off and took the stage fright update and phone did all the update and when the phone booted it did not go past the Verizon bootup screen, can anybody help me with this? Thanks you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I answered your other post. Please only post for help in one thread. Thanks.
Sent from my Nexus 6 using Tapatalk

Thanks for keeping your eyes open, dottat. Good reminder that he'll have to reflash TWRP and SuperSU though. And, he'll have to reflash any tweaks.

homers1 said:
Thanks for keeping your eyes open, dottat. Good reminder that he'll have to reflash TWRP and SuperSU though. And, he'll have to reflash any tweaks.
Click to expand...
Click to collapse
You also would be wise to note if the user was already getting nagged for the ota they will still be nagged about it even after upgrading this way. Couple more steps needed ?
Sent from my Nexus 6 using Tapatalk