Unlocked Bootloader/Custom Recovery - Verizon LG G3

I am currently on a galaxy s4, just started messing around with android a little. I am interested in switching to a slightly newer phone. Assuming I get a g3 that is on the latest OTA update, is it possible to unlock the bootloader or install any type of custom recovery? I am interested in flashing different roms, which I currently can't do on my verizon OF1 S4. If I can't on this phone, what about a g4? I am really only interested in phones with user replaceable batteries that I can swap out, so my options are somewhat limited. Thanks for any help.
James.

I got a G3 that was on 35B -- which I believe is the latest version. You pretty much have to TOT back to 10B (see the thread regarding flashing back to stock), and then you can root, install TWRP, etc from there. Once you've got that, you can pretty much do what you want.
Personally, I had some fussing about with USB device drivers and so on -- I think it took me more time to get the device properly recognized in windows than any other parts of the process!
You'll notice that there are various different ROMS, some based on stock and some that are AOSP, Cyanogen, etc...
jamesvmccann said:
I am currently on a galaxy s4, just started messing around with android a little. I am interested in switching to a slightly newer phone. Assuming I get a g3 that is on the latest OTA update, is it possible to unlock the bootloader or install any type of custom recovery? I am interested in flashing different roms, which I currently can't do on my verizon OF1 S4. If I can't on this phone, what about a g4? I am really only interested in phones with user replaceable batteries that I can swap out, so my options are somewhat limited. Thanks for any help.
James.
Click to expand...
Click to collapse

Hey, thanks for the quick reply. That is excellent news. Sealed the deal for me, I will be buying this phone sometime this weekend. Not familiar with any of the LG tools, or this TOT method you mentioned, so I will read through the threads carefully. Thanks again.

Sure thing!
back to stock, using TOT is this thread.
To get back to 10B from 35B you'll need the dll file in here
Once I was back at 10B, I used stumproot to get root and then used adb to push a bumped TWRP onto the device.
Other tip: Backup your phone's EFS partition before you do too much, you want to keep a copy of that around just in case...

jamesvmccann said:
Hey, thanks for the quick reply. That is excellent news. Sealed the deal for me, I will be buying this phone sometime this weekend. Not familiar with any of the LG tools, or this TOT method you mentioned, so I will read through the threads carefully. Thanks again.
Click to expand...
Click to collapse
just to clarify what was said,
there is NO way to unlock the bootloader
there is a bypass called Bump, similar to loki, but not. yes, you can do anything you would with a real unlock, but we also have no fastboot, and thats not fixable.
if this is ever effectively patched, and you take the update, flashing roms is over.
just wanted to make sure you understood, there was no true unlock.

Related

[Q] basic info I need to know?

Hey guys,
I know how much noob questions piss everyone off, but I'm really confused after reading the threads about FreeGee, root, JB OTA and N4 conversion. I'm probably getting an AT&T Optimus G in a few weeks, so I need to get this stuff understood. So please, bear with me.
1. Should I update to the JB OTA? That is, if the phone has never been past official LG 4.0.4?
2. What are EFS partitions? I read the thread about how to make backups of them; does this complicate making nandroid backups on the LGOG?
3. How does one use LGNPST? Do I use this instead of normal update method when updating to JB OTA?
4. Is FreeGee revesible? Or is your phone permanently unlocked after using FreeGee?
5. Are there any ROMs that are JB, but can be flashed without updating to official 4.1.2 or unlocking with FreeGee?
Thanks.
1. Should I update to the JB OTA? That is, if the phone has never been past official LG 4.0.4?
No longer have to update to JB OTA. You can just LGNPST the TeenyBin.
http://forum.xda-developers.com/showthread.php?t=2230994
This is what I did an hour or two right after I got my LGOG lol. Day of.
2. What are EFS partitions? I read the thread about how to make backups of them; does this complicate making nandroid backups on the LGOG?
http://forum.xda-developers.com/showthread.php?t=2278873
This is the main use of EFS partitions. People lose GPS from certain roms and backing up a working EFS helps. Nandroid backups are kind of like system restore points in terms of PC. You make a back up, do some new stuff and if it doesn't work, just restore the nandroid backup. Backing up the EFS is just so you don't have to back up the entire thing.
3. How does one use LGNPST? Do I use this instead of normal update method when updating to JB OTA?
Refer to the TeenyBin link I gave above. It has an LGNPST tutorial. It's similar to Odin if you've used a Samsung before.
4. Is FreeGee revesible? Or is your phone permanently unlocked after using FreeGee?
Yep. Basically the freegee app has like two buttons, Unlock and Restore lol. Unlock unlocks the bootloader, and Restore restores it. It's pretty simple, I love it.
5. Are there any ROMs that are JB, but can be flashed without updating to official 4.1.2 or unlocking with FreeGee?
You need an unlocked bootloader to flash roms so you need to be unlocked with FreeGee regardless. As far as having to deal without updating to official, you really just need to LGNPST the TeenyBin and you can flash any of the roms in the Original or Android Development forums.
Cheers.
Your order of business on your phone should be Root, Unlock, TeenyBin, flash whatever rom you feel. Constantly make backups when you know your phone is in perfect working condition before moving on to the next big step.
Just to add to the above post, teenybin unlocks boot loader and installs twrp recovery. No need to root and unlock beforehand. Also relocking a non stock ROM with FreeGee may cause security error soft brick.
Thanks for the quick replies. No offense to my other forummates from the Desire and Defy forums, but I can actually understand everything in the ATT LGOG forum because there aren't any people from Europe and Asia who have to use Google translate.
So just to clarify, I don't actually need to use Freegee, correct? Using the teenybins with LGNPST can unlock my bootloader and solve bootlooping problems, right?
I don't think I'll convert to N4 because there aren't any worthy ROMs for N4 in my opinion (purely my opinion, but there are not even any efforts to get Sense 4+ or 5 going) and CM10.1 which was originally for N4-converted LGOGs has another version for LGOG. It looks like the conversion is hard to reverse anyways...
Once again, thanks guys.
EDIT: oh yeah and one more thing. Can someone grab me a latest version of LGNPST? Apparently 1.3 is really old.
Yes exactly right. I came from Samsung (SGS2) and you know how easy stuff is there to the OG Triple OG and haven't really missed a beat. I used FreeGee myself but that's because I didn't find out about teenybin until a couple days ago.
Anyways you're good to go with what you've been told. Wham bam thank you ma'am.:thumbup:
I'm not sure where to get LGNPST from. Assuming a Google search would probably tell me. In all honesty there's really no need to mess with converting the LGOG to N4.
Sent from my LG-E970 using Tapatalk 2
Use links and guide in teenybin thread for lgnpst (additional info section).

About to buy an LG G3, PLEASE HELP!!

Dear Friends,
I am a US consumer. About to buy a Verizon LG G3. My number # 1 priority in a phone is, more of less development support for a phone. Number of ROMs being developed, how many choices, mods, frequent updates, and etc.
Clearly, the International version D855 is the King. Number 2 is probably D851, the T-Mobile US Variant with the Unlocked bootloader. International versions are expensive and hard to find in America and it's more or less the same for the T-Mobile version.
I browsed the Development section for all G3 variants on XDA, and surprisingly, the number 3 variant is the Verizon, US Model! Which is fine by me, because it can be unlocked and used on AT&T and I am moving to Verizon soon, for the better coverage and LTE speeds.
I am lined up to pull the trigger on buying the Verizon G3, as we speak, but I need some help confirmation from you guys:
1. Is it true, that with the BUMP'd/TWRP recovery, the Verizon G3 is as good as the Unlocked bootloader models, like D851 and D855? If not, what is the difference, disadvantage?
2. How would you rate the Development support for the Verizon variant of the LG G3?
Thank you for your help! I have the seller lined up, please respond as soon as you can, I would really appreciate it!
ProFragger said:
Dear Friends,
I am a US consumer. About to buy a Verizon LG G3. My number # 1 priority in a phone is, more of less development support for a phone. Number of ROMs being developed, how many choices, mods, frequent updates, and etc.
Clearly, the International version D855 is the King. Number 2 is probably D851, the T-Mobile US Variant with the Unlocked bootloader. International versions are expensive and hard to find in America and it's more or less the same for the T-Mobile version.
I browsed the Development section for all G3 variants on XDA, and surprisingly, the number 3 variant is the Verizon, US Model! Which is fine by me, because it can be unlocked and used on AT&T and I am moving to Verizon soon, for the better coverage and LTE speeds.
I am lined up to pull the trigger on buying the Verizon G3, as we speak, but I need some help confirmation from you guys:
1. Is it true, that with the BUMP'd/TWRP recovery, the Verizon G3 is as good as the Unlocked bootloader models, like D851 and D855? If not, what is the difference, disadvantage?
2. How would you rate the Development support for the Verizon variant of the LG G3?
Thank you for your help! I have the seller lined up, please respond as soon as you can, I would really appreciate it!
Click to expand...
Click to collapse
Having the bump'd twrp is basically the same thing. No matter which way you get to a custom recovery it's all the same. In my opinion its a great phone to have and pretty hard to screw something up. Sky Dragon and Jasmine are my personal favorites as far as Stock roms go. Unless you want to wait for the G4 i would go ahead and pull the trigger. You won't be disappointed.
Edde3d said:
Having the bump'd twrp is basically the same thing. No matter which way you get to a custom recovery it's all the same. In my opinion its a great phone to have and pretty hard to screw something up. Sky Dragon and Jasmine are my personal favorites as far as Stock roms go. Unless you want to wait for the G4 i would go ahead and pull the trigger. You won't be disappointed.
Click to expand...
Click to collapse
This is excellent news bud, thank you! What tripped me up was the fact that the T-Mobile version is so much more expensive... Why exactly ?
One question for you, how would you rate the development support for the Verizon variant? And yes, I'm more interested in CM12 kind of ROMs.
Lastly, if the seller has OTA'd to Lollipop, can I somehow bring it back to the KK firmware in I want that?
Thanks so much for your help again!
ProFragger said:
This is excellent news bud, thank you! What tripped me up was the fact that the T-Mobile version is so much more expensive... Why exactly ?
Click to expand...
Click to collapse
Must be that Qi charging antenna sticker... The VZW comes with only the NFC installed, but it is easy and cheap to upgrade.
ProFragger said:
One question for you, how would you rate the development support for the Verizon variant? And yes, I'm more interested in CM12 kind of ROMs.
Click to expand...
Click to collapse
I have to say that it is pretty excellent. Lots of support just for the VZW variant on the AOSP side and many of the goodies from the main LG G3 thread are also applicable. I find the best phones for hacking up are the ones available on most of the US carriers.
ProFragger said:
Lastly, if the seller has OTA'd to Lollipop, can I somehow bring it back to the KK firmware in I want that?
Click to expand...
Click to collapse
Easiest way would be to flash a KK stock-based ROM. That way, you go bloat-free, get fixes, and stop the OTA if you're freezing on KK.
epidenimus said:
Must be that Qi charging antenna sticker... The VZW comes with only the NFC installed, but it is easy and cheap to upgrade.
I have to say that it is pretty excellent. Lots of support just for the VZW variant on the AOSP side and many of the goodies from the main LG G3 thread are also applicable. I find the best phones for hacking up are the ones available on most of the US carriers.
Easiest way would be to flash a KK stock-based ROM. That way, you go bloat-free, get fixes, and stop the OTA if you're freezing on KK.
Click to expand...
Click to collapse
Thanks for the response, bud. Wireless charging really hasn't been a factor me, so far, so it's a non-issue. Good to hear of the VZW Dev support, although I'd have to say it's probably because someone found a way to "bump" or install Custom Recovery on a locked Bootloader, which is every phone on Verizon ! Too bad, because these LTE phones are factory unlocked for Global use, but so crippled, thanks to the bootloader non-sense. I wish the exploit extended to the Note lines or even HTC phones.
This is one reason why we see most of the T-Mobile variants selling like hot cakes, even though Sprint has that as well, the supported GSM functionality and bands are just not there.
I assume doing a simple Stock ROM flash via the LG Flash Tools, or "KDZ" is the way to get back to KK, if wanted? No downgrade issues like Notes, correct? Apparently, you can't downgrade the bootloader on those once moved to LP ...
ProFragger said:
Thanks for the response, bud. Wireless charging really hasn't been a factor me, so far, so it's a non-issue. Good to hear of the VZW Dev support, although I'd have to say it's probably because someone found a way to "bump" or install Custom Recovery on a locked Bootloader, which is every phone on Verizon ! Too bad, because these LTE phones are factory unlocked for Global use, but so crippled, thanks to the bootloader non-sense. I wish the exploit extended to the Note lines or even HTC phones.
This is one reason why we see most of the T-Mobile variants selling like hot cakes, even though Sprint has that as well, the supported GSM functionality and bands are just not there.
I assume doing a simple Stock ROM flash via the LG Flash Tools, or "KDZ" is the way to get back to KK, if wanted? No downgrade issues like Notes, correct? Apparently, you can't downgrade the bootloader on those once moved to LP ...
Click to expand...
Click to collapse
Yes, you can either use the "kdz", or " tot" methods of restoring back to software version 10B (the initial stock software that is easily rootable/unlockable using stump and bump). I personally prefer the tot method, but that probably because I've got a Win 7 computer ( Win 8 has apparently caused some issues for some using the tot method), and its the first method that came out that I used so just stuck with it, but either would work great. And no, no downgrade nonsense or risk of bricks, regardless of firmware it comes on (at least as of this writing lol)
ohlin5 said:
Yes, you can either use the "kdz", or " tot" methods of restoring back to software version 10B (the initial stock software that is easily rootable/unlockable using stump and bump). I personally prefer the tot method, but that probably because I've got a Win 7 computer ( Win 8 has apparently caused some issues for some using the tot method), and its the first method that came out that I used so just stuck with it, but either would work great. And no, no downgrade nonsense or risk of bricks, regardless of firmware it comes on (at least as of this writing lol)
Click to expand...
Click to collapse
This is excellent news and response, bud, thanks! Although, from a little bit of reading around here, I have heard of at least a few instances of people restoring stock firmware and in the process, somehow magically clearing out their IMEI to 0 !!! Is this actually true and a common occurrence? I heard their is a process to correct is via QPST, but it is arduous.
I wish someone did a video of Root + TWRP from starting to end for the LG G3 (Verizon version). Seeing how this will be my first LG phone, terms still confuse me, like Root method names, what exactly does "stump" or "bump" mean, and yeah, getting TWRP on there.
There is also a one-click TWRP installer for the VZW G3 on the Playstore? Is that true? Is that the same as having Bumped TWRP? Thanks!
ProFragger said:
This is excellent news and response, bud, thanks! Although, from a little bit of reading around here, I have heard of at least a few instances of people restoring stock firmware and in the process, somehow magically clearing out their IMEI to 0 !!! Is this actually true and a common occurrence? I heard their is a process to correct is via QPST, but it is arduous.
I wish someone did a video of Root + TWRP from starting to end for the LG G3 (Verizon version). Seeing how this will be my first LG phone, terms still confuse me, like Root method names, what exactly does "stump" or "bump" mean, and yeah, getting TWRP on there.
There is also a one-click TWRP installer for the VZW G3 on the Playstore? Is that true? Is that the same as having Bumped TWRP? Thanks!
Click to expand...
Click to collapse
I can't speak to the IMEI clearing as being a "common" issue....I've restored at least 5 different phones using the tot method, several multiple times and never once had an issue. I do, however, maintain a backup in the cloud of the EFS partition (same basic thing I think? I just know it's an important partition lol) for every phone I oversee and have messed with.
As for your question about stump/bump/etc., there are several different root methods out now...."Stump root" was just the name of the first - and so it's what I've always stuck with. "Bump", on the other hand, is the method for "unlocking" the bootloader and flashing TWRP.
As for the play store 'auto' app, I hadn't even heard of it until you said something and I searched. I'm assuming you're talking about this. All I can say is that I've never used it so I have no idea. Below I've laid out the steps that I, personally, follow each and every time I've gotten a new device or restored one. I realize there may be simpler ways out there now, but I've been in this specific community since the very beginning, and so I've just stuck with the "tried and true" stuff that came out first.
As for the one click TWRP installer on the play store, again I don't know. However, flashing the "bumped" TWRP via flashify is probably the easiest way to do it (it is not officially stated by the devs to work, but countless people including myself numerous times have confirmed it does).
So, TLDR:
If I were to get a brand new, VS985 today, here is the exact set of steps I would follow (I just got another one 2 weeks ago and these are what I did, and have always done):
1). Use the tot method, found here to restore (downgrade) back to the initial stock release software (version 10B_03). Alternatively, you can use the "kdz" method found here, but on my Windows 7 PC the tot method has always worked like a charm and the one time I used the kdz method it seemed a bit sketchier, but to each their own. I think the main "push" for the kdz method was that some people were having trouble getting the tot method to work on computers w/ Windows 8/8.1.
2). Once that's done, reboot and do minimal setup, then use stump root (found here) to root. Follow the directions exactly, and as long as you're on 10B it will still work - it's just been patched in newer software versions. After rooting and rebooting, then install superSU from the play store, open that, update the binary via "normal" method and then reboot once more. After that reboot, uninstall the stump app, you don't need it anymore.
3). Then, install Flashify from the play store. To be safe, I usually open it and make sure I've granted root, then close it and open superSU and make sure it's got the green mark next to it signifying it has full root access (again, just to be sure). Then, download the "bumped" TWRP image from here, and put it somewhere you can find it on your INTERNAL storage (not sure if this is vital, but again, just being safe). Also, for later, download the zip of TWRP 2.8.6.1 from here
4). Use the Flashify file browser to flash that recovery image you just downloaded to the your internal storage. Let it do it's thing, then reboot when it prompts you.
5). You should now boot up into TWRP. Use the install function to update from the TWRP you just flashed (2.8.0.0) to the 2.8.6.1 zip you just downloaded. Then use reboot>recovery to confirm it took.
6). That's pretty much it. With that you're fully rooted + unlocked. Only other thing I would highly recommend at this point is following the guide here to back up your EFS partition, and then store it to your Google drive or dropbox or other cloud storage or somewhere safe lol. If you're gonna stay stock I'd freeze the system update apps, or better use just flash skydragon or jasmine roms as they're great stock-based roms.
Any other questions just let me know.
ohlin5 said:
I can't speak to the IMEI clearing as being a "common" issue....I've restored at least 5 different phones using the tot method, several multiple times and never once had an issue. I do, however, maintain a backup in the cloud of the EFS partition (same basic thing I think? I just know it's an important partition lol) for every phone I oversee and have messed with.
As for your question about stump/bump/etc., there are several different root methods out now...."Stump root" was just the name of the first - and so it's what I've always stuck with. "Bump", on the other hand, is the method for "unlocking" the bootloader and flashing TWRP.
As for the play store 'auto' app, I hadn't even heard of it until you said something and I searched. I'm assuming you're talking about this. All I can say is that I've never used it so I have no idea. Below I've laid out the steps that I, personally, follow each and every time I've gotten a new device or restored one. I realize there may be simpler ways out there now, but I've been in this specific community since the very beginning, and so I've just stuck with the "tried and true" stuff that came out first.
As for the one click TWRP installer on the play store, again I don't know. However, flashing the "bumped" TWRP via flashify is probably the easiest way to do it (it is not officially stated by the devs to work, but countless people including myself numerous times have confirmed it does).
So, TLDR:
If I were to get a brand new, VS985 today, here is the exact set of steps I would follow (I just got another one 2 weeks ago and these are what I did, and have always done):
1). Use the tot method, found here to restore (downgrade) back to the initial stock release software (version 10B_03). Alternatively, you can use the "kdz" method found here, but on my Windows 7 PC the tot method has always worked like a charm and the one time I used the kdz method it seemed a bit sketchier, but to each their own. I think the main "push" for the kdz method was that some people were having trouble getting the tot method to work on computers w/ Windows 8/8.1.
2). Once that's done, reboot and do minimal setup, then use stump root (found here) to root. Follow the directions exactly, and as long as you're on 10B it will still work - it's just been patched in newer software versions. After rooting and rebooting, then install superSU from the play store, open that, update the binary via "normal" method and then reboot once more. After that reboot, uninstall the stump app, you don't need it anymore.
3). Then, install Flashify from the play store. To be safe, I usually open it and make sure I've granted root, then close it and open superSU and make sure it's got the green mark next to it signifying it has full root access (again, just to be sure). Then, download the "bumped" TWRP image from here, and put it somewhere you can find it on your INTERNAL storage (not sure if this is vital, but again, just being safe). Also, for later, download the zip of TWRP 2.8.6.1 from here
4). Use the Flashify file browser to flash that recovery image you just downloaded to the your internal storage. Let it do it's thing, then reboot when it prompts you.
5). You should now boot up into TWRP. Use the install function to update from the TWRP you just flashed (2.8.0.0) to the 2.8.6.1 zip you just downloaded. Then use reboot>recovery to confirm it took.
6). That's pretty much it. With that you're fully rooted + unlocked. Only other thing I would highly recommend at this point is following the guide here to back up your EFS partition, and then store it to your Google drive or dropbox or other cloud storage or somewhere safe lol. If you're gonna stay stock I'd freeze the system update apps, or better use just flash skydragon or jasmine roms as they're great stock-based roms.
Any other questions just let me know.
Click to expand...
Click to collapse
Hey bud,
This is probably the BEST post I have EVER been a recipient of at XDA. And trust me, I have been here since almost 2008! So please accept my deepest gratitude, so detailed, and so patient, really excellent job and excellent member of the community!
I ordered my phone, it is used, so not sure what build it will have, but if it took the OTA, then likely, it's LP and I would have to downgrade to 10b, like you said and then use Stump to Root. Problem is, since we can't backup EFS without Root, or TWRP, rather, it is making me nervous to use the TOT method first, which as I mentioned earlier, I have read, people blowing their IMEIs like that before ...
With that said, I think you have laid everything out nicely for me, just a matter of getting the phone, sitting down, and getting through the process . What would make it easier, is a Rooting method without the downgrade, but that's just me being really nit picky .
The other thought lingering in my head... since this my first LG, do I enjoy a Optimus UI ROM for a bit or go straight for the no nonsense CM12 or 12.1? Do you guys have the non working NFC on CM ROMs as well or other bugs that are common like that? I heard the LG G3 stock ROM got super laggy and heats the phone up!
ProFragger said:
Hey bud,
This is probably the BEST post I have EVER been a recipient of at XDA. And trust me, I have been here since almost 2008! So please accept my deepest gratitude, so detailed, and so patient, really excellent job and excellent member of the community!
I ordered my phone, it is used, so not sure what build it will have, but if it took the OTA, then likely, it's LP and I would have to downgrade to 10b, like you said and then use Stump to Root. Problem is, since we can't backup EFS without Root, or TWRP, rather, it is making me nervous to use the TOT method first, which as I mentioned earlier, I have read, people blowing their IMEIs like that before ...
With that said, I think you have laid everything out nicely for me, just a matter of getting the phone, sitting down, and getting through the process . What would make it easier, is a Rooting method without the downgrade, but that's just me being really nit picky .
The other thought lingering in my head... since this my first LG, do I enjoy a Optimus UI ROM for a bit or go straight for the no nonsense CM12 or 12.1? Do you guys have the non working NFC on CM ROMs as well or other bugs that are common like that? I heard the LG G3 stock ROM got super laggy and heats the phone up!
Click to expand...
Click to collapse
Thanks for the compliment What can I say, I've just seen too many crap-tastic tutorials
I understand your concern about the whole imei thing, I'd be the same way had I not done it so many times. Could you link the places where you've seen people wiping out their imeis supposedly? Also, if you're willing to do a little reading, something along these lines MIGHT work just to obtain root while still on STOCK LP (which I'd what I'm assuming it would come on:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
If you do go this route and try to root while still on stock and before downgrading so that you can backup the efs partition, then be sure to NOT install twrp unless you do a bunch of reading beforehand as I believe it is the aboot that changed on LP and if you try to flash the twrp images I posted while on stock LP you'll get secure boot errors and have a heck of a mess. IMHO, better to either bite the bullet and do the downgrade straight (as I haven't seen these imei wipes you're noting and I've done several myself with zero issues), OR try and root stock LP, then backup the EFS partition, and THEN downgrade through the steps I posted.
Either way, with the Roms, its pretty much same as normal. I never recommend full stock, as if you're gonna root and unlock, you might as well use it IMHO. Stock is good if your most important things are stability and (at least currently and in my experience) battery life, while aosp based is better if you like the cleaner look, and most customizability. Either way you'll be OK. If you go for stock LG, I'd recommend either jasmine ROM or skydragon ROM. I've used skydragon ROM for a bit and its great if you love stock. I'm more of an aosp guy and so I currently use CM 12.1 and its easily DD stable for me, but not without it's quirks - sometimes the screen double tap to wake doesn't work or screen doesn't come on post-call, sometimes the battery life ain't great, sometimes it runs hot, etc. but all typically good enough for reasonable DD stability. I've started using 777kernel on top of the CM 12.1 flash and the device seems to run a bit cooler.
ohlin5 said:
Thanks for the compliment What can I say, I've just seen too many crap-tastic tutorials
I understand your concern about the whole imei thing, I'd be the same way had I not done it so many times. Could you link the places where you've seen people wiping out their imeis supposedly? Also, if you're willing to do a little reading, something along these lines MIGHT work just to obtain root while still on STOCK LP (which I'd what I'm assuming it would come on:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
If you do go this route and try to root while still on stock and before downgrading so that you can backup the efs partition, then be sure to NOT install twrp unless you do a bunch of reading beforehand as I believe it is the aboot that changed on LP and if you try to flash the twrp images I posted while on stock LP you'll get secure boot errors and have a heck of a mess. IMHO, better to either bite the bullet and do the downgrade straight (as I haven't seen these imei wipes you're noting and I've done several myself with zero issues), OR try and root stock LP, then backup the EFS partition, and THEN downgrade through the steps I posted.
Either way, with the Roms, its pretty much same as normal. I never recommend full stock, as if you're gonna root and unlock, you might as well use it IMHO. Stock is good if your most important things are stability and (at least currently and in my experience) battery life, while aosp based is better if you like the cleaner look, and most customizability. Either way you'll be OK. If you go for stock LG, I'd recommend either jasmine ROM or skydragon ROM. I've used skydragon ROM for a bit and its great if you love stock. I'm more of an aosp guy and so I currently use CM 12.1 and its easily DD stable for me, but not without it's quirks - sometimes the screen double tap to wake doesn't work or screen doesn't come on post-call, sometimes the battery life ain't great, sometimes it runs hot, etc. but all typically good enough for reasonable DD stability. I've started using 777kernel on top of the CM 12.1 flash and the device seems to run a bit cooler.
Click to expand...
Click to collapse
Forgive the late response bud, the compliments are well deserved, trust me !
Here's an example of a gentleman losing his IMEI via TOT: http://forum.xda-developers.com/verizon-lg-g3/help/restore-via-tot-wipe-imei-t3033445
Let's hope it's the abnormal and not so normal .
I think let me get the phone I will keep, and will figure it out how to Root and Bump it. This phone I have to return, the item was not as described, but incidentally, came with Android 4.4.2! I imagine a simple Stump and Bump would have worked like a charm here?
In the end, playing with Optimus UI/LG UI, I couldn't find anything really that would make me stay with it. Outside of the camera app, 4K recording, and some minor features which I love, but no one else cares about.. like the Phone Muting and Speaker options in the Notification bar, while on a call. Can you believe, I couldn't even find a replacement app/dialer that could do that on AOSP ROM !?
Since you are a CM12.1 user, can I ask you what works on it and doesn't? NFC? Bluetooth? Knock-on, but NOT Knock Code, correct? IR Blaster? And have you had much luck with Xposed?
Please let me know your thoughts and input? Also, for CM12/12.1, do I need a special kernel for Knock on (and Knock Code) to work? If so, which one?
Thanks again bud!
ProFragger said:
In the end, playing with Optimus UI/LG UI, I couldn't find anything really that would make me stay with it. Outside of the camera app, 4K recording, and some minor features which I love, but no one else cares about..
Click to expand...
Click to collapse
The stock camera is surely missed, but the screen clarity is still amazing, the removable battery is sizeable, the sound is decent (no boom sound though), and you can slap an external SD card in it for more fun. The real appeal of this is that the hardware setup is pretty awesome for running and testing custom software. The LG stock ROM is really lackluster; a good AOSP ROM makes far better use of it.
ProFragger said:
Since you are a CM12.1 user, can I ask you what works on it and doesn't? NFC? Bluetooth? Knock-on, but NOT Knock Code, correct? IR Blaster? And have you had much luck with Xposed?
Click to expand...
Click to collapse
Yes, all of this works fine in the 12.1 ROMs I have tested out. You get knock-on and knock-off at the status bar. Quick Remote has been ported and works great. Most things that you might use Xposed to do are integrated in a good AOSP/CM based ROM already. I have not seen a need to install it on AOSP, just stock.
ProFragger said:
Please let me know your thoughts and input? Also, for CM12/12.1, do I need a special kernel for Knock on (and Knock Code) to work? If so, which one?
Click to expand...
Click to collapse
If the dev baked the feature in, the kernel that comes with it should work.
Just my two cents. I hope it helps!
Pretty much what he said ^^^
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
ProFragger said:
Forgive the late response bud, the compliments are well deserved, trust me !
Here's an example of a gentleman losing his IMEI via TOT: http://forum.xda-developers.com/verizon-lg-g3/help/restore-via-tot-wipe-imei-t3033445
Let's hope it's the abnormal and not so normal .
I think let me get the phone I will keep, and will figure it out how to Root and Bump it. This phone I have to return, the item was not as described, but incidentally, came with Android 4.4.2! I imagine a simple Stump and Bump would have worked like a charm here?
In the end, playing with Optimus UI/LG UI, I couldn't find anything really that would make me stay with it. Outside of the camera app, 4K recording, and some minor features which I love, but no one else cares about.. like the Phone Muting and Speaker options in the Notification bar, while on a call. Can you believe, I couldn't even find a replacement app/dialer that could do that on AOSP ROM !?
Since you are a CM12.1 user, can I ask you what works on it and doesn't? NFC? Bluetooth? Knock-on, but NOT Knock Code, correct? IR Blaster? And have you had much luck with Xposed?
Please let me know your thoughts and input? Also, for CM12/12.1, do I need a special kernel for Knock on (and Knock Code) to work? If so, which one?
Thanks again bud!
Click to expand...
Click to collapse
See the other guys post, does a pretty fair overview. And thanks for that link....I mean it does show it can happen I guess, although I did also note the OP said in his last response that the 2nd time he toted he didn't have the issue, so he thinks maybe he screwed something up the first time....who knows lol
ohlin5 said:
Pretty much what he said ^^^
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
See the other guys post, does a pretty fair overview. And thanks for that link....I mean it does show it can happen I guess, although I did also note the OP said in his last response that the 2nd time he toted he didn't have the issue, so he thinks maybe he screwed something up the first time....who knows lol
Click to expand...
Click to collapse
That would be me.
Yup, the second time around it worked just fine when I flashed back to 10b so I could then take the LP OTA. Of course, now we know that you can use the 12b image to flash back to official KK to take the OTA, or you can now flash the official 23C image that's out there and one-click root it.
Glad my post has been of use. I definitely wanted to share my experience so that others who experience the same issue can then get it rectified.
epidenimus said:
The stock camera is surely missed, but the screen clarity is still amazing, the removable battery is sizeable, the sound is decent (no boom sound though), and you can slap an external SD card in it for more fun. The real appeal of this is that the hardware setup is pretty awesome for running and testing custom software. The LG stock ROM is really lackluster; a good AOSP ROM makes far better use of it.
Yes, all of this works fine in the 12.1 ROMs I have tested out. You get knock-on and knock-off at the status bar. Quick Remote has been ported and works great. Most things that you might use Xposed to do are integrated in a good AOSP/CM based ROM already. I have not seen a need to install it on AOSP, just stock.
If the dev baked the feature in, the kernel that comes with it should work.
Just my two cents. I hope it helps!
Click to expand...
Click to collapse
ohlin5 said:
Pretty much what he said ^^^
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
See the other guys post, does a pretty fair overview. And thanks for that link....I mean it does show it can happen I guess, although I did also note the OP said in his last response that the 2nd time he toted he didn't have the issue, so he thinks maybe he screwed something up the first time....who knows lol
Click to expand...
Click to collapse
iBolski said:
That would be me.
Yup, the second time around it worked just fine when I flashed back to 10b so I could then take the LP OTA. Of course, now we know that you can use the 12b image to flash back to official KK to take the OTA, or you can now flash the official 23C image that's out there and one-click root it.
Glad my post has been of use. I definitely wanted to share my experience so that others who experience the same issue can then get it rectified.
Click to expand...
Click to collapse
Guys,
I wanted to follow up/close the loop on this thread and thank you guys once again for all your help! I received 12B on my phone, was downloading materials to TOT down to 10B to root with stump, till I found this:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Worked like a charm, and can save others an hour or two, downloading the stock firmware and etc.
Now I am Rooted, TWRP'd 2.6.8.1, is it?, and efs backedup as well!
This is my first LG ever, so I will use stock ROM on it for a few weeks. It is unbelievable how LITTLE stock ROM support is, compared to the CM stuff, across the board for the G3. Maybe your experience is different, but that is what I have found. For every 5 aosp builds there is one stock ROM. And the Verizon variant is no different, only Jasmin and skydragon available. Please do correct me if I am wrong, and there are more ROMs out there to try? I still can't believe the lack of stock ROMs considering how crucial the camera is on this phone!
Between the sd and Jasmine, I think I will start out sd. Yes Jasmine is smaller and also updated later?, but also a little too complicated to install with separate Zips and stuff. What o you guys think?
Finally, if I go the aosp route, which likely I will in a few weeks, which one do you recommend for best features, updates, and performance/battery life?
Lastly, and possibly the most important question... What camera are you using on your CM ROMs ? I found that Lenovo was the best on my Note 3, best features and quality. Although a battery drain, no 4K, or HDR, and Panorama ... What do you guys think?
Thank you again guys for ALL your help!
ProFragger said:
Guys,
I wanted to follow up/close the loop on this thread and thank you guys once again for all your help! I received 12B on my phone, was downloading materials to TOT down to 10B to root with stump, till I found this:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Worked like a charm, and can save others an hour or two, downloading the stock firmware and etc.
Now I am Rooted, TWRP'd 2.6.8.1, is it?, and efs backedup as well!
This is my first LG ever, so I will use stock ROM on it for a few weeks. It is unbelievable how LITTLE stock ROM support is, compared to the CM stuff, across the board for the G3. Maybe your experience is different, but that is what I have found. For every 5 aosp builds there is one stock ROM. And the Verizon variant is no different, only Jasmin and skydragon available. Please do correct me if I am wrong, and there are more ROMs out there to try? I still can't believe the lack of stock ROMs considering how crucial the camera is on this phone!
Between the sd and Jasmine, I think I will start out sd. Yes Jasmine is smaller and also updated later?, but also a little too complicated to install with separate Zips and stuff. What o you guys think?
Finally, if I go the aosp route, which likely I will in a few weeks, which one do you recommend for best features, updates, and performance/battery life?
Lastly, and possibly the most important question... What camera are you using on your CM ROMs ? I found that Lenovo was the best on my Note 3, best features and quality. Although a battery drain, no 4K, or HDR, and Panorama ... What do you guys think?
Thank you again guys for ALL your help!
Click to expand...
Click to collapse
Nope, no other main stock based Roms for the G3....SD and Jasmine. If I were running stock I'd go SD with the custom kernel packaged with it. As for AOSP, people may disagree with me here, but I just sitck with CM. I like the idea of nightlies and being able to easily find updates from their websites and keep tabs on the progress updates merged, but that's just me. Recently I've been running CM with the 777 kernel, but only because the stock kernel seemed to be running very warm and draining battery a fair bit faster than usual. As for the camera, I again just stick with stock, as I find its good enough for me. I flashed several motorola, lenovo, etc. camera mods but it seemed like all too often it'd either be glitchy beyond measure or would break FFC in certain apps I knew to be otherwise working, etc. So I just started sticking with stock.
Random info:
I like focal (altho deprecated) it's in the play store. Lots of camera options.
If you do end up on some non stock roms, and have a dual band router, turn the channel on it to 11. It doesn't fix the wifi problems 100% but it may help.
Also there's plenty of g4 stuff floating around if you look for it.
Also you shouldn't have more than 0.25-0.5%/hr idle drain. If you do then somethings wrong. I'd install better battery stats right away and charge up to full and unplug before bed.
Amplify and greenify help but really the display is your battery culprit. I like cf lumen to help adjust the display from day to night usage.
ohlin5 said:
Nope, no other main stock based Roms for the G3....SD and Jasmine. If I were running stock I'd go SD with the custom kernel packaged with it. As for AOSP, people may disagree with me here, but I just sitck with CM. I like the idea of nightlies and being able to easily find updates from their websites and keep tabs on the progress updates merged, but that's just me. Recently I've been running CM with the 777 kernel, but only because the stock kernel seemed to be running very warm and draining battery a fair bit faster than usual. As for the camera, I again just stick with stock, as I find its good enough for me. I flashed several motorola, lenovo, etc. camera mods but it seemed like all too often it'd either be glitchy beyond measure or would break FFC in certain apps I knew to be otherwise working, etc. So I just started sticking with stock.
Click to expand...
Click to collapse
jfriend33 said:
Random info:
I like focal (altho deprecated) it's in the play store. Lots of camera options.
If you do end up on some non stock roms, and have a dual band router, turn the channel on it to 11. It doesn't fix the wifi problems 100% but it may help.
Also there's plenty of g4 stuff floating around if you look for it.
Also you shouldn't have more than 0.25-0.5%/hr idle drain. If you do then somethings wrong. I'd install better battery stats right away and charge up to full and unplug before bed.
Amplify and greenify help but really the display is your battery culprit. I like cf lumen to help adjust the display from day to night usage.
Click to expand...
Click to collapse
Guys, horrible day of flashing.
GPS issues with both SD and Jasmine. Tried both stock and SD kernels, as well as 12B and 23C radios, no dice :'(!
Resurrection Remix, not enough options for me and zero GPS locks :'(!
BlissPop came the closest. Bluetooth worked, Xposed, had the options I wanted, but GPS is still not strong enough indoors, and there is an issue WiFi not autoconnecting on each boot :'(!
Long story short, I think I need to head back to 12B somehow. Can anyone please tell me how? I will TOT to 10B, but then, how do I get to 12B? I can't find the image for it anywhere! Please do help, I need a reliable
working phone tomorrow, porting my number into a new carrier...
Thanks in advance!
Some people have to tot back to get gps working. For me, flashing sky always did the trick. Sometimes it takes longer or a reboot, and even setting gps to gps only (strange huh)?
Didn't u make a TWRP backup of working firmware?
I would seriously try flashing skydragon again. Why do u need gps indoors anyway?
Not sure about the tot but I think u can just take updates. Once u get to 10b please make a TWRP backup if you haven't already.
jfriend33 said:
Some people have to tot back to get gps working. For me, flashing sky always did the trick. Sometimes it takes longer or a reboot, and even setting gps to gps only (strange huh)?
Didn't u make a TWRP backup of working firmware?
I would seriously try flashing skydragon again. Why do u need gps indoors anyway?
Not sure about the tot but I think u can just take updates. Once u get to 10b please make a TWRP backup if you haven't already.
Click to expand...
Click to collapse
Thanks for the quick response bud. I will try SD again, maybe, but for now, I liked how Stock felt out of the box which was 12B. I feel like with rooting, manual debloating, and maybe the CPU thermals mods, I would have a snappy 4.2 device.
I'm stupid, I did not Nandroid the 12B I had . Thought it would be like Samsung, each firmware easily available for download on the Internet to flash via the LG Flash Tools.
I will TOT to 10B tomorrow, but then question is, how do I upgrade or OTA to 12B? Would it give me options on which update to take? Or will it take me to the latest, which is 23C?
Appreciate your help or if anyone can! Thank you!

[Q] Am I screwed (bootloader issue)?

Hi all. Please excuse if this has been asked (and answered), but I just spent two days with this phone and have just about torn my hair out.
I have a Verizon S4 (SCH-I545). I got it second-hand, so I don't know if the previous owner took any OTA updates. I wanted to put CM12 on it. However, in that thread, it's made very clear that it won't work without being on the MDK bootloader.
Well, when I execute the command "getprop ro.bootloader" from within Safestrap, I get "I545VRUFNC5".
Obviously, this is not MDK. Is this a bootloader that came after MDK as part of an OTA update? Either way, am I no longer able to Odin flash the MDK bootloader?
Thanks in advance.
Yes..This Bootloader is newer, and locked and cannot be reverted using ODIN. You would need to find a manual copy/change method to revert the Bootloader.
Sent from my SCH-I545 using Tapatalk
Hi KaosMaster. Thanks for your quick reply. So, does a manual copy/change method exist? You can probably surmise that I tried Odin'ing several stock ROMs with MDK packaged in and each one failed for various reasons. Can I do this copy/change action or would Verizon themselves have to do it? If the latter, would they do it without charging me a small fortune?
While I'm on the subject, are there any other gotchas you know of regarding this I545VRUFNC5 bootloader? What other ROMs won't work with it?
Thanks again!
Odin Won't work.
JTAG won't work(tested, phone bricks)
nc5 has root and safestap + limited ROMs with a touchwiz base
Some ROMs:
Hyperdrive
Echoe
Super6 Port
KitPop
Eclipse
Hi XxD34THxX. When you say the phone bricks using JTAG, do you mean it brick bricks? As in, turning the phone into a doorstop?
Do you know if Verizon would revert it back if you made such a request? If so, would it cost anything?
Well... with JTAG, I am pretty sure it turns into a soft brick. I can't confirm.
BWAHAHAHAHAHAHAH
Verizon will just laugh in your face if you asked them that.
XxD34THxX said:
Well... with JTAG, I am pretty sure it turns into a soft brick. I can't confirm.
BWAHAHAHAHAHAHAH
Verizon will just laugh in your face if you asked them that.
Click to expand...
Click to collapse
Arggh! Locked bootloaders are a complete and utter PITA.
What I don't understand is why CM12 requires a specific bootloader to function. To me, that sounds like Windows needing a specific BIOS or bootstrap to work.
Does CM10 have this requirement as well?
BTW, thanks for the rom list. I'll definitely check 'em out.
Yes, it needs an unlocked bootloader(any CM). It DOES need a specific bootstrap to work...
fleggett1 said:
Arggh! Locked bootloaders are a complete and utter PITA.
What I don't understand is why CM12 requires a specific bootloader to function. To me, that sounds like Windows needing a specific BIOS or bootstrap to work.
Does CM10 have this requirement as well?
BTW, thanks for the rom list. I'll definitely check 'em out.
Click to expand...
Click to collapse
Unfortunately you are stuck as no one has successfully downgraded the bootloader. Many developers have tried without success.
CyanogenMod will only work on an MDK device because the kernel is replaced during the flash process. This can only be accomplished with a custom recovery or unlocked bootloader.
FWIW, the MDK bootloader is technically not unlocked. There is a process called "loki" that took advantage of an exploit that was present on MDK which allowed the installation of a custom recovery. It did not unlock or overwrite the MDK recovery.
All bootloader versions past MDK have had this exploit closed.

Is there any chance of soft-bricking my LG G3 if/when i install BusyBox?

Hi there, I'm not entirely sure if this is the right place to post this.. I'm kind of a noob at this as I have just joined the XDA community.
I have a rooted Verizon LG G3 VS985 running android 5.1.1. Software version VS98535B
I have been recently trying new root apps, but I have noticed that some require busybox. I downloaded the installer, but was hesitant to install because of hearing rumors of soft-bricks and bootloops after installing BusyBox. I am curious if anyone has installed busybox with a similar phone and if they installed BusyBox successfully. I don't know if this a dumb question or not. I am just a bit hesitant to install busybox because my LG G3 is my daily driver, and if it gets screwed up, I'm screwed.
Please help me....
P.S. Sorry again if this is the wrong place to post this thread...
I never had a problem installing it on any device. That said, it's always wise to make a TWRP backup to the MicroSD card before any major changes especially root related.
roirraW "edor" ehT said:
I never had a problem installing it on any device. That said, it's always wise to make a TWRP backup to the MicroSD card before any major changes especially root related.
Click to expand...
Click to collapse
The thing is, I don't want to risk bricking by installing TWRP
zebereeh7 said:
The thing is, I don't want to risk bricking by installing TWRP
Click to expand...
Click to collapse
I don't know what to tell you then.
When we root, and what we do with our phones after we root, is not according to how the manufacturer meant for us to use our devices. There's always some chance of something not going according to plan. The chance of that is usually somewhat slim when following (reliable) directions exactly, but there's always going to be a chance. You can brick your device without even rooting. No one can give you any 100% assurances, although some may try, but nothing is ever 100%, you know what I mean?
No matter what you're likely to do, there's hardly any chance that you won't be able to recover your phone. If you have your Android O/S and apps configured just right for you, at least use the built-in LG Backup in Settings/Backup. Backup to MicroSD and copy anything you don't want to lose from your internal storage to your MicroSD card. If you ever have to Factory Reset or reflash the completely stock unrooted ROM in a way that'll cause your internal storage to be wiped, then you'll be happy you made that backup.
There are both unofficial and official tools to recover your phone to complete stock just like from the factory.
If you weren't at least open to some kind of possibility of bricking, you probably wouldn't have rooted to begin with. Or at least, I should say, if you're going to root you have to be prepared for the possibility of things happening in a way you didn't mean to.
Using a custom recovery like TWRP is the easiest way to get your phone back to a known good state while keeping root.
I'm not trying to convince you to put TWRP on your device, but I will always recommend making a backup in TWRP before making major changes. If you don't and things go wrong enough, then you have to accept the fact that you'll effectively do the work you would've had to do to put TWRP on in the first place, to recover your phone to a usable state.
Sorry if this sounds like a rant, I don't intend it that way.
roirraW "edor" ehT said:
I don't know what to tell you then.
When we root, and what we do with our phones after we root, is not according to how the manufacturer meant for us to use our devices. There's always some chance of something not going according to plan. The chance of that is usually somewhat slim when following (reliable) directions exactly, but there's always going to be a chance. You can brick your device without even rooting. No one can give you any 100% assurances, although some may try, but nothing is ever 100%, you know what I mean?
No matter what you're likely to do, there's hardly any chance that you won't be able to recover your phone. If you have your Android O/S and apps configured just right for you, at least use the built-in LG Backup in Settings/Backup. Backup to MicroSD and copy anything you don't want to lose from your internal storage to your MicroSD card. If you ever have to Factory Reset or reflash the completely stock unrooted ROM in a way that'll cause your internal storage to be wiped, then you'll be happy you made that backup.
There are both unofficial and official tools to recover your phone to complete stock just like from the factory.
If you weren't at least open to some kind of possibility of bricking, you probably wouldn't have rooted to begin with. Or at least, I should say, if you're going to root you have to be prepared for the possibility of things happening in a way you didn't mean to.
Using a custom recovery like TWRP is the easiest way to get your phone back to a known good state while keeping root.
I'm not trying to convince you to put TWRP on your device, but I will always recommend making a backup in TWRP before making major changes. If you don't and things go wrong enough, then you have to accept the fact that you'll effectively do the work you would've had to do to put TWRP on in the first place, to recover your phone to a usable state.
Sorry if this sounds like a rant, I don't intend it that way.
Click to expand...
Click to collapse
Thank you. It didn't sound like a rant at all, more like an honest answer. Now, my question is.. is TWRP or CWM even compatible with my phone? I've heard rumors of TWRP not working on 35B
zebereeh7 said:
Thank you. It didn't sound like a rant at all, more like an honest answer. Now, my question is.. is TWRP or CWM even compatible with my phone? I've heard rumors of TWRP not working on 35B
Click to expand...
Click to collapse
You're welcome!
Yes. As far as I know, TWRP is the only one actively maintained for the VS985. The way I recommend installing it is downgrading to 10B temporarily. Since you're on 35B you'll likely have to use the TOT method with the new .DLL gotten from the 35B KDZ, which you can find toward the bottom of a post in the General section by @hokiealumnus.
There are instructions multiple places, one is here http://lgflashtool.net/index.php/tot-method/, with the exception of using the new .DLL I mentioned instead.
After downgrading to 10B, which will wipe all user data and your internal storage, root with the Stump app, then use TWRP Manager from the Play Store to install the latest TWRP. Both rooting and putting TWRP get more complicated after 10B.
There may be other ways of getting TWRP working on 35B but this is the way I recommend and in my opinion is most foolproof and easiest.
If you do this just remember that you can use the built in LG Backup on what you have now, then you can restore it when you're back on 35B, or if you choose to flash the 46A ROM.
I'm sure it's possible to put TWRP directly on 35B by flashing the right partitions - the 12B aboot.img (bootloader) and laf.img (Download mode). If you would rather use a terminal emulator with superuser permissions and use the commands and partitions found in @bweN diorD 's stickied thread in the General section, you can go about it that way instead. I copy/paste the commands from a text file. If you type them manually and you type something wrong there's a greater chance something will be flashed wrong.
The way people temporarily brick their device on 35B trying to put TWRP on is using Flashify or TWRP Manager or terminal commands without having downgraded the bootloader and download partitions. Or I've seen users use @bender_007 's autorec TWRP app made for either 23C or 24B on 35B.
The fortune is - it´s easy fixable
I´ll work on one for 35b for sure

VS990, Help a noob out! =) ROM?

Question for those of you with experience on the V10. I just upgraded to the V20 (love it btw). My V10 is probably the first phone I never rooted, or loaded a ROM on. I've had many devices with custom roms in the past, however they were always carried branded (not unlocked) phones. Here is my question:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Thanks in advance..
X
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
xarius76 said:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Click to expand...
Click to collapse
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
beavis5706 said:
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
Click to expand...
Click to collapse
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
emdroidle said:
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
Click to expand...
Click to collapse
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
X
xarius76 said:
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
Click to expand...
Click to collapse
This is a substantial annoyance to many people, though there are some hopes of working around this...
xarius76 said:
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
Click to expand...
Click to collapse
I won't swear to it, but I was under the impression the updates come from LG, at which point it should still nominally update if brought to the EU. Failing that, LG Bridge should be able to get updates.
xarius76 said:
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
Click to expand...
Click to collapse
Remember, this is risky though hopeful.

Categories

Resources