I thank @frantisek.nesveda for his Agnostic-kernel - partition independent kernel flasher on which I base this. I also thank everyone he thanks. Additionally, I thank anyone who posted about F2FS and formatting partitions. I read a lot of threads and I’m sure I gleaned something from everything I read.
For now this has to be done after flashing your preferred firmware (ROM). I recommend you make all your desired changes especially changing kernels.
Copy the files to your sdcard where you typically put flash files. I recommend an external card, because this is the only way I do it and I have not tested the other way. If you put it on your internal card it needs to be outside the /system and /data partitions because you'll lose them during formatting.
Also, I have only tested this on PhilZ Touch 6.58.9 recovery. I would appreciate anyone testing on other recoveries if you find one that supports f2fs.
If you are not on PhilZ 6.58.9, flash the zip and reboot to recovery.
Make a full back up of your ROM.
I also recommend you have an Odin based recovery plan. During my trials I ended up with a blank screen and used Odin to get back. This may not be the case with this latest PhilZ.
Format the partitions to f2fs.
It is in "Wipe and Format Options", then "Custom Format Options" then "Toggle f2fs <-> ext4 migration"
Remember, to format data you pick /sdcard. Also, this will remove everything on your internal card.
See warnings in post #2
I include a testF2FS zip to confirm the formatting.
Then use custom restore to get the data and/or the system from the backup. You can skip cache since it gets rebuilt.
Then flash GS3-F2FS-kernel-fstab-Fixer to adjust the kernel boot image to support the new formats.
This only fixes the fstab and if the kernel does not have f2fs support it will not work.
As always, no one is responsible for what happens to your phone. Everyone does this on their own and at their own risk.
Please do NOT mirror these files.
It appears to only work with the PhilZ recovery I built. If someone finds another please let us know.
Also, it does not work on TouchWiz ROMs. If someone finds one that it does work on please let us know.
Do not use the phone setting Factory Data Reset
XDA:DevDB Information
F2FS, Tool/Utility for the AT&T Samsung Galaxy S III
Contributors
RoryB
Version Information
Status: Beta
Beta Release Date: 2014-11-13
Created 2014-10-21
Last Updated 2014-12-06
Reserved
Latest files on Android File Host
Remember, to format data you pick /sdcard. Also, this will remove everything on your internal card.
Do not factory reset through the phone settings. This appears to format as ext4 and does not keep your formatting.
If you do you would need to try the f2fs fixer before rebooting. I have not so let us know how it goes if you try.
[OLD WAY]
For now this has to be done after flashing your preferred firmware (ROM).
Copy the files to your sdcard where you typically put flash files. I recommend an external card, because this is the only way I do it and I have not tested the other way. Also, I have only tested this on PhilZ Touch 6.48.4 recovery. I would appreciate anyone testing on other recoveries.
Make a full back up of your ROM.
It seems it is best to get everything the way you want before the back up, including any kernel changes.
I also recommend you have an Odin based recovery plan. During my trials I ended up with a blank screen and used Odin to get back.
Flash the zip file for what format you want to change. I include a testF2FS zip to confirm the formatting. For some reason it sometimes takes more than one try to format the partitions. Sometimes rebooting recovery helps before trying to confirm the formatting.
NOTE: Sometimes the phone reboots on its own while formatting. Be prepared to press the home and volume up buttons for two vibrations to get back to recovery. The first is the final power down and the second is the powering up. Remember to wait for the blue text in the upper left corner.
Then I use custom restore to get the data and/or the system from my backup. You can skip cache.
Then I flash GS3-F2FS-kernel-Fixer to adjust the boot image to support the new formats.
This only fixes the fstab and if the kernel does not have f2fs support it will not work. If they are getting upstream changes they should have it.
As always, no one is responsible for what happens to your phone. Everyone does this on their own and at their own risk.
Please do NOT mirror these files.
yahoo!!!! thank you for what had to have been alot of research , testing , and i cant imagine what-nots.:victory:
will try out tonite and report back
err on the side of kindness
Saving my response until after class... Thus is awesome
Sent from my HTC One_M8 using XDA Free mobile app
Look forward to testing tonight! Will post with results when I have them
Sent from my CARBON-SGH-I747
TheSchatz said:
Look forward to testing tonight! Will post with results when I have them
Sent from my CARBON-SGH-I747
Click to expand...
Click to collapse
Two different phone both liquid ROM. F2fs all versus f2fs none
Thanks again Rory!!
Didn't work for me in TWRP, with latest Carbon Nightly. Just finished in about two seconds, and the test zip failed, indicating nothing changed.
Next step is a CWM I guess!
Sent from my CARBON-SGH-I747
TheSchatz said:
Didn't work for me in TWRP, with latest Carbon Nightly. Just finished in about two seconds, and the test zip failed, indicating nothing changed.
Next step is a CWM I guess!
Sent from my CARBON-SGH-I747
Click to expand...
Click to collapse
I tried some stuff before with formatting partitions in twrp and it always failed. Even the newest 8.whatever just freaks out with unrecognized file system. I've not been a fan of philz ever before, but since that's what is working I Will adapt
aircooledbusses said:
I tried some stuff before with formatting partitions in twrp and it always failed. Even the newest 8.whatever just freaks out with unrecognized file system. I've not been a fan of philz ever before, but since that's what is working I Will adapt
Click to expand...
Click to collapse
I guess Philz it is, as latest CWM failed in the same fashion.
Yeah, same here with CWM.
Running vanilla CM11. Took a full nandroid, formatted system, cache, and data with Philz. Restored nandroid, installed latest Quantum kernel and flashed the kernel fix.
Everything is up & running, but performance has downgraded. AnTuTu score down by about 20%. I have seen other f2fs discussions that said it needs time to settle in, so I'll let the phone on all night and check it in the morning.
Just some more scores I am not too sure what to make of. But obviously f2fs has the edge.
Html5 test seems a bit fictitious but again shows f2fs showing some advantage....... If more birds is a good thing that is.
one more to confirm: failed with twrp 2.6.3.1 . tried multiple times. running Q v3.66 with appropriately dated kernels = QK / dkp / BMS .
ohh philzzz , where are you ? time to come and play.!
err on the side of kindness
mrrocketdog said:
one more to confirm: failed with twrp 2.6.3.1 . tried multiple times. running Q v3.66 with appropriately dated kernels = QK / dkp / BMS .
ohh philzzz , where are you ? time to come and play.!
err on the side of kindness
Click to expand...
Click to collapse
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/
I used one for d2lte. Please ignore the update to latest binary message
TheSchatz said:
Didn't work for me in TWRP, with latest Carbon Nightly. Just finished in about two seconds, and the test zip failed, indicating nothing changed.
Next step is a CWM I guess!
Sent from my CARBON-SGH-I747
Click to expand...
Click to collapse
Remember, sometimes it takes a few times. I've been trying things like adding sleeps to "rest" between each format command. It did not help. I sometimes had to format, reboot to recovery, format again and then maybe it showed up as changed.
I think I got things mixed up. I have to set up boot image to support the new format and then flash quantumkernel. I"ll update the first post.
Yup, I use this one https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.zip
RoryB said:
Remember, sometimes it takes a few times. I've been trying things like adding sleeps to "rest" between each format command. It did not help. I sometimes had to format, reboot to recovery, format again and then maybe it showed up as changed.
I think I got things mixed up. I have to set up boot image to support the new format and then flask quantumkernel. I"ll update the first post.
Yup, I use this one https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.zip
Click to expand...
Click to collapse
Well, now I can't get past the kernel splash. Philz finally sees everything as f2fs, but I can't mount data at all... I've managed to royally screw up everything, lol. Off to Odin, I'll try again sometime but it's a no go for now.
Thanks for the files though, I'm really excited for the opportunity!
TheSchatz said:
Well, now I can't get past the kernel splash. Philz finally sees everything as f2fs, but I can't mount data at all... I've managed to royally screw up everything, lol. Off to Odin, I'll try again sometime but it's a no go for now.
Thanks for the files though, I'm really excited for the opportunity!
Click to expand...
Click to collapse
Yes, formatting is a bit wonky but the test zip file is very helpful. After formatting I'd run the test zip till desired partitions showed f2fs and not unknown. I also rebooted recovery before restoring. That custom restore really messed me up and I had to have only one back up to keep stuff straight. Then the fix file and a reboot. I only flashed qk 10.11 after it was all running.
Don't know if This will help anyone but it worked for me.
aircooledbusses said:
Yes, formatting is a bit wonky but the test zip file is very helpful. After formatting I'd run the test zip till desired partitions showed f2fs and not unknown. I also rebooted recovery before restoring. That custom restore really messed me up and I had to have only one back up to keep stuff straight. Then the fix file and a reboot. I only flashed qk 10.11 after it was all running.
Don't know if This will help anyone but it worked for me.
Click to expand...
Click to collapse
Eventually everything read f2fs, but I wasn't doing any data restoration. I was just going to start with a fresh rom install, but that's when I was stuck on the kernel splash with no adb. I'll probably try again tonight after work, maybe I'll have better luck!
Sent from my CARBON-SGH-I747
Many ROMs have format built into their updater script and that would undo your format to f2fs unless the ROM is written to support it.
Related
Post Removed.
Add on
Post Removed.
maybe your phone not bricked
that say on cwm, your cwm cant mount everything right?
what cwm you use?
maybe your cwm doesnt support to mount ext4
because on my cm7 build, all partition will be ext4. except sdcard
have you try to format system, data, cache & sd-ext on your cwm?
now, all your partition must be at RFS again
and how you flash stock rom?
from odin? or?
Post Removed.
InMyBedNow said:
People with this phone, DO NOT FLASH CUSTOM ROMS THAT ARE MADE FOR JUST THE GTS5660 NOT THE M Model. I flashed CM7 ported by phiexz (amazing build btw) and when i wanted to flash back to stock, It bricked.
Click to expand...
Click to collapse
Sorry to hear about your issue but your assumption that you can't use other versions on an "M" is a little bit of a blanket statement. I've tried almost every release made and posted on xda and other than boot loops on occasion haven't had any lasting issues.
I do flash back to the lightly tweaked stock release by Darkshadow once in a while when starting fresh, which IS a "M" only release, but that's just so I have a clean starting point to upgrade from so I have the right WiFi and CSC already installed.
Heck, in my Odin ROM folder I have 7 different main release branches I liked and continue to follow from version to version. 3 of which I still switch between from week to week as new versions come up.
Like most things you just need to read, be careful, and try to know what your doing first. There will ALWAYS be risk, even with a stock ROM, that something will go wrong and brick your system but if you back things up and do your due diligence and wait until a trusted source posts a release with instructions you can mitigate the risk and get support.
As long as you can use Odin, CWM Recovery, or boot into phone you have a very good chance to fix or roll back. Just don't panic and/or fail to wait long enough for things to finish. Sometimes I've had to wait 5 minutes for a loop screen to reboot itself and complete...at other times pulling the battery was the only way to stop things. At other times a reboot into recovery to wipe all info was needed, including mounting all partitions first.
The only "M" versions I'm even aware of all come from Darkshadow....up to version 8 last time I checked.
So...yes...be careful...but to say you can't use GT-S5660 ROMs on a GT-S5660M isn't correct.
InMyBedNow said:
Yeah, from Odin. I'm pretty sure I was using the CWM from your Cm7 build, I installed it by flashing over my old cwm which was this one http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559. I think i semi-bricked by pulling out the battery during bootloop, I shouldn't have. I'll probably sent it in to Samsung since I reflashed everything stock, even the recovery.
Click to expand...
Click to collapse
try to use your old cwm, and go to mount & storage
and you should format system. data & partition
and try to flash stock rom again
are u using adb?
can you paste here your log?
use: adb logcat
maybe i can help you
I thought the "rule" was don't flash the modem/radio - i.e. do a multi file Odin update and select nothing for modem/radio.
I took a stock s5660 2.3.5 rom from this forum and flashed my S5660m in this way, and it's fine.
Post Removed.
Post Removed.
Post Removed.
congratulation man
i'm happy to hear that ^^
Hello All,
I'm not expert in android platform. I found that there are many articles that are talking about F2FS performance in compare to EXT4.
Is there any tool to convert my device t889 to F2FS keeping the same experience? i.e. android 4.3, current ROM DN3 V3.2 LTE, and Kernel AGNI V3.9.4-OC-LTE
Regards
Guys ... Your reply please ... I think this may have significant performance change if it is doable ... Also if there is a way to override all system call to fsync() by fdatasysnc(), it will produce a massive performance change in the whole device
K3A said:
Guys ... Your reply please ... I think this may have significant performance change if it is doable ... Also if there is a way to override all system call to fsync() by fdatasysnc(), it will produce a massive performance change in the whole device
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2631278 try this rom
mattlowry said:
http://forum.xda-developers.com/showthread.php?t=2631278 try this rom
Click to expand...
Click to collapse
I just did the f2fs and had ROM running OK, did not see any improvement so I flashed CWM recovery and tried to restore a nandroid and it failed on data then phone would boot but gave me an error about having to reset phone. So i'm odining+root66ing my Note2 to get back to stock. I assume Im not f2fs any more.
Question? Once you switch to f2fs, do you have to use devil recovery from that point on to flash new roms?
Can some one explain the options to flashing a new roms once on f2fs, ex: what recovery can be used?
Converting to f2fs was not difficult and will do once again when I understand more.
Cheers, they really need a beer mug icon, but jolly face will do.
pvaldeben said:
I just did the f2fs and had ROM running OK, did not see any improvement so I flashed CWM recovery and tried to restore a nandroid and it failed on data then phone would boot but gave me an error about having to reset phone. So i'm odining+root66ing my Note2 to get back to stock. I assume Im not f2fs any more.
Question? Once you switch to f2fs, do you have to use devil recovery from that point on to flash new roms?
Can some one explain the options to flashing a new roms once on f2fs, ex: what recovery can be used?
Converting to f2fs was not difficult and will do once again when I understand more.
Cheers, they really need a beer mug icon, but jolly face will do.
Click to expand...
Click to collapse
Odin will format as ext4. You will need to keep devil recovery in order to keep f2fs as no other recovery can write to f2fs partitions. Ive found though that some zips dont like to install using devil recovery. Once partitions are f2fs, before you can do anything else with another recovery, you need to reformat the partitions back to ext4 ( or go through odin and start all over again lol ).
You will need to use devil and reformat the partitions back as ext4. Then flash cwm / phils touch recovery. Once thats done you can flash a new rom zip. To revert the new rom back to f2fs, Install a compatible kernel (agni and devil so far ), then flash devil f2fs recovery. Reboot to make sure things are working properly. Then reboot into devil recovery to do a nandroid, format f2fs, and restore the new nandroid.
Hope this helps! I just did a write up in the Jedi X2 thread with links.
Dont forget the thaks button
Sent from my SGH-T889 using xda app-developers app
pyraxiate said:
Odin will format as ext4. You will need to keep devil recovery in order to keep f2fs as no other recovery can write to f2fs partitions. Ive found though that some zips dont like to install using devil recovery. Once partitions are f2fs, before you can do anything else with another recovery, you need to reformat the partitions back to ext4 ( or go through odin and start all over again lol ).
You will need to use devil and reformat the partitions back as ext4. Then flash cwm / phils touch recovery. Once thats done you can flash a new rom zip. To revert the new rom back to f2fs, Install a compatible kernel (agni and devil so far ), then flash devil f2fs recovery. Reboot to make sure things are working properly. Then reboot into devil recovery to do a nandroid, format f2fs, and restore the new nandroid.
Hope this helps! I just did a write up in the Jedi X2 thread with links.
Dont forget the thaks button
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Yes Saw your post on JediX2 and used you link to get the devil recovery. really not difficult as you explained it. But just posted my question here as f2fs was deviating from rom thread. Thanks again. Cheers.
Read directions in op from thread provided by matt. Performance gains require a little more than converting file system. Added effort is well worth it.
Bruce lee roy said:
Read directions in op from thread provided by matt. Performance gains require a little more than converting file system. Added effort is well worth it.
Click to expand...
Click to collapse
Shore enough.
I readit and I'm going to try again.
Shore enough.
Yes, I have don't the searches, and tried a ton of stuff including formatting portions. Seems this is working on the international version, and most nexus devices. Is the a thread that might help, or has anyone heard success stories with our device.
I really hate starting new threads, but sgh-i747 seems not to have the information out there for ways to getbf2fs working for data, cache, AND system.
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Information on F2FS
There is some information in the Quantum thread starting with http://forum.xda-developers.com/showpost.php?p=53958476&postcount=17136 and several of the posts following it. I tried to get the ROM running but never could get the kernel to boot.
drbmm said:
There is some information in the Quantum thread starting with http://forum.xda-developers.com/showpost.php?p=53958476&postcount=17136 and several of the posts following it. I tried to get the ROM running but never could get the kernel to boot.
Click to expand...
Click to collapse
Same here.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Yes, I have don't the searches, and tried a ton of stuff including formatting portions. Seems this is working on the international version, and most nexus devices. Is the a thread that might help, or has anyone heard success stories with our device.
I really hate starting new threads, but sgh-i747 seems not to have the information out there for ways to getbf2fs working for data, cache, AND system.
Click to expand...
Click to collapse
Same question here, I can't even find the option to format data partition in f2fs. I installed latest version of TWRP (2.7.1.0) and I looked in Advanced wipes menu, I selected "Change filesystem" option and it showed me the filesystem choice menu, but I only get the option to use ext2, ext3, ext4 or fat, no f2fs option. I also tried with Philz recovery but I see no option for f2fs in it too.
Nico3d3 said:
Same question here, I can't even find the option to format data partition in f2fs. I installed latest version of TWRP (2.7.1.0) and I looked in Advanced wipes menu, I selected "Change filesystem" option and it showed me the filesystem choice menu, but I only get the option to use ext2, ext3, ext4 or fat, no f2fs option. I also tried with Philz recovery but I see no option for f2fs in it too.
Click to expand...
Click to collapse
philz has the option in mount advanced format and you have to toggle ext4-f2fs.
decronic has an successful method for the N5 and has been helpful in supplying tools to convert a rom f2fs and attempting to get me off the ground but the kernel seems to fail on my attempts.
here is a flashable zip to format system, data, and cache for the d2LTE devices. It will completely wipe the internals of the phone so be sure to have an external sd card prepared for your next steps.
"https://www.dropbox.com/s/4beylkg0gvhgitv/Format-All-Partitions-to-F2FS-d2lte.zip">https://www.dropbox.com/s/4beylkg0gvhgitv/Format-All-Partitions-to-F2FS-d2lte.zip
please keep me posted as I would really like to use the full potential of this device.
aircooledbusses said:
please keep me posted as I would really like to use the full potential of this device.
Click to expand...
Click to collapse
Will try when I come back from work. Supposedly CM11 is supported right out of the box, if you use newer than 06/30 version.
I'm attempting to make it work now. I installed Philz Recovery 6.48 instead of 6.26 and I now have the f2fs option. I tried formatting all partitions to f2fs (sytem, data and cache) and I modified the updater script, using the instructions in Quantum Kernel thread, but it failed to boot (won't go past boot splash screen). Now, I'll try to only format /data and /cache partitions.
Edit: using only f2fs on /data and /cache, it won't go past the boot animation. It's a pain in the ass for now, nothing's working.
Nico3d3 said:
I'm attempting to make it work now. I installed Philz Recovery 6.48 instead of 6.26 and I now have the f2fs option. I tried formatting all partitions to f2fs (sytem, data and cache) and I modified the updater script, using the instructions in Quantum Kernel thread, but it failed to boot (won't go past boot splash screen). Now, I'll try to only format /data and /cache partitions.
Edit: using only f2fs on /data and /cache, it won't go past the boot animation. It's a pain in the ass for now, nothing's working.[/QUOTE
try just data. cache always failed for me regardless of the kernel
Click to expand...
Click to collapse
It successfully booted by using f2fs only on /data but it stopped dead in its track, when it showed a screen telling me that encryption is unsucsessful and that I need to perform a factory reset. Looks like there's really no way at all to make it work. Flashing a different kernel didn't change anything.
Nico3d3 said:
It successfully booted by using f2fs only on /data but it stopped dead in its track, when it showed a screen telling me that encryption is unsucsessful and that I need to perform a factory reset. Looks like there's really no way at all to make it work. Flashing a different kernel didn't change anything.
Click to expand...
Click to collapse
No, there is a way. I'm not sure how to get system to stick. S3 mini has it, nexus devices, and others. it will happen soon I'm sure.
Sent from my Nexus 7 using XDA Premium 4 mobile app
thanks for ur efforts.
(trollin).
err on the side of kindness
http://review.cyanogenmod.org/#/c/68382/ maybe we'll be able to get it with what they added on the latest nightly
Quantum 5.2
Has anybody been able to get F2fs working on their s3? I have been experimenting for hours. So far ive gotten an infinite bootlogo formatting to f2fs and installing quantum 5.2. if i convert quantum 5.2 rom to f2fs and install it gets stuck on gimme pwncakes picture (kernel)
Edit: also getting the encryption error when formatting data only
f41lbl0g said:
Has anybody been able to get F2fs working on their s3? I have been experimenting for hours. So far ive gotten an infinite bootlogo formatting to f2fs and installing quantum 5.2. if i convert quantum 5.2 rom to f2fs and install it gets stuck on gimme pwncakes picture (kernel)
Edit: also getting the encryption error when formatting data only
Click to expand...
Click to collapse
Haven't managed to get it working yet.
I tried flashing a recent CM nightly (with the default kernel) in vanilla CWM, Philz Touch CWM, and TWRP and no luck with any of them. Flashing the Format-All-Partitions zip doesn't seem to work, and if I use the F2FS format options already included in Philz Touch, I am never able to mount /system afterwards. I didn't even have the option to switch to the new file system in TWRP.
So I'm not too sure what's going on. Is it a recovery issue? Or is our device somehow permanently limited to what file systems we can choose from? I'm out of ideas at this point.
f2fs s3
Theres barely any roms or kernels that support f2fs for the d2att s3. I think it has to do something with the compatibility of the rom. Pwncakes has said that his kernel does support f2fs, but im confused whether the rom supports f2fs. Also, most of the tools for f2fs are for the nexus devices, so there might be some error in the compatibility of them. Other devices like the i9300 have kernels that support f2fs as well as dualbooting, but it hasn't picked up for the d2att yet.
I'm not positive, but I think the kernel can be either-or, but the ROM can only be one or the other. So the ROM will have to be made specifically for f2fs.
compatibility
Major kernels such as Kt747, leankernel and QuantumKernel all support f2fs, but theres no compatible rom to go with it. I would love the speed boost of f2fs on my phone if it were possible.
The interesting thing is I tried the F2FS ROM converter tool that was posted in the Quantum thread. The output zip looked like it did in fact have some changes to reflect support for the file system, but I still couldn't get past the kernel image on boot with TWRP. With Philz Touch, I was still unable to mount /system after flashing the ROM.
Sent from my SAMSUNG-SGH-I747
I have a feeling that the slimkat rom will work with f2fs. Im going to try it out along with quantum kernel or kt747
f41lbl0g said:
I have a feeling that the slimkat rom will work with f2fs. Im going to try it out along with quantum kernel or kt747
Click to expand...
Click to collapse
please post back your progress. Device maintainer said that it has something to do with the Fstab that is preventing it from working for us.
my expirience with Dechronic's rom converter is that it makes use of a modified boot image. I fear the one I have is too old to working with so I am sort of stuck waiting for a further development. its a shame too, I have a spare S3 I can be a little risky with.
Hi guys, I'm freaking out!
I'm proposing to my girlfriend this weekend and the PacMan ROM I was using (4.4.2 I believe) was lagging/running out of storage, so I decided to flash to the newest 4.4.4 ROM I could find. I wanted to make sure my phone was in tip top shape for the big weekend. I booted into TWRP and took the normal steps to flash (wipe ROM,dalvik,cache) but this time I also decided to delete internal storage because I was running out previously and just kind of wanted a fresh start. I decided to try the MerkMod ROM (4.4.4) w/PA 4.4.4 micro GApps, and everything worked great (fast, no reboots) after flashing....until I tried the camera maybe a day later. I got the 'Can't connect to Camera' error, and freaked out immediately because I need to snap some selfies of the big moment this weekend! I then tried deleting the camera thru Titanium Backup and flashing PA's Google Camera module, which didn't work either.
So then I went through all of the steps to go to ND8 stock from MerkMod as outlined by CNexus in this thread. I also switched to Philz recovery. Unfortunately, the camera would also freeze up/not start on the stock ND8 ROM as well (no explicit 'cant connect to camera error' but the screen was all black and the phone froze up). TW + samsung bloat was literally about to make me throw up, so then I decided to try SlimKat 4.4.4 w/Slim GApps, and I'm still getting the camera error. I deleted the Camera2.apk in SlimSettings and downloaded Google Camera, and that didn't work either.
I have no idea what happened! I don't think there was any physical/water damage to the phone, so I don't think it's a hardware issue. Should I try to go back to an older version of the stock ROM? Did this happen because I deleted my internal storage, or used PA Gapps (I've read that both might have contributed)? If so, how do I fix this!? PLEASE HELP!
riazrahman said:
Hi guys, I'm freaking out!
I'm proposing to my girlfriend this weekend and the PacMan ROM I was using (4.4.2 I believe) was lagging/running out of storage, so I decided to flash to the newest 4.4.4 ROM I could find. I wanted to make sure my phone was in tip top shape for the big weekend. I booted into TWRP and took the normal steps to flash (wipe ROM,dalvik,cache) but this time I also decided to delete internal storage because I was running out previously and just kind of wanted a fresh start. I decided to try the MerkMod ROM (4.4.4) w/PA 4.4.4 micro GApps, and everything worked great (fast, no reboots) after flashing....until I tried the camera maybe a day later. I got the 'Can't connect to Camera' error, and freaked out immediately because I need to snap some selfies of the big moment this weekend! I then tried deleting the camera thru Titanium Backup and flashing PA's Google Camera module, which didn't work either.
So then I went through all of the steps to go to ND8 stock from MerkMod as outlined by CNexus in this thread. I also switched to Philz recovery. Unfortunately, the camera would also freeze up/not start on the stock ND8 ROM as well (no explicit 'cant connect to camera error' but the screen was all black and the phone froze up). TW + samsung bloat was literally about to make me throw up, so then I decided to try SlimKat 4.4.4 w/Slim GApps, and I'm still getting the camera error. I deleted the Camera2.apk in SlimSettings and downloaded Google Camera, and that didn't work either.
I have no idea what happened! I don't think there was any physical/water damage to the phone, so I don't think it's a hardware issue. Should I try to go back to an older version of the stock ROM? Did this happen because I deleted my internal storage, or used PA Gapps (I've read that both might have contributed)? If so, how do I fix this!? PLEASE HELP!
Click to expand...
Click to collapse
Right now, I think the best first step for you would be to try flashing the ROM and GAPPs package with a different recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Navigate to the above link and download the latest zip (not md5) file to flash in your current recovery. Your current recovery will simply flash the zip file and overwrite your current recovery with PhilZ.
I personally can't see a GAPPs package causing that sort of issue, as it is not replacing code, changing libraries, or messing with the kernel. The GAPPs package is simply flashing system apps to the /system folder of the Android OS. Additionally, I use the PA GAPPs package when I flash CM11 nightlies.
A recovery can make all the difference of making sure that the correct files are being flashed to the correct areas and I, personally, find PhilZ to be the most bug-free and user-friendly.
When you boot into PhilZ, make sure you have all the files that you intend to flash on your device.
In PhilZ, the Wipe Data/Factory Reset option actually has an option to wipe the device to install a new ROM. Use that option
Install your ROM of choice and your GAPPs package. Reboot and see what happens.
Also, just had a passing thought: Did you flash a custom kernel? Did you not make a backup of your last working setup?
Higgs_Boson said:
Right now, I think the best first step for you would be to try flashing the ROM and GAPPs package with a different recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Navigate to the above link and download the latest zip (not md5) file to flash in your current recovery. Your current recovery will simply flash the zip file and overwrite your current recovery with PhilZ.
I personally can't see a GAPPs package causing that sort of issue, as it is not replacing code, changing libraries, or messing with the kernel. The GAPPs package is simply flashing system apps to the /system folder of the Android OS. Additionally, I use the PA GAPPs package when I flash CM11 nightlies.
A recovery can make all the difference of making sure that the correct files are being flashed to the correct areas and I, personally, find PhilZ to be the most bug-free and user-friendly.
When you boot into PhilZ, make sure you have all the files that you intend to flash on your device.
In PhilZ, the Wipe Data/Factory Reset option actually has an option to wipe the device to install a new ROM. Use that option
Install your ROM of choice and your GAPPs package. Reboot and see what happens.
Also, just had a passing thought: Did you flash a custom kernel? Did you not make a backup of your last working setup?
Click to expand...
Click to collapse
Thanks for your prompt and detailed reply! I did switch to Philz recovery after Odining to ND8, but I'll try again using the link you provided. Unfortunately I never made a backup, my mistake. I never explicitly tried a custom kernel, could my initial flash to MerkMod have changed the kernel?
riazrahman said:
Thanks for your prompt and detailed reply! I did switch to Philz recovery after Odining to ND8, but I'll try again using the link you provided. Unfortunately I never made a backup, my mistake. I never explicitly tried a custom kernel, could my initial flash to MerkMod have changed the kernel?
Click to expand...
Click to collapse
Sorry. After re-reading your post, I do see where you mentioned switching to PhilZ. However, please make sure that you have the latest version of PhilZ (which can be found at the link I previously provided).
After reading up on MerkMod, I have no reason to believe that ROM to be the cause of your issues. It is OMNI ROM-based and I have run OMNI ROM on my device without any issues. I, personally, use CM11 as my daily driver. But, as long as you are using the latest PhilZ recovery and flashing D2LTE ROMs to your device, there should be no issue. Also, make sure the GAPPs package you are using matches the Android version of the ROM you are flashing (e.g. 4.4.4 GAPPs --> 4.4.4 ROM)
If you download the .MD5 version of PhilZ, you can flash that via ODIN. Good luck to you.
Also, forgot to mention it in my previous post, but congratulations in advance on your engagement!
I don't think there's much to help here with. You said you odined to stock ND8 and still had the error. At that point, it definitely sounds hardware related and I would say that something is wrong with the device itself.
CNexus said:
I don't think there's much to help here with. You said you odined to stock ND8 and still had the error. At that point, it definitely sounds hardware related and I would say that something is wrong with the device itself.
Click to expand...
Click to collapse
Ah that's what I was afraid of :crying: I reflashed Philz and installed CM11 nightly with PA micro gapps 4.4.4 and am still getting the same issue. I did read a thread that mentioned something that Gummy ROM was the only one to work for someone in a similar situation, so I may try that. Then I think I'll try Odin to ND8 one more time just in case, and then just give up. I guess I can try to borrow a digital camera from a friend. I do still have a TEP plan with sprint so maybe they can replace the camera module at my local store without me having to pay the ridiculous $100 deductible.
One last thing, if this was kernel related, what's a good kernel for me to try?
Thank you both for your time and insight.
riazrahman said:
Ah that's what I was afraid of :crying: I reflashed Philz and installed CM11 nightly with PA micro gapps 4.4.4 and am still getting the same issue. I did read a thread that mentioned something that Gummy ROM was the only one to work for someone in a similar situation, so I may try that. Then I think I'll try Odin to ND8 one more time just in case, and then just give up. I guess I can try to borrow a digital camera from a friend. I do still have a TEP plan with sprint so maybe they can replace the camera module at my local store without me having to pay the ridiculous $100 deductible.
One last thing, if this was kernel related, what's a good kernel for me to try?
Thank you both for your time and insight.
Click to expand...
Click to collapse
Not likely that it's kernel related if the standard kernel with CM11 didn't work. You can always try the DKP kernel, which I use, found here in the Sprint S3 development forum.
Higgs_Boson said:
Not likely that it's kernel related if the standard kernel with CM11 didn't work. You can always try the DKP kernel, which I use, found here in the Sprint S3 development forum.
Click to expand...
Click to collapse
Ah understood, well I just tried GummyROM and Odined to ND8 again and still no dice, so I gave up on blaming the kernel. I just don't get it...if it's a hardware issue would both of my cameras go out? Shouldn't I still be able to access the front camera if theres a short or something in my rear camera? I feel like my phone just doesn't know theres cameras attached to it because I deleted something I shouldn't have while flashing the first time around.
One last question before I try the Sprint store tomorrow...while I was using Odin I saw the re-partition option. Now I know I shouldn't touch that unless I have a .pit file, so I left it unchecked this time. However, if I did track down a pit file, could repartitioning potentially solve this issue?
riazrahman said:
Ah understood, well I just tried GummyROM and Odined to ND8 again and still no dice, so I gave up on blaming the kernel. I just don't get it...if it's a hardware issue would both of my cameras go out? Shouldn't I still be able to access the front camera if theres a short or something in my rear camera? I feel like my phone just doesn't know theres cameras attached to it because I deleted something I shouldn't have while flashing the first time around.
One last question before I try the Sprint store tomorrow...while I was using Odin I saw the re-partition option. Now I know I shouldn't touch that unless I have a .pit file, so I left it unchecked this time. However, if I did track down a pit file, could repartitioning potentially solve this issue?
Click to expand...
Click to collapse
The only thing that repartitioning will do is restore the memory partitions in your phone in the event that one of the partitions became corrupted.
This is essentially what a PIT would be restoring:
Code:
sprint # cat parted.txt
cat parted.txt
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 30777344s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8192s 131071s 122880s modem
2 131072s 131327s 256s sbl1
3 131328s 131839s 512s sbl2
4 131840s 132863s 1024s sbl3
5 132864s 136959s 4096s aboot
6 136960s 137983s 1024s rpm
7 137984s 158463s 20480s boot
8 158464s 159487s 1024s tz
9 159488s 160511s 1024s pad
10 160512s 180991s 20480s param
11 180992s 208895s 27904s ext4 efs
12 208896s 215039s 6144s modemst1
13 215040s 221183s 6144s modemst2
14 221184s 3293183s 3072000s ext4 system
15 3293184s 28958719s 25665536s ext4 userdata
16 28958720s 28975103s 16384s ext4 persist
17 28975104s 30695423s 1720320s ext4 cache
18 30695424s 30715903s 20480s recovery
19 30715904s 30736383s 20480s fota
20 30736384s 30748671s 12288s backup
21 30748672s 30754815s 6144s fsg
22 30754816s 30754831s 16s ssd
23 30754832s 30765071s 10240s grow
Info credit: http://androidforums.com/virgin-mob...ameleon-some-efs-imei-info-brick-backups.html
Hence, I have no reason to believe this would help you.
Temporarily forget it. Link removed.
TWRP 2.8 v2 for e980.
Fixed auto-loki support.(But there will be a weird floating loki option, i will fix the position of it when i have time)
Should be no longer have secure boot issue after flashing kernel.
Reboot-into-recovery-loop bug still presents, always prepare madmack's twrp for e986 hack, in case boot-loop happens!
When recovery-loop happens, please flash madmack's hacked TWRP 2.6 for e986(please see post #23), then reboot into madmack recovery(you can install back my recovery in this step), reboot system, the recovery-loop will stop.
I am not able to solve this bug, as with Philz touch also has this bug and never solved.
**This recovery will only cause recovery-loop. All other bootloop will not be cause by this recovery!**
**I held no responsibility for any damage due to the use of this recovery.**
Features:
1)Full nandroid backup is much faster on TWRP than on CWM / PHILIPS TOUCH.
2)Ability to format any partition into F2FS/EXFAT/FAT/EXT2/EXT3/EXT4, and read/write all these format partitions.(don't use F2FS format until a compatible kernel and rom come out.)(I am using stock at this moment, still love stock, but failed to make stock rom fully compatible with F2FS, what a pity!)
Download it from attachment.
Backup anythings important.
Flash through recovery.
Enjoy!
Wing
P.S. I am **not** a developer, so I **may not be able to** fix any bugs if you encounter!
P.S. Again, i am using phone network at home, which have data usage limit, so the source will be uploaded when i can use wifi.
P.S.I am not programmer, I used very long time to understand what is what, if you think this recovery is useful, consider make a donation!
Wow, thanks! Working great!
Wow .thank you so much .already flashed waiting for new build to test .will report back .thanks again
---------- Post added at 03:01 AM ---------- Previous post was at 03:00 AM ----------
Keep this thread alive
Actually, the thing i actually want/try to do is to add F2FS support to CM kernel and whole CM rom.
Since i am not a developer, i use a lot of time try to figure out what need to patch and failed.
I used too much time and can't understand what make the compile fail and give up.
Then I do the next thing I want to do: compile a fully working twrp to replace the easily boot-loop PhilZ Touch recovery.
This TWRP is actually a side product of my failure attempt.
(ha, i still don't have right to post external links, so i will put the TWRP e980 compile method and source up later)
Wing
Great job man .thanks
mukwing said:
Actually, the thing i actually want/try to do is to add F2FS support to CM kernel and whole CM rom.
Since i am not a developer, i use a lot of time try to figure out what need to patch and failed.
I used too much time and can't understand what make the compile fail and give up.
Then I do the next thing I want to do: compile a fully working twrp to replace the easily boot-loop PhilZ Touch recovery.
This TWRP is actually a side product of my failure attempt.
(ha, i still don't have right to post external links, so i will put the TWRP e980 compile method and source up later)
Wing
Click to expand...
Click to collapse
how did u build i could help i have linux on virtual mmachine on windows 8.1
bountyman334 said:
how did u build i could help i have linux on virtual mmachine on windows 8.1
Click to expand...
Click to collapse
Attached is the patch file for cm kernel to make it support F2FS.(I forget where to get)
Not all codes can be patched sucessfully, some I need to modify the kernel sources by hand.
It seems some codes will lead to compile error, but i am not programmer, I don't know how to adjust.
I am using up-to-date CM sources, without modification, i can compile unofficial cm build successfully for my own test.
Wing
Forget this patch. I think this patch might be outdated.
I am trying to investigate the commits about F2FS in Nexus 5 CM F2FS kernel sources.
Will try to merge these commits to see if it can compile.
If I sucessfully getting a F2FS supported CM kernel, will try to make a F2FS supported TWRP.
Making CM rom to support F2FS seems to be easy, there exists some tools ready to do it.
Wing
Thank you so much for you hard work
I finally learned how to correctly patch kernel commits!
Good news. A F2FS suppported kernel has been successfully compiled!
(need testing, but need to compile F2FS suppported TWRP and ROM before i can test.)
Next step, F2FS suppported TWRP.
Wing
I can't find resources of how to modify TWRP 2.8.0.0 to support F2FS for our device.
But the modified KT-TWRP from the following
http://forum.xda-developers.com/showthread.php?t=2778248
I can compile it successfully against e980 CM sources.
So, I get F2FS supported TW-TWRP working on my phone.
I still haven't try format partition to F2FS.
Will report if it works later.
I don't want to be another failure, used me sooooo much time to research.
Wing
version?
It says in the flash screen that it is madmack's 2.6.1.0 only.
I am confused..
Edit - but the recovery header says it is 2.8.0.0
XD
Edit 2 - It has messed up with the phone. Not able to get into the ROM. only boots into the recovery. Tried philz recovery and then tried to boot again but it isn't working anymore.
mukuluppal said:
It says in the flash screen that it is madmack's 2.6.1.0 only.
I am confused..
Edit - but the recovery header says it is 2.8.0.0
XD
Edit 2 - It has messed up with the phone. Not able to get into the ROM. only boots into the recovery. Tried philz recovery and then tried to boot again but it isn't working anymore.
Click to expand...
Click to collapse
It say madmack's 2.6.1.0 because i use madmack's old zip and replaced the recovery.
If in the boot-into-recovery loop, install philz recovery, then install TWRP again should fix it?
BTW, is it caused by wiping of /data?
Again, i am not programmer. I will try to find out reason to see if i can fix it.
Wing
mukwing said:
It say madmack's 2.6.1.0 because i use madmack's old zip and replaced the recovery.
If in the boot-into-recovery loop, install philz recovery, then install TWRP again should fix it?
BTW, is it caused by wiping of /data?
Wing
Click to expand...
Click to collapse
Yeah i tried that and it didn't work.
So i tried a bunch of my old recoveries and the twrp e986 hacked one worked.
Now i can see ext card too in twrp. But that's not your recovery. It's old one.
No it didn't happen coz of wipe data.. After flashing it,the recovery boot started.
Failed to find out why has this bug on this recovery. Sorry.
Btw, testing of F2FS gave me soft brick of my phone. When I returned to stock, I surely love the smoothness of original stock lg 4.1.2. So I may stay with stock for a while.
When I feel too boring with stock again, I will return to cm and try compiling something to have fun again.
recovery updated.
please test!
Wing
If anyone tests this out let me know if the Loki works because last time I tried it it made my phone soft brick. It was an easy fix to unbrick it but I'm hoping it doesn't do that anymore.
mukwing said:
recovery updated.
please test!
Wing
Click to expand...
Click to collapse
So..
If you go to install,there is a "Loki support" floating checkbox that won't go away...
If you try to Enable MTP and actually try to copy something to internal SD card, recovery reboots and copy fails (I noticed that you can still delete stuff).
It also got me a bootloop when flashing a rom, I had to recover through download mode and a KDZ...
Bunch of issues that are pretty noticeable, OP,are you even testing this on your phone before sending it out risking other phones?
The floating Loki doesn't affect the usage much.
And the boot loop have been mentioned using madmack 2.6 e986 to solved.
Sorry, will never share anything again.
Jeez....
2SHAYNEZ