Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
Portal Link: http://www.xda-developers.com/android/twrp-recovery-now-available-for-the-xperia-u-p-go-and-sola/
Click to expand...
Click to collapse
Installation:
since our device developers are constantly trying to fix bugs, they are always changing something in init.*.rc files for testing. For this reason I can't post a regular boot.img file because it won't work. For now, I've created a script that will take all init.*.rc files from current rom's boot.img and then compile new boot.img with TWRP inside it.
Note : For Rooted & Unlocked Bootloader Only
Note : For 4.4 ROM (should work on older version of android upto 4.1). I only tested with CM11. So please provide feedback
1) Download the latest zip file.
2) Extract it in a folder and place your current rom's boot.img inside that folder. (it must be named boot.img)
3) For latest ramdisk, download it and replace the old initrd.gz with it.
4) Connect your phone with PC. (adb must be working)
5) Open your command line and cd to that folder
6) For linux users, type
Code:
chmod 755 run_me.sh
./run_me.sh
For windows users, type
Code:
run_me.bat
new boot.img file will be created in the current directory named new_boot.img. Power off your phone and flash the boot image.
Code:
fastboot flash boot new_boot.img
7) If you want flashable zips after creating boot image, use this zip http://forum.xda-developers.com/showpost.php?p=51580620&postcount=85
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
To ROM makers
if you include it in your ROM, please give proper credits cause I've spent almost a month trying to port this.Thanks.
Download
recovery_install_19_03_2014.zip - 6.42 MB
Source
TWRP source -> https://github.com/omnirom/android_bootable_recovery
device tree -> https://github.com/Agontuk/android_device_sony_kumquat
Credits
all teamwin members, especially @Dees_Troy for giving me constant advice
@munjeni for his support and answering all my questions
Changelog 14/03/2014
booted
full touch working
adb working
usb mass storage working
custom led for booting
fixed show battery capacity & charging status (+ icon next to percentage)
reboot to bootloader working (from twrp menu)
Changelog 15/03/2014
fixed reboot to recovery (from twrp menu)
Changelog 17/03/2014
added led support to indicate battery status
added brightness slider (under settings => screen in twrp)
Changelog 19/03/2014
reboot to recovery from ROM is fixed
reboot to bootloader from ROM is fixed
F.A.Q
1) Are CWM backups compatible with TWRP ?
Ans: CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it.
Compatible with witch ROM ?
Works great..thanks
Info4Geek said:
Compatible with witch ROM ?
Click to expand...
Click to collapse
OP updated. For 4.4 only. Only tested with CM11.
cdavide98 said:
Works great..thanks
Click to expand...
Click to collapse
did you try it already? How was it ? Which rom are you using ?
NoobCoder said:
OP updated. For 4.4 only. Only tested with CM11.
did you try it already? How was it ? Which rom are you using ?
Click to expand...
Click to collapse
using right now ,with cm11 and it was god .Only one thing where i can find themes for this ?
And if i understeand with some modifications we can have twrp for all rom using your metod ?
Matoxxi said:
using right now ,with cm11 and it was god .Only one thing where i can find themes for this ?
And if i understeand with some modifications we can have twrp for all rom using your metod ?
Click to expand...
Click to collapse
check OP for theming guide. yes, I think it'll work on all 4.4 roms
what is the major difference between CWM and TWRP recovery, and how is TWRP better than CWM?
gomzee1024 said:
what is the major difference between CWM and TWRP recovery, and how is TWRP better than CWM?
Click to expand...
Click to collapse
Google is your friend.
This is a development thread !
Successful installation on MoKee rom.
Appears to work well, don't really have anything to test..
If anyone want the modded TWRP boot.img for CM11 (build 11/03/2014) it's here > http://i4g.me/75hph
recovery boot with slicm
Thank you very much for your effort. Although I'm not using CM11 ATM, I'm pleased to see that TWRP is being developed for XU.
Will it be possible to somehow adapt it to ICS or GB? I'm not asking you to do so, just asking if it is remotely possible
Thanks . It works .
Sent from my Xperia U using XDA Premium 4 mobile app
@NoobCoder : TWRP is working to some extent with CM10 (LE) but the only issue is the USB Mass Storage mode, somehow it is not getting recognized by my PC?! I'm also having the exact same issue when porting the latest CM11 CWM recovery to older Kernels! Here's the logcat, hope you can find what's wrong? -
Thanks.Can mount sdcard in recovery.
Only one bug: can't reboot in recovery.
ROM : CM11 2014/03/11
Kernel : 3.0.101 2014/03/11
Sent from XU powered by KitKat.
PuiuMarius2000 said:
Thanks.Can mount sdcard in recovery.
Only one bug: can't reboot in recovery.
ROM : CM11 2014/03/11
Kernel : 3.0.101 2014/03/11
Sent from XU powered by KitKat.
Click to expand...
Click to collapse
It might be ROM problem. I have already mentioned that in cm11 associated thread.
CM11 20140310
Dhiraj said:
It might be ROM problem. I have already mentioned that in cm11 associated thread.
CM11 20140310
Click to expand...
Click to collapse
No.
On CWM =OK.
On TWRP = NO.
Same ROM and kernel.
Sent from XU powered by KitKat.
@NoobCoder you are the best thing that ever happened to us
keep it up
Related
CHANGELOG
MAIN CHANGELOG IS HERE it's the main CM gerrit changelog
Code:
28/8/13 Nightly
HD Videos in youtube
Updated source
MTP Fixed thanks @[URL="http://forum.xda-developers.com/member.php?u=2404769"]tombriden[/URL]
Camera Fixed to 8mp
SELinux added (not 100% stable)
CMAccount added (for this build only)
------------------------
31/7/13 (nightly)
added the NEXUS 7 UPDATED Audio+EGL blobs (just to get stuff working let me know how this goes)
Updated to 4.3 (CM10.2)
Lack of sleep
Very tired
enjoy :)
------------------------
[ROM][SEMI-UNOFFICIAL] 28/8/13 HTC OneX+ INTER CM10.2 (4.3) Nightlies
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (JB), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, we will laugh at you, all, at the same time.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATIONS
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
CHECK KNOWN ISSUES IN SECOND POST
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
First time installing CyanogenMod 10.2 to your ONE X+, or coming from another ROM:
- Read known issues ans FAQs
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into HBOOT (hold Volume Down at boot)
- Flash the boot.img
- Fastboot flash boot boot.img
- Reboot into recovery via the bootloader menu
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 10.2:
- Copy CM10.2 ZIP to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Reboot
Nightlies:
http://downloads.kanger.me/?dir=nightlies%2Fxplusinter%2Fcm10.2
Google Apps:
http://goo.im/gapps
ClockworkMod Recovery:
http://forum.xda-developers.com/showthread.php?t=2074244
Changelog:
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
source
https://github.com/cyanogenmod/android_device_htc_enrc2b
https://github.com/cyanogenmod/android_kernel_htc_enrc2b
https://github.com/cyanogenmod/android_device_htc_tegra3-common
Thanks to
@maxwen for the bluetooth fix
CyanogenMod team
@tombriden on working with me to get everything fixed with the new base
Install guide:
Download the rom
Download gapps
open the rom.zip (DONT EXTRACT THE WHOLE FOLDER) and pull boot.img out
once you have pull the boot.img out, put the two ZIP files onto your internal partition or sideload them or adb push
reboot into bootloader
flash the boot.img
fastboot flash boot boot.img
then reboot into recovery
FULL WIPE which means WIPE DATA/DALVIK/CACHE/SYSTEM (dont press format data)
Install the Cyanogemod zip
install gapps
reboot
Going back to 4.1.2
If you go back to your old 4.1 backup: Do not forget to re-flash your 'old' boot.img.
Also note that you'll have to move your migrated data from /sdcard/0/ back to /sdcard/ (CWM doesn't know about /sdcard/0/ yet).
This can be done via (while booted in CWM):
Code:
adb shell
cd /sdcard/0/
mv * ../
mv .* ../
cd ..
rmdir 0
Ok this section is the F&Q so if anyone ask's me a question that's been listed here, you'll be ignored.
Q:[B]I cant find all my stuff on the sdcard, where is it?[/B]
A: It's in the 0 folder, it's advisable to move all of your stuff to the 0 folder before flashing.
Q:[B]Where's developer options gone?[/B]
A: Go to about phone and bash Build Number until it says "you are now a developer"
Q:[B]I flashed your rom and all of my sdcard stuff is gone..I HATE YOU![/B]
A: Did you have TWRP or my CWM installed? if not that's why.
Q:[B]DO i need to full wipe?[/B]
A: No if your coming from CM10 then you don't need to full wipe, just install the rom, wipe the dalvik-cache and install rom + gapps and kernel (boot.img)
So much for taking time off!
i'll add 4.3 to the change log + and update the not working list.
Unbelievable
Gesendet von meinem HTC One X+ mit Tapatalk 4 Beta
Notechis said:
Unbelievable
Gesendet von meinem HTC One X+ mit Tapatalk 4 Beta
Click to expand...
Click to collapse
it's not perfect, but i said i would release once AUDIO was working again.
this build includes FOCAL, but ummmm yea camera is borked...looks pretty though
Lloir said:
it's not perfect, but i said i would release once AUDIO was working again.
this build includes FOCAL, but ummmm yea camera is borked...looks pretty though
Click to expand...
Click to collapse
Do you want Logs ? If something happens or a report at bugtracker or , not ?
Well, will flash it in a couple of hours ...
Notechis said:
Do you want Logs ? If something happens or a report at bugtracker or , not ?
Well, will flash it in a couple of hours ...
Click to expand...
Click to collapse
yes please log EVERYTHING, whack it onto the tracker for me please, and state you are using 4.3
Notechis said:
Do you want Logs ? If something happens or a report at bugtracker or , not ?
Well, will flash it in a couple of hours ...
Click to expand...
Click to collapse
let me know if there's crackly audio still, ( you can play music via the cm file manager for now until i fix the usb storage problem) headsets work, don't know about BT headsets though as i don't own one
{
"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"
}
just coz i can
btw guys i cannot put this strongly enough
4.2 GAPPS ARE FOR CM10.1
4.3 GAPPS ARE FOR CM10.2
DO NOT FLASH THE WRONG GAPPS, THE LACK OF KEYBOARD WORKING IS A PAIN IN THE A$$ AND I WONT HELP YOU
work around for google calendar sync, simple as this
download the google calender from the playstore
done
i have uploaded a boot.img to the cm10.2 folder, flash that, usb storage on the device has been fixed, MTP is broken still though. if you can live with using adb push\pull for now great.
Apollo works now
Gallery works now
ringtones + notification tones also fixed with this boot.img
by the way guys
FULL WIPE OR ELSE
and before anyone say's anything, yes i know we now have disco notification lights........bug? i'll let you lot decide hahahaha
Lloir said:
by the way guys
FULL WIPE OR ELSE
and before anyone say's anything, yes i know we now have disco notification lights........bug? i'll let you lot decide hahahaha
Click to expand...
Click to collapse
So I flashed it and gonna test a bit ...
Whats about SuperSU
Flashed the one from Ax and updated it ... but the binaries fail ?
Any idea?
Notechis said:
So I flashed it and gonna test a bit ...
Whats about SuperSU
Flashed the one from Ax and updated it ... but the binaries fail ?
Any idea?
Click to expand...
Click to collapse
no need, koush's su is part of this rom + updated to work
Lloir said:
no need, koush's su is part of this rom + updated to work
Click to expand...
Click to collapse
Strange... Didnt find it and cant get access .... Will have a look at that. Thx Reply soon
Settings > superuser
it's working fine here :/ i even restored everything via Helium
Lloir said:
Settings > superuser
it's working fine here :/ i even restored everything via Helium
Click to expand...
Click to collapse
Hehe. Yes I know thtat place , but Titanium cant get root access like any other app...
If I go into the app everything seems to be fine ...
Notechis said:
Hehe. Yes I know thtat place , but Titanium cant get root access like any other app...
If I go into the app everything seems to be fine ...
Click to expand...
Click to collapse
really??? i got it in my "allow" list in superuser.....
{
"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"
}
for Stock-Oreo
Code:
/* *** Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* BOOM goes the Dynamite
*/
Current Features
* Up streamed to latest stable version 4.4.115
* Built with GCC 4.9
* KCAL Control
* Wakelock Blocking
* Safetynet fixes
* Some other tweaks
* GPU initial frequently lowered to 160mhz
Kernel Aduitor/EX Kernel Manager is recommended for making kernel changes
Kernel Downloads:
Click
Instructions:
A) Boot into Recovery
* (Recommended) Make a complete backup of everything! At least backup BOOT via TWRP
* If you're not coming from completely stock kernel, please dirty flash stock first.
* Flash kernel zip and Reboot
B) via fastboot
* flash Ryzen_rX.img via fastboot (this image doesn't have root)
* flash Ryzen_rX_m.img via fastboot (this image is already patched with latest Magisk-v15.3)
Reporting Bugs (please read):
1. Make sure you're not using any tweak apps (Greenify, Naptime, anything else related), otherwise no support will be given.
2. If you previously flashed another custom kernel, make sure you dirty flash stock first.
3. Logs! Please provide dmesg kernel logs via Syslog app. If you experienced a kernel panic (system crash/reboot) please provide all ramoops file in /sys/fs/pstore/
thanks to everyone who helped me achieve this.
RenderBroken, flar2, joshuous, ak, myfluxi, Savoca and Many More!
Thank you guys!
XDA:DevDB Information
[KERNEL][FEB 8] RyzenKernel -r3 (stock/oreo), Kernel for the Moto X4
Contributors
kraatus90
Source Code: https://github.com/kraatus90/payton.git
Kernel Special Features: Powered by potatoe
Version Information
Status: Stable
Current Stable Version: r3
Stable Release Date: 2018-02-08
Current Beta Version: r1
Beta Release Date: 2018-01-22
Created 2018-01-22
Last Updated 2018-03-19
changelog for r3
* backlight dimmer
* wireguard support
* some other changes
Click to expand...
Click to collapse
can i flash twrp and magisk patched kernel simultaneously ?
rehanraza said:
can i flash twrp and magisk patched kernel simultaneously ?
Click to expand...
Click to collapse
you can try but most likely twrp won't work after flashing kernel. so in order to use twrp, you will have to use bootable twrp image and use it whenever you need it. best thing to do is, flash Ryzen_rX_m.img via fastboot. and instead of flashing twrp, just boot the bootable version.
kraatus90 said:
you can try but most likely twrp won't work after flashing kernel. so in order to use twrp, you will have to use bootable twrp image and use it whenever you need it. best thing to do is, flash Ryzen_rX_m.img via fastboot. and instead of flashing twrp, just boot the bootable version.
Click to expand...
Click to collapse
yes you are right just tried few minutes back and it doesnt work.
kraatus90 said:
you can try but most likely twrp won't work after flashing kernel. so in order to use twrp, you will have to use bootable twrp image and use it whenever you need it. best thing to do is, flash Ryzen_rX_m.img via fastboot. and instead of flashing twrp, just boot the bootable version.
Click to expand...
Click to collapse
The trouble with TWRP being in the boot image is that...well... it is in the boot image.
I have a script to install TWRP as a patch into the current boot image... basically, you would flash the kernel, boot the bootable TWRP and then flash the TWRP installer. Will test it out...
mightysween said:
The trouble with TWRP being in the boot image is that...well... it is in the boot image.
I have a script to install TWRP as a patch into the current boot image... basically, you would flash the kernel, boot the bootable TWRP and then flash the TWRP installer. Will test it out...
Click to expand...
Click to collapse
that would be great, cuz currently there's no way to modify ramdisk and ramdisk modification is necessary for upcoming eas kernel for flash and forget installing. otherwise it's kinda too much work to setup properly. although there's a long way to get fully stable eas. hopefully next month it will be ready.
Bro , After installing the kernel my Wi-Fi became unstable, all online games like bullet force, critical ops and modern combat 5 are disconnecting every 3 minutes. I solved re-flash Stock boot.img And it was stable as before.
Can you give a better Instruction for beginners. Do we need unlocked BL or not and how to flash via ADB Tools, would be awesome!
mk4y5en said:
Can you give a better Instruction for beginners. Do we need unlocked BL or not and how to flash via ADB Tools, would be awesome!
Click to expand...
Click to collapse
Yeah sure, if you're a beginner don't bother installing or messing with this right now.
boladaso said:
Bro , After installing the kernel my Wi-Fi became unstable, all online games like bullet force, critical ops and modern combat 5 are disconnecting every 3 minutes. I solved re-flash Stock boot.img And it was stable as before.
Click to expand...
Click to collapse
Logs, please.
So... I have not had much time lately to work on X4 stuff. But I did find time to build a script to inject the TWRP ramdisk into whatever boot image happens to be on the device.
It works, but for SOME reason it seems to always boot to recovery. Weird. I need to figure out why this is happening. Once I do, we should be able to use the bootable TWRP to flash a TWRP installer ZIP after flashing a custom kernel.
This seems like a much better scenario than having to recompile TWRP with each new custom kernel as it is released.
Will update again in a few days when I nail down this recovery bootloop.
If anyone wants to look, the ZIP is here (again, DON'T flash it as it bootloops): https://drive.google.com/open?id=1UzCz5sgJGCZJZ9ws_H4XZkxOQioWeyoc
It is frustrating that I spent 2 months trying to make a boot image start directly to recovery, and now I can't seem make one that DOESN'T.
Update r2 is released. link on first post.
* upstreamed to latest stable kernel release 4.4.114.
can I flash this kernel in stock android without unlocked bootloader?
diogobuique said:
can I flash this kernel in stock android without unlocked bootloader?
Click to expand...
Click to collapse
nope.
would it be possible to add support for lowering minimum screen brightness?
Abomb said:
would it be possible to add support for lowering minimum screen brightness?
Click to expand...
Click to collapse
will try in next update.
Edit:
Update r3 is here
Hello,
Just wondering, would it be possible to incorporate TWRP (with permission/cooperation from @mightysween of course) into the kernel along with Magisk, so that both TWRP and Magisk get flashed when boot partition is flashed. I am not a programmer or anything, so just ignore if it is a dumb question and is not feasible.
Thank you
anonyo said:
Hello,
Just wondering, would it be possible to incorporate TWRP (with permission/cooperation from @mightysween of course) into the kernel along with Magisk, so that both TWRP and Magisk get flashed when boot partition is flashed. I am not a programmer or anything, so just ignore if it is a dumb question and is not feasible.
Thank you
Click to expand...
Click to collapse
i believe he has tried it already, problem is it boots to recovery instead of system. so pretty much unusable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.1
For device: A6020
Authors build: ATG Droid
Developers: yankit293
Thanks: @yankit293 (for building this for a6020), @Harry8242(for his omni device tree), @Sharps(for his official twrp tree), @[email protected] (for sharing server and guiding me ), @z31s1g (the base of his theme), @Ray Li (For his useful advice in the beginnings), @osm0sis (for his image scripts) etc.
Features
Code:
Translated to EN & CZ
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
* Changes for security reasons *
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
Some differences to the official version:
Code:
[COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- kernel compiled inline with the recovery
- There isn't bug with reboot from recovery to recovery
- more languages
- other improvements from Features and Changelog lists
Changelog
Code:
Initial Build
Installation instructions:
Flash using fastboot method or in recovery as IMG..
Known Bugs:
- Flashlight is not working
Downloads:
Latest build for Lenovo Vibe K5/K5+
Links to builds:
RedWolf-Unofficial-A6020
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery.
XDA:DevDB Information
Red Wolf Recovery Project, Tool/Utility for the Lenovo Vibe K5 Plus
Contributors
Dhruv_Agarwal, yankit293
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2018-02-12
Last Updated 2018-04-09
Reserved
Why did you make several duplicate threads?
One is enough tho...
yayakuya said:
Why did you make several duplicate threads?
One is enough tho...
Click to expand...
Click to collapse
XDA problem when I was posting this thread it always saying error 500 but in actual it's posted
noice boi thread looks fine...
Dhruv_Agarwal said:
XDA problem when I was posting this thread it always saying error 500 but in actual it's posted
Click to expand...
Click to collapse
Maybe you should talk to moderator for delete the entire threads you just accidentally made
Anyway, keep up your great job bro
Very appreciate it :good:
Screenshot please
anyone tried this recovery.
Dhruv_Agarwal said:
XDA problem when I was posting this thread it always saying error 500 but in actual it's posted
Click to expand...
Click to collapse
Me too faced the same often
Screenshots attached.
Nice. You need to port kernel flashlight driver from stock to fix flashlight
Thank you...
what is substratum legacy rescue, how it's works.
run faiz said:
what is substratum legacy rescue, how it's works.
Click to expand...
Click to collapse
If you applied any overlay and phone is not responsive or some problem occurrs ... There's a rescue zip in substratum in internal storage , you can flash that through twrp to remove all overlays !!
i use TWRP not the redwolf version,
can the back up from TWRP be use in this redwolf version?
blitzrachmat said:
i use TWRP not the redwolf version,
can the back up from TWRP be use in this redwolf version?
Click to expand...
Click to collapse
I have some test for backup using twrp, then restore using rwrp. everything is fine, working well without issue at my device a46 3GB variant. my result maybe can help you.
some features are not working, when it get update.
run faiz said:
some features are not working, when it get update.
Click to expand...
Click to collapse
After my exams
Thanks Dev i always waitin something like this.
Amazing! Worked on my phone (Lenovo Vibe k5 w/ Lineoage OS 14.1 w/ root and xposed). So much better than the original TWRP
Dhruv_Agarwal said:
- If you have device variant with 2GB RAM then download zip and flash it using custom recovery!
- If you have 3GB RAM or more then download image and flash it as you want!
Click to expand...
Click to collapse
Really? Won't just flashing a recovery from a recovery create problems? What will happen just after flashing RedWolf from TWRP? Will I get directly redirected to RedWolf or will I have to reboot? Please tell me if this is risky. Using 2GB variant.
{
"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 3.x, or twrp3 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.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Open Source
- Decryption working
- Padding for notch area
Install Instructions:
- Make sure your bootloader is unlocked. If not, unlock it first.
- Reboot to bootloader
- Execute:
Code:
fastboot flash recovery twrp-3.3.1-0-begonia_UNOFFICIAL.img
fastboot reboot
- Boot using power and volume up.
Note: MIUI will keep replacing the recovery with it's own recovery. You need to boot to recovery right after flashing it. Booting to MIUI after flashing may cause MIUI to replace TWRP with Redmi-Recovery. So either find and remove the script responsible for this, or just wait for custom roms
Download:
NON-CFW Recovery:
TWRP 3.3.1-0 Unofficial by Agent_fabulous | md5sum
CFW Recovery:
TWRP for CFW 3.3.1-0 Unofficial by Sahil_Sonar
Source code:
Recovery Source
Device tree
Kernel
XDA:DevDB Information
TWRP for Redmi Note 8 Pro, Tool/Utility for the Redmi Note 8 Pro
Contributors
Agent_fabulous, Sahil_Sonar
Source Code: https://github.com/AgentFabulous/twrp_redmi_begonia
Version Information
Status: Alpha
Created 2019-11-12
Last Updated 2020-06-05
Reserved
Changelog
> 12/11
- Initial build
- Decryption working
> 18/11
- Fix compatibility.zip error when flashing ROMs
- Remove flash, backup and reboot to recovery options from TWRP
> 29/12
- Disable compatibility check entirely
- Fix boot-up on newer MIUI builds
- Fix decryption on newer MIUI builds
> 30/12
- Fix backlight for some users.
Archive
everything working?
thanks
good job mate
Thank you very much for your work man ?
Thank you buddy for your efforts ?
Awesome and just in time. My timer is up tomorrow for bootloader unlock.
I followed your instructions and still miui replaces twrp. Is there a fix for that?
finally developers are here. :victory:
Recovery Updated
> 18/11
- Fix compatibility.zip error when flashing ROMs
- Remove flash, backup and reboot to recovery options from TWRP
Note: For some reason, writing to recovery from within TWRP and rebooting back to recovery bricks the device (in my experience).
Thus, the options have been removed for now.
Download
Can I install this on Indonesian rom with miui 11?
Agent_fabulous said:
Recovery Updated
> 18/11
- Fix compatibility.zip error when flashing ROMs
- Remove flash, backup and reboot to recovery options from TWRP
Note: For some reason, writing to recovery from within TWRP and rebooting back to recovery bricks the device (in my experience).
Thus, the options have been removed for now.
Download
Click to expand...
Click to collapse
You should have left both options available. The original twrp worked perfectly on my global phone. Is the twrp updated to support miui 11?
I am so excited to try this out. I'm just about to unlock the bootloader and it might take years lol... Thank you devs for supporting such device!
Edit: Does it support MIUI 11?
uglypish06 said:
I am so excited to try this out. I'm just about to unlock the bootloader and it might take years lol... Thank you devs for supporting such device!
Edit: Does it support MIUI 11?
Click to expand...
Click to collapse
It does and I am using it right now. Just becareful and make sure you follow instructions to a tee. If not the phone will over write the recovery or you will loose your boot.img file. I lost mine and had to open the battery, disconnect, wait 30 seconds, boot into fastboot, and reinstall 10.4.1 to try again.
Are the steps all right?
1. Unlock the bootloader first
2.turn on USB debug
3.reboot to fastboot mode
4.starting flash twrp
5.boot into recovery mode
6.starting flash xiaomi.eu miui 11 stable rom from twrp
7.waiting it reboot
Are the steps all right? I don't have chance to disconnect the battery from cellphone so I have to do this at all RIGHT steps.
mcarden2006 said:
It does and I am using it right now. Just becareful and make sure you follow instructions to a tee. If not the phone will over write the recovery or you will loose your boot.img file. I lost mine and had to open the battery, disconnect, wait 30 seconds, boot into fastboot, and reinstall 10.4.1 to try again.
Click to expand...
Click to collapse
Sorry I am not understanding, did you flash it on miui 11? Everything is working fine? I'm on miui 11.0.1 Global.
And to reboot into twrp after flash it, will the command 'fastboot boot TWRP.img' work or I have to use physical button?
Thanks!
jim.Duke said:
Sorry I am not understanding, did you flash it on miui 11? Everything is working fine? I'm on miui 11.0.1 Global.
And to reboot into twrp after flash it, will the command 'fastboot boot TWRP.img' work or I have to use physical button?
Thanks!
Click to expand...
Click to collapse
I'd prob wait till this gets sorted out there's a few different posts on this and there all different but all seem to be facing bootloop issues. I'm not sure if it's safe to go back to miui 10 or not without bricking it.
fastjohnson said:
I'd prob wait till this gets sorted out there's a few different posts on this and there all different but all seem to be facing bootloop issues. I'm not sure if it's safe to go back to miui 10 or not without bricking it.
Click to expand...
Click to collapse
I am new to Xiaomi and miui, for what I know it is not safe you will brick the device, but maybe I am wrong... anyway I don't want to downgrade, just to root this damn miui 11 until a good rom is out.
Maybe the dev can clear our mind about! : )
jim.Duke said:
I am new to Xiaomi and miui, for what I know it is not safe you will brick the device, but maybe I am wrong... anyway I don't want to downgrade, just to root this damn miui 11 until a good rom is out.
Maybe the dev can clear our mind about! : )
Click to expand...
Click to collapse
Oh it will there developing mods as we speak. I'm sure this root method works. I'm on miui 11 myself and actually liking it so I'm not into setting up my device time n time again cause I looped it.
fastjohnson said:
Oh it will there developing mods as we speak. I'm sure this root method works. I'm on miui 11 myself and actually liking it so I'm not into setting up my device time n time again cause I looped it.
Click to expand...
Click to collapse
I hope so!
Which root method you mean?
Ok , so did you already flash this recovery on miui 11 global and is working fine?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: Poco M2 Pro (gram)
Maintainer/Authors build: kenny3fcb
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Kernel: https://github.com/ChaitanayaMittal/android_kernel_xiaomi_sm6250.git
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR\
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Downloads
Flashable zip
https://sourceforge.net/projects/po...m-3.0.0-20200806-1712-UNOFFICIAL.zip/download
Contributors
Kenny3fcb , ChaitanayaMittal
reserved
Thanks. Buying this phone tomorrow.
Here we go..
Thanks for the recovery..
Thanks for pbrp. This device gonna rock.
thanks for the recovery sir
This should work on as curtana as well right?
Thanks. need to disable encryption, should i flash any lazyflasher?
btw nice work.
can someone please tell me how to make backups
I want to make backup of my apps and the settings related to it. in backup page I'm getting 2 "super" options what should i so pls help
Encryption problem
It is asking for password when I try to wipe internal storage, showing decryption failed when I try with blank password.....
mohanbarman said:
It is asking for password when I try to wipe internal storage, showing decryption failed when I try with blank password.....
Click to expand...
Click to collapse
i had this issue as well, i fixed it by just starting fresh. flashed stock rom using miflash then rooted it again, watch a video with exact steps. im on a custom rom now but im scared to root it because it bricked my device somehow
Why is there no more update for this recovery?
Unlocked bootloader and flashed recovery (followed the mentioned procedure). Rebooted into the system. Booted back to recovery, replaced by default MIUI recovery. Why? Using MIUI 12 stock
deathgame said:
Unlocked bootloader and flashed recovery (followed the mentioned procedure). Rebooted into the system. Booted back to recovery, replaced by default MIUI recovery. Why? Using MIUI 12 stock
Click to expand...
Click to collapse
I think u need to flash a file lazy flasher.
Or change rom on first recovery boot.
MIUI overwrites recovery to stock.
jthreja said:
I think u need to flash a file lazy flasher.
Or change rom on first recovery boot.
MIUI overwrites recovery to stock.
Click to expand...
Click to collapse
Please provide the link for lazy flasher. Can't find much development and discussion here on xda for this device strange.
Can't flash custom rom just after installing recovery. Can't mount product, vendor etc kind of errors.
deathgame said:
Please provide the link for lazy flasher. Can't find much development and discussion here on xda for this device strange.
Can't flash custom rom just after installing recovery. Can't mount product, vendor etc kind of errors.
Click to expand...
Click to collapse
Need to google bro should not be device specific.
Also you can flash recovery when you are ready to flash the rom. That would be better.
jthreja said:
Need to google bro should not be device specific.
Also you can flash recovery when you are ready to flash the rom. That would be better.
Click to expand...
Click to collapse
I flashed rom just after installing recovery without even booting to system. Got errors while wiping the partitions.
deathgame said:
I flashed rom just after installing recovery without even booting to system. Got errors while wiping the partitions.
Click to expand...
Click to collapse
Have you tried mounting the partitions?
What is the error you get?
jthreja said:
Have you tried mounting the partitions?
What is the error you get?
Click to expand...
Click to collapse
Recovery was unable to mount or unmount product, vendor and system partitions.
Hi,
It is asking for password when I try to wipe internal storage before installing custom rom, showing decryption failed when I try with blank password....
To avoid this issue in future, do i also need to install disable_dm_verity_force_enc zip before magisk?
How to proceed, pls help