== 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 with TWRP: 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 Z1, ZU kexec patch v1 [18/01/14], a Tool/Utility for the Sony Xperia Z1
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.
Awesome work man! Also glad to see another thread of yours on XDA. Keep the good work up!
Awesome work man and welcome back ^_^
Sent from my Xperia Z1 using XDA Premium 4 mobile app
Thx, did anyone tried it? I'd like to have confirmation it works, then I can make multiboot
Sent from my C6903 using xda app-developers app
krabappel2548 said:
Thx, did anyone tried it? I'd like to have confirmation it works, then I can make multiboot
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
nice!
i can have a multiboot solution ready in a short time
full GUI based
@krabappel2548
tested the cm-test kernel!
working well
kernel boots
now testing if it can boot my kernel for stock rom
tested my kernel... boots but takes a VERY long time for the initial boot-up (bootlogo)...
but its great work!
It is duel boot ?
nadavgal said:
It is duel boot ?
Click to expand...
Click to collapse
it will multiboot tomorrow (today), if i get time
ok so I had implemented something similar about 3 years back on the Xperia X10 (phew its been that long )
Boot Manager for Xperia X10
{
"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"
}
I can create a similar interface for the Z1 and other devices...
my idea is to make this "base kernel" into a bootloader from which we can select the kernel we want to boot by default and also have ability to select a different kernel to boot into...
I don't really get this KEXEC-kernel thing.. Is this making custom kernels bootable on locked bootloaders?
Destroyedbeauty said:
I don't really get this KEXEC-kernel thing.. Is this making custom kernels bootable on locked bootloaders?
Click to expand...
Click to collapse
no, you need unlocked bootloader for this:
you can simply swap between two kernels
moritz31 said:
no, you need unlocked bootloader for this:
you can simply swap between two kernels
Click to expand...
Click to collapse
It's the first step to multiboot roms on unlocked bootloaders
krabappel2548 said:
It's the first step to multiboot roms on unlocked bootloaders
Click to expand...
Click to collapse
The possibility of multiboot can reach the rest of the Xperia 2013 line? In particular Xperia SP.
lvints said:
The possibility of multiboot can reach the rest of the Xperia 2013 line? In particular Xperia SP.
Click to expand...
Click to collapse
Yes it's possible, but first I'll make it for Z1
Sent from my C6903 using xda app-developers app
krabappel2548 said:
Yes it's possible, but first I'll make it for Z1
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
I am wondering one thing, that was achieved on the X10 back in 2010 (2011?) by master developer @goroh_kun, if it is possible on the Z1 and additional Xperia 2012 / 2013 / future 2014 devices.. Check down below!
No one here that has thought about getting around the bootloader and bypass the security check on locked bootloaders, so custom kernels can be booted w/o any hassles on LB?
Just something that crossed my mind..
Destroyedbeauty said:
I am wondering one thing, that was achieved on the X10 back in 2010 (2011?) by master developer @goroh_kun, if it is possible on the Z1 and additional Xperia 2012 / 2013 / future 2014 devices.. Check down below!
No one here that has thought about getting around the bootloader and bypass the security check on locked bootloaders, so custom kernels can be booted w/o any hassles on LB?
Just something that crossed my mind..
Click to expand...
Click to collapse
With root it is theoretically possible to patch a live kernel to allow kexecing another kernel, but this is tricky stuff and certainly not something I can figure out. There is hope for you, just not very much. May I humbly suggest you (and/or everyone else applicable) do some market research in the future and buy from a place where you get an unlockable bootloader?
Rekoil said:
With root it is theoretically possible to patch a live kernel to allow kexecing another kernel, but this is tricky stuff and certainly not something I can figure out. There is hope for you, just not very much. May I humbly suggest you (and/or everyone else applicable) do some market research in the future and buy from a place where you get an unlockable bootloader?
Click to expand...
Click to collapse
My bootloader is already unlocked and loaded with Doomkernel, so this is not a problem for me..
Rather, I am speaking towards those people that is on fully BL-locked phones and that only can root their phones (and not more than so) if it's any hope for them to get custom kernels working on LB by cracking / hacking / bypassing the bootloader signature key check and make those kernels bootable?
Like achieved on the X10.. Wasn't KEXEC used back here also?
Sent from my C6903 using XDA Premium 4 mobile app
Destroyedbeauty said:
My bootloader is already unlocked and loaded with Doomkernel, so this is not a problem for me..
Rather, I am speaking towards those people that is on fully BL-locked phones and that only can root their phones (and not more than so) if it's any hope for them to get custom kernels working on LB by cracking / hacking / bypassing the bootloader signature key check and make those kernels bootable?
Like achieved on the X10.. Wasn't KEXEC used back here also?
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It was... but from my understanding the signed kernel on the X10 allowed kernel modules to be loaded post-boot, as far as I know the stock kernel on the Z1 doesn't allow this, making it much harder to achieve kexec functionality on a locked bootloader.
Rekoil said:
It was... but from my understanding the signed kernel on the X10 allowed kernel modules to be loaded post-boot, as far as I know the stock kernel on the Z1 doesn't allow this, making it much harder to achieve kexec functionality on a locked bootloader.
Click to expand...
Click to collapse
Nothing is impossible with the proper support and patience.
Sent from my C6903 using XDA Premium 4 mobile app
Destroyedbeauty said:
Nothing is impossible with the proper support and patience.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are right of course, but still bloody difficult and at the same time not something that is strictly necessary since the option exists to get a device with an unlockable bootloader (unlike back on the Xperia X10 where all devices were locked). I wouldn't hold my breath.
Sent from my Xperia Z1 using Tapatalk
Related
[ info ]
ok guys so I was testing few things... saw that the Sony ZU GPE was released and then saw the disk dumps in this thread:
http://forum.xda-developers.com/showthread.php?t=2570197
since sony was kind enough to release the kernel sources for the ZU GPE.. i just corrected the kernel sources to support Z1 (as both devices have same board) and managed to get a bootable kernel..
I think this is now clear for public testing!
so far:
kernel boots
device boots in OS
phone calls work
bluetooth works
audio playback works
video playback works
3G data works
GPS works
NFC works
camera doesnt work [for now ]
wifi now works [WiFi FIX]
i invite all interested devs to help with fixing the broken stuff!
[ proof ]
{
"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"
}
dont bother about model number in screenshot
[ WARNING ]
THIS IS A PORT FROM ANOTHER DEVICE!
some things will not work! that is expected!
[ requirements ]
Xperia Z1 - i am testing on C6902 & C6903 (users need to flash additional package for C6903!)
unlocked bootloader
[ how to install ] {NEW - ONLY FOR v2}
you will need a recovery kernel (use my DooMKernel)
reboot into bootloader
hotboot into the recovery kernel
Code:
fastboot boot DooMKernel.img
the device will start booting my old kernel
keep pressing volume UP keys to enter recovery
you can flash the ROM zip in recovery
no need to wipe data!
ONLY for C6903 users: while still in recovery flash Z1-Stock_C6903_FW_4.3_Files << THIS IS CRUCIAL OR YOU WILL GET BOOTLOOPS!
NOW reboot from recovery
thats it!
device will start booting into Sony 4.4.2 GPE
[ how to install ] {OLD - ONLY FOR v1}
you will need a recovery kernel (use my DooMKernel)
reboot into bootloader
hotboot into the recovery kernel
Code:
fastboot boot DooMKernel.img
the device will start booting my old kernel
keep pressing volume UP keys to enter recovery
you can flash the ROM zip in recovery
no need to wipe data!
NOW reboot into bootloader from recovery
flash the Z1 GPE kernel
Code:
fastboot flash boot boot.img
now reboot from fastboot mode
Code:
fastboot reboot
thats it!
device will start booting into Sony 4.4 GPE
[ kernel sources ]
https://github.com/DooMLoRD/android_kernel_sony_msm8974/tree/z1_gpe_port
[ downloads ]
PLEASE DO NOT MIRROR MY FILES!
v2: [NEW]
ROM + KERNEL (with dual recoveries!): <COMMON FOR C6902/C6903>
DooMLoRD_ZU-GPE_port_Z1-KOT49H.S2.2052-ROM-v2 {MIRROR}
Size: 453 MB
MD5HASH: a69042b72eb77d21bc9d9904a116cd22
WiFi FIX (Thanks to @MohammadAG)
Special firmware files for C6903: <ONLY for C6903>
Z1-Stock_C6903_FW_4.3_Files {MIRROR}
Size: 17 MB
MD5HASH: 74832814c7de976356a1e9c9a37bee36
v1: [OLD]
Kernel:
DooMLoRD_ZU-GPE_port_Z1-KRT16O.S3.1044-Kernel-v1 {MIRROR}
Size: 8.24 MB
MD5HASH: d445e99f0ad1d0d34f35b614a8cb0216
ROM:
DooMLoRD_ZU-GPE_port_Z1-KRT16O.S3.1044-ROM-v1
Size: 440 MB
MD5HASH: 732a90cce84450d5545ed2af05bcab6b
enjoy!
regards,
DooMLoRD
reserved for later
Very nice... Is it using ZU camera drivers (that's why camera don't works)?
Should be great to run Android 4.4 ROMs based on AOSP for Z1.
RHBH said:
Very nice... Is it using ZU camera drivers (that's why camera don't works)?
Should be great to run Android 4.4 ROMs based on AOSP for Z1.
Click to expand...
Click to collapse
probably yes... we can hopefully fix that soon...
DooMLoRD said:
probably yes... we can hopefully fix that soon...
Click to expand...
Click to collapse
Well, Sony took 1 month to release sources for .257 FW, hopefully they won't take longer to release .290 sources!
Well that was quick We should probably lure you into the ZU section so you can make some kernels for us too
LordManhattan said:
Well that was quick We should probably lure you into the ZU section so you can make some kernels for us too
Click to expand...
Click to collapse
well when i have the time to work on it i do things pretty fast (almost forgot have two submissions tomorrow! gtg sleep)
i will only make stuff for the devices i have...
regards,
DooMLoRD
kernel sources have been pushed to git
https://github.com/DooMLoRD/android_kernel_sony_msm8974/tree/z1_gpe_port
regards,
DooMLoRD
Will take a look into it.
hopefully if all goes well, I will be able to release the 4.4.2 update tonight!
DooMLoRD said:
hopefully if all goes well, I will be able to release the 4.4.2 update tonight!
Click to expand...
Click to collapse
Yea!!!!
DooMLoRD said:
probably yes... we can hopefully fix that soon...
Click to expand...
Click to collapse
Jeez, can't wait!!!!!!!!!!!!!!!!!!!!!
@DooMLoRD do you have a mirror?
Code:
Sorry, the server is getting overloaded, please try again later!
I have waited around 30 mins.
Also, any update?
The ported GPE is something really amazing for us!
DooMLoRD said:
hopefully if all goes well, I will be able to release the 4.4.2 update tonight!
Click to expand...
Click to collapse
Flashable zip on the z ultra forum for 4.2.2, maybe the can used utilized for 4.2.2 update, it's not just an incremental updated but all /system
Sent from my C6833 using Tapatalk
have you guys tried swapping some libs and binaries from Z1 4.3 update
Hint for the binary i was researching mm-qcom-camera-daemon...this is a binary file which contains the functions of camera
as promised here is the Z1 KitKat 4.4.2 GPE port from ZU!
this ROM+Kernel can be publicly tested and used!
[ changelog ]
new ROM v2 with files from 4.4.2 ZU GPE
new source built kernel
added dual recoveries! CWM + TWRP in kernel! - press volume UP for CWM OR press volume DOWN for TWRP
kernel directly included in ROM package (will be autoflashed in recovery)
download links at first post!
If anyone can please test it on a C6903 and report back it would be great!
regards,
DooMLoRD
Since I love this GPE (but I need camera working :victory here my transaction Id: #6PS73145LN377620R
I'll try this GPE later on the 03.
Thanks @DooMLoRD
DAddYE said:
Since I love this GPE (but I need camera working :victory here my transaction Id: #6PS73145LN377620R
I'll try this GPE later on the 03.
Thanks @DooMLoRD
Click to expand...
Click to collapse
thank you for your kind donation!
I am trying to find the required files to get camera working... but from experience i know that this is going to be VERY tough... will surely keep trying though!
regards,
DooMLoRD
DooMLoRD said:
thank you for your kind donation!
I am trying to find the required files to get camera working... but from experience i know that this is going to be VERY tough... will surely keep trying though!
regards,
DooMLoRD
Click to expand...
Click to collapse
If there is one that can do that hihi... is you
DAddYE said:
If there is one that can do that hihi... is you
Click to expand...
Click to collapse
well i am just a noob... trust me there are a lot more experienced devs who can get it working.. i just hope that they take interest in doing it...
DooMLoRD said:
well i am just a noob... trust me there are a lot more experienced devs who can get it working.. i just hope that they take interest in doing it...
Click to expand...
Click to collapse
Hhahah, we know is not true.
QQ:
Code:
the device will start booting my old kernel
keep pressing volume UP keys to enter recovery
you can flash the ROM zip in recovery
no need to wipe data!
NOW reboot into bootloader from recovery
thats it!
I think for the v2 there are missing steps... no? No need to flash the GPE kernel?
Again super thanks!
Hello There!
I am here with a good news and a bad news!
The good news is that I have sucessfully compiled TWRP recovery for our beloved Xperia M!
The bad news is that It is unstable, and I am not able to make it stable. I need help from some developers in order to make it stable.
Please note that this kernel bringup is only for CM11 FXP310.So, dont try it on other ROMs, as your may get into a serious problem after that.
Please bear with me, as I am a noob and will need a lot of help in making this stable for use!
Sources :
The TWRP sources can be found here : https://github.com/omnirom/android_bootable_recovery
The device tree of rebelos(contains commits for TWRP bringup, thanks to him for letting me use the tree) : https://github.com/rebelos/android_device_sony_nicki
The Kernel sources used : https://github.com/freexperia/android_Kernel_sony_msm8x27
Working /Not working
Working :
Normal Touch
Navigation
And Basic operations
Not - Working
Some glitches (sometimes) [that is, the half screen problem]
Screenshots(again, thanks to Bonoboo)
{
"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"
}
Downloads
New flashable zip(thanks to Bonoboo) : https://www.mediafire.com/?gg84xysk8w64fwc
OLD[not recommended for use] :
boot.img
recovery.img ( I am having problems installing this, via fastboot. Use boot.img)
Changelogs
16-03-2014
Initial Release
17-03-2014
fixed up the bugs in main ROM. i.e, the wifi and RIL bugs.
Credits :
PecanCM - For sources
FXP, for supporting this device officially
rebelos for allowing me to use his updated commits in device tree. His device tree can be found on his github.
Bonoboo for giving the idea of packing the ramdisk(the partition with recovery and the boot.img) and for packing it up for me!
A note : I need help from you all to achieve this task Please help me up.
XDA:DevDB Information
[RECOVERY] TWRP, a Tool/Utility for the Sony Xperia M
Contributors
PixCM
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2014-03-17
Created 2014-03-16
Last Updated 2014-03-18
lol twrp.. just got real ..
see these commits
https://github.com/freexperia/android_device_sony_nicki/pull/1
these will fix all your issues
rebelos said:
lol twrp.. just got real ..
see these commits
https://github.com/freexperia/android_device_sony_nicki/pull/1
these will fix all your issues
Click to expand...
Click to collapse
Thank You soo much Will compile and post in an hour or so! Got to do something else at the moment
Tried.. But they didnt help :/ Same bugs!
Finally, TWRP! Thanks!
About problems with Wi-Fi and RIL – yes, it's really due compiling kernel on your side.
I extracted from your boot.img ramdisk-recovery.cpio and replaced it in kernel from latest FXP310 build – all fine.
So maybe you do the same in future for avoiding problems?
Recovery bundled in boot.img so recovery.img can't be flashed with saving current kernel.
I think better to post ramdisk-recovery.cpio so users can combine it with needed in their case kernel: stock, modded or whatever.
Here easy tutorial and tool for do these on Windows. Almost same for Linux.
Bugs:
– no mount of any partitions
– screen most time halved
– at screen timeout it don't off
Best Recovery Shown up!
TWRP just the best recovery ever... my fav.
hope this can be fixed soon... thanks for the good job
Good work bro...
Sent from my C1905 using XDA Premium 4 mobile app
Thanks mate for TWRP recovery! Always used this on my GT-I9100
Wating for an update
Sent from my C1905 using Tapatalk
Bonoboo said:
Finally, TWRP! Thanks!
About problems with Wi-Fi and RIL – yes, it's really due compiling kernel on your side.
I extracted from your boot.img ramdisk-recovery.cpio and replaced it in kernel from latest FXP310 build – all fine.
So maybe you do the same in future for avoiding problems?
Recovery bundled in boot.img so recovery.img can't be flashed with saving current kernel.
I think better to post ramdisk-recovery.cpio so users can combine it with needed in their case kernel: stock, modded or whatever.
Here easy tutorial and tool for do these on Windows. Almost same for Linux.
Bugs:
– no mount of any partitions
– screen most time halved
– at screen timeout it don't off
About screenshots.
Please hide them under spoiler – thread very lagre with them now.
Here flashable ZIP with original FXP310 kernel and this recovery.
Click to expand...
Click to collapse
Thanks dude! I will give you another build, check if the mount is working in this one!
Check your PM.
SUM ONE SAY TWRPDDDDDD goddamn, i want try it, but after the bug like wifi-RIL etc fixed
PixCM said:
Thanks dude! I will give you another build, check if the mount is working in this one! .
Click to expand...
Click to collapse
– Now all partitions mounts, switching internal/external storage ok too. Thanks!
– ADB works
– But there no option for USB Mass storage connection
– Screen still halved, affect touch too
– Screen timeout still broken
Here directly captured screenshots.
Please replace screens in first post and hide them under spoiler.
Richardsentosa said:
i want try it, but after the bug like wifi-RIL etc fixed
Click to expand...
Click to collapse
Use this flashable ZIP with original FXP310 kernel and this new version recovery. No bugs in main ROM (CM11).
Bonoboo said:
– Now all partitions mounts, switching internal/external storage ok too. Thanks!
– ADB works
– But there no option for USB Mass storage connection
– Screen still halved, affect touch too
– Screen timeout still broken
Here directly captured screenshots.
Please replace screens in first post and hide them under spoiler.
Use this flashable ZIP with original FXP310 kernel and this new version recovery. No bugs in main ROM (CM11).
Click to expand...
Click to collapse
but now i using HellKat .-.
Updated
Updated OP with new build.
Download : https://www.mediafire.com/?gg84xysk8w64fwc
Special thanks to @Bonoboo for this
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Bonoboo said:
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Click to expand...
Click to collapse
If I will be compiling again, then it would be in any form. You say. Which one is better? I think for people's use, its better to release in boot.img form. Or else, I will do one thing..
I will release it in both the forms.
P.S I will be updating the OP soon. In an hour or so.
And, will you become my tester? I will send you links to build through PM. I am trying to compile omni at the moment.
PixCM said:
I will release it in both the forms.
Click to expand...
Click to collapse
Yes, this will be nice and more flexible: someone can manually add recovery in beloved kernel and CM11 users can directly flash it.
PixCM said:
And, will you become my tester?
Click to expand...
Click to collapse
Recovery – yes, but not ROM, sorry.
PixCM said:
If I will be compiling again, then it would be in any form. You say. Which one is better? I think for people's use, its better to release in boot.img form. Or else, I will do one thing..
I will release it in both the forms.
P.S I will be updating the OP soon. In an hour or so.
And, will you become my tester? I will send you links to build through PM. I am trying to compile omni at the moment.
Click to expand...
Click to collapse
OmniROM with TWRP recovery is brilliant mate! Hope you will release it
Sent from my C1905 using Tapatalk
a new build? i will try it (if i flashed the FXP CM11)
Richardsentosa said:
a new build?
Click to expand...
Click to collapse
Yep, CM11 FXP311 released.
Here flashable zip with kernel from there with integrated this TWRP recovery.
Bonoboo said:
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Click to expand...
Click to collapse
+1 lol... you just wrote what i want to...
now it's being clear...
coz i need to replace the whole cwm from every Roms i've downloaded... yeah... keep it rolling dude :good:
CM11 FXP312 released.
Here flashable zip with kernel from there with integrated this TWRP recovery.
As everyone knows mokee official release uses a old kernel build from month of may, while the latest kernel is from sept. So I have made a repack of the latest kernel. As far my primary tests everything is working so just flash it and enjoy the latest one, incase xiaomi updates their kernel and anyone uses it but mokee, I will repack again and update the thread.
Enjoy!
ps: Sorry no flashable zip available. please report any bug you may find!
Steps:
1. enable usb debugging
2. connect to pc and open adb
3. copy the downloaded boot.img file to the adb folder.
4.open cmd, navigate to adb folder and type these lines one by one.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
5. after reboot, just copy the 2nd downlaoded file "pronto_wlan.ko" to /system/lib/modules/pronto and replace the existing file,
6. change the permission to rw-r-r
7. reboot and enjoy the latest kernel.
If anyone can make a twrp/cwm flashable zip, you can share here.
Download
Screenshot:
{
"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"
}
thnx to the help from
kapil.git
Thanks for the Wake Up!!
saurabhrck said:
As everyone knows mokee official release uses a old kernel build from month of may, while the latest kernel is from sept. So I have made a repack of the latest kernel. As far my primary tests everything is working so just flash it and enjoy the latest one, incase xiaomi updates their kernel and anyone uses it but mokee, I will repack again and update the thread.
Enjoy!
ps: Sorry no flashable zip available. please report any bug you may find!
Steps:
1. enable usb debugging
2. connect to pc and open adb
3. copy the downloaded boot.img file to the adb folder.
4.open cmd, navigate to adb folder and type these lines one by one.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
5. after reboot, just copy the 2nd downlaoded file "pronto_wlan.ko" to /system/lib/modules/pronto and replace the existing file,
6. change the permission to rw-r-r
7. reboot and enjoy the latest kernel.
If anyone can make a twrp/cwm flashable zip, you can share here.
Download
Screenshot:
thnx to the help from
kapil.git
Click to expand...
Click to collapse
deadlyindian said:
Thanks for the Wake Up!!
Good Work Brothers !!!!:laugh::laugh::laugh:
Keep it up.....:good::good::good:
But, if I am not wrong Xiaomi has not released any kernel sources and so all of our Devs are using only headers for compiling the ROM and so they are just changing the date in headers. Does this matters in performance, or stability?
Please do correct me, if I am wrong anywhere. I am always ready to learn new things.
Best Regards
BOND
Click to expand...
Click to collapse
SuperDroid-BOND said:
Good Work Brothers !!!!:laugh::laugh::laugh:
Keep it up.....:good::good::good:
But, if I am not wrong Xiaomi has not released any kernel sources and so all of our Devs are using only headers for compiling the ROM and so they are just changing the date in headers. Does this matters in performance, or stability?
Please do correct me, if I am wrong anywhere. I am always ready to learn new things.
Best Regards
BOND
Click to expand...
Click to collapse
xiaomi has not released kernel source dts right, but they are updating kernel while they update miui rom(secure source), devs are actually using that updated kernel which is made by xiaomi. Mokee on the other hand was using a old kernel and they were not updating , so I took the liberty to update it.
saurabhrck said:
xiaomi has not released kernel source dts right, but they are updating kernel while they update miui rom(secure source), devs are actually using that updated kernel which is made by xiaomi. Mokee on the other hand was using a old kernel and they were not updating , so I took the liberty to update it.
Click to expand...
Click to collapse
You did the right thing brother and thanks (I already pressed it for both of you) for keeping us updated.
So, you mean to say that Xiaomi has updated the kernel and sources but its secured only, not public. If it is like this, would you mind linking us to those sources, because there are so many ROMs waiting for some fixed kernel sources or if you can tell us what things have been fixed, can we use single SIM with this code "
Code:
setprop persist.radio.multisim.config none
".
We, all the users, can get several ROM with almost all utmost and best features available. Please do let me know about the kernel, best if we could talk on PM.
Best Regards
BOND
The Kernel gets updates by new Miui releases...i'll give a notable example to prove that !
Before v41.1 there isn't built in Zram implemented but with new kernel (v41.1+) there is Zram Support !
SuperDroid-BOND said:
You did the right thing brother and thanks (I already pressed it for both of you) for keeping us updated.
So, you mean to say that Xiaomi has updated the kernel and sources but its secured only, not public. If it is like this, would you mind linking us to those sources, because there are so many ROMs waiting for some fixed kernel sources or if you can tell us what things have been fixed, can we use single SIM with this code "
Code:
setprop persist.radio.multisim.config none
".
We, all the users, can get several ROM with almost all utmost and best features available. Please do let me know about the kernel, best if we could talk on PM.
Best Regards
BOND
Click to expand...
Click to collapse
The source is secure to xiaomi, they are not releasing to public as of now. Don't know whats the reason for this idiotic move. Anyway I don't have the source, like anyone else, I just repacked with proper module. dts all! Will update when xiaomi releases a new update
saurabhrck said:
The source is secure to xiaomi, they are not releasing to public as of now. Don't know whats the reason for this idiotic move. Anyway I don't have the source, like anyone else, I just repacked with proper module. dts all! Will update when xiaomi releases a new update
Click to expand...
Click to collapse
so is it repack of old ramdisk and new zimage... btw can u please give me link/info about the tool which u have used to repack kernel.. i tried to make kernel unsecure once but cant make it boot... kernel size reduced ~4 mb....
deadlyindian said:
Thanks for the Wake Up!!
Is no need to set permission at pronto wlan ?
Click to expand...
Click to collapse
pgreed said:
Is no need to set permission at pronto wlan ?
Click to expand...
Click to collapse
Nope its automatically set when phone boots...
What are the features of the kernel? This for mokee only? Any version??
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small (as density is around 400dpi!!) and after app is launched phone reboot.
pgreed said:
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small and after app is launched phone reboot.
Click to expand...
Click to collapse
ofcourse it will not work with unofficial version. unofficial version is based on cm11 source and uses that prebuilt kernel. you have to repack it separately for that. This one is only for mokee official release which uses mokee kernel/device files not from cm11, mentioned in OP!
saurabhrck said:
ofcourse it will not work with unofficial version. unofficial version is based on cm11 source and uses that prebuilt kernel. you have to repack it separately for that. This one is only for mokee official release which uses mokee kernel/device files not from cm11, mentioned in OP!
Click to expand...
Click to collapse
No it use the 8 May kernel! (is the sychost unofficial)
Shahi00 said:
The Kernel gets updates by new Miui releases...i'll give a notable example to prove that !
Before v41.1 there isn't built in Zram implemented but with new kernel (v41.1+) there is Zram Support !
Click to expand...
Click to collapse
So you mean Roms above 41.1 have zram implemented? before that it was not available?
Shahan_mik3 said:
So you mean Roms above 41.1 have zram implemented? before that it was not available?
Click to expand...
Click to collapse
Yep...even though we have 1GB RAM it is done that way !
I am very sure that V36 don't have ZRAM and V41.1 and above have it...that's the way they found to currect RAM management !
it causes a bit battery drain & and performance regression !
pgreed said:
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small (as density is around 400dpi!!) and after app is launched phone reboot.
Click to expand...
Click to collapse
link for mokee unofficial plz..
RohanAJoshi said:
link for mokee unofficial plz..
Click to expand...
Click to collapse
Because from Mokee site was deleted all unofficial and experimental version (I dunno why) I've upload the file elsewhere:
Shahi00 said:
Yep...even though we have 1GB RAM it is done that way !
I am very sure that V36 dont have ZRAM and V41.1 and above have it...thats the way they found to currect RAM management !
it causes a bit battery drain & and performance regression !
Click to expand...
Click to collapse
Also I wanted to know. How is it possible to get a stable cm/aosp Roms on Redmi but not on mi3?
Shahan_mik3 said:
Also I wanted to know. How is it possible to get a stable cm/aosp Roms on Redmi but not on mi3?
Click to expand...
Click to collapse
Our developer is good enough for tracking bugs that causes Random Reboots !!
Kra always did that (on previous phone too)
:good:
{
"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"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
IMPORTANT
1. I'm not responsible for anything, you do all this on your own risk.
2. Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to "Advanced -> MultiROM" to flash ROMs/kernels or other mods.
3. If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
4. I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
5. Your device must not be encrypted.
6. To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
7. When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.INSTALLATION
1. Make sure you are on a rom compatible with these kernels.
2. Flash the required kernel zip.
3. Flash MultiROM_TWRP-xx-xx-xxxx.img on fota partition.
4. Flash MultiRom_xx-xx-xxxx-v31x.zip
5. Done1Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs).
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android Rom
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch old)
Modified TWRP - https://github.com/XperiaMultiROM/an...table_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/aweosomeabhijeet/android_kernel_sony_msm8x27 (cm-Kernel)
CREDITs
Tasssadar
Alvinhochun - without his kexec patch, it would have been impossible for me, kudos to him :highfive:
Xperia Multirom
Myself5
Every other dev behind this
If you think my work is good, please consider a small donation
Donate to me
You might want to consider a Donation to Tasssadar, who is the Mastermind behind all of this, I just ported it to the M
Donate to Tasssadar
XDA:DevDB Information
MultiRom for Xperia M, Tool/Utility for the Sony Xperia M
Contributors
aweosomeabhijeet, alvinhochun, XperiaMultirom
Source Code: https://github.com/XperiaMultiROM/multirom/
Version Information
Status: Stable
Current Stable Version: v31x
Stable Release Date: 2015-08-13
Created 2015-08-07
Last Updated 2015-08-13
BUGs
NO BUGS as of now
LIMITATIONs
1. For MTP to work in TWRP you need to disable and enable it again.
CHANGELOG :
Code:
2015-08-13
Stable release!
Fixed minor touch issues present in the kernel by [email protected] !
2015-08-07
Beta version
Fixed erasing primary rom with secondary
Fixed wifi
2015-08-07
Initial release!
DOWNLOADS
Kernels with kexec-hardboot support :
XMS-stock-Kexec.zip(To be flashed in recovery)(not yet tested)
XMD-stock-Kexec.zip(To be flashed in recovery)(not yet tested)
XM_CM_kexec-08-13-2015.zip(has touch screen issue)
Other kernels with kexec-hardboot support:
1. NUI kernel(kudos to dev.)
Instructions to use NUI kernel
MultiROM TWRP :
recovery.img(To be flashed on fota-partition)
MultiROM-zip :
multirom-20150813-v31x-UNOFFICIAL-nicki.zip(To be flashed in recovery)
Use sdcard class 10 to boot cm11, run very smoothly
Great work, thang's ..
Sent from my waifu
Superb job @aweosomeabhijeet
And u can even add XMD in thread title bcoz it even works on it.. I am XMD user.. It's working well
@aweosomeabhijeet, to prevent compatibility issues that may occur it will be better to use boot image repacking script (e.g. with unpackbootimg and mkbootimg utilities) that will inject new zImage (it is kernel file in your out/target/product/nicki folder) in boot image than flashing raw boot.img, so ramdisk will not be overridden (as far as I understand we don't need changes in ramdisk for kexec, do we? and even if we do, it will be better to replaced only changed files, not the whole ramdisk). Noel Macwan uses that thing in his kernels, I used his script as base for my old injecting CWM/TWRP script.
---------- Post added at 21:26 ---------- Previous post was at 20:57 ----------
BTW, what kernel sources did you use for your kexec-patched kernel? Are they Sony stock ones? Aren't they from CM12.1 repo?
SUCCESS
so today i successfully flashed 3 roms on in XMD which run smoothly..the only problem i faced is patience when flashed through recovery i in usbdisk (which is obvious)..so now i dont need to wipe or format my primary rom in oder to test other builds..fabulous job @aweosomeabhijeet
Now mutlirom thread is active almost after one and half year for our xperia m...
All credits to u...
[deleted]
cucumber09 said:
@aweosomeabhijeet, to prevent compatibility issues that may occur it will be better to use boot image repacking script (e.g. with unpackbootimg and mkbootimg utilities) that will inject new zImage (it is kernel file in your out/target/product/nicki folder) in boot image than flashing raw boot.img, so ramdisk will not be overridden (as far as I understand we don't need changes in ramdisk for kexec, do we? and even if we do, it will be better to replaced only changed files, not the whole ramdisk). Noel Macwan uses that thing in his kernels, I used his script as base for my old injecting CWM/TWRP script.
---------- Post added at 21:26 ---------- Previous post was at 20:57 ----------
BTW, what kernel sources did you use for your kexec-patched kernel? Are they Sony stock ones? Aren't they from CM12.1 repo?
Click to expand...
Click to collapse
Indeed a very good idea, but I am worried about pure stock users. I think the script won't work, though I haven't tried.
They are from CM repo only, I am fixing some issues will push changes to my fork of CM kernel.
aweosomeabhijeet said:
Indeed a very good idea, but I am worried about pure stock users. I think the script won't work, though I haven't tried.
They are from CM repo only, I am fixing some issues will push changes to my fork of CM kernel.
Click to expand...
Click to collapse
We can make different zip for pure stock and for custom ROMs. But is now MR working on stock? Doesn't it have split screen bug? If yes, you should try using custom recovery graphics, and I am not familiar to C, so can't help. And BTW does stock work with CM kernel? I very doubt it. Even if it will work with stock ramdisk and CM zImage (which I doubt too, as CM kernel is built on CAF sources with some changes from stock kernel if I'm not wrong), it surely won't work with full CM boot image, so repacking script will be the best solution (I can even make it for you today if changes in initrd are not needed). And if stock will boot with CM zImage we will not have screen split bug anymore, and script also should work even with stock (as the command line is the same, and even if not, we can read it from unpackbootimg output by using `cat *.img-cmdline` for command line value in script). But building different kernels for stock and custom ROMs (all custom ROMs for our device share the same kernel source, difference is only in ramdisk, you can even boot CM11 with CM12.1 kernel if you will keep CM11's ramdisk) is better solution.
cucumber09 said:
We can make different zip for pure stock and for custom ROMs. But is now MR working on stock? Doesn't it have split screen bug? If yes, you should try using custom recovery graphics, and I am not familiar to C, so can't help. And BTW does stock work with CM kernel? I very doubt it. Even if it will work with stock ramdisk and CM zImage (which I doubt too, as CM kernel is built on CAF sources with some changes from stock kernel if I'm not wrong), it surely won't work with full CM boot image, so repacking script will be the best solution (I can even make it for you today if changes in initrd are not needed). And if stock will boot with CM zImage we will not have screen split bug anymore, and script also should work even with stock (as the command line is the same, and even if not, we can read it from unpackbootimg output by using `cat *.img-cmdline` for command line value in script). But building different kernels for stock and custom ROMs (all custom ROMs for our device share the same kernel source, difference is only in ramdisk, you can even boot CM11 with CM12.1 kernel if you will keep CM11's ramdisk) is better solution.
Click to expand...
Click to collapse
Actually you are getting it wrong!
1. We would not have any screen shift bug
2. Every ROM we boot from multirom can use it's own kernel irrespective of what kernel is installed in the device. (That's the benefit of kexec-hardboot)
3. I have a better idea for maintaing stock and all. Will upload new zip soon. I would like to use parts of your script if you don't mind.
BTW, why didn't you git clone kernel repository (it would save commit history and make your fork git-compatible with original) and then apply your patches? Otherwise, it will be harder to support your patched kernel, as it has another commit history and you if I am not wrong will not be able to merge and cherry-pick commits from CM kernel to your kernel, you will have to do it manually, which is quite annoying, or leave your kernel unupdated in future.
---------- Post added at 15:49 ---------- Previous post was at 15:45 ----------
aweosomeabhijeet said:
Actually you are getting it wrong!
1. We would not have any screen shift bug
2. Every ROM we boot from multirom can use it's own kernel irrespective of what kernel is installed in the device. (That's the benefit of kexec-hardboot)
3. I have a better idea for maintaing stock and all. Will upload new zip soon. I would like to use parts of your script if you don't mind.
Click to expand...
Click to collapse
Seems that we misunderstand each other. I talk about using other ROMs as primary, not only CM. We can do this by using kexec-ed kernel. I just offer you another method installing it, which will keep original ramdisk (if kexec doesn't need changes in it) and only replace kernel itself (zImage only, not boot image).
And I don't mind using parts of this script.
cucumber09 said:
BTW, why didn't you git clone kernel repository (it would save commit history and make your fork git-compatible with original) and then apply your patches? Otherwise, it will be harder to support your patched kernel, as it has another commit history and you if I am not wrong will not be able to merge and cherry-pick commits from CM kernel to your kernel, you will have to do it manually, which is quite annoying, or leave your kernel unupdated in future.
---------- Post added at 15:49 ---------- Previous post was at 15:45 ----------
Seems that we misunderstand each other. I talk about using other ROMs as primary, not only CM. We can do this by using kexec-ed kernel. I just offer you another method installing it, which will keep original ramdisk (if kexec doesn't need changes in it) and only replace kernel itself (zImage only, not boot image).
And I don't mind using parts of this script.
Click to expand...
Click to collapse
I know it. I have forked the repo and currently cloning. It's just in beta status and is just for giving details about the patch. I'll soon be on CM kernel and would merge all its commits and kernel would be updated always.
Don't you worry about it, I have all in mind. It takes time, I am free majorly on weekends so I won't rush on things.
I understand this and I have already made installer zip which does exactly what you are trying to tell, it uses parts of your script to replace just zImage and not whole boot.img. I still have something better coming. Just wait for few days.
aweosomeabhijeet said:
I know it. I have forked the repo and currently cloning. It's just in beta status and is just for giving details about the patch. I'll soon be on CM kernel and would merge all its commits and kernel would be updated always.
Don't you worry about it, I have all in mind. It takes time, I am free majorly on weekends so I won't rush on things.
I understand this and I have already made installer zip which does exactly what you are trying to tell, it uses parts of your script to replace just zImage and not whole boot.img. I still have something better coming. Just wait for few days.
Click to expand...
Click to collapse
Okay, that's nice. Sorry if I was too annoying.
Nice dev discussions
Sent from my waifu
itsnie said:
Nice dev discussions
Sent from my waifu
Click to expand...
Click to collapse
Dev and just-advanced-user discussion as I am not a developer. Just enthusiastic and sometimes full of curiosity user, nothing more. (BTW, we should stop OT not to make a mess in the thread)
It's not a order or request.. A small advice or suggestions.. Can you overclock ur kernel for more smoothness
kjinx01 said:
It's not a order or request.. A small advice or suggestions.. Can you overclock ur kernel for more smoothness
Click to expand...
Click to collapse
Please upload kernel.sin from build 15.5.A.1.5 if anyone here is having ftf of the same so that I can build for XMD stock devices. Thanks
Hey bro why does it take so long time to flash in recovery.. Any rom on sdcard takes abt 10 min to get flashed..??
aweosomeabhijeet said:
Please upload kernel.sin from build 15.5.A.1.5 if anyone here is having ftf of the same so that I can build for XMD stock devices. Thanks
Click to expand...
Click to collapse
here u go for it..i uploaded kernel.sin from 15.5.A.1.5 of XMD ftf stock rom
https://www.mediafire.com/?9dobzi8nu2tqzjy
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Device specific page including instructions for a manual install
Download links for current and past versions of TWRP
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[dora] TWRP 3.0.2-0 touch recovery, Tool/Utility for the Sony Xperia X Performance
Contributors
AndroPlus
Version Information
Status: Stable
Created 2016-10-08
Last Updated 2016-10-08
Wow that's good news! Hoping to see twrp support for full X-series
Now it's official
I'll build TWRP for XZ, but I can't build for other variant as I don't have devices and can't maintain...
AndroPlus said:
Now it's official
Click to expand...
Click to collapse
Great! Now we need to wait root on locked bootloader but it can be very looooong waitng
AndroPlus said:
Now it's official
I'll build TWRP for XZ, but I can't build for other variant as I don't have devices and can't maintain...
Click to expand...
Click to collapse
Hi AndroPlus,
Is that means your future builds will be also compatible with xperia XP, specially and as i known the XP and XZ has about the same processor (core)? Or you will abandon the XP definitively [emoji22].
And another question: as i now have an xperia XP for about 1 month, and i decided now to rooting it with the help of your modified kernel, is it confirmed that the kernel will contouring the consequences of deleting the DRM keys a cause of unlocking bootloader and leading to restore the functionality (or at least most of them) of DRM features?.
Thanks
Envoyé de mon Xperia x performance
baha76_s said:
Hi AndroPlus,
Is that means your future builds will be also compatible with xperia XP, specially and as i known the XP and XZ has about the same processor (core)? Or you will abandon the XP definitively [emoji22].
And another question: as i now have an xperia XP for about 1 month, and i decided now to rooting it with the help of your modified kernel, is it confirmed that the kernel will contouring the consequences of deleting the DRM keys a cause of unlocking bootloader and leading to restore the functionality (or at least most of them) of DRM features?.
Thanks
Envoyé de mon Xperia x performance
Click to expand...
Click to collapse
I'll continue building kernel for XP even after buying XZ
DRM function restore is working well for XP with my kernel.
AndroPlus said:
I'll continue building kernel for XP even after buying XZ
DRM function restore is working well for XP with my kernel.
Click to expand...
Click to collapse
Thank you very much for your reply.
I'm glad to hear that you will continue the development for this flag.
And final question: is there any chance that you will find a way to modify the kernel in android 7 (nougat) in this flag?, specially as i read that the new android 7 core has a new feature to detect any changes in W/R status of the system partition and leading to become the (boot.img) inaccessible and consider as corrupted file, i.e more secure options to kernel level.
Thanks
Envoyé de mon Xperia x performance
baha76_s said:
Thank you very much for your reply.
I'm glad to hear that you will continue the development for this flag.
And final question: is there any chance that you will find a way to modify the kernel in android 7 (nougat) in this flag?, specially as i read that the new android 7 core has a new feature to detect any changes in W/R status of the system partition and leading to become the (boot.img) inaccessible and consider as corrupted file, i.e more secure options to kernel level.
Thanks
Envoyé de mon Xperia x performance
Click to expand...
Click to collapse
I think it can be disabled in kernel.
Let's wait 7.0 for our device...
AndroPlus said:
Now it's official
I'll build TWRP for XZ, but I can't build for other variant as I don't have devices and can't maintain...
Click to expand...
Click to collapse
Was hoping for an other answer but I can understand your decision! It's nice to see some support for the xp & XZ, keep up the good work!
Verstuurd vanaf mijn F5121 met Tapatalk
AndroPlus said:
Now it's official
I'll build TWRP for XZ, but I can't build for other variant as I don't have devices and can't maintain...
Click to expand...
Click to collapse
Hi, do you think this variant will work for the Sony X (not Performance) too?
I had some bad experiences flashing TWRP (i.e. with TWRP for Huawei M2, that wasn't suitable for the European device, only the Chinese one, leading to a bootloop) - I guess X and X Perf. aren't too different, but I'd like to make sure it fits
Thanks!!
xtools said:
Hi, do you think this variant will work for the Sony X (not Performance) too?
I had some bad experiences flashing TWRP (i.e. with TWRP for Huawei M2, that wasn't suitable for the European device, only the Chinese one, leading to a bootloop) - I guess X and X Perf. aren't too different, but I'd like to make sure it fits
Thanks!!
Click to expand...
Click to collapse
X has different SoC, so it won't work...
AndroPlus said:
X has different SoC, so it won't work...
Click to expand...
Click to collapse
So twrp for the x compact should/could work for the x? They have the same soc
kistigun said:
So twrp for the x compact should/could work for the x? They have the same soc
Click to expand...
Click to collapse
Maybe.
AndroPlus said:
Maybe.
Click to expand...
Click to collapse
okey, would like to test this. If it's not compatible could I just restore everything by reflashing original firmware ftf from sony?
kistigun said:
okey, would like to test this. If it's not compatible could I just restore everything by reflashing original firmware ftf from sony?
Click to expand...
Click to collapse
Yes, you can restore stock recovery by flashing FTF (FOTAKernel is recovery)
@AndroPlus bro, I can't get it working on my F8131 (custom kernel, not yours).
This is the flashing output:
Code:
[B][I][COLOR="Blue"]fastboot flash recovery twrp-3.0.2-0-dora.img[/COLOR][/I][/B]
target reported max download size of 268435456 bytes
sending 'recovery' (20600 KB)...
OKAY [ 0.638s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.797s
Combo keys (Power + Volume Down) turn device off after the "Your device has been unlocked..." message (and before sony logo shows up)!
Am I doing something wrong or forgetting something?
Btw, if I try to just boot into twrp while in fastboot, I get this error:
Code:
[B][I][COLOR="blue"]fastboot boot twrp-3.0.2-0-dora.img[/COLOR][/I][/B]
downloading 'boot.img'...
OKAY [ 0.643s]
booting...
[B][COLOR="Red"]FAILED (remote: dtb not found)[/COLOR][/B]
finished. total time: 1.068s
Thanks in advance!
serajr said:
@AndroPlus bro, I can't get it working on my F8131 (custom kernel, not yours).
Click to expand...
Click to collapse
Try to use my TWRP for MultiROM, it's fully functional from hardware recovery boot too.
Adrian DC said:
Try to use my TWRP for MultiROM, it's fully functional from hardware recovery boot too.
Click to expand...
Click to collapse
And it did work flawlessly at first try (downloaded multirom-20161116-recovery-fota-dora.zip > extracted twrp.img > fastboot flash recovery twrp.img)!
Thank you so much!! :highfive:
It really looks like Androplus needs to fix something on this!
hmm, maybe I missed something... when I build TWRP on my own, it's working.
I'll look into it.
AndroPlus said:
hmm, maybe I missed something... when I build TWRP on my own, it's working.
I'll look into it.
Click to expand...
Click to collapse
Thank you!
We're all waiting for that, once this is the official one!