Database Develop

What rom should i use? for xt1063

I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.

abispac said:
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
Click to expand...
Click to collapse
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case

reefuge said:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
Click to expand...
Click to collapse
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.

abispac said:
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
Click to expand...
Click to collapse
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?

reefuge said:
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
Click to expand...
Click to collapse
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.

abispac said:
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
Click to expand...
Click to collapse
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone

reefuge said:
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
Click to expand...
Click to collapse
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Its going to take 5hrs to upload my backup

abispac said:
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Click to expand...
Click to collapse
ok ii'm thinking corrupted partitions too.... but if you are willing to try i've made a xt1063 easy installer script for you to try now normally i work on xt1068 and would test on my xt1068 - so have NO xt1063 its UNTESTED - use at own risk.....
just stock firmware / drivers / adb and mfastboot ( same as my xt1068 script) I see no reason it should not be compatible.
download to pc / unzip to folder / read instruction inside
https://mega.co.nz/#!Tok2DJ6T!ggMoQDfAzuA7cmQQjbGCbXolWZTnx_567vG02CiURVsxt1063 4.4.4 easy installer
I repeat it YOUR choice - if it works- great - if runs ok but rom remains same would suggest somethings corrupt - if it doesnt work at all back to square 1....
now im presuming your boot loader is unlocked, as will fail if locked or relocked - if you use and get error please report what they are, i would have done 5.0.2 but its only 50% downloaded with a 1 hr+ to still go, estimate 2 hrs from time of this post until I can post a link

im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...

abispac said:
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
Click to expand...
Click to collapse
just to let you know TWRP is now 2.5.8.0 fixes some bugs cause older versions know to break permissions in Lollipop!!
https://mega.co.nz/#!Dx03wTbD!3sDFubGomhegQqdoGzNb1RWnQwApzyaTlVq69uX1TqkFlash-able version (unzip to pc and flash from there) 2.5.8.0
https://mega.co.nz/#!n5cUQCAY!uf66vEcQlmtu6VZMLPxksEFMEioZUFpystzTP6kwU4I Temporary boot version (no flash) 2.5.8.0.
will look but cant promise

I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.

abispac said:
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
Click to expand...
Click to collapse
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?

reefuge said:
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
Click to expand...
Click to collapse
Yeah i tried those erase commands many many times and same result, i cant replace recovery at all, only boot of it, so when i do " mfastbooot flash recovery twrprecovery.img " then try to boot of recovery, i boot into factory recovery not, twrp, but if i do, "mfasboot boot twrprecovery.img" i can see the recovery img gets flashed and the phone boots of twrp. Weird behavior. So when i notice that i tried to flash a rom with mfastboot, and at the end i gave the command mfasboot boot recovery.img (the original rom recovery) then it gets flashed, and phone reboots, but i gets stuck at the motorola logo. This phone its playing hard to get....

heres, my backup https://mega.co.nz/#!md0AwbLR!uWe9PLklIugOziPLV6O_plbU-Zz9EXbqRvUVpYxECk0 hope you can find something.

Im going to take this phone to a shop to see if they can fix it as i have lost all hope, thanks refuuge for your help.

[TWRP 3.0.2-1][ROOT] Samsung galaxy A9 pro SM-A910F/9100 - 26/7/2016

TWRP 3.0.2-1. for the Samsung Galaxy A9 pro SM-A910/9100 - Qualcomm MSM8976
Please note I don't own this device.
Stock Recovery is posted below if required.
NOTE:
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Boot to download mode.
Flash with Odin using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
NOTE: ON SOME ANDROID 5.1.1 and 6.01 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Install with ODIN:
twrp_3.0.2-1_sm-a910f_25716
Update 8/2/2017
Fixed build for latest firmware :
twrp_3.0.2-1_sm-a910_a9100_7217
Stock recovery:
A910FXXU1APFC_stock_recovery
IMPORTANT
At the moment TWRP isn't working with encryption, this means the DATA Partition and internal storage cannot be mounted.
To mount the Data partition encryption needs to be removed and the boot image patcher needs to be flashed below
This can be done via the FORMAT DATA button under the WIPE option in TWRP.
Please note this will erase all user data.
The boot image patcher can be flashed with TWRP.
The boot image patcher MUST be flashed before booting the device to system or the DATA partition will be re-encrypted at boot time.
BOOT IMAGE PATCHER
Boot image patcher to remove DM-verity and Forced encryption.
Instead of flashing one of the boot images above flash the zip below with TWRP.
This was built by jcadduono not me, so props to him, I just modified it to work for this device and to remove the SEANDROID ENFORCING message.
Steps:
1. BOOT TO TWRP
2. FORMAT DATA
3. FLASH SUPERSU
4. FLASH THE BOOT IMAGE PATCHER
5. REBOOT TO RECOVERY
6. CHECK DATA IS STILL MOUNTABLE
no-verity-no-encrypt_ashyx
TO ROOT
Flash the file below in twrp.
http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.

Reserved

Thanks mate
everything is working
---------- Post added at 12:49 ---------- Previous post was at 12:43 ----------
may you know how to do Custom Boot Splash for A9100 pro ?

Hi, I'm on firmware A9100ZCU1APD5 so these boot images wont work right. So now to be able to mount data, what I got is that I'll have to first wipe data in twrp and then flash the boot image patcher in order to get full access to twrp?

omar.abbas said:
Hi, I'm on firmware A9100ZCU1APD5 so these boot images wont work right. So now to be able to mount data, what I got is that I'll have to first wipe data in twrp and then flash the boot image patcher in order to get full access to twrp?
Click to expand...
Click to collapse
TWRP >BOOT IMAGE PATCHER >FORMAT DATA >SUPERSU
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

ashyx said:
TWRP >BOOT IMAGE PATCHER >FORMAT DATA >SUPERSU
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Thanks I'll try now and get back to you
Sent from my SM-A9100 using XDA-Developers mobile app

Wow thanks a lot it works. Dont have to change the language to English everytime I boot into recovery ? and can finally make backups. Thanks once again, you're the man!!
Sent from my SM-A9100 using XDA-Developers mobile app

Thanks, hope for more development.
Thanks for the development, not much out there for the A9100/A910f. Own a A9100(CH), which came without any Google apps and full of Chinese applications and region locked. Was able to load recovery and unencrypt boot, root, sideload Google apps. Is there a way to remove my region lock? Wish someone would develope the A910f international firmware to port over to the A9100. The A9 phone has some pretty impressive specs, hope for more development. Thank you.

gsnewport said:
Thanks for the development, not much out there for the A9100/A910f. Own a A9100(CH), which came without any Google apps and full of Chinese applications and region locked. Was able to load recovery and unencrypt boot, root, sideload Google apps. Is there a way to remove my region lock? Wish someone would develope the A910f international firmware to port over to the A9100. The A9 phone has some pretty impressive specs, hope for more development. Thank you.
Click to expand...
Click to collapse
By region lock you mean unable to flash with ODIN?
You can use FLASHFIRE to flash the stock firmware.
Sent from my SM-T280 using XDA-Developers mobile app

ashyx said:
By region lock you mean unable to flash with ODIN?
You can use FLASHFIRE to flash the stock firmware.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
No, flashed recovery with Odin. I mean by region locked is the csc file is just for China and it's the only csc on the phone. So I'm seeing some Chinese in some of the stock apps still even though I changed the language to english. Location is working for me. But some of the apps still show Chinese

gsnewport said:
No, flashed recovery with Odin. I mean by region locked is the csc file is just for China and it's the only csc on the phone. So I'm seeing some Chinese in some of the stock apps still even though I changed the language to english. Location is working for me. But some of the apps still show Chinese
Click to expand...
Click to collapse
So what's actually stopping you from flashing another rom? Like I say you can use Flashfire.

Would like to stay stock Marshmallow 6.0.1. Tried to flash the rom for the A910f but if failed, same with the A9000(Android L). Both of these roms have multiple crc files for other regions. I think the failure is being caused by partition size. Didn't want to mess with for fear of bricking.

ashyx said:
So what's actually stopping you from flashing another rom? Like I say you can use Flashfire.
Click to expand...
Click to collapse
Have you tried it? Does it work? I tried using Odin but got some partition size errors and soft bricked my phone. So just need to make sure before I give Flashfire a go.
Sent from my SM-A9100 using XDA-Developers mobile app

So the actual failure to flash is the partition size, but which partition is failing?
More info needed here.
There are ways of adjusting the partition size on the device by simply flashing with the required PIT file.
Or the actual image itself can be resized to fit.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

ashyx said:
So the actual failure to flash is the partition size, but which partition is failing?
More info needed here.
There are ways of adjusting the partition size on the device by simply flashing with the required PIT file.
Or the actual image itself can be resized to fit.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
I can't remember which partition size error it was as it was a few days ago. So do you know anyone who has done that on this phone successfully? Because if it is possible then thats all I'd want right now.
Sent from my SM-A9100 using XDA-Developers mobile app

omar.abbas said:
I can't remember which partition size error it was as it was a few days ago. So do you know anyone who has done that on this phone successfully? Because if it is possible then thats all I'd want right now.
Sent from my SM-A9100 using XDA-Developers mobile app
Click to expand...
Click to collapse
It is possible as I myself have done it with other devices.
If you can try the flash again with ODIN and then post the output log then we can find out which partition fails.
Just reflash your stock firmware after the failure.
By the way I don't own this particular device.
In the meantime I'm going to download the stock A9100 firmware and check the image sizes against the a910f firmware.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

I tried to flash the A910F with Odin and It's give Auth fail on pitfile and stops there. I downloaded the firmware via samfirm 0.36 with binary to get the full 4 firmware files. Extract the pit file, point to it in Odin and BL, CSC, CP, AP in their slots and it always fail. Also does not work with flashfire with a single firmware file.
But now there is another way, I did it yesterday and works great. No Chinese! Credits to @dadimon29. You flash the full A9100 firmware but untick autoreboot. Once finished you boot back in download mode and flash @ashyx TWRP with Odin with no reboot. Reboot again to TWRP, flash the no-verity-no-encrypt_ashyx.zip, reboot again to twrp, now format data not wipe! Mount system and flash Supersu, your own CSC file and GPS.conf for your region and the GAPPS micro package. Now reboot to samsung and you will find everything is English or whatever language you prefer. And Google works out of the box, no permission errors. Now I can keep this phone!

steberg said:
I tried to flash the A910F with Odin and It's give Auth fail on pitfile and stops there. I downloaded the firmware via samfirm 0.36 with binary to get the full 4 firmware files. Extract the pit file, point to it in Odin and BL, CSC, CP, AP in their slots and it always fail. Also does not work with flashfire with a single firmware file.
But now there is another way, I did it yesterday and works great. No Chinese! Credits to @dadimon29. You flash the full A9100 firmware but untick autoreboot. Once finished you boot back in download mode and flash @ashyx TWRP with Odin with no reboot. Reboot again to TWRP, flash the no-verity-no-encrypt_ashyx.zip, reboot again to twrp, now format data not wipe! Mount system and flash Supersu, your own CSC file and GPS.conf for your region and the GAPPS micro package. Now reboot to samsung and you will find everything is English or whatever language you prefer. And Google works out of the box, no permission errors. Now I can keep this phone!
Click to expand...
Click to collapse
Could you tell me what firmware files you downloaded exactly? When you reboot your phone, does it show Galaxy A9 Pro in english? I'm still a little confused on the procedure too
Sent from my SM-A9100 using XDA-Developers mobile app

In order to get rid of the Chinese when you boot up I guess you have to flash the bootloader from A910F but you can't.
Download Samfirm 0.36 and download the latest SM-A9100 firmware.
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Be sure to tick Binary Nature.

gsnewport said:
Thanks for the development, not much out there for the A9100/A910f. Own a A9100(CH), which came without any Google apps and full of Chinese applications and region locked. Was able to load recovery and unencrypt boot, root, sideload Google apps. Is there a way to remove my region lock? Wish someone would develope the A910f international firmware to port over to the A9100. The A9 phone has some pretty impressive specs, hope for more development. Thank you.
Click to expand...
Click to collapse
You can try this out.
I have repacked the A910F firmware so it will be flashable on the A9100. I have replaced the A910F build.prop with the A9100 build.prop to help prevent boot issues.
It is the system image only. It should flash fine with ODIN in the AP slot. Whether it will boot or not is another matter, but I should think it will. If everything will be working, I don't know.
It may also be necessary to flash the A910F kernel boot.img. NOTE: this boot.img does not support encryption.
A910FXXU1APFC_no_encryptable_boot
Make sure you have a TWRP backup of the system partition or the stock firmware before flashing just in case you need to restore.
sm-a9100_system.img.tar.zip
.
.

Stuck in recovery

Hi guys.
tl;dr
every try to flash a custom rom ends in recovery with encrypted date. stock rom is working tho
I have a big problem with my beloved Mi9.
I had the 12.0 stable version of xiaomi.eu rom on it. then wanted to flash the latest developer version 12.1. (20.7.9).
downloaded the latest version, went to the recovery (twrp) and started flashing just like many times before. this time i got an "Error 7" or something like that and the phone didnt finish flashing. i reflashed the version i had before and the flashing went normal. but after it was finished i wasnt able to boot to the system, it always booted to the recovery, no matter what.
there, all the files were encrypted on /sdcard, no way to flash a new file or something.
i was able to reflash the stock rom via "MiFlash20191206" and relocked the bootloader. then i used "XiaoMiTool V2" to unlock the bootloader again, this worked. but everytime when i try to flash a custom rom, i get the same problem again.
phone boots into recovery, and after i try flashing something (no matter if i get an error or not) all the files on /sdcard are encrypted again and i cant boot into the system. i dont get past this.
i even tried the latest orangefox recovery, same issue there.
does anyone have an idea for a solution because i dont really want to have the stock rom as a daily driver.
thank you guys in advance
greetings
Xetro

Some advices here:
1. Make sure you have most updated version of TWRP
2. You can flash disable dm-verify&encrypt after flashing ROM every time(https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip). Of course, flashing it after OTA as well.
Good luck !

Thank you for your fast reply!
I have tried the latest twrp and latest orangefox.
After im landing in recovery after flashing a rom, data is already encryptet so i cant flash your zip. Only possibility might bei to queue both zips... Will try this! But it still wont let me boot to the system then...
What do you mean with "flashing it after OTA as Well"?

It doesn't make sense. You just flash the file what I posted and it would descrpted your data then make you boot into system after rebooting.
Just one situtaiton you cannot boot into system => If your data&cache is F2FS, you still need to flash a patch file to make you boot into system.
The last one thing and action that may help you: flash vbmeta.img with the comment of "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" under fastboot mode before flashing rom.
Good luck !
Xetro84 said:
Thank you for your fast reply!
I have tried the latest twrp and latest orangefox.
After im landing in recovery after flashing a rom, data is already encryptet so i cant flash your zip. Only possibility might bei to queue both zips... Will try this! But it still wont let me boot to the system then...
What do you mean with "flashing it after OTA as Well"?
Click to expand...
Click to collapse

EDIT:
man you safed my digital life! i just flashed your patch via adb sideload (never used adb before, had to figure out everything first) and it worked, right after patching it restartet to recovery, i manualle startet to system and it runs like a charm with the latest xiaomi.eu rom (which i flashed before)
can you tell me what exactly this patch did (for r noob pls)
thank you so much!
first of all, thank you for your effort!
i have a problem with this:
Kris Chen said:
It doesn't make sense. You just flash the file what I posted and it would descrpted your data then make you boot into system after rebooting.
Click to expand...
Click to collapse
after i flashed a new rom, i get in recovery mode automatically and the data is already broken, so i cant flash your patch via recovery...
orangefox shows all of my partitions as Ext4 except for USB-OTG (it has a vfat filesystem).
the thing is, everytime when i am in recovery mode (evertime i boot the phone) the data is encrypted and i cant flash any file because i cant find it.
the one and only time i dont hit into recoverymode is after flashing the stock rom with miFlash...

That's great and it's my pleasure to help me out.
I think dm-verify would play an important role - What's dm-verify ? Reference
Xetro84 said:
EDIT:
man you safed my digital life! i just flashed your patch via adb sideload (never used adb before, had to figure out everything first) and it worked, right after patching it restartet to recovery, i manualle startet to system and it runs like a charm with the latest xiaomi.eu rom (which i flashed before)
can you tell me what exactly this patch did (for r noob pls)
thank you so much!
Click to expand...
Click to collapse

I think I messed up royally

Long story short: I tried to install a GSI so I installed TWRP and flashed some necessary zips (vbmeta, mutidisabler, ...) from different sources and the GSI, but maybe it was a bad idea to follow multiple sources, because the phone was bootlooping when I tried to reboot into system. I then wiped everything and reflashed everything but that didn't fix it. After meddlilng around for a while, I was able to get into the download mode, so I thought of flashing the factory firmware with Heimdall. I used samloader and downloaded the supposedlly correct firmware (M215FXXU2BUH6/M215FODM2BUI1/M215FDDU2BUH1/M215FXXU2BUH6, region is BKD). When I was adding the files, I found out that I was missing the following files:
md5.img (MD5HDR)
efs.img (EFS)
sec_efs.img (SEC_EFS)
nad_fw.bin (NAD_FW)
param.bin (PARAM)
steady.bin (STEADY)
uhuh.bin (UHCFG)
blcmd.bin (BLCMD)
spu.img (SPU)
ul_key.bin (UL_KEYS)
nad_refer.bin (NAD_REFER)
dqmdbg.img (DQMDBG)
There were other partitions, but no files were listed for them, so I think they are not supposed to be flashed. There were also two different "fota.zip" files, but I didn't know what to do with them. Anyway, I flashed the other files, but the phone started bootlooping with the bootloader unlocked warning screen. I locked the bootloader from the download mode and tried again but no luck. I tried reflashing everything again, but the flashing stopped halfway with the message "super.img blocked by OEM" or something like that. I performed a force reboot with volume down + power and it rebooted into the "Emergency Recovery Function" screen. I reflashed everything again, but this time, without super.img, and it flashed fine, but the same bootloop problem remained. Looking up on the internet, it seems that efs.img has something to do with the IMEIs. I don't have any backup of it. I also don't know how to get the rest of the files (if all of them are even necessary), or what they even do/mean.
Basically, I'm trying to get it back to the factory software, or salvage it in any other way. Does somebody have any idea how to fix it?

Naah... Stuff like this happens to me all the time.
Download this ODIN first: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Then download this firmware: https://samfw.com/firmware/SM-M215F/BKD/M215FXXU2BUG2
Now first a few things:
1. You probably downloaded a engineer firmware that isnt allowed as of now.
2. Heimdall is mostly dead, last I checked. It isnt very wise to use it.
3. LOCKING THE BOOTLOADER IN A UNSTABLE STATE IS FOOLISHNESS. I do not mean to offend anyone, but pls dont do this.
4. I think you are using ErfanGSI/ some other port. These will NOT work. Only phhusson's GSI's have worked for me so far.
So coming back to the topic, Just open up the ODIN and connect up your phone. It will get recognized. If it is not in emergency/ download modes, just hold vol down + power, then press both vol buttons and connect to pc immediately - it will boot into dl mode.
Select the BL, AP, CP and HOME_CSC. Flash these.
It should reboot right back up into stock.
Also, are you using my vbmeta zip from ItsMeKande's thread?
Chill
GuruPrasadAH

Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
GuruPrasadAH said:
Also, are you using my vbmeta zip from ItsMeKande's thread?
Click to expand...
Click to collapse
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?

newt23 said:
Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?
Click to expand...
Click to collapse
My to-go answer is always crdroid. Its lightweight, customizable, and comes in variants with gapps, foss and vanilla. The one you're looking for is vanilla. Here's the post where u can find the link
Any official or unofficial lineage OS for Samsung galaxy M21
Hello everyone so I have a Samsung galaxy M21 with One UI 3.1 core. Are there any lineage OS official or unofficial builds for Android 11? If you know please reply to this, thank you in advance!!! 🙏🏾🙏🏾🙏🏾
forum.xda-developers.com

Hmm, it didn't work. I get bootloops...

Did you follow all the instructions given in that thread?
Only if you flash vbmeta, Multidisabler it will boot.
Then too magisk is recommended. The zips are in that thread.
Follow the instructions and let me know. On guy OldNoobOne also successfully flashed and booted a gsi
Let me know if it works
Chill
GuruPrasadAH

For Multidisabler just do a google search one for samsung devices will appear

Here's what I did (stock firmware, unlocked bootloader):
1. Boot into dl mode
2. Flash TWRP and boot into it
3. Wipe > Format data > "yes"
4. Reboot > Recovery
5. Advanced > Terminal
6. "cd external_sd/flash"
7. "super mount system"
8. "super flash system crdrom-v313-210921-arm64-bvZ-lite.img"
9. Install > vbmeta.zip, multidisabler-samsung-3.1.zip"
10. Reboot into system
And I get bootloops. Multidisabler detects Android 10, doesn't find the stock recovery and fails to mount /system. Maybe that's the problem? I'm using this one.

Also try flashing magisk... I dont really understand what is happening to you.
Maybe you set the system as read only? Really not sure.
Also, a ROM might be coming soon
Chill
GuruPrasadAH

Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!

newt23 said:
Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!
Click to expand...
Click to collapse
Use Overlay-Fix by dev Yillie. It had worked for me on crd too. You will find Yillie on telegram 'Galaxy M21 Updates' group, download from there.

Question [Updated] This is ENG binary Please Use USER binary after stock flash with Odin

New update to topic:
I decided to repair the software of my Galaxy S21 (Exynos) by flashing official firmware from Samfirmware, same version as I was running. It was in a bootloop before, so there was nothing esle to do. Phone was rooted with magisk, stock recovery.
I found what my firmware is from the recovery, found the exact same file, with the correct CSC.
Downloaded that firmware from Samfirmware, downloaded patched Odin from XDA.
Added, flashed, used HOME_CSC in order to preserve my data.
Reboot and immediately before I even get the boot logo or the charging animation, I get this error:
This is ENG binary Please Use USER binary
Allegedly this is what happens when you flash an engineering build, not an official one. But how? I downloaded and flashed official stuff? It's the exact same version my phone is already running. Where did I go wrong and how can I fix that?
I've attached the Download screen of my phone.
Thanks!
Old news:
Hello,
Hope this is the right place to ask for this kind of help.
I have a Galaxy S21 5G (SM-G991B), rooted with Magisk back in March 2021. Phone is bootloader unlocked, not encrypted, but the recovery is stock. Version currently running is Android 11. USB Debugging is enabled, but my computer is listed as unauthorised.
Yesterday my phone died due to low battery, so I plugged it and after it charged a bit I switched it on, only to be greeted with a constant bootloop. The bootloop is "soft", meaning only the system crashes, it doesn't go all the way to the initial boot screen (as if the battery was unplugged). The phone crashes about 1-2 seconds after the initial lockscreen is displayed.
Is there any way to help me recover this and save my phone? My entire life is there, from photos that can't be recovered, to authenticators I need for work and bank logins I need to be able to pay rent.
I thought about flashing TWRP and just doing a backup from there, but would it be as simple as that? All the tutorials talk about requiring to flash some extra zips and wiping the data, but those tutorials are combo root+twrp tutorials, and I've already done those steps. so no wiping should be needed to put TWRP on?
I'd be very grateful if anyone is profficient enough to help me recover the data, I already gave the phone to a data recovery company but they say it's unlikely anything will come out of it. If you manage to help me get my phone working as it was (or at least get my data back somehow), I'd gladly pay you the money for your efforts.
Help me XDA, you're my only hope.
Click to expand...
Click to collapse

Flashing TWRP = having to delete data (to be able to access the internal storage)
I am pretty sure (wait for confirmation before doing it) that if you flash the HOME_CSC file instead of the CSC on Odin it keeps your data.
This is why we need to vote with our wallets and buy phones with sd cards. I dont really care, because I never keep anything important on my phone, but I feel for you buddy.
EDIT: from here: https://www.droidviews.com/difference-between-csc-and-home_csc-samsung-firmware/
CSC – If you flash the CSC file, it’ll perform a factory reset of your Galaxy device and wipe all data while installing a new firmware to bring your device to the same state as it was when you purchased it. Go with CSC if you want a clean installation.
HOME_CSC – On the other hand, if you want to keep your Samsung phone’s data and settings even flashing the stock firmware, you can select the HOME_CSC file.
At your own risk, pls dont blame me if it doesnt work!

Flash a patched vbmeta again

GeeAyeZee said:
Flash a patched vbmeta again
Click to expand...
Click to collapse
Hi, what do you mean? Flash both TWRP and vbmeta, as if I'm doing it for the first time?
I think the phone was already decrypted while following the Magisk root tutorial, so these two steps should be the only thing necessary for the phone to boot to TWRP, right? I know how to rescue everything once I'm in there.

Try entering safe mode and disable all magisk modules:
Power on your Galaxy phone or tablet in Safe mode
We’ll walk you through how to start your Samsung Galaxy phone or tablet in Safe mode. This mode prevents third-party apps from running on your device.
www.samsung.com
You can access adb when on recovery mode or download mode so you can also enter safe mode via one of these commands:
setprop persist.sys.safemode 1
or
echo "1" > /data/property/persist.sys.safemode

dikime said:
Hi, what do you mean? Flash both TWRP and vbmeta, as if I'm doing it for the first time?
I think the phone was already decrypted while following the Magisk root tutorial, so these two steps should be the only thing necessary for the phone to boot to TWRP, right? I know how to rescue everything once I'm in there.
Click to expand...
Click to collapse
Flash the vbmeta file in odin

shaharofir said:
Try entering safe mode and disable all magisk modules:
Power on your Galaxy phone or tablet in Safe mode
We’ll walk you through how to start your Samsung Galaxy phone or tablet in Safe mode. This mode prevents third-party apps from running on your device.
www.samsung.com
You can access adb when on recovery mode or download mode so you can also enter safe mode via one of these commands:
setprop persist.sys.safemode 1
or
echo "1" > /data/property/persist.sys.safemode
Click to expand...
Click to collapse
The phone auto-enters safe mode after a few bootloops, so I guess that's beat. When the phone is in stock recovery, doing any adb commands tells me the device is recognized, but "unauthorized".

dikime said:
The phone auto-enters safe mode after a few bootloops, so I guess that's beat. When the phone is in stock recovery, doing any adb commands tells me the device is recognized, but "unauthorized
Click to expand...
Click to collapse
So you can enter download mode and flash stock (just super)

You gonna have to get authorized again. Check youtube for help. I had that issue a couple months ago. Think it had to delete the android folder and reinstall adb

Alright, decided to flash stock firmware with Odin. Found my files from Samfirmware, and since I want to keep my data, flashed HOME_CSC. Now the phone won't boot at all, giving the error:
This is ENG binary, please use USER
Now why did this happen and can I do anything to change that? I would really like to not flash CSC and wipe my phone, but it's looking more and more likely.
I used the patched 3.14.1 Odin, could that be the issue? Shouldn't matter.
The Download mode screen says: