I am fairly competent with installing and wiping and what be, I was comfortable with 10b on my G3 and stuck with it till now. I am ready for LP. I just don't know where to go.
I want to run stock but I also want to tinker with CM again.
What would be the best way to update to a fully working ROM or heck even to 24b?
I can't update on my phone for some reason it just boots to TWRP and I have to flash a fix.
Thanks
illyfilly said:
I am fairly competent with installing and wiping and what be, I was comfortable with 10b on my G3 and stuck with it till now. I am ready for LP. I just don't know where to go.
I want to run stock but I also want to tinker with CM again.
What would be the best way to update to a fully working ROM or heck even to 24b?
I can't update on my phone for some reason it just boots to TWRP and I have to flash a fix.
Thanks
Click to expand...
Click to collapse
Use this thread http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140 to update to 23C from here: http://forum.xda-developers.com/verizon-lg-g3/general/vzw-vs985c01-kdz-t3077799
I HIGHLY recomend booting to stock LG recovery and doing a factory wipe after flashing the KDZ
Then root using this method: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
install twrp recovery by using the autorec vs985 app from the play store.
Edit: the OTA failed because you had TWRP installed. You could also use the 12B KDZ and then take whatever OTAs are available, that might get you to 24B
You can also just use LG Flash Tool 2014 to flash the 23C KDZ instead of 12B and root using the one click root script, then for TWRP, search in the Play Store for autorec VS985.
There's no root for 24B yet and you can't be rooted before you take the 24B OTA so if you want 24B and don't want to wait then don't root and don't install a custom recovery, just take the OTA once you're in 23C.
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 35A_08 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 35A_08 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
You could also just wipe and Flash Jasmine ROM or SkyDragon ROM for your stock-based ROM--all the features, debloated, no KDZ mess required.
Once you have that in place and have made a backup via TWRP, you can play with whatever AOSP ROM(s) you like.
BladeRunner said:
Use this thread http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140 to update to 23C from here: http://forum.xda-developers.com/verizon-lg-g3/general/vzw-vs985c01-kdz-t3077799
I HIGHLY recomend booting to stock LG recovery and doing a factory wipe after flashing the KDZ
Then root using this method: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
install twrp recovery by using the autorec vs985 app from the play store.
Edit: the OTA failed because you had TWRP installed. You could also use the 12B KDZ and then take whatever OTAs are available, that might get you to 24B
Click to expand...
Click to collapse
I'm in the same boat as OP. Essentially there is no difference between 10B and 23C? (Aside from Lollipop vs Kit Kat). You can still root, install a custom recovery, and flash roms like CM?
cooldman224 said:
I'm in the same boat as OP. Essentially there is no difference between 10B and 23C? (Aside from Lollipop vs Kit Kat). You can still root, install a custom recovery, and flash roms like CM?
Click to expand...
Click to collapse
Yes. 24B is the only one not rooted yet.
illyfilly said:
I am fairly competent with installing and wiping and what be, I was comfortable with 10b on my G3 and stuck with it till now. I am ready for LP. I just don't know where to go.
I want to run stock but I also want to tinker with CM again.
What would be the best way to update to a fully working ROM or heck even to 24b?
I can't update on my phone for some reason it just boots to TWRP and I have to flash a fix.
Thanks
Click to expand...
Click to collapse
Since you are running TWRP, that means you are rooted and therefore, it will not take the update because it senses your phone has been modified. You will have to flash back to a stock image (which means it will wipe everything on your phone so back it all up - photos, music, data, etc). This includes everything on the internal SD card (but not the external SD card).
Once you've done that, follow the directions given by others in this thread to go back to a stock image.
roirraW "edor" ehT said:
Yes. 24B is the only one not rooted yet.
Click to expand...
Click to collapse
This was of course before "edor" found out there is actually a root now for 24B.
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197/
iBolski said:
Since you are running TWRP, that means you are rooted and therefore, it will not take the update because it senses your phone has been modified. You will have to flash back to a stock image (which means it will wipe everything on your phone so back it all up - photos, music, data, etc). This includes everything on the internal SD card (but not the external SD card).
Once you've done that, follow the directions given by others in this thread to go back to a stock image.
This was of course before "edor" found out there is actually a root now for 24B.
[/QUOTE]
It's amazing the slight d...ry Reset after using that root on 23C or 24B.
Click to expand...
Click to collapse
roirraW "edor" ehT said:
It's amazing the slight differences in rooting methods with different results. The one that works on 24B doesn't work on 12B, or at least for me it caused endless boot animation even with a reboot, but it was the middle of the night so I don't think I tried a Factory Reset to be sure, but I haven't had to Factory Reset after using that root on 23C or 24B.
Click to expand...
Click to collapse
Isn't it nice how Verizon makes our lives such a b*tch?
Related
What is the recommended version to run? I would like to upgrade without losing data and the ability to root.
I've been having issues with messaging locking up, random FCs, the keyboard locking up during messaging, etc, etc. All in all 23c has been horrible. The only thing I need is root. It is a must.
35b can be rooted with King root
Sent from my VS985 4G using Tapatalk
94SupraTT said:
What is the recommended version to run? I would like to upgrade without losing data and the ability to root.
I've been having issues with messaging locking up, random FCs, the keyboard locking up during messaging, etc, etc. All in all 23c has been horrible. The only thing I need is root. It is a must.
Click to expand...
Click to collapse
I'm not clear on if you're already rooted. If you are, and already have TWRP, use the built in LG Backup to backup your stuff on your current system, then in TWRP follow the appropriate ROM's directions to flash a 35B-based ROM like @xdabbeb 's VS985 v2.0, @hsbadr 's JasmineROM 9.0+9.1 update or @HolyAngel 's SkyDragon v6.x. Then use LG Backup to restore your stuff.
It is currently rooted. I would prefer to stay away from roms. The phone is my lady's. Are there any issues with 35b that I should worry about. I don't mind just going to 24b if there are.
I think 35B works the best of all the Lollipop ROMs. Only thing they changed that myself and others don't like but is fixable is the screen brightness on "auto" goes way too dim too soon in darker lighting. Someone suggested to me the app "Lux Lite" in the Play Store with it being set to "Dynamic" and it works much better now. It's worth it due to how much better 35B/Android 5.1.1 works over 24B/23C/Andorid 5.0.1.
Since you're rooted but don't want to use custom ROMs, I would use LG Backup to backup your stuff to your MicroSD card, use the 35B KDZ in CSE mode to put completely stock unrooted 35B on the phone, which will wipe your internal storage so be sure to move what you want to keep, then use Kingroot to root. I haven't used Kingroot myself but many people have reported it working on 35B, at least since Kingroot was updated.
roirraW "edor" ehT said:
I think 35B works the best of all the Lollipop ROMs. Only thing they changed that myself and others don't like but is fixable is the screen brightness on "auto" goes way too dim too soon in darker lighting. Someone suggested to me the app "Lux Lite" in the Play Store with it being set to "Dynamic" and it works much better now. It's worth it due to how much better 35B/Android 5.1.1 works over 24B/23C/Andorid 5.0.1.
Since you're rooted but don't want to use custom ROMs, I would use LG Backup to backup your stuff to your MicroSD card, use the 35B KDZ in CSE mode to put completely stock unrooted 35B on the phone, which will wipe your internal storage so be sure to move what you want to keep, then use Kingroot to root. I haven't used Kingroot myself but many people have reported it working on 35B, at least since Kingroot was updated.
Click to expand...
Click to collapse
Thanks so much! That is exactly what I will do! I appreciate it.
94SupraTT said:
Thanks so much! That is exactly what I will do! I appreciate it.
Click to expand...
Click to collapse
You're welcome. Good luck!
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
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.
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
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!
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?