No, you'll need to kdz to stock M, ensure Enable OEM Bootloader unlock is checked, and then reboot into bootloader mode to 1) do OEM unlock and 2) boot into TWRP in order to permanently install TWRP. It's pretty simple. I think I spent a grand total of 10-15 minutes setting it up: http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Same as I posted above. If you're not yet on M, you'll need to flash the M KDZ (or OTA update to M, if you're still on stock), unlock bootloader and re-install TWRP to flash any M ROM.
Lol, this thread only has one page, and the answer is right above your post.
Wow lol you just repeated the same question that was already answered literally above your post. Like you didn't even read. If your on any 5.1 ROM you have to flash the stock mm ota update first before flashing any mm ROM. After flashing the stock mm always make sure OEM unlock is enabled. Unlock your bootloader,flash twrp recovery.
As with any non-stock camera app, I'm sure there is a bit of a hit to quality, since they can't access LG's closed-source camera, but honestly, I can't tell a huge quality difference myself. The Snap camera used in CM (as well as Bliss, which I'm currently running with Llama Sweet Kernel with some tweaks - I highly recommend this kernel so far for CM or Bliss, or just about any other AOSP-ish ROM) has taken some big steps forward since CM was first available for the G4. (Full disclosure, some people have had issues with the flash going at the wrong time, causing over/underexposed pics, but I haven't seen it on mine. Others have also reported a bit of a hit to video (some lagginess) but I haven't taken any video yet to confirm or deny.)
Thank you very much for your reply. I suppose I'll stick with a stick ROM. Camera and video quality are very important to me. I take a lot of pictures and videos of my kids.
Honestly, and this is always my advice, I'd say go ahead and try it out. Just do a backup beforehand, and test out the camera first thing after flashing. If it's up to par, great! If not, 5 minutes later you're back to stock. Like I said, I haven't seen any of the issues a few others are reporting so far. Of course it's totally up to you. Just don't want you to deprive yourself of AOSP for something that may not effect you at all.
I definitely have been toying with the idea of it. I'm a huge AOSP fan. I may take your advice sooner or later
Hello. I when I click on download, it crashes. I get "unfortunately, the process android.process.media has stopped." So far that is the only app behaving like that. Someone else can confirm this or is just me?. I even reset whole system and same issue.
