Database Users

[n80xx] CyanogenMod 10.2 Dual Boot

{
"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:

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://docs.google.com/uc?id=0B5c3gpyMBJusXzRfRWg4TXhZdVE&export=download
aromafm_cooper.zip (v1.91)
http://www.upload.ee/files/3959191/aromafm_cooper.zip
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ Touch Recovery for Galaxy Ace, Tool/Utility for the Samsung Galaxy Ace S5830
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-07

:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.

NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary
commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root

Very nice... will try it soon... :good:

Wow this should be great

I tried the recovery and it works. Installation is quick and simple and works just as described. Installing, wiping, backups, touch (up and down) and everything else works just as said. Kudos to you OP!

The last thing I wanna know:
After installing/restoring anything, can you successfully reboot to system?
You should also try Aroma File manager, it's the best part of this recovery.

Gonna Try...

@Bhargav97 i tested it , everything is working but there is one big problem , the recovery cannot reboot to system , it only reboot to recovery ,even if i shut down the device and then boot it , still stuck on recovery
hope you fix it
thanks for your hard work
Sent from my GT-S5830 using Tapatalk

nizar.nasani said:
@Bhargav97 i tested it , everything is working but there is one big problem , the recovery cannot reboot to system , it only reboot to recovery ,even if i shut down the device and the boot it , still stuck on recovery
hope you fix it
thanks for your hard work
Sent from my GT-S5830 using Tapatalk
Click to expand...
Click to collapse
Expect a fix soon!
I was understanding the problem for last few days (because same happens to other two devices also) and finally got the solution and I'll be re-compiling recovery as soon as I get some time.

UPDATE:
-Updated philz recovery sources to 6.23.9 (26.03.2014)
-cm-ota compatibility fixes.
-reboot to system bug is now fixed.
Download link updated in first post.

Am I dreaming? Thanks for revive my old Ace
Sent from my Nexus 5 using XDA Premium 4 mobile app

Bhargav97 said:
UPDATE:
-Updated philz recovery sources to 6.23.9 (26.03.2014)
-cm-ota compatibility fixes.
-reboot to system bug is now fixed.
Download link updated in first post.
Click to expand...
Click to collapse
swipe left and right dont work for me ????

Rhievaldo said:
swipe left and right dont work for me ????
Click to expand...
Click to collapse
Always Read OPs of a thread.
See my post #3, I've already stated that Right/Left swipe won't work yet. We're lucky to at least have a basic touch code implemented in our androidarmv6 sources. It is improving...someday if androidarmv6 developers plan to furnish the recovery touch code, right/left swipe will also be fixed. I can't fix that.

Bhargav97 said:
Always Read OPs of a thread.
See my post #3, I've already stated that Right/Left swipe won't work yet. We're lucky to at least have a basic touch code implemented in our androidarmv6 sources. It is improving...someday if androidarmv6 developers plan to furnish the recovery touch code, right/left swipe will also be fixed. I can't fix that.
Click to expand...
Click to collapse
always read it,, but forgot about that. Sorry... cause read it at 23 march, and try at 30 march..

MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusUkVLRWJ2OVBXak0/edit?usp=sharing

everything seems to be working for me
---------- Post added at 06:43 PM ---------- Previous post was at 06:34 PM ----------
actually, all features work butkeeps rebooting into recovery,, not sure if its a problem restoring a back up ill try installing a new rom
edit,, yes it reboots into recovery no matter what,, damn,, nearly close to perfect

Bhargav97 said:
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusUkVLRWJ2OVBXak0/edit?usp=sharing
Click to expand...
Click to collapse
yes right when i reboot to system it reboot to recovery, the same as the previous time.

There was a little bug which caused issue for rebooting to system. I just fixed it and asked @chraso to compile. So, now finally it's done! Updated first, second and third posts.
Report back for the download link put up on first post.

i've test almost everything and i can say this is the best recovery ever made for ace ✌
thanks for bring it to our ace
sent from my kitkat ACE

[DEV] AoL - Android ON Linux - GM-T810 Edition [CLOSED]

This project is closed due to lack of interest. I'm leaving the files and instructions here for any that want it...
One last present.... See here for a working Arch-AoL MircoSD rootfs.... Just extract it to the ext4 partition of the MicroSD (Step 1) and install the modified kernel (Step 3).
AoL - Android ON Linux - GM-T810 Edition - MicroSD
{
"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"
}
Background
This project was started on the Lenovo Yoga Tab 2 by @ionioni. Over the past couple months he managed to unlock the bootloader and get Linux running natively with Android in the chroot. See his thread here for more details and the real reasons why we would want this. Having Linux in charge makes for a much nicer environment for me. Also having REAL Linux on the go helps with my day to day work.
MicroSD Install of:
AoL - Android ON Linux - GM-T810 Edition
You must be rooted, and have TWRP and Busybox installed
1) Format MicroSD using Linux gparted:
--MAKE SURE IT IS YOUR MICROSD CARD(/dev/mmcblk..) YOU ARE WORKING WITH!!
--Delete all partitions of MicroSD
--Device>>Create partition table - Select ms-dos
--Partition>>New - Select fat32 and the size you want
--Partition>>New - Select ext4 and the rest of the card (suggest ~4-8GB)
--Click the checkmark...
Click to expand...
Click to collapse
2) Install the rootfs on Partition 2 of the MicroSD:
(The following is for an Arch AoL install. Someone else will need to do other Distro's)
**The following is run as root not sudo in a terminal on your Linux PC**
--"su"
--Create and cd into a temp directory
--Download - "wget http://archlinuxarm.org/os/ArchLinuxARM-armv7-latest.tar.gz"
--Download - "wget https://busybox.net/downloads/binaries/latest/busybox-armv7l"
--Download and extract - aol_inits.7z
--Download aol_cold_initramfs.cpio.gz
--cd to root_of_MicroSD_partition2
--"tar -xpvf /path/to/temp_directory/ArchLinuxARM-armv7-latest.tar.gz ."
--"cp /path/to/temp_directory/busybox-armv7l usr/bin/busybox"
--"cp /path/to/temp_directory/aol_inits/init.stage* etc/"
--"chmod a+x usr/bin/busybox etc/init.stage*"
-- "mkdir -p android android/hot android/cold"
--"cd android/cold"
--"gzip -dc /path/to/temp_directory/aol_cold_initramfs.cpio.gz | cpio -idv"
--"cd ../../" (Root of sdcard)
--"rm etc/resolv*"
--"echo "nameserver 8.8.8.8" > resolv.conf"
--"echo "nameserver 8.8.4.4" >> resolv.conf"
--"echo "inet:x:3003:root" >> etc/group"
--"echo "net_raw:x:3004:root" >> etc/group"
--"echo "PermitRootLogin Yes" >> etc/ssh/sshd_config"
--cd out of the MicroSD and do a sync
--Remove MicroSD and place into your tablet
Click to expand...
Click to collapse
3) Installing the aol_kernel:
***YOU MUST DO THIS FIRST***
***Goto SuperSU app and do a "cleanup for reinstall from Playstore"
***Reboot
***DO NOT REINSTALL SuperSU app (or be ready to flash a stock image in ODIN and start all over)
--
--Extract aol_external_sm-t810.7z to /sdcard
--Reboot to TWRP (backup if you wish)
--Install>>Image file
--Select aol_external_sm-t810.img and flash
--Reboot and profit.
Click to expand...
Click to collapse
After AoL boots you will need to log in to ssh localhost, port 22 (Arch install user:alarm pass:alarm) and run the following as root(pass:root):
--"su"
--"gpasswd -a alarm inet"
To go back just need to reflash your old kernel...
If you would like a X11 Desktop (LXDE, XFCE4...) see this thread.... Either use the user alarm or create a new one...
I will be crediting all sources here:
@ionioni - Master Linux/Android chef
@BigBot96 - Rooting tutorial
@ashyx - GTS2 Root, permissive kernel and Recovery Threads, also the permissive custom kernel
Blog @ http://whiteboard.ping.se/Android/Debian - Great hints
@osm0sis - For his AIK
Click to expand...
Click to collapse

Dev Updates
01/17/2016
- Data corruption
At this point the internal installer does its job resizing and creating the needed new partitions. The issue now is the same one I encountered on my first install. The data partition (even if wiped) ends up corrupted. TWRP can't even mount it or fix it. The only solution to fix the error and finish the install process has been to flash the stock recovery. This extra step is not what I want to release to the "public". Until I find a solution I will not be releasing this.
Anyone that "has" to have this installed and doesn't mind the extra 5 minutes of work can PM me and I'll fill you in on the details....
I will release the MicroSD install as it doesn't require any internal partitioning. I will only support Arch at the moment because that is my distro of choice....
12/22/2015
- SUCCESS!!!! AGAIN!!!
After much testing and then a total fail (partitions got corrupted), I now have a working internal AoL install on my tablet. I resized /data (mmcblk0p22) and added 2 new partitions (mmcblk0p23 + 24).
After I work out the kinks in the installer I'll post it. The internal installer will also need a fresh rootfs but I will help with that via a menu driven script similar to my AKBI-TF700 project. It will be better to do the two separately, especially if someone just needs to split their /data partition ( @moonbutt74).
12/16/2015
- SUCCESS!!!!
Apparently AIK was the ticket!!! I also had a bad rootfs (someone somewhere had said to use GPT for the sdcard... GRRR). Arch linux is now in charge and "letting" Android run on my tablet! I have to get the internet working from Linux (systemd issue...) but Android works flawlessly as before. Stay tuned!
EDIT:
- Ok, so I have a working rootfs and a working kernel (thanks to @ashyx (permissive kernel), @moonbutt74 for pointing me to AIK and @osm0sis for making AIK!!!!). I'll be packing up the rootfs as is (simple root and 1 regular user) and anyone who would like to try it shoot me a PM.
I'll run some testing but I'm confident this is a good build. I'll post a rootfs and kernel once at least 2 people PM me and try it... Also eventually my rootfs builder and kernel init's...
My new priority is repartitioning mmcblk0 to add 2 new partitions for Linux to be installed.
EDIT2:
- Posted the install instructions but no files until someone steps up to do a confirming test... Also I decided not to supply any rootfs as it is better (and easy) to build your own fresh.
12/11/2015
- Here is where I am at on the project. I am now setup to compile, pack and unpack successfully the kernel for the SM-T810. Unfortunately (I hate to keep saying that...), any time I modify or replace the ramdisk, it fails to boot. This is what I had thought would be the "easy" way using an externalsd install. All permissions and binaries check out. Grrr.
So, on the advice of my "Master Chef", I'm going to focus on an internal install. This requires taking some space from the /data partition to make 2 new internal partitions. This worked flawlessly on the YT2 and we think that will solve the init issue.
I am going to keep this on hold until @CTXz finishes his port of CM 12.1 to the SM-T710 and he ports CM 12.1 and more importantly CWM-recovery the SM-T810. I need adb access from recovery to do some "safe" initial formatting and the current TWRP does not support adb. Also CM will be a more generic install and will, I think, be more linux friendly...
So to the 350+ observers so far of this project... Stay tuned!
12/8/2015
-I've tried many ways but can't get a kernel to even try to boot. I even tried unpacking ashyx's permissive kernel and repacking it and it won't boot either. I don't have any experience building (or apparently modifying) kernels and no one has stepped up or shown interest. So regretfully this project is on hold. If someone wants to take over feel free to PM me I'll give you everything you need to get an sdcard install running, you just need the "secret" to packing this kernel.
12/7/2015
- So got all my Linux rootfs ducks in a row (binaries and scripts in place). Still can't get the kernel to boot past the first splash... I'm not a kernel man but I guess I'll need to hit the books and see what I can do...

Reserved 2
This one too...

Thank you for your time and effort. I would be happy to test once you get to that in development.
Take care and have a wonderful day.

I went ahead and got an sd install setup. I can't get the kernel to flash in ODIN though. I'm trying to look for information about the kernel build, are they still signed even though the bootloader is unlocked... Probably. I'll have to ask around and find how to sign it...

workdowg said:
I went ahead and got an sd install setup. I can't get the kernel to flash in ODIN though. I'm trying to look for information about the kernel build, are they still signed even though the bootloader is unlocked... Probably. I'll have to ask around and find how to sign it...
Click to expand...
Click to collapse
Unsigned images can be flashed with odin if the bootloader is unlocked.
It's more likely to be something with the way it's been packaged.
How did you repack the boot.img, what is the error in Odin?
Wouldn't it be easier to flash the boot.img with recovery?

ashyx said:
Unsigned images can be flashed with odin if the bootloader is unlocked.
It's more likely to be something with the way it's been packaged.
How did you repack the boot.img, what is the error in Odin?
Wouldn't it be easier to flash the boot.img with recovery?
Click to expand...
Click to collapse
Yes I realize that. There was some there was something wrong with the way I repacked it. It flashed this time but didn't boot. And I do plan on flashing recovery I am just testing and playing around right now. Thank you!
From my LG-G4, Rooted running Stock 5.1

Dev Update
12/7/2015 - So got all my Linux rootfs ducks in a row (binaries and scripts in place). Still can't get the kernel to boot past the first splash... I'm not a kernel man but I guess I'll need to hit the books and see what I can do...
All updates HERE

workdowg said:
12/7/2015 - So got all my Linux rootfs ducks in a row (binaries and scripts in place). Still can't get the kernel to boot past the first splash... I'm not a kernel man but I guess I'll need to hit the books and see what I can do...
All updates HERE
Click to expand...
Click to collapse
@ashyx - Didn't want to bother you with a PM... I tried unpacking and immediately repacking your kernel to test my mod and it doesn't boot either. How is the kernel packed for this device? Thanks.
Edit: I'm thinking it may be the ram base address? Umkbootimg doesn't spit out that on this kernel...
Sent from my SM-T810 using Tapatalk

I've tried many ways but can't get a kernel to even try to boot. I even tried unpacking ashyx's permissive kernel and repacking it and it won't boot either. I don't have any experience building (or apparently modifying) kernels and no one has stepped up or shown interest. So regretfully this project is on hold. If someone wants to take over feel free to PM me I'll give you everything you need to get an sdcard install running, you just need the "secret" to packing this kernel.

Update - 12/11/2015
12/11/2015 - Here is where I am at on the project. I am now setup to compile, pack and unpack successfully the kernel for the SM-T810. Unfortunately (I hate to keep saying that...), any time I modify or replace the ramdisk, it fails to boot. This is what I had thought would be the "easy" way using an externalsd install. All permissions and binaries check out. Grrr.
So, on the advice of my "Master Chef", I'm going to focus on an internal install. This requires taking some space from the /data partition to make 2 new internal partitions. This worked flawlessly on the YT2 and we think that will solve the init issue.
I am going to keep this on hold until @CTXz finishes his port of CM 12.1 to the SM-T710 and he ports CM 12.1 and more importantly CWM-recovery the SM-T810. I need adb access from recovery to do some "safe" initial formatting and the current TWRP does not support adb. Also CM will be a more generic install and will, I think, be more linux friendly...
So to the 350+ observers so far of this project... Stay tuned!

workdowg said:
12/11/2015 - Here is where I am at on the project. I am now setup to compile, pack and unpack successfully the kernel for the SM-T810. Unfortunately (I hate to keep saying that...), any time I modify or replace the ramdisk, it fails to boot. This is what I had thought would be the "easy" way using an externalsd install. All permissions and binaries check out. Grrr.
So, on the advice of my "Master Chef", I'm going to focus on an internal install. This requires taking some space from the /data partition to make 2 new internal partitions. This worked flawlessly on the YT2 and we think that will solve the init issue.
I am going to keep this on hold until @CTXz finishes his port of CM 12.1 to the SM-T710 and he ports CM 12.1 and more importantly CWM-recovery the SM-T810. I need adb access from recovery to do some "safe" initial formatting and the current TWRP does not support adb. Also CM will be a more generic install and will, I think, be more linux friendly...
So to the 350+ observers so far of this project... Stay tuned!
Click to expand...
Click to collapse
How do you repack the boot.img. Usually the kitchen is fault. Try carliv image kitchen. Works almost always.

CTXz said:
How do you repack the boot.img. Usually the kitchen is fault. Try carliv image kitchen. Works almost always.
Click to expand...
Click to collapse
I'll definitely try it...
But I'm almost positive because I'm able to pack and then repack any working kernel it is my changes that aren't being liked... The ramdisk init is actually a shell script and it makes calls for /dev/mmcblk1p2 which may be called something else at boot before Android starts (Android names it /dev/block/mmcblk1p2).

workdowg said:
I'll definitely try it...
But I'm almost positive because I'm able to pack and then repack any working kernel it is my changes that aren't being liked... The ramdisk init is actually a shell script and it makes calls for /dev/mmcblk1p2 which may be called something else at boot before Android starts (Android names it /dev/block/mmcblk1p2).
Click to expand...
Click to collapse
Maybe multirom would be usefull for such cases. If I remember right you can decide what partition to boot from multirom itself. Anyways, i am building CM recovery now to see if I have root access.

Nice utility... He put some work into that... But it still boot loops... Thanks though, it will come in handy.

Hmm CM recovery still saying
33005960dd4672df offline
Guess i'll have to build another recovery then.
I was hoping that selinux was the fault. I will still check the kmsg if it is kernel related.
By the way, realized this right now. I remember getting adb in LPM mode. So while the rom didn't work, instead of reflashing all, I just booted into LPM and from there I had adb. You need to set your default.prop for that.
---------- Post added 12-12-2015 at 12:10 AM ---------- Previous post was 11-12-2015 at 11:52 PM ----------
Ok little update here. I got adb working on the stock recovery. There still no root access tough. I'll replace it with a rooted kernel.

CTXz said:
Hmm CM recovery still saying
33005960dd4672df offline
Guess i'll have to build another recovery then.
I was hoping that selinux was the fault. I will still check the kmsg if it is kernel related.
By the way, realized this right now. I remember getting adb in LPM mode. So while the rom didn't work, instead of reflashing all, I just booted into LPM and from there I had adb. You need to set your default.prop for that.
Click to expand...
Click to collapse
The only info I could fine on LPM mode is for mobile sim cards.... What exactly is this you are refering to...
Ok little update here. I got adb working on the stock recovery. There still no root access tough. I'll replace it with a rooted kernel.
Click to expand...
Click to collapse
Sounds like progress... Not for me... well a little bit. I'm not having any issues modifying the default.prop or any .rc script in the ramdisk and repacking so the kitchen is fine. Although they all boot, none of my changes did anything though.

workdowg said:
The only info I could fine on LPM mode is for mobile sim cards.... What exactly is this you are refering to...Sounds like progress... Not for me... well a little bit. I'm not having any issues modifying the default.prop or any .rc script in the ramdisk and repacking so the kitchen is fine. Although they all boot, none of my changes did anything though.
Click to expand...
Click to collapse
With LPM I mean charging mode, with the big battery. Usually it would gain me full adb access but it would take about a min until adb started.

CTXz said:
Hmm CM recovery still saying
33005960dd4672df offline
Guess i'll have to build another recovery then.
I was hoping that selinux was the fault. I will still check the kmsg if it is kernel related.
Click to expand...
Click to collapse
Well I edited the ramdisk on ashax twrp (based on the nexus 9) and before it couldn't find adb devices at all. Now I get the same error you are:
Code:
3300123a6b6982cd offline
Maybe something in the kernel build stopping it from working???

workdowg said:
Well I edited the ramdisk on ashax twrp (based on the nexus 9) and before it couldn't find adb devices at all. Now I get the same error you are:
Code:
3300123a6b6982cd offline
Maybe something in the kernel build stopping it from working???
Click to expand...
Click to collapse
I thought the same. Strangely enough stock recovery seems to wnter adb fine if the flags are set unsecure in the default prop.

Dual/Multi Boot On the OnePlus 3T

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have looked around and haven't seen anyone mention this so I thought I would post about it. I hope others find this useful. I've used this tool on my Galaxy Note 4 to have two different OS's running (mostly due to bluetooth problems on CM, but I digress). This allows the user to dual boot and maintain safetynet with Magisk. I've used this a lot and was really excited to see that it is compatible with this amazing phone!
The thread that caught my interest on the subject (for Note 4): http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
The original thread quoted by @aukhan (for S4, but most of the discussion is here too): http://forum.xda-developers.com/showthread.php?t=2447534
All credit goes to the original developers for this tool, I had nothing to do with its development. This thread is made to troubleshoot our specific device without clogging up their threads for other devices.
Thanks to @aukhan, @rlorange, @chenxiaolong , and other contributors.
Download the Dual Boot Patcher snapshot apk from here. That is the only app that you should need to complete the process. Click on the latest build link and then click on the android file that ends in "snapshot.apk". The snapshots are the recommended version at the moment.
I made a video walkthrough of this process for the Note 4. A lot of it is similar, but I will try to get a new video up for the OP3T when I have time.
Basically you patch all of the .zip files that you would have flashed normally and then you flash them to a new ROM slot. If there are more questions that the video and my more specific instructions below don't answer I'll be happy to answer them or post a better walkthrough if needed.
It should be noted that to switch back and forth you'll need to install the Dual Boot Patcher apk on both ROMs. This does not affect TWRP Recovery.
So far I've only done this once on the 3T and I haven't had any issues. Obviously the 5 second delay is a little annoying when booting between ROMs, but I can get over that. I currently have RR Official installed as my primary with Open Beta 6 as my secondary. Normally the stock ROM is recommended for the primary boot slot, but this seems to work fine.
More Specific Instructions for recommended Data Slot:
1) Download all .zip files that you would flash if you were going to flash the ROM normally (ex. LOS, Gapps, SuperSu, XPosed, kernels, etc)
2) Download the Dual Boot Patcher apk: https://snapshots.noobdev.io/, install it on your phone, set the kernel, and update the ramdisk (ROMs page, three dots on Primary, scroll to bottom)
3) Open Dual Boot Patcher app and tap the three lines in the upper left then select "Patch Zip File"
4) Tap the plus button and find each of the .zip files that you will be flashing. After selecting one make sure to change "Partition Configuration" to "Data slot" and enter a number (be consistent with each file). Push continue.
5) A file browser will now open. Navigate to the place you'd like to save the file and select the location.
6) You may now repeat steps 4 and 5 to add the rest of the zip files
7) Tap the check mark in the upper right to "Patch" all of the .zip files
8) Tap the three lines in the upper left again and select ROMs
-Installation
--Option 1
9) Tap the phone icon in the lower right and push okay
10) Tap the plus button in the lower right and navigate to where you saved your patched files. Select the main ROM (the ROM you want to dual boot to) and tap "keep location" (this will put all data in the location it specified ie /data/multiboot/data-slot-1 for this case)
11) Repeat step 10 until all zips are added in the order you want them flashed (the order is important so get your ROM before your Gapps etc). If you mess up swipe the one that's in the wrong order to the right to remove it from the list
12) Tap the check mark in the upper right. A console should appear and it should virtually flash the ROM as you would expect in TWRP
13) Once it says "x/x completed" in cyan text and it has stopped you can just tap the back arrow in the upper left
14) If you go back to the ROMs page there should now be a "Secondary" ROM. To test it out you'll need to select it and then reboot the phone.
15) Once it has booted and you are past the setup you'll need to enable "unknown sources" in the menu and install Dual Boot Patcher. Once it's installed, open it. It should find the two ROMs and you'll be able to select Primary from the ROMs menu and reboot back
--Option 2 (best if your ROM doesn't report your device name like RR)
9) After patching the files reboot into TWRP
10) Flash the patched files like you would normally flash a ROM (order is important so flash the ROM before Gapps, su, etc)
11) Once the process has completed reboot into system
12) Since you haven't selected the secondary ROM at this point it should boot to your primary ROM (although I can't remember at the moment). Open Dual Boot Patcher, select the ROMs page, select the secondary ROM, and reboot your phone
13) It should reboot to your newly installed ROM where you can set it up and install DBP to boot back between ROMs.
This process can be done using any of the partition configurations listed when patching a Zip file. Secondary and Multi Slots go to the System partition and data slot goes to internal storage. I recommend not using the Multi Slots since more than two ROMs is a lot on the system partition. I would recommend the data slots.
If you have problems make sure to set the kernel and update the ramdisk before flashing
In the event of a bootloop you can recover your primary ROM by entering TWRP, tapping install, selecting image in the bottom right corner, navigating to the /sdcard/MultiBoot/primary folder, and selecting the "boot.img" file. This will return your phone back to the primary ROM.
There is a multiboot.log file that is very useful for debugging. Please post it if you have issues (found in the /sdcard folder)
If you later want to flash anything to the ROM that you're "dual booting" into then all you have to do is patch the zip files and flash them like before except you're flashing to a slot that already has a ROM now.
Tasker Integration
I've been using RR as my daily driver, but the BT doesn't work in my car. I did a lot of research to enable ROM switching in Tasker so that I could easily switch over ROMs when I get into my car. I use my android watch to trigger the task into my OOS ROM and then when BT disconnects I have it trigger a task to switch back to RR. Here it is:
Add action>system>send intent
Under "Action" enter
Code:
com.github.chenxiaolong.dualbootpatcher.SWITCH_ROM
Under "Cat": Default
Under the first "Extra" enter
Code:
rom_id:primary
(change primary to dual or whatever your other slot name is)
Under the second "Extra" enter
Code:
reboot:true
(this tells the app to reboot right after switching the ROM to the desired one)
Under "Target": Activity
I have found that the intent will trigger if the phone is locked, but won't do anything until the phone is unlocked. With swipe or smart lock enabled you can use secure settings to wake the screen and then run a shell with root to swipe up on the lock screen (Command: "input swipe X1 Y1 X2 Y2" replace the X's and Y's with numbers for your screen. Use developer settings to figure out where the start and stop should be.)
All of this allows me to trigger a ROM switch and reboot from my watch without taking my phone out of my pocket (i.e. while driving).
Backup/Restore/Move ROMs from/to specified slots
chenxiaolong said:
Wow, a lot has happened since my midterms started Once midterms are over, I'll start replying to posts here again (starting from around page 731 when I last posted).
I haven't been doing absolutely nothing over the past couple weeks though! We now have a very basic backup and restore implementation. This is still very much a work-in-progress and currently has no UI (nor does it work outside of recovery mode). But anyway, I figured some people who love bleeding edge stuff will want to give this a try. (And yes, backing up one slot and restoring to another already works!)
Like the installer, DualBootUtilities, and pretty much everything multiboot-related, backup and restore is handled by mbtool. I've compiled debug versions here with the new backup & restore features: https://snapshots.noobdev.io/misc/mbtool/mbtool_recovery_8.0.0.r1855.gfeb767e_DEBUG.tar.xz EDIT: Extract "mbtool_recovery" from the PC zip (easier) or from assets/data-8.0.0-rVERSION.tar.xz in the apk.
To give this a try, you'll want make sure your adb command is set up properly and reboot into recovery. Then you'll need to copy the appropriate mbtool_recovery binary to /tmp/:
Code:
# For 32-bit ARM devices
adb push armeabi-v7a/mbtool_recovery /tmp/
# For 64-bit ARM devices
adb push arm64-v8a/mbtool_recovery /tmp/
# For x86/x86_64 Intel devices, you guys probably already know what you're doing
Then, make sure /system is mounted because TWRP does not mount it by default.
Code:
adb shell mount /system
Now, to backup a ROM, run, for example (to backup extsd-slot-cm to a backup named "my_backup_name"):
EDIT: One thing to note because the tool doesn't detect this yet. If you want to backup the primary ROM, make sure to do a ramdisk update from the app first. Otherwise, the kernel will not have any multiboot code and won't boot if you decide to restore it to another slot.
Code:
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery backup -r extsd-slot-cm -n my_backup_name
To restore a ROM, run, for example (to restore "my_backup_name" to multi-slot-1):
Code:
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery restore -r multi-slot-1 -n my_backup_name
If you want to do partial backups (say, backing up the data and kernel only), you can add "-t data,boot" to the command. For more command arguments, see:
Code:
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery backup --help
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery restore --help
I expect there to be a lot of bugs, so feel free to blame me or yell at me for whatever issues you run into
Click to expand...
Click to collapse
Edit: Turns out I didn't look hard enough. There is a thread that has already been created to discuss this tool on this wonderful phone and it fixes an issue where some ROMs with 3/3T support won't flash in dual-boot.

I erroneously did the upgrade ramdisk on my 3t with OxygenOS and now phone is not booting anymore (5 vibration and then recovery)... Someone can help me in understanding what I can do to solve it?

mar.ste said:
I erroneously did the upgrade ramdisk on my 3t with OxygenOS and now phone is not booting anymore (5 vibration and then recovery)... Someone can help me in understanding what I can do to solve it?
Click to expand...
Click to collapse
It has been awhile since I've played with DBP, but I seem to recall that it stores a copy of the boot image before the ramdisk update that you can flash

[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]

{
"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"
}
Fastboot Enhance
What it can do?
- Show fastboot vars
- Switch between fastbootd & bootloader
- Switch between A & B slot
- Flash Payload.bin in fastbootd
- Flash images
- Erase partitions
- Delete logical partitions
- Create logical partitions
- Resize logical partitions
- Unpack Payload.bin
- Extract specific image from Payload.bin
- Show Payload vars
- Show dynamic partition metadata
And above all, it has friendly GUI
Download
Releases · libxzr/FastbootEnhance
A user-friendly Fastboot ToolBox & Payload Dumper for Windows - libxzr/FastbootEnhance
github.com
By using this, you can freely switch between different versions of HydrogenOS & OxygenOS & Custom ROMs.
It is mostly tested on 8T but should work fine on any device shipped with dynamic partitions.

Notes for fastboot visualization
- You need to pre-install related fastboot usb drivers to make sure the device can be recognize by the software.
- Only in fastbootd or bootloader mode can the software recognize your device.

reserved2

I wonder if this would work with kb2007 TMO to go to ColorOS? I will download a check it out, thanks for the contribution!

xzr467706992 said:
Fastboot Enhance
Click to expand...
Click to collapse
Dev
xzr467706992​thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.

mslezak said:
Dev
xzr467706992​thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
Click to expand...
Click to collapse
Disregard I just found your thread

Great job

mslezak said:
Dev
xzr467706992​thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
Click to expand...
Click to collapse
Google has mentioned the copy-on-write(COW) device here
Virtual A/B Overview | Android Open Source Project
source.android.com
For virtual a/b, the COW devices are created during the process of update. When there's enough spaces in super, they'll be created there, otherwise they'll be created in /data/gsi/ota.

xzr467706992 said:
Google has mentioned the copy-on-write(COW) device here
Virtual A/B Overview | Android Open Source Project
source.android.com
For virtual a/b, the COW devices are created during the process of update. When there's enough spaces in super, they'll be created there, otherwise they'll be created in /data/gsi/ota.
Click to expand...
Click to collapse
Yes I found it there for "virtual A/B" just an hour or two ago actually. They don't explain it too well, however.

Please don't mind I have few doubts about how to use this.
1. Suppose I have installed a custom rom and now I want to go back to Oxygen OS, can I do it by flashing the payload.bin using this fastboot enhance tool? If yes, what exact steps I have to go through?
2. If I flash the payload bin using this tool, will my all partitions will be recreated automatically as it was in a fresh stock condition when I used this 8T for first time even if the custom rom did any mess up with size or anything else? Also will it cleanup inactive slot too?

Amsal1 said:
Please don't mind I have few doubts about how to use this.
1. Suppose I have installed a custom rom and now I want to go back to Oxygen OS, can I do it by flashing the payload.bin using this fastboot enhance tool? If yes, what exact steps I have to go through?
2. If I flash the payload bin using this tool, will my all partitions will be recreated automatically as it was in a fresh stock condition when I used this 8T for first time even if the custom rom did any mess up with size or anything else? Also will it cleanup inactive slot too?
Click to expand...
Click to collapse
Yes, you can switch between custom ROMs and OOS using this tool.
This tool will only flash partitions listed in payload.bin, that means other partitions will remain unchanged.
Logical partitions will be automatically resized during flashing.
This tool will not create snapshot & switch slot when flashing, which is different from a normal update or sideload. That means the current slot will be flashed with new images in payload.
Note that on 8T, only the current slot you are using is bootable because of virtual ab, DO NOT SWITCH SLOT.

xzr467706992 said:
Yes, you can switch between custom ROMs and OOS using this tool.
This tool will only flash partitions listed in payload.bin, that means other partitions will remain unchanged.
Logical partitions will be automatically resized during flashing.
This tool will not create snapshot & switch slot when flashing, which is different from a normal update or sideload. That means the current slot will be flashed with new images in payload.
Note that on 8T, only the current slot you are using is bootable because of virtual ab, DO NOT SWITCH SLOT.
Click to expand...
Click to collapse
Thanks for your clarification
So the exact steps to flash any rom(OOS, Custom Rom) would be:
1. Boot to fastbootd mode
2. Load the payload.bin in Fastboot enhance v1.8
3. Click the flash payload.bin
4. Reboot to recovery and wipe
5. Reboot to system
right?

Amsal1 said:
Thanks for your clarification
So the exact steps to flash any rom(OOS, Custom Rom) would be:
1. Boot to fastbootd/bootloader mode
2. Load the payload.bin in Fastboot enhance v1.8
3. Click the flash payload.bin
4. Reboot to system
right?
Click to expand...
Click to collapse
Yes but you need to reboot to fastbootd for logical partitions (also theres hint in software)
Btw remember to enter recovery and wipe data after flashing

xzr467706992 said:
Yes but you need to reboot to fastbootd for logical partitions (also theres hint in software)
Btw remember to enter recovery and wipe data after flashing
Click to expand...
Click to collapse
reboot to fastbootd for logical partitions? I didn't got this.
Sure I will wipe from recovery after flashing the rom!

Amsal1 said:
reboot to fastbootd for logical partitions? I didn't got this.
Sure I will wipe from recovery after flashing the rom!
Click to expand...
Click to collapse
That means: flash payload in fastbootd because we have logical partitions.

xzr467706992 said:
That means: flash payload in fastbootd because we have logical partitions.
Click to expand...
Click to collapse
How can I enter fastbootd mode bro ? Thank you

hieu76pro said:
How can I enter fastbootd mode bro ? Thank you
Click to expand...
Click to collapse
If you are in system
adb reboot fadtboot
If you are in bootloader
Press the "reboot to fastbootd" button in software

xzr467706992 said:
If you are in system
adb reboot fadtboot
If you are in bootloader
Press the "reboot to fastbootd" button in software
Click to expand...
Click to collapse
Thanks bro

I am getting this while trying to flash evo x rom payload.bin:
These are the two cow partitions I found:
Is it safe to delete these two partitions?

Amsal1 said:
I am getting this while trying to flash evo x rom payload.bin:
View attachment 5383121
These are the two cow partitions I found:
View attachment 5383123
Is it safe to delete these two partitions?
Click to expand...
Click to collapse
Yes if system update status is none