The Windows 10 April 2018 update has arrived! Get the new Dell XPS 15, starting at $999.99
02-14-2018 12:30 AM
321 ... 34567 ...
tools
  1. fishsniffer2's Avatar
    I jus did and tweeted Alcatel for a fix!
    06-09-2017 02:13 PM
  2. nate0's Avatar
    Edit : Wrong hopeful. Idol 4S T-Mobile's .ffu file also. Probably also for all other .ffu files of all other OEMs : http://i.imgur.com/xrZ8Tub.png
    I see an ffu now for the IDOL4s available again. But not for the T-Mobile model
    fatclue_98 and anon(10197358) like this.
    06-09-2017 02:18 PM
  3. anon(10197358)'s Avatar
    @Nate W

    Just

    Hi, Dylan! Thank you for contacting Alcatel Support. What is the issue that you are experiencing with your device?
    I answered to their DM. Now, I wait of their next reply.

    Yep, it seems that Microsoft has fixed the issue with the Azure repository servers.
    nate0 likes this.
    06-09-2017 04:02 PM
  4. nate0's Avatar
    @Nate W

    Just

    I answered to their DM. Now, I wait of their next reply.

    Yep, it seems that Microsoft has fixed the issue with the Azure repository servers.
    Do you actually own an IDOL 4s? Appreciate everyones support to bring this issue to light.
    anon(10197358) likes this.
    06-09-2017 04:23 PM
  5. anon(10197358)'s Avatar
    @Nate W

    Nope, I've a Lumia 650.
    nate0 likes this.
    06-09-2017 04:25 PM
  6. Iain_S's Avatar
    maybe this means ms are in the process of doing something to fix the program and or files that are available on wdrt.
    06-09-2017 06:14 PM
  7. Iain_S's Avatar
    just seeing now if the open market one now flashes to the device without errors.
    06-09-2017 06:18 PM
  8. Luke Rossini's Avatar
    I sent my Idol in for repair with an RMA to have them "force" an open market flash. I received the phone back today and it immediately booted with the T-Mobile logo. I confirmed the device still had the T-Mobile firmware and was disappointed.

    Here is the best part.
    The work notes say, "Your phone has been repaired" and "Work Done". Both of which insinuate something was done to the device. By the looks of it all they did was use the Reset My Phone option under settings. I called and they could not help me or give me any explanation of what "work" was done. I attempted to argue my case and after some time the employee started to "understand". Their explanation of why it still has the T-Mobile firmware was that I was not clear on the issue/request. She said this even though she can't access my original RMA to see what I typed or requested. She then said I can start a new RMA request and when they get the device it will be reset to factory settings..... I explained this is why I just sent my idol in and it came back "unrepaired". I asked if she could create an RMA for me or work with me to guarantee this work will be completed on the next RMA. She claimed she can't start a RMA for me but, recommended I put in the "Please explain in detail the problem" field, of the RMA request page, something like "Install Open Market Firmware on device". Then if the device matches the T-Mobile version they will load that firmware and if it matches an unlocked version they will install that firmware. Other than that, she could not directly help me.

    I'm curious if the ID that is changed when you install the T-Mobile firmware also changes the ID they reference. I would hope they can reference the Imei number to pull this information though.

    A few personal takeaways

    1. Alcatel Support can't access the FineTechWin RMA workflow application/notes ( Cannot tell me what work/notes are on my RMA )
    2. They don't know much about the Idol 4s Windows version ( She thought I had a T-Mobile branded device that was sim unlocked by a T-Mobile provided code )
    3. They have no idea about the firmware/WDRT issue ( She could find no information on this PLAT ID/ Firmware issue being addressed )
    4. They think since I can put in a ATT sim without error/warning the device is fine and working ( She asked what the error I get when entering an ATT sim says )


    Let me know if you have any questions or need more details
    anon(10197358) and nate0 like this.
    06-09-2017 06:23 PM
  9. Iain_S's Avatar
    nope still fails.
    06-09-2017 06:24 PM
  10. anon(10197358)'s Avatar
    @Iain_S

    It seems to me that a issue like that from api.swrepository.com and sr.azureedge.net Azure repository servers had never happened before. However, it was simply a issue, not a maintenance to prepare a fix to the problem of the Idol 4S Open Market's .ffu file.

    Edit : Idol 4S Open Market's .ffu file is the same that before, http://i.imgur.com/sksIy8G.png.

    * * * * * * *

    @Luke Rossini

    Thx for your experience. Alcatel's support is really a joke. I ask me increasingly if, one day, Idol 4S users will get really a fix for that.
    Last edited by DylanCochard; 06-09-2017 at 06:49 PM.
    nate0 and Mr Mendelli like this.
    06-09-2017 06:30 PM
  11. RumoredNow's Avatar
    Three of us. -_-
    Four of us too smart for Twitting.
    fatclue_98, mark233 and editguy like this.
    06-09-2017 06:42 PM
  12. nate0's Avatar
    @Luke Rossini
    The PLAT ID will not change if you flash the IDOL 4s T-Mobile FFU. It really is quirky. All the phones match the FFU's contained PLAT ID.

    @DylanCochard
    Ya it was not changed. Like you said some issue happened...I downloaded it and ran an integrity check myself from thor2 to be sure...
    What is making the Open Market FFU flashing check for the plat id ALCATEL.8996.IDOL4S.NA instead of ALCATEL.8996.IDOL4S? Is it how it was signed or something else?
    anon(10197358) likes this.
    06-09-2017 06:56 PM
  13. Iain_S's Avatar
    capture-error-idol-4s.jpg

    this is it in a nutshell, when using wdrt it runs four checks before being able to flash the ffu, the important one being

    To validate that the image supports the current device platform before flashing, the application performs the following tasks:
    It retrieves the DevicePlatformID string from the device platform package in the image that is being flashed. For more information about this string, see Set device platform information.

    If the string has the format http://Manufacturer.Family*.Product Name.Version and all four values in the string match the corresponding Manufacturer, Family, Product Name, and Version SMBIOS values on the device, the platform validation succeeds and the flashing operation continues.
    If the string has the format http://Manufacturer.Family*.Product Name and all three values in the string match the corresponding Manufacturer, Family, and Product Name SMBIOS values on the device, the platform validation succeeds and the flashing operation continues.

    Otherwise, the platform validation fails and the image is not flashed to the device.

    non-retail image, OEMs can disable the device platform validation for flashing by adding the DISABLE_FFU_PLAT_ID_CHECK feature to the OEMInput file that is used to generate the image.
    paschott likes this.
    06-09-2017 07:30 PM
  14. Iain_S's Avatar
    So this is squarely on the head of ALCATEL because they make the FFU from there OEMInput file which sets the name for the PLAT_ID_CHECK from within WDRT
    nate0 likes this.
    06-09-2017 07:32 PM
  15. nate0's Avatar
    @Iain_S
    Are you flashing manually from cmd.exe on that snippet?

    Also do you know where it is retrieving the DevicePlatformID string from the device platform package?
    06-09-2017 08:22 PM
  16. anon(10197358)'s Avatar
    06-09-2017 08:38 PM
  17. Iain_S's Avatar
    @Iain_S
    Are you flashing manually from cmd.exe on that snippet?

    Also do you know where it is retrieving the DevicePlatformID string from the device platform package?
    I used ffutool to test to what the error actually was cause wdrt is pretty vague. The string for the plat id is inserted into the ffu by alcatels oemtool when they create the ffu.
    nate0 likes this.
    06-10-2017 03:59 PM
  18. Iain_S's Avatar
    So the Platform id information is written to the SMBIOS on the device.

    On each device platform, OEMs must ensure that the following values in the SMBIOS system information structure are set:
    PhoneManufacturer
    Family
    Product Name
    Version

    is there a way to edit the SMBIOS information once its already on the device?
    nate0 likes this.
    06-10-2017 04:57 PM
  19. nate0's Avatar
    I used ffutool to test to what the error actually was cause wdrt is pretty vague. The string for the plat id is inserted into the ffu by alcatels oemtool when they create the ffu.
    I am without my IDOL4s to be able to check around with it is why I ask. The FFU must use something flagged from the OEMinput.xml file other than the smbios.cfg inside it to validate against the device. Because that file matches the Open market and the T-Mobile model. The T-Mobile FFU also has the same smbios.cfg file PLAT ID. Just wondering if there would be a way to override the plat id using a different flashing tool, or some other method. There is option to skip plat ID check when using thor2 but the WDRT tool uses a specific DLL file for Alcatel when flashing. The idol 4s does not support a specific boot manager or flash app within the WDRT like we know for the Lumia's. Are there any other tools that can flash this ffu to the IDOL 4s? Have you tried Image Designer or something else?
    06-10-2017 05:20 PM
  20. Iain_S's Avatar
    I'm looking into alternatives right now to see if there is anyway to do this and bypass the id check.
    06-10-2017 06:52 PM
  21. Iain_S's Avatar
    whats the commond line and flags for over riding platid when using thor2? or if you have the xml file I can edit and do an emergency program using the xml and ffu?
    nate0 likes this.
    06-10-2017 07:44 PM
  22. nate0's Avatar
    So the Platform id information is written to the SMBIOS on the device.

    On each device platform, OEMs must ensure that the following values in the SMBIOS system information structure are set:
    PhoneManufacturer
    Family
    Product Name
    Version

    is there a way to edit the SMBIOS information once its already on the device?
    Only way I could see doing that would be with a pre-signed cab file with the smbios.cfg matching what that ffu needs. But when doing that you always want to have a way to revert back to stock. I have found zero files so far containing an smbios.cfg file.
    06-10-2017 10:03 PM
  23. nate0's Avatar
    whats the commond line and flags for over riding platid when using thor2? or if you have the xml file I can edit and do an emergency program using the xml and ffu?
    The idol 4s does not rely on the thor2 command. It used the WDRT app directly (WindowsDeviceRecoveryTool.exe) and sets of .dll files like AnalogAdaptation.dll AlcatelAdaptation.dll Model.dll. I have been looking again at the WDRT trace logs and building more of a understanding of what is happening.
    There is a dll file called LogicCommon.dll. It along with the AnalogAdaptation.dll look like they are able to see and read the smbios.cfg file to verify the Device ID embedded there and compare it to what is expected on the FFU.

    If thor2 would have worked it would include the skip id check flag to bypass that feature.
    -skip_id_check Secure FFU flashing. Skips Platform ID check between the device and FFU file.

    Unfortunately other security measures are usually in place if that flag is used. Was thinking maybe there is another tool available since thor2 is not used anyway that might be considered. But we could be doing that at the risk of the device, since there appears to be no Emergency files out there and anything could happen since WDRT is only tool really designed for the IDOL4s.
    anon(10197358) likes this.
    06-10-2017 11:46 PM
  24. Iain_S's Avatar
    The idol 4s does not rely on the thor2 command. It used the WDRT app directly (WindowsDeviceRecoveryTool.exe) and sets of .dll files like AnalogAdaptation.dll AlcatelAdaptation.dll Model.dll. I have been looking again at the WDRT trace logs and building more of a understanding of what is happening.
    There is a dll file called LogicCommon.dll. It along with the AnalogAdaptation.dll look like they are able to see and read the smbios.cfg file to verify the Device ID embedded there and compare it to what is expected on the FFU.

    If thor2 would have worked it would include the skip id check flag to bypass that feature.
    -skip_id_check Secure FFU flashing. Skips Platform ID check between the device and FFU file.

    Unfortunately other security measures are usually in place if that flag is used. Was thinking maybe there is another tool available since thor2 is not used anyway that might be considered. But we could be doing that at the risk of the device, since there appears to be no Emergency files out there and anything could happen since WDRT is only tool really designed for the IDOL4s.
    I can flash the tmobile rom onto my idol4s independently of wdrt using the ffutool, I don't think that tool uses anything from wdrt. and is done from the command prompt.
    06-11-2017 01:31 PM
  25. Iain_S's Avatar
    so the flag in thor2 would be -skip_id_check Secure FFU Flashing or just -skip_id_check?
    06-11-2017 01:33 PM
321 ... 34567 ...

Similar Threads

  1. Suggest an open source/free photoviewer
    By Raviraj Halarnekar in forum Windows 10
    Replies: 9
    Last Post: 07-07-2017, 10:21 AM
  2. Would you still buy a Alcatel IDOL 4S?
    By kuau in forum Alcatel Idol 4S
    Replies: 44
    Last Post: 04-25-2017, 07:24 PM
  3. Continuum on the Alcatel Idol 4S
    By Ventus221 in forum Alcatel Idol 4S
    Replies: 6
    Last Post: 04-24-2017, 08:31 PM
  4. Best Open source/ freeware utilities for Windows 10
    By Raviraj Halarnekar in forum Windows 10
    Replies: 1
    Last Post: 04-19-2017, 01:07 AM
  5. Replies: 2
    Last Post: 04-17-2017, 12:19 PM
LINK TO POST COPIED TO CLIPBOARD