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.
Related
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
Hi all,
I'm french, so excuse my bad englsih.
I had a Pocket PC on Windows Mobile 2003 First Edition and i backup my system to my ROM memory. After a new ROM installation (Windows 2003 Second Edition), i can't see this backup file in ROM, and now i have only 1Mo in ROM Memory.
How can i erase the old backup file ? Total Commander & Co can't see the file also...
Thanks a lot for you help !
Regards,
Bertrand
Please specify exactly what device do you have.
(I am not familiar with devices that got upgraded from 2003 to 2003SE)
The reason you cant see your backup is because its gone. When you reflash your device (upgrade the ROM) the File Store (where you save stuff you don't want deleted during hard reset) is also formatted. The reason you only have 1 MB storage left could be one of two things:
A) The new ROM takes more space.
B) Something went wrong during the upgrade and the ROM was not properly partitioned.
NOTE:
There is no way to recover this data. It is recommended that you backup important stuff to SD card or your PC (ActiveSync has a backup function).
I have a PDA, a "Yakumo Alpha GPS" (equal to "Acer N35").
Yesterday, I installed wrong ROM to try to free ROM Storage, and the install have been down. So, I reinstall Windows Moblie Seconde Edition, and now my ROM Storage is 0.2 MO. (
So, yes, I think that an installation was down one week ago, and that's why i had less ROM Storage.
PLease, tell me it's possible to recover my ROM Storage...
Hi beber49!
I am not sure of the details, but I can point you in the right direction and after some searching you should have the solution:
Find a device with the original ROM, there are instructions in the wiki on how to backup ROM to SD then restore. I think if you manage to reflash your device with the original ROM you might get your storage back.
But be careful: If the reflash is not done properly, you may loose all of the free storage or even kill the device.
Sorry, that's all I have. Hope someone gives you a better idea!
i tryed that but no way to see these file...
So I got in this situation by running step 1 of the cheetahunlocker with a CHEETAH.grh file on the SD card. Everything worked (I got OK) on everything but the "OS" flash never finished, just stayed on 90% progress and never moved.
Yes I didn't do a hard SPL, I was trying, but for some reason to hardspl process grabbed a ROM off my SD card and ran with it.
From the various searches I have found that I should get a stock ROM, reflash with this.
I do not have a "Stock ROM" and cannot find one anywhere. Also how would I even flash this ROM if I had it? I would assume I would drop this ROM on the SD card (FAT 32, and rename properly) but where do I find the elusive stock ROM?
I cannot use active sync or anything, my phone with only boot into the bootloader (red/blue/green)
I have an SIM unlocked 750:
- On reset with no SD my phone hangs on the Palm OS progress bar
- On reset + PTT with no SD I get:
Palm Tr
IPL-0.20
Palm Tr
SPL-0.24.0000
- I've tried the cheetachunlocker, step 1, says my image file is corrupted at 7% progress.
- I've tried the athena_unlocker.exe with cheetachunlcoker.exe method, no dice.
- I've tried various ROMs on the SD and none of them seem to go anywhere.
If the answer is "Use your backup ROM", I don't have one. If the answer is "find a stock ROM", where????
I do have another 750 I could "backup" and then use this backup to flash my bricked 750... but how to backup the good one? How to use this backed up ROM to flash the bricked one?
Thanks in advance!!
QuakerOatz said:
So I got in this situation by running step 1 of the cheetahunlocker with a CHEETAH.grh file on the SD card. Everything worked (I got OK) on everything but the "OS" flash never finished, just stayed on 90% progress and never moved.
Yes I didn't do a hard SPL, I was trying, but for some reason to hardspl process grabbed a ROM off my SD card and ran with it.
From the various searches I have found that I should get a stock ROM, reflash with this.
I do not have a "Stock ROM" and cannot find one anywhere. Also how would I even flash this ROM if I had it? I would assume I would drop this ROM on the SD card (FAT 32, and rename properly) but where do I find the elusive stock ROM?
I cannot use active sync or anything, my phone with only boot into the bootloader (red/blue/green)
I have an SIM unlocked 750:
- On reset with no SD my phone hangs on the Palm OS progress bar
- On reset + PTT with no SD I get:
Palm Tr
IPL-0.20
Palm Tr
SPL-0.24.0000
- I've tried the cheetachunlocker, step 1, says my image file is corrupted at 7% progress.
- I've tried the athena_unlocker.exe with cheetachunlcoker.exe method, no dice.
- I've tried various ROMs on the SD and none of them seem to go anywhere.
If the answer is "Use your backup ROM", I don't have one. If the answer is "find a stock ROM", where????
I do have another 750 I could "backup" and then use this backup to flash my bricked 750... but how to backup the good one? How to use this backed up ROM to flash the bricked one?
Thanks in advance!!
Click to expand...
Click to collapse
Stock ROM would be the ROM that was officially shipped with the device, either a carrier branded version or Palm's own version.
Since you said your device was unlocked, it could be one of two possibility:
1. You unlocked it by asking the carrier to provide you with an network unlock code or by purchasing a network unlock code from a 3rd party vendor.
2. Your phone was purchased without a contract tied to a carrier so it was a Palm branded unlocked Treo 750.
Which is it?
This will determine which stock ROM you should run.
And ALL stock ROMs are floating around here or some other forum somewhere...
[Update]
Here's a link to download the 2.23 ROW ROM for the Treo 750: http://rapidshare.com/files/173145556/Treo750_2.23_ROW_WM6.rar
ROW=Rest of the World; Official Palm ROM
Great thanks for that, now how to use this file correctly, now that I screwed this up the first time. I can't use active sync, can only get to the Bootloader Red/Blue/Green screen.
Should I extract the cheetah.rgh to SD and do a reset? I don't think that has been working for me but will try again with this different ROM
Thanks!!
Stuck
So I downloaded the ROW firmware from above, copied to MicroSD and did the old reset+PTT button.
The screen flashes with "Loading..." for a moment and I'm back to
Palm Tr
IPL-0.20
Palm Tr
SPL-0.24.0000
What next? Thanks!
SOLVED!!!!
Hey I might have a solution here:
When you format the Mini SD card, do NOT do a quick format. Uncheck that box and do a full format, FAT32, Default Allocation Size.
This took over 15 minutes for me.
Do a scandisk (Right click the drive/tools/scandisk) and check "Fix Errors". This should ensure your SD card is in good shape.
Now copy a good ROM to the card and reset+PTT. The Palm should flash successfully now. If not your ROM may be corrupted.
Hope this helps! It worked for me!
QuakerOatz said:
Hey I might have a solution here:
When you format the Mini SD card, do NOT do a quick format. Uncheck that box and do a full format, FAT32, Default Allocation Size.
This took over 15 minutes for me.
Do a scandisk (Right click the drive/tools/scandisk) and check "Fix Errors". This should ensure your SD card is in good shape.
Now copy a good ROM to the card and reset+PTT. The Palm should flash successfully now. If not your ROM may be corrupted.
Hope this helps! It worked for me!
Click to expand...
Click to collapse
Glad that your phone is up & running.
Those who brick their Treo 750 should be able to follow the procedures mentioned here & other related thread to recover their devices as long as the bootloader screen is able to display.
QuakerOatz said:
Hey I might have a solution here:
When you format the Mini SD card, do NOT do a quick format. Uncheck that box and do a full format, FAT32, Default Allocation Size.
This took over 15 minutes for me.
Do a scandisk (Right click the drive/tools/scandisk) and check "Fix Errors". This should ensure your SD card is in good shape.
Now copy a good ROM to the card and reset+PTT. The Palm should flash successfully now. If not your ROM may be corrupted.
Hope this helps! It worked for me!
Click to expand...
Click to collapse
i tried that but kept having the same problem....do you think the card is bad????
I got my Inspire and used it normally for about a month. Then I rooted it and tested out about 5 different ROMs and came to like Android Revolution for it's Gingerbread and Sense 2.0 that could have parts of it individually upgraded. (That's besides the point)
Anyway, as it only comes with an 8 GB microSD I looked on ebay for a 16 GB microSD and found one for about $20 or something, class 4. Anyway, I basically hooked up my phone with the old SD card in it, copied the entirety of its contents and then ejected the SD card and put in the new one. Pasted the contents from the old onto the new. Worked fine for a time. Now my phone will occasionally get stuck in a loop of boot animation, starting and working for 1 minute, then going back to the boot animation. I also noticed that any app installed to my SD through ZDBox becomes unusable. I then have to go back to the market and reinstall the apps as trying to restore from my Titanium Backup doesn't work.
I also have noticed that my photos and music can't be accessed. I even looked with root explorer and on my computer and can't find my music or photos at all. I've tried syncing using DoubleTwist and by copying and pasting the folders from the old SD to the new SD in the same directories.
Finally, just a bunch of force-close issues with everything on the phone. Using Rom Manager to Fix Permissions fixes things for a while but then it restarts.
I know it's a lot to read, but I don't know what is causing this and how to fix this. I even tried restoring a backup I had made, but it only resumed about 3 hours later. Any ideas or suggestions are welcome. Thanks in advance!
Things I would do:
If AR requires EXT4 sd card (it will say on the front page, and I believe it does)
-Format your sd card.
-Follow the steps for converting it to EXT 4 ( should be found on the front page)
-Create a back up with recovery or rom manager.(it doesn't matter which)
-Retain the 8gig back up.
-Wipe your phone through recovery (not through rom manager.)
-Redownload the rom.
-Re flash the rom.
Thanks, I'll be sure to try this later tonight.
Hate to reopen this topic, but when I tried to reflash the ROM, I was greeted with a an error saying I cannot open "(insert filename here).zip (bad)".
I've looked, and tried a couple of solutions other people have had, but so far they haven't worked. What can someone suggest?
I'm assuming it has something to do with the fact that the md5 checksums are different and don't match. I've downloaded AR HD about 5 times and moved to the phone. I get a different md5 checksum everytime.
Ssssschwartz said:
Hate to reopen this topic, but when I tried to reflash the ROM, I was greeted with a an error saying I cannot open "(insert filename here).zip (bad)".
I've looked, and tried a couple of solutions other people have had, but so far they haven't worked. What can someone suggest?
I'm assuming it has something to do with the fact that the md5 checksums are different and don't match. I've downloaded AR HD about 5 times and moved to the phone. I get a different md5 checksum everytime.
Click to expand...
Click to collapse
Make sure all anti virus is shut off when you dl the rom
zelendel said:
Make sure all anti virus is shut off when you dl the rom
Click to expand...
Click to collapse
Thanks for the advice. The checksum for the downloaded ROM matched, then I pasted it onto the SD and it matched when I checked it on the computer. Then I went into recovery and tried to load it and it's still giving me a the file bad error. I checked the checksum through recovery and it was a completely different checksum.
I'm really confused as to why I'm having these issues.....
make sure you disconnect the phone/sd card properly - sometimes the OS will report the file has fully written but the cache is still writing the file. If you can, use a service like dropbox or another file sharing (via web) and download the rom directly to the sd card - might get better results.
No need to bring back a very old thread. Thread closed
Hello everydody, I am experiencing some difficulties with my Samsung, model GT-I9003-phone which "dropped off a lorry" somewhere next to my relatives somewhere in Asia. When I goth the device, it was in a non-working condition, except a boot-loop and the download-mode. Back then, I had the package of the phone where the exact version ( I don't know if this is what is called "Baseband" or at least is called baseband at my wife's GT-I5003) was specified. So, back then, I was able to find the exact ROM for the device. Unfortunately, the box with the version number now is - somewhere.
After flashing a stock-rom, I managed to enter recovery-mode where I read something about the internal memory being corrupt. As far as I can recall, I then mounted the external SD-Card and somehow managed to reboot the system back to almost normal operation. Even reboots appeared to work normal, besides the fact I had no memory access, neither to internal nor to external sd. In addition, GPS malfunctioned, too.
Unfortunately, even this state didn't last for long time. After several weeks of now-and-then-use, the system just broke down again into a boot-loop. After some time of flashing a variety of stock roms, I managed to flash clockworkmod recovery which works perfectly well. Unfortunately, I didn't manage to root the phone before it "collapsed" again. Besides the possibility, I'd guess this could be a resaon for CWM being unable to flash a custom rom? Otherwise, I'd just test my way through the varieties of versions .
Basically, I do have two questions: 1. is there a possibility to find out if internal memory has failed - and if yes: How?
2. Is it possible to install any version of CM on that phone in the condition it is in?
Thanks a lot in advance for any answers
Hello everybody, I finally found the box . It reads GT-I9003MKDTHL. Is my assumption right that there are no such things as basebands in the GT-I9003 any more and I should be able to flash pretty much any firmware? Furthermore, today I tried to format what is specified as "sd-card ext" in CWM fir GT-I9003 and it gives me an error-message. When I flash "sd-card", my external sd-card gets formatted. So, I'd presume the internal sd is just fried. I read about a workaround for GT-I 9000, where someone installed Androd on a partitioned external SD. Is there somebody who knows someboy having heard about somthing similar working with the GT-I9903?
One step forward...
Hello everybody, I finally managed to get some light into my issues as I once again figured out how to get a software installed and running . It's this one:
http://forum.xda-developers.com/showthread.php?t=2329200
Thanks a lot to the guy who just posted it somewhere where id could do good...
By the way, I figured out that this software actually includes the Baseband.
As in this version, the original recovery system is running and giving me an error message when I start it without external SD-card, I am now quite sure that the internal memory has just failed as this error message was specified in another posting of someone who had a similar issue with a GT-I9000.
The biiiig "Outch" is, that I am unable to install any CWM Recovery System with that Baseband..This results in me not being able to upgrade the software to ICS, where - as far as I read some troubleshoot-information - will enable me to mount an additional partition on my SD-Card as Data-Partition which isn't possible yet (i.e.: I can't access my SD for storing data or whatever - it's just specified as "not there").
I tried to install the XXKPE-Baseband to be able to go for KPQ which would enable me to install CWM Recovery. I also installed Bagarias CWM-normalboot-image via Heimdall - but I was unable both to boot the OS and to find any trace of a zip-file on the SD-card.
Edit: I managed to install the right CWM - it's mentioned in the post where I've got the firmware from... now, I only have to figure out how to deal with the fact that "officially" there is no SD-card inserted - or, better, that this SD-card is now flagged as "internal SD" - and how that machine can find the zip-file on it
Thanks for every bit of help with that issue
Try Aroma File Manager with Terminal
For SDCard issue you could probably switch them in vold.fstab in /system/etc
Good Luck !!!
try this- http://forum.xda-developers.com/showthread.php?t=2329200