yashsingh1/xdaforums huggingface dataset:
[Xperia Z Android Development] Rajeev:
VARIOUS ADD-ONS PACK

(1) SMALL DPI NAVIGATION BAR ( SOFTKEYS ) MODS

Please DON'T Use This Small DPI In OTA v2

28 DPI SMALL NAVIGATION BAR MOD

32 DPI SMALL NAVIGATION BAR MOD

36 DPI SMALL NAVIGATION BAR MOD

40 DPI SMALL NAVIGATION BAR MOD

48 DPI STOCK NAVIGATION BAR MOD

INSTRUCTIONS

Download and Copy The Zip To Ur Internal Memory ( Not in SD Card 1) It Must Be In SD Card 0

Power Off and Enter Recovery

Important :- Go To Mount and Storage and Then Mount System ( Other Wise It Won't Work )

Flash Zip

Wipe Cache and Dalvik Cache

Reboot

Done...

(2) DEFAULT 4.4.2 STOCK THEME

http://d-h.st/Aq4 ( Thanks To @Pandemic For Uploading )

(3) OLD STYLE SYSTEMUI TOGGLES

SCREEN

DOWNLOAD ( Mount System and Then Flash )

CREDITS

| RyokoN |
[Xperia Z Android Development] nino2603:
Download & try(TOMORROW)
[Xperia Z Android Development] bruce1x:
Same... looking forward to this as I hate he white:D
[Xperia Z Android Development] diaboliku123:
At least give us some screenshots!
[Xperia Z Android Development] Thugscub:
Awesome, cant wait...

Happy Birthday Rajeev.
[Xperia Z Android Development] Rajeev:
Can't Upload SS via Tapatalk... SS will update Tomorrow.. Sorry My Friend
[Xperia Z Android Development] nhoc_huhu:
Wait.....i love black version
[Xperia Z Android Development] deanz93:
please make it for white version also..
[Xperia Z Android Development] Rajeev:
For White version awsomm eXistenZ will come soon.. And there is already a Deodexed Rom with White Apks..
[Xperia Z Android Development] MattJaO3D:
Awesome, thanks [MENTION=4970751]Rajeev[/MENTION] love the black :D
[Xperia Z Android Development] ikentoy:
I hope this will be compatible with Xperia ZL.. :(
[Xperia Z Android Development] vkass:
Damn you!

Saw the thread name, pulled out the usb cable from my bag and connected to the pc.

Scrolled down and what do I see? TOMORROW!

:p

Thanks for the black edition, I missed it so much..
[Xperia Z Android Development] Rajeev:
Haaaaaa haaaa.. I like that buddy
[Xperia Z Android Development] Rajeev:
For ZL also.. After This
[Xperia Z Android Development] deanz93:
deodexed rom dont has many modded..or you can please make flashable zip mod for me?

:crying: :D
[Xperia Z Android Development] Rajeev:
:p:p:p:p

What Mod U Need For White Deodexed ROM Buddy ;) ?
[Xperia Z Android Development] izukamikain:
hi [MENTION=4970751]Rajeev[/MENTION] thanks for this upcoming rom.

btw i wonder why the flashable zip rom should be placed in sdcard0 not sdcard1?

edit: ive tried, and it said " cant mount sdcard1 something like that in philz. :confused:

maybe some incompatibility with XZDR?

but if i use TWRP (vol-) the flashable can be executed via external...:confused:
[Xperia Z Android Development] bruce1x:
Places a copy on both internal and external as sometimes when you do all cache wipes it can wipe the internal, also on kit kat you cannot read external sd from recovery.

The op is intended for newbies.
[G Pad 8.3 Android Development] fefifofum:
The LG G Pad 8.3 has a locked bootloader, and to bypass it we have two different tools: Open bump and Loki. Most custom roms now use Open bump (recommended), but some still use Loki. Jellybean and Kitkat bootloaders have different backlight settings, and kernels need to be adapted to match those backlight settings. So here I provide some flashable zips, so you can choose the bootloader that best suits your custom rom.

IMPORTANT: to install these files, reboot into recovery and flash the zip of your choice. After that, reboot into recovery again so the changes take effect. If you are stuck on Lollipop bootloader and have no access to recovery, check this post.

V50020F Bootloader is needed if the kernel in your custom rom/recovery is adapted to Kitkat bootloader backlight, like CyanogenMod 12.1 and TWRP official builds.

V50020F Bootloader: https://www.androidfilehost.com/?fid=24352994023707804

*** DEPRECATED (below) ***

V50010B Bootloader is needed if the kernel in your custom rom is adapted to Jellybean bootloader backlight, like those based on CyanogenMod old code.

V50010B Bootloader: https://www.androidfilehost.com/?fid=23991606952613674

V50020D Bootloader Loki is needed if the kernel in your custom rom is adapted to Kitkat bootloader backlight, but it's packed with Loki. All the files are from V50020D, except aboot.img from V50010B. This should not be used anymore, every custom rom should use Open bump instead of Loki. If you are a developer and want to use Open bump instead of Loki, check this commit.

V50020D Bootloader Loki: https://www.androidfilehost.com/?fid=23991606952613676

* If you are a developer and want to use Kitkat bootloader backlight settings (instead of Jellybean), check this commit.
[G Pad 8.3 Android Development] yawako:
Wow I may not have my Gpad yet but I think its getting easier now because of this base flashable zip. Thanks

This will automatically replace old version of TWRP if flash for the first time like this one?

http://xdaforums.com/showthread.php?t=2641409
[G Pad 8.3 Android Development] Drgravy:
[MENTION=4517918]jsevi83[/MENTION] Great Idea! :good:
[G Pad 8.3 Android Development] yawako:
How can we exactly use this?

Just want to make sure nothings bad gonna happen

Im currently on LRS Kitkat and old TWRP. If I want to replace it with CM 4.4.2 ROM. I have to wipe the system then use 4.2.2 base then the full CM ROM?

Just found out that even the new TWRP 2.7.0.1 is still not compatible LRS ROM

Its possible to replace recovery.img with old TWRP or perhaps Philz CWM?
[G Pad 8.3 Android Development] ptargino:
Yeah, I'm a little lost too on how to proceed. If you can post some detailed instructions, it'd be much appreciated :)
[G Pad 8.3 Android Development] annoyingduck:
It's pretty simple, If your on a 4.4 stock (not aosp) and want to flash an aosp 4.4 rom (which uses 4.2 bootstack) flash the 4.2 zip then reboot into recovery from recovery (important) and then flash your rom normally. If your on 4.2 stock or aosp and want to flash a 4.4 stock rom, flash the 4.4 zip then do the same by rebooting into recovery from recovery and flash away. Its important to reboot into recovery from recovery after flashing these because if you boot your current rom, the kernel and other boot partitions won't match - bad things will happen.
[G Pad 8.3 Android Development] fefifofum:
Thanks, I added the instructions to the first post and mentioned you in the credits.
[G Pad 8.3 Android Development] RyanEJ25:
What do you meant boot into recovery from recovery?why boot into it twice? Im on stock 4.2 and want to flash 4.4
[G Pad 8.3 Android Development] erwaso:
ok, so i did the thing where bad things happen, i tried flashing the 4.4.2 one thinking i had 4.2.2 and now its bootloop hell. Goes to teamwin screen then it auto runs "Running Open recovery script" then bootloops again. Hard reset does not work, just goes back into loop.

How can i undo the stupidity? thanks
[G Pad 8.3 Android Development] fefifofum:
Boot into recovery, flash the chosen base zip, then press the reboot button and then recovery, this way it reboots into recovery again and the changes are applied. Then you flash the rom you want.

It depends on what rom you want to have. If you want stock 4.4.2, flash any of the zips found in the forum (like the flashable V50020B), it will also change the base. If you want CM11 or any other AOSP based rom, flash the 4.2.2-base.zip, reboot into recovery again and then flash the zip of the rom.
[G Pad 8.3 Android Development] erwaso:
I understand that part. Problem is I don't have the chance to do anything. It goes from LG screen to teamwin logo to the flashing screen then back to the LG screen.

How can I stop the boot looping?
[G Pad 8.3 Android Development] fefifofum:
I don't understand how you got into that situation, I tested the zips a lot before publishing them. Anyway, if I were you I would install the KDZ file to get back to stock. There are some threads in the forum explaining how to do that.
[G Pad 8.3 Android Development] annoyingduck:
Free thanks...

Anyways, can you get into download mode?
[G Pad 8.3 Android Development] erwaso:
Yes sir. But while I use the mobile tool in Windows Vista, it keeps stopping at 30% during extraction. I saw that YouTube video for unbricking going from 5 to 80 in a second during extraction.

So annoyed lol. Never happened to me before.

---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------

I was already in trouble before, I was rooted on 4.2.2 and did a factory reset before updating to Stock 4.4.2. I got stuck in twrp home screen and no matter what I tried to wipe or flash it went back to twrp home. So I tried to flash your 4.4.2 zip and now it's all boot loop happy lol

I saw that kdz thread. I'll try it when the kids aren't running around me in circles :)
[G Pad 8.3 Android Development] annoyingduck:
Use mobile tool and do it again. Be sure your using the regular mobile tool, not the modified one for the kdz method. Get in dl mode, choose upgrade recovery option + manually enter your model # and serial #. Give it a good 5+ min to determine if it's actually hanging. If it does, unplug it and plug it back in and it'll continue. I did that once and it worked fine.

-VZW LG G2 VS980
[G Pad 8.3 Android Development] erwaso:
Thanks! I'll try it and report back. Appreciate the assist!
[G Pad 8.3 Android Development] erwaso:
Ended up deleting all LG related anything on my comp, then reinstalling them as suggested in another thread. This worked lol. Now to root ioroot and see if I can't screw up again.

Thanks.
[G Pad 8.3 Android Development] graphdarnell:
I still don't get it. If I am on Pacman that says 4.4.2, what do I flash? How do I know if a certain rom is AOSP based, and what bootstack when it says 4.4.2? And if I'm already on PacMan 442, and want to get rid of the dim light issue, do I flash the appropriate zip, then reflash the rom? Or do I need to downgrade to stock 4.2.2 then flash 422 zip, then flash the custom rom again???
[G Pad 8.3 Android Development] fefifofum:
If you have the dim light issue at boot, flash the 4.2.2 base zip. If you want to install a custom rom based on stock 4.4.2, install the 4.4.2 base zip.
[G Pad 8.3 Android Development] graphdarnell:
Thank you for the prompt reply and help. Lest I belabor the point, I understand what you're saying from the beginning, but what confused me was the mention by another member that the 4.4.2 customs roms used 4.2 "bootstack" (whatever that means). So the question again is: if a custom rom says 4.4.2, is it really 4.4.2 or 4.2 boot stack (whatever that is)? And in which case, which zip do I use?? I can do it by trial and error, but need to be assured that shooting from the hip won't mess my tab unnecessarily. Again thanks for the help.
[G Pad 8.3 Android Development] annoyingduck:
So basically an android device has something like 20+ partitions. The 4 that are most commonly known are recovery, rom, boot (kernel), and the modem. When you flash a rom your overwriting the rom (os), and boot (kernel) partions only (in general).

The other partitions which are mostly part of the firmware include the modem, radios, and bootstack (which is a bunch of tiny items, like tz, laf, and others I don't fully understand). These are not updated when flashing a rom.

The official 4.4 update, updated all of those partions. Now before the official kk we were on 4.2, but aosp roms (cm, Mahdi, PA, pac, etc) were all 4.4 roms that ran on our 4.2 firmware. Now that the official 4.4 is out it's technically the job of all those rom devs to update their roms to boot correctly on the 4.4 source, but that's not an easy task so a work around was created to keep some of the old 4.2 boot firmware on the official 4.4 full firmware.

Weather or not aosp roms get updated to boot on the 4.4 source is unknown. So for now these zips allow you to transition very easily. It sounds confusing, but it's really not. You just need to view it deeper than a 4.2 vs 4.4 rom because they're is more to it than just the rom.

One of the devs can probably create a good analogy to help you see it differently....
[G Pad 8.3 Android Development] graphdarnell:
Thanks for the elaboration. So basically, I should assume all the presently available custom roms run off 4.2 in partitions that matter to users, and thus should flash 4.2.2 TWRP before reflashing the rom, to eliminate the dim light issue.
[G Pad 8.3 Android Development] annoyingduck:
Yes, unless it's a stock based 4.4 rom
[G Pad 8.3 Android Development] graphdarnell:
I was on 442 stock with TWRP 2710. I just flashed 422 zip in TWRP, then rebooted to recovery from TWRP menu. It went back to TWRP, opened and wrote some script, then turned off and booted back to OS. Wouldn't stay in TWRP 422. Have no idea why. Maybe I should flash back to stock 422 (20A) before flashing zip? Makes no sense since the whole point of flashing 422 zip is so not to have to downgrade. Am I wrong?

Update

: So I flashed recovery back to regular TWRP 2700 with Aboot V50020, then restored NAND Backup (PA 443) and to my surprise, the dimming problem disappeared. Just to test, I then flashed Slimkat 443, and experienced no dim stuff there either!

Apparently, something happened though 422 zip didn't stick. So long as it works, who cares? The question is, if I ever upgrade the recovery to 27xx, would that undo the "cure" and revert to dimming again?
[G Pad 8.3 Android Development] paradiselost28:
Hi,

I read your post and I would like to know what to do in my case :

First I was in 4.2.2 stock LG ROM then I rooted, installed TWRP (2.7.1.0) and installed Infected V500 ROM 4.4.4 (based on CM11). Everything seems to work but the brightness is strange (compared to my Nexus 7 2013...)

EDIT : I also have this msg on boot :

http://fr.tinypic.com/view.php?pic=5n7psj&s=5#.U8FT0rFXqq0

Do you think I need to flash the 4.4 base zip now without any problem ? Will it resolve my brightness screen problem ?

Thanks a lot for your help :) I want to be sure I won't brick my brand new LG G PAD...
[G Pad 8.3 Android Development] LeighR:
Quick case study, as I expect most people are in my situation.

I was on rooted stock 4.4.2. The OTA screwed me around so I tried slimkat and CM11. Both had brightness issues.

Flashed the 4.2.2 base file, rebooted recovery and DIDN'T reflash my ROM (Infected CM11). Rebooted the system and it works great. Brightness is fixed and didn't have to reflash my ROM.

I'm using TWRP 2.7.0.1

-------------------------------------

Edit: scratch that, was very unstable. Had to reflash the ROM
[G Pad 8.3 Android Development] gffmac:
Just a little heads up, brightness on none stock works fine on 4.4.2 base with this kernel http://xdaforums.com/lg-g-pad-83/development/kernel-mani-kernel-t2809530
[G Pad 8.3 Android Development] creeater:
That message on boot is normal. Means you are unlocked.
[G Pad 8.3 Android Development] Jhon998:
Ohhhh, I haven't read the instructions first,

I was on LRS, and wiped everything, the flashed the base 4.2, the it refused to boot into recovery and booted into system, so I couldn't do anything, so I flashed the philz img, the flashed the twrp zip, then flashed stock 20b rooted, then flashed base 4.2, then wiped everything, then flashed cm11 infected, then gapps,and now what? dyn kernel?

Thanks devs...
[G Pad 8.3 Android Development] LeighR:
The CM11 kernel works well

I'm using the oubeichen kernel from the AIC thread and it works very well
[G Pad 8.3 Android Development] whoamigriffiths:
Didn't this one need building* first?

If so, are you happy to share it?

I'm sure oubreichen wouldn't mind.

Thanks in advance :)
[G Pad 8.3 Android Development] LeighR:
No, he posted it in the thread (last few pages?). I didn't have to build it
[G Pad 8.3 Android Development] Rapepini:
As other people, I had problems when I rebooted to recovery (it rebooted to system after flashing a script), so i couldn't access recovery. I'm back to stock now, but I don't want to risk losing recovery anymore. Can someone give me a hint?
[G Pad 8.3 Android Development] Jhon998:
Needed:

1. flashify

2. twrp zip

3. philz zip

4. file explorer+extract ability

5. Browser

instructions:

Use flashify,

1. Backup your twrp

Go to goo.im

2. Download philz

File explorer

3. Extract philz.img

Flashify

4. Flash philz and don't reboot

5. Restore twrp

6. Reboot recovery

Recovery

7. Flash twrp zip

Then reboot recovery from power, fresh twrp again!

Press thanks f helped!
[G Pad 8.3 Android Development] wind0zer:
Same issue here. TWRP throws a reboot. Data is gone, so it's like afactory reset. CM11 loads but I had uninstalled CM11 first time initalization apk along with other bloatware. I have CM11 in "unable to start" OK button loop, and TWRP in recovery script loop. I can't seem to go into download mode.
[G Pad 8.3 Android Development] wind0zer:
I had no choice but to wipe flash the v500 with LG tool and .kdz stock rom.

LG Flash Tool 2014 - The best way to Flash L… | LG G2 | XDA Forum
[G Pad 8.3 Android Development] Feed Me:
Is it possible to find out on which base my G Pad is running?
[G Pad 8.3 Android Development] muiriddin:
I think this works basically getprop has some variables that I believe are set from the firmware base.

I assume you have a version of twrp installed

1. Boot into recovery

2. Advanced, Terminal Command

3. Hit select to choose the root directory

4. Type getprop

4. Search results for two entries ro.build.description and ro.build.fingerprint and see if those lines contain V50010a or something newer

My tablet has V50010a among other things in both entries and it is 4.2.2 firmware based
[G Pad 8.3 Android Development] renatohm:
Hey dev, thanks for these. I have a noob question here.

I flashed CM11 Infected 4.4.4 and got thiss pesky dim thingie. What should I do to fix it? Flashing your 4.4.2 zip file will do?
[G Pad 8.3 Android Development] iruiz2:
If you have the dimming issue is because you have the 4.4.2 base, so actually you have to flash the 4.2.2 one. If you are not changing rom, remember the procedure:

Do nandroid backup

Flash base

Reboot into recovery

Restore backup
[G Pad 8.3 Android Development] chn110:
Support button combinations to boot into recovery

Thanks for these two files. They are so very useful!

Is it possible to add support for button combinations to boot into recovery to these two files? Right now the button combinations would result in a factory reset. In the event of a bad ROM install it will be extremely useful.
[G Pad 8.3 Android Development] bjcrj:
If you have a custom recovery installed the factory reset just boots into the recovery. It doesn't actually reset the device.
[G Pad 8.3 Android Development] chn110:
Just tried a minute ago. It goes into TWRP for a couple seconds, rebooted by itself and is reset to factory. :(
[G Pad 8.3 Android Development] bjcrj:
What screen did it show in twrp?
[G Pad 8.3 Android Development] chn110:
It might be the main screen but I can be sure since it happened so fast and then gone.
[G Pad 8.3 Android Development] annoyingduck:
Install reboot menu from the playstore...
[G Pad 8.3 Android Development] bjcrj:
Sounds like an issue with the rebase. Did you flash a current twrp after the base changing zip?
[G Pad 8.3 Android Development] chn110:
Earlier I tried flash 2.8.0.0 twrp over the base it resulted in twrp being trashed and I had to flash the old twrp to recover. The whole point to have the base is to prevent this type of problem.

Of all the android devices I've tried (starting from the Windows Mobile turn Android HTC HD2), it seems the LG Pad recovery scheme is the most problematic. Because many a time one has to recover the recovery (or boot code) :crying: And if a ROM also develops problem we may end up having to restore to stock then reroot and reinstall recovery. Therefore I give huge credit to OP for making this less error prone. If the button combination also works, it will make the recovery much safer.
[G Pad 8.3 Android Development] bjcrj:
I flash the vase then the current recovery for the correct base right in a row, then reboot to recovery, then flash the rom. The button combo always takes me to recovery.. I'm sorry it didn't work on your end.
[G Pad 8.3 Android Development] Deltadroid:
Works great. Can you tell me what image version the 4.4.2 and 4.2.2 base files come from? For example, v50010a is the image used for the 4.2.2 base?
[G Pad 8.3 Android Development] fefifofum:
I think they were 10b and 20b, but I'm not sure. Anyway I don't think the change much between 20b and 20d.

Updated OP, now the zips don't contain recovery, persist and modem images, it's just the bootloaders. You can also find separated zips with TWRP 2.8.1.0 for each base.
[G Pad 8.3 Android Development] Deltadroid:
Maybe you should just remove aboot.img from the zip also. Anyone that flashes this already has the correct version of aboot because they couldn't have already installed a custom recovery without it. We shouldn't need to reinstall aboot and the recovery if we already have it. The only things need changing are the other partitions (not aboot and recovery).

Note: the aboot is the same in 4.2 and 4.4 bases. The recovery installation script should just extract the current aboot and use that to lokify the recovery before installing it.

The installation of TWRP depends on the version of aboot, not the version of the base, AFAIK.

Edit: oh, now I understand why you have two versions of twrp in the OP. It is to fix the brightness problems between the two bases. They are different because the recoveries are compiled for different bases.
[G Pad 8.3 Android Development] fefifofum:
You are right, we don't need to flash aboot.img since users with custom recovery already have the right aboot.img. As for the brightness issue it depends on the kernel, that's why we have two zips for TWRP, one with a kernel using 4.2.2 brightness and the other with 4.4.2 brightness.
[G Pad 8.3 Android Development] Deltadroid:
I've been using stock CWM from the nightly cm 11 builds and the brightness seems to be ok for both bases with the same kernel. I wonder why?

Edit: I think the difference is that CWM is not full touch, so it doesn't load the same drivers, so, that is why it's not affected by the brightness problem.
[G Pad 8.3 Android Development] android404:
Hi. At the moment i use infected_s cm 12 and twrp and I'm having brightness issues . Which file do I flash? I still don't get it after reading this whole thread...
[G Pad 8.3 Android Development] Deltadroid:
You need 4.2 base files if you want to use the stock kernel in cm12. If you want to use red kernel or mani kernel, then you need 4.4 base files.
[G Pad 8.3 Android Development] android404:
Thank you. And what's with the "twrp for 4.2.2" file in the first post? What is that about?
[G Pad 8.3 Android Development] Deltadroid:
Twrp has a brightness functionality that is affected by which base files are installed. You need a version of twrp that is compiled for either 4.2 or 4.4 base files, or you will experience brightness problems.

CWM is not affected by brightness issues between the two bases because it doesn't load the same drivers.
[G Pad 8.3 Android Development] Gmobilize:
looks like flashing the aosp rom and redkernel while being on 4.4.2 base helps with the brightness issues on boot.
[G Pad 8.3 Android Development] Schrotty35:
I use Stock 20d with TWRP 2.8.3.0 and will install latest CM11. But after i have install CM11 i see only the LG Logo. Must i install V500-4.2.2-Base for working CM11?
[G Pad 8.3 Android Development] Deltadroid:
No, if you installed the 10b image, then you already have the 4.2.2 base. The problem you are having is probably because you need to perform a factory reset after installing cm11 for the first time.
[G Pad 8.3 Android Development] Schrotty35:
Whene i make a factory reset after install cm11 i lost cm11??
[G Pad 8.3 Android Development] Deltadroid:
A factory reset just clears the system so you can install a new Rom. A factory reset is necessary after installing cm 11 over stock. After you install the cm 11 zip file, do a factory reset, then reboot into the new cm 11 system.
[G Pad 8.3 Android Development] Schrotty35:
I dont install over stock. I have make a factory reset befor i have install cm for a clean install.