Database Users

[Recovery]TWRP 3.0.2-0 For j2lte

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project (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.It is, therefore, often installed when rooting Android devices.
FEATURES-->>
•MTP support
•USB Mass Storage support
•Micro SDcard and USB OTG storage support
•f2fs file system support (read, write, format, backup & restore)
•exFAT file system support (read, write, format, backup & restore)
•NTFS file system support (read, write, format)
•ADB root
•Full SELinux support
•Built in android 6.0 tree
Downloads-->>
•Link To Download From Official Website-->>Here
Installation-->>
•In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
•Now go to Settings -> Developer options. (above About device).
•You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
•Extract Odin_3.10.7.zip to your computer.
•Install Samsung Mobile Phone Drivers for Odin to find your device.
•Download a .tar image of TWRP For J2.
•Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
•Once you reach the Download mode warning screen, press [Volume Up] to continue.
•Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
•Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery.
Sources-->>
•TWRP-->>https://github.com/omnirom/android_bootable_recovery
•Device Tree-->>https://github.com/TeamWin/device_samsung_j2lte
•Kernal Source-->>https://github.com/CTXz/android_kernel_samsung_j2lte
Gerrit For TWRP-->>http://gerrit.omnirom.org/
Enjoy It
XDA:DevDB Information
TWRP 3.0.2-0, Tool/Utility for Samsung Galaxy J2 (see above for details)
Contributors
Albe96, Dees_Troy
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-04-04
Created 2016-08-18
Last Updated 2016-08-18

Changelogs-->>
Code:
3.0.2-0:
•Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
•Add Greek translation to some builds.
3.0.1-0:
•support new CM 13.0 pattern encryption (sultanqasim).
•fix slow flashing issue due to modprobe (present on only some devices) (#twrp).
•libtar updated to latest upstream and fixes (jcadduono).
•fixes for loading custom themes (_that).
•TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy).
•translation updates - added Italian, Czech and Polish and significant updates to Dutch
•progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy).
•fix input box text display (Dees_Troy).
•reboot option after zip install complete (bigbiff).
•other mostly invisible bug fixes and improvements.
3.0.0-0
•Completely new theme - Much more modern and much nicer looking (by z31s1g).
•True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that).
•Language translation - It won't be perfect and especially some languages that require large font files like Chinese & Japanese won't be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM's Gerrit. (mostly by Dees_Troy).
•Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173).
•Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy).
•SuperSU prompt will no longer display if a Marshmallow ROM is installed.
•Update exfat, exfat fuse, dosfstools (by mdmower).
•Update AOSP base to 6.0!
•A huge laundry list of other minor fixes and tweaks.

One More

Which J2 2016 ? Model No ?

sam razzy said:
Which J2 2016 ? Model No ?
Click to expand...
Click to collapse
No.Its for j2 2015
Sent from my SM-G935F using Tapatalk

I follow some of tutorials in youtube about installing TWRP in j200f but all of them still boots in stock system boot recovery, and failed to flash TWRP. and now i notice in your last step of instruction on installation, that i should go to the boot recovery by doing this "Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery." should i wait for the RESET message in ODIN window? before i do the boot recovery mode? what do you mean "near the end of the flash" help please.

maxxetan said:
I follow some of tutorials in youtube about installing TWRP in j200f but all of them still boots in stock system boot recovery, and failed to flash TWRP. and now i notice in your last step of instruction on installation, that i should go to the boot recovery by doing this "Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery." should i wait for the RESET message in ODIN window? before i do the boot recovery mode? what do you mean "near the end of the flash" help please.
Click to expand...
Click to collapse
Nope.just go to recovery!

can you help me to root j200f using this TWRP? please...

maxxetan said:
can you help me to root j200f using this TWRP? please...
Click to expand...
Click to collapse
Why not?

not boot to TWRP recovery
Albe96 said:
Nope.just go to recovery!
Click to expand...
Click to collapse
i used ODIN3_v3.11.1 to flash j200f after flash it using odin it say RESET and 0 failed, then when i boot to recovery it still boots in stock system boot recovery, same problem in some youtube tutorials any solutions please.

maxxetan said:
i used ODIN3_v3.11.1 to flash j200f after flash it using odin it say RESET and 0 failed, then when i boot to recovery it still boots in stock system boot recovery, same problem in some youtube tutorials any solutions please.
Click to expand...
Click to collapse
At first i also faced this error[emoji23] [emoji23] !
To avoid this follow these steps-->>
1.Download The Files(TWRP,Odin,A Stable SuperSU.zip)
2.Open Odin.exe as administrator.
3.Uncheck The "Auto Reset"/"Reset" Option.
4.Click On AP/PDA option and choose the recovery img.tar file.
5.Simply Flash.
6.After Done,Boot Into Recovery Manually.

@Albe96 thanks i can now successfully boot into TWRP then start flashing superSU but then it stuck in bootloop (samsung logo) please help, i dont know the cause if it is flashing TWRP or the supersu that i flash using TWRP. help me please.

maxxetan said:
@Albe96 thanks i can now successfully boot into TWRP then start flashing superSU but then it stuck in bootloop (samsung logo) please help, i dont know the cause if it is flashing TWRP or the supersu that i flash using TWRP. help me please.
Click to expand...
Click to collapse
Use a stable version of SuperSU.Like V2.46!

maxxetan said:
@Albe96 thanks i can now successfully boot into TWRP then start flashing superSU but then it stuck in bootloop (samsung logo) please help, i dont know the cause if it is flashing TWRP or the supersu that i flash using TWRP. help me please.
Click to expand...
Click to collapse
Make sure you have checked the option OEM UNLOCKING and USB DEBUGGING in development mode.
Also the latest super su zip also works.

Is this Samsung j200f model..?

imranpopz said:
Is this Samsung j200f model..?
Click to expand...
Click to collapse
Yes

is it work for j200g?

bambitoswa said:
is it work for j200g?
Click to expand...
Click to collapse
yep

Any custom rom available for j200f ?

[Recovery][TWRP][SANTONI] Recovery for Redmi 4x/Redmi 4 (India)

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.
{
"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"
}
/*
* Your warranty is now void.
*
* 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.
*
*/
Click to expand...
Click to collapse
Install guide:
> Install fastboot tools from google's sdk on your PC
> Enter fastboot mode
> Unlock your bootloader
> Download recovery*.img and Lazyflasher
> Copy lazyflasher In your internal Phone memory
> Run fastboot flash recovery twrp-3.1.0-1-santoni.img in command line
> Boot into recovery and flash Lazy flasher (Important for miui, else you can boot into system)
> Reboot and enjoy it
Download:
Lazy flasher
twrp-3.1.0-1-santoni.img
Lazy flasher - updated link

Thejayyadav said:
Need recovery for Redmi 4x (China) or Redmi 4 (India)
Click to expand...
Click to collapse
You find it on MIUI official Forum, i can't post the link.

Video tutorial for rooting redmi 4/4x

I have unlocked my phone recently. And then I downloaded TWRP from "twrp.me" for my Redmi 4X. And I tried to flash it through adb and fastboot. And I successfully flashed. But unfortunately my phone doesn't boot to TWRP recovery except commanding through cmd "fastboot boot recovery.img". When I try to boot to recovery mode with volume up + power button, the stock recovery comes up. How can I fix this?

its asking password for decrypt mount at recovery startup

cssk19 said:
its asking password for decrypt mount at recovery startup
Click to expand...
Click to collapse
Clear data

twrp
incubus9867 said:
I have unlocked my phone recently. And then I downloaded TWRP from "twrp.me" for my Redmi 4X. And I tried to flash it through adb and fastboot. And I successfully flashed. But unfortunately my phone doesn't boot to TWRP recovery except commanding through cmd "fastboot boot recovery.img". When I try to boot to recovery mode with volume up + power button, the stock recovery comes up. How can I fix this?
Click to expand...
Click to collapse
Have you solved this issue? I've the same problem

Thejayyadav 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.
Install guide:
> Install fastboot tools from google's sdk on your PC
> Enter fastboot mode
> Unlock your bootloader
> Download recovery*.img and Lazyflasher
> Copy lazyflasher In your internal Phone memory
> Run fastboot flash recovery twrp-3.1.0-1-santoni.img in command line
> Boot into recovery and flash Lazy flasher (Important for miui, else you can boot into system)
> Reboot and enjoy it
Download:
Lazy flasher
twrp-3.1.0-1-santoni.img
Click to expand...
Click to collapse
Thanks buddy

i was using twrp 3.0 but as i installed latest 3.1.1 it is encrypted and asking for password . Files are also not properly flashing . System mount unmount error etc. I did factory format , data wipes and also flashed recovery using fastboot but nothing happened but when i reverted back to twrp 3.0 all the problems were solved .

Same for me, went back to 3.0.3.0, too, because of the encryption problem. This might be solved (not testet yet):
see: h11ps://forums.oneplus.net/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/page-2#post-16003616
I just edited the scipt within the zip-file to only remove the locksettings.db (without testing, yet):
see: h11ps://forums.oneplus.net/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/page-2#post-15926929
Edit: just upgraded to "TWRP 3.1.0-1 Santoni.img" (see dl-link above) which runs without any problem so far...

Use TWRP 3.1.0..
DON'T use the newest 3.1.1.0... it's faulty as sh*te

Why i am not able to boot into recovery through advanced power option? Even i tried through power and volume up buttons but failed.... Please help me....

volumeup+volumedown+power=twrp recovery
Or use the twrp app to boot into recovery, BUT do not twrp update!! It'll update to the sh*te 3.1.1 version!

Plz sign the petition if you guys want that the kernel sources must be released for redmi 4X https://www.change.org/p/xiaomi-dev...m_medium=copylink&utm_campaign=share_petition

Error 7 while flashing post 1 zip on redmi 4x
Please let me give sollution for installing pie i had error 7 while flashing post 1 zip file

JASALPURABM said:
Please let me give sollution for installing pie i had error 7 while flashing post 1 zip file
Click to expand...
Click to collapse
File download corrup

I had try that also but same issue from different downloaded file also

[OFFICIAL][R10.0][Stable] OrangeFox Recovery Mi A3 [laurel_sprout]

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"
}
Redwolf fork​
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.
*
*/
OrangeFox is FREE SOFTWARE​
Supports Treble, Miui, Custom Roms
Download:
Stable Builds
OrangeFox Recovery R10.0_2.1 [Latest]
INSTALLATION:
1- How to install OrangeFox Recovery ?
Method-1=
1. Download the OrangeFox zip file and copy it to your device (internal or external storage)
2. Extract the recovery.img from the zip and store it, on the folder where you have adb and fastboot files, on your PC
3. Open a cmd line and execute these commands (being on that folder, of course):
- adb devices (to make sure your device is detected)
- adb reboot bootloader (to reboot into fastboot mode)
- fastboot getvar current-slot (to check what's your current active slot)
- fastboot set_active b (if your active slot was a, if it was b then change it to a)
- fastboot erase boot
- fastboot flash boot recovery.img
- fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)
4. When OrangeFox recovery boots, if you have the stock boot.img that matches the build on this "currently active" slot, flash it into boot partition. If you don't have, then just ignore this step...(it's not mandatory)
5. Install the OrangeFox zip (always install the latest build available)
6. Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)
7. Reboot to System
8. Enjoy!
Method-2=
0. Backup your ROM and all your files
1. Download the OrangeFox zip file to your device
2. Reboot to your custom TWRP-based Recovery
3. Install the OrangeFox zip file as a normal zip
4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
5. Enjoy!
2 -How to flash rom(s) using OrangeFox Recovery:
1. Format data (TIPPING YES).
2. Flash rom zip (PE, BEAST, ATOM
ETC...)
3. Flash OrangeFox-Recovery.zip again. ( INSTALLER, THE PHONE WILL REBOOT TO ORANGE RECOVERY (IF YOU DONT FLASH THIS AGAIN, RECOVERY WILL DISAPPEAR)
4. Flash Magisk v20.
5. Flash Gapps (optional).
6. Flash Patch_no_fde.
Frequently Asked Questions, MIUI OTA, Troubleshooting, and Sundry Information:
* See https://forum.xda-developers.com/showpost.php?p=76885728&postcount=3
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* ATG and Dadi11 - for Redwolf
* Kirillmaster4 - for graphics
* z31s1g - for TWRP theme
* @mauronofrio - for the decryption on Mi A3
* All our helpers and testers ( @prakaship78 , @nelinthon_Kekis , @Dvyhrs , @ihsaneDZ and the others ) - for your patience and help
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 [only for some devices]
* 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
* Alternative lockscreen
* And many more!
Screenshots - see below
Visit to https://orangefox.tech/

Finally,now we can see some roms for this device
Thanx alot to all creators and supporters

Any rom there for orange fox or still only fastboot Roms?
And big thx for the recovery works like a charm
But i don't flash any rom for now

dennis46419 said:
Any rom there for orange fox or still only fastboot Roms?
And big thx for the recovery works like a charm
But i don't flash any rom for now
Click to expand...
Click to collapse
Pixel experience now has a recovery flashable zip

trkzmn said:
...bla bla bla...
INSTALLATION:
Method-1=
1. Download the OrangeFox zip file, copy to your computer and your device.
2. Unpack the zip and input recovery.img to your pc desktop.
3. Open cmd and give this command "fastboot flash boot recovery.img"
4. Reboot to recovery.
5. When boot orangefox recovery install > OrangeFox-R10.0_2-laurel_sprout.zip [Download Latest Build] .
6. Enjoy
...bla bla bla...
Click to expand...
Click to collapse
Hello!
Thanks for your work, truly appreciate it.
Could you update the OP with the install method that I'm going to describe next? It's just to avoid future complications (lost of Wi-Fi, sound, etc...) for Noob users.
Download the OrangeFox zip file and copy it to your device (internal or external storage)
Extract the recovery.img from the zip and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (being on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot getvar current-slot (to check what's your current active slot)
fastboot set_active b (if your active slot was a, if it was b then change it to a)
fastboot erase boot
fastboot flash boot recovery.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)​
When OrangeFox recovery boots, if you have the stock boot.img that matches the build on this "currently active" slot, flash it into boot partition. If you don't have, then just ignore this step...(it's not mandatory)
Install the OrangeFox zip (always install the latest build available)
Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)
Reboot to System
Enjoy
Why do I suggest this? Well, please read the hidden content:
By doing this method (which seems more complicated but I've tried my best to explain it as if I were explaining it to a 4 years old kid...) we will flash the recovery.img into the "inactive" slot, thus, not breaking anything on the "currently active" slot. When OrangeFox boots, it will patch both slots boot ramdisks. But the thing is, on the "currently active" slot (the one inactive on the beginning) it will patch the recovery.img but, on the "currently inactive" slot (the one that was active on the beginning), it will patch the stock boot.img, thus, no bug will happen that usually appears when a user accidentally flashes the wrong boot.img into boot partition. On the other hand, if we have the stock boot.img, that matches the build on the "inactive" slot, we could flash it into boot partition before installing the zip that patches ramdisk. By doing this we will patch both stock boot.img present on both slots (instead of patching recovery.img and boot.img).
Cheers!
---------- Post added at 12:04 ---------- Previous post was at 11:16 ----------
Hello....again...
I've just tested the install method that I've explained but, unfortunately, it's not working.
OrangeFox recovery only boots if the installer zip is run through TWRP...don't really know why since I've tested a lot of times doing this exact same method with TWRP recovery, and it's working. It should be working here as well.
Anyway the OF recovery boots but I think that it does not decrypt data. It doesn't gets frozen on the welcome screen (like before) but it doesn't decrypt (I see all the files with the "weird" names). This, of course, is only bad for those who want to remain on stock ROM. For anyone who wants to move on to custom ROMs, just format user data and your set to go.
Cheers!

OrangeFox Recovery R10.0_2.1 Changes
* Fix stuck in fastboot mode after flashing OrangeFox with fastboot

Post Changes
1. OrangeFox recovery installation made easier with explanations (Thanks to @Typhus_)
2. Custom rom install method added (Thanks to @nelinthon)

Hi all, can we do a backup of all data (system, boot...) And restore with orangefox?
I'm afraid to test any rom and not to be able to return to the original configuration... I have the 5 october update

Shineali said:
Hi all, can we do a backup of all data (system, boot...) And restore with orangefox?
Click to expand...
Click to collapse
Yes you can.
Shineali said:
I'm afraid to test any rom and not to be able to return to the original configuration... I have the 5 october update
Click to expand...
Click to collapse
Follow the install custom rom steps. If you still have problem with it take recovery.log and send me

trkzmn said:
Yes you can.
Follow the install custom rom steps. If you still have problem with it take recovery.log and send me
Click to expand...
Click to collapse
Ok thanks!!!

Anyone fix this error

There is recovery.img
I already changed name to .img and then try..but nothing happened

RJ- said:
Anyone fix this error
Click to expand...
Click to collapse
RJ- said:
There is recovery.img
I already changed name to .img and then try..but nothing happened
Click to expand...
Click to collapse
On the first image your running commands on "C:\Program Files\Minimal ADB and Fastboot" folder.
On the second image your showing the files on "C:\adb" folder.
You must run the commands on the folder where you have the img file stored! Rename the file!!? WTF!?
Besides, you didn't read the instructions carefully, not only your running the command to change slot wrong but, also, you've tried to flash recovery.img into currently active slot before trying to change slot (based on your command history on first image).
PLEASE!
If you're not comfortable doing these simple steps, or if you don't have patience to read all instructions carefully, then just DON'T DO ANYTHING!!
People with this kind of behavior are the main reason why most devs often just drop development. How will you be able to successfully flash a ROM and/or report true bugs, if you're not able to just execute simple commands that have been explained step by step? Maybe my instructions weren't clear enough....perhaps I should have start the steps with:
"Turn on your computer";
"Put your hands on your keyboard and mouse";
"Login to your account";
etc....
ALSO, the recovery on the OP has been updated. Even if you did everything correctly you would end up on fastboot since your trying to flash the wrong OF version!
Please, search, please read, please...USE YOUR BRAIN!

Thanks

Hi I tried to install but i get an error during orangefox first boot there's no option to install orangefox....zip ot seems like the files were encrypted. They have a strange names...
It could be that didn't give permission to write? O do the steps again bit didn't ask me for permission.
Thanks in advance.

Shineali said:
Hi I tried to install but i get an error during orangefox first boot there's no option to install orangefox....zip ot seems like the files were encrypted. They have a strange names...
It could be that didn't give permission to write? O do the steps again bit didn't ask me for permission.
Thanks in advance.
Click to expand...
Click to collapse
Seems files are encrypted.
- Format data
- Flash OrangeFox.zip

RJ- said:
Anyone fix this error
Click to expand...
Click to collapse
Don't use minimal adb, try to use platform tools for windows.

Can Orangefox recovery support for OTA updates in MiA3???

ricky9779 said:
Can Orangefox recovery support for OTA updates in MiA3???
Click to expand...
Click to collapse
No rom for this device has ota support yet anyway. And if you mean ota for stock rom then definitely not as you need stock boot.img for stock ota or it won't work

Website and download link down at the moment or it is just for me?

[RECOVERY][A9/A10] [UNOFFICIAL]SHRP 3.0 (20/01/15)

{
"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"
}
Standard Disclaimer:-
* Your warranty is... still valid?
* 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 Recovery
* 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.
SHRP is inspired by Material Design 2 to bring the newest design to TWRP. SHRP provides much more features alongside it's rich UI experience. New and improved dashboard makes it very easy to interact with TWRP. SHRP also got some extra cool features like whole new theming section , flash Magisk (root or unroot), Camera2API enabler directly from dashboard, password protection etc. It's all only just started , a lot more to come.
- Themes
- List view mode along with grid dashboard
- Status bar customization
- New rounded icons added on dashboard
- Notch mode with toggle to disable
- Dark mode or pure white, it's on you
- Navigation bar customization
- Settings + Advanced Settings
- Flash Magisk
- Clear fingerprints.
- Flash ViperFX
- Recovery Locking , Pin or Pattern lock
- CPU core lock/unlock
- Language changing
- HAL3 / CameraAPI2 enabling/disabling
- Oreo+ reboot menu style
- Redesigned lock screen interface
- Flashlight
- Magisk manager - Enable, disable or delete magisk modules right from SHRP
- and many more, flash right now to find out
1. Make sure you have a custom recovery installed
2. Download the latest SHRP recovery for your device
3. Boot into recovery
4. Flash SHRP recovery zip
5. Reboot to recovery.
6. Done
or
Fastboot flash boot shrp.img (currently only for stock vendor ROMs)
Recovery asks for decryption password every boot (You can say that this is a feature that increases security or just an inconvenient bug, i prefer the former)
File Manager back button dosent work, have to press home button to exit
Loading time is slightly longer than SHRP2 on boot
Thanks to @Master_L at the Telegram group for pointing out these small bugs
https://drive.google.com/drive/folders/12MDRsmJWtbQDCoAXlp1D3U0gHPYA4PSr?usp=sharing
Github
Website
Telegram Group
SHRP Team:
EpicX
DNI9
Giovix92
TeamWin
osmOsis
VR25
Topjohnwu
Mauronofrio
DarthJabba9
Pritish
Kirill
Burak D.
ZJRDroid
LayeardDevMod
Olek & Oliwier
Special Thanks:
@Nikesh001 (for TWRP trees)
@oddlyspaced (for SHRP trees)
@HarukeyUA (for LineageOS trees from which i took kernel and dtbo for recovery)
@AlaskaLinuxUser (for his amazing tutorials for building recoveries)
The Arch Wiki for helpming me deal wih pesky python building errors
Docker Inc. for Docker which helped me to finally compile this in Manjaro ( I don't like Ubuntu)
Please inform if I forgot to mention your name here , thanks !
Maintainer: NanduPV
Based On: TWRP
Source: SHRP 3_9.0
Screenshots:
​

is this able to flash it over Android 11 so in order to be able installing a Custom Rom? (Pixel Experience, EvolutionX)

Vicro2821 said:
is this able to flash it over Android 11 so in order to be able installing a Custom Rom? (Pixel Experience, EvolutionX)
Click to expand...
Click to collapse
No, only A9/A10 till TWRP supports A11

Is there any difference between this and my official builds?

oddlyspaced said:
Is there any difference between this and my official builds?
Click to expand...
Click to collapse
Just ported to new version 2.3.2 to 3.0, same trees. Many thanks for your contributions to our device

I don't ever see a clear guide how to install this recovery to a stock a10 unrooted device with bootloader unlocked... Step by step with any bricking risc. It's the first Time in ten year that i ever don't undsterstand the correct way to do this

wetito said:
I don't ever see a clear guide how to install this recovery to a stock a10 unrooted device with bootloader unlocked... Step by step with any bricking risc. It's the first Time in ten year that i ever don't undsterstand the correct way to do this
Click to expand...
Click to collapse
It is a bit complicated due to A/B system-as-root and new fastboot security restrictions
But, once you understand and do it, it is pretty simple.
Installing / Flashing TWRP (or any other recovery) on A/B devices:
Since all known A/B devices do not have a separate recovery partition, you will eventually have to flash TWRP to the boot partition. On the Pixel 1 and 2, and some other devices, we use fastboot boot to temporarily boot TWRP without flashing TWRP. We then flash a zip installer to to flash TWRP to both slots.
The Mi A3 unfortunately does not support fastboot boot. Instead, users have to determine their currently active boot slot using
Code:
fastboot getvar all
then use,
Code:
fastboot set_active_a
or
fastboot set_active_b
to switch slots to the inactive slot. From here, the user can
Code:
fastboot flash boot twrp.img && fastboot reboot
to get into TWRP. Once in TWRP they can then go to the reboot page and change back to their originally active slot, make a backup, then install TWRP. Using the inactive slot allows users to get a good, unmodified backup of their device before installing TWRP.
Hopefully this helps!
Taken from @Dees_Troy guide on all things TWRP @https://forum.xda-developers.com/t/dev-how-to-compile-twrp-touch-recovery.1943625/post-32965389
Note: To get TWRP or in this case SHRP image file, just extract SHRP installer zip and find recovery.img, this is the Image file you need.

NanduxXxPV said:
It is a bit complicated due to A/B system-as-root and new fastboot security restrictions
But, once you understand and do it, it is pretty simple.
Installing / Flashing TWRP (or any other recovery) on A/B devices:
Since all known A/B devices do not have a separate recovery partition, you will eventually have to flash TWRP to the boot partition. On the Pixel 1 and 2, and some other devices, we use fastboot boot to temporarily boot TWRP without flashing TWRP. We then flash a zip installer to to flash TWRP to both slots.
The Mi A3 unfortunately does not support fastboot boot. Instead, users have to determine their currently active boot slot using
Code:
fastboot getvar all
then use,
Code:
fastboot set_active_a
or
fastboot set_active_b
to switch slots to the inactive slot. From here, the user can
Code:
fastboot flash boot twrp.img && fastboot reboot
to get into TWRP. Once in TWRP they can then go to the reboot page and change back to their originally active slot, make a backup, then install TWRP. Using the inactive slot allows users to get a good, unmodified backup of their device before installing TWRP.
Hopefully this helps!
Taken from @Dees_Troy guide on all things TWRP @https://forum.xda-developers.com/t/dev-how-to-compile-twrp-touch-recovery.1943625/post-32965389
Note: To get TWRP or in this case SHRP image file, just extract SHRP installer zip and find recovery.img, this is the Image file you need.
Click to expand...
Click to collapse
Tnx a lot!

Great contribution! I'm looking forward to unlock bootloader, install recovery and a custom rom on my friend's mi A3. I have done my research but I still have one question. If I wanna keep the recovery after I install the custom rom, do I have to do anything? Or just flashing the zip before installing the rom will do the job? Thanks!

Batpope said:
Great contribution! I'm looking forward to unlock bootloader, install recovery and a custom rom on my friend's mi A3. I have done my research but I still have one question. If I wanna keep the recovery after I install the custom rom, do I have to do anything? Or just flashing the zip before installing the rom will do the job? Thanks!
Click to expand...
Click to collapse
Just make sure to flash the Recovery installer zip after the ROM you flash.

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note 20 & Note 20 Ultra Exynos

{
"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"
}
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 Ultra​Only for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery 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.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu

Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection

FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version or Rollback protection might kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

Updated first post with official pages from twrp.me, but since the builds are not up yet, i posted latest test builds in post #2.
Regards

well done sir

Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!

edsoedso said:
Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!
Click to expand...
Click to collapse
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards

corsicanu said:
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards
Click to expand...
Click to collapse
Nothing changes in the screen phone. Attached is odin screen. Thank you!

edsoedso said:
Nothing changes in the screen phone. Attached is odin screen. Thank you!
Click to expand...
Click to collapse
Can you please check Kg state line from download mode? What's written there?

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
I installed twrp but it seems that it does not read the internal storage.

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
And how to flash the multidisabler? it seems that everything is encrypted and is impossible to locate it in twrp?

I found it!
1. enter into TWRP (after flashing twrp.tar and Vbmeta.tar via odin), format data and reboot again in TWRP
2. Being in TWRP, transfer from PC to your phone multidisabler.zip and magisk zip.
3. flash them both
4. reboot system
That is all!

i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system

Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?

m7mdo_93 said:
i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system
Click to expand...
Click to collapse
edsoedso said:
Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?
Click to expand...
Click to collapse
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
yeah , after flashing multidisabler second time my mobile able to working .. thanks for your help

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
Thank You very much. It worked!

A big thank you, it works fine.

hey.
i did everything from this guide, and i got root access+twrp installed.
the problem that i am facing, is that i canot install anything from twrp, due to insufficient space.
the system size that twrp is reading is only 8384kb, so every installation of gapps is failed.
i tried to wipe ,format data, and changing the file system, but nothing helped.
please give me an idea how to solve it.
thanks.

Good day
Does this work for Android 13 One UI 5.1?