Just a problem of space?

Goodmorning everyboy,
I have a problem with my iPod Nano 4G.
Actually, since yesterday everything was fine and I still had a lot of space. Today I updated more songs (something like 5 or 6) and the iPod suddenly said that there was no longer space. I saw the details and I found out that almost a giga is taken by the "other" issues... I don't know if this is the right name in english... And I really don't understand how this can be possible since that I just uploaded the images of the songs... And before doing that, there was space. So it is impossible that few images can take so much space.
Please, help me. Is there a way to check what is in the "other sruff" directory?
Thank you so much!

The storage space taken up by "Other" can be made up of, notes or files of any kind you've added to the iPod whilst using it as a hard disk.
There will always be a few MBs of used space under "other" but if it's in GBs it's unusually large.
If the iPod is enabled for disk use, you can look at the folders on the iPod through Explorer and delete anything you don't want.
Otherwise, see how to restore the iPod to factory settings which will erase the iPods contents and reclaim the used space.
Then reload the music from iTunes.

Similar Messages

  • Problem about space management of archived log files

    Dear friends,
    I have a problem about space management of archived log files.
    my database is Oracle 10g release 1 running in archivelog mode. I use OEM(web based) to config all the backup and recovery settings.
    I config "Flash Recovery Area" to do backup and recovery automatically. my daily backup schedule is every night at 2:00am. and my backup setting is "disk settings"--"compressed backup set". the following is the RMAN script:
    Daily Script:
    run {
    allocate channel oem_disk_backup device type disk;
    recover copy of database with tag 'ORA$OEM_LEVEL_0';
    backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
    the retention policy is the second choice, that is "Retain backups that are necessary for a recovery to any time within the specified number of days (point-in-time recovery)". the recovery window is 1 day.
    I assign enough space for flash recovery area. my database size is about 2G. I assign 20G as flash recovery area.
    now here is the problem, through oracle online manual, it said oracle can manage the flash recovery area automatically, that is, when the space is full, it can delete the obsolete archived log files. but in fact, it never works! whenever the space is full, the database will hang up! besides, the status of archived log files is very strange, for example, it can change "obsolete" stauts from "yes" to "no", and then from "no" to "yes". I really have no idea about this! even though I know oracle usually keep archived files for some longer days than retention policy, but I really don't know why the obsolete status can change automatically. although I can write a schedule job to delete obsolete archived files every day, but I just want to know the reason. my goal is to backup all the files on disk and let oracle automatically manage them.
    also, there is another problem about archive mode. I have two oracle 10g databases(release one), the size of db1 is more than 20G, the size of db2 is about 2G. both of them have the same backup and recovery policy, except I assign more flash recovery area for db1. both of them are on archive mode. both of nearly nobody access except for the schedule backup job and sometime I will admin through oem. the strange thing is that the number of archived log files of smaller database, db2, are much bigger than ones of bigger database. also the same situation for the size of the flashback logs for point-in-time recovery. (I enable flashback logging for fast database point-in-time recovery, the flashback retention time is 24 hours.) I found the memory utility of smaller database is higher than bigger database. nearly all the time the smaller database's memory utility keeps more than 99%. while the bigger one's memory utility keeps about 97%. (I enable "Automatic Shared Memory Management" on both databases.) but both database's cup and queue are very low. I'm nearly sure no one hack the databases. so I really have no idea why the same backup and recovery policy will result so different result, especially the smaller one produces more redo logs than bigger one. does there anyone happen to know the reason or how should I do to check the reason?
    by the way, I found web based OEM can't reflect the correct database status when the database shutdown abnormally. for example, if the database hang up because of out of flash recovery area, after I assign more flash recovery area space and then restart the database, the OEM usually can't reflect the correct database status. I must restart OEM manually to correctly reflect the current database status. does there anyone know in what situation I should restart OEM to reflect the correct database status?
    sorry for the long message, I just want to describe in details to easy diagnosis.
    any hint will be greatly appreciated!
    Sammy

    thank you very much, in fact, my site's oracle never works about managing archive files automatically although I have tried all my best. at last, I made a job running daily to check the archive files and delete them.
    thanks again.

  • Just purchased more storage space for iphone6 but not showing?

    I just purchased more storage space for my iphone6, 20gb, but my backup storage still shows 5gb?  How do I troubleshoot this problem, my credit card info is accurate?

    You cannot install more storage space on an iDevice. If you don't have space on the device to download to it, then you need to delete stuff from it. Buying more cloud space does not do a thing for you unless you store to the cloud and remove from the device.

  • DW CS5.5 in OSX Lion - anyone seeing problems with Spaces?

    DW seems to have problems with Spaces in OSX Lion.Switching into DW from other spaces is not 'clean'. When DW comes up, sometimes the Code/Design is blank white, and windows within the workspace don't show their headers. Clicking on Code/Design redraws that window, but the only thing that seems to recover the window headings is switching to and then back from another app in the same Space.
    Seems like screen redrawing triggered by switching apps within the same Space is a little different than that triggered by switching apps across Spaces.
    Anyone else seeing this?

    I did report it as a bug, using the link kindly provided by you and Shocker.
    The two Macs I've tried this on now are a Mac Pro and an iMac, so there's no Automatic Graphics Switching option to enable/disable.
    I was only able to check this out on the iMac late last night.
    Hardware synopsis:
    Mac Pro Early 2009
    Processor  2 x 2.93 GHz Quad-Core Intel Xeon
    Memory  16 GB 1066 MHz DDR3 ECC
    Graphics  NVIDIA GeForce GT 120 512 MB
    Software  Mac OS X Lion 10.7 (11A511)
    The iMac isn't available to me at the moment, I'll have to fill in missing details later (can't remember the exact graphics card info):
    DW is CS5, not CS5.5, was also installed well ahead of the Lion upgrade
    Computer is iMac instead of Mac Pro, about 1.5 years old
    Quad-Core i7
    4GB memory
    Mac OS X Lion 10.7
    I used the same procedure upgrading to Lion on the iMac...
    Ran Cocktail 'Pilot' to clean up the system prior to install (runs Daily, Weekly, Monthly maintenance scripts, clears System, User, and Internet caches, repairs disk permissions on "Macintosh HD", clears log files)
    OS10.7 was purchased through the Mac App Store and installed.
    JRE installed.
    DW on the iMac exhibited the same problem as on the Mac Pro.
    To reproduce:
    Start DW, open a file for editing
    Start any other app in the same Space
    Open a new Space, open any other app there.
    Test switching between DW and other apps in the same Space compared with switching between DW and other apps in different Spaces.
    Consistently, when I switch between DW and other apps in the same Space, DW's windows/panels redraw properly,
    and when I switch between DW and other apps in different Spaces, DW's windows/panels don't redraw properly.

  • I using mozilla firefox so long times but it just get problem today because i can't type in english words but i can type in thai and some buttons is not english but it's other alphbets that i can't read and it's happening with yahoo and friendster and not

    I using mozilla firefox so long times but it just get problem today because i can't type in english words but i can type in thai and some buttons is not english but it's other alphbets that i can't read and it's happening with yahoo and friendster and not sure for other website
    == today ==
    == User Agent ==
    Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)

    Same problem with the mouse, but with the mouse I can leave the cursor in place in the text field and move to the keyboard to type. As long as the cursor is in the field it stays editable.
    The problem with the pen is it's in my hand all of the time. I just flip it up under my thumb against my palm to type. So, as soon as I move the pen, the field goes away and I can't type in it. Hoping this is making sense.
    My tablet does have the touch function too, and I just found out I can use my finger to tap in the text field, then type. I guess that'll be my solution since I prefer not to leave a mouse set up on this iMac.
    I'm thinking now that this is just a problem with the pen itself, and nothing to do with iPhoto. So glad to have this figured out! I really like iPhoto '11! So much easier for me, a simple P&S gal, than Aperture 3. I use iPhoto Library Manager too and love it!
    Thanks so much! Debbie

  • I'm now using iPhoto '11 (9.3.2), and none of the photos in my library will enlarge.  I can view them all as thumbprints, but when I click to enlarge just a black, blank space shows up.  Occasionally, one will enlarge for a second, then disappear.  Help!

    I'm now using iPhoto '11 (9.3.2), and none of the photos in my library will enlarge.  I can view them all as thumbprints, but when I click to enlarge just a black, blank space shows up.  Occasionally, one will enlarge for a second, then disappear.  Help!

    Just to clarify, I am not getting an "!" mark in a triangle, as I read others have experienced.  The screen is just blank except the grey flag in lefthand corner to flag the photo.

  • After updating to ios6. I am unable to have voice control in my Fiesta Titanium has this been a problem for anyone else or just my problem?

    After updating to ios6. I am unable to have voice control in my Fiesta Titanium has this been a problem for anyone else or just my problem?

    I am an activist when it comes to rip-offs and I intend to set up a group to pressure the Ausralian government to legislate to make all computer software producers to make all new software compatible with all old software AT NO COST to the user.
    I thought about that myself, but when it comes to Windows XP. It is peculiar that software companies get away with "selling" software that suddenly stops working properly. The problem with XP is of course an environmental one as well. There is a huge number of fully functional PCs that suddenly are no longer supported by Microsoft, and that are not powerful enough to take newer supported MS operating systems. What MS basically recommends people is to throw them away with a horrible cost for our environment.

  • How do I erase pics from I phone wi my I pad.    Just want to free space from my phone.

    How do I erase pics from I phone without erasing them from I stream or my I pad.    Just want to free space from my phone.

    http://support.apple.com/kb/ht4083

  • Problem with Spaces that started with Snow Leopard

    I've noticed two problems with Spaces that have arrived since switching to Snow Leopard... First, if I am in say Space 1 where I use Safari and I then want to move over to an open application, say like Excel, that I have running in Space 4, there are a number of ways to get there but one way I used to use all the time was to move down to the Dock and simply single click on the open Excel application and that would immediately switch me over to Space 4 and whatever Excel documents were already open there... Now, since switching to SL, a single click of whatever application in the Dock makes that application active in the Finder (you see its name appear in the upper left of the menu bar) but otherwise nothing happens... You then have to click a second time and then you switch over to Space 4... It's not really a double click because that implies to clicks closely spaced in time... For this, you can click once, leave the room, come back, click a second time and you will now switch to the alternate space where the open application is running... That is clearly different than it was under Leopard and I would suggest that it is a bug because there is no value in the outcome of that first click... It highlights the switched application but doesn't actually switch to it until you click a second time...
    Second, and this one is worse, if you say launch Excel (which you want to open in Space 4) while you are in Space 1, Excel will open and switch over to Space 4... So far so good... But now, with Excel open over in Space 4, if you are now back and working in Space 1 and while there you use the Finder to go to some other, currently unopened, Excel file and request that it open, it should switch over to Space 4 and open that file but instead it opens it wherever you are, in the case mentioned here, in Space 1... So now you have Excel files opened both in Spaces 1 and 4... Clearly a bug... Spaces had some similar issues in a few early versions of Leopard but they eventually got it working... Now it appears Spaces has regressed somewhat in SL... I love spaces and use it all the time... Hope it gets fixed soon... thanks... bob...

    Hi... I have since learned that the first paragraph of my original post where I say,
    "I've noticed two problems with Spaces that have arrived since switching to Snow Leopard... First, if I am in say Space 1 where I use Safari and I then want to move over to an open application, say like Excel, that I have running in Space 4, there are a number of ways to get there but one way I used to use all the time was to move down to the Dock and simply single click on the open Excel application and that would immediately switch me over to Space 4 and whatever Excel documents were already open there... Now, since switching to SL, a single click of whatever application in the Dock makes that application active in the Finder (you see its name appear in the upper left of the menu bar) but otherwise nothing happens... You then have to click a second time and then you switch over to Space 4... It's not really a double click because that implies to clicks closely spaced in time... For this, you can click once, leave the room, come back, click a second time and you will now switch to the alternate space where the open application is running... That is clearly different than it was under Leopard and I would suggest that it is a bug because there is no value in the outcome of that first click... It highlights the switched application but doesn't actually switch to it until you click a second time... "
    ...that turned out to be my mistake... In another post someone pointed out that in Spaces preferences you must have checked ON the preference that says,
    "When switching to an application, switch to a space with open windows for the application"...
    I had been playing with a number of things trying to figure out what was going on and somewhere in the mix had switched that off... (It is on on all my other computers and I'm sure it originally was on this one too)... When I switched it back on the above described problem went away... So that was my fault...
    But the second part,
    "Second, and this one is worse, if you say launch Excel (which you want to open in Space 4) while you are in Space 1, Excel will open and switch over to Space 4... So far so good... But now, with Excel open over in Space 4, if you are now back and working in Space 1 and while there you use the Finder to go to some other, currently unopened, Excel file and request that it open, it should switch over to Space 4 and open that file but instead it opens it wherever you are, in the case mentioned here, in Space 1... So now you have Excel files opened both in Spaces 1 and 4... Clearly a bug... "
    ...is a real problem... I fired up my G4 (power pc) that runs Leopard, 10.5.8, to see whether it behaves the above way or not and it does NOT... It works as one would expect.. So at least later in Leopard, the above mentioned problem was not present but it is in this first incarnation of Snow Leopard...
    To me, the utility of Spaces is all about keeping a single desktop from being cluttered with many open applications/files and to now have an application that opens in whatever space you happen to be in after it is first opened in its "correct" space sort of defeats the idea behind Spaces... I am currently trying to train myself to first hit <command><4> (my Excel space) before opening a second or subsequent Excel document to prevent it from opening somewhere where I don't want it to be...
    Again, I hope Apple sees and fixes this... I did submit an "Apple feedback" item for this issue... thanks... bob..

  • I just had problems with a game called call of duty 4, modern warfare.  I decided that if I deleted it, I could reinstall it, I could get it back to normal. After I deleted it,I went to to the appstore and went to purchases and accidentaly deleted it/help

    I just had problems with a game called call of duty 4, modern warfare.  I decided that if I deleted it, I could reinstall it, I could get it back to normal. After I deleted it,I went to to the appstore and went to purchases and accidentaly deleted it.  please help me!

    You have not deleted it from the purchases list, it is just hidden. To unhide an app, open the Mac App Store app, click the Account link in the Quick Links to the right of the pane and go to the iTunes in the Cloud section where you can manage hidden apps.

  • Just One Problem - The Application Can't Be Found

    I've successfully moved from a Mac Pro (2,1) to a Mac Mini (6,2), running OS 10.9.5 and iTunes 12.0.1.26. There were several glitches during the move, but I finally associated my iTunes folder, now on an external HD, with the application using the option key during launch method. Everything works, iPhones, iPads, iPods all sync properly, all the playlists are there and play all songs, the App Store and iTunes Store function normally using my single Apple ID.
    Just one problem.
    When I try to play content from within the iTunes Music [Media] folder, either by double-clicking on a track or by control-click "Open With", I get an error message "The Application Can't be Found".
    My iTunes Library goes back to iTunes 3 and contains over 350 GB media. This new behavior is worrying, because I don't understand why moving the iTunes Folder should have caused this. Any ideas will be appreciated.

    Thanks for replying.
    Yes, from within the iTunes app all behaviors appear normal. I should test if tracks or other media that are not inside the iTunes Library respond the same way.

  • I am having some display and loading problems with my Mac book pro..I have filled just 10 gb of space..Since buying it 3 months back I have been pretty disappointed with use of this laptop..I would like a new one.

    after talking to the apple guys I wasnt satisfie as they told me everything is correct but it still makes those errors.

    Take it to an Apple store or AASP. As far as getting a new one unless there is something radically wrong with the one you have that cannot be repaired you're out of luck. You're not satisfied about what? If you have problems then you need to elaborate and describe them here. Moaning doesn't do it.

  • Problems with spaces in directory or file names and Word.exe

    Hi
    I'm trying to open a file with Word from my java aplication, and I have a problem with some file/directory names.
    I have this
    String cmd = "c:\\Program Files\\Microsoft Office\\Office10\\WINWORD.EXE" + " " + path;
    try {
    Runtime.getRuntime().exec(cmd);
    } catch (Exception errorea){ }
    Here is what happens:
    if path is something like this: "c:\people\info.doc" , there's no problem, Word opens the document, but if path contains blank spaces somewhere, it doesn't work. For example:
    path = "c:\Documents and Settings\info.doc"
    path = "c:\Hi everybody\info.doc"
    path = "c:\tests\test results.doc"
    with the above examples it doesn't work :( Word tries to open "c:\Documents", "c:\Hi" or "c:\tests\test".
    Can anyone help? thanx a lot ! : )

    No, the exec method runs the Word.weird, it shouldn't, and it wouldn't on my system going by the test I just made, but I'm running linux & not windows, maybe the command line parsing is different for some reason.
    The problem is that
    Word starts and then Word says that it can't open the
    file because the name or the path to the file is not
    valid.You still should use the overload that takes a String array.

  • Problems after space error reported

    My Time Capsule device has worked perfectly for months and deletes old backups as necessary when there is insufficient space for a new backup. I'm using a 500Gb device to backup a Mac Pro and a G4 Powerbook - no problems until yesterday.
    During a backup I received an error message - this gist of it was "Time Capsule encountered an unexpected space problem during a backup and will create space next time". Expecting this problem to be resolved automatically I clicked OK and carried on working. The problem I now have is that Time Capsule has been preparing for backup for several hours (across two consecutive days) now and shows no sign of starting a new backup.
    I left the MacPro running overnight yesterday but the new backup had not started when I started work this morning. I restarted the MacPro this morning (8 hours ago) and prompted Time Capsule to "Backup Now" - it has been eight hours and the backup has not started - it is still "preparing".
    I have looked in the system log and can see messages containing write error 28 and something to do with "needs recovery" (see below) but this way above my level of expertise.
    (May 27 00:00:29 Cliffs-G5-Tower mds[31]: (Error) DiskStore: permission cache (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/2AC640AD-DD16-4A9E-9A7C-7CE19E555775/perm Store) write error: 28
    May 27 00:00:29 Cliffs-G5-Tower mds[31]: (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/B452885D-CF11-4D79-8349-35C3D3EF5545)(Err or) IndexCI in CIMetaInfoSync:write err: 28
    May 27 00:00:29 Cliffs-G5-Tower mds[31]: (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/2AC640AD-DD16-4A9E-9A7C-7CE19E555775)(Err or) IndexCI in openIndex:index shadow err:-1 at 0.
    May 27 00:00:29 Cliffs-G5-Tower mds[31]: (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/2AC640AD-DD16-4A9E-9A7C-7CE19E555775)(Err or) IndexCI in ContentIndexOpenBulk:Could not open /Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/2AC640AD-DD16-4A9E-9A7C-7CE19E555775/0.; needs recovery)
    There are lots of messages in the system log as follows: -
    (May 27 16:48:48 Cliffs-G5-Tower KernelEventAgent[33]: tid 00000000 type 'hfs', mounted on '/Volumes/Backup of Cliff's G5 Tower', from '/dev/disk5s2', low disk
    May 27 16:49:04 Cliffs-G5-Tower mds[31]: (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/F856DAC8-CE5F-46E8-B826-19B10BC52F31)(Err or) IndexCI in CIMetaInfoSync:write err: 28
    May 27 16:49:34 Cliffs-G5-Tower mds[31]: (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/F856DAC8-CE5F-46E8-B826-19B10BC52F31)(Err or) IndexCI in CIMetaInfoSync:write err: 28
    May 27 16:50:04 Cliffs-G5-Tower mds[31]: (/Volumes/Backup of Cliff's G5 Tower/.Spotlight-V100/Store-V1/Stores/F856DAC8-CE5F-46E8-B826-19B10BC52F31)(Err or) IndexCI in CIMetaInfoSync:write err: 28)
    I can also see messages from 26 May that report no space left on device and then others that say "waiting for index to be ready (909 >0) - see below.
    26/05/2009 14:57:17 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    26/05/2009 14:57:17 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    26/05/2009 14:57:17 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    26/05/2009 14:57:17 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    26/05/2009 14:57:18 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    26/05/2009 14:57:18 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    26/05/2009 14:57:18 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    26/05/2009 14:57:18 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    26/05/2009 14:57:19 /System/Library/CoreServices/backupd[3567] Exception writing exclusions cache. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    26/05/2009 14:57:19 /System/Library/CoreServices/backupd[3567] Unable to create exclusions cache data.
    26/05/2009 14:57:19 /System/Library/CoreServices/backupd[3567] Failed to write exclusions cache. Continuing anyway.
    26/05/2009 14:57:19 /System/Library/CoreServices/backupd[3567] Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: No space left on device
    26/05/2009 14:57:19 /System/Library/CoreServices/backupd[3567] Waiting for index to be ready (909 > 0)
    26/05/2009 14:57:24 /System/Library/CoreServices/backupd[3567] Waiting for index to be ready (909 > 0)
    26/05/2009 14:57:34 /System/Library/CoreServices/backupd[3567] Waiting for index to be ready (909 > 0)
    26/05/2009 14:57:49 /System/Library/CoreServices/backupd[3567] Waiting for index to be ready (909 > 0)
    This message is repeated every 30 seconds and is the only entry in the log since the "no space left on device" message.
    Is this just Time Capsule carrying out a deep traversal (there's no mention in the log) or do I have a problem with the TC device? I'd be very grateful for any help or suggestions.
    Kind regards,
    Cliff
    Brighton, UK

    I think I got it.
    Open Terminal, type "hdiutil compact " and drag the sparsebundle onto the terminal window, so that it copies the right path. Hit return and let it free some space. The sparsebundles do not automatically compact themselves when they delete some old backups, so doing it manually did the trick for me.
    After completing, I had some 40 GB space again and the backup worked again.

  • Update problems, no space left on device (ZTE Open)

    I just received a ZTE Open device in the mail today, and after playing around with it a bit, I noticed that every time I tried to check for system updates, it would show me one 13.xx MB update, which I downloaded, apparently applied, and the phone seemed to restart itself, but then I would be shown the same (??) update available. The phone is without a SIM card, just playing with it connected via Wifi, with the 4GB microSD card installed. Then, this evening, I got an error message, which apparently was recorded on the SD card, a file called recovery.log (contents follow):
    <pre><nowiki>Starting recovery on Fri Aug 23 07:29:21 2013
    framebuffer: fd 4 (320 x 480)
    recovery filesystem table
    =========================
    0 /tmp ramdisk (null) (null) 0
    1 /boot mtd boot (null) 0
    2 /amss mtd amss (null) 0
    3 /appsbl mtd appsbl (null) 0
    4 /mibib mtd mibib (null) 0
    5 /qcsbl mtd qcsbl (null) 0
    6 /oemsbl1 mtd oemsbl1 (null) 0
    7 /oemsbl2 mtd oemsbl2 (null) 0
    8 /splash mtd splash (null) 0
    9 /cache yaffs2 cache (null) 0
    10 /data yaffs2 userdata (null) 0
    11 /misc mtd misc (null) 0
    12 /recovery mtd recovery (null) 0
    13 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
    14 /system yaffs2 system (null) 0
    I:Got arguments from /cache/recovery/command
    mtd: successfully wrote block at 0
    I:Set boot command "boot-recovery"
    Command: "/sbin/recovery"
    ro.secure=1
    ro.allow.mock.location=0
    ro.debuggable=0
    ro.build.id=IMM76D
    ro.build.display.id=OPEN_US_DEV_FFOS_V1.0.0B01
    ro.build.version.incremental=eng..20130724.030603
    ro.build.version.sdk=15
    ro.build.version.codename=REL
    ro.build.version.release=4.0.4
    ro.build.sw_internal_version=US_DEV_FFOS_V1.0.0B01
    ro.build.baseband_version=P752D04B02
    ro.build.firmware_revision=V1.01.00.01.019.144
    ro.build.date=2013年 07月 24日 星期三 03:06:47 CST
    ro.build.date.utc=1374606407
    ro.build.type=user
    ro.build.user=
    ro.build.host=ThinkCentre2-XXXX
    ro.build.tags=test-keys
    ro.product.model=roamer2
    ro.product.external_model=ZTE OPEN
    ro.product.brand=ZTE
    ro.product.name=roamer2
    ro.product.device=roamer2
    ro.product.board=roamer2
    ro.product.cpu.abi=armeabi-v7a
    ro.product.cpu.abi2=armeabi
    ro.product.manufacturer=ZTE
    ro.product.locale.language=en
    ro.product.locale.region=US
    ro.wifi.channels=
    ro.board.platform=msm7627a
    ro.build.product=roamer2
    ro.build.description=roamer2-user 4.0.4 IMM76D eng..20130724.030603 test-keys
    ro.build.fingerprint=ZTE/roamer2/roamer2:4.0.4/IMM76D/eng..20130724.030603:user/test-keys
    ro.build.characteristics=default
    rild.libpath=/system/lib/libril-qc-1.so
    rild.libargs=-d /dev/smd0
    persist.rild.nitz_plmn=
    persist.rild.nitz_long_ons_0=
    persist.rild.nitz_long_ons_1=
    persist.rild.nitz_long_ons_2=
    persist.rild.nitz_long_ons_3=
    persist.rild.nitz_short_ons_0=
    persist.rild.nitz_short_ons_1=
    persist.rild.nitz_short_ons_2=
    persist.rild.nitz_short_ons_3=
    ril.subscription.types=NV,RUIM
    DEVICE_PROVISIONED=1
    debug.sf.hw=1
    debug.composition.7x27A.type=mdp
    debug.composition.7x25A.type=mdp
    dalvik.vm.heapsize=128m
    persist.cne.UseCne=none
    persist.cne.bat.range.low.med=30
    persist.cne.bat.range.med.high=60
    persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
    persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
    persist.cne.bwbased.rat.sel=false
    persist.cne.snsr.based.rat.mgt=false
    persist.cne.bat.based.rat.mgt=false
    persist.cne.rat.acq.time.out=30000
    persist.cne.rat.acq.retry.tout=0
    persist.cne.fmc.mode=false
    persist.cne.fmc.init.time.out=30
    persist.cne.fmc.comm.time.out=130
    persist.cne.fmc.retry=false
    media.stagefright.enable-player=true
    media.stagefright.enable-meta=false
    media.stagefright.enable-scan=true
    media.stagefright.enable-http=true
    media.stagefright.enable-fma2dp=true
    media.stagefright.enable-aac=true
    media.stagefright.enable-qcp=true
    ro.opengles.version=131072
    ro.use_data_netmgrd=true
    persist.data.ds_fmc_app.mode=0
    persist.ims.regmanager.mode=0
    ro.bluetooth.request.master=true
    ro.qualcomm.bluetooth.sap=false
    ro.bluetooth.remote.autoconnect=true
    persist.sys.strictmode.visual=false
    persist.omh.enabled=1
    ro.config.ehrpd=true
    ro.qualcomm.cabl=1
    ro.fm.analogpath.supported=true
    ro.fm.transmitter=false
    ro.fm.mulinst.recording.support=false
    ro.hw_plat=7x27a
    ro.emmc.sdcard.partition=18
    ro.screen.layout=normal
    debug.enabletr=false
    debug.camcorder.disablemeta=0
    persist.fuse_sdcard=false
    debug.camera.landscape=true
    ro.max.fling_velocity=4000
    hwui.render_dirty_regions=false
    httplive.enable.discontinuity=true
    power.webview.DM=false
    dalvik.vm.heapstartsize=5m
    dalvik.vm.heapgrowthlimit=36m
    org.bluez.device.conn.type=boolean
    keyguard.no_require_sim=true
    ro.com.android.dataroaming=false
    ro.com.android.dateformat=MM-dd-yyyy
    ro.config.ringtone=Ring_Synth_04.ogg
    ro.config.notification_sound=pixiedust.ogg
    ro.config.alarm_alert=Alarm_Classic.ogg
    ro.vendor.extension_library=/system/lib/libqc-opt.so
    ro.display.colorfill=1
    ro.moz.ril.emergency_by_default=true
    ro.moz.omx.hw.max_width=640
    ro.moz.omx.hw.max_height=480
    ro.moz.cam.0.sensor_offset=270
    ro.moz.ril.simstate_extra_field=true
    persist.sys.ztelog.enable=1
    persist.radio.add_power_save=1
    ro.sensor.arch.type=new
    net.bt.name=Android
    net.change=net.bt.name
    dalvik.vm.stack-trace-file=/data/anr/traces.txt
    ro.factorytest=0
    ro.serialno=ROAMER2
    ro.bootmode=unknown
    ro.baseband=msm
    ro.carrier=unknown
    ro.bootloader=unknown
    ro.hardware=roamer2
    ro.revision=0
    ro.emmc=0
    init.svc.recovery=running
    E:Error in /cache/recovery/log
    (No space left on device)
    E:Error in /cache/recovery/last_log
    (No space left on device)
    mtd: successfully wrote block at 0
    I:Set boot command ""
    E:Error in /cache/recovery/log
    (No space left on device)
    E:Error in /cache/recovery/last_log
    (No space left on device)</nowiki></pre>
    The SD card also contains a zip file in updates/fota/update.zip, which in turn contains patch/system/P752D04_DEV_US_20130726.zip, which contains: amss.mbn (about 20 meg) and boot.img (about 4 meg).

    Just jumping in here, I received mine on the 23rd and I am also seeing the same problem, but the logs are a bit different. Although, I am running OPEN_US_DEV_FFOS_V1.0.0'''B02'''. While the recovery log states B01.
    I'll toss my log up as well so trends can be examined.
    Starting recovery on Sun Aug 25 07:04:10 2013
    framebuffer: fd 4 (320 x 480)
    recovery filesystem table
    =========================
    0 /tmp ramdisk (null) (null) 0
    1 /boot mtd boot (null) 0
    2 /amss mtd amss (null) 0
    3 /appsbl mtd appsbl (null) 0
    4 /mibib mtd mibib (null) 0
    5 /qcsbl mtd qcsbl (null) 0
    6 /oemsbl1 mtd oemsbl1 (null) 0
    7 /oemsbl2 mtd oemsbl2 (null) 0
    8 /splash mtd splash (null) 0
    9 /cache yaffs2 cache (null) 0
    10 /data yaffs2 userdata (null) 0
    11 /misc mtd misc (null) 0
    12 /recovery mtd recovery (null) 0
    13 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
    14 /system yaffs2 system (null) 0
    I:Got arguments from /cache/recovery/command
    mtd: successfully wrote block at 0
    I:Set boot command "boot-recovery"
    Command: "/sbin/recovery" "--update_package=/sdcard/updates/fota/update.zip"
    ro.secure=1
    ro.allow.mock.location=0
    ro.debuggable=0
    ro.build.id=IMM76D
    ro.build.display.id=OPEN_US_DEV_FFOS_V1.0.0B01
    ro.build.version.incremental=eng..20130724.030603
    ro.build.version.sdk=15
    ro.build.version.codename=REL
    ro.build.version.release=4.0.4
    ro.build.sw_internal_version=US_DEV_FFOS_V1.0.0B01
    ro.build.baseband_version=P752D04B02
    ro.build.firmware_revision=V1.01.00.01.019.144
    ro.build.date=2013年 07月 24日 星期三 03:06:47 CST
    ro.build.date.utc=1374606407
    ro.build.type=user
    ro.build.user=
    ro.build.host=ThinkCentre2-XXXX
    ro.build.tags=test-keys
    ro.product.model=roamer2
    ro.product.external_model=ZTE OPEN
    ro.product.brand=ZTE
    ro.product.name=roamer2
    ro.product.device=roamer2
    ro.product.board=roamer2
    ro.product.cpu.abi=armeabi-v7a
    ro.product.cpu.abi2=armeabi
    ro.product.manufacturer=ZTE
    ro.product.locale.language=en
    ro.product.locale.region=US
    ro.wifi.channels=
    ro.board.platform=msm7627a
    ro.build.product=roamer2
    ro.build.description=roamer2-user 4.0.4 IMM76D eng..20130724.030603 test-keys
    ro.build.fingerprint=ZTE/roamer2/roamer2:4.0.4/IMM76D/eng..20130724.030603:user/test-keys
    ro.build.characteristics=default
    rild.libpath=/system/lib/libril-qc-1.so
    rild.libargs=-d /dev/smd0
    persist.rild.nitz_plmn=
    persist.rild.nitz_long_ons_0=
    persist.rild.nitz_long_ons_1=
    persist.rild.nitz_long_ons_2=
    persist.rild.nitz_long_ons_3=
    persist.rild.nitz_short_ons_0=
    persist.rild.nitz_short_ons_1=
    persist.rild.nitz_short_ons_2=
    persist.rild.nitz_short_ons_3=
    ril.subscription.types=NV,RUIM
    DEVICE_PROVISIONED=1
    debug.sf.hw=1
    debug.composition.7x27A.type=mdp
    debug.composition.7x25A.type=mdp
    dalvik.vm.heapsize=128m
    persist.cne.UseCne=none
    persist.cne.bat.range.low.med=30
    persist.cne.bat.range.med.high=60
    persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
    persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
    persist.cne.bwbased.rat.sel=false
    persist.cne.snsr.based.rat.mgt=false
    persist.cne.bat.based.rat.mgt=false
    persist.cne.rat.acq.time.out=30000
    persist.cne.rat.acq.retry.tout=0
    persist.cne.fmc.mode=false
    persist.cne.fmc.init.time.out=30
    persist.cne.fmc.comm.time.out=130
    persist.cne.fmc.retry=false
    media.stagefright.enable-player=true
    media.stagefright.enable-meta=false
    media.stagefright.enable-scan=true
    media.stagefright.enable-http=true
    media.stagefright.enable-fma2dp=true
    media.stagefright.enable-aac=true
    media.stagefright.enable-qcp=true
    ro.opengles.version=131072
    ro.use_data_netmgrd=true
    persist.data.ds_fmc_app.mode=0
    persist.ims.regmanager.mode=0
    ro.bluetooth.request.master=true
    ro.qualcomm.bluetooth.sap=false
    ro.bluetooth.remote.autoconnect=true
    persist.sys.strictmode.visual=false
    persist.omh.enabled=1
    ro.config.ehrpd=true
    ro.qualcomm.cabl=1
    ro.fm.analogpath.supported=true
    ro.fm.transmitter=false
    ro.fm.mulinst.recording.support=false
    ro.hw_plat=7x27a
    ro.emmc.sdcard.partition=18
    ro.screen.layout=normal
    debug.enabletr=false
    debug.camcorder.disablemeta=0
    persist.fuse_sdcard=false
    debug.camera.landscape=true
    ro.max.fling_velocity=4000
    hwui.render_dirty_regions=false
    httplive.enable.discontinuity=true
    power.webview.DM=false
    dalvik.vm.heapstartsize=5m
    dalvik.vm.heapgrowthlimit=36m
    org.bluez.device.conn.type=boolean
    keyguard.no_require_sim=true
    ro.com.android.dataroaming=false
    ro.com.android.dateformat=MM-dd-yyyy
    ro.config.ringtone=Ring_Synth_04.ogg
    ro.config.notification_sound=pixiedust.ogg
    ro.config.alarm_alert=Alarm_Classic.ogg
    ro.vendor.extension_library=/system/lib/libqc-opt.so
    ro.display.colorfill=1
    ro.moz.ril.emergency_by_default=true
    ro.moz.omx.hw.max_width=640
    ro.moz.omx.hw.max_height=480
    ro.moz.cam.0.sensor_offset=270
    ro.moz.ril.simstate_extra_field=true
    persist.sys.ztelog.enable=1
    persist.radio.add_power_save=1
    ro.sensor.arch.type=new
    net.bt.name=Android
    net.change=net.bt.name
    dalvik.vm.stack-trace-file=/data/anr/traces.txt
    ro.factorytest=0
    ro.serialno=ROAMER2
    ro.bootmode=unknown
    ro.baseband=msm
    ro.carrier=unknown
    ro.bootloader=unknown
    ro.hardware=roamer2
    ro.revision=0
    ro.emmc=0
    init.svc.recovery=running
    Finding update package...
    I:Update location: /sdcard/updates/fota/update.zip
    Opening update package...
    I:1 key(s) loaded from /res/keys
    Verifying update package...
    I:comment is 1746 bytes; signature 1728 bytes from end
    I:whole-file signature verified against key 0
    I:verify_file returned 0
    Installing update...
    try_update_binary(path(/sdcard/updates/fota/update.zip))
    radio.diff not found
    Verifying current system...Failed to mount /dev/block/mtdblock4 on /cache: Device or resource busy
    mtd mount of cache failed: Device or resource busy
    51191808 bytes free on /cache (5714 needed)
    applying patch to /system/build.prop
    "/system/build.prop" is already target; no patch needed
    Removing unneeded files...
    Patching system files...
    Symlinks and permissions...
    script result was [/system]

Maybe you are looking for

  • Iphone orginal Logo Freeze

    umm my ihone got few problems 1.Main is that when i charge it it put the battery with red low and a N sign saying it charge but i let it charge for like a hour and when i take plug out few seconds it turns off 2.My power button is Jam 3.Just a minute

  • Close the application from a window or a view

    Hi, I need to check some prerequisities in the WDDOINIT of a window. If they are not available I send a pop up window to confirm to the user with the missing information. When the Ok button is selected I would like the application to be exit, I mean

  • Problem to install LR trial - why?

    Hi, I have downloaded LR trial V 4.3 from here: https://www.adobe.com/cfusion/tdrc/index.cfm?product=photoshop_lightroom&loc=de and have problems to install it. My system runs under Windows Vista, all service packs etc. installed. The download worked

  • Using BC poplet lightbox for iframe content?

    Greetings! I'm having issues where BC's poplet lightbox is preventing our other lightbox script from working. Is there a way present iframe content using BC's poplet lightbox by giving the content a new "rel" tag?

  • Upgrade NW7.0(Java Only) to NW7.1 CE/NW7.2 CE

    Hi, Does anybody know if there are any tools(SAPINST,JUP, etc.,) available in SMP(service market place) for upgrading NW7.0(Java Only) to NW7.1 CE/NW7.2 CE? Thanks, regards, Krishna