Develop Bugs

Bricked or not bricked?

I had an issue with my phone a couple of weeks ago where I'm only able to the bootloader screen and the fastboot screen. Fortunately, I got a replacement EVO 3 days later but I'm still trying to get my old phone up and running. But after trying everything I can find, still nothing.
So my question is, when do I say that the phone is officially bricked?
Sent from my PC36100 using Tapatalk

If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!

dwelder said:
If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!
Click to expand...
Click to collapse
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk

Were you using CM7 before your phone started bootlooping?

Concordium said:
Were you using CM7 before your phone started bootlooping?
Click to expand...
Click to collapse
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk

andygu3 said:
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.

andygu3 said:
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Have you tried flashing the images via fastboot?

Concordium said:
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.
Click to expand...
Click to collapse
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk

teh roxxorz said:
Have you tried flashing the images via fastboot?
Click to expand...
Click to collapse
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk

andygu3 said:
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.

andygu3 said:
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2

teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk

andygu3 said:
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.

Concordium said:
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
Click to expand...
Click to collapse
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk

andygu3 said:
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Oh crap I forgot you were the one having the issue with the boot.img. If you can't get that to work then the post I gave you will most likely not work either. It's worth a try....but I doubt it.

teh roxxorz said:
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.
Click to expand...
Click to collapse
Well sh**, that's a downer! If this is the case, I'm definitely sol! But hopefully I can get something out of the phone but I seriously doubt it!
Thanks guys for your input, again much appreciated. I will report back if I have any breakthrough!!
Sent from my PC36100 using Tapatalk

Im having the same issue
bootloop and the phone was using CM7. I was able to get to boot loader menu but can not get to recovery.
Tried to add recovery image no dice...now the phone will only charge and not boot

teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
No luck!
I know someone posted the EVO Brick_fix, I believe cutthroat but since no PC36IMG.ZIP is being recognized on my sdcard. I may officially say my phone is toast.
Any other suggestions are welcome!
Sent from my PC36100 using Tapatalk

Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk

andygu3 said:
Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Did you unbrick your EVO
I tried to use unbrick method and now phone will not boot at all
It just stays at black screen and vibrates once after pressing the power button

[Q] complete unlock process

honesly I havent rooted or unlocked my bootloader yet, i dont really have a sense of urgency. at least not till aosp roms drop.
my question is, now that the boot loader has been cracked. we should expect an untethered recovery right?
also, from what i undrstand. i have to root first, then boot loader unlock, then i can flash the tethered recovery, right?

When you root and unlock the bootloader using the methods in the dev threads it will put in CWM.
Sent from my LG-LS970 using xda premium

So I root. Unlock boot loader. N cwm is installed like magic?!
Is it the tethered version

sheek360 said:
So I root. Unlock boot loader. N cwm is installed like magic?!
Is it the tethered version
Click to expand...
Click to collapse
I honestly have no idea what tethered version is, I am assuming you can only get into it by plugging your phone in and running some type of cmd? If so, then its untethered cause I can use it anywhere.

_Epic said:
I honestly have no idea what tethered version is, I am assuming you can only get into it by plugging your phone in and running some type of cmd? If so, then its untethered cause I can use it anywhere.
Click to expand...
Click to collapse
Can you wipe, back up, etc? Exactly how did recovery wind up on your device? I'm confused.

sheek360 said:
Can you wipe, back up, etc? Exactly how did recovery wind up on your device? I'm confused.
Click to expand...
Click to collapse
The Freegee bootloader unlock process installs it for you. You can wipe, mount, flash.... it gave me an error when I tried to back up but i'm pretty sure that can be done too.

Rocket_Science said:
The Freegee bootloader unlock process installs it for you. You can wipe, mount, flash.... it gave me an error when I tried to back up but i'm pretty sure that can be done too.
Click to expand...
Click to collapse
Gotcha. Thnx

Rocket_Science said:
The Freegee bootloader unlock process installs it for you. You can wipe, mount, flash.... it gave me an error when I tried to back up but i'm pretty sure that can be done too.
Click to expand...
Click to collapse
What he said ^
Sent from my LG-LS970 using xda premium

You have to backup up to internal sd card or something like that, it's a few lines down from the normal backup.
Sent from my super fast Optimus G!!!

[HBOOT MOD] Remove the red text

YOU MUST BE SOFF TO USE THIS MOD, IF YOU DONT KNOW WHAT THAT IS YOU DONT HAVE IT. I AM NOT RESPONSIBLE FOR BRICKS DUE TO YOUR NEGLIGENCE. Now lets continue.
You can find the hboot here to download: Download
Once you download this zip, extract all of its contents. You will need to verify the md5 of the mmcblk0p18 so be sure to pull the .md5 as well. Once you have the files, open the md5 in a text editor of choice. Then, put the mmcblk0p18 into your adb folder. If its in your path, I will make the assumption you can modify this to your needs. You will now need to use the code below. Be sure you are booted into android!
Code:
adb push mmcblk0p18 /sdcard/mmcblk0p18
adb shell
su
md5sum /sdcard/mmcblk0p18
#now check the output of this command with the md5 in the file you opened in notepad. If it DOES [U]NOT[/U] MATCH, [U][B]DO NOT[/B][/U] proceed
dd if=/sdcard/mmcblk0p18 of=/dev/block/mmcblk0p18
diff /sdcard/mmcblk0p18 /dev/block/mmcblk0p18
# IF THESE DIFFER DO NOT REBOOT, try the command again. If you are not S-OFF then you will see that the files WILL differ.
Now, you can reboot and the red warning text will be gone! Enjoy!

After you do this, it will look like this (Hboot will show 1.18.9999):
In addition, phone will no longer be recognized in fastboot mode on USB 3.0 ports

kusanagi-sama said:
After you do this, it will look like this:
In addition, phone will no longer be recognized in fastboot mode on USB 3.0 ports
Click to expand...
Click to collapse
Any other side-effects???

rohov said:
Any other side-effects???
Click to expand...
Click to collapse
Just that

kusanagi-sama said:
After you do this, it will look like this (Hboot will show 1.18.9999):
In addition, phone will no longer be recognized in fastboot mode on USB 3.0 ports
Click to expand...
Click to collapse
s-off....how???....
Sent from my One V using xda premium

handryg555 said:
s-off....how???....
Sent from my One V using xda premium
Click to expand...
Click to collapse
I think you have to be one of the lucky ones to have an S-Off phone.

Can I have a more simpler method for noobo like me. Thanks anyway.
Sent from my One V

to_sukanta said:
Can I have a more simpler method for noobo like me. Thanks anyway.
Sent from my One V
Click to expand...
Click to collapse
There isn't any other simpler way than that. If you can't handle a few commands, you shouldn't be modding your phone.

Is it also possible to change the screen to diff boot logo with s-off? Or can i only remove red text?
Sent from a hand.

Snyper0012 said:
Is it also possible to change the screen to diff boot logo with s-off? Or can i only remove red text?
Sent from a hand.
Click to expand...
Click to collapse
You can change the boot animation, but you can't change the boot logo, just remove the red text.

Not entirely true. I know of a utility that converts a 480x800bmp to nbh. From there (with an eng fast boot mod,(I got a friend working on it who will be nameless so you don't all bug him)) fastboot flash splash custom.nbh
Sent from my One V using Tapatalk 2

Can anyone please please confirm if I need to boot into boot loader to run the mode or normal booting into the system would be enough to run the adb commands?? I booted into normal system but adb commands showing that device not found.

You do this in rooted android with USB debugging enabled. If you can't follow the instructions, then you shouldn't be using this mod
Sent from my One V using Tapatalk 2

simonsimons34 said:
You do this in rooted android with USB debugging enabled. If you can't follow the instructions, then you shouldn't be using this mod
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
Just asking, are there phones shipped with S-Off?As there is no method to off it by ourselves.If there are, they are indigenous to which countries?Where have they appeared?Or are they development phones?

Steam. said:
Just asking, are there phones shipped with S-Off?As there is no method to off it by ourselves.If there are, they are indigenous to which countries?Where have they appeared?Or are they development phones?
Click to expand...
Click to collapse
Some rare cases are there where the phone is factory s-off.the security is absent by default in such handsets.

Steam. said:
Just asking, are there phones shipped with S-Off?As there is no method to off it by ourselves.If there are, they are indigenous to which countries?Where have they appeared?Or are they development phones?
Click to expand...
Click to collapse
Yeah, most of the cases is when the guy received the phone from HTC as a gift... we've seen-
GB ship s-off
PVT ship s-off
And one more I don't remember
Sent from my One V

After running all the commands successfully, it is still showing there is a file difference. Is there any other way to remove this red text while booting. Please please help somebody. I''m desperate to get rid of this.

>.> learn to read. This is only for s-off phones. If you had an older phone or an unupdated one x you would of just bricked all because you didn't read
Sent from my One V using Tapatalk 2

simonsimons34 said:
>.> learn to read. This is only for s-off phones. If you had an older phone or an unupdated one x you would of just bricked all because you didn't read
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
I'm sure my One V is s-off, I've just done it few days back. I'm currently running on PA2.99, how can it be s-off, even I tried to copy the mmcblk0p18 file to the /dev/block folder manually with proper permission. Still no luck. Please help.

You are not soff. Final. Your unlocked. And you don't even know what your talking about at this point
Sent from my One V using Tapatalk 2

[MOD] Hboot 3.16.0.000 without red text on custom kernels.

This mod removes the red text from HBOOT with custom kernels.
It is a simple binary replacement of the text that would normally display with a long string of 0x20 (The character for spaces).
WARNING: THIS IS DANGEROUS, if your phone powers off while you are writing to the hboot, you CAN brick.
S-off, root, and busybox are required
Download:
http://www.cheatersedge.org/android/m8/hboot-no-red-text.img
SHA1: 8619b74b5f22459753498d89de38f47b23518f78
Installation (This can be done in normal boot mode, but booted to TWRP is a MUCH safer bet):
Code:
adb push hboot-no-red-text.img /sdcard/
adb shell
su
dd if=/sdcard/hboot-no-red-text.img of=/dev/block/mmcblk0p11
reboot

will this be persistent between rom flashes? ie. a 1 time thing? I think it should since it is its own partition right?

epsiblivion said:
will this be persistent between rom flashes? ie. a 1 time thing? I think it should since it is its own partition right?
Click to expand...
Click to collapse
Yes, it should be persistent unless for some insane reason you decide to flash a ROM with an HBOOT image built into it.

Fenny said:
Yes, it should be persistent unless for some insane reason you decide to flash a ROM with an HBOOT image built into it.
Click to expand...
Click to collapse
it would take an even more insane dev to make such a zip. I don't think I ever saw one. except maybe one time when one of the phones I was using needed firmware update to be compatible with the new android version, and the new roms included it. though it'd be safer to have it as a separate zip.

For some reason, it's giving me an error
Code:
/sbin/sh: su: not found
while booted into twrp recovery. It has no issue finding it while booted though. Don't want to mess around flashing this hboot without being in recovery. Any ideas?

captainreynolds said:
For some reason, it's giving me an error
Code:
/sbin/sh: su: not found
while booted into twrp recovery. It has no issue finding it while booted though. Don't want to mess around flashing this hboot without being in recovery. Any ideas?
Click to expand...
Click to collapse
OH no need to worry, you are already running as root in the recovery. You can skip the "su" step.

Fenny said:
OH no need to worry, you are already running as root in the recovery. You can skip the "su" step.
Click to expand...
Click to collapse
Yeah, figured it out when I noticed the hash symbol Got it working - thanks for making this!

Hey, if I make a backup of my current hboot using dd, will I be able to restore that backup using dd if I ever need to go back to stock? Thanks!
Also, if any of y'all want the stock t-mobile hboot (3.16.0.0000) let me know, I'll upload it somewhere.

crashfocus said:
Hey, if I make a backup of my current hboot using dd, will I be able to restore that backup using dd if I ever need to go back to stock? Thanks!
Also, if any of y'all want the stock t-mobile hboot (3.16.0.0000) let me know, I'll upload it somewhere.
Click to expand...
Click to collapse
Yes, that works just fine.
Sent from my HTC One_M8 using Tapatalk

It says "no such file or directory" on the first command. Am I doing something wrong?
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 12:27 AM ---------- Previous post was at 12:01 AM ----------
verysick said:
It says "no such file or directory" on the first command. Am I doing something wrong?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I forgot to copy the img to my adb folder [emoji28][emoji191] It worked. Thanks! No more red letters [emoji41]
Sent from my HTC One_M8 using Tapatalk

Thanks for this. Worked perfectly

Thank you very much Fenny for this Eazy Peazy mod!!!!
Makes reboot look soooooooo much better

It doesn't seem to work if you have a custom splash screen installed. Any way around that? Thanks for the mod anyways :highfive:

So the phone have to be on bootloader or recovery?
Sent from my HTC One_M8 using xda premium

So i am assuming that reverting the hboot to have red text, we would just flash our own Hboot dumps?

I'm assuming so.. Either way it can't hurt to put back what was already there to begin with so give it a go
Sent from my HTC One_M8 using xda app-developers app

pp085ster said:
I'm assuming so.. Either way it can't hurt to put back what was already there to begin with so give it a go
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
I just removed the "Tampered" banner (Didn't know i can do that, LOL), so really all that is left if the Red Text. i really don't care if it says locked or unlocked.

Any way to do this in the phone without a computer?
Thanks
Sent from my HTC One_M8 using xda app-developers app

Worked as said. Red warning gone. Thank you!
Phone: T-Mobile HTC M8 rooted-superCID-s-Off
ROM: Latest Cyanogen
Recovery: Lates TWRP

tony_5309 said:
I just removed the "Tampered" banner (Didn't know i can do that, LOL), so really all that is left if the Red Text. i really don't care if it says locked or unlocked.
Click to expand...
Click to collapse
How did you remove the tampered banner?

[Q] htc m8 tempered... locked... brick my devıce??

m8 is staying on my device htc hboot as in the picture. recoery does not enter, the phone will not turn on and does not see the fastboot commands. 130 error in the file is directly

gokboru09 said:
m8 is staying on my device htc hboot as in the picture. recoery does not enter, the phone will not turn on and does not see the fastboot commands. 130 error in the file is directly
Click to expand...
Click to collapse
Have you tried flashing a firmware.zip by naming it 0P6BIMG.zip and putting it on the root of SD, and you the flashing process is done see if you can get into stock recovery. If that works then you can try flashing TWRP and see if it sticks.
Sent from my HTC One_M8 using Tapatalk

couple of things
gokboru09 said:
m8 is staying on my device htc hboot as in the picture. recoery does not enter, the phone will not turn on and does not see the fastboot commands. 130 error in the file is directly
Click to expand...
Click to collapse
first of all you've posted this in the wrong section.
post right section you'll get better answers. but they will need more detail how did it get like this what was you doing at the time as it looks like your boot loader is locked but you've tampered with the firmware or recovery so what exactly have you done?

manup456 said:
Have you tried flashing a firmware.zip by naming it 0P6BIMG.zip and putting it on the root of SD, and you the flashing process is done see if you can get into stock recovery. If that works then you can try flashing TWRP and see if it sticks.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
ıts 0P6BIMG.zip where ıs ıd_? and ınstall hboot_?

agentbardall said:
first of all you've posted this in the wrong section.
post right section you'll get better answers. but they will need more detail how did it get like this what was you doing at the time as it looks like your boot loader is locked but you've tampered with the firmware or recovery so what exactly have you done?
Click to expand...
Click to collapse
ok. ıts One_M8_All-In-One_Kit_v ınstall make relock bootloader. then not open my devıce nad recovery.

gokboru09 said:
ıts 0P6BIMG.zip where ıs ıd_? and ınstall hboot_?
Click to expand...
Click to collapse
This is the wrong section for this but look here for flashing firmware http://forum.xda-developers.com/showthread.php?t=2824048
Firmware Flashing without the panic attacks...
Sent from my HTC One_M8 using Tapatalk

manup456 said:
This is the wrong section for this but look here for flashing firmware http://forum.xda-developers.com/showthread.php?t=2824048
Firmware Flashing without the panic attacks...
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
nooooo do not do this as you bootloader says your s-on so this is likely not to work and may damage your device.

agentbardall said:
nooooo do not do this as you bootloader says your s-on so this is likely not to work and may damage your device.
Click to expand...
Click to collapse
Edit: I need to get some rest lack of sleep has me slipping.
Sent from my HTC One_M8 using Tapatalk

manup456 said:
The point of that thread is for people with s-on to flash without panics.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
the first sentence from that thread.
"To anyone that is S-OFF and wanting to flash firmware I have a safe, quick, and pain free way that I have tested many times on my m7_ul_ca that works flawlessly!"

agentbardall said:
the first sentence from that thread.
"To anyone that is S-OFF and wanting to flash firmware I have a safe, quick, and pain free way that I have tested many times on my m7_ul_ca that works flawlessly!"
Click to expand...
Click to collapse
I edited my last post I need some sleep my bad.
Sent from my HTC One_M8 using Tapatalk

manup456 said:
This is the wrong section for this but look here for flashing firmware http://forum.xda-developers.com/showthread.php?t=2824048
Firmware Flashing without the panic attacks...
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
tnx. but now my devıce how ıs s off make??

manup456 said:
I edited my last post I need some sleep my bad.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
dw man happens to us all :good:
anway i think you need help from some experts and in right section i did a similar thing last month except managed to have a custom recovery and unlocked bootloader
I recon your best bet is to try and unlock your bootloader again have you tried reinstalling/manually installing the drivers on your computer? also does it make a sound when you plug it in? and what happens if you select hBoot?
Was you trying to return to stock when this happened?
---------- Post added at 03:57 PM ---------- Previous post was at 03:53 PM ----------
gokboru09 said:
tnx. but now my devıce how ıs s off make??
Click to expand...
Click to collapse
considering your version of hboot I don't think firewater will work which means you would need to use sunshine which costs money...
You would also need to be within you system(Android) and be rooted so at the moment best thing to concentrate on is getting your device a recovery / get it to connect to a PC
If you can get your Device to show up in ADB your chances of recovering it get a lot higher

gokboru09 said:
tnx. but now my devıce how ıs s off make??
Click to expand...
Click to collapse
You need to use firewater s-off or if that one does not work for you sunshine s-off works but cost $25 dollars.
The issue your going to have is you can't boot at all and you said fastboot commands not working. Are you sure you have the correct fastboot and adb files in the folder your connected to?
Firewater http://firewater-soff.com/instructions/
Sunshine http://theroot.ninja/
Sent from my HTC One_M8 using Tapatalk

Thread moved to Q&A

manup456 said:
You need to use firewater s-off or if that one does not work for you sunshine s-off works but cost $25 dollars.
The issue your going to have is you can't boot at all and you said fastboot commands not working. Are you sure you have the correct fastboot and adb files in the folder your connected to?
Firewater http://firewater-soff.com/instructions/
Sunshine http://theroot.ninja/
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
but not open my device
how ınstall firewater

gokboru09 said:
but not open my device
how ınstall firewater
Click to expand...
Click to collapse
What did you do to get your phone to this point? I need to know what you tried to do to get a better idea of how to fix it. You said the phone won't boot or go into recovery I need to figure out why so I need to know what you did.
I think your fastboot setup is wrong that's why fastboot is not working what are you typing in terminal from start to when it fails.
Sent from my HTC One_M8 using Tapatalk

manup456 said:
What did you do to get your phone to this point? I need to know what you tried to do to get a better idea of how to fix it. You said the phone won't boot or go into recovery I need to figure out why so I need to know what you did.
I think your fastboot setup is wrong that's why fastboot is not working what are you typing in terminal from start to when it fails.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
htc one m8 2014 program after you install the bootloader relock the phone did not open anymore. s off my oabilri because it is not? water does not enter the recovery, the phone will not turn .This as in the picture I do not know how I could edit. 0P6BIMG try restart when trying to install, but still the same

gokboru09 said:
htc one m8 2014 program after you install the bootloader relock the phone did not open anymore. s off my oabilri because it is not? water does not enter the recovery, the phone will not turn .This as in the picture I do not know how I could edit. 0P6BIMG try restart when trying to install, but still the same
Click to expand...
Click to collapse
I want to help but I'm not understanding I asked what commands your using because you say fastboot is not working. And your comment is very confusing.
Sent from my HTC One_M8 using Tapatalk

gokboru09 said:
..... after you install the bootloader relock the phone did not open anymore.....
Click to expand...
Click to collapse
OK... this is what I can understand.
You relocked the bootloader for some reason then you unable to boot the phone anymore and when you try to enter recovery, it boots to bootloader again. All fastboot command doesn't work.
Now ... do you still have the unlock_code.bin with you ? You need to re unlock the bootloader then other fastboot command will work like fastboot flash recovery recovery.img and etc.

ckpv5 said:
OK... this is what I can understand.
You relocked the bootloader for some reason then you unable to boot the phone anymore and when you try to enter recovery, it boots to bootloader again. All fastboot command doesn't work.
Now ... do you still have the unlock_code.bin with you ? You need to re unlock the bootloader then other fastboot command will work like fastboot flash recovery recovery.img and etc.
Click to expand...
Click to collapse
yes guys. ı have bin code. but how ınstall not understand