Related
i have a a100 with the latest flexreaper rom installed and im stuck with a pretty serious issue:
a couple of days ago the tab was acting real slow and sluggish and getting bad battery life didnt think nothing of it so i just rebooted a couple times and left it alone . all was good untill the battery hit 10% and i plugged it up using the factory ac adapter. the next day (maybe 6-7 hours later) i went to turn it on and nothing no vibrate no screen flash nothing; other than the power button turning blue as i pressed it and it would stay on for a couple hours but still no other response from the tablet.
im at my wits end on what could be wrong and now i got my wife with her foot on my neck till i get it fixed. can anyone help me?
ive tried to do a hard reset with the reset button tried to boot into recovery /bootloader no dice
(also my home button flashed a couple time i pressed the power button) dont know if its relevant but wanna get as much info out as possible
wondering if anyone can help me...
frenize said:
wondering if anyone can help me...
Click to expand...
Click to collapse
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
pio_masaki said:
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
frenize said:
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
Click to expand...
Click to collapse
Yeah I know that sound it means USB connected but error for some reason. Its been shown if this thing dies all the way down it wont read the battery correctly and probably needs to be sent in. Before that I personally would unplug it open it up and remove the battery for awhile, maybe an hour then put it back and plug it in. But thats me, not the advice I'm giving. If you have warantee on it use that.
The batteries on a lot of devices and laptops etc have something of a fail safe, if the voltage drops below a certain point it trips to prevent cell damage, however it renders the battery useless.
I haven't searched out much past that if a reset is possible by us, but it seems the pack is trash after or needs sent in.
Since this is a sealed unit you void warranty opening it (well unlocking the boot loader did too) so you can't send it in for repairs without paying for it.
I hope someone can jump in and help figure this out, and prove me wrong.
Tapatalked from my Galaxy S II.
Weird, This exact same thing happened to me. Used it in the morning and now after work it won't turn on. I had already tried disconnecting the battery, but hadn't thought to leave it disconnected for an hour. My tablet has been running the leaked ICS since it came out and The last factory reset it had was about a month ago. It was working fine up until this. The power button seems to be responding correctly, the issue is that after the LEDs light up, there is no vibration or display. I hope someone can help us with this issue.
EDIT:
It won't connect in ADB mode. It will only appear on my computer as an APX device and since there is no vibration I am unable to boot into fastboot. Any help or suggestions? All the threads I have found have involved booting into fastboot.
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
same thing here.
max69power said:
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
Click to expand...
Click to collapse
I have been using ICS the leaked one, and last night I was goint to check my email and it did not turn on, I though the battery died. I plugged to the charger and this morning I tried to turning it on but it failed. I did the reset pin but nothing. I connected to the computer and it was recognized as a APX device and installed a driver ACER Picasso USB recover but i cant access anything. I am a nob. Thanks
A100 blackscreen
i am also having this problem. last night. just a black screen it turns on or the home button dose but nothing comes up on the screen. :crying: Help!!!!!!
Has anyone tried holding the power button for a while? Laptops do this too, if someone felt ventures, try taking the battery out and hold the power button. No promises, might work.
sent from my ICONia
same here
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
If the screen is blank while powered on its in failsafe mode, in other words is bricked, has to go to Acer.
Tapatalked from my Galaxy S II.
This just happened to me a few weeks ago as well. If you are still under warranty send it in to Acer, thats what I did. I just got an email saying they had fixed it and were sending it back for free!!
At the time I was on the 9/02 JB build. I wonder if this issue is caused by faulty hardware or if it is an issue that was made by rooting and unlocking it? I don't know enough about this stuff to answer that though, but it does make me think whether I should root/unlock it when I get it back or leave it stock.
Also thanks Pio_masaki for helping me a few weeks back wasn't sure if I was even going to send it in until you said they most likely won't be able to tell.
I highly doubt they even CARE when sending these in. They will void for physical damage most likely.
tshm55 said:
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
Click to expand...
Click to collapse
Ohmygod,
Same here, but it's 3 years ago. Sorry for digging the topic. Still no hope? I still keep the tablet and have just buy another refurbished mainboard to replace but still no vibrate and blacksreen still there.
Hey there,
Im a newb here, and this is my first thread, but whatever.
It all started a few months ago.
Several weeks after I rooted my play, and flashed cm7, with doom kernal, my play just suddenly didn't turn on. (Like, turned it off for the night, but refused to turn on in the day again) . However, after I took out the battery and charged it for 10 mins before plugging the battery back in and turning it on again, it worked. This happened intermittently, and through the 12 months I had with this phone, this has happened multiple times, albeit rarely. Every time it happened, it wouldn't turn on, no led when plugged in the charger, no nothing. Its like a dead brick. Plugged it into the computer and it says "QHSUSB_DLOAD". It would work after I charge it without the battery tho. LOL. - weird. (Something like this, link here
However, yesterday, 31/1/2013, my luck basically ran out. The same thing happened again, with "QHSUSB_DLOAD" showing up and all, but my above method didn't work. And so, I'm stuck with a dead brick.
Basically, my xperia play is unresponsive. Plugged it into the computer and it shows "QHSUSB_DLOAD" I think it stands for Qualcomm High Speed USB Download mode. Today, following this link I just randomly plugged in my phone while holding the back button, with flashtool open in the background. Its some miracle, like, my pc suddenly detected it as an unknown device, and flashtool did some kind of thing, not sure, forgot to screen shot but i think it goes along the lines of "installftfkit". After that, my phone booted.
However, because I wanted to plug in my sim card, i rebooted it, and this time it wouldn't turn on. I tried replicating the results, and all i got wasn't "unknown device" but "QHSUSB_DLOAD".
And there you have it, Xperia Play stuck at "QHSUSB_DLOAD" permanently after several times of intermittent incidents of that happening. It may be hardware failure, which explains the intermittent incidents.
But Im still kind of curious. What causes "QHSUSB_DLOAD"? What component fails that would cause the PC to read it as "QHSUSB_DLOAD"?
Its a dead brick, but I am still trying to revive it. I installed qpst and the QHSUSB_DLOAD drivers. QPST configuration reads a phone in download mode(image 1), QPST software download seems to be able to flash a phone and boot image(image 2). But it needs a hex file and stuff. (Not sure bout that)
Is it easy to get a boot image thing for xperia play? Can i flash it using QPST and make my phone work again?
Thanks for your help guys! Really appreciate it!
Mr_Pistachios said:
Hey there,
Im a newb here, and this is my first thread, but whatever.
It all started a few months ago.
Several weeks after I rooted my play, and flashed cm7, with doom kernal, my play just suddenly didn't turn on. (Like, turned it off for the night, but refused to turn on in the day again) . However, after I took out the battery and charged it for 10 mins before plugging the battery back in and turning it on again, it worked. This happened intermittently, and through the 12 months I had with this phone, this has happened multiple times, albeit rarely. Every time it happened, it wouldn't turn on, no led when plugged in the charger, no nothing. Its like a dead brick. Plugged it into the computer and it says "QHSUSB_DLOAD". It would work after I charge it without the battery tho. LOL. - weird. (Something like this, link here
However, yesterday, 31/1/2013, my luck basically ran out. The same thing happened again, with "QHSUSB_DLOAD" showing up and all, but my above method didn't work. And so, I'm stuck with a dead brick.
Basically, my xperia play is unresponsive. Plugged it into the computer and it shows "QHSUSB_DLOAD" I think it stands for Qualcomm High Speed USB Download mode. Today, following this link I just randomly plugged in my phone while holding the back button, with flashtool open in the background. Its some miracle, like, my pc suddenly detected it as an unknown device, and flashtool did some kind of thing, not sure, forgot to screen shot but i think it goes along the lines of "installftfkit". After that, my phone booted.
However, because I wanted to plug in my sim card, i rebooted it, and this time it wouldn't turn on. I tried replicating the results, and all i got wasn't "unknown device" but "QHSUSB_DLOAD".
And there you have it, Xperia Play stuck at "QHSUSB_DLOAD" permanently after several times of intermittent incidents of that happening. It may be hardware failure, which explains the intermittent incidents.
But Im still kind of curious. What causes "QHSUSB_DLOAD"? What component fails that would cause the PC to read it as "QHSUSB_DLOAD"?
Its a dead brick, but I am still trying to revive it. I installed qpst and the QHSUSB_DLOAD drivers. QPST configuration reads a phone in download mode(image 1), QPST software download seems to be able to flash a phone and boot image(image 2). But it needs a hex file and stuff. (Not sure bout that)
Is it easy to get a boot image thing for xperia play? Can i flash it using QPST and make my phone work again?
Thanks for your help guys! Really appreciate it!
Click to expand...
Click to collapse
Correct me if Im wrong...but Im guessing you tried Flashtool and it doesn't work ?
Also , are you familiar with using fastboot?
another Xperia Play Problem
Hi I am a noob also.
I am having a similar problem. Today I was trying to install the wifi module since it wasn't installed on the gin2Jellybean rom, i tried to flash the phone using the Flashtool (turned the cellphone off and pluged it in again while holding the back button) then the window disappeared and nothing happened. So I tried again, but first I took out the battery and put it in again and tried to flash again and now nothing is happening, Doesn't turn on, Flashtool doesn't do anything and when I try plugging it the laptop does the sound of an unrecognized device. The phone doesn't vibrate or anything when I press the power button.
Just realized that I tried flashing my cell phone using the x10 BLRelock.ftf crap.. is there anyway I can fix this?
Please Help.
Thank you.
216Monster said:
Correct me if Im wrong...but Im guessing you tried Flashtool and it doesn't work ?
Also , are you familiar with using fastboot?
Click to expand...
Click to collapse
Flashtool and fastboot doesn't detect my phone. So yea .
Mr_Pistachios said:
Flashtool and fastboot doesn't detect my phone. So yea .
Click to expand...
Click to collapse
Are the fast boot drivers installed ? Is your boot loader unlocked ?
Sent from my ARCHOS 101G9 using xda premium
216Monster said:
Are the fast boot drivers installed ? Is your boot loader unlocked ?
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
LOL WTS.
As I said, its totally intermittent and random. I tried plugging it into the computer today, and this time a red led was flashing. I let it charge up a little, and there i had it, booted up perfectly normally.
Maybe the plug is becoming dusty or whatever, resulting in the detection being very intermittent? It happens on and off.
When the phone booted up, I noticed the battery level being very low (2%) maybe it needed some charging? Maybe the battery's screwed?
Its really weird.
And yea, fast boot drivers are installed, and boot loaders are unlocked (If not cm10 wouldn't have been installed lol)
Gonna keep you guys posted and see if it goes dead after restarting. Gonna restart after it charges up to 40%.
(I need to restart cos I have to plug in my sim and memory card)
Mr_Pistachios said:
LOL WTS.
As I said, its totally intermittent and random. I tried plugging it into the computer today, and this time a red led was flashing. I let it charge up a little, and there i had it, booted up perfectly normally.
Maybe the plug is becoming dusty or whatever, resulting in the detection being very intermittent? It happens on and off.
When the phone booted up, I noticed the battery level being very low (2%) maybe it needed some charging? Maybe the battery's screwed?
Its really weird.
And yea, fast boot drivers are installed, and boot loaders are unlocked (If not cm10 wouldn't have been installed lol)
Gonna keep you guys posted and see if it goes dead after restarting. Gonna restart after it charges up to 40%.
(I need to restart cos I have to plug in my sim and memory card)
Click to expand...
Click to collapse
Well, I restarted and it worked.
My theory is this: Phone ran out of batt one day. Plug is loose and dusty. Computer couldn't detect it properly, charger couldn't charge my phone properly (contacts are rusty or whatever shyt) and therefore phone couldn't on.
Don't know why my computer detected it as QHSUSB_DLOAD multiple times throught the 1 month tho.
Could a dirty plug cause that?
During that 1 month there was no response on the computer, thought it was bricked lol.
Anyways, I will keep you guys posted if this happens again, thanks for your help guys!
Imma keep this thread open since this is intermittent.
I'll only close it after 2 months.
Mr_Pistachios said:
Well, I restarted and it worked.
My theory is this: Phone ran out of batt one day. Plug is loose and dusty. Computer couldn't detect it properly, charger couldn't charge my phone properly (contacts are rusty or whatever shyt) and therefore phone couldn't on.
Don't know why my computer detected it as QHSUSB_DLOAD multiple times throught the 1 month tho.
Could a dirty plug cause that?
During that 1 month there was no response on the computer, thought it was bricked lol.
Anyways, I will keep you guys posted if this happens again, thanks for your help guys!
Imma keep this thread open since this is intermittent.
I'll only close it after 2 months.
Click to expand...
Click to collapse
zzz. It couldn't boot up again. This time no QHSUSB_DLOAD, no nothing on the computer. 0 detection 0_0
Mr_Pistachios said:
zzz. It couldn't boot up again. This time no QHSUSB_DLOAD, no nothing on the computer. 0 detection 0_0
Click to expand...
Click to collapse
My phone is just driving me batshyt insane -.-
I tried pressing the power button again and it worked, without plugging in the charger nor the computer.
It's intermittent, and now im afraid to turn it off 0_0
Mr_Pistachios said:
My phone is just driving me batshyt insane -.-
I tried pressing the power button again and it worked, without plugging in the charger nor the computer.
It's intermittent, and now im afraid to turn it off 0_0
Click to expand...
Click to collapse
FML. Hands were itchy and wanted to see what would happen if I turned my phone off.
Now it can't turn back on, with the computer only detecting QHSUSB_DLOAD.
Mr_Pistachios said:
FML. Hands were itchy and wanted to see what would happen if I turned my phone off.
Now it can't turn back on, with the computer only detecting QHSUSB_DLOAD.
Click to expand...
Click to collapse
Turned on my phone after 10+ tries.
What I did:
1) Plugged out battery, held power button
2)Without releasing the power button, insert the battery.
Repeat until phone turns on.
Moral of story: Persistence pays off. Nah jk.
Made sure to on my phone with the sim card in this time
Never gonna off my phone ever again (Hope it doesn't run out of batt LOL)
One thing to note is this really weird fluctuation in my phone's battery levels. Maybe my battery is going nuts? Attached is the screenshot.
Made sure to on my phone with the sim card in this time
The epic fluctuation may provide clues as to why my phone's behaving like so.
As you can see from the third dip, I was charging my phone. And then after switching it off, it wouldn't turn on. After a day, and countless times of trying to wake it up, you can see that the battery level has dropped sharply. Weird.
The first dip happened a few days ago(not able to turn on) on 1st Feb. The second dip happened on the 4th, while the third happened on the 5th, today These drops in battery levels happened when my phone couldn't turn on.
Qhsusb_dload
I am sorry to say that my problem is still the same every time I plug my phone it is shown as QHSUSB_DLOAD.
I just need to find a driver for it.
PS my phone never turned on after the brick.
Can someone send me a link to the driver and instructions if hard to install.
Thank you.
extrem3hunt said:
I am sorry to say that my problem is still the same every time I plug my phone it is shown as QHSUSB_DLOAD.
I just need to find a driver for it.
PS my phone never turned on after the brick.
Can someone send me a link to the driver and instructions if hard to install.
Thank you.
Click to expand...
Click to collapse
Does plugging the phone into the computer while holding the back button work?
Mr_Pistachios said:
Does plugging the phone into the computer while holding the back button work?
Click to expand...
Click to collapse
Nope every time I connect it is detected as QHSUSB_DLOAD and it tries to find a driver and fails.
extrem3hunt said:
Nope every time I connect it is detected as QHSUSB_DLOAD and it tries to find a driver and fails.
Click to expand...
Click to collapse
Even if it finds the driver, it wouldn't help you, cos QHSUSB_DLOAD means that the phone can't find the rom, and kernel or whatever. (I think) Its like a computer without an operating system. QHSUSB_DLOAD = Qualcomm Highspeed USB Download Mode, which means its waiting for the manufacturer to flash the rom and shyt, and therefore, your phone is bricked. (Dead brick, i think?)
For me, i think there's something wrong with the connections in my motherboard, resulting in the phone not being able to find the rom and stuff.
Maybe there's no hope for you.........
In short, I think your phone's bricked forever.... Most probably.
any fix bricked play
Hi,
I am in the same boat. I get the QSHUSB Dload error and I cant get the phone into flash mode. Its basically dead, as the others have mentioned. Anyone get a fix for this thanks
Tommy
---------- Post added at 04:15 PM ---------- Previous post was at 04:06 PM ----------
extrem3hunt said:
Nope every time I connect it is detected as QHSUSB_DLOAD and it tries to find a driver and fails.
Click to expand...
Click to collapse
Hi, could you fix it in the end, I have the same problem...looks like I may need a new play after only 1 week lol : (
QSHUSB_Dload Fix
tommyforest123 said:
Hi,
I am in the same boat. I get the QSHUSB Dload error and I cant get the phone into flash mode. Its basically dead, as the others have mentioned. Anyone get a fix for this thanks
Tommy
---------- Post added at 04:15 PM ---------- Previous post was at 04:06 PM ----------
Hi, could you fix it in the end, I have the same problem...looks like I may need a new play after only 1 week lol : (
Click to expand...
Click to collapse
Hi, I have fixed my HARD bricked phone with the help of Alejandrissimo, contact him and tell him about your problem and he fix your phone online.You will need to know some basic knowledge of electronics and you will require a piece of wire. This is where you contact him.
unlock-bootloader(dot)com/contact/
extrem3hunt said:
Hi, I have fixed my HARD bricked phone with the help of Alejandrissimo, contact him and tell him about your problem and he fix your phone online.You will need to know some basic knowledge of electronics and you will require a piece of wire. This is where you contact him.
unlock-bootloader(dot)com/contact/
Click to expand...
Click to collapse
Well, okay, imma give it a try, tnks.
Before flashing your "bricked" device, try this!
Mr_Pistachios said:
Turned on my phone after 10+ tries.
What I did:
1) Plugged out battery, held power button
2)Without releasing the power button, insert the battery.
Repeat until phone turns on.
Moral of story: Persistence pays off. Nah jk.
Click to expand...
Click to collapse
YOU SAVED ME! We have an Xperia Play at work and it wouldn't boot. Plugged it in USB and the HS-USB QDLoader 9008 Device came up. I read your post, did the power+battery thing 8 times, and it magically came back to life!
I wouldn't believe it if someone told me, but for some reason this seams to work. removing the battery and plugging it back in did not work for me, but holding down the power button did the trick.
:good::victory:
proteusgr said:
YOU SAVED ME! We have an Xperia Play at work and it wouldn't boot. Plugged it in USB and the HS-USB QDLoader 9008 Device came up. I read your post, did the power+battery thing 8 times, and it magically came back to life!
I wouldn't believe it if someone told me, but for some reason this seams to work. removing the battery and plugging it back in did not work for me, but holding down the power button did the trick.
:good::victory:
Click to expand...
Click to collapse
HAHAHAHA LOL.
Glad it worked out for you
My guess is that there's something loose inside, and repeatedly trying to do that may help.
I think it's something to do with Sony's build quality, or maybe because the phone sustained hard knocks and stuff. (Probably just wear and tear)
Aledranssimo didn't reply me, so yea. T.T
This issue is probably an intermittent one I guess. I've since moved on and gotten a new phone (Lumia 520)
Hey everyone,
So, I got a new Xperia XA1 Ultra (G3223) through a trade running stock Android 7.0. Checked everything and initially it looked fine.
Over the last few days, things have been acting weird. Every time I start the device, it gives me a blank (black) screen with a blinking white notification light - it doesn't even show me the boot screen at times when it boots. Just yesterday, I got it to boot by pressing VOLUME UP + POWER after being in that state - but, that's not normal. Does anyone know why in the world my phone does that?
Furthermore, when using the Sony charger that came with the device, it takes over 6 hours to charge and doesn't even show the charging sign while charging. Could this be an Android 7.0 bug or is something seriously wrong with my phone? Only one time since I got it, did I get it to charge normal with the charging sign and everything; it actually charged quite rapidly at that point.
Any help would be appreciated with this, guys, because I'm at a loss. I do want to mention that the device doesn't seem to be recognized by the computer, so I'm not even sure that the cable is original.
vince.lupe said:
Furthermore, when using the Sony charger that came with the device, it takes over 6 hours to charge and doesn't even show the charging sign while charging. Could this be an Android 7.0 bug or is something seriously wrong with my phone? Only one time since I got it, did I get it to charge normal with the charging sign and everything; it actually charged quite rapidly at that point.
Any help would be appreciated with this, guys, because I'm at a loss. I do want to mention that the device doesn't seem to be recognized by the computer, so I'm not even sure that the cable is original.
Click to expand...
Click to collapse
Try a new cable and/or charger. (I found I had a bad charger once)
Since you had computer issues, I'd start with the cable. Also check the charging port on the phone for debris/damage.
avg2424 said:
Try a new cable and/or charger./QUOTE]
Okay, I'll do that - but, do you have any idea regarding the blank screen issue, my friend?
Click to expand...
Click to collapse
vince.lupe said:
Okay, I'll do that - but, do you have any idea regarding the blank screen issue, my friend?
Click to expand...
Click to collapse
How is your phone turning on? Power button or inserting the USB cable?
Only thing I can think of is perhaps a stuck volume key placing the phone into recovery or flash mode.
Try turning on the phone with no USB cable attached. Before you turn it on, press the volume keys a few times to make sure they aren't stuck and then power on.
avg2424 said:
How is your phone turning on? Power button or inserting the USB cable?
Only thing I can think of is perhaps a stuck volume key placing the phone into recovery or flash mode.
Try turning on the phone with no USB cable attached. Before you turn it on, press the volume keys a few times to make sure they aren't stuck and then power on.
Click to expand...
Click to collapse
The thing is that it's weird.... For one, sometimes when I use the touch reset/turn off button, it takes at least two minutes to reset, or it doesn't even reset. Then, when I turn the phone on while it's off, the phone sometimes enters into this weird state with the flashing white notification light. I never power on the phone via USB cable, so I don't know, really. Yesterday, I shut the phone off to test it, plugged the phone in to charge it, it wouldn't charge while off, but then hit power on, and then it wouldn't turn on, so I used VOLUME UP + POWER, and then it turned on just fine.
Hi
Happened also to be with my older Xperia J.
Backup your phone (cause you'll lose your data), connect it to a PC (or Mac) and install Xperia companion, then select "repair phone" or something similar (I know the written in Italian version ).
Wait and it will be all fine.
Regards
Faby:highfive:
vince.lupe said:
The thing is that it's weird.... For one, sometimes when I use the touch reset/turn off button, it takes at least two minutes to reset, or it doesn't even reset. Then, when I turn the phone on while it's off, the phone sometimes enters into this weird state with the flashing white notification light. I never power on the phone via USB cable, so I don't know, really. Yesterday, I shut the phone off to test it, plugged the phone in to charge it, it wouldn't charge while off, but then hit power on, and then it wouldn't turn on, so I used VOLUME UP + POWER, and then it turned on just fine.
Click to expand...
Click to collapse
faby GT said:
Hi
Happened also to be with my older Xperia J.
Backup your phone (cause you'll lose your data), connect it to a PC (or Mac) and install Xperia companion, then select "repair phone" or something similar (I know the written in Italian version ).
Wait and it will be all fine.
Regards
Faby:highfive:
Click to expand...
Click to collapse
Okay, let me see if I can get it to connect to the computer, and then I'll let you know if I have progress.
I have the same slow charging problem on my xperia xa1 ultra. you could solve it?
Hi,
I'm wondering if there's anyone else who is facing this problem or I'm just unlucky.
On last Sunday, when I was listening to YouTube Music at a low battery (around 15%), after a while the phone shut itself off. I guess it was just the phone ran out of battery so I tried to charge it. But the moment I plugged in the charger, the hidden emergency flash light in the front turned on (the one on top right). When the phone successfully booted up, an application called CQATest appeared with a notification. The phone won't charge and take SIM card anymore since then.
I've done some research and tried many methods to fix it, including reboot in the recovery, factory reset, using adb to change boot mode, reflash the rom, disabling the CQATest app. None of them could solve my problem. Disabling the CQATest app does let me to have signal again, but I still cannot get the phone charge. It shows Turbo Power connected, but not charging.
Is there anybody facing the same issue, or even better, have a solution?
Thank you.
Update: I found a solution for this. I put my phone to fastboot mode and charge it from there, overnight. Next morning, it's working normal again.
You can always try a custom ROM. And make sure to format every partition in TWRP before - format, not just wipe.
If that works you can try other stuff. If not you have a hardware issue is guess and only a phone repair could fix that.
PS: try a different charger. If it's only not charging it might be an issue there. And have you tried to charge it while the device is shut down?
Artim_96 said:
You can always try a custom ROM. And make sure to format every partition in TWRP before - format, not just wipe.
If that works you can try other stuff. If not you have a hardware issue is guess and only a phone repair could fix that.
PS: try a different charger. If it's only not charging it might be an issue there. And have you tried to charge it while the device is shut down?
Click to expand...
Click to collapse
Thank you for your reply. Yes I did try another charger. However I'm using a Qualcomm qualified charger so I don't think that's an issue. I brought it to UbreakIfix and they told me it's a motherboard problem so the only way to fix it is to change the motherboard. It'll cost a phone to do that. I'm just wandering if there's any body else who is having the same issue. Because my problem appeared out of no where.
That's normal. Hardware problems often appear out of nowhere all the sudden. And it's always hard the really on them down to a source.
And yes, repairs for not typical phones are always expensive. On my first Z Play the screen cracked. Seeing the price of a repair and realising I could get an unused Z2 Play for the same money you can guess what I did. Can't say I regret it too much.
Hi,
My Galaxy S9 (Exynos) just stopped charging today. It had no problem this morning, but when I tried recharging in the evening, it won't charge at all. Connecting it to PC won't work either. But OTG works just fine. I am wondering if it is a hardware or software problem.
I unfortunately do not own a wireless charger so its almost dead now. If I could confirm it's a hardware problem, I would just buy another charging board but I would like to confirm it first before buying. Is this a common problem in s9? Could there be any issue on the software level?
Any help is appreciated. Thank you.
seijidinzuala said:
Hi,
My Galaxy S9 (Exynos) just stopped charging today. It had no problem this morning, but when I tried recharging in the evening, it won't charge at all. Connecting it to PC won't work either. But OTG works just fine. I am wondering if it is a hardware or software problem.
I unfortunately do not own a wireless charger so its almost dead now. If I could confirm it's a hardware problem, I would just buy another charging board but I would like to confirm it first before buying. Is this a common problem in s9? Could there be any issue on the software level?
Any help is appreciated. Thank you.
Click to expand...
Click to collapse
the only things that come to mind that could cause this is the board being bad or the kernel being corrupt. If you can OTG, you should be able to Odin with it (key word there is should), if you can Odin with it, just flash the HOME_CSC firmware files and if it charges afterwards, then you know it was the kernel. If it still doesnt work, bad charging port/card
Thank you for your response, but as I have said, my PC cannot charge it or even detect it at all. OTG is the only thing that works. Maybe the phone is blocking any data transfer when power come along on the usb port? Am I making any sense?
seijidinzuala said:
Thank you for your response, but as I have said, my PC cannot charge it or even detect it at all. OTG is the only thing that works. Maybe the phone is blocking any data transfer when power come along on the usb port? Am I making any sense?
Click to expand...
Click to collapse
you are making sense, but if the OTG works, then data transfer should be working too. Can you boot to DL mode?
youdoofus said:
the only things that come to mind that could cause this is the board being bad or the kernel being corrupt. If you can OTG, you should be able to Odin with it (key word there is should), if you can Odin with it, just flash the HOME_CSC firmware files and if it charges afterwards, then you know it was the kernel. If it still doesnt work, bad charging port/card
Click to expand...
Click to collapse
youdoofus said:
you are making sense, but if the OTG works, then data transfer should be working too. Can you boot to DL mode?
Click to expand...
Click to collapse
Yes I can boot to dl mode and recovery too. When I connect it to PC, the PC don't even make any sound (you know that usb connect sound).
youdoofus said:
you are making sense, but if the OTG works, then data transfer should be working too. Can you boot to DL mode?
Click to expand...
Click to collapse
I tried going to dl mode again and noticed that I can only boot to the warning screen, and then the volume button stops functioning there. Volume buttons works normally in recovery and OS. And also, I borrowed my friend's wireless charger and it was able to charge just fine with it.
youdoofus said:
you are making sense, but if the OTG works, then data transfer should be working too. Can you boot to DL mode?
Click to expand...
Click to collapse
I apologise for quoting you again and again, but I just wanted to update you that my Bixby button was stuck which made the volume buttons not working in the warning screen. I tore down the phone, fixed the bixby button and now I can boot to dl mode. And good news, Odin can detect the phone in dl mode. I will flash as you suggested and report back. Thanks a ton
seijidinzuala said:
I apologise for quoting you again and again, but I just wanted to update you that my Bixby button was stuck which made the volume buttons not working in the warning screen. I tore down the phone, fixed the bixby button and now I can boot to dl mode. And good news, Odin can detect the phone in dl mode. I will flash as you suggested and report back. Thanks a ton
Click to expand...
Click to collapse
youre most welcome! im glad you found the culprit because i wouldnt have ever thought of that. Situations like these are good in that they show examples of how weird stuff can get from time to time lol
if the phone is recognized by Odin and youre able to get to DL mode now, you should be all set
youdoofus said:
youre most welcome! im glad you found the culprit because i wouldnt have ever thought of that. Situations like these are good in that they show examples of how weird stuff can get from time to time lol
if the phone is recognized by Odin and youre able to get to DL mode now, you should be all set
Click to expand...
Click to collapse
So, I downloaded the firmware, did a complete wipe with the csc file. Annnd bad news, it still won't charge I just gonna buy a new charging board.
I wonder why the usb works only in download mode though, still give me doubts that the charging board is the culprit. :laugh: anyway thanks for helping.
Hey, I faced a similar problem today, what was your solution to fix it?
I got the screen on my S9 replaced and now it won't charge... usually. I took it back to the shop and they got it to charge with a different cable. I tried a different cable at home and it worked for a while, but now it's not charging again. So annoying and confusing.
I am going to write how it went since there are people asking. Maybe will be helpful or not helpful for people who stumble across this thread in the future too.
So, I gave up trying to fix it and bought a new charging board, it worked for a day and then it stopped working again. I am pretty sure even the original charging board was just fine. I think the whole issue had something to do with Samsung's security or self-protection system.
I will not buy Samsung again. Thanks.