Related
Hi,
I just became stupid again. I got my phone hanged upped on BOOTLOADER. after trying "fastboot oem writecid HTC__044"
i got this message.
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.273s
I noticed its hanging now, I did this with unlocked bootloader
how do i know if this is still workable? how can I get out of the bootloader. I promise not to do anything stupid If i get passed after this :crying:
You can't write a cid on a s-on hox !
Post the outcome of :
Fastboot getvar version-main
Sent from my HTC One X using XDA Premium 4 mobile app
Hello xda-community,
I want to relock bootloader in my device (HBOOT 1.18.0000 and S-OFF), but when I run the command, it shows the following message:
Code:
noris$ fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) Error status=0x482A00
(bootloader) [SD_HW_ERR] SD: read fail ..
(bootloader) START_BIT_ERR
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] sdcc_read: retry..
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(735): error 2
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.253s
And bootloader stays as ***UNLOCKED***. I have done a research through the website & google, but I cannot see any solution to my problem. It is pretty annoying as Im running out of ideas and I need it relocked.
I have tried with different recoveries & ROMs:
Stock recovery v1.56.401.2 - no luck
CWM recovery - no luck
cyanogenmodROM - no luck
PrimoU_Europe_2.22.401.1_ tock_Rooted_ODEX_LITE ROM - No luck
Did anyone have the same problem or knows what is going on?
Auto-answer:
It seems that after fresh "PrimoU_Europe_2.22.401.1_ tock_Rooted_ODEX_LITE ROM" install with CWM recovery touch and with the sd-card removed, it worked. Not sure what was blocking me before form being relocked, but finally it worked.
--Closing this topic--
You must flash RUU. W/o root init.d and stock kernel. If you're S-OFF you must son it first
Wysłane z mojego One V przy użyciu Tapatalka
I am fixing a TMO Htc One M8 for a friend. He currently has TWRP recovery but nothing will wipe or flash. I have posted the get var information and the log below along with all the steps I've taken, please share any insight into the matter.
Here is the Get VAR Information. I have tried to fix this device by relocking the Bootloader, flashing stock RUU RUU_M8_TMOUS_1.57.531.7 , Flashing modified firmware.zip, flashing recovery.img, nothing. Then unlocking the bootloader, flashing Philz recovery.img, Twrp.img, still same error. Current TWRP recovery registers nothing but errors. No wiping data, cache, system, etc. No installing backup nandroid, no flashing new rom through external SD card or adb sideload. Literally the phone won't flash anything and the error is error 12, "Remote signature verifiey failed" What kinda insight do you have into this? Anyway to get back to stock?
Thanks!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA446WM02874
(bootloader) imei: 352628060329457
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
LOG: D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash TMOUS-M8-1.12.53
1.19.recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.691s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.953s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash philz_touch_6.48
.4-m8.img
sending 'flash' (14436 KB)...
OKAY [ 1.467s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.293s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash T_Mo_1.57.531.7_
recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.688s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.753s
D:\All Android Devices\T Mobile HTC One M8>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(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 (Too many links))
finished. total time: 1.132s
twill1987 said:
I am fixing a TMO Htc One M8 for a friend. He currently has TWRP recovery but nothing will wipe or flash. I have posted the get var information and the log below along with all the steps I've taken, please share any insight into the matter.
Here is the Get VAR Information. I have tried to fix this device by relocking the Bootloader, flashing stock RUU RUU_M8_TMOUS_1.57.531.7 , Flashing modified firmware.zip, flashing recovery.img, nothing. Then unlocking the bootloader, flashing Philz recovery.img, Twrp.img, still same error. Current TWRP recovery registers nothing but errors. No wiping data, cache, system, etc. No installing backup nandroid, no flashing new rom through external SD card or adb sideload. Literally the phone won't flash anything and the error is error 12, "Remote signature verifiey failed" What kinda insight do you have into this? Anyway to get back to stock?
Thanks!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA446WM02874
(bootloader) imei: 352628060329457
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
LOG: D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash TMOUS-M8-1.12.53
1.19.recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.691s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.953s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash philz_touch_6.48
.4-m8.img
sending 'flash' (14436 KB)...
OKAY [ 1.467s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.293s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash T_Mo_1.57.531.7_
recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.688s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.753s
D:\All Android Devices\T Mobile HTC One M8>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(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 (Too many links))
finished. total time: 1.132s
Click to expand...
Click to collapse
okay I'm wondering why the bootloader is 3.18. I just converted my T-Mobile HTC one m8 to dev edition and that's what my bootloader is now.
That device must have been s-off before if it has the 3.18 bootloader. the problem is now you're s-on with the wrong bootloader in the phone. So it's not gonna verify something it can't. U need to unlock the bootloader then try to s-off again. Let me know if u need more help
twinnfamous said:
okay I'm wondering why the bootloader is 3.18. I just converted my T-Mobile HTC one m8 to dev edition and that's what my bootloader is now.
That device must have been s-off before if it has the 3.18 bootloader. the problem is now you're s-on with the wrong bootloader in the phone. So it's not gonna verify something it can't. U need to unlock the bootloader then try to s-off again. Let me know if u need more help
Click to expand...
Click to collapse
Yes, I think the device was S-off before was well. But how can I get the device S-off when I can't load any rom to establish an internet connection?
There's no way to get back to stock, or get an internet connection through the device to obtain S-off. I can unlock the boot-loader,
I've done that a few times, but how to get S-Off when the only two screens I can access are the bootloader and twrp? When bootloader is unlocked. I have used firewater before for S-off and it requires active internet connection on device.
Thanks again for helping
twill1987 said:
Yes, I think the device was S-off before was well. But how can I get the device S-off when I can't load any rom to establish an internet connection?
There's no way to get back to stock, or get an internet connection through the device to obtain S-off. I can unlock the boot-loader,
I've done that a few times, but how to get S-Off when the only two screens I can access are the bootloader and twrp? When bootloader is unlocked. I have used firewater before for S-off and it requires active internet connection on device.
Thanks again for helping
Click to expand...
Click to collapse
Unlock bootloader try to flash the latest open twrp recovery and try to install another Rom or backup. If you can see the roms in the sdcard then you should be able to flash the roms or backup.
If there was a way to get into adb YOU would be able to s-off again.
twinnfamous said:
Unlock bootloader try to flash the latest open twrp recovery and try to install another Rom or backup. If you can see the roms in the sdcard then you should be able to flash the roms or backup.
If there was a way to get into adb YOU would be able to s-off again.
Click to expand...
Click to collapse
I've tried to flash TWRP but I get that error. I tried to flash the newest twrp but it wouldn't flash.
I think the system is no longer mounted, that's why I get this error :"E: Unable to mount 'data'" and "E: Unable to mount internal storage"
twill1987 said:
I've tried to flash TWRP but I get that error. I tried to flash the newest twrp but it wouldn't flash.
I think the system is no longer mounted, that's why I get this error :"E: Unable to mount 'data'" and "E: Unable to mount internal storage"
Click to expand...
Click to collapse
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Well first your doing the wrong command. Its fastboot flash recovery recovery.img, not fastboot flash flash recovery.img.
x714x said:
Well first your doing the wrong command. Its fastboot flash recovery recovery.img, not fastboot flash flash recovery.img.
Click to expand...
Click to collapse
Yes, that was a typo. Every fastboot flash ends with error 12. Remote Signature.
I have tried literally everything with this device. Tried flashing new TWRP, Radio, Firmware, Etc. Nothing works.
Inside TWRP everything finishes with "failed" or "E: Unable to mount cache"
I tried to select cache under the mount in TWRP and it's greyed out. I fastboot erase cache, and it is literally
the only thing that worked for me. But still no way to restore previous Android. Tried flashing stock RUU's for 4.4.2 and 4.4.3, no dice.
Both RUU's get to 6 percent and then say failed. I'm wondering if the device thinks it's a different phone possibly a GPE edition so it won't
go back to stock? Just a thought. I have unlocked, and relocked the bootloader a million times trying different methods as well, not
sure what else there is to do next. This might be the end of the road for this customers phone.
twinnfamous said:
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Click to expand...
Click to collapse
Yes, that was a typo. Every fastboot flash ends with error 12. Remote Signature.
I have tried literally everything with this device. Tried flashing new TWRP, Radio, Firmware, Etc. Nothing works.
Inside TWRP everything finishes with "failed" or "E: Unable to mount cache"
I tried to select cache under the mount in TWRP and it's greyed out. I fastboot erase cache, and it is literally
the only thing that worked for me. But still no way to restore previous Android. Tried flashing stock RUU's for 4.4.2 and 4.4.3, no dice.
Both RUU's get to 6 percent and then say failed. I'm wondering if the device thinks it's a different phone possibly a GPE edition so it won't
go back to stock? Just a thought. I have unlocked, and relocked the bootloader a million times trying different methods as well, not
sure what else there is to do next. This might be the end of the road for this customers phone.
twinnfamous said:
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Click to expand...
Click to collapse
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
twill1987 said:
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
Click to expand...
Click to collapse
I just tried to reformat data again and it says same error in TWRP E: Cannot mount cache
I am able to flash Viper Rom though, but because it is S ON the rom won't boot past start up screen.
What a bizarre issue
twill1987 said:
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
Click to expand...
Click to collapse
There should be a way now that the new T-Mobile update to flash ruu if we can find one.
Edit: found one
http://www.htcdev.com/devcenter/downloads/P00
Just select T-Mobile as carrier and USA as region then you Wil see the latest ruu to download.
twinnfamous said:
There should be a way now that the new T-Mobile update to flash ruu if we can find one.
Click to expand...
Click to collapse
I flashed the 4.4.3 RUU update at HTCDEV.com It failed at the 6 percent mark. http://www.htcdev.com/devcenter/downloads
twill1987 said:
I just tried to reformat data again and it says same error in TWRP E: Cannot mount cache
I am able to flash Viper Rom though, but because it is S ON the rom won't boot past start up screen.
What a bizarre issue
Click to expand...
Click to collapse
the latest viper is from New firmware base so it takes 15 to 20 minutes to boot. Have you waited that long?
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
twill1987 said:
I flashed the 4.4.3 RUU update at HTCDEV.com It failed at the 6 percent mark. http://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
Sorry it seems I'm getting posts in different orders.
Flash viper and wait 15 to 20 minutes. And we can go from there.
I'm pretty sure we can get this resolved.
twinnfamous said:
the latest viper is from New firmware base so it takes 15 to 20 minutes to boot. Have you waited that long?
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
Sorry it seems I'm getting posts in different orders.
Flash viper and wait 15 to 20 minutes. And we can go from there.
I'm pretty sure we can get this resolved.
Click to expand...
Click to collapse
I'll try to flash the latest Viper. The 1.6.0 it says everything flashed correctly, but gets stuck at the HTC boot screen.
I just flashed the 1.8.0 OTA update and everything installs but it sticks at the boot screen.
I see the 2.2.0 update is out so I'm downloading that now, I'll flash and see how it goes.
I'll update, thanks for your help!
Ruu requires the bootloader be locked
Sent from my HTC One_M8 using XDA Free mobile app
Hellooow!
I noticed i got an message when relocking my bootloader.
It is relocked but still wondering what this means?
see bold text
hope someone knows! Thnx!
I'm S-OFF
HTC one m8 stock android 4.4.4
3.28.401.9
Radio 1.22.21331147A1.29G
ps: already searched foru and google and www etc...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(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 (Too many links))
finished. total time: 1.153s
0kk0 said:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(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 (Too many links))
finished. total time: 1.153s
Click to expand...
Click to collapse
Hi,
i have the same problem- searched the web etc, i didnt find what is the problem.
and it is not relocked on my phone, so i suppose its not on yours either
mato123 said:
Hi,
i have the same problem- searched the web etc, i didnt find what is the problem.
and it is not relocked on my phone, so i suppose its not on yours either
Click to expand...
Click to collapse
Hi!
No mine relocks fine.. it says RELOCKED and i can unlock it again and relock etc.. but everytime got that "error" message.
Are you s-off?
0kk0 said:
Hi!
No mine relocks fine.. it says RELOCKED and i can unlock it again and relock etc.. but everytime got that "error" message.
Are you s-off?
Click to expand...
Click to collapse
no, im S-ON and every time i try it says ***UNLOCKED***
mato123 said:
no, im S-ON and every time i try it says ***UNLOCKED***
Click to expand...
Click to collapse
you could try to download correct 0P6BIMG.zip for your device and place it on sdcard in your phone.
Then flash it from bootloader...
It flashed correctly on mine(unlocked) without fastboot oem lock
And then try to relock it again?
0kk0 said:
you could try to download correct 0P6BIMG.zip for your device and place it on sdcard in your phone.
Then flash it from bootloader...
It flashed correctly on mine(unlocked) without fastboot oem lock
And then try to relock it again?
Click to expand...
Click to collapse
Sorry, what is 0P6BIMG.zip? how can i find one for myself? im at&t one m8.
Also what should i write in fastboot command?
mato123 said:
Sorry, what is 0P6BIMG.zip? how can i find one for myself? im at&t one m8.
Also what should i write in fastboot command?
Click to expand...
Click to collapse
That zip is all in one file to flash stock system/os firmare recovery etc...
Here is more info for flashing RUU for your device: http://forum.xda-developers.com/att-htc-one-m8/general/lolipop-ruu-htc-att-m8-t3075854
0kk0 said:
That zip is all in one file to flash stock system/os firmare recovery etc...
Here is more info for flashing RUU for your device: http://forum.xda-developers.com/att-htc-one-m8/general/lolipop-ruu-htc-att-m8-t3075854
Click to expand...
Click to collapse
i ran RUU.exe and this is what i get:
capture.png where it rebooted to bootloader, fastboot usb mode, took it quite a while, cca 1 min
capture1.png says sth is wrong with usb
mato123 said:
i ran RUU.exe and this is what i get:
capture.png where it rebooted to bootloader, fastboot usb mode, took it quite a while, cca 1 min
capture1.png says sth is wrong with usb
Click to expand...
Click to collapse
strange...
have you tried:
1) From a powered off state, hold VOLUME DOWN while powering on the device.
2) Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
3) Connect the device to the PC while in this state and attempt the ROM update again.
0kk0 said:
I noticed i got an message when relocking my bootloader.
I'm S-OFF
Click to expand...
Click to collapse
There is no reason to relock the bootloader, since you are s-off.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
0kk0 said:
you could try to download correct 0P6BIMG.zip for your device and place it on sdcard in your phone.
Then flash it from bootloader...
It flashed correctly on mine(unlocked) without fastboot oem lock
And then try to relock it again?
Click to expand...
Click to collapse
It won't work for that guy, since he is s-on.
The reason it flashed for you with the bootloader unlocked, is since you are s-off.
redpoint73 said:
There is no reason to relock the bootloader, since you are s-off.
Click to expand...
Click to collapse
thnx for your answer but doenst answer my question
i got an "error" ans whas wondering what it means etc...
mato123 said:
i ran RUU.exe and this is what i get:
capture.png where it rebooted to bootloader, fastboot usb mode, took it quite a while, cca 1 min
capture1.png says sth is wrong with usb
Click to expand...
Click to collapse
You have a USB connectivity issue, so this is probably the reason why fastboot oem lock does not work.
Make sure you run the command while the phone is booted into bootloader-fastboot mode.
redpoint73 said:
You have a USB connectivity issue, so this is probably the reason why fastboot oem lock does not work.
Make sure you run the command while the phone is booted into bootloader-fastboot mode.
Click to expand...
Click to collapse
tnx for your answer.
i was in bootloader in fastboot usb mode already.
i sent you PM regarding whole situation. should i continue to write here or make a new thread?
Originally unlocked bootloader through HTC-DEV
CID: 11111111
Hboot 3.19.0.0000
Radio-1.2121331147A1.19_2G
M8_UL_CA PVT SHIP S-OFF
I'm trying to relock the bootloader so I can RUU, however keep getting the following error when running "fastboot oem lock"
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))
finished. total time: 1.230s
After the above message, the phone goes from unlocked -> relocked. However I believe the phone is still actually unlocked because I'm getting Error: 155 when I try to run an RUU. I also can see the red text on the charging screen indicating the phone is unlocked.
I have also used this method http://forum.xda-developers.com/showthread.php?t=2708571 to try unlock/relock, and also tried to relock and use HTC-DEV to lock but no matter what, I'm still getting Error 155.
Also, none of the user data is being wiped when I use fastboot flash unlocktoken Unlock_code.bin
blazerxzero said:
Originally unlocked bootloader through HTC-DEV
CID: 11111111
Hboot 3.19.0.0000
Radio-1.2121331147A1.19_2G
M8_UL_CA PVT SHIP S-OFF
1. I'm trying to relock the bootloader so I can RUU, however keep getting the following error when running "fastboot oem lock"
2. After the above message, the phone goes from unlocked -> relocked. However I believe the phone is still actually unlocked because I'm getting Error: 155 when I try to run an RUU. I also can see the red text on the charging screen indicating the phone is unlocked.
Click to expand...
Click to collapse
1. You don't need to relock bootloader to run RUU on S-Off device.
2. Are you trying to run Marshmallow RUU ? You'll get error 155 if the current firmware is lower than Marshmallow. You need to flash its Marshmallow firmware first then run RUU.
Thanks for the reply, I tried your method of matching the RUU with the firmware version and got a different error.
Error couldn't allocate space, even though the RUU image was smaller than the available storage.
The solution which resolved the problem was to rename the correct RUU version zip load onto SD card and flash using the bootloader auto-detection method.