Develop Bugs

Last desperate attempt to save My desire HD

I'm a total n00b, just wanted to get that out of the way first
I have acquired an HTC Desire HD which booted very slowly when I got it, and ran ok except that sms did not work. I was told it was unlocked and rooted.
I have been trying for days to un-root or revert back to a stock rom with no success. I only half understand what I'm doing and everything I try fails at some point and I seem to have totally fuc%&d the poor thing.
Now when I switch it on, it goes to the T-Mobile splash screen and sits there forever. I can boot into H-boot and run recovery (CWM Recovery installed). I can then mount usb storage and acces it from my PC via usb.
In HBOOT or FASTBOOT I can not connect to my PC via usb (I have installed the correct drivers and it used to connect before I "fixed it"):crying:
These are the phone stats
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0029
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.13.110.4
(bootloader) serialno: HT0CVRX10795
(bootloader) imei: 356299043105830
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 4189mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fcef1579
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.003s
...
(bootloader) setup_tag addr=0xC0000100 cmdline add=0x8D0985F8
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x26503
(bootloader) TAG:hero panel = 0x1
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is T-MOB005
(bootloader) setting->cid::T-MOB005
(bootloader) serial number: HT0CVRX10795
(bootloader) commandline from head: no_console_suspend=1 wire.search_coun
(bootloader) t=5
(bootloader) command line length =510
(bootloader) active commandline: board_spade.disable_uart2=0 board_spade.
(bootloader) usb_h2w_sw=0 board_spade.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_spade.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=true androidboot.baseband=26.14.04.28_M androidboot.cid
(bootloader) =T-MOB005 androidboot.batt_poweron=good_battery androidboot.
(bootloader) carrier=TMUK androidboot.mid=PD9810000 androidboot.keycaps=q
(bootloader) werty androidboot.mode=normal androidboot.serialno=HT0CVRX10
(bootloader) 795 androidboot.bootloader=2.00.0029 zygote_oneshot=off kmem
(bootloader) leak=off no_console_suspend=1 wire.search_count=5
(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=lib
(bootloader) partition number=10
(bootloader) Valid partition num=10
(bootloader) jump_to_kernel: machine_id(2844), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:73765 msec
FAILED (status read failed (Too many links))
finished. total time: 7.544s
Any help would be greatly appreciated.
Please be gentle with me.

sup3rbird said:
I'm a total n00b, just wanted to get that out of the way first
I have acquired an HTC Desire HD which booted very slowly when I got it, and ran ok except that sms did not work. I was told it was unlocked and rooted.
I have been trying for days to un-root or revert back to a stock rom with no success. I only half understand what I'm doing and everything I try fails at some point and I seem to have totally fuc%&d the poor thing.
Now when I switch it on, it goes to the T-Mobile splash screen and sits there forever. I can boot into H-boot and run recovery (CWM Recovery installed). I can then mount usb storage and acces it from my PC via usb.
In HBOOT or FASTBOOT I can not connect to my PC via usb (I have installed the correct drivers and it used to connect before I "fixed it"):crying:
These are the phone stats
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0029
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.13.110.4
(bootloader) serialno: HT0CVRX10795
(bootloader) imei: 356299043105830
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 4189mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fcef1579
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.003s
...
(bootloader) setup_tag addr=0xC0000100 cmdline add=0x8D0985F8
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x26503
(bootloader) TAG:hero panel = 0x1
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is T-MOB005
(bootloader) setting->cid::T-MOB005
(bootloader) serial number: HT0CVRX10795
(bootloader) commandline from head: no_console_suspend=1 wire.search_coun
(bootloader) t=5
(bootloader) command line length =510
(bootloader) active commandline: board_spade.disable_uart2=0 board_spade.
(bootloader) usb_h2w_sw=0 board_spade.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_spade.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=true androidboot.baseband=26.14.04.28_M androidboot.cid
(bootloader) =T-MOB005 androidboot.batt_poweron=good_battery androidboot.
(bootloader) carrier=TMUK androidboot.mid=PD9810000 androidboot.keycaps=q
(bootloader) werty androidboot.mode=normal androidboot.serialno=HT0CVRX10
(bootloader) 795 androidboot.bootloader=2.00.0029 zygote_oneshot=off kmem
(bootloader) leak=off no_console_suspend=1 wire.search_count=5
(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=lib
(bootloader) partition number=10
(bootloader) Valid partition num=10
(bootloader) jump_to_kernel: machine_id(2844), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:73765 msec
FAILED (status read failed (Too many links))
finished. total time: 7.544s
Any help would be greatly appreciated.
Please be gentle with me.
Click to expand...
Click to collapse
You could try returning to stock if that may help by extracting the PD98IMG.zip from a RUU and putting it in the root of your SD Card then booting into HBOOT

What does it say in hboot? Is your phone in fastboot (not hboot, not recovery, not system) when you try to use fastboot from the computer? What have you done so far?

thekool said:
You could try returning to stock if that may help by extracting the PD98IMG.zip from a RUU and putting it in the root of your SD Card then booting into HBOOT
Click to expand...
Click to collapse
I have tried that, but it didn't work. I'm not sure if I used a suitable RUU.
I also tried with a couple of downloaded stock PD98IMG.zip files which were recommended in various how-to posts.
When I boot into HBOOT the phone shows the following error
SD Checking........
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nbh]
No image or wrong image!
Loading...[PD98IMG.zip]
No image!
Loading...[PD98IMG.nbh}
No image or wrong image!
and returns to the HBOOT screen

OK, first, you want a file named PD98IMG.zip, not PD98DIAG.zip. Second, what RUUs? Find one compatible with your phone's region. And I'm reiterating my questions from my earlier post.

bananagranola said:
What does it say in hboot? Is your phone in fastboot (not hboot, not recovery, not system) when you try to use fastboot from the computer? What have you done so far?
Click to expand...
Click to collapse
The phone is in fastboot when I try to connect via fastboot on my PC.
When I boot into hboot with a PD98IMG.zip file on a goldcard I get this error message
SD Checking........
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nbh]
No image or wrong image!
Loading...[PD98IMG.zip]
No image!
Loading...[PD98IMG.nbh}
No image or wrong image!
If I try to install PD98IMG.zip file using recovery I get the following response
Finding update package...
Opening update package...
Installing update...
Installation aborted.
NB I've been continuing to fiddle with it and I am once again able to connect to the phone via usb when in fastboot mode!
I am running windows 7 x64 if that makes a difference

You can't install PD98IMGs from recovery. If you want to flash one, put it on the root of your sdcard, boot into hboot, and choose to update. Make sure it's a compatible one for DHD. However, since you have recovery apparently, why don't you just full wipe and flash a ROM from recovery? Android Revolution HD is very stable and stock-ish.
And again. What does it say in hboot? What have you done so far?

bananagranola said:
You can't install PD98IMGs from recovery. If you want to flash one, put it on the root of your sdcard, boot into hboot, and choose to update. Make sure it's a compatible one for DHD. However, since you have recovery apparently, why don't you just full wipe and flash a ROM from recovery? Android Revolution HD is very stable and stock-ish.
And again. What does it say in hboot? What have you done so far?
Click to expand...
Click to collapse
I have attached an image of the hboot screen and the image which I was trying to use. The inf says its suitable for my phone cid T-MOB005
I'v just downloaded the rom you recommended and copied it to my sd card. Wiping now.
HOLY CRAP!!!!! it's working this time and I'm not doing anything I didn't try before. I just needed someone to hold my hand for a bit:laugh:
Many Many Thanks guys, specially bananagranola for persevering with my ineptitude.
EDIT Ok, I got over-excited and spoke too soon, it went through the full install routine but on reboot it's just sitting on the t-mobile splash screen:crying:

sup3rbird said:
I have attached an image of the hboot screen and the image which I was trying to use. The inf says its suitable for my phone cid T-MOB005
I'v just downloaded the rom you recommended and copied it to my sd card. Wiping now.
HOLY CRAP!!!!! it's working this time and I'm not doing anything I didn't try before. I just needed someone to hold my hand for a bit:laugh:
Many Many Thanks guys, specially bananagranola for persevering with my ineptitude.
EDIT Ok, I got over-excited and spoke too soon, it went through the full install routine but on reboot it's just sitting on the t-mobile splash screen:crying:
Click to expand...
Click to collapse
Check that the name of the file is incorrect. It should be PD98IMG and not PB98
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Wait, so did you do the recovery thing or the hboot thing? If the recovery thing, since you're S-On unlocked, you need to flash the ROM zip's boot.img from fastboot each time you flash a ROM. "fastboot flash boot boot.img"

bananagranola said:
Wait, so did you do the recovery thing or the hboot thing? If the recovery thing, since you're S-On unlocked, you need to flash the ROM zip's boot.img from fastboot each time you flash a ROM. "fastboot flash boot boot.img"
Click to expand...
Click to collapse
Thanks for sticking with me
I tried the recovery thing.
Ok I have flashed the boot.img from the Revolution rom via fastboot. It says it was successful.
Please tell me exactly what I should do next (as if you were talking to a moron).
It's 3:30 am here and I'm getting more stupid by the minute.

Did you flash the ROM from recovery before flashing the boot? You need to do that first. Then the boot.img. Then reboot.

bananagranola said:
Did you flash the ROM from recovery before flashing the boot? You need to do that first. Then the boot.img. Then reboot.
Click to expand...
Click to collapse
I did it in the wrong order...................I'm wiping everything and starting again.
Right, I have flashed the rom from my sdcard using cwm recovery; how do I get from here to fastboot to flash the boot.img which I copied from the rom?
FYI . If I "reboot system now" from recovery I cannot go directly to fastboot. The phone will only reboot into the regular boot mode or recovery mode.
My only other available method for restarting the phone is to pull the battery as the power switch no longer works.
FINAL EDIT Got it sorted working 100%
Thanks for your help

[Q] Unroot HTC One M8 Dual SIM

Hi, I have an HTC One M8 Dual SIM which I managed to root and s-off. I need to get this back to stock but am having some problems.
At the moment my phone is as follows:
Software Status: Official
***LOCKED***
M8_DUGL PVT SHIP S-OFF
CID-HTC__032
HBOOT-3.19.0.0000
OS-3.33.401.6
I have TWRP v2.8.4.0 installed as well
I have looked at the following thread http://forum.xda-developers.com/showthread.php?t=2735235 and managed to get the phone back to Software Status: Official and ***LOCKED*** I think but not managed to get S-ON or unrooted.
I have found firmware 3.33.401.6 for the M8 but not managed to find the actual stock OS.
Can someone point me in the right direction of what I need to do now?
This is the first time I have tried to unroot a device so sorry for anything I am missing from this post.
Thanks.

1. Do NOT S-ON unless the phone is 100% stock (and even then I wouldn't bother)
2. Flash the RUU in here - https://drive.google.com/file/d/0B17smFr95pleb3dJVDZVZTFfUEU/

EddyOS said:
1. Do NOT S-ON unless the phone is 100% stock (and even then I wouldn't bother)
2. Flash the RUU in here - https://drive.google.com/file/d/0B17smFr95pleb3dJVDZVZTFfUEU/
Click to expand...
Click to collapse
Thanks. I have downloaded and run and get the error "ERROR [130]: MODEL ID ERROR"
I followed the previous guide and think I may have used the wrong recovery image as the guide doesn't mention Dual SIM. So, I have downloaded recovery_1.54.401.10.img from here http://forum.xda-developers.com/showthread.php?t=2701376 and tried "fastboot flash recovery recovery_1.54.401.10.img" but get the following error:
sending 'recovery' (15236 KB)... OKAY
writing 'recovery'... FAILnot allowed
FAILED (remote: not allowed)
Execution time is 1(s)
Not sure if the recovery image is the problem or not however.
Any suggestions?
Thanks.

If you've relocked the bootloader it won't work. If you're getting the Model ID error it means you've changed your MID at some point. Can you connect your phone in fastboot and post the results of fastboot getvar all (leave out your IMEI and S/N)

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.30306251.27G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B64000
(bootloader) cidnum: HTC__032
(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: 4c3fbd70
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 27(ms)
Thanks.

Back to being unlocked now by following htconeroot com again. After this, I have now been able to run the command "fastboot flash recovery recovery_1.54.401.10.img" to remove TWRP.
I have tried running the RUU EXE again but get the same issue. Is there anything you can suggest to get this fixed?
Thanks for the help.

Well, you've go the right Model ID, so do this...before we start make sure the RUU I linked to is named ruu.zip (not ruu.zip.zip!) and that you have htc_fastboot in the same location (if you don't have htc_fastboot you can get it here - https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/). Also make sure you've relocked the bootloader using fastboot oem lock
1. Connect phone in fastboot mode
2. Run fastboot oem rebootRUU to get into RUU mode
3. Open a command window in the location where the RUU and htc_fastboot are
4. Type htc_fastboot flash zip ruu.zip
5. Wait for it to finish
If you get any errors please post them up

With "fastboot oem lock" I received the following, however after a reboot of the phone it is showing as *** RELOCKED ***:
Code:
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
Execution time is 1(s)
"fastboot oem rebootRUU" worked fine:
Code:
... (bootloader) Start Verify: 0
OKAY
Execution time is 21(ms)
"fastboot flash zip ruu.zip" failed:
Code:
sending 'zip'... (46605 KB) OKAY
sending time = 2.308 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 2(s)

Hmmmm, I'm not sure. Never had an issue doing it before but never used the Dual-SIM model. Can't see it being any different, though

I appreciate the help.
Do you have a link to stock recovery for the Dual SIM M8 as not sure that is 100% at the moment - when I press on RECOVERY it just goes back to the FASTBOOT menu.
Thanks.

I don't, no. I've been trying to see if anyone has the OTA cause you can pull it from that but the RUU is encrypted so can't be pulled without decrypting the RUU (which I don't know how to do)

M8whl radio; open dsp invalid version info

Hey Errybody;
thanks for all you getting with...
i have an htc m8whl, that only boots to H-boot and has such errors as invalid radio and open dsp.
I have attempted a (fastboot getvar all) and this is what i get.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45YWM03121
(bootloader) imei: (i deleted this)
(bootloader) imei2: Not Support
(bootloader) meid: (i deleted this)
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: d4c3cae5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
from then, i attempted an (
fastboot oem rebootRUU) and go this..
E:\adb>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [ERR] partition_read_emmc(562): error 1
(bootloader) Start Verify: 0
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
OKAY [ 10.076s]
finished. total time: 10.076s
with me is RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651 .18_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_44 6215_signed_2
but cant have a way of flashing it because it doesn't reboot to boot loader!
please help me on how to run through this.
much appreciated.

In the first lines you say it boots to H-Boot and in the last lines you say it doesn't boot to the bootloader.
Hboot and bootloader are the same. So where does it boot to and where does it not ?
Put it in the hboot/bootloader - fastboot USB menu and execute the RUU.exe from the PC .....
For a ruu you don't have to be in the fastboot oem rebootRUU mode

Mr Hofs said:
In the first lines you say it boots to H-Boot and in the last lines you say it doesn't boot to the bootloader.
Hboot and bootloader are the same. So where does it boot to and where does it not ?
Put it in the hboot/bootloader - fastboot USB menu and execute the RUU.exe from the PC .....
For a ruu you don't have to be in the fastboot oem rebootRUU mode
Click to expand...
Click to collapse
sorry, but i'd always think H-boot is one where i choose between options, whilst boot-loader is the dark screen where's the progress bar during a flash operation!
putting it right, the machine never reboots to RUU mode.
thanks for the info.

You don't have to be in the RUU mode at all to execute the ruu. If you have the ruu.exe you can do it like i previous posted, if you have the ruu.zip you can do it via the external SD card by renaming the zip file. Can't remember the exact name. Check for RUU.zip via sd card.

Thanks much Mr. Hofs for the support, lemme get with the zip option.,, will post results as soon

How-to S_ON back to stock firmware + ota updates?

Hey,
i currently run cm13 on my phone but i really would like to get back to stock. I found a sht-ton of guides but i really dont know where to start. If i run a nand backup (philz) will i be able to receive ota updates? Which firmware do i have to flash? Flash the stock recovery as well? What first? A step by step help would be really appreciated. I am not looking forward to pay 25$ for S_Off and as far as i can tell there is no other way to get S_off.
If you need any infos feel free to ask.
Thank you very much in advance

You usually don't need S-Off to return to stock and OTA.
First thing to do is getting to know your device variant.
Then we'll see what actually that you need.
Post fastboot getvar all result (without serial & imei no.)

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.131s
Click to expand...
Click to collapse
I also found the following easy to understand guide. Would this work for me ?

departet said:
I also found the following easy to understand guide. Would this work for me ?
Click to expand...
Click to collapse
Yes

(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.191s
Click to expand...
Click to collapse
Not working at all. After flashing the kernel and the recovery i got an error while relocking which leads to a reboot and a bootloop.
After i unlocked it again and flashed the newest twrp and a cm12.1 rom i tried it again (for some it helped) but i got the same thing again and was stuck at the bootloop once again. Any other way to do this or am i doing something wrong ?
EDIT: The failure is no problem at all. RUU has to be run in the fastboot mode which i can access. Didnt know that but its working now. Can be closed.

departet said:
EDIT: The failure is no problem at all. RUU has to be run in the fastboot mode which i can access. Didnt know that but its working now. Can be closed.
Click to expand...
Click to collapse
:good::good:
At least you did try and succeed

M8 s-on, relocked bootloader custom recovery...cannot unlock bootloader again

hi mates,
here is my problem, m8 whit kikat, s-on.
I tried to update to version 5 per ota but by recovery custom I did not allow it, by mistake I gave a relock to the bootloader with the twrp now I can not unlock the bootloader nor can I put the original recovery because I always get the error failed signature , What I can do, i need to reflash the stock recovery.
fastboot flash unlocktokem code.bin
target reported max download size of 1826017280 bytes
sending 'unlocktokem' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktokem'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.158s

request another unlock code from http://www.htcdev.com/bootloader/
and flash it then you can flash the stock recovery and do ota
or simply search for an RUU for your device variant ( if it's available ) and flash it while relocked

WarEduar said:
fastboot flash unlocktokem code.bin
target reported max download size of 1826017280 bytes
sending 'unlocktokem' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktokem'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.158s
Click to expand...
Click to collapse
unlocktokem is wrong
unlocktoken is correct
fastboot flash unlocktoken Unlock_code.bin

ahmed.ismael said:
request another unlock code from http://www.htcdev.com/bootloader/
and flash it then you can flash the stock recovery and do ota
or simply search for an RUU for your device variant ( if it's available ) and flash it while relocked
Click to expand...
Click to collapse
The Ruu was my hero. thanks.

ckpv5 said:
unlocktokem is wrong
unlocktoken is correct
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
nice to see you around ( long time no see you )
it turns out OP was sending a wrong command i didn't notice it was "m" not "n"
anyway he did what he wants to do

ahmed.ismael said:
nice to see you around ( long time no see you )
it turns out OP was sending a wrong command i didn't notice it was "m" not "n"
anyway he did what he wants to do
Click to expand...
Click to collapse
bro when i try to relock it error comes as
bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such device))
finished. total time: 6.177s
phone gets rebooted and then nothing happens

saiyansection said:
bro when i try to relock it error comes as
bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such device))
finished. total time: 6.177s
phone gets rebooted and then nothing happens
Click to expand...
Click to collapse
which device variant you have ?
also why you want to relock the bootloader ?
Sent from my OnePlus 5T using XDA Labs

ahmed.ismael said:
which device variant you have ?
also why you want to relock the bootloader ?
Sent from my OnePlus 5T using XDA Labs
Click to expand...
Click to collapse
I feel like my htc one m8 is messed up with emmc hardware , as i have phone suddenly rebooted
phone is s-on with unlocked bootloader!
current scenario is /data is corrupted I have tried all methods like changing the /data filesystem , format internal storage through TWRP , Repair the /data but no luck
bootloader is not getting relocked by using fastboot oem lock , unable to pass RUU through fastboot , fastboot zip gets halted if i try to pass RUU.zip through sdcard!
please help me to resolve the issue
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Hxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s

saiyansection said:
I feel like my htc one m8 is messed up with emmc hardware , as i have phone suddenly rebooted
phone is s-on with unlocked bootloader!
current scenario is /data is corrupted I have tried all methods like changing the /data filesystem , format internal storage through TWRP , Repair the /data but no luck
bootloader is not getting relocked by using fastboot oem lock , unable to pass RUU through fastboot , fastboot zip gets halted if i try to pass RUU.zip through sdcard!
please help me to resolve the issue
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Hxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s
Click to expand...
Click to collapse
have you tried to back to stock using twrp backups ?
from this thread https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
it's the easiest way to back to stock and see if your problem is solved
also you can update through OTA easily ( just accept it ) also it doesn't matter if the bootloader is locked or unlocked in this method
Sent from my OnePlus 5T using XDA Labs

ahmed.ismael said:
have you tried to back to stock using twrp backups ?
from this thread https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
it's the easiest way to back to stock and see if your problem is solved
also you can update through OTA easily ( just accept it ) also it doesn't matter if the bootloader is locked or unlocked in this method
Sent from my OnePlus 5T using XDA Labs
Click to expand...
Click to collapse
thanks brother at least you gave me proper suggestion ,
i am downloading backup , will flash and will let you know!
hope this will work

ahmed.ismael said:
have you tried to back to stock using twrp backups ?
from this thread https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
it's the easiest way to back to stock and see if your problem is solved
also you can update through OTA easily ( just accept it ) also it doesn't matter if the bootloader is locked or unlocked in this method
Sent from my OnePlus 5T using XDA Labs
Click to expand...
Click to collapse
I have tried to restore backup but data is not getting restored hence it is failing to restore!
when i only marked to restore cache , it went till 30mb and then phone rebooted itself!
any idea to set up m8 partitions? like my /data partition is corrupted or there is damn possibility of EMMC failure!
i have tried almost all methods still data is not mounting!

saiyansection said:
I have tried to restore backup but data is not getting restored hence it is failing to restore!
when i only marked to restore cache , it went till 30mb and then phone rebooted itself!
any idea to set up m8 partitions? like my /data partition is corrupted or there is damn possibility of EMMC failure!
i have tried almost all methods still data is not mounting!
Click to expand...
Click to collapse
did you used the suggested twrp version in the thread ( every backup have a suggested twrp version ) ?
if yes then try to format data in twrp then reboot to twrp and wipe all partitions then restore system and boot then reboot to system
if not solved i'm afraid it's a hardware failure and i can't help you further sorry
Sent from my OnePlus 5T using XDA Labs

ahmed.ismael said:
did you used the suggested twrp version in the thread ( every backup have a suggested twrp version ) ?
if yes then try to format data in twrp then reboot to twrp and wipe all partitions then restore system and boot then reboot to system
if not solved i'm afraid it's a hardware failure and i can't help you further sorry
Sent from my OnePlus 5T using XDA Labs
Click to expand...
Click to collapse
https://www.aliexpress.com/item/329...chweb0_0,searchweb201602_8,searchweb201603_52
its EMMC failure , so can i fix this motherboard on my old HTC one m8 16gb? please suggest so i can order!
above link is related to 32GB

saiyansection said:
https://www.aliexpress.com/item/329...chweb0_0,searchweb201602_8,searchweb201603_52
its EMMC failure , so can i fix this motherboard on my old HTC one m8 16gb? please suggest so i can order!
above link is related to 32GB
Click to expand...
Click to collapse
as i said,if it's a hardware failure i can't help
sorry
Sent from my OnePlus 5T using XDA Labs

ahmed.ismael said:
as i said,if it's a hardware failure i can't help
sorry
Sent from my OnePlus 5T using XDA Labs
Click to expand...
Click to collapse
Image CRC check result
rpm :0xAxxxxxxAB
sbl1: :0x9xxxxxxC4
sbl2 :0x0
sbl3 :0x0
tz :0xCxxxxxxxDC
radio :0x3xxxxxxx83
hboot :0x6DxxxxxxGA
boot :0x0
recovery :0x0
system :0x2xxxxxxxx8C
Can you explain the meaning of this... So i will be sure that it's hardware issue only..
Check sbl2 and sbl3

saiyansection said:
Image CRC check result
rpm :0xAxxxxxxAB
sbl1: :0x9xxxxxxC4
sbl2 :0x0
sbl3 :0x0
tz :0xCxxxxxxxDC
radio :0x3xxxxxxx83
hboot :0x6DxxxxxxGA
boot :0x0
recovery :0x0
system :0x2xxxxxxxx8C
Can you explain the meaning of this... So i will be sure that it's hardware issue only..
Check sbl2 and sbl3
Click to expand...
Click to collapse
sorry i can't
Sent from my OnePlus 5T using XDA Labs