Develop Bugs

[KERNEL] 26/Jan r3: MoDaCo Custom Kernel for the Samsung Galaxy Tab

{
"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"
}
If you've been following my Twitter feed, you will have noticed i've finally started playing with (and enjoying) my Tab.
I've been playing with ROM updates, ClockworkMod recovery and other bits and bobs, and here is the first fruit of my labour - MoDaCo Custom Kernel r1 for the Samsung Galaxy Tab.
What? Why?
Koush has posted his EXT4 converting ClockworkMod release / kernel at XDA-Developers, however unfortunately it breaks a fair few things on the latest ROMs for international Tabs - keyboard backlights, rotation, camera and a few other bits. So, I set about compiling up my own kernel using Samsung's source, with the aim of including all of Koush's great additions plus the usual TUN and CIFS modules, as well as including things like IKCONFIG to make kernel development easy for others (particularly as I plan to upload the whole lot to github). As well as releasing for EXT4 / ClockworkMod, i've packaged it for standard RFS ROMs. The kernel / ramdisk is 'insecure' (for adb remount etc.).
This turned out to be somewhat traumatic due to the 'update1' Samsung source refusing to work on my device, but I got there in the end. So this is a prelude to the MoDaCo Custom ROM... my MoDaCo Custom Kernel.
Requirements
This kernel has been tested on a number of Tabs running a number of different ROMs with no issues. It comes in two versions - a simple 'RFS' version to use with a regular ROM, or the 'EXT4 ClockworkMod' version if you already have (or wish to) convert to EXT4.
In order to use either kernel you need to be familiar with flashing via Odin or Heimdall, although you could in theory extract the TAR file and flash using 'flash_image' I guess.
If you plan to do the EXT4 conversion, you MUST have a microSD inserted with enough space to do a backup of your system / data partitions (so this will depend on how much data is on your device).
YOU SHOULD BACKUP BEFORE INSTALLATION OR BE FAMILIAR USING ODIN / HEIMDALL FOR FULL SYSTEM RECOVERY IN CASE OF A SERIOUS ISSUE. YOU USE THESE DOWNLOADS AT YOUR OWN RISK!
This kernel is ONLY tested on a UK Galaxy Tab. It MAY work on other GSM Tabs, it almost certainly WON'T work on a CDMA Tab. If you have a non UK Tab and want to test (and know how to flash back to a regular version), then go ahead and report your results. At your own risk.
How to
RFS version
To use the RFS version (i.e. you have not converted to EXT4 yet and don't wish to)...
Download the RFS TAR file from below
Flash using ODIN (version 1.7, do not select the 'repartition' option)
Reboot, you're done!
Optionally download the kernel modules zip (for TUN/CIFS) and copy to a location of your choice
Simple huh?
EXT4 version
To use the EXT4 version (i.e. you are already running EXT4 or you wish to convert)...
Download the EXT4 TAR file from below
Flash using ODIN (version 1.7, do not select the 'repartition' option)
IF YOU NEED TO UPGRADE TO EXT4: Your device won't reboot normally - that's OK, just turn it off (hold down power button for 5 seconds)
IF YOU NEED TO UPGRADE TO EXT4: Load recovery - turn the device on with 'volume up' held
IF YOU NEED TO UPGRADE TO EXT4: Your device will now perform the EXT4 conversion - depending on the volume of your data, this can take a while, so be patient
Reboot, you're done!
Optionally download the kernel modules zip (for TUN/CIFS) and copy to a location of your choice
Downloads
DOWNLOAD
And finally
I hope this is usual for everyone - i've found this is a real performance boost (particularly with the newest ROMs) and I look forward to rolling MCR out for the Tab! I'll have the kernel in GitHub soon, after which i'll post the URL here.
Enjoy!
P

Changelog
r3 26/Jan
Additional governor / scheduler options
Battery icon fix for when device is powered off
Other minor tweaks
r2 24/Jan
Set default governor to 'on demand'
Added Fuse module (by request)
MCK version now shown in about
Updated compiler
EXT4 performance tweaks
r1 23/Jan
Initial release

Looks good!
Great too see you here!

Looking forward to the first MCR!
Does the RFS version include CWM?

On what versions will this work?
Thanks for the effort you put into this. Can you please tell on what version the base Tab must be, to make this kernel work? And also, if it will work with the protected bootloaders?
Thanks again!

Testing it now on Roger/AT&T GSM Tab i987.
It is backing up and converting to ext4 right now.

It would be helpful if you put GSM in the title, or Euro for that matter, if that's the case.

Cheers Paul,
Will give the EXT4 a whirl once I work out the pros/cons

Confirmed that it works for NA GSM Tabs. Converted everything over to ext4 and working.
No real increase in speed really. Quadrant scores are about the same...around 1000.
Gallery has some glitches were it does not show pictures the first time...have to exit and come back in.

Let's give it a shoot
Sent from my GT-P1000 using Tapatalk

rmanaudio said:
Confirmed that it works for NA GSM Tabs. Converted everything over to ext4 and working.
No real increase in speed really. Quadrant scores are about the same...around 1000.
Gallery has some glitches were it does not show pictures the first time...have to exit and come back in.
Click to expand...
Click to collapse
I get this on all my Android devices now and again if a media index is running (generally soon after a boot)...
P

paulobrien said:
I get this on all my Android devices now and again if a media index is running (generally soon after a boot)...
P
Click to expand...
Click to collapse
Really weird problem where browser (with google.com as homepage) starts to rotate itself once you open browser till it is upside down!

If you have any issues, please post your ROM version and whether you are on the latest release.
I am on XXJMF and don't experience the issues mentioned above.
P

Great work man thank you!!! Only 1 ( noob i think question ) : what exactly do the additionals zip TUN/CIFS?

Frustu said:
Great work man thank you!!! Only 1 ( noob i think question ) : what exactly do the additionals zip TUN/CIFS?
Click to expand...
Click to collapse
If you don't know what they are, you don't need them

Screenshot from r2 (coming tomorrow).
P

TheGrammarFreak said:
If you don't know what they are, you don't need them
Click to expand...
Click to collapse
Ah ok thank you ... But i m curious please tell me

Im on Roto JME v4...and only problem found is Web browser rotates itself 180 degrees when you start it up.

Frustu said:
Ah ok thank you ... But i m curious please tell me
Click to expand...
Click to collapse
http://lmgtfy.com/?q=What+is+CIFS
http://lmgtfy.com/?q=What+is+TUN

TheGrammarFreak said:
http://lmgtfy.com/?q=What+is+CIFS
http://lmgtfy.com/?q=What+is+TUN
Click to expand...
Click to collapse
Well i learn 2 new things thank you

[APP/KERNEL] Dual Boot Ancora

{
"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"
}
Hello everyone!
Together with @h0rn3t we bring you Dual Boot Support for the Samsung Galaxy Wonder (Ancora)
Let's get started
Requirements:
Root
Busybox
CM or other AOSP like ROM based on 4.0+
Minimum ~350MB internal storage free space
External SD (min 4GB, the higher class, the better)
Description:
The process is fairly simple. The application will format your external-sd (we recommend to back up your personal data), then create 3 partitions as follows:
/dev/block/mmcblk1p1 -> storage (formatted VFAT)
/dev/block/mmcblk1p2 -> /system (formatted EXT4)
/dev/block/mmcblk1p3 -> /data (formatted EXT4)
After that you'll be given the possibility to flash a secondary ROM on your EXT-SD (currently only 4.1.2+ ROM's are supported as secondary and 4.0+ as primary).
At last, you'll be able to switch between ROM's within the app.
Process:
WARNING: Partitioning and flashing operations could take up to 5 minutes to complete, please be patient !
Download the app and kernel pack from the Downloads section
If you want the app to be automatically installed on the secondary ROM, push the app to /system/app and give proper permissions (rw-r-r or 644). Otherwise, just install it normally.
Backup your personal data from the external sd card.
Run the app and partition your external-sd.
In app, choose flashing then choose your preferred secondary ROM from your internal SD card (must be 4.1.2 or higher).
Your phone will reboot into recovery and automatically flash the secondary ROM. (in CWM, if you get "Signature Verification Failed", continue flashing, it is normal)
After the flashing process is done, you'll be redirected to your primary ROM.
On your internal SD-Card, you'll have a folder called DualBootSplus, open it up.
Copy the kernels from the kernels pack into their appropriate subfolder. (eg CM-10 kernel (boot2.img) goes into 4.1.2 subfolder -> you'll have to create the subfolder if it doesn't exit)
Now you can switch between ROM's or flash secondary gapps within the app.
Additional details:
You must put only 1 boot2.img in each DualBootSplus subfolders.
The kernel will determinate which ROM will be booted. So, if you have a primary and secondary ROM, you can quickly switch between them within the app (make sure you have the kernels in the SD-Card subfolders), or manually by flashing the correspondent kernel.
The boot2.img can be flashed separately in ADB.
Special thanks goes to @arsradu for his kernels and @Madridii for testing.
XDA:DevDB Information
[GT-I8150] Dual Boot [ANCORA], Tool/Utility for the Samsung Galaxy W I8150
Contributors
educk, h0rn3t
Version Information
Status: Stable
Current Stable Version: 1.5.1
Stable Release Date: 2013-10-27
Created 2013-10-04
Last Updated 2014-05-20

For Kernel Developers
For Kernel Developers
How to make a kernel suitable for dual-booting (mounting ext-sd partition)
We know that a kernel (for Galaxy W, S Plus and many others) has 2 major components. The RAMDISK and the zImage.
The RAMDISK is responsible for mounting and other init processes so to successfully boot up a secondary ROM (from the external SD-Card) we need a kernel with a modified RAMDISK, so that it recognizes these external partitions.
As stated in the OP, the app partitions the ext-sd like this:
/dev/block/mmcblk1p1 -> storage (formatted VFAT)
/dev/block/mmcblk1p2 -> /system (formatted EXT4)
/dev/block/mmcblk1p3 -> /data (formatted EXT4)
So these are the exact instructions we should pass to the fstab. (this particular file from the RAMDISK is responsible for disk mounting).
I pasted here a modified fstab.qcom which should explain pretty much everything I did to make a proper dual boot kernel:
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
[B]/dev/block/mmcblk1p2[/B] /system ext4 ro,barrier=1 wait
/dev/block/mmcblk0p16 /cache ext4 nosuid,nodev,barrier=0 wait,check
[B]/dev/block/mmcblk1p3[/B] /data ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=1 wait,check,encryptable=footer
Please note that fstabs might vary with Android version.
Currently, only 3.0 kernels are able to mount ext-sd partitions, the 3.4 one has some bugs/differences in the emmc driver which were not fixed/adapted until now.
For decompiling the boot image there are several tools out there. My personal favorite is bootimgtools, there are several toolkits which use this little binary like dsixda's Android Kitchen.
Good luck!

educk said:
Hello everyone!
Together with @h0rn3t we bring you Dual Boot Support for the Samsung Galaxy Wonder (Ancora)
Let's get started
Requirements:
Root
Busybox
CM or other AOSP like ROM based on 4.0+
Minimum ~350MB internal storage free space
External SD (min 4GB, the higher class, the better)
Click to expand...
Click to collapse
awesome job:thumbup:
Sent from my GT-I8150

finally, thanks mr educk :good::good:
---------- Post added at 12:33 AM ---------- Previous post was at 12:24 AM ----------
hi mr educk, it's that ok if i swap the mmc to sd when dual boot ? sorry bad english

Good job mate... thanks :thumbup:

Awesome
Thanks sir educk:thumbup::thumbup:

I have to think about it because i already formatted and configured my ext-sd to be used as app swap with link2sd.
Thanks a lot nevertheless!

tycoo said:
I have to think about it because i already formatted and configured my ext-sd to be used as app swap with link2sd.
Thanks a lot nevertheless!
Click to expand...
Click to collapse
haha sure, i'm just test it, my second rom is swap mmc to sd and i forgot to change it, it's run very laggy on second rom

GOOD!!
thank you very much educk .
now we are able to use stock rom and cm together on the one phone :good::good::good::good:
you are awesome man thanx again

sir mordred said:
thank you very much educk .
now we are able to use stock rom and cm together on the one phone :good::good::good::good:
you are awesome man thanx again
Click to expand...
Click to collapse
i think no, the primary rom is 4.0.+ and secondary is 4.1.2+

sir mordred said:
thank youcan't use sy much educk .
now we are able to use stock rom and cm together on the one phone :good::good::good::good:
you are awesome man thanx again
Click to expand...
Click to collapse
First big thanks to Mr Erik..
No you cant use stock rom as primary read carefully ..
We hope it will support cm9 and 2.3.6

fsl7th said:
i think no, the primary rom is 4.0.+ and secondary is 4.1.2+
Click to expand...
Click to collapse
no first rom is cm10.1 second rom is stock
if there is a cwm flashable stock rom for galaxy w like that XXLB4.zip ı think we can do it

sir mordred said:
no first rom is cm10.1 second rom is stock
if there is a cwm flashable stock rom for galaxy w like that XXLB4.zip ı think we can do it
Click to expand...
Click to collapse
but the rule is that the second rom must be 4.1.2+, that's why mr educk append the cm 10 and cm 10.1 kernel on his post,
correct me if im wrong

fsl7th said:
but the rule is that the second rom must be 4.1.2+, that's why mr educk append the cm 10 and cm 10.1 kernel on his post,
correct me if im wrong
Click to expand...
Click to collapse
You are right.
As stated in the OP, the primary ROM can be any either ICS or JB (4.1.2 & 4.2.2).
The secondary can be only JB (4.1.2 & 4.2.2). Make sure you have the appropriate dual boot kernel (boot2.img) in the correspondent sub folder from /sdcard/DualBoot.
I'm working on ICS as secondary. After that, we'll see about GB.

educk said:
You are right.
As stated in the OP, the primary ROM can be any either ICS or JB (4.1.2 & 4.2.2).
The secondary can be only JB (4.1.2 & 4.2.2). Make sure you have the appropriate dual boot kernel (boot2.img) in the correspondent sub folder from /sdcard/DualBootAncora.
I'm working on ICS as secondary. After that, we'll see about GB.
Click to expand...
Click to collapse
Is cm 10.2 not possible ?

Guys, I made a mistake in the application. Please wait few minutes until I fixed... Sorry for inconvenient !
---------- Post added at 11:02 PM ---------- Previous post was at 10:53 PM ----------
OK. Problem solved. Please update your application. You must put boot2.img files in DualBoot folder. If you already have DualBootSplus folder rename it DualBoot.
The correct folder is /sdcard/DualBoot. You must have something like this /sdcard/DualBoot/4.2.2/boot2.img

Well, thanks guys! I've been waiting for you to do that for ancora.
Sent from my GT-I8150 using Tapatalk 4

This is really new for galaxy w, Amazing work educk.... :thumbup:
Sent from my LT29i using Tapatalk 4

does it support cm9 as secondary ?

Dwama said:
does it support cm9 as secondary ?
Click to expand...
Click to collapse
Not yet !

[MOD][Z3] MultiROM v33x

{
"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
I'm not responsible for anything, you do all this on your own risk.
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.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
Your device must not be encrypted.
To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
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
Make sure you are on a Rom compatible with one of these kernels and flash it
Reboot into MultiROM TWRP and flash the MultiROM installer
That's it. You can now go to "Advanced -> MultiROM" to start flashing other ROMs.
Adding 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 ROMs
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 master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/Myself5/android_kernel_sony_msm8974/ (M5-Kernel)​
FAQs can be found here.
CREDITs
Tasssadar
Olivier
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
AndroPlus
Panic Brothers
If you think I deserve a donation, I won't stop you
Thanks a lot to those who have donated!​
You might want to consider a Donation to Tasssadar, who is the Mastermind behind all of this, I just ported it to the Z3
​
XDA:DevDB Information
MultiROM for Sony Xperia Z3, Tool/Utility for the Sony Xperia Z3
Contributors
Myself5
Source Code: https://github.com/XperiaMultiROM/multirom/tree/master
Version Information
Status: Testing
Created 2015-01-23
Last Updated 2016-06-06

CHANGELOGs
General MultiROM Changelog can be found here:
Changelog
XperiaMultiROM Specific Changelog is here:
Recovery Changelog
MultiROM Changelog
DOWNLOAD
https://dl.myself5.de
The recovery.img is Tassadars modified TWRP to flash secondary Roms. It is needed to flash the secondary Roms.
SUPPORTED KERNELs
M5 Kernel
AndroPlus Kernel (starting with V19)
If you want your favorite kernel to support kexec tell the dev to merge my commits.

Reserved
General Informations about Kexec are coming here soon.

I will test it when i come home and report the result.
Edit: all is stable only Multirom menu needed to be fixed but that you have reported, thanks
Now i can use stock as daily driver and cm12 to see the progress. many thanks.

Whaaaaaaat. This is amazing! Thanks for your work, keep at it! I will surely use the multirom a bit later, when some more roms like PA are avaiable.

Wow great work! A noob question but one assumes that I would not be able to have one rom on 4.4.4 and another on Lollipop 5.0 due to the fact the base Kernel AndroPlus is designed for 4.4.4 or does Multi Rom allow 2 different Kernels? Thanks in Advance.
Sent from my D6603 using XDA Free mobile app

panzerscope said:
Wow great work! A noob question but one assumes that I would not be able to have one rom on 4.4.4 and another on Lollipop 5.0 due to the fact the base Kernel AndroPlus is designed for 4.4.4 or does Multi Rom allow 2 different Kernels? Thanks in Advance.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
It actually is possible. The Base Kernel is patched to be kexec-hardboot compatible. This means it is able to load other kernel to the RAM and run them from there. The host kernel is just a middleman loading the kernel to the RAM, it is not doing anything else which means it is not affecting the secondarys kernel at all.

I used to do this on Nexus 5, loading 4.4.4 with kexec kernel and then 5.0 preview as the other rom and it worked, so it should be possible here as well.

Myself5 said:
It actually is possible. The Base Kernel is patched to be kexec-hardboot compatible. This means it is able to load other kernel to the RAM and run them from there. The host kernel is just a middleman loading the kernel to the RAM, it is not doing anything else which means it is not affecting the secondarys kernel at all.
Click to expand...
Click to collapse
Oh wow thats fantastic news for sure. Lollipop here I come. I was hesitant before due to lollipop not being daily driver material but now it does not really matter. Do you get an option to select which rom upon phone boot up?
Thanks guys and great work
Sent from my D6603 using XDA Free mobile app

panzerscope said:
Oh wow thats fantastic news for sure. Lollipop here I come. I was hesitant before due to lollipop not being daily driver material but now it does not really matter. Do you get an option to select which rom upon phone boot up?
Thanks guys and great work
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
see the pic in the op ? Thats what is going to appear after the Sony scrren and before the initial Rom bootup.

Myself5 said:
see the pic in the op ? Thats what is going to appear after the Sony scrren and before the initial Rom bootup.
Click to expand...
Click to collapse
Woops I thought all that was is a logo but did not check, my bad and thanks!
Sent from my D6603 using XDA Free mobile app

Wow it's already here for the Z3, thanks guys, this is awesome!!

Sorry but my english is to bad to understand what to do... Can anyone create please a step by step tutorial i have the d6603 whith androplus kernel v 19a please help me

Just confirming, looking at your files I assume that the Leo folder is for the z3?
Sent from my D6603 using XDA Free mobile app

panzerscope said:
Just confirming, looking at your files I assume that the Leo folder is for the z3?
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
yup, leo is the Z3's codename. Sirius is Z2 and n801x is my Samsung Galaxy Note 10.1. Guess thats what happens when CM breaks the naming law and calling it just z3..

Myself5 said:
yup, leo is the Z3's codename. Sirius is Z2 and n801x is my Samsung Galaxy Note 10.1. Guess thats what happens when CM breaks the naming law and calling it just z3..
Click to expand...
Click to collapse
Yeah I knew it use to be Leo but after checking the CM website it was Z3 so I just wanted to confirm before fracking my phone lol. Thanks!
Sent from my D6603 using XDA Free mobile app
---------- Post added at 10:47 PM ---------- Previous post was at 10:04 PM ----------
So far so good, Modified Recovery and Multirom Installed. Now to flash CM12
Sent from my D6603 using XDA Free mobile app
---------- Post added at 11:28 PM ---------- Previous post was at 10:47 PM ----------
Reporting back after testing.
This is either my ignorance or a possible bug.
So I am ready to add a second ROM. These are the steps I take.
Select Add ROM
Select Internal Memory ( I did get another option called ''/dev/block/mmcblk1p1 (exfat) ....Should that have been used instead ? )
Select Next
Select ZIP File
Select The Rom To Flash (CM12)
The flashing Process starts but fails with the following message
E: Error executing updater binary in zip '/tmp/mr_update.zip'
Please see below for full Flashing Log.
Updating Partition Details.....Done
Full Selinux Support Is Present
Installing ROM cm12
Creating folders and images for type 1
Flashing Zip File cm12
Rom: cm12
Preparing zip file
Copying ZIP to /tmp
Changing mounts to ROM cm12
Current Boot Sector was used as base for fake boot.img !
Zip uses block updates
Creating system.img
Installing 'tmp/mr_update.zip.....
Checking for MD5 File
Skipping MD5 Check: No MD5 File Found
This Package Is For devices: D6602,D6603,D6633,D6643; This device is Leo
E: Error executing updater binary in zip '/tmp/mr_update.zip'
Failed To Install ZIP
Restoring Mounts
Updating Partition Details.....Done
Erasing Incomplete ROM
Click to expand...
Click to collapse
I hope this helps.

panzerscope said:
Yeah I knew it use to be Leo but after checking the CM website it was Z3 so I just wanted to confirm before fracking my phone lol. Thanks!
Sent from my D6603 using XDA Free mobile app
---------- Post added at 10:47 PM ---------- Previous post was at 10:04 PM ----------
So far so good, Modified Recovery and Multirom Installed. Now to flash CM12
Sent from my D6603 using XDA Free mobile app
---------- Post added at 11:28 PM ---------- Previous post was at 10:47 PM ----------
Reporting back after testing.
This is either my ignorance or a possible bug.
So I am ready to add a second ROM. These are the steps I take.
Select Add ROM
Select Internal Memory ( I did get another option called ''/dev/block/mmcblk1p1 (exfat) ....Should that have been used instead ? )
Select Next
Select ZIP File
Select The Rom To Flash (CM12)
The flashing Process starts but fails with the following message
E: Error executing updater binary in zip '/tmp/mr_update.zip'
Please see below for full Flashing Log.
I hope this helps.
Click to expand...
Click to collapse
see there we go with the Leo thingy again Seems like I need to edit the device tree to make the Phone in Recovery appear as some D**** device instead of Leo. Will do tomorrow and release a update. /dev/block/mmcblk1p1 is your physical SD Card (it is formatted as exFat which is what TWRP is displaying).

change updater-script to leo. this should help.

Yeah when I saw that in the log I figured it was incorrectly detecting the device. I look forward to the update. I also guess that's why the Multirom app does not work?
Sent from my D6603 using XDA Free mobile app

Possible use for the Z3 compact?

[Nexus 9][Wifi][ROM][CM13.0][6.0.1] Temasek UNOFFICIAL Builds [Almost Daily]

Temasek's UNOFFICIAL CM13.0 BUILDS
{
"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 will attempt to get builds out as soon as Temasek releases a new version, however due to commitments i may miss a release. I will not upload a ROM until i have flashed it myself. Please report any bugs or issues that you see; when applicable, Thank you.
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
...not ready yet
A WORKING version TWRP is required i use Official TWRP 2.8.7.2
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Ensure you’re on the latest vendor image from google - https://developers.google.com/android/nexus/images
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
probably something i havn't found as yet
@temasek
@apascual89 - Developer of nexus 9 temasek dark
@Chainfire
CM Team, CyanogenMod
@DrawnToLife
@zawata
@joshuabg
@craigacgomez
Source
Orignally forked from CyanogenMod
Kernel Source
Device Tree
Temasek Source
Rom Source
Changelogs
https://github.com/temasek/Changelogs/blob/cm-13.0/cm_hlte-Changelog.txt​

Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65562191&postcount=652
Basketbuild Download - Backup Download Location (OR for those not in Google Shares)
https://basketbuild.com/devs/Joshndroid/Temasek Roms/flounder
GApps - Lollipop 5.1 64 Bit GApps Package
http://opengapps.org/
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to Chainfire
http://download.chainfire.eu/supersu

and one more.

okay rom is now uploaded onto basketbuild. Please follow link in post 2.
i recommend clean flash from another rom as usual. If dirty flashing in the future there is no necessity to flash gapps again, however sometime i do notice supersu goes a bit funny so i would recommend reflashing supersu just to be safe. failing that you can just install it again from market and cause it to update via openrecovery script.

awesome !!! love this rom on my N6 . and now also on my N9 thanks !!!

Currently going through 2nd attempt at flashing. Used 64-bit GApps and linked SuperSU. Followed instructions for coming from another ROM. 20 minutes passed without a boot so I'll attempt again without flashing SuperSU until it (hopefully) boots up and I complete the setup screen.

nericollin said:
Currently going through 2nd attempt at flashing. Used 64-bit GApps and linked SuperSU. Followed instructions for coming from another ROM. 20 minutes passed without a boot so I'll attempt again without flashing SuperSU until it (hopefully) boots up and I complete the setup screen.
Click to expand...
Click to collapse
Let me know otherwise I will full wipe again and try again myself

Guessing it went well this time round might make a change to the op to not recommend SuperSU flash on clean flash

I know the change log is on the device once you flash the ROM. But I would like to know the changes that have been made besides what is in CM12 already.

Err... Far to many to list. Notification tweaks, button tweaks, stylus options, status bar options as well as others in temasek spare parts. That is a cm12 theme the standard colors would be regular cm in the attached screenahot

Does LTE work on this ROM?

Alright. Thanks man. I'll just flash it and play around
Edit:: Flashed it. Everything running great. One thing I have been looking for in several ROMs is the ability to put the nav bar on one side while in landscape. I kinda sucks having the bar at the bottom of my screen when it would be much more convenient right by one of my hands whole holding in it landscape. Is that possible here or in any rom yet.

joshndroid said:
Err... Far to many to list. Notification tweaks, button tweaks, stylus options, status bar options as well as others in temasek spare parts. That is a cm12 theme the standard colors would be regular cm in the attached screenahot
Click to expand...
Click to collapse
FINALLY!!! hahaha kidding great job
Fianlly pass your updater error? What fixed it?

joshndroid said:
Guessing it went well this time round might make a change to the op to not recommend SuperSU flash on clean flash
Click to expand...
Click to collapse
My apologies for the late response, I fell asleep earlier than normal.
It never ended up getting to the setup screen. I wonder if this has something to do with the format of the system partition.
---------- Post added at 08:02 PM ---------- Previous post was at 07:45 PM ----------
nericollin said:
My apologies for the late response, I fell asleep earlier than normal.
It never ended up getting to the setup screen. I wonder if this has something to do with the format of the system partition.
Click to expand...
Click to collapse
UPDATE: the file system was in fact the problem. Changed it to F2FS and it works now even flashed the SuperSU zip too.

zawata said:
FINALLY!!! hahaha kidding great job
Fianlly pass your updater error? What fixed it?
Click to expand...
Click to collapse
Reverted the bootable cm commit that was pointing to a register.inc for a 32 bit executable
. the one I highlighted to you about a week ago. Just tracking my own bootable for now.
nericollin said:
My apologies for the late response, I fell asleep earlier than normal.
It never ended up getting to the setup screen. I wonder if this has something to do with the format of the system partition.
---------- Post added at 08:02 PM ---------- Previous post was at 07:45 PM ----------
UPDATE: the file system was in fact the problem. Changed it to F2FS and it works now even flashed the SuperSU zip too.
Click to expand...
Click to collapse
Excellent that is good to hear. Were you originally partitioned to ext4 ?
Sent from my SM-N9005 using Tapatalk

joshndroid said:
Reverted the bootable cm commit that was pointing to a register.inc for a 32 bit executable
. the one I highlighted to you about a week ago. Just tracking my own bootable for now.
Excellent that is good to hear. Were you originally partitioned to ext4 ?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I was! I figured it must have been that because I remember changing it from F2FS to ext4 when development for the N9 was still in early stages.
The ROM runs amazingly now though! Awesome job! Will report feedback if any issues arise!

andreglud said:
Does LTE work on this ROM?
Click to expand...
Click to collapse
I see some apn data in there that is required for LTE service to work yet I don't see a specific commit for it as Zawata did for his device tree.

joshndroid said:
I see some apn data in there that is required for LTE service to work yet I don't see a specific commit for it as Zawata did for his device tree.
Click to expand...
Click to collapse
So in short, I shouldn't expect it yet?

Not necessarily. I don't have a LTE device to try it on, so I can't just flash it and let u know.

disregaurd, didnt realize there were more replys

[GUIDE] Dualboot Custom ROMs on L5 and L7

{
"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"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have managed to support L3II, L5, L7 and L7II (Officially)
I am not the creator, just the supporter
XDA NEWS!!!
Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements
1. A Custom Recovery (TWRP or PhilZ Touch or the old CWM )
2. A KitKat ROM (Real KitKat ROM, not build.prop edited, a fake KK ROM)
3. The Dualboot Patcher - http://goo.gl/0bcbbN (Download the APK in Downloads Section)(For L3II, L5, L7 and L7II)
4. A KitKat ROM (To install )
Installation
1. Make a nandroid backup in case anything fails. (optional if you like playing with fire)
2. Install the DualbootPatcher
3. In the Patcher, go to the ROMs section, and a popup will ask you to set the kernel. Do it.
4. After this you need to go in menu (the tree dots) of Primary ROM and search for Update Ramdisk. Press it.
5. In the patcher, go to the Patch ZIP file section, open your ROM zip file
6. After this select in what partition you want to install:
Primary ROM Upgrade - To update ROM without affect the Secundary ROM (and others) when you have one installed.
Secundary - To install in /system.
MultiROM (1-3) - To install in /cache, you have 3 slots in this.
Data Slot - To install in /data (ID is IDentification of ROM)
Extsd slot - To install in your sdcard
7. You not need to change the Device
8. Do the same for GAPPS (optional)
9. Press in confirmation button and wait.
You have two options here:
9. Go to ROMs section and press in button of a device with arrow inside, select the patched zip files (ROM and GAPPS), and by last press in confirmation button, just wait..
10. After finish, close the app (see Know Issues), open and go again to ROMs section and you will see the default ROM to boot (the last installed). Reboot your phone.
11. It will now boot onto your ROM installed, once you've completed your first boot setup, install the DualBootPatcher.
or
9. Restart in recovery, flash the patched zip files (ROM and GAPPS). Restart your phone.
10. It will now boot onto your ROM installed, once you've completed your first boot setup, install the DualBootPatcher.
You are now able to select which rom to boot from the ROMs section. Once you've selected which rom is the default, restart your phone. Voilà!
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Never use this in JellyBean 4.1 or "You are gonna have a bad time"
- Contact me
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
@virulentt for him original thread for tutorial (and encouragement)
@Jonas Cardoso for testing in L5
@WinterR for testing in L7
@ECr34T1v3 for testing in L3II
ScreeShots
​

Thanks for the mention

@WinterR test the unofficial snapshot, please

What about different kernel and not the one from rom's zip? Better to add them to zip before patch or can be installed later by patching kernel's zip?
Or there can be only one kernel for all roms?
Sent using XT1562 - stock 5.1.1

ch3mn3y said:
What about different kernel and not the one from rom's zip? Better to add them to zip before patch or can be installed later by patching kernel's zip?
Or there can be only one kernel for all roms?
Sent using XT1562 - stock 5.1.1
Click to expand...
Click to collapse
For kernels you need to flash two times, first flash with patched zip (in app) and second flash you need to set the ROM and flash again (via recovery).
The first will update modules (/system) and second is to update the boot.img
Note: Ever you change kernel you need to go to app and set the kernel to save you new boot.img

Now DualBootPatcher supports the L7 and L7II!!!

I got some time and would like to check it out.
I can only use 4.4.4 roms (on L7 there are no newer ones)?
How it works with sdext? Is it used as both /system and /data? Or just /system? But than where is nonprimary rom /data located?
PS. What file systems are supported by app? Or maybe it depends on kernel?

@ch3mn3y you can use all ROMs up to 4.2, because SELinux and other core things like storage/emulated/0.
The SdExt only store system.img, and only system (for now, the patch is under progress all time).
You have option to put 1 in /system (dual), 3 in /cache (multi-slot), and unlimited in /data and /sdext (External Card).
Support F2FS and Ext4, auto-detect, just need support in your ROM and all will works (not tested because no F2FS support for mine device )

If I can ask: where /data goes? I mean /data/app, /data/data, etc., not /data/media)?

So I tried to mod cyanhacker 2.0 to work from extsd, but app FC's at 1.4%. Tried last 8.0.0. Anyone know which one works with our device or this rom (don't know which one cause FC)?

ch3mn3y said:
So I tried to mod cyanhacker 2.0 to work from extsd, but app FC's at 1.4%. Tried last 8.0.0. Anyone know which one works with our device or this rom (don't know which one cause FC)?
Click to expand...
Click to collapse
The rom is stored in any partition in a folder called "multiboot", try other rom or old app versions.
Enviado de meu E435 (L3 II Dual) usando Tapatalk

I used this: DualBootPatcher-8.0.0.r2115.g279e1b2-win32.zip (last build from 09.01.2016). It patched the file (older ones couldn't open the archive). Now i will try to flash it on my device and than i will probably use app from the same build (DualBootPatcherAndroid-8.0.0.r2102.gd35e5db-snapshot.apk).

Naah, i use newest app. Zips can be edited on Windows machine.
Small request: any chance to move /cache and /data to the same folder as /system? Or at least /data (as /cache is more temporary) as it can become big for one rom and we have less than 3GB of space on this partition...
Sent using XT1562 - stock 6.0 (retasia DualSim)
---------- Post added at 02:03 PM ---------- Previous post was at 01:55 PM ----------
Bug?
After reboot from extsd rom back to primary, app on ptimary doesnt find sdext rom. I can only choose primary one.
Only change on sdext rom I did is installation of app...
Sent using P700 - Mahdi-Rom/SKernel

Check in external card the multiboot folder.
This app have a lot of bugs, use the zip in DualBootPatcher site, for cat the logs, and we can see if something goes wrong and report a bug.
Enviado de meu E435 (L3 II Dual) usando Tapatalk

Its ok. After 2 reboots of primary rom, sdext one is back and after next two reboots between roms its still there. Dont know what was wrong, but right now i suppose there wont be any useful info in logs.
Downloaded the logs zip, so next time will use it.
It works really fast from class 4 sdcard. However I thought that extsd is 2 partition and created one
Sent using P700 - Mahdi-Rom/SKernel

Thread closed as per OP request.
-XDA Staff