Hello.
i searched this forum and not found the answer. thats why i started new thread. appologize if duplicate Q/A exist.
Flashing Recovery and boot_signed.img and try to boot into recovery. no luck. always get into bootloader. tried to flash other partitions, but getting error from remote (device). tried stock rom with RUU. but after rebooting device RUU does not detect. and exit with code 171.
unable to flash any partition with fastboot flash patition name partitionfile.img
but can only flash boot and recovery.
tried ziped rom with sd card. but it stuck on device halted while parsing large image. and prompt to reboot
got phone in bricked mode.
Bootloader UNLOCKED. tried to relock with fastboot oem lock but not lock. status is UNLOCKED
***SYSTEM STATUS IS MODIFIED***
This is can be only change after moving to stock.
LOG FILE of getvar
Code:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.13.111.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT55DYS00****
(bootloader) imei: 358031060861***
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: T-MOB101
(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: e31b162e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
Please advise.
sylentears said:
Hello.
i searched this forum and not found the answer. thats why i started new thread. appologize if duplicate Q/A exist.
Flashing Recovery and boot_signed.img and try to boot into recovery. no luck. always get into bootloader. tried to flash other partitions, but getting error from remote (device). tried stock rom with RUU. but after rebooting device RUU does not detect. and exit with code 171.
unable to flash any partition with fastboot flash patition name partitionfile.img
but can only flash boot and recovery.
tried ziped rom with sd card. but it stuck on device halted while parsing large image. and prompt to reboot
got phone in bricked mode.
Bootloader UNLOCKED. tried to relock with fastboot oem lock but not lock. status is UNLOCKED
***SYSTEM STATUS IS MODIFIED***
This is can be only change after moving to stock.
LOG FILE of getvar
Please advise.
Click to expand...
Click to collapse
Have you tried booting TWRP recovery without actually installing it?
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
fastboot boot recovery NAME OF RECOVERY.img
For example: fastboot boot recovery twrp3.0.1.1.img
---------- Post added at 07:53 PM ---------- Previous post was at 07:30 PM ----------
Since your device reports bootloader to be unlocked, you should be able to :
1. Boot your device to bootloader
2. Connect to PC ( i presume you have drivers installed )
3. Run: fastboot devices
4. Upon successful device discovery try to boot twrp as written above
5. If the phone boots to twrp, do a full wipe in twrp
6. Try sideloading cyanogen rom and then installing it.
---------- Post added at 07:54 PM ---------- Previous post was at 07:53 PM ----------
If that works, either leave the phone as it is, or try ruu to go back to stock
twrprecovery.img. but after that device stuck and go unresponsive. And does not accept any command.
sylentears said:
twrprecovery.img. but after that device stuck and go unresponsive. And does not accept any command.
Click to expand...
Click to collapse
Sorry I didn't understand your post. What did you do and what happened?
when send this command with fastboot boot twrp3.x.x.x.img device accept command and after successfull message on fastboot command. device does not respond even i keep for some time. and after draining battery it power off itself. and when i put this on charge after little charging it goes to bootloader again. i hope so. now cleared.
sylentears said:
when send this command with fastboot boot twrp3.x.x.x.img device accept command and after successfull message on fastboot command. device does not respond even i keep for some time. and after draining battery it power off itself. and when i put this on charge after little charging it goes to bootloader again. i hope so. now cleared.
Click to expand...
Click to collapse
Have you tried both versions of twrp?
Would you please specify the versions???
sylentears said:
Would you please specify the versions???
Click to expand...
Click to collapse
https://ruu.lalleman.net/HTC_M8S(QL_UL)/Recovery/
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
You will find some stock recoveries there as well.
already been tried with. but device not reboot ro recovery after this command
fastboot boot twrpver.img
Click to expand...
Click to collapse
and also
fastboot boot stockrecovery.img
Click to expand...
Click to collapse
I m able to flash recovery and boot into recovery image command. but does not effect on device.
It might be a eMMC chip issue???
Image CRC check result
rpm :0xAxxxxxxAB
sbl1: :0x9xxxxxxC4
sbl2 :0x0
sbl3 :0x0
tz :0xCxxxxxxxDC
radio :0x3xxxxxxx83
hboot :0x6DxxxxxxGA
boot :0x0
recovery :0x0
system :0x2xxxxxxxx8C
0x0 stated partition images are reported corrupted or damaged. i think it can fixed only by Qualcomm USB mode to extract rom image
sylentears said:
Image CRC check result
rpm :0xAxxxxxxAB
sbl1: :0x9xxxxxxC4
sbl2 :0x0
sbl3 :0x0
tz :0xCxxxxxxxDC
radio :0x3xxxxxxx83
hboot :0x6DxxxxxxGA
boot :0x0
recovery :0x0
system :0x2xxxxxxxx8C
0x0 stated partition images are reported corrupted or damaged. i think it can fixed only by Qualcomm USB mode to extract rom image
Click to expand...
Click to collapse
Have you ever done that Qualcomm usb mode? I have one perfectly working HTC m8s, so if you could shed some light on the procedure that would be great. Googling didn't give me much insight in relation to it.
If you have Easy jtag pro box then it can fix. please see this video.
Not sure if this helps but I was unable to get twrp 3.x.x workING.
I'm on 2.8.7
Can you Boot into stock. and able to flash ruu image with PC Application or able to flash .zip image with SD Card.
post the status of work and let us advise you further.
Note: TWRP will only work if your bootloader is unlocked. and still will not work if the partition structure is damaged. check CRC check on fastboot Screen.
Sorry I thought this usb qualcomm mode can be used with pc and phone only
Ok
so you are in dead boot mode. and only cant connect in Qualcomm USB mode 9008
watch this tutorial carefully and try to unbrick your phone and back to bootloader mode and reflash stock image or stock backup.
Hit Thanks or like if it does help you.
Try booting to TWRP again using HTC_Fastboot. Fastboot will not work with a HTC, they have their own version.
sylentears said:
Ok
so you are in dead boot mode. and only cant connect in Qualcomm USB mode 9008
watch this tutorial carefully and try to unbrick your phone and back to bootloader mode and reflash stock image or stock backup.
Hit Thanks or like if it does help you.
Click to expand...
Click to collapse
how to use this method on htc one m8? as i am facing ,
rpm :0xAxxxxxxAB
sbl1: :0x9xxxxxxC4
sbl2 :0x0
sbl3 :0x0
tz :0xCxxxxxxxDC
radio :0x3xxxxxxx83
hboot :0x6DxxxxxxGA
this sbl2 and sbl3 values as 0x0 any leads?
Related
Hello, everyone!
First of all, I want to thank all the xda comminity for help, I recieved, but today I have to ask for help again.
I have read all the topics I was able to find and followed some advices, but they didn't help...So back to start..
I have Asus Nexus 7 2013 16Gb Wi-Fi. It had latest Android 4.4.2 from OTA update.
Few day ago I had to reboot it, because the screen stopped responding for touches (the hardware buttons still worked). Such thing happened before, so I didn't panic. I pushed the Power button for a long time and the device was switched off. Then I tried to boot it again and... it hang on Google logo.
I tried to reboot it few more times, but I got the same result. Here is the list of my following steps and results:
I booted to fastboot and tried to boot recovery - fail. still have only google logo.
booted to fastboot and unlocked it by
Code:
fastboot oem unlock
. - fail. still have only google logo.
downloaded the latest factory image and flashed if by
Code:
flash-all
. Everything flashed successfully, but..fail. still have only google logo and open locker on a screen.
downloaded custom recovery and flashed. Tried to boot to recovery again - fail. still have only google logo with locker.
tried to flash cyanogenmod. it flashed but... fail again. only google logo with locker.
erased all the partitions through fastboot and flashed previous factory image. fail - still have google logo.
Please, if anyone can suggest something to resurrect my Nexus, tell me, what should I try next.
Or it is a brick? =(
Is there any chance to get any log from bootloader?
I don't know, if this could help, but here is info from fastboot:
fastboot getvar all
(bootloader) version-bootloader: FLO-04.02
(bootloader) version-baseband: none
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: flo 16G
(bootloader) serialno: 05848bba
(bootloader) product: flo
(bootloader) secure_boot: enabled
(bootloader) lock_state: unlocked
(bootloader) project: flo
(bootloader) off-mode-charge: yes
(bootloader) uart-on: no
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0x0000000000aee000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000034800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000023000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x000000031b7fbe00
all:
Click to expand...
Click to collapse
Demian87 said:
Hello, everyone!
First of all, I want to thank all the xda comminity for help, I recieved, but today I have to ask for help again.
I have read all the topics I was able to find and followed some advices, but they didn't help...So back to start..
I have Asus Nexus 7 2013 16Gb Wi-Fi. It had latest Android 4.4.2 from OTA update.
Few day ago I had to reboot it, because the screen stopped responding for touches (the hardware buttons still worked). Such thing happened before, so I didn't panic. I pushed the Power button for a long time and the device was switched off. Then I tried to boot it again and... it hang on Google logo.
I tried to reboot it few more times, but I got the same result. Here is the list of my following steps and results:
I booted to fastboot and tried to boot recovery - fail. still have only google logo.
booted to fastboot and unlocked it by
Code:
fastboot oem unlock
. - fail. still have only google logo.
downloaded the latest factory image and flashed if by
Code:
flash-all
. Everything flashed successfully, but..fail. still have only google logo and open locker on a screen.
downloaded custom recovery and flashed. Tried to boot to recovery again - fail. still have only google logo with locker.
tried to flash cyanogenmod. it flashed but... fail again. only google logo with locker.
erased all the partitions through fastboot and flashed previous factory image. fail - still have google logo.
Please, if anyone can suggest something to resurrect my Nexus, tell me, what should I try next.
Or it is a brick? =(
Is there any chance to get any log from bootloader?
I don't know, if this could help, but here is info from fastboot:
Click to expand...
Click to collapse
I posted somewhere In Q&A on how to unbrick the device so please go ahead and take a look
---------- Post added at 05:52 PM ---------- Previous post was at 05:52 PM ----------
I'm a bit lazy to retype out the instructions all over again
Bobbi lim said:
I posted somewhere In Q&A on how to unbrick the device so please go ahead and take a look
---------- Post added at 05:52 PM ---------- Previous post was at 05:52 PM ----------
I'm a bit lazy to retype out the instructions all over again
Click to expand...
Click to collapse
Thank you for a suggestion to search your posts.
I found only the same post in this thread: http://forum.xda-developers.com/showthread.php?t=2624688
and some flash-all decision here: http://forum.xda-developers.com/showthread.php?p=49347871#post49347871
As you can see, I have already tried to flash-all few times and this piece of advice was useless in my case, unfortunatelly.
Hi,
I awoke this morning to have my One reboot on me, only to have it hang at the green HTC logo.
I need help getting it functional again, asap.
I'm s-off and rooted.
What I can do:
Boot to bootloader and use fastboot commands - but
Code:
fastboot reboot oem rebootRUU
does not boot to the black HTC screen, but back to the green HTC logo, so I'm unable to flash a RUU.
What I can't do:
Use adb commands
Boot to recovery - freezes at teamwin screen. However, when the phone is stuck at the teamwin screen, I seem to be able to use adb - if I get here, I can reboot to the bootloader with adb.
Boot to system - hangs at the green HTC startup logo.
What I've tried:
Using fastboot to flash a new recovery to restore the backup I should have - still hangs at teamwin screen
Is there anything that can be done to fix this, or is my phone a lost cause?
can you get to hboot by holding vol- and power for a bout 30 sec?
Yes, that's how I'm able to get the fastboot stuff working.
After further investigation, it seems nothing I do persists on the phone. I attempted to flash the stock recovery to attempt another factory reset, but it still attempts to boot to TWRP.
axeseven said:
After further investigation, it seems nothing I do persists on the phone. I attempted to flash the stock recovery to attempt another factory reset, but it still attempts to boot to TWRP.
Click to expand...
Click to collapse
i would RUU to get back to a working phone.
by any chance did you make a backup of you internal storage because ruu will format it.
EDIT:
are you s-off and unlocked?
Yes to both - but how can I flash a RUU? When I run the fastboot oem rebootRUU command it does not boot to the usual black/silver HTC screen, instead the normal green startup logo.
before you said you did command:
Code:
fastboot reboot oem rebootRUU
the actual command is:
Code:
fastboot oem rebootRUU
also make sure RUU is the only capital letters
when i fastboot, if you type:
Code:
fastboot devices
what is the output ??
Unfortunately, that has the same result - stuck at the green HTC boot logo.
EDIT:
After sitting at this screen for awhile, it booted into what looks like the stock rom, asking for a password to decrypt the storage. I don't recall ever setting a password for this, and even if I did, I stopped using the stock rom almost as soon as I got the phone.
Code:
fastboot devices
outputs the serial number and that it's in fastboot:
Code:
-serial number here- fastboot
axeseven said:
Unfortunately, that has the same result - stuck at the green HTC boot logo.
Click to expand...
Click to collapse
make sure the pc can see fastboot on the device with command:
Code:
fastboot devices
if output looks like this:
C:\>fastboot devices
FA38PS904782 fastboot
you should be able to type:
Code:
fastboot flash zip nameofruu.zip
and it will start to process.
---------- Post added at 01:17 PM ---------- Previous post was at 01:10 PM ----------
axeseven said:
Unfortunately, that has the same result - stuck at the green HTC boot logo.
EDIT:
After sitting at this screen for awhile, it booted into what looks like the stock rom, asking for a password to decrypt the storage. I don't recall ever setting a password for this, and even if I did, I stopped using the stock rom almost as soon as I got the phone.
Code:
fastboot devices
outputs the serial number and that it's in fastboot:
Code:
-serial number here- fastboot
Click to expand...
Click to collapse
yay, this means fastboot is talking to the phone. thats odd that storage is encrypted. can you still use the phone to get to settings?
synisterwolf said:
yay, this means fastboot is talking to the phone. thats odd that storage is encrypted. can you still use the phone to get to settings?
Click to expand...
Click to collapse
Unfortunately, no. I just get an option to decrypt the storage with a password or make an emergency call. I'm about to attempt to flash the ruu .zip without booting into rebootRUU, unless there is something else I can do.
did you use a kernel or recovery with F2FS?
Not to my knowledge, no. When trying to flash the ruu without rebootRUU I get the following:
Code:
C:\>fastboot flash zip PN07IMG_M7_WL_JB_50_VZW_1.10.605.15_DECRYPT.ZIP
sending 'zip' (1178528 KB)...
OKAY [ 55.707s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 55.762s
and just so it's here, when I fastboot getvar:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.1104
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -serialnumberhere-
(bootloader) imei: -imeihere-
(bootloader) meid: -meidhere-
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4309mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fb8d0c81
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Are you still stuck?
hawknest said:
Are you still stuck?
Click to expand...
Click to collapse
Yes, flashing the ruu didn't work.
Have you tried flashing recovery again ?.
Try flashing philz recovery . Make sure it's m7wlv version
rename to recovery.img and add to platform tools folder
fastboot flash recovery recovery.img
fastboot erase cache
Try rebooting into recovery
hawknest said:
Have you tried flashing recovery again ?.
Try flashing philz recovery . Make sure it's m7wlv version
rename to recovery.img and add to platform tools folder
fastboot flash recovery recovery.img
fastboot erase cache
Try rebooting into recovery
Click to expand...
Click to collapse
I can't seem to find a version of Philz recovery for m7wlv. Am I correct in thinking I need the m7vzw version from https://goo.im/devs/philz_touch/CWM_Advanced_Edition/m7vzw/ here?
You are on older firmware, have you tried flashing newer firmware and see if ruu mode works after flashing firmware? You are s-off, so you can downgrade when you ruu.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
You are on older firmware, have you tried flashing newer firmware and see if ruu mode works after flashing firmware? You are s-off, so you can downgrade when you ruu.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
This is worth a shot, I guess. Is there any particular version of the firmware or might any newer than 1.10.605.15 work?
EDIT:
After trying this, I get the same remote:not allowed error as above.
Additionally, after flashing philz recovery - which the console says is successfully flashed, when I reboot to recovery, it still hangs at the blue teamwin logo as before.
axeseven said:
I can't seem to find a version of Philz recovery for m7wlv. Am I correct in thinking I need the m7vzw version from https://goo.im/devs/philz_touch/CWM_Advanced_Edition/m7vzw/ here?
Click to expand...
Click to collapse
Yeah the bottom one .. sorry . M7wlv is the official name but yeah that one
Revamped 2.0 Lunar 4.4.3
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
Here's the latest ruu for s-off http://forum.xda-developers.com/showthread.php?p=52987679
Revamped 2.0 Lunar 4.4.3
That was the one I tried, to no success. After flashing it and clearing the cache, when I boot to recovery it still sits at a blue teamwin screen.
hi,
someone gave me a bricked HTC M8 and i wanna fix it for him. i don't know what got him to be bricked...
the situation is this:
- Boot Loop
- Fastboot working
- Unlocking Worked
- Able to flash TWRP and enter recovery mode
- mounting for all partition fails with unable to mount
- TWRP "Repair" fails: "E:/sbin/e2fck -fp /dev/block/mmcnlk0p47 proccess ended with ERROR=8 ; unable to repair /data ; Error repairing fail system"
- TWRP "Change File System" to ESX4 not working: "unable to mount /data ; Unknown MTP message type: 1 ; Error changing file system; unable to mount /system ; unable to mount /data ; unable to mount /devlog ; unable to mount storage"
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.1540.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 55eb39ab
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
PLS HELP what doo?
Install the dev edition ruu.....
Mr Hofs said:
Install the dev edition ruu.....
Click to expand...
Click to collapse
how?
omer323 said:
hi,
someone gave me a bricked HTC M8 and i wanna fix it for him. i don't know what got him to be bricked...
the situation is this:
- Boot Loop
- Fastboot working
- Unlocking Worked
- Able to flash TWRP and enter recovery mode
- mounting for all partition fails with unable to mount
- TWRP "Repair" fails: "E:/sbin/e2fck -fp /dev/block/mmcnlk0p47 proccess ended with ERROR=8 ; unable to repair /data ; Error repairing fail system"
- TWRP "Change File System" to ESX4 not working: "unable to mount /data ; Unknown MTP message type: 1 ; Error changing file system; unable to mount /system ; unable to mount /data ; unable to mount /devlog ; unable to mount storage"
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.1540.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 55eb39ab
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
PLS HELP what doo?
Click to expand...
Click to collapse
You CID number BS_US001 is developper edition M8. As @Mr Hofs suggested, Download Dev edition RUU, Boot into fastboot and install RUU.
Grab this RUU.exe (not OTA, RUU): https://onedrive.live.com/?authkey=!AJ5pbUC2atPkSaA&id=8B8E71545D3D985B!1658&cid=8B8E71545D3D985B
Turn On phone and go to bootloader, connect it to PC, install drivers and run RUU.exe on PC.
omer323 said:
- Unlocking Worked
Click to expand...
Click to collapse
I assume you mean bootloader unlock, as the term "unlock" is vague and can mean several things.
You will need to relock to run the RUU, since you are s-on. Do so with the command:
fastboot oem lock
Also, this isn't a brick. A brick by definition is not fixable. At least not without opening the phone, and JTAG, replacing motherboard, etc.
What you have is no boot, and you don't know how to recover. That isn't a brick.
WTF.
i did "fastboot oem lock" which resulted with:
[PGFS] partition_update_pgfs: pg1fs_security
TZ_HTC_SVC_ENC ret = 0
[PGFS] partition_update_pgfs: pg2fs_sec_recover
Lock successfully...
deinit_lcd
mipi display off
mdp_clock_off
turn off fd8c2308 failed 1 times. Try again...
disable_mmss_clk done
pll1_disable done
TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7
[CRITICAL] SPMI write command failure:
= 4
[CRITICAL] SPMI write command failure:
= 4
[ERR] Cannot halt SPMI arbiter!!
[INFO] Rebooting device
us read failed (No such file or directory))
tal time: 1.227s
than i run RUU, which failed, i pressed recover, it told to me to unplug the device and shut it down.
and not it won't turn on no mather what!! not even battery logo....
WHAT HAVE I DONE
omer323 said:
WTF.
i did "fastboot oem lock" which resulted with:
Click to expand...
Click to collapse
Was it unlocked before, or not? This wan't clear to me, from what you posted.
After the command, was it RELOCKED or UNLOCKED?
omer323 said:
than i run RUU, which failed
Click to expand...
Click to collapse
What was the failure message and/or error number?
RUU failed before sending or writing anything?
You need to be specific, and provide as much detail as necessary.
omer323 said:
i pressed recover, it told to me to unplug the device and shut it down.
and not it won't turn on no mather what!! not even battery logo....
Click to expand...
Click to collapse
What does that mean "no matter what"? I doesn't tell us anything about what you tried, or didn't try. Please be specific instead of vague statements, that tell us nothing.
Try holding power and vol up for 30 to 60 seconds, and see if there is any change.
I don't think you did anything serious, that wasn't already screwed up. You are s-on, and assuming the RUU failed before sending/writing anything, then a true brick is unlikely.
redpoint73 said:
Was it unlocked before, or not? This wan't clear to me, from what you posted.
Click to expand...
Click to collapse
UNLOCKED
redpoint73 said:
After the command, was it RELOCKED or UNLOCKED?
Click to expand...
Click to collapse
RELOCKED
redpoint73 said:
What was the failure message and/or error number?
RUU failed before sending or writing anything?
You need to be specific, and provide as much detail as necessary.
Click to expand...
Click to collapse
i don't remember exactly what heppened, BUT i found RUU log file on my computer,
i attached the log.
redpoint73 said:
What does that mean "no matter what"? I doesn't tell us anything about what you tried, or didn't try. Please be specific instead of vague statements, that tell us nothing.
Try holding power and vol up for 30 to 60 seconds, and see if there is any change.
I don't think you did anything serious, that wasn't already screwed up. You are s-on, and assuming the RUU failed before sending/writing anything, then a true brick is unlikely.
Click to expand...
Click to collapse
the screen is black.
every combination of buttons i try results NOTHING - nothing on screen, no vibrations...
i tried holding all the combinations for a long time...
the only thing i get - if i plug the device via USB, every ~20 seconds i see in device manager that it disconnect for a second and connected again as QHSUSB_BULK
THANK YOU SO MUCH FOR HELPING~!!!
omer323 said:
every combination of buttons i try results NOTHING - nothing on screen, no vibrations...
i tried holding all the combinations for a long time...
Click to expand...
Click to collapse
You shouldn't be trying "every" combination. You should be trying the one I specified.
Put the phone on wall charger (not connected to computer) or a few hours, and try again.
Then try the combo I specified. Try it with and without the wall charger connected.
---------- Post added at 01:03 PM ---------- Previous post was at 01:01 PM ----------
What RUU did you run exactly? Was it the one linked in Post #5 above? What was the exact file name?
I don't have any reason to be suspicious of this link, specifically. But on the other hand, this RUU is easily downloaded direct from HTC, and I don't see a reason to download from some other (unconfirmed) source. Or for all we know, the download was corrupt/damaged.
redpoint73 said:
You shouldn't be trying "every" combination. You should be trying the one I specified.
Click to expand...
Click to collapse
tried it.... nothing...
redpoint73 said:
Put the phone on wall charger (not connected to computer) or a few hours, and try again.
Then try the combo I specified. Try it with and without the wall charger connected.
Click to expand...
Click to collapse
ill try that...
redpoint73 said:
---------- Post added at 01:03 PM ---------- Previous post was at 01:01 PM ----------
Click to expand...
Click to collapse
redpoint73 said:
What RUU did you run exactly? Was it the one linked in Post #5 above? What was the exact file name?
I don't have any reason to be suspicious of this link, specifically. But on the other hand, this RUU is easily downloaded direct from HTC, and I don't see a reason to download from some other (unconfirmed) source. Or for all we know, the download was corrupt/damaged.
Click to expand...
Click to collapse
yes, the link he gave me.
filename: RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2
omer323 said:
filename: RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2
Click to expand...
Click to collapse
Well, the file name is right. Assuming the file is what it says it is, and not damaged or corrupt during download, it possible for the correct RUU to brick the phone. It doesn't happen often, but I have seen it happen a few times, even on completely stock (unmodified) M8 devices and the correct, official RUU.
Or its possible that it was messed up before, such as bad emmc, and the RUU just made it worse.
In any case, charging for a few hours, then trying power+vol up is about all you can do at this point.
QHUSB is Qualcomm emergency mode. Try to get out of it by pressing (for long) Vol UP + Power.
For me it looks like fried eMMC chip... Sometimes it happens. Some time ago my One M7 died at me because of this in exactly the same way.
eMMC chip was corrupted before running RUU - unable to mount partition and errors during "fastboot oem lock".
redpoint73 said:
I don't have any reason to be suspicious of this link, specifically. But on the other hand, this RUU is easily downloaded direct from HTC, and I don't see a reason to download from some other (unconfirmed) source.
Click to expand...
Click to collapse
It's from this thread: http://forum.xda-developers.com/showthread.php?t=2701376
I don't think it's suspicious or unconfirmed.
I'm pretty sure that this RUU.exe is correct, because I was flashing with it few times.
Please check MD5 checksum. My working RUU.exe (downloaded from thread linked above) checksum is: c661c073d368274c3137d5080c88a45c and file size of 1 548 439 552 bytes (on disk).
radkor said:
It's from this thread: http://forum.xda-developers.com/showthread.php?t=2701376
I don't think it's suspicious or unconfirmed.
I'm pretty sure that this RUU.exe is correct, because I was flashing with it few times.
Click to expand...
Click to collapse
As I said, I don't have any reason to doubt the source. But for lack of any other evidence (the subsequent report that you did use it a few times does count for something there) I have no reason to trust it more than the official source. The RUU is available for download direct from HTC, so I don't see a reason to use a mirror (unless its faster): http://www.htc.com/us/support/htc-one-m8/news/
Again, I don't doubt the mirror. Mr Hofs has made valuable contributions here, so if he posted it; I trust it. But I was just trying to consider every possibility for the OP's issue.
redpoint73 said:
The RUU is available for download direct from HTC, so I don't see a reason to use a mirror (unless its faster): http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
OK, but on HTC's site it's only newest MM update available for download.
I can't see a link for older LP ROM which OP was using. Best for him (as he has S-ON) was to reflash ROM version that he already have, basing on pasted "fastboot getvar all" result.
If he would flash newer version (MM) with S-ON, then he will be stuck on this newer version without possibility to downgrade, unless he's S-OFF.
As I said earlier, phone supposedly "bricked" earlier, what you can see during "fastboot oem lock" and resulting error messages after issuing this command.
QHSUSB_DLOAD mode is because of bad NAND.
I've had similiar issue with my M7: http://forum.xda-developers.com/htc-one/help/bricked-device-swap-to-dev-ed-partially-t3015574/
I hope you're not blaming me for unsuccessful OP's phone flashing or earlier bricking?
radkor said:
OK, but on HTC's site it's only newest MM update available for download.
Click to expand...
Click to collapse
You're right, I forgot we were talking about LP (OP's current state).
The direct HTC link for OP's current LP version is here: http://dl3.htc.com.s3.amazonaws.com/application/RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2.exe
radkor said:
I hope you're not blaming me for unsuccessful OP's phone flashing or earlier bricking?
Click to expand...
Click to collapse
Of course not! I never stated any such thing. Just considering every possibility, like a corrupt RUU file. But as I already stated, the fact that you reported using it successfully (and more than once) tells me the file is good.
redpoint73 said:
The direct HTC link for OP's current LP version is here: http://dl3.htc.com.s3.amazonaws.com/application/RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2.exe
Click to expand...
Click to collapse
I'm downloading it right now just to compare it with RUU.exe posted on Mr Hofs' thread.
EDIT:
OK, CRC is exactly the same. Everyone can check this. So I think we can exclude corrupted RUU.exe linked on Mr Hofs' thread. It's exactly the same as the file on HTC servers.
charged for hours, pressed VOL-UP+POWER for 2 minutes with or without charging, and..... NOTHING
the only response i get is the red led when charged and the QHUSB when plugged to computer
so i guess it's bricked for ever
omer323 said:
charged for hours, pressed VOL-UP+POWER for 2 minutes with or without charging, and..... NOTHING
the only response i get is the red led when charged and the QHUSB when plugged to computer
so i guess it's bricked for ever
Click to expand...
Click to collapse
Most likely, yes.
I mentioned early in the thread that this wasn't a brick. As long as the screen comes on (as it did earlier), it almost never is. But this is the relatively uncommon exception, which can be caused by a bad emmc or radio brick.
omer323 said:
charged for hours, pressed VOL-UP+POWER for 2 minutes with or without charging, and..... NOTHING
the only response i get is the red led when charged and the QHUSB when plugged to computer
so i guess it's bricked for ever
Click to expand...
Click to collapse
Try Power + Volume Up + Volume Down more that 2 minutes ... usually about to close 3 minutes, it should up. This is how I got out from QHUSD many times...
But a bad emmc is also possible .. if that is the reason, then only HTC can fix it.
Also after fastboot oem lock, did you do fastboot reboot-bootloader to confirm the bootloader is relocked then only run RUU ?
I don't see you mentioned that except after fastboot oem lock you ran the RUU right away.
Hello, I have my M8 with Android 6.0 and software version 6.16.708.1 , I installed TWRP 3.0.2-0 and I downloaded the backup 6.16.708.1_ckpv5 , when I 'm in the step of the restore the backup, jumps to me an error ( attached image error) extractTarFork () enden process with error : 255, and then it does not continue, could someone help me ?. I'm trying to install a previous version of android, but it still with the error :S.
Anybody?
kikirimai said:
..... I'm trying to install a previous version of android, but it still with the error :S.
Click to expand...
Click to collapse
Try with TWRP 2.8.7.0
ckpv5 said:
Try with TWRP 2.8.7.0
Click to expand...
Click to collapse
I tried it but it doesn't work :S what more can I do?
Anybody?????
Try fastboot erase cache after install TWRP ...
Can you post your fastboot getvar all without serial & imei no. ?
Usually this error is related to partition problem .. maybe flashing the firmware, then TWRP follow by fastboot erase cache command can fix this.
ckpv5 said:
Try fastboot erase cache after install TWRP ...
Can you post your fastboot getvar all without serial & imei no. ?
Usually this error is related to partition problem .. maybe flashing the firmware, then TWRP follow by fastboot erase cache command can fix this.
Click to expand...
Click to collapse
I tried to install TWRP and then I did fastboot erase cache, but it doesn't work, I'm posting the fatboot getvar all, what more can I do, if I flash system in CMD it can works?
(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.16.708.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: HTC__622
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
kikirimai said:
I tried to install TWRP and then I did fastboot erase cache, but it doesn't work, I'm posting the fatboot getvar all, what more can I do, if I flash system in CMD it can works?
Click to expand...
Click to collapse
First - a stupid question (because it happened before) - you do flash a correct version TWRP meant for HTC M8, right ? The one that you downloaded from https://dl.twrp.me/m8/
If the answer is yes for the above, try flashing firmware.
Get the firmware fw_6.16.708.1.zip and read how-to in my thread here : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Then unlock the bootloader with the unlock_code.bin .. when successfully unlocked, the system will reboot but it will fail .. press both power + volume up button .. when the screen goes black, release both buttons but press and hold volume down button. This will get you to hboot, press power once to get to bootloader/fastboot ... flash TWRP then try to restore backup.
ckpv5 said:
First - a stupid question (because it happened before) - you do flash a correct version TWRP meant for HTC M8, right ? The one that you downloaded from https://dl.twrp.me/m8/
If the answer is yes for the above, try flashing firmware.
Get the firmware fw_6.16.708.1.zip and read how-to in my thread here : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Then unlock the bootloader with the unlock_code.bin .. when successfully unlocked, the system will reboot but it will fail .. press both power + volume up button .. when the screen goes black, release both buttons but press and hold volume down button. This will get you to hboot, press power once to get to bootloader/fastboot ... flash TWRP then try to restore backup.
Click to expand...
Click to collapse
Bro, thanks a lot for you help, I really really appreciate it. I fixed my problem with flashing the nandroid 4.16.708.1 with TWRP 2.8.7.0 but I have the same error that it makes me to flash my cellphone, I dont have signal and the cellphone doesnt show to me the imei, do you think if I put the imei in fastboot can it works? (Sorry for my english) and one more time thank you for all your support .
kikirimai said:
....but I have the same error that it makes me to flash my cellphone, I dont have signal and the cellphone doesnt show to me the imei, do you think if I put the imei in fastboot can it works?
Click to expand...
Click to collapse
So .. that's your actual problem. If it is not hardware problem, you can fix this by flashing firmware as I mentioned above. A few people succeed to fix the same problem by flashing firmware.
ckpv5 said:
So .. that's your actual problem. If it is not hardware problem, you can fix this by flashing firmware as I mentioned above. A few people succeed to fix the same problem by flashing firmware.
Click to expand...
Click to collapse
Perfect, Im going to do all your instructions and then reply, thank you for all
Im sorry, where is the unlock_code.bin? and how can I flash/install that?
Edit: Actually I know that xD sorry.
Man, you are amazing, thanks for your support , I did all your instructions and it works, my cellphone now has signal and all its correct, only one thing, the backup 6.16.708.1_ckpv5 maybe its wrong, I couldn't flash it, but it doesn't matter, I installed nandroid 4.xxx, thank you one more time , greetings!
Maybe the 6.x download is bad..
You can install stock recovery then check OTA to update from current 4.x
hi i was given an m9 so im trying to resurrect it first a few stats
soft version modified
locked
s-on
security warning
i can get into recovery mode
android recovery
htc/htc_himauhl/htc_himauhl
6.0/mra58k/buildteam02041257user/release-keys
then menu
reboot sys
reboot to bootloader
apply update from adb
apply update from sd card
wipe data/factory reset
wipe cache partition
power off
them some messages support api3
handle_cota_install install cwpkg to /cache/cota/cwpkg.zip
please any ideas??????????
First, we need to know more about your device.
You need adb and fastboot installed(I recommend Minimal ADB & Fastboot if you don't have already), HTC Drivers.
Put your phone in download mode and do "fastboot getvar all" remove imei/sn from output and post here.
lucyr03 said:
First, we need to know more about your device.
You need adb and fastboot installed(I recommend Minimal ADB & Fastboot if you don't have already), HTC Drivers.
Put your phone in download mode and do "fastboot getvar all" remove imei/sn from output and post here.
Click to expand...
Click to collapse
(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
hi yes have adb just downloaded the original rru tyed to install via sd card but it failed
glinjik said:
(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
hi yes have adb just downloaded the original rru tyed to install via sd card but it failed
Click to expand...
Click to collapse
Do the command again from download mode not bootloader
Sent from my OnePlus 2 using XDA Labs
lucyr03 said:
Do the command again from download mode not bootloader
hi cant get into download mode it comes up in red
failed to boot to download mode press vol
up or down to back to menu
then htc log
then in red
this build is for development purposes only do not distribute outside of htc without htc's written permission failure to comply may lead to legal action
Click to expand...
Click to collapse
No download mode means no way to flash. Dead phone.
hi so i persisted and tryed holding power button vol up down etc and somehow got to this
HTC Download Mode
****locked*****
htc_himauhl pvt s-on
lk-1.0.0.0000
radio-01.01_u11440792_95.00.51130g_f
opendsp-15.6.1.00.522.8994_1026
os-3.35.61.14
feb 4 2016, 13:06:46(670363)
then the following
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
then in yellow
security warning
blah blah
sd card not mounted
glinjik said:
hi so i persisted and tryed holding power button vol up down etc and somehow got to this
HTC Download Mode
****locked*****
htc_himauhl pvt s-on
lk-1.0.0.0000
radio-01.01_u11440792_95.00.51130g_f
opendsp-15.6.1.00.522.8994_1026
os-3.35.61.14
feb 4 2016, 13:06:46(670363)
then the following
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
then in yellow
security warning
blah blah
sd card not mounted
Click to expand...
Click to collapse
I can't find a ruu for your phone.
Try to unlock bootloader, flash twrp and flash any marshmallow based sense custom rom.
Your only way to revert to full stock is s-off.
Sent from my OnePlus 2 using XDA Labs
hi is it possible to unlock bootloader from adb in download mode or twrp? is it possible to get soff in this mode?
i have the correct rru but i tryed to flash from sd
so i renamed the rru to opjaimg.zip
i get to flash menu press vol up to start flash
start ui_updating
it just goes back to bootloader
this is the rru i got
0PJAIMG_HIMA_UHL_M60_SENSE70_MR_Orange_UK_3.35.61.14_Radio_01.01_U11440792_95.00.51130G_F_release_472007_combined_signed.zip
after trying again managed to get to recovery mode
android recovery
htc/htc_himauhl/htc_himauhl
6.0/mra58k/buildteam02041257
user/release-keys
use volume up/down and power
then reboot system now
reeboot to bootloader
apply update from adb
apply update from sd card
wipe data/ factory reset
wipe cache partition
power off
tryed apply update from sd card
gives following
e:failed to set up expected mounts for install aborting
e: failed to mount / devlog (invalid argument) try emmc mount
e: cant find device node for mount point/devlog
the list goes on
the goes back to recovery mode
You need to rename it to 0PJAIMG.zip
The first character it's zero(0) not O
And boot in download mode and follow the on screen instructions
Sent from my OnePlus 2 using XDA Labs
that 0 might b the problem il try that and report back thank you so far
tried the official rom just goes back to bootloader gonna try a custom rom next fingers crossed
tried flashing from sd get
255
255
fail 255
glinjik said:
tried flashing from sd get
255
255
fail 255
Click to expand...
Click to collapse
Fail 255 indicated a broken SD card as far as i know.
il give it a go with a different sd card
Hello,
i have a big problem with my HTC one M9 OS 3.35.161.12( s-on, bootloader locked)
Recovery mode is broken , i'm able to enter into download mode, but when i want to flash a zip file i have problems to enter into RUU Mode because it is in a bootloop after i give the command "htc_fastboot oem rebootRUU" , it means the phone attempts to enter into RUU mode but it keeps just restarting in the black screen with htc Logo for 2 -3 sec.
can annybody pls tell me what can i do to repair the RUU mode?