Question [Solved] Narzo 30A stuck in bootloop, no access to Recovery/Fastboot - Realme Narzo 30A / Narzo 20 / Realme Realme 7i EU

I had just unlocked my phone's bootloader, installed a custom recovery based on TWRP, and a custom ROM (PixelExperience).
I was using the phone just fine until I restarted it into recovery,
ever since, it's been rebooting none stop
But now I have no way to access my recovery/adb/fastboot
I can only put in Download Mode
I tried flashing via Download Mode using SP Flash Tool, but I have been receiving STATUS_BROM_CM_SEND_DA_FAIL error.
Is there any way to fix it?

After trying every tool out there + potentially having infected my pc with some virus (Hopefully that's solved too), I managed to bring my Narzo 30A to life.
To anyone facing this problem : your best bet would be an after-sales services,
Otherwise, if you're as desperate as I was (This really is a last resort option, since it could totally brick the phone as far as I know), here's what I did:
> I downloaded & installed
* All required drivers MTK drivers, VCOM...
* SP Flash Tool (spflashtool.com),
* mtk_bypass_rev4 from MobileGuru4.com
* The official ROM (.OZIP format) - I could access it using Winrar
* PBRP recovery (Based on TWRP)
> I then extracted in a folder (let's call it "C:/Flash/"):
* recovery.img from PBRP
* preloader_emmc.img, boot.img & vbmeta.img from the Stock ROM
> I looked for the appropriate Scatter + .AUTH + MT6768.DA files for my device and found them on the net
> I opened SP Flash tool,
* Used the MT6768.DA, scatter and auth files I downloaded
* Ticked only preloader, recovery, vbmeta & boot and associated each one to its relevant .img file (that I previously extracted)
* I entered into EDL mode
* I opened mtk_bypass_rev4
* Chose my MT model (mine's MT6768)
* Clicked on Bypass
* Once it said the bypass succeeded, I clicked on Download on SP flash tool
* Waited till it finished flashing
* After rebooting, my bootloader + recovery were restored

Related

Prestigio 3404 need stock boot.img, and system.img (for flash using fastboot)

I tried to install custom rom on my phone. Flashed wrong recovery, after changed to working recovery (which i had previously) phone didnt detect sim cards. I think it was because of system so thats why need system.img. And boot.img because read somewhere to flash boot.img using fastboot, so flashed and phone have bootloop now. Thank you from the mountain. So I think if i flash boot.img and system.img with fastboot it will work fine again.
EDIT: Found stock rom at russian forums gsmforums.ru and 4PDA forum
Phone working but I still have problem that it can't read SIM cards. It's dual sim and both sim cards don't working tried with some other cards and don't work too. Someone have any idea? It's wrong recovery flash problem? :/ Because phone can't read cards since i flashed wrong recovery and returned to working one. Thanks, hope for fast reply.
Help
I have found the ROM but it would be helpful if you could link it too. I haven't flashed android before and don't know how to do it properly, so it would be of great help if you could tell me how you did it. I have tried few things but with no success.
MM3100 said:
I have found the ROM but it would be helpful if you could link it too. I haven't flashed android before and don't know how to do it properly, so it would be of great help if you could tell me how you did it. I have tried few things but with no success.
Click to expand...
Click to collapse
Sorry for the really late reply, but I've bought 3 new phones already in the meantime so I stopped watching the forum for the solution. Here's the link for the stock rom: https://cloud.mail.ru/public/d126368659a8/KK_4.4.2_stock_ Prestigio 3404 Duos.7z You should be able to download it without any problems. If You encounter some problems then tell me in next reply and I'll upload the rom to the other hosting site. Next thing You should download is a file from this link: https://cloud.mail.ru/public/c1e9138eac6e/backup.7z It contains scatter file which includes required info for SP Flash Tool to flash the image. Extract both files to the same folder on Your desktop so it'll be easier to find them. To flash the rom You have to download and install SP Flash Tool. It would be best if You'd follow the tutorial on YouTube like this one: https://www.youtube.com/watch?v=5CxDF2pkdCQ Here's the link to SP Flash Tool official site: https://spflashtool.com/ In the flashtool You should select download agent which is inside the tool folder and is most likely named something like "MTKallinoneDL". Then You should select scatter file from the rom folder which is named something like "mt6752_android_scatter" The next step is to select the "download only" option from the menu. You should follow the video on how to install the drivers and what steps You should take to connect the device correctly to the pc. So once again:
1. Download all the files and extract them:
* https://cloud.mail.ru/public/d126368659a8/KK_4.4.2_stock_ Prestigio 3404 Duos.7z << stock rom
* https://cloud.mail.ru/public/c1e9138eac6e/backup.7z <<scatter file etc.
* https://androidfilehost.com/?fid=24269982087012126 <<mtk preloader drivers
* https://spflashtool.com/download/SP_Flash_Tool_v5.1824_Win.zip << Latest version of SP Flash Tool
2.Install the MTK preloader drivers as shown in the video: https://www.youtube.com/watch?time_continue=219&v=sADkzyI8Z5Q
3.Open SP Flash tool and select download agent, scatter file and select "download only" option from the drop down menu. (NOTE: You should open SP Flash Tool as administrator to avoid any problems)
4.Select checkboxes for ANDROID, BOOTIMG, RECOVERY.
5.Click the downlaod button (before connecting Your phone)
6.Connect Your phone without battery to Your pc.
7.Now wait untill the message window pop-ups with "download OK" message.
If You have trouble using the SP Flash Tool here's another video: https://www.youtube.com/watch?v=OKpt0TLE6_A NOTE: If You flash Your phone with "FORMAT ALL AND DOWNLOAD" You could erase Your IMEI partition which will result in another problems with phone calls etc. It's best if You select download only and select only these 3 partitions I mentioned earlier. If You encounter any problems please let me know in Your future reply.

[Guide][Stock][Recovery] Stock Recovery for OnePlus Nord

Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you're 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.
*/
I have extracted Stock Recovery for OnePlus Nord, Currently tested in Indian Version. EU and Global users please test it if you can.
There are two methods to restore stock recovery TWRP or Fastboot
Requirements:
- Working ADB and Fastboot (e.g. Google's Platform Tools)
- TWRP Backup or Stock Recovery
Steps for TWRP:
- Download archive from AFH
- Extract the content of archive, There will be a folder named 'BACKUPS'.
- Paste 'BACKUPS' directly into TWRP folder in your Internal Storage.
- Boot into TWRP and restore the recovery partition.
- Reboot
- Profit
Steps for Fastboot
- Download Recovery image from AFH
- Open terminal in your ADB folder
- type "adb reboot bootloader"
- Copy stock recovery image you have downloaded to your ADB folder
- type "fastboot flash recovery <file-name>.img where filename is the name of img file you have downloaded.
- Reboot
- Profit
Mirrors:
TWRP Backup
Recovery Image
I have extracted the backup by booting into TWRP and backing up the recovery partition. The img file has been extracted from my device with dd command.
Enjoy.
Reserved
**Reserved**
im in PixelExperience rom i want to go back to oxygen os can i do this method? or i will use msm tools?
Did somebody check the recovery with the EU model?
Or maybe have the EU recovery....
(I want to go full stock OOS11 after the Pixel Experience)
JD00 said:
Did somebody check the recovery with the EU model?
Or maybe have the EU recovery....
(I want to go full stock OOS11 after the Pixel Experience)
Click to expand...
Click to collapse
You can do it through unbrick tool for EU region. Unbrick tool for EU is only with android 10. You can flash it firstly and after that update to android 11.
Where can I get the "unbrick tool for EU region"?
robdg80 said:
Where can I get the "unbrick tool for EU region"?
Click to expand...
Click to collapse
Here

[GUIDE] Unlock, Flash TWRP, and Root X50 Pro (A42)

Please read this guide fully before attempting to follow it. It requires some knowledge of how to use a Terminal and basic ADB/Fastboot operation. I don't think this guide is thorough enough for a person who's modifying their phone for the very first time. Feel free to ask for help though!
I am not reliable for any adverse effects this guide might have on your phone. If something breaks, that's your responsibility. However: if your phone doesn't boot anymore, but you can still get into fastboot, you should be able to flash the Stock Firmware OFP using the Realme Flash Tool. To get into fastboot, power off your phone, wait a few seconds, and hold power and volume down until you see the fastboot logo.
This guide was cobbled together using various other tutorials and my own attempts. I've used it on my RMX2075. It should also work for the RMX2076. The files Realme provides for the RMX2075 are named "RMX2076", so I assume they're the same device. I have no idea how the RMX2071 fits into this. Curiously, the TWRP version used here is intended for the RMX2071, although it works flawlessly on my RMX2075. However: if you're using it on an RMX2075/2076 TWRP thinks you're using an RMX2071, so it won't flash packages intended for the RMX2075/2076. Hence the following warning:
!!! YOU WON'T BE ABLE TO INSTALL OTA UPDATES AFTER INSTALLING TWRP !!!
If you attempt to install an OTA Update downloaded from within the Settings.app, the phone will reboot, TWRP will attempt to install the OTA Update and fail with an error. This does not break anything, it just doesn't update.
DOWNLOADS:
- Realme Flash Tool
- Stock Firmware OFP
- OTA Update OZIP
- TWRP 3.4.1b for RMX2071 by wzsx150 and LR. Team
Spoiler: further details
The licensing of this TWRP is pretty unclear, so I can't provide a download link. If you search for it Online, make sure to find a version that includes both "recovery.img" and "misc.bin"
- Realme DeepTesting App
- Magisk Manager by topjohnwu
- oppo ozip decrypt
PREPARATION:
- install ADB & Fastboot on your computer
- enable "USB debugging" on your phone
- install the oppo ozip decryption tool by following the instruction on the GitHub page
UNLOCKING
- follow the unlock instructions provided by the official Realme Tutorial
RESTORING AND UPDATING - if you're on firmware A42, skip this step
- follow the restore instructions provided by the official Realme Tutorial
- go to the Realme Software Update page, click on "How to update?" and follow the instructions
FLASH TWRP
- open a Terminal window and cd into the folder that holds recovery.img and misc.bin
cd /path/to/folder
- enter the following commands and hit enter after each
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash misc misc.bin
fastboot reboot recovery
- your phone should now reboot into TWRP
- enter your phones unlock code if you have one
- go to "Advanced" -> "Disable Replace TWRP"
- reboot phone
ROOTING
DO NOT use "Install Root" in TWRP, it'll "destroy" the bootloader and you'll have to flash the stock firmware
Follow this instead:
- decrypt the OTA .ozip using the oppo ozip decrypt tool (instructions on its GitHub page)
- unzip the resulting decrypted file
- copy "boot.img" onto your phone
- copy "/firmware-update/vbmeta.img" into a folder of your choice
- install Magisk Manager on your phone
- open Magisk Manager, tap on "Install" followed by "Select and Patch a File"
- select the "boot.img" you've previously copied onto your phone and let Magisk do its thing
- the patched "boot.img" is called "magisk_patched_XXXX.img" or something similar. Make note of the resulting file name which is specific to you.
- copy the patched "magisk_patched_XXXX.img" into the same folder that holds your "vbmeta.img"
- open a terminal and cd into the folder that holds the patched "boot.img" and "vbmeta.img"
- enter the following commands and hit enter after each
adb reboot bootloader
in the following step, replace "magisk_patched_XXXX.img" with whatever your patched "boot.img" is called
fastboot flash boot magisk_patched_XXXX.img/ICODE]
[ICODE]fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
- your phone should now be rooted
I have also uploaded the stock boot.img along with the rooted version as well as vbmeta.img here. They were created using the method described above with OTA update A42. I would recommend creating your own though, since this has a higher chance of success.
Another method to get the stock boot.img and vbmeta.img is creating a TWRP backup, renaming "boot.emmc.win" to "boot.img", and "vbmeta.emmc.win" to "vbmeta.img". I have NOT TESTED this method.
I don't know if this will work for Android 11 / ColorOS 2.0. My theory is that if you can get the RMX2076PU_11.C.16.ozip somewhere, you could just follow this guide using it instead of the A42 one. Again, I have NOT TESTED this method.
Unfortunately does not work with Android 11. The result is that the phone stays in the fastboot. The Realme flash tool doesn't work anymore. The phone is now bricked. Let's see if I can reach the service now. Isn't the first time they haven't answered. Now actually needs the MSM tool. But haven't found a working one yet.
corneo said:
Unfortunately does not work with Android 11. The result is that the phone stays in the fastboot. The Realme flash tool doesn't work anymore. The phone is now bricked. Let's see if I can reach the service now. Isn't the first time they haven't answered. Now actually needs the MSM tool. But haven't found a working one yet.
Click to expand...
Click to collapse
Android 11twrp brush Android 10, and then brush Android 10twrp, you can boot
can u using volte with stock ofp eu version?

[RECOVERY][3.6.0-11][RMX1931]Unofficial TWRP for RUI2 - Realme X2 Pro (Stable)

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!

[STARTER GUIDE][SM-G531F]Guide for Modding the SM-G531F

Hello everyone! This is your Starter Guide for modding the SM-G531F!
(This document is based on: GuestD2581 guide. =))
DRIVERS & UTILITIES
Odin [v3.13.1]
Samsung USB Drivers [Link]
__________________________________________________
STOCK ROM , BOOT & RECOVERY IMAGES
[Link]
__________________________________________________
CUSTOM RECOVERY [TWRP]
TWRP 3.1.1-0 : img
TWRP 3.0.2-0 : tar
TWRP 2.8.7.1 : img | tar
__________________________________________________
CUSTOM ROM
Linage OS 13.0
__________________________________________________
CUSTOM KERNEL
[Link]
__________________________________________________
ROOT
•MAGISK
XDA | GITHUB​
MagiskManager-v7.5.1.apk
Magisk-v20.4.zip
Magisk-uninstaller-20200323.zip
MUST HAVE MAGISK MODULES​•SUPERSU
CHAINFIRE | SUPERSU RELEASE​
SuperSU-v2.82-201705271822.zip
•MUST HAVE ROOT APPS
__________________________________________________
XPOSED [WANAM]
XposedInstaller_3.1.5.apk
xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125.zip
xposed-uninstaller-20160211.zip
XPOSED MODULE REPOSITORY​
MUST HAVE XPOSED MODULES​__________________________________________________
ZIPS
FRP Destroyer
Lock Screen Fixer
__________________________________________________
THEMES
THEME CHOOSER S6Plus
????? Theme| G531F | 5.1.1
__________________________________________________
TUTORIALS
FLASH STOCK ROM , TWRP , ROOT & XPOSED​
Note :- *Before starting backup all your data to an external storage
*Your warranty would be void after rooting
*Do some research on risks of rooting such as "Bootloops" and "Bricking" (a bricked phone is completely unusable)
_____________________________________________
1.Download and install Samsung USB Drivers
2.Download Odin and extract (no installation is needed)
_____________________________________________
3.Download latest Firmware and extract it once
4.Run Odin (make sure the only checked Options are "Auto reboot" and "F.Reset Time" make sure "RE-Partition" is not checked
5.Now click on AP and pick your Firmware file (in .tar.md5 format)
6.First Enable Developer Options (go to Settings > About phone> tap 7 times on build number) Then enable "OEM Unlock" and "USB debugging"
7.Now reboot to Odin/Download mode turning off your device and holding VOLUME DOWN + HOME + POWER button simultaneously until you see a disclaimer on the screen then press Volume Up to continue
8.Connect USB cable to the phone , text "Added" should appears in Message box in Odin , click Start and wait to complete , when it shows "Pass" you can disconnect the cable , wait for autoreboot (of the device) and you are done!
_____________________________________________
Note :- *Before flashing Custom recovery you must remove your google account(by going into settings>accounts) to turn off FRP lock
*It is better to have a Factory reset (rather than removing google account) to have a clean start
_____________________________________________
9.Download latest TWRP (.tar) , again reboot to odin/download mode and flash it using the same AP button in Odin but remember to untick auto reboot and make sure repartition is not checked
10.After flashing don't do a normal reboot , After the flash has succeeded disconnect the usb cable, then power down the phone by holding the power button for 10 sec , once it's powered off use the VOLUME UP + HOME + POWER button combo to boot directly into recovery. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP
(If you don't follow this step, you will have to repeat the install)
_____________________________________________
Note:- After having a custom recovery flashed when you sign in your google account and the next time you boot into recovery (or sometimes a normal boot) you will get a message "custom binary blocked by FRP lock" and your phone will not boot after this and you have to flash the firmware again to get out of this
So, before adding your google account you have to flash a zip called "FRP Destroyer" (by Zillinium) which completely removes the FRP partition
Hence,you can have a custom recovery and google account added at the same time
_____________________________________________
11.Get Magisk Manager APK and Magisk zip file
12.Boot into recovery (TWRP) and install the zip file then wipe cache/dalvic and then reboot your phone
13.The Magisk framework is now installed on your device. To manage it, you’ll need Magisk Manager App
_____________________________________________
Note :- Make a NANDroid backup in TWRP (allows you to restore your phone to the exact condition at backup)
So if anything goes wrong with further modding, you'll be able to restore all of your apps and settings to working order in no time
_____________________________________________
14.Install Xposed installer app like you normally would
15.Flash "xposed.zip" file through TWRP.
Reboot and Wait, it may take several minutes to boot up depending on your Rom size.
__________________________________________________
Code:
Before using this guide:
*** Disclamer
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.
A lot.
Check my website, because why not: web.galaxxyafonso.codes​
Reserved

Categories

Resources