Right I feel silly, knowing this I just couldn't resist trying to fix my "phone", so I've bought a S7 Edge from eBay from a trusted company with a 14 day refund which is good right?
We'll I couldn't rest as the phone was going into boot loops, i.e booting once every 5 times, going into the black screen of death with blue LED.(Had to wait for the battery to drain to 0%) https://youtu.be/K9T_UF-_5ho (Even though it booted at the end after a minute of use it crashed and went back into a boot loop and crashed and then it was fine for like an hour)
It would get stuck if I went to stock recovery, get this weird static line. I did boot into recovery once so I did a factory reset hoping it would fix something, which it did not. So I guess I was going to return the phone, I then had the stupid smart idea that it booting up fully and me activating it and then resetting it would be a good idea, and boy I was wrong. So it went to you know the usual "erasing screen" in which it would get stuck on, I did the hard restart maybe 4 times then it sorta worked the android guy kept spinning until IT JUST DIED.
And here we are now me typing this out, I feel like the company isn't going to accept it back due to it not being "functional".
Absolutely no sign of life now. Not even charging, this has happened before with it when I went into the recovery menu and it got stuck. I waited out an hour and then pressed ALL the buttons and the charging icon appeared but now, now I think it's different.
TLDR: Bad eMMC of phone, caused me to try to reset it and now it's bricked?
Well lesson learned? When things aren't working at the first place don't try to fix them just refuse outright.
Some say the phone can't be bricked but I feel like I really did it this time.
No the phone wasn't rooted, no I didn't flash with ODIN.
http://imgur.com/SxA0Q9b
http://imgur.com/QLLwhot
Just return it.
There is nothing else you can do and I see no reason why they wouldn't accept it unless there's a physical damage.
Sent from my SM-G935F using Tapatalk
Related
Hey guys,
I've done some searching on this issue, yet I can't find much besides battery problems, or people who have contacted T Mobile and got warranty replacements. I've had some issues with my G1. Over the past month or two, my G1 has been rebooting repetitively, and this week it's gotten BAD. I would open a SMS, and then BAM. Start dialer, and then BAM. Reboot. Hell, even in the middle of a reboot it would reboot. Cool huh?
Anyways I called T-mobile customer support and they said I'm out of warranty. Great. Well, it still turns on, and it still operates when it's happy, so maybe I can work with this for a little bit... I did some searching, and some people attributed it to a software glitch in the gyroscope... Most people called T-mobile and got a warranty replacement. I'm over the one-year
I'm not about to say this is because I had CyanogenMod on it, because I would wipe, and put it back to an older version and it would still reboot... even in the SPL, it would reboot. But regardless, I decided to follow this how-to to unroot my G1: http://forum.xda-developers.com/showthread.php?t=491350
After step 6 (6. Push Alt+S on your G1 to flash it with update.zip), it came up with an error about the splash... "Cant store hboot image."
Well anyways, before I could do anything about it, guess what happened?
Yeah, it rebooted.
It came up with the unboxing logo at first, I didn't know what to do. I had forgotten what this meant, so I heled the power button down ( I realize this may have been the misteak I made, however there was nothing visual indicating anything was being done).
It shut down, the screen went blank, the charge LED remained on....
I pressed power.... Nothing.
I unplugged the phone, took out the battery.... put the battery back in... Nothing. The screen stayed black. Now my phone will not power up, and there is no LED charging indicator.
Anyways, I'm lost. This is my second G1. I'm slightly pissed and I feel bad for the T-Mobile rep on the other end of the call I just had, but, really, I can't spend $1200 a year on a slow phone.
Do any of you guys have any suggestions?
Home+power does nothing.
Camera+power does nothing.
Putting in the cable lights up no LEDs...
It is literally a brick. An unresponsive brick.
Well, I ended up taking the mainboard out of my old phone and putting it in this G1.... Everything should be back to normal however I'm still looking for responses as to what might be happening.
Hello i have a question regarding my recently water damaged galaxy grand prime (rather not discuss how it got wet) but the top portion of my phone got submerged. I immediately removed the battery and vacuumed out water for a few minutes, tested it to see if it would power on (i know, too soon. So stupid) and to my dismay the camera flashed upon the battery touching the connectors inside the phone so im guessing something shorted there. I proceeded to let it sit in rice for the day but i dont have much patience and was missing using my device with cm12.1 flashed and kept checking it every 4-5 hours or so. So at the end of the day i took it out the bag of rice, powered it on, and everything was functioning as it should, besides a little screen flickering which has disappeared entirely now. But here and there and random times im not using my phone, it will restart and get stuck on the "Samsung Galaxy Grand Prime Powered By Android" screen. It wont make it to the boot animation or even go into recovery, but it will boot download mode. So after pulling the battery a dozen times i finally get it to boot again and i go into recovery and try repairing the system with TWRP repair or replace file system option thinking it could probably help. But to this point my phone still restarts by itself and gets stuck on the logo screen here and there and i have to fight it to boot system. Could somebody please help me out here? I hope it isnt a hardware failure and just some software corruption i can fix by factory resetting and re-flashing the rom. Any help is highly appreciated. Oh and i forgot to mention my camera definitely shorted somewhere only the rear works and if i try to switch to front it cant connect. This happens in snapchat and the cameranextmod cyanogen camera. My stock one stopped entirely.
If your phone got submerged, i'm afraid it'll damage the hardware, sorry bro, you'll have to let it go
I decided to start a thread because I noticed there were multiples about this issue. So 3 days ago I was on Facebook when my phone randomly froze. I pushed the power button, and that's when it began bootlooping. I instantly tried booting into recovery with no success. I was hopeful, however, because I could still access the bootloader. I got on my computer and began researching the issue and steps I could take to fix it. I tried every method out there and was unsuccessful. I ended up buying a Pixel today off Craigslist and am loving it so far. So anyway since my Pixel came with the OEM charger, and I had been using a non-oem ever since I had my 6P, I decided to plug in the OEM and see what happens. Within the first hour my 6P began to get very hot, almost to the point where I couldn't even hold it in my hand. Keep in mind the phone was still consistently boot looping the whole time. So I decided to unplug it. Well I left it sitting and went about my business and when I came back to my bed I noticed it was doing the Google boot animation!!!! I started freaking out! After it booted up I finished the tutorial stuff and just let it sit on the home screen for a second. I noticed the battery was low so I figured I would plug the charger back up and let it charge. Well in the time it has taken me to write this post, it just started boot looping again... Lol. So I just unplugged the charger AGAIN, to see if it will boot up again. To me, it seems like there might be a hardware issue with my battery. Anyway, my 6P was rooted and running nitrogen OS (wasn't running the latest build but was 7.1.)
what are the exact symptoms? and does it boot into bootloader and recovery if not what is it physically doing?
dontbeweakvato said:
what are the exact symptoms? and does it boot into bootloader and recovery if not what is it physically doing?
Click to expand...
Click to collapse
As of now it is still boot looping and no it doesn't boot into recovery. Only symptoms I've noticed is the phone starts to get extremely hot when I plug in the OEM charger that came with my Pixel. I figured they were the same so that's why I decided to use it since it was OEM.
I had a 6p that bootlooped eternally couldnt access boot or recovery, I sent it in and they sent a new one. Board was damaged.
I also had a nexus 5 that bootlooped and it turned out to be a bad power botton. the internal connection was broken so it would get power and lose power all in the same second, off and on but too fast to see other than seeing a bootlooping device. that was fixed with a new power button which had to be soldered on.
if not on warranty you could take to a cell phone repair shop maybe they might be able to fix the issue.
dontbeweakvato said:
I had a 6p that bootlooped eternally couldnt access boot or recovery, I sent it in and they sent a new one. Board was damaged.
I also had a nexus 5 that bootlooped and it turned out to be a bad power botton. the internal connection was broken so it would get power and lose power all in the same second, off and on but too fast to see other than seeing a bootlooping device. that was fixed with a new power button which had to be soldered on.
if not on warranty you could take to a cell phone repair shop maybe they might be able to fix the issue.
Click to expand...
Click to collapse
It is under warranty, but the sad part is that I no longer have the receipt for it. I got the phone off Craigslist and the guy gave me the original box and receipt but I managed to lose it. I haven't been able to get it to fully boot back up again since last night. I'm not that worried about it anymore because I already have a new phone, but I wouldn't mind if it were to some how fix itself lol.
e1ement08 said:
It is under warranty, but the sad part is that I no longer have the receipt for it. I got the phone off Craigslist and the guy gave me the original box and receipt but I managed to lose it. I haven't been able to get it to fully boot back up again since last night. I'm not that worried about it anymore because I already have a new phone, but I wouldn't mind if it were to some how fix itself lol.
Click to expand...
Click to collapse
my first bootloop years ago i thought the same.
it wont fix itself. its not a software isssue because youd be able to at least boot into bootloader. it sucks to hear the truth but thats the truth.
its a hardware issue and you could take it to a repair shop because they will inspect and fix. small drops that dont harm the device can ultimately cause small breaks in the solder joints so who knows what is wrong without inspection
Hi all,
Hopefully this wasnt covered before- I used the search function and it didnt return any results, at least not for my specific scenario.
I've had this 6p for about 18-20 months roughly. Been my best phone by far, and I've been very happy with it(normally i replace my phones every 8-12 mos because I need the latest and greatest lol).
About six months ago I threw PureNexus on there with I believe Flash kernel. Worked flawlessly, and I've been really happy with it.
About a week ago, it powered off on its own but i had it in my back pocket so I just assumed it was an accidental reboot. However, this morning, I woke up, threw it on the charger for about 30 minutes, got to about 60%, and unplugged it. While I was using the browser, it froze up for a minute then shut down. No bueno. Cannot get it to power back on. No power light while charging. I did what others have had luck with, holding power, and/or power/down for several minutes, still nothing.
I reached out to Project Fi, and they want a 500 dollar hold to send me out a refurb replacement. I know they release the funds in approximately 12 days but we had a recent death in the family and I just cannot afford to have 500 bucks locked up, especially right now. Spoke w a supervisor, apologized, but said nothing they can do.
On a whim, I plugged it into the pc, and it DOES detect it but its the dreaded QHSUSB_BULK under 'other devices'. So that tells me its at least got power, but, I'm unsure if just trying to use adb(i havent in a while, not since i did the initial rom install but im sure i can find instructions) to attempt to throw the base image back on there, will work, or which direction to go.
I found this but I dont think its for my specific phone but thought maybe there was a set of instructions for this particular phone similar to these:
https://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I have seen several reports of this error happening when flashing the wrong rom, or using the wrong image, but never just all of a sudden when its been running like a champ.
any thoughts? thanks in advance.
Nexus 6p is plagued with issues like shutting down at certain percentages and the dreaded bootloop of death. You could get in contact with Google heard even people out of warranty having success. Could also have a shop replace the battery in some cases that fixed the shutdowns.
If it doesnt boot up at all I can't help you. If you can get to bootloader, flash stock image, un-root, re-lock your phone. see if it boots. I had to do all this, this morning. Phone would just shut off at 80%, reset and hang at the google sign. I could only get to into the main system with a hard reset every time. then it would reset and lock up. So i reverted it to stock and we will see how it goes. So far its been 6 hrs and no random resets and its in full use.
Yea, the problem is, I cant. Its not even a boot loop. Just looks like its dead. Held the power button down for roughly 10 minutes out of desperation.
The odd thing is, if i plug it into my pc it shows how i mentioned in my initial post. So it must have juice even though the power light/etc isnt on and it doesnt show charging.
Last hope I think i have is to run it out of battery leaving it on the table, then hope somehow when i plug it into charge, that resets it somehow since it was dead, and maybe clears whatever the issue is. Very odd considering it was working fine until this.
Your phone is stuck in the EDL mode when its detected as QHSUSB__BULK. There are solution for this but i dont know if this solution is combined with data loss or not and i try to find that out recently. I also still dont know how to fix that with linux.
Here two howtos:
https://forum.xda-developers.com/nexus-6p/general/guide-how-to-bring-to-life-dead-nexus-t3581948
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
This is an out-of-the-box Verizon S7. Never tried to root it or do anything with it. Out of seemingly nowhere, it just stopped turning on today. I know it sounds weird that I haven't touched the phone and it mysteriously "just stopped working," but I swear. It was working fine about 3 weeks ago. I left it uncharged (dead) on my desk for about 2 - 3 weeks without touching it. Now it won't boot. I contacted Samsung and my phone is out of warranty by 5 months.
I downloaded Odin 3.12.7. I booted the phone into Download Mode and flashed an Android 7.0 file from this website. After flashing the phone, it started to turn on properly, but then abruptly got thrown back into a boot loop before getting to the lock screen.
What can I do? I really just need my pictures and stuff off this phone, but it would be great if there's a way to make it work like it did 3 weeks ago.
edit: nvm. battery is shot, won't hold a charge and won't boot up for some reason.
Lithium Ion batteries don't like being stored with no charge at all! It's very likely that you've killed your battery and it can no longer generate or keep the voltage at the right levels. See this article about storing Li-Ion batteries for a better understanding.
EDIT: nvm. didn't see the edit.
if you flash twrp you can mount and take files off, i believe
Fridder said:
This is an out-of-the-box Verizon S7. Never tried to root it or do anything with it. Out of seemingly nowhere, it just stopped turning on today. I know it sounds weird that I haven't touched the phone and it mysteriously "just stopped working," but I swear. It was working fine about 3 weeks ago. I left it uncharged (dead) on my desk for about 2 - 3 weeks without touching it. Now it won't boot. I contacted Samsung and my phone is out of warranty by 5 months.
I downloaded Odin 3.12.7. I booted the phone into Download Mode and flashed an Android 7.0 file from. After flashing the phone, it started to turn on properly, but then abruptly got thrown back into a boot loop before getting to the lock screen.
What can I do? I really just need my pictures and stuff off this phone, but it would be great if there's a way to make it work like it did 3 weeks ago.
edit: nvm. battery is shot, won't hold a charge and won't boot up for some reason.
Click to expand...
Click to collapse
Have you tried factory reset and wipe cache from stock recovery?