LG G3 Boot Problems - Verizon LG G3

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.

Related

[Q] VS98524B Stock rooted Verizon question

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.

Help with stock upgrade from 23c to 46a

Hey XDA,
I had my LG G3 on the liquidsmooth ROM, for quite a long time, and am resetting it to factory and upgrading to 46a Marshmallow.
I have been using LG Flash Tool 2014 and got the 23c Normal Flash completed successfully, but have been unable to get the 24b KDZ to flash (LG Flash Tool 2014 keeps crashing). Tried on multiple Windows 7 computers and one windows 10 computer with compatibility for LG Flash Tool 2014 without any success.
I also tried getting the OTA updates with a verizon SIM installed and no luck there either.
I would love to find a .dlpkgfile of 24b, 35b and 46a to get my phone updated to current software.
If anyone can help, it would be much appreciated. And of course I have searched high and low for answers with no success as well.
You could root and put TWRP on and flash the 46A ROM in the Development section. I've only seen 2-3 people mention actually getting an OTA to 46A so even if you OTA to 35B it's not certain when or if you'll see the OTA to Marshmallow.
FYI it's easiest to root and put TWRP on by flashing the 10B KDZ first. Use the Stump app to root and TWRP Manager to put TWRP on. Rooting and putting TWRP on gets more complicated after 10B.
Sometimes it can take a day or two for an OTA to show up.
Even if you got the .dlpkgfile files you needed, I wasn't able to use the same method that worked to manually apply the OTA from 12B to 23C, to do the same thing to go from 23C to 24B. And since only a few people have reported getting the 46A OTA, and I'm sure they weren't rooted (because otherwise the 46A OTA wouldn't have actually worked), and without root there's no way to capture the OTA file. Once everyone starts getting the OTA, assuming this is the final official Marshmallow, then someone with root and OTA enabled would be able to capture it if they thought about it.
roirraW "edor" ehT said:
You could root and put TWRP on and flash the 46A ROM in the Development section. I've only seen 2-3 people mention actually getting an OTA to 46A so even if you OTA to 35B it's not certain when or if you'll see the OTA to Marshmallow.
FYI it's easiest to root and put TWRP on by flashing the 10B KDZ first. Use the Stump app to root and TWRP Manager to put TWRP on. Rooting and putting TWRP on gets more complicated after 10B.
Sometimes it can take a day or two for an OTA to show up.
Even if you got the .dlpkgfile files you needed, I wasn't able to use the same method that worked to manually apply the OTA from 12B to 23C, to do the same thing to go from 23C to 24B. And since only a few people have reported getting the 46A OTA, and I'm sure they weren't rooted (because otherwise the 46A OTA wouldn't have actually worked), and without root there's no way to capture the OTA file. Once everyone starts getting the OTA, assuming this is the final official Marshmallow, then someone with root and OTA enabled would be able to capture it if they thought about it.
Click to expand...
Click to collapse
I have the intention of selling the phone and having on OFFICIAL status.
j1999t said:
I have the intention of selling the phone and having on OFFICIAL status.
Click to expand...
Click to collapse
Ah. Afraid flashing the 35B KDZ and letting it OTA on its own whenever/if the OTA actually spreads to everyone would be your best bet. Assuming they'll put a Verizon SIM in it, that is. 35B works really great anyway.
roirraW "edor" ehT said:
Ah. Afraid flashing the 35B KDZ and letting it OTA on its own whenever/if the OTA actually spreads to everyone would be your best bet. Assuming they'll put a Verizon SIM in it, that is. 35B works really great anyway.
Click to expand...
Click to collapse
I tried that, the LG Flash Tool 2014 continuously crashes when getting phone information, so I am essentially stuck at the moment
j1999t said:
I tried that, the LG Flash Tool 2014 continuously crashes when getting phone information, so I am essentially stuck at the moment
Click to expand...
Click to collapse
Are you manually selecting the "Read Phone Information" button? You don't have to do that if you are, and has often crashed for me too. Just click "Start".
Otherwise, you could:
1. Root.
2. Put TWRP on.
3. Get the completely stock 35B aboot (bootloader), laf (Download mode), boot (kernel), system and recovery partition images from @bweN diorD 's stickied thread in the General section.
4. Take @xdabbeb 's 35B bootstack zip, replace the aboot and laf in there, which are 12B's, with the ones from 35B.
5. Modify the updater-script in the bootstack zip to also flash the boot, system, and recovery partitions.
6. Flash the zip in TWRP.
You should be 100% completely stock 35B with no root or custom recovery at this point.
I am not responsible if you mess up the commands in the updater-script, or any other issue and you end up bricking your phone, however.
Just sayin', you could.
FYI - I took the route of flashing the 46A rom in the developer section. I'm rooted, running xposed and my status shows "official"
If you're wanting to sell it, why not just slap 35B on there and call it a day? 46A is not current software for the masses

Help with rooted 11C to 46A prior to switching to TMO

I'm going to be switching to a TMO unlimited plan and would like to move over my rooted G3, which is currently on 11C with the tethering hack, and would like to move with a more recent version. What's going to be the most straightforward way to get there? I'd like to have root on 46A for TB but that's about the only reason.
If I could simply unroot and take the OTA's that would be fine but my vague recollection is that it's not as simple as that. While the OTA method would be nice so I don't need to reload everything, going from scratch would be OK.
If you have TWRP installed, follow a ROM's directions to flash a 46A ROM. Update TWRP to the latest (either 2.8.7.0 or 3.0.0) first. Always make a backup first and store it somewhere that won't be affected by a factory reset or stock flash of TOT or KDZ (in other words, on your MicroSD card).
Just in case you're not aware, the built-in LG Backup (Settings / Backup) works really fast and I've been using it instead of TB for restoring user apps and data.
I was thinking of using the stock ROM listed here but it talks about installing a 35B bootstack first as does the Azadi ROM.
I've already upgraded to TWRP 2.8.7.0 so that's done as is the LG Backup. So do I then need to flash the 35B bootstack and then the 46A ROM or is there a "complete" 46A that can be installed from scratch? I've poked around and everything basically says I'll need to be on the 35B bootstack before going to 46A.
tgmorris said:
So do I then need to flash the 35B bootstack and then the 46A ROM
Click to expand...
Click to collapse
Yes.
Success - sort of.
I did 35B & 46A from TWRP and rebooted but ran into com.android.phone has stopped errors. Seemed like the simplest solution was a factory reset, which did cure it. However now I've lost root so I need to investigate how to get that back on 46A
Thanks for the help as at least I'm now current.
tgmorris said:
Success - sort of.
I did 35B & 46A from TWRP and rebooted but ran into com.android.phone has stopped errors. Seemed like the simplest solution was a factory reset, which did cure it. However now I've lost root so I need to investigate how to get that back on 46A
Thanks for the help as at least I'm now current.
Click to expand...
Click to collapse
You're welcome, glad you've had some success. You could try flashing the latest beta (made for Marshmallow) SuperSU.zip (v2.67?), or dirty flashing the ROM.
roirraW "edor" ehT said:
You're welcome, glad you've had some success. You could try flashing the latest beta (made for Marshmallow) SuperSU.zip (v2.67?), or dirty flashing the ROM.
Click to expand...
Click to collapse
That worked after manually booting into recovery and hoping to get to TWRP.
Once there I flashed v2.6.7 and seem like I'm good to go. Now just need to set things upo the way I was.
Really appreciate all the fast help.
tgmorris said:
That worked after manually booting into recovery and hoping to get to TWRP.
Once there I flashed v2.6.7 and seem like I'm good to go. Now just need to set things upo the way I was.
Really appreciate all the fast help.
Click to expand...
Click to collapse
You're welcome!

No Marshmallow update?

I just found out Verizon released Marshmallow for the G3 not too long ago so I thought I might switch back over to my old G3. Before doing so, I wanted to update the phone first and see how I like it. OTA update(on wifi) didn't find any new updates so I used the software upgrade assistant. The upgrade assistant found new updates and updated my phone to what I thought would be Marshmallow. To my surprise, it updated to Lollipop 5.1.1. I figured it must have to upgrade to Lollipop first, so I went back into the upgrade assistant and it says my phones up-to-date. Same goes for the OTA update.
It's been a couple hours now and my phones still not seeing any Marshmallow update. Does my phone have to have a sim card and be active in order to update to Marshmallow? What would cause me not to be able to update to Marshmallow?
Do you have an activated Verizon SIM in? Sometimes it can take days for the OTA to show up after restoring to stock.
roirraW "edor" ehT said:
Do you have an activated Verizon SIM in? Sometimes it can take days for the OTA to show up after restoring to stock.
Click to expand...
Click to collapse
No, I do not have a sim in. My current Verizon phone uses a nano sim so unfortunately, I can't just swap them out. I wanted to see how I liked Marshmallow before getting a new sim. However, I was able to upgrade to lollipop without a sim.
Designer17 said:
No, I do not have a sim in. My current Verizon phone uses a nano sim so unfortunately, I can't just swap them out. I wanted to see how I liked Marshmallow before getting a new sim. However, I was able to upgrade to lollipop without a sim.
Click to expand...
Click to collapse
The computer software doesn't require a SIM, but as you discovered, they haven't released the 46A Marshmallow KDZ yet, which is why it only took you to 35B 5.1.1 since all the software does is download the latest released KDZ and flash it.
For OTAs on the phone itself, it does require an activated Verizon SIM for it to even recognize that there's an OTA available. I know there are adapters to change SIM sizes, but I've never had to use one.
If you root and put TWRP on (second link in my signature below), you can flash @xdabbeb 's completely stock 46A ROM in the Development section.
roirraW "edor" ehT said:
The computer software doesn't require a SIM, but as you discovered, they haven't released the 46A Marshmallow KDZ yet, which is why it only took you to 35B 5.1.1 since all the software does is download the latest released KDZ and flash it.
For OTAs on the phone itself, it does require an activated Verizon SIM for it to even recognize that there's an OTA available. I know there are adapters to change SIM sizes, but I've never had to use one.
If you root and put TWRP on (second link in my signature below), you can flash @xdabbeb 's completely stock 46A ROM in the Development section.
Click to expand...
Click to collapse
Thanks for clearing that up. Maybe I will flash adabbeb's rom instead of waiting for Verizon to release the KDZ.
Designer17 said:
Thanks for clearing that up. Maybe I will flash adabbeb's rom instead of waiting for Verizon to release the KDZ.
Click to expand...
Click to collapse
You're welcome! Yeah, Verizon/LG are taking an extraordinarily long time to release this one. Complicating matters is that they changed things so that an old pattern of URL we were able to use in the past to check for the KDZ no longer works.
I was restoring my phone to a JasmineROM 9.1 TWRP backup to check a few times every day with the official computer software to see when it would start downloading the 46A KDZ but I've given up checking - it was a lot of backing up and restoring - someone else probably would find the news sooner anyway.
roirraW "edor" ehT said:
You're welcome! Yeah, Verizon/LG are taking an extraordinarily long time to release this one. Complicating matters is that they changed things so that an old pattern of URL we were able to use in the past to check for the KDZ no longer works.
I was restoring my phone to a JasmineROM 9.1 TWRP backup to check a few times every day with the official computer software to see when it would start downloading the 46A KDZ but I've given up checking - it was a lot of backing up and restoring - someone else probably would find the news sooner anyway.
Click to expand...
Click to collapse
I know all about Verizon taking forever to release updates. My current phone, Sony Xperia Z3v, just got Lollipop a couple weeks ago. It's been nearly 2yrs since Verizon promised it would get Lollipop. I was quite shocked when I found out Marshmallow was already available for the G3.
Designer17 said:
I know all about Verizon taking forever to release updates. My current phone, Sony Xperia Z3v, just got Lollipop a couple weeks ago. It's been nearly 2yrs since Verizon promised it would get Lollipop. I was quite shocked when I found out Marshmallow was already available for the G3.
Click to expand...
Click to collapse
Wow, that is a LONG time!
We were all quite surprised when 46A released so quickly. Even before it was official, there were a few helpful people who got the OTA I think it was a couple of weeks or maybe even a month before anyone else, and with our help, they imaged the 46A partitions for us. Since we haven't had the KDZ available to extract, that's what the 46A-based ROMs are using. @xdabbeb and I compared all the files/partitions from the "leak" and the official OTA and they're identical, however, so no danger the ROMs are any different than the official besides that the rooted ROMs *have* to use the 35B modem because the 46A modem requires the 46A sbl1 partition, and the 46A sbl1 in combination with the 12B aboot (bootloader) which we require to be able to get into TWRP put the phone into QHSUSB_BULK mode. @xdabbeb tried modifying files to get the 46A modem and sbl1 to work with the 12B aboot, but no luck.
I remember when at least one user (I don't remember who) on here was insistent that we wouldn't get 5.1.1 and when the earliest reports of the OTA occurred, they thought it was fake. I was cautiously optimistic. Very grateful that we got 35B. If we never get another OTA to hopefully fix just the few quirks with 46A, I'd probably restore back to @xdabbeb 's VS985 v2.0 based on 35B as it's overall the cat's meow in my opinion. It gives me that warm, fuzzy feeling of knowing just how professional a job he did with it. I do admittedly find it hard to move "backwards" though, knowing there's a more recent stock ROM.
roirraW "edor" ehT said:
The computer software doesn't require a SIM, but as you discovered, they haven't released the 46A Marshmallow KDZ yet, which is why it only took you to 35B 5.1.1 since all the software does is download the latest released KDZ and flash it.
For OTAs on the phone itself, it does require an activated Verizon SIM for it to even recognize that there's an OTA available. I know there are adapters to change SIM sizes, but I've never had to use one.
If you root and put TWRP on (second link in my signature below), you can flash @xdabbeb 's completely stock 46A ROM in the Development section.
Click to expand...
Click to collapse
Were is this completely stock Marshmallow Rom located.All the ones I've found have been modified in someway.
AtrixHDMan said:
Were is this completely stock Marshmallow Rom located.All the ones I've found have been modified in someway.
Click to expand...
Click to collapse
In the Development section, the one that says 46A firmware, thread by @xdabbeb. That's as close to 100% stock rooted you can be while still being able to get into TWRP.
There's only one other stock 46A-based ROM in the Development section.
roirraW "edor" ehT said:
In the Development section, the one that says 46A firmware, thread by @xdabbeb. That's as close to 100% stock rooted you can be while still being able to get into TWRP.
There's only one other stock 46A-based ROM in the Development section.
Click to expand...
Click to collapse
Oh ok. I saw that.I'm guessing since I'm on 12B rooted I can just install TWRP and that 46A Rom and keep root and TWRP installed.Is that correct.If so I'm going to proceed but not if exposed can't be installed or since I already have exposed install will it still be after update to Marshmallow?
AtrixHDMan said:
Oh ok. I saw that.I'm guessing since I'm on 12B rooted I can just install TWRP and that 46A Rom and keep root and TWRP installed.Is that correct.
Click to expand...
Click to collapse
As @xdabbeb says and links to in the first post of that thread, you have to be on the 35B bootstack, so flash the 35B bootstack before flashing that ROM.
Before you flash any ROM, in TWRP you select to wipe Cache, Dalvik/ART and Data. I wipe System as well.
Otherwise yes. You can, if you wish, use the built in LG Backup to backup your user apps and user data, and limited system data.
If so I'm going to proceed but not if exposed can't be installed or since I already have exposed install will it still be after update to Marshmallow?
Click to expand...
Click to collapse
When you flash a ROM, it overwrites your old one, which includes overwriting Xposed or any other system modifications because when you flash Xposed or other system mods, it installs to the same place the ROM is. Xposed for Marshmallow works fine for me.
roirraW "edor" ehT said:
As @xdabbeb says and links to in the first post of that thread, you have to be on the 35B bootstack, so flash the 35B bootstack before flashing that ROM.
Before you flash any ROM, in TWRP you select to wipe Cache, Dalvik/ART and Data. I wipe System as well.
Otherwise yes. You can, if you wish, use the built in LG Backup to backup your user apps and user data, and limited system data.
When you flash a ROM, it overwrites your old one, which includes overwriting Xposed or any other system modifications because when you flash Xposed or other system mods, it installs to the same place the ROM is. Xposed for Marshmallow works fine for me.
Click to expand...
Click to collapse
I'm still a little confused about how to install this.I'm on 12B and it sounds like I need to be on 35B before I can flash this 46A Rom.So do I need to install TWRP and 35B Rom first or can I go from 12B Rom to 46A Rom but I will need to flash 35B bootstack to go from 12B to 46A.
AtrixHDMan said:
I'm still a little confused about how to install this.I'm on 12B and it sounds like I need to be on 35B before I can flash this 46A Rom.So do I need to install TWRP and 35B Rom first
Click to expand...
Click to collapse
No.
or can I go from 12B Rom to 46A Rom but I will need to flash 35B bootstack to go from 12B to 46A.
Click to expand...
Click to collapse
Yes.
Install TWRP using TWRP Manager. Like I said in the other thread, don't "kill" me if I'm wrong but I believe that 12B was the last version that you could simply use TWRP Manager to install TWRP - after 12B it's not that simple. So what I'm saying is, be prepared, have everything backed up if you care about it, moved to your external storage in case you need to flash a KDZ to restore to stock, etc.
Follow the link in @xdabbeb 's 46A thread and download the 35B bootstack and the 46A ROM. If you wish you can download debloat zips that I provided in the third post of that thread.
Use an app like Quick Boot in the Play Store to reboot to TWRP Recovery, or with the phone off, press and hold the Down Volume button and while keeping it pressed, also press and hold the Power button. When you see it load a stock-looking recovery with white background, let go of both buttons right away. If you hold the power button for too long, it'll turn off or reboot. Then select Wipe Cache from the stock-looking recovery to manually go into TWRP. You can also press Factory Reset to get to TWRP but since I'm not positive if using TWRP Manager on 12B is fine, just use the Wipe Cache option. I know for a fact TWRP Manager is just fine on 10B because 10B is what I always root and install TWRP on.
From TWRP, wipe Cache and Dalvik/ART, and Data.
Again from TWRP, flash the 35B bootstack you downloaded.
Once more from TWRP, flash the 46A ROM you downloaded.
If you so wish you can flash any debloat zips.
Reboot.
roirraW "edor" ehT said:
No.
Yes.
Install TWRP using TWRP Manager. Like I said in the other thread, don't "kill" me if I'm wrong but I believe that 12B was the last version that you could simply use TWRP Manager to install TWRP - after 12B it's not that simple. So what I'm saying is, be prepared, have everything backed up if you care about it, moved to your external storage in case you need to flash a KDZ to restore to stock, etc.
Follow the link in @xdabbeb 's 46A thread and download the 35B bootstack and the 46A ROM. If you wish you can download debloat zips that I provided in the third post of that thread.
Use an app like Quick Boot in the Play Store to reboot to TWRP Recovery, or with the phone off, press and hold the Down Volume button and while keeping it pressed, also press and hold the Power button. When you see it load a stock-looking recovery with white background, let go of both buttons right away. If you hold the power button for too long, it'll turn off or reboot. Then select Wipe Cache from the stock-looking recovery to manually go into TWRP. You can also press Factory Reset to get to TWRP but since I'm not positive if using TWRP Manager on 12B is fine, just use the Wipe Cache option. I know for a fact TWRP Manager is just fine on 10B because 10B is what I always root and install TWRP on.
From TWRP, wipe Cache and Dalvik/ART, and Data.
Again from TWRP, flash the 35B bootstack you downloaded.
Once more from TWRP, flash the 46A ROM you downloaded.
If you so wish you can flash any debloat zips.
Reboot.
Click to expand...
Click to collapse
Just making sure root will hold and get TWRP from Play Store?
AtrixHDMan said:
Just making sure root will hold
Click to expand...
Click to collapse
Answered in the first post of @xdabbeb 's thread for his 46A ROM.
and get TWRP from Play Store?
Click to expand...
Click to collapse
I answered that in the other thread.
roirraW "edor" ehT said:
Answered in the first post of @xdabbeb 's thread for his 46A ROM.
I answered that in the other thread.
Click to expand...
Click to collapse
I`ve updated and my phone is not rooted.Tried a few apps that require root and it is not rooted.How to fix?
AtrixHDMan said:
I`ve updated and my phone is not rooted.Tried a few apps that require root and it is not rooted.How to fix?
Click to expand...
Click to collapse
Try dirty flashing the ROM? @xdabbeb 's 46A ROM is pre-rooted. Had you wiped anything AFTER flashing the ROM?
You could download the SuperSU.zip off of @Chainfire 's website and flash it in TWRP. It would have to be the same version @xdabbeb used on his ROM, though - I think 2.67.
I haven't had this problem when flashing his ROM so I don't know what else to suggest.
roirraW "edor" ehT said:
Try dirty flashing the ROM? @xdabbeb 's 46A ROM is pre-rooted. Had you wiped anything AFTER flashing the ROM?
You could download the SuperSU.zip off of @Chainfire 's website and flash it in TWRP. It would have to be the same version @xdabbeb used on his ROM, though - I think 2.67.
I haven't had this problem when flashing his ROM so I don't know what else to suggest.
Click to expand...
Click to collapse
I got it to work,but I`m having several problems with this rom.Like very slow charging.weather not working,brightness not working,and if you shut phone off and try to boot back up it buzzes but no boot up.Have to pull battery out in order to boot up.
AtrixHDMan said:
I got it to work,but I`m having several problems with this rom.Like very slow charging.weather not working,brightness not working,and if you shut phone off and try to boot back up it buzzes but no boot up.Have to pull battery out in order to boot up.
Click to expand...
Click to collapse
I don't have those problems. Maybe you should post in the ROM thread to see if anyone else who's running that ROM has those problems or suggestions.
Had you wiped Cache, Dalvik/ART and Data before flashing the ROM?

How to get to 47A from new phone?

My LG G3 seems to have died tonight.
See here: http://forum.xda-developers.com/verizon-lg-g3/help/phone-dying-t3347199
I really do like this phone so I ordered a cheap refurb replacement off ebay.
What's the process to go to from whatever it shipped with to xdabbeb's 47A version found here w/TWRP?
http://forum.xda-developers.com/showthread.php?t=3304365
Bump. Can't imagine it's that hard to get from new phone to 47A rooted with TWRP, but want to do it right the first time.
Does anyone have the steps I should follow?
Various ways are out there. A quick look through the forums will find you a solution to what you're looking for.
Here's a flashable stock firmware image that can be used:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
iBolski said:
Various ways are out there. A quick look through the forums will find you a solution to what you're looking for.
Here's a flashable stock firmware image that can be used:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
Click to expand...
Click to collapse
Yes, i see that thread, but i may have to go backwards, root and twrp before that, right?
Those are the steps I'm looking for.
lexluthor said:
Yes, i see that thread, but i may have to go backwards, root and twrp before that, right?
Those are the steps I'm looking for.
Click to expand...
Click to collapse
Again, there is a topic exactly for what you need in this specific forum:
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-manually-downgrade-partitions-t3326775
Hope that helps! I myself haven't done this as I'm fully satisfied being on stock 47A unrooted at this point. Once I can verify that the latest CM is pretty stable (which it appears to be but there are still a few nagging issues), I'll probably eventually go to that, but I want to wait and see if LG and VZW are done with updating this phone.
lexluthor said:
Yes, i see that thread, but i may have to go backwards, root and twrp before that, right?
Those are the steps I'm looking for.
Click to expand...
Click to collapse
Note that unless you truly can't, I always recommend the 10B TOT method with the .DLL from the 35B KDZ over the instructions in the thread that was linked. It works for me fine both times I've tested it but several people ended up having to TOT their phone after those instructions anyway.
Once you're on 10B, root with the Stump app then use TWRP Manager in the Play Store to flash TWRP.
roirraW "edor" ehT said:
Note that unless you truly can't, I always recommend the 10B TOT method with the .DLL from the 35B KDZ over the instructions in the thread that was linked. It works for me fine both times I've tested it but several people ended up having to TOT their phone after those instructions anyway.
Once you're on 10B, root with the Stump app then use TWRP Manager in the Play Store to flash TWRP.
Click to expand...
Click to collapse
The .tot does seem easier than the instructions in the other thread. At least, that's if no complications with getting Windows set up to do the .tot right.
So if the phone comes and it's 35B or higher, TOT to 10B w/35B DLL (where's the correct .35B DLL, I wasn't sure exactly which file to use?), stump root, install TWRP Manager from play store and flash TWRP, reboot to TWRP, flash 35B bootstack, flash xdabbeb's 47A. Done? I'll then still have TWRP, be rooted and be on 47A, right?
If the phone comes lower than 35B, can I just .kdz to 10B and then do the same?
lexluthor said:
The .tot does seem easier than the instructions in the other thread. At least, that's if no complications with getting Windows set up to do the .tot right.
So if the phone comes and it's 35B or higher, TOT to 10B w/35B DLL (where's the correct .35B DLL, I wasn't sure exactly which file to use?),
Click to expand...
Click to collapse
My Android File host link at the bottom of the first post of the other thread by @annoyingduck has both the 10B_3 TOT (don't accidentally get the 10B_01 KDZ) and the 35B .DLL you need.
stump root, install TWRP Manager from play store and flash TWRP, reboot to TWRP, flash 35B bootstack, flash xdabbeb's 47A. Done? I'll then still have TWRP, be rooted and be on 47A, right?
Click to expand...
Click to collapse
Correct.
If the phone comes lower than 35B, can I just .kdz to 10B and then do the same?
Click to expand...
Click to collapse
Yes.
47a kdz just came out as another easy option if you want stock
Sent from my VS985 4G using Tapatalk
gspinelli said:
47a kdz just came out as another easy option if you want stock
Click to expand...
Click to collapse
Can that be rooted though? Do I still go back to 10b, stump root, installed TWRP and then kdz to 47a?
If I'm going to do that, I'm probably just better off using xdabbeb's 47a. I've been happy with his 46a.
Or can I just go from whatever version my phone comes with, kdz to 47a and then root there using ?? (kingroot)? Then I'll be on 47a stock/rooted, but no TWRP? That may suffice for my needs. I like that xdabbeb's 46a had systemless root and I was able to get android pay working.
lexluthor said:
Can that be rooted though? Do I still go back to 10b, stump root, installed TWRP and then kdz to 47a?
If I'm going to do that, I'm probably just better off using xdabbeb's 47a. I've been happy with his 46a.
Or can I just go from whatever version my phone comes with, kdz to 47a and then root there using ?? (kingroot)? Then I'll be on 47a stock/rooted, but no TWRP? That may suffice for my needs. I like that xdabbeb's 46a had systemless root and I was able to get android pay working.
Click to expand...
Click to collapse
When you flash a KDZ, even with LG Flash Tool 2014's "Normal" option versus "CSE", it overwrites everything currently installed: System (your ROM), Modem, Bootloader, Kernel, Recovery and other partitions. "Normal" mode enables keeping user apps and user and system data, although doing that works best when only "upgrading" from perhaps the previous official release.
In other words, if you're going to root and install TWRP, flashing a KDZ would just undo all that so yes, absolutely, it would be easier/better to just flash @xdabbeb 's stock 47A ROM.
You can temporarily root 47A with Kingroot. You have to re-root whenever you reboot, and Kingroot is very invasive. You don't want to use Kingroot. The only times I recommend it is as a temporary solution, as for my alternate way of installing TWRP which you're already aware of.
Flashing newer KDZs is more for those people who want to stay 100% stock unrooted, especially for those who don't actually use Verizon so they don't receive OTAs.
roirraW "edor" ehT said:
When you flash a KDZ, even with LG Flash Tool 2014's "Normal" option versus "CSE", it overwrites everything currently installed: System (your ROM), Modem, Bootloader, Kernel, Recovery and other partitions. "Normal" mode enables keeping user apps and user and system data, although doing that works best when only "upgrading" from perhaps the previous official release.
In other words, if you're going to root and install TWRP, flashing a KDZ would just undo all that so yes, absolutely, it would be easier/better to just flash @xdabbeb 's stock 47A ROM.
Click to expand...
Click to collapse
Yes xdabbab's 47A is the way to go for me.
Just got the new phone and its on 35B. I'm trying to TOT to 10B with the 35B DLL. I did the COM41 in device manager. I've got the phone in download mode. I'm running the LG Flash tool as admin in Windows 10. I load the 2 files and click the start arrow. It goes through some things where it says BIN CRC check or something like than and then it just sits and says READY!! in yellow, but nothing ever happens.
Am I doing something wrong?
EDIT: Unlplugged USB and plugged it back in and it's going now. Stand by, could maybe use some more help getting through this
Optimizing apps on 47A (hopefully). I'm sure finding my Titanium folder on the external drive will be a pain as always, but hopefully smooth sailing from there.
The process worked great. East to TOT, install stump root, then TWRP and then flashed 35b bootstack and 47a xdabbeb with some wiping data/caches in between.
Titanium took a good few hours to restore my 300+ apps. I don't know why that took so long. There's probably a better way, but even though Titanium always takes long, it's easy to automatic backups during the week and it usually gets my apps back to a nice spot.
Back up and running on my replacement phone today. The ebay listing said it was B+ condition. Screen is in great shape, some scraping on the sides, but I don't care about that. I used my back cover that I had put an NFC sticker on when I got the original phone. All working great so far.
Thanks for the help here.
Thanks!
David
lexluthor said:
Titanium took a good few hours to restore my 300+ apps. I don't know why that took so long. There's probably a better way, but even though Titanium always takes long, it's easy to automatic backups during the week and it usually gets my apps back to a nice spot.
Thanks for the help here.
Thanks!
David
Click to expand...
Click to collapse
Were you charging at the same time as restoring backups? Maybe it was throttling down due to heat.
Yeah, for me since Lollipop, even with Mount Space Separation disabled (and then phone rebooted), besides TB taking a long time it also would get hung up on restoring an app occasionally. I'd have to reboot and then resume restoring, and any that it would get hung up on I'd skip until after. Then I was able to restore those one by one and then TB handled them fine.
I've been using the built in LG Backup since 12B and it's fast. It has a couple quirks such as I find it resets my keyboard to stock when backing up, may have killed other things that I normally had running in the background, but I don't recall for sure.
When restoring I have a pet peeve that it forces the screen to stay on during the process, even once it finishes and is waiting for you to select the button to reboot.
Taking OTAs manages to let you know it's successful after it automatically reboots, why can't they have LG Backup do the same?
Still, overall, I prefer it for speed and reliability/stability, but TB is still a must have tool.
You're welcome!
roirraW "edor" ehT said:
Were you charging at the same time as restoring backups? Maybe it was throttling down due to heat.
Yeah, for me since Lollipop, even with Mount Space Separation disabled (and then phone rebooted), besides TB taking a long time it also would get hung up on restoring an app occasionally. I'd have to reboot and then resume restoring, and any that it would get hung up on I'd skip until after. Then I was able to restore those one by one and then TB handled them fine.
I've been using the built in LG Backup since 12B and it's fast. It has a couple quirks such as I find it resets my keyboard to stock when backing up, may have killed other things that I normally had running in the background, but I don't recall for sure.
When restoring I have a pet peeve that it forces the screen to stay on during the process, even once it finishes and is waiting for you to select the button to reboot.
Taking OTAs manages to let you know it's successful after it automatically reboots, why can't they have LG Backup do the same?
Still, overall, I prefer it for speed and reliability/stability, but TB is still a must have tool.
You're welcome!
Click to expand...
Click to collapse
I've never gotten LG Backup to work right for me. Never seems to restore nearly everything or get errors when backing up. Not worth looking into it more as I don't start fresh much.
I was using the phone much of the time TiBU was working, so that didn't help, but still slow going even if I plugged it in and let it sit. It missed about 30 apps the first time around that I did in a 2nd pass. Didn't get hung too much in the main batch, at least. And if It does hang, no need to reboot. Just FC TiBU and then start it back up and leave the hung app off to do as a one by at the end.
I did just discover a strange problem with the new phone. I can't restart it. If I try to restart it goes blank after a bit and a battery pull is needed to get it back on. I can power off, let it go off and power on, that works fine. Only fails when I do it as a restart.
Any ideas?
lexluthor said:
I did just discover a strange problem with the new phone. I can't restart it. If I try to restart it goes blank after a bit and a battery pull is needed to get it back on. I can power off, let it go off and power on, that works fine. Only fails when I do it as a restart.
Any ideas?
Click to expand...
Click to collapse
It's a common problem on this phone. There's no particular known reason why it happens, nor any solution - there's only been a ton of speculation without any strong evidence other than a thread I had made about this subject, during which I made a detailed test of rebooting the phone about 140 times under different circumstances (10 times in a row in each specific circumstance). I'm fairly certain I would have to at minimum do about 1500 more reboots in various circumstances to only possibly get closer to narrowing down the problem.
Some people will tell you they think it's caused by a particular (35B) bootstack. I don't believe it because I had 70 reboots in a row while on the 35B bootstack without having the problem during part of my testing.
I also have had the problem before 35B even came out. I haven't had the problem happen at all in the past couple of months - since the last time I had TOT'd back to 10B (and I've done various KDZ flashes since then when testing things for myself and for others).
Rebooting
I noticed the reboot problem started after I installed a 64GB memory card. Without the additional memory card...rebooting works normally. With it inserted, a battery pull is needed 2x out of 5 to bring the phone back from limbo. I'm on Jasmine 9.1
Circlesqr said:
I noticed the reboot problem started after I installed a 64GB memory card. Without the additional memory card...rebooting works normally. With it inserted, a battery pull is needed 2x out of 5 to bring the phone back from limbo.
Click to expand...
Click to collapse
Definitely not my issue. My phone was rebooting in download mode without even a SIM or memory card installed.

Categories

Resources