Related
{
"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"
}
hello
I have an HTC dezire Z and it stuck after power on at the BOOTLOADER screen , as you can see on the Picture .
and i want to know if there is anyway to solve this problem
i flashed it with this room [RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed] it was successful and i start using it normally but when i restart it , it stuck again on this screen
i know that the phone is working but there is something wrong with the boot sequence
i want to repair this phone to give it to my little brother
please Help
You have a S-ON Device, so you have to extract the boot.img from the zip file. Then enter fastboot modus on the phone and open fastboot in the command line on your pc, you also have to connect the phone via usb to the pc. Copy the boot.img to the folder where fastboot is.
Run "fastboot devices" and check if your device is listed.
Then run the command "fastboot flash boot boot.img", now the phone should boot.
akamarukiba said:
You have a S-ON Device, so you have to extract the boot.img from the zip file. Then enter fastboot modus on the phone and open fastboot in the command line on your pc, you also have to connect the phone via usb to the pc. Copy the boot.img to the folder where fastboot is.
Run "fastboot devices" and check if your device is listed.
Then run the command "fastboot flash boot boot.img", now the phone should boot.
Click to expand...
Click to collapse
thanks for your help ,
the problem is when i turn-on the phone it stuck on the BOOT screen as in the picture , AND the UP and DOWN button don't work at all
when i boot in the recovery mode ( power-on + down button ) i have the same problem the UP and DOWN keys don't work at all
the only way a can start the phone with is to plug it to the computer to execute FASTBOOT and type in the command line "FASTBOOT REBOOT" and it starts normally .
i followed the instruction carefully in http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD to get S-OFF and ROOT and ENG HBOOT with Gfree and i have a ROOTED device , and i installed clockwork recovery and a newer ROM (aosp-4.2.2) .
but the problem is always here , it's abnormal why my phone is not booting normally even if i flashed all things that can be flashed ???
View attachment 2445883
as you can see here
the Vol up and Down button are working normally expect in the BOOT Mode , i have tried to go to the recovery using ROM Manager App and it works by choosing " Reboot in recovery " , i have ClockworkMod Recovery v6.0.4.5 installed ,i did a test key to check if it's a hardware issue related to the keys, and am sure it's not due to that . keys are respnding perfectly .
if you have any suggestion or solution to that problem ????
i think it's related to the boot process :s
i typed "fastboot oem partition_test all" in the command line and i got :
C:\HTC>fastboot oem partition_test all
...
(bootloader) Testing Partition[merge_emmc]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[misc]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[hboot]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[sp1]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[wifi]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[recovery]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[boot]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[mfg]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[sp2]...
(bootloader) Can not allocate heap for flash_block_test
(bootloader) Testing Partition[pdata]...
(bootloader) Can not allocate heap for flash_block_test
OKAY [ 0.139s]
finished. total time: 0.141s
=============================================================
and for "fastboot oem check_emmc_mid"
C:\HTC>fastboot oem check_emmc_mid
...
(bootloader) Manufacturer ID, MID=45
(bootloader) eMMC should be Sandisk
OKAY [ 0.009s]
finished. total time: 0.009s
==============================================================
and also for "fastboot oem boot"
C:\HTC>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D087B50
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is HTC__102
(bootloader) setting->cid::HTC__102
(bootloader) serial number: SH0BMRT05576
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =465
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.13.04.19_M androidboot
(bootloader) .cid=HTC__102 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=HTC-GER androidboot.mid=PC1011000 androidboot.ke
(bootloader) ycaps=qwerty androidboot.mode=normal androidboot.serialno=SH
(bootloader) 0BMRT05576 androidboot.bootloader=0.84.2000 no_console_suspe
(bootloader) nd=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:493018 msec
FAILED (status read failed (Too many links))
finished. total time: 7.807s
Which radio do you have installed? I do not know if it is the problem, but it might be.
I am using this one: Vision_Radio_12.62.60.27_26.13.04.19
It workes well with Flinnys CM 10.1 Build 25 test4 and Nevergones CM 11.
Instruction and Radioimages are here:
http://forum.xda-developers.com/showthread.php?t=970809
akamarukiba said:
Which radio do you have installed? I do not know if it is the problem, but it might be.
I am using this one: Vision_Radio_12.62.60.27_26.13.04.19
It workes well with Flinnys CM 10.1 Build 25 test4 and Nevergones CM 11.
Instruction and Radioimages are here:
http://forum.xda-developers.com/showthread.php?t=970809
Click to expand...
Click to collapse
i have the same radio Radio_12.62.60.27_26.13.04.19
HLOOX said:
[...] and i installed clockwork recovery and a newer ROM (aosp-4.2.2) [...]ClockworkMod Recovery v6.0.4.5 installed
Click to expand...
Click to collapse
Sorry, I do not have any good ideas left, these are my last ideas, but I think they will not solve the problem.
Which AOSP-Rom are you using? Did you searched for similar issues with that rom, have you tried another rom yet? (Like the offical CM 7.2 for Vision?)
And you are using a ported ClockworkMod Recovery by NeverGone, I have not tested it yet, and I do not think it causes the problem, but there might me unkown issues with flashing. You could try the official one to flash the Rom.
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.7-vision.img
am using AOSP - Jelly Bean 4.2.2 - Build 16 ,
it's not caused by the ROM or by the ClockworkMod Recovery , because this problem appeared when i were using the phone with his original shipped ROM .
and to solve the problem i first tried to RUU shipped ROM file , the problem consist .
the problem was here bofore i flashed anything , i flashed the HBOOT and RADIO and changed the ROM to solve the problem but noting works with me to solve this problem .
I have a solution that you Should try...
You need to download proper RUU ... the android 2.2 PC10.img thing...I don't remember the name..
No doubt you will return to stock ...but after re root 100% it will solve your problem!!
Sent from my T05A using xda app-developers app
mohnish.killer said:
I have a solution that you Should try...
You need to download proper RUU ... the android 2.2 PC10.img thing...I don't remember the name..
No doubt you will return to stock ...but after re root 100% it will solve your problem!!
Sent from my T05A using xda app-developers app
Click to expand...
Click to collapse
thank you mohnish.killer , i have already try this solution with this original shipped rom
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_ 12.56.60.25_26.10.04.03_M_release_199043_signed
am familiar with HTC devices and i know a lot about flashing and rooting and i know how to solve many problems and i have never faced like this problem .
before this problem my HTC was running under Gingerbread StockRom ,i shut it down before i sleep one night and in the next morning i tried to turn it on but it stuck on the boatlooder screen .
the first thing i did is to try solve the problem with an original shipped ROM (RUU) ,the instalation was successful but it didnt work .
the second thing is to flash only BOOT.IMG with fastboot using a Stok boot , the flashing was successfull but the problem is always here.
the last thing i did is to root the device with the ENG-HBOOT and install jelly bean 4.2.2 and ClockworkMod Recovery ,but i still have the problem.
my little brother is using the phone now , i show him how to start the phone with the computer and the command fastboot reboot
and am still confused with this problem , there is something freak with that phone
I don't know from where did you get that image for gingerbread stock anyways.... Just give the android 2.2 image another shot !
Sent from my HTC Vision using xda app-developers app
The phone is a VZW HTC One. I have S-off with Hboot 1.55, bootloader unlocked and I was rooted prior to the flashing of TIKTAK going sideways. Now I can ADB when i'm in recovery and I can flash new recovery mods. I know this means that I'm not completely done for.
When I let the phone try to boot without going into the boot loader it sits at the green HTC screen with the red distribution statement. In this state it tries to make an MTP connection with windows but it doesn't install the drivers properly.
I don't seem to have an internal file structure. I tried downloading HTC1guru's nandroid backup but TWRP doesn't recognize it in either its zipped form or extracted. CWM doesn't seem to recognize any file system at all. I have to use someone elses backup because I was dumb and didn't move my backup off the device before dropping a bomb in the file system.
TWRP is asking for a password that I don't know (and didn't set) every time it opens
I also tried RUU but I never get to the silver HTC screen.
I'm at a loss as to how to proceed. Any thoughts would be most appreciated. I'm pretty handy in the IT world but this is my first time flashing a custom ROM, it may be the last. Thanks in advance.
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000428178272
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4328mV
(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
Just do the 2.10.605.1 ruu (found in santods rom/radio/kernel thread), then " fastboot erase cache ", then " fastboot flash recovery name_of_recovery.img ". From there you can flash a rom, or just flash superuser and be stock rooted.
I can't get the phone into RUU. any reboot that doesn't go to recovery or fastboot just hangs on the green HTC screen.
>fastboot oem rebootRUU
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: read fifo failed, retry
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 17
(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 [ 2.156s]
finished. total time: 2.156s
Are there any other thoughts out there on how I might proceed before I put the phone in a bucket of water and use my warranty?
Sent from my Galaxy Nexus using Tapatalk
Any luck?
jbeavis19 said:
Are there any other thoughts out there on how I might proceed before I put the phone in a bucket of water and use my warranty?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
JBeavis, I am in a very similar situation to the one you are in. Have you had any luck with fixing it or getting a warranty repair?
Thanks!
I'm also in a similar situation
One critical difference between the HTC One and the thunderbolt... no SDCard. Which would not be a big deal had I not wiped the phone with no backup (stupid I know) before loading a new rom image to replace it. Now I can't get ADB to recognize my phone in CWM recovery. No sideload. Nothing. I do have S-off and CWM 6.0.4.7 installed successfully. If anybody has any advice I'd really appreciate it.
@wantasmartcookie @eicos
@jbeavis19
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html?m=1
Try this out.
Thanks, @Gizmoe, but I've already been down that road. I think my EMMC is fried. When I get the adb shell going and check /dev/block, I don't see any mmc devices - only ram and loop devices. And when I run cat /proc/emmc, all of the entries are mmcblk0. As with the others, when I try to relock the device, I get a CMD25 error.
I am open to suggestions but fear I will have to try to get a new device. Does anyone have any suggestions about how to do that? Should I go to Verizon or try HTC? And what should I say? This is really a bummer!
eicos said:
Thanks, @Gizmoe, but I've already been down that road. I think my EMMC is fried. When I get the adb shell going and check /dev/block, I don't see any mmc devices - only ram and loop devices. And when I run cat /proc/emmc, all of the entries are mmcblk0. As with the others, when I try to relock the device, I get a CMD25 error.
I am open to suggestions but fear I will have to try to get a new device. Does anyone have any suggestions about how to do that? Should I go to Verizon or try HTC? And what should I say? This is really a bummer!
Click to expand...
Click to collapse
Did you try the repair process regardless with the right mount point?
These are the Verizon HTC one mounts
{
"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"
}
Yes @Gizmoe, the command fails with "could not stat /dev/block/mmcblk0p37 --- no such file or directory". Any other ideas? I appreciate your help.
Have you tried it with cache or system? Does fastboot oem rebootRUU give you an error too like the op?
---------- Post added at 09:37 PM ---------- Previous post was at 09:31 PM ----------
You could also hit up Mike1986 to see if he can help you out. He wrote the thread and does help people in irc. It's worth a shot.
I gave up and warrantied the phone and now it has 4.4.2 on it so no rooting until ther is a method that works and I'm not sure I'll try another custom rom any time soon.
@Gizmoe, thanks for the suggestion, that is an approach that I didn't try, I thought I went through them all.
Gizmoe said:
Have you tried it with cache or system? Does fastboot oem rebootRUU give you an error too like the op?
---------- Post added at 09:37 PM ---------- Previous post was at 09:31 PM ----------
You could also hit up Mike1986 to see if he can help you out. He wrote the thread and does help people in irc. It's worth a shot.
Click to expand...
Click to collapse
Thanks @Gizmoe, I had the same error with fastboot oem rebootRUU as the op. I am 99.999% sure the EMMC got fried somehow. Probably I hard booted the phone at a bad time during the installation or something - or maybe it was just ready to die. In any case I also have warrantied the phone. Replacement to arrive tomorrow. Here's hoping it doesn't have 4.4.2, though it probably will. @mike1986., do you have any light to shed on this topic?
Gizmoe said:
@wantasmartcookie @eicos
@jbeavis19
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html?m=1
Try this out.
Click to expand...
Click to collapse
I got my phone to a state where I could push a rom down to it using that fix. Thanks for the help! (I've created an entirely different thread detailing my new problem) http://forum.xda-developers.com/showthread.php?t=2657211
Hi,
I have a big problem with my HTC one M8 that was like new, never rooted or rom customised...
Since the last HTC OTA update, my phone is rebooting and starting in recovery mode like pictured, I have already tried to factory reset, wipe data and cache,... No change, I have no more acces to my Android like before the update...
I tried to install from SD card stock rom 4.16.401.10 but it stopped with an error E: Footer is Wrong / Signature verification failed...
HELP PLEASE I!!! I CANT USE MY PHONE ANYMORE ! THANKS
In the recovery mode, it write under strange loading errors, may be it can help... :
{
"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"
}
same problem happened to me.. still looking for an answer
riselljosh said:
same problem happened to me.. still looking for an answer
Click to expand...
Click to collapse
is the phone from Hong Kong ?
Please help newbies... !
THX
I'm not sure how many more times I need to answer this question today!
Run the RUU (will wipe phone).
Thanks for your help, but what is RUU ? I already flashed device but I'm quite a newbie, please guide and again THANK YOU
buzjay said:
Thanks for your help, but what is RUU ? I already flashed device but I'm quite a newbie, please guide and again THANK YOU
Click to expand...
Click to collapse
RUU for your version is here: http://forum.xda-developers.com/showpost.php?p=64869713&postcount=3
Download RUU to PC (PC required) then connect phone in bootloader-fastboot mode. Then simply run the RUU.exe on your PC and it will prompt your through the rest.
Be aware, the RUU will wipe all data on the phone.
Thanks
redpoint73 said:
RUU for your version is here: http://forum.xda-developers.com/showpost.php?p=64869713&postcount=3
Download RUU to PC (PC required) then connect phone in bootloader-fastboot mode. Then simply run the RUU.exe on your PC and it will prompt your through the rest.
Be aware, the RUU will wipe all data on the phone.
Click to expand...
Click to collapse
Thanks a lot REDpoint73, I downloaded the file, which is a ZIP File, not an exe file ? Is that normal ? I look on the internet for a tool named ruu.exe to load this zip files but don't find, please explain to allow me to use my phone again
buzjay said:
Thanks a lot REDpoint73, I downloaded the file, which is a ZIP File, not an exe file ? Is that normal ? I look on the internet for a tool named ruu.exe to load this zip files but don't find, please explain to allow me to use my phone again
Click to expand...
Click to collapse
Read the first two links that I have here : http://forum.xda-developers.com/showpost.php?p=65105965&postcount=6
Link 1 : what you need
Link 2 : how-to
buzjay said:
Thanks a lot REDpoint73, I downloaded the file, which is a ZIP File, not an exe file ? Is that normal ? I look on the internet for a tool named ruu.exe to load this zip files but don't find, please explain to allow me to use my phone again
Click to expand...
Click to collapse
You're correct, I forgot the link was the zip format RUU, instead of the exe format. Sorry for any confusion.
ckpv5 has graciously linked his fine instructions for running the RUU zip.
Again me
In the link provided by ckpv5, (http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6) there is three step in cmd...
I have error in step three : it tell me to restart process... While errors... Please check
C:\RUU>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.017s]
finished. total time: 0.017s
C:\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.023s]
finished. total time: 0.023s
C:\RUU>htc_fastboot flash zip RUU.zip
sending 'zip'... (53965 KB) OKAY
sending time = 2.644 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) total_image_number=8
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) current_image_number=1
(bootloader) current_image_number=2
(bootloader) current_image_number=3
(bootloader) current_image_number=4
(bootloader) current_image_number=5
(bootloader) current_image_number=6
(bootloader) current_image_number=7
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device FA46DWM07854...
sending 'zip'... (53965 KB)
buzjay said:
Again me
In the link provided by ckpv5, (http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6) there is three step in cmd...
I have error in step three : it tell me to restart process... While errors... Please check
C:\RUU>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.017s]
finished. total time: 0.017s
C:\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.023s]
finished. total time: 0.023s
C:\RUU>htc_fastboot flash zip RUU.zip
sending 'zip'... (53965 KB) OKAY
sending time = 2.644 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) total_image_number=8
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) current_image_number=1
(bootloader) current_image_number=2
(bootloader) current_image_number=3
(bootloader) current_image_number=4
(bootloader) current_image_number=5
(bootloader) current_image_number=6
(bootloader) current_image_number=7
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device FA46DWM07854...
sending 'zip'... (53965 KB)
Click to expand...
Click to collapse
Just do it man! Do what it tell u. That's how it works. Run your last command again.
buzjay said:
I have error in step three : it tell me to restart process... While errors... Please check
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device FA46DWM07854...
sending 'zip'... (53965 KB)
Click to expand...
Click to collapse
This is normal. Just flash the zip again. Its typical to get this error message, and have to flash a 2nd time.
I'm doing this exact same process and stuck at "sending 'zip'... (53965 KB)" I tried flashing again and it says "sending 'zip'... (53965 KB)". It doesn't show progress or anything, how long I should expect this to last?
Please, My M9 Is usually on a same boot loop situation.
When I start it it shows just this screen
Software status MODIFIED
LOCKED
S-ON
Security warning (Sometimes it disappear)
REBOOT
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
POWER DOWN
Phone not detected to use adb commands.
Please, I need this phone and I donn't have a warranty.
There is no solution to go out from this screen? There is no software to force flash or flash a dead phone.
There is no hardware tweak to bypass this situation...I don't know anything please.
Please my friends Help me
{
"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'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.
I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help
freshmike said:
I have exactly the same
Click to expand...
Click to collapse
Sadly, I have exactly the same answer. Sorry, but you're probably out of luck.
computerslayer said:
I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.
Click to expand...
Click to collapse
Thank you very much
Just to clarify, status modified on a non rooted, bootloader locked, s-on, never touched phone most likely means a dead nand which is unrecoverable.
Beamed in by telepathy.
my phone is S-ON unlocked .
Today my phone turn off and after stay on boot loop . When i try go to recovery mode or download mode just restart to fastboot.
I connect to computer but only what i can get after command: fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT558YJ00694
all:
I think my nand memory is F...ck ?
If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.
shivadow said:
If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.
Click to expand...
Click to collapse
I do not know if it's worth repairing on htc. Used on ebay 150 €.
freshmike said:
I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help
Click to expand...
Click to collapse
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
obywatel2x said:
I do not know if it's worth repairing on htc. Used on ebay 150 €.
Click to expand...
Click to collapse
Consider Swappa as well - good prices and often it's XDA users (who care more about caring for their phones) upgrading/changing phones & selling their old ones.
blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
If the phone is assuredly duff then I'd try this too, even if I'm yet to know of an instance where it actually worked.. Either that or smack it one time with something really heavy. It won't fix it but you'll feel better!.
Beamed in by telepathy.
blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.
freshmike said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.
Click to expand...
Click to collapse
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip
blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
blueberry60 said:
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s
freshmike said:
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s
Click to expand...
Click to collapse
Have you flashed other img files?
blueberry60 said:
Have you flashed other img files?
Click to expand...
Click to collapse
Yes, none of them went though. All command report you need to be s-off
FAILED (remote: cannot flash this partition in s-on state)
The only one which worked was hosd_signed.img, but that didn't change anything in the state of the phone.
is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s
freshmike said:
is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s
Click to expand...
Click to collapse
You are in download mode?
sipas4 said:
You are in download mode?
Click to expand...
Click to collapse
Boot to bootloader (When I chose this option phone restart and come back to the same screen does nothing)
Boot to download mode (result: failed to boot to download mode press volume up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volume up or down...)
Looks like bootloader/recovery/download mode have been wiped out from the OTA update.
Hello,
I have a friend's HTC M) which is stuck in the black HTC logo loop, approx 1.5 second loop that goes on and on until it dies from battery depletion.
This happened after some heating up by the phone, so my search points to corrupt data on Nand memmory (or Nand itself died), don't know whter we can reverse it or not.
After some tries, I managed to get it in recovery mode, and wiped cache and data, both completed with errors. I attached some pic of it.
If from recovery menu, I choose reboot into bootloader, it reboots and gets stuck on white screen with HTC logo (not the black one I spoke before).
I have been reading the HTC M9 thread, but I don't know which nex step to take.
This is an unbranded M9, without any rom modifications.
Model OPJA1000,
Software status: Official
Locked
S-ON
{
"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"
}
If anyone could point me in the right direction, I'll gladly try to go by myself.
Thank you in advance!
I have same problem
My software status is modify.
D:\HTC M9\L51>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT55CYJ00237
all:
finished. total time: 0.125s
i am stuck on bootloader mod doesn't go on download mod nor to recovery mod.
can't boot to Android as well,
All the other values for CID, MID and other stuff is blank when I do indivdual fastboot getvar command.
can I bring my M9 to life with any stock image flashing with Fastboot command.
If yes please let me know which stock image I use and how to flash?
Thanks
ketulharini said:
I have same problem
My software status is modify.
D:\HTC M9\L51>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT55CYJ00237
all:
finished. total time: 0.125s
i am stuck on bootloader mod doesn't go on download mod nor to recovery mod.
can't boot to Android as well,
All the other values for CID, MID and other stuff is blank when I do indivdual fastboot getvar command.
can I bring my M9 to life with any stock image flashing with Fastboot command.
If yes please let me know which stock image I use and how to flash?
Thanks
Click to expand...
Click to collapse
I still haven't made progrss, since I got no help and even searching I got no easy solution. One thing I did make was a somewhat easy way to access recovery by trial and error. I disassembled back cover and tied to boot to recovery. If it entered in the bootloop, I'll just unplug the battery and tried again and again. With some tries I can get to recovery. I'll try to install from sd card to see if I can fix it.
While I put into recovery or download mode it shows this screen.
My one doesn't go into bootloop just stuck on this screen.
Do you think it can go to download or recovery mode with your method.
Thanks
If you can't get to download mode then the phone is broken.
c_sarmento said:
Hello,
I have a friend's HTC M) which is stuck in the black HTC logo loop, approx 1.5 second loop that goes on and on until it dies from battery depletion.
This happened after some heating up by the phone, so my search points to corrupt data on Nand memmory (or Nand itself died), don't know whter we can reverse it or not.
After some tries, I managed to get it in recovery mode, and wiped cache and data, both completed with errors. I attached some pic of it.
If from recovery menu, I choose reboot into bootloader, it reboots and gets stuck on white screen with HTC logo (not the black one I spoke before).
I have been reading the HTC M9 thread, but I don't know which nex step to take.
This is an unbranded M9, without any rom modifications.
Model OPJA1000,
Software status: Official
Locked
S-ON
If anyone could point me in the right direction, I'll gladly try to go by myself.
Thank you in advance!
Click to expand...
Click to collapse
Suck in the same situation. Rooted for months no issues then started bootlooping. I can get to twrp but wont go further any ideas??
Had the same issue. Hold up volume button and power button until phone switches off. Remove sd card then power on.
Must be trying to boot from and old or corrupted file on sd