Database Info

[Q] Droid phone crashed and won't reboot/can't navigate the root menu

I suspect it's a software problem and not related to the hardware models. We have htc inspires though.
Wife and I have identical phones. She came home from work and told me hers crashed; she said she charged it on her way in to work and when she reached to use it saw the root/boot/recovery/whatever screen. (She described it and then when it came up when I looked at it, confirmed that was the screen she'd seen.)
We've got android 2.2.1, if that helps.
Anyway, the phone crashed and won't restart. I pulled the battery out, waited, and popped it back in, and nothing happened. Pulled it out, waited, popped it in, tried the method described here *edit: apparently too new to post links. it was at the htc community.* of trying to bring up the recovery menu. Looks like we have fastboot enabled, which a mod describes as being a known thing. I do the keystroke method as described here, and it brings the menu with the 4 options - reboot, recover, factory reset, and something else, but it doesn't let me navigate with the volume key the way the site and the bootscreen on the phone tell me I should be able to.
So - what went wrong, how can I fix it? I'd rather not have to schlep out to an AT&T store if I don't have to, especially if we can figure it out here. I'd rather not have to do a factory reset, as probably nothing is backed up or saved to the sim, but at this point, I'm worried that's not even an option I can select.
Cliffs:
1. Android phone crashed and won't reboot.
2. Can't make selections in the boot menu using the volume key as I'm supposed to
3. Phone runs through fastboot and fails to start up - I tried the thing I'm supposed to do in response to that as described here *edit: apparently too new to post links. it was at the htc community.*
4. This should be an easy fix / probably something someone here has encountered before.
edit: Don't know if this means anything diagnostically, but while the phone should be fully charged right now, it reads as at 0% when I plugged it in. I figured the utility that measures that probably isn't available at this level in the start-up?
edit2: She mentioned just now that it looked normal when she got up for work. Was at work and tried to use it but it was in airplane mode and she hadn't put in airplane mode herself. She clicked the airplane mode icon to switch out of it and the icon animation just sort of hung. She put it back on her belt like that, it sounds like. When she picked it up again it was in that root menu.
We're not rooted, and these should be vanilla installations.

If this is the wrong place to ask about this, can someone direct me to the right section? I wasn't quite sure where to post this. I reviewed the instructions and did a quick search... but my search-fu might suck.

[Q] CM 7 Boot loop/Blank screen

Hi All,
Disclaimer: I have scoured the internet and this forum looking for others who found solutions to my problem, and I've found several similar cases, but none quite like mine. I've done all I can think of short of sacrificing lambs on giant LG logos painted on the ground, so I'm resorting to posting. Forgive me if I missed something obvious - it's entirely possible since I'm still a newbie...
With that said, here's my issue:
I downloaded a CM7 nightly build and successfully flashed it on my p999 this morning using ROM manager. I went back to stock 2.2.2 afterward. Earlier this evening, I decided to flash CM7 again from the ClockWork recovery mode, but this time I didn't do a wipe (yes, I realize I'm a massive idiot). After rebooting, I got stuck in the standard boot loop with the cyan android alien doing its skateboard thing. I tried booting to recovery mode, but holding down power+down volume just brought up the android alien and the white box with a loading bar for a short time before rebooting. Standard suggestions involved (reasonably so) performing a hard reset. Though the phone won't boot straight into recovery mode, pressing the home button while the loading bar is visible brings up text suggesting the data, cache, etc of the phone are being formatted. After this process completes, I'm left at the system recovery utility with blue text and I can navigate the first menu, but the power button (nor any of the others for that matter) doesn't actually select any of the options. After removing the battery to reboot the phone, it still gets stuck in the boot loop and occasionally goes blank after failing to get to the launcher a few times.
I've also tried using the adb approach, but no device is detected on the linux machine despite being able to access some form of the bootloader.
Have I legitimately bricked my phone, or is there still something I haven't tried? Thanks a million for any help.

You didn't search very long did you? Go to the development section and find the thread on the one click nvflash tool, read the OP in that thread and you should be good to go.
G2X CM7

unusualparadigm said:
Disclaimer: I have scoured the internet and this forum looking for others who found solutions to my problem, and I've found several similar cases, but none quite like mine.
Click to expand...
Click to collapse
This forum is saturated with problems and cases exactly like yours, almost word for word.
G2X CM7

I found plenty involving a boot loop with CM7, but all of them were able to get to recovery mode just fine. Despite what you might think, I spent several hours trying to find something that worked. Thanks for the help. I'll see if nvflash helps.

They were able to get into recovery mode because they flashed it correctly using nvflash. Pardon my tone. I guess it sounds rude. Its been a long day and I'm tired. Anyway, nvflash recovery and you'll have no issues getting stuck like this.
G2X CM7

No problem. =) When trying to go the adb route, I saw the volume up+down trick to get the device to be detected, but it wasn't working on the linux or mac (lion - it's been having issues detects various external devices anyway) machines that I was using. After checking out the nvflash thread, it seems maybe a windows machine is necessary. Getting bootcamp going. Here's to hoping it'll work. Thanks a ton again for the suggestion - this is exactly what I was looking for (wanted a way to get CWM on the phone).

Make sure to check out this thread if you haven't already. Its a one click tool for nvflash.
http://forum.xda-developers.com/showthread.php?t=1056847
G2X CM7

Yay!
Thanks a ton! In retrospect, it seems my problem was right along the lines of multiple others', but I just didn't realize it since a few details on the specifics here and there seemed different. Sorry for wasting the board space, but thanks for your patience and help. I can't emphasize how much I appreciate it.

[Q] Can't Access HBoot, Random Startup

Hello,
I am posting in this forum for a few reasons.
First of all, I rooted my phone the day I bought it and took it home. I originally rooted it with a simple one-click method from a webpage I randomly found online.
Unfortunately, I do not remember the name of the hack, and I'm beginning to think that it has permanently affected the boot for my phone. After installing the hack, I found the CynoagenMod (or however it is spelled) custom ROM. I took some time into researching more about custom ROMs and installing with advanced settings, etc.
After I did my research, I found it best to flash with the new ROM and have had trouble with my boot since.
I did everything step by step from the website, and ran everything to the best of my abilities. The problem I am having now is that I can not access the HBoot menu.
In fact, every time I restart or shut off my phone, the screen goes black and will not respond to me holding down the recovery mode buttons. It stays pitch black and even battery resetting does nothing.
It will randomly turn on, vibrating for about a minute or two straight with the HTC splash screen, and then boot into my phone with the current ROM.
It seems strange that this is going on, and I have been searching all over the internet for weeks now trying to figure out what's wrong. I have reinstalled the stock RUU for my Inspire multiple times to no avail. It still sits at a black screen and will randomly boot into the splash whenever it deems to do so.
Is there anyone with any suggestions or advanced technical knowledge that could lead me to a solution? It is most unfortunate because I can't access for viewing s-on, s-off. I'm really debating whether to take the phone back to the rep and replace it. I'm just afraid they will discover the security off and tell me to suck a ****.
Thanks.

Run this nice little tool to factory reset, s-on your device
http://forum.xda-developers.com/showthread.php?t=1208507
Then reroot with the Hack Kit here. Read the "effen manual"
http://forum.xda-developers.com/showthread.php?t=952352

Thanks for the reply.
But here's my problem:
I can't access the HBoot menu in order to flash or install any type of file.
I've been using the terminal on my Mac to do most of my editing, and now I've ran in to a new problem: whenever I try to move files to my sd root, it says that the card is read only and therefore no files can be transferred to it.
I use the command ./adb push PD98IMG.zip /sdcard/
This is where I get the error.
Also, it takes my phone literally 5 or 6 minutes to boot into the splash screen after I use the command ./adb reboot bootloader/recovery (both of which I have tried).
I'm beginning to get quite frustrated, as I'm sure you can understand. I've also attempted to rewrite all of the necessary root programs onto the device in hope that the bootloader and recovery options will be accessible.
Do you have a solution for the write problem I am getting from my device?
Thanks.

Also, is there a way to go about doing this procedure straight from the Terminal since I can't run HBoot and recovery directly from my phone?

I have sucessfully restored s-on on my previous inspire so I can rma it for a signal issue I was having.
So I consider myself savy enough on this task. I rooted that inspire using a method available on here and not some random site. Doing that, u accept the possiblility that you may not get support on xda for using a root method that was not posted here. However, I do remember reading somewhere on here that certain inspires will go to a black screen at somewhere during the rooting process. My advice is to search the inspire threads for this topic, using keywords black screen, and see if this can provide a solution for you.
Sent from my HTC Inspire 4G using XDA App

Thanks soldier, but I've already searched through every black screen forum topic on this site for the inspire, all of which require reboot to HBoot, which I can not access from my phone without terminal access.
It seems like my phone is permanently soft bricked or something, or maybe the key commands don't do as they are supposed to. I can never get into the HBoot menu or recovery by holding down vol. - and the power button.
All it does is boots into the splash screen after about five minutes or son, and once the splash screen comes up, the phone vibrates for about 2 minutes straight.
During this time, my phone is not recognized by adp until after the phone stops vibrating.
I can't seem to find any forums ANYWHERE that propose a solution to this problem, let alone anyone that has the same issue as me.

Yeah that sux man. Well I would say, if you are within your warranty exchange, I would go that route first. Worst thing they can say is no. Although I still have yet to find a story about how someone was denied a warranty exchange for a phone that does not have physical damage. The next route is to suck it up and pay the deductible if you have insurance on it. (I always recommend insurance on any modern touchscreen smartphone) If that is not an option, then start saving up for a new phone, and lesson learned.

Ya, that seems like the only available option at the moment since my phone can't access HBoot even though I rewrote the root files to the device.
I just bought the phone this weekend, so I'm thinking of hard bricking the phone in case they decide to do an on-the-spot check. Hopefully they'll believe some bull**** story I can come up with and just give me a replacement.
Would any of you still recommend rooting again with a new phone? And what would be the best way to do so without the consequence of a soft or hard brick?
I'm just thinking of rooting and keeping the original stock OS on the device instead of running a custom ROM. That's what seems to have effed my phone.
All I really wanted to do was cut all the crappy useless programs and services out of the original Google Apps package with a fresh install to get the most out of my hardware.

FYI...if you haven't figured it by now, xda is the BEST site there is for android hacking/modding. This website IS the centralized location for all android developers/modders. Sure there are plenty of other android community sites out there, but this is the direct centralized source for all android hacking/modding.
My suggestion is to go ahead and root the next inspire you get using the hack kit in the development section. That is a long time proven and supported rooting method for the inspire. As far as roms go, from what you are saying, i would recommend you install a custom rom that is based on stock. (ex. Android Revolution) It was not the custom rom that effed up your phone, it was the questionable rooting method that did. Custom roms, by default, are superior to true stock roms, because they are modded, tweaked, and optimized far beyond the stock rom.

Awesome, I appreciate the information.
I'll keep that in mind. So which exact ROM would you suggest for my Inspire that's completely like Gingerbread?
I wasn't too fond of the CyanogenMod ROM because the GUI was a little sketchy. I like having a professional looking GUI, and I love the Gingerbread screens and menus.
Oh, one more thing. I had some success a little while ago getting into the HBoot menu from the terminal. Now I'm having a new issue:
I get into the menu at which the phone freezes and I can not use the arrow keys or power button to make a selection. Any tips?
I also believe that it is in fastboot, since it says fastboot at the top and has the Androids on the bottom skateboarding. Is this an issue? And am I screwed because I can't access the OS to turn the option off?

When you see the fastboot at the top of the screen and the androids skating at the bottom, that is perfectly normal. That is the pre screen before actually going into the bootloader. If your keys work, u press the volume down button to select which option you want, which will highlight in blue. The first option is the bootloader, so if you press the power button, it will load into the bootloader. The bootloader looks exactly the same as this screen, but with different options. This screen will show hboot at the top and have the options of fastboot, recovery, factory reset, simlock, and image crc. I have never heard of the keys not working at this point, so i couldn't help you there. Search around the forums if you haven't already.
If you want to compare this to something more familiar, think of these two screens as your motherboard bios to your PC. (What you see when your pc boots up, before it loads the OS, windows, mac, etc) On a pc, you can install any OS you want, like on the inspire, you can install any custom rom you want. But the motherboard bios is the highest level of permanent software that is directly written to the motherboard itself, like the bootloader/hboot is on the inspire. When rooting, you are essentially altering the motherboard bios on the inspire. When you install a custom rom, you are just installing an OS on the inspire.
There are plenty of custom ROMS that are based off of stock in the development section. I use and like Android Revolution. But when choosing custom roms, its always a matter of preference, and what works best for you.

digitalism said:
Thanks for the reply.
But here's my problem:
I can't access the HBoot menu in order to flash or install any type of file.
I've been using the terminal on my Mac to do most of my editing, and now I've ran in to a new problem: whenever I try to move files to my sd root, it says that the card is read only and therefore no files can be transferred to it.
I use the command ./adb push PD98IMG.zip /sdcard/
This is where I get the error.
Also, it takes my phone literally 5 or 6 minutes to boot into the splash screen after I use the command ./adb reboot bootloader/recovery (both of which I have tried).
I'm beginning to get quite frustrated, as I'm sure you can understand. I've also attempted to rewrite all of the necessary root programs onto the device in hope that the bootloader and recovery options will be accessible.
Do you have a solution for the write problem I am getting from my device?
Thanks.
Click to expand...
Click to collapse
It sounds like you may have the bad combination of a newer Inspire and the older ENG hboot. This is a problem dealt with commonly on the Aria/Inspire IRC channel. If you want to jump in, we can probably get you straightened out.
http://webchat.freenode.net/?channels=#liberatedAria

Awesome.
I am a little upset that I can't choose an action from the boot menu with the keys on the phone.
It also seems that the only way I can completely get into the boot menu is through the terminal after which I run ./fastboot-mac
After I put in this action, the menu will begin looking for the PD98IMG.zip file, and only goes on to say that there is no file, when there actually is one.
I just wish I could do all of this straight from the phone since I'm not well versed on terminal and commands for running programs to their full ability.
I wish I could figure out a way to the write permission on my sdcard so I could reinstall the .zip file for the bootloader to find.

digitalism said:
Awesome.
I am a little upset that I can't choose an action from the boot menu with the keys on the phone.
It also seems that the only way I can completely get into the boot menu is through the terminal after which I run ./fastboot-mac
After I put in this action, the menu will begin looking for the PD98IMG.zip file, and only goes on to say that there is no file, when there actually is one.
I just wish I could do all of this straight from the phone since I'm not well versed on terminal and commands for running programs to their full ability.
I wish I could figure out a way to the write permission on my sdcard so I could reinstall the .zip file for the bootloader to find.
Click to expand...
Click to collapse
You will not be able to use the volume rocker to select options if you have a PD98IMG.zip on your SD card.
Try booting into hboot with the SD card removed. That should let you move around the menu.
Sent from my Inspire 4G using the power of the dark side

Thanks for the heads up!
I can move the menus now.
Seems like all is going well now...
Just a matter of time.

digitalism said:
Thanks for the heads up!
I can move the menus now.
Seems like all is going well now...
Just a matter of time.
Click to expand...
Click to collapse
It's good to hear you're moving forward. Let us know how it comes out.
Sent from my Inspire 4G using the power of the dark side

[Q] Sony Xperia Z1 Compact stuck when using TWRP 2.8!

Hi,
I am very new to all of this and I appear to have bricked my phone (sort of).
Before discovering this website I thought I'd remove the bloatware from my phone by following a Youtube video by SHEM so I could get root privileges.
However I got up to the part where I start using TWRP (5:40) and the actual display doesn't fit on my screen! Only three buttons fit going down the screen (Install, Backup and Mount) the others in the next row are cut off before the text reveals what they are. Because I know the one next to Install is Wipe, I press it but I cannot continue because Swipe to Wipe is completely off-screen.
So it seems that I am stuck with a phone that doesn't really do anything. All that happens when I switch on my phone is a light turns red, then the Sony logo appears, then the light turns green and the cycle repeats. All I am able to do is go into TWRP or switch off my phone (which doesn't appear to be completely off, the screen just turns black and it still seems to drain power). I am hoping that there's a way to resolve the issue, but my current level of inexperience leaves me clueless.
I think it may be important to mention that when I ran Z1-lockeddualrecovery2.8.0-RELEASE.installer it revealed a couple errors in the process. Everything seemed to work as expected however up until this point, though I'm not sure if my issue is connected.
I'm hoping somebody here will be able to assist, because I need my phone (obviously) and I would like to learn get root access without all the headaches.
Please help me!

Erm4hgerd_Lulz said:
Hi,
I am very new to all of this and I appear to have bricked my phone (sort of).
Before discovering this website I thought I'd remove the bloatware from my phone by following a Youtube video by SHEM so I could get root privileges.
However I got up to the part where I start using TWRP (5:40) and the actual display doesn't fit on my screen! Only three buttons fit going down the screen (Install, Backup and Mount) the others in the next row are cut off before the text reveals what they are. Because I know the one next to Install is Wipe, I press it but I cannot continue because Swipe to Wipe is completely off-screen.
So it seems that I am stuck with a phone that doesn't really do anything. All that happens when I switch on my phone is a light turns red, then the Sony logo appears, then the light turns green and the cycle repeats. All I am able to do is go into TWRP or switch off my phone (which doesn't appear to be completely off, the screen just turns black and it still seems to drain power). I am hoping that there's a way to resolve the issue, but my current level of inexperience leaves me clueless.
I think it may be important to mention that when I ran Z1-lockeddualrecovery2.8.0-RELEASE.installer it revealed a couple errors in the process. Everything seemed to work as expected however up until this point, though I'm not sure if my issue is connected.
I'm hoping somebody here will be able to assist, because I need my phone (obviously) and I would like to learn get root access without all the headaches.
Please help me!
Click to expand...
Click to collapse
you are stuck in a bootloop,
Thankfully there is a simple guide to fix this here, hope it all goes well

mbloomer04 said:
you are stuck in a bootloop,
Thankfully there is a simple guide to fix this *Wont let me post the link yet* hope it all goes well
Click to expand...
Click to collapse
Thanks for getting back to me. I went to the link and tried what it suggested.
I tried to follow the instructions under Finding the cause of the bootloop for After flashing a new rom, but the first part Start your phone in CWM Recovery says to hold down Home whilst turning the phone on. However, there is no Home button on the Xperia Z1 Compact. There is only Power, Vol Up & Down and the Camera button. I tried combinations of all and nothing changes. I still end up in a bootloop.
I will note that the bootloop occurs in the same way that I described in the OP, except that the red light doesn't flash. This only happens when the phone is connected to my computer via usb.

I managed to download the latest firmware from firmwaremobile(dot)com, re-flashed my phone and now it's back to normal.
I think I'll try getting root access again from one of the tutorials here on this site. I get the feeling that a lot of you know what you're doing when it comes to this sort of thing and can be trusted.
Can anybody recommend any particular one that gives root access on an Xperia Z1 Compact with the view of removing all bloatware from the device?

Erm4hgerd_Lulz said:
I managed to download the latest firmware from firmwaremobile(dot)com, re-flashed my phone and now it's back to normal.
I think I'll try getting root access again from one of the tutorials here on this site. I get the feeling that a lot of you know what you're doing when it comes to this sort of thing and can be trusted.
Can anybody recommend any particular one that gives root access on an Xperia Z1 Compact with the view of removing all bloatware from the device?
Click to expand...
Click to collapse
Here is an easy to use guide designed for the z1 compact, once you have rooted you can uninstall bloatware as you would any other app

mbloomer04 said:
Here is an easy to use guide designed for the z1 compact, once you have rooted you can uninstall bloatware as you would any other app
Click to expand...
Click to collapse
Thanks! I'll check it out and see how I go. :good:

Erm4hgerd_Lulz said:
Thanks! I'll check it out and see how I go. :good:
Click to expand...
Click to collapse
cheers, let us know how it goes and if need be we can look at other options

Question Z flip 3 bootloop

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.