My HTC DESIRE HD is looping on boot...
the only thing I can do, is to launch in fastboot mode...
My info about the phone:
ACE PVt SHIP S-ON RL
HBOOT-0.85.0018
MICROP-0438
RADIO-26.04.02.17_M2
eMMC-boot
Dec 7 2010,00:29:52
the usb debbuging is disabled and my phone wasn't root.
I have try many solution found on web but nothing works...
if anyone have a idea...
P.S: Sorry for my bad very bad english...
well, what kind solution found on web did you try? what version of stock did you have before thas issue?
have you tried to reinstall offcial RUU??
I try with adb but my htc still offline.
I try to run different RUU...signed but always error like Failed remote 42 custom id check fail..
I try many times to reset factory, etc...
the only way that work i with fastboot... i can see the device, run command like fastboot oem rebootRUU, but impossible to do more...
I search a command with fastboot to change the s-on to -off or for adb see my htc....
Your DHD is branded, and as such you will only be able to run a RUU for your particular network/carrier.
If you let us know what that network is we can find a suitable fix for you.
My phone is branded by swisscom (switzerland). i have tried some Ruu... but always an error appears....
With the command fastboot oem gencheckpt
I have this info:
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8D08BCEC
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26503
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is VODAP110
INFOsetting->cid::VODAP110
INFOserial number: HT0B8RX02111
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =473
INFOactive commandline: board_spade.disable_uart2=0 board_spade.
INFOusb_h2w_sw=0 board_spade.disable_sdcard=0 diag.enabled=0 boa
INFOrd_spade.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=true androidboot.baseband=26.04.02.17_M2 androidboot.ci
INFOd=VODAP110 androidboot.batt_poweron=good_battery androidboot
INFO.carrier=VODA-Swisscom-DE androidboot.mid=PD9810000 androidb
INFOoot.keycaps=qwerty androidboot.mode=recovery androidboot.ser
INFOialno=HT0B8RX02111 androidboot.bootloader=0.85.0018 no_conso
INFOle_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOaARM_Partion[6].name=devlog
INFOaARM_Partion[7].name=pdata
INFOpartition number=8
INFOValid partition num=8
INFOjump_to_kernel: machine_id(2844), tags_addr(0x4000100), kern
INFOel_addr(0x4008000)
INFO-------------------hboot boot time:181615 msec
FAILED (status read failed (Too many links))
Voilà, thanks everybody for your help...
hi im a noob and having trouble with my bell dz, any help would be greatly appreciated, its downgraded to 1.34 and i think i have gained root, but still s-on
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\ron>cd :c/platform-tools
The filename, directory name, or volume label syntax is incorrect.
C:\Users\ron>cd c:/platform-tools
c:\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
c:\platform-tools>fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8D085C50
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x25203
INFOTAG:hero panel = 0xF
INFOTAG:engineerid = 0x4
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is BM___001
INFOsetting->cid::BM___001
INFOserial number: HT0ARRV02723
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =461
INFOactive commandline: board_vision.disable_uart2=0 board_visio
INFOn.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
INFOboard_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=true androidboot.baseband=26.03.02.18_M3 androidboo
INFOt.cid=BM___001 androidboot.batt_poweron=good_battery android
INFOboot.carrier=BM androidboot.mid=PC1012000 androidboot.keycap
INFOs=qwerty androidboot.mode=normal androidboot.serialno=HT0ARR
INFOV02723 androidboot.bootloader=0.85.0005 no_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOaARM_Partion[6].name=devlog
INFOaARM_Partion[7].name=pdata
INFOpartition number=8
INFOValid partition num=8
INFOjump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
INFOel_addr(0x4008000)
INFO-------------------hboot boot time:11343 msec
FAILED (status read failed (Too many links))
c:\platform-tools>
any ideas?
http://forum.xda-developers.com/wiki/HTC_Vision
did you follow this?
no i originaly unlocked the boot loader at htcdev then relocked it and followed strawmetals guide. I should have asked for help a while ago, im pretty sure i have messed it right up
is there a way to undo things and start fresh?
You can flash an RUU to return it to complete stock. You can find the RUU's at http://www.shipped-roms.com/index.php?category=android&model=Vision
You'll most probably need a goldcard though
-Nipqer
ok can i flash an earlier rom? or would it be best to go back to gingerbread
?
if you managed to run misc_version properly, you can flash an earlier rom. Otherwise you'll have to go for the gingerbread one (2.42 I think)
-Nipqer
i have tried to flash my stockrom a several times, but i keep getting a signature 12 verify fail, i dont think my gc is right, when i downgraded i flashed the wrong rom RUU_Vision_hTC_Asia_WWE_1.34.707.3_Radio_12.28b.60.140e_26.03.02.18 could this be why? also i think i used a g2 hboot, i am lost as to how to fix these issues
if someone could point me in the right direction it would be greatly appreciated
Hi guys
I got a big problem and im in way over my head so i really hope someone can help me
I tried the search and found many treads to use but non with sucess
The phone is S-ON
About a week i tried to fix my fathers phone because it was on boot-loop
in lack of better knowles i tried til unlock the bootlocker via htvdev, it told me to update the hboot and it instant went on OOW-locked after that..
Tried to update it again but then got a 191 error rom version not supported
Then i tried to Ruu it with a goldcard and a shipped rom ( RUU_Ace_Gingerbread_S_HTC_WWE_2.50.405.2) but i diddent work, showed error 140 wrong bootloader version...
I then tried to flash a newer rom ( RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1) which failed on Radio v2 ( PU-fail as i remember) got a error 152 image error wrong ruu and then it got stuck in RUU mode/ black screen with 4 /!\
I tried to fastboot flash diffrent PD98img's but they fail
I also tried to flash a t-mobile branded rom (shipped with that when new) diddent work
Also tried to but .zip on card.. no luck either
Also tried Ace hack thing but dont work as i cant adb push
-------------------
I cant get_indentifier_token (to unlock bootloader)
I cant Adb (as i cant turn on the phone for ativating debugging)
I cant boot in to bootloader or recovery (as the phone is stuck in RUU)
-----------
I can fastboot via cmd
I can Ruu from PC
I have all drivers installed
Goldcard is inserted
Code:
ACE PVT SHIP S-ON RL
HBOOT-2.00.00.27
MICROP-0438
RADIO-26.09.04.11.m2
eMMC-boot
Sep 7 2011,19:06:24
RUU (highlighted)
Code:
E:\root>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.00.0027
INFOversion-baseband: 26.09.04.11_M2
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 2.52.0.0
INFOserialno: HT11BRX09090
INFOimei: -removed-
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9810000
INFOcidnum: T-MOB101
INFObattery-status: good
INFObattery-voltage: 4204mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: 743ca94a
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.016s
Code:
E:\root>fastboot reboot oem boot
... INFOsetup_tag addr=0xC0000100 cmdline add=0x8D
08C9AC
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26503
INFOTAG:hero panel = 0x1
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is T-MOB101
INFOsetting->cid::T-MOB101
INFOserial number: HT11BRX09090
INFOcommandline from head: no_console_suspend=1 wire.search_coun
INFOt=5
INFOcommand line length =510
INFOactive commandline: board_spade.disable_uart2=0 board_spade.
INFOusb_h2w_sw=0 board_spade.disable_sdcard=0 diag.enabled=0 boa
INFOrd_spade.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=true androidboot.baseband=26.09.04.11_M2 androidboot.ci
INFOd=T-MOB101 androidboot.batt_poweron=good_battery androidboot
INFO.carrier=TMD androidboot.mid=PD9810000 androidboot.keycaps=q
INFOwertz androidboot.mode=normal androidboot.serialno=HT11BRX09
INFO090 androidboot.bootloader=2.00.0027 zygote_oneshot=off kmem
INFOleak=off no_console_suspend=1 wire.search_count=5
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=local
INFOaARM_Partion[5].name=cache
INFOaARM_Partion[6].name=userdata
INFOaARM_Partion[7].name=devlog
INFOaARM_Partion[8].name=pdata
INFOaARM_Partion[9].name=lib
INFOpartition number=10
INFOValid partition num=10
INFOjump_to_kernel: machine_id(2844), tags_addr(0x4000100), kern
INFOel_addr(0x4008000)
INFO-------------------hboot boot time:597262 msec
FAILED (status read failed (Unknown error))
finished. total time: 21.031s
Dont hesitate to ask me for further info if you need it..
ANY help will be greatly apriciated as im stuck right now..
Any one?? i keep reading that Radio fail = Bricked, but also that is you can reach th e phone via fastboot you can still save it?
Is my dads phone dead?
bump
braarup said:
bump
Click to expand...
Click to collapse
First, stop trying anything at arm length or will definitely brick the phone. You need to have a locked bootloader to flash a RUU. If you are still S-ON then you will need to use the official RUU and no other one.
Once you have the RUU, rename it PD98IMG.zip, put it in the root of the sdcard and then boot in hboot...let it parse the file and when prompted to update just choose yes.
If the phone is S-ON not rooted and S-OFF there's no reason for it to go on a bootloop. Maybe some hardware issue.
I have Desire HD and microsd slot is not working and also low signal when SIM card inserted. I've followed some guides here but some have dead links.
Whenever I try to flash it with RUU it hangs on 'signature checking......'
The phone boots up to Android version 2.3.5 HTC sense 3.0 software 3.12.405.1 kernel 2.6.35.10-g931a37e htc [email protected] #1 baseband
12.65.60.29U_26.14.04.28_M build 3.12.405.1 CL199157 release-keys
Phone says "SD card blank or has unsupported filesystem" and when I click on this message it says format? and then says ... "SD card was removed before being unmounted". The microsd card works fine in other phones.
I've tried htcdev to unlock and I have the Unlock_code.bin for my phone, I have flashed it to the phone but the phone stays on the HTC grey logo screen and doesn't ask if I want to unlock?
Press Volume Down
*****LOCKED (OOW) ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011, 14:28:19
On this screen it seems to freeze? as I can't choose fastboot, recovery, factory reset I have to pull the battery out.
fastboot oem boot
... INFOsetup_tag addr=0xC0000100 cmdline add=0x8D
0985F8
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26503
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__001
INFOsetting->cid::HTC__001
INFOserial number: HT0B6RX10792
INFOcommandline from head: no_console_suspend=1 wire.search_coun
INFOt=5
INFOcommand line length =513
INFOactive commandline: board_spade.disable_uart2=0 board_spade.
INFOusb_h2w_sw=0 board_spade.disable_sdcard=0 diag.enabled=0 boa
INFOrd_spade.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=true androidboot.baseband=26.14.04.28_M androidboot.cid
INFO=HTC__001 androidboot.batt_poweron=good_battery androidboot.
INFOcarrier=HTC-WWE androidboot.mid=PD9810000 androidboot.keycap
INFOs=qwerty androidboot.mode=normal androidboot.serialno=HT0B6R
INFOX10692 androidboot.bootloader=2.00.0029 zygote_oneshot=off k
INFOmemleak=off no_console_suspend=1 wire.search_count=5
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=local
INFOaARM_Partion[5].name=cache
INFOaARM_Partion[6].name=userdata
INFOaARM_Partion[7].name=devlog
INFOaARM_Partion[8].name=pdata
INFOaARM_Partion[9].name=lib
INFOpartition number=10
INFOValid partition num=10
INFOjump_to_kernel: machine_id(2844), tags_addr(0x4000100), kern
INFOel_addr(0x4008000)
INFO-------------------hboot boot time:14689 msec
FAILED (status read failed (Too many links))
finished. total time: 9.079s
As the title suggests, Whenever i turn on the camera, it shows black screen with UI Grid/Camera settings/icons etc and then all of the sudden it crashes and go back to the Android home screen. It doesn't matter what app i use to launch the camera and in what orientation i do it, the results are same.
Here are my phones detail
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
Here are the logs that i captured using adb logcat while launching camera from whatsapp
Code:
adb logcat
to see whats going on, I noticed that I am getting following exception when whatsapp tries to open the camera
Paste Bin Link for convenience
Code:
I/ActivityManager( 1001): START u0 {cmp=com.whatsapp/.camera.CameraActivity (has extras)} from uid 10188 on display 0
D/Venom ( 1001): Force new Task enabled: false
D/PMS ( 1001): acquireWL(21afa246): PARTIAL_WAKE_LOCK ActivityManager-Launch 0x1 1001 1000 null
D/HtcSystemUPManager( 1001): HtcSystemUPolicy [canLog (default)] category: launch, enable: true
I/SwipeUpService(15616): SwipeUpService started but not active, your device have already Google New gesture
E/CameraParams( 513): //CC140618++ m_p = 0xb93eba6c android::CameraParameters_EXT::CameraParameters_EXT(android::CameraParameters*), [578]:
D/FlashlightController( 1155): onCameraUnavailable(0)
D/FlashlightController( 1155): dispatchAvailabilityChanged(false)
E/QCamera2HWI( 513): [TimeHelper] void qcamera::QCamera2HardwareInterface::TimeHelper::reset():7042, open device /dev/time_helper error!
E/CameraParams( 513): //CC140618++ m_p = 0xb46bd904 android::CameraParameters_EXT::CameraParameters_EXT(android::CameraParameters*), [578]:
E/CameraParams( 513): //CC140618++ m_p = 0xb93f7f14 android::CameraParameters_EXT::CameraParameters_EXT(android::CameraParameters*), [578]:
W/SensorService( 1001): Following SensorService logs are not warning, just make sure they are printed
W/SensorService( 1001): enable: get sensor name = Accelerometer Sensor
W/SensorService( 1001): pid=513, uid=1013
W/SensorService( 1001): Active sensors: size = 3
W/SensorService( 1001): Accelerometer Sensor (handle=0x00000000, connections=3)
W/SensorService( 1001): CM36282 Light sensor (handle=0x00000003, connections=1)
W/SensorService( 1001): CM36282 Proximity sensor (handle=0x00000004, connections=1)
W/QCamera2HWI( 513): void qcamera::ionDump(): open failed
E/QCamera2HWI( 513): Load library end
E/QCamera2HWI( 513): [KPI Perf] int qcamera::QCamera2HardwareInterface::openCamera(hw_device_t**): E PROFILE_OPEN_CAMERA CameraID:0
E/mm-camera-intf( 513): mm_camera_open: dev name = /dev/video1, cam_idx = 1
E/mm-camera-sensor( 530): module_sensor_start_session:558 session 1
E/mm-camera( 530): isp_tintless_open: E: b6dd8a61
E/hdr ( 530): Session id 0x1 started
E/mm-camera-img( 530): module_imglib_msg_thread:75] abort 0
E/mm-camera( 530): isp_tintless_get_version: lib returned version 3.61 err=0
E/mm-camera( 530): is_module_start_session: Enter
E/mm-camera( 530): is_module_start_session: Exit successful
E/mm-camera( 530): is_module_get_port: Exit successful
E/mm-camera( 530): c2d_module_start_session:227, info: starting session 1
E/mm-camera( 530): c2d_thread_func:41: c2d_thread entering the polling loop...
E/mm-camera( 530): c2d_module_start_session:274, info: c2d_thread created.
E/mm-camera( 530): pp_buf_mgr_open_subdev: MSM_CAMERA_SUBDEV_BUF_MNGR opened =27
E/mm-camera( 530): c2d_module_start_session:296, info: session 1 started.
E/mm-camera-img( 530): module_imglib_msg_thread:75] abort 0
I/ActivityManager( 1001): Recipient 15297
D/Process ( 1001): killProcessQuiet, pid=15297
D/Process ( 1001): com.android.server.am.ActivityManagerService.appDiedLocked:-1 com.android.server.am.ActivityManagerService$AppDeathRecipient.binderDied:-1 android.os.BinderProxy.sendDeathNotice:-1
I/ActivityManager( 1001): Process com.handmark.expressweather (pid 15297) has died
D/HtcUPManager( 1155): HtcUPServiceProxy onTrimMemory() has been called. Memory Level: 10
D/HtcUPManager( 1155): HtcUPServiceProxy onTrimMemory() has been called. Memory Level: 10
I/RecentsTaskLoader( 1155): trim:RUNNING_LOW/MODERATE
E/mm-camera-sensor( 530): actuator_process:1786 ACTUATOR_SET_SENSOR_INFO : ov4688
E/mm-camera-sensor( 530): af_actuator_set_af_value:1416 (), act_name ti201_act
E/mm-camera-sensor( 530): af_actuator_set_af_value:1416 (), act_name rumbas_act
E/mm-camera-sensor( 530): af_actuator_set_af_value:1416 (), act_name lc898212_act
E/mm-camera-sensor( 530): af_actuator_set_af_value:1416 (), act_name ti201_act
E/mm-camera-sensor( 530): af_actuator_set_af_value:1416 (), act_name ti201_act
E/mm-camera-sensor( 530): af_actuator_set_af_value:1416 (), act_name lc898212_act
E/mm-camera-sensor( 530): af_actuator_set_af_value:1416 (), act_name ti201_act
E/mm-camera-sensor( 530): af_actuator_set_af_value:1416 (), act_name ti201_act
E/mm-camera-sensor( 530): af_actuator_set_OTP_info:219 VCM Module vendor = 0
E/mm-camera-sensor( 530):
E/mm-camera-sensor( 530): af_actuator_set_OTP_info:302 OTP_data[2] 0 OTP_data[3] 0 OTP_data[4] 0 OTP_data[5] 0
E/mm-camera-sensor( 530):
E/mm-camera-sensor( 530): af_actuator_set_OTP_info:303 VCM_Start = 0, MODULE_ID_AB = 0x0
E/mm-camera-sensor( 530):
E/mm-camera-sensor( 530): af_actuator_set_OTP_info:304 VCM_Infinity = 0
E/mm-camera-sensor( 530):
E/mm-camera-sensor( 530): af_actuator_set_OTP_info:305 VCM_Macro = 0
E/mm-camera-sensor( 530):
E/mm-camera-sensor( 530): af_actuator_set_OTP_info:307 ori_VCM_Infinity = (0x0)0
E/mm-camera-sensor( 530):
E/mm-camera-sensor( 530): af_actuator_check_vcm_property:720 af_actuator_check_vcm_property: Not enable VCM sorting
E/mm-camera-sensor( 530):
E/mm-camera-sensor( 530): sensor_thread_func:101 sensor_thread_func: readfd:26 writefd:28
E/hdr ( 530): Sensor 2688x1520 = 4085760 > 2M (1928*1088),HDR supported 1
E/mm-camera-intf( 513): mm_camera_open: opened, break out while loop
E/mm-jpeg-intf( 513): mm_jpeg_init:1651] Launch jobmgr thread rc 0
E/mm-jpeg-intf( 513): Max picture size 2688 x 1520, WorkBufSize = 6193152
E/qomx_image_core( 513): OMX_Init:94] Complete 2
E/QCameraParameters( 513): int qcamera::QCameraParameters::initDefaultParameters() supportd_feature_mask 0x77f
E/QCameraParameters( 513): int qcamera::QCameraParameters::setPreviewFpsRange(int, int): Setting preview fps range 10200,40490
E/CameraParams( 513): //CC140618++ m_p = 0xb46bd6a0 android::CameraParameters_EXT::CameraParameters_EXT(android::CameraParameters*), [578]:
E/mm-camera( 530): mct_pipeline_process_set:command=800000e
E/camera_calibration( 513): [Calibration Record] Sensor_Check_LSC_Calibration_Result: check fuseid fail
E/camera_calibration( 513): [Calibration Record] Sensor_Check_AWB_Calibration_Result: check fuseid fail
E/camera_calibration( 513): [AEC Calibration Record] Sensor_Check_AEC_Calibration_Result: check fuseid fail
E/camera_calibration( 513): [Calibration Record][dual] Sensor_Check_FLASH_Calibration_Result: check fuseid fail
E/camera_calibration( 513): [Calibration Record] Sensor_Check_FLASH_Calibration_Result: check sum is not valid
E/camera_calibration( 513): [Calibration Record] Sensor_Check_FLASH_Calibration_Result: check fuseid fail
E/camera_calibration( 513): [Calibration Record] Sensor_Check_FLASH_Calibration_Result: calibration fail
E/camera_calibration( 513): [Calibration Record] Sensor_Check_DUAL_Calibration_Result: check fuseid fail
E/Thermal-Lib( 513): Thermal-Lib-Client: thermal_client_register_callback: Client Registration failed
E/Thermal-Lib( 513): Thermal-Lib-Client: thermal_client_register_callback: Client Registration failed
I have factory restored number of times & and I even upgraded from Android Kitkat 4.4.3 to Android Lollipop (VenomROM) with corresponding firmware. Please note that the camera issue started before i upgraded. So the issue (all of the sudden) started to happen when I was using RevolutionHD Rom on Android 4.4.3
bump ...
Have you tried to revert to stock with RUU ?
Not stock backup but RUU and see whether you have same problem.
Use the EU RUU exe
ckpv5 said:
Have you tried to revert to stock with RUU ?
Not stock backup but RUU and see whether you have same problem.
Use the EU RUU exe
Click to expand...
Click to collapse
I have few quesitons. I am currently using the phone on Fido (Canada), would going back to Stock RUU lock my phone to the carrier ? (I guess not but i just want to make sure).
Secondly, There are lots of threads and lots of informaiton and i always get confuse what would be the stock ROM that i will be using. Could you suggest (based on my fastboot getvar command) which stock ROM to install ?
Third, would I have to update/downgrade firmware as well ?
..alee said:
I have few quesitons. I am currently using the phone on Fido (Canada), would going back to Stock RUU lock my phone to the carrier ? (I guess not but i just want to make sure).
Secondly, There are lots of threads and lots of informaiton and i always get confuse what would be the stock ROM that i will be using. Could you suggest (based on my fastboot getvar command) which stock ROM to install ?
Third, would I have to update/downgrade firmware as well ?
Click to expand...
Click to collapse
You have a S-Off device, so you don't need to worry about lock to your carrier as you don't have to (for now ... you need to go back to your carrier ROM for warranty purpose when it is needed)
I suggested to use EU RUU exe because I see your fastboot getvar info is good for that.
Again... as you have a S-Off device you can upgrade/downgrade firmware as and when you need to that.
For now what you need is :
Download RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10 here : http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1 - use the first link for the exe
This will update your device to the latest stock lollipop 4.16.401.10
1. put your device in bootloader/fastboot mode and connect to PC
2. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed.
Once completed, don't install anything yet ... check the Camera .. see whether there is still problem.
thanks, let me try it out.
ckpv5 said:
You have a S-Off device, so you don't need to worry about lock to your carrier as you don't have to (for now ... you need to go back to your carrier ROM for warranty purpose when it is needed)
I suggested to use EU RUU exe because I see your fastboot getvar info is good for that.
Again... as you have a S-Off device you can upgrade/downgrade firmware as and when you need to that.
For now what you need is :
Download RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10 here : http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1 - use the first link for the exe
This will update your device to the latest stock lollipop 4.16.401.10
1. put your device in bootloader/fastboot mode and connect to PC
2. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed.
Once completed, don't install anything yet ... check the Camera .. see whether there is still problem.
Click to expand...
Click to collapse
it didn't fix the issue ...
..alee said:
it didn't fix the issue ...
Click to expand...
Click to collapse
If RUU didn't fix the issue, and it didn't seem to be related to any other software changes at the time (based on your description), it might be a hardware issue.
redpoint73 said:
If RUU didn't fix the issue, and it didn't seem to be related to any other software changes at the time (based on your description), it might be a hardware issue.
Click to expand...
Click to collapse
Given that I am s-off, can i go back to the original state of my device so that i can contact HTC to fix the device ? I am not sure if i am under warranty or not.
..alee said:
Given that I am s-off, can i go back to the original state of my device so that i can contact HTC to fix the device ? I am not sure if i am under warranty or not.
Click to expand...
Click to collapse
That would probably be your best bet.
Keep in mind, if you unlocked the bootloader via HTCDev.com, they have a record of you doing so; regardless of whether you return the phone to stock.
redpoint73 said:
That would probably be your best bet.
Keep in mind, if you unlocked the bootloader via HTCDev.com, they have a record of you doing so; regardless of whether you return the phone to stock.
Click to expand...
Click to collapse
damn it HTC ... gotta call them and see what they say.
Thanks a lot guys.
..alee said:
damn it HTC ... gotta call them and see what they say.
Click to expand...
Click to collapse
Yeah, that's probably the best play. Reports vary widely on whether the bootloader unlock via HTCDev.com voids the warranty or not. Have your poker face on, cross your fingers and hope for the best!
..alee said:
damn it HTC ... gotta call them and see what they say.
Thanks a lot guys.
Click to expand...
Click to collapse
In my country based on my experience with many HTC devices, as long as the bootloader show "LOCKED" they will accept to repair on warranty.
You have a s-Off device, you set the bootloader "LOCKED" instead of "RELOCKED"
Given that my phone is from UK and I am using it in Canada. I don't think that I will be sending it back to HTC to get it fix by spending $200 on courier. I might much rather go to buy a new device. Now i am struggling which one to buy ...
Anyway, Thanks a lot guys I really appreciate your time and replies.