Related
Hi All
I've searched and not found much info on this.
I've got a dump of an HTC HD7 using the Riff box (JTAG). The file is a 512MB BIN file.
Basically I would like to be able to see the files inside it. Ideally I would like to see the files/folders/structure inside the dump. I don't know how difficult or easy this is, so forgive me if I'm asking for the impossible. But is there a way of converting the bin file to something like a cab/nbh or even the files/folders so that I can view them in explorer or some similar tool?
At the moment I'm viewing the file in a hex editor trying to carve out certain files. But I figure since the file system and structure is known on Windows Phone 7, there may be a way of converting the entire image to a better support format.
So if anyone can suggest any tools or ways of doing this, it would be much appreciated.
Thanks
How do you use the jtag to get a dump of it? I don't know if you can use htcrie or not (search in this forum for the tool)
Sent from my SGH-i917 using XDA Windows Phone 7 App
snickler said:
How do you use the jtag to get a dump of it? I don't know if you can use htcrie or not (search in this forum for the tool)
Click to expand...
Click to collapse
I use the Riff Box which is supposed to a dump of the ROM/NAND, which it did, into a .bin file.
I've tried htcrie, but it doesn't load the bin file. I've tried looking for a tool that converts the .bin to a nbh, but found nothing so far
puunda said:
I use the Riff Box which is supposed to a dump of the ROM/NAND, which it did, into a .bin file.
I've tried htcrie, but it doesn't load the bin file. I've tried looking for a tool that converts the .bin to a nbh, but found nothing so far
Click to expand...
Click to collapse
Where do you get a riff box from? I want to dump my rom. I would look into the Windows Mobile threads and see if there is a tutorial OR pm ansar or xboxmod and see if they can help out. If possible can you provide how to obtain an use the riff box?
Sent from my SGH-i917 using XDA Windows Phone 7 App
nbh or nb it's for bootloader to write to nand, so it will have diff format with nand dump.
ted973 said:
nbh or nb it's for bootloader to write to nand, so it will have diff format with nand dump.
Click to expand...
Click to collapse
I'm not sure. I took a complete dump of the HD7 and it gave me a 512MB file in a .bin format. I believe that includes the bootloader and everything else, but I could be wrong.
I don't mind what kind of file it gets converted to, as long as I can view the files inside. Thanks
puunda said:
I'm not sure. I took a complete dump of the HD7 and it gave me a 512MB file in a .bin format. I believe that includes the bootloader and everything else, but I could be wrong.
I don't mind what kind of file it gets converted to, as long as I can view the files inside. Thanks
Click to expand...
Click to collapse
Try this thread http://forum.xda-developers.com/showthread.php?t=1260757 . There's something on there that speaks about WP7 Binary tools.
snickler said:
Try this thread http://forum.xda-developers.com/showthread.php?t=1260757 . There's something on there that speaks about WP7 Binary tools.
Click to expand...
Click to collapse
I've looked on that thread and have downloaded the tools. I've also messaged the author of the tool, but not got a reply yet. It looks like the tools which does work on the raw dump/bin files are for the logo and bootloader, not the entire image.
I'm still working on it, but there seems to be a lot of info that I need to sort though.
You may use Qualcomm tool from riff plugin. It's view all partitions
Missed this one.
No questions in the development section please!
Thread Closed
For those who are still waiting for a fix for the update error and don't want to undergo the recovery process, I found a different solution, which doesn't need a recovery operation on the phone.
I tested it with success on my 1020 and another 925 which were stuck in the CU build .297.
Keep in mind that the parameters that I will use are specific to these phone models, so if you have a different one you need to find the parameters specific to your phone model.
This is an heuristic procedure, tested on a limited number of phones, so use it at your risk, keeping in mind that you could have problems or need to recover your phone loosing all your data, so do a proper backup before.
Let's start.
The problem appears because, during update phase, the oeminput.xml file becomes corrupted: as far as I know it happens only on some x20 models, and not for all the users.
Now we're going to rebuild it...
Go to the following link
https://msdn.microsoft.com/en-us/library/windows/hardware/dn756630(v=vs.85).aspx
Copy the content of example file oeminput.xml: i.e. copy the content of the framed zone after the phrase "The following example shows the contents of a sample ProductionOEMInput.xml file"
Paste in a .txt file which you'll rename and change extension so that it becomes oeminput.xml. Save it with notepad.
Now modify the file
at the node <SOC>{PROCESSOR_NAME}</SOC> modify {PROCESSOR_NAME} fake parameter in order to have the processor name of your phone: for the 920/925/1020 use QC8960
at the node <Resolution>480x800</Resolution> instead of 480x800 use the resolution of your phone: for the 920/925/1020 use 768x1280
in all the nodes related to language <Language>en-US</Language> use the language of your phone: I used for example it-IT because I have the phone in Italian language.
Save the file.
Now if you still don't have interop tools installed (but I think you should have if you arrived to CU with an x20 phone model) install it.
Launch interop tools and then click this device and enable full file system access. Reboot your phone, connect it to a pc with cable: you'll see more directories than usual, because you also unlocked system dirs: be careful not to delete or modify any dir apart from what you find in this guide or you'll risk to damage your phone. If you want to find your usual dirs (docs photos...etc), go to phone\Data\Users\Public. I advise you that after the procedure I couldn't deactivate full file system access, because it continues re-activating in interop tools, maybe there is a way: but you can live with this, because you can find the usual dirs in the path that I specified...
Now go to phone\windows\imageupdate, make a backup on pc of the current oeminput.xml and overwrite it with the new one.
At this point in the phone go to settings, update and then search for updates: you should find Fall Creators Update...
Good Luck!
p.s. I didn't extensively search on the forum if a similar guide has been already posted, in the case sorry for the duplication.
Thanks to Antonio who has actively participated in the realization of this guide
sigfrid696 said:
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx
Click to expand...
Click to collapse
The link is wrong
Thank you!
I modified it, now it should be ok!
friend can you share the oeminput.xml file that you used?
NeoTriXz said:
friend can you share the oeminput.xml file that you used?
Click to expand...
Click to collapse
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
sigfrid696 said:
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
Click to expand...
Click to collapse
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
NeoTriXz said:
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
Click to expand...
Click to collapse
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
sigfrid696 said:
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
Click to expand...
Click to collapse
thank you friend, for your time, but I already solved it, well I had to perform a hard reset,
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
i could not able to copy paste it it shows you don't have permission
how i get permission
---------- Post added at 06:42 AM ---------- Previous post was at 06:22 AM ----------
it gives me this error
Yash Agarwal windows said:
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
Click to expand...
Click to collapse
I think you should use for 520
<SOC>QC8227</SOC>
<Resolution>480x800</Resolution>
If you receive an error when you try to overwrite oeminput.xml, it means that your phone has not been unlocked for full filesystem access. Please refer to the guide in order to enable full filesystem access
thanks
it worked for me
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
this error is get due to incorrect processor no or incorrect screen resolution
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
You can examine your oeminput.xml file and check if it is somehow not well-formed.
If that is the case you can use
<SOC>QC8926</SOC>
<Resolution>720x1280</Resolution>
Thanks for the reply guys.
I couldn't wait longer, so went with an reset. It updated fine after that.
Later came to know it was some server issue
how do you replace the xml file? it says copying but refuses to actually replace the file.
rancorx2 said:
how do you replace the xml file? it says copying but refuses to actually replace the file.
Click to expand...
Click to collapse
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Yash Agarwal windows said:
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Click to expand...
Click to collapse
how is complete unlock ??????????
I use interop tools
bloody_earth said:
how is complete unlock ??????????
I use interop tools
Click to expand...
Click to collapse
The error overwriting oeminput.xml happens when you haven't obtained full filesystem access.
In order to obtain full filesystem access:
Open Interop Tools, then this device, then Interop Unlock.
Check Full Filesysytem Access and restart your device.
Refer to this thread to download correct version of Interop Tools
https://forum.xda-developers.com/windows-10-mobile/tutorial-restore-glance-windows-10-t3540571
Let me know if you can solve the problem this way.
I was trying to unlock camera2 api on my phone but every attempt ends with "Updater process ended with ERROR: 1". I tried a few other files but it ended the same way. Changing from TWRP to OrangeFox doesn't help as well. Is there any way to make something with it without root?
If I'm not wrong you can use any build prop editor to enable camera2api as well. There are several threads where you can find the strings to manipulate.
Tischbein said:
If I'm not wrong you can use any build prop editor to enable camera2api as well. There are several threads where you can find the strings to manipulate.
Click to expand...
Click to collapse
Build prop editors need root and I can't do it through ADB because when I'm entering recovery pc stops detecting my phone in ADB.
KapitanSuchar said:
Build prop editors need root and I can't do it through ADB because when I'm entering recovery pc stops detecting my phone in ADB.
Click to expand...
Click to collapse
Clean install then, editing build.prop requires root
For anyone searching..
I was facing the "no caller id issue" on VOLTE/VOWifi calls
The solution for me was always this guide.
However, this wasn't a stable solution for A12, as the made changes to the modem config were gone after a reboot and defaulted back to ROW Commericial. My own network wasn’t available in the PDC list as well (NL KPN)..
Then I recently started playing with the firmware flashable img from xiaomifirmwareupdater.com (fw_alioth_miui_ALIOTHGlobal_V13.0.3.0.SKHMIXM.zip in my case).
I had extracted the modem.img , opened it with powerISO and I found that the PDC tool wasn't showing my specific network because my network wasn't listed in one of the txt files in the folder \image\modem_pr\mcfg\configs\mcfg_sw.
However, the right modem config file (mcfg_sw.mbn) was available, deeply nested in the generic folder.
(\image\modem_pr\mcfg\configs\mcfg_sw\generic\EU\KPN\Commercial\NL).
So there are a lot more (hundreds) configs available than the PDC tool shows!
Not knowing which txt file I needed to change to add my network, I boldly replaced the default ROW commercial mcfg_sw.mbn file (\image\modem_pr\mcfg\configs\mcfg_sw\generic\common\ROW\Commercial) with the one I found nested.
- Saved the image file.
- Replaced it in the firmware zip.
- Flashed the edited zip file.
- Boot into system
Success!
I now have a working VOLTE/VoWifi after each reboot!
Checking with the PDC tool afterwards. It showed that my own network was automatically chosen.
No root acces needed!
Good luck!
Hi there landgenoot,
Came across your topic. Facing the same issues overhere with KPN on a Mi10tpro.
Can you tell me how you extracted the modem.img from the firmware. I did my research but not way I could find the modem.img file in the firmware (extracted with winrar)
TY
hi there, problem solved. your solution was great and working for me too!
Thank you very much!
I guess it can easily be an universal for Xiaomi Devices
I also tried this method on a Poco F3 device, but it didn't work. I am from EU\Slovenia and my mobile operator is Mobitel. I found the settings in the file structure
\image\modem_pr\mcfg\configs\mcfg_sw\generic\EU\Mobitel\Commercial\SI\mcfg_sw.mbn
and copied them to the
\image\modem_pr\mcfg\configs\mcfg_sw\generic\common\ROW\Commercial\mcfg_sw.mbn
in the modem.img file, but I still get an unknown caller ID when using VoLTE.
I also added the path of my carrier settings to the text files (mbn_global.txt, oem_sw.txt, oem_sw_j11.txt and oem_sw_l3a_global.txt) that were missing at
\image\modem_pr\mcfg\configs\mcfg_sw
hoping that would solve my problem, but the caller id didn't work in that case either.
In order to check if the settings for my operator are correct, I also tried the process with the QPST and PDC tools. This time the caller id works, but the process is really complicated, especially with root access in the ArrowOS I'm using and I don't want to do it every time I upgrade.
Miami_T said:
I also tried this method on a Poco F3 device, but it didn't work. I am from EU\Slovenia and my mobile operator is Mobitel. I found the settings in the file structure
\image\modem_pr\mcfg\configs\mcfg_sw\generic\EU\Mobitel\Commercial\SI\mcfg_sw.mbn
and copied them to the
\image\modem_pr\mcfg\configs\mcfg_sw\generic\common\ROW\Commercial\mcfg_sw.mbn
in the modem.img file, but I still get an unknown caller ID when using VoLTE.
I also added the path of my carrier settings to the text files (mbn_global.txt, oem_sw.txt, oem_sw_j11.txt and oem_sw_l3a_global.txt) that were missing at
\image\modem_pr\mcfg\configs\mcfg_sw
hoping that would solve my problem, but the caller id didn't work in that case either.
In order to check if the settings for my operator are correct, I also tried the process with the QPST and PDC tools. This time the caller id works, but the process is really complicated, especially with root access in the ArrowOS I'm using and I don't want to do it every time I upgrade.
Click to expand...
Click to collapse
Sorry it didn't work for you. I assume that you properly replacement the edited modem IMG in the firmware zip and flashed the edited firmware?
Perhaps you can also try again using the same config you chose with the PDC tools
I did try I think three times even with different national mobile providers (A1, Telemach), but it didn't worked. For now it is working because I set it up with PDC tool. I guess I will try again on next update of ArrowOS
Do i need to unlock the bootloader to flash the firmware and how do i flash the firmware?
These instructions are for custom roms only. If you have any of the available custom roms installed for Alioth, you already have an unlocked bootloader. The firmware can be applied in recovery.
EldigoR said:
However, the right modem config file (mcfg_sw.mbn) was available, deeply nested in the generic folder.
(\image\modem_pr\mcfg\configs\mcfg_sw\generic\EU\KPN\Commercial\NL).
Click to expand...
Click to collapse
I've been searching high and low for a solution, and this one is so relatively easy.
There is an other way to do this, if you've already a working connection with PDC.
- extract the correct .mbn file from the firmware with your suggestion.
- start the PDC tool
- chose load and then chose the .mbn file
- activate it on the sub0 and sub1
- reboot your phone and check if it still works.
Thanks a lot!!! Because I used the wrong modem config, it reseted itself on reboot. Had to use PDC every time I rebooted my phone. Now with the right profile, it stays active.
Hi, I tried to unlock bootloader by using Qfill. During the process i backed up the AFL-A file and it creates .bin exten. After that i erroneously pressed erase of AFL-A file. Now the problem is i had AFL-A file backup in .bin exten but I don't know how to restore that file using qfill app. Thanks in advance.
syedrafi8 said:
Hi, I tried to unlock bootloader by using Qfill. During the process i backed up the AFL-A file and it creates .bin exten. After that i erroneously pressed erase of AFL-A file. Now the problem is i had AFL-A file backup in .bin exten but I don't know how to restore that file using qfill app. Thanks in advance.
Click to expand...
Click to collapse
This should give you a good idea of how to re-write the partitions!
Sorry, maybe I'm referring to the wrong place, but I did not find another post related to qfill. My question is: Is it possible to replace the APN settings file through QFILL and if so, what is the name of this file? I have lg v50 thanq 5g. Thank you!
Yur11B said:
Sorry, maybe I'm referring to the wrong place, but I did not find another post related to qfill. My question is: Is it possible to replace the APN settings file through QFILL and if so, what is the name of this file? I have lg v50 thanq 5g. Thank you!
Click to expand...
Click to collapse
APN settings can be modified under your network settings.You won't need Qfil or anything for that?What are you trying to accomplish?
Surgemanxx said:
APN settings can be modified under your network settings.You won't need Qfil or anything for that?What are you trying to accomplish?
Click to expand...
Click to collapse
I don't have access to APN settings and *# codes on my Verizon here. conventional methods won't help