Related
So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
stealth.kid said:
So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
Click to expand...
Click to collapse
It reminds me Desire S problem - fried emmc chip... If your phone has no valid warranty, I'm suggesting to see phone's internals and inspect emmc chip.
The phone still has warranty, I will try to have it repaired/replaced. The only thing I'm concerned about is the fact that it was S-OFF and running a custom ROM... And I don't have the knowledge or equipment to try to take it apart and fix it myself
If you have warranty just use it they won't be able to ckeck if phone was unlocked or not since it can't boot up.
Background, I have a Droid Maxx that I purchased/leased from Verizon, that arrived with 6-7.2. I downgraded to 6-7 and rooted. From the time of purchase the phone would reboot a few times a week. After rooting it began to reboot usually daily or many times a day. A week ago on Saturday it rebooted and began to loop from splash screen and back off. After many restarts it went into the factory recovery and no options would work and the screen forever went black. It has been charged for days, no button combinations work, except when plugged into the computer while holding the down vol it will load the hsusb drivers will sometimes load, and occasionally when connected to the computer or wall charger the green led will light. So I took the phone into verzion and they see the same results and attempted to charge it with both a cable and wireless, same results. So they shipped a new unit to me and before shipping this old one back to them I have a few questions for ones of you that may know the answer:
Anything I can do to restore it to stock? I assume no from my research
Will they discover its rooted?
If so what will be the resulting action?
Thanks for taking the time to read this.
Hi..
It's just a guess, but I don't think they waste any time trying to figure out what happened, specially since they already gave you a new unit. I would say, Don't bother
Enviado desde mi XT1080 mediante Tapatalk
ZMaissi said:
Hi..
It's just a guess, but I don't think they waste any time trying to figure out what happened, specially since they already gave you a new unit. I would say, Don't bother
Enviado desde mi XT1080 mediante Tapatalk
Click to expand...
Click to collapse
Thanks, that is sort of what I was thinking. I suspect the boot partition is corrupt. But, wasn't sure being a new customer with Verizon.
Hey can you link me something about how you downgraded your droid ultra from SU6-7.2 to SU6-7
LOL, just flash SU6-7 (CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml) with RSD-Lite. That's the easiest way.
rfunderburk39 said:
Background, I have a Droid Maxx that I purchased/leased from Verizon, that arrived with 6-7.2. I downgraded to 6-7 and rooted. From the time of purchase the phone would reboot a few times a week. After rooting it began to reboot usually daily or many times a day. A week ago on Saturday it rebooted and began to loop from splash screen and back off. After many restarts it went into the factory recovery and no options would work and the screen forever went black. It has been charged for days, no button combinations work, except when plugged into the computer while holding the down vol it will load the hsusb drivers will sometimes load, and occasionally when connected to the computer or wall charger the green led will light. So I took the phone into verzion and they see the same results and attempted to charge it with both a cable and wireless, same results. So they shipped a new unit to me and before shipping this old one back to them I have a few questions for ones of you that may know the answer:
Anything I can do to restore it to stock? I assume no from my research
Will they discover its rooted?
If so what will be the resulting action?
Thanks for taking the time to read this.
Click to expand...
Click to collapse
Possible input hopefully it helps with your issue. Something similar has happened to me, but it was not software related. I am BootLoader Unlocked, but the only mod is for tether.
My phone would continuously reboot, but all I ever see is a black screen. sometimes when it stops rebooting the phone was actually powered on and responds to my voice commands, rings from calls, and notifications sounds work, but black screen.
My issue was actually due to the screen/LCD connection getting a little loose . Tech took phone apart disconnected and reconnected my screen, and problem solved. No more boot loops nor black screen.
It happened to me again a few months later, but I had dropped the phone a couple of times, which probably caused the loose screen connection a second time. After getting fixed again, I have had no issues, but then again, my Maxx also hasn't had any bad falls.
Mangu said:
Possible input hopefully it helps with your issue. Something similar has happened to me, but it was not software related. I am BootLoader Unlocked, but the only mod is for tether.
My phone would continuously reboot, but all I ever see is a black screen. sometimes when it stops rebooting the phone was actually powered on and responds to my voice commands, rings from calls, and notifications sounds work, but black screen.
My issue was actually due to the screen/LCD connection getting a little loose . Tech took phone apart disconnected and reconnected my screen, and problem solved. No more boot loops nor black screen.
It happened to me again a few months later, but I had dropped the phone a couple of times, which probably caused the loose screen connection a second time. After getting fixed again, I have had no issues, but then again, my Maxx also hasn't had any bad falls.
Click to expand...
Click to collapse
In the case of my phone, you could hold the power button in for a long period of time and then release and still nothing, not a flicker. I did not try voice commands, not a bad idea, but I did not want to open the phone due to the fact it was being replaced (further risking a decline on replacement).
On a similar note, the new unit seems to reboot at least once daily.
My phone: Nexus S, 16Gb, Rom CM11, Android 4.4.4 (List of updates: https://download.cyanogenmod.org/?device=crespo)
My story
Yesterday, (about 9.00pm 13/12/2015) my phone got some laggy, so I powered him off. I left it there, 15 minutes later I came back, and I forgot that he had been powered off, so I thought it was just sleeping. I picked him up and press PowerButton. Nothing happended!
Then I got a look at CM rom, found that interesting is my Rom just got a new update at 2.00pm 13/12/2015. I think that my phone has auto-updated!!
In the past, sometime he behaved the same: PowerButton not respond. So, after that 1st press, about 5 sec later, I started to press the PowerButton repeatedly and rapidly, hopefully the phone would wake up.
But no, the reality was that he was being off. There were about 6-7 presses, I will describe slowly below (assume between each press is 0.2 sec):
1st and 2nd press: nothing happened
3rd press: the phone vibrated, and Google logo appeared
4th press: (I had no mean to continue pressing, but it was too fast, I couldn't stop) suddenly, the Google logo disappeared (so the logo stayed on screen just for about 0.2 sec; while normally, it should stay there for atleast 5 sec)
5th and 6th press: nothing happened!
And from then on, no more, anything happened.
What I tried
Hold PowerButton for even 1 minute: nothing happen!
Hold PowerButton + VolumeUP for even 1 minute: none!
Hold PowerButton + VolumeUPandDOWN for even 1 minute: none too!
Connect to charger (wall or pc): no Battery Animation show up! BUT the phone and Battery get warming up!
Take out the Battery for even 15 minutes, then put it back, and PowerButton: nothing!
And the phone not get recognized by PC too.
Sumary
No display
No vigration
No recognized by PC (because of this, I can not follow this method: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
More Information
In the past, the VolumeDOWN sometimes seems get stucked, cause the phone silent and auto boot to safemode, after many try to press and reboot, the phone may get out of safemode (because VolumeDOWN back to normal)
PowerButton sometimes not respond.
My Battery is not good, sometimes it drops too much! Eg: having 50%, after reboot, dropped to 3%, and start to increase slowly, max around 30% and become normally.
Hope you guys have some ideas! I still can't do anything, when the phone is not regconized by PC!!
Thanks for reading!
Thank you!
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
demkantor said:
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
Click to expand...
Click to collapse
Thank you. I'll try your suggest ASAP.
But I'm wondering, that do you think that CM Update maybe also a reason?
I kind of doubt it as that should only effect the software, if you were getting a bootloop or anything to that extant yeah, but being it won't power on at all I doubt it
thank you
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See: https://wiki.cyanogenmod.org/w/EMMC_Bugs
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
FalconFour said:
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See:
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device[/URL] to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
Click to expand...
Click to collapse
thank you!!
my heart just stop breathing :'( :'(
God, I wish there were a solution to it. I'd really like to donate a phone to anyone that thinks they have the tools or skills to make a "how I did it" explanation - involving whatever tools/software are necessary - to bring these phones back and help us all. I bought 2 of those 3 phones as "for parts" on eBay, and it turned out that both of those phones appeared to have exactly this same issue (though one also had a cracked glass). I even verified the issue by swapping in my good phone's eMMC (at least on the NS4G, it's a swappable card module), and the boards booted up. I only needed the one for the good screen (as I had a good board but completely destroyed display panel) - and that's how I got my one working again.
Then, in the end, I accidentally stumbled upon the method by which the previous two phones were bricked - and now there are three. It seems like a fairly common problem. :/
Hi,
I think I have bricked my S7.
Yesterday I installed Superman Rom and everything was working fine until this afternoon.
I played a bit around and somehow my S7 got stuck and it seemed like i messed something up. I was in some kind of bootloop so i flashed everything new -Bootlaoder, Modem and Superman Rom.
Now I have a black screen and the LED is light up in blue.
I can't do anything. Tried to restart with Home Vol- and Power key but it doesn't work.
If I connect it to the Computer it won't be recognized.
Strange thing is, if I press the Power Key the computer recognizes Exynos8890 in the device manager, but only if I keep pressing the power key.
As soon as I release the power key the computer recognizes nothing...
Does anyone have an idea?
Try holding Volume Down & Home & Power until the phone reboots twice, keep the buttons pressed for 2 full reboots, and hopefully the 2nd one will get you back into download mode
Thank you for your help!
I tried that but it doesn't work.
It's strange because I can do what I want and nothing happens.
Black screen and blue light. It doens't even turn off or reboot...
Only thing what happens is that exynos8890 appears in the device manager as long as I keep pressing the power button.
Same problem as me?
http://forum.xda-developers.com/galaxy-s7/help/boot-loop-bricked-t3499109/post69596073#post69596073
Sounds different.
Because you are able to get into recovery and download. I'm not able to do that
alexx3333 said:
Sounds different.
Because you are able to get into recovery and download. I'm not able to do that
Click to expand...
Click to collapse
How long are you holding the button combination for?
Try 30 seconds+
I tried for several minutes, but the phone doesn't do anything.
I can only think you'll need to wait until the battery runs out, the phone shuts off, then when you charge it again, try the download mode button combo when you power it back on
Ok thank you.
I thought the same.
Unfortunately the battery was at 90% so I think it will take a few days/weeks until it dies...
alexx3333 said:
Ok thank you.
I thought the same.
Unfortunately the battery was at 90% so I think it will take a few days/weeks until it dies...
Click to expand...
Click to collapse
Connect the white Micro > Normal USB adapter that came with the phone to the MicroUSB port, and connect a power hungry USB device to it, I just tried with a USB desk fan and the phone powered it on spinning
That will drain the battery quickly
Great idea but it doesn't seem to work.
Looks like I have no power in the USB connection.
Seems like the phone is totaly frozen.
Ok so how it looks at the moment, my only choiches are wait several days until the battery dies (don't know how long this will take) or sending it to Samsung for a repair.
Thank you for your help!
Good luck, if I think of anything else I'll reply here, hope you get it sorted
EDIT - Did you try holding the power button while you had the USB device connected, to see if it provides USB power then?
Wow, the exact same thing literally happened to me yesterday.
I wasn't doing anything to the phone - it's completely stock and unrooted, and I wasn't messing with anything. At the time it happened, I scrolling through the task switcher when all of the screenshots of running apps suddenly became white squares. I tried pressing the home button but it didn't respond (though I could still scroll fluidly through the white squares). A few seconds later the screen went black and that was it. Dead dead dead. Totally bricked. The only response I can get is "Exynos8890" in the Device Manager when holding the power button, just like you.
This really sucks because I paid full cash and imported an international version, so I have no warranty. I'm off to the Samsung store to plead with them about honoring the warranty anyway, maybe if I offer some cash on top.
I suspect the storage chip failed. Yesterday before it died, I was downloading all of my images off of the SD card to organize them, and I noticed that about 5% of them failed to copy due to an unknown I/O error. Of course I assumed this was a corrupt SD card, not internal storage. I did manage to pull them all off (though some were damaged) through a combination of adb shell, dd, and adb pull. During the process the phone hard-locked a few times, but each time I was able to reboot via the VolDown+Power combo.
When the phone finally died for good, it was several hours after I had finished copying the photos and since hte last reboot. It had been working perfectly since then - I was browsing reddit, watching netflix, etc. However, given that I got the white squares in the task switcher right before it kicked the bucket, I think the internal storage was actually to blame, not the SD card. The white squares indicates that it was trying to fetch the screenshots off the disk and failing.
It's very odd that I cannot find any other instance of this kind of failure on the internet except this one thread, which happened on the exact same day that my phone died. Very strange.
*Detection* said:
Good luck, if I think of anything else I'll reply here, hope you get it sorted
EDIT - Did you try holding the power button while you had the USB device connected, to see if it provides USB power then?
Click to expand...
Click to collapse
Yes I have tried that but no power at all...
stoanhart said:
Wow, the exact same thing literally happened to me yesterday.
I wasn't doing anything to the phone - it's completely stock and unrooted, and I wasn't messing with anything. At the time it happened, I scrolling through the task switcher when all of the screenshots of running apps suddenly became white squares. I tried pressing the home button but it didn't respond (though I could still scroll fluidly through the white squares). A few seconds later the screen went black and that was it. Dead dead dead. Totally bricked. The only response I can get is "Exynos8890" in the Device Manager when holding the power button, just like you.
This really sucks because I paid full cash and imported an international version, so I have no warranty. I'm off to the Samsung store to plead with them about honoring the warranty anyway, maybe if I offer some cash on top.
I suspect the storage chip failed. Yesterday before it died, I was downloading all of my images off of the SD card to organize them, and I noticed that about 5% of them failed to copy due to an unknown I/O error. Of course I assumed this was a corrupt SD card, not internal storage. I did manage to pull them all off (though some were damaged) through a combination of adb shell, dd, and adb pull. During the process the phone hard-locked a few times, but each time I was able to reboot via the VolDown+Power combo.
When the phone finally died for good, it was several hours after I had finished copying the photos and since hte last reboot. It had been working perfectly since then - I was browsing reddit, watching netflix, etc. However, given that I got the white squares in the task switcher right before it kicked the bucket, I think the internal storage was actually to blame, not the SD card. The white squares indicates that it was trying to fetch the screenshots off the disk and failing.
It's very odd that I cannot find any other instance of this kind of failure on the internet except this one thread, which happened on the exact same day that my phone died. Very strange.
Click to expand...
Click to collapse
That sounds exactly like my Problem.
A faulty storage chip would also explain my Problems before the phone died for good.
The day my phone died I had some Problems. The phone was frozen from time to time until it got into the bootloop, but I thought I messed something up in the Rom because I did a lot of testing and the Combo also did work.
After reflashing the Rom everything seemed to be fine first until it died for good.
Yes it's strange, I also didn't find anything similar on the Internet.
I have learned my phone is from Nigeria. This should be a fun RMA process. FML
stoanhart said:
I have learned my phone is from Nigeria. This should be a fun RMA process. FML
Click to expand...
Click to collapse
Contact Samsung on twitter, unlikely they'll force you to RMA to Nigeria, they'll have service centres in your region
I managed to get Samsung Canada to refer me to a local service center. I drove 1.5 hours to go there today, the dude plugs it into a charger, and the damn thing just lights up like nothing ever happened. Now it's working fine, but I swear this thing was fully bricked before. The battery still had 73% charge when it came back alive...
I'm happy it's working now, but I'm worried it's just going to crap out again at any time.
Update: after the phone revived itself, it worked pretty well for a week. It locked up a few times, but I was able to reboot each time.
But, after a week, it hard-froze again. This time, it happened to be on charge while it froze so the green LED was on. It's been completely unresponsive for 2.5 weeks now, off charger, with the green LED on. I keep waiting for the LED to drain the battery, but it's taking forever. I'm losing hope that it will recover this time. I guess I'll re-start the process of getting in touch with Samsung, or alternatively, look for a replacement motherboard on eBay.
Does anyone know if the G930F motherboard fits into the G930FD body? I don't actually care about dual sim, but I'm concerned the SIM tray/slot won't work with the G930F motherboard.
Update:
so in the meantime the battery of my s7 died but that didn't change anything. I wasn't able to charge it after that so now it was completely dead.
So I contacted Sasmsung.
They replaced the motherboard and the USB connector on warranty.
Seems like it really was a hardware issue...
alexx3333 said:
Update:
so in the meantime the battery of my s7 died but that didn't change anything. I wasn't able to charge it after that so now it was completely dead.
So I contacted Sasmsung.
They replaced the motherboard and the USB connector on warranty.
Seems like it really was a hardware issue...
Click to expand...
Click to collapse
Hi,
Do you need Proof of Purchase for the warranty?
Thanks.
Hello,
I had an accident and after that my Nexus 5 screen was broken. So I decided to buy an new one from Amazon (~60$) and I tried to replace the screen on my own.
Yesterday I replaced the screen with a YT-Video, then I charged my Nexus 5 an the "Charging-Symbol" showed up.
After that I left the house for 2 hours and when I came back (I left the Nexus at home for charging ofc.) I tried to turn on the phone and nothing happened.
Then I tried to press power and volume down to get into the boot-menu and this also worked and the screen showed everything perfectly (!) and then I tried to start my handy from the boot-menu.
Until then everything has worked well but during the start progress I noticed that the (starting-)animation is really slow and laggy, so I decided to try to reboot my phone by holding power off for around 10 secs.
I tried to start my phone one or two times more and tried to get into the boot-menu, restart bootloader, etc. and then I realized that my phone didn't even want to work anymore. I could(and can) neither get into the bootmenu nor simply start it...
Do you have any ideas?
What suprised me the most is that it stopped working so quickly, so I concluded that I replaced the screen right but anything else went wrong...
Please help me :/
PS:
USB-Debugging is turned off and I cant access my phone with my pc or anythin else
Leave the phone on the charger for about an hour and then try to get into the bootloader.
When my phone is in the process of booting and I force it to power off by holding down the power button, it will not power up until I either leave it on a charger for a bit or leave it power off for a bit, usually 5 to 20 minutes.
audit13 said:
Leave the phone on the charger for about an hour and then try to get into the bootloader.
When my phone is in the process of booting and I force it to power off by holding down the power button, it will not power up until I either leave it on a charger for a bit or leave it power off for a bit, usually 5 to 20 minutes.
Click to expand...
Click to collapse
Thanks, now I could get into my phone and enable USB-Debugging with much lock D)
My problem is, that my phone runs very unstable and shuts down often so I can't really work with it.
Do you know any solution and the more important question:
How can I save my data? I think, that I can save it anyhow if I enabled USB-Debugging with the bootloader and a pc, can't I?
Yes, you could pull the data from the phone using ADB commands.
You could also flash twrp to the phone. Once flashed, you could boot into twrp, mount the data partition, and copy data from the phone to the computer.
You could also use twrp to create a nandroid backup for safekeeping.
Is it possible that there is a loose connection in the phone? Have you tried disassembling and re-assembling?
audit13 said:
Yes, you could pull the data from the phone using ADB commands.
You could also flash twrp to the phone. Once flashed, you could boot into twrp, mount the data partition, and copy data from the phone to the computer.
You could also use twrp to create a nandroid backup for safekeeping.
Is it possible that there is a loose connection in the phone? Have you tried disassembling and re-assembling?
Click to expand...
Click to collapse
I have now moved on!
My charger cabel was broken but now I got a new one!
I can start my Nexus (with some issues) and it runs but sometims it still shuts down and always when I try to plug in my cabel into the Nexus the screen gets black (but on the side you can see that the screen is light up in some way, idk...)
Is there a reason for the heating and for the shut downs? :/
I'm not sure but it seems like the screen has suffered a hardware malfunction because you can see that the backlight is on but no image.
audit13 said:
I'm not sure but it seems like the screen has suffered a hardware malfunction because you can see that the backlight is on but no image.
Click to expand...
Click to collapse
And that means what?
And can I do anything for it? Maybe flash it or something?
Reset, etc..
With a hardware failure, there's nothing that software can fix. Did you try disassembling and re-assembling the phone?
With the old screen, can you see anything on screen? Did the phone power up and charge properly? If yes, put on the old screen to test the other components to see if it charges and powers up.
audit13 said:
With a hardware failure, there's nothing that software can fix. Did you try disassembling and re-assembling the phone?
With the old screen, can you see anything on screen? Did the phone power up and charge properly? If yes, put on the old screen to test the other components to see if it charges and powers up.
Click to expand...
Click to collapse
Yeah first sentence makes sence..
I swapped software and hardware, sry
my other screen doesn't work at all, completly destroyed...
The problem is that I can't imagine what should be the failure...
And yeah, I already tried disassembling and re-assembling it...
Still same problem
I have used cheap 3rd party screens to replace a few N5 phones and they quality is very inconsistent so I wouldn't be surprised if a 3rd party screen fails after a short period of use.
audit13 said:
I have used cheap 3rd party screens to replace a few N5 phones and they quality is very inconsistent so I wouldn't be surprised if a 3rd party screen fails after a short period of use.
Click to expand...
Click to collapse
Nahh but the screen works I think..
Everything looks clear etc and the screen wasn't really cheap with 65$-70$ I guess..
I think it's something else because my phone gets really on near the CPU and this can't be because of the screen...
Where did you get the screen?
If it gets really hot near the cpu, then something else is going on. Could it be possible that there is a short-circuit somewhere?
Since the value Canadian dollar has dropped, I'm also paying about $60 for what was a $40 screen.
audit13 said:
Where did you get the screen?
If it gets really hot near the cpu, then something else is going on. Could it be possible that there is a short-circuit somewhere?
Since the value Canadian dollar has dropped, I'm also paying about $60 for what was a $40 screen.
Click to expand...
Click to collapse
Yeah, I also thought about a short-circuit but I don't know how I can test this.
When I try to start my phone it fails like 4-5 times and then it works most of the time. The fail looks the following:
The "Google" logo appears and then suddenly the screen gets black, but not the "out"-Black (so that screen it out), I mean the "on, but black"-Black (hope u can understand.. xD)
During this 4-5 Tries my phone feels like 40°C-50°C (sry im from Germany, idk the conversion to °F value.. )
After this (I got the phone running one time for about 20 minutes) the phone doesn't heat up so much, if it starts right I think that the temparatur problem is over, but there is still the problem (also if the phone is running for 20 minutes) that it suddenly shuts down... :/
Sorry, idk much about canadian dollar, like I said im from germany and I payed around 65€
Google says, that this is around 67 (US-Dollar)
I don't know what to suggest other than either getting a new battery or new screen. Both items can be very expensive.
audit13 said:
I don't know what to suggest other than either getting a new battery or new screen. Both items can be very expensive.
Click to expand...
Click to collapse
Mhh, ok :/