{
"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"
}
INT2EXTV2+ Posted
If you like it please click thanks on this post and give it a rating
Thanks to all users and contributors
About:
CronMod INT2EXT was wrote for use in my rom with the goal to achive a stable and fast way of moving the data partition of your phone to the sd-ext partition, they are available for all users and developers to use in any rooted rom with init.d support.
CronMod INT2EXT scripts are the first universal INT2EXT method released
Developer Stuff Next Post
Features:
(All scripts are tested on Android 2.3.7 - 4.2.2)
INT2EXT
-Mounts /sd-ext to /data
-Works with EXT 2/3/4 filesystems
-ZipAligns /data/app on every boot
-No symlinks
INT2EXT+
-Mounts /sd-ext to /data
-Leaves /data/data on internal for speed
-Works with EXT 2/3/4 filesystems
-ZipAligns /data/app on every boot
-No symlinks
INT2EXT4
-Mounts /sd-ext to /data
-Works with EXT 4 filesystem
-ZipAligns /data/app on every boot
-No symlinks
INT2EXT4+
-Mounts /sd-ext to /data
-Leaves /data/data on internal for speed
-Works with EXT 4 filesystem
-ZipAligns /data/app on every boot
-No symlinks
INT2EXTV2+
-Mounts /sd-ext to /data
-Leaves /data/data on internal for speed
-Works with EXT 2/3/4 filesystems
-ZipAligns /data/app on every boot
-No symlinks
-Supports SWAP2INT
-Completely universal (Testing is needed)
Prerequisites:
-Rooted Rom with init.d support
-SD-EXT partition
-100mb internal is needed for every 500mb sd-ext
SD Card Partitioning:
Partition 1 - Fat32
Partition 2 - Ext 2/3/4
Install:
(Instructions based on ClockWorkMod recovery)
-Download Chosen Script Below
-Place on root of your sdcard
-Reboot Recovery
-Select "install zip from sdcard"
-Select "choose zip from sdcard"
-Select "CronMod-****_signed"
-Select "mounts and storage" category
-Select "format /sd-ext"
-Reboot
(if you already use a A2SD/D2EXT/INT2EXT/M2SD script then you will need to remove it completely)
Downloads:
(Please leave feedback)
INT2EXT
INT2EXT+ (Recommended and featured in CronMod Roms)
INT2EXT4
INT2EXT4+
INT2EXTV2+ (This script is a new int2ext script that should fix all bugs, it cannot be flashed over previous versions, please test and leave feedback)
Dalvik-Cache Wipe Tool (This is for wiping /dalvik-cache when running a INT2EXT script)
Extra:
Bravo/Bravoc GB thread
Bravo/Bravoc JB thread
Dream thread
Sapphire thread
Bugs:
-Some phones can experience a low sound bug (fix: run fix-permissions or try INT2EXTV2+)
Credits
-Wes Garner - "Auto ZipAlign Script"
-CyanogenMod - "Bind Cache Script"
-Matermind1024 "Help with resolving IMEI and Baseband issues"
-vvFICKvv, DK75, and Dark Passenger "Help to fix compatibility issues with Android 4.2.x"
[email protected] "Code to check if mmcblk0p2 exists"
-BlazinReign (my girlfriend) "donating her old laptop to the cause, and putting up with my development work "
-XDA "hosting the fourms"
Donators
(if you make a donation and your name is not here send me a pm)
[URL="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=RXYPT5A5ACJ7W"]
[/URL]
Developer Area
Developer area
Info
These scripts are for use in your roms if you like them and want to include them all i ask is that you give me proper credit in your thread.
Instructions
To include one of my scripts in your rom just add it to the init.d folder and rename it to 40a2sd/40d2ext/40int2ext depending on the chosen script, if you choose a d2ext/int2ext script then remove the "06mountdl" or "06BindCache" if they exist as the script will do this from now on.
CronMod A2SD/D2EXT/INT2EXT Scripts for Developers
Nice job with all these scripts. I will give it a try in my ported rom, just one question: it will be activated from the first boot or users have to activated from terminal?
rmg2 said:
Nice job with all these scripts. I will give it a try in my ported rom, just one question: it will be activated from the first boot or users have to activated from terminal?
Click to expand...
Click to collapse
They activate on boot and do not require a reboot after firstboot like most d2ext
I can successful install A2SD++ in my Hauwei v8150 w/CM7.2 RC3 ROM and
working normal but Partition 2 of SD card only can format to Ext 3 due to
class-4 limitation!
Thanks so much for your effort!!!
jackson0829 said:
I can successful install A2SD++ in my Hauwei v8150 w/CM7.2 RC3 ROM and
working normal but Partition 2 of SD card only can format to Ext 3 due to
class-4 limitation!
Thanks so much for your effort!!!
Click to expand...
Click to collapse
thanks for the feedback glad you like it
D2EXT or D2EXT+
Hi!
Which one is the best choice for a low-RAM device like a HTC Magic 32B?
Which are the expected features for the incoming INT2EXT script?
Data2ext+ is working well in my device... Thanks for your effort!!!
:good:
gonzalocav said:
Hi!
Which one is the best choice for a low-RAM device like a HTC Magic 32B?
Which are the expected features for the incoming INT2EXT script?
Data2ext+ is working well in my device... Thanks for your effort!!!
:good:
Click to expand...
Click to collapse
i prefer the d2ext+, the int2ext is like d2ext but uses no symlinks
what is the difference between these and mount2sd?? and i like to install d2ext+ or int2sd+ for euroskank rom.is it possible?and what is the best?
siavash2death said:
what is the difference between these and mount2sd?? and i like to install d2ext+ or int2sd+ for euroskank rom.is it possible?and what is the best?
Click to expand...
Click to collapse
i dont use mount2sd so i am unsure, i would recommend if you need stability to use d2ext+ because the int2ext scripts are not long term tested.
Works with the wildfire s, no need to reboot twice to get d2ext+ working, in first boot after rom install working flawlessly. Thanks
andreasf93 said:
I am unsure what to use. I have a Galaxy Mini with very low internal memory. I should install A2SD++ right?
Sent from SGM using CyanMobile
Click to expand...
Click to collapse
try a d2ext script first they give the most space, if you find it to slow use a a2sd script instead
Currently trying A2sd++ on Lg500h Cm7 nightly 7/01. Simple enough to setup, and works flawlessly, keep up the good work :thumbup:
Sent from my LG-P500 using xda app-developers app
is possible to use this script in a sense rom? thank you
katurras said:
is possible to use this script in a sense rom? thank you
Click to expand...
Click to collapse
possibly i have not tried, i have tried it in ics and gb, if you try please let me know the results and i will try to write one for sense if it does not work
andreasf93 said:
I tried both D2EXT and A2SD on cm7.2 official galaxy mini and none worked. Applications get installed in internal memory as usual.
Click to expand...
Click to collapse
then somthing is wrong with your partitions
what is your partition table?
edit: in terminal emulator run "df" if you use d2ext you will see a mount called /data_internal if you do it is working, if you use a2sd you will see mounts called /data/app and /data/app-private and maybe more depending on the chosen script if you do it is working
croniccorey said:
possibly i have not tried, i have tried it in ics and gb, if you try please let me know the results and i will try to write one for sense if it does not work
Click to expand...
Click to collapse
does not work.
Thanks for your effort to keep our old HTC Magic alive
only tried A2SD
katurras said:
does not work.
Thanks for your effort to keep our old HTC Magic alive
only tried A2SD
Click to expand...
Click to collapse
thank you i will try to make 1 for sense roms
hi
getting Status (0) error.what am i doing wrong
Running df
croniccorey said:
then somthing is wrong with your partitions
what is your partition table?
edit: in terminal emulator run "df" if you use d2ext you will see a mount called /data_internal if you do it is working, if you use a2sd you will see mounts called /data/app and /data/app-private and maybe more depending on the chosen script if you do it is working
Click to expand...
Click to collapse
I thought I installed D2EXT+ and it was working. But I see this image and I don't know now...
Is it working?
Related
*** I am not responsible for any damage, lost or explosion. So, try it as your own risk ***
I successfully mount my 250G powered external HD with NTFS partition on this post: http://forum.xda-developers.com/showpost.php?p=14650094&postcount=146
Here are the steps:
1. Root is a must
2. Install any terminal emulator from the market.
3. d/l and extract the ntfs.ko to your i9100
4. load the ntfs.ko with insmod (update: Some custom kernel doesn't work with module, try CF-root kernel or any stock kernel if you have problem loading the module)
5. Connect your drive with OTG.
6. Don't need to worry about "USB storage blank or has unsupported file" complaint in the notification area. But you may need a Y splitter USB cable with power supply if you got an high power consumption complaint.
7. Follow the screen shoot for the mounting command. "iocharset=utf8" is needed if you have non English files/folders name
8. Verify the mount with ls command
9. Verify non root apps (e.g. Astro File Manager) are able to read the files
10. After you done, make sure no process is accessing the mount, then un-mount using the umount command. You may want to remove the module using rmmod.
{
"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"
}
[request] Can this be done with a sdcard? That would be nice.
Maybe built in a rom
Awesome work il give it a try.. Just one question lol whats insmod?
Sent from my GT-I9100 using XDA App
I have a problem with "mount" - "mount: can't read /etc/fstab: No such file or directory". What's wrong? I can't find fstab in /etc, there is only vold.fstab.
Try
#cat /proc/mounts > /etc/fstab
#chmod 644 /etc/fstab
Now I have /etc/fstab but "mount: can't find /dev/block/sd in /etc/fstab".
How can I build a good fstab???
Edit: nevermind, I used a bad command, it works now but read only, so I'm waiting for a full working module. Thanks very much for your works jackleung. Best regards!
jackleung said:
*** I am not responsible for any damage, lost or explosion. So, try it as your own risk ***
I successfully mount my 250G powered external HD with NTFS partition on this post: http://forum.xda-developers.com/showpost.php?p=14650094&postcount=146
Here are the steps:
1. Root is a must
2. Install any terminal emulator from the market.
3. d/l and extract the ntfs.ko to your i9100
4. load the ntfs.ko with insmod
5. Connect your drive with OTG.
6. Don't need to worry about "USB storage blank or has unsupported file" complaint in the notification area. But you may need a Y splitter USB cable with power supply if you got an high power consumption complaint.
7. Follow the screen shoot for the mounting command. "iocharset=utf8" is needed if you have non English files/folders name
8. Verify the mount with ls command
9. Verify non root apps (e.g. Astro File Manager) are able to read the files
10. After you done, make sure no process is accessing the mount, then un-mount using the umount command. You may want to remove the module using rmmod.
Click to expand...
Click to collapse
Can you please upload a video showing how to do it for noobs
Sent from my GT-I9100 using XDA App
Waiting for my OTG Cable to arrive and will 100% try this. Do you get a good playback speed of 720p/1080p videos using ntfs drives?
hakkinenvthh said:
Edit: nevermind, I used a bad command, it works now but read only, so I'm waiting for a full working module. Thanks very much for your works jackleung. Best regards!
Click to expand...
Click to collapse
What command have you use finally? I was thinking you may have different block device instead of hda1.
For writing, we may need NTFS-3G but that I don't know where to get the source for **Android**. And I really don't have time to dig into that yet.
mythoc said:
Waiting for my OTG Cable to arrive and will 100% try this. Do you get a good playback speed of 720p/1080p videos using ntfs drives?
Click to expand...
Click to collapse
I haven't try. Practically, media sharing over Samba (cifs) is more useful for me. I can watch 720p video over the wireless G network shared folders.
@Tulips, it should work but may not be useful without write ability.
insmod = insert modules
lsmod = list modules
rmmod = remove modules
okey, sdcard works using the device /dev/block/mmcblk1p1, but as you said read only.
@jackleung : Where did you get this module from? Did you build it yourself from the kernel source, or downloaded it from somewhere else? As far as I understood, the linux kernel now fully supports ntfs rw capabilities (for several years, if I'm not mistaken).
Tulips said:
@jackleung : Where did you get this module from? Did you build it yourself from the kernel source, or downloaded it from somewhere else? As far as I understood, the linux kernel now fully supports ntfs rw capabilities (for several years, if I'm not mistaken).
Click to expand...
Click to collapse
I built from the kernel source d/l from Samsung. Here is the situation stated in wiki:
The ability to read and write to NTFS is provided by the NTFS-3G driver. It is included in most Linux distributions. Other solutions exist as well:
Linux kernel 2.2: Kernel versions 2.2.0 and later include the ability to read NTFS partitions
....
Note that all three userspace drivers, namely NTFSMount, NTFS-3G and Captive NTFS, are built on the Filesystem in Userspace (FUSE), a Linux kernel module tasked with bridging userspace and kernel code to save and retrieve data.
Click to expand...
Click to collapse
I do find the FUSE in the kernel source, but I believe we still need some user space program like NTFS-3G to manage it.
jackleung said:
What command have you use finally? I was thinking you may have different block device instead of hda1.
For writing, we may need NTFS-3G but that I don't know where to get the source for **Android**. And I really don't have time to dig into that yet.
Click to expand...
Click to collapse
I used exactly the same to you I think it's better if you can make it mounted automatically (by modify the kernel???) or make a software to do it
I can mount a NTFS microsd but after that the phone can't be recognized by the PC, unless I format it by the phone
mythoc said:
Waiting for my OTG Cable to arrive and will 100% try this. Do you get a good playback speed of 720p/1080p videos using ntfs drives?
Click to expand...
Click to collapse
well i watched 1080p clips and they worked perfectly fine, the file size was 8gb, not sure about bitrate or anything though
why is this not in the Dev Section???!!
[email protected]!
My first successful attempt with ntfs-3g can be found here: http://forum.xda-developers.com/showpost.php?p=15001824&postcount=23
jastonas said:
why is this not in the Dev Section???!!
[email protected]!
Click to expand...
Click to collapse
Because nothing being developed. I simply compiled a module from existing source code.
I wrote two small shell scripts for mount and unmount.
Both i can run in GScript (free light version from market).
The first ist mounting:
Code:
insmod /mnt/sdcard/ntfs.ko
mkdir /mnt/sdcard/usbStorage/usb_ntfs
sleep 1
mount -t ntfs -o rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,iocharset=utf8 /dev/block/sda1 /mnt/sdcard/usbStorage/usb_ntfs
And this one for unmounting:
Code:
umount -f /mnt/sdcard/usbStorage/usb_ntfs
rmmod ntfs
Both scripts are attached and if they are saved on sdcard in a folder namend "gscript" they can be imported directly into GScript.
The ntfs.ko file has to be placed in the root folder of the SD-Card (/mnt/sdcard/ntfs.ko).
@jackleung: Thank you for compiling
Ps: sorry for my bad english... ;-)
Could someone please upload a video on youtube showing how to do it. I dont understand all this mount and unmount.. Do i need to unmount before i take out the usb drive?
Sent from my GT-I9100 using XDA App
Could you compile ext3 kernel module too, please ?
I'm trying to mount a linux image but there's no ext3 support so I cannot mount it
alx5962 said:
Could you compile ext3 kernel module too, please ?
I'm trying to mount a linux image but there's no ext3 support so I cannot mount it
Click to expand...
Click to collapse
Maybe ext2/3 doesn't even need a module? Could someone just try this command?
Code:
mount -t ext2 -o uid=1000,gid=1015,iocharset=utf8,umask=000 /dev/block/sda1
(.../dev/block/mmcblk1p1 for microSD)
Help wat do i do i keep getting this
Sent from my GT-I9100 using XDA App
Dual Boot for SGSA
So many devices are getting Dual Boot capability nowadays.So i decided to do same for our beloved SGSA.
EDIT : Guide Updated. Using slow sdcard as /system and /data was bad idea. Now secondary ROM work at same speed as primary ROM since we aren't using external SD card anymore
Read first three posts carefully before doing anything
Highlights:
No lags, bugs.Both ROMs works almost same
Stable. Booting of ROM is based on kernel. So as long as you stay on a kernel it'll keep booting ROM for which it is designed without interference with another ROM.
ROM can be switched by changing Kernel.
Stock ROM fully supported. Now you can feel speed of CM ROM with stability of stock ROM
Click to expand...
Click to collapse
How to use this:
Well, steps are quite easy.Just follow them one by one and you won't get any troubles.But please follow steps one by one, don't take shortcuts.
On PC extract ROM which you want to install as secondary ROM.
You'll get following files/folders there : META-INF, system, boot.img
Delete META-INF and boot.img
Download appropriate META-INF_*.zip from downloads section.Extract it and move extracted META-INF folder to location from where we deleted META-INF.
Navigate to /system folder and move folder named app to parent folder (i.e. if app folder is located at C:\blah\system\app then move it to C:\blah\app)
Select three folders (META-INF, system, app) and compress them to zip format.Push this file to device.
All above steps are mentioned in below video
Download appropriate Kernel from Downloads sections.
Flash that kernel using Universal Kernel Flash Tool or by writing in terminal dd if=/sdcard/kernel.bin of=/dev/block/mmcblk0p15
Power off your device
Now reboot into recovery by holding VOL UP + HOME + POWER (don't take shortcut here )
Ignore any warnings recovery shows.
Install the zip file which you pushed before as you install normally (Do not use Wipe options)
Download appropriate GAPPS package from download section (Do not install normal gapps.To know reason, read third post)
Reboot it.That's all (Keep in mind, first boot always takes long time)
If WiFi don't work on secondary ROM then flash appropriate modules from Downloads section
Read "Things to keep in mind" in third post.
Click to expand...
Click to collapse
How to switch ROM:
Flash kernels provided here to boot secondary ROM.
Flash native kernel (which comes with ROM) to boot primary ROM. (If you're using CM based primary ROM then take backup of stock CM kernel before flashing another kernel.)
Click to expand...
Click to collapse
How to change ROM:
Boot up your primary ROM.
Navigate to /data
Delete folder : /data/secondary_data
Now flash secondary Kernel and flash secondary ROM as you would.
or you can use my App for doing this stuff...
Click to expand...
Click to collapse
Using DualBoot App:
After installing secondary ROM as mentioned above, you can use my Dual Boot app to switch easily between ROMs. Additionally you can also use it for other options like sharing installed apps, factory reset secondary ROM etc. It will automatically download required kernel (Read third post). App is easy to use, just install it as Normal apk. You can also share this app with secondary ROM as mentioned below.
Wipe data/factory Reset - Factory reset secondary ROM
Share Apps with Primary - Share all apps of primary ROM with secondary ROM. This will reduce space used by secondary ROM. Use this option with CAUTION because some apps like Play store can FC. So it is better to use custom share apps option.
Revert Share Apps with Primary - This will remove all installed apps of secondary ROM
Custom Share Apps - Best way to share installed apps on primary with secondary ROM. Share as much apps as possible to reduce storage usage by secondary ROM.
Clean UP - Removes all files used in DualBoot mode
And more to come...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
ROMs supported:
Primary ROM ----> Any ROM
Secondary ROM ----> All CM based ROM
Click to expand...
Click to collapse
Technical info:
--> Mounted /dev/block/mmcblk0p4 as /system
--> Since it is smaller (300 MB) in size we're symlinking /system/app folder of secondary rom to /data/app
--> Using /data partition for both /data & /cache of secondary ROM
Click to expand...
Click to collapse
Future Plans:
An App so things become more easy (done)
Kexec support in kernel (WIP)
Click to expand...
Click to collapse
Sources:
Kernel Sources : Checkout TeamCanjica's repo
DualBoot App : Github
Click to expand...
Click to collapse
I'm writing an app for this.Once it is completed it would be much easier to do this thing
As usual, i don't take any responsibility of bricked devices, nuclear wars etc...
Downloads & Changelog
Downloads:
EDIT:
Since Dev-Host removed all my files i've re uploaded them to mediafire (Link to folder below). Since all files are removed from my account DualBoot app won't be able to download kernels. So manually download them and put them on sd card as instructed.
META-INF:
CM 10.1 || CM 10.2 || CM 11 || MIUI || AOSP (KK) || Liquid Smooth 3.0
Click to expand...
Click to collapse
Kernel:
CM 10.1 || CM 10.2 || CM 11 || MIUI || AOSP (KK)
Click to expand...
Click to collapse
Modules:
CM 11
Click to expand...
Click to collapse
GAPPS:
CM 10.1 || CM 10.2 || CM 11
Click to expand...
Click to collapse
Download META_INF, Kernels, GApps:
Mediafire Folder
Click to expand...
Click to collapse
DualBoot Application:
DualBoot v1.22
Click to expand...
Click to collapse
Changelog:
27/04/14 ---> Fixed FC problem on CM11, Kernel with OC support (same as TC's last release)
21/02/14 ---> Liquid Smooth 3.0 Support
10/02/14 ---> AOSP (KK) Support, Fixed download links of stock kernels for CM10.2/11
05/02/14 ---> MIUI v5 Support
21/01/14 ---> DualBoot App released, Updated META-INF folder for latest CM10.2 to fix errors
08/01/14 ---> Fixed bug with CM11 which was preventing it from booting second time
06/01/14 ---> CM11 support
04/01/14 ---> No need for external SD card.Both ROMs work at same speed, no more lagginess
11/11/13 ---> Initial Release
Click to expand...
Click to collapse
DualBoot App Changelog:
27/04/14 ---> Unsupported device problem fixed, Updated all kernel links
12/02/14 ---> Fixed AOSP, Removed app folder share (use custom app share instead)
10/02/14 ---> AOSP (KK) Support, Fixed download links of stock kernels for CM10.2/11
05/02/14 ---> MIUI support. Allows user to flash unknown kernel to use any ROM as Primary ROM
21/01/14 ---> Initial Release
Click to expand...
Click to collapse
Pros, cons, Tips, Future Plans
FAQs:
Q. How can i factory reset second ROM?
A. Boot into primary ROM and go to /data/secondary_data using any explorer and delete following folders : cache, data
Click to expand...
Click to collapse
Q. How can i totally remove dual boot from my data partition?
A. Simple, just boot into primary ROM and delete /data/secondary_data folder.Now delete all contents of /cache folder.
Click to expand...
Click to collapse
Q. WiFi is not working on secondary ROM. What should i do?
A. Boot into secondary ROM's recovery and flash appropriate modules from downloads section
Click to expand...
Click to collapse
Things to keep in mind:
Wipe/data Factory reset from primary ROM will remove secondary ROM also.
Do not wipe cache partition after installing this mod (for both primary & secondary ROMs).
Don't touch anything other than install zip ( like wipe data/cache etc because they'll lead to unexpected results ) when using secondary ROM's recovery.
We're running out of space for /system partition in secondary ROM so please don't keep flashing random tweaks, mods which put files on /system partition.If it is emergency then use /preload partition and symlink them manually.
Do not install GAPPS for secondary ROM.Use only which i provided.
When CM based ROM is installed as secondary ROM then by default swap functionality is disabled on /preload (which TeamCanjica enabled).So stock ROM as primary ROM is compatible.
Ignore any warnings shown by secondary recovery.If you get any error then contact me.
Provided GAPPS are not full gapps it'll only install Play Store s that you can install other apps from market.
We have 2GB space in /data partition.I've been using this device for 9 months and it never took more than 1GB space on /data.But still if you're finding less storage then move some apps to sdcard.Still if you need more then contact me, we'll move some more files.
If you want to dual boot CM & stock ROM then it is necessary to install stock as primary because they're huge to be included on /cache partition.Although it is not impossible, if you're expert there, then you can create symlinks to make it work.But i won't support that way.So secondary ROM must be CM based.
Backup/Restore function won't work with secondary ROM
When wiping primary rom, it is impossible to save secondary rom unless you made backup.
Even though Dual Boot app downloads kernel automatically, it is advised that you download required kernels & manually and put them in proper folder ({internalsdcard}/DualBoot/) to avoid bad & corrupt downloads. In case if this happens & you phone don't boot up, don't worry, just flash stock kernel with odin & everything will be fine.
Click to expand...
Click to collapse
How to add Support for Unsupported ROM:
This tutorial will help you to add support for those ROMs which are based on already supported ROMs (like CM11, CM10.2 etc). This tutorial will teach you to create META-INF folder for particular ROM to avoid status 7 error. Please follow it carefully
Open META-INF\com\google\android\updater-script
Find and delete following code/ same code
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
set_metadata("/tmp/backuptool.functions", "uid", 0, "gid", 0, "mode", 0644);
run_program("/tmp/backuptool.sh", "backup");
Now find
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p3", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
& replace /dev/block/mmcblk0p3 with /dev/block/mmcblk0p4
Search for package_extract_dir("system", "/system"); & add this code after it
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/primary_data");
run_program("/sbin/busybox", "mkdir", "-p", "/primary_data/secondary_data/system");
delete_recursive("/primary_data/secondary_data/system");
package_extract_dir("app", "/primary_data/secondary_data/system");
symlink("/primary_data/secondary_data/system", "/system/app");
At the end of the script remove package_extract_file("boot.img", "/dev/block/mmcblk0p15"); or anything related to kernel flashing like write_raw_image etc.
Click to expand...
Click to collapse
Awesome...:good:
Wanted to try it but I have a 2gb memory card...
So I will have to Wait till my new memory card arrives:fingers-crossed:
i have a class 10 sd card..i ll try this as soon as i can..just a thing...AWESOME
Sent from my GT-I9070 using XDA Premium 4 mobile app
tried but not work. it just boot direct to recovery
wmfaiz said:
tried but not work. it just boot direct to recovery
Click to expand...
Click to collapse
Yep because you messed up with our param drivers.As i told before don't use any command like reboot recovery and don't use 4 way reboot (if your ROM supports) to enter recovery.This will keep you throwing into recovery.The solution is flash primary ROM's kernel then reboot normally.Use UKF to flash secondary kernel.Now power off your device and then use Hardware keys to enter recovery or if you've already installed secondary ROM then power on normally.
Our ramdisk is splitted on device tree/rootdir, device-common/rootdir, vendor/cm/rootdir and so... We went back to gzip kernel compression so you can easily unpack its boot.img
Sent from my GT-I9070 using xda app-developers app
frapeti said:
Our ramdisk is splitted on device tree/rootdir, device-common/rootdir, vendor/cm/rootdir and so... We went back to gzip kernel compression so you can easily unpack its boot.img
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Thanks.I'm waiting for next build because last build has lzma compressed zImage.
dual boot?
cool...
I was used dual boot on my old device Galaxy Tab 2, very useful for testing a new rom before become it that rom as primary rom for daily use
great work
Update
So as i told on FB group yesterday i managed to boot both ROMs directly from eMMC.
--> Now we don't need external sdcard.
--> Both ROMs works at same speed.
--> Stable, no bugs.
--> Easy to install.
For writing noob friendly guide it took longer time.So if i'd forgot to write anything or if you've any question feel free to post here.
But Before posting anything read first 3 posts carefully.
And yeah i'm also writing an app to do it easily.Once i'll do it, this will be much easier.
Sorry guys i've messed up my Debian partition so can't add support for CM11, CM10.1 now. I'll add links for them asap .
Till then enjoy CM10.2 and keep supporting me...:good:
Many thanks for your hardwork man! For achieving dual boot on our device and keep on simplify the method of doing it. It is also happy to see that there is another app under developing to make things more easier, i will definitely try this out once i finished my exam!
Thanks a lot man :thumbup:
I will use it when you will add CM 11 compatibility.
BOOTMGR said:
So as i told on FB group yesterday i managed to boot both ROMs directly from eMMC.
--> Now we don't need external sdcard.
--> Both ROMs works at same speed.
--> Stable, no bugs.
--> Easy to install.
For writing noob friendly guide it took longer time.So if i'd forgot to write anything or if you've any question feel free to post here.
But Before posting anything read first 3 posts carefully.
And yeah i'm also writing an app to do it easily.Once i'll do it, this will be much easier.
Sorry guys i've messed up my Debian partition so can't add support for CM11, CM10.1 now. I'll add links for them asap .
Till then enjoy CM10.2 and keep supporting me...:good:
Click to expand...
Click to collapse
OFFTOPIC
Did anybody tell you that you are AWESOME.
If you can debloat more and odex your harshjelly rom & put the odexes in preload folder and symlink them to /system, then probably you can save some space in /system partition and /data as dalvik cache wont be generated.
As you said there wont be any future updates, odexing is a fine option.
Just a thought. Can it be done ????
EDIT:
You can also remove apps like gmail hangouts etc as they are updated from time to time. You will save some space in /system
Again offtopic
Are you going to change your rom's name BOOTMGRjelly???
<O.T>
+1 to each thing in above post....
let me again tell u that you r really really AWESOME :angel: :laugh:
btw idea of debloating HJ is good ......personally i'm using heavily debloated HJ without any feature loss
BOOTMGR said:
ROMs supported:
Primary ROM ----> Any ROM
Secondary ROM ----> All CM based ROM
Click to expand...
Click to collapse
I assume Primary ROM must be 4.0 or higher and not GB?
Just installed CM 10.2 as You wrote, all works fine. Great work, really. Tnx for that.
I have a question: if is possible to make links from main ROM app and data to second ROM app and data to save space?
I mean: no install new app only use existing installation of applications and their data.
GT-I9070 ==> Tapatalk space
anantttt said:
OFFTOPIC
Did anybody tell you that you are AWESOME.
If you can debloat more and odex your harshjelly rom & put the odexes in preload folder and symlink them to /system, then probably you can save some space in /system partition and /data as dalvik cache wont be generated.
As you said there wont be any future updates, odexing is a fine option.
Just a thought. Can it be done ????
EDIT:
You can also remove apps like gmail hangouts etc as they are updated from time to time. You will save some space in /system
Again offtopic
Are you going to change your rom's name BOOTMGRjelly???
Click to expand...
Click to collapse
Yeah it can be fitted as secondary ROM by debloating.But still some users will ask for some features.We can even use symlinks and can place it as secondary ROM without debloating it but it'll raise complexities.So it is better to use it as secondary ROM.
Odexing and placing them on /preload i also nice idead.But still i'll prefer to use it as primary ROM...
BTW,HarshJelly seems better than BOOTMGRjelly...:silly:
purplepizza said:
I assume Primary ROM must be 4.0 or higher and not GB?
Click to expand...
Click to collapse
Yeah.No support for GB (i'll think about it.If there won't be much difference (except baseband) between GB and JB we can also do it.)
darcik said:
Just installed CM 10.2 as You wrote, all works fine. Great work, really. Tnx for that.
I have a question: if is possible to make links from main ROM app and data to second ROM app and data to save space?
I mean: no install new app only use existing installation of applications and their data.
GT-I9070 ==> Tapatalk space
Click to expand...
Click to collapse
Yesterday @Sami Kabir asked same question on FB group.Here is the answer.
Only apps can be shared between both ROMs not their data.The reason is that data of system apps and normal data apps both are stored under same folder (/data/data).So can't we share this folder? answer is no because namespace conflicts will arise there (Ex. package name for phone app is com.android.phone.It'll remain same for all android versions.It is possible that use have installed both ROMs of different API level.So if one phone app stores its data under /data/data then other won't be able to read it and you'll get FC)
Although it is possible to share apps between two apps.When i'll complete app, i'll provide an option for that....:good:
Cache partition
FAQs:
Q. How can i totally remove dual boot from my data partition?
A. Simple, just boot into primary ROM and delete /data/secondary_data folder
Click to expand...
Click to collapse
Do I need to also delete files from or format the cache partition?
Idk if this partition is used if is only one ROM, seems not if dual is using it.
CM11 Support
darcik said:
Do I need to also delete files from or format the cache partition?
Idk if this partition is used if is only one ROM, seems not if dual is using it.
Click to expand...
Click to collapse
Yeah i forgot to write, you also need to delete contents of /cache folder or format cache partition.
That partition is like placebo.It is only used when upgrading android (that means generating dalvik cache (actually that partition was used to store dalvik cache but later on dalvik cache was also moved to /data partition so its useless now except time of generation of dalvik cache)
@all:
Added CM11 support.
Links are up.
Method remains same.
I've checked way to share apps between ROMs (and thus storage use will be much less).
I'll let user to choose whether to share apps or not which will be possible through DualBoot app.
{
"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"
}
For anyone interested, below are the steps for getting your device dual-booting with CyanogenMod 10.2.
Why?
I don't want to erase native firmware and want to give a try to CyanogenMod
I want to have both native and CM, because I like native Samsung S-Pen apps, but want to have more fresh Android too
I like experimenting - it's cool!
The Idea
Our Android device has 2 boot partitions - for normal boot, and to boot into recovery. If I want to boot CyanogenMod, I need to place its boot image instead one of those boot partitions. E.g. if I want to have both native firmware and cyanogen - then obviously I need to replace recovery partition. However I can do the backup of recovery and restore it later if needed.
But, I also need to place cyanogen system and data partitions somewhere. Putting it on the external sdcard makes CM working really slow, repartitioning internal memory might be good idea, but it is not so easy and is not necessary for experimenting. Thus I've created 2 image files and put it to native data partition (mmcblk0p12) to media folder, e.g. into internal sdcard, then changed cyanogen boot image to mount those image files on boot as system and data partitions.
Prerequisites:
Rooted Samsung Galaxy Note 10.1 2012 Edition
2GB of free disk space at internal sdcard
Recovery partition backup, because we are going to replace it with CyanogenMod boot image
Clear understanding of what you are doing, because you potentially can break your device
Downloads:
CM 10.2 boot image
CM 10.2 data partition image
CM 10.2 system partition image
Steps
This manual suggests that you are going to do the recovery backup to external sdcard and has native firmware which means that recovery partition is mmcblk0p6, data partition is mmcblk0p12 and internal sdcard is /mnt/sdcard folder (otherwise you need to change the commands appropriately and might need to fix cyanogen boot image too).
Download 3 files by the links above and upload to internal sdcard of your device. Connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to external sdcard to create recovery backup
cd /mnt/extSdCard
dd if=/dev/block/mmcblk0p6 of=./recovery.img
# go to internal sdcard folder
cd /mnt/sdcard
# unpack partition images - each is 1Gb of disk space
gunzip ./system.img.gz
gunzip ./data.img.gz
# write CM boot image to recovery partition
dd if=./cyanogen.img of=/dev/block/mmcblk0p6
# finish
exit
exit
Now you can reboot your device into recovery mode and see CyanogenMod booting.
Restoring native recovery:
If you got tired from CyanogenMod and/or would like to take back your recovery, please use the backup you've done before. Lets say it is placed on your external sdcard, then connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to the folder with recovery backup
cd /mnt/extSdCard
# write recovery image over recovery partition
dd if=./recovery.img of=/dev/block/mmcblk0p6
Please let me know If I missed anything in my steps.
P.S. What I've changed in Cyanogen boot.img to make it using img files instead of partitions in form of patch: View attachment cyanogen_boot_img.patch. It is also necessary to create /host folder in initrd folder tree.
wow!!
it's really hard to be done xD
i thought it will be as easy as it was on my old Galaxy S2
all what i needed to do is to restart the phone and press home to boot to second Rom
i hope it's going to be easier soon
and thank you for you efforts toward our device Development
MoNsTeRmUk said:
wow!!
it's really hard to be done xD
Click to expand...
Click to collapse
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
X-Stranger said:
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
Click to expand...
Click to collapse
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
MoNsTeRmUk said:
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
Click to expand...
Click to collapse
Thanks for kind words Actually you don't need to have the computer to change ROM, you can type commands from terminal emulator directly from Android. I'm also thinking about creating small Android app which can be installed to each ROM and will be able to switch boot partition within one click.
Thanks for this superb work. Can't download last file ?
Please if can make someone flashable zip it would be great I am a noob but I want try this thanks again
Sent from my GT-N8000 using Tapatalk HD
other roms
Can I do this this with another rom
maro_X said:
Can I do this this with another rom
Click to expand...
Click to collapse
It is possible, but your another rom must be specially modified for this.
What rom are you talking about exactly?
Multi-boot solution
I've tired of writing images to boot partition every time I want to switch between native firmware and Cyanogen, so decided to compose a little program that I was talking before. So let me introduce you N8xx Boot Manager!
The idea:
You put your boot images files to some folder on your sdcard, lets say to /mnt/extSdCard/images/boot
And recovery boot images to /mnt/extSdCard/images/recovery
Now you run Boot Manager and select what you want to boot as normal boot or as recovery
As soon as you selected it, the application asks you if you would like to write this image to the appropriate partition (boot or recovery)
After successful writing it will ask you for booting from that partition, e.g. propose to reboot into your another rom or recovery
For sure all the settings like path where to keep images and boot/recovery partition names can be fixed appropriately to your device at the Settings tab
For sure the application requires root permissions, e.g. your device must be rooted. You can also check this from Settings tab
The application file: View attachment bootmanager-1.0.apk - feel free to install it to your device and use posting me bug reports
P.S. The only thing I've forgotten - the button to create native boot image file backup You still need to do it manually, sorry Hopefully in next release, if there be people interested in N8xx Boot Manager
P.P.S. Generally this program can be used for any device - just put correct images and correct boot partition names
P.P.P.S. Why N8xx and not N8xxx or N80xx? Because I've missed one symbol when typed application name in Android Studio and was too lazy to change that later :laugh:
N80xx Boot Manager
Updated version of N80xx Boot Manager: View attachment bootmanager-1.1.apk
Changelog:
Fixed application name
Fixed images path detection when no settings were changes
Added "Backup boot partiton" and "Backup recovery partition" buttons
Thus, now to install CM 10.2 as dual boot you don't need to go to ADB or terminal - just upload 3 img files to your device proper locations, installl boot manager apk, create stock boot/recovery partitions backup, then select what you want to boot and boot to that rom!
P.S. Going to update first post of this thread with steps based on Boot Manager, just would be nice if someone confirm that it works.
swamimahesh said:
Can't download last file
Click to expand...
Click to collapse
Re-uploaded.
I love u man
Finally alittle love for our device :crying:
Do I have to reinstall apps when booting to cm?
edit: I dont really understand the first step when you extract data and system.img. Can you explain more clearly the procedure?
edit2: did anyone do this dualboot successfully?
data.img.gz
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
netj said:
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
Click to expand...
Click to collapse
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment data.img.gz and let me know if it works for you.
muop_92 said:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
X-Stranger said:
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
Click to expand...
Click to collapse
Where is /mnt ? I saw in my device only /storage/extSdCard
Sent from my GT-I8160 using Tapatalk 2
muop_92 said:
Where is /mnt ? I saw in my device only /storage/extSdCard
Click to expand...
Click to collapse
It's the same. External sdcard is available on both these paths as far as I know. You can change it otherwise in application settings tab.
Ok !
X-Stranger said:
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment 2519204 and let me know if it works for you.
Click to expand...
Click to collapse
Hi,
It's Ok !
Thanks !
I have just modify the paths :
dd if=/dev/mmcblk0p6 of=./recovery.img --> dd if=/dev/block/mmcblk0p6 of=./recovery.img
dd if=./cyanogen.img of=/dev/mmcblk0p6 --> dd if=./cyanogen.img of=/dev/block/mmcblk0p6
:good:
Features:
install zip from sdcard or sideload into system1 or system2
mount and format system1 or system2
fix permissions on system1 or system2
set bootmode to system1 or system2
automatically checks for install-recovery.sh on both systems and asks you if you want to delete them
TrueDualBoot
TrueDualBoot notes:
Enabling or disabling TDB will completely wipe your data-partition. Once enabled your data partition will be VIRTUALLY split which means that both systems together can use the full space of the data-partition.
There are some things which will break TDB:
everything which removes CWM(like Xiaomi Updater App's live install)
ROM's which don't support mount_ext4.sh (I did not see any ROM without support yet)
Changelog:
Code:
2014-07-08:
- update to 6.0.5.0
- fix CWM's recovery updater
2014-05-10:
- update to 6.0.4.8
- enable swipe
2014-03-23:
- kernel change to allow "adb reboot dload"
2014-03-15:
- fix restoring backups with TDB enabled
2014-03-13-2:
- fix error when installing zip's
- unmount data when switching system
2014-03-13:
- update to CWM 6.0.4.7
- use opensource(4.4) kernel
- USB-OTG support
- use global choice for system
- prepare for merge into CM(for official CWM)
2013-11-15
- support 4.4 roms
2013-05-24:
- update to CWM 6.0.3.2
2013-04-13:
- fix flashing modem1
2013-04-06:
- update kernel to fix boot on MIUI since 3.4.5
2013-03-24:
- update to CWM 6.0.3.0
- block access to recovery partition from android
look here for more information: [URL]https://github.com/M1cha/android_bootable_recovery/commit/333f6101e155ebe4e6eba577719fd13680e06c71[/URL]
2013-03-09:
- introduce TrueDualBoot feature
- backup/restore boot1 because it was missing in first release(CHECK YOUR OLD BACKUPS!!)
- show existing images in advanced restore menu only and provide system-selection
- merge upstream commits(from cyanogenmod)
2013-02-22:
first release
=========== IMPORTANT ===========
I removed all builds of CWM, Philz, etc prior 2014-07-08 because
this new version contains a important fix.
Also check the new point "4" in installation notes below.
if you want to make sure everything went well after you booted into your ROM,
open the file /system/bin/mount_ext4.sh and check if there is this line somewhere
at the bottom of the file:
NO_HIDE="$(getprop ro.keep.recovery.partition)"
================================
Download:
http://d-h.st/users/M1cha/?fld_id=11289#files
Sourcecode:
https://github.com/M1cha/android_bootable_recovery/tree/cm-10.1
Donate:
I do this just for fun but if you like my work it would be great if you want to spend me a beer
Installation:
Download latest recovery-signed-***.zip
if you are on stock recovery: Copy the file as “update.zip” in the root directory of your sdcard
Reboot into recovery and install the zip file
if you come from any other recovery or from CWM pre-2014-07-08, DIRECTLY reboot into recovery again before doing anything else so the dualboot(even without TDB) hook's will be updated.
Final notes:
Please be aware that your phone has only ONE data-partition. If you have TrueDualBoot disabled that means:
You can't install AOSP and MIUI on one phone
If you wipe your data, the settings in both systems will be deleted
Furthermore you shouldn't use the feature of MIUI-Updater app which lets you install during running system. Otherwise you'll have to reinstall CWM after every update.
Bootloader MiRecovery is now locked, installation with fastboot only.
Στάλθηκε από το TPC1057 μου χρησιμοποιώντας Tapatalk
NightHeron said:
Bootloader is now locked, installation with fastboot only.
Στάλθηκε από το TPC1057 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
Small but important correction: RECOVERY is locked.
I think I have read somewhere that there is some kind of updater.
Is there any app to update or do I always have to flash the zip?
CM11 updates CWM with every nightly if u enable this in the Developer settings.
does it cwm touch recovery for Mi2* in plans?
Bucci said:
does it cwm touch recovery for Mi2* in plans?
Click to expand...
Click to collapse
no because it's closed source and CWM isn't maintained by koush anymore.
What do u think about Phil touch recovery?
TDB
About TDB, when System1 & 2 contains the same app, will they use the same folder in data partition to store things which means the app will share the same data in two systems?
Alting said:
What do u think about Phil touch recovery?
Click to expand...
Click to collapse
A old version of this exists already but I don't have time to maintain this.
riowong said:
About TDB, when System1 & 2 contains the same app, will they use the same folder in data partition to store things which means the app will share the same data in two systems?
Click to expand...
Click to collapse
no, I hope this explains it:
{
"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"
}
m11kkaa said:
no, I hope this explains it:
View attachment 2948994
Click to expand...
Click to collapse
Thanks for the partitions layout. I'm new to data_root. Since I will install many many apps in userdata originally, will the storage space be shrinked in using data_root? Or would you mind quote any websites for me to read more about the data_root please?
riowong said:
Thanks for the partitions layout. I'm new to data_root. Since I will install many many apps in userdata originally, will the storage space be shrinked in using data_root? Or would you mind quote any websites for me to read more about the data_root please?
Click to expand...
Click to collapse
data_root root is just a mountpoint.
mountpoints are any folders where you can access the files of a partition. (unlike windows, where u have driver letters like C or D, you bind partitions to folders).
so instead of mounting the data partition to /data TDB mounts it to /data_root.
Then a special linux feature called "bind mount" is used. that just means that instead of mounting a partition to a destination directory, you mount another directory(ANY) to the destination directory.
This way TDB can either bind /data_root/system0 or /data_root/system1 to /data.
if you would insert your NAND as a harddrive to your computer and open the data partition your would see these two folders then.
This means that all the space of the data partition is shared for both systems. there's no fixed line or anything, both together can use all available space.
So may I say when there is the same app called ABC installed in both systems, there will be two folders for this app located in /data partition?
Yep
And may I say the /data_root is mainly to store symbolic links to redirect to /data?
riowong said:
So may I say when there is the same app called ABC installed in both systems, there will be two folders for this app located in /data partition?
Click to expand...
Click to collapse
what i can say from my experience is, that same version apps share the same folder, Tapatalk for example...
Sent from my MI 2 using Tapatalk
riowong said:
And may I say the /data_root is mainly to store symbolic links to redirect to /data?
Click to expand...
Click to collapse
Kind of. It may appear to you as if these were symlinks, but it behaves differently:
when you delete a symlink, the target file still exists.
when you delete a file in a mount-bind, it gets deleted also in the original mount location - because it is the same file, which was just shown on two locations.
---------- Post added at 07:33 PM ---------- Previous post was at 07:26 PM ----------
CBpbxEcmecmBeH said:
what i can say from my experience is, that same version apps share the same folder, Tapatalk for example...
Sent from my MI 2 using Tapatalk
Click to expand...
Click to collapse
Here you talk about "storage" rather than "userdata".
In TDB, the former is shared and the latter is unique for each of the 2 systems.
In other words, the two systems are not completely separated and some apps may have problems (if they put their version dependent data in "storage").
@m11kkaa
We have advanced restore, can we have advanced back-up?
I'm confused about Active partition and Manage partition options. When I install ROM, will it be installed to Active partition?
riowong said:
I'm confused about Active partition and Manage partition options. When I install ROM, will it be installed to Active partition?
Click to expand...
Click to collapse
Nope.
When you boot cwm it asks u which partitions to manage (system1 and system2). Everything you do is on the partition you selected at the start. You can change managed system by choosing it from the first entry. To change boot system you have to go to advanced > boot system and choose the system
Instructions HERE.
TO DO:
- Other things mentioned in the wiki:
https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
VERSION INFORMATION (CHANGELOG)
A newer MATE image is available to download. Download it here or here.
Notes about this release:
v4.0
- Please read the updated instructions.
- Vast performance improvements overall (because it's using mainline 5.12.8 grate kernel).
- It's trickier to get it working, if you cannot follow the instructions please change to v3.0.
v3.0
- Firmware has to be renamed at first boot.
Do the following command as root or using sudo:
Code:
sudo ash rename-firmware.sh
Those who are migrating from older versions or want to know what this .sh file is:
https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
Follow the wiki, look into Wi-Fi section.
Reboot and done.
- Bluetooth is working, but only from terminal.
Code:
sudo hciconfig hci0 up
hcitool scan
hcitool pair, etc etc
- Buttons from trackpad are working, mousepad not yet.
- Updated kernel zip. Latest release here: https://github.com/antonialoytorren...rnel_zip/PostmarketOS-kernel-3.1.10-15-r2.zip
v2.0
- Changed icons (https://github.com/vinceliuice/vimix-icon-theme) and GTK (https://github.com/vinceliuice/vimix-gtk-themes) of XFCE. Now it is a modern XFCE.
- Removed second panel to save space.
- The XFCE Whiskermenu does not close when typing in onboard.
· Other things that will be included in the next release:
- Make a desktop shortcut opening a browser linking this XDA thread.
- Try to get trackpad working
v1.0
- Initial Release
Screenshots
MATE 4.0 (mainline PostmarketOS kernel)
See HERE.
https://imgur.com/a/Sf7BbFt
XFCE 2.0
{
"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"
}
XFCE
MATE
JWM
Dual Booting Android and PostmarketOS
You can only dual boot if you have installed postmarketOS in your microSD or SD Card. If not, you (probably) have to wipe your partition where postmarketOS is located for booting Android again.
Well, the easiest way to do dual boot is this:
In the sdcard folder or whatever folder you want, put the Android ROM zip and PostmarketOS' kernel zip.
Note: Be sure to run the TWRP version 2.8.1.1, otherwise Android won't flash.
The Android ROM (I'm using timduru's ROM: https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496) can be downloaded here: https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip
The PostmarketOS' kernel zip can be downloaded here: https://github.com/antonialoytorrens/TF101-linux-images/raw/master/postmarketOS/kernel_zip/PostmarketOS-kernel-3.1.10-15.zip (has some issues with WiFi, flashing the blob using dd and adb is more recommended, https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101))
If you want Android, go to recovery and flash timduru's ROM.
If you want PostmarketOS, go to recovery and flash my kernel zip (please, disable signature verification when flashing)
Reserved
Reserved
aat596 said:
XFCE
MATE
Click to expand...
Click to collapse
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
be.sign said:
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
Click to expand...
Click to collapse
Having the PostmarketOS system in internal memory is harder and more difficult. You cannot install it on the bigger partition (the 30 GB one), I once tried and almost bricked my tablet because fails to boot due to media/ symlinks.
Unfortunately, you have to install it on /dev/block/mmcblk0p1 (533 MB partition).
I'm trying to make an usable small desktop image for /dev/block/mmcblk0p1 , XFCE is too big for that.
Nevertheless, you can enter recovery mode, do a Factory Reset and wipe Internal Memory to delete Android; then boot Linux from SDCard and use all available space to store your files.
If you want to make your image yourself, please look at https://wiki.postmarketos.org/wiki/Installation_guide and https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
be.sign said:
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
Click to expand...
Click to collapse
EDIT: A mini JWM image is available for download. It has the size to fit in the Asus TF101 first partition (/dev/block/mmcblk0p1). Download here: https://downloads.sourceforge.net/project/tf101-linux-images/postmarketOS/minijwm-postmarketOS-TF101.zip
Then execute exactly the following commands:
Code:
$ unzip minijwm-postmarketOS-TF101.zip
$ cd minijwm-postmarketOS-TF101
$ adb push blob-asus-tf101 /cache
$ adb push minijwm-tf101.img /sdcard
$ adb shell
# dd if=/cache/blob-asus-tf101 of=/dev/block/mmcblk0p4
# dd if=/sdcard/minijwm-tf101.img of=/dev/block/mmcblk0p1
Hello, thanks a lot for your sharing
I have an error with the XFCE image. When in try to boot from an external SDCard, following message occurs : "Initramfs-extras not found".
It work's without any problem when i boot from a custom built flashed on internal storage.
Do you have an idea from the causes ?
Raphzer said:
Hello, thanks a lot for your sharing
I have an error with the XFCE image. When in try to boot from an external SDCard, following message occurs : "Initramfs-extras not found".
It work's without any problem when i boot from a custom built flashed on internal storage.
Do you have an idea from the causes ?
Click to expand...
Click to collapse
This means that initramfs-asus-tf101-extra file is missing from pmOS_boot partition. All files located in this partition are strictly required.
EDIT: Btw, now I have download the XFCE image from sourceforge, flashed it into a new SD Card and boots fine.
aat596 said:
This means that initramfs-asus-tf101-extra file is missing from pmOS_boot partition. All files located in this partition are strictly required.
EDIT: Btw, now I have download the XFCE image from sourceforge, flashed it into a new SD Card and boots fine.
Click to expand...
Click to collapse
I don't understand why it doesn't work with sdcard. I have tried to flash my working build on the sdcard and the same error occurs
No file are missing on the sdcard, very strange.
Raphzer said:
I don't understand why it doesn't work with sdcard. I have tried to flash my working build on the sdcard and the same error occurs
No file are missing on the sdcard, very strange.
Click to expand...
Click to collapse
If it's your own working build then try these steps:
Code:
$ sudo pmbootstrap init (select asus-tf101 device, select [I]none[/I] when prompting graphical interface)
$ sudo pmbootstrap install && sudo pmbootstrap export
$ sudo dd if=/tmp/postmarketOS-export/asus-tf101.img of=/path/of/sdcard status=progress
$ adb push /tmp/postmarketOS-export/blob-asus-tf101 /cache
$ adb shell
# dd if=/cache/blob-asus-tf101 of=/dev/block/mmcblk0p4
And then insert your sdcard and reboot.
Hope this helps. I have extracted it from https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101). The only difference is flashing onto internal memory or the sd card.
EDIT: Are you using a reliable SD Card (Kingston, SanDisk, ...)? It could lead to random errors or not identify it if not.
This is what i did :/
Yep,i used this sdcard on a raspberrypi before.
I think he problem come from partition label name. As i have flash everything on internal memory and sdcard, i have 2 partition named pmos_boot. In the initramfs init script, there is multiple references to label name especially for loading initramfs-extras.
I will do some tests in that way.
Raphzer said:
This is what i did :/
Yep,i used this sdcard on a raspberrypi before.
I think he problem come from partition label name. As i have flash everything on internal memory and sdcard, i have 2 partition named pmos_boot. In the initramfs init script, there is multiple references to label name especially for loading initramfs-extras.
I will do some tests in that way.
Click to expand...
Click to collapse
Yes, it could be the reason. If you run into multiple problems, try to format /system in TWRP and then try it again with only the SD Card.
Btw, what version is your TF101? SBKv1 or SBKv2? I have SBKv1, that could be another problem (but I'm not sure, as the SD Card is partition-independent, and the kernel blob file is compatible for both versions)
Very nice image !
Just tested and looks very promising.
USB mouse and keyboard gets detected but don't work.
oink666 said:
Just tested and looks very promising.
USB mouse and keyboard gets detected but don't work.
Click to expand...
Click to collapse
Yep, that's one of the things mentioned in the TODO list in my guide (look at nearly the end)
We have to compile xf86-mtrack-driver to get it working (there's no such driver in Alpine repos)
I lack a bit of C knowledge to get it working (because it fails when compiling), so help is appreciated
Awesome work.
Any chance of dual boot?
Thank you
riptide981 said:
Awesome work.
Any chance of dual boot?
Thank you
Click to expand...
Click to collapse
You can only dual boot if you have installed postmarketOS in your microSD or SD Card. If not, you (probably) have to wipe your partition where postmarketOS is located for booting Android again.
Well, the easiest way to do dual-boot is this:
In the sdcard folder or whatever folder you want, put the Android ROM zip and PostmarketOS' kernel zip.
The Android ROM (I'm using timduru's ROM: https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496) can be downloaded here: https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip
The PostmarketOS' kernel zip can be downloaded here: https://github.com/antonialoytorrens/TF101-linux-images/raw/master/postmarketOS/kernel_zip/PostmarketOS-kernel-3.1.10-15.zip
If you want Android, go to recovery and flash timduru's ROM.
If you want PostmarketOS, go to recovery and flash my kernel zip (please, disable signature verification when flashing)
XFCE 2.0
A newer XFCE image is available to download. Download it here: https://sourceforge.net/projects/tf101-linux-images/files/postmarketOS/xfce-postmarketOS-TF101-v2.0.zip
A little screenshot:
Notes about this release:
v2.0
- Changed icons (https://github.com/vinceliuice/vimix-icon-theme) and GTK (https://github.com/vinceliuice/vimix-gtk-themes) of XFCE. Now it is a modern XFCE.
- Removed second panel to save space.
- The XFCE Whiskermenu does not close when typing in onboard.
· Other things that will be included in the next release:
- Make a desktop shortcut opening a browser linking this XDA thread.
- Try to get trackpad working
v1.0
- Initial Release
Cool stuff - i tried the latest v2.0 image but ran into some issues:
If I have the keyboard docked it won't boot - it ends up with a blinking cursor top left of the screen and a bunch of errors are shown repeatedly during bootup.
Without the keyboard it boots correctly - keyboard wont work if attaching the keyboard after the system is up.
https://photos.google.com/share/AF1...?key=UUFNdVNfZ3N6X0ZOX054eDJLYWxWd0tPYThCV1dR
Any idea on what I could try to get this going?
gh05tface said:
Cool stuff - i tried the latest v2.0 image but ran into some issues:
If I have the keyboard docked it won't boot - it ends up with a blinking cursor top left of the screen and a bunch of errors are shown repeatedly during bootup.
Without the keyboard it boots correctly - keyboard wont work if attaching the keyboard after the system is up.
https://photos.google.com/share/AF1...?key=UUFNdVNfZ3N6X0ZOX054eDJLYWxWd0tPYThCV1dR
Any idea on what I could try to get this going?
Click to expand...
Click to collapse
I have just redownloaded zip file from sourceforge and I don't have this problem, so I don't know what it could be...
But there are some questions I would like to ask you:
- Does your keyboard work on Android? You can test it by flashing Timduru's Android image (https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip).
- Have you tried to do your own XFCE from scratch? https://github.com/antonialoytorrens/TF101-linux-images#doing-xfce-from-scratch. Hope this works, otherwise a patch for this kernel is needed.
- By the way, what version is your TF101? SBKv1 or SBKv2? I have SBKv1.