First of all, I'd like to say that I performed Anansky's BigStorage upgrade without a hitch on my 850MHz JAM running on Cingular's network. The only concern was that the device was reporting itself as a PM10A instead of a PM10C.
Precautions:
1. Use the write-protect feature on your SD card in the unlikely event that Windows or your PocketPC wishes to write or format it.
2. Use a smaller SD card, as the steps will create a ROM file as big as your card, and it'll take a while to load the file to make changes, update the SD card, etc.
3. Burn a copy of your downloaded ROM file to a CD for safety purposes.
4. Always keep your PocketPC charged either through your PC's USB port, or through a USB-to-AC adapter.
For those who want a quick rundown on how I did it:
1. From the FTP, download NTRW.EXE (version 2.0), ROMUPDATE.EXE, and MAGICIAN_OS1.11WWE_BIGSTORAGE_6.ZIP.
2. With your JAM connected via USB to your PC, disable ActiveSync's connections.
3. Enter the Bootloader and backup your entire ROM to your SD card using ROMUPDATE.EXE.
4. Read the contents of your SD card into a ROM file using NTRW.EXE. (Note that Administrator priviliges are required on your Windows account in order to read/write to the card)
5. Modify the first 416 decimal bytes of the OS1.11WWE_BIGSTORAGE.NB1 (extracted from the ZIP file) by using the first 416 decimal bytes from your ROM file.
6. Write the newly modified ROM file onto your SD card using NTRW.EXE.
7. Enter the Bootloader with the SD card inserted and flash the newly modified ROM to your device.
Notes:
1. I was able to reflash the official i-mate CE ROM (1.11) and Radio, thinking I'd force 850MHz support back into the device in the uncertain event it lost it during Anansky's upgrade. However:[list:44fd36694d]1. The Radio can't be flashed without the CE ROM being flashed alone first.
2. Any reflashing of the Radio or the CE ROM will lose your newly acquired 27MB Storage area. The Device Information applet will report a crazy value for the Storage area when in fact it's totally gone. The only way to restore it is to put your backed up old ROM image onto the SD card and perform the flash from the card.
2. The only way to find out how the hack was done is to look at the different versions of the hack and compare them byte-by-byte to the official updaters.
3. Perhaps one can perform another full SD-to-ROM backup with Anansky's upgrade and compare the files as well, then inject the compatible ROM portions and leave his hack in place.
4. Reflashing any of the ROM portions did NOT restore my model back to PM10C, which leads me to believe that it's outside that region untouched by the official flash utility.
5. I was only able to reflash with the official ROM updaters AND the hacked MaUpgradeUt_noID.exe from the FTP, and while it was in Bootloader mode only.
[/list:u:44fd36694d]
Lastly, I restored my original ROM image in its entirety and will try again sometime in the future to see if I can incorporate the 850MHz ROM into Anansky's hack. It was nice having the extra 27MB free for a short while, but until he comes back or someone else figures it all out, it'll be a risky endeavour in the event of another official ROM upgrade.
ADVANCED USERS ONLY. I take no responsibility for the information I provide below.
I dissected Anansky's ROM to find different sections which I could possibly compare. This is by no means accurate, but I have found certain locations to be of value.
Using the Magician ROM layout on http://wiki.xda-developers.com/index.php?pagename=MagicianRomLayout, I was able to build upon that template. Note that the values start with 80000000, but subtract that value and you get the starting points below.
00A6019C-00AC82D6 = UNKNOWN
00AE019C-00B3319A = UNKNOWN (REFERENCES TO RINGTONES)
00B6019C-00C3F3D5 = UNKNOWN (REFERENCES TO GPRS?)
00CB019C-00F88BF6 = UNKNOWN
00FB019C-014101CF = UNKNOWN
0143019C-0185B015 = UNKNOWN (APPROXIMATELY 4MB... RADIO ROM?)
0187019C-01995D38 = UNKNOWN (REFERENCES TO T9 DICTIONARY)
019E01AC-01CDDE58 = UNKNOWN (REFERENCES TO LDAP, DRM)
01DB019C-01E21343 = UNKNOWN (WINDOWS MEDIA PLAYER COMPONENTS?)
01E4019C-01EF8943 = UNKNOWN (SOLITAIRE / JAWBREAKER)
01F1019C-01F9B0CE = UNKNOWN (REFERENCES TO VPN)
01FC019C-0236A72B = UNKNOWN (APPROXIMATELY 3.8MB, REFERENCES TO NETWORK ADAPTERS, MODEM)
03F80140 = ANANSKY'S ROM CREDITS
03FB819C = MODEL (PM10A)
03F4015C = DATA STRING (UNKNOWN)
03F4019C = SPLASH SCREEN ("HTC MAGICIAN" VOLCANO)
For instance, if you wish to change the splash screen, you could replace the 153,600 decimal bytes starting at 03F4019C hexidecimal with your Splash2.NB file.
I have compared the 4MB block (0143019C-0185B015 hexidecimal) between my 1.11 NA ROM dump and Anansky's and found NO DIFFERENCE. It is possible that this section is the Radio ROM area, due to the size. I have to have the radio.nbk file decrypted in order to confirm.
If there are minute differences, I'll be sure to catch them now. Stay tuned.
I did something similar to find out, what he did. I first flashed Qtek's 1.11, then backed it up on SD card and wrote it to a file. Then I flashed Ananskys ROM and was now able to compare.
Unfortunately we know to few about the internals of the ROM (at least considering what's in the wiki).
BeyoneTheTech,
A question completly unrelated to the big storage ROM. How is it that your JAM has a 850Mhz Processor?
It's 850MHz radio band, unfortunately not CPU speed! I live in North America where the 900MHz is not utilized due to many pre-cellular products hogging up the 900MHz frequency.
As for everyone else, I used a program called WinHex to byte-compare the minimal differences between Anansky's BigStorage ROM file and my own ROM dump file. Bear in mind it's almost in the morning now and I crazily did this at work, so the details will be minimal:
I noticed two byte differences - B8 01 (1B8 hex=440 dec) vs 80 00 (80 hex=120 dec). I did NOT change those because I found it once in the bootloader, so I assumed it might be related to the way it handles the Storage area/Extended ROM.
The second set of differences were where the string "PM10A" was found in Anansky's ROM. Mind you, "PM10A" was also found in my ROM file (in the CE ROM portion), so I took my bytes around the "PM10C" section near the end and transposed it into Anansky's ROM file.
Of course, there was a major differrence in the middle of the two ROM files: the Extended ROM data. I left that the way it was in Anansky's ROM, mostly zeros and some "header"-looking information.
Bottom line is I have what appears to be a fully-functioning ROM file that I flashed successfully onto my 850MHz-band i-mate JAM (running on Cingular's network in the Northeast Americas.) I have little doubt it's not utilizing the 850MHz band, since the byte changes were so minimal between Anansky's WWE ROM and my official NA (850MHz) WWE ROM. My Device Information applet reports "PM10C," of course because I hardcoded it into the ROM, but I also mapped the bytes around it from my original "850MHz" ROM. Oh, and I've got my 27MB back! :wink:
I don't particularly see a problem with having your PM10C device updated with Anansky's ROM. Although the machine will now identify itself as PM10A, people have reported still being on 850MHz cells... so there shouldn't really be a problem there.
The only issue is that now when i-Mate releases upgrades, I'm only able to flash the European and not the North American mods.
What exactly is the method to force a North American ROM upgrade onto a supposedly European JAM? I didn't save the backup which was on the SD card.
As I stated last night and bleary-eyed, there was very little difference between the North American (850MHz) and the WWE (900MHz) versions of the ROM dumps. I believe most, if not all of the differences resided in the Extended ROM. Just the changes noted below worked on my 850MHz JAM.
Using the os1.11wwe_bigstorage.nb1 file...
1. Write FF's into offset 0000028Ch to 00000293h, erasing the T-MOB101 designation.
2. Change the letter A (41h) to C (43h) at offset 03FB81A4h, so it should read "P M 1 0 C."
3. Change bytes 09 2D 4D 27 C7 to 09 2D 4C D1 8E at offset 03FB81DDh to 03FB81E1h. Again, this was near the PM10C designation, and it's unlikely that this code is my IMEI number, so I'm trying to retain as much of my original ROM as possible.
4. Change the splash screen if you wish (see previous post).
Perform a full backup with Sprite Backup or similar program.
SD-Flash the new file onto your JAM and you should be good to go.
Perform a full restore with Sprite Backup, ignoring any ROM upgrade warnings.
If you feel comfortable with hex editing, use WinHex with the ROM files. It opens files fast and can copy and "write" (not paste) the splash screen in one shot.
I am hoping that if someone can easily decrypt the new CE and Radio ROM images, they can be injected into Anansky's ROM dump, while someone who still has their Extended ROM area will be able to extract any new changes or updates in the CAB files.
Shawn_230 said:
What exactly is the method to force a North American ROM upgrade onto a supposedly European JAM? I didn't save the backup which was on the SD card.
Click to expand...
Click to collapse
Just use the "NoID" version of the MaUpgrade EXE found on the FTP, but remember: Any flashing after Anansky's hack will make your Extended ROM/Storage area disappear! Like I stated in my previous post, let's hope someone can create a new xda3nbftool to decrypt the new ROMs and we might be able to either "inject" it into Anansky's ROM dump file, or we can change the necessary bytes, reencrypt, then upgrade only that portion of the ROM to your Magician/JAM device.
BeyondtheTech said:
Just use the "NoID" version of the MaUpgrade EXE found on the FTP, but remember: Any flashing after Anansky's hack will make your Extended ROM/Storage area disappear!
Click to expand...
Click to collapse
BeyondtheTech, I had an 900mzh version but I am living in US too. Actually, there is a very simple solution w/o going thru the hacking of the rom (But it's good someone can experiment how Anansky's did it so that we could do it for the future rom update).
1. Grab the latest USA rom from imate.
2. extract it w/ Winrar and U will get 3 nbf files.
3. Keep the radio_.nbf and remove the other 2
4. Use the no id version of MaUpgrade and it will only update the radio
5. U radio is 850mzh version and U still have the big storage
FYI, I don't know if you actually tested your sets, because I did flash just the alleged "USA" radio portion on my 850MHz JAM and I did lose the BigStorage area entirely, which is why I said that any subsequent flashing will do just that.
BeyondtheTech said:
FYI, I don't know if you actually tested your sets, because I did flash just the alleged "USA" radio portion on my 850MHz JAM and I did lose the BigStorage area entirely, which is why I said that any subsequent flashing will do just that.
Click to expand...
Click to collapse
Of course, I did.
BeyondtheTech said:
ADVANCED USERS ONLY.
00A6019C-00AC82D6 = UNKNOWN
.../...
03F80140 = ANANSKY'S ROM CREDITS
03FB819C = MODEL (PM10A)
03F4015C = DATA STRING (UNKNOWN)
03F4019C = SPLASH SCREEN ("HTC MAGICIAN" VOLCANO)
I have compared the 4MB block (0143019C-0185B015 hexidecimal) between my 1.11 NA ROM dump and Anansky's and found NO DIFFERENCE. It is possible that this section is the Radio ROM area, due to the size. I have to have the radio.nbk file decrypted in order to confirm.
If there are minute differences, I'll be sure to catch them now. Stay tuned.
Click to expand...
Click to collapse
Following to BeyondtheTech post, I'm now shure that the so called 'big storage' is located between address:
023c0190 : 03f40190 (about 27 MB)
I've also determined that every 256 kB (+40000h), this 'virtual disk' include something similar to a 'sector header' conform to:
f0 f0 f0 f0 00 00 00 00 96 f2 e7 10 db d3 00 fc
Click to expand...
Click to collapse
this string is present at address:
02400140h, 02440140h, 02480140h, 02480140h .../...
03f00140h, 03f40140h
For checking the validity of my theory, I've copied about 15 MB of different files, before making a backup of my Qtek S100. It's confirm that the data are occupying this space.
Because, I'm normaly working on a french OS version, I need all accentuated; and diacritic characters to answer my mail. So my purpose is now to 'reverse engeneer' the Anansky method to include this very usefull 'big storage' on a french based OS.
So, I've merged all content of my original v1.11 French OS UpGrade from address 00000000h to 023c0100h... This personaly cooked OS is working, and all is in french... but 'no-big-storage' available unfortunately.
So, in the next step, I've tried to undestand, how 'virtual storage' is working under Qtek S100. Back to my original OS, with small 7 MB storage. On the hexadecimal point of view, nothing more than, with the Anansky backup version, except that the virtual disk is smaller... Everything is in order, according to my theory...
But because the 'big storage' is not even visible, my conculsion is simple: "the solution is in the 'registry', but I've not yet been able to go through the mystery:
HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\VDisk
"Name"="Extended_ROM"
"Folder"="Extended_ROM"
.../...
[HKEY_LOCAL_MACHINE\Drivers\Active\43]
"Hnd"=dword:0068e3f0
"Name"="DSK8:"
"Key"="Drivers\\VDisk"
"ClientInfo"=dword:00000000
.../...
[HKEY_LOCAL_MACHINE\Drivers\VDisk]
"Key"="Drivers\\VDisk"
"WindowBase"=dword:a2c00000
"Size"=dword:01300000
"Folder"="Extended_ROM"
"DisableInt"=dword:00000000
"OnBoard"=dword:00000001
"Dll"="VDISK.DLL"
"Index"=dword:00000008
"Prefix"="DSK"
"Profile"="VDisk"
.../...
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\FlshDrv]
"FolderName"="Storage"
Click to expand...
Click to collapse
Close to all references in the registry seem to be dedicated to the Extended_ROM (about 19 MB) that can become visible, but not writable... until yet.
I've found only one reference to the 'Storage' folder (about 7 MB on my QTek), but I don't understand how the OS know it's type, size, location, etc. Another thing is shure: the registry is not directely visible in the backup. I suppose that this file is compressed in ROM, and decompress to Ram for working (all modification disapear in case of har reset).
Lost of questions... :?:
Regards,
Thierry
To easy patch any ROM... folow this link ;-)
http://forum.xda-developers.com/viewtopic.php?t=22582
I am not sure it's in the registry as I did a byte compare of my backed up ROM (which was the 1.11 NA 850MHz from i-mate) to Anansky's (1.11 WWE) and found that the there were two sets of bytes that were different (changed?) in the bootloader area as well as the CE ROM, and of course, the 27MB chunk of data for the Extended ROM.
I think the bootloader may have something to do with the way the memory is set up.
The bytes that were different were in both places were B8 01 vs 80 00. 1B8h=440 and 80h=128, if that means anything. There were no other changes in the Radio or CE ROM areas, which leads me to believe that the 27MB area is just formatted differently (perhaps the start of the 7MB area was pulled back to the beginning of the Extended ROM area).
The only remaining change was near the end where it has the "PM10x" designation," but I doubt that has anything to do with the BigStorage area since I used his bytes and tried my bytes with no difference.
If you feel bold enough, you can mess with these two bytes (try a value in between) to see if it enlarges the 7MB storage space, corrupts it, makes it writable, etc.
pigot,
If you're willing to try this...
After you've injected your French ROM into the NB1 file, use a hex editor and change the following bytes:
On or around 00007E32h, change B8 01 to 80 00.
Do the same at 0211E32Eh, change B8 01 to 80 00.
Leave Anansky's changes in the Extended ROM and Storage area as well as the end of the file unless you want to call your device a PM10x.
SD-Flash it and tell me if you have the 27MB of Storage free with your French OS.
You are in the good way :lol: ... Those bytes (hB8 + h01 to h80 + h00) are the key. But not always they are in the same site in all the ROM's.
Bye. 8)
Seems to work great for me over the last couple of minutes at least! Upgraded a 3 day old UK o2 qtek s100.
Thanks a million.
BTW - what software is stored in the extended rom that we lose?
Vijay
MKS said:
You are in the good way :lol: ... Those bytes (hB8 + h01 to h80 + h00) are the key. But not always they are in the same site in all the ROM's.
Bye. 8)
Click to expand...
Click to collapse
Well, the application developped by MKS is a great job. It works perfectly for me on a v1.11 Fr... The process is very simple, and really accessible to even 'medium range' users. Sounds pretty good, isn't it?
Omho, the 'anansky trial' is over, and the big winner is MKS.
Thanks alot,
Thierry
I don't know how to link to another thread, but I've got blackberry working on the WM6 rom. Basically this method can be used to make it work on ANY rom... If you want to find out how, there is a thread started by c0rnholio; he's THE person who cracked it for the Universal; I just followed his method for the Wizard.
----------------------------------------------------------------
It works!!!!!!!!!
I compiled a new nbf file, flashed the phone, changed the AKU (if you don't do this, BB will connect but not pull any emails).
In the log it used the same data as with my previous rom (5.1.195, bb version 2.2.16 and AKU 0.2.0.0).
All thanks to c0rnholio. Everybody else with a wizard (and rom WM6...):
Use typhoonnbfdecode_v5 to extract the 800310000-os.nb
Then use HEXEDIT to change:
05 20 A0 E3 02 10 A0 E3 A5 EF A0 E3
into
05 20 A0 E3 01 10 A0 E3 C3 E0 A0 E3
Then use nb2nbf_tornado to recreate the nk.nbf. Put in:
Model: WIZARD
Language: WWE
OEM: empty
Version: empty
CID: Empty (very important)!
Select File 1 the changed 8... .nb file. Select OS and make sure you change the 82040000 (automatically defaulted) to 80040000.
then flash the nk.nbf to your phone, change the AKU and that's it!!!
Awesome News!
Hi,
This is awesome, no more carrying two phones, ha,
Just have a question is there a tutorial on how to use typhoonnbfdecode_v5. I fool around with it, but still wasn't comfortable with what I was doing? Building back the nk.nbf I have done before so that's okay. Would you be kind enough to post up a tutorial or some pics so all of us to benefit this great finding.
Thank you for posting this.
Tutorial
Dude, I'll try and build a tutorial with pictures etc one of these days.
But using typhoonnbddecode_v5 is very easy and most information is on the Development forum in this post (read all):http://forum.xda-developers.com/showthread.php?t=294218&page=5
in the command prompt:
typhoonnbfdecode_v5 -x nk.nbf
to extract the nk.nbf file.
Thanxs Man.
Yeah got it to work, I'm using Vista and for anyone that might run into the same problem I had, you have to run Command Prompt in Run as Admin or it won't won't.
Quick Question.
I'm at the part rebuilding my nk.nbf but my default is 82040000 opposite to what you said, so and so I read before in another post the default is 82040000 and you should change it to 80040000, got that information from ..the guilde to install 2.x rom in a CID locked G3-G4. Can you please confirm me on this. Hope I explained myself right. Also you mention after you flash change AKU? sorry I dont' know what is AKU, can you explain, sorry to be such a noob.
Is there an already prepared ROM available?
One of you guys that has already done it with Most Beautiful ROM:
Would you be able to make it available to us via rapidshare or torrent?
Thanks!
Sure would be nice
My employer will ONLY let me sync to Blackberry, and I hate the things. I'm not willing to give up my wizard, and I'm not educated enough to get this fix right. I'm barely hanging on when the guy said blackberry worked. Could somebody make a cab? Please don't flame me if that is a stupid request.
A rom image will do
If it is not easy via a CAB install, maybe someone would be as kind as to provide a Rom image of the patched OS...
Pretty Please...
I have really tried to follow this discussion through the various threads mentioned and I start drooling and cussing madly after about four minutes and twentyseven seconds. I just don't have the background/education to make it work. I'm not a moron. You guys are just way smarter about this stuff...
A little help would be greatly appreciated.
Hello!
I bring to your attention a small script to change the size of PagePool directly on the device.
The script allows to replace the size PagePool From 2.00 to 16.00th mbyte without a reflash of the device and loss of data.
After work of a script it is enough to make a soft reset to the device.
In a script is implemented the algorithm of automatic search of the address of offset and check result of search with use of check value on algorithm MD5 . In this mode every possible checks are made so much what kill the device practically not possible.
Also there is a possibility of instructions of own displacement of value of the size PagePool In a case when automatic search cannot find out it. In this mode value to the specified address is checked only. And if it not in the range of values of the size PagePool from 2 to 16, script also refuses to make changes to a device insertion.
The script is checked up with several firmwares and devices.
If program can't autodetect offset value of PagePool, generate "dev info"
and provide it to me. Im add your device in autodetection feature.
Thankful in advance for responses about work of a script and the help in perfection of this.
Screenshots and script are applied
P.S. Sorry for bad english
latest version available at ftp://intruder.spb.ru/PPSmartChanger.exe
First of all thank you for your hard work!
I read everywhere about this "PagePool". Can i ask what's this? And which PagePool is more wise to use?
TIA
If I correctly have understood you, I answer
PagePool it is area which it is used by system for caching various information. The size of accessible RAM depends on the size of this area for. As a rule this value selects everyone under itself individually. Someone uses the big programs which is necessary a lot of memory, and someone a much small programms.
As the program allows to change this value without loss of data, it is possible to experiment.
If has worked address autodetection that all it should be good.
If has not worked, I need info about your device and firmware to try add your device to autodetection.
Thanks for this sweet app....
Now I can change the pagepool on the fly... even though I wonder how many times I will actually change it...
You can change the size of PagePool as many times as you need without any limits.
Version updated:
1. Improved method of info retrival from device.
2. Added multidevices support.
3. EXPERIMENTAL: Added support of WM6 on FS LOOX C550 (can't test on device, my device HTC Touch)
So, what would be the best size for the Touch? I know it should be smaller, I've read 4MB somewhere but is that best or at least better than original?
I'm using BatteryStatus with enabled CPUScaler and I noticed when I change the PagePool size to 4 Mb, TCPMP player works on higher frequency (299 MHz, Boost) instead of 247 MHz (Max) with 8 Mb PagePool size.
So if PagePool size is 4 Mb and less we have low productivity.
I found that 6 Mb is good size. The productivity is the same as with 8 Mb and free memory bigger for 2 Mb.
Version updated.
Hi shark... It's not working on my Touch. Firmware using is 1.11707.1B WWE.
Swiftblade said:
Hi shark... It's not working on my Touch. Firmware using is 1.11707.1B WWE.
Click to expand...
Click to collapse
Hi! Please use new version and if it not work, build info for me (option in menu) and attach to reply
Latest version can be accessed at ftp://intruder.spb.ru/PPSmartChanger.exe
the link of your app doesn't work anymore...
can you upload it to a different server please.
thanks
It did work on mind.
It said Dump size mis-matched.
Try built Development Information.
It also failed and sais Some **** happened!
Don't know what is next. ROM I used is the 55Meg Big Storage ROM without Extended ROM found in this forum.
jychan28 said:
It did work on mind.
It said Dump size mis-matched.
Try built Development Information.
It also failed and sais Some **** happened!
Don't know what is next. ROM I used is the 55Meg Big Storage ROM without Extended ROM found in this forum.
Click to expand...
Click to collapse
Same to me
Please wait while tool locate PagePool setting offset
_______________________________________________________
Started at 10:50:08.39
> Initializing... done
> Reading ROM info... done
> Dumping part of ROM.. ERROR
> Locating PagePool setting. skipped
> Checking MD5. skipped
Finished at 10:50:41.82
_______________________________________________________
Size of dump is mismatch
Press any key to continue . . .
Click to expand...
Click to collapse
But building of debug info worked.
Don't know how to contact you at 4PDA.ru since my russian is very rusty (cannot even read any of these words).
So I post the log here
My ROM is1.11.407.1B.GER (original german HTC Touch)
I have the same problem with jychan28
ROM: 1.11.721.2B WWE
Radio Ver: 02.93.90
Hi,
I was wondering how i can change the pagepool size when i'm cooking a rom?
I've been searching and searching but didn't find anything to change the touch's pagepool.
Gr. bram
New version at ftp://intruder.spb.ru/PPSmartChanger.exe
bram_smulders said:
Hi,
I was wondering how i can change the pagepool size when i'm cooking a rom?
I've been searching and searching but didn't find anything to change the touch's pagepool.
Gr. bram
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=323269
If any **** happens, download new version
It buil development info in C:\PPSCDev.
sorry...
_________________________________
> Checking........7z.exe: No such
file or directory
.. ERROR
Tool might be broken
Execution aborted
Press any key to continue . . .
Click to expand...
Click to collapse
the file I downloaded is also only 229kB instead of 295kB of 0.37a
Sorry, it's my fault. Script updated, try again.
I want to restore a backup after i played with some ROMS, but WP7C is giving me Error 8000ffff
on the console i see:
05.11.11 00:07:43 [0x0-0x4e04e].com.microsoft.Windows-Phone-7-Connector[1641] 2011-11-05 00:07:43.010 NOTE [A0ABA540] Sync 0-1-1-0.0545
05.11.11 00:08:03 [0x0-0x4e04e].com.microsoft.Windows-Phone-7-Connector[1641] 2011-11-05 00:08:03.325 ERRR [B0103000] DU Error: restore transfer operation async status = failed
05.11.11 00:08:03 [0x0-0x4e04e].com.microsoft.Windows-Phone-7-Connector[1641] 2011-11-05 00:08:03.325 ERRR [B0103000] Async Op Status Error opCode 00000009 status 00000003 percentage 255 moduleid 00000005 errorCode 8000ffff
does anyone know how to force a restore on mac?
or how to restore the "Data.xx.dat" with Zune, as the mac does not create the accompanying hash files
Same problem here with my Lumia 800 on a MBP. Have you been able to solve this problem?
Well if you've been playing with ROMs, it's most likely because the ROM on the backup is different than on the phone and they aren't compatible. I think this is why custom ROMs don't have cab updateability, of which backups are cabs. As far as I know, there isn't a solution =/
Good luck though!
Hmm thanks, well I didn't update my phone before I tried to restore it though... Anyway having a "clean" installation isn't so bad once in a while..