/*
* 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 before asking or use anything on this thread.
*/
OxygenOS 11.3 A.15 EU Full Stock Firmware for OnePlus Nord 2Requirements :
ADB & Fastboot + Google & MTK drivers
Partitionsbackupper ( @Raygen )
A.15 Firmware ( @AssoDiPicche )
Instructions :
Download the .zip and the latest version of PartitionsBackupper.
Download A.15 Firmware, extract it and put all files in the PartitionsBackupper folder.
Reboot your phone in fastboot mode (Power off, than power button + volume down)
Run PartitionsBackupper.bat, choosing the restore option, to flash all partitions with fastboot.
I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.
Type on command line "fastboot flashing lock"
Enjoy your brand new OPNord2.
Credits:
@Raygen (For PartitionsBackupper)
@AssoDiPicche (To die with this phone for two days)
AssoDiPicche said:
/*
* 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 before asking or use anything on this thread.
*/
OxygenOS 11.3 A.15 EU Full Stock Firmware for OnePlus Nord 2Requirements :
ADB & Fastboot + Google & MTK drivers
Partitionsbackupper ( @Raygen )
A.15 Firmware ( @AssoDiPicche )
Instructions :
Download the .zip and the latest version of PartitionsBackupper.
Download A.15 Firmware, extract it and put all files in the PartitionsBackupper folder.
Reboot your phone in fastboot mode (Power off, than power button + volume down)
Run PartitionsBackupper.bat, choosing the restore option, to flash all partitions with fastboot.
I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.
Type on command line "fastboot flashing lock"
Enjoy your brand new OPNord2.
Credits:
@Raygen (For PartitionsBackupper)
@AssoDiPicche (To die with this phone for two days)
Click to expand...
Click to collapse
now I try to do the operation
The file it's in the same folder. Where i wrong?
Cugno83 said:
The file it's in the same folder. Where i wrong?
Click to expand...
Click to collapse
Change your ADB tool. try "Tiny ADB and Fastboot".
Ok, i restored all and lock bootloader. the guide is not really step by step, but it can work with a minimum of knowledge
Cugno83 said:
Ok, i restored all and lock bootloader. the guide is not really step by step, but it can work with a minimum of knowledge
Click to expand...
Click to collapse
please send me pm and tell me what you did!
Can i reflash stock oxygenOS rom and return completely stock without locking the bootloader? I flashed elixir, but the wifi doesn't work, so i would like to turn on stock, maybe doing root and installing magisk, viper ecc... Is there a complete oxygen that i can flash with maybe sideload on twrp or things like that?
Andrea17982 said:
Can i reflash stock oxygenOS rom and return completely stock without locking the bootloader? I flashed elixir, but the wifi doesn't work, so i would like to turn on stock, maybe doing root and installing magisk, viper ecc... Is there a complete oxygen that i can flash with maybe sideload on twrp or things like that?
Click to expand...
Click to collapse
If you use this, you must unlock bootloader and install twrp aftet that.
I did it, and the bat told me he flashed everything without problem, but then it rebooted me to twrp, and my bootloader is still unlocked, but most importantly, when i go "reboot system" it stays on oneplus logo and no os start... So I'm semi bricked now without OS, at least I have twrp to make some experiment... ideas? I retry the same thing?
Edit: the phone booted... with Elixir OS (?) so nothing changed, still my wifi and bluetooth don't work...
Andrea17982 said:
I did it, and the bat told me he flashed everything without problem, but then it rebooted me to twrp, and my bootloader is still unlocked, but most importantly, when i go "reboot system" it stays on oneplus logo and no os start... So I'm semi bricked now without OS, at least I have twrp to make some experiment... ideas? I retry the same thing?
Edit: the phone booted... with Elixir OS (?) so nothing changed, still my wifi and bluetooth don't work...
Click to expand...
Click to collapse
Try ask in "nord 2 community" telegram group. They are really helpful.
Try to press 1 botton. And use image of dn2103.zip
Don't try restore your backup file. Try restore file unzipped of a.15 firmware, and you return to stock and lock bootloader
Hi! I have a some problem! The first part of the firmware is fine, and after a reboot this happens
Same problem here.
Error with flashboot command.
Please put the "PartitionsBackup" folder with all the partition images in the same directory of this script.
----------------------------------------
Errors were detected while running the script.
You can find the error logs in the "PBlog.txt" file.
Press any key to continue . . .
I have tried this and it worked, partly. The process stopped on flashing vendor and nothing happened for hours. So I disconnected the phone and it boots fine. I can set up everything, but updates fails. It's now on A15 and will not update. I have also tried to lock the bootloader again, but then the phone won't boot at all, something about an error to boot/system. If I unlock the bootloader, it works again.
Something is clearly wrong here. How can I restore my device back to full working stock again?
I was on A17 before installing TWRP + PixelExperience Rom. But when I wanted to return to stock all hell broke loose
jadajada said:
I have tried this and it worked, partly. The process stopped on flashing vendor and nothing happened for hours. So I disconnected the phone and it boots fine. I can set up everything, but updates fails. It's now on A15 and will not update. I have also tried to lock the bootloader again, but then the phone won't boot at all, something about an error to boot/system. If I unlock the bootloader, it works again.
Something is clearly wrong here. How can I restore my device back to full working stock again?
I was on A17 before installing TWRP + PixelExperience Rom. But when I wanted to return to stock all hell broke loose
Click to expand...
Click to collapse
Any luck?
shivbizle said:
Please put the "PartitionsBackup" folder with all the partition images in the same directory of this script.
----------------------------------------
Errors were detected while running the script.
You can find the error logs in the "PBlog.txt" file.
Press any key to continue . . .
Click to expand...
Click to collapse
I've got the same error! Trying to restore my phone from a PixelExperience overheating and camera nightmare
Should I "Read Partitions" in mtkclient only the ones that are present in mtkclinet and not the A.15 firmware file?
Thanks a lot, this really saved me!
After flashing I got error: "The current image(boot/recovery have been destroyed and can not boot."
And here is how I got around that:
It was possible to boot into fastboot mode only after shutting down the phone first. (from recovery)
And then pressing the key combination while powering up.
Then I ran "fastboot flashing unlock" to get around that "error with fastboot command".
and then I flashed boot and vbmeta with the fastboot command. After that It finally booted.
Then I locked the bootloader and installed all the updates.
Related
Help!! My LG V30 V300L Can't Boot
Boot Show LG LOGO alway.
can't boot entrance.
i try Press hold Power+Volum down = restart.
i try Press hold Power+Volum up = notrespone.
i try Press hold Volum up+put charge = notrespone.
i need to off device.
:crying::crying::crying::crying::crying:
Same problem here buddy!
I have bricked my LG V30 purchased on eBay by following this guide: https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
It has a booloop and I can't go to fastboot, download or recovery. When I go to download the screen goes black and Windows detects it as Qloader 9008
At the time of purchase I made sure it was the us998 version but it is refurbished and maybe not its real model. I have two possible causes in mind. The first one that the flashing model does not correspond to my model. The second one that flashes the latest version of Magisk from its website and not from the post
Is there any solution I can reach? I have been reading to extract the dkz and flash the images of the partitions with LG Flash Tool but I don't know if that would work in my case
A greeting!!
mariets said:
Same problem here buddy!
I have bricked my LG V30 purchased on eBay by following this guide: https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
It has a booloop and I can't go to fastboot, download or recovery. When I go to download the screen goes black and Windows detects it as Qloader 9008
At the time of purchase I made sure it was the us998 version but it is refurbished and maybe not its real model. I have two possible causes in mind. The first one that the flashing model does not correspond to my model. The second one that flashes the latest version of Magisk from its website and not from the post
Is there any solution I can reach? I have been reading to extract the dkz and flash the images of the partitions with LG Flash Tool but I don't know if that would work in my case
A greeting!!
Click to expand...
Click to collapse
What stage were you at, when it bootlooped? What were you flashing at the time?
Have you tried Master Reset?
https://forum.xda-developers.com/showpost.php?p=76429682&postcount=101
Yes you should use the Magisk in the instructions. You can update later.
Qualcomm 9008 in Device Manger needs Octoplus box to JTAG flash your device to recover. Ebay service has 2 offerings (one from Florida and another from Moldova). I used the guy from Florida (Tennolee) and he did a great job. He messaged me via Ebay and asked me to install Teamviewer. Once my PC has that and my phone is hooked up to USB 2.0, he remotely logged in and install needed software to JTAG this sucker remotely. He had all the KDZ's and you can ask for any versions for your phone you want. He can't do H932 though (no one can apparently)
ChazzMatt said:
What stage were you at, when it bootlooped? What were you flashing at the time?
Have you tried Master Reset?
https://forum.xda-developers.com/showpost.php?p=76429682&postcount=101
Yes you should use the Magisk in the instructions. You can update later.
Click to expand...
Click to collapse
You are a light of hope along the way, friend. These are the points that I followed. Looking at it with perspective. It was an installation disaster. Anything could have failed.
OK * flash twrp: fastboot flash TWRP.img (TWRP-3.2.3-7-default.img re-named as just "TWRP.img")
OK * boot twrp: fastboot boot TWRP.img (TWRP-3.2.3-7-default.img re-named as just "TWRP.img")
OK* swipe to allow modifications (do NOT leave read-only, TWRP NEEDS to be able to make changes to your system.)
OK* select WIPE data
Really I did a full wipe. I know. No sense. * wipe caches
OK * flash Magisk
OK * flash encryption disabler
I did not install it because de official github was down - * flash root check disabler
OK * FORMAT DATA, type yes
OK * reboot to TWRP
OK * re-flash Magisk
DEAD * reboot to system
EDIT: I tried frankenstein. I'm on twrp now and ****ing freaking out!!!! I will keep informing
EDIT: I only haved flash a firmware like the one I had initially (in my case March 8, 2018) prepared for twrp and and followed the WTF guide step by step with calm and has worked. I'm now in HavocOS!! I had a little scare when the twrp has entered bootloop after flash gapps. I've solved it by simply forcing reboot pressing vol +, vol- and power on
Thanks a lot ChazzMatt, i'm blessed and I learned a valuable lesson about material things and flash calmly
God luck, @Ritazizy
A greeting
mariets said:
You are a light of hope along the way, friend. These are the points that I followed. Looking at it with perspective. It was an installation disaster. Anything could have failed.
OK * flash twrp: fastboot flash TWRP.img (TWRP-3.2.3-7-default.img re-named as just "TWRP.img")
OK * boot twrp: fastboot boot TWRP.img (TWRP-3.2.3-7-default.img re-named as just "TWRP.img")
OK* swipe to allow modifications (do NOT leave read-only, TWRP NEEDS to be able to make changes to your system.)
OK* select WIPE data
Really I did a full wipe. I know. No sense. * wipe caches
OK * flash Magisk
OK * flash encryption disabler
I did not install it because de official github was down - * flash root check disabler
OK * FORMAT DATA, type yes
OK * reboot to TWRP
OK * re-flash Magisk
DEAD * reboot to system
EDIT: I tried frankenstein. I'm on twrp now and ****ing freaking out!!!! I will keep informing
EDIT: I only haved flash a firmware like the one I had initially (in my case March 8, 2018) prepared for twrp and and followed the WTF guide step by step with calm and has worked. I'm now in HavocOS!! I had a little scare when the twrp has entered bootloop after flash gapps. I've solved it by simply forcing reboot pressing vol +, vol- and power on
Thanks a lot ChazzMatt, i'm blessed and I learned a valuable lesson about material things and flash calmly
God luck, @Ritazizy
A greeting
Click to expand...
Click to collapse
OK, glad you got it figured out!
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?
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM/Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Working Features:
- Decryption Works
- Backup works
- Wipes Work
- MTP
- ADB
- OTG
- RUI 2 ozip Flashing
- RUI 1 ozip flashing
Not Working:
- No f2fs support yet
- Not tested on CN variants (Can't confirm working status)
Flashing Guide:
Patched VBMETA is must to boot a twrp , so flash the below image to successfully boot this recovery and make it available even after booting back to RealmeUI.
Download Links:
TWRP Download Link
VBMETA Link
To flash TWRP:
fastboot flash recovery twrp-3.6-RUI2-RMX1931-final.img
Flash the VBMETA using below commands
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_path.img
ADB and Fastboot Drivers:
ADB and Fastboot Installer
Source code:
https://github.com/TeamWin/android_bootable_recovery
https://github.com/arnodorian-r/recovery_realme_RMX1931
https://github.com/arnodorian-r/kernel_realme_sm8150
Credits:
Thanks to @mrtechnophile2.0 , Roy for the testing
Thanks @pjgowtham @XiaoAk for guiding me
The best thing ever happened for realme ui 2. Great work mate..!
Finally, a proper working Recovery for our device
Wow...Finally Working TWRP for RMX1931 on RUI2.
Thanks alot bro.
Can I flash this, when I'm on Lineage-18.1?
zheka99 said:
Can I flash this, when I'm on Lineage-18.1
Click to expand...
Click to collapse
Technically its possible...but you should do it after roms released based on rui2 firmware. If not , you will endup with broken OS. For now dont flash custom roms with this recovery.
can i flash magysk to optine root, wich version?
Isavar said:
can i flash magysk to optine root, wich version?
Click to expand...
Click to collapse
Magisk-92546e8a(23016) from CANARY all Ok!
Sorry for my English. And thank you very much for your work. I have the mobile with the latest version of rui2 and with root done following this guide:
https://forum.xda-developers.com/t/...fix-rui-2-0-android-11-global-indian.4371041/ When I went to install twrp, the mobile only started in twrp , and I had to reinstall everything. I used realme flashtool and refollowed the guide to get me back up and running properly. What could have happened?
Leozgz85 said:
Sorry for my English. And thank you very much for your work. I have the mobile with the latest version of rui2 and with root done following this guide:
https://forum.xda-developers.com/t/...fix-rui-2-0-android-11-global-indian.4371041/ When I went to install twrp, the mobile only started in twrp , and I had to reinstall everything. I used realme flashtool and refollowed the guide to get me back up and running properly. What could have happened?
Click to expand...
Click to collapse
Hi
was the same for me, had to reinstall everything, only started in TWRP. Would like to install the recovery but I don't feel like this error anymore.
Thanks. It's working.
Doesnt work for me, i cant boot to realme ui after flashing the vbmeta, i got stuck on recovery. (f.14)
This recovery is broken for me, it gives me no space left on sdcard even after a full data reformat, ozip extraction stops after 500mb.
It's just not working as it should 3.4 works best
arnodorian-r said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM/Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Working Features:
- Decryption Works
- Backup works
- Wipes Work
- MTP
- ADB
- OTG
- RUI 2 ozip Flashing
- RUI 1 ozip flashing
Not Working:
- No f2fs support yet
- Not tested on CN variants (Can't confirm working status)
Flashing Guide:
Patched VBMETA is must to boot a twrp , so flash the below image to successfully boot this recovery and make it available even after booting back to RealmeUI.
Download Links:
TWRP Download Link
VBMETA Link
To flash TWRP:
fastboot flash recovery twrp-3.6-RUI2-RMX1931-final.img
Flash the VBMETA using below commands
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_path.img
ADB and Fastboot Drivers:
ADB and Fastboot Installer
Source code:
https://github.com/TeamWin/android_bootable_recovery
https://github.com/arnodorian-r/recovery_realme_RMX1931
https://github.com/arnodorian-r/kernel_realme_sm8150
Credits:
Thanks to @mrtechnophile2.0 , Roy for the testing
Thanks @pjgowtham @XiaoAk for guiding me
Click to expand...
Click to collapse
I followed this guide and many others in the past 48 hours, with no success. Every time I flash TWRP and the VBMETA, I get stuck in TWRP bootloop.
I started unblocking the bootloader, rolling back to RUI1 - Android 9 and using the Deep-Test App.
After the roll back, I got the phone unblocked right, but then first soft-brick, with only bootloader available and no way to flash a working ROM. After some searches, I've finally managed to unbrick, using OPPO flash tool, and installing stock rom RMX1931_11_F.14_2021102817443142.
This gives me a working phone, RUI.2 - Android 11. Standard recovery.
I tried to flash TWRP and got the phone soft bricked again, in TWRP recovery bootloop.
I'd like to install TWRP and from there going to OrangeFox and finally install Lineage 19.1...
How can i first have a working TWRP recovery??? If you can support also following steps, would be amazing. Thank you!!!
I went few step further... but still I am not able to install a working custom recovery for my realme X2 pro.
I have now also rooted my device with magisk.
I just need a custom recovery to perform 2 actions:
- make a NANDroid backup;
- install a custom ROM.
Any advice? Thank you for your time!
Installed. Working like a charm with lineage 19.1. Only problem: can't access files in storage. Digging into the matter, it seems to be an issue with android 12's new encryption method, which can't be overriden by this version of the recovery. There's a brand new TWRP 3.7.0_9.0 in the official TWRP website which boasts to overcome this problem but, whenever I try to install it (with or without the vbmeta.img provided for version 3.6.0_11), the recovery won't start. Guess a new vbmeta.img is needed as everything goes ok reinstalling TWRP 3.6.0_11 and its corresponding vbmeta. Tried to extract and install vbmeta.img from the lineage zip file without success. Shall we have to patch vbmeta.img? How can we do that? Through Magisk? I've come across some "vbmeta patcher" apk... Am I pointing the right way?
can any one help me to unlock bootloader in realme x2 pro . i am on RUI 10 . i installed in depth tool it said seccesful but no bootloader just keep rebooting and showing fast boot for a moment .. help please i search every where for fix but no way to yet
I'm using the CN variant device, which I understand does not yet have confirmed support, nonetheless sharing the error I'm encountering in case it's a simple or obvious fix I'm missing.
Having followed all above steps, I'm able to flash and get into TWRP recovery, but decryption always failed (even after a dozen tries) with the following:
"Attempting to decrypt FBE for user 0...
Failed to decrypt user 0"
Much obliged for any insight on this. I'm attempting to get back on OF after successfully installing Lineage 19.1, which broke the OF recovery, and since OF needs to be installed as a ZIP, I need to get some version of TWRP working as an intermediary. Specifically this is because I didn't install GAPPS along with Lineage 19.1 (I misread the opening post, which seemed to imply that GAPPS was included in that particular ROM). So alternatively, if there's another way to get GAPPS onto the device without recovery (sideload won't work since I can't decrypt...) then that would be helpful too.
Thanks in advance for any insight on this!
It has stayed on this screen, it does not allow access to: volume down / up + power, volume down+power, volume up+power.
No fastboot access. Mode BROM Yes.
Logo screen turns on and off, but you can't turn off the phone.
to turn off
press and hold:
volume + and volume - and power
Help me in this problem!
I have boot.img pached with Magisk and i have updated my Oneplus Nord 2
now the phone is in bootloop
no access in fastboot volume + and power
I also had a problem with the latest update, oxygenos 12 auto installed itself on my Nord 2 EU. This broke fastboot and removed root.
The phone still works, but trying to boot into fastboot gives a serial error and the phone reboots back into the os. Any suggestions? Did anyone manage to snag a copy of the update zip?
I have copied the 4.5 Gb update on the computer.
My knowledge is very limited and with this phone I am very angry. I use google translate.
I used the re_livdvdv5 with the MTK client to reroot mine, pulled the stock boot.img, patched with magisk, and wrote it back to the phone, worked fine for me to reroot. To recover your phone, i suspect you can probably flash that zip image with the mtk client, or downgrade back to os 11
If you have BROM then you can use MTKclient to flash what you need to unbrick your device, regardless of what's wrong with it
Download the ready-to-use Live DvD file from here https://github.com/bkerler/mtkclient#use-re-livedvd-everything-ready-to-go-based-on-ubuntu and use Rufus to make a bootable USB thumbdrive from https://rufus.ie/en/
Once you have MTKclient setup and working you will have a functioning method to flash any .img files needed to recover your phone, check out the details in the thread I embedded below, it is likely you will need a stock recovery.img file, a stock vbmeta.img file, and then you will need to track down the stock boot.img for the current operating system of your phone.
As always, make sure to use mtkclient or the Partitions backup tool to backup everything you can, especially the persist.img which contains calibration data unique to your own device, if you wipe your own data in this partition by accident no one will be able to help you. There are also other partitions with similarly unique data that should also be backed up (full ist of these are: seccfg, nvcfg, nvdata, nvram, persist, proinfo, protect1 and protect2 partitions)
As your error happened in the middle of an update, I would suggest you grab multiple boot.img files for both the previous and new version that your phone was trying to install, as you can't be fully certain if the update was succesful, so just try flashing multiple versions of the boot.img file for all the various versions, only the correct version will unbrick your device.
Luckily, to the best of my knowledge, the recovery.img and vbmeta.img should be the same across both versions.
Good luck. You can post in the following thread as well if you run into issues with the unbrick method, but getting MTKclient working and sourcing the correct .img files to flash is 99% of the difficulty here, with the remaining 1% the trial and error flashing various boot files to see which one works for you.
[STOCK][FULL-ROM] OxygenOS_11.3_A.20 EU DN2103 | Unbrick guide
/* * 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 yourself before asking or use anything on this...
forum.xda-developers.com
My partition userdata 107.12 Gb.
Can i delete it directly?
edulcorante1 said:
My partition userdata 107.12 Gb.
Can i delete it directly?
Click to expand...
Click to collapse
During the unbrick process you will be reformatting/wiping your device so you will lose all your data. If you wish to keep your data, you can back it up, or if you're willing to lose it all and install and setup all your data again, it's up to you.
You don't need to back it up if you don't want to, but it'll contain all your old apps, appdata, and photos/videos etc