OTA Update comming EVERYONE please read - Droid Incredible General

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

Related

Magic not booting

Installed a hero rom, Maxisma's, didn't like the speed so I went for MghtyMax rom instead. After reading on a few threads, I decided to update the SPL, but accidentally flashed a 32A SPL, mine is a 32B. Have now installed 1.33.2004, for the 32B, and can access recovery and fastboot. I can install roms, and different recovery programs, I am currently running Amon RA's recovery. Now, the problem, I have tried this with about 5 different roms, and every one gets stuck on the splash screen (Which is custom btw). I have attached the logcat log from cmd:
C:\SDK\tools>adb logcat
- waiting for device -
I//system/xbin/busybox( 47): +++ "In a world of deceit, open your eyes. Don't
be afraid and you realize......"
I//system/xbin/busybox( 47): +++ Welcome to Android 1.6 / CyanogenMod-4.2.9.1
I//system/xbin/busybox( 47): --- Executing firstboot.sh
I//system/xbin/busybox( 47): --- Checking filesystems
I//system/xbin/busybox( 47): e2fsck 1.41.9 (22-Aug-2009)
I//system/xbin/busybox( 47): /dev/block/mmcblk0p2: recovering journal
I//system/xbin/busybox( 47): /dev/block/mmcblk0p2: clean, 15/244320 files, 392
81/488281 blocks
I//system/xbin/busybox( 47): cp: cannot stat '/data/app-private/*': No such fi
le or directory
I//system/xbin/busybox( 47): cp: cannot stat '/data/dalvik-cache/*': No such f
ile or directory
I//system/xbin/busybox( 47): +++ Apps-to-SD successfully enabled
I/logwrapper( 47): /system/xbin/busybox terminated by exit(0)
I/DEBUG ( 132): debuggerd: Dec 17 2009 21:34:52
E/flash_image( 138): error opening /data/recovery.img: No such file or director
y
I/vold ( 131): Android Volume Daemon version 2.0
I/vold ( 131): New MMC card 'SD16G' (serial 3495231383) added @ /devices/pla
tform/msm_sdcc.2/mmc_host/mmc1/mmc1:9b35
I/vold ( 131): Disk (blkdev 179:0), 31326208 secs (15296 MB) 3 partitions
I/vold ( 131): New blkdev 179.0 on media SD16G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:9b35, Dpp 3
I/vold ( 131): Partition (blkdev 179:1), 30015625 secs (14656 MB) type 0xc
I/vold ( 131): New blkdev 179.1 on media SD16G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:9b35, Dpp 2
I/vold ( 131): Partition (blkdev 179:2), 976562 secs (476 MB) type 0x83
I/vold ( 131): New blkdev 179.2 on media SD16G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:9b35, Dpp 1
I/vold ( 131): Partition (blkdev 179:3), 318497 secs (155 MB) type 0x82
I/vold ( 131): New blkdev 179.3 on media SD16G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:9b35, Dpp 0
I/vold ( 131): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mm
c1:9b35/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 131): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 131): Volmgr not ready to handle device
D/vold ( 131): Bootstrapping complete
Click to expand...
Click to collapse
No one knows any solutions? Or how much it could cost for a repair? All I'm looking for is to get my phone usable again but I've tried undoing everything I've done so far, but I can't find the stock SPL for a Vodafone UK Magic or any nandroid backups that might fit my phone (I did have one but my laptop hard drive stopped working so I update the SLIC and installed Windows 7). I would be willing to pay for any help that would get my phone working again. Thanks.
update the spl to a higher number i'm using update.SPL_Crios_1.33.2004 (you might already be on this one)which thinks its 2005 also is you card partitioned with 3 partitions and make sure you wipe everything with wipe from recovery
Thanks for the help, no I'm not on the Crios SPL, I'm on the normal 1.33.2004. I have now sorted the problem, I wiped and partitioned many times, and downloaded a previous CyanogenMod. I don't know which one of these solved the problems but now my phone boots. I am having a problem with the phone still though, as every time I try to open a message, the app force closes, the home button will not work, and the contacts app will not open.

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)

WiFi suddenly always searching, no ssids, nothing found

Hi,
I intensively searched for my problem, but found always other non-related stuff.
Recently (last 1, 2 days) my WiFi didn't connect to any APs any more. I was using CN nightlies and franco kernel, so today I did update CN without franco. Afterwards I downgraded CN and did a radio update and now I tried the stock 4.2.2 image with the flash-all script, which also seemed to reflash my radio.
The default wifi dialog always displayed the saved wifis only. And after installing stock, the initial wifi dialog displayed "searching" only for a very long time. Sometimes I see some networks and I even managed to connect to mine, but it dropped immediately.
I know, this is very undetailed, but do you have any recommendations / logs to look out / smth which could point me in the right direction? Or is my hardware just broken?
logcat outputs this when turning wi-fi on (on stock 4.2.2, unrooted):
D/WifiService( 499): setWifiEnabled: true pid=1942, uid=1000
D/BluetoothAdapter( 1942): 1110956336: getState() : mService = null. Returning STATE_OFF
W/Netd ( 156): No subsystem found in netlink event
D/NetlinkEvent( 156): Unexpected netlink message. type=0x11
W/Netd ( 156): No subsystem found in netlink event
D/NetlinkEvent( 156): Unexpected netlink message. type=0x11
D/Tethering( 499): sendTetherStateChangedBroadcast 1, 0, 0
D/Tethering( 499): InitialState.processMessage what=4
D/Tethering( 499): sendTetherStateChangedBroadcast 0, 0, 0
D/SoftapController( 156): Softap fwReload - Ok
D/CommandListener( 156): Setting iface cfg
D/CommandListener( 156): Trying to bring down wlan0
E/NetdConnector( 499): NDC Command {219 softap fwreload wlan0 STA} took too long (739ms)
I/wpa_supplicant( 9715): Successfully initialized wpa_supplicant
I/wpa_supplicant( 9715): rfkill: Cannot open RFKILL control device
I/wpa_supplicant( 9715): rfkill: Cannot open RFKILL control device
D/CommandListener( 156): Setting iface cfg
D/CommandListener( 156): Trying to bring up p2p0
D/BluetoothAdapter( 1942): 1110956336: getState() : mService = null. Returning STATE_OFF
Click to expand...
Click to collapse
when flashing stock (via the official google flash scripts), stock firmware files (qualcom, ..) are also flashed, right? or could I do something useful with the official google binaries?
Stupid post.... Ignore

[Solved] GT-I9205 Stuck At Boot Animation

Hi,
Currently I'm compiling OmniRom for Samsung Galaxy Mega GT-I9205.
When I try to boot it for the first time, the Omni is stuck at the boot animation...
May I know what is the general failure for this particular issue? and how to solve it?
logcat F/
Code:
12-29 19:01:06.722 F/MediaProfiles( 287): frameworks/av/media/libmedia/MediaProfiles.cpp:324 CHECK(quality != -1) failed.
12-29 19:01:06.722 F/libc ( 287): Fatal signal 6 (SIGABRT) at 0x0000011f (code=-6), thread 287 (zygote)
logcat /E
Code:
12-29 19:01:07.513 E/QualcommCamera( 754): Qint android::get_number_of_cameras(): E
...
12-29 19:01:07.513 I/AudioPolicyManagerBase( 754): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
12-29 19:01:07.523 D/ALSADevice( 754): ALSA module opened
12-29 19:01:07.533 D/AudioHardwareALSA( 754): AudioHardware: DLOPEN successful for ACDBLOADER
12-29 19:01:07.533 D/ACDB-LOADER( 754): ACDB -> ACDB_CMD_INITIALIZE
12-29 19:01:07.533 E/ ( 754): [ACDB RTC]->rtc init done!->result [0]
12-29 19:01:07.533 E/Diag_Lib( 754): actp_diag_init: call diag init function with B5F20ECD
12-29 19:01:07.533 E/Diag_Lib( 754): Diag_LSM_Init: Failed to open handle to diag driver, error = 13
12-29 19:01:07.533 E/Diag_Lib( 754): actp_diag_init: diag init failed
12-29 19:01:07.533 E/ ( 754): [ACDB ACPH]->actp diag init done!
---
I suspect the media_profiles.xml is corrupted... but nope...
anywhere this is the comparison of media_profiles.xml between
melius >> https://github.com/Grarak/android_d...mon/blob/android-4.4/media/media_profiles.xml
hammerhead >> https://github.com/omnirom/android_device_lge_hammerhead/blob/android-4.4/media_profiles.xml
Diff >> http://diffchecker.com/ghjvhy51
and the device mk file
Code:
https://github.com/Grarak/android_device_samsung_melius-common/blob/android-4.4/melius-common.mk
# Media Profile
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/media/media_profiles.xml:system/etc/media_profiles.xml
# Note: Didnt have media_codecs.xml
Code:
https://github.com/omnirom/android_device_lge_hammerhead/blob/android-4.4/device.mk
PRODUCT_COPY_FILES += \
device/lge/hammerhead/media_codecs.xml:system/etc/media_codecs.xml \
device/lge/hammerhead/media_profiles.xml:system/etc/media_profiles.xml
Try using hammerhead (or another closer similar Qcom device)'s media_codec.xml and media_profiles.xml (or remove those files)
Thank your for the suggestion... look like i have to test on hammerhead xml afterall :crying:
but b4 that,
Im hoping someone able to tell me the logcat diagnostic
coz this file is currently used in CM11 (I9205) and they didnt have issue for this particular matter
Great news...
I managed to get it working... now omnirom have another working device in his pocket
Solutions: use media codec + profile from hammerhead... media codec + profile by touchwiz wont work
---
but i still have some problem
i able to get the camera to work, but the video recording is recording black screen...

sensors (acceleration gyroscope orientation etc) issues, nv data dump request

Hello,
i got a D802 phone which apparently has some sensors disabled in some way. When apps try to use them (so the system see them as existent) they fail or crash.
here some example log:
-Orientation:
Code:
W/OrientationEventListener( 957): Cannot detect sensors. Invalid disable
-Calibration:
Code:
E/AndroidRuntime( 7456): java.lang.NullPointerException: Attempt to invoke virtual method 'int android.hardware.Sensor.getType()' on a null object reference
E/AndroidRuntime( 7456): at com.qualcomm.sensors.sensortest.SensorID$SensorTyp e.getSensorType(SensorID.java:61)
E/AndroidRuntime( 7456): at com.android.settings.lge.MotionSensorCalibration$C alThreadRunnable.run(MotionSensorCalibration.java: 228)
E/AndroidRuntime( 7456): at java.lang.Thread.run(Thread.java:818)
-Gravity:
Code:
I/SensorManager(14094): registerListenerImpl() [Sensor: LGE Gravity Sensor, Rate: 200000, SensorEventListener: [email protected]] by com.kfodor.MySensors.SensorView.registerSensorListener():735
D/sensors_hal_SAM( 949): batch:sensor(android.sensor.gravity) handle:29 freq:1 report_rate:1 max:1.000000 min:0.000000
D/sensors_hal_Gravity( 949): enable: handle=29
D/sensors_hal_Gravity( 949): enable: handle=29, freq=1 report_rate=1 batch_rate=0 batched=0 wakeup 0
D/sensors_hal_Gravity( 949): enable: handle=29 synchronous req
I/sensors_hal_SAM( 949): sendEnableReq:sensor(android.sensor.gravity) Sending enable to svc no:20
E/Sensors ( 474): sns_acm_mr.c(776):Request made to disabled service
E/Sensors ( 474): sns_main.c(1331):Error writing request. sns_err 3 error 0 qmi_err 0
E/sensors_hal_Gravity( 949): processResp: Msg 2; Result: 1, Error: 3
D/sensors_hal_Gravity( 949): enable: Received Response: 1
-Acceleration:
Code:
I/sensors_hal_SAM( 949): sendEnableReq:sensor(android.sensor.linear_acceleration) Sending enable to svc no:20
E/Sensors ( 474): sns_acm_mr.c(776):Request made to disabled service
E/Sensors ( 474): sns_main.c(1331):Error writing request. sns_err 3 error 0 qmi_err 0
E/sensors_hal_LinearAccel( 949): processResp: Msg 2; Result: 1, Error: 3
-Rotation:
Code:
I/sensors_hal_SAM( 949): sendEnableReq:sensor(android.sensor.rotation_vector) Sending enable to svc no:18
E/Sensors ( 474): sns_acm_mr.c(776):Request made to disabled service
E/Sensors ( 474): sns_main.c(1331):Error writing request. sns_err 3 error 0 qmi_err 0
E/sensors_hal_RV( 949): processResp: Msg 2; Result: 1, Error: 3
I/SensorManager(14094): removeAllSensors() [Sensor: LGE Rotation Vector Sensor] by com.kfodor.MySensors.SensorView.registerSensorListener():732
I followed a lot of paths to find a solution, different distributions and full revert to all available stock versions. no way.
As my last trial I want to try to compare my NV data with a working one to search for some misconfigured parameter.
I found a great guide on how to access and extract all NV parameters and save to a text file, here:
http://www.droidviews.com/how-to-bac...imei-on-lg-g2/
As you can see, the guide is for changing IMEI, but the application permit to dump all parameters to a file.
I ask some good man to send me his dump. or i can send mine and get the differences. Because this file contains sensitive data, they should be removed (IMEI, S/N, MAC) even if i am not interested in stealing ids!
I have a D802 32GB.
thank you to everyone, hope to receive some useful feedback!.
Fabio T

Categories

Resources