Database Users

Totally Borked TF101

I think I have totally borked my ASUS TF101..
I get nothing on the screen and the only sign of life it shows is that it goes into APX mode..
I have tried to follow many different guides for recovery......
http://forum.xda-developers.com/showthread.php?t=1688012
..... but they all pretty much end with this:
http://sjfm.us/temp/tf101c.jpg
It just sits there like that. I left it for almost 10 hours... No change.
This is a really awesome tablet and I want to exhaust all possibilities before giving up..
Anyone have another procedure I can try???
Thanx
Michale

I'm assuming your unit is a b60 or greater since you're running wheelie? I'm bricked too but I have a b30 and Nvflash has always been confusing to me.

To be honest, I am not sure what TF101 I have.. I don't get ANYTHING on the display and the only sign of life is when I have it hooked to my PC via USB and can go into APX mode...
This is the label on my TF101:
http://sjfm.us/temp/tf101a.jpg
Here's a more detailed analysis of my issue..
http://www.transformerforums.com/forum/asus-transformer-help/25346-tf101-dead-doornail.html
Since the last post on that thread, I have tried the PERI package and the package here:
http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.24
It still freezes at 100% right after the bootloader load...
http://sjfm.us/temp/tf101e.jpg
I am pretty much at the point to where I either have a bad USB cable (waiting for a new one) or my TF101 is completely borked..

I have a friend here in Spain, in the same situation.
no way to restart pressing power button , the tablet seems to be always in apx.
I tried all possible methods, rootkit, easyflasher, reflash with wheelie.
and always the same result, stuck on the same spot as you.
I've run out of ideas already, and just hope that someone who has solved something like this , give us a hand.

partio said:
I have a friend here in Spain, in the same situation.
no way to restart pressing power button , the tablet seems to be always in apx.
I tried all possible methods, rootkit, easyflasher, reflash with wheelie.
and always the same result, stuck on the same spot as you.
I've run out of ideas already, and just hope that someone who has solved something like this , give us a hand.
Click to expand...
Click to collapse
That's interesting that you have the exact same problem.. Hopefully there is someone out there who also had, but fixed it. I PMed with a guy and he said to keep trying NVflash (wheelies) and see if it will "POP".. I did that for several hours with no luck..
I'll follow up on this when my new cable gets here. Frankly, I don't hold out much hope that it's going to fix things, but there is always that possibility.
If not, I'll just keep searching around for a TF101 that has a busted screen..

on the screen of my friend's tablet, when the process starts it appears:
Entering NvFlash recovery mode / Nv3p Server
Chip uid: 037c710942ffc217
check out : http://youtu.be/bwW0RiL35_o

partio said:
on the screen of my friend's tablet, when the process starts it appears:
Entering NvFlash recovery mode / Nv3p Server
Chip uid: 037c710942ffc217
check out : http://youtu.be/bwW0RiL35_o
Click to expand...
Click to collapse
Well, that's very interesting.. Mine did the same thing, except I didn't see any text on the TF101..
When I get home, I'll check it more closely..
Thanx

Well, apparently I have a bad LCD in addition to a borked unit.. I don't see ANY text on my screen, but the output from NVFlash is identical...
This just keeps getting better and better.. :crying:

I couldn't really find the serial number in your picture, IIRC it's just a sticker with a bunch of numbers and letters on it. Mine peeled off a while ago so I have nothing to compare it to :-/ It should start with a B
Sadly, the only way to make sure that the tablet is truly off is to rip the thing open and disconnect the battery (which is connected by an 8-pin connector). You need a T-5 torx screwdriver to take out the two screws around the charging port so you can pop the bezel off and a small Phillips screwdriver to remove the screws that hold down the screen/rear cover. I had to do this with mine because the only two things that I could get to were APX mode and the stock recovery, but my cable seemed to crap out the moment I needed it even though it had worked a few minutes earlier!

brando56894 said:
I couldn't really find the serial number in your picture, IIRC it's just a sticker with a bunch of numbers and letters on it. Mine peeled off a while ago so I have nothing to compare it to :-/ It should start with a B
Sadly, the only way to make sure that the tablet is truly off is to rip the thing open and disconnect the battery (which is connected by an 8-pin connector). You need a T-5 torx screwdriver to take out the two screws around the charging port so you can pop the bezel off and a small Phillips screwdriver to remove the screws that hold down the screen/rear cover. I had to do this with mine because the only two things that I could get to were APX mode and the stock recovery, but my cable seemed to crap out the moment I needed it even though it had worked a few minutes earlier!
Click to expand...
Click to collapse
Havn't tried it myself but there is this tool (http://forum.xda-developers.com/showthread.php?t=1290503) to check the SBK version

JoinTheRealms said:
Havn't tried it myself but there is this tool (http://forum.xda-developers.com/showthread.php?t=1290503) to check the SBK version
Click to expand...
Click to collapse
Thanx JTR.. I'll check that...
On another note, I got a new USB cable in. This one actually does worse than the first one. With the new USB cable, I can't even get the TF101 into APX mode..
Something else I noticed that may or may not be related...
When I have either cable plugged in, it seems to take over my USB ports. If I plug in a Thumb Drive while the TF101 cable is plugged in, the computer will not see the ThumbDrive..
Does that indicate that BOTH cables are bad???

Your TF may be done for :-/
Sent from my Transformer TF101 using Tapatalk 2

i am currently having the exact same issue as you do...can only go into apx mode and nothing ever shows up on the screen. Mine all started from trying to install an OTA firmware from asus...i feel like im about ready to give up

Same problem here.
In fact my tablet work very well but the display died. It works with an hdmi cable though.
In didn't try this but maybe it could fix some thing for you:
http://www.youtube.com/watch?v=yRLcxI2JddQ
I really am disgusted, my display dies two weeks after warranty without more obvious reasons than randomness.
If a lot of people have their display broken (and only the display, with hdmi working) I think we should think complaining to asus... It's not acceptable for this kind of devices.

have you tried flashing RougeXM recovery 1st? Then flash the asus recovery fw from easyflasher in apx mode.
Make sure its in /AsusUpdate dir. You won't see anything on the screen in apx.
I thought I killed mine but EF saved it. Was stuck hanging just like yours is doing so i reflashed & it worked.
Good luck,
Sent from my Transformer TF101 using xda app-developers app

Need Help with APX Mode Brick.

Running (was) a stock rooted N7 v1 on 4.3. Bought a data recovery tool off of the play store to try and recover some photos I had deleted. At some point it rebooted into safe mode, my battery was running low and I shut it off to let it charge. Now it's dead in the water. Stuck in APX mode. I am asking if there is anyway to breathe life back into this tablet.
The tablet does nothing on the screen, period, no matter what you do. When plugged in to a computer it sometimes registers as an unknown device, sometimes APX. None of these get you anywhere. Toolkits on these forums won't recognize the device, installing the android development kit and drivers does nothing, executing commands from the command line is worthless because the device won't register. I do not have any "blobs" and have no clue at this point even what they are or what they could have done for me had I made them.
I've searched this forum and found bits and pieces here and there and wanted to start a thread dealing solely with devices stuck like this and what has or hasn't worked and get others input if warranty service was done and the state your tablet was in when you sent it in (locked/unlocked, rooted etc).
Anyone stuck here will have probably tried the same things as I have but here is is a minor rundown...
1) Every button combo press known to man for short, medium, and extended periods of time.
2) Charging with the Original charger/cable for 1 hour, then button presses then charging for 12 hours.
3) Same as above but with different aftermarket chargers at different amperages.
4) Uninstalling and deleting drivers. Trying different drivers. Getting the Android drivers etc.
5) Trying every toolkit on the forums to no avail because the device won't register.
6) Checking to make sure the battery cables are seated correctly.
7) Screaming and yelling at your new paperweight.
My hope here is that I've missed some important thread about recovery and someone can point me in the right direction. Failing that, if I should get a new mobo or try and send it in for warranty service in the state it's in.
Any help would be much appreciated.
Sent from my Rooted Frameworked SCH-I545 using xda app-developers app

I don't know what you tried before to revive your tablet and what the tool did to get you into this state, but generally APX mode can be left by pushing the power button *only* for about 10-20 sec, as long as there us enough power within your battery and the hardware / software is working / consistent.
Sent from my Nexus 7 using xda app-developers app

I don't think I've ever seen anyone in here describe a situation where they observed the tablet in bootloader mode without seeing *something* on the screen.
And as you found out through your reading, using "nvflash" on the N7 is only useful at this time for folks that made prior disaster recovery preparations. So, APX mode is of no use to you (at this date 12/2013).
So, until you see something happen on that screen, drivers on a PC are of no value to you anyway.
It is really unfortunate that the N7 doesn't have a physical charging indicator - that makes it difficult to distinguish between a tablet which is truly borked vs. one that refuses to boot simply because the battery isn't charged.
Holding down a specific button combo (iirc Pwr+VolUp) during an attempt to get "something, anything" to happen will put the tab into APX mode, so it isn't particularly diagnostic that you have observed APX mode once or twice.
Really about the only way to know if the battery in a non-responsive N7 is charged or not is to put it in another tablet or measure the open-circuit voltage. (About 4.15v fully charged & about 3.5v discharged)
The reason that I mention this is that there have been a few reports from users in similar straits as you that report something like "I don't know what happened, but I tried it a few days later and all of a sudden the tablet booted up". Almost every one of those reports involved mentions of low battery conditions, just as your narrative does.
I don't know what file recovery program you used, but I suspect that is a red herring . It might have to have root privileges in order to read raw partitions, and might even want the tablet in safe mode to minimize write activity by *other apps* while it does it's forensics, but it certainly isn't going to recover files by writing in raw mode on a mounted, live filesystem - it would do all it's writing through normal kernel syscalls. That's the long way of saying that a low battery is more likely to be the original source of your troubles.
So what to do now? I think the first order of business is to figure out if your battery is charged or failing to take a charge. If it really is well charged, then a warranty return is probably in your future.
If you can't find a second N7 or a voltmeter, then you could try just leaving it on the charger for a couple of days... but that really is just a "grope about in the dark, wing & prayer" kind of strategy.
good luck
Button sequences & USB Identifiers (VID/PID pairs):
http://forum.xda-developers.com/showthread.php?t=2133986

You are in the same situation I was in - nothing shows up on screen. I got APX drivers to finally install (had to search all over the internet to find them) and that STILL didn't help. I was never able to get it to come back. Nothing ever showed up on the screen.
No combination of button presses helped. I finally gave up and, since my N7 was still under warranty, I RMA'd it back to ASUS. It took about 3 weeks, but I got it back with a new motherboard installed on it.
It was borked and your's sounds the same way as mine. Just either register your N7 on the ASUS website and RMA it that way, or call it in over the phone and RMA it that way. Hopefully, you still have the box your N7 came in because you'll need the serial number.
Others have stated you can get it by opening the back, but that will void your warranty. I do believe you MUST have the serial number, so find the box and get it from there.
Also, you'll definitely lose everything that was there, especially if they replace the motherboard. So hopefully, you backed it up. I backed mine up just before it got borked, so I was lucky.
Good luck!

I am wary of trying to do the battery swap. I went and bought a new version after it crashed but I would be voiding both warranties to try the battery swap.
I do have the serial number if I want to try and get service.
I have done some reading about "deep discharge" battery issues and I suspect this may be a part if it but I have tried leaving it plugged in for days and nada.
I don't know if there is a way to "shock" or jump start the charging process and I am going to put the multimeter on it tomorrow and see what I get.
Thanks for everyone's input. I will keep you up to date.
Sent from my Rooted Frameworked Verizon Galaxy S4 on MJ7 using the XDA App.

Ideos x5 totally bricked

Hi there,
My phone not turning on not without battery and SD not with home and volume+ and power button not with both volumes and power nothing at all not even vibrating when charging I am not sure if it's the battery but it was charged before I rebooted once rebooted it didn't turn back on I am on aurora ics and cwm.
I didn't have any problems with it partitions might of been wiped but I guess this would leave me with access to bootloader or anything or a vibrate on charge at least it happened as I was formatting another device but put the wrong sd on ubuntu so I started to think it might be the battery except it was charged unless it decided to leak all the charge in no time.
Also it doesn't do anything on usb or charge connection no vibrate no led no light buttons no nothing just nothing.

Sounds like my issue...
If in fact you did format the whole 3.69gb partition, then you wiped the phone.
So far, my only recourse has been to attempt a JTAG and install a bootloader.
I'm thinking that maybe I can try some form of "wire trick", like the ones used on the HTC Sensation, but I don't want to blow it up by shorting something unrepairable.
If you find another solution, please reply as it would be helpful to others.

PoXFreak said:
Sounds like my issue...
If in fact you did format the whole 3.69gb partition, then you wiped the phone.
So far, my only recourse has been to attempt a JTAG and install a bootloader.
I'm thinking that maybe I can try some form of "wire trick", like the ones used on the HTC Sensation, but I don't want to blow it up by shorting something unrepairable.
If you find another solution, please reply as it would be helpful to others.
Click to expand...
Click to collapse
nope i didnt format 3.96 gb it was 3 mb and it was shown as linux cd gadget also it worked afterwards until i rebooted next day then blackness the thing is i cant seem to find a battery to try with so i need to try everything first

The one I have here wouldn't start charging the battery until I force-fed the battery directly. (use a 4-5v charger and directly charge the battery for a couple of minutes).
Mine worked, but I made the mistake of formatting the entire partition (3.69gb), so now the phone does absolutely nothing.

PoXFreak said:
The one I have here wouldn't start charging the battery until I force-fed the battery directly. (use a 4-5v charger and directly charge the battery for a couple of minutes).
Mine worked, but I made the mistake of formatting the entire partition (3.69gb), so now the phone does absolutely nothing.
Click to expand...
Click to collapse
I am a bit confused here so now when you plug it you can do something to it since it's charging? I guess I never did the 3.69 thingy if I am not mistaken..So lemme ask you if I tried the wall outlet for example instead of the USB to tv or laptop would that help to start it? I am thinking of replacing the battery and see what happens that's if I can find it here in Turkey the Turks always into the newest phones so this one is ancient to them to find a battery for...

Mine is in the same state. But I know that in my efforts to get it to start again I accidently wiped the the entire partition. Can't turn it on, can't get a pink screen, not a thing and haven't beenable to find any solution. So I guess all I can do is sit back and check the postings to see if anyone else has the same issue and knows of a way to restore the boot partition.

Burtrum57 said:
Mine is in the same state. But I know that in my efforts to get it to start again I accidently wiped the the entire partition. Can't turn it on, can't get a pink screen, not a thing and haven't beenable to find any solution. So I guess all I can do is sit back and check the postings to see if anyone else has the same issue and knows of a way to restore the boot partition.
Click to expand...
Click to collapse
I'm thinking of trying to run MTTY 1.42 and talk directly with the qualcomm chip to send the boot files myself, but I need to know what I need and where it goes first.
I did this with the HTC Kaiser (AT&T Tilt) with some success.
That was on Windows XP though...not sure if it will run correctly on Win 7.

PoXFreak said:
I'm thinking of trying to run MTTY 1.42 and talk directly with the qualcomm chip to send the boot files myself, but I need to know what I need and where it goes first.
I did this with the HTC Kaiser (AT&T Tilt) with some success.
That was on Windows XP though...not sure if it will run correctly on Win 7.
Click to expand...
Click to collapse
help me i have the same issue....

service
May be best option is to take it to service center.

N910F - strange issues with charging

Hello everybody,
- On monday i ran into a strange problem with my N910F. At first it was just not charging whatsoever.
- after the phone ran out of power, i attempted to charge it which gave me a brick with a black screen, vibrating short every two seconds
- Fine by me i thought, went and got a replacement battery (after checking simple stuff like the physical state of the battery (normal) and killing the batterystats (which i heard both yay and nay about so i decided to give it a try).
- Replacement battery charged overnight on the USB Port of my computer (2.0, for the completionists) went smooth (didn't turn it on, just had this bubble animation of charging).
- Turned it on this morning (booting apparently took 3% off my battery) and all well so far.
- finally in my chair at work i plugged it into my power cable (genuine Samsung FastCharging adapter that came with the phone itself) and nothing happened
- tried another adapter (some cheapo 1A adapter) which started charging around 10secs after connecting but decided to stop charging after a couple of minutes
- some shaking and gentle knocking brought back the charging symbol for some seconds, seemed like some loose contact or a broken cable so i felt fancy and plugged the very same cable (the one originally shipped with the phone) to my laptop. started charging instantly and no shaking or knocking stopped this (so no loose contact or broken cable at all)
This is the story until now, put together as complete and organized as possible. For now i'm stuck to charge my phone on the laptop or computer which seems to work. In this progress above i tested around 7 chargers, 3 laptops, 2 computers, 10 cables and 3 screens with both batteries, although the workaround i have now is only tested with the genuine cable as i was just done with testing for the night.
Now for my questions (apart from a touch with the magical fix-everything tool):
- What i see as possible causes based on my very shallow knowledge are either the microUSB port on the phone or the power distribution unit. Anyone has an idea what to check?
- As i have no idea how deep the OS goes, could it be a software issue by any chance?
Even though the device is only ~9 months old, I don't like the idea of going through Samsung for this one as i tripped KNOX already.
Hope there's still hope for me
Cheers,
Fachtal

sooooooo, does nobody have an idea lying around somewhere?

Fachtal said:
Hello everybody,
- On monday i ran into a strange problem with my N910F. At first it was just not charging whatsoever.
- after the phone ran out of power, i attempted to charge it which gave me a brick with a black screen, vibrating short every two seconds
- Fine by me i thought, went and got a replacement battery (after checking simple stuff like the physical state of the battery (normal) and killing the batterystats (which i heard both yay and nay about so i decided to give it a try).
- Replacement battery charged overnight on the USB Port of my computer (2.0, for the completionists) went smooth (didn't turn it on, just had this bubble animation of charging).
- Turned it on this morning (booting apparently took 3% off my battery) and all well so far.
- finally in my chair at work i plugged it into my power cable (genuine Samsung FastCharging adapter that came with the phone itself) and nothing happened
- tried another adapter (some cheapo 1A adapter) which started charging around 10secs after connecting but decided to stop charging after a couple of minutes
- some shaking and gentle knocking brought back the charging symbol for some seconds, seemed like some loose contact or a broken cable so i felt fancy and plugged the very same cable (the one originally shipped with the phone) to my laptop. started charging instantly and no shaking or knocking stopped this (so no loose contact or broken cable at all)
This is the story until now, put together as complete and organized as possible. For now i'm stuck to charge my phone on the laptop or computer which seems to work. In this progress above i tested around 7 chargers, 3 laptops, 2 computers, 10 cables and 3 screens with both batteries, although the workaround i have now is only tested with the genuine cable as i was just done with testing for the night.
Now for my questions (apart from a touch with the magical fix-everything tool):
- What i see as possible causes based on my very shallow knowledge are either the microUSB port on the phone or the power distribution unit. Anyone has an idea what to check?
- As i have no idea how deep the OS goes, could it be a software issue by any chance?
Even though the device is only ~9 months old, I don't like the idea of going through Samsung for this one as i tripped KNOX already.
Hope there's still hope for me
Cheers,
Fachtal
Click to expand...
Click to collapse
You seemed to have tried using the cheap charger which allowed you to charge after shaking it a bit, have you tried purchasing a new genuine charger?
Sent from my trltexx using XDA Premium 4 mobile app

Tripping Knox does not necessarily mean that you've lost warranty.

Battlehero said:
You seemed to have tried using the cheap charger which allowed you to charge after shaking it a bit, have you tried purchasing a new genuine charger?
Sent from my trltexx using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried around 7 adapters (from cheap ones to genuine galaxy S3, Note2, and Note4), around 10 different cables (again, from cheap ones to genuine samsung cables), 3 Laptops (again with all cables), 2 computers (all cables) abd one of those mobile charging battery things.
The only thing that works is either the genuine cable on my computer or the same cables on my screen at work.
@geevh that's news to me. As far as i heard is tripping know equal to losing warranty.

Fachtal said:
I tried around 7 adapters (from cheap ones to genuine galaxy S3, Note2, and Note4), around 10 different cables (again, from cheap ones to genuine samsung cables), 3 Laptops (again with all cables), 2 computers (all cables) abd one of those mobile charging battery things.
The only thing that works is either the genuine cable on my computer or the same cables on my screen at work.
@geevh that's news to me. As far as i heard is tripping know equal to losing warranty.
Click to expand...
Click to collapse
Have you tried to flash stock firmware, in case it's the kernel?
KNOX warranty shouldn't void your warrant in the EU as I have gotten two knox tripped devices repaired from Samsung before.
Sent from my SM-N910F using XDA Premium 4 mobile app

Battlehero said:
Have you tried to flash stock firmware, in case it's the kernel?
KNOX warranty shouldn't void your warrant in the EU as I have gotten two knox tripped devices repaired from Samsung before.
Sent from my SM-N910F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just flashed the official ROM using Odin. Had some problems getting the phone connected while in DL mode (didn't work at all while in normal android mode).
This seemed to be a dirty flash (already was on stock Rom, just put CWM on, rooted the phone and replaced the kernel to have SELinux permissive for Viper4Droid) as it didn't go through the setup process and was like before.
Anyway, charging still doesn't work. Is there anything else I can test? I'm nearly at the point where I migrate back to my old SGS3 and have the N910F sent to the carrier (well, in the end it will go to Samsung) to get it fixed.
Thanks about the whole Knox false knowledge.
Cheers, Fachtal

Fachtal said:
I just flashed the official ROM using Odin. Had some problems getting the phone connected while in DL mode (didn't work at all while in normal android mode).
This seemed to be a dirty flash (already was on stock Rom, just put CWM on, rooted the phone and replaced the kernel to have SELinux permissive for Viper4Droid) as it didn't go through the setup process and was like before.
Anyway, charging still doesn't work. Is there anything else I can test? I'm nearly at the point where I migrate back to my old SGS3 and have the N910F sent to the carrier (well, in the end it will go to Samsung) to get it fixed.
Thanks about the whole Knox false knowledge.
Cheers, Fachtal
Click to expand...
Click to collapse
I would just give the device in for repairs but make sure to flash a full stock rom and factory reset before giving the phone, since you have already tried everything else.
Good luck

Battlehero said:
I would just give the device in for repairs but make sure to flash a full stock rom and factory reset before giving the phone, since you have already tried everything else.
Good luck
Click to expand...
Click to collapse
Well, flashing stock ROM seems to be slightly less relaxing than I thought. It feels like I have to connect the phone to the pc, put it on the table in a very specific position/way and then hope that it doesn't disconnect halfway through flashing...
This has become quite an adventure so far and I hope I'll get this done so i can get rid of this very expensive paperweight
Thanks for all the help so far, I guess I'll add the explanation from my carrier/Samsung as soon as I (hopefully) get my device back.
Fachtal

PMIC or Charging IC is probably broken on the mainboard, i hear more N4's have this problem.
Best is to send it for warranty or let the components be replaced by a "good" repair shop.
Most service centers don't check knox status so i would go for that, if all fails take it for repairs if the costs are not too high.

Hi guys, back for a rather unexpected "solution"
When i finally freed up some time to actually get to the carrier shop to get my phone fixed, I was in for a rather embarrasing experience.
The lady in the shop pulled a charging cable and an adapter out of a box, plugged my phone in and it suddenly charged as if nothing ever happened. Now, some time later, it still works perfectly fine, as if there never were problems...
I have absolutely no idea on what happened. Before going to the shop i obviously flashed the stock rom yet again (with the usual wipe user data/cache/dalvik procedure).
Now, on what i had when the problems started: stock BOC5 ROM, touch CWM, rooted and with a custom kernel for SEAndroid permissive (emotion something i believe the kernel was called). Now during my rather extensive troubleshooting I actually flashed the stock ROM at least once and the issue persisted, which is why i just stood there, staring on my charging phone, my jaw somewhere on its way to the ground, unable to form any proper words :silly:
So basically, does someone have a possible explanation to clear this up? If not, I'll consider this thread solved i guess^^
In the meantime, I downgraded to Stock 4.4.4 with CWM, root and xposed (which i really missed on Lolli) and I'd say I'm happy with this :victory:
Fachtal

Fachtal said:
Hi guys, back for a rather unexpected "solution"
When i finally freed up some time to actually get to the carrier shop to get my phone fixed, I was in for a rather embarrasing experience.
The lady in the shop pulled a charging cable and an adapter out of a box, plugged my phone in and it suddenly charged as if nothing ever happened. Now, some time later, it still works perfectly fine, as if there never were problems...
I have absolutely no idea on what happened. Before going to the shop i obviously flashed the stock rom yet again (with the usual wipe user data/cache/dalvik procedure).
Now, on what i had when the problems started: stock BOC5 ROM, touch CWM, rooted and with a custom kernel for SEAndroid permissive (emotion something i believe the kernel was called). Now during my rather extensive troubleshooting I actually flashed the stock ROM at least once and the issue persisted, which is why i just stood there, staring on my charging phone, my jaw somewhere on its way to the ground, unable to form any proper words :silly:
So basically, does someone have a possible explanation to clear this up? If not, I'll consider this thread solved i guess^^
In the meantime, I downgraded to Stock 4.4.4 with CWM, root and xposed (which i really missed on Lolli) and I'd say I'm happy with this :victory:
Fachtal
Click to expand...
Click to collapse
It's sound strange but a couple of years ago i read somewhere,forgotten where and about the specific device. The thing was that phone wasn't charging eather ,and now it comes.....the solution was turnig around the charger in te power socket.

ludoke said:
It's sound strange but a couple of years ago i read somewhere,forgotten where and about the specific device. The thing was that phone wasn't charging eather ,and now it comes.....the solution was turnig around the charger in te power socket.
Click to expand...
Click to collapse
this indeed sounds strange. And honestly, i didn't pay attention on the orientation of the power adapter (although my stock samsung one is always in the same orientation because the cable goes out on the side (which means it worked in the same direction as it didn't before).
The only even remotely considerable approach would be that the custom kernel along with this synapse app somehow screwed with the power intake and i forgot to wipe everything when i first flashed stock over it, meaning that synapse still had its fingers in the system screwing around with that.
But then again, as I seem to be the only one with this problem and this custom kernel had more than just a few users I don't think this is the way it went (I don't even use an unusual collection of root Apps which could cause some sort of malfunctioning combination of effects).
I had a few evenings just thinking about this and draw some simple mindmaps/schematics to make some sort of a sense...

Nexus 6p Won't Start (Suspected Hardware Failure)

My nexus 6p suddenly won't start, I've had my phone since May 2016 so more than a year now.
I've flashed a custom ROM onto it, I'm sure this isn't a software issue because it's been running fine since I bought it (and flashed it) and I followed all the instructions correctly.
I've read through this thread and tried the solutions there, hold the power button for longer than usual (a few minutes), hold the volume down button and power together, hold the volume down button then charge it, now hold the power button. I tried all 3 solutions which worked for many in that thread, but not me.
This all started 2 days ago, with no changes software-wise and using the same configuration as when I first flashed it, I opened the app HERE Maps and then my phone froze, totally stuck and unresponsive, restarting was no good, I had to go into TWRP and wipe the cache and dalvik cache, and it booted fine.
Today, same thing, I opened up HERE Maps and it got stuck again, I now notice that it takes longer than usual to start up via the power button, and wiping the cache and dalvik cache does not work anymore, it stucks on boot.
Now, my phone is not able to start at all. I think this is a hardware-related issue.
So quick recap:
1. Opened HERE Maps and gets frozen
2. Wiping cache and dalvik cache no longer works, stuck on boot.
3. Phone not able to start at all.
I am out of warranty period-wise, but I also custom it, so obviously my warranty is out the window. I need some insight from you guys here at XDA before I buy another costly phone.

someRandomSamaritan said:
...Now, my phone is not able to start at all. I think this is a hardware-related issue...
Click to expand...
Click to collapse
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?

v12xke said:
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?
Click to expand...
Click to collapse
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken

someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Can you access recovery or bootloader mode?
If within warranty, contact google/Huawei depending on where you purchased the phone from.
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.

someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Is it recognized at all when you plug a data cable to your PC? Your phone may be stuck in Qualcomm's EDL mode. Search.

No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.
Click to expand...
Click to collapse
This is a possible option..I'll try that tomorrow when it's morning
Anything else I could try? I think the most obvious methods are not available for me with this kinda situation

someRandomSamaritan said:
No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
Click to expand...
Click to collapse
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.

v12xke said:
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.
Click to expand...
Click to collapse
Okay, this is helpful, you guys seems to think it is in EDL mode (which I haven't heard of until now), I'll try this and hopefully a driver loads or something
EDIT: nope, no drivers are loading, doesn't seem to be anything new in device manager, no device plug in sound, how sure are you that I'm in EDL mode?
It did work a few times yesterday (being able to boot into TWRP and wiping cache and dalvik cache), but now I'm not so lucky, it doesn't work anymore. I don't believe my phone is completely dead for some reason, I still do believe it can be saved. Hopefully I'm right :|

If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?

someRandomSamaritan said:
If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?
Click to expand...
Click to collapse
I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2. They have project treble.
Your issue is different than most others. Most n6p with issues are bootlooping devices.

I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...

BadBoy2K7 said:
I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...
Click to expand...
Click to collapse
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?

I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2.
Click to expand...
Click to collapse
Pixel 2 is some expensive thing, out of my budget

someRandomSamaritan said:
Pixel 2 is some expensive thing, out of my budget
Click to expand...
Click to collapse
Then you should look for alternatives. Perhaps OnePlus 5T, etc.

I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?

someRandomSamaritan said:
I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?
Click to expand...
Click to collapse
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.

I was facing bootlooping problem with my Nexus 6P and bootloader was locked so was unable to flash ROM by any mean.
So I tried following few threads and did "fastboot continue" and my device is not showing any sign of power since then. When connected to PC then no USB connection is there.
Is there any suggestions that can solve issue?

someRandomSamaritan said:
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?
Click to expand...
Click to collapse
No. Unfortunately this happened to me last month and ive had the phone for almost 2 years now. Its sad because others are having the same issue and I think the hardware is faulty

I just called up a local phone repair and they said from their experience of repairing nexus 6p phones, most (if not all) of them had dead motherboards. The technician told me to get a new model of a phone and skip the 6p as it is a poorly built phone.
I consider saving up for a pixel..

NoobInToto said:
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.
Click to expand...
Click to collapse
Ive heard of people baking motherboard on Nexus 5x and many other phones to reflow the solder.