Hi, first post here and its a plea for help, most probably the same way quite a few people find their way onto here!
My wife has a HTC one mini and it will power on and go straight to the "Fastboot" screen, it does this constantly. if you select restart it ends up in exactly the same place, same with the power button.
The phone had been unlocked with TWRP recovery about 6 months ago. it was flashed with a stock ROM
This has happened before a couple of times but after a couple of restart attempts it fired up normally and went into normal operation, after a little research we started to believe that it had a sticking volume down button, but now no amount of squeezing and resetting will get it to power up this time
If i select to go into recovery the screen goes blank for a split second and comes right back onto the "Fastboot" screen.
When I connect the phone to a computer the phone goes into "Fastboot USB" and the computer beeps to say something has been connected, HTC sync fires up but says no phone is connected.
With the phone plugged into the computer I can use fastboot to see it is connected but adb does not see it:
Code:
C:\adb>fastboot devices
SH3ACWA****** fastboot
C:\adb>adb devices
List of devices attached
C:\adb>
I have tried to reflash the recovery, I have tried CWM TWRP and the Stock recovery but all do this:
Code:
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 800227328 bytes
sending 'recovery' (8572 KB)...
OKAY [ 1.065s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.218s
C:\adb
I have used the command "fastboot oem boot" and this makes the phone show a white screen with the scateboarding androinds in the centre and gives:
Code:
C:\adb>fastboot oem boot
...
(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) [DISPLAY_ERR] read sp1 partition fail!!!
(bootloader) [ERR] Cmd17 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 CMD17
(bootloader) CMD17: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) [ERR] Cmd17 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 CMD17
(bootloader) CMD17: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) [ERR] Boot/Recovery image does not exist!!!
OKAY [ 0.407s]
finished. total time: 0.409s
C:\adb>
In case this is of any help:
Code:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3ACWA*****
(bootloader) imei: 355866056******
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4274mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-871d213f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.230s
I have also tried to fastboot flash a new ROM onto the phone (one that will not wipe the SDcard and all data), this also fails:
Code:
C:\adb>fastboot flash rom mini.zip
target reported max download size of 800227328 bytes
sending 'rom' (36992 KB)...
OKAY [ 2.731s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 8.164s
The rom was from the thread http://forum.xda-developers.com/showthread.php?t=2659109 - I have renamed the zip out of lazyness so there is less to type in CMD prompt!
I have loaded up a FUU and this seems to work, it will recognise and bring up the software number of the phone and bring up the option to update it - I haven't gone through with this as it will wipe all of the SDcard data and this against what I am trying to achieve.
I would like to get access to the phone to extract the data, whether that be by mounting it and getting the data via comuter or getting it working via another method. We have a new Mini 2 as an upgrade for this phone so it does not neccesarily need to work completely.
Any help anyone can give will be greatly appreciated,
It may be a silly idea but have you tried flashing the file without the spaces in the file name? Ie fastboot flash rom_mini.zip (you'd have to change the file name to reflect that obviously), but I've had it happen on my nexus before a recovery just wouldn't flash because of the spaces in the zip's file name. It's worth a shot. If it still fails then I'd look into that signature verification error you're getting.
Have you managed to solve the issue? I in exactly the same situation as you are/were.
I'm having similar issues with a One Mini I got off of Craigslist for $40. For me the biggest issue (as far as I can tell) is that the security is still enabled (S-ON) and it appears you have a similar issue ("security: on" result from your "getvar" command). From what I've found on the forums here flashing the original ROM should bring it back to life (which you tried) but it didn't work for me either. I should mention, HTC drivers installed (of course ), fastboot will recognize it but adb won't.
The bootloader screen for me.
Code:
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT—2.22.0000
OS—4.09.631.2
eMMC—boot 1024MB
Jun 23 2014, 13:57:59.0
FASTBOOT USB
etc etc...
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.631.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3B1WA*****
(bootloader) imei: 3564820507*****
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5822000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3850mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.553s
A bit of an update with a couple things I've tried. I was thinking that being unable to find my device with adb could be messed up drivers, and found someone else on the forums that had a post precisely about this [http://forum.xda-developers.com/showpost.php?p=60834905&postcount=7]. Using Ubuntu is apparently an option, and as I dual-boot Ubuntu 14.04 LTS and Win7 x64 I figured I would give it a shot. Followed 'jollywhitefoot's' instructions on installing the necessary repositories, and then fastboot and adb. I could detect the device using 'sudo fastboot devices' but adb still wouldn't recognize it ('sudo adb devices'), returning a blank list. I also attempted to install the latest TWRP, to no avail. Perhaps the person who messed up the phone in the first place never enabled USB debugging.
If anyone out there has an idea of what I'm missing here, I would appreciate a little help. If not, I'll keep plugging away and see what else I can find to try. Thanks!
Code:
[email protected]********:~$ sudo fastboot flash recovery /usr/bin/twrp.img
target reported max download size of 800227328 bytes
sending 'recovery' (11460 KB)...
OKAY [ 1.636s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.777s
-- EDIT 1 --
I should add a few details. I've attempted to unlock the phone using HTCdev from both Windows and now Ubuntu and I supposedly get a valid unlock but never do see the bootloader screen change to reflect that (always stays at '*** LOCKED ***'). I'll post one of the sample outputs below.
Code:
[email protected]********:~/Downloads$ sudo fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800227328 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.155s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.161s
-- EDIT 2 --
I've tried to flash a few different recoveries, in the hope that one would work. Unfortunately I couldn't find the stock recovery anywhere, I'm guessing that would have the highest chance of working. The three I tried were from here [http://forum.xda-developers.com/htc-one-mini/development/mega-index-roms-recoveries-mods-kernels-t2835180]. I also grapped a dmesg dump, it appears that something with the "SD card" (I know the Mini doesn't have one, but that's what it reports it's storage as) is causing problems, though I'm not sure if this is due to a lack of a formatted partition, or rather super-aggressive writes and thus failing memory.
Code:
(bootloader) [6:9:29.394207] fastboot_command:[erase:cache]
(bootloader) [6:9:29.403677]
(bootloader) eMMC Manufacturer ID: 15
(bootloader) [6:9:29.415209] [ERR] Cmd35 polling status timed out, MCI_ST
(bootloader) ATUS: 0x4C0000
(bootloader) [6:9:29.419677] [ERR] sdcc_command: sdcc_poll_status error,
(bootloader) rc: 2
(bootloader) [6:9:29.421825] sdcc_erase, CMD35 fail
(bootloader) [6:9:29.425520] emmc_erase(2704): sd_erase_sector failed!
Buzz84, I think it's apparent now that my problem could be quite different than yours, I shouldn't have opened up your thread again but I originally thought we had very identical problems!
Anyone made any headway here? My One Mini was sitting in a drawer for months and now that my primary phone got stolen, I need it. Same problem as the others. It just goes right to fastboot and refuses to do anything else. Here's my info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.111.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37G*****
(bootloader) imei: ********
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Side note: Does anyone know how to unlock the bootloader without access to the OS? The HTC unlock token requires access to the OS to confirm via pop up.
Solution found
In case anyone still encounter this problem, here's a solution.
everybody has the same cure which is put the phone into constant boot loop so that in between loops the battery takes a little bit of a charge until eventually it has enough, i sorted mine out by plugging in the phone then wrapping a strong elastic band around the bottom of phone and the power button which will keep the power button pressed and the phone will keep looping until it gets enough charge, once you see the htc logo release the band before it goes into another loop.
Click to expand...
Click to collapse
htc mini loop
Hi to all,i just waste 10 hours looking for solution so for now i dont have no luck. Try it all all for one tool,windroid tool,i try from fast boot to just make small step but NO..... htc mini is stuk in fastboot mode,pc see htc as other device tru cmd -powershell everything i try had eror or remote eror. With windroid and htcdev page i got unlock-bin file and after doing steps when they say that my bootlader is unlock it is not. tru cmd the same with unlock bin file. I dont have idea how to bypass that signature chek. if someone have idea Imglad to hear it.
Related
Help me!!!
The phone have been s-off and unlock bootloader before.
But after bricked, I want to flash official RUU to fix it,
So I run fastboot oem lock , the bootloader was locked again and can't be be unlock again ,becuase the hboot version has changed.
Current status:
Screen is not bright ,but plug my phone with usb can list unknown devices. and I can use fastboot command to list devices. but can't flash any files.
F:\signed>fastboot flash zip PL99IMG.zip
sending 'zip' (488 KB)...
OKAY [ 0.025s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.035s
F:\signed>fastboot devices
???????????? fastboot
F:\signed>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.41.0000
(bootloader) version-baseband: 1.01.10.0201
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.070s
Thanks
If you can get into fastboot like you are. Your not hard bricked.
To flash the RUU like you are doing. In fastboot do the following commands...
Fastboot oem rebootRUU
Fastboot flash zip PL99IMG.zip
That should work.
Sent from my HTC6435LVW using Tapatalk 2
Flyhalf205 said:
If you can get into fastboot like you are. Your not hard bricked.
To flash the RUU like you are doing. In fastboot do the following commands...
Fastboot oem rebootRUU
Fastboot flash zip PL99IMG.zip
That should work.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
not work
Fixed by RIFF box JTAG
Thanks
Help, HTC butterfly bricked,blocked in fastboot
Hello everyone,
asking for your help because my htc butterfly is stuck in fastboot after the procedure to bring it back to stock rom.
Unfortunately I could not find the ruu.exe and tried as indicated but unfortunately they are now in this situation.
Now the phone is relocked and S-ON, is there any way to replace it?
thanks to those who help me.
help
vjeson said:
not work
Fixed by RIFF box JTAG
Thanks
Click to expand...
Click to collapse
can you make downgrade from 1.29 ota to 1.15 with riff box?
I am locked and I can sim unlock! please give more details!
thank you
vjeson said:
Help me!!!
The phone have been s-off and unlock bootloader before.
But after bricked, I want to flash official RUU to fix it,
So I run fastboot oem lock , the bootloader was locked again and can't be be unlock again ,becuase the hboot version has changed.
Current status:
Screen is not bright ,but plug my phone with usb can list unknown devices. and I can use fastboot command to list devices. but can't flash any files.
F:\signed>fastboot flash zip PL99IMG.zip
sending 'zip' (488 KB)...
OKAY [ 0.025s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.035s
F:\signed>fastboot devices
???????????? fastboot
F:\signed>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.41.0000
(bootloader) version-baseband: 1.01.10.0201
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.070s
Thanks
Click to expand...
Click to collapse
you're have soff, are you chaged cid? with stock rom you're need write cid (your CID of stock rom) , flash FW and get token code again (fastboot oem get_identifier_token)
after unlock bootloader, you can flash stock rom.
Junior Member - OP :
How can you Fixed by RIFF box JTAG
no JTAG for HTL21...
can you help me..
I Have the same problem as you..
bright screen (blank), fastboot ok..
but failed..
please help me..
Thanks.
vjeson said:
Help me!!!
The phone have been s-off and unlock bootloader before.
But after bricked, I want to flash official RUU to fix it,
So I run fastboot oem lock , the bootloader was locked again and can't be be unlock again ,becuase the hboot version has changed.
Current status:
Screen is not bright ,but plug my phone with usb can list unknown devices. and I can use fastboot command to list devices. but can't flash any files.
F:\signed>fastboot flash zip PL99IMG.zip
sending 'zip' (488 KB)...
OKAY [ 0.025s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.035s
F:\signed>fastboot devices
???????????? fastboot
F:\signed>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.41.0000
(bootloader) version-baseband: 1.01.10.0201
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.070s
Thanks
Click to expand...
Click to collapse
1. Download firmware from here:
https://mega.co.nz/#!pEVXGZ6K!auhgoO81DzNQduWfJPQJ-lBV6g29PL6wAOEvpYsm1Hk
2. On fastboot, flash this firmware
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip firmware1.55_cid044.zip
fastboot reboot-bootloader
and see if you can manage from here.
Credits:
victor0888
---------- Post added at 02:01 PM ---------- Previous post was at 01:39 PM ----------
Try to download and flash a new/different firmware.
Alright, this is yet another wiped OS for an HTC ONE M7. I have spent DAYS trying to figure out a solution to this, but nothing has worked... Probably because I don't even know what the next step is.
BOOTLOAD SCREEN **
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.128.274.0909
OS-6.10.531.9
eMMC-boot 2048 MB
(todays date)
I have tried fastboot flashing the zip files for the OS and it shows this in command prompt.
C:\Users\JamesM\Desktop\adbfastboot\adbfastboot>fastboot flash zip OS.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1221704 KB)...
OKAY [ 44.790s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 44.853s
Basically, the phone was rooted and unlocked and I was installing cyanogenmod on it which failed and I deleted the system folder instead of doing a factory reset on it. It does not get past the HTC screen and I have attempted to flash zip files after attempting relocking and rebootRUU, which have all failed.. I have also tried the .exe RUU files. I am also feeling like there is a definite driver issue, since my computer used to show My HTC in the device manager and now it shows it in "other devices" as "One" and seems to be showing up as a disc drive. There honestly is not much that I can think of at the moment that I have not tried to get this going, youtube videos, hours of looking for similar issues, messing with things on my own to see if there is ANYTHING to do and nothing has worked. I am assuming that it has something to do with it being S-ON, but I have tried to change that with revone and it wouldn't flash through USB. Everything is wiped, but I have my bootloader and recovery... there has to be a way back from here..
This is my fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.10.531.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA39HW907463
(bootloader) imei: 355972057571995
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4328mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.069s
Seriously though, if anyone can help me with this that would be amazing. If there is any information needed, I will be around to update. I have installed CWM recovery v6.0.4.3 and also have TWRP v2.6.3.0.
SIDE NOTE*
I don't expect someone to spend a tremendous amount of time spelling things out for me, but if someone could give me a starting point... Like (Oh, it's probably drivers.. Or incorrect RUU)
Thanks again!
JamesM1027 said:
Alright, this is yet another wiped OS for an HTC ONE M7. I have spent DAYS trying to figure out a solution to this, but nothing has worked... Probably because I don't even know what the next step is.
BOOTLOAD SCREEN **
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.128.274.0909
OS-6.10.531.9
eMMC-boot 2048 MB
(todays date)
I have tried fastboot flashing the zip files for the OS and it shows this in command prompt.
C:\Users\JamesM\Desktop\adbfastboot\adbfastboot>fastboot flash zip OS.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1221704 KB)...
OKAY [ 44.790s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 44.853s
Basically, the phone was rooted and unlocked and I was installing cyanogenmod on it which failed and I deleted the system folder instead of doing a factory reset on it. It does not get past the HTC screen and I have attempted to flash zip files after attempting relocking and rebootRUU, which have all failed.. I have also tried the .exe RUU files. I am also feeling like there is a definite driver issue, since my computer used to show My HTC in the device manager and now it shows it in "other devices" as "One" and seems to be showing up as a disc drive. There honestly is not much that I can think of at the moment that I have not tried to get this going, youtube videos, hours of looking for similar issues, messing with things on my own to see if there is ANYTHING to do and nothing has worked. I am assuming that it has something to do with it being S-ON, but I have tried to change that with revone and it wouldn't flash through USB. Everything is wiped, but I have my bootloader and recovery... there has to be a way back from here..
This is my fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.10.531.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA39HW907463
(bootloader) imei: 355972057571995
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4328mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.069s
Seriously though, if anyone can help me with this that would be amazing. If there is any information needed, I will be around to update. I have installed CWM recovery v6.0.4.3 and also have TWRP v2.6.3.0.
Click to expand...
Click to collapse
Hi,
Here a dedicated help thread in your device section that you can ask about your issue in,
http://forum.xda-developers.com/showthread.php?t=2180425
Good luck!
I had given my sister this phone in June. It's unlocked, S-OFF, and was running CM11 with some custom recovery installed (was twrp, afair)
She had complained a few times about the phone directly booting to the bootloader/fastboot screen. A reboot from there usually worked after a couple of attempts.
Last week she dropped the phone and cracked the screen at the bottom. The display still works and the glass is still intact with some crack lines.
Yesterday, her battery drained completely and when she booted the phone after connecting the charger, it showed the bootloader/fastboot screen and wouldn't go beyond it.
fastboot devices detects the device.
flashing twrp 2.8.3 through fastboot fails with the following
target reported max download size of 800227328 bytes
sending 'recovery' (10575 KB)...
OKAY [ 1.800s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.948s
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.32.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT3B8WA02143
(bootloader) imei: 356482050812395
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3834mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f6d46eca
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.141s
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.061s
phone reboots to bootloader/fastboot again.
Reading through many threads on various forums suggests the eMMC might be dead. Is there any way to recover this phone?
Any help?
Hi, I have problem with my phone which is similar to the one described in this topic.
I have tried to S-off my One SV but I didn't update to the newest version of stock ROM which resulted in an error while running moonshine (it stopped after step 10 saying "Don't drink and moonshine" which was quite funny at first ).
Now the hboot says that the phone is unlocked and tampered.
I have tried flashing a stock rum using RUU exe file but it obviously failed.
Flashing .img files works fine (I have already tried to flash several boot.img's), I have even tried to flash new Venom ROM using TWRP recovery and it flashed fine, but the phone hangs on boot screen.
When I try to flash zip using fastboot it fails:
sending 'zip' (441985 KB)...
OKAY [ 19.654s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 31.754s
When I try to flash anything using PL80IMG.zip method the file is being read (I can see a progress bar) but nothing happens after that.
getvar all output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.01.0000
(bootloader) version-baseband: 0.12.40.00.14_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT32WTP00820
(bootloader) imei: 352803051180587
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3986mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.075s
I would appreciate any help Thanks
My Htc one mini keeps getting stuck in fastboot it is locked and s-off. Is there any way to fix it? I have searched forum for hours. And in 90% of threads phones are unlocked or tempered while mine is locked and have s-off.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.32.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT399W******
(bootloader) imei: 355866051******
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3912mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have tryed to unlock and after
C:\adb>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800227328 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.172s
Nothing happens on phone
Is there a way to fix it?
any ROM or Recovery, you can load Recovery via fastboot and give revone a try.
Wingman2K said:
any ROM or Recovery, you can load Recovery via fastboot and give revone a try.
Click to expand...
Click to collapse
When I try to flash recovery I get this:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 800227328 bytes
sending 'recovery' (9756 KB)...
OKAY [ 1.228s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.265s
I thought about "fastboot boot recovery.img" but did not work on mine to so never mind.
Can u get it the phone in RUU Update mode? "fastboot oem rebootRUU" and then flash a RUU or Firmware which match your region/phone via "fastboot flash zip Rom.zip"
Files for One Mini
Wingman2K said:
I thought about "fastboot boot recovery.img" but did not work on mine to so never mind.
Can u get it the phone in RUU Update mode? "fastboot oem rebootRUU" and then flash a RUU or Firmware which match your region/phone via "fastboot flash zip Rom.zip"
Files for One Mini
Click to expand...
Click to collapse
I have download RUU.exe and when I run it I get error 171
Also fastboot boot recovery.img does not work on mine.
When I try fastboot oem rebootRuu
I get this:
C:\adb>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.079s]
finished. total time: 0.083s
Ok this looks not good at all. Did you make the Phone s-off and Super-CID?
Did you eventually write some firmware.zip or other files in fastboot mode before that happened?
What did you do before it happen or was the phone on the charger on its own? Looks like an HW Problem.
Wingman2K said:
Ok this looks not good at all. Did you make the Phone s-off and Super-CID?
Did you eventually write some firmware.zip or other files in fastboot mode before that happened?
What did you do before it happen or was the phone on the charger on its own? Looks like an HW Problem.
Click to expand...
Click to collapse
I have bought phone this way... Never thought that HTC would have this issue.
Here there, @sanica, have you got it fixed? As I am not able to fix it on my dad's HTC One Mini M4 but it's S-ON. It's just stuck at bootloader screen and can only be switched to HBOOT and vice versa. Interestingly I have also damaged the volume buttons and they just don't work. Only power button can switch the modes from bootloader to HBOOT or HBOOT to bootloader.
I tried to flash recovery but it fails at bootloader signature checking.
I am not sure if any firmware is still there on it. I am not sure what RUU I need to use in that case.
I tried unlocking the bootloader in a normal fashion but the message exactly comes out as yours with (sending 0KB) and no prompt on the phone's screen.
Any help will be appreciated.
nothing new
Alo good afternoon I have a problem with my HTC min m4 it made an automatic update and it does not leave bootload and it extracts a following information *** locked **
M4_ul pvt ship s-on rl
Hboot-2.22.0000
Os-4.09.206.4
EMMC-boot 1024mb
Aug 13 2015.23: 05: 25.5
I ask you to return to normal boot
Wingman2K said:
Ok this looks not good at all. Did you make the Phone s-off and Super-CID?
Did you eventually write some firmware.zip or other files in fastboot mode before that happened?
What did you do before it happen or was the phone on the charger on its own? Looks like an HW Problem.
Click to expand...
Click to collapse
Hi, i have same problem, any help please