Database Users

unable to backup efs

DDJP6 indian stock froyo rooted with z4root and have titanium backup
i am unable to take backup of efs
here's the log
E:\i9000\AndroidSDK\tools>adb shell
$ busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 152.0M 0 152.0M 0% /dev
df: /mnt/.lfs: Function not implemented
tmpfs 152.0M 0 152.0M 0% /mnt/asec
/dev/block/stl9 275.8M 256.6M 19.2M 93% /system
/dev/block/mmcblk0p2 1.9G 395.3M 1.5G 21% /data
/dev/block/stl10 127.2M 15.8M 111.4M 12% /dbdata
/dev/block/stl11 30.1M 2.0M 28.1M 7% /cache
/dev/block/stl3 5.9M 5.0M 936.0K 85% /efs
/dev/block/vold/179:1
13.4G 2.3G 11.1G 17% /mnt/sdcard
/dev/block/vold/179:9
1.8G 550.4M 1.3G 29% /mnt/sdcard/external_sd
df: /mnt/secure/asec: Permission denied
/dev/block/dm-0 3.1M 1.6M 1.5M 51% /mnt/asec/com.codingcave
man.SoloTrial-1
/dev/block/dm-1 3.1M 1.4M 1.6M 46% /mnt/asec/com.ubermind.i
lightr.free-1
/dev/block/dm-2 3.1M 1.2M 1.9M 39% /mnt/asec/carnero.cgeo-1
/dev/block/dm-3 3.1M 1.5M 1.5M 49% /mnt/asec/com.glympse.an
droid.glympse-1
/dev/block/dm-4 8.1M 6.5M 1.6M 80% /mnt/asec/com.theveganro
bot-2
/dev/block/dm-5 3.1M 1.5M 1.6M 49% /mnt/asec/com.adobe.read
er-1
/dev/block/dm-6 3.1M 1.7M 1.4M 55% /mnt/asec/com.heroplanet
.blackgothic3dwallpapers-1
/dev/block/dm-7 2.0M 232.0K 1.8M 11% /mnt/asec/gabriel.metron
ome-1
/dev/block/dm-8 4.1M 2.1M 2.0M 51% /mnt/asec/com.droidhen.g
ame.superman-1
/dev/block/dm-9 2.0M 128.0K 1.9M 6% /mnt/asec/org.cohortor.g
strings-1
/dev/block/dm-10 4.1M 2.9M 1.1M 72% /mnt/asec/com.zodttd.psx
lite-1
/dev/block/dm-11 3.1M 1.1M 1.9M 37% /mnt/asec/com.google.and
roid.apps.unveil-1
/dev/block/dm-12 7.1M 5.5M 1.7M 77% /mnt/asec/com.waze-1
/dev/block/dm-13 3.1M 1.5M 1.5M 49% /mnt/asec/com.batterypow
eredgames.lightracer3dbasic-1
/dev/block/dm-14 4.1M 2.1M 2.0M 51% /mnt/asec/com.google.and
roid.stardroid-1
/dev/block/dm-15 2.0M 108.0K 1.9M 5% /mnt/asec/com.dev47apps.
droidcam-1
/dev/block/dm-16 14.2M 12.3M 1.9M 87% /mnt/asec/com.rovio.angr
ybirdsseasons-1
/dev/block/dm-17 7.1M 5.3M 1.8M 75% /mnt/asec/com.yahoo.mobi
le.client.android.imvideo-1
/dev/block/dm-18 4.1M 2.0M 2.0M 50% /mnt/asec/com.droidhen.f
ruit-1
/dev/block/dm-19 15.2M 13.3M 1.9M 87% /mnt/asec/org.mozilla.fe
nnec-1
/dev/block/dm-20 7.1M 5.3M 1.8M 75% /mnt/asec/com.com2us.sli
ceit-1
/dev/block/dm-21 2.0M 484.0K 1.6M 23% /mnt/asec/com.google.zxi
ng.client.android-1
$ su
su
# busybox cp -a /efs /sdcard/
busybox cp -a /efs /sdcard/
cp: can't preserve ownership of '/sdcard/efs/.android': Operation not permitted
cp: can't preserve ownership of '/sdcard/efs/.nv_data.bak': Operation not permit
ted
cp: can't preserve ownership of '/sdcard/efs/imei/mps_code.dat': Operation not p
ermitted
cp: can't preserve ownership of '/sdcard/efs/imei/bt.txt': Operation not permitt
ed
cp: can't preserve ownership of '/sdcard/efs/imei': Operation not permitted
cp: can't preserve ownership of '/sdcard/efs/.nv_state': Operation not permitted
cp: can't preserve ownership of '/sdcard/efs/.nv_data.bak.md5': Operation not pe
rmitted
cp: can't preserve ownership of '/sdcard/efs/nv_data.bin': Operation not permitt
ed
cp: can't preserve ownership of '/sdcard/efs/nv_data.bin.md5': Operation not per
mitted
cp: can't preserve ownership of '/sdcard/efs/.nv2.bak': Operation not permitted
cp: can't preserve ownership of '/sdcard/efs/.nv2.bak.md5': Operation not permit
ted
cp: can't preserve ownership of '/sdcard/efs': Operation not permitted
#
Click to expand...
Click to collapse
please help

+help?...................................

try:
cp -r /efs /sdcard

after cp -r /efs /sdcard/
it goes back to #
i tried but i am still unable to backup efs

anonymusneo said:
after cp -r /efs /sdcard/
it goes back to #
i tried but i am still unable to backup efs
Click to expand...
Click to collapse
It goes back to # because there is no error backing up /efs to the internal sd-card, /efs folder should be there now.

[Ramad] said:
It goes back to # because there is no error backing up /efs to the internal sd-card, /efs folder should be there now.
Click to expand...
Click to collapse
but the total size of the /efs Folder it creates is hardly 4 MB ???

gday
just bumping this thread as i have the same question..
is the efs folder usually around 4mb? need to know if this backup worked.
thanks.

Compare disk usage for both directories with the 'du' command -
du -s /efs
du -s /mnt/sdcard/efs
Skip the -s if you want to compare each file size. Also, you might want to get superuser access before you do the copy operation (with 'su')
PS: I don't have the phone with me right now, but I assume 'du' is available on the system or as a part of busybox.

[Q] Storage space running out - but what's using it?

I realize there's plenty of threads with more or less the exact same topic. But I haven't found an answer in any of them that helps my situation.
Alright here's the deal:
I'm getting the "Storage space running out"-notification. And apps are starting to FC.. My phone is a i9505 and I'm currently running Carbon. But this was a problem with CM 10.2 too.
Here's what confuses me:
Code:
[email protected]:/data # busybox df -m
Filesystem 1M-blocks Used Available Use% Mounted on
...
/dev/block/platform/msm_sdcc.1/by-name/userdata
9351 9300 50 99% /data
...
/dev/fuse 9351 9300 50 99% /mnt/shell/emulated
...
/dev/block/vold/179:33
30688 25851 4837 84% /storage/sdcard1
Those should be the interesting bits (I'm showing off my 32GB external card here as well). Right, so I'm using 99%, or 9300MB.
Now here's how I check what's taking up the space:
Code:
[email protected]:/ # du -d1 -m /data
1 /data/dontpanic
3404 /data/media
1 /data/misc
1 /data/local
252 /data/data
1 /data/app-private
176 /data/app-asec
203 /data/app-lib
939 /data/app
1 /data/property
1 /data/ssh
1 /data/radio
321 /data/dalvik-cache
1 /data/resource-cache
1 /data/lost+found
1 /data/drm
1 /data/mediadrm
1 /data/security
4 /data/system
1 /data/wpstiles
1 /data/wiper
1 /data/shared
1 /data/fota
1 /data/time
1 /data/bluetooth
1 /data/audio
1 /data/.ssh
1 /data/tombstones
1 /data/nfc
1 /data/user
6 /data/qcks
1 /data/backup
1 /data/anr
5302 /data
du sums it up for us: 5302MB on /data
DiskUsage is showing me "System data" is taking up the space, but it doesn't tell me what or where:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've checked solutions mentioned in related threads (all over the internets):
* The "/datadata" issue - I don't have this directory
* The "lost + found" - It's 1MB as you can see
* The "/data/log" issue - I don't have this directory
So what am I missing?

Well wouldn't you know. After a reboot the usage is down and df reports the same as du. I'm still confused as to what took up the space though.. I even got Java exceptions (from DiskUsage) saying the disk was full.

Problem installing Google Calendar

While installing Google Calendar, I get the following from logcat:
Code:
D/Finsky (13807): [1] DownloadImpl.setState: com.google.android.calendar from DOWNLOADING to SUCCESS.
D/Finsky (13807): [1] DownloadQueueImpl.onComplete: com.google.android.calendar: onComplete
D/Finsky (13807): [1] DownloadQueueImpl.remove: Download com.google.android.calendar removed from DownloadQueue
I/installd( 220): free_cache(0) avail 10924060672
D/MarketUpdateReceiver( 3549): market is installing: com.google.android.calendar
W/ActivityManager( 918): No content provider found for permission revoke: file:///data/user/0/com.android.providers.downloads/cache/downloadfile.apk
D/Finsky (13807): [1] PackageVerificationReceiver.checkPrerequisites: Skipping verification because own installation
D/Finsky (13807): [1] PackageVerificationReceiver.onReceive: Verification requested, id = 2
W/ActivityManager( 918): No content provider found for permission revoke: file:///data/user/0/com.android.providers.downloads/cache/downloadfile.apk
I/PackageManager( 918): Copying native libraries to /data/app-lib/vmdl259487226
D/dalvikvm( 918): GC_CONCURRENT freed 4178K, 15% free 38955K/45648K, paused 5ms+8ms, total 121ms
D/dalvikvm( 918): WAIT_FOR_CONCURRENT_GC blocked 79ms
D/dalvikvm( 918): WAIT_FOR_CONCURRENT_GC blocked 70ms
D/dalvikvm( 918): GC_FOR_ALLOC freed 5321K, 15% free 38826K/45648K, paused 105ms, total 105ms
E/PackageManager( 918): Package com.google.android.calendar has no signatures that match those in shared user com.google.android.calendar.uid.shared; ignoring!
W/PackageManager( 918): Package couldn't be installed in /data/app/com.google.android.calendar-1.apk
D/dalvikvm( 918): GC_EXPLICIT freed 1738K, 16% free 38772K/45648K, paused 6ms+15ms, total 123ms
D/Finsky (13807): [290] 1.packageInstalled: Package install status for "com.google.android.calendar" is -8
D/Finsky (13807): [1] InstallerTask.cancelCleanup: Cancel running installation of com.google.android.calendar
D/MarketUpdateReceiver( 3549): market has decided not to install: com.google.android.calendar
D/dalvikvm(13807): GC_CONCURRENT freed 8100K, 23% free 41142K/52892K, paused 4ms+18ms, total 94ms
W/View (13807): requestLayout() improperly called by android.widget.TextView{4432dd70 VFED..CL ......ID 30,18-1050,408 #7f08001e app:id/section_content} during layout: running second layout pass
W/View (13807): requestLayout() improperly called by android.widget.TextView{4433ff68 VFED..CL ......ID 30,18-1050,90 #7f08001e app:id/section_content} during layout: running second layout pass
I've found workarounds to fix this by messing with package.xml files, but then on the next nightly, I'll have to do that all over again.
I'm on Nexus 5 (hammerhead).

bhundven said:
While installing Google Calendar, I get the following from logcat:
Code:
D/Finsky (13807): [1] DownloadImpl.setState: com.google.android.calendar from DOWNLOADING to SUCCESS.
D/Finsky (13807): [1] DownloadQueueImpl.onComplete: com.google.android.calendar: onComplete
D/Finsky (13807): [1] DownloadQueueImpl.remove: Download com.google.android.calendar removed from DownloadQueue
I/installd( 220): free_cache(0) avail 10924060672
D/MarketUpdateReceiver( 3549): market is installing: com.google.android.calendar
W/ActivityManager( 918): No content provider found for permission revoke: file:///data/user/0/com.android.providers.downloads/cache/downloadfile.apk
D/Finsky (13807): [1] PackageVerificationReceiver.checkPrerequisites: Skipping verification because own installation
D/Finsky (13807): [1] PackageVerificationReceiver.onReceive: Verification requested, id = 2
W/ActivityManager( 918): No content provider found for permission revoke: file:///data/user/0/com.android.providers.downloads/cache/downloadfile.apk
I/PackageManager( 918): Copying native libraries to /data/app-lib/vmdl259487226
D/dalvikvm( 918): GC_CONCURRENT freed 4178K, 15% free 38955K/45648K, paused 5ms+8ms, total 121ms
D/dalvikvm( 918): WAIT_FOR_CONCURRENT_GC blocked 79ms
D/dalvikvm( 918): WAIT_FOR_CONCURRENT_GC blocked 70ms
D/dalvikvm( 918): GC_FOR_ALLOC freed 5321K, 15% free 38826K/45648K, paused 105ms, total 105ms
E/PackageManager( 918): Package com.google.android.calendar has no signatures that match those in shared user com.google.android.calendar.uid.shared; ignoring!
W/PackageManager( 918): Package couldn't be installed in /data/app/com.google.android.calendar-1.apk
D/dalvikvm( 918): GC_EXPLICIT freed 1738K, 16% free 38772K/45648K, paused 6ms+15ms, total 123ms
D/Finsky (13807): [290] 1.packageInstalled: Package install status for "com.google.android.calendar" is -8
D/Finsky (13807): [1] InstallerTask.cancelCleanup: Cancel running installation of com.google.android.calendar
D/MarketUpdateReceiver( 3549): market has decided not to install: com.google.android.calendar
D/dalvikvm(13807): GC_CONCURRENT freed 8100K, 23% free 41142K/52892K, paused 4ms+18ms, total 94ms
W/View (13807): requestLayout() improperly called by android.widget.TextView{4432dd70 VFED..CL ......ID 30,18-1050,408 #7f08001e app:id/section_content} during layout: running second layout pass
W/View (13807): requestLayout() improperly called by android.widget.TextView{4433ff68 VFED..CL ......ID 30,18-1050,90 #7f08001e app:id/section_content} during layout: running second layout pass
I've found workarounds to fix this by messing with package.xml files, but then on the next nightly, I'll have to do that all over again.
I'm on Nexus 5 (hammerhead).
Click to expand...
Click to collapse
Hmm, that's usually included in gapps so should be an update not a raw install... I'll see if it's not included in PA's mini gapps.
Which gapps variant are you using? Most of the Omni team are using PA gapps. (need to document this better...) If you're having this issue with PA Gapps, then I wonder if it might be related to some of the signature issues that have been breaking OmniSwitch too.
Please file a bugreport in JIRA on this with more detail.

Entropy512 said:
Hmm, that's usually included in gapps so should be an update not a raw install... I'll see if it's not included in PA's mini gapps.
Which gapps variant are you using? Most of the Omni team are using PA gapps. (need to document this better...) If you're having this issue with PA Gapps, then I wonder if it might be related to some of the signature issues that have been breaking OmniSwitch too.
Please file a bugreport in JIRA on this with more detail.
Click to expand...
Click to collapse
Damn, I used slim gapps. :facepalm:
I'll do a TiB and reinstall with pa gapps.
It's what I had on my phone's sd, I should have used pa gapps.
Do you still want me to file a bug?

[GUIDE] How to Logcat

Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
This is a share.original thread

Hmmm.. I think all can see original guide in Android section...
There's no need of posting it again..
Anyway.. Thanks..

TheStrix said:
Hmmm.. I think all can see original guide in Android section...
There's no need of posting it again..
Anyway.. Thanks..
Click to expand...
Click to collapse
I think that it is good for moto E users, most of them are newbies, so they won't have to search a lot

What's the difference BTW logcat and androids inbuilt Bug report function
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1033 using Tapatalk

jaspreet997 said:
What's the difference BTW logcat and androids inbuilt Bug report functionView attachment 2751421
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Logcat gives you the messages of the system logs and you can submit them to a developer manually. Bug report is kinda an automatic thing that keeps track of your errors

NST Issues after a botched cleaning process

Hi,
I was wondering if anyone can help me figuring out what happened to my NST.
I was checking my NST hidden settings menu (NSTHiddenSettings.apk) when I pressed one the generic settings buttons (they appears at the bottom of the menu and they look all the same). One of these buttons initiated a "cleaning" process + reboot that I could not stop.
The end result of this was:
My NST was hanging after the reboot. I resetted to factory settings using NookManager and upgraded to 1.2.2 US firmware (my Nook has originally a 1.2.0 UK firmware), registered the device and re-rooted again: It all went well.
However NookManager "'informed me" that the NookButtons Mod APK was not installed during the rooting process.
I understood why when I tried install more apps. The system would not allow me to because every time I try to install a new apk I get a "memory full" message (mind you: the Nook is just rooted, so plenty of space, in theory).
Moreover, "back"/menu/notifications buttons on the top toolbar disappear when I access the settings menu
I have the feeling the file system is quite messed up (e.g. .orig files that should not be there), however since I do not have a backup copy (yes, silly me!), I cannot verify it. I have copied my Nook filesystem, and I was wondering if you could gather what happened to it and how I can fix it.
Code:
drwxrwx--- system system 1970-01-01 01:00 rom
drwxrwxrwt root root 2019-02-03 20:34 sqlite_stmt_journals
drwxrwxrwx system system 2019-02-03 20:34 sdcard
drwxrwxr-x system sdcard_rw 1970-01-01 01:00 media
drwxrwx--- system cache 2019-02-03 15:09 cache
drwxrwxrwx root root 2019-02-03 20:34 tmp
lrwxrwxrwx root root 2019-02-03 20:34 etc -> /system/etc
drwxrwx--x system system 2019-02-03 20:34 data
-rw-r--r-- root root 324 2019-02-03 15:44 env.txt
-rwxr-x--- root root 128000 2019-02-03 15:44 init
-rwxr-x--- root root 1677 2019-02-03 15:44 init.goldfish.rc
dr-xr-xr-x root root 1970-01-01 01:00 proc
drwxr-x--- root root 2019-02-03 15:44 sbin
drwxr-xr-x root root 1970-01-01 01:00 sys
drwxr-xr-x root root 2019-02-03 15:44 system
-rw-r--r-- root root 118 2019-02-03 15:44 default.prop.orig
-rw-r--r-- root root 118 2019-02-03 15:44 default.prop
-rw-r--r-- root root 118 2019-02-03 15:44 init.rc.orig
-rwxr-x--- root root 19284 2019-02-03 15:44 init.rc
drwx------ root root 2017-05-17 09:47 root
drwxr-xr-x root root 2019-02-03 20:34 dev
NOTE: I have tried to factory-reset it also using the 8 failed boot ups followed by holding both bottom "page left/right" buttons. Nothing. I always end up with the same messed-up configuration.
Can anyone help me?
Marco

You're going to have to dig deeper than that to find out what's what.
First step:
Code:
# df
That will tell you what you have for disk space.

And this is what I've got:
Code:
/dev: 116520K total, 0K used, 116520K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16116K total, 3655K used, 12460K available (block size 512)
/system: 285583K total, 210512K used, 75071K available (block size 1024)
/data: 808292K total, 64200K used, 744092K available (block size 4096)
/cache: 237987K total, 6263K used, 231724K available (block size 1024)
/media: 245484K total, 40K used, 245444K available (block size 4096)
And this is just right after the rooting process. Nothing else installed.
Renate NST said:
You're going to have to dig deeper than that to find out what's what.
First step:
Code:
# df
That will tell you what you have for disk space.
Click to expand...
Click to collapse

Well, you've got the space.
The "memory full" thing might be a red herring.
The package installer copies the file to somewhere temporary before it ends up in /data/app.
It could be a permission problem.
How are you installing the app? With adb install?
Use a second window running adb logcat and look for anything that happens.

In the original NookManager thread similar issues were discussed with early versions starting about here. There are some suggested work-arounds, including adb install (useful, but annoying) and, if I recall correctly, some attempts at patches for the permissions issue.
I have seen questions regarding the "out of space" issue from time to time but it took awhile for them to bubble up to the top in my brain. Why this happens with some installations, I have no idea.

Renate,
this is interesting: [email protected] always installed the apps with PackageManager, and that's what I did this time too, and that's what gave me the "memory full" error.
However, I have now used adb install and things went pretty smooth. I installed NookMods from NM and this is the log:
Code:
D/AndroidRuntime( 2112): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I/AndroidRuntime( 2112): Heap size: -Xmx64m
D/AndroidRuntime( 2112): CheckJNI is OFF
D/dalvikvm( 2112): creating instr width table
D/AndroidRuntime( 2112): --- registering native functions ---
I/NATIVE-EPD( 2112): framebuffer_handle: 17
D/PackageParser( 788): Scanning package: /data/app/vmdl35313.tmp
I/PackageManager( 788): /data/app/vmdl35313.tmp changed; unpacking
D/installd( 745): DexInv: --- BEGIN '/data/app/vmdl35313.tmp' ---
D/dalvikvm( 2125): creating instr width table
D/dalvikvm( 2125): DexOpt: load 32ms, verify 151ms, opt 7ms
D/installd( 745): DexInv: --- END '/data/app/vmdl35313.tmp' (success) ---
I/installd( 745): move /data/dalvik-cache/[email protected]@[email protected] -> /data/dalvik-cache/[email protected]@[email protected]
D/PackageManager( 788): New package installed in /data/app/org.nookmods.ntmm.apk
D/AndroidRuntime( 2112): Shutting down VM
D/dalvikvm( 2112): DestroyJavaVM waiting for non-daemon threads to exit
D/dalvikvm( 2112): DestroyJavaVM shutting VM down
D/dalvikvm( 2112): HeapWorker thread shutting down
D/dalvikvm( 2112): HeapWorker thread has shut down
D/jdwp ( 2112): JDWP shutting down net...
I/jdwp ( 2112): adbd disconnected
D/dalvikvm( 2112): VM cleaning up
W/ResourceType( 788): Resources don't contain package for resource number 0x7f060001
I/AmazonAppstore.UpdateService( 874): Self-updating enabled: true
D/AmazonAppstore.UpdateService( 874): Adding self-update command to UpdateService
D/AmazonAppstore.UpdateService( 874): Received action: com.amazon.mas.client.framework.UpdateService.APP_WAS_INSTALLED from intent: Intent { act=com.amazon.mas.client.framework.UpdateService.APP_WAS_INSTALLED cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService (has extras) }
D/InstallReceiver( 1444): org.nookmods.ntmm
D/dalvikvm( 2112): LinearAlloc 0x0 used 625764 of 5242880 (11%)
D/dalvikvm( 788): GC freed 15270 objects / 1017944 bytes in 70ms
and the adb install message:
Code:
adb install org.nookmods.ntmm.apk
822 KB/s (170731 bytes in 0.202s)
pkg: /data/local/tmp/org.nookmods.ntmm.apk
Success
rm failed for -f, Read-only file system
May this be the problem encountered by PackageManager (and not adb install):
Code:
rm failed for -f, Read-only file system
------------------------
Incidentally, logcat keeps throwing this connectivity error at me, even though I actually registered the device succcessfully:
Code:
I/BnCloudReqMgr( 837): BnCloudRequest Service: starting now
W/ActivityManager( 788): Unable to start service Intent { act=com.bn.cloud.IRequestHandler }: not found
E/GPBRequestHelper( 837): Cannot get handle on BN Cloud Request Service
E/GPBRequestHelper( 837): com.bn.cloud.ServiceUnavailableException: Cannot bind with service: Context.bindService() failed
E/GPBRequestHelper( 837): at com.bn.cloud.RequestManagerImpl$BnCloudServiceConnection.<init>(RequestManagerImpl.java:255)
E/GPBRequestHelper( 837): at com.bn.cloud.RequestManagerImpl.<init>(RequestManagerImpl.java:217)
E/GPBRequestHelper( 837): at com.bn.cloud.BnCloudRequestManager.getRequestHandler(BnCloudRequestManager.java:29)
E/GPBRequestHelper( 837): at com.bn.cloud.GPBRequestHelper.obtainBnCloudRequestHandler(GPBRequestHelper.java:110)
E/GPBRequestHelper( 837): at com.bn.cloud.GPBRequestHelper.access$300(GPBRequestHelper.java:18)
E/GPBRequestHelper( 837): at com.bn.cloud.GPBRequestHelper$3.handleMessage(GPBRequestHelper.java:148)
E/GPBRequestHelper( 837): at android.os.Handler.dispatchMessage(Handler.java:99)
E/GPBRequestHelper( 837): at android.os.Looper.loop(Looper.java:123)
E/GPBRequestHelper( 837): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/GPBRequestHelper( 837): at java.lang.reflect.Method.invokeNative(Native Method)
E/GPBRequestHelper( 837): at java.lang.reflect.Method.invoke(Method.java:521)
E/GPBRequestHelper( 837): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/GPBRequestHelper( 837): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/GPBRequestHelper( 837): at dalvik.system.NativeStart.main(Native Method)
Renate NST said:
Well, you've got the space.
The "memory full" thing might be a red herring.
The package installer copies the file to somewhere temporary before it ends up in /data/app.
It could be a permission problem.
How are you installing the app? With adb install?
Use a second window running adb logcat and look for anything that happens.
Click to expand...
Click to collapse

We have here a total of three badly worded/misleading errors.
"Memory full"
It isn't.
"rm failed for -f"
They are trying to rm -f on something but the error message is just presuming what is immediately after "rm" must be the file name.
They didn't think that there could be some flags after "rm".
"Resources don't contain package for resource number 0x7f060001"
You're missing a resource that is referenced in some other resource (or AndroidManifest).
It's not a resource that is referenced in the code because that would be a runtime error.
The "7f" tells you that it's a user-supplied resource, the "06" tells you not much because they are issued sequentially.
My bet, probably a string referenced in AndroidManifest.
Link, please, to the apk that gives you this error.

Here it is, attached.
It is the version of nookmods contained in NookManager 0.50. (NookManager/files/data/app/org.nookmods.ntmm.apk)
NM does not install it already when I try to root the Nook. (It throws a "Nook Mods not installed" message)
Renate NST said:
We have here a total of three badly worded/misleading errors.
"Memory full"
It isn't.
"rm failed for -f"
They are trying to rm -f on something but the error message is just presuming what is immediately after "rm" must be the file name.
They didn't think that there could be some flags after "rm".
"Resources don't contain package for resource number 0x7f060001"
You're missing a resource that is referenced in some other resource (or AndroidManifest).
It's not a resource that is referenced in the code because that would be a runtime error.
The "7f" tells you that it's a user-supplied resource, the "06" tells you not much because they are issued sequentially.
My bet, probably a string referenced in AndroidManifest.
Link, please, to the apk that gives you this error.
Click to expand...
Click to collapse