-- Team Win Recovery Project --
{
"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"
}
Supported model ONLY ks01lte
I'm sorry but my i9506 is definitely dead, who wants to use my source code to create new updates this is the guide:
(links below)
device > use branch cm-14.1_twrp
kernel > use branch cm-14.1-rc
android_bootable_recovery repo > rebase with official omni repo or cherry-pick my last two commit on top
Team Win Recovery Project 3.x, or twrp 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.
I built this recovery by using my cleaned source code for kernel and OmniRom for twrp.
If you find any bug or problem please reply below this thread or use the dedicated tab page "Bug Reports" over here.
Phone look:
Features:
MTP auto mounting for SD / External SD
Mass storage mounting for External SD
Usb OTG
Full SELinux support
Supported F2FS (system, data, cache partitions)
CPU temperature handled
Thermal control and Performance profiles are active by default
Backup/Restore tested with 4.4.2/5.1 TW original samsung rom and all CyanogenMod
Screen shot capture enabled (Volume (-) + Power) (saved in the "Picture" folder)
Charge-Led
Known problems:
-Samsung HW encryption does not work well, follow this steps to decrypt /data: (thanks Diapolo)
1 - In the initial dialog "Enter Password." press Cancel
2 - "Swipe to Allow Modifications"
3 - Go to "Mount" and select "System" partition
4 - Press "Decrypt Data" and on "Enter Password." dialog press Accept
Changelog:
This is the changelog of my TWRP versions releases, if you want read the original changelog of TWRP versions go to:
http://teamw.in/project/twrp2
CHANGELOG for 3.1.0-0 [04/04/2017]:
-Updated kernel
CHANGELOG for 3.0.3-0 [18/12/2016]:
-Updated kernel
-Fixed twrp screen off timeout problem
CHANGELOG for 3.0.2-0 [20/11/2016]:
-Switched to TWRP android-7.1 branch
-Builded with a new stable kernel for Nougat and CM-14.1
-Added /misc partition on fstab for the recovery commands (Nougat changes)
-Tried to add Samsung HW encryption, it does not seem to work well i think it's incomplete, in our stock rom missing some file
such as keystore.xx.so and firmware files such as keymaster.xxx
CHANGELOG for 3.0.2-0 [08/05/2016]:
-Fixed chargeled service
-Fixed SEANDROIDENFORCE warning at boot, again
-Some changes in the partitions parameters on fstab
CHANGELOG for 3.0.2-0 [07/05/2016]:
-Switched to TWRP android-6.0 branch
-Builded from cm-13.0 repo
-New kernel made by me with latest LP sources
CHANGELOG for 2.8.7.0 [01/08/2015]:
-Switched to TWRP android-5.1 branch
-Builded from cm-12.1 repo
-Updated kernel from cyanogenmod
-Fixed brightness slider
-Fixed SEANDROIDENFORCE warning at boot
CHANGELOG for 2.8.5.0 [15/02/2015]:
-Fixed problem when wiping Data partition in F2FS
CHANGELOG for 2.8.4.0 [07/02/2015]:
-Added rewrite of TWRP settings after a SD wipe (prevent lost settings)
-Fixed mount F2FS or others filesystems to system, data, cache partitions
-Updated with latest changes from source
CHANGELOG for 2.8.4.0 [24/01/2015]:
-Switched to TWRP android-5.0 branch
-Brightness slider still does not work (it's a kernel related problem)
CHANGELOG for 2.8.1.0 [24/01/2015]:
-Updated kernel from cyanogenmod
-Screen blink on boot is not longer present
-Brightness slider no longer work (it's a kernel related problem)
-Added chargeled - adapted for samsung devices
CHANGELOG for 2.8.1.0 [27/11/2014]:
-Enabled mass storage mounting for external sd
-Fixed MTP mounting without external sd
CHANGELOG for 2.8.1.0:
-Initial TWRP release for I9506 (ks01lte)
How to do for install it:
FIRST INSTALL FROM ODIN (v3.07 or higher):
-Download twrp .TAR.MD5 file.
-Go to download mode (Volume down + Home + Power)
-Open Odin and check AutoReboot and F.Reset Time checkboxes are selected, also Re-Partition it NOT selected.
-Click on AP (PDA) and select the downloaded twrp recovery tar.md5 file.
-Check if all options are corrects, and press Start.
-Once the installation process complete, your phone will restart and soon you will see a PASS message with green background in the left-most box at the very top of the Odin. You can now unplug the USB cable to disconnect it from the computer.
-Some users has found problems with previous procedure: in this unlucky situation, when phone reboot and the logo (i9506 Samsung S4 Galaxy) appear, pull out the battery. Don't panic, the logo is there for several seconds. The installation process should be finalized now. There will be no PASS status in Odin. Put back the battery in the phone and try to boot straight to recovery.
UPGRADE YOUR TWRP:
-Download twrp .ZIP file.
-Copy the recovery zip file in the internal SD or external SD.
-Go to recovery mode (Volume up + Home + Power)
-Touch the INSTALL button.
-Select the appropriate SD
-Select the twrp file copied previously and slide to flash.
-Press back some times and reboot.
DOWNLOAD:
You can dowload the current version from this folder, you will find the flashable zip and tar version.
CLICK HERE TO GET DOWNLOAD FOLDER
To download Odin go here: samsungodin.com
SOURCES:
TWRP Source: https://github.com/omnirom/android_bootable_recovery
Kernel Source: https://github.com/CastagnaIT/android_kernel_samsung_ks01lte
Device Source: https://github.com/CastagnaIT/android_device_samsung_ks01lte
Thanks to: CyanogenMod, OmniRom Team, TWRP Team, Dees_Troy, Solk2, DualJoe
XDA:DevDB Information
TWRP, Tool/Utility for the Samsung Galaxy S4
Contributors
CastagnaIT, smeroni68
Version Information
Status: Stable
Current Stable Version: v3.1.0-0
Stable Release Date: 2017-04-04
Created 2014-11-16
Last Updated 2017-07-15
Thank you! It works great!
Sent from my Galaxy S4 LTE-A [GT-I9506] using Settings app
I've trayed stock recovery version. It doesn't work, there is something wrong with "footer"?
Signature verification failed.
I have the latest stock NEE firmware.
Wysłane z mojego GT-I9506
checking in the next days, probably the stock recovery isn't compatible with the classic signature, for now use odin
Your current filename TWRP_2.8.1.0_ks01lte_20141115.tar.md5 won't get accepted by Odin 3.09. It should be TWRP_2.8.1.0_ks01lte.tar.md5 as generated by md5sum (that includes/binds filename as well). Or just omit md5sum step completely. Its not mandatory.
Edit: Looks like forum database has been set back (and so is your 1st post). One fellow guy is missing again.
working perfectly for me thanks
Sent from my GT-I9506 using XDA Free mobile app
Fixed files updated from CIT... md5 corrected...
When I'm trying to root my I9506 it tells me it failed to verify footer. I have tried keymaster, PhilZ touch and ROOT_E330S_I9506_v2 - it won't root the phone. And since this goes on, I cannot use Odin to flash neither TWRP or CWM (specified for I9506). I really hope for some help for this, as it bugs me really hard.
nydxlil said:
When I'm trying to root my I9506 it tells me it failed to verify footer. I have tried keymaster, PhilZ touch and ROOT_E330S_I9506_v2 - it won't root the phone. And since this goes on, I cannot use Odin to flash neither TWRP or CWM (specified for I9506). I really hope for some help for this, as it bugs me really hard.
Click to expand...
Click to collapse
Du får ikke root ved at flashe recovery... Du skal flashe en version (som svarer til din firmware version) af AutoRoot fra denne tråd http://forum.xda-developers.com/showthread.php?t=2597058
morten82 said:
Du får ikke root ved at flashe recovery... Du skal flashe en version (som svarer til din firmware version) af AutoRoot fra denne tråd http://forum.xda-developers.com/showthread.php?t=2597058
Click to expand...
Click to collapse
Så har jeg åbenbart fuldstændig misforstået de guides der er. Alle de forskellige roots jeg har fundet har ikke været signed så dem har jeg ikke kunne bruge Jeg prøver en af de pre-rooted rom'er og ser om de ikke kan "do the magic" senere i dag, BBL med svar. På forhånd tak
ENGLISH PLEASE!! XDA Rules!! Thanks
Kernel seandroid enforcing?
Hi. I have flasch tvrp recovery and it works perfect.
Only thing is this message on boot screen KERNEL IS SEANDROID ENFORCING
NO WARANTY BIT.
what its this?
Thanks for answers.
Sorry for my bad English
Rado G said:
Hi. I have flasch tvrp recovery and it works perfect.
Only thing is this message on boot screen KERNEL IS SEANDROID ENFORCING
NO WARANTY BIT.
what its this?
Thanks for answers.
Sorry for my bad English
Click to expand...
Click to collapse
Not stock recovery give knox 0x1 broken... the message is reporting this... it is irreversibile... That's the rule...
Inviato dal mio GT-I9505 utilizzando Tapatalk
--new updates--
Only a quick update, the most important i fixed the MTP mount for internal storage when external SD isn't present, that before seemed not work properly.
All the changelog below.
CHANGELOG for 2.8.1.0 [27/11/2014]:
-Enabled mass storage mounting for external sd (CastagnaIT)
-Fixed MTP mounting without external sd (CastagnaIT)
-Various other bugfixes and tweaks by twrp team
Click to expand...
Click to collapse
Bye
CastagnaIT
Thanks for the update.
So far, working fine here.
CastagnaIT said:
Only a quick update, the most important i fixed the MTP mount for internal storage when external SD isn't present, that before seemed not work properly.
All the changelog below.
Bye
CastagnaIT
Click to expand...
Click to collapse
Thank you for the update! [emoji106]
WOW
Super! Works pretty good on I9506 with rooted Stock Rom 4.4.2 NNE ! Big thanks from Germany!:good:
Hey,
Recently bought Galaxy S4 4g+ (i9506) and now trying to flash the latest TWRP (TWRP_2.8.1.0_ks01lte_20141127.tar.md5) with Odin 3.07, but it doesn't seem to work? Odin completes the flash just fine and gives the green "PASS" just fine but when I boot into recovery it's just the default one. Also Knox Warranty flag isn't triggered. What should I do to be able to flash TWRP (or any custom recovery)?
Thanks.
---------- Post added at 06:56 PM ---------- Previous post was at 06:02 PM ----------
enkku said:
Hey,
Recently bought Galaxy S4 4g+ (i9506) and now trying to flash the latest TWRP (TWRP_2.8.1.0_ks01lte_20141127.tar.md5) with Odin 3.07, but it doesn't seem to work? Odin completes the flash just fine and gives the green "PASS" just fine but when I boot into recovery it's just the default one. Also Knox Warranty flag isn't triggered. What should I do to be able to flash TWRP (or any custom recovery)?
Thanks.
Click to expand...
Click to collapse
Nevermind, battery pull trick did it and got it installed now (removed battery on Galaxy S4 logo after it auto reboots after flashing TWRP with Odin).
When trying to flash ROM (CM12 2.4.1 I9506) it seems like it can't install/mount/unmount the /data, which results in the the recovery prompts that OS is not installed.
I've tried both TWRP and PhilZ (in PhilZ i get error: "unmount of /data failed; no such volume").
I'm desperate for a solution! Thanks in advance!
Thanks for this versions. I can instal cm12 lollipop with. Thanks
Related
{
"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"
}
MultiROM is a 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.
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Many Stock-based ROMs will fail to install because their boot.imgs cannot be unpacked using normal tools or use unsupported compressions. Please contact me in that case, but do note I can't add support for each Stock-based ROM out here.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to "Advanced -> MultiROM" to flash ROMs/kernels or other mods.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
Don't try to flash ROMs with Stock boot.imgs (supported by LBs). They need special unpacking tools and are therefore currently not supported. I haven't yet tried flashing other Stock ROMs. -- If you are on a stock-based ROM .230, flash this kernel.
This is still a work in progress. Only ROMs like as Omni, CM11 or Carbon have been confirmed working as of yet. Don't ask for ETAs please.
Your device must not be encrypted.
To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Make sure you are on OmniROM OR on any ROM based on 10.5.A.0.230/233 (or any other ROM compatible with these kernels)
Flash a supported kernel
Reboot into MultiROM TWRP and flash the MultiROM installer
That's it. You can now go to "Advanced -> MultiROM" to start flashing other ROMs.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. 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 USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
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.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/tree/master (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/olivieer/android_kernel_sony_apq8064 (HodorKernel | branch 10.5.A.0.xxx) and https://github.com/omnirom/android_kernel_sony_apq8064 (branch android-4.4)
FAQs can be found here.
CREDITs
Tasssadar
domicq
omnirom
Everyone else mentioned here.
XDA:DevDB Information
MultiROM for Sony Xperia Z, Tool/Utility for the Sony Xperia Z
Contributors
Olivier
Source Code: https://github.com/XperiaMultiROM/multirom/tree/master
Version Information
Status: Stable
Current Stable Version: v31x
Stable Release Date: 2015-11-12
Created 2014-08-10
Last Updated 2015-11-12
Changelog
DOWNLOAD
You can always get the latest releases from my build server or using the MultiROM Manager.
CHANGELOG
Code:
[b]12/11/2015:[/b] Updated MultiROM to v32x and MultiROM TWRP to 2.8.7 (incl. upstream <-> TWRP 2.8.7.0)
[b]13/02/2015:[/b] Updated to v31x | Updated adb | Print error when multirom crashes | Added support for multiple entries per path in fstab | Set is_second_boot also if mrom_kexecd=1 is present in /proc/cmdline | Support interlaced PNGs | Updated to MultiROM TWRP 2.8.5 (incl. upstream <-> TWRP 2.8.5.0)
[b]29/01/2015:[/b] Improved compability with some ROMs
[b]17/01/2015:[/b] Updated to MultiROM TWRP 2.8.4 (incl. upstream <-> TWRP 2.8.4.0), fixed "Swap ROMs" feature
[b]08/01/2015:[/b] Inserted dummy line instead of removing to prevent breaking IFs (fixes the installation of AOSPA 5.0)
[b]04/01/2015:[/b] Updated to MultiROM TWRP 2.8.3 (incl. upstream <-> TWRP 2.8.3.0)
[b]08/12/2014:[/b] Fixed the installation of L-based ROMs as secondary ROMs
[b]04/12/2014:[/b] TWRP upstream
[b]21/11/2014:[/b] Moar TWRP upstream, updated to MultiROM v30x, fixed klog saving and text size on emergency reboot screen
[B]01/11/2014:[/B] Updated to MultiROM TWRP 2.8.1 (incl. upstream <-> TWRP 2.8.1.0) | Fixed perms of extract_elf_ramdisk
[B]23/10/2014:[/B] Upstream: Updated to v29x | Added "DirtyUnicorns icon" | Added device hook to allow incomplete fstab file | Bind mount /realdata to /data for rom quirks to work properly
[B]02/10/2014:[/B] Added support for external sdcard
[B]27/09/2014[/B]: Fixes for recovery, updated to MultiROM v28x (device-specific version), added kernel for [B]10.5.A.0.283[/B]-based ROMs
[B]14/09/2014:[/B] Added [I]new[/I] kernel for CM11 (new blobs/kernel)
[B]03/09/2014:[/B] Added kernel for CM11 (old blobs/kernel)
[B]31/08/2014:[/B]: Updated to v28 | fixed MultiROM loading twice | automatically replace recovery ramdisk
[B]11/08/2014:[/B] Added another kexec-hardboot-patched kernel based on [B]10.5.A.0.230[/B] ([URL="http://forum.xda-developers.com/devdb/project/dl/?id=7909"]boot_230.img[/URL]) and a [URL="http://forum.xda-developers.com/devdb/project/dl/?id=7908"]flashable multirom uninstaller[/URL] - [COLOR="Lime"]Stock-based ROMs now supported![/COLOR]
[B]10/08/2014:[/B] Initial public release.
Currently supported kernels
SUPPORTED KERNELs/ROMs
HodorKernel (4.4.4 Stock)
Lightning Kernel (CM11 | 4.4 Stock)
KMA Kernel (CM11)
OmniROM 4.4.4 (supported by default)
ParanoidAndroid 4+ (supported by default)
ParanoidAndroid 5+ (supported by default)
SlimKat (supported by default)
SlimLP (supported by default)
Validus ROM (supported by default)
Zombie Kernel (4.3 Stock | 4.4.4 Stock )
EDIT: Almost every kernel support kexec-hardboot now, I've hence stopped updating this list.
Looks very good, thanks for your work
Gesendet von meinem Nexus 5
Bro can I add the kexec hardboot patch to my lightning kernel based on cm source thanks
i flashed boot.img but i dont have the modified twrp recovery i still have my old recovery ( Philz Touch ) anyway to manually flash recovery only?
nikhil18 said:
Bro can I add the kexec hardboot patch to my lightning kernel based on cm source thanks
Click to expand...
Click to collapse
Of course.
Akil97 said:
i flashed boot.img but i dont have the modified twrp recovery i still have my old recovery ( Philz Touch ) anyway to manually flash recovery only?
Click to expand...
Click to collapse
Your kernel also needs to be kexec-hardboot-patched so you have to flash the one from the OP.
Gesendet von meinem Xperia Z mit Tapatalk
Olivier said:
Of course.
Your kernel also needs to be kexec-hardboot-patched so you have to flash the one from the OP.
Gesendet von meinem Xperia Z mit Tapatalk
Click to expand...
Click to collapse
Actually i flashed your modified OmniROM kernel with kexec support but i did'nt get the recovery tried flashing it two times
Did you do it via fastboot like op stated?
I frankly don't know what you're doing wrong. To get sure I didn't upload a wrong file, I re-downloaded and tested it and... it does work.
I have carbon band first boot crash... I flash omni band again
After installing MultiROM can we change the primary ROM to anyother ROM or it has to be OMNI based?
Oliviers modified recovery will not boot if you have other recovery installed in FOTA. You need to wipe it first.
zakitheracer said:
After installing MultiROM can we change the primary ROM to anyother ROM or it has to be OMNI based?
Click to expand...
Click to collapse
As of now, you have to flash my kernel (intended for OmniROM), hence your Internal ("primary") ROM has to be compatible with it.
macia10 said:
Oliviers modified recovery will not boot if you have other recovery installed in FOTA. You need to wipe it first.
Click to expand...
Click to collapse
I'd recommend keeping MultiROM TWRP recovery in the FOTA partition by the way.
Olivier said:
I'd recommend keeping MultiROM TWRP recovery in the FOTA partition by the way.
Click to expand...
Click to collapse
But its not installed to FOTA by default so it would be good to add an instruction on how to install it to FOTA
So it is possible in future for the boot.IMG to be compatible with CM11?
Sent from my Xperia Z using Tapatalk
Quick tips : If you're using stock ROM right now you should wait for a specific kernel to be released first to use with this multiboot.
please do correct me if I'm mistaken.
Sent from my C6603 using Tapatalk 2
A new build is up as well as a patched boot.img for all ROMs based on 10.5.A.0.230/233. I have updated the OP and the Changelog.
Good idea would be FOTA multiTWRP with ability to inject kexec support to any installed kernel.
The Boot img for .230 ROMs is softbrocking my phone for some reason
Flashing it on eXistenz
Team Win Recovery Project 3.0.2-1
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S6 edge (6.0+) stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash no-verity-opt-encrypt.zip.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys6edge.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR ROOTING YOUR DEVICE
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"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"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for your device variant.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] + [Power] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
Hold [Volume Up] + [Home] + [Power] buttons near the end of the flash, and keep holding them until you are in recovery.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 12 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
Only if you want your internal storage or data partition to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you only want a bootable system partition or readable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
** If your internal storage is encrypted, you will need to use adb sideload instead.
Go to [Reboot] -> [System].
Wait up to 5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 (twrp.me) - same as v3.0.2-1
v3.0.2-1 - New device tree and kernel, support added for Marshmallow, f2fs, and MTP.
v3.0.2-0 - See here for the changes.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_samsung_zerolte (android-6.0)
Kernel: https://github.com/jcadduono/nethunter_kernel_noblelte (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S6 edge, Tool/Utility for the Samsung Galaxy S6 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/jcadduono/android_device_samsung_zerolte
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-05-27
Created 2016-04-08
Last Updated 2016-10-02
Builds are coming soon, just putting a thread up for a reference on the device page!
jcadduono said:
Builds are coming soon, just putting a thread up for a reference on the device page!
Click to expand...
Click to collapse
Sweet, stick a mention that G925W8 users flash T-Mobile variant plz. [emoji6] thanks for this! Now my friends can read.
Sent from my SM-G925W8 using XDA-Developers mobile app
christopherrrg said:
Sweet, stick a mention that G925W8 users flash T-Mobile variant plz. [emoji6] thanks for this! Now my friends can read.
Sent from my SM-G925W8 using XDA-Developers mobile app
Click to expand...
Click to collapse
there won't be a marshmallow G925W8 or G925T build until kernel sources are released. afaik neither of those devices have 6.0 officially yet.
they will still be using lollipop at 3.0.2-0 for now.
for others:
https://idlekernel.com/twrp/zerolte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
I have successfully flashed the latest twrp. Though I had issues with the older one in backup restore area. Does the new do up backup and restore without error?
Nothing for SM-G925I ? zeroltedv
Ognjen123 said:
Nothing for SM-G925I ? zeroltedv
Click to expand...
Click to collapse
Brother I am using g925i only. Go to arter97 kernel page and download the recovery which he has modded for both and F and I variants.
jcadduono said:
there won't be a marshmallow G925W8 or G925T build until kernel sources are released. afaik neither of those devices have 6.0 officially yet.
they will still be using lollipop at 3.0.2-0 for now.
for others:
https://idlekernel.com/twrp/zerolte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
Click to expand...
Click to collapse
G925W8 PC5 sources are up. Nothing for the 920W8 yet.
violin.siva said:
Brother I am using g925i only. Go to arter97 kernel page and download the recovery which he has modded for both and F and I variants.
Click to expand...
Click to collapse
Can you please pm the link ?
---------- Post added at 11:16 PM ---------- Previous post was at 11:06 PM ----------
Can the twrp-3.0.2-1-zerolte.tar.md5 be flashed on the g925i ?
Why aren't the link working?
G925f link?
Inviato dal mio SM-G925F utilizzando Tapatalk
Is the topic dead ? Anybody can tell me what recovery they are using on g925i 6.0.1 android ?
Ognjen123 said:
Is the topic dead ? Anybody can tell me what recovery they are using on g925i 6.0.1 android ?
Click to expand...
Click to collapse
Twrp 3.0.2 with arter97 kernel. Working flawlessly in my g925i.
This is making me crazy , is there any suport here ? Links not working , where from to dl the 3.0.2-1 ver for g925i ?
OEM Unlock ??
I can't find it in my Developper Menu. I have 6.0.1 !
Help please...
Anyone found a working link for the recovery file?
Questions about TWRP versions found over some threads
I would like to know some things. Firstly say there's still nothing when you open http://teamw.in/devices/samsunggalaxys6edge.html
so, i looked up the link you gave
https://idlekernel.com/twrp/zerolte
but if I don't remember wrong, zerolte is S6 flat.
Does that kernel work anyway?
If that's so, does that mean official http://teamw.in/devices/samsunggalaxys6.html or TWRP S6 Edge Europe Version would also work?
Why wouldn't they?
Also, what's the difference with the twrp from @arter97 found Here
with yours?
Thanks!!
I hope someone could shed some light over those questions.
Sorry for my bad english!
Nobody is answering from them here , 0 suport . Kernel from arter97 and twrp recovery from him work fine .
Ognjen123 said:
Nobody is answering from them here , 0 suport . Kernel from arter97 and twrp recovery from him work fine .
Click to expand...
Click to collapse
See my above post.
Alright, this is what I did for my S6 Edge 925F which works fine so I thought I would share it with you guys:
I flashed the latest TWRP using ODIN from this link:
http://www.arter97.com/browse/S6/ke...r97-recovery-g925fi-13.1-twrp_3.0.2-0.tar.md5
which is the same link given at the bottom of this post along with the instructions as well:
http://forum.xda-developers.com/showpost.php?p=60390986&postcount=5
After rebooting the phone (which looped a couple of times), I flashed the latest SuperSU 2.71 (Beta) from ChainFire in the newly flashed TWRP which is given here:
http://forum.xda-developers.com/showthread.php?t=1538053
And now I have TWRP with SuperSU. I need to mention that I rooted my phone with CF-Auto root previously so it was already rooted, but I just wanted to have custom recovery for flashing other .zip files.
I also tried the latest stable version of SuperSU first, but it had problems finding and installing binaries. But there are no problems with the latest Beta (2.71) so far.
{
"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.
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.
MultiROM has 2 parts you need to install + one optional (deprecated) :
MultiROM (multirom-YYYYMMDD-v33x-yuga.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (multirom-YYYYMMDD-recovery-yuga.zip) - download the ZIP file from second post and use a recovery to flash it into the FOTA partition
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 ROMs
1. 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
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. 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 USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Android to 4Gb image on a pretty fast USB drive takes about 20 minutes maximum.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
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.
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 menus
Main 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 code
MultiROM - https://github.com/XperiaMultiROM/multirom (branch master)
Modified TWRP- https://github.com/Tasssadar/Team-Win-Recovery-Project (branch android-6.0)
MultiROM available for Yuga also thanks to :
- Tasssadar
- The XperiaMultiROM team
- The MultiROM HTC team
- Arvind7352
- nkk71
- AdrianDC
XDA:DevDB Information
MultiROM for Xperia Z, Tool/Utility for the Sony Xperia Z
Contributors
@Chippa_a
Thread Source Code: http://forum.xda-developers.com/xperia-sp/orig-development/mod-multirom-xperia-sp-t3351032
Version Information
Status: Abandoned
Downloads
1. Main downloads
MultiROM: multirom-2016MMDD-v33x-yuga.zip
Modified recovery (based on TWRP 3): multirom-2016MMDD-recovery-fota-yuga.zip
2. Uninstaller
MultiROM uninstaller: Unavailable for Yuga due to the already considerable SONY ELF format port
Reflash a ROM or a boot.img without injection (or the v33x zip) to remove MultiROM bootimage from your device.
Then delete the "multirom..." folders from internal & external storages.
If you don't want MultiROM menus in recovery, re-flash a normal TWRP, but it is not needed,
those menus don't do anything if MultiROM is not installed.
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...)
Read about the no-kexec workaround by nkk71 here : http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
Reboot the phone
Changelog
Code:
MultiROM v33x - 03/08/2016
======================================
* Initial release with full SONY ELF port and dual ramdisk support
Recoveries :
Code:
03/08/2016
======================
* Initial Yuga release
Supported ROMs
Code:
[COLOR="Gray"][SIZE="2"]Actually should be OK on all available ROMs
But this is a confirmed list[/SIZE][/COLOR]
CyanogenMod 12.1 : OK (Primary & Second)
CyanogenMod 13.0 : OK (Primary & Second)
ResurrectionRemix-MM: OK (Primary & Second)
SONY Stock 5.1.1: OK (Primary & Second)
FAQ and other notes
About 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.
MultiROM recovery says it's 2.8.4. Why isn't it updated to 2.8.4.*highernumber*?
It is, it just shows wrong version.
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.
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.
awesome work bro! Can't wait to test. Ill report you very soon! :good:
Nice to see someone taking over. I'll close my thread.
Sent from my Sony Xperia Z3+ using XDA Labs
Can i use latest zombie kernel for primary rom ? Zombie kernel have kexec hardboot support ..
itsnie said:
Can i use latest zombie kernel for primary rom ? Zombie kernel have kexec hardboot support ..
Click to expand...
Click to collapse
Please read OP again. Especially about "no-kexec workaround".
i installed both zip file.but recovery hasnt multirom option in andvanced!!!
Thank you a lot, I'll try it later!
The basketbuild site isn't working,they are doing recovery,
Would you please upload the files to another server?
Sent from my C6603 using Tapatalk
Does anyone know if there is multirom development on the xperia z5 e6653? I got it working on and of, but there are more breakdowns than anything else. This results in having to frequently reinstall the original boot.img and restart from scratch. Any help is appreciated. Thx
Sent from my E6653 using XDA-Developers mobile app
i have installed in xperia z and flash cm13 in sd card.. on multirom i have seleceted CM13 but still booting in to primary
---------- Post added at 08:34 AM ---------- Previous post was at 07:44 AM ----------
multirom worked using ressurection remix and cm 14 thank u.....
I tried -
PureX Z Premium v3.0
X rom ( 5.1)
Xperia_Z_eXistenZ_Premium
ResurrectionRemix-N-v5.8.0
almost all stock based ,But non of them works and gives error during flashing..
Only
ResurrectionRemix-M-v5.7.4
Omni rom , are working fine ...
Any help how to use sony stock roms or others ?
Chippa_a said:
Why is my USB connection to computer not detected ?
Uncheck the "Enable ADB" option in MultiROM Settings.
Click to expand...
Click to collapse
Did not help... the setting is unchecked by default.
Charging on a Wallcharger works, pluging the phone to the computer doesn't show anywhing.
Falshing the Recovery only still worked fine, but after flashing the MultiROM zip the phone doesn't budge when connected to the Computer.
Syslog attached.
The MultiROM menu is not under Advanced such as v32 rather the icon upper right - pic 1.
RR N 7.1.1 as second Rom failed, ERROR 7 @ RR M 6.0.1 - pic 2.
My oldest backup Omnirom 4.4.4 as sec Rom was successfully - pic 3.
#Edit: Additional compatible secondary ROMs::
-XOSP M [6.0.1] [Unofficial] [Release 6] 6.3 [Revision 3] [2016/08/03]
-AOSP M [6.0.1] [FINAL] [OMS/Substratum] [Updated 31-10-2016]
The installation of Lineage 14.1 as sec also ends with Error 7.
Now the burning question arises: What is and why ERROR: 7?
MichaBit said:
The installation of Lineage 14.1 as sec also ends with Error 7.
Now the burning question arises: What is and why ERROR: 7?
Click to expand...
Click to collapse
You need newer twrp recovery for newer roms
langeveld024 said:
You need newer twrp recovery for newer roms
Click to expand...
Click to collapse
There was und is always the newest One installed. :angel:
MichaBit said:
There was und is always the newest One installed. :angel:
Click to expand...
Click to collapse
Alright but error 7 ALWAYS means wrong recovery
langeveld024 said:
Alright but error 7 ALWAYS means wrong recovery
Click to expand...
Click to collapse
Oh, Im currently desiring LEOs 3.1.1, so I will give Nailyk a drink.
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
{
"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"
}
What's new in 3.1.1-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Features:
MTP working > to be confirmed
ADB working > to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 vesrion .or above
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
[MOD EDIT] Link removed
If you already have custom twrrp recovery to a lower version put img file from link below on your external sdcard and flash with flashify ap from play store or directly from Twrp with Install Image and tap recovery
[MOD EDIT] Link removed
To Root:
Chainfire SUPERSU v2.82
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
or MAGISK 13.3 and magisk manager 5.1.1.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install root (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
XDA:DevDB Information
TWRP recovery for the Galaxy A5 2017 Exynos7880, Tool/Utility for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
vocoderism, ashyx
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-07-28
Created 2017-07-28
Last Updated 2017-07-28
Thanks !! ??
Works?
Inviato dal mio SM-A520F utilizzando Tapatalk
Thank you.
are u building any device trees for exynos7880 of lineage os
im oves786
j7 2016 tw developer
Oves786 said:
are u building any device trees for exynos7880 of lineage os
im oves786
j7 2016 tw developer
Click to expand...
Click to collapse
Not yet but device tree that I will use is for aosp like a5x6
Inviato dal mio SM-A520F utilizzando Tapatalk
vocoderism said:
Not yet but device tree that I will use is for aosp like a5x6
Inviato dal mio SM-A520F utilizzando Tapatalk
Click to expand...
Click to collapse
i hav j7 2016 im a tw developer
j7 2016 has exynos7870 and urs has exynos7880 and both processors are same just clock at 1.9 and different radio band rest all are of exynos7870
You have device tree?to port?You mean exynos7850?
Inviato dal mio SM-A520F utilizzando Tapatalk
Hi
installed your twrp by .img file coz I had already a previous version
seems all. ok
I'll try to flash a beta Custom ROM just. now through your TWPR
thanks
Thx.It can work on A520K
I installed TWRP but can't install viper4Android. Anyone else? Having issues?
Hi @vocoderism
Have you switched phone from A510 to A520 now?
Sent from my SM-A310F using Tapatalk
Sure development for a520 a510 broken
Sent from my Nexus 7 using Tapatalk
Is it possible to just boot and not flash the recovery?
Many thanks, works a treat. I finally have a TWRP backup.
Great job! everything is working like a miracle!
At first MTP & ADB didn't worked for me (Windblows 10 Creators update build ver. 10.0.15064), but after a lot of trials and errors I've finally managed to get It working.
Rockchip drivers Here
Thanks again.
vocoderism said:
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Features:
MTP working > to be confirmed
ADB working > to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 vesrion .or above
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
TWRP: twrp_3.1.1-0_sm-a520_odin
If you already have custom twrrp recovery to a lower version put img file from link below on your external sdcard and flash with flashify ap from play store or directly from Twrp with Install Image and tap recovery
twrp_3.1.1-0_sm-a520_img
To Root:
Chainfire SUPERSU v2.82
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
or MAGISK 13.3 and magisk manager 5.1.1.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install root (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
XDA:DevDB Information
TWRP recovery for the Galaxy A5 2017 Exynos7880, Tool/Utility for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
vocoderism, ashyx
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-07-28
Created 2017-07-28
Last Updated 2017-07-28
Click to expand...
Click to collapse
succsfully installed in my a520f/ds..but when creating a back up it says in the end "failed to mount /data (Invalid argument)"..how can i fix this...?i want to create back up before doing anything else...i also got 0md reading for my internal storage...
this what i dis on creating back up
* reboot to recovery mode
*it boots to twrp..and there is a question if i want to allow modification then swipe but i didnt i only checked read only
*then i go to backup then i start creating backup
after a while it almost done and then it says "failed to mount /data (Invalid argument)"...thats what it says...i dont created a back up..please help me
ryzel said:
succsfully installed in my a520f/ds..but when creating a back up it says in the end "failed to mount /data (Invalid argument)"..how can i fix this...?i want to create back up before doing anything else...i also got 0md reading for my internal storage...
this what i dis on creating back up
* reboot to recovery mode
*it boots to twrp..and there is a question if i want to allow modification then swipe but i didnt i only checked read only
*then i go to backup then i start creating backup
after a while it almost done and then it says "failed to mount /data (Invalid argument)"...thats what it says...i dont created a back up..please help me
Click to expand...
Click to collapse
You have to decrypt your device first. follow the procedure in this thread:
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622
tsarig said:
You have to decrypt your device first. follow the procedure in this thread:
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622
Click to expand...
Click to collapse
I'm having a similar issue. got up to:
Turn the phone off
Hold power + home button and volume up to enter the recovery .
Dont swipe to allow modifcations!! use read only!
Flash Supersu and after that reboot to android.
Also download the No-verity-no-encrypt Patch made by Ashyx and put it on your sdcard ( not internal )!!!
https://www.androidfilehost.com/?fid=24591000424951049
I'm guessing installing no-verify-no-encrypt patch is the decrypt? How do I install it (read only, allow modifications?). My phone is now rooted due to previous steps, but I still get the failed to mount message.
y2klol said:
I'm having a similar issue. got up to:
Turn the phone off
Hold power + home button and volume up to enter the recovery .
Dont swipe to allow modifcations!! use read only!
Flash Supersu and after that reboot to android.
Also download the No-verity-no-encrypt Patch made by Ashyx and put it on your sdcard ( not internal )!!!
https://www.androidfilehost.com/?fid=24591000424951049
I'm guessing installing no-verify-no-encrypt patch is the decrypt? How do I install it (read only, allow modifications?). My phone is now rooted due to previous steps, but I still get the failed to mount message.
Click to expand...
Click to collapse
WARNING: You must backup your data first. this procedure will wipe your data. (As instructed in the link I've attached, just read it and follow carefully).
Flash the dm-verity patch as any other zip.
After you flash the dm-verity patch you'll have to format your phone, otherwise, your phone will never get decrypted. to do so, in TWRP you must choose wipe>format data. then it asks you to type 'yes' for safety measures, just type yes and that's It.
{
"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"
}
Unofficial TWRP 3.4.0.0 For Galaxy note 7 FE (N935X)
Disclaimer:
I do not own this device, however i work on the S7/S7E and there was enough requests for a FE support. so here we are.
This TWRP has been tested on 2 devices so far, it fixes mounting issues, and is based on new device trees. This should pave the way for other S7 developers to join in and add support to the FE since its not that difficult.
My custom kernel (Cronos) and Floyd Q Rom will make it to this thread once they are validated more.
Thanks to @butchieboy and Đỗ Gia Huy for testing
Also moving forward with this thread, you take full responsibility of any modifications done towards your device.
Features: :
Code:
- built from latest Pie source
- built from android-9.0 recovery sources
- fully compatible with Android 8.*/9.0/10.0
- Full F2FS Support for data and cache
- Full support for FLoydQ ROM
- Built with Busybox and resetprop
Downloads:
N935X (N935F/FD/S/L/K) : Download
Instructions:
Odin
Download latest Odin zip from Here
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home + Volume down + Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in your hands, disconnect the usb cable and press simultaneously the Home + Volume down + power until the Download mode pop-up shows
Press volume DOWN (so the phone reboots) then quickly press Home + VolumeUp + Power until the TWRP screen shows up
If it didn`t worked, redo the steps from #1 being more careful. and faster
TWRP (If you have a previous twrp installed)
Download TWRP_*.img, push it into phone storage (or external sdcard if thats not avalible), choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods due to RMM Lock / KG State, make sure you check this thread
Rooting and Internal Storage:
Finally, if you want to be able to read/write to the internal storage, you must format it to clear encryption, take a backup of your stuff before hand.
Go to TWRP > Wipe > Format Data > Type YES.
your data is now usable. if you didnt flash noverity-opt-encrypt or MagiskRoot your data will be encrypted again.
If you want to root your device now, simply download the latest magisk and flash it in your new recovery.
Sources:
Device tee : Github
Kernel : Github
Credits:
TeamWin, corsicanu, morogoku, Shariq3422 and testers
XDA:DevDB Information
TWRP-3.4.0.0, Tool/Utility for the Samsung Galaxy Note FE
Contributors
ananjaser1211, morogoku, corsicanu, Shariq3422
Source Code: https://github.com/ananjaser1211/android_device_samsung_gracerlte
Version Information
Status: Testing
Current Stable Version: V1.0
Stable Release Date: 2020-06-23
Current Beta Version: V1.0
Beta Release Date: 2020-06-23
Created 2020-06-23
Last Updated 2020-06-25
Misc Links:
Telegram Support Group
[*]Telegram news Channel
Latest Magisk
FloydQ Oneui 2.0 Beta ROM + N7FE Kernel
F.A.Q
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Can,t find OEM Toggle, RMM Locked
A : Read this thread
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Make sure you have the latest samsung stock firmware installed (to be on latest bootloader and modem combo)
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: How to Use F2FS ?
A : This requires you to be on Floyd ROM and the latest FE CronosKernel build. otherwise you wont be able to boot. Follow these steps
1) Wipe > advanced wipe > Data > CHANGE > F2FS (Your entire internal storage will be wiped out!)
2) Reboot and you will have DATA as F2FS, the same can be done to CACHE as well. Do not do it to SYSTEM
P.S : Again, make sure BOTH your ROM and KERNEL support F2FS.
Please let me know what issues you find in this TWRP, i am aware it boots, backsup and flashes zips. but do let me know if USB / MTP works as expected or if it needs further work.
I will be working on adding FE Support to all my exynos8890 projects moving forward. hopefulyl putting some life in this forum
Yo ma...man
Well done bro!
USB OTG works. Got this error when formatting data. Restored backup that was generated, everything went fine booted up as normal.
Sent from my SM-N975U using Tapatalk
TWRP-3.4.0.0-gracerlte-20200625
TWRP-3.4.0.0-gracerlte-20200625
* Fix error in SAR disable script (Fixes installing android 9 roms while 10 is installed)
* include resetprop (required for SAR script)
* Add custom TWRP Ver Name
Download : Github
This should fix the error reported above, and fix installing Pie roms while having 10 installed.
Wow, you are all over the place my friend. Thank you..lol[emoji481]
Sent from my SM-N975U using Tapatalk
Error no longer present
Sent from my SM-N975U using Tapatalk
Getting error again when trying to create backup or flash anything
Sent from my SM-N975U using Tapatalk
butchieboy said:
Getting error again when trying to create backup or flash anythingView attachment 5048397
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
Could you try to flash a pie rom while having my Q rom installed ?
the script is there to change /system_root mount point back to /system . which is due to recent TWRP changes
i think the script is erroring due to line endings, but im not sure. let me know if the ROM flashed.
for System backup always use the system image format while dealing with android 10. ill update you if twrp pushes any more updates to this
The only Pie roms that we had for FE caused major issues. Not sure if anyone even uses them there was 1 I think. Developer threw a rom together that would throw malware on your device, lock it up and made device unusable then vanished without fixing anything. So not sure if anything is out there and really don't want to update my bootloader.
Sent from my SM-N975U using Tapatalk
ananjaser1211 said:
Please let me know what issues you find in this TWRP, i am aware it boots, backsup and flashes zips. but do let me know if USB / MTP works as expected or if it needs further work.
I will be working on adding FE Support to all my exynos8890 projects moving forward. hopefulyl putting some life in this forum
Click to expand...
Click to collapse
Installed TWRP 3.4.0.0 on the SM-N930, everything works ... Thanks Bro !!!
---------- Post added at 10:02 AM ---------- Previous post was at 09:18 AM ----------
ananjaser1211,may I ask you to build a core for SM-N930X???...I will be grateful.
I have released my cronos kernel for Pie
For a feature list , they are mentioned on this thread here
So now you can use the same kernel from Q on pie ROMs if you choose so.
Download : Github
Enjoy
Just flashed your Floyd Q 3.0 on Note FE...my friend you are really keeping these older devices alive. Thank you.
NOTE FE FLOYD Q 3.0
thank you thank you THANK YOU
---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------
It's work
butchieboy said:
Just flashed your Floyd Q 3.0 on Note FE...my friend you are really keeping these older devices alive. Thank you.
NOTE FE FLOYD Q 3.0
Click to expand...
Click to collapse
Did you have issues booting into system after you rooted? I know it's old but I just can't do it after flashing and following the root guide here
Nope sure didnt
Sent from my SM-N975U using Tapatalk
twrp-3.5.2_9-0-gracerlte.img
twrp-3.5.2_9-0-gracerlte.tar
ripee said:
twrp-3.5.2_9-0-gracerlte.img
twrp-3.5.2_9-0-gracerlte.tar
Click to expand...
Click to collapse
link broken