PirateXPERIA Project - Sony Xperia M

PirateXPERIA Project - Sony Xperia M

Reserved
Changelog:
- Project paused until i will have time to look up kexex, and it´s use.
//EDIT: Project died with my device. So no more updates.
- Versions uses date, inside of numbers.(from next version)
- Downloads moved to BasketBuild
- Created bootanimation. (bootanimation.zip in downloads)
Version 2.1.1
- Kernel patch copy is recursive, you can add folders to pach.
Version 2.1.0
- Fixed kernel patch function. (thanx thichthat)
- Added support to run user's script before boot. (thanx thichthat)
- Changed CM Recovery Version for touch support (Fixed power-down bug too).
Version 2.0.0:
- Added CM11 Support
- Auto boot into recovery if ramdisk not found
- Load build-in recovery, when recovery not found
- need to flash cm11_addon.zip or cm11_addon.zip to get working
- added stock ROM support (with some extra optimalizations)
Version 1.10.0:
- TWRP Downgraded to 2.8.0.0 for mtp fix
- Fixed boot without config
Version 1.9.0:
- Can define kernel type (IMG/CPIO/FOLDER)
- TWRP recovery moved from /recovery to /sbin
- some bug fixes
Version 1.8.0:
- TWRP Updated to 2.8.4.0
- Changed logo colour
- Automatic patch kernel files from /system/kernel/patch
- Load recovery from FOTA
Version 1.7.0:
- Fixed logo position
- recoveries located in /system/kernel/recovery (TWRP located in kernel too)
- ramdisk located in /system/kernel/boot.cpio
- config file in /system/kernel/cofing
Version 1.6.0:
- Fixed Logo resultion
- Some bug fixes
- cpio images will deleted from ramdisk after one of it unpacked.
Version 1.5.0:
- Changed Logo
- Project renamed from MultiRecovery
to PirateXPERIA Project
Version 1.4.0:
- Added Philz Recovery
Version 1.3.0:
- Added CWM Recovery
- Added CyanogenMod Recovery
- Updated Kernel Version
Version 1.2.0:
- Updated Kernel Version
Version 1.0.0:
- Initial relase
- TWRP Recovery
- BattleField Boot logo
//When you see new version in challengelog, but not in downloads, just wait until i will upload it.
//Newest version can be relased few days after added to changelog. (time to test and compile it.)
Click to expand...
Click to collapse

Reserved
Woking on:
- Incudle MULTIROM by alvinhochun
- Higher freq. for manual overclocking. (use is optional)
- More variants of BootAnimation
- Fix screen shift bug in CWM and Philz Recovery.
- PirateXPERIA ROM
Click to expand...
Click to collapse
Know bugs:
- Screen shift bug in CWM and Philz Recovery.
- Phone will not in turn off when pressed Power off in CM Reovery
Click to expand...
Click to collapse
You can report bug here.
For advanced users, look into /system/kernel folder
config - configuration file. open with notepad++ (you can here change paths)
boot.cpio - ramdisk (overclocked cyanogenmod factory ramdisk)
recovery - folder with recoveryes.
script.sh - execute this file before boot to system/recovery.
patch -
this folder will copyred after ramdisk extract, and before execute ramdisk startup file.
here you can patch files from kernel. Applyed to boot.cpio and recoveries.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

awesome
Ill try this. I cant see the installation progress / logs in the cm recovery included in the cm12 package

Can it work on C1904/C2004?
Hi. Great job with the kernel dev. Have been waiting for an OC kernel for CM12. Problem is, I have a C2004 with C1904 firmware cross-flashed on it, on top of which i have CM-12 based Resurrection Remix ROM running. Will this kernel be able to run on my device, since you have mentioned only C1905 in your post?

manal.21sinha said:
Hi. Great job with the kernel dev. Have been waiting for an OC kernel for CM12. Problem is, I have a C2004 with C1904 firmware cross-flashed on it, on top of which i have CM-12 based Resurrection Remix ROM running. Will this kernel be able to run on my device, since you have mentioned only C1905 in your post?
Click to expand...
Click to collapse
Hi, i think no, just try. When it will no work, just flash your prevous kernel. Hope it works.

Tommienots said:
Ill try this. I cant see the installation progress / logs in the cm recovery included in the cm12 package
Click to expand...
Click to collapse
I will try to fix it.

SystemUI FC on c1904/2004
gouster3 said:
Hi, i think no, just try. When it will no work, just flash your prevous kernel. Hope it works.
Click to expand...
Click to collapse
Hi I flashed your kernel today on my device with configuration mentioned above. SystemUI keeps on FCing. So it doesn't work for now. Really hope it will be workable for c1904/2004 in the near future. Keep up the good work!
---------- Post added at 12:33 PM ---------- Previous post was at 11:58 AM ----------
manal.21sinha said:
Hi I flashed your kernel today on my device with configuration mentioned above. SystemUI keeps on FCing. So it doesn't work for now. Really hope it will be workable for c1904/2004 in the near future. Keep up the good work!
Click to expand...
Click to collapse
Also, Philz recovery doesn't load when I do the necessary steps. Also, the CWM recovery included has a screen shift bug. Please look into this if you can. Thanks!

I Will try this awesome kernel on pa 4.6 beta 6, i will report soon if this kernel works perfectly or not ..
Edit: i get only blank screen after boot logo appear ..
But i'm really confused, OP says support cm11, so this kernel probably work with kitkat rom, but i'm wrong .. :crying:
Sorry for my bad engelish

manal.21sinha said:
Hi I flashed your kernel today on my device with configuration mentioned above. SystemUI keeps on FCing. So it doesn't work for now. Really hope it will be workable for c1904/2004 in the near future. Keep up the good work!
Click to expand...
Click to collapse
Thank you. C2004 Not supported. Maybe later.
manal.21sinha said:
Also, Philz recovery doesn't load when I do the necessary steps. Also, the CWM recovery included has a screen shift bug. Please look into this if you can. Thanks!
Click to expand...
Click to collapse
Yes. I have it in to-do list.

itsnie said:
I Will try this awesome kernel on pa 4.6 beta 6, i will report soon if this kernel works perfectly or not ..
Edit: i get only blank screen after boot logo appear ..
But i'm really confused, OP says support cm11, so this kernel probably work with kitkat rom, but i'm wrong .. :crying:
Sorry for my bad engelish
Click to expand...
Click to collapse
Working just on CM12 (Lollipop) //Edit: now cm11 & stock supported

Can i boot any roms with this multirom?

itsnie said:
Can i boot any roms with this multirom?
Click to expand...
Click to collapse
No. This is not multirom, but MultiRecovery. (you can have TWRP, Philz, CWM and CM Recoveryes in one kernel)
if you mean cm11_addon cm12_addon and stock_addon, you can use only one of this.
i dont want to upload new kernel versions for both, so you must install kernel first. and then one of addons.
if you flash more of addons, it will use last flashed addon.
MultiRom is another project by alvinhochun
but i want implement it in my MultiRecovery kernel in future.
But, when you want, you can extract ramdisk from kernels, replace recovery cpio´s in /system/kernel/recovery
and now you can boot 4 different kernels. but without editing this kernels you can use kenrel only for rom located in /system.
only cm11, cm12 and stock rom are supported.
but if you want boot "unsupported" rom with this kernel, you must unpack ramdisk.cpio from rom kernel, and then move it in /system/boot.cpio.
cm11_addon, cm12_addon and stock_addon flashes only thit boot.cpio. so you can support any ramdisk you want.
but you will not have OC.

I copied my fstab.qcom and init.qcom.rc to /patch folder but it didn't replace the original files
I found this code in your init.sh:
Code:
busybox cp /system/kernel/patch /
And I think it should be changed to
Code:
busybox cp /system/kernel/patch/* /
We should also have an option to run user's script before system boot. I added this line:
Code:
exec /system/kernel/script.sh

Thanx. I have not trayed patch function yet.
I will change this in next version.

gouster3 said:
Thanx. I have not trayed patch function yet.
I will change this in next version.
Click to expand...
Click to collapse
i think using -R is allowed in busybox. or not? cp -r /system/kernel/patch/* /

Help!! Overclock works, but UI force closes and nav buttons, notifications and status bar dissapear.... Help please... thanks

ByronFer said:
Help!! Overclock works, but UI force closes and nav buttons, notifications and status bar dissapear.... Help please... thanks
Click to expand...
Click to collapse
Which rom are you using? i have same problem with Resurrection Remix 5.3.3.
Try cm-12-20150123-UNOFFICIAL-nicki by PecanCM´s CM12
Now i am using Resurrection Remix 5.3.3, with my kernel, but i have copyred ramdisk from rom into /system/kernel/boot.cpio.
it is solution too. but you will have not overclock.

Related

[Development Stopped][JB 4.1.2][Xperia S/SL] MIUI V5 ML LB/UB [4.8.1] - STOCK BASED

{
"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"
}
DEVELOPMENT OF THIS STOCK BASED MIUI V5 ROM IS STOPPED
THANKS TO ALL ROM USERS FOR YOUR SUPPORT
TRY OUR KITKAT BASED MIUI V5 ROM LINK
ROM AUTHORS:
FD-Ghost - http://www.miui.com/space-uid-31268862.html
City Zero - http://www.miui.com/home.php?mod=space&uid=100209901
Midnight Souls (kin912) - http://www.miui.com/home.php?mod=space&uid=176034
Balcan GSM - http://en.miui.com/space-uid-84584497.html
ROM INFORMATION:
- Rom Base:
Sony Official Stock FW 6.2.B.1.96 For Sony Xperia S LT26i/LT26ii (Nozomi) - http://developer.sonymobile.com
- MIUI Base(Closed Source):
Compatible CPU Patchrom Base - http://www.miui.com/getrom.php
- ROM Build:
Xiaomi MIUI Patchrom Adaptation - https://github.com/MiCode/patchrom
- Kernel Base:
Sony Stock Kernel 3.4/6.2.B.1.96 For Sony Xperia S LT26i/LT26ii (Nozomi) - http://developer.sonymobile.com
ROM CREDITS:
Upper Mentioned Rom Authors -
Specially Thanks To Great Dev Midnight Souls (@ kin912)
Xiaomi MIUI Development Team - http://www.miui.com/getrom.php
Making Great MIUI Rom And Developing Patchrom For Adaptation And Porting MIUI To Many Devices
All Other Devs Which Help With Sony Xperia Custom Kernels,Rooting Methods,Recoveries And Advices
- @ lpws521
- @ DooMLoRD
- @ schickel
- @ RaymanFX
- @ Rimmer1966
- @ sijav
- @ letama
- @ panel1
- @ Novastylez
- @ ViPER
- @ djoliver
!!! THIS ROM IS IN STABILE STAGE WITH CONSTANT DEBUGGING AND UPGRADING TO LATEST MIUI RELEASES !!!
- All Files And Tutorials Except Rom Are Collected From Internet & Xda Forums,So All Credits Are Going To Their Authors. -
- I'm Not Responsible For Any Eventual Errors And Misbehaving Of Your Devices. -
- Xiaomi MIUI Is One Of The Greatest And Most Unique Custom Roms For Android Devices.
- MIUI Developement Team Abandoned Stock Based MIUI For Sony Xperia S/SL In MIUI Version V4
- Till Then Our Team Bringing You CM Based MIUI V5 Port Every Week.
- Our Team Is Group Of Enthusiasts Which Try To Bring Full MIUI V5 Experience On Xperia S/SL.
- Please Remember That Our Work Is Voluntary,And Not An Obligation.
ROM WORK FOR LOCKED/UNLOCKED BOOTLOADERS ON XPERIA S/SL DEVICES
IN ORDER TO KEEP THREAD CLEAN PLEASE:
Use Thanks Button If You Are Grateful For Rom Or Advice
For Viewing Screenshots & Bug Feedback Please Use Thread Nav - Bar
[REQUIREMENTS]
[*]Windows/Linux/Mac Powered Computer
[*]Installed Latest Java Runtime Environment Depends Of Your Computer OS - LINK
[*]Android Device Drivers Installed
[*]Enabled Settings → Security → Unknown Sources & Settings → Development → Usb Debugging
[*]Phone Battery Charged - 60% At Least.
[STOCK ROM & RECOVERY FLASH PROCEDURE]
[*]Download And Install Latest Flash-Tool Software Depends Of Your Computer OS - LINK
[*]Download And Install Adb & Fastboot - WINDOWS LINK / LINUX & MAC LINK
[*]Download Sony Stock FW 6.2.B.1.96 And Flash It Via Flash-Tool - LINK
- FLASHING RECOVERY -
UNLOCKED BOOTLOADER :
Download Advance Stock Kernel(FW .96 - CWM Recovery Included) - LINK
Reboot Device Into Fastboot Mode With Command:
Code:
adb reboot bootloader
Flash The Kernel Using Command :
Code:
fastboot flash boot kernel.elf
(Where Kernel.elf (.img) Is The Name Of The File You Downloaded)
LOCKED BOOTLOADER (Please Test It - I Dont Have Device With LB):
Root FW .96 Stock Rom Using Doomlord's Method - LINK
Download & Extract CWM Recovery For LB And Save It On C: - LINK
Go To Extracted Folder And Execute Cwm-Install-En.Bat
Follow The On-Screen Instructions
[FLASH MIUI ROM]
DOWNLOAD XPERIA S/SL MIUI V5 4.8.1 ROM Latest Stock Based Version
[QRCODE]http://miuirom.xiaomi.com/rom/u101516757/4.8.1/miui_26_cheng_4.8.1_f9dad992d6_4.1.zip[/QRCODE]
DOWNLOAD XPERIA S/SL MIUI V5 4.7.25 MULTILANGUAGE ROM (No OTA Support - Repacked Rom ) - Latest Stock BasedVersion
(Flash It Via Recovery And Apply Language Via Set Locale App If You Cant See It In Language List)
[QRCODE]https://goo.im/devs/ibotpeaches/miuiandroid/releases/4.7.25m/xiaomi.eu_multi_LT26i_4.7.25_jb-4.1.zip[/QRCODE]
1. Put XXX.Zip Copied To The Root Directory Of Cell Phone (That Is A Direct Copy)
2. Enter Recovery (Twrp Or Cwm) (Turn Off, Turn On & Repeatedly Keep Pressing Vol+)
3. Select [Wipe Data / Factory Reset] → [Yes]
4. Select [Wipe Cache Partition] → [Yes ]
5. Select [Advanced] → [Wipe Dalvik Cache] → [ Yes ] → Back
6. Select [Install Zip From Sdcard] → [Choose Zip From Sdcard] → [XXX.Zip] → [Yes]
7. Wait Flash Finished, Press Back And Select Reboot System Now [], The Phone Going To Automatically Restart With Installed Miui Rom.
First Boot Need ~ 3 - 5 Min.
- FLASH GAPPS -
DOWNLOAD 4.1.2 GAPPS
[QRCODE]http://d-h.st/CAg[/QRCODE]
1.After First Boot Reboot Your Phone To Recovery Again.
2.Select [Install Zip From Sdcard] → [Choose Zip From Sdcard]→ [Miuiandroid_Gapps-4.1.2-Small_Signed.Zip] → [Yes]
3. Wait Flash Finished, Press Back And Select Reboot System Now [], The Phone Going To Automatically Restart With Installed Gapps.
4.Set Up Your Google And Xiaomi Accounts(For Themes).
DOWNLOAD WSM TOOLS FOR ADDING VARIOUS OPTIONS FOR MIUI - LINK
Current Rom Status:
Rom Proper (Without Errors) Builded With MI Code Patchrom
Rom Partially Debugged Before Patchrom FullOTA Build
Rom Hardly Debugged And Fixed For Everyday Use > 300MB Of Free RAM
? - EVERYTHING IS WORKING - ?
Taking Screenshot Will Reboot Device- FIXED
Auto Brightness Disabled- FIXED
MTP Connection FC - FIXED
All Sounds Muted Upon First Boot - You Must Set Them Manualy- FIXED
No Mobile Data Signal - FIXED
Lockscreen Not Showed Up - FIXED
Camera Dont Work - Only Black - FIXED
Home Key Dont Work - FIXED
When Somebody Call You Its Always Busy - FIXED
Browser FC - FIXED
Provision App FC - FIXED
Cant Change Rom Language Bug - FIXED
Input Method Dont Work - FIXED
Rom Booted With Lot Of Bugs - FIXED
Constantly Bootloop On System Start - FIXED
ADB Logcat Not Working - FIXED
OFFICIAL MIUI CHANGELOG
XDA:DevDB Information
[Development Stopped][JB 4.1.2][Xperia S/SL] MIUI V5 ML LB/UB [4.8.1] - STOCK BASED, ROM for the Sony Xperia S
Contributors
ghetto_thug, FD-GHOST, kin912
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Sony Stock FW 6.2.B.1.96 + Recovery
Based On: Official Sony Stock FW 6.2.B.1.96
Version Information
Status: Stable
Current Stable Version: 4.8.1
Stable Release Date: 2014-08-01
Created 2013-09-30
Last Updated 2014-08-19

Is there bootlop on Sony logo or MIUI logo ?
I had some problems with bootlop on sony logo when I have tried to repack kernel.
Sent from my LT26i using xda app-developers app

panel1 said:
Is there bootlop on Sony logo or MIUI logo ?
I had some problems with bootlop on sony logo when I have tried to repack kernel.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
This same problem. Bootlop on miui logo.
Full wipe (dalvik, cache, data, system) before install.
ROM is without kernel . which kernel should I use?

karellang said:
This same problem. Bootlop on miui logo.
Full wipe (dalvik, cache, data, system) before install.
ROM is without kernel . which kernel should I use?
Click to expand...
Click to collapse
Stock One.

Do you think it's possible to get it booting without any modifications in the kernel? I tried to port MIUI v5 for LB in August but failed (bootloop).
Gesendet von meinem LT26i mit Tapatalk 4

djolivier said:
Do you think it's possible to get it booting without any modifications in the kernel? I tried to port MIUI v5 for LB in August but failed (bootloop).
Gesendet von meinem LT26i mit Tapatalk 4
Click to expand...
Click to collapse
It's definitely possible. I've got an Xperia T and managed to get v5 booting on a stock base using the stock kernel.. It's not perfect, have some issues with the notification led's and some bugs with the audio, but everything else works fine..

Can somebody try this?
power on the phone
after the bootloop shut down the phone
flash a working kernel / rom ....
restart the system
run in terminal "su cat proc/last_kmsg > [path to the sdcard]/kmsg.txt"
and please upload kmsg.txt here.
http://forum.xda-developers.com/showthread.php?p=23036410

I don't have any time to mess with MIUI at the moment, but I hope I can provide some guideance out of the blue:
* Yes, you can run MIUI on a stock kernel. But not using a stock boot.img. You need to modify the ramdisk (at least that's what I found when I worked on my own patchrom).
* To get adb logcat and things working, you need to set ro.secure to 0 in the ramdisk. It's probably set to 1.

But I now that we're talking about MIUI for Xperia S, I remember there is MIUIv4 for devices with locked bootloaders. I even tested it and it was working like a charm. As my device's bootloader is "ununlockable" but it worked, I guess a Stock boot.img has been used. Or am I wrong when I say that each little modification in the kernel renders it unusable for devices with LB (because of a special fingerprint/signature whatever of Sony that gets lost)?
Gesendet von meinem LT26i mit Tapatalk 4

djolivier said:
But I now that we're talking about MIUI for Xperia S, I remember there is MIUIv4 for devices with locked bootloaders. I even tested it and it was working like a charm. As my device's bootloader is "ununlockable" but it worked, I guess a Stock boot.img has been used. Or am I wrong when I say that each little modification in the kernel renders it unusable for devices with LB (because of a special fingerprint/signature whatever of Sony that gets lost)?
Gesendet von meinem LT26i mit Tapatalk 4
Click to expand...
Click to collapse
You are right with your last point, but remember: we're talking about MIUI v5 here.
And MIUI 5 definately needs a different ramdisk than MUIU 4.
So regarding MIUI on locked bootloaders, it more ore less depends on the OEM (read: Sony) if you're able to get it working or not, because they decide what the stock ramdisk will contain, afterall.
There might be workarounds to this (hijacking the ramdisk using init.d scripts), but I did not test those as my device was unlockable right from the start. It might also be possible to get MIUI 5 running without any ramdisk additions at all, but that needs to be tested excessively, for which I sadly lack time at the moment.

RaymanFX said:
I don't have any time to mess with MIUI at the moment, but I hope I can provide some guideance out of the blue:
* Yes, you can run MIUI on a stock kernel. But not using a stock boot.img. You need to modify the ramdisk (at least that's what I found when I worked on my own patchrom).
* To get adb logcat and things working, you need to set ro.secure to 0 in the ramdisk. It's probably set to 1.
Click to expand...
Click to collapse
I will try to do this tomorrow. I have no time too, but will try to find some time. Thanks for guide

Any progress?
Sent from my LT26i using xda app-developers app

hamad335500 said:
Any progress?
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
+1

Patience is a virtue, guys. It's really not a piece of cake to port MIUI using Stock as a base.

djolivier said:
Patience is a virtue, guys. It's really not a piece of cake to port MIUI using Stock as a base.
Click to expand...
Click to collapse
Sent from my LT26i using xda app-developers app

RaymanFX said:
I don't have any time to mess with MIUI at the moment, but I hope I can provide some guideance out of the blue:
* Yes, you can run MIUI on a stock kernel. But not using a stock boot.img. You need to modify the ramdisk (at least that's what I found when I worked on my own patchrom).
* To get adb logcat and things working, you need to set ro.secure to 0 in the ramdisk. It's probably set to 1.
Click to expand...
Click to collapse
I had ported some roms from nozomi to aoba,like tita rom and baidu os,all base on stock ICS.When I used the stock ramdisk the phone bootloop and the adb shell did not start.So I must add the shell in ramdisk and the rom work well.
I also ported the miui v5 base on cm.I did not add the shell in ramdisk and it stop at the "mi" bootanimation.But the key lights on and I can get the log.
About this miui v5 base on stockJB,I modify the ramdisk or not all bootloop.The worse thing is the adb logcat can not work.So I think the problem is the micode port in the .jar files.
@Rimmer1966 @djolivier @sijav
I need the keypoint.Nomaly a rom make out can boot at less the adb logcat work

kin912 said:
I had ported some roms from nozomi to aoba,like tita rom and baidu os,all base on stock ICS.When I used the stock ramdisk the phone bootloop and the adb shell did not start.So I must add the shell in ramdisk and the rom work well.
I also ported the miui v5 base on cm.I did not add the shell in ramdisk and it stop at the "mi" bootanimation.But the key lights on and I can get the log.
About this miui v5 base on stockJB,I modify the ramdisk or not all bootloop.The worse thing is the adb logcat can not work.So I think the problem is the micode port in the .jar files.
@Rimmer1966 @djolivier @sijav
I need the keypoint.Nomaly a rom make out can boot at less the adb logcat work
Click to expand...
Click to collapse
I had the same problem with the logcat. What I did was use a Kernel with an unsecure ramdisk, DoomKernel for example. I modified it to start the logcat earlier, even then the logcat only works properly on Linux. Once I'd worked out the bugs I was able to switch back to a stock kernel without making any modifications.
Hope this helps you..

Also as @RaymanFX has already mentioned, it is possible to modify the ramdisk without de- and recompiling the kernel using init.d scripts. But @Rimmer1966's method seems more likely to work...
Unfortunately, I don't have access to a computer ATM (mine is being repaired) and also, my bootloader cannot be unlocked (...easily), which means I'll have to try the init.d script method (as soon as I get my laptop back).
Gesendet von meinem Sony Xperia S mit Tapatalk 4

Rimmer1966 said:
I had the same problem with the logcat. What I did was use a Kernel with an unsecure ramdisk, DoomKernel for example. I modified it to start the logcat earlier, even then the logcat only works properly on Linux. Once I'd worked out the bugs I was able to switch back to a stock kernel without making any modifications.
Hope this helps you..
Click to expand...
Click to collapse
I had set ro.secure=0,ro.debuggable=1,persist.service.adb.enable=1 in the ramdisk.But the fact is the adb service is not start when the phone boot.
So I can not get the logcat.
I think when you port the phone is stop at the bootanimation,the notification led is on too.You can get the logcat.
@djolivier The init.d support start later than the adb support,I think your method is not work.
If I can get the logcat,I can handle this by myself.I had ported many times.I have no idea and I want to give up now.

kin912 said:
I had ported some roms from nozomi to aoba,like tita rom and baidu os,all base on stock ICS.When I used the stock ramdisk the phone bootloop and the adb shell did not start.So I must add the shell in ramdisk and the rom work well.
I also ported the miui v5 base on cm.I did not add the shell in ramdisk and it stop at the "mi" bootanimation.But the key lights on and I can get the log.
About this miui v5 base on stockJB,I modify the ramdisk or not all bootloop.The worse thing is the adb logcat can not work.So I think the problem is the micode port in the .jar files.
@Rimmer1966 @djolivier @sijav
I need the keypoint.Nomaly a rom make out can boot at less the adb logcat work
Click to expand...
Click to collapse
sorry for delay (I lost my computer and didn't get internet and so on), I'm not sure if you figure it out by now or not, you should put those lines on in build.prop in the room (because those values will be over written by build.prop in rom)
so you should look for ro.debuggable and persist.sys.usb.config and change them to (or create if not exists):
Code:
ro.debuggable=1
persist.sys.usb.config=adb
good luck

[MOD] MultiROM v31x [13/02/2015]

Changelog
DOWNLOADs
You can get everything from my build server.
CHANGELOG
Code:
[b]13/02/2015:[/b] Updated to v31x | Updated adb | Print error when multirom crashes | Added support for multiple entries per path in fstab | Set is_second_boot also if mrom_kexecd=1 is present in /proc/cmdline | Support interlaced PNGs | Updated to MultiROM TWRP 2.8.5 (incl. upstream <-> TWRP 2.8.5.0)
[b]17/01/2015:[/b] Updated to MultiROM TWRP 2.8.4 (incl. upstream <-> TWRP 2.8.4.0), fixed "Swap ROMs" feature
[b]08/01/2015:[/b] Inserted dummy line instead of removing to prevent breaking IFs (fixes the installation of AOSPA 5.0)
[b]04/01/2015:[/b] Updated to MultiROM TWRP 2.8.3 (incl. upstream <-> TWRP 2.8.1.3)
[b]08/12/2014:[/b] Fixed the installation of L-based ROMs as secondary ROMs
[b]04/12/2014:[/b] TWRP upstream
[b]28/11/2014:[/b] Moar TWRP upstream, updated to MultiROM v30x, fixed klog saving and text size on emergency reboot screen
[B]28/11/2014:[/B] Updated to MultiROM TWRP 2.8.1 (incl. upstream <-> TWRP 2.8.1.0) | Fixed perms of extract_elf_ramdisk
[B]23/10/2014:[/B] Upstream: Updated to v29x | Added "DirtyUnicorns icon" | Added device hook to allow incomplete fstab file | Bind mount /realdata to /data for rom quirks to work properly
[B]02/10/2014:[/B] Added support for external sdcard
[B]27/09/2014[/B]: Fixes for recovery, updated to MultiROM v28x (device-specific version)
[B]02/09/2014[/B]: Initial public release.

SUPPORTED KERNELs
OmniROM (and DirtyUnicorns, which is based off Omni)
lightning kernel by nikhil18

psycho-punk said:
Can OmniROM be replaced with some other after installing MultiROM?
Click to expand...
Click to collapse
I'm running Dirty Unicorns ROM which is omni based rom, will this work?
I'm want to make PA my secondary rom..
Thanks

psycho-punk said:
Can OmniROM be replaced with some other after installing MultiROM?
Click to expand...
Click to collapse
DU should work too, but otherwise no.
AndreIrawan97 said:
I'm running Dirty Unicorns ROM which is omni based rom, will this work?
I'm want to make PA my secondary rom..
Thanks
Click to expand...
Click to collapse
Yes, probably.

Thanks for this, it gave new life to my ZL! Multiboot rocks! I've managed to run Omni, CM11 and Carbon KK , so far so good. Are you also by chance doing a stock kernel for ZL that works with multirom, just like your stock kernel in Z? Hope you could also create stock kernel for ZL, really appreciate it. Thanks in advance.

What about adding MultiRom support to 4.4.4 stock kernel? Should we wait for new kernel source release from Sony?

francarl said:
What about adding MultiRom support to 4.4.4 stock kernel? Should we wait for new kernel source release from Sony?
Click to expand...
Click to collapse
I'd need you to upload a stock boot.img/kernel.elf in that case.

Olivier said:
I'd need you to upload a stock boot.img/kernel.elf in that case.
Click to expand...
Click to collapse
Will this work, it is based on stock .283 but with added features -
http://www.mediafire.com/download/1bf5bhjbtbvxhnk/Advanced_stock+kernel_for_KK_10.5.1.A.0.283.zip
Features:
Dual recovery - CWM Philz Touch 6.48.4/TWRP 2.7.1.0 (vol up - CWM / vol down - TWRP)
Init.d suport
Debugging enabled by default
Disable debugging notification icon in the status bar
Kernel insecure (ro.secure=0)
Kernel taken from here - http://forum.xda-developers.com/xpe...ed-stock-kernel-kitkat-4-4-t2873475#undefined
I've also informed the developer if he is ok with it being modified to have kexec patch.

^^ probably not, as multirom needs w/ kexec modification, which isn't listed above.
Did someone manage to boot ubuntu ( http://forum.xda-developers.com/showthread.php?t=2434585) in multirom? How?
Could we have native ubuntu touch support with the next version, please?
Gesendet von meinem Xperia ZL mit Tapatalk

stock rom as primary rom
ryanrudolf said:
Will this work, it is based on stock .283 but with added features -
http://www.mediafire.com/download/1bf5bhjbtbvxhnk/Advanced_stock+kernel_for_KK_10.5.1.A.0.283.zip
Features:
Dual recovery - CWM Philz Touch 6.48.4/TWRP 2.7.1.0 (vol up - CWM / vol down - TWRP)
Init.d suport
Debugging enabled by default
Disable debugging notification icon in the status bar
Kernel insecure (ro.secure=0)
Kernel taken from here - http://forum.xda-developers.com/xpe...ed-stock-kernel-kitkat-4-4-t2873475#undefined
I've also informed the developer if he is ok with it being modified to have kexec patch.
Click to expand...
Click to collapse
Thank you.
So could this kernel be used to start stock rom 10.5.1.A.0.283 as primary rom?

Hey guys, a new update is up. There have been many changes, you can now install ROM to the external sdcard. Enjoy!

thanks for this! im using latest update and also lightning kernel and CM11 as primary rom, it works good! im thinking for stock kernel to work as secondary rom, we have to modify the mount points? edit the ramdisk? just trying to understand before i try to do it on my own. really wanted to have working CM11 as primary and stock as secondary. thanks again

Olivier said:
Hey guys, a new update is up. There have been many changes, you can now install ROM to the external sdcard. Enjoy!
Click to expand...
Click to collapse
Thanks @olivier. Ext SD support is great.
I was wondering if we will get stock rom support as primary in the future.

ryanrudolf said:
thanks for this! im using latest update and also lightning kernel and CM11 as primary rom, it works good! im thinking for stock kernel to work as secondary rom, we have to modify the mount points? edit the ramdisk? just trying to understand before i try to do it on my own. really wanted to have working CM11 as primary and stock as secondary. thanks again
Click to expand...
Click to collapse
You can do the following (once my stock-based kernel is available): Install a stock rom as primary, back it up and restore it as secondary ROM.
Kr3i0s said:
Thanks @olivier. Ext SD support is great.
I was wondering if we will get stock rom support as primary in the future.
Click to expand...
Click to collapse
I will as soon as I get enough time.
Gesendet von meinem Xperia Z mit Tapatalk

Olivier said:
You can do the following (once my stock-based kernel is available): Install a stock rom as primary, back it up and restore it as secondary ROM.
I will as soon as I get enough time.
Gesendet von meinem Xperia Z mit Tapatalk
Click to expand...
Click to collapse
sorry for asking, but do you have any news on this? thanks

francarl said:
sorry for asking, but do you have any news on this? thanks
Click to expand...
Click to collapse
Patience please, I do have other things in life to do - I'll let you know for sure.
Gesendet von meinem Xperia Z mit Tapatalk

MultiROM v29x is up!
As for the Stock-based kernel: I have decided not to support Stock ROMs officially, but you can always use the lightning kernel by nikhil18 to have a Stock-based kernel with kexec-hardboot support.

Olivier said:
MultiROM v29x is up!
As for the Stock-based kernel: I have decided not to support Stock ROMs officially, but you can always use the lightning kernel by nikhil18 to have a Stock-based kernel with kexec-hardboot support.
Click to expand...
Click to collapse
@Olivier which version of lightning kernel to use?

Kr3i0s said:
@Olivier which version of lightning kernel to use?
Click to expand...
Click to collapse
The one for Stock ROMs.

[RECOVERY] KANG TWRP TF300T [email protected] JULY 28

TWRP for Transformer Pad TF300T
{
"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"
}
MUST BE ON A BOOTLOADER ENDING IN 27.1 or 27.5
Changelog 2.8.7.2
- All Upstream changes
- Small changes to the 'new theme' (thx z31s1g)
- Added flash to staging partition, via flash image feature
Changelog 2.8.7.1
- Removed ability to flash raw .img files....
- gui: keyboard: support longpress label offset, code cleanup ( Thx @_that)
- Added flashable zip
- merged upstream changes
Changelog- 2.8.7.0
- Fully merged 2.8.7.0 source from upstream
- Removed SU from twrp ( Its useless & only takes up extra room)
Changelog- 2.8.6.5
- New theme fully implemented ( Huge thx to @z31s1g ) Still a WIP
- Fix mount -o bind error on recreating /data/media/0 (Huge thx to @xiaolu ) & ( @_that )
- All upstream merges by Team Win
Changelog 2.8.6.1
- GUI: Prevent duplicate page overlays. Thx Matt & _that
- Replace legacy DEVICE_RESOLUTION with the new TW_THEME
- Using new common repo to build recovery.
- Build with grimlocks-5.1 kernel from zombi
- All upstream changes. Thx TeamWin
Changelog- 2.8.6.0
- All upstream changes (They are on git)
- Cleaned up external mount labels
Changelog- 2.8.5.1
- Added dock sd card support to twrp
Changelog- 2.8.5.0
- Added formatting of ext sdcard for ROM2SD & DATA2SD
- Added ability to backup ext sdcard partitions
- Added reboot to recovery & reboot to bootloader from with TWRP
- Fixed error formatting /data to f2fs <- Thx Dees Troy for this fix
- A few upstream changes
Click to expand...
Click to collapse
UPGRADE INSTRUCTIONS----------------------------------------------------------------------------------------------------------------------------------------
- Flashing recovery with fastboot.
- Boot tablet into fastboot.
Code:
fastboot -i 0x0B05 flash recovery foo.img
- Replace foo with the file name.
- Once flashed reboot into bootloader.
Code:
fastboot reboot-bootloader
- Enter recovery.
-FLASHING WITH 'dd'
You will need a super user terminal to make this work .....
Code:
su
Code:
dd if=/sdcard/foo.img of=/dev/block/mmcblk0p4
Replace foo.img with the recovery image name .....
This will move the recovery image to /staging so on the next boot it flashes it to /recovery
So make sure you do a reboot before trying to enter recovery .......
This command also expects the image to be in /sdcard
----------------------------------------------------------------------------------------------------------------------------------------
XDA:DevDB Information
TWRP for TF300T [KANG], Tool/Utility for the Asus Transformer TF300T
Contributors
lj50036, hardslog, DrBeaker
Source Code: https://github.com/zombi-x
Version Information
Status: Testing
Created 2015-03-05
Last Updated 2015-07-21

Downloads
OLDER VERSIONS
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1
TWRP [email protected] KANG FLASHABLE ZIP FULL MIRROR 1
TWRP [email protected] KANG FULL MIRROR 1

The more you know
JOIN US ON IRC !!!https://webchat.frt/
Channel: ##zombi-x
HOW TO TAKE A RECOVERY LOGYou will be taking this log cause of some kind of error message .....
Once you get and error message, here is how to retrieve a recovery log ....
Using a PC with adb/fastboot installed on it, and if windows the correct drivers. ....
Code:
adb pull /tmp/recovery.log
This log will be in the same directory as the terminal/cmd window is cd'd into ....
Now you have the log, upload it to a pasting site or for download, and give us a link....

You are a sneaky bugger aren't you? :laugh:

hardslog said:
You are a sneaky bugger aren't you? :laugh:
Click to expand...
Click to collapse
You know me @hardslog .....

Could you remove showing the kernel boot and add dock SD card mount in next relese?

You may also want to add instructions for noobs... Is it a blob, img or zip... Is it flashable in recovery, fastboot... ijs...

Dredz said:
You may also want to add instructions for noobs... Is it a blob, img or zip... Is it flashable in recovery, fastboot... ijs...
Click to expand...
Click to collapse
it is a blob file for fastboot flashing.

Clamor said:
it is a blob file for fastboot flashing.
Click to expand...
Click to collapse
This, I know... However noobs and people just picking up this tablet may not. It's good to have the info in the OP to keep it from being asked hundreds of times in the thread.

Clamor said:
Could you remove showing the kernel boot and add dock SD card mount in next relese?
Click to expand...
Click to collapse
Yes I add the dock sd card, the framebuffer is part of the zImage and something we have for debugging ....
The framebuffer is going to stay, but I may be able to repack the recovery with a different zImage.....
I just dont know how much demand for it or time I would like to spend on it .....
Thx Josh
Dredz said:
You may also want to add instructions for noobs... Is it a blob, img or zip... Is it flashable in recovery, fastboot... ijs...
Click to expand...
Click to collapse
I will add some instrution over the next few days, yes ..... :good:
Yes for it is a blob, but the build outputs a recovery.img and I see no need to rename it .....
Thx Josh

I had in the 2.8.1 being able to repair an exfat 64GB external micro sd card.
Upgraded to 2.8.5 the only option is to change the file system. Went back to 2.8.1 and it no longer is available now.
Is this the same for others?
Regards
Duke

NEW KANG !!!
NEW TWRP 2.8.6.0 FOR ALL YOUR FLASHING NEEDS !!!!!
Changelog -2.8.6.0
- All upstream changes (They are on git)
- Cleaned up external mount labels
Click to expand...
Click to collapse
Thx Josh

lj50036 said:
NEW KANG !!!
NEW TWRP 2.8.6.0 FOR ALL YOUR FLASHING NEEDS !!!!!
Thx Josh
Click to expand...
Click to collapse
is this for use with any rom or only for KANG Omni

lbeavisc said:
is this for use with any rom or only for KANG Omni
Click to expand...
Click to collapse
You should be able to use it to install any rom of your choice ...... :good:
Thx Josh

lbeavisc said:
is this for use with any rom or only for KANG Omni
Click to expand...
Click to collapse
Works great with KatKiss 5.1!
Just make sure that you do not try to install it from within TWRP, using the image installation functionality. I did that yesterday, and ended up without a recovery and with a tablet that would not allow me to install one. I had to do a backup/full wipe/restore of my tablet to revive it. No harm done, but I got a big scare!

KritonK said:
Works great with KatKiss 5.1!
Just make sure that you do not try to install it from within TWRP, using the image installation functionality. I did that yesterday, and ended up without a recovery and with a tablet that would not allow me to install one. I had to do a backup/full wipe/restore of my tablet to revive it. No harm done, but I got a big scare!
Click to expand...
Click to collapse
Its not an image ? its a blob .... :good:
Thx Josh

lj50036 said:
Its not an image ? its a blob .... :good:
Click to expand...
Click to collapse
Which is why one should definitely not do what I did, no matter how tempted one is!
BTW, can someone point me to a description of what the .img and .blob formats are? I haven't been able to find anything.

KritonK said:
Which is why one should definitely not do what I did, no matter how tempted one is!
BTW, can someone point me to a description of what the .img and .blob formats are? I haven't been able to find anything.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=36925180
Check out this thread by @_that lots of good info in there ....
Thx Josh

lj50036 said:
http://forum.xda-developers.com/showpost.php?p=36925180
Check out this thread by @_that lots of good info in there ....
Click to expand...
Click to collapse
Very enlightening. So, if I understood things correctly, if I unpack the recovery blob with blobunpack, then twrp_tf300t_kang_2.8.6.0.img.SOS, which is contained therein, is the actual image, which I could, theoretically, use with tools that handle images, such as the TWRP image installer. (I've learned my lesson, however, and will stick to the tried and true methods!)

KritonK said:
Very enlightening. So, if I understood things correctly, if I unpack the recovery blob with blobunpack, then twrp_tf300t_kang_2.8.6.0.img.SOS, which is contained therein, is the actual image, which I could, theoretically, use with tools that handle images, such as the TWRP image installer. (I've learned my lesson, however, and will stick to the tried and true methods!)
Click to expand...
Click to collapse
No the device will not flash an image.... It has to be a blob .....
There is alot of info in that guide......
Thx Josh

[AROMA]3.0.8 Official CrisKelo MultiRom V7.8.1 LB&UB.

{
"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"
}
︻╦̴╦═━───━━━✺~CRISKELO THEME~✺━━━───━═╦̴╦︻
⇝CrisKelo Theme⇜
︻╦̴╦═━───━━━✺~CRISKELO MULTIROM~✺━━━───━═╦̴╦︻
No Bugs
IMPORTANT to Know
The OTA-Updater dont work on Z1 with D_Vovan_238 versions, all Updates only on XDA and Official CrisKelo page!
Locked Bootloader
Way 1.
You must install 4.4.4 with Root and CWM. If you don't come from 4.4.4 then
- Install Offical 4.4.4 Firmware. 6903 Firmware
- Root Your Device
- Install CWM
Copy my ROM on your Internal SD Card
Install My ROM with Wipe/Factory Reset
Reboot your Phone
enjoy
Locked Bootloader Root problems Flash >>Su Fix<<
Way 2.
Copy my ROM on your Internal SD Card
Install My ROM with Wipe/Factory Reset
Turn off your Phone and Flash The Stock [.108] Kernel
Reboot your Phone
enjoy
Locked Bootloader Root problems Flash >>Su Fix<<
Unlocked Bootloader
Copy my ROM on your Internal SD Card
Install My ROM with Wipe/Factory Reset
Flash Stock TFT Kernel >>Klick<< or choose Custom kernel in AROMA
Reboot your Phone
enjoy
⇩⇩⇩New Aroma Installer⇩⇩⇩
⇝CrisKelo ♚[AROMA]V3.0.8♚ DOWNLOAD LINK⇜
⇩⇩⇩Mega Cloud Mirror⇩⇩⇩
⇝CrisKelo ♚[AROMA]V3.0.8♚ DOWNLOAD LINK⇜
⇝Official Discussion-Thread⇜
⇩⇩⇩Old Versions⇩⇩⇩
⇝CrisKelo ♚[AROMA]V3.0.7♚ DOWNLOAD LINK⇜
⇝CrisKelo ♚[AROMA]V3.0.6♚ DOWNLOAD LINK⇜
⇝CrisKelo ♚[AROMA]V3.0.5♚ DOWNLOAD LINK⇜
⇝CrisKelo ♚[AROMA]V3.0.4♚ DOWNLOAD LINK⇜
⇝CrisKelo ♚[AROMA]V3.0.3♚ DOWNLOAD LINK⇜
⇝CrisKelo ♚[AROMA]V3.0.2♚ DOWNLOAD LINK⇜
⇝CrisKelo ♚[AROMA]V3.0.1♚ DOWNLOAD LINK⇜
⇝CrisKelo ♚[AROMA]V3.00♚ DOWNLOAD LINK⇜
⇝CrisKelo ♚Aroma2.7MR♚ DOWNLOAD LINK⇜
⇝CrisKelo ♚Aroma2.7S2♚ DOWNLOAD LINK⇜
Simplified Installation Instructions :
1) Download 2 zip installers, first kernel and second Aroma zips.
2) Flash Downloaded MultiBoot Kernel, Reboot in to MultiRom TWRP by tapping camera button after first vibration.
3) Run Aroma Installer WITH "INJECT MULTIROM AFTER INSTALLATION" FUNCTION ENABLED, AND CHOOSE TRINITY MULTIBOOT KERNEL INSIDE AROMA INSTALLER!
In the rest of options follow Aroma Installer wizard
4) Enjoy
⇝CrisKelo ♚V7.8.1♚ Rom DOWNLOAD LINK⇜
⇧⇧⇧All Modifications Aroma Installer!!!⇧⇧⇧
⇝CrisKelo Simplified MultiRom DOWNLOAD LINK⇜
Recovery Themes
All TWRP recovery themes and configurations will be applied automatically.
But you must apply the Philz recovery settings manually.
Go to Philz recovery settings, backup/restore settings, then choose restore theme and finally restore theme and settings.
Done, we have the best settings and recovery theme. The background will change acording with the kernel that you selected from AROMA INSTALLER
Some apps and xposed modules added.
All recoveries updated, including Nut dual recovery solution.
And that's all for locked bootloaders :?
Unlocked Bootloaders
MultiRom Installation Guide :
WARNING: Read and Follow my installation instructions! I'm not responsible for bad or inappropriate use of my works! You are installing it for your own risk. If you will correctly follow my instructions all will work good and you will don't need PC. Allways make nandroid backup, just incase.
Installation Procedure :
1)Download the latest AROMA INSTALLER and install it with full wipe, choosing the Trinity MultiBoot Kernel, without DATA RESRESTORE.
It will also install support for Rom and extract all necessary Files to /sdcard1/0-MultiRom folder .
2)Boot up the Android,connect to the internet and run multirom app.
Allow it root access , download and install all necessary files. When it finish, It Will Ask for reboot in recovery to complete installation, CHOOSE "NO".
IF YOU REBOOTED THAN REFLASH TRINITY MULTIBOOT KERNEL, from 0-MultiRom folder, DO NOT REBOOT WITHOUT REFLASHING KERNEL, OR IT WILL NOT BOOT !!!
In case IT NOT BOOT you must FASTBOOT FLASH BOOT BOOT.IMG with Windows command line, to bring your device life again.
3)Shutt down your device , than boot it in MultiRom TWRP Recovery by pressing camera button or rebooting in recovery with Philz recovery .
Go to /sdcard1/0-MultiRom folder and install :
Check the option "Inject MultiRom After Installation ", it must be ENABLED!
FLASH :
1)MultiROM-v30x-180115-UNOFFICIAL-honami.zip, do not REBOOT OR IT WILL NOT BOOT!
Check the option "Inject MultiRom After Installation ", it must be ENABLED!
Then you have two Kernel installers for flash :
2)LTrinityUltimateKernel_V3.2_by_D_Vovan_238.zip - by all buttons you will enter in Philz Recovery.
2)ULTrinityUltimateKernel_V3.2_by_D_Vovan_238.zip - you can enter MultiRom TWRP Recovery by camera button pressing.
4)And finally boot in to your New CrisKelo MultiRom V7.8!
5)Enjoy
For correct functionality of all secondary roms check MultiRom settings, Enable ADB must be enabled, otherwise you will always getting problems with your secondary Roms!
If some secondary Rom get stuck, sometimes it happens, will be impossible to boot nothing apart recoveries. Boot in to MultiRom TWRP and repeat step number 3) of my installation guide. Now MultiBoot is restored . Stucked secondary Rom will also not work, to restore it simply reflash Rom and optionally Gapps zip installers, DONE ALL RESTORED
You will also find init.d script zip installers in /sdcard1/0-MultiRom/MountingScripts folder.
There are 3 installers for mmcblk1p2, mmcblk1p3 and mmcblk1p4 mount. So you can use it for External Secondary Roms installation or like EXT4 storage
But first you must prtitionate your Micro SD Card with mini partition tool, than install script acording with your SDCard partitions.
You can even install external roms on USB OTG Disks, FAT32(vfat) formatted
You will also find MultiRom uninstaller zip in 0-MultiRom folder, if you want to remove it.
Remember ALWAYS REFLASH KERNEL After actions with MultiRom, like installing, reinstalling or uninstalling MultiRom !!!
This way you ensure that it will 100% boot up other time!
No need to Reflash Kernel after secondary rom installing
⇝CrisKelo MultiRom DOWNLOAD LINK⇜
︻╦̴╦═━───━━━✺~CRISKELO ROM~✺━━━───━═╦̴╦︻
First unofficial update for CrisKelo rom available for download.
Installer version 2.3.7 will update your ROM to unofficial 7.6.3a version.
My first AROMA INSTALLER V 2.4.7 Done
It will update your ROM to unofficial CrisKelo 7.6.7a version.
It's edited CrisKelo AROMA INSTALLER (I will spend very much time to make new like CrisKelo's)
LOCKED AND UNLOCKED BOOTLOADERS
INSTALLATION GUIDE :
1)Make NANDROID BACKUP of whole system (just incase), and later we will need data backup!
2)Reboot your phone to recovery.
3)Install the update choosing first option, with wiping all system. If you choose second option, customize your rom, NO ROM UPDATE, NO ANDROID PATCHES AND NO MODDED PLAYSTORE WILL BE INSTALLED.
4)Reboot in to recovery, and select costume restore and RESTORE ONLY DATA! IF YOU WILL RESTORE SYSTEM ALL CHANGES WILL BE ELIMINATED!!!
5)Finally boot in to android.
6)ENJOY FREEDOM
⇝OLD DOWNLOAD LINK⇜
♔CHANGELOG♚
AROMA v2.4.7 Unofficial CriskeloROM v7.6.7a
By D_Vovan_238
⇝ Aroma Installer Added
+ All Kernels Updated
+ Android Patches Added
+ Modded Playstore Added
+⇩ All Kernel Recoveries Updated⇩
⇝Ported from newest NUT Kernel⇜
+ Nut DualRecovery Solution Updated
+ Gps Configuration Added
+ Framework Animations Updated
+ SystemUI Icons Added
+ AOSP Stock Lockscreen added
+ DroidLogo Fonts Added
Click to expand...
Click to collapse
If you like my work please hit the thanks button

XDA:DevDB Information
CrisKelo MultiRom V7.8.1 LB&UB, ROM for the Sony Xperia Z1
Contributors
D_Vovan_238, f(x)THaxxorX, amarullz, Garcia98, Philz, TWRP Team, CWM Team, DoomLord, [NUT], rovo89, ChelpuS.
Source Code: criskelo.de.vu
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Xperia Z 1: C6903 or C6902.
Based On: Sony Stock Rom
Version Information
Status: Stable
Current Stable Version: [AROMA]3.0.8
Stable Release Date: 2015-06-14
Current Beta Version: AROMA 2.7S
Beta Release Date: 2015-02-06
Created 2015-04-09
Last Updated 2017-04-14

Reserved

RESERVED
RESERVED

RESERVED2
RESERVED

Seems nice but wow it's a tad bit confusing

I know but try it, I'm sure you will like it

D_Vovan_238 said:
I know but try it, I'm sure you will like it
Click to expand...
Click to collapse
Hi mate good to see you here !

Hi glad to see you to
Now started new thread wright here

noahvt said:
Seems nice but wow it's a tad bit confusing
Click to expand...
Click to collapse
My Aroma Installer also use this method for Kernel splash image change

noahvt said:
Seems nice but wow it's a tad bit confusing
Click to expand...
Click to collapse
Please use less colors at instructions..
Sent by my Z1 with XDA Fax

Duvel999 said:
Please use less colors at instructions..
Sent by my Z1 with XDA Fax
Click to expand...
Click to collapse
Ok

D_Vovan_238 said:
Ok
Click to expand...
Click to collapse
I received an error during installation: cannot stat /system/build.prop no such file or directory

noahvt said:
I received an error during installation: cannot stat /system/build.prop no such file or directory
Click to expand...
Click to collapse
You wiped your system before run Aroma Installer.
That's because it happens, wipe your phone with Aroma, while old rom is on system,it will not wipe data/media/0!
I was not thinking about this
But otherwise my device verification will not work.
Like all good Roms CrisKelo must verify if it is installing on correct device, because if the device is incorrect, it will possibly bricked or worse, Hard Bricked
Try it this way if still don't work, save the Installation Log and send it to me, or post it

Aroma installer updated !
New version released
Enjoy

From criskelo.de.vu
From criskelo.de.vu
D_Vovan_238 said:
Now it's not Simplified Multirom Aroma Installer it's just Multirom Aroma Installer
To have Multiple Roms now simply flash my newest [Aroma2.7MR], with Trinity Ultimate MultiBoot Kernel, IN TWRP OR PHILZ RECOVERY, and enjoy all Multirom Features
Pretty soon will post newest Aroma Installer
Some bootanimations added also.
Click to expand...
Click to collapse
D_Vovan_238 said:
All tested and seems to work perfectly with ALL RECOVERIES.
And because now wee don't need to inject multirom after installation I reenabled Reboot Now Option after installation
Click to expand...
Click to collapse

Was uploading my work whole night, but got error
Now will go to work, but later will try other time

Take your time
Sent by my Z1 with XDA Fax

Im not beeing able to download the rom. i get "enter decryption key" on that site...
also i seem to have lost the recovery thing. pressing back button on restart does nothing any more. what is recommended to use here?
EDIT: i manage to install towel using dualrecovery...
But still missing the stable realease as i cant download i only got the full multipackage thing. dont know whats the difference here...
EDIT2: after chosing a bunch of stuff when installing rom and now restarting the phone is stuck with "SONY". what to do?
EDIT3: I manage to get it working again. flashtool etc. and finally i got the rom up running. So far so good.
But 1 quetion change i change the font on text? i find it a bit to fanzy and hard to read.

U5tabil said:
Im not beeing able to download the rom. i get "enter decryption key" on that site...
also i seem to have lost the recovery thing. pressing back button on restart does nothing any more. what is recommended to use here?
EDIT: i manage to install towel using dualrecovery...
But still missing the stable realease as i cant download i only got the full multipackage thing. dont know whats the difference here...
EDIT2: after chosing a bunch of stuff when installing rom and now restarting the phone is stuck with "SONY". what to do?
EDIT3: I manage to get it working again. flashtool etc. and finally i got the rom up running. So far so good.
But 1 quetion change i change the font on text? i find it a bit to fanzy and hard to read.
Click to expand...
Click to collapse
Sorry, was buissy, will fix it on next versions
For now only solution is wipe
Now preparing to new release, all details on criskelo.de.vu
Detected some unstable scenario, possibly 25% that it will happens, but it is almost fixed
That's why still not uploading new version

But is it possible to change font? Cause its hard for an old guy like me to read it

[MOD][07-08-2015][XMS] MultiRom v31x for Xperia M

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

Develop Bugs

welcome