[Q] [HELP] -Garmin-Asus A10 -Requesting for technical support - General Questions and Answers

Suspected problem: Bootloop
It all started when I connect my phone (Garmin-Asus A10 (v5.0.82 (updated with GarminAsusPhoneUpdater_Telenor_v2.0.3.exe of denmark))) on laptop through USB cable, the USB slot looks slightly damaged already upon looking at it, after connecting the expected to be happen is that the back-light will turn on, but what happen is that the phone has no response from it, I try to press the power button still no response, I removed the battery and bring it back and try to turn on again the logo appears (without vibrate which is supposed to be present in turning on my phone) then disappear after 7-10 secs.
It's already stock on the logo as I turn it on, the moment I pressed the power button the logo appears for about 7-10 secs then it disappear, also when I removed the battery and put it back the logo appears without pressing anything and disappear again after 7-10 secs.
I try to wipe the data through Volume Up + Volume Down + Power Button the ** WIPE USERDATA ** appears but then after a few secs it disappear again which is supposed to last for about a minutes.
And also I still can go to the **USB POLLING MODE ** through Volume Up + Power Button but seems like there is nothing to do with that thing.
I know it will be easy to fix this with the use of Garmin-Asus phone updater but it requires the phone storage which is so impossible to access at this point.
Hope you guys can help me with this, I badly need that phone.
----
Updates:
I can already open the phone and go to the home screen and menus... etc., but only when I close/cover the 1st metal/copper of the battery (back view (- to +))., but then I get an error saying that "The installed battery is not compatible with this device"
Upon doing this the phone is keep on rebooting, even if I already turn it off it keeps on turning on by itself, also I can't use any network at this point.
I already formatted the phone using master clear & **WIPE USERDATE** (Volume up + power button) still got the same problem.
And also updated with 006-B1243-00.update (The last .update file I used to update my phone (V5.0.82 DN)), upon rebooting after verifying the .update file it just blink twice then the update stops already at that point.
Updates 2:
Physically there is nothing wrong with the phone, I can still use the phone but as I mention already "only when I close/cover the 1st metal/copper of the battery (back view (- to +))." everything works fine except for the error "The installed battery is not compatible with this device" the red with "X" battery (Screenshot-1434948958913)
Also I notice something from my storage the "System Volume Information" (Screenshot-1434949331146, Screenshot-1434949336619, & Screenshot-1434949345666), I'm pretty sure that I haven't seen yet that before, I deleted the folder still it comes back.
Also once I connected my garmin phone to my computer the USB connected thing (Screenshot-1434949876071) don't disappear just until I restarted the phone.
Thanks in Advance.

Related

[Completed] Sony Xperia Tablet S SGPT1211 not responding to reset/power comands

Hello,
I think I might be at the end of the road with my tablet. I've never rooted it or tampered with it in an way, however yesterday it locked up so I did the usual soft reset (hold power and vol+ for 10 seconds) I then turned it back on and the sony logo popped up, but there it just hung. If I press and hold the power button it switches off, a brief press on the power button brings it back on in the same state. So I go Googling, including looking at threads on this site, all seemed to advise to try to get the Android recovery menu up. on the Sony this is done by holding the power and vol+ and then releasing the power button (only) when the son logo appears (this process to be started when the tablet is off) so I did this, and no response at all. Worse than that, where it would turn on and instantly hang, it now doesn't turn on at all. Hooking it up to my PC I can see the device in device manager, but it tells me my usb device has malfunctioned.
At the moment, my thoughts are to open it up, to:
1. Check that the power/volume buttons aren't stuck in some way (preventing the boot command being given correctly)
2. Remove and resolder if necessary internal battery to force a power cycle.
3. Bin it and get something new (it is 2.5yrs old so no big loss i suppose)
Any ideas where to look or similar experiences?
Thanks
Hi
Please post in Tablet S Q/A section after signing up.You will get better help from your peers.
http://forum.xda-developers.com/sony-tablet-s/help
Good day !

Phone unresponsive, even to volume up + power button combination

Hello folks,
* mistake in title: I mean volume down + power
I'm having some trouble with my Samsung Galaxy S6 not responding.
I can't remember which Android version it has; it's whatever it came with in 2015, so it's Marshmallow or earlier. The phone is not rooted, not modified. I think that USB debugging is enabled.
The phone is showing a slowly blinking blue notification light.
It does not respond to pressing any of the keys, does not respond to soft reset (volume down + power), does not respond to hard reset (volume up + power + home).
When plugged into a computer via USB cable the computer does not give the option to connect to the phone.
Running "adb devices" at the (Ubuntu) command line with phone connected returns blank list of devices.
What are my options? Is there some other reset option I haven't yet tried?
Did u figure it out? I am having the same problem, thinking of changing the motherboard.
Same problem here, I wake up and the phone was dead, without touching it
It has RR OS 6.2 Android 8.1, no notification light, just nothing... Dead
This is weird, it's happening to me too, the same days...
If you find something about or see other S6 users with the same problem comment here
It is stupid answer, but leave phone for discharging battery, charge for a 15%, maybe (for quick discharge, if phone gets stuck again), and try to turn on. If it's doesn't helps, you can go to recovery and do reset.

Oneplus 8T bricked after dying last night

Was watching youtube videos last night before my phone died, now I can't get it to start boot into the OS. Not sure if this is relevant but my power button had been a little finnicky- rather maybe not the power button itself because it doesn't feel stuck or anything at all but I noticed that it would take an extra second or two after pressing the power button to get into my lock screen. I never really paid attention because it only happened once in a while and I would just restart my phone and be done with it. However I can't even get into the lock screen or anything now.
After my phone died last night I plugged it in right away and came back a while later to turn it on. I tried turning it on but noticed my phone just kept rebooting. It's still repeatedly rebooting and I can only get in the fastboot menu by holding down both volume buttons when rebooting. I get the options power off- which just reboots it after a while, start - which just reboots the phone, restart boot loader- which literally takes me back to the same menu, recovery mode- just reboots and show barcode which shows the barcode at the bottom of the menu.
I've tried downloading the qualcomm driver and trying to get into EDL mode but don't see it on my pc or msmtool, i'm also not even sure if i'm trying to get into EDL mode correctly. I've tried disable Driver signature Enforcement and then redownloading the qualcomm driver but still no luck. I don't know what else I should try. Someone please help me out, i'm pissed this happened just because my phone died, about to have ptsd whenever my phone is at 5% fml.
Also after seeing the 1+ logo and powered by android on the bottom, sometimes I would see like a line of color, which I would assume is text not being rendered all the way, fade out and then the phone shuts down and reboots itself.
yellownese said:
Was watching youtube videos last night before my phone died, now I can't get it to start boot into the OS. Not sure if this is relevant but my power button had been a little finnicky- rather maybe not the power button itself because it doesn't feel stuck or anything at all but I noticed that it would take an extra second or two after pressing the power button to get into my lock screen. I never really paid attention because it only happened once in a while and I would just restart my phone and be done with it. However I can't even get into the lock screen or anything now.
After my phone died last night I plugged it in right away and came back a while later to turn it on. I tried turning it on but noticed my phone just kept rebooting. It's still repeatedly rebooting and I can only get in the fastboot menu by holding down both volume buttons when rebooting. I get the options power off- which just reboots it after a while, start - which just reboots the phone, restart boot loader- which literally takes me back to the same menu, recovery mode- just reboots and show barcode which shows the barcode at the bottom of the menu.
I've tried downloading the qualcomm driver and trying to get into EDL mode but don't see it on my pc or msmtool, i'm also not even sure if i'm trying to get into EDL mode correctly. I've tried disable Driver signature Enforcement and then redownloading the qualcomm driver but still no luck. I don't know what else I should try. Someone please help me out, i'm pissed this happened just because my phone died, about to have ptsd whenever my phone is at 5% fml.
Also after seeing the 1+ logo and powered by android on the bottom, sometimes I would see like a line of color, which I would assume is text not being rendered all the way, fade out and then the phone shuts down and reboots itself.
Click to expand...
Click to collapse
Which OOS build are you on? And your device is unlocked or not?
Getting into EDL mode is tricky. Power off device completely. With the device powered off, hold down volume up and volume up at the same time, keep them pressed all the time, and during that time plug into PC (phone all the time powered off). Still hold both of the buttons. By the time you plug into PC, you should be in EDL mode, BUT it only lasts about 10 seconds. I mean you have to click start in this 10 seconds time bracket, other way phone exits EDL itself. After you click start, you can release button, obviously

Question Boot issue - not powering on and unable to reach recovery mode

Hi,
I own an S22 ultra Exyonos 128gb and i'm having severe issues.
I was using the device (chrome) and it suddenly froze, and powered off. I powered back on, and it almost immediately powered off again. Since then ive been unable to power on.
I've tried force restarting, plugging into a PC with a usb-c cable and holding down volume up and power for 5-10 secs, but nothing happens. The phone simply gets stuck on the Samsung logo screen, sometimes the basic "Samsung" screen, and sometimes the "Samsung S22 ultra 5g secured by knox" screen.
Also when trying to charge with a cable, no animation to show charging pops up, ive not tried wireless charging yet.
Any idea how I can boot into recovery mode
If vol up + power doesnt work?
Thanks in advance
Can you boot into download mode (cable unplugged and device off press Vol Up and Down together and plug in cable) ? What is the screen showing after you agree to enter download mode ?
Is your device rooted or else modified in any way ? Did you do anything special prior to this behaviour ?
Hi s3axel,
thanks for replying.
yes, I can access download mode, it comes up with a Warning page saying "A custom OS can cause critical problems in phone and installed application. if you want to download a custom OS, press the volume up key"
No, the phone isn't rooted.
Nothing out of the ordinary was being done, I was just on google chrome browsing Reddit, when all of a sudden it froze, wouldn't respond to touch or power/wake button presses, and then crashed, and hasn't been able to boot u since.
I did have issues with the phone previously randomly crashing and then restarting and thought it could be malware. I booted into safe mode to see if it occurred again and if so an app could be the cause, but it didn't. I then booted normally and ran a virus scan with Samsungs in-built anti-virus software and then again with Malwarebytes, but nothing was found. it happened a few more times before stopping after a software update, so I thought nothing more of the issue until now.

Soft Bricked S7? Recovery Mode Keeps Getting Interrupted

A few weeks after switching from my old S7 Edge to my old S8 (which I did about a month ago), I tried turning on my S7 Edge only for it to enter recovery mode. Since the power button is broken, I figured I would have to reboot it out of recovery mode using ADB on my PC. When I switched my S7 on again the next day to enter recovery mode and connect it to my PC, I got to the "installing updates" screen that precedes recovery mode. This screen showed up for about three seconds before my screen went black. After 10 seconds my phone rebooted and went back to the "installing updates" screen, went black, rebooted, and so on.
I think my phone might be out of battery so when it charges a little bit, it automatically tries to enter recovery mode, which uses up all the power in the battery and causes it to die, restarting the cycle. Is there any way I can stop my phone from automatically turning on when it is plugged in so that it can charge enough to actually make it to recovery mode?
Thanks!
For some reason, the bootloader on this device remembers if you were last booted into recovery, and will return to it on the next poweron, so - without a working power button - there aren't very many options.
The power button could be an easy fix - depending on if it's stuck or damaged. The outer parts of the volume and power buttons on this device are interchangable, so that could make all boot modes possible again. Opening your device may sound scary, but - with good research and some patience - you will find it is certainly doable using basic tools. And if you don't want to do it yourself, a local repair shop would probably do it for cheap as well.
As far is I know, there isn't any usable software fix without a working power button.

Categories

Resources