TF700t-AKBI v2.6.8
I no longer own this device but will continue development. That said, all testing must be done by others. Thank you.
Android Kexecboot Installer script (TF700t-AKBI) is a prompted script run from inside an Android terminal.
The installer script source is here on github
(Please note: This thread is now only for the TF700t-AKBI installer. I have moved all the old dualboot stuff to the old dev thread here)
You must have a fully stable running install of:
CROMi-X 5.4, ZOMBi-POP or KatKiss (For CROMBi-KK, ZOMBi-X use v2.6.6)
(running from the internal sd ONLY, no f2fs, data2sd or rom2sd)
AND
either TWRP_that-2.6.4 or TWRP 2.7+
See these threads for help installing any of the following:
CROMi-x 5.4 ROM Thread
CROMBi-KK ROM Thread
ZOMBi-X ROM Thread
ZOMBi-POP ROM Thread
KatKiss ROM Thread
_that v10 Kernel Thread(for CROMi-X)
(If you are on stock rooted only, see rabits old thread as this is your only option, here).
PLEASE READ THIS:
Not for novices... You won't find every detail here... This is kept "simple" with assumption you have at least basic Linux and Android terminal knowledge. Read through both this thread and the closed dev thread here for more info. See cogano's excellent tutorial, here, it will help with some of the details I leave out....
Again you should understand what ALL this means before starting this endeavour.
YOU MAY BRICK YOUR DEVICE... The choice to continue is your own responsibility!
The short story:
What happens here is by flashing the kexecboot kernel blob (to mmcblk0p4) you are given a menu to choose a rootfs to boot from, ie Android, Linux image file, Linux on a partition... So in order for the kexecboot kernel to be of any use to you, you need to install Android and Linux kernels in your rootfs. It then reboots using the kernel you chose. The config file, boot.cfg, is installed to a small 5MB vfat partition (mmcblk0p5)
ANDROID: Android mounts root (mmcblk0p1) "/" as /system. So we install a kernel (without modules, you did that when you installed your ROM) to a directory we make called /boot which needs to be in the mount /system directory. This kernel (zImage and initrc.img) is just extracted from _that's cm112 or _that9oc+ kernel blobs and a copied to the /boot directory.
LINUX: This kernel was especially compiled by JoinTheRealms from _that5 source using configs moreD_cn came up with. It needs to be installed in /boot of a Linux rootfs.
Installing the installer: :silly:
If you are using KitKat (CROMBi-KK or ZOMBi-X), the rootfs installer will only make a 3GB image file. If you need a bigger image you will need to use one of the Aroma recovery based installers. Sorry
1- Download:
Zombi-POP or KatKiss
TF700t-AKBI-v2.6.8.zip
md5 458174c4438b279e1062d634c3c719c1
(For Crombi-KK and Zombi-X only use
TF700t-AKBI-v2.6.6.zip )
2- Extract to /sdcard or your favorite place
3- Place **ONE** "rootfs.tar.lzma" file in the extracted directory, see example files below
4- Open terminal and get root - su
5- cd to the directory you extracted the installer to
6- Run the script - sh TF700t-AKBI.sh (For a first time install select menu item 1)
7- Follow the prompts
Profit!
TF700t-AKBI Change log:
v2.6.8 - 09/05/15
-- Added KatKiss ROM support
v2.6.7 - 04/29/15
-- Removed old kernels
-- Updated for Zombi-pop Beta 6
v2.6.6 - 02/16/2015
--Added Zombi-POP Support
v2.6.5 - 11/21/2014
--Added that11 CROMBi-KK
v2.6.4 - 08/26/2014
--Updated rootfs and first time install to include ZOMBi-X kernels (forgot)
v2.6.3 - 08/26/2014
--Removed ZOMBi-X Stock Omni kernel
--Added ZOMBi-X Stock cm11
v2.6.2 - 08/25/2014
--Added Zombi-X kernels
v2.6.0 - Final - 08/08/2014
--Added all in one first time install script
--More error checking
--Final version
v2.5.9 - 08/05/2014
--Added back support for CROMBi-KK
--More error checking
v2.5.8 - 07/31/2014
--More error checking and better error exiting
--Check for valid rootfs image name and add extension if needed
--Added restore boot.cfg to bootcfg installer
v2.5.7 - 07/30/2014
--Fixed kernel installer error checking
v2.5.6 - 07/28/2014
--Added ability to install/add current entry to boot.cfg in rootfs installer
v2.5.5 - 07/19/2014
--Updated CROMBi-KK Kernels
--Only including latest kernel blob images, should work for all versions
--Changed folder structure
v2.5.4 - 07/14/2014
--Added stockcm11 kernel
--Added stock CROMi-X (JB) kernel
--Fixed more typo's (as usual)
v2.5.3 - 07/13/2014
--Add hardslog's CROMBi-KK cm11 kernel
v2.5.2 - 07/5/2014
--More typos
--Error checking for rootfs image size - it now won't try to make an image larger than your SD
v2.5.1 - 07/3/2014
--Added that10cm11 kernel for CROMBi-KK 6/17 release
--Changed main script name and links to it
v2.5 - 06/30/2014
--Scripts and project names changed
--Other small error checking fixes
v2.0 - 06/13/2014
--Added rootfs installer
--Fixed more error checking issues
--Simpler boot.cfg
v1.5 - 06/07/2014
--Added menu
--Fixed some issues in boot.cfg modifier script
v1.0 - 05/26/2014
--First release
Click to expand...
Click to collapse
Running the installer for the first time:
1) Copy a "rootfs.tar.lzma" file (see examples below) to the directory you extracted the
installer to (ex. - /sdcard/TF700t-AKBI-v2.X.X/ ). There can only be ONE "rootfs.tar.lzma" file in the install directory at one time.
2) Using an Android terminal (suggest Android Terminal Emulator from the Playstore)
cd into the installer directory (ex. - cd /sdcard/TF700t-AKBI-v2.X.X/ ) and become superuser (su)
3) Run the script - (sh TF700t-AKBI.sh)
4) Choose menu item 1 reading carefully and follow prompts
5) Reboot and profit
After you reboot it will bring you directly to the kexecboot menu which will have 2 choices:
Android and your new rootfs. The kexecboot menu will time out after 10 seconds and boot to
the highest priority OS (default is Android). To choose an OS to boot, use either the volume
keys or dock arrow keys and select with the power button or dock enter key.
Using after install - Advanced users:
Installer menu item 4 allows you to install a boot.cfg from the installer directory. This can be any file named boot.cfg or boot.cfg.old (your backup file)
Installer menu item 5 gives the opportunity to manually edit boot.cfg using a text editor (installer pauses while you switch to a text editor)
Aroma recovery based installers for KitKat (CROMBi-KK or ZOMBi-X) users wanting rootfs image files over 3GB or to install anywhere other than /data/media/linux
lubuntu-rootfs-installer-v.1.1.zip
ubuntu-rootfs-installer-v.1.1.zip
Question - " When I try to login, it kicks back to login screen"
Answer - Reinstall without make /dev/mmcblk0p8 as home
See the README.md for additional details.
Rootfs.lzma archive example files:
AndroidFileHost doesn't allow lzma files so ...
DOWNLOADS ARE ZIP FILES. YOU NEED TO EXTRACT THE LZMA
-- rabits' Ubuntu 12.10 (with that10 Linux kernel by conago added) - 720mb (2.9GB installed)
rootfs-ubuntu-12.10-that10-kexec.zip
md5 6ce2c4ad4366e44b56cd45a1b25cdcf3
-- workdowg's lubuntu 12.10 (with that10 Linux kernel by conago added) - 727mb (2.2GB installed)
rootfs-lubuntu-tf700t-05182014-that10-kexec.zip
md5 b223883da002274b0190550fcddbe5b1("New" cleaned up version)
Your Best Bet! --Ananasnonym's Lubuntu 12.04 LTS v1.3 (with that10 Linux kernel by conago6 added) - 351mb (1.5GB installed). (Directory structure fixed by workdowg)
rootfs-minimal-Lubuntu-12.04-v1.3.dirfixed.zip
md5 947b6dc24b4bdfdc67223ffd2194f570
Credits:
rabits
sbdags
JoinTheRealms
moreD_cn
_that
lj50036
cogano
Ananasnonym
jcfunk
and many more
I am happy to continue my enthusiasm here in this thread! I look forward to the possibility of having a dependable dual boot of up to date Android and Linux before long.
Oh, and the obligatory, "FIRST!"
Happy to see someone has picked up the project again!
Excellent!! Really looking forward to getting Linux working along side CROMi-X - although it may kill CROMi-X development for a while
It'll be for the best, sbdags, glad to have you on board!
yoda-sama said:
It'll be for the best, sbdags, glad to have you on board!
Click to expand...
Click to collapse
It could also aid it as I'll be able to dev whilst at work on my tab
Im just gonna leave this here: http://forum.xda-developers.com/showthread.php?t=2347581
Could we do this with a dualboot? huge increase in write speeds
JoinTheRealms said:
Im just gonna leave this here: http://forum.xda-developers.com/showthread.php?t=2347581
Could we do this with a dualboot? huge increase in write speeds
Click to expand...
Click to collapse
Sounds like it could definitely be adapted for our tablet. I'll look into it this weekend.
Sent from my ASUS Transformer Pad TF700t - CROMi-X 4.7.0 ODEX
Well I took a shoot today at building moreD_cn patch against _that's source/patches, to try to get a stable kernel. I have build custom kernels before for my pc but with this I failed miserably (I said I was not a kernel guy...). I can't get it to build. I got the source from Asus, the patches from _that4 and moreD_cn. Patching went fine, but when I tried to build it, it kept trying to build a x86 kernel and keeps asking a million questions I have no idea how to answer. I officially give up on kernel building. Someone who has the knowledge will have to step up....
workdowg said:
Well I took a shoot today at building moreD_cn patch against _that's source/patches, to try to get a stable kernel. I have build custom kernels before for my pc but with this I failed miserably (I said I was not a kernel guy...). I can't get it to build. I got the source from Asus, the patches from _that4 and moreD_cn. Patching went fine, but when I tried to build it, it kept trying to build a x86 kernel and keeps asking a million questions I have no idea how to answer. I officially give up on kernel building. Someone who has the knowledge will have to step up....
Click to expand...
Click to collapse
Ah its defaulting to the x86 compiler, spent hours edit: days! trying to get my machine to cross compile, the thing that fixed it for me was updating all compiler packages, i just went around all the different tutorials and installed all the packages they recommended and it suddenly worked lol.
Uploaded correct installer. I have been playing with so much I had a test one uploaded. Installs and runs fine now.
workdowg said:
Uploaded correct installer. I have been playing with so much I had a test one uploaded. Installs and runs fine now.
Click to expand...
Click to collapse
Thanks workdowg working fine now on my tf700! just a note to other users, when the installer hits 90% it stays there for a long time (about half an hour) but it will complete successfully.
Also the initramfs(not sure if thats its name...) is picking up directories stored in /data/media/linux and trying to boot them, for example i had /data/media/linux/linux and it was trying to boot /linux , so just make sure you dont have any folders inside of /data/media/linux
workdowg said:
Uploaded correct installer. I have been playing with so much I had a test one uploaded. Installs and runs fine now.
Click to expand...
Click to collapse
Nice! Is there any way to make it work with Cyanogenmod or would it require a different kernel?
Right first weird issue with ubuntu on 4.2. It seems the dns_resolver is requiring su permissions to run hence chromium, host, ping etc aren't working right , and need to be ran with sudo. Not quite sure how to fix this one...
JoinTheRealms said:
Thanks workdowg working fine now on my tf700! just a note to other users, when the installer hits 90% it stays there for a long time (about half an hour) but it will complete successfully.
Thanks for that, I gave up after 15mins
Click to expand...
Click to collapse
Has anyone else tested ubuntu on 4.2 yet? wifi works fine but dns doesn't (without su permissions, so no browsers atm) seems moreD_cn has compiled with "CONFIG_ANDROID_PARANOID_NETWORK" in his config which from my research sandboxes low level internet activity (ping etc)
i'm still trying to find a fix without having to re-compile the kernel.
Edit: problem solved you must add this to /etc/group
inet:x:3003:root,ubuntu
net_raw:x:3004:root,ubuntu
---------- Post added at 11:09 PM ---------- Previous post was at 10:24 PM ----------
Not sure if there's an easy fix, but the new kernel needs usb devices plugged in at boot
JoinTheRealms said:
Has anyone else tested ubuntu on 4.2 yet? wifi works fine but dns doesn't (without su permissions, so no browsers atm) seems moreD_cn has compiled with "CONFIG_ANDROID_PARANOID_NETWORK" in his config which from my research sandboxes low level internet activity (ping etc)
i'm still trying to find a fix without having to re-compile the kernel.
Edit: problem solved you must add this to /etc/group
inet:x:3003:root,ubuntu
net_raw:x:3004:root,ubuntu
---------- Post added at 11:09 PM ---------- Previous post was at 10:24 PM ----------
Not sure if there's an easy fix, but the new kernel needs usb devices plugged in at boot
Click to expand...
Click to collapse
So wifi does work. My Arch installs won't let me turn it on. When you get a chance, right after you fresh boot into Ubuntu, could you get a dmesg output? I have one from the old kernel setup and I would like to compare all three....
Sent from my ASUS Transformer Pad TF700t - CROMi-X 4.7.0 ODEX
workdowg said:
So wifi does work. My Arch installs won't let me turn it on. When you get a chance, right after you fresh boot into Ubuntu, could you get a dmesg output? I have one from the old kernel setup and I would like to compare all three....
Sent from my ASUS Transformer Pad TF700t - CROMi-X 4.7.0 ODEX
Click to expand...
Click to collapse
Not sure if this is what you were after
https://www.dropbox.com/s/nzmfnqnl31cicq7/logs.tar.gz (all logs)
https://www.dropbox.com/s/kl0tdkbce22ftn6/boot (dmesg)
Also how do i disable logging? i think its really hitting io performance, those logs above were 6mb when i uploaded now they are over 100
JoinTheRealms said:
Not sure if this is what you were after
https://www.dropbox.com/s/nzmfnqnl31cicq7/logs.tar.gz (all logs)
https://www.dropbox.com/s/kl0tdkbce22ftn6/boot (dmesg)
Also how do i disable logging? i think its really hitting io performance, those logs above were 6mb when i uploaded now they are over 100
Click to expand...
Click to collapse
Thank you.
That is is the kernel config... I think. MoreD_cn said he made it big for debugging.
Next time get me this from a terminal right after a fresh boot.
Code:
dmesg > dmesg.txt
Sent from my HTCEVOV4G using Tapatalk 4
Never mind it was in there.
Sent from my HTCEVOV4G using Tapatalk 4
BIG FAT WARNING:
NEXT kernel 1.0 - 2.0 requires mali-400-r3p2-01rel3-t31x.zip!
NEXT kernel 2.1 and later requires mali-400-r3p2-01rel3-api29-t31x.zip!
Sources:
Kernel sources at https://github.com/kumajaya/android_kernel_samsung_smdk4x12/tree/cm-11.0
Features:
Based on Samsung OSRC Note 2 N7100, Tab 3 8.0 and Note 8.0 kernel source
Single source for T310, T311, and T315 target (and Note 2 N710x, Note 8.0 N51xx). Only T311 version well tested on my device but both T310 and T315 version boot T311, not working GSM radio of course
Traceable source level changes: https://github.com/kumajaya/android_kernel_samsung_smdk4x12/commits/cm-11.0
Open source Samsung exFAT modules included
Remove a lot of debug message from touchscreen driver, display, mmc, modem, bluetooth, etc. Now, dmesg output more useful than stock kernel
Disable a lot of kernel debugging support
Linaro GCC compiler
The ramdisk based on JB 4.2.2 AMG3 (T310 and T311) and AMH1 (T315), OTA recovery flash disabled
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Auto root, SuperSU included please download SuperSU from Google Play. Heimdall v1.4.0 work for our device. For a brand new T31x, flash your device using "sudo heimdall flash --BOOT boot.img" and you will get rooted
Self compiled static BusyBox v1.21.1 in /sbin, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. On stock ROM, this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Mali GPU driver r3p2-01rel3
KitKat external sdcard write access for user apps patcher
Known Problems:
Thanks To:
gokhanmoral, Chainfire
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
Downloads:
http://forum.xda-developers.com/devdb/project/?id=5210#downloads
Todo:
Dual boot
Special Thanks:
@onemoreidiot, @kutaxov, @bout_time
XDA:DevDB Information
[KERNEL][SM-T31x][SINGLE/DUAL][STOCK/CM] blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 3
Contributors
ketut.kumajaya
Kernel Special Features: Dual boot stock and CM ROM
Version Information
Status: Stable
Current Stable Version: 1.7
Stable Release Date: 2014-07-11
Created 2014-08-01
Last Updated 2014-09-11
Changelog 24/08/2014, NEXT 2.x WIP:
Samsung KitKat support
Auto root reworked
External sdcard write access auto pacher
Mali 400 r3p2-01rel3 API version 29
Changelog 11/07/2014, NEXT 1.7:
Samsung OSRC SM-T310 KitKat NF4 kernel source:
Exynos platform update
Battery, regulator, and charger driver update
Touchscreen driver and firmware update
Flip sensor, WiFi, sound, IR LED and camera driver update
Memory and block related tuning
swap, frontswap, and zswap support, etc
LZO compression/decompression update
Recent GCC versions (e.g. GCC-4.7.2) compatibility fix
Changelog 16/06/2014, NEXT 1.6:
GCC Linaro 4.9.1-2014.05 toolchain
Nintendo Wii remote support, latest CM version needed
Changelog 12/06/2014, NEXT 1.5:
Applied Samsung OSRC N7100 KitKat ND4 update on top of MK9, and then rebase our current kernel to it
Low power mode charging bug fix applied, this kernel compatible to our current JB bootloader and upcoming KitKat bootloader
Incompatibility issue to CM's hwcomposer fixed
New WiFi driver, new exFAT filesystem, arm and exynos spesific update, a lot of updates from Samsung
More efficient method of passing vsync to userspace for CM
GCC Linaro 4.8-2014.04 toolchain
Full changelog https://github.com/kumajaya/android_kernel_samsung_smdk4x12/commits/cm-11.0 . Linaro 4.8 patch still not available on my github, I will push it later
Changelog 21/04/2014, NEXT 1.4:
Kernel update: stop log buffer spam, extra scheduler (sio, vr, and row), interactive governor, revert f2fs quick hack, etc: https://github.com/kumajaya/android_kernel_samsung_smdk4x12/commits/cm-11.0
Ramdisk update to upstream CM (SE Linux context, sepolicy, init and healtd binary)
Install script update for easier future maintenance
Remove workaround fix for write access to the root of ext4 or f2fs formatted SD card
Changelog 26/03/2014, NEXT 1.3:
Fix boot menu reboot to bootloader option
Insecure adb, fix compatibility issue to Omni and Slim ROM
SE Linux policy update
Workaround fix for write access to the root of ext4 or f2fs formatted SD card
Default ueventd config
Compiled AROMA from source
Compiled static busybox from CM source with patched reboot applet
Changelog 16/03/2014, NEXT 1.2:
F2FS filesystem support, completely based on @DerTeufel1980 github commits and small hack in include/linux/blk_types.h https://github.com/kumajaya/android_kernel_samsung_smdk4x12/commits/cm-11.0, Extended PhilZ Touch recovery needed for ext4 to f2fs migration
exFAT filesystem integrated in kernel
In sync to CM 11.0 init changes, CM multi SIM support compatibility issue fixed
Changelog 22/01/2014, NEXT 0.6.4:
Updated kernel source, new Mali GPU kernel driver r3p2
SuperSu 1.91 for stock ROM
Directly flash mali-400-r3p2-01rel3-blobs-t31x.zip (on both ROM for dual boot user) is a must or your device will fail to boot!
As reported by @manup456, graphic glitch occurred in stock ROM with Mali r3p2. Workaround for this issue is "Turn off hardware overlays - Always use GPU for screen compositing" in Settings - Developer but this setting doesn't stick, so you must set it on every boot. Another solution is switch to previous version of NEXT kernel and directly flash Mali r3p1 blobs (on both ROM for dual boot user).
Changelog 16/01/2014, NEXT 0.6.3:
Reworked init script as CM playground
Changelog 09/01/2014, NEXT 0.6.2:
Compatible to the new CM lights module
Changelog 05/01/2014, NEXT 0.6.1:
Flip cover detector, work on both stock and CM ROM
Changelog 30/12/2013, NEXT 0.6:
CM 11.0 support
Changelog 10/12/2013, NEXT 0.5:
Initial T315 support
CM: Ramdisk synced to unofficial CM 10.2
Changelog 02/12/2013, NEXT 0.4:
CM: fix back camera still image capture
Changelog 28/11/2013, NEXT 0.3:
CM: fix bluetooth discovery problem
CM: fix front camera preview
Add PAC ROM support
Stock: SuperSU 1.80, thanks Chainfire
T310 support
Changelog 26/11/2013, NEXT 0.2:
Add lates CM-10.2 nightly 20131125 support
SuperSU 1.75 (for stock ROM), thanks Chainfire
Changelog 25/11/2013, NEXT 0.1 brand:
Stop more spams
Linaro gcc 4.7 compatibility fix, now use GCC Linaro 4.7 compiler
VR and SIO scheduler, SIO as default sheduler
R/W semaphores implemented using ARM atomic functions
Merge espresso10 interactive CPU governor, interactive with EARLYSUSPEND support
Initializing Android USB depending on the rom type for dual boot support
Notify userspace of vsync_time using sysfs for AOSP based ROM support
Partial netfilter update, allow tracking loopback and rate limit some of the printks
Unofficial PhilZ Touch recovery
Attached PhilZ Touch recovery repack for T310 and T311. Both version tested on my T311. Both version not well tested (i.e. backup and restore not tested since have no free space SD card) but since this version based on official P5100, everything should be work correctly. Flash this at your own risk using existing CWM/TWRP recovery or Heimdall v1.4.0 "sudo heimdall flash --RECOVERY recovery.img" command.
I am almost sure @Phil3759 will officially support our device anytime soon.
ROOT + BLACKHAWK + PHILZ TOUCH FOR YOUR BRAND NEW T31X
Single step for root and PhilZ Touch recovery using Heimdall v1.4.0:
Extract both blackhawk kernel boot.img and PhilZ Touch recovery.img
Install Heimdall for your operating system: Linux, OSX, or Windows
Boot your device into download mode, connect it to your computer, flash:
Code:
heimdall flash --BOOT boot.img --RECOVERY recovery.img
Done!
NOTE: I've deleted PhilZ Touch non SELinux version to avoid confusion, total 618 downloads for all variant!
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p16 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel. BIG FAT WARNING: For stock Samsung ROM, NEXT kernel 1.0 or later requires mali-400-r3p2-01rel3-blobs-t31x.zip!
b) Flash latest Extended PhilZ Touch recovery: http://forum.xda-developers.com/showpost.php?p=51364377&postcount=33
c) Atleast 90% battery left.
d) 3 GB free on internal SD.
e) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery (red on screen navigation buttons)
iv) Flash aosp ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery (red on screen navigation buttons)
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Reboot into primary recovery
viii) Flash aosp ROM as 1st ROM
ix) Flash blackhawk's NEXT kernel again
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
25. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
26. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
27. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
28. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p21 = /data
mmcblk0p20 = /system
mmcblk0p19 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk0p16 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p21 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p16 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Build kernel and kernel modules for Samsung Galaxy Tab 3 8.0 SM-T31x Exynos 4212
Ketut P. Kumajaya <ketut.kumajaya at gmail dot com>, Oct 2013
Samsung Open Source Release Center: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-t31
Samsung OSRC exFAT source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat
Working kernel source, compilable and tested on SM-T311: https://github.com/kumajaya/android_kernel_samsung_lt01
I assume your home directory is /home/android
Clone kernel source repo:
Code:
$ cd /home/android/
$ git clone git://github.com/kumajaya/android_kernel_samsung_lt01.git
Create an environtment text file, save it as /home/android/build.env (change CROSS_COMPILE to point to your toolchain):
Code:
export CROSS_COMPILE='/opt/toolchains/arm-eabi-4.6/bin/arm-eabi-'
export LDFLAGS=''
export CFLAGS=''
export SUBARCH=arm
export ARCH=arm
Import environtment file above (dot+space+build.env), create build directory outside kernel source directory, and start the building process:
Code:
$ cd /home/android/android_kernel_samsung_lt01
$ . /home/android/build.env
$ mkdir -p /home/android/build/lt01
$ make O=/home/android/build/lt01 mrproper
$ make O=/home/android/build/lt01 tab3_3G8_01_defconfig
$ make -j8 O=/home/android/build/lt01
Copy the resulting kernel and modules to a binary directory:
Code:
$ mkdir -p /home/android/build/lt01-bin
$ cp /home/android/build/lt01/arch/arm/boot/zImage /home/android/build/lt01-bin/
$ find /home/android/build/lt01/ -type f -name *.ko -exec cp {} /home/android/build/lt01-bin/ \;
Your kernel and all kernel modules ready in /home/android/build/lt01-bin/
{
"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"
}
The resulting kernel also already tested as PhilZ Touch recovery kernel, running on SM-T311 PhilZ Touch repacked from PhilZ Touch recovery for Galaxy Tab 2 10.1 target
Samsung Galaxy Tab 3 8.0 original boot logo:
oc kernel ?? thanks.
Finally a developer with GTab 3 8inch :good: :good:
Can't wait to see a flashable zip and try on my tab
Just got a black screen of death when trying to replace Samsung boot logo Solved: reflash my own param.bin Odin flashable tar.md5
rothshek said:
oc kernel ?? thanks.
Click to expand...
Click to collapse
There's no OC commit: https://github.com/kumajaya/android_kernel_samsung_lt01/commits/master
Kernel and unofficial PhilZ Touch recovery repack attached at post #1.
Kernel: almost stock, compiled using gcc linaro 4.7, a lot of kernel debugging support disabled, still leave all Samsung kernel spams, restricted root disabled
Ramdisk: self compiled busybox included, auto root, init.d support, flash recovery disabled
Open source, commit history: https://github.com/kumajaya/android_kernel_samsung_lt01/commits/master
PhilZ Touch repack based on official PhilZ Touch for Tab 2 10.1, thanks @Phil3759
Still in development
Flash the kernel and/or PhilZ Touch using existing CWM/TWRP recovery
Derp!
ketut.kumajaya said:
Kernel and unofficial PhilZ Touch recovery repack attached at post #1.
Kernel: almost stock, compiled using gcc linaro 4.7, a lot of kernel debugging support disabled, still leave all Samsung kernel spams, restricted root disabled
Ramdisk: self compiled busybox included, auto root, init.d support, flash recovery disabled
Open source, commit history: https://github.com/kumajaya/android_kernel_samsung_lt01/commits/master
PhilZ Touch repack based on official PhilZ Touch for Tab 2 10.1, thanks @Phil3759
Still in development
Flash the kernel and/or PhilZ Touch using existing CWM/TWRP recovery
Click to expand...
Click to collapse
PhilZ Touch runs on T-310? ExFat memory cards supported? There is support for the work of internal memory?
marincax said:
PhilZ Touch runs on T-310? ExFat memory cards supported? There is support for the work of internal memory?
Click to expand...
Click to collapse
I will upload T310 version. T311 version attached at post #1 also work on T310 but every device have a different identity (default.prop). Internal and external memory works, including exFAT support.
I've been disable so much kernel spam but still a lot left flooding the kernel message buffer, just saying
ketut.kumajaya said:
I will upload T310 version. T311 version attached at post #1 also work on T310 but every device have a different identity (default.prop). Internal and external memory works, including exFAT support.
Click to expand...
Click to collapse
Thanks a lot for your reply.:good:
Will be there be enough to replace default.prop in a version for T-311 on default.prop recovery from original T-310?
marincax said:
Thanks a lot for your reply.:good:
Will be there be enough to replace default.prop in a version for T-311 on default.prop recovery from original T-310?
Click to expand...
Click to collapse
Yes, with 2 lines modification:
Code:
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ketut.kumajaya said:
I've been disable so much kernel spam but still a lot left flooding the kernel message buffer, just saying
Click to expand...
Click to collapse
Please leave messages Logcat, kmsg and dmesg. :crying:
Yes, with 2 lines modification:
Code:
ro.debuggable=1
persist.sys.usb.config=mtp,adb
Click to expand...
Click to collapse
Thank you so will I do.
Still changed:
ro.secure=0
ro.adb.secure=0
marincax said:
Please leave messages Logcat, kmsg and dmesg. :crying:
Thank you so will I do.
Click to expand...
Click to collapse
Don't worry, disable the kernel message is really a bad idea :laugh: How about switchable logcat?
ketut.kumajaya said:
Don't worry, disable the kernel message is really a bad idea :laugh: How about switchable logcat?
Click to expand...
Click to collapse
Yes, it will be good. :good: