== Warning!! ==
This is at your own risk and only for unlocked bootloaders, don't try this on a locked bootloader device!!
I'm not responsible for damage to your device!
== Info ==
In this post, I would like to explain what kexec-hardboot patch is.
@kernel developers: Feel free to add my patch into your kernels, the patch can be found on my github: Kexec commits. You can just cherry-pick the commits, but I'll update my kernel repo with a new branch so the patch will be only 1 commit.
== What is kexec? ==
It is syscall of Linux kernel, which allows you to boot another Linux kernel without restarting the device - "Linux boots itself". The functionality is equivalent to fastboot -c *cmdline* boot zImage initrd.img, but without PC and fastboot. It is fairly known thing, so more info at wikipedia and man kexec.
Standard kexec call unfortunatelly does not work on Nexus 4. It freezes somewhere, and it is very difficult to find out where - probably some of the drivers are not shut down/re-initialized properly, it is a commong thing among Android devices, which is why kexec-hardboot was made.
== What is the difference between normal and hardboot exec? ==
Kexec-hardboot patch adds a real device restart to that process, so that all the drivers can be properly reinitialized. It stores new kernel to RAM, reboots the device as usual, and kernel from boot partition immediately jumps to the one which was stored to RAM before reboot.
Unlike grouper's kexec-hardboot patch, this one only requires the host kernel to be patched. This is one of the improvements I made, and I think it is pretty significant.
To sumarize the process:
kexec --load-hardboot.... is called and kernel it loaded into RAM.
kexec -e is called. Special info is written to memory (to area which is not overwritten on reboot) and the device is rebooted.
After reboot, very early in the boot process, kernel checks if that special info is present in RAM and if so, it loads new kernel from RAM and jumps to it.
Kexecd' kernel starts and boots.
For more info, read the original thread.
== Instructions: ==
1) Download all required files:
- The host kernel
- the kexec binary
- Kexec script
- kernel files you want to kexec-hardboot
2) Then you need to fastboot flash the host kernel:
Code:
fastboot flash boot stock-290-TWRP-kexec.img
3) Put kexec binary, kexec.sh, initrd.img and zImage-dtb inside cache
4) Fire up adb and insert the following commands:
Code:
adb shell
su
cd cache
chmod 0755 kexec
sh ./kexec.sh
== Downloads: ==
- Host kernel 4.3 290: Sony 290 kexec host kernel
- kexec binary: kexec binary
- CM kernel to hardboot as test: cm test files
- kexec script: kexec script
== Authors: ==
This patch was made by Mike Kasick for Samsung Epic 4G. Since that, it was ported to several devices, one of them is Asus Transformer TF201 - I used patch from TF201 and modified it a bit (basically just changed few SoC specific constants). People at #ubuntu-arm helped me out with that, thanks.
For hammerhead, Tassadar improved the patch a bit - only the host needs to be patched now and Tassadar added support for DTB.
Last but not least for Xperia Z1 and Z Ultra I ported the patch to our sony 4.3 kernel sources. But most work was done by the awesome other devs
XDA:DevDB Information
[UB]Xperia ZU kexec patch v1 TESTERS needed [18/01/14], a Tool/Utility for the Sony Xperia Z Ultra
Contributors
krabappel2548
Version Information
Status: Testing
Current Stable Version: V1 and future versio
Stable Release Date: 2014-01-18
Created 2014-01-18
Last Updated 2014-01-18
Purpose of this kexec patch?
Now I have this working, I'm going to work on a multiboot solution for people with unlocked bootloaders.
Other kernel developers
I have my sources on github. If you wanna make a host kernel with kexec patch, feel free to use my patches on github:
https://github.com/Krabappel2548/android_kernel_sony_msm8974-kexec/commits/master
trying another kernel then cm to kexec boot:
When you compile the kernel don't take the zIamge, but the zImage-dtb from arch/arm/boot.
kexec needs the zImage with dtb appended to it. This is just the way it works.
Also don't forget to take the right ramdisk for the kernel and call it initrd.img.
Are you back ?
Sent from my C6806_GPe using Tapatalk
gbohm said:
Are you back ?
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
hope so. i would love omni to be complete so we can have multi-window
Welcome back Mr Apple
It will be interesting to see how this get going
Welcome back Mr Apple
It will be interesting to see how this get going
Click to expand...
Click to collapse
Don't call me Mr Apple :banghead:
Me hate apple and love Android
Ps: just kidding
EDIT: did someone had the guts to test this? I need to know if it works to make multiboot
Sent from my C6903 using xda app-developers app
krabappel2548 said:
EDIT: did someone had the guts to test this? I need to know if it works to make multiboot
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Dear Tim Cook, i'm not even sure what this is, so that's a negative, Sir :cyclops: I do understand the basics of this, but i'm not sure how i can test it, or how i'll know what to look for.
krabappel2548 said:
EDIT: did someone had the guts to test this? I need to know if it works to make multiboot
Click to expand...
Click to collapse
You write
Put kexec binary, kexec.sh, initrd.img and zImage-dtb inside cache.
Click to expand...
Click to collapse
And where to take them: initrd.img and zImage-dtb?
Feodorus 4PDA said:
You write
And where to take them: initrd.img and zImage-dtb?
Click to expand...
Click to collapse
These are the cm test files you can download
Sent from my C6903 using xda app-developers app
Does this mean we can have sony rom and GPE roms duel booting.
krabappel2548 said:
These are the cm test files you can download
Click to expand...
Click to collapse
Explain NUB how to make:
Fire up adb and insert the following commands:
Click to expand...
Click to collapse
?
Had to
jutley said:
Does this mean we can have sony rom and GPE roms duel booting.
Click to expand...
Click to collapse
I think the whole idea is for them not to duel but to peacefully coexist
brashmadcap said:
I think the whole idea is for them not to duel but to peacefully coexist
Click to expand...
Click to collapse
Well that's no fun! Brace yourselves for an epic war between the ROMs. One will boot, one will noot(?) Tune in at eleven to find out.
brashmadcap said:
I think the whole idea is for them not to duel but to peacefully coexist
Click to expand...
Click to collapse
When I'm finished you should be able to install more then 1 rom and choose which one you want to boot in multirom menu before booting up
Sent from my C6903 using xda app-developers app
Next time I'm in Euroland I'll buy you a beer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my C6903 using xda app-developers app
krabappel2548 said:
View attachment 2529583
Click to expand...
Click to collapse
Tell where MultiROM for Z1 and ZU can download?
Thanks.
Feodorus 4PDA said:
Tell where MultiROM for Z1 and ZU can download?
Thanks.
Click to expand...
Click to collapse
I'm working on it almost finished
Sent from my C6903 using xda app-developers app
krabappel2548 said:
I'm working on it almost finished
Click to expand...
Click to collapse
For TX can be ported? Plizzzzz
krabappel2548 said:
I'm working on it almost finished
Click to expand...
Click to collapse
OKEY NICE
Related
R800x Users, I have just compiled a kernel based of the 3.0.1.E.0.88 Sources.
I need a few testers, Big update, read the update section for v.2 (2012 Feb 12)
Pax
Update 01: 2012 February 08 1500 CST:
Code:
Working:
Stock kernel (no overclocking yet)
Boots
No random reboots (yet)
Autobrightness is disabled (as it was in 2.3.3 update)
Not Working:
Wifi (came from DooMLoRD's Kernel, need to check coming from stock update: need to flash Doom's stock wifi)
Recovery (need to look into this, in the meanwhile, use market link below)
Will be added Later:
Governers
I/O Schedulers
Overclocking
Auto-rooting
Note: This kernel's ramdisk is ro.secure = 0, which means it can be rooted, you'll just have to do the work.
Update 2012 February 08 -- 1900
Attached boot.img
Update: 2012 February 12 -- 2020
Code:
Big update to the kernel
I switched from my ramdisk, which ended up being a headache to DooMLoRD's v10 ramdisk
That means:
Wifi Works
Autoroot (should) work (I haven't tested it yet)
Recovery Works
New Splash on boot (thanks [URL="http://forum.xda-developers.com/showthread.php?t=1494076"]KeiranFTW[/URL] )
What I've added:
Overclocking is possible up to 2.0ghz (be warned, I have not had a chance to completely test it out, and my device only works up to 1.6ghz) (Freqs are from DooM v10)
Governors added:
brazillianwax
smoothass
smartassv2
savagedzen
interactivex
lagfree
Scary
smartass
Original governers
UPDATE: 2012 Feb 12 1055
Noticed that when I switched to DooMLoRD's ramdisk, autobrightness got re-enabled. Fixed that. Uploaded new kernel.
UPDATE: 2012 Feb 13 1335
Changed version from .2 to 1.0
Added IO Schedulers:
Anticipatroy
CFQ
V(R)
SIO
UPDATE: 2012 Feb 13 -- 1400
Realized last update unintentionally removed governors, as soon as I get a stable internet connection, i'll upload completely working kernel.
UPDATE: 2012 Feb 13 -- 1525
Uploaded fixed kernel.
Note: I am not to be held responsible if your device fails you. By flashing this, you are taking your device's ability to work into your own hands. ESPECIALLY WITH OVERCLOCK. TEST BEFORE YOU DECIDE TO SET ON BOOT. IF YOUR PHONES FAILS YOU, IT IS YOUR RESPONSIBILITY
Follow these instructions from Doom if you don't know what to do
download the boot.img
save the boot.img in the folder with fastboot binaries (fastboot.exe files)
power down device
start device in fastboot mode
use the following command to flash the boot.img
Code:
fastboot -i 0x0fce flash boot boot.img
reboot phone and enjoy the kernel
What's Left to be added:
What do people want?
To get into recovery, use the exact same key as you would on DooM's
Sources for code:
Github -- Ramdisk (From ftf, if you really want to mess with this, have fun, but it's not worth the time.): https://github.com/paxchristos/R800x-Ramdisk
Github -- Kernel Source: https://github.com/paxchristos/R800x-2.3.3-Kernel
Big thanks to Keiran/Doom for the help in getting this to work.
Reserved for future use
Any modifications regarding I/O schedulers & CPU governors? Any additional kernel modules?
CrimsonKnight13 said:
Any modifications regarding I/O schedulers & CPU governors? Any additional kernel modules?
Click to expand...
Click to collapse
There well be, as of right now, this is pretty much an alpha release. I'm in class for a little bit, then I'm going to actually flash it (
I just did a fastboot boot) and start bug checking ...
Sent from my R800x using Tapatalk
paxChristos said:
R800x Users, I have just compiled a kernel based of the 3.0.1.E.0.99 Sources.
I need a few testers, I will post soon (I literally just got it to boot)
expect more info soon!
Pax
Click to expand...
Click to collapse
I'm game for trying it out.
With this kernel we can overclock? Like with SetCPU?
I'll try this later when some other stuff is fixed. But nice job.
Is this a kernel for 2.3.3?
What's to prevent you from grabbing sources from a later version and doing this?
i think this kernel is for unlocked bootloaders???
Because locked can't flash kernels
nickholtus said:
i think this kernel is for unlocked bootloaders???
Because locked can't flash kernels
Click to expand...
Click to collapse
There can be kernels that can be flashed with CWM Recovery.
I'm SOOO ready to test! Hit me with your best shot!
EDIT: Do you think this kernel will eventually evolve into a kernel that will be able to boot Cyanogenmod and/or MIUI? I'm assuming that's what you're aiming for. lol
Nope we can't flash kernels with cwm on SEMC devices
PariahLantern said:
Is this a kernel for 2.3.3?
What's to prevent you from grabbing sources from a later version and doing this?
Click to expand...
Click to collapse
I have a R800x (the Verizon Xperia Play) and I play to focus development on sources exclusively for the R800x. If the R800x gets new sources, I will update code based on that, not sources for GSM.
nickholtus said:
i think this kernel is for unlocked bootloaders???
Because locked can't flash kernels
Click to expand...
Click to collapse
You are correct sir, I was updating between classes and posted the wrong info *fixed*
Selim873 said:
There can be kernels that can be flashed with CWM Recovery.
I'm SOOO ready to test! Hit me with your best shot!
EDIT: Do you think this kernel will eventually evolve into a kernel that will be able to boot Cyanogenmod and/or MIUI? I'm assuming that's what you're aiming for. lol
Click to expand...
Click to collapse
Sorry, only for unlocked boot loaders, my bad
Eventually I might get into other development. First I wanna get this working, perfectly.
nickholtus said:
Nope we can't flash kernels with cwm on SEMC devices
Click to expand...
Click to collapse
Yupp, the /boot partition is locked so we can't flash kernels that way
(hint: if you do (from terminal emulator as root) cat /proc/mtd and you see /boot, you can use CWM to flash kernels.)
Kernel v.1 is uploaded and attached to post 1
Selim873 said:
There can be kernels that can be flashed with CWM Recovery.
I'm SOOO ready to test! Hit me with your best shot!
EDIT: Do you think this kernel will eventually evolve into a kernel that will be able to boot Cyanogenmod and/or MIUI? I'm assuming that's what you're aiming for. lol
Click to expand...
Click to collapse
Probably. We are gonna end up finding another exploit.
paxChristos said:
Yupp, the /boot partition is locked so we can't flash kernels that way
(hint: if you do (from terminal emulator as root) cat /proc/mtd and you see /boot, you can use CWM to flash kernels.)
Click to expand...
Click to collapse
nope u cant see /boot and it cant be flashed to using CWM (on xperia devices)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DooMLoRD said:
nope u cant see /boot and it cant be flashed to using CWM (on xperia devices)
Click to expand...
Click to collapse
Couldn't we not "find" the boot partition values and then mount the boot partition? Would require a little kernel editing but would be well worth it.
KeiranFTW said:
Couldn't we not "find" the boot partition values and then mount the boot partition? Would require a little kernel editing but would be well worth it.
Click to expand...
Click to collapse
I didn't think about that! I would love to try to get at it, but I'm only a user and know nothing of development... I'm sure that'll get cracked eventually.
Selim873 said:
I didn't think about that! I would love to try to get at it, but I'm only a user and know nothing of development... I'm sure that'll get cracked eventually.
Click to expand...
Click to collapse
The only problem (that I can see) with what Keiran is suggesting is that the you'd need a custom kernel to affect the /boot partition, which once again, makes it useless for anybody with a locked bootloader...
paxChristos said:
The only problem (that I can see) with what Keiran is suggesting is that the you'd need a custom kernel to affect the /boot partition, which once again, makes it useless for anybody with a locked bootloader...
Click to expand...
Click to collapse
I understand that, but since it was based off the stock kernel, would the values be the same for everybody with a locked bootloader? I know that you meant when you said that, but what I was thinking was that someone could dig around the kernel to find those values and what trigger the /boot partition in the first place, then use the correct adb shell command, whatever it is, to make that show up on locked devices. Whether the device is on it's recovery mode (Back+Power) or fastboot (Search+Power) state. Like I said, I don't know anything about developing, and I might just be walking off a cliff at the moment, but it's just a thought.
EDIT: As in looking and thinking on the modified "stock" kernel, and applying on the locked devices. Trial and Error.
Just a quick update,
I'm trying to get the overclocking working, but right now it's being a stone cold b*tch with compiling
As soon as I get it working, i'll upload a new kernel version
Code:
For Xperia Z Ultra only!
*** Disclamer
This is an AOSP kitkat rom for Xperia Z Ultra only!
[B][COLOR="Red"]I am not responsible if you brick your device[/COLOR][/B], but I will try to help you if things go wrong.
Introduction
This is a new rom I created, the main cause of RevolutionRom is to have a vendor tree, hardware repos and AOSP repos with some small changes for Xperia devices. This will make it a lot easier in the future to provide and update AOSP roms on Xperia devices.
You can find my sources on github: RevolutionDev github
Click to expand...
Click to collapse
Features
- Packed with RevolutionKernel: RevolutionKernel thread
-Android 4.4
Click to expand...
Click to collapse
Images
- For more images check the screenshots tab of this devdb project
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Installation instructions
Warning! The recovery in the Ubuntu Touch device image doesn't recognise external sd (Micro SD)
- Reboot into fastboot
- Flash boot.img and system.img:
- fastboot flash boot boot.img
- fastboot flash system system.img- Reboot into recovery
- Do a factory reset
- Flash gapps and supersu zip
- Reboot into system and anjoy the power of RevolutionRom android kitkat!
Click to expand...
Click to collapse
Download
- RevolutionRom Boot.img
- RevolutionRom System.img
- 4.4 ART-runtime compatible gapps
- Supersu
Click to expand...
Click to collapse
Project status
Working
Code:
- ADB
- Display
- Touchscreen
- Wifi
- Camera
- Sensors
- External Micro-SD
- GPS
- Audio playback
- Ril: Cell reception, calling, messaging
- Audio
Not woking
Code:
- Bluetooth
- Video Playback (HW decoder) [B][COLOR="Blue"]You can use MXPlayer to play almost every video with sw decoding for now[/COLOR][/B]
- Mobile Data
Click to expand...
Click to collapse
Changelog
Code:
== 13/11/2013 ==
- Migrated to almost complete AOSP
- Camera should be fully functional
- Some minor bug fixes
- Small improvements on ril
== 11/11/2013 ==
- Initial release
Click to expand...
Click to collapse
Thanks to:
Code:
- Google for the amzingly optimized Android kitkat :)
- CM team for 4.3 base (device tree)
XDA:DevDB Information
[Rom]RevolutionRom, Pure AOSP kitkat project for Xperia [Android 4.4][11/11], a ROM for the Sony Xperia Z Ultra
Contributors
krabappel2548
Version Information
Status: Beta
Beta Release Date: 2013-11-11
Created 2013-11-11
Last Updated 2013-11-29
odexed gapps works best. for the time being its not a daily.
But its amazingly fast. Not so stable thou but it will get there im sure
Your the man krabappel2548
ps. DONT activate ART as its a bit to early to goof around with that...
Thanks very much for this. Are you in need of logcat output to diagnose any issues?
Also, I've been wondering: As we share the same soc as the N5, is it possible to use the binaries from that device to get HW accelerated video? I know this is a dumb question, but you've got to learn somehow!
Thanks,
Sweet! Would be nice to have calling fully working, so i think i'll wait
Is it OK to test and then restore 4.3 from a nandroid?
baileyjr said:
Is it OK to test and then restore 4.3 from a nandroid?
Click to expand...
Click to collapse
I guess? Or?
Sent from my C6833 using Tapatalk
LordManhattan said:
I guess? Or?
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Well I restored from an nandroid. Didn't work first time but was ok when I formatted data/system/ manually.
Only issue is that the play store now won't update my google apps, maps for example, now i'm back on 4.2. "Application requires newer SDK version". I think that may be temporary mind as google play still seems to think I'm on 4.4
I'll try updating them again later.
look forward for update version!
Thank god this isn't good enough to be a daily driver!
I just sent in my ZU for a replacement and would've been heartbroken to have to wait
Sent from my C6902 using Tapatalk
Gave it a go!
.
On first boot I get com.android.phone crash. Which makes sense.
Every touch makes a red square around the edge of the display and it reboots.
Couldn't unlock the screen and no wizard for first clean install (to setup accounts, etc)
That is the furthest I was able to get.
ps. Followed installation method.
Thanks for pushing 4.4 to XZU.
Sent from my Xperia Z Ultra using XDA Premium 4 mobile app
Anxiously waiting for this!
TREMER said:
.
On first boot I get com.android.phone crash. Which makes sense.
Every touch makes a red square around the edge of the display and it reboots.
Couldn't unlock the screen and no wizard for first clean install (to setup accounts, etc)
That is the furthest I was able to get.
ps. Followed installation method.
Click to expand...
Click to collapse
Yeah I got that with normal gapps. It's more stable with pa-gapps-ODEXED
Sent from my Xperia Z Ultra using Tapatalk 4
Reb0rn said:
Yeah I got that with normal gapps. It's more stable with pa-gapps-ODEXED
Sent from my Xperia Z Ultra using Tapatalk 4
Click to expand...
Click to collapse
I used the gapps from the op which I understood to be odexed gapps. Unless I'm missing something?
TREMER said:
I used the gapps from the op which I understood to be odexed gapps. Unless I'm missing something?
Click to expand...
Click to collapse
Works for me... I'd start over mate.
Heres a dropbox link you the odexed gapps, but they "should" be the same as the ones you have...
https://www.dropbox.com/s/dxl7pcpfkxy7xqx/pa_gapps-ODEX.zip
Working on ril issues (phone crash, mobile data and calling)
Sent from my Xperia Z1 using xda app-developers app
krabappel2548 said:
Working on ril issues (phone crash, mobile data and calling)
Sent from my Xperia Z1 using xda app-developers app
Click to expand...
Click to collapse
Awesome. Can't wait.
Sent from my C6833 using Tapatalk
---------- Post added at 01:02 AM ---------- Previous post was at 12:59 AM ----------
One stupid question: I haven't flashed any ROMs on the Ultra yet, but why do we have to flash boot.img and system.img before we flash in recovery? Why can't we just flash them in recovery and be done with it?
Sent from my C6833 using Tapatalk
I'll be all over this once the issues are fixed, lol. Great work tho!!
Sent From My Bada$$ XZU
krabappel2548 said:
Code:
For Xperia Z Ultra only!
*** Disclamer
This is an AOSP kitkat rom for Xperia Z Ultra only!
[B][COLOR="Red"]I am not responsible if you brick your device[/COLOR][/B], but I will try to help you if things go wrong.
Introduction
Images
Installation instructions
Download
Changelog
Thanks to:
Code:
- Google for the amzingly optimized Android kitkat :)
- CM team for 4.3 base (device tree)
XDA:DevDB Information
[Rom]RevolutionRom, Pure AOSP kitkat project for Xperia [Android 4.4][11/11], a ROM for the Sony Xperia Z Ultra
Contributors
krabappel2548
Version Information
Status: Beta
Beta Release Date: 2013-11-11
Created 2013-11-11
Last Updated 2013-11-11
Click to expand...
Click to collapse
Thanks a lot,though there is something wrong with the system,causing it reboot.We are looking forward to the next update.Thanks for your work again.
LordManhattan said:
Awesome. Can't wait.
Sent from my C6833 using Tapatalk
---------- Post added at 01:02 AM ---------- Previous post was at 12:59 AM ----------
One stupid question: I haven't flashed any ROMs on the Ultra yet, but why do we have to flash boot.img and system.img before we flash in recovery? Why can't we just flash them in recovery and be done with it?
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
The boot image (boot.img) is composed of both the kernel and the initial root file system (initramfs). It's related to some sort of 'insecure boot' which is requisite for root and other stuff. Hence it is advised to flash it before flashing the ROM. Also, each rom had a different one, just because the boot.img of one rom works with the other,it doesn't mean it fully 'compatible'.
I dunno about the system image. That's the first time I've seen it being flashed from fastboot.
Sent from my C6902 using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
neXusCM
CHANGE-LOG:
Build # 5
-CM latest source
-Linaro 4.8
-All audio video patches and updated binaries,libs from my PA tree
-Rear mic fixes also included
RECOMMENDED KERNEL: STOCK 205
Build # 4
- CM updated source and new apps.
- New files from 205 firmware
- Removed old build props and updated with new ones.
- Glove mode patch removed for touch stability
Build # 3
- CM source update
- fixed and updated ramdisk
- Sepolicies restored to original
- Userdebug build instead of eng
Build # 2
fixed ramdisk
Build # 1
-Initial Build
Click to expand...
Click to collapse
Click to expand...
Click to collapse
DOWNLOAD:
Build # 5:
http://d-h.st/K8H
NOTE: Flash this for Audio Echo Fixes and Volumes
https://mega.co.nz/#!vQp1BCha!kvuw31Bx5r03qf_b3U8vMZ64qU9doBQc4f6vsK6nH48
Build # 4:
https://mega.co.nz/#!HYxziQZK!ERbol6pVsKuiMPnxw4vhO-JYZGRPmTPjl-jvdlMtR8I
Build # 3:
http://d-h.st/EUK
Build # 2:
https://mega.co.nz/#!WApk0QaL!oIsNBseh-7bhbrEp9fMXFUtSGGw6TNpPdSvtZEq1ICc
Build # 1:
http://d-h.st/QdX
Click to expand...
Click to collapse
Click to expand...
Click to collapse
GAPPS:
http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Locked BLs FTF Files:
Kernel 205 FTF:
https://mega.co.nz/#!zJohFDzb!bgo6C1MjtiBdVQZXkjl-r-n9wQAkTAsRzo0K5ynERWk
Kernel 201 FTF:
http://d-h.st/DgV
Click to expand...
Click to collapse
Click to expand...
Click to collapse
WORKING:
Everything apart from below
Click to expand...
Click to collapse
NOT WORKING:
Rear MIC, although i havent confirmed myself
Use SPIRITFM for Radio
Click to expand...
Click to collapse
Click to expand...
Click to collapse
INSTRUCTIONS:
1. I suppose you have a custom recovery. (Philz, TWRP, CWM are all good to go)
(Use latest LBL recovery. If you can't find it, go die !!!)
2. I hope you can download the zip from link below in Download category.
3. Place it on SD Card and boot to recovery and flash it.
4. Wipe factory reset (dont argue why full reset, and why wipe AFTER installing zip)
5. Use flashtool (for locked) to flash 205 kernel ftf.
Use fastboot (for unlocked) to flash anything u want which is cm11 compatible.
6. Reboot. (AND SUFFER if you forgot to flash GAPPS, you deserve this)
7. Reboot again to recovery to flash GAPPS and accept your insolence.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
SOURCE:
https://github.com/neXusPRIME/android_device_sony_huashan
https://github.com/neXusPRIME/android_vendor_sony
https://github.com/neXusPRIME/android_kernel_sony_msm8960t
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CREDITS:
-bagyusz
- MrSteve555
-dh.harald
-KeiranFTW
-cray_Doze
-adfad666
-davidmarco
-dssmex
-DooMLoRD
-Cyanogenmod team
Click to expand...
Click to collapse
Click to expand...
Click to collapse
So If coming from 4.3 ( .201 FW )...Wipe data/cache/dalvik then flash ROM? then reboot after first boot?
thanks
Revontheus said:
So If coming from 4.3 ( .201 FW )...Wipe data/cache/dalvik then flash ROM? then reboot after first boot?
thanks
Click to expand...
Click to collapse
Yes, u can keep 201 kernel stock or optionally 205 via flashtool.
Although i only flashed via PHILZ.
What does "GSM/MOBILE BASEBAND: NOPE" mean?
Tia!
Sent from my C5303 using XDA Free mobile app
air001 said:
What does "GSM/MOBILE BASEBAND: NOPE" mean?
Tia!
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
don't work.
"What does "GSM/MOBILE BASEBAND: NOPE" mean? "
This mean phone calls don't work? And 3G doesn't work?
Precisely !
So then what does this rom good for?
It's useless right now but I hope the bugs will be fixed in the next version.
@neXus PRIME
I just want to report that flashing via TWRP doesn't fix baseband issue. Small step forward, but now it's clear that the issue is somewhere in source.
I'd suggest you to start from strach and use unmodified bagyusz sources. After that there will be time to add some updates. If that won't work, it means that 4.4.3 brings new RIL management or something similiar. Even one commit could break it.
Raz9 said:
It's useless right now but I hope the bugs will be fixed in the next version.
Click to expand...
Click to collapse
I also hope your useless feedback is also fixed in future versions.
I am filling in VOLUNTARILY for bagyusz until he is back, not my duty ... and people askedme to port 4.4.3.
Stay away from this development threads if u are allergic to bugs.
MrSteve555 said:
@neXus PRIME
I just want to report that flashing via TWRP doesn't fix baseband issue. Small step forward, but now it's clear that the issue is somewhere in source.
I'd suggest you to start from strach and use unmodified bagyusz sources. After that there will be time to add some updates. If that won't work, it means that 4.4.3 brings new RIL management or something similiar. Even one commit could break it.
Click to expand...
Click to collapse
Thanks, The sources are UNMODIFIED. Its something to do with releasetools maybe
The only change i do is delete the line:
TARGET_RELEASETOOLS_etcetc..... Could it be the reason?
Thanks given for @neXus PRIME and @MrSteve555, appreciate the efforts.
Would love an update on LBL Slimkat if possible
Sent from my C5303 using Tapatalk
@neXus PRIME
If you didn't touch the dev trees, CM sources, and you only modified releasetools, I'd suspect the root of the problem there.
MrSteve555 said:
@neXus PRIME
If you didn't touch the dev trees, CM sources, and you only modified releasetools, I'd suspect the root of the problem there.
Click to expand...
Click to collapse
But it has nothing related to baseband... i searched and lot of threads tagged cm11 unknown baseband many xperia phones too. There is a fix floating around. Please help me search it.
One such post is:
http://forum.xda-developers.com/showpost.php?p=52006785&postcount=6
in here:
http://forum.xda-developers.com/showthread.php?t=2720512
Flashing LBL Cm11 via Twrp and Philz gave me no baseband only via Cwm did it work.
But I had no WiFi Hotspot on any.
Sent from my C5303 using Tapatalk
Treboeth said:
Flashing LBL Cm11 via Twrp and Philz gave me no baseband only via Cwm did it work.
But I had no WiFi Hotspot on any.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Which CWM made it work??? I can fix hotspot but need to know the CWM version.
Same baseband issue here too:
https://code.google.com/p/freexperia/issues/detail?id=2419
neXus PRIME said:
Which CWM made it work??? I can fix hotspot but need to know the CWM version.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2649923
This is the one I used but may have caused confusion I meant this rom http://forum.xda-developers.com/showthread.php?t=2735975
I found that:
There is a fix in the first post, maybe it will be helpful.
http://forum.xda-developers.com/showthread.php?t=2762703
Also, we should have in mind that the ramdisk changes when the Android build changes, and running new build on kernel/ramdisk can lead to weird issues. Maybe not in our case but worth checking.
I know the releasetools aren't connected to baseband but it's the only thing that was changed by you.
Also, flashing basebands after flashing the ROM doesn't do anything, it still stays unknown. So the issue really goes deeper than the baseband.
One thing to note: When FXP320 was released, the ramdisk was broken and baseband wasn't working, but flashing kernel from FXP319 fixed the issue. But when someone combined FXP320 kernel and FXP319 ramdisk, everything also worked fine
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lollipop Kernels
Code:
#include <std_disclaimer.h>
#include <respect.h>
#include <courtesy.h>
/*
*
* We are not responsible for your device.
* You alone take the inital risk by flashing files to your device.
* I test all kernels on my development device before I release them.
* These kernels are made in my spare time, with that being said , Please respect that.
* Please treat others with repect in this thread.
* You were the new guy or girl at one time or another.
* Please help and instruct others.
*/
Downloads
@ΠΣΘ Adrenaline Rom
Sense 5.0.1 Powerhouse kernel
Also if you are applying settings on boot in your favorite kernel app, Make sure you clear app cache before flashing other wise you might not boot.
Changlog and source link in post #2
Happy flashing!
Changelog:
Powerhouse:
Voltage control
OC to 2.5Ghz
UC to 2.68Ghz
GPU OC to 650Mhz
Sweep2sleep
Ondemandplus CPU governor
Simpleondemand GPU governor
I/O schedulers added: sio, vr, fiops and bfq
Kexec-hardboot for MultiROM support
** Aside from the commits above there are various improvments to the code which can be found in my source **
Source
Nicely done:good:
TonyStark said:
Nicely done:good:
Click to expand...
Click to collapse
thank you sir, for all you done.
Thanks for bringing more kernels for Lollipop
Hey all,
I know this is the Lollipop Thread but I see the other one barely had any use since September of 2014. I was hoping someone could point me in the right direction to download this kernel on the "old" 4.4.4 KK for CM11 on the HTC One M8 Verizon variant. I am not using MultiROM but may in the future. What are people using as their settings? The Furnace Kernel I'm using doesn't allow for MinFree Control. I could edit that manually but I'm not well versed in that. Thanks!
Always dig having more kernels to choose from!
Em....My device is M8tl (China market )I really want someone can make a GPE or CM kernel FOR US...All users of M8tl will be thankful...
hellobbn said:
Em....My device is M8tl (China market )I really want someone can make a GPE or CM kernel FOR US...All users of M8tl will be thankful...
Click to expand...
Click to collapse
Does GPE not work with the existing kernels? It should, I think.
CM is a different story, but some of the custom builds *might* support it.
Captain_Throwback said:
Does GPE not work with the existing kernels? It should, I think.
CM is a different story, but some of the custom builds *might* support it.
Click to expand...
Click to collapse
I have tried to flash some CM based ROMs as they doesn't work on my device because CM does not support it...I am now trying to flash the GPE kernel .reply soon
---------- Post added at 12:55 PM ---------- Previous post was at 12:41 PM ----------
Captain_Throwback said:
Does GPE not work with the existing kernels? It should, I think.
CM is a different story, but some of the custom builds *might* support it.
Click to expand...
Click to collapse
I have tried but failed...I think maybe it's because of the kernel souce...and the firmware....And the GPE rom on my device is ported by another developer...
I'm runnning digital high gpe and cm 12 the only thing that's different is the ramdisk
Evolutionmods said:
I'm runnning digital high gpe and cm 12 the only thing that's different is the ramdisk
Click to expand...
Click to collapse
I wanna...can you make a kernel for my device or maybe you can teach me the way? Huge thanks
Sent from my HTC M8t using XDA Free mobile app
hellobbn said:
I wanna...can you make a kernel for my device or maybe you can teach me the way? Huge thanks
Sent from my HTC M8t using XDA Free mobile app
Click to expand...
Click to collapse
First result with Google-
http://forum.xda-developers.com/showthread.php?t=1748297
http://www.xda-developers.com/compile-kernel-tutorial/
@Evolutionmods sorry for the off topic reply, nice work btw, thanks for the new options.
Evolutionmods said:
I'm runnning digital high gpe and cm 12 the only thing that's different is the ramdisk
Click to expand...
Click to collapse
So are you saying the GPE kernel works on CM? I'll have to see if my kernel works on CM then, since I use AnyKernel, it uses the ramdisk from the ROM. Unless that's not what you meant.
Captain_Throwback said:
So are you saying the GPE kernel works on CM? I'll have to see if my kernel works on CM then, since I use AnyKernel, it uses the ramdisk from the ROM. Unless that's not what you meant.
Click to expand...
Click to collapse
yes, the source works on both. just remove the pronto driver from being built into the kernel. for some reason i couldnt get the stock driver to load. once i removed it being built in, it grabbed the stock module
Evolutionmods said:
yes, the source works on both. just remove the pronto driver from being built into the kernel. for some reason i couldnt get the stock driver to load. once i removed it being built in, it grabbed the stock module
Click to expand...
Click to collapse
There's no pronto driver in GPE source .
Captain_Throwback said:
There's no pronto driver in GPE source .
Click to expand...
Click to collapse
what i meant was that if you had the commit to add cafs pronto/prima into the kernel like cm does then you just have to remove it from being built in. but looking at your source, it should just work. no problem.
Evolutionmods said:
what i meant was that is you had the commit to add cafs pronto/prima into the kernel like cm does then you just have to remove it from being built in. but looking at your source, it should just work. no problem.
Click to expand...
Click to collapse
Ah, okay. Cool, thanks. I'll give that a shot.
I am using the CM Powerhouse on CM12 Sprint, working well, thanks for the good work, nice to see more AOSP kernel choices.
Thanks bud! Glad to see the other variants are good
Hello all.
Today I am proud to bring you ODS Kernel for Android 6.0, based off FrancoKernel r33.
The purpose of this kernel is to build off of the amazing base that is FrancoKernel, and add a variety of passive patches, as well as some minimal features.
Features:
- Uses a Ramdisk based off of ChainFire's new SE Policy, meaning that we are able to leave SE Linux Enforcing, and retain Root
- Adds Kexec-HardBoot Flags to default build
- Disables some security check to allow (hopefully) for a full Kexec bringup in the near future (I'll be making an attempt at it, please PM me if you are interested in helping)
- Edits Ramdisk for additional MultiROM compatibility
- Built with custom ARM-EABI-4.6
- Adds partial ability to load kernel modules (in prep for aforementioned Kexec Module bringup)
- Everything included in FrancoKernel
To be implemented:
- Make use of ChainFire's new non-system altering root setup
- Allow for Wake gesture
- Allow for screen off gestures
- Add several binaries to ramdisk
Changelog:
- 8/31 - Happy Halloween!!!
Initial Release
Only setting that should be enabled by default is Charging LED, which can be disabled through any variety of Kernel Configuration apps.
I strongly recommend grabbing the FrancoKernel Updater app from the Play Store to support FrancoKernel's developer! If you want a free alternative, I recommend Kernel Adiutor (Not a misspelling).
To try the kernel, you can just "fastboot boot boo.img" To flash the image, you can use: TWRP Image Flash Option, "fastboot flash boot boot.img", or good ole' dd.
Source can be found here: https://github.com/npjohnson/ODS-Kernel-Shamu
Download: In the download tab up top. Won't work in TapaTalk. Open this page in a browser. If you can't do that, see here: https://drive.google.com/file/d/0B1rm1VFiz_2FV1lJcWpscWdDZ3M/view?usp=docslist_api
Happy Flashing!!!
XDA:DevDB Information
[KERNEL][M] ODS Kernel, Kernel for the Nexus 6
Contributors
npjohnson, npjohnson
Source Code: https://github.com/npjohnson/ODS-Kernel-Shamu
Kernel Special Features: Kexec-HardBoot/MultiROM Support, (Partially) Loadable Modules, Some Security Checks disabled to allow for a full Kexec Bringup, Root by defualt on M with SE Linux Enforcing
Version Information
Status: Testing
Current Stable Version: r3
Stable Release Date: 2015-10-30
Created 2015-10-31
Last Updated 2015-10-30
Download link?
Sent from my Nexus 6 using Tapatalk
Hai
Is This the DL?
Hi guys I am running stock m how do i flash this kernel do i need to flash only the boot.img or i need to install twrp and chainfire boot.img and then franco zip i am just so confused plz help sos
Actually... You did misspell it
Adiutor
Sent from my Nexus 6 using Tapatalk
Faux Sound?
No download link.
DreamFX said:
No download link.
Click to expand...
Click to collapse
Its in the git.
https://github.com/npjohnson/ODS-Ke.../target/product/shamu/ODS_Kernel-Shamu-r3.img hit "view raw" and you get the download
Flashed multiple times on Pure Nexus rom and couldn't ever get it to boot. Flashed from Franco kernel.. Anyone got this to boot? I installed through twrp and flashify and no go. Even tried Chainfire's boot image then su 2.52 then this kernel and no go. Bootlooped every time.
Maybe I need to do a full wipe and install that way?
flashback7 said:
Flashed multiple times on Pure Nexus rom and couldn't ever get it to boot. Flashed from Franco kernel.. Anyone got this to boot? I installed through twrp and flashify and no go. Even tried Chainfire's boot image then su 2.52 then this kernel and no go. Bootlooped every time.
Maybe I need to do a full wipe and install that way?
Click to expand...
Click to collapse
Did you clear app kernel setting, or dirty flash whatever rom your on first. I haven't tried flashing this kernel yet though
Sent from my Nexus 6 using Tapatalk
an21281 said:
Did you clear app kernel setting, or dirty flash whatever rom your on first. I haven't tried flashing this kernel yet though
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Been flashing for 4 years and I couldn't get it to boot. Booted every other kernel on the map.
an21281 said:
Download link?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
In the download tab up top. I don't really like the new DevDB format. I added a download link as well.
biglilsteve said:
Hai
Click to expand...
Click to collapse
OK...
farahzadfarahzad said:
Hi guys I am running stock m how do i flash this kernel do i need to flash only the boot.img or i need to install twrp and chainfire boot.img and then franco zip i am just so confused plz help sos
Click to expand...
Click to collapse
Flash the boot image through TWRP by selecting "install" then "images" (found in the bottom right), then selecting the boot image and installing.
MoSeriouS said:
Is This the DL?
Click to expand...
Click to collapse
The one on got is broken. Ill fix this asap.
rignfool said:
Actually... You did misspell it
Adiutor
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Lol. I will fix that.
DreamFX said:
No download link.
Click to expand...
Click to collapse
See above.
Tylog said:
Its in the git.
https://github.com/npjohnson/ODS-Ke.../target/product/shamu/ODS_Kernel-Shamu-r3.img hit "view raw" and you get the download
Click to expand...
Click to collapse
Yeah... Oops. The on in got releases is broken. It grabbed the one in the out directory, which I messed up the ramdisk on. The one in the Google Drive link above works fine!
flashback7 said:
Flashed multiple times on Pure Nexus rom and couldn't ever get it to boot. Flashed from Franco kernel.. Anyone got this to boot? I installed through twrp and flashify and no go. Even tried Chainfire's boot image then su 2.52 then this kernel and no go. Bootlooped every time.
Maybe I need to do a full wipe and install that way?
Click to expand...
Click to collapse
I apologize for the mistake. The one on git is broken. Please use the one linked in the OP.
an21281 said:
Did you clear app kernel setting, or dirty flash whatever rom your on first. I haven't tried flashing this kernel yet though
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
ROM shouldn't have to be clean flashed. Clearing current kernel settings is always a good idea.
flashback7 said:
Been flashing for 4 years and I couldn't get it to boot. Booted every other kernel on the map.
Click to expand...
Click to collapse
Like I said above, apologies, the one on git is broken.
Also, FYI, I test the kernel on both stock and PureNexus. It works beautifully on the 10/30 build of PureNexus, and even allows for Enforcing SE Linux, whereas Bean's kernel opts for Permissive.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk
npjohnson said:
Also, FYI, I test the kernel on both stock and PureNexus. It works beautifully on the 10/30 build of PureNexus, and even allows for Enforcing SE Linux, whereas Bean's kernel opts for Permissive.View attachment 3526746
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thank you sir. I redownloaded kernel from link in op as you said and boot image flashed fine in twrp.
Any plans to add Francos color control in? Like the presets like he has in FKU? I immediately missed that feature. Going to give her a run a few days and see what happens. Thanks for sharing!
flashback7 said:
Thank you sir. I redownloaded kernel from link in op as you said and boot image flashed fine in twrp.
Any plans to add Francos color control in? Like the presets like he has in FKU? I immediately missed that feature. Going to give her a run a few days and see what happens. Thanks for sharing!
Click to expand...
Click to collapse
I'm not against it. I'll start a poll later today and gauge what is the popular opinion.
Sent from my Nexus 6 using Tapatalk
maybe it can sounds as a noob question but in daily use what's the difference between the original Franco's kernel and this mod?
provolinoo said:
maybe it can sounds as a noob question but in daily use what's the difference between the original Franco's kernel and this mod?
Click to expand...
Click to collapse
Read the features tab.
npjohnson said:
Read the features tab.
Click to expand...
Click to collapse
yes, I read it and it's full of features as it should be but that wasn't my question
provolinoo said:
yes, I read it and it's full of features as it should be but that wasn't my question
Click to expand...
Click to collapse
It has everything FK has, PLUS what is in the features.
Sent from my Nexus 6 using Tapatalk