TWRP FOR THE A52 5G! (With issues)
Help needed!
Are you someone that has ported TWRP before without any issues?
Or are you someone that knows how to fix any problem that has been listed in the 'Additional Notes' section?
PM me. We can work together to fix the issue(s)
Note
Code:
* 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.
Additional Notes
Code:
THIS RECOVERY IS NOT FULLY TESTED!
There are atleast these issues:
1. MTP Does NOT work. (Not with computer or with OTG)
2. NO access to your SD cards
3. Incorrect resolution (TWRP is 1080x1920, phone is 1080x2400)
4. Temperature sensor doesn't work.
THERE MIGHT BE MORE ISSUES I DO NOT KNOW OF! FLASH AT YOUR OWN RISK.
How to install?
First of all you need an unlocked BL. This is extremely easy to do and there are a lot of guide online.
Download recovery.tar (TWRP) from this post.
Select the AP slot in Odin
Disable auto reboot in Odin
Flash
Credits
TeamWin Recovery Project
Source code:
Minimal TWRP AOSP: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp
Device Tree for the a52 5g: Can't upload because of 25mb+ kernel file. Will make a custom kernel soon
Thank you so much for your work on TWRP. Waited for it a year
GiulianoB said:
Thank you so much for your work on TWRP. Waited for it a year
Click to expand...
Click to collapse
No problem.
Hi,
Firstly, thanks for doing this!
Secondly, I've been trying to flash a zip (BluetoothLibraryPatcher) but I cannot find a way to get TWRP to read a zip file. Things I've tried:
From the device itself: The data partition is encrypted. twrp decrypt (in the TWRP terminal) says "No crypto support was compiled into this build".
From ADB Sideload: It gets stuck on "Starting ADB sideload feature..." for 5 minutes, then fails.
From MTP/USB OTG: As you say in your post, neither MTP from PC nor from a USB flash drive works.
Would you have any idea of how I can get TWRP to read a zip file to install?
Thanks!
ByteSizedBit said:
Hi,
Firstly, thanks for doing this!
Secondly, I've been trying to flash a zip (BluetoothLibraryPatcher) but I cannot find a way to get TWRP to read a zip file. Things I've tried:
From the device itself: The data partition is encrypted. twrp decrypt (in the TWRP terminal) says "No crypto support was compiled into this build".
From ADB Sideload: It gets stuck on "Starting ADB sideload feature..." for 5 minutes, then fails.
From MTP/USB OTG: As you say in your post, neither MTP from PC nor from a USB flash drive works.
Would you have any idea of how I can get TWRP to read a zip file to install?
Thanks!
Click to expand...
Click to collapse
Hey, you can use commands by just being on the home screen of TWRP. ADB push <file location and name> /sdcard
ByteSizedBit said:
Hi,
Firstly, thanks for doing this!
Secondly, I've been trying to flash a zip (BluetoothLibraryPatcher) but I cannot find a way to get TWRP to read a zip file. Things I've tried:
From the device itself: The data partition is encrypted. twrp decrypt (in the TWRP terminal) says "No crypto support was compiled into this build".
From ADB Sideload: It gets stuck on "Starting ADB sideload feature..." for 5 minutes, then fails.
From MTP/USB OTG: As you say in your post, neither MTP from PC nor from a USB flash drive works.
Would you have any idea of how I can get TWRP to read a zip file to install?
Thanks!
Click to expand...
Click to collapse
Btw, afaik the encryption problem isn't something I can remove.
This is fantastic to see! Nice work.
Have you tried any custom ROMs with this? Do any of the current custom ROMs (like Lineage OS) support A52 5G, or are we still a far way away from that?
biscuitpants said:
This is fantastic to see! Nice work.
Have you tried any custom ROMs with this? Do any of the current custom ROMs (like Lineage OS) support A52 5G, or are we still a far way away from that?
Click to expand...
Click to collapse
Hey. I've not started a custom ROM yet. I've been busy with school mostly. I will probably start developing Lineage OS as the first custom rom.
Things405 said:
Hey. I've not started a custom ROM yet. I've been busy with school mostly. I will probably start developing Lineage OS as the first custom rom.
Click to expand...
Click to collapse
Good luck and thanks again for your effort
Hey! I found this on GitHub and I was wondering if it's you. Your post is still saying "Will upload in a minute". Thanks!
MeowNyaaa said:
Hey! I found this on GitHub and I was wondering if it's you. Your post is still saying "Will upload in a minute". Thanks!
Click to expand...
Click to collapse
Yep thats me. I can't upload a kernel file on github as its 25mb+ So the device tree won't be complete without it. I'll change the post.
Things405 said:
Yep thats me. I can't upload a kernel file on github as its 25mb+ So the device tree won't be complete without it. I'll change the post.
Click to expand...
Click to collapse
I recommend using Git LFS for that, more info about it here: https://git-lfs.github.com/
I created a device tree myself long time ago as well, was just missing the kernel
I may sell my U1 for the Dual Sim model so I can root. I need parts of this lol
Any progress?
I just can't wait for LineageOS
@Things405 I have GitHub pro if you want someone to host the device tree on there... I'm on https://github.com/SImPilotAdamT/
Also by A52 5G do you mean the A526B?
Also for some reason I can't unlock the bootloader in my device... I have the A526B international model. https://forum.xda-developers.com/t/unable-to-unlock-the-bootloader-a52-5g-sm-a526b.4476861/
TWRP 3.7.0 is out with the support for decryption on Android 12 to be able to backup firmware. Pls update, thx
I'm sorry to have left you guys hanging! I've been too busy with personal stuff but I will get back on this as soon as possible.
flashed in A526BXXU1AUAH, when press buttons for recovery, it freeze on boot logo
does this also work for the a52s 5g version?
LuzzyKins said:
does this also work for the a52s 5g version?
Click to expand...
Click to collapse
No, the version you should be looking at is: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-2-for-galaxy-a52s-5g.4488419/
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android M (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
This rom is for both the Nook Tablet 512M/8GB and 1GB/16GB versions. The device code name is "acclaim".
Prerequisites:
A recovery. To install a recovery when coming from a stock device, you need to prepare a special SD card. Installation instructions can be found here on xda.
Installation:
Grab a new recovery (http://get.cm/?device=acclaim or TWRP) and flash it with fastboot.
If you have a CM installed, flash the new recovery and try the updater, otherwise download the zip from nightlies, boot to CM recovery or TWRP and flash it.
Once a version is installed (and all bugs fixed), you will be able to use CM Updater
Settings->About tablet->CyanogenMod updates->Refresh
THE NEW NIGHTLIES HAVE EMULATED STORAGE ENABLED. YOU LOOSE ALL YOUR DATA. MAKE SURE YOU BACKUP!!!! THE INTERNAL EMMC 1GB PARTITION IS ALSO NOT ACCESSIBLE ANYMORE. COPY THE CONTENT. THE EXTERNAL SDCARD IS NOT USED ANYMORE AS PRIMARY STORAGE. ALL APP DATA ON THE SDCARD WILL BE LOST. I ALSO RECOMMEND TO WIPE.
BACKUP!
RE-PARTITIONING IS NOT MANDATORY. IF YOU WANT TO RECLAIM THE 1GB PARTITION (called media) YOU CAN TRY TO FOLLOW THE RE-PARTITION GUIDE:
https://docs.google.com/document/d/1wSAaAZfQcnvkiHKlbZ7_H1h67m2kx0mq-p3Wjgue3qA/edit?usp=sharing
PLEASE COMMENT ON THE DOCUMENT IF SOMETHING IS NOT CLEAR.
Building:
The CM wiki explains that here: http://wiki.cyanogenmod.org/w/Build_for_acclaim
Returning to stock BN firmware:
If you have installed above rom and the CWM recovery and you really hate it and want to go back to stock, you may wish to try to flash the original acclaim_update.zip from BN. You have to unzip that file and edit META-INF/com/google/android/updater-script. Drop the first two lines here:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Zip the package again. Then go to recovery, flash the zip, wipe, and reboot.
Support:
For any issues encountered, please post into this forum, but add steps to reproduce and dmesg, logcat and audit.log information. If you don't know what this is or how to get them, try to find that out first before posting here.
Thanks:
hashcode, ntemis, kuzma30, fattire, mik_os, and many others that contribute to cyanogenmod and especially this version.
kuzma30 - great kernel job
hashcode - we have reused lots of your work and effort for the various omap devices (esp kindle fire). It is thanks to you mainly that we are now official CM device. Also many thanks for the L bringup help.
mik_os - great touchscreen firmware flasher and other efforts
fattire - for helping us everywhere he can
ntemis - thanks for giving so much energy to this - esp for 4.4 and L I have copied lots of things from you
CM community (stargo, etc.) - thanks for replying to all my questions!
DISCLAIMER:
- update the CWM if you come from older versions - otherwise you'll see funny error messages when installing zip
- It is possible that you need to wipe your device. I did not do that, but...
- Also you must flash your own gapps. It can be found somewhere....
- The SELINUX policies are enforced now.
Known issues:
- system partition is too small for full gapps. use a mini gapp package.
- the touchscreen firmware flasher doesn't work on M. Use CM11 to flash it first.
- Currently the CM13 recovery does not flash the open gapps (due to move to toybox instead of busybox)
- CMUpdater (and adb reboot recovery) don't boot into recovery
- The system is altogether not really the fastest thing on earth
Recently fixed:
- M bringup
Get it from
http://download.cyanogenmod.org/?device=acclaim
Get ENG recovery from here. It allows to adb into recovery even when data is wiped.
File: https://dl.dropboxusercontent.com/u...cclaim-eng-recovery-UNOFFICIAL-20150606.0.img
md5sum: 6136fc49c5e9a32f115d40d762bb6f2d
- Reserved -
Need some help. I flashed the recovery from the CM site, and now it only boots to recovery, even after side-loading the CM13 zip for acclaim. Any ideas how to get out of recovery?!?!
Edit: I also tried to "adb sideload" a different recovery (CWM) but it fails to install, saying "E: footer is wrong, E: signature verification failed"
I can only get into adb sideload mode, as "adb devices" says my device is "UNAUTHORIZED", and can't boot to CM at all.
Edit #2: Anything (other than CM zip) I try to flash from ADB sideload within CM recovery fails due to signature verification. Seems like its checking for updates signed by CM. Ugh, not seeing a way out of this.
Thank you, it runs well in account to the specs and age of this old tablet. This experience is better than the CM12 experience, more stable.
Sent from my LGLS991 using Tapatalk
srgibbs99 said:
Need some help. I flashed the recovery from the CM site, and now it only boots to recovery, even after side-loading the CM13 zip for acclaim. Any ideas how to get out of recovery?!?!
Edit: I also tried to "adb sideload" a different recovery (CWM) but it fails to install, saying "E: footer is wrong, E: signature verification failed"
I can only get into adb sideload mode, as "adb devices" says my device is "UNAUTHORIZED", and can't boot to CM at all.
Edit #2: Anything (other than CM zip) I try to flash from ADB sideload within CM recovery fails due to signature verification. Seems like its checking for updates signed by CM. Ugh, not seeing a way out of this.
Click to expand...
Click to collapse
Most likely the bootcounter reached max number of boots. So when booting, the bootloader sends you to recovery.
I'll try to see if the bootcounter reset doesn't work anymore in cm13 recovery.
Anyway, to get you out of this, can't you hold the nook key during boot to go in cyanoboot menu, start fastboot and flash twrp or old recovery with fastboot?
Chris
I Confirm, experience is much better than CM12.1.
Chris you are a legend.
chrmhoffmann said:
Most likely the bootcounter reached max number of boots. So when booting, the bootloader sends you to recovery.
I'll try to see if the bootcounter reset doesn't work anymore in cm13 recovery.
Anyway, to get you out of this, can't you hold the nook key during boot to go in cyanoboot menu, start fastboot and flash twrp or old recovery with fastboot?
Chris
Click to expand...
Click to collapse
The bootcounter reset indeed doesn't work anymore.
To get out of here:
- Let the device go to recovery
- adb to the device
- run the following commands:
mount /system
/sbin/clearbootdata.sh
Reboot
I'll try to fix this ASAP.
Chris
chrmhoffmann said:
The bootcounter reset indeed doesn't work anymore.
To get out of here:
- Let the device go to recovery
- adb to the device
- run the following commands:
mount /system
/sbin/clearbootdata.sh
Reboot
I'll try to fix this ASAP.
Chris
Click to expand...
Click to collapse
Fixed:
http://review.cyanogenmod.org/#/c/128693/
Chris
chrmhoffmann said:
Fixed:
http://review.cyanogenmod.org/#/c/128693/
Chris
Click to expand...
Click to collapse
Thanks for the reply Chris!
The boot counter does increment (top left corner of cyanoboot, goes from 0-9 then starts over) however no matter what I press on that screen it immediately loads recovery.
Also, I can't get shell access with ADB. When I do "adb devices" it says this device is "UNAUTHORIZED". I can, however, choose "Apply update via ADB" in recovery and it changes to "sideload" but it still won't give me shell access.
Without shell access, what are my options? Seems like i can only flash official CM builds. Will the next nightly help me if your fix is in it? Does it affect the boot.img or or does that only affect the recovery?
First boot time? ... working now!
How long does the initial flash take to boot up for the first time?
I built this ROM (cm-13.0-20160116-UNOFFICIAL-acclaim.zip) and gave up after 45 minutes on the bootanimation.
Right now, I am flashing the cm-13.0-20150117-NIGHTLY-acclaim.zip and it is still booting after 30 minutes.
I flashed with TWRP 2.8.7. Is this OK?
BTW - great work on this ROM!
== // ==
Never mind. I built another (completely Linaro) ROM and it flashed and booted OK. The only thing that I did differently was that I did not flash SuperSu-v2.46 after I flashed the ROM.
Again, thanks for bringing Marshmallow to this device!
srgibbs99 said:
Thanks for the reply Chris!
The boot counter does increment (top left corner of cyanoboot, goes from 0-9 then starts over) however no matter what I press on that screen it immediately loads recovery.
Also, I can't get shell access with ADB. When I do "adb devices" it says this device is "UNAUTHORIZED". I can, however, choose "Apply update via ADB" in recovery and it changes to "sideload" but it still won't give me shell access.
Without shell access, what are my options? Seems like i can only flash official CM builds. Will the next nightly help me if your fix is in it? Does it affect the boot.img or or does that only affect the recovery?
Click to expand...
Click to collapse
I am afraid that you are now in trouble, but it is not fatal.
Options:
a) You can flash with "adb sideload" a zip that installs another recovery. I'll try to create that for CM13 now, as there's only some really old stuff available.
b) You can prepare a SDCARD that flashes recovery like if you would come from stock.
Hang on a bit until I provide a).
Chris
chrmhoffmann said:
I am afraid that you are now in trouble, but it is not fatal.
Options:
a) You can flash with "adb sideload" a zip that installs another recovery. I'll try to create that for CM13 now, as there's only some really old stuff available.
b) You can prepare a SDCARD that flashes recovery like if you would come from stock.
Hang on a bit until I provide a).
Chris
Click to expand...
Click to collapse
Sounds good and thanks.
I actually tried dropping the TWRP recovery.img inside the official CM13 zip and flashing that, but again, it failed due to signature verification. I wonder if you could have access to add a build that includes TWRP (or a fixed recovery image) to the "experimental" channel for CM? Or maybe a boot.img that gives me a second or two to press N and load something other than EMMC recovery.
Maybe that way it would be signed by CM and the current recovery would accept it.
chrmhoffmann said:
I am afraid that you are now in trouble, but it is not fatal.
Options:
a) You can flash with "adb sideload" a zip that installs another recovery. I'll try to create that for CM13 now, as there's only some really old stuff available.
b) You can prepare a SDCARD that flashes recovery like if you would come from stock.
Hang on a bit until I provide a).
Chris
Click to expand...
Click to collapse
I had some time today so I tried b) and it finally got some results. I was able to boot to another recovery and flash twrp. Installing CM13 now! I'll update once im done.
Demetris said:
I Confirm, experience is much better than CM12.1.
Chris you are a legend.
Click to expand...
Click to collapse
Yep, this tablet is usable on CM13.
Sent from my LGLS991 using Tapatalk
srgibbs99 said:
I had some time today so I tried b) and it finally got some results. I was able to boot to another recovery and flash twrp. Installing CM13 now! I'll update once im done.
Click to expand...
Click to collapse
Finally got it up and running on CM13. Runs great, and as others have said its much more stable than CM12.
Also, based on my experience, I would advise against installing the CM custom recovery. Much safer to stick with TWRP.
Thanks for all your help Chris.
The new nightlies should have the boot counter fixed, but it's true that cm recovery doesn't support open gapps flash right now as busy box support was dropped.
So it's maybe best to stick with twrp until further notice.
Chris
Sent from my wiko using Tapatalk
Updated to the latest nightly last night (20160119) and upon reboot got "Google Play Services has stopped", and a notification that Play services wont run until you update,.
am unable to go into apps setting to attempt to clear app storage . Crashes when trying the "manage space" option for Google Play Services
ignore , sorry I thought I was in the CM 12 thread duh...
I never posted on this site but a google now card mentioned cm13 on the ole nook tablet so I gave it a whirl.
Clean flashed the 1/18 nightly the other night. Flashed the smallest gapps I could find because the other kept giving me error that not enough space. Was up and running and though bit slow all seemed well.
Tried running cm updater to get the 1/19 nightly but I got a md5 error. So I ended up downloading the nightly. Then I had to move it to the external sd card. Then I dirty flashed it. Everything still worked and no errors except there were no quick tiles when I pulled down from the top. This was fixed by holding the gear icon for a few seconds until it was spinning. After that there were several options that popped up and then the quick tiles were back.
Lastly and the main reason I am here. Is the home screen supposed to be stuck in landscape mode? The lock screen rotates but the home screen does not. Also the clock is not correct and I am unable to change it.
I use ClockWorkMod 6.0.4.5 to flash the roms btw if that matters.
You must change the auto rotate settings for the home screen.
Chris
Auto rotate is on as is 0, 90, and 270 degrees. Also have rotate on lock screen on. Not sure if there is another rotate setting I am not seeing. I will clean flash the next update and see if this fixes it.
Edit: fixed. I did not know about the cm13 menu by holding the screen then swiping up. Rookie mistake.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Flash Indian Stock .ozip roms works
- Flash Roms works
- Mtp works
- Backup works
- .ozip flash
- Android 10 Support
- Android 11 Decryption
Download:
TWRP 3.4.0-10 Unofficial by mauronofrio
TWRP 3.4.0-0 Unofficial by mauronofrio
TWRP 3.3.1-13 Unofficial by mauronofrio
TWRP 3.3.1-12 Unofficial by mauronofrio
TWRP 3.3.1-11 Unofficial by mauronofrio
TWRP 3.3.1-7 Unofficial by mauronofrio
TWRP Official Builds
TWRP 3.3.1-1 Unofficial by mauronofrio
TWRP 3.3.1-0 Unofficial by mauronofrio
To Flash the TWRP:
if it's the first time you flash the TWRP or you are getting problems of TWRP lost or device doesn't boot after flashed magisk or something else you need to flash a script to patch your vbmeta:
VBMETA PATCHER
To flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually.
Flash the VBMETA PATCHER and reboot.
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_realme_RMX1931
Precompiled stock one
Donations:
Credits:
Thanks to @Jerry08 for the testing
Created 2019-11-5
This is not tested, i have not the stock recovery, so before flash directly it, please try to only boot this twrp using:
fastboot boot twrp.img command
Here we go! If this works, this will be my new phone
This is exactly what I was hoping to see, just picked up this phone and can't wait to be rid of ColorOS. Is there a solution available to flash Android 10 on this device? I'd be happy to commit a donation for getting Android 10 working smoothly on this device with full camera support.
hanakon said:
This is exactly what I was hoping to see, just picked up this phone and can't wait to be rid of ColorOS. Is there a solution available to flash Android 10 on this device? I'd be happy to commit a donation for getting Android 10 working smoothly on this device with full camera support.
Click to expand...
Click to collapse
Would also love stock Android or oxygenOS. Full camera support while keeping the super macro mode. I'm not sure if that's a feature on other phones but really like it. At 50% battery as I type this with almost 9 hours of use and lil over 4 hours on on screen time. Best battery life I've had in a phone and to top it off or charges incredibly fast.
Did anyone test this? If twrp works, then it will not be far from getting a few custom roms for this device. I really hope this works since if it does, I'm buying this phone immediately!
How to unlock bootloader? , i haven't found anything about boot loader unlock for realme X2 pro yet. We can't flash twrp with locked bootloader right?
Try this?: https://realmeroot.com/how-to-unlock-the-boatloader-in-realme-x2-pro/.
kaminsky.victor said:
Try this?: https://realmeroot.com/how-to-unlock-the-boatloader-in-realme-x2-pro/.
Click to expand...
Click to collapse
Not working , cannot install that app
Is this TWRP working on Realme X2 (RMX1991)?
ospeto said:
Not working , cannot install that app
Click to expand...
Click to collapse
Yet i did get the phone....
But...
There is an option on developers menue which i guess it should be toggled: link is below...
https://www.hardreset.info/devices/realme/realme-x2-pro/developer-options/
---------- Post added at 11:42 PM ---------- Previous post was at 11:39 PM ----------
shamllakh said:
Yet i did get the phone....
But...
There is an option on developers menue which i guess it should be toggled: link is below...
https://www.hardreset.info/devices/realme/realme-x2-pro/developer-options/
Click to expand...
Click to collapse
Also, i found this on RealmeX2Pro china forum:
https://www.realmebbs.com/post-deta...06252043546624&subForumId=1181409566403866624
shamllakh said:
Yet i did get the phone....
But...
There is an option on developers menue which i guess it should be toggled: link is below...
https://www.hardreset.info/devices/realme/realme-x2-pro/developer-options/
---------- Post added at 11:42 PM ---------- Previous post was at 11:39 PM ----------
Also, i found this on RealmeX2Pro china forum:
https://www.realmebbs.com/post-deta...06252043546624&subForumId=1181409566403866624
Click to expand...
Click to collapse
One guy on RealmeX2Pro china forum reported A Success Bootloader Unlock, here is his method link:
https://www.realmebbs.com/post-deta...06252043546624&subForumId=1181409566403866624
shamllakh said:
One guy on RealmeX2Pro china forum reported A Success Bootloader Unlock, here is his method link:
https://www.realmebbs.com/post-deta...06252043546624&subForumId=1181409566403866624
Click to expand...
Click to collapse
That's great , but I'll just wait for xda 's method to be sure. I hop we can get custom ROMs soon. Ported oxygen os or AEX would be great. That Color OS is not good. I am experiencing some notification and permission bugs now.
Just tried, and the phone won't go in bootloader mode. The 'adb reboot bootloader' do nothing :/
Thanks @nathan30 for testing!
I downloaded the package from that chinese website which was linked by @ospeto
I translated the folders inside the zip with google to english, since many people have issues with chinese characters in their file structure but in case anyone needs the original files, I kept the chinese zip as well.
Download English zip:
http://www.mediafire.com/file/qdkqs577zskml9k/realme_X2_pro_Eng.zip/file
Download Chinese zip:
http://www.mediafire.com/file/yrlhze0l5ahzd7n/realme_X2_pro_Ch.zip/file
If anyone can test this, please report back.
Thank you guys!
EDIT: There is a google translated bootloader unlocking guide in the zip.
SethPDA said:
Thanks @nathan30 for testing!
I downloaded the package from that chinese website which was linked by @ospeto
I translated the folders inside the zip with google to english, since many people have issues with chinese characters in their file structure but in case anyone needs the original files, I kept the chinese zip as well.
Download English zip:
http://www.mediafire.com/file/qdkqs577zskml9k/realme_X2_pro_Eng.zip/file
Download Chinese zip:
http://www.mediafire.com/file/yrlhze0l5ahzd7n/realme_X2_pro_Ch.zip/file
If anyone can test this, please report back.
Thank you guys!
EDIT: There is a google translated bootloader unlocking guide in the zip.
Click to expand...
Click to collapse
I could try but have you and idea about the phone which don't boot in bootloader mode ?
Is this TWRP working on Realme X2 (RMX1991)?
MTsv DN said:
Is this TWRP working on Realme X2 (RMX1991)?
Click to expand...
Click to collapse
Definitely not, don't you see this is for the Pro?
MTsv DN said:
Is this TWRP working on Realme X2 (RMX1991)?
Click to expand...
Click to collapse
I don't think it will work, maybe i can make a dedicated version
mauronofrio said:
This is not tested, i have not the stock recovery, so before flash directly it, please try to only boot this twrp using:
fastboot boot twrp.img command
Click to expand...
Click to collapse
Do you think you will get the stock recovery to test your Twrp ?
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.
HTML:
#include <std_disclaimer.h>
/*
* 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 recovery
* before flashing it! YOU are choosing to make these modifications, and if
* y
Let’s start with the installation process
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Now you need to overwrite vbmeta partition, so you can flash third party partitions. Download vbmeta_disabled.tar then go into download mode on your device. Put vbmeta_disabled.tar to userdata in Odin, click start. This should finish pretty quickly, so pay attention when your device reboots, because you need to boot into recovery (Hold power and volume up after the screen turns black). When booted into recovery, wipe your data and reboot normally into system. Now you can setup your phone as usual and make sure oem unlocking is still greyed out and enabled!
Time to flash recovery. Download (link is at the end of this post). . In Odin put the tar file in AP and simply hit start. Congrats you now have TWRP installed!
BOOT TO TWRP RECOVERY AND MAKE FORMAT DATA AND WIPE SYSTEM
Developers specific details
Sources
https://github.com/blacktox/r1q
https://github.com/Grarak/android_bootable_recovery-1
vbmeta_disabled
https://drive.google.com/file/d/1_Ws71h--Z7YBGfllsbt8qlJElXRxTB1p/view?usp=sharing
twrp based on A805FXXU4BTC3 so you must on firmware binary 4
https://drive.google.com/file/d/1FkYQY_O7daPFX6lWt66Bn-aXadRrDWez/view?usp=sharing
XDA:DevDB Information
twrp galaxy a80, Tool/Utility for the Samsung Galaxy A80
Contributors
blackbuga
Version Information
Status: Testing
Created 2019-11-09
Last Updated 2020-07-03
Awesome! Where do I get the vbmeta.tar file?
Nazato said:
Awesome! Where do I get the vbmeta.tar file?
Click to expand...
Click to collapse
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases/download/3.3.1-3/vbmeta.tar
Sent from my SM-A805F using XDA-Developers Legacy app
blackbuga said:
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases/download/3.3.1-3/vbmeta.tar
Sent from my SM-A805F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Just got it to boot and the touchscreen is unresponsive. Quite a bummer since twrp is the only way to root as far as I've concluded :crying:
Nazato said:
Just got it to boot and the touchscreen is unresponsive. Quite a bummer since twrp is the only way to root as far as I've concluded :crying:
Click to expand...
Click to collapse
Rename it to recovery.img then compress to tar file and flash it
Fixed touchscreen
When reboot twrp flash again this img as image in boot to complete rooting
https://www.mediafire.com/file/ccix57wmz61crzd/magisk_patched.img/file
Sent from my SM-A805F using XDA-Developers Legacy app
blackbuga said:
Rename it to recovery.img then compress to tar file and flash it
Fixed touchscreen
When reboot twrp flash again this img as image in boot to complete rooting
https://www.mediafire.com/file/ccix57wmz61crzd/magisk_patched.img/file
Sent from my SM-A805F using XDA-Developers Legacy app
Click to expand...
Click to collapse
I followed your steps to no avail. First try, twrp didn't even boot up completely as it was stuck in the twrp logo screen. My second attempt was wiping data first using the stock recovery, then flashing twrp. Twrp booted up and I was happy as heck, but the touchscreen was unresponsive. I've completely set up my phone again after giving up. I wouldn't mind losing all my data again just to gain root, but I don't want to lose it for nothing
Now it just doesn't load further than the logo! !(
UPLOAD NEW BUILD
FIX TOUCHSCREEN
https://github.com/blacktox/r1q/releases/download/TWRP/recovery.img
blackbuga said:
UPLOAD NEW BUILD
FIX TOUCHSCREEN
https://github.com/blacktox/r1q/releases/download/TWRP/recovery.img
Click to expand...
Click to collapse
Thanks for fixing the issues! Bummer that I can't root. It's just stuck on bootloop with the Samsung splash image.
You must as sg7 firmware
Then flash twrp recovery
Open magisk manager and patch this recovery.img
And reboot to twrp instal image seltect magisk patched and flash it at boot
Wipe all and reboot
Now you have twrp and rooted
For patching recovery with magisk use this custom source
https://github.com/blacktox/work/blob/master/ianmacd.json
For patching with magisk 19.4
Sent from my SM-A805F using Tapatalk
blackbuga said:
You must as sg7 firmware
Then flash twrp recovery
Open magisk manager and patch this recovery.img
And reboot to twrp instal image seltect magisk patched and flash it at boot
Wipe all and reboot
Now you have twrp and rooted
For patching recovery with magisk use this custom source
https://github.com/blacktox/work/blob/master/ianmacd.json
For patching with magisk 19.4
Sent from my SM-A805F using Tapatalk
Click to expand...
Click to collapse
Thanks, man! This finally worked. Any way I can donate to you or something like buy you a beer or what
Is anything working? Decryption? Back-up? Restore?
I have saw the a70 page and it included many custom roms. Is it easy to port it over to the a80? I really want lineage os on my phone. Thanks
(I have an SM-A8050)
@blackbuga ; how about detail explaining about sg7 firmware how can we get it? what about give us step by step way of unlocking until flash twrp within provided link donwload files we needed, & last could u gv us stock recovery img for emergency used while we faced some trouble like bootloop or something else we dont expected. so we dont needed to flash whole firmware stock & make us felt safety & shortcut the time of we got trouble. thx for great works
Hello blackbuga,
I recently installed your unofficial TWRP-build for the A80.
I want to let you know that it is impossible to flash ROMs successfully. I am a TouchWiz developer since 2016 and I wanted to continue with OneUI.
So, I was porting the A71 firmware, but it didn't let me install the zip. It ended with the Error 7.
Here's a part of the log:
" -- Setting ROM Permissions
ApplyParsedPerms: removexattr of /system/system/usr/srec/en-US/wordlist.syms to 0 failed: Operation not supported on transport endpoint
ApplyParsedPerms: removexattr of /system/system/usr/srec/en-US/wordlist.syms to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Updater process ended with ERROR: 7 "
It seems like it's a problem of the recovery. I hope to get an answer from you.
Greetings
Soon i realase new build recovery
Im waiting samsung realase new source s4 or u4
blackbuga said:
Soon i realase new build recovery
Im waiting samsung realase new source s4 or u4
Click to expand...
Click to collapse
Will this solve the above mentioned problem, or don't you know what the problem might be?
n0tavailable said:
Will this solve the above mentioned problem, or don't you know what the problem might be?
Click to expand...
Click to collapse
probelme related to your port not from recovery
edit the permission
Is it possible to installieren android 10 GSI i allways in bootloop and restart in recovery
Nazato said:
Thanks, man! This finally worked. Any way I can donate to you or something like buy you a beer or what
Click to expand...
Click to collapse
Bro @Nazato, could you write steps by steps to root A80 please...
Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
I’d recommend to read everything in this post, if you care about your phone.
If you already unlocked your bootloader, start with step 3.
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Flash Galaxy A20e TWRP.tar via Odin or heimdall
Reboot into TWRP AS SOON AS THE FLASHING PROCESS IS DONE because otherwise TWRP will get replaced with the stock Android recovery
If you want to flash a GSI, skip to step 7
Factory reset in TWRP and reboot to stock
Wipe everything in TWRP excluding SD Card / USB OTG
Put a GSI image file onto an SD Card, alongside GSI_Fix_boot.zip and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Flash the GSI image, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, flash GSI_Fix_boot.zip, wipe cache and reboot.
Enjoy
Current bugs
Encryption/Decryption on stock does not work, you cannot read the internal storage while using the stock firmware
ADB and USB connection / USB OTG does not work
Latest release: https://drive.google.com/file/d/1Nbrmn7BgA3BxA1bqnLXYMuCY4KjpR0Vn/view?usp=sharing
Social media
Twitter: https://twitter.com/xyn_dev
Telegram: https://t.me/xyn_dev
Reserved.
Wow finally... thx a lot for that
Xyn XDotnest said:
Reserved.
Click to expand...
Click to collapse
Great work
Can you now install GSIs
Make sure you backup boot, data, system before you start
physwizz said:
Great work
Can you now install GSIs
Make sure you backup boot, data, system before you start
Click to expand...
Click to collapse
Yep, GSIs work, I am currently using Descendant X on mine.
Xyn XDotnest said:
Yep, GSIs work, I am currently using Descendant X on mine.
Click to expand...
Click to collapse
Beautiful
I'm stuck at GSI (PixelExperience) installation. I've extracted the img file on sd card and the wizard is asking which partition should be used to flash image (boot,recovery,product image,system image,vendor image).
ZemoDroid said:
I'm stuck at GSI (PixelExperience) installation. I've extracted the img file on sd card and the wizard is asking which partition should be used to flash image (boot,recovery,product image,system image,vendor image).
Click to expand...
Click to collapse
System
A few Questions about the process
Xyn XDotnest said:
Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
I’d recommend to read everything in this post, if you care about your phone.
If you already unlocked your bootloader, start with step 3.
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Flash Galaxy A20e TWRP.tar via Odin or heimdall
Reboot into TWRP AS SOON AS THE FLASHING PROCESS IS DONE because otherwise TWRP will get replaced with the stock Android recovery
If you want to flash a GSI, skip to step 7
Factory reset in TWRP and reboot to stock
Wipe everything in TWRP excluding SD Card / USB OTG
Put a GSI image file onto an SD Card, alongside GSI_Fix_boot.zip and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Flash the GSI image, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, flash GSI_Fix_boot.zip, wipe cache and reboot.
Enjoy
Current bugs
Encryption/Decryption on stock does not work, you cannot read the internal storage while using the stock firmware
ADB and USB connection / USB OTG does not work
Latest release: https://drive.google.com/file/d/1Nbrmn7BgA3BxA1bqnLXYMuCY4KjpR0Vn/view?usp=sharing
Social media
Twitter: https://twitter.com/xdotnest
Telegram: https://t.me/dotnest
Click to expand...
Click to collapse
,
Hey thanks for this, I´ve got a few questions about the process that might also help others.
Do you recommend this method of rooting still over the new method using Magisk?
Do we still need to wipe everything in TWRP after first boot? And what specifically steps should we take to wipe?
Can you recommend any specific GSI images that are known to boot on the A20e (A202F) because so far I've tried LineageOS 17.1 / AOSP system -quack-arm64-ab-gapps.img and system -quack-arm64-ab-vanilla.img / Crdroid and nothing gets past the loading icon.
Do we still need to flash Disable_Verity_ForceEncrypt and GSI_Fix_boot.zip if not installing a GSI ?
a few notes
for anyone else. It helps if you boot into the rom and install magisk manager via APK (recent version is fine) before installing it via TWRP. After I did that rooting worked properly.
Lost ADB for some reason though, might be unrelated.
I also think that the a20e (SM-a202f) is an A device and not an A/B partition device at least according to treble check app.
ADB and USB connection / USB OTG does not work
Click to expand...
Click to collapse
oh.....right. that stinks
moogle said:
,
Hey thanks for this, I´ve got a few questions about the process that might also help others.
Do you recommend this method of rooting still over the new method using Magisk?
Do we still need to wipe everything in TWRP after first boot? And what specifically steps should we take to wipe?
Can you recommend any specific GSI images that are known to boot on the A20e (A202F) because so far I've tried LineageOS 17.1 / AOSP system -quack-arm64-ab-gapps.img and system -quack-arm64-ab-vanilla.img / Crdroid and nothing gets past the loading icon.
Do we still need to flash Disable_Verity_ForceEncrypt and GSI_Fix_boot.zip if not installing a GSI ?
Click to expand...
Click to collapse
1. This method does use Magisk
The tar file contains boot.img patched with Magisk
It also contains recovery.img and vbmeta.img
2. The boot.img is from Android 10 firmware so you need to upgrade to Q first.
3 there is a step missing in the instructions
It should say
6. Reboot the A20e into TWRP and mount everything you can.
Click Wipe then Format Data (not just wipe) - don't restart
Flash Disable_Dm-Verity_ForceEncrypt
Reboot to recovery and wipe both caches
Reboot system .
Click to expand...
Click to collapse
You can then backup boot, data and system for stock.
You can then install GSIs
I'm having some major problems with sd cards not being recognized by google play store as external storage and whatsapp unable to download images. any idea what it might be?
moogle said:
I'm having some major problems with sd cards not being recognized by google play store as external storage and whatsapp unable to download images. any idea what it might be?
Click to expand...
Click to collapse
What OS are you running?
physwizz said:
What OS are you running?
Click to expand...
Click to collapse
Just the stock android 10, I didn't find a GSI that worked for me.
moogle said:
Just the stock android 10, I didn't find a GSI that worked for me.
Click to expand...
Click to collapse
try Crdroid
physwizz said:
try Crdroid
Click to expand...
Click to collapse
Already have, and LOS 17.1 and AOSP system-quack-arm64-ab-vanilla
all of them got stuck at boot icon for an hour. Thats why I went back to stock.
I'm more interested in why I cannot seem to install discord or firefox from the app store, or whatsapp cannot download images.
moogle said:
Already have, and LOS 17.1 and AOSP system-quack-arm64-ab-vanilla
all of them got stuck at boot icon for an hour. Thats why I went back to stock.
I'm more interested in why I cannot seem to install discord or firefox from the app store, or whatsapp cannot download images.
Click to expand...
Click to collapse
Go into magisk and hide any apps that misbehave
physwizz said:
Go into magisk and hide any apps that misbehave
Click to expand...
Click to collapse
Tried it, no change, there's no apps misbehaving, just strange sd storage card behaviour
Is the SM-A202F/DS supported by these methods, I noticed in some other threads it wasn't working back in March, that's the unit I have.
moogle said:
Tried it, no change, there's no apps misbehaving, just strange sd storage card behaviour
Is the SM-A202F/DS supported by these methods, I noticed in some other threads it wasn't working back in March, that's the unit I have.
Click to expand...
Click to collapse
There is a fix here
https://forum.xda-developers.com/showpost.php?p=80184282&postcount=2
physwizz said:
There is a fix here
https://forum.xda-developers.com/showpost.php?p=80184282&postcount=2
Click to expand...
Click to collapse
Which part are you referring to in that thread?
OrangeFox Recovery Project
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 MIUI and Custom Roms
Credits
* OrangeFox Recovery Project Team
* @LUNARIO, who did ALL the work, but sadly opened a thread violating the rules and the link to Recovery was deleted and the thread moved. Original here.
FEATURES:
* Touch Screen every single time
* Decryption works
* Fixed Error 7 while clean or dirty flashing (starting from version 6)
* Migrate backup installation (starting from version 6)
* OTG support
* ROM Flashing works 100%
* F2FS Support
* Fastboot commands supported
NOT WORKING FOR NOW:
* Fastbootd
* ADB Sideload
* Backing up and restoring Image Flash (system-vendor-product)
DOWNLOAD
Version 6 - Google: https://drive.google.com/file/d/1eHM9ST9ni-55bbT3z-TGSZQsgE3KYr9s/view
OLD VERSION DOWNLOAD
Version 4 - Google: https://drive.google.com/file/d/1Qq6hqaEOstxajOC7Y6AGeRYajhMWjttL/view
Version 0 - Sourceforge: https://sourceforge.net/projects/or...x-R11.0_0_Alpha-Unofficial-surya.img/download
INSTALLATION
1. Download the OrangeFoxRecovery IMG file to your PC.
2. Restart your POCO X3 in Fastboot mode (Power+Vol Down)
3. Use ADB and type in the following command:
Code:
fastboot flash recovery "OrangeFox-R11.0_6_Alpha-Unofficial-surya.img"
4. After it is installed successfully, type in this command:
Code:
fastboot boot "OrangeFox-R11.0_6_Alpha-Unofficial-surya.img"
5. The device will automatically reboot into OrangeFox Recovery after installation (allow this to happen)
6. Enjoy!
Version Information
Status: Alpha
Alpha Release Date: 2020-10-14
Does it support dd commands to backup/flash persist.img?
I tried but after I flashed xiaomi eu and went back to recovery, the touchscreen would't work
hope this gets updated i like this recovery
olujnap316 said:
hope this gets updated i like this recovery
Click to expand...
Click to collapse
here you can download updated version, I have this flashed for around one week... so far so good, but still adb sideload not working... dunno what other bugs are there... I am flashing with this NitrogenOS.... zero problems for me so far...
jeryll said:
here you can download updated version, I have this flashed for around one week... so far so good, but still adb sideload not working... dunno what other bugs are there... I am flashing with this NitrogenOS.... zero problems for me so far...
Click to expand...
Click to collapse
yes i saw that on telegram. but why is it not updated on this thread.
olujnap316 said:
yes i saw that on telegram. but why is it not updated on this thread.
Click to expand...
Click to collapse
oh, you were talking about the thread itself, sorry... but the recovery itself will work the same regardless number of posts here on xda or telegram... I personally don't care where are new versions announced...
Not affiliated
olujnap316 said:
yes i saw that on telegram. but why is it not updated on this thread.
Click to expand...
Click to collapse
Because sadly I am not the developer and I cannot post Telegram links here.
I can update manually, as long as any of you guys DM me the link to the Telegram group, so I can join.
@jeryll @olujnap316
Can anyone of you guys provide the Telegram link for me to update the thread more often?
Best regards,
billabongstaff said:
Because sadly I am not the developer and I cannot post Telegram links here.
I can update manually, as long as any of you guys DM me the link to the Telegram group, so I can join.
@[email protected]
Can anyone of you guys provide the Telegram link for me to update the thread more often?
Best regards,
Click to expand...
Click to collapse
@POCox3OfficialUpdates just search that on telegram, they posted the latest orangefox there
Thank you
olujnap316 said:
@POCox3OfficialUpdates just search that on telegram, they posted the latest orangefox there
Click to expand...
Click to collapse
Thank you, man.
I appreciate it.
I'll try to keep the thread updated.
Best regards,
Are there any written instructions anywhere on how to run the adb tools and commands precisely? Total noob here
nikolaos8 said:
Are there any written instructions anywhere on how to run the adb tools and commands precisely? Total noob here
Click to expand...
Click to collapse
of course there are, you can use Google search with the exact query you posted here and you can then choose where to start learning or click here...
nikolaos8 said:
Are there any written instructions anywhere on how to run the adb tools and commands precisely? Total noob here
Click to expand...
Click to collapse
Very good for Beginners. ▼
For ADB
https://android.tutorials.how/adb-commands/#adb_devices_command
For FASTBOOT
https://android.tutorials.how/fastboot-commands/
Update.
New build is up.
Version 6.
Fixes error 7 while clean or dirty flashing.
Backup migration now works.
Cheers.
Thanks guys. Made small instructions video for the absolute noobs (me included).
Tools used: https://developer.android.com/studio/releases/platform-tools
Instructions on adb commands and flashing:
1. Bootloader Unlocked
2. Download the latest Orangefox boot.img from first post and put it into a dedicated folder in your computer.
3. Go to the folder where you have put the Orangefox-file. Now open a command window inside that folder. To do that hold together "Shift + Right click" on any empty white space inside the folder and then select "Open PowerShell Window Here" or "Open Command Window Here" (depends on your pc).
4. Enter fastboot mode by holding together "Volume Down + Power" and connect your device to your computer
5. Enter the terminal command in command line: >>fastboot flash recovery OrangeFox-R11.0_6_Alpha-Unofficial-surya.img
(Needs to be exactly as the name of the file, in case developer uploads new version with new name)<<. Attention: Do not restart your device otherwise Xiaomi's original recovery might overwrite Orangefox!
6. After, device will reboot into Oangefox recovery.
Video Tutorial: https://youtu.be/E7fl_02Kgc8
I had also downloaded the latest Magisk zip (not Manager) from here: https://github.com/topjohnwu/Magisk/releases and placed it into the device before flashing Orangefox, so that i flash Magisk directly from recovery (as we left it above), in order to ensure it will not lose Orangefox installation after reboot.
In case it does not automatically reboot, hold +VOL + Power Button in order to reboot into the new orangefox recovery and install magisk zip from there ( do not forget to have it downloaded somewhere on your device before initiating the procedure)
Thanks everyone, especially OP for his contributions!
Factory reset /wipe prevents userdata to be decrypted? For twrp after you do a factory reset you have to format userdata even without password/pin inside the OS.
Can i backup persist partition with this recovery?
Hi!
I'm getting the error "Failed to map file" while I try to flash Magisk in this recovery.
Any help?
Hope this recovery will be official soon ! I don't know why there is no stable built yet of twp or yours ! I'm waiting for it to flash !
Jess182 said:
Can i backup persist partition with this recovery?
Click to expand...
Click to collapse
Yes you can using dd.