Database Info

[Q] Flashing Mods

Ok yes I am a noob at this and after much searching I have not found an answer to my question so I decided to make a thread.
Can anyone explain to me the process of flashing mods to your ROM? More specifically do you have to wipe data and everything to flash a mod to your ROM or can you just flash it on top of your ROM and keep it moving ?

To flash a mod usually you download a file in. Zip form. You then flash it in recovery the same way you flash a rom. (Install zip) make sure you know where the file is external or internal. Wiping anything should not be necessary unless the dev specifies. And you flash it at anytime after the rom has been installed. Check versions and make sure its compatible. Hope this helps
Sent from my GT-P7510 using xda premium

roughneckboren said:
To flash a mod usually you download a file in. Zip form. You then flash it in recovery the same way you flash a rom. (Install zip) make sure you know where the file is external or internal. Wiping anything should not be necessary unless the dev specifies.
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Thank you so much ! I have been searching for an answer for weeks now.

No problem man.
Sent from my GT-P7510 using xda premium

Beast to wipe cache and Dalvik immediately before flashing the zip.
But, most important (other than reading the flash instructions) -- Nandroid BACKUP -- with CWM Recovery prior to flash so you can restore your ROM if you don't like, have issues etc with the mod just flashed.
Sent from my GT-I9100 using xda premium

Thanks
Sent from my PC36100 using XDA

UpInTheAir said:
Beast to wipe cache and Dalvik immediately before flashing the zip.
But, most important (other than reading the flash instructions) -- Nandroid BACKUP -- with CWM Recovery prior to flash so you can restore your ROM if you don't like, have issues etc with the mod just flashed.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
U don't need to wipe data or cache if ur just flashing a mod. Those are only needed if ur flashing a rom

QuantumFoam said:
U don't need to wipe data or cache if ur just flashing a mod. Those are only needed if ur flashing a rom
Click to expand...
Click to collapse
Sorry, you are incorrect. Flashing certain mods and apps you should most definitely.
This guy explains it simply, and better than I could put it:
http://androidforums.com/4287822-post4.html
Sent from my GT-P6810 using XDA Premium HD app

UpInTheAir said:
Sorry, you are incorrect. Flashing certain mods and apps you should most definitely.
This guy explains it simply, and better than I could put it:
http://androidforums.com/4287822-post4.html
Sent from my GT-P6810 using XDA Premium HD app
Click to expand...
Click to collapse
I stand corrected

Recovery
Most mods (if not all) will require root access and a custom recovery tool like CWM and 4EXT. To get the recovery tool the phone will need S-Off mode enabled (Security Off). If you are on 2.2, S-Off wasn;t around then so you shouldn't have that problem, but startgin with 2.3 it was introduced, so you will need to get S-Off in order to get the recovery tool installed.
Getting into Recovery mode is another thing that depends on your phone. My Samsung uses Power + Volup and Vol Down togheter, then Vol Up plus Vol Down after it turns on forseverl aseconds. I have an HTC that is the same, but just with Vol down (no Vol up required). Of course to do anything there you need the S-Off plus root plus custom recovery tool.
You can also get a USB driver and adb (plus dll) toolkit to access the phone via yoru USB cable (this requires turning on USB debugging under phone settings). From there you can get into recovery by issuing commands in DOS.
> adb reboot bootloader
You can even flash some img files (mods) from the command line also ...
> fastboot flash radio radio.img
and then reboot the phone to normal
> fastboot reboot

Horrible clarifying question

Ok everyone. Horrible question I know but here goes. I want to be right so please excuse a question I am sure has been asked many many times.
Situational info:
HTC one s s4 boot loader 1.06
No regular PC access.
Extensive knowledge and experience rooting and flashing G1 and G2X
Goal: unlock boot loader and open root access to enable flashing of roms via recovery while remaining PC independent
Steps I plan to execute:
1) unlock bootloader on htcdev site
2)grant root access following instructions(or all in one tool - your input here is appreciated)
3)instal CWM
4)download rom and kernel of choice
5) boot into boot loader, enter recovery, wipe, flash, boot
If I have any of this wrong please advise.
Again I apologize for the redundancy of this thread. Mods please delete after my process is verified to keep board clean. I only have one crack at this (PC access extremely limited) and I want to get it right.
Sent from my HTC VLE_U using xda app-developers app

Looks correct. First install HTC drivers & HTC Sync software (in order to unlock bootloader, I believe HTCdev site will instruct this).
I recommend (as well as many others, I believe) TWRP over CWM. ESPECIALLY if you do not have computer access. The 1S does not have S-OFF, which makes it very hard for us to flash kernels & radios. Well, not hard, but you need a PC if using CWM. Using TWRP, you can usually flash these things from your device. So definitely use TWRP for your situation.

You can't root without a PC. It's impossible. You are required to get a token that you can only get from a command prompt on the computer. Sorry, but you're out of luck. But when/if you get a PC the steps you wrote were mostly right
1) Correct
2) FLASH RECOVERY (use TWRP, CWM is not good on this device)
3) Then root by flashing a SuperSU zip in RECOVERY (that's why #2 and #2 are switched)
4) Yep
5) Always always always BACKUP YOUR ROM. Then wipe system, data, cache, and dalvik cache. then flash the ROM. If you have extra time you should fastboot your kernel if your hboot is below 1.13 (meaning 1.13 is NOT able to flash the kernel.)
Hope I helped. If I did press thanks

OP did mention that he will have limited PC access to perform the unlock process, so he will be able to do it initially.
Here's the link for TWRP: http://forum.xda-developers.com/showthread.php?t=1677670 (make sure to use this one, the other link in the forums is for the S3 processor)

Ok so I can flash recovery as soon as I unlock boot loader and use twrp check.
The supersu, that's just a zip to flash in recovery to grant root access?
What is fasbooting kernel?
Thanks guys, appreciate the help. Will be performing this within the next two hours. Just trying to be ready so it goes off smooth. Once I get this done I need to do my friend's G2(condition for PC time lol)
Sent from my HTC VLE_U using xda app-developers app

TWRP is a recovery. You will use that instead of CWM, not in addition to.
If you're going to flash a custom rom then you don't have to worry about rooting first. The rom will be rooted already.
Fastbooting kernel is a method of using a pc + command prompt to flash the kernel on your phone. Because HTC hasn't completely "unlocked" the 1S, we need workarounds like that to do certain things. However. TWRP will allow you to flash most things, including most kernels. If you use TWRP and yout hboot is low (which yours is) you shouldn't have too many issues.

Brief note here, I won't have adb access on this pc....will I be able to flash twrp without adb? I see there is an app in the market for it but seems to require root first. Thanks again for the input
Also, downloaded roms and kernels will need to reside on my SD card. This will become an issue if pre install format/wipe kills my SD card. Please advise. Roms and kernels will need to always be installed from SD card via recovery
Sent from my HTC VLE_U using xda app-developers app

briandresstoyota said:
Brief note here, I won't have adb access on this pc....will I be able to flash twrp without adb? I see there is an app in the market for it but seems to require root first. Thanks again for the input
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
You need adb access. That's how you flash recovery, using command prompt on the PC.
Not sure about this app, what's the name of it? To my knowledge you need adb to flash recovery on this phone.
If this isn't possible, you will still be able to root, just not have a custom recovery or flash roms. I don't believe you need to unlock the bootloader to root...not 100% sure but I believe you can root without it, which should be pretty simple.

On twrp website there is an option to install recovery via an app called goomanager. In the app store goo manager states root required. Should I revise my steps to this:
1)unlock bl
2) root using supersu img
3)goomanager install twrp
4)use twrp to flash roms and kernels
I would really love to avoid flashing radios btw. I just feel like it might be safer to let it be. Radios always made me nervous on previous devices
Sent from my HTC VLE_U using xda app-developers app

You could download goo manager from the play store then install open recovery script from menu..then flash the SuperSU zip. You wouldn't require ADB then.

invasion2 said:
You could download goo manager from the play store then install open recovery script from menu..then flash the SuperSU zip. You wouldn't require ADB then.
Click to expand...
Click to collapse
This is correct. I forgot about goomanager.
As for the radios, there isn't really too much risk on the 1S. I remember it was always a scary issue on the HD2 because of EU vs. US radios, which could cause a brick. On the 1S you can flash EU radios with no prob. Actually, some people report better performance in the US with EU radio. So yeah, don't be worried about it, it's pretty safe on this device - with normal precautions and proper flashing of course.
HOWEVER:
Make sure to only use S4 radios/roms on S4 processor. There is an S3 version of the 1S as well, and you cannot switch any roms/kernels/radios between the two.

Hey hey!!! Made it work. Flashed aokp. Running sooooo amazing. Anyone know how to make home screen and app store rotate?
Sent from my HTC One S using xda app-developers app

Can't make home screen. But turn on auto-rotate in settings and it should rotate the store.

So I am a happy rooted owner. No sound in music apps or YouTube.
Sent from my HTC One S using xda app-developers app

Soo started with aokp then cm10. No sound on either except in power amp. So weird
Sent from my HTC One S using xda app-developers app

Try flashing official CM10
http://get.cm/?device=ville
If you prefer a stock look try TrickDroid or Viper
Sent from my HTC One S using xda app-developers app

Actually flashed most recent cm10 nightly after my go with AOKP. Still no dice. I've posted the issue on both ROM dev forums so hopefully it will get resolved. I feel like it is operator error but I have flashed each ROM twice with a full wipe before each install. I understand the process for flashing so I hope its something small I missed.
Sent from my HTC One S using xda app-developers app

briandresstoyota said:
Actually flashed most recent cm10 nightly after my go with AOKP. Still no dice. I've posted the issue on both ROM dev forums so hopefully it will get resolved. I feel like it is operator error but I have flashed each ROM twice with a full wipe before each install. I understand the process for flashing so I hope its something small I missed.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Do you have no sound from the speaker or do you have headphones or something plugged in?

Strange TWRP problem, no OS detected etc. Boots fine to stock

I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.

Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2

Xx

BadUsername said:
Try to use cwm or philz and see if you have the same issue.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!

Smogon said:
Can you install a different custom recovery over one using the causal applet? I was planning on trying to reinstall TWRP but I wasn't sure if I had to do it a certain way like through odin or Using the unified tool kit?
Thanks for the help so far!
Click to expand...
Click to collapse
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Then check and see if you're getting a similar error message.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
No.
Download latest philz touch recovery d2lte zip, then flash it in recovery, then reboot recovery.
Click to expand...
Click to collapse
I can't, recovery doesn't detect my internal or external memory. That's my main issue.

Smogon said:
I can't, recovery doesn't detect my internal or external memory. That's my main issue.
Click to expand...
Click to collapse
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
OK.
Then download the Odin version and flash through that. Then boot the phone into recovery.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll try the second option, Thanks!

BadUsername said:
OK.
Or download ez recovery, and the latest cwm image file, and flash through that from your rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried CWM and the stock recovery through EZ, both gave the same error as TWRP, unable to mount /
I'm really confused as to whats wrong. At this point I don't care if I get stuck with the OTA 4.3, but I don't want to try to update it with the recovery still not reading either my SD cards.
Any Ideas?

Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app

Smogon said:
I ran the causal root applet on a new SG3 on 4.1.2. Ran root, the unlock script and installed TWRP. Booted into recovery and I got the error for a locked bootloader. I used download mode to get back to the stock rom and then used E-Z unlock to unlock the bootloader. Was able to boot into recovery this time but TWRP read internal and external memory as 0mb, unable to make a backup, and gave a no OS error when went to reboot. I updated TWRP with TWRP manager but the problems are still persistent. Phone boots fine and reboots fine at the moment.
I'm not sure what to do now though. I'm at the point were I don't care if I get stuck with the OTA update but I'm afraid that will brick the phone. I'm not sure what went wrong with TWRP, since this is the second S3 I've rooted.
Any sugestions? I'm afraid to use odin or try anything else since the phone currently works fine. But I'd prefer to not have to sleep in fear it might force the OTA update while I'm asleep and wake up to a bricked phone.
I tried searching, the best I could find is that newer versions of TWRP can't read the memory on a 4.1.2 rom, but the problems were there when I originally started with the recommended version.
Thanks for any help anyone can give.
Click to expand...
Click to collapse
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.

xevildoerxx said:
by any chance did u try to setup dualboot? I have a similar issue where nothing gets mounted and o mb for storage, .only receovery i get to work is cwm. im pretty sure its a partition issue but idk. i tried flashing pit files for my phone but so far the issue remains.
Click to expand...
Click to collapse
No I just used the causal tool.
dpeeps74 said:
Are you sure of your phone model? I believe it puts it on the screen in download mode and also on a sticker under the battery. I'm mostly curious because you mention that this is a new phone with 4.1.2. Are you trying older versions of cwm as well?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm pretty sure, has all the verizon bloat and logos, also I'm pretty sure the causal applet bricks the international ones. I don't remember the version of twrp that the causal script flashed, but I tried that one, the most recent one, and 2.5 i think from EZ recovery. The stock recovery from EZ has the same issue now though which is what really confuses me. at the moment I have root dissabled and the bootloader is locked and its back with the stock recovery, it still says custom when i reboot the phone though.

New m8 wants to update

I just got my m8 and want to s-off but I'm traveling and won't be able to figure that out until I'm back on my pc next week. The update keeps prompting me to take it. Is it safe to do so? Sorry if this was already answered trying to figure out the best way to browse with tapatalk.
I don't have root or anything yet...
Sent from my HTC6525LVW using Tapatalk

I used Firewater's method for permanent root, s-off and custom recovery. If I allow my phone to update will I mess things up or lose root?

Same boat here... s-off, permanent root, TWRP
The update to 1.55 downloaded but when I tried to let it install it just rebooted my phone into TWRP and that was it. Rebooted back to system and I'm still on the 1.12.605.11 software. Checking software update status shows "Result: Update Failed,410"

N00bs. Lol. You need a stock recovery to flash an OTA. Also, I am s-off and I had a flashback to a stock recovery to flash the OTA . Everything is still fine and then I flashed back to a custom recovery no problem
Sent from my HTC One M8

Totally a noob here, How do you flash to a stock recovery?
Sent from my HTC6525LVW using Tapatalk

You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
http://www.megafileupload.com/en/file/520717/stockrecovery-img.html
There are also videos on YouTube on flashing recoveries to the m8 if you need more help.
Sent from my HTC6525LVW using Tapatalk

Justintoxicated said:
I just got my m8 and want to s-off but I'm traveling and won't be able to figure that out until I'm back on my pc next week. The update keeps prompting me to take it. Is it safe to do so? Sorry if this was already answered trying to figure out the best way to browse with tapatalk.
I don't have root or anything yet...
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
You can install the update, and when you have the chance you can s-off using the weaksauce/supersu/firewater method. I picked up a new M8 a couple nights ago and took the update, and afterwards did the temproot/firewater method and it worked just fine. Hope this helps.

I flashed stock recovery and tried the OTA and it failed twice. I can't seem to get it on my phone through any of the methods for some reason.

In order to install update, you need to have STOCK recovery and STOCK Rom....NOT debloated or with mods....STOCK.
Again, you need STOCK recovery using a STOCK Rom.
If you have modified the system in anyway, it WONT work until you put it back to STOCK.
Sent from my HTC6525LVW using xda app-developers app

^you can have bloatware frozen and it'll work, just can't be removed.
Sent from my HTC6525LVW

dadams312 said:
I flashed stock recovery and tried the OTA and it failed twice. I can't seem to get it on my phone through any of the methods for some reason.
Click to expand...
Click to collapse
z-man79 said:
Totally a noob here, How do you flash to a stock recovery?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
KnightDavid said:
Same boat here... s-off, permanent root, TWRP
The update to 1.55 downloaded but when I tried to let it install it just rebooted my phone into TWRP and that was it. Rebooted back to system and I'm still on the 1.12.605.11 software. Checking software update status shows "Result: Update Failed,410"
Click to expand...
Click to collapse
z-man79 said:
I used Firewater's method for permanent root, s-off and custom recovery. If I allow my phone to update will I mess things up or lose root?
Click to expand...
Click to collapse
No need to take ota. Ota us our enemy. Lol. The ota has been pulled an you can simply flash the firmware an that's half of the ota an then flash a stock Rom based off 1.55 or install the backup that was posted of a pure stock 1.55 Rom. After those 2 things you will have the full ota. New radios everything.. flashing a stock recovery taking ota flashing back is not needed.
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Thanks guys it was annoying having that update keep popping up and no real computer to lookup info or soff. As for getting updates after roming the phone usually just wait for authors to incorporate the updates. But I did not realize you can't have two recoveries like you can on Motorola phones which is good to know.
Sent from my HTC6525LVW using Tapatalk

New to android here.
I rooted the device with WeakSauce and use Firewater for S-Off. I didn't flash any custom recoveries. I did freeze some apps with Titanium Backup. If I do the OTA, 1) will it work? and 2) will it remove my root and/or s-off?

NoFanboy said:
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
megafileupload.com/en/file/520717/stockrecovery-img.html
Click to expand...
Click to collapse
For clarification, after flashing the stockrecovery.img you posted and installing the update, there should be no problem flashing back to CWM recovery after the fact?
Thank you for your help and your time!

skivvies said:
For clarification, after flashing the stockrecovery.img you posted and installing the update, there should be no problem flashing back to CWM recovery after the fact?
Thank you for your help and your time!
Click to expand...
Click to collapse
Nope there will be no problem.
Sent from my HTC6525LVW using Tapatalk

richii0207 said:
In order to install update, you need to have STOCK recovery and STOCK Rom....NOT debloated or with mods....STOCK.
Again, you need STOCK recovery using a STOCK Rom.
If you have modified the system in anyway, it WONT work until you put it back to STOCK.
Sent from my HTC6525LVW using xda app-developers app
Click to expand...
Click to collapse
All your big words confuse me...will it work with custom rom's and recoveries?

I don't remember ever having to have stock recovery and stock rom for my old DNA to take an update. Normally devs would update their rom with the updates and all we had to do was fastboot flash the new radio.

NoFanboy said:
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
http://www.megafileupload.com/en/file/520717/stockrecovery-img.html
There are also videos on YouTube on flashing recoveries to the m8 if you need more help.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So I flash the file you linked to, thank you but when I try to get into recovery I get a red triangle with an exclamation point in it. Seemed pretty straight forward.

sfreemanoh said:
All your big words confuse me...will it work with custom rom's and recoveries?
Click to expand...
Click to collapse
Lol, I had to. I just know someone is going to start a thread saying "update won't work, it just boots into twrp"
Sent from my HTC6525LVW using xda app-developers app

z-man79 said:
So I flash the file you linked to, thank you but when I try to get into recovery I get a red triangle with an exclamation point in it. Seemed pretty straight forward.
Click to expand...
Click to collapse
Hold the volume up button and pressed the power button to get to the recovery menu.

Boot recovery.img from phone

Is it possible to boot a recovery image from the phone without flashing? If not is it ok to reflash backups of stock recovery? Tnx

and313 said:
Is it possible to boot a recovery image from the phone without flashing? If not is it ok to reflash backups of stock recovery? Tnx
Click to expand...
Click to collapse
It is possible via android sdk. You can use command: fastboot boot twrp.img
where twrp.img is the name of the recovery that you downloaded and not twrp.img

Alexandar92zr said:
It is possible via android sdk. You can use command: fastboot boot twrp.img
where twrp.img is the name of the recovery that you downloaded and not twrp.img
Click to expand...
Click to collapse
Yes i know but i would like to do it from the phone... There are tons of flash recovery apps but no boot recovery apps

ROM manager used to do it years ago until people got into trouble with it and it was removed.
If you intend on flashing things AMD backing up, flash a recovery. If you're not willing to flash a recovery, don't modify your phone
Sent from my Nexus 5 using Tapatalk

and313 said:
Yes i know but i would like to do it from the phone... There are tons of flash recovery apps but no boot recovery apps
Click to expand...
Click to collapse
Try flashify

AndreIrawan97 said:
Try flashify
Click to expand...
Click to collapse
That flashes recovery. Clue is in the name.
Sent from my Nexus 5 using Tapatalk

rootSU said:
ROM manager used to do it years ago until people got into trouble with it and it was removed.
If you intend on flashing things AMD backing up, flash a recovery. If you're not willing to flash a recovery, don't modify your phone
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The problem with flashing is that you loose the ota update ability. That's why i would like to keep the stock recovery and just boot into cwm when i need it... But i guess i can restore the stock recovery via flashify before the ota is being installed so thats a solution... I just dont like flashing this stuff via apps

and313 said:
The problem with flashing is that you loose the ota update ability. That's why i would like to keep the stock recovery and just boot into cwm when i need it... But i guess i can restore the stock recovery via flashify before the ota is being installed so thats a solution... I just dont like flashing this stuff via apps
Click to expand...
Click to collapse
1) you do not lose OTA update ability with custom recovery. Read "OTA help-desk" available via my signature
2] what's the big deal about OTA? Its the worst way of updating available to everyone. Why bother? If you rely on OTA, remain unrooted, unmodified. Rooting is not for you.
Sent from my Nexus 5 using Tapatalk

Ugh lol OK, so worried about the ota? No worries, flash whatever recovery you want twrp,cwm,philz whatever floats your boat. Then when your ota comes out use Rashr to reflash stock recovery so you can update(you have to be on stock obviously).
I've done this numerous times, works every time.
Sent from my Nexus 5 using XDA Free mobile app

todorcim said:
Ugh lol OK, so worried about the ota? No worries, flash whatever recovery you want twrp,cwm,philz whatever floats your boat. Then when your ota comes out use Rashr to reflash stock recovery so you can update(you have to be on stock obviously).
I've done this numerous times, works every time.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
One of the problems with OTA is the slow delivery and partial nature.
If I wasn't rooted, i'd always update using factory images. But since I am, the best way is for flash a pre-rooted stock ROM via recovery. They're usually available within an hour of the factory image becoming available
Sent from my Nexus 5 using Tapatalk

rootSU said:
One of the problems with OTA is the slow delivery and partial nature.
If I wasn't rooted, i'd always update using factory images. But since I am, the best way is for flash a pre-rooted stock ROM via recovery. They're usually available within an hour of the factory image becoming available
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Agreed 100%, I normally stay rooted,this most recent preview though I'm staying stock. After running L for the last couple months its hard to go back to KitKat(I've tried several times). I have no intention of flashing another rom atm, I'll worry about root after the 3rd.
As for buddy worrying about the ota, really you have two choices.
#1 root and flash a recovery then wait for someone to post a root stock ROM
#2 wait for the ota
The only real benefit I see in waiting for the ota is you will probably get to keep all your apps on your phone. Me personally? I'd just fastboot the preview and wait till the 3rd.
Materialized From The DarkSide