I wanted to create a thread for developers only. Please do not fill this thread with questions or other pointless post.
As of now, test indicate that loki is patched. Grep returns a string of values meaning it is patched.
The only options left that I have not tested are kexec or safestrap. Kexec was patched by current source code but I am not sure if LG has used that code. Safestrap would be our best option but this will not give us AOSP ROMs unless we can get kexec.
If someone wants to work with me on either kexec or safestrap please PM me. Please do not be a user. I need someone who knows what they are doing and can help me get this functional.
Sent from my LG-D950 using Tapatalk
Proof of Loki being patched. http://pastebin.com/xSkUmT42
Sent from my LG-D950 using Tapatalk
Can you dump the abootimg?
I already verified it is patched with Dan R.
Sent from my LG-D950 using Tapatalk
https://www.dropbox.com/s/q24z2ts7n8n5118/aboot.img
Sent from my LG-D950 using Tapatalk
Related
Do we have this capability yet? If so, how do I get it?
Sent from my DROID BIONIC using Tapatalk 2
?
Sent from my DROID BIONIC using Tapatalk 2
By posting in the correct thread. Moved to Q and A
I got init.d support and put a couple scripts one for swap and it works. Rooted ics 6.273 no overclock though we still need the module compiled for this kernel
Do you have a download I can flash?
Sent from my DROID BIONIC using Tapatalk 2
I will work on it tonight i didnt use a flashable zip.
Thanks. I appreciate your time. If all I need to do is drop some files in place, then thats fine also. Whatever is easiest for you.
Sent from my DROID BIONIC using Tapatalk 2
Will it be a great help for bring the ICS to us?
Check it's out
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
mp9_sit said:
Will it be a great help for bring the ICS to us?
Check it's out
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
No not at all. For 1 our device isn't supported and for 2 we have already figured out a workaround to the locked bootloader
Sent from my XT860 using xda premium
It may not be supported yet but if they do add our phone to it, yes it will help. We may have a Kexec kernel but an unlocked bootloader will make things far easier.
Sent from my XT862 using xda premium
Will for one it says page not found so im saying they are not unlocking the bootloader but it it does not matter because of the fact that we have a workaround.
Sent from my Galaxy Nexus using xda app-developers app
leerpsp said:
Will for one it says page not found so im saying they are not unlocking the bootloader but it it does not matter because of the fact that we have a workaround.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Apparently it got posted and pulled and I think reposted. Android police or droid had the supported device list
Sent from my XT860 using xda premium
If you look here (https://motorola-global-portal.cust...sion/L3RpbWUvMTM0NTI1NDk1NC9zaWQvU3VDYlRZM2w=) only the Photon, Xoom, and RAZR dev can be unlocked. And the RAZR dev should be unlocked anyways... it IS the dev edition. This means nothing, and with working Kexec, I don't see why we'd even change since everything now is being written for Kexec and development for this phone ins't exactly active, we essentially have 2 people developing new things for it. There are more GNex kernels than there are D3 devs.
jesusishere said:
It may not be supported yet but if they do add our phone to it, yes it will help. We may have a Kexec kernel but an unlocked bootloader will make things far easier.
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
At this point what difference can it make. Either way we can load a kernel, just need the kernel to be built
Sent from my XT860 using xda premium
Kexec makes this pointless. The reason development stopped initially was because making a ducati binary work with the Gingerbread stock kernel for ICS was impossible. Also doing a kernel module custom was too. Now even though we have ducati and it won't work for the camera we can do other things like Chrome. Also, Hash was going to modify his custom kernel for a camera driver for us as his next approach. This gives us options we didn't have before. The fact that we use Kexec is better because it is flashed on top of the kernel existing at first and it is just a ROM. If it is a bad flash all you have to do is just reflash from Safestrap. We couldn't do that before.
Sent from my xt862 using xda app-developers app
Between our device, and the HTC one X's stock, what are the kernel differences? I'm attempting to port over sense 4.1.1 stock and I only get a reaction out of a 4.1.2 stock kernel(Mexican retail).
Also, is there anyone who could assist with updater scripts? I'm stuck adb pushing through recovery right now and it's very unreliable.
Update: 4.1.1 AT&T stock kernel didn't even get a boot loop. It seems the 4.1.2 retail has some of the needed components but not all of them. Does anyone have any opinions? I cannot get to the point in which I can obtain a logcat. Things would probably get much simpler once I can get logcats.
Sent from my MB886 using xda premium
I dont think you can port the kernel. People usually port SYS. Kernel is device specific. So you take our kernel and get Sys from one x, fiddle with them to boot...
You can port kernel too, but need to decompile it and replace some scripts in ramdisk.... Search in android general section, you may get some tutorials....
Sent from my MB886 using xda app-developers app
Aingaran said:
You can port kernel too, but need to decompile it and replace some scripts in ramdisk.... Search in android general section, you may get some tutorials....
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
My Internet is beginning to work better, so I'll be able to upload stuff soon.
Sent from my mb886 using xda premium
I want to use my T-Mo note 4 for USB keyboard
https://play.google.com/store/apps/details?id=remote.hid.keyboard.client
but I get this error- 'Kernel not supported'
when contacted dev, he suggests to use his patch
https://github.com/pelya/android-keyboard-gadget
for making the kernel compatible.
Can anyone tell me or help me making this, or is there one already working? If so please help me get that if it can work.
I'm using T-Mo note 4(SM-N910T), stock, rooted, deodexed lollipop 5.0.1, with xposed, firmware- COG2, and stock kernel, Build- LRX22C.N910TUVU1COG2, and SE enforcing
Thanks in advance
I'm no expert, but I don't think that patch will work for the Note 4. Did you tell the dev you were using a N4?
Sent from my SM-N910T3 using Xparent Skyblue Tapatalk 2
yeah. told note 4.
he was not sure, and he suggested to get help from xda. someone could make some tweaks or something to make it work. would be much happy.
it is easy when using keepass using a plugin where we can send password without needing to type in.
Way above my pay grade... Sorry.
Sent from my SM-N910T3 using Xparent Skyblue Tapatalk 2
I could have sworn that I could have seen the flashable zip that restores the VoLTE support that's missing in the factory build of CM 12.1. I've been looking for it all day and it's driving me *nuts* that I can't. Could someone please point me in the right direction.
Thx
M
Sent from my DROID Turbo using Tapatalk
Not that I recall. Best I recall someone posted the changes need made and somebody asked "can this be made flashable"? ...
Nevermind. I see the error I made.
Sent from my DROID Turbo using Tapatalk
mrkhigh that's the thread I ended up finding and as a matter of fact, cm is starting to integrate the feature. The first commit I saw regarding it, was tonight's build, not that it works, yet.
Sent from my DROID Turbo using Tapatalk