Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
Latest Builds Here
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.[/QUOTE]
Links are up enjoy the light show
Twrp now has haptic feedback.
Wow...first post. I thought this would explode...Lol.
Great job dev.
Like the haptic... Thanx!
Sent from my SPH-D710
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
EVObastard said:
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
Click to expand...
Click to collapse
This recovery is pretty useless if you're not going to flash a Kit Kat ROM.
HighxVoltage said:
This recovery is pretty useless if you're not going to flash a Kit Kat ROM.
Click to expand...
Click to collapse
It works to flash jb+ I first built twrp when I was on stock then I flashed jb and went to 4.4
Sent from my SPH-D710 using Tapatalk
This is a repost of the twrp from a while back right?
sent from tumblr
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
EVObastard said:
Hmm, the dl link is taking me to version 6.3 and for some reason I can not get it to stick. I'm messing with my E4GT (not what's in my sig.) I've installed the BlueKuban and for some reason can't get rid of Agats recovery, not that I need to it is working fine but I like the touch recovery. Any ideas, just reboot to recovery and flash right?
Oh yeah, I also tried using goo but it said it could not find a compatible version for my phone.
Click to expand...
Click to collapse
I've used an older version of twrp. I install it through Odin then upgrade to this one.
sent from tumblr
@Linux guy this is a new build hint why it has haptic feedback.
Sent from my SPH-D710 using Tapatalk
Working great on my E4GT. Thanks
☞"And on the eight day the Lord made a backup"☜
Any chance for v2.7.0.0 in the near future?
CrimsonKnight13 said:
Any chance for v2.7.0.0 in the near future?
Click to expand...
Click to collapse
This is 2.7 basically I wait for major changes but probably in a week
Unjustified Dev said:
This is 2.7 basically I wait for major changes but probably in a week
Click to expand...
Click to collapse
Thanks! I look forward to your next release.
Any updates regarding 2.7 being compiled & released?
How does one flash this?
I downloaded the file, but don't see any instructions on how to flash this on the phone. I installed Goo Manager. From the menu, when I select "Install OpenRecoveryScript", I get the toast "No recoveries were found for your device"
os2baba said:
I downloaded the file, but don't see any instructions on how to flash this on the phone. I installed Goo Manager. From the menu, when I select "Install OpenRecoveryScript", I get the toast "No recoveries were found for your device"
Click to expand...
Click to collapse
Can't use goo for this phone... Simply install it from the current recovery you have now...
Sent from my SPH-D710 using Tapatalk
dirtyhewr said:
Can't use goo for this phone... Simply install it from the current recovery you have now...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I don't have the phone with me. But it looks like I have the stock recovery. At least it doesn't look like either CWM or TWRP. I downloaded it as a zip file (Twrp_6.3_Unofficial_20140211_d710.zip) from http://www.androidfilehost.com/?w=files&flid=12045. Should I just rename it as update.zip and install it from the stock recovery?
os2baba said:
I don't have the phone with me. But it looks like I have the stock recovery. At least it doesn't look like either CWM or TWRP. I downloaded it as a zip file (Twrp_6.3_Unofficial_20140211_d710.zip) from http://www.androidfilehost.com/?w=files&flid=12045. Should I just rename it as update.zip and install it from the stock recovery?
Click to expand...
Click to collapse
This is not for stock ROMs. You should probably read up some more in this device
Trolling from my SPH-D710 using Tapatalk
Surj138 said:
This is not for stock ROMs. You should probably read up some more in this device
Trolling from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Okay. Thanks. I'm a long time Android user (from G1 days). New to the S2 though. I have to use the S2 for a couple of months. I thought of installing Cyanogenmod KitKat. But lack of 4G is a deal killer. So I'm probably going to stick with the stock ROM. I just wanted to use TWRP so I can do system backups. From what you are saying, that doesn't seem to be an option. Strange. I have never had this issue on any other phone. I have changed the recovery on G1, HTC G2, Vibrant, Galaxy S3, LG G2, HTC One, Nexus 4, 4, 7, 10. I'll have to read up to see why I can't do that on the Galaxy S2.
os2baba said:
Okay. Thanks. I'm a long time Android user (from G1 days). New to the S2 though. I have to use the S2 for a couple of months. I thought of installing Cyanogenmod KitKat. But lack of 4G is a deal killer. So I'm probably going to stick with the stock ROM. I just wanted to use TWRP so I can do system backups. From what you are saying, that doesn't seem to be an option. Strange. I have never had this issue on any other phone. I have changed the recovery on G1, HTC G2, Vibrant, Galaxy S3, LG G2, HTC One, Nexus 4, 4, 7, 10. I'll have to read up to see why I can't do that on the Galaxy S2.
Click to expand...
Click to collapse
This device is different because the recovery comes bundled with the kernel. This particular recovery is only for kk aosp ROMs... It overwrites the recovery those ROMs come with (CWM).
There are custom kernels for stock ROMs that come with a custom recovery. If you're on stock JB I recommend Agats 1.3
Trolling from my SPH-D710 using Tapatalk
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.
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.
Would it be possible to format the file system on this tablet for use with F2FS and how would I go by doing so if yes?
Grizzly6117 said:
Would it be possible to format the file system on this tablet for use with F2FS and how would I go by doing so if yes?
Click to expand...
Click to collapse
You'd need a custom Kernel.....I'm not aware of one that supports F2FS but can I ask a dumb question....why? There's still no Stable release out yet is there?
Yes. In addition to a F2FS enabled custom kernel, you would require an enabled custom recovery.
My SkyHigh kernel has in built F2FS support but never tested
UpInTheAir said:
Yes. In addition to a F2FS enabled custom kernel, you would require an enabled custom recovery.
My SkyHigh kernel has in built F2FS support but never tested
Click to expand...
Click to collapse
Yeah, I know by my post that I made my self to be clueless on things like this just wanted to see if people have already tested on this for this, I'm considering changing one of the ROMs to f2fs and test your kernel for f2fs compatibility, I'm just worried about bricking as I am on contract with this device but I don't see why I couldn't recover everything flashing stock with Samsung kies
F2FS
I managed to convert SuperSamsung v2 to F2FS by using a F2FS converter script I got from the Nexus 7 side of the forums and used your latest SkyHighKernel to boot into F2FS succesfully
EDIT: Feels snappier and less stutter, the major improvement atm is App Loading times
Grizzly6117 said:
I managed to convert SuperSamsung v2 to F2FS by using a F2FS converter script I got from the Nexus 7 side of the forums and used your latest SkyHighKernel to boot into F2FS succesfully
EDIT: Feels snappier and less stutter, the major improvement atm is App Loading times
Click to expand...
Click to collapse
Sweet. Can you please link to the script thread, and did you need to modify it for our device partition table?
UpInTheAir said:
Sweet. Can you please link to the script thread, and did you need to modify it for our device partition table?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2731666
Thats the Script I used, didnt change anything, but during the process when it asks what boot.img to use, you can select to use your own, and I simply just pulled it from your Kernel and placed into the folder directory, but I did flash the kernel zip anyway once flashing the ROM, I changed System and Cache to F2FS first, flashed ROM etc. then rebooted recovery and converted Data to F2FS, which wipes everything on internel Memory, so i kept my backup of everything on my External SD
Grizzly6117 said:
http://forum.xda-developers.com/showthread.php?t=2731666
Thats the Script I used, didnt change anything, but during the process when it asks what boot.img to use, you can select to use your own, and I simply just pulled it from your Kernel and placed into the folder directory, but I did flash the kernel zip anyway once flashing the ROM, I changed System and Cache to F2FS first, flashed ROM etc. then rebooted recovery and converted Data to F2FS, which wipes everything on internel Memory, so i kept my backup of everything on my External SD
Click to expand...
Click to collapse
Good stuff. Glad the kernel worked so far.
Another nice (treble) ROM for Oneplus5 (cheeseburger).
No fancy intro, no long list of features...just try it for a couple of days and if you don't like it - toss it and restore your previous rom!
ROM: https://androidfilehost.com/?fid=11410963190603857500
built using
- ROM source: https://github.com/TeamHorizon
- Krieg kernel: https://github.com/Krieg-Kernel
- GZOSP: https://github.com/GZOSP-Devices
It's still in its early 9.0 stage, not many settings are implemented yet. I can only promise to post a fresh build as the dev.team adds new features.
Tried & tested on my own OP5 (decrypted) after having installed OB19 firmware (tried also 5.1.5 and it's ok, too).
IF YOUR device satisfies those conditions then, installation is straightforward:
1. In TWRP wipe dalvik/cache/system/data/vendor
2. In TWRP -> install ROM and (if you wish) opengapps/magisk
3. add noverity
4. flash
5. reboot
6. enjoy your new ROM
sha fa ！chinese man will try
Added to the OnePlus 5 Index Thread here.
quake73 said:
Another nice (treble) ROM for Oneplus5 (cheeseburger).
No fancy intro, no long list of features...just try it for a couple of days and if you don't like it - toss it and restore your previous rom!
ROM: https://androidfilehost.com/?fid=1322778262904025974
built using
- ROM source: https://github.com/TeamHorizon
- Krieg kernel: https://github.com/Krieg-Kernel
- GZOSP: https://github.com/GZOSP-Devices
...
Click to expand...
Click to collapse
Excellent new rom and like the mantainer (you other roms)
All is fine, there already all the stuff for a daily usage, really (AOD, AudioFX, QS Columns/Rows numbers, etc)
Just a little thing for me is essential for keep this rom :
- Disable / Enable HW Buttons & Backlight
- Button Mapper
Good job mate, for sure i will try the others builds
Hello
It's looking a good base with stable kernel, but need to fix :
- battery menu crashes
- no traffic in/out visible after activation
- notification slider button on side left are not working
Can you check?
Thanks
Try
I'd try it later.
https://androidfilehost.com/?fid=1322778262904029541
I tried to 'fix' the slider but it doesn't work as it should
The phone reacts to the notif.switch but stays at 'mute' when you go back to the bottom position.
here's another build:
https://androidfilehost.com/?fid=11410963190603845568
November 5, 2018 security patch; android branch android-9.0.0_r16.
https://androidfilehost.com/?fid=11410963190603846419
Noob question, but in TWRP what partitions do you need to backup (treble rom) in order to restore it, should you not like the new rom you've just flashed (so to speak)
As I'm using the latest Blu_Spark TWRP, but a little unsure of what to back up... some info here, but to be honest it not really that clear (unless i'm misreading it) : https://forum.xda-developers.com/pr...o-choose-nandroid-backup-twrp-please-t3839546
Thanks.
L22EEW said:
Noob question, but in TWRP what partitions do you need to backup (treble rom) in order to restore it, should you not like the new rom you've just flashed (so to speak)
As I'm using the latest Blu_Spark TWRP, but a little unsure of what to back up... some info here, but to be honest it not really that clear (unless i'm misreading it) : https://forum.xda-developers.com/pr...o-choose-nandroid-backup-twrp-please-t3839546
Thanks.
Click to expand...
Click to collapse
The ones that are selected as default are enough. I have the latest twrp from codeworx and on backup, the selected partitions are: boot/system/data. In previous versions of twrp (from codeworkx) there was also vendor partition. Here's also a pic of my twrp screen when i do backup.
quake73 said:
The ones that are selected as default are enough. I have the latest twrp from codeworx and on backup, the selected partitions are: boot/system/data. In previous versions of twrp (from codeworkx) there was also vendor partition. Here's also a pic of my twrp screen when i do backup.
Click to expand...
Click to collapse
Thanks.
Yes it's the vendor partition that's a grey area for me. As I know the vendor partition is for treble enabled roms (I believe).
So if I was to backup Boot, System and Data (like your photo), then backed that backup to a PC (not forgetting the contents of the SD card folder), did a Format data, flashed a new rom and disliked it (as I do flashing between roms). All I would need to do it copy the TWRP backup back onto the phone, and restore that backup via the TWRP. I know it's pretty simple, but always best to be sure.
L22EEW said:
Thanks.
Yes it's the vendor partition that's a grey area for me. As I know the vendor partition is for treble enabled roms (I believe).
So if I was to backup Boot, System and Data (like your photo), then backed that backup to a PC (not forgetting the contents of the SD card folder), did a Format data, flashed a new rom and disliked it (as I do flashing between roms). All I would need to do it copy the TWRP backup back onto the phone, and restore that backup via the TWRP. I know it's pretty simple, but always best to be sure.
Click to expand...
Click to collapse
You dont have to format data if switching between custom roms. Do a backup of your current rom (if your twrp version has also a "vendor" partition selected then leave that, too). Then just follow the standard procedure: wipe system/data/cache/dalvik, flash the new rom and your twrp backup(s) will still be there. But if you FORMAT data, as you said, then of course you need to first save the twrp backups to your pc.
Today's build:
https://androidfilehost.com/?fid=11410963190603857500
any newer builds for this ROM since 24 NOV 2018 ?
metaxda said:
any newer builds for this ROM since 24 NOV 2018 ?
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=11410963190603864729