did you solve your problem? I seem to have the same or similar. but the other advice about using a slower USB got me a little closer. still stuck with no TWRP after 5 hours
Have either of you tried the USB flag batch file that's mentioned in the second post of the thread? I spent many hours dealing with the same thing, and that finally solved it.
I'm back, approaching my wit's end after two hours of dealing with different bootloops.
I don't think it's the ROM (Android 10 Havoc unofficial 3.11), so I'm posting here.
I clean-installed Havoc -> Magisk -> Nanodroid -> Haumea.
Upon the first boot attempt, I got a warning about corrupted storage, and the system booted into OrangeFox, prompting me to format my data.
this was the final solution for me. i was plugged into the usb 2.0 front panel all day so i didn't think much of it. as soon as i plugged it in through an old 2.0 hub into the 3.0 port, it worked. endless hours troubleshooting this one can't believe it was that.
I always follow direction when it comes to rooting and unlocking bootloader, step by step. Now, I have yet to successfully install TWRP, and have proceeded to revert back to nougat, oreo, and now pie.
I've tried using the slower cord as mention, and while that works on the communication between my computer and the v30, it still will not install TWRP. I've tried different versions of it, and still not successful. My phone as mentioned and posted with pictures, bootloader is unlocked. Is there a possible different thread I can look into? I've looked tirelessdly everywhere and tried almost everything. I just used the kdz file for pie after nougat and oreo steps, so im on stock pie as of now, bootloader still unlocked but no twrp. I suppose i'll settle for stock pie lol
I apologize, I'd never noticed that your long step-by-step was not actually the OP of this thread.
Yes, I've never crossed flashed, as my phone is originally from the ATT variant. I'm on US99830b from the kdz. I've clicked on the link you provided and followed everything step by step. I have the slowest cord connected 2.0 and the computer recognizes the phone and communicates well up until the flashing of twrp. Here are some pics I took as I was doing the process. In one of the pictures is where it lingers and doesn't install twrp, so I have to disconnect it because my phone goes to boot screen, ergo i have to unplug and restart the v30 again. That goes with all kdz files from nougat, oreo, and pie.What PIE are you on? US998? One of the H930* variants? You need to be on firmware that has fastboot flash commands. For WTF method, you can only use US998 or one of the H930 variants KDZ. You shouldn't cross flash between Europe/India H930* and US998, but if you have a North America Verizon or AT&T model, you have to use US998 firmware as the VS996 and H931 don't have fastboot flash commands. Nor does the Canada H933.
If you are bootloader unlocked on a Pie firmware with fastboot flash commands, follow these specific instructions. See the attached files on that post. It's a different version of TWRP than in the initial bootloader unlock instructions.
Follow the instructions exactly. Do NOT use a newer version of Magisk, do not skip any steps. You can't sub out ingredients in this recipe.
@ChazzMatt always gets props from me. been helping me since the mexican variant of my moto maxx (damn i miss that phone)
Flashing Samsung's are EASY. Just use the right ODIN app for your model phone.Yeah, Moto Maxx (known as "Droid Turbo" for Verizon, "Moto Turbo" in India) was a GREAT phone. Except for the Verizon variant (XT1254), the XT1225 and XT1250 had free Motorola official bootloader unlock. And the Moto Maxx XT1250 was an clone of the Droid Turbo XT1254 -- same FCC ID. Identical phone sold under different name. With a Verizon SIM card could run like Droid Turbo on Verizon network with all the same LTE/CDMA bands. It was basically the "developer" version of the Droid Turbo. In the U.S., the XT1250 was sold by regional LTE/CDMA carriers who used Verizon for roaming. So, for awhile people bought THAT, unlocked bootloader and ran it on Verizon. Then Sunshine team figured out bootloader unlock for the Verizon XT1254 (Droid Turbo) variant, with a paid solution.
I had three Moto Maxx XT1225, bought from Mexico and Puerto Rico off eBay. They had all the AT&T LTE/HSPA bands and official bootloader unlock. As you know, I wrote the instructions for that, including installing TWRP, rooting, and flashing different boot logos and animations.
This 2017 LG V30 was the first phone since then that I felt was a true successor to the Moto Maxx. It's just the early 2018 LG V30S variant with 6GB RAM, 128GB internal memory was what LG should given the first batch. I have the 128GB V30+, but over the last year I really feel the strain of the 4GB RAM.
AT&T is cutting off HSPA next February but they are aggressively forcing people to upgrade to new phones which can handle AT&T VoLTE. They are sending threatening text messages.
My wife and my mother now both have the LG V35 (yes, 6GB RAM) and will work on AT&T when they cut off HSPA early next year. But it only has 64GB internal storage. I do have microSD card, but I have too many apps, too many email accounts to go with only 64GB storage.
I've bought a mint Samsung Galaxy S10+, but it's been sitting in a box the past couple of weeks. I hate having to learn about Odin and going through all the steps to learn new bootloader unlock and root, install TWRP.
AT&T now says they are shipping me a "new" phone and after 30 days they will auto activate it and my V30 will no longer work on AT&T network. But I've already bought my own replacement phone. I am waiting for their phone to arrive before I switch over to the S10+. I'll give the new phone (probably some cheapo budget model) to my oldest daughter. If I start using the S10+ before then, they may not ship the free phone.
He created a separate thread for Korean variants to help others.
Due to the July 2018 LG security patch blocking the WTF bootloader unlock exploit, I've added instructions in post #1 of US998, H930 and India H930DS Oreo KDZ threads to use dev patched LGUP to downgrade to earlier versions of KDZ in order to use this WTF bootloader unlock exploit. You can always update to newer firmware AFTER bootloader unlock.
I've also updated the instructions in this thread to include references to the July 2018 security patch situation.
I actually don't see an LG G4 unlock.bin in that thread. I see someone asking for one. Somebody supplied one from an M8, but I don't see one from an LG G4. OR if they did, they edited off, back in 2015. So, where did you find it? Which post?so, i search on google lg unlock.bin
i found lg g4 unlock.bin in this link https://forum.xda-developers.com/g4/general/unlock-bin-t3158596
Wait. You flashed an Huawei M8 unlock.bin code onto an AT&T LG V30 H931 and UNLOCKED the bootloader? After of course crossflashing H930 Oreo KDZ and basically bricking your phone.
The only reason I halfway believe this is because the guy with the rooted H932 in China is running Galaxy 8 TWRP with parts of H930 flashed over the phone.
And because you were one of the first to crossflash your phone in this forum. So, you know what you are doing.
So, how does your phone identify now in About Phone? H930 or H931? Or Canadian H933 (which you had cross flashed to earlier.)
In LGUP, in download mode, how does it identify? Even after I flashed US998 over LS998 (Frankenstein thread), in download mode with LGUP, the phone still showed as LS-998.