Database Develop

HELP XDA! Phone Reboot's if using 3g Data

Hey,
My AT&T rooted nexus one is still randomly rebooting if I use 3g data. I am in Costa Rica and the 3g is on the 850 band. I also have to add the apn "kolbi3g".
So basically I can use the phone for anything and it works great, but if I add the apn and start using the 3g heavily I will get a reboot, sometimes it will reboot vibrate 7 times and I have to pull the battery. I have tried 2.1 and 2.2 rooted and not also cyanogen 6 all the same problem.
If I do *#*#4636#*#* and select the wcdma only it runs the 3g better but reboots way more, sometimes the instant I place load on the connection. However if I select wcdma "unkown" the 3g works much better I can use it sometimes 30min at a time without a problem.
So any ideas what I could try? Is there a kernel that will up the volt's a bit just help stability? Or anything else I could try? Data roaming is off, I have tried both off and on, no difference that I can tell.
Thanks a lot this is driving me crazy! Just got this phone Sunday too sick to my stomach of the thought I spend $600 on this phone if I can't get 3g to work

How about radio image???
It is currently on baseband 4.06.00.12_7. Is there a more current radio?

I came across this multiple reboot issue on a (locked) Vodafone UK Nexus.
It booted into the OS (lockscreen) and as soon as data connected it looped back to the last couple seconds of the animated Nexus logo.... and again.... and again.
I powered down the unit (battery pull), booted into bootloader (voldown+power) and selected clear storage (voldown,voldown,power) then (volup) to confirm.
This deletes the user data and you have to sign in and set up the phone again but it certainly fixed the issue. My only guess is some user data became corrupt and the kernel panicked and forced a partial reboot.
Give it a try and lemme know.

Cabarnacus said:
I came across this multiple reboot issue on a (locked) Vodafone UK Nexus.
It booted into the OS (lockscreen) and as soon as data connected it looped back to the last couple seconds of the animated Nexus logo.... and again.... and again.
I powered down the unit (battery pull), booted into bootloader (voldown+power) and selected clear storage (voldown,voldown,power) then (volup) to confirm.
This deletes the user data and you have to sign in and set up the phone again but it certainly fixed the issue. My only guess is some user data became corrupt and the kernel panicked and forced a partial reboot.
Give it a try and lemme know.
Click to expand...
Click to collapse
Just did that (had the phone plugged into wall charger), and the second I got to the home screen it rebooted then vibrated like 6 or seven times. Seems to do it worse when it is plugged in. And now it won't even boot up even after pulling the battery, it vibrates 6-7 times.
I am really worried about this, any other ideas??? I will try anything! Thanks for the help

Update! Now the phone just reboot when I do anything period with it plugged in. Just like posted in another thread on this section!
Please any ideas I am very desperate and very sick to my stomach!

Hmmm very strange.
I'm aware from what you were saying on the other thread that you've got an unlocked bootloader and you're wondering what to do on the warranty front.
If you've really tried different combinations of stock and custom firmware and having the same issue I'm tempted to say its a hardware issue.
Many people have returned their unlocked phones with no comeback from HTC some have reported that they have noticed the unlocked bootloader and have issued a motherboard repair as part of the fix because of this.
Although im unsure of the additional cost (if any) i would definitely recommend going through the warranty repair route with HTC. They won't say no and send you back the same broken phone. And who knows, if its a confirmed hardware issue they may just replace it as a goodwill gesture.

Other than that I don't have any more ideas.
A nexus support thread has a popular answer referring to the clear storage fix.
http://www.google.de/support/forum/p/android/thread?tid=40f52d29e9c4177e&hl=en
Just make sure you are definitely clearing the storage FROM THE BOOTLOADER before calling HTC. It is the first thing they will make you do before accepting a return anyway.

Cabarnacus said:
Other than that I don't have any more ideas.
A nexus support thread has a popular answer referring to the clear storage fix.
http://www.google.de/support/forum/p/android/thread?tid=40f52d29e9c4177e&hl=en
Just make sure you are definitely clearing the storage FROM THE BOOTLOADER before calling HTC. It is the first thing they will make you do before accepting a return anyway.
Click to expand...
Click to collapse
Ok thank you so much sir. I am so glad to hear that I may still have a chance at getting it replaced! It was very fullish of me to unlock it, I know, it is just that I figured it was software and could be fixed by unlocking. It is going to cost me $$$ to get this to the States, but that is life. If I still can't get it to work I will call htc and let you know what they say

Little update here. I cleared storage again and just simply disabled data, I have been using the phone for a couple of hours on work without any problems. Next thong I am going yo yty is another friends 3g similar card and see if it still reboots on that sim, if it does then I am calling HTC.
Also still open to any other ideas you guys may have.

[Q] Pattern lock -> Too many tries

I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?

Do a hard reset / wipe. That's my suggestion.

Try booting into recovery (Home Button, Vol Up + Power), and resetting your cache and wiping it. Then try logging in with your Google account. If all else fails, try changing your Google password on the PC then logging in on the phone. And then if it still fails, looks like you need to flash the phone again. Next time, don't enter the thing wrong! Stop rushing haha .

I wasn't rushing, I was playing with the lock. It takes about 30 times before it's permanently requiring the username/password. But really...you can't blame me for not expecting this. :/
I'm currently trying to flash a new ROM but I've run into another problem - I can't get it to boot into downloader/recovery. It's not the lack of the 3 button combo - I've managed to reach Recovery and Downloader ONCE each in the past, but never again since.
And now with all my efforts to boot into recovery/downloader, it now cannot boot into normal usability mode (or in my case, locked mode). Instead, the Galaxy S logo loops endlessly.
Sigh.

Have you read the thread for the fix for Galaxy S variants that are lacking the 3 Button Combos? It's in Android Development. Maybe try that? Or, can you still connect the phone and connect with Kies?

I can't turn on the phone anymore, meaning no changing to USB debugging etc. And I'm having problem accessing recovery/download, even though I definitely HAVE done each of them once before and therefore do not have the 3 button problem.
Without turning on my phone, Kies can't detect it

So what happens when you power on?

Now, it shows the first Galaxy S splash screen, then shows the boot logo, then nothing. The boot logo continues to glow endlessly.

Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App

okpc said:
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yeah it's continuously shining. Haven't left it for up to five minutes though... And even then it probably won't help since I'm still locked out of the phone, and unable to access download/recovery mode to reflash it.

After waiting for a long time, the logo disappears, screen goes black. Menu and back buttons light up. Nothing else.

Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.

PaulForde said:
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
Click to expand...
Click to collapse
Good advice considering he said his 3 button combo stopped working =))

All I did when I got that black screen was adb reboot recovery and wiped and phone bootedup fine. But only if you have debuging enable and and sumsung drivers. Hopes this help.
Sent from my SGH-T959 using XDA App

Can't enable USB debugging when phone can't be turned on at all.

danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.

danamoult said:
Can't enable USB debugging when phone can't be turned on at all.
Click to expand...
Click to collapse
you need to be able to enter recovery mode for you to solve this problem

danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
dear friend dont worry or panic... i'll tell you a trick , go to the samsung customer care and tell them that your phone gets heated up very often and today it just refuses to boot up normally...
since your device cannot get into recovery mode or download mode the company will never know that you had played with the system files in the device or not... (rooted )..
since the samsung people will also try to get your device in recovery mode.. but when it will not go to the recovery mode you will get a mother board replacement under warranty.....
this heating up of the device is a common problem in the galaxy here in india.. so use this excuse and i know it works 100% ... (just dont tell them that you had rooted and lagfixed your device )

What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
OzzYGuY said:
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
Click to expand...
Click to collapse

distortedloop said:
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
Click to expand...
Click to collapse
chill my dear friend.... it cant be true.... its just his 1st post.. and samsung cannot be so dumb to leave a password protected keypad that can be cracked so easily.. even i tried the back key on a call with a password lock.. i cannot get passed the lock screen....

Phone keeps shutting down

Today my 4X encountered a strange problem: It shut down itself (I thought the battery was empty and charged it), and after restarting it just shuts down immediately. It shows the lockscreen saying "no SIM" and then shuts down. Anyone know a solution to fix this? I suppose a factory reset might do it, but I don't have a backup now and would like to keep my data.

muellersmattes said:
Today my 4X encountered a strange problem: It shut down itself (I thought the battery was empty and charged it), and after restarting it just shuts down immediately. It shows the lockscreen saying "no SIM" and then shuts down. Anyone know a solution to fix this? I suppose a factory reset might do it, but I don't have a backup now and would like to keep my data.
Click to expand...
Click to collapse
If it is the SIM then try a different SIM, or put a folded piece of paper between the holder and the SIM - I always do that with phones just to make sure it keeps good contact at all times.
Other than that, no real idea mate - sorry

I think it should also work without a SIM. But as said, it just shows the lockscreen for ~2 seconds and then shuts down. I have tried without a sim, it's the same. I'll try with a different one, but I suppose that won't help much. I think i'll also try a kdz reflash, but i'll have to set up my father's PC to do so. Just thought maybe someone knows a quick solution.

Alright, i've just done a kdz reflash - same situation. Is there a way to adb pull the /data/data from any of the other modes (recovery, Emergency etc.?)

muellersmattes said:
Alright, i've just done a kdz reflash - same situation. Is there a way to adb pull the /data/data from any of the other modes (recovery, Emergency etc.?)
Click to expand...
Click to collapse
Weird... Reflash use to replace all files and stock settings unless you have some app avoiding them to run... Reflash don't delete installed apps most part of the time. If you have frozen apps they'll remain frozen. Did you factory reset before reflash?
Sent from my LG-P880 using xda app-developers app

RuedasLocas said:
Weird... Reflash use to replace all files and stock settings unless you have some app avoiding them to run... Reflash don't delete installed apps most part of the time. If you have frozen apps they'll remain frozen. Did you factory reset before reflash?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
No, as said i wanted to try everything before doing a factory reset (don't have a recent backup because Ubuntu won't recognize the MTP mode properly). I have restarted the phone many times before without that strange behaviour and didn't freeze anything since then. I just can't tell where the problem comes from. BTW, the SIM is recognised now (after the reflash), but still shutting down.

muellersmattes said:
No, as said i wanted to try everything before doing a factory reset (don't have a recent backup because Ubuntu won't recognize the MTP mode properly). I have restarted the phone many times before without that strange behaviour and didn't freeze anything since then. I just can't tell where the problem comes from. BTW, the SIM is recognised now (after the reflash), but still shutting down.
Click to expand...
Click to collapse
You notice some over heat, you try to use it without SD card, it keeps rebooting when charger is connected?...
Cause appart of hardware malfunction, I can't see any other reason... of course we don't know if the system file is corrupted or not...
If the phone is ON time enough, you can copy the data files/ folders to your SD card, after save them all you can factory reset...
Wait for better help cause I have no idea... sorry

RuedasLocas said:
You notice some over heat, you try to use it without SD card, it keeps rebooting when charger is connected?...
Cause appart of hardware malfunction, I can't see any other reason... of course we don't know if the system file is corrupted or not...
If the phone is ON time enough, you can copy the data files/ folders to your SD card, after save them all you can factory reset...
Wait for better help cause I have no idea... sorry
Click to expand...
Click to collapse
It's not because of heat, the phone is really cool. It just stays on for a second or so, just enough to see the lockscreen or the "Enter PIN" screen and then it shuts down. It's like the battery was empty, but it's charged. It even shows the charged battery symbol. Guess I'll have to do a factory reset and lose my data. As root is gone, I also can't boot to the bootstrap recovery (with this method) to backup there. Should have done that before doing a reflash...

muellersmattes said:
It's not because of heat, the phone is really cool. It just stays on for a second or so, just enough to see the lockscreen or the "Enter PIN" screen and then it shuts down. It's like the battery was empty, but it's charged. It even shows the charged battery symbol. Guess I'll have to do a factory reset and lose my data. As root is gone, I also can't boot to the bootstrap recovery (with this method) to backup there. Should have done that before doing a reflash...
Click to expand...
Click to collapse
You can try to downgrade before factory reset... some apps won't work but, maybe the phone just don't turn OFF and you'll be able to save your data.

So downgrading didn't work either. I'll use the LG Support Tool to upgrade and factory reset now (with data loss). That should hopefully fix it.

Well, the LG Support tool also didn't fix it. Data is lost now, so I can freely do whatever I want
I've tried to get into the "low-level mode" (http://forum.xda-developers.com/showpost.php?p=35524491&postcount=11), but no success. Can someone point me into the right direction and on how to press those buttons? I've tried several combinations, but they all didn't work out - either the battery symbol appeared or the phone booted to recovery or to the "do not touch cable notice" mode.
As far as I understand I should do the following steps:
1) Remove the battery and USB cable
2) Insert the battery and plug in the cable. The phone vibrates once, then shows the LG logo, then shows a battery symbol and then turns off the screen.
3) Press Vol+ and power and hold it. The battery logo shows again. There is a sound indicating that some device is connected to Windows. The screen turns off and there is a sound indicating that the device is disconnected from Windows. Let go off the buttons.
4) Press the buttons again until there is a sound indicating that a device is connected to Windows. Let go off the buttons. The screen should remain off.
Is this correct? What am I doing wrong? Do I have to wait at some point for some action? As said, all I ever got was the "battery symbol" again (for a few seconds).

muellersmattes said:
Well, the LG Support tool also didn't fix it. Data is lost now, so I can freely do whatever I want
I've tried to get into the "low-level mode" (http://forum.xda-developers.com/showpost.php?p=35524491&postcount=11), but no success. Can someone point me into the right direction and on how to press those buttons? I've tried several combinations, but they all didn't work out - either the battery symbol appeared or the phone booted to recovery or to the "do not touch cable notice" mode.
As far as I understand I should do the following steps:
1) Remove the battery and USB cable
2) Insert the battery and plug in the cable. The phone vibrates once, then shows the LG logo, then shows a battery symbol and then turns off the screen.
3) Press Vol+ and power and hold it. The battery logo shows again. There is a sound indicating that some device is connected to Windows. The screen turns off and there is a sound indicating that the device is disconnected from Windows. Let go off the buttons.
4) Press the buttons again until there is a sound indicating that a device is connected to Windows. Let go off the buttons. The screen should remain off.
Is this correct? What am I doing wrong? Do I have to wait at some point for some action? As said, all I ever got was the "battery symbol" again (for a few seconds).
Click to expand...
Click to collapse
Once that data is gone, just reflash the phone.
My advice, like always is, downgrade, factory reset, upgrade , root, factory reset.
hope you don't tell me that you have problems with flash method...

I have tried that. Flashed v10a, wiped data in recovery, upgraded to v10h via LG Support Tool. Still shutting down. I thought the emergency recovery might fix it but I cant get the emergency mode to work. I'll call the LG support tomorrow and hope they'll bring me a new phone.
Gesendet von meinem ASUS Transformer Pad TF300TG mit Tapatalk 2

muellersmattes said:
I have tried that. Flashed v10a, wiped data in recovery, upgraded to v10h via LG Support Tool. Still shutting down. I thought the emergency recovery might fix it but I cant get the emergency mode to work. I'll call the LG support tomorrow and hope they'll bring me a new phone.
Gesendet von meinem ASUS Transformer Pad TF300TG mit Tapatalk 2
Click to expand...
Click to collapse
If when you're flashing, you use "web upgrade" instead of normal upgrade, it will upgrade with LG Tool, official firmware, what it means that is the same than the emergency recovery that you're trying to use.
The difference is that you don't need to use IMEI. The detection is automatic.

RuedasLocas said:
If when you're flashing, you use "web upgrade" instead of normal upgrade, it will upgrade with LG Tool, official firmware, what it means that is the same than the emergency recovery that you're trying to use.
The difference is that you don't need to use IMEI. The detection is automatic.
Click to expand...
Click to collapse
Thanks, I thought the Emergency Recovery was still different. So no chance to fix this now. LG's support won't work on Christmas, so three more days stuck with it.

I got the phone back today. Put the battery in, started, and... it shut down. AGAIN. They were supposed to fix that! Anyone near me who has a spare battery for testing? After all that might be faulty.

muellersmattes said:
I got the phone back today. Put the battery in, started, and... it shut down. AGAIN. They were supposed to fix that! Anyone near me who has a spare battery for testing? After all that might be faulty.
Click to expand...
Click to collapse
It goes down when charger is connected?

Yes, it does. And it recognises the battery as full, that's why I don't suppose it's because of that. But one never knows.

mines done it a couple times recently too! just living with it till the update!

Problem solved. A new battery did the trick. But I still don't know why it would shut down with the old one.

[Q] Why does My HTC One M7 Turns Off After Factory Reset?

Hey guys. I'm planning on selling my HTC One M7 since I recently upgraded. I did a full data reset to bring it back to how it was out of the box. I then SIM unlocked it with my unlock code and currently don't have a SIM sitting in it.
When you turn it on it'll bring up the Get Started/Emergency screen so you can begin to set up your new phone. Everything looked good, so I let the screen timeout. A little while later I come back and find the phone turned off on it's own. I power it back on and see it still has a lot of battery left. I leave it alone again and about 2 hours later I find it turned off again.
Is something wrong with the phone? It was working great up until I did the reset and now this happens. Or is it maybe some sort of power mode thing that shuts it off on it's own after a while since it hasn't been set up yet. I've tried to Google for answers, but come up with nothing.
Help! Thanks!

thegreatmikesby said:
Or is it maybe some sort of power mode thing that shuts it off on it's own after a while since it hasn't been set up yet. I've tried to Google for answers, but come up with nothing.
Click to expand...
Click to collapse
probably, only way to know is to go trough the setup and see if it reboot again, then you could factory reset the phone again.

alray said:
probably, only way to know is to go trough the setup and see if it reboot again, then you could factory reset the phone again.
Click to expand...
Click to collapse
Thanks. That did the trick. Once the phone was setup, no more problem. I guess it must be a power saving thing while still in fresh out of box mode.

Phone freezes with black screen and have to hard reboot

I have only 2 days of warranty left on my phone so that makes things scary for me.
I recently got my motherboard changed but still have the same problem. No problem what ROM or kernel I use I get the same issue. I have been facing this since last 3 months and no solution till date. So please if you could just find some time please read on.
(Am posting the same text over a couple more threads as well in order to maximize the help I can get. So please forgive me for that.)
I currently have two sim cards:
BSNL: 2g and 3g coverage only
Jio 4g: only 4g coverage.
So I primarily use my data from Jio 4g but I recently also recharged my BSNL as well because of low data rates and also so that I can use more data per day. (They both have per day data plans).
When I use data from Jio sim, it uses the 4g network and hence the BSNL shifts to 2g only mode and I don't face any problems. But when I switch to BSNL sim for data, it jumps to 3g and the jio sim has no network because it only has 4g coverage and no 2g network. That's all expected. But that's the setup when I face problem in.
When am using my phone it runs smooth and every thing is perfect. But when I leave it aside for some time and come back to see it, it doesn't responds. There is only black screen. It doesn't responds to power button or the charging cable. It just sits like that. I have to hard restart the device by pressing the power button for like 15 seconds. And the phone eats battery while it was in that state of unresponsiveness. It occurs randomly. No phone calls or alarms ring while in that state and it eats a damn lot of battery.
I tried swapping sim slots but that does not changes anything. I switched places (and they were all at least 20 km apart).
But the strange thing is that when I swap either of the sim cards with any other 3rd company sim there is no problem whatsoever is the sim selected for the data. Also if I use the BSNL and JIO 4g one at a time(only one sim at a time) I don't face any problem even then. It only occurs when I use both of them together and that too when the data is turned on in BSNL. I have tried nearly everything I could. And now you are the only help left.
(And those who get annoyed by this post(s) please swallow in your anger as am already really broke as of now)
I will help you in any possible way I can.
Currenctly on stock OOS with locked bootloader but tell me and I'll move to your desired setup.
Update: i forgot to mention about logs. sorry for that. i know a little about taking adb logcat and i know that without logs no one would be actually help me out effectively. so please guide me on what kind of logs i need to get(logcat, radio logcat or kernel log). also since am not rooted adb will be the option for taking logs
Update2: adding latest radio logcat and a normal logcat as well. am giving another chance at taking a normal logcat again as last time i forget to export the logcat but instead made the CMD to display the logcat live in the window. Also while i was taking radio logcat i noticed that the phone's screen went black(and became unresponsive) at around 15:38 but the log shows it for only upto 15:35, hope i didn't missed something.
was unable to upload the files on xda hence uploading them to gdrive
Update3:took another log. this time also the log show last time as 16:10 but the phone went black at around 16:38. file is named logcat1.txt
Update4: ok i got another radio log. a proper one this time directly from cmd. maybe that's all i can do to help myself. i really need support now

Is your device in totally stock state? Stock oos stock recovery and bootloader locked? If yes then seems like hardware issue. If no then flash stock original oos whith stock recovery and check if problem is still there? If problem is still there submit your device to service center again.
Sent from my ONEPLUS A3003 using Tapatalk

meetpatel said:
Is your device in totally stock state? Stock oos stock recovery and bootloader locked? If yes then seems like hardware issue. If no then flash stock original oos whith stock recovery and check if problem is still there? If problem is still there submit your device to service center again.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
yes it is brother. stock oos, locked bootloader and stock recovery. and have been going to service centre since last few weeks and for some weeks they didn't find any problem but they eventually replaced the motherboard but still i face the issues.

Ashish.akc said:
yes it is brother. stock oos, locked bootloader and stock recovery. and have been going to service centre since last few weeks and for some weeks they didn't find any problem but they eventually replaced the motherboard but still i face the issues.
Click to expand...
Click to collapse
With time so short, I think that invoking the warranty is best.
Don't take delivery of the repaired phone unless it is demonstrated to you at the service center that the issue is set right, even if you have sit there for a few hours waiting to see if the phone freezes. Otherwise, the next time they will claim that it is out of warranty.

tnsmani said:
With time so short, I think that invoking the warranty is best.
Don't take delivery of the repaired phone unless it is demonstrated to you at the service center that the issue is set right, even if you have sit there for a few hours waiting to see if the phone freezes. Otherwise, the next time they will claim that it is out of warranty.
Click to expand...
Click to collapse
but i already brought back the phone yesterday with the new motherboard. it reached there around 5:30 in evening and they were getting closed in some time. but the moment i reached home i started facing the issue.
can anyone help me with the logs brother?