I can see my device 'fastboot devices' I can see my device as fastboot device. But even if I enter 'fastboot flash' command, I see no respond, CMD freezes immediately so I can't flash any img to my device. For example when I use 'fastboot flash recovery twrp.img', CMD will freeze up. After disconnecting the device, CMD continues up and I see:
Code:
target didn't report max-download-size
sending 'recovery' (30324 KB)...
FAILED (command write failed (No error))
finished. total time: 0.017s
output.
EDIT: I asked these questions based upon the post above. We need more information. Many variants don't have full fastboot flash commands. For those that do, you may need to change ADB installations or use a different computer. AMD Ryzen doesn't work well with V30.
_________
What variant do you have? What firmware are you on?
Further questions... Have you already bootloader unlocked your phone? You have to unlock your bootloader before you can install TWRP custom recovery.
Instructions on how to do both are in the WTF thread.
Also if you've unlocked your bootloader, you know that many V30 variants don't have fastboot flash commands.
Which is why you need the WTF instructions to unlock your bootloader and install TWRP custom recovery.
Unless you have a T-Mobile H932, in which case there's an alternate set of instructions to install TWRP custom recovery... That's why we need to know what variant you have and what firmware you are on.
I think you need to read the Root Sticky Guide. Start with Post #1:
ROOT YOUR V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Heroata said:
I can see my device 'fastboot devices' I can see my device as fastboot device. But even if I enter 'fastboot flash' command, I see no respond, CMD freezes immediately so I can't flash any img to my device. For example when I use 'fastboot flash recovery twrp.img', CMD will freeze up. After disconnecting the device, CMD continues up and I see:
output.
Click to expand...
Click to collapse
Sounds like you did NO Google searching and even failed to look at XDA itself to see how to root.
Also I bet you have a T-Mobile V30.
Basic Google search.
XDA root LG V30
That will bring up WTF and LAFsploit. Would have saved you a post and got what you needed 100X faster...
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Sounds like you did NO Google searching and even failed to look at XDA itself to see how to root.
Also I bet you have a T-Mobile V30.
Basic Google search.
XDA root LG V30
That will bring up WTF and LAFsploit. Would have saved you a post and got what you needed 100X faster...
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
Just searched his posts. He's not a newbie -- posted months ago -- and he has an H930 variant:
Heroata said:
I have H930G Turkey converted to H930.
---------- Post added at 04:13 PM ---------- Previous post was at 03:37 PM ----------
Which version should I use? @ChazzMatt
Click to expand...
Click to collapse
Heroata said:
Not problem. Eventually ChazzMatt saved my day.
Click to expand...
Click to collapse
So my suggestion about reading the Root Sticky Guide (which is normally good advice for everyone!) doesn't apply to him.
Unless he now has another V30 and is trying to root that one? In which case maybe he has a T-mobile H932?
ChazzMatt said:
EDIT: I asked these questions based upon the post above. We need more information. Many variants don't have full fastboot flash commands. For those that do, you may need to change ADB installations or use a different computer. AMD doesn't work well with V30.
_________
What variant do you have? What firmware are you on?
Further questions... Have you already bootloader unlocked your phone? You have to unlock your bootloader before you can install TWRP custom recovery.
Instructions on how to do both are in the WTF thread.
Also if you've unlocked your bootloader, you know that many V30 variants don't have fastboot flash commands.
Which is why you need the WTF instructions to unlock your bootloader and install TWRP custom recovery.
Unless you have a T-Mobile H932, in which case there's an alternate set of instructions to install TWRP custom recovery... That's why we need to know what variant you have and what firmware you are on.
I think you need to read the Root Sticky Guide. Start with Post #1:
ROOT YOUR V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Click to expand...
Click to collapse
As you found I have H930G turned to H930. I flashed a fresh new Pie KDZ with REFURBISH option. So had to refollow WTF steps. But like in almost every time, new ADB environment occured some problems. This problem occured in 2 modern laptops. Then I tried on an old laptop and problem is just a bit decreased like sometimes it's not freezing but having write error. Then I figured out that if I plug in and out quickly then plug in persistent, it will work. I don't have any idea why i can solve it by that way but I wanted to share my exact experience.
Heroata said:
As you found I have H930G turned to H930.
Click to expand...
Click to collapse
Such a weird problem. Have you tried to use newer (or older) adb/fastboot binary? I had similar issue with my older xiaomy phone, I thought it was usb port or cable issue, then I tried to replace adb/fastboot binary with those from MiFlash app folder. Now it works as usualy does.
Are you by any chance using Ryzen CPU and using 1903 version of Windows 10?
Related
Hello All,
I'm new here, so I'm not exactly sure if this is the correct forum to be posting this, but here's my question:
When I attempt to unlock my bootloader using fastboot and the "fastboot oem unlock" command, it simply returns:
Code:
... INFOOEM unlock is not implemented
OKAY [ 0.001s]
Has anyone else gotten this message or anything like it? Or am I doing something wrong?
I'm rooted and running the 4.5.91 (ATT) update, and I updated from Gingerblur 3.5 using the PC update program.
The only way to unlock bootloader at this time is flashing pudding and then running fastboot OEM commands
SevenandForty said:
Hello All,
I'm new here, so I'm not exactly sure if this is the correct forum to be posting this, but here's my question:
When I attempt to unlock my bootloader using fastboot and the "fastboot oem unlock" command, it simply returns:
Code:
... INFOOEM unlock is not implemented
OKAY [ 0.001s]
Has anyone else gotten this message or anything like it? Or am I doing something wrong?
I'm rooted and running the 4.5.91 (ATT) update, and I updated from Gingerblur 3.5 using the PC update program.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
Really? Huh- I found that fastboot method on this website
briefmobile(dot)com/how-to-unlock-the-atrix-4g-bootloader
It says to use the command prompt to run fastboot and unlock it- I'm not sure if this was disabled or something, because it seems to have worked for most people on the 2.3.4 beta.
SevenandForty said:
Oh, really? I found that fastboot method on this website
briefmobile(dot)com/how-to-unlock-the-atrix-4g-bootloader
It says to use the command prompt to run fastboot and unlock it- I'm not sure if this was disabled or something, because it seems to have worked for most people on the 2.3.4 beta.
Click to expand...
Click to collapse
if you're running the ota update, then you don't have an unlockable bootloader. you need to flash a pudding sbf to get one, which you can find instructions to on either the general forum or the dev forum.
Oh, I see. Thanks!
same problem
I also have the same problem but I have a stock 2.3 atrix does it make a difference?
I had to flash the 4.5.91 pre root sbf Via rsd lite then run that fastboot command.
Sent from my MB860 using XDA App
You need to flash the unlock sbf first. Just remember that if you're on 2.3.4, after you flash the sbf, the phone will reboot and soft brick - that's normal. Be ready to fastboot flash RomRacer's CWM recovery, and have the two 2.3.4 Fruitcake builds on your external sdcard beforehand.
Once you've flashed RomRacer's recovery successfully, pull the battery, put in your SIM and sdcard again, boot into recovery, and then install both fruitcake builds.
After that, your phone will boot and you can root it at your leisure.
SevenandForty said:
Hello All,
I'm new here, so I'm not exactly sure if this is the correct forum to be posting this, but here's my question:
When I attempt to unlock my bootloader using fastboot and the "fastboot oem unlock" command, it simply returns:
Code:
... INFOOEM unlock is not implemented
OKAY [ 0.001s]
Has anyone else gotten this message or anything like it? Or am I doing something wrong?
I'm rooted and running the 4.5.91 (ATT) update, and I updated from Gingerblur 3.5 using the PC update program.
Click to expand...
Click to collapse
Are you flashing the .sbf first? If not, that is your problem or you have the same luck as me.. One or the other. Anyway, this is how I fixed mine:
I had this issue too.. Very irritating. I was using Linux to get my phone unlocked. When I went home from work, I tried again on windows 7 this time using RSDLite. It kinda worked. RSDLite got to 98%, the phone crashed and the flash status displayed failed. However, at 98%, the only thing left to do was for the phone to turn back on and verify the flashed image as far as I was concerned. Anyway, the phone said "Operating system not found" and went into fastboot mode from there. I felt I had nothing to lose by moving on. I issued a fastboot oem restore, and was able to get my code. I then reissued the command and typed in the whole code as windows wouldn't let me copy/paste from the command prompt (thanks Bill..). After doing this and pressing enter, my bootloader was nice and unlocked in about half a second. I rebooted using fastboot, and it locked up, so a battery pull got me working just fine. Hope this helps someone.
same problem
i have the same problem
1. i did use the sdf. but in the end it says FAIL in RSD
2. cant continue
3. still searching for answer:crying:
---------- Post added at 06:18 PM ---------- Previous post was at 06:07 PM ----------
hammerlock13 said:
Are you flashing the .sbf first? If not, that is your problem or you have the same luck as me.. One or the other. Anyway, this is how I fixed mine:
I had this issue too.. Very irritating. I was using Linux to get my phone unlocked. When I went home from work, I tried again on windows 7 this time using RSDLite. It kinda worked. RSDLite got to 98%, the phone crashed and the flash status displayed failed. However, at 98%, the only thing left to do was for the phone to turn back on and verify the flashed image as far as I was concerned. Anyway, the phone said "Operating system not found" and went into fastboot mode from there. I felt I had nothing to lose by moving on. I issued a fastboot oem restore, and was able to get my code. I then reissued the command and typed in the whole code as windows wouldn't let me copy/paste from the command prompt (thanks Bill..). After doing this and pressing enter, my bootloader was nice and unlocked in about half a second. I rebooted using fastboot, and it locked up, so a battery pull got me working just fine. Hope this helps someone.
Click to expand...
Click to collapse
sir, could you kindly pls. give the codes step by step, it will help a lot, i can not use my Atrix Thanks in Advance
OEM unlock is not implemented
I also have this issue
I am desperately looking for a solution without luck for my rooted
Atrix 4G Buld 4.5.2A
GB 2.3.4
If someone can point me to a solution I will be very glad
Thanks
Eli
i'm in the same situation....
help please
FIXED it and now my phone is unlocked
you have to flash the phone with RSD this file http://diamantephoto.com/IHOP_Bell.rar
and rerun the command to give you the phone ID
hope it helps for you
Will huawei give any trouble if we unlock the bootloader, does anyone think its worth it? I would like to try cm when it does release and right now I'm thinking of trying the mod to turn on and off swap
Sent from my KIW-L24 using Tapatalk
Turning on and off swap is the main reason I want to unlock the bootloader at the moment. Just haven't had time yet.
Arobase40 said:
If you're talking about commercial and customers side, and for what I know Huawei won't give any kind of supports with unlocked devices.
On the legal side it may depend on your country or region laws for the hardware warranty : Europe is more protective with customers...
So the answer is YES, you may have trouble with Huawei and with unlock devices if you're seeking after any kind of supports. Otherwise you can do what you want as the device is yours...
Click to expand...
Click to collapse
Yea was wondering about that and if I ever needed any repairs, I ended up doing it anyway everyone here seems to be unlocking anyway
Sent from my KIW-L24 using Tapatalk
Silly question, but what is swap?
Sent from my KIW-L24 using Tapatalk
Is there a tool made for this device yet for flashing adb fastboot? I used adb fastboot to unlock my L24 but when trying to flash the recovery.img that is where I hit a wall. I am not to up on adb fastboot besides simple commands for logs and unlocking a bootloader such as this. when I open a comand prompt it doesn't see the img file and give me a fail message. I just thought I would check to see if anyone has made their own tool yet. Thank you for your time.
Arobase40 said:
I may probably misunderstand your post but if you passed the bootloader unlocking process the rest of the procedure should be straightforward...
The "recovery.img file" (could be named differently) should be in your local system folder (Windows or Linux) and not in the phone (so no adb shell command) and make sure you ticked the USB debug mode in the developer panel...
The full procedure is here :
http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190
Click to expand...
Click to collapse
Yes, that was the post I was using as a guide. All the commands worked great to it came to the part where I had to flash recovery in bootloader mode. It wouldn't/couldn't find the destination file. I will just have to read some more and figure this out. Thank you for your reply. I'm almost done, just have to get recovery flashed now and I'll be good to go.
"Chance Favors the Prepared"
Probably 70% chance of having some hassle with warranty with bootloader unlocked, they will also blame any glitches on software or roms you using.
I scenario where phone 100% power dead they likely never look into bootloader or rom status so won't matter .
your region & person dealing with it will make huge difference on the day ...
Arobase40 said:
I still don't understand your actual position and troubles...
- Is your bootloader already unlocked ?
- If yes, so I guess you have already installed the Honor drivers and setup the adb software ???
- Which OS are you using ?
I don't know what you call the destination file, but you simply need to download the recovery file in step 8, and then continue to step 11.
If the downloaded file is "kiwi_twrp_3-21_recovery.img" save it to for example to your C:\temp folder.
When you open the command prompt, simply "cd c:\temp"and change the command "fastboot flash recovery twrp_kiwi.img"with "fastboot flash kiwi_twrp_3-21_recovery.img" or rename the original name to a simpler one, what suite you the best.
---------- Post added at 01:44 PM ---------- Previous post was at 01:34 PM ----------
I have written different posts about warranty and the fact that manufacturers say you'll be out of warranty if you unlocked or rooted your devices has no chance to be applied according to your local laws. The manufacturers contractual rules has no value if the local laws say differently !
Click to expand...
Click to collapse
Thank you Sir. That is exactly what I needed. I needed to know where to put the .img TWRP file, the destination, and his to access that file then with the command prompt.
Yes, my bootloader was unlocked successfully and adb had no problems picking up my device. It just couldn't locate the file that I was typing into the command prompt window. A lot of the roles that are out for use have spoiled me and that is all automate because everything is located in the same folder. I need to learn this though.
Thank you again.
"Chance Favors the Prepared"
Again, thank you. That was all I needed. It worked great once I put the TWRP.img file where it needed to be. I am unlocked, have custom recovery installed and am now rooted.
Chance Favors the Prepared "
So I got the T-Mobile Variant of the LG V30 and ran command to unlock the bootloader and it seems to have unlocked it as well as wiping the data and cache. I know with previous LG devices with T-mobile that the there were no commands to be able to write to the device. Is there anyway to verify if this is the case?
Following
Binary Flood said:
So I got the T-Mobile Variant of the LG V30 and ran command to unlock the bootloader and it seems to have unlocked it as well as wiping the data and cache. I know with previous LG devices with T-mobile that the there were no commands to be able to write to the device. Is there anyway to verify if this is the case?
Click to expand...
Click to collapse
This is very interesting, I wonder if bootloader is unlocked on the upcoming "sim unlocked" US998 as well? If the T-Mobile bootloader is unlocked this may be a game changer.
Apparently you can unlock bootloader but cannot run ANY other commands. So, its basically useless.
Binary Flood said:
So I got the T-Mobile Variant of the LG V30 and ran command to unlock the bootloader and it seems to have unlocked it as well as wiping the data and cache. I know with previous LG devices with T-mobile that the there were no commands to be able to write to the device. Is there anyway to verify if this is the case?
Click to expand...
Click to collapse
You have already verified by the fastboot oem id command
Killua96 said:
You have already verified by the fastboot oem id command
Click to expand...
Click to collapse
It's a damn shame, thanks for letting me know. Hopefully we could get another dirty santa type exploit.
I wonder what's up with that flashall command...
Sent from my VS995 using Tapatalk
Whatever you do, don't use fastboot flashing unlock_critical ... it'll factory reset your phone and won't unlock a damn thing ... not that I know from experience or anything.
gogozombiii said:
Whatever you do, don't use fastboot flashing unlock_critical ... it'll factory reset your phone and won't unlock a damn thing ... not that I know from experience or anything.
Click to expand...
Click to collapse
if only i would've seen this earlier because that's what i ended up trying out in adb and boom a voided warranty and i didn't get time to take up the daydream offer since i'm sure they will be able to see i already voided my warranty. . In the mean time i have pulled a couple of files out like for example system(i used the adb pull /system), vendor( adb pull /system/vendor) and frameworks(adb pull /system/framework). ive just been poking around trying to see if there is any way to find the boot image. any ideas where it could be located?
If you have pulled system. can you please check if you have any *.mbn files there. If yes then copy, zip and attach them here.
These are lte modem configuration files which interest me much.
Thank you
Binary Flood said:
So I got the T-Mobile Variant of the LG V30 and ran command to unlock the bootloader and it seems to have unlocked it as well as wiping the data and cache. I know with previous LG devices with T-mobile that the there were no commands to be able to write to the device. Is there anyway to verify if this is the case?
Click to expand...
Click to collapse
It has been discussed in the LG V30 Unlock bootloader and Root thread as well as the more specific T-mobile LG V30 root effort thread.
This post (October 7) shows commands a T-mobile LG V30 user tried after unlocking his bootloader:
https://forum.xda-developers.com/showpost.php?p=74080195&postcount=112
And here's other exchanges in that same thread:
bp328i said:
Try "fastboot oem device-id"
I bet it fails which means yes the bootloader can be unlocked but adb is disabled so no way to load TWRP or any custom recovery. This would be the same as on the T-Mobile G6.
Click to expand...
Click to collapse
ShadowDXS said:
It does fail. That means we will have to download the image for TWRP on the device, and if root is gained we can then cp the file to the recovery directory. That blows.
Click to expand...
Click to collapse
bacon612 said:
So there we have it. It's locked just like previous models. Now we wait for the unlocked variant...
Edit: locked as in the fastboot commands have been disabled the same was they were on the g6
Click to expand...
Click to collapse
With the fastboot commands disabled you need root to install TWRP or you need TWRP to get root, and neither is possible right now.
The posts above are from the more general LG V30 Unlock bootloader and Root -- general because it covers ALL LG V30 models, and it's pretty much agreed only the official carrier unlocked LG V30 US998 and H930 will have "real" bootloader unlock with full ADB fastboot commands. That doesn't exclue that some exploit might be found by devs, but just if you want easy bootloader unlock and root -- like with the LG G6 carrier unlocked models, which have root, recovery, ROMs, kernels.
_________
However, this is the thread below is to specifically discuss the T-mobile LG V30 root efforts:
T-mobile LG V30: Progress Towards Root/TWRP/ROMs (not achieved yet)
If there's any dev magic, that will be the thread to watch.
Initially the op did not specify he wished to only talk about the T-mobile LG V30 instead of all LG V30 models -- but once we got that clarified (the first few posts on page 1) then that's what the rest of the thread is about.
---------- Post added at 07:26 AM ---------- Previous post was at 06:38 AM ----------
_______________________
arh2o said:
This is very interesting, I wonder if bootloader is unlocked on the upcoming "sim unlocked" US998 as well? If the T-Mobile bootloader is unlocked this may be a game changer.
Click to expand...
Click to collapse
Been discussed in depth since early September in the bootloader unlock and root thread -- even before the LG V30 was released. Well known, the T-mobile LG V30 would have an "unlocked" bootloader -- but it doesn't do any good because the ADB fastboot commands are removed. (September 3)
The official carrier unlocked US998 and H930 models -- the ones NOT sold by any carriers, what LG calls for the "open market" will be placed on the LG Developer Bootloader Unlock list AFTER release, and will be eligible for bootloader unlock. They will have full ADB fastboot commands. Just like the LG G6 models then they will quickly get dev support for root, recovery, ROMs, kernels.
The official carrier unlocked LG G6 US997 was released May 12, 2017 but was not placed on the the Bootloader Unlock list until June 29. SIX WEEKS. However, there's now tons of dev work available.
Let's hope it doesn't take that long after the LG V30 US998 is released!
Whereas, the T-mobile LG G6 while ostensibly having an unlocked bootloader still has no root or recovery. Six or seven months later, still no dev work available.
R800x_user said:
if only i would've seen this earlier because that's what i ended up trying out in adb and boom a voided warranty and i didn't get time to take up the daydream offer since i'm sure they will be able to see i already voided my warranty. . In the mean time i have pulled a couple of files out like for example system(i used the adb pull /system), vendor( adb pull /system/vendor) and frameworks(adb pull /system/framework). ive just been poking around trying to see if there is any way to find the boot image. any ideas where it could be located?
Click to expand...
Click to collapse
Can't pull boot without root access.
Sent from my VS995 using Tapatalk
Out of curiosity, has anyone tried
Code:
fastboot oem ?
command?
gokart2 said:
Out of curiosity, has anyone tried
command?
Click to expand...
Click to collapse
Deleted
Made a bit of a boob here. I was upgrading my firmware version 10v to the new January firmware using LGUP. Unfortunately i forgot to click Upgrade, and so by accident ran the refurbish command.
The 'upgrade' ran through OK, and it boots, but I lost root/twrp (im on H930).
When I tried to bung TWRP back on, I cant get the fastboot boot twrp.img command to work (sorry if syntax is wrong while typijg this message) - that command just reboots the phone but it sits of the LG v30 loading screen.
Ive noticed that the fastboot screen tells me to make sure I flip the OEM Unlock switch in Dev options (a blue message). However, that setting is greyed out. Running the getvar command says I am unlocked though, as does re-running the unlock command.
So im confused. Im guessing i cant install TWRP as fastboot mode thinks im locked?
Any ideas??
Sent from my LG-H930 using Tapatalk
It may say you are unlocked, but you are not. Once you are rooted, you should never flash a KDZ -- especially if you are unlocked via the unlock.bin method. If you want to upgrade, flash the firmware via TWRP.
But you are in this situation now.... so, have you tried flashing unlock.bin again?
-- Brian
runningnak3d said:
It may say you are unlocked, but you are not. Once you are rooted, you should never flash a KDZ -- especially if you are unlocked via the unlock.bin method. If you want to upgrade, flash the firmware via TWRP.
But you are in this situation now.... so, have you tried flashing unlock.bin again?
-- Brian
Click to expand...
Click to collapse
Hi Brian
Yeah, if i try flash the unlock.bin file again i get an error telling me im already unlocked (or words to that affect...im away from my PC so can't see the exact message)
Sent from my LG-H930 using Tapatalk
When you get a chance, grab a copy of the patched LG UP, dump misc, persist and persistent, zip them up and PM me a link to the zip.
If you have any chance of fixing this, it will be wiping one or all of those partitions -- but I need to take a look at them to figure out which ones.
Once wiped, the phone will no longer report being unlocked and you can flash your unlock.bin again. Once you are unlocked, you will need to make a dump of those partitions again so I can compare them. I will then fix them so you can flash them back.
-- Brian
runningnak3d said:
When you get a chance, grab a copy of the patched LG UP, dump misc, persist and persistent, zip them up and PM me a link to the zip.
If you have any chance of fixing this, it will be wiping one or all of those partitions -- but I need to take a look at them to figure out which ones.
Once wiped, the phone will no longer report being unlocked and you can flash your unlock.bin again. Once you are unlocked, you will need to make a dump of those partitions again so I can compare them. I will then fix them so you can flash them back.
-- Brian
Click to expand...
Click to collapse
Awesome Brian, thanks loads for the help. I'll PM you the Zip as soon as ive done it
Sent from my LG-H930 using Tapatalk
runningnak3d said:
When you get a chance, grab a copy of the patched LG UP, dump misc, persist and persistent, zip them up and PM me a link to the zip.
If you have any chance of fixing this, it will be wiping one or all of those partitions -- but I need to take a look at them to figure out which ones.
Once wiped, the phone will no longer report being unlocked and you can flash your unlock.bin again. Once you are unlocked, you will need to make a dump of those partitions again so I can compare them. I will then fix them so you can flash them back.
-- Brian
Click to expand...
Click to collapse
Brian, quick question. Would i need to be rooted to create the dumps....?
Sent from my LG-H930 using Tapatalk
Nope.
-- Brian
thenoble06 said:
Any ideas??
Click to expand...
Click to collapse
Since you flashed a fully stock rom, can you try to do 'fastboot oem lock' and then check developer settings if OEM unlocking became active so you can flip it to ON again?
padmanek said:
Since you flashed a fully stock rom, can you try to do 'fastboot oem lock' and then check developer settings if OEM unlocking became active so you can flip it to ON again?
Click to expand...
Click to collapse
Ahhh cool, that did it. Re-locked, flashed latest KDZ with LG UP and then relocked, installed Recovery and re-rooted.
Jobs a good un!
I'll stay away from KDZ files now and just update/upgrade via TWRP (that's right yeah)?
Thanks both for your help!!
Sent from my LG-H930 using Tapatalk
Has anyone figured out how to root a Verizon vs996 phone? I read on the internet its maybe possible using the Frankenstein bug but I cant seem to find any detailed guides on how to root my vs996 using the Frankenstein bug. If anyone could point me to detailed instructions, it would be greatly appreciated.
Find and read the wtf thread. Go to the very first post on it and click the link. That link will take you to the post that gives you the guide and will answer all your questions. I am a Verizon customer with the vs996 phone currently running it on a rooted stock us998 rom. Read that post (#193) very carefully so you understand what needs to be done.
Here it is.
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500/post76520798
Can anyone explain how, in the video, the phone was booted into the screen he's in to run the commands against the phone? The screen says "restart" in large font.
dorlow said:
Has anyone figured out how to root a Verizon vs996 phone? I read on the internet its maybe possible using the Frankenstein bug but I cant seem to find any detailed guides on how to root my vs996 using the Frankenstein bug. If anyone could point me to detailed instructions, it would be greatly appreciated.
Click to expand...
Click to collapse
You haven't looked very hard. In the Guides section, WTF instructions thread is one of the most frequent in this forum. It's clearly titled:
(WTF...!) LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions)
"Frankenstein" isn't a bug. It's a procedure to temporarily convert to another variant. Either used to SIM card unlock a phone and/OR (in this instance) to get fastboot flash commands.
"WTF" however is an exploit to allow us to unlock the bootloader on early Oreo firmware. So you use Frankenstein (if necessary) to convert to variant with fastboot flash commands and then use the early Oreo firmware to unlock the bootloader. THEN, you can either convert back to to the variant you came from and/or upgrade to newer firmware. Some phones don't need this Frankenstein, if they already have fastboot flash commands. But yes VS996 does.
dorlow said:
Can anyone explain how, in the video, the phone was booted into the screen he's in to run the commands against the phone? The screen says "restart" in large font.
Click to expand...
Click to collapse
On post #1 of that WTF thread, you apparently ignored the
HUGE LINK FOR THE INSTRUCTIONS.
That's the link to post #193 of the quite detailed instructions, where all your questions will be answered... ALL V30/V30+/V30S on the planet can be bootloader unlocked and rooted. PRINT OUT those instructions and read them. PRINT THEM OUT.