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
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 Friends:
I've a big problem on my M8: It doesn't load S.O and remains only in fastboot mode. Yesterday, when I arrived to my home, suddenly reboots and stayed in fastboot mode. I share with you screen captures of my M8 ASAP. I tried to install in fastboot mode a stock RUU but it gives me error code in the bootloader process.
Please, i need your help or any advice to know how to fix it.:crying:
Many thanks and salutes from Chile.
I can't load SC yet...the forum won't let me do it. :crying:
What CID, hboot, radio, number, OS number (in bootloader)?
What is the filename for the RUU you tried?
What is the specific error message when running the RUU? Try running it a 2nd time (not unusual for it to fail the first time).
redpoint73 said:
What CID, hboot, radio, number, OS number (in bootloader)?
What is the filename for the RUU you tried?
What is the specific error message when running the RUU? Try running it a 2nd time (not unusual for it to fail the first time).
Click to expand...
Click to collapse
Hello, this is the info:
I install the ViperOne 4.51
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: 4.20.531.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(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: 06f11f5b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
You didn't answer half the questions I asked you.
Hard to help, if you don't provide all the info requested.
This is the error code:
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: 0
(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.297s]
finished. total time: 10.297s
redpoint73 said:
You didn't answer half the questions I asked you.
Hard to help, if you don't provide all the info requested.
Click to expand...
Click to collapse
Sorry man, but after 4 minutes i can answer in the forum... i'm doing my best.
I guess this is all the information... or did i miss something?
I tried to install the RUU for T-Mobile:
Device Name Latest ROM #
HTC One (M8) 4.20.531.4
XBEOP said:
I tried to install the RUU for T-Mobile:
Click to expand...
Click to collapse
I asked for the filename, that isn't a filename. I asked for a reason, since folks often think they have the right RUU, when in fact is completely the wrong one.
But probably irrelevant anyway. Based on the error message, you may have a fried emmc.
redpoint73 said:
I asked for the filename, that isn't a filename. I asked for a reason, since folks often think they have the right RUU, when in fact is completely the wrong one.
But probably irrelevant anyway. Based on the error message, you may have a fried emmc.
Click to expand...
Click to collapse
Oh! So my M8 is dead or not??
Please, let me know if there is a solution...
Thanks!
XBEOP said:
Oh! So my M8 is dead or not??
Click to expand...
Click to collapse
I'm not sure, but I'm thinking its dead.
I haven't seen those error messages before, so maybe somebody here with more knowledge can chime in.
Hi guys
So today I decided to unroot my phone and restore the stock ROM. I started by restoring backup that I made using TWRP before installing the custom ROM. After installing the stock ROM I powered on the phone and found the SuperSU was installed so I went to the settings and unrooted my phone. After that, I downloaded stock recovery file 4.16.401.10 from this thread forum.xda-developers.com/showpost.php?p=60211779&postcount=4> and flashed it on my phone.
Everything was working fine until I installed a OTA and after installing the update, it got stuck on HTC boot screen. I tried pressing volume up+ power buttons but the screen goes black after the first boot screen. I tried factory reset and clearing cash partition but to no avail. When I factory reset my phone it passes the first boot screen but it get stuck in the second boot screen where it shows HTC one m8.
I used fastboot before unrooting to get my cid and other information.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Also when I go to the recovery screen I get this
missing bitmap oem_unlock_bg (code -1)
missing bitmap oem_unlock_bg (code -1)_yes
missing bitmap oem_unlock_bg (code -1)_no
handle_cota_install; can't mount /sdcard, 1times
handle_cota_install; can't mount /sdcard, 2times
handle_cota_install; can't mount /sdcard, 3times
handle_cota_install; can't mount /sdcard, 4times
handle_cota_install; can't mount /sdcard, 5times
Click to expand...
Click to collapse
Please help I feel like my phone is bricked for good
You can't use a unrooted backup to do OTA .. won't work. OTA needs a pure non-rooted stock ROM to proceed.
Why don't you start again ... reinstall TWRP then restore the non-rooted backup (you can get the backup from the same thread where you got your stock recovery)
Or .. relock bootloader then install RUU zip - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Thank you for your reply.
I was finally able to get my m8 working after couple of tries of flashing stock ROM on my device. First, I extracted the zip file from the RUU and renamed rom.zip to 0P6BIMG.zip. After I've moved the file to my SD card and booted up my device I got the following error
PHP:
Device Halted due to Large Image update fail! Press <Power> to reboot
and my device kept rebooting so I took out the SD card.
Then I followed the instruction from this thread http://forum.xda-developers.com/htc-one-m8/general/guide-restore-european-htc-one-m8-to-t3072235 and I finally got my device working :victory:.
All the steps went okay except an error that I got when trying to lock the bootloader
PHP:
C:\Program Files (x86)\Minimal ADB and Fastboot>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 (No such file or directory))
finished. total time: 1.282s
but I just skipped it and started the RUU installation wizard and every thing went fine from there.
I still haven't tried to upgrade to Marshmallow and I doubt that I ever will, after the nightmare I experienced yesterday:laugh:. Beside, I don't see any significant upgrades compared to Lollipop.
I guess what caused this problem was the stock ROM that I restored using twrp. Maybe it was not installed properly. I should've installed fresh and clean stock ROM from the beginning.
Hey folks,
i wrongly made a thread in the M8-forum, because i thought this smartphone was a M8, but it's a M8s.
Anyway, a friend of mine sent me his smartphone to repair but i'm sitting in a corner right now.
I never had a HTC before, not in my hands, not received by any other person - first try so far.
Here's the situation:
The battery from the smartphone was empty over a night.
Next day, when he want to start - it doesn't start and runs into bootloader.
He tried some things i think, but isn't really familiar with that.
Bootloader saying:
*** Software status: Modified ***
*** UNLOCKED ***
M8QL_UL PVT SHIP S-ON
Click to expand...
Click to collapse
I searched the web and found the original RUU (RUU[email protected]50408_15.00_016_F_release_450409_combined_signed.zip) which i already downloaded. Beside, i already unlocked the Bootloader via "Unlock_code.bin".
Some useful infromations:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.0.[email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.16.401.10
(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: 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: 1d456ef7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
Click to expand...
Click to collapse
I don't really know how to restore this smartphone to 100% stock. Most of all Howtos describe M8 and that's not working at all.
Is someone familiar with that on M8s?
Can someone support me with this?
Okay, copied several zip-files to internal Samsung microSDXC EVO 64GB (exFAT) card, while renaming always to 0PKVIMG.zip but this phone won't eat any of these:
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.10_Radio_1.0.U20410.1@050408_15.00_016_F_release_450409_combined_signed.zip
Checking...
Wrong zipped image !
Device halted due to Large Image update fail!
Press <POWER> to reboot.
Click to expand...
Click to collapse
RUU_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.10_Radio_1.0.U20410.1@050408_15.00_016_F_release_450409_combined_signed.zip
Checking...
Wrong zipped image !
Device halted due to Large Image update fail!
Press <POWER> to reboot.
Click to expand...
Click to collapse
extracted rom.zip from RUU_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.10_Radio_1.0.U20410.1@050408_15.00_016_F_release_450409_combined_signed.zip
Checking...
Wrong zipped image !
Device halted due to Large Image update fail!
Press <POWER> to reboot.
Click to expand...
Click to collapse
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1_Radio_1.0.U20410.1@50408_15.00_016_F_release_436156_signed.zip
Parsing...
Device halted due to Large Image update fail!
Press <POWER> to reboot.
Click to expand...
Click to collapse
0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1@60201_20.05_018_F_release_479349_combined_signed.zip
Checking...
Wrong zipped image !
Device halted due to Large Image update fail!
Press <POWER> to reboot.
Click to expand...
Click to collapse
MD5Sums are always identical to the provided ones.
All zip-files comes from ruu.lalleman.net.
Read something about, the bootloader must be LOCKED/RELOCKED, but when i try, i get the following:
(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) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdif 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 (Too many links))
Click to expand...
Click to collapse
The phone reboots after that, but still says UNLOCKED.
Seem something is dead on that phone?
It always starts at bootloader.
Any hints!?
I don't have M8s only M8 but the basic is still the same.
You need a locked or relocked bootloader to proceed.
The RUU zip won't work on unlocked bootloader. The different that I noted is you need to use htc_fastboot mostly for M8s, M8 can run mostly on generic fastboot.
Try again .. use the htc_fastboot that you can find in this thread -
http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
htc_fastboot oem lock
htc_fastboot reboot-bootloader
I tried @ckpv5, doesn't work either.
Try what I suggested here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/help-request-t3439356
If it work, take it as temp fix. Need to find whether backup for 1.16.401.10 is available or not.
It's very late over here, I'll see anything I can find to help you tomorrow.
Thanks @ckpv5 !
Already tried flashing recoveries and all of them succeeded with:
sending 'recovery' (31014 KB)... OKAY
writing ''recovery'... OKAY
Execution time is 8(s)
Click to expand...
Click to collapse
After rebooting into bootloader and selecting RECOVERY, the phone reboot immediately to bootloader again.
For just a thousand of second i can see a white screen, with green htc and black android - logo.
Tried with:
twrp-recovery-2.8.6.0-m8s-qlul.img
twrp-2.8.7.0-m8s-qlul.img
twrp-3.0.2-0-m8.img
Always the same.
Oh ... that's bad. Without relocking bootloader you can't install RUU
and without TWRP installed you can restore a backup
I don't know whether these indicate some hardware problem.
Seems so.
Reading hundreds of tutorials and threads but all of them are different.
That's sad...
Anyway, thanks for your effort!
Hey guys,
i have also a problem with getting back to 100% stock.
I have restored my first backup with twrp and have the original rom. I can download the update for marshmallow.
When i want to install it the phone is restarting into bootloader with the following error message.
I think there is a problem with the recovery. I already tried the Vodafone UK & DE_CH recovery version.
The device is relocked. Somebody has an idea what i can do?
edit: sorry it should be the thumbnail
Greetings
realclone
realclone1000 said:
Somebody has an idea what i can do?
Greetings
realclone
Click to expand...
Click to collapse
The screenshot is too small to read what the error is.
If it is recovery error, you can adb pull the OTA and use the recovery that come from OTA to proceed.
As I said, the screenshot is too small, unable to read where the OTA is located on your device.
Short Update:
I tried again to run the RUU_M8_QL_UL_L50_SENSE60_Vodafone_UK_1.11.161.1_Radio_1.0.U20410.1G50408_15.00_016_F_release_430447_signed via ARUWizard.exe and now it worked.
So it was a downgrade, but after 2 Software updates i finally installed the Marshmallow update.
In my Opinion it's faster and the battery stays longer.
Now Nougat can come
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.