OK So this morning I went to check on some bank accounts on my tablet. The screen became unresponsive, and after a few seconds the device rebooted. I went to enter my password and it crashed. It went to what looks like it could have been a stock recovery with an error that said something to the effect of "Error there is no PIT binary".
Steps I have taken to resolve my issue:
1) I contacted Samsung support, and went through their troubleshooting...no dice.
2) Plugged SM T713 into original charger, allowed it to sit 10 mins (it had an 80% charge when this started happening), and held the power button for 30 seconds (this fixed random wonkiness in my previous Nexus 7 (2013)...nothing
3) Googled my issue. I haven't seen anything relevant at this point. Most cases I see with this issue are the result of a bad odin flash. This tablet has not been flashed since I purchased it. I purchased the tablet new so a previous owner did not flash it either.
Additional details:
1) Running on Stock 6.0.1
2) Never rooted (this device...yet)
3) Installed apps all from the play store with the exception of Amazon Underground.
4) Device is currently under warranty, and warranty support has been requested.
My question is, has anyone had this happen without rooting or attempting to flash? Is there a way to resolve this without tripping Knox, or having to wait on a tech to service my device?
Related
Hi, i'm trying to find out what is the problem with my friend her samsung s5 mini, (running android 4.4.2, full stock unrooted).
Almost every day her phone freezes for no reaseon and needs battery to be pulled or it simply random reboots while she sleeps and then her alarm doesn't go off in the morning as the phone is waiting for her pin number after restarting (she says turning of the pin is not an option).
Is there someone who found a solution for this or what might cause the problem? i told her to install an app to auto clear background apps and also suggested to take out micro sd card for testing but the problem remained.
Also factory reset didn't solve the problem
contrinsan said:
Hi, i'm trying to find out what is the problem with my friend her samsung s5 mini, (running android 4.4.2, full stock unrooted).
Almost every day her phone freezes for no reaseon and needs battery to be pulled or it simply random reboots while she sleeps and then her alarm doesn't go off in the morning as the phone is waiting for her pin number after restarting (she says turning of the pin is not an option).
Is there someone who found a solution for this or what might cause the problem? i told her to install an app to auto clear background apps and also suggested to take out micro sd card for testing but the problem remained.
Also factory reset didn't solve the problem
Click to expand...
Click to collapse
This seems to be a common error with the S5 mini. There is a whole thread in the German Android forum about this issue. Also the German Amazon product page for the S5 mini has about 40 users complaining about this problem.
Some users report that the reboots start after some weeks of usage. First it just reboots once per week, then it gets more frequent until it reboots once per day.
Factory resets or firmware updates do not help. Some users sent their phone in for repair but not with huge success.
But not every device is affected by this. So far I did not notice that behavior with my phone (G800F).
I guess it is a hardware issue as not every device is affected and the error gets worse after some time.
The only way to diagnose what's wrong with the device is to check the adb and kernel log (at least the last kernel log before reboot might be available at /proc/last_kmsg). But this would require rooting the device which in turn would void the warranty. It would also be interesting if those reboots also occur with CM 12 (installing this will also void your warranty).
So it seems that sending the device in (without a great chance of repair) is the only option that Samsung gives you without loosing warranty.
Alternatively you also might want to wait for the official Lollipop release and hope that this will fix the problem.
If someone with this problem already rooted his device it would be interesting to get the log files (adb + kernel) of the times of the crashes.
Thanks for your reply, so it might be a hardware problem after all
Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!
Hi!!
My tab is upgraded to 5.6. from last week. m facing many problems.
1) When i want to put it shutdown. it just shows shutdown dialogue but it wont shutdown itself.
2) the backside of charging point is heating up.
3) the tab is hanging alot.
i went to a shop. showed him my tab. as he was a hardware person. he said there is nothing issue with the tab.
i already did factory reset from recovery.
but m still wondering what to do with this stupid thing.
can i downgrade???? so i can use other roms
liboct87 said:
Hi!!
My tab is upgraded to 5.6. from last week. m facing many problems.
1) When i want to put it shutdown. it just shows shutdown dialogue but it wont shutdown itself.
2) the backside of charging point is heating up.
3) the tab is hanging alot.
i went to a shop. showed him my tab. as he was a hardware person. he said there is nothing issue with the tab.
i already did factory reset from recovery.
but m still wondering what to do with this stupid thing.
can i downgrade???? so i can use other roms
Click to expand...
Click to collapse
- likely something went wrong during 5.4->5.6 update that is now driving high CPU use (heat) and hangs as device is busy doing 'something' that will never complete; seen this many times before with major FireOS updates
- usually can not be fixed via a factory reset (no access to system partition)
- current unknown if FireOS 5.6 can be safely rolled back to 5.4.x (likely not)
- neither FireOS build can be rooted - hence no custom ROMs
Try contacting Amazon for resolution. They might toss you a coupon which can be applied to a new device - including deeply discounted Fires through November 27th 2017 (Black Friday specials).
My OnePlus 3T gave up the ghost 2 weeks ago. I was running stock everything, unrooted.
One night I had just finished up a Pokemon GO trading session and went to plug in my phone (it was below 10%). I then noticed that the screen was frozen so I rebooted the phone, and then I got stuck in a boot loop.
(In hindsight, I was having connectivity issues with my network carrier (ATT) earlier in the day where I would randomly lose the signal, exclusive to this device)
I did the first sensible thing, I did a factory reset of the phone. During the setup process I can make it through several pages of the setup before the device freezes and shuts down. I then went through the fiasco that is OnePlus customer support. I did a live session this morning where the current ROM was flashed and I still get nothing. Their response is send it in for repair, which I'm guessing will cost more than the phone is worth.
I should note that the Fastboot and Recovery menus function fine. I have not rooted the device.
If anyone has thoughts on whether this is truly a hardware problem, I would appreciate them.
Hi,
A few days ago, I replaced a USB socket on friend's old Samsung Note 1 (GT-N7000). Soldering may not be very professional, but it does the job - the phone is charging and it can connect to the computer.
Today (3 days after replacing the USB) he came back to me with another problem -
after turning on the phone, only the white brand name and model appear at the start and then nothing, a black screen. I think it's turning off. He says he had some problems with the battery in the meantime and the screen was flickering strangely.
He had a custom ROM loaded for a long time that worked normally and worked well on this phone.
Today, despite not starting the system, I was able to enter TWRP recovery and DL mode. However, if I wanted to do anything in recovery (backup, factory reset, etc), the screen turned off. After a few attempts, it stopped going into recovery.
I have restored the original software using Odin and N7000XXLSZ_OXELS7_4.1.2_Repair_Firmware
- still after the white inscriptions at the start, the screen goes black and nothing
- trying to enter recovery, overturned android appears for a moment and the screen goes black
- DL mode works
Maybe someone knows what could have happened and most importantly how to get this phone work? Preferably on some "custom ROM" to have at least Android 7.
I was thinking, I was looking, I was tearing my hair out of my head. I searched half the internet and suddenly stumbled upon this - https://forum.xda-developers.com/t/...bricked-only-download-mode-available.3096409/
The phone is the same, the problem is the same - the battery is to blame. I immediately called the owner to give all the batteries he has.
OH, OF COURSE! The one I got along with the phone and its problems was the only one that caused all the restarts and errors. After inserting a different battery, the problems were resolved.
All that's left is to clean up Android and the case is closed.
By the way - I have collected in one place the files and information (Polish language only) on how to install NightOwl LineageOS 14.1 Android 7.1.
2 on this phone. If anyone needs this information, please visit here - https://drive.google.com/drive/folders/1libYpWC4qJbjGJRE1Szf8L3eTdoHPTpE?usp=sharing