Database Users

Can I update to 4.2.2?

Howdy,
So I'm considering updating my trusty XT907 from 4.1.2 up to the new update 4.2.2.
I"m running stock ROM unlocked with Motochopper, using Safestrap 3.12. Removed a mass of stuff, been running it steamlined and smooth. I'd like to update though from what I've read. I've always ran ROMs for years now, but at this point in my busy schedule I can't keep up with the development, and I"m outta the loop. The last ROM I ran on the razr m before stock was the Energy ROM.
My question is, now with bootloader unlocked am I safe to update to 4.2.2 and keep root? Innocent question, hopefully.
Thank you -

blksheep said:
Howdy,
So I'm considering updating my trusty XT907 from 4.1.2 up to the new update 4.2.2.
I"m running stock ROM unlocked with Motochopper, using Safestrap 3.12. Removed a mass of stuff, been running it steamlined and smooth. I'd like to update though from what I've read. I've always ran ROMs for years now, but at this point in my busy schedule I can't keep up with the development, and I"m outta the loop. The last ROM I ran on the razr m before stock was the Energy ROM.
My question is, now with bootloader unlocked am I safe to update to 4.2.2 and keep root? Innocent question, hopefully.
Thank you -
Click to expand...
Click to collapse
With an unlocked bootloader, you can flash TWRP and install CM10.1 from http://androidhosting.org/Devs/Dhacker29
Sent from my XT907 using xda premium

I see. But I"m curious about keeping the stock ROM.
Leraeniesh said:
With an unlocked bootloader, you can flash TWRP and install CM10.1 from http://androidhosting.org/Devs/Dhacker29
Sent from my XT907 using xda premium
Click to expand...
Click to collapse

blksheep said:
I see. But I"m curious about keeping the stock ROM.
Click to expand...
Click to collapse
from my understanding, CM10.1 by dhacker is essentially stock. all others are custom variations.

blksheep said:
I see. But I"m curious about keeping the stock ROM.
Click to expand...
Click to collapse
Stock has only gone as far as 4.1.2. If you want 4.2.2, you need to run AOSP.
Sent from my Droid RAZR M using xda app-developers app

RikRong said:
Stock has only gone as far as 4.1.2. If you want 4.2.2, you need to run AOSP.
Sent from my Droid RAZR M using xda app-developers app
Click to expand...
Click to collapse
Many thanks for the tips! However, this last one made me a little more confused - are you saying to be rooted with 4.2.2 I need to run AOSP roms?
Apologies but I just upgraded to the razr M after running my beloved Droid Incredible with CM10 forever -- absolutely loving it but entirely confused by the rooting options.
My ideal is to have the 4.2.2 update, and to still be unlocked and rooted, with no additional rom's, and with whichever recovery is needed to achieve this. Then I'll start having a look at dhacker's and the Orion looks good too. But I just want the stock 4.2.2 with root access first - if possible.
Many thanks for the clarity --

blksheep said:
Many thanks for the tips! However, this last one made me a little more confused - are you saying to be rooted with 4.2.2 I need to run AOSP roms?
Apologies but I just upgraded to the razr M after running my beloved Droid Incredible with CM10 forever -- absolutely loving it but entirely confused by the rooting options.
My ideal is to have the 4.2.2 update, and to still be unlocked and rooted, with no additional rom's, and with whichever recovery is needed to achieve this. Then I'll start having a look at dhacker's and the Orion looks good too. But I just want the stock 4.2.2 with root access first - if possible.
Many thanks for the clarity --
Click to expand...
Click to collapse
if you want to get to 4.2.2, you'll need root access and an unlocked bootloader. stock 4.2.2 is AOSP (it's available in the development section).
the latest update (from what I have read) is NOT 4.2.2 update - I believe is to lock the bootloader. so folks are recommending to NOT accept the update.
I would advise to root, unlock, install TWRP. From there, you can choose your flavor of ROM (keeping in mind that 4.2.2 has not been officially released for the M).

blksheep said:
Many thanks for the tips! However, this last one made me a little more confused - are you saying to be rooted with 4.2.2 I need to run AOSP roms?
Apologies but I just upgraded to the razr M after running my beloved Droid Incredible with CM10 forever -- absolutely loving it but entirely confused by the rooting options.
My ideal is to have the 4.2.2 update, and to still be unlocked and rooted, with no additional rom's, and with whichever recovery is needed to achieve this. Then I'll start having a look at dhacker's and the Orion looks good too. But I just want the stock 4.2.2 with root access first - if possible.
Many thanks for the clarity --
Click to expand...
Click to collapse
Sorry, I confused things a little, and JCO's post wasn't very clear either.
If want you to run 4.2.2, you need to run an aftermarket ROM. The M has only been updated to 4.1.2. So, you won't find a stock based ROM that's 4.2.2. JCO refers to CM10.1 as being "stock", but it's not. It's the most basic AOSP ROM. As a comparison, the M's stock ROM is Motoblur based.
Sent from my Droid RAZR M using xda app-developers app

RikRong said:
Sorry, I confused things a little, and JCO's post wasn't very clear either.
If want you to run 4.2.2, you need to run an aftermarket ROM. The M has only been updated to 4.1.2. So, you won't find a stock based ROM that's 4.2.2. JCO refers to CM10.1 as being "stock", but it's not. It's the most basic AOSP ROM. As a comparison, the M's stock ROM is Motoblur based.
Sent from my Droid RAZR M using xda app-developers app
Click to expand...
Click to collapse
well, CM10.1 is the closest to stock (appearance-wise) of all the after market 4.2.2 ROMs available (to my understanding, there is no themeing on it). but I think there a few tweaks in it (hence AOSP).

jco23 said:
well, CM10.1 is the closest to stock (appearance-wise) of all the after market 4.2.2 ROMs available (to my understanding, there is no themeing on it). but I think there a few tweaks in it (hence AOSP).
Click to expand...
Click to collapse
Yeah, CM10.1 is pretty bone stock. I just wanted to make sure there was no confusion with the term "stock." I read our posts, and it would've made a lot of people crawl into the corner, crying.

Excellent, many thanks! That was confusing me also - seeing an update available for my xt097 but reading that 4.2.2 is not available for the razor m - I was wondering what the update was.
I'll be flashing to TWRP tonight - cheers again -hopefully no issues flashing over safestrap. That was neat tho - being able to pick between ROMs to run.

If your already unlocked you never really loose root ever
And the latest verzion update breaks the root method and won't let you unlock if your still locked it doest relock you I think that's impossible
Sent from my XT907 using Tapatalk 2

Unlocked Bootlader/ safe strap Question????

OK so I have no clue really want safestrap is really. I've only had phones that I could unlock my bootloader.
I guess my questions are is how much different is safestrap vs unlocked bootloader and did Verizon/Samsung lock this thing down to the point we can't unlock this thing.?
I just bought this phone on Verizon edge and had no knowledge about this thing being locked down.

Simple search will help.
Safe strap allows you to Flash stock ROMs and stock kernels. It is not a bootloader bypass. You cannot have recovery at this time. The chance of an actual bootloader unlock and/or recovery is slim.
We currently do have root.
If you want to do anything other than flash stock based ROMs and kernels (when SS is available, which is likely soon), then you should use a different device or get the Dev edition when it comes out.
You should do more research before putting that much money on a device down. I want the Note3 very much, but I much prefer a device with more flexibility, even if it isn't as badass.

I've had safe strap on my bionic and flashed asop ...but why would anyone on this device want asop??? ...that would not make a lot of..."touchwiz" lol.

Thanks for the reply. Yes your correct but no need to be an douche. Yes search answers questions but people who have used safestrap can sometimes provide better answers. This is the q&a section so that means you can ask questions. Anyways thanks for part of your reply.
Sent from my SM-N900V using xda app-developers app

jprovan1 said:
Thanks for the reply. Yes your correct but no need to be an douche. Yes search answers questions but people who have used safestrap can sometimes provide better answers. This is the q&a section so that means you can ask questions. Anyways thanks for part of your reply.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I hope that was for the jerk and not the joke.....

Was for the jerk. I liked the joke
Sent from my SM-N900V using xda app-developers app

xdadevnube said:
Simple search will help.
Safe strap allows you to Flash stock ROMs and stock kernels. It is not a bootloader bypass. You cannot have recovery at this time. The chance of an actual bootloader unlock and/or recovery is slim.
We currently do have root.
If you want to do anything other than flash stock based ROMs and kernels (when SS is available, which is likely soon), then you should use a different device or get the Dev edition when it comes out.
You should do more research before putting that much money on a device down. I want the Note3 very much, but I much prefer a device with more flexibility, even if it isn't as badass.
Click to expand...
Click to collapse
This is wrong. Safestrap is a bootstrap recovery. It IS a "bootloader bypass" of sorts. Once everything is squared away, safestrap WILL allow flashing of non-stock ROMs and the execution of Kexec kernels. We will have access to almost everything available with an unlocked bootloader, except it will require room on our internal storage for the ROM files.

Banggugyangu said:
This is wrong. Safestrap is a bootstrap recovery. It IS a "bootloader bypass" of sorts. Once everything is squared away, safestrap WILL allow flashing of non-stock ROMs and the execution of Kexec kernels. We will have access to almost everything available with an unlocked bootloader, except it will require room on our internal storage for the ROM files.
Click to expand...
Click to collapse
AFAIK, it will not allow kexec, as that is a different exploit. Also, it cannot modify aboot. So you will not be able to install AOSP ROMs or anything but a modified stock kernel. Believe me, I would love to be wrong.

xdadevnube said:
AFAIK, it will not allow kexec, as that is a different exploit. Also, it cannot modify aboot. So you will not be able to install AOSP ROMs or anything but a modified stock kernel. Believe me, I would love to be wrong.
Click to expand...
Click to collapse
Hashcode has implemented kexec into nearly every device's safestrap. Also, AOSP is still possible with the stock kernel. You simply have to incorporate certain parts of the stock ROM. I did all of this on the Droid Bionic. I had an AOSP ROM before safestrap was even created. It had a couple Blur elements that were very minor, but required.

Do we loose safestrap if we take OTA upgrade to Kitkat (when it's available)?

Banggugyangu said:
Hashcode has implemented kexec into nearly every device's safestrap. Also, AOSP is still possible with the stock kernel. You simply have to incorporate certain parts of the stock ROM. I did all of this on the Droid Bionic. I had an AOSP ROM before safestrap was even created. It had a couple Blur elements that were very minor, but required.
Click to expand...
Click to collapse
I was thinking of the S4 that doesn't have kexec and cannot flash AOSP. It is reasonable to assume that the N3 could get kexec even although the S4 doesn't have it.
SS is not bootloader bypass. Many benefits of an unlocked bootloader will not be realized with SS. However, it should be a decent option for at least getting some ROMs. With kexec, then most people will be happy.

xdadevnube said:
I was thinking of the S4 that doesn't have kexec and cannot flash AOSP. It is reasonable to assume that the N3 could get kexec even although the S4 doesn't have it.
SS is not bootloader bypass. Many benefits of an unlocked bootloader will not be realized with SS. However, it should be a decent option for at least getting some ROMs. With kexec, then most people will be happy.
Click to expand...
Click to collapse
There is a huge difference when Hashcode has the phone in question. It's my understanding that this is the first Samsung phone he has had.

So he's stated that he plans to add kexec? That would be [email protected]$$.
Sent from my SM-N900V using Tapatalk

[Q] Who doesn't Loki work on MF3?

Hello everyone,
So, I've been looking into the status of unlocking the bootloader for MF3 updates (I downloaded it and read too late that they locked the bootloader in the update, sneaky bastards) and it appears this issue still hasn't been fixed. From what I understand, Dan Rosenberg waited until the Verizon update was released before he revealed the Loki exploit but, from what I've read, this exploit does not work on the MF3 update.
My question is now what is it that stops this from working with the MF3 version? Wasn't that the initial point of the release was to solve this particular issue?
I'm trying to understand some of the specifics as I've read a number of articles and links (both in XDA as well as others) and I'm still a bit confused as to where we're at with this. From what I can see, it doesn't appear there is any workaround in sight if the Loki exploit doesn't fix it. Am I more than likely stuck with a locked bootloader for the life of this phone?
Realistically, I am still able to get root access, so it's really not the end of the world but I'd definitely like to be able to flash custom roms if I wanted to. It sounds like I can indirectly do that via Safestrap (does it basically just protect all the crucial stuff that can break the fuse on the device and allow you just use TW based roms, just not custom kernals, is that correct?). But as of now, I believe that's my only option, if I understand correctly.
I realize a number of these issues have been addressed probably a number of times but, due to the amount of details and updates that seem to be changing, I just want to make sure I have a good understanding of everything so I know what my options are. If anyone wants to address this, I'd appreciate it but if these have all been answered a million times in one form or another, I understand that as well.
Thanks for your help!
(I put my questions in bold just to draw attention to them so anyone reading it doesn't have to search through my message to find them to address them, I'm not trying to come off like I'm yelling).

jbrookley said:
Hello everyone,
So, I've been looking into the status of unlocking the bootloader for MF3 updates (I downloaded it and read too late that they locked the bootloader in the update, sneaky bastards) and it appears this issue still hasn't been fixed. From what I understand, Dan Rosenberg waited until the Verizon update was released before he revealed the Loki exploit but, from what I've read, this exploit does not work on the MF3 update.
My question is now what is it that stops this from working with the MF3 version? Wasn't that the initial point of the release was to solve this particular issue?
I'm trying to understand some of the specifics as I've read a number of articles and links (both in XDA as well as others) and I'm still a bit confused as to where we're at with this. From what I can see, it doesn't appear there is any workaround in sight if the Loki exploit doesn't fix it. Am I more than likely stuck with a locked bootloader for the life of this phone?
Realistically, I am still able to get root access, so it's really not the end of the world but I'd definitely like to be able to flash custom roms if I wanted to. It sounds like I can indirectly do that via Safestrap (does it basically just protect all the crucial stuff that can break the fuse on the device and allow you just use TW based roms, just not custom kernals, is that correct?). But as of now, I believe that's my only option, if I understand correctly.
I realize a number of these issues have been addressed probably a number of times but, due to the amount of details and updates that seem to be changing, I just want to make sure I have a good understanding of everything so I know what my options are. If anyone wants to address this, I'd appreciate it but if these have all been answered a million times in one form or another, I understand that as well.
Thanks for your help!
(I put my questions in bold just to draw attention to them so anyone reading it doesn't have to search through my message to find them to address them, I'm not trying to come off like I'm yelling).
Click to expand...
Click to collapse
When Samsung released the MF3 update they used a two-prong attack to close the Loki exploit... those being
1. Closing the exploit in the code itself.
2. Blowing a qFuse on the board to prevent us from flashing any firmware lower then MF3.
I don't really want to get into the technical aspects of how this happened... I'll let someone else answer it if they wish.

jbrookley said:
Hello everyone,
what is it that stops this from working with the MF3 version? Wasn't that the initial point of the release was to solve this particular issue?
Am I more than likely stuck with a locked bootloader for the life of this phone?
does it basically just protect all the crucial stuff that can break the fuse on the device and allow you just use TW based roms, just not custom kernals, is that correct?
Click to expand...
Click to collapse
Nighthawk gave the short answer for the first two. Also, it's possible the update mentioned may have been the MDB>MDL update or verizon equivalent.
Technically even MDL people are stuck with a locked bootloader, but they have an exploit. People are working on an exploit for MF3+, but I can't say how likely it is one will be found.
Safestrap lets you do anything a normal recovery can except flash kernels. This is why you can only flash TW ROMs, as the AOSP and TW kernels are not compatible. Kernels would trip the bootloader checks. However, to add a bit to this and the last answer, something called kexec is in progress of being implemented into Safestrap. The exploit found allows loading unsigned modules, which in turn allows loading a kexec module, which would then load a kernel over the stock kernel while in the boot process. So if this works, it would be the next best thing to a bootloader exploit in that it would give us the same result, though I don't know if kernels will require tweaks to load in kexec.

DeadlySin9 said:
Nighthawk gave the short answer for the first two. Also, it's possible the update mentioned may have been the MDB>MDL update or verizon equivalent.
Technically even MDL people are stuck with a locked bootloader, but they have an exploit. People are working on an exploit for MF3+, but I can't say how likely it is one will be found.
Safestrap lets you do anything a normal recovery can except flash kernels. This is why you can only flash TW ROMs, as the AOSP and TW kernels are not compatible. Kernels would trip the bootloader checks. However, to add a bit to this and the last answer, something called kexec is in progress of being implemented into Safestrap. The exploit found allows loading unsigned modules, which in turn allows loading a kexec module, which would then load a kernel over the stock kernel while in the boot process. So if this works, it would be the next best thing to a bootloader exploit in that it would give us the same result, though I don't know if kernels will require tweaks to load in kexec.
Click to expand...
Click to collapse
Thanks for taking the time to explain that!
A somewhat related question, if my S4 ever gets an OTA update for 4.3, should I deny the update in case they create more obstructions for updates or should I take it since that's the only way my phone will get 4.3 at this point?

jbrookley said:
Thanks for taking the time to explain that!
A somewhat related question, if my S4 ever gets an OTA update for 4.3, should I deny the update in case they create more obstructions for updates or should I take it since that's the only way my phone will get 4.3 at this point?
Click to expand...
Click to collapse
I believe the kexec exploit is being worked on for mk2? But I'm not too sure you will have to review the threads.
Sent from my GT-I9505 using xda premium

jbrookley said:
Thanks for taking the time to explain that!
A somewhat related question, if my S4 ever gets an OTA update for 4.3, should I deny the update in case they create more obstructions for updates or should I take it since that's the only way my phone will get 4.3 at this point?
Click to expand...
Click to collapse
[email protected] said:
I believe the kexec exploit is being worked on for mk2? But I'm not too sure you will have to review the threads.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
It is MK2 exclusive since the MK2 root method gives access to kernel memory and allows it. However, once on MK2 you should definitely not take any and I'm not sure whether the security policy updates are safe or not.

[Q] Please Help!

So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.

khampton_03 said:
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
Click to expand...
Click to collapse
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?

Adam Browning said:
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Click to expand...
Click to collapse
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.

khampton_03 said:
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
Click to expand...
Click to collapse
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Here is a link for the Eclipse thread: http://forum.xda-developers.com/showthread.php?t=2620723

Adam Browning said:
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Click to expand...
Click to collapse
So could I somehow unlock the bootloader??

khampton_03 said:
So could I somehow unlock the bootloader??
Click to expand...
Click to collapse
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876

Adam Browning said:
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Click to expand...
Click to collapse
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha

khampton_03 said:
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
Click to expand...
Click to collapse
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?

Adam Browning said:
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Click to expand...
Click to collapse
Ive never flashed anything and I dont know how to use odin. Lol

khampton_03 said:
Ive never flashed anything and I dont know how to use odin. Lol
Click to expand...
Click to collapse
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558

Adam Browning said:
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Click to expand...
Click to collapse
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?

khampton_03 said:
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
Click to expand...
Click to collapse
That, you don't really have to worry about honestly. I never check, though it may be good practice to. Just follow along with the video in the thread and you will be good to go. Just remember that after you install 4.4.2, you cannot flash 4.3 based ROMs. Also, there is a bug in Safestrap right now that renders the ROM slots somewhat useless, though you can attempt to use them at your own risk. If you want to flash one of the 4.4.2 based ROMs afterwards, it is suggested to back up the stock ROM, and flash the custom ROM in the stock ROM slot. All I can say is, goodluck. Lol. It is a fun process, though somewhat difficult at times. If you have anymore questions after the fact, just reply here. I'll help out as much as I can. It always puts a smile on my face to help convert an Apple fanboy/girl over to Android.

Lollipop source is out

Who shall be the first to build ?
The race is on
Buahahhahahhaha
Sent from my LG-D851 using Tapatalk

brolic925t said:
Who shall be the first to build ?
The race is on
Buahahhahahhaha
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Source ?
Sent from my LG-D852 using XDA Free mobile app

shahkam said:
Source ?
Sent from my LG-D852 using XDA Free mobile app
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...roid-5-0-lollipop-source-code-aosp-right-now/

I'm OK now, I'm happy to have waited this long for an AOSP ROM.
I can wait longer if it becomes a L ROM for our G3!!

Great news !

it's hard to say...i'm working on a lollypop port since weeks now and the main problem is a kernel panic related to the modem resetting.. i think that once i will figure out how to solve it i will be able to release a first beta

It is usually very hard to get new android versions ported to a device where there is no official rom of the same version for it - you basically are going in blind trying to get all the hardware to work.
If we are lucky we might see one or two builds before LG release theirs (which is now less than 2 months away!) but I would expect them to be buggy with some hardware not working - so far we don't even have a fully working Kitkat AOSP build for our device.

manups4e said:
it's hard to say...i'm working on a lollypop port since weeks now and the main problem is a kernel panic related to the modem resetting.. i think that once i will figure out how to solve it i will be able to release a first beta
Click to expand...
Click to collapse
good luck bro!!! lets see if you can beat LG to the draw...
please keep us posted!!!
Thanks in advance

Deeemm79 said:
good luck bro!!! lets see if you can beat LG to the draw...
please keep us posted!!!
Thanks in advance
Click to expand...
Click to collapse
if someone would like to help here is last_kmsg at the very end you'll find the kernel panic about modem

bah, who needs the LG Lollipop rom? probably gonna have their own skin again which, in my opinion, is inferior to stock lollipop. plus, if you have not read, Android 5.0 Lollipop gives developers the option to completely lockdown devices and prevent root, specifically in our devices where bootloader is not unlockable. Don't think I'll take the risk though. It's a huge one!
http://www.xda-developers.com/android/android-l-lockdown/

Oooh. I so happy. ????

jayzhoukj said:
bah, who needs the LG Lollipop rom? probably gonna have their own skin again which, in my opinion, is inferior to stock lollipop. plus, if you have not read, Android 5.0 Lollipop gives developers the option to completely lockdown devices and prevent root, specifically in our devices where bootloader is not unlockable. Don't think I'll take the risk though. It's a huge one!
http://www.xda-developers.com/android/android-l-lockdown/
Click to expand...
Click to collapse
this is true although (and i may well be wrong) i would presume this would only apply if you take the update from OEM and not custom rom .... if we take a flashable custom rom i would assume that this lockdown is completely irrelevant and fairly risk free providing the devs can get all the hardware side of things up and running

ah yes, you are right. personally though i would prefer to go straight to stock rom after rooting. not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom

jayzhoukj said:
ah yes, you are right. personally though i would prefer to go straight to stock rom after rooting. not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
Click to expand...
Click to collapse
that all depends what you want to be able to do on your device ..... without root you cannot use xposed (although until made to run on ART it wont work with lollipop onwards ) ... you need root to delete / modify any / all system apps and other tweaks under the hood ..... there are many things you could need root for

jayzhoukj said:
not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
Click to expand...
Click to collapse
Root alone does nothing. It's what you do with the elevated privileges that matters. With root access, you pretty much have complete control over the phone's software, so you can do next to nothing, or completely overhaul everything to the point where it is indistinguishable from a stock, non-modified phone.
By the way... If LG isn't blowing smoke up our backsides, we'll have a working Optimus UI w/ 5.0.. guessing 6 weeks, give or take. And it remains to be seen how quickly they release their sources. Until those sources are released, any 5.0 custom ROMs are going to be Lollipop on top of LG's KK stuff (kernel, radio/modem, graphics drivers, etc). Not sure how stable that will all be. My only experience with a phone running a ROM like that was running early KK builds on my old Galaxy S3, which was Android 4.4 built on top of Samsung's Jelly Bean stuff. And that was buggy as hell, tons of problems. Basic stuff, like every time it switched from Wi-Fi to mobile data, I got a kernel panic and it would reboot.
So I would be wary of any LP ROMs for the G3 that didn't include the native LP stuff from LG.

LeoRex said:
Root alone does nothing. It's what you do with the elevated privileges that matters. With root access, you pretty much have complete control over the phone's software, so you can do next to nothing, or completely overhaul everything to the point where it is indistinguishable from a stock, non-modified phone.
By the way... If LG isn't blowing smoke up our backsides, we'll have a working Optimus UI w/ 5.0.. guessing 6 weeks, give or take. And it remains to be seen how quickly they release their sources. Until those sources are released, any 5.0 custom ROMs are going to be Lollipop on top of LG's KK stuff (kernel, radio/modem, graphics drivers, etc). Not sure how stable that will all be. My only experience with a phone running a ROM like that was running early KK builds on my old Galaxy S3, which was Android 4.4 built on top of Samsung's Jelly Bean stuff. And that was buggy as hell, tons of problems. Basic stuff, like every time it switched from Wi-Fi to mobile data, I got a kernel panic and it would reboot.
So I would be wary of any LP ROMs for the G3 that didn't include the native LP stuff from LG.
Click to expand...
Click to collapse
infact since 1 month i'm trying to port lollypop and i'm blocked by kernel panic at boot due to modem resetting

My concern is for our d850 development .... It will pick up im guessing
2SHAYNEZ

OEM Unlock feature in Lollipop dev options
Lollipop has an OEM Unlock feature in the development options. Chainfire already utilized it to root the N9. See attached.

so excited in looking forward to your effort - friends....

hwong96 said:
Lollipop has an OEM Unlock feature in the development options. Chainfire already utilized it to root the N9. See attached.
Click to expand...
Click to collapse
OEM unlock meaning ?