Develop Bugs

"Error accessing image files"..?

Hi all!
When I try to read an extended ROM image with the softworkz ER2003Edit tool, I get an error-box saying "Error accessing image files", no matter which ROM I try to load (have tried several operators/countries). What am I doing wrong?
Thx.
/Joe72

I've got the same problem.
anyone any idea pls????
thnx

i had the same problem, i kept on messing with the application and eventually was through.
Reason :
when you open er2003edit and click on file and then open rom image a window pops up, over most of us tend to go directly to the file which we want to open, BUT in actual you are suppose to change the FILES OF TYPE in that window at the bottom and select "WM2003 EXTENDED ROM (ms_.nbf)" and then open the file.
this will solve the issue FOR SURE
regards
jeetz

zairyaab said:
i had the same problem, i kept on messing with the application and eventually was through.
Reason :
when you open er2003edit and click on file and then open rom image a window pops up, over most of us tend to go directly to the file which we want to open, BUT in actual you are suppose to change the FILES OF TYPE in that window at the bottom and select "WM2003 EXTENDED ROM (ms_.nbf)" and then open the file.
this will solve the issue FOR SURE
regards
jeetz
Click to expand...
Click to collapse
it's working.
thnx 4 the tip
cheers :lol:

any time ...by the way if anyone of you guys want downloads links or ne thing on this forum or for any softwares follow http://forum.xda-developers.com/viewtopic.php?p=81950#81950
cheers
jeetz

Asus A639 briced during upgrade

Hi ppl,
I just bricked my Asus A639 while trying to upgrade
to WM6. Probably my own fault, the SD was FAT32
rather then FAT16 and I noticed too late.
Also, I was stupid enough not to create a backup
of the WM5 first so I'm really stuck here.
I have been reading the forums on this but many topics
are mixed up ; they discuss migrating to another language
mixed up with rescueing the device.
I am not interested in switching language. I have read
that it is possible to force a WM5 image onto the device
but there are two issues ;
1. I don't fully understand how to do it
2. I don't have a WM5 image
So I guess I have two questions ...
1. Can anyone provide me a Dutch Asus A639 WM5 backup
2. Can anyone tell me how to get it onto the device.
Tnx,
c0r3

Got it fixed. Many tnx goes to cmonex !
There was a post some time ago which described how to recover from
a crashed upgrade ....
http://forum.xda-developers.com/showthread.php?t=308611&highlight=asus+wm6+update&page=19
I started of by downloading the official WM6 update from the Asus
site. I renamed the Update.img to A639_K733.DIO and tried to get it
onto the device. Although it did load, the PDA still wouldn't get past
the Asus welcome screen.
It appears the .img file from the update package contains too much
for this to work.
cmonex said:
find MSFLSH50 signature (search for string in a proper hexeditor!!) in the file, then go back 512 bytes and cut everything until then.
so the remaining file will have the MSFLSH signature at offset 0x200 (i.e. 512).
Click to expand...
Click to collapse
So I tried but could not find the "MSFLSH50" string in the .img file. Tried
several different hex editors, no luck.
cmonex said:
ok, it is possible it is a XOR'd file, some ASUS updates are like that.
Click to expand...
Click to collapse
Once I got the correct file from cmonex ;
1. Formatted SD FAT16
2. Rename cmonex's file to A639_K733.DIO
3. Copied file onto the SD
4. Inserted SD into PDA
5. On PDA : press+hold power+enter+reset
6. PDA enters bootloader mode and copies the file into the ROM
7. Press reset on PDA and all boots just fine although it takes a while before
it passes the Asus welcome screen. This is only the first time after the
download however. Reboots after then go as they should normally go.
The hard part in this sequence seems to be to find a decent ROM file.
Once you have a file that contains the MSFLSH50 signature it pretty
straight forward.

as someone sent this link to this thread to me in PM just now I thought I'd clarify some details..
a sample english .DIO is available from my server, but link is not public - you can PM me
otherwise, to obtain a .DIO, just make a backup of your ROM with pdocread while PDA is still working. if help is needed with that, please post the output of the command "pdocread -l"

cmonex said:
as someone sent this link to this thread to me in PM just now I thought I'd clarify some details..
a sample english .DIO is available from my server, but link is not public - you can PM me
otherwise, to obtain a .DIO, just make a backup of your ROM with pdocread while PDA is still working. if help is needed with that, please post the output of the command "pdocread -l"
Click to expand...
Click to collapse
can somebody give my a link to .DIO file

Same problem: need Dutch .DIO
Hello there,
I have exactly the same problem as described here. I also tried a rename of the
Update.img to A639_K733.DIO which did load and was written in the ROM but the device still "hangs" at the blue "welcome" screen.
Would it be possible to obtain the "correct" .DIO from one of you guys? That would help me a lot! Thanks already in advance!
My system is originally Dutch and I would like to stick with it, so I would need a Dutch .DIO, but since I have a backup of my old system made with SpriteBackup, I guess (or better hope), also an English .DIO will do.
Again, thanks in Advance,
Andreas

I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar
now people can stop PM'ing me, this link should work fine

Many thanks to Cmonex,
With your help and this magic DIO file, my A639 is not dead and running again !

Hi there,
I have reflashed my A639 with cmonex file posted abowe it boot now ok but is stuck on the align screen and it not detect when i press on the cross. I think it is not defective because when the screen enter in save power mode if i touch the screen it become active. What can i do ? Thank you very much for any sugestion !

cmonex said:
I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar
now people can stop PM'ing me, this link should work fine
Click to expand...
Click to collapse
You are the man. Thank you for the share of the ROM. Saved me huge headache.

ASUS A639 fix
Israeli users (hebrew support): this image is not the israeli original ROM image supplied by Ronlight! it does not contain Eyron Hebrew support!
Unless you already had a WM6 w/hebrew support img on your A639 flash memory, after flashing this rom img you will need to install a new third party hebrew support software!
==flashing this img can void your warranty==
If anyone still need some help fixing a bricked Asus, just PM me.
Cheers,

cmonex said:
as someone sent this link to this thread to me in PM just now I thought I'd clarify some details..
a sample english .DIO is available from my server, but link is not public - you can PM me
otherwise, to obtain a .DIO, just make a backup of your ROM with pdocread while PDA is still working. if help is needed with that, please post the output of the command "pdocread -l"
Click to expand...
Click to collapse
Hello cmonex,
can detail(retail) you how to make a protection(saving) of the rom of the PDA with " pdocread " and tranformer files got back there .nbo

Hello cmonex,
can detail(retail) you how to make a protection(saving) of the rom of the PDA with " pdocread " and tranformer files got back there .nbo

I know it's an old post, but I got a bricked a639 that I only can get the bootloader to run. USB doesn't work, only updating with a A639_Kxxx.DIO works.
cmonex mentions in the post that "I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar". The A639_V10733.rar file on rapidshare however contains a file called A639_V10733.NB0 and not a *.DIO...
Since I can only update using a A639_Kxxx.DIO on my sd card, does anyone have a *.DIO available? I've been searching the internet for quite a while now, but can't find a DIO for download anywhere...

Greetings Ladies and Gents,
I believe I'm having a problem here of the same sort with an Asus A639. In a few words, I wanted to upgrade WM6 to a newer version (got it from Asus support site) and the installation crashed (the message said "could not read SD card"). After reset my PDA got stuck to the Asus welcome, blue screen
Now, I followed the lead, from previous posts but got real fast, completely lost.
I also tried several files provided but did not work. The last shown on display line reads "Waiting for download !".
I am using the english version for WM6.
Can someone help me out with a complete description for what I need to do?
Thank you
Regards
Forja

cmonex said:
I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar
now people can stop PM'ing me, this link should work fine
Click to expand...
Click to collapse
Hi cmonex.
One question about your uploaded file: Am I going to unrar the file then rename A639_V10733.NB0 into A639_V10733.DIO ?
Thanks!

ondeugd said:
I know it's an old post, but I got a bricked a639 that I only can get the bootloader to run. USB doesn't work, only updating with a A639_Kxxx.DIO works.
cmonex mentions in the post that "I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar". The A639_V10733.rar file on rapidshare however contains a file called A639_V10733.NB0 and not a *.DIO...
Since I can only update using a A639_Kxxx.DIO on my sd card, does anyone have a *.DIO available? I've been searching the internet for quite a while now, but can't find a DIO for download anywhere...
Click to expand...
Click to collapse
Hi, how did you do it?

wont work
nervoptik said:
Hi cmonex.
One question about your uploaded file: Am I going to unrar the file then rename A639_V10733.NB0 into A639_V10733.DIO ?
Thanks!
Click to expand...
Click to collapse
I've tried this, and wont work
I've changed the extension from NB0 to DIO.
After holding power + reset + enter, a gray screen appears for 2 seconds and it's written "FAT 16" ... and that's it!

nervoptik said:
I've tried this, and wont work
I've changed the extension from NB0 to DIO.
After holding power + reset + enter, a gray screen appears for 2 seconds and it's written "FAT 16" ... and that's it!
Click to expand...
Click to collapse
Hi @ all!
I have the same problem (downloaded file from rapidshare, renamed to DIO and after holding power+enter+reset for 2 seconds fat 16 and then freezed asus blue welcome screen), can anybody please help us ? (my device language rom was italian)
Bye

Asus A639 upgrade problem...
Join me in the remarks, I have the same problem: "after holding power+enter+reset for 2 seconds fat 16 and then freezed asus blue welcome screen"
What's this exactly? I did something wrong, or the PDA does'nt work properly?
I downloaded the file that Cmonex published on Rapid, but are'nt working.
I tried to upgrade, because it does not load the operating system ... only the blue screen appears at startup.
Any idea what might be the problem?

nyestegabesz said:
Join me in the remarks, I have the same problem: "after holding power+enter+reset for 2 seconds fat 16 and then freezed asus blue welcome screen"
What's this exactly? I did something wrong, or the PDA does'nt work properly?
I downloaded the file that Cmonex published on Rapid, but are'nt working.
I tried to upgrade, because it does not load the operating system ... only the blue screen appears at startup.
Any idea what might be the problem?
Click to expand...
Click to collapse
I think I had the same problem ,
try renaming the file on the SD card to exactly A639_K733.DIO

Asus P552w/P565 ROM Decryption !!

For all those who are struggling to extract the contents of the '.abi' file for P552w and P565, here is a good news !!
I found these tools somewhere on a non-English forum, while searching for the decryption tools.
It is a command-line tool that directly works on the '.abi' file, and produces the '.nb0' file.
Part02.nb0 is the OS Image and Part03.nb0 is the ExtROM.
Let me know if you face any difficulties. I have used it on my P565 and successfully dumped the ROM (using imgfs tools on the the OS image). Working on the kitchen now....
Hoping for someone to come up with a kitchen for P552w/P565 soon...lol
cheers,

We also have decrypted P565's rom,and now the problem is how to encrypt the rom.Do you found any tools to encrypt it?

gerry86 said:
We also have decrypted P565's rom,and now the problem is how to encrypt the rom.Do you found any tools to encrypt it?
Click to expand...
Click to collapse
Well, decryption and encryption are both resolved. The only issue is to find where the IMGFS checksum is stored, and update the new checksum there. The '.abi' ROM Header is encrypted using some complicated encrption( not XOR ), and I have not been successful in decoding it as of now.

I see you're all experts here. Maybe you can help me.
I just want to know if it is possible to upgrade my italian ROM with an english one (P552w)?
If not I guess I can throw away my Asus while I don't speak Italian
Thanks for your help,

VanGog said:
I see you're all experts here. Maybe you can help me.
I just want to know if it is possible to upgrade my italian ROM with an english one (P552w)?
If not I guess I can throw away my Asus while I don't speak Italian
Thanks for your help,
Click to expand...
Click to collapse
Sure buddy, no need to throw it away...
Just follow these simple steps :
1. Ensure that your Storage card capacity does not exceed 2GB and is not corrupt.
2. Connect the device using activesync and wait till the connection is established.
3. Go to file explorer on your PC and enable the option to display hidden files and folders.
3. Take your English ROM ( .exe file) and execute it from your PC.
4. Press 'next' till you see the error message that the ROM is not meant for your device. Wait !!
5. While this message is still being displayed, go to the folder which contains your ROM ( .exe file). You will see a file called 'tmp_rom.abi'. Rename this file to 'GM5.abi'.
6. Now close the error message screen.
7. Copy 'GM5.abi' to your Storage card.
8. Now Press the "Navipad down"+ "Reset" buttons and keep them pressed until you see the reboot screen.
9. That's it. The ROM flashing process will begin automatically.
10. Do not press any button till the ROM flashing is in progress. The device wil reboot automatically.
Enjoy your new English ROM.
Disclaimer : Hope you are aware about the risks associated with the ROM flashing process.

First of all, thanks rishi for your help, but in my case something doesn't work.
I get to the boot screen where it says that it can not find the file (but it is on the card).
I followed all the steps (including 1GB storage card) but always the same, no success.
Is it possible that this is because of my Asus which was I suppose unlocked before I bought it. It has an Italian mobile provider logo on boot screen?
Do you have any other solution for my problrm?
Thanks again for your effort,
Van Gog
Found a solution!!!!
The name of *.abi file must be the same as the name of an *.exe file!
WOW!
Thanks a lot, you saved my Asus!!
Greetings,
VanGog

It should be GM2_name.abi and don't forget to clear hidden attribute.
For me it works also on 4GB card.

rishi, you said that "decryption and encryption are both resolved", is it using the same tool? I cannot say I got it...

weiqiix,
You may use this tool: http://forum.xda-developers.com/showthread.php?t=511158

Thank you very much, I'll test it right now.
Then I could even understand what (and how) to do with those *.nb0 files,
and who knows, I could understand my p552w's internals

If anyone can fix the camera and video problem that will be perfect!

[Help][D855]Nt-code changed by mistake in hidden menu

hello,
I had this message, cant find matches cost for NT code mcc/mnc[], subset[],
I found by chance the NT-code section in settings, version info. by mistake I changed it from:
"0","FFF,FFFFFFFF,FFFFFFFF,FF" to "01","FFF,FFFFFFFF,FFFFFFFF,FF"
since then I can't modify this anymore beceause when i want to enter to the settings in hidden menu, my phone just freeze and terminate settings process.
Please help me, is ther any way to reset this NT-CODE with ADB?
thanks a lot!

Can you opened with file explorer in etc>cust>cust-path-mapping.cfg ?
Is it same with what's your need ?

Solved
I just upgraded new marshmawllow ROM, I was able to change my NT CODE easily via hidden menu and correct it to match EURO-XX.

majorak said:
I just upgraded new marshmawllow ROM, I was able to change my NT CODE easily via hidden menu and correct it to match EURO-XX.
Click to expand...
Click to collapse
Could u be so kind and write for me step by step what did u do??

dboo said:
Could u be so kind and write for me step by step what did u do??
Click to expand...
Click to collapse
+1

[GUIDE] How to fix Windows Update Issue on CU builds - Error 0x80070273

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.