Develop Bugs

[Q] Help: impossible to start my HDH

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...

unrevoked failed half way through

A couple of weeks ago I tried to apply the 'one touch' unrevoked tool, and whilst the phone rebooted a couple of times and all seemed to be working well, it eventually froze.
I left it for over an hour with no progress:
Code:
[email protected]:~/Downloads$ ./reflash
unrEVOked recovery reflash tool
git version: 8b5c9e4
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
Now, since I can see the phone with fastboot:
Code:
[email protected]:~/Downloads$ sudo ./fastboot devices
HT09JPL00xxx fastboot
(last 3 digits of serial xxx'd out)
I tried to install an RUU in Windows whose operator+radio match ( RUU_Bravo_Froyo_TMO_UK_2.12.110.4_R_Radio_32.49.00.32U_5.11.05.27_release_157560_signed.exe ) but it fails at the 'RADIO_V2' flash stage.
Code:
Parsing...[downloaded ZIP]
[1] USERDATA - OK
[2] RADIO_CUST - OK
[3] RECOVERY - OK
[4] BOOTLOADER - OK
[5] SPLASH1 - OK
[6] BOOT - OK
[7] RADIO_V2 - Fail-PU
[8] SYSTEM - OK
[9] SPLASH2 - OK
Partition update fail!
Update fail!
When I boot the phone i get the 'htc' logo with exclamation marks in each corner.
I can get into hboot OK with Power + Volume down which shows this:
Code:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010.17:52:18
The installed Android OS is corrupted, so if I run "fastboot oem boot" I see a pink circle with an arrow (same shade as the T-Mobile pink...) and then the phone vibrates briefly 7 times.
Code:
[email protected]:~/Downloads$ sudo ./fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A0D
INFOTAG:hero panel = 0x3
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is T-MOB005
INFOsetting->cid::T-MOB005
INFOserial number: HT09JPL00xxx
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =418
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.11.05.27 androidboot.cid=T
INFO-MOB005 androidboot.carrier=TMUK androidboot.mid=PB9920000 a
INFOndroidboot.keycaps=qwerty androidboot.mode=normal androidboo
INFOt.serialno=HT09JPL00905 androidboot.bootloader=0.93.0001 no_
INFOconsole_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
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw A1E 1000
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:279875 msec
How can I get some kind of working system back again? Am not bothered if it's rooted or not - I'd just like a working phone

try another RUU, try my guide for some other help

Try Bortak's guide - very nice and useful. And BTW this question is answered a couple (dozen) times.
Sent from my customized HTC Desire using TTP

Thanks for the tips,
I had no doubt this problem had come up before; the terminology is just a little overwhelming - I'll work through bortak's guide.
Is it possible to make a goldcard even when there's no usable Android on the phone? (i.e. can't select USB Debugging for 'adb shell')

yup http://jo0ls-dotnet-stuff.blogspot.com/2008/12/read-secure-digital-sd-card-serial.html use this to get the CID of the sd-card (copy down without commas, spaces) then follow this tut http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/ after they get the CID of the sd-card through the phone (the step you're skipping)

Heh, I've been having fun with this to no end result.
All the Micro-SD's I have are SanDisk which came with previous phones (I am using a 1GB for the gold card)
Tried the full manual process for creating the gold card, reversing the bytes manually, pasting the goldcard.img using hex editor, etc. but when I pop that card in the phone and launch the latest WWE RUU
http://www.mirrorcreator.com/files/0FVU0Y7T/RUU_Bravo_Froyo_HTC_WWE_2_29_405_5_Radio_32_49_00_32U_5_11_05_27_release_159811_signed.exe_links
I still get a CID error. The only RUU I've been able to get to start properly is http://www.shipped-roms.com/download.php?category=android&model=Bravo&file=RUU_Bravo_Froyo_TMO_UK_2.12.110.4_R_Radio_32.49.00.32U_5.11.05.27_release_157560_signed.zip
and that one gives the 'Fail-PU' at the RADIO_V2 stage.
So I then found this: http://www.addictivetips.com/mobile/how-to-easily-create-gold-card-for-htc-desire-without-hex-editing/ and I've included screenshots showing the CID + webpage where I downloaded the goldcard.img
I put the 1GB card into my main phone, a Desire S in order that the Gold Card Tool could run 'adb shell' commands
Even after all that, the WWE RUU still failed with a CID error
What am I doing wrong?

don't use the goldcard tool, use the tut I showed you.. it worked for me..

Hullo again - I've returned and have a little more success - the Goldcard creation worked this time - must've messed something up first time round.
Now I'm able to launch the WWE RUU without CID errors.
I am using: RUU_Bravo_Froyo_HTC_WWE_2_29_405_5_Radio_32_49_00_32U_5_11_05_27_release_159811_signed.exe
Unfortunately, the core problem still exists... when the RUU gets to RADIO_V2 step, it still shouts "Fail-PU" in red letters.
I'm beginning to wonder if there's a hardware fault on this handset even tho it worked before I started messing with ROMs; is there anything else I can try?

gdhgdh said:
Hullo again - I've returned and have a little more success - the Goldcard creation worked this time - must've messed something up first time round.
Now I'm able to launch the WWE RUU without CID errors.
I am using: RUU_Bravo_Froyo_HTC_WWE_2_29_405_5_Radio_32_49_00_32U_5_11_05_27_release_159811_signed.exe
Unfortunately, the core problem still exists... when the RUU gets to RADIO_V2 step, it still shouts "Fail-PU" in red letters.
I'm beginning to wonder if there's a hardware fault on this handset even tho it worked before I started messing with ROMs; is there anything else I can try?
Click to expand...
Click to collapse
Yeah your phones bircked, radio fail is unfixable.
Before you send off for warranty use the 2.3.3 RUU.

Oh poo
No chance with warranty - this phone is well over a year old.. ah well I'll drop it in the 'box of fail' at work

gdhgdh said:
Oh poo
No chance with warranty - this phone is well over a year old.. ah well I'll drop it in the 'box of fail' at work
Click to expand...
Click to collapse
hah, sorry dude... hmm try the 2.3.3 RUU a couple of times and hope for a miracle

Hm, I tried this one last time and the WWE ROM successfully installed - all 9 partitions were 'OK' - maybe it's a heat problem since I powered on, used the PB99IMG.zip method on the SD card, and it flashed first time!
So, now HBOOT + FASTBOOT are both working again, but the device is stuck on white screen with green 'htc' logo. Sometimes it will vibrate 7 times.
I've read the 'ADVANCED BOOT PROBLEMS' in section 2 of your guide for S-ON devices.. and it looks like the only hope is to keep flashing the WWE ROM and hope that the phone just magically starts to boot - is that right?

Ha! Continuing in the spirit of 'one last time', I powered it on again, went to get a drink and heard the 'chimes'.. and sure enough the phone was booting OK - I got through the choose Country / wifi setup wizard, saw a moment of the HTC Sense home screen and the phone rebooted again to the htc static logo
I conclude this phone has a bad hardware problem and I won't be wasting any more time on it.
Many thanks for your time + advice

[Q] trouble with dz

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

[Q] Struck in Ruu mode

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.

Camera isn't working

Lately, my phones' camera isn't working. I have tried multiple camera apps, whatsapp, facebook messenger and other apps which has built-in capture picture options. Every app crashes when i open the camera.
The camera shows the black screen with camera options visible on the screen. It stays like this for a while and then crashes, regardless if its front camera or rear camera.
When i did
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
P.S:
I have formatted my device multiple times and the issues persists. I am currently running ViperROM (5 Lollipop) and previously I was on RevolutionHD ROM (4.3)

..alee said:
I have formatted my device multiple times and the issues persists. I am currently running ViperROM (5 Lollipop) and previously I was on RevolutionHD ROM (4.3)
Click to expand...
Click to collapse
What is your hboot and radio baseband numbers?
What version of ARHD? 4.3 isn't a version, of either ARHD or Android (at least for this device). Do you mean Android 4.4.3?

redpoint73 said:
What is your hboot and radio baseband numbers?
What version of ARHD? 4.3 isn't a version, of either ARHD or Android (at least for this device). Do you mean Android 4.4.3?
Click to expand...
Click to collapse
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.052s
The main version is empty even though i tried installing latest TWRP. Perhaps I need to update the firmware but i will do it later.
when i said 4.3 i meant RevolutionHD based on android 4.4.3. Now I am running ViperRom based on Android Lollipop

Your hboot and baseband indicate you are already on LP firmware. I'd avoid any older KK based ROMs, as you will likely have some firmware incompatibility.
Doesn't seem firmware is the issue (as your firmware should support any LP Sense ROM).
When you said you formatted the device many times, what partitions exactly did you wipe?
Also, make sure that the option is disabled for "OK Google" voice command to work on any screen (Settings>Language & keyboard>Google voice typing>"Ok Google" detection - turn off the option "From any screen"). This has been known to cause the HTC camera to crash. Although it seems like your issue is something different, its at least worth a try.

redpoint73 said:
Your hboot and baseband indicate you are already on LP firmware. I'd avoid any older KK based ROMs, as you will likely have some firmware incompatibility.
Doesn't seem firmware is the issue (as your firmware should support any LP Sense ROM).
When you said you formatted the device many times, what partitions exactly did you wipe?
Also, make sure that the option is disabled for "OK Google" voice command to work on any screen (Settings>Language & keyboard>Google voice typing>"Ok Google" detection - turn off the option "From any screen"). This has been known to cause the HTC camera to crash. Although it seems like your issue is something different, its at least worth a try.
Click to expand...
Click to collapse
I started to have this issue when my camera was working perfectly fine. At that time I was at Android 4.4.3 (Revolution HD). After the camera issue, I thought lets do factory reset and see what happenes, It ddn't solve the issue. So while I was messing around with the phone, I upgraded the firmware and Android version in the hope that I will have my camera issue resolved, But it didn/t
I just checked all possible "Ok Google" options (HTC Sense Launcer & Nova Launcer both) but still the problem is there.