[Kernel][Loki][8-9-13]Broken Out Modded Stock Kernel

Duples

New Member
Joined
Mar 31, 2013
Messages
5
Reaction score
0
Thanks, I'll get to it when I get a minute. If anyone else wants to, feel free, otherwise i'll eventually get them.

Got'em
im on Jellybean with the Loki kernel; Good Luck :)

boot.img
aboot

EDIT: cant seem to find a aboot.img this this is the best i got.
I got the boot.img from a cwm backup and found the aboot in the directory you said

aboot is at the same place with boot
/dev/block/platform/msm_sdcc.1/by-name/aboot
 
Joined
Feb 8, 2013
Messages
32
Reaction score
0
Congratulations.
Thanks to djrbliss.
I've used his work to make a loki-patched recovery for my Korean version VS930(F160L), it really works and is a perma-recovery!
I think it's the way also works with VS930~
Just compiled from cm10.1 source and is clockworkmod recovery v6 and patched with loki.
Still trying to make a twrp2 but failed for many times, seems to be gpu driver problem.
I'm glad to have the news of removing security error~It really sucks...
If convenient, Can u release the source code of the modded kernel?
I'm still trying to learn how to make a my first modded kernel for my F160L and compile it with myself to remove security error and add some more features such as overclock or more schedular.
I'll be very glad to have your help.
Many and many thanks again!

would the patched version work with our US version?

Thank you
 

asianflavor

Member
Joined
Dec 31, 2012
Messages
105
Reaction score
24
Location
Momence, IL
So did a CM 10.1 get dropped for this phone or not? I maybe getting this phone back next month and would love to start work on this again. If we have a working CM 10.1, I can try to port MIUI to this fine phone. As long as it's CM 10.1.2 before the SElinux merge (MIUI won't boot yet with it). If there is no working CM, I can look at that Korean version again and try to fix that touchscreen issue.
 

asianflavor

Member
Joined
Dec 31, 2012
Messages
105
Reaction score
24
Location
Momence, IL
Alright... a little update. I did find a CM10 ZIP file from the LTE2 in one of my virtual machines. I am pretty sure that I can fix the touch screen issue (video below), but I do need a folder from someone's phone. I need the keylayout folder that is in system/usr. I need to diff those out to see if my theory is correct. I also have an idea that should fix data on the build that I have. With that being said, I should have my $$$ for my Note 3 this Monday. As soon as I have the Note 3, my wife gets my S3, and I get the Spec2 back in my hand. I have no issues testing this on my phone to see if I can fix that touch screen issue. But if anyone is willing to test, I could have something after the looking at the keylayout folder. I have also added the build.prop from the CM10 ROM just show you what I am working with.

[video=youtube;0jUNcmFCXTw]https://www.youtube.com/watch?v=0jUNcmFCXTw[/video]

Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JRO03L
ro.build.display.id=cm_d1lu-userdebug 4.1.1 JRO03L eng.root.20120901.140644 test-keys
ro.build.version.incremental=47741
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Sat Sep  1 14:07:03 KST 2012
ro.build.date.utc=1346476023
ro.build.type=userdebug
ro.build.user=985hPaKicK
ro.build.host=maverick-amd64
ro.build.tags=test-keys
ro.product.model=LG-F160L
ro.product.brand=lge
ro.product.name=d1lu_LGU_KR
ro.product.device=d1lu
ro.product.board=D1LU
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=lge
ro.product.locale.language=ko
ro.product.locale.region=KR
ro.wifi.channels=13
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=d1lu
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=1.53.401.16 CL47741 release-keys
ro.build.fingerprint=tmous/d1lu/d1lu:4.0.3/IML74K/47441.16:user/release-keys
ro.build.characteristics=default
ro.cm.device=d1lu
# end build properties
#
# system.prop for d1lu
#
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
ro.telephony.ril_class=LGEQualcommUiccRIL
ro.telephony.ril.v3=qcomuiccstack
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.baseband.arch=msm
ro.config.lte=true
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
telephony.lteOnGsmDevice=1
ro.ril.shutdown=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.ehrpd=true
ro.config.svlte1x=true
ro.cdma.subscribe_on_ruim_ready=true

persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
#ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
ro.sf.compbypass.enable=1
dev.pm.dyn_samplingrate=1

sys.lge.core.manual=0

ro.sf.lcd_density=320

#LGE_CHANGE_E [email protected] 2011.12.19  LPA Mode off ==> 2012.02.-1 LPA Mode ON
#lpa.use-stagefright=true

#system props for the MM modules

media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true

#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data.netmgrd.qos.enable=true

#system props for time-services
persist.timed.enable=true

# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=analog

# System prop to select audio resampler quality
af.resampler.quality=255

#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
ro.opengles.version=131072

#
# system prop for Bluetooth
ro.qualcomm.bluetooth.dun=false
ro.qualcomm.bluetooth.ftp=true
ro.qualcomm.bluetooth.hfp.wbs=true
ro.qualcomm.bt.hci_transport=smd
ro.bluetooth.request.master=false
ro.bluetooth.remote.autoconnect=true

#
# System prop for switching gps driver to qmi
#
persist.gps.qmienabled=true

#
# System property for cabl
#
ro.qualcomm.cabl=2

#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true

ro.hwui.text_cache_width=2048
ro.nfc.port=I2C
persist.data_netmgrd_mtu=1428
ro.config.vc_call_vol_steps=9
ro.config.vc_call_vol_default=5
ro.hdmi.enable=true
com.qc.hardware=true
com.qc.hdmi_out=true
wlan.chip.vendor=qcom
wlan.chip.version=wcnss
#lpa.decode=true

wifi.interface=wlan0
ro.crypto.fuse_sdcard=true
dalvik.vm.dexopt-data-only=1

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10-20120901-UNOFFICIAL-d1lu
ro.modversion=10-20120901-UNOFFICIAL-d1lu
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.carrier=unknown
ro.setupwizard.enable_bypass=1
dalvik.vm.lockprof.threshold=500
ro.com.google.locationfeatures=1
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaputilization=0.25
dalvik.vm.heapidealfree=8388608
dalvik.vm.heapconcurrentstart=2097152
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
 

Duples

New Member
Joined
Mar 31, 2013
Messages
5
Reaction score
0
Alright... a little update. I did find a CM10 ZIP file from the LTE2 in one of my virtual machines. I am pretty sure that I can fix the touch screen issue (video below), but I do need a folder from someone's phone. I need the keylayout folder that is in system/usr. I need to diff those out to see if my theory is correct. I also have an idea that should fix data on the build that I have. With that being said, I should have my $$$ for my Note 3 this Monday. As soon as I have the Note 3, my wife gets my S3, and I get the Spec2 back in my hand. I have no issues testing this on my phone to see if I can fix that touch screen issue. But if anyone is willing to test, I could have something after the looking at the keylayout folder. I have also added the build.prop from the CM10 ROM just show you what I am working with.

[video=youtube;0jUNcmFCXTw]https://www.youtube.com/watch?v=0jUNcmFCXTw[/video]

Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JRO03L
ro.build.display.id=cm_d1lu-userdebug 4.1.1 JRO03L eng.root.20120901.140644 test-keys
ro.build.version.incremental=47741
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Sat Sep  1 14:07:03 KST 2012
ro.build.date.utc=1346476023
ro.build.type=userdebug
ro.build.user=985hPaKicK
ro.build.host=maverick-amd64
ro.build.tags=test-keys
ro.product.model=LG-F160L
ro.product.brand=lge
ro.product.name=d1lu_LGU_KR
ro.product.device=d1lu
ro.product.board=D1LU
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=lge
ro.product.locale.language=ko
ro.product.locale.region=KR
ro.wifi.channels=13
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=d1lu
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=1.53.401.16 CL47741 release-keys
ro.build.fingerprint=tmous/d1lu/d1lu:4.0.3/IML74K/47441.16:user/release-keys
ro.build.characteristics=default
ro.cm.device=d1lu
# end build properties
#
# system.prop for d1lu
#
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
ro.telephony.ril_class=LGEQualcommUiccRIL
ro.telephony.ril.v3=qcomuiccstack
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.baseband.arch=msm
ro.config.lte=true
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
telephony.lteOnGsmDevice=1
ro.ril.shutdown=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.ehrpd=true
ro.config.svlte1x=true
ro.cdma.subscribe_on_ruim_ready=true

persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
#ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
ro.sf.compbypass.enable=1
dev.pm.dyn_samplingrate=1

sys.lge.core.manual=0

ro.sf.lcd_density=320

#LGE_CHANGE_E [email protected] 2011.12.19  LPA Mode off ==> 2012.02.-1 LPA Mode ON
#lpa.use-stagefright=true

#system props for the MM modules

media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true

#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data.netmgrd.qos.enable=true

#system props for time-services
persist.timed.enable=true

# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=analog

# System prop to select audio resampler quality
af.resampler.quality=255

#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
ro.opengles.version=131072

#
# system prop for Bluetooth
ro.qualcomm.bluetooth.dun=false
ro.qualcomm.bluetooth.ftp=true
ro.qualcomm.bluetooth.hfp.wbs=true
ro.qualcomm.bt.hci_transport=smd
ro.bluetooth.request.master=false
ro.bluetooth.remote.autoconnect=true

#
# System prop for switching gps driver to qmi
#
persist.gps.qmienabled=true

#
# System property for cabl
#
ro.qualcomm.cabl=2

#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true

ro.hwui.text_cache_width=2048
ro.nfc.port=I2C
persist.data_netmgrd_mtu=1428
ro.config.vc_call_vol_steps=9
ro.config.vc_call_vol_default=5
ro.hdmi.enable=true
com.qc.hardware=true
com.qc.hdmi_out=true
wlan.chip.vendor=qcom
wlan.chip.version=wcnss
#lpa.decode=true

wifi.interface=wlan0
ro.crypto.fuse_sdcard=true
dalvik.vm.dexopt-data-only=1

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10-20120901-UNOFFICIAL-d1lu
ro.modversion=10-20120901-UNOFFICIAL-d1lu
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.carrier=unknown
ro.setupwizard.enable_bypass=1
dalvik.vm.lockprof.threshold=500
ro.com.google.locationfeatures=1
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaputilization=0.25
dalvik.vm.heapidealfree=8388608
dalvik.vm.heapconcurrentstart=2097152
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

Was able to zip my keylayout folder
here you go

keylayout
 

asianflavor

Member
Joined
Dec 31, 2012
Messages
105
Reaction score
24
Location
Momence, IL
Was able to zip my keylayout folder
here you go

keylayout

Thanks!

And here's the difference that I was talking about.

Spec2
Code:
key 114   VOLUME_DOWN
key 115   VOLUME_UP
key 116   POWER             WAKE

key 158   BACK              VIRTUAL
key 172   HOME              VIRTUAL
key 139   MENU              VIRTUAL
key 217   SEARCH            VIRTUAL
key 249   APP_SWITCH 	   VIRTUAL

LTE2
Code:
key 114   VOLUME_DOWN
key 115   VOLUME_UP
key 116   POWER             WAKE
key 172   HOME               WAKE

key 158   BACK              VIRTUAL
key 139   MENU              VIRTUAL

This is what Miller and I was talking about when back in the day when I got this phone. The LTE2 has a home button like the S3 where the Spec2 has the blue touch buttons. So in theory, all I have to do is switch out the layout folder in the LTE2 CM10 ROM that I have, and the touch screen issue should be fixed...but only in theory. When you recovery the phone with the CAB file, the touch screen issue stayed. If @layvin1 is up for some testing, I could have something by Sunday. I will be busy all day tomorrow. But when I get my new phone, I will get my wife's Spec2 and I have no issues testing on that. Now I'm going to try to restore my internal storage card on my S3 since one of my stupid fingers decided to hit the delete button in root explorer.
 

dalg91

New Member
Joined
Sep 29, 2013
Messages
7
Reaction score
0
I have been going crazy trying to find more information so I can contribute to making a CM 10.1/10.2 build for this phone. I have been barely able to find this info for getting past the bootloader and have just been trying to see what other info I can find. Anyway I am pretty new to building ROMS and would love to learn/assist so if any of you who are building the roms need an extra hand PLEASE PLEASE PLEASE message me. I don't have a job at the moment so lots of free time for a week or two until my new job starts. I desperately want this verizon bloatware gone and to help out the CM community.
 

Layvin1

Member
Joined
Jan 13, 2013
Messages
68
Reaction score
18
@asianflavor.
I recently lent my Spec2 to my buddy to see if he can get it working on a straight talk plan. From what I understand he should be able to. If he can't I'll get it back and be willing to test anything.
 

mordant80

Member
Joined
Jan 25, 2010
Messages
78
Reaction score
1
Location
West Virginia
mtmichaelson, do you know if the kernel in the new OTA is any different from the previous kernel? If so any chance of getting an updated broken out loki kernel?

Everyone else: Any of you that havent updated yet mind posting a screenshot of your software information screen under settings/about phone?
 

ozozznozzy

New Member
Joined
Jun 2, 2013
Messages
3
Reaction score
0
So it seems that communication on this thread has come to a standstill. Any news on CM10?
 

JimiMack

Member
Joined
Jan 4, 2013
Messages
130
Reaction score
12
Location
Long Island NY
No news and I do not expect to see this unit get much love from CM or any other Rom. I like the phone but I am already planning it's replacement unit just because of the lack of development. Sad because it is such a nice unit just too bad it is so locked down.
 

asianflavor

Member
Joined
Dec 31, 2012
Messages
105
Reaction score
24
Location
Momence, IL
I have a test build of CM10 that I gave to bullriders. He bricked his phone from the last VZW update. Don't know if he going to try to flash the CM ROM. Don't blame him if doesn't. I got my Note 3 just this past Friday and have been playing with that and dealing with some issues at home...(2 routers blew on me, sick kids...). I still need to transfer my old S3 to my wife and get the Spectrum 2. I am going look into everything again and make sure this thing does not screw up the touch screen like it did last time. Plus I am trying to learn how build modules for Xposed. Not enough time. I may just even try to get a bloat-free ROM with the loki kernel out first with Xposed in it. Sorry that I haven't done too much...
 

JimiMack

Member
Joined
Jan 4, 2013
Messages
130
Reaction score
12
Location
Long Island NY
I have a test build of CM10 that I gave to bullriders. He bricked his phone from the last VZW update. Don't know if he going to try to flash the CM ROM. Don't blame him if doesn't. I got my Note 3 just this past Friday and have been playing with that and dealing with some issues at home...(2 routers blew on me, sick kids...). I still need to transfer my old S3 to my wife and get the Spectrum 2. I am going look into everything again and make sure this thing does not screw up the touch screen like it did last time. Plus I am trying to learn how build modules for Xposed. Not enough time. I may just even try to get a bloat-free ROM with the loki kernel out first with Xposed in it. Sorry that I haven't done too much...

A completely de-bloated stripped down rom is always the first step, take out all the Verizon and LG addons. Thank you.
 
Top