Related
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
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
I have been given a 32gb us model which is stuck in bootloader i have tried everything and all fails.
Code:
fastboot getvar all
Code:
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT43SWM00546
(bootloader) imei: 35
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: -0.000s
htc_fastboot finished. total time: 0.047s
Unable to lock the boot loader to try flash RUU
Code:
fastboot oem lock
Code:
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 2082
(bootloader) [SD_ERR] sd_read_sector: read sector failed (2082 2)
(bootloader) [PG_ERROR] htc_pg_hdr_get(118):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(170):
(bootloader) htc_pg_hdr_get failed
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 262656
(bootloader) [SD_ERR] sd_read_sector: read sector failed (262656 2)
(bootloader) [PG_ERROR] htc_pg_hdr_get(118):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(170):
(bootloader) htc_pg_hdr_get failed
(bootloader) Update pg2fs_sec_recovery fail (-1)
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 11.170s
htc_fastboot finished. total time: 11.232s
Is it worth trying anything else?
Try to flash this ruu with unlocked bootloader, I'm not sure It'll work but I think you have the developer edition which comes with an unlocked bootloader.
https://androidfilehost.com/?fid=24269982087015187
lucyr03 said:
Try to flash this ruu with unlocked bootloader, I'm not sure It'll work but I think you have the developer edition which comes with an unlocked bootloader.
https://androidfilehost.com/?fid=24269982087015187
Click to expand...
Click to collapse
The RUU exe file runs for a second i then accept the eula, After that nothing happens. The phone is connected to my pc also via fastboot usb.
David_UK said:
The RUU exe file runs for a second i then accept the eula, After that nothing happens. The phone is connected to my pc also via fastboot usb.
Click to expand...
Click to collapse
Get the ROM.zip from the exe and flash it by htc_fastboot.exe
lucyr03 said:
Get the ROM.zip from the exe and flash it by htc_fastboot.exe
Click to expand...
Click to collapse
Unable to flash
Code:
fastboot oem rebootRUU
Code:
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.041s]
finished. total time: 10.041s
htc_fastboot finished. total time: 10.096s
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>
Also unable to flash twrp
Code:
fastboot flash recovery twrp-3.2.1-0-m8.img
Code:
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot flash recovery twr
p-3.2.1-0-m8.img
htc_fastboot v3.0.9.2 (2015-05-29)
sending 'recovery' (20298 KB)...
OKAY [ 2.437s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 12.539s
htc_fastboot finished. total time: 12.609s
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>
I think its F***ed
Yeah, it seems like a dead nand.
David_UK said:
i have tried everything and all fails.
Click to expand...
Click to collapse
This statement doesn't tell us anything. It's worth listing the things you tried to flash, and the specific results for each. Otherwise, we waste your time and ours, as we guess or assume what you tried and didn't try.
Did you try to flash custom recovery TWRP? If so, which version number? Did you get an error message, or what was the failure mode or other results?
redpoint73 said:
This statement doesn't tell us anything. It's worth listing the things you tried to flash, and the specific results for each. Otherwise, we waste your time and ours, as we guess or assume what you tried and didn't try.
Did you try to flash custom recovery TWRP? If so, which version number? Did you get an error message, or what was the failure mode or other results?
Click to expand...
Click to collapse
I flashed twrp 3.2.1-0 this was the output
Code:
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot flash recovery twr
p-3.2.1-0-m8.img
htc_fastboot v3.0.9.2 (2015-05-29)
sending 'recovery' (20298 KB)...
OKAY [ 2.437s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 12.539s
htc_fastboot finished. total time: 12.609s
I haven't tried an ruu zip from sd card yet as i don't know which one to flash
I just tried ruu from sdcard and this is the result
David_UK said:
I haven't tried an ruu zip from sd card yet as i don't know which one to flash
Click to expand...
Click to collapse
The RUU which corresponds with your current firmware number (main version in getvar: 6.12.401.4) is here:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You can try to flash using htc_fastboot per the instructions, or SD card method.
If you can't get the RUU to work, relock the bootloader, or flash TWRP, I agree that it's probably emmc failure.
Help me please.
Help me please. Is this also a brick?
Code:
fastboot getvar all
Code:
C:\Users\Алекс>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH***
(bootloader) imei: 35***
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Finished. Total time: 0.031s
Unable to lock the boot loader to try flash RUU
Code:
fastboot oem lock
Code:
C:\Users\Алекс>fastboot oem lock
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure:
cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure:
cmd_id = 0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (Status read failed (Unknown error))
Finished. Total time: 1.252s
Is it worth trying anything else?
Alex IvanoVVV said:
Help me please. Is this also a brick?
Click to expand...
Click to collapse
Please don't post same question to multiple threads. It is against forum rules to do so, as it clutters up the forum, and makes it very confusing for those trying to help you.
I've tried to help you in one of the 3 threads you posted in. So go look for it (now you see one of the reasons why cross posting is not a good idea?).
Hello. I think I messed it up trying to root my Motorola G10. I'm stuck on a bootloop as you can see in the picture.
{
"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"
}
I've tried to recover it with all kinds of assistants, but they all fail. I've also tried to flash it with fastboot, but it turns out that oem is not enabled, and if I try to unlock it with fastboot commands I just get the "Check OEM unlocking in Android settings >Developer options" message. Obviously, I cannot access my phone so I cannot check that option. After searching for many hours in the forums, the only thing I haven't tried is EDL mode, but I can't manage to set it on either.
I don't know what else to do, so any help will be welcome. Thanks.
luisgb78 said:
I've tried to recover it with all kinds of assistants
Click to expand...
Click to collapse
What does that mean? Which assistants? There is only one that I know of.
Well. First I tried with "Rescue and Smart Assistant", suggested by Motorola support team, but it fails. At this point I don't really know if I have to recover it, flash it, factory reset it or what. I also tried other software like Kingo Root, RSD Lite, but I don't get anywhere.
In case this helps, this is what i get with >fastboot getvar all:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-capri_retail-7d6811cfd7-201230
(bootloader) product: capri
(bootloader) board: capri
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX hC9aP3 RV=08 PV=01 FV=0000000031303030
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5-M8=06 05 00 11
(bootloader) cpu: SM_KAMORTA 1.0
(bootloader) serialno: ZY32C2KNPT
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: CEC0747D
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804464640
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 03-28-2021
(bootloader) sku: XT2127-2
(bootloader) carrier_sku: XT2127-2
(bootloader) battid: SB18C85291
(bootloader) battery-voltage: 4140
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: reteu
(bootloader) ro.build.fingerprint[0]: motorola/capri_retailen/capri:11/R
(bootloader) ro.build.fingerprint[1]: RB31.Q1-3-16-2/67641:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-01800-KAMORTA.0
(bootloader) version-baseband: HAK10_18.534.02.63R CAPRI_EUAPEMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.19.136-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Wed D
(bootloader) kernel.version[4]: ec 30 02:41:02 CST 2020
(bootloader) git:abl: MBM-3.0-capri_retail-7d6811cfd7-201230
(bootloader) frp-state: no protection (0)
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SP69A6PCNN
(bootloader) primary-display: tm_ili9882n_652_vid_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.399s
When I try to follow tutorials that I've found online I always run into the OEM problem. If I try to unlock it with fastboot this is what I get:
>fastboot oem unlock
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.092s
My initial plan was to root the phone, but at this point the device is useless. I don't know what should I do next to fix it or go back to its original state. Any help will be apreciated.
Hi. This is what Rescue and Smart Assistant shows:
It looks like bootloader is locked and I can't unlock it because OEM is not checked:
>fastboot oem unlock xxxxxxxxxxxxxxxxxxxxxxx
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.261s
>fastboot flashing unlock
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.307s
Is there anything I can do?
Anybody knows how to start EDL mode in a Motorola G10?
Thanks.
luisgb78 said:
It looks like bootloader is locked and I can't unlock it because OEM is not checked:
>fastboot oem unlock xxxxxxxxxxxxxxxxxxxxxxx
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.261s
>fastboot flashing unlock
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.307s
Is there anything I can do?
Click to expand...
Click to collapse
Ik I am very late, but did you try flashing the stock firmware?
Hi,
I am trying to restore my data partition (photos/videos) from my bricked Asus Zenfone Zoom S (ZE553KL). Phone suddenly turned off and that's all. Completely no contact - it doesn't even try to boot, screen is black - maybe some graphic chip corrupted (because screen module is working - I checked it on another device).
or maybe some memory flash corruption. I don`t know.
Fortunately I have access to fastboot (screen is still black but I can see new device on PC).
I know that fastboot can not dump/backup data from any partition.
The only way to do that is to install TWRP and later switch to recovery TWRP mode by fastboot boot/flash recovery. But I can`t do that. Phone was never unlocked so I can`t flash or boot any external images.
I don`t have access to OEM recovery - it doesn`t start. But it is useless at this time because it doesn't have adb enabled.
I know that there is another option - EDL or Emergency DownLoad Mode.
It can be accessed by:
ADB, Fastboot or manually by short the test points on device’s mainboard
ADB- I dont have access to it,
fastboot - I tried this
fastboot.exe reboot-edl
rebooting into edl...
OKAY [ 0.009s]
finished. total time: 0.011s
but it doesn`twork. I don`t see any new com port on device manager
Third option is to short the test points. I have searched the entire internet but cannot find the information which points I should shorten for ZE553KL.
Do you have any information about ZE553KL?
{
"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"
}
fastboot.exe getvar all
(bootloader) EMCP:4
(bootloader) RFsku:WW
(bootloader) project:ZE553KL
(bootloader) cputype:8953
(bootloader) version:0.5
(bootloader) cpusn:699086081
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3955000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x10000000
(bootloader) partition-type:APD:ext4
(bootloader) partition-size:APD: 0x14000000
(bootloader) partition-type:ADF:ext4
(bootloader) partition-size:ADF: 0x2000000
(bootloader) partition-type:asdf:ext4
(bootloader) partition-size:asdf: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x8000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd5f7f7e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xf0000000
(bootloader) serialno:H9AZCXXXXXXXXX
(bootloader) kernel:lk
(bootloader) product:MSM8953
all:
Finished. Total time: 1.401s
fastboot.exe oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) Sysconf ssn: H9AZCXXXXXXXXX
(bootloader) Sysconf adb enable: 1
(bootloader) Sysconf reboot reason: 0
(bootloader) Sysconf isn: N0CY1729MB00xxxx
OKAY [ 0.438s]
Finished. Total time: 0.442s