Database Info

[recovery] CWM for Betelgeuse v0.3 - Now with USB support

I have made some modifications to the famous ClockworkMod recovery that enable to chose internal storage or sd-card for backup and flashing. I think this is quite useful. I also want to try to add usb-drives to this list, but that will take some more coding.
The source code is availlable in my gihub.
WARNING: USB does not seem to be hotplugable. Plug before boot and don't remove till reboot. I managed to get a complete lockup (had to remove battery to get out) by not obeying this.
USB Disk must have exactly one vfat partition.
Download v0.3:
Image file
update.zip (flash with ClockworkMod as included in CM7)

Changelog
v0.3
- Add USB support
v0.2
- Based on ClockworkMod Recovery v3.0.2.8
- Add menu items to chose sd or internal drive

Your idea is great and keep up!!! I'll flash your recovery when its become more stable. I just make it usable after lots of problems and I want to brick it again. I think you understood me.
Sent from my Folio 100 using Tapatalk

Dual boot command in CWM possible ?
MBlaster
First of all, thank you for your work and efforts.
Since you seem to be familiar with adding features to CWM, I have one question : would it be possible to add a menu-entry for choosing an alternative boot (like for example ubuntu installed on a SD-Card ...) ?
Regards,
eRaph

v0.3
- Add USB support
Have Fun!

mblaster said:
I have made some modifications to the famous ClockworkMod recovery that enable to chose internal storage or sd-card for backup and flashing. I think this is quite useful. I also want to try to add usb-drives to this list, but that will take some more coding.
The source code is availlable in my gihub.
WARNING: USB does not seem to be hotplugable. Plug before boot and don't remove till reboot. I managed to get a complete lockup (had to remove battery to get out) by not obeying this.
USB Disk must have exactly one vfat partition.
Download v0.3:
Image file
update.zip (flash with ClockworkMod as included in CM7)
Click to expand...
Click to collapse
Thanks for this job. Just a question: what is the procedure for recovery update ? I start with a stock rom rooted and with recovery from foliomod1.4 installed via ADB.
Thanks
miazza

Hello to everybody. I need this recovery but the links are boken. can someone help by reaupload or send as PM.
Thanks

[ROM] CyanogenMod 9 for LG Optimus Net (P690)

This is CyanogenMod 9 created by me
What works:
- everything
What doesn’t work:
- Offline charging (can't work good)
- Camera
- Youtube HQ
- Funny sim (can't be fixed)
Gapps:
http://goo.im/gapps/gapps-ics-20120429-signed.zip
Rom:
http://lgics.altervista.org/
Source device folder: https://github.com/lgics/cm_device_lge_p690
Screenshoots:
Thanks:
diogobuique for donate me money for buy the phone
lupohirp for source of cm9 for optimus one
adfad666 for help with cm9
Code Aurora Forum for kernel
Cyanogenmod team
Prerequisites:
Back up your contents of the sd card to PC
Root your phone
Install a recovery Clockworkmod
enter in recovery
Enable USB-MS toggle: Copy ROM.zip and GAPPS.zip
Disable USB-MS
Skip to the Installation section
Installation:
Enter recovery
Make a nandroid back up
Make full wipe (except wipe sd) for the first time installation
Flash from ZIP: Select ROM and reboot
Flash GAPPS and reboot
Have fun!

I heard that you could fix bt and cam by adding files to \system?

need other thing to do that add file on /system

markolino631 said:
need other thing to do that add file on /system
Click to expand...
Click to collapse
How? could you be a bit more specific??

We really need the camera especially for us IG users. My phone is useless without a cam.
Sent from my LG-P690 using xda premium

And how do i know if my sim is a funny sim?

Thanks

need the right libcamera for the camera! is funny sim if the telephone doesn't read you sim

markolino631 said:
need the right libcamera for the camera! is funny sim if the telephone doesn't read you sim
Click to expand...
Click to collapse
how will it be done???

vicfirth_23 said:
how will it be done???
Click to expand...
Click to collapse
If we will not have a developer that will work on this phone this phone will be only a good phone with stock rom guys

if i have this phone i should be fix the errors first but i don't have this phone...

Ready to help.
@Marko If you can fix this rom we can check out the bugs.......

markolino631 said:
Cyanogenmod 9, Android ICS 4.0.4, My kernel modified! All for the LG Optimus Net (P690)
What works:
- Full H/W acceleration with new adreno drivers, 3D (yamato)
- Calls, SMS, MMS, 3G/2G, Mobile data
- Wireless, Bluetooth tethering
- Data limit, IPv4, IPv6
- Stereo audio, headset
- GPS, Sensors, Lights, Touch screen
- Usb Mass storage, Usb debugging
- Browser, GMail, GPlay
What doesn't work:
- Wifi tethering & USB tethering, Offline charging: needs usb driver update from 3.0 kernel
- FM Radio: not implemented in CM yet
- Youtube HQ: needs OpenMaX(omx) libraries for armv6
- Camera
- Funny SIM (128k USIMs)
- Bluetooth
Releases aren't usefull for daily usage if you want to use camera and bluetooth.
It is almost fast!
Download rom: http://www.mediafire.com/?2vp9425z39hto4b
Screenshoots:
Thanks:
lupohirp for source of cm9 for optimus one
adfad666 for help with cm9
Code Aurora Forum for kernel
Cyanogenmod team and Android for ICS and for kernel .35 for chic
Prerequisites
Back up your contents of the sd card to PC
Root your phone
Install a recovery Clockworkmod
enter in recovery
Enable USB-MS toggle: Copy ROM.zip and GAPPS.zip
Disable USB-MS
Skip to the Installation section
Installation
Enter recovery
Make a nandroid back up
Make full wipe (except wipe sd) for the first time installation
Flash from ZIP: Select ROM and reboot
Flash GAPPS and reboot
Have fun!
Click to expand...
Click to collapse
Thanks marko....Admire your works....hope you will clear the bugs soon....nice to see you here....

Marko, I flashed the ROM on first page but it freezes on the boot logo, pls help.

you have done all wipe? wipe all and mount /system format /system?

markolino631 said:
you have done all wipe? wipe all and mount /system format /system?
Click to expand...
Click to collapse
Yes Marko, all your previous versions I was able to flash successfully but not this one.

it's strange! for other works

markolino631 said:
it's strange! for other works
Click to expand...
Click to collapse
I was able to install it properly now. I redownloaded the rom. Previous one was corrupt.

Corrupted?
amolebirje1982 said:
I was able to install it properly now. I redownloaded the rom. Previous one was corrupt.
Click to expand...
Click to collapse
Which is the corrupted one?

abhishek046 said:
Which is the corrupted one?
Click to expand...
Click to collapse
no, I mean the file I downloaded earlier it was not completely downloaded. I redownloaded and then flashed, no problems then.

[MOD] [All ROMS] F2FS for TF700T

******************* INFO&CREDITS *******************​
I know i've been away from this forum for a lot of time (mostly my Nexus 5 fault ) but when i've seen that F2FS it's now possible on this device i decided to create an easier way to create&use this filesystem,so average users can try it and decide.The best part of XDA is that everyone can contribute in the best way he/she can.
Anyway all credit goes to: samsung (for the f2fs) , Alex Page <[email protected]>, @_that @Dees_Troy (TeamWin ), @dasunsrule32 (cyanogenmod), @Hundsbuah and to everyone who contributed to make this device better.Thank You all!
******************* About F2FS *******************​
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk (Hangul: 김재극) 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.
Samsung chose a log-structured file system approach, which it adapted to newer forms of storage. F2FS also remedies some known issues of the older log structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. Because a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), Samsung also added various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms. (source Wikipedia )
******************* WARNING *******************​
* Please be aware that F2FS is still experimental and DATA LOSS or other issue may occur.
* You agree to use this MOD on you own risk and i don't take any responsability if you encounter any issue or if your personal data is lost
******************* Requirements *******************​
Your tf700t device must be Unlocked
An external MicroSD card or a PC (for backup/restore )
A brain
******************* Preinstalling steps *******************​
Backup of your personal data to an external card or PC (photo,music,ringtones,etc)
Create a backup from recovery and store it in a safe place (external sdcard or PC)
Download twrp_f2fs from the Download Section (second post )
Download a kernel from the Download Section (second post) - _that and Hundsbuah are for stock based roms only ; CM11 is for Cyanogenmod based.
Download your favorite rom
******************* Install Steps *******************​
1) Install twrp_f2fs recovery using one of the methods bellow
Fastboot method
Code:
fastboot -i 0x0B05 flash recovery twrp_f2fs.blob
fastboot -i 0x0B05 reboot
Terminal/ADB
Save twrp_f2fs.blob to the root of your /sdcard directly (internal memory only).
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
Code:
su
dd if=/sdcard/twrp_f2fs.blob of=/dev/block/mmcblk0p4
and reboot your device
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2) Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
3) Enter the WIPE menu and select Format DATA ( warning all your personal data will be lost )
4) Wait until the format is complete then reboot to recovery again (if previous step was succefull your DATA partition is now F2FS )
5) Wipe Cache (Wipe Menu --> Advanced --> select only Cache partition and go)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6) ROM installation ( you can choose several methods to get your system back and running)
a) if you already have a System installed you can skip to step 7)
b) install your favorite ROM from external sdcard and Reboot to Recovery
c) restore your previous backup from an external sdcard (select only SYSTEM and DATA partitions) and Reboot to Recovery
7) Install one of the F2FS kernels (based on the ROM you have) and REBOOT SYSTEM
Remember that everytime you install a new ROM you have to Reboot to Recovery and install an F2FS kernel.
That's it,the system should boot with an F2FS data partition,start playing with it. :good: :laugh:
******************* Rom2SD_F2FS *******************​
NOTE:
In order to use Rom2SD you need to have a running and rooted stock-based ROM with busybox and a kernel with preinit support (_that and hundbuah kernels are one of them
Also make sure there are no residual folders&files from an old Data2SD/Rom2SD setup ( basically delete the /boot folder in /system if there is one)
Partitioning your MicroSD -- > You can find a good tutorial (thx @sbdags) here
**** Install steps ****
Download all the files from Rom2SD section in the Download page ( post #2) and save them on MicroSD
Download a Kernel from the Download page ( choose the correct one depending on your favorite ROM base) and save it to MicroSD
Boot your device in Recovery
Install Rom2SD_F2fs.zip
Install Rom2SD1.zip
Go to Mount option and make sure Data partition is unchecked ,if not,uncheck it and press Home icon to go back to the Main menu (don't press back)
Go to Wipe and press Format Data (this will format your external data partition to F2FS) - if is failing check the Mount option again
Install your favorite ROM (don't reboot)
Install an F2FS Kernel (don't reboot)
Install Rom2SD2.zip
Reboot and enjoy Rom2SD_F2FS
**** Tips ****
If you have a Backup for the Rom installed on external then you can restore your data and avoid the waste of time needed to configure everything again
Boot to Recovery
Install Rom2SD1.zip
Go to Restore and select the desired backup and check only Data
Swipe to restore and then reboot to system
******************* Back2EXT4 Script *******************​
Description: This script will help you format the Data partition to EXT4 without the need to change the recovery.
Instructions:
**** Internal Data ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk0p8) partition it's EXT4 but you can still use twrp_f2fs
**** External Data (Rom2SD/Data2SD setup) ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Download Rom2SD1.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Rom2SD1.zip
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk1p2) partition it's EXT4 but you can still use twrp_f2fs
*********************************************************************************************************************************************************************************************************************
Note: As you can see there are several ways to get your system up and running after your Data partition was formated with F2FS.Also based on my tests you can use an "old" EXT4 backup to restore on F2FS and should work viceversa too.
I will also update this thread with info on how to go back to EXT4 without changing the recovery,and also i will try to modify the Data2SD/Rom2SD scripts and make them F2FS compatible.
And btw,please kick that THANKs button

Downloads
********************************************************* Downloads *********************************************************​
++++++++ Kernels ++++++++
That_F2FS.zip --> MD5 Sum: 1165247d099f5dbd5f5a4d4a848ff186
Kernel_F2FS_Hund_v3.4.5 --> MD5 Sum: 888e71f5fade857ed7a062dc08b36d77
CM11_Kernel_F2FS.zip --> MD5 Sum: e9772d2b8a63a009d0499c43fb93a6db
Build by @sbdags F2FS kernels
++++++++ Recovery ++++++++
twrp_f2fs.blob --> MD5 Sum: 4391cdfac9bf9660f52b8b0081543ea0
++++++++ Rom2SD_F2FS++++++++
Rom2SD_F2fs.zip -- > MD5 Sum: f5629e4fc9c40cbb7590152001de8179
Rom2SD1.zip -- > MD5 Sum: f6a6b0e5f0260078782a86c2e60c664e
Rom2SD2.zip -- > MD5 Sum: e82008368cb8ee663a70e63c6cb10040
++++++++ Back2EXT4 Script ++++++++
Format Data to EXT4.zip -- > MD5 Sum: 7ddbbbbe5d7e3c546c46ab8c185b4a70
********************************************************* Sources *********************************************************​
Recovery - build from the official sources available in Omnirom 4.4 tree (android_bootable_recovery)with @that kernel (kernel source ).
Hundsbuah kernel - original kernel from here + modified ramdisk
_that kernel - original kernel from here + modified ramdisk
CM11 kernel - Source + Patch

Pretoriano80 said:
Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
Click to expand...
Click to collapse
Even if you hadn't told me before, I could guess which kernel your recovery is using.
Thanks for making this package available to all users!
A warning to all potential users of f2fs: There is still no program to repair a corrupted filesystem - fsck.f2fs can only detect corruption but not fix it. Don't store anything important on f2fs.

Do you run into any issue with this f2fs so far?

LetMeKnow said:
Do you run into any issue with this f2fs so far?
Click to expand...
Click to collapse
Nope, no issue so far. At some point i was afraid that internal storage will die on me with all the formatting, installing and erasing i've did during F2FS tests, but still no issues.
Sent from my Nexus 5

Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?

deadlocked007 said:
So does this zips the full internal storage or just the data part with apps and stuff?
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Internal storage will be completely wiped,so /data/media too.
ariadnejro said:
Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?
Click to expand...
Click to collapse
Didn't experienced issues so far but i 'm using CromiX here.
F2FS it's useful mostly for random write (or writing operations in general) ,there's no point using it for /system or /cache imo.
Sent from my Nexus 5 using Tapatalk

I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk

berndblb said:
I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
twrp_f2fs it's based on official TWRP 2.7.0 and it should work fine with latest bootloader and all ROMs.
Basically i tested all those roms mentioned in your post and are working fine.
Sent from my Nexus 5

Seems to work well! I'm on the 3-19 build of CM11. Had really major IO issues with the device, nothing would make it even remotely usable, even on the performance CPU profile in both the cpu govenor and the asus cpu changer. It was always slow and laggy, it would not handle multiple things well, you basically had to single task. However, flashing this, doing my usual modifications, and it's making this baby fly again. I can open multiple apps and actually navigate without too much lag. Not sure if it's a placebo effect, but so far, it seems great, I'm able to install multiple things at once. I'll see how long this lasts (Wiping the SD can have some beneficial effects too) and I'll try to give an update later, it usually slows down after a few weeks. But this could be "settling" still, it's a fresh flash, even so, I'm happy it's usable again!

Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET

yew123 said:
Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET
Click to expand...
Click to collapse
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...

_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Well as long as you only do the data partition it should be OK. I'll look into f2fs support this week.

_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Thanks @_that, when i've got some free time i'll give it a go

CM10 kernel?
Have a request for you, guys. Can someone make f2fs kernel for CM10?
Because I really don't want update my TF700 to 4.4, and stock-based roms isn't my choice...

I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353

sbdags said:
I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353
Click to expand...
Click to collapse
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk

Frostbiter said:
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Should do.

delete please

sbdags said:
Should do.
Click to expand...
Click to collapse
I end up with encryption unsucessful error on boot using the _that/sbdags kernel then reboots and twrp runs an open recovery script, reformatting cache with the mk_ext4 (IIRC), then same error on boot.
The CM kernel runs smoothly for me, but cannot get the touchscreen to respond from a deep sleep. The screen will turn on / off with power button press, but unable to get past the reboot screen or slide to wake screen because there isn't a response with touch. Fully charged the screen reads 'connect your charger' and will not connect to adb so I could not get a log for you.

[DEV][WIP][RECOVERY][TWRP 2.7] TWRP Touch Recovery for Samsung Galaxy S Duos[ALPHA 1]

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.
Phone look:
Tablet look:
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
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
DOWNLOAD:
Latest Release
INSTALLATION
Power off your Galaxy S Duos
Get into Download mode by pressing Volume (-) + Home + Power Keys followed by Volume (+) to Confirm.
Step:1 - Press "PDA" button and choose the filerecovery.tar.md5 !
Step:2 - Press "Start" button under Execution.
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.
Credits-
@coolamit for testing.
XDA:DevDB Information
TWRP - kylexx, Tool/Utility for the Android General
Contributors
v_superuser
Version Information
Status: Stable
Stable Release Date: 2014-04-21
Created 2014-04-21
Last Updated 2014-08-18

Note - There might be some things broken, you need to keep calm.
Also, you need to install with the update package from codename13. (Thanks to @coolamit )

Man this recovery almost screw up my phone. for no reason from a certain point the restored backups doesn't boot anymore, stuck at Samsung logo, tried making other backups, reflash twrp, first cwm then twrp but nothing.
The only one working was AN old backup of a week ago, restored that.
I can't use this if it isn't 100% reliable sorry

holymoz said:
Man this recovery almost screw up my phone. for no reason from a certain point the restored backups doesn't boot anymore, stuck at Samsung logo, tried making other backups, reflash twrp, first cwm then twrp but nothing.
The only one working was AN old backup of a week ago, restored that.
I can't use this if it isn't 100% reliable sorry
Click to expand...
Click to collapse
What else do you expect from an Alpha build? :/

v_superuser said:
What else do you expect from an Alpha build? :/
Click to expand...
Click to collapse
ok, I will wait for a more stable version, I like this recovery specially for the compression of backups that saves a lot of space

Awesomee and good work sir ...
can weget for ldpi devices like galaxy pocket,y etc phones ..?? in zip format

Does anyone know if it also works on ace 2x?
Sent from my GT-S7560M using XDA Premium 4 mobile app

Need help for s duos
do you have still s duos and could you please tell how to fix the animation problem in cm11 4.4.4 for s duos( in your cm11 there is no such problem)

I just installed sucefully, but when boot in recovery mode, just hang up.... therefore, the phone boot normally... well, I also lost the root

Not booting in TWRP. Getting restarted every time I am trying to boot with VolUP+Power+Home. If I hold the keys it keeps rebooting, and if I release it boots to system.
If I execute the command from terminal
Code:
adb reboot recovery
it boots into Samsung stock recovery.
Also showing a yellow symbol (!) while booting.
Should I flash it to stock recovery image?
Or is there any other way out to update the recovery to TWRP?

Solved
Thanks to KlinkOnE and m4jonez.
First I installed (ROOT) Rashr - Flash Tool from Play Store as suggested in the post.
Then downloaded Recovery - TWRP 2.8.0.1 and Recovery - TWRP 3.0.2 as mentioned here .
Placed both of the .zip files in the internal memory.
Now I open Rashr and flashed the recovery selecting the .zip file of TWRP 2.8.0.1 (My phone is rooted, so Rashr was able to flash it). Then rebooted to TWRP. But, failed. Removed the battery and insert it again. Now with Vol + Home + Power key, booted the phone in TWRP. From TWRP installed the TWRP 3.0.2. Rebooted to TWRP. It works fine now.

hcp006sl said:
Thanks to KlinkOnE and m4jonez.
First I installed (ROOT) Rashr - Flash Tool from Play Store as suggested in the post.
Then downloaded Recovery - TWRP 2.8.0.1 and Recovery - TWRP 3.0.2 as mentioned here .
Placed both of the .zip files in the internal memory.
Now I open Rashr and flashed the recovery selecting the .zip file of TWRP 2.8.0.1 (My phone is rooted, so Rashr was able to flash it). Then rebooted to TWRP. But, failed. Removed the battery and insert it again. Now with Vol + Home + Power key, booted the phone in TWRP. From TWRP installed the TWRP 3.0.2. Rebooted to TWRP. It works fine now.
Click to expand...
Click to collapse
pls help i'm new to the whole rom flashing thing. i tried what you wrote but the Rashr dosnt seem to find the TWRP both in my phone and external memory. i tried it on both core prime (SM-G360H) and (GT-I9060). i rooted both with kingroot via pc. thanks in advance for your assistance.

digitzonline said:
pls help i'm new to the whole rom flashing thing. i tried what you wrote but the Rashr dosnt seem to find the TWRP both in my phone and external memory. i tried it on both core prime (SM-G360H) and (GT-I9060). i rooted both with kingroot via pc. thanks in advance for your assistance.
Click to expand...
Click to collapse
I don't think this TWRP is for those two models - Core Prime and Grand Neo. Please download TWRP for your phone.
For GT-I9060 follow the thread [RECOVERY][GT-I9060] TWRP 2.8.0.1 touch recovery [UNOFFICIAL] and you can download the TWRP recovery for I9060 from here -Mod edit link removed ppc
For SM-360H follow the thread [Recovery] Official TWRP SM-G360H.
Please don't use king root for rooting. If you have used, replace it with SuperSU. Super-Sume Pro is the app that replaces KingRoot by SuperSu.

[MOD][07 August] MultiROM v32a

Code:
#include
/*
* Your warranty is now void.
*
* I'm 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.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy ACE 3 LTE. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from external SD card. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the image above. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from Internal memory and MicroSD Card (non tested)
Warning!
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. Always.
Installation, Note: Only manual installation is supported, because this mod is not officially supported.
MultiROM has 3 parts you need to install:
MultiROM
Modified recovery
Patched kernel
Now let's head to the installation. Note: Your primary ROM is recommended to be lollipop, because it doesn't act well as a secondary, due to enforcing selinux. Although you can use it as secondary, but change it's selinux status. My setup is Lollipop as primary, and KitKat as secondary. Stock ROM was not tested, because I hate it
I spent about 5 days working on this. My head will explode There is a tiny issue. MultiROM boot menu does not show up as it should. That's why we should use the MultiROM manager apk. and switch ROMs from the app.
Attention: The steps are if you use CM-12.1 as primary ROM
Kernel for Stock ROM with kexec-hardboot patch here
Step 1: Install this patched kernel over CM12.1. Or this, if you want OC.
Step 2: Install the modified Multirom Manager apk, I added support for our device
Step 3: Install Multirom
Step 4: Install MultiROM TWRP, via previous TWRP recovery, it can flash images
Step 5: Reboot into new recovery
Step 6: Install CM11, as secondary ROM!!
Step 7: Go to recovery-->Advanced-->MultiRom-->List ROM-->Choose CM11-->Flash Zip. Flash either stock kernel, or oc_kernel. Both include the necessary kexec-hardboot patch. Usually Multirom requires only primary ROM to have the kexec-hardboot patch, but in our case it does not work this way.
Now you are ready to switch ROMs. Ooh, almost forgot. MultiROM boot manager will show up if you connect the phone for offline charging, you will find out what happens on each case. This is the only bug that I can't resolve yet. Although multirom can be used, with this bug.
Code:
Update 20150829: Download everything from this [URL="https://androidfilehost.com/?w=files&flid=37974"]folder[/URL]
Kernel will be updated when ROM is built
Changelog: Re-implemented kexec hardboot and fixe last_kmsg creation
Video on how to install
Video on how to flash updates
*Thanks Tech Tutorials channel for the videos
NOTE: If secondary ROM does not boot, select Restorecon under multirom
Click to expand...
Click to collapse
Switch ROMs from the MultiRom manager app
NOTICE: I can't guarantee it will work on other variants rather than "R"
To uninstall Multirom simply flash this
You current ROM will not be erased by the installation.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using MicroSD Card
During installation, recovery lets you select install location. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - Add ROM to boot manager
- List ROMs - List installed ROMs and manage them
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - Well, settings
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - Flash ZIP to the ROM, for example GApps
- Add/replace boot.img - Replaces boot.img used by the ROM, this is more like developer option.
Source Code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
CM12.1 stock kernel w/ kexec-hardboot patch- https://github.com/kostoulhs/android_kernel_samsung_msm8930-common/tree/cm-12.1
CM11 stock kernel w/ kexec-hardboot patch- https://github.com/kostoulhs/android_kernel_samsung_msm8930-common/tree/cm-11.0
Stock kernel for stock rom w/ kexec-hardboot patch - https://github.com/kostoulhs/android_kernel_samsung_loganrelte/tree/master
MultiROM device tree - https://github.com/kostoulhs/android_device_samsung_loganreltexx/tree/multirom
Big thanks to Tasssadar for this awesome utility.
Also thanks @Grarak for the melius patch, i was based on it

Reserved

All the zip files listed above(steps 1 and 3) should be installed via TWRP, is that correct?

Levivig said:
All the zip files listed above(steps 1 and 3) should be installed via TWRP, is that correct?
Click to expand...
Click to collapse
Exactly
Sent from my GT-S7275R

This looks great, will defenatly try it. With 4,5 GB free internal memory do you recommend installing rom's on internal or SD ?

F. Dutch said:
This looks great, will defenatly try it. With 4,5 GB free internal memory do you recommend installing rom's on internal or SD ?
Click to expand...
Click to collapse
Installing on internal works. I haven't tried to install on sdcard yet
My setup is Lollipop as primary and KitKat as secondary, installed on internal
Sent from my GT-S7275R

kotzir said:
Installing on internal works. I haven't tried to install on sdcard yet
My setup is Lollipop as primary and KitKat as secondary, installed on internal
Sent from my GT-S7275R
Click to expand...
Click to collapse
Can I Make My Setup Like This ? :
Stock ROM(4.2.2) as primary and Lollipop as secondary , Stock ROM installed on internal , Lollipop ROM installed on SD card .
And my sd card use ext4 partition , is this partition supported ?
This is amazing feature !
Thanks a lot for this great work !
Sent from my GT-S7275R using XDA Free mobile app

zh_eco said:
Can I Make My Setup Like This ? :
Stock ROM(4.2.2) as primary and Lollipop as secondary , Stock ROM installed on internal , Lollipop ROM installed on SD card .
And my sd card use ext4 partition , is this partition supported ?
This is amazing feature !
Thanks a lot for this great work !
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
Multirom works on fat systems on sdcard as fas as I know, see more info about the limitations on the OP. To use stock ROM you need a stock kernel with kexec hardboot patch, I have already patched it, it is also available on my github. I just haven't built it. I can build it although
Edit: Due to the bug, that multirom does not show up on boot, we actually can't install ROMS on Sdcard, they are not visible by MultiRom manager app.
Edit2: stock kernel with kexec-hardboot patch download
Edit3: Trying to make it fully functional
Sent from my GT-S7275R

kotzir said:
Multirom works on fat systems on sdcard as fas as I know, see more info about the limitations on the OP. To use stock ROM you need a stock kernel with kexec hardboot patch, I have already patched it, it is also available on my github. I just haven't built it. I can build it although
Edit: Due to the bug, that multirom does not show up on boot, we actually can't install ROMS on Sdcard, they are not visible by MultiRom manager app.
Edit2: stock kernel with kexec-hardboot patch download
Edit3: Trying to make it fully functional
Sent from my GT-S7275R
Click to expand...
Click to collapse
So I can't install any ROM on the SD card ..
until you fix the bug .. Right ?
Or just we will never can install ROMs on the SD card ?
Sent from my GT-S7275R using XDA Free mobile app

zh_eco said:
So I can't install any ROM on the SD card ..
until you fix the bug .. Right ?
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
you can boot into multirom menu, if the phone is off and you connect it to the charger, so you can experiment a little

kotzir said:
you can boot into multirom menu, if the phone is off and you connect it to the charger, so you can experiment a little
Click to expand...
Click to collapse
So we will stay do this , just if we install a ROM in the SD card .
Or what ?! :|
OK , after flashing the stock kernel with kexec-hardboot patch, I can't flash any other kernel like arasma kernel in my stock ROM(4.2.2) ?
If I can't .. Can you make a kexec-hardboot patch for arasma kernel ?
Here : http://d-h.st/aYr
Or .. Can you make the lollipop kernel (1.7GHz) work on the stock ROM ?
Sent from my GT-S7275R using XDA Free mobile app

Its not my problem if I'm always not understand.
Its my brain problem ..
Just answer me ..
Why you always Ignore me ?
I'm just asking you , you can tell me oh I'm sorry ! I can't .. Just like this and I will accept .

zh_eco said:
Its not my problem if I'm always not understand.
Its my brain problem ..
Just answer me ..
Why you always Ignore me ?
I'm just asking you , you can tell me oh I'm sorry ! I can't .. Just like this and I will accept .
Click to expand...
Click to collapse
Mate I want to answer you and I do the best I can. Now I am working to make multirom fully functional, what don't you understand? The same time I am studying. It is pretty hard for me. The thing you ask me requires fully functional multirom. Enjoy it as it is, if you can and wait for the fix. Thanks
*Also, I will modify the stock kernel, as the others

kotzir said:
Mate I want to answer you and I do the best I can. Now I am working to make multirom fully functional, what don't you understand? The same time I am studying. It is pretty hard for me. The thing you ask me requires fully functional multirom. Enjoy it as it is, if you can and wait for the fix. Thanks
*Also, I will modify the stock kernel, as the others
Click to expand...
Click to collapse
:good::good: Nice Work Man

zh_eco said:
Can I Make My Setup Like This ? :
...my sd card use ext4 partition , is this partition supported ?
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
May I ask why you do this?
MTP practically destroys any real world benefit that EXT could possibly offer you, and if you use UMS et al you'll hit permissions issues with the media that completely ruin its ability to function as removable storage unless every single one of the systems it touches only has a single user or you carefully craft the system environment so that the user always has the same UID.
It's just weird to use a journalled filesystem with access permissions as removable storage. Either MTP destroys any gains you might possibly get, or UMS makes it impossible to access the contents of the volume on ~99% of all the systems you'll ever encounter in the wild. Ever wondered why you never see external storage volumes with permission based filesystems? This is why. It's largely silly.

I tried to restore a backup of stock rom, i want to try if it works and maybe use it as 3rd rom but CWM says .android_secure.vfat.tar and .Android_secure.vfat.Tar.a are missing does anyone know what it means and how to fix it. Does CWM version matter? Can TWRP instal backups made by CWM?

F. Dutch said:
I tried to restore a backup of stock rom, i want to try if it works and maybe use it as 3rd rom but CWM says .android_secure.vfat.tar and .Android_secure.vfat.Tar.a are missing does anyone know what it means and how to fix it. Does CWM version matter? Can TWRP instal backups made by CWM?
Click to expand...
Click to collapse
To use it with stock ROM, you need to install a stock kernel with hardboot patch, there is one in the OP. TWRP can't restore backups from CWM, different format of backup. I don't see any reason of using CWM, since there is TWRP.
Sent from my GT-S7275R

kotzir said:
To use it with stock ROM, you need to install a stock kernel with hardboot patch, there is one in the OP. TWRP can't restore backups from CWM, different format of backup. I don't see any reason of using CWM, since there is TWRP.
Sent from my GT-S7275R
Click to expand...
Click to collapse
Thanks but the only backups i have of stock are made with CWM. When i try to restore it says .Android_secure.vfat.Tar and .Android_secure.vfat.Tar.a are missing so i can't restore and make a backup with TWRP. Found some info about it and trying tot make it work right now.

kotzir said:
Video on how to install
Video on how to flash updates
*Thanks Tech Tutorials channel for the videos
Click to expand...
Click to collapse
Thank U Very Much @kotzir For Adding My Videos To "OP"

Small update, check OP