Hi All,
I've recently updated my Desire S to CM10.1 using a ROM off here --> [ROM][XXYYYZZ][UNOFFICIAL] CyanogenMod 10.1.
Everything has been running fine until I found the "Simulate Secondary Displays" button under Developer Options and decided it would be cool to see what it does...
The kicker:
a) Screen is now stuck exactly where it was on the Developer Options prior to selecting a screen resolution
b) Holding down power button for any period of time does nothing
c) Holding down Volume up + Volume down + Power for any period of time does nothing
d) The computer recognizes the phone as it makes it's lovely "new device found" sound, but stupidly, at some point I've disabled USB debugging so can't use adb to reboot as it returns authorisation error (The authorisation option doesn't pop-up on device screen as it's frozen).
I've read about this exact problem happening on other phones after selecting this option but they all seem to be able to use either b) or c) to get back to bootloader to reflash the ROM.
So, my question: if I let the battery die, what are my chances? I've read myself out of pulling the battery due to eMMC issues. Unfortunately the damn battery was mostly full so could take a long while to drain :S
Thanks!
So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.
Pulling the battery out doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.
SimonTS said:
Pulling the battery ut doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.
Click to expand...
Click to collapse
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.
Click to expand...
Click to collapse
Apologies, it wasn't a particularly open question. It was more out of frustration that there is an option available that will always freeze the phone when it isn't supported on the device.
I let it die then used recovery to clear cache and davlik cache and booted fine until freezing on the "Optimising apps" screen. Let it die again, clear all data, clear cache, clear davlik cache, restore nand successfully.... Boots to HTC then black screen, no response to anything, same as when it first froze.
EDIT:
Repeat same process but clear cache and davlik cache after nand restore... black screen, no response. Cant even tell if it is actually doing anything. Charge light doesnt come on when plugged into pc whilst on black screen.
All I can think of now is flash the CM10.1 ROM again or maybe restoring the original nand from before CM10 but will have to be after work. Is this behavior indicative of a larger (potentially physical) problem?!
PoZER937 said:
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
Click to expand...
Click to collapse
From what I remember - there was some in-depth discussion on one of our threads about 18 months ago - the actual cause is that re-inserting the battery while the circuitry is discharging causes a spike which can be high enough to blow the eMMC.
Just to let you know, reflashed CM10.1 ROM and all is well in the world again Thanks guys for replying!
However, NAND restore did not work. As the NAND backup is supposed to be the be-all and end-all for phone recovery, should I be concerned this failed?
Related
Had my G tablet for a month now and I've rooted it a couple of times (to tnt lite,) but I've since resorted to the latest update from the mfg. Its fast enough and I can get most of the aps I'm intersted in with the stock cfg.
Problem is, it occasionally hangs, usually in the middle of a web surfing session. The hang is complete, meaning I can't even shut down. the only remedy I've found is to set the tablet aside and wait till the battery runs down. Then I charge it, boot up, and everything's back to normal again.
Has anyone else seen this happen and is there a way to prevent/cure it?
thanks.
Rich
First off you say you rooted a couple of TIMES? Do you mean flashed a couple of times? Regardless if it locks up again then hold the power button till it powers off. Then you should be able to reboot.
thanks, but...
when I say its locked up I mean locked up. The on/off button is inoperative. I've held it for varying lengths of time, up to 15 seconds and nothing happens.
When I said that I had rooted it several times I mean that I've taken it from stock to tnt lite twice. Its now unrooted and stock again and working fine. (till the next time it locks up, that is-)
but thanks for replying
rich
zookarama said:
when I say its locked up I mean locked up. The on/off button is inoperative. I've held it for varying lengths of time, up to 15 seconds and nothing happens.
When I said that I had rooted it several times I mean that I've taken it from stock to tnt lite twice. Its now unrooted and stock again and working fine. (till the next time it locks up, that is-)
but thanks for replying
rich
Click to expand...
Click to collapse
Try doing a factory reset as well as wiping the internal memory. There are several ways to do this, but only one way on stock. I won't ask you to go back to using Clockword Mod if you no longer have it on there so I'll go through the stock way first, and then the CWM way in case you have it installed.
Prep: Copy out anything you figure you need from there. I don't recommend backing up because if you back up a corrupt or faulty app then you're going to restore it and your problems with it.
So copy your stuff off that you don't have otherwise, maybe downloaded wallpapers or whatever. Best method is just to copy them right to your PC I'd say. Do this from both internal storage and the SD if you have that installed as I recommend you wipe that as well.
Stock:
Go into settings to security and do a factory reset. After the factory reset, don't bother setting up, go back into the settings and to storage and wipe the SD card if you have one installed. You'll have to unmount it first I think. After that, wipe your internal user storage. This is going to 1. reset the tablet's OS and system software/settings to factory defaults and 2. remove any gunk that may have gotten on there and is messing things up. Since Apps generally don't overwrite their settings on purpose, I recommend wiping them and putting them back over clearing data/clearing cache for each app. You start over with more or less a clean slate this way.
Clockwork Mod:
Go into CWM and wipe your data as well as the cache. Wipe Dalvik as well, for good measure. When the tablet starts back up, go to storage and wipe the SD as well as the internal storage, again, just for good measure.
Once you're all done, power the tablet off and then on again and do your thing.
If the tablet STILL messes up after a few days then it could mean that there's some hardware at fault. My tablet has never frozen like that before to the extreme where I'd have to sit and wait for it to die...and afaik that's def. not something that should occur often. I have seen other members report it, but they've usually done some 'heavy' tweaking like repartitioned their internal storage and other things like that.
People may recommend that you re-partition, etc. but I'd just try to exchange it and try my luck at another unit before getting into all of that UNLESS you have indeed partitioned or altered the internal storage manually before this started happening - in which case you may have it partitioned incorrectly and should def. try getting it back to the default using CWM, HOWEVER, if you did not do this and all you really did was install TnT lite then I'd do the exchange.
Good Luck.
thanks
Your advice and your instructions on how to address this problem are VERY helpful. Thanks.
rich
Hi
I can't seem to find an answer to this anywhere.
I'm having an issue with the youtube app, it won't launch after it has been updated, so I hope that a cold boot can fix this, however I can't do it with the usual trick.
When I hold the volume down + power button, I get a menu where I can choose the following:
Enter SD Down mode
Factory reset
Exit update mode
Does anyone know how to perform a cold boot on the LTE version of the Infinity?
A "cold boot" on all devices works exactly the same: Turn it off (not only standby), turn it on. Anything more is either voodoo or includes modifying storage content.
Okay, I thought a cold boot was real
Can you help me with my youtube issue then?
When I open youtube, I get the messge "The application Youtube has stopped". The only way I can open it, is if I remove the application update, but I would really like to use the newest version.
A cold boot is very real.
We have a [How-To] All-In-One Guide For Asus Infinity (TF700) in which all these things are discussed. Right here: http://forum.xda-developers.com/showthread.php?t=1833212
It very clearly says:
Note: Make sure your device is OFF before using this.
** Cold Boot - FastBoot - Wipe Data Menu **
Press Volume Down + Power untill you see a white text on the screen then release the buttons. Use Volume Down to navigate and Volume Up to confirm your selection.You have 10 seconds to make your choise, or else the system will do a Cold Boot by default.
So don't press anything when the white text appears and it will cold boot.
_that said:
A "cold boot" on all devices works exactly the same: Turn it off (not only standby), turn it on. Anything more is either voodoo or includes modifying storage content.
Click to expand...
Click to collapse
Please don't answer if you have no idea what you're talking about. A cold boot clears the cache, a regular boot does not.
No, as I said in my first post, this way doesn't work on the LTE model.
I'm open to all ideas, but I have also tried it with the volume up button, which just tells me that no USB cable is plugged in.
ShadowLea said:
Please don't answer if you have no idea what you're talking about. A cold boot clears the cache, a regular boot does not.
Click to expand...
Click to collapse
Where is this cache located that is cleared with this procedure?
http://forum.xda-developers.com/showpost.php?p=32365090&postcount=13
Not sure if the above link is relevant to the YouTube crash bug.
I remember reading on one of the Android forums about a fix by setting YouTube to the english language or something like this.
---------- Post added at 11:26 AM ---------- Previous post was at 11:22 AM ----------
_that said:
Where is this cache located that is cleared with this procedure?
Click to expand...
Click to collapse
App caches are available under: settings\apps\downloaded\clear cache, uninstall updates, disable (if available)
Thats OK said:
App caches are available under: settings\apps\downloaded\clear cache, uninstall updates, disable (if available)
Click to expand...
Click to collapse
Yes, but app caches have nothing to do with cold boot. Cold boot is power on, executing the bootloader and starting an OS, that's the definition of cold boot since 50 years for any computer.
And I argue that the procedure with holding Volume- and waiting does *exactly* the same as a normal power-on. To everyone who claims it does more: please provide a reproducible way to prove any differences. Otherwise it's voodoo.
@ Thats OK - Thank you very much. Changing the Android language to English, has fixed the youtube app.
_that said:
Yes, but app caches have nothing to do with cold boot. Cold boot is power on, executing the bootloader and starting an OS, that's the definition of cold boot since 50 years for any computer.
And I argue that the procedure with holding Volume- and waiting does *exactly* the same as a normal power-on. To everyone who claims it does more: please provide a reproducible way to prove any differences. Otherwise it's voodoo.
Click to expand...
Click to collapse
I remembered a while ago I did ask Asus tech support about "cold boot" vs normal power cycle and he said: A cold boot is different from a normal power cycle (hit the power button to turn off and on). With normal power off/on, it will not clear various caches in ram, kind of like you restart a computer from a restart button, versus you unplug the power cord then plug it back in. a cold boot it performs a "clean" boot. He provided example like video display, if you experiencing flickering or color fade or color spot on the screen a normal boot will not address the issue but a cold boot will. I did ask him about what are "various caches" and being told that they are hard ware cache like graphic, preloaded ram space etc..(too much technical at this point). And yes you're right he said it has nothing to do with application cache or data. Again a normal boot is NOT same as cold boot. He said the right way to do a cold boot (he refered a cold boot as hard reset, they are the same under Asus technical term), you must unplug your device, then power down, then do the button combinations, navigate to the Android icon then execute it. A cold boot does resolved issue like FC, weird screen issue, stutter, lag etc...(it will not resolved issue if software bug, or hardware issue). The last thing he said is hitting reset with the pin hole is same as cold boot (clear various caches).
buhohitr said:
I did ask him about what are "various caches" and being told that they are hard ware cache like graphic, preloaded ram space etc..(too much technical at this point).
Click to expand...
Click to collapse
Voodoo spread by Asus support to keep the customer busy.
All those "various caches" are made of RAM. So they lose their content when the power is turned off, and are initialized when the system is booted. When the bootloader screen appears, these caches are already as clean as possible.
Let's try to find some evidence. The Tegra 3 TRM says:
* Frozen boot: The RTC partition power transitions from OFF to ON
* Cold boot: The main partition power transitions from OFF to ON with no previous state available, SW must construct all state from scratch. Boot ROM is executed. DRAM is brought on-line.
* Warm boot: The main partition power transitions from OFF to ON with previous state available, SW checks for the preserved state integrity and restores the saved state from DRAM, which was in self-refresh prior to warm-boot. This is also called Deep Sleep wake-up or LP0 exit.
Click to expand...
Click to collapse
As you can see, "cold boot" is the only one that involves the boot ROM (which starts the bootloader) - or vice versa: any reboot that involves the bootloader screen is a cold boot.
buhohitr said:
A cold boot does resolved issue like FC, weird screen issue, stutter, lag etc...(it will not resolved issue if software bug, or hardware issue).
Click to expand...
Click to collapse
No doubt on that. Running programs can have an impact on each other and on the system performance. But as long as nobody provides a plausible explanation what exactly that magical button fiddling in the bootloader would really do differently, I don't believe it makes a difference *how* you reboot.
LiquidoDK said:
@ Thats OK - Thank you very much. Changing the Android language to English, has fixed the youtube app.
Click to expand...
Click to collapse
No problem my friend!
So glad to be of some small help.
Enjoy YouTubing!
jim
_that said:
Voodoo spread by Asus support to keep the customer busy.
All those "various caches" are made of RAM. So they lose their content when the power is turned off, and are initialized when the system is booted. When the bootloader screen appears, these caches are already as clean as possible.
Let's try to find some evidence. The Tegra 3 TRM says:
As you can see, "cold boot" is the only one that involves the boot ROM (which starts the bootloader) - or vice versa: any reboot that involves the bootloader screen is a cold boot.
No doubt on that. Running programs can have an impact on each other and on the system performance. But as long as nobody provides a plausible explanation what exactly that magical button fiddling in the bootloader would really do differently, I don't believe it makes a difference *how* you reboot.
Click to expand...
Click to collapse
I don't think that Asus developers just waisting time to put the extra icon in there just for fun. So it's just common sense that on our PC, we could unplug the power cable or hit the switch on the power supply to get cold boot. However on the infinity, there is a non removable battery build in so you can't removed or unplugged it. In short, a cold boot is like take out the battery of the infinity..make sense!!
buhohitr said:
I don't think that Asus developers just waisting time to put the extra icon in there just for fun. So it's just common sense that on our PC, we could unplug the power cable or hit the switch on the power supply to get cold boot. However on the infinity, there is a non removable battery build in so you can't removed or unplugged it. In short, a cold boot is like take out the battery of the infinity..make sense!!
Click to expand...
Click to collapse
This is a nice theory, and it would really make sense, but if you do this "cold boot" procedure, the power stays on, as you can verify for yourself. And also on the PC there is no difference between booting from soft power off (power button) or hard power off (switch on power supply).
The whole thing is more like if you press F8 on the PC - you get a boot menu, but then you can still select to start Windows normally.
Is it not possible that the cold boot icon in the bootloader menu actually clears the cache partition (which doesn't get cleared on a normal power on/off cycle)?
I would have to believe that the cold boot does do something different than simply powering off and on - why else would they include it?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Is it not possible that the cold boot icon in the bootloader menu actually clears the cache partition (which doesn't get cleared on a normal power on/off cycle)?
Click to expand...
Click to collapse
I tried it - it doesn't. And it would not have any major effect, because the cache partition is only used for communication between Android and the recovery.
jtrosky said:
I would have to believe that the cold boot does do something different than simply powering off and on - why else would they include it?
Click to expand...
Click to collapse
Maybe just to start Android normally if you changed your mind? Just like the "Start Windows normally" option in the Windows bootloader if you pressed F8.
My tablet froze on me and I powered it down to restart it and then it went into what folks on here call a bootloop. After holding down Power and volume down, it brought me to a screen that had three icons and I chose the one on the right by mistake and now it's looping again, but instead of the Asus screen with the refreshing icon, it's the android falling with an Error on his chest after quickly flashing Installing System Update.
The power volume combo works no more and the only way I can shut off my tablet completely is to use the power and volume up button. I can't get back to screen with the three icons no matter how many times I try.
I've already resolved myself to purchasing a new device, so my main concern is recovering the data, slim as that might be. Any recommendations?
Also, note that Ive never rooted or installed anything on my tablet. No roms or kernels or any other modifications. If I can get my data by any means necessary, I'd be satisfied, even If I Ihad to open it and retrieve the harddrive.
Hopefully Ive explained myself sufficently for you guys to help me. Cheers.
Meth_Badger said:
My tablet froze on me and I powered it down to restart it and then it went into what folks on here call a bootloop. After holding down Power and volume down, it brought me to a screen that had three icons and I chose the one on the right by mistake and now it's looping again, but instead of the Asus screen with the refreshing icon, it's the android falling with an Error on his chest after quickly flashing Installing System Update.
The power volume combo works no more and the only way I can shut off my tablet completely is to use the power and volume up button. I can't get back to screen with the three icons no matter how many times I try.
I've already resolved myself to purchasing a new device, so my main concern is recovering the data, slim as that might be. Any recommendations?
Also, note that Ive never rooted or installed anything on my tablet. No roms or kernels or any other modifications. If I can get my data by any means necessary, I'd be satisfied, even If I Ihad to open it and retrieve the harddrive.
Hopefully Ive explained myself sufficently for you guys to help me. Cheers.
Click to expand...
Click to collapse
If I read your post correctly, you selected the right icon which is a Wipe data from your bootloader. When you executed that Wipe data, it will wipe everything on your internal SD including your /media folder or your personal files and data... The chance is very slim unless someone knows how to recover data from a wipe. Technically, your data is still there but it is only a dumb files which contain only 0's and 1's. Some recovery tools may be able to retrieve your data but I don't have that knowledge.. I hope that someone will be able to help you out and good luck...:fingers-crossed:
I'm afraid LMK is right: Your data is gone.
Do I suspect correctly that you interrupted the Wipe Data process after selecting it "accidentally"?
Choosign Wipe Data from the bootloader causes the BL to write a command to the misc partition to start the recovery and wipe the data partition. If you interrupted the process, there's no telling what and where that got corrupted - unless you just let it loop and pray that it finishes the wipe process which would erase the BL command. Connect it to power and let it loop for a few hours. What have you got to loose?
But your data is gone either way - sorry.
Morning, cheeky question(s)
Where are you located, and would you be interested in selling your bricked TF700? I have a broken screen among other things and would be interested in buying your tablet for spares if you are getting a new one?
PM me if you are interested.
Thank you
Freddie
I'm not all too sure what the Icon on the left wad, but I'm sure it said RKU or some sort. I would have given up all hope if I had hit the wipe data on the right.
Days recovery aside, is there anyway I can get my looped tablet to work? I plugged it into a comp and it didn't recognise it.
Hi,
I also posted this in the Moto G forum, possible by mistake. If the Mods. could decide which location is better, and delete the unnecessary post, it would be great....
Wondering if anyone can help.
I have a Moto G3 8Gb model. Everything is stock. Not rooted, unlocked. The phone is 4 Months old.
The problem I am having is the battery symbol always displays the "Lightening Flash" for charging, even when the phone is not plugged into the charger. I have tried clearing the cache, but that didn't work. I am not sure if this "bug" is only an indication issue, or if the phone will actually think it is in charging mode and that will have knock-on effects to the phone itself. I am tempted to do a Factory Reset to see if that cures the problem, but maybe someone has a fix......
Thanks for your help.
Does it also show 'charging' in the settings>battery page? Or only statusbar?
Edit:- Sorry no idea.
Broadcasted from Zeta Reticuli
No, on Settings>Battery it shows XX% - approx. YY hrs left.
First, do a hard reboot... With the phone operating, press and hold power for 10+ seconds until it reboots. Test
Second, boot in safe mode and see if it persists. Hold the power button a different when prompted to Shutdown, long press the button and select Reboot to Safe Mode. If the trouble is gone after reboot, it's an app you have installed that causing the issue
Third, clear cache... https://motorola-global-portal.cust...ail/a_id/105527/p/30,6720,9390/kw/clear cache
Lastly, do a full factory reset to wipe all information (delete Google account first).
If it still persists it's a hardware issue and there is nothing you can do but send it in for repair.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
First, do a hard reboot... With the phone operating, press and hold power for 10+ seconds until it reboots. Test
Second, boot in safe mode and see if it persists. Hold the power button a different when prompted to Shutdown, long press the button and select Reboot to Safe Mode. If the trouble is gone after reboot, it's an app you have installed that causing the issue
Third, clear cache... https://motorola-global-portal.cust...ail/a_id/105527/p/30,6720,9390/kw/clear cache
Lastly, do a full factory reset to wipe all information (delete Google account first).
If it still persists it's a hardware issue and there is nothing you can do but send it in for repair.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Did hard reboot, and factory restore. Problem still there. Contacted my mobile operator. They are sending phone for repair (phone still under warranty). Hopefully that's the end of the saga. Mind you, it seems very easy to replace the charging port. There is an access panel at the bottom of the phone - 3 screws, and out pops the charging port. Anyone any experience replacing the port?
The problem I have is with the galaxy z flip 3, it worked just fine inthe morning but after it ran outta juice and I charged it to a certain percentage, it stopped working properly, and got into an infinite boot loop, I tried forcing it to restart by long pressing volume down+power , but it didn't work, then I tried opening the recovery by long pressing on volume up+power and yet it also didn't work (I think that maybe it's because it was trying to boot at the time), so have you guys any solutions , please do help me cuz this phone really is important and with all honestly, isn't even mine XD, I'll be waiting for an answer
Your failsafe options are contact Samsung or do a factory reset (and then potentially contact Samsung).
If you can't boot it to anything, the only real option you have is to flash firmware, which likely won't help without wiping.
Unfortunately, not booting doesn't have a whole lot of options that don't wipe data without being rooted. Even then, you'd need recovery.
I see, then I may consider giving it to samsung, as long as they won't reset it, cuz the only reason why the phone is so important is because of the data, altough, isn't there any other way to acess recovery? Cuz I had this problem with the s10 before and I fixed it somehow (a certain Bixby key combination), but this time it seems there isn't any hidden combination.
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
twistedumbrella said:
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
Click to expand...
Click to collapse
Well I just asked the original owner (my mother), and apparently she doesn't remember downloading anything new into it, and it just went crazy by itself, also something else I wanna note, I tried charging it and it booted into recovery all by itself, I taught it was weird but Still went and wiped the cache and then when I tried restarting it it suddenly ran out of juice once again, also, it's second display shows some weird curruption/bug or glitch-like lines. So based off of this, can you really find the origin of this problem and if there is really any hope of saving it's data XD. Thank you btw, and once again, I'll be waiting for an answer
There are hundreds of reasons it could do that, including a faulty board. Thanks to the removal of physical sdcard support, you'd need to get it to boot into something with at least adb support to pull anything off it. Stock recovery doesn't provide any ways to perform a decent backup, but it sounds like the only option that wouldn't wipe the device didn't work.
I see, alright, thanks a lot, I'll consider resetting it
It may be worth trying to flash firmware first. Go into it knowing it may reset the device or leave you needing to reset it, but it doesn't hurt to try if you run out of safer options.
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
ariveraiv said:
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
Click to expand...
Click to collapse
Hello everyone just a quick update. Once I got home I plugged the device into a Samsung fast charger and Samsung OEM USB type-c cable and realize the device booted all the way to the home screen but register the same battery level as I mentioned above. Device was working as if nothing happened to it. So I updated all the apps on the Galaxy store then updated all the apps left over from the Google Play store, I then proceeded to check for a firmware update because I know the April update just released and installed the update with no issues. Updated the apps that needed to be updated again somehow there's always something and unplug the device from the power cable. Everything was working if no issues about half hour later the device cuts off and does not want to power on. FYI I already had my wife contact T-Mobile and get a warranty replacement we only paid $5.00 so my thoughts and conclusion on what's going on something happened to the battery or it's defective. Btw we only use Samsung OEM cables and equipment at home and in the car while connected through Android auto. it's only working while being plugged in it's not charging all the way even though it's registering it's charge level while the device is on.