General GDPR to EXPORT and reverse

Search This thread

StratOS_HTC

Senior Member
Sep 25, 2007
656
409
Celje
Realme 8 Pro
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 ...
 
Last edited:
  • Like
Reactions: santo.81

SrCDA

Senior Member
Mar 12, 2019
130
120
Realme GT Neo 2
@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.
 

StratOS_HTC

Senior Member
Sep 25, 2007
656
409
Celje
Realme 8 Pro
Won't work.


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.


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
 
Last edited:

StratOS_HTC

Senior Member
Sep 25, 2007
656
409
Celje
Realme 8 Pro
... 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/[email protected]/759948/system_vendor/20713/RMX3081GDPR_11_A.44_2021110921090000/build.prop88B86647B46496A0D8C8054ED25B2A84
8babba8c5a1b36ec0ac94d51825106bd/work/jenkins/workspace/[email protected]/759948/system_vendor/20713/RMX3081GDPR_11_A.44_2021110921090000/super_map.csv8BABBA8C5A1B36EC0AC94D51825106BD
0f1ad197293466548b532db1d900b8fe/work/jenkins/workspace/[email protected]/759948/system_vendor/20713/RMX3081GDPR_11_A.44_2021110921090000/MsmDownloadTool.exeEA6EBBBA5F193129CD9E09ED09F51569MsmDownloadTool_V2.0.67-Rcsm.exe
a00bc5314ae01bf663f24b9720575cdc/work/jenkins/workspace/[email protected]/759948/system_vendor/20713/RMX3081GDPR_11_A.44_2021110921090000/RMX3081GDPR_11_A.44_2021110921090000.ofpnot checked
75db4d94375063a76adec420d84e21c4/work/jenkins/workspace/ofp_fat_release/759953/system_vendor/20711/RMX3081export_11_A.44_2021110921030235/super_map.csv75DB4D94375063A76ADEC420D84E21C4
0f1ad197293466548b532db1d900b8fe/work/jenkins/workspace/ofp_fat_release/759953/system_vendor/20711/RMX3081export_11_A.44_2021110921030235/MsmDownloadTool.exeEA6EBBBA5F193129CD9E09ED09F51569MsmDownloadTool_V2.0.67-Rcsm.exe
64738ed2610959172300a1802bfb2be9/work/jenkins/workspace/ofp_fat_release/759953/system_vendor/20711/RMX3081export_11_A.44_2021110921030235/build.prop64738ED2610959172300A1802BFB2BE9
392a5f8b25368ff1aa63017ec072de73/work/jenkins/workspace/ofp_fat_release/759953/system_vendor/20711/RMX3081export_11_A.44_2021110921030235/RMX3081export_11_A.44_2021110921030235.ofpnot 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.
 
Last edited:

SrCDA

Senior Member
Mar 12, 2019
130
120
Realme GT Neo 2
@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.
 
  • Like
Reactions: StratOS_HTC

StratOS_HTC

Senior Member
Sep 25, 2007
656
409
Celje
Realme 8 Pro
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.

DigesttoSign.png


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
1642524214172.png



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

Attachments

  • Diff.zip
    21.9 KB · Views: 15
Last edited:

SrCDA

Senior Member
Mar 12, 2019
130
120
Realme GT Neo 2
@StratOS_HTC
I recently helped to improve a bit the code of a github project that unzips an OFP, then I unzipped an ofp EXPORT and GDPR in the same update, and I made a program to check the differences, it reads the bytes of each unzipped file and converts to a sha256 and then check if it is the same as another. and this was the result:

summary: basically NV and userdata are different.

==================================== ChainedTableOfDigests_nv00011010.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv00110011.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv00110111.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv00111000.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv00111001.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv01010101.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv01010110.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv01011010.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv01100000.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv01100011.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv01100100.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv01110100.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv01110101.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv10010110.bin (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv10011010.bin (have in Export, NOT have in GDPR) DigestsToSign_nv00011010.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv00110011.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv00110111.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv00111000.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv00111001.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv01010101.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv01010110.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv01011010.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv01100000.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv01100011.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv01100100.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv01110100.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv01110101.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv10010110.bin.mbn (have in Export, NOT have in GDPR) DigestsToSign_nv10011010.bin.mbn (have in Export, NOT have in GDPR) super.1.a0f90c6f.img (have in Export, NOT have in GDPR) super.2.16b9d689.img (have in Export, NOT have in GDPR) super.2.1913e5ba.img (have in Export, NOT have in GDPR) super.2.36bdcb22.img (have in Export, NOT have in GDPR) super.2.3966f314.img (have in Export, NOT have in GDPR) super.2.4027e833.img (have in Export, NOT have in GDPR) super.2.4c32ac99.img (have in Export, NOT have in GDPR) super.2.528bed36.img (have in Export, NOT have in GDPR) super.2.6fd81839.img (have in Export, NOT have in GDPR) super.2.88a45b82.img (have in Export, NOT have in GDPR) super.2.8c6cad19.img (have in Export, NOT have in GDPR) super.2.8f0b3c8e.img (have in Export, NOT have in GDPR) super.2.909e14d8.img (have in Export, NOT have in GDPR) super.2.92ad9583.img (have in Export, NOT have in GDPR) super.2.aad94f7a.img (have in Export, NOT have in GDPR) super.2.c44c6680.img (have in Export, NOT have in GDPR) super.2.fd79bc4d.img (have in Export, NOT have in GDPR) ChainedTableOfDigests_nv01000100.bin (have in GDPR, NOT have in Export) ChainedTableOfDigests_nv01010001.bin (have in GDPR, NOT have in Export) ChainedTableOfDigests_nv10000101.bin (have in GDPR, NOT have in Export) ChainedTableOfDigests_nv10000111.bin (have in GDPR, NOT have in Export) ChainedTableOfDigests_nv10001100.bin (have in GDPR, NOT have in Export) ChainedTableOfDigests_nv10001101.bin (have in GDPR, NOT have in Export) ChainedTableOfDigests_nv10001111.bin (have in GDPR, NOT have in Export) ChainedTableOfDigests_nv10100010.bin (have in GDPR, NOT have in Export) DigestsToSign_nv01000100.bin.mbn (have in GDPR, NOT have in Export) DigestsToSign_nv01010001.bin.mbn (have in GDPR, NOT have in Export) DigestsToSign_nv10000101.bin.mbn (have in GDPR, NOT have in Export) DigestsToSign_nv10000111.bin.mbn (have in GDPR, NOT have in Export) DigestsToSign_nv10001100.bin.mbn (have in GDPR, NOT have in Export) DigestsToSign_nv10001101.bin.mbn (have in GDPR, NOT have in Export) DigestsToSign_nv10001111.bin.mbn (have in GDPR, NOT have in Export) DigestsToSign_nv10100010.bin.mbn (have in GDPR, NOT have in Export) super.1.254549e8.img (have in GDPR, NOT have in Export) super.2.25c7bd95.img (have in GDPR, NOT have in Export) super.2.4c7ff445.img (have in GDPR, NOT have in Export) super.2.689c505c.img (have in GDPR, NOT have in Export) super.2.7694024d.img (have in GDPR, NOT have in Export) super.2.97984148.img (have in GDPR, NOT have in Export) super.2.d7d4e2be.img (have in GDPR, NOT have in Export) super.2.e2378c51.img (have in GDPR, NOT have in Export) super.2.ea46afff.img (have in GDPR, NOT have in Export) ==================================== abl.elf Equal aop.mbn Equal apdp.mbn Equal boot.img Equal BTFM.bin Equal cache.img Equal ChainedTableOfDigests_2169B_ddr4_persist_no_userdata_no.bin Equal ChainedTableOfDigests_2169B_ddr4_persist_yes_userdata_no.bin Equal ChainedTableOfDigests_2169B_ddr5_persist_no_userdata_no.bin Equal ChainedTableOfDigests_2169B_ddr5_persist_yes_userdata_no.bin Equal ChainedTableOfDigests_pre_provision.bin Equal ChainedTableOfDigests_provision_hynix.bin Equal ChainedTableOfDigests_provision_micron.bin Equal ChainedTableOfDigests_provision_samsung.bin Equal ChainedTableOfDigests_provision_toshiba.bin Equal cmnlib.mbn Equal cmnlib64.mbn Equal devcfg.mbn Equal DRIVER.ISO Equal dspso.bin Equal dtbo.img Equal dynamic_nvbk.2169B.bin Equal emmc_fw.bin Equal engineering_cdt.img Equal featenabler.mbn Equal fwupdateConfig.xml Equal gpt_backup0.bin Equal gpt_backup1.bin Equal gpt_backup2.bin Equal gpt_backup3.bin Equal gpt_backup4.bin Equal gpt_backup5.bin Equal gpt_main0.bin Equal gpt_main1.bin Equal gpt_main2.bin Equal gpt_main3.bin Equal gpt_main4.bin Equal gpt_main5.bin Equal hyp.mbn Equal imagefv_ddr4.elf Equal imagefv_ddr5.elf Equal km4.mbn Equal logfs_ufs_8mb.bin Equal metadata.img Equal modemdump.img Equal multi_image.mbn Equal NON-HLOS.bin Equal oppo2169B.bin Equal opporeserve2.img Equal oppo_sec.mbn Equal patch0.xml Equal patch1.xml Equal patch2.xml Equal patch3.xml Equal patch4.xml Equal patch5.xml Equal persist.img Equal prog_firehose_ddr4.elf Equal prog_firehose_ddr4_fwupdate.elf Equal prog_firehose_ddr5.elf Equal prog_firehose_ddr5_fwupdate.elf Equal prog_firehose_lite.elf Equal Projectconfig.xml Equal provision_hynix.xml Equal provision_micron.xml Equal provision_samsung.xml Equal provision_toshiba.xml Equal qupv3fw.elf Equal rawprogram0.xml Equal rawprogram1.xml Equal rawprogram2.xml Equal rawprogram3.xml Equal rawprogram4.xml Equal rawprogram5.xml Equal recovery.img Equal sec_smt.dat Equal Setting.xml Equal splash.img Equal spunvm.bin Equal SS_KLUDG4UHDB-B2D1_1900.fw Equal SS_KLUEG8UHDB-C2D1_1900.fw Equal static_nvbk.2169B.bin Equal tz.mbn Equal uefi_sec.mbn Equal vbmeta.img Equal vbmeta_system.img Equal vbmeta_vendor.img Equal xbl_config_ddr4.elf Equal xbl_config_ddr5.elf Equal xbl_ddr4.elf Equal xbl_ddr5.elf Equal zeros_5sectors.bin Equal ==================================== ChainedTableOfDigests_2169B_ddr4_all.bin Different ChainedTableOfDigests_2169B_ddr4_persist_no_userdata_yes.bin Different ChainedTableOfDigests_2169B_ddr4_persist_yes_userdata_yes.bin Different ChainedTableOfDigests_2169B_ddr5_all.bin Different ChainedTableOfDigests_2169B_ddr5_persist_no_userdata_yes.bin Different ChainedTableOfDigests_2169B_ddr5_persist_yes_userdata_yes.bin Different ChainedTableOfDigests_nv00000000.bin Different DigestsToSign_2169B_ddr4_all.bin.mbn Different DigestsToSign_2169B_ddr4_persist_no_userdata_no.bin.mbn Different DigestsToSign_2169B_ddr4_persist_no_userdata_yes.bin.mbn Different DigestsToSign_2169B_ddr4_persist_yes_userdata_no.bin.mbn Different DigestsToSign_2169B_ddr4_persist_yes_userdata_yes.bin.mbn Different DigestsToSign_2169B_ddr5_all.bin.mbn Different DigestsToSign_2169B_ddr5_persist_no_userdata_no.bin.mbn Different DigestsToSign_2169B_ddr5_persist_no_userdata_yes.bin.mbn Different DigestsToSign_2169B_ddr5_persist_yes_userdata_no.bin.mbn Different DigestsToSign_2169B_ddr5_persist_yes_userdata_yes.bin.mbn Different DigestsToSign_nv00000000.bin.mbn Different DigestsToSign_pre_provision.bin.mbn Different DigestsToSign_provision_hynix.bin.mbn Different DigestsToSign_provision_micron.bin.mbn Different DigestsToSign_provision_samsung.bin.mbn Different DigestsToSign_provision_toshiba.bin.mbn Different ProFile.xml Different super.0.48453346.img Different userdata.img Different
 

StratOS_HTC

Senior Member
Sep 25, 2007
656
409
Celje
Realme 8 Pro
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
 

StratOS_HTC

Senior Member
Sep 25, 2007
656
409
Celje
Realme 8 Pro
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_idnv_textsuper_0_pathsuper_1_pathsuper_2_path
1000100EUEXsuper.0.35e5269c.imgsuper.1.de62627a.imgsuper.2.3e674d94.img
1010001TRsuper.0.35e5269c.imgsuper.1.de62627a.imgsuper.2.bd4abb42.img
10000101EU-NONEEAsuper.0.35e5269c.imgsuper.1.de62627a.imgsuper.2.358c76e4.img
10000111UAsuper.0.35e5269c.imgsuper.1.de62627a.imgsuper.2.0d48ab09.img
10001010GBsuper.0.35e5269c.imgsuper.1.de62627a.imgsuper.2.745e1476.img
00000000GBsuper.0.35e5269c.imgsuper.1.de62627a.imgsuper.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 :

Code:
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.
 
Last edited:

SrCDA

Senior Member
Mar 12, 2019
130
120
Realme GT Neo 2
HI.
There is no official release of the deep test for GDPR [EU] RMX3081.
on EXPORT https://forum.xda-developers.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 ?
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
 

Attachments

  • DeepTest.apk
    4.3 MB · Views: 52

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    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 ...
    1
    @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.
    1
    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
    the projectid is 2169B
    1
    Thank you.
    It's the same.Same error still exists on mine GDPR [EU] rom .44.

    The files are exactly the same.