Related
So, I want to preface this by saying I've been searching on this forum for the past day and repeatedly tried several suggestions, but I could have always missed a few posts.
I was running the 30c that was posted here, so previously had TWRP and root, but something happened to my phone and I had to basically wipe it, but I ended up losing the OS (most likely my own fault). No matter what I tried, it would always reboot into recovery, so I read that flashing with the kdz would bring it back, which it did! I flashed the 20j KDZ and I was happy to get my phone working again. Except now, I couldn't root. Every time I did fastboot flash or boot, it would say ERROR (remote: command unknown). After scouring as much as I could, I've come to the conclusion that upgrading to Nougat basically patched and removed several fastboot commands, meaning even if I flash to any other ARBv2 version, I'm out of luck.
Are my findings correct or am I missing something here?
To any and all who respond to my post, thank you.
DoNutsDC said:
So, I want to preface this by saying I've been searching on this forum for the past day and repeatedly tried several suggestions, but I could have always missed a few posts.
I was running the 30c that was posted here, so previously had TWRP and root, but something happened to my phone and I had to basically wipe it, but I ended up losing the OS (most likely my own fault). No matter what I tried, it would always reboot into recovery, so I read that flashing with the kdz would bring it back, which it did! I flashed the 20j KDZ and I was happy to get my phone working again. Except now, I couldn't root. Every time I did fastboot flash or boot, it would say ERROR (remote: command unknown). After scouring as much as I could, I've come to the conclusion that upgrading to Nougat basically patched and removed several fastboot commands, meaning even if I flash to any other ARBv2 version, I'm out of luck.
Are my findings correct or am I missing something here?
To any and all who respond to my post, thank you.
Click to expand...
Click to collapse
If you flashed Nougat unmodified .kdz then root is not available as you have lost the necessary commands. I was on an H901 v10 (T-Mobile) and took the OTA upgrade to Nougat and was not able to get root for the same reason.
Sent from my VS995 using Tapatalk
Stransky said:
If you flashed Nougat unmodified .kdz then root is not available as you have lost the necessary commands. I was on an H901 v10 (T-Mobile) and took the OTA upgrade to Nougat and was not able to get root for the same reason.
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Hey Stransky, thanks for replying.
No, I was on the modified Nougat that was posted here (everything was pretty much stock except for recovery) but eventually reflashed stock 20J .kdz as I remember that was rootable. I can still get into fastboot and whatnot, just can't flash or boot into TWRP from it.
DoNutsDC said:
Hey Stransky, thanks for replying.
No, I was on the modified Nougat that was posted here (everything was pretty much stock except for recovery) but eventually reflashed stock 20J .kdz as I remember that was rootable. I can still get into fastboot and whatnot, just can't flash or boot into TWRP from it.
Click to expand...
Click to collapse
Have you tried booting into TWRP holding the volume down button and pressing the power button and releasing it when the LG screen appears and then quickly pressing it again and follow the instructions to reset which will then take you into TWRP if it is still there.
Sent from my VS995 using Tapatalk
Stransky said:
Have you tried booting into TWRP holding the volume down button and pressing the power button and releasing it when the LG screen appears and then quickly pressing it again and follow the instructions to reset which will then take you into TWRP if it is still there.
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Yep, get the stock erase recovery
https://developers.google.com/android/ota
Ota is live too...
Where I found the changelog?
Thanks
shark147 said:
Where I found the changelog?
Thanks
Click to expand...
Click to collapse
Same place as always: https://source.android.com/security/bulletin/pixel/2019-05-01.html
There doesn't seem to be much though:
This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices.
Click to expand...
Click to collapse
No issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
sliding_billy said:
No issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Could you give me some more details on what you did to install Magisk? For the first time with my P3 I cannot get anything to work. I flashed the May update minus -w, but every method of installing Magisk 19.1 that I've tried ends up with a bootloop.
CSX321 said:
Could you give me some more details on what you did to install Magisk? For the first time with my P3 I cannot get anything to work. I flashed the May update minus -w, but every method of installing Magisk 19.1 that I've tried ends up with a bootloop.
Click to expand...
Click to collapse
1) flash-all (minus -w). Phone reboots to system automatically.
2) shut down and boot to BL
3) fastboot boot twrp-3.3.0-0-blueline.img (be sure to have a copy of the .img file on your phone)
4) install twrp using Advanced > Install Recovery Ramdisk > twrp-3.3.0-0-blueline.img
5) boot to system
6) shut down and boot to BL>recovery (TWRP loads)
7) install Magisk-v19.1 (I did already have 19.1 installed on this phone via Magisk Manager update/Magisk update from before the May image came out in case it matters, so if necessary install 18.1 and then update to 19.1 with Magisk Manager)
8) reboot to system
9) confirm root and install kernel (for me that was ElementalX automated install using EX Kernel Manager app but installing the kernel by going back to TWRP and flashing should do the same)
The two things I might be doing different than others are not using ADB to get back to BL or recovery (I always use the key combo) and booting to system before next step (I don't stack my TWRP/Magisk/kernel installs). Hope this helps.
Whew! Back in business. Thanks!
CSX321 said:
Whew! Back in business. Thanks!
Click to expand...
Click to collapse
That's cool. Which part was the culprit?
sliding_billy said:
That's cool. Which part was the culprit?
Click to expand...
Click to collapse
Well, I don't really know. I initially did what I always do: extract the new boot.img from the update, patch it with MM, run flash-all without -w, let the update finish, reboot and flash the patched boot to boot_a and boot_b. That bootlooped. I flashed stock boot.img and ran like that for a day. Next I booted (but didn't install) TWRP, and tried to install 19.1 (bootloop), and 18.1 (wouldn't install). I decided to try to downgrade to the April update and did flash-all from there (without -w). Big mistake, because then it stuck on the G screen and wouldn't boot at all. I ultimately was able to flash back to the May update, get it to boot, then followed your directions. I did have to install 18.1 first, because even after following your directions, 19.1 still bootlooped when installed from TWRP. MM was able to update to it fine, though, from 18.1. Who knows what the problem really was.
CSX321 said:
Well, I don't really know. I initially did what I always do: extract the new boot.img from the update, patch it with MM, run flash-all without -w, let the update finish, reboot and flash the patched boot to boot_a and boot_b. That bootlooped. I flashed stock boot.img and ran like that for a day. Next I booted (but didn't install) TWRP, and tried to install 19.1 (bootloop), and 18.1 (wouldn't install). I decided to try to downgrade to the April update and did flash-all from there (without -w). Big mistake, because then it stuck on the G screen and wouldn't boot at all. I ultimately was able to flash back to the May update, get it to boot, then followed your directions. I did have to install 18.1 first, because even after following your directions, 19.1 still bootlooped when installed from TWRP. MM was able to update to it fine, though, from 18.1. Who knows what the problem really was.
Click to expand...
Click to collapse
I'd just be spit balling at this point like you are, but at least you are up and running. I do think there is possibly something going on with Magisk going from 18.1 to 19.1 without Manager doing the back end work (even if it happened previously) since Magisk still does retain some data even if root is lost during the upgrade. There are certainly some changes that occured between 18.1 and 19.0 beta since coming from 18.1 you would need to redo your Magisk hide check marks. Either that or using MM to patch boot may have completely changed.
sliding_billy said:
There are certainly some changes that occured between 18.1 and 19.0 beta
Click to expand...
Click to collapse
I probably just had something in some weird state, because I ran 18.1, 19.something beta, 19.something canary, then back to 19.1 stable when it came out. I forgot, I also ran the uninstaller at some point in my previous attempts.
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Same question
djboydva1 said:
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Click to expand...
Click to collapse
I was coming to ask the same question, only I am in WA and have T-mobile. Stock, not rooted. Not had an issue before.
Same here. New P3 during April, so awaiting first security update for my new device. Carrier is AT&T, but why would that matter, right? Just seems strange having to wait. I got the impression that monthly updates for Pixels would come out the same day they were announced as being available. Live and learn I guess.
Finally popped this evening (5/16/2019). No clue why the delay.
djboydva1 said:
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Click to expand...
Click to collapse
I have a Pixel 3 on Google Fi and still haven't gotten the update. Contacted support yesterday and they couldn't find anything wrong. They "promised" I'd get it. Always gotten them within a day or two before.
I guess I just never looked into this before since I'm a new Pixel user or I'm just naive but I assumed when I got a Pixel phones updates would not have to be pushed through my carrier anymore? No May update here on my stock Pixel 3 on T-Mobile.
Always get OTA on the day of release, stock phone, T-Mobile, the Netherlands.
(Pixel didn't launch in the Netherlands, I got it from Germany)
Just installed the may update OTA.
Anyone else having issues with apps accessing the gallery. Both WhatsApp and stock messenger now taking ages to display the thumbnails of the images and videos in my gallery when I add them to a message.
ok could I get some hints here on how to update?
I have rooted and I have magisk.
So, got my V30 here, Frankensteined H931 to US998, never had basically any issues with it so far. Decided to attempt to install the TWRP flashable US998 30b from John Fawkes and that's when all hell broke loose. But I won't get into all that, here's the primary issue now:
I get Download Mode when I power the V30 off and hold Volume Up + insert USB cable (and I've done this with multiple USB cables as well as multiple USB ports), but I never get a connection to the computer anymore in that mode. Nothing, no connects at all, no sounds to indicate a connection, while the V30 shows it's in Download Mode and is waiting for a connection.
If I power it off back to TWRP (3.2.3.7, just flashed earlier as instructed because of the Pie attempt), I get all the proper connections, sounds, etc, can copy files over to the internal as well as external storage, no issues.
Normally when most people say they can't get into Download Mode it's some issue where the device won't power on into that mode when the USB cable is attached - that's not the case here as stated: it powers on and says Download Mode and waiting for a connection, but regardless of any USB cable or port there's never a connection.
I'm suspecting it's a software issue since obviously on a reboot into TWRP the USB port works exactly as expected.
Any suggestions? Because of this I'm unable to do a clean proper US998 20h KDZ flash or the 30b KDZ flash either so thankfully I did have a backup of my previous 20h Oreo install. Of course, because it's all pooched now that is effectively useless because of course of the encryption and upon restoring the backup it won't boot because of the password crap and forces me to format DATA and start all over again.
/me hates encryption when this BS happens, seriously...
So, any tips or tricks that might get me back to a working connection with Download Mode? Flashing a particular partition or something? I'm basically about to redo it with a clean 20h TWRP flashable here in a bit, not left with many other options now.
Anything is appreciated, thanks...
1) Try flashing US998 20e TWRP-FLASHABLE zip. See if that gets you download mode back.
If not, then
2) Try different LGUP.
______
After you get Download mode back, try these steps. Helpful people been testing this out...
For users with TWRP who get stuck on LG logo.
* Flash Verizon VS996 Nougat Partition DL -- EXCEPT for Recovery partitions, to keep TWRP. Do NOT choose all partitions!
You will probably lose download mode, but you've prepped your phone, corrected any partitions. (This is not just for Verizon users, this is for all North American variants -- except for T-Mobile H932.)
* Flash US99820e TWRP flashable zip to get back Download mode.
* Then REFURBISH to US998 20h KDZ.
* Now flash TWRP recovery again and then flash John's zip US99830b.
"Phone booted immediately on pie and everything is working great."
---------- Post added at 01:01 AM ---------- Previous post was at 12:58 AM ----------
rmgibbs1861 said:
ATT 931 on US998. Hangs on the LG Logo for PIE. Will there. be another release for US998 Pie? I do miss Anxious!
Click to expand...
Click to collapse
See Instructions above. Going to write something up in the US998 thread.
Yah, the 20e thing got download mode working normally meaning when the device went into that mode I'd get the traditional notification from Windows that a USB device was now attached - that's what was missing previously for whatever reason.
So I flashed 20h clean with the dev patched LGUP, no issues with Partition DL because I wanted it truly clean without anything that shouldn't be there, and that meant the factory recovery partition as well.
Then I attempted to flash the 30b KDZ, no joy, just stuck at the LG logo and I've wasted enough time on this now so, I'll just wait till some other point and maybe give it a shot in the near future.
Kinda sucks starting over totally clean but hey, this phone has worked near-perfectly since I got it in May so it'll be fine with a clean fresh start. I'm not even going to install Magisk this time, I can't think of a single reason I even need root anymore but if I do I'll worry about that a later time.
br0adband said:
Yah, the 20e thing got download mode working normally meaning when the device went into that mode I'd get the traditional notification from Windows that a USB device was now attached - that's what was missing previously for whatever reason.
So I flashed 20h clean with the dev patched LGUP, no issues with Partition DL because I wanted it truly clean without anything that shouldn't be there, and that meant the factory recovery partition as well.
Then I attempted to flash the 30b KDZ, no joy, just stuck at the LG logo and I've wasted enough time on this now so, I'll just wait till some other point and maybe give it a shot in the near future.
Kinda sucks starting over totally clean but hey, this phone has worked near-perfectly since I got it in May so it'll be fine with a clean fresh start. I'm not even going to install Magisk this time, I can't think of a single reason I even need root anymore but if I do I'll worry about that a later time.
Click to expand...
Click to collapse
You need to do the VS996 Nougat Partition DL step. It preps the phone.
This is what you need to do:
I have all the steps above. The first 20e flash was just to get Download mode back.
ChazzMatt said:
After you get Download mode back, try these steps. Helpful people been testing this out...
For users with TWRP who get stuck on LG logo.
* Flash Verizon VS996 Nougat Partition DL -- EXCEPT for Recovery partitions, to keep TWRP. Do NOT choose all partitions!
You will probably lose download mode, but you've prepped your phone, corrected any partitions. (This is not just for Verizon users, this is for all North American variants -- except for T-Mobile H932.)
* Flash US99820e TWRP flashable zip to get back Download mode.
* Then REFURBISH to US998 20h KDZ.
* Now flash TWRP recovery again and then flash John's zip US99830b.
"Phone booted immediately on pie and everything is working great."
Click to expand...
Click to collapse
Let me start firstly by saying, thank you ChazzMatt! V30 owners around the globe are incredibly fortunate to have your dedicated write-ups and support for these terrific phones. FWIW, I'm seriously impressed with the level of knowledge and your willingness to deep dive issues with folks... thanks again!
Getting to the topic however; I have the identical issue occurring with my LS998U (V30+) that I just went through the unlock process with yesterday. This morning I TWRP flashed the VS99630c ROM and everything worked A-OK except download mode. Exact same symptoms as br0adband is describing - phone appears to enter download mode as normal (though the initial "LG V30 ThinQ" boot screen appears to have replaced the bootloader warning screen?) but is not initiating the USB port for a connection at all.
Connections are established and work normally in TWRP and when booted into the OS so there appears to be something fundamentally wrong with Pie or the flash method.
I'm 99% confident it's not a PC side issue as there isn't even a connection for LGUP or drivers to fault out on.. I also tried my other US998 phone which is on dotOS and everything worked normally.
I'm about to try the TWRP flashable 20e per ChazzMatt's suggestion and will report back if I have success (or not).
Windza said:
Let me start firstly by saying, thank you ChazzMatt! V30 owners around the globe are incredibly fortunate to have your dedicated write-ups and support for these terrific phones. FWIW, I'm seriously impressed with the level of knowledge and your willingness to deep dive issues with folks... thanks again!
Click to expand...
Click to collapse
You're welcome!
Windza said:
This morning I TWRP flashed the VS99630c ROM and everything worked A-OK except download mode. Exact same symptoms as br0adband is describing - phone appears to enter download mode as normal (though the initial "LG V30 ThinQ" boot screen appears to have replaced the bootloader warning screen?) bu
I'm about to try the TWRP flashable 20e per ChazzMatt's suggestion and will report back if I have success (or not).
Click to expand...
Click to collapse
VS996 firmware doesn't have bootloader unlocked warning. Verizon never thought it would ever be unlocked.
While flashing 20e should give you download mode back, to me or seems both of you are sort of missing the point of the preliminary VS996 Nougat Partition DL flash (while omitting the Recovery partitions to keep TWRP)
Maybe in your case you don't need it -- since you made it to the other side of Pie, but that Nougat flash fixes any Partition problems. Just be sure to keep TWRP during that.
You may temporarily lose download mode again
Then TWRP-flashable zip US998 20e fix that.
Then REFURBISH to US998 20h. You'll temporarily lose TWRP at that point.
Re-Install TWRP and the three root files.
Then flash US998 30b TWRP-flashable zip.
ChazzMatt said:
While flashing 20e should give you download mode back, to me or seems both of you are sort of missing the point of the preliminary VS996 Nougat Partition DL flash (while omitting the Recovery partitions to keep TWRP)
Click to expand...
Click to collapse
While my "missing the point" is entirely possible ChazzMatt, I was under the impression that I was already AT the preliminary Nougat step after having just stepped through the Frankenstein and unlock methods?
My progression through those steps was simply;
Frankenstein per your post here; https://forum.xda-developers.com/lg...ssflashing-t3780969/post76510671#post76510671
Unlock the bootloader, install TWRP et. al. per your directions here ;https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193
Upon completing these steps, Nougat is already installed at which point I figured I was ready to flash VS99630c. What am I missing here... should I have reflashed Nougat?
I didn't have any issues like others are reporting with the upgrade to 30c (TWRP flashed it flawlessly and it booted right up).
It wasn't until I decided I'm not ready for Verizon Pie (tastes gross) and went to step back to US99820h that I realised Download Mode was broken.
Is all of this not just a case of Download Mode being broken in 30c for everyone?
ChazzMatt said:
Then TWRP-flashable zip US998 20e fix that.
.
Click to expand...
Click to collapse
Yup - just as you said. 20e restored Download Mode.
ChazzMatt said:
Then flash US998 30b TWRP-flashable zip.
Click to expand...
Click to collapse
Does Download Mode work for anyone after this step or is TWRP back to a 20 series ROM the only way back to a working LGUP?
Sorry if I'm only confusing things more but I figure I'm not the only one tripping up on this... once I understand it better, I promise I'll step in and help educate other folk
It really is true about ChazzMatt's willingness to help around here.
What I never could understand is why some users, after receiving help AND successfully using it to fix their phones, don't even bother saying thank you. I'll happily spend my daily Thanks quota on helpful posts, even if they have no relevance for me at all. And I see Chazz do the same, every day. Others too, of course. But it seems some people feel being thankful is beneath them. Or something... I just don't understand it.
</rant>
Windza said:
While my "missing the point" is entirely possible ChazzMatt, I was under the impression that I was already AT the preliminary Nougat step after having just stepped through the Frankenstein and unlock methods?
My progression through those steps was simply;
Frankenstein per your post here; https://forum.xda-developers.com/lg...ssflashing-t3780969/post76510671#post76510671
Unlock the bootloader, install TWRP et. al. per your directions here ;https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193
Upon completing these steps, Nougat is already installed at which point I figured I was ready to flash VS99630c. What am I missing here... should I have reflashed Nougat?
I didn't have any issues like others are reporting with the upgrade to 30c (TWRP flashed it flawlessly and it booted right up).
It wasn't until I decided I'm not ready for Verizon Pie (tastes gross) and went to step back to US99820h that I realised Download Mode was broken.
Is all of this not just a case of Download Mode being broken in 30c for everyone?
Click to expand...
Click to collapse
No, download mode isn't broken for everyone. Most people flash to Pie with no issues and download mode still works. It's when reverting to US998 Download mode seems to go away for a number of poeple (not sure how many and may depend on the LGUP used)
_______
OK, if all you wanted was for Download mode to be restored and you had no problems getting to Pie before that, then ignore what I said.
I thought you were trying to get to Pie and couldn't. In that case the workaround involves flashing Verizon VS996 Nougat -- NOT US998 Nougat like in Frankenstein -- via Partition DL mode except for Recovery partitions. That's a necessary prep stage for Pie. Both people in this thread weren't doing that. OK, so you had good reason. :silly:
THEN going to US998 20e via TWRP flashable zip, which restores Download mode. But if the goal was to get to Pie (yours wasn't) flashing 20e to get Download mode was also step zero. It was also necessary to restore Download mode so you could then flash VS996 Nougat via Partition DL mode (except for Recovery), to then flash back US998 20e TWRP flashable zip AGAIN, to then REFURBISH to US998 20h.
The VS996 Nougat part is important for those people hitting the LG logo wall.
ChazzMatt said:
No, download mode isn't broken for everyone. Most people flash to Pie with no issues and download mode still works. It's when reverting to US998 Download mode seems to go away for a number of poeple (not sure how many and may depend on the LGUP used)
Click to expand...
Click to collapse
This is good news... thanks for confirming!
I've likely done a few hundred ROM flashes and plenty of roots/unlocks in the past 15-20yrs and this was the first time I had a genuine "Oh crap" moment where a low level mode like Download Mode truly failed.
I was also having trouble getting back into TWRP (Noxx PM refused to work on 30c) which fostered a rapidly growing concern that without TWRP and Download Mode, I was effectively bricked (or at least in for a few hours of work to find a resolution).
I breathed a sigh of relief when attempting a Master Reset led me back to TWRP... I still had options!
Anyhow, it's probably fitting for me to exit this thread on the same subject I entered on by saying thank you again for the information share and willingness to help out :good:
Cheers!
ChazzMatt said:
No, download mode isn't broken for everyone. Most people flash to Pie with no issues and download mode still works. It's when reverting to US998 Download mode seems to go away for a number of poeple (not sure how many and may depend on the LGUP used)
_______
OK, if all you wanted was for Download mode to be restored and you had no problems getting to Pie before that, then ignore what I said.
I thought you were trying to get to Pie and couldn't. In that case the workaround involves flashing Verizon VS996 Nougat -- NOT US998 Nougat like in Frankenstein -- via Partition DL mode except for Recovery partitions. That's a necessary prep stage for Pie. Both people in this thread weren't doing that. OK, so you had good reason. :silly:
THEN going to US998 20e via TWRP flashable zip, which restores Download mode. But if the goal was to get to Pie (yours wasn't) flashing 20e to get Download mode was also step zero. It was also necessary to restore Download mode so you could then flash VS996 Nougat via Partition DL mode (except for Recovery), to then flash back US998 20e TWRP flashable zip AGAIN, to then REFURBISH to US998 20h.
The VS996 Nougat part is important for those people hitting the LG logo wall.
Click to expand...
Click to collapse
I lost download mode and TWRP for some reason and all I have is system recovery and nothing works in it for me . Is there anything I can do now? All I see is MTP android device.
KDZ 99820a
Hello i wanna thank all of you guys for the amazing support on this device, he LG v30 is an amazing phone just bought a US99830B , downgraded it with LGUP to oreo, unlocked bootloader in oreo and installed TWRP downloaded 99830B flasheable zip and flashed it , then i waned to try lineage 17 and flashed it in TWRP clean install booted up in android 10 but noticed lots of bugs and no WIFI, flashed modem for oreo in TWRP wifi came back up but wanted to go back to PIE restored from a backup that performed for PIE and got botloop maybe because of the incompatible modem, tried download mode, no USB activity back to TWRP restored lineage OS and im back in the system, i took your advice to flash 99820b in TWRP my download mode is back and im on oreo, my question is if i KDZ 99830B from 99820b will download mode still work even tho it doesn't when i flash stock 99830b download mode gets lost, i dont want to flash the KDZ and end up with no download mode and no TWRP and have a hard brick
Update : I have KDZ 99820a using LGUP and locked bootloader I'm back to stock is there any issues if I update to the 99830b which is the original software that the phone came with? Can I perform that update via KDZ?
SOU55 said:
Hello i wanna thank all of you guys for the amazing support on this device, he LG v30 is an amazing phone just bought a US99830B , downgraded it with LGUP to oreo, unlocked bootloader in oreo and installed TWRP downloaded 99830B flasheable zip and flashed it , then i waned to try lineage 17 and flashed it in TWRP clean install booted up in android 10 but noticed lots of bugs and no WIFI, flashed modem for oreo in TWRP wifi came back up but wanted to go back to PIE restored from a backup that performed for PIE and got botloop maybe because of the incompatible modem, tried download mode, no USB activity back to TWRP restored lineage OS and im back in the system, i took your advice to flash 99820b in TWRP my download mode is back and im on oreo, my question is if i KDZ 99830B from 99820b will download mode still work even tho it doesn't when i flash stock 99830b download mode gets lost, i dont want to flash the KDZ and end up with no download mode and no TWRP and have a hard brick
Update : I have KDZ 99820a using LGUP and locked bootloader I'm back to stock is there any issues if I update to the 99830b which is the original software that the phone came with? Can I perform that update via KDZ?
Click to expand...
Click to collapse
Losing your download mode has nothing to do with stock.
Why did you lock your bootloader back? You can run stock rooted firmware just fine and have lots of advantages like DTS surround sound stereo.
I don't understand why people lock the bootloader back just because they decide they don't want custom ROMs. The best thing to do is run rooted stock firmware, have everything you want.
ChazzMatt said:
Losing your download nose has nothing to do with stock.
Why did you lock your bootloader back? You can run stock rooted firmware just fine and have lots of advantages like DTS surround sound stereo.
I don't understand why people lock the bootloader back just because they hate custom ROMs. The best thing to do is run rooted stock firmware, have everything you want.
Click to expand...
Click to collapse
Don't get me wrong i like having rooted devices because of the endless possibilities it offers but this time mayor newer games that are coming out they have the ability to detect if you are rooted or if your bootloader has been unlocked and they kick you out of their servers, that's the main reason why i want to go full stock, and I was so afraid to do so because some people are reporting when moving from oreo to pie it creates bootloop and since I had issues when I was rooted and flashed via twrp 99830.zip download mode won't detect the USB cable only when I rolled back with LGUP to oreo downloadode started working and I KDZ oreo to have official recovery and relocked bootloader but I want pie is just I am not sure if I can go up with LGUP to pie using 99830b (which my phone originally came with pie) from 99820b
Could you please help me with the same problem with download mode on h932? I'm on stock pie now. I want to downgrade to nought but my PC not recognize phone in download mode. Thank you.
Or_dos said:
Could you please help me with the same problem with download mode on h932? I'm on stock pie now. I want to downgrade to nought but my PC not recognize phone in download mode. Thank you.
Click to expand...
Click to collapse
First try a different USB port, different cable and/or different computer. If you never rooted the phone, there is very little chance that your actual Download Mode got corrupted, and one of the above will most likely solve it (although many doubt it because it sounds too trivial).
Also, make sure you're using the latest Dual Mode Dev patched LGUP from one of ChazzMatt's ROM threads.
Next I would try the Update Recovery mode in LG Bridge (on the Update tab).
Finally, if none of those work, you can try force installing the Pie OTA using LGUP FOTA mode (doesn't require Download Mode). It's described in the thread linked below. Best to read the whole thread for context, it's just a few pages.
[H932][T-MOBILE] URL for the H932 Pie OTA file
https://forum.xda-developers.com/lg-v30/help/h932-url-h932-pie-ota-file-t3991417
Hopefully one of those will work for you. Please report your results, regardless of outcome.
Good luck to you :fingers-crossed:
TheDannemand said:
First try a different USB port, different cable and/or different computer. If you never rooted the phone, there is very little chance that your actual Download Mode got corrupted, and one of the above will most likely solve it (although many doubt it because it sounds too trivial).
Also, make sure you're using the latest Dual Mode Dev patched LGUP from one of ChazzMatt's ROM threads.
Next I would try the Update Recovery mode in LG Bridge (on the Update tab).
Finally, if none of those work, you can try force installing the Pie OTA using LGUP FOTA mode (doesn't require Download Mode). It's described in the thread linked below. Best to read the whole thread for context, it's just a few pages.
[H932][T-MOBILE] URL for the H932 Pie OTA file
https://forum.xda-developers.com/lg-v30/help/h932-url-h932-pie-ota-file-t3991417
Hopefully one of those will work for you. Please report your results, regardless of outcome.
Good luck to you :fingers-crossed:
Click to expand...
Click to collapse
I tried all things with cabels, PCs and drivers, i'm not sure but as i know LG phone in download mode should be recognized as anything, but in my case i have no any devices in the device manager. I didn't root this phone but i bought it with unlocked bootloader so it is possible that it was rooted. I tried lock bootloader but it didn't helps so i unlocked it again. Now i'm going to try to flash OTA file. Thank you so much for help.
Or_dos said:
I tried all things with cabels, PCs and drivers, i'm not sure but as i know LG phone in download mode should be recognized as anything, but in my case i have no any devices in the device manager. I didn't root this phone but i bought it with unlocked bootloader so it is possible that it was rooted. I tried lock bootloader but it didn't helps so i unlocked it again. Now i'm going to try to flash OTA file. Thank you so much for help.
Click to expand...
Click to collapse
Does Download Mode start on the phone?
Just to make sure: From Power off, press and hold VolUp while plugging in the cable. Then load LGUP. Again make sure you're using the Pie compatible LGUP from one of ChazzMatt's ROM threads.
Otherwise I'd try LG Bridge next.
As for force installing the Pie update with LGUP FOTA (the thread I linked) we've only had one confirmed case of it fixing Download Mode so far, although not many tried it yet. On Oreo we had many users confirming it, but Pie is different.
I should add that if you have working Pie, but just would like to roll back, there is a risk that the FOTA will mess up what you have. So if it doesn't fix your Download Mode, you could be worse of. Just a heads-up
TheDannemand said:
Does Download Mode start on the phone?
Just to make sure: From Power off, press and hold VolUp while plugging in the cable. Then load LGUP. Again make sure you're using the Pie compatible LGUP from one of ChazzMatt's ROM threads.
Otherwise I'd try LG Bridge next.
As for force installing the Pie update with LGUP FOTA (the thread I linked) we've only had one confirmed case of it fixing Download Mode so far, although not many tried it yet. On Oreo we had many users confirming it, but Pie is different.
I should add that if you have working Pie, but just would like to roll back, there is a risk that the FOTA will mess up what you have. So if it doesn't fix your Download Mode, you could be worse of. Just a heads-up
Click to expand...
Click to collapse
Actually the main problem is that phone doesn't recognize by PC when download mode is on the screen. I have tried to use lg bridge to recover, but anyway it reboots my phone and then my phone doesn't recognize. Now i'm trying to solve lg up error with FOTA update, it looks like wrong dll file. I'll keep you up to date.
Thank you!
Or_dos said:
Actually the main problem is that phone doesn't recognize by PC when download mode is on the screen. I have tried to use lg bridge to recover, but anyway it reboots my phone and then my phone doesn't recognize. Now i'm trying to solve lg up error with FOTA update, it looks like wrong dll file. I'll keep you up to date.
Thank you!
Click to expand...
Click to collapse
Got it! Thank you for the update.
Completely uninstall LGUP and remove all folders of it. Then install the Dual Mode LGUP from ChazzMatt's H932 ROM thread linked below, using his exact installation steps. That's important: LGUP isn't just LGUP!
[H932][STOCK][PIE]LG V30 U.S. T-Mobile H932 H93230d_00_0902.KDZ
https://forum.xda-developers.com/lg-v30/development/h932-lg-v30-s-t-mobile-h932-t3952258
I have a rooted/unlocked Verizon V30 and tried to install the Havoc OS rom on my phone. For some reason, it will not download the updates upon initial boot. It does not bootloop, it just looks like it is working on finding these updates and they never show. I wanted to access TWRP and for whatever reason I can't figure out, it will not boot into it. So without getting into android and the settings to enable usb debugging I am seriously confused on what to do next. I have also tried to do factory reset, but after hitting yes 2x, it only brings me to the same question and will not progress unless I hard reset.
If I could get usb debugging on and then push TWRP I could either flash back to what I was using or try and reinstall...
Any assistance is greatly appreciated! Thank you!
Bobert3332 said:
I have a rooted/unlocked Verizon V30 and tried to install the Havoc OS rom on my phone. For some reason it will not download the updates upon initial boot. It does not bootloop, it just looks like it is working on finding these updates and they never show.
Click to expand...
Click to collapse
I almost have no idea what you're talking about. What updates? You mean you're trying to download the Havoc ROM? Or you have it installed and you're trying to do something else?
Bobert3332 said:
I wanted to access TWRP and for whatever reason I can't figure out, it will not boot into it. So without getting into android and the settings to enable usb debugging I am seriously confused on what to do next. I have also tried to do factory reset, but after hitting yes 2x, it only brings me to the same question and will not progress unless I hard reset.
If I could get usb debugging on and then push TWRP I could either flash back to what I was using or try and reinstall...
Any assistance is greatly appreciated! Thank you!
Click to expand...
Click to collapse
What firmware are you on right now? VS996 you flashed with TWRP flashable zip? US998 20h? Havoc ROM?
If you are still on rooted stock firmware, the best way to access TWRP is what the WTF instructions recommend. Why are you trying to do it differently?
End of Section 6. Hint: it says STRONG SUGGESTION.
___
If you've done something strange and need to re-install TWRP for some reason, go see the WTF instructions again...
If by "USB debugging" you mean fastboot flash commands (because I don't understand what you are saying), Verizon firmware doesn't have fastboot flash commands. Of the North American variants, only US998 has fastboot flash commands. That's why in WTF INSTRUCTIONS you had to temporarily Frankenstein to US998 to unlock the bootloader and install TWRP.
But you should still have had TWRP unless you've done something wierd. However you've factory reset it seems.
ChazzMatt said:
I almost have no idea what you're talking about. What updates? You mean you're trying to download the Havoc ROM? Or you have it installed and you're trying to do something else?
What firmware are you on right now? VS996 you flashed with TWRP flashable zip? US998 20h? Havoc ROM?
If you are still on rooted stock firmware, the best way to access TWRP is what the WTF instructions recommend. Why are you trying to do it differently?
End of Section 6. Hint: it says STRONG SUGGESTION.
___
If you've done something strange and need to re-install TWRP for some reason, go see the WTF instructions again...
If by "USB debugging" you mean fastboot flash commands (because I don't understand what you are saying), Verizon firmware doesn't have fastboot flash commands. Of the North American variants, only US998 has fastboot flash commands. That's why in WTF INSTRUCTIONS you had to temporarily Frankenstein to US998 to unlock the bootloader and install TWRP.
But you should still have had TWRP unless you've done something wierd. However you've factory reset it seems.
Click to expand...
Click to collapse
The update is the initial boot screen on Havoc, as in when you boot android for the first time and it has you select your language. That part. Then it says it is updating, and does that indefinitely. If I could do step 6 I would, but as the title says, I cant enable usb debugging because i cant access settings. This is where I am stuck. I can no longer get into any settings besides those that come on havoc are rom specific. Does this help clarify? Sorry for the confusion. I followed the WTF as best as I could, and I believe I installed TWRP per the instructions but I cannot get back to it to save my life.
Bobert3332 said:
The update is the initial boot screen on Havoc, as in when you boot android for the first time and it has you select your language. That part. Then it says it is updating, and does that indefinitely.
If I could do step 6 I would, but as the title says, I cant enable usb debugging because i cant access settings. This is where I am stuck. I can no longer get into any settings besides those that come on havoc are rom specific. Does this help clarify? Sorry for the confusion. I followed the WTF as best as I could, and I believe I installed TWRP per the instructions but I cannot get back to it to save my life.
Click to expand...
Click to collapse
OK, so you actually installed the Havoc ROM. I thought you were possibly on stock firmware still -- either VS996 (from TWRP flashable zip) or US998. You basically have a ROM problem, so you should also post in the Havoc ROM thread.
To install Havoc ROM -- which to my knowledge is still based on LOS-16 -- you needed to be coming from Oreo blobs, meaning Oreo stock firmware or similar LOS-16 ROMs based on Oreo blobs.
You can't install LOS-16 firmware from stock Pie or LOS-17 ROMs (which are Pie blobs).
If you were EVER on stock Pie -- just to see what it was like -- you not only have to downgrade back to Oreo to run LOS-16 ROMs but you also have to run permissive kernel from now and sometimes you need to flash permissive zip to even boot:
tech_infinity said:
If the ROM doesn't boot for you then try using permissive SElinux. Use zip from here: https://zackptg5.com/android.php
Click to expand...
Click to collapse
@tech_infinity is the expert on ROMs. Maybe he can help you more.
______
What I was referring to is on stock firmware I recommend a couple of apps that will let you boot to TWRP, as long as you give them root privileges.
You can also reboot to TWRP from the Magisk Manager app, but that reboot to recovery choice is deep in the options menu. Open up Magisk Manager, look in the menu for Modules, then click on that three dots menu...
Another option is the Reboot Recovery app. Make a shortcut button on the desktop. Click on it, it says are you sure, and it boots to Recovery.
Bobert3332 said:
The update is the initial boot screen on Havoc, as in when you boot android for the first time and it has you select your language. That part. Then it says it is updating, and does that indefinitely. If I could do step 6 I would, but as the title says, I cant enable usb debugging because i cant access settings. This is where I am stuck. I can no longer get into any settings besides those that come on havoc are rom specific. Does this help clarify? Sorry for the confusion. I followed the WTF as best as I could, and I believe I installed TWRP per the instructions but I cannot get back to it to save my life.
Click to expand...
Click to collapse
Which gapps are using? Before the checking for updates screen appears, ensure you've got good internet connection / if need be take hotspot from someone who has good internet. It gets stuck for a while if you've bad internet.
Edit: One thing you could do is go back and disable internet (both wifi and mobile data) in the initial options. Then press skip all the way. It won't check for updates then. Then sideload apk of the apps @ChazzMatt recommends to reboot into recovery or if you've flashed magisk, goto modules menu, click on right top corner and select reboot to recovery. Maybe try different gapps this time
The OTA Pie update keeps breaking my phone (stuck on Verizon loading screen). The first time, I believe I downloaded VS99620k_02_0510_ARB00.kdz and used LGUP Dual Mode to replace the OS since nothing else worked, not even resets. (I also tried stock Pie and had the same issue as the OTA upgrade.) I kept skipping the update every day until last month, I guess it was accepted accidentally because next thing I knew, I was stuck on the Verizon loading screen again. Haven't wanted to deal with it and have been using my tablet for calls and texts. But I do need a working phone.
This time, I decided to go ahead and follow https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193. I used the Frankenstein instructions to go from VS996 to US998 20a and am now running Oreo and unlocked bootloader, etc. What is the next step? I believe I need to go back to VS because I have Verizon. The current Oreo doesn't function properly (can't make calls, glitches, random reboots). Which Oreo ROM should I download? Or can I use the KDZ I already have? I've found many ROMs and info but I don't want to just guess.
edit: the zip link here doesn't work https://forum.xda-developers.com/lg-v30/development/rom-fw-lg-v30-joan-verizon-vs996-21f-t3865671. john-fawkes.com doesn't load. I guess I'll just do the previous version on AFH?
Also, what can I do to prevent this happening in the future? Verizon update reminded me every day about updating with an annoying popup and I always said to remind me the next day, but I don't want it to get accepted accidentally again. I wish it had an option to say no! Maybe there's something now that I'm rooted?
CheshireKat_ said:
This time, I decided to go ahead and follow https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193. I used the Frankenstein instructions to go from VS996 to US998 20a and am now running Oreo and unlocked bootloader, etc.
What is the next step? I believe I need to go back to VS because I have Verizon. The current Oreo doesn't function properly (can't make calls, glitches, random reboots). Which Oreo ROM should I download? Or can I use the KDZ I already have? I've found many ROMs and info but I don't want to just guess.
edit: the zip link here doesn't work https://forum.xda-developers.com/lg-v30/development/rom-fw-lg-v30-joan-verizon-vs996-21f-t3865671. john-fawkes.com doesn't load. I guess I'll just do the previous version on AFH?
Also, what can I do to prevent this happening in the future? Verizon update reminded me every day about updating with an annoying popup and I always said to remind me the next day, but I don't want it to get accepted accidentally again. I wish it had an option to say no! Maybe there's something now that I'm rooted?
Click to expand...
Click to collapse
Your next step is Section 9 of the WTF Instructions. You got through Section 6 but didn't finish. Section 9 is about updating firmware.
You would choose the Verizon Pie TWRP flashable zip (i.e. stock ROM which can be installed with TWRP). You would re-flash Magisk and can even update to newer version of Magisk. Once on that, you won't get any update reminders.
ChazzMatt said:
Your next step is Section 9 of the WTF Instructions. You got through Section 6 but didn't finish. Section 9 is about updating firmware.
You would choose the Verizon Pie TWRP flashable zip (i.e. stock ROM which can be installed with TWRP). You would re-flash Magisk and can even update to newer version of Magisk. Once on that, you won't get any update reminders.
Click to expand...
Click to collapse
I tried that. As I said in my post, the problem is that the linked zip doesn't work, so I didn't know what to do. I ended up going with a previous version (J instead of K) and got calling, etc. back but still had problems with it randomly restarting. I plugged it into the wall charger to charge and woke up to it not turning on at all, even connected to the computer. It's totally dead. Now what? The cord works with my tablet so it's not the cord.
CheshireKat_ said:
I tried that. As I said in my post, the problem is that the linked zip doesn't work, so I didn't know what to do. I ended up going with a previous version (J instead of K) and got calling, etc. back but still had problems with it randomly restarting. I plugged it into the wall charger to charge and woke up to it not turning on at all, even connected to the computer. It's totally dead. Now what? The cord works with my tablet so it's not the cord.
Click to expand...
Click to collapse
Hmmmm..
The link is wrong. For some reason goes to Oreo 20k. Sorry. Should go to Pie. I'll have to fix it tonight when I get home from work.
Go to Verizon Pie TWRP flashable zip and install that. I know you find it. It's in the Developers section, both in my KDZ thread and standalone John Fawkes thread. Google if you have to.
I have separate threads for VS996 Oreo and Pie KDZ, and they also include TWRP flashable zips.
ChazzMatt said:
Hmmmm..
The link is wrong. For some reason goes to Oreo 20k. Sorry. Should go to Pie. I'll have to fix it tonight when I get home from work.
Go to Verizon Pie TWRP flashable zip and install that. I know you find it. It's in the Developers section, both in my KDZ thread and standalone John Fawkes thread. Google if you have to.
I have separate threads for VS996 Oreo and Pie KDZ, and they also include TWRP flashable zips.
Click to expand...
Click to collapse
Thanks, but since my phone no longer turns on, shows charging, or connects to the computer, I'm not sure what to do. I can't boot into recovery or anything. I'm guessing it's bricked? Wish I knew what had happened overnight to mess it up.
I did Google it and search the forums. For example, here: https://forum.xda-developers.com/lg-v30/development/vs996-lg-v30-verizon-vs996-t3865398 the flashable zip goes to john-fawkes.com, which "can't be reached" (doesn't load). Same with here https://forum.xda-developers.com/lg-v30/development/rom-fw-lg-v30-joan-verizon-vs996-21f-t3865671.
CheshireKat_ said:
I did Google it and search the forums. For example, here: https://forum.xda-developers.com/lg-v30/development/vs996-lg-v30-verizon-vs996-t3865398 the flashable zip goes to john-fawkes.com, which "can't be reached" (doesn't load). Same with here https://forum.xda-developers.com/lg-v30/development/rom-fw-lg-v30-joan-verizon-vs996-21f-t3865671.
Click to expand...
Click to collapse
Both of those are latter Oreo. I don't know why they didn't work for you.
Here are the VS996 Pie (30c) TWRP flashable zips, found using simple forum search:
* LG V30 VS996-30c ROM (John Fawkes)
* [VS996][STOCK][PIE]LG V30 VS99630c_00_0904_ARB00.KDZ
See post #2 of that thread. Has both LG KDZ and John Fawkes TWRP-flashable zip with instructions on how to install, as well as compatible Dev Patched LGUP for Pie, if you need to install KDZ instead of TWRP flashable zip.
* [ROM][VS996] Verizon LG V30 Pie 30c Debloated Rom
Debloated version of 30c by another dev. But you must FIRST be on full 30c (either JohnFawkes TWRP flashable zip or full KDZ) before flashing this via TWRP to then remove stuff.
None of the John Fawkes links worked on my laptop... But one seemed to have worked on my tablet just now....not sure what that's about.
Pie does not work on my phone and is what screws it up, so I do not want it.
Most importantly, as I said before, my phone no longer turns on, charges, or connects to the computer so I cannot upgrade/update Oreo. The links are a moot issue now.
I do not know what happened as it was working and charging when I went to sleep. I just noticed that I think I used my tablet's charger, so maybe the battery was shot during the night?