[ROM][4.4.x] [OFFICIAL] SlimKat - V500 - LGPAD8.3

[zedorda]

Hm, you really got some odd problems, this is what I did/would recommend (step by step):

flash a base
(you can even use a 4.4.2, but only with a different kernel)
reboot recovery
update twrp
(there are two “2.7.1.0”, make sure to use the right one for your base!
["Current build" is for 4.2.2])
reboot recovery
wipe everything (include format data))
reboot recovery
flash slim
flash gapps
(in case of 4.4.2 base flash kernel)

I tried this method from stock 4.4.2 with TWRP 2.7.1.0 but right after I flashed the 4.2.2 base then rebooted recovery as soon as TWRP rebooted it runs a script wiping my data then rebooting system. I cant do anything with TWRP anymore and was wondering how you fixed this when you tried this method?

EDIT: I fixed it. I was still able to boot up stock 4.4.2 so i redownloaded Flashify and reflashed 2.7.1.0 TWRP and it loaded recovery without the script. I think my original TWRP was messed up or something because after that the above method worked fine and I am now running SlimKat.

 

[NexusPenguin]

Hi Tana, Demetris and DarkMaster,

Sorry I did not reply to your ind posts earlier : I was not at home and had to get a monkey off my back before I could come back to my V500.

Anywyays, I just wished to thank you for your kind posts that obviously helped to solve my problem.
I flashed a 4.2.2 bootloader and installed ROM ToolBox Pro (even even the interface is confusing, I like that "All-In-One" tool) and installed the ROM from there.
I so was able to update from SlimKAT 7.4 to SlimKAT 7.6 without a glitch and preserving all my data and settings.

That is nice

So a great great thank you to all three !

Regards.

 

[tekka-maki]

AOSP based ROMs like SlimKat don't play good work LG's KitKat bootloader (screen dimming problem), but work totally fine on jellybean bootloader.
Go to Flashable zips to change between 4.2.2 and 4.4.2 Base thread and download 4.2.2 zip. Flash it on recovery and reflash ROM and gapps. I don't know if it will help for your problem but it's good to be sure you have correct base for AOSP ROM.

If it doesn't solve the date wipe problem flash LG stock jelly bean ROM [ROM] 4.2.2 Flashable [V500] JDQ39B.V50010A_US [easily go back to stock 4.2.2]. Let it boot. Then reboot back to recovery and flash SlimKat with Slim gapps.
If this doesn't help I don't know what else to do.

---------- Post added at 09:22 AM ---------- Previous post was at 09:20 AM ----------

Did you flash the TWRP on it or was it already installed? Download latest TWRP.img and flash it yourself. This should exclude recovery error.

i was running mahdi (based off settings, i presumed 4.4.2 base) on v500; flashed 4.2.2 via twrp; now stuck in this situation where (potentially?) 'bad things happened' in so far as when i reboot to recovery after installing flash, openscript runs, wipes data, then automatically rebooots.

essentially, i cant get twrp to stay open beyond this looping OpenRecoveryScript that force reboots to system when it completes wiping data. what am I to do? arrrgghhhh... i had my reservations about installing a 4.2.2 base from the non original android side despite seeing reference from v500 side... :/

---------- Post added at 08:51 AM ---------- Previous post was at 08:05 AM ----------

was able to install rom manager and get Stock LG build JDQ39B.V50010A installed. wondering how the f--k ROM manager shows i have two recoveries, both TWRP and CWM. I thought one always overwrote the other as recovery.img


NEVERMIND, sorted and don't really care why the problem.

 

[olskar]

Will we see a stable 8.0 for our v500?

 

[MattNoir]

OTG

Hello, is OTG working in slimkat? It's one of essential things I need, thank you.

 

[zedorda]

Yes OTG works and if your using TWRP you can even use OTG in recovery.

 

[MattNoir]

Yes OTG works and if your using TWRP you can even use OTG in recovery.

Well if OTG works, then it's not fully functional. I can't connect my camera and control it via dslr dashboard app...
also if I connect devices with ntfs formatting it doesn't work, but that's normal

 

[zedorda]

Well if OTG works, then it's not fully functional. I can't connect my camera and control it via dslr dashboard app...
also if I connect devices with ntfs formatting it doesn't work, but that's normal

True OTG has many functions I did not assume you were asking about since all you asked was if OTG was working. I tested FAT32 USB disk access and HID devices. The two most commonly used functions of OTG. I would not assume proprietary device control would work since I would of needed the same device to test it.

In general app to device control via OTG is disabled with proprietary connections on unsecured(rooted) devices.

 

[MattNoir]

True OTG has many functions I did not assume you were asking about since all you asked was if OTG was working. I tested FAT32 USB disk access and HID devices. The two most commonly used functions of OTG. I would not assume proprietary device control would work since I would of needed the same device to test it.

In general app to device control via OTG is disabled with proprietary connections on unsecured(rooted) devices.

And would it be possible to make it work for cameras, too? As I said, it connects, but after a while disconnects...

 

[indian84]

Build 8.9 is up....

 

[Demetris]

Sorry for the lag of updates from my part Ok after i finish with my other projects am planning a kernel upgrade for slim on L. Stay tuned.
Regards

 

[Mennooo]

Slimpop?

Sent from my LG-D855 using XDA Free mobile app

 

[Demetris]

SlimLP

 

[indian84]

Yup, official name is SlimLP

 

[knightsh]

Tried searching this thread and the saberkat one with no luck. So, is anyone experiencing bluetooth connection problems?? The last couple updates for me have killed it. I've even flashed different kernels with no luck. My tab just keeps connecting then disconnecting with my GBoom speaker. I have to end up using my OnePlus instead. Anyone have this problem or know of a solution?

 

[jonup]

Tried searching this thread and the saberkat one with no luck. So, is anyone experiencing bluetooth connection problems?? The last couple updates for me have killed it. I've even flashed different kernels with no luck. My tab just keeps connecting then disconnecting with my GBoom speaker. I have to end up using my OnePlus instead. Anyone have this problem or know of a solution?

Infected slimkat here and Bluetooth works with my jaybirds

 

[knightsh]

Infected slimkat here and Bluetooth works with my jaybirds

Tried the Infected's version with same result. Hmm.... wiped cache/dalvik/system and reflashed and same thing. Going to try and connect to another device and hope it's not the g pad having a hardware problem.

 

[jonup]

Tried the Infected's version with same result. Hmm.... wiped cache/dalvik/system and reflashed and same thing. Going to try and connect to another device and hope it's not the g pad having a hardware problem.

I also run red kernel

 

[zedorda]

Why doesn't "Slim-v500-4.4.4.build.8.12.1-WEEKLY-7864.zip" include SuperSU and why can't it reboot to recovery from long-press of the power button?
Hard to think these were unwanted features. I updated from 7.4 and these features were working fine before.

Thanks for any help.

 

[ncguy68]

Why doesn't "Slim-v500-4.4.4.build.8.12.1-WEEKLY-7864.zip" include SuperSU and why can't it reboot to recovery from long-press of the power button?
Hard to think these were unwanted features. I updated from 7.4 and these features were working fine before.

Thanks for any help.

Root has to be enabled in developer options and the advanced reboot option can be enabled in security.

Sent from my LG-V500 using xda premium