Related
So my FUZE was working fine since I bought it when it first came out. It was on Stock ROM, Radio, and SPL. I decided to flash the EnergyROM to try out the new Manilla. I installed the Hard-SPL, flashed the 1.12.25.19 radio, and then flashed EnergyROM 2.0 32209. First thing I noticed was that the DPAD was HORRIBLE.
It would not correctly sense what I am pressing! I press home, and some times it doesn't register anything, sometimes it thinks I pressed left. I try the back button but it thinks I pressed right. I have had this thing since it came out so I know how to use the DPAD now, but whatever happened has completely screwed it up! I thought it was the ROM so I went to the leaked AT&T Test ROM which is also VERY nice. But the problem is still there, the DPAD just does NOT work correctly.
Also, I was unable to send an SMS earlier until I soft reset the phone. That had never happened before either.
Since it is not the ROM, it is either the Radio or the SPL. What I don't understand is that many many people have installed both the same Radio and SPL without any problems. How can I fix my DPAD?
petard said:
So my FUZE was working fine since I bought it when it first came out. It was on Stock ROM, Radio, and SPL. I decided to flash the EnergyROM to try out the new Manilla. I installed the Hard-SPL, flashed the 1.12.25.19 radio, and then flashed EnergyROM 2.0 32209. First thing I noticed was that the DPAD was HORRIBLE.
It would not correctly sense what I am pressing! I press home, and some times it doesn't register anything, sometimes it thinks I pressed left. I try the back button but it thinks I pressed right. I have had this thing since it came out so I know how to use the DPAD now, but whatever happened has completely screwed it up! I thought it was the ROM so I went to the leaked AT&T Test ROM which is also VERY nice. But the problem is still there, the DPAD just does NOT work correctly.
Also, I was unable to send an SMS earlier until I soft reset the phone. That had never happened before either.
Since it is not the ROM, it is either the Radio or the SPL. What I don't understand is that many many people have installed both the same Radio and SPL without any problems. How can I fix my DPAD?
Click to expand...
Click to collapse
Did you try flashing back to the stock ROM? If that doesn't work, I wonder if flashing back to stock everything (ROM, radio, SPL) might kick out the bugs (?)
Did you hard reset after flashing? That might be your problem. And what programs/settings did you install? I would hard reset-don't run UC-then see if the dpad is working fine.
I had the problem without installing anything over the ROM itself. When you flash a ROM, it hard resets, so what does hard resetting again do? I spent like 2 hours getting it the way I like it so I don't want to hard reset again. I tried reflashing the radio but it still had the problem right afterwards, but now it seems to have stopped. This is very weired.
EDIT: It started doing it again but if I put the phone to sleep and bring it back, it normally fixes it. What an annoying problem. I am going to try to flash a different radio and see what happens. I just like this radio so much its GPS actually works decently.
petard said:
I had the problem without installing anything over the ROM itself. When you flash a ROM, it hard resets, so what does hard resetting again do? I spent like 2 hours getting it the way I like it so I don't want to hard reset again. I tried reflashing the radio but it still had the problem right afterwards, but now it seems to have stopped. This is very weired.
Click to expand...
Click to collapse
No, it doesn't do a full hard reset when you flash. A lot of crap is left over, and if you just start using the ROM, you get a bunch of random bugs, like, say your DPAD doesn't work. You're supposed to hard reset when the the phone asks you to align the screen. It's a must. Seriously, hard reset and start over and all of your problems will go away.
I reverted to my stock radio and the problem seems to have disappeared. I will try it out more tomorrow.
How is anything left over? It just seems so odd because I can't ever find anything from before when I flash a ROM.
It seems that I can still get fast GPS locks with this radio too, so I guess the A-GPS fix is all in the ROM.
petard said:
I reverted to my stock radio and the problem seems to have disappeared. I will try it out more tomorrow.
How is anything left over? It just seems so odd because I can't ever find anything from before when I flash a ROM.
It seems that I can still get fast GPS locks with this radio too, so I guess the A-GPS fix is all in the ROM.
Click to expand...
Click to collapse
I have no idea how anything is left over, it just is. Here's what mskip's thread says:
mskip said:
[FONT="]Flashing Via ActiveSync[/FONT]
[FONT="]1. Download your prefered Rom from the Raphael Rom Develpoment Page and unzip/unrar it to your computer.[/FONT]
[FONT="]2. REMOVE SIM and microSD CARDS!![/FONT]
[FONT="]3. Turn phone back on and wait until it syncs with your PC.[/FONT]
[FONT="]4. Run the Raphael_RUU.exe (or [/FONT][/SIZE]RaphaelWrapper.exe if thats included instead) [FONT="]from the Roms Folder.[/FONT]
[FONT="]5. Once phone finishes flashing and gets to the screen where it configures the stylus, HARD RESET[/FONT]
[FONT="](hold the VOLUME DOWN and ENTER (center) Buttons, press the RESET button with the stylus tip, then release the RESET button but continue to hold the VOLUME DOWN and ENTER buttons until the reset screen appears)[/FONT]
[FONT="]6. Follow onscreen instructions to set up your New Rom.[/FONT]
[FONT="]7. Once phone has gone through the customisation procedure then replace Sim and microSD Cards.[/FONT]
[FONT="]8. Turn phone back on and set up as required.[/FONT]
[FONT="]Flashing Via MicroSD Card[/FONT]
[FONT="]1. Make sure your microSD is Formatted to fat32 using a PC (you dont have to delete all files but it is safer if you do).[/FONT]
[FONT="]2. Download your prefered Rom from the Raphael Rom Develpoment Page and unzip/unrar it to your computer.[/FONT]
[FONT="]3. Goto the Roms Folder and rename the .nbh file to RAPHIMG.nbh[/FONT]
[FONT="]4. Copy the RAPHIMG.nbh file to the root of your microSD Card.[/FONT]
[FONT="]5. Plug the microSD Card into the phone.[/FONT]
[FONT="]6. Press and hold the volume down button, then press the reset button with the stylus. Release the volume down button when bootloader tricolour screen appears.[/FONT]
[FONT="]7. Follow the onscreen instructions to start flashing.[/FONT]
8. Once phone finishes flashing and says Update Complete, reset with the stylus
[FONT="]9. When it gets to the screen where it configures the stylus, HARD RESET[/FONT]
[FONT="](hold the VOLUME DOWN and ENTER (center) Buttons, press the RESET button with the stylus tip, then release the RESET button but continue to hold the VOLUME DOWN and ENTER buttons until the reset screen appears)[/FONT]
[FONT="]10. Follow onscreen instructions to set up your New Rom.[/FONT]
Click to expand...
Click to collapse
Here are flashing instructions from At0mAng:
Install Instructions
Read The Flashing Your First GSM ROM Guide
Make sure your battery is 50% charged or more
Power off & Remove SIM Card
Power back on and sync with PC
Flash ROM
Hard Reset where it ask you to align screen
Click to expand...
Click to collapse
They're not telling you to do the hard reset just for the heck of it; there's a very good reason for doing it. Not following the standard flashing instructions and then posting in the chef's thread that his ROM is buggy is just not cool.
It turned out to be the radio causing my problems not the ROM. I have never hard reset after flashing a ROM and never had a problem (and that time wasn't a problem because it was due to the radio ROM)
Not that I am asking for it, but unless there is actual proof that you need to hard reset, I don't think there is a point of doing it.
Ok the problem is back! So annoying. Does flashing the SPL hard reset the phone? I want to try going back to the stock SPL since that is the only thing it could still be, but I would rather not now if it hard resets.
Just get it over with and do a hard reset. Jeez, it's not that complicated.
roms and radios will not adjust the dpad i used the same rom u talk about and never had an issue
Hey petard, did you ever fix the issue with the D-pad ?
I have the exact same issue with my Fuze and can't figure it out.
It is a hardware issue. I had to replace it. My replacement worked fine until about 3 weeks ago where it just started to act up. I called for another replacement a couple days ago and should get it tuesday. They offered me a different phone (Epix or Incite) but I declined but told them to note it that I was offered a different phone.
In about 3 months (when my warranty ends) I will call for another replacement. If they have refurbed Touch Pro 2s by then I will ask for that, if not I will get another FUZE which will extend my warranty for 3 more months (you get 3 months or whatever was left of your original warranty, whichever is longer) and by that time they have to have refurbed Touch Pro 2s where I will then try to get one.
petard said:
It is a hardware issue. I had to replace it. My replacement worked fine until about 3 weeks ago ...
Click to expand...
Click to collapse
It figures, no easy fix. It's strange how it started to act up, mine crapped out right after a flash as well.
Good luck on aquiring the TP2 though.
I have a device that used to belong to a MSFT employee. At Microsoft you can just hand in your device and they will put a new ROM on it for you. So first thing I did when I got it is to HardSPL (OliNex 1.90) it and load up a new ROM (the one on it was a couple of builds back, and GPS didn't work etc.).
The strange thing is that ROMS seem to be 'loosing' files (as far as I can tell - apps won't open etc.) after a few days of otherwise great operation. If the device is rebooted, it's almost like a hard-reset; although the installation takes next to no time: and it gets stuck on the splash. Hard resetting the device makes it work for a few days more. The device didn't have these problems with the MSFT ROM (which I stupidly didn't backup).
I have tried a few ROMs and they all seem to have the problem:
MagicROM_23541_Sense25_Mar01
TAELROM_v4.23541_SENSE_2.5_28FEB10_LD
Timolol_5100207TH (awesome ROM)
So my current plan:
Flash stock ROM.
Flash stock SPL.
Flash stock ROM (hoping it will clear anything funny MSFT put on it).
Hard SPL.
Flash Timolol Stock-Like (seems to have the problems the soonest - 2 days max).
Does anyone have any other ideas?
Thanks guys.
I assume since you posted in the Touch Pro2/Tilt 2 section, that you own one of those devices. The roms you have mentioned below are (I believe) for a touch pro/fuze device. That could be your problem. Although, I would assume that you have one as I'm sure a rom for a different device would even flash to the device period. If you have the right rom/device combo and its a touch pro, then you should post in the thread for the roms. More details such as network and device will help the most.
Ah crap - the dangers of having too many tabs open. Can I move the thread myself?
moitoius said:
Ah crap - the dangers of having too many tabs open. Can I move the thread myself?
Click to expand...
Click to collapse
i moved it for you good luck at finding a solution
I don't think it's a hot idea to flash the stock spl. I'm not sure that it can be over-written with hard spl-you'll have to ask in the hard spl thread. If you do it, you might be stuck with the stock rom. Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.
Farmer Ted said:
...Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.
Click to expand...
Click to collapse
Thanks, that is significantly fewer steps . I will do that for now and report back in 2 or so days...
Small update - just flashed the latest stock Fuze ROM. Just before the customization app come up I saw that device.exe crashed... In any case, I will see what happens with the custom ROM.
You may need to reformat the memory of your phone. Having device.exe crash on a stock rom during bootup is kind of weird. I've never done it myself, but there are threads on it in the Leo forum. I wouldn't try the apps that they've put together, though. I guess you can search around for "Task 29" to find out how to do it properly.
Moved as not ROM Development.
@OP:
If the device was flashed on a regular basis, it's possible that the device flash memory is near end-of-life.
You could try running Raphael Diagnostics on it to see if that sorts it out.
HTH,
What is the lifespan (in terms of flashes) for a device like this?
Plus minus 2 days - it has been able to go as far as 5.
According to this post: http://forum.xda-developers.com/archive/index.php/t-514940.html
These are good options:
http://forum.xda-developers.com/showthread.php?t=435527
http://forum.xda-developers.com/showthread.php?t=491554
This one in particular: http://forum.xda-developers.com/showpost.php?p=3446141&postcount=16 (it applies to Rhodium, but people have had success with it).
Apparently Task 2a (equivalent of 29) is disabled on the OliNex 1.90 SPL - so I can't do a NAND format without reflashing the stock SPL (not that I would attempt that myself in any case ).
I'll run RaphaelDiagnostics and see if that comes up with anything.
Thanks for the help so far guys, I first want to see if the stock flash I did works (I smell a Wiki page).
I tried out the raphdiag-it's pretty cool. I've been having a few weird issues lately on my fuze. In particular, all of a sudden my boot-up time seems to have gotten slow (millisecond to idle thread went from 65-70 sec to 90-95 sec, and I hadn't messed with start up programs). Also, I have been having an issue with files on the main memory becoming corrupted, which has just been weird. Anyway, I ran an 'info 8' with mtty a few weeks ago, and it came up with 7 bad blocks, which seems normal. So, I ran raphdiag this morning, and ran the format nand routine. I was a little surprised, because after running it, I soft reset and the phone booted up normally like after a hard reset. I thought that it was going to wipe the entire rom memory clean, leaving only the radio, bootloader and splash screen. It didn't seem much different from a hard reset. The good news is that my startup is faster. With a setup I was using beforehand, the millisecond-to-idle-thread speed was 76 seconds, and after the format it was down to 71 seconds. However, I ran an 'info 8', and the memory analysis hadn't changed at all (same 7 bad blocks). I'm not sure if the formatting (task 29 or this) is supposed to clear that up, though.
I put both the raphdiag.nbh and a raphimg.nbh on the root of my normal 16 gb card. When you go into bootloader, it does a quick image update (takes about 2 seconds), then the screen tells you to push power for a rom update or push the action button to go into diagnostics. From there, you have maybe 4 or 5 choices. Scroll up and down with the up/down buttons, then push action. The first is a set of hardware tests, the second is something like 'run in/on', which appears to be a test scheduler. The 3d is the NAND format option, and I think the 4th and 5th options are 'calculate rom checksum' and then 'skuid', or something like that. To exit, I just soft reset, or used soft reset/vol down to go back to bootloader. After the format, I tried to flash (I think it called it re-flash), but it said there was no image present. You may need to do this on a clean card to get it to work (that is, format and then flash off the same card without swapping things out).
The diag tests are kind of cool. There's an auto mode that runs through all of them, but you have to do things to get it to work. The first is an LED test. The screen turns red, you stare at it for 5 min wondering what the hell is going on, then push the action button for the hell of it. Then the screen turns green. Push it a bunch more times, and it goes through shaded and checkered screens and whatnot, then it tells you it passed the test. There's a test for the slider, and you need to slide the keyboard in and out. The qwerty test was weird. It's configured for a touch pro (not a fuze), so I didn't know what the hell to do at first. The screen just says 'QWERTY_KBD_1', or something like that. I tried hitting the '1' button, and fn-1, and it did nothing. Then I just hit the top left button, and it said OK and prompted to hit 2. So, you just push all the keyboard buttons from left to right, top to bottom. There are also tests for the other hardware buttons, except for the 4 main buttons on the d-pad (home, back, send, end), which was kind of weird. If you think your power button or vol down button is effed, this tool will confirm/deny it for you.
Right, so the RaphDiag didn't brick your device. It's a bit risky - so I will first resort to less extreme measures - at least I know there is one success story.
I seriously wouldn't worry about it, but you may want to have a card reader available in case you need to remove raphdiag from you sd card to get a flash to work. It's possible that I didn't get the nand format to work properly, but I think I did it right, because the device definitely needed to cold boot. I was just surprised that there was still an OS there.
I'll take your word for it - BUT - in terms of gaining knowledge I am going to try the steps in the posts I found. If the NAND does need a format there is no doubt that I will land up doing it - but I will have first-hand experience.
This really needs a Wiki page once I am done; so I want to squeeze as much info out of the device as I can.
Can anyone else think of any gotcha's before I potentially brick it?
I ran the format a second time. It's really fast; it takes maybe 5 seconds. I haven't figure out how to exit from that part of the diag other than soft resetting, which leads to a cold boot. I'm surprised it's so fast. A hard reset takes about 30 seconds. I guess that it's working properly.
Farmer Ted said:
I ran the format a second time.
Click to expand...
Click to collapse
You are either very brave or very rich . Right, so here is hoping I have to go the final resort route - nothing yet though.
Hi all
Today I was trying to get my nexus s onto the official ota ICS update by flashing it manually, following guides other people had had success with.
I was on the cm9 ics beta, so I had to flash the full rom of 2.3.6.
This worked completely, however I think the ota update file I downloaded was corrupted, as flashing didn't work, it said something about signature verification failed. So I redownloaded it, from the same link, and the new one was bigger. I tried that, and the same error. I tried wiping data/factory reset etc, and I accidentally started to flash a cm7 rom I had on my phone.
I stupidly did a battery pull as it started to flash (the back cover was off already), and now my touchscreen doesn't work. I was able to successfully flash other roms including the 2.3.6 I downloaded, and I couldn't do the first setup procedure (touch the android to begin). I tried cleaning the screen very carefully with 90% isopropyl alcohol, the same stuff I use to replace thermal paste on cpus.
It still doesn't work. I am hoping it is a software issue that can be fixed otherwise I have to return it.
Someone please help
I have used the search function and none of the solutions I found worked.
(UPDATE) I rebooted again, and when the phone booted into cm7, the "internet" icon(the globe picture) on the bottom left of the dock was in the "pressed" state(orange). It was like the phone thought I was holding my finger on it, which suggested a hardware issue. I cleaned it again and nothing changed. Then I held the phone in the landscape position. When the screen rotated, the button stayed pressed. So the phone doesn't think "this part of the screen is being pressed" it thinks "this internet icon" is being pressed. Rotating the phone again and again didn't change anything, the icon was still pressed in.
Defiantly a software issue. I would try to unroot and reroot. Then if it is still not working, try to format the SD card. You may want to considering buying a USB to micro USB adapter to help you, considering then u could plug in a mouse. I have one just in case I need it.
Thank me if any of this helped
Also try and keep this updated with new info. If I can't help, maybe someone else can.
Sent from my XT862 using XDA App
Thanks techno-update, I will try that. I haven't "unrooted" before, Is that just typing fastboot oem lock or whatever it is instead of fastboot oem unlock?
Also, I found a youtube video with the EXACT same problem.
v=zpfE15Xw_os&feature=related
Skip to 3:15, and you will see when he opens the power menu, the phone thinks he is pressing on one of the options, but he isn't.
I will let you know how unrooting and rerooting goes.
Thanks
(UPDATE)
I tried unrooting and then rooting again. It still does the same thing.
Even in cwr I can't use the capacitive buttons to navigate menus, does that rule out software problems? I am really hoping its just a software problem :/
I need my phone for an outing tonight (im in australia, its 5pm now) and I would appreciate it if some genius could solve this
I am usually the "go to fix it IT guy" in my area, but I can't figure this one out. I have tried formatting the phone, reflashing the mod etc.
Is there some more aggressive COMPLETE wipe or something that fully wipes the phone?
UPDATE 2
Guys please help,
I just flashed zulugen mod, as it has the trinity kernel, I don't know much about android os, but I hoped that that might replace the touchscreen driver or something. The rom flashed correctly, but touchscreen and the capacitive buttons still don't work. Please help
Guys, is there some sort of system partition where the touchscreen drivers are kept or something? And when I pulled the battery as it was flashing cm7, it corrupted these?
Is there some way to fix this?
bump
bump. I need help with this urgently. Is it possible the connections for the screen came loose inside? I would crack it open but don't have screwdrivers for the 3 smaller screws on the last layer of plastic before the pc board.
So I picked up my phone, wouldnt turn on. No biggie, battery must be gone (stupid custom rom sucking all the power) plugged it in, let it charge for a bit, I came back to it and tried to turn it on. I got 3 vibrations and an orange light but no screen. I attempted to access the bootloader, got 5 vibrations I think and a green light but no screen. I started searching for ruu and img.zip files to attempt to reflash, backed up my sd card and then went back to the phone and tried once more to turn it on and it started up? I had the battery removed for a few minutes. However, it worries me that this happened and I'm wondering if the guys here that know about more technical stuff can explain why this was only temporary when it seemed like a serious corruption in the boot sequence? most vibrate bricks are permanent in that they have to be reflashed. And finally, how can I prevent this from happening again? Sorry for the book I just typed <--- But if it happens anyone else, its nice to know they have someone else who was in the same boat.
Edit:
HTC Desire S
Europe-Factory Unlocked
Custom Rom: Andromadus - CM10... Has a few small things to be fixed but atleast its Jelly Bean
Clock Speed before brick: 245-806, interactive governer. (was trying to save battery, usuall on about 1.2-1.4)
Unsure of hboot
Solved
I apologise to moderators if this thread messes with any rules but I managed to figure out the problem, So this thread may be handy to someone else. Most HTC phones are similar in the way they boot and how the buttons are set up with the board. So i believe my up volume buttton was stuck due to some dirt which caused it to be held down. This caused either a boot error or it was the backup download thing (fastboot or something along that road). So dont panic guys if you get the vibrate brick. It might just be as simple as some dust. Thank fully my phone is in working order again.
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.