How To Guide Samsung Galaxy Tab A8 2021 (SM-X200) Android 12 / Android 13 Treble flash Guide

How To Guide Samsung Galaxy Tab A8 2021 (SM-X200) Android 12 / Android 13 Treble flash Guide - Samsung Galaxy Tab A8 (2021)

Your warranty will be void after any of these procedures.
* I am not responsible for the outcome for using any of this information, e.g. bricked devices, dead devices, boot loops
* do some research regarding flashing, custom ROM and unlocking bootloaders
* you chose to make these modifications under your own responsibility.
The following guide is for flashing any Treble Project compatible ROM (GSI) on the Samsung Galaxy Tab A8 2021 (SM-X200)What's working on android 12 / 12.1 ROMs :
Everything
What's working on android 13 ROMs :
Everything
There are two ways of flashing GSI, generic system images, for treble compatible devices:
ROM flash from fastboot mode.
Dynamic System Updates (DSU) loading
Prerequisites:
First you should check if your device is treble compatible, this has been already checked by me. Here's the app link for checking it if you make sure yourself
Then you should unlock your bootloader and flash TWRP, here's the link for it
Enable ADB over USB.
Wipe the Data Partition from TWRP
You can root with Magisk if you like.
Option 1 ROM flash from fastboot mode:This is my preferred mode
Instructions:
Turn off the device and Hold Power & Vol Up buttons during restart to enter TWRP recovery
Format data from TWRP and wipe all partitions
Navigate to reboot and select Fastboot mode
Download a GSI image, including LineageOS, Google Android, AOSP, or any other custom GSI Treble compatible ROM for AB partition scheme.
fastboot flash system system.img
also a fastboot -w after flashing for additional wiping wouldn't hurt
IMPORTANT: remember to always only flash *.img files, never flash zip, img.xz, img.tar, gz, or img.tar.zx files, look for the tools for unzipping these file formats and always extract just the system.img file for these procedures. NEVER flash the vbmeta.img this can brick your device
Option 2 Dynamic System Updates (DSU) loading:Instructions:
Enable the DSU feature flagBefore using DSU, ensure the corresponding feature flag is enabled. You can enable the flag using one of the following methods:
On a device with a userdebug Android build: You can enable the feature in Settings > System > Developer options > Feature flags > settings_dynamic_system.
On other devices: Use the following adb command:
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
Launch DSUAfter the feature is enabled, launch DSU using the adb tool.
Download a GSI image, including LineageOS, Google Android, or any other custom GSI Treble compatible ROM for AB partition scheme.
Note: If you build your own GSI from source, or if you download a GSI from another image server, your GSI might not be unsparsed. Use the following command inside your build tree to convert the image to an unsparsed image: simg2img system.img system_raw.img
gzip the GSIand then Push the GSI to the device:
gzip -c system_raw.img > system_raw.gz
adb push system_raw.gz /storage/emulated/0/Download/
Launch DSU using adb.
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b *.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
The KEY_SYSTEM_SIZE should be for the uncompressed image file, otherwise it will fail
IMPORTANT: remember to always only flash *.img files, never flash zip, img.xz, img.tar, gz, or img.tar.zx files, look for the tools to uncompressed these file formats and always extract always the system.img file for these procedures. NEVER flash the vbmeta.img this can brick your device
Boot into the GSI
{
"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"
}
Figure 1. A persistent notification that you can use to control DSU.
After DSU installs the GSI, a DSU menu appears as a persistent notification inside the system notification drawer (see figure 1).
At this point, you can do one of the following:
Boot into the GSI by tapping Restart.
Clean up the GSI by tapping Discard.
Switch back to the device's original system imageAfter you are done testing your app using the GSI, you can perform a cold reboot to boot the system back into its original system image.
When setting the next reboot to use a GSI, you can have the GSI stay installed through multiple boot cycles (until discarded) by enabling sticky mode, or have it used for only one boot cycle by disabling sticky mode.
The following command enables sticky mode:
adb shell gsi_tool enable
The following commands disable sticky mode:
adb shell gsi_tool disable
adb shell gsi_tool enable -s
adb shell gsi_tool disable
Install GSIs using DSU and the DSU LoaderAndroid 11 introduced the DSU Loader, a tool available in the device's developer options that lets you download, install, and manage GSIs entirely through the system's UI.
To install a GSI using the DSU Loader, follow these steps on a device running Android 11 or higher:
Enable developer options on your device.
Open your device's Settings app, then tap Developer options > DSU Loader.
Choose the GSI that you want to install on your device.
Agree to the GSI terms and conditions.
After you agree to the terms and conditions, the GSI that you selected starts downloading. You can check the status of the download through the DSU notification.
After the download has finished, tap Restart to boot the GSI.
When you want to switch back to your device's original system image, tap Restart from the DSU system notification.
[IMG alt="DSU notification with an option that lets you reboot the device using the
original system image"]https://developer.android.com/static/images/topic/dsu/restart-original-system-image.png[/IMG]
Thanks to Magendanz for the TWRP recovery

Does anyone know if selinux and encryption work with this gsi?

only issue is rainbow six mobile and pubg new state detect it as a emulator so how would we fix this?

Twrp keeps saying entering fastboot but never does.
I think it was using older versions of adb and usb drivers

jeffbar2 said:
Twrp keeps saying entering fastboot but never does.
I think it was using older versions of adb and usb drivers
Click to expand...
Click to collapse
When it says that, try checking "fastboot devices" from the PC. I think you'll find you are in fastboot mode.

Does this trip knox like on s22 etc, or does it go back to normal if you restore back to original and relock bootloader?

MarcusGuy1108 said:
Does this trip knox like on s22 etc, or does it go back to normal if you restore back to original and relock bootloader?
Click to expand...
Click to collapse
AFAIK, the knox bit is a physical "fuse" and once it is tripped, it will never restore back. But normally Sansung will still honor the warranty so long as you go back to a stock ROM and relock the bootloader. That will also re-enable OTA updates.

lewmur said:
AFAIK, the knox bit is a physical "fuse" and once it is tripped, it will never restore back. But normally Sansung will still honor the warranty so long as you go back to a stock ROM and relock the bootloader. That will also re-enable OTA updates.
Click to expand...
Click to collapse
I see, just like the phones... damn samsung. Thank you very much for the quick response.

MarcusGuy1108 said:
I see, just like the phones... damn samsung. Thank you very much for the quick response.
Click to expand...
Click to collapse
It isn't just Samsung. Installing a custom ROM or rooting your device will void the warranty with all makers. But at least Samsung will still honor the warranty unless there is some indication that what you did caused the problem. Like bricking the device. But if it is really a hardware problem, they'll still fix it for free during the warranty period.

lewmur said:
It isn't just Samsung. Installing a custom ROM or rooting your device will void the warranty with all makers. But at least Samsung will still honor the warranty unless there is some indication that what you did caused the problem. Like bricking the device. But if it is really a hardware problem, they'll still fix it for free during the warranty period.
I mean the knox warrantee bit
Click to expand...
Click to collapse

I know what you meant. Yes, the warranty bit is blown. But as I said, Samsung will honor it anyway unless they feel something you did caused the problem. Of course, you will still have to reflash to a stock rom, relock the bootloader and factory reset before sending in for repair.

lewmur said:
I know what you meant. Yes, the warranty bit is blown. But as I said, Samsung will honor it anyway unless they feel something you did caused the problem. Of course, you will still have to reflash to a stock rom, relock the bootloader and factory reset before sending in for repair.
Click to expand...
Click to collapse
Maybe I'll try it then. I like a lot about this tablet but god is it sluggish on OneUi. Games and all that work fine (even smooooth) but animations and stuff on OneUI are just.... wow

MarcusGuy1108 said:
Maybe I'll try it then. I like a lot about this tablet but god is it sluggish on OneUi. Games and all that work fine (even smooooth) but animations and stuff on OneUI are just.... wow
Click to expand...
Click to collapse
There is a fix for that. It has to do with using ADB to change the options for how to size the ramdisk to zero. You might try googling "Samsong One Ui laggy". Lineage doesn't have One Ui so it doesn't have the problem.

MarcusGuy1108 said:
Maybe I'll try it then. I like a lot about this tablet but god is it sluggish on OneUi. Games and all that work fine (even smooooth) but animations and stuff on OneUI are just.... wow
Click to expand...
Click to collapse
This will fix your issue - https://www.androidpolice.com/samsung-ram-plus-phone-how-to-disable/

kevinco1 said:
This will fix your issue - https://www.androidpolice.com/samsung-ram-plus-phone-how-to-disable/
Tried that - made a bit of difference but just gonna return the tablet.
Click to expand...
Click to collapse

if you still own it: maybe you're in the mood to take a look here:https://forum.xda-developers.com/t/samsung-galaxy-one-ui-optimization-guide.4376755/

The SM-X200 is a budget device so if you've had a higher end Sam tab then yeah this will seem very slow

Hey all. I just recently bought a Tab A8 32GB and was looking for a way to load a ROM on it so I can use the SD Card as internal storage.
I found this guide, but I'm not seeing some of the steps it says to take on my device. I've enabled Developer Options, but I don't see the DSU/GSI stuff. Nor the 'feature flag' to turn that on.
I know back in the old days all you have to do way flash a recovery image and then you could load the ROM from recovery. Is that still the basic process? Can I flash TWRP and then flash the ROM, or is more detailed now than that?

ke4peo said:
Hey all. I just recently bought a Tab A8 32GB and was looking for a way to load a ROM on it so I can use the SD Card as internal storage.
I found this guide, but I'm not seeing some of the steps it says to take on my device. I've enabled Developer Options, but I don't see the DSU/GSI stuff. Nor the 'feature flag' to turn that on.
I know back in the old days all you have to do way flash a recovery image and then you could load the ROM from recovery. Is that still the basic process? Can I flash TWRP and then flash the ROM, or is more detailed now than that?
Click to expand...
Click to collapse
The full process for flashing is in the first post, in case you don't have the DSU option

Related

Can i Root Galaxy Note 8 with latest security Updates

Samsung releases security updates every month, and i think they are the culprit, since i just cant flash TWRP with Odin on My Galaxy Note 8. It says failed. Ive tried 3.3.1and even latest 3.5.0 and both fail.
Its the Exynos CPU which can be rooted. At least i know this for sure
Do you know of any solutions to this
{
"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"
}

therock003 said:
Samsung releases security updates every month, and i think they are the culprit, since i just cant flash TWRP with Odin on My Galaxy Note 8. It says failed. Ive tried 3.3.1and even latest 3.5.0 and both fail.
Its the Exynos CPU which can be rooted. At least i know this for sure
Do you know of any solutions to this
Click to expand...
Click to collapse
I recently flashed the latest filmware and managed to flash TWRP 3.5 after so it's not Samsung blocking it. What Odin version are you using? I'm using 3.13.3. I had to install 15 second Adb for it to work though which can be found in the link below. You enabled the OEM toggle?
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com

Whats the OEM toggle.
Are you sure that adb install is legit cause it looks like a 2013 post. Anyway i even tried the latest 3.14.1 odin and also that adb package you posted. It still fails

therock003 said:
Whats the OEM toggle.
Are you sure that adb install is legit cause it looks like a 2013 post. Anyway i even tried the latest 3.14.1 odin and also that adb package you posted. It still fails
Click to expand...
Click to collapse
You have to enable the OEM toggle in the development settings (settings/about phone/software information/the click on the build number 7 times will enable dev setting) for TWRP to be able to flash. This is probably why it's not flashing for you. If you don't know about the OEM toggle, do you know that as soon as you flash TWRP that it trips Knox and Samsung Pay will never work again unless you get a motherboard replacement?
Yes the 15 second adb is legit. Used it for a long time.

If you mean the auto update on deleveper iptions i turned it off after you said so. But still same thing. Apparently theres this frp lock happening

therock003 said:
If you mean the auto update on deleveper iptions i turned it off after you said so. But still same thing. Apparently theres this frp lock happening
Click to expand...
Click to collapse
I did not mention auto update...
therock003 said:
If you mean the auto update on deleveper iptions i turned it off after you said so. But still same thing. Apparently theres this frp lock happening
Click to expand...
Click to collapse
I have not said anything about auto update. In the dev setting you should see "OEM unlocking" toggle, like in the screenshot I added. If you don't see this option let me know and I will see if I can find the thread that might help you get the toggle.
FRP lock is Factory Reset Protection. So if your phone is lost or stolen that person can't just flash stock firmware to use your phone it makes it so they have to login to your account to be able to use the phone, although this only works on the stock rom without root as it needs encryption.

No you were right. didnt notice the oem unlocking toggle. Read another page that told me to turn off auto updates and this was misleading
Does Odin Unlock Bootloader? - codekomusic.com
What happens if I unlock bootloader? A device with a locked bootloader will only boot the operating system currently on it. You can’t install a custom operating system – the bootloader will refuse to load it. If your device’s bootloader is unlocked, you will see an unlocked padlock icon on the...
codekomusic.com
How do I turn off OEM lock?
Open developer options (in the Settings app itself), and find the option called ‘Auto update system’. Use the toggle button to disable it.
Click to expand...
Click to collapse
Anyway i got TWRP running now, and im off to install magisk and the rest of the steps. Thanx man for helping me

therock003 said:
No you were right. didnt notice the oem unlocking toggle. Read another page that told me to turn off auto updates and this was misleading
Does Odin Unlock Bootloader? - codekomusic.com
What happens if I unlock bootloader? A device with a locked bootloader will only boot the operating system currently on it. You can’t install a custom operating system – the bootloader will refuse to load it. If your device’s bootloader is unlocked, you will see an unlocked padlock icon on the...
codekomusic.com
Anyway i got TWRP running now, and im off to install magisk and the rest of the steps. Thanx man for helping me
Click to expand...
Click to collapse
Glad to hear! Happy flashing.

Oh man now I get a verirication failed. Followed this guide and flashed magisk , no verity opt and rmm state. After that it says reboot your mobile
Root Samsung Galaxy Note 8 SM-N950F Pie 9.0 using TWRP and Install Magisk
After Samsung released One UI Pie 9.0 version, most of the users who blame Samsung's Custom skin OS, Praising Samsung. It may not be best like OnePlus
www.androidinfotech.com
And it has a footnote. "Oh we didnt actually mean that. We meant reboot into recovery otherwise youll have to reflash your firmware."
I mean cmon how stupid csn these guides get. So what now hoe do i reflash the stock firmware

Seriously i need some help cause thst guide inposted previously is the worst. I refladhed stock firmware and redid the procedure. Based on thst guide you must first flash twrp. After you boot into TWRP you install magisc no verity and smm and reboot. I do all that and end up eith no firmware. Whats going wrong here

therock003 said:
Seriously i need some help cause thst guide inposted previously is the worst. I refladhed stock firmware and redid the procedure. Based on thst guide you must first flash twrp. After you boot into TWRP you install magisc no verity and smm and reboot. I do all that and end up eith no firmware. Whats going wrong here
Click to expand...
Click to collapse
You must have wiped "system" in TWRP for that to happen. You only need to format data where you have to type "yes" to confirm, then you can flash Magisk.
Make sure to backup your EFS folder with TWRP too! So important to do this

Wait doni need to format or something, cause i was under the impression that i get to keep.my files. I havent wiped anyrhing besides cache. I only do advanced wipe and select cache each time i installed anyrging. I never did a full wipe. Do i need to?
So here is what i do in detail step by step.
I flash TWRP on AP on odin and then boot in TWRP. I select full permission and not read only and go to instal.
I install magisc 20.3.zip then go advances wipe and wipe cache.
Then repeat with the rest. Install thst opt verity then clear chache. Instal smm state then clear cach and finally i reboot.
What did i not do here

therock003 said:
Wait doni need to format or something, cause i was under the impression that i get to keep.my files. I havent wiped anyrhing besides cache. I only do advanced wipe and select cache each time i installed anyrging. I never did a full wipe. Do i need to?
So here is what i do in detail step by step.
I flash TWRP on AP on odin and then boot in TWRP. I select full permission and not read only and go to instal.
I install magisc 20.3.zip then go advances wipe and wipe cache.
Then repeat with the rest. Install thst opt verity then clear chache. Instal smm state then clear cach and finally i reboot.
What did i not do here
Click to expand...
Click to collapse
I'm not sure as I have never flashed the RMM and Verity, I just flash a custom Rom which has all that patched already.
I thought we had to format data to be able to flash anything in TWRP, I didn't think keeping all data was possible.

Then i guess ill have to spend all day to backup all apps and files and try to fully erase memory

[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

[ROM][SOFIAR][11][UNOFFICIAL][GAPPS][VANILLA] ArrowOS

{
"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
ArrowOS is an AOSP/CAF based project 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
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : via the Matlog app included or check how to
DOWNLOADS
Here!
INSTALLATION - TWRP
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
Flash the ArrowOS zip
REBOOT TO RECOVERY!!
Reboot to system
Profit
INSTALLATION - FASTBOOTD
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and extract it to your adb/fastboot folder
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
In TWRP reboot menu, select fastboot, wait for it to reboot
Open a cmd window where you extracted the files to earlier and flash the ROM with the below commands
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
Reboot to system
Profit
*** Dont install Magisk until you have booted the ROM once
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Odin1101/Project-Sofia/tree/Upstream-plus
Device Source: https://github.com/whatthef84/android_device_motorola_sofiar-1
Vendor Source: https://github.com/whatthef84/android_vendor_motorola_sofiar-1/tree/android-11
Many thanks to @vache for the above device/vendor trees, the flash tool, and building TWRP. The guy's a legend!

View attachment 5273685View attachment 5273649View attachment 5273651View attachment 5273653View attachment 5273655
View attachment 5273657View attachment 5273659View attachment 5273661View attachment 5273669View attachment 5273671View attachment 5273673View attachment 5273675View attachment 5273677View attachment 5273679

Agh, plain AOSP. I miss Havoc already.

Testing it out and everything thing seems smooth. I did find one minor issue for the people that like their temperatures in imperial units. You can change the lockscreen temp to imperial and it displays an F for farenheit but the temperature value is still Cecius.

Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?

jonshmorg said:
Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?
Click to expand...
Click to collapse
You will need to go back to rooted stock, and copy your apn_conf.xml file from product/etc to your sd card, amd replace it on arrow (or another rom)

Quantumstate said:
Agh, plain AOSP. I miss Havoc already.
Click to expand...
Click to collapse
Closest thing to havoc is crDroid ATM mate, it's on the forums here

This ROM is marked as only being compatible with sofiar, but I can confirm that everything seems to work on my sofia device.

Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Edit: It turns out I was using the wrong build of TWRP. Use the one linked in the original post, not the one elsewhere on the forums.

RaspberryPiBen said:
Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Click to expand...
Click to collapse
While in twrp, if you select reboot to fastboot, that is fastboot d

Beetle84 said:
While in twrp, if you select reboot to fastboot, that is fastboot d
Click to expand...
Click to collapse
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.

RaspberryPiBen said:
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.
Click to expand...
Click to collapse
Using the twrp linked here or another?

Beetle84 said:
Using the twrp linked here or another?
Click to expand...
Click to collapse
I just noticed that. I was using the TWRP build from https://forum.xda-developers.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/ because I assumed that was what the link was for. Thank you.

Apps aren't able to see registered fingerprints. Fingerprint auth is grayed out and the apps complain "register fingerprints on the device settings".
I have tried:
Deleting and redoing fingerprints (just one and multiple) with and without rebooting.
Confirmed the fingerprints work for screen unlock and gestures.
Re-installed 08-04-21 Vanilla build with full format, issue persists.
Anything I missed to check? I do not have my phone rooted, so cannot see system logs using the logging app.
Using sofiar (moto g8 power). Tested the apps themselves on my second phone klte (Samsung S5 Lineageos 16) and fingerprints work just fine there.

Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?

jdude520 said:
Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?
Click to expand...
Click to collapse
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.

ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?

Carl-Robert said:
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.
Click to expand...
Click to collapse
I'm not the person with the problem, but thank you for the explanation. I installed my ROMs before Android 11 came out for this phone and I was planning to test the stock Android 11 ROM, so this information will be very useful.

jdude520 said:
ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?
Click to expand...
Click to collapse
I believe you have to roll back to Android 10. Custom Android 11 ROMs may work, but you can't install custom ROMs so that doesn't help.

actually it is rescuing me to android 11 no matter what i do

[ROM][11][AOSP] DotOS for OnePlus Nord N10 5G [UNOFFICIAL][BILLIE]

{
"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"
}
" #DroidOnTime "
ROM Version: 5.2.1
Device: OnePlus Nord N10 5G [billie]
Maintainer: @kronflux
Build Status: UNOFFICIAL
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
dotOS is an Android ROM that focuses on performance, stability, and User Experience. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get the most out of your device.....
1. Download the ROM and Recovery image
2. Boot into bootloader/fastboot mode
* adb reboot bootloader
3. Flash the Recovery image
* fastboot flash recovery recovery.img
4. Boot into Recovery
* fastboot reboot-recovery
5. Perform a Factory Reset/Wipe in Recovery
6. Go to Apply Update and choose Apply from ADB
7. Sideload the ROM
* adb sideload rom.zip
Reboot and voila!
ROM [VANILLA]: https://www.androidfilehost.com/?fid=2981970449027577449
MD5: F852EB929ED7DA566EBC0F291678CB6A
SHA-1: 3CD283C4AA9AF0B4290261BD3F19D5DED0DD947F
ROM [WITH GAPPS]: https://www.androidfilehost.com/?fid=2981970449027577450
MD5: 14F7938C0982CC0749FC160F412453B6
SHA-1: BFD74BC13CBF2AA69ABA9ACB45D44E5B70BBFAC8
*NOTE: dotOS Recovery not currently working properly, included PixelExperience recovery in the meantime, which will work fine*
RECOVERY: https://www.androidfilehost.com/?fid=2981970449027577417
MD5: BFE3114F2A966E03CFD0CF6C0040146B
SHA-1: B14B3102C97C15E3C7C045182489514C0827713F
In case you need it for magisk or any other reason, here's the boot image as well:
BOOT IMAGE: https://www.androidfilehost.com/?fid=2981970449027577448
MD5: EAD909E81843EAB13E1DA1FA95B0FEBB
SHA-1: 81CC6D595C1802E9E839408CB717BCB62C40289B
Complete Changelogs: https://changelogs.droidontime.com/
AOSP
Lineage OS
Pixel Experience
Dirty Unicorns
Mohan CM - Founder/Core Developer
Iacob Ionut - UI, UX Developer/ Core Developer
Important Links
dot OS source
Telegram Channel
Website
REPORTING BUGS !
As soon as the problem occurs, take a LOGCAT!
for more READ THIS
Contributors: @iamsaalim, @kronflux
Source Code: https://github.com/DotOS
Device Sources: - https://github.com/kronflux/device_oneplus_billie
Kernel Sources: - https://github.com/danascape/kernel_oneplus_sm6350
ROM OS Version: 11.x Android R
Version Information
Status: STABLE
Current Stable Version: v5.2.1
Stable Release Date: 27-01-2022
Last Updated: 21-03-2022
ROM Firmware Required: OxygenOS 11.x
ROM Kernel: 4.19.125

Nice work!

Can this be flashed with twrp?

Thrilled to see this! Any known issues like DTW and/or Adaptive Brightness not working? Or no known issues at this point?

First of all thank you for this amazing ROM! I noticed that Bluetooth audio works fine but when you plug in headsets/headphones they still produce sounds from the speakers and not the headphones/headsets. WiFi is also a tad bit weak so I transitioned to ArrowOS. Thank you again for the good work. I appreciate it!

heyho i have a few questions about this rom. Is it possible to install a own gapps packet like the pico variant? If yes which one should i use? Arm64/Android 11/Pico is this the right package?
Whats about root can i flash magisk for rooting?

Andariyel said:
heyho i have a few questions about this rom. Is it possible to install a own gapps packet like the pico variant? If yes which one should i use? Arm64/Android 11/Pico is this the right package?
Whats about root can i flash magisk for rooting?
Click to expand...
Click to collapse
I am not sure about the gapps, but as for the rooting Magisk works for me just fine.

I'm new to all this, so I hope I do this right, but I bought this phone specifically to be a 5G hotspot, and OnePlus disabled 5G after Android 11 update.
I'm on build number 11.0.3.BE89BA, so EU model, and before I take the plunge into installing custom ROM for the first time since I owned an LG G3 like 7 years ago, I'd like to at least confirm this will work on my build and it will re-enable 5G.
Thank you for answering, and if you have any extra tips or info how to make it as easy as possible, I'd be grateful.
EDIT: I've followed the instructions to the best of my understanding, and it gets stuck at 47%, which I've heard is normal, but I always reboot into stock firmware. I tried it at least 5 times so far, even following Youtube videos (different OnePlus phones on YT though), but the result is always the same. Instructions say nothing about TWRP, but can I maybe try that way?

@wanamy thx for your reply good to read. For gapps i google it and from what i read on other phones with dotos it works flashing after the Dotos. So i guess it should be okay. Will try it at the weekend when i have time.

Sophos437 said:
I'm new to all this, so I hope I do this right, but I bought this phone specifically to be a 5G hotspot, and OnePlus disabled 5G after Android 11 update.
I'm on build number 11.0.3.BE89BA, so EU model, and before I take the plunge into installing custom ROM for the first time since I owned an LG G3 like 7 years ago, I'd like to at least confirm this will work on my build and it will re-enable 5G.
Thank you for answering, and if you have any extra tips or info how to make it as easy as possible, I'd be grateful.
EDIT: I've followed the instructions to the best of my understanding, and it gets stuck at 47%, which I've heard is normal, but I always reboot into stock firmware. I tried it at least 5 times so far, even following Youtube videos (different OnePlus phones on YT though), but the result is always the same. Instructions say nothing about TWRP, but can I maybe try that way?
Click to expand...
Click to collapse
I MsM back to stock rom which for me was version 10 at which point I needed to update os to 11 twice to make sure that 11 was on both partitions. After that I unlocked, flashed recovery, reboot recovery, format data, adb sideload rom, then adb sideload partition fix, then reboot to bootloader, fastboot--set-active=a( or b depending on what partition you were on. you want to be on the other partition), boot back into recovery, adb sideload rom again for the different partition, format data again, then reboot. works fine for me. here is the link for the copy partition zip https://www.androidfilehost.com/?fid=2188818919693768129

boffster99 said:
I MsM back to stock rom which for me was version 10 at which point I needed to update os to 11 twice to make sure that 11 was on both partitions. After that I unlocked, flashed recovery, reboot recovery, format data, adb sideload rom, then adb sideload partition fix, then reboot to bootloader, fastboot--set-active=a( or b depending on what partition you were on. you want to be on the other partition), boot back into recovery, adb sideload rom again for the different partition, format data again, then reboot. works fine for me. here is the link for the copy partition zip https://www.androidfilehost.com/?fid=2188818919693768129
Click to expand...
Click to collapse
Hey man, thank you for the help, but I'm really bad at understanding this, so please have some patience with me asking a few questions. I've only started looking into this a couple of hours ago, and I'm not the most tech savy when it comes to phones.
I don't know what MsM is, but I'll look around the forum and try to find more info. Question is, do I really need to flash back to 10 just to install 11 again, since I'm already on an official 11? Honestly, I'm not really sure my phone ever was on 10, I just know when I got the phone I updated to the new firmware straight out of the box, then discovered about 5G being turned off in 11 afterwards.
I've read about partitions in comments for Pixel Experience Custom ROM, and I've tried to do that, but Powershell insisted there's only partition A, and no matter what I would do it wouldn't switch. Is that the zip file for? How do I use it?

Sophos437 said:
Hey man, thank you for the help, but I'm really bad at understanding this, so please have some patience with me asking a few questions. I've only started looking into this a couple of hours ago, and I'm not the most tech savy when it comes to phones.
I don't know what MsM is, but I'll look around the forum and try to find more info. Question is, do I really need to flash back to 10 just to install 11 again, since I'm already on an official 11? Honestly, I'm not really sure my phone ever was on 10, I just know when I got the phone I updated to the new firmware straight out of the box, then discovered about 5G being turned off in 11 afterwards.
I've read about partitions in comments for Pixel Experience Custom ROM, and I've tried to do that, but Powershell insisted there's only partition A, and no matter what I would do it wouldn't switch. Is that the zip file for? How do I use it?
Click to expand...
Click to collapse
Did you go into fastboot or fastbootd?
Fastboot allows you to switch slots, fastbootd does not.
fastboot --set-active=a and the commands pertaining to dynamic partitions also requires a newer version of adb and fastboot. Old version will just give you an "unknown command" response.

Sophos437 said:
Hey man, thank you for the help, but I'm really bad at understanding this, so please have some patience with me asking a few questions. I've only started looking into this a couple of hours ago, and I'm not the most tech savy when it comes to phones.
I don't know what MsM is, but I'll look around the forum and try to find more info. Question is, do I really need to flash back to 10 just to install 11 again, since I'm already on an official 11? Honestly, I'm not really sure my phone ever was on 10, I just know when I got the phone I updated to the new firmware straight out of the box, then discovered about 5G being turned off in 11 afterwards.
I've read about partitions in comments for Pixel Experience Custom ROM, and I've tried to do that, but Powershell insisted there's only partition A, and no matter what I would do it wouldn't switch. Is that the zip file for? How do I use it?
Click to expand...
Click to collapse
If your on stock 11 then no shouldn't need to MsM. I've tried the rom for a few days. At first it was pretty good. noticed some wifi glitching and although it would allow me to establish a hot spot, it did not allow internet access doing it. So I never was able to get the hos spot working.

ninjasinabag said:
Did you go into fastboot or fastbootd?
Fastboot allows you to switch slots, fastbootd does not.
fastboot --set-active=a and the commands pertaining to dynamic partitions also requires a newer version of adb and fastboot. Old version will just give you an "unknown command" response.
Click to expand...
Click to collapse
I followed the instructions a few times and I'm sure I typed fastboot not fastbootd, unless that has nothing to do with entering fastbootd. As for the versions, I've downloaded the Platform tools r32 from the adb tutorial on this website, which I guess is the newest version. I also tried the 15 second adb tool I found on some youtube tutorial, but CMD just immediately crashes when I tried to run it, so I had to do everything in Poweshell. When I tried to switch partition powershell would say something in the lines of "looking for any device", then pretty much freeze and get unstuck 30 seconds later with nothing happening.

boffster99 said:
If your on stock 11 then no shouldn't need to MsM. I've tried the rom for a few days. At first it was pretty good. noticed some wifi glitching and although it would allow me to establish a hot spot, it did not allow internet access doing it. So I never was able to get the hos spot working.
Click to expand...
Click to collapse
Oof, that's a deal breaker for me, hotspot is a must for me. I'll try another ROM and hopefully I have more luck with it. The thing is, I don't know if it's stock 11 or not, I've never checked, my phone just pretty much downloaded a software update on the first run and I clicked install without thinking too much about it.

Cant sideload the ROM. I get the following error
C:\Users\Harrison\OneDrive\Desktop\Metro pcs\platform-tools_r32.0.0-windows\platform-tools>adb sideload C:\Users\Harrison\Downloads\dotOS-R-v5.2.1-billie-GAPPS-20220124-0523.zip
serving: 'C:\Users\Harrison\Downloads\dotOS-R-v5.2.1-billie-GAPPS-20220124-0523.zip' (~0%) adb: failed to read command: No error
C:\Users\Harrison\OneDrive\Desktop\Metro pcs\platform-tools_r32.0.0-windows\platform-tools>adb sideload C:\Users\Harrison\Downloads\dotOS-R-v5.2.1-billie-GAPPS-20220124-0523.zip
Total xfer: 0.00x

umaga2012 said:
Cant sideload the ROM. I get the following error
C:\Users\Harrison\OneDrive\Desktop\Metro pcs\platform-tools_r32.0.0-windows\platform-tools>adb sideload C:\Users\Harrison\Downloads\dotOS-R-v5.2.1-billie-GAPPS-20220124-0523.zip
serving: 'C:\Users\Harrison\Downloads\dotOS-R-v5.2.1-billie-GAPPS-20220124-0523.zip' (~0%) adb: failed to read command: No error
C:\Users\Harrison\OneDrive\Desktop\Metro pcs\platform-tools_r32.0.0-windows\platform-tools>adb sideload C:\Users\Harrison\Downloads\dotOS-R-v5.2.1-billie-GAPPS-20220124-0523.zip
Total xfer: 0.00x
Click to expand...
Click to collapse
usually get that error if your coming from the wrong Os or from a custom rom. Are you running stock OOS 11 on your phone?

Sophos437 said:
I followed the instructions a few times and I'm sure I typed fastboot not fastbootd, unless that has nothing to do with entering fastbootd. As for the versions, I've downloaded the Platform tools r32 from the adb tutorial on this website, which I guess is the newest version. I also tried the 15 second adb tool I found on some youtube tutorial, but CMD just immediately crashes when I tried to run it, so I had to do everything in Poweshell. When I tried to switch partition powershell would say something in the lines of "looking for any device", then pretty much freeze and get unstuck 30 seconds later with nothing happening.
Click to expand...
Click to collapse
Are you typing in adb reboot bootloader or adb reboot fastboot?
Bootloader leads to official fastboot.
Fastboot leads to fastbootd which doesn't do the fastboot things oddly enough.

boffster99 said:
usually get that error if your coming from the wrong Os or from a custom rom. Are you running stock OOS 11 on your phone?
Click to expand...
Click to collapse
I'm coming from OOS11. My device is the Metro version. Apparently these new ROMS only work on the global devices

ninjasinabag said:
Are you typing in adb reboot bootloader or adb reboot fastboot?
Bootloader leads to official fastboot.
Fastboot leads to fastbootd which doesn't do the fastboot things oddly enough.
Click to expand...
Click to collapse
I'm typing ./adb reboot bootloader. Like I've said, my knowledge is limited, so I've followed the tutorial word for word. Anyway, I'll have a few days off next week, so I'll try to do all sorts of things, starting with downgrading to OOS10 with MSM. That by itself should fix my 5g problem, and if it doesn't then I'll do more Custom ROM shenanigans.

[RECOVERY][UNOFFICIAL][3.5.2] TWRP for Galaxy M21 [CWB1 and Above]

{
"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"
}
Disclaimer:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
I am not the developer.
Developer: @naz664
Changelog:
Spoiler: View
Changelog :-
- Souls recovery with latest A12 support (Jan 2023)
- Updated kernel
- This recovery won't work on older stock version
So don't flash this unless you are running latest jan 2023 stock rom
How to install?
Spoiler: ODIN (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + Bixby key + USB cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this, Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
TWRP Source: GitHub
Credits:
Soul reaper
Nazim
Lmao
Max B
Darshana & Encrypted for testing
Important:
This version only works on the latest update of stock rom (M215FXXU3CWB1) and above. If you are running an older version, use the previous build of TWRP.
Download: Link

И что делать ?

w1nk1 said:
И что делать ?
Click to expand...
Click to collapse
Different device?

Hi Fredin friend,
I Recently upgraded SM-M215G device to OneUi5.1 (M215GDDS3CWD1-20230522142126) Binary 3 and TWRP (twrp-3-5-2-m21-v3-1-a12-tar)but anything I am flashing is either bootlooping or stuck on Rom Logo, I flashed (Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip) still only Rom Logo showing, how to boot the GSIs? Any help appreciated.

OldNoobOne said:
Hi Fredin friend,
I Recently upgraded SM-M215G device to OneUi5.1 (M215GDDS3CWD1-20230522142126) Binary 3 and TWRP (twrp-3-5-2-m21-v3-1-a12-tar)but anything I am flashing is either bootlooping or stuck on Rom Logo, I flashed (Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip) still only Rom Logo showing, how to boot the GSIs? Any help appreciated.
Click to expand...
Click to collapse
Hi
If you had unencrypted data (if you could see files in internal storage) and flashed the latest stock rom, but you didn't flash encryption/multi disabler before the first boot into OneUI, it will probably cause problems.
So try formatting data and flash encryption/multi disabler (although I believe dm verity disabler also disables encryption by default, but it won't hurt flashing them). Or you can format data and not flash anything to let data stay encrypted, but then you won't be able to use the internal storage in TWRP.

Fredin_ said:
Hi
If you had unencrypted data (if you could see files in internal storage) and flashed the latest stock rom, but you didn't flash encryption/multi disabler before the first boot into OneUI, it will probably cause problems.
So try formatting data and flash encryption/multi disabler (although I believe dm verity disabler also disables encryption by default, but it won't hurt flashing them). Or you can format data and not flash anything to let data stay encrypted, but then you won't be able to use the internal storage in TWRP.
Click to expand...
Click to collapse
Hi friend Fredin,
Thanks for the reply.
I used (twrp-3-5-2-m21-v3-1-a12-tar) and it is smooth (just like previous Soulr-A11 twrp) but sideload did not work while the other recovery (TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) by Dev Ravindu Deshan works great too but Reboot to Recovery does not work properly all the time, so sometimes instead of Reboot to Recovery the changes happen when manually reboot to recovery using usb cable also sometimes it does not recognise pen drive. Till now I only managed to boot Tuki1.2 and the other Lineage 20 zip had Oplist error 1 issue. Hoping for GSI boot too later. Thanks for recovery

OldNoobOne said:
Hi friend Fredin,
Thanks for the reply.
I used (twrp-3-5-2-m21-v3-1-a12-tar) and it is smooth (just like previous Soulr-A11 twrp) but sideload did not work while the other recovery (TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) by Dev Ravindu Deshan works great too but Reboot to Recovery does not work properly all the time, so sometimes instead of Reboot to Recovery the changes happen when manually reboot to recovery using usb cable also sometimes it does not recognise pen drive. Till now I only managed to boot Tuki1.2 and the other Lineage 20 zip had Oplist error 1 issue. Hoping for GSI boot too later. Thanks for recovery
Click to expand...
Click to collapse
I'm not the dev btw, @naz664 is

Fredin_ said:
I'm not the dev btw, @naz664 is
Click to expand...
Click to collapse
Hi Friend,
Naz Roms great also
sidetalk: Do you know how to unlock CWD1 Stock Rom bootloader? my bootloader isnt unlocked fully? And in Shaomi phones which model would you recommend, it has fastboot so.

OldNoobOne said:
Hi Friend,
Naz Roms great also
sidetalk: Do you know how to unlock CWD1 Stock Rom bootloader? my bootloader isnt unlocked fully? And in Shaomi phones which model would you recommend, it has fastboot so.
Click to expand...
Click to collapse
What do you mean by it's not fully unlocked? iirc the toggle stays like that once the bootloader is unlocked.

Fredin_ said:
What do you mean by it's not fully unlocked? iirc the toggle stays like that once the bootloader is unlocked.
Click to expand...
Click to collapse
Hi Friend,
When I had unlocked the bootloader of the same device while it had A11 loaded in it, the oem unlock button was TOTALLY GREYED OUT (I swear I'm not lying), I mean even the toggle button was greyed out but in above picture you can see toggle buttons are Blue color and oem-unlock toggle button is light-blue but not fully greyed out, I didnt relock my bootloader before flashing A13 Stock CWD1 update
Now I cant flash GSI they refuse to boot always stuck on bootlogo.

OldNoobOne said:
Hi Friend,
When I had unlocked the bootloader of the same device while it had A11 loaded in it, the oem unlock button was TOTALLY GREYED OUT (I swear I'm not lying), I mean even the toggle button was greyed out but in above picture you can see toggle buttons are Blue color and oem-unlock toggle button is light-blue but not fully greyed out, I didnt relock my bootloader before flashing A13 Stock CWD1 update
Now I cant flash GSI they refuse to boot always stuck on bootlogo.
Click to expand...
Click to collapse
Don't think there is any in between state. If you can flash stuff, your bootloader is unlocked. If the GSI is not booting, that's some other issue. Try the new AOSP ROMs instead.
A51 Builds by Royna - Browse Files at SourceForge.net
sourceforge.net

Fredin_ said:
Don't think there is any in between state. If you can flash stuff, your bootloader is unlocked. If the GSI is not booting, that's some other issue. Try the new AOSP ROMs instead.
A51 Builds by Royna - Browse Files at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
Thanks Friend,
It looks like Royna's ROM zips (Lineage 20 & evolution_m21-ota-tq2b.230505.005.a1-06050648-community-unsigned.zip & crDroidAndroid-13.0-20230427-m21-v9.4.zip) not flashing, reason - TWRP error : 1 Assert failed : update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list") and repartition issue even while sideloading. The only one that boots is TukiRom1.2, I havent tried Tuki1.3 yet. I tried Roynas' TWRP files too but after boot to recovery they get stuck, the other TWRP files (TWRP-3.5.2-m21-v3.1-A12.tar & TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) boot and work with some issues though.

Database Develop

welcome