Related
Latest TWRP version for Optimus G [E975/F180X]
What is new in 2.8.7.0:
Code:
Initial ground work for software drawn keyboard (_that)
Fix handling of wiping internal storage on datamedia devices (xuefer)
Allow DataManager to set and read values from the system properties (xuefer)
Fix crash when taking screenshots on arm64 devices (xuefer)
Fix error message after an ORS script completes (Dees_Troy)
Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
Add system read only option – more details below (Dees_Troy)
Add resize2fs and GUI option to run resize2fs (Dees_Troy)
Fix crash loop caused by empty lines in AOSP recovery command file (_that)
Prevent duplicate page overlays such as multiple lock screens (mdmower)
Download:
TWRP v2.8.7.0
How to install:
Code:
- turn your phone into bootloader mode
- connect phone with pc
- using fastboot flash recovery "fastboot flash recovery recovery.img"
- reboot
Screenshot:
Credits:
Omni Team
Kevinjoa
XDA:DevDB Information
TW, Tool/Utility for the LG Optimus G
Contributors
DevSwift1
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Beta
Created 2015-07-18
Last Updated 2015-07-18
good job
Sir Devswift1
I got a problem. I bump philz & cwm for optimus g locked bootloader & go to them easily with hardreset.
But for twrp, every time I try to go to it, it performs a factory reset!
Can you please make one without this problem?
So we can use all kinds of recovery with bump...
M.M.K said:
Sir Devswift1
I got a problem. I bump philz & cwm for optimus g locked bootloader & go to them easily with hardreset.
But for twrp, every time I try to go to it, it performs a factory reset!
Can you please make one without this problem?
So we can use all kinds of recovery with bump...
Click to expand...
Click to collapse
This recovery support only unlocked bootloader..
about flash my AOSP rom you can try with cwm but I am not sure if all will be working
DevSwift1 said:
This recovery support only unlocked bootloader..
about flash my AOSP rom you can try with cwm but I am not sure if all will be working
Click to expand...
Click to collapse
Actually I have used your twrp. But only with reboot to recovery through running os!
Then it wont perform factory reset. But what if I get bootloop?anytime? Kdz...
I mean thats how G3 users enter to twrp! But we cant!
I hoped you could fix it Please try
Thank you anyway. I'm gonna flash your perfect rom with unlocked boot loader
Try Jollaman twrp.
Also Jollaman twrp is multirom compatible.
Enviado do meu Optimus G através de Tapatalk
Hey im new to this how i install this i used before to unlock boot via freegee?
the download link is broken
mi_guel69 said:
the download link is broken
Click to expand...
Click to collapse
Flashable zip - dont remember who made it sorry
http://www.multiupfile.com/f/02f8982a
Pls, fix link at the top. Thx
this is very old now... use this https://mirrors.c0urier.net/?dir=android/Dadi11/TWRP
DisclaimerThis software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [filename].img --> ex: fastboot flash recovery_ramdisk twrp_p10_lite_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9.
Contributors
**** Pretoriano80
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
**** @Tecalote - He was the main tester for the Mate 9
**** @Blackball
**** @Eurofighter_ty for testing on P10 Lite
**** Team OpenKirin - thanks for the "Oem Path wipe esclusion" code
Download links
twrp_p10_lite_0.1.img - initial release,OTG connection not working
twrp_p10_lite_0.2.img - minor fixes,OTG connection should be fixed (please test and report)
twrp_p10_lite_0.3.img - OTG is now fixed
twrp_p10_lite_0.4.img - fixed mount issues
Why after entering into TWRP I got "Mount Decrypt Data" menu and ask me for some password? What is this?
Then I press Cancel because I don't know what is this menu.
Also I can't make any backups because I got an error: "Failed to unmount '/data' (device or resource busy)" and "Failed to unmount '/system' (device or resource busy)"
Something is wrong with this TWRP.
Aalesund said:
Why after entering into TWRP I got "Mount Decrypt Data" menu and ask me for some password? What is this?
Then I press Cancel because I don't know what is this menu.
Also I can't make any backups because I got an error: "Failed to unmount '/data' (device or resource busy)" and "Failed to unmount '/system' (device or resource busy)"
Something is wrong with this TWRP.
Click to expand...
Click to collapse
Obviously it's asking for password, otherwise it couldn't decrypt the internal storage.
You have to use the same password/pin/pattern that you use in Android.
The feature Internal Storage Decryption is really cool!
And this TWRP has better compatibility with magisk, at last I can use recovery mode for mm.
Thanks!
The problem of not being able to unmount /system means that it'll always be mount read-only, which then means unless a whole system image is flashed, no modifications can be made to /system. This is the only gripe I have about this TWRP; otherwise it works brilliantly.
AndyYan said:
The problem of not being able to unmount /system means that it'll always be mount read-only, which then means unless a whole system image is flashed, no modifications can be made to /system. This is the only gripe I have about this TWRP; otherwise it works brilliantly.
Click to expand...
Click to collapse
Yes, that's right - I saw the issue with keeping system ready only yesterday night on Huawei Mate 10 Lite.
This TWRP works except this also brilliantly on Mate 10 Lite
i tried to flash my emui 5 p10lite with no success:
#
Code:
fastboot flash recovery_ramdisk ./twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24952 KB)...
OKAY [ 3.186s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 3.194s
dlewando said:
i tried to flash my emui 5 p10lite with no success:
#
Code:
fastboot flash recovery_ramdisk ./twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24952 KB)...
OKAY [ 3.186s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 3.194s
Click to expand...
Click to collapse
It only works on EMUI 8.
Tecalote said:
Yes, that's right - I saw the issue with keeping system ready only yesterday night on Huawei Mate 10 Lite.
This TWRP works except this also brilliantly on Mate 10 Lite
Click to expand...
Click to collapse
Here's a test build,i hope that system unmount issue is fixed -- > https://mega.nz/#!AscFxY5R!UdDKb-FIlZI2rjJyCZiMu2er1-HnTWdKYJfGpAoGJdM
Pretoriano80 said:
Here's a test build,i hope that system unmount issue is fixed -- > https://mega.nz/#!AscFxY5R!UdDKb-FIlZI2rjJyCZiMu2er1-HnTWdKYJfGpAoGJdM
Click to expand...
Click to collapse
Same deal unfortunately. Device is a Honor 7X, btw.
AndyYan said:
Same deal unfortunately. Device is a Honor 7X, btw.
Click to expand...
Click to collapse
Well, my magic crystal ball is broken so i will need logs this time.Next time please grab recovery.log and dmesg, otherwise i will start ignoring all these "not working" posts.
Pretoriano80 said:
Well, my magic crystal ball is broken so i will need logs this time.Next time please grab recovery.log and dmesg, otherwise i will start ignoring all these "not working" posts.
Click to expand...
Click to collapse
Done.
I'd need to know how to help (what logs you need) before I do so, no?
AndyYan said:
Done.
I'd need to know how to help (what logs you need) before I do so, no?
Click to expand...
Click to collapse
Just had a quick look, which device you were using to get the logs, it doesn't seem to be a Honor 7x?!
Pretoriano80 said:
Just had a quick look, which device you were using to get the logs, it doesn't seem to be a Honor 7x?!
Click to expand...
Click to collapse
Weird, I didn't have another device at hand when I was taking the logs, I'm fairly certain that it's from my 7X. I do see it mention this in the recovery.log:
Code:
persist.radio.current_version=BND-AL10 8.0.0.331(C00)
I captured logs again just in case.
I was on Oreo beta B331 and am now on LineageOS Treble GSI, if that matters.
AndyYan said:
Weird, I didn't have another device at hand when I was taking the logs, I'm fairly certain that it's from my 7X. I do see it mention this in the recovery.log:
I captured logs again just in case.
I was on Oreo beta B331 and am now on LineageOS Treble GSI, if that matters.
Click to expand...
Click to collapse
As far as i can see, your device is not encrypted! Also, custom roms are not supported yet. I will have a look later, after work, but loke i said, from logs is seems that your storage is not encrypted.
Pretoriano80 said:
As far as i can see, your device is not encrypted! Also, custom roms are not supported yet. I will have a look later, after work, but loke i said, from logs is seems that your storage is not encrypted.
Click to expand...
Click to collapse
Yes, I have modified fstab in vendor to disable storage encryption on /data (various reasons); I don't see how that's related to not being able to mount /system properly, however.
Probably the other guy who reported a similar problem would be able to get you the "clean" logs you need.
AndyYan said:
Yes, I have modified fstab in vendor to disable storage encryption on /data (various reasons); I don't see how that's related to not being able to mount /system properly, however.
Probably the other guy who reported a similar problem would be able to get you the "clean" logs you need.
Click to expand...
Click to collapse
I already know why it's happening in your case, the cause being the unencrypted storage. This TWRP was especially created to support encryption, otherwise there's already official TWRP without encryption support.
However, your logs are still useful! ?
Pretoriano80 said:
I already know why it's happening in your case, the cause being the unencrypted storage. This TWRP was especially created to support encryption, otherwise there's already official TWRP without encryption support.
However, your logs are still useful!
Click to expand...
Click to collapse
Pardon me, but which official? I don't see 7X / P10Lite / M10Lite on official TWRP site.
AndyYan said:
Pardon me, but which official? I don't see 7X / P10Lite / M10Lite on official TWRP site.
Click to expand...
Click to collapse
Oh, my bad, i thought someone already ported TWRP from Mate 10 Pro.
I might be able to fix system unmount issue with unencrypted devices, but i will need your help with testing cause i only have a Mate 10 Pro and it's encrypted. The best solution would be to add a workaround in the current version without building a new one for unencrypted devices.
Pretoriano80 said:
Oh, my bad, i thought someone already ported TWRP from Mate 10 Pro.
I might be able to fix system unmount issue with unencrypted devices, but i will need your help with testing cause i only have a Mate 10 Pro and it's encrypted. The best solution would be to add a workaround in the current version without building a new one for unencrypted devices.
Click to expand...
Click to collapse
I had for some days Mate 10 Lite - rebranded it from c432 to c185 on Android 7 (cause there was not Oreo-Update available for c432) and updated the phone to Oreo with Nocheck Recovery. I tested your TWRP for P10 Lite for Mate 10 Lite - on Stock its working pretty good. I had not any issues.
The owner of the phone like to have a Stock based Custom Rom, I flashed it and tested 3 different TWRPs.
The Dev of the Rom made one, but it does not working properly - Backup /restore without data is only possible on internal storage, no permission to external SD.... Same with two others.
Your TWRP had only issues with data (cause of the modified vendor/etc/fstab.hi6250 - avb and encryption disabled) and issues with system mount/unmount on Custom Rom. But on Stock Rom no issues.
Here are some Logs (from your TWRP). I had not time before to post it
Introduction:
Team Win Recovery Project or TWRP 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
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Poco F3/Mi 11X/Redmi K40
touch and adb work
flashing works
USB OTG works
Decryption is working
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
3. select the new image
4. after that is done, if you were using a custom kernel, reflash it now
5. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_alioth
https://github.com/TeamWin/android_device_xiaomi_sm8250-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomipocof3.html
Unofficial android 12 builds: https://www.pling.com/p/1836619/
mirror: https://store.kde.org/p/1836619/
Thanks for your hard work
All function has usable especially decryption.
Thank you mate!! That's is very important for all the community .What version of magisk i have to install??But you mean flash the zip of magisk??Thanks.
Awesome, mate!
I've been waiting for this, thank you sir for your contribution!
@Nebrassy Nice work - tested on my crDroid working-build and all ok
I only can say thank you a lot!! I'll buy a beer
"Failed to mount /data (Invalid argument) :/ Im on HentaiOS btw
reas0n said:
"Failed to mount /data (Invalid argument) :/ Im on HentaiOS btw
Click to expand...
Click to collapse
I believe that rom has customized encryption, so it's not supported
Nebrassy said:
I believe that rom has customized encryption, so it's not supported
Click to expand...
Click to collapse
Damn.. I will wait for any officially supported custom ROM then so I could just get OTAs, I dont want to do another wipe and setup lol. thx anyway
raystef66 said:
@Nebrassy Nice work - tested on my crDroid working-build and all ok
Click to expand...
Click to collapse
your what?
raystef66 said:
@Nebrassy Nice work - tested on my crDroid working-build and all ok
Click to expand...
Click to collapse
Not shared as yet?
arifqur said:
Not shared as yet?
Click to expand...
Click to collapse
Not yet. Won't take long though when first release will be posted in development.
this works "out of the box" for poco f3 with miui 12.x?
Thank you
Henkl said:
this works "out of the box" for poco f3 with miui 12.x?
Click to expand...
Click to collapse
answering my own question: you have to unlock the phone first with MIUI unlock tool.
AND unlocking involves wiating on part of xiaomi site afer registering ...can be even 7 days..
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
lejeanlouisF said:
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
Click to expand...
Click to collapse
So it asked for password, did you enter it?
As for magisk, just flash latest magisk apk with twrp
lejeanlouisF said:
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
Click to expand...
Click to collapse
The password is ur security PIN for unlocking ur phone.
No idea about backuping the boot.img in TWRP (I am not using it )
Nebrassy said:
So it asked for password, did you enter it?
As for magisk, just flash latest magisk apk with twrp
Click to expand...
Click to collapse
I have entered a password but it failed. Is it a free password ?
EDIT : It's ok, sorry. the security PIN, of course !!!
EDIT 2 : And Thank you very much for your work and your help
When I Use Twrp the data folder automatically locks itself and I tried many passwords but it won't open. Then I delete all the data and flash new rom with decrytion file flashing but still the decrytion is temporary and whenever I update my custom rom it strucks in boot loop... I want permanent Decryption someone please help to decrypt my Mi 11x.
AFAIK there is no way around this. You must flash DFE (Disable-Force-Encryption) after every update to avoid bootloops/encryption.
(in my experience, if I forget to re-flash DFE after an OS update, it just doesn't start anymore, only bootloops.)
This is because OS Updates replace system-files, including the text-file which, by default, contains the line for AES-encryption.
I think the DFE-Mod sets the system to read-write (if it's read-only), and removes the AES-encryption argument in a specific text-file.
cyanGalaxy said:
AFAIK there is no way around this. You must flash DFE (Disable-Force-Encryption) after every update to avoid bootloops/encryption.
(in my experience, it just doesn't start anymore, if I forget to re-flash DFE after an OS update)
This is because OS Updates replace system-files, including the text-file which, by default, contains the line for AES-encryption.
I think the DFE-Mod sets the system to read-write (if it's read-only), and removes the AES-encryption argument in a specific text-file.
Click to expand...
Click to collapse
Is there any way to know my data encryption password because if I know it I do not need to decrypt it using file anymore?
Ishan.Sharma said:
Is there any way to know my data encryption password because if I know it I do not need to decrypt it using file anymore?
Click to expand...
Click to collapse
Oh yes, I remember now. You are using Android 12, yes?
Use "TWRP skkk", it's a special version that supports Android 12's Encryption.
I think OrangeFox also has a version that supports Android 12's Encryption...
YouTube Video:
Download Link for unofficial TWRP skkk: https://dl.akr-developers.com/?dir=skkk/TWRP/A12
I found both the video and the download link from here: https://forum.xda-developers.com/t/...p-3-6-0_11-v2-9-3_a11-alioth-skkk-is.4373463/
I use it myself and it works.
cyanGalaxy said:
Oh yes, I remember now. You are using Android 12, yes?
Use "TWRP skkk", it's a special version that supports Android 12's Encryption.
I think OrangeFox also has a version that supports Android 12's Encryption...
YouTube Video:
Download Link for unofficial TWRP skkk: https://dl.akr-developers.com/?dir=skkk/TWRP/A12
I found both the video and the download link from here: https://forum.xda-developers.com/t/...p-3-6-0_11-v2-9-3_a11-alioth-skkk-is.4373463/
I use it myself and it works.
Click to expand...
Click to collapse
Ok thanks
I bought my poco few months ago and it is still locked, with my old phone i removed the encription simply formatting (not wiping) the internal storage with TWRP. Is this still working with the poco?
massima said:
I bought my poco few months ago and it is still locked, with my old phone i removed the encription simply formatting (not wiping) the internal storage with TWRP. Is this still working with the poco?
Click to expand...
Click to collapse
No, Android encrypts the data-partition using AES-algorithm on first boot, unless before the first boot you flash a script that removes the Encryption-argument.
Hey folks OrangeFox Recovery is finally here for OnePlus Nord (avicii)...
THIS RECOVERY WILL SUPPORT STOCK ROMS, FBEv1 CUSTOM ROMS, FBEv2 CUSTOM ROMS.
DISCLAMER
Your warranty is now void.
I am not responsible for any damage that is made due to this action.
{
"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"
}
"If the device is encrypted, then you must format the data partition (NOTE: format - not just wipe). If the device is not encrypted, then you can just wipe the data partition (ie, no need to format)"
-source wiki.orangefox.tech
KNOWN ISSUE FOR FBEv1 Recovey : DATA BACKUP AND RESTORE NOT WORKING
DATA DECRYPTION NOT WORKING FOR SOME ROMS
KNOWN BUG FOR 00S12 Recovery (0.1%) : DATA BACKUP AND RESTORE WORKS, BUT HAVEN'T FOUND A PERFECT WAY TO RESTORE AND MAKE THE PHONE FULLY WORKING. IF YOU ARE FREE PLEASE CONSIDER TO FIND A WAY TO PERFECTLY BACKUP AND RESTORE OOS12 ROM DATA PARTITION
Note: Only boot and work with OOS12, never try to flash with FBEv1 or FBEv2 roms, if you do so, your device will face a softbrick. Similarly donot try FBEv1 or FBEv2 recoveries with OOS12. This is due to the mismatch in firmwares of OOS12 and other roms
If flashing rom from OOS12 variant, after installing custom rom, flash FBEv1, FBEv2 recovery accordingly. And vice versa
To flash OOS12 OTA (Only available from R11.1_3 onwards)
I added 2 scripts inside the recovery.
Before flashing OOS12 OTA
Go to terminal
Type and press enter
sh /system/bin/pre_oos_flash.sh
You will see an error "kPostinstallError" : just ignore it.
After flashing OOS12 OTA
Go to terminal
Type and press enter
sh /system/bin/post_oos_flash.sh
Then switch slot to updated slot
Downloads :
For FBEv1 Custom Roms :
OrangeFox Recovery R11.1_2 (Image File)
OrangeFox Recovery R11.1_2 (Flashable Zip Installer)
For OOS12 Rom:
OrangeFox Recovery R11.1_3 (Image File)
OrangeFox Recovery R11.1_3 (Flashable Zip Installer)
For FBEv2 Custom Roms :
OrangeFox Recovery R11.1_2 (Image File)
OrangeFox Recovery R11.1_2 (Flashable Zip Installer)
Guide to flash recovery :
• Reboot to FASTBOOT
• Connect your phone via USB to PC
• Open Command Prompt (You must install ADB and fastboot platform files) and type
• Only to boot the recovery
fastboot devices
fastboot boot <path to recovery image file>
• To flash recovery
fastboot devices
fastboot flash recovery <path to recovery image file>
Special Thanks to
OrangeFox Recovery Project
@DarthJabba9
@Wishmasterflo
@lordfinix
For People residing inside India
UPI :- [email protected]
For People residing outside India
Paypal
CHANGELOG (16/11/2022) - R11.1_3_OOS12
1) Initial Build
2) Support OOS12
3) 99.9% Features work
CHANGELOG (16/11/2022) - R11.1_2_FBEv1
1) Initial Build
2) Toggle Flashlight FIxed
3) Screen Ratio Fixed
4) Notch Positioning Fixed
5) Added CPU Temperature Monitor
6) Slot Switching Fixed
CHANGELOG (16/11/2022) - R11.1_2_FBEv2
1) Fixed Data Partition Backup & Restore
2) Fixed Data Partition Wipe
CHANGELOG (13/11/2022) - R11.1_1_FBEv2
1) Initial Build
2) Data Decryption Fixed
3) Toggle Flashlight FIxed
4) Screen Ratio Fixed
5) Notch Positioning Fixed
6) Added CPU Temperature Monitor
7) Slot Switching Fixed
Can you do one for a12 coloros?
skia16 said:
Can you do one for a12 coloros?
Click to expand...
Click to collapse
Ys. But require few edits. I need to build another separate version for Oxygen OS, Color OS and some other custom roms since they use FBEv1 file encryption.
Works super good! one of GOAT recoveries
@Sreeshankar K
Thanks for this great recovery! It´s working like a charm on my device.
One question: is it able to decrypt data/internal storage? I have a pattern, but there is no option in decryption to use this or am I wrong? I´m on Lineage OS 19.1.
gllark said:
@Sreeshankar K
Thanks for this great recovery! It´s working like a charm on my device.
One question: is it able to decrypt data/internal storage? I have a pattern, but there is no option in decryption to use this or am I wrong? I´m on Lineage OS 19.1.
Click to expand...
Click to collapse
Probably Lineage OS 19.1 is FBEv1 ROM. This recovery only support FBEv2 ROMs. I had mentioned it in the post. Currently no support for FBEv1 ROMs. If u want fully functioning recovery please go to the telegram group mentioned in the XDA post.
And also thanks for ur positive comment
Wasn't able to decrypt the data partition with LOS 18.1 and the FBEv1 version.
And now after booting, Bluetooth is no more starting/working.
It's doesn't turn on, it goes back to off every time.
Had this problem also in the past with the OFRP from the other thread.
Edit: was able to fix the Bluetooth problem with: restorecon -R /data
Doc Sniper said:
Wasn't able to decrypt the data partition with LOS 18.1 and the FBEv1 version.
And now after booting, Bluetooth is no more starting/working.
It's doesn't turn on, it goes back to off every time.
Had this problem also in the past with the OFRP from the other thread.
Edit: was able to fix the Bluetooth problem with: restorecon -R /data
Click to expand...
Click to collapse
Lemme check with lineage os 19.1. both 18.1 and 19.1 are FBEv1
Doc Sniper said:
Wasn't able to decrypt the data partition with LOS 18.1 and the FBEv1 version.
And now after booting, Bluetooth is no more starting/working.
It's doesn't turn on, it goes back to off every time.
Had this problem also in the past with the OFRP from the other thread.
Edit: was able to fix the Bluetooth problem with: restorecon -R /data
Click to expand...
Click to collapse
I checked it on superior os which is FBEv1. And data partition was successfully decrypted
Sreeshankar K said:
I checked it on superior os which is FBEv1. And data partition was successfully decrypted
Click to expand...
Click to collapse
Strange, because here the decryption doesn't work.
The partition was once encrypted by LOS 18.1, hence probably FBEv1.
Also tried the FBEv2 recovery, but as expected no decryption dialog appears.
Thanks for testing and also creating the recovery.
Do we have any other options to test or fix this?
Doc Sniper said:
Strange, because here the decryption doesn't work.
The partition was once encrypted by LOS 18.1, hence probably FBEv1.
Also tried the FBEv2 recovery, but as expected no decryption dialog appears.
Thanks for testing and also creating the recovery.
Do we have any other options to test or fix this?
Click to expand...
Click to collapse
Ys not working. It was the first build of FBEv1 recovery released yesterday. I will check it.. Thanks for testing it. I go through the logs found that FBE decrypt setup is working fine but it cannot decrypt metadata partition.
Sreeshankar K said:
Ys not working. It was the first build of FBEv1 recovery released yesterday. I will check it.. Thanks for testing it. I go through the logs found that FBE decrypt setup is working fine but it cannot decrypt metadata partition.
Click to expand...
Click to collapse
This could possibly cause the Bluetooth problem, because the SELinux permissions don't seem to match after trying to decrypt data.
In any case, it's great that you're taking the time to look for the problem and fix it. Thanks.
Doc Sniper said:
This could possibly cause the Bluetooth problem, because the SELinux permissions don't seem to match after trying to decrypt data.
In any case, it's great that you're taking the time to look for the problem and fix it. Thanks.
Click to expand...
Click to collapse
Recovery settings and rom settings have no connections. Recovery only look for the fstab of rom to do the operations like wipe, install, backup and restore etc. Idk why that prob is appeared
Sreeshankar K said:
Ys not working. It was the first build of FBEv1 recovery released yesterday. I will check it.. Thanks for testing it. I go through the logs found that FBE decrypt setup is working fine but it cannot decrypt metadata partition.
Click to expand...
Click to collapse
Any news ?
Tried booting then flashing the R11.1_2_FBEv1 build using the fastboot manual flash, with OOS F17 EU (the latest for my device at the time of writing), it doesn't boot and just show the "boot/recovery destroyed" screen, any idea why?
Phone was also not booting after the flash, stuck on the "destroyed" screen, and I had to reflash the boot.img (no, I did not flash over boot, I double checked that I did specify recovery_a/_b when flashing)
WORMSTweaker said:
Tried booting then flashing the R11.1_2_FBEv1 build using the fastboot manual flash, with OOS F17 EU (the latest for my device at the time of writing), it doesn't boot and just show the "boot/recovery destroyed" screen, any idea why?
Phone was also not booting after the flash, stuck on the "destroyed" screen, and I had to reflash the boot.img (no, I did not flash over boot, I double checked that I did specify recovery_a/_b when flashing)
Click to expand...
Click to collapse
It is bcoz, OOS12 firmware doesn't support other custom kernels, firmwares etc
Sreeshankar K said:
It is bcoz, OOS12 firmware doesn't support other custom kernels, firmwares etc
Click to expand...
Click to collapse
Isn't "For Stock Roms (Oxygen OS and Color OS) & FBEv1 Custom Roms" a bit misleading then? Since it mention OOS and it being "For Stock Roms"
Tried out the new OOS12 option, works like a charm! Both the img and the zip!
I haven't tested everything but decryption, usb mounting, usb_otg, backups, sideloading and a lot more works perfectly!
I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything
Finally a proper working recovery for the Nord!
WORMSTweaker said:
Tried out the new OOS12 option, works like a charm! Both the img and the zip!
I haven't tested everything but decryption, usb mounting, usb_otg, backups, sideloading and a lot more works perfectly!
I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything
Finally a proper working recovery for the Nord!
Click to expand...
Click to collapse
Data backup and restore is buggy, means not saying that it is not working, haven't found a correct way to restore the backup of data partition, so if you have time please found a correct way to restore data partition, and post it here. Data decryption and all other features work.
[RECOVERY] [13] [UNOFFICIAL] TeamWin Recovery Project (8T / 9R) (2022-07-27)
Introduction: Team Win Recovery Project or TWRP 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...
forum.xda-developers.com
Like this we also need correct way to backup and restore data partition, so, if your are free do it.
WORMSTweaker said:
Tried out the new OOS12 option, works like a charm! Both the img and the zip!
I haven't tested everything but decryption, usb mounting, usb_otg, backups, sideloading and a lot more works perfectly!
I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything
Finally a proper working recovery for the Nord!
Click to expand...
Click to collapse
"I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything "
This is bcoz your data partition is not decrypted. Decrypt it using your rom password then everything will be normal. That's not a bug... Bug is in the restoration of backuped data. Actually not a bug. Didn't found a fully working way.
Need to find a perfect way to restore. OOS12 data restore is bit painful.
Take a look on data backup and restore
if you are free
Thank you