Database Info

HTC One S shuts down and won't turn on, no charging led.

Hi,
yesterday I pulled my One S out of my pocket, opened up the browser, made a search on google and all of a sudden, while the page was loading the screen turned off, completely black. The capacitive buttons stayed awake for 4-5 seconds, then they turned off too.
Completely dead, the phone won't turn on anymore, not even in recovery mode. If I connect the wall charger the charging led doesn't light up, although I can feel the phone is heating (as usually happens when charging).
I've tried connecting it to the pc via usb and windows after a while, detects a peripheral named "qhsusb_dload". I've read on google that this isn't any good... Anyway, even connected to the pc (for hours) the charging led doesn't light up.
No signs of life from my One S... :crying:
The phone is completely stock, unrooted.
Do someone have any hints?
Thanks.

I believe you're in download mode.
Hold the power button until your button leds start flashing and then keep holding it until they stop again. Now let go. If they don't start flashing within (say) 20 seconds, you can also let go. Hold the vol-down button and press&release the power button. Hopefully this boots you into bootloader mode. If not I don't nkow what else to suggest other than look at the unbricking thread in the development forum.

There's no way I can enter bootloader. The phone shows no signs of life (no capacitive buttons, no charging led, nothing at all)...
One thing that maybe is important: for about a month, I've been experiencing a strange battery drain. The drain used to occur even if the phone was in deep sleep (I'm sure about this because I've checked with cpuspy and anyway I hadn't installed any new apps for quite a while), at a rate of 7-8% each hour. I could leave the phone on the desk with screen off and in standby (no 3g data, no wifi, not even cellular network) and the drain was still there.
By the way, when my phone died I had plenty of battery left, about 70%.

nor-ric said:
The phone is completely stock, unrooted.
Do someone have any hints?
Thanks.
Click to expand...
Click to collapse
If it's unrooted then your warranty is still 100% intact and HTC will replace your phone no problem. What you describe just happens sometimes, more so with this phone then others I've seen.
The qhsusb_dload means it's not worth tinkering with yourself if you can just submit it for warranty.

dc211 said:
If it's unrooted then your warranty is still 100% intact and HTC will replace your phone no problem. What you describe just happens sometimes, more so with this phone then others I've seen.
The qhsusb_dload means it's not worth tinkering with yourself if you can just submit it for warranty.
Click to expand...
Click to collapse
I see, thanks. Is this qhsusb-dload issue hardware-related? If so, is it possible that they swap my S4 chip with an S3?

nor-ric said:
I see, thanks. Is this qhsusb-dload issue hardware-related? If so, is it possible that they swap my S4 chip with an S3?
Click to expand...
Click to collapse
Think of qhsusb-dload kinda like your normal PC without windows. Your phone could not find an operating system to boot into and defaulted to qhsusb-dload mode waiting for a command. Our problem is that we don't really know the commands for qhsusb-dload nor do we have the files needed to use it only the manufactures do.
They can't swap a s4 chip for a S3 version that isn't the same product.

Most likely it the micro USB charging port that's gone toast.. happened to mine exact same symptoms. I was actually unlocked, HTC dev unlocked too, running a custom ROM as well as custom recovery and splash screen. I still sent it in repair with hope of they will never be able to turn the damn thing on to discover my deeds and will replace my phone but they didn't mind, they reflashed stock rom after repair and sent it back but I was still s-off
Send it into repair mate. Best option instead of tinkering with it lol
Sent from my HTC Sensation using xda premium

Nope, there is a solution.
http://unlimited.io/qhsusbdload.htm
Sent from my HTC One S+

Ok, thanks everybody.
I'm going to try usaff22's method and if that doesn't work I'll send the phone in.
I'll let you know! :fingers-crossed:

It didn't work. The terminal waits for the device, however it doesn't respond...
I'll have to send the phone in.

Crazy idea but that sounds like the mode you go into for the downgrade so maybe the last part of it might help to get you up and running again.

Darknites said:
Crazy idea but that sounds like the mode you go into for the downgrade so maybe the last part of it might help to get you up and running again.
Click to expand...
Click to collapse
Where can I find the guide you're referring to?
Thanks.

nor-ric said:
Where can I find the guide you're referring to?
Thanks.
Click to expand...
Click to collapse
Here you go, Downgrade/Unbrick.

Darknites said:
Here you go, Downgrade/Unbrick.
Click to expand...
Click to collapse
I've read that thread: do you mean I should try the 9th point?
you can open a new terminal window and run the following command IF AND ONLY IF the phone doesn't reset out of QDL mode
Code:
$ sudo ./emmc_recover -r
Click to expand...
Click to collapse

nor-ric said:
I've read that thread: do you mean I should try the 9th point?
Click to expand...
Click to collapse
No that for flashing Hboot think you want step 12 but will need to edit the file the download has but you will need to do step 3 so you can do step 12. I have no idea if it will work but its an idea and also might be best to ask about it there too before doing anything.

thanks a lot touch of jobo i was going to get crazy :laugh:

touch of jobo said:
I believe you're in download mode.
Hold the power button until your button leds start flashing and then keep holding it until they stop again. Now let go. If they don't start flashing within (say) 20 seconds, you can also let go. Hold the vol-down button and press&release the power button. Hopefully this boots you into bootloader mode. If not I don't nkow what else to suggest other than look at the unbricking thread in the development forum.
Click to expand...
Click to collapse
that worked for me. thanks a lot
btw. maybe someone can answer this: how come that the phone goes in download mode?! I had the phone unused the last hours before I recognized it wasn't on anymore? Does this just happen? I am on CM11 Nightlies atm.

Nexus S 4G hard bricked!! want to restore

i have a nexus s 4 g from sprint. it is hard bricked. i tried to root it and change recovery.then it shut off and wont power on, light up at all. I would like to know if i am able to achieve download mode, what do i need to do, what files and how to install to return this phone to stock?? please help!!!

Take out the battery for a few seconds and put it back; then while holding Volume UP (+) press the Power Button.
See what happens...
One helpful tool is found here:
http://forum.xda-developers.com/showthread.php?t=1984849

kozmo2k4 said:
Take out the battery for a few seconds and put it back; then while holding Volume UP (+) press the Power Button.
See what happens...
One helpful tool is found here:
http://forum.xda-developers.com/showthread.php?t=1984849
Click to expand...
Click to collapse
Nothing. Happens it don't light up or power on at all. It is not reconized on computer either. It's hard bricked.

Make sure the Battery is charging...

How can I make sure the battery is charging when no lights come on at all? All I do know is I had it plugged in for a while yesterday and it got really warm. But no lights whatsoever. The screen doesn't light up at all neither does the led.

??????

There are no notification lights on the D720, but when you plug it in with a charger, you should see a battery bar on the display.
Other than that, you are probably right about hard-brick.
I, luckily, never had a "brick" on the Nexus S, so someone else with experience may wanna chime in. But Google and YouTube are your friends.
Sorry...
Sent from my NookColor using Tapatalk 4

Hey man, did you have any luck with this? I'm experiencing the same problem.

Talal916 said:
Hey man, did you have any luck with this? I'm experiencing the same problem.
Click to expand...
Click to collapse
Please help me, i have the same problem

been awhile since any action here. saved mine with JIG method once but this time it won't work ??!(why) , in search of a solution again! -> hardbrick #2 on this device!

You guys can try a USB Jig. If that does not help, I think JTAG is what you need.

Jesus... just to revive this thread (and this concept of hard bricking), I think I just accidentally bricked mine as well.
Here's exactly what I did:
One moment, it was working spectacularly - fully stock, but unlocked. I had just listed it on eBay, too.
So I ran a factory reset on it (from the Settings menu), also "erase USB storage".
Then, after it shut down for the reboot, I pulled the battery.
...
That was it. Now it doesn't turn on for anything whatsoever. No device detected on USB when plugged into PC. Remove, replace battery, hold VolUp+Power, nothing. Plug into power adapter, nothing. Nothing at all.
But the back does get lukewarm after a minute or so, as if it's alive in the head but frozen, unable to start the bootloader.
WTF? I also have 2 more of these Nexus S 4G's, and both of them seem to have Flash storage chips that exhibit the same behavior when their chips are placed in (this) working motherboard. They can't boot. When I try to "hot-flash" it by booting the bootloader then swapping the Flash chips, they can't flash anything (this is probably to be expected). So, if I can get my ONCE-WORKING phone back to life, there's a good chance I can get another working as well (one just has a cracked glass, otherwise working mainboard & peripherals).
It's old, yes, but it's a damn shame to E-waste these things for a stupid software problem like this!

UnBricking the One S

Hey guys, so yea, my friend, who's father flashed a HTC One rom on to the One S, got the phone brick. Cannot be charged, cannot be switched on, although previously, it can get access to TWRP and suddenly it just went to stone now... Any solutionS?
Sent from my eeepc using xda app-developers app

TiTAN-O-One said:
Hey guys, so yea, my friend, who's father flashed a HTC One rom on to the One S, got the phone brick. Cannot be charged, cannot be switched on, although previously, it can get access to TWRP and suddenly it just went to stone now... Any solutionS?
Sent from my eeepc using xda app-developers app
Click to expand...
Click to collapse
I am not very deep into this stuff, but had the same issue today. Luckely I was able to enter the bootloader by pressing Vol- and Power on at the same time. Maybe this will help - I hope so. Failing that, just wait a little longer, this community is always here to help and very clever!
Best wishes

You should go to the bootloader (as mentioned above) and relock it, And then install the proper RUU from here:
ht tp ://w ww. androidruu. com/?developer=Ville (S4 version, bootloader says VLE)
ht tp ://w ww. androidruu. com/?developer=VilleC2 (S3 version, bootloader says VILLEC2)
(remove spaces from the link)

So, my friend told me the phone could be charged. And so does that mean, he can go to the bootloader and ressurect it?
Sent from my eeepc using xda app-developers app

TiTAN-O-One said:
So, my friend told me the phone could be charged. And so does that mean, he can go to the bootloader and ressurect it?
Sent from my eeepc using xda app-developers app
Click to expand...
Click to collapse
Yes

I guys, just to be sure if all these steps are correct.
1. See if the phone can got to Bootloader
2. Plug in the phone to the computer
3. Download the compatible RUU
4. Relock it.
But idk how to do the fourth step. I'm using Ubuntu so drivers aren't rly required. And i heard there's 2 types of One S. The C2, no how to check whether i have either the C2 or the standard One S?
Really really appreciate if you can answer all this
Sent from my eeepc using xda app-developers app

TiTAN-O-One said:
I guys, just to be sure if all these steps are correct.
1. See if the phone can got to Bootloader
2. Plug in the phone to the computer
3. Download the compatible RUU
4. Relock it.
But idk how to do the fourth step. I'm using Ubuntu so drivers aren't rly required. And i heard there's 2 types of One S. The C2, no how to check whether i have either the C2 or the standard One S?
Really really appreciate if you can answer all this
Sent from my eeepc using xda app-developers app
Click to expand...
Click to collapse
1- To lock your phone you should enter bootloader, select fastboot, then connect the device to a computer. Now you should see "fastboot usb" white text on red background. Open a terminal and type
Code:
sudo fastboot oem lock
That's all(I assume you know what to do next)
2- if you could enter bootloader and see VLE after TAMPERED and UNLOCKED tags it's s4 variant and if you see VILLEC2, it's s3(c2) variant
Sent from my HTC One S

Doesn't do show anything on the display.
ka_55 said:
1- To lock your phone you should enter bootloader, select fastboot, then connect the device to a computer. Now you should see "fastboot usb" white text on red background. Open a terminal and type
Code:
sudo fastboot oem lock
That's all(I assume you know what to do next)
2- if you could enter bootloader and see VLE after TAMPERED and UNLOCKED tags it's s4 variant and if you see VILLEC2, it's s3(c2) variant
Sent from my HTC One S
Click to expand...
Click to collapse
OKay guys so i got my hands on the Bricked One S.. First things first, when i got it, i think some mad guys at the repair shop removed the screws on the One S and taking the top cap off kinda bend the Blue plate or whatever. Anyways, when i plugged the device to charge, theres the LED Notification lit up, then about 2 secs, it doesn't anymore. So while charging, i tried going to the bootloader, Power Button + Vol Down same time. Then suddenly, the One S's screen had a white flash on a certain part of the screen either top or bottom then it disappeared somewhat like lightining. After that flash assuming its going to turn on, i let go of the Power Button but the Vol Down. The LED Notification light was lit too but like the situtation when charging, it went off. So i can't go to Bootloader or Fastboot, but is there any way possible to ressurect this phone? Or maybe the screws were affecting the Main PCB or smth? HELP PLS. Counting on you guys

TiTAN-O-One said:
OKay guys so i got my hands on the Bricked One S.. First things first, when i got it, i think some mad guys at the repair shop removed the screws on the One S and taking the top cap off kinda bend the Blue plate or whatever. Anyways, when i plugged the device to charge, theres the LED Notification lit up, then about 2 secs, it doesn't anymore. So while charging, i tried going to the bootloader, Power Button + Vol Down same time. Then suddenly, the One S's screen had a white flash on a certain part of the screen either top or bottom then it disappeared somewhat like lightining. After that flash assuming its going to turn on, i let go of the Power Button but the Vol Down. The LED Notification light was lit too but like the situtation when charging, it went off. So i can't go to Bootloader or Fastboot, but is there any way possible to ressurect this phone? Or maybe the screws were affecting the Main PCB or smth? HELP PLS. Counting on you guys
Click to expand...
Click to collapse
I have this.. It happened after my battery went empty.. every time my battery goes empty it's a problem booting up the phone and now it doesn't respond anything... I have the same white flash you describe..

remigo said:
I have this.. It happened after my battery went empty.. every time my battery goes empty it's a problem booting up the phone and now it doesn't respond anything... I have the same white flash you describe..
Click to expand...
Click to collapse
Yeah guys this is a problem of death batt or empty one. Let it to charge for a few hours and then try again, if still the issue persist then (even is littlebit difficult) try to test it with a good batt. If it goes to bootloader consider replacing with a new batt.

Insecret said:
Yeah guys this is a problem of death batt or empty one. Let it to charge for a few hours and then try again, if still the issue persist then (even is littlebit difficult) try to test it with a good batt. If it goes to bootloader consider replacing with a new batt.
Click to expand...
Click to collapse
I have the same problem even after charging for few days, it is hard bricked, but everytime i do the vol down + power I see a greenish white flicker either at the top, middle or bottom, so looks like it may be salvageable but just not sure if there is a cheat method.any updates pls do post.

unknown
danceunlimited said:
I have the same problem even after charging for few days, it is hard bricked, but everytime i do the vol down + power I see a greenish white flicker either at the top, middle or bottom, so looks like it may be salvageable but just not sure if there is a cheat method.any updates pls do post.
Click to expand...
Click to collapse
Yup. I'm having the same issue here. And it wierd because if you try charging to the wall charger for a day the LED will have the orange light and this time if you were to try the button combination the white flash that we use to see initially stops happening. An one the orange light dissapear the button combination will start back. But the phone is still bricked or Dead.
How can we make the phone respond to the computer or even get any response itself?
Without having responding is there any way to fix this?

Sadly, i sort of sent my One S to a repair shop cos of that problem. Im getting it back soon cos another guy told me to adb reboot-bootloader. Now the saddiest thing is that my computer is running Linux with adb but it doesnt detect any device i plugged.
Sent from my GT-S6500 using XDA Free mobile app

ashe241 said:
Yup. I'm having the same issue here. And it wierd because if you try charging to the wall charger for a day the LED will have the orange light and this time if you were to try the button combination the white flash that we use to see initially stops happening. An one the orange light dissapear the button combination will start back. But the phone is still bricked or Dead.
How can we make the phone respond to the computer or even get any response itself?
Without having responding is there any way to fix this?
Click to expand...
Click to collapse
Cvolton said:
There are problems entering HBoot sometimes. Try to enter it via your computer. Plug your phone into computer and use the command "adb reboot-bootloader" twice. You should get to the bootloader
Odesláno z mého HTC One S pomocí Tapatalk
Click to expand...
Click to collapse
Try this! Update this thread for whatever situation you encounter during the process.
Sent from my GT-S6500 using XDA Free mobile app

Is there any news about unbricking? Im getting phone back from the an aftermarket repair centre. They can't repair the device weirdly enough so i thought I'd try adb again
CM11 Powered G-Wonder

[Q] Phone died, now won't boot

I have a nexus 5 that was rooted on stock rom. I have not made any changes recently to anything. I went to wake the phone and got nothing. I used vol down and power to get into bootloader. Selected start and then the phone sat on the google logo for 5 mins. I again tried vol down and power and it went off and now will not do anything with any button combo. I charged it overnight in case the battery was just dead. Nothing this morning. I then tried to plug it into the computer and it looked for drivers for QSUSB_BULK. Never seen this before. It also shows up in device manager and an unknown device with that same title. I assume that this is a "hard brick" but surprised it just came out of the blue... Is there any chance of saving the phone?

crazycd1 said:
I have a nexus 5 that was rooted on stock rom. I have not made any changes recently to anything. I went to wake the phone and got nothing. I used vol down and power to get into bootloader. Selected start and then the phone sat on the google logo for 5 mins. I again tried vol down and power and it went off and now will not do anything with any button combo. I charged it overnight in case the battery was just dead. Nothing this morning. I then tried to plug it into the computer and it looked for drivers for QSUSB_BULK. Never seen this before. It also shows up in device manager and an unknown device with that same title. I assume that this is a "hard brick" but surprised it just came out of the blue... Is there any chance of saving the phone?
Click to expand...
Click to collapse
Ah, that sucks! I'm a little confused though, because you said that the button combos do nothing now, but when you now plug it into the PC, it attempts to load different / incorrect drivers? Is the screen just black and it's trying to load the drivers still or...? Have you tried to manually load the drivers when it's showing the unknown device? Tried different USB cables and / or ports? I realize the phone is not acting correctly, but it's best to eliminate the easy things first.

I don't think its the screen, I saw it shut off then never do anything again. I have tried different cables and ports. The phone never booted back into android I know that much. Trying to load drivers or use nexus tool kit to look for adb or fastboot devices does nothing either.
I also do not get a light or anything on the screen when I plug in the charger.

Yea, I wasn't thinking it was the screen itself. I was just wondering if now the phone is "on" and attempting to load drivers, albeit incorrectly or not at all, and the screen was still dark/off? What computer OS are you using? I'm assuming Windows due to the unknown device error, but which iteration: XP/Vista/7/8/8.1? What is the error when you manually try to load the drivers - not with a tool kit? Have you tried another cord / USB port / PC? Like I mentioned earlier, it's obviously a phone issue, but sometimes just trying these different things can at least get it to load the drivers correctly where you could at least fastboot the system back to the phone.

Ok
You are on the qualcomm cpu strict mode.
Keep it like that for ten -15 minutes the battery will charge.
After that keep it plugued in and press the power button until you hear the sound that the device is disconnected.
After that vol down + power right after
Should work
Sent from my Nexus 5 using xda app-developers app

jsmasterx said:
You are on the qualcomm cpu strict mode.
Keep it like that for ten -15 minutes the battery will charge.
After that keep it plugued in and press the power button until you hear the sound that the device is disconnected.
After that vol down + power right after
Should work
Click to expand...
Click to collapse
Now this answer seems logical and only hope to me ....and
i also think that these nexus phones can't hard brick that much easily ...
Sent from my Nexus 5 using Tapatalk

crazycd1 said:
I don't think its the screen, I saw it shut off then never do anything again. I have tried different cables and ports. The phone never booted back into android I know that much. Trying to load drivers or use nexus tool kit to look for adb or fastboot devices does nothing either.
I also do not get a light or anything on the screen when I plug in the charger.
Click to expand...
Click to collapse
And there's your problem right there. You don't know what you're doing.
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5

BirchBarlow said:
And there's your problem right there. You don't know what you're doing.
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
Click to expand...
Click to collapse
I was not doing anything with the kit other they try other option to get the phone back on. I have not even installed an app on the phone in amonth it was running fine and just shut off an died. I was not playing with things I don't know. You post was an absolute waste...

crazycd1 said:
I was not doing anything with the kit other they try other option to get the phone back on. I have not even installed an app on the phone in amonth it was running fine and just shut off an died. I was not playing with things I don't know. You post was an absolute waste...
Click to expand...
Click to collapse
Alright maybe I misunderstood what you did. Have you tried reinstalling the USB driver for fastboot?

BirchBarlow said:
Alright maybe I misunderstood what you did. Have you tried reinstalling the USB driver for fastboot?
Click to expand...
Click to collapse
Of course you misunderstood, you only read one FOUR words in the tread and made your judgement.

I am using Windows 7. I tried to update the google driver in the device manager in windows but it will not accept it for that device. It only shows up as QSUSB_BULK. I have tried different cables and different ports. I have not tried another PC yet. I am going to set one up and try it just to eliminate PC issues.

crazycd1 said:
I am using Windows 7. I tried to update the google driver in the device manager in windows but it will not accept it for that device. It only shows up as QSUSB_BULK. I have tried different cables and different ports. I have not tried another PC yet. I am going to set one up and try it just to eliminate PC issues.
Click to expand...
Click to collapse
Pretty sure your device took a dump on you. Rma is your only option.

jd1639 said:
Pretty sure your device took a dump on you. Rma is your only option.
Click to expand...
Click to collapse
That is pretty much what I am thinking!

crazycd1 said:
That is pretty much what I am thinking!
Click to expand...
Click to collapse
Hate to see it but it does happen once in awhile. Emmc probably failed

Try holding the power button only for 15 seconds this is like the fail safe of pulling the battery out since we can't do that
Sent from my Nexus 5 using XDA Premium 4 mobile app

DREWHAMM974 said:
Try holding the power button only for 15 seconds this is like the fail safe of pulling the battery out since we can't do that
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have tried holding for a minute many times. All button combos..

jsmasterx said:
Ok
You are on the qualcomm cpu strict mode.
Keep it like that for ten -15 minutes the battery will charge.
After that keep it plugued in and press the power button until you hear the sound that the device is disconnected.
After that vol down + power right after
Should work
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Also while plugged in it always shows in the device manager and I never get the disconnect while holding in the power button.

blocked on black screen

Hello,
Ive tried to look for a similar situation in other thread but each case is different so i open a new one.
This morning, when i took my idol 3 the screen did not switch off when pressing power button. I thought it was battery but when i plugged charger,nothing happened except the led is on continuously. I kept power button pressed for 10 seconds. The phone vibrates shortly but still a black screen, no sound and no reaction from the touch panel. Power+vol+ did not led me to my twrp recovery. What can i do now to get it work again? The phone is rooted with Rom Eu 4.2 from murigny64 and it is the first time i encounter this issu. Thanks in advance for helping me

Tonight i disconnected the battery for about 30min then connect it again. Then i tried to start in recovery: Just a vibration but no display and no sound. I unplugged/plugged the battery again and try to start. Same problem. What the hell could happen? Maybe a deffective hardware

Insist on boot ( normal or in to recovery with vol + and power).
That is a hardware brick.
Happened to me to some times, insist, it will unbrick

persona78 said:
Insist on boot ( normal or in to recovery with vol + and power).
That is a hardware brick.
Happened to me to some times, insist, it will unbrick
Click to expand...
Click to collapse
Hopelessly i tried to restart several times before you post your message. But im gonna try again.
I charged the phone all the night but nothing better and the phone is not detected on pc so no adb action possible.
Maybe the battery is dead...

nigloud said:
Hopelessly i tried to restart several times before you post your message. But im gonna try again.
I charged the phone all the night but nothing better and the phone is not detected on pc so no adb action possible.
Maybe the battery is dead...
Click to expand...
Click to collapse
Can be, can be to... To bad if is battery.
But still trying to boot, is very difficult to.
.

thank you for advise but it's still not working. I spend about 30 minutes trying different combination of button: power pressed until it vibrate, power+vol up, power+vol down, power+vol up & down, discontinuous press of power with charger and no charger....and so on. Its a complete failure.
If it is the battery, there was no sign of weakness before (short life, random shutoff, ....) . It happen suddenly: I lock my screen before sleeping and the next morning no way to switch it on again.
I thought I would avoid problems for long with a twrp recovery, a backup and adb tools on my pc.....but for hardware issues its useless.

How can I be sure it is battery before purchasing another one ?

nigloud said:
How can I be sure it is battery before purchasing another one ?
Click to expand...
Click to collapse
There is also possibility that your screen has been broken
Sent from my 6045I using Tapatalk

belkoo said:
There is also possibility that your screen has been broken
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
If it was the screen the touch panel would work and i could sense vibration when typing the pin code no?
The led bright continuously when i plug instead of flashing slowly as it used to do when charging. That why i think its battery.

...and when i start in recovery the phone is not detected on my pc

That's hardware brick. Don't give up, try to boot, normally or in recovery, keep trying it will boot.

Have you tried to open the phone and disconnect battery? Custom ROMs made me similar issue a few times.

jani0417 said:
Have you tried to open the phone and disconnect battery? Custom ROMs made me similar issue a few times.
Click to expand...
Click to collapse
Wtf idol 3 has non removable battery haha
Sent from my 6045I using Tapatalk

belkoo said:
Wtf idol 3 has non removable battery haha
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
Therefore the back can be dismantle and we can access battery and that s what i did.
Yes i disconnected it for several hours and pluged it again but it gave me the same result. And now it doesnt vibrate anymore when i keep the power button pressed a while.
I purchased a battery on internet and im waiting for delivery to test if im right or not. Il feedback about the test.
Anyway its nice from you to look for any solution. Thanks

nigloud said:
Therefore the back can be dismantle and we can access battery and that s what i did.
Yes i disconnected it for several hours and pluged it again but it gave me the same result. And now it doesnt vibrate anymore when i keep the power button pressed a while.
I purchased a battery on internet and im waiting for delivery to test if im right or not. Il feedback about the test.
Anyway its nice from you to look for any solution. Thanks
Click to expand...
Click to collapse
I guess you did everything properly, so just one thing: at first time when I did this, I choosed the wrong cable (which didn't 'reset' the phone), so I hope you pulled both out.

jani0417 said:
I guess you did everything properly, so just one thing: at first time when I did this, I choosed the wrong cable (which didn't 'reset' the phone), so I hope you pulled both out.
Click to expand...
Click to collapse
I think i choose the good connection: This is the one over the battery with 6 wires: 2 red, 2 white and 1 black (see picture attached). I just left it with a small screwdriver to disconnect.

nigloud said:
I think i choose the good connection: This is the one over the battery with 6 wires: 2 red, 2 white and 1 black (see picture attached). I just left it with a small screwdriver to disconnect.
Click to expand...
Click to collapse
Yep, that's it

Hello,
I received the new battery today.
So i unpacked it, i unplugged the old one and plugged the new one ...and guess what happened......the same bevahiour as with the old battery: when i press the button power, it vibrate but it doesnt start neither in recovery nor in normal mode.
I just precise that the new battery is charged at 50%........:crying:
So the problem is not the battery but it was the only thing i could test by myself before sending the phone to alcatel for repair.
Im still wondering what could happen to my idol 3: It had been woking perfectly for months and one morning with no warning, it refuse to switch on. Ok sorry for annoying us and hope it wont happen with yours.
I hope alacatel will apply the guarantee although the phone is rooted and bootloader unlocked....because its a hardware issue i think.

Hello,
Just to conclude. The phone got back from repair after 10 days. They have changed motherboard, battery and also the back that was damaged. Its a brand new phone .