TWRP 2.7.1
Team Win Recovery Project 2.7, 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.
{
"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"
}
You can use this recovery with any android version upto 4.4. This includes all sense,cm,stock roms etc
Credits: Nexus prime
Downloads:
TWRP 2.7.1 with Selinux (recommended)
TWRP 2.7.1 without Selinuxhttp://d-h.st/G6a
Changelog:
What's new in 2.7.1.0:
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. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
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
What's new in 2.7.0.0:
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Allow sideloading from /tmp on encrypted devices
Check for a crypto footer before asking for a password to prevent user confusion
Additional checks for validity to auto generated backup names
Text wrap in the console output
Proper caps lock support in the keyboard
Mouse support via USB OTG for devices with a broken digitizer
Improve scanning of storage locations for OpenRecoveryScript
Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
Update SuperSU to 1.93 and improve installation process
Added selinux contexts restoration to fix permissions
Load RTC offset on Qualcomm devices to fix the date/time in recovery
USB Mass Storage fixes Add SELinux support checking
Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
Add 4.4 AOSP decrypt support
Add some toolbox utilities to TWRP (
Click to expand...
Click to collapse
Awesome dude, eagerly awaiting Sellinux kernel now
Tested a small Boot backup and restore and it works. I don't have space to do the whole data or system backup.
Is this the same version i installed with the toolkit today?
There i get many grafic glitches on my desire x.
Bib_x said:
Is this the same version i installed with the toolkit today?
There i get many grafic glitches on my desire x.
Click to expand...
Click to collapse
The graphic glitches are probably related to flashing unstable roms and not wiping after new install as i'm using this recovery and experience no graphic glitches.
and the recovery from toolkit is most likely the older twrp recovery
Do we need a kernel with SElinux to flash the cm11 you shared or just the recovery will do?
Sent from my HTC Desire X running mySENSEdx5 RC4.0
Dolanoi said:
Do we need a kernel with SElinux to flash the cm11 you shared or just the recovery will do?
Sent from my HTC Desire X running mySENSEdx5 RC4.0
Click to expand...
Click to collapse
Directly flash the recovery. No kernel required.
InfinityShooter said:
Directly flash the recovery. No kernel required.
Click to expand...
Click to collapse
Alright. I'll try your cm11 build in about an hour..
Thanks!
Dolanoi said:
Alright. I'll try your cm11 build in about an hour..
Thanks!
Click to expand...
Click to collapse
Wont boot
Wait for fozzy's build instead
InfinityShooter said:
Wont boot
Wait for fozzy's build instead
Click to expand...
Click to collapse
Ohh.. Alright.
But I'm definitely gonna try the recovery!
Stunning Work As Always @InfinityShooter :good:
Finally smooth scrolling in file manager.. Thanks for your hard work
Keep up :good:
Just did a full backup and restore. Works like charm!
Well done! Waiting for a cm11 build now..
Am i right, if i install s-off i can install new roms without flashing boot.bin with fastboot?
Simply flash the new rom, wipe cache witch twrp and i don´t need computer anymore for adb commands?
Wipe cache is not working without s-off if i do it with twrp?
Btw it isn't hard to enable selinux in kernel compilation, but IMHO it is not everything needed. I can provide you a SElinux enabled kernel for test, twrp should have a test to verify selinux.
Found bug where I can't flash boot.img from recovery
//.dax said:
Found bug where I can't flash boot.img from recovery
Click to expand...
Click to collapse
I think you cant, only with S-Off and that has the Vibration-Bug...
Pandur said:
I think you cant, only with S-Off and that has the Vibration-Bug...
Click to expand...
Click to collapse
I am S-Off.. Restoring from backup works fine, flashing together with ROM too, but flashing separately not.
Error has something to do with name of the partition, because it shows that kernel has to be flashed on Boot LNX or something, I don't know
i install it after i use 2.5.0.0 and its works good ... Thanks!
Now we need KitKat :cyclops:
Related
Hi All, This is my Proudest accomplishment and i though to share it with yous.
I've Made This Tool For The HTC One X, but it shouldn't work any differently on your Device,
If You Found A Problem That's One X+ specific, ill make a separate update that work specifically for the HOX+
I'm Thunder & This is My Flash.....er
{
"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"
}
I Made this simple flasher because its really annoying flashing the modules & Kernel separately,
and as the name says One Click,
just choose your kernel & module and let it do the rest.
Download Link V2.1
Functions:V1.0
Flash Kernels & Modules
Flash Recoveries
Reboot The Phone
Reboot Into Recovery/Bootloader
V1.1
Kernel Repack - Phone on Android with USB Debug Enabled - No Need For The Recovery
v1.2
MultiKernel Repack
Repacked output Format Kernel.Ramdisk.IMG
V1.3
One Click Root
V1.4
Reworked Module Flasher
Decreased/Removed some delays
Fixed Faux Module Unzipping Problem
V1.5
Added RUU Zip Flashing Ability - For Advanced Users
V1.6
Added Erase Cache
Added Basic Help Section
Added About
V1.7
Added Lock/Unlock Option
This Requires HTCDev's Unlock_Code.bin,
Which has to go into the unlock folder
Updated V1.8
PC Based Repack (Thanks To The Great Work Of XDA Member Langer Hans)
IMG/APK Flasher/Installer (With The Open With Command (will add an association option later on))
V1.9
Logger (Logcat/kmsg/last_kmsg retriever)
V2.0
Can Now Flash Modules Without Having To Flash The Kernel,
Modified The Logger (Debugger) To Show Logs In Console, As it's Much Better At Handling Text
Removed Log Limit
V2.1
Added Battery Stat Into Phone GroupBox
Can Log Logcat & KMsg at the same time (last_kmsg if you really want to go all out )
Dont Touch The Apps Folder
Kernels/Modules/Recoveries go into there respective folders,
and they will appear in the app
Connect The Phone To The PC Via a USB Cable In Anymode (Android(With USB Debug)/Recovery/Bootloader) Though Preferably In The OS or The Recovery,
Choose The Option You Want, E.g. Flash Kernel
Choose The Option That Show Up, The Kernel & its Modules.
Choose What To Do On Completion
Click Perform Action, Site & Wait.
Requirements:
Unlocked Bootloader
CWM Recovery (Havent Tested other recoveries)
USB Debug Enabled (Settings --> Developers Tools --> USB Debug)
.Net Framework 3.5(Only need this if you get .NET framework initialization error)
Though i have tested it and its working fine and just to cover my ass....
Always have a nandroid backup incase things go wrong,
If anything goes wrong i would help you, but i'm not to be held responsible for any damange done (hopefully there wont be any)
Coming SoonList Updated 25th Sept
ADB Based File Explorer
Backup
And Some More
Waiting For Your Suggestions
if you find any problem or have a suggestion feel free to drop a comment
Please keep the suggestions/problems on this thread and not through my PM,
to avoid repeated suggestions/problems, see other reaction and get help from the community.
Also Leave A Comment To Keep This Post Alive.
Thank You
Credits:Daekin - For Providing The Tools For Repack
ChainFire - For His SuperSU
Langer Hans - For His PC Based Repack Code
you might want to remove the link pointing to the HOX recovery image dude
Lloir said:
you might want to remove the link pointing to the HOX recovery image dude
Click to expand...
Click to collapse
Done
Thanks
Nice tool
Just one comment regarding all AOSP based roms
from Lloir and myself which use the BLADE kernel
You dont need to do this for those roms!
The rom is taking care that the kernel modules are
in the correct location if required using an init.d script
But it will do no harm cause we are "smart" enough do detect it
maxwen said:
Nice tool
Just one comment regarding all AOSP based roms
from Lloir and myself which use the BLADE kernel
You dont need to do this for those roms!
The rom is taking care that the kernel modules are
in the correct location if required using an init.d script
But it will do no harm cause we are "smart" enough do detect it
Click to expand...
Click to collapse
cool, im guessing you're speaking of modules injector??
i was wondering why we aren't using something like that on the HOX,
im guessing you either have a bigger boot partition or that module's sizes are really small?
worst come to worst... this still have a logging feature which will come in handy...
and for the record, ill update and make it more usable
thunder07 said:
cool, im guessing you're speaking of modules injector??
i was wondering why we aren't using something like that on the HOX,
im guessing you either have a bigger boot partition or that module's sizes are really small?
Click to expand...
Click to collapse
The modules are included in the boot image in /lib/modules
and synced with /system/lib/modules on boot if required
Using xz compression for the kernel makes it small enough
So e.g. BLADE kernel has about 4.4mb including everything
Updated V2.0
Can Now Flash Modules Without Having To Flash The Kernel,
Modified The Logger (Debugger) To Show Logs In Console, As it's Much Better At Handling Text
Removed Log Limit
Get it in the 1st post
V2.1
Added Battery Stat Into Phone GroupBox
Can Log Logcat & KMsg at the same time (last_kmsg if you really want to go all out )
Get it in the 1st post
Help! I'm getting "Invalid Modules" when trying to flash kernel. This is what I did: unzipped boot.img and modules folder from elemental kernel, put those them in the respective folders under one x one click folder, ran the one click exe as administrator (win7), chose the kernel img and modules zip, it seems to run for a second and then the invalid modules and operation terminated. Obviously I'm not doing it correctly with the modules zip process.
jamesc760 said:
Help! I'm getting "Invalid Modules" when trying to flash kernel. This is what I did: unzipped boot.img and modules folder from elemental kernel, put those them in the respective folders under one x one click folder, ran the one click exe as administrator (win7), chose the kernel img and modules zip, it seems to run for a second and then the invalid modules and operation terminated. Obviously I'm not doing it correctly with the modules zip process.
Click to expand...
Click to collapse
can you link me to those module?
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
What's new in 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
What's new in 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
Downloadhttp://androidfil.es/1mMD
Huge shoutouts go specifically to
@Flemmard @bigbiff @Dees_Troy
I learned how to properly deal with DTB from these guys....
Known Issues:
No known issues anymore
No exFAT support. Need kernel source to investigate
Random segfaults when starting actions. i.e. flashing restoring, backing up. Just makes you redo what you were trying to do. Dees_troy deems this nearly impossible to trace.
Glad to see you here JMZ!!
Hi I'm trying to get a recovery flashed on my phone and I've been working with mike1986 for a couple hours and for whatever reason my phone refuses to flash it. Every time I run the fastboot flash recovery command it gets to: sending 'recovery'... and then just hangs there indefinitely until I reboot. Any ideas? Thanks!
im getting cache errors in the recovery.
fix-this! said:
im getting cache errors in the recovery.
Click to expand...
Click to collapse
Can you pull /tmp/recovery.log and post here. I'm not seeing this on my device
Sent from my HTC One_M8 using Tapatalk
jmz said:
Can you pull /tmp/recovery.log and post here. I'm not seeing this on my device
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Just tried to flash it. It worked when I backed up to internal memory but when I tried to back up to the external sd card I got this error:
E: Unable to create folder: /external_sd/TWRP/BACKUPS/SerialNum/Date
errno=13
failed to make backup folder
graffixnyc said:
Just tried to flash it. It worked when I backed up to internal memory but when I tried to back up to the external sd card I got this error:
E: Unable to create folder: /external_sd/TWRP/BACKUPS/SerialNum/Date
errno=13
failed to make backup folder
Click to expand...
Click to collapse
you on freenode anywhere?
jmz said:
you on freenode anywhere?
Click to expand...
Click to collapse
Not at the moment. I'm in class. I should be home on a couple of hours
Sent from my HTC One_M8 using Tapatalk
Uploaded a new version. Tested backing up to external sdcard and OTG. Not quite sure what the issue was before
How is this different from the one posted in the international m8 section? I see this is 2.7.0.0 though. Is it wise to run theirs or no?
jmz said:
Uploaded a new version. Tested backing up to external sdcard and OTG. Not quite sure what the issue was before
Click to expand...
Click to collapse
Still getting the same error. I'll be home in a few and can jump on irc
and to add to it.. When it failed to back up I pressed the reboot system button right there. All the other times I would back out to the main menu to the reboot menu.. Now after I pressed reboot right after the error I'm stuck at the bootlogo, no adb access and holding power isn't rebooting the phone either
I got it to reboot by holding volume up and power. Booted back in now.. That was odd.
graffixnyc said:
Still getting the same error. I'll be home in a few and can jump on irc
and to add to it.. When it failed to back up I pressed the reboot system button right there. All the other times I would back out to the main menu to the reboot menu.. Now after I pressed reboot right after the error I'm stuck at the bootlogo, no adb access and holding power isn't rebooting the phone either
I got it to reboot by holding volume up and power. Booted back in now.. That was odd.
Click to expand...
Click to collapse
What format is your sdcard in
Sent from my HTC One_M8 using Tapatalk
Adb fasboot flash recovery recovery.img right? Been awhile lol
Sent from my HTC One_M8 using Tapatalk
Fidelio_o said:
Adb fasboot flash recovery recovery.img right? Been awhile lol
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
It should just be
Code:
fastboot flash recovery recovery.img
The "adb" at the beginning isn't necessary.
fix-this! said:
How is this different from the one posted in the international m8 section?
Click to expand...
Click to collapse
I'm curious to know too.
fix-this! said:
How is this different from the one posted in the international m8 section? I see this is 2.7.0.0 though. Is it wise to run theirs or no?
Click to expand...
Click to collapse
Tikerz said:
I'm curious to know too.
Click to expand...
Click to collapse
this is built from source. Not ported from M7. plus this supports external sdcard
im getting error: cannot open recovery.img
NEVERMIND IM AN IDIOT
Uploaded a new version. 2.7.0.2 This has working offmode charging
{
"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"
}
Having the same issue with my SD card as above. 64gb SD formatted in exfat. System uses it fine for photos etc...
Sent from my HTC One_M8 using Tapatalk
Team Win Recovery Project
for Huawei Mediapad
{
"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"
}
Chagelog:
What's new in 2.7.1.0 :
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. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
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
What's new in 2.7.0.0 :
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Allow sideloading from /tmp on encrypted devices
Check for a crypto footer before asking for a password to prevent user confusion
Additional checks for validity to auto generated backup names
Text wrap in the console output
Proper caps lock support in the keOnly For KitKat ]yboard
Mouse support via USB OTG for devices with a broken digitizer
Improve scanning of storage locations for OpenRecoveryScript
Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
Update SuperSU to 1.93 and improve installation process
Added selinux contexts restoration to fix permissions
Load RTC offset on Qualcomm devices to fix the date/time in recovery
USB Mass Storage fixes Add SELinux support checking
Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
Add 4.4 AOSP decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes
Download:
TWRP 2.7.1.0
In case of Twrp freezing with a blank screen, like previous versions except the very first release, disable screen timeout.
Team Win Recovery Projecty 2.7.1.0 - 05.08.14
- Fixed mount sdcard / intrenal storage
- Add mount otg-usb
Update
Which device is this for?
omniphil said:
Which device is this for?
Click to expand...
Click to collapse
OP's title says "Mediapad" so I think it's for the s7-301u. He's one of the 2 famous devs for keeping the Mediapad alive for 2 years after its EOL.
The original Mediapad is still a good device, and the X1 is its true successor.
joytest said:
OP's title says "Mediapad" so I think it's for the s7-301u. He's one of the 2 famous devs for keeping the Mediapad alive for 2 years after its EOL.
The original Mediapad is still a good device, and the X1 is its true successor.
Click to expand...
Click to collapse
Ok, so that's the Tablet and not the Mediapad phone...
omniphil said:
Ok, so that's the Tablet and not the Mediapad phone...
Click to expand...
Click to collapse
LOL....the Mediapad is ALSO a phone....in tablet form. It is 7" 1280x800, with a Qualcomm S3...a beast for its day. It's being used by the kids now
joytest said:
LOL....the Mediapad is ALSO a phone....in tablet form. It is 7" 1280x800, with a Qualcomm S3...a beast for its day. It's being used by the kids now
Click to expand...
Click to collapse
Ah, so you can see where the confusion is with the naming conventions from Huawei.
Mediapad vs Mediapad X1
Hellooo !
To be honest I dont remember how to install the TWRP, why? cuz i did it a loooooong time ago and nowdays i only flash the *.zip in my Galaxy S3mini
Im using the MediaPad Lite 7 ( s7 - 932u ) and i have the twrp on it, can someone be the kindly one that explain it to me?
I like Twrp so much, that i have two of them installed. Probably since a very long time. Occasionally, Twrp 2.3.2.3 could not access sdcard, a reboot fixed that. I could not explain that to myself. Since the update to 2.7.1.0, occasionally a Twrp 2.3.2.3 shows up, which cannot access the sd.
BTW, how big is the MP's Recovery Partition supposed to be? Mine is 16mbyte, big enough for two recoveries, and maybe corrupt.
Update
Team Win Recovery Projecty 2.7.1.0 - 13.07.14
- Fixed mount /cache
zyr3x said:
Team Win Recovery Projecty 2.7.1.0 - 13.07.14
- Fixed mount /cache
Click to expand...
Click to collapse
hello everyone ... but how do I install this img file?
thank you
lucacata said:
hello everyone ... but how do I install this img file?
thank you
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
zyr3x said:
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry but I have not figured out how and where to perform the installation ... could you help me?
lucacata said:
sorry but I have not figured out how and where to perform the installation ... could you help me?
Click to expand...
Click to collapse
Get the device into fastboot mode by pressing Power + Down Vol
Connect to the PC and type those commands by zyr3x
I updated with Rashr. There's also Flashify and Rom Installer, the latter one having issues with the MP.
The secondary recovery Twrp 2.3.2.3 is still there and can be invoked by a cold start. Is 16mbyte the correct size for the recovery partition, as something must have gone wrong in the past?
Sorry but i didnt understand...is it for Mediapad X1, will it work?
moviehunter2009 said:
Sorry but i didnt understand...is it for Mediapad X1, will it work?
Click to expand...
Click to collapse
Not
Sent from my Nexus 4 using XDA Premium 4 mobile app
Huawei mediapad x1 recovery
Is there any recovery, either Cwm or TWRP for the Huawei mediapad x1?
I think i've read about one real custom rom(cm11?), so there must also be a recovery.
Not necessary for modded, rooted stock roms installed via standard procedure. Though I installed one for convenience on the original MP, with Comec rom.
TLDR:
MAKE A BACKUP. Seriously.
Downloads in second post. Flash recovery, then kernel, then MultiROM.
A kernel with the kexec-hardboot patch doesn't exist as of now. It is being worked upon be me
{
"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
This is a port of Tassadar's MultiROM, a multi-boot mod for OnePlus 2. 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.
This is still very experimental!
Features:
Multiboot any number of Android ROMs
Restore nandroid backup as secondary ROM
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
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 3 parts you need to install:
Modified recovery (TWRP_multirom_oneplus2_YYYYMMDD.img) - download the IMG file from second post and use fastboot/recovery to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch.
Download the ZIP file and flash it in recovery.
MultiROM (multirom-YYYYMMDD-vXX-oneplus2.zip) - download the ZIP file from second post and flash it in recovery.
Note: Your current ROM will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Updating 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 MultiROM in recovery and do Inject current 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 MultiROM and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Changing ROMs
A kernel with the kexec-hardboot patch does not exist as of yet. It is being worked upon by me.
Hence for now, please use the recovery to swap the ROMs
Source Code
MultiROM - https://github.com/regalstreak/multirom (branch: master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch: android-6.0)
Kernel w/ kexec-hardboot patch (being worked upon) - https://github.com/regalstreak/android_kernel_oneplus_msm8994/tree/android-6.0-mrom
Device tree: https://github.com/regalstreak/android_device_oneplus_oneplus2/tree/android-6.0-mrom (branch android-6.0-mrom)
Credits
This port is based on the hard work of Tassadar, Geoff Levand, webgeek1234, Mike Kasick, Npjohnson, Hashbang173, 500 Internal Server Error and many others. Thank you.
Special thanks to @500 Internal Server Error for porting MultiROM to arm64 devices!
Donations
I'd be glad if you could spare a few bucks. You can use either Paypal or Bitcoin, my address is 1mg1HJcNTrNNPbrQqKXsUgdDfZhGo2acC
Also consider donating to @Tasssadar
Thanks to all donors, it is much appreciated!
Downloads
MultiROM Recovery
MultiROM Installer Flashable ZIP
MultiROM Uninstaller Flashable ZIPs
Reserved Post 1
Reserved Post 2
Wow, You made it. You Da real MVP.
Will report back here.
Perfect. Works perfectly. Able to swift between roms. Thanks a lot. This takes development to a whole new level.
MultirROM --> Ubuntu Touch!
Finally!
You are one of the best devs out there
regalstreak said:
Downloads
MR-TWRP IMG: recovery-20160228.img
MultiROM Installer Flashable ZIP: multirom-20160228-v33-UNOFFICIAL-oneplus2.zip
MultiROM Uninstaller Flashable ZIP: multirom_uninstaller.zip
All being uploaded. Keep calm please
Click to expand...
Click to collapse
R I O T
jk good work man!
Sent from my ONE A2005 using Tapatalk
Links up. Please test!
TESTING
added cm13 as secondary and oxyslim as primary
currently its flashing.
will report
edit - booting oxyslim... after booting ill try to boot secondary rom
edit 2 - booting cm13
so.. swapping works
How to switch between roms? Have not boot Menü
Ok. Sorr, only swap works this time.
rakieta said:
How to switch between roms? Have not boot Menü
Ok. Sorr, only swap works this time.
Click to expand...
Click to collapse
Go to recovery and switch rom.
Thanks a ton @regalstreak. Literally been waiting for ages for this! You da real MVP!
Is there anyway to transfer my "dual boot patcher" roms (primary and 3 data slot roms) to multirom?
JudderArts said:
Is there anyway to transfer my "dual boot patcher" roms (primary and 3 data slot roms) to multirom?
Click to expand...
Click to collapse
Haha nice idea
But there isnt any way you will have to manually do it!
Recovery won't work with H2OS M version, right?
regalstreak said:
Haha nice idea
But there isnt any way you will have to manually do it!
Click to expand...
Click to collapse
Manually as in flash them again and such?
lucasbtx said:
Recovery won't work with H2OS M version, right?
Click to expand...
Click to collapse
I guess yeah as h2os is too pretty ****ed up, it doesnt even have a kernel source :3
JudderArts said:
Manually as in flash them again and such?
Click to expand...
Click to collapse
yes bro
Hi dear. I can't find kernel on 2nd post. Will it be enough to have my existing primary kernel.
Sent from my ONE A2001 using Tapatalk
Awesome Regal !!! I also made my multirom for op2 some days ago but wasn't able to build kernel too.... Thus didn't make thread.... See the commits for our kernel on github.com/multirom-op2
Looks like a problem at ramoops ... Everything else is perfect....
Sent from my ONE A2003 using Tapatalk
So question...is there any way to share app data or such between Roms? Possibly a noob question but still gonna ask ?
TWRP RECOVERY FOR GALAXY J7 PRIME
{
"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"
}
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.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR BRICKS. FOLLOW THE STEPS CORRECTLY.
WARNING: 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.
What's new in 3.1.0-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
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.
Instructions:
Flash with ODIN in the AP slot.
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/7.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.
DOWNLOADS:
twrp3.1.0-0
Use Odin to flash.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot to if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery. If you choose to 'Allow' then SuperSU needs to be flashed to disable dm-verity.
To Root:
Flash the latest SuperSU:
http://www.supersu.com/download#zip
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
(Note this MUST be flashed before SuperSU if you intend to root)
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 modded kernel from below.
5. Reboot
Modded Kernel:
https://mega.nz/#!tJ5XVa4I!_kMCzV7kOMvEdvJwB3ZUDPZjGUNIuuzK6RSLHMiZG4M (Thanks to maxx35000)
NOTE: NO NEED TO FLASH MODDED KERNEL IF YOU ARE USING ANY CUSTOM ROM
HIT THANKS IF I HELPED YOU:good:
is this oficial ?
Mounting internal is working?
Not work on last update from samsung, with update AQC4 recovery not incompatible
Janeslejade said:
Mounting internal is working?
Click to expand...
Click to collapse
Yes. Read the thread on how to do this.
hoangphuc057 said:
Not work on last update from samsung, with update AQC4 recovery not incompatible
Click to expand...
Click to collapse
It's working. I'm on AQC4
Not working on G610Y.
---------- Post added at 09:23 AM ---------- Previous post was at 09:11 AM ----------
Guys, i want to go back to stock recovery, questions.... Is it safe to flash this stock recovery??
SM-G610F/M_stock_recovery
My unit is G610Y.
Up... Please help, i need the SM-G610Y_stock_recovery... Please someone help or advise if SM-G610F/M_stock_recovery is okay to flash on G610Y??
Help guys! I tried to root my phone but no success. It says need adb 1.3 or newer. What should i do?
External sd mounting?
Thanks for the update, working on G610M
4. Install modded kernel from below.
Click to expand...
Click to collapse
how to do this?
Ephesis said:
how to do this?
Click to expand...
Click to collapse
Flash through odin in AP
Siddhant NAik said:
Flash through odin in AP
Click to expand...
Click to collapse
how about rooting? flash via odin too?
---------- Post added at 09:52 AM ---------- Previous post was at 09:40 AM ----------
Flash through odin in AP
Click to expand...
Click to collapse
Odin wont read it since its a zip file not a tor file.
inamie said:
External sd mounting?
Click to expand...
Click to collapse
This is the essential question!
thank
trinaldi said:
This is the essential question!
Click to expand...
Click to collapse
not working.
Anyone tried this on G6100 ?
Please update aqc4 mod kernel
Thank you bro. Haha :d :d