Whilst attempting to return my phone back to stock to that i can use the stock RUU i ran into a problem,
fastboot oem writecid T-MOB010
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(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 file or directory))
finished. total time: 1.201s
Hboot menu:Relocked
S-on
Any help much appreciated
How you tried to change CID on relocked and s-on device ?:crying:
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
How you tried to change CID on relocked and s-on device ?:crying:
Click to expand...
Click to collapse
Yes, I'm wondering the same.
Was the phone previously s-off, then made s-on again?
Additionally, you shouldn't need to change the phone back to the "stock" CID in order to RUU. The T-mob RUU should work fine with SuperCID.
Related
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)
Hello, I am trying to re-lock my bootloader using the "fastboot oem lock" command in adb but it is giving me this error:
...
(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) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.215s
Has anyone ran into this situation before? Any help would be greatly appreciated. My phone decided today that it wasn't going to work properly. When I boot the phone the OS itself is sluggish and inoperable. I want to just flash an RUU for convenience but getting my bootloader relocked is proving to be difficult. Thanks in advance!
I am upgradeing and want to put my phone back to stock using RUU. When I try to lock the bootloader I get an error (see below) it reboots to the bootloader and says "relocked" but I cannot boot to a rom or recovery. It just boots back to the bl. I can re-unlock the bootloader and it is fine. Any one have any idea? Thanks
(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 (Too many links))
finished. total time: 1.188s
I am not sure you need to re-lock your boot loader. When I went to upgrade my phone I restore a stock image to my phone and then restore the stock recovery. My boot loader is still unlocked and I am s-on (I never had s-off).
My biggest issue (at the time) was finding the correct stock recovery that match my stock rom. If the 2 mis-match it would not install the lollipop update.
Also I did not use an RUU. I believe RUU's also include radios and I didn't update my radio when I rooted my phone. So I used an image backup that made my phone look exactly as just before I installed the custom recovery.
-brad
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
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?).