TWRP Recovery 3.0.2.0 For Samsung Galaxy Star GT-S5282
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.*/
Team Win Recovery Project (TWRP), is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface which allows users to install third-party firmware and backup the current system, which are often unsupported by stock recovery images.
Screenshots
Under screenshots tab
Installation
Pick your build type, i.e recovery flashable or Odin flashable.
If recovery flashable, simply put the zip in phone, and flash it from an existing working recovery.
If Odin flashable, go to download mode, connect to PC, run Odin, select 'PDA', select the twrp tar.md5, flash it.
Enjoy.
Walkthrough
Since our device resolution is low, TWRP does not fit into the screen, hence there is a button with arrow key (left/right), which indicates that there is another section of the page, pressing that button takes you to the other section.
Downloads
Flashable ZIP
ODIN Flashable tar
Device Specific Source
Here .
Credits
@corphish
@Dreamstar
@psych.half
@andii_nr
TeamWin
XDA:DevDB Information
TWRP 3.0.2-0, Tool/Utility for the Samsung Galaxy Star
Contributors
LahKeda
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2016-08-08
Created 2016-08-08
Last Updated 2016-08-08
Fetures And Notes !
Fetures
You can now backup your EFS partition !
Full Selinux support !
Compressed using LZMA to fit our device space !
Notes
-You will not be able to unpack this recovery image to take kernel image or modify ramdisk as the ramdisk is compressed using LZMA not GZIP to fit the device recovery partition ! - You will only get kernel Image if you used boot-repacker for windows - .
-If you are going to build a recovery using device tree provided in this thread you'd better use the prebuilt kernel provided with the tree !
Hello reserved
Cool bro !!! please tell me whether it is possible to flash the kernel r10 "psych.half"on cm13 by using a script http://forum.xda-developers.com/showthread.php?t=2670512
medved197938 said:
Cool bro !!! please tell me whether it is possible to flash the kernel r10 "psych.half"on cm13 by using a script http://forum.xda-developers.com/showthread.php?t=2670512
Click to expand...
Click to collapse
You can't flash psych.half kernel on cm13 it won't work .
pretty cool,.THANKS for this one...
s5282
"E:signature verification failed"
what can I do?
got it
Pfff. installed windows on old comp and managed to install TWRP using Odin.
No idea why it doesn't work with adb
anyway I guess I'm last one with this phone on this planet
Is it still working? I tried everything but couldn't flash twrp in my gt 5282
ShineBaka said:
Is it still working? I tried everything but couldn't flash twrp in my gt 5282
Click to expand...
Click to collapse
Install as odin flashable.tar. Install odin 3.10.6, add it to the AP part and flash it. I just tried it works
Worked like a charm thanks
i installed with odin, flash succeded, but when i want to go to recovery by power + volup + home it just turns off and restart. when i use adb reboot recovery it just turns to android default recovery.
---
edit: i'm not sure how but it's working
Related
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, I will laugh at you.
*/
NVFlash backups, please do them before flashing anything below otherwise you will **** out of luck if you brick
Download:
cm-12-20150219-UNOFFICIAL-tf201.zip
cm-12-20150321-UNOFFICIAL-tf201.zip
cm-12.1-20150405-UNOFFICIAL-tf201.zip
cm-12.1-20150713-UNOFFICIAL-tf201.zip
Recovery:
recovery.img
Note that the touch buttons are really close together and there's no confirmation before you want to flash a zip sooooo... use the power keys if you are extra scared/careful.
In addition, the script output is impossible to see, which is kinda problematic.
XDA:DevDB Information
Cyanogenmod 12.1 Unofficial, ROM for the Asus Eee Pad Transformer Prime
Contributors
Namidairo, Androidroot, CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-02-15
Last Updated 2015-04-05
Hi. I see no download section. So do I use the current recovery or should I wait? Using twrp with f2fs.
Hi,
What's the differences with official cm12 for tf300t?
I tested tf300 official and had lots of problems and I would prefer not to have them again ?
hi, please upload f2fs recovery if this rom support f2fs.thank you!
Edit: all is good. I'm back on track.
Ahhhh. I used the one from cm11 topic. Big mistake. Now I'm getting android service icon flashing screen. Reboot is the same, can't access fastboot or bootloader or recovery, tablet is recognized by pc. Attached the picture of what is on my screen if anyone has an idea.
Just curious. Installed cm recovery, the rom and gapps (the smallest ones) and now waiting at Asus bootlogo. How long does the first boot take?
I have the same problem. My TF201 is stuck at the bootscreen with the Asus-logo.
What did I do:
- wiped cache
- factory reset
- flashed recovery.img from post #1
- flashed firmware from post #1
- reboot and stuck at Asus-logo
I can still reboot into the recovery.
Where did I go wrong?
Just flash the last cm11 with f2fs support to get the tablet working. No need to change recovery.
suhiSLO said:
Just flash the last cm11 with f2fs support to get the tablet working. No need to change recovery.
Click to expand...
Click to collapse
thx reply,
i listed the step as below. am i right?
1)download recovery_f2fs on cm11 section
2)use the code format mmcblk
mkfs.f2fs -t 0 /dev/block/mmcblk0p2
mkfs.f2fs -t 0 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
3)install cm12
4)reboot
if i were wrong,may i know the step and compatible recovery download link?
suhiSLO said:
Just flash the last cm11 with f2fs support to get the tablet working. No need to change recovery.
Click to expand...
Click to collapse
Why should I flash CM11 (KitKat) when I want CM12 (Lollipop, that this thread is about)?
I used the software (recovery, firmware) that Namidairo posted in his first post in this thread.
GoldenAvatar said:
Why should I flash CM11 (KitKat) when I want CM12 (Lollipop, that this thread is about)?
I used the software (recovery, firmware) that Namidairo posted in his first post in this thread.
Click to expand...
Click to collapse
Just to make the tablet working until namidairo offers a solution. At least that's what I did.
---------- Post added at 04:41 PM ---------- Previous post was at 04:34 PM ----------
atoyu said:
thx reply,
i listed the step as below. am i right?
1)download recovery_f2fs on cm11 section
2)use the code format mmcblk
3)install cm12
4)reboot
if i were wrong,may i know the step and compatible recovery download link?
Click to expand...
Click to collapse
If you want to try to make cm12 work use the recovery from this topic. I replied to goldenavatars post.
when using recovery on this topic, it hold on asus boot screen......
any md5 for this file?
Did the install using TWRP 2.7.0.0 and also flashed the gapps-lp, On reboot screen stuck at the Asus logo and will not proceed. Is there a md5 available for the ROM zip file so I can do a check?
I am currently running namidairo's CM11 build on my TF201. Do I just flash the recovery and then this image to get lollipop?
Also was GAPPS work with this build?
Thanks.
Oops, SELinux chucks a fit about some of the vendor libs when I set it to enforcing.
This is why you actually test with the same kernel that you are deploying. (Reboot shenanigans meant the bootloader ignored my staging partition and didn't flash the new kernel, yay.)
Anyway, I'll pull the zip and upload one with it set to permissive for now (Which is a temporary fix, I'll fix up the sepolicies when I have time)
Edit: Up
Working. Thank you.
Namidairo said:
Oops, SELinux chucks a fit about some of the vendor libs when I set it to enforcing.
This is why you actually test with the same kernel that you are deploying. (Reboot shenanigans meant the bootloader ignored my staging partition and didn't flash the new kernel, yay.)
Anyway, I'll pull the zip and upload one with it set to permissive for now (Which is a temporary fix, I'll fix up the sepolicies when I have time)
Edit: Up
Click to expand...
Click to collapse
Can't wait to try this later tonight
Yup, same.
Missing superSU. So additional apk install needed. I tried to install zip version but it looks like it didn't stick.
suhiSLO said:
Missing superSU. So additional apk install needed. I tried to install zip version but it looks like it didn't stick.
Click to expand...
Click to collapse
Did you enable root in developer options?
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, I will laugh at you.
*/
Warning
This recovery will TRIP your Knox Counter and your warranty will be void.
This recovery is only for Samsung Galaxy A700FD Qualcomm Snapdragon variant running 5.0.2 (lollipop).
Tested Safely on following devices.
Samsung Galaxy A700FD
Why TWRP ? Why not some rooted firmware which keeps warranty safe ?
TWRP is a custom recovery. It has many more functionality than stock recovery! if something goes wrong while flashing something you can always make a backup use this recovery which can be restored when things get messed. if mess is of large extend you can always flash stock firmware.
Why new TWRP Recovery ?
The older version which was released will not be compatible with cm structure due to mount points and hence this recovery will be supportable for all custom flashing.
Instructions
Follow the instructions carefully.
Step 1 :
Install Samsung Drivers and connect your device to PC. let it install drivers and if its updating let it update. your device drivers should be perfectly installed without a single failure.
Link to Samsung Drivers
Step 2 :
Download Odin 3 you can use 3.07 or 3.09
You can download Odin from here
Download the TWRP Recovery
Step 3:
Turn of your device and go to odin mode [ Vol down + power + home button (all at the same time) ] release it when you see Galaxy A7 Logo
Press vol up to confirm
Step 4:
Now that you are in Odin Mode connect your device via USB cable.
Now open Odin3 3.09 or 3.07 that you have downloaded.
If there is a pop-up like Installing ADB drivers let it get finished it usually updates.
Make sure the COM : xx (xx is usb port number it can be any number so dont worry about it,just verify COM is lit up)
Now select AP and browse to where you have .tar file and select it
Make Sure only Default Auto Reboot and F. Reset Time is ticked and nothing.verify twice only these 2 are ticked.
Untick Auto Reboot if you are installing recovery for first time!
Click Start and wait for the process to end. DO NOT Interrupt during this time.
Once it says PASS. BOOT INTO RECOVERY USING VOL UP + HOME + POWER BUTTON.
Done.
Credits:
TWRP Team for their awesome recovery.
@RVR for testing recovery!
XDA:DevDB Information
TeamWin Recovery Project, ROM for the Samsung Galaxy A Series
Contributors
jackeagle
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 3.0.2.0
Stable Release Date: 2016-03-07
Created 2016-03-07
Last Updated 2016-05-25
Downloads
TWRP Build 1
TWRP Build 2 (V3.0.0)
TWRP v3.0.2.0 (Build 3)
TWRP v3.0.2.0 (Build 4)
Changelog
Code:
27/06/2016
- Added Compatibility for Samsung Marshmallow Firmware Release
- Merged with Samsung Marshmallow kernel release
- TWRP upstream merge.
25/05/2016
- Fixed Recovery Loop Issues.
- Fixed MTP Media Transfer on Recovery.
- Added EFS Partition Backup Option
- Fixed Brightness Slider
- Updated TWRP to latest v3.0.2.0
07/03/2016
- Updated TWRP to v3.0.0
20/11/2015
- Initial Release
Reserved 2
I need a custom recovery for Galaxy A8 (A800F) please.
Thanks
How to root Galaxy A700FD and install a recovery running on lolipop 5.0.2.
Developers please go for Samsung Galaxy A7 A700FD ..
Sent from my SM-A700FD using Tapatalk
Nice keep posting about A700FD
Sent from my SM-A700FD using Tapatalk
TWRP Link is dead.
TWRP updated to v3.0.0.
Links are in OP.
Enjoy!
jackeagle said:
TWRP updated to v3.0.0.
Links are in OP.
Enjoy!
Click to expand...
Click to collapse
build 2 is invalid ,help
nukedanoob said:
build 2 is invalid ,help
Click to expand...
Click to collapse
Use this link: https://www.androidfilehost.com/?fid=24438995911970888
and what if I can't flash because of secure boot enabled?
(in download mode there is a line "Qualcomm Secureboot - Enabled (CSB)" and "Write Protection - Enabled". I think this is the cause).
what should I do? any help appreciated.
nevermind. it was a faulty cable.
lifehijack said:
Use this link: https://www.androidfilehost.com/?fid=24438995911970888
Click to expand...
Click to collapse
thanks
A7000 want to twrp 3.0.0too
来自我的 SM-A7000 上的 Tapatalk
lifehijack said:
Use this link: https://www.androidfilehost.com/?fid=24438995911970888
Click to expand...
Click to collapse
works fine,just rename the file
Qualcomm Secure Boot is enabled and trying to flash recovery gives this message on phone
secure check fail : recovery
Custom Binary(recovery) Blocked by A/L
Odin says Fail
Solved: Disabled Reactivation Lock in security settings
Phone booting into recovery each time when I reboot the phone. How to come out of recovery mode boot loop?
Can i use it on my a7000?
Hello jackeagle, I ask you to continue the CM13 E5 project, I enjoyed the rom! If I can help in any way! even a my donation and my friends for you to continue the rom!
Always get kernel not seandroid enforcing .... i cannot boot to the system i just installed... just a blank screen
. .
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.*/
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.
Screenshots
Under screenshots tab
Installation
Odin flashable, go to download mode, connect to PC, run Odin, select 'PDA', select the twrp tar.md5, flash it.
Enjoy.
Downloads
Recovery
Recovery Updated New*
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
https://twrp.me/devices/samsunggalaxycoreprime3g.html?_e_pi_=7,PAGE_ID10,4826727325
Support:
Click http://webchat.freenode.net/?channels=twrp
for live support or join us in #twrp on Freenode IRC servers
Device Specific Source can be found in TeamButter repo.
very nice @Dreamstar
coool
Finally we have twrp for core prime G360H
Thanks for your effort
Good One
Thank you @Dreamstar !! Not only for root,but now for a working custom recovery.
Truly the 2 most important tools we could have for our phone.
help
can someone try to flash supersu ? su ?
newbidev001 said:
can someone try to flash supersu ? su ?
Click to expand...
Click to collapse
Yes flash supersu.zip it works
Good work
We need now CyangonMod for our device
Great
Great!!! Working well for me...
Hi
Hi im really new to this and im stuck .I get as far as adb devices and when i entre adb eboot recovery it no longer shows my device .So glad you have this root , but now i cant get beyond this
Thanks so much in advance !!!!
Geniusxd said:
Hi im really new to this and im stuck .I get as far as adb devices and when i entre adb eboot recovery it no longer shows my device .So glad you have this root , but now i cant get beyond this
Thanks so much in advance !!!!
Click to expand...
Click to collapse
You no need to install it with adb just flash it with odin ?
Thanks
Thank you very much
Anyone Help me i cant able to flash supersu.zip
Help please..
Can I update my recovery which is TWRP 2.8.7.1 to TWRP 3.0.0-0 ??
TIA
yup just open odin an flash recovery
Dreamstar said:
yup just open odin an flash recovery
Click to expand...
Click to collapse
Thanks. done it nice and easy. :good:
Problem Solved
Thanks
Working Prefect
Need cwm for backup.
Sent from my SM-G360H using XDA Free mobile app
you can take backup with twrp too
Changelog for 3.0.1-0:
Twrp 3.0.1.0 For G360H
Click to expand...
Click to collapse
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.
*
*/
BUG :
OTG
Lemme know
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Download: here
Contributors
imjyotiraditya
Thx to jjjhitel for his EROFS patch
Source Code: https://github.com/TeamWin/android_bootable_recovery
https://github.com/imjyotiraditya/device_xiaomi_odin-twrp
thanks and reserved
thanks and reserved
treid it this morning, and it looks and feels great so far.. no errors.
Would it be possible for somebody to post a guide for this, never installed it before?
jrvenge said:
Would it be possible for somebody to post a guide for this, never installed it before?
Click to expand...
Click to collapse
I'm not entirely sure what you mean tbh. Would you mind to explain?
imjyotiraditya said:
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.
*
*/
BUG :
OTG
Lemme know
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Download: here
Contributors
imjyotiraditya
Thx to jjjhitel for his EROFS patch
Source Code: https://github.com/TeamWin/android_bootable_recovery
https://github.com/imjyotiraditya/device_xiaomi_odin-twrp
Click to expand...
Click to collapse
Hey, i wanted to report a bug...
After i installed twrp permanently by advanced settings, i lost the touchscreen, after i rebooted into recovery.
SanHelios said:
Hey, i wanted to report a bug...
After i installed twrp permanently by advanced settings, i lost the touchscreen, after i rebooted into recovery.
Click to expand...
Click to collapse
how did u recover sir ? flashed original boot.img?
jrvenge said:
Would it be possible for somebody to post a guide for this, never installed it before?
Click to expand...
Click to collapse
as of now, no use of flashing twrp as there are no proper custom rom, but inorder to put this ur phone should be unlocked, to do that follow this guide https://forum.xda-developers.com/t/...to-eu-rom-and-root-guide-with-magisk.4338671/
vamsi209 said:
how did u recover sir ? flashed original boot.img?
Click to expand...
Click to collapse
Kinda... i booted the twrp-recovery bootimage by using
fastboot boot twrp.img
that brought me back to twrp and restored touchscreen-control. In twrp i formatted the device and completely wiped all partitions, so i would have a clean install. After all that was done i returned to bootloader and used the fastboot-image to clean-flash everything. I wanted to do this anyways, so no biggy.
It's still okay to use it, but installing it on the device as permanent recovery doesn't work as long as the touchscreen doesn't work at all.. but when this is fixed, go for it.
already did all of it...
vamsi209 said:
as of now, no use of flashing twrp as there are no proper custom rom, but inorder to put this ur phone should be unlocked, to do that follow this guide https://forum.xda-developers.com/t/...to-eu-rom-and-root-guide-with-magisk.4338671/
Click to expand...
Click to collapse
already did all of it...
SanHelios said:
Hey, i wanted to report a bug...
After i installed twrp permanently by advanced settings, i lost the touchscreen, after i rebooted into recovery.
Click to expand...
Click to collapse
Fixed!
Thanks for reporting..
vamsi209 said:
as of now, no use of flashing twrp as there are no proper custom rom, but inorder to put this ur phone should be unlocked, to do that follow this guide https://forum.xda-developers.com/t/...to-eu-rom-and-root-guide-with-magisk.4338671/
Click to expand...
Click to collapse
Phone is already unlocked as im running 21.9.28 lol
jrvenge said:
Phone is already unlocked as im running 21.9.28 lol
Click to expand...
Click to collapse
to just run this twrp, u can boot your device to bootloader, open terminal or powershell, and use command
fastboot boot twrp*.img
this will boot your twrp recovery,
as mentioned by @SanHelios there seems to be a small bug when u r flashing it permanently as recovery,
and the dev already got a fix for the same, he will mostly update the links tomorrow, i tested and it was working,
this is the file he provided, link, @SanHelios test this mate
download the above file,
use fastboot boot twrp*.img, and go to advance, and click on flash current twrp,
it will patch your boot.img file and flash the patched boot.img with twrp recovery
use volume up and power button combo to boot into twrp
imjyotiraditya said:
Fixed!
Thanks for reporting..
Click to expand...
Click to collapse
Thx for your awesome work, man..
I still dont get what it actually does lol
jrvenge said:
I still dont get what it actually does lol
Click to expand...
Click to collapse
You mean, the general function of TWRP?
yes
jrvenge said:
yes
Click to expand...
Click to collapse
TWRP is a well-rounded recovery for android-devices. There's a lot it can do, but basicly, you use it to flash/install software or images on your device. If there is a custom rom you wanna use, you flash it via TWRP, since the stock roms-recoveries only flash/install their associated roms. Apart from that, you can wipe or format your device, so it will be "clean" if you want to make a fresh installation.
In the past it was simple to install it, because devices were mostly A-only devices with a dedicated "recovery"-partition. To install it, the most common way was
- Boot into Fastboot mode, connect android via USB
- open computer CLI/Shell-window
- "fastboot flash recovery twrp.img" - Enter
The Mi Mix 4 is an A/B-Device, which means that the vital partitions are doubled and there's no "recovery"-partition anymore, since all recovery-functions are parked in a different partition. TWRP offers the ability to install itsself according to the A/B-Partitions-scheme and therefore becoming the new System-Recovery. Here the installation-steps are different.
- Boot into Fastboot mode, connect android via USB
- open computer CLI/shell-Windows
- "fastboot boot twrp.img" - Enter <- Starts the system using the image
- Touch Advanced
- Touch "Flash Current TWRP"
If a custom rom ever becomes available, there's certain routine you want to do...
backup vital information and files
format device
wipe all partitions
flash Firmware required
flash rom
flash Google Apps i.e. Open Gapps Project or NikGapps if available and desired
wipe dalvik-cache/cache/data
Enjoy
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.
#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/Recovery
* 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.
*
*/
Working Features:
- Decryption Works
- Backup works
- Wipes Work
- MTP
- ADB
- OTG
- RUI 2 ozip Flashing
- RUI 1 ozip flashing
Not Working:
- No f2fs support yet
- Not tested on CN variants (Can't confirm working status)
Flashing Guide:
Patched VBMETA is must to boot a twrp , so flash the below image to successfully boot this recovery and make it available even after booting back to RealmeUI.
Download Links:
TWRP Download Link
VBMETA Link
To flash TWRP:
fastboot flash recovery twrp-3.6-RUI2-RMX1931-final.img
Flash the VBMETA using below commands
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_path.img
ADB and Fastboot Drivers:
ADB and Fastboot Installer
Source code:
https://github.com/TeamWin/android_bootable_recovery
https://github.com/arnodorian-r/recovery_realme_RMX1931
https://github.com/arnodorian-r/kernel_realme_sm8150
Credits:
Thanks to @mrtechnophile2.0 , Roy for the testing
Thanks @pjgowtham @XiaoAk for guiding me
The best thing ever happened for realme ui 2. Great work mate..!
Finally, a proper working Recovery for our device
Wow...Finally Working TWRP for RMX1931 on RUI2.
Thanks alot bro.
Can I flash this, when I'm on Lineage-18.1?
zheka99 said:
Can I flash this, when I'm on Lineage-18.1
Click to expand...
Click to collapse
Technically its possible...but you should do it after roms released based on rui2 firmware. If not , you will endup with broken OS. For now dont flash custom roms with this recovery.
can i flash magysk to optine root, wich version?
Isavar said:
can i flash magysk to optine root, wich version?
Click to expand...
Click to collapse
Magisk-92546e8a(23016) from CANARY all Ok!
Sorry for my English. And thank you very much for your work. I have the mobile with the latest version of rui2 and with root done following this guide:
https://forum.xda-developers.com/t/...fix-rui-2-0-android-11-global-indian.4371041/ When I went to install twrp, the mobile only started in twrp , and I had to reinstall everything. I used realme flashtool and refollowed the guide to get me back up and running properly. What could have happened?
Leozgz85 said:
Sorry for my English. And thank you very much for your work. I have the mobile with the latest version of rui2 and with root done following this guide:
https://forum.xda-developers.com/t/...fix-rui-2-0-android-11-global-indian.4371041/ When I went to install twrp, the mobile only started in twrp , and I had to reinstall everything. I used realme flashtool and refollowed the guide to get me back up and running properly. What could have happened?
Click to expand...
Click to collapse
Hi
was the same for me, had to reinstall everything, only started in TWRP. Would like to install the recovery but I don't feel like this error anymore.
Thanks. It's working.
Doesnt work for me, i cant boot to realme ui after flashing the vbmeta, i got stuck on recovery. (f.14)
This recovery is broken for me, it gives me no space left on sdcard even after a full data reformat, ozip extraction stops after 500mb.
It's just not working as it should 3.4 works best
arnodorian-r said:
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.
#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/Recovery
* 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.
*
*/
Working Features:
- Decryption Works
- Backup works
- Wipes Work
- MTP
- ADB
- OTG
- RUI 2 ozip Flashing
- RUI 1 ozip flashing
Not Working:
- No f2fs support yet
- Not tested on CN variants (Can't confirm working status)
Flashing Guide:
Patched VBMETA is must to boot a twrp , so flash the below image to successfully boot this recovery and make it available even after booting back to RealmeUI.
Download Links:
TWRP Download Link
VBMETA Link
To flash TWRP:
fastboot flash recovery twrp-3.6-RUI2-RMX1931-final.img
Flash the VBMETA using below commands
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_path.img
ADB and Fastboot Drivers:
ADB and Fastboot Installer
Source code:
https://github.com/TeamWin/android_bootable_recovery
https://github.com/arnodorian-r/recovery_realme_RMX1931
https://github.com/arnodorian-r/kernel_realme_sm8150
Credits:
Thanks to @mrtechnophile2.0 , Roy for the testing
Thanks @pjgowtham @XiaoAk for guiding me
Click to expand...
Click to collapse
I followed this guide and many others in the past 48 hours, with no success. Every time I flash TWRP and the VBMETA, I get stuck in TWRP bootloop.
I started unblocking the bootloader, rolling back to RUI1 - Android 9 and using the Deep-Test App.
After the roll back, I got the phone unblocked right, but then first soft-brick, with only bootloader available and no way to flash a working ROM. After some searches, I've finally managed to unbrick, using OPPO flash tool, and installing stock rom RMX1931_11_F.14_2021102817443142.
This gives me a working phone, RUI.2 - Android 11. Standard recovery.
I tried to flash TWRP and got the phone soft bricked again, in TWRP recovery bootloop.
I'd like to install TWRP and from there going to OrangeFox and finally install Lineage 19.1...
How can i first have a working TWRP recovery??? If you can support also following steps, would be amazing. Thank you!!!
I went few step further... but still I am not able to install a working custom recovery for my realme X2 pro.
I have now also rooted my device with magisk.
I just need a custom recovery to perform 2 actions:
- make a NANDroid backup;
- install a custom ROM.
Any advice? Thank you for your time!
Installed. Working like a charm with lineage 19.1. Only problem: can't access files in storage. Digging into the matter, it seems to be an issue with android 12's new encryption method, which can't be overriden by this version of the recovery. There's a brand new TWRP 3.7.0_9.0 in the official TWRP website which boasts to overcome this problem but, whenever I try to install it (with or without the vbmeta.img provided for version 3.6.0_11), the recovery won't start. Guess a new vbmeta.img is needed as everything goes ok reinstalling TWRP 3.6.0_11 and its corresponding vbmeta. Tried to extract and install vbmeta.img from the lineage zip file without success. Shall we have to patch vbmeta.img? How can we do that? Through Magisk? I've come across some "vbmeta patcher" apk... Am I pointing the right way?
can any one help me to unlock bootloader in realme x2 pro . i am on RUI 10 . i installed in depth tool it said seccesful but no bootloader just keep rebooting and showing fast boot for a moment .. help please i search every where for fix but no way to yet
I'm using the CN variant device, which I understand does not yet have confirmed support, nonetheless sharing the error I'm encountering in case it's a simple or obvious fix I'm missing.
Having followed all above steps, I'm able to flash and get into TWRP recovery, but decryption always failed (even after a dozen tries) with the following:
"Attempting to decrypt FBE for user 0...
Failed to decrypt user 0"
Much obliged for any insight on this. I'm attempting to get back on OF after successfully installing Lineage 19.1, which broke the OF recovery, and since OF needs to be installed as a ZIP, I need to get some version of TWRP working as an intermediary. Specifically this is because I didn't install GAPPS along with Lineage 19.1 (I misread the opening post, which seemed to imply that GAPPS was included in that particular ROM). So alternatively, if there's another way to get GAPPS onto the device without recovery (sideload won't work since I can't decrypt...) then that would be helpful too.
Thanks in advance for any insight on this!