yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 Android Development] roirraW "edor" ehT:
No, unfortunately, there's no other way to root on VK810 Lollipop other than Kingroot, or a lot of trial and error by following a guide of [MENTION=5022682]Hnk1[/MENTION] 's but it seemed to be hit and miss if people successfully rooted, and it involved Kingroot too.

I always do the exact same process I detail in the first link in my signature below. I don't recall at this point if Stump worked for me on VK810's KitKat, but it works for me 100% of the time on Jellybean. To begin with, I flash the 11A (Jellybean) KDZ with LG Flash Tool 2014. Plus, installing the initial version 2.7.0.1 of TWRP is one less step on 11A versus later releases because you don't have to downgrade the bootloader first, it's already downgraded. Full details at the link. If you have any questions about that process go ahead and send me a message in that thread.
[G Pad 8.3 Android Development] mikekoz:
OK......I am trying to flash my VK810 again because I am still having problems. I just put the tablet in download mode, but the laptop is seeing it as a modem. The flash tool keeps saying it cannot reach the server (what server?), and I cannot get the thing to restart and come out of download mode. I have tried holding the power button down for over 10 secs, holding the power and vol up and down keys, nothing works. The screen goes blank when I hit the power button again, but it still shows download mode. HELP!!! :mad:
[G Pad 8.3 Android Development] roirraW "edor" ehT:
Sorry to hear you're having troubles. It's normal that the device shows up in the Modem section - it should.

It's also common that the flash tool gives error dialogs including about not being able to reach the server. Ignore all error dialogs, just drag them out of your way. Within 20 minutes you should find your tablet flashed.

I don't know what to suggest regarding the power. I'd try holding power for 30 seconds, just be aware of when the screen goes off and let go of the power button right away or it'll just power right back on.
[G Pad 8.3 Android Development] mikekoz:
I really appreciate all of your help with this! One more thing, should I go into the tabs recovery and do a full format, data and system, before I do this? I was planning on doing the CSE format in the LG tool which is supposed to do that anyway.
[G Pad 8.3 Android Development] roirraW "edor" ehT:
You're welcome! As you say, CSE does that anyway so no need to factory reset.
[G Pad 8.3 Android Development] mikekoz:
This is interesting! I let the LG Flash tool do its thing and it worked. Now KingRoot will not root it, but Kingoroot did! Kingoroot never worked on it before. However, I still am having one problem that has lingered since I originally screwed it up with Super sume. It appears to be maybe 90% rooted. Most apps that need root work, like Purify, Greenify, Lucky Patcher, Titanium backup, etc. I also use Kernel Audiator, but the settings I make in that app do not hold after a restart. You can change settings and they will work as long as you do not restart. I tried other similar apps and they do the same thing, so I am guessing that there is still some system file location that Kingoroot is not giving these programs full access to.
[G Pad 8.3 Android Development] roirraW "edor" ehT:
Thanks for the report! Which KDZ did you use? For whatever reason, the latest Kingroot app from it's website roots it for me on 36B, but it's good to have options in case it stops working, or doesn't as in your case.

Because I have no experience with using either in the long-term, I would suggest downgrading the bootloader and installing and updating TWRP as described in my first link below. Then you can flash my 36B ROM, and flash SuperSU.

As I said before, flashing the 11A KDZ with the CSE option is the easiest way to root and put TWRP on. I know you didn't necessarily care about putting TWRP on, but maybe doing so would solve your problems since you could flash my ROM and SuperSU, and there'll be no Kingroot or Kingoroot to get rid of.
[G Pad 8.3 Android Development] mikekoz:
Yes.....I think it is time to get off my butt and do it!! Thanks!!!
[G Pad 8.3 Android Development] roirraW "edor" ehT:
LOL! :D You're welcome!
[G Pad 8.3 Android Development] mikekoz:
I put stock 4.2.2 back on the tablet, rooted with Stump, installed TWRP, then flashed your ROM. All of that went fine. The tablet seemed to work normally for a day. Today, some applications cannot get root access, they just hang. I also cannot get back into TWRP using ADB. I get an error on the tablet stating "Secure Booting Error" Cause: boot certification verify. WTH! I did not do anything to it after I flashed the rom. I initially booted into the older version of TWRP, then flashed the more recent one mentioned here.
[G Pad 8.3 Android Development] roirraW "edor" ehT:
Did you read the part in the first post of my ROM instructions about having to re-downgrade your aboot (just like you had to do before the first time you installed TWRP) to get into TWRP again? You don't have to flash TWRP again, just have to downgrade to the 4.2.2 aboot to get into TWRP. When you're done in TWRP, you have to flash my zip that's just the 36B 5.0.2 aboot in order to be able to boot the ROM again. I know it's a pain but I'm not knowledgeable enough to find another way.
[G Pad 8.3 Android Development] mikekoz:
Would I have to do that every time I wanted to get into TWRP?
[G Pad 8.3 Android Development] roirraW "edor" ehT:
Yes. Getting into TWRP requires the bump-vulnerable 4.2.2 bootloader. 35B and 36B Lollipop each require their matching bootloader.
[G Pad 8.3 Android Development] mikekoz:
I think I will just leave it as is. Problems are pretty minor really. So far I am not experiencing the slowdown / lag problem, it is booting quicker, and most rooted apps work fine. Sometimes if I open up Supersu I will get a request to give root access to an app. I was just trying to get back into TWRP to reinstall Supersu. You cannot update it normally. I may do the bootloader trick this weekend if I get the energy, but my tablet is working better than it did when it had Kingroot or Kingoroot on it. The only thing that is a bit strange is that settings I set using a Kernel Tweaking program do not stick after a restart. I have tried multiple tweaking apps, and the problem is the tablets OS, not the individual application. I think it is still not 100% rooted, but this tablet has always been hard to root/hack!
[G Pad 8.3 Android Development] roirraW "edor" ehT:
With flashing SuperSU.zip, I've never had trouble being rooted and keeping it that way. You were using at least SuperSU v2.46? I've performed the process of restoring to stock unrooted, rooting, putting TWRP on, and flashing my ROM/SuperSU and debloating so many times it's crazy (several dozen times minimum). LOL. Sorry to hear you're still experiencing any trouble at all.

I haven't used kernel tweaking programs in a long time so I can't advise you there.
[G Pad 8.3 Android Development] mikekoz:
I tried updating it by downloading one of the beta version using the apk. It installs, but does not update the binary.
[G Pad 8.3 Android Development] ssimaa:
vk810 Help me

Hello Can anyone help with a brick vk810 need .tot file 4.2.2 or 4.4.2
[G Pad 8.3 Android Development] roirraW "edor" ehT:
http://www.lgbbs.com:41/thread-838-1-1.html

Costs money to get it (I think $10 U.S.), no way to know ahead of time if it's real or working. You'd also need a .DLL for the VK810 which you can find on there too, or the .DLL from one of the KDZs might work.

If you try it please share it?
[G Pad 8.3 Android Development] roirraW "edor" ehT:
Thanks to [MENTION=7370899]Papay346[/MENTION] for purchasing and testing the 22B_00 TOT file from a Chinese website, and for sharing it with us! His original post here http://xdaforums.com/showpost.php?p=66089535&postcount=6.

Added 22B TOT and the 22B .DLL that should be necessary to flash the TOT. [MENTION=7370899]Papay346[/MENTION] tested the TOT - I haven't personally tested it and the .DLL (unsure if that's the .DLL he used but it should be fine).

TOT: VK81022B_00.TOT file with MD5 hash inside - KitKat 4.4.2.7z

DLL for TOT method: VK81022B_00-KitKat_4.4.2-Web8064.DLL_for_TOT_method.7z
[G Pad 8.3 Android Development] ssimaa:
THANK YOU SO MUCH

I regained my tablet

good luck to you )))))))))))))))
[G Pad 8.3 Android Development] roirraW "edor" ehT:
Awesome! All thanks to [MENTION=7370899]Papay346[/MENTION]. :)
[G Pad 8.3 Android Development] roirraW "edor" ehT:
Added the partition images extracted from the 22B TOT.
[G Pad 8.3 Android Development] ouellettesr:
I have a Hard Bricked vk810, will the TOT file help me? I have tried to use minitool and qfil, but the Minitool doesnt recognize the disc, and Qfil fails to download anything. I apologize if this is not the right place to post.

my device shows up as: Qualcomm HS-USB QDLoader 9008
[G Pad 8.3 Android Development] roirraW "edor" ehT:
You will need the TOT, but not the usual TOT flashing method. Just Google for "Qualcomm HS-USB QDLoader 9008" and you should find the software and special drivers necessary to recover. It's different drivers and software than used for any other KDZ/TOT flashing.

You'll find several detailed threads on XDA about recovering from "Qualcomm HS-USB QDLoader 9008".
[G Pad 8.3 Android Development] ouellettesr:
I have found several detailed threads on XDA with Google about recovering from "Qualcomm HS-USB QDLoader 9008", but none of them work.

I've found several tutorials, and a couple videos, but nothing is working or applies directly to vk810, so the files they have arent specific to my device. I even read in one thread that recovering a hardbricked vk810 isnt possible because it hasnt been supported enough.

Ive downloaded 3 different versions of qualcom drivers and they all have the same result. One thread talks about the new and old 9008, but says to use minitool to delete partitions. My device shows up in device manager, but not minitool. Ive used the command line to put windows in test mode, etc. Ive probably tried every tutorial google has to offer thats specific to LG in the least if not the vk810. One tutorial says to download the stock firmware for Qfil for my device but then the rest of the tutorial says nothing about it, link below.

https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html

followed that exactly but no go.

I could list all of the tutorials ive found but I think that would just be a waste of everyones time. I was hoping for a guide specific to "vk810 Qualcomm HS-USB QDLoader 9008 hard bricked"

But nothing comes up.

Im over it at this point, thanks for the google search suggestion.
[G Pad 8.3 Android Development] roirraW "edor" ehT:
They don't have to be specific to the VK810. The software and drivers are the same, as far as I know, for any make or model device in "Qualcomm HS-USB QDLoader 9008" mode. The TOT is the only part that's specific to the device you're trying to recover. If you try any further TOT methods and can't get them to work, I suggest writing in the threads that have to do with the method as someone there would probably be able to help better than I can. I haven't had this happen in a year, although I had personally recovered from this condition on both my VK810 and my VS985 several times; but I'm no expert.

Maybe PM [MENTION=2250889]R-T-B[/MENTION]. He has done work repairing devices before, I became familiar with him in the Verizon LG G3 threads and he's offered to repair people's devices for a nominal fee before. PM him and ask him if he's willing to give it a try.
[G Pad 8.3 Android Development] Switcher05:
I am trying to download the VK81024A from the androidfilehost.com however it is going a painful 100k/bs and dropping connection every few minutes. I got 167mb on 32 connection retries...

There is no other mirror listed and I can't seem to find an active link for the Kitkat kdz, I have tried rooting with Lollipop and the Chinese apps are giving me cancer.

Do you have another host? Or I can send you a onedrive folder to upload?
[G Pad 8.3 Android Development] roirraW "edor" ehT:
Hi, I've confirmed that AFH is extremely slow downloading that file right now. I'm uploading just this file to here right now. It estimates 50 minutes from now for it to finish syncing. Let me know if that helps.

Thanks!
[G Pad 8.3 Android Development] Switcher05:
I got it downloaded, thanks. Ready to throw this thing in the target practice pile I have spent hours on it and continuous issue after issue.
[G Pad 8.3 Android Development] roirraW "edor" ehT:
You're welcome! I know what you mean. :)
[G Pad 8.3 Android Development] harpy.eagle:
Did u manage to revive the tab?

My tab was perfectly working with twrp, lineage 17.1.

While using it, it's battery died. So put it on charging. It showed some sign on screen like connect charger to tablet while display ON all the time which charger was connected.

So after about 30 mins, I tried powering it ON but after that it died completely. No sign of any life. Tried all key presses to revive tab with dead battery and charger but no results.

So now tried connecting it to PC and it's detected as Qualcomm 9008 device.

Again tried to flash kdz with lg 2014 tool byt it's showing error of device disconnected from pc. And flashing doesn't continue beyond 60%.

I tried flashing tot file but flashing doesn't start as if device isn't detected by flash tool. It just shows flashing app as ready. Doesn't proceed further.

Don't know what to do to come out of Qualcomm mode as tab already has twrp and custom rom.
[G Pad 8.3 Android Development] roirraW "edor" ehT:
When reviving from QHSUSB_BULK 9008 mode, you have to use a very specific flashing method that's different than how you normally flash TOTs. I've done it many times successfully on my LG G3 VS985 when I had it - I don't recall if I ever had to on the tablet but it should be just as reliable to recover using the method. Here are a couple of links that may help. The procedure is the same or similar on any device: [FIX] Unbrick LG G2 stuck in Qualcomm HS-USB QDLoader 9008 mode and I know there was some helpful information in post # 442 in that thread. The instructions will say this, but to summarize, besides the specific steps to follow, you'll need the BoardDiag program and the QHSUSB_BULK 9008 mode driver that matches your Windows OS (usually 64-bit).

I don't remember any other details about it, but the forum thread at those links should tell you all you need, even if you might have to do some Googling to find the tool and driver (if they don't have working links to those). I don't recall if you need the .DLL that comes with the .TOT for this method, but I provide a separate link just for the .DLL along with the KDZs and TOTs I have up on Android File Host linked to in the first post.

Good luck!
[G Pad 8.3 Android Development] harpy.eagle:
Tks for the tips.

While experimenting with tab to revive it from Qualcomm 9008 mode... I tried removing battery terminals by opening back panel (which is serious pain and really hard to do). Kept on pressing power button while battery is disconnected, hoping all capacitor charge will be lost. Left the tab alone for some time and then tried connecting charger again to it. By doing it, it came out of Qualcomm mode and booted up fine.

It's like booting any other lg device in normal mode from Qualcomm 9008 mode. Just remove and fit back the battery after a while and power it on. But here with this tab, it's hell difficult to do with back cover so much hard to remove.

Problem is, my tab is going into Qualcomm mode every time it's made to restart. So God knows what can be done to access the battery so often. It's ridiculous how disgusting lg designs or manufactures their devices. I have lg g3 as well having exactly same problem. Booting into Qualcomm mode all the time.

It's extremely irritating. One can't even restart device or try to go into custom recovery to flash another rom or even let device power off with discharged battery because it's not certain whether device will boot back up normally. Most of the times it boots into Qualcomm mode only.
[G Pad 8.3 Android Development] Lostwon:
Hey yall, I sucessfully got android 9.0 via LineageOS 16 on this here tablet VK810 (Verizon G Pad 8.3)

I just used the 4.4.2 tot that above user supplied, then rooted with stump root (brute force)

Installed Busybox! (Sterricson)

Installed superuser via apk and upgrade binary.

Next I DD'd Twrp 2.8.7.0 and rebooted into recovery.

*Major edit*******

I might have installed LineagOS 14.1 between last step and next step :cautious:

sorry wish I remebered better

***********

In here I flashed Twrp 3.3.0. and restarted to recovery.

Finally I wiped everything but InternalSTRG/SDcardext

Flashed LineageOS 16.0

Reflashed twrp 3.3.0

Wiped Dalvik/Cache.

Rebooted into Android 9.

Only Build number that worked for 16.0 so far:

lineage_vk810-userdebug 9 PQ3A. 190705.003 1388 dev-keys

Added Gapps via twrp after first successfully booting LineageOS.

Thanks @Papay346

https://xdaforums.com/m/7370899/

For: VK81022B_00 .tot

MEGA

MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now

mega.nz

Unzip Password: lgbbs

Invisiblek has provided the romz : https://updater.invisiblek.org/vk810

I used LgFlashTool 1.8.6.527 (2014?) to flash:

Uninstall all LG programs and drivers

Uninstall all Verizon programs and divers

!!Restart computer!!!

Install both LG drivers and Verizon Drivers

LG_VZW_United_WHQL_v2.20.0.exe

drive.google.com

LGUnitedMobileDriver_S51MAN313AP22_ML_WHQL_Ver_3.13.2.exe

drive.google.com

!!RESTART Computer!!

Plug in tab in Download mode:

(While off hold Vol. up wile plugging in usb cord)

Open Device Manager and expand Ports (COM & LPT):

Under Ports look for either:

LGE AndroidNet for VZW USB Serial Port (COM X)

LGE Mobile for VZW USB Serial Port (COM X)

Open Properties ; Change tab to Port Settings:

Then click advanced entering port 41 for COM port.

!!RESTART Computer!!

Redo above steps with device manager to make sure it is at (COM41)

In LgFlashTool Root Directory put:

megalock.dll 7kb,

Web8064.dll 1,511kb

(Not sure you have to do next step)

??and UPPERCUT_1.0.0.0.exe 4,177kb??

(Not sure you have to do next step)

??Run UPPERCUT ignore box asking for model??

Without quitting UPPERCUT ie (without closing Model Select) then:

Run LGFlashtool.exe (2014 I think) :

In the Setting/Model Config menu toggle on Manual mode

Then set the DLL path to the location of Web8064.dll (ie c:\LgFlashTool\Web8064.dll)

Set the S/W path to location of the VK81022B_00.tot (ie c:\LgFlashTool\VK81022B_00 .tot)

Make sure Action Mode is set to Upgrade

Hit ok

Now hit yellow Start arrow at top left of LGFLASHTOOL

Now (if nothing starts) UNPLUG and REPLUG tablet to computer..... it will begin.
[G Pad 8.3 Android Development] Bobberino:
How did you unlock the bootloader? I have root, but have been completely unsuccessful for many days trying to get bootloader unlocked. ADB commands that all guides share (eg. adb devices, adb reboot bootloader etc) all just reboot stock bootloader with no option to enter fastboot...any help would be greatly appreciated.
[G Pad 8.3 Android Development] roirraW "edor" ehT:
Hi, and welcome to XDA.

The answer to this is that on the LG devices that I was familiar with (the LG G Pad 8.3 and LG G3) where we were able to root, we were never able to unlock the bootloader. Root was achieved by a vulnerability instead. The method to exploit that vulnerability was called Stump, and you can find my thread about that here:

[VK810.4G] [altev] most reliable way to root and install a custom recovery

Rooting VK810 official stock release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install...

xdaforums.com

Note that I have nothing to do with creating root methods, I only created some how-to guides, along with this repository thread.
[G Pad 8.3 Android Development] Bobberino:
Thank you for the reply. I guess I am not understanding how this user got TWRP and Lineage on to the pad without unlocking the bootloader.

I have root and used their methods up until 'dd twrp 2.8.7.0 and reboot into recovery' - all guides I see say to achieve this you need to unlock the bootloader...what am I missing?
[G Pad 8.3 Android Development] roirraW "edor" ehT:
You're welcome! Unfortunately, I can't be any help regarding Lineage because I've mostly broken this old tablet. I just wanted to clarify that the bootloader cannot be unlocked on these devices. Back then, we didn't have to unlock the booloader in order to root, the same as with my first Android device in 2010. Are you saying that the dd step in @Lostwon's instructions doesn't work for you at that point?
[G Pad 8.3 Android Development] Bobberino:
Since I last replied I soft bricked trying to put TWRP on to the pad. I just reflashed the provided .tot to downgrade to 4.4.2(?) and now brute forcing with stump root as I did earlier this week, so I will have root again shortly.

Thank you again for clarifying about the bootloader, as I have spent a lot of time looking for a solution and thinking I was doing something wrong!

Where I'm stuck is in Italics, original instructions in bold:

'Next I DD'd Twrp 2.8.7.0 and rebooted into recovery. <----- How was this accomplished, and do you know which version of 2.8.7.0 was used? They seem device specific and I can't find a generic 'v2.8.7.0' unless they just didn't specify V500 version, as TWRP site lists that as compatible. I have windows and linux machines running side by side in case that helps.

*Major edit*******

I might have installed LineagOS 14.1 between last step and next step :cautious:

sorry wish I remebered better <-------- I planned on installing 14.1 to be safe since this user most likely did this or they wouldn't be including it. Do you have a reliable guide for this process?

***********

In here I flashed Twrp 3.3.0. and restarted to recovery.

Finally I wiped everything but InternalSTRG/SDcardext

Flashed LineageOS 16.0

Reflashed twrp 3.3.0

Wiped Dalvik/Cache.

Rebooted into Android 9.' <------This all seems doable if I know how to do the former steps correctly, as I will be flashing a different TWRP and lineage version but I assume I will use similar if not the same methods?
[G Pad 8.3 Android Development] roirraW "edor" ehT:
You're welcome!

The thread I had linked has a link to this thread:

[Recovery] [vk810] [2015-07-05] TWRP 2.8.7.0

Install Instructions: You will need root. With custom recovery already installed. Download Place zip file on phone Reboot into recovery Flash zip file through recovery Reboot With stock recovery - Need ADB installed. Download zip file...

xdaforums.com

and it looks like the link to TWRP v2.8.7.0 for this device still works.

Sorry that I can't help with that or anything beyond. Back then, I had successfully flashed CyanogenMod/Lineage, but it's been way too long, and I never stayed on it. It doesn't look like that user has been on XDA since May 2023, either.

I wish I could help more, and I hope you succeed. By all means, if you feel like sharing your experience once you've either succeeded or if that eludes you, or possibly you might be able to write your own version of the instructions.
[G Pad 8.3 Android Development] Bobberino:
Great points and thank you for all your help!! I will continue to tinker and see what I come up with.
[G Pad 8.3 Android Development] Bobberino:
When following these instructions I get this error in adb terminal:

atform/msm_sdcc.1/by-name/recovery <

/dev/block/platform/msm_sdcc.1/by-name/recovery: write error: No space left on device

49153+0 records in

49152+0 records out

25165824 bytes transferred in 2.771 secs (9081856 bytes/sec)

It is stock with nothing added except SU app and busybox.

EDIT: I used a bloatware removal tool to take out 135mb of junk- Do you think it is safe to try the same instructions? Or should I still downgrade to 4.2.2?