Hi,
I have a serious problem. My phone for some reason was working fine, but all the sudden is now stuck in HBOOT.
i have tried recovery but the phone would just shut itself down. i couldn't not use adb even though before the phone went into this state, i turned the USB debugging mode on
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
please help , many thanks
Bump, I'm having the same problem on my tmobile m8
mmmgosu said:
Hi,
I have a serious problem. My phone for some reason was working fine, but all the sudden is now stuck in HBOOT.
i have tried recovery but the phone would just shut itself down. i couldn't not use adb even though before the phone went into this state, i turned the USB debugging mode on
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
please help , many thanks
Click to expand...
Click to collapse
raphi809 said:
Bump, I'm having the same problem on my tmobile m8
Click to expand...
Click to collapse
What versions of the M8 do you have?
EddyOS said:
What versions of the M8 do you have?
Click to expand...
Click to collapse
I have a t-mobile m8, I actually started a thread over there http://forum.xda-developers.com/tmobile-htc-one-m8/help/m8-bricked-soloution-t2818678 but so far no answers either
raphi809 said:
I have a t-mobile m8, I actually started a thread over there http://forum.xda-developers.com/tmobile-htc-one-m8/help/m8-bricked-soloution-t2818678 but so far no answers either
Click to expand...
Click to collapse
In which case stick to your thread as opposed to jumping on to others, makes it easier to follow
EddyOS said:
In which case stick to your thread as opposed to jumping on to others, makes it easier to follow
Click to expand...
Click to collapse
Yes, if you have already started a thread asking for help, don't jump around.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
mmmgosu said:
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
Click to expand...
Click to collapse
What response do you get for:
fastboot devices
If it returns the device ID, than try:
fastboot erase cache
Then try to flash recovery again.
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
when i tried fastboot devices it returns an ID
but when i tried
fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
i have at&t
Maybe try to flash one of the modded hboots?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hawkysoft said:
Maybe try to flash one of the modded hboots?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do i do that?
fastboot oem rebootRUU
fastboot flash zip name_of.zip
fastboot reboot-bootloader
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hard to help you if you do not even bother to answer all the questions posed to you. As I asked earlier:
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
redpoint73 said:
Hard to help you if you do not even bother to answer all the questions posed to you. As I asked earlier:
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
Click to expand...
Click to collapse
I tried factory reset but it doesn't seem to be doing anything, just a white screen with android picture.
what do you mean by " corrupts the internal memory on modded devices?"
i tried
fastboot oem rebootRUU
but it says ...
(bootloader) [DEBUG] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(560): error 2
(bootloader) Start Verify: 3
(bootloader) [DEBUG] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.018s]
finished. total time: 0.018s
question, can i flash TWRP with 0p6bimg.zip?
If yes, can anyone provide the file?
Thanks
mmmgosu said:
I tried factory reset but it doesn't seem to be doing anything, just a white screen with android picture.
what do you mean by " corrupts the internal memory on modded devices?"
Click to expand...
Click to collapse
It means you should never ever do that (factory reset in bootloader) if bootloader unlocked, rooted, etc.. Only within the OS Settings or in recovery.
What this means, is that on a stock device, factory reset in bootloader works normally; but on a modded (rooted, etc.) device this corrupts the internal memory and renders it unable to be read or written to. This is probably why can't wipe cacher, install custom recovery, reboot RUU, etc (all are giving you errors reading data; and I think this is the reason why).
Connect the phone to a Windows PC (sorry if that is not what you use, its all I know) and use Device Manager to format the phone's internal memory. Once its formatted try again to wipe cache and flash custom recovery again.
This is great info to tuck away for future reference. How should the memory be formatted? FAT32 or exFAT?
Sent from my Nexus 10
bruce7373 said:
How should the memory be formatted? FAT32 or exFAT?
Click to expand...
Click to collapse
FAT32.
redpoint73 said:
It means you should never ever do that (factory reset in bootloader) if bootloader unlocked, rooted, etc.. Only within the OS Settings or in recovery.
What this means, is that on a stock device, factory reset in bootloader works normally; but on a modded (rooted, etc.) device this corrupts the internal memory and renders it unable to be read or written to. This is probably why can't wipe cacher, install custom recovery, reboot RUU, etc (all are giving you errors reading data; and I think this is the reason why).
Connect the phone to a Windows PC (sorry if that is not what you use, its all I know) and use Device Manager to format the phone's internal memory. Once its formatted try again to wipe cache and flash custom recovery again.
Click to expand...
Click to collapse
How exactly does one format the phone's internal memory via Device Manager?
adriankeith said:
How exactly does one format the phone's internal memory via Device Manager?
Click to expand...
Click to collapse
Couldn't actually tell you "exactly" myself as I haven't personally had to do it. But I know its been given as advice many times, and reported to work (at least for some instances of corrupted internal memory or can't mount memory).
In brief, open Device Manager, browse to the device/internal memory, and try to find the option to format FAT32.
Ok, I'm in the same pickle as person above. Let me just post the state the phone was in before everything happened. Unlocked bootloader, s-on, Android revolution HD installed (4.4.3). Friend tried to get back to stock and now the phone is stuck in hboot. Things done to phone: bootloader relocked, tried to change tampered flag without success, flashed stock recovery and boot image. Fastboot devices returns Id, storage is not recognized, adb commands do not work. I think he also tried to do factory reset while in hboot. Just stumbled upon this format memory thing, will do it once I get home. What are the steps after, can I just flash the correct ROM.zip or some moded hboot? If you can just point me in right direction I would very much appreciate it, thanks. Also if you need any additional info just ask for it
Similar problem here also,
I could really use some help guys! The new GPE 6.0 images are out on XDA. http://forum.xda-developers.com/htc...uu-m8-google-play-edition-5-1-lmy470-t3226765
I did a full wipe then I put on the rom using the zip file first through TWRP and it did install but the radio drivers failed.
So I then downloaded the system img file ruu and renamed it to 0P6BIMG.zip and now it is just stuck in a loop and will not boot into the Operating system. It will just freeze at the White HTC logo.
I press the power button and the volume up button to reset the device then push the power button and volume down button to get into the bootloader the bootloader instantly selects Hboot and starts loading up the 0P6BIMG.zip. The phone then procedes to give me the highlighted HBoot option and the message "Press <POWER> to reboot." Which then reboots right into the White HTC loading screen.
The phone is unlocked and has s-on. I have tried using ADB commands but cannot get an ID with ADB devices command.
Can someone help a brotha out?
Related
Hello
i have some problems with my HTC One X. Until 2 hours ago it worked perfectly and without problems. i didn't flash anything in the last few weeks, but theres ARHD (ICS) installed. But then suddenly it had a freeze, so i had to restart it with pressing the powerbutton for 10 seconds. Since then, it doesn't boot anymore and also i can't access the Recovery, i get a blackscreen if i try, But i come into the Bootloader, Fastboot is possible but doesn't work...
I tried to reflash the Boot.img, but there was an error: erasing cache FAILED (remote: 19000008)
I also tried to reflash the CWM Recovery but there was another error:
5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.904s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: (00030000))
finished. total time: 1.150s
So can anybody help me? All that I want is access to my virtual SD Card for saving my data, and can anybody tell me how and if I can "repair" my One X? And sorry for the bad english, i'm no native speaker...
you can try this, http://forum.xda-developers.com/showthread.php?t=1609190
Thanks, but it didn't help. When i tried to flash the images in fastboot almost the same errors as before occured...i absolutely dont know what to to now, i think i even can't relock the bootloader, flash the stock recovery and a RUU
Achsoistdas19 said:
Thanks, but it didn't help. When i tried to flash the images in fastboot almost the same errors as before occured...i absolutely dont know what to to now, i think i even can't relock the bootloader, flash the stock recovery and a RUU
Click to expand...
Click to collapse
what the error mate?
Hm, i don't really know. There are these Error-Codes, mostly "remote: 19000008" or "remote: 00000004" also with a 5 at the end, and it says "remote: not allowed" sometimes.
In short, I'm trying to factory reset the phone to it's default settings, but every attempt is met with a failed attempt. Here's the specs
HTC Incredible
Android 2.2
Locked
S-ON
Hboot 1.02.000
Software: 3.26.605.1
Baseband: 2.15.00.07.28
Upgrading using the RUU file, PB3120000_Incredible_C_hboot_1.02.0000_4.08.605.2.exe, does nothing because even when it says it succeeds, the software version is the same. Tried the PB31IMG.zip method doesn't work because I get the error, "Main version is older". Going into recovery mode and resetting from there does nothing either because that fails.
The closest method I've seen which resembles mine is from this thread, but because the phone is deactivated I can't access the market to download and install rom manager to fix what could be a corrupted recovery? On top of that, I spent over an hour working with SDK, and came to the conclusion that I'm out of my depth. If anyone could point me in the right directions.
Edit: Figured out I had the wrong zip file so when I finally got it to update to 4.08.605.2 image, the boot screen is stuck at "HTC Incredible" splash screen, so I'm to assume I bricked it?
S_K_I said:
In short, I'm trying to factory reset the phone to it's default settings, but every attempt is met with a failed attempt. Here's the specs
HTC Incredible
Android 2.2
Locked
S-ON
Hboot 1.02.000
Software: 3.26.605.1
Baseband: 2.15.00.07.28
Upgrading using the RUU file, PB3120000_Incredible_C_hboot_1.02.0000_4.08.605.2.exe, does nothing because even when it says it succeeds, the software version is the same. Tried the PB31IMG.zip method doesn't work because I get the error, "Main version is older". Going into recovery mode and resetting from there does nothing either because that fails.
The closest method I've seen which resembles mine is from this thread, but because the phone is deactivated I can't access the market to download and install rom manager to fix what could be a corrupted recovery? On top of that, I spent over an hour working with SDK, and came to the conclusion that I'm out of my depth. If anyone could point me in the right directions.
Edit: Figured out I had the wrong zip file so when I finally got it to update to 4.08.605.2 image, the boot screen is stuck at "HTC Incredible" splash screen, so I'm to assume I bricked it?
Click to expand...
Click to collapse
If you can get to hboot, its not bricked. Have you tried a factory reset from hboot since doing the update?
cmlusco said:
If you can get to hboot, its not bricked. Have you tried a factory reset from hboot since doing the update?
Click to expand...
Click to collapse
Yes, I can get to hboot, and unfortunately doing a factory reset from there didn't work either? What are my options now you think, since I ran out of ideas a while ago.
S_K_I said:
Yes, I can get to hboot, and unfortunately doing a factory reset from there didn't work either? What are my options now you think, since I ran out of ideas a while ago.
Click to expand...
Click to collapse
So am I out of options at this point, because I've exhausted every resource I could find.
S_K_I said:
So am I out of options at this point, because I've exhausted every resource I could find.
Click to expand...
Click to collapse
Try this ruu thru hboot http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip. If that dosent work i would unlock your bootloader with http://htcdev.com/bootloader. Then flash a custom recovery. Then from recovery try to do a full wipe and a flash of a rom.
How do I get access to the sim card from my computer and install the zip if the phone won't boat? Or is there a way I can still do this through hboot?
S_K_I said:
How do I get access to the sim card from my computer and install the zip if the phone won't boat? Or is there a way I can still do this through hboot?
Click to expand...
Click to collapse
Well to put the PB file on the sdcard you would need to remove it from the phone, and then use a pc to put the file on there. You would most likley need an adapter, as most card readers dont do micro sd. However you can use fastboot to flash a pb file. Place the PB file on your pc in the same folder as fastboot.exe. Then type the folowing one at a time.
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip PB31IMG.zip
Also unlocking the bootloader, and flashing a recovery only requires the use of fastboot.
EDIT: I guess i should have asked first if you have fastboot adb and their drivers setup on your pc? And if you know how to use them?
Sorry bout not mentioning I'm still a noob at this but for the most part I'm pretty tech savvy (just with iphones shhhh), I was in the middle of updating my progress, and I just finished installing SDK and recovery-clockwork-5.0.2.0-vivo.img, so now after installing the PB zip udate I got this message, "Failed (remote: 99 unknown fail)". What version of PB is this anyways?
S_K_I said:
Sorry bout not mentioning I'm still a noob at this but for the most part I'm pretty tech savvy (just with iphones shhhh), I was in the middle of updating my progress, and I just finished installing SDK and recovery-clockwork-5.0.2.0-vivo.img, so now after installing the PB zip udate I got this message, "Failed (remote: 99 unknown fail)". What version of PB is this anyways?
Click to expand...
Click to collapse
The latest 4.08.605.15. Wait that is not a correct recovery for this phone. So you are unlocked now? If so that is why the fastboot ruu failed, the bootloader must be locked.
Yea I googled it not too long ago and figured that out. So what's the right version then?
S_K_I said:
Yea I googled it not too long ago and figured that out. So what's the right version then?
Click to expand...
Click to collapse
CWM - http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/
Or
TWRP - http://dinc.does-it.net/Recoveries/TWRP_2.4.4.0/
I need to do some errands but I"ll be back in 30 minutes, Just letting you know in case you're waiting on me, but irregardless thanks for the help so far and I apologize having to put up with me. Bueno, ttys..
OK, I think I just made things worse. First off, I didn't know I shouldn't of unlocked it because now I instead of getting that error 99 when trying to mount the PB, I get the message saying, "bootloader err command error !!!" after I enter "fastboot oem rebootruu". And trying to mount it while it's unlocked I get the message, "FAILED (remote: not allowed)". Sad face all around. Also, those 2 links you gave me are broken or just aren't working for me, so I'll try to find other links in the mean time. But as far as re-locking the phone, I still get the same messages as above.
S_K_I said:
OK, I think I just made things worse. First off, I didn't know I shouldn't of unlocked it because now I instead of getting that error 99 when trying to mount the PB, I get the message saying, "bootloader err command error !!!" after I enter "fastboot oem rebootruu". And trying to mount it while it's unlocked I get the message, "FAILED (remote: not allowed)". Sad face all around. Also, those 2 links you gave me are broken or just aren't working for me, so I'll try to find other links in the mean time. But as far as re-locking the phone, I still get the same messages as above.
Click to expand...
Click to collapse
You can relock by typing in fastboot
Code:
fastboot oem lock
Or your saying you already tried that and it have an error?
The links should be working again.
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Wait, does your hboot still have the same info you posted earlier as far as software version and baseband? In othet words are you still on android 2.2? And do you have a working recovery now?
C:\Android>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.009s
C:\Android>fastboot flash zip PB31IMG.zip
sending 'zip' (3064 KB)...
OKAY [ 0.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.965s
This is while it's relocked btw.
S_K_I said:
C:\Android>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.009s
C:\Android>fastboot flash zip PB31IMG.zip
sending 'zip' (3064 KB)...
OKAY [ 0.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.965s
This is while it's relocked btw.
Click to expand...
Click to collapse
The RUU has to be capital letters in that first command. (fastboot rebootRUU)
Try with this one http://dinc.does-it.net/Stock_Images/4.08.605.2/PB31IMG.zip, i forgot that last one was built and not official.
S_K_I said:
C:\Android>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.009s
C:\Android>fastboot flash zip PB31IMG.zip
sending 'zip' (3064 KB)...
OKAY [ 0.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.965s
This is while it's relocked btw.
Click to expand...
Click to collapse
I got 4.08.605.2 installed, with radio 2.15.10.12.20. And if I understand you correctly regarding the recovery, I got clockwork installed and working.
S_K_I said:
I got 4.08.605.2 installed, with radio 2.15.10.12.20. And if I understand you correctly regarding the recovery, I got clockwork installed and working.
Click to expand...
Click to collapse
Well you could try thay ruu in the post above, or go to recovery, do a wipe, and flash a rom.
EDIT: To flash a rom thru recovery you would need to unlock again with the bin file.
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
Lol we kind of have two different things going here, and they kind of conflict. So either stay locked and try that othet ruu, or unlock again and wipe and flash a rom with cwm.
Ok, it succesfully mounted that last image you linked to me. Only thing now after it finished on the command prompt, looking at the phone now and it's sitting there with the HTC logo, a black background, and a finished green bar. Should I just reboot it or keep waiting?
S_K_I said:
Ok, it succesfully mounted that last image you linked to me. Only thing now after it finished on the command prompt, looking at the phone now and it's sitting there with the HTC logo, a black background, and a finished green bar. Should I just reboot it or keep waiting?
Click to expand...
Click to collapse
Keep waiting, mabey for 10 15 min. It may take awile and reboot a few times.
I've been trying to flash an AT&T HTC One M8 with the GPe ROM found here: http://forum.xda-developers.com/showthread.php?t=2706441
I've used this guide and everything went fine: http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
I was in the TWRP Recovery and wanted to format the internal sd card for a fresh start, so I formatted. Afterwards I was unable to get back into the recovery, for some reason I can't erase or format recovery using fastboot, erasing the cache and flashing the recovery image again only brings me to a flickering TeamWin screen, then tries to normally boot but nothing is there for it to boot into so it just sits in a boot loop.
I've tried Philz recovery as well. That works for a little bit but after 10-15 seconds the phone tries to boot normally again and I get stuck in the boot loop.
I tried running `fastboot oem rebootRUU`, that brought me to a black HTC screen and gave me the ability to use fastboot. In RUU mode, I erased the cache again and reflashed the recovery, then erased the cache again and rebooted to fastboot. Tried to boot into Recovery and was greeted with the flickering TeamWin logo and a boot loop.
Can anyone give me a hand here?
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..
http://forum.xda-developers.com/showthread.php?t=2708589
This should set you to the GPE that you were on.
If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
androidbuff123 said:
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..
http://forum.xda-developers.com/showthread.php?t=2708589
This should set you to the GPE that you were on.
If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
Click to expand...
Click to collapse
I'm trying that now, will post back with results
androidbuff123 said:
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..
http://forum.xda-developers.com/showthread.php?t=2708589
This should set you to the GPE that you were on.
If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
Click to expand...
Click to collapse
I tried that and I'm still in a boot loop. This was the output:
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.266s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.618s
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.404s
JustLikeThat said:
I tried that and I'm still in a boot loop. This was the output:
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.266s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.618s
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.404s
Click to expand...
Click to collapse
Doesn't the ruu post say that the flash will fail the first time and if you try it again it should go thru.
Sent from my HTC One_M8 using Tapatalk
androidbuff123 said:
Doesn't the ruu post say that the flash will fail the first time and if you try it again it should go thru.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, and I did try twice but got the same error both times (the error I got was different than in the example). I just realized I don't have S-Off, but am stuck in bootloader without any access to `adb`
You need to be soff
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
JustLikeThat said:
Yes, and I did try twice but got the same error both times (the error I got was different than in the example). I just realized I don't have S-Off, but am stuck in bootloader without any access to `adb`
Click to expand...
Click to collapse
You can also boot a recovery without actually flashing it. Once in boot loader try
flashboot boot recovery.img
Use the actual name of the recovery image instead of recovery.img.
Make sure the twrp or whatever recovery you are using is in the same folder.
Sent from my HTC One_M8 using Tapatalk
androidbuff123 said:
You need to be soff
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
How can I make my phone S-Off without any access to ADB though? I'm pretty much stuck in Bootloader/Fastboot
JustLikeThat said:
How can I make my phone S-Off without any access to ADB though? I'm pretty much stuck in Bootloader/Fastboot
Click to expand...
Click to collapse
if you are able to do fastboot commands.. try using the firewater s-off http://firewater-soff.com/instructions/
you may not be to do this either since you said you don't have adb. Can't help you beyond here.. If you are able to get to RUU mode.. I would suggest trying flashing RUUs since they are most comprehensive.
Did you try flashing the sense RUU?
androidbuff123 said:
You need to be soff
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
You can also boot a recovery without actually flashing it. Once in boot loader try
flashboot boot recovery.img
Use the actual name of the recovery image instead of recovery.img.
Make sure the twrp or whatever recovery you are using is in the same folder.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...
But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
JustLikeThat said:
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...
But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
Click to expand...
Click to collapse
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.
Have you tried fastboot flash boot.img?
of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
androidbuff123 said:
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.
Have you tried fastboot flash boot.img?
of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
Click to expand...
Click to collapse
Using Philz, I see that it can't mount or open anything in `/cache/`... I'm guessing that that's because I wiped the internal storage with TWRP initially. Is there anyway I can mount my phone and add the directories manually?
It really sounds like I need access to ADB but I can't run anything because nothing can mount the internal storage.
In the bootloader, what is next to OS-?
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
androidbuff123 said:
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.
Have you tried fastboot flash boot.img?
of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
Click to expand...
Click to collapse
I've tried that now. It looks as if it's trying to boot but then I just end up back in the bootloader. I'll try with a different image.
In the mean time: I had managed to get Philz CWM formatting the storage properly (with /system, /data, etc), and without any errors that it couldn't mount /cache/recovery (because I had managed to format /cache manually before it rebooted). It's still rebooting 10-15 seconds after booting into recovery, even in the middle of formatting...
I have done more exploring in between reboots and it doesn't look like there's an `/sdcard` directory that it can mount either
umjammerlammy said:
In the bootloader, what is next to OS-?
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
Click to expand...
Click to collapse
Nothing, since it was wiped earlier.
JustLikeThat said:
Nothing, since it was wiped earlier.
Click to expand...
Click to collapse
Try flashing the recovery using the htc one all-in-one toolkit. see if that helps. I'm pretty much out of ideas beyond this point.
JustLikeThat said:
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...
But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
Click to expand...
Click to collapse
Restore a stock backup in twrp then flash the att ruu
If you are in the US message me your number and I can walk you through it
Sent from my HTC One_M8 using XDA Premium 4 mobile app
UPDATE
As mentioned in my initial post, I wiped/formatted my internal memory so I have no internal file structure.
My attempts at booting into or flashing a recovery are failing after 10-15 seconds since they can't mount to anything in the internal memory.
I'm stuck in Bootloader and it seems like the only tool I can utilize is `fastboot`.
I'm currently looking for a way to restore a file structure to my internal memory.
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
What about flashing the stock recovery and then trying a factory wipe?
I want to return my at&t m8 back to stock (currently on stock rooted with one bad mod installed) so I can give the phone to my father. I dont have S-OFF and dont care about resetting the tamper flag. I have tried many methods to do so, the first being fastboot flashing the stock recovery, then fastboot oem lock, rebooting bootloader, then running the AT&T RUU. After i tried this several times, i noticed that the stock recovery never gets flashed even though it reports 'okay':
Code:
fastboot flash recovery recovery.img
target reported max download size of 1830723584 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.789s]
writing 'recovery'...
OKAY [ 0.896s]
Fastboot reboot-bootloader (both the cli command and if you go select reboot fastboot on the phone) also doesn't work, it reboots the phone normally.
Seems weird that the flash doesn't happen and that reboot-bootloader doesnt work, but nonetheless i try another method restoring a stock nandroid from http://forum.xda-developers.com/showthread.php?t=2701376 . I followed the steps, fastboot erase cache --> fastboot flash boot boot.emmc.win --> fastboot erase cache --> reboot to recovery and restore nandroid --> reboot phone. ANNDDD.... somehow I'm still on the same System/ROM as I was before all this. Also worth noting, any files I push with adb are gone after a reboot. Not sure what is going on but any help would be appreciated.
So you have root permission right ?
Try downloading the stock recovery to the device and flash it with an app called "Flashify" or sense you know how to fastboot maybe try the "dd" method using Terminal emulator to push the stock recovery assuming you know the block where recovery lives [ mmcblk0p43 ]
jball said:
So you have root permission right ?
Try downloading the stock recovery to the device and flash it with an app called "Flashify" or sense you know how to fastboot maybe try the "dd" method using Terminal emulator to push the stock recovery assuming you know the block where recovery lives [ mmcblk0p43 ]
Click to expand...
Click to collapse
Yes I have root.
Unfortunately anything that has to be done from the phone that isn't in the boot loader or recovery, is not an option at this point because it's in a boot loop (makes it to lock screen and then reboots). Sometimes it stops the loops and works for awhile, so if it does I'll give this a shot. However, is there any other method via adb/Fastboot over USB or TWRP?
Do you get the phone's ID (don't post it, just say yes or no) in response when you type: fastboot devices
If not, you have a fastboot connectivity issue. Try to re-install HTC Sync and HTC drivers.
You don't need to flash stock recovery to RUU. I think you might be mixing up your guides/methods. But if you don't have fastboot connectivity (which I suspect is the issue), you won't be able to relock the bootloader and RUU, anyway.
You can also use the bootable RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486'
But again, you need to relock the bootloader first.
redpoint73 said:
Do you get the phone's ID (don't post it, just say yes or no) in response when you type: fastboot devices
If not, you have a fastboot connectivity issue. Try to re-install HTC Sync and HTC drivers.
You don't need to flash stock recovery to RUU. I think you might be mixing up your guides/methods. But if you don't have fastboot connectivity (which I suspect is the issue), you won't be able to relock the bootloader and RUU, anyway.
You can also use the bootable RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486'
But again, you need to relock the bootloader first.
Click to expand...
Click to collapse
Device id shows when i run fastboot devices . I am Positive the fastboot connectivity is not the issue here. So i am attempting to use the bootalble RUU. Since I am S-On though, I have to relock the bootloader first. When I run fastboot oem lock I get this:
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.126s
And then it reboots the phone normally, it goes into its loop, I go back to bootloader, and it still shows unlocked.
Just noticed that if i run "fastboot getvar all" the "version-main" is blank. Weird...?
cojomojo said:
Just noticed that if i run "fastboot getvar all" the "version-main" is blank. Weird...?
Click to expand...
Click to collapse
This is very common, usually caused by older TWRP versions. Shouldn't effect anything you are trying to do, I don't think.
Its odd that fastboot devices works, but fastboot oem lock fails.
Try re-installing HTC drivers, and maybe re-installing your fastboot/adb package.
redpoint73 said:
This is very common, usually caused by older TWRP versions. Shouldn't effect anything you are trying to do, I don't think.
Its odd that fastboot devices works, but fastboot oem lock fails.
Try re-installing HTC drivers, and maybe re-installing your fastboot/adb package.
Click to expand...
Click to collapse
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
EDIT:
To clarify, I have tried this both natively on a Mac and on a PC.
cojomojo said:
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
Click to expand...
Click to collapse
Try flashing the boot.img for your device from fastboot
https://www.androidfilehost.com/?fid=23329332407584494
jball said:
Try flashing the boot.img for your device from fastboot
https://www.androidfilehost.com/?fid=23329332407584494
Click to expand...
Click to collapse
Code:
fastboot flash boot boot.img
target reported max download size of 1830707200 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.868s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.416s
Ok... looks good.... so I reboot, try to fastboot oem lock.... same issue as before. Tried to fastboot flash the stock recovery... says successful... still have TWRP. I went into TWRP, erased system, cache, etc. Reboot the phone, and its all there still. What the heck is going on.
cojomojo said:
Code:
fastboot flash boot boot.img
target reported max download size of 1830707200 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.868s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.416s
Ok... looks good.... so I reboot, try to fastboot oem lock.... same issue as before. Tried to fastboot flash the stock recovery... says successful... still have TWRP. I went into TWRP, erased system, cache, etc. Reboot the phone, and its all there still. What the heck is going on.
Click to expand...
Click to collapse
After each flash "reboot bootloader"
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Than try booting to recovery from hboot
I don't think you can flash recoveries with the bootloader locked if its locking when you fastboot oem lock,I do believe you can lock the bootloader with a custom recovery flashed before hand.
jball said:
After each flash "reboot bootloader"
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Than try booting to recovery from hboot
I don't think you can flash recoveries with the bootloader locked if its locking when you fastboot oem lock,I do believe you can lock the bootloader with a custom recovery flashed before hand.
Click to expand...
Click to collapse
Ok so, i followed that exactly. I ended up in TWRP still. Here is what I did:
Code:
Cody-Macintosh:Downloads Cody$ fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.855s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.402s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
Cody-Macintosh:Downloads Cody$ fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.621s]
writing 'recovery'...
OKAY [ 0.897s]
finished. total time: 2.517s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
Every fastboot reboot-bootloader booted the phone normally. Even tried the "reboot fastboot" option via the device. I still did the steps as you said despite this abnormality, and I ended up in TWRP still. somehow. Tried to wipe the System, Dalvik, Cache, and Data 5 times in TWRP... the phone still boots to its old system, and all the files reappear. I also tried reflashing Chainfire's SuperSU. It reported successful, tried all the fastboot and TWRP stuff again, and the same issue prevails.
Oh, and I have tried multiple USB cables for the hell of it.
cojomojo said:
Ok so, i followed that exactly. I ended up in TWRP still. Here is what I did:
Code:
Cody-Macintosh:Downloads Cody$ fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.855s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.402s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
Cody-Macintosh:Downloads Cody$ fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.621s]
writing 'recovery'...
OKAY [ 0.897s]
finished. total time: 2.517s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
Every fastboot reboot-bootloader booted the phone normally. Even tried the "reboot fastboot" option via the device. I still did the steps as you said despite this abnormality, and I ended up in TWRP still. somehow. Tried to wipe the System, Dalvik, Cache, and Data 5 times in TWRP... the phone still boots to its old system, and all the files reappear. I also tried reflashing Chainfire's SuperSU. It reported successful, tried all the fastboot and TWRP stuff again, and the same issue prevails.
Oh, and I have tried multiple USB cables for the hell of it.
Click to expand...
Click to collapse
K you said you use a type of virtual machine right.
Try installing adb/fastboot directly to your Mac and run the fastboot-mac commands and hope for a better outcome
jball said:
K you said you use a type of virtual machine right.
Try installing adb/fastboot directly to your Mac and run the fastboot-mac commands and hope for a better outcome
Click to expand...
Click to collapse
No, I dont use a virtual machine. I have adb/fastboot installed directly on my mac, and its failed. I also installed adb/fastboot on another computer I have, which runs Windows 8.1, and it fails with the same errors. I could see why you thought I meant virtual machine, so I added an edit to that post. But to clarify, I am not using a virtual machine.
cojomojo said:
No, I dont use a virtual machine. I have adb/fastboot installed directly on my mac, and its failed. I also installed adb/fastboot on another computer I have, which runs Windows 8.1, and it fails with the same errors. I could see why you thought I meant virtual machine, so I added an edit to that post. But to clarify, I am not using a virtual machine.
Click to expand...
Click to collapse
One more ridiculous question I need to ask
Do you have fastboot unchecked through your battery/power settings
---------- Post added at 10:19 AM ---------- Previous post was at 09:54 AM ----------
@cojomojo
If nothing else works maybe try what I have over in here
http://forum.xda-developers.com/showthread.php?t=2586472
cojomojo said:
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
EDIT:
To clarify, I have tried this both natively on a Mac and on a PC.
Click to expand...
Click to collapse
Strange, fastboot problems are most often a driver issue. But I agree, if you've tried it natively on Mac and PC, it would seem that drivers is not the cause.
Out of curiosity, what ROM is running on the phone currently?
jball said:
One more ridiculous question I need to ask
Do you have fastboot unchecked through your battery/power settings
Click to expand...
Click to collapse
I am trying to check to see if maybe fast boot is on. I suppose it is a possibility, now I just need the phone to stay on long enough to check.
redpoint73 said:
Out of curiosity, what ROM is running on the phone currently?
Click to expand...
Click to collapse
Running stock rooted, with one mod installed (wifi tethering). It is the 50% of the problem because it is causing the reboot loop i mentioned earlier.
******* Update **********
"Fast Boot" is turned on in battery/power settings. However, I turned it off, rebooted, and its back on. Tried multiple times and it won't stick. Thanks to all sticking with helping me out here, even as we approach 3 pages
@cojomojo
Post an update if and when you fix it and what you did to fix it so others might pass in and learn.
I'm still racking my brain thinking of any possibilities it could still be
jball said:
@cojomojo
Post an update if and when you fix it and what you did to fix it so others might pass in and learn.
I'm still racking my brain thinking of any possibilities it could still be
Click to expand...
Click to collapse
Will do for sure. Thanks for your help! I'm thinking I might try and get the phone on long enough to try flashify or something. Maybe try and get s-off???
Are you absolutely sure the bootloader is currently unlocked and you didn't previously re lock it, does it state so in the bootloader screen?
If you can still get into twrp then try flashing a nandroid back to stock from the stock backup thread. I'd also be trying a different cable regardless of whether you think the one you're using is okay.
ashyx said:
Are you absolutely sure the bootloader is currently unlocked and you didn't previously re lock it? If you can still get into twrp then try flashing a nandroid back to stock from the stock backup thread. I'd also be trying a different cable regardless of whether you think the one you're using is okay.
Click to expand...
Click to collapse
Bootloader says unlocked... so I assume it is unlocked. I suppose I could go through the unlock process again, but it definitely says "unlocked". Also TWRP flashing/restoring/anything does absolutely nothing. And I have tried 3 cables and 2 computers.
*** CLARIFICATION ****
I can get into TWRP fine, and I can restore, flash ROMS, whatever... BUT even though they report okay with 0 errors, everything stays the same, i.e. nothing in TWRP actually works. Same with Fastboot.
Hey guys,
my girlfriend has an M9. Saturday it lied idle on the table and rebooted itself. When it booted it just showed the white screen with the HTC logo and the read disclaimer warning.
I rebooted with power off and volume up and the phone just bootlooped all the time. Shows black screen with HTC Logo.
I tried to press the Vol down button on a restart but that didnt work it just bootlooped as before. Then I pressed Vol up +down and could enter the bootloader. From there I entered twrp and tried to wipe the system and then it just shows:
"Could not mount /data and unable to find crypto footer." and it failed to mount /cache , /system, /data, /devlog, /carrier , /cota , /preload and "Unable to mount storage" followed by failes in /data and cache.
Every fail have an (Invalid argument).
I also tried following fastboot commands:
format system
Couldn't parse partition size '0x0X118000000'.
erasing 'system'...
OKAY [ 0.241s]
finished. total time: 0.241s
format data
Formatting is not supported for file system with type ''.
format cache
Couldn't parse partition size '0x0X14000000'.
erasing 'cache'...
OKAY [ 0.270s]
finished. total time: 0.270s
flash zip 0PJAIMG.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2368399706 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2368399706 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2368399706 is not a multiple of the block size 4096
OKAY [ 1.015s]
writing 'zip' 1/1...
(bootloader) HOSD CL#671447
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.209s
The output of getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.161.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_96.00.51201G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: VODAP102
all:
finished. total time: 0.006s
Could someone please tell me if it even possible to rescue the phone? Is there something I forget to try or do somebody know something?
I appreciate every help i could get.
And forgive my bad english.
I think Twrp has gone mental.. If i remember correctly you have to flash back to stock. Follow flippy's thread in the general section.
Beamed in by telepathy.
Thx for the answer first.
I already tried what is shown at the spreadsheet of Flippy. I downloaded the right RUU again and gave it one more try but the same. It appears "Start ui_updating". After a few seconds the screen turns black and it appears the HTC logo on an black screen and it vibrates and turn black agan and again the logo with vibration. If i immediatly try to flash it a second time, itcontinues,shows name of system types but the percent is still 0. When it reaches a certain system type (after 10 or 12) it reboots to the white screen with the green HTC logo and the red disclaimer and stuck there.
Do you have an idea?
I have the same error. We have to do something and solve this. Can you solve it?
you can also just get a backup for twrp, which is matching your cid/mainversion, wipe everything except your internal storage and restore the backup
Like i said at the beginning, its not possible to wipe the partitions. They cant be mounted by twrp. I tried already to install an TWRP Backup with the right CID but even that failed because twrp couldn't write to the partitions.
THX for your answers
Ah fock, at first remove your imei from first post, then tell me if your phone is s-offed or not
Sent from my HTC One M9 using XDA-Developers mobile app
Oh sry overlocked that the imei was there.
The phone is s-on.
get stock recovery for your mainversion/cid, re-lock the bootloader, and flash a signed firmware matching your cid/mainversion, and flash with fastboot oem rebootRUU
then fastboot flash firmware nameofthezip.zip and do this a second time and then fastboot erase cache and reboot into download mode, unlock bootloader again and flash twrp and you should be able to wipe everything
DeeZZ_NuuZZ said:
get stock recovery for your mainversion/cid, re-lock the bootloader, and flash a signed firmware matching your cid/mainversion, and flash with fastboot oem rebootRUU
then fastboot flash firmware nameofthezip.zip and do this a second time and then fastboot erase cache and reboot into download mode, unlock bootloader again and flash twrp and you should be able to wipe everything
Click to expand...
Click to collapse
It wont work. Phone dont let us to write anything
We cant change cid, mid, lock and unlock bootloader. It is emmc issue. Emmc have to change.
P.s. my phone is s-off.
degerli43 said:
It wont work. Phone dont let us to write anything
We cant change cid, mid, lock and unlock bootloader. It is emmc issue. Emmc have to change.
P.s. my phone is s-off.
Click to expand...
Click to collapse
you should be able to fix it with an install of a RUU. s-off has more chances for that.
the other guy should try to flash the firmware zip in RUU mode, not just normal mode. it should work.. if not he has to get a RUU, if that doesn't work.. yea only RMA or how it is called for you should help. if they won't fix it, sell the device, and get another one
DeeZZ_NuuZZ said:
you should be able to fix it with an install of a RUU. s-off has more chances for that.
the other guy should try to flash the firmware zip in RUU mode, not just normal mode. it should work.. if not he has to get a RUU, if that doesn't work.. yea only RMA or how it is called for you should help. if they won't fix it, sell the device, and get another one
Click to expand...
Click to collapse
When i type fastboot oem rebootRUU the phone rstarting rebooting continuously so i cant flash anything. It s very expensive device here and i love it. I will be so sad if it wont fix
DeeZZ_NuuZZ said:
get stock recovery for your mainversion/cid, re-lock the bootloader, and flash a signed firmware matching your cid/mainversion, and flash with fastboot oem rebootRUU
then fastboot flash firmware nameofthezip.zip and do this a second time and then fastboot erase cache and reboot into download mode, unlock bootloader again and flash twrp and you should be able to wipe everything
Click to expand...
Click to collapse
Ok when i type fastboot oem lock in the download mode, it restarts and stops again in the bootloop on the HTC logo with blackscreen. If I press Vol UP+DOWN I can see that the device is still unlocked.
Do you have any other ideas? And thx for your help
VGLink said:
Ok when i type fastboot oem lock in the download mode, it restarts and stops again in the bootloop on the HTC logo with blackscreen. If I press Vol UP+DOWN I can see that the device is still unlocked.
Do you have any other ideas? And thx for your help
Click to expand...
Click to collapse
Get the proper HTC fastboot files and try with that...if that doesn't work, your phone is dead..I can't help further, sorry
Sent from my HTC One M9 using XDA-Developers mobile app
Hi, its not possible to enter RUU or to relock or Flash the Phone. It seems its gone dead by itself. Nevertheless thank You for your help .