WHY¿ The vs985has great Specs!
It has a locked boot loader and the only workaround method so far, Bump - developed by Team Codefire, was leaked by a selfish idiot, compromising the method so it will probably be patched in a future (Lollipop ?) OTA, leaving us owners with no root and no custom recovery.
Sent from my VS985 4G using Tapatalk
The method was compromised the minute codefire announced. Their method getting reverse engineered has nothing to do with whether out not lg makes an update which breaks it's functionality. If that comes to pass, it's simple...don't update. Meantime, development is just beginning as lollipop rolls out. Don't believe everything you hear.
theistus said:
The method was compromised the minute codefire announced. Their method getting reverse engineered has nothing to do with whether out not lg makes an update which breaks it's functionality. If that comes to pass, it's simple...don't update. Meantime, development is just beginning as lollipop rolls out. Don't believe everything you hear.
Click to expand...
Click to collapse
Yea, I won't update. I'm on a 5.0.1 and it's great. I have wife's on KZD 10b and TB system updates frozen because it took 11c before I knew it.
foundingfathersfan2 said:
WHY¿ The vs985has great Specs!
Click to expand...
Click to collapse
First off, where did you here this from? I haven't heard it.
Also, there have been several OTAs since "bump" was released and it hasn't been patched so far. Bump was released back in October and we just got a new update for the VZW model (VS985) in December (v 12B) and you can downgrade from that and install TWRP on it. Plus, there are already "rooted/bumped" images for you to flash if you don't want to take the official OTAs (of course, you have to tell SuperSU to preserve root over the OTAs and you must NOT be bumped in order to take the OTAs). I'm on the official 12B OTA and then flashed TWRP, so I'm bumped. So, at this time, the phone is still bump-able even at the latest version.
Also, reports from overseas where some are getting LP have been able to downgrade back to a Kit Kat. That might change here in the United States, but definitely, I would hold off on taking any more OTAs until it can be verified if it fixes the "bump" exploit or not.
But, so far, ROMs are being developed, etc. So, I have as of yet to hear about devs not wanting to develop for this phone anymore.
Again, if you could point us to some sources, that would be good because I would like to know as well, but I don't go by hearsay.
iBolski said:
First off, where did you here this from? I haven't heard it.
Also, there have been several OTAs since "bump" was released and it hasn't been patched so far. Bump was released back in October and we just got a new update for the VZW model (VS985) in December (v 12B) and you can downgrade from that and install TWRP on it. Plus, there are already "rooted/bumped" images for you to flash if you don't want to take the official OTAs (of course, you have to tell SuperSU to preserve root over the OTAs and you must NOT be bumped in order to take the OTAs). I'm on the official 12B OTA and then flashed TWRP, so I'm bumped. So, at this time, the phone is still bump-able even at the latest version.
Also, reports from overseas where some are getting LP have been able to downgrade back to a Kit Kat. That might change here in the United States, but definitely, I would hold off on taking any more OTAs until it can be verified if it fixes the "bump" exploit or not.
But, so far, ROMs are being developed, etc. So, I have as of yet to hear about devs not wanting to develop for this phone anymore.
Again, if you could point us to some sources, that would be good because I would like to know as well, but I don't go by hearsay.
Click to expand...
Click to collapse
Its just something I've seen on some ROM Threads. It may just be hearsay. I hope that's all it is.
foundingfathersfan2 said:
Its just something I've seen on some ROM Threads. It may just be hearsay. I hope that's all it is.
Click to expand...
Click to collapse
Okay, thanks. I haven't seen it in ROM threads and ROM threads normally don't have the devs posting there, so it's probably from people who don't really know what they're talking about, or it could be someone who represents the devs and posts updates for them. Either way, I'll keep an eye out on that and see if I can determine who it's coming from. Just curious because I definitely would like to know.
I look at this differently. Team Codefire figured out the only way known, so far, to flash a custom recovery and/or kernel and have it boot past the security check. Without that method (Bump), nothing is possible other than stuff based on stock firmware, like Jasmine.
Though the bump method was arguably already compromised by its use through the bump website, and that had its own drawbacks for sure (no nightly builds from CM, for example), there was an "understanding" between Team Codefire and LG, at least hinted at by Autoprime. The full public release of the bump method upset Team Codefire enough for them to abandon further work on the LG G3 altogether, and no one else has picked up on it or come up with any alternatives. You cannot even root any version other than the original stock v10b to this day.
So, though Roms are currently installable since you can still roll-back to v10b, root, and flash a bumped TWRP, folks getting new G3s in the future will likely be stuck with a totally locked down firmware, like we original purchasers thought we might be stuck until bump. For months...
How much Dev interest will remain if that happens ?
Will many Dev teams want to even just build for the G3 if only a subset of owners can install their works ?
trent999 said:
I look at this differently. Team Codefire figured out the only way known, so far, to flash a custom recovery and/or kernel and have it boot past the security check. Without that method (Bump), nothing is possible other than stuff based on stock firmware, like Jasmine.
Though the bump method was arguably already compromised by its use through the bump website, and that had its own drawbacks for sure (no nightly builds from CM, for example), there was an "understanding" between Team Codefire and LG, at least hinted at by Autoprime. The full public release of the bump method upset Team Codefire enough for them to abandon further work on the LG G3 altogether, and no one else has picked up on it or come up with any alternatives. You cannot even root any version other than the original stock v10b to this day.
So, though Roms are currently installable since you can still roll-back to v10b, root, and flash a bumped TWRP, folks getting new G3s in the future will likely be stuck with a totally locked down firmware, like we original purchasers thought we might be stuck until bump. For months...
How much Dev interest will remain if that happens ?
Will many Dev teams want to even just build for the G3 if only a subset of owners can install their works ?
Click to expand...
Click to collapse
Crap. Your right, we are almost a subset.
Look..there will always be a work around.. as long as there is someone out there with a need, there will be someone able to provide it.. The truth stands for all makes and models of smartphone.. The ROM build craze goes on and on, and eventually the phone is outdated and dev passes over it to a new model to play with.. BEST advice for anyone is learn to write if youre not a progressive upgrader
The whole scene is a revolving door, and like most things good, eventually theres an end...
Does anyone know if there are any lollipop roms out yet and if so where I can find them. Also, I'm looking for a good lollipop rom where everything works. If there lollipop roms what version of recovery of twrp do I use? I'm currently on 2.8.2. Thanks
As for the second question, 2.8.2 will work fine. There is a new version, 2.8.3 ,but it's not really necessary.
Where to find Lollipop ROMs? Assuming you're on Sprint, look in the development and original development sub-forums here in the Sprint G3 forum. Read the threads and see what works and what doesn't. At the moment, I think all the AOSP Lollipop ROMs have some bugs. Some of them more than others, and some of the bugs might not matter much to you.
Development on the G3 hasn't been going on for very long. It'll be a little bit longer before all the issues are worked out.
Hi, I posted this in the main troubleshooting thread. It includes a video. I am not a very good phone tech, but I can BASH my way through some basic stuff.
http://forum.xda-developers.com/xperia-z-ultra/help/lollipop-update-crashes-released-help-t3212525
I DO have my TA partition backed up. I haven't tried restoring it. Thanks!
The main issue here is that there are only a few people around here with the GPe model, and the GPe doesn't work like the regular one, so it's hard for us to help you. If I were you, I would update manually to 5.1 by downloading the update.zip for the Togari GPe and flash it in a terminal. That's what people with Nexus' do when they don't wanna wait for the OTA. It's as official as the OTA.
OR you can flash a custom ROM, like CyanogenMod 12.1 (5.1.1). Or Candy 5. Or something else.
Deleted...
I'm sorry if I'm asking questions that have been answered here, but I am new to rooting and am suffering from information overload. I get confused about references to stock Android and whether this means the stock Verizon version or the untouched Android that Nexus devices get.
I'm using this phone through Tracfone and thus do not receive OTA updates. This also makes all of the Verizon bloat all the more useless. I'm not looking for a special ROM, I just want vanilla Android that will receive new updates over wifi.
Is this possible?
Hi. Stock means what LG/Verizon put on our phone. I understand the confusion, though, and I used to be confused about it too. It's best to call "pure" or "purer" Android AOSP, or from what I've read there isn't any true full AOSP that's user compiled any more - they're all more or less based on CyanogenMod, so "AOSP" or "CM", but CM is more realistic. AOSP is what Nexus has, although of course, it can be called stock too since in that case they're one in the same unless you're running a user-compiled AOSP in which case if it were me I would call it something else to distinguish it from the stock AOSP on Nexus.
CyanogenMod-based ROMs will be the closest you'll get. CM13 for Marshmallow. I don't know if CM gets OTAs, I think sometimes in the past they have, at least once a version of CM has gone "final" (not sure if CM13 has gone final). Some ROMs that are based on CM have OTAs too.
I can't speak as to how well these work. I used to use CM-based ROMs more on other phones but for me, stock works so much more reliably/predictably and overall smoother than AOSP/CM. AOSP/CM and International-based stock ROMs always seem to have some unreliableness factor.
If you want a debloated but reliable ROM based on stock (which would receive OTAs if there ever are any more, but it's doubtful there will be), use @xdabbeb 's stock 47A (Marshmallow) firmware along with either my debloat zips or the debloat generator made by another user, which I link to in the third post of the 47A firmware thread in the Development section. The debloat zips/generator are also linked to in my signature below.
Overall, personally, I consider @xdabbeb 's VS985 v2.0 ROM, based on 35B (5.1.1) the best ROM, but I'm currently using the stock 47A firmware with complete debloating and am satisfied with it.
I use Xposed and G3TweaksBox to get some features on stock ROMs that I consider a must.
The easiest way to flash the ROM I mentioned is (if you're not rooted yet), first tell us what version of the stock ROM you're on. If it's anything but 23C or 24B, the absolute easiest way to root and put custom recovery on is by downgrading to 10B using the TOT method and the .DLL that's extracted from the 35B KDZ. Links to the TOT and DLL in @annoyingduck 's stickied return to stock thread in the General section, also the first link in my signature below.
Directions and the links to the program to flash TOTs, you'll have to Google for.
In the future, please ask all questions in the Q&A section. I'll ask a moderator to move this thread. Thanks!
Thanks for the response. I am definitely most interested in reliability. After reading your post, I think I might just stick with the stock Verizon image and wait for the upgrade tool to release Marshmallow.
Nate Wrigley said:
Thanks for the response. I am definitely most interested in reliability. After reading your post, I think I might just stick with the stock Verizon image and wait for the upgrade tool to release Marshmallow.
Click to expand...
Click to collapse
You're welcome! Or if I didn't say it before, you can flash the 47A KDZ with LG Flash Tool 2014, preferably with the CSE option which will wipe all data including internal storage, so use the built in LG Backup and also move what you want to keep from your internal storage.
I have an LG G5 H831 from WIND/Freedom mobile which I recently upgraded to Nougat.
For some reason I don't like the new update and I'd like to revert back to the stock firmware. Is this possible?
I've looked around this forum and I couldn't find anything helpful.
Please help.
Jerry+ said:
I have an LG G5 H831 from WIND/Freedom mobile which I recently upgraded to Nougat.
For some reason I don't like the new update and I'd like to revert back to the stock firmware. Is this possible?
I've looked around this forum and I couldn't find anything helpful.
Please help.
Click to expand...
Click to collapse
I agree. Android v7 is the Windows ME of mobile operating systems. Too many great features removed, excused by positive sounding mumblings and overbearing rhetoric.
If you can find the LG-H831 DLL for LGUP then you can flash a H83110d_00_0711.kdz ROM image (you can find or I can put up for you). I cannot find a H831 DLL for LGUP anywhere though so if anyone has one please let us know.
I'm a complete noob when it comes to flashing LG phones.
Is there a tutorial I can follow?
Where can I download the files needed?
I'm very happy with this phone btw. It's very snappy, works well and the camera is simply awesome!
It seems to me that Nougat is using more RAM than Marshmallow and that concerns me a bit.
I forgot to mention something.
Few days ago I was able to find the KDZ files here, but they were for Rogers/Fido. I was very cautious and I did not flash them.