[script][tool][windows][4.4]convert any rom to full f2fs - Nexus 4 Android Development

This is a Windows Batch Script/Tool to make any 4.4 based ROM to full F2FS compatibility !! This tool can convert any existing ROM from ext4 to Full F2FS Compatibility in a few clicks !! All tools necessary for conversion included in the batch file itself !!
Basic Info
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
DISCLAIMER
Code:
*I am Not responsible for any bricked devices,SD cards or thermonuclear attacks.
*Please do some research about what you are doing before you use the tool.
*YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Current Device Compatibility
Code:
1. Nexus 4 ( Mako )
2. Nexus 7 2012 Edition ( Grouper)
3.Nexus 5 Hammerhead
Prerequisites
Code:
1. A Mako
2. Any 4.4 based ROM with [B][U]busybox [/U][/B]installed
3. Proper F2FS Compatible Recovery and Partition Zip from
[url]http://forum.xda-developers.com/nexus-4/orig-development/recovery-rom-kernel-f2fs-05-04-14-t2706825[/url]
4. Any Windows version and my batch script
Features
Code:
1. One Click F2FS Conversion Process
2. All tools included in the Zip file itself
3. Changes only the relevant parts of your updater-script keeping the rest unmodified
4. Compatible boot.img included in the ROM itself
5. Now Scripts are Device Specific
6. Error conditions at many places so a noob cant go wrong
***Special note for Stock ROM users***
Code:
The script requires busybox and since stock roms dont have busybox the repacked ROM wont boot up.
In such a case the best option is try out any other AOSP based ROM
Instructions
Code:
[LIST=1]
[*] Unpack the Zip file you downloaded from Link Below to a folder named F2FSROMConvetor (Dont Mess with the name).
[*] Take Care that the path you extract my Zip for eg in my case "C:\Users\Nabendu\Desktop\F2FSROMConvetor"
does not contain any blank spaces in between or else the script will not work as intended.
[*] Run F2FS Convertor.bat
[*] Select your device
[*] Place the Zip in the Extract /Input directory when prompted
[*] The script will Unpack your ROM
[*] Select option 11 for AOSP,12 for CM, 13 for com.android FC 14 for Any Other
[*] Repack your ROM
[*] A black window will open showing the Repacking progress. Dont close my Blue Window anytime during it the repacking process.
After 100% repacking is done the Black Window will close automatically and you can now press any key to Continue
[*] Check NEW F2FS ROM directory for the Repacked ROM
[*] Flash and Enjoy
[*] Cleanup the working directory cleanup.bat (Cleans everything including original input ROM.Only a copy of the Output ROM is maintained)
[/LIST]
***FAQ's***
Q. I get errors compiling the ROM on my XYZ Windows Version?
A. Read through my steps once again especially point 1 & 2. Hopefully u can get it to work.
If you think you are doing everything correctly post it on the thread and Ill try to reply within 24Hrs.
Q. I want to do it on Linux !! Why you no create bash scripts ?
A. Im not good at bash scripting !! Also dont own a Linux Distro so cant help you guys !! But look here @jolinnard has a script for Linux users
https://github.com/figue/f2fs-scripts/blob/master/convert_ROM_to_f2fs.sh and make necessary changes for Hammerhead updater script if any
Q. I can do the same with the Convert to F2FS apk on the Playstore ?
A. Sure you can. Converting on mobile is easier also. But only reservation is that it is paid.Not everyone can afford it.
Also time permitting Ill create a Android Terminal Script based on jolinnards script for Linux.
Q. Do you think I can convert it myself ?
A. Yes its just clicks . Read my steps and do it you wont go wrong.
Download Links
V1.1 NEWEST !!
1) https://mega.co.nz/#!s4FkiIpA!O60y6xAFeOme13tCOn96QqV0tAqVAftVdBufEueXPrA
2) https://drive.google.com/file/d/0ByrfJAT1lgDFOTBhZFdsc3N2cjg/edit?usp=sharing
V1:
1) English
2) German (Thanks to @mikaole)
Changelog
Code:
V1.1 : Now script is device specific ( So this script is only for N4 Mako)
:Added CAF based Kernel for CM ROMs
:Added com.android.phone fc error boot.img
V1 : Initial Release
Credits
Code:
@legolas93 For bringing F2FS to Nexus and also for providing the boot.img for the script
[user=4439521]@mikaole[/user] For the German Translations and extensive testing
[user=2002216]@jolinnard[/user] For the amazing F2FS kernels he is providing
[user=4544860]@osm0sis[/user] For his amazing Android Image Kitchen.The cleanup.bat script is taken from his tool.
[user=3325155]@fishears[/user] For helping out on the kernel side.
[user=5501864]@USBhost[/user] For being the lone tester for the N7 ( 2012 )
[user=4450732]@CallMeAldy[/user] For the CM trick and his compilation thread
And all other beta testers !! Sorry if I forgot anyone from the list !!
Screenshots in the Next Post
Hit the Thanks button if you Like My Work

Screenies atlast
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

<<<<<<Reserved>>>>>>

NABENDU1 said:
<<<<<<Reserved>>>>>>
Click to expand...
Click to collapse
Boot.img supplied with the script is F2FS compatible?
Sent from my Nexus 4 using Tapatalk

snak3ater said:
Boot.img supplied with the script is F2FS compatible?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yes it is fully f2fs compatible !! Its an aosp based boot.img so if u using a cm based rom kindly flash a F2FS cm based kernel zip after the ROM!!!

NABENDU1 said:
Yes it is fully f2fs compatible !! Its an aosp based boot.img so if u using a cm based rom kindly flash a F2FS cm based kernel zip after the ROM!!!
Click to expand...
Click to collapse
Using Aosp based rom..so it shouldn't be a problem here...thanks for the tool
Sent from my Nexus 4 using Tapatalk

I make all my roms with it. Really easy to use.
Thx for the work.

Made Rastakat compatible with F2FS

What I said easy with that nice tool.

snak3ater said:
Made Rastakat compatible with F2FS
Click to expand...
Click to collapse
Would appreciate if you could upload it somewhere and post the link in the F2FS General Thread so that everybody could try it

CallMeAldy said:
Would appreciate if you could upload it somewhere and post the link in the F2FS General Thread so that everybody could try it
Click to expand...
Click to collapse
Well that's a personal build.. Not sure if it's okay to include it with other roms..anyways.. I've converted latest rastakat stockui.. Will upload it soon
Sent from my Nexus 4 using Tapatalk

Thank you for this. I just went to f2fs 2 days ago and was thinking of how to include one of my favorites kalo now and once 4.4.3 comes out. Knowing enough to wait for compatibility once 4.4.3 drops . Really thanks again.
Sent from my Nexus 4 using XDA Premium 4 mobile app

Please just want to know what im doing with the busybox how i put it in
Thx

It will be good to have a linux version of this tool.
If i have time i will try to make it next week
Sent from my Nexus 4 using Tapatalk

ohad129 said:
Please just want to know what im doing with the busybox how i put it in
Thx
Click to expand...
Click to collapse
Most of the custom Roms already come with busybox installed !! So shouldn't be a problem for anyone unless u usingn a stock ROM !!
malcho said:
It will be good to have a linux version of this tool.
If i have time i will try to make it next week
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thx a lot I'm not good at Linux so dint try bash scripting !! Anyways if we can get this it will be smooth to develop a mobile version of the script too !!
Bdw @fishears also wanted to port this to Linux !! Might be you could get in touch with him to know the progress made by him

Can someone point out the differences and advantages of all-f2fs ?
Are we currently using f2fs or ext4?
I know, noob question.

Normally every one is using ext4 for all partitions.
That's why you have to format all partitions before you can start with f2fs.
F2fs is faster than ext4. Apps are opening quocker. Reboot is a bit faster. Everything feels smoother than on ext4.

mikaole said:
Normally every one is using ext4 for all partitions.
That's why you have to format all partitions before you can start with f2fs.
F2fs is faster than ext4. Apps are opening quocker. Reboot is a bit faster. Everything feels smoother than on ext4.
Click to expand...
Click to collapse
Ql, but do I need to make a backup of /data partirion before flash? I mean backup of all user data. I assume that format to f2fs will erase all user data.

adamz667 said:
Ql, but do I need to make a backup of /data partirion before flash? I mean backup of all user data. I assume that format to f2fs will erase all user data.
Click to expand...
Click to collapse
Yes

adamz667 said:
Ql, but do I need to make a backup of /data partirion before flash? I mean backup of all user data. I assume that format to f2fs will erase all user data.
Click to expand...
Click to collapse
Take note.
Restoring a ext4 nandroid backup onto a F2FS partition is impossible (except when using something like Titanium Backup to restore apps from from data nandroid).
So I'd suggest you to backup your apps with Titanium Backup or Carbon/Helium. Send all your "SDCard" content to a PC, format and flash ROM send stuff back and restore using the backup app.

Related

[RECOVERY] Unofficial TWRP 2.2.2.1 Full Touch recovery

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
I'm not responsible of your Incorrect flashing of a recovery that can brick your device! Do not install this recovery if you don't know what you are doing with your phone.
This is latest TWRP build for LG P500 which have full touch support.
Dees_Troy said:
Team Win Recovery Project 2.2, 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.2.2.0 compared to 2.2.0.0):
Mostly bugfixes:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name
Click to expand...
Click to collapse
This Recovery for :
Who tired of scrolling through huge lists of files in ClockworkMod with the volume rocke,
want a recovery with a graphical interface that can controlled using the touchscreen
ScreenShots:(from my P500)
FEATURES:
FULL TOUCH SCREEN SUPPORT
Graphical touchscreen interface with buttons and drag-to-scroll!
Ability to save custom recovery settings
New: Integrated Terminal Emulator
Easy one-button cache & dalvik cache clearing after an installation
Default partitions to back up
Default zip folder location
Default color theme
Default Time Zone
Zip Signature Verification
Zip md5 Verification
Compressed backups that can save you up to 50% disk space
New: Custom names for backups, rename and delete backups inside recovery
Ability to flash multiple zips in one go
Ability to select which individual partitions to backup, and restore.
Ability to choose compression or no compression backups.
Ability to auto restore GAPPS on zip flash
Ability to auto reboot after successful flashes
Battery Level and Timestamp
File Manager that allows you to move, copy, delete and rename files and change their permissions
Reboot into bootloader
ADB support
Detailed logfile
Themeable
Download links
2.2.2.1
1) download zip file and place on your root of sd card
2) reboot you phone into recovery mode and flash this zip file
3) enjoy twrp recovery
Common FAQ
Can I restore my CWM/Amon ra backups on TWRP?
No you can't. but other way is: flash CWM, restore a backup, flash TWRP, create new backup, repeat.
Click to expand...
Click to collapse
BUGS:
I have tested install,wipe and backup and it's working good, If you have found a bug post here but don't post common twrp bugs.
Credits:
- Dees_Troy and other all Twrp team - for making this recovery
- Cyanogenmod team - used cm7 device folder to compile this recovery
Just flashed it. Nice job!
No bugs so far, but don't take my word for it since I only played around with it for five minutes.
Noticed so far:
1. Very quick to exit recovery and reboot into the system (less than a second)
2. A lot of customizations and nice interface
I love it! Finally someone did.
The other day, I was thinking of compiling CWM 6 Touch from source but I guess I don't need it now
Real nice, just installed and take a fast look on it. Will test more later. Thanks:good:
been waiting for this. I had this on my a100 but i couldn't find it on my p500
finally this day has come
this should be in original development
hey it rebooted in the middle of a backup(that backup was like 200 mb). now it can't backup anymore. it can't create folder sdcard/ (text cuts off)
edit: reflashing recovery. rebacking up. seeing what happens
wierd... its says my sd-ext is 0 mb. i use link2sd and i definitly have stuff on my sd-ext
Edit: Now everything works. thanks...
It say's on recovery that it's 2.2.2.1.. And thank's a lot to this wonderful recovery..
Sent from my LG-P500 using Tapatalk 2
But how to wipe battery stats from recovery??
carrthee89 said:
But how to wipe battery stats from recovery??
Click to expand...
Click to collapse
it don't have that option
Thanks dude i am big fan of TWRP and only use twrp recovery.now time to update.
[Q] possible theme blue??? thanks by Notonlyeyes
Just a little bug here, there are some overlapping text specially when backing up..
Sent from my LG-P500 using Tapatalk 2
plzz....support multirom
thanks
dnle71 said:
Just a little bug here, there are some overlapping text specially when backing up..
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
This is due to our phone's screen size. I guess Ron can fix it while building, it needs some xml edits
Is it as stable as CWM 5.0.2.0? What are the added features? Need your suggestions as I never used any other recovery other than CWM.
Sent from my LG-P500
myawan said:
Is it as stable as CWM 5.0.2.0? What are the added features? Need your suggestions as I never used any other recovery other than CWM.
Sent from my LG-P500
Click to expand...
Click to collapse
The only added feature there is really a file manager everything else the same
Twip just has a really cool touch interface
Sent from the My Little Pony Official App
x-dira said:
plzz....support multirom
thanks
Click to expand...
Click to collapse
ask to Tasssadar for that
dnle71 said:
Just a little bug here, there are some overlapping text specially when backing up..
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
i will try to fix on next version.
@Ron G: I posted about your work on DroidViews.com: Here
After long time twrp is back..just want to know is this fully suitable or compatible for ics or miuiv4 roms flashing like amonra???
Jaani said:
After long time twrp is back..just want to know is this fully suitable or compatible for ics or miuiv4 roms flashing like amonra???
Click to expand...
Click to collapse
Yes it is, successfully flashed AOKP, Oxygen, Hep's ics, CM7, MIUI GB/ICS
Sent from my LG-P500 using Tapatalk 2

[RECOVERY]TWRP 2.4 - TeamTX

Hello fellow old friends! I've brought something new and cool to this old forum(slow to keep up with the latest stuff).. And exremely cool for guys with non-working sd slots; You can now easily flash roms using "ADB Sideload" feature of TWRP.. bla bla...
UPDATE - 12MAR2013 - TWRP 2.4 Build taken down due to huge size which can't fit in our recovery partition.. Currently trying to slim it down..
Today, I felt like getting my ubuntu up and doing some fun stuff like old day. There! I decided to get another build of TWRP. I couldn't really test is as my bros phone is nowhere to be found . However, since I used the exact same source as the first build it should work just fine. Anyone willing to try their luck is welcome and appreciated..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction:
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for 2.3 features
What's new in 2.3:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
What's new in 2.2 & 2.1:
On-screen keyboard! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups before creation and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
Numerous small bug fixes and improvements
Zip queuing as seen in TWRP 1.1.x is back
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.2 features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues: (General TWRP issues)
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Issues I found:
-UMS doesn't work
i installed but couldnt install any zip's or back ups looks really good tho...nice 2 see summit different :victory:
Congrats bro on your first source build!!! :thumbup:
shmokeyuk said:
i installed but couldnt install any zip's or back ups looks really good tho...nice 2 see summit different :victory:
Click to expand...
Click to collapse
Ill check install from zip. But backup was working good..
rishabh.raj37 said:
Congrats bro on your first source build!!! :thumbup:
Click to expand...
Click to collapse
actually not my first.. I'm building aosp for my nexus
Sent from my Galaxy Nexus using xda app-developers app
Haha grats i would count this as your first source build AOSP for maguro is officially supported and not much needs to build it just select the option
-Grift- said:
Haha grats i would count this as your first source build AOSP for maguro is officially supported and not much needs to build it just select the option
Click to expand...
Click to collapse
Well, yeah you have a point.
Sent from my Galaxy Nexus using xda app-developers app
Great, thank you! but where can I find "erase battery stats"? It's gone from the wipe menu!
Punkiderma said:
Great, thank you! but where can I find "erase battery stats"? It's gone from the wipe menu!
Click to expand...
Click to collapse
Ill see that when my bro comes back home...
XiproX said:
Ill see that when my bro comes back home...
Click to expand...
Click to collapse
Confirmed: can't install zips
Thanks anyway! I'll be waiting for further verions =D
Well thats weird I just checked now and it looked like it flashed AOSP 1.4 successfully.. Ill check again after a full wipe..
And yes battery stats button is gone. Have no idea why.. I had just disable sd_partitioning to lower recovery image size to fit our phone. I dont remember disabling anything else.. Why do you even need wiping battery stats?
did a full wipe including system and flashed:
1.AOSP GB 1.4 -- FLASHED
2.TX-MIUI-SDSL -- FLASHED
3.Grifts CM10 build -- Took longer than the previous 2 roms but FLASHED (I was even gonna make a battery pull cause I thought it was doing nothing, then just saw the final show_progress)
4.IceCreamSwift RC2 -- FLASHED
As you can easily see, it has no problem flashing android 2.3.7, 4.0.4, 4.1.2...
if you still cant flash, please try some other rom and report.. Thanks1
XiproX said:
did a full wipe including system and flashed AOSP 1.4 and successfully booted..
Ill be testing these roms and report..
1.AOSP GB 1.4 -- FLASHED
2.TX-MIUI-SDSL -- FLASHED
3.Grifts CM10 build -- Took longer than the previous 2 roms but FLASHED (I was even gonna make a battery pull cause I thought it was doing nothing, then just saw the final show_progress)
4.Miro's Oxygen
Click to expand...
Click to collapse
miro has oxygen ? you mean 4.0 that is based on ice cream swift ?
smileydr0id said:
miro has oxygen ? you mean 4.0 that is based on ice cream swift ?
Click to expand...
Click to collapse
yeah, but I think my bro deleted that rom from sd. so Im gonna try flashing IceCreamSwift RC2
btw, I think it was based on AOSP not CM
XiproX said:
yeah, but I think my bro deleted that rom from sd. so Im gonna try flashing IceCreamSwift RC2
btw, I think it was based on AOSP not CM
Click to expand...
Click to collapse
Can you explain me how did you ported it ? i wanna try to port it on my xperia U
smileydr0id said:
Can you explain me how did you ported it ? i wanna try to port it on my xperia U
Click to expand...
Click to collapse
if its TWPR you are asking, I had already got my build environment set up following this, then it was really easy to build TWRP;
you can simply follow those instructions there for ubuntu, udev rules, and other tools like java, then skip Gnex stuff, use the same process for getting repo commands and instead of initializing AOSP source initialize CM source(https://github.com/Cyanogenmod -----...). After getting the cm repo follow The official TWRP guide. NOTE: Youll need device files for your phone. I hope someone has an open-source project
Good Luck! feel free to pm if you need something. And in case of any problem with building twrp or other twr related make sure you check their freenode you'll get your answer faster than you would on the guide thread..
Again, if you still cant flash roms, please briefly explain what happens and provide a log (Advanced>Copy Log to SD) Thanks!
XiproX said:
Again, if you still cant flash roms, please briefly explain what happens and provide a log (Advanced>Copy Log to SD) Thanks!
Click to expand...
Click to collapse
My problem is not flashing roms (didn't tried either), is flashing mods (apks, fixes, and so on). With those installation fails always and with the previous version of TWRP they install correctly
coto39 said:
My problem is not flashing roms (didn't tried either), is flashing mods (apks, fixes, and so on). With those installation fails always and with the previous version of TWRP they install correctly
Click to expand...
Click to collapse
it could be because of TWRP 2.3 being based on AOSP jelly bean sources, "TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder."
if there was a particular reason then it would affect ROM flashing too. (I guess).. I think you should try to flash a not working patch with the above provided update-binary..
XiproX said:
it could be because of TWRP 2.3 being based on AOSP jelly bean sources, "TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder."
if there was a particular reason then it would affect ROM flashing too. (I guess).. I think you should try to flash a not working patch with the above provided update-binary..
Click to expand...
Click to collapse
That's right I also had that issue but it was because of older binaries.
But I do have another issue, this version backs up my rom without problem but when it comes to restore, i just get bootloops. The thing is that apparently there are no errors restoring the backup. I have TWRP 2.1.4 and 2.3.1.1 flashable zips for when I need to restore
Are you aware of this XiproX?

[INDEX][REPO] F2FS Roms and Kernels 14/6/2014

What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
Instructions:
(All credits to authors. legolas93 only made them compatible with F2FS)
Download compatible ROM
Download FormatPartitions.zip
Download "special" TWRP for All-F2FS: openrecovery-twrp-2.7.0.0-mako-All-F2FS.img
(This is different for that of simply F2FS)
Copy FormatPartitions.zip and ROM on Phone
Flash "special" TWRP with Fastboot
Flash FormatPartitions.zip with new Recovery
Reboot Recovery
Flash ROM with new Recovery
(Flash GApps with new Recovery)
Go to Wipe Menu and press Format Data (The Big BUTTON!) (You will LOSE all your Data! Music, Movies etc!!)
Reboot
(Recovery has a RED back button to remember you that you are using the F2FS recovery!)
Phone is snappy and smooth with All-F2FS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Revert to EXT4
- Flash a "normal" recovery
- Format Data
- Reboot Recovery
- Flash RestorePartitions.zip (Untested)
- Reboot Recovery
- Flash your previous ROM
(Required commit)
Compatible ROM's
UPDATE :- C-RoM Uploaded to AFH. ​
Compatible ROM's
Slim-mako-4.4.2.build.4-All-F2FS-2.zip (Credits :- legolas93)
For Various F2FS Roms (AOSP and CM) Go Here. (Credits :- CallMeAldy)
For All F2FS PSX Builds Go Here. (Credits :- mikaole)
SlimKaterator Rom (Credits :- Godzillandroid)
DarkSideTeam ROM (AOSP) THREAD (Credits :- DarkSideTeam)
Please Note :- Flash the CM rom and then HellsGod CM kernel linked in the kernels post and then boot
Compatible Kernels
Kernels
HellsDoctor (AOSP and CM) (Credits :- barome)
Jolie Kernel (AOSP) (Credits :- jolinnard)
HellsCore (CM) (Credits :- hellsgod and jolinnard)
HellsCore (AOSP) (Credits :- hellsgod and callmealdy)
Matrix (AOSP) (Credits :- mathkid and jolinnard)
franco.Kernel(AOSP and CM) (Credits :- franco and jolinnard)
Aufa's Kernel V26 (CM) (Credits :- mnajem)
UPDATE-adreno-drivers-n4&n7-may-30.zip
HTC M8 Binaries
CM11 Moto X Dalvik Patches
Stock Moto X Dalvik Patches
CallMeAldy said:
Reserved. Just in case
Click to expand...
Click to collapse
Thanks for this detailed thread. It will help lot of the users to actually know which ROM,Kernels are F2FS compatible.
Thanks for this thread a lot more of compatible F2FS ROMs to come in the coming days !! Also can you link some compatible boot.imgs to this list
I know 2 compatible boot.imgs atm
1) SlimF2FS boot.img
2) Firebird F2FS boot.img
If anyone wants to make an F2FS ROM, here's a HOW-TO
Also upload it somewhere, so the OP will update the first post.
@OP, ak xGenesis works on F2FS. It should be in OP.
Updated Adreno Binaries 17/04/2014 F2FS can be downloaded here: http://www.sendspace.com/file/shm6bl
Rohit02 said:
Thanks for this detailed thread. It will help lot of the users to actually know which ROM,Kernels are F2FS compatible.
Click to expand...
Click to collapse
It's just easy as cake to make every rom out there f2fs compatible. I just make the roms from the psx dev, because in my opinion these are the absolute fastest roms out there. I can just recommend to all to just try psx402 with ak kernel on art. Unbelievable
mikaole said:
It's just easy as cake to make every rom out there f2fs compatible. I just make the roms from the psx dev, because in my opinion these are the absolute fastest roms out there. I can just recommend to all to just try psx402 with ak kernel on art. Unbelievable
Click to expand...
Click to collapse
What's the actual advantage of F2FS, compared to EXT4 for example?
Faster
What app do you use to check mount point, file system, access time, block size etc..?
nmogas said:
What app do you use to check mount point, file system, access time, block size etc..?
Click to expand...
Click to collapse
DiskInfo it's available on playstore
Sent from my Nexus 4 using Tapatalk
CallMeAldy said:
Kernels
HellsDoctor (AOSP) (Credits :- jolinnard)
HellsGod (AOSP and CM) (Credits :- jolinnard)
Matrix (AOSP) (Credits :- jolinnard)
franco.Kernel-nightly-r204-SaberMod-4.9Test-selectable (AOSP) (Credits :- jolinnard)
Aufa's Kernel V26 (CM) (Credits :- mnajem)
Click to expand...
Click to collapse
Maybe you can add credits to devs too. And my kernel work very well on F2FS without jolinnard modifications.
you should just link my folder and not the roms itself, cause I always update the daily builds for the roms. Noone will find the roms you linked, cause they are not there anymore.
And I deletet plsx, cause there is no use for it since psx is out. Same rom, same speed, just more features in PSX.
https://drive.google.com/folderview?id=0B__yyNLq1EIRR2lVbmNIT3RBeU0&usp=sharing#list
mikaole said:
you should just link my folder and not the roms itself, cause I always update the daily builds for the roms. Noone will find the roms you linked, cause they are not there anymore.
And I deletet plsx, cause there is no use for it since psx is out. Same rom, same speed, just more features in PSX.
https://drive.google.com/folderview?id=0B__yyNLq1EIRR2lVbmNIT3RBeU0&usp=sharing#list
Click to expand...
Click to collapse
I see psx 4.0.3on your Google drive, but on the psx forums I can only download 4.0.2. What sorcery is this? Can we get changelog? Thanks
Edit: I spotted OmniSwitch in 4.0.3 version.
i just spent the last hour mocking around on the phone
these are my findings:
from mikaole's drive, i managed to get rusty's build working after i manually formatted the cache directory
i didn't follow the instructions from OP since i'm on f2fs for data already
anyway after i got it working with slim's kernel, i found that it is not possible for me to use jolinard's selectetable kernel....
i'm back on purity now with only data as f2fs
thanks for everyone's good work in putting this together, i'm not critising, just reporting back what happened
hopefully the kinks in the system will be ironed out next time i try going all f2fs
Hi, which kernel work better with omni ART+F2FS
Thanks
nat510 said:
Hi, which kernel work better with omni ART+F2FS
Thanks
Click to expand...
Click to collapse
I used hellsdoctor
shubu000 said:
i just spent the last hour mocking around on the phone
these are my findings:
from mikaole's drive, i managed to get rusty's build working after i manually formatted the cache directory
i didn't follow the instructions from OP since i'm on f2fs for data already
anyway after i got it working with slim's kernel, i found that it is not possible for me to use jolinard's selectetable kernel....
i'm back on purity now with only data as f2fs
thanks for everyone's good work in putting this together, i'm not critising, just reporting back what happened
hopefully the kinks in the system will be ironed out next time i try going all f2fs
Click to expand...
Click to collapse
I did use rusty's build on full f2fs with jolinard's hellsdoctor selectable kernel.
I hope you renamed the kernel before flashing it
I just can not believe how fast PSLX + Matrix + F2FS is!
It totally worth migrate from EXT4, i think i've never felt a so smooth, fast and stable experience!
Thanks!

{All 2011}[DEV][Lollipop 5.1.1][LegacyXperia] unofficial CyanogenMod 12.1 builds

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]
Not developed actively anymore. You can update to cm-13.0.
This is an unofficial build of CM12.1.
This is an attempt to stay close to official cm12.1 and not make crazy hacks to make things working.
This is a pure CM build, only contains official CM features. I will not add any other external feature/app/etc.
For an up-to date working/not working list, bug tracker, useful guides & FAQ, visit our website:
http://legacyxperia.github.io
Want to contribute? Visit the brand new msm7x30 gerrit:
http://review.msm7x30.org
WARNING: This ROM uses a modified internal memory layout.
Our /system partition is originally 400MB but this space is not enough for a fluid experience and a full installation with proper google apps.
The internal storage has been repartitioned to give the whole space to /system & /cache. You will need a secondary partition on your SD card to be used as the /data partition.
If you want to use this ROM you will always have to use the included kernel or use a kernel that includes the layour changes. Bug reports with non-standard kernels will be ignored.
You will have to wipe the device and make a clean install.
You cannot restore nandroid backups from previous android versions or restore backups from this ROM to other ROMs that don't use the new partition layout since you risk corrupting the data.
I suggest to use Titanium Backup, Helium or any other similar app to backup your data if you really need to.
Requirements:
* Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm12.1, it will work both ways)
* LT15i (Arc) users need to flash LT18i (Arc S) ftf
* MT15i (Neo) users need to flash MT11i (Neo V) ftf
* Minimum 2GB secondary ext4 partition for /data on class 10 SD card.
Steps required for correct installation (order is important):
1: Flash boot.img in fastboot & reboot into recovery
2 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
3: Enter recovery
4: Format /system using System-Formating-Tool_signed.zip (can be found here) , then /data and then /cache (Important step!)
5: Flash update zip
6: Flash gapps
Steps 2, 4, 6 are not needed when you install new LX build on top of an older one in the future
If you want to return to a ROM that doesn't use the new partition layout, you need to follow the above steps again (only replace boot.img & update zip with the ones you want to use).
FAQ/Q&A/Discussion thread:
{All 2011}[FAQ][Q&A][CM12.1] LegacyXperia discussion
How to make your own test builds:
{All 2011}[GUIDE][DEV] How to build CyanogenMod 12.1
Changelog:
Release changes
Working/Non-working list
Lollipop status
Downloads:
https://s.basketbuild.com/devs/LegacyXperia
PLEASE DON'T MIRROR OUR UPLOADS
Recommended Google Apps:
Google Apps packaged by Mardon
NOTE:
Following xda's rule #12 spirit: If you are developing something that is based on my work, you MUST first seek my permission, you must add my name in the credits and you must add links pointing to my original thread and to my github sources.
Breaking this rule will lead me to report the thread to the moderators.
BUG Tracker
If you want to help fixing those bugs, please report the bugs in the bug tracker. Thanks!
Logs are needed (logcat/dmesg/last_kmsg), not just "got FC" or "+1" useless replies.
For more detailed instructions check the bug reporting guide in the FAQ.
XDA:DevDB Information
LegacyXperia, ROM for the Sony Ericsson Xperia Arc
Contributors
mikeioannina, Blefish, Mardon, pcfighter, mikegapinski, Men_in_black007, Rrreutel, nobodyAtall
Source Code: http://github.com/LegacyXperia
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest version of official ICS firmware: 4.1.B.0.587 or the latest supported baseband: 8x55A-AAABQOAZM-203028G-77
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Current Beta Version: 20150513
Beta Release Date: 2015-05-13
Created 2015-03-13
Last Updated 2016-02-26
Got an issue?
first test on urushi... :good: :good: :good:
5.1 on its way i think..
*] front LED holographic keyboard >> another dream in android
There´s no cm12 for Mango?
Fjss said:
There´s no cm12 for Mango?
Click to expand...
Click to collapse
It Will Be Available In Few Hours.
Also Important Note : Please Don't Spam Here (Like Thnx Mike , First One To Try, Blah Blah)
We Have Ques/Answer Thread For That .
Men_in_black007 said:
It Will Be Available In Few Hours.
Also Important Note : Please Don't Spam Here (Like Thnx Mike , First One To Try, Blah Blah)
We Have Ques/Answer Thread For That .
Click to expand...
Click to collapse
Ok. Great work Dev´s. Keep up.:highfive:
am unable to flash the ine2ext file...it fails as the package cannot be loaded. i have use the same file many times before..and when the phone reboots :android is upgrading" takes a long time to complete.....there is lot of over heating too.
am sorry but is this ROM not prerooted? i cannot find superuser app and titanium backup won't work if ROM is not rooted
vipinrahul said:
am unable to flash the ine2ext file...it fails as the package cannot be loaded. i have use the same file many times before..and when the phone reboots :android is upgrading" takes a long time to complete.....there is lot of over heating too.
am sorry but is this ROM not prerooted? i cannot find superuser app and titanium backup won't work if ROM is not rooted
Click to expand...
Click to collapse
Guys, please read new instructions... There is no need to use int2ext or link2sd, while 2nd partition is automatically mounted as /data and any app you install and all their files, go directly to SD
To use root you have to enable Developer options and set root access for "apps and ADB"
my phone is very lag after flash google apps. It is smooth without google apps...
restart when camera is trigger...
my phone is phoenix.
Guys plz head over here with all your queries,doubts,problems.
this thread is in development section so over here there should be posts related to development of the rom and not your grievances
plz don't post your doubts here and respect the devs
Thread for your Doubts :
http://forum.xda-developers.com/xperia-mini/help/faq-2011-legacyxperia-discussion-t3053947
Can anyone here perhaps help me with installing the usb drivers for my Xperia Arc please?.. The flashtool drivers aren't installing right, they keep giving back failed responses!.. Plus, I don't wanna go through that signature malarky crap!.. Is there any other way I can get the drivers installed on Windows 8.1 so that I can flash this ROM, PLEASE!!!
Thanks...
Will the Cm12 Rom work without ext4 partition in future?
Hi everyone, I have a trouble, my mini pro seems not run, is slow, what can I do?
yuber26 said:
Will the Cm12 Rom work without ext4 partition in future?
Click to expand...
Click to collapse
no. because our phone has to less space for lollipop
FranckJZA said:
Hi everyone, I have a trouble, my mini pro seems not run, is slow, what can I do?
Click to expand...
Click to collapse
buy a fast sd card!
To set a real dev discussion:
I was supposed to so something else, so I started reading through my kmsg.log and of course I found "ti_st_open: st_register failed -22" which is followed by 2 min of suspend (being stuck at boot logo). I googled it and found out it is related to bluetooth driver. Those codes from our kernel sends that error:
https://github.com/LegacyXperia/and...c2dac8e3446a7695/drivers/misc/ti-st/tty_hci.c
https://github.com/LegacyXperia/and...c2dac8e3446a7695/drivers/bluetooth/btwilink.c
But why I'm mentioning it after all. After some research, I have found on TI Support page some thread related to wl1271 with the same issue in log:
http://e2e.ti.com/support/wireless_connectivity/f/307/t/237355
According to it, problem is related to GPIO BT_EN suspend/power down sequence, which have bad effect on next power up.
GPIO is handled by:
https://github.com/LegacyXperia/and...2c2dac8e3446a7695/drivers/misc/ti-st/st_kim.c
@mikeioannina is it helpful?
More links:
http://e2e.ti.com/support/wireless_connectivity/f/307/t/340453#pi239031348=1
+ commands for terminal:
http://processors.wiki.ti.com/index.php/NLCP_Bluetooth_Command_Lines
Hi,
how does the partiontable of the sd card need to look?
I mean is it enough if there's any ext4 partition or can the whole card be formatted as ext4?
Which filesystem should the default? part be?
Awesome CM12
Successfully Booted up CM12 on coconut
Thanks Dev:good::good::good::good::good:
keibak said:
Hi,
how does the partiontable of the sd card need to look?
I mean is it enough if there's any ext4 partition or can the whole card be formatted as ext4?
Which filesystem should the default? part be?
Click to expand...
Click to collapse
The install script will mount your second partition as ext4, my suggestion:
first partition fat/fat32 for "external SD" in the ROM
second partition ext4 for the /data partition
Both partitions should be primary partitions
Screenshots pls?
Sent from my Micromax AQ4501 using XDA Free mobile app

[TWRP][sprout] Team Win Recovery Project [2.8.7.x]

Team Win Recovery Project for Android One 1st Generation​​
[ UNOFFICIAL ]
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOAD
[ AFH | DRIVE ]
CHANGELOG
Code:
[B]TWRP 2.8.7.x[/B]
[LIST]
[*]Updated sources
[*]Fixed issues with Android M custom roms
[*]Fixed "Mount system read-only" disabled after reboot
[*]F2FS support. Huge thanks to Swapnil Solanki for the ZEUS kernel commits
[*]Faster Partition Formating for EXT4 filesystem. F2FS may take 3-5 minutes or more.
[/LIST]
[B]TWRP 2.8.7.0[/B]
[LIST]
[*]Initial ground work for software drawn keyboard (_that)
[*] Fix handling of wiping internal storage on datamedia devices (xuefer)
[*] Allow DataManager to set and read values from the system properties (xuefer)
[*] Fix crash when taking screenshots on arm64 devices (xuefer)
[*] Fix error message after an ORS script completes (Dees_Troy)
[*] Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
[*] Add system read only option – more details below (Dees_Troy)
[*] Add resize2fs and GUI option to run resize2fs (Dees_Troy)
[*] Fix crash loop caused by empty lines in AOSP recovery command file (_that)
[*] Prevent duplicate page overlays such as multiple lock screens (mdmower)
[/LIST]
[B]Enabled few options which were not included with the official TWRP for Sprout[/B]
[LIST]
[*][URL="https://gerrit.omnirom.org/12728"][WIP] gui: stock theme rework[/URL] by z31s1g (9-27-2015)
[*]OEM, LOGO and IMEI support
[*]USB Mass Storage
[*]CPU Temperature
[/LIST]
Full Changelog
PROCEDURE
- Flash the zip with your current custom recovery
- Or extract the .img file and flash it with Flashify
FASTBOOT METHOD
Code:
[B][CENTER]$ fastboot flash recovery twrp-2.8.7.x-sprout.img[/CENTER][/B]
MATERIALIZE THEMES
I personally like the default ui, but decided to add more themes for you to choose from. But in case you want more themes there are alternatives, you can grab em here Ave_Hornet, SethPDA and annson08 And make sure that the theme is compatible with your current twrp version.
Manual Installation:
Download the theme of your choice and rename it to " ui.zip "
Navigate to Internal storage "/data/media/0/TWRP" and create a new folder name "theme"
Place the "ui.zip" inside the theme folder similar to this "/data/media/0/TWRP/theme/ui.zip".
Reboot to recovery and enjoy
Don't forget to hit the thanks button for z31s1g, Ave_Hornet, SethPDA and annson08
BUGS
-Aroma filemanager....
-If you found an insect you tell me
MD5 HASH
Check out the AFH mirror, it contains all the md5 signature
Flash at your own risk :good:
Huge Thanks to Linus Torvalds for the Linux Kernel, TeamWin for the source, Varun.Chitre15 Sprout Device Tree, Swapnil Solanki for the Zeus kernel F2FS commits, z31s1g and Behold_this for the rest of the themes​
Screenshots​
Tested and working for Sprout4 variants...
Verified working for Sprout8 by @joeyhuab. Big thanks
Thanks! I hope an official build will be released, maybe make this one official if there's no problems!
awesome work sir
Thanks for this @1cefire!!
Thank you very much it works flawlessly one question though it has option of backing up imei does it work?Lot of devices lost imei on flashing stock it would be very helpful if it worked.
Cann aroma file manager be fixed.
vjtigas said:
Thanks! I hope an official build will be released, maybe make this one official if there's no problems!
Click to expand...
Click to collapse
Not possible dude, TWRP official is already available for sprout
ARAVIND_PAVAN said:
awesome work sir
Click to expand...
Click to collapse
joeyhuab said:
Thanks for this @1cefire!!
Click to expand...
Click to collapse
rohitsonone said:
Thank you very much it works flawlessly one question though it has option of backing up imei does it work?Lot of devices lost imei on flashing stock it would be very helpful if it worked.
Cann aroma file manager be fixed.
Click to expand...
Click to collapse
Regarding IMEI, I think it might work since TWRP will backup the partitions responsible for our device equipment identity. I haven't tried it though, since I haven't lost my IMEI on this device. I was able to try with my previous mtk6582 device thanks to this thread. And regarding Aroma FM, I guess it doesn't work with the latest twrp, use the built-in filemanager for now
1cefire said:
Not possible dude, TWRP official is already available for sprout
Regarding IMEI, I think it might work since TWRP will backup the partitions responsible for our device equipment identity. I haven't tried it though, since I haven't lost my IMEI on this device. I was able to try with my previous mtk6582 device thanks to this thread. And regarding Aroma FM, I guess it doesn't work with the latest twrp, use the built-in filemanager for now
Click to expand...
Click to collapse
I mean, they should label this recovery you made as official! I think there are no bugs in this recovery that you made, it should be called official and be uploaded to the official TWRP site...
vjtigas said:
I mean, they should label this recovery you made as official! I think there are no bugs in this recovery that you made, it should be called official and be uploaded to the official TWRP site...
Click to expand...
Click to collapse
I guess so, but no worries dude.....
doesn't matter, as long as its stable
How to flash using flashify,!?
Sent from my MyPhone UNO using XDA Forums
shirozxc said:
How to flash using flashify,!?
Sent from my MyPhone UNO using XDA Forums
Click to expand...
Click to collapse
Extract the zip using es filemanager/root explorer and flash twrp-2.8.7.0-sprout.img
Built TWRP with the new stock GUI by z31s1g
DOWNLOAD : TWRP New GUI
Changelog
[WIP] gui: stock theme rework: Combine the current theme with a touch of material.
Big thanks to z31s1g
1cefire said:
DOWNLOAD : TWRP New GUI
Changelog
[WIP] gui: stock theme rework: Combine the current theme with a touch of material.
Big thanks to z31s1g
Click to expand...
Click to collapse
Cool! Where's that UI from?
---------- Post added at 06:58 AM ---------- Previous post was at 06:52 AM ----------
Never mind, I just understood.
By the way, when I change the filesystem of any partition to f2fs, TWRP cannot mount it.
vjtigas said:
Cool! Where's that UI from?
---------- Post added at 06:58 AM ---------- Previous post was at 06:52 AM ----------
Never mind, I just understood.
By the way, when I change the filesystem of any partition to f2fs, TWRP cannot mount it.
Click to expand...
Click to collapse
It will be the default twrp UI, soon
This build was not built with f2fs enabled, a separate build is recommended since a kernel with f2fs enabled is also needed. i will look into it when i get the chance.
1cefire said:
It will be the default twrp UI, soon
This build was not built with f2fs enabled, a separate build is recommended since a kernel with f2fs enabled is also needed. i will look into it when i get the chance.
Click to expand...
Click to collapse
The Material TWRP 2.8.7.0 for sprout has the chmod 644 button. It makes pushing system apps easier. In this build, there's no such button. I have to type it manually. I hope that button can be added. Thanks
vjtigas said:
The Material TWRP 2.8.7.0 for sprout has the chmod 644 button. It makes pushing system apps easier. In this build, there's no such button. I have to type it manually. I hope that button can be added. Thanks
Click to expand...
Click to collapse
Dude, you should send a request to z31s1g regarding the issue, besides I use 755 more often You could do it yourself by unpacking the img file using AIK, then look for /twres/ui.xml or portrait.xml and search for the line containing chmod "755" and replace it with "644". Another option is to use a 3rd party theme such as material, or use the repacked version :good:
Anyhow, I have successfully compiled a working TWRP w/ f2fs support. Unfortunately, it seems like our kernel implementation of f2fs is messed up at the moment since none of my compiled f2fs enabled kernel works with a patched fstab, even f2fs enabled custom kernels such as monarch and zigzag were not able to get past the boot animation. i will look into it once again when M sources arrives.
Please add mounting of SD card after making it internal memory in Marshmallow. Really hard to flash zips via sideload
Thanks
Does this work for the android one varient (infinix hot 2 X510)
vjtigas said:
Can you make a blue themed (original) one? It looks so much better for me, thanks!
Click to expand...
Click to collapse
done :good:
hp5942 said:
Please add mounting of SD card after making it internal memory in Marshmallow. Really hard to flash zips via sideload
Thanks
Click to expand...
Click to collapse
I tried, but it looks like the internal storage feature of Android M is encrypted. As soon as teamwin found a way to support this feature I will update this recovery.
anarchtic said:
Does this work for the android one varient (infinix hot 2 X510)
Click to expand...
Click to collapse
No, It might work by porting, upload your device boot.img and I will try.

Categories

Resources