It will not charge, turn on, connect to pc even while using power+back button.
It's around a month old, i flash it 2 times with Floyo v0.20 using xrecovery. it has been dropped about 4 times... i attempted to install something which corrupted the os. It then crashed and i removed the battery then attempted to turn back on and it turned on a few times but i was unable to access xrecovery pushing back over and over again. I then attempted to flash using my pc and it came up with some errors and now the phone will not even turn on. I used the X10FlashTool thread that is compatible with the x8. Is the phone completely dead or is there a way to recover it.
Thanks in advance.
NOTE: These errors on the flash program wasn't while it was flashing. It was while it was trying to connect... I don't think the software killed it.
Sorry m8 to here this I have done the same and my motherboard cook it self I hope it not the same for ur phone if so you need a new board m8
my civic
I hope not too, i guess your most likely right .
Try eBay for a bricked phone so it nice and cheap and look online on how 2 replace the screen it show u how to get the motherboard out so u can replace it with the bricked phone.PS I have seen the x8 going for a 5pound becouse it was brick I got the bird a bricked x8 for 20pound
my civic
Hopefully one goes on there soon since i couldn't find any... the phone is on contract so i might be able to get it replaced since i haven't had it that long and really i've done nothing to kill it.
Try to recover it using PC Companion or SEUS
I hope it helps... Good luck bro!
I'm not sure that will work since my pc doesn't even detect it's there.. i don't eve get the sony ericsson screen when i try and turn it on.
If you want to reinstall firmware with SEUS or with FlashTool you don't need to turn phone on. Try to look here maybe this will help you:
http://forum.xda-developers.com/showthread.php?p=12442257#post12442257
I've attempted this also, it doesn't detect the phone. I will give it another attempt in a moment... FINGERS CROSSED. Other wise i will try and get a replacement.
Update: I'm now sending it away for repair, i've tried everything i can find to repair it... It's obviously completely DEAD!
m8 try holding back key(the on on the right )and plug in the usb in at the same time seus should find it just did it 2 my old phone to try and help u
sooooo hold back button and plug in your usb while holding the back key untill phone driver install just done it less than ten min ago ( my old phone didnt turn on no se logo or anything i think this is the same as you and it may help you ps it take a bit of time like 2min to start but it work back to factory 2.1
Okay i will give this a try, Hopefully it recognizes that it's plugged in if i wait.
Mine doesn't even light up when plugged in to the charger or pc.
This didn't work either, i think it's completely dead since it does nothing at all.
I'm sending it away for repair, will they know i used a custom filmware though it's dead?
erm... maybe use pc companion?
I have the same problem. I got my phone back from repair (mainboard was changed) and decided to install the floyo v0.25 ROM. Installed it succesfully, but then my phone freeze and I took the battery out, same as he did also. After that my phone was dead, the SE logo wont appear. I tried to repair it with SEUS, but It didnt change anything.
Flashtool didnt work for some reason, said that I should turn my phone on and enable something..
I installed that rom just before mine broke...
i will stick with 0.20
so 0.25 is bricking everyones phones. Good to know ._.
If I manage to fix my phone somehow I will stay on original firmware. Thanks to the 0.25 developer
One thing ive seen you all state that made it go kaboom more or less is that you remove the battery, also i belive it isnt the FW you put in since im using 0.25 without any hickups or any bugs at all (well battery icon <60% but its fixable).
So don't blame the developer, you put this in with full knowledge it could brick your phone.
Try and think about what you did and what went wrong, because i seriously doubt that you did it 100% like you should, Backup org ROM->Restore 0.25 ROM-> wipe cache->factory reset->reboot into 0.25.
Also on a side note, dont be afraid to root and put in custom ROM, learn something from it instead. every "negative" experience is GOOD experience since you learn what NOT to do then
Best of luck to you all in the future and may the custom ROM gods be with ya !
Mine is partly dead...
Hi all,
A few days ago installed the newer floyo v0.25. For a day or 2,donno how long,but till my battery flatted out completely,did not have any probs with the rom.Than after recharge,think it was not a full recharge,turned on and left it on till next morning. Still everything ok,started music app and could not turn off music (pause) as the touchscreen didnt respond. Nothing helped yet so far to get it working properly.Did a restore,full wipe did a Seus update back to stock Eclair. Now at this point lemme mention that I`ve made service tests and everything was in mint order Yes the touchscreen too.(!) Started to be happy,could do a few things like making calls,navigating within menu,then it just went back to its sad state.Cannot even unlock the screen,as there is no reaction whatsover...No matter which backup am restoring,all of them reproducing the error. Now 2 things I`ve learned so far.
1.) when I installed (restored from xRecovery) floyo v0.25, did an advance restore and restored system only,as it was mentioned in other post,its possible,because I am upgrading from floyo v0.20
2.) did not make a full wipe AFTER restored custom rom.
I donno if these 2 mistakes lead me where I am now,just hoping I need not a new motherboard or dont have any hardware issue.
Sorry for the long post,hopefully someone can learn from it,also could help me to move forward,as am still working on it to make the touchscreen back in properly.
I also had the music issue and touchscreen not responding. After removing the battery and rebooting it worked at first, but then the phone froze and didnt want to reboot after I removed the battery the second time.
There is really no sollution to fix the problem?
So that filmware killed it , thing is my phone was only just over a month old...
I've sent it away for repair will they know i used a custom filmware on the phone?
Since it's dead really they shouldn't be able to find out.
Related
Hi guys,
I've been having a few issues with my phone - thought it was due to some custom roms i was using,,,,,butmaybe not....
Recenty the phone has been rebooting on its own, at random times. The most recent one happened in the night, and now the phone is completly dead. I can not even get the bootloader screen.
Any one got any ideas, i guess it needs to go away, but would like to clear the personal info and work stuff off it. Guess i should also put stock rom back on.
Anyone had this before? could the bootloader (olinex 1.14) be currupt?
Advice would be welcome.....
update
after leaving the battery out for a long time, the phone boots, but crashes before finnishing and then wont start again.
I'm worried that if i send this back they could see that i have a non htc rom installed. Anyone had any experince wth this?
Having the same issue. Flashed Duttys ROM, then it starts. But same thing with L26. Think its the HSPL 1.56?
Which Bootload do you usw?
Frank
Did you have these issues with the stock ROM? When did the problem start - was it after flashing to a custom ROM? Have you reset twice after flashing the ROM?
Eventually my Phone completely died. I sent the device away for repair - HTC replaced the main board. When i got it back, the phone worked ok for 3 hours and then started to reboot again. Sent it back a second time, the main board was replaced, and the FPC connector was re-seated. Phone has been ok for 1 week now.
Suggest that you re-flash to the stock ROM and SPL. See if it still has the problem - if so, send it back to HTC. Here in the UK the turn-around was 6 days from notifying them of the issue to receiving the phone back.
I recieved this phone yesterday so plugged in to pc and was offered 2 updates.
The first went fine but the second crashed with an error showing in Zune.
Managed to get it to reboot and it now shows 7.0.7392.0 but is very unstable, it will reboot itself after a while and it doesn't matter what program I am using, all seem to make it crash.
It will get stuck at the "Samsung Omina 7" screen unless I take the battery out for 5 mins
I also can have problems turning the device off, sometimes it will just come back on and refuse to be turned off !
I am thinking its either overheating or corrupted software ?
Any ideas as what I could try before it goes back ?
Flash stock ROM, the update went wrong appearantly.
Try to recover in Zune maybe first
I was able to recover/roll back to previous firmware with Zune but it didn't fix the problems.
Replacement on its way for Friday
Thanks for your replies
It's your problem,not phone 's,friend.what I puzzle,why donot update to mongo beta?it runs stable and you will have a better experience.and how to flash stock rom or roll back to 7004,you should have a look at tutorial threads.
I now realise that the update failed due to the phone
crashing during the process.
I have updated the new phone and her sisters without a hitch this time
Don't want to play with Roms etc as I have had enough that on my
Galaxy S !
it seems like my problem .. I can't use my phone couse it's usually shut down by itself..
it's a hardware issue .. return it back and get a new one before you leave the place like I did ..
OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Sshaffer1992 said:
OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Click to expand...
Click to collapse
god that is really hard to read...did you make a back up before you do installation? if so do a restore, if you dint, download another rom, kernel, put it in your phone, wipe everything except internal storage via TWRP then flash rom then kernel.
G1_enthusiast said:
god that is really hard to read...did you make a back up before you do installation? if so do a restore, if you dint, download another rom, kernel, put it in your phone, wipe everything except internal storage via TWRP then flash rom then kernel.
Click to expand...
Click to collapse
lol sorry i wanted to be as pacific as possible. I did make a backup before flashing the rom. when i tried to go back to it i had the same problem with it rebooting after a few mins. i tried flashing furnace 0.0.8 kernel after installing a fresh rom but same problem. I am back on factory recovery atm is there anyway to flash twrp back to the phone without it being rooted? i tried to get the computer to communicate with the phone when it turns on but it wont seem to connect unless im in download mode or recovery.
Sshaffer1992 said:
lol sorry i wanted to be as pacific as possible. I did make a backup before flashing the rom. when i tried to go back to it i had the same problem with it rebooting after a few mins. i tried flashing furnace 0.0.8 kernel after installing a fresh rom but same problem. I am back on factory recovery atm is there anyway to flash twrp back to the phone without it being rooted? i tried to get the computer to communicate with the phone when it turns on but it wont seem to connect unless im in download mode or recovery.
Click to expand...
Click to collapse
so the phone turn on? try enable debugging in developer option, sometimes that works for me, not sure why.
Solution?
Sshaffer1992 said:
OK to start off i am not a noob at this, i have read though the forms and cant seem to find out why my phone will not come out of this bootloop. This started happening 2 days ago when I went to install a new rom on my phone. I powered down my phone, put it in recovery (Twrp), I wiped everything but internal storage. I then processed to flash the new rom. Everything went great. My phone rebooted and worked fine for the first 1 min, when i tried to pull down the notification bar the phone stuck off and went into a bootloop. I then tried to go back to my old rom and had the same problem (notification bar would not pull down). So i went to plan B and used the Back To Stock Form to restore the phone back to stock. The process went smooth as well not a problem at all. When the phone started up it allowed me to set up the voice navigation and name of the phone, as i went to update the prl and profile the phone shut off again, when it turned back on it starts normally and the goes to the lock screen where i am unable to make any iterations with the screen at all besides when it turns the blacklight off, as i try to use the knock on the LED light turns white but the screen will not turn back on (not even with the power button). Then it reboots to the lockscreen again and continues to do it until i manually force it off. I have tried everything from redownloading the firmware files, tried back to stock 3 times, hard factory reset, and reset in recovery mode. My phone is back to stock but i am unable to do anything with it unless i factory reset and go though the set up again, but even then i cant get a connection (even with wifi) without the phone shutting off and rebooting. Everytime the phone reboots the time reads 12:00am and switches to 12:01 really quick. I cant get a connection at ALL (I EVEN TRIED REMOVING THE SIMS AND AND PUT IT BACK IN AFTER BACK TO STOCK PROCESS.)
Im not sure if the application Dr.Web could possibly be making my phone do this. I did have it installed and did not remove before I tried to switch to the new rom. The anti-theft part was active.
SOMEONE PLEASE BE MY HERO AND HELP........I REALLY WOULD HATE TO DEAL WITH LG ON THIS ISSUE IF I CAN FIX IT MYSELF
THANKS TO EVEYONE THAT SUPPORTS AN ANSWER
Click to expand...
Click to collapse
I had the same problem except with me, i was just trying to change fonts manually. It went into a bootloop and i stressed dover it for hours until finally i found out that you have to use the lg mobile support tool (you can find it in one of these threads on the lg g2) and revert it back to stock. That fixed it perfectly fine. Its a lengthy process but simple. If that doesn't work you have to do what the lg mobile support tool does semi-manually with another program lg flash tool which is longer but just as simple if you follow the directions given in the thread to the letter.
androidfantic32 said:
I had the same problem except with me, i was just trying to change fonts manually. It went into a bootloop and i stressed dover it for hours until finally i found out that you have to use the lg mobile support tool (you can find it in one of these threads on the lg g2) and revert it back to stock. That fixed it perfectly fine. Its a lengthy process but simple. If that doesn't work you have to do what the lg mobile support tool does semi-manually with another program lg flash tool which is longer but just as simple if you follow the directions given in the thread to the letter.
Click to expand...
Click to collapse
I tried the lg flash tool and it put my phone back to stock but still have the same problem. I also tried lg mobile support tool but it will not recongize my phone. I did happen to get into settings and seen that both my imei and baseband are unknown. Could this be causeing the proble m? is there any way to fix it?
G1_enthusiast said:
so the phone turn on? try enable debugging in developer option, sometimes that works for me, not sure why.
Click to expand...
Click to collapse
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Sshaffer1992 said:
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Click to expand...
Click to collapse
**** thats not good at all. This happen when I was using my S3, if IMEI is gone then you could not use the phone at all, theres no way you can get it back unless you made a back up. you have to sent it in man, sorry this is as good as hard brick.
G1_enthusiast said:
**** thats not good at all. This happen when I was using my S3, if IMEI is gone then you could not use the phone at all, theres no way you can get it back unless you made a back up. you have to sent it in man, sorry this is as good as hard brick.
Click to expand...
Click to collapse
My friend also has a lg g2 that i rooted for him would i be able to use a backup from his phone. Also when i turn the phone conpletely off and hold down all 3 bottons it brings me to a hardware key settings it does shows my imei number there. If i sent it into lg would they know the phone was once rooted or does the back to stock method cover it up? Thanks for your help btw
Sshaffer1992 said:
My friend also has a lg g2 that i rooted for him would i be able to use a backup from his phone. Also when i turn the phone conpletely off and hold down all 3 bottons it brings me to a hardware key settings it does shows my imei number there. If i sent it into lg would they know the phone was once rooted or does the back to stock method cover it up? Thanks for your help btw
Click to expand...
Click to collapse
they have coders there, I'm sure if they really want to know they can figure it out. If you send it in to get it fix out of your own pockets (meaning you pay them) then i'm sure they dont care, but if you want a replacement due to warranty then it may be a different story.
Sshaffer1992 said:
Yes my phone turns on but doesnt stay on for long it will freeze and reboot i noticed my imei and baseband are unknown. Any idea what can be causeing that to happen? Could it cause the phone to reboot like it is? I am back on stock firmware again,. I did try debugging but still no luck, i was even luck enough to root it again before it rebooted but still didnt help.
Click to expand...
Click to collapse
That suck bro I'm facing the same issue right now hope you got it repaired if so feel free to share the process lol
Nba2kgod said:
That suck bro I'm facing the same issue right now hope you got it repaired if so feel free to share the process lol
Click to expand...
Click to collapse
I eneded up restoreing my phone back to stock and took it into my local sprint store it cost ne 75 dollars to replace the phone not under warranty (if u have sprint protection its free) i told them i took and ota update and it started rebooting itself. If you do get a replacement make sure u back up your efs files to a safe place on your phone. Theses files can become corrupted by flashing roms and kernals.
Sshaffer1992 said:
I eneded up restoreing my phone back to stock and took it into my local sprint store it cost ne 75 dollars to replace the phone not under warranty (if u have sprint protection its free) i told them i took and ota update and it started rebooting itself. If you do get a replacement make sure u back up your efs files to a safe place on your phone. Theses files can become corrupted by flashing roms and kernals.
Click to expand...
Click to collapse
Not under warranty? Doesn't it have a 1 year manufacturer warranty? The G2 wasn't released on Sprint until November last year so it should have been covered.
Sent from my LG-LS980 using Tapatalk
Yes its still under manufacturer warranty but when i made a repair order with lg it said it would take 2 to 3 weeks to get my phone back and if they found out it was due to being rooted and flashing roms im sure lg would of charged a arm a leg to repair it. With sprint i got a new phone in 2 days or ordering it.
My phone just restart now even i didnt use it. I tried factory reset already but still . But i havent try to cleach cache before factory. Idk how. Xd can anyone teach me or any idea how to fix this auto restart. I remove my sd card too
Thats not normal. I recommend sending/bringing it back to the store you bought it and ask for a RMA
i seen some issues too. but they tried factory reset and they said it wont restart any more. so i tried it also but still
Just return it to the shop you bought it. Its warranty
Make sure the battery is fully seated. Sometimes if its making intermittent contact, it can appear to be doing restarts. Its actually loosing power for a split second and starts back up when the battery moves back into contact. Had a buddy's phone do this, and reseating the battery fixed it.
I had the same problem with the stock rom but i flashed another rom and no problems so far !
Su1i said:
I had the same problem with the stock rom but i flashed another rom and no problems so far !
Click to expand...
Click to collapse
to behonest i want to root my phone and flash but i'm scared on my other phone i can do play it with. but on my note4 it's kinda scary XD
I had BlackDiamond.N8.PIE.V2.0 over a year on my phone and it was working with no problem.
today I decided to update my phone, first updated the TWRP to the latest version "TWRP-3.4.0-0-hero2lte" updated without any problem,
then I downloaded BlackDiamond N8 Port V10.0, wiped everything (even internal storage), and installed the ROM,
it installed successfully, wiped the caches, reboot to the system, android loaded without any issue,
after loading into android, I added my google account, and I was testing the phone, after 10min of working with the phone,
while I was testing the camera app (it's was a little laggy) my phone freezes and after a couple of seconds, the screen went black! I thought it's gonna reboot, but nothing happened.
I tried to hard reset the phone by pressing "power+volume down+home key", but it didn't work, connecting to the charger is nothing happen, there is no LED light, my phone is completely dead
does anyone have any idea why this happened? installation and booting to android was completely fine, everything worked fine, and suddenly my phone freeze and hard bricked.
you know this is not the first time I'm installing custom ROM, I'm done it before and I've always been careful, never had any issue like this, but this time really I don't know what happened and to be honest, I really love my S7 Edge, I don't want to replace it.
aalireza439 said:
I had BlackDiamond.N8.PIE.V2.0 over a year on my phone and it was working with no problem.
today I decided to update my phone, first updated the TWRP to the latest version "TWRP-3.4.0-0-hero2lte" updated without any problem,
then I downloaded BlackDiamond N8 Port V10.0, wiped everything (even internal storage), and installed the ROM,
it installed successfully, wiped the caches, reboot to the system, android loaded without any issue,
after loading into android, I added my google account, and I was testing the phone, after 10min of working with the phone,
while I was testing the camera app (it's was a little laggy) my phone freezes and after a couple of seconds, the screen went black! I thought it's gonna reboot, but nothing happened.
I tried to hard reset the phone by pressing "power+volume down+home key", but it didn't work, connecting to the charger is nothing happen, there is no LED light, my phone is completely dead
does anyone have any idea why this happened? installation and booting to android was completely fine, everything worked fine, and suddenly my phone freeze and hard bricked.
you know this is not the first time I'm installing custom ROM, I'm done it before and I've always been careful, never had any issue like this, but this time really I don't know what happened and to be honest, I really love my S7 Edge, I don't want to replace it.
Click to expand...
Click to collapse
Possibly a hardware problem. You will have to take some technician for a more accurate analysis.
Dark Stranger said:
Possibly a hardware problem. You will have to take some technician for a more accurate analysis.
Click to expand...
Click to collapse
if it's hardware, why I didn't have any problem before updating the ROM? is it possible updating damaged the phone?
one more thing, I saw some people use a dongle called USB-JIG on dead Samsung phones, that enter phone to download mode and after that flashing with Odin.
do you think it's work on my phone?
aalireza439 said:
if it's hardware, why I didn't have any problem before updating the ROM? is it possible updating damaged the phone?
Click to expand...
Click to collapse
It can occur, despite being very difficult. I already corrupted the xperia bootloader I had, but it never happened on my samsung devices. I even have a s7 edege and I am changing his rom and I never had any problems. As I said, you should take the device to an assistance center to get an idea of what really happened. Perhaps it could be a hidden problem, which was only expressed by changing the rom, or it could give the same problem with the old rom. What I can say is that a simple exchange of rom, would hardly cause a hard brick in a device.
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
aalireza439 said:
one more thing, I saw some people use a dongle called USB-JIG on dead Samsung phones, that enter phone to download mode and after that flashing with Odin.
do you think it's work on my phone?
Click to expand...
Click to collapse
You can also try, because if your device is not completely dead, it can come back to life with this procedure. But I still recommend taking the device in for a technical assistance.
There are 3 cases in this:
1. If you flashed a corrupted/wrong bootloader in twrp/flashfire or anything that doesn't blocks a wrong flash like odin. Your phone is dead for good. Only a usb jig/repair box or a local mobile technician can fix that.
2. Your phone is bugged with black screen. Installing a custom rom can cause weird things. Sometimes hard stuck with screen off/black .. now you need to wait for battery draining itself completely and then plugging in charger and trying to get in download mode. If you could go in download mode then you can reflash through odin and it will be back to normal. Although sudden turn off and then complete deadness is often a hardware failure.
3. If phone after draining completely doesn't shows life when connected to charger and can't go in dl mode then its either hardware failure or bootloader problem like in no.1 point. You will need to take it to a mobile repairer or use a repair box/jig nevertheless.
Sent from my hero2lte using XDA Labs