DualBootPatcher
A big thanks to @chenxiaolong for originally creating this wonderful utility.
What is dual booting?
It is like having 2 ROMs installed at once, and you can switch to other ROM without flashing it all over again, your data, stuff everything is preserved.
How to use the patcher?
A quote from the author himself:
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Click to expand...
Click to collapse
For now we dont have Windows executable, so only prefer to use the android app.
How to dual boot?
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
Click to expand...
Click to collapse
App and data sharing?
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
(Hope my analogy didn't suck too much )
Click to expand...
Click to collapse
How do I?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Click to expand...
Click to collapse
Just in case, if the app does not work, use the DualBootUtilities.zip from recovery to switch.
Downloads
App - https://www.androidfilehost.com/?fid=24438995911976818
Utilities - https://www.androidfilehost.com/?fid=24438995911976820
Credits
@chenxiaolong and to all the contributors in this project
XDA:DevDB Information
DualBootPatcher for Samsung Galaxy Star, ROM for the Samsung Galaxy Star
Contributors
corphish, chenxiaolong
ROM OS Version: 4.2.x Jelly Bean
Version Information
Status: Beta
Created 2016-03-11
Last Updated 2016-03-11
Reserved
Info about partitions
Our system partition is large enough to hold both CM10.1 and CM11.
I am currently using CM11 as primary and CM10.1 as secondary ROM.
In any case, one of the ROMs is stock, you may want to install the other on some other partitions.
It is recommended to use stock as primary.
If you are installing any ROM on ext-sdcard, you would need a fast sdcard.
corphish said:
Info about partitions
Our system partition is large enough to hold both CM10.1 and CM11.
I am currently using CM11 as primary and CM10.1 as secondary ROM.
In any case, one of the ROMs is stock, you may want to install the other on some other partitions.
It is recommended to use stock as primary.
If you are installing any ROM on ext-sdcard, you would need a fast sdcard.
Click to expand...
Click to collapse
Just in one day you did it ! you're GREAT corphish !
At all can the system partition hold both of cm12.1 and JB4.1 ? also what about kernel ? will the both of them use the same one or each one uses its individual one ?
This will save a lot of time for me when I want to test cm12.1 as I have to flashed it then restore the one I use :crying:
thanks @corphish
i cant open shared apps menu while on cm11(primary).. and rom menu wont open too in cm10(secondary) but can access shared apps menu
LahKeda said:
Just in one day you did it ! you're GREAT corphish !
At all can the system partition hold both of cm12.1 and JB4.1 ? also what about kernel ? will the both of them use the same one or each one uses its individual one ?
This will save a lot of time for me when I want to test cm12.1 as I have to flashed it then restore the one I use :crying:
Click to expand...
Click to collapse
You will have to check how much space is left in system when on stock. Then calculate accordingly.
And kernel used is different for different ROMs.
aLchiEro_06 said:
thanks @corphish
i cant open shared apps menu while on cm11(primary).. and rom menu wont open too in cm10(secondary) but can access shared apps menu
Click to expand...
Click to collapse
App works perfectly fine on kitkat. But not in jb because it is not able to load libs, I will have a look on it.
corphish said:
You will have to check how much space is left in system when on stock. Then calculate accordingly.
And kernel used is different for different ROMs.
Really ! Ok I will try it !
Click to expand...
Click to collapse
@corphish
That moment, when u helped me to remember about somebody who tried to make multi-boot supporting kernel for gts5282.
And we have the thing now.
---------- Post added at 12:54 PM ---------- Previous post was at 12:53 PM ----------
[/COLOR @corphish
That moment, when u helped me to remember about somebody who tried to make multi-boot supporting kernel for gts5282.
And we have the thing now.
can i instal stock jb 4 .1.2 on my secondary partition? ,, thanks
duck'man said:
can i instal stock jb 4 .1.2 on my secondary partition? ,, thanks
Click to expand...
Click to collapse
you need to patch it's zip first , and if you will use original ..tar file you won't be able to do it !
LahKeda said:
you need to patch it's zip first , and if you will use original ..tar file you won't be able to do it !
Click to expand...
Click to collapse
for primary partition its only working for KK+ right?
duck'man said:
can i instal stock jb 4 .1.2 on my secondary partition? ,, thanks
Click to expand...
Click to collapse
yah
duck'man said:
for primary partition its only working for KK+ right?
Click to expand...
Click to collapse
I don't think so you can flash any ROM in primary one !
LahKeda said:
I don't think so you can flash any ROM in primary one !
Click to expand...
Click to collapse
im using 4.1.2,, it cant instal dualbootpatcher.apk
duck'man said:
im using 4.1.2,, it cant instal dualbootpatcher.apk
Click to expand...
Click to collapse
this app still not usable for jb
How to delete or disable this dual boot
Any way
Hridul P.K said:
How to delete or disable this dual boot
Any way
Click to expand...
Click to collapse
by wiping system/data/cache/dalvik from recovery
Dark Knight Begins said:
by wiping system/data/cache/dalvik from recovery
Click to expand...
Click to collapse
Thanks man
Going to boot cm 11 and cm 12 in external sd
Is there any problem iam gonna face
Or
Can i flash a new cm 12.1 on old cm 12.1
Hridul P.K said:
Thanks man
Going to boot cm 11 and cm 12 in external sd
Is there any problem iam gonna face
Or
Can i flash a new cm 12.1 on old cm 12.1
Click to expand...
Click to collapse
to do a clean install u should wipe things first.
hit d thank button, don't say it
Help me plzzzz..........
I am using gts5282 resurrection remix marshmallow custom ROM and I want dual boot but my kernel is not supported and in the previous link of gts5282 in which the developer has given a link of kernel which supports dual boot. This is the link- http://forum.xda-developers.com/showthread.php?t=2733137.
But the download link was expired so I kindly request you guys who downloaded that kernel to please update that link or just upload that kernel in this blog so that I can flash that kernel . And MY device will also be dual boot supported .Your help will be appreciated :good: .
Mohsin Pathan said:
I am using gts5282 resurrection remix marshmallow custom ROM and I want dual boot but my kernel is not supported and in the previous link of gts5282 in which the developer has given a link of kernel which supports dual boot. This is the link- http://forum.xda-developers.com/showthread.php?t=2733137.
But the download link was expired so I kindly request you guys who downloaded that kernel to please update that link or just upload that kernel in this blog so that I can flash that kernel . And MY device will also be dual boot supported .Your help will be appreciated :good: .
Click to expand...
Click to collapse
It's not necessary just use this tool and it will patch the kernel image for you .
Related
Hello fellas
This guide is just a quick how-to on dual booting. Many people have doubts on how to dual boot on Siyah, because it's something new and perhaps "scary" because they may think it can brick their phone.
___________________________________________
Requirements
A Galaxy S II I9100
3.x Siyah Kernel (3.2.x preferred). For latest version, visit the Siyah Kernel thread
90% charged battery
2.5GB of free space in your internal SD card
Patience
Time
So, do you complete all those requirements? Time to go to action. BUT BEFORE, a brief FAQ in a simplified way, based from this post made by the amazing droidphile
___________________________________________
FAQ
Can I dual boot Ice Cream Sandwich and Jelly Bean?
Yes you can, using Siyah v3.5.2.
1) What is dual booting?
Dual booting is the ability to boot into two different Ice Cream Sandwich-based ROMs (like CM9 and AOKP).
2) How is this done?
This is achieved by sharing the kernel and using a hidden partition in dev/block to store the 2nd ROM's /system and the /sdcard (Internal storage) to store /data and /cache inside a hidden folder (/sdcard/.secondrom)
3) How much does it take to clone a ROM?
It should take around 7 minutes
4) I want to dual boot fasturr. wat do?
When you get the splash screen to choose between ROMs, touch the screen or press volume UP to enter the PRIMARY ROM, and press the Home button or volume down for the SECONDARY ROM.
5) How can I remove the Dual boot and its partitions?
Just use the "Remove 2nd ROM" option in the Dual Boot options menu.
6) If I format my /sdcard, will my second ROM go kaput?
Yep, because you're wiping the folder that contains /data and /cache.
7) Can I dual boot a gingerbread ROM in a ICS ROM?
Niet. No.
___________________________________________
Now, the PROCEDURE
You must flash the Siyah kernel, either with CWM or ODIN
After you have flashed the kernel, reboot and let Android upgrade itself.
All done? Alright, move up to next step!
Download the desired ROM that you want to make it secondary, and place it in a safe place in your internal SD card
After that, reboot to CWM Recovery, and navigate to "Dual Boot options"
You'll see a list of options, namely :
View current status
Clone 1st ROM to 2nd ROM
Clone 2nd ROM to 1st ROM
Swap 1st ROM with 2nd ROM
Swap 2nd ROM with 1st ROM
Remove 2nd ROM
Install 2nd ROM from Internal SD card
Install 2nd ROM from External SD card
Wipe 2nd ROM data/cache
Wipe 2nd ROM dalvik-cache
Fix 2nd ROM permissions
What does each one mean, you ask?
View current status - This option will show you the stats of the dual booted ROM.
Clone 1st ROM to 2nd ROM - This option will copy (clone) the current ROM that you use (for example, CM9) and paste it to the 2nd ROM directory. Takes around 7-20 mins.
Clone 2nd ROM to 1st ROM - This options copies the 2nd ROM (after installed of course) and pastes it to the place where the 1st ROM was, replacing it.
Swap 1st ROM with 2nd ROM - This will swap the 1st ROM with the 2nd ROM, making the Primary ROM -> Secondary ROM and the Secondary ROM -> Primary
Swap 2nd ROM with 1st ROM - This will do the exact opposite of the above option
Remove 2nd ROM - This will completely wipe and remove any 2nd ROM files and folders
Install 2nd ROM from Internal SD card - This option is to flash the ROM to the 2nd ROM directory from the Internal SD card
Install 2nd ROM from External SD card - This option is to flash the ROM to the 2nd ROm directory from the External SD card
Wipe 2nd ROM data/cache - This will wipe the 2nd ROM data and cache. When it's done for the first time, it'll create data.img and cache.img and create the folders inside /sdcard/.secondrom, preparing your phone for the 2nd ROM.
Wipe 2nd ROM dalvik-cache - This will wipe the dalvik cache of the 2nd ROM
Fix 2nd ROM permissions - This will fix the permissions of the 2nd ROM
Select the option Wipe 2nd ROM data/cache. This will prepare your phone to flash the 2nd ROM. It takes around 5-7 minutes.
After having that done, select the option to wipe the dalvik cache.
After all that is done, select either "Install 2nd ROM from Internal SD card" or "Install 2nd ROM from External SD card" depending on the location of your ROM
Wait a few minutes for the flash
Reboot
Press the Home button or volume down to enter the Secondary ROM
___________________________________________
After you have done all that, you're set and you're in the Dual Booting world! I hope that this guide helped you, and if it did, press the thanks button!
___________________________________________
Credits
GokhanMoral - For his amazing kernel
Droidphile - For his great FAQ
Nice. Great for people who are not sure how they going to set up their dual boot option.
Edit: What about mounts and options, where you need to format the /secondrom_cache, /secondrom_system and /secondrom_data when you try to setup the very first time? If this step is not taken, you won't be able to have the option to choose either 1st or 2nd rom. Only subsequent reflashing of 2nd rom, then you just need to wipe 2ndrom cache and data.
Unless Gokhanmoral had changed his kernel, I think this is the most important part.
Please correct me if I am wrong.
Nice tutorial, very clear...
One question: I want to dual boot to a stock ICS rom for use a MHL adapter (resurrection remix dont support it as most of the AOSP/AOKP roms)... appart of that, what uses can you give to dual boot?? I cant imagine more!
whats wrong with this guide which is in the first post of siyah thread if people fail to read the faq prior to doing this instructions are pretty easy anyways even tho your guide is more clearer and pretty lol and you have taken the time to do this you will still get the some old questions beening asked lol.
anyways best wishes to you
Maybe it is time GM gets a section in XDA specifically for Siyah ...
g00ndu said:
Nice. Great for people who are not sure how they going to set up their dual boot option.
Edit: What about mounts and options, where you need to format the /secondrom_cache, /secondrom_system and /secondrom_data when you try to setup the very first time? If this step is not taken, you won't be able to have the option to choose either 1st or 2nd rom. Only subsequent reflashing of 2nd rom, then you just need to wipe 2ndrom cache and data.
Unless Gokhanmoral had changed his kernel, I think this is the most important part.
Please correct me if I am wrong.
Click to expand...
Click to collapse
It seems that kernel was changed recently. What I did for my current dual-booting (used Siyah 3.2.3 that time): Wiped data/cache and dalvik of 2nd rom and just flashed new rom from recovery. I didn't format any partitions and had no problems at all with possibility to choose a rom at boot. Regards
Perhaps you can put in the GUIDE FAQ that step 9 doesn't flash the kernel image if present in the zip. (Assuming that it doesn't flash anything other than the /system and /data partitions correct me if I'm wrong)
The first time I used it I feared that I would mess up because I knew that the zip had the kernel img inside.
Good tutorial, thanks!
Many40 said:
It seems that kernel was changed recently. What I did for my current dual-booting (used Siyah 3.2.3 that time): Wiped data/cache and dalvik of 2nd rom and just flashed new rom from recovery. I didn't format any partitions and had no problems at all with possibility to choose a rom at boot. Regards
Click to expand...
Click to collapse
What about the 1st time when you set up your dual rom? I remember that there were a few people who had written in saying they do not have the option of booting into the 2nd rom after following the method describe by the OP.
g00ndu said:
What about the 1st time when you set up your dual rom? I remember that there were a few people who had written in saying they do not have the option of booting into the 2nd rom after following the method describe by the OP.
Click to expand...
Click to collapse
Belive me I did only what I wrote to you. I did not format any partitions and had no problems at boot at all. (Boot option to choose 2nd rom has been available). To be sure I have asked this afternoon also droidphile (author of very helpful guide and experienced on this topic). This is his answer: http://forum.xda-developers.com/showthread.php?p=26742671 Regards. Happy if helped.
Sent from my GT-I9100 using xda premium
DJBoxer said:
whats wrong with this guide which is in the first post of siyah thread if people fail to read the faq prior to doing this instructions are pretty easy anyways even tho your guide is more clearer and pretty lol and you have taken the time to do this you will still get the some old questions beening asked lol.
anyways best wishes to you
Click to expand...
Click to collapse
My intent was to make it even easier and more accessible/straightforward. My guide is meant for first timers, while that guide is more for people who have basic knowledge, which isn't always the case.
g00ndu said:
Nice. Great for people who are not sure how they going to set up their dual boot option.
Edit: What about mounts and options, where you need to format the /secondrom_cache, /secondrom_system and /secondrom_data when you try to setup the very first time? If this step is not taken, you won't be able to have the option to choose either 1st or 2nd rom. Only subsequent reflashing of 2nd rom, then you just need to wipe 2ndrom cache and data.
Unless Gokhanmoral had changed his kernel, I think this is the most important part.
Please correct me if I am wrong.
Click to expand...
Click to collapse
g00ndu said:
What about the 1st time when you set up your dual rom? I remember that there were a few people who had written in saying they do not have the option of booting into the 2nd rom after following the method describe by the OP.
Click to expand...
Click to collapse
Replying to both of those quotes, wiping data/cache creates data.img and cache.img. GM did a great job on dual booting, now it requires fewer steps.
Not booting second rom!
Hey there its a good tutorial but the problem is that its not booting the second rom! My primary rom is Resurrection Remix v2.0 and I want to dual boot Cyanogenmod 7.2.0 RC3 but I do everything and when I go to boot it and press the home button to boot into the second rom it just displays a blank screen with no boot animation. Any help would be appreciated!
Thank you!
Catley!
Sweet...Siyah
Cool Tutorial...Been using dual ROMS on my GS2 for about a week now...works like a charm...gives a chance to try out all those cool customs ROMS...
Catley said:
Hey there its a good tutorial but the problem is that its not booting the second rom! My primary rom is Resurrection Remix v2.0 and I want to dual boot Cyanogenmod 7.2.0 RC3 but I do everything and when I go to boot it and press the home button to boot into the second rom it just displays a blank screen with no boot animation. Any help would be appreciated!
Thank you!
Catley!
Click to expand...
Click to collapse
Phistachio said:
7) Can I dual boot a gingerbread ROM in a ICS ROM?
Niet. No.
Click to expand...
Click to collapse
It's all in the FAQ/OP...
I currently have VK 4.8 and I was wondering if it's possible to install a stock rom as secondary, XXLPW for istance.
Thanks
pippofiori said:
I currently have VK 4.8 and I was wondering if it's possible to install a stock rom as secondary, XXLPW for istance.
Thanks
Click to expand...
Click to collapse
Currently ICS Sammy and AOSP roms can be dual-booted so it's possible.
If you have .zip CWM flashable rom file:
1. Flash Siyah kernel
2. Flash your rom as 2nd from dual boot CWM menu
If you have .tar Sammy rom file:
1. Flash Siyah kernel
2. Clone 1st rom to 2nd
3. Flash Sammy rom as 1st rom from for example mobile odin - remember not to loose root so when you open rom .tar file then when all partitions are recognized change in odin stock kernel to Siyah.
4. Swap 1st and 2nd roms.
Sent from my GT-I9100 using xda premium
hello,
I want cm9 and the stock rom.. is it the same way to do it? just flash the stock rom as secondary??
yakie996 said:
hello,
I want cm9 and the stock rom.. is it the same way to do it? just flash the stock rom as secondary??
Click to expand...
Click to collapse
Yes, but a way to do that depends whether you have .tar or .zip rom file
Sent from my GT-I9100 using xda premium
Great info and easy to follow, will give it a try and see the results
Hi,
I have Resurrection Remix 2.0 as my 1st ROM with Siyah 3.2.7.2. I'd like to add Slim ROM as a 2nd, but Slim comes with the Fluxi kernal as part of the zip. Will that screw things up?
hi
here is the flashable d855 20d rom
Italy
for 16/32gb
testet
how to :
1.install latest 4.4.2
2.root then install recovery (unlock)
3.(optional , wipe cache,dalvik,system,data,internal)
4.copy to memory then flash through recovery
5.then reboot
6.go to recovery and flash super su
all partitions are stock
rom:
Code:
http://uptobox.com/znwrofiifz9u
http://oceanhost.eu/aowq7vl2h57k/20d_g0dsend313v2.zip.htm
http://ul.to/631f6ec9
md5 :
067651767d3f59cc68673b9bc56a4ee0
supersu:
Code:
http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
Credit:
@cybojenix
@bump! team
@thecubed
Skin1980_autobump script
if you have problem with using internal memory
in cmd type
Code:
adb shell
su
restorecon -v -R /data/media
or
adb shell
su
restorecon -FR /data/media/
It includes 20D bumped kernel or another kernel?
Thank you!
davidep85 said:
It includes 20D bumped kernel or another kernel?
Click to expand...
Click to collapse
Well, if it is Stock, then it should be the original 20D kernel. The OP did not say otherwise.
tobitege said:
Well, if it is Stock, then it should be the original 20D kernel. The OP did not say otherwise.
Click to expand...
Click to collapse
yes
all partitions are stock
mlm1102003 said:
yes
all partitions are stock
Click to expand...
Click to collapse
Can you upload the kernel please ..cos i flashed kdz rom and im not rooted ..my internet too slow to download this rom
rom is not working for me, I have problems with secure boot, like not bumped kernel. restored my backup.
davidep85 said:
rom is not working for me, I have problems with secure boot, like not bumped kernel. restored my backup.
Click to expand...
Click to collapse
tested 10 times
check md5
Code:
9e4082949fdc71da61d8254ccb8d5161
Hi, thank you for the great work! I am on AOSP liquid smooth rom. Is it possible to flash/update only the modem?
chaosnever said:
Hi, thank you for the great work! I am on AOSP liquid smooth rom. Is it possible to flash/update only the modem?
Click to expand...
Click to collapse
the best way to install it
is in first post
install 10n
then install root and recovery(unlock)
then flash the rom
mlm1102003 said:
the best way to install it
is in first post
install 10n
then install root and recovery(unlock)
then flash the rom
Click to expand...
Click to collapse
Entirely clear,
but one thing I am not clear (in general) about the internal SD memory: moving from KitKat to Lollipop ROM by using TWRP recovery should I format the internal SD (or delete all content manually)?
In generally, I didn't understand if there's an incompatibility of data applications residues coming from KitKat that might annoy Lollipop.
Thanks in advance
Romulus76 said:
Entirely clear,
but one thing I am not clear (in general) about the internal SD memory: moving from KitKat to Lollipop ROM by using TWRP recovery should I format the internal SD (or delete all content manually)?
In generally, I didn't understand if there's an incompatibility of data applications residues coming from KitKat that might annoy Lollipop.
Thanks in advance
Click to expand...
Click to collapse
/system format means your Android system is removed
/data format means your apps are erased
/cache format means.. pretty much what it says
That's all what you need for a new ROM. It's called a "clean flash"
A dirty flash would be the above, but without formatting /data. This retains the installed apps and their settings, but it might upset the new system and cause incompatibilities. It's not a recommended move.
But now, if, for some reason (like selling your phone), you'd like to "FULLY wipe" the phone
/data/media fully wipes your visible folders (not system ones, but the one where apps stores data files, photos, images, music etc)
So wiping Data is mandatory? No way to keep the apps, when coming from an older stock rom 10l?
Download link? I tried all links but only ads become in my screen...
thedoginthewok said:
So wiping Data is mandatory? No way to keep the apps, when coming from an older stock rom 10l?
Click to expand...
Click to collapse
Yes, always do when between different Android or ROM versions. Dirty flashing usually only works without issues when upgrading from a ROM version (example) 4.0 to 4.1 etc. But going from Kitkat to Lollipop it is required or the phone may not boot at all. There are obviously plenty of tools to help with backup/restore of apps+settings, but time spent on fresh install well spent compared to fixing issues or doing it all over again later.
Please anyone who downloaded this rom upload the kernel
Hi i have a few questions about this rom
1-is it necessary to install a 4.4.2 rom and then flash this rom or i can clean flash this rom over android HD 4.0 rom that i have right now ?
2-is this rom smooth or it has lags ?
3-how much screen time do u get with this rom?
Thanks in advance
Stupid quesiton, sorry, delete this post.
mlm1102003 said:
hi
rom:
Code:
updating
md5 :
Click to expand...
Click to collapse
Thanks for all, but where is the link
Edit : Link is back... You uploaded 313V2.... What's the difference between V1 and V2 ?????
TeamR said:
Thanks for all, but where is the link
Edit : Link is back... You uploaded 313V2.... What's the difference between V1 and V2 ?????
Click to expand...
Click to collapse
v1 sometime have problem with system ui (it does not load)
v2 just fix that problem
I used F2FS file system on data and cache partition and now its like i have a nexus 6p there is little to no UI lag or even any delay in opening apps.
Used to use F2FS on my previous devices(lg g2, Galaxy S2 and Xperia Z ultra) and man the effect was noticeable from day1, so tried it on this device and guess what it works flawlessly.
Here is a thread for comparition between F2FS vs EXT4(the default one).
So here is guide for you guys its Highly dangerous setup so please follow this if you know how to restore a SoftBrick status.
Caution:--
ONLY FOR CM13 and N based roms which support F2FS, If used on OOS3 or H2OS(mm) it will result in not converting the data/cache partition properly and will end up 0mb partition because of modified twrp used for these roms and you wont be able to be mount your internal memory too.
Backup backup backup. Make sure you take a backup and save it on your pc before performing the steps.
Things you can do to make your life easier:--
Clean flashing of rom is highly recommended but you can try dirty too as it does not touch the system partition but still clean is preferred.
Use ZipMe app to make a zip file for your apps so that installing all those apps becomes easier if coming from clean flash.
Full backup of your internal memory files as this setup formats even your internal memory even if you select only the data partion.
Best stay on stock kernel as there is no mention of any cm13 custom kernel to have f2fs support. They may have but in any thread of these i couldnt find f2fs word anywhere. So stay stock.
Rom compatibility/tried on:--
Exodus.
All cm13 based roms work flawlessly.
LineageOS14
Kernel compatibility:--
Darkbeast
Stock kernel or the one provided by default by the rom.
Yarpin's kernel.
Benschold kernel.
Note:- Please this method has worked on F2FS supported roms only before following any of it make sure your rom developer has incorporated f2fs support in his/her rom.
Steps:--
Use revert2lollipop to revert back to lollipop firmware if you are on OOS3/H2OS and wanna try f2fs.
Download and upgrade your twrp version to latest.
Copy the .img file to your root folder and reboot to twrp select--->Install-->Install images button-->select the new .img file you copied and reboot to recovery.
Format everything including your internal memory.
Go to advance wipe and select cache partition and select repair and change file system, once there select change file system and change it to f2fs and swipe. Images.
Repeat the above step for data partition.
Go to twrp settings and tick rm -rf, this will make your device retain your f2fs system after clean flash of some roms.
Reboot your recovery once and copy back all your data back to your internal memory.
Flash the required modem for your rom and clean flash your rom for the best bug free experience.
Benefit!
PS:- Please if someone daring does use this on another rom and if everything works flawlessly then please post about it, i will add it compatible roms/kernels.
Press thanks if it worked for you and do post about any improvements you saw.
Credits:-
@Androguide.fr
@ opt devs for awesome roms.
@ jrummy Apps for zipme app.
Seems rock solid for me! I'm running AICP Nightlies .... Running great! Getting it all set back up but no issues at all.
jbarcus81 said:
Seems rock solid for me! I'm running AICP Nightlies .... Running great! Getting it all set back up but no issues at all.
Click to expand...
Click to collapse
Ohhh great will add aicp in the compatible ROMs.
BTW are you on stock aicp kernel?
So we need stock kernel
isoladisegnata said:
So we need stock kernel
Click to expand...
Click to collapse
Yeah for now, since for f2fs roms to work properly the kernel also needs to support the file system and no custom kernel has f2fs as a feature mentioned in their list. I couldnt find anything related to f2fs even with the search function, will update the thread if f2fs support is confirmed by the devs of the respective kernels.
chintu1234 said:
Ohhh great will add aicp in the compatible ROMs.
BTW are you on stock aicp kernel?
Click to expand...
Click to collapse
Yeah.. Not using any kernel other than what's built into AICP from the OP.. :highfive:
Added yarpin's kernel to the compatible kernels.
Using AOKP with stock kernel perfectly! Thanks for this OP and also for sharing the ZipMe app! Which is amazing, Didnt work for me on CM13 though but love the idea! JRummy devs make the best apps
Can i use titanium backup to app+data?
isoladisegnata said:
Can i use titanium backup to app+data?
Click to expand...
Click to collapse
Yes you can.
A noob questions:
- How do I put my data in internal sd...?
. I save the internal memory sd on pc before
. will format everything including internal memory.
. change cache and data partition in F2FS...
when I reboot in twrp.. how do I put all data in sd card?..with ROM ..Modem etc..?
is it possible? if I connect the phone to usb..I'll see internal memory?
isoladisegnata said:
A noob questions:
- How do I put my data in internal sd...?
. I save the internal memory sd on pc before
. will format everything including internal memory.
. change cache and data partition in F2FS...
when I reboot in twrp.. how do I put all data in sd card?..with ROM ..Modem etc..?
is it possible? if I connect the phone to usb..I'll see internal memory?
Click to expand...
Click to collapse
Yeah if you connect to PC after conversion you will be able to access your memory as you used to with default system.
Just make sure to wipe system,data,cache,dalvic,internal before going any further for good measure.
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
boulder96 said:
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
Click to expand...
Click to collapse
how it compare with ext4? u see the different?
Sent from my ONE A2003 using XDA-Developers mobile app
Tatsuya_ said:
how it compare with ext4? u see the different?
Sent from my ONE A2003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Honestly I wouldn't notice a difference unless you put 2 phones running ext4 and f2fs side by side for comparison. But if I were to really force an answer out from myself I would say that app opening and switching times are greatly reduced.
you really deserved more thanks for this guide.. keep it up and great work!
boulder96 said:
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
Click to expand...
Click to collapse
Nice! thanks for reporting, will add to OP.
Works great with Exodus ROM !!!
very good. Thank you very much. wonder why only cache and data? What about the system partition?
rakieta said:
very good. Thank you very much. wonder why only cache and data? What about the system partition?
Click to expand...
Click to collapse
It really isnt needed because in system partition most of the time only read function is done while data and cache constantly need read/write functions to be performed so you wont notice anything different if you format system to f2fs.
PixelExperience ROM 2019-12-13
Project ended.
This is BETA version, USE STABLE crDroid or GoogleDroid ROMs.
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA!
It is recommended that you use the latest ugglite Xiaomi firmware. (2019.11.05 Global)
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery) My TWRP: LINK
Boot into recovery
Wipe dalvik, system, data, cust (vendor), cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy any storage)
Flash Magisk Root (Optional)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 1 minute.
Unfortunately all AOSP-based ROMs are still in the test phase, so we wait for a stable OS.
GAPPS included
DOWNLOAD ROM
Made at viethoang18's request. No additional support. I don't like GAPPS!
Know bugs: ?
*
Screenshots: LINK
OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140
ROM info: Q10 system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
Created 2019-12-13 V0 version
Last Updated 2019-12-13
______________________________________________________
Other:
RevengeOS Q10 TWRP backup downloadable in comment section #20 comment. LINK
could you please port revenge os Q
port DU-REX rom please
you need remove flash opengapps optional in pixel experience is just no needed ...
Also impossible to install magisk 20.1 its needed to install latest canary magisk for information ...
it's turn me to fastboot
also twrp not full my screen plz fix it
viethoang18 said:
also twrp not full my screen plz fix it
Click to expand...
Click to collapse
viethoang18 said:
it's turn me to fastboot
Click to expand...
Click to collapse
After I make the final version of the ROM, I install it and when it works I only upload it.
Deleting/formating partitions is important.
TWRP works perfectly for me.
It is recommended that you use the latest ugglite Xiaomi firmware.
I can deal with these after further feedback.
thanks, i will try also can you build more like Evolution X ??
viethoang18 said:
thanks, i will try also can you build more like Evolution X ??
Click to expand...
Click to collapse
These ROMs are all equally bad for the time being, faulty applications, faulty Ui, faulty settings, faulty permissions, etc.
I think unnecessary to try many BETA ROMs for now.
And a lot of unnecessary work.
alright thanks you so much
Hafitz Setya said:
port DU-REX rom please
Click to expand...
Click to collapse
I tried DU-REX.
No messenger in it, I didn't get an SMS today ...
There is no FM radio.
It has GalleryGO but cannot associate it with a contact image... I needed to install another image viewer...
The lights are not working properly. (But this is common in other ROMs.)
Alpha version. But the boot animation is cool...
viethoang18 said:
alright thanks you so much
edit: still goes to fastboot after back Miui with miflash
Click to expand...
Click to collapse
Flash back previous recovery?
szanalmas said:
I tried DU-REX.
No messenger in it, I didn't get an SMS today ...
There is no FM radio.
It has GalleryGO but cannot associate it with a contact image... I needed to install another image viewer...
The lights are not working properly. (But this is common in other ROMs.)
Alpha version. But the boot animation is cool...
Click to expand...
Click to collapse
okey, thanks for you hard work dude
yess
Hafitz Setya said:
okey, thanks for you hard work dude
Click to expand...
Click to collapse
You ask? Packaged?
With Google Photos and Textra Messages have made it quite tolerable. : D
(And with my FMradiofix.)
DU-REX OS
Hafitz Setya said:
okey, thanks for you hard work dude
Click to expand...
Click to collapse
DU-REX OS (TWRP backup) DOWNLOAD
Unzip folder, and copy your phone sdcard or internal storage "/TWRP/BACKUPS/(phone_id)/" folder.
Wipe Data, Cache.
In TWRP -> Restore -> 2019-12-14-DUREX.
Install Textra SMS messages app and Google Photos app if you want messages or contact photos.
Your welcome.
Big +1: In the ROM built-in OpenCamera!
szanalmas said:
DU-REX OS (TWRP backup) DOWNLOAD
Unzip folder, and copy your phone sdcard or internal storage "/TWRP/BACKUPS/(phone_id)/" folder.
Wipe Data, Cache.
In TWRP -> Restore -> 2019-12-14-DUREX.
Install Textra SMS messages app and Google Photos app if you want messages or contact photos.
Your welcome.
Big +1: In the ROM built-in OpenCamera!
Click to expand...
Click to collapse
thanks dude, maybe I'll try tonight, I'm busy now
Please help me, it still go to fastboot
viethoang18 said:
Please help me, it still go to fastboot
Click to expand...
Click to collapse
Which one? Pixel or Durex?
Revenge os 3.0
ahmedhelmy71 said:
could you please port revenge os Q
Click to expand...
Click to collapse
REVENGE OS 3.0 (TWRP backup) DOWNLOAD
Unzip folder, and copy your phone sdcard or internal storage "/TWRP/BACKUPS/(phone_id)/" folder.
Wipe Data, Cache.
In TWRP -> Restore -> 2019-12-16-REVENGEOS.
Install Textra SMS messages app. (Was not SMS notification for me...)
Your welcome.
Screenshots: LINK
@Topser99 has provided us with some newly modified recoveries.
They all have TWRP 3.4 and also now 3.5
⇨NewUpdate
-update kernel
By : @physwizz
Follow : @ULtimaTe_Pie2
Follow Galaxy_A20_official
System and System_root
Twrp-sm-a20 - Google Drive
drive.google.com
Choose .img you want and flash it from your current recovery onto the recovery slot.
Then reboot into recovery.
Or choose the .tar to flash from odin
You must be aware though that your previous backups will not restore .
You should read this next section carefully.
TWRP recovery Incompatability Issue
There are 2 types of recovery:
Type 1 backs up /system
Type2 backs up /system_root but labels it "system"
Both types work well but you can't backup on one type and restore on the other
To overcome this problem, I suggest that filenames of TWRPs should either contain SYSTEM or SYSTEM_ROOT
Also.
TWRP 3.4 is incompatible with TWRP 3.3 and @Topser had modded to produce TWRP 3.4 for us to use.
So now there are 4 types:
1. TWRP 3.3 SYSTEM
2. TWRP 3.3 SYSTEM_ROOT
3. TWRP 3.4 SYSTEM
4. TWRP 3.4 SYSTEM_ROOT
A backup made with one type will not restore with any of the other 3 types.
Post 2
I can confirm TWRP 3.4 SYSTEM version works correctly (including MTP at recovery level). Funnily enough, I just finished porting the A30 version for myself and came up with an almost identical result. I remove the fstab lines for product image, vendor image and system image just to make it cleaner
Thanks for doing this for all @Topser
Whats the difference between system_root and system ?
So this can be installed over 3.3 aswell ?
Jeremy_J7 said:
Whats the difference between system_root and system ?
So this can be installed over 3.3 aswell ?
Click to expand...
Click to collapse
both work as backups.
you can replace 3.3 with 3.4 but read the 1st post carefully
physwizz said:
both work as backups.
you can replace 3.3 with 3.4 but read the 1st post carefully
Click to expand...
Click to collapse
I see now, its labels it differently , thanks alot, will flash it later today . Thanks Bro ?
physwizz said:
both work as backups.
you can replace 3.3 with 3.4 but read the 1st post carefully
Click to expand...
Click to collapse
I just flashed the new recovery, I tested MTP and its working ? I noticed a new option in settings that allows to unmount system before installing a zip, it was enabled by default, I should disable it right ?
Jeremy_J7 said:
I just flashed the new recovery, I tested MTP and its working ? I noticed a new option in settings that allows to unmount system before installing a zip, it was enabled by default, I should disable it right ?
Click to expand...
Click to collapse
It's the default
Topser99 said:
It's the default
Click to expand...
Click to collapse
So you're saying that it's always been the default in TWRP but now we have the option of turning it on/off. And I should leave it enabled ?
Jeremy_J7 said:
So you're saying that it's always been the default in TWRP but now we have the option of turning it on/off. And I should leave it enabled ?
Click to expand...
Click to collapse
Should think of android 4.4 and supersu
Jeremy_J7 said:
So you're saying that it's always been the default in TWRP but now we have the option of turning it on/off. And I should leave it enabled ?
Click to expand...
Click to collapse
I'd leave it as it is.
Try that and then untick it and try that to see what happens
physwizz said:
I'd leave it as it is.
Try that and then untick it and try that to see what happens
Click to expand...
Click to collapse
Ain't got anything to flash at the moment thou ? Maybe will try when a new version of Edxposed comes up.
Jeremy_J7 said:
Ain't got anything to flash at the moment thou ? Maybe will try when a new version of Edxposed comes up.
Click to expand...
Click to collapse
In my understanding
Twrp_3.3 mount system before installing a zip for supersu =>> system/sbin,bin,xbin
Twrp_3.4 unmount system before installing a zip for magisk =>>/data/adb/magisk
@Topser has updated the files on post 1
You can now choose a TWRP to backup data and storage
Jeremy_J7 said:
I just flashed the new recovery, I tested MTP and its working I noticed a new option in settings that allows to unmount system before installing a zip, it was enabled by default, I should disable it right ?
Click to expand...
Click to collapse
It's disabled by default since most things using recovery work systemlessly. Most packages that use the system mount point will automatically mount system for reading and writing anyway. So there's no need to mess with the toggle.
can i flash this tar file on my a205f
A205FXXU8BTG3
shawal_islam said:
can i flash this tar file on my a205f
A205FXXU8BTG3
Click to expand...
Click to collapse
yes
K I back on the scene again and I have a Galaxy A20 I want to root with TWRP!
Heres what I need to know how to the program that installs TWRP and which 3.4 files do I need?
And how will do the install of TWRP I been off 2yrs I just coming back to the website today?
Sorry if this is hard to follow I will post now for ques and feedback. TIA!
techmanc said:
K I back on the scene again and I have a Galaxy A20 I want to root with TWRP!
Heres what I need to know how to the program that installs TWRP and which 3.4 files do I need?
And how will do the install of TWRP I been off 2yrs I just coming back to the website today?
Sorry if this is hard to follow I will post now for ques and feedback. TIA!
Click to expand...
Click to collapse
what do you want to know about Twrp3.4
Topser99 said:
what do you want to know about Twrp3.4
Click to expand...
Click to collapse
Which Odin and TWRP do I need to install my Galaxy A20 as per my sig!