Database Develop

[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

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?

How To Guide Guide to Flash Miui_VILIGlobal_V13.0.1.0.SKDMIXM_e7e8f0ef90_12 and use Magisk

Hello All,
Quick and dirty guide.
Warning!
I'm not responsible for any damage to you, to your device or to your data. Do this at your OWN RISK! If you don't know what you are doing, STOP now!
Steps to flash the ROM using TWRP:
Be on Android 11 (MIUI 12.5) and flash TWRP. There is a guide here on how to do it, so i'm not posting that.
Obviously, you'll need unlocked bootloader so if it's not unlocked, your case is lost
Download the ROM in the title from here and copy it to your phone
Reboot to TWRP
If you want, i guess you can wipe data - i haven't done this
Flash the ROM like you would any other (install and select the zip you copied over from the above link)
At the end, it'll give you mounting error but it's all good, reboot
Wait for the ROM to settle if you wish - you can stop here
For Magisk, follow the below steps
Enable developer settings and USB debugging
Install the Magisk Manager app (latest version 24.1 at the time of writing this little guide)
Turn off the phone and boot it into fastboot mode
Start the fastboot app of your choice from your pc and connect your phone via USB (I'm using Minimal ADB and Fastboot, you can find it on XDA)
issue the following commands in the same order:
Code:
fastboot devices
if you don't get as a response a few digits of your device ID with the fastboot text next to it, you'll doing something wrong (driver might be or you are not in fastboot mode)
Code:
fastboot flash boot_a patched_boot.img
if the command completes you'll get a finished message
Code:
fastboot flash boot_b patched_boot.img
patched_boot.img is the full path of the patched boot.img file
Code:
fastboot reboot
wait for the device to boot.
Patched boot.img is attached but if you wish, you can extract it from the rom yourself using payload dumper and patch it on your phone with Magisk. The attached boot.img is patched with Magisk 24.1, this is what you'll need as well - this is the current version. You need to unzip the attached file of course!
Enjoy.

{
"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"
}

Just flashed by TWRP and reset to the factory. So far there is no fastboot image, only recovery one, and normal way it is not possible to flash it as it is only for Mi Pilot people.

Pichulec said:
Just flashed by TWRP and reset to the factory. So far there is no fastboot image, only recovery one, and normal way it is not possible to flash it as it is only for Mi Pilot people.
Click to expand...
Click to collapse
what do you mean with "no fastboot image"?

There are two types of images - recovery and fastboot.

Hello, im trying your guide but my phone stuck on fastboot mode and when im try to enter twrp, it stuck on frozen screen i cant swipe to unlock twrp....any idea?(

Yuditkiichi said:
Hello, im trying your guide but my phone stuck on fastboot mode and when im try to enter twrp, it stuck on frozen screen i cant swipe to unlock twrp....any idea?(
Click to expand...
Click to collapse
Hi, if TWRP worked before, it should as well now.

donjamal said:
Hi, if TWRP worked before, it should as well now.
Click to expand...
Click to collapse
Any idea how to solved my twrp problem? Or should i reflash it with pc?

Yuditkiichi said:
Any idea how to solved my twrp problem? Or should i reflash it with pc?
Click to expand...
Click to collapse
I would probably relfash twrp as long as I'm still on 12.5.

Yesterday received OTA update for my 11t pro. I'm not in Pilot Programm..

Yuditkiichi said:
Any idea how to solved my twrp problem? Or should i reflash it with pc?
Click to expand...
Click to collapse
for now twrp not working for a12.
wait for update

All can download rom here https://xiaomifirmwareupdater.com/miui/vili/stable beta/V13.0.1.0.SKDMIXM/
and use updater to update it.. that dont need any mi pilot.. i just installing it.. yeeah!

[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?

[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.