Database Develop

[Q] Flashing Nokia Lumia 820 RM-824 (AT&T) to RM-824 (Global)

Hi everyone,
My device:
Nokia RM-824 (AT&T)
Product Code 059M0F3 RM-824 NDT AMERICA US ATT
Want to flash:
RM-824 (Global)
Product Code 059R4Q6 RM-824 lta lta1 GLOBAL Swap
Tools Installed on PC:
Nokia Care Suite for Store version: 5.0.0 (5.4.119)
Product Support Tool for Store 5 (Ver. 5.4.119.1432)
Once flashing shows an error:
0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
Click to expand...
Click to collapse
I have found this error on majority of posts here and there but no fix for that problem.
There was one solution for that by modifing DLLs of Nokia Care Suite to bypass this checking ... but it doesnt work anymore
Anybody found solution for that ?
TO MOTIVATE PEOPLE HERE I WILL DONATE $$ FOR WORKING SOLUTION

why do you want to flash other region's ROM on your device?

etios123 said:
why do you want to flash other region's ROM on your device?
Click to expand...
Click to collapse
thanks for reply
I need to ADD more languages

genevaq said:
thanks for reply
I need to ADD more languages
Click to expand...
Click to collapse
No need of flashing ROM's for that, just go to settings -> language -> Add languages

etios123 said:
No need of flashing ROM's for that, just go to settings -> language -> Add languages
Click to expand...
Click to collapse
Thanks, this just add regional settings. I want to change the whole OS menu to have in different langauge (german).
On first start up you can pick language. Thats why i want to flash the ROM to Global.

genevaq said:
Thanks, this just add regional settings. I want to change the whole OS menu to have in different langauge (german).
On first start up you can pick language. Thats why i want to flash the ROM to Global.
Click to expand...
Click to collapse
Ok, i got it, hopefully someone here will help in solving the errors while flashing the Global ROM.

@genevaq
Hi,
Since you got the error FFU, you can not flash your NL820. The NAM (especially AT&T) versions are very hard to flash, and in most cases impossible.

I flahied with ATF
here is result any solution
Nokia Phone Info Mode Initiated...
Please wait upto 15 Seconds for SW Reset
IMEI: 355941050749569
Version: 1.1.1.2
Product Code: 059R7P8
Module Code: 0205162
Basic Tranceiver Code: 059M0F7
Continuing Previous Boot...
Please wait upto 30 Seconds for Boot Re-entry
Boot Flash Mode Successful...
Buffers Flushed OK...
Phone Info Query Start...
Blocks Returned: 0x07 Blocks
Block ID 0x01 : 00241000
Block ID 0x02 : 00240000
Block ID 0x03 : 00E90000
Block ID 0x05 : Nokia.MSM8960.P5174.3.2.1
Block ID 0x0D : 0001
Block ID 0x0F : 0301010100000101FF
Block ID 0x10 : 0100030000
Checking SD Card Size...
Card Size: 0x00000000
Checking Platform Security Status...
Platform Secure Boot Status: Active
Secure FFU EFUSE Status: Active
Debug Status: Active
RDC Status: Not Active
Authentication Status: Not Active
UEFI Secure Boot Status: Active
Checking Secure FFU Mode...
Secure FFU Mode : SYNC + ASYNC
Query Flash App Information...
Flash App Information: 020109011000
UEFI App: FLASH APP
Flash App Protocol Version: 1.9
Flash App Implementation Version: 1.16
Query ROOT KEY HASH...
ROOT_KEY_HASH: DB73418E5840941CE7BD35949085B8F74628D511F19285A092ED3B600A64CC29
Sending Image Signatures...
ERROR: Flash Signature Block REJECTED! (0x13040000000000000000)
This Flash File is NOT COMPATIBLE with this Phone.
ERROR: Flashing Failed!

regmwesiga said:
I flahied with ATF
here is result any solution
Nokia Phone Info Mode Initiated...
Please wait upto 15 Seconds for SW Reset
IMEI: 355941050749569
Version: 1.1.1.2
Product Code: 059R7P8
Module Code: 0205162
Basic Tranceiver Code: 059M0F7
Continuing Previous Boot...
Please wait upto 30 Seconds for Boot Re-entry
Boot Flash Mode Successful...
Buffers Flushed OK...
Phone Info Query Start...
Blocks Returned: 0x07 Blocks
Block ID 0x01 : 00241000
Block ID 0x02 : 00240000
Block ID 0x03 : 00E90000
Block ID 0x05 : Nokia.MSM8960.P5174.3.2.1
Block ID 0x0D : 0001
Block ID 0x0F : 0301010100000101FF
Block ID 0x10 : 0100030000
Checking SD Card Size...
Card Size: 0x00000000
Checking Platform Security Status...
Platform Secure Boot Status: Active
Secure FFU EFUSE Status: Active
Debug Status: Active
RDC Status: Not Active
Authentication Status: Not Active
UEFI Secure Boot Status: Active
Checking Secure FFU Mode...
Secure FFU Mode : SYNC + ASYNC
Query Flash App Information...
Flash App Information: 020109011000
UEFI App: FLASH APP
Flash App Protocol Version: 1.9
Flash App Implementation Version: 1.16
Query ROOT KEY HASH...
ROOT_KEY_HASH: DB73418E5840941CE7BD35949085B8F74628D511F19285A092ED3B600A64CC29
Sending Image Signatures...
ERROR: Flash Signature Block REJECTED! (0x13040000000000000000)
This Flash File is NOT COMPATIBLE with this Phone.
ERROR: Flashing Failed!
Click to expand...
Click to collapse
I'm having the same problem. If someone here know how to fix it...

[Q] Moto x blank flash complete but not enter fastboot

C:\Android>qflash.exe -com10 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloader_si
ngleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM10
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
EOF_REC
Sleeping for 3s
-----------------------------------------------------
RAM DOWNLOADER INFORMATION
-----------------------------------------------------
cmd : 0x2
description : QCOM fast download protocol targ
version_number : 0x7
compatible_version: 0x2
max_block_size : 0x400
flash_base_address: 0x0
flash_id_len : 0x4
flash id : eMMC
window_size : 0x1e
number_of_sectors : 0x80
-----------------------------------------------------
sdl_send_security_mode: secutiry mode 0x0
Flashing MSM8960_bootloader_singleimage.bin 1969664 bytes into device
Keeping the first packet (1024 bytes) as hostage
Will release it if all is flashed well
100
Hostage released!
done
@ but same problem here. not come to fastboot and mobile like dead.
please help me. @

Not sure what exactly you are attempting to flash? Or how?
Can you provide more details on what happened to your device and what you are now trying to do?
Thanks!
Also note, questions go in the Q&A section, not general. This thread will be moved to Q&A for you. ?

Ah! This is what you are trying...
http://forum.xda-developers.com/showthread.php?t=2629057
Unfortunately, if the method is followed exactly in that thread, and doesn't work.... There isn't much else you can do. Going to a repair shop might be the only way.

Darth said:
Not sure what exactly you are attempting to flash? Or how?
Can you provide more details on what happened to your device and what you are now trying to do?
Thanks!
Also note, questions go in the Q&A section, not general. This thread will be moved to Q&A for you.
Click to expand...
Click to collapse
My moto x xt1052 older android version 4.4.4, then i am trying to flash (ATT_XT1058_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml) with RSDLite but (gpt.bin) file not to be enter. then i am unlock bootloder (Device is UNLOCKED. Status Code: 3 )
then i am trying to flash with (XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml) then gpt.bin and some file enter but others file not to be enter then not come to fastboot and mobile like dead. then i am completely success with blank flash but same problem here. not come to fastboot and mobile like dead.

You've either downgraded and bricked, or attempted to downgrade and bricked. Ask for help in the thread I linked. But if it doesn't work, your device is likely dead. You'll need a repair shop to look at it.

What could you solve it?

Phone Platform ID Modification

Looks like the WPRT has corrupted my Platform ID. It is reported by Thor2 as:
Nokia MSM8974..2..2.
When I check the FFU file of the recovery download:
Nokia.MSM8974.P6039
So, 2 questions:
1) Does anyone know how to update/modify the phones Platform ID?
2) Does anyone know where a Lumia Icon RM-927 hex file can be found?

dumper_gumper said:
Looks like the WPRT has corrupted my Platform ID. It is reported by Thor2 as:
Nokia MSM8974..2..2.
When I check the FFU file of the recovery download:
Nokia.MSM8974.P6039
So, 2 questions:
1) Does anyone know how to update/modify the phones Platform ID?
2) Does anyone know where a Lumia Icon RM-927 hex file can be found?
Click to expand...
Click to collapse
Hi, I have the exact problem did you manage to solve it?????
My phone is Lumia 1520 RM-940, and I have tried everything humanly possible to fix it but i couldn't.
The phone is bricked and no rom will ever flash on it because of the wrong platform ID error
guys if anyone has any idea how to either skip the id check or change a platform id of the rom to match the corrupted one or any other solution. then please help.
Thanks in advance

oke lol

dumper_gumper said:
Looks like the WPRT has corrupted my Platform ID. It is reported by Thor2 as:
Nokia MSM8974..2..2.
When I check the FFU file of the recovery download:
Nokia.MSM8974.P6039
So, 2 questions:
1) Does anyone know how to update/modify the phones Platform ID?
2) Does anyone know where a Lumia Icon RM-927 hex file can be found?
Click to expand...
Click to collapse
ekhader said:
Hi, I have the exact problem did you manage to solve it?????
My phone is Lumia 1520 RM-940, and I have tried everything humanly possible to fix it but i couldn't.
The phone is bricked and no rom will ever flash on it because of the wrong platform ID error
Click to expand...
Click to collapse
Are you using the updated tool and what mode is your phone in? These were downloaded directly from the WPRT which has been rebranded and updated to Windows Device Recovery Tool. If you are stuck with Emergency Download mode QHUSB_DLOAD/QHUSB_BULK then use Emergency payload cmd
Code:
thor2 -mode emergency -hexfile MPRG8974_fh.ede -edfile RM927_fh.edp
or
Code:
thor2 -mode emergency -hexfile MPRG8974_fh.ede -edfile RM940_fh.edp
Or just try using the updated tool if you haven't already

tonbonz said:
Are you using the updated tool and what mode is your phone in? These were downloaded directly from the WPRT which has been rebranded and updated to Windows Device Recovery Tool. If you are stuck with Emergency Download mode QHUSB_DLOAD/QHUSB_BULK then use Emergency payload cmd
Code:
thor2 -mode emergency -hexfile MPRG8974_fh.ede -edfile RM927_fh.edp
or
Code:
thor2 -mode emergency -hexfile MPRG8974_fh.ede -edfile RM940_fh.edp
Or just try using the updated tool if you haven't already
Click to expand...
Click to collapse
Hi,
Thanks for replying,
Yes I am using the latest tool and the device is in flash mode so its not stuck in the emergency mode.
the problem is that the recovery tool changed the device Platform ID from : Nokia.MSM8974.P6081_ATT.2.2 -----> Nokia.MSM8974..2.2
so after this change everytime i try to flash it gives the error : Platform Id Check failed, even though i am using the official and correct version of the firmware.
I have tried so many things to bypass this check but they all failed.
I wonder if the emergency flashing of the device was the cause of changing the Platform ID, I am not sure how the tool even managed to change the device Platform ID, and thinking is there anyway i can return the original platform ID ???
and by the way the attached files you posted for RM-940 they are corrupted or something winRar couldn't extract them.
-Thanks

ekhader said:
Hi,
Thanks for replying,
Yes I am using the latest tool and the device is in flash mode so its not stuck in the emergency mode.
the problem is that the recovery tool changed the device Platform ID from : Nokia.MSM8974.P6081_ATT.2.2 -----> Nokia.MSM8974..2.2
so after this change everytime i try to flash it gives the error : Platform Id Check failed, even though i am using the official and correct version of the firmware.
I have tried so many things to bypass this check but they all failed.
I wonder if the emergency flashing of the device was the cause of changing the Platform ID, I am not sure how the tool even managed to change the device Platform ID, and thinking is there anyway i can return the original platform ID ???
and by the way the attached files you posted for RM-940 they are corrupted or something winRar couldn't extract them.
-Thanks
Click to expand...
Click to collapse
Fixed corrupt zip....Thank you!!! Are you in UEFI flash mode (thunderbolt/gear symbol) or Nokia flash? What tool are you using to flash? See if thor2, WP Image Designer, or ffutool recognize the device the same. I used WPID to flash ffu downloaded from navifirm after emergency flash because Recovery Tool kept getting corrupt ffu file. If all else fails you can try hard reset using power and volume button combos.

tonbonz said:
Fixed corrupt zip....Thank you!!! Are you in UEFI flash mode (thunderbolt/gear symbol) or Nokia flash? What tool are you using to flash? See if thor2, WP Image Designer, or ffutool recognize the device the same. I used WPID to flash ffu downloaded from navifirm after emergency flash because Recovery Tool kept getting corrupt ffu file. If all else fails you can try hard reset using power and volume button combos.
Click to expand...
Click to collapse
Yes the device is in UEFI flash mode, but its completely dead bricked no screen showing no hard or soft reset, nothing showing on the device no vibration no power off/on.
the only way i communicate with the device is through the usb and thor2.exe
I tried to use the ffutool but it won't detect the phone, and neither would the WPID. even though the Nokia NSU and WDRT do detect the device. Is there a special thing should be done so the ffutool could detect the device?
I even made a modified version of the FFUClient/FFuComponent.dll to flash device and changed the usb code detection but still I couldn't get it to work.
BTW the RM-940_firehose.zip you uploaded is still corrupted, i would be happy to try it out and see if this has any effect on the Platform ID of the device.

ekhader said:
Yes the device is in UEFI flash mode, but its completely dead bricked no screen showing no hard or soft reset, nothing showing on the device no vibration no power off/on.
the only way i communicate with the device is through the usb and thor2.exe
I tried to use the ffutool but it won't detect the phone, and neither would the WPID. even though the Nokia NSU and WDRT do detect the device. Is there a special thing should be done so the ffutool could detect the device?
I even made a modified version of the FFUClient/FFuComponent.dll to flash device and changed the usb code detection but still I couldn't get it to work.
BTW the RM-940_firehose.zip you uploaded is still corrupted, i would be happy to try it out and see if this has any effect on the Platform ID of the device.
Click to expand...
Click to collapse
Hmmm... I can download and unzip it fine with 7zip. Try this... http://1drv.ms/1HjO1Gs Can you restore the PLAT.bin from dump using
Code:
thor2 -mode uefiflash -partitionname PLAT -partitionimagefile "PLAT.bin"
If it's in UEFI Flash mode both WPID and FFUTool should detect it. In device manager what is the device description and what is the Hardware ID ?

tonbonz said:
Hmmm... I can download and unzip it fine with 7zip. Try this... Can you restore the PLAT.bin from dump using
Code:
thor2 -mode uefiflash -partitionname PLAT -partitionimagefile "PLAT.bin"
If it's in UEFI Flash mode both WPID and FFUTool should detect it. In device manager what is the device description and what is the Hardware ID ?
Click to expand...
Click to collapse
Thanks i got the files now from one drive but no improvement, and Yes the device is in flash mode the USB driver is "NOKIA BOOTMGR2".
when i try to restore the PLAT.bin i get this error:
Code:
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -partitionname PLAT -partitionimagefile c:\dump\PLAT.bin
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -partitionname PLAT -partitionimagefile c:\dump\PLAT.bin
Process started Tue Nov 24 14:35:06 2015
Debugging enabled for partitionimageflash
Initiating flash of partition image operations
WinUSB in use.
Using programming of partition image method
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 2.29 Implementation version 2.52
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 2.29 Implementation version 2.52
Size of one transfer is 2363392
MMOS RAM support: 0
Size of buffer is 2359296
Number of eMMC sectors: 30535680
Platform ID of device: Nokia.MSM8974..2.2
Async protocol version: 01
Security info:
Platform secure boot enabled
Secure FFU enabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0031
Subblock ID 32
getGpt failed. Error code 12 h
Cannot flash partition image. Write the RDC into the device or use open/RnD HW & SW
Operation took about 0.00 seconds.
THOR2_ERROR_UEFI_RDC_OR_AUTHENTICATION_REQUIRED
THOR2 1.8.2.18 exited with error code 84214 (0x148F6)
and when i try to flash this what i get:
Code:
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -ffufile c:\ProgramData\M
icrosoft\Packages\Products\RM-940\RM940_02540.00019.14484.37028_RETAIL_prod_signed_200_01ACB8_ATT-US.ffu
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -ffufile c:\ProgramData\Microsoft\Packages\Products\RM-940\RM940_02540.00019.14484.37028_RETAIL_pr
od_signed_200_01ACB8_ATT-US.ffu
Process started Tue Nov 24 14:15:13 2015
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 2.29 Implementation version 2.52
Size of one transfer is 2363392
MMOS RAM support: 0
Size of buffer is 2359296
Number of eMMC sectors: 30535680
Platform ID of device: Nokia.MSM8974..2.2
Async protocol version: 01
Security info:
Platform secure boot enabled
Secure FFU enabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0031
Subblock ID 32
[THOR2_flash_state] Device programming started
Using secure flash method
CoreProgrammer version 2015.06.10.001.
Start programming signed ffu file c:\ProgramData\Microsoft\Packages\Products\RM-940\RM940_02540.00019.14484.37028_RETAIL
_prod_signed_200_01ACB8_ATT-US.ffu
FfuReader version is 2015061501
Send FlashApp write parameter: 0x4d544f00
Perform handshake with UEFI...
Flash app: Protocol Version 2.29 Implementation Version 2.52
Unknown sub block detected. Skip...
DevicePlatformInfo: Nokia.MSM8974..2.2
Unknown sub block detected. Skip...
Unknown sub block detected. Skip...
Supported protocol versions bitmap is 31
Secure FFU sync version 1 supported.
Secure FFU async version 1 supported.
Secure FFU sync version 2 supported.
Secure FFU async version 2 supported.
Secure FFU async version 3 supported.
CRC header v. 1
CRC align bytes. 4
Get CID of the device...
Get EMMC size of the device...
Emmc size in sectors: 30535680
CID: Samsung, Size 14910 MB
Start charging...
Requested write param 0x43485247 is not supported by this flash app version.
Start charging... DONE. Status = 0
ConnSpeedEcho: Elapsed= 0.165000, EchoSpeed= 40.91, Transferred= 7077918 bytes
Get security Status...
Security Status:
Platform secure boot is enabled.
Secure eFUSE is enabled.
JTAG is disabled.
RDC is missing from the device.
Authentication is not done.
UEFI secure boot is enabled.
Secondary HW key exists.
Get RKH of the device...
RKH of the device is 3774964A7E6AC7EF7D428DDC0C0EAD71640B0D8DD3BFC3829110AF2D8ED68D7C
Get ISSW Version...
Get ISSW Version, SKIPPED!
Get system memory size...
Size of system mem: 2097152 KB
Read antitheft status...
Requested read param 0x41545250 is not supported by this flash app version.
Send backup to RAM req...
Clearing the backup GPT...SKIPPED!
Successfully parsed FFU file. Header size: 0x000e0000, Payload size: 0x0000000067bc0000, Chunk size: 0x00020000, Header
offset: 0x00000000, Payload offset: 0x00000000000e0000
RKH match between device and FFU file!
Option: Skip CRC32 check in use
Start sending header data...
FlashApp returned reported error in SecureFlashResp!
Status: 0x1304, Specifier: 0x00000000
FA_ERR_FFU_STR_HDR_INVALID_PLATFORM_ID
Send of FFU header failed!
[IN] programSecureFfuFile. Closing c:\ProgramData\Microsoft\Packages\Products\RM-940\RM940_02540.00019.14484.37028_RETAI
L_prod_signed_200_01ACB8_ATT-US.ffu
programming operation failed!
0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image doe
s not match with platform ID of the device.
Operation took about 0.00 seconds.
THOR2_ERROR_FA_FFU_STR_HDR_INVALID_PLATFORM_ID
THOR2 1.8.2.18 exited with error code -100658428 (0xFA001304)
Any Ideas?

ekhader said:
Thanks i got the files now from one drive but no improvement, and Yes the device is in flash mode the USB driver is "NOKIA BOOTMGR2".
when i try to restore the PLAT.bin i get this error:
Code:
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -partitionname PLAT -partitionimagefile c:\dump\PLAT.bin
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -partitionname PLAT -partitionimagefile c:\dump\PLAT.bin
Process started Tue Nov 24 14:35:06 2015
Debugging enabled for partitionimageflash
Initiating flash of partition image operations
WinUSB in use.
Using programming of partition image method
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 2.29 Implementation version 2.52
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 2.29 Implementation version 2.52
Size of one transfer is 2363392
MMOS RAM support: 0
Size of buffer is 2359296
Number of eMMC sectors: 30535680
Platform ID of device: Nokia.MSM8974..2.2
Async protocol version: 01
Security info:
Platform secure boot enabled
Secure FFU enabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0031
Subblock ID 32
getGpt failed. Error code 12 h
Cannot flash partition image. Write the RDC into the device or use open/RnD HW & SW
Operation took about 0.00 seconds.
THOR2_ERROR_UEFI_RDC_OR_AUTHENTICATION_REQUIRED
THOR2 1.8.2.18 exited with error code 84214 (0x148F6)
Any Ideas?
Click to expand...
Click to collapse
Get GPT failed so maybe try this...
Code:
thor2 -mode uefiflash -startsector 0 -imagefile "gpt.bin"

tonbonz said:
Get GPT failed so maybe try this...
Code:
thor2 -mode uefiflash -startsector 0 -imagefile "gpt.bin"
Click to expand...
Click to collapse
hi, Unfortunately this didn't work as well , i get this error:
Code:
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -startsector 0 -imagefile
C:\dump\GPT.bin
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -startsector 0 -imagefile C:\dump\GPT.bin
Process started Wed Nov 25 12:49:09 2015
Debugging enabled for imageflash
Initiating flash of image file operations
WinUSB in use.
Using programming of image method
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 2.29 Implementation version 2.52
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 2.29 Implementation version 2.52
Size of one transfer is 2363392
MMOS RAM support: 0
Size of buffer is 2359296
Number of eMMC sectors: 30535680
Platform ID of device: Nokia.MSM8974..2.2
Async protocol version: 01
Security info:
Platform secure boot enabled
Secure FFU enabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0031
Subblock ID 32
Cannot flash partition image. Write the RDC into the device or use open/RnD HW & SW
Operation took about 0.00 seconds.
THOR2_ERROR_UEFI_RDC_OR_AUTHENTICATION_REQUIRED
THOR2 1.8.2.18 exited with error code 84214 (0x148F6)
is there a way to restore the Platform ID of the device? I am trying to see if i can find where is the check code in the assembly code of thor2.exe but I am not that good in assembly I wonder if there is anyone who tried to skip the check code in the assembly of the thor2.exe

ekhader said:
hi, Unfortunately this didn't work as well
is there a way to restore the Platform ID of the device? I am trying to see if i can find where is the check code in the assembly code of thor2.exe but I am not that good in assembly I wonder if there is anyone who tried to skip the check code in the assembly of the thor2.exe
Click to expand...
Click to collapse
Possibly the Samsung EMMC on Lumia device bug??? Maybe check with
@Kaptaiin and his thread on flashing Lumia phones or try @Heathcliff74 and his thread here http://forum.xda-developers.com/windows-phone-8/development/windows-phone-internals-unlock-t3257483

tonbonz said:
Possibly the Samsung EMMC on Lumia device bug??? Maybe check with
@Kaptaiin and his thread on flashing Lumia phones or try @Heathcliff74 and his thread here http://forum.xda-developers.com/windows-phone-8/development/windows-phone-internals-unlock-t3257483
Click to expand...
Click to collapse
Thanks alot for your help, I have checked out the HeathCliff tool it seems it has potential but unfortunately it does not support lumia 1520 yet
this Microsoft damn tool broke the phone beyond fixing. I wish if @Heathcliff74 could give his opinion about this problem.

Wait to L1520 support, for now, dump partitions from any compatible FFU with WPInternals and keep them until that time.

Any updates here? I'm stuck in exactly the same place. Thanks!

RM892_fh.edp end MPRG8960_fh.ede

nokia lumia 630
ekhader said:
hi, Unfortunately this didn't work as well , i get this error:
Code:
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -startsector 0 -imagefile
C:\dump\GPT.bin
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -startsector 0 -imagefile C:\dump\GPT.bin
Process started Wed Nov 25 12:49:09 2015
Debugging enabled for imageflash
Initiating flash of image file operations
WinUSB in use.
Using programming of image method
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 2.29 Implementation version 2.52
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 2.29 Implementation version 2.52
Size of one transfer is 2363392
MMOS RAM support: 0
Size of buffer is 2359296
Number of eMMC sectors: 30535680
Platform ID of device: Nokia.MSM8974..2.2
Async protocol version: 01
Security info:
Platform secure boot enabled
Secure FFU enabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0031
Subblock ID 32
Cannot flash partition image. Write the RDC into the device or use open/RnD HW & SW
Operation took about 0.00 seconds.
THOR2_ERROR_UEFI_RDC_OR_AUTHENTICATION_REQUIRED
THOR2 1.8.2.18 exited with error code 84214 (0x148F6)
is there a way to restore the Platform ID of the device? I am trying to see if i can find where is the check code in the assembly code of thor2.exe but I am not that good in assembly I wonder if there is anyone who tried to skip the check code in the assembly of the thor2.exe
Click to expand...
Click to collapse
marcio-msa said:
RM892_fh.edp end MPRG8960_fh.ede
Click to expand...
Click to collapse
Hello People, I have a big problem, my nokia Phone model: Lumia 630 Dual SIM
PackageTitle: RM-978 VAR EURO DE CV
Product Code: 059V9G7
ManufacturerHardwareModel: RM-978
Last Firmware: 02040.00021.15235.50004
After I put a new firmware (unfortunately not the right one 059v506 mala) and now it does not turn on. What can i do in the pc it does not connect does not vibrate and just died

Rockies19 said:
Any updates here? I'm stuck in exactly the same place. Thanks!
Click to expand...
Click to collapse
Any update on Lumia 1520 RM-940 issue discussed above. Mine is ATT US 32gb version.
I am stuck in same place. The phone is bricked and no rom will ever flash on it because of the wrong platform ID error.
Phone is UEFI flash mode (connected via WinUSB) with Platform ID of the device being reported as "PlatformInfo is Nokia.MSM8974..2.2".

vdenduluri said:
Any update on Lumia 1520 RM-940 issue discussed above. Mine is ATT US 32gb version.
I am stuck in same place. The phone is bricked and no rom will ever flash on it because of the wrong platform ID error.
Phone is UEFI flash mode (connected via WinUSB) with Platform ID of the device being reported as "PlatformInfo is Nokia.MSM8974..2.2".
Click to expand...
Click to collapse
And has anyone tried to download plat.bin in bulk storage mode using emmcrawtool, a tool where you can load any partition. However, you can use the Windows device repair tool to run the command
Code:
thor2 -mode fbreader-ffufile "C:\ storage location \xxx.ffu" -dump_partitions -filedir D:\dump (the dump may be different
), performs the dump of all partitions of the firmware
Nokia.MSM8974..2.2 this bootloader you can flash firmware from rm-938, not blocked under ATT, by the following command
Code:
thor2 -mode uefiflash -ffufile "C:\storage location \xxx.ffu" -productcodeupdate "product code from rm-938" -skip_flash
and
Code:
thor2 -mode uefiflash -ffufile "C:\storage location \xxx.ffu"

Same Problem
The same thing happened with my lumia 435 after I accidentally format the emmc, it would be possible to create a new emergency file (MPRG8x12_fh.ede in my case) so that after installed the device enter the data storage mode to restore the partition PLAT and UEFI?

Bricked Samsung S8 (TMO version) showing Qualcomm HS-USB QDloader 9008

Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Thanks a lot in advance

taj786 said:
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Thanks a lot in advance
Click to expand...
Click to collapse
This thread may be old, but for now, the only option you have is getting a replacement. I had that qualcomm HS-USB composite identity on my hard bricked lg g stylo and i couldn't do anything about it but get it replaced.

taj786 said:
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Thanks a lot in advance
Click to expand...
Click to collapse
If this is still an issue you face PM me and i will help you unbrick the device!

TimelessPWN said:
If this is still an issue you face PM me and i will help you unbrick the device!
Click to expand...
Click to collapse
I'm ready to help for unbrick my S8

I have the same exact hard brick on my S8, did you guys ever figure out a solution?

TimelessPWN said:
If this is still an issue you face PM me and i will help you unbrick the device!
Click to expand...
Click to collapse
I have the same error, could you solve it?

did you get it fixed? I think TimelessPWN would have used EDL mode.

mweinbach said:
did you get it fixed? I think TimelessPWN would have used EDL mode.
Click to expand...
Click to collapse
I have not fixed it ye, i need help.

FUBUKY said:
I have not fixed it ye, i need help.
Click to expand...
Click to collapse
ok. from what i am reading, you have a hard brick. that QDloader 9008 is EDL mode. the EDL files that we got from QUALCOMM must be sent to you, and you have to run a QUALCOMM software and apply those files through EDL. I currently have the files but I am not 100% sure how to use them. I recommend contacting https://www.facebook.com/GSMCHEN.up for help. he 100% can.

mweinbach said:
did you get it fixed? I think TimelessPWN would have used EDL mode.
Click to expand...
Click to collapse
FUBUKY said:
I have not fixed it ye, i need help.
Click to expand...
Click to collapse
mweinbach said:
ok. from what i am reading, you have a hard brick. that QDloader 9008 is EDL mode. the EDL files that we got from QUALCOMM must be sent to you, and you have to run a QUALCOMM software and apply those files through EDL. I currently have the files but I am not 100% sure how to use them. I recommend contacting for help. he 100% can.
Click to expand...
Click to collapse
thx man, i am retry repair.

mweinbach said:
ok. from what i am reading, you have a hard brick. that QDloader 9008 is EDL mode. the EDL files that we got from QUALCOMM must be sent to you, and you have to run a QUALCOMM software and apply those files through EDL. I currently have the files but I am not 100% sure how to use them. I recommend contacting https://www.facebook.com/GSMCHEN.up for help. he 100% can.
Click to expand...
Click to collapse
Do you mind sharing the files sir? I have this issue and need the files please
Regards,
.:112:.
Sent from my SM-G928T using Tapatalk

stuntman112 said:
Do you mind sharing the files sir? I have this issue and need the files please
Regards,
.:112:.
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
I have been told not to. Sorry.

I hope soon a solution comes out, while I continue with my brick.
GSMCHEN apparently can repair them, but you have not answered my messages.

I found the files needed. Will upload a link tonight
Sent from my SM-G928T using Tapatalk

stuntman112 said:
I found the files needed. Will upload a link tonight
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
thank you very much, I hope the link to try to unbrick my s8 +

Some of the files are in plain sight at AFH. The developer has all the required QCOM tools at the link.
Prog_UFS_Firehose_8998_ddr.elf file:
https://androidfilehost.com/?fid=961840155545585810
Notice it is UFS storage, not EMMC so make sure you have the latest QPST software. Thanks to the developer (hazmat) for the prog file but i believe we will need others also such as .XML's
Messed around with it for a little but didnt figure it out. Hopefully this is a start to dead boot repair for the SM-G955..The Dream2 awakes..
Sent from my SM-G928T using Tapatalk

stuntman112 said:
Some of the files are in plain sight at AFH. The developer has all the required QCOM tools at the link.
Prog_UFS_Firehose_8998_ddr.elf file:
https://androidfilehost.com/?fid=961840155545585810
Notice it is UFS storage, not EMMC so make sure you have the latest QPST software. Thanks to the developer (hazmat) for the prog file but i believe we will need others also such as .XML's
Messed around with it for a little but didnt figure it out. Hopefully this is a start to dead boot repair for the SM-G955..The Dream2 awakes..
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
without the xml files it does not help us.
I had already tried it, the xml files that it has shared (hazmat) are from xiaomi.

mweinbach said:
I have been told not to. Sorry.
Click to expand...
Click to collapse
That's the right thing to do,
Anyway, we have to protect these documents, right

Could not get the device un bricked. Thanks GSM CHEN for help. Possible CPU hardware problem. Seems stuck in EDL
LOG
Programmer Path:C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\prog_ufs_firehose_8998_ddr.elf
Image Search Path: C:\Users\User1\Desktop\nhlos\common\tools\emergency_download
RAWPROGRAM file path: C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\rawprogram0.xml
PATCH file path:C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\patch0.xml
Start Download
Program Path:C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\prog_ufs_firehose_8998_ddr.elf
***** Working Folder:C:\Users\User1\AppData\Roaming\Qualcomm\QFIL\COMPORT_11
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\User1\AppData\Roaming\Qualcomm\QFIL\COMPORT_11
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\prog_ufs_firehose_8998_ddr.elf
11:44:18: Requested ID 13, file: "C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\prog_ufs_firehose_8998_ddr.elf"
11:44:18: 599432 bytes transferred in 0.172000 seconds (3.3236MBps)
11:44:18: File transferred successfully
11:44:18: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:UFS
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\User1\AppData\Roaming\Qualcomm\QFIL\COMPORT_11
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
11:44:22: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM11 --sendxml=rawprogram0.xml --search_path=C:\Users\User1\Desktop\nhlos\common\tools\emergency_download --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
************************************************
11:44:22: INFO: Current working dir (cwd): C:\Users\User1\AppData\Roaming\Qualcomm\QFIL\COMPORT_11\
11:44:22: INFO: Showing network mappings to allow debugging
11:44:22: INFO:
11:44:22: INFO: Trying to store 'rawprogram0.xml' in string table
11:44:22: INFO: Looking for file 'rawprogram0.xml'
11:44:22: INFO: User wants to talk to port '\\.\COM11'
11:44:22: INFO: Took 0.00000000 seconds to open port
11:44:22: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
11:44:22: INFO: If you don't want this, use --dontsorttags
11:44:22: INFO: Looking for file 'gpt_main0.bin'
11:44:22: INFO: Looking for file 'gpt_backup0.bin'
11:44:22: INFO:
Total to be tansferd with <program> or <read> is 44.00 KB
11:44:22: INFO: Sending <configure>
11:44:22: INFO: TARGET SAID: 'Binary build date: Jun 1 2017 @ 14:29:30'
11:44:22: INFO: TARGET SAID: 'Chip serial num: 4294967295 (0xffffffff)'
11:44:22: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
11:44:22: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
11:44:22: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
11:44:22: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
11:44:22: INFO: In handleProgram('gpt_main0.bin')
11:44:22: INFO: Looking for file 'gpt_main0.bin'
11:44:22: INFO: =======================================================
11:44:22: INFO: {<program> FILE: 'C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\gpt_main0.bin'}
11:44:22: INFO: {<program> (24.00 KB) 6 sectors needed at location 0 on LUN 0}
11:44:22: INFO: =======================================================
11:44:22: INFO: TARGET SAID: 'ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0'
11:44:22: INFO: TARGET SAID: 'ERROR: ufs_open_error_code 0 :: 0x27c'
11:44:22: INFO: TARGET SAID: 'ERROR: last ufs_open_error_code 16 :: 0x27c'
11:44:22: INFO: TARGET SAID: 'ERROR: Failed to open the device 3 slot 0 partition 0'
11:44:22: INFO: TARGET SAID: 'INFO: Device type 3, slot 0, partition 0, error 0'
11:44:22: INFO: TARGET SAID: 'WARN: Get Info failed to open 3 slot 0, partition 0, error 0'
11:44:22: INFO: TARGET SAID: 'storage_device_get_num_partition_sectors FAILED!'
11:44:22: INFO: TARGET SAID: 'parseSectorValue could not handle start_sector value'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
11:44:22: {ERROR: program FAILED - Please see log}
Writing log to 'C:\Users\User1\AppData\Roaming\Qualcomm\QFIL\COMPORT_11\port_trace.txt', might take a minute
Log is 'C:\Users\User1\AppData\Roaming\Qualcomm\QFIL\COMPORT_11\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
Sent from my SM-G928T using Tapatalk

a me has not helped me yet.

Error while trying to build a rom

Hi everyone.
I'm trying to build a rom using the well known lineageos repo's.
But unfortunately I get this error:
Code:
hardware/ril-caf/rild/rild.c:60: error: undefined reference to 'joinRpcThreadpool'
It's called like this:
Code:
void rilc_thread_pool() {
joinRpcThreadpool();
}
(The call to joinRpcThreadpool is set by myself to prevent other error's. So you can't find it online in rild.c. It is a test...)
Ok. I know what this error means, but, I can't find how and where joinRpcThreadpool is defined.
I need help... :fingers-crossed: