Develop Bugs

Mode Fastboot doesn´t detect Htc Desire usb

Hey, I did a S-Off mode to Htc Desire However it installed a recovery program different which doesn´t like me and I back to amon-ra recovery, and my big surprise is when I try to change Splash for Adb or Android flasher (both running on fastboot mode) my htc desire isn´t recognised however in android system the usb is recognised but don´t recognised in fastboot mode , I don´t use for change splash1, somebody can help me? Thanks for all
Pardon for my poor english

Do you have hboot drivers installed? If not that's your problem.
Sent from my HTC Desire using XDA App

In this moment I have formatted pc, and the firs step I have done is installing hboot driver and the problem coming , Where is the problem? help me please!! Thanks for all

usb-brick?
Hi there,
same thing happened to me since I upgraded to oxygen 2 last week. It does look like a usb-brick, however radio, bluetooth and sd (reading music, storing pic from camera) work..
Once plug to my pc, the phone charges but no notification about mounting the sd pops up. Sd is not recognize, I tryed to mount it manually (android booted and through clockwork), via a dedicated apps (like automount ...)n nothing fugging work.
Wanted to use the usb fix from modaco and also listed here, however the phone is not recognize in fastboot (no fastboot usb). I have reinstalled, adk, htc sync, java ... and nothing fugging work.
Any leads on what happening would be much appreciated.
Cheers.

Do you get mend it?

same thing happend to me

ebi023 said:
same thing happend to me
Click to expand...
Click to collapse
To me too
that´s a snippet from my dmesg log
Code:
<4>[ 733.389221] samsung_oled_panel_init()
<6>[ 733.456909] capella_cm3602_ioctl cmd 2
<6>[ 733.457305] capella_cm3602_disable
<6>[ 733.457702] capella_cm3602_disable: already disabled
<6>[ 733.458526] capella_cm3602_ioctl cmd 1
<6>[ 733.458923] lightsensor_ioctl set value = 1
<6>[ 733.459289] lightsensor_enable
<3>[ 733.459991] lightsensor_enable: microp is suspended
<6>[ 733.460388] lightsensor_ioctl get enabled status: 1
<6>[ 733.540222] gpio_keys_scan_keys: key 1-74, 0 (94) changed to 0
<6>[ 733.703613] msmfb: ready, waiting for full update
<6>[ 733.704040] bravo_ts_power: power 1
<6>[ 733.733581] msmfb: pan_update in state(1)
<6>[ 733.733612] msmfb: full update starting
<6>[ 733.757202] msmfb: pan_update in state(3)
<6>[ 733.766235] msmfb: full update completed
<6>[ 733.766357] msmfb: turning on panel
<6>[ 733.766387] lcdc_unblank: ()
<4>[ 733.766387] amoled_panel_unblank
<4>[ 733.774383] amoled_panel_unblank: last_val = 80
<4>[ 733.850677] wlan: power active. usb_type:2
<4>[ 733.857666] wlan: update dtim listern interval: 0
<7>[ 733.858825] __capella_cm3602_power: Turn the capella_cm3602 power on
<3>[ 733.859527] curcial_oj_late_resume: enter
<3>[ 733.866485] curcial_oj_poweron:OJ power enable(1)
<6>[ 734.040832] OpticalJoystick Device ID: 0d
<6>[ 734.044677] OJ Driver: Revision : 02
<6>[ 734.049438] [R] late_resume end
<6>[ 734.648437] [email protected], 3810
<7>[ 734.676391] ALS value: 0x0, level: 1 #
<7>[ 734.687530] ALS value: 0x0, level: 1 #
<6>[ 734.890747] [email protected], 6493
<6>[ 734.983581] capella_cm3602_ioctl cmd 1
<6>[ 734.983581] lightsensor_ioctl get enabled status: 1
<6>[ 734.990692] __spi_bma150_set_mode: BMA get into NORMAL mode!
<4>[ 739.800750] Division by zero in kernel.
<4>[ 739.800933] Function entered at [<c002e948>] from [<c01bfb3c>]
<4>[ 739.801239] Function entered at [<c01bfb3c>] from [<c02629b0>]
<4>[ 739.801391] Function entered at [<c02629b0>] from [<c006fb38>]
<4>[ 739.801696] Function entered at [<c006fb38>] from [<c00732c4>]
<4>[ 739.801849] Function entered at [<c00732c4>] from [<c002a99c>]
<6>[ 739.827331] batt: 80%, 4079 mV, 404 mA (539 avg), 27.5 C, 1086 mAh
<6>[ 747.659454] cable_status_update: status=0
<6>[ 747.660186] msm_hsusb_set_vbus_state: 0
<6>[ 747.660614] hsusb: ONLINE -> OFFLINE
<6>[ 747.660949] usb: lpm exit
<6>[ 747.670135] batt: charging OFF
<6>[ 747.678588] usb: notify offline
<6>[ 747.678955] bravo_usb_phy_reset
<6>[ 747.679290] msm_hsusb_phy_reset
<6>[ 747.738281] usb: lpm enter
<6>[ 747.738403] usb_suspend_phy
<6>[ 747.739624] usb: send connect type 0
<6>[ 747.739715] fsg_set_ums_state: 0
<4>[ 747.739929] ### notify_usb_connected(0) ###
<6>[ 748.843475] cable_status_update: status=1
<6>[ 748.868286] msm_hsusb_set_vbus_state: 1
<6>[ 748.868988] hsusb: OFFLINE -> ONLINE
<6>[ 748.869323] usb: lpm exit
<6>[ 748.870758] hsusb: reset controller
<6>[ 748.877838] batt: charging SLOW
<6>[ 748.908477] bravo_usb_phy_reset
<6>[ 748.908874] msm_hsusb_phy_reset
<6>[ 749.118438] msm72k_udc: ulpi: write 0x0c to 0x31
<6>[ 749.118652] msm72k_udc: ulpi: write 0x31 to 0x32
<6>[ 749.118774] msm72k_udc: ulpi: write 0x1d to 0x0d
<6>[ 749.118957] msm72k_udc: ulpi: write 0x1d to 0x10
<6>[ 749.119110] usb: notify offline
<6>[ 749.119232] msm_hsusb: enable pullup
<6>[ 749.138397] usb: AC charger
<6>[ 749.158477] usb: lpm enter
<6>[ 749.158599] usb_suspend_phy
<6>[ 749.159790] usb: send connect type 2
<6>[ 749.160003] fsg_set_ums_state: 2
<4>[ 749.160095] ### notify_usb_connected(2) ###
<6>[ 749.167480] batt: charging FAST
<6>[ 750.570068] sudden key ignore
<6>[ 750.577270] sudden key ignore
<6>[ 750.584808] sudden key ignore
<6>[ 750.592163] sudden key ignore
<6>[ 750.599548] sudden key ignore
<6>[ 750.606872] sudden key ignore
<6>[ 778.073272] capella_cm3602_ioctl cmd 1
<6>[ 778.073455] lightsensor_ioctl get enabled status: 1
<6>[ 778.161499] __spi_bma150_set_mode: BMA get into SLEEP mode!
<6>[ 791.238342] batt: 80%, 4089 mV, 423 mA (415 avg), 27.6 C, 1091 mAh
<6>[ 798.738037] capella_cm3602_ioctl cmd 1
<6>[ 798.738159] lightsensor_ioctl get enabled status: 1
<6>[ 798.753601] __spi_bma150_set_mode: BMA get into NORMAL mode!
<6>[ 802.085937] capella_cm3602_ioctl cmd 1
<6>[ 802.085937] lightsensor_ioctl get enabled status: 1
<6>[ 802.271789] __spi_bma150_set_mode: BMA get into SLEEP mode!
<6>[ 808.274749] cable_status_update: status=0
<6>[ 808.275482] msm_hsusb_set_vbus_state: 0
<6>[ 808.275909] hsusb: ONLINE -> OFFLINE
<6>[ 808.276245] usb: lpm exit
<6>[ 808.288330] usb: notify offline
<6>[ 808.288757] bravo_usb_phy_reset
<6>[ 808.289123] msm_hsusb_phy_reset
<6>[ 808.289611] batt: charging OFF
<6>[ 808.348266] usb: lpm enter
<6>[ 808.348266] usb_suspend_phy
<6>[ 808.349365] usb: send connect type 0
<6>[ 808.349365] fsg_set_ums_state: 0
<4>[ 808.349365] ### notify_usb_connected(0) ###
<6>[ 809.500976] cable_status_update: status=1
<6>[ 809.528320] msm_hsusb_set_vbus_state: 1
<6>[ 809.529022] hsusb: OFFLINE -> ONLINE
<6>[ 809.529357] usb: lpm exit
<6>[ 809.530822] hsusb: reset controller
<6>[ 809.538848] batt: charging SLOW
<6>[ 809.568450] bravo_usb_phy_reset
<6>[ 809.568847] msm_hsusb_phy_reset
<6>[ 809.778442] msm72k_udc: ulpi: write 0x0c to 0x31
<6>[ 809.778717] msm72k_udc: ulpi: write 0x31 to 0x32
<6>[ 809.778839] msm72k_udc: ulpi: write 0x1d to 0x0d
<6>[ 809.779052] msm72k_udc: ulpi: write 0x1d to 0x10
<6>[ 809.779205] usb: notify offline
<6>[ 809.779327] msm_hsusb: enable pullup
<6>[ 809.798339] usb: AC charger
<6>[ 809.818359] usb: lpm enter
<6>[ 809.818542] usb_suspend_phy
<6>[ 809.821197] usb: send connect type 2
<6>[ 809.821502] fsg_set_ums_state: 2
<4>[ 809.821655] ### notify_usb_connected(2) ###
<6>[ 809.829315] batt: charging FAST
<7>[ 814.113616] ALS value: 0x6, level: 1 #
<7>[ 815.128906] ALS value: 0x0, level: 1 #
<6>[ 828.444671] capella_cm3602_ioctl cmd 1
<6>[ 828.444885] lightsensor_ioctl get enabled status: 1
<6>[ 828.453491] __spi_bma150_set_mode: BMA get into NORMAL mode!
<6>[ 841.308776] batt: 81%, 4084 mV, 420 mA (346 avg), 28.5 C, 1097 mAh
I hope somebody can help
greetings

I have the same problem, phone is attempting to be repaired but I doubt they can fix it.
Had water damage at my usb connector, which i though was the cause but issue still exists after being fixed.
downgraded hboot
flashed stock ruu via PB99IMG.zip method
attempted various methods of the mtd0.img fix

still broken dam usb
Hi,
Got my phone back... but still not joy after they replaced usb connector.
Still have the same issue, but now I have no root (using visionary+ for temp root) and s-on.
Issue : PC unable to connect\detect to desire in hboot/fastboot/normal operations ie... not device detected.
Ps... i think issue occurred after doing oxygen rom as well
Code:
<6>[14908.060607] SMEM_APPS_DEM_SLAVE_DATA: 35s 2010000 0 0 1 0 30100000 2 RPCCA
LL 5c
<6>[14908.060607] wakeup wake lock: SMD_RPCCALL
<6>[14908.060882] perflock_notifier_call: cpufreq recover policy 245000 998400
<6>[14908.061248] batt: M2A_RPC: cable_update: USB at 14895032896089 (2011-02-25
07:39:19.574920653 UTC)
<6>[14908.061523] batt: htc_cable_status_update: 0 -> 1
<6>[14908.061798] msm_hsusb_set_vbus_state: 1
<6>[14908.061950] hsusb: OFFLINE -> ONLINE
<6>[14908.062103] usb: lpm exit
<6>[14908.063812] hsusb: reset controller
<6>[14908.063934] [HTC_BATT] cable change to 1
<6>[14908.064025] batt: ds2784_notify: 0 1 at 14895035734223 (2011-02-25 07:39:1
9.577697752 UTC)
<6>[14908.064331] batt: charger ON (SLOW) at 14895035947846 (2011-02-25 07:39:19
.578002928 UTC)
<4>[14908.068084] Restarting tasks ... done.
<6>[14908.073272] sleep_stat.2: 12966403s 10991 12944611s 10643 - 0 13 207 - 0 0
- 0 0 0 0 0(2011-02-25 07:39:23.505737305 UTC)
<6>[14908.073455] suspend: exit suspend, ret = 0 (2011-02-25 07:39:23.505950928
UTC)
<6>[14908.073669] [R] resume end
<6>[14908.073760] [R] suspend start
<6>[14908.073883] suspend: abort suspend
<6>[14908.074066] active wake lock vbus_present
<6>[14908.098663] bravo_usb_phy_reset
<6>[14908.098785] msm_hsusb_phy_reset
<6>[14908.308624] msm72k_udc: ulpi: write 0x0c to 0x31
<6>[14908.309265] msm72k_udc: ulpi: write 0x31 to 0x32
<6>[14908.309600] msm72k_udc: ulpi: write 0x1d to 0x0d
<6>[14908.310211] msm72k_udc: ulpi: write 0x1d to 0x10
<6>[14908.310607] usb: notify offline
<6>[14908.310943] msm_hsusb: enable pullup
<6>[14908.314575] msm72k_udc: usb: suspend
<6>[14908.328582] usb: not AC charger
<6>[14908.628723] usb: send connect type 3
<6>[14908.629364] fsg_set_ums_state: 1
<6>[14908.629699] ums: set state 1
<6>[14908.638214] batt:online=1
<6>[14908.639617] [HTC_BATT] cable change to 1
<6>[14908.640563] batt: ds2784_notify: 0 1 at 14895612394381 (2011-02-25 07:39:2
4.073028566 UTC)
<6>[14908.641265] batt: charger ON (SLOW) at 14895613370943 (2011-02-25 07:39:24
.073730470 UTC)
<6>[14908.921600] request_suspend_state: wakeup (3->0) at 14895893064561 (2011-0
2-25 07:39:24.354064957 UTC)
<6>[14908.921936] [R] late_resume start
<6>[14908.922058] lcdc_resume: resuming
<4>[14908.922180] samsung_oled_panel_init()
<6>[14908.990783] capella_cm3602_ioctl cmd 2
<6>[14908.990905] capella_cm3602_disable
<6>[14908.991027] capella_cm3602_disable: already disabled
<6>[14908.991210] capella_cm3602_ioctl cmd 1
<6>[14908.991332] lightsensor_ioctl set value = 1
<6>[14908.991516] lightsensor_enable
<3>[14908.991607] lightsensor_enable: microp is suspended
<6>[14908.991729] lightsensor_ioctl get enabled status: 1
<6>[14909.233154] msmfb: ready, waiting for full update
<6>[14909.233489] bravo_ts_power: power 1
<6>[14909.256652] msmfb: pan_update in state(1)
<6>[14909.256652] msmfb: full update starting
<6>[14909.267913] msmfb: pan_update in state(3)
<6>[14909.283782] msmfb: full update completed
<6>[14909.283874] msmfb: turning on panel
<6>[14909.283874] lcdc_unblank: ()
<4>[14909.283905] amoled_panel_unblank
<4>[14909.291503] amoled_panel_unblank: last_val = 90
<4>[14909.388610] wlan: power active. usb_type:3
<4>[14909.401947] wlan: update dtim listern interval: 0
<7>[14909.402648] __capella_cm3602_power: Turn the capella_cm3602 power on
<6>[14909.402679] sleep_stat.3: 12966403s 10991 12944611s 10643 - 0 13 207 - 0 0
- 0 0 0 0 0(2011-02-25 07:39:24.835144068 UTC)
<3>[14909.402709] curcial_oj_late_resume: enter
<3>[14909.404449] curcial_oj_poweron:OJ power enable(1)
<6>[14909.490234] OpticalJoystick Device ID: 0d
<6>[14909.496704] OJ Driver: Revision : 02
<6>[14909.501617] [R] late_resume end
<7>[14910.205230] ALS value: 0x0, level: 1 #
<7>[14910.214782] ALS value: 0x0, level: 1 #
<6>[14910.389862] [email protected], 4749
<6>[14910.729736] [email protected], 6441
<6>[14922.707183] capella_cm3602_ioctl cmd 1
<6>[14922.707305] lightsensor_ioctl get enabled status: 1
<6>[14922.719879] __spi_bma150_set_mode: BMA get into NORMAL mode!
<6>[14930.603973] capella_cm3602_ioctl cmd 1
<6>[14930.604187] lightsensor_ioctl get enabled status: 1
<6>[14930.631195] __spi_bma150_set_mode: BMA get into SLEEP mode!
<6>[14937.077880] [HTC_BATT]RSNSP=67,RARC=81,Vol=4016mV,Current=136mA,Temp=322C(
1/10)
<6>[14937.078247] batt: charging SLOW
<3>[14952.175964] init: sys_prop: Unable to stop service ctl [adbd] uid: 10093 p
id:4900
<3>[14952.188079] init: sys_prop: permission denied uid:10093 name:service.adb.
tcp.port
<3>[14952.199890] init: sys_prop: Unable to start service ctl [adbd] uid: 10093
pid:4902
<6>[14965.169830] disabling adb
<6>[14965.170013] hsusb: ONLINE -> RESET
<6>[14965.170135] msm_hsusb: disable pullup
<6>[14965.170257] hsusb: reset controller
<6>[14965.170654] adb_release
<6>[14965.208709] bravo_usb_phy_reset
<6>[14965.208862] msm_hsusb_phy_reset
<6>[14965.418609] msm72k_udc: ulpi: write 0x0c to 0x31
<6>[14965.418823] msm72k_udc: ulpi: write 0x31 to 0x32
<6>[14965.418914] msm72k_udc: ulpi: write 0x1d to 0x0d
<6>[14965.419097] msm72k_udc: ulpi: write 0x1d to 0x10
<6>[14965.419250] usb: notify offline
<6>[14965.419372] msm_hsusb: enable pullup
<6>[14965.419555] hsusb: RESET -> ONLINE
<6>[14965.422576] msm72k_udc: usb: suspend
<7>[14973.482391] ALS value: 0xC, level: 1 #
<7>[14975.492218] ALS value: 0x0, level: 1 #
<6>[14987.178466] [HTC_BATT]RSNSP=67,RARC=81,Vol=4021mV,Current=137mA,Temp=325C(
1/10)
Using ADB Wireless to get access to phone... but need to work out how to root my HBOOT 93.xxx
Can downgrade I guess to 83.xx but not sure if that will help

When you formatted your PC you htc sync drivers are also deleted. My desire had also problems with not getting recognized because I never had installed htc sync when going to windows 7 ultimate. After install en delete of htc sync (drivers stay in place) I never had any issues with recognising.

[Q] emcc identity crisis

Background:
My Samsung Galaxy S died, so I am using my backup rooted G2 with CM7.
After the Market downloaded all of my apps onto the G2 (this failed for a bunch of apps and had to be restarted a few times to complete), the phone started to freeze randomly.
Today it just boots to the HTC logo.
Recovery fails and complains about /cache and /data not found.
Through some troubleshooting, I found that those are mounted on /dev/block/mmcblk0p#
Any attempt to read that block device throws I/O errors.
I was able to confim that my SD card is /dev/block/mmcblk1 and can mount that and access the files on it.
Thought the emcc was dead but:
fastboot oem check_emmc_mid
... INFOManufacturer ID, MID=15
INFOeMMC should be samsung
OKAY
Notice that is says SAMSUNG (hmmm.. does it somehow think it is the Galazy S phone?)
Questions:
- Is this phone dead?
- Should the check_emmcc against an HTC phone report Samsung?
- There does not seem to be any mmcblk0, (I assume, from the hundreds of articles I've read so far, that this would be the SDCard), so how can I tell the system to use mmcblk1?
- Can I change /etc/fstab to point to new partitions that I would create on SDCard (mmcblk1p#)
- Any other ideas?
Thanks in advance.

The chip made by Samsung on our phones is prone to read/write failures making the phone essentially a brick. You may be able to run os off of SD card.
more info here
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my Nexus 7 using xda premium

demkantor said:
The chip made by Samsung on our phones is prone to read/write failures making the phone essentially a brick. You may be able to run os off of SD card.
more info here
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
@demkantor : Thanks for the quick reply (wish my filters had't junked the notification). I will give this a try and report back here.

demkantor said:
The chip made by Samsung on our phones is prone to read/write failures making the phone essentially a brick. You may be able to run os off of SD card.
more info here
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
That was quite a bit to go through and I learned a whole lot. Thanks.
From what I've been able to gather, seems I have a fried chip (hmm, sounds tasty).
I didn't find any articles, however, on running the OS from the SD.
Just in case, here is all the system info I gathered along the way. Perhaps you can confirm that my chip is indeed dead and determine if this is capable of running off the SD or maybe I missed something.
Code:
~ # dmesg | grep mmc0
<3>[ 4.308654] mmc0: No card detect facilities available
<6>[ 4.309295] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 8
<6>[ 4.309417] mmc0: Platform slot type: MMC
<6>[ 4.309661] mmc0: 4 bit data mode disabled
<6>[ 4.309783] mmc0: 8 bit data mode enabled
<6>[ 4.309936] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 4.310180] mmc0: Slot eject status = 0
<6>[ 4.310302] mmc0: Power save feature enable = 1
<6>[ 4.310546] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x0bb6d000
<6>[ 4.310668] mmc0: DM cmd busaddr 0x0bb6d000, cmdptr busaddr 0x0bb6d300
<6>[ 4.466278] mmc0: new high speed MMC card at address 0001
<6>[ 4.468261] mmcblk0: mmc0:0001 M4G2DE 2.04 GiB
<3>[ 5.746704] mmc0: failed to get card ready
<6>[ 5.746826] mmc0: reinit card
<4>[ 5.746978] mmc0: Starting deferred resume
<6>[ 7.786712] mmc0: Deferred resume failed
<3>[ 7.885559] mmc0: DMA channel flushed (0x80000004)
<6>[ 7.885986] mmc0: Controller has been reset
<6>[ 7.886169] mmc0: Worked around bug 1535304
<3>[ 7.887542] mmc0: DMA channel flushed (0x80000004)
<6>[ 7.887969] mmc0: Controller has been reset
<6>[ 7.888153] mmc0: Worked around bug 1535304
<6>[ 7.895080] mmc0: reinit card
<4>[ 7.895202] mmc0: Starting deferred resume
<6>[ 9.926788] mmc0: Deferred resume failed
<3>[ 10.075073] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.075500] mmc0: Controller has been reset
<6>[ 10.075714] mmc0: Worked around bug 1535304
<3>[ 10.077087] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.077514] mmc0: Controller has been reset
<6>[ 10.077697] mmc0: Worked around bug 1535304
<6>[ 10.084564] mmc0: reinit card
<4>[ 10.084686] mmc0: Starting deferred resume
<6>[ 12.116760] mmc0: Deferred resume failed
<3>[ 12.119018] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.119445] mmc0: Controller has been reset
<6>[ 12.119659] mmc0: Worked around bug 1535304
<3>[ 12.121032] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.121490] mmc0: Controller has been reset
<6>[ 12.121795] mmc0: Worked around bug 1535304
<6>[ 12.128601] mmc0: reinit card
<4>[ 12.128723] mmc0: Starting deferred resume
<6>[ 14.166809] mmc0: Deferred resume failed
<3>[ 14.279052] mmc0: DMA channel flushed (0x80000004)
<6>[ 14.279510] mmc0: Controller has been reset
<6>[ 14.279785] mmc0: Worked around bug 1535304
<3>[ 14.281036] mmc0: DMA channel flushed (0x80000004)
<6>[ 14.281463] mmc0: Controller has been reset
<6>[ 14.281768] mmc0: Worked around bug 1535304
<6>[ 14.288574] mmc0: reinit card
<4>[ 14.288696] mmc0: Starting deferred resume
<6>[ 16.326751] mmc0: Deferred resume failed
<3>[ 16.328826] mmc0: DMA channel flushed (0x80000004)
<6>[ 16.329254] mmc0: Controller has been reset
<6>[ 16.329559] mmc0: Worked around bug 1535304
<3>[ 16.330810] mmc0: DMA channel flushed (0x80000004)
<6>[ 16.331237] mmc0: Controller has been reset
<6>[ 16.331542] mmc0: Worked around bug 1535304
<6>[ 16.338348] mmc0: reinit card
<4>[ 16.338470] mmc0: Starting deferred resume
<6>[ 18.376800] mmc0: Deferred resume failed
<3>[ 18.586914] mmc0: DMA channel flushed (0x80000004)
<6>[ 18.588073] mmc0: Controller has been reset
<6>[ 18.588836] mmc0: Worked around bug 1535304
<3>[ 18.590942] mmc0: DMA channel flushed (0x80000004)
<6>[ 18.592102] mmc0: Controller has been reset
<6>[ 18.592559] mmc0: Worked around bug 1535304
<6>[ 18.601043] mmc0: reinit card
<4>[ 18.601715] mmc0: Starting deferred resume
<6>[ 20.636810] mmc0: Deferred resume failed
<3>[ 20.640533] mmc0: DMA channel flushed (0x80000004)
<6>[ 20.641998] mmc0: Controller has been reset
<6>[ 20.642425] mmc0: Worked around bug 1535304
<3>[ 20.644561] mmc0: DMA channel flushed (0x80000004)
<6>[ 20.645721] mmc0: Controller has been reset
<6>[ 20.646148] mmc0: Worked around bug 1535304
<6>[ 20.654327] mmc0: reinit card
<4>[ 20.654998] mmc0: Starting deferred resume
<6>[ 22.686828] mmc0: Deferred resume failed
+++
# cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0\:0001/name
M4G2DE (confirmed that this is the bad Samsung chip)
+++
[email protected]:~$ fastboot devices
SH12RRXXXXXX fastboot
+++
[email protected]:~/Downloads/G2$ fastboot flash recovery recovery.zip
sending 'recovery' (5333 KB)... FAILED (status malformed (1 bytes))
+++
VISION PVT ENG S-OFF
HBOOT-0.76.200 (PC1010000)
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Aug 20 2010,16:51:01
SYSTEM INFO
SN-SH12RRXXXXX
LCD-SO
TOUCH PANEL-ATMELC12_10aaT
Commit-977d3036
OS Ver.-1.22.531.8
CID-11111111
eMMC-samsung 2091MB 4284415sectors

Read up on this
www.thinkthinkdo.com/trac/project1/wiki/boot_sdcard
And this
http://forum.xda-developers.com/showthread.php?p=29940580
Sent from my HTC Vision using xda premium

demkantor said:
Read up on this
www.thinkthinkdo.com/trac/project1/wiki/boot_sdcard
And this
http://forum.xda-developers.com/showthread.php?p=29940580
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I am probably restating the obvious, but I just want to go on the record here:
You Totally ROCK!!!!!!
It's alive! Now to see if I can get a copy kbeezie's CM7 UPDATE.zip. (OK, so I am greedy)

[Q] sdcard suddenly stopped working

I have had my refurbished HTC Vision for about three weeks and it hadn't had any problems. Then yesterday, I rebooted it and now the sdcard doesn't work. Not just that it doesn't mount, rather there is not even a /dev/block/mmcblk1 device.
Here is what I tried:
* Boot into ClockworkMod, and run adb shell. Still no /dev/block/mmcblk1.
* Boot into fastboot and run "fastboot oem enableqxdm 0" and "fastboot oem eraseconfig".
* Per some random instructions on the net, I held vol-up and power, then pulled the battery after the phone vibrated. Then I held vol-up, vol-down, power and did the same. Then the fastboot commands again.
* Bent the sdcard port's pins out a bit with tweezers.
* SDcard works in computer (Linux).
* Tried another card that has nothing but a vfat partition.
Nothing works! There are some errors in dmesg:
Code:
$ dmesg |grep mmc
<5>[ 0.000000] Kernel command line: board_vision.disable_uart2=0 board_vision.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0 board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=true androidboot.baseband=26.02.01.15_M2 androidboot.cid=T-MOB010 androidboot.batt_poweron=good_battery androidboot.carrier=TMUS androidboot.mid=PC1010000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT09LR200858 androidboot.bootloader=0.76.2000 no_console_suspend=1 console=null
<6>[ 2.532989] vision: vision_init_mmc
<3>[ 3.267822] mmc0: No card detect facilities available
<6>[ 3.268341] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 3.268615] mmc0: Platform slot type: MMC
<6>[ 3.268737] mmc0: 4 bit data mode disabled
<6>[ 3.269012] mmc0: 8 bit data mode enabled
<6>[ 3.269134] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.269378] mmc0: Slot eject status = 0
<6>[ 3.269531] mmc0: Power save feature enable = 1
<6>[ 3.269653] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2b774000
<6>[ 3.269927] mmc0: DM cmd busaddr 0x2b774000, cmdptr busaddr 0x2b774300
<6>[ 3.270751] mmc1: Qualcomm MSM SDCC at 0x00000000a3000000 irq 96,0 dma 8
<6>[ 3.270996] mmc1: Platform slot type: N/A
<6>[ 3.271148] mmc1: 4 bit data mode enabled
<6>[ 3.271392] mmc1: 8 bit data mode disabled
<6>[ 3.271514] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.271789] mmc1: Slot eject status = 1
<6>[ 3.271911] mmc1: Power save feature enable = 1
<6>[ 3.272064] mmc1: DM non-cached buffer at ffa0d000, dma_addr 0x2b777000
<6>[ 3.272308] mmc1: DM cmd busaddr 0x2b777000, cmdptr busaddr 0x2b777300
<6>[ 3.273468] mmc2: Qualcomm MSM SDCC at 0x00000000a3100000 irq 100,0 dma 8
<6>[ 3.273712] mmc2: Platform slot type: SD
<6>[ 3.273834] mmc2: 4 bit data mode enabled
<6>[ 3.273986] mmc2: 8 bit data mode disabled
<6>[ 3.274230] mmc2: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.274353] mmc2: Slot eject status = 0
<6>[ 3.274658] mmc2: Power save feature enable = 1
<6>[ 3.274810] mmc2: DM non-cached buffer at ffa0e000, dma_addr 0x2b778000
<6>[ 3.275054] mmc2: DM cmd busaddr 0x2b778000, cmdptr busaddr 0x2b778300
<6>[ 3.275207] mmc2: Polling status mode enabled
<6>[ 3.425598] mmc0: new high speed MMC card at address 0001
<6>[ 3.427093] mmcblk0: mmc0:0001 SEM04G 2.09 GiB
<6>[ 3.428100] mmcblk0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 >
<6>[ 3.569030] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: barrier=1
<4>[ 3.703063] mmc2: high speed mode max_dtr = 50000000
<4>[ 3.703491] mmc2: host does not support reading read-only switch. assuming write-enable.
<6>[ 3.703643] mmc2: new high speed SDHC card at address 0001
<6>[ 3.704498] mmcblk1: mmc2:0001 00000 7.41 GiB
<6>[ 3.705291] mmcblk1: p1
<4>[ 4.648254] EXT4-fs (mmcblk0p26): warning: maximal mount count reached, running e2fsck is recommended
<7>[ 4.651062] EXT4-fs (mmcblk0p26): ext4_orphan_cleanup: deleting unreferenced inode 24790
<7>[ 4.655670] EXT4-fs (mmcblk0p26): ext4_orphan_cleanup: deleting unreferenced inode 24741
<6>[ 4.657012] EXT4-fs (mmcblk0p26): 2 orphan inodes deleted
<6>[ 4.657379] EXT4-fs (mmcblk0p26): recovery complete
<6>[ 4.703216] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts: noauto_da_alloc
<4>[ 4.758331] EXT4-fs (mmcblk0p27): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 4.760345] EXT4-fs (mmcblk0p27): recovery complete
<6>[ 4.762298] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: barrier=1
<4>[ 4.886474] EXT4-fs (mmcblk0p28): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 4.888580] EXT4-fs (mmcblk0p28): recovery complete
<6>[ 4.890563] EXT4-fs (mmcblk0p28): mounted filesystem with ordered data mode. Opts: barrier=1
<7>[ 20.824981] mmc1: card_present 1
<6>[ 20.825134] mmc1: Slot status change detected (0 -> 1)
<7>[ 23.383300] mmc1: queuing CIS tuple 0x91 length 3
<6>[ 23.383331] mmc1: new high speed SDIO card at address 0001
<3>[ 38.746368] mmc2: Data CRC error
<6>[ 38.746978] mmc2: Controller has been reset
<3>[ 38.747467] mmcblk1: error -84 transferring data, sector 2080, nr 1, card status 0x900
<6>[ 38.747619] mmc2: reinit card
<4>[ 38.747863] mmc2: Starting deferred resume
<3>[ 38.814849] mmc2: Data CRC error
<6>[ 38.815521] mmc2: Controller has been reset
<3>[ 38.815856] mmc2: Re-init card rc = -84 (retries = 5)
<3>[ 38.997650] mmc2: Data CRC error
<6>[ 38.998291] mmc2: Controller has been reset
<3>[ 39.001403] mmc2: Re-init card rc = -84 (retries = 4)
<3>[ 39.200927] mmc2: Data CRC error
<6>[ 39.201507] mmc2: Controller has been reset
<3>[ 39.201721] mmc2: Re-init card rc = -84 (retries = 3)
<3>[ 39.384826] mmc2: Data CRC error
<6>[ 39.385406] mmc2: Controller has been reset
<3>[ 39.385650] mmc2: Re-init card rc = -84 (retries = 2)
<3>[ 39.583618] mmc2: Data CRC error
<6>[ 39.584228] mmc2: Controller has been reset
<3>[ 39.584472] mmc2: Re-init card rc = -84 (retries = 1)
<6>[ 39.666137] mmc2: Deferred resume failed
<6>[ 39.666412] mmc: reinit failed, remove card
<6>[ 39.666625] mmc2: remove card
<3>[ 39.666778] end_request: I/O error, dev mmcblk1, sector 2080
<3>[ 39.667053] Buffer I/O error on device mmcblk1p1, logical block 32
<4>[ 39.667205] lost page write due to I/O error on mmcblk1p1
<3>[ 39.667480] mmc_blk_issue_rq failed!!
<6>[ 39.667633] mmc2: mmc_remove_sd_card
<6>[ 39.667907] mmc2: card 0001 removed
<3>[ 39.670318] mmcblk1: error -123 sending status comand
<3>[ 39.670471] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.670867] end_request: I/O error, dev mmcblk1, sector 2080
<3>[ 39.671783] mmc_blk_issue_rq failed!!
<3>[ 39.671966] mmcblk1: error -123 sending read command, response 0x0
<4>[ 39.672210] mmcblk1: retrying using single block read
<3>[ 39.672332] mmcblk1: error -123 sending status comand
<3>[ 39.672607] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.672882] end_request: I/O error, dev mmcblk1, sector 32378
<3>[ 39.673126] end_request: I/O error, dev mmcblk1, sector 32379
<3>[ 39.673278] end_request: I/O error, dev mmcblk1, sector 32380
<3>[ 39.673522] end_request: I/O error, dev mmcblk1, sector 32381
<3>[ 39.673675] end_request: I/O error, dev mmcblk1, sector 32382
<3>[ 39.673919] end_request: I/O error, dev mmcblk1, sector 32383
<3>[ 39.674072] end_request: I/O error, dev mmcblk1, sector 32384
<3>[ 39.674316] end_request: I/O error, dev mmcblk1, sector 32385
<3>[ 39.674499] mmc_blk_issue_rq failed!!
<3>[ 39.674774] mmcblk1: error -123 sending status comand
<3>[ 39.674926] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.675292] end_request: I/O error, dev mmcblk1, sector 32378
... and so on. In this run, I see that at least briefly the kernel could read the mmcblk1 partition table (although there still was not /dev/block/mmcblk1). However, most of the time it can't and just gives the CRC errors.
Is this a hardware or software problem. Any suggestions? Thanks.

Almost 100% hardware from what you have written, I would suggest disconnecting the ribbion cable, clean it, and put it back. If it still won't work a new sd card tray is about 10$ on ebay and a snap to put it
Sent from my HTC Vision using xda premium

worked!
demkantor said:
Almost 100% hardware from what you have written, I would suggest disconnecting the ribbion cable, clean it, and put it back. If it still won't work a new sd card tray is about 10$ on ebay and a snap to put it
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Worked, thanks!!! The CRC errors made me suspect hardware, but I wanted someone else to say it before I tore the thing open. I've always had bad luck tearing these things apart (only junk phones in the past), but I bought a cheapo disassembly kit a while back which has helped greatly with popping the case off. And thankfully I only had to get to about step three of the instructions before the ribbon cable was accessible!

WiFi not working on on ANY ROM

Hi everyone,
sorry for the lengthy post, but I wanted to be precise. Please read the whole of it, if you think you might be able to help. I love this phone but it's useless without WiFi for me. I am also sorry, if I unwittingly violated any forum rules. I tried the best I could.
Currently, I am having a severe issue with the WiFi of my HTC Desire Z. It won't turn on or do anything. First of all: I worked myself through all threads that I could find which were just remotely connected with this issue, also in forums concerning other devices. I still hope I overlooked something... Btw.: My phone is almost 3 years old and a German version. I don't remember what method I used to root it since it was one of the first things I did.
The aforementioned problem appeared right after the following incident: My phone went out of battery while I was listening to an audiobook via Audible. I put the phone in airplane mode some 10 minutes earlier to prevent this, very <irony>successfully<\irony>...
After rebooting, I tried to turn WiFi on, but it just kept telling me "turning wifi on". The switch turned grey and nothing happened. I tried rebooting, turning WiFi on and of several times as well as airplane mode. I flashed the following ROMs, some of which I have been using sometime earlier where WiFi has definitively been working: Andromadus JellyBean by Flinny (version 123, 133 if that matters), all CM stable releases, Andromadus Mimicri 1.50 together with the sugested WiFixIt. With these ROMs I did the same. I could not find any stock ROM that has been able to boot. I did not try to reverse root and s-off (seems pointless to me).
I update the Radio to (afaik most recent version) and I downgraded it a few other versions without any change. I also did a superwipe with the tools given on the following page and reinstalled the ROMs, to no avail: http://forum.xda-developers.com/showthread.php?t=1044992
I also tried different sim-cards (from UK and Germany), both with and without sim-card and sd-card. Also no success.
Bluetooth is working flawlessly. I have just copied a file from my Laptop over to my phone via BT, which is strange, because, as far as I know, both WiFi and BT use the same chips and the same antenna.
I pulled all the logs I found (logcat: main, event, radio; dmesg) and boiled it down to the driver not being able to be loaded. Please correct me, but the WiFi drivers come with the ROM, therefore it CANNOT be due to a faulty driver, since I installed some that worked months ago (tried this before and after flashing different radios).
I reckon that the following parts are the important ones, but I attached the complete logs (cover the boot process and me trying to turn WiFi on) to be on the safe side. As far as I understand, it just says that it tries to load the driver bot fails to attach some kind of module.
Dmesg:
<6>[ 45.185119] [WLAN] ## wifi_probe
<4>[ 45.185302] [WLAN][WRN] wifi_set_power = 1
<6>[ 45.185455] [WLAN]vision_wifi_power: 1
<6>[ 46.075988] [WLAN] wifi_set_carddetect = 1
<6>[ 46.076141] vision_wifi_set_carddetect: 1
<6>[ 46.076293] mmc1: Slot status change detected (0 -> 1)
<6>[ 46.089599] [WLAN] Dongle Host Driver, version 5.90.125.120
<6>[ 46.089599] Compiled in drivers/net/wireless/bcmdhd on Oct 1 2012 at 17:46:03
<4>[ 46.129547] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
<6>[ 46.129882] mmc1: new high speed SDIO card at address 0001
<6>[ 47.087982] [LED]pm8058_drvx_led_brightness_set: bank 3 brightness 0 +
<6>[ 47.088287] [LED]pm8058_drvx_led_brightness_set: bank 3 brightness 0 -
<6>[ 47.935516] [TP][email protected],797
<3>[ 48.187652] mmc1: CMD53: Data timeout
<6>[ 48.187927] mmc1: SDCC PWR is ON
<6>[ 48.188110] mmc1: SDCC clks are ON, MCLK rate=50000000
<6>[ 48.188262] mmc1: SDCC irq is enabled
<6>[ 48.188507] ===== SDCC-CORE: Register Dumps @base=0xec832000 =====
<6>[ 48.188629] Reg=0x00: 0x00000003, 0x00009b00, 0x15000004, 0x00001475.
<6>[ 48.188903] Reg=0x10: 0x00000035, 0x00001000, 0x00000000, 0x00000000.
<6>[ 48.189025] Reg=0x20: 0x00000000, 0x05f5e100, 0x00000004, 0x00000043.
<6>[ 48.189270] Reg=0x30: 0x00000004, 0x00400200, 0x00000000, 0x00a081ff.
<6>[ 48.189514] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 48.189666] Reg=0x50: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 48.189910] Reg=0x60: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 48.190063] mmc1: PIO mode
<6>[ 48.190307] mmc1: xfer_size=4, data_xfered=0, xfer_remain=4
<6>[ 48.190429] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0
<4>[ 48.190917] [WLAN][WRN] F1 signature read @0x18000000=0xffffffff
<6>[ 48.797210] [TP][email protected],866
<6>[ 48.798217] [TP]calibration confirm with recal by position
<6>[ 48.823303] [TP]0x01 0x10 0xA8 0x85 0x00
<6>[ 48.835113] [TP]0x01 0x00 0xA8 0x85 0x00
<3>[ 50.226043] mmc1: CMD53: Data timeout
<6>[ 50.226226] mmc1: SDCC PWR is ON
<6>[ 50.226409] mmc1: SDCC clks are ON, MCLK rate=50000000
<6>[ 50.226684] mmc1: SDCC irq is enabled
<6>[ 50.226806] ===== SDCC-CORE: Register Dumps @base=0xec832000 =====
<6>[ 50.227081] Reg=0x00: 0x00000003, 0x00009b00, 0x15000004, 0x00001475.
<6>[ 50.227233] Reg=0x10: 0x00000035, 0x00001000, 0x00000000, 0x00000000.
<6>[ 50.227478] Reg=0x20: 0x00000000, 0x05f5e100, 0x00000004, 0x00000043.
<6>[ 50.227630] Reg=0x30: 0x00000004, 0x00000200, 0x00000000, 0x00a081ff.
<6>[ 50.227874] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 50.228149] Reg=0x50: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 50.228271] Reg=0x60: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 50.228546] mmc1: PIO mode
<6>[ 50.228668] mmc1: xfer_size=4, data_xfered=0, xfer_remain=4
<6>[ 50.228820] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0
<4>[ 50.229370] [WLAN][WRN] dhdsdio_probe_attach: si_attach failed!
<4>[ 50.229644] [WLAN][WRN] dhdsdio_probe: dhdsdio_probe_attach failed
<4>[ 50.242645] [WLAN][WRN] dhd_module_init: wifi_fail_retry is true
<6>[ 50.247802] [WLAN] ## wifi_remove
<4>[ 50.247985] [WLAN][WRN] wifi_set_power = 0
<6>[ 50.248107] [WLAN]vision_wifi_power: 0
<6>[ 51.038665] [WLAN] wifi_set_carddetect = 0
<6>[ 51.038818] vision_wifi_set_carddetect: 0
<6>[ 51.038970] mmc1: Slot status change detected (1 -> 0)
<6>[ 51.039978] mmc1: card 0001 removed
<6>[ 51.041442] [WLAN] ## wifi_remove leave
Click to expand...
Click to collapse
Logcat main:
E/CommandListener( 115): Failed to open /proc/sys/net/ipv6/conf/wlan0/disable_ipv6: No such file or directory
E/WifiStateMachine( 294): Failed to disable IPv6: java.lang.IllegalStateException: command '1 interface ipv6 wlan0 disable' failed with '400 1 Failed to change IPv6 state (No such file or directory)'
...
I/WifiService( 294): WifiService starting up with Wi-Fi enabled
D/WifiService( 294): setWifiEnabled: true pid=294, uid=1000
D/WifiWatchdogStateMachine( 294): Disabling poor network avoidance for wi-fi only device
...
may times:
E/WifiHW ( 294): Supplicant not running, cannot connect
E/WifiHW ( 294): Supplicant not running, cannot connect
E/WifiStateMachine( 294): Failed to setup control channel, restart supplicant
Click to expand...
Click to collapse
Methinks it is a hardware issue and I am very close to taking the thing apart, which will possibly break something else... Second last comment: As I try to turn WiFi on via the status bar, it reboots after like one minute. Last comment: Is there any way to check whether it really is a hardware fault?
I apprecieate any comment intended to be helpful. Even when it is you telling me that it IS a hardware issue. If you need any further information, I am more than happy to provide it. I would also be happy to make the life of my phone-saviour more enjoyable with one or two pints of something, if we can arrange a meeting.

haha, i doubt ill be in germany any time soon... but i will be in greece in a month or so...
well it sounds like youre trying all the right things and it possibly is a hardware fault. but being you rooted 3 years ago you dont have true radio s-off, as it wasnt around.
if it were me, i would unroot, then follow the gfree method to downgrade and root via gfree, this will fully wipe out all partitions (except efs) and then flash a tried and true rom like cm7, hopefully all will be well at this point... if not, hardware...

Thank you for your advice. I did as you told me and went through the pain to reinstall stock Froyo as well as stock recovery and hboot. I also had s-on (at leats that's what hboot and gfree_verify said). Then I went to reroot it again, this time using gfree1.0 (which was definitely not what I used last time).
But unfortunately WiFi did not work neither with stock Froyo nor after rerooting and running CM7. Bluetooth still worked fine in every case... Log still says the exact same thing.
There is just two things left that might be worth a try, but it's a long shot. Could it be a problem with some data on the efs-partition that is messed up? As far as I understand it that is where android stores important information about IMEI, MAC-adress an the like. But I really do not know how to restore this partition even if it were the cause. Or could it be a problem with the RIL since that is what communicates with the radio? But I also do not know how to restore this if it were the cause (but it's just said that matching the RIL might just improve performance).
What's your opinion about this? Do you think that a look at the phone's insides might yield any results/certainty?

Unfortunetly if you never made a backup of your efs partition there is no way to restore this, you can back it up now, wipe it, restore and see if that helps but I doubt it.
Ril is matched when you downgraded so that's not it. Trutfully my best guess is hardware, sorry
Sent from my HTC Vision using xda premium

Unfortunately, I never made a backup of my /efs. I also tried wiping it, but no change.
The only sad thing is, that there is no adequate replacement...
I still don't get why BT is working and WiFi is not while both use the same chip, but that will stay a mystery forever unresolved.
Is there any way to close this tread? Somehow I don't see any.

Mine does what you are describing, but it's cause my gf dropped it
Sent from my SGH-T999 using xda premium
---------- Post added at 01:10 AM ---------- Previous post was at 01:08 AM ----------
And disconnected the wireless "modem"
The drop was pretty severe, however. I needed a whole new battery cover
Sent from my SGH-T999 using xda premium

op did you solved error ?

Nope, I could not solve the issue and I did not disassemble my phone and risk being left without one. So far, my mobile data plan has been sufficient and for large data, I access the internet via a USB-cable. I will get a new phone though when I am less busy at work.
Sent from my HTC Vision

[Q] Desire Z (Tmobile G2) Help do I have eMMC problem noted in this forum, HELP!

Hello, I am asking for help. I am new to this forum.
I have a T-Mobile G2 (HTC Vision Z equiv) that I was given by a friend. He rooted it and put CyanogenMod on it.
Two days ago, the phone rebooted of its own, and stayed stuck at the HTC white screen.
I did take the battery out and reinserted it in order to reboot the phone ( I have read several forum threads here about eMMc and battery problems resulting from battery removal, fwtw)
I am asking for assistance to determine if I can restore this phone, if its suffering the eMMC problem that has been noted in this forum, etc. I'm okay with the command line, new to Android hacking, so please keep your comments light.
On my laptop, I am running Linux Mint Nadia 14, I have the Android SDK installed and Oracle Java latest as well. I can bring the phone, plugged in via USB<-->MicroUSB cable, up in Android Debug Bridge, and see its serial number with ./adb devices, as long as my udev and the adb server are started in the right order
I can, using VOL-DOWN and POWER, get to HBOOT. Here is the headers:
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
and below, I have:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
I can then get the phone to RECOVERY,
ClockWorkMod Recovery v3.0.2.4
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recover/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Now, on my laptop, from the platform-tools directory, I can issue:
platform-tools # ./adb devices
List of devices attached
SH12SR201118 recovery
and I can enter adb-shell:
platform-tools # ./adb shell
~ # ls
boot init sys
cache init.rc system
data proc tmp
datadata res ueventd.goldfish.rc
default.prop root ueventd.rc
dev sbin ueventd.vision.rc
emmc sd-ext
etc sdcard
Now the disturbing bits begin, that make me suspect the fried eMMc.
According to /etc/fstab, which when cat'd, yields:
/etc # cat fstab
/dev/block/mmcblk0p27 /cache auto rw
/dev/block/mmcblk0p26 /data auto rw
/dev/block/mmcblk0p25 /system auto rw
/dev/block/mmcblk1p1 /sdcard vfat rw
So is it correct that on my internal eMMC, that is /dev/block/mmcblk0p27 for /cache, ...0p26 for /data, etc?
fdisk is unable to give me any information about /dev/block/mmcblk0:
/etc # /sbin/fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/block/mmcblk0': I/O error
while fdisk is fine to give me information about my sdcard (mmcblk1, according to fstab cat'd above):
/etc # /sbin/fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 2001 MB, 2001731584 bytes
42 heads, 41 sectors/track, 2270 cylinders
Units = cylinders of 1722 * 512 = 881664 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 2271 1954751+ 6 FAT16
Okay, xda folks, what should my next steps be?
thank you very very much,
Forrest :cyclops:

And...where should I go in xda to find actual help?
40 views of this message....and not a single reply? Where do I go for help?

http://forum.xda-developers.com/showthread.php?p=43195539
Sent from my Nexus 4 using Tapatalk 2

That's an information repository for sure, but...
demkantor, you posted a link to your gold mine of information http://forum.xda-developers.com/showthread.php?p=43195539. that's wonderful.
I will use the eMMC testing tips at http://forum.xda-developers.com/showthread.php?t=1983163. Remember that I posted a fairly complete description in my post of my situation....

Does this mean I have a fried eMMC? Looks like it. could someone verify?
Using the procedures on the page http://forum.xda-developers.com/showthread.php?t=1983163, i found the following:
In ADB shell, grepping for the eMMC yields this:
~ # dmesg | grep mmc0
<3>[ 4.904113] mmc0: No card detect facilities available
<6>[ 4.904663] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 8
<6>[ 4.904907] mmc0: Platform slot type: MMC
<6>[ 4.905059] mmc0: 4 bit data mode disabled
<6>[ 4.905273] mmc0: 8 bit data mode enabled
<6>[ 4.905426] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 4.905670] mmc0: Slot eject status = 0
<6>[ 4.905792] mmc0: Power save feature enable = 1
<6>[ 4.905914] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x0bb9a000
<6>[ 4.906158] mmc0: DM cmd busaddr 0x0bb9a000, cmdptr busaddr 0x0bb9a300
<6>[ 5.065429] mmc0: new high speed MMC card at address 0001
<6>[ 5.067108] mmcblk0: mmc0:0001 M4G2DE 2.04 GiB
<3>[ 6.364196] mmc0: failed to get card ready
<6>[ 6.364440] mmc0: reinit card
<4>[ 6.364562] mmc0: Starting deferred resume
<6>[ 8.404327] mmc0: Deferred resume failed
<3>[ 8.510040] mmc0: DMA channel flushed (0x80000004)
<6>[ 8.511199] mmc0: Controller has been reset
<6>[ 8.511962] mmc0: Worked around bug 1535304
<3>[ 8.514099] mmc0: DMA channel flushed (0x80000004)
<6>[ 8.515228] mmc0: Controller has been reset
<6>[ 8.515655] mmc0: Worked around bug 1535304
<6>[ 8.524291] mmc0: reinit card
<4>[ 8.524963] mmc0: Starting deferred resume
<6>[ 10.564331] mmc0: Deferred resume failed
<3>[ 10.715789] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.716217] mmc0: Controller has been reset
<6>[ 10.716430] mmc0: Worked around bug 1535304
<3>[ 10.717803] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.718200] mmc0: Controller has been reset
<6>[ 10.718414] mmc0: Worked around bug 1535304
<6>[ 10.725219] mmc0: reinit card
<4>[ 10.725433] mmc0: Starting deferred resume
<6>[ 12.764282] mmc0: Deferred resume failed
<3>[ 12.766510] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.766967] mmc0: Controller has been reset
<6>[ 12.767181] mmc0: Worked around bug 1535304
<3>[ 12.768585] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.769042] mmc0: Controller has been reset
<6>[ 12.769226] mmc0: Worked around bug 1535304
<6>[ 12.776184] mmc0: reinit card
<4>[ 12.776306] mmc0: Starting deferred resume
<6>[ 14.814331] mmc0: Deferred resume failed
<3>[ 14.936950] mmc0: DMA channel flushed (0x80000004)
<6>[ 14.937408] mmc0: Controller has been reset
<6>[ 14.937622] mmc0: Worked around bug 1535304
<3>[ 14.938964] mmc0: DMA channel flushed (0x80000004)
<6>[ 14.939422] mmc0: Controller has been reset
<6>[ 14.939727] mmc0: Worked around bug 1535304
<6>[ 14.946594] mmc0: reinit card
<4>[ 14.946716] mmc0: Starting deferred resume
<6>[ 16.984283] mmc0: Deferred resume failed
<3>[ 16.986480] mmc0: DMA channel flushed (0x80000004)
<6>[ 16.986938] mmc0: Controller has been reset
<6>[ 16.987152] mmc0: Worked around bug 1535304
<3>[ 16.988525] mmc0: DMA channel flushed (0x80000004)
<6>[ 16.988983] mmc0: Controller has been reset
<6>[ 16.989257] mmc0: Worked around bug 1535304
<6>[ 16.996093] mmc0: reinit card
<4>[ 16.996215] mmc0: Starting deferred resume
<6>[ 19.034301] mmc0: Deferred resume failed
<3>[ 19.175415] mmc0: DMA channel flushed (0x80000004)
<6>[ 19.175872] mmc0: Controller has been reset
<6>[ 19.176208] mmc0: Worked around bug 1535304
<3>[ 19.177459] mmc0: DMA channel flushed (0x80000004)
<6>[ 19.177917] mmc0: Controller has been reset
<6>[ 19.178222] mmc0: Worked around bug 1535304
<6>[ 19.185028] mmc0: reinit card
<4>[ 19.185180] mmc0: Starting deferred resume
<6>[ 21.224273] mmc0: Deferred resume failed
<3>[ 21.226348] mmc0: DMA channel flushed (0x80000004)
<6>[ 21.226806] mmc0: Controller has been reset
<6>[ 21.227111] mmc0: Worked around bug 1535304
<3>[ 21.228393] mmc0: DMA channel flushed (0x80000004)
<6>[ 21.228942] mmc0: Controller has been reset
<6>[ 21.229156] mmc0: Worked around bug 1535304
<6>[ 21.235961] mmc0: reinit card
<4>[ 21.236083] mmc0: Starting deferred resume
<6>[ 23.274291] mmc0: Deferred resume failed

Perhaps I should have posted in General?
I am reading the thread at http://forum.xda-developers.com/showthread.php?t=1039504&page=3, which appears to be in General, about fried eMMCs in the Desire.
If anyone reading this can verify that my phone indeed has that condition (fried eMMC), thanks!