Alcatel open market 4s

[Iain_S]

Just to let you guys know the FFU is now available for the NA open market device.

 

[RumoredNow]

Gonna try this soon on my T-Mo Idol 4S to unbrand it. Should work since you can flash the T-Mo on an unlocked with no problems...

 

[Iain_S]

I had the open market and flashed the tmobile because the FFU wasn't available, seems I cant flash back to open market now, gives error.

 

[RumoredNow]

Drats

 

[fatclue_98]

Does the Open Market come without the VR apps? If so, I'll have to do some reg edits to get that firmware.

 

[PFSP]

Does the Open Market come without the VR apps? If so, I'll have to do some reg edits to get that firmware.

The open market phone includes the VR apps.

 

[fatclue_98]

The open market phone includes the VR apps.

To quote @RumoredNow - Drats

 

[nate0]

I failed to flash the open market on my open market idol 4s not sure why yet though.. I am on feature2 build.

 

[Iain_S]

I failed to flash the open market on my open market idol 4s not sure why yet though.. I am on feature2 build.

yup I haven't been able to flash back to the open market FFU after installing the tmobile FFU a couple months ago.

 

[nate0]

yup I haven't been able to flash back to the open market FFU after installing the tmobile FFU a couple months ago.

What error do you see in the error log? Seems in the log the WDRT app is unable to make a complete handshake with the device. Was thinking it had something to do with reset protection while on the Feature2 build. Will look into it later tomorrow again.

 

[Iain_S]

What error do you see in the error log? Seems in the log the WDRT app is unable to make a complete handshake with the device. Was thinking it had something to do with reset protection while on the Feature2 build. Will look into it later tomorrow again.

let us know how you make out, would like to get mine back to original FFU to put it up for sale. Thanks

 

[nate0]

It is the FFU file. There is something, an incorrect something or lack of something packaged into it that is not allowing the handshake to commence. The T-Mobile FFU still wants to flash to my Unlocked Idol with no issues. My guess is that we need to get this info to Alcatel and especially Microsoft so that we can look for a newer download with the updated FFU. I am not certain what is not jiving between that FFU and the devices though. I bet anyone trying to flash the open market FFU to any Idol 4s W10M phone, it fails with the same general error. I am not sure how or who to get this info to. I called Alcatel, but they said they do not even support the WDRT.

UPDATE: Anyone update to the CU build then try flashing?

 

[anon(10197358)]

@Nate W

No idea, I haven't that device. What WDRT .log files say ?

I called Alcatel, but they said they do not even support the WDRT.

Lol, Alcatel, they are champs :evil:

 

[nate0]

Not much in the log, but this over and over...
4/26/2017 9:51:00 AM Info Initialized flashing platform logging at C:\Users\natha\AppData\Local\Temp\WindowsDeviceRecoveryTool12256.log
4/26/2017 9:51:00 AM Info [IN 10544] WinUsbDevMsg::Initialize

4/26/2017 9:51:00 AM Info [IN 10544] CThread<class WinUsbDevMsg>::Create

4/26/2017 9:51:00 AM Info m_hThread (0xc2c)
4/26/2017 9:51:00 AM Info [OUT 10544] CThread<class WinUsbDevMsg>::Create

4/26/2017 9:51:00 AM Info [IN 9712] WinUsbDevMsg::MessageLoop

4/26/2017 9:51:00 AM Info [IN 9712] WinUsbDevMsg::CreateMessageWindow

4/26/2017 9:51:00 AM Info WinUsbDevMsg MSG WINDOW HANDLE 1303a6

4/26/2017 9:51:00 AM Info [OUT 9712] WinUsbDevMsg::CreateMessageWindow

4/26/2017 9:51:00 AM Info [OUT 10544] WinUsbDevMsg::Initialize

4/26/2017 9:51:00 AM Info [IN 10544] WinUsbDevMsg::SetWinUsbDevMsgClient

4/26/2017 9:51:00 AM Info [OUT 10544] WinUsbDevMsg::SetWinUsbDevMsgClient

4/26/2017 9:51:00 AM Info [IN 10544] WinUsbDevMsg::StartWaitingNotifications

4/26/2017 9:51:00 AM Info [IN 10544] WinUsbDevMsg::RegisterNotification

4/26/2017 9:51:00 AM Info GUID {88bae032-5a81-49f0-bc3d-a4ff138216d6}

4/26/2017 9:51:00 AM Info [OUT 10544] WinUsbDevMsg::RegisterNotification

4/26/2017 9:51:00 AM Info [IN 10544] WinUsbDevMsg::RegisterNotification

4/26/2017 9:51:00 AM Info GUID {ec4e3c4d-b0e8-4d97-a85f-d1631a54ea03}

4/26/2017 9:51:00 AM Info [OUT 10544] WinUsbDevMsg::RegisterNotification

4/26/2017 9:51:00 AM Info [IN 10544] WinUsbDevMsg::RegisterNotification

4/26/2017 9:51:00 AM Info GUID {08324f9c-b621-435c-859b-ae4652481b7c}

 

[nate0]

I cannot remember exactly how the thor2 command should be to send an ffu only to a device in flash mode...otherwise I would see if that log is the same...

 

[anon(10197358)]

@Nate W

The thor2 command should be

thor2.exe -mode uefiflash -ffufile FullFlashUpdate.ffu

 

[Alex Alderson]

To give some context I bought the Idol from Amazon and having encountered camera issues on the Fast ring flashed the T-Mobile ffu with WDRT.

I tried flashing with thor2 on two different laptops without success. Having tried with the Idol both in flash mode and booted thor2 returns the same error as the attached image.



I also tried using WPID too which gives more detail on the error. The device is listed as ALCATEL.8996.IDOL4S.1.0 while the ffu image has ALCATEL.8996.IDOL4S.NA.



I changed the value data in HKLM/SYSTEM/Platform/DeviceTargetingInfo/PhoneModelName to IDOL 4S with Windows 10 NA but the WPID error remains.

What do you reckon, has the T-Mobile ffu changed the device ID from ALCATEL.8996.IDOL4S.NA to ALCATEL.8996.IDOL4S.1.0?

Could anyone with the unlocked variant check this by resetting their device with the Open Market ffu and WPID?

 

[Iain_S]

from what you have tried there it does seem if you flashed the open market 4s with the tmobile FFU it has actually changed the device ID, which sucks balls. I hope that is not the case.

 

[nate0]

I also tried using WPID too which gives more detail on the error. The device is listed as ALCATEL.8996.IDOL4S.1.0 while the ffu image has ALCATEL.8996.IDOL4S.NA.

The platform id is not pulled from the registry. Thanks for this find. I can take a look later tonight and add more info too.

 

[nate0]

from what you have tried there it does seem if you flashed the open market 4s with the tmobile FFU it has actually changed the device ID, which sucks balls. I hope that is not the case.

Not true. I had the open market and could not flash either. Seems all the phones are provisioned the same. The open market ffu was provisioned different from most of the phones or maybe all. I could be wrong but I flashed the T-Mobile rom because I wanted off the fast ring. That was the only way I could do it. I think I know how to change that ID though to flash the open market rom.