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!
Related
Sorry if this is already answered, but I searched around and couldn't find it.
I tried to flash to CM12, but I have too old of a bootloader.
I reverted everything to stock, but I have never been able to get any OTA updates.
I downloaded the 322 update from huawei's site (from her http://consumer.huawei.com/us/support/downloads/detail/index.htm?id=52043) but when I try to install it from my SDCard I get the following error:
oemsbl version list check error!
'E ,write data error
Error:update.app is a invalid package
Error:SD card update failure,SD card update abort!
My end goal is to get on CM12 or some other rom that lets me get rid of all of the stock rom craziness.
Any ideas or can someone point me in a direction?
Thanks in advance!
bot2600 said:
Sorry if this is already answered, but I searched around and couldn't find it.
I tried to flash to CM12, but I have too old of a bootloader.
I reverted everything to stock, but I have never been able to get any OTA updates.
I downloaded the 322 update from huawei's site (from her http://consumer.huawei.com/us/support/downloads/detail/index.htm?id=52043) but when I try to install it from my SDCard I get the following error:
oemsbl version list check error!
'E ,write data error
Error:update.app is a invalid package
Error:SD card update failure,SD card update abort!
My end goal is to get on CM12 or some other rom that lets me get rid of all of the stock rom craziness.
Any ideas or can someone point me in a direction?
Thanks in advance!
Click to expand...
Click to collapse
Does your phone really have B146 or do you have B148 or B126?
You're on the right path. You must first successfully install B322 before you can install CM or any other non-stock ROMs.
Make sure you follow the Huawei B322 upgrade instructions very carefully.
See http://forum.xda-developers.com/asc...icial-b322-available-public-download-t3193929
divineBliss said:
Does your phone really have B146 or do you have B148 or B126?
You're on the right path. You must first successfully install B322 before you can install CM or any other non-stock ROMs.
Make sure you follow the Huawei B322 upgrade instructions very carefully.
See http://forum.xda-developers.com/asc...icial-b322-available-public-download-t3193929
Click to expand...
Click to collapse
Your edit is looking at the same thing I was looking at I had followed those directions but it looks like the issue is that I am on b146. The build number that shows up on my device is MT2-L03V100R001C642B146.
I guess I need to poke around and see if I can get it on B148 first, then try the update again, but B148 might have a prereq of B126
Madness!
Either way it is late, so I might just leave it be until tomorrow and pick back up. Thanks for the help!
Edit:trying to download B148 now, they are both 4.3, so who knows how this is going to go
I know Huawei has files and instructions to go from B322 back down to B148. I don't know anything about B146.
The B322 instructions reference B126 and B148, but no mention of B146.
divineBliss said:
I know Huawei has files and instructions to go from B322 back down to B148. I don't know anything about B146.
The B322 instructions reference B126 and B148, but no mention of B146.
Click to expand...
Click to collapse
Yep, I am downloading B148 and am going to try to install it. If that doesn't work, I will probably follow the soft bricked instructions to force wipe it back to B126 and then roll forward from there.
Good times!
B146 is Consumer Cellular phone. Not stock mate 2.
After all the madness, I hope you are not like some who don't like the new stuff and end up downgrading ... Time for me to zzzzzzz.
divineBliss said:
After all the madness, I hope you are not like some who don't like the new stuff and end up downgrading ... Time for me to zzzzzzz.
Click to expand...
Click to collapse
I was able to successfully install B126, but it is time for zzzz's here too. I doubt I will want to downgrade, my biggest complaint is the alternate default apps that Huawei uses cause some weird behaviors with bluetooth integration. Especially with my car, my headphones and the Pebble. And even if I use the normal apps (music etc) the integration doesnt work at all since their rom doesnt see them as the default system app.
Plus I have used CM on some other devices and always liked it
Moody66 said:
B146 is Consumer Cellular phone. Not stock mate 2.
Click to expand...
Click to collapse
I might have accidentally installed it at some point returning to stock. My phone is on of the sim unlocked phones from Walmart (not the prepaid, just the unlocked).
User error on my part Thanks for the info!
bot2600 said:
I was able to successfully install B126, but it is time for zzzz's here too. I doubt I will want to downgrade, my biggest complaint is the alternate default apps that Huawei uses cause some weird behaviors with bluetooth integration. Especially with my car, my headphones and the Pebble. And even if I use the normal apps (music etc) the integration doesnt work at all since their rom doesnt see them as the default system app.
Plus I have used CM on some other devices and always liked it
Click to expand...
Click to collapse
That awesome.... Should be downhill now.
I suggest you consider skipping CM and install PACROM or Carbon, which are both based on CM. I prefer PACROM. You should also consider Dual Boot / Multiboot - I use it to run multiple ROMs. You could install all three and see which one you like the best.
divineBliss said:
That awesome.... Should be downhill now.
I suggest you consider skipping CM and install PACROM or Carbon, which are both based on CM. I prefer PACROM. You should also consider Dual Boot / Multiboot - I use it to run multiple ROMs. You could install all three and see which one you like the best.
Click to expand...
Click to collapse
Thanks for the suggestion, I will definitely try all three. I am running around all day getting ready for Halloween so it probably won't happen today though, but I agree, things should be relatively straightforward from here
bot2600 said:
Thanks for the suggestion, I will definitely try all three. I am running around all day getting ready for Halloween so it probably won't happen today though, but I agree, things should be relatively straightforward from here
Click to expand...
Click to collapse
I'd personally recommend you install PACROM first ('cause you might like it so much, you won't bother with the other two ) , then once you are comfortable that you have a solid installation, after a few days go install Dual Boot/Multiboot : http://forum.xda-developers.com/ascend-mate2/themes-apps/patcher-multi-boot-t3222899/page1 in order to install some other ROMs.
divineBliss said:
I'd personally recommend you install PACROM first ('cause you might like it so much, you won't bother with the other two ) , then once you are comfortable that you have a solid installation, after a few days go install Dual Boot/Multiboot : http://forum.xda-developers.com/ascend-mate2/themes-apps/patcher-multi-boot-t3222899/page1 in order to install some other ROMs.
Click to expand...
Click to collapse
Thanks, I think I have just hosed it at this point. B126 still works, but it sees no OTA updates and won't take B148, B309 or B322 (guessing on the version numbers I tried). It continues to get the same error. I've reset the phone a couple times, wiped cache etc, but something somewhere makes it sad.
Thanks for the guidance and ideas, but I think the powers that be are telling me to get a new phone. I am trying to decide between the note 5, nexus 6p or wait for the new windows phone (950 xl). I could just buy another MT2L03, but if I am going to spend money on another phone, I might as well get one that I dont have to muck about with to clean up all of the forced apps etc
bot2600 said:
Thanks, I think I have just hosed it at this point. B126 still works, but it sees no OTA updates and won't take B148, B309 or B322 (guessing on the version numbers I tried). It continues to get the same error. I've reset the phone a couple times, wiped cache etc, but something somewhere makes it sad.
Thanks for the guidance and ideas, but I think the powers that be are telling me to get a new phone. I am trying to decide between the note 5, nexus 6p or wait for the new windows phone (950 xl). I could just buy another MT2L03, but if I am going to spend money on another phone, I might as well get one that I dont have to muck about with to clean up all of the forced apps etc
Click to expand...
Click to collapse
You have to go through the CC conversion. You can't just flash a different version to it.
Moody66 said:
You have to go through the CC conversion. You can't just flash a different version to it.
Click to expand...
Click to collapse
Thanks, I know somewhere along the line I must have flashed CC to it when I was restoring it (did a lot of tinkering when I first got it), but I am pretty sure it wasn't originally a CC phone. I picked it up from this link: http://www.walmart.com/ip/HUAWEI-As...M-4G-LTE-Android-Smartphone-Unlocked/42287058 which I read as just being unlocked, not being on any prepaid network.
Like I said earlier, I think it ending up with a CC rom on it somewhere along the way was just user error on my part
bot2600 said:
Thanks, I know somewhere along the line I must have flashed CC to it when I was restoring it (did a lot of tinkering when I first got it), but I am pretty sure it wasn't originally a CC phone. I picked it up from this link: http://www.walmart.com/ip/HUAWEI-As...M-4G-LTE-Android-Smartphone-Unlocked/42287058 which I read as just being unlocked, not being on any prepaid network.
Like I said earlier, I think it ending up with a CC rom on it somewhere along the way was just user error on my part
Click to expand...
Click to collapse
Use Xordos post for repairing a bricked phone. It will get you to b148.
Moody66 said:
Use Xordos post for repairing a bricked phone. It will get you to b148.
Click to expand...
Click to collapse
Ah, I used that post already but grabbed a B126 build instead. I will flip my recovery back and restore to B148 instead, good idea
Don't know what I was thinking at the time to go to B126, but it was really late, so that's my excuse
Edit: I see why I ended up on B126, he says to use the file TWRP_BACKUPS_stock-system-with-root.zip to restore the system partition, that file takes you back to B126, not B148.
Second Edit:I went back to see what files he had in his little area and saw there was a full B148.zip, so I flashed it with TWRP. I might try to update again from there, I assume I can't flash any higher as the B3xx builds the partitions changed, right?
I might have an answer, it looks like this version of the phone might not be supported, though its a bit unclear from the thread, but it does reference the phone that I have.
https://community.gethuawei.com/devices/mate_2/f/2/t/2672
Oh, and it looks like it did come with B146, I think its just time to get a new phone, thank you all for the time you spent though
bot2600 said:
I might have an answer, it looks like this version of the phone might not be supported, though its a bit unclear from the thread, but it does reference the phone that I have.
https://community.gethuawei.com/devices/mate_2/f/2/t/2672
Oh, and it looks like it did come with B146, I think its just time to get a new phone, thank you all for the time you spent though
Click to expand...
Click to collapse
I thought you said you have an MT2-L03 ....... does that not imply it's 16GB flash memory/ROM?
Did you put he B126 recovery back on the phone with your B126 ROM? My phone (non-CC) came out of the box with B148, then I went to B322, then PACROM, then Dual Boot, etc, etc.
Hopefully, you can get this to work ....... even if your heart is sent on a new phone. Then you can sell this one or give it to family, etc, etc .... maybe get some money out of it . Good luck.
divineBliss said:
I thought you said you have an MT2-L03 ....... does that not imply it's 16GB flash memory/ROM?
Did you put he B126 recovery back on the phone with your B126 ROM? My phone (non-CC) came out of the box with B148, then I went to B322, then PACROM, then Dual Boot, etc, etc.
Hopefully, you can get this to work ....... even if your heart is sent on a new phone. Then you can sell this one or give it to family, etc, etc .... maybe get some money out of it . Good luck.
Click to expand...
Click to collapse
Looks like I was wrong, mine is 16 gig, so ignore that link
I am not set on a new phone, but I am set on being done mucking about, I have a couple apps like RSA token things etc that are a pain when I wipe my phones. I am pretty sure I bought mine before B148 came out, but who knows, it all melts together. I write mobile apps for work so I have a bunch of random iphone, android phones and even a couple windows phones lying around, but this one has me so spoiled by its big screen, that I can't imagine going back to anything 5" or smaller, and the wife claimed the 6S plus, so what are you going to do
I might mess around with this a bit more, but Monday fast approaches and it is time to be productive again
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.
Hi,
I ordered an LG Exceed 2 VS450PP, but haven't received it yet. Looks like the device can be rooted and the bootloader unlocked, but there don't seem to be any custom ROMs avaialble for the device.
However, I found this link here:
http://downloads.hostingsharedbox.com/rashed/msm8610/vs450/
This seems to be an unofficial CM12.1 release for this device. Does anybody know if this is legit? Thanks
Well, I've read about some customs roms for this device by some developer, but it seemed faulty and made me wary about using them. Can't really remember if it was this rom, but it's probable.
Now, another thing I'd like to point out is that the latest LG Exceed 2 models seem to be updated, so they aren't anymore VS450PP, instead now they are VS450PP2! At least that's my case, I ordered mine from Amazon on late Christmas just so you guys know the date. So, since the device received an update, I don't think it safe trying methods intended for older versions.
About rooting, I just got mine today and when I tried using Towel Root it didn't work, but thanks to this I was able to root, using the very same Towel Root. I quote:
'Just hitting Make it Rain gave me the message that my phone wasn’t supported, but after I changed the Mod string to 1337 0 0 0 4 0 it ran fine.'
By the way, the root seems to be permanent. Rebooted the phone and no changes.
What I'd like to do, though, is installing, or at least be able to boot into recovery to make a backup before wiping bloatware. But since I have no guarantee I don't know what to do yet. Here's unbloating guide that might prove useful:
https://www.reddit.com/r/perktv/comments/3f5kym/deploying_a_new_lg_exceed_2_howto/
dullian said:
Well, I've read about some customs roms for this device by some developer, but it seemed faulty and made me wary about using them. Can't really remember if it was this rom, but it's probable.
Now, another thing I'd like to point out is that the latest LG Exceed 2 models seem to be updated, so they aren't anymore VS450PP, instead now they are VS450PP2! At least that's my case, I ordered mine from Amazon on late Christmas just so you guys know the date. So, since the device received an update, I don't think it safe trying methods intended for older versions.
About rooting, I just got mine today and when I tried using Towel Root it didn't work, but thanks to this I was able to root, using the very same Towel Root. I quote:
'Just hitting Make it Rain gave me the message that my phone wasn’t supported, but after I changed the Mod string to 1337 0 0 0 4 0 it ran fine.'
By the way, the root seems to be permanent. Rebooted the phone and no changes.
What I'd like to do, though, is installing, or at least be able to boot into recovery to make a backup before wiping bloatware. But since I have no guarantee I don't know what to do yet. Here's unbloating guide that might prove useful:
https://www.reddit.com/r/perktv/comments/3f5kym/deploying_a_new_lg_exceed_2_howto/
Click to expand...
Click to collapse
Well, I am hoping I will be able to install custom reocvery, like TWRP, to make a backup. Then debloating as well as trying out the ROM above wouldn't be risky.
Did you try the instructions here? http://techchomps.com/how-to-install-twrp-recovery-on-the-lg-exceed-2-vs450pp/
yeah, I'd like to install twerp, but since my version is VS450pp2 I'm still wary of doing it, and I'd much prefer not messing with it at least until I found a stock rom of it.
I've also seen this method: http://androidforums.com/threads/lg-exeed-2-twrp-2-8-6.944072/
But then again I don't want to try since it's meant for VS450pp, not VS450pp2. Yeah, it might work fine, but seriously don't wanna risk it, at least not yet.
Tell us if you decide to try installing twerp.
I've also seen that you can make a backup stock rom of your, but don't know if I making one of my phone would be a good idea since I already rooted and some bloatware I disabled doesn't seem to work anyone, so that might compromise the 'pureness' of the rom. Should have done it when the phone was fresh out of the box xD But then again I don't know if making those KDZ roms requires root or not.
I just used the towel root method using the Mod strings from previous post and used the apk you linked to install the TWRP Recovery with out issues. It completed a backup to the SD card with out issues also.
In this link http://androidforums.com/threads/lg-exceed-2-resources.979449/
It states "If you have a vs450pp2 model just downgrade with the vs450pp1 kzd in download mode"
if you look on the bar code of the box it shows SKU LG-VS450PP and Software version VS450PP2
So it would seem the phone has not changed just the base software that comes installed.
dullian said:
yeah, I'd like to install twerp, but since my version is VS450pp2 I'm still wary of doing it, and I'd much prefer not messing with it at least until I found a stock rom of it.
I've also seen this method: http://androidforums.com/threads/lg-exeed-2-twrp-2-8-6.944072/
But then again I don't want to try since it's meant for VS450pp, not VS450pp2. Yeah, it might work fine, but seriously don't wanna risk it, at least not yet.
Tell us if you decide to try installing twerp.
I've also seen that you can make a backup stock rom of your, but don't know if I making one of my phone would be a good idea since I already rooted and some bloatware I disabled doesn't seem to work anyone, so that might compromise the 'pureness' of the rom. Should have done it when the phone was fresh out of the box xD But then again I don't know if making those KDZ roms requires root or not.
Click to expand...
Click to collapse
this is one of the best ROMs I've seen yet for the VS450pp and its 5.1.1 based! all the other ROMs available are 4.4.2 based.
Fixed home button by editing Generic.kl from /system/usr/keylayout changed key 102 to HOME and key 172 to MOVE_HOME
Bugs:
home button does not work (fixed)
notification ring on constantly
No sd card seen
Rear camera does not work.
After a fairly stressful 48hours trying to fix my tf700t after messing up rooting it I have learned to be more cautions. Im looking for for some advice before doing anything else with my LG G3.
Its already rooted. I did that almost immediately after getting it, but I haven't done anything else since. I would now like to upgrade to a quicker, cleaner ROM to help with some of the performance issues.
Here are my Specs.
Root, but not Custom recovery.
Model VS985G
Software VS98523C
Android 5.0.1
Questions.
1. Should I factory default first, then use the new one-click to re-root my phone.
2. Should I install a older version of TWRP first, then upgrade to a more recent software release, then upgrade to a newer TWRP before moving to a 6.0 based rom.
3. Any recommendations on a fast and stable ROM. I don't need anything flashy, but performance is important to me.
4. Will the new ROMS work with PDAnet USB teather. Which is very important and dear to me.
5. Will I still be able to use my Wifi hotspot. Also very important to me
6. Will it get rid of the annoying voice mate popping up when I plug in some headphones.
Any help appreciated. I tried searching but couldn't really find definitive answers to my questions.
Hey, Thanks for asking the questions. here are some answers (p.s. i dont have my g3 right now will have it fixed by saturday.)
1. No, you dont have to, if you feel like you do go ahead. but once you get a custom recovery just be sure to back up the stock rom.
2. Since i have to redo my G3, i have no idea what the stock software my FrenkinG3 (The mobo died in mine so i bought a broken one and am putting the mobo in mine.) will have so, i dont know if i need to use the special bump'ed twrp first or not, ill let you know what happens, im am going to use the flashify to try to just flash the latest twrp 3
3. Before it broke, i really really liked Resurrection Remix rom. IMO it was the best. but for you probably just CM13. obviously i really don't know it has been since early January since i have had my g3. so maybe things have changed, but i cant assume they changed too much.
4. I dont see why not. If an Android 6 rom wont work try something like CM12.1 or a different Lollipop rom.
5. Yes, any custom rom you install, (at least in my experiance) will have the hotspot ready to go.
6. HAHAHAHAHAHAHAHA, probably not. i know it never really happened to me, but my buddy had it happen to him all of the time. He solved it by freezing one of the google apps.
If you have any other questions let me know. Happy to help any time.
p.s. Use Flashify (for root users), on the app store to flash recovery. i used it to update my recovery on my g3 many times. and will use it again soon.
6. Will it get rid of the annoying voice mate popping up when I plug in some headphones.
Click to expand...
Click to collapse
I had the same problem, and it turned out to be a faulty aux port on the phones mainboard. It is a relatively easy replacement all you need is YouTube, something thin to pry it up, and a Philips head screwdriver size 0, haven't had an issue since and now the G3 properly recognizes headphones vs line in vs mic...
RussTdesign said:
1. Should I factory default first, then use the new one-click to re-root my phone.
Click to expand...
Click to collapse
You don't need to. Do it if you are super paranoid about clean installs.
2. Should I install a older version of TWRP first, then upgrade to a more recent software release, then upgrade to a newer TWRP before moving to a 6.0 based rom.
Click to expand...
Click to collapse
You should be fine installing the most recent version of TWRP (3.0.0?) It will be compatible with non-marshmallow versions.
3. Any recommendations on a fast and stable ROM. I don't need anything flashy, but performance is important to me.
Click to expand...
Click to collapse
I've tried several and my favorite is Jasmine 9.1
It is stock Lollipop based with moderate debloating for speed and is compatible with xposed and the LG G3 Tweaksbox.
Alternatively xdabbebs 2.0 is similar and many people love it. SkyDragon is similar to Jasmine but has a custom kernel for speed tweaks and other minor stock mods.
Personally I stay on modified stock because the stock camera is very good and you loose access to it on AOSP Roms.
If you want marshmallow I recommend doing a 47A install and using road warrior's debloating scripts. But MAKE 100% SURE you have Rooted and installed custom recovery BEFORE instill ng ANY Marshmallow Stock based ROM.
5. Will I still be able to use my Wifi hotspot. Also very important to me
Click to expand...
Click to collapse
Using a modified stock ROM should allow for Wifi hotspot.
Mine still works.
6. Will it get rid of the annoying voice mate popping up when I plug in some headphones.
Click to expand...
Click to collapse
Xposed Framework + LG G3 Tweaksbox has an option for disabling the audio warnings (among other things...)
Best of luck. PM me if you want longer answers.
I bought a LG V10 today i dont know if its used or new (LOL) any way to find that out i checked IMEI says its orignal talked to people at LG USA they said its Original Here are my questions:
1) How to know if your phone is Legit like New + Lasting?( in my country they replicate used to orignal or fake to orignal)
2) How to Root LG V10? (i tried it with other phones i broke them)
3) Suggest Some Recommended Apps and ROMS?
4)I have seen a youtube video of xdadevelopers they were talking how you can overclock or under clock your device can i do that with my phone?
5)Last Question How can i myself from the infamous Bootloop? (Any Suggestion, Tricks Ways)
I am new here i need your help for not doing a rookie mistake....
1) Get the LG Phone Info app on the Google Play Market and as long as that shows "OK" in the Original info (the first box after you click the Get Information button) then your device is an original and not something that's been modified on a firmware level.
2) If you have Lollipop or Marshmallow rooting is fairly easy by comparison to Nougat. If you have Nougat on it already things are basically a stop - there is no working root for Nougat at this moment IF the device has been upgraded to Nougat using T-Mobile's OTA direct from them. Once that's been installed there's no turning back and no working root at this point but some devs are working on it, no guarantees they'll ever be able to create one.
If the device has Lollipop or Marshmallow on it you can get it rooted. The best course of action is to go from Lollipop to Marshmallow (the last Marshmallow build is 20l and that's an "L" there, lowercase, not 1 or i/I) and then what you'll need to do is get TWRP on it (that step is critical) then you would flash this modified update.zip to get to Nougat build 30b on it. runningak3d modified that update.zip file so it does NOT overwrite the recovery partition and you get to keep TWRP installed for flashing purposes. If you use T-Mobile's official OTA update.zip you'll be stuck, not able to flash anything including TWRP, or get rooted, etc.
So, again, the process is get to Marshmallow 20l, then get TWRP installed - at that point root is not necessary just to get the modified 20b update.zip on it. Then use TWRP to flash that modified 20b update.zip at which point it'll be Nougat, and THEN you can flash SuperSU with TWRP and you end up with a V10 running Nougat and rooted, that's the only method at this point.
runningak3d said he (or she, sorry, I just don't know) would try to create another modified update.zip which is pre-rooted so when installed you've got root/SuperSU ready to go but it's barely a minute to install SuperSU manually after flashing that modified 20b update.zip so it's not really a big issue there.
3) There are no custom ROMs for the V10 at this point, no Lineage, no AOSP, nothing really. There are some modified stock ROMs iirc but nothing that's totally custom and we V10 owners are still hoping some dev will take some time and create an unofficial Lineage build for the V10 based on Nougat (or even Marshmallow, I don't really care which Android version it's based on just that it's Lineage through and through). It seems pretty screwy that nobody seems to care about the V10 enough to have created a custom ROM but that's how it goes sometimes. The V10 is like an LG G4 on steroids in some respects, basically the same hardware overall with some minor differences (the second screen, of course, but I don't even use that on mine so I don't care about it at all).
I just wanted Lineage because it's so lean and efficient compared to any stock ROM and of course the potential for having a custom kernel with more governor support and other aspects is the big draw for me so, the hope remains that someone out there will take some pity on us woeful V10 owners and drop a Lineage build someday.
As for apps, well, that's entirely up to you and what you use your V10 for, and since nobody knows that but you then it'll be up to you to decide what kinds of apps you're going to be looking for.
4) Over-and-underclocking requires a custom kernel that allows for such things, and the stock kernel that's available (I think there was one custom kernel but it's just a modified stock one with limited additional capabilities) simply doesn't allow for such alterations. The V10 is quite fast on its own natively so, I can't imagine why someone would need to overclock it - I can understand WHY someone would WANT to do it, of course, but as for an actual need to do it, nope.
As for underclocking, that would save battery and be what I'd call a need in some respects, but again there just doesn't seem to be any developer out there that gives a damn about the V10 sadly. I wish I had spent more time learning how to create custom ROMs over the years and trick out some kernels as well using the provided source from manufacturers of these smartphones but I never did.
5) There is no way to prevent the potential bootloop issue which affects the G3/G4/G5/G6 (I saw one report so it could be bogus for the G6) and also the V10/V20 (seen two reports for the V20) and the Nexus 5x because it's a hardware manufacturing defect related to how the Snapdragon SoCs are mounted on the motherboards. There's nothing that you can do about it and there's no way to know for sure if the V10 you have will develop problems because of it or not, all you can do is use it and be done with it and hope for the best. Again, there is no fix and there's no way to know or prevent it from happening so, no matter what so called "fix" you read about or see a video about, it's all BS and best avoided.
My recommendation: since you just got the V10, go to LG's website and register the V10 in your name (might have to create an account) and then say you bought it in March, April, or May of 2017 (just a few months ago) and that will give you warranty protection through at least mid-2018. If you do that and it does bootloop on you, LG will replace it through the warranty period. Don't register it and you're out of luck if it does bootloop on you.
Hope this helps...