yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 Android Development] Deltadroid:
[MENTION=4517918]jsevi83[/MENTION] I understand why you separated out the recovery from the base packages, but why did you remove modem.img and persist.img? Was there a compatibility problem with certain devices using the these files?

Best Regards.
[G Pad 8.3 Android Development] HTC Tytn user 188:
Today i installed this: http://xdaforums.com/lg-g-pad-83/development/rom-android-5-0-lollipop-lrx21m-t2941207 and im having Brightness problem (its too bright). I have CWM recovery http://xdaforums.com/lg-g-pad-83/orig-development/recovery-t2945917 installed to my tablet. I red this tread but i still didint figure out what i need to do to fix it. Im propably going to stay with this rom and kernel. If i understand right i need just to download one zip and install it in recovery to fix this problem?

Question is which one i need to download/upgrade. If it matters i had to downgrade my tablet from 20D to install this recovery when i got tablet couple of weeks ago.
[G Pad 8.3 Android Development] Deltadroid:
If you install one of these zip files in this post, it will replace your aboot partition. That means that you MUST reinstall your recovery AND your kernel BEFORE you try to reboot into the normal operating system.

I have just compared the firmware bases found in this thread with the European firmware bases using a binary diff tool and there appear to be many differences in the files between the two regions.

The firmware bases in this thread appear to be created from US ROMS and I wanted to upgrade my firmware, but I wanted to upgrade with the euro version (Great Britain). I will post my firmware update package to 4.4.2 using 20B from GB region.
[G Pad 8.3 Android Development] HTC Tytn user 188:
Ok, thanks alot. I will wait for it :) Does my brightness problem get fixed if i downgrade back to some custom 4.4.x rom while waiting or will that take long time to make?
[G Pad 8.3 Android Development] Deltadroid:
V500-4.4.2-Base-KOT49I.V50020B_GB

I've created two different packages for updating to 4.4.2 firmware base (GB version).

The first package will update all of your partitions to 4.4.2, except it will not change your current aboot and custom recovery. Since aboot is not changed, that means you can install this package and reboot directly into the operating system without having to reinstall the recovery and kernel (boot) partitions.

Recommened method: V500-4.4.2-Base-KOT49I.V50020B_GB-no-aboot-signed.zip

The second (alternate) firmware installation package will update all of your partitions to 4.4.2, except, it will also update your aboot partition to version 10A. If your previous version of aboot was not 10A, then you will need to also flash the recovery and kernel (boot partition) directly after flashing this firmware update package. Do not directly reboot into the operating system without flashing your recovery and kernel (or custom rom) right after flashing this firmware update package.

Alternate method to update aboot to version 10A: V500-4.4.2-Base-KOT49I.V50020B_GB-signed.zip

Note: I suggest that you use the "no aboot" option because it does not change your aboot which means you dont have to worry about reinstalling your current recovery and kernel. I have just included an alternate installation to follow the same installation procedure as the OP intended. The version of aboot that is included in this alternate procedure is the same version of aboot used by the firmware update packages in the OP. AFAIK, there is no real good reason to update the aboot partition to 10A if you already have a working aboot/custom recovery installed.

Note #2: If you are currently using TWRP, then you will need to choose a version that supports the 4.4.2 bootloader (or else you will have brightness problems in the recovery). If you are currently using CWM 6.0.5.1, then the recovery will not have any brightness problems with any firmware bases.
[G Pad 8.3 Android Development] Deltadroid:
I misunderstood.

Since you installed stock 20D ROM, then your firmware base is now 4.4.2. If you want to use official CM 11 with a stock kernel, then you will need the 4.2.2 firmware base files to be installed. So, all you need to do is install the 4.2.2 firmware base, then flash a compatible recovery , then flash cm 11 ROM, then reboot into CM 11.
[G Pad 8.3 Android Development] Deltadroid:
I just checked with diff tool and the 4.2.2 firmware on the OP is from JDQ39B.V50010A_US and the 4.4.2 firmware on the OP is from KOT49I.V50020B_US. So, they are actually 10A (US) and 20B (US).

Maybe I should make 4.2.2 10C and 4.4.2 20D firmware update packages also. I know that 10A has some bugs in the firmware that are fixed with 10C and I'm pretty sure there are also bugfixes in 20D when you compare it to 20B.

Edit:

Here is a link for 20D (US) base firmware package. Please report back any findings. This package will not overwrite the currently installed aboot/recovery partitions, so your custom recovery and kernel will remain functional.

V500-4.4.2-Base-KOT49I.V50020D_US-no-aboot-signed.zip

Credits: [MENTION=4517918]jsevi83[/MENTION] [MENTION=4557482]Drgravy[/MENTION] [MENTION=3210378]id10terror[/MENTION]

Thanks, I'm using this 20D US firmware on my v500 that originally came with European firmware and it's working just fine with red kernel and mani kernel. I'm just really curious what Linux or Windows tools are available that are compatible with v500 kdz files. I would not have been able to extract the files without [MENTION=4557482]Drgravy[/MENTION] and [MENTION=3210378]id10terror[/MENTION] ROMS on android file host.
[G Pad 8.3 Android Development] Schrotty35:
Can you make 10b and 20d europe?
[G Pad 8.3 Android Development] Deltadroid:
I'm trying to figure out what tools are necessary to extract an official kdz file for v500. All of the Windows and Linux based kdz extraction tools don't seem to support the v500 kdz files.

I'm also trying to find a larger v500 kdz repo for more regions.
[G Pad 8.3 Android Development] Schrotty35:
Which base i need for cm12?
[G Pad 8.3 Android Development] Deltadroid:
Official cm 12 default kernel uses 4.2.2 base.
[G Pad 8.3 Android Development] Deltadroid:
I've realized after lots of testing that every time you change your firmware and bootloader, you must reformat the sdcard. Even if you are changing from 20B to 20D, the SD card must still be reformatted or else the card starts to act really weird and slow.

This is why everyone started having problems when the new 4.4.2 bootloader was released. They probably updated the bootloader but did not reformat their sdcard.

Edit: It seems that switching firmware bases does not always mean you need to reformat the sdcard. I would only recommend reformatting if you start to have lockups when reading or writing to the sdcard.
[G Pad 8.3 Android Development] Darkmasterhk:
nice to know^^

i was actually wondering, why my sdcard problem got so much worser after changing between your bases.

so... lets see if 20d works better.

Thanks for your work.
[G Pad 8.3 Android Development] tekka-maki:
Am I the only one on slimkat official (latest weekly) & 4.2.2 base who cannot select ART run time? It's there in developer options of course, but it always defaults back to davlik upon reboot.
[G Pad 8.3 Android Development] slebit:
Do you have xposed installed?
[G Pad 8.3 Android Development] tekka-maki:
Yes, I didn't know that it was incompatible. Possibly that's causing DAVLIK to sort of take over. Interesting, I would think runtime would just change to ART once selected/reboot, then Xposed would be broke. But now that I know, hmmm... that's a tough one; I have 1 or 2 modules i really depend on, mainly xinternalsd, the rest i could do w/o but those pesky obb files...:confused:

---------- Post added at 10:46 AM ---------- Previous post was at 09:52 AM ----------

so... currently on 4.2.2 base; slimkat official 4.4.4, redkernel 110. should i upgrade to that 20D?
[G Pad 8.3 Android Development] Deltadroid:
Double post.
[G Pad 8.3 Android Development] tekka-maki:
so... currently on 4.2.2 base; slimkat official 4.4.4, redkernel 110. should i upgrade to that 20D? also, you say it doesn't touch recovery, but if coming from 4.2.2 base, i assume TWRP 2.8.1.0 for 4.4.2 Base is still prudent after base flash? thank you
[G Pad 8.3 Android Development] Deltadroid:
If you are using red kernel, then updating to 20D (or any 4.4.2 base) will fix any brightness issues you might be experiencing with that kernel.

Edit: If you use TWRP, then you need a version of it compiled for 4.4.2 also. If you use CWM, then the recovery is unaffected by the brightness issue.

Edit: I also wanted to mention that switching firmware bases does not always mean you need to reformat the sdcard. I would only recommend doing that if you start to have lockups when reading or writing to the sdcard.
[G Pad 8.3 Android Development] fefifofum:
OP updated with new details and info.
[G Pad 8.3 Android Development] Deltadroid:
Are you saying that Bump will work with an aboot from 4.4.2 so users don't need to downgrade aboot anymore?
[G Pad 8.3 Android Development] fefifofum:
Yes.
[G Pad 8.3 Android Development] Deltadroid:
[MENTION=4517918]jsevi83[/MENTION]

Since lg released an official lollipop update, maybe we could use the new bootloader. Although, the 4.4.2 or 4.2.2 aboot is needed since lg changed the keys to stop open bump.
[G Pad 8.3 Android Development] fefifofum:
I have it (I extracted the korean 30A), but didn't test it. Anyway, I don't think it brings many advantages, it uses the same backlight setting than kitkat bootloader, so from my point of view our best option at the moment is staying in kitkat bootloader and use open bump.
[G Pad 8.3 Android Development] Deltadroid:
Open Bump functionality depends on the version aboot, right? Could we not use the lollipop bootloader and the kitkat aboot with open bump? Just like when we downgraded aboot before when loki only worked with the 4.2.2 aboot.
[G Pad 8.3 Android Development] fefifofum:
I added to the first post a flashable zip with v510 bootloader. It is untested, and it could brick our v500, but if it works we would have an unlocked bootloader like the GPE. If someone is willing to test it, let us know how it goes.
[G Pad 8.3 Android Development] Deltadroid:
Tempting. :)

What are the hardware differences between v500 and v510?
[G Pad 8.3 Android Development] muiriddin:
I'd start with someone running cpuz on both a v500 and v510 and comparing the output. I'd pay particular attention to the bluetooth and wifi chipset since in past attempts this is what often broke and may be a clue as to where some differences may lie...

When I get home I'll see if I can get the v500 info posted here, I don't however have a v510...
[G Pad 8.3 Android Development] fefifofum:
I think wifi and bluetooth differences might be related to the bootloader and the way it uses the persist partition. The other main difference between v500 and v510 is the partition table. Everything else should be the same, so now we only need to confirm if v510 bootloader works in v500. I would test it myself, as I did in the past with the bootloader flashable zips we have in the first post, but right now I really need my gpad fully working and cannot take any risks.
[G Pad 8.3 Android Development] muiriddin:
So the .zip file you have here, only writes the contents from the V510 into the 6 relevant partitions it does not repartition the device itself to match the partition table of a v510?

The key thing I'm wondering here, is how is download mode activated for the LG tool to work(since that is how we can get back to stock) and do these partitions affect the ability to get into download mode? I only have rudimentary knowledge of the android boot process so bear with me here... Or is this enough such that fastboot would potentially work? If I try this, I'm trying to understand what my recovery options might be...
[G Pad 8.3 Android Development] fefifofum:
I don't really know what recovery options we would have in case this doesn't work. I don't think there is download mode in v510 bootloader, but there is fastboot. In case this works we wouldn't need LG tool anymore, since we could extract the partitions from the KDZ file and directy flash them without any special software.
[G Pad 8.3 Android Development] muiriddin:
So a win would be working fastboot, a lose would potentially be a brick since we have no idea if we could get the device back to a state in which we could flash things back again...
[G Pad 8.3 Android Development] fefifofum:
I've been doing some tests with v510 kernel on v500. The only thing that doesn't work is wifi, and it's because the mac address is stored in persist partition on v510. Bluetooth and everything else works good. So the main difference between v500 and v510 is the partition table, which affects where the wifi stores the mac address.

I would say the main benefit is unlocked bootloader, and fastboot comes with it. :D

Something else that I just found out is that the backlight of v510 bootloader is exactly the same of v500 jellybean bootloader, so now I'm more convinced that our bootloaders can be exchanged without issues.
[G Pad 8.3 Android Development] muiriddin:
For science! Types reboot recovery...

I have a QHSUSB_DLOAD brick

I do not suggest anyone else tries this...
[G Pad 8.3 Android Development] fefifofum:
I'm sorry for the brick. I'll try to find something to help you out. Link removed from first post.
[G Pad 8.3 Android Development] muiriddin:
Going slowly about recovering this thing... I am currently doing a lot of reading about others who have recovered from a similar situation to gain a better understanding of what is involved. If I manage to recover my V500 from this, I will post a step by step process of what I did. This process may also lead to a V510 conversion process since understanding things at an extremely low level for the V500 may give us more information...
[G Pad 8.3 Android Development] Deltadroid:
KOT49I.V50020D_US Bootloader/firmware with updated aboot

Since Open Bump became available, the 20D 4.4.2 firmware for the v500 can be fully upgraded (including aboot). Upgrading aboot to 20D 4.4.2 was not possible when we were using Loki based recoveries and kernels. Provided below is a flashable zip to update aboot, bootloader, modem, and persist partitions to 20D 4.4.2. No more having to downgrade aboot to 4.2.2 when using a 4.4.2 bootloader. :)

WARNING: This package REQUIRES that your device already has a bumped ROM/kernel AND bumped recovery installed BEFORE installing this firmware package. This installation package will update aboot to a version that is ONLY compatible with bumped recovieries and kernels.

This zip is to provide a complete 20D 4.4.2 firmware package since we dont have to downgrade aboot anymore when using 4.4.2 firmware/bootloader.

V500-4.4.2-Base-KOT49I.V50020D_US-signed.zip

Note: this package is the same as the 4.4.2 20D "no aboot" version, except it also includes aboot from 4.4.2.
[G Pad 8.3 Android Development] 0nebukadnezar0:
Hi Deltadroid, thx very much for your work. How can we determine a bumped ROM/Kernel from a non bumped? I'm on the latest CM12.1 nightlies, Redkernel RXXX test release (avoid black screen issue) and if I'm not wrong, TWRP 2.8.0.1
[G Pad 8.3 Android Development] Deltadroid:
The latest cm 12.1 nightly is bumped which provides a bumped kernel. Also, there is a bumped version of twrp provided in this forum (no loki needed).

http://xdaforums.com/showthread.php?t=3074758

You can tell the kernel and recovery are bumped when you boot into the system and the recovery and don't see the secure boot error message.

I must also caution you that updating aboot to 4.4.2 requires the install scripts of older non-bumped custom kernels to be changed to not use loki or the custom kernel will fail to install (ie; red kernel #15 needs to have it's installation script updated to work correctly with an updated aboot). The new versions of red kernel are bumped so they are fine to use with an updated 4.4.2 aboot.
[G Pad 8.3 Android Development] fefifofum:
First post rewritten, I added a "pure" kitkat bootloader and detailed instructions. I hope now it's clear for everyone.
[G Pad 8.3 Android Development] 0nebukadnezar0:
Thousand thanks, you gave my gpad a new life. After updated aboot, my gpad is running as expected, with no lag after power on WLAN, very smooth and quick responsive. But a question, do I have to update aboot each time I update the CM ROM?
[G Pad 8.3 Android Development] Deltadroid:
No. Just once.
[G Pad 8.3 Android Development] muiriddin:
Okay more information on my brick.

After detective work with linux It is in QHSUSB_Dload 9008 mode.

Info from log when connecting it looks like this:

Jun 6 09:45:48 mw kernel: [600403.032714] usb 5-1.1: new high-speed USB device number 7 using ehci-pci

Jun 6 09:45:49 mw kernel: [600403.125265] usb 5-1.1: New USB device found, idVendor=05c6, idProduct=9008

Jun 6 09:45:49 mw kernel: [600403.125270] usb 5-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

Jun 6 09:45:49 mw kernel: [600403.125272] usb 5-1.1: Product: QHSUSB_DLOAD

Jun 6 09:45:49 mw kernel: [600403.125274] usb 5-1.1: Manufacturer: Qualcomm CDMA Technologies MSM

Jun 6 09:45:49 mw kernel: [600403.125690] qcserial 5-1.1:1.0: Qualcomm USB modem converter detected

Jun 6 09:45:49 mw kernel: [600403.125881] usb 5-1.1: Qualcomm USB modem converter now attached to ttyUSB0

I have found some threads on people who have brought a device back from 9008 mode.

Just thought I would give you all an update...
[G Pad 8.3 Android Development] wayne2001:
GET error from zip install

Mod Edit: Quote of first post unnecessary...removed

I get error after running the 50020d it states: Finding update package...

Opening update package ...

Verifying update package...

E: footer is wrong

E:signature verification failed

Installation aborted

I am bricked and loop hell , this is me begging :crying

Cyanogen Recovery loop, I can get into hard reset but I still in up in the loop
[G Pad 8.3 Android Development] tmihai20:
[MENTION=4039786]wayne2001[/MENTION]: Try disabling md5 check (or signature check) in Recovery. Go to Settings and disable it. Most of the Recovery flashable zips are not signed nor do they have any checksum available. When does that message appear? What were you trying to do?
[G Pad 8.3 Android Development] Deltadroid:
Turn off the gpad. Press volume down and power button until LG logo shows up, then wait half a second, release both buttons, then quickly press all three buttons at the same time (volume up, volume down and power). The factory reset menu should show up, and pressing the power button a couple of times should send you to recovery.
[G Pad 8.3 Android Development] Cluey:
Did you get any further with this?

It would be interesting to try and work out the differences between the partitions and sizes between the V500 and V510 to see if [MENTION=4517918]fefifofum[/MENTION] hypothesis is correct.

I know I'm months late to this but I only recently got one.
[G Pad 8.3 Android Development] fefifofum:
Partition table is very different, and v510 bootloader doesn't work in v500. I guess we would need to flash the partition table from v510 and all partitions, but that is a very risky procedure. It would be easy to test, and I have all the files needed, but chances are it won't work and brick the device.
[G Pad 8.3 Android Development] fefifofum:
KitKat bootloader updated

KitKat bootloader updated to V50020F. I think it's the same as V50020D, but just in case someone want to have the latest. I installed it and everything went fine.
[G Pad 8.3 Android Development] Deltadroid:
[MENTION=4517918]fefifofum[/MENTION]

Are the modem and persist partitions not mounted any more?

I usually included those two extra images in the firmware package with the bootloader.

Edit:

I flashed 20F and everything is good. Thanks for that!
[G Pad 8.3 Android Development] fefifofum:
It depends on the rom if they are mounted or not. /persist is always mounted, but the persist.img doesn't contain anything useful (just empty folders), and those are already created from the ramdisk. Modem (firmware) partition is mounted on some roms, but they don't necessarily expect kitkat firmware files. My builds of cm-12.1 and cm-13.0 already include the firmware files in /system (where we have plenty of space), so we don't rely on modem partition and we don't mount it. Other popular custom roms like adriano's aosp-6.0 builds and infected's slimrom lp builds use my repos as a base, so they don't need the modem partition either.

Also, most custom roms that use the firmware files in modem partition are based on cm (outdated) repos, so they probably expect jellybean firmware. And custom roms based on lg stock lp expect lp firmware files. What I'm trying to say is that kitkat firmware files contained in the modem.img are probably not ideal for any custom rom (only those based on lg stock kk), and they are not dependant on the bootloader, so there is no need to include them.
[Xperia Arc Q&A, Help & Troubleshooting] DizXDA83:
Hi there! Like many of us here i've come to realise that the 380mb of internal storage of my Arc S is insuficient!

So i've decided to try and partition my 16GB Sd card!

I've made a research and followed one of several guides here, basically, partition my sd on a FAT 32 partition and the other one Ext4 via MiniTools and then use Link2SD to move apps to SD Card!

I've unlocked bootloader and i was on a ICS Rom! But i decided to wipe it out and give a try some KitKat Roms like Carbon, CM11, Dark CM and others on Android Development Section and give it a try on Partition my SD!

The main problem here is that i'am having problems in maintaining the Ext 4 partition!

I leave 12GB to Fat32 and the other 4 on Ext4 partition! The problem is that in some roms, the memory is recognized and in internal memory it shows up 3 or 4 GB!

But after a few days of usage, and in 3 or 4 roms i've tried, i begin to experience random reboots and at some point the phone wont boot!! And i've have to do the all thing again!

On other Roms, i make the Ext partition but on phone it shows me internal memory 380MB free and not the 3 or 4 GB! I mean on Link2SD the 2nd partition shows up (on /data/sdext2) but not as internal memory!

What am i doing wrong here? I've even tried 2 and 3 Ext partitions! The results the same! Some times it works, other it doesn't! Am i giving too much GB to ext? I've tried with 2, 3 , 4GB and the same happens!

Is there any problem with KitKat roms and Arc S on this matter? I'am beginig to think on getting back to ICS!

Thanks!
[Xperia Arc Q&A, Help & Troubleshooting] Someguyfromhell:
I used 16GB memory card as well and also made 4GB Ext4 partition. I used Link2SD and never occurred a problem.

Did you use any other scripts in addition to Link2SD? I didn't check the internal memory in Settings that much, but I can't remember having seen more than 420MB in the settings.
[Xperia Arc Q&A, Help & Troubleshooting] DizXDA83:
but the objective here isn't that internal memory stays "linked" to the ext partition? becouse it did happen after i finish the process to check internal memory and showing up has 3 or 4GB.

Becouse otherwise whats the point of ext partition? And then, with only 420mb showing up i try install several apps, move them to sd card, and even then there's always some data that stays on internal and fills up quickly the 420mb!