Random Reboots using the ViperXL ROM

Search This thread

Mr Davo

Senior Member
May 6, 2010
217
20
Melbourne
Hi Everyone,

I have just installed the ViperXL ROM and I have noticed random reboots of the phone. The period between these reboots doesn't appear to be consistent, and furthermore it doesn't matter whether the phone is plugged in or not. So far a reboot hasn't occurred in the middle of me using the phone; however this may simply be because I have not been using it a lot.

If anybody has any suggestions on what may cause this behaviour they will be greatly appreciated.

Kind Regards,

Davo
 

exad

Senior Member
Jan 26, 2010
3,459
1,518
Montreal
Hi Everyone,

I have just installed the ViperXL ROM and I have noticed random reboots of the phone. The period between these reboots doesn't appear to be consistent, and furthermore it doesn't matter whether the phone is plugged in or not. So far a reboot hasn't occurred in the middle of me using the phone; however this may simply be because I have not been using it a lot.

If anybody has any suggestions on what may cause this behaviour they will be greatly appreciated.

Kind Regards,

Davo

What firmware/hboot version you using?
 

Mr Davo

Senior Member
May 6, 2010
217
20
Melbourne
Thank you. I am having trouble doing the 'S-Off', have tried the 'Facepalm' method, and posted to that thread concerning the issues that I am facing. What method did you use to 'S-Off'? Furthermore did it give you any grief?
 

exad

Senior Member
Jan 26, 2010
3,459
1,518
Montreal

Mr Davo

Senior Member
May 6, 2010
217
20
Melbourne
Thanks exad (for your continued interest / help) -

HTML:
C:\Program Files\Android SDK\sdk\platform-tools>fastboot flash zip PJ8312000-One
X.zip
sending 'zip' (36064 KB)...
OKAY [  2.786s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 4.307s

C:\Program Files\Android SDK\sdk\platform-tools>fastboot oem boot
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02F50C4
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2FD09
(bootloader) TAG:hero panel = 0x4940047
(bootloader) TAG:engineerid = 0x2
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is not super CID
(bootloader) CID is TELST001
(bootloader) setting->cid::TELST001
(bootloader) serial number: HT2B2W301400
(bootloader) command line length =740
(bootloader) active commandline: poweron_status=1 reset_status=0 board_el
(bootloader) ite.disable_uart3=0 diag.enabled=0 board_elite.debug_uart=0
(bootloader) userdata_sel=0 androidboot.emmc=true androidboot.pagesize=20
(bootloader) 48 skuid=0 ddt=20 ats=0  androidboot.lb=1 td.sf=1 td.td=1 td
(bootloader) .ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.ofs=69
(bootloader) 4 imc_online_log=0  androidboot.efuse_info=NNSL androidboot.
(bootloader) baseband=0.23a.32.09.29 androidboot.cid=TELST001 androidboot
(bootloader) .devicerev=3 androidboot.batt_poweron=good_battery androidbo
(bootloader) ot.carrier=Telstra a
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=fat
(bootloader) aARM_Partion[A].name=extra
(bootloader) aARM_Partion[B].name=reserve
(bootloader) aARM_Partion[C].name=radio
(bootloader) aARM_Partion[D].name=adsp
(bootloader) aARM_Partion[E].name=dsps
(bootloader) aARM_Partion[F].name=wcnss
(bootloader) aARM_Partion[10].name=radio_config
(bootloader) aARM_Partion[11].name=modem_st1
(bootloader) aARM_Partion[12].name=modem_st2
(bootloader) aARM_Partion[13].name=reserve
(bootloader) partition number=20
(bootloader) Valid partition num=20
(bootloader) setting_get_bootmode() = 9
(bootloader) ram size = 0
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 90005000 (phy 90005000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_LOG_OPERATOR ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
(bootloader) Start Verify: 3
(bootloader) jump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
(bootloader) nel_addr(0x80408000)
(bootloader) -------------------hboot boot time:27572 msec
FAILED (status read failed (Too many links))
finished. total time: 6.170s

C:\Program Files\Android SDK\sdk\platform-tools>
 

exad

Senior Member
Jan 26, 2010
3,459
1,518
Montreal
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)

this part should be remote: 92 and not 99

press and hold power until it hard reboots (do not software reboot). Then try again
 

exad

Senior Member
Jan 26, 2010
3,459
1,518
Montreal
I am still receiving the 'remote: 99 unkown fail' message. Do you have any other ideas?

no. keep pressing and holding power until it shuts off and then try again. ive seen it take some people several tries.

come to think of it. It may be the software version of viper rom. Try flashing an older version or any sense 4 rom