Hi all,
I have got my hands on a Moto 360 which seems to not be able to complete its boot. So I figured I would unlock it and flash it to something that is known to work from these forums. I have made a USB cable and was able to put the watch to bootloader. However after executing fastboot oem unlock I see the following output on the console:
Code:
➜ ~ fastboot oem unlock
...
(bootloader) WARNING: This will erase all private information on device
(bootloader) Press power button within 5 seconds to confirm
OKAY [ 0.005s]
finished. total time: 0.005s
It finishes right away, even without me pressing the power button. And the bootloader remains locked even if I press the power button afterwards. Is this a known ununlockable Moto 360 issue?
Here is the output of the getvar all command if it helps:
Code:
➜ ~ fastboot getvar all
(bootloader) max-download-size: 50331648
(bootloader) version: 0.3
(bootloader) version-hardware: 0009
(bootloader) version-bootloader: MINNOW0954
(bootloader) version-baseband: N/A
(bootloader) serialno: P027XQ2X63
(bootloader) apdieid: 12100219F7A73A0A0000D8FF0100
(bootloader) product: minnow
(bootloader) model-id: 0000
(bootloader) secure: no
(bootloader) qe:
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) sstdiag: 04000000d2a13787000000000000000
(bootloader) cpu: OMAP3 SE
(bootloader) sbd_dis: 0
(bootloader) variant: minnow
(bootloader) ram-size: 512MB
(bootloader) partition-size:mbr:0000000000020000
(bootloader) partition-type:mbr:emmc
(bootloader) partition-size:mbmloader:0000000000020000
(bootloader) partition-type:mbmloader:emmc
(bootloader) partition-size:mbm:0000000000080000
(bootloader) partition-type:mbm:emmc
(bootloader) partition-size:mbmbackup:0000000000080000
(bootloader) partition-type:mbmbackup:emmc
(bootloader) partition-size:ebr:0000000000080000
(bootloader) partition-type:ebr:emmc
(bootloader) partition-size:cdt.bin:0000000000080000
(bootloader) partition-type:cdt.bin:emmc
(bootloader) partition-size:pds:0000000000400000
(bootloader) partition-type:pds:ext4
(bootloader) partition-size:utag:0000000000180000
(bootloader) partition-type:utag:emmc
(bootloader) partition-size:logo.bin:0000000000100000
(bootloader) partition-type:logo.bin:emmc
(bootloader) partition-size:boot:0000000001000000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:recovery:0000000001000000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:misc:0000000000080000
(bootloader) partition-type:misc:emmc
(bootloader) partition-size:cid:0000000000080000
(bootloader) partition-type:cid:emmc
(bootloader) partition-size:kpanic:0000000000800000
(bootloader) partition-type:kpanic:emmc
(bootloader) partition-size:system:0000000010000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:cache:0000000010000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:customize:0000000008000000
(bootloader) partition-type:customize:ext4
(bootloader) partition-size:userdata:00000000c0e00000
(bootloader) partition-type:userdata:ext4
all: Done
finished. total time: 0.024s
I was not able to unlock this watch. But I was able to sideload an older version of F/W which now at least makes the watch to boot normally:
Code:
adb -s P027XQ2X63 sideload 5781439d7b4593772eeca3e32c168645bc229d37.signed-metallica-ota-2166028.zip
Hi everybody.
I ask for any help to restore my smartphone.
The problem is:
That I accidentally uploaded someone else's backup, the "cid" section. Now I have a cid: 0xDEAD
An interesting case, after this recovery the bootloader locked. Status:
securestate: oem_locked
*verity-state: enforcing
And I can not unlock it He writes an error, I think it's because of the frp section that changes the last byte to 01. After setting the checkbox in the setting - for the developer - the factory unlock.
D: \ ADB> fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) validate header error: 55
(bootloader) 3A15880808988261 #
(bootloader) 5A5932323442425A5642004D6F746F205A320000 #
(bootloader) 9D6169D0A91A800175B1EDA6CADAE6D3FB144F98 #
(bootloader) 09FAAB8E000000000000000000000000
OKAY [0.103s]
finished. total time: 0.104s
D: \ ADB> fastboot oem unlock XBZQPOSESK3KL7XQRRFT
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) feature disabled
OKAY [0.007s]
finished. total time: 0.008s
I watched a lot of articles and videos on the web. And I found an interesting video, where on Moto x the 2nd generation. In this situation, the bootloader was unlocked, unlocked, i.e. after flashing and starting the phone, oem_unlocked has already been indicated on the screen. I wonder if it's possible to do this on Z2 play?
https://www.youtube.com/watch?v=aYjzD9WZum0
I was trying to flash a full firmware. I can download all the parts of the firmware, except: system, boot, recovery. oem.img
In recovery I also can not get, only fastboot.
When flashing different versions of the bootloader, the file names change when prompting fastboot getvar all. So the bootloader loads well. But I have on my smartphone's screen:
Start up failed:
Your device did not start up succeessfuly.
Use the sofrware Repair Assistent on your computer to repair your device.
Connect yor device to your omputer to get the Software Repair Assistant.
When loading bootloader.img
-keys-cid50_retru \ Windows> fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot: bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB) ...
OKAY [0.178s]
writing 'bootloader' ...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [0.550s]
finished. total time: 0.730s
All is well.
.
But here's an example of boot.img
-keys-cid50_retru \ Windows> fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot: boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB) ...
OKAY [0.514s]
writing 'boot' ...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.726s
If you look at the smartphone's screen in bootlaoder logs - Failed to verify hab image boot.
Here's what fastboot shows: getvar all:
D:\ADB>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C7
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY224BBZVB
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 1E28AD1500000000000000000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 351888080892816
(bootloader) meid:
(bootloader) date: 07-25-2017
(bootloader) sku: XT1710-09
(bootloader) battid: SNN5985A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/albus/albus:7.1.1/NPS26.1
(bootloader) ro.build.fingerprint[1]: 18-19/19:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.51.19.albus.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953P_23.33.07.34R ALBUS_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g3b78496-0000
(bootloader) kernel.version[1]: 5-ge5590f6 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Fri Jun 30 23:09:12 CDT 20
(bootloader) kernel.version[4]: 17
(bootloader) sbl1.git: git=MBM-NG-VC0.C7-0-ge9cd975
(bootloader) rpm.git: git=5578f74
(bootloader) tz.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) devcfg.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) keymaster.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) cmnlib.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) prov.git: git=MBM-NG-VC2.06-0-g82f94af-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.C7-0-gb6d4956
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.134s
I will be glad to any help. I can check any action on my smartphone.
Hello as in topic.
I cant fix this. When i turn the phone on there's logo and 7 vibrations and phone hangs out.
If I use VOL DOWN + POWER and run Fastboot phone is recognized by windows and cmd fastboot but when I go to Bootloader phone is not recognized (USB enumeration failed).
I have tried to upload a recovery with fastboot and to unblock bootloader by HTC Dev website (other devices) when I try to use .bin file there's Question If I want to unlock bootloader I can choose yes but when I use POWER nothing happens. Same with commands fastboot oem unlock / fastboot oem lock (there's only 3 dots . . . and nothing happens).
There's no code for this but I get signature verification failed response when I am trying to flash recovery.img. Without this I can't probably use TRWM or Clockwork recovery.
Code:
D:\HTC>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.014s]
finished. total time: 0.016s
D:\HTC>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 421527552 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.136s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.014s]
finished. total time: 0.151s
D:\HTC>fastboot oem unlock
...
^C
D:\HTC>fastboot oem lock
...
^C
D:\HTC>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.004s
D:\HTC>fastboot reboot
rebooting...
finished. total time: 5.002s
D:\HTC>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 95B4C9068DC4D238C16CFFEB651A3899
(bootloader) 0B4F6B59C898234A372EF4432BE26F22
(bootloader) EE6A90CFDDF2C11F0EB32E26F112D1FA
(bootloader) F697601F1BC1A3D2781354C95CD2A39D
(bootloader) 4CD430F9251AC39650F38490738A1285
(bootloader) D75226FDFFC8D58A811F0EBB4C8FA00E
(bootloader) 225C951BFB1C5E06E86410BBAECA8EC5
(bootloader) 001071667674F9A8CB2D1DB3542FD922
(bootloader) 7DBAA091B3C105AE4DCD4A9EB3F37205
(bootloader) 1E52BF88AA1C62314DECCD1912B8D129
(bootloader) EE0445CAAE290F127E0B52768904A1AA
(bootloader) 79249B2311ADEB07AF838F504AC9E698
(bootloader) 36261A6E05E3E5E37068C6A2932BCDF1
(bootloader) 17B38436DE331A780F5CAF18F841805D
(bootloader) 55A18A2733ED627B2F61532D48E51E14
(bootloader) A59C3C02EEB4A79949B787AE059AB070
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.098s]
finished. total time: 0.099s
D:\HTC>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.18.0002
(bootloader) version-baseband: 14.11.36Q4.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT43HWL01784
(bootloader) imei: 35828xxxxxxxxx
(bootloader) meid:
(bootloader) product: g3u
(bootloader) platform: HBOOT-8225
(bootloader) modelid: 0P6A10000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4060mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e1c32097
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
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?).
Hello all,
I recently got a HTC ONE M8S that is OS wiped and I'm struggling to make it functional again.
When I turn on the device it goes to fastboot instantly and shows:
Code:
*** Software status : Modified ***
*** Unlocked ***
M8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OS-
eMMC-boot 2048MB
Aug 24 2015,19:4356.0
Menu is responsive but when I switch to hboot and select recovery phone goes off and back to fast boot again, factory reset is the same.
My idea to move from here was to use custom recovery so I flashed TWRP:
Code:
C:\adb>htc_fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img
sending 'recovery' (30548 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
Unfortunetaly it didn't helped much as i was still not able to run recovery from hboot menu.
I tried to trick the phone to boot into recovery with fastboot:
Code:
C:\adb>fastboot boot twrp-2.8.7.0-m8s-qlul.img
downloading 'boot.img'...
OKAY [ 2.440s]
booting...
OKAY [ 0.000s]
finished. total time: 2.440s
Unfortunetaly in my case it had no effect and recovery not booted.
I did further research and the most promissing advice was to restore the stock, so the idea was to follow this thread.
I used adb again to get more info about the phone and find a proper RUU for it:
Code:
C:\adb>fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(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: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: T-MOB009
(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: 1b18125b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
and after that downloaded 0PKV[email protected]50408_15.00_016_F_release_429388_signed.zip and copied it to SD card, but I could not proceed further as I cannot relock my phone (which is mandatory).
The error I got is this:
Code:
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recover
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: 15
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.400s
I'd really appreciate any sugestion about possible next step.
_dravec_ said:
Hello all,
I recently got a HTC ONE M8S that is OS wiped and I'm struggling to make it functional again.
When I turn on the device it goes to fastboot instantly and shows:
Code:
*** Software status : Modified ***
*** Unlocked ***
M8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OS-
eMMC-boot 2048MB
Aug 24 2015,19:4356.0
Menu is responsive but when I switch to hboot and select recovery phone goes off and back to fast boot again, factory reset is the same.
My idea to move from here was to use custom recovery so I flashed TWRP:
Code:
C:\adb>htc_fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img
sending 'recovery' (30548 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
Unfortunetaly it didn't helped much as i was still not able to run recovery from hboot menu.
I tried to trick the phone to boot into recovery with fastboot:
Code:
C:\adb>fastboot boot twrp-2.8.7.0-m8s-qlul.img
downloading 'boot.img'...
OKAY [ 2.440s]
booting...
OKAY [ 0.000s]
finished. total time: 2.440s
Unfortunetaly in my case it had no effect and recovery not booted.
I did further research and the most promissing advice was to restore the stock, so the idea was to follow this thread.
I used adb again to get more info about the phone and find a proper RUU for it:
Code:
C:\adb>fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(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: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: T-MOB009
(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: 1b18125b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
and after that downloaded 0PKV[email protected]50408_15.00_016_F_release_429388_signed.zip and copied it to SD card, but I could not proceed further as I cannot relock my phone (which is mandatory).
The error I got is this:
Code:
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recover
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: 15
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.400s
I'd really appreciate any sugestion about possible next step.
Click to expand...
Click to collapse
I suggest booting/flashing earlier twrp version for now. That worked for me once. Thread