[RECOVERY] TeamWin Recovery 2.7.1.0 for GT-I9195 [2014-06-14] - Galaxy S 4 Mini Original Android Development

{
"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 your information
Team Win Recovery Project 2.7, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
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.
*/
This is developed for the LTE version of Samsung Galaxy S4 Mini (GT-I9195), but it may on the other variants.
I'll only support this variant since it's the only one I own, that means I can only test software for it, and on the way that I'll never give support or bugfixes for any other model.
Changelog
2014-06-14
- Merged latest kernel changes by arco.
- Upstream update to TWRP 2.7.1.0 (For more info, check official changelogs: http://teamw.in/project/twrp2).
2014-03-16
- Fixed flashing builds of any android version older than 4.4
- Merged latest kernel changes by arco.
- Upstream update to TWRP 2.7.0.0 (For more info, check official changelogs: http://teamw.in/project/twrp2).
2014-02-20
- Fixed 4.1+ data encryption/decryption support.
- Corrections of the screen timeout behaviour.
- Some upstream fixes and features like:
a) Support for mouse control (not tested here at all).
b) Vibration when touching screen or buttons (can be disabled).
c) And more...
2013-12-29
- First version
Reporting Bugs
If you want to report bugs please read THIS HOWTO first. Please try to provide logs if you see errors (logs and dmesg). If you don't know how to do that check google or ask people here to help you.
- To take logs you can use the option "Copy log to SD" inside recovery "Advanced" menu
- To grab a dmesg (if the recovery is not booting normally), just reboot on android system and provide the output of this command run from the adb shell:
Code:
cat /proc/last_kmsg
Download
You are storing very sensitive information on your phone. You always have to be careful with what you flash and who you trust on. If you don't trust me then don't use my work or compile it from source yourself.
Two files are provided, the .tar one is only flashable over Odin, but the .img one could be flashed using Heimdall and also using a shell command as below after pushing the file to the sdcard renamed to recovery.img (root access on the device is needed).
Make sure you do not make any typos writting this command, because is an easy and fast way of briking your device:
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
You can download the recovery here.
If you are going to host my builds somewhere else, please let me know that on this thread or over PM, so I can add the link here also
Sources
The source of the kernel is this one, compiled along android 4.4.2 codebase of OmniROM and using the default gcc 4.7 compiler:
https://github.com/OliverG96/android_kernel_samsung_serranoltexx
The flags used for TWRP settings are the ones below (full device tree might be avalaible soon, WIP on cleaning up):
TW_HAS_DOWNLOAD_MODE := true
TW_NO_REBOOT_BOOTLOADER := true
DEVICE_RESOLUTION := 540x960
RECOVERY_GRAPHICS_USE_LINELENGTH := true
TW_NO_SCREEN_BLANK := true
TW_BRIGHTNESS_PATH := "/sys/devices/platform/mipi_samsung_oled.1281/lcd/panel/backlight"
TW_MAX_BRIGHTNESS := 255
TW_INCLUDE_JB_CRYPTO := true
TW_NO_USB_STORAGE := true
RECOVERY_SDCARD_ON_DATA := true
TW_INTERNAL_STORAGE_PATH := "/data/media/0"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"
Credits
- Arne Coucheron
- Dees_Troy and bigbiff

Can I flash CM11 Rom with this Recovery?

TacoLoco said:
Can I flash CM11 Rom with this Recovery?
Click to expand...
Click to collapse
hello
yes you can

yannickamet said:
hello
yes you can
Click to expand...
Click to collapse
Are you sure? In other TWRP 2.6.3.0 thread OP says:
UPDATE: Do not flash cm-11 roms with the current stable version (2.6.3.0) of TWRP. It won't work. I will create new builds for the I9195 and the I-9190 after someone this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2449107
Seems to me that TWRP is the source of the error and not the recovery build.. And as this is the same TWRP Version here, I'm not sure..

TacoLoco said:
Are you sure? In other TWRP 2.6.3.0 thread OP says:
http://forum.xda-developers.com/showthread.php?t=2449107
Seems to me that TWRP is the source of the error and not the recovery build.. And as this is the same TWRP Version here, I'm not sure..
Click to expand...
Click to collapse
I tried with the rom and it works bam kitkat

yannickamet said:
I tried with the rom and it works bam kitkat
Click to expand...
Click to collapse
Thanks man, will try to update my encrypted ROM with the newest nightly..

TacoLoco said:
Thanks man, will try to update my encrypted ROM with the newest nightly..
Click to expand...
Click to collapse
ok

The number is the same because officially Dees_Troy, main dev of TWRP didn't changed it recently, but many things changed.
I also made a bit nicer workaround for screen glitches after timeout, screen won't be turned off, but at least will reduce brightness to skip burning and save battery
Enviado desde mi GT-I9195 mediante Tapatalk

This recovery also works on i9192, partitions are the same as i9195, just updated mine

Odin says for the file twrp-2.6.3.0-20131229.tar.md5:
Code:
md5 error! Binary is invalid

Try installing over dd command, I'll try to check that later.
Enviado desde mi GT-I9195 mediante Tapatalk

TacoLoco said:
Thanks man, will try to update my encrypted ROM with the newest nightly..
Click to expand...
Click to collapse
Does it work for you? I cannot open my encrypted cm10.1.2 /data partition,it states: "wrong input", even if i tried it 4 times and also tried a reboot. Same partition worked with my TWRP build. Also no fuse support, so not NTFS

johanneszab said:
Does it work for you? I cannot open my encrypted cm10.1.2 /data partition,it states: "wrong input", even if i tried it 4 times and also tried a reboot. Same partition worked with my TWRP build. Also no fuse support, so not NTFS
Click to expand...
Click to collapse
Provide recovery logs if you find a bug you want fixed, about the NTFS support, my SDCard is formatted as NTFS and works well, please explain your problem better.
Enviado desde mi GT-I9195 mediante Tapatalk

OliverG96 said:
Provide recovery logs if you find a bug you want fixed, about the NTFS support, my SDCard is formatted as NTFS and works well, please explain your problem better.
Enviado desde mi GT-I9195 mediante Tapatalk
Click to expand...
Click to collapse
i would have, but i didn't had any accessible storage (no decryption of data, no NTFS mount for SD card) and was short of time. So.. here is the log:

johanneszab said:
i would have, but i didn't had any accessible storage (no decryption of data, no NTFS mount for SD card) and was short of time. So.. here is the log:
Click to expand...
Click to collapse
The prebuilts binaries were added in order to support TouchWiz crypto support, but I'm getting rid of them since forces me to build along ICS crypto and may broke the JB crypto you seems to be using.
Enviado desde mi GT-I9195 mediante Tapatalk

So the question is, there's anybody here still with this recoverie installed along a TouchWiz ROM and using encryption of data for it?
If not I'll try to delete it and move forward to JB encryption methods.
Enviado desde mi GT-I9195 mediante Tapatalk

Hi guys, good work! But how restore samsung recovery without deleting ROM data?

zago84 said:
Hi guys, good work! But how restore samsung recovery without deleting ROM data?
Click to expand...
Click to collapse
Take the recovery.img from the .tar.md5 file containing full stock rom that you flash over odin and apply it using the dd command I wrote on first post, I didn't tried, but must work.
Enviado desde mi GT-I9195 mediante Tapatalk

dd metod work for me, also flash cm 11 using twrp from this post and work 100%
Sent from my GT-I9195 using XDA Premium 4 mobile app

Hi, i have cm11 Rom which is encrypted.. I flashed twrp to decrypt data and flash Rom update but twrp cannot decrypt data (entered password about ten times).. I think twrp needs update to decrypt kitkat, am i right with this?
Greetings

Related

[ROM][4.4.4] CyanogenMod 11.0 [OFFICIAL][NIGHTLIES]

{
"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:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), 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, dead cats,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will break it! :P
* Act accordingly
*/
Code:
[CENTER][COLOR="Cyan"]IMPORTANT INFORMATION[/COLOR]
I am not supporting that ROM, I am just releasing for if someone wanna give a try to it until nightlies came out.
Also want to say I do not add any mod to this build, is just native one as CM sources are.
If this thread becomes a mess, I'll stop posting CyanogenMod 11.0
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 => I DON'T CARE!
Your mod => your problem![/CENTER]
Code:
[CENTER][COLOR="Cyan"]HOW TO INSTALL[/COLOR]
[COLOR="Red"]First time installing CyanogenMod 11.0 to your Galaxy Note N7000[/COLOR]:
Read known issues ans FAQs
Make sure you're running a proper working ClockworkMod-Recovery/TWRP
Copy Gapps and CM11.0 ZIPs to your Internal/External SDcard
Boot into Recovery
Wipe data/factory reset
Wipe Cache and Dalvik Cache
Format System
Flash CM11.0 zip
Flash GApps zip from SDCard
Reboot
Don't restore system data using Titanium Backup!
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
[COLOR="Red"]Updating from previous version of Cyanogenmod 11.0[/COLOR]:
Copy CM11.0 Zip to your Internal/External SDcard
Flash the ROM
Reboot and enjoy![/CENTER]
SCREENSHOTS
​
Code:
[CENTER][COLOR="Cyan"]CHANGELOG[/COLOR]:
[COLOR="Red"] 20140220 [/COLOR]:
* Nightlies start rolling out from CyanogenMod Jenkins.
[COLOR="Red"] frantisheq builds[/COLOR]:
* Updated to latest CyanogenMod sources.
[COLOR="Red"]BETA7 20131222[/COLOR]:
* Updated to latest CyanogenMod sources.
[COLOR="Red"]BETA6 20131118[/COLOR]:
* Fixed Videorecording.
[COLOR="Red"]BETA5 20131115[/COLOR]:
* Fixed Root on ART.
* Selinux on permissive mode.
* Lockscreen statusbar transparent (thanks to chasmodo).
[COLOR="Red"]BETA4 20131115[/COLOR]:
* Fixed Brightness and AutoBrightness.
[COLOR="Red"]BETA3 20131114[/COLOR]:
* Fixed CWM Recovery.
* Fixed libsensors.
[COLOR="Red"]BETA2 20131114[/COLOR]:
* Fixed Battery broken.
[COLOR="Red"]BETA1 20131113[/COLOR]:
* First Beta Release.
* Using stock CM kernel.
[/CENTER]
Code:
[CENTER][COLOR="Cyan"]KNOWN BUGS[/COLOR]
- You tell me
[/CENTER]
Code:
[CENTER][COLOR="Cyan"]DOWNLOADS[/COLOR]
[SIZE="5"][URL="http://download.cyanogenmod.org/?device=n7000"][COLOR="Cyan"][B]NIGHTLIES[/B][/COLOR][/URL][/SIZE]
[SIZE="4"][URL="http://forum.xda-developers.com/showthread.php?t=2397942"][COLOR="Green"][B]Gapps for 4.4[/B][/COLOR][/URL][/SIZE]
[/CENTER]
Code:
[CENTER][COLOR="Cyan"] CREDITS[/COLOR]
Cyanogenmod Team
Frantisheq for release older builds
[/CENTER]
Code:
[CENTER][COLOR="Cyan"]SUPPORT[/COLOR]
Android IRC>FreeNode> #cyanogenmod
Don't expect any support if you:
- are not running stock cm-kernel
- have installed any mods
- have modified system files[/CENTER]
Downloading! WIll report
Wow thank you so much man
and here is a note for you :
Released Beta 2, changelog and link on OP.
Enviado desde mi GT-N7000 mediante Tapatalk
How many ROMs are you trying to maintain.
Again well done @herna :thumbup:
Already rooted?
Hi herna
I have a question.
I know all the past CyanogenMods I have put on my device use CWM recovery and not TWRP.
Will CyanogenMod always keep using CWM recovery?
I don't mean that as a bad thing. I like both recoveries but I thought I would ask this.
CWM recovery is still my favorite
Also thanks for releasing this. Really appreciate it
isquite said:
Already rooted?
Click to expand...
Click to collapse
Yes , it came rooted by default.
NutZInTheHead said:
Hi herna
I have a question.
I know all the past CyanogenMods I have put on my device use CWM recovery and not TWRP.
Will CyanogenMod always keep using CWM recovery?
I don't mean that as a bad thing. I like both recoveries but I thought I would ask this.
CWM recovery is still my favorite
Also thanks for releasing this. Really appreciate it
Click to expand...
Click to collapse
It will have always CWM. Now is broken , I need to fix it so I would suggest to install my fixthat.zip on the Omni ROM 4.4 until I release a fixed one
Enviado desde mi GT-N7000 mediante Tapatalk
Thanks
Hi Herna,
Many thanks and really appreciate your contribution for our Galaxy Note.
Please explain what is the mean of "Recovery Broken"
Thanks again mate.
Recovery broken means "kaputt", damaged, you can't use CWM recovery.
mjrifath said:
Hi Herna,
Many thanks and really appreciate your contribution for our Galaxy Note.
Please explain what is the mean of "Recovery Broken"
Thanks again mate.
Click to expand...
Click to collapse
AA1973 said:
Recovery broken means "kaputt", damaged, you can't use CWM recovery.
Click to expand...
Click to collapse
It means flash my fixthat.zip from Omni 4.4 thread, @AA1973 if you can post the link here, please. Until I compile new version, I am on school until 4 hours
Enviado desde mi GT-N7000 mediante Tapatalk
AA1973 said:
Recovery broken means "kaputt", damaged, you can't use CWM recovery.
Click to expand...
Click to collapse
Oh! Thanks you,
So how to do the future updates
@herna you mean that one... fixthat.zip
++++ link removed by me ++++
@mjrifath that is why it is called experimental
The fix above is confirmed working on Omni 4.4,but I haven't tested it on CM 11. Because I won't touch CM anymore! So flash it on your own risk etc yadda yadda
Beta2 didnt even boot for me. But i flashed the fixthat.zip before rebooting from recovery. But no go here
Thanks for confirming @Galaxtus
I removed the link, sorry for the inconvenience
Gesendet von meinem GT-N7000 mit Tapatalk
AA1973 said:
@herna you mean that one... fixthat.zip
++++ link removed by me ++++
@mjrifath that is why it is called experimental
The fix above is confirmed working on Omni 4.4,but I haven't tested it on CM 11. Because I won't touch CM anymore! So flash it on your own risk etc yadda yadda
Click to expand...
Click to collapse
the fix that you mention did not work the device will not start and stick to black unresponsive screen...
but I flash with just the cm11 and gapps.. if worked
testing now hope that the issues in omin4.4 is not present in this rom
I removed link, maybe I uploaded the wrong file, can someone confirm me that Beta2 booted correctly without flash fixthat.zip AA1973 posted?
Enviado desde mi GT-N7000 mediante Tapatalk
msh2050 said:
the fix that you mention did not work the device will not start and stick to black unresponsive screen...
but I flash with just the cm11 and gapps.. if worked
testing now hope that the issues in omin4.4 is not present in this rom
Click to expand...
Click to collapse
What do or did you expect after roughly 10 days on kitkat? Btw Omni 4.4 is not
even a week old!
herna said:
I removed link, maybe I uploaded the wrong file, can someone confirm me that Beta2 booted correctly without flash fixthat.zip AA1973 posted?
Enviado desde mi GT-N7000 mediante Tapatalk
Click to expand...
Click to collapse
Even if it boots what about the broken recovery Then you cant use the recovery to flash anything. Maybe @AA1973 suggestion might work doing preload/TWRP hack on Omni thread
herna said:
I removed link, maybe I uploaded the wrong file, can someone confirm me that Beta2 booted correctly without flash fixthat.zip AA1973 posted?
Enviado desde mi GT-N7000 mediante Tapatalk
Click to expand...
Click to collapse
no it is not working (black boot) with fixthat
and fhashed the b2 .. from the start it show "unfortunately, CyanogenMod Account has stopped..
---------- Post added at 12:55 PM ---------- Previous post was at 12:16 PM ----------
Flashing through sideload and then recovering cm10.2.... Waiting for next releases thanks.
Sent from my GT-N7000 using Tapatalk

[RECOVERY][XU] TWRP 2.7.0.0 touch recovery [2014-03-19]

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

[OFFICIAL&TESTS]TWRP for the LeEco Le Max 2

{
"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:
#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 doing this to your device
* 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.
*/
This is for OFFICIAL and BETA builds of TWRP for the LeEco Le Max 2
Stable Downloads:
[url]https://twrp.me/leeco/leecolemax2.html[/URL]
Test Downloads:
https://osdn.net/projects/twrp-for-x2/releases/
Sources:
Official: https://github.com/TeamWin/android_device_leeco_x2
Tests: https://github.com/ThEMarD/android_device_leeco_x2-twrp
Platform Tools (adb/fastboot):
https://developer.android.com/studio/releases/platform-tools.html#download
Installation:
Make sure your bootloader is unlocked
Download the recovery image from above
Reboot into fastboot
Run this command (Change the .img to whatever the name of file is you downloaded):
Code:
fastboot flash recovery twrp-3.5.0_9-0-x2.img
Once it is flashed, please force a reboot to recovery by holding down the Power and Volume Up buttons at the same time until the phone reboots and you see the LeEco logo and the word "recovery" underneath it. (This is because if you allow normal boot after flashing TWRP and you are using EUI ROM and your phone reboots to EUI ROM? It will overwrite recovery with stock EUI ROM recovery. Forcing a reboot from bootloader to recovery prevents this issue)
Upgrade instructions
Download desired TWRP version
Reboot to recovery
Select Install
tap on "install image" and select the TWRP.img you downloaded from step one
select the recovery partition and install the TWRP.img to it
Reboot to recovery and confirm that the updated TWRP image is installed
For the TEST builds of TWRP? Please let me know if this works. If so? I will submit it to Gerrit for official updates.
Credits:
bigbiff for helping me get setup on on gerrit.twrp.me for official status and updating official TWRP for the Le Max 2
Varzag, LEvvvEL, harryohh, kayyappan, bilausdaniel and anyone else I missed who tested my builds of TWRP
Ncrypt3d : He had a original base that did not boot but we ping ponged and got it working.
AndroPlus-org Fixing Decryption and getting OTG working with some cables
deadman96385 for the work he has done on for the Le Max 2
jrior001 for his work on TWRP for the Le Max 2 and in general for msm8996-common stuff too
codeworkx for his tweaks I implemented into my TWRP commit and everything he has done for LeEco devices
andr68rus for everything he has done for the LeEco Le Max 2
infrag as well for everything he has done for the Le Max 2
shivatejapeddi as well for his work on the Le Max 2
GalaticStryder for helping resolve the f2fs issue and his contributions to the kernel and x2's truly panel fix
Dianlujitao for his continued work on TWRP and fixing encryption footers for TWRP based on 8.1 and above
ok I could literally be here all day typing so essentially anyone who has worked on the msm8996 common kernel for LineageOS (note: will take forever to generate the list https://github.com/LineageOS/android_kernel_leeco_msm8996/graphs/contributors)
XDA:DevDB Information
[OFFICIAL&TESTS]TWRP for the LeEco Le Max 2, Tool/Utility for the LeEco Le Max 2
Contributors
ThE_MarD, deadman96385, jrior001, Ncrypt3d, AndroPlus-org, codeworkx, andr68rus, infrag, shivatejapeddi
Official Builds Changelog
TWRP-3.3.1-0
x2: README: improve device configuration table
x2: remove lineage makefiles
x2: fstab: clean up formatting
x2: fstab: add efsc modem partition
TWRP-3.3.0-1
x2: Use toolbox instead of busybox
x2: Add persist entry to fstab
x2: remove mounting of persist in init
x2: remove firmware mounting in init
x2: remove unused system.prop
x2: allow vendor partition to be backed up
x2: Set TARGET_2ND_ARCH_VARIANT as armv8-a
x2: Fix HW FDE when building with Pie tree
x2: BoardConfig: remove wait for qsee cflag
x2: update kernel, fstab and init
x2: Update QSEE stack from OP3 OOS 9.0
x2: Use libcryptfs_hw from commonsys repo
x2: update init for pie qsee blobs
x2: Update README for TWRP Pie
TWRP-3.3.0-0
x2: kernel: add pstore support
x2: fstab: allow vendor wipe in GUI
TWRP-3.2.3-1
x2: add vendor partition
x2: Update prebuilt kernel for treble and Pie compatibility
TWRP-3.2.1-2
x2: enable f2fs, quota & default brightness to 40%
(please note, converting to f2fs does not work on this build. Please use test build by GalaticStryder and report here if it works or not for you https://github.com/GalaticStryder/lineage_releases/releases/tag/recovery )
TWRP-3.2.1-1
x2: Rebase on zl1 android-8.1 TWRP device tree. We are now Oreo based with working data decryption and adb sideload. Major thanks to @codeworkx for his zl1 TWRP I used as my base.
TWRP-3.2.1-0
We are Official!
x2: prebuilt kernel and miscelaneous tweaks (TWRP-3.2.1-0 compatible)
* Prebuilt kernel and updated init and qseecomd from LineageOS (https://github.com/LineageOS/android_kernel_leeco_msm8996)
* Miscelaneous tweaks from leeco-devs/android_device_leeco_zl1 and omnirom/android_device_leeco_x2
TEST Builds Changelog
April11-2018
F2FS support and default brightness set to 40% (100% hurts my eyes haha)
https://gerrit.twrp.me/#/c/3066/
March30-2018
Rebased on official LineageOS 15.1 kernel with zl1 android-8.1 TWRP branch
This fixes adb sideload and data decryption
Feb23-2018
Ported the zl0 TWRP Oreo build by codeworkx to the x2.
Jan152018
Attempted fixes for encryption
unfortunately it seems the pulldecryptfiles.sh script doesn't always work and on some newer versions of EUI ROM can even fail to work at all... Importing the vendor/lib64 encryption files directly into the device tree for TWRP fixes this issue.
vendor/lib64 files pulled from 1512699115_LE_X2_X820-CN-FN-FEXCNFN5902812081S-5.9.028S
*** Please note, decryption fix isn't 100%!!! I think I need to use the Indian 5.8.019s decryption files as decryption fails when testing from indian 5.8.019s to custom Oreo ROM hmm... ***
Jan212018
Switched decryption to blobs from Indian EUI ROM 5.8.019s
unfortunately it seems the pulldecryptfiles.sh script doesn't always work and on some newer versions of EUI ROM can even fail to work at all... Importing the vendor/lib64 encryption files directly into the device tree for TWRP fixes this issue.
crypto files pulled from LE_X2_X820-OS-OP-FGXOSOP5801910121S-5.8.019S (Indian 5.8.019s) because it has encryption and it's forced encryption.
It seems Chinese EUI ROM doesn't have encryption capabilities only Indian EUI ROM which could be why switching from Indian EUI ROM to a custom ROM causes decryption to fail.
xxxhdpi screen density and support for extra languages (eg Chinese)
Heyyo, if you have problems with MTP drivers on Windows? Please check device manager as Windows messes up the device driver installation. Select it and update driver and manually pick a driver like in the example picture.
kihope12 said:
Nice ! default theme on board? anyway oyur post is dubled
Click to expand...
Click to collapse
Heyyo, yes default theme... and derp! My internet's acting up. Kept getting timeouts haha I'll use this one since I set this thread up proper
Hi excellent work.
Check this to if anything can help on development..
le_x2 Latest TWRP 3.2.1-1. Updated Firmware Recovery .. Kernel latest OREO-N-Support. f2fs support, more partitions for backup and restore. Extra tools inside.. Flash it through TWRP, like a regular zip . https://drive.google.com/open?id=1T3NQ_QQafWulIxtD9JT-yH0wYXZtK7Ye
SS
https://imgur.com/a/qHJWV
@ThE_MarD, i have install and it's ok, test backup ok, now test install rom
CrisBalGreece said:
Hi excellent work.
Check this to if anything can help on development..
le_x2 Latest TWRP 3.2.1-1. Updated Firmware Recovery .. Kernel latest OREO-N-Support. f2fs support, more partitions for backup and restore. Extra tools inside.. Flash it through TWRP, like a regular zip . https://drive.google.com/open?id=1T3NQ_QQafWulIxtD9JT-yH0wYXZtK7Ye
SS
https://imgur.com/a/qHJWV
Click to expand...
Click to collapse
Heyyo, ah cool I didin't know someone else already had TWRP-3.2.1 up and going.
Are you going to submit it to https://gerrit.twrp.me/ ?
vazarg said:
@ThE_MarD, i have install and it's ok, test backup ok, now test install rom
Click to expand...
Click to collapse
Sounds good!
ThE_MarD said:
Heyyo, ah cool I didin't know someone else already had TWRP-3.2.1 up and going.
Click to expand...
Click to collapse
This was my base. Credits to my friend geoanto555 from Greek Xiaomi forum. Based on firmware Mi6plus I think..
Νew twrp support android 8.1
root supersu, unroot, file manager aroma
http://www.mediafire.com/file/oi7nwkn8i2mdd2g/twrp_lemax2_3.2.1-1_tools-su.img/
twrp_lemax2_3.2.1-1_blue-tools
install rom MM miui ok
restore in test
---------- Post added at 07:08 PM ---------- Previous post was at 06:58 PM ----------
restore ok
vazarg said:
install rom MM miui ok
restore in test
---------- Post added at 07:08 PM ---------- Previous post was at 06:58 PM ----------
restore ok
Click to expand...
Click to collapse
Cool! Thanks for testing it out vazarg! Submitting it to gerrit.twrp.me
https://gerrit.twrp.me/#/c/2866/
It's Cool ! Thanks for all you guy great work !
CrisBalGreece said:
Hi excellent work.
Check this to if anything can help on development..
le_x2 Latest TWRP 3.2.1-1. Updated Firmware Recovery .. Kernel latest OREO-N-Support. f2fs support, more partitions for backup and restore. Extra tools inside.. Flash it through TWRP, like a regular zip . https://drive.google.com/open?id=1T3NQ_QQafWulIxtD9JT-yH0wYXZtK7Ye
SS
https://imgur.com/a/qHJWV
Click to expand...
Click to collapse
Works great, thanks.
Finally TWRP accepts my pattern to decrypt partition!! Thanks
Edit: spoke too soon. It only works sometimes. Worked the first time. Has now failed a few times. Just worked again now. Anybody know what the issues might be here?
harryohh said:
Finally TWRP accepts my pattern to decrypt partition!! Thanks
Edit: spoke too soon. It only works sometimes. Worked the first time. Has now failed a few times. Just worked again now. Anybody know what the issues might be here?
Click to expand...
Click to collapse
Hmm I can try and take a look at it sure. Can you please post the logs? It can be found under the advanced menu to copy logs and then just zip them up and post them here
ThE_MarD said:
Hmm I can try and take a look at it sure. Can you please post the logs? It can be found under the advanced menu to copy logs and then just zip them up and post them here
Click to expand...
Click to collapse
Thanks for the reply. I tried it a few times this morning and it has worked every time thankfully. Next time it fails I'll post the logs here.
Oh Mr. Mard, you were cooking something for us without telling, I like how you play. Thanks.
harryohh said:
Finally TWRP accepts my pattern to decrypt partition!! Thanks
Edit: spoke too soon. It only works sometimes. Worked the first time. Has now failed a few times. Just worked again now. Anybody know what the issues might be here?
Click to expand...
Click to collapse
Heyyo harryohh wanna take an adventure with me?
changes commit I made to fix decryption
https://github.com/ThEMarD/android_...mmit/17eda0f901917edcf351da55b078b70df2256b0a
download here to try it out
https://www.androidfilehost.com/?fid=817906626617958526
I'll update the OP with this link
i tried to flash the recovery but when i flash it in fastboot mode everything says ok but when i try to boot into it it boots into the previous recovery that i had installed on the phone dont know why
Flash it with the previous recovery!
ThE_MarD said:
Heyyo harryohh wanna take an adventure with me?
changes commit I made to fix decryption
https://github.com/ThEMarD/android_...mmit/17eda0f901917edcf351da55b078b70df2256b0a
download here to try it out
https://www.androidfilehost.com/?fid=817906626617958526
I'll update the OP with this link
Click to expand...
Click to collapse
I like an adventure.
I'll download and try it out this evening

[beryllium][unofficial][R10.0-b6] OrangeFox Recovery Project

OrangeFox Recovery Project​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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 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.
*
*/
Download: https://curoviyx.ru/orangefox
Maintainer: @curoviyxru
Credits:
MrYacha - frontend dev, CEO, site, UI
fordownloads - frontend dev, theme creator, designer
DarthJabba9 - backend dev, build system, C++
TWRP Team - base recovery
KMP Design, PBRP Team, RedWolf Team and others
Source: https://gitlab.com/OrangeFox
Telegram releases channel: https://t.me/pigspool
Frequently Asked Questions, MIUI OTA, Troubleshooting, and Sundry Information: coming soon.
Installation:
via TWRP-based recovery:
Download the OrangeFox ZIP file to your device
Reboot to your custom TWRP-based Recovery
Install the OrangeFox zip file as a normal zip
The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
Enjoy!
via fastboot:
Download the OrangeFox IMG file to your PC
Reboot your device to fastboot mode
Install the OrangeFox image with command:
Code:
fastboot flash recovery OrangeFox-VERSION-Unofficial-beryllium.img
Reboot to recovery.
Enjoy!
Features:
Supports Treble and non-Treble ROMs
Up-to-date Oreo kernel, built from sources
Increased compatibility with TWRP
Updated with latest TWRP commits
Built-in support for installing init.d functionality
Built-in support for installing Magisk
AromaFM (disabled by now, but you can enable it by file rename at internal_storage/Fox/FoxFiles/AromaFM/AromaFM.zip.not to AromaFM.zip)
Password
Support for Miui and Custom ROMs
Better language support
Optimized versions of community scripts
Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
- choice of font
Alternative lockscreen
...and many more!
XDA:DevDB Information
OrangeFox Recovery Project, Tool/Utility for the Xiaomi Poco F1
Contributors
curoviyxru, MrYacha , DarthJabba9, fordownloads
Source Code: https://gitlab.com/OrangeFox
Version Information
Status: Beta
Current Stable Version: R10.0-b6
Stable Release Date: 2019-06-27
Current Beta Version: R10.0-b5
Beta Release Date: 2019-06-26
Created 2019-06-26
Last Updated 2019-06-27
Reserved
Reserved
Please, report your bugs and problems in that thread.
Wow! So nice thanks you! I like it!!
Hello.. . Does this support multirom? thanks for your work
The LED kept turned on even though Im not plugging the phone into a power source, and the File tab always reset the default location upon booting to the internal storage even though I was last using the external sdcard
Sharfuddin Ahmed said:
Hello.. . Does this support multirom? thanks for your work
Click to expand...
Click to collapse
No, it doesn't.
OrangeFox Recovery Project Unofficial updated. (beryllium, R10.0-b6)
Changelog:
* Splash logo partition backup and image flashing were enabled. (hello, PocoSphasher!)
* Optimus Drunk kernel was updated to stable June 27 build.
* AromaFM was fully removed.
I tried many different recoveries to flash Aroma gapps but it didn't worked on any.., Will Aroma gapps work on this recovery?
killeradi said:
I tried many different recoveries to flast Aroma gapps but it didn't worked on any.., Will Aroma gapps work on this recovery?
Click to expand...
Click to collapse
No Poco recovery supports aroma as far as I know.
Hi m8!
Does decryption work? In previous releases it didn't use to...
Tia!
Enviado desde mi POCO F1 mediante Tapatalk
Hi,
any way to support encrpytion?
Came from official twrp and falshing OrangeFox r10 b6 but recovery asks for password because decryption failed with stock password...
Thanks
StefanV3
whats r the diffn betwn Official v9.0 n unofficial one ?
Amazing work guys it looks so damn good! Now we finally got rid of that old recovery look
markmywordz said:
whats r the diffn betwn Official v9.0 n unofficial one ?
Click to expand...
Click to collapse
its v10 beta
Glassgg said:
its v10 beta
Click to expand...
Click to collapse
stable one released, then why status is on beta?! also zip file stated as unofficial.
isnt stable one is official?
StefanV3 said:
Hi,
any way to support encrpytion?
Came from official twrp and falshing OrangeFox r10 b6 but recovery asks for password because decryption failed with stock password...
Thanks
StefanV3
Click to expand...
Click to collapse
Advanced07 said:
Amazing work guys it looks so damn good! Now we finally got rid of that old recovery look
Click to expand...
Click to collapse
Anything like encrypting internals as quoted above, while flashing OFRP Zip ?
Advanced07 said:
Amazing work guys it looks so damn good! Now we finally got rid of that old recovery look
Click to expand...
Click to collapse
Have screen shot of glory you seeing?
Indha Lezzio said:
Hi m8!
Does decryption work? In previous releases it didn't use to...
Tia!
Enviado desde mi POCO F1 mediante Tapatalk
Click to expand...
Click to collapse
Answer for myself and everybody: unable to decrypt encrypted data partition. It's a shame, as the look of the recovery is very fancy.
Hope op may resolve this issue! Cheers!
Enviado desde mi POCO F1 mediante Tapatalk

[RECOVERY][SHARED][SURYA/KARNA][R11-0_5] Orange Fox Recovery Project by ManoloRey [UNOFFICIAL]

{
"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"
}
Orange Fox Recovery Project 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>
/*
* Devs 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 RECOVERY
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at them for messing up your device, they will laugh at you.
*
*/
Features:
Synced with the latest Teamwin changes
Designed with latest Material design 2 guidelines
Implemented support for Flyme and MIUI OTA, and incremental block-based OTA in custom ROMs
Included customization
Inbuilt patches, like Magisk and password reset patch
Password protection
Fully open-source
and more
Bugs:
- files sorting is not remembered between reboots (it seems this depends on the MIUI base used, I just found out that on 12.0.7 this works, but not on 12.0.8)
Screenshots:
Click to expand...
Click to collapse
Changelog - current version:
-----------------------------------
OFOX R11-0_5
md5: 28094aef3c3c8b4ed99810991aecadc6
-----------------------------------
• Sync with latest OrangeFox source
• Added zip encryption-disabler-v1 on modules ofox (Menu/Fox Addons/Other)
• Fixed version number Ofox
• Fixes minor bugs that appear in the previous release
DOWNLOAD - HERE
(also for older versions): BOX
or see attached files
Changelog - older versions:
Spoiler
-----------------------------------
OrangeFox-R11-Unofficial-Beta-surya-10-01
md5: 6e35f2aedc8a11621bd490dec12dc6db
-----------------------------------
• Fix Vibration
• Rework Fastbootd and Adb Sideload code
• Use USB configs from MIUI
• Remove predefined services
-----------------------------------
OrangeFox-R11.0_0_B004-Beta
md5: cb6ffb8710e2a31e68bf8345d1c5d6a9
-----------------------------------
• Fix ADB sideload
• Fix Fastbootd (It's in the reboot menu - "fastboot")
• Decryption works 100% now (Even with PIN or password and Android 11)
How to flash the OFOX:
- via fastboot
Code:
fastboot flash recovery recovery.img
Next reboot in OFOX manually or using a fastboot command.
Code:
fastboot boot recovery.img
REMEMBER: it is important that from fastboot you directly reboot into OFOX recovery or the OFOX will be overwritten.
- via custom recovery:
Code:
flash zip file (see attached file) in recovery
Credits:
- Thanks to TeamWin devs
- Thanks to Orange Fox Recovery Project devs
- Thanks to @MrYacha and @DarthJabba9 - Source Development
- Thanks to @ManoloRey - DONATE
Thanks for the work!
What is the difference with the rest orangefox recoveries?
ManoloRey builds are noticeably faster at startup than Brigudavs, also naming of internal storage is different, also name of backup folder differ. Other needs to be tested, now you can choose between two excellent devs/products and if you feel for it, you can compare which one suits you better...
Thx @jeryll for your help !!! Trying this evening...
Thanks @jeryll for presenting this new variant of OrangeFox.
Is it safe to switch between the different OrangeFox variants?
If you don't use backup restore function, then it is safe to switch between them, otherwise you need move your backups to a proper location so that specific recovery can see them:
ManoloReys OFOX use
/Fox/BACKUPS/insert_your_number_here/folders_with_your_backup(s)
Brigudavs OFOX use
/Fox/BACKUPS/POCO_X3/folders_with_your_backup(s)
Thank you for the swift response! I'm only using TitaniumBackup so I should be safe
Can decrypt after install if coming from a twrp mauronofrio version?
Thanks
jorgeepelos said:
Can decrypt after install if coming from a twrp mauronofrio version?
Thanks
Click to expand...
Click to collapse
probably yes, but I never used mauronofrios TWRP, so IDK
jeryll said:
If you don't use backup restore function, then it is safe to switch between them, [....]
Click to expand...
Click to collapse
I.e. the problem of dynamic position handling is solved and a full system backup/restore is now supported?
Do you know if there are plans to make OFox for surya an official version?
just Nob said:
I.e. the problem of dynamic position handling is solved and a full system backup/restore is now supported?
Click to expand...
Click to collapse
- AFAIK the problem of dynamic position handling is not solved (yet)
- full system backup/restore is now supported (if certain conditions are met) more about it - HERE
just Nob said:
Do you know if there are plans to make OFox for surya an official version?
Click to expand...
Click to collapse
AFAIK only two people can answer that ManoloRey or brigudav, they are kindly providing OFOX builds for POCO X3
Damned, totally overlooked that you started a new thread @jeryll
So OrangeFox-R11.0_5-Unofficial-surya is indeed a newer version than @brigudav's OrangeFox-R11.0_1.0-A10-Beta-surya?
With ArrowOS 11 just having moved to OSS vendor, people are reporting problems with decryption in recovery.
Can the current OFOX deal with device decryption on a real A11 base + OSS vendor or does it require an update to OFOX?
Master One said:
Damned, totally overlooked that you started a new thread @jeryll
So OrangeFox-R11.0_5-Unofficial-surya is indeed a newer version than @brigudav's OrangeFox-R11.0_1.0-A10-Beta-surya?
With ArrowOS 11 just having moved to OSS vendor, people are reporting problems with decryption in recovery.
Can the current OFOX deal with device decryption on a real A11 base + OSS vendor or does it require an update to OFOX?
Click to expand...
Click to collapse
OFox is indeed older & It won't probably work with A11 OSS encryption, but you can find & try newer TWRP version by brigudav which dates from 3.5.2021. It's on 4pda. I would share download link, but brigudav doesn't allow it.
SkaboXD said:
OFox is indeed older & It won't probably work with A11 OSS encryption, but you can find & try newer TWRP version by brigudav which dates from 3.5.2021. It's on 4pda. I would share download link, but brigudav doesn't allow it.
Click to expand...
Click to collapse
I thought @brigudav is maintaining both OrangeFox and TWRP?
So no new version of OrangeFox that supports A11 OSS decryption yet?
I've just downloaded twrp-3.5.2_10-1-surya.img dated with 20210503, but I already got used to OrangeFox, which just looks nicer, has the proper keyboard for PIN entry and the simplified view for OTA updates.
Can you or someone else confirm that twrp-3.5.2_10-1-surya.img is indeed the correct and newest version supporting A11 OSS decryption?
No it doesn't work. There is no recovery available right now that supports OSS vendor rom decryption. Go back to MIUI vendor roms if you need it.
syl0n said:
No it doesn't work. There is no recovery available right now that supports OSS vendor rom decryption. Go back to MIUI vendor roms if you need it.
Click to expand...
Click to collapse
Even if with MIUI Vendor there's no way to access to internal storage if it's related to an Android 11 rom. Neither with the latest TWRP release by Brigudav. I see only weird folders / files names.
EDIT : there's a new version by Brigudav... maybe ?!
PYCON said:
Even if with MIUI Vendor there's no way to access to internal storage if it's related to an Android 11 rom. Neither with the latest TWRP release by Brigudav. I see only weird folders / files names.
Click to expand...
Click to collapse
I, too, saw "weird" folders / filenames,
but eventually I was able to access the internal storage, via TWRP
(ie. read the files unencrypted).
This is not recommended, because it weaken's the phone security,
but you can read some steps --> here
metaxda said:
I, too, saw "weird" folders / filenames,
but eventually I was able to access the internal storage, via TWRP
(ie. read the files unencrypted).
This is not recommended, because it weaken's the phone security,
but you can read some steps --> here
Click to expand...
Click to collapse
I don't understand what some users mean with "no security at all"...
Running Android 10 for example, even if your device is encrypted, if u have a TXT in the internal storage with your bank user / password, it's sufficient to reboot into recovery ( or turn on the device into the recovery pressing VOL + ) and... et voilà. The TXT is here. Encryption of course but perfectly readable.
So the difference? From that situation to a device with Android 11 and a decrypted internal memory... I can see no differences...
My 2 cents
PYCON said:
So the difference? From that situation to a device with Android 11 and a decrypted internal memory... I can see no differences...
My 2 cents
Click to expand...
Click to collapse
If phone has Android 11 with OSS Vendor ROMs (or MiUI ROM),
then the TWRP does not show files from internal storage,
ie. all files show like this
Even if encryption is turned off (or no lockscreen/PIN/pattern),
the files/folders cannot be decrypted by TWRP.
metaxda said:
If phone has Android 11 with OSS Vendor ROMs (or MiUI ROM),
then the TWRP does not show files from internal storage,
ie. all files show like this
Even if encryption is turned off (or no lockscreen/PIN/pattern),
the files/folders cannot be decrypted by TWRP.
Click to expand...
Click to collapse
So basically, it seems that Android 11 is more "secure" than Android 10, speaking only about recovery accessing memory... right ?

Categories

Resources