Related
Didn't even flash or root yet and my 32 grey GT died last night. It had been working great and was getting ready to flash pershoots kernel this weekend. Last night I plugged in after shutting it down like I do every night. Today when I went to turn it on nothing. I tried holding down the power button for a while and still nothing. I tried holding down volume buttons with power for extended period still nothing. I even tried plugging into different outlet to see if something happened with outlet and maybe drained the battery overnight. Luckily I got it from Fry's two weeks ago on Friday right when they came out and Fry's has a 15 day return policy but this makes me a little concerned... and that's cutting it a little too close.
Has anyone heard of things like this happening with the GT? I'm thinking I may need to see if they'll still sell me the extended warranty. I babied this thing and hadn't even flashed anything on it yet. I'm a little concerned about the reliability of the hardware... I'm not usually the one with the needle in the haystack device that goes bad but who knows... I'm already in withdrawal without it.
Is there anything else I can try before I take it back? Maybe try plugging it into the computer instead to see what happens? I can't really see what else I could do since this thing doesn't have a removable battery. If it won't power on I can't imagine there's much I can test with the SDK dev tools from the PC using the usb cable?
plugged it in with usb...
I do hear the sound of a device being plugged in on win7 when I plugged GT in and got the driver message in tray. GT still won't turn on. When I hold down the power button every about 6 seconds my windows machine machine makes the same sound you get when plugging in a usb device in addition to an extra sound at the end.
[email protected] well I guess it's going back tomorrow.
You got the sleep of death. This is a honeycomb bug that i have personally experienced in the xoom, transformer, and the GT. The way to fix it is to unplug the GT, press the power button down by itself and hold it until the you see the screen turn on and startto boot up. It may take 15 seconds or more.
If that doesnt work, plug it into the wall outlet and try the process again. If that fails also, unplug it again and try the process once more.
That combination seems to work for everyone. The only exception would be if the battery is completely drained. You would need to plug it into a wall charger for a few hours and let the battery charge, and then try the process again.
I dont know why this hasnt been fixed by google yet, its really annoying. I thought 3.1 would fix it but it didnt.
you should have post this on the general thread, but why dont you return it for a different one? problem solve...
Android Development is not for your Questions or Problems Please post in the correct forums
Moving to General
I think you got the battery drained .. for some odd reasons the android has leaky power consumption even when shutdown on occasions ..
Charge it up for a while .. wait .. correction LONG while ..
Hope that is the problem
Exactly the same problem, I have tried the hold power button but it is not working... any other work around?
Please Help
I chatted with a rep from Samsung last knight and he told me that I needed to leave the Tab charging for at least 6 hours and then try again... so I'll let you know if that did the trick... hope it does...
I've actually had this happen on two different 32GB Galaxy Tabs (the original one I purchased and its replacement). After powering the device down it would not boot up.
In both cases it happened about 3 days after receiving the tablet and with 80-90% battery charge remaining. I tried additional charging, holding the power button down for an extended period of time, and attempting to boot into download mode - everything failed to bring it back to life.
I'm not sure what triggers this condition my only suspicion was that it may have something to do with enabling encryption on the device. On the second tablet I didn't have time to do much customization or install many apps but it ended up dying shortly after enabling encryption.
Wow. This happened to me yesterday with my 16gb from Sprint. Had come unlocked,yesterday 3 days in, died. I tried all the suggestions above to no avail.
Took it to corporate today. Now waiting on replacement.
bumming*
Hope next one is unlocked
Edit**** worked. Lol. Guess I didn't try it again today after I tried charging it last night.
About 15 to 20 seconds and she's back!!! Excellent! ! Thank you so much.
Not sure now whether to replace it.
With another.
Sent from my PC36100 using XDA Premium App
So I woke up this morning and went to charge my nexus 4, which had around a week of life, only to be greeted with a flashing red light on its LED. It was working perfectly fine up until now, but now it doesn't turn on, it doesn't do anything if I try a hard reset (power + volume down) and charging it with via USB or AC only shows the red flashing LED, with no charging icon at all.
I have absolutely no idea why did it decide to spontaneously die, it didn't even leave the house yet because I was too paranoid I would drop it Is there anything I can do? Any ideas? It looks like getting a replacement is my only option but I wanted to ask you guys if by any chance there's anything else I could try.
have you rooted it or flash anything into it? Overclocking it or something? what have you done to it in the period of a "week"?
Nevermind, I managed to boot into recovery mode after pressing vol.down+power for about 40 secs while plugged to AC. It looks like the battery depleted completely and that was causing the red led — why did the battery go down to 0 while the phone was off is completely beyond me though. (FWIW I did not root the device, didn't flash anything, and didn't overclock it)
I had the same thing happen to be just now. Yesterday my battery died at 2% so I shut it off. I didn't charge it that night. Today I went to plug it in and I got a red flashing led. However after about 3-5 minutes of the charger the regular white charging battery symbol came up on the screen. I think the battery was just really dead.
i got my n4 today, had an gnex before
so i unlocked my phone, rooted and installed cwm
i flashed xylon rom and trinity kernel any 10, and everything was fine, like it was on my gnexus
after a couple of hours i pressed the power button to unlock the screen but nothing happend.
phone seems to be dead, pressing power button for 10 seconds do nothing
when i plug it into charger, the led is blinking red all the time, but phone wont turn on
do you think the device is broken?
i am really ****ed up, now wtf is the quality of that?
used it for 3 hours and its broken?
any idea is welcome..(
Nexus 4 DEAD... possibly not charging.
I have this exact same issue... but trying the volume down+power key or trying the power key by itself does not do a thing. The phone will only turn on for a couple of seconds and then die. I have been trying to charge it for a couple of days now with no luch.
I am overseas and just got my phone, which was thoroughly tested by my brother in the US, but it has been off the charger for a couple of weeks until it got to my hands... Is there any reset button or anything else that I can do if I open it???
Please, sending it back will be a major hassle, thank you.
As long as you are properly charging from a source that can provide at least 1.2A, you should be able to charge the phone back up.
Make sure you're not using an Apple charger, charging from a computer, or charging with a wall adapter that is rated below 1.2A.
pa.pn2 said:
i got my n4 today, had an gnex before
so i unlocked my phone, rooted and installed cwm
i flashed xylon rom and trinity kernel any 10, and everything was fine, like it was on my gnexus
after a couple of hours i pressed the power button to unlock the screen but nothing happend.
phone seems to be dead, pressing power button for 10 seconds do nothing
when i plug it into charger, the led is blinking red all the time, but phone wont turn on
do you think the device is broken?
i am really ****ed up, now wtf is the quality of that?
used it for 3 hours and its broken?
any idea is welcome..(
Click to expand...
Click to collapse
Perhaps a kernel related problem? Phone is still very new, devs might have to sort out some shady stuff going on. There will and can always be a certain danger when flashing custom kernels, especially with a device that new.
This just happened to me right when I was demo'ing the 8GB to a buyer since I'm selling it back as I was able to order a 16GB on the last re-offering from Google, (so I don't need two Nexus phones). Hands were sweating when it wouldn't power on, so I grabbed my charger, plugged it in, and then it started flashing a red light. Eventually it turned on after about 5 mins, finally. Battery graph showed 90% charge before it turned off, then 0%, then started back now at 10% charge. This was after powering it off and leaving it in the box since only Tuesday.
Really strange issue... I actually remember something similar happening to my Mom's HP Touchpad a few months back as well. Had to plug it in for about 40 mins after she apparently turned it off and let it sit for a couple weeks during which time it discharged completely. Guess this is the bad part about non-removable batteries lol. Though my iPod touch 2G does sit here with next to no charge and it always powers on without fail.
Happened to me just a few minutes ago, luckily got it turning on again. Weird.
Im using franco kernel and now im scared thanks to this thread...
Which version you have? 8Gb or 16Gb? 14 nov or 14 dec?
Overdose1986 said:
Im using franco kernel and now im scared thanks to this thread...
Which version you have? 8Gb or 16Gb? 14 nov or 14 dec?
Click to expand...
Click to collapse
16GB, Nov 14.
I have the same problem i call the Google support and i became a brand new device.
It's okay but the Christmas holidays are the big problem dammit i must wait
Somewhat a similar situation..and its 2 days ... Phone not turning on ((
XX-RAZOR-XX said:
Somewhat a similar situation..and its 2 days ... Phone not turning on ((
Click to expand...
Click to collapse
call google for an rma
i did it on monday, new device arrived friday evening. really nice support from google...
pa.pn2 said:
call google for an rma
i did it on monday, new device arrived friday evening. really nice support from google...
Click to expand...
Click to collapse
Rma not possible.... .... Purchased this from google USA to india..and it already passed 15 day grace.....
lewis_saint said:
I have a Blue Angel device.
Thanks for your reply,
Lewis
Click to expand...
Click to collapse
That sucks... Several people have reported that their phones started to work again just by doing nothing. I hope you somehow manage to bring it to life.
Sent from my Nexus 4 using Tapatalk 2
Same issue here.
I didn't fina a solution. I've kept the phone connected to the charger for a wole night but it's not booting anymore. I'b only able to enter in fastboot mode pressing vol down + power and connecting it to PC.
L.
This happened to me about 3 days ago while running Antutu with franco kernel r19
My phone completely depleted its battery all the way from 98%. I was able to recover it by connecting my charger for 3 mins and powering on the device with the charger connected. I let it charge for about 10 mins(It refused to charge above 3%).
So i disconnected the charger and restarted the phone. Lo and behold, my battery was back to 98%..
I have been reading lots of threads and i don't seem to be the only one that experienced this issue while running Antutu. Although i have run Antutu multiple times after restart and the problem has not replicated itself..
At first i thought Franco kernel was the culprit but this also happened to people who were completely stock..Leads me to believe that this could be a hardware issue...Lg and Google better figure out what is going on because this could lead to bad publicity and furthermore push people who are currently on the fence regarding a purchase of this device further away.
I have the same issue since this Monday. I still cannot power it on or access fastboot mode.
It happened after I updated to Franco R20 from R19. I still run stock and never OC'ed.
How can I unroot and lock the phone without being able to access fastboot or bootloader?
darll said:
This happened to me about 3 days ago while running Antutu with franco kernel r19
My phone completely depleted its battery all the way from 98%. I was able to recover it by connecting my charger for 3 mins and powering on the device with the charger connected. I let it charge for about 10 mins(It refused to charge above 3%).
So i disconnected the charger and restarted the phone. Lo and behold, my battery was back to 98%..
I have been reading lots of threads and i don't seem to be the only one that experienced this issue while running Antutu. Although i have run Antutu multiple times after restart and the problem has not replicated itself..
At first i thought Franco kernel was the culprit but this also happened to people who were completely stock..Leads me to believe that this could be a hardware issue...Lg and Google better figure out what is going on because this could lead to bad publicity and furthermore push people who are currently on the fence regarding a purchase of this device further away.
Click to expand...
Click to collapse
Hello.
When I try to turn on my N4, I hold power button, and after about 10 seconds Red light blinks (just once, if it's connected to USB that 1 blink last for 3 seconds, if connected to wall, it's just quick 1 blink. If it not connected anywhere there is no action at all, it just stays dead, no blinks, nothing). Same if I try to go in bootloader by holding volume down+power.
This happened after I successfully installed CM12, with no errors. Then I rebooted my phone, and it just stayed black as it is now. Battery was around 25~30% that time, and phone was connected to USB.
Did I bricked my phone totally? I am now trying to charge it up already for 1 hour... but it nothing changes.
I have searched here for similar problems, but couldn't find solution...
Edit: Charging already for 10h+ , still same..
Edit2: I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Edit3: I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".
easy fix
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:
zelexon said:
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:
Click to expand...
Click to collapse
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.
I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Cracken6 said:
I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Click to expand...
Click to collapse
I had the same problem a year ago, I tried to remove the battery, charging all night, and other solutions that I found online and no one worked.
Finally I found here in XDA a user with the same problem and his solution was charger the phone with a wireless charger, a friend of mine has one and I put the phone to charge and after a few minutes the screen goes on and the phone was charged, then I press power button and the nexus run again.
Hope this works.
Sorry for my bad English, I'm from Spain.
Good luck.
(I bought a wireless charger in case it happen again)
I don't know anyone with wireless charger. I already ordered a new battery, and then I probably will get wireless charger also. Ty.
But this problem is very weird if you think so.. I think it happened because of many aspects together:
1) Battery was already below 30%
2) I pretty regularly charge phone with USB (won't do it again)
3) It was connected to PC USB in same time.
4) I installed CM12 ROM in same time
So main reason I think is USB, that I restarted phone while it was on pretty low battery and with USB connected.. phone restarted and got invalid voltages and couldn't even boot up or charge phone. I also found an article which says, minimum voltage, when phone battery has 0%, it's 3.0V, so I was below that.. it just screwed everything and battery died. Well, I am not sure for 100% that it's battery fault, but I hope so, I really love my N4 and still wanna use it for long time, I hope it's not dead phone, just a dead battery. Lets see! I will update this thread , when I get my new battery (less than month probably).
Sorry, my english is also not perfect. I am from Latvia.
I was playing when it happened to me. The phone was very very hot and the battery was around 70%. When I put in the wireless charged and I can reboot the phone the battery was at 65%, so it had charge but the phone won't boot.
I charge my phone almost every day, sometimes with AC, others with USB (plugging to PC) or wireless that depends of my needs
I hope you can fix it. Good luck.
Btw. Do you know if battery charges with wireless charger, if it's removed from the phone?
Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.
Flipz77 said:
Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.
Click to expand...
Click to collapse
The battery will charge with a NCF Charger
Major Issue Google
This "Nexus SOD" issue is showing up on many sites across the Internet. I have multiple "Nexus" devices including 2 Nexus 4, 1 Nexus 5, 2 "Nexus 7 2013". It suddenly started out of the blue with one of my Nexus 4 phones. Symptoms included rapid battery discharge. I am using Lollipop 5.1 on all devices. There are many claims as to the cause, Hardware Motherboard, Power Button etc. Others claim it is "Software Related" or App Related. The problem effects Nexus 4 and Nexus 5 phones. I have ordered a new motherboard for my nexus 4 device and see if that makes a difference.
This problem should warrant a "Major Android Lollipop Crisis Team" by Google to investigate the cause and let us know what it is and what Google is doing to solve the problem before moving to announce "Android M". This issue needs to brought up and actively pursued at the upcoming "Google I/O Conference" by the strong Android Developers Groups to press for "Formal Action"
charging method
Cracken6 said:
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.
Click to expand...
Click to collapse
I had this problem a long time ago and my fix worked for me after doing a little research it seems like this is a case called battery total discharge. The fix was simply to charge your phone using the wall adapter that came with your phone (I still use my old apple cube wall thing) and to wait for the red light to appear then wait about ten minutes before trying to reboot.
I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".
Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help
AndRe5575 said:
Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help
Click to expand...
Click to collapse
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...
Cracken6 said:
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...
Click to expand...
Click to collapse
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved
as9333 said:
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved
Click to expand...
Click to collapse
Just tried booting without battery, and connecting to wall. Same - red light blinks once, after I hold Power button or Power+Volume down for about 15 seconds. If I keep buttons pressed, it just repeats every ~15 seconds.
Power buttons works fine.
After I checked that Device manager thing in google.. it looks very bad.. phone is dead.. probably need to change motherboard. I am just shocked, how this could happen... I didn't receive any errors during CM12 installation. Phone just instantly died after restart.
Last night I left my phone charging overnight.Today morning when I woke up phone was working.I opened snapchat and phone got stuck.I gave it some time but the screen turned off after a while and now the phone is dead.No charging animations,no recovery mode,no flashing LEDs,NOTHING !! I have bought phone from 3rd party seller(Flipkart - Google's official sales partner here) coz Google rarely had the phone in stock. Also my 1 year warranty is also over.
akshaysalunke13 said:
Last night I left my phone charging overnight.Today morning when I woke up phone was working.I opened snapchat and phone got stuck.I gave it some time but the screen turned off after a while and now the phone is dead.No charging animations,no recovery mode,no flashing LEDs,NOTHING !! I have bought phone from 3rd party seller(Flipkart - Google's official sales partner here) coz Google rarely had the phone in stock. Also my 1 year warranty is also over.
Click to expand...
Click to collapse
Do you mean it won't power on at all? If so, hold the power button only down for 2-3 minutes or until it boots, or not.
If you meant it starts but gets stuck at the Google (no startup animation) and you cannot access recovery mode, that is totally different.
Connect it to a PC and see how it is detected in Device Manager.
v12xke said:
Do you mean it won't power on at all? If so, hold the power button only down for 2-3 minutes or until it boots, or not.
If you meant it starts but gets stuck at the Google (no startup animation) and you cannot access recovery mode, that is totally different.
Connect it to a PC and see how it is detected in Device Manager.
Click to expand...
Click to collapse
I tried holding power button for several minutes. Nothing .
It does not show any signs of life, and its definitely not stuck in a bootloop.
Also got nothing in device manager too , not even EDL 9008 Mode.
akshaysalunke13 said:
I tried holding power button for several minutes. Nothing .
It does not show any signs of life, and its definitely not stuck in a bootloop.
Also got nothing in device manager too , not even EDL 9008 Mode.
Click to expand...
Click to collapse
Seems like after charging all night, the battery would be full. Never heard of a 6P dying on the spot with a full battery. Were you using a stock charger or aftermarket? Wall charger or something else? I'd put it on a *different* wall charger overnight and try the long power button press again. At least 2 minutes.
v12xke said:
Do you mean it won't power on at all? If so, hold the power button only down for 2-3 minutes or until it boots, or not.
If you meant it starts but gets stuck at the Google (no startup animation) and you cannot access recovery mode, that is totally different.
Connect it to a PC and see how it is detected in Device Manager.
Click to expand...
Click to collapse
v12xke said:
Seems like after charging all night, the battery would be full. Never heard of a 6P dying on the spot with a full battery. Were you using a stock charger or aftermarket? Wall charger or something else? I'd put it on a *different* wall charger overnight and try the long power button press again. At least 2 minutes.
Click to expand...
Click to collapse
Stock charger. The charger works fine as i have checked it with other phones.
Either your charging port is bad in the phone has no juice and died. Or the battery is bad and come morning it died because of the charging all night. Or possibly the power button connection is bad internally maybe broken and can't turn on. I had a bad power button
dontbeweakvato said:
Either your charging port is bad in the phone has no juice and died. Or the battery is bad and come morning it died because of the charging all night. Or possibly the power button connection is bad internally maybe broken and can't turn on. I had a bad power button
Click to expand...
Click to collapse
How did you know it was a bad power button?
I have a similar problem as the OP. If I shut my phone off I can't usually get it started for about a day or 2. I'm starting to think I may have a bad power button as well.
*Edit*
It can't be a bad power button on my unit cause it works flawlessly with the phone on. I'm stumped.
akshaysalunke13 said:
Last night I left my phone charging overnight.Today morning when I woke up phone was working.I opened snapchat and phone got stuck.I gave it some time but the screen turned off after a while and now the phone is dead.No charging animations,no recovery mode,no flashing LEDs,NOTHING !! I have bought phone from 3rd party seller(Flipkart - Google's official sales partner here) coz Google rarely had the phone in stock. Also my 1 year warranty is also over.
Click to expand...
Click to collapse
I guess the battery has been dead coz I have faced similar situation with my HTC ONE X+ using it for just a year and the battery got swollen and it's completely dead. I went out to a repair shop nearby and after opening the mobile, the battery was completely swollen and the technician just replaced a new battery and it did boot up and worked fine. So from my experience I guess it's the battery that got damaged completely (dead) and you need to replace the battery. Hope this information is helpful
jassun16 said:
I guess the battery has been dead coz I have faced similar situation with my HTC ONE X+ using it for just a year and the battery got swollen and it's completely dead. I went out to a repair shop nearby and after opening the mobile, the battery was completely swollen and the technician just replaced a new battery and it did boot up and worked fine. So from my experience I guess it's the battery that got damaged completely (dead) and you need to replace the battery. Hope this information is helpful
Click to expand...
Click to collapse
You couldn't tell the battery was swollen before the phone was opened up? I wasn't aware until recently that this was a potential problem with the 6P but since other people have reported the same I guess it can be added to the list.
Chewmasey said:
How did you know it was a bad power button?
I have a similar problem as the OP. If I shut my phone off I can't usually get it started for about a day or 2. I'm starting to think I may have a bad power button as well.
*Edit*
It can't be a bad power button on my unit cause it works flawlessly with the phone on. I'm stumped.
Click to expand...
Click to collapse
My job involves troubleshooting electronics with circuit boards all the way up to 3 phase hv. It's probably likely a power issue which is either the battery, screen, board, switch, or connection. But the most likely are the forementioned.
I got it diagnosed from Huawei Service Centre at nominal charges.They say motherboard is fried.
akshaysalunke13 said:
I got it diagnosed from Huawei Service Centre at nominal charges.They say motherboard is fried.
Click to expand...
Click to collapse
Hello sir im having the same condition as of you ,how much did the motherboard replacement cost you ??
Now my nexus 6P also having same problem
yep. happened just now. stock unrooted rom and all. 8.1 beta working flawlessly, and suddenly phone dies.
i get the same one.....phone was working fine while using whats app....and then suddenly off then never on again.
no charging
no recovery or bootloader
i tried all the way like holding power(force reboot) but nothing helps...
now its showing (QDLOADER 9008) in device manager
any chance to fix it back????
Thanks v12xke! Holding the power button worked like a charm! I still don't know why it blacked out on me but it is working now.
So here the deal guys , my mi 9t pro is about a 18 months old and recently started to have issues with battery life (long story and since I wasn't personally using it I can't explain the issues very clearly but it was all over the place doesn't charge at times verified the charger was indeed charging another phone , sometimes the phone turn off when the charger is connected so quite a lot of erratic faults and no consistent issue to point out )
I have been trying to look into it for a week now and this is my observations.
So first and foremost the phones does not turn on ,meaning that when just the power button is pressed it is stuck on the boot screen with just mi displayed on the screens and does not change at all even after hours.
I did find a way around it when I send the phone to recovery mode by pressing the volume+ and the power button and then selecting reboot and reboot to system. This way the phone always turns on . How long it remains on is a different matter some times it a few secs while at other times it could up to 10 mins and most of the time if its plugged to a charger and I disconnect the charger it immediately turns off.
Things that I have tried
Firstly, I had suspected the battery but on opening the rear cover realized that the previous battery looks in extremely good shape additionally I connected the new battery but connect the cable and realised that the fault persisted.
Thinking it was a software issue I also tried to flash the latest MIUI version from its official website with no help.
Now I am certain the issue is with the circuit or with the motherboard.
Any previous experiences and how it was fixed could be helpful .I don't mind doing some troubleshooting myself and can arrange for advance tools if required.
In short would appreciate advance level help as I enjoy fixing these things myself.
TL;Dr my phone is behaving quite erratically and having tried the battery and software need help repairing it.