Related
The below info will remain for historical informations but this system has been replaced by a better system found at http://forum.xda-developers.com/showthread.php?t=1100777
DualRom ***Dual boot 2 roms on your Droid Incredible***
Team ADX presents your dual booting solution for the Droid Incredible. Please Read entire post before using any of the zips given. Undo zip in second post to put your phone back to the state it was in before flashing these zips.
I have added some empty shells to allow people to use any rom. See bottom of first posts.
DualRom comes in DualRomSenseFroyo and DualRomCM7. We wanted to give you the option to basically use the opposite of what you would use as your normal rom. CM7 is CM7. It was compiled from CM7 source and only made changes needed for it to boot off interanl storage. SenseFroyo is stock rom with Ziggy's kernel to allow overclocking. I did not remove any bloat since you will have over 5GB's free so there is plenty of room. I don't use sense roms so I'm not familiar with what sense tweaks are out there but I may research and make changes to the sense rom in future updates. I chose these roms because I wanted roms that would be very stable right out of the box. This is a new method for dual booting and there hasn't been any wide testing yet so you should still consider this Beta till there is more feedback. Everything has been stable in the limited testing. All feedback encouraged and appreciated.
DualRom Terminology for this post
PhoneRom - refers to the rom that is installed normally on your phone
InternalRom - refers to the DualRom version that you install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* Who is Team ADX?
For those that don't know us Team ADX was formed by a few Dev's from the HTC Droid Eris. We collaborate on projects together even though we've all branched to different phones. Team ADX is Conap, Workshed, and Gnarlyc. Conap has the Droid Incredible and will handle most of the support in this thread. The Team ADX account is usually only used for the op and all follow posts will be done with our personall accounts.
* Why would you want 2 roms on your phone?
Sometimes you can't decide between Sense and CM/Aosp roms. Both have thier benifits and both have thier downfalls. Why not have both on your phone. For app developers this is a great solution so that you can easily test your apps on Sense and Aosp roms. Also it's just another cool reason to root right?
* Any downside to this?
The only downside for this is that it uses the entire 6.5Gb of internal storage that the incredible has. The reason it does is because the emmc which includes the 6.5GB of internal storage also includes the 750mb's for the data partition and the 200mb's for the cache partition of the phone. For this reason HTC has locked this from being repartitioned. I did not find a way to unlock it although there probably is. I personally don't use the internal storage on my phone at all since most apps defaut to sdcard. If you don't use or need to use your internal storage this is a great alternative to what you can use it for. I tested many methods which included putting the rom on SD card or rearanging the partitions where the normal rom is stored and I found this method to be most stable and the least intrusive to your normal rom.
* How does it work?
With this DualRom setup you will be able to keep your current rom and even change your current rom on your phone in the normal fashion you are used too. There is a zip file to flash before flashing your DualRom that will set up your current rom to work with DualRom. It only makes minor changes to your current rom and I will explain that during install instructions. The DualRom will then get installed to the internal storage of the phone. An app called DR Reboot written by Conap specifically for this setup will be installed in both roms that will let you boot back and forth between the 2 roms. There will also be zips automatically added to your sd card that will allow you to choose which rom you want to boot to from recovery.
* Is this risky?
With any phone modification done with root there is always risk involved. From my testing I determined the phone would not let me repartition the internal storage therefore not letting me screw up the phone. As long as you use the zips we provide there should be no issues. As always though flash at your own risk!!!!
* Is this compatible with my rom?
DualRom should work with any rom you use. For the DR Reboot app to work you will need a rom with busybox installed but that is pretty standard. If DR Reboot does not work for you you can use recovery to boot back and forth. The zip you flash in recovery only takes a few seconds so this is still a much faster option then doing nandroid/restore's.
* How do I install this? What do the zips do?
The zip files are named with a number to start. Flash in the order of the numbers. All my testing was done with CWM v2.5.1.2.
1DRPrep-setupEMMCforRomFlash.zip We flash this zip first. All it does is change the filesystem of the internal storage partition(6.5gb) from fat32 to ext3. THIS WILL ERASE ALL FILES FROM YOUR INTERNAL STORAGE. Please backup any files you want to keep. This zip can also be used to reformat if you decide you want to switch from one version of DualRom to another(i.e. Sense to CM7). This zip will take a few minutes to flash so be patient.(I know my progress bars don't move right in recovery but it is working).
2SetupPhoneRomForDualBoot.zip We flash this second. This zip will do a couple of things. It installs the app into your current rom that will allow you to boot back and forth. It also backups the boot.img from your current rom to your sdcard so that it can use it when you want to boot back to the Phone Rom. It add's another zip to sdcard that allows you to boot back to Phone Rom from recovery. It also adds an edited vold.fstab to your current rom so that your phone will not complain that it can no longer fine the interal storage since your using it for something else. If you have dualrom already installed and decide to flash another normal rom to your phone you can just re-run this zip after flashing the normal rom.
3DualRomSenseFroyo.zip or 3DualRomCM7.zip These are the actuall roms. They will install the rom to the internal partition and also put a zip on your sdcard that allows you to boot the internal storage rom from recovery if you need too. Please flash only one of these.
* I've installed it now what?
Once you have flashed the first 3 zips your phone is ready to reboot. Reboot the phone and it will boot to the internalrom. This is a first boot so it will take a few minutes but not really longer then the first boot on a normal rom. Once it boots go through the normal setup of the rom. Then you can look in the app drawer and you well see DR Reboot app. I would reccomend placing a shortcut to this on a home screen somewhere for ease of access. Open DR reboot and from there you can reboot to the phone rom, internal rom, or recovery.(See Photo at top of post) You can still use the normal reboot options of the rom if you want to boot back into the same rom you are in. Alternativley you can boot to recovery and flash the bootphonerom.zip or the boot-internal.zip's to boot to either rom. These are a backup mainly in case the DR Reboot app malfunctions (occasionally it fails to flash the boot.img)and you need to get back into one rom or the other. I would not delete them from the sdcard. That's it....use the roms as normal and boot back and forth as you wish.
* My phone won't reboot to the phonerom even after flashing the phonerom.zip in recovery?
This is why we do a nandroid backup. Restore it now and then reflash the 2SetupPhoneRomForDualBoot.zip.
* What about tweaks/zips/themes?
If the phone is booted into either rom then anything you apply will get applied to the rom you are booted in...(i.e. metamorph). Keep in mind I have not tested much as of yet with the internal rom but in theory it will work fine. The phone rom will continue to work as normal. Any flashable tweaks/themes will only affect the phone rom. The install scripts would need to be modified to apply them to the internal rom. It shouldn't be too hard to modify them and I will try to post some instructions on that later.
* What about ADB?
ADB will acess what ever rom you have booted at the time.
* Will this allow us to boot other operating systems(i.e. WM, IOS)?
No they are not bootable on android devices and don't know if they ever will be. This will allow us to boot larger Rom Ports as some of the Rom's are getting larger then our internal storage.
** KEY POINTS TO REMEMBER
1. Everytime you flash a normal rom please flash 2SetupPhoneRomForDualBoot.zip after to update your stored boot.img.
2. Try to stick with more stable tweaks on the internalrom untill we can work out a easy way to wipe data/cache or a way to make a reliable nand.
3. Nandroid is your friend. Don't forget to do your normal Nandroid's in recovery for the phonerom before flashing any zips.
4. Zips are numbered in order so you can flash them in order.
5. Enjoy your 2 roms!!!
** TODO List
1. Make data/cache wipes available
2. Watch to see if the roms sharing the .android_secure folder on sd is going to be a big problem. So far in my testing is has not been an issue.
3. Make some type of Nandroid available...We have a something but it's not very reliable so working on a more stable method.
*Thanks to:
Cyanogenmod for thier great work http://www.cyanogenmod.com/
Htc I guess for sense and for making quality phones.
Ziggy471 for his kernel http://www.ziggy471.com/
TeamADX members for all they do!!!
XDA member unCoRrUpTeD for getting me interested in Dual Booting
Everyone and anyone who contributes to open source projects
Downloads
FLASH AT YOUR OWN RISK
1DRPrep-setupEMMCforRomFlash.zip - THIS ZIP WILL ERASE EVERYTHING ON YOUR INTERNAL STORAGE WHEN FLASHED. YOU HAVE BEEN WARNED MD5-ea34104a4b8ee11ee3d6442c13c0f93c
2SetupPhoneRomForDualBootV2.zip MD5-f2a55ed14f720332cfe9f88d32918a9f
V2 fixes flash_image binary not having execute permissions causing phone to not boot from phone rom to internal rom. Make sure you are on phonerom and reboot to recovery and just flash this zip if you've already installed DualRom.
3DualRomSenseFroyoV2.zip
V2 includes update boot.img that i added in the test zip i posted. That's the only change.
DRSenseUpdatetoV2.zip
If you flashed v1 of sensefroyo you can just flash this to update so you don't need to wipe.
3DualRomCM7v3.zip
v3
Updated to CM7.02 Stable
v2
Adds new boot.img that automatically fixes the filesystem on reboot.
DRCM7v2Update.zip
Updates DRCM7 to v2 with no wipe if you already have DualRomCM7 installed.
How can I use other roms with this?
I made some rom "shells". You can open the zip of the rom you want to use and drag the system and data folders and drop them in the "shell" zip. There is a shell for miui 2.3, cm/aosp 2.3, and Sense 2.2. This way you all have the option to use any rom without me releasing other peoples work.
MIUI-GB-shell.zip
Sense-2.2-shell.zip
CM-AOSP-GB-shell.zip
* What if I want my phone back to normal?
This Zip will completely undo the changes to your phone rom and will reformat your internal storage back to fat32 so it can be used for storage again.
UndoDualRom.Zip
* Nandroid Backup and Restore
DualRomNandroid.zip Boot to your internal rom and then boot to recovery. Then flash this zip in recovery and it will create a folder called DR on your sdcard in /DualRom/backups/. If you want to make multiple backups then you can rename the DR folder to whatever you want. If you want to restore the backup just rename the folder back to DR. If your only making one backup you can leave it named DR. If you make another backup without renaming the folder then it will overwrite the old backup.
DualRomNandroidRestore.zip Guess what this does ...flash this to restore the backup you made with the DualRomNandroid.zip. This script will restore from the DualRom/backups/DR/ folder on your sdcard. Rename whichever backup you want to restore back to DR.
All zips are provide as is. Use at your own risk.
If you have suggestions/ideas/improvements feel free to let us know. I will note here that I have looked at symlinking the database's for mms and phone logs so they would show on both roms but it seems to cause issues. I beleive the issues have something to do with CM7/2.3 databases is not the same as Sense/2.2 database. I know people have had problems when trying to restore that type of data when switching roms so it's probably the same case here. If anyone has idea's or knowledge more in depth on that issue feel free to share!!!!
So how does this work with SMS/phone logs? If I get a text while on one ROM, and switch to the other, will it still be read with the other? Same thing for phone calls.
This looks like a groundbreaking project, and I look forward to trying this out
TheWhiteBandito said:
So how does this work with SMS/phone logs? If I get a text while on one ROM, and switch to the other, will it still be read with the other? Same thing for phone calls.
This looks like a groundbreaking project, and I look forward to trying this out
Click to expand...
Click to collapse
Currently they act independently of each other so you will only see it on the rom booted up. At some point I will attempt to merge them as much as possilbe. I will need to test what backups and databases are compatible between CM and Sense.
Team ADX said:
* Will this allow us to boot other operating systems(i.e. WM, IOS)?
No they are not bootable on android devices and don't know if they ever will be. This will allow us to boot larger Rom Ports as some of the Rom's are getting larger then our internal storage.
Click to expand...
Click to collapse
This sounds sick, especially having the space to port large roms like Sense 3.0! Looking forward to whatever comes out of this.
Wow this is great ill try it out once there's some way to nandroid.
Wow good job guys. Just wanted to give you some props and say ill definitely be watching this thread for updates and sometime soon I will definitely try it out. Keep up the great work, and thanks.
Sent from my ADR6300 using XDA Premium App
kschwarz88 said:
This sounds sick, especially having the space to port large roms like Sense 3.0! Looking forward to whatever comes out of this.
Click to expand...
Click to collapse
Oh yes *licks lips* Sense 3.0, here we come!
r3nz024 said:
Wow this is great ill try it out once there's some way to nandroid.
Click to expand...
Click to collapse
You can nandroid your current rom in recovery as normal and flashing this won't have much affect on your current rom other then adding the app that lets you boot into the other. The only thing you can't back up is the rom on the internal storage. But even if the internal rom goes all crazy on you it won't affect your current rom.
Is there a way to restore the EMMC partition to FAT32 if I decide not to keep the dual ROM functionality? aka: what's a command I could stick inside of a CWM zip to format back to FAT32?
Is this working with the most recent recovery? I know the OP says it was tested with the older 2.X version
jonesh said:
Is there a way to restore the EMMC partition to FAT32 if I decide not to keep the dual ROM functionality? aka: what's a command I could stick inside of a CWM zip to format back to FAT32?
Click to expand...
Click to collapse
I added a zip to return the phone to normal if you wanted to go back. The zip does this for you but if you wanted to change the filesystem back to fat32 manually you would go into recovery and do:
adb shell
parted dev/block/mmcblk0
mkfs
it will prompt you that it will erase all data and type yes and hit enter
then you choose partition number 3 hit enter then type fat32 hit enter and it will reformat to fat32. The zip does this as well as removing the app from the phonerom and the other files that were installed.
chris61292 said:
Is this working with the most recent recovery? I know the OP says it was tested with the older 2.X version
Click to expand...
Click to collapse
I'm use to working with amon's and not CWM so I'm not sure what the changes were. I know they changed the way you mount the partitions so i'm not sure if i did it the old way or knew way. I will check into it and fix it if it needs to be. Are the newer recovery zip's still compatible with the older recoveries I assume?
Wow! Conap is here! All over the dl...... ty u shed, conap, and company
I saw this and got excited for a WP7 dual boot solution :< we can dream can't we?
very cool. OMFGB and OMGB at the same time xD
Team ADX said:
I'm use to working with amon's and not CWM so I'm not sure what the changes were. I know they changed the way you mount the partitions so i'm not sure if i did it the old way or knew way. I will check into it and fix it if it needs to be. Are the newer recovery zip's still compatible with the older recoveries I assume?
Click to expand...
Click to collapse
as long as the old recoveries support edify, there shouldnt be an issue
r2DoesInc said:
as long as the old recoveries support edify, there shouldnt be an issue
Click to expand...
Click to collapse
Thankyou...
So, sacrificing our emmc for a larger partition would also open up options for larger android roms like a full Sense 2.0/3.0 Rom wouldn't it?
phoenixs4r said:
So, sacrificing our emmc for a larger partition would also open up options for larger android roms like a full Sense 2.0/3.0 Rom wouldn't it?
Click to expand...
Click to collapse
Yes room is not an option here. That doesn't mean it is easier to port but room is definitely not an issue. As soon as i can find the links to some of these larger roms i'll look at them although I'm more accustomed to building from source then I am to porting.
Hello Nookers,
I myself and pndo1 of XDA have posted guides for dual booting CM7 and Stock 1.2. My first one was crappy, my second one was a little less crappy, and pndo1's was pretty good, but had too many steps. So yeah, I decided to clear this up once and for all. Alright, enough of that garbage, let's get on with the guide!
0. Make a CWM sd card using these instructions.
1. Download CM7 to your sd card. I recommend the latest version from here. Also, if you would like to overclock download this. Lastly, if you would like to remap Volume + and - to Menu and Back, download this too. Also, your gonna want (duh) have a copy of Nook Color Stock 1.2. This one is the best in my opinion. Also, if you would like to root Stock 1.2, get this. Now get gapps from here. Almost! Download thishere. And now the multiuboot! Grr... this is tiring... but lasties! Get it here. Put ALL the files you downloaded on your SD Card.
1. Boot into CWM. Go into Backup+Restore and create a backup. Then go into Mounts+Storage and unmount the sd card. Put in an MicroSD reader in your computer. Navigate to /sdcard/clockworkmod/ and find the backup. Copy it to your computer. You can now delete it from the SD Card. Put the SD Card back in the nook. Go into Mounts+Storage and hit "Mount sd card" Now from the same place, wipe system, data, and cache. Now go to the root menu (hit the power button once). Hit "Install zip from sd card" then "Choose zip from sd card" Select prep.dualboot.zip. Then redo the choose zip Select your downloaded 1.2 Zip. It should be called "update_nc_stock_1.2_keepcwm.zip" Flash that. Now wait for it to install. Reboot your Nook. It will boot and will ask you to setup the Nook. Set it up but if you don't have wifi, follow these instructions. After setting up, boot back into CWM using your sd card.
2. Now Choose the zip from sd again, but select ManualNooter. That will take one minute to flash. Reboot again. Make sure your root is setup. To confirm, download an app from the market. Any app.
3. Once that is done, boot back into CWM. Flash the zip "eclair-to-dualboot-0.2.zip" It will duplicate Stock 1.2 to the Second partition. Now go into Mounts+Storage, and wipe system+data+cache. Now choose zip again, but this time pick CM7. Then Choose again, pick GAPPS. Then anything else, like that KeysMod or OC kernel. Now flash Multi-Uboot-0.3.zip. Now reboot without holding anything. It should boot CM7. Reboot, but this time hold the home button. BAM! Stock 1.2. Hope it worked for ya!
To those whom it doesn't work:
yelloguy said:
I had the same problems as everyone else is reporting on this thread. I did this on Tuesday without the benefit of this guide but with the help of other two mentioned in the OP.
So after talking to iKingBlack via PM, I tried it again yesterday. And here is the exact sequence of events in case it helps anyone.
Install removal script for dual boot found in these forums
Install stock 1.2 from the link mentioned in OP
Boot 1.2 and register the device
Sleep 7.5 hours and then chat with iKingBlack
Install manual nooter, then the apk enabler
Boot 1.2 to check root access
(no boot from now on)
Install prep dual boot
Install eclair to dual boot
Format system, data and cache
Install CM7 nightly
Install gapps
Install multi boot
Reboot holding N and check stock works as it used to
Reboot normally, check CM7 works and set it up
Since then I have used both partitions successfully.
Click to expand...
Click to collapse
Credits:
@GirLuvsDroid for the feedback and testing
@GabrialDestruir for 1.2 Manual Nooter
@Koush for ROM Manager and CWM Flashes
@yellowguy for telling us to flash prep.dualboot
@Anyone else who helped but escapes my mind at the moment
@pndo1 (Who has moved on to better things than our little NC's... aka Flyer) for this orignal project
I've been wanting to dual boot my NC for a while now, but I've read several sets of instructions and kept getting twisted up in them. I was also concerned that having a dual boot would make it difficult to impossible to continue installing the CM7 nightlies and the latest Dal kernels.
These instructions look really clear and easy to follow and I thank you for that!
I just want to clarify my understanding: both CM7 and stock 1.2 are run from eMMC, correct? And, because stock 1.2 is on the second partition, it's just business as usual to install the nightlies and the latest kernel on the first partition, right?
Again, thanks for taking the time to rework your instructions again. Your contributions are much appreciated!
Why a special uboot? Stock cm7 uboot (based on bn 1.2) already does multiboot... (hold down n on boot for info) and dalingrin's nook tweaks lets you set up default options from prefs menu...
That said, I didn't read the instructions carefully so maybe there's a reason...
@GirLuvsDroid Your welcome, and yes both run from the emmc. Flash nightlies and kernel like anything. Just nothing to the dual boot partition.
@fattire For me the CM7 Alternate boot option hangs. But again, that's me.
I may have just missed it, but I didn't see where in the instructions to download the Multi-Boot-Uboot-0.3.zip file.
I found and downloaded v0.4 file from this thread
http://forum.xda-developers.com/showthread.php?t=947698
and it doesn't quite work right. It boots CM7 fine, but it hangs on the Nook 'N' screen when booting into stock 1.2. I'm not sure if that's because of the v0.4 multi-boot file, or because of something else I did wrong. (It did boot into stock 1.2 correctly at the point where you said it would in the instructions).
Any thoughts, or the link to the v0.3 multi-boot zip and I'll flash that to see if it corrects the problem.
MHotovec said:
I may have just missed it, but I didn't see where in the instructions to download the Multi-Boot-Uboot-0.3.zip file.
I found and downloaded v0.4 file from this thread
http://forum.xda-developers.com/showthread.php?t=947698
and it doesn't quite work right. It boots CM7 fine, but it hangs on the Nook 'N' screen when booting into stock 1.2. I'm not sure if that's because of the v0.4 multi-boot file, or because of something else I did wrong. (It did boot into stock 1.2 correctly at the point where you said it would in the instructions).
Any thoughts, or the link to the v0.3 multi-boot zip and I'll flash that to see if it corrects the problem.
Click to expand...
Click to collapse
MH, it's the link in the OP that says this: "Last one (yes, really!) here." It's not the Multi-Boot-Uboot-0.3.zip but the eclair-to-dualboot-0.2.zip.
Disgregard this post -- I'm an idiot and apparently blind, as well.
Thanks GLD.
I'll reflash that one (I flashed both, just like the directions said ) and see if that makes it behave better.
MHotovec said:
Thanks GLD.
I'll reflash that one (I flashed both, just like the directions said ) and see if that makes it behave better.
Click to expand...
Click to collapse
I must be blind -- I don't see where it says to flash both. I only see the eclair-to-dualboot in the instructions.
Nevermind -- I found it. It's the last step. I stand corrected and I'm glad I do because I'm planning to do this when I get home from work tonight. Thanks for setting me straight!
Reflashing the eclair to dualboot wasn't the answer, now is doesn't even TRY to boot the stock 1.2.
Now where did I leave that drawing board....
I found the download link for the Multi-Boot-Uboot-0.3.zip:
http://api.viglink.com/api/click?fo...dified u-boot.bin based on B&N 1.2 source
GLD, if anyone tells you that you're not a goddess, you tell them that I said you are.
Of course, that didn't solve the problem. (sigh)
I ran the entire routine again, and this time used the v.03 multi-boot that you found, same problem. It will boot into CM7 just fine, but it hangs up when booting into stock.
ahhhhhh, that's just so sweet, MH!
I just went through the whole process myself and everything went perfectly right up until I tried to boot into stock 1.2. Exactly like you, it hangs on the N and won't boot up. CM7 boots just fine, though.
Well, at least I know it's not just me.
By any chance, have you run the app that changes your Nooks RAM from 'new way' to 'old way'? (1gb data, 5gb apps).
I have, I wondering if that has something to do with it (just fishing of course, it's not like I actually KNOW anything).
Yes, I had a blue dot NC that I repartioned, but I did it using the custom partition (around 2GB data).
Well, multi-boot link added.
Oh, to those whom it doesn't work (stuck on N), try flashing 1.2 zip and manual nooter without rebooting and then eclair2dualboot then wipe system,data, and cache. Then flash cm7 and goodies. Not one reboot. Try it and only then say if it works or doesn't.
I'll try this no-boot method when I get a chance tomorrow. One question for you -- assuming I get this to work, is there any reason I can't restore /data from the CWM backup of my original setup that I made before I started the dual boot process?
I get the same result with the no boot method. CM7 boots fine, Nook stock hangs on the 'N' screen.
I had the same problems as everyone else is reporting on this thread. I did this on Tuesday without the benefit of this guide but with the help of other two mentioned in the OP.
So after talking to iKingBlack via PM, I tried it again yesterday. And here is the exact sequence of events in case it helps anyone.
Install removal script for dual boot found in these forums
Install stock 1.2 from the link mentioned in OP
Boot 1.2 and register the device
Sleep 7.5 hours and then chat with iKingBlack
Install manual nooter, then the apk enabler
Boot 1.2 to check root access
(no boot from now on)
Install prep dual boot
Install eclair to dual boot
Format system, data and cache
Install CM7 nightly
Install gapps
Install multi boot
Reboot holding N and check stock works as it used to
Reboot normally, check CM7 works and set it up
Since then I have used both partitions successfully.
@GLD Yes, I think you can restore safely.
@yellowguy You don't need prep dual boot because eclair2dualboot already takes care of that. And if my instructions didn't work, try yellowguys, a slightly refined method.
Hello
My name is Alvin and I really want to help the people who are new to Android hacking/rooting/flashing/roming<made that up . This post may not be interesting or super helpful, but I want to help people with a question that's not usually mentioned.
Upgrading/Downgrading, that's the Technology world right now. It's important people know how to keep up by upgrading without having to lose all their data.
Upgrading/Downgrading Difficulty Level: 2
(Scale of 1, being Beginners, to 10, being a developer)
To upgrade a ROM without losing data, you must me under these certain circumstances,
The ROMS match. THAT'S IT. Well what do I mean by "Rom Matches"???
The /data has to be compatible with the newer ROM.
The ROMs that are not compatible with the same data.
NC Stock to any other ROMS
THE DATA MUST BE WIPED BOTH GOING FROM STOCK AND GOING BACK TO STOCK. THE DATA IS NOT COMPATIBLE.
The ROMs that ARE Compatible:
CM7<>CM7
CM7<>CM9
CM7<>CM10
Custom ROMs<> Any CM ROM.
Note: Downgrading the Android OS and keeping Data is fine, but some items may be broken or incompatible after being modified in a newer Android Version.
NOW you read all the circumstances and determined that your Nook Color is OK to upgrade+keeping /data partition, here are instructions if you don't already know them.
Open any type of Recovery. CWM or TWRP. SD or Emmc.
Go to Mounts and Storage at the bottom
Carefully select Format /system
Next, select format /cache
Now, we are leaving the /data alone.
Click Back or use the power button to do so.
Click Install Zip from SDCARD.
Find your .zip file that you want to flash to upgrade/downgrade your Nook.
When finished, you may apply GApps which is optional. GApps was formatted with /system. If you need to find gapps, go to: goo.im
Reboot and the New ROM should look like it was used before by you.
Note: The location of these instructions are based on C.W.M. All instructions are same on other recoveries.
If this post helped you, I would appreciate a thanks because it would make my day.
If this post provides any false information, typos or errors, please tell me so because this is a great learning experience for me.
If there are any questions, I will answer them withing 48 hours. Valid till 11/4/12. After that I'll check periodically.
P.S I love smiley faces.
Sources: Picture from neown.com
Hey -- I'm just about to try these steps. It seems really self-explanatory to me, I'm more than a beginner but not quite at developer. I'd say I'm like a 6 or 7 in your list.
However, the one thing I haven't tried yet is upgrading to a newer ROM. I flashed Nameless v2.0.2 for the HTC Desire C and now they're at version 5. I just did a FULL backup using CWM Touch for the Desire, and I'm about to do what you suggest. I have a custom lockring, battery icon and boot animation, I guess I'll just have to push those three things back on afterward? I think everything will go smoothly, I even have a separate SD card to flash from ^^
Anyway, I guess that's not really a question... I just want to make sure these steps apply to any ROM... but logically it seems like it would.
-AC
Hey, if i downgrade my rom (Android N) with only remove the system, and install the lower rom (Android M) is it will delete the installed application and the data too?
Dual Boot for P990 & SU660 on Both Bootloaders
Now with more and more new ROMs being released every day and only one phone (at least for most of us) to try them all, I think this was needed.
It is based on the method Bihariel found on a Chinese forum and his latest v2 version for the old bootloader and my previous version 3 for the new one.
It is now modified to work on both bootloaders and Partition layouts. Read change log for details.
Thanks to:
SuperSkill personally, for digging it up from the grave and giving me the vote of confidence to port dual boot into the new bootloader. He is also the 1st after me, who tested it. (thank you again my friend)
KingMGT personally, for helping me make the necessary modifications for SU660 and of course for testing it since I don’t own a SU660. (thank you again my friend)
Bihariel of course, for his great work on which I based the new version (and for copying a lot of text from his thread)
ChinaGB, the creator of the System changer app and the original idea.
What is this useful for?
Devs: you can have one ROM configured and ready for use in one partition and a second partition to test your ROMs without touching your daily ROM, so you won/t need to wipe or backup anything.
Users: you can have a stable ROM, let’s say a stock ROM with everything working and configured and you can have a second partition to test ROMs (for example a custom stock based one or a CM10 beta) so you won't need to do backups and wipes.
How Dual Boot works?
Dual-Enabler.zip: this file enables Dual boot by splitting system partition into two.
Dual-ROM-1-to-XX.zip: this file have to be flashed after flashing ROM 1, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 2.
Dual-ROM-2-to-XX.zip: this file have to be flashed after flashing ROM 2, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 1.
What ROMs can I use?
P990 Devices:
You can use theoretically, any combination of ROMs for dual booting, working on the same Bootloader of course.
SU660 Devices:
On OLD layout you can use theoretically, any combination of ROMs for dual booting, working on this Bootloader of course.
On ICS layout, due to lack of any custom ROMs for SU660, the p990 layout and bootloader is used so only custom CM, PA & MIUI ROMs are compatible, working on this Bootloader of course.
Attention !! The only ROMs you should not use are Auto-wipe ROMs because they will delete your data partition and with it ROM1 and ROM2 save files. Of course if you are an advanced user, you can open the wipe rom and modify the updater-script to remove the auto wipe lines.
Download from here the package for your device and follow the instructions in post #2.
For older versions follow the instructions included in package.
Change Log:
v5.0 Date 05 Feb 2013
DualBoot-Control.zip. All five zips used till now for enabling/maintaining Dual-Boot have been replaced by this aroma-style flash-able zip.
SU660 package now supports also the su660 ics bootloader & layout.
V4.6 Date 30 Jan 2013
512MB-512MB system partitions for both bootloaders,
Reduced data (to 2000MB) for old-bootloader (because a 2048MB one cannot be formatted on old bootloader)
Bug-fix for dual-boot remover (SystemChanger app wasn't removed).
V4.5 Date 22 Jan 2013
Now it auto enters recovery after repartitioning. No need to keep pressing Vol- & Pwr.
Linux nvflash binary added. (I had forgotten to include it in package, sorry.)
Minor changes in flash.sh (for linux).
V4 Date 20 Jan 2013
It now works on both bootloaders. During repartition with nvflash you have the option to select which one
In old bootloader the system partition is splitted in 370MB for ROM1 and 512MB for ROM2 (in case someone wants to install tonyp's & harsh's full ICS version for old bootloader).
Same simple procedure to enable and maintain dual-boot.
Common flash-able zips because they detect current bootloader and partition layout and act accordingly.
Re-compiled SystemChanger app to display more correct messages and also in which ROM you are switching to.
V3 Date 12 Jan 2013
System partition size is 512 MB for each ROM.
Data partition is still shared but with the max size of 2GB.
Included latest cwm recovery 6.0.2.5 by pengus77. It works for all available ROMs for new BL (DM X, FLEX-ICER & unofficial CM10 CM10.1 ones)
NewBL-Dual-Enabler’s scripts are modified not only for the new layout but now also check and format (if needed) the internal SD (the first time after NVFlash is always needed). It also returns to recovery automatically to let you install or restore the 1st ROM.
NewBL-Dual-ROM-1-to-XX.zip & NewBL-Dual-ROM-2-to-XX.zip no longer need to be updated with the boot images of the ROMs.
SystemChanger app’s scripts, before switching to the other ROM, check if current ROM is changed (by md5 checksum of its build.prop as before) and saves the boot.img for next switch.
noshare file, containing the data folders list, is now also saved under /data/dual-boot. This way it will be always accessible and updatable if needed, no matter which ROM is running.
Boot images and md5 checksums are also saved under /data/dual-boot.
Two more flash-able zips added:
Wipe-ROM-data.zip This will wipe the data of the current ROM. Useful for changing ROM or if required by ROM’s chef
Remove-DualBoot.zip This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts from the current ROM. Useful if you want to make a clean nandroid backup, to restore after a repartition to normal layout.
For V2 change log see bihariel's thread
Here is the guide to get Real Dual boot on both BLs.
Please read carefully because this may mess up your phone if you don't know what you are doing.
Oh!! I forgot, this phone is unbrickable, so give it a try.
Installation Instructions
Extract the downloaded package with WinRAR or similar to any folder.
Copy ROM1, ROM2 and the DualBoot-Control.zip to external SD.
Go to the folder DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions select BootLoader and wait until NVFlash process finishes and the screen goes black.
Disconnect the USB cable, put the battery back and just power on the phone it will enter into recovery automatically. (It takes about 40 secs to enter recovery 1st time after NVFlash)
Install DualBoot-Control.zip and select Enable Dual Boot option. The phone will reboot (if supported by recovery) and enter in recovery again (if not select reboot recovery from recovery).
Make a full wipe just in case to avoid boot-loops and format /system because it may not be formatted by ROM’s updater-script (mounts and storage --> format /system)
Now flash ROM1 (or restore a nandroid backup of ROM1) and without rebooting install DualBoot-Control.zip, select ROM1 update and reboot when it finishes.
When the phone completely boots, you will find an app called SystemChanger, launch it and click Switch ROM, it will ask you for root rights, click yes, the phone will reboot quickly, press and hold Pwr button + vol down when the screen goes black to enter recovery, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
Format /system (the 2nd system now), because it may not be formatted by ROM’s updater-script.
Now flash ROM2 and without rebooting install DualBoot-Control.zip, select ROM2 update and reboot when it finishes. (Attention: do not restore a backup of ROM2 because it will wipe data files of ROM1)
And that is all, if you want to switch to ROM1, as before, run SystemChanger and click Switch ROM.
Note for those having experienced the older version 2: No need to add boot images in Dual-ROM zips any more.
How to change/update a ROM or Kernel
You have to be on the ROM you want to change/update.
Enter Recovery
If you are changing the ROM or kernel and/or a wipe is needed, install the DualBoot-Control.zip and select Wipe current ROM data.
Flash the ROM or kernel and before reboot install the DualBoot-Control.zip and select ROM1 update if you flashed ROM1 or ROM2 update if you flashed ROM2.
Info: There is also the wipe-rom-x-data.sh in /data/dual-boot/ which can be used to delete the non-running Rom’s data. You can also run this from terminal or adb shell to clean the data of the non-running Rom quickly. For example if you are on ROM1 and you want to change the ROM2 run the script, switch to ROM2 but when screen goes black press pwr & vol- to enter recovery.
How to disable Dual Boot
You have to be on the ROM you want to keep.
Enter Recovery
Install the DualBoot-Control.zip and select Remove Dual Boot. This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts. Useful if you want to make a clean nandroid backup, to restore after a repartitioning to normal layout with AIO-Toolkit.
Enjoy it !!
Wow......one thing i ws missing on NEW BL......thank you so much....now can hold onto this phone for 1more year....
This is just Aweosme <3 will give a try for sure ! LG O2X still the Crazy phone will try today eveng and comment back again ! can i try CM10.1 & V30B (Roms available) ???
Kudooos 4 ur post
This is what i need, i often flash rom 1 to another and restore my app and setting manualy... with this i would keep my daily rom and other for testing
thanks good job
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Nice ! Trying soon... :fingers-crossed:
SuperSkill said:
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Click to expand...
Click to collapse
Thank you too again.
No, don't give me another challenge now. :laugh:
I am thinking on making a v3 version for old bootloader too, or even better a v4 hybrid one for both bootloaders. So I do have work for now.
Yes I could integrate that into AIO-toolkit eventually in an "Addvanced Options" menu , but let's see how it is working, when more users will try it and "cure" any "baby sicknesses" that may come up first.
I can't thank you enough for your testing it so thoroughly.
I really appreciate it.
i don't really understand how this dual boot work
but, can i use my internal sd card for booting stock-based custom rom and using my external one for booting CM10 based rom?
what about ics and gingerbread on dual boot!?
jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Nice man" I ll try it soon!
jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
babi_perang said:
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Click to expand...
Click to collapse
I don't know if this will be ever possible or if it's worth trying it.
The only thing that can be done at the moment, is having one 370MB & one 512MB system partitions on the upcoming gb dual-boot version for installing the tonyp's and harsh's full ics 28g version as 2nd ROM on old bootloader.
I installed yesterday dual boot on my 2X and worked fine without any problems!
Great tool Spyrosk!!
You have done our life easier!!!
Thank you for dual boot
is indeed something very special!!!
It works beautifully for me,
the P990 is significantly upgraded:laugh:
And what about dual boot with linux?
tomsi91 said:
And what about dual boot with linux?
Click to expand...
Click to collapse
What do you mean? Read step 3 carefully.
3.Go to the folder NewBL-DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions and wait until NVFlash process finishes and the screen goes black.
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
tomsi91 said:
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
Click to expand...
Click to collapse
And iOS & Windows Mobil 8...
How about flashing the second rom that have aroma installer??
This guide is for the Sprint Galaxy S4 only and as of now it is only compatible with two kernels: KToonsez S4 Kernel 4.4 AOSP (4/17 or later) and PoKernel 1.7 F2FS ONLY Build. This guide CANNOT be used on Touchwiz or Android 4.3 yet. I will update it when and if that becomes possible
*Disclaimer: You are doing this to your phone under your own consent. This is an experimental procedure and may not work on some hardware revisions or on devices where certain conditions are not met. You assume all the risk by flashing any of the software below or changing your filesystems. I am not responsible if your phone does not work based on the method I am describing below. Modify at your own risk.
This guide had to be updated in order to correct misinformation. The guide will follow KT's instructions explicitly until it gets to the formatting of the system partition
***If you want to format your /system partition to F2FS please read that section first as it requires steps to be taken from your currently working AOSP rom!***
First, go this link download the file:TWRP-KT.ALL-IN-1.zip
http://goo.gl/HLz4al
Formatting Data and Cache to F2FS
NOTE: Follow these steps EXACTLY, do NOT add or remove any steps, period!!!!
1. Backup everything from your internal SD to your PC or external SD, since the entire internal SD is going to get wiped out with format!!!!!!!!!!
2. Download the files from the folder that you got these instructions from (Ignore the OLD WAY folder) and SAVE TO THE EXTERNAL SD!!!
3. ONLY DO THIS STEP IF YOU ARE ON AN OLD VERSION OF MY TWRP. Flash TWRP-KT.ALL-IN-1.zip (this is what gives us the ability to format using F2FS)
4. Reboot recovery
5. Go to "Settings" and check the box to force F2FS for data and cache (you can also check the box to include /system partition if you want to convert your ROM's zip to use that too)
6. Go to "Wipe->Advanced" option and wipe the "Cache" partiton
7. Go to "Wipe->Format Data" option (THIS WIPES YOUR ENTIRE INTERNAL SD CARD, all files and folders, all gone so make a backup to your external SD or PC!!!!!!!!!!!!!)
8. This step you have 2 choices:
A. Flash your ROM/gapps to start completely fresh
B. Go to restore option and ONLY restore your "Data" (you can also restore /system if you are doing the f2fs conversion on /system partition too)
9. ONLY DO THIS STEP IF YOU INSTALLED A NEW ROM. Flash my newest kernel (needs to be a kernel dated 05.05.2014 or newer)
10. DONE!!!!!!!!!!!!!
11. KTweaker has a new option under "Tools" screen to "Get Partition info" to double check your work.
Formatting System Partition with F2FS (Required: KT SGS4 Kernel 4/28 or later!)
Steps:
1.) Before doing any F2FS conversion with the above instructions, use your currently working AOSP ROM to grab the AOSP 4.4 Kernel from HERE (4/28 or later only!) and save it to your external memory card
2.) Once it is saved reboot to recovery and install it (Flashing a kernel in TWRP is Install -> Folder where kernel is -> Click KT 4/28 kernel -> Swipe to install -> Clear cache/dalvik -> Main menu -> click advanced -> Fix Permissions -> Reboot to system)
3.) After you are back in your working AOSP ROM with KT 4/28 kernel installed, download the AOSP rom you want to use and save it to your external sd card (You can leave the filename as it is, the program will rename it for you)
4.) Open KTweaker and click "Tools" and at the very bottom choose "F2FS: Convert ROM ZIP"
5.) It will ask you to locate the file, ask if you're sure, and then it will do the conversion; upon completion the zip file that was created will have "-F2FS.zip" at the end of it
6.) Now you can follow the steps above, but when you get to step 9A you will use the "-F2FS.zip" file instead of the standard ROM file
This procedure is necessary because KTweaker changes your favorite ROM to pass the command mkfs.f2fs so that your system partition is formatted to F2FS before the files are installed. I did this myself to verify and it works a treat. One crucial step to remember though is that after you install your F2FS converted ROM you absolutely must install KT's kernel so your phone will boot.
Returning to EXT4
NOTE: Follow these steps EXACTLY, do NOT add or remove any steps, period!!!!
1. Backup everything from your internal SD to your PC or external SD, since the entire internal SD is going to get wiped out with format!!!!!!!!!!
2. Download the files from the folder that you got these instructions from (Ignore the OLD WAY folder) and SAVE TO THE EXTERNAL SD!!!
3. ONLY DO THIS STEP IF YOU ARE ON AN OLD VERSION OF MY TWRP. Flash TWRP-KT.ALL-IN-1.zip (this is what gives us the ability to format using F2FS)
4. Reboot recovery
5. Go to "Settings" and uncheck the box to force F2FS for data and cache (If you checked the box to include /system partition uncheck it first)
6. Go to "Wipe->Advanced" option and wipe the "Cache" partiton
7. Go to "Wipe->Format Data" option (THIS WIPES YOUR ENTIRE INTERNAL SD CARD, all files and folders, all gone so make a backup to your external SD or PC!!!!!!!!!!!!!)
8. This step you have 2 choices:
A. Flash your ROM/gapps to start completely fresh
B. Go to restore option and ONLY restore your "Data" (you can also restore /system if you are doing the f2fs conversion on /system partition too)
9. ONLY DO THIS STEP IF YOU INSTALLED A NEW ROM. Flash my newest kernel (needs to be a kernel dated 05.05.2014 or newer)
10. DONE!!!!!!!!!!!!!
11. KTweaker has a new option under "Tools" screen to "Get Partition info" to double check your work.
FAQ
Q: Why can't I use this on Touchwiz?
A: It has been developed for the most recent Linux kernel 3.8 and has been implemented in kernels built for 4.4.x OSP builds. This isn't to say it cannot be used on Touchwiz, it is a filesystem and as long as there is a kernel that offers support for reading it installed on your device it should theoretically work on your hardware. However, this can be proven/disproven by the devs here and I will update this answer if it cannot be implemented in a backwards fashion.
Q: Are there advantages to using F2FS?
A: It is built and intended for use on flash filesystems which our devices run exclusively. So since it was developed for flash memory there will be a benefit to using it as it matures. However, this does not imply that benchmarks will increase or your whole phone will become more responsive, its intent is to have files be accessed and written more efficiently. It is supposedly also built for the long-term user who does not constantly reformat their devices because it is supposed to handle large amounts of old files and cleaning more effectively that EXT4. Source: https://www.kernel.org/doc/Documentation/filesystems/f2fs.txt
Q: Will this trip Knox?
A: No more than installing a custom recovery would. So if you already had a custom recovery (Read: TWRP, PhilZ, CWM) in place you are safe following this guide. For now of course; I do not know if there will be another iteration of Samsung software that locks down the device futher.
Q: Can I clear Cache and Dalvik to troubleshoot after changing my filesystem?
A: I tried this myself and the answer is yes. As long as you are using the F2FS custom recovery made by KToonsez you can wipe Cache and Dalvik from recovery and it will rebuild your system. Something I did notice is that first boot will stay on the splash screen longer with F2FS than with EXT4. I saw it hang on the splash screen of my Liquid rom for an extra minute before actually booting and showing cache rebuild. **Your Mileage May Vary**
Q: Why isn't the System Partition formatted into F2FS?
A: This can be done now with KTweaker. See section above.
Q: What ROMs can I use with this filesystem?
A: Any 4.4.x rom (most are 4.4.2 now) that is compatible with either KToonsez S4 AOSP kernel or Pokernel 1.7 F2FS Only.
Q: In Advanced Wipe, Preload has been added to the options of things to wipe. Should I?
A: Ktoonsez answer found HERE was that he has never wiped preload. So I suggest against it unless you know what you are doing.
Thanks
Linux, Google, and Samsung (all this neat stuff comes from those communities)
TWRP Team for their custom recovery and its updates
Ktoonsez for his awesome kernel and the modified recoveries
CPA Poke for his awesome kernel that has F2FS support baked in
LuigiBull23 for edits and reminding me to add content
XDA for giving us a place to host experimental phone procedures
The XDA Devs for all the work they do for us with their time
The XDA community for providing feedback and making this a great place to hang out
If I forgot anyone specifically please let me know and I will update this section or any section
Enjoy and let us know how it works on your device!
Great guide my friend!
delete
Thanx great guide
Sent from my SPH-L720 using XDA Premium 4 mobile app
Great guide OP! Always nice to have a thread to link to.
I'm sure it's been talked about but your posts doesn't mention the ramdisk files. They're listed but not talked about. Now I'm somewhat limited myself in understanding everything there is to know about these things but are those files to do with eventually formatting the system partition to f2fs?
May be worth putting a little note in there regarding those files... You know how some folks go flash crazy once in recovery lol
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Great guide OP! Always nice to have a thread to link to.
I'm sure it's been talked about but your posts doesn't mention the ramdisk files. They're listed but not talked about. Now I'm somewhat limited myself in understanding everything there is to know about these things but are those files to do with eventually formatting the system partition to f2fs?
May be worth putting a little note in there regarding those files... You know how some folks go flash crazy once in recovery lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Hello again.. Lol
The ramdisk mod is now obsolete as it's already included in the kernel zip, which will automatically determine whether you're still on EXT4 or F2FS and make the required changes to the ramdisk accordingly. So no need to flash anything but the kernel as usual after following the steps.
OK yea I figured it was either to do with what I said or to do with the kernel obviously. Just figured I'd ask anyways
Sent from my SCH-I545 using Tapatalk
I'll be the first to admit that I wasn't entirely sure what the ramdisk files were for. I knew they might have been for advanced users considering they were offered, but not listed in the instructions. I didn't know for sure and I didn't want to use the word "obsolete" because, well, I was so wrong before
I am glad LuigiBull23 jumped in and answered that for us. I'll get it added into the the guide so future users know what they are or are not used for. Keep the questions coming, I love learning about this stuff!
I'll be the first to admit that I wasn't entirely sure what the ramdisk files were for. I knew they might have been for advanced users considering they were offered, but not listed in the instructions. I didn't know for sure and I didn't want to use the word "obsolete" because, well, I was so wrong before
I am glad LuigiBull23 jumped in and answered that for us. I'll get it added into the the guide so future users know what they are or are not used for. Keep the questions coming, I love learning about this stuff!
Click to expand...
Click to collapse
I understand. A lot of people were and still are confused about these files..
In short, during the testing phases of F2FS, KT compiled a separate zip for changes to the ramdisk that in turn would reflect the EXT4/F2FS mount points as a means to avoid possible bootloops and such. It was indeed a success and as a result was included in his kernel.
Now, upon flashing the kernel it is able to determine which partitions are formatted as EXT4 or F2FS and mod the ramdisk accordingly. He only left the files on his server in case he ever needed them again. So they are most definitely OBSOLETE. You certainly wouldn't have gone wrong using the term in this case.
Updated the guide for KT's new all-in-one TWRP recovery that will allow you to switch back and forth between F2FS and EXT4. I used his exact instructions from his guide in all areas except for the system formatting section which I wrote. If you are using his custom TWRP recovery go ahead and grab the new one so you can use it in the future!
F2FS with CM11 Nightly
When I used KTweaker to convert my latest CM 11 nightly, it came back and said that it was done but could not find all the lines to modify. Is this ok?
mwilder817 said:
When I used KTweaker to convert my latest CM 11 nightly, it came back and said that it was done but could not find all the lines to modify. Is this ok?
Click to expand...
Click to collapse
I know it has been forever since you posted this and I apologize for the late answer, but I imagine that if you received that error you got a bad download of CM11. I've personally converted the snapshot and several nightlies of CM11 and they all passed nicely.
So for anyone getting this, if you get a similar error message: Re-download the ROM you are converting
to bad its still not possible with touchwiz, love to use f2fs on a stock rom for my sgs4-lte.
is it possible in the near future that we can use f2fs on those devices with a Samsung stock rom, using another kernel is no problem.
or is this hard to tell ?
Hello, I've been trying to use this to change my filesystem because I'm coming from CM12 and I'm trying to flash a GPE rom on my S4. But after flashing I am rebooting straight to recovery. Also I'm using the latest TWRP.
RealMikeyTaylor said:
Hello, I've been trying to use this to change my filesystem because I'm coming from CM12 and I'm trying to flash a GPE rom on my S4. But after flashing I am rebooting straight to recovery. Also I'm using the latest TWRP.
Click to expand...
Click to collapse
Make sure you are using a version of TWRP that support F2FS. I don't think the standard issue TWRP does. @AntaresOne has one that does support F2FS and is based on the latest version (2.8.3.0). That's the one I use. Of course, I'm hooked on his CM12 ROM as well. He does really good work!!
mwilder817 said:
Make sure you are using a version of TWRP that support F2FS. I don't think the standard issue TWRP does. @AntaresOne has one that does support F2FS and is based on the latest version (2.8.3.0). That's the one I use. Of course, I'm hooked on his CM12 ROM as well. He does really good work!!
Click to expand...
Click to collapse
But doesn't it have to be in EXT4 for it to work for a GPE ROM?
RealMikeyTaylor said:
But doesn't it have to be in EXT4 for it to work for a GPE ROM?
Click to expand...
Click to collapse
You are probably right. I haven't tried the GPE ROM yet.
Sent from my SPH-L720 using XDA Free mobile app
RealMikeyTaylor said:
But doesn't it have to be in EXT4 for it to work for a GPE ROM?
Click to expand...
Click to collapse
Yup gpe uses ext4 on all partitions because it uses tw framework