Develop Bugs

Working pdroid patches [currently AOKP(toro+maguro), stock AOSP, cm9]

I'm using this thread to share working pdroid patches I've got for various Galaxy Nexus roms. This was made using the patcher being developed here (patcher is in the 4th post). The patcher is currently linux-only, but will also work with cygwin in windows. I'm posting the finished flashable zip here as a convenience to anyone who can't use it themselves. Please note that I am not one of the people actively developing this patcher, just a willing tester who happens to own a toro Gnex.
If you don't know what Pdroid is, this is the thread for it on xda. Basically, it lets you deny permissions to apps on a per-permission basis, without risking apps crashing. Same basic idea as LBE privacy guard, but in my opinion executed better. Plus, open source is always a plus. Even though the official patcher there won't work for us yet, check the official thread. You'll need to download the app from the market and follow the same instructions, just using the zips I'll post here (or make your own).
I'll include a revert.zip for anything I post here, but please note that I take no responsibility for anything that happens to your phone. Make backups before flashing things. Try TWRP if you haven't, it's faster at backup/restore than CWR and does a bunch of other neat stuff like compressed backups and queued zip flashing. Also, in case of things breaking, please note that these revert zips are (1) only going to work if you are running the same rom used to create the zip and (2) just a slimmed down version of the rom's zip. What this means is that if you flash a pdroid zip and you need to revert, the surest thing to do is just re-flash your rom without wiping anything.
I'll try to update this thread as I get more patches working. Here's where my own experiments stand:
Link to my dropbox folder with files, notes below
Working patches:
-AOKP b39 (toro):
-AOKP b39 (maguro):
-CM9 Nightly: Patched build: 2012/06/19
--Note: Not sure if these will automatically fail with later nightlies or only when something relevant is updated in the rom. Feel free to try, just reflash your rom if it bootloops.
-Stock AOSP(+root, busybox): Patched build: 2012/06/02
-Paranoid Android v1.4a
Not Working (Yet):
-Liquidsmooth 1.5RC4:
-Slim ICS 4.0:
Unless otherwise noted, these are all for the toro (verizon) Galaxy Nexus. It's pretty quick and easy for me to make new patches so feel free to request something. But please be aware that sometimes it's a few days between when I can devote any time to this and don't be offended if I don't reply to you right away.
Just to reiterate, all you need to do for this is download the "Pdroid Patch Zip" file for your rom, flash it in recovery, and download Pdroid from Google Play.
Finally, be aware that the first boot after flashing can take a very long time, without any indication like the "Android is Upgrading..." screen. Don't assume it's bootlooping! Seriously, put the phone down and do something else for a bit. Anything in the tested section I've either personally flashed on my phone or someone else reported as working. If you're sure you're getting a bootloop on a clean install, my only advice is to do a full revert to stock and re-unlock/root/etc and see if it works then. Though rare, it is possible for something to be corrupt that persists across the usual "clean install" routine.

Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions

Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?

xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
For gsm you'd need a new patch. There are instructions in the first thread I linked to if you'd like to try it out. I might make one in a bit since I expect that to be a popular request and I expect it to work.
danger-rat said:
Isn't that what Permissions Denied does?
https://play.google.com/store/apps/details?id=com.stericson.permissions
Click to expand...
Click to collapse
Same idea, different approach. Permissions denied generally causes apps to crash if they need info that they are denied. I also had a major issue with it a while back that I ended up doing a factory reset for, but I think that's been fixed since then.
Not sure how pdroid gets around apps fc'ing (maybe it spoofs data so apps go on running normally? It has an option to set your own values I haven't played with much), but it works very smoothly.

xternal said:
Wow, I didn't realise you could patch AOKP on ICS yet. Have been waiting for this for so long. How would I go about applying your patch for AOKP gsm?
Click to expand...
Click to collapse
Quick update, I put up a maguro for AOKP, and I also updated the OP quite a bit since I last posted. Finally got around to testing the patches I made; getting better at reading the patching process as well to tell when a patch will work before flashing it, too.
At far as updates go, I don't really intend to follow the cm9 nightlies as I don't run them myself. I'll probably continue to try new versions of AOKP and paranoid android as they come out. I'll continue to try the roms that don't patch yet with new versions of the patcher as they are released.

Thank you. The maguro patch works for me.
Edit: not sure, but this likely breaks 2 apps: Listen, Drive.

I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.

deaffob said:
I've been using LBE Privacy to control permissions and this app doesn't crash apps that have permissions blocked. It's one of their selling points, doesn't crash apps.
Click to expand...
Click to collapse
PDroid source has been released, whilst LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
The patch works a treat on GSM aokp, many thanks
edit: looking at it though, it seems it doesn't find all the permissions correctly. I am assuming this is a limitation of the current pdroid as it is not designed for ics.
For instance it does not find hardware controls. Google Drive has access to hardware controls to take photos/videos.

Thanks for the confirmations on the maguro zip, I edited the post to reflect that it's definitely working.
I hadn't heard of LBE before making these threads but from what I've read it seems like people generally prefer pdroid. I'll check it out at some point but it looks like it does a bit more than I'd want it to, and pdroid being open source is definitely a plus.

IIRC, there's certain instances where apps can bypass LBE but not PDroid. I think reboot is one of those times due to when LBE loads.

I've been running LBE but lately the service keeps stopping because it doesn't get root soon enough after boot. Trying this now on Paranoid. Thanks!

i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?

SGDynamite said:
i have used this patch for CM9 but after the Bootscreen have i a Blackscreen -.- what can i do?
Click to expand...
Click to collapse
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.

xternal said:
LBE created by a 'suspect' chinese company. I put the suspect in inverted comma's because nothing has actually been proven.
Click to expand...
Click to collapse
I hadn't heard of pdroid until I was on the Nexus, so I'm not familiar with it to compare, but I'm currently using LBE and blocking its data connections with Droidwall. Perhaps a bit overkill... but works great as far as I can tell.
Sent from my Galaxy Nexus using xda premium

JoeSyr said:
I'm guessing you are running a different build/more recent nightly? I might take that link down as it was meant as more of a proof of concept if the cm9 patcher was working and it's unlikely anyone is going to be flashing that particular build just to test pdroid.
The most effective thing would be to just re-flash the original rom's zip, you don't need to wipe anything. The revert zip file is basically just four files copied from a given rom's original zip, services.jar, core.jar and framework.jar in /system/framework, and build.prop in /system.
Click to expand...
Click to collapse
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.

robjective said:
I think I flashed it to a nightly a day or two after 5-18 and it worked, but it definitely did not work on 5-27 or 5-29.
If the patch doesn't work for you, pull the battery, then hold volume up and down while you hold power, then use volume up and down to get to recovery option--press power to select. Either flash the revert or the old from there on top of the non-working one. Don't clear data partition and you won't lose anything.
@Joesyr, I think there is some interest in CM9 nightly patches...would you mind making a CM9 patch maybe once a week? I haven't had any luck making the patch on my own.
Click to expand...
Click to collapse
Well the last cm9 nightly I tried didn't patch at all (I believe it was a 5/29 build). I will try tinkering with things as I get the time but I'm not really at the level of fully understanding these kinds of failures yet.
Next time there's an updated cm9 patch I will try to get a working pdroid zip and I'll consider weekly updates. I'm also generally willing to make these on request as it's a pretty quick process. Fiddling with dropbox links is probably the longest part of any of this.
Any particular issue you're having with the patcher? I've been thinking I could write a little tutorial for getting cygwin up and running since I imagine that for most people the limiting factor is just that they don't have a linux environment to work in. But until I get the time to do that I can help troubleshoot.

Can you make a patch for stock root.
Thx

Has anybody experienced random rebooting? All was fine until I opened a non system app. Then it just started rebooting randomly after opening any app. I ran it on Maguro with AOKP b37.

soloxp said:
Can you make a patch for stock root.
Thx
Click to expand...
Click to collapse
Yup, not sure if the rom I just put up is the same you were looking for but it's the first one I've been able to get to patch correctly with the aosp patch.

Just flashed the Toro AOKP b37 patch, tested and working great here. Thank so much! Awesome work!!

[WIP][ROM][Verizon] CM10.1 for LG G2 (Verizon) looking for help!!

Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: kernel, device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_kernel_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
10/17/13:
http://forum.xda-developers.com/showpost.php?p=46554268&postcount=271
10/12/13: alpha
http://forum.xda-developers.com/showpost.php?p=46407049&postcount=138
10/3/13: Super alpha
http://forum.xda-developers.com/showpost.php?p=46147336&postcount=74

I would love to help, but I admit I don't know much about Android development. I've got an AT&T G2 and I know C# and a bit of C++, so I'm sure I can figure out C. I think it's awesome that you're working on CM, if I can help out somehow I'd love to!

Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?

bose301s said:
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
Click to expand...
Click to collapse
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.

fonix232 said:
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
Click to expand...
Click to collapse
Ok, that is what I was thinking but I have never done any dev work or anything so I figured I would ask.

I cant help but I sure want to thank you folks for trying to get this up and running. This phone is an absolute BEAST! Coming from the gnex I'm excited about the G2's potential.
Sent from my VS980 4G using Tapatalk 4

Thanks!
I just wanted to thank you very very much for working on this! I knew this was going to be a well developed phone and I bet before 4 months we will have a good amount of choice as far as roms go. Thanks again!

I've been trying to port beanstalk to the G2 but I need the same information you are trying for. I need device trees to sync with. I can PM you with what info I've came up with So far if you are interested.?
Edit: tress are up! Great work
Sent from my LG-D800 using xda app-developers app

If you lived in my town I'd probably help by cleaning the gutters for you hehe. Thanks for your work!
Sent from my EVO using xda app-developers app

I am definitely willing to help in any way I can.

I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...

grandmasterlarry said:
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
Click to expand...
Click to collapse
same goes for me, I have the Korean version.

Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?

mrbig012 said:
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
Click to expand...
Click to collapse
LG UI feature. I'm fairly sure it will be ported to an AOSP/CM10/LGUI hybrid ROM at some point. I believe part of the issue that devs are running into is that a lot of the custom LG software appears to be tied together.

Can you guys keep us updated on your progress, this is a make or break thing for me with this phone, CM is just so much better than any stock ROM that I don't know if I can deal with a phone that has no prospect of official support.

JackpotClavin said:
Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
Click to expand...
Click to collapse
Are we going to try getting mobile network and wifi working first? Is adb working?

droid_<3er said:
Are we going to try getting mobile network and wifi working first? Is adb working?
Click to expand...
Click to collapse
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source

JackpotClavin said:
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
Click to expand...
Click to collapse
I am NOT a developer, but this could help perhaps?
http://opensource.wolfsonmicro.com/content/wm5110-linux-driver-released
Not sure if it really is open source or only available as binaries, but the WM5110 is the audio SoC in this phone... I am probably not helping.
Additionally, I think the S4 uses this SoC as well. It's a pretty new part but is gaining a lot of momentum.
Edit: My god that WM5110 is a hell of a part... quad-core, 600 MIPS... dayum!

Glad to hear an update, even if it's about issues. Seeing that there are people actively working on this to make it happen makes me much happier and less worried about keeping this phone vs. returning it tomorrow or Friday to see how the Nexus 5 plays out etc.

Have any of you tried talking to Ricardo Cerqueira? He is in fact the primary maintainer for all LG Devices with regards to Cyanogenmod. I am sure he is planning on supporting this device in the near future, I just don't know when. It will probably be when the device is more readily available since it was pretty much just released.

[Q]S4 Mini LTE After Root Wi-Fi & Bluetooth Not Working

Hi Guys, I thought I would make a thread here as i can not seem to be able to find a solution. Rooted my device obviously, everything is fine until I installed a "Kernel" (cant remember author) to overclock mainly then encountered several problems. 1: Wi-Fi has become unstable. It seems to either crash my phone or signal disappears after my phone is on standby for a period of time (variable). 2: My Bluetooth just does not work. At all!! I have not done anything more to my device so the solution (hopefully). I forgot to mention that it is STOCK ROM. I do not wish to wipe my phone clean, i want to find a fix. Possibly a more stable kernel. Overclocking does not want to happen either but the "Governor's, I/O Scheduler's and Underclocking" do work. If there is anything more you guys need to know please ask!!
Looking forward to ideas
Kye

KyeWalker said:
Hi Guys, I thought I would make a thread here as i can not seem to be able to find a solution. Rooted my device obviously, everything is fine until I installed a "Kernel" (cant remember author) to overclock mainly then encountered several problems. 1: Wi-Fi has become unstable. It seems to either crash my phone or signal disappears after my phone is on standby for a period of time (variable). 2: My Bluetooth just does not work. At all!! I have not done anything more to my device so the solution (hopefully). I forgot to mention that it is STOCK ROM. I do not wish to wipe my phone clean, i want to find a fix. Possibly a more stable kernel. Overclocking does not want to happen either but the "Governor's, I/O Scheduler's and Underclocking" do work. If there is anything more you guys need to know please ask!!
Looking forward to ideas
Kye
Click to expand...
Click to collapse
It not the root that causing the issue, it the kernel that tried. If I remember correctly there's only two kernel for the S4 mini that allows overclcoking, and one of them has stopped developerment since last year. That leaves the F4k kernel.
He has two different kernels: one for the AOSP/CM (custom) ROM another is also a bit outdated for the default Samsung TouchWiz ROM. Are you sure you've download the correct kernel?

TNCS said:
It not the root that causing the issue, it the kernel that tried. If I remember correctly there's only two kernel for the S4 mini that allows overclcoking, and one of them has stopped developerment since last year. That leaves the F4k kernel.
He has two different kernels: one for the AOSP/CM (custom) ROM another is also a bit outdated for the default Samsung TouchWiz ROM. Are you sure you've download the correct kernel?
Click to expand...
Click to collapse
Well to my knowledge I had used the correct kernel....... I never used one from here but I did find a website claiming that F4k has a stock over clocking kernel...... Unfortunately for the life of me I can not find this website. I've managed to overclock with success using a apk. I found on here (performance control) brilliant tool!! Is there any chance you able to post a link to this stock kernel you talk about so I can test myself and report back? Everything else is working without a problem apart from Wi-Fi and bluetooth.
Kye

KyeWalker said:
Well to my knowledge I had used the correct kernel....... I never used one from here but I did find a website claiming that F4k has a stock over clocking kernel...... Unfortunately for the life of me I can not find this website. I've managed to overclock with success using a apk. I found on here (performance control) brilliant tool!! Is there any chance you able to post a link to this stock kernel you talk about so I can test myself and report back? Everything else is working without a problem apart from Wi-Fi and bluetooth.
Kye
Click to expand...
Click to collapse
For custom ROM - http://forum.xda-developers.com/showthread.php?t=2568479
For Samsung TW ROM - http://forum.xda-developers.com/showthread.php?t=2636890

summarise.....
TNCS said:
For custom ROM - http://forum.xda-developers.com/showthread.php?t=2568479
For Samsung TW ROM - http://forum.xda-developers.com/showthread.php?t=2636890
Click to expand...
Click to collapse
So I've come to a conclusion after many weeks of testing and searching........ Unfortunately the overclock kernel for "TouchWiz" roms is unstable........ looking through forums I can see that F4k has only realised a "test" version....... on the other hand I have found a kernel from Vikinger (if spelt correctly) that's has fixed my issue and is working great... shame it isn't overclocked nor under and has no additional governors..... any one with ideas please feel free to share..... many thanks.
Kye

[Q] Very low screen bright after reboot

Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot

reypescador said:
Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot
Click to expand...
Click to collapse
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411

muiriddin said:
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411
Click to expand...
Click to collapse
Thank you very much
I try to read the info and decide what to do.
Thanks again

Ok it´s done
First I´ve installer V500-4.2.2-Base from recovery, I have reinstalled CM 11 and everything OK.
I have tried a step beyond and I have installed [KERNEL][v500][4.4.4][AOSP] RedKernel [16/09] (everybody seems to be very happy with it) but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help

reypescador said:
but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help
Click to expand...
Click to collapse
Seems to be problems with Super SU but I can´t solve them at the moment

You must install the UKM scripts from recovery. Read the op from the red kernel thread...

edisso10018 said:
You must install the UKM scripts from recovery. Read the op from the red kernel thread...
Click to expand...
Click to collapse
What he said!
This confused me at first too. In the very early days of redkernel he included his own forked version of the UKM scripts those have been removed because the UKM script maintainer agreed to merge his changes and therefore he doesn't have to maintain his own copy (better for all involved so he can focus on kernel development). Search the thread you will find a link to where you can download the official UKM scripts and your problem will go away.
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...

muiriddin said:
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...
Click to expand...
Click to collapse
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium

ncguy68 said:
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.

muiriddin said:
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.
Click to expand...
Click to collapse
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium

ncguy68 said:
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.

muiriddin said:
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.
Click to expand...
Click to collapse
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium

ncguy68 said:
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I am unaware of a problem with the 4.4.2 base files provided. I have just never used them, I already had the LG Support Tool downloaded and it was easiest to use the path I knew and was comfortable with.
The key thing (and why I run the 4.4.2 base instead of the 4.2.2. base) that is different is the brightness at its lowest setting. The 4.2.2 base on many of the V500's suffers from alternating light and dark spots on one side of the tablet when viewing the tablet in low light with the brightness at its lowest setting and viewing gmail (any app with a white background basically). I use my tablet mostly in dark conditions like this (man I make it sound like I live in a basement somewhere *laughs*). The 4.4.2 base firmware changes the tablet so it functions well at the lowest brightness.
The first picture in this thread shows the screen problem I refer to (although not on a white screen):
http://forum.xda-developers.com/showthread.php?t=2553055

[Q] LG Security Error but slightly different than others

I know this has been covered in one way or another in other threads but mine is slightly different. I have the newest philz touch recovery for my ls-970. I installed the newest cm12 unofficial (nightly 1/11/2015 is the newest). I then installed jolla kernel but was having problems with system ui crashing so i stupidly decided to install the stock version of the kernel ( this kernel is an all in one bundle using aroma to select which kernel for your device). Right after this was installed, it would not boot into cm12 and gave me this lg security error. Problem is all Ig et is the LG symbol and the words security error. Unlike other people that have a cause listed, this has nothing. I am able to go into recovery easily. The boot loader still says unlocked (i assume fastboot is an option too?). I installed optimus de (which was residing as a backup on my sd) and the phone boots fine. But as soon as I go back to cm12, it has a security error. I have already taken it upon myself to download lgnpst and the lg drivers.
What are my options here? When it shows this error, it simply powers off after a few seconds.

thejase said:
I know this has been covered in one way or another in other threads but mine is slightly different. I have the newest philz touch recovery for my ls-970. I installed the newest cm12 unofficial (nightly 1/11/2015 is the newest). I then installed jolla kernel but was having problems with system ui crashing so i stupidly decided to install the stock version of the kernel ( this kernel is an all in one bundle using aroma to select which kernel for your device). Right after this was installed, it would not boot into cm12 and gave me this lg security error. Problem is all Ig et is the LG symbol and the words security error. Unlike other people that have a cause listed, this has nothing. I am able to go into recovery easily. The boot loader still says unlocked (i assume fastboot is an option too?). I installed optimus de (which was residing as a backup on my sd) and the phone boots fine. But as soon as I go back to cm12, it has a security error. I have already taken it upon myself to download lgnpst and the lg drivers.
What are my options here? When it shows this error, it simply powers off after a few seconds.
Click to expand...
Click to collapse
I am not sure, but the "Stock" kernel you flashed might have been for a locked bootloader. It seems backwards, but I know you get that error when you flash a rom, or another kernel that is not for a locked device on a locked bootloader.
Try this:
Restore your CM12 or flash a new one;
flash the rom again so it will be the built in kernel, OR
Flash an alternate kernel.
I am not sure which CM you used but there are a few different ones. If you used the official, I don't think jollaman has support for it yet.
Same goes for the unofficial ls970. They are both built with gproj sources, so you will have to find a kernel that uses the same sources. I believe solid kernel does. It is in the international threads, they use the same sources (not all do, if you see GEE, that is not gproj. that is unified across most of the Optimus G devices).

dopy25 said:
I am not sure, but the "Stock" kernel you flashed might have been for a locked bootloader. It seems backwards, but I know you get that error when you flash a rom, or another kernel that is not for a locked device on a locked bootloader.
Try this:
Restore your CM12 or flash a new one;
flash the rom again so it will be the built in kernel, OR
Flash an alternate kernel.
I am not sure which CM you used but there are a few different ones. If you used the official, I don't think jollaman has support for it yet.
Same goes for the unofficial ls970. They are both built with gproj sources, so you will have to find a kernel that uses the same sources. I believe solid kernel does. It is in the international threads, they use the same sources (not all do, if you see GEE, that is not gproj. that is unified across most of the Optimus G devices).
Click to expand...
Click to collapse
I did indeed use the unofficial built from gproj sources. That was my mistake. I wound up cleaning it out and restarting fresh with the same rom. It's a shame as it runs so well. Thanks for the tip on solid kernel, I'll check it out. Just to be clear, with the ls970 I can basically run any international rom as long as the kernel is right?
Sent from my LG-LS970 using XDA Free mobile app

thejase said:
I did indeed use the unofficial built from gproj sources. That was my mistake. I wound up cleaning it out and restarting fresh with the same rom. It's a shame as it runs so well. Thanks for the tip on solid kernel, I'll check it out. Just to be clear, with the ls970 I can basically run any international rom as long as the kernel is right?
Sent from my LG-LS970 using XDA Free mobile app
Click to expand...
Click to collapse
Actually, the international and the Sprint are basically the same phone. The only difference I know of is that their SIM is removable and ours is built in. So essentially you can use any of their ROMs but you might have data issues. I know any of the ROMs Kevin builds will work for both devices with little to no issues. OMNI runs perfect, the others have data toggle not working and built in messenger not working. OMNI is almost identical to CM at this point. The only thing I can think of right off hand is the messenger and gallery apps are different and I think OMNI has some extra options in the settings of the device.
You want a great rom, try omni. You will not be disappointed. Plus, you can use Jollaman's kernel if you really want to. Use his GEE kernel option. Built in kernel is great for me and I am constantly on my device.
ALSO: there are no mistakes using the official or unofficial. Each has their perks or quirks. Both are amazing.

dopy25 said:
Actually, the international and the Sprint are basically the same phone. The only difference I know of is that their SIM is removable and ours is built in. So essentially you can use any of their ROMs but you might have data issues. I know any of the ROMs Kevin builds will work for both devices with little to no issues. OMNI runs perfect, the others have data toggle not working and built in messenger not working. OMNI is almost identical to CM at this point. The only thing I can think of right off hand is the messenger and gallery apps are different and I think OMNI has some extra options in the settings of the device.
You want a great rom, try omni. You will not be disappointed. Plus, you can use Jollaman's kernel if you really want to. Use his GEE kernel option. Built in kernel is great for me and I am constantly on my device.
ALSO: there are no mistakes using the official or unofficial. Each has their perks or quirks. Both are amazing.
Click to expand...
Click to collapse
Could you link me to the omni for ls970 thread?
Sent from my LG-LS970 using XDA Free mobile app

thejase said:
Could you link me to the omni for ls970 thread?
Sent from my LG-LS970 using XDA Free mobile app
Click to expand...
Click to collapse
It's not specifically for the ls970, it's for any gee* device.
http://forum.xda-developers.com/optimus-g-intl/orig-development/rom-cyanogenmod-12-t2980060
Choose one of the servers, you'll see a link to parent directory, from there you'll see omni and the others.
Any gee*= you might need a different kernel for gee/b.

dopy25 said:
It's not specifically for the ls970, it's for any gee* device.
http://forum.xda-developers.com/optimus-g-intl/orig-development/rom-cyanogenmod-12-t2980060
Choose one of the servers, you'll see a link to parent directory, from there you'll see omni and the others.
Any gee*= you might need a different kernel for gee/b.
Click to expand...
Click to collapse
Thanks for much for the info! I installed Omni from the link and I cannot obtain root now. Says that root is not there. I tried towel root, freegee (refuses to load). Now what?

thejase said:
Thanks for much for the info! I installed Omni from the link and I cannot obtain root now. Says that root is not there. I tried towel root, freegee (refuses to load). Now what?
Click to expand...
Click to collapse
I replied to one of your other posts about root for omni (try to only ask once. It will be answered). Flash superSU from recovery.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

dopy25 said:
I replied to one of your other posts about root for omni (try to only ask once. It will be answered). Flash superSU from recovery.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Thank you and sorry.
Sent from my LGOG with much love to the xda community!