Database Users

Vibrant USB Connection Issue

Hello XDA Community!
I made a post about this issue before, but have more details so hopefully someone can help me figure out this issue.
My phone even when unplugged from my PC continuously says USB Connected/ USB Debugging in the notification menu.
Also, when I try and reboot the phone, instead of booting even to the Vibrant logo screen, the loading circle continuously blinks on and off, without actually booting.
As I type this, I am not holding down the power button, and the loading circle is blinking on and off by itself....
I used to be able to turn the phone on into recovery mode in the past, but now when I try to reboot into recovery I get a big yellow picture that says "Downloading"
The only way the phone will turn on is if it is plugged in.
I am fairly certain that this reboot issue and the USB issue are correlated in some way.
Did anyone else have this issue with their phones? And if so, how did you solve it?

Another thing I have just discovered...
When the phone is on and idle, the USB Connection notification will constantly blink on and off, which is why I think the phone would do the same when trying to power on!
Is this a hardware issue or a software issue?
I have not flashed anything in a very long time before this issue started happening so I believe a restore is unnecessary .
Someone please help me! This is very annoying, not only do I have NO notification bar because of the constant USB Connection notification turning on and off, I cannot turn on my phone at all unless it is plugged in!
ACK!

Take it back
I carry the insurance, so personally if this was happening to me I would not even mess with it. It sounds like you have a genuine problem with the phone and it needs to be replaced.
If it is possible to do try a nandroid backup of your phone to make getting back to where you are on your new device easier. Then take your phone back to stock with the recovery image here -->
http://forum.xda-developers.com/showthread.php?t=734475 (Thank you justanothercrowd)
One you have a stock device see if you are still having the issue. If you are take it back as defective. Even if you don't have the insurance, that sounds like a factory defect and should be covered by the factory warranty. The insurance just makes the process easier and makes sure they just give you a swap out at the store rather than having to wait for repairs. It also covers things the warranty does not, such as screen breakage - which is the specific reason I carry the insurance.

Ah crap wish I had insurance.... Do I have to do that whole odin procedure or is there a one click un root procedure as well?
Sent from my SGH-T959 using XDA App

Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App

I actually have not had reason to go back to stock, or even use odin yet at this point. My only roms were .zip files that I flashed via clockwork recovery.
I would say that your best best it to just follow the instructions on justanothercrowd's thread very carefully and deliberately. You are already having issues with reboots and your USB port, so this is not the time to deviate into experiments.
So to cut you off and just answer you next three questions:
Q) Can I just . . .
A) No! Just follow the directions exactly.
Q) But can I . . .
A) No! Just follow the directions exactly.
Q) Do I have to . . .
A) Hey look, Just follow the damn directions exactly!
Sorry, I can't help much beyond that. You chose to modify your phone and risk that you would not have issues, just like the rest of us here. In your case you did have issues. Now you have to get it back to stock so they don't have any reason to claim you caused this or that your warranty is void. I hope all goes well and it works out for you. Let as know and keep us posted. Good luck.

Lo N Slo said:
Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
We must have been typing at the same time LOL.
There is a thread on unrooting, and basically it is just deleting a few things. After doing this you should not have any non-stock applications on the phone and there would be no reason to think it was rooted unless they went digging on the file system. Personally, I would delete those telltale files just in case, it looks a little suspicious to bring in a phone that looks like it has not been used since you bought it, but they have no proof you did anything and you can claim that you first did a factory reset to see if it would fix the problem.

Just want to keep this thread going, as I am having the exact same issue as the OP as of today. It happened out of the blue, and I haven't flashed anything new to my phone since JI6 was released, other than that, it's just a stock, rooted phone.
Hoping someone has an idea, but I will likely get it replaced under warranty, since the GPS has never worked either.

damnit damnit damnit I really wish I had warranty.
Random question about clockword mod recoveries.
If I were to do a backup right now, and save that file to my computer, could I restore that file later on a different phone after I root my replacement?
I don't have that many mods flashed, and I know all of the apps can be synced, but still it would be sooo convenient .

I believe that is how it works, so yes. It should be no different then when you clone a hard drive to put the image on multiple computers for easy distribution.
It is (just like the cloning metaphor) hardware specific. Just like I could not purchase a upgrade computer and expect a cloned image to work, don't expect to create a Vibrant backup and restore it on a Captivate.
That said, you should be able to restore your backup to new (identical) hardware.
By the way, what is the warranty on these? I thought it was a year for defects. I didn't think the Vibrant had been around long enough yet for anyone to be off warranty.

it should be a year, but there was also the option for a purchased warranty. I did not purchase a warranty, so I should be good on just my manufacturer's defect warranty

Being discussed here:
http://forum.xda-developers.com/showthread.php?t=817643

[Q] LG repair costs

My phone is bootlooping and I can't access recovery. I can't restore the phone's stock software because I edited build.prop and it's not showing up as a Verizon phone. I decided to bite the bullet and just pay LG to reset it. However, when I contacted them to do this they told me I need to mail the phone in and they will tell me how much it costs after their tech looks at it. I'm worried if I do this that they'll charge me an exorbitant amount to fix it... Does anyone have any idea how much they usually charge to do this?

Sending the phone off to LG should be your last resort. It sounds like you've not tried everything!

Send it in to warranty. As long as there's no physical damage Verizon isn't going to give a rats a$$

06stang said:
Send it in to warranty. As long as there's no physical damage Verizon isn't going to give a rats a$$
Click to expand...
Click to collapse
Well, in another thread a Sprint tech said that LG did not give them a method to flash the stock software if the model check failed. I assumed this was the case for Verizon as well. I'll call them tomorrow and ask, I may have misunderstood what he wrote. I can't seem to find his post now. I'll update this post after work tomorrow if they can recover the phone.
theoneofgod, what is it that you think I haven't tried yet? If you have a suggestion which would save me the trouble of sending this phone in I would be super happy. To recap, here's what I've tried:
1. Using hard keys to factory reset (on TWRP 2.6.3.1 so it actually factory resets instead of booting into recovery)
2. Hitting "adb reboot recovery" over and over as TWRP loads and performs factory reset (this worked for people on 2.6.3.1 on AT&T but doesn't seem to be working on my Verizon phone for some reason. I've tried it dozens of times and even wrote a batch file which spams "adb reboot recovery" many, many times faster than I could type it)
3. Flashing the .tot file through download mode (Model check fails)
4. Flashing the .kdz file through download mode (Hangs at either 4% or 10% and asks me to restart. Never gets past 10%)
5. Entering my IMEI into the LG update tool, letting it download the software for the phone, and letting it try to flash the software (it fails)

What was the reason for bootloop? i also change my model name to make camera app show pics in menu, but it didn't help, and i returned to stock build.prop. So whats your story? Its good to know what i should NOT do with the phone.

Yea a good idea if you share what you've done so readers can be aware of it. Goodluck to your G2 pal and we're sorry for you..

marshygeek said:
Yea a good idea if you share what you've done so readers can be aware of it. Goodluck to your G2 pal and we're sorry for you..
Click to expand...
Click to collapse
Np don't mind sharing, thanks for the sympathy this definitely sucks aha. I usually add in qemu.hw.mainkeys=1 to get rid of the software keys when I put a new ROM on. It worked the first time I did it on this phone, my best guess is that I mistyped something. I'm not 100% sure why this is making my phone not show up as a Verizon model during the model recovery check...someone more knowledgeable than me would have to explain that.
Melodycd, I think you should be fine doing that as long as you're careful. I was pretty careless and made a lot of mistakes to get in my position. As long as you don't do ALL of the following things you should be safe:
1. Not have the latest recovery
2. Not have USB debugging enabled
3. Mess up while editing a build.prop file so you bootloop

It doesn't matter what they can or can't do with the phone. They don't care what you did to it as long as it's not physically damaged or have water damage. Software issues can be fixed. If they couldn't flash new software they wouldn't have CLN devices to send out for warranty.
I've sent in several dozen phones that I left rooted (for legitimate defect concerns) and none were charged back. They don't need to know what happened to the phone when you call all they need to know is its not working and to send you out a device. They'll receive yours, flash it or send it back to LG to flash, then send it out to someone else as a warranty device.

06stang said:
It doesn't matter what they can or can't do with the phone. They don't care what you did to it as long as it's not physically damaged or have water damage. Software issues can be fixed. If they couldn't flash new software they wouldn't have CLN devices to send out for warranty.
I've sent in several dozen phones that I left rooted (for legitimate defect concerns) and none were charged back. They don't need to know what happened to the phone when you call all they need to know is its not working and to send you out a device. They'll receive yours, flash it or send it back to LG to flash, then send it out to someone else as a warranty device.
Click to expand...
Click to collapse
Okay I'll send it in tomorrow. Thanks man, I was just worried that since the phone says "rooted" in download mode they would flip out about it. Appreciate the reassurance.

ccmbr002 said:
Okay I'll send it in tomorrow. Thanks man, I was just worried that since the phone says "rooted" in download mode they would flip out about it. Appreciate the reassurance.
Click to expand...
Click to collapse
I'm just sharing my experience. Over the past 5 years I've been rooting and returning. I can't guarantee anything but i can tell you my experiences and what I've been told by vzw people I know.

I had my g2 repaired when it was rooted. My camera wasn't working atall would just show up black when i opened the app. I sent it in rooted w CWM recovery as i stupidly forgot to remove it. And i had a replacement within 5 days no questions asked.
Not sure if this is because i am in UK or not, but they didn't blink an eye.

Swanseatom said:
I had my g2 repaired when it was rooted. My camera wasn't working atall would just show up black when i opened the app. I sent it in rooted w CWM recovery as i stupidly forgot to remove it. And i had a replacement within 5 days no questions asked.
Not sure if this is because i am in UK or not, but they didn't blink an eye.
Click to expand...
Click to collapse
Yep I was just worried because the Verizon phone explicitly states that it is rooted. Just to follow up for those who are on Verizon and are stuck bootlooping and with no way to flash the stock ROM, what 06stang said held true for me (so far). The Verizon rep on the phone couldn't help me (she said she needed me to put my SIM card in my G2 when I was calling her from my old phone) so I took it to a Verizon store. The dude checked it for physical damage, tried to turn it on, and when he saw it bootloop he put in an order to get me a replacement phone. I'll report back in a week or two after I send in my rooted phone and let people know what happens, it seems like they won't charge me as of right now though.

[Q] Note 3's note charging/connecting to a PC

Hi,
My brother has a Galaxy Note 3 (the LTE version. N9005) which has been brilliant up until just now, where it can't charge nor connect to a PC.
He's tried using both the microUSB 3.0 cable that came with it - both connecting to a computer and to charge - as well as a microUSB 2.0 cable to charge... Neither has worked.
He's on stock, no rooting whatsoever (not that kind of person).
Is this a hardware problem or is there anything that could solve this before we send it off to warranty?
Any answers are greatly appreciated...
UPDATE: Its suddenly charging again... But we'll see what happens... In the meantime, can anyone offer an explanation?
Sent from my GT-P7510 using Tapatalk HD

I have the same problem with the phone not being recognised by the computer or charger. Strange thing is that the computer recognises the phone in download mode via odin (an kies for a while). And it has been charging while in download mode connected to kies or odin.
I initially thought it was a bad third party rom i had downloaded and tried to change to another rom. It was back to charging for a bit and then after a day stopped again. Tried to reset to factory rom and bricked the phone in the process (as stupidly checked reactivation lock and clicked a wrong button when titanium backup asked if I wanted to restore the previous id - spent 2 days to unbrick it.....
But now I'm back to the phone not being able to charge or being recognised by the computer. Even the OTG cable isn't recognised. HELP pleaseeee someone. First issue with a Galaxy since the S3/S4/Note1/Note2.
Any thoughts as to what the issue could be? Someone mentioned that it could be a setting in phoneutils menu (if USB set to modem it wont recognise - has to be set to PDA). But the *#7284# command doesnt seem to work on the Note 3. Does anyone know how to invoke the phone utility menu?
I might have to take it back to Samsung - only that I have rooted it and knox shows it!!
Update :
I sent the device into the service centre this morning and explained the problem. The guy at the counter didn't bat an eye while telling me its likely a usb port problem and that he would try to check it and get it turned around within a day. When I asked him if others had similar problems, his response seemed to indicate that it wasn't an uncommon problem. They even had plenty of spares for the port.
I got a text within 2 hours telling me that the unit was fixed. They didn't give me any hassle about the unit being rooted but I guess with a hardware issue, it shouldn't have mattered anyway.
So far so good with the unit. Just thought I'd update you guys.

arul said:
Update :
I sent the device into the service centre this morning and explained the problem. The guy at the counter didn't bat an eye while telling me its likely a usb port problem and that he would try to check it and get it turned around within a day. When I asked him if others had similar problems, his response seemed to indicate that it wasn't an uncommon problem. They even had plenty of spares for the port.
I got a text within 2 hours telling me that the unit was fixed. They didn't give me any hassle about the unit being rooted but I guess with a hardware issue, it shouldn't have mattered anyway.
So far so good with the unit. Just thought I'd update you guys.
Click to expand...
Click to collapse
Sorry to revive an old thread, but is it just a hardware problem then?
The phone suddenly started charging again shortly after your reply, so we didn't have this problem for months.
The phone got repaired after quite a bad incident, and now its not charging or connecting to a PC again.
There's a Samsung service centre down the road from where I am so we're planing on going tomorrow. Just wanted to see whether it was hardware or software related...
Sent from my GT-I9300 using Tapatalk

This maybe aswell related to cache, you could go into the st9ock recovery and wipe cache (no need to factory reset) Ive used this method to solve connecting issues with note 3 to computers.

dogmatism said:
This maybe aswell related to cache, you could go into the st9ock recovery and wipe cache (no need to factory reset) Ive used this method to solve connecting issues with note 3 to computers.
Click to expand...
Click to collapse
And that causes no side effects whatsoever?
It also doesn't charge via AC, so could jt fix it as well..?
Sent from my GT-I9300 using Tapatalk

Clearing cache does not create any problem/ harm. The ones ive tested had connecting issues data/debug ... but showed charging... but no harm in trying your luck eh?

dogmatism said:
Clearing cache does not create any problem/ harm. The ones ive tested had connecting issues data/debug ... but showed charging... but no harm in trying your luck eh?
Click to expand...
Click to collapse
Hoping it'll work indeed... since we're overseas we can't exactly claim warranty either, though I'm not sure it'd even pass for warranty anyway
Sent from my GT-I9300 using Tapatalk

Fixed it, we just took it down to the service centre the guys there replaced the USB port for free (after a bit of complaining on our part, we had already paid quite a bit to repair the thing after a freak accident)
@dogmatism, thank you for your help anyway!
Sent from my GT-I9300 using Tapatalk

good foe you...
you never mentioned abt a physical damage/accident.

dogmatism said:
good foe you...
you never mentioned abt a physical damage/accident.
Click to expand...
Click to collapse
This problem happened before the freak accident, but it just fixed itself somehow, so wasn't much of an issue until now.
Sent from my GT-I9300 using Tapatalk

Bricked beyond repair?

So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.

Just to rule out the obvious, have you tried different cable and computer?

gabriwinter said:
Just to rule out the obvious, have you tried different cable and computer?
Click to expand...
Click to collapse
Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.

godraistlin said:
Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.
Click to expand...
Click to collapse
I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.

How did you brick your OP in the first place? Does it still charge?

Z-Blade said:
How did you brick your OP in the first place? Does it still charge?
Click to expand...
Click to collapse
It bricked in the middle of using the unbrick tool. It literally doesn't do anything. No charging, no vibrations. Nothing.

gabriwinter said:
I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.
Click to expand...
Click to collapse
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.

The fact it does not even charge sounds like a hardware issue. Even when its bricked it should at least charge.

godraistlin said:
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.
Click to expand...
Click to collapse
This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.

Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.
I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.
There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.
Good luck.

Did you try holding power button for >40 seconds?

godraistlin said:
So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.
Click to expand...
Click to collapse
If it's totalled then one plus will have no idea what is wrong either, send it back mate.

After reviewing all the replies, which won't work for you.
Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.

dladz said:
If it's totalled then one plus will have no idea what is wrong either, send it back mate.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

GAMIT PRUTHVI said:
After reviewing all the replies, which won't work for you.
Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

gabriwinter said:
This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

jhs39 said:
Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.
I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.
There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.
Good luck.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

HI. I'm a user of POCO m3 global device and i want to know the problem of my phone

my phone was just 5 month old since i bought it. I always update my phone. and the problem started (when started to notice) at version 12.0.5 of the update. it won't turn on as it should whenever I restart or shut down then try to open it again. have I ever tried to charge to my phone and wait to be fully charged then open it? YES I wait for it and NO it never charge like it's dead. it wasn't even drained when I turned it off. I tried to open it m, access fastboot mode or recovery mode multiple attempts but in vain. And after some days passed of not charging it, it was drained (literally 0%) and whenever it got a charge, it just turned on by itself. My phone is now at version 12.0.8 and yet the problem to continues and even got worse. just yesterday morning, every apps that use started to crash like in the attached photos. (1st photo- flashlight not available.). I then try to restart it, but it never turn on again until now. I tried to access to recovery and fastboot but still in vain.. PLS HELP

RealTiz said:
my phone was just 5 month old since i bought it. I always update my phone. and the problem started (when started to notice) at version 12.0.5 of the update. it won't turn on as it should whenever I restart or shut down then try to open it again. have I ever tried to charge to my phone and wait to be fully charged then open it? YES I wait for it and NO it never charge like it's dead. it wasn't even drained when I turned it off. I tried to open it m, access fastboot mode or recovery mode multiple attempts but in vain. And after some days passed of not charging it, it was drained (literally 0%) and whenever it got a charge, it just turned on by itself. My phone is now at version 12.0.8 and yet the problem to continues and even got worse. just yesterday morning, every apps that use started to crash like in the attached photos. (1st photo- flashlight not available.). I then try to restart it, but it never turn on again until now. I tried to access to recovery and fastboot but still in vain.. PLS HELP
Click to expand...
Click to collapse
It's a motherboard error, complaining, cell phone replacement or repair.

rotoko said:
It's a motherboard error, complaining, cell phone replacement or repair.
Click to expand...
Click to collapse
is there a chance that the problem only exist in the firmware or a virus causes this? 'cause it never fell off since I bought it (6months ago). but something fell onto it but only caused a tiny bubble on its screen protector and the touchscreen work just fine as it never happens. which do you think is more likely??

RealTiz said:
is there a chance that the problem only exist in the firmware or a virus causes this? 'cause it never fell off since I bought it (6months ago). but something fell onto it but only caused a tiny bubble on its screen protector and the touchscreen work just fine as it never happens. which do you think is more likely??
Click to expand...
Click to collapse
The cause is unknown. Instead of guess what the cause is, go find Xiaomi repair center to inspect and repair for you.
Make use of Xiaomi warranty.
Backup your stuff, apps, and data. Prepare for factory reset as Xiaomi repair center may erase your personal data.
Don't push your luck assuming firmware or virus cause. Assume hardware issue first, this cannot wait once it pass warranty period deadline. ROM, firmware, software issues can be dealt with later, and can also be dealt by Xiaomi repair center.

pl1992aw said:
The cause is unknown. Instead of guess what the cause is, go find Xiaomi repair center to inspect and repair for you.
Make use of Xiaomi warranty.
Backup your stuff, apps, and data. Prepare for factory reset as Xiaomi repair center may erase your personal data.
Don't push your luck assuming firmware or virus cause. Assume hardware issue first, this cannot wait once it pass warranty period deadline. ROM, firmware, software issues can be dealt with later, and can also be dealt by Xiaomi repair center.
Click to expand...
Click to collapse
but i only bought it online. how can i know if it's warranty is still valid?

RealTiz said:
but i only bought it online. how can i know if it's warranty is still valid?
Click to expand...
Click to collapse
Warranty in general is at least 1 year.
The personal in Xiaomi repair center will judge the warranty. There are some conditions that will void the warranty. Check the Xiaomi warranty policy of your country/region yourself.
Warranty only covers the phone model you bought from local country/regions. I.E. phone bought from India will not be covered under warranty in Indonesia, this case, you bring the phone to India and repair it.

pl1992aw said:
Warranty in general is at least 1 year.
The personal in Xiaomi repair center will judge the warranty. There are some conditions that will void the warranty. Check the Xiaomi warranty policy of your country/region yourself.
Warranty only covers the phone model you bought from local country/regions. I.E. phone bought from India will not be covered under warranty in Indonesia, this case, you bring the phone to India and repair it.
Click to expand...
Click to collapse
well my phone was from overseas. Japan I think not sure. is this mean it's warranty wont be valid in the philippines?

RealTiz said:
well my phone was from overseas. Japan I think not sure. is this mean it's warranty wont be valid?
Click to expand...
Click to collapse
The repair center in your country will not deal with it.
If you want to repair it, you have to repair in Japan. The warranty is still valid in Japan in this case.
Or you can ask if the Xiaomi repair center in your country willing to repair it if you pay.

pl1992aw said:
The repair center in your country will not deal with it.
If you want to repair it, you have to repair in Japan. The warranty is still valid in Japan in this case.
Or you can ask if the Xiaomi repair center in your country willing to repair it if you pay.
Click to expand...
Click to collapse
okay.. thanks for your recommendation..

RealTiz said:
okay.. thanks for your recommendation..
Click to expand...
Click to collapse
Did u bough your POCO M3 from Lazada??? I think its a combination of hardware and software problem were almost there same issue bro, i just need to BURN my motherboard just to turning it on.

RealTiz said:
my phone was just 5 month old since i bought it. I always update my phone. and the problem started (when started to notice) at version 12.0.5 of the update. it won't turn on as it should whenever I restart or shut down then try to open it again. have I ever tried to charge to my phone and wait to be fully charged then open it? YES I wait for it and NO it never charge like it's dead. it wasn't even drained when I turned it off. I tried to open it m, access fastboot mode or recovery mode multiple attempts but in vain. And after some days passed of not charging it, it was drained (literally 0%) and whenever it got a charge, it just turned on by itself. My phone is now at version 12.0.8 and yet the problem to continues and even got worse. just yesterday morning, every apps that use started to crash like in the attached photos. (1st photo- flashlight not available.). I then try to restart it, but it never turn on again until now. I tried to access to recovery and fastboot but still in vain.. PLS HELP
Click to expand...
Click to collapse
Firstly you need to learn basic formatting because reading your story it's too hard.
If you bought with a credit card, make a complaint to your financial institution and apply for a charge back.
Same goes if you paid with Paypal, but that it's a bit more tricky.
No one will fix your phone because it'll cost more than what you paid for it.