Related
My wife insisted on remaining stock on her VS985... Until the lolliplop update. She wants her kitkat back and I cannot find a way to do it yet. I have successfully rooted it but cannot get a custom recovery install to stick. I have tried the methods that I know for the kitkat version, to install philz and twrp and get an error message upon reboot. Has an exploit been figured out yet to downgrade from stock lollipop?
I use the kdz method to return to 10b stock http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
After you are rooted http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906 and on 10b i use flashify to flash the twrp img. From there just find a nice stock KK rom for her.
This is just how i do things and find it fairly easy.
Or directly flash the 12B KDZ, use the new root script if you want her phone rooted and use Flashily from the Play Store to flash TWRP.
roirraW "edor" ehT said:
Or directly flash the 12B KDZ, use the new root script if you want her phone rooted and use Flashily from the Play Store to flash TWRP.
Click to expand...
Click to collapse
I wasn't aware of the new root script. Got anymore info or a link to this. Can't say I've seen anything about it.
Sent from my VS985 4G using XDA Free mobile app
Edde3d said:
I wasn't aware of the new root script. Got anymore info or a link to this. Can't say I've seen anything about it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Thank you both!
The One Click Root works like a boss.
It worked effortlessly on my new phone.
I sticking with 12B rooted too, as it seems to be a good solid O/S.
I rooted without issue, I was stuck at installing twrp. I did get it to work, using autorec! Slapped twrp in, and romed out to jasmine 4. I hope that this helps others out down the road.
Hey everyone,
I was able to root my LG G3 with the help of the XDA forms so I figured maybe someone could help me out here. I am running the STOCK Verizon Rom that came with the phone. I wanted to know if there is a customer kernal I can install to improve battery life and/or if anyone knows the good Tricker Mod settings to set up so the battery life improves, that would be helpful as well.
Thanks for the help everyone.
TheBull50 said:
Hey everyone,
I was able to root my LG G3 with the help of the XDA forms so I figured maybe someone could help me out here. I am running the STOCK Verizon Rom that came with the phone. I wanted to know if there is a customer kernal I can install to improve battery life and/or if anyone knows the good Tricker Mod settings to set up so the battery life improves, that would be helpful as well.
Thanks for the help everyone.
Click to expand...
Click to collapse
You will need to install TWRP to install a custom kernel.
I am running Jasmine ROM 8.0 with the Skydragon 4.2 Kernel with great battery life.
Great. Thank you. I was able to install twrp and installed sky dragon
Kernel to my Verizon stock Rom. Seems to be doing just fine ☺
TheBull50 said:
Great. Thank you. I was able to install twrp and installed sky dragon
Kernel to my Verizon stock Rom. Seems to be doing just fine ☺
Click to expand...
Click to collapse
Another good one is Gabriel Kernel
TheBull50 said:
Hey everyone,
I was able to root my LG G3 with the help of the XDA forms so I figured maybe someone could help me out here. I am running the STOCK Verizon Rom that came with the phone. I wanted to know if there is a customer kernal I can install to improve battery life and/or if anyone knows the good Tricker Mod settings to set up so the battery life improves, that would be helpful as well.
Thanks for the help everyone.
Click to expand...
Click to collapse
Can I ask what method you used to root after 24B update? I have tried a few different methods I found on XDA and all of them just hang at the part where it should push root to the phone. Thanks.
garyj1 said:
Can I ask what method you used to root after 24B update? I have tried a few different methods I found on XDA and all of them just hang at the part where it should push root to the phone. Thanks.
Click to expand...
Click to collapse
[GUIDE][ROOT]Newest Root Method for LG devices
garyj1 said:
Can I ask what method you used to root after 24B update? I have tried a few different methods I found on XDA and all of them just hang at the part where it should push root to the phone. Thanks.
Click to expand...
Click to collapse
Besides using the root method @quadjacks linked to below, just wanted to make sure you know that in order to root 24B, you have to come from a string of at least two OTAs. In other words, if you at any time flashed the 23C KDZ, then after you take the 24B OTA, you won't be able to root the phone, at least that's our experience.
You will be able to root it (not using the one-click but the one @quadjacks links to) if you flash the 12B KDZ, then OTA to 23C, then OTA to 24B.
quadjacks said:
[URL=" Root Method for LG devices[/URL]
Click to expand...
Click to collapse
roirraW "edor" ehT said:
Besides using the root method @quadjacks linked to below, just wanted to make sure you know that in order to root 24B, you have to come from a string of at least two OTAs. In other words, if you at any time flashed the 23C KDZ, then after you take the 24B OTA, you won't be able to root the phone, at least that's our experience.
You will be able to root it (not using the one-click but the one @quadjacks links to) if you flash the 12B KDZ, then OTA to 23C, then OTA to 24B.
Click to expand...
Click to collapse
I flashed the 23C KDZ and then OTA to 24B. Root works fine.
Sent from my VS985 4G using Tapatalk
NBreunig3 said:
I flashed the 23C KDZ and then OTA to 24B. Root works fine.
Click to expand...
Click to collapse
For most people who have tried and reported back, including myself several times and with all the root methods I could think of, that didn't work, but a couple of people have reported being able to root after OTAing from 23C.
roirraW "edor" ehT said:
For most people who have tried and reported back, including myself several times and with all the root methods I could think of, that didn't work, but a couple of people have reported being able to root after OTAing from 23C.
Click to expand...
Click to collapse
There is a 24B KDZ available. I also have used this KDZ and then been able to root.
Sent from my VS985 4G using Tapatalk
NBreunig3 said:
There is a 24B KDZ available. I also have used this KDZ and then been able to root.
Click to expand...
Click to collapse
I'm aware of that, too - I posted the link to it, but I haven't had the inclination to flash it and try rooting after. I won't be surprised since the first method I mentioned in the previous message, flashing the 23C KDZ and taking the OTA, then trying to root, didn't work myself and several others that it won't work for me with flashing the 24B KDZ directly, but I'm just speculating. I'm sure I'll attempt it again when I have a need to reset to completely stock unrooted again unless by that time I'm in too much of a hurry to take another new OTA that may come and try to root that first.
roirraW "edor" ehT said:
I'm aware of that, too - I posted the link to it, but I haven't had the inclination to flash it and try rooting after. I won't be surprised since the first method I mentioned in the previous message, flashing the 23C KDZ and taking the OTA, then trying to root, didn't work myself and several others that it won't work for me with flashing the 24B KDZ directly, but I'm just speculating. I'm sure I'll attempt it again when I have a need to reset to completely stock unrooted again unless by that time I'm in too much of a hurry to take another new OTA that may come and try to root that first.
Click to expand...
Click to collapse
I was able to root after flashing the 24B KDZ. The root.bat did not work (hung on the installing root part). But I was able to do option 2 and manually push the files and install root with one minor change. The first time I ran the Send_Command to push root it hung, I did a ctrl-C on it then ran it again right after and it went through. Then I did the send_command reboot and the phone rebooted and was rooted when it came up. I did this a couple of times and had the same results every time, first send_command would hang and I had to break out of it (ctrl-c) the send_commands after that worked fine. Not sure why that is but that is what worked for me. Just wanted to share in case anyone is having the same problem.
And then after rooting 24B, how to install TWRP??? I tried and got the Security Error message. Help would be appreciated.
sd_N said:
And then after rooting 24B, how to install TWRP??? I tried and got the Security Error message. Help would be appreciated.
Click to expand...
Click to collapse
I downloaded version 2.8.7.0 then used adb to install with the instructions from this thread...
http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
sd_N said:
And then after rooting 24B, how to install TWRP??? I tried and got the Security Error message. Help would be appreciated.
Click to expand...
Click to collapse
Just to present another option, in the Play Store, search for:
Code:
autorec VS985
It'll install TWRP v2.8.6.x and downgrade your bootloader, which you can then update TWRP to the latest from within the "old" version.
garyj1 said:
I downloaded version 2.8.7.0 then used adb to install with the instructions from this thread...
[/QUOTE]
Click to expand...
Click to collapse
Need to check if I have the 24B...... and Thanks!!
I spent the greater part of the evening trying to root my LG G3 VS985 unsuccessfully, but I don't recall if it is the 24B. I got it off eBay to upgrade my current RazrHD which is hopelessly underpowered - but it is rooted, and didn't want to lose my unlimited data plan on VZW. Need to mark this thread for all the helpful comments.
The methods of rooting I tried were the One-Click, both the gui and the CLI script with similar results of hanging trying to "see" the device, I tried PurpleDrake, but I think it is for a different LG or android version, and there was one other method that I got from a link either here on XDA or another android forum, but all seemed to have the same problem - once you connect the phone, it initially tries to connect to the device, but never succeeds, just keeps you waiting for the root push to start, but it never does. I was using a Win-7 PC and laptop, switching back and forth to see if I could get one of them to work........ Of course, I have the developer option enabled and turned on the USB debugging. I really like this LG G3 and want to get this thing rooted!!
The other root method I tried was ioroot; I checked my folders. Further reading seems to indicate I may be SOL unless I want to wait for someone to figure it out; oh, yeah, and I tried towelroot as well, but it only tells me my device is not supported........I plan to try one more root method - stumproot, and see if it can bruteforce it. If not, will be a sadder day.......
roirraW "edor" ehT said:
Just to present another option, in the Play Store, search for:
Code:
autorec VS985
It'll install TWRP v2.8.6.x and downgrade your bootloader, which you can then update TWRP to the latest from within the "old" version.
Click to expand...
Click to collapse
I think AutoRec got me the Security Error. I'll try when I get home. Thanks for ur help.
Ok-Full specs on my LG G3 that I want to root....
Running android 5.0.1
Build: LRX21Y
Software Version: VS985 23C
Went back and looked at some of the info and it can be confusing; some root progs need certain version of android running, on a certain set of builds and proper software versions........ enough to make you want to start drinking...... Going to go back one more time and see what I can do to organize all this disparate info and make some more sense out of it. On the plus side, since I have the 32GB version/model, it has 3GB RAM which I confirmed, and even though I have a ton of junky bloat stuff running that I can't currently stop, the phone is running like a champ.
Doesnt work
roirraW "edor" ehT said:
Just to present another option, in the Play Store, search for:
Code:
autorec VS985
It'll install TWRP v2.8.6.x and downgrade your bootloader, which you can then update TWRP to the latest from within the "old" version.
Click to expand...
Click to collapse
I can get into twrp.... just cant boot to system. I'm really dont want to have to KDZ back. Thanks
I used autorec to flash twrp on my 24b LP VZW G3. That was successful. Then booted to recovery...made a backup... then flashed twrp 2870 img, then booted recovery... then booted system and it went to LG bootlogo with Security Error message.
I'd really love to get this straightened out if possible. Would appreciate any advice and help.
sd_N said:
I think AutoRec got me the Security Error. I'll try when I get home. Thanks for ur help.
Click to expand...
Click to collapse
sd_N said:
I can get into twrp.... just cant boot to system. I'm really dont want to have to KDZ back. Thanks
I used autorec to flash twrp on my 24b LP VZW G3. That was successful. Then booted to recovery...made a backup... then flashed twrp 2870 img, then booted recovery... then booted system and it went to LG bootlogo with Security Error message.
I'd really love to get this straightened out if possible. Would appreciate any advice and help.
Click to expand...
Click to collapse
I apologize for the misinformation! I realized earlier after reading what some others had said that in all the testing I had done regarding 24B that I had actually NOT run autorec on 24B, or at least not *just* autorec. To fix your phone, download and flash JasmineROM 8.0. If you felt adventurous, all you really need out of the JasmineROM 8.0 zip is the bootloader (aboot.img) and possibly the kernel (boot.img) too. The changes to the bootloader and possibly the kernel too are what get rid of the security error with TWRP installed.
Hello, my Verizon Lg g3 wont boot at all. The screen wont turn on but the phone vibrates. Thats it. Any suggestions or comments would be greatly appreciated.
Phoner44 said:
Hello, my Verizon Lg g3 wont boot at all. The screen wont turn on but the phone vibrates. Thats it. Any suggestions or comments would be greatly appreciated.
Click to expand...
Click to collapse
Please explain more. Was it rooted? TWRP? What did you do before it couldn't boot?
Sent from my VS985 4G using Tapatalk
NBreunig3 said:
Please explain more. Was it rooted? TWRP? What did you do before it couldn't boot?
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
mine has same problem..was rooted with kingroot and replaced by supersu..on stock Lp 5.1.1...stock recovery..
..was doing anything with phone ..left unplugged last night and battery died and plugged in this morning and all it does is vibrate periodically..cant get to download mode does nothing when i try..can take battery out and plug in and it gives the battery question mark on screen but thats it
i ran lg flashtool 2014 blind (meaning i hooked phone to computer still black screen) changed LGE Androidnet for VZW USB serial port to COM41 and used vs98535b kdz...it loaded firmware and started right up
verizon funny business
I haven't had to reboot my VZW LG G3 in a while, I have stayed back on 23C Lollipop since I was perfectly happy with it and had Hotspot mod working fine with root. Otherwise the phone was just stock 23C. I lost power last night and wanted to charge my phone a little faster so I turned it off to charge for an hour. When I tried to boot now I just get to the red Verizon screen and the phone gets pretty warm and I get a notification beep every 10-15mins, but no boot. I didn't have any update pending (I always remove the update files from cache/fota). So I guess now I need to do a stock recovery if I can get the phone to come up in Download mode. I'm pissed at VZW because I did not OK the installation of any updates, VZW basically disabled my perfectly good 23C phone. Any chance they target phones with 'root' modification flag set now with 'mainenance' updates?
What next?
I still haven't done anything with my G3 that is currently stuck on the 'Red Verizon' screen indefinitely at bootup. This was rooted and running otherwise stock 23c and I simply kept declining updates (have unlimited data so just deleted OTA files when they showed up). I want to make sure I proceed using the best approach to get back to a working state. I did *NOT* accept any updates, so scratching my head why simply rebooting would change anything. I'm ready to take the plunge to xdabbeb's flashable 46a if I can recover from the red vz screen.
Any suggestions on best course of action?
skay said:
I still haven't done anything with my G3 that is currently stuck on the 'Red Verizon' screen indefinitely at bootup. This was rooted and running otherwise stock 23c and I simply kept declining updates (have unlimited data so just deleted OTA files when they showed up). I want to make sure I proceed using the best approach to get back to a working state. I did *NOT* accept any updates, so scratching my head why simply rebooting would change anything. I'm ready to take the plunge to xdabbeb's flashable 46a if I can recover from the red vz screen.
Any suggestions on best course of action?
Click to expand...
Click to collapse
Try removing the Micro SD card. Try Factory Reset if on stock recovery, or wiping Cache and Dalvik if on custom recovery. If the latter doesn't help, try wiping Data. Second to last resort, wipe internal storage.
If all that fails, use LG Flash Tool 2014 on a Windows PC with the 10B KDZ in CSE mode, which will wipe all data including internal storage.
Use the Stump app to root and TWRP Manager to put TWRP on, then flash the ROM of your choice.
roirraW "edor" ehT said:
Try removing the Micro SD card. Try Factory Reset if on stock recovery, or wiping Cache and Dalvik if on custom recovery. If the latter doesn't help, try wiping Data. Second to last resort, wipe internal storage.
If all that fails, use LG Flash Tool 2014 on a Windows PC with the 10B KDZ in CSE mode, which will wipe all data including internal storage.
Use the Stump app to root and TWRP Manager to put TWRP on, then flash the ROM of your choice.
Click to expand...
Click to collapse
You are such a champ reverse "rode" . I was set to try the method you suggested, but figured since you mentioned first removing the micro SD that I might as well just trying rebooting after removing it, and 'voila' as they say, it booted right up!
Ever heard of a rebooting issue with micro SD cards inserted? I've been running for a long time with the same card (64gb Samsung EVO) so it baffles me why *this* reboot caused the boot hang?
So I think now it's time to dive in completely and get setup for TWRP with flashable ROM of 46a (thnx xdabbeb).
I just tried sticking the micro SD card back in after clean shutdown and get the same behavior, hanging at 'Red Verizon' boot screen. Could it be a micro SD formatting issue? Like I said I have been running the phone with the same 64gb card for over 2 months?
skay said:
You are such a champ reverse "rode" . I was set to try the method you suggested, but figured since you mentioned first removing the micro SD that I might as well just trying rebooting after removing it, and 'voila' as they say, it booted right up!
Click to expand...
Click to collapse
Thanks and you're welcome! ?
It's happened occasionally to other G3 users.
Do you have TWRP installed? You can use it or a Windows PC and delete the Android and android-secure folders and it might work after that. Otherwise, I suggest a reformat, preferably from within running Android.
roirraW "edor" ehT said:
Thanks and you're welcome!
It's happened occasionally to other G3 users.
Do you have TWRP installed? You can use it or a Windows PC and delete the Android and android-secure folders and it might work after that. Otherwise, I suggest a reformat, preferably from within running Android.
Click to expand...
Click to collapse
Wow, this appears to be a bona-fide micro SD failure. I have bought cheapo Chinese copies in the past, and learned my lesson that you won't get a decent card (either smaller than advertised, slow, etc.). But this card was purchased at my local Walmart and I ran the Crystaldiskmark suite on it and it was fine. Now ~2 mos later it's not functioning properly, but at least I could 'read' the data off of it. Samsung gave me an RMA to send it in for a replacement.
But now I psyched for MM 46a so I will get TWRP installed and try flashing xdabbeb's ROM. Can I install TWRP straight to my stock 23c rooted phone?
skay said:
Wow, this appears to be a bona-fide micro SD failure. I have bought cheapo Chinese copies in the past, and learned my lesson that you won't get a decent card (either smaller than advertised, slow, etc.). But this card was purchased at my local Walmart and I ran the Crystaldiskmark suite on it and it was fine. Now ~2 mos later it's not functioning properly, but at least I could 'read' the data off of it. Samsung gave me an RMA to send it in for a replacement.
But now I psyched for MM 46a so I will get TWRP installed and try flashing xdabbeb's ROM. Can I install TWRP straight to my stock 23c rooted phone?
Click to expand...
Click to collapse
It happens. Depends on a lot of factors and flash storage can be finicky. The easiest/best way to install TWRP on 23C is @bender_007 's autorec TWRP app. You can find the 23C version in the Play Store. It works ONLY on 23C. Never try to use it on anything else. He makes a 24B version - it's in his thread for autorec TWRP in the non-Verizon G3 General section, I believe, if you ever find yourself on 24B. Again, don't use that one on anything else.
The app takes asks for root permissions. Once you grant it, it appears to be frozen but that's because it's making a backup of your current recovery. Then you can press the button to install TWRP and it'll let you know when it's done.
Once you've got it installed, if it's not at least v2.8.7.0, flash either v2.8.7.0 or v3.0.0 from the version of TWRP the app installs, then choose Reboot Recovery from TWRP.
roirraW "edor" ehT said:
It happens. Depends on a lot of factors and flash storage can be finicky. The easiest/best way to install TWRP on 23C is @bender_007 's autorec TWRP app. You can find the 23C version in the Play Store. It works ONLY on 23C. Never try to use it on anything else. He makes a 24B version - it's in his thread for autorec TWRP in the non-Verizon G3 General section, I believe, if you ever find yourself on 24B. Again, don't use that one on anything else.
The app takes asks for root permissions. Once you grant it, it appears to be frozen but that's because it's making a backup of your current recovery. Then you can press the button to install TWRP and it'll let you know when it's done.
Once you've got it installed, if it's not at least v2.8.7.0, flash either v2.8.7.0 or v3.0.0 from the version of TWRP the app installs, then choose Reboot Recovery from TWRP.
Click to expand...
Click to collapse
I see the (VS985) LG G3 AutoRec-Lollipop from neko_dugacko_ime. It looks like that is the installer you are referring to, correct?
skay said:
I see the (VS985) LG G3 AutoRec-Lollipop from neko_dugacko_ime. It looks like that is the installer you are referring to, correct?
Click to expand...
Click to collapse
Yep, that's what I found. https://play.google.com/store/apps/details?id=b007.autorecvs985&hl=en
Many thanks. Just one more question, I really would like to jump on xdabbeb's flashable 46a ROM. But it looks like he wants the bootstack from 35B, and it looks like TWRP is not compatible with 35B? Not sure which is the best path OR if I should just install TWRP from GPlay and then flash another 46a ROM when/if it becomes available? I figured the xdabbeb 46a would get me to the most recent MM official release but I could keep root if done properly.
skay said:
Many thanks. Just one more question, I really would like to jump on xdabbeb's flashable 46a ROM. But it looks like he wants the bootstack from 35B, and it looks like TWRP is not compatible with 35B? Not sure which is the best path OR if I should just install TWRP from GPlay and then flash another 46a ROM when/if it becomes available? I figured the xdabbeb 46a would get me to the most recent MM official release but I could keep root if done properly.
Click to expand...
Click to collapse
I'm not sure what you mean about TWRP not compatible with 35B.
If you're on any stock ROM other than 10B, you can't install TWRP as simply as going to Google Play. At minimum you have to downgrade your aboot.img (bootloader) and @xdabbeb likes to keep the laf.img (Download mode) matching the aboot, to 12B's aboot and laf.
I usually recommend to people to just downgrade to 10B via TOT or KDZ (TOT is only option if coming from unrooted stock 35B) for the easiest way to root using the Stump app, and to install TWRP via TWRP Manager.
Thanks edor. But a little more confused. I thought the GPlay auto-rec install from https://play.google.com/store/apps/d...recvs985&hl=en made for an easy TWRP install on 23c with root (exactly my configuration). I thought I could install TWRP and download and flash xdabbeb's 46a flashable ROM.
If the best approach for staying on the latest ROM images is going back to 10B or 12B and starting from there with TWRP I'll go that route, but my main goal now was simply to be able to flash the 46a ROM from xdabbeb http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365. Now that my phone is working fine I want to take the time to set it up in the best possible way for installing ROM images going forward since it appears each new release gets more difficult to get root access and I want to keep the hotspot mod going since I have unlimited data. Though I admit I miss having the stock unrooted NFL Mobile working, but I have a while till next season rolls around !
skay said:
Thanks edor. But a little more confused. I thought the GPlay auto-rec install from https://play.google.com/store/apps/d...recvs985&hl=en made for an easy TWRP install on 23c with root (exactly my configuration). I thought I could install TWRP and download and flash xdabbeb's 46a flashable ROM.
If the best approach for staying on the latest ROM images is going back to 10B or 12B and starting from there with TWRP I'll go that route, but my main goal now was simply to be able to flash the 46a ROM from xdabbeb http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365. Now that my phone is working fine I want to take the time to set it up in the best possible way for installing ROM images going forward since it appears each new release gets more difficult to get root access and I want to keep the hotspot mod going since I have unlimited data. Though I admit I miss having the stock unrooted NFL Mobile working, but I have a while till next season rolls around !
Click to expand...
Click to collapse
You confused me when you said you heard TWRP isn't compatible with 35B or 46A, whichever you said. TWRP is compatible. The Autorec app to put TWRP on is only compatible with 23C and 24B - the one in the Play Store for 23C, then there's one in @Bender007 's Autorec thread for 24B.
It's just my opinion but yes, I always recommend going back to 10B for the easiest way to root and put TWRP on.
You may be able to get away with simply flashing the 12B aboot.img (bootloader) and laf.img (Download mode) in a terminal emulator with superuser permissions. The commands are near the bottom of @bweN diorD 's stickied thread in General. I recommend copy and paste because if you get the commands slightly wrong you could at least temporarily brick your device.
Then you should be able to flash TWRP either also in terminal emulator or you might be able to use TWRP Manager then.
Hi,
Just bought a new LG G3. It has Android 4.4.2, Build version KVTL49L.VS98512B, Software version VS98512B.
I'd like to root it, and then install a custom ROM that will maintain root.
There are many root threads on this forum, but most appear not to work on my phone.
1. What is the best way to root 4.4.2? I assume I should not take an OTA upgrade?
2. Once rooted, can I install TWRP, and how?
3. Once those are done, what is the highest Android version custom ROM I can install that will maintain root?
Please don't say read the forum. I have, and it's total confusion.
Thanks in advance.
There are other ways, but in my personal opinion the easiest way to root is to install the Verizon LG drivers, reboot your Windows PC, connect the phone in Download mode using the original USB cable connected to a USB 2.0 port. It can take Windows up to 10 minutes to load the driver, the first time you connect in Download mode to a different USB 2.0 port. You can see the driver's loaded by looking for the phone in the Modem section of Device Manager. Use LG Flash Tool 2014 on Windows to flash the 10B KDZ (might as well get familiar with that process anyway), then use the Stump app available on XDA to root the phone in brute force mode, then use the TWRP Manager from the Play Store to install TWRP. Rooting and installing TWRP get progressively more complicated after 10B.
The stickied return to stock thread in the General section is what you want for more information about flashing a KDZ, and links to the KDZ.
The highest is 46A which is Marshmallow 6.0.
roirraW "edor" ehT said:
There are other ways, but in my personal opinion the easiest way to root is to install the Verizon LG drivers, reboot your Windows PC, connect the phone in Download mode using the original USB cable connected to a USB 2.0 port. It can take Windows up to 10 minutes to load the driver, the first time you connect in Download mode to a different USB 2.0 port. You can see the driver's loaded by looking for the phone in the Modem section of Device Manager. Use LG Flash Tool 2014 on Windows to flash the 10B KDZ (might as well get familiar with that process anyway), then use the Stump app available on XDA to root the phone in brute force mode, then use the TWRP Manager from the Play Store to install TWRP. Rooting and installing TWRP get progressively more complicated after 10B.
The stickied return to stock thread in the General section is what you want for more information about flashing a KDZ, and links to the KDZ.
The highest is 46A which is Marshmallow 6.0.
Click to expand...
Click to collapse
I ended up just using LG One Click Root and not changing anything. Running kitkat 4.4.2 rooted, and checked the root with Root checker.
I'll run the phone as is for a while, just to make sure everything works during the return window, and then maybe install the SkyDragon G3 VS985 Edition Version 6.0.2 if that would work? It looks like I can just flash that directly from my current build. or do I need to downgrade to 10B?
android94301 said:
I ended up just using LG One Click Root and not changing anything. Running kitkat 4.4.2 rooted, and checked the root with Root checker.
I'll run the phone as is for a while, just to make sure everything works during the return window, and then maybe install the SkyDragon G3 VS985 Edition Version 6.0.2 if that would work? It looks like I can just flash that directly from my current build. or do I need to downgrade to 10B?
Click to expand...
Click to collapse
If you have TWRP you can flash whatever you want.
roirraW "edor" ehT said:
There are other ways, but in my personal opinion the easiest way to root is to install the Verizon LG drivers, reboot your Windows PC, connect the phone in Download mode using the original USB cable connected to a USB 2.0 port. It can take Windows up to 10 minutes to load the driver, the first time you connect in Download mode to a different USB 2.0 port. You can see the driver's loaded by looking for the phone in the Modem section of Device Manager. Use LG Flash Tool 2014 on Windows to flash the 10B KDZ (might as well get familiar with that process anyway), then use the Stump app available on XDA to root the phone in brute force mode, then use the TWRP Manager from the Play Store to install TWRP. Rooting and installing TWRP get progressively more complicated after 10B.
The stickied return to stock thread in the General section is what you want for more information about flashing a KDZ, and links to the KDZ.
The highest is 46A which is Marshmallow 6.0.
Click to expand...
Click to collapse
Can I flash the 46A global kdz over stock verizon 35b?? Sorry If this question has been asked before, I just got this phone yesterday ( verizon g3 35b 5.1.1 ) and I have been poring over the xda forums ever since on all the different root methods and software versions, and at this point I am completely overwhelmed by the amount of information thats out there.
My main goal is to be on Marshmallow, rooted and twrpd. If you could point me in the right direction It would be highly appreciated
JayDream said:
Can I flash the 46A global kdz over stock verizon 35b??
Click to expand...
Click to collapse
If you're referring to some 46A KDZ made for some other device than the VS985, then no. I'm not aware of the VS985 46A KDZ being available yet.
Sorry If this question has been asked before, I just got this phone yesterday ( verizon g3 35b 5.1.1 ) and I have been poring over the xda forums ever since on all the different root methods and software versions, and at this point I am completely overwhelmed by the amount of information thats out there.
My main goal is to be on Marshmallow, rooted and twrpd. If you could point me in the right direction It would be highly appreciated
Click to expand...
Click to collapse
If you want to be rooted, then you don't want to bother flashing a KDZ anyway since both 35B and 46A can only flash the 35B KDZ (it won't let you downgrade further without the TOT method I already mentioned). For further information about the TOT method, you'd have to Google for it. Another way to get TWRP on 35B or 46A is in my signature below, titled "[VS985][35B][46A][TWRP]How to install TWRP on 35B or 46A".
roirraW "edor" ehT said:
If you're referring to some 46A KDZ made for some other device than the VS985, then no. I'm not aware of the VS985 46A KDZ being available yet.
If you want to be rooted, then you don't want to bother flashing a KDZ anyway since both 35B and 46A can only flash the 35B KDZ (it won't let you downgrade further without the TOT method I already mentioned). For further information about the TOT method, you'd have to Google for it. Another way to get TWRP on 35B or 46A is in my signature below, titled "[VS985][35B][46A][TWRP]How to install TWRP on 35B or 46A".
Click to expand...
Click to collapse
I was reading this thread http://forum.xda-developers.com/lg-g3/general/lg-g3-android-marshmallow-discussions-t3216143 and I remembered on the G pro I was able to flash other firmwares from other countries, I thought maybe that was the case here too.
I'm trying your alternate method now, after following all the steps I just reboot to recovery, wipe, then flash any rom I want?
update: I followed all the steps then when I went to boot into recovery thru adb, i got the secure boot error, and the phone will no longer boot up
JayDream said:
I was reading this thread and I remembered on the G pro I was able to flash other firmwares from other countries, I thought maybe that was the case here too.
Click to expand...
Click to collapse
I haven't heard of anyone flashing any for other variants on this phone.
I'm trying your alternate method now, after following all the steps I just reboot to recovery, wipe, then flash any rom I want?
Click to expand...
Click to collapse
Yes.
update: I followed all the steps then when I went to boot into recovery thru adb, i got the secure boot error, and the phone will no longer boot up
Click to expand...
Click to collapse
I'll address in the other thread now.
Hey everyone, I have a verizon g3 with firmware version 47a. I'm hell bent on rooting it and it's hell bent on stopping me at any cost XD So the problem is, I'm trying to flash the 10b kdz file, and when I load up the tool and start the flash, it gets the bar to 100% and then gives me an error that says can't connect to server. After that, I just click OK and watch my phone for activity, and there is none. The firmware update bar on my phone remains on 0%. Any solutions would be very much appreciated.
Thanks in advance.
*IF* you're not rooted/haven't flashed one of @xdabbeb 's Bootstacks, then you can't flash anything older than the 35B KDZ from (stock unrooted) 35B or higher. You have to use the 10B TOT along with the .DLL that's extracted from the 35B KDZ. You can find both in my Android File Host section linked to at the bottom of @annoyingduck 's stickied return to stock thread in the General section, also linked to in my signature below.
Regarding no connection to server, read the second or third post of the thread I reference above. But as I said above, if you're coming from 100% stock unrooted 47A, you have to use the TOT method to downgrade to the easily rootable 10B, where you can then use the Stump app on XDA to root it using the brute force option, and then use TWRP Manager from the Play Store to put on TWRP. Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B.
roirraW "edor" ehT said:
*IF* you're not rooted/haven't flashed one of @xdabbeb 's Bootstacks, then you can't flash anything older than the 35B KDZ from (stock unrooted) 35B or higher. You have to use the 10B TOT along with the .DLL that's extracted from the 35B KDZ. You can find both in my Android File Host section linked to at the bottom of @annoyingduck 's stickied return to stock thread in the General section, also linked to in my signature below.
Regarding no connection to server, read the second or third post of the thread I reference above. But as I said above, if you're coming from 100% stock unrooted 47A, you have to use the TOT method to downgrade to the easily rootable 10B, where you can then use the Stump app on XDA to root it using the brute force option, and then use TWRP Manager from the Play Store to put on TWRP. Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B.
Click to expand...
Click to collapse
Hey, thanks so much for the help and reply. So I followed everything you said and everything in the guide, and i still have a small problem. When I start the flash, it's fine. It detects the phone and "analyzes phone setting". Then, it gets to the software extraction part, and **** hits the fanXD. Basically, the connection to server lost window pops up, and the original window states "Upgrade stopped due to an error". And of course, my phone has no activity, the firmware update bar is still on 0%. What gives??
andr0id187 said:
Hey, thanks so much for the help and reply. So I followed everything you said and everything in the guide, and i still have a small problem. When I start the flash, it's fine. It detects the phone and "analyzes phone setting". Then, it gets to the software extraction part, and **** hits the fanXD. Basically, the connection to server lost window pops up, and the original window states "Upgrade stopped due to an error". And of course, my phone has no activity, the firmware update bar is still on 0%. What gives??
Click to expand...
Click to collapse
Are you clicking on analyze phone? You don't need to do that. And I know in the past that has messed me up.
Sent from my One M8 using XDA Labs
andr0id187 said:
Hey, thanks so much for the help and reply. So I followed everything you said and everything in the guide, and i still have a small problem. When I start the flash, it's fine. It detects the phone and "analyzes phone setting". Then, it gets to the software extraction part, and **** hits the fanXD. Basically, the connection to server lost window pops up, and the original window states "Upgrade stopped due to an error". And of course, my phone has no activity, the firmware update bar is still on 0%. What gives??
Click to expand...
Click to collapse
You're welcome!
Did you wait 5-10 minutes since the connection to server dialog is normal? Commonly if you wait 5-10 minutes and not have touched any buttons in any dialogs in the software that pop up, you'll find the phone is flashed.
Can you confirm since you haven't said - are you 100% stock unrooted or rooted and have previously flashed one of @xdabbeb 's Bootstacks? Like I said, if you're 100% stock unrooted, you have to use the TOT method, not KDZs. TOT uses a different tool. Just Google for it. "TOT Method"
If waiting 5-10 minutes doesn't help, try the TOT method. It's better overall anyway, even if it's less user friendly (except that LG Flash Tool 2014 throws up bogus error dialogs).
---------- Post added at 02:59 PM ---------- Previous post was at 02:57 PM ----------
jurington said:
Are you clicking on analyze phone? You don't need to do that. And I know in the past that has messed me up.
Click to expand...
Click to collapse
^^^^^^^^^^ yep, definitely, what @jurington said.
roirraW "edor" ehT said:
You're welcome!
Did you wait 5-10 minutes since the connection to server dialog is normal? Commonly if you wait 5-10 minutes and not have touched any buttons in any dialogs in the software that pop up, you'll find the phone is flashed.
Can you confirm since you haven't said - are you 100% stock unrooted or rooted and have previously flashed one of @xdabbeb 's Bootstacks? Like I said, if you're 100% stock unrooted, you have to use the TOT method, not KDZs. TOT uses a different tool. Just Google for it. "TOT Method"
If waiting 5-10 minutes doesn't help, try the TOT method. It's better overall anyway, even if it's less user friendly (except that LG Flash Tool 2014 throws up bogus error dialogs).
---------- Post added at 02:59 PM ---------- Previous post was at 02:57 PM ----------
^^^^^^^^^^ yep, definitely, what @jurington said.
Click to expand...
Click to collapse
Goddamit you're right, I'm stupid, I didn't read that I AM on stock, unrooted so I'm going to have to use TOT. So will the file remain the same? vs98510b?
andr0id187 said:
Goddamit you're right, I'm stupid, I didn't read that I AM on stock, unrooted so I'm going to have to use TOT. So will the file remain the same? vs98510b?
Click to expand...
Click to collapse
I'm not clear on your question. It's a 10B TOT (and the .DLL I mentioned previously) instead of the 10B KDZ, so it's a different file.
roirraW "edor" ehT said:
I'm not clear on your question. It's a 10B TOT (and the .DLL I mentioned previously) instead of the 10B KDZ, so it's a different file.
Click to expand...
Click to collapse
Ok, so I flashed the 10b tot, rooted it with stump, installed SuperSU and TWRP. Then, according to this article: http://androiding.how/root-verizon-g3-47a-marshmallow-firmware/
I'm supposed to flash the 35b bootstack which I also did successfully. Then, I can flash back to 47a and keep the root. Only problem is, after installing the bootstack, when I try to flash 47a, it's not rooted, and gives me a "con.android.phone has stopped working" error. I think this might have something to do with the fact that in the article, it says NOT to let TWRP install SuperSU when flashing 47a. When i flash it, it gives me no option to accept or deny the installation of Super SU. Is this the problem? Or is it something else entirely? Thanks again.
andr0id187 said:
Ok, so I flashed the 10b tot, rooted it with stump, installed SuperSU and TWRP. Then, according to this article: http://androiding.how/root-verizon-g3-47a-marshmallow-firmware/
I'm supposed to flash the 35b bootstack which I also did successfully. Then, I can flash back to 47a and keep the root. Only problem is, after installing the bootstack, when I try to flash 47a, it's not rooted, and gives me a "con.android.phone has stopped working" error. I think this might have something to do with the fact that in the article, it says NOT to let TWRP install SuperSU when flashing 47a. When i flash it, it gives me no option to accept or deny the installation of Super SU. Is this the problem? Or is it something else entirely? Thanks again.
Click to expand...
Click to collapse
Did you flash xdabbebs 47A rom? Also did you did you do any wipes in twrp before you flashed the rom? And what version of twrp do you have?
Sent from my One M8 using XDA Labs
andr0id187 said:
Ok, so I flashed the 10b tot, rooted it with stump, installed SuperSU and TWRP. Then, according to this article: http://androiding.how/root-verizon-g3-47a-marshmallow-firmware/
I'm supposed to flash the 35b bootstack which I also did successfully. Then, I can flash back to 47a and keep the root. Only problem is, after installing the bootstack, when I try to flash 47a, it's not rooted, and gives me a "con.android.phone has stopped working" error. I think this might have something to do with the fact that in the article, it says NOT to let TWRP install SuperSU when flashing 47a. When i flash it, it gives me no option to accept or deny the installation of Super SU. Is this the problem? Or is it something else entirely? Thanks again.
Click to expand...
Click to collapse
I'd wipe Cache, Dalvik /ART and Data and reflash @xdabbeb 's VS985 stock 47A firmware.
TWRP v3.0.0 is systemless root (or at least Marshmallow) aware so doesn't offer to flash SuperSU.
2.8.7.0 isn't aware and asks since it won't be able to find SuperSU where it looks.
If you do wipes after flashing the ROM, it's common to lose root. Just reflash the ROM.
Also optional debloat zips in post three of his ROM thread.
Ok so first of all, yes I have the xdadev 47a rom, yes I did a wipe in twrp, is that bad? And I have twrp 3.0.0.0(latest?) If you need any more information please ask, I'm really hoping to solve this problem. Thanks
andr0id187 said:
Ok so first of all, yes I have the xdadev 47a rom, yes I did a wipe in twrp, is that bad? And I have twrp 3.0.0.0(latest?) If you need any more information please ask, I'm really hoping to solve this problem. Thanks
Click to expand...
Click to collapse
No, you're supposed to wipe in TWRP, he was just covering all bases. Did you re-flash the ROM?
You can also/instead potentially flash the latest SuperSU.zip from @Chainfire 's website.
roirraW "edor" ehT said:
No, you're supposed to wipe in TWRP, he was just covering all bases. Did you re-flash the ROM?
You can also/instead potentially flash the latest SuperSU.zip from @Chainfire 's website.
Click to expand...
Click to collapse
so whats happening is, every time after i flash the xdadev 47a rom(i dont wipe mind you, i just reboot), it's giving me the com.android.phone has stopped error and no root. I really don't understand why
andr0id187 said:
so whats happening is, every time after i flash the xdadev 47a rom(i dont wipe mind you, i just reboot), it's giving me the com.android.phone has stopped error and no root. I really don't understand why
Click to expand...
Click to collapse
Check the ROM zip MD5 hash? I assume you're meaning you don't wipe after. Did you try wiping again before flashing it?
roirraW "edor" ehT said:
Check the ROM zip MD5 hash? I assume you're meaning you don't wipe after. Did you try wiping again before flashing it?
Click to expand...
Click to collapse
yes i've tried wiping before flashing and it still gives me the error, I'm currently wiping after flash to see what happens, hopefully i dont lose root
andr0id187 said:
yes i've tried wiping before flashing and it still gives me the error, I'm currently wiping after flash to see what happens, hopefully i dont lose root
Click to expand...
Click to collapse
That's not going to make a difference but you will likely not be rooted. You'll still have TWRP though.
roirraW "edor" ehT said:
That's not going to make a difference but you will likely not be rooted. You'll still have TWRP though.
Click to expand...
Click to collapse
so how do i go from 10b to 47a and keep root?
andr0id187 said:
so how do i go from 10b to 47a and keep root?
Click to expand...
Click to collapse
The only way I know is what we've already discussed and what you already did. Did you check the ROM zip MD5 hash? I've flashed my (and my wife's) G3's many times with these files when I was doing tests and haven't had this problem. I'm perplexed as well but if you should check the MD5 hash to eliminate that as a problem. That said, you might need to reflash the 10B TOT. TOTs flash more partitions than KDZs and can fix problems that flashing KDZs and ROMs can't. I once had a weird issue that it didn't matter what KDZ or rooted ROM I flashed, the problem persisted. I don't recall the exact problem but it conceivably could've been the same as similar to yours. Once I flashed the 10B TOT, all was well and when discussing with @xdabbeb, that's when he educated me that TOTs have more partitions than KDZs. I'm a diehard TOT fan ever since (I preferred KDZ when possible previously).
I know you already flashed the TOT but we're running out of ideas. If the MD5 hash of the 47A ROM and 35B Bootstack match what they're supposed to (listed on the Android File Host download page for each file). Make sure and
You should also get in the habit of flashing the appropriate Bootstack every time you flash a ROM, or after every time you restore a TWRP backup. Even if you know you're already on the 35B Bootstack - mind you, I'm not meaning this as "snake oil" or as a solution to the trouble you're having, and flashing it more than once won't change anything, but I just wanted to make sure you know this since some ROM's (JasmineROM and SkyDragon) include a partial Bootstack and can cause a brick (so the Bootstack should be flashed after the ROM in their case), and TWRP Backups/Restores don't backup or restore the entire set of partitions including in the Bootstack, so if you happen to be on a ROM that you were using the 24B Bootstack with, and restore a TWRP Backup of a 35B or higher ROM, you might not have a signal.
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
@andr0id187 I also want to be completely clear since I read back and I don't think you specified. Sorry for the repetetiveness but when you wipe before flashing, you're wiping Cache, Dalvik /ART and Data correct?
roirraW "edor" ehT said:
The only way I know is what we've already discussed and what you already did. Did you check the ROM zip MD5 hash? I've flashed my (and my wife's) G3's many times with these files when I was doing tests and haven't had this problem. I'm perplexed as well but if you should check the MD5 hash to eliminate that as a problem. That said, you might need to reflash the 10B TOT. TOTs flash more partitions than KDZs and can fix problems that flashing KDZs and ROMs can't. I once had a weird issue that it didn't matter what KDZ or rooted ROM I flashed, the problem persisted. I don't recall the exact problem but it conceivably could've been the same as similar to yours. Once I flashed the 10B TOT, all was well and when discussing with @xdabbeb, that's when he educated me that TOTs have more partitions than KDZs. I'm a diehard TOT fan ever since (I preferred KDZ when possible previously).
I know you already flashed the TOT but we're running out of ideas. If the MD5 hash of the 47A ROM and 35B Bootstack match what they're supposed to (listed on the Android File Host download page for each file). Make sure and
You should also get in the habit of flashing the appropriate Bootstack every time you flash a ROM, or after every time you restore a TWRP backup. Even if you know you're already on the 35B Bootstack - mind you, I'm not meaning this as "snake oil" or as a solution to the trouble you're having, and flashing it more than once won't change anything, but I just wanted to make sure you know this since some ROM's (JasmineROM and SkyDragon) include a partial Bootstack and can cause a brick (so the Bootstack should be flashed after the ROM in their case), and TWRP Backups/Restores don't backup or restore the entire set of partitions including in the Bootstack, so if you happen to be on a ROM that you were using the 24B Bootstack with, and restore a TWRP Backup of a 35B or higher ROM, you might not have a signal.
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
@andr0id187 I also want to be completely clear since I read back and I don't think you specified. Sorry for the repetetiveness but when you wipe before flashing, you're wiping Cache, Dalvik /ART and Data correct?
Click to expand...
Click to collapse
Yes, I'm doing the default TWRP wipe which includes all of the above(right?)
andr0id187 said:
Yes, I'm doing the default TWRP wipe which includes all of the above(right?)
Click to expand...
Click to collapse
No idea. As with backups it might default to what was chosen previously. I don't know what it defaults to on flash of TWRP from freshly rooted. I look at the list and make sure those three are checked everytime. Sometimes I wipe other things like internal storage or just Cache and Dalvik /ART so other times I want to make sure I have selected exactly what I want.