yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A53 5G] Andoreid:
I got the same problem with these update requests showing up all the time on a rooted a536b without booting after confirmation. (Initially mentioned in this thread: https://xdaforums.com/t/google-play-systemupdate-problem.4649844/)

Just deactivate cidmanager (CID Manager package: com.samsung.android.cidmanager) with a third-party app like 'System App Remover' or via ADB:

1.) Enable USB debugging from developer options

2.) Get ADB files: https://developer.android.com/tools/releases/platform-tools

3.) In adb folder, press shift+right click on empty space in the explorer window, select “open power shell window here/ open command window here”

4.) Connect smartphone to the PC with a USB data cable and select “File transfer mode” on the phone

5.) Run the “adb devices” command to list up your device

6.) Run this command and then press enter:

adb shell pm disable-user --user 0 com.samsung.android.cidmanager
[Samsung Galaxy A53 5G] MitzaBobitza:
Thanks! Worked perfectly.
[Samsung Galaxy A53 5G] JeffATL:
For some reason without cidmananager enable I cant get the Verizon configuration and my video messages (mms) will not work. They work in Verizon Messages though , must be using internet.
[Samsung Galaxy A53 5G] Andoreid:
In most cases you only have to set up the provider specific configurations once so there is no need for the cid manager to check regularly. Without cid manager enabled you still should be able to request the network configuration from your user account at your provider, here verizon, where you receive a config message on your phone afterwards. Or enter the settings manually in your phones connection settings.
[Samsung Galaxy A53 5G] POQDavid:
I am also facing the same situation i was wondering did you use KitsuneMagisk also?
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
Hello all masters,

I need help and maybe advice. (i am completely noob )

I have Stock recovery backup from Android phone. (Doogee Mix 6+64gb) on SD Card.

It is 27 files named "userdata_xxxxxxx_yyyy.backup" to ".backup27"

After succesful backup via stock recovery phone was bricked and it is stuck in bootloop. ( i tired few things heh)

so all i have is SD Card with backup.

I read many threads here but nothing was successful.

I have dual boot ready with Windows and linux mint 21.3 cinnamon.

I tried combining all backup files into "img.ext4" file with command:

dd if=userdata_20190929_172118.backup skip=512 bs=128k iflag=nocache,skip_bytes oflag=nocache,append conv=notrunc of=img.ext4

(so skipping 512 bytes with every part) but final file "img.ext4" was not able to open anywhere ( linux reader, 7zip and others) it says file is not a archive.

i will be completely honest, i have in this backup somewhere in gallery screenshot on crypto wallet. So i really want to recover and extract data from backup.

Mod edit: Social media redirect removed.

Badger50 Senior Moderator
[Android Q&A, Help & Troubleshooting] alecxs:
open one file with HxD and show the first three blocks
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
Thank you for patience, so:

i merge all 27 backup files into one .ext4 file with manual skipping first 512 bytes, and open this in HxD as you say. this is result. let me know if it is what you looking for ( iam totally noob)
[Android Q&A, Help & Troubleshooting] alecxs:
please open one file with HxD and show the first three blocks. I need the original header of first file 2 GB not the merged skipped file.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
I am sorry , my bad. I am not native english so iam sorry. here it is. (first original file ) if you need something more let me know.
[Android Q&A, Help & Troubleshooting] alecxs:
Unfortunately your backup is encrypted, so it's impossible to extract it on PC. You can however try to decrypt it - on device - if prerequisites are fulfilled.

the origin device is available

you haven't factory reset the device

device is FDE encrypted

you have backup of metadata partition

you have raw access to storage

(mtk-su, TWRP or mtkclient)

In case of FBE file-based encryption the screen lock credentials are required for decryption. For FDE full-disk encryption there is hope.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
So i think i hit dead end:

-I have original device but it is bricked right now stuck in bootloop and even 3 repair shop were not able to flash new ROM. So not possible to boot up device.

-I have only backup of 27 files from stock recovery mode made on sdcard.

-i think that in process of flashing device it was reseted factory few times with stock recovery mode.

so in short there is no possibility to recover data right? even if someone will be able to fix the device to working again there is no way? i guess it is not simple like that put sdcard in working device and hit restore from sd card while in recovery mode. anyway Thank you for advices and your time i highly appreciate it. wish you all best. thank you for amazing support.
[Android Q&A, Help & Troubleshooting] alecxs:
for FDE you can double check the crypto footer is in last 16384 bytes of last file, but I doubt. for mediatek usually crypto footer is in separate partition metadata, and that's already overwritten. restoring backup is possible with bckp2raw, but it won't decrypt without crypto footer.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
ok, phone was locked via "pattern lock" method i am just thinking is there any way to restore backup to phone to be fully operating with lock again and just trying combinations? or after factory reset backup can´t be restored . Sorry for dumb question.
[Android Q&A, Help & Troubleshooting] alecxs:
yes, for FDE it's possible to restore it, it's even possible to by-pass pattern. but you need the crypto footer for decryption.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
I found some article about this specific device (doogee mix 6+64gb version) that even with mediatek processor they used FDE with Android 7 and higher. in my device was Android 7 nougat so maybe. I am not 100% sure. I made a call to some repair shop about 120km from me and they said they are specialist even to this concrete model and maybe they will be able to flash and repair phone to be operating again. My question is , If and really big IF they repair phone to be working again can i message you and maybe you will help me to try restore it? i will maybe try to contact manufacturer to obtain more informations.
[Android Q&A, Help & Troubleshooting] alecxs:
No. After flashing, the crypto footer is 100 % lost. Either you have a backup of crypto footer, or the data is lost. If that company is half as good as they claim, they can analyze your .backup files and tell you if crypto footer is included or not.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
I only have stock recovery mode backup on SD card soo i guess there is no chance than. Device is no capable to boot or do anything.
[Android Q&A, Help & Troubleshooting] alecxs:
I would first get a backup of metadata partition and double check the location of crypto footer. you can do this with mtkclient. for some devices the crypto footer is located at end of userdata partition, so it may included in userdata_20190111_193416.backup27. It might even possible they included backup of metadata partition (if so, I am very curious about)
[Android Q&A, Help & Troubleshooting] CXZa:
It's on metadata alright... FDE.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
ok, again i am so sorry for dumb questions (you must hate me). but i have very limited knowledge.

1. - How i am able to make "backup of metadata partition" without operating device.

2. - If i get it right if I open last (27 part) in HxD i can check if crypto footer is there right?

i will need like step by step. please be patience with me. i am doing my best.
[Android Q&A, Help & Troubleshooting] alecxs:
1. with mtkclient on PC. I recommend Linux.

$ python3 mtk r metadata metadata.img

2. yes. check the last 16384 bytes for "aes" with HxD editor.
[Android Q&A, Help & Troubleshooting] alecxs:
do you know the file name? I remember for LG Nexus it was on EFS partition /efs/metadata. all the links are broken. /metadata/metadata maybe? in fstab it only points to the mount point but not the file name.
[Android Q&A, Help & Troubleshooting] CXZa:
It's not a file. Text aes-cbc... is almost at the start of the partition.

On LG's it's in many cases on the encrypt partition...

This is from my LG...

0000000: c4b1 b5d0 0100 0300 4009 0000 0000 0000 ........@.......
0000010: 2000 0000 0100 0000 00bc 3301 0000 0000 .........3.....
0000020: 0000 0000 6165 732d 6362 632d 6573 7369 ....aes-cbc-essi
0000030: 763a 7368 6132 3536 0000 0000 0000 0000 v:sha256........
0000040: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0000050: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0000060: 0000 0000 0000 0000 e129 5356 2b70 ca83 .........)SV+p..
[Android Q&A, Help & Troubleshooting] alecxs:
I don't have it, but I don't use any encryption at all. Sure it's hidden in the header? I can see only ext4 partition.

:/ # blkid /dev/block/platform/soc/4804000.ufshc/by-name/metadata
/dev/block/platform/soc/4804000.ufshc/by-name/metadata: UUID="fc597be4-384c-458b-a4cb-1e7b4ac5354e" TYPE="ext4"
:/ # find /metadata
/metadata
/metadata/password_slots
/metadata/apex
/metadata/apex/sessions
/metadata/vold
/metadata/vold/metadata_encryption
/metadata/lost+found
/metadata/gsi
/metadata/gsi/dsu
:/ # hexdump -n1088 -C /dev/block/platform/soc/4804000.ufshc/by-name/metadata
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000400 00 10 00 00 00 10 00 00 28 00 00 00 69 0b 00 00 |........(...i...|
00000410 ee 0f 00 00 00 00 00 00 02 00 00 00 02 00 00 00 |................|
00000420 00 80 00 00 00 80 00 00 00 10 00 00 f3 51 bd 01 |.............Q..|
00000430 f3 51 bd 01 76 00 ff ff 53 ef 01 00 01 00 00 00 |.Q..v...S.......|
00000440
[Android Q&A, Help & Troubleshooting] CXZa:
There is only this much data on it..

----------------------------------------------------
Trailing Nulls Trimmer Bat by CXZa
https://cxzstuff.blogspot.com/
----------------------------------------------------
Target: mmcblk0p27
Size: 524288 bytes
----------------------------------------------------
Trimming... (this may take a while) : Done!
----------------------------------------------------
New size: 4633 bytes
mmcblk0p27-RestoreNulls.bat created.
----------------------------------------------------
Press any key to close this window . . .
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
Ok, i will be honest, I don´t know how to use mtkclient and python itself. And iam totally new into whole Linux OS. I made dualboot with linux mint 21.3 cinnamoth. I know for you it is like basic easy thing but i must google almost everything to even know what iam trying to do. I have very brave question, it is somehow possible to give you like teamviewer session and you check everything you want? i think it will be soo much faster and you and me will be 100% sure that everything was made right. I know i want to mcuh i i will be grateful. I can prepare all files ( all 27 backups in all OS )

anyway i opened "27th" part in HxD and just search all "aes" in all bytes. this is results. 29 records across whole file. Don´t know if it helps.
[Android Q&A, Help & Troubleshooting] alecxs:
follow the installation instructions. for linux it's easier. If you have mint, follow the instructions for ubuntu.

https://github.com/bkerler/mtkclient

If you have windows, follow the instructions in the thread.

https://xdaforums.com/t/guide-mtk-how-to-use-mtkclient-and-set-it-up.4509245
[Android Q&A, Help & Troubleshooting] CXZa:
Using the mtkclient DVD would have been simpler, but it's the connection that sometimes is the hardest part. One might need to connect some test points, remove the battery or empty it... Interesting topic, keep us updated...
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
Just for making sure, when i want to use MTKclient for backup metadata i need to device be connected? like i said earlier device is stuck in boot loop and was already factory reseted. Or MTKclient can extract metadata from .backup files?
[Android Q&A, Help & Troubleshooting] alecxs:
As described in tutorial, first start the read back, then connect the device.

Doesn't matter. You don't even need the battery. bootrom and preloader comes way earlier than bootloader, device must not even powered on.

Nothing can do this, it's different partition than the backuped one.

Just to be clear: What you do ist most likely useless, it's just to confirm that crypto-footer is indeed on separate partition - and therefore not included in backup.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
ok, so i had problems running MTKclient in Linux (some errors) so i decide to try in windows. i made all steps and run your code " $ python3 mtk r metadata metadata.img" it says i need to reconnect phone in "brom " mode so due instructions i poweroff device, hold vol up and vol down and connect cable. something happend and this is result. what are next steps or something? (anyway guys thanks you are like magicians)
[Android Q&A, Help & Troubleshooting] alecxs:
seems preloader file is required for bootrom mode. check some downloads for stock ROM if you can find any for this device. I would search for it myself but no time today sorry.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
i will try to fins something and let you know.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
i found this.

https://www.needrom.com/category/doogee/mix/

Can you just check if it is legit and if you think it will be good? I notices in description is that ROM is for HelioP25 but in my terminal it says HelioP20 is that a problem?
[Android Q&A, Help & Troubleshooting] alecxs:
I can't download it. I doubt Helio P20 and Helio P25 uses same preloader, I don't recommend that download. Just realized it's an old device so SLA/DAA auth bypass should work (mtkclient does it for you). can you repeat to read metadata but with no buttons pressed? buttons are for bootrom mode, no buttons is preloader mode.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
So i tried to Power Off device, start Terminal inside Mtkclient folder, start

python3 mtk r metadata metadata.img

and connect device without any buttons.

error code appears handshake failed.

View attachment 6076817
[Android Q&A, Help & Troubleshooting] alecxs:
maybe try with just one volume button? not sure about windows stuff - did you install vcom preloader drivers, UsbDk drivers or Zadig usb?

Maybe try to readback preloader (EMMC_BOOT_1) with SP Flash Tool instead, this is old method for dumping phones. VCOM preloader drivers must be installed like this.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
I will try everything, sorry for inactivity and thank you for patience. i had spine surgery so recovering. i will try next things soon
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
Ok, on windows i ahd installed UsbDk Drivers. i tried just one volume button ( both alternatives - single Up button and single down button)

Button down holding- Handshake failed

Button up holding - enter brom mode again (so the same as previous)

Next i download Sp flash tool v 5.1924 windows version. I follow instructions and sucessfully install VCOM drivers and restart Windows in mode with disabled certified drivers mode. Can you give me please next instructions? in sp flash tool in readback section i need some scatter file. Should i download some or is there any way to obtain it from device?.

(bonus quesion: Do you think that first version of dumping metadata with python command can work better and have success in Linux space?)

EDIT: Or just dumb question, should i try mtk client metadata read again with VCOM drivers? can it make change in output with no buttons pressed?
[Android Q&A, Help & Troubleshooting] alecxs:
yeah try all. for SP Flash Tool scatter file can created with WwR MTK but you need to find a tutorial. don't you have scatter file shipped with ROM download?

anyway, afair you don't need scatter file for readback, just read the whole EMMC_BOOT from start offset 0x0 that's the preloader.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
So, I tried again cycle with MTK client and with VCOM drivers and disabled driver signature with command:

python3 mtk r metadata metadata.img

basically same output as before, with "brom" mode same result and without buttons " handshake" failed

___________________________________________________________________________________________________________

SP Flash Tool Method ( v. 5.1924)

In readback tab when i clicked "readback" it always says i need to load a scatter file. Soo i tried to download sooo many ROMS and scatter files. Almost everytime it give me some error. I googled error code and found out that i probably have bad scatter files because almost everywhere is ROM with Helio P25 and not P20 as my device or different version based on storage and RAM version of device. After lot of ROMs i found 1 which clamis it if official from manufacturer. I load a scatter and only "check" preloader in "download tab.

View attachment 6082612

So in readback tab I added ROM , start readback and with one buttton pressed (volume up) and connect a device. I think all was succesfull and a get "readback ok" notice and it created file "ROM1" in sp flash tool folder with only 4kb size ( don´t know if it is normal)

View attachment 6082613

In case this was all good, what are next steps? thanks
[Android Q&A, Help & Troubleshooting] alecxs:
You have done it right, but you need readback of EMMC_BOOT instead of EMMC_USER to get the preloader.

Next step is, provide the file path as argument to the --preloader flag of mtkclient.

Alternative, if mtkclient still failes, you can use the preloader file for creating a valid scatter file with WwR MTK 3.51 (guide step 30)
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
Ok, how exactly can i choose EMMC_BOOT instead EMMC_USER. i had checked preloader (EMMC_BOOT1) in download tab (in SP flash) can you direct me?

If it will be successful can you please provide some steps or link to "provide the file path as argument to the--preloader flag of mtkclient" (which command should i used inside MTKclient)

Thank you so much.
[Android Q&A, Help & Troubleshooting] CINOBER:
Try out this : Factory reset, user defults, reboot - connect the charger - encrypt your phone file system (user setup /Security/ Phone encryption) -

after this : load into the user backups ...

Ps: possible if your phone was encrypted under the backup, after incompatible user setups ...in datastore etc..=database crash because the backup is encrypted but after the factory reset the phone db isnt...
[Android Q&A, Help & Troubleshooting] alecxs:
from memory (untested): in the readback tab - right click (or add?) - new entry - save as file <name> - choose region EMMC_BOOT_1 - set start address (offset) 0x0 - set end address (length) 0x800
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
Ok so i figured out how to do it finally. So with only "preloader " checked in download tab I manage to change EMMC-USER to EMMC-BOOT_1 in readback.

View attachment 6084684

with this settings, i hold down only volume up and connect device. readback was ok.

View attachment 6084685

So i should have correct file of preloader with right partition. Can you please describe next step little bit more detailed? which and how to you commmand next with created file ROM_0. Thanks
[Android Q&A, Help & Troubleshooting] alecxs:
Sorry I believe size is 0x8000 not 0x800 my bad. Next, do what you have done before with mtkclient, but with preloader given.

python3 mtk r metadata metadata.img --preloader=./ROM_0

Then share the metadata.img please for further analysis.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
Hello, so i have some results. (negative)

1. I made successfull readback of preloader with EMMC_BOOT1 with start 0x0000 and lenght 0x8000 . It came up with "ROM_0" file with size around 32kb.

2. Next step was little harder. I probably make some mistake. I put this File (ROM_0) into main folder of MTKclient. Restart PC in "disable driver signature mode" start terminal inside folder and put you command.

python3 mtk r metadata metadata.img --preloader=./ROM_0

( This is where iam not sure if it is enough to put ROM_0 into folder or i need to "modify" command to put path to ROM_0.) because i start brom mode (volume up and down holding) and this is result:

View attachment 6087304

Because of note : "no preloader given" i think i must somehow put path into command? iam noob i know.

3. When i tried to run command in "preloader" mode (without buttons) i get same status as before : Handshake failed.

So i think it can not found or read preloader. So can you give me some right format with path ? how it should look? Or ROM_0 from spflash tool is corrupted or something. Thank you
[Android Q&A, Help & Troubleshooting] alecxs:
Seems like... maybe the necessary information is not in preloader? So forget mtkclient and use WwR MTK to create scatter file based on already dumped preloader. once you have scatter, you can dump metadata with SP Flash Tool instead.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
Ok, i tried some variation. I opened Wwr and in automode choose scatter file for MTK6757D and save it.(opened it with notepad and checked start adress 0x0 , lenght 0x80000 EMMC_BOOT_1. Next i opened scatter in Spflashtool (there was only preloader partition) after readback i get error.

View attachment 6087354

you mention i can create scatter file based on already dumped ROM_0 with sp. but in WwR i can only see to create just simple clean preloader scatter. Can you please write me some details how to do it properly?

I tried to open already dumped ROM_0 in WwR in preloder tab. but it said this.

View attachment 6087355
[Android Q&A, Help & Troubleshooting] alecxs:
see this text file this worked for me on older mediatek device

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-77795016
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
I will check this text file later. But i noticed someting. I opened scatter file (one downloaded with firmware, which i was using to dump ROM in spflash. ) in Notepad and noticed that "preloader" partition has lenght not 0x8000 but 0x40000.

View attachment 6087690

So i dump preloader in spflash again with this settings.

EMMC_BOOT_1

Start addr: 0x0

Lenght: 0x40000

Readback was ok (it takes little more time than last) and create file with 256kb size.

Next i open new created ROM in WwR MTK in preloader tab. and it finally open right.

View attachment 6087691

Don´t know if this help but i am able to save preloader.bin now.
[Android Q&A, Help & Troubleshooting] alecxs:
Now you have correct preloader.bin try mtkclient again.
[Android Q&A, Help & Troubleshooting] Alfa_omega001:
OK so I tried use code:

python3 mtk r metadata metadata.img --preloader=./ROM_0

Inside MTK client with volume up button (Brom mode) it makes difference and this was a result with right preloader.

View attachment 6090120

But i don´t know what i am looking for. I expected file "metadata.img" inside mtk folder but there is no file.

2. Since i have probably right preloader dump from spFlashtool. I open it in wwr and save preloader.bin. Next I tried dump second dump (pgpt) in sp flash tool with same parametres but in EMMC_User region. Dump was successfull and i was able open this inside wwr to see tables.

View attachment 6090125

What is next step? what can i do? thank you.
[Android Q&A, Help & Troubleshooting] alecxs:
yes. Idk what happens.

According to this guide next step probably is 36. full ROM dump and creating scatter file. But now that you have offset and length already, maybe you can skip that steps and directly readback metadata from EMMC_USER in SP Flash Tool.