yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 Original Android Development] pnin:
Hi. Just wanted to let you know that I upgraded the recovery on my V500 (still on stock V50020d) to the latest version here and everything seems to be working correctly -- I haven't tested it in any real situation, though.

As my recovery was seriously outdated (v2.8.0.0), I had first to use TWRP Manager to get a newer one which would allow me to flash IMaGe files. From there, I just flashed the awifi image linked from the OP and, after some nerve wrecking long wait (I already soft bricked this tablet once while trying to upgrade the recovery), I was able to boot into the new recovery.

So thanks for all your work, from another happy customer. :)
[G Pad 8.3 Original Android Development] jeremywh7:
From stock to 30a ROM in an hour(-ish)!

^^^'That App' [Rashr - Flash Tool] is what I used with the downloaded TWRP 2.8.7.1. Despite the warning, I first tried the TWRP Manager app see if it was up to date, but no go. So I downloaded it separately.

For completeness, what I did, from stock, was:

1. Download Stump Root v1.2.0 and install (Towelroot is another option...I had trouble downloading it)

Stump Root XDA Page

2. Run it; using the Brute Force method...takes 5-10min, then it as you reboot

3. Install Chainfire's latest SuperSU from Play Store, run it and let it install in Normal mode...takes 10-15sec. Reboot when prompted.

4. Install BusyBox (optional? My TWRP Manager attempt said to install the 'Stephen (Stericson)' version, but I did not; I used 'JRummy' instead.) Either way, run it to install Busybox. The JRummy app also verifies that you have root, and whether BB is already present and what version. The other one probably does too...?

5. Install Rashr - Flash Tool [link from fefifofum above], download latest V500 TWRP (or /palman for GPE)

6. Use Rashr's second option to install 'Recovery from Storage' and install TWRP, then select to reboot into recovery.

7. Here you get the message mentioned a few posts back about the Read/Write and System partition stuff. I did the slide to modify, installed skin1980's 30a ROM, let it wipe cache & davlik, then reboot. I got a message to install SuperSU here, which I used.

It all went without a hitch. Had to reinstall SuperSU yet again after it booted up, and obviously Busybox is gone again. Hope this helps!
[G Pad 8.3 Original Android Development] Cal:
Why isn't 2871 heading this thread? It is official TWRP now isn't it? Got it from the official site?

Things are extremely quick changing format...just wondering why not a lot of talk about format changes? :confused:
[G Pad 8.3 Original Android Development] fefifofum:
Latest official TWRP is 2.8.7.0. The fourth digit in the version is for device specific updates. The v500 model got an (official) update (2.8.7.1) to add F2FS support, but I think it's best to use TWRP version in the title of this thread instead of device specific updates. Remember this thread is also for palman and its latest version is 2.8.7.0.
[G Pad 8.3 Original Android Development] ravi_buz:
These methods dont seem to work on stock LP build. Is there a way i can get twrp on it so that i can try CM?
[G Pad 8.3 Original Android Development] fefifofum:
You need kitkat bootloader, as stated on the first post. Root, install kitkat bootloader, then install TWRP, after that you can flash any rom you want.
[G Pad 8.3 Original Android Development] ravi_buz:
Can I just install the kk bootloader directly when I am in lp? Don't want to downgrade and do the whole process again. I am rooted now
[G Pad 8.3 Original Android Development] Deltadroid:
You do not need to downgrade anything if you have root.

Flash the latest version of TWRP to your recovery and then boot into TWRP and flash the new bootloader.
[G Pad 8.3 Original Android Development] ravi_buz:
How? I installed the TWRP app and it dosnt seem to work. When i try to select the recovery it says i dont have permission to this folder, I downloaded the twrp from the website, and used the terminal and installed it but could never get into recovery. Used flasify to flash the img file and still could not enter recovery
[G Pad 8.3 Original Android Development] fefifofum:
You are probably using LP bootloader, which is not compatible with open bump. You need to install kitkat bootloader to be able to use custom recoveries and roms. You should dd the kitkat bootloader files or find another way to scape LP bootloader. If you properly install kitkat bootloader and official TWRP, you will surely be able to boot to recovery and flash any rom you want. If you can't solve the bootloader issue by yourself, ask in the bootloader thread and I will try to provide a method for those of you who installed LP bootloader.
[G Pad 8.3 Original Android Development] ravi_buz:
Agreed. dont want to mess this thread. Created my own thread in Q&A. Hope you can help

link - http://xdaforums.com/lg-g-pad-83/help/v500-how-to-install-twrp-stock-lp-t3165846
[G Pad 8.3 Original Android Development] neodraig:
How to boot into recovery ?

Hello,

I've installed TWRP with Flashify on my G Pad but I don't know how to boot into recovery and access TWRP.

I googled but I couldn't find an answer.

Could someone be kind enough to tell me how to boot into recovery (TWRP).

Thanks.
[G Pad 8.3 Original Android Development] pnin:
Look at the three dots menu in the top right corner of Flashify, e.g....
[G Pad 8.3 Original Android Development] neodraig:
Oh my bad. That's so obvious, why didn't I try that :eek:

Thanks a lot !!!
[G Pad 8.3 Original Android Development] Mennon:
I've recently updated twrp from a very outdated one (2.7.0.0) to 2.8.7.1, using Flashify. Right after the update, twrp worked just fine. I was even able to flash fefifofum's rom and I'm currently using it. But now, I can't boot to twrp again. Every time I try it, I get stuck in a black screen with the following words:

fastboot mode started

udc_start()

I thought I had bricked my tablet, but then I was able to reboot it through power button, and system was working fine. Problem is I can't access recovery anymore - every time I try it, i get stuck on same screen and have to reboot again. Any ideas on how to solve this?

Thanks.
[G Pad 8.3 Original Android Development] Deltadroid:
The v500 does not use fastboot, so maybe you accidentally flashed the palman recovery on your v500. I would recommend booting to system and using dd to flash twrp again.

Edit: here are some good instructions on how to manually fix the bootloader and recovery. http://xdaforums.com/showthread.php?p=62050593
[G Pad 8.3 Original Android Development] Mennon:
Thanks a lot, it seems to work just fine now.
[G Pad 8.3 Original Android Development] barnsbru:
Hi,

I am currently on stock V500-30A (Lollilop). Looking at TWRP install methods, they all seem to require root, which I don't have, being on stock.

Unfortunately, I cannot seem to find a way to root v500-30A on the forum, any guidance you could provide, or post you could link me to?

Thanks in advance.
[G Pad 8.3 Original Android Development] dbux:
Fastboot in LG-V500

[MENTION=4517918]fefifofum[/MENTION] I previously had TWRP with 2.8.6.0 running with Official CM 12.1 and I don't what bootloader I was in. Initially I rooted the device from the KitKat official stock ROM. And the I tried different ROMs including the Korean Lollipop Official stock ROM, flashed the .kdz. I don't know whether the bootloader changed with that. Finally somehow after problems with the Official CM 12.1, came to your's UNOFFICIAL CM 12.1 and this what I did,

Flashed the ROM.

Flashed kitkat bootloader.

Couldn't flash latest official TWRP (since I didn't know .img can be flashed through TWRP).

Rebooted to system.

[Noticed SuperSU is not in-built]

For flashing SuperSU tried rebooting to recovery (hoped TWRP 2.8.6.0 is still there).

What I saw was a blaxk screen with saying 'fastboot [something here]' at top.

Flashed the latest recovery with the fastboot command.

Done.

Maybe I will be able show you the same screen again but not much sure ;)
[G Pad 8.3 Original Android Development] Deltadroid:
CM already has built in superuser. No need to install SuperSU on any CM ROM. You must enable developer options to enable root.

Flashing that kdz probably changed the boot loader.
[G Pad 8.3 Original Android Development] dbux:
OK. That maybe the reason. Anyway I have the latest recovery now flashed through the fastboot. It showed this screen(refer attached pic). I chose modify. Hope everything is fine. Am I right?
[G Pad 8.3 Original Android Development] Deltadroid:
Yes, that is normal to show that screen on initial setup. It should be ok.

I was also not aware that fastboot works if recovery is unavailable. I learned something new.
[G Pad 8.3 Original Android Development] dbux:
So I guess changing the bootloader erases the recovery, right?

Anything useful for development with the fastboot?
[G Pad 8.3 Original Android Development] Deltadroid:
Changing the bootloader is separate from changing the recovery, but the kdz could change both.

Having fastboot is another way of recovering if the recovery doesn't work and you can't boot to the system.
[G Pad 8.3 Original Android Development] nsmart:
The above explains what happened to me last week. I was on stock V50020B rooted and wanted to install cm12.1. I had newest twrp 2.8.7.1 installed. After installing cm12.1 nightly, gapps, and V50020D Bootloader and rebooting I was in fastboot mode, no more recovery available. I could not reflash recovery through fastboot. I had to get back to stock V50020D with LGMobileTool and after that successfully repeated the steps to install cm12.1.
[G Pad 8.3 Original Android Development] dbux:
Flashing error!

I'm getting this error(refer pic) while flashing a ROM. Problem with the bootloader?
[G Pad 8.3 Original Android Development] Deltadroid:
It means the rom you are flashing is not bumped and it is trying to use loki. You have updated your firmware (aboot) that is not compatible with loki and requires a bumped rom and recovery.
[G Pad 8.3 Original Android Development] dbux:
Is there anyway to do it?
[G Pad 8.3 Original Android Development] Deltadroid:
Yes, install aboot from 4.2.2. Flash the zip below and your bootloader will be from kitkat and your aboot will be from jellybean. Now you can install older ROMs that are not bumped.

https://www.androidfilehost.com/?fid=23991606952613676
[G Pad 8.3 Original Android Development] dbux:
Don't know why I'm getting this error(refer pic attached), before and after flashing the boot loader you referred to. Thoughts?
[G Pad 8.3 Original Android Development] Deltadroid:
I think you should flash your recovery over again, but not use fastboot.

Use these instructions:

http://xdaforums.com/showthread.php?p=62050593
[G Pad 8.3 Original Android Development] dbux:
Please recheck the link.
[G Pad 8.3 Original Android Development] Deltadroid:
I had a paste malfunction :)

http://xdaforums.com/showthread.php?p=62050593
[G Pad 8.3 Original Android Development] dbux:
Thanks. Since I already have the bootloader you recommended. I think I can start from 5th step, isn't it?
[G Pad 8.3 Original Android Development] Deltadroid:
Yes.
[G Pad 8.3 Original Android Development] dbux:
Unfortunately I end up with fastboot mode, no recovery. Also I have the brightness problem with ROM after a boot. But becomes alright once turned the screen off and turning back again.
[G Pad 8.3 Original Android Development] Deltadroid:
Try going through all the steps in that procedure, not just starting from step #5. Make sure you are flashing the correct recovery for v500 and not for the palman.
[G Pad 8.3 Original Android Development] dbux:
I did everything in that post but now the device is stuck in fastboot mode, 'fastboot reboot' didn't work.
[G Pad 8.3 Original Android Development] Deltadroid:
You may need to start over and go back to stock with LG tool to fix this.
[G Pad 8.3 Original Android Development] dbux:
Yeah. That's the only way.
[G Pad 8.3 Original Android Development] dbux:
[MENTION=5227588]Deltadroid[/MENTION] Everything done but I still have the brightness issue. Should I try this[LINK: http://xdaforums.com/showthread.php?t=2719411 ] as said in this post[LINK: http://xdaforums.com/showpost.php?p=54078599&postcount=4 ]?
[G Pad 8.3 Original Android Development] redhk886:
links down for v500
[G Pad 8.3 Original Android Development] b0li:
I flashed stock 4.4.2 fw.

Am I on stock kk bootloader or it stayed lp bootloader (went something wrong, so i went back to stock).

Did not change any settings in lg flash tool.
[G Pad 8.3 Original Android Development] GXGOW:
For some reason I am not able to enter recovery anymore since yesterday. It's been working fine before, but now I'm just getting stuck at the TWRP splash screen. Reflashing it through the dd terminal command didn't work. Any idea guys?

Btw I'm talking about the V500 variant of the G Pad.

Sent from my OPO running Sultanxda's CM 12.1
[G Pad 8.3 Original Android Development] fefifofum:
I'm not sure I understand your post. Is that a question? In case you don't know what bootloader you have currently installed, you can always flash again the kitkat bootloader to be sure.

If you have adb access, you can view the recovery log with this comand:

adb shell cat /tmp/recovery.log

And then upload the log so we can find the problem. It's possible that some partition (or the external sdcard) is causing that issue.
[G Pad 8.3 Original Android Development] Deltadroid:
I've noticed that the recovery will load much faster after a factory reset.
[G Pad 8.3 Original Android Development] GXGOW:
Thanks for the reply! I will upload the log tomorrow. Haven't had time to do that today, unfortunately.

That's pretty hard when I can't enter recovery to perform a factory reset ?

Sent from my OPO running Sultanxda's CM 12.1
[G Pad 8.3 Original Android Development] Deltadroid:
Try deleting the TWRP directory on your internal sdcard.

You could also try flashing cyanogen recovery.
[G Pad 8.3 Original Android Development] fefifofum:
I agree that deleting the contents of the TWRP directory (except the BACKUP folder) on the internal (or external) sdcard could be a possible fix for the problem. Installing cyanogen recovery is a very bad fix... ;)
[G Pad 8.3 Original Android Development] GXGOW:
Unfortunately, deleting the TWRP directories did not work. However, I've tried to install version 2.8.6.0 and then I managed to get back into recovery. It couldn't read my internal storage because it's formatted to f2fs, but it's something already. Maybe it has something to do with my issue.

EDIT: I've managed to get the latest recovery working again by reformatting /system, /cache and /data to EXT4. It's not one of the best solutions, but it did work. Thanks for the help guys!

Sent from my OPO running Sultanxda's CM 12.1
[G Pad 8.3 Original Android Development] Nike2:
I had the same problem - stuck at the TWRP splash screen. That happened after installing fefifofum's CM12.1 update from 2015/09/11. Everything was working before that. Changelog says "F2FS updates" so maybe that's the reason. Anyway, I fixed it by flashing twrp-2.8.7.0, formatted /cache and /data back to ext4. Then flashed twrp-2.8.7.1 and reformatted /data and /cache to f2fs. Then installed the last update of fefifofum's CM12.1.
[G Pad 8.3 Original Android Development] Deltadroid:
[MENTION=4517918]fefifofum[/MENTION]

Factory reset is not formatting /external_sd/.android_secure. This creates empty container error messages after installing a clean rom and can cause the package maintainer to load orphaned data.
[G Pad 8.3 Original Android Development] fefifofum:
EDIT: read two posts below.
[G Pad 8.3 Original Android Development] Deltadroid:
CWM formats .android_secure during a factory reset.

Why would TWRP want to keep a stale android_secure if data has been wiped?
[G Pad 8.3 Original Android Development] fishears:
"A factory reset will also wipe sd-ext and android_secure if your device has those items." from TWRP FAQ
[G Pad 8.3 Original Android Development] Deltadroid:
Thanks. so then there must be a bug with the factory reset if it is not being wiped properly.
[G Pad 8.3 Original Android Development] fefifofum:
I thought a factory reset didn't wipe android_secure, if it's supposed to and it's not working I will look at it when I have some time. Thanks [MENTION=3325155]fishears[/MENTION] for that link.
[G Pad 8.3 Original Android Development] stbxxl:
A few days ago I updated TWRP on my v500 from v2.7.0.1 to v2.8.7.1 in order to do a clean install of fefifofum's unofficial CM12.1 ROM (incl. the V50020D bootloader). I was able to do nandroid backup and the flashing went smoothley. I'm enjoying Lollipop.

However, I now have a problem with booting into recovery. Every time I try to boot into it I get only black screen with the message "fastboot mode started udc_start()" displayed. After pressing the power button for a few seconds the message disappears. After that I can do a normal boot into CM12.1 by pressing the power button again.

I'd appreciate any recommendations how this can be fixed?

Thanks.
[G Pad 8.3 Original Android Development] Cluey:
Given this is the recovery thread I think this is the right place to ask.

Could you guys give me a history lesson on this device and the different versions of recovery you've had to use please?

I've read lots of the threads here but there is no Sticky post summarising things like other device forums I've used.

This is my understanding so far.

Initially you had to take advantage of the Loki exploit to get root and custom recovery.

Later this became obsolete because of Bump. I don't know if that was because of the official ROM update to 4.4.2 or not.

There were different brightness level settings depending on which bootloader your device had and which version of recovery you were using.

The awifi has no Fastboot.

Which bootloader do I want for running recent custom ROMs? Do we still have to swap between them?

Now as far as we can tell the awifi and palman devices are the same but due to partition table differences converting to palman results in WiFi not working properly. So far nobody has been able to do this but the current hypothesis is that this should work. [MENTION=5143648]muiriddin[/MENTION] tried but ended up in a QHSUSB_DLOAD situation and hasn't replied about fixing it for a while.

Is there shell access we can use to re-partition the device to the same as palman or is this missing without Fastboot?

Is there a way of getting into QHSUSB_DLOAD mode without opening the device up and shorting the right capacitors like they did in the G2 thread?
[G Pad 8.3 Original Android Development] fefifofum:
Open bump is better than Loki because it works in jellybean and kitkat bootloaders (as opposed to Loki, that only works in jellybean bootloader), and because with Loki you get a warning when you boot the device (I already forgotten exactly what it said, but it did not look too good). Jellybean bootloader has a bug when you rebooted the device with usb connected, and has different backlight settings than kitkat/lollipop bootloaders (and stock roms). To match the backlight settings you need a change in the kernel, and that affects the rom and recovery. Once we found open bump, which supports kitkat bootloader, there was no reason to stay on jellybean bootloader anymore, so all kernels could adapt to kitkat/lollipop backlight and forget about all this mess.

That's why most custom roms/kernels are now adapted to open bump and kitkat bootloader backlight, so I don't think you need to switch bootloaders anymore (unless you want to use an outdated rom). You can flash V50020B bootloader from this thread, it will work with most updated roms (aosp, official and unofficial cm-12.1, slimrom, stock LG kk and lp, ...). I didn't look into the new v50020F bootloader (yet), but it will probably be the same as V50020B.

About recovery, with each twrp version we had different builds from different users, so I thought it would be best to submit the code to twrp so we have official updates and everybody can contribute there. I don't know what other recoveries users had in the past, but I think right now the best option is to use latest official twrp build. Lastly, awifi has fastboot, but it is only accessible if you erase recovery partition and then reboot to recovery (that's in V50020B bootloader). I didn't mess much with it, but I think it's quite limited due to our locked bootloader. I don't know if it could be used to repartition the device and flash palman backup partition images.
[G Pad 8.3 Original Android Development] Cluey:
Thanks for that mate.

Sounds like the Loki warning is similar to the unlocked bootloader warning the Motorola devices show on boot, or the Samsung triangle one which prompted Chainfire to make a mod to hide it.

I ended up putting TWRP 2.8.7.0 as I detailed here.

I've got no idea which bootloader is on it now, I'm not sure if that got changed with what I've done so far. I need to learn some more I think.

I take it we can't unlock the bootloader on this?

I know with the other devices I've got/had they could be unlocked, both the Sony and Motorola ones involved getting a key from their websites. I assume they do that so they can look up if you've unlocked it if you send it back for a warranty claim.

I'm assuming LG haven't got this feature (yet?). So is there a way of unlocking it with an exploit?

Removing the recovery partition to access Fastboot sounds a bit drastic!

How much can we do in download mode using that send_command.exe or using the LG Flash Tool 2014 which is floating around?

I'm not sure if you've used Samsung devices in the past but they have a similar program, Odin, which lets you flash things in download mode. At least I think it was download mode, I'm going from memory here and haven't had to use it for a while now.

I'll keep an eye out for another tablet for experimenting, even one with a cracked screen would work for testing this sort of stuff.
[G Pad 8.3 Original Android Development] mafiaboy:
Hi , i have now 4.4.2 rooted in my tablet. I will sell my tablet and i want to unroot it and leave 4.4.2 or return back to custom unrooted 4.2.2 rom.

I have download from here *.kdz file, but i cannot find a tutorial to install this file. How can i install kdz file please?
[G Pad 8.3 Original Android Development] youngsta2010:
http://xdaforums.com/showthread.php?t=2622777
[G Pad 8.3 Original Android Development] stbxxl:
I'm still looking for a solution to this issue since I haven't found one. Without being able booting into recovery I can't apply and updates anymore.

Thanks!
[G Pad 8.3 Original Android Development] fefifofum:
Your recovery is gone, that's why it reboots to fastboot. You need to flash the recovery.img again, you can use THIS APP or use the dd install method metioned here. Also, double check if you enabled by accident the option to update recovery in developer settings.
[G Pad 8.3 Original Android Development] stbxxl:
I'm back in business! Using the dd install method I was able to restore recovery, create a Nandroid backup, and flash your latest CM12.1 ROM. I also checked Developer Settings and recovery auto-update was disabled.

Thank you very much for your help.

Cheers!
[G Pad 8.3 Original Android Development] ledabe974:
Hi,

Where can I find boot.img ?

Thanks
[G Pad 8.3 Original Android Development] Deltadroid:
The boot.img is your kernel. Although, you must use a boot.img that is included with the rom you are using.
[G Pad 8.3 Original Android Development] ledabe974:
Of course

I give it a try.

Hope it solve the rebooting issue in recovery.

It's doesn't work for me.

TWRP don't reboot in recovery or system.

It's working with 2.8.6.0 but not with 2.8.7.X. What can I do now ?
[G Pad 8.3 Original Android Development] GXGOW:
There's still some kind of issue with f2fs and the latest TWRP version (2.8.7.1). I flashed CM 13 a few weeks ago (it supports f2fs) and everything was working fine, until today. I can't boot into TWRP anymore. I only get stuck at the splash screen for a few seconds before the device reboots itself.

I am able to boot into recovery with the preview version (2.8.7.0) installed, however, this one doesn't support f2fs.

Has anyone else experienced this issue and found a way to fix it?

Sent from my LG-V500 running CM 13