I came back from lunch and my phone wouldn't turn on. I did the power+vol combo to bring me into fastboot, but when I try to reboot or get into recovery the phone vibrates and goes directly back into fastboot.
It's S-ON, with TWRP 2.something, rooted, running stock Sense Kitkat.
I tried to flash the latest TWRP but I get this:
Code:
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 1830727680 bytes
sending 'recovery' (17020 KB)...
OKAY [ 1.509s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.578s
ADB doesn't list the device, so no ADB:
Code:
C:\adb>adb devices
List of devices attached
I tried several fastboot commands like "oem unlock", "oem lock", "flashing unlock", "flashing lock", and "erase cache"; all gave an error like "FAILED (remote: not allowed)" or "FAILED (remote: image update error)" or similar.
I also tried to use the "FACTORY RESET" menu command, but it just does vibrates and goes back to the main menu.
Any and all help is appreciated.
When I power up, I get this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I select HBOOT:
More details I can grab...
Code:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -- removed by winnower --
(bootloader) imei: -- removed by winnower --
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.181s
Thank you.
I tried something else and got even more errors:
Code:
C:\adb>fastboot oem rebootRUU
...
(bootloader) [DEBUG] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(560): error 2
(bootloader) Start Verify: 3
(bootloader) [DEBUG] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.035s]
finished. total time: 0.037s
I found the original unlock code from HTC Dev and tried to re-unlock my unlocked bootloader:
Code:
C:\adb>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830727680 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.113s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.005s]
finished. total time: 0.119s
The phone didn't do anything after I had done it though.
what are you trying to achieve here? i see you have no OS/fw installed to start.
this below step will wipe everything and install all fresh. rename files accordingly.
once you in fastboot adb doesn't work
it should be
fastboot devices
then to flash firmware
fastboot oem rebootRUU
fastboot flash zip fw.zip
fastboot reboot
then flash the twrp
fastboot flash recovery twrp.img
fastboot reboot
Thanks for the help henryrk, but I'm starting to think I've had an eMMC failure.
Code:
C:\adb>fastboot oem rebootRUU
...
(bootloader) [DEBUG] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(560): error 2
(bootloader) Start Verify: 3
(bootloader) [DEBUG] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.058s]
finished. total time: 0.059s
winnower said:
I tried to flash the latest TWRP but I get this:
Click to expand...
Click to collapse
Latest TWRP (2.8.7.0) won't work with your ancient hboot. You need an older version TWRP. Forget the cutoff exactly, but old hboots won't work on new version TWRP; and also old TWRP won't work on most newer hboot/firmware configs.
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
winnower said:
Thanks for the help henryrk, but I'm starting to think I've had an eMMC failure.
Click to expand...
Click to collapse
Its certainly possible. Especially if the simple command to reboot bootloader RUU mode fails.
It would also explain why the phone seemingly went bad with no action on your part.
Did you try any of the above and have you got a solution yet
---------- Post added at 09:51 PM ---------- Previous post was at 09:47 PM ----------
what Rom was you using before this happened ie Cyanogen Mod.......
Ok, I've given up on recovering this thing.
I tried flashing TWRP 2.7.0.1 and it failed with the same message.
Every command I try I end up with some version of SD_HW_ERR or READ_EMMC_FAIL or similar. The solution is to get a new mainboard, or a new phone...
*sigh*
winnower said:
Ok, I've given up on recovering this thing.
I tried flashing TWRP 2.7.0.1 and it failed with the same message.
Every command I try I end up with some version of SD_HW_ERR or READ_EMMC_FAIL or similar. The solution is to get a new mainboard, or a new phone...
*sigh*
Click to expand...
Click to collapse
May I suggest that you leave your device as is for now. Messing around with it while you have INVALID radio, OS, and recovery will only serve to brick your M8. Also, attempting to lock/unlock your phone at this point will most likely kill it.
A most agreeable step at this point is to flash a full stock firmware FROM SD CARD, or even an RUU. From there on you can try to flash "TWRP 2.7.1.0" and restore a stock nand backup.
Cheers
Related
I used firewater to unlock and s-off my HTC One with 4.3. Everything went well and I installrd TWRP. I did a back up and when I restarted the phone it said No OS. After trying so many things I ended up, only able to boot into bootloader with no recovery or os and anything I try to send to the phone fails.
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN073****
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4256mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.110s
This is what I get when I try to flash a new recovery.
C:\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7vzw.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9744 KB)...
OKAY [ 1.166s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.326s
Thanks for any in put guys.
Make sure you open command prompt in administrator mode. Try renaming your recovery to recovery.img. And make sure you can see file extensions on your computer. If file extensions are hidden and you add that img at the end,it could really be recovery.img.img.
joeymagnus1 said:
Make sure you open command prompt in administrator mode. Try renaming your recovery to recovery.img. And make sure you can see file extensions on your computer. If file extensions are hidden and you add that img at the end,it could really be recovery.img.img.
Click to expand...
Click to collapse
I tried this and it failed....
C:\platform-tools>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) Start Verify: 0
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.057s]
finished. total time: 0.057s
C:\platform-tools>fastboot flash zip Twrp_2.6.3.4_RUU_Mode.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9278 KB)...
OKAY [ 1.150s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.185s
C:\platform-tools>
I got the same errors running as adm... Should I try this? Someone had a similar problem but he was S-On.
Here you guys go. Santod added it to his thread. http://goo.gl/JEkyCk 2.10.605.1 RUU Signed
joeyz400 said:
I used firewater to unlock and s-off my HTC One with 4.3. Everything went well and I installrd TWRP. I did a back up and when I restarted the phone it said No OS. After trying so many things I ended up, only able to boot into bootloader with no recovery or os and anything I try to send to the phone fails.
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN073****
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4256mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.110s
This is what I get when I try to flash a new recovery.
C:\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7vzw.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9744 KB)...
OKAY [ 1.166s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.326s
Thanks for any in put guys.
Click to expand...
Click to collapse
This line: (bootloader) product: m7_wlv indicates that you flashed a Sprint bootloader to the phone. It should say m7_vzw. The Sprint model has different mount points, so that could explain the error.
NotATreoFan said:
This line: (bootloader) product: m7_wlv indicates that you flashed a Sprint bootloader to the phone. It should say m7_vzw. The Sprint model has different mount points, so that could explain the error.
Click to expand...
Click to collapse
I must have messed something up when I was still able to get into recovery, I wasn't able to flash anything. I kept getting E: drive errors so I flashed a stock recovery.... that is when I lost Twrp and only bootloops into boot loader with no OS.
I just tried flashing openrecovery-twrp-2.6.3.3-m7.img and got the same errors....
C:\platform-tools>fastboot flash zip Twrp_2.6.3.4_RUU_Mode.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9278 KB)...
OKAY [ 1.152s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.190s
C:\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 4.911s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 5.090s
C:\platform-tools>
joeyz400 said:
I must have messed something up when I was still able to get into recovery, I wasn't able to flash anything. I kept getting E: drive errors so I flashed a stock recovery.... that is when I lost Twrp and only bootloops into boot loader with no OS.
I just tried flashing openrecovery-twrp-2.6.3.3-m7.img and got the same errors....
C:\platform-tools>fastboot flash zip Twrp_2.6.3.4_RUU_Mode.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9278 KB)...
OKAY [ 1.152s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.190s
C:\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 4.911s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 5.090s
C:\platform-tools>
Click to expand...
Click to collapse
If you have stock recovery on the phone now, try using ADB Sideload to push the stock, rooted 4.4.2 ROM from here: http://forum.xda-developers.com/showthread.php?t=2485319
If that works for you, then try pushing TWRP 2.6.3.4.
Will that relock my bootloader and make it S-On? I was on stock 4.3 before I started everything.
NotATreoFan said:
If you have stock recovery on the phone now, try using ADB Sideload to push the stock, rooted 4.4.2 ROM from here: http://forum.xda-developers.com/showthread.php?t=2485319
If that works for you, then try pushing TWRP 2.6.3.4.
Click to expand...
Click to collapse
joeyz400 said:
Will that relock my bootloader and make it S-On? I was on stock 4.3 before I started everything.
Click to expand...
Click to collapse
No. But you will also need to flash the latest firmware package from that thread. It also does not affect S-Off, so don't worry.
Seems my bootloader is corrupt... Is there anyway to wipe it clean to start over?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\platform-tools
C:\platform-tools>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) Start Verify: 0
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.059s]
finished. total time: 0.059s
C:\platform-tools>
I tried flashing the stock recovery and got this error:
C:\platform-tools>fastboot flash recovery 1.10.605.10_recovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (16383 KB)...
OKAY [ 1.793s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.953s
C:\platform-tools>
I just tried this...... FAIL
C:\platform-tools>fastboot flash RUU RUU_M7_WL_JB43_SENSE50_VZW_MR_VERIZON_WWE_2
.10.605.1_Radio_1.12.41.1112_2_NV_VZW_3.71_002_release_341019_signed_2.zip
target reported max download size of 1526722560 bytes
sending 'RUU' (1232586 KB)...
OKAY [ 41.968s]
writing 'RUU'...
FAILED (remote: not allowed)
finished. total time: 42.006s
C:\platform-tools>
joeyz400 said:
I just tried this...... FAIL
C:\platform-tools>fastboot flash RUU RUU_M7_WL_JB43_SENSE50_VZW_MR_VERIZON_WWE_2
.10.605.1_Radio_1.12.41.1112_2_NV_VZW_3.71_002_release_341019_signed_2.zip
target reported max download size of 1526722560 bytes
sending 'RUU' (1232586 KB)...
OKAY [ 41.968s]
writing 'RUU'...
FAILED (remote: not allowed)
finished. total time: 42.006s
C:\platform-tools>
Click to expand...
Click to collapse
Is this the encrypted RUU? If so, you may need the decrypted one. Or vice versa.
Sent from my HTC6500LVW using Tapatalk
This is my latest attempt... FAIL***** Am I doing something wrong?
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-OFF
(bootloader) serialno: 12345678****
(bootloader) imei: 99000428262****
(bootloader) meid: 9900042826****
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN073****
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4074mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.113s
C:\platform-tools>fastboot flash recovery PN07IMG_M7_WL_JB_50_VZW_1.10.605.10_DE
CRYPT.zip
target reported max download size of 1526722560 bytes
sending 'recovery' (1178304 KB)...
OKAY [ 40.982s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 41.018s
C:\platform-tools>fastboot flash RUU PN07IMG_M7_WL_JB_50_VZW_1.10.605.10_DECRYPT
.zip
target reported max download size of 1526722560 bytes
sending 'RUU' (1178304 KB)...
OKAY [107.432s]
writing 'RUU'...
FAILED (remote: not allowed)
finished. total time: 107.468s
C:\platform-tools>
you are doing more than I can do right now. how did you get the sdk bundle to work?
I had it working before things went wrong. If you are on windows 8 people have problems so search that if that is your OS. I'm running Windows 7 on my PC. I had Unlocked S-Off and rooted with TWRP 2.6.3.3 installed. Everything was working till I did my first back up. When I restarted my phone it said there was no OS installed and the bootloops started but I still had recovery. But I couldn't restore my backup. Now I can only boot into bootloader with no OS or Recovery. Search how to set up SDK and ADB for your OS and take it from there. I am stumped because I cant run any RUU's, all I get are errors. Good luck.
I don't have my SIM card installed. Does that matter?
joeyz400 said:
I don't have my SIM card installed. Does that matter?[/QUOTE
]that shouldn't matter
Click to expand...
Click to collapse
If I fried something can the part be bought and replaced?
Jamesdbritt said:
joeyz400 said:
I don't have my SIM card installed. Does that matter?[/QUOTE
]that shouldn't matter
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I gave up... I'm sending the phone to MobileTechVideos.COM they say they can repair it for $60. Thanks for all your help. Has anyone heard of their service to repair bricked phones using Riff Jtag tools?
Hello all Masters
I own HTC desire C i first did everything correct
with this thread http://forum.xda-developers.com/showthread.php?t=2275761
but there was no google apps and all
so i retried the same procedure with GAAP (Please forgive me i dnt remember)
and got my phone all DEAD
I have given HTC centre they says motherboard is dead u have to spent 5700 rs for the same.
as i can not bare that much money.. hard working guy..
Now
with details of error
****UNLOCKED*****
GOLFU PVT SHIP S-ON RL
HBOOT-1.31.0000
RADIO-1.10.98.15
eMMC-boot
Jul 12 2012,15:44:30
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.31.0000
(bootloader) version-baseband: 1.10.98.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.00.720.2
(bootloader) serialno: removed
(bootloader) imei: Removed
(bootloader) product: golfu
(bootloader) platform: HBOOT-7225A
(bootloader) modelid: PL0110000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4204mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e118df77
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
I have tried everything as its S-ON so can not got recovery mode
C:\android-sdk\sdk\platform-tools>adb push NaMeLeSsR0m_v7.o.0_HtCDeSiReC.zip /sd
card/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\android-sdk\sdk\platform-tools>adb devices
List of devices attached
C:\android-sdk\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (4888 KB)...
OKAY [ 0.855s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 0.932s
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (4888 KB)...
OKAY [ 0.855s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 0.932s
Nothing works for me please help
C:\android-sdk\sdk\platform-tools>fastboot oem gencheckpt
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(735): error 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(735): error 2
(bootloader) [DISPLAY_ERR] read sp1 partition fail!!!
(bootloader) [SD_HW_ERR] read data fail in CMD17
(bootloader) CMD17: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(735): error 2
(bootloader) [SD_HW_ERR] read data fail in CMD17
(bootloader) CMD17: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(735): error 2
(bootloader) [ERR] Boot/Recovery image does not exist!!!
OKAY [ 0.403s]
finished. total time: 0.403s
C:\Android>fastboot oem gencheckpt
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(735): error 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(735): error 2
(bootloader) [DISPLAY_ERR] read sp1 partition fail!!!
(bootloader) [SD_HW_ERR] read data fail in CMD17
(bootloader) CMD17: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(735): error 2
(bootloader) [SD_HW_ERR] read data fail in CMD17
(bootloader) CMD17: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(735): error 2
(bootloader) [ERR] Boot/Recovery image does not exist!!!
OKAY [ 0.403s]
finished. total time: 0.403s
During this time my Phone goes white with 3 androind cartooons...(
Hello
Can anyone please help...
no reply please help guys
XDA guys
My thread is from tomorrow no reply yet ..
aren't developers and masters care for us..you guys are masters..
thats why i came here
Please help me
reply atleast please
Better to search and then ask here, or in the thread you linked.
Looks like you needed to:
- full wipe
- flash rom
- flash gapps
- flash boot.img manually
If you can't get it to boot, looks like you may need to the correct RUU for your device.
i did everything
As i have posted the details
can you suggest rom and kernel
and steps please
1. Look in the right place...
2. Find a rom which you like, read the features and last few pages of each thread to get an idea potential bugs.
3. Each Rom thread should have the install instructions written on first page. If they don't, search then ask in the thread itself. There are guides everywhere too...
Hello, I have a verizon htc one m7. I am rooted and s-off.
1: getvar info
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
2: In the the bootloader screen if I choose recovery the phone tries to load twrp screen goes to entering recovery goes black then the entering recovery screen comes back up and stays until I power down:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3: I have tried fastboot, flashify, rom toolbox pro and linux to flash twrp images. every one of them does so without error, yet I can not get into twrp. The md5 on every file I have tried to flash checked out ok.
4: I installed the ruu from dottat kitkat 4.4.2 and 4.4.3 and installed the ruu version of twrp 2.7.0.8 and 2.7.1.12 and still recovery does not load. This is after installing an ruu and wipes the phone completely.
5:I have tried everything that has been suggested including running the commands from a linux terminal.
If anybody knows how to fix this please help!
vaping redhead said:
Hello, I have a verizon htc one m7. I am rooted and s-off.
1: getvar info
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
2: In the the bootloader screen if I choose recovery the phone tries to load twrp screen goes to entering recovery goes black then the entering recovery screen comes back up and stays until I power down:
3: I have tried fastboot, flashify, rom toolbox pro and linux to flash twrp images. every one of them does so without error, yet I can not get into twrp. The md5 on every file I have tried to flash checked out ok.
4: I installed the ruu from dottat kitkat 4.4.2 and 4.4.3 and installed the ruu version of twrp 2.7.0.8 and 2.7.1.12 and still recovery does not load. This is after installing an ruu and wipes the phone completely.
5:I have tried everything that has been suggested including running the commands from a linux terminal.
If anybody knows how to fix this please help!
Click to expand...
Click to collapse
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
jpradley said:
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
Click to expand...
Click to collapse
they are in zip format and can be downloaded from dottat thread in the developer section. you use the command fasboot flash zip "filename"
http://forum.xda-developers.com/verizon-htc-one/development/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643
http://forum.xda-developers.com/showthread.php?t=2765784
vaping redhead said:
they are in zip format and can be downloaded from dottat thread in the developer section. you use the command fasboot flash zip "filename"]
Click to expand...
Click to collapse
OK, thanks.
But what's wrong with the file format that most everyone uses for a recovery installation, which isn't a *zip file, but a *img file?
jpradley said:
OK, thanks.
But what's wrong with the file format that most everyone uses for a recovery installation, which isn't a *zip file, but a *img file?
Click to expand...
Click to collapse
It is my understanding that img files can be flashed directly from fastboot or flashify etc. the zip file contains the image file and also a txt file and can only be flashed while your phone is in ruu mode "fastboot oem rebootRUU"
since there is 2 files that it why it is zipped. the txt file contained in there is the istructions that tell the rom update utility how to flash the enclosed recovery image file.
jpradley said:
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
Click to expand...
Click to collapse
Fastboot erase cache
Then flash your recovery again and see what you have.
dottat said:
Fastboot erase cache
Then flash your recovery again and see what you have.
Click to expand...
Click to collapse
I have tried that command, it does not solve recovery not loading. Trust me I have tried every suggestion I can find on the internet and nothing solves this. I am hoping someone out there has knowledge of exaclty how the recovery partition works because at this point it would appear that the recovery partition on my phone is either not being written to or is corrupted.
vaping redhead said:
I have tried that command, it does not solve recovery not loading. Trust me I have tried every suggestion I can find on the internet and nothing solves this. I am hoping someone out there has knowledge of exaclty how the recovery partition works because at this point it would appear that the recovery partition on my phone is either not being written to or is corrupted.
Click to expand...
Click to collapse
When you flash the ruu mode twrp put a -w on the end of the command.
dottat said:
When you flash the ruu mode twrp put a -w on the end of the command.
Click to expand...
Click to collapse
I will try. Here are the results
c:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
c:\adb>fastboot flash zip M7_RUU_TWRP.zip -w
target reported max download size of 1514139648 bytes
sending 'zip' (9360 KB)...
OKAY [ 1.059s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,10
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,30
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,61
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,87
(bootloader) [RUU]UZ,recovery,98
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
OKAY [ 3.179s]
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 4.250s
Revovery still does not load.
vaping redhead said:
I will try. Here are the results
c:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
c:\adb>fastboot flash zip M7_RUU_TWRP.zip -w
target reported max download size of 1514139648 bytes
sending 'zip' (9360 KB)...
OKAY [ 1.059s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,10
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,30
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,61
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,87
(bootloader) [RUU]UZ,recovery,98
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
OKAY [ 3.179s]
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 4.250s
Revovery still does not load.
Click to expand...
Click to collapse
Failed (remote not allowed)
Is a sure sign that something isn't set up right for flashing to the device.
It will never work if that is the result in terminal.
Are you using Usb 2.0 and the original data cable that is meant for the device?
I think you probably never successfully flashed any recovery.
I would advise trying a cable meant for this device.
santod040 said:
Failed (remote not allowed)
Is a sure sign that something isn't set up right for flashing to the device.
It will never work if that is the result in terminal.
Are you using Usb 2.0 and the original data cable that is meant for the device?
I think you probably never successfully flashed any recovery.
I would advise trying a cable meant for this device.
Click to expand...
Click to collapse
I am using the htc cable that came with the phone. I will double check that I am using USB 2.0 and try a different cable.
I also noticed wihen flashing with rom toolbox pro is says successful yet also says #error: cannot locate recovery partition
Is it possible my recovery partitiion is not there?
I just tried several cables including the the one from htc. I also made sure I was using a usb 2.0 port. I still get the failed(remote not allowed)
Thank you for the help btw.
Hi, I think I have figured this one out. I changed my phone from blue to red. Verizon only offers silver or blue. Anyway I thought I might have damaged my motherboard, So I bought a silver verizon htc one off ebay with a cracked screen. (easy fix). So I swapped the hardware from the silver to my red and with a new board in the red shell twrp does not load. However my old board wich twrp would not load on is now in the silver shell and twrp now loads. Bottom line the red shell is the problem.
vaping redhead said:
Hi, I think I have figured this one out. I changed my phone from blue to red. Verizon only offers silver or blue. Anyway I thought I might have damaged my motherboard, So I bought a silver verizon htc one off ebay with a cracked screen. (easy fix). So I swapped the hardware from the silver to my red and with a new board in the red shell twrp does not load. However my old board wich twrp would not load on is now in the silver shell and twrp now loads. Bottom line the red shell is the problem.
Click to expand...
Click to collapse
Update. The red shell is 100% to blame for recovery software not loading. I did some more tinkering with two m7 motherboards and in a stock verizon silver shell twrp loads. Both board when in the red shell, twrp does not load.
If anyone out there was thinking of converting their blue or silver verizon m7 to a different color. Be warned that your recovery software will probably not load once you transfer the hardware over to the new shell.
I guess if I want a red htc one that twrp works on, I have to get a m8
vaping redhead said:
Update. The red shell is 100% to blame for recovery software not loading. I did some more tinkering with two m7 motherboards and in a stock verizon silver shell twrp loads. Both board when in the red shell, twrp does not load.
If anyone out there was thinking of converting their blue or silver verizon m7 to a different color. Be warned that your recovery software will probably not load once you transfer the hardware over to the new shell.
I guess if I want a red htc one that twrp works on, I have to get a m8
Click to expand...
Click to collapse
Or just.... Paint it with a good quality modeling paint (like you buy for model cars, boats, etc). It is durable and lasts if you know how to coat it correctly.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Doesn't seem to me that you solved the initial problem, just found a work around for it. I have the same problem with my phone not accepting the stock recovery for what ever reason. It will, however, accept the TWRP recovery, but this doesn't do me any good wrt warranty returns. before I S-On and Lock it, I need to have the stock recovery installed.
gryghst72 said:
Doesn't seem to me that you solved the initial problem, just found a work around for it. I have the same problem with my phone not accepting the stock recovery for what ever reason. It will, however, accept the TWRP recovery, but this doesn't do me any good wrt warranty returns. before I S-On and Lock it, I need to have the stock recovery installed.
Click to expand...
Click to collapse
Have you tried ruu? That should flash the stock recovery and everything else stock. Need to ruu when you s-on to ensure everything is okay before turning secure flag on.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Have you tried ruu? That should flash the stock recovery and everything else stock. Need to ruu when you s-on to ensure everything is okay before turning secure flag on.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
I have RUU'd the following and in different orders:
5.28.605.2_NoBoot-IMG_firmware.zip
VZW.M7.5.28.605.2.PN0731IMG.zip
as well as "fastboot flash recovery 5.28.605.2_Stock_recovery.img"
all with a scattering of "fastboot erase cache".
The flash says it is successful, but when I boot to recovery, the screen graphics are garbage and when not garbage, it's the ! droid after the usual 15-20 sec blank screen. When I flash TWRP either via flash recovery or RUU that takes and works just fine. But this obviously isn't a "back to stock" set up.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3899mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.164s
Thoughts?
gryghst72 said:
I have RUU'd the following and in different orders:
5.28.605.2_NoBoot-IMG_firmware.zip
VZW.M7.5.28.605.2.PN0731IMG.zip
as well as "fastboot flash recovery 5.28.605.2_Stock_recovery.img"
all with a scattering of "fastboot erase cache".
The flash says it is successful, but when I boot to recovery, the screen graphics are garbage and when not garbage, it's the ! droid after the usual 15-20 sec blank screen. When I flash TWRP either via flash recovery or RUU that takes and works just fine. But this obviously isn't a "back to stock" set up.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3899mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.164s
Thoughts?
Click to expand...
Click to collapse
Have you tried the 2.x.y.z signed ruu in santod's stock Rom/firmware thread? Unsigned ruus are good, but sometimes a signed, official ruu gets the job done that unofficial ones can't.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Have you tried the 2.x.y.z signed ruu in santod's stock Rom/firmware thread? Unsigned ruus are good, but sometimes a signed, official ruu gets the job done that unofficial ones can't.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Is the signed one located here? I have not only because I have not read that one can go backwards, especially that far back. Can this be done successfully? What are the risks? Does the signed RUU contain all he necessary files to restart after the flash, are there any supporting flashes necessary (HBOOT, Recovery, Radios, etc.) Is this a viable solution or a shot in the dark which could brick the device?
Thanks for the on-going troubleshooting. I'm not trying to be a pain, just being careful since I am unfamiliar with the bootload/security features build into the system.
---------- Post added at 03:33 PM ---------- Previous post was at 02:58 PM ----------
I tried to RUU flash the 1.10.605.10 version .. here was my result:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Android>fastboot flash zip PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178274 KB)...
OKAY [ 44.569s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 51.044s
C:\Android>fastboot flash zip PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178274 KB)...
OKAY [ 44.632s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 51.075s
C:\Android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.031s
Well, that didn't do anything, good or bad. Just didn't take and phone operates just fine as a phone, but still no recovery image, stock or otherwise.
Downloading 2.x.y.z signed version now. Will report the results after flash attempt.
Same results:
C:\Android>adb reboot-bootloader
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Android>fastboot flash zip RUU_2_10_605_1.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1232586 KB)...
OKAY [ 41.931s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 48.420s
Hi guys,
I have read a lot of threads on this and other forums and i didnt find any way out for my device.
I have a problem with my HTC One M8 AT&T, bootloader is unlocked, S-ON, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
Its friends phone and he told me it completely discharged and booted to hboot and wouldnt boot to android. i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
Here is data about the phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *******HIDDEN******
(bootloader) imei: *********HIDDEN***********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BOOTLOADER picture
fastboot devices works:
C:\sdk-tools>fastboot devices
HT45YWM01368 fastboot
1) i tried this in fastboot:
C:\adb>fastboot flash recovery C:\adb\openrecovery-twrp-2.8.5.0-m8.img
target reported max download size of 1830727680 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.438s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.500s
2) flashing stock recovery via fastboot( i dont know if i had the right one):
C:\adb>fastboot flash recovery C:\adb\recovery.img
target reported max download size of 1830727680 bytes
sending 'recovery' (14109 KB)...
OKAY [ 1.262s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.277s
3) also tried bootloader lock for RUU- failed, it rebooted( cca 1 min to reboot) , and i can hear it connects and disconnects to pc with screen off about 5 times before booting to bootloader:
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) [DEBUG] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [PG_ERROR] htc_pg_hdr_get(118):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(170):
(bootloader) htc_pg_hdr_get failed
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.244s
4) tried official HTC KitKat 4.4.4. RUU.exe but failed:
5) tried bootable RUU over sd card- failed at "parsing...." command
i am 100% sure it isnt about corrupted files or wrong md5 sums or usb drivers not working, i tried 5 times every step i described here just to be sure( ofc i will try everything from the beginning if you have some ideas).
last thing to mention:
i found 2 threads with "similar" problems:
first one, second where @redpoint73 told them a solution may be formatting through Windows device manager. I searched for cca 3 hours in device manager and disk management etc- didnt find a solution.
maybe formatting through fastboot could be a solution( format[:[<fs type>][:[<size>]] <partition> format a flash partition. ), but my knowledge about cmd/fastboot/htc partitioning is way below that point.
Can please anyone help me? Thanks in advance
Anyone guys?
mato123 said:
Anyone guys?
Click to expand...
Click to collapse
Not really got much input I'm sorry, but this doesn't look good at all bootloader) version-baseband: INVALID_VER_INFO you can see this all along your bootloader screen shot, id say the phone is dead, baseband chip problem.
your drivers on your computer also look to be installed wrong.
171 RUU error is a USB connection problem, which again links back to your drivers, should say MyHTC
also which RUU are you using, because your version main is missing ?
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?).