[RECOVERY][UNOFFICIAL] TWRP for Galaxy A71 (Snapdragon) - Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 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:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy A71 SM-A715F, SM-A715U, SM-A715U1, SM-A715V and SM-A715W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download A71: a71.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
Link
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
GitHub History

after unlock bootloader and root, fingerprint doesnt work.
how to fix it ?
thank you in advance

kevin mitnick said:
after unlock bootloader and root, fingerprint doesnt work.
how to fix it ?
thank you in advance
Click to expand...
Click to collapse
Dont use Ian multidisabler.

afaneh92 said:
Dont use Ian multidisabler.
Click to expand...
Click to collapse
I reflashing rom and reflashing twrp and not used ian multidisabler. but fingerprint still not fixed. please help

kevin mitnick said:
I reflashing rom and reflashing twrp and not used ian multidisabler. but fingerprint still not fixed. please help
Click to expand...
Click to collapse
Try this vbmeta disabler https://drive.google.com/file/d/1-4K--sTHhGY9ekmKd_oiaP0eoGrD4vAf/view?usp=drivesdk

afaneh92 said:
Try this vbmeta disabler https://drive.google.com/file/d/1-4K--sTHhGY9ekmKd_oiaP0eoGrD4vAf/view?usp=drivesdk
Click to expand...
Click to collapse
thank you sir..
I flashed this file, but still ask calibration for finger print and not fixed.

kevin mitnick said:
thank you sir..
I flashed this file, but still ask calibration for finger print and not fixed.
Click to expand...
Click to collapse
So other twrp recoveries are ok?

afaneh92 said:
So other twrp recoveries are ok?
Click to expand...
Click to collapse
I tried your twrp and ian recovery..still same..

Flashing The Twrp on Odin is ok. But when i flash using twrp with zip or img. Always showing in Red error.. reading flashin error..

alpher17 said:
Flashing The Twrp on Odin is ok. But when i flash using twrp with zip or img. Always showing in Red error.. reading flashin error..
Click to expand...
Click to collapse
post recovery log

kevin mitnick said:
I tried your twrp and ian recovery..still same..
Click to expand...
Click to collapse
still working on a fix

Sorry i forgoten my firm version is A715FXXS6BUI1 . Is not supported?

alpher17 said:
Sorry i forgoten my firm version is A715FXXS6BUI1 . Is not supported?
Click to expand...
Click to collapse
should be ok

afaneh92 said:
still working on a fix
Click to expand...
Click to collapse
I bought another a71 mainboard and the problem is still same. finger print need calibration. is that software or hardware problem ? finger print work well before unlock bootloader

kevin mitnick said:
I bought another a71 mainboard and the problem is still same. finger print need calibration. is that software or hardware problem ? finger print work well before unlock bootloader
Click to expand...
Click to collapse
I think disabling encryption broke it. This doesn't effect US devices only international variants on specific models.

afaneh92 said:
I think disabling encryption broke it. This doesn't effect US devices only international variants on specific models.
Click to expand...
Click to collapse
my device is a715fxx.
so, how to fix it ?
please help

kevin mitnick said:
my device is a715fxx.
so, how to fix it ?
please help
Click to expand...
Click to collapse
I cant help you now, as I said above still working on it. dont spam the thread.

@afneh92
afaneh92 said:
I cant help you now, as I said above still working on it. dont spam the thread.
Click to expand...
Click to collapse
Can you help me with something?
I have the TWRP 3.5.1 [ianmacd] recovery installed and a custom Samsung ROM (NcX 3.1.2).
I want to flash the stock firmware via odin to keep the ROM up to date (though without losing data, by flashing the HOME_CSC file).
I'll need to flash TWRP again to install Magisk and Root later via Odin as even though it wont format my data, it will flash on top of my current TWRP.
To install yours, what steps should i follow after i flash the Stock ROM again? (Remember that i wont lose data/need to encrypt the phone again)?

Pupet_Master said:
@afneh92
Can you help me with something?
I have the TWRP 3.5.1 [ianmacd] recovery installed and a custom Samsung ROM (NcX 3.1.2).
I want to flash the stock firmware via odin to keep the ROM up to date (though without losing data, by flashing the HOME_CSC file).
I'll need to flash TWRP again to install Magisk and Root later via Odin as even though it wont format my data, it will flash on top of my current TWRP.
To install yours, what steps should i follow after i flash the Stock ROM again? (Remember that i wont lose data/need to encrypt the phone again)?
Click to expand...
Click to collapse
There is 90% chance to lose data, make data backup move it to PC then try.
Note1: changing vbmeta will lose data so must flash same file.
Note2: if you disabled encryption need to do again.
Ignoring note 1&2 then rebooting to system will lose data

Related

[RECOVERY][ROOT]TWRP 3.2.3-1 Galaxy A7 2018/A750

Unofficial release -TWRP recovery for the Galaxy A7 2018 - SM-A750F EXYNOS 7885
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.2.3-0 Released
Aug 6, 2018
TWRP 3.2.3-0 is out now for most currently supported devices.
What's new in 3.2.3-0:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Update 25/12/2018
Beta build released.
Current status - (Tested working)
Treble supported
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)
2. Load the file below into the AP slot, uncheck AUTO-REBOOT and hit start.
twrp_3.2.3-1_a750_251218
3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
4. Flash the RMM bypass zip
https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
5. Reboot to TWRP (Do not boot to the OS yet)
*****OREO ROOT INSTRUCTIONS:*****
NOTE: To mount data it is necessary to first *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
Continue with the instructions below to prevent the data partition becoming re-encrypted.
1. To root I suggest downloading and installing the latest Magisk as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Copy the Magisk zip to a Micro sd card then install with TWRP.
3. Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, @BlackMesa123 for RMM bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
158 views, 20 downloads and not one reply.
Smashing guys. :good:
4. перепрограммируйте обходной zip- архив rmm.можно поподробнее?
Mod edit: English please!
Google translation:
4. reprogram the rmm bypass zip archive. can you be more specific?
Odin shows Failed !! Tried 3 Times ? Had to Flash the Firmare Again.
Help !!
notoriouschyld said:
Odin shows Failed !! Tried 3 Times Had to Flash the Firmare Again.
Help !!
Click to expand...
Click to collapse
Sorry about that, build error on my end. Fixed now.
It will not work on SM-A750FNXXU1ARIC?
Sfuj24 said:
It will not work on SM-A750FNXXU1ARIC?
Click to expand...
Click to collapse
Is that a statement or question?
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
powermen27 said:
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
Click to expand...
Click to collapse
No matter how complete an instruction is, if you don't bother reading it in the first place it's not going to make any difference.
As clearly posted in the OP:
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Click to expand...
Click to collapse
sorry
ashyx said:
Sorry about that, build error on my end. Fixed now.
Click to expand...
Click to collapse
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
notoriouschyld said:
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
Click to expand...
Click to collapse
Can you tell me which firmware build number you are running and if possible a screen shot of your device screen while booted to download mode?
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
A7whatever said:
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
Click to expand...
Click to collapse
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
https://androidfilehost.com/?fid=11410963190603874542
ashyx said:
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
Click to expand...
Click to collapse
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
A7whatever said:
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
Click to expand...
Click to collapse
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
ashyx said:
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
Click to expand...
Click to collapse
Flashed the old sboot.bin however got the same bootloop
A7whatever said:
Flashed the old sboot.bin however got the same bootloop
Click to expand...
Click to collapse
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
ashyx said:
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
Click to expand...
Click to collapse
Yes
A7whatever said:
Yes
Click to expand...
Click to collapse
Hmm looks like I'll have to take another look at the twrp config or kernel build.
If I pack the kernel into a boot image would you be willing to test if it boots?

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S10 5G (Snapdragon)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 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:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy S10 5G G9770, G977U, G977U1 and G977W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download S10 5G: beyondxq.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
Code:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@Mentalmuso for base device tree
@jesec for unlock guide
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
27.04.2021 - Update to G977PVPU6FUBH kernel source
31.12.2020 - Update TWRP to 3.5.0
20.11.2020 - Initial Release
You can add the G977P/T to the list as working, confirmed working on my G977T.
Is this still good for android 11?
If you need to download the latest version's twrp, you can do it this link(Download TWRP for beyondx)
G977B supported? Android 11?
Yoonwoo said:
If you need to download the latest version's twrp, you can do it this link(Download TWRP for beyondx)
Click to expand...
Click to collapse
This is the wrong one, this is for exynos, we are dealing with snapdragon here.
razercortex said:
You can add the G977P/T to the list as working, confirmed working on my G977T.
Click to expand...
Click to collapse
Just got my G977P, getting info on how to root Android 11 G977PVPS5EUA4, trying not to brick my device. Any tips on how to do it the safe way? First time trying to root Snapdragon device.
Absolutely! You need to first unlock the bootloader, so go into developer options and enable OEM unlock. After you enable it, reboot to DL mode by volume down + power. Select the power keys that allow for unlock and confirm with the displayed key press. After, follow this thread's guide. Then, download Magisk from the official github, it should be from topjohnwu, it will be in apk format, just rename it to zip. Flash in TWRP and you will be good to go!
razercortex said:
Absolutely! You need to first unlock the bootloader, so go into developer options and enable OEM unlock. After you enable it, reboot to DL mode by volume down + power. Select the power keys that allow for unlock and confirm with the displayed key press. After, follow this thread's guide. Then, download Magisk from the official github, it should be from topjohnwu, it will be in apk format, just rename it to zip. Flash in TWRP and you will be good to go!
Click to expand...
Click to collapse
Thanks! Is it safe to update to latest official software update before installing TWRP?
Yes, it shouldn't matter.
razercortex said:
Yes, it shouldn't matter.
Click to expand...
Click to collapse
Confirmed working on G977P, so fast and easy, thanks for the support!
razercortex said:
You can add the G977P/T to the list as working, confirmed working on my G977T.
Click to expand...
Click to collapse
Man I'm at a loss, I've followed this guide and nothing makes sense in terms of.
I'll get twrp installed just fine but the second i reboot my device it'll either throw me back into twrp or I'll get stuck in "Android is starting" and nothing will happen for hours. I'm on G977p and my bootloader is unlocked
Nexu F said:
Man I'm at a loss, I've followed this guide and nothing makes sense in terms of.
I'll get twrp installed just fine but the second i reboot my device it'll either throw me back into twrp or I'll get stuck in "Android is starting" and nothing will happen for hours. I'm on G977p and my bootloader is unlocked
Click to expand...
Click to collapse
Did you flash vbmeta? Also, starting android for the first time takes a really long time.
razercortex said:
Did you flash vbmeta? Also, starting android for the first time takes a really long time.
Click to expand...
Click to collapse
I did yes. I'll try this doing this guide once more later tonight. Could be quite possible I'm missing a step or didn't pay close attention to one since the others with the same Device on this thread reported a success
razercortex said:
Did you flash vbmeta? Also, starting android for the first time takes a really long time.
Click to expand...
Click to collapse
Any rough idea to how long the starting Android could take before i stop it?
Is the SM-G977N korean model supported
Android 11
Do you know how to access OEM Unlock in development. There is no sign of it on this phone.
Thanks
Any updates for Android 12 G977PVPS8HVE1 for SM-G977P (Sprint)? I can see the official firmware already out, but waiting for working version of TWRP.
Yo, idiot. This guide is for Beyondx not Snapdragon. Misleader.....

[Android 11][Recovery][A715F]TWRP 3.5.1 [ianmacd]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* 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.
*/
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Disclaimer:
- I do not claim this work as my own, this thread was created to have an XDA thread for A71 TWRP. I will try my best to keep it up to date with Ian's work, but can't promise that will remain for ever. If you want the latest TWRP and to be notified as soon as its published, be sure to join the Telegram channel.
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox Features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
How to Install:
First, you need to unlock the bootloader. Here's how to do it:
- Backup all media before proceeding, this will erase everything in your internal storage including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash TWRP and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Your bootloader now accepts unofficial images in download mode.
After finally unlocking the bootloader, proceed with installing TWRP (tar) with Odin:
- Boot to download mode and load TWRP tar file and VBMeta disabler tar file in AP and BL of Odin, doesn't matter which goes where
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL+, VOL - and POWER buttons at the same time
- After the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to TWRP
- After booting to TWRP successfully, go to WIPE in TWRP
- At the bottom, you should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops.
(Optional) Flash magisk.zip to root (google where to find it)
- Reboot to system
- Wait patiently for the device to boot for the first time
How to flash TWRP (img):
- Reboot to recovery
- Select Install
- Select Install Image and search for the TWRP img file
- Flash as recovery
- Reboot to recovery
- Done
Downloads:
twrp-a71-3.5.1_10-A11_2b1_ianmacd.img
twrp-a71-3.5.1_10-A11_2b1_ianmacd.tar
Multidisabler zip by Ianmacd
VBMeta disabler
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
Change log:
17/03/21: Release for Android 11 BL
Credits:
- Samsung for kernel source code
- TeamWin for their awesome recovery
- @ianmacd for compiling, updating, and maintaining for A71
reserved 1
reserved 2
Sorry for the delay, this TWRP should work perfectly with Android 11 BL
Thanks! However, it kept encrypting after booting to Recovery? Already format and flash Multidisabler zip by Ianmacd.
After several tries, it did not encrpt any more. It really beats me. Anyway, great job. Thanks!
@ShaDisNX255 have you came across config files for Link to Windows / Your Phone Companion, namely something to do with features enabled ?
Now that A71 got OneUI 3.1 (A11) I was wondering if there is a way to enable multi-apps in Link to Windows.
I also wonder if this "multi-apps" new feature in A11 needs to be enabled in OneUI too (or maybe there isn't a Link to Windows special toggle at all, only system one).
All I know is that only the high tier Samsung phones has multi-apps streaming to Windows, like S21, Note20, Fold and Z Flip but also last gen S20 and Note10.
Would like to hear your thoughts on this.
EDIT: the backbone of the feature is this: https://www.xda-developers.com/android-q-splitscreen-multitasking-multi-resume/
donkeyman1234 said:
Thanks! However, it kept encrypting after booting to Recovery? Already format and flash Multidisabler zip by Ianmacd.
After several tries, it did not encrpt any more. It really beats me. Anyway, great job. Thanks!
Click to expand...
Click to collapse
Very strange. Hopefully your issue is fixed, I'll try and see what could be wrong. Thanks for the input.
ban.codrut said:
@ShaDisNX255 have you came across config files for Link to Windows / Your Phone Companion, namely something to do with features enabled ?
Now that A71 got OneUI 3.1 (A11) I was wondering if there is a way to enable multi-apps in Link to Windows.
I also wonder if this "multi-apps" new feature in A11 needs to be enabled in OneUI too (or maybe there isn't a Link to Windows special toggle at all, only system one).
All I know is that only the high tier Samsung phones has multi-apps streaming to Windows, like S21, Note20, Fold and Z Flip but also last gen S20 and Note10.
Would like to hear your thoughts on this.
EDIT: the backbone of the feature is this: https://www.xda-developers.com/android-q-splitscreen-multitasking-multi-resume/
Click to expand...
Click to collapse
I haven't used the Link to Windows feature, I don't really have a good understanding of what you mean.
ShaDisNX255 said:
Very strange. Hopefully your issue is fixed, I'll try and see what could be wrong. Thanks for the input.
Click to expand...
Click to collapse
I took a shot of log.
I'm running stock Android 11 and I've tried to make a backup with TWRP but failed with this message:
Can create '/data/media/o/TWRP/ folder (required key not available).
Failed to make backup folder.
It means that I'm encrypted, right ??. If I'm correct, should I format data and flash the new multidisabler ?
EDIT: on A10 it was unencrypted, flashing A11 encrypted it again?
viktor92 said:
I'm running stock Android 11 and I've tried to make a backup with TWRP but failed with this message:
Can create '/data/media/o/TWRP/ folder (required key not available).
Failed to make backup folder.
It means that I'm encrypted, right ??. If I'm correct, should I format data and flash the new multidisabler ?
EDIT: on A10 it was unencrypted, flashing A11 encrypted it again?
Click to expand...
Click to collapse
Yes, you must format and flash multidisabler.
Question, i went though the bootloader unlock but the option don't appear grey out on the dev menu, what should i do to really unlock it?
Edit:
Ok i manage to do it but idk how to reboot in to TWRP, is it vol+ and power? it isn't working
Pupet_Master said:
Question, i went though the bootloader unlock but the option don't appear grey out on the dev menu, what should i do to really unlock it?
Edit:
Ok i manage to do it but idk how to reboot in to TWRP, is it vol+ and power? it isn't working
Click to expand...
Click to collapse
Android 11 changes the way it works
Now, it is necessary to be connected to a PC to boot to recovery with that combination of keys.
ShaDisNX255 said:
Android 11 changes the way it works
Now, it is necessary to be connected to a PC to boot to recovery with that combination of keys.
Click to expand...
Click to collapse
Thanks Friend
I have a Samsung A71 Anroid 11 and I'm also trying to root it. Everything you have written I understand, up to this point:
"- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops."
I answer "Yes" and than at the next screen I only can choose between Back or Reboot. How must I flash at this stage the Multidisabler?
Must I go back to the TWRP main menue to the Point "install"?
Greetings from Cologne
Germany
Norbert
Nobby52 said:
I have a Samsung A71 Anroid 11 and I'm also trying to root it. Everything you have written I understand, up to this point:
"- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops."
I answer "Yes" and than at the next screen I only can choose between Back or Reboot. How must I flash at this stage the Multidisabler?
Must I go back to the TWRP main menue to the Point "install"?
Greetings from Cologne
Germany
Norbert
Click to expand...
Click to collapse
Yes, you have to go back to the main menu
Thank you, I'll try it again.
Norbert
Unfortunately, this method doesn't work for me. I've tried rooting three times. It went through every time without any errors. The device was not rooted afterwards. The smartphone then triggered a reset every few minutes when it was operated. What can I do?
Greetings from Cologne
Norbert
Nobby52 said:
Unfortunately, this method doesn't work for me. I've tried rooting three times. It went through every time without any errors. The device was not rooted afterwards. The smartphone then triggered a reset every few minutes when it was operated. What can I do?
Greetings from Cologne
Norbert
Click to expand...
Click to collapse
What ROM are you trying to root?
Are you Rooting with Magisk or Super SU? Do you install SUper SU App or Magisk Manager after?
About the reset, did you flash the multiboot disabler after flash the root zip file?
I root the original Samsung Stock Rom. "A715FXXU3BUB5_A715FOXM3BUB6_DBT". I followed the instructions here exactly.
First unroot and debug mode
1.) download mode
2.) with Odin TWRP + VBMeta-Disabler
3.) TWRP started, wipe, then yes, then back to install, Multidisabler.zip flashed.
4.) restarted
That was it
I don't have a Super_SU or Magisk installed
greeting
Norbert

How To Guide [GUIDE][REALME 8i][NARZO 50] Unlock Bootloader Flash TWRP and Root [RMX3151][RMX3286]

Hi Guys!
Since there is no deeptest.apk available for our device to unlock bootloader, we came up with another method to unlock bootloader unofficially!
In this guide I'll tell you how to unlock bootloader, root with magisk and flash TWRP on your Realme 8i/Narzo 50 (RMX3151/RMX3286)
Code:
/*
* This Guide is tested and working
* However 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 unlocking and flashing TWRP
* before flashing it! YOU are choosing to make these modifications.
*/
1. UNLOCKING BOOTLOADER:
Requirements
PC or Laptop
Internet connection
Realme 8i/Narzo 50
USB cable
Working Brain
Take a backup of your data since it'll be wiped
Go to About phone > Version and tap build number 7 times
Go to Settings > advanced settings > Developer options and turn on OEM unlocking and USB debugging
STEPS
Install Python from windows store
Install USBDk
Download this and extract : https://github.com/bkerler/mtkclient/archive/refs/heads/main.zip
Download vbmeta and patched boot image (Download for your respective version) in copy to the mtkclient-main folder
Now open command prompt or powershell in that folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now type pip3 install -r requirements.txt and hit enter
Now type python mtk e metadata,userdata,md_udc hit enter - This command wipes data
Then power off your phone and hold both volume buttons and connect usb cable (DON'T LEAVE THE BUTTONS, KEEP THEM HOLDING THROUGHOUT THE PROCESS) - This boots device into BROM mode
Now type python mtk da seccfg unlock This will unlock the bootloader (If you face waiting for device issue then unplug the device and plug in the device again with holding volume buttons, also don't leave the buttons)
After this unplug your phone and turn it on (It'll show your device dm verity corrupted and first boot might take 20-25 mins, don't panic)
Now your bootloader is unlocked
Due to realme's limitations you still can't access fastboot after unlocking via this method
2. ROOTING YOUR DEVICE:
Install This Magisk apk
Now in pc type python mtk w boot,vbmeta boot.patched,vbmeta.img.empty hit enter
Then power off your phone and connect usb while holding both volume buttons (and don't leave them)
Now disconnect and reboot phone
Now open magisk
3. FLASHING TWRP RECOVERY:
Download TWRP - From here
Download and install Flashify app
Open Flashify and grant root permission
Select Recovery image and install the twrp you have downloaded
After flashing is done click reboot now or you can reboot to recovery via magisk app
"Congrats Now we have working TWRP in our Realme 8i/Narzo 50"
Credits:
Me (@pritish1998) for TWRP, Unlock and Flashing guide
B Kerler fot MTKClient
Rohit for testing
Stock boot Images (to revert root)
If you face any issues contact me here
Thanks for the detailed guide, hope we get kernel sources soon..
sany.svenson said:
Добрый вечер.А как теперь заблокировать загрузчик,подскажите пожалуйста.
Click to expand...
Click to collapse
English is required, you can use your native language too, adding it to your post.
Inside the tool is provided a README.md file with basic instructions and usage. To relock bootloader you can use python mtk xflash seccfg lock just be careful to not relock it while running custom binaries, you have to return completely back to stock prior to do that.
After using boot.img from this topic wifi is dead! Now I need original boot to patch it. My firmware is A20. Somebody help!
DimaS_EKB said:
After using boot.img from this topic wifi is dead! Now I need original boot to patch it. My firmware is A20. Somebody help!
Click to expand...
Click to collapse
The provided boot image is from A30... Why are u still using A20?
I didn't know about A20 or A30 or anything. You should have mentioined this! Better off dump user's own boot.img and patch it with magisk. Now I have problems. It is good that I've found A20 firmware but it was not easy, I've lost a lot of time to read about firmwares, patching etc.
DimaS_EKB said:
I didn't know about A20 or A30 or anything. You should have mentioined this! Better off dump user's own boot.img and patch it with magisk. Now I have problems. It is good that I've found A20 firmware but it was not easy, I've lost a lot of time to read about firmwares, patching etc.
Click to expand...
Click to collapse
Download stock boot image from here I've saved them https://mega.nz/folder/BvpwibLB#lDDAbRG5SMKS4ucdj1dELg
Also there is nothing to mention at the time of making this guide almost everyone was updated to A.30, but no problem now I've updated the link for all patched boot images
recovered, thanks
now I'm updating to A32
what's next?
download your patched boot image for A32? and that's all?
DimaS_EKB said:
recovered, thanks
now I'm updating to A32
what's next?
download your patched boot image for A32? and that's all?
Click to expand...
Click to collapse
Yes

			
				
pritish1998 said:
Yes
Click to expand...
Click to collapse
Sorry but it appears I cannot update. I tried original and modified boot.img, also I installed original recovery. It doesn't help. The phone downloads the A32 firmware, reboots and cannot start recovery mode to update the firmware.
DimaS_EKB said:
Sorry but it appears I cannot update. I tried original and modified boot.img, also I installed original recovery. It doesn't help. The phone downloads the A32 firmware, reboots and cannot start recovery mode to update the firmware.
Click to expand...
Click to collapse
Flash stock boot, vbmeta and recovery then format data then reboot
If I flash stock vbmeta it cannot boot. Is that ok? Should I erase data anyway?
DimaS_EKB said:
If I flash stock vbmeta it cannot boot. Is that ok? Should I erase data anyway?
Click to expand...
Click to collapse
Yes
pritish1998 said:
Yes
Click to expand...
Click to collapse
Format data
Thanks! Now everything works fine!
pritish1998 said:
Download stock boot image from here I've saved them https://mega.nz/folder/BvpwibLB#lDDAbRG5SMKS4ucdj1dELg
Also there is nothing to mention at the time of making this guide almost everyone was updated to A.30, but no problem now I've updated the link for all patched boot images
Click to expand...
Click to collapse
how to flash stock boot image?
bobongros said:
how to flash stock boot image?
Click to expand...
Click to collapse
python mtk w boot boot.img
pritish1998 said:
python mtk w boot boot.img
Click to expand...
Click to collapse
can i dm you? please help me my phone is bricked
bobongros said:
can i dm you? please help me my phone is bricked
Click to expand...
Click to collapse
How did your phone brick?

[ROM] [Android 13] [blueline/crosshatch] ArrowOS 13.0 | UNOFFICIAL

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS​
Code:
/*
* 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.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
4G
You tell me
Be sure to include a log : check how to
DOWNLOADS[/BG]
Blueline
Crosshatch
Only GAPPS variants
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
GPL compliance:
ROM Source- https://github.com/ArrowOS
Device Source- https://github.com/ArrowOS-Devices/android_device_google_crosshatch
Kernel Source- https://github.com/ArrowOS-Devices/android_kernel_google_bluecross
Vendor Source- https://github.com/ArrowOS-Devices/android_vendor_google_bluecross
ROM OS Version: Android 13
ROM Kernel: Linux 4.9.x
ROM Firmware: built-in
Created 2022-08-22
Last Updated 2022-08-22
How to install?
nameless354 said:
How to install?
Click to expand...
Click to collapse
Download the boot.img and flash it.
Reboot to recovery
Wipe data factory reset.
reboot to bootloader
fastboot update rom.zip
4G doesn't work - it's not good.
If I install this since its Android 13 is it gonna lock me on android 13 like its doing to the Pixel 6's? or will i still be able to go back to Android 12 if i wanted to?
crisis_trustee said:
4G doesn't work - it's not good.
Click to expand...
Click to collapse
That's stated in the first post.. please read the entirety of posts before commenting next time. Thank you
Waiting pixel experience android 13
This is cool. Waiting for the 4G to be working
dhaniynhy said:
Waiting pixel experience android 13
Click to expand...
Click to collapse
i also
Stoner242020 said:
If I install this since its Android 13 is it gonna lock me on android 13 like its doing to the Pixel 6's? or will i still be able to go back to Android 12 if i wanted to?
Click to expand...
Click to collapse
no it won't. It doesn't have the bootloader update that Google put it in Android 13 official update. That means if the device had 13 updated and it was only effecting the 6 and up models from what I understand. Either way. I flashed if and No. It's not locked again. This is a OTA zip and I flashed boot img and OTA in TWRP so. Other than the OS not getting data it works nicely. Hopefully it's something simple
Slim2none4u said:
Download the boot.img and flash it.
Reboot to recovery
Wipe data factory reset.
reboot to bootloader
fastboot update rom.zip
Click to expand...
Click to collapse
when i will flash boot img isn't it be a dirty flashing?
on the third step when i will wipe data and do factory reset isn't it remove the OS?
on last step, there is rom zip which i have to update but after downloading files i have only GAPPS zip
please help me in understanding the whole process.
You flash boot image first, fastboot flash boot (nameofbootimg).img. Once that flashes, go into recovery, I just used volume up and down buttons in fastboot and entered that way. Once in recovery, wipe data and factory reset. It'll ask you if you're sure. Select yes. Once that's finished, you have to flash the zip with name ending with gapps. I had trouble flashing mine in fastboot, kept getting an error about android-info.txt not being in the archive, so I just went back into recovery and chose the option to adb side load the zip (I can't remember what it says exactly). Once that finished, I just chose the reboot option, and it loaded up just fine. It took about 5min or so on the boot animation screen before the Welcome screen appeared, but once loaded everything worked great!
mattprice86 said:
You flash boot image first, fastboot flash boot (nameofbootimg).img. Once that flashes, go into recovery, I just used volume up and down buttons in fastboot and entered that way. Once in recovery, wipe data and factory reset. It'll ask you if you're sure. Select yes. Once that's finished, you have to flash the zip with name ending with gapps. I had trouble flashing mine in fastboot, kept getting an error about android-info.txt not being in the archive, so I just went back into recovery and chose the option to adb side load the zip (I can't remember what it says exactly). Once that finished, I just chose the reboot option, and it loaded up just fine. It took about 5min or so on the boot animation screen before the Welcome screen appeared, but once loaded everything worked great!
Click to expand...
Click to collapse
Except 4G right?
thehassanrasool said:
when i will flash boot img isn't it be a dirty flashing?
on the third step when i will wipe data and do factory reset isn't it remove the OS?
on last step, there is rom zip which i have to update but after downloading files i have only GAPPS zip
please help me in understanding the whole process.
Click to expand...
Click to collapse
I just used TWRP formate data then flash the boot img and sideload the zip
mattprice86 said:
You flash boot image first, fastboot flash boot (nameofbootimg).img. Once that flashes, go into recovery, I just used volume up and down buttons in fastboot and entered that way. Once in recovery, wipe data and factory reset. It'll ask you if you're sure. Select yes. Once that's finished, you have to flash the zip with name ending with gapps. I had trouble flashing mine in fastboot, kept getting an error about android-info.txt not being in the archive, so I just went back into recovery and chose the option to adb side load the zip (I can't remember what it says exactly). Once that finished, I just chose the reboot option, and it loaded up just fine. It took about 5min or so on the boot animation screen before the Welcome screen appeared, but once loaded everything worked great!
Click to expand...
Click to collapse
Thank you so much for your help.
JovialQuestion said:
I just used TWRP formate data then flash the boot img and sideload the zip
Click to expand...
Click to collapse
Thank you so much.
Slim2none4u said:
Download the boot.img and flash it.
Reboot to recovery
Wipe data factory reset.
reboot to bootloader
fastboot update rom.zip
Click to expand...
Click to collapse
install from bootloader or recovery?
viynera said:
install from bootloader or recovery?
Click to expand...
Click to collapse
flash it from custom recovery
thehassanrasool said:
flash it from custom recovery
Click to expand...
Click to collapse
There is no custom recovery for a13 for our models as of yet.
Has 4g being fixed yet?

Categories

Resources