Database Info

[Q] Question about reset switch

Hey, all.
What does the internal reset button actually do? I was expecting it to reset to factory settings, but fortunately for me it didn't do this. I'm actually happy it didn't, as it means I didn't lose any of the customizations I had done or applications I had installed.
I just cracked open the case on my gTablet and pressed what I assumed to be the reset button, a tiny little white switch in the center of the unit. After pressing and holding it for about 3 seconds, the tablet immediately powered back on and returned to its previous state. Everything appears to be functioning perfectly normally and exactly as it was before.
What does the reset button actually do? Do I need to worry about battery meter not being accurate or any other weird side effects? I only mention that because the battery gauge is showing 100%, but the external red charge light is still on.
I'm not sure what prompted it, but earlier today, my gTablet went blank and wouldn't turn back on at all. My son had been playing Angry Birds for an hour or so and I had been using it heavily showing it off to my in-laws, so I thought perhaps the battery had simply gone dead. I had not plugged in the charger the night before, so it seemed to be a reasonable explanation.
I plugged the charger in and the external red light was visible, so I let it charge for a little while, then tried turning back on. I could press any number of different key combinations (power & vol+, power & vol-, holding button for long time followed by short press, etc.) but I got nothing but a black screen. There was no indication whatsoever that anything was happening.
I was assuming something had gone quite awry, but didn't panic. My wife was not quite so calm, but I reassured her that I would be able to find the answer on the XDA forums. Thanks to everyone who has contributed to this great community, by the way!
First, I tried plugging in the USB cable to my Windows 7 laptop and heard the distinctive 'bing-bing,' notifying me that hardware was recognized, so I knew it wasn't dead. But, it didn't show up anywhere, so I checked the Device Manager. Interestingly, there was no yellow exclamation mark anywhere, as I expected from reading some other posts about NVFlash. I finally found it listed under the 'Disk Drives' section as: 'NVIDIA Tegra 2 USB Device.'
I remembered reading about people experiencing problems with the unit going into APX mode, but I also remembered reading about the internal reset button on the gTablet. So, I figured before I attempted to use NVFlash, I would try the reset button first. Fortunately, these devices were designed well and the case was very easy to pop off.
By the way, I was running the stock ROM, but with the TNT 3588 Enhancement Pack (Gapps with nVidia Drivers) provided by edirector. I had also installed the z4root application. I used the default ROM for the first day, but was comfortable with the idea of flashing othe ROMs, as I've done it with my HTC Aria phone. I flashed roebeet's TNT Lite 4.40 and used that for several days before going back to the factory ROM with the enhancement pack.
Thanks in advance,
Calvin

Well,
I've been reading these forums since last November and I don't know of anyone who
has really reported on "pushing" the reset button before!!!
Usually when people crack the case to push the reset button or unplug the battery
for 10-15 seconds it is a situation where they can't get the machine to start and
literally have nothing to loose.
Sounds to me (in terms of 30+ year of different computers) that you did a hardware
reset and boot. I assume something was locked up inside and the reset key released
it to restart.
Glad for you!!!
Rev

[Q] Samsung Galaxy Tab 2 10.1 Hacked, Touchscreen unresponsive

Samsung Galaxy Tab 2 10.1 Hacked, Touchscreen unresponsive
Hi! I need help with my tablet.
Device: Samsung Galaxy Tab 2 10.1 Tablet, model GT-P5113 TS. This model doesn't have a way to yank out the battery.
What's wrong: Touchscreen is not responding.
Current state: Attempting to drain the battery. Doesn't appear to be turned on. Factory reset apparently performed.
What happened: Sorry, this is long. It is as best as I can remember it. It may be somewhat inaccurate.
Yesterday evening, I was on my Windows laptop and logged into my Google account. I *thought* I used the Google Play Store to install Chrome to the tablet. (I had looked at the html5test website and it said Chrome had a higher HTML5 rating than the Dolphin/Jetpack browser I've been using on my tablet.)
But something went terribly wrong.
After sending Chrome to it, I unlocked the tablet and used both Chrome and Dolphin to go to html5test website. They both scored the same or nearly the same. I don't know if any of that is relevant, but I'm including it just in case.
At some point after that, I woke the tablet with the power key and used my unlock pattern on the dots lock screen.
That's when I saw what I believe was mal-ware in action. The settings menus were scrolling and sub-menus being selected, all by themselves. I couldn't say exactly what was changed because whatever program or script that was running the process was going extremely fast.
When I realized it might be trying to send out data over my Wifi network, I turned off the Wifi router in my home.
I repeatedly held down the power key to turn the system off, but doing so only rebooted back to the useless lock screen which was not responding to anything. The normal method of holding the power button for a few seconds to bring up the menu and then tapping the "Power Off" option on that menu refused to power off the system. Nothing on that menu responded to touch.
Entering my pattern on the lock screen did absolutely nothing. I didn't even see any lines traced when I ran my finger over the screen.
At some point, I pulled out the external SD card. I have no idea if whatever hacked the tablet also put a copy of itself on the SD card.
I called a friend who looked up how to restore the tablet to factory settings. I didn't understand the directions exactly, so I ended up on a screen with a Warning!! about installing a Custom OS. (Holding down the Power + Volume Up seems to get me there)
I left it on this screen, and I turned my router back on and using my laptop, contacted Live Chat at Samsung but they didn't understand my problem. They told me to reboot the device and swipe my pattern several times and then after several failed attempts I would have the chance to use my Google credentials to get into it. But the device apparently never registered that my swipe attempts were failing.
So my device was booted up with me locked out, with the WiFi router on for a little while again. I turned off the router as soon as I realized that. That disconnected the chat session, but since Samsung chat wasn't helping me anyway, I didn't bother trying to go back.
I got the device back to the "Warning!!" screen. Then turned the router back on and searched for how to do a factory reset of the device. I found a video on YouTube and followed it.
I pressed the Volume Down and Power buttons simultaneously, followed by letting go of the power button. That brought up a menu which contained several options, including an option to do a factory reset. I used the volume buttons to highlight that and pressed Power key. A second screen came up and I used the volume buttons and power button to select "Yes" to confirm the reset.
It appeared to have done a factory reset, rebooting eventually.
However, after that, when I tried to tap on the touch screen to move forward through the selections, the touch screen was still unresponsive!
So I brought back the "Warning!!" screen and ran the battery down until the screen was blank and it wouldn't start when I held the power key.
Then I charged it for about 20 minutes and rebooted it. I think when it came back it was on the Recovery menu. I think I did a second factory reset, but not 100% sure. It eventually rebooted after a lot longer than usual.
When it came up, it was saying battery was low. I tried to tap the OK button, but nothing happened. Behind the battery window was the first setting screen to set up the device for the first time after a factory reset. (I think selecting USA?)
I brought back the "Warning!!" screen and left it on overnight so that the battery would run down.
That was about 8 hours ago. When I woke up, I used clear tape to keep the power button pressed down, to ensure that the battery will continue to run down.
____________________________________________
What do I do next? How do I get the touch screen to start working again? It is not a hardware problem, unless mal-ware can break the hardware. The touchscreen had been working fine until this happened.
Should I take the tablet back to Best Buy where I bought it at least a year (maybe 2 years) ago? I don't know if it's still under warranty.
I have over 20 year of experience as a software developer, but not for Android. I am not very experienced with doing anything to hardware.
Should I try to fix it myself?
I have never rooted any Android device and I'm not sure what that means, either.
I've never re-installed the ______ ? (rom? image? Odin?)
I read on this and/or other forums that there's a way to replace something, but the instructions were beyond my level of understanding. I would need the procedures to be broken down into steps which don't assume too much about what I know.
I understand how to download a file to Windows, given a URL for it. I understand what a zip file is and how to extract it. I understand how to press hardware buttons and plug in cables, and do these steps in the order I'm told.
I don't understand what I'd use to get the downloaded whatever-they-are onto the tablet to replace whatever-the-other-thing-is so that the touchscreen works again.
As far as I know, Odin is a Norse god.
The only firmware updates I've ever done are the ones that the device does on it's own through Samsung's updates.
I'd deeply appreciate getting this device back since I have extremely limited funds and probably won't be able to buy a replacement.
Thank you,
Linda

LMurphy said:
Samsung Galaxy Tab 2 10.1 Hacked, Touchscreen unresponsive
Hi! I need help with my tablet.
Device: Samsung Galaxy Tab 2 10.1 Tablet, model GT-P5113 TS. This model doesn't have a way to yank out the battery.
What's wrong: Touchscreen is not responding.
Current state: Attempting to drain the battery. Doesn't appear to be turned on. Factory reset apparently performed.
What happened: Sorry, this is long. It is as best as I can remember it. It may be somewhat inaccurate.
Yesterday evening, I was on my Windows laptop and logged into my Google account. I *thought* I used the Google Play Store to install Chrome to the tablet. (I had looked at the html5test website and it said Chrome had a higher HTML5 rating than the Dolphin/Jetpack browser I've been using on my tablet.)
But something went terribly wrong.
After sending Chrome to it, I unlocked the tablet and used both Chrome and Dolphin to go to html5test website. They both scored the same or nearly the same. I don't know if any of that is relevant, but I'm including it just in case.
At some point after that, I woke the tablet with the power key and used my unlock pattern on the dots lock screen.
That's when I saw what I believe was mal-ware in action. The settings menus were scrolling and sub-menus being selected, all by themselves. I couldn't say exactly what was changed because whatever program or script that was running the process was going extremely fast.
When I realized it might be trying to send out data over my Wifi network, I turned off the Wifi router in my home.
I repeatedly held down the power key to turn the system off, but doing so only rebooted back to the useless lock screen which was not responding to anything. The normal method of holding the power button for a few seconds to bring up the menu and then tapping the "Power Off" option on that menu refused to power off the system. Nothing on that menu responded to touch.
Entering my pattern on the lock screen did absolutely nothing. I didn't even see any lines traced when I ran my finger over the screen.
At some point, I pulled out the external SD card. I have no idea if whatever hacked the tablet also put a copy of itself on the SD card.
I called a friend who looked up how to restore the tablet to factory settings. I didn't understand the directions exactly, so I ended up on a screen with a Warning!! about installing a Custom OS. (Holding down the Power + Volume Up seems to get me there)
I left it on this screen, and I turned my router back on and using my laptop, contacted Live Chat at Samsung but they didn't understand my problem. They told me to reboot the device and swipe my pattern several times and then after several failed attempts I would have the chance to use my Google credentials to get into it. But the device apparently never registered that my swipe attempts were failing.
So my device was booted up with me locked out, with the WiFi router on for a little while again. I turned off the router as soon as I realized that. That disconnected the chat session, but since Samsung chat wasn't helping me anyway, I didn't bother trying to go back.
I got the device back to the "Warning!!" screen. Then turned the router back on and searched for how to do a factory reset of the device. I found a video on YouTube and followed it.
I pressed the Volume Down and Power buttons simultaneously, followed by letting go of the power button. That brought up a menu which contained several options, including an option to do a factory reset. I used the volume buttons to highlight that and pressed Power key. A second screen came up and I used the volume buttons and power button to select "Yes" to confirm the reset.
It appeared to have done a factory reset, rebooting eventually.
However, after that, when I tried to tap on the touch screen to move forward through the selections, the touch screen was still unresponsive!
So I brought back the "Warning!!" screen and ran the battery down until the screen was blank and it wouldn't start when I held the power key.
Then I charged it for about 20 minutes and rebooted it. I think when it came back it was on the Recovery menu. I think I did a second factory reset, but not 100% sure. It eventually rebooted after a lot longer than usual.
When it came up, it was saying battery was low. I tried to tap the OK button, but nothing happened. Behind the battery window was the first setting screen to set up the device for the first time after a factory reset. (I think selecting USA?)
I brought back the "Warning!!" screen and left it on overnight so that the battery would run down.
That was about 8 hours ago. When I woke up, I used clear tape to keep the power button pressed down, to ensure that the battery will continue to run down.
____________________________________________
What do I do next? How do I get the touch screen to start working again? It is not a hardware problem, unless mal-ware can break the hardware. The touchscreen had been working fine until this happened.
Should I take the tablet back to Best Buy where I bought it at least a year (maybe 2 years) ago? I don't know if it's still under warranty.
I have over 20 year of experience as a software developer, but not for Android. I am not very experienced with doing anything to hardware.
Should I try to fix it myself?
I have never rooted any Android device and I'm not sure what that means, either.
I've never re-installed the ______ ? (rom? image? Odin?)
I read on this and/or other forums that there's a way to replace something, but the instructions were beyond my level of understanding. I would need the procedures to be broken down into steps which don't assume too much about what I know.
I understand how to download a file to Windows, given a URL for it. I understand what a zip file is and how to extract it. I understand how to press hardware buttons and plug in cables, and do these steps in the order I'm told.
I don't understand what I'd use to get the downloaded whatever-they-are onto the tablet to replace whatever-the-other-thing-is so that the touchscreen works again.
As far as I know, Odin is a Norse god.
The only firmware updates I've ever done are the ones that the device does on it's own through Samsung's updates.
I'd deeply appreciate getting this device back since I have extremely limited funds and probably won't be able to buy a replacement.
Thank you,
Linda
Click to expand...
Click to collapse
Definitely sounds like malware. You have two choices that I see, either root and custom rom or flash back to stock. Since you are stock you'd just be overwriting your existing install. Read this thread and decide your course of action http://forum.xda-developers.com/showthread.php?t=2203309

Can't boot, restarts constantly

Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock

Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.

a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!

Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/

Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed

jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:

A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.

u12+ black screen after PIN unlock / Device unusable

Hi everyone, I'm throwing this out there because I've run out of ideas about what has just happened to my U12+ (64gb) today.
I woke up and used my phone as normal, caught up on Twitter and the news, the usual apps etc. nothing untoward. The same routine I've had with my phone for the past 18 months of owning it with zero issues. My handset is stock OS (Android 9) and so not rooted or anything like that. Virtually all the apps I use are standard issue from the Play Store, nothing really "out there" and I have BitDefender installed to look after security. Same setup I've had for over a year. The battery was around 35% so I plugged it into my wall charger while I went off to grab some breakfast. When I returned a couple of hours later the light on the handset was green, I unplugged the charger and attempted to unlock it with my fingerprint.
The phone asked for my PIN, no big deal so I entered it. Black screen. Tapped the power button again, it requested my PIN again, I entered and... black screen. Okay, I was a little bit concerned now. I held down the power button so the haptic buzz occurred, held for 10/20/30 seconds, a minute... nothing, no restart. Tap the power button and it asks me for my PIN again and shows yet another black screen. I held down Power + Volume Down but again, nothing and no restart.
I asked someone to call me, the screen came to life and I could take the call but each time I tried to pull down the system tray in order to try and reach Settings to restart it asked me for my PIN, I entered it = black screen. The call was unaffected.
I removed my SIM + microSD card tray = same deal as above.
The phone is clearly responsive in some way and the screen does display to ask for my PIN but I can't get into it in order to reboot it. Extremely worrying.
Does anyone have any advice? At the moment I am faced with the prospect of simply allowing the battery to run out so the phone shuts down naturally but that is going to take the best part of 2 days.
I'm really disappointed because I was planning another 1-2 years use for this handset as I just bought a 1TB microSD card which has been fine in the phone for weeks so I don't think that's the cause. It is also genuine SanDisk.
Any suggestions or advice? Thanks in advance.

Hello, I hope you have made a backup with google backup recently... This does not happen often on android, but sometimes the system could have a problem. You can try this go the bootloader with the power and volume buttons , after recovery.. after apply a wipe data/ factory reset.. is will make a factory reset of your phone except the sd card. You should by fine after that and profit again.

Thanks, I appreciate your reply.
At the moment I am running the battery down until the handset switches off naturally. When it comes back on I will try to launch the phone normally, if that doesn't work I'll run the battery down again and attempt to reach the bootloader.
My photos are backed up to the cloud, I may lose some text messages but I managed to transfer the majority of my 2FA over to another Android device bar one.
At the end of the day if it's a choice between wiping it or a bricked/unusable handset then I don't really have one. What a pain.

Magimix^ said:
Thanks, I appreciate your reply.
At the moment I am running the battery down until the handset switches off naturally. When it comes back on I will try to launch the phone normally, if that doesn't work I'll run the battery down again and attempt to reach the bootloader.
My photos are backed up to the cloud, I may lose some text messages but I managed to transfer the majority of my 2FA over to another Android device bar one.
At the end of the day if it's a choice between wiping it or a bricked/unusable handset then I don't really have one. What a pain.
Click to expand...
Click to collapse
At the moment I am running the battery down until the handset switches off naturally <----- why that??? Even on a bootloop or a black screen you can reset it hold the buttons power and the volume, you can go on the bootloader.

Max128 said:
At the moment I am running the battery down until the handset switches off naturally <----- why that??? Even on a bootloop or a black screen you can reset it hold the buttons power and the volume, you can go on the bootloader.
Click to expand...
Click to collapse
The first thing I tried to do was hold down the power button or the power button in tandem with the volume buttons but the handset won't restart. I tried loads of times holding it for different amounts of time and... nothing.
Trust me, I tried.
The only way I can get the device to switch off is by draining the battery. I'm almost at 20% so it shouldn't be too much longer.

Well I already got a black screen after flashing a module magisk.. I have holding the power button and the phone have restart no problem, same thing on bootloop. You need to be sure to hold the button correctly.

Max128 said:
You need to be sure to hold the button correctly.
Click to expand...
Click to collapse
Yeah, I'm certain I was holding the buttons correctly. I tried about 20 times using different combinations just to be sure but the device would not restart. The haptic shock buttons are one of my least favourite features of the u12+, it's got to be said.
Anyway, the phone ran out of battery about 15 minutes ago. I left it alone for few minutes and switched it back on. It allowed me back in and the device appears to be fully functional again. I can unlock by thumb print, face or PIN without issue.
Basically, it's fixed. My only concern is I have no idea what caused it or if it will happen again.
Thanks for offering help though, I appreciate it. I'm not sure if this thread can be closed/locked now? I'll look into that.
Cheers.

Yes.. i love the buttons too i never got a problem with this. Great if is fixed! Maybe make a factory reset the next time.
I am wondering if the new flagship have haptic buttons too.. htc will announce it Tuesday.

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.