Has anyone been able to install TWRP on a 35b rooted phone... I rerooted with kingroot and then replaced it with SuperSU Me with no issues this time... I did install twrp with twrp manager but it did not work.... Now my regulare recovery doean't work either.... I can do a kdz flash again if I have to. the phone itself still works no problem..
I think I mentioned before but this is applicable to this problem - you can use the root terminal DD commands as given at the bottom of @bweN diorD 's stickied thread in General to reflash just the stock 35B recovery.img, which he also has linked among all the other partitions for all of the LG builds. Otherwise, using the 35B KDZ is the only alternative since you haven't been able to downgrade.
It's known and expected that flashing TWRP through TWRP Manager on anything Lollipop and newer won't work as intended.
If you do the DD command method, I'd be tempted to first (instead) downgrade your bootloader (aboot.img) to the 12B one, and also the Download mode partition (laf.img) to the 24B one. Downgrading the bootloader might enable you to use/get into the TWRP you flashed. If that doesn't work, downgrading the laf.img should enable you to be able to use LG Flash Tool 2014 to downgrade to 10B so that you can root using the Stump app easily, and then be able to use TWRP Manager to flash TWRP and then be able to flash whatever ROM you want.
For performing DD commands, I'd copy/paste on the phone itself from his stickied thread so that you don't get a command wrong and brick your device.
Thanks I will give it a try tonight.
Sent from my VS985 4G using Tapatalk
My only question is I know I have to type in laf.img in one spot, but at the end of the command what name do I put.... I can use command line on a pc, but phone is new to me... It would be nice if you could just flash the dam thing LOL
dd if=/sdcard/**.img of=/dev/block/platform/msm_sdcc.1/by-name/*
doubledragon5 said:
My only question is I know I have to type in laf.img in one spot, but at the end of the command what name do I put.... I can use command line on a pc, but phone is new to me... It would be nice if you could just flash the dam thing LOL
dd if=/sdcard/**.img of=/dev/block/platform/msm_sdcc.1/by-name/*
Click to expand...
Click to collapse
laf
roirraW "edor" ehT said:
laf
Click to expand...
Click to collapse
I quess it worked. my phone boots but I do not have download mode anymore... Now to figure how how to correct it, so I can have a working phone...
Got it fixed, Boy nothing seems to work with getting rid of theis 35B B.S.
doubledragon5 said:
Got it fixed, Boy nothing seems to work with getting rid of theis 35B B.S.
Click to expand...
Click to collapse
Had you also flashed the downgraded (12B) aboot.img (bootloader)? Not to try to confuse you, to throw one more item into the mix, but @xdabbeb 's 35B bootstack zip contains all of the same 35B partitions extracted from the KDZ except it has the 12B bootloader and 24B Download partition. Since you already flashed the 35B KDZ (I think?) we know you're running the exact same software, so I'm starting to think there's actually a slight difference with your phone hardware. That's the only thing that makes sense to me, and would apply to those others who got the "ks error" with trying the TOT method.
Anyway, back to the bootloader. Had you tried downgrading that to see if you can get into TWRP that you tried flashing? Again, though, I'm not responsible if this bricks your device, so no pressure from me to actually try this. Just wondering if you did. It's possible that the 24B Download partition wouldn't work with anything but the 12B bootloader.
Did you just flash the 35B laf.img to fix your Download mode?
And when you thought you didn't have Download mode anymore, did you just have a black screen? If so, did you try connecting it to your PC and see if in it's listed in Device Manager under modem, which would confirm it actually was in Download mode despite the black screen? That's common when there's a weird mis-mash of partitions although the 24B Download mode does come up fine with everything else 35B except for the 12B bootloader.
roirraW "edor" ehT said:
Had you also flashed the downgraded (12B) aboot.img (bootloader)? Not to try to confuse you, to throw one more item into the mix, but @xdabbeb 's 35B bootstack zip contains all of the same 35B partitions extracted from the KDZ except it has the 12B bootloader and 24B Download partition. Since you already flashed the 35B KDZ (I think?) we know you're running the exact same software, so I'm starting to think there's actually a slight difference with your phone hardware. That's the only thing that makes sense to me, and would apply to those others who got the "ks error" with trying the TOT method.
Anyway, back to the bootloader. Had you tried downgrading that to see if you can get into TWRP that you tried flashing? Again, though, I'm not responsible if this bricks your device, so no pressure from me to actually try this. Just wondering if you did. It's possible that the 24B Download partition wouldn't work with anything but the 12B bootloader.
Did you just flash the 35B laf.img to fix your Download mode?
And when you thought you didn't have Download mode anymore, did you just have a black screen? If so, did you try connecting it to your PC and see if in it's listed in Device Manager under modem, which would confirm it actually was in Download mode despite the black screen? That's common when there's a weird mis-mash of partitions although the 24B Download mode does come up fine with everything else 35B except for the 12B bootloader.
Click to expand...
Click to collapse
Yup I had downgraded both, with no luck with getting twrp to boot.... When I went into download mode, I did get the download screen, but then it would go blank and the light in the corner would flash blue, then red none stop... So I ended up getting back to the main screen (yes it would boot, and boot then dd command stock partitions back on the phone, and the phone would once again boot into download mode and stay there... I'm not sure what different hardware I would have... I do know according to the sticker on the box, this phone was made 10/2015.. Is there a program that will list the phone exact hardware info? That was I can post it here if possible..
doubledragon5 said:
Yup I had downgraded both, with no luck with getting twrp to boot.... When I went into download mode, I did get the download screen, but then it would go blank and the light in the corner would flash blue, then red none stop... So I ended up getting back to the main screen (yes it would boot, and boot then dd command stock partitions back on the phone, and the phone would once again boot into download mode and stay there... I'm not sure what different hardware I would have... I do know according to the sticker on the box, this phone was made 10/2015.. Is there a program that will list the phone exact hardware info? That was I can post it here if possible..
Click to expand...
Click to collapse
I doubt if the difference would be anything any user program could distinguish. It would have to be not much different since it's compatible with the same KDZ. Just some small tweak they did on phones manufactured late last year is my guess.
I'd be tempted to make a thread asking others with the ks error when their phones were manufactured. Just a guess though.
Related
I know this thread has been posted millions of times, nothing at all works for me
Ok so I rooted my phone yesterday and thought I'd try Cyanogen Mod. After following every step in the Wiki, it had me install AutoRec and reboot, and now I'm stuck at:
Fastboot mode started
udc_start()
- reset -
- portchange -
fastboot: processing commands
When trying LF Flash Tool, it says phone is disconnected, I can't go into download mode, or do anything like that, only fastboot mode. When trying to go into download mode it works for a second before going into fastboot again. Hardware factory reset does not work either.
I've tried MANY threads/videos/etc (B2CApPSetup; LG United; some Fastboot tool; LG FlashTool; SO many more) and none of the programs work. I really need my phone and I desperately need any help. I have ZERO clue where to go from here. I thought about just trying to install CM again through whatever means possible but I can't even seem to be able to reset the phone to stock.
If factory reset isn't taking you to the recovery, it sounds autorec didn't work? I don't know, I don't have a VS980, but in your position I'd make sure the LG driver package was installed, make sure Windows is actually using the fastboot driver when connected in the device manager (Win 8.1 here, I've always had to manually tell it what driver to use), then I'd fastboot flash a twrp img, which would hopefully allow factory reset to take me to recovery. If that works, you'll probably have to adb push a Rom over.
Hopefully someone with a little more insight can help you further / better.
It's not really bricked at all. You most probably downloaded AutoRec for an other variant, next time read more carefully.
You'll need to flash the stock aboot, boot and laf images back using fastboot.
I know you said fastboot doesn't work, but it has to work. Try updating your drivers, use a different PC or something. You can download said image files from here, BUT I'm not familiar with your variant, so I have no idea which version you should download, it would be the best to use the ones you've just overwritten with AutoRec; if they are on the linked server, good for you, if they aren't, you might better extract them yourself from the kdz.
I followed some link to tell me what kdz to get, its' called VS98026A_00.kdz. How do I go from here to just reset my phone completely?
This is pretty much my problem:
Reddit r/lgg2/comments/2b7tob/installed_autorec_and_stuck_at_the_boot/
I'm amazed I got this far. I really need all the little details I can get lol.
gyazo.com /56a5a1ff9b071f8505b883c753dcf6d9
Ok so I tried LGFlashTool once more after doing fastboot with LAF.img and says it can't find phone.
Sounds like you should update your LG drivers.
If you can't get download mode to work, flash these images the same way you flashed that laf.img one. I think you'll be able to boot to system just fine. I included a laf.img in the rar as well, you can skip that one I guess.
Hid3rs said:
Sounds like you should update your LG drivers.
If you can't get download mode to work, flash these images the same way you flashed that laf.img one. I think you'll be able to boot to system just fine. I included a laf.img in the rar as well, you can skip that one I guess.
Click to expand...
Click to collapse
I flashed boot.img then restarted and it was stuck at LG icon. I restarted it and got it into firmware update and it seems to be frozen at 0%. Was I supposed to do aboot before fastboot reboot? Thank you so much for your help btw, I have no idea what I'm doing really.
Sounds like you put a different version of a bootstack your vs980. I've seen too many people screw their phones using autorec. If you can't get it fixed by doing a kdz restore and are still under warranty, call vzw and get a warranty replacement.
Then use my Freedom Tools made only for the VS980 to get a custom recovery on your phone to flash roms.
http://forum.xda-developers.com/showthread.php?t=2713954
I fixed it! Thanks so much!
MicroMod777 said:
Sounds like you put a different version of a bootstack your vs980. I've seen too many people screw their phones using autorec. If you can't get it fixed by doing a kdz restore and are still under warranty, call vzw and get a warranty replacement.
Then use my Freedom Tools made only for the VS980 to get a custom recovery on your phone to flash roms.
http://forum.xda-developers.com/showthread.php?t=2713954
Click to expand...
Click to collapse
nice work。thank you
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?
Everytime i upgrade to an international marshmallow rom i lose 4g signal and becuz of it i get "cell stanby" draining my battery heavily. I tried flashing all the basebands and bootstacks even backedup my efs from an older rom or marshmallow rom on verizon becuz my data works perfect on verizon roms. The right apns looks to be in tact. I just really want this to work becuz this is the lg g5 rom im on. (Fulmics 5.0) i can also still text and call. Just no 4g and bars.
MonstaSaleens said:
Everytime i upgrade to an international marshmallow rom i lose 4g signal and becuz of it i get "cell stanby" draining my battery heavily. I tried flashing all the basebands and bootstacks even backedup my efs from an older rom or marshmallow rom on verizon becuz my data works perfect on verizon roms. The right apns looks to be in tact. I just really want this to work becuz this is the lg g5 rom im on. (Fulmics 5.0) i can also still text and call. Just no 4g and bars.
Click to expand...
Click to collapse
If it's not specifically for the VS985, I wouldn't flash it. You'll have to either fully TOT or KDZ flash it back to fix all your partitions just to be on the safe side.
You should never flash a non-VS985 ROM on the VS985. If you do, you're taking a risk to brick it.
If this was for the VS985, then my apologies, but you didn't specify which ROM it was and I'm assuming since you're postin ghere in the Verizon G3 forums, you have the VS985 G3 and not some other variety.
iBolski said:
If it's not specifically for the VS985, I wouldn't flash it. You'll have to either fully TOT or KDZ flash it back to fix all your partitions just to be on the safe side.
You should never flash a non-VS985 ROM on the VS985. If you do, you're taking a risk to brick it.
If this was for the VS985, then my apologies, but you didn't specify which ROM it was and I'm assuming since you're postin ghere in the Verizon G3 forums, you have the VS985 G3 and not some other variety.
Click to expand...
Click to collapse
Yes it is for verizon, its fulmicsROM 5.0 i chose vs985 in aroma. Other verizon users are saying thier data works without even touching apns. Mine worked in the bigginning but after a couple hours it just did what it did in the pics and havnt worked since.
MonstaSaleens said:
Yes it is for verizon, its fulmicsROM 5.0 i chose vs985 in aroma. Other verizon users are saying thier data works without even touching apns. Mine worked in the bigginning but after a couple hours it just did what it did in the pics and havnt worked since.
Click to expand...
Click to collapse
When you flashed this ROM, what boot partition to you flash from? I did find one in the generic G3 Development forum so I'm assuming the following link is where you probably found it:
http://forum.xda-developers.com/lg-g3/development/rom-fulmics-rom-1-0-tweaks-ota-v20u-t3232340
You might have flashed it with the wrong boot and modem partition. I believe 12B is the last one that works with the current version of TWRP that is bumped for the VS985. Anything above that will not work as they haven't released a new bumped TWRP for the more recent OTAs.
I would find one of the revert back to stock threads, flash it back to a version such as 10B (via TOT or KDZ) and see if your LTE signal comes back. If so, then you should be able to root from there, flash TWRP and then hopefully flash the fulmicsROM at that point and it should hopefully work. If it doesn't work on 10B, then it sounds like your LTE antenna may be going bad.
Otherwise, I'm not sure what is going on.
Hope that helps!
I have same problem. Seems vs985 is updated to 47a witch there is no bumped boot loader for 47a. That may be our problem.
Sent from my VS985 4G using XDA-Developers mobile app
iBolski said:
When you flashed this ROM, what boot partition to you flash from? I did find one in the generic G3 Development forum so I'm assuming the following link is where you probably found it:
http://forum.xda-developers.com/lg-g3/development/rom-fulmics-rom-1-0-tweaks-ota-v20u-t3232340
You might have flashed it with the wrong boot and modem partition. I believe 12B is the last one that works with the current version of TWRP that is bumped for the VS985. Anything above that will not work as they haven't released a new bumped TWRP for the more recent OTAs.
I would find one of the revert back to stock threads, flash it back to a version such as 10B (via TOT or KDZ) and see if your LTE signal comes back. If so, then you should be able to root from there, flash TWRP and then hopefully flash the fulmicsROM at that point and it should hopefully work. If it doesn't work on 10B, then it sounds like your LTE antenna may be going bad.
Otherwise, I'm not sure what is going on.
Hope that helps!
Click to expand...
Click to collapse
Theres nothing wrong with my data when i flash any verizon rom. So when i go back to it it works perfectly. But when i go to any marshmallow rom for multiple variants my data seems it cant connect. Ive tried the kdz method like 3 times and flashed from there but it didnt work. Im not sure about what you mean by what boot partition i flashed from
MonstaSaleens said:
Theres nothing wrong with my data when i flash any verizon rom. So when i go back to it it works perfectly. But when i go to any marshmallow rom for multiple variants my data seems it cant connect. Ive tried the kdz method like 3 times and flashed from there but it didnt work. Im not sure about what you mean by what boot partition i flashed from
Click to expand...
Click to collapse
Depending on the version of Android you used KDZ'd from, that determines what your modem and boot partition are set up as. In order to flash any Marshmallow ROM, you cannot be on the current 72A boot and modem partitions. They do not work with TWRP for the G3. So based on what you've told me, where your LTE signal is fine on stock, that to me suggests one of two things:
You're flashing the custom ROM with an incorrect modem and/or boot partition (later than 10B)
The ROM itself is bad
So, you have to KDZ or TOT back to 10b and flash your ROM from there. I'm assuming that's what you've done, but I wanted to make sure.
The directions in that thread do not give the specifics for the VS985 version.
Here are directions on downgrading to 10B properly so that you can flash custom ROMs properly:
http://forum.xda-developers.com/verizon-lg-g3/general/lg-g3-downgrade-to-10b-t3354834
Here's another thread on doing the same:
http://forum.xda-developers.com/verizon-lg-g3/general/lg-g3-downgrade-to-10b-t3354834
@iBolski From what I read in the Fulmics v5.0 thread, the 12B bootstack is the one that's necessary to have data working on Verizon (for most people). The OP said he tried all the bootstacks though so no idea there.
roirraW "edor" ehT said:
@iBolski From what I read in the Fulmics v5.0 thread, the 12B bootstack is the one that's necessary to have data working on Verizon (for most people). The OP said he tried all the bootstacks though so no idea there.
Click to expand...
Click to collapse
@roirraW "edor" ehT Thanks! I must have missed that somewhere in the thread.
@MonstaSaleens, there's your answer. Make sure you TOT or KDZ back to 12B (I would flash the entire thing). @roirraW "edor" ehT has links in his sig that can point you to all the correct images and instructions you need. The first two links in his sig are what you want.
iBolski said:
@roirraW "edor" ehT Thanks! I must have missed that somewhere in the thread.
@MonstaSaleens, there's your answer. Make sure you TOT or KDZ back to 12B (I would flash the entire thing). @roirraW "edor" ehT has links in his sig that can point you to all the correct images and instructions you need. The first two links in his sig are what you want.
Click to expand...
Click to collapse
Ive done this multiple times before. I even formated internal storage. Went bakc down to 12b used stump root to root and still no data on fulmics. Ive been had problems with the data on roms that are for all varients and are marshmallow. It just doesnt like my phone. But hey, data is doing the same thing on my brothers g3 when he flashed this rom cuz he wanted the new g5 ui too.
roirraW "edor" ehT said:
@iBolski From what I read in the Fulmics v5.0 thread, the 12B bootstack is the one that's necessary to have data working on Verizon (for most people). The OP said he tried all the bootstacks though so no idea there.
Click to expand...
Click to collapse
Do we have any flashable marshmallow radios yet?
MonstaSaleens said:
Do we have any flashable marshmallow radios yet?
Click to expand...
Click to collapse
Short answer: No.
There's technical reasons why we can't use the 46A and 47A modems, at least if you want to be able to use TWRP. There's nothing to stop you from flashing the modem extracted out of the 47A KDZ, but you won't have a signal or data with the modem alone. The 46A and 47A modem require the 46A or 47A sbl1 partition.
Putting the 46A or 47A sbl1 on the phone when you already have working TWRP will cause a QHSUSB_BULK 9008 mode brick because those sbl1 really don't like the 12B (or older) bootloader, and the 12B (or 11C or 10B) bootloader is required to get into TWRP.
So...you can have either:
1. TWRP along with the 12B bootloader, but only up to 35B sbl1 and modem.
Or
2. The Marshmallow bootloader, sbl1 and modem.
I haven't tried or tested getting rid of TWRP and re-upgrading the bootloader, sbl1 and modem, but that should in theory work, at least on stock 46A and 47A ROMs - don't know about international or CM13 ROMs.
Just bought a VS996 on Ebay and followed the Frankenstein steps to get it to US998 and then WTF unlocked the bootloader, installed TWRP, removed encryption, etc, and finally the Verizon 20i ROM designed for TWRP/root.
All was well for a brief time. Then I started debloating the ROM and installed a Magisk module -- Terminal Debloater or something -- figured it was harmless.
Rebooted and I no longer have the Bootloader warning screen and the Verizon white screen with animating dots comes up but never moves past that. I waited at least 15 minutes and then hard reset.
Fortunately I could get into TWRP still so I wiped and flashed the ROM 20i ROM and Magisk again which will boot just fine.
Unfortunately, Download Mode (which worked previously via the Volume Up key for the Frankenstein method) no longer works. I see the mini Download mode icon and then the phone reboots to the LG V30 screen and then the OS. Tried going to Download Mode via ADB and it won't stay then either. Somehow my LAF partition got corrupted?
So TWRP works and so does the 20i ROM rooted. Just no Download Mode. Also "adb reboot bootloader" doesn't work either - just goes to the OS.
Is there anything I can do to bring back Download Mode?
Thanks,
Drew
Once you're on vs996, you don't get the bootloader warning anymore.
Extract the TWRP flashable package, get the laf image and write it to your laf partition with dd. You can also flash it from fastboot
crumbling9999 said:
Extract the TWRP flashable package, get the laf image and write it to your laf partition with dd. You can also flash it from fastboot
Click to expand...
Click to collapse
So in vs99620i.zip found: https://androidfilehost.com/?w=files&flid=287569, I see in the bootloader folder there is a laf.img. I've recently installed the whole ZIP again so shouldn't that have fixed the Download Mode? Or could it be that this ZIP is the reason for the messed up Download Mode in the first place?
Anyway, assuming there's nothing wrong with the laf.img, what are the steps for writing to the laf partition with dd?
I'd ask about the fastboot steps, but I'm not sure I can get to it... As mentioned in my OP, "adb reboot bootloader" is accepted via ADB, but the phone reboots and just goes past the bootloader to the OS. Not sure what is wrong with my bootloader either... Or is it because I'm on VS996 and no longer US998 that I don't have fastboot?
Thank you!
You are correct. Since you flashed back to VS996, you no longer have fastboot.
As for laf, you can use any laf image. Go to the H932 root thread and there is a TWRP flashable laf zip in the first post.
If you want fastboot back, you will need to flash xbl and abl from the US998. Let me know, and I will make you a zip for that as well.
-- Brian
runningnak3d said:
You are correct. Since you flashed back to VS996, you no longer have fastboot.
As for laf, you can use any laf image. Go to the H932 root thread and there is a TWRP flashable laf zip in the first post.
If you want fastboot back, you will need to flash xbl and abl from the US998. Let me know, and I will make you a zip for that as well.
-- Brian
Click to expand...
Click to collapse
So helpful, thank you Brian! Yes I would be most grateful if you could make a fastboot zip for me/others!
There is no issue flashing an H932 laf image/zip on a VS996? I know H932 isn't like other N. American V30s in terms of the WTF method, so just want to be sure I don't mess things up. Maybe you/I could make a US998 laf image/zip?
Thank you again!
Nope, there is no issue flashing any models laf. The laf in that H932 thread isn't even an H932 laf, it is an H930 or H933 don't remember.
Laf is laf is laf
I will make you a zip for fastboot as soon as I can.
-- Brian
runningnak3d said:
Nope, there is no issue flashing any models laf. The laf in that H932 thread isn't even an H932 laf, it is an H930 or H933 don't remember.
Laf is laf is laf
I will make you a zip for fastboot as soon as I can.
-- Brian
Click to expand...
Click to collapse
Flashed the h932_laf.zip in TWRP and think it was successful. However, I still cannot get into Download Mode -- it just reboots and goes to the OS. Guess no more LG UP fail-safe for me? Or is there anything else I can try?
Thanks!
-Drew
drewcu said:
Flashed the h932_laf.zip in TWRP and think it was successful. However, I still cannot get into Download Mode -- it just reboots and goes to the OS. Guess no more LG UP fail-safe for me? Or is there anything else I can try?
Thanks!
-Drew
Click to expand...
Click to collapse
What steps are you taking to go into Download mode? I'm not doubting it's possibly corrupted, just want to make sure you have tried both methods of getting into download mode. LGUP and manually?
Apologies if you have tried this...
Manually with the hardware buttons:
Press and hold the Volume Up key on your LG V30.
While still holding this button connect your phone to the USB cord on your computer.
The download mode should now be displayed on your device.
You can release the Volume Up key and resume the update / downgrade operation.
Click to expand...
Click to collapse
Actually, without fastboot, the vol up + USB is the only way to get to download mode.
Just an FYI, the phone has to be powered off.
So, power off the phone, hold vol up, plug in the USB cable.
There is no reason you wouldn't have download mode if you have a valid laf partition.
-- Brian
ChazzMatt said:
What steps are you taking to go into Download mode? I'm not doubting it's possibly corrupted, just want to make sure you have tried both methods of getting into download mode. LGUP and manually?
Apologies if you have tried this...
Manually with the hardware buttons:
Click to expand...
Click to collapse
No worries, but yes I have tried that. I get the Download Mode tiny icon in the center of the screen and I keep holding Vol Up and it then reboots back to the same tiny icon over and over. I eventually release the Vol Up and it just goes to the OS. But it worked perfectly when I got the phone Friday and tried the Frankenstein LG UP method, etc.
I have also tried rebooting into Download Mode in ADB via "adb reboot bootloader" and also using a root-only Power Menu app in the OS but both just reboot and go right to the OS.
My hunch is it somehow got corrupted when I:
1) Used Titanium Backup to uninstall some system apps like Music, Youtube, Photos, etc and the white Verizon loading screen never let me into the OS and I had to hard reset.
2) Installed vs99620j.zip by John Fawkes which won't boot past the LG V30 screen. This non-booting issue may more have to do with the 20J KDZ than what John did, and no one else has complained about a loss of Download Mode in that thread when I asked the question there.
3) Installed a Terminal Debloater module in Magisk previously. Never actually ran it though, but I installed it as I was debloating via Titanium Backup and when I rebooted, the OS would never load.
I have subsequently flashed the 20i VZ zip with a laf.img and the H932 laf img ZIP which should each have fixed the Download Mode but neither has.
Could there be something else other than the LAF partition which causes my phone to not enter Download Mode?
EDIT: Noticed that my computer's LGUP sees my phone just fine when the Verizon 20i ROM is loaded -- shows up as on COM14 in STANDBY. Download Mode, again, is another story! (And no I don't have LGUP loaded before doing the Vol Up method normally. Tried it this time though just out of curiosity and nothing showed up in LGUP.)
drewcu said:
My hunch is it somehow got corrupted when I:
1) Used Titanium Backup to uninstall some system apps like Music, Youtube, Photos, etc and the white Verizon loading screen never let me into the OS and I had to hard reset.
2) Installed vs99620j.zip by John Fawkes which won't boot past the LG V30 screen. This non-booting issue may more have to do with the 20J KDZ than what John did, and no one else has complained about a loss of Download Mode in that thread when I asked the question there.
3) Installed a Terminal Debloater module in Magisk previously. Never actually ran it though, but I installed it as I was debloating via Titanium Backup and when I rebooted, the OS would never load.
Click to expand...
Click to collapse
Sounds a little bit like you were trying to do too much at one time. I understand the impatience.
Also, others have reported the vs99620j.zip may not quite work right. The dev is investigating issues.
Last, be very careful about debloating where you are permanently removing stuff. With this phone a lot of stuff is connected in ways LG knows and we don't. Personally, I prefer FREEZING in Titanium Backup rather than uninstalling. (However I know Verizon does shove a lot of bloatware down your throat, while I have a US998.)
First, there's system space and user space. Uninstalling "system" apps do not gain you any user space. It may make people "feel better", but it has no advantage whatsoever over just freezing. With freezing, out of sight out of mind, and you won't cause lag because the roots are ripped out and the phone has to pause while searching for something it can't find. (I'm not talking about Verizon branded bloatware, but other stuff.)
Second, if you find you DO need something you froze, it's then simple to unfreeze. There were people who messed up their AOD, their GPS, their Google Pay, their microSD card storage by debloating willy nilly from some alleged "comprehensive" someone posted in this forum of ALL the stuff that could be debloated. Just because you can remove it doesn't mean you should. There was a lot items on that list you should never even touch, unless you are trying to turn your modern smartphone into a simple flip phone.
ChazzMatt said:
Sounds a little bit like you were trying to do too much at one time. I understand the impatience.
Also, others have reported the vs99620j.zip may not quite work right. The dev is investigating issues.
Last, be very careful about debloating where you are permanently removing stuff. With this phone a lot of stuff is connected in ways LG knows and we don't. Personally, I prefer FREEZING in Titanium Backup rather than uninstalling. (However I know Verizon does shove a lot of bloatware down your throat, while I have a US998.)
First, there's system space and user space. Uninstalling "system" apps do not gain you any user space. It may make people "feel better", but it has no advantage whatsoever over just freezing. With freezing, out of sight out of mind, and you won't cause lag because the roots are ripped out and the phone has to pause while searching for something it can't find. (I'm not talking about Verizon branded bloatware, but other stuff.)
Second, if you find you DO need something you froze, it's then simple to unfreeze. There were people who messed up their AOD, their Google Pay, their microSD card storage by debloating willy nilly from some stupid list "comprehensive" list someone posted in this forum of ALL the stuff that could be debloated. There's lots in that list you should never even touch.
Click to expand...
Click to collapse
Yeah, you're right about Freezing as that's what I did after having the Uninstall issues. And yes, you are right about it not recouping user space either, so I am fine just Freezing.
Regardless, not sure why Uninstalling system apps would mess up Download mode; if anything I could see the ROM not loading but that's about it.
Any thoughts on restoring Download Mode in some other way? It's not critical for my phone to work right now, but I can imagine a situation where somehow TWRP gets overwritten somehow and the stock recovery is practically useless. Thankfully I have TWRP and a rooted VZ ROM for now, but it'd be nice to have the insurance in case bad anything happens!
Thanks,
Drew
drewcu said:
I have also tried rebooting into Download Mode in ADB via "adb reboot bootloader" and also using a root-only Power Menu app in the OS but both just reboot and go right to the OS.
Click to expand...
Click to collapse
You won't be able to ADB reboot bootloader while on Verizon firmware. However, if you flashed US998 TWRP flashable zip (converting back to US998), you would again have fastboot flash commands, etc. That might be worth trying, then later you could always flash back to Verizon TWRP-flashable zip.
drewcu said:
Could there be something else other than the LAF partition which causes my phone to not enter Download Mode?
EDIT: Noticed that my computer's LGUP sees my phone just fine when the Verizon 20i ROM is loaded -- shows up as on COM14 in STANDBY. Download Mode, again, is another story! (And no I don't have LGUP loaded before doing the Vol Up method normally. Tried it this time though just out of curiosity and nothing showed up in LGUP.)
Click to expand...
Click to collapse
It does seem somehow your Download mode has been corrupted. The only things I know of (and I'm not a dev) about how Download mode disappears is either corruption or you flash something else over it. Some T-mobile H932 users flash an extra copy of TWRP over LAFF and they lose Download mode -- but they are doing that on purpose for reasons specific to the H932.
runningnak3d said:
Nope, there is no issue flashing any models laf. The laf in that H932 thread isn't even an H932 laf, it is an H930 or H933 don't remember.
Laf is laf is laf
I will make you a zip for fastboot as soon as I can.
-- Brian
Click to expand...
Click to collapse
Yeah I'd appreciate the fastboot zip when you get a chance, thanks!
Any other ideas for restoring Download Mode or is that pretty much shot, you think?
So thanks to the H932 guide and the following, I now have a 2nd working TWRP in place of my Download Mode/LAF partition. When I hold the Vol Up and plug in a USB cable, I first see the tiny Download Mode image as before, but then the 2nd TWRP loads up! Not sure why when I restored a working laf img via TWRP before, Download Mode still wouldn't work, but this will work via ADB. Guess TWRP as a fail-safe in many cases is better than Download Mode, so I'll take it! Perhaps if I flashed the laf img via ADB like this instead of TWRP, it would restore Download Mode, but I'll live with TWRP there for now.
Still would love to have fastboot on VS996 as Brian described on Page 1, if that's even possible.
If you would like a second copy of TWRP on your laf partition (I *highly* recommend this), follow these instructions:
Download the version of TWRP that you want to install onto laf.
Rename it to twrp.img
Boot your phone to TWRP, and connect it to your PC
Open a command prompt where you downloaded TWRP and type:
adb push twrp.img /sdcard/
adb shell dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/laf
With the phone off, hold vol up and plug in the USB cable and you should be greeted by your second copy of TWRP.
Click to expand...
Click to collapse
drewcu said:
So thanks to the H932 guide and the following, I now have a 2nd working TWRP in place of my Download Mode/LAF partition. When I hold the Vol Up and plug in a USB cable, I first see the tiny Download Mode image as before, but then the 2nd TWRP loads up! Not sure why when I restored a working laf img via TWRP before, Download Mode still wouldn't work, but this will work via ADB. Guess TWRP as a fail-safe in many cases is better than Download Mode, so I'll take it! Perhaps if I flashed the laf img via ADB like this instead of TWRP, it would restore Download Mode, but I'll live with TWRP there for now.
Still would love to have fastboot on VS996 as Brian described on Page 1, if that's even possible.
Click to expand...
Click to collapse
If you flashed to US998 TWRP-flashable zip you should have ADB/fastboot flash commands back.
ChazzMatt said:
If you flashed to US998 TWRP-flashable zip you should have ADB/fastboot flash commands back.
Click to expand...
Click to collapse
I have Verizon service so would I have any issues with US998 in terms of MMS or Voicemails or anything? I figured I'd be assured of no MMS issues (which I thought I read could occur with Verizon on US998) by going with a VS996 rooted ROM. Plus the VS996 ROM comes with the Verizon Voicemail app and maybe the US998 ROM's Voicemail app isn't compatible? The one thing I know I'd lose with US998 and Verizon is WiFi Calling... Believe that has to be done with the VS996 ROM, right?
I'm not sure I care that much about fastboot now that I have 2 TWRP partitions on my phone, so maybe I just stick with VS996 on Verizon.
drewcu said:
I have Verizon service so would I have any issues with US998 in terms of MMS or Voicemails or anything? I figured I'd be assured of no MMS issues (which I thought I read could occur with Verizon on US998) by going with a VS996 rooted ROM. Plus the VS996 ROM comes with the Verizon Voicemail app and maybe the US998 ROM's Voicemail app isn't compatible? The one thing I know I'd lose with US998 and Verizon is WiFi Calling... Believe that has to be done with the VS996 ROM, right?
I'm not sure I care that much about fastboot now that I have 2 TWRP partitions on my phone, so maybe I just stick with VS996 on Verizon.
Click to expand...
Click to collapse
It would just be temporary to see if you can get download mode back.
Then you can go back to Verizon TWRP-flashable zip.
Sent via open market LG US998 V30/V30+