[SBF] Gingerbread 2.3.3 for CDMA DROID Pro XT610 Verizon USA [SBF]
ro.build.display.id=4.5.1-110-VNS-22
Android 2.3.3 ---- Blur_Version.4.6.8.XT610.Verizon.en.US
VRZ_XT610_4.6.8_user_signed_1FF.sbf.gz
http://www.wupload.com/file/2650689337/VRZ_XT610_4.6.8_user_signed_1FF.sbf.gz
WARNING: AFTER FLASHING SBF to 2.3.3 DOWNGRADING to FROYO MAY NOT BE POSSIBLE AND MAY BRICK YOUR PHONE !!!!
Compression MD5 - 1F3B0D352A765756AAB0205F3BB08928
MD5 - 8CCC9847335B5F3970C42BEA08C289FE
Even of you SBF your phone to Froyo it won't work?
after update = black screen forever
Hello!
I used rsdlite 4.9 to flash this after turning the phone on using vol up + down.
Black screen is all I get rebooting, even waiting for ages
R+M works, but @ does not (no reaction)
Any ideas? Bricked?
Any way of going back to 3.8.7 and restoring a cwm backup I made beforehand?
MD5 checked and correspondent.
Any ideas?
Thanks!
G
log: 01/10/12 01:18:00 --------------------------------------------------------------------------------
01/10/12 01:18:00 New Log Started For Software Download.
01/10/12 01:18:07 The FlashLog key is turned off.
01/10/12 01:18:42 Multi upgrade started for 0 phones
01/10/12 01:18:53 Multi upgrade started for 0 phones
01/10/12 01:18:54 Multi upgrade started for 0 phones
01/10/12 01:18:54 Multi upgrade started for 0 phones
01/10/12 01:18:56 Multi upgrade started for 0 phones
01/10/12 01:18:57 Multi upgrade started for 0 phones
01/10/12 01:18:57 Multi upgrade started for 0 phones
01/10/12 01:18:57 Multi upgrade started for 0 phones
01/10/12 01:19:03 Multi upgrade started for 0 phones
01/10/12 01:19:44 Multi upgrade started for 0 phones
01/10/12 01:19:47 ERROR: MultiUpgrade(): Removing device that is not listed in display map.
01/10/12 01:20:55 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:20:55 00000fc8 Phone.cpp 1557 0 ERROR GetPhoneID failed: ERROR.
01/10/12 01:20:57 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:20:57 00000fc8 Phone.cpp 1557 0 ERROR GetPhoneID failed: ERROR.
01/10/12 01:20:59 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:20:59 00000fc8 Phone.cpp 1557 0 ERROR GetPhoneID failed: ERROR.
01/10/12 01:20:59 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:20:59 00000fc8 Phone.cpp 1652 0 ERROR GetTechnology failed: ERROR.
01/10/12 01:20:59 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:20:59 00000fc8 Phone.cpp 1720 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
01/10/12 01:20:59 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:20:59 00000fc8 Phone.cpp 1878 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
01/10/12 01:20:59 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:20:59 00000fc8 Phone.cpp 1767 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
01/10/12 01:21:05 Multi upgrade started for 1 phones
01/10/12 01:21:05 [Device ID: 0] Flashing phone.
01/10/12 01:32:16 [Device ID: 0] Please manually power up this phone.
01/10/12 01:33:21 00000988 Phone.cpp 3837 -1 ERROR CPhone::WaitForPhone timed out. Iteration-1
01/10/12 01:33:21 [Device ID: 0] Please manually power up this phone.
01/10/12 01:34:26 00000988 Phone.cpp 3837 -1 ERROR CPhone::WaitForPhone timed out. Iteration-2
01/10/12 01:34:26 [Device ID: 0] Please manually power up this phone.
01/10/12 01:35:31 00000988 Phone.cpp 3837 -1 ERROR CPhone::WaitForPhone timed out. Iteration-3
01/10/12 01:35:31 [Device ID: 0] Please manually power up this phone.
01/10/12 01:36:36 00000988 Phone.cpp 3837 -1 ERROR CPhone::WaitForPhone timed out. Iteration-4
01/10/12 01:36:36 [Device ID: 0] Please manually power up this phone.
01/10/12 01:37:41 00000988 Phone.cpp 3837 -1 ERROR CPhone::WaitForPhone timed out. Iteration-5
01/10/12 01:37:41 [Device ID: 0] Please manually power up this phone.
01/10/12 01:38:46 00000988 Phone.cpp 3837 -1 ERROR CPhone::WaitForPhone timed out. Iteration-6
01/10/12 01:38:46 [Device ID: 0] Please manually power up this phone.
01/10/12 01:39:51 00000988 Phone.cpp 3837 -1 ERROR CPhone::WaitForPhone timed out. Iteration-7
01/10/12 01:39:51 [Device ID: 0] Please manually power up this phone.
01/10/12 01:40:56 00000988 Phone.cpp 3837 -1 ERROR CPhone::WaitForPhone timed out. Iteration-8
01/10/12 01:40:56 [Device ID: 0] Please manually power up this phone.
01/10/12 01:42:01 00000988 Phone.cpp 3837 -1 ERROR CPhone::WaitForPhone timed out. Iteration-9
01/10/12 01:42:01 [Device ID: 0] Please manually power up this phone.
01/10/12 01:43:06 00000988 Phone.cpp 3837 -1 ERROR CPhone::WaitForPhone timed out. Iteration-10
01/10/12 01:43:06 [Device ID: 0] Please manually power up this phone.
01/10/12 01:43:49 [Device ID: 0] Waiting for others to finish current operation.
01/10/12 01:43:49 The FlashLog key is turned off.
01/10/12 01:43:49 FlashLog file is turned off.
01/10/12 01:43:49 Multi upgrade finished.
01/10/12 01:43:49 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:49 00000fc8 Phone.cpp 1557 0 ERROR GetPhoneID failed: ERROR.
01/10/12 01:43:50 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:50 00000fc8 Phone.cpp 1557 0 ERROR GetPhoneID failed: ERROR.
01/10/12 01:43:50 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:50 00000fc8 Phone.cpp 1557 0 ERROR GetPhoneID failed: ERROR.
01/10/12 01:43:50 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:50 00000fc8 Phone.cpp 1652 0 ERROR GetTechnology failed: ERROR.
01/10/12 01:43:50 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:50 00000fc8 Phone.cpp 1720 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
01/10/12 01:43:50 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:50 00000fc8 Phone.cpp 1878 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
01/10/12 01:43:50 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:50 00000fc8 Phone.cpp 1767 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
01/10/12 01:43:57 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:57 00000fc8 Phone.cpp 1557 0 ERROR GetPhoneID failed: ERROR.
01/10/12 01:43:57 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:57 00000fc8 Phone.cpp 1557 0 ERROR GetPhoneID failed: ERROR.
01/10/12 01:43:57 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:57 00000fc8 Phone.cpp 1652 0 ERROR GetTechnology failed: ERROR.
01/10/12 01:43:57 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:57 00000fc8 Phone.cpp 1720 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
01/10/12 01:43:57 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:57 00000fc8 Phone.cpp 1878 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
01/10/12 01:43:57 00000fc8 Phone.cpp 451 0 ERROR Generic failure when sending command.
01/10/12 01:43:57 00000fc8 Phone.cpp 1767 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
01/10/12 01:43:58 Multi upgrade started for 1 phones
01/10/12 01:43:58 [Device ID: 0] Flashing phone.
01/10/12 01:52:56 [Device ID: 0] Please manually power up this phone.
01/10/12 01:54:01 00000e94 Phone.cpp 3837 -1 ERROR CPhone::WaitForPhone timed out. Iteration-1
01/10/12 01:54:01 [Device ID: 0] Please manually power up this phone.
01/10/12 01:55:06 00000e94 Phone.cpp 3837 -1 ERROR CPhone::WaitForPhone timed out. Iteration-2
01/10/12 01:55:06 [Device ID: 0] Please manually power up this phone.
#G# said:
R+M works, but @ does not (no reaction)
Click to expand...
Click to collapse
Press volUp+volDown together instead of @
need help
daywalker04 said:
[SBF] Gingerbread 2.3.3 for CDMA DROID Pro XT610 Verizon USA [SBF]
ro.build.display.id=4.5.1-110-VNS-22
Android 2.3.3 ---- Blur_Version.4.6.8.XT610.Verizon.en.US
VRZ_XT610_4.6.8_user_signed_1FF.sbf.gz
http://www.wupload.com/file/2650689337/VRZ_XT610_4.6.8_user_signed_1FF.sbf.gz
WARNING: AFTER FLASHING SBF to 2.3.3 DOWNGRADING to FROYO MAY NOT BE POSSIBLE AND MAY BRICK YOUR PHONE !!!!
Compression MD5 - 1F3B0D352A765756AAB0205F3BB08928
MD5 - 8CCC9847335B5F3970C42BEA08C289FE
Click to expand...
Click to collapse
link not work
Download link works fine.
http://www.wupload.com/file/2650689337/VRZ_XT610_4.6.8_user_signed_1FF.sbf.gz
You can downgrade...! I did it...
Update on unlocked droid pro
By updating my unlocked droid pro using this sbf file... is there a possibility of my phone getting locked again?
^ i also have the same question .
PLEASE FIX DOWNLOAD LINK
Cannot download the file
Note:
Wupload does not allow files to be shared. We are a STORAGE ONLY product so you can only download your own files.
If you have uploaded this file yourself, login first in order to download it.
Any other link?....
ANY other link!!!!
Update pls
Please fix download link!!!
https://sites.google.com/site/motosbf/droid-pro-sbf-files
locarbdontmeannosugar said:
...
Click to expand...
Click to collapse
Thanks, mate.
Really appreciate that.
This sbf file is froyo 2.2 and not gb 2.3.3.. Where do i find the sbf 2.3.3 gingerbread?
please repair link, not work.
thx
Anyone has XT609 (!!!) firmware?
Or maybe you can give me a link for any VNS2EM firmware for XT610 ?
Related
Hi there,
Could anyone explain me, this strange errors in dmesg log?
I checked and there aren't this errors on stock (don't rooted rom),
but after use unrevoked3 tool on this rom, errors appears in log,
also on pre-rooted teppic rom and another pre-rooted stock roms from here.
[...]
<3>[ 25.553009] msm_nand_erase: erase failed, 0x4d40000
<3>[ 25.553436] msm_nand_erase: erase failed, 0x4dc0000
<3>[ 25.553894] msm_nand_erase: erase failed, 0x4f80000
<4>[ 25.554199] yaffs_read_super: isCheckpointed 0
<3>[ 25.554687] msm_nand_write_oob 11a80000 800 1c failed -5
[a lot of same messages]
[a lot of same messages]
[a lot of same messages]
<3>[ 25.617645] msm_nand_write_oob 11afc800 800 1c failed -5
<4>[ 25.617828] save exit: isCheckpointed 1
<6>[ 25.632659] yaffs: dev is 32505861 name is "mtdblock5"
<6>[ 25.632781] yaffs: passed flags ""
[...]
Hello,
looking at the log (dmesg) after turning on my phone, I find errors related to partitions, which persist after changing SD card ...
11/23/2011 12:50:05 [INFORMATION] yaffs: dev is 32505859 name is "mtdblock3" rw
11/23/2011 12:50:05 [INFORMATION] yaffs: passed flags ""
11/23/2011 12:50:05 [DEBUG] yaffs: yaffs: Attempting MTD mount of 31.3,"mtdblock3"
11/23/2011 12:50:05 [DEBUG] yaffs: yaffs_read_super: is_checkpointed 1
11/23/2011 12:50:05 [INFORMATION] yaffs: dev is 32505861 name is "mtdblock5" rw
11/23/2011 12:50:05 [INFORMATION] yaffs: passed flags ""
11/23/2011 12:50:05 [DEBUG] yaffs: yaffs: Attempting MTD mount of 31.5,"mtdblock5"
11/23/2011 12:50:05 [DEBUG] yaffs: yaffs_read_super: is_checkpointed 1
11/23/2011 12:50:05 [INFORMATION] yaffs: dev is 32505860 name is "mtdblock4" rw
11/23/2011 12:50:05 [INFORMATION] yaffs: passed flags ""
11/23/2011 12:50:05 [DEBUG] yaffs: yaffs: Attempting MTD mount of 31.4,"mtdblock4"
11/23/2011 12:50:05 [DEBUG] yaffs: yaffs_read_super: is_checkpointed 0
...
11/23/2011 12:50:05 [WARNING] mmc1: host does not support reading read-only switch. assuming write-enable.
11/23/2011 12:50:05 [INFORMATION] mmc1: new high speed SDHC card at address e624
11/23/2011 12:50:05 [INFORMATION] mmcblk0: mmc1:e624 SU08G 7.40 GiB
11/23/2011 12:50:05 [INFORMATION] mmcblk0: p1 p2 p3 p4
11/23/2011 12:50:05 [INFORMATION] batt: 27%, 3669 mV, -283 mA (-228 avg), 22.7 C, 369 mAh
11/23/2011 12:50:05 [INFORMATION] batt: charging OFF
11/23/2011 12:50:07 [ERROR] init: exec: pid 70 exited with return code 225: Unknown error: 57837
11/23/2011 12:50:07 [ERROR] init: untracked pid 90 exited
11/23/2011 12:50:07 [ERROR] init: untracked pid 91 exited
11/23/2011 12:50:07 [ERROR] init: untracked pid 92 exited
11/23/2011 12:50:07 [ERROR] init: service 'console' requires console
...
11/23/2011 12:50:09 [ERROR] msm_nand_read_oob: unsupported from, 0xdfc0400
11/23/2011 12:50:09 [ERROR] end_request: I/O error, dev mtdblock5, sector
11/23/2011 12:50:09 [ERROR] EXT4-fs (mtdblock5): unable to read superblock
11/23/2011 12:50:09 [ERROR] msm_nand_read_oob: unsupported from, 0xdfc0400
11/23/2011 12:50:09 [ERROR] end_request: I/O error, dev mtdblock5, sector
11/23/2011 12:50:09 [ERROR] EXT4-fs (mtdblock5): unable to read superblock
11/23/2011 12:50:09 [ERROR] msm_nand_read_oob: unsupported from, 0xdfc0400
11/23/2011 12:50:09 [ERROR] end_request: I/O error, dev mtdblock5, sector
11/23/2011 12:50:09 [ERROR] EXT4-fs (mtdblock5): unable to read superblock
11/23/2011 12:50:09 [ERROR] msm_nand_read_oob: unsupported ops->len, 512
11/23/2011 12:50:09 [ERROR] end_request: I/O error, dev mtdblock5, sector
11/23/2011 12:50:09 [ERROR] FAT: unable to read boot sector
11/23/2011 12:50:09 [INFORMATION] yaffs: dev is 32505861 name is "mtdblock5" rw
11/23/2011 12:50:09 [INFORMATION] yaffs: passed flags ""
11/23/2011 12:50:09 [DEBUG] yaffs: yaffs: Attempting MTD mount of 31.5,"mtdblock5"
11/23/2011 12:50:09 [DEBUG] yaffs: auto selecting yaffs2
11/23/2011 12:50:09 [DEBUG] yaffs: yaffs_read_super: is_checkpointed 1
11/23/2011 12:50:09 [ERROR] init: untracked pid 188 exited
11/23/2011 12:50:09 [ERROR] init: untracked pid 189 exited
11/23/2011 12:50:09 [ERROR] init: untracked pid 190 exited
11/23/2011 12:50:09 [ERROR] init: untracked pid 191 exited
11/23/2011 12:50:09 [INFORMATION] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
11/23/2011 12:50:11 [INFORMATION] EXT4-fs (mmcblk0p3): mounted filesystem without journal. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
11/23/2011 12:50:12 [INFORMATION] EXT4-fs (mmcblk0p3): mounted filesystem without journal. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
11/23/2011 12:50:18 [ERROR] init: untracked pid 70 exited
...
11/23/2011 12:51:13 [ERROR] binder: release proc 1257, transaction 8261, not freed
11/23/2011 12:51:15 [ERROR] mmc1: Data CRC error
11/23/2011 12:51:15 [ERROR] msmsdcc_data_err: opcode 0x00000012
11/23/2011 12:51:15 [ERROR] msmsdcc_data_err: blksz 512, blocks 256
11/23/2011 12:51:15 [ERROR] mmc1: DMA channel flushed (0x80000004)
11/23/2011 12:51:15 [ERROR] Flush data: 0000c003 3b27d030 00000000 00200040 00710070 00002003
11/23/2011 12:51:15 [WARNING] mmcblk0: retrying using single block read
11/23/2011 12:51:18 [ERROR] mmc1: Data CRC error
11/23/2011 12:51:18 [ERROR] msmsdcc_data_err: opcode 0x00000012
11/23/2011 12:51:18 [ERROR] msmsdcc_data_err: blksz 512, blocks 256
11/23/2011 12:51:18 [ERROR] mmc1: DMA channel flushed (0x80000004)
11/23/2011 12:51:18 [ERROR] Flush data: 0000c003 3b27d000 00000000 00200040 01a901a8 00002003
11/23/2011 12:51:18 [WARNING] mmcblk0: retrying using single block read
11/23/2011 12:51:20 [ERROR] mmc1: Data CRC error
11/23/2011 12:51:20 [ERROR] msmsdcc_data_err: opcode 0x00000012
11/23/2011 12:51:20 [ERROR] msmsdcc_data_err: blksz 512, blocks 16
11/23/2011 12:51:20 [ERROR] mmc1: DMA channel flushed (0x80000004)
11/23/2011 12:51:20 [ERROR] Flush data: 0000c003 3b27d000 00000000 00200040 00310030 00002003
11/23/2011 12:51:20 [WARNING] mmcblk0: retrying using single block read
...
11/23/2011 12:51:23 [ERROR] init: sys_prop: permission denied uid:1000 name:ro.auto_time.startup_synced
11/23/2011 12:51:26 [ERROR] mmc1: Data CRC error
11/23/2011 12:51:26 [ERROR] msmsdcc_data_err: opcode 0x00000012
11/23/2011 12:51:26 [ERROR] msmsdcc_data_err: blksz 512, blocks 256
11/23/2011 12:51:26 [ERROR] mmc1: DMA channel flushed (0x80000004)
11/23/2011 12:51:26 [ERROR] Flush data: 0000c003 3b27d1f8 00000000 00200040 00190018 00002003
11/23/2011 12:51:26 [WARNING] mmcblk0: retrying using single block read
...
Do I have a problem with my internal memory? Or a problem with my current ROM MIUI D2EXT X-PART?
Did I can fix by reflashing the CM7/r2 hboot?
Thank you. Greetings.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi. I have Nexus 7 2013 WiFi 32Gb. FLO 04.02 bootloader. Stock 4.4.2 android with root and teamwin.
Recently, I start download file and after that my nexus 7 rebooted. And it stuck on Google boot screen. I try to run teamwin, but it also stuck on Teamwin logo.
In fastboot mode i get:
Code:
> sudo fastboot -u format cache
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 89.945s
> sudo fastboot -w
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.015s
> sudo fastboot flash bootloader bootloader-flo-flo-04.02.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 1.068s
e2fsck:
Code:
e2fsck /dev/block/mmcblk0
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0
Filesystem mounted or opened exclusively by another program?
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p30
Filesystem mounted or opened exclusively by another program?
mount:
Code:
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
dmesg: pastebin. com/j4hnHkwg
PS. Can't insert links, and can't insert dmesg here, message are too long... =(
Some other logs:
Code:
<4>[ 1013.807952] ------------[ cut here ]------------
<4>[ 1013.807952] WARNING: at drivers/mmc/host/msm_sdcc.c:3538 msmsdcc_disable+0x84/0x10c()
<4>[ 1013.807952] mmc0: msmsdcc_disable: failed with error -22
<4>[ 1013.807983] [<c010cbc8>] (unwind_backtrace+0x0/0x11c) from [<c01730e8>] (warn_slowpath_common+0x48/0x60)
<4>[ 1013.807983] [<c01730e8>] (warn_slowpath_common+0x48/0x60) from [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 1013.807983] [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0659b18>] (msmsdcc_disable+0x84/0x10c)
<4>[ 1013.808013] [<c0659b18>] (msmsdcc_disable+0x84/0x10c) from [<c0646130>] (mmc_release_host+0x4c/0xb0)
<4>[ 1013.808013] [<c0646130>] (mmc_release_host+0x4c/0xb0) from [<c06571a0>] (mmc_blk_issue_rq+0x480/0x4c0)
<4>[ 1013.808044] [<c06571a0>] (mmc_blk_issue_rq+0x480/0x4c0) from [<c0657648>] (mmc_queue_thread+0xd4/0x19c)
<4>[ 1013.808044] [<c0657648>] (mmc_queue_thread+0xd4/0x19c) from [<c018f804>] (kthread+0x84/0x90)
<4>[ 1013.808044] [<c018f804>] (kthread+0x84/0x90) from [<c0107228>] (kernel_thread_exit+0x0/0x8)
<4>[ 1013.808074] ---[ end trace c0d52a61d7a24c7c ]---
<6>[ 1013.808074] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<6>[ 1013.808074] mmc0: RPM: runtime_status=0, usage_count=0, is_suspended=0, disable_depth=0, runtime_error=-110, request_pending=0, request=0
<4>[ 1013.901123] ------------[ cut here ]------------
<4>[ 1013.901245] WARNING: at drivers/mmc/host/msm_sdcc.c:3510 msmsdcc_enable+0x108/0x144()
<4>[ 1013.901306] mmc0: msmsdcc_enable: failed with error -22
<4>[ 1013.901397] [<c010cbc8>] (unwind_backtrace+0x0/0x11c) from [<c01730e8>] (warn_slowpath_common+0x48/0x60)
<4>[ 1013.901519] [<c01730e8>] (warn_slowpath_common+0x48/0x60) from [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 1013.901580] [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c) from [<c065db64>] (msmsdcc_enable+0x108/0x144)
<4>[ 1013.901702] [<c065db64>] (msmsdcc_enable+0x108/0x144) from [<c0646018>] (__mmc_claim_host+0x170/0x180)
<4>[ 1013.901824] [<c0646018>] (__mmc_claim_host+0x170/0x180) from [<c0656d54>] (mmc_blk_issue_rq+0x34/0x4c0)
<4>[ 1013.901916] [<c0656d54>] (mmc_blk_issue_rq+0x34/0x4c0) from [<c0657648>] (mmc_queue_thread+0xd4/0x19c)
<4>[ 1013.902038] [<c0657648>] (mmc_queue_thread+0xd4/0x19c) from [<c018f804>] (kthread+0x84/0x90)
<4>[ 1013.902130] [<c018f804>] (kthread+0x84/0x90) from [<c0107228>] (kernel_thread_exit+0x0/0x8)
<4>[ 1013.902221] ---[ end trace c0d52a61d7a24c7d ]---
<6>[ 1013.902343] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<6>[ 1013.902404] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=-110, request_pending=0, request=0
<6>[ 1013.903350] sps:BAM 0x12402000 enabled: ver:0x5, number of pipes:6
<3>[ 1013.908935] mmcblk0: error -110 sending status command, retrying
<3>[ 1013.914428] mmcblk0: error -110 sending status command, retrying
<3>[ 1013.919891] mmcblk0: error -110 sending status command, aborting
<3>[ 1013.919982] end_request: I/O error, dev mmcblk0, sector 4718594
<3>[ 1013.920104] EXT4-fs (mmcblk0p30): unable to read superblock
<4>[ 1013.920104] ------------[ cut here ]------------
<4>[ 1013.920135] WARNING: at drivers/mmc/host/msm_sdcc.c:3538 msmsdcc_disable+0x84/0x10c()
<4>[ 1013.920135] mmc0: msmsdcc_disable: failed with error -22
<4>[ 1013.920135] [<c010cbc8>] (unwind_backtrace+0x0/0x11c) from [<c01730e8>] (warn_slowpath_common+0x48/0x60)
<4>[ 1013.920166] [<c01730e8>] (warn_slowpath_common+0x48/0x60) from [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c)
<4>[ 1013.920166] [<c0173158>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0659b18>] (msmsdcc_disable+0x84/0x10c)
<4>[ 1013.920166] [<c0659b18>] (msmsdcc_disable+0x84/0x10c) from [<c0646130>] (mmc_release_host+0x4c/0xb0)
<4>[ 1013.920196] [<c0646130>] (mmc_release_host+0x4c/0xb0) from [<c06571a0>] (mmc_blk_issue_rq+0x480/0x4c0)
<4>[ 1013.920196] [<c06571a0>] (mmc_blk_issue_rq+0x480/0x4c0) from [<c0657648>] (mmc_queue_thread+0xd4/0x19c)
<4>[ 1013.920227] [<c0657648>] (mmc_queue_thread+0xd4/0x19c) from [<c018f804>] (kthread+0x84/0x90)
<4>[ 1013.920227] [<c018f804>] (kthread+0x84/0x90) from [<c0107228>] (kernel_thread_exit+0x0/0x8)
<4>[ 1013.920227] ---[ end trace c0d52a61d7a24c7e ]---
<6>[ 1013.920227] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<6>[ 1013.920257] mmc0: RPM: runtime_status=0, usage_count=0, is_suspended=0, disable_depth=0, runtime_error=-110, request_pending=0, request=0
<3>[ 703.888671] EXT4-fs (mmcblk0p30): unable to read superblock
<3>[ 7.323852] mmcblk0: error -110 sending stop command, original cmd response 0x940, card status 0x2400e40
umount: can't umount /dev/block/mmcblk0: Invalid argument
mmc0: msmsdcc_enable: failed with error -22
<3>[ 757.383453] end_request: I/O error, dev mmcblk0, sector 4718592
<6>[ 1364.750000] mmc0: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<6>[ 1364.750091] mmc0: RPM: runtime_status=0, usage_count=1, is_suspended=0, disable_depth=0, runtime_error=-110, request_pending=0, request=0
<6>[ 1364.751068] sps:BAM 0x12402000 enabled: ver:0x5, number of pipes:6
<3>[ 1364.756591] mmcblk0: error -110 sending status command, retrying
<3>[ 1364.762145] mmcblk0: error -110 sending status command, retrying
<3>[ 1364.767608] mmcblk0: error -110 sending status command, aborting
<3>[ 1364.767700] end_request: I/O error, dev mmcblk0, sector 4718592
<3>[ 1364.767791] end_request: I/O error, dev mmcblk0, sector 4718593
<3>[ 1364.767852] end_request: I/O error, dev mmcblk0, sector 4718594
<3>[ 1364.767974] end_request: I/O error, dev mmcblk0, sector 4718595
<3>[ 1364.768035] end_request: I/O error, dev mmcblk0, sector 4718596
<3>[ 1364.768127] end_request: I/O error, dev mmcblk0, sector 4718597
<3>[ 1364.768218] end_request: I/O error, dev mmcblk0, sector 4718598
<3>[ 1364.768310] end_request: I/O error, dev mmcblk0, sector 4718599
I have exactly the same problem. I wasn't doing anything - I just lifted the cover the other morning to find it sitting at the Google logo. Can it really be hosed? Are we SOL for warranty repair?
eecummings said:
I have exactly the same problem. I wasn't doing anything - I just lifted the cover the other morning to find it sitting at the Google logo. Can it really be hosed? Are we SOL for warranty repair?
Click to expand...
Click to collapse
Have you guys test the nexus root tool kit?
it's a wonderful piece of software..
it does helped alot my nexus 4 when it's half bricked...
Try flashing system images and see what happens?
Sent from my XT1032 using XDA Premium 4 mobile app
Hi, I've the exact same problem too.
Did you manage to solve it or did you have to send it back for repair?
Thanks,
Alessandro
I believe this is the same problem I have: Not being able to format my corrupted cache partition.
Since my tablet was not unlocked or rooted I can't seem to flash a ROM either, even stock.
1c3_5n0w said:
Try flashing system images and see what happens?
Click to expand...
Click to collapse
I can't flash or erase or format any partition. I get the same error after some period of timeout.
My phone was working fine until morning. I flashed D-kernel via terminal, and it doesn't boot(i was on stock 4.1.2 firmware). I left for a while to charge the phone because the battery was nearly discharged.Then i flashed 3 parted firmware via Odin. It takes horribly long time to boot up and just stay on bootscreen for considerable amount of time. When it finally booted, i was not able to use the touch screen.
I tried to restore my nandroid backup via cwm but it did not help. There is my kmsg log:
Code:
<6>[ 0.796936] input: gpio-keys as /devices/platform/gpio-keys.0/input/input0
<7>[ 0.797210] [KEY] key: home_key gpio_keys_report_event state = 1
<7>[ 0.797271] [KEY] key: volup_key gpio_keys_report_event state = 1
<7>[ 0.797271] [KEY] key: voldown_key gpio_keys_report_event state = 0
<6>[ 0.797912] input: sec_touchscreen as /devices/platform/nmk-i2c.3/i2c-3/3-0020/input/input1
<6>[ 0.798431] input: sec_touchkey as /devices/platform/nmk-i2c.3/i2c-3/3-0020/input/input2
<6>[ 0.798675] bt404_ts_device 3-0020: panel_type=1
<6>[ 0.897277] bt404_ts_device 3-0020: ldo power control(0)
<4>[ 1.052215] raw soc = 60
<6>[ 1.052398] ab8500-fg ab8500-fg.0: CC_CONF_REG : 3
<6>[ 1.052429] ab8500-fg ab8500-fg.0: Calibration ongoing...
<6>[ 1.313446] bt404_ts_device 3-0020: fw state checked(0x0, 0x0)
<6>[ 1.313873] bt404_ts_device 3-0020: send reset command
<3>[ 1.509521] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 1.709564] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 1.909637] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 1.909729] bt404_ts_device 3-0020: bt404_ts_init_device: err: rd (ic rev)
<3>[ 2.498291] bt404_ts_device 3-0020: retry to initiallize(retry cnt = 1)
<3>[ 2.689697] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 2.889709] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 3.089721] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 3.289733] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<6>[ 3.300476] ab8500-fg ab8500-fg.0: CC_CONF_REG : 3
<6>[ 3.300537] ab8500-fg ab8500-fg.0: Calibration done...
<3>[ 3.489746] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
....
<3>[ 8.889739] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 9.089752] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 9.099639] bt404_ts_device 3-0020: fail to sw reset
<3>[ 9.099670] bt404_ts_device 3-0020: fail to write interrupt register
<3>[ 9.688385] bt404_ts_device 3-0020: retry to initiallize(retry cnt = 2)
<3>[ 9.879760] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 10.079772] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 10.279754] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 10.479797] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<4>[ 10.551635] raw soc = 54
...
<3>[ 16.069732] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 16.269744] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 16.279632] bt404_ts_device 3-0020: fail to sw reset
<3>[ 16.279663] bt404_ts_device 3-0020: fail to write interrupt register
<3>[ 16.279663] bt404_ts_device 3-0020: retry init (cnt = 3)
<6>[ 16.279663] bt404_ts_device 3-0020: work_state = 0
<3>[ 16.479736] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 16.679748] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 16.879730] nmk-i2c nmk-i2c.3: Write to slave 0x20 timed out
<3>[ 16.879821] bt404_ts_device 3-0020: bt404_check_fw_update: err: rd (fw ver)
<6>[ 17.890716] bt404_ts_device 3-0020: flashing firmware (size=32768)
<3>[ 18.089752] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 18.289733] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 18.489746] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 18.489837] bt404_ts_device 3-0020: fail to flash 0th page (-110)
<3>[ 20.696899] bt404_ts_device 3-0020: failure: 2 retrial is left
<6>[ 21.700744] bt404_ts_device 3-0020: flashing firmware (size=32768)
<3>[ 21.899749] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 22.099731] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 22.299743] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 22.299835] bt404_ts_device 3-0020: fail to flash 0th page (-110)
<3>[ 24.506866] bt404_ts_device 3-0020: failure: 1 retrial is left
<6>[ 25.510742] bt404_ts_device 3-0020: flashing firmware (size=32768)
<3>[ 25.709747] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 25.909729] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 26.109741] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 26.109832] bt404_ts_device 3-0020: fail to flash 0th page (-110)
<3>[ 28.316864] bt404_ts_device 3-0020: failure: 0 retrial is left
<3>[ 28.509735] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 28.709747] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 28.909729] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 28.909820] bt404_ts_device 3-0020: bt404_ts_init_device: err: rd (ic rev)
<3>[ 28.909820] bt404_ts_device 3-0020: retry init (cnt = 4)
<6>[ 28.909851] bt404_ts_device 3-0020: work_state = 0
<3>[ 29.109771] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 29.309753] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 29.509735] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 29.509826] bt404_ts_device 3-0020: bt404_check_fw_update: err: rd (fw ver)
<6>[ 30.520751] bt404_ts_device 3-0020: flashing firmware (size=32768)
<3>[ 30.719757] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 30.919738] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 31.119750] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 31.119781] bt404_ts_device 3-0020: fail to flash 0th page (-110)
<3>[ 33.327117] bt404_ts_device 3-0020: failure: 2 retrial is left
<6>[ 34.330718] bt404_ts_device 3-0020: flashing firmware (size=32768)
<3>[ 34.529754] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 34.729736] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 34.929748] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 34.929779] bt404_ts_device 3-0020: fail to flash 0th page (-110)
<3>[ 37.137207] bt404_ts_device 3-0020: failure: 1 retrial is left
<6>[ 38.140747] bt404_ts_device 3-0020: flashing firmware (size=32768)
<3>[ 38.339752] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 38.539733] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 38.739746] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 38.739776] bt404_ts_device 3-0020: fail to flash 0th page (-110)
<3>[ 40.947204] bt404_ts_device 3-0020: failure: 0 retrial is left
<3>[ 41.139739] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 41.339752] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 41.539733] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 41.539855] bt404_ts_device 3-0020: bt404_ts_init_device: err: rd (ic rev)
<3>[ 41.539886] bt404_ts_device 3-0020: retry init (cnt = 5)
<6>[ 41.539886] bt404_ts_device 3-0020: work_state = 0
<3>[ 41.739746] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 41.939727] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 42.139739] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 42.139831] bt404_ts_device 3-0020: bt404_check_fw_update: err: rd (fw ver)
<6>[ 43.150756] bt404_ts_device 3-0020: flashing firmware (size=32768)
<3>[ 43.349731] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 43.549743] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 43.749755] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 43.749786] bt404_ts_device 3-0020: fail to flash 0th page (-110)
<3>[ 45.956848] bt404_ts_device 3-0020: failure: 2 retrial is left
<6>[ 46.960754] bt404_ts_device 3-0020: flashing firmware (size=32768)
<3>[ 47.159729] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 47.359741] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 47.559753] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 47.559844] bt404_ts_device 3-0020: fail to flash 0th page (-110)
<3>[ 49.766876] bt404_ts_device 3-0020: failure: 1 retrial is left
<6>[ 50.770721] bt404_ts_device 3-0020: flashing firmware (size=32768)
<3>[ 50.969757] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 51.169738] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 51.369750] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 51.369842] bt404_ts_device 3-0020: fail to flash 0th page (-110)
<3>[ 53.576843] bt404_ts_device 3-0020: failure: 0 retrial is left
<3>[ 53.769744] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 53.969757] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 54.169738] nmk-i2c nmk-i2c.3: Write to slave 0x50 timed out
<3>[ 54.169830] bt404_ts_device 3-0020: bt404_ts_init_device: err: rd (ic rev)
<3>[ 54.169830] bt404_ts_device 3-0020: retry init (cnt = 6)
<3>[ 54.169860] bt404_ts_device 3-0020: failed to force upgrade (6)
<6>[ 54.170898] bt404_ts_device 3-0020: successfully probed.
I've read similar topics, but does not seem that at least one problem was solved.
The problem has been solved by touch screen replacement.
Take care man, scary story, that log...any idea on what happened? It may be important, you know..it just died, or..values killed it?
xo.en said:
Take care man, scary story, that log...any idea on what happened? It may be important, you know..it just died, or..values killed it?
Click to expand...
Click to collapse
I guess it happened because the installation method via the terminal(or cwm) by dd command is incorrect. It's always needs to erase /boot partition before you install kernel:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p15
If the new kernel is smaller than the previous one, it will not overwrite it completely(if you did not erase boot partition).
But honestly, I have no idea why this has led to damage to the touch screen.
..so, there's reason to stay with slower CWM method, lol.. G'to know.
Anyway weird coincidence, imho.
xo.en said:
..so, there's reason to stay with slower CWM method, lol.. G'to know.
Anyway weird coincidence, imho.
Click to expand...
Click to collapse
There is no difference between the CWM and the terminal method, because when flashing via CWM, we have the following line in updater_script:
Code:
assert (package_extract_file ("boot.img", "/tmp/boot.img"),
write_raw_image ("/tmp/boot.img", "/dev/block/mmcblk0p15"),
delete ("/tmp/boot.img"));
i.e. / boot partition will not be erased .
dear
i downloaded S7-701wa_FIRMWARE_Android4.1_C199B002_MiddleEast_Channel_05011UBC.zip
but when i tried to upgrade i got error in 90% upgrading
i also checked the log file and this error showing there
!coulmeter_pid = 121,coulmeter_status =256, coulmeter ret = 1
huawei_process_firmware_update_record,Touchscreen child process finished naturally
!touchscreen_pid = 122,touchscreen_status=0,touchscreen ret = 0
sensors update fail......................
sensors_upgrade_record failed!
finish_recovery: boot.command=bootloader boot.recovery=update-bootloader boot.status=
anyone help me
what i can do further