Develop Bugs

Possibly bricked A100

This morning I woke up and went to switch on my Acer A100 to no avail. The power button will light up blue and the home button will light up, but the screen is black.
I first tried the paperclip reset, and worked all the way up to a hard reset, but the problem persists.
Thinking I could possibly just reflash the ROM (I'm running the ICS Gen1 ROM I downloaded from XDA (which worked for the last several months)), I went to plug my Acer into my computer running Windows 7, and heard a strange noise. My tablet is showing up in APX mode, which from what I have read may be helpful for me to start fixing this thing.
However, I'm having trouble finding the drivers I'd need to start doing further troubleshooting.
Any help that could be provided would be greatly appreciated.
Hopefully this isn't a lost cause, because I've certainly voided my warranty by flashing ROMS in the past, correct? I've had the tablet for less than a year, and have been generally dissatisfied with it (it gets sluggish, doesn't always charge correctly, and generally acts strange).

The same thing recently happened to me, no screen but the blue light was on. I had to send it in to Acer. I also had a custom ROM on my tablet but they fixed it for free ad sent it back, so its worth a try. If it doesn't show the boot screen I don't think they can tell.

nsmith4 said:
The same thing recently happened to me, no screen but the blue light was on. I had to send it in to Acer. I also had a custom ROM on my tablet but they fixed it for free ad sent it back, so its worth a try. If it doesn't show the boot screen I don't think they can tell.
Click to expand...
Click to collapse
Good to know. Thanks.

MarkBell said:
Good to know. Thanks.
Click to expand...
Click to collapse
Exact thing happened to me. Sent it to acer. Fixed under warrenty. Still had to pay shipping one way though.

MarkBell said:
This morning I woke up and went to switch on my Acer A100 to no avail. The power button will light up blue and the home button will light up, but the screen is black.
I first tried the paperclip reset, and worked all the way up to a hard reset, but the problem persists.
Thinking I could possibly just reflash the ROM (I'm running the ICS Gen1 ROM I downloaded from XDA (which worked for the last several months)), I went to plug my Acer into my computer running Windows 7, and heard a strange noise. My tablet is showing up in APX mode, which from what I have read may be helpful for me to start fixing this thing.
However, I'm having trouble finding the drivers I'd need to start doing further troubleshooting.
Any help that could be provided would be greatly appreciated.
Hopefully this isn't a lost cause, because I've certainly voided my warranty by flashing ROMS in the past, correct? I've had the tablet for less than a year, and have been generally dissatisfied with it (it gets sluggish, doesn't always charge correctly, and generally acts strange).
Click to expand...
Click to collapse
Sounds like a dead emmc. Since it is not bootable, acer will not know if you were flashing roms, send it back... :good:
They have to be getting a ton of these dead tabs back, so I doubt they even waste time looking anymore.

Same thing happened to me. Just sent it into Acer Repair yesterday.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

Romman0 said:
Sounds like a dead emmc. Since it is not bootable, acer will not know if you were flashing roms, send it back... :good:
They have to be getting a ton of these dead tabs back, so I doubt they even waste time looking anymore.
Click to expand...
Click to collapse
Wow this really seems to be happening often with the Acer A100. Happened to me just yesterday, Tab was working great there were no signs of problems or at least none that I could tell then out of the blue the Tab just froze up forcing me to Power down by holding the power button for xx number of seconds and never booted up again. Only thing that comes on the screen the the Acer logo screen.So what does dead emmc mean, does it just mean the system died or is there any detailed info on what it really is?

BlueIce said:
Wow this really seems to be happening often with the Acer A100. Happened to me just yesterday, Tab was working great there were no signs of problems or at least none that I could tell then out of the blue the Tab just froze up forcing me to Power down by holding the power button for xx number of seconds and never booted up again. Only thing that comes on the screen the the Acer logo screen.So what does dead emmc mean, does it just mean the system died or is there any detailed info on what it really is?
Click to expand...
Click to collapse
Its been explained a few times, notably in the bricked thread. Its partial erasing of the emmc which corrupts the gpt. What causes it is unknown, and Acer won't admit to it or help us with it or even talk about it.
Sent from my Galaxy Nexus using Tapatalk 2

Potential Brick, Unsure How To Proceed

Hello all.
I am an HTC guy through and through and have never owned a Samsung device. I'm familiar with HTC's S-OFF/HBOOT/bootloader stuff, but I'm not really all that clear on how it works for Samsung devices. I promise I've tried to do some reading before hand before coming to you, including looking at other threads, but they don't seem to be the issue I'm having.
I'm trying to help a friend out who has an AT&T GS3 that I unlocked for him and put an AOSP ROM on it a few months ago (don't worry, I made damn sure it was the AT&T version and no other carrier/international ROM).
He came to me today telling me that his phone suddenly turned off, and was not turning on again. I figure it's probably just a corrupted partition, something that I could fix with a reflash or something like that.
However, when I look at it, it seems to be something potentially worse. The phone did nothing with the battery in, so I took it out and put it back in. The phone very briefly vibrates, the Samsung logo shows for about 1.5 - 2 seconds at most, and then the screen goes dark.
When I try to enter Download Mode, I'm able to get to the custom software "warning" page, where I press Volume Up, and it shows me Download Mode and "Waiting" (as I expect it to) but then the screen just goes black again after about a second or two.
It's roughly the same with Recovery Mode, I can catch a glimpse of what looks like CWM (but I'm not entirely sure) and then the screen goes black.
If I choose to forgo the battery altogether, and I plug it in straight to the wall, the red LED on the top right lights up for again maybe 3 - 4 seconds at most, the light goes away, and the phone briefly vibrates, shows me the Samsung logo, and then goes dark.
I'm confused. I don't know if it's a brick, but then again, to me as an HTC user, "brick" means Qualcomm USB Download mode. I've also read about this infamous Samsung Sudden Death Syndrome that struck some of the 16 GB models that Samsung sold (and yes, you guessed it, this is the white 16GB model).
I don't really know what other troubleshooting options there are (but as I said before, I'm an HTC guy). If any of you have any sort of advice I would love to hear it.
Thank you for your time.

I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.

xBeerdroiDx said:
I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.
Click to expand...
Click to collapse
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.

Yeah, the biggest problem is that once you get into recovery or download mode, the device reboots/loops. This eliminates the possibility of any kind of flashing or wiping.

You might have a bad motherboard. If I was you I'd take it to att for a replacement. BTW if he doesn't have insurance for the phone they do have open enrollment , I'd wait a day or two after enrolling to submit a claim.
Wish you the best.
Sent from my SGH-I747 using xda app-developers app

LiquidSolstice said:
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.
Click to expand...
Click to collapse
It's a realllly long shot but he could contact mobile tech videos and tell them his issue and see if a jtag repair would help. If it's hardware of course he is out of luck but it's worth a shot and a lot cheaper.

Really...really bricked OnePlus 3

Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.

dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Damn that sucks. He probably flashed the wrong rom or something else. You should contact oneplus and see if they can do something about it cuz i reckon your brother's phone still has warranty.

dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Really sorry To hear it?? BUT CM12 rom??? ? where he find it....?? if you hard bricked phone.. go to a expart devs shop.. he may be solved your problem

If your phone will not power on oneplus service center person are also not able to check how your phone will dead i think so you can claim the warranty.

CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.

dannytgt said:
CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.
Click to expand...
Click to collapse
No wonder why it got bricked xD. You should see if you still have the warranty for your brothers phone. Contact oneplus and see if they can replace the phone.

I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.

dannytgt said:
I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.
Click to expand...
Click to collapse
Well ****. Can't you contact the seller that you bought it from? Also your brother should be careful next time he flashes a rom. We all make mistakes, sometimes ppl have to learn it the hard way.

Yes this will be the first phone since 2005 year when I started to flash custom roms on samsung omnia i900, thats really dead, I bring from the death a lot of bricked phones. But this phone is really dead so I think I will start sparing parts, maybe we can recover some of the money invested on the device.

Nexus 5x shut off and won't turn on

If I posted this in the incorrect place or there is something related to my issue, I apologize in advance.
I've been searching here and all over the internet and no progress yet so I decided to make a new account here just to see if anyone can help me because I'm out of ideas right now.
This morning my Nexus 5x (Non-rooted Nougat) woke me up like every morning, after dismissing the alarm I left it on my bed and when I came back to grab it later I noticed it shut off.
Here are the facts and what I have tried so far:
- Battery level was almost full
- I tried to turn it on but nothing happened, not even the Google logo
- Connected it to power and no icons or any response at all
- Left it connected for like an hour and tried to get it into recovery mode
- I was able to get into fastboot mode a few times but after electing "start" or "recovery mode" the Google logo comes up and then shuts off again right after.
- Tried getting into recovery mode after leaving it charging for a while again but I couldn't even get into fastboot this time, no signs of life at all.
- Disconnected the battery for a few minutes and tried to get into fastboot mode again, this time it worked but same thing happened. (Google logo then shuts off)
- Tried connecting it to my PC but doesn't show up on Linux nor Windows, on Windows it makes the sound like I connected a peripheral but that's pretty much it.
- I have USB debugging enable but never accessed my stuff through usb connection because I have had this issue before where it is connected but it won't show up or it shows up but won't let me access the files even though the phone is unlocked.
At this point it just won't do anything and I ran out of ideas. I just want to at least recover some pictures and information I have in it that isn't backed up, if anyone can help me I would greatly appreciate it.
Thanks in advance

It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.

Just boot to bootloader (fastboot) then unlock it and flash a factory image... u can find many guides to this operation on the XDA

sfhub said:
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Click to expand...
Click to collapse
At this point, I'm willing to try anything. Thanks

driss.sadok said:
Just boot to bootloader (fastboot) then unlock it and flash a factory image... u can find many guides to this operation on the XDA
Click to expand...
Click to collapse
If it's a hardware issue like sfhub suggested, I don't think this will fix it.

PennyScissors said:
If it's a hardware issue like sfhub suggested, I don't think this will fix it.
Click to expand...
Click to collapse
Same here... cannot enter recovery mode, so flashed new rom stock rom.
The flashing was fine but it didn't help.

guys if u can get to the bootloader, sure it can be fixed.. everything is possible with the fastboot, u can fix any issue. if it's a hardware issue the bootloader wouldn't work as well.

Re Nexus 5X won't turn on - I've had same issue
PennyScissors said:
This morning my Nexus 5x (Non-rooted Nougat) woke me up like every morning, after dismissing the alarm I left it on my bed and when I came back to grab it later I noticed it shut off.
Here are the facts and what I have tried so far:
- Battery level was almost full
- I tried to turn it on but nothing happened, not even the Google logo
- Connected it to power and no icons or any response at all
- Left it connected for like an hour and tried to get it into recovery mode
- I was able to get into fastboot mode a few times but after electing "start" or "recovery mode" the Google logo comes up and then shuts off again right after.
- Tried getting into recovery mode after leaving it charging for a while again but I couldn't even get into fastboot this time, no signs of life at all.
- Disconnected the battery for a few minutes and tried to get into fastboot mode again, this time it worked but same thing happened. (Google logo then shuts off)
- Tried connecting it to my PC but doesn't show up on Linux nor Windows, on Windows it makes the sound like I connected a peripheral but that's pretty much it.
- I have USB debugging enable but never accessed my stuff through usb connection because I have had this issue before where it is connected but it won't show up or it shows up but won't let me access the files even though the phone is unlocked.
At this point it just won't do anything and I ran out of ideas...
Click to expand...
Click to collapse
I've had the same problem with my 5X, except my alarm didn't even go off! I woke up 15 minutes late to see the boot screen "enter your pattern to start Android". I entered my pattern and it looked like it was going to boot up but when I went back to it it was blank. Tried again, got to the Google loading dots and it switched off again and I haven't been able to power it up since. No bootloader, nothing. Tried all the troubleshooting steps on the Nexus Google Support pages (I did post a link but because I'm new it won't show, so just Google "Nexus Support") and nothing worked. I also knew the battery was fully charged because it had been on charge overnight and when I did get to the 'enter your pattern' screen, the battery icon in the notification bar was full.
I requested a call back from Google and nothing happened so I tried the chat and they said it sounded like a hardware issue and are sending me a replacement device within the next 3-5 working days. Good that they're replacing it. Bad that it happened on a device less than a year old and they only offered £10 Play Store credit by way of compensation, when I've had to spend £15+ on a PAYG sim card to use in my old phone in the meantime because the nano sim in my 5X was too small and I've spent over an hour and half this afternoon wasting my time with troubleshooting and waiting for a call back... Not really the customer service I expected from Google for what appears to be a hardware issue. If you bought the phone from Google, my advice would be to get in touch with Google Support and they should replace it under warranty.

danielledowns01 said:
I've had the same problem with my 5X, except my alarm didn't even go off! I woke up 15 minutes late to see the boot screen "enter your pattern to start Android". I entered my pattern and it looked like it was going to boot up but when I went back to it it was blank. Tried again, got to the Google loading dots and it switched off again and I haven't been able to power it up since. No bootloader, nothing. Tried all the troubleshooting steps on the Nexus Google Support pages (I did post a link but because I'm new it won't show, so just Google "Nexus Support") and nothing worked. I also knew the battery was fully charged because it had been on charge overnight and when I did get to the 'enter your pattern' screen, the battery icon in the notification bar was full.
I requested a call back from Google and nothing happened so I tried the chat and they said it sounded like a hardware issue and are sending me a replacement device within the next 3-5 working days. Good that they're replacing it. Bad that it happened on a device less than a year old and they only offered £10 Play Store credit by way of compensation, when I've had to spend £15+ on a PAYG sim card to use in my old phone in the meantime because the nano sim in my 5X was too small and I've spent over an hour and half this afternoon wasting my time with troubleshooting and waiting for a call back... Not really the customer service I expected from Google for what appears to be a hardware issue. If you bought the phone from Google, my advice would be to get in touch with Google Support and they should replace it under warranty.
Click to expand...
Click to collapse
I contacted Google and they didn't help me at all because my warranty expired last month, they literally just told me to put in a repair request at the LG repair webpage....this sucks

My experience exactly...
My wife's Nexus 5 exhibited the exact same symptoms this morning. It's been running perfectly for 20 months and today it died, and we're unable to even get into the bootloader screen or power on the phone.
Taking your advice, we put it in the freezer for 15 minutes and were able to perform a factory reset wiping all data from the phone. We are going to take advantage of Google's Christmas 2017 promotion and return the Nexus 5X and buy a Moto 4X. They require you perform a factory reset before returning the phone in order to receive a credit for the returned Nexus 5. Thank you so much for the help!
Dennis
sfhub said:
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Click to expand...
Click to collapse

https://forum.xda-developers.com/nexus-5x/help/help-nexus-5x-lg-off-to-t3729739
I've just posted this thread overlooking yours. I think this is becoming another common issue. Has the freezer trick worked with anybody else?

I am having the same issue described here. My Nexus 5x went into a Bootloop about one month ago, but I was able to get it working again by going into Recovery Mode. About 4 days ago it went into a constant Bootloop, just showing the Google screen, and I couldnt get back in to recovery mode. I ordered a new phone on Tuesday (Pixel 2) and as long as I am able to do a factory reset I should get a $150 credit when I send this phone back. So, in desperation, I took a chance on the 15 minute freezer trick, and it worked! I was able to get into recovery mode (power + volume down, select Recovery Mode, little dude on his back came up, pushed power + volume up once) and cleared the cache and applied the factory reset. Ridiculous that this phone only lasted 18 months, but if I get the $150 credit I will be happy.

Same problem here -- just froze for a few seconds, powered off, and won't turn back on. Not a boot loop issue as there is no response at all from any buttons. Swapping the mainboard from a working phone powered up without a problem, but obviously that's the other phone's emmc.
I tried the freezer thing and it sort of worked- LCD powered on for a couple seconds, but then shut back off again and even that only happened once. That's progress over the usual absolutely no response though... Anyone have insight into why the temperature would matter? something is overheating that this gives a bit of wiggle room since it starts much colder than usual? maybe a more complex analog electronic situation?
I would happily pull the flash chip off and put it in a emmc reader, but I think I'm out of luck because from what I've read the dm-crypt key is generated from some data stored in in the processor's trust zone thing. I know the "password" but if that's only part of what makes the key and the rest isn't on the flash chip I suppose there's no point in going that route.
I don't care about the hardware surviving; mostly just looking to recover my data. Anyone have suggestions? Hardware debugging direction? I'm willing to buy some electronics test equipment (within reason of course; not picking up a 10000USD rework station for some old photos and contact list...)

d_ckhole said:
Same problem here -- just froze for a few seconds, powered off, and won't turn back on. Not a boot loop issue as there is no response at all from any buttons. Swapping the mainboard from a working phone powered up without a problem, but obviously that's the other phone's emmc.
I tried the freezer thing and it sort of worked- LCD powered on for a couple seconds, but then shut back off again and even that only happened once. That's progress over the usual absolutely no response though... Anyone have insight into why the temperature would matter? something is overheating that this gives a bit of wiggle room since it starts much colder than usual? maybe a more complex analog electronic situation?
I would happily pull the flash chip off and put it in a emmc reader, but I think I'm out of luck because from what I've read the dm-crypt key is generated from some data stored in in the processor's trust zone thing. I know the "password" but if that's only part of what makes the key and the rest isn't on the flash chip I suppose there's no point in going that route.
I don't care about the hardware surviving; mostly just looking to recover my data. Anyone have suggestions? Hardware debugging direction? I'm willing to buy some electronics test equipment (within reason of course; not picking up a 10000USD rework station for some old photos and contact list...)
Click to expand...
Click to collapse
The only way to connect that buddy to PC is to get SoC (CPU) working, so theoretically you can go towards reballing the chip. But I guess it's not an easy thing for such a little chip. Also u will need kinda plate for balls, i think there are no common ones, so u can make it yourself if have a technical education.
Another way is to connect memory right to PC without a phone but with some connector. IDK if there are any available, but this looks much more simple. I actually got the same happened, and tried to heat the plate, but with particular success.
IMHO

orcgoblinsupply said:
Another way is to connect memory right to PC without a phone but with some connector. IDK if there are any available, but this looks much more simple. I actually got the same happened, and tried to heat the plate, but with particular success.
IMHO
Click to expand...
Click to collapse
Here's the reader
https://www.amazon.com/ALLSOCKET-eMMC169-Programmer-Kingston-Interface/dp/B06Y55DKND/
But I assume the problem is I will not be able to generate the encryption key because part of it is in the processor.
If someone has tried this and it definitely works, I'll give it a go. Just don't want to buy the emmc reader and heat gun this chip off if it's certainly a waste of time.

d_ckhole said:
Here's the reader
https://www.amazon.com/ALLSOCKET-eMMC169-Programmer-Kingston-Interface/dp/B06Y55DKND/
But I assume the problem is I will not be able to generate the encryption key because part of it is in the processor.
If someone has tried this and it definitely works, I'll give it a go. Just don't want to buy the emmc reader and heat gun this chip off if it's certainly a waste of time.
Click to expand...
Click to collapse
I've seen a post of a guy who sent his motherboard to china and got reballed it and gained 4gb of ram. Can be wrong, but it was around $50 and a month of time.
---------- Post added at 04:46 PM ---------- Previous post was at 04:40 PM ----------
Actually found the post itself: https://4pda.ru/forum/index.php?showtopic=722679&st=3440#entry68093395 (it's in russian, so u're welcome at translate.google.com) In short - a guy fount a Chinese service and men in the middle who could resend his motherboard to china, it cost him $100

Hardbrick , dead boot , no response , just red led blink

To all of member here.
I'm still waiting for another solution to solve my LENOVO P2 which is totally dead. only red led light when I connect to pc and charger.
I've tried the way given by brother "Hendibudi", but no results. previously the device was detected as HS-QD 9008, but when I will go into bootloader the process always fails with notification "error IO" and "no response"
then I want to try the QFIL method, but I did not find the filehorse and some files needed.
I confused my friends. is there anyone can help?
if anyone says "why not taken to lenovo service center?" then I replied: you must know they usually suggest to replace the part that cost equal to 80% of the sale price.so I took the initiative to struggle to fix it first, before I sold it.
I hope there from my friends here who kindly. hope god will reward you with happiness forever.
sorry if my english is bad, because i use google translate.
regards.

On rare occasions, when I'm flashing roms via fastboot, my newer P2 behaves in this way. However, I can always get it back in fighting shape by pressing the power button for about 15-30 seconds.

eried1 said:
On rare occasions, when I'm flashing roms via fastboot, my newer P2 behaves in this way. However, I can always get it back in fighting shape by pressing the power button for about 15-30 seconds.
Click to expand...
Click to collapse
thank you so much for your comment in my thread.
maybe you include getting luck in this case. you can still enter fastboot mode, but the bad news my device can not get into fastboot, can not enter recovery,just red led blinking, but I still feel there is hope because my device still can detected on the PC as HS-QD 9008.only I do not know what else to try again.but strangely on ADB method, my device is not detected ?? whereas in device manager, my device is detected as HS-QD 9008 brother ..
once again thanks for the advice. i will try it my friend .. hopefully work on my device ..

I saw an another thread to fixing hardbricked device pls chek that your phone will be fixed
Sent from my Lenovo P2a42 using Tapatalk

adzerrians said:
To all of member here.
I'm still waiting for another solution to solve my LENOVO P2 which is totally dead. only red led light when I connect to pc and charger.
I've tried the way given by brother "Hendibudi", but no results. previously the device was detected as HS-QD 9008, but when I will go into bootloader the process always fails with notification "error IO" and "no response"
then I want to try the QFIL method, but I did not find the filehorse and some files needed.
I confused my friends. is there anyone can help?
if anyone says "why not taken to lenovo service center?" then I replied: you must know they usually suggest to replace the part that cost equal to 80% of the sale price.so I took the initiative to struggle to fix it first, before I sold it.
I hope there from my friends here who kindly. hope god will reward you with happiness forever.
sorry if my english is bad, because i use google translate.
regards.
Click to expand...
Click to collapse
Mail me [email protected]

Shuvamilu said:
Mail me [email protected]
Click to expand...
Click to collapse
Please do not take discussions offline where others cannot benefit from the knowledge sharing.
I had this issue after I let the battery drain completely because my screen was broken.
When I replaced the screen and connected it, I only had a slow flashing red LED.
After charging it for maybe 15 minutes (try longer, preferably a night) I was able to boot it again by keeping the power button pressed, or maybe the home/volume combi as mentioned in the reset procedure.
So with a bit of luck just an empty battery. If nothing strange happened I can imagine the battery died, or the charger is bad.
Let us know how it went if still applicable, thank you.

adzerrians said:
To all of member here.
I'm still waiting for another solution to solve my LENOVO P2 which is totally dead. only red led light when I connect to pc and charger.
I've tried the way given by brother "Hendibudi", but no results. previously the device was detected as HS-QD 9008, but when I will go into bootloader the process always fails with notification "error IO" and "no response"
then I want to try the QFIL method, but I did not find the filehorse and some files needed.
I confused my friends. is there anyone can help?
if anyone says "why not taken to lenovo service center?" then I replied: you must know they usually suggest to replace the part that cost equal to 80% of the sale price.so I took the initiative to struggle to fix it first, before I sold it.
I hope there from my friends here who kindly. hope god will reward you with happiness forever.
sorry if my english is bad, because i use google translate.
I have same problem I read some devices need test point if they are dead but I don't know if our p2 has test point or not and if it has it is there any benefit?
Click to expand...
Click to collapse

hsheemi said:
adzerrians said:
To all of member here.
I'm still waiting for another solution to solve my LENOVO P2 which is totally dead. only red led light when I connect to pc and charger.
I've tried the way given by brother "Hendibudi", but no results. previously the device was detected as HS-QD 9008, but when I will go into bootloader the process always fails with notification "error IO" and "no response"
then I want to try the QFIL method, but I did not find the filehorse and some files needed.
I confused my friends. is there anyone can help?
if anyone says "why not taken to lenovo service center?" then I replied: you must know they usually suggest to replace the part that cost equal to 80% of the sale price.so I took the initiative to struggle to fix it first, before I sold it.
I hope there from my friends here who kindly. hope god will reward you with happiness forever.
sorry if my english is bad, because i use google translate.
I have same problem I read some devices need test point if they are dead but I don't know if our p2 has test point or not and if it has it is there any benefit?
Click to expand...
Click to collapse
Bro how ur device connected to device manager?
Click to expand...
Click to collapse

What happend for your phone to get to this state?
If you werent in the process of installing your ROM or ****ing around with root, some Lenovo p2's just die and show blinking red light. A friends p2 died and showed exactly the same symptoms ( started to smoke when charging, took it apart, dead motherboard). Just saying, sometimes you wont be able to fix it.

Sorry for the bump but my dad's lenovo P2 just dies this way, really have the feeling it is the battery, and since I also have a P2 I am going try to fix it.

OP, have you fixed your p2??

So my spare P2 seems to have given up. Slowly blinking red when charging.
Edit: Hm. No. Seems to be working, but the screen is pitch black. Can only view it if I am in complete darkness.
Edit 2: Changed the screens. Back to life! I truly recommend to change the original screen if you had it since 2017. Much better experience with my replacement.