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
Related
{
"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?
{
"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
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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is one-of-a-kind multi-boot mod for Oneplus 3. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is encrypted).
MultiROM has 2 parts you need to install:
Modified recovery - You cand download the unified IMG file here, or specific for OP3 from second post and use fastboot or TWRP or Flashify app to flash it.
MultiROM - download the unified ZIP file here, or specific for OP3 from second post and flash it in recovery.
Go into TWRP MultiRom settings and check "Enable No-KEXEC Workaround"
Your current rom will not be erased by the installation.
Download links for specific OP3 version are in the second post.
WORKAROUND for FCs
If you get FC's in your secondary, edit build.prop in that secondary's /system dir and set:
Code:
#ro.sys.sdcardfs=true
...to comment the line (don't delete, don't set to false).
Don't boot before editing this line (flash secondary, edit and then boot).
You can edit in your primary if you are rooted, looking into:
Code:
/sdcard/multirom/roms/<your_sec_rom>/system/build.prop
*You can also try using multiromfix.zip, available in this post, thx to @Startrek852 (to disable sdcardfs support in that secondary).
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/MR-op3/multirom
Modified TWRP - https://github.com/MR-op3/android_bootable_recovery
MultiROM device tree - https://github.com/MR-op3/device_oneplus_oneplus3
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
MultiROM, Tool/Utility for the OnePlus 3
XDA:DevDB Information
MultiROM OP3/3T, Tool/Utility for the OnePlus 3
Contributors
martinusbe, BitOBSessiOn
Version Information
Status: Alpha
Current Beta Version: 3.0.3-2
Beta Release Date: 2017-02-12
Created 2016-07-10
Last Updated 2019-09-10
Reserved
Downloads
IT WILL NOT WORK WHEN ENCRYPTED
How-To by @bihariel
MultiRom for oneplus3
Recovery 08/03 Fixed usb-otg
multirom-20160814-v33b-UNOFFICIAL-oneplus3.zip
uninstaller
Update 11/26
Recovery 11/26
multirom-20161126-v33e-UNOFFICIAL-oneplus3.zip
Update 02/05/2017 op3
for new firmware 4.0.+, so older roms/kernels will not work on this!
AFH folder here
Update 02/20 by @BitOBSessiOn Unified
In post #1183
Update 03/10 Unified By BitOBSessiOn
recovery https://www.androidfilehost.com/?fid=745425885120713897
mr zip https://www.androidfilehost.com/?fid=817550096634752067
Update 08/07 by BitOBSessiOn
Post #1950
Flashable zip to fix your locksettings can be found here
MR Manager TBO 2016/08/17
Multirom Manager apk with oneplus support
Changelog:
- Darkened UI by @daveyannihilation #WhiteUImustDie
- Added icons for OOS, Tipsy, Tesla, Validus, Slim (needs the new zip flashed)
- Supports all Oneplus devices, Redmi2, Lux unoffically (to use the icons, the MR maintainer will need to update his MR zip)
MR Manager TBO 2017/04/21
Multirom Manager apk with added oneplus3T support
Flash recovery
Flash multirom zip
Enable kexec workaround in TWRP mr settings
Enjoy!
Reserved
Please read all about the no-kexec workaround from the author directly, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
*Updated MultiROM Manager APK available here.
*FCs in secondaries should have been fixed in latest TWRP-MROM versions.
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Hello, MultiRom does not recognize the recovery amends
bihariel said:
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Click to expand...
Click to collapse
Its a first build, give me a minute, i have a family
jejemc said:
Hello, MultiRom does not recognize the recovery amends
Click to expand...
Click to collapse
i know
Great work bro :beer: :good:
Unreal work bro much alohas
And here we are!! Thanks a lot @martinusbe, working like a charm!
Superfast! Many thx! Can´t wait to get my oneplus3
Dope. Nice way to use cm13 if I need dash boot into oxygen OS awesome!!
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
cunc-cam said:
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
Click to expand...
Click to collapse
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
bihariel said:
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Click to expand...
Click to collapse
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
cunc-cam said:
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
Click to expand...
Click to collapse
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
bihariel said:
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
Click to expand...
Click to collapse
Huh. Be sure you checked the custom recovery setting related to kexec, I don't think that is supported on our device. Other than that, I'm as clueless as you
Its checked kexec warkaround. Injected sector boot. When i select secondary to boot, the phone reboots but it always goes back to boot menu... Will investigate a bit more...
touchscreen does not work on boot menu
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
bud77 said:
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
Click to expand...
Click to collapse
does touchscreen working for you?
{
"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
xzr467706992thanks 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
xzr467706992thanks 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
xzr467706992thanks 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