Database Develop

Extract data.img

Hello,
I have some backup files in the format .img.
Most of them it is possible to extract with unaffy but for data.img I receive unaffys.ex has stopped working.
I´m running on Win7.
Problem signature:
Problem Event Name: APPCRASH
Application Name: unyaffs.exe
Application Version: 0.0.0.0
Application Timestamp: 49c0f760
Fault Module Name: unyaffs.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 49c0f760
Exception Code: c0000005
Exception Offset: 00001340
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 1053
Additional Information 1: bc2e
Additional Information 2: c8cb9f379b8ed40abf4cf05764838fce
Additional Information 3: a990
Additional Information 4: 7b7a26d9fe2af3ce2040f60a66da4947
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=501...mp;clcid=0x0409
Anyone know how to solve this?
I do have a Spritebackup also if anyone know how to extract such files (.sbf) instead.
BR
Pierre

Which version of unyaffs did you use? I've seen old versions floating around that sometimes don't work properly for some files.
Here is a version I compiled from the latest source with some unofficial fixes added. It's worth a try at least.

In the past I've used the the emulator and specified my data.img to be loaded, then used adb to pull the wanted files...

C:\temp\android-sdk-windows\tools>emulator.exe -help
Android Emulator usage: emulator [options] [-qemu args]
options:
-sysdir <dir> search for system disk images in <dir>
-system <file> read initial system image from <file>
-datadir <dir> write user data into <dir>
-kernel <file> use specific emulated kernel
-ramdisk <file> ramdisk image (default <system>/ramdisk.img
-image <file> obsolete, use -system <file> instead
-init-data <file> initial data image (default <system>/userdata
.img

blunden said:
Which version of unyaffs did you use? I've seen old versions floating around that sometimes don't work properly for some files.
Here is a version I compiled from the latest source with some unofficial fixes added. It's worth a try at least.
Click to expand...
Click to collapse
Worked with the new version.
Thanks.

pdais97 said:
Hello,
I have some backup files in the format .img.
Most of them it is possible to extract with unaffy but for data.img I receive unaffys.ex has stopped working.
I´m running on Win7.
Problem signature:
Problem Event Name: APPCRASH
Application Name: unyaffs.exe
Application Version: 0.0.0.0
Application Timestamp: 49c0f760
Fault Module Name: unyaffs.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 49c0f760
Exception Code: c0000005
Exception Offset: 00001340
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 1053
Additional Information 1: bc2e
Additional Information 2: c8cb9f379b8ed40abf4cf05764838fce
Additional Information 3: a990
Additional Information 4: 7b7a26d9fe2af3ce2040f60a66da4947
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=501...mp;clcid=0x0409
Anyone know how to solve this?
I do have a Spritebackup also if anyone know how to extract such files (.sbf) instead.
BR
Pierre
Click to expand...
Click to collapse
gunzip -c ../your-ramdisk-file | cpio -i starting from 1F8B

[Q] Help!!! aka "is my phone bricked?"

So i plugged in my Milestone to my PC and ran the Motorola Software Update, in hopes that 2.2 will get flashed.
Everything went smoothly until the update stopped and my phone was stuck with "SW Update In progress... " on the screen. The Motorola program on my PC had disappeared.
I waited for a bit but nothing happened to my phone, so I took out the battery and rebooted it. Then it booted into the bootloader and said shows "Err:A5,69,4E,00,3D".
Tried to boot into Recovery (i rooted my phone with openrecovery a few months back) but same, won't load recovery, won't boot Android either. Same error message.
Then I tried to flash the vulnerable SBF again, RSDLite shows all ok but I still can't enter into Recovery mode. Then I tried to flash the whole SBF instead of just the vulnerable recovery, and RSDlite stopped at 19% with this error:
ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xD304DB80 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=39
Device ID: 0
Click to expand...
Click to collapse
Did Google search on this, found nothing useful, I don't know what is the problem. Have tried UK, HK and SG firmware but nothing works. Did my phone just become a brick? Now the IMEI and other details doesn't even show up on RSDLite anymore...
My system is Windows 7 32-bit, using RSDLite 4.9, latest drivers (4.8.0). Here is the full RSDLite log:
00:21:44, January 25, 2011
Line: 527
ERROR: AP Die ID: 22700114fe980304000000002400
00:21:44, January 25, 2011
Line: 534
ERROR: BP Die ID: 0000000000000000000000000000
00:21:44, January 25, 2011
Line: 541
ERROR: AP Public ID: 449dd7999eac8318cda5dc848722cd304fb725de
00:21:44, January 25, 2011
Line: 548
ERROR: BP Public ID: 0000000000000000000000000000000000000000
00:25:42, January 25, 2011
Line: 340
ERROR: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xD304DB80 Command: ADDR
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
00:25:42, January 25, 2011
Line: 1190
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
00:25:42, January 25, 2011
Line: 597
ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xD304DB80 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=39
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Click to expand...
Click to collapse

What about the bootloader mode (aka fastboot mode)?
Does that work? Does a "fastboot devices" work at that point?
If fastboot sees your devices, you could flash from there.
Fastboot gives you the option to flash an update.zip, a specific partition or all partitions...
Sent from my Milestone using Tapatalk

A855 Boot Loop
Rooted - Rom Manager Clockwork Mod install
Liquid Frozen Yogurt 1.95
Phone boots to animation screen and reboots
Can not reboot into recovery
Will boot into bootloader
ADB recognizes phone when it is at animation screen in windows - "adb reboot recovery" reboots phone but not into recovery - same for "adb reboot bootloader"
Suggestions?
Love,
Guy with a pretty paperweight

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?

[Solved] ERROR: 32-bit Linux Android emulator binaries are DEPRECATED

Hello,
I am taking my first steps into trying to create an Android app.
In installed Android Studio 1.5.1 on Linux Mint 17.3 (kernel 3.19.0-32-generic, 64-bit). JRE version is 1.7.0_95-b00 amd64 (according to the about box).
I try to run the app in the emulator. I have created a virtual device, with the following details:
Code:
Name: Moto_X_Play_API_23
CPU/ABI: Google APIs Intel Atom (x86_64)
Path: /home/gewe/.android/avd/Moto_X_Play_API_23.avd
Target: Google APIs (API level 23)
Skin: nexus_5x
Snapshot: no
hw.lcd.density: 400
hw.dPad: no
avd.ini.encoding: UTF-8
hw.camera.back: none
disk.dataPartition.size: 200M
hw.gpu.enabled: yes
runtime.network.latency: none
skin.dynamic: yes
hw.keyboard: yes
runtime.network.speed: full
hw.device.hash2: MD5:3f75bdae5e6cbfeae9214f0ae67b97b4
hw.ramSize: 1536
tag.id: google_apis
tag.display: Google APIs
hw.sdCard: yes
hw.device.manufacturer: User
hw.mainKeys: no
hw.accelerometer: yes
hw.trackBall: no
hw.device.name: Moto X Play
hw.sensors.proximity: yes
hw.battery: yes
AvdId: Moto_X_Play_API_23
hw.sensors.orientation: yes
hw.audioInput: yes
hw.camera.front: none
hw.gps: yes
avd.ini.displayname: Moto X Play API 23
snapshot.present: no
vm.heapSize: 64
runtime.scalefactor: auto
If I select this virtual device I get the following error message:
Code:
Cannot launch AVD in emulator.
Output:
WARNING: Cannot decide host bitness because $SHELL is not properly defined; 32 bits assumed.
ERROR: 32-bit Linux Android emulator binaries are DEPRECATED, to use them
you will have to do at least one of the following:
- Use the '-force-32bit' option when invoking 'emulator'.
- Set ANDROID_EMULATOR_FORCE_32BIT to 'true' in your environment.
Either one will allow you to use the 32-bit binaries, but please be
aware that these will disappear in a future Android SDK release.
Consider moving to a 64-bit Linux system before that happens.
I downloaded an example app, but that results in the same error.
Why does Android Studio or the emulator think it is running on a 32-bit system?
How can I get rid of this error?

The emulator uses the shell to define if you are running a 32 or 64 bits machine.
The $SHELL environment variable doesn't seem to be defined in your case
Try to launch Android Studio from a terminal:
Code:
$ <YOUR_ANDROID_STUDIO_INSTALL_DIR>/bin/studio.sh
If this works, try to create a menu entry starting the following command:
/bin/bash <YOUR_ANDROID_STUDIO_INSTALL_DIR>/bin/studio.sh

I am running Android Studio from a terminal, I don't have a menu entry for it.
If I change the command into
Code:
export SHELL=/bin/bash && android-studio/bin/studio.sh
the emulator runs fine.
Another account on the same machine has the environment variable SHELL set automatically. Both accounts do not have a .bashrc in their home directory. The both have identical .pam_environment and .profile files.
From where could it have been set?

gewe said:
I am running Android Studio from a terminal, I don't have a menu entry for it.
If I change the command into
Code:
export SHELL=/bin/bash && android-studio/bin/studio.sh
the emulator runs fine.
Another account on the same machine has the environment variable SHELL set automatically. Both accounts do not have a .bashrc in their home directory. The both have identical .pam_environment and .profile files.
From where could it have been set?
Click to expand...
Click to collapse
Well AFAIK, the SHELL environment variable is set by the shell executable itself when it starts. It looks like something unsets it on your system.
You already checked the 3 files that came to my mind.
Maybe one of the global environment file (/etc/environment, /etc/bash.bashrc, /etc/profile or /etc/profile.d/*) But I doubt it as you would have the same issue with your other account

With some help from the Linux Mint forum the problem is solved. In /etc/passwd some accounts did not have a default shell specified. Adding that solved the problem.
Thanks for pointing me in the right direction!

General issue in Android Studio - Cannot launch AVD in emulator.

Hello,
I could not find an answer on how to preload the expected libaries so I hope anyone can help me here.
I am a complete noob In devloping with Android Studio.
I tried to write a small app and ran it with the following errors while loading th e AVD (Android 5.1 , WVGA):
Code:
Cannot launch AVD in emulator.
Output:
libGL error: unable to load driver: i915_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i915
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request: GLXBadContext
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 49
Current serial number in output stream: 48
emulator: ERROR: virtual device name contains invalid characters
emulator: could not find virtual device named '3.2_QVGA_(ADP2)_API_22'
I think to get this solved will not be quiet diffcult for advanced users.
Thank you verry much for your help! :good:
Some infos that might help you:
OS: Kubuntu 16.04
Android Studio 2.2.3
used coding language: Java