If you are on 35b (rooted or unrooted) without TWRP here is a simple guide to get TWRP and rooted Marshmallow 46A on your phone. This is all info available in various threads here on XDA (typically mentioned by roirraW "edor" ehT) and I take no credit for any of this work. After going thru the process yesterday I simply thought it would make it easy for others to find everything in one place with links. Standard disclaimer : use this method at your own risk
1.Use the TOT method to return to 10B (backup your data, this will wipe your phone) http://forum.xda-developers.com/verizon-lg-g3/general/restore-verizon-to-stock-t2827878
The most helpful posts in this thread were the OP, #9 and #236 note: if this doesn't work for you look here http://forum.xda-developers.com/verizon-lg-g3/general/ks-version-error-downgrade-trouble-t3306028
2. Root your phone (now on 10B) using Stump http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
3. After rooted Install SuperSu https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
4. After SuperSU is installed install TWRP using TWRP manager https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
5. Reboot into TWRP recovery and factory reset (just to be safe)
6. Flash 35B bootstack from TWRP recovery http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
7. Wipe data/cache within TWRP
8. Flash 46A in TWRP link to stock http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365 Or use the rom of your choice
9. Reboot to system (do not install superSU from TWRP if using the link above)
For ease of installation I suggest downloading everything to your PC first then create a folder on your SD card called flash and copying the needed apk and zip files to that folder before you get started. This way you won’t have to sign into your google account in 10B to download the APK for SuperSu and TWRP manager. Use apkmirror or a similar site to download what you need.
Any issues to report on running 46A? Any issues with having an SD card?
No issues, I flashed stock 46A yesterday and everything has worked perfectly so far. No problems with SD card, (Sony 32Gb Class 10-UHS1) I mostly have it for photos and music. I have only disabled/uninstalled some preinstalled apps and flashed the hotspot mod so far. Can't comment on battery life, needs a few days to settle.
Are you still able to downgrade back to 35B, if need be?
Not sure haven't tried but I assume this method would work
someguyatx said:
Not sure haven't tried but I assume this method would work
Click to expand...
Click to collapse
I am trying to downgrade, but it fails. It fails with model information check FAIL! I have downgraded before without a problem. Is there a fix for this or am I doing something wrong?
I don't know, you will probably get a better answer in one of the other threads. You may also have to try the alternate method of the tot method doesn't work.
chadhoard said:
I am trying to downgrade, but it fails. It fails with model information check FAIL! I have downgraded before without a problem. Is there a fix for this or am I doing something wrong?
Click to expand...
Click to collapse
I think I answered you in another thread where you asked. Use the 10B TOT method with the new 35B .DLL that came inside in the 35B KDZ, available in the other thread I referenced in my other answer.
roirraW "edor" ehT said:
I think I answered you in another thread where you asked. Use the 10B TOT method with the new 35B .DLL that came inside in the 35B KDZ, available in the other thread I referenced in my other answer.
Click to expand...
Click to collapse
You did!! Everything worked and I am up and running!! Thank you!
Would you happen to know, before I start searching, if Xposed works? If so, where I would be able to downlload it?
chadhoard said:
You did!! Everything worked and I am up and running!! Thank you!
Would you happen to know, before I start searching, if Xposed works? If so, where I would be able to downlload it?
Click to expand...
Click to collapse
Great, glad to hear it. Xposed works for me. I always have to Google for:
Code:
xposed lollipop
I'm pretty sure the Marshmallow xposed can be reached that way too. I think SDK23 is Marshmallow, so that's what you'll look for in the different Xposed flashables.
I have an issue and I had it before I did the above steps I was just hoping upgrading to 6.0 would fix the problem. My G3 boots into the fine but the wireless says "turning On" for about 1 minute and then it finally turns on and asks to connect to my home wireless, I enter the password and within 2 minutes the phone shuts down and will not go past the Red V Verizon screen, it just keeps rebooting. I can go back into TWRP and wipe it and it will boot back into 6.0 again. I was able to turn the wireless off before it went on and side loaded 25 diffenent apps and was able to use the phone for 4 hours without any issues but then I thought I would try the wireless again and it took like 4 minutes to finally turn on then as soon as I connected to a wireless network (office network this time) within 2 minutes it shut down. I was able surf the web and get on Google play store before it shut down but then it went back to the endless reboot loop..
My thoughts are that I might be able to flash a bootstrap update and I am not completely sure if a new one came in the 6.0 Android updated listed above actually came with one and if not I am not sure which one to use.
This all started in middle of December when the daily CM updates went from 5.1 to 6.0 overnight and everything got messed up. I was over trying to fix it so I ordered myself a Nexus 6P for Christmas and then life was good till I ran over it yesterday with my Jeep and destroyed it.. So back to trying to get the G3 working...
thanks for the help
Doug
Doug, What a strange problem. If you use the TOT method to go back to 10B then turn on the Wi-Fi in 10B does it still lock up and boot loop?
I can confirm this method works and I had no issues except for steps that i misread and had to repeat..
I used to be on Rooted on 35B with no Recovery. Now I am on 46A rooted with Recovery.
I am having an issue with a checksum fail on 46a during the twrp install, any suggestions?
(file d-loaded onto PC then copied into the phone memory download folder)
Nesbocaj said:
I am having an issue with a checksum fail on 46a during the twrp install, any suggestions?
(file d-loaded onto PC then copied into the phone memory download folder)
Click to expand...
Click to collapse
Did you verify the md5 on your pc before copying to your sd card?
someguyatx said:
Did you verify the md5 on your pc before copying to your sd card?
Click to expand...
Click to collapse
Yes.
Second try: I d-loaded directly into the phone mem and flashed that, seems to have done the job overnight (!!! ), restoring applications right now.
Thank you for the most excellent guide, not that simple (for me), but very well done.
The phone has become un-rooted with this last flash, TWRP app will not load. OK reloaded and back.
Glad it helped you. I spent several hours reading the forums and installing and wanted to save others some time. Everything was here already just not easy to put the pieces together.
someguyatx said:
Doug, What a strange problem. If you use the TOT method to go back to 10B then turn on the Wi-Fi in 10B does it still lock up and boot loop?
Click to expand...
Click to collapse
Yes it did the same thing in 10B, I was hoping install 6.0 would help the issue but it does the same thing. I can get the wireless to work maybe for a minute, maybe for 30 minutes but then it shuts down and will not boot again till I do a factory reset.
duglas said:
Yes it did the same thing in 10B, I was hoping install 6.0 would help the issue but it does the same thing. I can get the wireless to work maybe for a minute, maybe for 30 minutes but then it shuts down and will not boot again till I do a factory reset.
Click to expand...
Click to collapse
Hardware issue perhaps.
wait how do you know if you are on 35b?
Related
I have the Verizon LG G3 with build 12b installed (Was updated by the store when I purchased phone). Is there anyway to unlock the boot loader and root the device as is, or roll the device back to a previous build that is easily unlockable/rootable?
You should have posted in the q&a forum area.
Anyhow - if you want to root, and install a custom recovery (twrp), use the kdz method to get back to 10b:
http://forum.xda-developers.com/showthread.php?p=56484240
Then from this forum area install the bump/twrp from autoprime, and make sure to either freeze system updates or rename the two LGDMSClient files in /system/app. The freeze or rename is so new ota don't get pushed onto your phone after you get the custom recovery (twrp). Otherwise you'll needed the solution in the "stuck in custom recovery" thread:
http://forum.xda-developers.com/showthread.php?p=56061720
(It is handy to download the "stuck" zip onto your phone as a just-in-case. If you do get an ota, and your phone keeps booting to recovery, tell twrp to Install the zip to clear the ota files )
HTH!
I am trying that method now (actually before you replied) but the kdz file is taking for ever to download. Been running for 30 minutes and still showing 7 hours remaining. I have a really fast internet connection but that one file doesn't wanna download!
markfm said:
You should have posted in the q&a forum area.
Anyhow - if you want to root, and install a custom recovery (twrp), use the kdz method to get back to 10b:
http://forum.xda-developers.com/showthread.php?p=56484240
Then from this forum area install the bump/twrp from autoprime, and make sure to either freeze system updates or rename the two LGDMSClient files in /system/app. The freeze or rename is so new ota don't get pushed onto your phone after you get the custom recovery (twrp). Otherwise you'll needed the solution in the "stuck in custom recovery" thread:
http://forum.xda-developers.com/showthread.php?p=56061720
(It is handy to download the "stuck" zip onto your phone as a just-in-case. If you do get an ota, and your phone keeps booting to recovery, tell twrp to Install the zip to clear the ota files )
HTH!
Click to expand...
Click to collapse
Check post 150 in that thread. annoyingduck posted a second link
markfm said:
Check post 150 in that thread. annoyingduck posted a second link
Click to expand...
Click to collapse
I think I am in love with you, JK.....seriously though thanks a bunch....downloading the Mega link now and it seems to be going MUCH faster.
Did it work for you? I tried to downgrade, when phone said 100% it rebooted. I had a dark screen.... Went to the Verizon store, was told it was hard bricked. Haven't tried rooting my replacement yet.
Early adopter, got my phone in July, used the original ioroot, never had to revert.
The kdz method has had quite a few people who succeeded, based on what I read, no idea why it went bad for you. If you are gun shy, understandable, post 2 of annoying duck's thread has a link for the tot approach, supposed to be a slightly more pita way but not too exotic. Key is to flash any existing g3 drivers on your PC, install the proper things used by the tot method.
martinez5241 said:
Did it work for you? I tried to downgrade, when phone said 100% it rebooted. I had a dark screen.... Went to the Verizon store, was told it was hard bricked. Haven't tried rooting my replacement yet.
Click to expand...
Click to collapse
Anyway to downgrade without this happening? I want to run stock lollipop on my G3 but so far am stuck at the VS98512b update too
_AI_ said:
Anyway to downgrade without this happening? I want to run stock lollipop on my G3 but so far am stuck at the VS98512b update too
Click to expand...
Click to collapse
I did the kdz method. Omg you run the program and it starts don't click on any notifications, just let it run. Sorry about the late response.
Update: It works fine now. All I had to do was start over after flashing back to the original stock ROM. Then I UPDATED twrp... Duh... Well yeah
Alright so here we go...
I've debated rooting my lg g3 VS985 for a while and finally decided to do it.... Although many problems insued. I'll start from the top just incase any prior steps lead to my current issue.
As you probably all know the Lg G3 Had an update that patched roots so I flashed it back using an XDA form to 10B. I then rooted using stump root which all went well. Then I used TWRP to go to recovery with the illusion ROM and a Gapps saved to my SDcard. Problem is they didn't show up... (Unable to mount sdcard unknown error 150) But we finally got it to work through ADP sideload. We didn't clear cache or factory reset though. After reboot and install it kept saying unfortunately YouTube has stopped so i did a factory reset from the settings menue. We then got it into recovery (though twrp was gone) and ADP Gapps but it failed with status 7. I tried installing twrp app from the web but it just crashes immediately after being opened and as stated before my sdcard wont mount in recovery due to unknown error 150. I've looked all over but found nothing. All help is appreciated.
Hi
Thanks for writing to us at XDA Assist. In order to direct you properly I need to know which variant of the G3 you have please. Is it a carrier (Sprint, at&t, etc) version or the unbranded version?
Transmitted via Bacon
timmaaa said:
Hi
Thanks for writing to us at XDA Assist. In order to direct you properly I need to know which variant of the G3 you have please. Is it a carrier (Sprint, at&t, etc) version or the unbranded version?
Transmitted via Bacon
Click to expand...
Click to collapse
The VS985 or the Verizon variant
Thanks for the extra information. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your specific device forum here (bookmark/subscribe this):
Verizon LG G3
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Verizon G3 Q&A, Help & Troubleshooting
Good luck!
Transmitted via Bacon
artrex654 said:
Alright so here we go...
I've debated rooting my lg g3 VS985 for a while and finally decided to do it.... Although many problems insued. I'll start from the top just incase any prior steps lead to my current issue.
As you probably all know the Lg G3 Had an update that patched roots so I flashed it back using an XDA form to 10B. I then rooted using stump root which all went well. Then I used TWRP to go to recovery with the illusion ROM and a Gapps saved to my SDcard. Problem is they didn't show up... (Unable to mount sdcard unknown error 150) But we finally got it to work through ADP sideload. We didn't clear cache or factory reset though. After reboot and install it kept saying unfortunately YouTube has stopped so i did a factory reset from the settings menue. We then got it into recovery (though twrp was gone) and ADP Gapps but it failed with status 7. I tried installing twrp app from the web but it just crashes immediately after being opened and as stated before my sdcard wont mount in recovery due to unknown error 150. I've looked all over but found nothing. All help is appreciated.
Click to expand...
Click to collapse
Hi!
I'm going to recommend a complete clean install, which you've already done, but with an additional step that you might think is weird but it saved me once on a previous phone, and sometimes weird problems have weird solutions.
First, take and keep the MicroSD card out. I know it shouldn't affect things, but it won't hurt, either. Don't put it back in until everything is working the way it should. Once you have a running phone, if you need to flash anything else that's not on your internal storage any longer because flashing a stock ROM KDZ or TOT will wipe your internal storage, then you can connect the phone to your PC and transfer what you need to it that way, or download directly to the phone.
Second, you said you flashed to 10B. Did you use the 10B_01 KDZ or the 10B_03 TOT. It won't necessarily matter which, but it's good to have that information just in case. Personally, I recommend the KDZ because I've not had luck with the TOT, but I've heard the same thing from a few other people about recommending the TOT because they've had problems with the KDZ. So whichever you used, maybe you should try the other even though you actually seemed to successfully use it as far as we can tell.
Make sure and use "safely remove USB" options under Windows and Android before you remove any USB device. That doesn't apply to having the phone connected to the PC, there is no "safely remove..." function for that.
Use and test stock 10B on your phone until you're sure it's behaving correctly. Only then use Stump to root, download TWRP Manager from the Play Store, install the latest TWRP through that, reboot to recovery to test it, and then try flashing Illusion and GAPPs.
If I think of anything else, I'll update this. Please update if you try what I recommend.
Maybe the GAPPs was the issue? Where did you get it from and is it the latest?
I used the TOT and I got two of the Gapps from XDA forums and the third from amdroidbitz.
Hey all, ran into a (probably rookie) mistake yesterday.
I was running my phone on Cyan13 with 35B and decided, after seeing how popular it was, to check out JasmineROM 9.1. I downloaded the ROM files, 9.0 and 9.1 as well as some of the ancillary files, copied them to my phone and started the install process. I flashed 9.0, then 9.1 and then rebooted...my phone went blank.
You could see that the phone was still "working" but the screen was completely blank. I could take screenshots with power + vol down like normal, and hear the sound. Plus I could type on the screen (i could hear the touch tones), but the screen itself was completely black. Even during reboots you couldn't see the LG logo and since it was a new ROM I didn't have usb debugging on so I couldn't (assumed anyways) get into adb from my computer either.
After some digging, I ended up doing the following...as much of a PITA it was, it worked and I'm extremely thankful for the posts here on XDA and all of the contributors...so follow along if you're having this issue and you should be good to go.
Run the process found here with BoardDiag and TOT (I used the 10B.03 file found here --- http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488) (also yes the site says for Sprint, it works on Verizon as well) --- http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Then use the LG Flash Tool found here to flash the 12B KDZ firmware (make sure you download the 12B file) --- http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Go into the app store after your phone boots and install King Root --- http://www.kingroot.net/
Install TWRP from here --- http://forum.xda-developers.com/ver...recovery-twrp-touch-recovery-2-8-2-0-t2966014
Start doing your own thing again
Remember that you're on 12B at this point. The All in One tool found here --- http://forum.xda-developers.com/verizon-lg-g3/general/verizon-lg-g3-one-toolkit-vs985-root-t3124846 --- did NOT work for me for some reason, probably the various drivers that are required. That's why I used King Root.
Hope this helps someone.
The problem was that you had the 35B bootstack flashed before JasmineROM. JasmineROM (and SkyDragon) contain some older partitions. If you flash the 35B bootstack after its fine, even if you already had the 35B bootstack flashed before the ROM.
You didn't have to use BoardDiag. Even though the screen didn't show anything it still gets in Download mode.
Edit: my info regarding Download mode is not applicable in these users' case - they confirmed they couldn't get into Download mode no matter what. Sorry for the confusion.
For some reason mine wasn't entering download mode. Even without the screen showing I could see the LED flashing and then if you tapped the screen you'd hear the touchstone sounds. It was strange but it's fixed now.
roirraW "edor" ehT said:
The problem was that you had the 35B bootstack flashed before JasmineROM. JasmineROM (and SkyDragon) contain some older partitions. If you flash the 35B bootstack after its fine, even if you already had the 35B bootstack flashed before the ROM.
You didn't have to use BoardDiag. Even though the screen didn't show anything it still gets in Download mode.
Click to expand...
Click to collapse
Are you sure? Mine would not go into dl mode and I tried both TOT and KDZ methods.
CaptainElwood said:
Are you sure? Mine would not go into dl mode and I tried both TOT and KDZ methods.
Click to expand...
Click to collapse
You tried the board diag method? Make sure you're getting a good ground on the board and hold it for a few seconds...basically while holding the wire and attaching the USB cable to the computer watch device manager, specifically under the COM port section. Once you see the phone show up you can remove the wire, being careful not to touch any of the other pins. If you're running Vista or newer you must use the bcdedit commands from that post AND reboot into F8 and select disable driver signing (can't remember the exact verbiage).
Once you're done, I'd reverse those bcdedit commands BTW. Just a thought for the cleanup process.
malhovic said:
For some reason mine wasn't entering download mode. Even without the screen showing I could see the LED flashing and then if you tapped the screen you'd hear the touchstone sounds. It was strange but it's fixed now.
Click to expand...
Click to collapse
CaptainElwood said:
Are you sure? Mine would not go into dl mode and I tried both TOT and KDZ methods.
Click to expand...
Click to collapse
My mistake, sorry!
roirraW "edor" ehT said:
My mistake, sorry!
Click to expand...
Click to collapse
No need to be sorry, sometimes things act differently all depending on the steps people took with their devices. I was really hoping it would pop into download mode so I didn't have to run BoardDiag as I didn't feel like taking things apart (save for the back off so I could get to the battery).
Either way, hopefully the idea works for someone else so they don't have to go through all the extra steps that I (and others) have. :laugh:
malhovic said:
No need to be sorry, sometimes things act differently all depending on the steps people took with their devices. I was really hoping it would pop into download mode so I didn't have to run BoardDiag as I didn't feel like taking things apart (save for the back off so I could get to the battery).
Either way, hopefully the idea works for someone else so they don't have to go through all the extra steps that I (and others) have. :laugh:
Click to expand...
Click to collapse
Yes, it's funny the different behavior on theoretically the same hardware. It's probably still applicable that flashing the bootstack before and not after the ROM was the cause.
I had the 35b bootstack when I installed JasmineROM and so far I am unable to get into download mode, when I take out the battery the screen actually turns on for a second. I am installing a VM for Windows 8 to see if that will help with my issues of not detecting the device.
I wish I'd seen this before trying to go back Jasmine after flashing 35b, thanks so much for the guide! My screen wouldn't come on, but was actually still going into download mode (keep volume up button depressed for about 10 seconds after it vibrates and it entered DL mode.) I used this method http://forum.xda-developers.com/showthread.php?t=2475045 to get back to KK stock. Here is the DL link to the TOT http://www.mediafire.com/download/6i..._Stock_TOT.zip. Also needed the LGUP8974.dll to complete the operation (don't have the link for that one, sorry.) Hope this helps a few and thanks again!
I got an LG G3 that came packaged with 35B (5.1.1), and nothing seemed to be working to get TWRP installed. I couldn't use LG Flash Tools to downgrade using the "TOT" method, because it'd stop with an "no ks version" error. I finally found something that works, and I'm now running AICP (nice ROM) with TWRP installed!
The trick is to follow these instructions (make sure you use VS985 components for our Verizon LG G3s, not D855):
http://forum.xda-developers.com/lg-g3/help/help-secure-boot-error-trying-to-boot-t3054977
Overwrite aboot.img (12B version) & recovery (TWRP image) using dd commands via an adb shell, after rooting with KingRoot, while Android is running. I then used adb commands to reboot into recovery, and volia! I was in! I had AICP on my internal card, and the 12b bootstack, which I flashed in that order.
After seeing AICP successfully boot, I went back and flashed the 35B bootstack. Success!
Stock images (aboot 12B etc.): http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
Bootstacks: http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
KingRoot: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Great news for you and others. Thanks for sharing!
Well, i tried to follow this step by step and I ended up with a black screen after reboot. My G3 would power up, blue and green led's would flash like normal, I could hear the sounds being made by pressing the power button and touching the screen just like everything went as planned except for a black screen. My PC still recognized my device when Android was running and it was still detected when I entered download mode. I could see the device driver installation window popup on my PC and I could see my G3 in my Device Manager as well. I am a little unsure about what went wrong but I am doing my research to see if I can solve this problem. The good thing about the whole situation, I was able to use LG FLashTools 2014 to KDZ back to 35B which is what I was running at the beginning of this process. The software flash just finished and so did "Android is starting" so I will set this thing back up and try again once I find out what went wrong and why I received the black screen afterwards. If anyone can provide any input as to what my have happened or if there was something I missed I would appreciate it.
fast69mopar said:
Well, i tried to follow this step by step and I ended up with a black screen after reboot. My G3 would power up, blue and green led's would flash like normal, I could hear the sounds being made by pressing the power button and touching the screen just like everything went as planned except for a black screen. My PC still recognized my device when Android was running and it was still detected when I entered download mode. I could see the device driver installation window popup on my PC and I could see my G3 in my Device Manager as well. I am a little unsure about what went wrong but I am doing my research to see if I can solve this problem. The good thing about the whole situation, I was able to use LG FLashTools 2014 to KDZ back to 35B which is what I was running at the beginning of this process. The software flash just finished and so did "Android is starting" so I will set this thing back up and try again once I find out what went wrong and why I received the black screen afterwards. If anyone can provide any input as to what my have happened or if there was something I missed I would appreciate it.
Click to expand...
Click to collapse
Weird... this is what I did (nothing more):
1) Pick a ROM I wanted to use. I went with AICP nightly for VS985 (MM 6.0.1). Put that ROM zip to be flashed by TWRP on your internal memory.
2) Put the 12B bootstack on internal memory.
3) Put the 12B aboot.img & latest TWRP img on internal memory.
4) Root with KingRoot
5) Open up an "adb shell" and use "su" to get a root shell.
6) Use dd commands (like in the original post's link) to zero, flash aboot & the recovery image to their proper partitions.
7) Use "adb reboot recovery" to boot into TWRP
8) Factory reset
9) Flash ROM (AICP etc.)
10) Flash 12B bootstack (not 100% sure needed, but whatever)
11) Wipe cache/dalvik (not 100% sure needed, but whatever)
12) Reboot & profit!
After seeing successful boot, I did go back into TWRP & flash the 35B bootstack, just to have the latest stuff that still does work.
I *did* have one oddity where my screen went black, but NOTHING was responsive (not even the LED). Phone just appeared completely dead -- no response to anything. I pulled the battery, and it booted up fine. Hasn't happened again...
It was weird indeed. I flashed the 35B KDZ to return to stock after the screen went black. I was already on the stock 35B OTA that I received back in October. I was already rooted with Kingroot and had already removed Kingroot with SuperUser in its place. Was that something that was different between us maybe? Were you on the stock 35B, unrooted, before you started the process? Like I said, I was already rooted. Don't know if it makes a difference or not. Since I was able to flash back to stock after the mishap I will be trying it again here shortly when I get back in from of my Laptop. I am fully stock right now and my software status is official. I will do the process over again starting with a fresh template. I'll edit my post with an update after I'm finished. Thanks for the response and for the guide.
fast69mopar said:
It was weird indeed. I flashed the 35B KDZ to return to stock after the screen went black. I was already on the stock 35B OTA that I received back in October. I was already rooted with Kingroot and had already removed Kingroot with SuperUser in its place. Was that something that was different between us maybe? Were you on the stock 35B, unrooted, before you started the process? Like I said, I was already rooted. Don't know if it makes a difference or not. Since I was able to flash back to stock after the mishap I will be trying it again here shortly when I get back in from of my Laptop. I am fully stock right now and my software status is official. I will do the process over again starting with a fresh template. I'll edit my post with an update after I'm finished. Thanks for the response and for the guide.
Click to expand...
Click to collapse
I was on a "fresh", unrooted flash of the 35B KDZ after some previous failed attempts to get TWRP installed. Then, I started my steps listed above. I didn't swap out KingRoot to SuperSU (since I knew it'd just be overwritten when AICP gets installed). Just needed root to flash aboot & recovery.
What command did you run to flash the twrp img, in the other link with the commands of says he used flashify but you used terminal to flash yours. Thanks.
It works.
New here, also with VS985 35b. LG Flash tool kept giving me failed previous flash on every attempt to downgrade to 10b. Saw this and using the same aboot.img and bootstack.zip that you used, I used terminal emulator to update and it worked first time. I just had to remember to use VS985 components including twrp. Everything is now running, and am so thankful. My first G3, previously rooting and playing with Samsung S4. Again, thank you for your incredible work.
jimtom1948 said:
New here, also with VS985 35b. LG Flash tool kept giving me failed previous flash on every attempt to downgrade to 10b. Saw this and using the same aboot.img and bootstack.zip that you used, I used terminal emulator to update and it worked first time. I just had to remember to use VS985 components including twrp. Everything is now running, and am so thankful. My first G3, previously rooting and playing with Samsung S4. Again, thank you for your incredible work.
Click to expand...
Click to collapse
You mind giving m the exact commands you used and the order you did everything in? Got a little confused going from thread to thread to get everything downloaded. Think I read too much.lol confused myself
Evohog
1) Started on this site and downloaded:
Stock image (aboot.img 12b)
bootstack (12b) down the page in downloads.
This is important because the instruction page is for D855 and you need VS985 aboot and bootstack. This was what initially confused me.
2) I then went to the page that says follow these instructions.
Here I downloaded oversharpening fix flashable zip and a twrp recovery for VS985.
You will want to substitute VS985 aboot and bootstack for the D855 in his writeup.
3) I followed the rest of his tutorial, very carefully typing the commands into terminal emulator. (I haven't got my linux machine ready for adb yet.
4. Shut down the phone. rebooted into recovery (You can use flashify settings to reboot into recovery, or the buttons on back of the phone after shutdown.
5. It worked, I was in twrp. Flashed the oversharpening and the 12b bootstack.
Hope this helps.
jimtom1948 said:
1) Started on this site and downloaded:
Stock image (aboot.img 12b)
bootstack (12b) down the page in downloads.
This is important because the instruction page is for D855 and you need VS985 aboot and bootstack. This was what initially confused me.
2) I then went to the page that says follow these instructions.
Here I downloaded oversharpening fix flashable zip and a twrp recovery for VS985.
You will want to substitute VS985 aboot and bootstack for the D855 in his writeup.
3) I followed the rest of his tutorial, very carefully typing the commands into terminal emulator. (I haven't got my linux machine ready for adb yet.
4. Shut down the phone. rebooted into recovery (You can use flashify settings to reboot into recovery, or the buttons on back of the phone after shutdown.
5. It worked, I was in twrp. Flashed the oversharpening and the 12b bootstack.
Hope this helps.
Click to expand...
Click to collapse
One last question, where in the commands it says "block/name/a boot" so I enter vs985 where it says name or do I enter name. I'm so rusty,it's been a couple years since I've even rooted anything. Thanks again for the hand holding.
Evohog
If you are talking about the commands that you type into the terminal emulator, you enter them just as they are written, except for what is in quotes. Don't change them. Good Luck.
Hey guys, Tried this and now im hard bricked. Could anyone give me a hand? I have everything posted here.
http://forum.xda-developers.com/verizon-lg-g3/help/kdz-restore-t3315170/post65328929#post65328929
johnny567
I was successful twice with this method. The third time, it bricked so hard I couldn't even get into download mode. After a ton of reading, I found a recommendation in
verizon-lg-g3/general/restore-verizon-to-stock-t2827878/page24 no. 236 by jhtrades 1 at the bottom of his recommendation (ALT METHOD #2).
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928. I followed along starting with step 6, no wire, and somehow got the phone back to a version of verizon with a problem in the bootloader. At least, I was able to get into download mode and did a KDZ to 10b. After that everything was back on track.
I am not absolutely sure if this will work for you, or exactly sure what I did, but it's the best I can come up with. All I remember at the time, was it seemed complicated. Good luck and hope you get it back and working.
jimtom1948 said:
I was successful twice with this method. The third time, it bricked so hard I couldn't even get into download mode. After a ton of reading, I found a recommendation in
verizon-lg-g3/general/restore-verizon-to-stock-t2827878/page24 no. 236 by jhtrades 1 at the bottom of his recommendation (ALT METHOD #2).
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928. I followed along starting with step 6, no wire, and somehow got the phone back to a version of verizon with a problem in the bootloader. At least, I was able to get into download mode and did a KDZ to 10b. After that everything was back on track.
I am not absolutely sure if this will work for you, or exactly sure what I did, but it's the best I can come up with. All I remember at the time, was it seemed complicated. Good luck and hope you get it back and working.
Click to expand...
Click to collapse
It doesnt seem to be working for me. It is pulling up as the Qualcomm 9008 and i have tried with and without wire. It keeps failing and I end up with the error "No response from the device. Check PMIC first and if still boot problem replace AP." I noticed that I have a vs985k. Do you think that could contribute to the failure?
Hey folks. I'm in need of some help, but need to provide some background info as it seems there might be a few ways to correct this.
Background
I had a recent bad Nandroid mess up a restore process which somehow led to me losing root. I was on XDABBEB's 47A stock rooted ROM for months, then went to try the 3.1.1 ROM recently. I found that I wanted to go back, then BOOM! Bad restore from my data NANDROID. Then I:
Got stuck in a boot loop.
Rebooted into recovery
Saw the LG Recovery
(Stupidly?) chose to wipe cache
Continued to boot from LG Recovery
Went immediately to TWRP
Wiped Data and caches
Rebooted
At this point, I got back into 47A, but obviously without any data. I soon found that, though SuperSU was installed, it wasn't working:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-rot - consult the relevant forums for your device!
Click to expand...
Click to collapse
At this point, I checked Root Checker app and, surely enough, it says I wasn't rooted.
I checked ADB and tried to su from the prompt ($) and
Code:
su: notfound
However, adb reboot recovery brings me to TWRP
I tried TOT'ing on my Windows 10 (x64) machine, but it wasn't working:
PID: FAIL
IMEI: Unknown
[23:59: 0] CrossDL [Unknown] to [VS985].SW ***The text on this line continues, but I can't read it***
00000064
Error: [23:59: 0] CrossDL [Unknown] to [VS985].
Click to expand...
Click to collapse
I'm lucky in that my phone is currently working fine. I'm on 47a with everything working fine ... just not rooted, which I would really like to be.
So, my question is, what should I do next? I know some options that I have, I just don't know what options I should try or in what order I should try them...I understand some of the jargon and background info, but I don't understand the true inner workings of rooting and therefore don't feel comfortable making these choices on my own.
So, to all of you people that are way more intelligent at this than I am...
Should I try restoring my rooted 49A backup from TWRP?
Should I try to flash SU binaries in TWRP?
Should I TOT from my work machine that is Windows 7?
Should I KDZ on Windows 10?
Thanks in advance for your collective help.
This inquiring mind wants to know!
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone. In that case, you must flash back to 10B via the TOT method. That way, you can then root with Stump and then install TWRP, flash the correct boot images, and then reflash XDEBs ROM.
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method. It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
iBolski said:
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone
Click to expand...
Click to collapse
Correct. xdebbeb's stock 47A on a non-K model
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method.
Click to expand...
Click to collapse
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
Click to expand...
Click to collapse
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
my.ads0 said:
Correct. xdebbeb's stock 47A on a non-K model
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
Click to expand...
Click to collapse
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
iBolski said:
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
Click to expand...
Click to collapse
I just want to make sure that you're aware that I am NOT on pure stock 47A. I'm on xdabbeb_stock_vs98547a.zip from here.
When I flashed back from his 3.1.1 ROM, I flashed to my backup of the above ROM, which had Root. The SYSTEM flash from my nandroid back to his version of 47A worked without incident, but the DATA flash of my nandroid failed, left me in a bootloop, after which I performed the actions outlined in my original post. That squarely left where I am now, with no root, but on his version of 47A (I never had the stock 47A on my device before) with TWRP as my recovery.
In the end, I'm game for trying different things, but ideally, I'd like to try the least invasive method (trying to flash SuperSU in TWRP?; trying to flash my xdabebb 3.1.1 version?) ) before trying any other method or going to the extreme method (TOT'ing). I just am trying to avoid TOT'ing since my phone IS working AND the fact that I would have to do that at work. It would suck to go from a working phone to a broken phone without being able to fix it without knowing that I tried all of the least invasive methods first. I just need guidance from people like you as to what will or won't work in my situation.
The reason for this post is that I wasn't sure that you were aware I wasn't on pure stock 47A, but on xdabebb's version, which maybe you had overlooked and offered me more options? If you were aware of that and everything above is irrelevant, then I'm cool with that. Just tell me so. I just didn't want that fact overlooked.
Thanks again for entertaining my inquisitiveness, iBolski.
Well, trying to install the SuperSU binary zip from TWRP didn't work. That got me flashing blue & red lights. I tried restoring my XDABEBB 49A 3.1.1 install and that didn't help either. Both TOT & KDZ methods are failing on my PC (Windows 10) with both not able to read the phone properly (can't see imei). I will maybe try to uninstall the drivers or just wait until Monday to try my windows 7 machine at work.
Oops.
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
my.ads0 said:
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
Click to expand...
Click to collapse
Awesome. I saw your earlier post about being on XDEBB but that didn't matter. You were at a point that flashing back to 10b was your best option to get back to XDEB. That's why I kept saying you needed to flash back to 10B if you wanted to get back on XDEBB because where you were at that point was messed up, so it was just best to flash to 10b clean.
Glad you got it all worked out!