Dont worry about the .amf format just cook the rom like you normaly do, everyone is confused with this new acer flashing structure lol, you dont need to use this new acer_euu.exe to flash a rom with the new 3.003b oem drivers, unless of course your flashing the original 3.003b.00.EU rom =]
Yes, Rafy, but the problem is this:
ROM 3.003b.00_EN_03.03.08 (EU version) when flashing is attempted using the stock Ace ACER_EUU.exe, just returns an
"SKU_incompatible" error on existing ROM's like 2.003d (obviously a tricky-dicky language issue)
Using the modified ACER_EUU.exe version 2 from this forum throws up:
[Error Code=AcerResetApplicationRunProcessByPhoneFail]
when in download mode (flash red, screen black)
And using the modified ACER_EUU.exe version 1 from this forum just throws up the errors on all the *.bin, hex, mbn files etc missing from the new Acer ROM structure, which now just has a humungous *.amf file that the modified ACER_EUU.exe version 1 cannot read
So, what's the answer please (apart from a custom-cooked ROM) ?
NEXT DAY EDIT:
"SKU incompatible" Problem Resolved
Unbelievably simple - no need for modified ACER_EUU.exe, just a simple registry edit:
HKLM\ControlPanel\ACER\SystemInfo\Software (ROM 2.003d.01_EN_02_02.03)
relevant keys
ExtROMVer
leave as is
language
leave as is
Major
leave as is
Minor
edit 2 to 1
Then flash ROM 3.003b.00_EN_3.003.01 normally from the official Acer exe file through async
Editing the registry key "Minor" from 2 to 1 removes the SKU_incompatible error - that is, the minor ROM version from 2.003d is 02, but for 3.003b is 01. It seems that editing this Minor number to match the Minor number of the ROM to be flashed is needed to avoid the
SKU_incompatible error