Related
OK so i know a lot of members are intrested in Dual booting their galaxy S2, so i have decided to complice a list of all the dual boot options i can find and have found. I have found two ways as it stands now, but my search has not been that deep yet, so here are the two ways for now and i hope to add more to the list soon.
SGS2 Dual-Boot Setup (LolBoot) - Ok so the first is an app by Hellcatdroid that you can download from Google Play. It only supports GB roms for now, but their is hope that he will put his PSvita down and continue to work on this great app.
Links
Thread
Google Play
SiyahKernel v3.1beta1 Kernel - So option 2 is a kernel from Gokhanmoral, the kernel is stable but the dual boot side is still in beta. This dual boot kernel is working with ICS roms (not GB), Gokhanmoral has tried a dual boot on stock and cm9 and this combo is working, he is pretty sure it will work with MUIU roms. The members on this thread will start to tell of other working combos they have tried, so give this one a go it is looking very good.
Links
Thread
Blog - The blog includes a changelog, and the download link for his kernel
Here is a guide thanks to Phistachio on how to dual boot using Siyah Kernel
[GUIDE] How to Dual Boot using the Siyah Kernel
Here is a fantastic guide, FAQ writen by droidphile for the use with Siyah kernel, it is a fantastic FAQ, so if you use it please go and thank him here -
Dual Booting FAQs
Here are some dual-boot faqs. Some answers may not be 100% true at present since Gokhan is still working on enhancing dual-booting and implementing all the placeholder features in touch recovery dual boot options.
1) So what's dual booting?
A. Option to boot into either two ICS roms - aosp or sammy. Immediately after boot logo is displayed, you will have a 3 seconds time-out where you can boot into secondary rom by pressing the home key. To boot into primary rom, wait for 3 seconds time-out to complete. If you don't like to wait - touch the screen, or press a volume key, or press power key during time-out.
2) What's the basic architecture behind dual booting?
A. Any rom will have /system, /data, /cache partitions and requires a kernel to boot. Primary rom has all these partitions on the same location as if you were single-booting. Secondary rom uses a hidden partition (/dev/block/mmcblk0p9) to be used as /system (it's /dev/block/mmcblk0p12 for primary rom). Second rom uses sdcard to store /data and /cache partitions. They're stored in /sdcard/.secondrom directory as mountable ext4 block device images (data.img and cache.img).
Kernel partition is shared, so same kernel boots both the roms. If you switch from Siyah to a different kernel dual booting will not be available even though you have a clone of secondary rom. Internal sdcard, ofcourse external plastic sdcard, /efs, /emmc, other kernel related virtual filesystem directories, etc are shared among roms.
3) I have just one rom now. How do i setup one more rom to dual boot?
A.
-To use current rom as primary: Assuming the other rom is downloaded and copied to phone memory
i) Flash latest Siyah that supports dual boot.
ii) Nandroid backup your existing rom.
iii) Full wipe, install the rom you need to dual boot into.
iv) Boot into that rom, perform initial setups, flash whatever zip you need to flash on that rom - gapps, themes, mods, etc. (Because after setting up dual boot you don't have an easy way to flash zips onto second rom. Remember /system and /data partitions are different for both roms)
v) Flash latest siyah on this rom.
vi) Boot into recovery, under dual-boot options, select "Clone Primary ROM to Secondary". Be patient and wait about 6-7 minutes.
vii) Within recovery, restore nandroid backup.
viii) Just to be sure, flash latest Siyah again.
-To use current rom as secondary: Assuming the other rom is downloaded and copied to phone memory
i) Flash latest Siyah that supports dual boot.
ii) Boot into recovery, under dual-boot options, select "Clone Primary ROM to Secondary".
ii) Without exiting recovery, Full wipe, install the rom you need to use as primary rom.
iii) Boot into that rom, perform initial setups.
iv) Flash latest Siyah just to be sure.
Now you have two roms. Press home key to boot into second rom when time-out is shown.
4) How much time was it to clone a rom?
A. There's /system, /data/ and /cache to clone. 2 GB data + 103mb cache + 513 mb system = 2.6 gb
Shell prompt read speed = 7mb per second.
Total Time = 2.6*(1024/7) = 380 secs = 6/7 minutes.
5) If i reboot to recovery from power-off state using 3 button method, to which rom's recovery it's booted into?
A. Unified kernel, same recovery. And remember - flashing zips to second rom is not possible.
6) Any solution to flashing zips to secondary rom?
A. Not until secondary rom is "converted" to primary rom. If you know what the updater script in the zip is doing, you can do that manually using Root Explorer (replacing/copy files, setting permissions, etc).
Else, temporarily make secondary rom the primary rom. Goto recovery, dual-boot options, "Clone Secondary Rom to Primary". Now your second rom becomes primary rom. Flash your zips. When you're done, restore nandroid backup of the other rom to make it primary as before.
7) Should i have same versions of kernels on both roms?
A. Flash kernel from any rom. Both uses the same kernel partition anyway.
8) Will i get a prompt to dual-boot if i'm not using dual boot, as in i haven't cloned any rom to use as secondary?
A. NO
9) I don't like waiting for 3 seconds to boot into primary rom.
A. Touch the screen immediately upon prompt.
10) How do i swap primary and secondary roms?
A. Goto recovery, dual-boot options, "Backup secondary rom"
Under original Backup and Restore option, "Backup" to backup your primary rom.
"Restore as secondary rom" or "Restore as secondary rom from internal sd" and select the nandroid backup of what was actually your primary rom.
Then under original Backup and Restore option, "Restore" to restore the rom you backed up as secondary.
11) USB mass storage works?
A. Only external sd is mounted for second rom atm. MTP will work for internal sd also. Both will be mounted for primary rom.
12) If i had the same /data partition shared between roms, i could use same apps on both roms.
A. Data partition can not be shared as they're incompatible between roms. (Sometimes dev asks you to perform full wipe even if you're switching between versions of the same rom right). Even if they were shared, separate dalvik caches has to be used and hence every boot will take a long time to rebuild dalvik.
13) How to undo dual booting?
A. Use "Remove secondary rom" from dual-boot options in recovery.
14) How to remove secondary rom if "remove secondary rom in recovery" fails for some reason?
A. Format /system2 directory partition, remove data.img and cache.img under /sdcard/.secondrom directory manually by booting into primary rom.
15) How to upgrade primary rom?
A. As usual, goto recovery, wipe whatever you need to wipe and install the new version.
16) How to upgrade secondary rom?
A. Temporarily convert secondary rom to primary (like explained above), install new version and revert primary back to secondary.
17) How to replace secondary rom with another?
A. Perform the steps to setup dual boot as if you had only one rom which is going to be used as primary rom.
18) How to replace primary rom with another?
A. Normal procedure - wipe, install from recovery.
19) Can i have both aosp roms/both samsung roms/first aosp, second samsung/first samsung,second aosp?
A. Yes
20) Can i have one GB rom and second ICS rom?
A. No
21) Why?
A. Kernel partition is shared between roms. Dual boot functionality is implemented in ICS kernel. ICS kernel can run only ICS roms.
22) Are init.d scripts and extweaks profiles shared across the roms so that i can make changes by booting into any rom and the other rom automatically inherits the settings?
A. NO. Roms have differet /system partitions so different init.d directories. Roms uses different /data partitions and extweaks profiles are stored under /data/.siyah. So you gotta configure both separately. Initramfs scripts are shared anyway since both rom uses the same kernel.
23) So if at all i format /sdcard, my second rom is gone?
A. Yes
24) Is the size of /system partition of secondary rom re-sizable from user space?
A. NO
25) Can i have different kernels for the two roms?
A. NO
26) What're the options under dual-booting in touch recovery?
A. i) View Status
Displays secondary rom info if found.
ii) Clone Primary ROM to secondary
First time, you will have only one rom. You may clone it as secondary rom (so that another rom can be used as primary by nandroid restoring)
iii) Clone secondary rom to primary
Whatever has been cloned as secondary rom is cloned to primary rom.
iv) Remove secondary rom
Deletes /system, /data and /cache partitions of second rom. You will have normal booting.
v) Backup secondary rom
Nandroid backup secondary rom to external sd.
vi) Restore as secondary rom
Restore any nandroid backup as secondary rom from external sd.
vii) Backup secondary rom to internal SD
Nandroid backup secondary rom to internal sd.
viii) Restore as secondary rom from internal sd
Restore any nandroid backup as secondary rom from internal sd.
ix) init second rom data
Initialize /data parition of secondary rom to resize the partition to make it bigger in case you run out of space for apps. Init also wipes all the data in /data partition. So your existing apps in secondary rom will be gone.
x) wipe second rom davik cache, xi) wipe second rom cache, xii) fix permissions in second rom - self explanatory
Click to expand...
Click to collapse
I am now running a Dual Boot galaxy s2, using Siyah Kernel by Gokhanmoral, i am running CM9 and Resurrection Remix ics v1.2 PRO[4.0.4]
This is what i have got for now, but i am always looking for more dual booting options, if anyone knows of any please let me knowand i can add it to this thread.
If you have found this thread usfull then please hit the Thanks button
Nice work again fella
You should request this and your other thread are made into sticky's
Also, im hoping these two threads will help to stem the flow of threads and questions for previously trodden ground
Keep it up dude
Thanks man, the XDA community has give me so much, I just want to give back. It would be nice to see these as stickies, maybe the FM would be kind enough to consider placing them on the sticky thread.
Sent from my GT-I9100 using XDA
I am now running a Dual Boot galaxy s2, using Siyah Kernel by Gokhanmoral, i am running CM9 and Resurrection Remix ics v1.2 PRO[4.0.4]
I am now running a Dual Boot galaxy s2, using Siyah Kernel by Gokhanmoral, i am running SensatioN ROM 3.3 ICS by Crysis21 as Primary and CM9 as Secondary.. can anyone tell me any app so that i can automatically sync both rom 's SMS, Phone log and Phone Contact.. i know manual process..
What are the pro's/con's of dual booting? Cheers
Sent from my GT-I9100 using Tapatalk
shareking said:
I am now running a Dual Boot galaxy s2, using Siyah Kernel by Gokhanmoral, i am running SensatioN ROM 3.3 ICS by Crysis21 as Primary and CM9 as Secondary.. can anyone tell me any app so that i can automatically sync both rom 's SMS, Phone log and Phone Contact.. i know manual process..
Click to expand...
Click to collapse
You can use Rom Manager to Extract the apps and data from your nandroid backup, or another app that does the same is Nandroid Browser, you can get both of google play. Just as a side note, you should get an automation sync of data when flashing a new rom, as google now store all you apps and setting in the cloud, if you check in your settings it should be under Backup and reset - back up my data - check the box, and you should have an auto sync for your next rom flash.
blade30p said:
What are the pro's/con's of dual booting? Cheers
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
For me it is just the chance to have a change never getting bored of the same rom, the con is using a dual boot that is still in better and is buggy at the moment, which may cause problems with your rom mainly the 2nd rom, also the storage of data is causing some people problems, but the thread is give good solutions.
Dual booting rocks. android rules...
Thank you for this guide
So there is an option to boot two GB ROMs but no ICS and now we can boot two ICS ROMs but no GB...
The third option should be... - you know it
Sent from my GT-I9100 using XDA
Probably get flamed - btw, I don't care one jot - but why on earth should this be stickied?
This isn't a guide, it's a post with two links to the relevant threads, where the discussion is going to be a lot more useful than anything here.
s.d. o'connor, your other guides are guides, and are very useful, for which my thanks. This one isn't.
Flame-retardant pants on - fire away.
My defence
B3311 said:
Probably get flamed - btw, I don't care one jot - but why on earth should this be stickied?
This isn't a guide, it's a post with two links to the relevant threads, where the discussion is going to be a lot more useful than anything here.
s.d. o'connor, your other guides are guides, and are very useful, for which my thanks. This one isn't.
Flame-retardant pants on - fire away.
Click to expand...
Click to collapse
Why would you get flamed for having an opinion, you are entiled to that, but here goes my defence. I could only but ask if it could be a sticky i didnt make it one, and the idea is to stop new threads being opened asking the question can you dual boot the galaxy s2. Also as more options of dual booting become avaiable then they can be added to this thread.
P.S I dont want people to get flamed for having a opinion, they have a right to that, as long as they put that across in a good manner.
You don't need a defence (unlike Leeds United, but that's another story).
Flaming is an occupational hazard here sometimes, especially if someone has the temerity to diagree with someone else. I'm way past worrying anyway.
On topic - I still don't think this deserves sticky status. You and others do. No problem. Each to their own. It's up to the mods anyway, not us.
No foul on you SD O'C because you've put together some really good threads, but if this is 'sticky worthy' standards have plummeted on XDA. Rapidly. As has been pointed out, there's a couple of links & pretty much no original content or anything that could remotely be considered a 'guide'.
Droidphile's excellent dualbooting post in the Siyah dev thread a few days ago, now that was a guide (and sticky worthy).
okay, i am on dual boot. using LPQ as primary and cm9 latest nightly as secondary
and i note battery drain
MistahBungle said:
No foul on you SD O'C because you've put together some really good threads, but if this is 'sticky worthy' standards have plummeted on XDA. Rapidly. As has been pointed out, there's a couple of links & pretty much no original content or anything that could remotely be considered a 'guide'.
Droidphile's excellent dualbooting post in the Siyah dev thread a few days ago, now that was a guide (and sticky worthy).
Click to expand...
Click to collapse
What post number is it and i can include it and give him full credit, i will of course ask first. Also i would like to point out this was never intended as a guide, more a point of ref.
P.S If LUFC would like to change his mind on this being a sticky then i would have no problem with this.
ashifr5 said:
okay, i am on dual boot. using LPQ as primary and cm9 latest nightly as secondary
and i note battery drain
Click to expand...
Click to collapse
Battery drain has been noted with the kernel, he has made a fix for most roms and combo's but he will need time as it is still in the early stages. Also when flashing a new rom this can alter the casuse battery drain, a full charge of the batter could fix this problem.
MistahBungle said:
Droidphile's excellent dualbooting post in the Siyah dev thread a few days ago, now that was a guide (and sticky worthy).
Click to expand...
Click to collapse
Here it is, for all the non-searchers.
Off-topic again - s.d.oconnor, to quote an earlier post from yourself:
s.d.oconnor said:
Thanks man, the XDA community has give me so much, I just want to give back.
Click to expand...
Click to collapse
If so, what's the "donate to me" banner doing in your signature? Just awaiting love and affection?
You've compiled some useful guides, but let's face it, your work has mainly been collating readily available links and other posts that any reasonable modicum of searching ability could accumulate.
Nothing in the site rules that forbids you to ask for donations, but for what you've done - especially taking into account that you've been a member here for two months - I can think of an awful lot more contributors ("recognised" or not) whom are far more worthy of donations than yourself.
The "giving back to the community" spiel is very valiant and honourable, but you want donations. Fine, sure you've got some too. But don't dress it up behind the "giving back" line - not exactly sincere, no?
Again, I'm not flaming/trolling - merely my opinion.
B3311 said:
Here it is, for all the non-searchers.
Off-topic again - s.d.oconnor, to quote an earlier post from yourself:
If so, what's the "donate to me" banner doing in your signature? Just awaiting love and affection?
You've compiled some useful guides, but let's face it, your work has mainly been collating readily available links and other posts that any reasonable modicum of searching ability could accumulate.
Nothing in the site rules that forbids you to ask for donations, but for what you've done - especially taking into account that you've been a member here for two months - I can think of an awful lot more contributors ("recognised" or not) whom are far more worthy of donations than yourself.
The "giving back to the community" spiel is very valiant and honourable, but you want donations. Fine, sure you've got some too. But don't dress it up behind the "giving back" line - not exactly sincere, no?
Again, I'm not flaming/trolling - merely my opinion.
Click to expand...
Click to collapse
Ok, the banner donate to me has been their since i joined as you are giventhe option to include one, i was new (still am), i have not recived any donations, and if i did they would be used to go back to the XDA website, if it offends anyone i will remove the banner. Also if any mod belives that i am not worthy of my title and that my guides are not of the standard that is very good then they can by all means remove them from any sticky they may be on, and remove my title if they see fit.
I know you are saying that you are not flaming me, but it seems to be moving in that direction. I know i have only been here a short while but i belive that what i have done is not that bad of a standard, in the short time i have been here.
Here is just some of what is changed. Mine isn't just a stock port, mine has stuff removed. dave71670's Salty Rom is in the second post.
Now without further ado, here is my V26 Test Release
Wipe Data/Factory Reset/Wipe Dalvik Cache/Flash Rom/Flash Addons/Advanced Fix Permissions In Recovery. If your power button randomly stops working from flashing my rom or anything else happens and you blame me I am going to laugh at you. If you do not know what you are doing, don't attempt to flash it. If you break it you fix it, I will help, but I am not responsible for anything.
My V26 Test Build = http://www.mediafire.com/download.php?iv6mz6cr82l663p
V26 Addons (Same As V25) = http://www.mediafire.com/download.php?ja32agzq3o82ky3
Removed Apps & Files Folder (Some of them are newer than the old folder) = http://www.mediafire.com/?c0f17oxct7dq5
I am calling it a test release at this point, since I haven't ran it more than about an hour. I haven't had any problems though. If coming from CM10 or something else you will more than likely need to flash twice, first flash will go to around 15% and flash the kernel and reboot, second flash will go all the way and say install complete.
Changelog :
Based on 09/04/2012 Helly Bean
MMS updated with pop up notifications
Added https://play.google.com/store/apps/details?id=com.helroz.GSII_Repair&hl=en to the rom since I have noticed people complaining of losing there EFS folder a lot lately. I would download this on your current rom and back it up as long as you imei is correct, just to have it for all future releases of my rom or whoevers rom you decide to go to in case you ever lose your EFS folder which has your IMEI. It is a small app, is free and works great, I tried it by backing it up on my phone and then deleting my efs folder, then restoring it later with this program after I got the generic imei error. Credits go to Helroz for the app
Old Version Still Available V25 Rom = http://www.mediafire.com/download.php?mlet0rdrlduzl8k
My V25 Addons (Same As V24) = http://www.mediafire.com/download.php?0661t2w37jevi98
Link To Folder With Removed Gapps & Files = http://www.mediafire.com/?skubg7sgqbsew[/URL]
Md5 On Rom Zip = 839AC816B9D36E229C4A9344DA54EA33
Changelog =
Compiled from latest source of CM10 which you can find the changelog at http://changelog.bbqdroid.org/#captivatemtd/cm10/next
renamed the two navbar menus
More Build.prop tweaks
Edited Build.Prop Look In About Phone
Kernel in rom is always the latest VC Kernel
Updated GPS Config
Changed Boot Animation, Wait for a few seconds on boot up if you think it froze, It did not.
Changed Modem To KC1
Changed Updater.sh to Flash Modem if you have a modem already installed or not.
I have also created what I would like to call Cbalts Launcher Program. I have 4 launchers in the removed files folder, Apex, Nova, Trebuchet, And Zeam. You can flash any of them and it will remove the default zeam, to get zeam back flash Removal Tool.zip which will remove all 4 of the launchers if you decide to install all four of them at once. Then reflash the launcher of your choice and that will be the only launcher you have. If you do not reflash a launcher after flashing Removal Tool.zip you will not have a launcher. All launchers remove zeam, but the zeam launcher, I set it up that way since zeam is the default launcher. If you want a new launcher, tell me your choice and link me to it and I will make a flashable zip for it.
Removed
Apollo.Apk
CMWallpapers.apk
Development.apk
DevilAppSGS.apk
DevilKernelConfig-0.9.apk
DSPManager.apk
Email.apk
Exchange2.apk
HoloSpiralWallpaper.Apk
Changed LatinIME.apk To Smaller One With English Only
LiveWallpapers.apk
MagicSmokeWallpapers.Apk
Media/Video Folder
NoiseField.apk
Phasebeam.apk
QuickSearchBox.Apk
RomManager.apk
Term.Apk Aka Terminal
Trebuchet.apk in favor of Zeam
VideoEditor.apk
VisualizationWallpapers.apk
VoiceDialer.apk
Replaced Alarms Folder With My Own
It Only Has
Alarm_Beep_02.ogg
Alarm_Buzzer.ogg
Alarm_Classic.ogg
Alarm_Rooster_02.ogg
Beep_Beep_Beep.ogg
Buzzer.ogg
Cesium.ogg
CyanAlarm.ogg
Replaced Notifications Folder With My Own
It Only Has
Altair.ogg
Antares.ogg
Cobalt.ogg
Cricket.ogg
CyanMessage.ogg
Doink.ogg
DontPanic.ogg
PixieDust.ogg
Plastic_Pipe.ogg
Proxima.ogg
Tweeters.ogg
Replaced Ringtones Folder With My Own
It Only Has
Boxbeat.ogg
BussaMove.ogg
Carina.ogg
Enter_the_Nexus.ogg
Girtab.ogg
No_Limits.ogg
Playa.ogg
Pyxis.ogg
Ring_Digital_02.ogg
UrsaMinor.ogg
Replaced UI Folder With My Own
It Only Has
Dock.ogg
LowBattery.ogg
Media_Volume.ogg
Undock.ogg
VideoRecord.ogg
VideoStop.ogg
VolumeIncremental.ogg
Removed From Addons
FaceUnlock Stuff
GenieWidget.Apk
GoogleFeedback.apk
QuickSearchBox.apk
Talk.apk
Talkback.apk
Okay, since someone else already grabbed above me, I gotta say this.
This boot animation (cbalt) is beyond atrocious. The idea is not to have as much **** fly over the screen as possible. The last image looks like a 10 year old + ms paint.
Look at slim ics' animation. That one does it's job, looks good and classy.
I know I'm coming off as a troll, but it needs to be said.
I look forward to the rest of the ROM. Thanks a lot. I do really appreciate it.
I think the separate thread was a good idea.
Cool!
I may check this ROM out.
You may want to create a zip file for those who want to add back on any of the removed stuff.
I woud not need this as I use Titanium Backup.:victory:
factory reset?
is factory reset really necessary? i thought wipe data, cache partition and dalvik would be sufficient. and fix permissions too.
charging my cappy now. will report on the rom later.
hakim7489 said:
is factory reset really necessary? i thought wipe data, cache partition and dalvik would be sufficient. and fix permissions too.
charging my cappy now. will report on the rom later.
Click to expand...
Click to collapse
Probably a wise idea since you are coming from a different JB ROM or an ICS ROM or GB.
I would imagine that subsequent flashes of this ROM would not require a factory reset or /system wipe once you are on this ROM.
hakim7489 said:
is factory reset really necessary? i thought wipe data, cache partition and dalvik would be sufficient. and fix permissions too.
charging my cappy now. will report on the rom later.
Click to expand...
Click to collapse
Wipe data and factory reset are one and the same. Next time you flash take a look in recovery.
dave71670 said:
Wipe data and factory reset are one and the same. Next time you flash take a look in recovery.
Click to expand...
Click to collapse
now that you mentioned it, it does looks familiar 'wipe data / factory reset' in cwm. initially i thought factory reset means formatting internal storage. i don't want that to happen.
networkdood said:
Probably a wise idea since you are coming from a different JB ROM or an ICS ROM or GB.
I would imagine that subsequent flashes of this ROM would not require a factory reset or /system wipe once you are on this ROM.
Click to expand...
Click to collapse
I personally recommend a wipe every update of this rom, just to help avoid issues, since dirty flashing is never ideal. Yes you can dirty flash, would I do it no, I wipe every time even if it is just a little change I did in the rom, I like to try and avoid issues as much as possible.
Full wipe it is - format /system, too?
Anyways, you need to update your sig/link:
I spend most my time in CWM flashing roms. Check Out My Port Of HellyBean Thats Slimmed Down, Pm Me And Tell Me Thanks If You Like Or What You Think I Should Change, If I Get Enough Requests For The Same Thing I Might Do It.http://forum.xda-developers.com/show...84&postcount=1
networkdood said:
Full wipe it is - format /system, too?
Anyways, you need to update your sig/link:
I spend most my time in CWM flashing roms. Check Out My Port Of HellyBean Thats Slimmed Down, Pm Me And Tell Me Thanks If You Like Or What You Think I Should Change, If I Get Enough Requests For The Same Thing I Might Do It.http://forum.xda-developers.com/show...84&postcount=1
Click to expand...
Click to collapse
Yes I would do that to. Why do I need to update my sig? That link works. I still spend most of my time in CWM Flashing roms (mostly my versions though) .
Sounds like you've got a great rom here. The change log is GREATLY appreciated. Could you fill me in on the difference between "my v13" and devil v13 please. Do the "nightly 8/1 changes" apply to only the devil edition or your v13 as well? Thank you!
Sent from my SGH-I897 using xda premium
nadaltennis77 said:
Sounds like you've got a great rom here. The change log is GREATLY appreciated. Could you fill me in on the difference between "my v13" and devil v13 please. Thank you!
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Most of the difference is the stuff that is removed from devils version in my version. There are some other differences, such as some build.prop changes, updater-script changes, gps changes and some other stuff. If you look at the first post it will show must of the stuff I removed.
PS I am working on CWM Flashable Zips to Restore All Apps I removed and then Individual Zips to restore just one app that you want or more than one. Also working on a flashable zip to restore media aka notifications, system sounds etc.
cbalt said:
Most of the difference is the stuff that is removed from devils version in my version. There are some other differences, such as some build.prop changes, updater-script changes, gps changes and some other stuff. If you look at the first post it will show must of the stuff I removed.
PS I am working on CWM Flashable Zips to Restore All Apps I removed and then Individual Zips to restore just one app that you want or more than one. Also working on a flashable zip to restore media aka notifications, system sounds etc.
Click to expand...
Click to collapse
So in the second post, where it says "nightly 1/08/12 changes," do those changes apply to your v13 rom in the first post?
Sent from my SGH-I897 using xda premium
nadaltennis77 said:
So in the second post, where it says "nightly 1/08/12 changes," do those changes apply to your v13 rom in the first post?
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Yes they do, since his rom is my base that I improve more to my liking since I like a slimmer rom personally and dont use all the stuff I removed. He rom is an amazing rom and is perfect if you use all the stuff he includes.
quick question, if i am on Devil Edition V13 Aka 0801 Build, but want to try cbalt's V13 Release, does that require a wipe / factory reset? or could i just wipe cache and dalvik and flash?
pros - quick boot time, snappier than DerTeufel1980's V10 (rom which i was from), benchmarks show better scores than my previous rom (antutu, quadrant, linpack,nenamark,smartbench)
cons- not sure what you want to show in your bootanimation but i've seen better ones. changelog contains negativity. i don't know what happened between you and those 3 people but including rage in your rom does create some perceptions among users, at least me.
nonetheless, keep up the good work! with less anger perhaps
keredini said:
quick question, if i am on Devil Edition V13 Aka 0801 Build, but want to try cbalt's V13 Release, does that require a wipe / factory reset? or could i just wipe cache and dalvik and flash?
Click to expand...
Click to collapse
Full wipe.
hakim7489 said:
pros - quick boot time, snappier than DerTeufel1980's V10 (rom which i was from), benchmarks show better scores than my previous rom (antutu, quadrant, linpack,nenamark,smartbench)
cons- not sure what you want to show in your bootanimation but i've seen better ones. changelog contains negativity. i don't know what happened between you and those 3 people but including rage in your rom does create some perceptions among user, at least me.
nonetheless, keep up the good work! with less anger perhaps
Click to expand...
Click to collapse
Was my first animation, haven't had time to create another one and improve on that one. If you don't like what I put in the changelog and don't like the rom, then don't install it. Simple as that. I make the rom primarily for me and share it to be nice.
Btw im not angry.
Updated OP-Included Folder with all removed files.
Wasn't sure which thread to post in:
Running Der Teufel version and only issue I'm noticing is SDCard not being mounted after a reboot. Have had to go into Settings -> Storage -> select Mount SDCard each time. This also causes my default ringtone/notification to show as "Unknown" and has to be reset.
Anyone else having similar issues?
Like the title says, this is a work in progress and i'm releasing the zip for 4.2.1 for LaNightv9.x. I don't want anyone flashing previous LaNight flash this by mistake thus a new thread. This is a thread for android 4.2.1 only.
LaNight is a pure AOSP build, meaning it is NOT CM or built from CM source, so please do NOT ask for CM features. However, it does use device/hardware files from CM and rest from its own build.. so any device specific problems that is in CM may or may not be in LaNight. If you don't like "pure" AOSP, move on.
Features:
- Android 4.2.1 JellyBean
- Pawtip kernel for 4.2
- Build.prop tweaks
- init.d tweaks
- Galaxy Nexus Tweaked HW Acceleration
- New CM10.1 partition
- Speed and Cleanness of AOSP
- GPS Hack
- KC1 modem
- Stock Fonts
- And a lot more stuff!
What's working:
- Camera
- Logcat
- Sound
- Surface flinger
- Media Scanner
- Touch
- GPS
- Phone
- Internal Storage
- Tether
- Slight problem with Virtual Operators and roaming
- Bluetooth
- Everything
- Settings -> Storage FC
- Mount Ext SD to PC
- WiFi
- Data
- SMS
What's not working:
- Nothing i could find
Download:
- v9.2.1 Download is HERE
- v9.3 Download is HERE
- v9.4.1 Download is HERE
Others:
- Potential WiFi fix for people that don't have their WiFi working from HERE (DO NOT FLASH IF IT'S WORKING!)
- WiFi Fix from paw tip(I don't know what he did there to fix it in his ROM) http://goo.im/devs/pawitp/galaxysmtd_aosp42/fixes/20121125_wifi_fix.zip
- Clock font fix http://forum.xda-developers.com/showpost.php?p=34798184&postcount=55
Screen shots
- http://forum.xda-developers.com/showpost.php?p=34797716&postcount=54
Recommended flash procedure:
- Keep a copy of efs folder for security
- Reboot into recovery
- Make a nand backup before you proceed
- Wipe data/ factory reset
- mount and storage -> Wipe System/cache/data/datadata
- Wipe cache/cache partition
- Advanced -> Wipe dalvik cache
- Wipe voltage cache (If the option is given)
- devil -> run clean NStools options
- devil -> run clean init.d directory
- install rom zip from sdcard
- install rom zip once again if it boots you back in recovery (It's flashing kernel/recovery/partition if it finds an incompatible partition)
Required Set up:
- Settings > developer > background process limit > at most 2
- Settings > developer > Force 4x MSAA
Special thanks to:
Google
Whole CM10 Team
TeamHacksung
Pawtip (For first functional AOSP)
Derteufel (For the kernel and first AOSP rom)
Elitemovil(For the first 4.2 port)
Bigixie
Be18
Steeve76
HP40
iall5tar
mkalter (HW acceleration)
mikel.canovas & H3llstorm(For GPS hack)
Will try it out tomorrow. Thanks for all your hard work ace.
Sent from my SGH-I897 using Tapatalk 2
I will help.
Ace,
I can help a little. I will load this up and try a couple of modems, etc today but the majority of testing will have to wait until tomorrow. Let me know if that is too late. Thanks for the new toy.:victory:
Update:
Got it to boot easily with standard clears and wipes.
Had to revert back to Lanight 8.5 DD to load a GAPPS package and some modems on my SD card, USB doesn't work for me. It comes up and says "Connected as installer" which my PC doesn't recognize. So, I loaded several modems, a couple of GAPPS packages and reflashed. (BTW, if I select MTP in the USB select option, the PC sees the I897 but can't read the memory)
No advanced recovery options, have to power down and 3 button to recovery (Boo!)
KDH_Next_Gen_GAPPS kills the setup wizard.
gapps-jb-20121117-JOP40C-dmd151 loads OK with a couple of force closes, those can be worked through.
No modems install or are recognized.
Manual APNs do not save.
Lockscreen is a little skewed with the clock being partially obscured on wake.
Checking for storage from settings kills settings.apk
More later.. Thanks Ace, most fun I have had all day.
Play around with it that's why I posted here. Try new things and see if you can get it working. And share the findings here.
I will upload test2 today, hopefully the data,phone and storage issue is fixed.
I tried jl3, jk4 and kg3 modems, but none of them worked. This still is a great start. I see great potential with this one. I'll keep trying and reporting.
Maybe try replacing apns-conf.xml in system/etc with cm10 conf?
dave71670 said:
Maybe try replacing apns-conf.xml in system/etc with cm10 conf?
Click to expand...
Click to collapse
Thanks for the tip Dave71670, I will play around more tomorrow but I tried to replace some of the files in the zip and my 7zip or WinRAR couldn't recognize the format of the zipped files. Really weird. I PM'ed Ace on it. I will try more hacking tricks later. I love this kind of stuff.
dave71670 said:
Maybe try replacing apns-conf.xml in system/etc with cm10 conf?
Click to expand...
Click to collapse
Downloading the latest CM10 now. I'll replace the .xml and report back.
Test2 is up Let the testing begin! Changelog for Test2 is huge so I prefer full wipe even if coming from test1.
Many things has been fixed from build.prop to storage and ril related framework issues. I hope the changes will take affect with the boot.
Test2 Changelog:
- Huge fix in build.prop
- Almost Everything ril/storage related in Framework has been hacked to work
- Added init.d fixes
- apns-config.xml has been edited
- Changed the modem
- vold.fstab hacked
- using the ril drivers from pawtip source code
- A lot more things has been changed that I don't remember
- Some drivers were edited to put on forced mode to work with the device
On a side note: I saw pawtip and CM10 jumped in to help bring 4.2 AOSP for I9000 and this is something I appreciate with all my heart's content. I don't have the time to test his build but i'm sure he did a decent job and the word is out he fixed many issues. I will look into his build whenever I get more time. You can flash his build after a minor edit in updater-script then flash the appropriate cappy kernel to make things work if you do decide to try it. Enjoy!
AceofSpades90 said:
Test2 is up Let the testing begin! Changelog for Test2 is huge so I prefer full wipe even if coming from test1.
Many things has been fixed from build.prop to storage and ril related framework issues. I hope the changes will take affect with the boot.
On a side note: I saw pawtip and CM10 jumped in to help bring 4.2 AOSP for I9000 and this is something I appreciate with all my heart's content. I don't have the time to test his build but i'm sure he did a decent job and the word is out he fixed many issues. I will look into his build whenever I get more time. You can flash his build after a minor edit in updater-script then flash the appropriate cappy kernel to make things work if you do decide to try it. Enjoy!
Click to expand...
Click to collapse
Hey Ace, which kernel did you include in your build? I am running aosp with devil and the storage issues are mostly all I'm facing. I think with the correct kernel this issue would be fixed. If you are using stock kernel I will give it a shot.
dave71670 said:
Hey Ace, which kernel did you include in your build? I am running aosp with devil and the storage issues are mostly all I'm facing. I think with the correct kernel this issue would be fixed. If you are using stock kernel I will give it a shot.
Click to expand...
Click to collapse
I'm using Devil3_1.9.1_KLP_cappy_CFS_BLN_CMC_20121119.zip from HERE in test1 and test2 which is the latest for our cappy.
Derteufel said he fixed the mounting points(to make storage work) in his recent release of I9000 1.9.2 but that shouldn't be a problem since I updated Test1 AND Test2 with updated mount points so I don't see the need for 1.9.2 in my build. Everyone still has storage problems with 1.9.2, i'm more interested in pawtip's kernel if he does release it for our devices or I may have to find a way to compile it.
EDIT: Are you saying the data and phone is working for you? If that is the case, can you share how you got it to work?
AceofSpades90 said:
I'm using Devil3_1.9.1_KLP_cappy_CFS_BLN_CMC_20121119.zip from HERE in test1 and test2 which is the latest for our cappy.
Derteufel said he fixed the mounting points(to make storage work) in his recent release of I9000 1.9.2 but that shouldn't be a problem since I updated Test2 with updated mount points so I don't see the need for 1.9.2 in test2. Everyone still has storage problems with 1.9.2, i'm more interested in pawtip's kernel if he does release it for our devices or I may have to find a way to compile it.
Click to expand...
Click to collapse
I am using 1.9.1 as well. I know that pawitp fixed mount points in his kernel so I may have to compile it since he has the source up. I am downloading your build now. Thanks Ace
dave71670 said:
I am using 1.9.1 as well. I know that pawitp fixed mount points in his kernel so I may have to compile it since he has the source up. Thanks Ace
Click to expand...
Click to collapse
Thanks for always helping me out lol. Can't appreciate enough.
AceofSpades90 said:
Thanks for always helping me out lol. Can't appreciate enough.
Click to expand...
Click to collapse
No problem. I am getting file for repo now. I will let you know how it goes.
Edit: Just saw your edit. I am using a modified version of pawitp's build. It is the ril changes that he made to get data and phone to work.
dave71670 said:
Edit: Just saw your edit. I am using a modified version of pawitp's build. It is the ril changes that he made to get data and phone to work.
Click to expand...
Click to collapse
oh ok, the only place left untouched is service.jar under framework lol I messed around with pretty much everything I known existed or has to do with ril.
Someone in pawtip thread said he changed his dpi to 210 and the storage worked? Did you try it? Does it work on pawtip release? I'm just curious if dpi has anything to do with it... hmmm..
AceofSpades90 said:
oh ok, the only place left untouched is service.jar under framework lol I messed around with pretty much everything I known existed or has to do with ril.
Someone in pawtip thread said he changed his dpi to 210 and the storage worked? Did you try it? Does it work on pawtip release? I'm just curious if dpi has anything to do with it... hmmm..
Click to expand...
Click to collapse
I just tried and as I suspected dpi didn't make any difference. He has storage working out of the box with his kernel so I think that is where the issue lies.
dave71670 said:
I just tried and as I suspected dpi didn't make any difference. He has storage working out of the box with his kernel so I think that is where the issue lies.
Click to expand...
Click to collapse
lol THANK YOU! I thought I wasn't bright enough for such an original and creative idea haha
Lost Root
Ace,
I lost root when I installed test2. Alot of other things are definitely fixed though. I will play around a bit and see if I can get root back and do some further testing. Great job again.
Looks like a good start, will try when there are less things that don't work. GL.
Devil 1.9.4 released for I9000, flash it and see if the storage issue is resolved.
The original thread is not permitting being opened, so it is time to start fresh.
This thread is for the build, not for anything that is installed after the build.
Packages installed from the site have error report forms on the site as well.
Download:
* Available Build Listings *
Current Build Changes:
Interactive Changelog
* Extras, Error Reporting, Etc *
Next Build Plans:
- Verify camera does not boot in FFC
(Prevent having to clear camera data)
Known Long-term Issues:
- May cause boot loops on device
- Camcorder does not record video
- Netflix / streaming is only sound
- Some feeds become blanked out
Pre-Project Changelog:
- Updated All Apps to Latest
- Hopefully a netflix patch for future releases
- Full Ext 4 Support
- MMS Now Works
- Torch Is Fixed
- RIL/System Files Heavily Modified
- 1x/3G/4G Should Show correctly
- Updated/Tweaked the Menu Settings
- Now is REL, Fixes Google Music, etc
Credits:
Liquid0624 (Working Telephony/Data/SMS/MMS)
[SP]JESTER (1x Data)
CyanogenMod (Build base and modifications)
AOKP (Extended options and modifications)
Aeroevan (Numerous updates and fixes)
github: https://github.com/ThePlayground/
sweet!!!
dirty flash from 12/14 of 12/16 should be ok?
warmonster said:
sweet!!!
dirty flash from 12/14 of 12/16 should be ok?
Click to expand...
Click to collapse
Kinda pointless when 12/19 is up and will be ok.
Sent from my Galaxy Nexus using Tapatalk 2
twistedumbrella said:
Kinda pointless when 12/19 is up and will be ok.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I don't get it still boot looping from dirty flash from 12/6 . Trying wipe reflashing
twistedumbrella said:
Kinda pointless when 12/19 is up and will be ok.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Sweet, thanks!
Clean install boot looping too 12/19 build no extras.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
pakkman said:
Clean install boot looping too 12/19 build no extras.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
There is really nothing I can do about it. I don't get the issue with a clean or dirty install and it's not an issue for everyone so it's hard to pinpoint one change that caused it.
Sent from my Galaxy Nexus using Tapatalk 2
twistedumbrella said:
There is really nothing I can do about it. I don't get the issue with a clean or dirty install and it's not an issue for everyone so it's hard to pinpoint one change that caused it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I hear you. I hope you figure it out. Is there anything I can do to help figure it out?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
pakkman said:
I hear you. I hope you figure it out. Is there anything I can do to help figure it out?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
I'm gonna just post my suggested install procedure here for my rom, and pretty much any rom I install.
Anyhow, not posting this to hijack or interfere in anyone's thread, but more in attempts to help Twisted and you guys maybe get some relief and resolve in regards to these bootloops.
I happen to visit any thread that is active with development for our device, since there are so few.
I know if it were me, I would be frustrated and cofnused by all the varying reports and would be happy to see any sort of resolution.
So this is to hopefully help Twisted and the users, not to try and interfere in any way shape or form.
Take it as you will and try it if you may:
~Suggested Install Procedure~
** PLEASE READ **
____________
Use 4ext Recovery(not really required, but highly recommended!
Select Wipe/Format Menu Option
Wipe cache and dalvik
In the same Wipe/Format Menu: Wipe all partitions except SD
Now back in 4ext main menu: Select Tools
Select Format ext3
Format Cache
Format Data
Format System Now go back to the main menu and select the rom .zip to install
I haven't had any boot loops what so ever. Then again, I'm not dirty flashing, i'm not keeping my data.. I format EVERYTHING but the sd card. So there isn't anything left behind to interfere.
santod040 said:
I'm gonna just post my suggested install procedure here for my rom, and pretty much any rom I install.
The only part I will change for this rom, is the ext4 vs. ext3, as in my current ICS rom, I am stuck with a stock ext3 kernel essentially.
Anyhow, not posting this to hijack or interfere in anyone's thread, but more in attempts to help Twisted and you guys maybe get some relief and resolve in regards to these bootloops.
I happen to visit any thread that is active with development for our device, since there are so few.
I know if it were me, I would be frustrated and cofnused by all the varying reports and would be happy to see any sort of resolution.
So this is to hopefully help Twisted and the users, not to try and interfere in any way shape or form.
Take it as you will and try it if you may:
~Suggested Install Procedure~
** PLEASE READ **
____________
Use 4ext Recovery(not really required, but highly recommended!
Select Wipe/Format Menu Option
Wipe cache and dalvik
In the same Wipe/Format Menu: Wipe all partitions except SD
Now back in 4ext main menu: Select Tools
Select Format ext4 option for Twisted ICS Rom(ext3 for my rom)
Format Cache
Format Data
Format System Now go back to the main menu and select the rom .zip to install
Click to expand...
Click to collapse
I dont get why everyone formats to ext4. All my partitions are ext3. It never seemed to matter much how it's formatted as long as they all get mounted the same.
twistedumbrella said:
I dont get why everyone formats to ext4. All my partitions are ext3. It never seemed to matter much how it's formatted as long as they all get mounted the same.
Click to expand...
Click to collapse
Then perhaps there's the answer....
I assumed you did ext4 as well based on user replies. LOL
Edited the install procedure I posted to reflect that then.
Liquid's original installer would format system as ext4 by default so we just made it a habit to do it anyway.
Edit: I've been formatting ext4 this whole time with no issues. :\
Shadow Death said:
Liquid's original installer would format system as ext4 by default so we just made it a habit to do it anyway.
Edit: I've been formatting ext4 this whole time with no issues. :\
Click to expand...
Click to collapse
Well his installer script, clearly formats the system as ext4, so I don't know.
Sorry, was just trying to help, but it seems it may be somewhat of a mystery mix.
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p25", "0");
ui_print("Mounting System...");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
Since this rom has been out system has been formatting itself in ext4 and it hasn't posed a problem before. I flashed the 12/18 and 12/19 build without any issues. This is coming from NuSense with a full wipe. I do format all except sd twice even though it isn't necessary.
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Well his installer script, clearly formats the system as ext4, so I don't know.
Sorry, was just trying to help, but it seems it may be somewhat of a mystery mix.
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p25", "0");
ui_print("Mounting System...");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
Click to expand...
Click to collapse
I know you meant to help, it just never made sense to me. In theory all that ext4 was really supposed to do was speed up the read / write. It isn't like journaled versus un-journaled or anything huge.
twistedumbrella said:
I know you meant to help, it just never made sense to me. In theory all that ext4 was really supposed to do was speed up the read / write. It isn't like journaled versus un-journaled or anything huge.
Click to expand...
Click to collapse
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system"); could also be an issue. I forget if I changed that to run_program("/sbin/busybox", "mount", "/system");
I did not intend to quote myself. Need more caffeine
santod040 said:
I'm gonna just post my suggested install procedure here for my rom, and pretty much any rom I install.
Anyhow, not posting this to hijack or interfere in anyone's thread, but more in attempts to help Twisted and you guys maybe get some relief and resolve in regards to these bootloops.
I happen to visit any thread that is active with development for our device, since there are so few.
I know if it were me, I would be frustrated and cofnused by all the varying reports and would be happy to see any sort of resolution.
So this is to hopefully help Twisted and the users, not to try and interfere in any way shape or form.
Take it as you will and try it if you may:
~Suggested Install Procedure~
** PLEASE READ **
____________
Use 4ext Recovery(not really required, but highly recommended!
Select Wipe/Format Menu Option
Wipe cache and dalvik
In the same Wipe/Format Menu: Wipe all partitions except SD
Now back in 4ext main menu: Select Tools
Select Format ext3
Format Cache
Format Data
Format System Now go back to the main menu and select the rom .zip to install
Click to expand...
Click to collapse
Well I tried all that no luck. I then tried twrp with same result. While in 4ext I checked info after clean flash and system didn't report any size. Reinstalled again shows correctly but still won't boot. I also tried twisted's lean kernel without sucsess
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
twistedumbrella said:
There is really nothing I can do about it. I don't get the issue with a clean or dirty install and it's not an issue for everyone so it's hard to pinpoint one change that caused it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well this is odd. I was eventually able to get my timing right to catch the output of dmesg from just before the reboot occurs. Looks like I am seeing a kernel oops in the 12/16 and the 12/19 builds (I didn't check 12/14 or 12/18) that I am not seeing in the 12/13 build. I've attached a zip with a copy of one of the output files, in the case that it is useful.
FloatingBusError said:
Well this is odd. I was eventually able to get my timing right to catch the output of dmesg from just before the reboot occurs. Looks like I am seeing a kernel oops in the 12/16 and the 12/19 builds (I didn't check 12/14 or 12/18) that I am not seeing in the 12/13 build. I've attached a zip with a copy of one of the output files, in the case that it is useful.
Click to expand...
Click to collapse
Try this kernel
BE WARNED - THIS WILL ERASE EVERYTHING ON YOUR PHONE. DO NOT ATTEMPT THIS IF YOU HAVE NOT MADE A BACKUP AND/OR ARE NOT READY TO REINSTALL EVERYTHING ON YOUR PHONE FROM SCRATCH.
Credit goes to bbedward for his initial thread regarding this concept.
STATUS:
2017/01/08 - Not liking the performance of my Galaxy S3, so I've ordered a new phone (Huawei P8 Lite) for $58 from eBay! Supposedly brand new. I figured I'd have to give it a try just to see. Once I set this phone up I'll start tinkering with my Nexus 6 again. Phone should arrive around 17 Jan!
FOCUS:
Getting F2FS on ANY ROM, but for my purposes, I'm focused on getting F2FS with Flash Kernel to work on Nitrogen OS (if this can be done, then it can be done with any ROM!)
BASICS:
- Need recovery & kernel that support f2fs (tools + kernel driver version must match or be compatible - not sure what the specifics are yet)
Latest New Info:
- The Flash has said that his kernel and crDroid work with F2FS (I haven't tested it myself yet - this version of crDroid actually specifies F2FS support)
2017/01/08
- Found this thread by NABENDU1. It's for Nexus 4, but it gives some good insight on how F2FS works.
- @vprasad1 found another working combination (post #15) - franco.Kernel - r60 Anykernel 7.1.1 with Danvdh's Stock Lite N6F26Q 7.1.1
Explaining a few details:
The issue here is that the exact version of F2FS tools included in most modded recoveries isn't actually specified (that I have found) and the version of tools that end up in the ROM (/system/bin/), which come from the recovery unless built into the ROM, must be compatible. One of the following is true (not sure which one yet):
- the F2FS tools version must be the same or greater than the kernel driver support version
- the F2FS tools version must be the same or less than the kernel driver support version
- the F2FS tools version must match the kernel driver support version
Given that The Flash is consistently including the latest F2FS support in his kernel, and since I've had the most trouble getting F2FS support to work with his kernel and other ROMs that technically don't support F2FS (using bbedward's method mentioned above - link to thread included) I'm inclined to think that the F2FS tools must be the same or greater version compared to the kernel driver support, though I have no way of confirming this yet. Hopefully I'll have different luck with Flash Kernel v1.7!
========
I used:
- Nexus Root Toolkit v2.1.9
- Nitrogen OS 2016-11-19
- MagiKernel v1.1 Stable-1023
- TWRP 3.0.2-0 (modded by xanaxdroid - thread is here)
(TWRP v3.0.2-0 by xanaxdroid mirror) - the original link is down.
I'll take these down if xanaxdroid asks. I have yet to hear from him...
Steps for clean install (and initial install of F2FS recovery / conversion to F2FS):
1) revert to stock (Nexus Root Toolkit)
2) flash recovery with f2fs support (Nexus Root Toolkit)
3) boot into recovery on device
4) full wipe device (normal wipe)
5) convert /cache & /data to f2fs
6) copy over desired kernel and rom to /sdcard
7) install rom & then kernel
8) run adb commands:
# adb shell
# mount -o rw /system
# cp /sbin/fsck.f2fs /system/bin/
# cp /sbin/mkfs.f2fs /system/bin/
# chmod a+x /system/bin/*f2fs*
9) reboot
========
When changing ROMs/kernel (F2FS recovery already installed):
1) boot into recovery
2) do full wipe (f2fs should have stayed from the first time)
3) install rom & then kernel
4) run adb commands:
# adb shell
# mount -o rw /system
# cp /sbin/fsck.f2fs /system/bin/
# cp /sbin/mkfs.f2fs /system/bin/
# chmod a+x /system/bin/*f2fs*
5) reboot
========
More semi-lengthy explanation about fstab:
bbedward suggests a difference in the fstab as being the primary suspect causing the difference in compatibility. Here's the only difference I could find that seemed to be relevant:
- the fstab that worked (MagiKernel + TWRP v3.0.2-0 (by xanaxdroid) + Nitro OS)
/devices/*/xhci-hcd.0.auto/usb* auto auto defaults voldmanaged=usb:auto
- the fstab that didn't work (Flash Kernel + TWRP v3.0.2-0 (by xanaxdroid) + Nitro OS)
*block/sda* auto auto defaults voldmanaged=usbdisk:auto,noemulatedsd
Both fstab files did clearly have the lines needed to mount /data and /cache as f2fs, but they were identical.
NOTE: I also tried TWRP v3.0.0-0 (by xanaxdroid) with Flash Kernel and still no dice. I'm a fan of Flash Kernel since it's my first custom kernel I've played with. I hope to be able to use it some day with Nitrogen OS! Until then, thanks MagiKernel! (maybe I'll convert??? ) <- MagiKernel development has halted for now
========
What I've tried before:
All of the following implies that I've used the previously mentioned adb commands to copy over the f2fs tools and set the proper permissions.
In my experience, it seems that f2fs requires just the right combination of kernel + recovery. For example I used Nitrogen OS (2016-11-19) + Flash Kernel + mod TWRP 3.0.2-0 and it hasn't worked for me, but Nitrogen OS + MagiKernel + mod TWRP v3.0.2-0 did work. The failure for f2fs to work with Nitro OS + Flash Kernel is very reproducible, as is the success with Nitro OS + MagiKernel. (Again using TWRP v3.0.2-0 modded by xanaxdroid).
Keep in mind that the developer of Flash Kernel (developed by The Flash) has tested his kernel with crDroid (a CyanogenMod base ROM) and it worked for him, but I don't know what version of modded TWRP he was using and what version of f2fs tools were in that recovery. From what I've noticed, there seems to be a fundamental difference with CyanogenMod based ROMs when it comes to f2fs support, either that or there's just a version mismatch of f2fs tools between certain recovery + kernel combos. I don't know enough to understand the difference yet, but it is clear that just because a kernel claims to support f2fs doesn't mean that it will work with any ROM, even if you follow bbedward's tutorial mentioned at the top of this post.
The kernel and the recovery must work together (as in what version of mkfs.f2fs / fsck.f2fs supported by kernel & recovery must match (i think - thanks to bbedward again for this info)). The main issue here is that most modded recovery zips/imgs (that I have found) don't list the version of f2fs tools they have. On the other hand usually you can see this info on the main page of any given kernel developer.
I haven't found any specific rhyme or reason yet, but for those looking for Nitrogen OS (2016-11-19 - Android 7.1 - Nougat) + f2fs, this will help you.
NOTE: I'm a clean-freak, so I enjoy clean flashes, so my instructions are geared toward clean flashes, not dirty flashes. Having said that, doing this with a dirty flash is possible, but it will depend on the ROM/kernel you choose as to the details in how you upgrade/switch the ROM/kernel. Done properly, you should only have to switch file systems once and forego any future wiping of your /sdcard or internal storage.
========
NOTE : You'll know your recovery + kernel combo isn't working right when it takes longer than usual to get off the bootloader screen and start with your ROM's animation boot screen. If it's taking too long, you're probably having everything converted back to ext4.
*** WARNING *** WARNING *** WARNING *** WARNING ***
DO NOT INTERRUPT THIS PROCESS DURING BOOT. If you do then you'll render your /data partition inaccessible. It's still fixable with Nexus Root Toolkit > revert to stock, but that's a pain and it takes a while.
This OP will be updated as new info is uncovered!
Thank you for the updated tutorial and information! Been reading up on the benefits and side effects of f2fs. But wasn't sure on whether to do it. Like you I am on nitrogen ROM, 12.4.26. and am a fan of flash kernel. Il will definitely look into this. Also I notice that the link you posted for magikernel isn't working. Either way huge thank you.
Edit - Just read the original thread. Want to thank you again for hoe you asked for his approval first before making a new thread. Very respectful. Not to say people don't respect devs or users in general. Just wanted to add I appreciate you taking the time to reach out him first prior to making this thread.
Thank you again.
Sent from my Nexus 6 using XDA-Developers mobile app
ozzmanj1 said:
Thank you for the updated tutorial and information! Been reading up on the benefits and side effects of f2fs. But wasn't sure on whether to do it. Like you I am on nitrogen ROM, 12.4.26. and am a fan of flash kernel. Il will definitely look into this. Also I notice that the link you posted for magikernel isn't working. Either way huge thank you.
Edit - Just read the original thread. Want to thank you again for hoe you asked for his approval first before making a new thread. Very respectful. Not to say people don't respect devs or users in general. Just wanted to add I appreciate you taking the time to reach out him first prior to making this thread.
Thank you again.
Click to expand...
Click to collapse
Thanks for the feedback!
I'm still researching a way to get Flash Kernel with Nitro OS + f2fs. I have some ideas. I'll update the first post with any new findings.
Edit: unfortunately MagiKernel is dead. So ill be hot on another trail soon. Also MagiKernel isnt as good as Flash out-of-the-box in my experience so far.
ozzmanj1 said:
Also I notice that the link you posted for magikernel isn't working. Either way huge thank you.
Click to expand...
Click to collapse
I actually just tested the link to MagiKernel on my PC and my phone (on XDA Labs) and it worked fine. Are you using another (older) version of XDA forum viewer?
EDIT: OP updated. The "issues" we all run into is a version mismatch between RECOVERY & KERNEL mostly. As long as RECOVERY & KERNEL f2fs tools match, then you can copy over (mkfs.f2fs & fsck.f2fs) from /sbin/ to /system/bin/ and get any ROM to be compatible with F2FS.
EDIT: modified links and removed "" in URL tags. The quotes were necessary for proper display in the XDA Labs app, but not compatible with XDA Legacy app. I've switched to use XDA legacy!
Will this fix low battery throttling and video recording
PunishedSnake said:
Will this fix low battery throttling and video recording
Click to expand...
Click to collapse
LOL, no.
This won't "fix".... ANYTHING.
In fact, this will very likely BREAK things.
Lol how so
No not breaking things here ... Not any more than usual tinkering under the hood... I'm just trying to flush out bbedward's old thread with some more info...
PunishedSnake said:
Will this fix low battery throttling and video recording
Click to expand...
Click to collapse
To give you an answer, no it won't. This info will only "possibly" help you get a ROM to run on f2fs that was not initially designed to do so.
@ozzmanj1
Well the Nitrogen OS ROM developer just let me know he has no plan to include F2FS tools. Looks like we gotta go with plan B...
TheArkive said:
@ozzmanj1
Well the Nitrogen OS ROM developer just let me know he has no plan to include F2FS tools. Looks like we gotta go with plan B...
Click to expand...
Click to collapse
That is a darn shame. Looking at the comparisons of Ext4 and F2FS and it makes me wonder why it has gone more popular. I appreciate your time and work looking into this. Sadly with my schedule I do not have to do a lot of digging with wife, and kids and works....blah blah....lol. Anyways, thank you for letting me know about Nitro.
Side note, any suggestions on another ROM that you are aware of that supports F2FS?
ozzmanj1 said:
That is a darn shame. Looking at the comparisons of Ext4 and F2FS and it makes me wonder why it has gone more popular. I appreciate your time and work looking into this. Sadly with my schedule I do not have to do a lot of digging with wife, and kids and works....blah blah....lol. Anyways, thank you for letting me know about Nitro.
Side note, any suggestions on another ROM that you are aware of that supports F2FS?
Click to expand...
Click to collapse
The Flash said that latest crDroid worked fine. I haven't been able to confirm yet. I have a new smartphone on the way to setup as my primary phone while I experiment on my Nexus 6. Won't get here until Jan 23rd
TheArkive said:
The Flash said that latest crDroid worked fine. I haven't been able to confirm yet. I have a new smartphone on the way to setup as my primary phone while I experiment on my Nexus 6. Won't get here until Jan 23rd
Click to expand...
Click to collapse
Just came across this new kernel that has f2fs support. Based on flash kernel and afew other kernels.
http://forum.xda-developers.com/showthread.php?t=3526034
Going to look into it as flash kernel may drop nexus 6 support soon due to school obligations
Sent from my Nexus 6 using XDA-Developers mobile app
ozzmanj1 said:
Just came across this new kernel that has f2fs support. Based on flash kernel and afew other kernels.
http://forum.xda-developers.com/showthread.php?t=3526034
Going to look into it as flash kernel may drop nexus 6 support soon due to school obligations
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the news! I'll be checking that out as well.
FYI this works using franco.Kernel - r60 Anykernel 7.1.1 with Danvdh's Stock Lite N6F26Q 7.1.1
Code:
mount | grep f2fs
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6)
I tried Aero 1.0 Linaro kernel with Danvdh's Stock Lite N6F26Q 7.1.1 but it kept forcing /cache and /data to return to ext4.
Could also be that the rom is coded not to allow it as it is not really stable enough. Main reason it is not implemented in Android.
zelendel said:
Could also be that the rom is coded not to allow it as it is not really stable enough. Main reason it is not implemented in Android.
Click to expand...
Click to collapse
Was that in response to my post???
Sent from my SM-N910T using Tapatalk
vprasad1 said:
FYI this works using franco.Kernel - r60 Anykernel 7.1.1 with Danvdh's Stock Lite N6F26Q 7.1.1
I tried Aero 1.0 Linaro kernel with Danvdh's Stock Lite N6F26Q 7.1.1 but it kept forcing /cache and /data to return to ext4.
Click to expand...
Click to collapse
Many thanks for the info! I'm definitely trying to find combinations that in fact do work, and hopefully derive a method for getting it to work on other combinations as well (hopefully).
Thanks again for the help!
TheArkive said:
Many thanks for the info! I'm definitely trying to find combinations that in fact do work, and hopefully derive a method for getting it to work on other combinations as well (hopefully).
Thanks again for the help!
Click to expand...
Click to collapse
Just a quick link I came across. Not sure if it's useful but as it pertains to f2fs I thought I'd share.
https://www.xda-developers.com/xda-...upersu-has-trouble-with-f2fs-data-partitions/
Sent from my Nexus 6 using XDA-Developers Legacy app
What is F2FS
Can Ya Here Me Now