Hi,
So I started fiddling with flashing a RM-937 image onto a RM-940 device yesterday and I feel like I've achieved some success as the step I get stuck on, there is nothing about it online - 0 results on google.
Anyhow, at first I modified Nokia.Murzim.Uefi.FlashApp.CoreProgrammerAdaptation to take "SKIP_ID_CHECK" as an option which turned out to be a dead end as I was not authenticated with Nokia Care Servers and those flags need certain permissions to execute.
My second route was trying to trick the system into thinking it was an actual RM-940 ffu file, so I went ahead and downloaded the modified Nokia.Packages.VariantPackage.DataPackage20.dll to be able to edit the .VPL. I changed the FileList portion of the .VPL to contain the files from the latest RM-937 firmware instead of it's original RM-940 file list.
I also edited the RM-937 .ffu file to be marked as a release for the ATT version of the 1520 using HxD, saved the changes and checked the new CRC which I then applied in the RM-940 .vpl.
It successfully detects the image as a RM-940 image when I load up Product Support Tool for Store 5 and goes as far as to failing with the message:
"Unable to parse FFU file. The FFU has wrong version, must be version 2.0 but file has 1.0"
I don't know if this stage has been reached before, assuming it has, but nothing has been made public. I was hoping that someone on here might have a clue about how to edit the .ffu file version flag to see if that might be the last step in successfully flashing a RM-940 to a RM-937.
Regards,
Ekeroth88
few monthes ago i have flashed lumia 925 to another RM version but since then something was changed ?!
i am also having trouble with changing lumia 520 rom...
Q&A for [Help] programmer? unbrick possible without JTAG
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Help] programmer? unbrick possible without JTAG. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
(post this here as well, just in case)
Hey! I see we are very close...
I have some xml files that belong to the Huawei Ascend W1, maybe they can help us to generate the mbn, they contain partition info but I wasn't able to generate the mbn because the tutorial was for an old version of QPST and they changed the XML structure.
I can't post directly into your thread because I have less than 10 posts in XDA, but I will upload it when i'm home.
We have the bin/hex now, Maybe this could be the final piece of the puzzle.
If it works, we can even create our own free tool to solve this problem (until MS releases an official one) and stop InfinityBox and others from making profit out of this problem.
Can you make step-by-step guide fo recovery phone?
I have Lumia 920 brick
Can't find HEX for my RKH: 3676E9A0045A7EF8417B8E0E0677CED5F9DD47799826AEAE75F7081818DE716E
How can I get it? Please, help
Nokia Lumia 625H rm-943...
CD84376222AAF204C85119532BF34EA55C8844E4.bin problem
Hi, since bin2hexQ not working correctly for some BIN files in the list.
MIT bin2hex have been found and compiled (with slight code changes for c++). Did this, because I'm working on x64 bit system. See code and exe in attachments.
Still looking for solution with CD84376222AAF204C85119532BF34EA55C8844E4.bin.
Sure thing, :020000042A00D0 as first line, :040000052A000000CD as one before last added.
Thanks to Cicin7 on MS forum, also added following string
:020000042A01CF
between
:10FFF0009104012A01000000000000000000000040
and
:1000000001000000E8FF002A01000000900000004D
to prevent memory overwriting, but thor2 still saying:
THOR2_EMERGENCYFLASHV1_ERROR_MSG_SEND_RECEIVE_FAILED
THOR2 1.8.2.15 exited with error code 85021 (0x14C1D)
Does anybody have any ideas, what's wrong with the hex(file attached)?
http://forum.xda-developers.com/windows-phone-8/development/help-programmer-unbrick-jtag-t3082592
Finally, solution is here!
Thanks all!
johntheredimid said:
http://forum.xda-developers.com/windows-phone-8/development/help-programmer-unbrick-jtag-t3082592
Finally, solution is here!
Thanks all!
Click to expand...
Click to collapse
Yet no luck with Lumia 925 and CD84376222AAF204C85119532BF34EA55C8844E4.bin. Unfortunately, current solution is not working for us
---------- Post added at 11:30 PM ---------- Previous post was at 10:41 PM ----------
In MPRG_HEX.zip, generated files for bigger *.bin files are wrong (for files of 73 kb original size).
Those files are very different from generated by bin2hex (not bin2hexQ).
Edit : Actually i don't think it's a driver problem !
PS : My phone is a 925 (RM-910)
It was a problem on the hex file, i generated a new one(attached),
here is the result
Click to expand...
Click to collapse
I have Lumia 925 (RM-892). And provided hex, just like the hex files I've prepared is not working for my device.
Thank you John.
Actually my experiments started based on your thread only. You had provided enough data (like all the binary files, tools, etc. etc.) to investigate the recovery process. Thanks a lot
WORKS!!!
YEAH!! THANK YOU!!!
anything you want to ask me pls, do it (lumia 520 ^^)
the same problem with my L 925
THOR2 1.8.2.15
Built for Windows @ 13:33:08 Mar 11 2015
Thor2 is running on Windows of version 6.1
thor2 -mode emergency -hexfile C:\dump\CD84376222AAF204C85119532BF34EA55C8844E4.
hex -mbnfile C:\dump\msimage.mbn -orig_gpt
Process started Fri May 01 15:23:59 2015
Logging to file C:\Users\gewili\AppData\Local\Temp\thor2_win_20150501152359_Thre
adId-5848.log
Debugging enabled for emergency
Initiating emergency download
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.31.001
Hex download selected
Check if device in Dload
Connection to DLOAD mode succeeded
Get Dload parameters
Sending HEX flasher to the device
Sending GO command if HEX flasher successfully uploaded.
Message send failed with error code -1
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 4.00 seconds.
THOR2_EMERGENCYFLASHV1_ERROR_MSG_SEND_RECEIVE_FAILED
THOR2 1.8.2.15 exited with error code 85021 (0x14C1D)
any help here would be appreciated guys
thor2
no abre el thor2 , probé con dos sistemas operativos, windows 7 y 8.1, en dos computadoras diferentes, abre y se sierra de inmediato
It workkkkksss
Thank you soo so so so much, my lumia is alive *-*, if you want to ask me anything, just do it :3
Success!
My lumia 520 is alive again
Thanks for the tutorial
It wokrs to me (Lumia 520)!!!
Thanks a lot for the guide. The only problem was the rute for the dump files - use another path like "D:/dump" o desktop.
RM892 seems to be cursed.
migoz said:
the same problem with my L 925
THOR2 1.8.2.15
Built for Windows @ 13:33:08 Mar 11 2015
Thor2 is running on Windows of version 6.1
thor2 -mode emergency -hexfile C:\dump\CD84376222AAF204C85119532BF34EA55C8844E4.
hex -mbnfile C:\dump\msimage.mbn -orig_gpt
...
Using default emergency protocol
ALPHA EMERGENCY FLASH START
Emergency Programmer V1 version 2014.10.31.001
Hex download selected
Check if device in Dload
Connection to DLOAD mode succeeded
Get Dload parameters
Sending HEX flasher to the device
Sending GO command if HEX flasher successfully uploaded.
Message send failed with error code -1
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 4.00 seconds.
THOR2_EMERGENCYFLASHV1_ERROR_MSG_SEND_RECEIVE_FAILED
THOR2 1.8.2.15 exited with error code 85021 (0x14C1D)
any help here would be appreciated guys
Click to expand...
Click to collapse
The fact that you getting -1 after sending the hex, means your hex is wrong.
If your Lumia 925 is RM-910, you still have a chance. In attached archive there are correctly converted HEX files for models, with big binaries.
Else, it won't help you. Our fellow friend Cicin7 on MS forum, did sniffed the data packages send/recived by device during flashing. And this is what his got:
RM892 seems to be cursed. I used an USB communicaton sniffer to look at the command where it fails. Upload of flasher seems OK, then the GO command is sent:
7E 05 2A 00 00 00 DE BA 7E
and device responds:
7E 03 00 0A F2 86 7E, which, according to Qualcomm documentation is NAK packet (03) with reason "Write-verify failed" (000A). I have no idea what hides under this error.
Expected response would be 7E 02 ...
Click to expand...
Click to collapse
fenriv said:
The fact that you getting -1 after sending the hex, means your hex is wrong.
If your Lumia 925 is RM-910, you still have a chance. In attached archive there are correctly converted HEX files for models, with big binaries.
Else, it won't help you. Our fellow friend Cicin7 on MS forum, did sniffed the data packages send/recived by device during flashing. And this is what his got:
Click to expand...
Click to collapse
yeah mine is 892 I've been trying so hard and still nothing,would you tell me how to generate a new hex file,i tried using one of the attached hex files but in vain,may be i'm doing it wrong or something :crying:
migoz said:
yeah mine is 892 I've been trying so hard and still nothing,would you tell me how to generate a new hex file,i tried using one of the attached hex files but in vain,may be i'm doing it wrong or something :crying:
Click to expand...
Click to collapse
Correct hex files are attached to previous message.
If you want to generate your own - there is an instruction on a top post in the thread - just follow the instruction, covert *.bin to *.hex, and then edit it a bit.
But, since you are RM-89x owner, there will be no difference - even correctly generated HEX from provided BIN files (CD84376222AAF204C85119532BF34EA55C8844E4.bin in our case) will not give you any results.
I won't say our devices are doomed, but there is for sure no correct MPRG flasher is available for now.
Thanks!!! Worked - dead boot repair
Congratulations for the job, i fix dead boot in lumia 520 with this way. But, in my case, i used 7C81AABA97E4904DB782605A6C74A59480361E5A.hex and i don't modified in notepad, WORKED!
Sorry my english, i'm brasilian.
Help with Lumia 930 prototype
I have a lumia 930 prototype and when I try this method, says that the image ffu isn't signed for my device
---------- Post added at 12:52 PM ---------- Previous post was at 12:48 PM ----------
raulps10 said:
Congratulations for the job, i fix dead boot in lumia 520 with this way. But, in my case, i used 7C81AABA97E4904DB782605A6C74A59480361E5A.hex and i don't modified in notepad, WORKED!
Sorry my english, i'm brasilian.
Click to expand...
Click to collapse
the same error appear in Nokia Care Suite and others
Hello, long time no see.
I need help to Windows Phone can run on Nokia X2 -Ara. Today i tested on Nokia x2 prototype F1 RM1014 1 sim
This work high knowledge user, advance user, not for normal,noob or another guy dont know what they doing, need high knowledge.
Request:
A EDL cable to force X2 go to qcom 9008 dload or anothet mehod to force x2 go to qcom dload 9008
Full android backup of you system,back up via DD command or another tool kit. Full emmc image 3.6gb not backup of system,data,.tcc in twrp. full EMMC Backup via Terminal Android is my choise
Have a lot time to download file,restore file,flash file
And dont blame me if it doesnt boot to system
Need installed Thor2 . understand command of Thor2. Need install windows device recovery tool
XDA:DevDB Information
Firmware Windows Phone 8 on Nokia X2 (Unstable, need more work), ROM for the Nokia X2
Contributors
thinhx2
ROM OS Version: Windows 8 Mobile
ROM Kernel: Windows Kernel 1
Version Information
Status: Alpha
Created 2019-07-11
Last Updated 2019-07-29
Backup full emmc of android by terminal apk:
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img
Coppy it to pc/laptop to restore android
Flash Emergency payload of Windows phone:
https://protobetatest.com/downloads/ download lumia emergency payload from this site, extract folder rm1071
Use EDL cable to force x2 go to qcom 9008 dload (for my self)
Open Thor2, type:
thor2 -mode emergency -hexfile "path to ede file" -edfile "path to edp file"
Done you will see in Device Manager,it will show lumia usb connectivity
But no display because it just repartition few partition of WP,but dont worry continue to have full partition of wp. Next post
Download this file ~4gb : https://drive.google.com/file/d/1kvJzOCaekZLkPNxGYk_ol0LQGUmuGl0M/view
Continue type command in Thor2 : thor2 -mode uefiflash -imagefile [PATH TO THE DOWNLOADED FILE] -startsector 0
Wait. It take you about 33mins ) . after success. Reboot device. You will got WP8.1 on x2. But have big problem : no display driver
If you flash UEFI from 532/435 you will have display work but after logo windows. Device will reboot,cant go to system. link : https://drive.google.com/file/d/15Gz6IfBPL1LiJcphQbEEVYIqX7uwl1Se/view?usp=sharing
I tried flash FFU and full emmc backup of 435/532 but same result: after logo Windows. Device will reboot
I need help to fix problem
And i think i need try install win rt on it
And x2 only have 4gb rom. Cant install rt
and i only try it on x2 prototype. Not x2 retail. Maybe x2 retail have security fuse. But who know. I just try for fun
dont try if you dont have high knowledge. It really hard. Not easy
It so fun ???
Time to sleep,i will update tomorrow. A great nght to play wp with x2 ))
This work not for normal user. Dont try it if you dont have good knowledge ))
Uefi mass storage mode work fine on x2
some one can help me port display driver?
thinhx2 said:
some one can help me port display driver?
Click to expand...
Click to collapse
can you try copying oempanel.sys and oempanel_etw.dll from 532\MainOS.img\Windows\system32\DRIVERS\ to vela and flashing ??
vatva69 said:
can you try copying oempanel.sys and oempanel_etw.dll from 532\MainOS.img\Windows\system32\DRIVERS\ to vela and flashing ??
Click to expand...
Click to collapse
Problem from Display config of Uefi. Uefi of 532 can enable display of 2 fw
thinhx2 said:
Problem from Display config of Uefi. Uefi of 532 can enable display of 2 fw
Click to expand...
Click to collapse
Ok, can you copy uefi config from 532?
vatva69 said:
can you try copying oempanel.sys and oempanel_etw.dll from 532\MainOS.img\Windows\system32\DRIVERS\ to vela and flashing ??
Click to expand...
Click to collapse
You living in Hanoi? Can tell me you address?. I living at Vinhome riverside
Hi, I had a Lumia 925 and wanted to jailbreak it since I found a few people who did this and I wanted it for my own reasons. Anyway, as with all the guides, I used the Windows Phone Internals tool. I downloaded all of the files from LumiaFirmware.com and I opened Windows Phone internals, selected Unlock bootloader and added all of the files (rebooting to Flash mode, of course) and it wouldnt let me start. It would always say: The OS version is not supported. Use a donor-FFU. I tried with another FFu, but it still did not work (I tried flashing the downloaded rom and trying again, but same thing). Anyway, now I did something and now the device is recognised in Windows as "Qualcomm QHSUSB-DLOAD". How can I restart the phone? Windows Phone Internals does not recognize it.
By the way, this is my first time doing things, I may have done something wrong. I did download all drivers, in case you are wondering
Hi,
open windows device manager and use the windows/nokia emergency driver for your device. Then look for thor2.exe, it is a part of WindowsDeviceRecoveryTool.
Open a command prompt window.
Type/paste thor2 -mode emergency -hexfile D:\Packages\Products\RM-994\FAST8930_BATMANROW.hex -mbnfile D:\Packages\Products\RM-994\RM994_msimage_v1.0.mbn -ffufile D:\Packages\Products\RM-994\RM994_3056.40200.1407.0002_RETAIL_eu_euro2_1168_02_405247_prd_signed.ffu
REPLACE my product RM994 with your product and the file names too. Replace D:\Packages\Products with the directory on your PC. You get the emergency files from lumiafirmware.com.
Contact me if there are problems, we will sort that out.
Regards,
Joachim