Database Users

OTA Update comming EVERYONE please read

we have the link, so no need for this, thanks to everone who tried to help

Found this link stating an update but havent received it yet. Tried updating on my phone but says my software is up to date.
http://www.androidspin.com/2010/05/01/droid-incredible-gets-ota-update/

binny1007 said:
If someone gets the update, can you please do this before you accept it. and post the logcat.txt? Please this may help rooting.
How to get the URL for the OTA zip the following way:
Run logcat on the pc and accept the update on the phone
$ adb logcat > logcat_accept.txt
This will sit like this (it continues to log output into the output file) until the phone reboots. At that point, the adb logcat job will terminate, and the name of the zip file will be indicated in the logfile in a message similar to:
W/SystemUpdateHelper( 64): !!! REBOOTING TO INSTALL /cache/
You should see a link in the file like https://android.clients.google.com/updates/partner/*****
Thank you for whoever can get this done
Click to expand...
Click to collapse
would you care to explain the significance of that link? do you believe you will be able to dl any files from it. backwards engineering?

Hero_Over said:
would you care to explain the significance of that link? do you believe you will be able to dl any files from it. backwards engineering?
Click to expand...
Click to collapse
Well number one it will allow us to see what files they are changing and number too it will allow everyone to update before they get there push notification.

Should we all accept the update?...Meaning could the update close an exploit that can be used for rooting (Like the Droid Eris)?

Will be keeping an eye open and grab this for sure.....
I think that this may be in result of the north Carolina state issues?
Read over at engadet mobile.....

NC issues should be fixed. Are you still seeing reboots?

I haven't heard of *anyone* pulling down this update other than the guy that originally posted it at Phandroid.
Maybe he was just part of a test group and the patch isn't actually being pushed out yet.

Thats what I was thinking. Because Ive not seen anyone mention having the update on any other sites.

According to phandroid its only for people that pay for the corporate email.. ie 44.99 data/email package

The north Carolina issues have already been fixed, I am in Greensboro, NC and haven't had a single reboot since Friday night.

just got it...
should i install it?

https://android.clients.google.com/packages/incrediblec/OTA_IncredibleC_Verizon_WWE_1.22.605.2_1.22.605.0_release_sign.a33bc3bf.zip
Got the link

For people that do install, will it make root impossible? Thanks.

I've got the update message on my phone, do you still want the file and if so how do I get it

I do not have the 44.99 corporate package and I got the OTA update notice. I did install prior to seeing the request re logcat...

binny1007 said:
If someone gets the update, can you please do this before you accept it. and post the logcat.txt? Please this may help rooting.
Thank you for whoever can get this done
Click to expand...
Click to collapse
is this what you want? i've been posting this all day at androidforums.com but nobody has said if thats what they want

I had the corporate package email up until yesterday I changed it, but it wasnt until today that I woke up this morning and was prompted for an update. I chose to install the update but nothing happened and then the prompt went away and my phone says its up to date even though I didnt update it. Weird.

Deleted [redundancy]

Here is the logcat of the OTA Update 5-6-2010
Code:
W/SystemUpdateHelper( 83): !!! REBOOTING TO INSTALL /cache/OTA_IncredibleC_Verizon_WWE_1.22.605.2_1.22.605.0_release_sign.a33bc3bf.zip !!!
D/ ( 83): unable to unlink '/cache/recovery/command': No such file or directory (errno=2)
D/ ( 83): unable to unlink '/cache/recovery/log': No such file or directory (errno=2)
D/MountService( 83): Shutting down
D/vold ( 56): dispatch_cmd(eject_media:/sdcard):
D/MountListener( 83): handleEvent volume_ejecting:/sdcard
I/vold ( 56): volmngr quick stop umount(/sdcard) attempt 1 (Device or resource busy)
I/BootReceiver( 589): Got intent with action android.intent.action.MEDIA_EJECT
D/DiskCache( 589): Wrote index with 134 records.
I/BatteryStatsImpl( 83): notePhoneSignalStrengthLocked: 3->2
D/BluetoothHandsfree( 152): cdmaDbmEcioToSignal(cdmaDbm:-88, cdmaEcio:-55)
D/BluetoothHandsfree( 152): cdmaDbmEcioToSignal(evdoEcio:-10, evdoSnr:5)
I/vold ( 56): volmngr quick stop umount(/sdcard) attempt 2 (Device or resource busy)
I/vold ( 56): volmngr quick stop umount(/sdcard) attempt 3 (Device or resource busy)
I/vold ( 56): volmngr quick stop umount(/sdcard) attempt 4 (Device or resource busy)
I/vold ( 56): volmngr quick stop umount(/sdcard) attempt 5 (Device or resource busy)
W/vold ( 56): Volume /sdcard is busy (-1) - uncaging the reaper
W/vold ( 56): Reaper here - working on /sdcard
W/vold ( 56): volmngr reaper umount(/sdcard) attempt 1 (Device or resource busy)
D/DiskCache( 589): Wrote index with 5 records.
D/DiskCache( 589): Wrote index with 45 records.
D/DiskCache( 589): Wrote index with 8 records.
D/DiskCache( 589): Wrote index with 7 records.
I/CacheService( 589): Computing dirty sets.
W/vold ( 56): volmngr reaper umount(/sdcard) attempt 2 (Device or resource busy)
W/vold ( 56): volmngr reaper umount(/sdcard) attempt 3 (Device or resource busy)
W/vold ( 56): volmngr reaper umount(/sdcard) attempt 4 (Device or resource busy)
W/vold ( 56): volmngr reaper umount(/sdcard) attempt 5 (Device or resource busy)
E/vold ( 56): KillProcessesWithOpenFiles /sdcard
E/vold ( 56): process com.cooliris.media (589) has open file /sdcard/Android/data/com.cooliris.media/cache/local-skip-cachechunk_0
E/vold ( 56): Killing process 589
E/vold ( 56): process com.metago.astro (3519) has open file /sdcard/tmp/.astro/astro.db
E/vold ( 56): Killing process 3519
W/vold ( 56): volmngr reaper umount(/sdcard) attempt 6 (Device or resource busy)
I/ActivityManager( 83): Process com.metago.astro (pid 3519) has died.
I/WindowManager( 83): WIN DEATH: Window{4642c698 com.metago.astro/com.metago.astro.FileManagerActivity paused=false}
D/Zygote ( 59): Process 3519 terminated by signal (15)
I/ActivityManager( 83): Process com.cooliris.media (pid 589) has died.
D/Zygote ( 59): Process 589 terminated by signal (15)
E/vold ( 56): KillProcessesWithOpenFiles /sdcard
W/vold ( 56): volmngr reaper umount(/sdcard) attempt 7 (Unknown error: 0)
I/vold ( 56): Reaper sucessfully unmounted /sdcard
D/vold ( 56): Volume /sdcard state change from mounted -> unmounted
D/MountListener( 83): handleEvent volume_unmounted:/sdcard
D/ExternalStorageAgent( 206): db sync=>12ms

Rooting HTC magic

Hello,
I've problems to install Cyanogen 4.2 on my HTC Magic.
My setup:
HTC Magic (Vodafone)
Sapphire PVT 32B ENG S-OFF H
HBOOT-1.33.2005 (SAPP10000)
CPLD10
RADIO-2.22.19.26i
Apr 20 2009,15:30:43
- Android SDK installed on PC.
- USB driver installed.
- started "CMD" and give command:
fastboot boot cm-recovery-1.4.img
- Now I've maked a nandroid backup.
- Connected to USB and copy nandroid map to my PC.
- Formatted sdcard.
- Placed cm-recovery-1.4.img and update.zip to my SDcard.
- Started fastboot on my Magic.
- fastboot boot cm-recovery-1.4.img
- Wipe/reset factory.
- Apply update.zip.
Now my phone is doing the update and says everything is OK. When the update finisched I press restart. On startup only the Vodafone logo displayed. After 30 minutes only logo.
Whats going wrong?
I've read something about wrong spl package? Someone know this issue?
Also when I do the command adb devices there are no device found. When I check my Device manager on the PC I see an Android Phone and the drivers where installed correctly.
adblogcat command :
Code:
* daemon not running. starting it now *
* daemon started successfully *
- waiting for device -
I//system/xbin/busybox( 48): +++ "This is your world, these are your people. Y
ou can live for yourself today, or help build tomorrow for everyone."
I//system/xbin/busybox( 48): +++ Welcome to Android 1.6 / CyanogenMod-4.2
I//system/xbin/busybox( 48): [: 1: unknown operand
I/logwrapper( 48): /system/xbin/busybox terminated by exit(0)
I/DEBUG ( 73): debuggerd: Oct 23 2009 18:52:50
E/flash_image( 79): error opening /data/recovery.img: No such file or director
y
I/vold ( 72): Android Volume Daemon version 2.0
I/vold ( 72): New MMC card 'USD ' (serial 103819993) added @ /devices/plat
form/msm_sdcc.2/mmc_host/mmc1/mmc1:b368
I/vold ( 72): Disk (blkdev 179:0), 15659008 secs (7646 MB) 1 partitions
I/vold ( 72): New blkdev 179.0 on media USD , media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:b368, Dpp 1
I/vold ( 72): Partition (blkdev 179:1), 15650816 secs (7642 MB) type 0xb
I/vold ( 72): New blkdev 179.1 on media USD , media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:b368, Dpp 0
I/vold ( 72): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mm
c1:b368/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 72): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 72): Volmgr not ready to handle device
D/vold ( 72): Bootstrapping complete

Mod edit: not dev related, moved to general

Rooting HTC Magic on OSX
I am so confused. I'm using Mac OSX and I think I followed everything that needs to be done based on the guide found on Full Update Guide - G1/Dream/Magic32A Firmware to CyanogenMod. But when I get to step 5 under Installation, I'm "command not found" error on Terminal. I hope there's a step-by-step or screen-by-screen tutorial on this, starting from installing the SDK. Sigh

Did you flash the DRC83_defanged.zip first? You need that for CM4 ROMs.

jULY 2010 MR4 logcat

W/SystemUpdateHelper( 74): !!! REBOOTING TO INSTALL /cache/8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip !!!
D/ ( 74): unable to unlink '/cache/recovery/command': No such file or directory (errno=2)
D/ ( 74): unable to unlink '/cache/recovery/log': No such file or directory (errno=2)

[Q] Market/downloads errors, Couldn't find Pathname for completed download URI:

I've been getting the follow errors lately
Code:
D/vending ( 2898): [17] LocalAssetDatabase.notifyListener(): 3274705866231794954
/ DOWNLOAD_PENDING
I/vending ( 2898): [17] RequestDispatcher$RequestContext.<init>(): Some requests
use secure token but dont require SSL. Forcing SSL.
D/vending ( 2898): [220] AssetDownloader.downloadAndInstall(): Initiating Downlo
ad for 1 applications.
I/vending ( 2898): [220] DownloadManagerUtil.enqueueDownload(): Enqueue for down
load [email protected]
D/vending ( 2898): [220] LocalAssetDatabase.notifyListener(): 327470586623179495
4 / null
D/vending ( 2898): [220] LocalAssetDatabase.notifyListener(): 327470586623179495
4 / DOWNLOADING
D/dalvikvm( 2293): GC_FOR_MALLOC freed 11924 objects / 895944 bytes in 75ms
D/DownloadManager( 2293): download aborted - not enough free space in internal s
torage
D/vending ( 2898): [221] AssetDownloader$DownloadManagerBroadcastReceiver.handle
DownloadCompletedAction(): Got a download completed intent.
I/vending ( 2898): [221] AssetDownloader$DownloadManagerBroadcastReceiver.startN
extDownload(): Found Paused URI null
I/vending ( 2898): [221] AssetDownloader$DownloadManagerBroadcastReceiver.startN
extDownload(): No more paused downloads.
I/vending ( 2898): [221] AssetDownloader$DownloadManagerBroadcastReceiver.getDow
nloadStatus(): Unexpected status from download - 498
W/vending ( 2898): [221] AssetDownloader$DownloadManagerBroadcastReceiver.handle
DownloadCompletedAction(): Couldn't find pathname for completed download URI: content://downloads/download/7 -- assuming the download failed.
D/vending ( 2898): [221] LocalAssetDatabase.notifyListener(): 327470586623179495
4 / DOWNLOAD_FAILED
Anyone know what the issue is? I googled the term, but there are 0 results.
I've got a2sd cachepart (512ext), running wildmonk's 112010, geo411m frg83d, wifi calling

Specifically the downloads\ download error I'm getting
Sent from my Nexus One using XDA App
[edit]
I've tried to unmount/remount system/data via amon_ra, repair UID, a2sd reinstall, a2sd check, a2sd repair, reflash.
Still getting: "Couldn't find pathname for completed download URI: context://downloads/download/3 -- assuming the download failed"
All that's left is data wipe...

Tested few things, seems the sym links are broken, would a wipe plus reflash fix it?
Sent from my Nexus One using XDA App

Had the same problem.
After clearing the cache of the Market app the problem did disappear.

I've done that about a thousand times, still getting the same error.
Sent from my Nexus One using XDA App

as root from adb or terminal
chmod 777 /cache

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