Database Users

Thanks for the ride

So my otherwise trusty I9100 decided that it wanted to sleep the eternal black sleep. Yesterday it locked up and I had to remove the battery. When powered on, it asked for the password for the encrypted storage (I do not have encrypted storage that I know of). I could only power off or reboot at that point. I chose shutdown and let the phone rest for a couple of minutes. Then I started it again and then it went into eternal boot loop. I powered off by holding the power button and when that seemed to fail, I removed the battery. I tried to enter the normal boot menu (running standard firmware 4.1.2). This failed. I tried to use the volume down+home+power button and that to my relief showed the warning about installing a custom os. I proceeded and Odin started on the phone. Great I thought. I can at least flash the phone and have a phone again. I downloaded the firmware and Odin 3.0.7 and proceeded to flash. Odin 3.0.7 could detect the phone and started sending the cache image preparing instructions to the phone. This took a long time and then it timed out. The phone still showed the Odin downloading screen. I tried to restart the software on the pc, but that failed right away. I tried to restart Odin on the phone, but the phone was now completely dead. Black screen forever.
For reference, I have flashed with Odin before (long time ago) and it worked as intended. Besides, I was following the troubleshooting guide presented here on this site for the S2 and right now, I can get zero signs of life from this phone.
Seeing as my friends S2 died after 2-3 years with black screen of death and my sisters S2 died with black screen of death, also after approx 2 years and now my phone after close to 3 years, I can only suspect that Samsung has made the phone to die this fast. I only know of 2 more persons that have such a phone and their phones are not so old yet. But I guess theirs will die after 2-3 years as well. :-/
So, it was interesting having a smartphone and I liked it, but now I am back on my trusty old Nokia i6110 (has run 11 years without issues and with original battery, still lasting 3-4 days per charge).
But I'd like a new smartphone, just not a Samsung. They have burned me enough.

I just learned that the phone might be salvageable using the JTAG interface. So, any JTAG'ers around the Århus, Denmark area?

galmok said:
I just learned that the phone might be salvageable using the JTAG interface. So, any JTAG'ers around the Århus, Denmark area?
Click to expand...
Click to collapse
There's a thread called jTAG centre near you or something like that, look it up, maybe you can stike luck.
My device is like 3 years now, but it's gonna live forever, I'ma see it thru

If you have any linux (get a live cd for free everywhere) at hand post 'lsusb' into an terminal when the phone is connected. if it shows up any sign of an active usb device it might still be alive, else it truly is a jtag case

Phone instantly reboots?

I was listening to an audiobook when my phone suddenly died. It would not start back up, so I removed the battery. When I replaced the battery, the samsung logo would pop up but after about a second it would go black again. It will not start again until I remove/replace the battery, at which point it does the one second shutdown again.
At one point I got the phone to boot (no idea what I did differently) and I noticed that it got very hot around the camera area before going black again. A second time I was able to get into recovery, where I did a factory reset. Booted back up and it seemed to be okay, but then heated up very quickly and shut down.
Now, even if the phone is totally cool, I cant get past that 1 second of samsung logo. I'm really at a loss here, and totally screwed without my phone because I am traveling non-stop for the next 2 weeks. Does anyone know how I might try to troubleshoot this? Thanks

Possibly flash a new ROM and start over. That's what I would do

This EXACT situation happened to me yesterday! I was streaming from Google music, it was on the charger and things were fine. A call came in and the phone started vibrating like crazy and wouldn't stop. The screen went black and it kept vibrating. Finally it went off. On boot it will get to my lock screen and then crash after about 30 seconds. If I take the battery out and try again it lasts another few seconds after boot. If I leave it for a LONG time with the battery out and restart it I can get like 2 mins on the next boot without it crashing. The top part by the camera is getting hot on my phone as well. Recovery mode and download mode start fine and the phone doesn't crash. I have some data on the internal that I want to save so I tried to use Odin to flash the most recent build L720VPUFNG2 as that would just install the OS and not touch the data. On the next reboot things seemed to be working fine and I got maybe 5 mins out of the phone before it crashed again. I still don't have enough time to get the data off so I think I'm just going to say screw it and wipe it completely. You guys know of a way I can backup this app data using Odin or recovery mode? My phone is currently unrooted. I'm new to all this tinkering stuff. Phone is out of warranty now anyway.

Threw on a custom recovery, backed up all my data, did a full wipe, now I am good as new.

It worked for awhile but now it is back to rebooting itself. Any idea what could be the issue? I'm assuming at this point it is hardware related. Why can recovery and download mode run consistently without crashing but when an os is fired up it has issues? If it was a hardware issue shouldn't it not work across the board?

So I had Sprint replace my phone on the 8th. I have been using my same batteries (1 stock 1 Anker) and chargers (some stock some not) without issue the past 5 days. I rooted and installed xposed and some modules (original broken phone was never rooted and was completely stock). Things were going great until tonight when it started reboot looping exactly like the old phone. I switched battery and same proble. After I took the battery out and left it out awhile it fired back up but I'm afraid the problem will return. Is it possible that the battery or charger randomly are causing damage to the phone? I only have 14 day warranty on this replacement and need to figure this out.

I have no idea maybe try just using your stock battery for a couple days. See how that goes then use your other battery for a couple days and see what happens.

i7vSa7vi7y said:
I have no idea maybe try just using your stock battery for a couple days. See how that goes then use your other battery for a couple days and see what happens.
Click to expand...
Click to collapse
I think it was one of the xposed modules causing the issue. I realized the rebooting seemed to happen whenever I pressed the power button. I had installed a power menu module so perhaps it was the cause. I restored from a nandroid and uninstalled that module and things seem to be working now. Hopefully that was the cause and this thing won't start acting up again after the return period.

killerz298 said:
I think it was one of the xposed modules causing the issue. I realized the rebooting seemed to happen whenever I pressed the power button. I had installed a power menu module so perhaps it was the cause. I restored from a nandroid and uninstalled that module and things seem to be working now. Hopefully that was the cause and this thing won't start acting up again after the return period.
Click to expand...
Click to collapse
That makes a lot of sense. Have to be careful with those Xposed modules. Don't get too carried away installing so many at one time and playing with them and then rebooting. You'll have a hard time figuring out which one is causing it. I'm pretty sure you found your problem.

i7vSa7vi7y said:
That makes a lot of sense. Have to be careful with those Xposed modules. Don't get too carried away installing so many at one time and playing with them and then rebooting. You'll have a hard time figuring out which one is causing it. I'm pretty sure you found your problem.
Click to expand...
Click to collapse
That is exactly what I did I installed like 6 at once and things were working well for a few hours then disaster stuck. I think I won't play with this phone anymore as I am upgrading anyway and want to sell it in working order.

So things were going well for awhile and then the reboot loops started up again. I did some digging and read that apparently Samsung phones are notorious for sticking power buttons and the symptoms were exactly what I was experiencing. I watched some videos online how to open the phone and clean out the power button but it didn't make a difference. I then read that squeezing the connector for the power button with a pair of pliers sometimes does the trick. Not for me. So finally since I'm not under warranty, have no insurance, and the phone wasn't working anyway, I just ripped the white plastic part of the power button right off. Well, that seemed to do the trick. Phone immediately fired back up without issue and has been going strong. I glued a small thin piece of plastic where the old one used to be and I am back in action. If my little plastic piece solution eventually fails or breaks off I will consider soldering on a new button but so far so good.
If you have tried everything else, and are looking for last resort, try cleaning the power button with some alcohol, and if that fails, rip off that power button! Here is the video that gave me the idea: https://www.youtube.com/watch?v=3Glllc7bEJs and here are some other power button videos: https://www.youtube.com/results?search_query=s4%20power%20button&search_type=&aq=f&oq=

Phone finally booted after 3 day boot loop..

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

When you can't resist. (Hard Bricked?)

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

Nexus 6p - bricked?????

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