Help me with /storage folder - JAM, MDA Compact, S100 Software Upgrading

Hello,
i've tried to install 1.13 with bigrom and its installed. but now i flash back again with orig, but my ... /storage was gone. I dont know how to get it again? please help me

Why don't you flash 1.13BS again?

When i flashed to 1.13BS again, it's have 27MB Storage but used 1MB. Any idea?

I lost my \storage in a SD-flash BS attempt, got it back with a successful BS shipped-rom upgrade & take the loss of 1Mb for granted. Guess it's locked for 'permanent backup' or so. More people are having this symptom & 26Mb Storage is much more tha it was, so why bother.
BS can be successfully restored, since I saw reports on it in this forum. Haven't tried it myself though. My advice go 4 BS again.
Cheers, M

This problem has been solved.
I've tried to fill up my BS /storage with 8->10MB of data. Then i flashed to ShipRom. My /storage rom has been cleared and goes back again.
And i see, if u flash ur phone with ShipRom (last state is BigRom), ur /storage is empty u would get your /storage disappear.

Related

Storage area missing after mkbigstorage

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.
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.
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?
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?
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.
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.
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.
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?
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?
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.
patjack said:
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?
Click to expand...
Click to collapse
Are you flashing using the USB and GUI method or using an SD card and bootloader?
I am not a pro.
I only ran the EXE I downloaded from O2 website.
patjack said:
I am not a pro.
I only ran the EXE I downloaded from O2 website.
Click to expand...
Click to collapse
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......
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. :?
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?
patjack said:
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?
Click to expand...
Click to collapse
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.

Large program memory?

Is there a hack for 'large program memory, rather than 'big storage'? Or is it the same thing?
Thanks for any advice, M
Program memory and storage memory is shared- BigStorage releases the previously unusable storage, therefore increasing program and storage memory.
Just use the slider to dedicate more memory to programs...although this auto adjusts itself as and when required.
Thanks that makes BIG storage worth trying. For now I got a only around 35 MB free, with all apps in storage folder and sd-card. Trying to move even more executables from ram to storage or sd. Works fine uptill now.
Sincerely, M
Try memmaid as well to move dlls and executables from \windows\ to storage.
V
Will give a try, but apps like album and camera (both approximately 500K) saved me a lot of ram. I noticed that the default album and camera are in rom, so don't take any ram, though visibke in windiws folder.
Gr. M
BIG-storage try didn't work out. After the flash back of the changed (MKS method) rom, the device stays black and will only go into bootloader. This last saved my device I guess. I tried a restore with the original 1.13 shipped rom and got the device back. Unfortunately I lost my storage folder in this and ext-rom still exists. Is there a way to get the storage folder back? Even with ext-rom is acceptable.
Thnx byba very sad M.
Boot loader magician
OLTP, I had the same problem (only boot loader working and after reinstalling 113 storage gone ), I simply tried reinstalling again and got storage back. I also did a soft reset immediately after first boot after reinstalling 113, so before the programs in extended rom would install. This freed about 25MB working memory although extended rom is still -of course- not editable. I only installed the camera and ended up with a lean magician, and no GPRS bug.
Thnx Mozart,
Will give it another try. I think you mean you installed twice the 1.13 shipped rom? Cause I tried the SD flas twice with no result, a very dead and empty magician. I did do the soft-reset before the ext-rom would autoexec and that didn't help.
So olpnly question now is, did you do the SD flash twice or the upgrade with shipped 1.13 after the failed SD flash.
Thnx in advance, M
Ps. glad I am not the only one with this problem.
I tried the SD-method 3 times, then gave up, and then reinstalled T-Mobiles latest (1.13) rom. I had to use MaUpgradeUt_noID.exe to do this, by the way...., because the SD-flash had ruined the ID of my magician. It is still ruined, but at least my magician is alive and well.
Too bad, I tried the shipped rom for the third time now and still no storage. For the rest my magician is OK. Did not have to use the noid upgrade patch or anything like it. Though the shipped rom claims the device is empty. When I find a decent extracted rom I will try again.
Sincerely, M

A strange problem while upgrading Big storage

Hi there, I just tried to have a big storage upgrade for my XDAIIMini two weeks ago, and it worked!
Afterwards I've changed the ROM to CHT version of O2 Asia XDAIIMini with big storage, and it also worked!
Now, I want to change it back to the original ROM with big storage, then a strange problem appear:
I've edited the ROM correctly, and let the Magician download the ROM from SD. After 100% downloading, it showed
"Downloading failed. Check sum failed"
Then I tried to restore the original ROM without big storage, and it could download the whole ROM.
Now I can just restore the original ROM but not upgrade to Big storage.
Does anyone know what happened?
Any ideas? Thanks.
Billy.
when u restore from BS->Normal u will have
Lost /storage.
Resolution:
Back to BS, fill ur bigstorage /storage with 8-10MB (over 7MB) of data.
Then flash to ShipRom. your /storage will be back
Hi billy198,
The message "Downloading failed. Check sum failed" is very usual after a sd-flash. Just reset & see what happens, most of the time it boots normally. If you don't trust it get a shipped-rom to restore to defaults. & fill your storage over 7MB apparently that works. Wish I knew that 3 months ago, when I had that problem.
Regards, M

*SOLVED* can't mount /dev/block/mmcblk0 and "Image Not Found"

I tried searching for help, but can to a dead end. After I installed JF 1.5 and the phone rebooted, it just hangs on the G1 Tmobile boot screen.... I can restart it and load into recovery but get E: cant mount dev/block/.. I also tried the DREAIMG.NBH but when ever I try to load it (Power+Camera) I get "No Image Found!"... I dont know if it cant find the recovery_testkeys or if it was screwed up during the installation process... It does boot so im guessing no brick.
Any help is GREATLY appreciated
*EDIT*: SOLVED, I downloaded the DREAIMG-29.img, renamed the file with a .nbh extension, and bought a SD READER to MAC 4gig San Disk Card. IT ENDED UP BEING THE NEW CARD and READER THAT MADE IT POSSIBLE!
http://koushikdutta.blurryfox.com/G1/DREAIMG-RC29.zip (Rename DREAIMG.NBH..
Hope this helps this pesky problem
maybe
It might be that it's not reading the sdcard right to read image to reflash. But also some people have been saying some apps are causing it not to go past the g1 screen seem the most common factor is desktop theme apps are doing this people have been able to remove these apps useing umbuntu to remove these apps and all goes back to normal.
Hmm.. umbuntu has never been a real good friend to me.. but yea the SD card was my last possible indication. I thought that after doing a factor reset under recovery deleted the apps...? Is there a way to just reflash to stock rc 33 or rcc 29? Im sort of new to the Android Dev scene... Could the Recover_Testkeys.img image be causing an issue also?
Thanks
Edit: Iv heard that the type of SD card might be an issue (Transend, San Disc, ect.)? ..... I dont know though.
deleted comment... accidental duplicate post
Try a wipe. I had the same thing happen to me only i did something dumb, but once i flashed it, it worked again.
It happened to me today, It stayed on the Android screen for about 30 minutes So I removed the battery and turned it on with home+power button,
did a wipe, and applied the update again.
I dunno if doing the wipe helped but it works now
By wipe you mean recovery then (Alt+W).. Iv done it about 10 times. I keep getting the "cant mount SDCARD" and "dev/block/mmcblk0" after attempting to install update.zip.
Any other thoughts..? thanx
please tell me you have adb set up. if so i can try to help you otherwise i can't do much for you
Tubaking182, To be honest, i dont know for sure if I did set up adb... Could you please explain what it is and if it is still possible to set it up? If you could help me, It would be GREATLY appreciated... im about to give up.... such a pain in the a**
Bump.. for help issues
they may have changed the vold.conf in order to support A2SD, but that would prevent the phone from recognizing SD cards that are not partitioned.
I was rooting my HTC Magic 32A and had the same problem when I choose [Flash zip from sdcard] at RA-hero-v1.6.2
The message was "cant mount /dev/block/mmcblk0"
Then I choose [Other > Move recovery.log to SD] at RA-hero-v1.6.2
And went back to choose [Flash zip from sdgard] and then it works.

[Q] Writing to interal sdcard flash (/mnt/sdcard) galaxy s i9000 not possibe

Hello !
I have a big problem with my galaxy s.
Since January i am working with my JPY firmware quiete fine. On sunday the phone rebooted without anything done by me. Afterwards my homescreen was empty.
Most of my apps are not working now. So i have done a wipe. Nothing, the same. Interesting is, that all my data was still on the device. Then i try to format the internal sd. Not working, no error message. When I delete all files and deinstalled all apps, everthing was gone. After a reboot all data is back on the internal sd as before.
OK then i tried to flash different 1 and 3 file firmware versions with odin(also with repartitioning). But no version is really working and i never get to the homescreen. So I flashed the JPY back. Then everything is like before my first steps. All data is on the phone, i can not delete anything.
I tried do delete the storage also with recovery mode. Nothing.
I tried with adb (android sdk), deleted all files in /mnt/sdcard. After a remount all data appears back.
What can i do to get my phone working ? I have found no possibility so far.
Thanks in advance for your help!
Frederik
Fred001 said:
Hello !
I have a big problem with my galaxy s.
Since January i am working with my JPY firmware quiete fine. On sunday the phone rebooted without anything done by me. Afterwards my homescreen was empty.
Most of my apps are not working now. So i have done a wipe. Nothing, the same. Interesting is, that all my data was still on the device. Then i try to format the internal sd. Not working, no error message. When I delete all files and deinstalled all apps, everthing was gone. After a reboot all data is back on the internal sd as before.
OK then i tried to flash different 1 and 3 file firmware versions with odin(also with repartitioning). But no version is really working and i never get to the homescreen. So I flashed the JPY back. Then everything is like before my first steps. All data is on the phone, i can not delete anything.
I tried do delete the storage also with recovery mode. Nothing.
I tried with adb (android sdk), deleted all files in /mnt/sdcard. After a remount all data appears back.
What can i do to get my phone working ? I have found no possibility so far.
Thanks in advance for your help!
Frederik
Click to expand...
Click to collapse
try to update it using kies or if u have latest version then try flash your device using odn flasher
Thanks for your help harmandeep45. But all this is already done. I worked on this issue little longer and can say that there is some unrepairable problem with the internal sd. I can not delete any partition neither with adb (parted /dev/block/mmcblk0p1 rm). When I do a print everything is there. I am able to mount and unmount the partitions. No problem. But it is not possible to reorganize them. Even if i write on the sdcard partition, after a remount it is as before the write. Maybe the flash memory is broken. Does anybody had the same issue? I already tried the things written in this post, but without luck : http://forum.xda-developers.com/archive/index.php/t-845708.html
I have the same problem, i had installed another firmware on my sgs and start throwing me program errors I had before in my other firmware and when it comes to memory I saw that the folders that were there had not cleared and when I trying to delete the folders and files reappeared.
Ok, what i have tested is to flash different firmware versions. Nothing worked. I used the debug console adb to log in and tried to delete the partitions from /dev/block/mmcblk0 with parted. Nothing happens. I am not able to delete them. I don't want to send the phone to the samsung service, because there is important company data on it, like emails, banking, ebay, etc. I tried to mount it in Linux as usb memory device and used gpartet to create new partitions and overwrite all with dd if=/dev/zero of=/dev/sdb1, but after reboot everything was like before. Is there any other possibility to delete the flash???
Fred001 said:
Ok, what i have tested is to flash different firmware versions. Nothing worked. I used the debug console adb to log in and tried to delete the partitions from /dev/block/mmcblk0 with parted. Nothing happens. I am not able to delete them. I don't want to send the phone to the samsung service, because there is important company data on it, like emails, banking, ebay, etc. I tried to mount it in Linux as usb memory device and used gpartet to create new partitions and overwrite all with dd if=/dev/zero of=/dev/sdb1, but after reboot everything was like before. Is there any other possibility to delete the flash???
Click to expand...
Click to collapse
you have to flash it with jtag box riff, but I doubt you have one, you have to find a place where they have the box

Categories

Resources