Develop Bugs

Return to Stock

hi everyone
Been searching/ downloading and flashing but wanted to know if there is a way to confirm that i have in fact returned to Stock.
I am on EE (Orange) UK, unlocked bootloader, S-ON and custom recovery.
I wanted to return to pure stock and wait for the official OTA to 1.4x
I flashed correct RUU for my MID/ CID that got me back to 1.32.61.15
I then flashed the specific recovery.img for 1.32.61.15
it looks like i am back to stock but is there anyway of knowing for sure?
Fastboot getvar all returns the following (imei removed)
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: ********
(bootloader) version-main: 1.32.61.15
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: ORANG001
thanks -

If you used a RUU then you are back to stock
Sent from my HTC One M9 using Tapatalk

cid: BM___001 / S-ON / relocked / Looking for RUU 3.38.666.2

Hey guys,
stuck with relocked state,
S-ON.
can't boot to recovery.
if i flash the unlock bin, stays in relock.
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.38.666.2
(bootloader) boot-mode: download
(bootloader) version-baseband:
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001 (Bell Canada)
guess i have to wait for a RUU/firmware.zip with version 3.38.666.2 and above, correct ?
thanks.

guess i generated a new token which in turn rendered my unlock bin void.
just had to re-do the token and generate a new bin to unlock again.
now can boot to rom and s-off then fix with RUU/twrp backup available on the forum.
close thread.

Hi!
I have the same phone as you but don't have an OS anymore and can't find a recovery image for it.
Could you help?
Thanks!

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.

HTC One M9 No TWRP, No OS, No Recovery Mode

Hey guys I really need your help!
Just got this HTC One M9 that was previously rooted with the "Viper" ROM. As the person gave it to me he wiped it clean leaving only "TWRP" on there. Anyways somewhere along the line I accidentally wipe the whole phone clean and now there is no TWRP... Selecting recovery mode comes up with "Failed to boot to recovery mode". And now my computer won't even recognize it as a device. :crying: Guess I got what I paid for, $200.
Can someone please help urgently? Btw, I'm from Australia.
Cheers.

Did you try to turn it off, hold Vol- when powering up and see if it'll boot to download mode? If this works you can easily flash TWRP again to start flashing a custom ROM from scratch, or instead flash an appropriate RUU to return to full stock - if available for you combination of CID/MID.
For further help, if you can get to download mode a fastboot getvar all output would be if help to further assist you. Post it - if possible - without IMEI and Serial No.
Sent from my HTC 10 using XDA Labs

I got the same damn problem..
c:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(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__002
all:

Demyx11 said:
I got the same damn problem..
c:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(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__002
all:
Click to expand...
Click to collapse
I'd advice to download the RUU belonging to your above named main version number, rename it to 0PJAIMG.zip, place it on an external (FAT32 if less than 32GB, extFAT if lager) formatted extSD.
Insert this SD into your phone and boot to download. You should then see a yellow text on the bottom stating what to do to start flashing the RUU and follow it to proceed.
This will get you back to full stock, to be able to start from scratch with whatever you'll do next.
Sent from my HTC 10 using XDA Labs

How to make One M9 OTA-able again?

I previously rooted my carrier ONE M9, changed the CID and installed the regular ROM.
Now I don't want root anymore and be able to install OTAs. I tried flashing the RUU and installing a backup. Both approached didn't work, and the device still says it's modified and can't install OTAs. The recovery shows a red icon. How can I allow my device to be able to receive OTAs again?
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: *******************
(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: 11111111
all:
finished. total time: 0.010s

Taken from the ReadMe thread:
Flippy498 said:
Be aware that there have been several reports that it's not possible to receive/install OTAs while using the SuperCID (11111111). So make sure you use a CID that corresponds to the OTA you want to install.
Click to expand...
Click to collapse
Please use the search function before you create a new thread.