Storage area missing after mkbigstorage

[ppc4]

I would be absolutely grateful if someone has any type of answer to this problem. Won't go in to a lot of detail as to how many attempts have been made but will suffice to say that this has been a major time sink.

The upshot of the problem is that the "Storage" area has completely disappeared from the MDA Compact and the following summarizes the attempt to recover and how I wound up there:

1. Attempted mkbigstorage upgrade to MDA Compact.
2. All attempts failed at reloading modified mkbigstorage nb1 image from SD card at 63% of load.
3. Performed straight load of WWE 1.12 image, then performed d2s via "romupdate" to SD card. This was 100% successful. Attempted bootload of same exact ROM (without even doing anything to it or even removing it from the device) and received load error at 63% again.
4. Have loaded several different versions of ROM (nbf files) and wind up with the same result of the Storage area completely missing from MDA Compact.
5. Any attempt at "any" nb1 load from SD card gives error at 63% of load unless the specific d2s command of "d2s 80040000 023C0000" is provided. This strictly backs up the operating system and nothing more. (no ext_rom, radio, etc.). But after applying the mkbigstorage changes to this rom and reload (which is successful by the way), the Storage area is still missing from the unit.

Most ROMs that have been located via the nbf file type, work ok (1.03, 1.06, 1.11, etc.) but still don't show the Storage area any more after a load.

It seems as if the nbf file type ROM loads don't overwrite/correct the problem I'm experiencing with the original Storage area.

I have read through (I think) every single posting about mkbigstorage and can't seem to locate any reasonable solution to my problem.

The ideal correction would be to get the MDA Compact back to a state where the Storage area is recognized by the O/S, then go from there.

The unit is usable but it takes about 3 minutes for a soft reset. After which, the Storage area doesn't show within the system or as an alternative for an app install during ActiveSync.

I originally backed up the ROM that was already loaded before this whole mess began and have attempted to reload but an error results about not being able to update Section 1.

Any information at all would be most welcome. I am not real enthusiastic about having to take this thing to a service center. Being in the US, most of our T-Mobile centers would just look at it and wonder what the heck it is.

Please provide any insight that might help.

Thanks.

[nishadks]

The whole problem is with the area address of ROM you used while dump with d2s. I have also faced the same issue and only way to solve the same by restoring from your original backup or dump the rom from another magician using d2s only and restore the same your magician. Do dont use any address locations. Please remember while doing the dump backup for BigStorage use only D2S no other address locations.

[ppc4]

My initial SD backup with d2s (first step performed before all this started) was only using d2s with no address. It performed a 100% backup of my original rom and I still have it.

When attempting to put the original ROM back on, it fails with the "Address=1 not allowed" error. I'm not sure if another copy of the ROM from another Magician would help but I'm willing to try just about anything.

Are there any tools available to clear out parts of the ROM completely?

[ppc4]

A little more information on current standing:
1) Tried to load original ROM and received "Section=1 not allow update".
2) I then backed up what was already loaded on the compact (1.12).
3) Copied the first 416 bytes in to the original ROM file.
4) Tried to reload ROM. This time it let me begin the flashing but failed at 63%.
5) Did the same procedures as above but this next attempt I ran the mksBigStoragerENG.exe program, then created a new ROM file.
6) Tried to reload this new ROM and received a fail at 63% again.

I'm stumped at this point. It won't take the original ROM at all.

Any suggestions folks?

[nishadks]

Use a backup restore from another magician. I think this is the only way to do it. But while do the same never backup device information from the another magician.

[ppc4]

The original ROM was T-Mobile 1.01. I have attempted to perform an SD load of both my original backup (made with just "d2s") and a downloaded T-Mobile 1.01 .nb1 file.

Both files have had the first 416 bytes replaced with the current ROM information (tried both with and without).

When loading, I either get "Sections=1 not allow update" or if I'm lucky enough to get past that, I then get download fail at 63%.

If a straight load (using .nbf files for WWE 1.12) is performed via the standard update utility, all works fine but after reset, the Storage area is still gone.

I'm not sure if the Storage area can ever be recovered after a failed attempt at mkbigstorage. Many hours have been put in to this and I can see no solution at this point.

As stated earlier, the unit is still usable with the straight 1.12 load but it takes about 3 minutes for a soft reset, then the Storage area is still missing though.

Has anyone seen this at all and can point me in the right direction? I'd be happy at this point to get it back to the way it was (1.01 with the Storage area viewable) but can see no way to revert the ROM back to it's original condition.

[ppc4]

Thanks for the information about possibly loading a different nb1 file.

I have tried both my original backup and a different nb1 file backup from the ftp site. After getting past all the device information on both loads, both still come up with a load failure at 63%. This has been the problem all along. The Magician will never load anything past 63%.

I am finally convinced that the internal ROM is somehow corrupted beyond repair via just standard ROM loads or backup/restores.

Not sure what to do at this point but try to get it to a dealer.

[ppc4]

I think I have finally located the problem with why my flashes fail and the Storage area is missing. This section of the ROM seems to be messed up:
82400000-82c00000 00800000 backup area ( contacts, calendar, etc )

This is the internal Storage area of the ROM. A standard ROM update doesn't touch this area so this is why I'm still having problems after a GUI/USB based upgrade.

I have done a d2s on all sections of memory individually and this is the only one that fails miserably.

Anyone have any idea of how to restore this or at least clean it up somehow?

[patjack]

I never touched BigROM and my magician's internal storage is missing also.
I have tried hard resetting, and re-flashing it with the original 1.11.00.WWE.
But still no luck.

Any ideas guys? :(

[ppc4]

I sure wish I knew how to fix this storage folder missing thing. I've reflashed the ROM at least 10 times with different nb1 files and all fail at 63% of load. Digging through all the memory locations for everything, this is approximately where the internal flash drive is. The OS always loads but nothing after that.

Load order of a flash:
Bootloader
OS
Storage Folder data
External ROM
Unused section
bootsplash
Device Version and type info

I can't believe an nb1 flash doesn't fix this problem though. Please post if you can find any more information.

[ppc4]

I never touched BigROM and my magician's internal storage is missing also.
I have tried hard resetting, and re-flashing it with the original 1.11.00.WWE.
But still no luck.

Any ideas guys? :(

Are you flashing using the USB and GUI method or using an SD card and bootloader?

[patjack]

I am not a pro.
I only ran the EXE I downloaded from O2 website.

[ppc4]

I am not a pro.
I only ran the EXE I downloaded from O2 website.

I'm not a pro either. :) I've just been digging in to all of this over the last couple of weeks and made some determinations of how the upgrades actually happen and which does what.

I was just curious how you did the upgrade. Since you used the standard EXE for the install, that will only update the OS ROM, Extended ROM and Radio. The Storage folder isn't touched at all with this upgrade. The manufacturers purposely don't do anything with this area of memory because it contains user data.

It's not working for me (I actually think I have some bad memory in my unit) but from all that I've read, a ROM flash via the SD card may solve your storage folder problem. nb1 files contain the memory definitions for the storage folder. I've seen other posts about this and this has fixed the problem for them. When I attempt an SD flash, the download stops at 63% every single time. If you can do an SD flash and it downloads to 100%, your problem may go away.

Just an idea......

[patjack]

Thanks for the advice.
Yes, my internal storage was intack after the upgrade for nearly
a month. But it disappeared one morning.
You may be right, something in ROM or Flash might be broken. :?

[patjack]

What is an SD flash? How do you invoke?
Is your Magician operable at all now that
your flash is incomplete.
Is the nb1 part of the EXE ROM update?

[ppc4]

What is an SD flash? How do you invoke?
Is your Magician operable at all now that
your flash is incomplete.
Is the nb1 part of the EXE ROM update?

Lots of questions....let's see.....

An SD flash is a bit tricky but not too tough once you understand the instructions (attached).

Essentially, you need to get a few programs but they can be had off the ftp site.

Basic steps:
dump ROM that's already installed to an SD card (save this thing somewhere very safe)
copy the first 416 bytes and paste in to new rom that can be downloaded from the ftp site as well.
write the rom back to sd card
flash with new rom
done

The nb1 file is what is created when you do a flash backup of your current rom.

All this sounds a little complex but if you follow the instructions step for step, you'll be fine.

This method rewrites the entire ROM including the storage area so it might fix your problem.

Yes, my unit is still operable at this point but I still have the missing folder problem. My flash ALWAYS stops at 63% and won't go any further so I can't get the storage area, Ext_ROM and Radio to upgrade via this method.

None of this will overwrite the bootloader so you can't really screw anything up even if the flashes fail. If you try all this and run in to the same problem that I ahve, you can always just go back and run the executable again and you'll be back to where you were. I suspect this will probably work for you though.