Develop Bugs

From AT&T to DEV via s-off. stuck on any RUU. sensor_hub.img error

Hello guys.
I've got a problem here. I have an AT&T One M9 unlocked phone.
Yesterday i installed twrp ,than root, than got s-off. That went smooth.
Changed mid
fastboot oem writemid 0PJA11000
than cid
fastboot oem writecid BS_US001 or fastboot oem writecid 11111111 (none helped, mean, it changed but still an error in update)
i was going to install dev edition RUU, so after that upgrade to MM from 5.1.
any RUU i've tried got stuck after flashing radio and 87% and that error bla bla(nothing helpful, no error code or something)
Okay i've got zip RUU and tried to flash via
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip
or from latest android sdk fastboot.
Everytime i have the same error
....
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) ERR Flashing [sensor_hub.img] failed with status [255]
(bootloader) ERR Faild to update firmware [sensor_hub.img]
(bootloader) [email protected]
and after that only reboot helps.
any ideas? my guess that sensor_hub partition damaged somehow or maybe screen was changed on some non original?

From what i gather its a corrupt partition and only htc can fix it.
Beamed in by telepathy.

shivadow said:
From what i gather its a corrupt partition and only htc can fix it.
Beamed in by telepathy.
Click to expand...
Click to collapse
hmm and is there any way to skip flashing that sensor_hub.img?
or maybe get that partition from other phone?
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 3572XXXXXXXXXX
(bootloader) version-main: 1.32.617.6
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: 11111111

shoo said:
hmm and is there any way to skip flashing that sensor_hub.img?
or maybe get that partition from other phone?
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 3572XXXXXXXXXX
(bootloader) version-main: 1.32.617.6
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: 11111111
Click to expand...
Click to collapse
You can try flashing one of the firmware packages found in this thread: http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Use the no wipe version as they won't wipe your system and data partitions (although I assume you have no OS since RUU is failing.
Even if sensor_hub fails to flash, you should still be able to install a recovery flashable rom (as in any of the roms in the development section).
You could also try this:
1) rename the RUU.zip to 0PJAIMG.zip
2) copy the RUU to the root of your EXTERNAL sdcard
3) reboot into download mode where you will be prompted to press volume up to flash or volume down to cancel - press volume up and let the process run
This method basically just eliminates the computer and the USB cable as the source of the issue. Although if the RUU always fails at the same spot, I suspect the computer and cable are not the issues.

Unbrick HTC 10 on base 1.80.709.1 help

hi friends
i have a problem whit an HTC 10
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) imei: 354261XXXXXXXX
(bootloader) version-main: 1.80.709.1
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__621
the problem is that is bootloping on logo.
i had unbrick many HTC phones whit this problem only by flashing the stuck RUU, the problem in this case is that the base 1.80.709.1 has no RUU...an cant unlock bootloader becasue OEM unlock was OFF at the momento of the damage: So also i cant flash a custom RUU or TWRP
Thing i have Triied:
-HArd reset (wipe data/factory reset)...didnt work
-Modified Firwares (edited android-info.txt and info.bin to avoid security)...didnt work
-Flashed RUU 1.80.617.1 but (obviusly) didnt work because it cant be downgraded on S-on state
- Some other similar stuff
-Flashed the OTA alone whit the 1.80.709.1...dindt work (it dont have system partition) only the OTA
hipotetic solution: The fix here will be to find the 1.80.709.1 RUU ...hope someone could find it please, or have another idea for the soltion i will apreciate it to much.
thanks :good:

Problem updating M9 from MM to Nougat please give me a hand

Hello, have an M9 ATT with S-Off and Unlocked bootloader firsts was in ATT 5.0 stock, after downloaded an unlocked 6.0 RUU from htc support it installs well and no issues, after install TWRP and LeeDroid rom, everyting fine. Now restored 6.0 RUU no issues but try to install 7.0 unlocked RUU but get IMAGE error. I want to upgrade to Nougat.
The files that downloaded are this:
RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.16 (WORKS GOOD)
RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.23.617.1 Cant install
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 357227061068563
(bootloader) version-main: 3.35.617.16
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: 11111111
Thanks in advance

Supercid is no longer valid and you need a stock phone to update to nougat.
Beamed in by telepathy.

shivadow said:
Supercid is no longer valid and you need a stock phone to update to nougat.
Beamed in by telepathy.
Click to expand...
Click to collapse
Really? Can i get back to supercid again in nougat?

Already changed CID to BS_US001 but still getting error. RUU says ERROR [132]: Signature error
GEt correct update utility and try again.
What am i doing wrong? Becuase is the same model i choose to download the 5.0 RUU
Edit: Do I have to flash 4.23. 617.1 firmware to match RUU version?

Htc One M9 with relocked bootloader and S-ON

Hi.
Can I fix this phone with bootloader relocked and S-On? Phone is in a bootloop state and will only enter in download mode. Here's some info from the command "fastboot getvar all"
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226065********
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
I've tried to flash with sdcard this updated rom but ends with ruzip flash error 12.
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.28.401.3_Radio_01.01_U114401011_117.00.61117G_2_F_release_498151_signed_2

The error is 12 - the readme thread says the following:
12 SIGNATURE FAIL: The phone expects an HTC signature and can't find one or found a wrong one. This error occurs if you try to flash a RUU that uses a different encryption key than the one your phone is using (e.g. firmware 3.x and older vs. 4.x).
Click to expand...
Click to collapse
I think there was something about encryption keys being changed from 3 to 4 firmware. Please try flashing the 3.35.401.12 RUU from the readme thread, not 4.28.401.13

S-OFF SCID-11111111 SKU-651 - CDMA (?) Works in the UK back to stock question

I have an M9 which is S-OFF and SCID-11111111 with a locked bootloader but rooted. Current firmware version is 3.41.651.4 which suggests the SKU is 651 which is a CDMA variant. However, the phone settings do seem to provide options for both GSM and CDMA, and it works fine in the UK. I'd like to go back to stock using a Nougat upgrade RUU (it's currently on Marshmallow).
Soooo, my question is, if I change the CID to SPCS_001 (the MID is already the correct one for this SKU 0PJA20000) and flash an RUU for this SKU will this result in an upgraded stock phone which still works in the UK?
Here's my getvar and download mode info:
C:\adb2>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxx
(bootloader) version-main: 3.41.651.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: 11111111
all:
finished. total time: 0.029s
****LOCKED****
htc_himawhl PVT S-OFF
CID-11111111
LK-1.0.0.0000
RADIO-3.00.C1144084060114
OpenDSP-15.6.1.00522.8994_1026
OS-3.41.651.4
Feb 3 2016, 13:49:48(695981)

I went ahead with changing the CID as above and installing first the stock marshmallow RUU then upgraded to the latest nougat RUU via OTA. All works except that it is geared for a Sprint M9 and doesn't seem to properly register the 4g data signal. I'm just wondering if I could change the CID to HTC__001 and load the latest European RUU? I used the SD method and it worked fine. I've read different things, suggesting that with S-OFF it's possible to load any RUU provided the CID & MID are correct for the RUU. I've also read that you have to stay with the same SKU, so I'm not sure. Would this be possible?