Develop Bugs

[Q] TMOUS M8 accepted GPE hboot 3.18 - Am I busted?

It's been a long and wild ride, but I think my device is toasted.. sorta.
I unlocked via HTCDev, installed TWRP, rooted. All went well.
Wanted to test GPE ROM. Downloaded and installed 4.4.3.
It had an OTA. Flashed stock recovery to apply it. BAD MOVE!
Ever since, my white hboot is now black, says version 3.18. This is the GPE hboot.
Trying to manually write a new one with dd fails obviously, read only.
RUU fails, saying error 159 (Wrong RUU for this device. It isnt?)
RUU flashing hboot, "unknown error 99" - assuming because S-On.
Firewater s-off FAILED before this happened, because my device just wasn't compatible with it.
Now running the GPE hboot I tried it again, and it just force closes and kicks me back to a terminal after typing in "Yes"
Only AOSP based ROMs are booting now.
TWRP (Multiple versions) as well as PhilZ CWM both fail on most other roms with "set_perm: some changes failed"
And then kick me to a 2-3 bootloop back into recovery.
What are my options? Thanks guys.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SUREWHYNOT
(bootloader) imei: YESSIR
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

xHighAlert said:
It's been a long and wild ride, but I think my device is toasted.. sorta.
I unlocked via HTCDev, installed TWRP, rooted. All went well.
Wanted to test GPE ROM. Downloaded and installed 4.4.3.
It had an OTA. Flashed stock recovery to apply it. BAD MOVE!
Ever since, my white hboot is now black, says version 3.18. This is the GPE hboot.
Trying to manually write a new one with dd fails obviously, read only.
RUU fails, saying error 159 (Wrong RUU for this device. It isnt?)
RUU flashing hboot, "unknown error 99" - assuming because S-On.
Firewater s-off FAILED before this happened, because my device just wasn't compatible with it.
Now running the GPE hboot I tried it again, and it just force closes and kicks me back to a terminal after typing in "Yes"
Only AOSP based ROMs are booting now.
TWRP (Multiple versions) as well as PhilZ CWM both fail on most other roms with "set_perm: some changes failed"
And then kick me to a 2-3 bootloop back into recovery.
What are my options? Thanks guys.
Click to expand...
Click to collapse
You cant ruu because your CID is wrong you should supercid by doing ...
"fastboot oem readcid". Make a note of your original CID.
Then do
"fastboot oem writecid 11111111"
Not including parenthesis. Then try the ruu

iRunLinux said:
You cant ruu because your CID is wrong you should supercid by doing ...
"fastboot oem readcid". Make a note of your original CID.
Then do
"fastboot oem writecid 11111111"
Not including parenthesis. Then try the ruu
Click to expand...
Click to collapse
Reminder that I am S-On. All S-Off methods fail for me.
While in RebootRUU:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 1
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 1
(bootloader) [SD_ERR] No sd card inserted!
(bootloader) usb_hw_init
FAILED (status read failed (Too many links))
finished. total time: 0.053s
While in regular fastboot:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.002s]
finished. total time: 0.002s

xHighAlert said:
Reminder that I am S-On. All S-Off methods fail for me.
While in RebootRUU:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 1
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 1
(bootloader) [SD_ERR] No sd card inserted!
(bootloader) usb_hw_init
FAILED (status read failed (Too many links))
finished. total time: 0.053s
While in regular fastboot:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.002s]
finished. total time: 0.002s
Click to expand...
Click to collapse
Personally i would try to s-off u said firewater doesnt work but id just try sunshine s-off it costs money but its worth it.

iRunLinux said:
Personally i would try to s-off u said firewater doesnt work but id just try sunshine s-off it costs money but its worth it.
Click to expand...
Click to collapse
Sunshine wants you to get as close to stock as possible.
I'm running the wrong hboot, and can only boot AOSP roms.
But okay I'll give it a spin.

xHighAlert said:
Sunshine wants you to get as close to stock as possible.
I'm running the wrong hboot, and can only boot AOSP roms.
But okay I'll give it a spin.
Click to expand...
Click to collapse
Use the same method in which u flashed the black hboot to flash the stock hboot
---------- Post added at 03:47 AM ---------- Previous post was at 03:42 AM ----------
xHighAlert said:
Sunshine wants you to get as close to stock as possible.
I'm running the wrong hboot, and can only boot AOSP roms.
But okay I'll give it a spin.
Click to expand...
Click to collapse
And if not try flashing gpe stock rooted rom which should boot since your still using that firmware, then try and s-off with sunshine.

I'm in pretty much the same circumstance. Tried going GPE - installed GPE ROM, flashed GPE Recovery to get the 4.4.4 update and now neither GPE nor Sense Roms will install or boot. I had S-Off before, but I think the GPE Recovery put security back on and now I'm back to S-On.
I've tried GPE, Stock Sense, and custom Recoveries and Firmware - nothing is working... I'm stuck running CM11 at the moment.
If only there was an S-Off method that would actually work under CM.

Please help my htc 10 is dead

I Tried to flash but always getting error partition failed. Stucked in boot loop. no recovery. only i can get fastboot. below is my getvar.
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA64xxxxxxx
all:
finished. total time: 0.381s
htc_fastboot finished. total time: 0.738s
Press any key to continue . . .

What's your CID and latest ROM version? And what did you try to flash?

Dont know anything here... I dont know what was the ROM version at the time of root... now no information available... what can I do ...

When I try to flash anything via fastboot it says partion not exist
RUU also not working says battery is less than 30% but actually battery is full...

Does charging led turns green..
@Sneakyghost could help

cutecool said:
Does charging led turns green..
@Sneakyghost could help
Click to expand...
Click to collapse
no it doesnt... the battery icon comes up and then boot loop starts again...

Since you're in Qatar, you're probably on the 401 software. Did you get a software update in the last 2-3 weeks?
If not, download this: https://www.androidfilehost.com/?fid=24686681827312455
Relock your bootloader (fastboot oem lock), and flash this RUU (fastboot flash zip "name of zip").
If you got the recent update, then you're likely on 1.95, and you'll have to wait until there's an RUU, or take it to a service center.
This is as much help as I can give. Good luck.

I wouldn't lock the bootloader until you know your device fully boots.

Stephen said:
I wouldn't lock the bootloader until you know your device fully boots.
Click to expand...
Click to collapse
The 401 RUU zip won't flash on unlocked. This has been documented and I have gone through it myself. Do you have any alternate suggestions?
Why wouldn't you lock without a working system? My understanding is that unlocking via HTCdev would still be possible.

I tried dear but its not locking bootloader
here is the message
C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.257s
C:\Android\com>htc_fastboot oem relock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.249s
C:\Android\com>

abidpioneer said:
I Tried to flash but always getting error partition failed. Stucked in boot loop. no recovery. only i can get fastboot. below is my getvar.
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA64xxxxxxx
all:
finished. total time: 0.381s
htc_fastboot finished. total time: 0.738s
Press any key to continue . . .
Click to expand...
Click to collapse
You need to be in download mode then use the getvar all command. All fastboot commands are done in downlaod mode. How are you trying to flash RUU?

I am unable to use download mode..it says download mode failed in red

abidpioneer said:
I am unable to use download mode..it says download mode failed in red
Click to expand...
Click to collapse
You'll need a service center.

Yes. Service center. I don't think it's a brick since there's still a boot process but at this time I also wouldn't know how to force it to flash stuff, since it seems at least one vital partition is broken. So, call it a semi-brick with currently no way out...
Sorry that I can't offer any help here...

abidpioneer said:
I tried dear but its not locking bootloader
here is the message
C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.257s
C:\Android\com>htc_fastboot oem relock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.249s
C:\Android\com>
Click to expand...
Click to collapse
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Sent from my HTC6545LVW using Tapatalk

I will check dear..thanks

dottat said:
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Click to expand...
Click to collapse
What is hosd.. ? Never heard about it...

I tried but its not working... i went to htc service centre they refused to do the job saying its modified they cannot do the job.. WTH is this at htc service centre...

abidpioneer said:
I tried but its not working... i went to htc service centre they refused to do the job saying its modified they cannot do the job.. WTH is this at htc service centre...
Click to expand...
Click to collapse
What happened? Did it flash successfully? Any errors?
Sent from my HTC6545LVW using Tapatalk

dottat said:
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Interesting facts there, mate. Thought you retired. Obviously I'm much more retired than you, considering I never knew HOSD is directly flashable like aboot...
Good to see you around!
(Besides, is it a true story that you retired? People were telling me that...)

Sprint M9 - Can't boot to recovery, can't flash recovery, S-ON, Unlocked bootloader.

I'll try my best to be as detailed as possible.
I have an HTC One M9 from Sprint. Custom rom on it, I believe it was either Viper Rom or BadBoyz. Running a TWRP PRE 3.0 recovery.
My phone had a pattern lock screen.
I had let the phone sit for about a month with out use, after which I attempted to turn it back on to use it, what I got was a continuous HTC loading screen. So I'm thinking no big deal, all I gotta do is boot into recovery and reflash it.
I boot into recovery, It won't format a number of partitions (I.E. data, system, cache) to allow the flash.
I follow instructions in this video:
with no luck, still won't flash.
So after a few hours of research and attempting different versions of twrp and cwm, it no longer has a bootable recovery. any TWRP 3.0 and up wouldn't run at all, no CWM recovery would run.
My understanding is that those partitions were encrypted and pre 3.0 for twrp can't handle the encryption or some such. I flash a few different versions, going from pre 3.0 to post 3.0, with post 3.0 still not booting but pre 3.0 booting.
THEN
After trying to flash back to a pre 3.0 twrp, it acts as it takes it, but when i go to boot into recovery i get:
"Failed to boot to recovery mode"
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\PropertyCO\twrp.img
target reported max download size of 800000000 bytes
sending 'recovery' (36288 KB)...
OKAY [ 3.063s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.562s]
finished. total time: 5.629s
is what fastboot returns, yet it won't boot to recovery.
So, my next attempt was to run an RUU.
RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.41
I run it, starting with my phone in download mode, RUU sees it just fine, goes to reboot into bootloader. with out assistance when it reboots it just brings up a metalic HTC logo and sits there, so when it reboots i'll hold volume up and down to get it to the boot loader. after some processing from the RUU it gives me the error 170 - USB connection error. Me thinking it's either some drivers messing it up or the cable, i try another laptop, and a series of different cables, no luck there.
I find out that I have to have the bootloader locked to run a RUU, so I attempt to relock the bootloader to see if that fixes the error.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) RELOCK device
OKAY [ 0.286s]
finished. total time: 0.287s
phone reboots, i force it into bootloader cause it doesn't automatically go to it, still says "*** UNLOCKED ***" up at the top.
fastboot getvar all:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) imei: XXXXXXXXXXXXXX
(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: SPCS_001
all:
finished. total time: 0.048s
Thanks in advance!
Edit:
Attempted the ZIP method in this forum and failed too:
https://forum.xda-developers.com/showthread.php?t=1928439

Your nand is corrupt. Dead phone.
Beamed in by telepathy.

HTC M9 Got encrypted... Please i need help

Hello,
I got on my phone a very ni message, Your HTC is encrypted... You have 30 attemps to unlock your phone with a code or device data will be removed.
There was a button "Factory Reset" i have try this button and after a Hour nothing happend. I hold the power button and i can restart or Shutdown my Phone...
I think this is a Malware. I have try to Flash a new RUU but nothing help.. i have try it with "Fastboot oem rebootRUU" but what i only got was a boot loop. I have a custom Recovery on my phone (Team Win Recovery Project)
i have try to Format Data and Factory reset but i only got: Unable to mount Data..and more
I have try it to reboot over TWRP an he says "No OS installed , want to reboot?"
Did anybody know what i can do now?
Here are some Device Data:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226066******
(bootloader) version-main: 3.35.161.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_96.00.51201G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: VODAP102
all:
finished. total time: 0.027s
Click to expand...
Click to collapse
Thanks for Help

Flash the stock firmware via SD card method. You will lose all data. You can flash 3.35.161.x firmwares.. Do not lock bootloader or s-on.

shivadow said:
Flash the stock firmware via SD card method. You will lose all data. You can flash 3.35.161.x firmwares.. Do not lock bootloader or s-on.
Click to expand...
Click to collapse
I have try it before, but i get a Blackscreen and a white HTC logo is flashing. But i will try it again. Thanks for Help

No current TWRP for HTCOne m9 ?!? (Failed to boot to recovery mode)

I have the same problem as described several times in this (HTC M9 Boot mode errors - Failed to boot to recovery mode) thread. Thanks for this, it helped me and I was able to finally get the device working. However, this version of aicp (aicp_himaul_p-14.0-UNOFFICIAL-20181030.zip) is out of date and incompletely developed - as quasi unusable. Because I can only install a twrp-3.0.0-0-hima.img, I cannot install more recent versions.
I'm surprised because I've already been able to flash an HTC One m9 without any problems ?!
How can it be that the m9, which is younger than the m8, cannot use a newer TWRP ?
Is there an alternative to TWRP
Is there a functional way to fix the problem ?
Do you know another way to install a current aicp or lineage ?
Or is there another ROM that I don't know about ?
I can not express it better without guidance ...
I appreciate any help ...

Hello all,
I am already despairing and hope to find help here.
I want to make a firmware update of my htc m9, but can not cope with the variety and the resulting error possibilities.
Here is the info about the device:
Unlocked
htc_himauhl PVT S-on
LK-1.0.0.0000
Radio-01.04_U11440601_71.02.50709G_F
OPenDSP-v29.2.6-00492-M8994_0702
OS-2.10.111.6
Oct. 14 2015, 15:43:14
fastboot getvar all:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226062546916
(bootloader) version-main: 2.10.111.6
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: T-MOB101
all:
Finished. Total time: 0.006s
The device is unlocked and there is a TWRP on it (Vers. twrp-3.0.0-0-hima.img) It is not possible to install a more recent TWRP. Probably because the firmware is too old.
Is there someone here who can kindly support me and help me ?
It would be very important to me not to destroy the device, which is why I no longer dare without help.

Download twrp.img and flash over twrp recovery. Select IMG and flash the new twrpXXX.img

Download twrp.img and flas over twrp recovery. Select IMG and flash the new twrpXXX