Hello, am new here so if I did something wrong please correct me OK
-presentation:
we all love running latest android versions and install big a** games like asphalt 8 and have all the Google apps that we love
But in Janice it's some kind of impossible to do all of that ( come on its only 4 years old!!)
As they say no impossible under the sun now you can easily increase system or data or what ever partition your want just by flashing a Lil file and without losing a single file
-Warning:
Me and XDA are not responsible for any soft hard leaks or what ever you are doing this by your self!!!
Make a full backup(system data boot) before starting..
DO NOT USE THIS FILE WITH ROMS THAT USE CACHE (CM10.2)
-Requirements:
1. Janice or Janice-p(not tested)
2. TWRP Recovery (Any Version)
3. The attached file
Instruction:
1. Download the repartition file
-rename the file with your favorite partition sizes like "lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice.zip" which means 1gb system 2gb sdcard and the rest will go to data partition so you will be able to install more apps
2. Boot into TWRP and make a backup
3. Flash the repartition file of your desire
4. Take a nap or watch big bang theory just waste some time
5. When the script finish restore your backup and reboot
6. Enjoy your games or what ever
-Credit:
1. @Lanchon
2. @madkita
If you want a file with your own sizes just write or in comments and i'll do my best to offer it to you
hi,
thanks for the guide! a couple of comments:
1) i suggest people get REPIT from its main site:
https://github.com/Lanchon/REPIT
the files posted here are already very old, i've updated REPIT several times.
also, i only provide support for the latest version. older versions are unsupported.
2) if you download the files from here, they will not work.
(XDA messes with the filenames changing = for -)
3) you don't need to backup anything unless you want to revert the flashing of the kernel.
4) you don't need to flash any particular kernel to run REPIT, you just need a recent TWRP build.
5) TWRP with gparted is not needed anymore: REPIT now bundles gparted and other tools.
6) the configurations proposed here are incorrect. you should use:
a) if you want 3GB data and rest as internal sdcard:
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
b) if you have an external sdcard, and want 6GB data and a very small internal sdcard:
-system=1.0-data=max-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=0.0625+wipe.zip
then your internal sdcard will be useless. so you need to swap internal and external sdcards as detailed here:
http://forum.xda-developers.com/gal...ment/mod-internal-memory-repartition-t2863629
these configurations will keep contents of system and data. if you don't care about their contents, configure wiping (add '+wipe') for those partitions and REPIT will repartition much faster then.
7) read REPIT manual before using!
https://github.com/Lanchon/REPIT
Lanchon said:
hi,
thanks for the guide! a couple of comments:
1) i suggest people get REPIT from its main site:
https://github.com/Lanchon/REPIT
the files posted here are already very old, i've updated REPIT several times.
also, i only provide support for the latest version. older versions are unsupported.
2) if you download the files from here, they will not work.
(XDA messes with the filenames changing = for -)
3) you don't need to backup anything unless you want to revert the flashing of the kernel.
4) you don't need to flash any particular kernel to run REPIT, you just need a recent TWRP build.
5) TWRP with gparted is not needed anymore: REPIT now bundles gparted and other tools.
6) the configurations proposed here are incorrect. you should use:
a) if you want 3GB data and rest as internal sdcard:
-system=1.0-data=3.0-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=max.zip
b) if you have an external sdcard, and want 6GB data and a very small internal sdcard:
-system=1.0-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=0.0625 wipe.zip
then your internal sdcard will be useless. so you need to swap internal and external sdcards as detailed here:
http://forum.xda-developers.com/gal...ment/mod-internal-memory-repartition-t2863629
these configurations will keep contents of system and data. if you don't care about their contents, configure wiping (add ' wipe') for those partitions and REPIT will repartition much faster then.
7) read REPIT manual before using!
https://github.com/Lanchon/REPIT
Click to expand...
Click to collapse
Thus settings are right this is the same file I used and it worked perfectly and I told you I created this threat for noobs who can't understand github and there download section is not working for me it says "try again in 30 minutes" that's why I use old files
madkita said:
Thus settings are right this is the same file I used and it worked perfectly and I told you I created this threat for noobs who can't understand github and there download section is not working for me it says "try again in 30 minutes" that's why I use old files
Click to expand...
Click to collapse
lol no, without the '-sdcard=...' specifier those files won't work, trust me.
Lanchon said:
lol no, without the '-sdcard=...' specifier those files won't work, trust me.
Click to expand...
Click to collapse
Yeah thank you updated OP
first of all thank you both
just to be sure, i have a couple of questions:
- how much space does a full backup take?
- what is the limit to the repartition? right now i'd like to add one gigabyte to system for apps, which numbers do i need to write in the zip name?
- what does the "wipe preload" and "wipe fota" strings do?
TheSteve87 said:
first of all thank you both
just to be sure, i have a couple of questions:
- how much space does a full backup take?
- what is the limit to the repartition? right now i'd like to add one gigabyte to system for apps, which numbers do i need to write in the zip name?
- what does the "wipe preload" and "wipe fota" strings do?
Click to expand...
Click to collapse
In TWRP it will be around 500-600mb with compression
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice.zip
Just rename the file to this and your will have 1gb system 2gb SD card and the rest well go to data if you want to edit a partition size for example the number 1 after system means the system will be 1gb and the number 2 in front of SD card means the SD card will be 2gb and max in front of data means the rest well go to data partition
Preload and fota are partition used in only stock ROMs and stock based ROMs so if you are running a custom ROM this will give you more space in the partition your set to max
thanks to both devs, i have one question is it compatible with cm13 ?
will i be able to re-size F2fs or i need a EXT4 to use this tool .
i just did everything but i'm not sure it worked
i used this name for the flashable zip
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice
but in system info it still says that data is 3.91GB, and i have 1.84GB for SDcard
maybe i should have gone further and give 3GB to SDcard?
TheSteve87 said:
i just did everything but i'm not sure it worked
i used this name for the flashable zip
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice
but in system info it still says that data is 3.91GB, and i have 1.84GB for SDcard
maybe i should have gone further and give 3GB to SDcard?
Click to expand...
Click to collapse
Yup it works if your wanna check system download a small app called disk info
If you want 3gb on sdcard change the 2 number in front of it this will give you 2gb on data
DaksAnkit said:
thanks to both devs, i have one question is it compatible with cm13 ?
will i be able to re-size F2fs or i need a EXT4 to use this tool .
Click to expand...
Click to collapse
Yup 100%
Make a backup first and when resizing all partitions will be formated to ext4 then restore your backup it will automatically format them to f2fs
ayt man thanks , trying it right away !!
edit : getting error 1 in twrp 3.0.0 on cm13 rom I THOUGHT IT WAS compatible with repit , as said on the GITHUB
also i tried flashing zip from github page of lanchon , that zip also did not worked it said something like couldn`t find meta-inf lanchon REPIT.
??? where did i went wrong i just flashed the zip from twrp it did nt worked i moved the file to /tmp then tried there also same error .
DaksAnkit said:
ayt man thanks , trying it right away !!
edit : getting error 1 in twrp 3.0.0 on cm13 rom I THOUGHT IT WAS compatible with repit , as said on the GITHUB
also i tried flashing zip from github page of lanchon , that zip also did not worked it said something like couldn`t find meta-inf lanchon REPIT.
??? where did i went wrong i just flashed the zip from twrp it did nt worked i moved the file to /tmp then tried there also same error .
Click to expand...
Click to collapse
Cm13 recovery doesn't have parted script you have to use the recovery I provided in first post just follow it
madkita said:
Cm13 recovery doesn't have parted script you have to use the recovery I provided in first post just follow it
Click to expand...
Click to collapse
nope , it says error 1
invalid partition configuration ,.. sdcard : sdcard=max.zip
i flashed the kernel then renamed the file attached to ..
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
something is not right can you please help , i would like to have 1 gb system n 2 or 3gb in data partitions correct me if i am wrong if the size configuration is wrong ?? what should i do.
also so i have to now restore my backup to get back to cm13 coz i am stuck at recovery ? any shortcut,like(flashing cm13 kernel) to go back to system as it was before or i have to restore the backup ?
DaksAnkit said:
nope , it says error 1
invalid partition configuration ,.. sdcard : sdcard=max.zip
i flashed the kernel then renamed the file attached to ..
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
something is not right can you please help , i would like to have 1 gb system n 2 or 3gb in data partitions correct me if i am wrong if the size configuration is wrong ?? what should i do.
Click to expand...
Click to collapse
Use this and don't miss with it
lanchon-repit-20160317-system=1-data=2-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max-janice.zip
madkita said:
Use this and don't miss with it
lanchon-repit-20160317-system=1-data=2-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max-janice.zip
Click to expand...
Click to collapse
Thanks man , i sorted it out the problem was silly , i had checked option in windows to
HIDE EXTENSION NAMES OF KNOWN FILE TYPES , so i was just copying and the .zip kepton adding twice
.zip.zip and that is what was happening anyhow the device has started reparting , so one last question after when this process is over , i just install my backup and that is it ? right !!
DaksAnkit said:
Thanks man , i sorted it out the problem was silly , i had checked option in windows to
HIDE EXTENSION NAMES OF KNOWN FILE TYPES , so i was just copying and the .zip kepton adding twice
.zip.zip and that is what was happening anyhow the device has started reparting , so one last question after when this process is over , i ust install my backup and that is it ? right !!
Click to expand...
Click to collapse
Yup just restore your backup and you're done ?
madkita said:
yup just restore your backup and you're done
Click to expand...
Click to collapse
alrighty then !!
:good:
I`ll post how did it go later in the thread .
you have a good day bro enjoy sunday .. cheers
Can someone here confirm that the kernel cm12.1 (OP) can be installed in the latest CM11 ROM by epirex? And if repit could work after 12.1 Kernel installed in CM11 ROM? Thanks in advance.
TPD-21 said:
Can someone here confirm that the kernel cm12.1 (OP) can be installed in the latest CM11 ROM by epirex? And if repit could work after 12.1 Kernel installed in CM11 ROM? Thanks in advance.
Click to expand...
Click to collapse
First make a backup with your cm11's kernel then flash cm12.1 kernel then flash the script and the kernel doesn't t care about your current rom so it should work every where
Related
Hey,
I read a lot over the last months and am now willing to flash the overcome rom.
Situation:
- Euro Galaxy Tab (german, unbranded)
- Rooted (with z4root)
- Do not want to lose current configuration (backup?)
Step-by-Step:
- As I still use RFS file system, I need to convert first. Besides that, I need a CWM to flash overcome and a SD-Card for the auto-backup.
1. - Flash Modaco Kernel Full to convert file system and to get CWM (with Odin, activate repartition and select Kernel)
3. - Reboot in recovery (CWM) - backup and conversion will be done
2. - Wipe Data (in CWM)
3. - Install instructions from overcome:
INSTALL INSTRUCTIONS
BACKUP first! (The install script WILL wipe your data partition, but NOT your SD cards)
Copy ROM to SD Card.
Reboot into CWM
Choose Install zip from SD Card
Choose zip from SD Card
Install and reboot!
If you're system was not already ext4, on reboot enter recovery mode and the automatic conversion of your file system will happen
Click to expand...
Click to collapse
Is this the way to go? As I nowhere could find some really detailled instructions to flash this, I hope this is all right.
if u follow these instructions everything will work fine! good job on looking this up. i dont mind people asking questions but only after they TRIED finding the answers themselves. i have hope in people again.
You are definately on the right track, but for completeness sake, I have thrown together a tutorial for exactly what you are after. Check it out over here: http://forum.xda-developers.com/showthread.php?t=973402
I hope it is useful to you.
This is a CWM zip which intended purpose is to make creating heimdall one click roms easier.
It will backup partitions using dd and put them in a folder on your internal SD card labeled partition-backup. You can then use these to create heimdall one-click versions of your own rom.
The partitions backed up are as follows:
Captivate Stock based roms:
/system (/dev/block/stl9)
/dbdata (/dev/block/stl10)
/cache (/dev/block/stl11)
kernel (/dev/block/bml7)
modem (/dev/block/bml12)
param.lfs (/dev/block/stl6)
Captivate MIUI/Cyanogenmod based roms:
/system (/dev/block/mtdblock2)
/datadata (/dev/block/mtdblock6)
/cache (/dev/block/mtdblock3)
/radio (/dev/block/mtdblock5)
kernel (/dev/block/mtdblock0)
recovery (/dev/block/mtdblock1)
modem (/dev/block/mtdblock5)
The data partition is not included.
This is not intended to be a backup for your Captivate, although it could be used as one. Again, it's intended for Heimdall rom creation.
For backups, it is preferable to use CWM. I personally, really like the 5.0.2.6 version by mtcarey as it tars up the data rather than dd's the entire partition which saves a lot of space (like the /data partition for example).
DISCLAIMER: I am in no way to be held responsible for what you do to your device. If you use it, whatever the consequences, they are your responsibility.
Now with that being said, this script doesn't do anything destructive but simply copies the partitions to the internal SD card for later use.
Here are the links:
Captivate Stock based - http://db.tt/tPGn42Pi
MIUI/CyanogenMod based - http://db.tt/rwy5WIel
Let me know if you have any issues with the scripts.
My bad...
10 char
b-eock said:
You have to include data on stock ROM's as it will run the check when it installs on reboot... it will fail because of the missing data partition..., so you might wanna put that into the SCRIPT!
Click to expand...
Click to collapse
you will only get the error if you re-partition
b-eock said:
You have to include data on stock ROM's as it will run the check when it installs on reboot... it will fail because of the missing data partition..., so you might wanna put that into the SCRIPT!
Click to expand...
Click to collapse
You don't need /data...
dbdata is the one that gives that error if you re-partition.
Have you given thought to writing a cwm script to backup efs, or adding it to this script?
mrhaley30705 said:
Have you given thought to writing a cwm script to backup efs, or adding it to this script?
Click to expand...
Click to collapse
I could be wrong on this point but as I understand it the IMEI number is contained there so this isn't probably the best idea.
I could add a separate script for it but I will need to confirm that this wouldn't cause issues for people replicating an IMEI number.
I was thinking of using it as a way to backup an efs.
Understood. I'll put one up later today. In the meantime, you can always copy the folder to your sdcard for safe keeping.
backing up of both EFS and Data, would be nice for PERSONAL backups, make a note not to redistribute efs or data in the heimdall one click packages.
any of your passwords/saved information will be in data..... unless you backup data immediately after flashing/pushing apps BUT before android OS setup...
efs is still a DO NOT DISTRIBUTE.
Tried using partition backup and it didn't make the backup file, or i can't find it.
in a folder on your internal SD card labeled partition-backup
Click to expand...
Click to collapse
how long did it take? a while? it should if it did something.
No, just a couple of second.
Edit
Mount system first?
It should take a minute or so to complete. Once done, reboot back into the OS and there should be a folder /sdcard/patition-backup/.
Within this folder you should have multiple images all ending in .rfs. Really they would typically end in .img but I had it save the images using an rfs extention to facilitate things with heimdall as that's what it expects.
What version of Android are you running?
MIUI. 1.11.18 w/Neo 17r18.
TRusselo said:
backing up of both EFS and Data, would be nice for PERSONAL backups, make a note not to redistribute efs or data in the heimdall one click packages.
any of your passwords/saved information will be in data..... unless you backup data immediately after flashing/pushing apps BUT before android OS setup...
efs is still a DO NOT DISTRIBUTE.
Click to expand...
Click to collapse
Agreed. /data has all your personal data and efs has your IMEI. You don't want to distribute either of these. That is primarily why I left them out of the script. Don't forget you can either copy the entire efs folder or just zip it up and save it somewhere off your phone as a backup. If you are just looking to backup the phone, CWM is much more efficient at backing it up, IMO.
mrhaley30705 said:
MIUI. 1.11.18 w/Neo 17r18.
Click to expand...
Click to collapse
Hmmm... I haven't tested it on either MIUI or Cyanogenmod. They may use a different partioning scheme. Can you please copy/paste the response of typing 'mount' from a shell?
( adb shell, then just simply type 'mount' from there )
How's this
Ok, I see the problem. It appears the MIUI and Cyanogenmod use /dev/block/mtdblock* whereas stock Captivate based roms use /dev/block/mmcblk*.
I'll see about making one for your setup.
Thanks for testing this!
No problem.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this File
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Flashable Zips to increase Storage For GT-I9082
Important Notes :
This will delete all your data [ Including your ROM ] BACK THEM UP FIRST
You can't flash any stock-based ROM after re-partitioning unless you go back to stock-partition table ( see post #4 )
Instructions
1. Backup Your EFS , Read More Here
2. Copy <Partition-Size>.Zip and Ex2-Ex4 To your SD card
3. Boot to Recovery [Don't use TWRP] [ CWM 6.0.5.0 Recommened ]
4. Flash <Partition-Size>.Zip [ The Recovery Should Reboot Automatically ]
5. Flash Ex2-Ex4.Zip
6. Flash your ROM / Restore Your ROM Backup (Nandroid)
7. Flash GApps [Optional]
8. Reboot
MUST READ
1. You won't be able to install Lollipop and above ROMs after you flash 6.475GB ( But You will be able to flash Kitkat and lower normally )
2. Don't use Ex2-F2FS.zip unless you know what is F2FS [See The FAQ], And you know a Kernel / Rom That Supports it [K2wl's Cosmic4.4.4 ROM For Example], If you know a kernel then flash it after flashing the ROM immediately otherwise you will get stuck in a bootloop ( or on Samsung Galaxy grand Logo )
Downloads
5.975GB
6.175GB
6.275GB
6.375GB
Ex2-Ex4
Use this one with Caution:
6.475GB
Changelog
20-7-2015 :
Re-added Ex2-Ex4 [ Because Partitions didn't get converted correctly after the merge ]
Cleaned Ex2-Ex4 Code
18-7-2015 :
Re-named The Zips to : 5.975GB, 6.175GB, 6.275GB, 6.375GB And 6.475GB .
Merged Ex2-Ex4.Zip with 5.975GB, 6.175GB, 6.275GB, 6.375GB And 6.475GB ( Now You don't need to Flash EX2-Ex4 )
Cleaned The Code
Removed Ex2-F2FS
30-5-2015:
Named the partitions
29-5-2015:
Added Ex2-F2FS.zip
25-5-2015
Fixed Error (status 127) while Flashing Ex2-Ex4.Zip file
24-5-2015:
Added:
GT-I9082-IncreaseStorage-6.18GB.Zip
GT-I9082-IncreaseStorage-6.28GB.Zip
GT-I9082-IncreaseStorage-6.38GB.Zip
GT-I9082-IncreaseStorage-6.48GB.Zip
24-5-2015:
Initial Release
Frequently Asked Questions
1. Can i use this on Stock android ?
Yes but all your data will be deleted anyway [Including the Stock/Custom ROM] so you'll need to flash a Custom ROM after applying this file and you can't go back to stock android unless you Reset partition Table
2. I want to reset partitions table and go back to stock android
Refer to http://forum.xda-developers.com/showpost.php?p=60931021&postcount=4
3. After i flashed <Partition-Size>.Zip my phone Stuck at Galaxy grand Duos Logo
A. Remove the Battery
B. Put it in the phone again
C. Boot to recovery and Flash Ex2-Ex4 and then flash your ROM
4. I'm getting insufficient storage when i try to install Gapps, what should i do ?
Try to install a Gapps that doesn't use much Space in System Partition
5. Why are there different Files ?
Every file is different in how much it increase the Storage and every file's name is the Final Data Partition Size ( E.g. <Partition Size>.Zip )
6. Why don't i get the Right Storage Size [ E.g when i flash 6.375 i get 5.84 ]
> ROM and GApps take some space from data partition So it appears as 5.84
7. What is F2FS ?
> F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
More interesting improvment by f2fs described here [Must Read]
8. After i flashed Ex2-F2FS.Zip Nothing Happens, Why ?
> You Can't use any Recovery Except Phliz by @k2wl because he Modified it to flash the Zip correctly
9. Why can't i use TWRP to flash this Zip ?
> Because TWRP lacks of “parted” binary required for repartitioning.
Credits
@k2wl For His Guide
@Irwenzhao For His Zip
XDA:DevDB Information
Increase GT-I9082/L Storage, Tool/Utility for the Samsung Galaxy Grand Duos i9082
Contributors
ym123, k2wl, irwenzhao
Version Information
Status: Stable
Current Stable Version: 1.3
Stable Release Date: 2015-05-29
Beta Release Date: 2015-05-24
Created 2015-05-24
Last Updated 2015-07-20
Reserved
Reserved
How to restore a bricked device or how to restore the device if something goes wrong?
FILES REQUIRED : baffin.pit https://basketbuild.com/filedl/devs?dev=rutvikrvr&dl=rutvikrvr/i9082/restore/baffin.pit
Any stock ROM (link for mk3) : https://docs.google.com/file/d/0B80jsFgYZGOhRHJoY200Zktyekk/edit
ODIN: http://forum.xda-developers.com/attachment.php?attachmentid=1751204&d=1361535462
STEP 1 : In the PIT option add .. the baffin.pit AND IN THE PDA OPTION PUT THE FIRMWARE
STEP 2 : HIT START AND ONCE ITS COMPLETE YOUR PHONE SHOULD WORK FINE ...THEN YOU CAN ROOT YOUR DEVICE AND TRY THIS PROCEDURE AGAIN
Not working.Error(status 2)
billclinton70 said:
Not working.Error(status 2)
Click to expand...
Click to collapse
Ext2-Ext4 or GT-I9082-IncreaseStorage ?
Yousef Mohamed said:
Ext2-Ext4 or GT-I9082-IncreaseStorage ?
Click to expand...
Click to collapse
GT-I9082-IncreaseStorage
billclinton70 said:
GT-I9082-IncreaseStorage
Click to expand...
Click to collapse
Did you try the recommended recovery ?
if you didn't please try it and tell me the result
Yousef Mohamed said:
Did you try the recommended recovery ?
if you didn't please try it and tell me the result
Click to expand...
Click to collapse
Yes I did.
I followed the steps 1 to 4
billclinton70 said:
Yes I did.
I followed the steps 1 to 4
Click to expand...
Click to collapse
OP Updated Sorry for making you wait
you might face error status 127 after "done" in Ex2-Ex4
don't freak out its nothing
Yousef Mohamed said:
OP Updated Sorry for making you wait
you might face error status 127 after "done" in Ex2-Ex4
don't freak out its nothing
Click to expand...
Click to collapse
It's working fine now.Increased storage to 5.48GB
Thanks
billclinton70 said:
It's working fine now.Increased storage to 5.48GB
Thanks
Click to expand...
Click to collapse
Its 5.9 originally but ROM and GAPPs take some space from data partition so it appears as 5.48 , anyway I will upload 2 new Zip files one will be 6.1 and the other will be 6.2 or bigger
Yousef Mohamed said:
Its 5.9 originally but ROM and GAPPs take some space from data partition so it appears as 5.48 , anyway I will upload 2 new Zip files one will be 6.1 and the other will be 6.2 or bigger
Click to expand...
Click to collapse
Yes ,I know that.
Will try the other two files:good:
After flashing ur 2 zip files can I restore my back from recovery??
Mehul.S said:
After flashing ur 2 zip files can I restore my back from recovery??
Click to expand...
Click to collapse
Yes you can,that's what I did
billclinton70 said:
Yes you can,that's what I did
Click to expand...
Click to collapse
Ok.. Back up means nandroid back right??
Sent from my GT-I9082 on Resurrection Remix Rom
Mehul.S said:
Ok.. Back up means nandroid back right??
Sent from my GT-I9082 on Resurrection Remix Rom
Click to expand...
Click to collapse
Yes
billclinton70 said:
Yes
Click to expand...
Click to collapse
Well thanks for the help and quick answers.. Sorry to irritate you if I did.. [emoji14]
Sent from my GT-I9082 on Resurrection Remix Rom
Mehul.S said:
Well thanks for the help and quick answers.. Sorry to irritate you if I did.. [emoji14]
Sent from my GT-I9082 on Resurrection Remix Rom
Click to expand...
Click to collapse
It's OK.No problem
Mehul.S said:
Ok.. Back up means nandroid back right??
Sent from my GT-I9082 on
Resurrection Remix Rom
Click to expand...
Click to collapse
You can Make an Nandroid
Or backup them with Titanium Backup
Making Nandroid is better for those who don't want much fuss after flashing Repartition Zip ( if they don't have an Nandroid they will need to set up their phones again and then restore apps from TB/Google Play store which take long time )
I have looked around and haven't seen anyone mention this so I thought I would post about it since I've been using it and thought it was cool. I hope others find this useful.
The thread I'm talking about: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
The original thread quoted by @aukhan: http://forum.xda-developers.com/showthread.php?t=2447534
All credit goes to the original developers for this tool.
Thanks to @aukhan, @rlorange, @chenxialong, and other contributors.
Download the first .apk (Dual Boot Patcher). That is the only app that you should need to complete the process. A video guide is posted by @aukhan here: https://www.youtube.com/watch?v=h_i3GW_s-VE&spfreload=10
That is the best walkthrough I've seen.
Since it was requested, I've made a video walkthrough of this process: https://youtu.be/5VzYED1hhUA
Basically you patch all of the .zip files that you would have flashed normally and then you flash them to a new ROM slot. If there are more questions that the video doesn't answer I'll be happy to answer them or post a better walkthrough if needed.
It should be noted that to switch back and forth you'll need to install the Dual Boot Patcher apk on both ROMs. This does not affect TWRP Recovery.
I have run this with JasmineROM as the primary and CM13 as the secondary as well as CM13 as primary and JasmineROM as Secondary. I currently have this set-up to try different ROMs without needing to completely wipe my phone and deal with backups/restores. I also use it to use CM13 as my primary while having stock options (S-Pen, Car BT, and other Samsung stuff) available in a quick reboot.
Edit:
More Specific Instructions:
1) Download all .zip files that you would flash if you were going to flash the ROM normally (ex. CM13, Gapps, SuperSu, XPosed, datafixes, kernels, etc)
2) Download the Dual Boot Patcher apk: https://snapshots.noobdev.io/ and install it on your phone
3) Open ES File Explorer or another Root Explorer app and navigate to /sdcard/MultiBoot
4) Create a folder labeled "dual" in that directory (now there is a folder /sdcard/MultiBoot/dual)
5) Open Dual Boot Patcher app and tap the three lines in the upper left then select "Patch Zip File"
6) Tap the plus button and find each of the .zip files that you will be flashing. After selecting one make sure to change "Partition Configuration" to "Secondary"
7) A file browser will now open. Navigate to /sdcard/MultiBoot/dual and save the patched zip file there.
8) You may now repeat steps 6 and 7 to add the rest of the zip files
9) Tap the check mark in the upper right to "Patch" all of the .zip files
10) Tap the three lines in the upper left again and select ROMs
11) Tap the phone icon in the lower right and push okay
12) Tap the plus button in the lower right and navigate to the /sdcard/MultiBoot/dual folder. Select the main ROM (CM13, Kyubi, JasmineROM, etc) and tap "keep location"
13) Repeat step 12 until all zips are added in the order you want them flashed (the order is important). If you mess up swipe the one that's wrong to the right to remove it from the list
14) Tap the check mark in the upper right. A console should appear and it should virtually flash the ROM as you would expect in TWRP
15) Once it says "x/x completed" in cyan text and it has stopped you can just tap the back arrow in the upper left
16) If you go back to the ROMs page there should now be a "Secondary" ROM. To test it out you'll need to select it and then reboot the phone.
17) Once it has booted and you are past the setup you'll need to enable "unknown sources" in the menu and install Dual Boot Patcher. Once it's installed, open it. It should find the two ROMs and you'll be able to select Primary from the ROMs menu and reboot back
Edit 2:
This process can be done using any of the partition configurations listed when patching a Zip file. Secondary and Multi Slots go to the System partition, data slot goes to internal storage, and Extsd slot goes to the External SD card. I recommend not using the Multi Slots since more than two ROMs is a lot on the system partition.
If you have problems make sure to set the kernel and update the ramdisk before flashing and that the files are in the right folder typed exactly as it says in the prompt when patching the file.
I have noticed many problems when using a non-Touchwiz ROM as stock and trying to dual boot to a Touchwiz ROM. I have had bootloop situations when trying to dual boot to Kyubi or PaulPizz from CM13, but with PaulPizz as primary I have no issues switching back and forth.
In the event of a bootloop you can recover your primary ROM by entering TWRP, tapping install, selecting image in the bottom right corner, navigating to the /sdcard/MultiBoot/primary folder, and selecting the "boot.img" file. This will return your phone back to the primary ROM.
Edit 3: Video Tutorial: https://youtu.be/5VzYED1hhUA
If it is too blurry I can make another one, but I think you can see what you need to just fine. I hope it helps. I also forgot to mention that if you later want to flash anything to the ROM that you're "dual booting" into then all you have to do is patch the zip files and flash them like before except you're flashing to a slot that already has a ROM now.
Edit 4: I have now tested this on Marshmallow with success. I still recommend using a Touchwiz ROM as primary and you'll need to have a kernel that's permissive. I'm using Emotion, but I think Oscar's kernel should work as well. I have PaulPizzRom.VRU2CPF3.r-2 installed as primary with the CPF3 modem and Emotion kernel and CM13 as secondary (pretty much my daily driver at this point). Everything has been working so far.
Isn't there a kernel patch requirement for this to work?
Just tried it and working great for me. Jasmine primary, cm13 secondary. Definitely easier than messing with twrp to test roms. Thanks for the info!
jal3223 said:
Isn't there a kernel patch requirement for this to work?
Click to expand...
Click to collapse
I didn't need one to get this to work. You may be thinking of Multisystem, which is different and requires both ROMs to run the same kernel.
As far as I can tell this method boots each ROM with its own kernel. CM13 and JasmineROM both use a version of the Multisystem kernel, but I just checked and they are running different kernels.
I'll probably try the PaulPizz or Kyubi ROMs since I've been having some freeze issues with JasmineROM and see if the others work just as well.
shadeau said:
I didn't need one to get this to work. You may be thinking of Multisystem, which is different and requires both ROMs to run the same kernel.
As far as I can tell this method boots each ROM with its own kernel. CM13 and JasmineROM both use a version of the Multisystem kernel, but I just checked and they are running different kernels.
I'll probably try the PaulPizz or Kyubi ROMs since I've been having some freeze issues with JasmineROM and see if the others work just as well.
Click to expand...
Click to collapse
Awesome, thanks! I'm definitely going to give it a try.
I cannot seem to get it to recognize the path with the patched ROM file. none of the storage paths on my device show as "sdcard", they are either sdcard0 or ExtSdCard.
Even though the folder structure is created on the Internal storage, the DualBoot app does not recognize it.
EDIT: Nevermind, I realized I do not need that app. I just patched the ROM and then added it in the Patcher app mentioned above. The added the patched ROM to it and it shows up in the ROMs menu
EDIT2: This is just not working, I try and apply the ROM for dual boot/swap, however it fails to complete the configuration. I am on a rooted stock phone..could that be the issue?
jal3223 said:
Awesome, thanks! I'm definitely going to give it a try.
Click to expand...
Click to collapse
I just wanted to give an update and say I tried Kyubi ROM the other day and got it to boot just fine. I had one time where I needed to pull the battery, but then it rebooted to Kyubi and ran normally. I don't know if that was just bad luck or something else. I'm planning on trying PaulPizz's ROM today.
ssb13 said:
I cannot seem to get it to recognize the path with the patched ROM file. none of the storage paths on my device show as "sdcard", they are either sdcard0 or ExtSdCard.
Even though the folder structure is created on the Internal storage, the DualBoot app does not recognize it.
EDIT: Nevermind, I realized I do not need that app. I just patched the ROM and then added it in the Patcher app mentioned above. The added the patched ROM to it and it shows up in the ROMs menu
EDIT2: This is just not working, I try and apply the ROM for dual boot/swap, however it fails to complete the configuration. I am on a rooted stock phone..could that be the issue?
Click to expand...
Click to collapse
I added some better instructions in the OP. Can you tell me what step you're having problems with? JasmineROM is pretty close to stock so I assumed this would work just as well on the PaulPizz or stock ROM, but I personally haven't tried on either yet.
shadeau said:
I just wanted to give an update and say I tried Kyubi ROM the other day and got it to boot just fine. I had one time where I needed to pull the battery, but then it rebooted to Kyubi and ran normally. I don't know if that was just bad luck or something else. I'm planning on trying PaulPizz's ROM today.
I added some better instructions in the OP. Can you tell me what step you're having problems with? JasmineROM is pretty close to stock so I assumed this would work just as well on the PaulPizz or stock ROM, but I personally haven't tried on either yet.
Click to expand...
Click to collapse
I'll give it a try with the more specific steps. I think part of my issue was all the videos and other walk-throughs are with older versions of the software. I was also trying to use the other Dual Boot app that is in the other posts....that is where I had the path name issue.
I was finally able to get CM13 on the list of ROMs, however it would fail to switch to it....but that was using the Win32 app to patch it. I'll try it all with the phone app.
ssb13 said:
I'll give it a try with the more specific steps. I think part of my issue was all the videos and other walk-throughs are with older versions of the software. I was also trying to use the other Dual Boot app that is in the other posts....that is where I had the path name issue.
I was finally able to get CM13 on the list of ROMs, however it would fail to switch to it....but that was using the Win32 app to patch it. I'll try it all with the phone app.
Click to expand...
Click to collapse
I followed it to the T and here was my result...(screenshot attached)
EDIT: Added log file. Seems like perhaps it is either permissions, path, and or space issues.
ssb13 said:
I followed it to the T and here was my result...(screenshot attached)
EDIT: Added log file. Seems like perhaps it is either permissions, path, and or space issues.
Click to expand...
Click to collapse
I'll have to look at it tomorrow when I have time. You said you were on stock. What exactly are you running on your phone? What are the firmware version and the kernel? Also, how much free space is on your internal storage and are you using an SD card?
shadeau said:
I'll have to look at it tomorrow when I have time. You said you were on stock. What exactly are you running on your phone? What are the firmware version and the kernel? Also, how much free space is on your internal storage and are you using an SD card?
Click to expand...
Click to collapse
14gb free. About 40gb free on SD card.
Stock 5.1.1 bpa1.
Xceed kernel
Sent from my SM-N910V using Tapatalk
ssb13 said:
14gb free. About 40gb free on SD card.
Stock 5.1.1 bpa1.
Xceed kernel View attachment 3739482
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Try deleting all of the patched zip files and starting over. In the ROMs menu tap the three dots on the primary ROM and scroll down to the bottom. Update the ramdisk and set the kernel then reboot. Make a new folder in the sdcard/MultiBoot folder labeled "data-slot-1" all lowercase. Patch your .zip files and instead of selecting secondary select "Data Slot" and when it asks you what slot name, type "1". After tapping continue, navigate to the sdcard/MultiBoot/data-slot-1 folder and save the .zip files there. After the first time you should be able to select "1 (Data Slot)" for partition configuration instead of manually assigning one for subsequent .zips. Once you're done patching the files go back to the ROMs page and add a ROM then the .zips (selecting keep location like before) and see if that works.
The dual slot saves all ROM data to your system partition which could be pretty full even if your internal storage shows plenty of space. Since all apps are still on the system partition regardless of which slot you pick it may be good to look at how much free space is left before flashing. You can see how much space is left by tapping "Free Space" underneath the "Patch Zip File" button. The /system directory is your system partition.
shadeau said:
Try deleting all of the patched zip files and starting over. In the ROMs menu tap the three dots on the primary ROM and scroll down to the bottom. Update the ramdisk and set the kernel then reboot. Make a new folder in the sdcard/MultiBoot folder labeled "data-slot-1" all lowercase. Patch your .zip files and instead of selecting secondary select "Data Slot" and when it asks you what slot name, type "1". After tapping continue, navigate to the sdcard/MultiBoot/data-slot-1 folder and save the .zip files there. After the first time you should be able to select "1 (Data Slot)" for partition configuration instead of manually assigning one for subsequent .zips. Once you're done patching the files go back to the ROMs page and add a ROM then the .zips (selecting keep location like before) and see if that works.
The dual slot saves all ROM data to your system partition which could be pretty full even if your internal storage shows plenty of space. Since all apps are still on the system partition regardless of which slot you pick it may be good to look at how much free space is left before flashing. You can see how much space is left by tapping "Free Space" underneath the "Patch Zip File" button. The /system directory is your system partition.
Click to expand...
Click to collapse
Thank, I will try this method. I did check and the /raw/system partition is full. Should it be?
ssb13 said:
Thank, I will try this method. I did check and the /raw/system partition is full. Should it be?
Click to expand...
Click to collapse
My system partition says "Total size: 3.94 GiB, Free: 569.43 MiB" and that's with CM13 on Primary and PaulPizz on Secondary with Kyubi on data-slot-1. I haven't booted Kyubi yet so that may decrease my free space even further, but if your system partition is already full I don't think you'll be able to flash anything. You might try looking for big files in the /system directory. Also check to see if there are any files in /system/multiboot/dual and delete them. Do you have a lot of apps installed?
shadeau said:
My system partition says "Total size: 3.94 GiB, Free: 569.43 MiB" and that's with CM13 on Primary and PaulPizz on Secondary with Kyubi on data-slot-1. I haven't booted Kyubi yet so that may decrease my free space even further, but if your system partition is already full I don't think you'll be able to flash anything. You might try looking for big files in the /system directory. Also check to see if there are any files in /system/multiboot/dual and delete them. Do you have a lot of apps installed?
Click to expand...
Click to collapse
Mine says 56K free. Maybe I should revert to my nandroid which is pre-dualboot attempts and see. However I am on stock , rooted. Not even ROM, just the a rooted converter retail to DE. So perhaps the stock uses more system space.
ssb13 said:
Mine says 56K free. Maybe I should revert to my nandroid which is pre-dualboot attempts and see. However I am on stock , rooted. Not even ROM, just the a rooted converter retail to DE. So perhaps the stock uses more system space.
Click to expand...
Click to collapse
That might be a good option. If I tap the three dots for each of my ROMs the PaulPizz (essentially stock) lists a system size of 2.09 GiB, which is half the size of the system partition. You might want to check yours and see what it lists as the system size.
You might also just try using the data-slot-1 and see if it works before the nandroid revert.
shadeau said:
That might be a good option. If I tap the three dots for each of my ROMs the PaulPizz (essentially stock) lists a system size of 2.09 GiB, which is half the size of the system partition. You might want to check yours and see what it lists as the system size.
You might also just try using the data-slot-1 and see if it works before the nandroid revert.
Click to expand...
Click to collapse
Using data-slot-1 I received an exit code of 0 and a 2/2 completed!!!
I cannot reboot now because I am waiting for a phone call, but when I do I'll report in. :highfive:
ssb13 said:
Using data-slot-1 I received an exit code of 0 and a 2/2 completed!!!
I cannot reboot now because I am waiting for a phone call, but when I do I'll report in. :highfive:
Click to expand...
Click to collapse
So that did work. Now I have a follow up question. Say I flash a ROM, like CM13 and GAPPS...but when I boot a bunch of apps keep FC'ing and they keep relaunching, like the SetupWizard...basically I'm stuck clicking OK on all the messsages and they just keep coming back.
My question...am I stuck? How can I flip back to booting to my primary ROM? can I delete the files from the data-slot-1 folder? Any thoughts?
ssb13 said:
So that did work. Now I have a follow up question. Say I flash a ROM, like CM13 and GAPPS...but when I boot a bunch of apps keep FC'ing and they keep relaunching, like the SetupWizard...basically I'm stuck clicking OK on all the messsages and they just keep coming back.
My question...am I stuck? How can I flip back to booting to my primary ROM? can I delete the files from the data-slot-1 folder? Any thoughts?
Click to expand...
Click to collapse
It's actually pretty easy to revert back with TWRP. I was going to add this to the OP when I had time: Boot to recovery and tap install, then select image in the bottom right and navigate to /system/MultiBoot/Primary and select the boot.img, then flash it to the boot partition. That will let you boot to the primary ROM.
shadeau said:
It's actually pretty easy to revert back with TWRP. I was going to add this to the OP when I had time: Boot to recovery and tap install, then select image in the bottom right and navigate to /system/MultiBoot/Primary and select the boot.img, then flash it to the boot partition. That will let you boot to the primary ROM.
Click to expand...
Click to collapse
Thanks.
I'm proud to present the first dual boot project for the all Exynos7870 and Exynos7880-based Samsung devices. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer 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
Instructions for dual booting
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.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
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.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
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
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
Downloads
Here is the latest build : https://www.androidfilehost.com/?fid=962021903579496224
XDA:DevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
lzzy12
Source Code: https://github.com/Mysteryagr/DualBootPatcher
Version Information
Status: Beta
Created 2017-12-03
Last Updated 2017-12-03
thanks bro ,Great Work
Wow Good Work Bro It Will Be Very Useful For Us Bro
??
Great
got error 1 when flashing lineage as second rom
Tried it. It works if I flash the ROM from recovery but if I want to switch to primary using DualBoot utilities it doesn't work. Fortunately I had made a buk up...
One more thing : The secondary ROM detects the SD card as corrupted and needs formatting if installed to external storage :/
Can anybody help my?
I want to install second ROM on sd card, it will be perfect on ext4 separete partition.
I'v tried it.
I install second ROM on sd card (now it have only one partition vfat), but it cycle rebooting. Helps only restore from TWRP recovery.
DualBootUtilities..zip dont work and have an ERROR 1 in TWRP both 3.2.1.0 and 3.1.1.0.
My primary ROM is last oficial Android 6.0.1. , second ROM is [ROM] Stockrom Lite SM-A520F
Primary ROM rooted SuperSu, CSC - BTU, bootloader - A520FXXU4BRC4, PDA - A520FXXS2AQH1, Radio - A520FXXU4BRC1, ROM - A520FXXS4CRE1/A520FOXA4CRD3/A520FXXU4CRD3, Kernel 3.18.14-10911830 [email protected] #1 32-bit
Here is recovery log file
---------- Post added at 12:02 PM ---------- Previous post was at 11:56 AM ----------
May be it is the reason?:
I:Legacy property environment initialized.
mount: mounting /dev/block/mmcblk0p20 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p25 on /data failed: Device or resource busy
Click to expand...
Click to collapse
I have this problem when I go to roms. Anybody know what's wrong?
iloveoreos said:
I have this problem when I go to roms. Anybody know what's wrong?
Click to expand...
Click to collapse
You need root for this to work. Do you have that?
sheepkill15 said:
You need root for this to work. Do you have that?
Click to expand...
Click to collapse
Yes, I'm rooted with magisk. I wonder if it matters what version I am running. I am running stock 8.0 on an A520W.
iloveoreos said:
Yes, I'm rooted with magisk. I wonder if it matters what version I am running. I am running stock 8.0 on an A520W.
Click to expand...
Click to collapse
Oh right. I don't know if op patched something about this, but originally touchwiz roms don't work with DualBoot, not even Hades.
Or, at least, I couldn't get it to work.
sheepkill15 said:
Oh right. I don't know if op patched something about this, but originally touchwiz roms don't work with DualBoot, not even Hades.
Or, at least, I couldn't get it to work.
Click to expand...
Click to collapse
Ok, that makes sense, I tried a different version on my note5 and it didn't work either. The OP said to set Tw rom as primary though, is there a way to do that?
Edit: Would it work to flash lineage os, install dualboot, and then flash touchwiz as primary?
Do ROMs boot normally from an SD card? Or are they a bit slow?
iloveoreos said:
Do ROMs boot normally from an SD card? Or are they a bit slow?
Click to expand...
Click to collapse
Depends on the SD Card ;p
But, in my experience, SD is slower than internal memory
Where to get the DualBootUtilities? Cant find them in this thread. Can I use the official ones from the website? Or can I just install the App and im fine?
iloveoreos said:
Do ROMs boot normally from an SD card? Or are they a bit slow?
Click to expand...
Click to collapse
Did you fixed the error when going to ROMs? Im having the same error and I dont know what to do. Im rooted with magisk on Stock ROM 8.0
simon151102 said:
Did you fixed the error when going to ROMs? Im having the same error and I dont know what to do. Im rooted with magisk on Stock ROM 8.0
Click to expand...
Click to collapse
Try a custom ROM like lineage os and it should fix that error. However, when I updated ramdisk through dual boot on lineage os 16, my internal storage would quit showing up in stock file manager and downloads would fail. Haven't tried on any other ROM s though.
DualBootUtilities.zip?
lzzy12 said:
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
Click to expand...
Click to collapse
Great job ,thanks. I did'nt find the download link "DualBootUtilities.zip"
I am getting an error 1 while flashing a patched ROM. It looks like the ROMs aren't compatible by looking at the logs. Don't know if that is the correct verdict though.