yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A52s 5G] bobfrantic:
And so, Samsung support's only course of action is we must take our phones to a repair center. They cannot send the information to higher levels from the support department. Spam them on Twitter, Facebook, Messenger and Samsung Members will only frustrate with no promise our complaint will reach the people that should be informed of our displeasure...
[Samsung Galaxy A52s 5G] gorbyebrius:
Sweden with NEE as csc, unlocking breaks camera... Very disappointed, I was close to getting the Xiaomi 11T but opted for this one which I now regret... Going non-root is a complete deal-breaker for me.
[Samsung Galaxy A52s 5G] LimEP1227:
Taiwan with csc BRI

and yes I have camera problems when unlocking the bootloader
[Samsung Galaxy A52s 5G] bobfrantic:
No thanks. To far away from me to be bothered. Be 4-6 hour by train and bus there and back and no guarentee for a fix...
[Samsung Galaxy A52s 5G] bobfrantic:
it may be one hour as crow flies.. but i don't fly and i am not a crow hahaha
[Samsung Galaxy A52s 5G] bobfrantic:
From my home to brussels is 2 hours train & bus then another 40 min bus to the repair shop. The one in antwerp is 2.5 hours one way bus and train. I hope some lives near a repair shop and can go see if it requires repair BUT I am 99.44 % sure it is firmware issue and hardware.
[Samsung Galaxy A52s 5G] bobfrantic:
I'm curious. Has anyone taken their phone to a service center to see if they can fix the issue of camera failure when the boot loader is unlocked? If so, please report if they can correct the issue or if they confirm it is a firmware issue that Samsung has to corrected in an update... thanks in advance.
[Samsung Galaxy A52s 5G] bobfrantic:
I may look into this but, I hope that in the next firmware update things maybe, a big maybe corrected as I believe it is a firmware issue with faulty coding in there somewhere... because with the z fold 3 phones getting the same issue fixed with their update to android 12... see:

Unlocking the bootloader no longer kills the Galaxy Z Fold 3's cameras

Unlocking the Galaxy Z Fold 3's bootloader no longer kills camera functions on One UI 4 beta based on Android 12. Read on to learn more.

www.xda-developers.com

in the second paragraph, user @exocetd has said there is a file can be modified to correct this issue and I wonder if he has released the name of the file and what modifications to it to fix the issue..
[Samsung Galaxy A52s 5G] bobfrantic:
Ok, discussion about warranty is ended. IMHO this has gotten way off topic. Was supposed be a survey of peoples experience with unlocking boot loader and camera, not legal warranty issues that no one wants agree. So I will be asking a moderator to clean things up to get back on topic.
[Samsung Galaxy A52s 5G] bobfrantic:
Not sure, I don't remember what you wrote. PM me if you have it saved anywhere so I can investigate... sorry. I just got tired of the bs. all i am saying.
[Samsung Galaxy A52s 5G] Badger50:
It should fixed now. Sorry about the mistake.

Cheers: Badger50
[Samsung Galaxy A52s 5G] bobfrantic:
it is something i've thought of doing but first i am waiting for the next update which i hope comes soon.... and i think the thread has had no activity due to the bickering over warranty..
[Samsung Galaxy A52s 5G] bobfrantic:
Latest Feb 2022 update, at least for LUX region, sadly camera failed with bootloader unlocked. So not fixed yet...
[Samsung Galaxy A52s 5G] V0latyle:
Since this thread is starting to get out of control, I want to make a few things crystal clear:

The moderator team does not exist to mediate personal disputes. Do not report posts simply because you don't like what someone has to say. This is an abuse of the report system, and continuing to do so may result in action being taken against your account, including but not limited to permanent warnings and account suspensions.

Flaming and disrespect will not be tolerated. We expect all of you to conduct yourselves like adults and treat each other with respect. If someone is breaking the rules, simply report their post and let us handle it. Do not engage.

All members are expected to conduct themselves according to the XDA Forum Rules. This holds true for all of you, regardless of how long you've been with the forum, or how justified you might think you are in your actions.

Consider this a warning. If this continues, this thread will be locked, and members involved in conflicts will face administrative action.
[Samsung Galaxy A52s 5G] TTmouse:
Hi, I'm new here, I'm from Spain, I bought an A52s at Christmas, and a month ago, I tried to unlock the bootloader and it didn't go well.

Cameras stopped working, and NFC stopped working, so I tried loading the original firmware again to reset, and it didn't work.

Knox protection was triggered, so I tried my luck, and sent the smartphone to samsung support claiming software problems.

After 3 days I was contacted, that the knox had been triggered, and that the warranty had been revoked due to misuse.

I was charged 150€ for samsung technical assistance to restore the software properly working.

So now I have the phone working again and the wallet lighter, if I had done my homework properly I wouldn't have even tried rooting.

I came here to explore the forum a little in search of answers, but from what I see in this model there is not much news yet. the most certain thing is I go for another model where I can have a little more freedom, samsung is getting very restrictive.
[Samsung Galaxy A52s 5G] testestestest:
Camera NOT working for csc XEZ even with the latest firmware A528BXXS1BVB1 (2022.02.01).
[Samsung Galaxy A52s 5G] oli231:
Poland XEO camera working
[Samsung Galaxy A52s 5G] theghostkill:
Working for me with this guide.

CSC - INS (India)

Ver - 4.1 (April Patch)

https://xdaforums.com/t/updated-how-to-root-galaxy-a52s-5g-sm-a528b.4382243/
[Samsung Galaxy A52s 5G] theghostkill:
Edited in the previous comment.
[Samsung Galaxy A52s 5G] zate27:
Switzerland:

CSC = AUT

Unlocking BL causes camera problems. Only 1. April with Safety Net fix makes the camera work again.
[Samsung Galaxy A52s 5G] YouWotm8:
Greece:

CSC = VGR with February's 2022 update

Unlocking BL doesn't affect front or back camera at all 😁 Don't know the original country of the phone though. Will root and flash April's update to see if anything changes
[Samsung Galaxy A52s 5G] BlueChris:
Same here with CVE1 latest version.

All are fine & recording also.
[Samsung Galaxy A52s 5G] bobfrantic:
Region your phone is from?
[Samsung Galaxy A52s 5G] BlueChris:
EU Vodafone Greece

VGR csc
[OnePlus Nord 2 5G] 13singhanhad:
Hsy guys. I Use a Oneplus Nord 2 5g. Initially, the OIS used to work on apps like instagram and snapchat while making stories, and also worked on video calls. But i noticed it stopped working in 3rd party apps. Is there any fix to it? I've tried formatting and getting it flashed again but no success yet.
[OnePlus Nord 2 5G] mdsaqlainsaeed:
Got any answer?
[Moto G7 Questions & Answers] abarrett79:
Got sloppy with a brief return to stock to reprovision my sim card. When going back to a custom rom I managed to run the copy script from the wrong slot. My problem lies with getting a working blankflash. It seems those customer hating folk over at Lenovo keep revoking firehose files. I'm looking for ideas on solutions. Can't get to telegram because my phone is dead. I'm very good with computing but haven't learned how to build a singleimage file yet and how flexible the firehose is for using different models, mine is xt1962-1 (us retail, amazon, in case I'm chasing after the wrong device). Any pointers or links greatly appreciated.
[Samsung Galaxy S20 FE Questions & Answers] moovtome:
Hello!

Please, maybe someone knows where to find unofficial LineageOS for Galaxy S20 FE 4G Exynos (r8s).

r8s have some results here: https://www.lineageoslog.com/statistics

Rgrds!
[Samsung Galaxy S20 FE Questions & Answers] 3mel:
2 attempts to build it have so far been only unsuccessful. with a lack of experienced developers it's been left to keen first timers to give it a try. give it about a year and maybe things will have changed. in the meantime you can always flash a Lineage GSI rom.
[Samsung Galaxy S20 FE Questions & Answers] moovtome:
Thanks for info. Hope in next year, LOS will be fully supported.

Would be really great.
[Touch Diamond, MDA Compact IV General] johnjm28:
Hi All, first post on a great forum... pity its due to a problem!

My Diamonds virtual keyboard has been blacked out, no matter what I do, if I change the input method etc, it still pops out to input text, but I cant see any of the keys, its all black. If you press blindly it inputs, but it doesnt help me not being able to see the actual keys lol

Its rom version 1.93 and ive got the Core DivX player and Garmin XT installed. Thats about it... Any help is appreciated!
[Samsung Galaxy A70 Questions & Answers] domi.arnold:
So guys,

recently I created a topic, but with the wrong approach.

I want to start the phone as soon it gets plugged in the power.

Some older phones supported this out of the box.

After searching the www I found out, that before getting the new android versions, there was the possibilty to do this via the LPM reboot.

But with the new android versions this insn't possible anymore.

Does anybody have a solution for this.

The phone is rooted and runs twrp.
[Google Pixel 6 Pro] r9003:
when setting up an alarm, i enable a Google assistant routine,

but, in there i only have button to add another action, or arrange the steps, no delete button

I don't see how to delete steps (I don't want to hear news for every alarm)
[Google Pixel 6 Pro] craigacgomez:
Tap/click on the step you want to remove, and you will see a "Remove Action" button at the bottom.
[Google Pixel 6 Pro] r9003:
wow thank you so much ...unless you just hacked my phone and made that happen :D
[Realme 8 Pro] StratOS_HTC:
So far a couple of guys here on the forum has asked me how did I flash GDPR to EXPORT also with different Project ID.

The thing is that the guy from Pakistan via TeamViewer flashed mine phone from GDPR to EXPORT even with different ProjectID.

That means different PCB[2-7].

The truth is that he was using Production or Developer mode with manual servers, guess from China.

He was able to flash from GDPR Project ID-20713 .44 to EXPORT Project ID 20711.

Have provided him the PCB from start 0020713, didn't check it at flashed EXPORT, in 2 days it flashed me back.

From the downloaded files in C:\temp\MsmDownloadTool\DownloadData\ I have checked and found out differencies from the original downloaded roms.

All USF flashed files are the same, except gpt*.bin files, some XML and super*.img and of course userdata.img.

The only difference as I can spotted while doing the forensics is that multi_image.mbn NON-HLOS.bin, even oppo20711.bin and oppo20713.bin are different from the original download rom on the net.

Some of you said that from the aftersale mode you cannot flash GPRD<--->EXPORT witch have the same PROJID.

Looking forward for a support if any1 know a guy with Production or Developer credential or any1 who can give us support regarding this question.

I cannot contact that guy via WA - non existent ?

Weird thing is that now I know I can use keylogger and it works also threougth Team-Viewer, so if any1 wants to test and if they use Production or Developer credential could be usefull for further tests.

That has been stated just for testing purpuses. Use it at your own risk.

Need feedback some Oppo/Realme developers could easily provide that informations for sure.

I can feel/know that the knowledge is hard to share if it's paid, but we are lowering the costs after all ...

To acess PCB on phone dial *#888#

to get current ROM info use the mine info script for RMX3081 more details here.

I'm really looking forward to get this out ...

I'm still looking forward to get my UFS box and ISP circuit boad to do more forensics on the files on UFS.

Till then ...
[Realme 8 Pro] Efigeah:
@StratOS_HTC

I'm studying how the program that decompresses ofp, so that it does the process of recompressing an uncompressed file, it on github only has the recompression process just for oneplus, and from what I studied the code it basically only does the inverse process, so I'm trying to do this for the ofp files as well.
[Realme 8 Pro] StratOS_HTC:
Won't work.

GitHub - bkerler/oppo_decrypt: Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter

Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter - bkerler/oppo_decrypt

github.com

The current flashing Oppo/Realme program is only for OFP (Original firmware package).

You must have a production/manufacture credentials and access to server to done this ok.

You can pack in with the same public key as unpacker, but the flashing procedure won't work.

Need to change also *.xml

It won't work also in fastboot (GDPR) because if you have locked bootloader the only way to flash is throught EDL.

Firehose need auth,verification and certified checked files.

If you have unlocked bootloader (Export), you can only flash non-critical partitions. (Have checked allready).

And also recovery *.ozip is still not documented and is implemented on both versions.

Acess on temp files on /data/ is denied and also rewriting dev blocks via $ and not #.

From what I have learned the thing is highly complexed and will take time to do something.

Realme EU service is just a "bot" for answering.

First the EDL mode in our phone has it's own signing and verification and it's undocumented and via current method (emmcdl, QFIL ...) not implemented that it shoud work.

I guess it should with some USB sniffers via current driver and with official MSM application.

GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)

Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - bkerler/edl

github.com

RMX3081 - No kernel driver supported: Operation not supported or unimplemented on this platform · Issue #197 · bkerler/edl

For Realme 8 Pro : MSM8998 - debugmode. The device is first in EDL Sahara mode, then go out to the normal ... Guess this is not the same as in QPST server. It lock the device in EDL Sahara mode (do...

github.com

The GDPR bootloader cannot be unlock ! (Guess 4 now :()

So no custom flashing possible. AVB and verity is still present ... No flashing, no root ...

Fully stucked for GDPR rom.

Kernel can be checked/modified/moded :

https://github.com/realme-kernel-opensource/realme_6pro_7pro_8pro_X2-AndroidR-kernel-source
[Realme 8 Pro] StratOS_HTC:
... Also the EXE file for flashing he used were different then the original from the zip for .44 release of OFP zip.

They use jenkins software for OFP, also ota ...

From the original OFP *.zip (md5sum.md5.txt) for both Export and Gdpr

88b86647b46496a0d8c8054ed25b2a84	/work/jenkins/workspace/ofp_fat_release@3/759948/system_vendor/20713/RMX3081GDPR_11_A.44_2021110921090000/build.prop	88B86647B46496A0D8C8054ED25B2A84
8babba8c5a1b36ec0ac94d51825106bd	/work/jenkins/workspace/ofp_fat_release@3/759948/system_vendor/20713/RMX3081GDPR_11_A.44_2021110921090000/super_map.csv	8BABBA8C5A1B36EC0AC94D51825106BD
0f1ad197293466548b532db1d900b8fe	/work/jenkins/workspace/ofp_fat_release@3/759948/system_vendor/20713/RMX3081GDPR_11_A.44_2021110921090000/MsmDownloadTool.exe	EA6EBBBA5F193129CD9E09ED09F51569	MsmDownloadTool_V2.0.67-Rcsm.exe
a00bc5314ae01bf663f24b9720575cdc	/work/jenkins/workspace/ofp_fat_release@3/759948/system_vendor/20713/RMX3081GDPR_11_A.44_2021110921090000/RMX3081GDPR_11_A.44_2021110921090000.ofp	not checked

75db4d94375063a76adec420d84e21c4	/work/jenkins/workspace/ofp_fat_release/759953/system_vendor/20711/RMX3081export_11_A.44_2021110921030235/super_map.csv	75DB4D94375063A76ADEC420D84E21C4
0f1ad197293466548b532db1d900b8fe	/work/jenkins/workspace/ofp_fat_release/759953/system_vendor/20711/RMX3081export_11_A.44_2021110921030235/MsmDownloadTool.exe	EA6EBBBA5F193129CD9E09ED09F51569	MsmDownloadTool_V2.0.67-Rcsm.exe
64738ed2610959172300a1802bfb2be9	/work/jenkins/workspace/ofp_fat_release/759953/system_vendor/20711/RMX3081export_11_A.44_2021110921030235/build.prop	64738ED2610959172300A1802BFB2BE9
392a5f8b25368ff1aa63017ec072de73	/work/jenkins/workspace/ofp_fat_release/759953/system_vendor/20711/RMX3081export_11_A.44_2021110921030235/RMX3081export_11_A.44_2021110921030235.ofp	not checked

The 1st column is md5 from the enclosed files for both releases of the OFP zip.

The 2nd column is path to file on server and the file name.

The 3th is the MD5 check I made with md5 for each file.

The 4th is the name of the exe in zip

That means that the included EXE file in zip for both releases (EXPORT and GDPR) (MsmDownloadTool_V2.0.67-Rcsm.exe) are different from the original MsmDownloadTool.exe regarding MD5 check in the original md5sum.md5 text file. !

For both releases they use the same flashing exe in official *.zip.
[Realme 8 Pro] Efigeah:
@StratOS_HTC The change in the ofp package that I intend to do is just take the NV of the GDPR package and put it inside the EXPORT package, and flash it with authentication from the original server, the person who has access, which is the same as you mentioned earlier, will tell me help with that.
[Realme 8 Pro] StratOS_HTC:
Hi.

This won't work.

First the reseler (aftersale) credential is used to flash the same PROJECT ID, Same PCB [0-7].

It is used to flash with exe from the OFP zip.

Second of all, a lot of flashed files written on USF are same for both releases (GDPR-EXPORT).

The difference between is only in multi_image.mbn, NON-HLOS.bin, oppo*PROJID*.bin (all have same size !, but are different), of course userdata.img and of course GPT files gpt_main*.bin and gpt_backup.bin.

Also all Chainded tables and Digest to sign.

Fur sure some xml files also.

Ok, let's start the NV.

The NV is just a way to identify the needed programs,settings,language, enabled/disabled hardware regarding location,provider ...

That is our superimage.

The check is primarly checked via firehose EDL Sahara via XML communication.

That is why we get errors via QFIL,EMMCDL ...

It's the same oppo project, the Realme use just the new branch difference in NV (superimage).

The contents of sparsed superimage determine the situation, that is PROJ ID and specified NV ID.

You were right about that, but since the oppo uses signed NV digest for NV this is mission impossible.

View attachment 5510155

But since no debugging for current flashing via OFP is available only USB debugging or sniffing would be optional or EDL exploit ...

Guess super image create the needed init at start and change the flashed files at init.

Will check it after i get the UFS Box and guess in time we will be able to access UFS to check that.

Enclosing the difference in OPF .44 for the both releases and NV infos.

The file is in *.zip, rename it to *.xlsx !

file Diff.zip-->Diff.xlsx

View attachment 5511695

NOTE :

The verification and Authentication of files is via Sahara firehose original program use. The production/development credential are used only to download the needed files for flashing and NV files.

For now no optional flashing is available. Just FRP reset, Format - Factory reset and Partition Infos (Manager and scatter info).

Regarding the Production/Development credential I'm stucked.

The guy from PA (account on WA) is not available anymore ...
[Realme 8 Pro] StratOS_HTC:
This is for 2169b ?

Can you upload those :

prog_firehose_ddr4.elf

prog_firehose_ddr4_fwupdate.elf

prog_firehose_ddr5.elf

prog_firehose_ddr5_fwupdate.elf

prog_firehose_lite.elf
[Realme 8 Pro] Efigeah:
the projectid is 2169B
[Realme 8 Pro] StratOS_HTC:
Found out something new when updating via ota.

[ro.build.version.ota]: [RMX3081NV44_11.A.44_1440_202111092109]

Well I found out that the encrypted super sparsed image (system.img) consist out of multiple 3 superx*.img.

The NVid can be get from ota, so mine is NV44

nv_id	nv_text	super_0_path	super_1_path	super_2_path
1000100	EUEX	super.0.35e5269c.img	super.1.de62627a.img	super.2.3e674d94.img
1010001	TR	super.0.35e5269c.img	super.1.de62627a.img	super.2.bd4abb42.img
10000101	EU-NONEEA	super.0.35e5269c.img	super.1.de62627a.img	super.2.358c76e4.img
10000111	UA	super.0.35e5269c.img	super.1.de62627a.img	super.2.0d48ab09.img
10001010	GB	super.0.35e5269c.img	super.1.de62627a.img	super.2.745e1476.img
00000000	GB	super.0.35e5269c.img	super.1.de62627a.img	super.2.745e1476.img

Last 2 digits (for mine GDPR) are in hex, so : 44#h=68#d=01000100#b

So mine id="01000100" text="EUEX"

[ro.product.name]: [RMX3081EEA]

or via shell : adb shell getprop ro.build.oplus_nv_id

1st and last have different ID and same all 3 super, in majority the difference is NV ID and the super2.

Since oppo/realme for android11 doesn't allow change on the geo location as it were on previous version, only change via NV, but it has to be done vith developer/production credential, not the after sale (can only flash same ProjID-PCB).

Looking forward just for feedback regarding the info from getprop [ro.build.version.ota] and the original rom ( contents of the super_map.txt included in tho original OFP's zip).

Since all superx*.img is AVB encrypted by default and mounted as system :

boot:fstab.default :

system /system ext4 ro,barrier=1,discard wait,avb=vbmeta_system,logical,first_stage_mount,avb_keys=/avb/q-gsi.avbpubkey:/avb/r-gsi.avbpubkey:/avb/s-gsi.avbpubkey
system_ext /system_ext ext4 ro,barrier=1,discard wait,avb=vbmeta_system,logical,first_stage_mount
product /product ext4 ro,barrier=1,discard wait,avb=vbmeta_system,logical,first_stage_mount
vendor /vendor ext4 ro,barrier=1,discard wait,avb=vbmeta_vendor,logical,first_stage_mount

system_ext and product and vendor is also mounted

Looking for feedback for getprop [ro.build.version.ota]

and the super_map.txt from the original flashed OFP.

Thank you for the support.
[Realme 8 Pro] Efigeah:
@StratOS_HTC officially released bootloader unlock for my version, and it is GDPR, in my case it was just use the deep test app and unlock by fastboot normally
[Realme 8 Pro] StratOS_HTC:
HI.

There is no official release of the deep test for GDPR [EU] RMX3081.

on EXPORT https://xdaforums.com/t/rmx3081-deep-testing-app-export.4389025/post-86265113 it work, have test it.

On GDPR :

View attachment 5517603

It could be there is something wrong with my flashing back from EXPORT --> GDPR or something else ?
[Realme 8 Pro] Efigeah:
it could be your app or a version that works for the app hasn't arrived yet, I'll send you the app that worked for me, test it out
[Realme 8 Pro] StratOS_HTC:
Thank you.

It's the same.Same error still exists on mine GDPR [EU] rom .44.

The files are exactly the same.
[Realme 8 Pro] czaroslaw:
Realme 7 5G, RMX2111 -> flashed RMX2111EU_11_A.22. -> region changed to Multilingual EX -> unlocked bootloader with In Depth test -> updated to RMX2111PU_11_A.35 with ota ozip (PU version, Brazil), rooted with Magisk.

System update cannot find ota update to Android 11 (with vpn also). I cannot find any ota firmware. Therefore I think the only way is to flash full firmware which can be downloaded.

I have found two firmwares:

RMX2111GDPR_11_C.09

RMX2111export_11_C.06

Can you explain which version is better? Are there any differences in system functionalities? I would like also to unlock bootloader and root the phone.

Moreover, what is the difference in super.img regions? I have a possibility to choose the following:

GDRP firmware

01000100,EUEX
01101011,IT-TIM
00000000,IT-TIM

Export firmware

00000000,EXPORT
00011010,TWOP
00011110,AU
00101100,SGOP
00111000,MYOP
00111001,TH
01111011,MX
10000010,HK
10000011,SA
10010110,IL
10011110,BR

I have found such information:

Data privacy is the only difference?
[Redmi Note 8 Questions & Answers] c00LhaNd:
Hey folks.

I try to flash twrp to a Redmi Note 8 (2021).

After waiting one week my bootloader is unlocked.

Developer options and USB debugging are enable.

The phone is installed and detected correctly but every time I want to flash there is a failure that there isnt a partition called recovery. :/

fastboot boot .....img doesn't work to.

(without and with holding the Vol+ button while restarting)

I'm on MIUI 12.5.7 Android 11 (latest update). Any ideas?