[Q] Unroot HTC One M8 Dual SIM - One (M8) Q&A, Help & Troubleshooting

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)

Related

[Soft Bricked] need ruu for HTC M8

Hi all, first time in this forum and i hope someone would save me!
I have an HTC One M8
i'm **TAMPERED** **LOCKED** **SECURITY WARNING** and S-ON
so from hboot and fastboot i can't do anything (also enter in recovery mode)
via usb in hboot i can use fastboot command but not adb command (for that i have to turn on my device which restart in 30 secs so it's very hard)
i have to get it back to stock state but for doing that i need a RUU (fastboot flash is useless and as i sayed i can't do anything with adb in fastboot mode)
in order to do that i have downloaded from htc the mem_ul source to compile with AOSP but on the phone there aren't the proc/
config.gz file and i'm stucked here.
these are the fastboot getvar all instruction.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.19.1017
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.401.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***********
(bootloader) imei: *********
(bootloader) imei2: *******
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__001
(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: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.121s
Please help me you would be my hero!
ADB doesn't work in fastboot, only when booted into Android. You need to use the 4.16.401.10 RUU in General and flag it when connected in fastboot mode
EddyOS said:
ADB doesn't work in fastboot, only when booted into Android. You need to use the 4.16.401.10 RUU in General and flag it when connected in fastboot mode
Click to expand...
Click to collapse
His device is not M8 but HTC One mini 2.
ulisse2010 said:
Hi all, first time in this forum and i hope someone would save me!
Click to expand...
Click to collapse
Check this thread for your device type : http://forum.xda-developers.com/one-mini-2
and this for your RUU : http://forum.xda-developers.com/one-mini-2/general/htc-one-mini-2-european-signed-ruu-t3003069
Good spot!
thanks to all of you for the help in advance.
but i tried the ruu you suggested and it doesn't work. he said that i have to choice the correct one.
what it can be?
ulisse2010 said:
thanks to all of you for the help in advance.
but i tried the ruu you suggested and it doesn't work. he said that i have to choice the correct one.
what it can be?
Click to expand...
Click to collapse
That RUU says it requires s-off
Oh... i see
ok so it won't work if i modify like this? http://forum.xda-developers.com/showthread.php?t=2364349
it is about to inject another rom in a preexistent ruu...
have done it but and it starts but the progress bar stops on the first step and it reboot
ulisse2010 said:
thanks to all of you for the help in advance.
but i tried the ruu you suggested and it doesn't work. he said that i have to choice the correct one.
what it can be?
Click to expand...
Click to collapse
You have to use the one linked to by @ckpv5 as you have an M8 Mini - this is the 'proper' M8 forum...
i think it doesn't work because the file it's corrupted, another link maybe? i think also i'm getting trought this s****
Thx a lot all of you
How did you get this **TAMPERED** **LOCKED** **SECURITY WARNING**
Is it you unlocked it before then suddenly when it has reboot problem, it turns to **LOCKED** ?
How do you know the RUU zip is corrupted ? How actually you flash it, what commands ?
The OP will need the htc_fastboot version unless they do it via SD card...
i'm sorry it is **RELOCKED**
i'm pushing it by modifing another RUU (i put it inside by replacing the rom.zip and renaming it to rom.zip) and this RUU have the htc_fastboot.exe inside it so i'm trying now to push it via "cmd".
I think this op it's broken because i can't unzip it whitout error.
ulisse2010 said:
I think this op it's broken because i can't unzip it whitout error.
Click to expand...
Click to collapse
I have no idea what you are trying to do .... by pushing & modifying another RUU
But a signed RUU zip is encrypted, you can't unzip it, it's not that it's corrupted.
You flash it by connecting the phone in fastboot and then boot into RUU mode (fastboot oem rebootRUU) and then flash the RUU (htc_fastboot flash zip ruu.zip)
when i try to do fastboot oem rebootRUU the phone reboots but in normal mode not entering in bootloader or in RUU
it's possible to enter RUU mode with adb command?
ulisse2010 said:
when i try to do fastboot oem rebootRUU the phone reboots but in normal mode not entering in bootloader or in RUU
it's possible to enter RUU mode with adb command?
Click to expand...
Click to collapse
This is a symptom of a corrupted partition (more of a hardware problem) ...
I run out of idea to help you, further more your device is not M8.
Maybe someone else can help you ... good luck
please don't give up now i'm almost here:
i tried to flash it in ruu mode via htc_fastboot and the message is that:
sending 'zip'... (43267 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) total_image_number=7
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) current_image_number=1
(bootloader) current_image_number=2
(bootloader) current_image_number=3
(bootloader) current_image_number=4
(bootloader) current_image_number=5
(bootloader) current_image_number=6
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (SH4AAWR02353)...
< waiting for device >
sending 'zip'... (43267 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 74(s)
how i fix it?
i can't give the command two time because the device restart after this message.
I've moved this thread from the One M8 forum to the One Mini 2 forum. Hopefully you will get help here from people who have the same phone. Good luck!

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

{HELP} HTC M8 won't open recovery

Hello.
I have M8 in bootloader and it wont bootup, wont go in recovery etc. Everything I press, it returns to bootloader.
I don't know what to do, I already read all day stuff on forum and I can't do anything.
(I bought the phone like that)
You have to give more informations - firmware versions,boot version etc.Also try to flash some recovery.Do you get any error or ? Can be hardware problem if everything doesnt work...
mefistoreyon said:
You have to give more informations - firmware versions,boot version etc.Also try to flash some recovery.Do you get any error or ? Can be hardware problem if everything doesnt work...
Click to expand...
Click to collapse
I have errors, example, while trying to install recovery... "Writing recovery - FAILED"
Informations i have:
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.000
RADIO-INVALID_VER_INFO
OpenDSP_INVALID_VER_INFO
OS-
eMMC-boot 2048MB
Apr 18 2014, 16:06:33.0
juross said:
I have errors, example, while trying to install recovery... "Writing recovery - FAILED"
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.000
Click to expand...
Click to collapse
What version TWRP? Your firmware (hboot, radio, etc.) is really old, so most any version TWRP 2.8 or later will fail or cause other issues.
My recommendation would be to update to current firmware (by RUU may be the easiest way) then try to install TWRP again. If that is what you want to do, then I can give further info.
Also would be helpful if you do fastboot getvar all (if you know how) and post the output, so we can get more details on the phone's status (be sure to delete serial number and IMEI before posting).
redpoint73 said:
What version TWRP? Your firmware (hboot, radio, etc.) is really old, so most any version TWRP 2.8 or later will fail or cause other issues.
My recommendation would be to update to current firmware (by RUU may be the easiest way) then try to install TWRP again. If that is what you want to do, then I can give further info.
Also would be helpful if you do fastboot getvar all (if you know how) and post the output, so we can get more details on the phone's status (be sure to delete serial number and IMEI before posting).
Click to expand...
Click to collapse
I tried with twrp 2.6 and 2.7. - didn't work.
FASTBOOT GETVAR ALL info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(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_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s
imei and sn are deleted =)
I'd be gratefull if you guide me through firmware upgrade.
My advice would be to run the AT&T RUU (download link and instructions near the bottom of the following): http://www.htc.com/us/support/htc-one-m8-att/news/
You'll need to relock the bootloader to RUU with command: fastboot oem lock
RUU will wipe the phone, but it sounds like you haven't even had a chance to put any personal data on it yet, anyway.
RUU will put you on an updated, fully stock image including updated firmware. Hopefully will also get the phone booted back into OS.
After that, you can unlock the bootloader again, and flash TWRP if you like (to root, flash custom ROM, etc.).
redpoint73 said:
My advice would be to run the AT&T RUU (download link and instructions near the bottom of the following): http://www.htc.com/us/support/htc-one-m8-att/news/
You'll need to relock the bootloader to RUU with command: fastboot oem lock
RUU will wipe the phone, but it sounds like you haven't even had a chance to put any personal data on it yet, anyway.
RUU will put you on an updated, fully stock image including updated firmware. Hopefully will also get the phone booted back into OS.
After that, you can unlock the bootloader again, and flash TWRP if you like (to root, flash custom ROM, etc.).
Click to expand...
Click to collapse
Let me see if I undestand well.
1. Relock with that command
2. Double click od RUU file (I guess that ruu is system file and opens with CMD? ) and follow steps
juross said:
1. Relock with that command
2. Double click od RUU file (I guess that ruu is system file and opens with CMD? ) and follow steps
Click to expand...
Click to collapse
RUU is a Windows executable program. Just double click it, and it will lead you through the rest (very little action needed on your part). You don't run it from CMD.
If the phone is booted into OS, the RUU should reboot into into fastboot-bootloader mode. If not, you will need to boot into bootloader-fastboot mode yourself.
redpoint73 said:
RUU is a Windows executable program. Just double click it, and it will lead you through the rest (very little action needed on your part). You don't run it from CMD.
If the phone is booted into OS, the RUU should reboot into into fastboot-bootloader mode. If not, you will need to boot into bootloader-fastboot mode yourself.
Click to expand...
Click to collapse
when i try in CMD with command fastboot oem lock it gives me:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security (bootloader) [DEBUG] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000 (bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2 (bootloader) [SD_HW_ERR] read data fail in CMD18 (bootloader) CMD18: cmd failed (bootloader) [SD_HW_ERR] SD: Read data fail.. (bootloader) [PG_ERROR] htc_pg_hdr_get(118): (bootloader) sd_read_sector error (bootloader) [PG_ERROR] htc_pg_part_hdr_get(170): (bootloader) htc_pg_hdr_get failed (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 (Invalid argument)) finished. total time: 1.288s
Fail..
When I run RUU it stuck on "waiting for bootloader" (gives me error 170 or 171).
juross said:
when i try in CMD with command fastboot oem lock it gives me:
Fail..
Click to expand...
Click to collapse
It still says UNLOCKED in bootloader?
juross said:
When I run RUU it stuck on "waiting for bootloader" (gives me error 170 or 171).
Click to expand...
Click to collapse
Boot into bootloader-fastboot mode, if not already.
redpoint73 said:
It still says UNLOCKED in bootloader?
yes.
Boot into bootloader-fastboot mode, if not already.
Click to expand...
Click to collapse
I did...

HTC m8 phone keeps booting into fastboot mode

hello,
after root my phone
every time i try to put it in recovery mode it goes back to fastboot mode ..
even if i tried to flash a recovery on it , it would boot to fastboot mode
even when trying to install a official htc software update it just boots into fastboot ..
now i want to get it back to stock..
please help me !!
Need more info.
What version SuperSU? What version TWRP?
What "official update" file did you use? Was it an OTA or an RUU (list the exact file name)?
Also, do fastoboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
Need more info.
What version SuperSU? What version TWRP?
What "official update" file did you use? Was it an OTA or an RUU (list the exact file name)?
Also, do fastoboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
HI
Pls refer Bellow details
C:\miniadb_v1031>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.213311771.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.82.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mels_tuhl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B81000
(bootloader) cidnum: HTC__J15
(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: 8d01ca6e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
In addition to the fastboot output, I asked 4 questions, none of which you answered.
You have the M8 eye, not the "standard" M8. Far as I can tell (not many folks on xda have the "eye") you need a special version of TWRP for this version. You can try the right version TWRP, and flash SUperSU again, see if that helps. No idea if this version TWRP will work on not (can't personally vouch for it): https://forum.xda-developers.com/htc-one-m8/general/m8-eye-recovery-root-t3159648
Depending on what you did to the phone by flashing the wrong TWRP, it's hard to tell what the proper way to proceed.
redpoint73 said:
In addition to the fastboot output, I asked 4 questions, none of which you answered.
You have the M8 eye, not the "standard" M8. Far as I can tell (not many folks on xda have the "eye") you need a special version of TWRP for this version. You can try the right version TWRP, and flash SUperSU again, see if that helps. No idea if this version TWRP will work on not (can't personally vouch for it): https://forum.xda-developers.com/htc-one-m8/general/m8-eye-recovery-root-t3159648
Depending on what you did to the phone by flashing the wrong TWRP, it's hard to tell what the proper way to proceed.
Click to expand...
Click to collapse
Hi
It's work
Thanks for your support
redpoint73 said:
In addition to the fastboot output, I asked 4 questions, none of which you answered.
You have the M8 eye, not the "standard" M8. Far as I can tell (not many folks on xda have the "eye") you need a special version of TWRP for this version. You can try the right version TWRP, and flash SUperSU again, see if that helps. No idea if this version TWRP will work on not (can't personally vouch for it): https://forum.xda-developers.com/htc-one-m8/general/m8-eye-recovery-root-t3159648
Depending on what you did to the phone by flashing the wrong TWRP, it's hard to tell what the proper way to proceed.
Click to expand...
Click to collapse
hi
can i have stock recovery download link in that phone pls
I have a similar issue, but with a standard M8
£10 off ebay, so not expecting ,much (also means no known history) . 1 week old noob reading here and flashing phones
1) only boots to fastboot, and even does this when you leave it powered off, but charging.
2) select hboot, then to recovery, recovery doesn't run, just resets back to fastboot eventually, after screen goes white not black.
3) can partially speak to phone in fastbook and get versions ok (included below)
Getver all as below:
C:\Program Files (x86)\Minimal ADB and Fastboot>
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA615WM01404
(bootloader) imei: 357336060194484
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.114s
4) never been able to boot to full o/s so not in developer mode, so cant get response in adb (and dont know how to use this anyway)
5) tried RUU.exe - fails with usb error after it tries to restart bootloader
6) tried ruu.zip from memory card - fails with partition update fail
7) tried fastboot recovery image 6.12.401.4 and it fails to write - error is 'remote:signature verify fail'
8) random google lead me to fastboot oem reboot RUU which does this:
E:\android tools>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) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.052s]
finished. total time: 10.053s
9) htcdev unlock bootloader didnt work initially but has done now - is this a path i should try?
aim is to get a standard phone working again
Thanks
G
ok got my unlock token, seemed to flash it, but no status change/reaction on phone and rebooting still shows locked
E:\android tools>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.125s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ -0.000s]
finished. total time: 0.125s
G
My responses to some of your points below, in red font:
gda_scooby said:
(bootloader) version-main: 6.12.401.4
4) never been able to boot to full o/s so not in developer mode, so cant get response in adb (and dont know how to use this anyway) That is correct, you will not be able to use adb unless you can boot to OS or alternately TWRP custom recovery. So you are basically limited to fastboot in the current condition.
5) tried RUU.exe - fails with usb error after it tries to restart bootloader There isn't a valid exe format RUU for your version number (6.12.401.4) so you are probably using the wrong RUU. What is the version number or file name for the RUU.exe?
6) tried ruu.zip from memory card - fails with partition update fail Exactly what partition(s) is it failing to update? What is the version RUU you are using? The only valid one for your version would be the RUU.zip from here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
7) tried fastboot recovery image 6.12.401.4 and it fails to write - error is 'remote:signature verify fail' You can't flash an unsigned recovery image, unless the bootloader is unlocked. It also seems you are trying to flash stock recovery, and I don't see how that is going to help your current condition.
Click to expand...
Click to collapse
I think your best bet right now, is to try the correct RUU.zip which I linked above.

Is this eMMC bricked?

I have been given a 32gb us model which is stuck in bootloader i have tried everything and all fails.
Code:
fastboot getvar all
Code:
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT43SWM00546
(bootloader) imei: 35
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: -0.000s
htc_fastboot finished. total time: 0.047s
Unable to lock the boot loader to try flash RUU
Code:
fastboot oem lock
Code:
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 2082
(bootloader) [SD_ERR] sd_read_sector: read sector failed (2082 2)
(bootloader) [PG_ERROR] htc_pg_hdr_get(118):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(170):
(bootloader) htc_pg_hdr_get failed
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 262656
(bootloader) [SD_ERR] sd_read_sector: read sector failed (262656 2)
(bootloader) [PG_ERROR] htc_pg_hdr_get(118):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(170):
(bootloader) htc_pg_hdr_get failed
(bootloader) Update pg2fs_sec_recovery fail (-1)
(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 (Too many links))
finished. total time: 11.170s
htc_fastboot finished. total time: 11.232s
Is it worth trying anything else?
Try to flash this ruu with unlocked bootloader, I'm not sure It'll work but I think you have the developer edition which comes with an unlocked bootloader.
https://androidfilehost.com/?fid=24269982087015187
lucyr03 said:
Try to flash this ruu with unlocked bootloader, I'm not sure It'll work but I think you have the developer edition which comes with an unlocked bootloader.
https://androidfilehost.com/?fid=24269982087015187
Click to expand...
Click to collapse
The RUU exe file runs for a second i then accept the eula, After that nothing happens. The phone is connected to my pc also via fastboot usb.
David_UK said:
The RUU exe file runs for a second i then accept the eula, After that nothing happens. The phone is connected to my pc also via fastboot usb.
Click to expand...
Click to collapse
Get the ROM.zip from the exe and flash it by htc_fastboot.exe
lucyr03 said:
Get the ROM.zip from the exe and flash it by htc_fastboot.exe
Click to expand...
Click to collapse
Unable to flash
Code:
fastboot oem rebootRUU
Code:
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>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) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.041s]
finished. total time: 10.041s
htc_fastboot finished. total time: 10.096s
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>
Also unable to flash twrp
Code:
fastboot flash recovery twrp-3.2.1-0-m8.img
Code:
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot flash recovery twr
p-3.2.1-0-m8.img
htc_fastboot v3.0.9.2 (2015-05-29)
sending 'recovery' (20298 KB)...
OKAY [ 2.437s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 12.539s
htc_fastboot finished. total time: 12.609s
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>
I think its F***ed
Yeah, it seems like a dead nand.
David_UK said:
i have tried everything and all fails.
Click to expand...
Click to collapse
This statement doesn't tell us anything. It's worth listing the things you tried to flash, and the specific results for each. Otherwise, we waste your time and ours, as we guess or assume what you tried and didn't try.
Did you try to flash custom recovery TWRP? If so, which version number? Did you get an error message, or what was the failure mode or other results?
redpoint73 said:
This statement doesn't tell us anything. It's worth listing the things you tried to flash, and the specific results for each. Otherwise, we waste your time and ours, as we guess or assume what you tried and didn't try.
Did you try to flash custom recovery TWRP? If so, which version number? Did you get an error message, or what was the failure mode or other results?
Click to expand...
Click to collapse
I flashed twrp 3.2.1-0 this was the output
Code:
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot flash recovery twr
p-3.2.1-0-m8.img
htc_fastboot v3.0.9.2 (2015-05-29)
sending 'recovery' (20298 KB)...
OKAY [ 2.437s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 12.539s
htc_fastboot finished. total time: 12.609s
I haven't tried an ruu zip from sd card yet as i don't know which one to flash
I just tried ruu from sdcard and this is the result
David_UK said:
I haven't tried an ruu zip from sd card yet as i don't know which one to flash
Click to expand...
Click to collapse
The RUU which corresponds with your current firmware number (main version in getvar: 6.12.401.4) is here:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You can try to flash using htc_fastboot per the instructions, or SD card method.
If you can't get the RUU to work, relock the bootloader, or flash TWRP, I agree that it's probably emmc failure.
Help me please.
Help me please. Is this also a brick?
Code:
fastboot getvar all
Code:
C:\Users\Алекс>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH***
(bootloader) imei: 35***
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__032
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Finished. Total time: 0.031s
Unable to lock the boot loader to try flash RUU
Code:
fastboot oem lock
Code:
C:\Users\Алекс>fastboot oem lock
(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 (Unknown error))
Finished. Total time: 1.252s
Is it worth trying anything else?
Alex IvanoVVV said:
Help me please. Is this also a brick?
Click to expand...
Click to collapse
Please don't post same question to multiple threads. It is against forum rules to do so, as it clutters up the forum, and makes it very confusing for those trying to help you.
I've tried to help you in one of the 3 threads you posted in. So go look for it (now you see one of the reasons why cross posting is not a good idea?).

Categories

Resources