I found the exact page on Needrom and I am currently downloading the "Update V239" ROM as you recommended. I will let you know as soon as the download finishes. Thank you so much, brother!
The V239 ROM .pac firmware file has been completely downloaded to my computer, brother! I have also extracted the zip package.Now, I am ready to load the .pac file into the UpgradeDownload tool. I will uncheck the "Check Product ID" / "Check Platform" option in the Settings menu to bypass the region mismatch block. Then, I will load your custom signed boot and vbmeta files, keep USERDATA and CACHE checked for formatting, and uncheck all other system partitions.Is this the correct order you want me to follow, or should I wait for your final confirmation? Standing by for your instructions!
Hey Mouhamed,I followed the exact plan. Since the tool didn't allow me to change the file paths directly from the UI, I used a trick: I opened the Windows %temp% directory where the tool extracts the .pac firmware files.I deleted the stock boot.img and vbmeta-sign.img from the Temp folder, and replaced them with your signed custom files using the exact same names. After that, I returned to the UpgradeDownload tool and hit the Start button.The tool captured the device on COM port successfully, but after a few seconds, it threw this error: "IDownload Fail. Pls check the mem".It seems the tool is strictly checking the Checksum / CRC hash of the files in the Temp directory, matching them against the official firmware manifest, and blocking the operation because our custom file sizes/hashes don't match the original ones. Also, the verification options in the "Options" tab are completely greyed out, so I cannot uncheck them.Since my device is completely stuck in BROM mode right now and won't even boot into Fastbootd screen, how can we bypass this factory CRC/Checksum check on UpgradeDownload? Is there a modified configuration file or another tool we can use to force flash your signed files?
hmmmm flash the stock rom, the original one, once it done, boot the phone up if it boot up all the way to the setup wizard, then you can reboot to fastbootd, then use fastboot commands to flash boot and vbmeta, here is an example, fastboot flash boot boot.img
(Replace boot.img with the actual file name or path) fastboot flash vbmeta vbmeta.img
(Replace vbmeta.img with your actual file name or path then once the flashing is done, immediately go back to recovery (don't reboot to recovery just go back to it from the fastbootd menu) and then go to wipe user data do yes and do format for the cache too then you can reboot and please if it worked tell me