Recovery Downloads
Supported recoveries:
* TWRP
--------------------------------------------------------
* PhilZ-Touch-Recovery
CWM Base v6.0.5.1; Advanced Edition v6.59..x (discontinued)
--------------------------------------------------------
* CWM 6.0.5.1 Swipe-Edition - Update (discontinued)
--------------------------------------------------------
Code:
[B][COLOR="Red"]I am not responsible for bricked devices, dead SD cards.
I don´t own a P51XX and can´t test it myself.
Use on your own risk![/COLOR][/B]
I compiled all recoverys from Source myself!
I hope you like my work! Don´t forget the Thanks-Button
All latest Recovery´s can flash Android 4.4 (KitKat) and Android 5 (Lollipop) Roms!
1. Screenshots (later), general information, credits etc. (this post)
2. Information about the Recovery´s (later)
3. Downloads (TWRP, PhilZ Touch, CWM)
4. General FAQ & Developer FAQ
Encryption - TWRP is a must have!
Backup all important stuff! We need to format the device!
Make sure using latest TWRP
Wipe -> Advanced Wipe:
Cache
Dalvic
System
Data
Wipe -> Format Data -> Type yes to confirm
This is the most important step! It will keep some space for the footer! Without that encryption is not possible!
Flash Rom
Reboot
Set a Pin for Lockscreen
Encrypt your device
If done boot back in TWRP - TWRP will promt you to enter the PIN
If you haven't done Step 4 you'll get this error in logcat:
Code:
E/Cryptfs ( 105): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Wipe->Format Data is the only method that fully recreates the file system and obeys the length needed for encryption!
Thanks
@Phil3759 for his PhilZ Touch and Advanced CWM
@Dees_Troy and all the TWRP-Team for this great recovery
@ketut.kumajaya for his "android_kernel_samsung_espresso10" source
@CodyF86 for CM11 tree and his forked "android_kernel_samsung_espresso10" source; but i needed to switch to CM10.2
@gr8nole for helping me make internal SD visibile in TWRP, fix Touch-Orientation etc.
@ CyanogenMod-Team (thanks @codeworkx for supporting our device) for CM10.2 source
@ All testers - Special thanks @tetakpatak !!!
@budies3 for testing and confirm working TWRP 2.6.3.1 on P5110
XDA:DevDB Information
[P51xx] Recoveries: TWRP | PhilZ Touch | CWM , Tool/Utility for the Samsung Galaxy Tab 2
Contributors
Android-Andi
Version Information
Status: Stable
Created 2014-05-20
Last Updated 2015-08-03
All latest Recovery´s can flash KitKat-Roms without getting "Error: 7" like using older recoverys
TWRP
I builded this recovery from source, thanks to all who made this possible!
It wasn´t really easy - my flashcounter now > 20 But it´s working
How to flash a zip (it´s not laggy - it´s only because it´s recorded from screenshots ):
PhilZ-NON-Touch-Recovery (Advanced CWM)
CWM Base; Advanced Edition
Missing Features from PhilZ TOUCH:
all gui options, include touch code
name the backup folder with current ROM name
custom zip install menu (Free Browse Mode + custom startup folder)
Create Update.zip from current ROM or from pre-existing backups
misc nandroid settings menu (but /preload is included by default and I added option to toggle compression under backup format menu)
All Information about Features etc. in PhilZ Touch Main-Thread
On-Screen Navigation:
Swipe somewhere on your screen up / down to change selections
Swipe to right to enter
Swipe left to go back
How to flash a zip:
Same like CWM - you only have more features.
CWM
How to flash a zip (it´s not laggy - it´s only because it´s recorded from screenshots )
On-Screen Navigation:
Swipe somewhere on your screen up / down to change selections
Swipe to right to enter
Swipe left to go back
DOWNLOADS
Please don´t mirror my files without my permissions!
Recovery & ROM Downloads for all supported devices can be found here
Click to expand...
Click to collapse
FAQ
GENERAL
1. I found a bug.
You can post all bugs in this Thread! Please tell us your Device and the File / Recovery (including Version number) you are using.
You can use your recovery to safe a recover.log on your device - you can post this log and me or other user will have a look on it.
Please give us detailed information - this meight speed up to fix it
2. I am getting "Error: 7" in recovery, what is wrong?
Be sure you flashed a Recovery for your device!
[For P5100 = P5100 Recovery ; P5110 = P5110 or P511X Recovery ; P5113 = Use P5110 or P511XRecovery(!)]
Be sure the file was made for your device!
Try the latest Version of Recovery for your device, maybe your recovery is to old!
For KitKat (Android 4.4):
All latest Recovery's posted here now can flash Android 4.4 Roms! You will get "Error: 7" if you use an older reovery!
Minimum: CWM 6.0.4.4 or TWRP 2.6.3.1 or PhilZ NON Touch 6.00.1 (Advanced CWM) - or use any newer Version if available for your device!
DEVELOPER
1. How to compile this recoverys from source?
You need to compile CWM first! It it works you can try building TWRP or Advanced CWM / PhilZ NON Touch recoverys!
2. How to compile cwm from source?
Follow the Guide on how to compile CyanogenMod from Source for P5110 - you need this setup!
(For p5100 replace "p5110" with "p5100")
Small changes to this Guide at the moment:
Replace
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
with init for CM10.2 source:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-[U][B]10.2[/B][/U]
Follow the Guide until you come to this:mentined
Code:
$ brunch p5110
to build recovery you need to enter this instead "brunch":
Code:
make clean && make -j# recoveryimage
(Replace the # with the core count +1, so if you have a dual core it's -j3 and a quad core becomes -j5, etc.)
If it finished compileing (if nothing goes wrong):
Code:
cd $OUT
You'll have your "recovery.img" inside it
You can flash it and see if it works!
3. I compiled a working CWM, how to compile PhilZ NON Touch from source?
Visit PhilZ Main-Thread and read the Developer Informations. You will find it here.
4 I compiled a working CWM and/or PhilZ NON Touch, how to compile TWRP from source?
You will find all informations here: [DEV]How to compile TWRP touch recovery
(You will maybe need to use https://github.com/TeamWin/Team-Win-Recovery-Project/tree/twrp2.7 as source instead the source from Omnirom)
Usefull links for Devs:
Unpacking and repacking recovery or boot image (LINUX!): http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html
Complete Installation Guide for Android SDK on Ubuntu: http://askubuntu.com/questions/318246/complete-installation-guide-for-android-sdk-on-ubuntu
How to Install Oracle Java JDK on Ubuntu Linux: http://www.wikihow.com/Install-Oracle-Java-JDK-on-Ubuntu-Linux
More will be added later... i am thinking about it (what to add)
Click to expand...
Click to collapse
Changelog:
Code:
28.01.2014
2.6.3.4 --> 2.6.3.5
Backup-Fix:
"Clear the relative directory before passing on to twrpTar with the
static du object. Otherwise we will not backup /system/media etc"
e.g. bootanimation not got backuped.
https://gerrit.omnirom.org/#/c/5154/
23.01.2014
2.6.3.3 --> 2.6.3.4
Compiled on Omni´s Android 4.4.2 Source as base
support using old property system
USB Support
(i cherry-picked this commits:
https://gerrit.omnirom.org/#/c/3389/ and https://gerrit.omnirom.org/#/c/3390/
and put this to the boardconfig [code]BUILD_OLD_SYS_PROPS := true
COMMON_GLOBAL_CFLAGS += -DBUILD_OLD_SYS_PROPS
this makes TWRP compatible
with the old update-binary (used in older roms and flahsable zips))
2.6.3.3: Recovery-Kernel updated from
Linux version 3.0.31-CM-g010f848 to 3.0.101-blackhawk
Changed Source:
https://github.com/kumajaya/android_kernel_samsung_espresso10
2.6.3.2 - not released - recovery kernel updated
2.6.3.1: Initial release
Source:
https://github.com/CyanogenMod -CM10.2 branch
Recovery: https://github.com/TeamWin/Team-Win-Recovery-Project/tree/twrp2.7[/code]
CWM Based Touch-Recovery from Napstar:
CWM Base v6.0.4.5 - Update 21.12.2013
This is a One-Time-Build and i won´t update it!
!!! SORRY - FILE1 IS DOWN AND I WON´T UPLOAD IT AGAIN !!!
Hey together! Any feedback would be great!
Any Problems?
Android-Andi said:
Hey together! Any feedback would be great!
Any Problems?
Click to expand...
Click to collapse
Works fine on my P5110. Installed several roms, even simultaneously with other like tablet-ui patch and kernel.
Also backup and restore works fine.
Thanx for the great work.
Grtz,
John
Android-Andi said:
Hey together!
I updated kernelsource. you can test TWRP 2.6.3.3 if you want - it´s not tested by me.
Any feedbacl would be great
You´ll find flashable zips for custom recovery´s and odin flashable *.tar.md5 here: https://www.file1.info/album/L0zFSb1
Click to expand...
Click to collapse
Link doesn't work...
from gt-p5110
nachordez said:
Link doesn't work...
from gt-p5110
Click to expand...
Click to collapse
http://www.file1.info/OKRmlyp
found in OP
cheers
nachordez said:
Link doesn't work...
from gt-p5110
Click to expand...
Click to collapse
All Download-Links in 3rd post:
http://forum.xda-developers.com/showpost.php?p=47970089&postcount=3
Yeah link doesn't work. In that page there is nothing where i could start downloading. Nothing i click won't start download not even from any mirrors, yes even from no javascript link.
Try another browser, i can mirror it for you maybe later to devhost
@T3ER Here is the mirror http://d-h.st/users/Android-Andi/?fld_id=28391#files
Android-Andi said:
@T3ER Here is the mirror http://d-h.st/users/Android-Andi/?fld_id=28391#files
Click to expand...
Click to collapse
Thank you!
Android-Andi said:
Hey together! Any feedback would be great!
Any Problems?
Click to expand...
Click to collapse
Working great on my P5113. Thank you! :good:
OP Updated with new Download-Links for Different CWM / CWM Based Recoverys.
Something´s comeing.....
{
"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"
}
Click to expand...
Click to collapse
Edit:
Download-Links now Available!
@Android-Andi....I'm a TWRP'er but that looks Bada**. Much thanks for all your great work on these devices.
black screen after flashing recovery
I rooted my galaxy tab 2 10.1 5100 and tried flashing the custom recovery, but it doesn't seem to work. When I hold down the buttons to go into recovery it say booting recovery and the screen goes black and nothing happens. I tried waiting a few mins to let it load and nothing happens. I've tried other recoveries and none of them are working. I tried a factory reset and rerooting and still nothing. I've rooted and installed recovery on several devices and never had issues like this..any ideas?
Wich of the recovery are you talking about?
Have you been on Stock Recovery before?
Flashed the *.tar.md5 as PDA in Odin?
Please write all steps you have done, Step by Step.
Try latest CWM:
uncheck Auto-Reboot in Odin too.
When it finished flashing boot into recovery directly from Downloadmode.
Related
Hi there, i'm starting here a discussion thread about Team Win Recovery Project 2.x for our HTC One SV.
Team Win Recovery Project 2.x, 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.
Click to expand...
Click to collapse
{
"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"
}
Pictures by TWRP
As long as i know it will work for k2_u and k2_ul (LTE), cause both have the same partition layout.
This recovery don't work for boost mobile users!
Notice:
This is not my work, i'm not the developer of it!!! I only start the thread here about it because the dev is a russian guy (and i don't know, if he is here at xda and if he speaks english language).
Please be sure what you are doing, when you flash it, bricks can happen and i am not responsible for damaged devices. Do at your own risk!
Credits:
- xpirt for building it
- Modding.MyMind for his open mind
- MikG for earlier versions
- Team Win Recovery Project
- rollon76 for posting this here on xda
- jmztaylor (for being a great guy and help if needed)
- bkcokota (for his cwm recovery, a start for development)
Important: Recommended for hboot 2.21!
Download:
--------------------------------------------------------------------------------
This is not for boost mobile users!
You can find TWRP Recovery 2.7.0.1 (made by xpirt, credits and thanks to him) here.
Only for k2u & k2ul!
--------------------------------------------------------------------------------
The recovery for boost mobile (K2_CL) users is in the second post!!!
--------------------------------------------------------------------------------
How to install:
Download the img file and rename it to recovery.img
Put it into your fastboot folder and start a command window there.
Boot your phone into fastboot USB mode (bootloader + device plugged to pc)
Enter the following command:
Code:
fastboot flash recovery recovery.img
That's it.
K2_CL ONLY!!!!!
Kernel Source: Click Here!
Changelog Version 2:
Code:
* From commit [URL="https://github.com/ModdingMyMind/android_kernel_htc_k2_cl_twrp/commit/86a317157a741ef12042426696e3c84eeed3e263"]86a317157a[/URL] on my github.
* Kernel built in version 2.7.1.0
* Disabled Module support
Changelog Version 1:
Code:
* From commit [URL="https://github.com/ModdingMyMind/android_kernel_htc_k2_cl_twrp/commit/c34ea02e20b758e78cae9f8b8bc975d268accd84"]c34ea02[/URL] on my github.
* Kernel built in version 2.7.0.2[B]d[/B]
* Added full SELinux support.
* Removed HTC write protection.
---------------------------
---------------------------
TWRP 2.7.1.0 - for 4.2.2
TWRP 2.7.0.2d - for 4.2.2
TWRP 2.7.0.2c - for 4.2.2
TWRP 2.7.0.2b - for 4.2.2 (deprecated)
TWRP 2.7.0.2a - for 4.2.2 (deprecated)
---------------------------
---------------------------
TWRP source was patched from https://gerrit.omnirom.org/#/c/6283/
This patch allows the ability to take screenshots while in the recovery. It has not been merged over to the TWRP source yet so only unofficial builds at this moment will be seen with this feature.
To take screenshots while in recovery just press both the power key and volume down key. The screen will flash. It will naturally store the screenshot in your pictures folder of your sdcard if mounted in either your internal or external.
TWRP Changelogs:
Code:
[U]2.7.1.0
[/U]Built with custom kernel.
- [B]Removed custom theme and reverted back to stock theme.[/B]
- Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button.
- Various bugfixes to backup and restore
- Improvements to USB storage handling
- Added a class to search for files to make finding the correct brightness file automatic in most cases
- Various other bugfixes and tweaks
[U]2.7.0.2d[/U]
Built with custom kernel.
- Added full SELinux support
- Completely removed HTC write protection.
[U]2.7.0.2c[/U]
Fixed init.rc to allow communication with binaries in /sbin.
TWRP 2.7.0.2c is built ready for SELinux, but the kernel is stock. Until they release the source I can't modify the kernel to support SELinux. This is really only needed for having 4.3+ roms but I want to include it in case the day comes and we see CM, AOSP, or possibly other sources.
[U]2.7.0.2b[/U]
Minor theme adjustment
Upgraded screenshot functionality throughout entire recovery
Note - version 2.7.0.2a screenshots are limited to only the main page
TWRP 2.7.0.2b is built ready for SELinux, but the kernel is stock. Until they release the source I can't modify the kernel to support SELinux. This is really only needed for having 4.3+ roms but I want to include it in case the day comes and we see CM, AOSP, or possibly other sources.
[U]2.7.0.2a[/U]
Built from CM11 and Omni 4.4 sources.
Extended backup options.
1. System
2. Boot
3. Cache
4. Data
5. Recovery
6. Misc
7. Firmware_radio
8. Firmware_q6
9. android secure
*** I think I listed them all ;)
Built in AromaFM.
Implemented screenshot functionality.
Added offmode charging.
Completely updated to fit with 4.2.2.
Includes Holofied Black Theme.
TWRP 2.7.0.2a is built ready for SELinux, but the kernel is stock. Until they release the source I can't modify the kernel to support SELinux. This is really only needed for having 4.3+ roms but I want to include it in case the day comes and we see CM, AOSP, or possibly other sources.
HTC Dumlock Instructions:
HTC Dumlock Instructions specifically for S-On users but S-Off users can use it as well if they choose to:
1. Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery.* No fastboot booting it.* We need it in recovery so that this build of TWRP will be flashed to your boot.* This new build of TWRP has features in it to easily restore your original boot.
2. Reboot into recovery.
3. Make a backup of your phone.
4. Tap Advanced.
5. Tap HTC Dumlock. (If you don't see HTC Dumlock then you need to remove any custom TWRP theme that you might be using.)
6. Tap Install HTC Dumlock.* This will install the app and binaries needed to make everything work nicely.
7. Reboot your device.
8. Find and open the HTC Dumlock app.
9. If/when prompted, give the app root (SuperUser) permissions.
10. Tap the Execute HTC Dumlock button.
11. Wait patiently for a couple of minutes.* It takes a little while.
If your device doesn't reboot automatically, reboot it manually.* Reboot it normally.* DO NOT reboot it to recovery.
You should now be in your recovery, but your recovery is flashed into boot.
12. Tap Advanced.
13. Tap HTC Dumlock.
14. Tap Restore Original Boot.
Use your recovery like normal.* Flash a new kernel.* Restore a backup with a different kernel.* Do whatever you please!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Addition
This recovery also works in the ADB mode with root rigths.
In this mode, you can add (delete) files in the SYSTEM
on OS Jelly Beam
And sets the superuser, if superuser is not in the system.:good:
Are you the developer of it?
I hope it is ok for you that i have started a thread for it here?
Anyway, it works great and you have done it very well ! :good::good::good:
Thanks a lot!!
Thank you. Use it. Version 2.5.0.1 is made on the kernel 3.14.10-gf43d146.
Bootloader and boot restored only if you have S-OFF.
where can i download version 2.5.0.1?? i have 2.5.0 and it works great.
---------- Post added at 06:13 PM ---------- Previous post was at 06:06 PM ----------
MikG said:
This recovery also works in the ADB mode with root rigths.
In this mode, you can add (delete) files in the SYSTEM
on OS Jelly Beam
And sets the superuser, if superuser is not in the system.:good:
Click to expand...
Click to collapse
Is compulsory be S-OFF to delete files in system??could you explain how to do it??
thanks
titin83 said:
Is compulsory be S-OFF to delete files in system?
Click to expand...
Click to collapse
A custom kernel can do this also.
old.splatterhand said:
A custom kernel can do this also.
Click to expand...
Click to collapse
And is there alredy a kernel that let us do this?? By the way , what recovery are you using?? if is 2.5.0.1 , could yo tell me where download it?? in the russian page i got an error when i try to sign in there , and the translation with google is rather bad...
thanks
titin83 said:
And there is alredy a kernel that let us do this?? By the way , what recovery are you using?? if is 2.5.0.1 , could yo tell me where download it?? in the russian page i got an error when i try to sign in there , and the translation with google is rather bad...
thanks
Click to expand...
Click to collapse
To sign in there is really painful if you don't speak the language, but as far as i know it does not work as long you are on google translation. The captcha i could only pass with a guy from another board who speaks russian.
The recovery shows 2.5.0.0 but the filename from download page was Recovery_TWRP_2.5.0.1_HTC_ONE_SV.img so i think it is the same.
Kernel can be found here.
old.splatterhand said:
To sign in there is really painful if you don't speak the language, but as far as i know it does not work as long you are on google translation. The captcha i could only pass with a guy from another board who speaks russian.
The recovery shows 2.5.0.0 but the filename from download page was Recovery_TWRP_2.5.0.1_HTC_ONE_SV.img so i think it is the same.
Kernel can be found here.
Click to expand...
Click to collapse
And the last question , can i flash the kernel without installing the whole rom?? i mean , flash it in the rom that i update some weeks ago via OTA or have i to flash the ro that you have in your signature? My SV is K2_U , can i flash this despite be for K2_UL devices??
thanks
You can flash the kernel only and also for k2u (i have too).
If you are not S-off, you need to flash the zip in recovery and the boot.img inside with fastboot.
once i have flashed the kernel , what i have to do to delete some system app??
thanks again
Use a root explorer and go to system/apps/ and delete the one you don't need anymore (or rename it first to see if it causes problems).
But be carefull with what you delete and make a nand backup before!!!!!
titin83 said:
where can i download version 2.5.0.1?? i have 2.5.0 and it works great.
Is compulsory be S-OFF to delete files in system??could you explain how to do it??
thanks
Click to expand...
Click to collapse
Link in the header right.
S-OFF not need.
In the recovery mount SYSTEM. And the button ADVANCED-> File manager can work fine.
old.splatterhand said:
Use a root explorer and go to system/apps/ and delete the one you don't need anymore (or rename it first to see if it causes problems).
But be carefull with what you delete and make a nand backup before!!!!!
Click to expand...
Click to collapse
No, in JB OS files not be deleted.
Instead, use the file manager in the TWRP recovery.
edit: i was too fast... twrp doesnt work for me. it install perfectly but i cannot boot android anymore? does this work for someone else?
sakax said:
edit: i was too fast... twrp doesnt work for me. it install perfectly but i cannot boot android anymore? does this work for someone else?
Click to expand...
Click to collapse
Everything works fine in my device. Flash it again , perhaps something was wrong.
sakax said:
edit: i was too fast... twrp doesnt work for me. it install perfectly but i cannot boot android anymore? does this work for someone else?
Click to expand...
Click to collapse
This twrp recovery work on many device k2_u and k2_ul fine.
MikG said:
This twrp recovery work on many device k2_u and k2_ul fine.
Click to expand...
Click to collapse
my phone doesnt boot anymore after installing twrp recovery? do i have to reinstall kernel and system backup after flashing recovery? the problem is that i only have cwm backup available?
As long as i know, you can't restore cwm backup with TWRP. So you need to flash cwm and restore your backup with that.
PROJECT RECOVERY
DEVICES: XOLO Q800, GiONEE GN708W,FLY IQ446 + CLONES
Hey friends recently there has been loads of ROM comping up but porting recoveries has become completely stale and sulking. No DEV has taken interest either. So I am opening a Project Thread where everyone can participate in getting latest and awesome recoveries to our mobile .
PROJECT AIM:
1. Porting Latest Recovery
2. Testing
3. Solving Bugs
4. Publicizing!
WHO CAN JOIN : Any one can.. the recovery.img is open to all .. If you dont know how to edit recovery.img you can be really helpful by being a tester.
RULES:
1. Person who ports the basic recovery even if it is unstable will get the main credit for porting
2. Do not complain about the recovery.img if it is unstable. Please Report the BUG
3. If you are agreeing on being a tester , you are solely responsible for any damage to your mobile.
4. All people who help in solving bugs will be given credit
5. Please don't post a stable recovery under your name if you aren't the original porter. Request the original porter to post it any other forum or ask his/her permission if you want to do so.
6. All suggestions are welcome!
HOW TO REPORT BUG : FOR ALL
1. Mention the Recovery name and the BETA version no .
2. Mention all the problem in detail, as much as you can
3. Mention the solution or even a rough idea about how to solve if you know.
INSTRUCTION : (PORTERS)
This is for those who have ported the recovery by themselves and want help from others to solve bugs
1. PM Me about Recovery Name , Version , Features , Known Bugs
2. Upload the Recovery in d-h.st or Google drive
3. You can PM me for a newer version and i will upload it in here .
4. Once stable , You can (you wish) post in xda and other formus giving credit to those who helped you.
INSTRUCTION : (TESTER)
This is for those who would like new recovery and test them and help
1.No one from the forum is responsible for any damage to your phone
2.Keep a NANDROID back up
3.Try to go through every aspect of recovery
4.Post bugs accordingly
5.Testers will also be give credit..!
INSTRUCTION : TO FLASH RECOVERY
*HAVE A NANDROID BACKUP*
1.Install MobileUncleTools (apk in download link)
2.Copy the recoveryXXX.img to root of your extrenal sdcard not to any folder
3. Go to mobileunlce tools -> recovery update -> recoveryXXX.img -> ok -> reboot.
or
FOR Flashable Zip
1. Download the zip
2.Flash the zip via the current recovery
3.Reboot
4.Enjoy!!
RECOVERIES : (Ported)
1. CWM
2. TWRP
3. Carliv Touch Recovery
4. Cannibal Open Touch Recovery
5. Philz Recovery
CWM
CWM
About : No need introduction to this Recovery Do we?? It is the most basic and mother all other recoveries :
Version : 6.0.32 ( STABLE ) - By Taiwan101 Download : http://d-h.st/IIc
Latest version yet to be Ported!
RESERVED
TWRP Features :
Code:
What's new in 2.8.4.0:
Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
Fix some MTP related crashes and bugs
Eliminate TWRP toggling USB IDs during boot if MTP is enabled
Fix various adb sideload issues
Improve threading of actions
Eliminate separate thread for screen timeout
Update libblkid to 2.25.0
Use power button as back button on watch themes for easier navigation
Add mutex locking to data manager
Improve custom theme handling on encrypted devices
Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
Version :
1) 2.4.1.0 -STABLE - By - UKNOWN - Download here :http://d-h.st/k6i
2) 2.5.0.0 -STABLE - BY - UNKOWN - Download here : http://d-h.st/uaq
3) 2.8.4.0 - FULL SELINUX SUPPORT ( For Kitkat ROMz including CM 11 ) -STABLE - By Shikhar A
Recovery Img -http://d-h.st/qiOK
Flashable Zip : http://d-h.st/69uw or https://drive.google.com/file/d/0B9GVC-8ngPfqdk5uSEVnVm9jdDA/view?usp=sharing
THEME DEVELOPMENT FOR TWRP
As most of you would know twrp supports heavy themeing and it is also very simple to theme. This is because it woks on a very simple .xml . You can start trying to theme by just changin the folder lood text clor etc..Maybe later we will get to xml theming.
GUIDE : http://www.teamw.in/twrp2-theme-guide
PORTED THEMES :
Instruction
Download the .zip . DONT FLASH IT
Go to TWRP folder in root of your phone internal storage ( VVIMP) , if itz not here create one
Create a folder called theme in TWRP folder
Rename the downloaded theme zip file as ui.zip
Paste The ui.zip in theme folder
Repeat the same steps for your sd card too ( VVIMP)
Reboot and check out!!
1. MATERIALISED LIGHT THEME( for 2.8.4 only)
DOWNLOAD : http://d-h.st/TWmD
https://drive.google.com/file/d/0B9GVC-8ngPfqamlqZzlTOW9pMnM/view?usp=sharing
SCREENSHOT
{
"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"
}
2. MATERIALISED DARK THEME( for 2.8.4 only)
DOWNLOAD: http://d-h.st/vC2t
https://drive.google.com/file/d/0B9GVC-8ngPfqTDhDZVBkaTVsLTg/view?usp=sharing
SCREENSHOT
3. GOOGLE PLAY STYLE - MATERIALISED ( for 2.8.4 only)
DOWNLOAD : http://d-h.st/zg3K
https://drive.google.com/file/d/0B9GVC-8ngPfqRmJpZzdMdVI5cDg/view?usp=sharing
SCREENSHOT
RESERVED
Carliv Touch Recovery
About : Based on CWM (6.0.4.4) with full touch support and touch buttons menu. It has all functionality of CWM Recovery plus some added by me, and extra, Aroma File Manager support.
Code:
CHANGE LOG : V2.1
[SIZE="4"]removed swipe touch module developed by gweedo767 and now the touch is more stable.
new menu structure
a new "Wipe menu" with all wipes grouped
a new menu for advanced backup and restore
open recovery script ported from Cannibal Open Touch
in post #2 you will find builds with CUSTPACK support for phones that have that partition. Untested, because I don't have a phone with that partition.
in post #3 there are few builds with UBIFS support, ported from Christian Troy's source. I can't test them, so I expect some feedback from you.
There are more improvements in source and a few errors corrected.[/SIZE]
VERSIONS:
CTR v1.1 (STABLE) - By Shikhar A - Download Here : http://d-h.st/7wz
CTR v2.1 - To be ported
COT
Cannibal Open Touch Recovery
ABOUT : About Cannibal Open Touch:
Cannibal Open Touch is the next generation of custom recoveries. Jam-packed with cool and useful features, it can handle just about anything you can throw at it.
Code:
[SIZE="4"]Main Features:
1. Support for both Edify and Amend scripting (flash all ROMS!)
2. Theme support
3. Get out of recovery boot loops
4. Touch screen button controls!
5. Compatibility with Xionia nandroid backups (if on LG Optimus device)
6. GooManager support!
7. Internal e2fsprogs for size
8. Backported “retouch binaries” patch for ICS/JB compatibility
9. Advanced Backup
10. Delete old backups!
11. Persistent settings
12. User-defined backup locations!
13. ADB Sideload
14. Touchscreen calibration[/SIZE]
VERSIONS:
v2.1.3 ( STABLE ) - By Shikhar A - Download Here : http://d-h.st/jvC
RESERVED
Philz Recovery
ABOUT : SUPERIOR CWM BASED RECOVERY!
FIND EVERYTHING HERE :http://forum.xda- developers.com/showthread.php?t=2201860
VERSION :
v5 (Based on CWM 6.0.32) (UNSTABLE) (REMOVED) ( ERROR IN COMPILING)
RESERVED
RESEVED
RESERVED
RESRVED
Shikhar A said:
Philz Recovery
ABOUT : SUPERIOR CWM BASED RECOVERY!
FIND EVERYTHING HERE :http://forum.xda- developers.com/showthread.php?t=2201860
VERSION :
v5 (Based on CWM 6.0.32) (UNSTABLE) - By Shikhar A - Download here : http://d-h.st/oJY
Click to expand...
Click to collapse
its not backingup recovery. img & boot.img properly right ?
Sent from my GT-I9505 using Tapatalk
AnoopKumar said:
its not backingup recovery. img & boot.img properly right ?
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
YEs... i think some mistake while compiling.. i am removing.. will port TWRP 2.6 then come back to philz
Shikhar A said:
YEs... i think some mistake while compiling.. i am removing.. will port TWRP 2.6 then come back to philz
Click to expand...
Click to collapse
its unfixable to Mediatek devices i think
I tried.
AnoopKumar said:
its unfixable to Mediatek devices i think
I tried.
Click to expand...
Click to collapse
No .. it is possible... Philz has added MTK support .. in his version 6... check out... I made mistake.. In that ketornel where the main bootimg should be same as recovery. Fstab boot.IMG... I am busy with M E ROM too.. !
Shikhar A said:
No .. it is possible... Philz has added MTK support .. in his version 6... check out... I made mistake.. In that ketornel where the main bootimg should be same as recovery. Fstab boot.IMG... I am busy with M E ROM too.. !
Click to expand...
Click to collapse
i tried it from htc pico .. only the problem with recovery & boot img
Sent from my GT-I9505 using Tapatalk
AnoopKumar said:
i tried it from htc pico .. only the problem with recovery & boot img
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Well.. lets keep trying.. i read some one has ported it for mmx A110Q
TWRP 2.6
TWRP 2.6 Uploaded!! + Holofied play theme .. check out!!!
Shikhar A said:
TWRP 2.6 Uploaded!! + Holofied play theme .. check out!!!
Click to expand...
Click to collapse
Bro theme working good job
Sent from my GT-I9505 using Tapatalk
Great thread bro.. Sad, We can't get TWRP for Q700 due to Smaller Recovery Partition.
abhinav2hd said:
Great thread bro.. Sad, We can't get TWRP for Q700 due to Smaller Recovery Partition.
Click to expand...
Click to collapse
Thanks... will keep trying to solve TWRP bugs for q800 .. and you can extend your recovery partition... to 7mb and then you can try.... ..
AnoopKumar said:
Bro theme working good job
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Thanks... major credit to the main dev.. i just resized and edited xmlz..:laugh:
Twrp 2.8.4 + awesome themes up and running! Check out>.. :d
(Click on the image above to download my MultiROM Manager App)MultiROM for the Samsung Galaxy S3 i9305, brought to you by Alexander_the_B0ss
{
"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:
#include <std_disclaimer.h>
/*
* 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 S3 4G. It can boot any Android ROM . Besides booting from device's internal memory, MultiROM could boot from external SD card(untested). The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. 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.
Features:
* Multiboot any number of Android ROMs (as many as your internal memory can hold)
* Restore nandroid backup as secondary ROM (damn useful feature)
* Boot from Internal memory and MicroSD Card
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. I personally can't stress enough for you people to make nandroids becuase you never know.
Installation
Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app Install my modified app and select MultiROM and recovery on the Install/Update card the app is still in alpha, so don't select install, use manual install below. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are choosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM itself - download the ZIP file and flash it in recovery.
Modified recovery - download the ZIP file and flash it in recovery or Mobile Odin app to flash the recovery.img contained inside ZIP.
Patched kernel (Only TWO: AGNi PureCM or AGNi PureSTOCK) - Download the ZIP file and flash it in recovery (seems like kexec-hardboot isn't activated by psndna88, so menu won't show up on boot)
*Downloads in Post #2*
If your MAIN ROM is TouchWiz or TouchWiz based, please use AGNi PureSTOCK kexec-hardboot status unknown, someone with stock rom please install app and tell me if kexec-hardboot is enabled.
If your MAIN ROM is not TouchWiz, but CM or AOSP (basically custom rom except MIUI) use AGNi PureCM no kexec-hardboot, tested.
You current rom will not be erased by the installation.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using MicroSD Card (UNTESTED)
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.
Screenshots
Application
Recovery (Sorry for pictures...)
Bonus pic(zoom to see the RGBG-Matrix (PenTile))
My Homescreen and Lockscreen (for those interested)
Big thanks to Tasssadar for this awesome utility.
XDA:DevDB Information
MultiROM, multiboot tool for Samsung Galaxy S3 4G (i9305), Tool/Utility for the Samsung Galaxy S III I9300
Contributors
Alexander_the_B0ss
Version Information
Status: Beta
Current Beta Version: v32
Beta Release Date: 2015-08-30
Created 2015-08-29
Last Updated 2015-09-02
Reserved
DOWNLOADS
MultiROM itself: HERE (Check NOTE 2 below for testing zip)
Uninstaller: HERE
Recovery: HERE
Note 1: For recovery use 720x1280 multirom theme from here.
Note 2:
MultiROM Installer with MultiROMManager app and TWRP theme installation testing zip here. Basically what this zip does is, after MultiROM is installed, it copies to system/app my own version of MultiROM Manger to support i9305, then copies to the internal sdcard the theme for TWRP and sets the correct attributes.
What is that? I dont understand
a possibility to install more than just one operating system
Quick update for you guys:
Recovery works, but the theme is kinda weird, so use the theme provided for 'perfect' recovery
MultiROM menu won't show on boot, sent PM to Tassadar for help request. Meanwhile, i am trying to modify MultiROM Manager app to support i9305 to possibly have a workaround for the menu not showing up.
Stay tuned for more development and an OP update after everything is working. CYA
Another quick update for the ones interested in the project. I have succesfully compiled MultiROM Manger app that detects our device (after twenty attempts, then gave up and updated Android Studio to the latest version and redownloaded Android SDK and NDK. First attempt after reinstall worked).The APK fresh from the oven is here. This represents a milestone in MultiROM development because with the app now detecting the device one can avoid the boot menu not showing bug. BUT WAIT, THERE'S MORE
The bug i talked about is related to kernel, because the app doesn't detect kexec-hardboot.
Stay tuned for updated OP soon™.
Error in flashing. 'E: Error executing updater binary in zip '/external_sd/Roms/MultiRom/multirom-20150829-v32-UNOFFICIAL-i9305.zip'
Tried both with unmodified TWRP and MultiRom TWRP
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
fs71gh said:
Error in flashing. 'E: Error executing updater binary in zip '/external_sd/Roms/MultiRom/multirom-20150829-v32-UNOFFICIAL-i9305.zip'
Tried both with unmodified TWRP and MultiRom TWRP
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Click to expand...
Click to collapse
Are you really trying to install this on Note 4? Damn. It is only for i9305, aka m3xx aka m3 aka S3 4G. So WRONG FORUM
Alexander_the_B0ss said:
Are you really trying to install this on Note 4? Damn. It is only for i9305, aka m3xx aka m3 aka S3 4G. So WRONG FORUM
Click to expand...
Click to collapse
Sorry for your confusion but we also have an Eclipse for S3 LTE which is already in this forum and my device is undoubtedly also S3 LTE and not Note 4
fs71gh said:
Sorry for your confusion but we also have an Eclipse for S3 LTE which is already in this forum and my device is undoubtedly also S3 LTE and not Note 4
Click to expand...
Click to collapse
I don't want to keep this on, but check this post out http://forum.xda-developers.com/not...-x-teamwin-t2956011/post57742832#post57742832 and see the codename for the SM-910F and check your reply from before
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Alexander_the_B0ss said:
I don't want to keep this on, but check this post out http://forum.xda-developers.com/not...-x-teamwin-t2956011/post57742832#post57742832 and see the codename for the SM-910F and check your reply from before
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Click to expand...
Click to collapse
I guess the problem is with the rom specifically (some things left out while porting), as I got your your apk working with two other cm11 roms.
@Alexander_the_B0ss
Hi boss.
I like this dual-boot initiative but i have some problem with apk (device not supported (trelte)) but i think you can solve this.
I edit the updater-script and remove this line (assert(getprop("ro.product.device") == "i9305" || getprop("ro.build.product") == "i9305");) (i test now in terminal command: getprop ro.product.device and show me i9305 ..i dont now why i can't install zip package. but i solve this with removed line.
So, i install recovery (multirom recovery) and i install zip. I install your modded apk and i have error.
On recovery, i try to install a new rom, and was installed (but on internal_memory/multirom directory i dont see any folder/file..but my space on rom was used by "new rom")
I try to inject my kernel (pureSTOCK 5.9.2). Nothing happen when i reboot my phone. I think need to show a menu with "What rom do you want to boot"..but nothing.
I can help you with tests to dev this project.
Keep up
EDIT: And, i dont now how can install a theme for TWRP..because text buttons not aligned
il3gal said:
@Alexander_the_B0ss
Hi boss.
I like this dual-boot initiative but i have some problem with apk (device not supported (trelte)) but i think you can solve this.
I edit the updater-script and remove this line (assert(getprop("ro.product.device") == "i9305" || getprop("ro.build.product") == "i9305");) (i test now in terminal command: getprop ro.product.device and show me i9305 ..i dont now why i can't install zip package. but i solve this with removed line.
So, i install recovery (multirom recovery) and i install zip. I install your modded apk and i have error.
On recovery, i try to install a new rom, and was installed (but on internal_memory/multirom directory i dont see any folder/file..but my space on rom was used by "new rom")
I try to inject my kernel (pureSTOCK 5.9.2). Nothing happen when i reboot my phone. I think need to show a menu with "What rom do you want to boot"..but nothing.
I can help you with tests to dev this project.
Keep up
EDIT: And, i dont now how can install a theme for TWRP..because text buttons not aligned
Click to expand...
Click to collapse
Heh, the updater-script bug is well-known to me, i'll try to fix it in the upcoming updates. The manager app issue happens is because you are running a Note 4 ROM from this forum and that rom changes the ro.product.device if not mistaken. If I can make this work, which i will do, i will have a talk with the ROM developers to not alter the ro.product.device for the app to work. To install a TWRP theme you have the instructions along with the download here. Just make sure to download for 720p.
Alexander_the_B0ss said:
Heh, the updater-script bug is well-known to me, i'll try to fix it in the upcoming updates. The manager app issue happens is because you are running a Note 4 ROM from this forum and that rom changes the ro.product.device if not mistaken. If I can make this work, which i will do, i will have a talk with the ROM developers to not alter the ro.product.device for the app to work. To install a TWRP theme you have the instructions along with the download here. Just make sure to download for 720p.
Click to expand...
Click to collapse
Thanks for your "talk with ROM Developers". Hope kexec-hardpatch is enabled (if I am right) soon and we will have boot menu working
@Alexander_the_B0ss
Any update? I devices is see like: m3 not i9305
il3gal said:
@Alexander_the_B0ss
Any update? I devices is see like: m3 not i9305
Click to expand...
Click to collapse
The actual codename for i9305 is m3 or m3xx, i9305 is the 'commercial name'. About any updates: for now i have a dead hdd, so at least for a couple of weeks no updates. Sorry. And also I am sick and need to go to hospital.
Alexander_the_B0ss said:
The actual codename for i9305 is m3 or m3xx, i9305 is the 'commercial name'. About any updates: for now i have a dead hdd, so at least for a couple of weeks no updates. Sorry. And also I am sick and need to go to hospital.
Click to expand...
Click to collapse
Get well brother.
Get well soon friend
any news ?????
hi, does this work on the older i9300 model (3g)?
{
"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
MultiROM is one-of-a-kind multi-boot mod. 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 USB drive connected to the device via OTG cable. 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 left image below and in gallery. 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 USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!It _is_ dangerous. 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 and you will have to flash factory images again. Make backups. Always.InstallationManual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install + one optional (deprecated) :
MultiROM (multirom-YYYYMMDD-v33x-taoshan.zip) - download the ZIP file from second post and flash it in recovery.
Modified Recovery (multirom-YYYYMMDD-recovery-taoshan.zip) - download the ZIP file from second post and use a recovery to flash it into the FOTA partition (see TWRP 3 thread for more informations).
DEPRECATED: Patched kernel - You can use those kernels on most Marshmallow and Lollipop based primary ROMs to add kexec boot support.
Be aware that those patchers will be updated when possible after kernel sources updates
Kexec support no longer required thanks to the no-kexec workaround by nkk71.
For convenience reasons, I enabled the workaround by default if kexec is not found.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Recommended values are :
Cache : Keep default value
Data : Minimum 4000
System : 1000 is enough for most installs
Updating/changing ROMs1. 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.
OPTIONAL: Reflash the kernel patcher to add kexec support
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 menusMain menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- 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 this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source codeMultiROM - https://github.com/STRYDER-007/multirom_xperia (branch multirom-7.1)
Modified TWRP - https://github.com/nkk71/android_bootable_recovery/ (branch android-7.1-mrom)
Device Tree - https://github.com/STRYDER-007/multirom_device_sony_taoshan (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/STRYDER-007/android_kernel_sony_msm8930 (branch multirom)
MultiROM available for Taoshan also thanks to :- Tasssadar
- The XperiaMultiROM team
- The MultiROM HTC team
- @Olivier and @Adrian DC for lot of precious help and guidance in fixing many things
- @nkk71 for no-kexec workaround
- @Agent_fabulous for testing
- My Xperia L for surviving this!
XDA:DevDB Information
MultiROM for Xperia L, Tool/Utility for the Sony Xperia L
Contributors
STRYDER~007
Source Code: http://forum.xda-developers.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011
Version Information
Status: Stable
Created 2016-06-13
Last Updated 2016-09-24
Downloads
1. Main downloads
MultiROM: multirom-2017MMDD-v33x-taoshan.zip
Modified recovery (based on TWRP 3): multirom-2017MMDD-recovery-fota-taoshan.zip
OPTIONAL: Kernel w/ kexec-hardboot patch (msm8930 Marshmallow based):
multirom_kernel-2016MMDD-taoshan.zip
If used, kernel with kexec-hardboot patched needs to be only in your primary ROM!
* No longer required thanks to the no-kexec workaround.
2. Third-party kernels with kexec-hardboot patch
* None, No longer needed due to no-kexec implementation.
3. MultiROM Uninstaller
MultiROM uninstaller: multirom_uninstaller.zip
* Flash uninstaller zip from recovery to remove MultiROM completely. This will also remove all your secondary ROMs.How to install for the first time
Flash the 2 MultiROM zips as explained
Reboot to the FOTA Recovery (Volume +)
In MultiROM TWRP, Add a ROM, set everything properly
Wait for the ROM to be installed (can take a while)
In MultiROM screen, choose the ROM location
For the concerned ROM, "Flash zip" for wished zips (GApps, SuperSU, Addons...)
OPTIONAL: Read about the no-kexec workaround by nkk71
Reboot the phone and Enjoy MultiROM!
Changelogs
Code:
=========================================
MultiROM v33x - TWRP 3.1.1 - 02/10/2017
=========================================
* Fixed incorrect mounting of partitions in TWRP
* Removed unused and deprecated flags in TWRP
* Fixed MultiROM TWRP versioning
=========================================
MultiROM v33x - TWRP 3.1.1 - 24/09/2017
=========================================
* [B]Fixed touchscreen issue in MultiROM UI[/B]
* cyttsp3: Update multi-touch protocol for display driver
* defconfig: Compress kernel with XZ (Smaller TWRP Size)
* MultiROM UI dimensions completely fixed
* Access to MultiROM color themes and Shutdown
* Include all recent improvements from TWRP 3.1.1
* Updated to no-kexec workaround v4.1 by nkk71
* Autoboot accessible for external / MicroSD
* Improved versioning with header showing build date
* Built in a clean new tree of Android 7.1.2 (replaces 6.0)
* Multiple fixes to support 7.1 changes
* Fix the 7.1 busybox cpio corruption, needed for MultiROM
=========================================
MultiROM v33x - TWRP 3.1.0 - 15/06/2016
=========================================
* Fixed MultiROM logo in UI
* Some Minor changes in the UI
=========================================
MultiROM v33x - TWRP 3.0.2 - 13/06/2016
=========================================
* Initial public release
FAQ and other notes
FAQ and other notesAbout security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive./external SD card. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside?
Yes.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
The installation fails with "trampoline not found -1"
Often the issue appears because the ROM zip has a nested zip for rooting methods. Best solution is to remove the root zip from the ROM and flash it separately later.
Something wrong happened, I lost something or it's really laggy
You have been warned about making backups & the fact this is more experimental than stable.
You alone will be responsible for loosing data or having an usable ROM when you really needed it.
Everyone in this thread will try to help you, but we can't do backups of your data ourselves.
Thanks for your understanding, remember to read the previous comments and please try to help each other.Current local manifest of the MultiROM build
Code:
<!-- https://github.com/STRYDER-007/multirom_device_sony_taoshan -->
Awesome work bro,thanks!!!
You are the best
Honestly, I never imagined that I'll be able to see multiRom on Xperia L
Thanks Dev. :laugh:
Awesome dev!
Will test it as soon as possible!
Thanks!
Awesome! Will test it for sure
WTF (What The Fantastic)
You're the best I'll try it ASAP
Just wanna make things clear
1. Can I install it without reflashing the current ROM?
2. Installing Rom to external SD Card Won't format and delete all the data?
So it doesn't mess with memory partition??
That means there's no hardbrick just (maybe) softbrick.
Again thank you very much. For your hard work
Mouaz Kaadan said:
Just wanna make things clear
1. Can I install it without reflashing the current ROM?
2. Installing Rom to external SD Card Won't format and delete all the data?
Click to expand...
Click to collapse
1. Yes
2. Yes. You can keep your data along with ROM installation on ext sd.
n78 shadow said:
So it doesn't mess with memory partition??
That means there's no hardbrick just (maybe) softbrick.
Again thank you very much. For your hard work
Click to expand...
Click to collapse
No chances of bricking at all if you follow instruction and flash it correctly.
Wow. Extremely awesome, thanks for making this for Xperia L!
Just two questions: Does this work by "unpacking" the rom on external memory and booting as if it was internal? Also, how do we get Ubuntu (or any other Linux distro) to run on our device? (are there flashable zips for that?)
Sent from my taoshan using XDA Labs
Aenadon said:
Wow. Extremely awesome, thanks for making this for Xperia L!
Just two questions: Does this work by "unpacking" the rom on external memory and booting as if it was internal? Also, how do we get Ubuntu (or any other Linux distro) to run on our device? (are there flashable zips for that?)
Sent from my taoshan using XDA Labs
Click to expand...
Click to collapse
1. Yep.
2. There is no Ubuntu OS ported for Xperia L.
Thanks for this awesome Multirom. I have question. Can i install both stock rom and custom rom as a dual boot.?
kumardeepu said:
Thanks for this awesome Multirom. I have question. Can i install both stock rom and custom rom as a dual boot.?
Click to expand...
Click to collapse
Please go through entire thread. Everything is written there.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive./external SD card. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside?
Yes.
Click to expand...
Click to collapse
STRYDER~007 said:
Please go through entire thread. Everything is written there.
Click to expand...
Click to collapse
First Stockrom through flashtool>then multirom zip>modified recovery> custom rom am i right?
kumardeepu said:
First Stockrom through flashtool>then multirom zip>modified recovery> custom rom am i right?
Click to expand...
Click to collapse
Yes.
Well actually in detail, First stock rom via flashtool->Root->Install SuperSU->Install Recovery via Recovery Installer app->Flash MultiROM Recovery zip->Reboot to MultiROM recovery->Flash MultiROM zip->Add Custom ROM!
MultiROM Updated
MultiROM updated with minor UI changes. Check OP.
Changelogs-
Code:
** 15-06-2016
- Fixed MultiROM logo in UI
- Some Minor changes in the UI
It fails when i try to flash the multirom zip
Why??
Sorry for my bad English
ShadowA9 said:
It fails when i try to flash the multirom zip
Why??
Sorry for my bad English
Click to expand...
Click to collapse
Flash MultiROM recovery zip first then boot into new recovery and flash multirom zip.
{
"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"
}
Note - Iam Not Responsible for bricked devices & twrp image based on prebuilt stock kernel.
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
1. Download twrp tar file
2. Boot in to download mode
3. Open Odin
4. Select Ap
5. Select twrp.tar file
6. Click on flash
7. Immediately press volume up and power button to boot in to twrp other wise it boots in to system or whenever you wanted to boot in to twrp just switch off and just press volume up and power button that's it
bugs
- internal storage shows nothing
Main features
- Super partition support ( with read write support )
Special Credits
- TWRP team for source code
- Omni team for base sources
- Samsung for prebuilt kernel
- Google source for tools
Download Twrp-3.4.0-0 From Here
XDA:DevDB Information
TWRP 3.4.0-0 , for Samsung M12
Contributors
Raghu varma
Source Code: https://github.com/RaghuVarma331/android_device_samsung_m12-TWRP.git
prebuilt kernel: https://opensource.samsung.com/uploadSearch?searchValue=M127F
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Stable Version: 3.x
Stable Release Date 2021-05-07
Created 2021-05-07
Last Updated 2021-05-07
Is there any custom rom build yet?
yashchaudhari954 said:
Is there any custom rom build yet?
Click to expand...
Click to collapse
Custom rom, haha. Is there any working root yet?
Root: https://forum.xda-developers.com/t/root-modified-magisk-for-galaxy-a21s-r.4271537/
this twrp support SM-M127F?
ankush1492 said:
Root: https://forum.xda-developers.com/t/root-modified-magisk-for-galaxy-a21s-r.4271537/
Click to expand...
Click to collapse
It was wonderful what I found on this link. Now I'm just looking to see if it works on galaxy sm-m127f , with zto rom .thanks
Guys, does this work for f12 becoz both m12 adn f12 are the same
TeckySairam said:
Guys, does this work for f12 becoz both m12 adn f12 are the same
Click to expand...
Click to collapse
twrp doesn't work on m12 and I don't know if it works on f12
Custom Kernel here
Kernel and TWRP for a127f u2 (Exynos 850)
I have built a custom kernel for the a127f Exynos 850 I've also included a link to more custom recoveries in post#2 physwizz a12s kernel version 4 Based on a127f NOT for baseband u3 or higher For OneUI 3.1 ( also works for GSIs) Samsung...
forum.xda-developers.com
will this work on sm-m127f?
Twrp works on my SM-127f. Just need to see that Data partition now.
Got twrp just to make a Nandroid backup. Seems like the internal storage issue is not yet resolved
hxudsh said:
will this work on sm-m127f?
Click to expand...
Click to collapse
Yes. Just tried on my own. Data partition is unavailable and touch input glitches out sometimes after the screen times out. Just turn screen timeout off and you'll be fine.
To the dev: thanks for all the hard work
RogueHacker said:
Yes. Just tried on my own. Data partition is unavailable and touch input glitches out sometimes after the screen times out. Just turn screen timeout off and you'll be fine.
To the dev: thanks for all the hard work
Click to expand...
Click to collapse
Reboot to recovery.
Mount system (Press mount then choose system)
Tap on Wipe, tap on format data, type YES. (Not just wipe data)
install multidisabler
Reboot to recovery (tap on reboot, tap on recovery)
Install multidisabler\Reboot to recovery (tap on reboot, tap on recovery)
Reboot and go completely through the setup process. Wait for downloading to finish. This may take up to an hour. You can see the progress by pulling down from the top.
TeckySairam said:
Guys, does this work for f12 becoz both m12 adn f12 are the same
Click to expand...
Click to collapse
Does twrp work on f12?
its for indian version?
asskriss said:
this twrp support SM-M127F?
Click to expand...
Click to collapse
Yeah
ssaenz said:
its for indian version?
Click to expand...
Click to collapse
Yes
physwizz said:
Reboot to recovery.
Mount system (Press mount then choose system)
Tap on Wipe, tap on format data, type YES. (Not just wipe data)
install multidisabler
Reboot to recovery (tap on reboot, tap on recovery)
Install multidisabler\Reboot to recovery (tap on reboot, tap on recovery)
Reboot and go completely through the setup process. Wait for downloading to finish. This may take up to an hour. You can see the progress by pulling down from the top.
Click to expand...
Click to collapse
Would this work with sd card without detecting in twrp?
Pudleeysx said:
Would this work with sd card without detecting in twrp?
Click to expand...
Click to collapse
Yep
Raghu varma said:
View attachment 5302075
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
1. Download twrp tar file
2. Boot in to download mode
3. Open Odin
4. Select Ap
5. Select twrp.tar file
6. Click on flash
7. Immediately press volume up and power button to boot in to twrp other wise it boots in to system or whenever you wanted to boot in to twrp just switch off and just press volume up and power button that's it
bugs
- internal storage shows nothing
Main features
- Super partition support ( with read write support )
Special Credits
- TWRP team for source code
- Omni team for base sources
- Samsung for prebuilt kernel
- Google source for tools
Download Twrp-3.4.0-0 From Here
XDA:DevDB Information
TWRP 3.4.0-0 , for Samsung M12
Contributors
Raghu varma
Source Code: https://github.com/RaghuVarma331/android_device_samsung_m12-TWRP.git
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Stable Version: 3.x
Stable Release Date 2021-05-07
Created 2021-05-07
Last Updated 2021-05-07
Click to expand...
Click to collapse
SD card is Detecting Only 13MB wile my SD card is 8GB
Raghu varma said:
View attachment 5302075
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
1. Download twrp tar file
2. Boot in to download mode
3. Open Odin
4. Select Ap
5. Select twrp.tar file
6. Click on flash
7. Immediately press volume up and power button to boot in to twrp other wise it boots in to system or whenever you wanted to boot in to twrp just switch off and just press volume up and power button that's it
bugs
- internal storage shows nothing
Main features
- Super partition support ( with read write support )
Special Credits
- TWRP team for source code
- Omni team for base sources
- Samsung for prebuilt kernel
- Google source for tools
Download Twrp-3.4.0-0 From Here
XDA:DevDB Information
TWRP 3.4.0-0 , for Samsung M12
Contributors
Raghu varma
Source Code: https://github.com/RaghuVarma331/android_device_samsung_m12-TWRP.git
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Stable Version: 3.x
Stable Release Date 2021-05-07
Created 2021-05-07
Last Updated 2021-05-07
Click to expand...
Click to collapse
while I format Date data and Factory reset device using TWRP, the TWRP is messing something Up So I dont recommend Any one to use this TWRP recovery... as the sd card is not getting detected and while I format the device my device gets bricked. We Need More Improvement in This Recovery to work !!