Related
i bought a new atrix 2 MB865,not rooted.I am facing a problem like after some hours sounds of media(games,videos,youtube,...)are getting muted but in the settings it shows that sounds are full,then i need to change all the sounds in the setings and then media sound setting..then they will be audible but this is a cyclic process...can any one please help me out why this is happening
Here goes similar thread http://forum.xda-developers.com/showthread.php?t=2048647 (yeah that's in a wrong section). I have the issue too. Reboot when it happens. Works for me!
is there any other solution except rebooting???
it happens nearly 3-4 times a day and it is irritating to reboot always...
vdpraneeth said:
is there any other solution except rebooting???
it happens nearly 3-4 times a day and it is irritating to reboot always...
Click to expand...
Click to collapse
What?! Is that stock rom? It happens very rarely on cm10.
its unrooted....i just use as it is when i buy it
vdpraneeth said:
its unrooted....i just use as it is when i buy it
Click to expand...
Click to collapse
Hate to suggest this, but you might try a full FDR on the device. Either that, or you could try and clear the data of the settings/apps that are facing the issues/or anything else that could be calling for the media volume settings. Either way, you shouldn't be having this issue with a stock A2. I'd try to reset as a last option, but try to clear the data of those above mentioned in settings > manage applications > find those I listed and clear the data > reboot. If that doesn't solve it, try a full factory reset...
bro all the apps,games,videos,songs,....are facing this issue,,,,so i think its not possible to clear each data.....will a factory reset fix this problem??
if yes,then there is no problem for me to do a factory reset
It happened with me on CM10 today, had to switch out of app and go back, the sound returned.
NHS2008 said:
It happened with me on CM10 today, had to switch out of app and go back, the sound returned.
Click to expand...
Click to collapse
but in my case i didnt get like that..i need to reboot the mobile or change the settings of sound....
can u please tell me how did u unlocked bootloader,rooted,installed CM10....
any links or procedure is helpfull....thanks in advance
vdpraneeth said:
but in my case i didnt get like that..i need to reboot the mobile or change the settings of sound....
can u please tell me how did u unlocked bootloader,rooted,installed CM10....
any links or procedure is helpfull....thanks in advance
Click to expand...
Click to collapse
It's pretty easy, you don't need to unloack booloader for custom roms(same kernel is used)
Root your phone first.
http://forum.xda-developers.com/showthread.php?t=1742879
Install Bootstrap recovery.
Backup your STOCK rom if ytou want.
http://forum.xda-developers.com/showthread.php?t=1346977
Install the rom of your choice from here. (Using Paranoid Android now, pretty slick.
http://forum.xda-developers.com/forumdisplay.php?f=1376
That's it!
(Do read the instructions in the particular threads)
NHS2008 said:
It's pretty easy, you don't need to unloack booloader for custom roms(same kernel is used)
Click to expand...
Click to collapse
We can't unlock our bootloader yet.
Lifehacker7 said:
We can't unlock our bootloader yet.
Click to expand...
Click to collapse
can any 1 please tell me when there is a chance of brick like when i flash,root,....
what will cause our A2 to brick??
is it safe to load custom roms??
why cant we unlock our bootloader still??
(because when i bought the mobile 15 days back....i came with GB and UNLOCKED text on the top left of the screen when i boot my mobile but this vanished after ICS update....this is correct as per my memory but i wasnt sure of this)
thanks
vdpraneeth said:
can any 1 please tell me when there is a chance of brick like when i flash,root,....
what will cause our A2 to brick??
is it safe to load custom roms??
why cant we unlock our bootloader still??
(because when i bought the mobile 15 days back....i came with GB and UNLOCKED text on the top left of the screen when i boot my mobile but this vanished after ICS update....this is correct as per my memory but i wasnt sure of this)
thanks
Click to expand...
Click to collapse
There's a risk in everything you do, from playing around with mobile devices to just simply walking outside your home each day. Flash the wrong FXZ/SBF to your device, you could brick. There's many ways to "brick" any device, and there are different levels of being "bricked". My suggestion: read, re-read, and read again before you do anything to any of your devices. Understand what you are doing before you do anything. You'd be surprised how many people fail to follow that simple step, and end up posting on here that they have borked their phone all up. Rooting is the least likely to brick your device. And of course it's "safe" to install (flash) custom ROMs, so long as you follow the installation instructions for each, and understand what you are doing before you do anything (sound familiar?) -- why do you think we are all on this site, for the lulz? The bootloader is locked, and will continue to be until the great devs here are able to crack the security certs, etc. The "unlocked" text you saw was likely from your carrier. I have a One S that gave a similar indication when I got it, because it was 'globally unlocked' to be used on any carrier. Hope that clears things up.
vdpraneeth said:
(because when i bought the mobile 15 days back....i came with GB and UNLOCKED text on the top left of the screen when i boot my mobile but this vanished after ICS update....this is correct as per my memory but i wasnt sure of this)
thanks
Click to expand...
Click to collapse
Unlocked probably means 'Carrier unlocked' and not 'Bootloader unlocked' Is this the Indian Version or Imported AT&T Version?
NHS2008 said:
Unlocked probably means 'Carrier unlocked' and not 'Bootloader unlocked' Is this the Indian Version or Imported AT&T Version?
Click to expand...
Click to collapse
imported AT&T version
vdpraneeth said:
imported AT&T version
Click to expand...
Click to collapse
So, It meant it was 'Carrier unlocked' to be able to run on any network around the world and not just AT&T USA.
NHS2008 said:
So, It meant it was 'Carrier unlocked' to be able to run on any network around the world and not just AT&T USA.
Click to expand...
Click to collapse
how can i test whether boot loader is unlocked or locked in atrix and atrix2??
vdpraneeth said:
how can i test whether boot loader is unlocked or locked in atrix and atrix2??
Click to expand...
Click to collapse
On atrix2 bootloader can't be unlocked yet.
Hi all.
Am using an exynos Edge.
I did a full factory reset and started from scratch. With twrp rooted.
If I use phone for a while, then everything closes by itself. Maps, Facebook, keyboard mostly.
If I clear the ram and end all, or reboot, it gets fixed.
Anyone else having this?
Hi, anyone?
Give it time idk what time it is for you but it's 223 am here.
But my gs7 doesn't do that
PunishedSnake said:
Give it time idk what time it is for you but it's 223 am here.
But my gs7 doesn't do that
Click to expand...
Click to collapse
Hi, are you rooted? I'm trying to suss out if it's a faulty device (seems odd?) or because of twrp! I don't want a replacement to have the same issue if it's twrp!
AV1985 said:
Hi, are you rooted? I'm trying to suss out if it's a faulty device (seems odd?) or because of twrp! I don't want a replacement to have the same issue if it's twrp!
Click to expand...
Click to collapse
Nope
My need for root ended after lollipop
Lol another issue and another person blindly rooting their phone for no good reason.
I really don't know why people jump into rooting so quickly. What did you gain?
It doesn't happen on my unrooted exynos . You would know if yours was faulty if you actually used it before tampering with it.
HI I have 1+1 and its 2 years 3 month old. Presently its on CM13 MM(oxygen OS I guess) and rooted and have a recovery also. I did root and recovery around 8 months back.
2 days back when mobile was in pocket and 35% battery it went in to bootloop. after lot of stuffs like clearing cache and dalvik cache nothing worked.
Later at night i found out that mobile is working fine when its connected to charging (either by lapi or Mob charger). Hence I didn't go back to old recovery.
yesterday fully drained my battery and later charged to full and found same issue.
I am not able to make out whats the issue and how to move forward if I don't want to loose my resent data state. PLs guys help me to solve this issue.
will do whatever needed to restore my mobile. TIA
Wait I didn't understand what u said ,ur saying that your phone gets stuck in boot loop when its not charging ,what happens when you are changing and then u plug it off ? Does it like reset ?
Hunting_Party10 said:
Wait I didn't understand what u said ,ur saying that your phone gets stuck in boot loop when its not charging ,what happens when you are changing and then u plug it off ? Does it like reset ?
Click to expand...
Click to collapse
see it sounds weird but its true. when i connect charging it boots in normally and normal operation will start as usual. Even after full starting, once I remove charging connection it goes off to boot loop. I didn't do any modification in software also. just did normal downloading off apps.
I saw slimier 2 complaints in Oneplus forum but no one relied for that. even originator has not updated what he did finally. I have asked for reply from them too.
praveen4u13 said:
see it sounds weird but its true. when i connect charging it boots in normally and normal operation will start as usual. Even after full starting, once I remove charging connection it goes off to boot loop. I didn't do any modification in software also. just did normal downloading off apps.
I saw slimier 2 complaints in Oneplus forum but no one relied for that. even originator has not updated what he did finally. I have asked for reply from them too.
Click to expand...
Click to collapse
Try a factory reset?
Mr.Ak said:
Try a factory reset?
Click to expand...
Click to collapse
not tried but red reviews of same case who said factory reset did not help.
I was looking if anyone who faced slimier issue before can help me.
is it related to battery?
praveen4u13 said:
not tried but red reviews of same case who said factory reset did not help.
I was looking if anyone who faced slimier issue before can help me.
is it related to battery?
Click to expand...
Click to collapse
Seems to me like a hardware issue.
Can you be on recovery/fastboot without the need of a charger?
Mr.Ak said:
Seems to me like a hardware issue.
Can you be on recovery/fastboot without the need of a charger?
Click to expand...
Click to collapse
yes, along as i want. No issue to be on recovery/fastboot without charging connected. Only normal boot is having issue.
praveen4u13 said:
yes, along as i want. No issue to be on recovery/fastboot without charging connected. Only normal boot is having issue.
Click to expand...
Click to collapse
Then no issues with hardware....seems like a bad/corrupt frimware.
You need to unlock your bootloader and flash latest Cos13 through fastboot.
How to- https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
To flash Cos13- https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Hope this helps.
Edit:After reading your first post seems like you're already rooted and have Twrp installed,with a unlocked bootloader,obviously.Though I don't able to understand if you're using cm13 or cos13 or oxygen os...
If you don't want to loose your internal storage,you can skip the userdata flash command while flashing Cos13 through fastboot,though,it is recommended to do that command.
You can always go to Twrp and take the backup of your internal storage in pc through MTP or a full backup using ADB.
Mr.Ak said:
Then no issues with hardware....seems like a bad/corrupt frimware.
You need to unlock your bootloader and flash latest Cos13 through fastboot.
How to- https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
To flash Cos13- https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Hope this helps.
Edit:After reading your first post seems like you're already rooted and have Twrp installed,with a unlocked bootloader,obviously.Though I don't able to understand if you're using cm13 or cos13 or oxygen os...
If you don't want to loose your internal storage,you can skip the userdata flash command while flashing Cos13 through fastboot,though,it is recommended to do that command.
You can always go to Twrp and take the backup of your internal storage in pc through MTP or a full backup using ADB.
Click to expand...
Click to collapse
thanks pal. yes bootloader and all is unlocked. will see about this in coming weekend.
can't this problem be fixed if i just move back to old backup?
meanwhile is there any shortcut that reduce the time frame for doing all this on existing data. If anyone knows pls share. If this is the only go then do comment will ask to close the thread.
praveen4u13 said:
thanks pal. yes bootloader and all is unlocked. will see about this in coming weekend.
can't this problem be fixed if i just move back to old backup?
meanwhile is there any shortcut that reduce the time frame for doing all this on existing data. If anyone knows pls share. If this is the only go then do comment will ask to close the thread.
Click to expand...
Click to collapse
Nandroid backup?
Yes if you've one then you can definitely restore it to fix the issues.
Mr.Ak said:
Nandroid backup?
Yes if you've one then you can definitely restore it to fix the issues.
Click to expand...
Click to collapse
bro one more issue started yesterday. I thought to making battery full nil and charge to 100% may help.
Before without charging connected I was able to go in twrp but not now. if i remove charging its going to restart even recovery mode also. When I went to restore old backup in TWRP mobile is auto starting even when charger is connected. but if i dont do anything its staying fine in TWRP lock screen.
without charging connected i can go into fastboot n stay for as long as i want but comp is not detecting mobile even though developer option is ON.
Yesterday thought of restoring old backup which interrupted half within 1min and now if i start mobile while charging its getting struk at 1+1 welcome screen.
I am fully confused like anything..
is it not strange that so many people (including) have started facing this issue suddenly in the past two months?
I too am facing this issue. Has anyone managed to find a fix for the issue?
praveen4u13 said:
thanks pal. yes bootloader and all is unlocked. will see about this in coming weekend.
can't this problem be fixed if i just move back to old backup?
meanwhile is there any shortcut that reduce the time frame for doing all this on existing data. If anyone knows pls share. If this is the only go then do comment will ask to close the thread.
Click to expand...
Click to collapse
Did flashing cos13 fixed the issue? I'm also facing the same issue
piez97 said:
Did flashing cos13 fixed the issue? I'm also facing the same issue
Click to expand...
Click to collapse
flashing and all is time waste. If u r facing similar issue as quoted by me then its a battery problem. if your battery is not changed till now and old one around 2 years or more pls change it.
I wasted lot of time in flashing and lost all my data. I wish someone would have helped me with battery change suggestion. all the best..
praveen4u13 said:
flashing and all is time waste. If u r facing similar issue as quoted by me then its a battery problem. if your battery is not changed till now and old one around 2 years or more pls change it.
I wasted lot of time in flashing and lost all my data. I wish someone would have helped me with battery change suggestion. all the best..
Click to expand...
Click to collapse
But the sad truth is we can't get any original / as good as original replacement. Oneplus stopped production 2years ago. I did a quick google search and found out most of the batteries are ****. As you're name suggests, I think you're from India. Can you please inform me if you find any decent batteries? I will inform you if I find anything good.
Thx
piez97 said:
Did flashing cos13 fixed the issue? I'm also facing the same issue
Click to expand...
Click to collapse
piez97 said:
But the sad truth is we can't get any original / as good as original replacement. Oneplus stopped production 2years ago. I did a quick google search and found out most of the batteries are ****. As you're name suggests, I think you're from India. Can you please inform me if you find any decent batteries? I will inform you if I find anything good.
Thx
Click to expand...
Click to collapse
yes I am from India. I would suggest you first try with replacement battery as everyone sell replacement battery. you can find any of these in ebay. In India Oneplus is ready to arrange a original one costing Rs 1800. They asked me for a week time to arrange original battery. So its upto u to decide to take new one or replacement.
praveen4u13 said:
yes I am from India. I would suggest you first try with replacement battery as everyone sell replacement battery. you can find any of these in ebay. In India Oneplus is ready to arrange a original one costing Rs 1800. They asked me for a week time to arrange original battery. So its upto u to decide to take new one or replacement.
Click to expand...
Click to collapse
I contacted my nearest customer care. They said that they have to analyze the phone and it would take almost 15 days. Did you get a new battery?
praveen4u13 said:
bro one more issue started yesterday. I thought to making battery full nil and charge to 100% may help.
Before without charging connected I was able to go in twrp but not now. if i remove charging its going to restart even recovery mode also. When I went to restore old backup in TWRP mobile is auto starting even when charger is connected. but if i dont do anything its staying fine in TWRP lock screen.
without charging connected i can go into fastboot n stay for as long as i want but comp is not detecting mobile even though developer option is ON.
Yesterday thought of restoring old backup which interrupted half within 1min and now if i start mobile while charging its getting struk at 1+1 welcome screen.
I am fully confused like anything..
Click to expand...
Click to collapse
Same issue, start from 3 days ago...
Without charger or power bank i can't use phone [emoji19]
My phone is old around 2.5+ year
Sent from my A0001 using Tapatalk
Me too having the same issue. Seems like OnePlus one devices have some kind of kill switch to ruin it after 2.5 years. Quite a few number of people seems to have this issue all of a sudden.
after update experienced problem with BLOD.
after freezing I've managed to boot but for short time.
is there any fix that available like for nexus6p and nexus5x?
Can you get to fastboot/bootloader?
yes, except bootloader locked. can't get enough time to unlock it in settings
Tried to boot recovery from bootloader? I believe it's possible to flash a full ota image with lock bootloader, but someone correct me if i am wrong.
Cheers
Sent from my Google Pixel using XDA Labs
thanks for suggesting, but it wouldn't fix the phone. in order to get to recovery i still have to heat up phone to start appropriately
guotti said:
thanks for suggesting, but it wouldn't fix the phone. in order to get to recovery i still have to heat up phone to start appropriately
Click to expand...
Click to collapse
Have you uhhhhhhhh /tried it/
KittyRgnarok said:
Have you uhhhhhhhh /tried it/
Click to expand...
Click to collapse
yes, the phone reboots before finish
So, it is heating when you try booting bootloader and then recovery?
Sent from my Google Pixel using XDA Labs
yep, it won't start without heating
So it's heating itself even when booted to only bootloader?
That's very weird, never heard of that before.
When that's the case, maybe it's time for a replacement
Any warranty left maybe?
Sent from my Google Pixel using XDA Labs
Sgace said:
Tried to boot recovery from bootloader? I believe it's possible to flash a full ota image with lock bootloader, but someone correct me if i am wrong.
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Cosmic Radiation said:
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Click to expand...
Click to collapse
If it's bootlooping, how did you see OEM unlock is greyed out?
Sent from my Google Pixel using XDA Labs
Cosmic Radiation said:
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Click to expand...
Click to collapse
I have 2 Pixels that both have the same symptom. I was lucky enough to get them to boot so I could unlock the bootloader, but flashing the factory image didn't make any difference. Based on what I've seen on the Google forums, it appears some of theses devices have faulty memory which is most likely the cause of the bootloop. Both of mine have Samsung memory. I'd be curious if your device does as well.
Sgace said:
If it's bootlooping, how did you see OEM unlock is greyed out?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
jman315 said:
I have 2 Pixels that both have the same symptom. I was lucky enough to get them to boot so I could unlock the bootloader, but flashing the factory image didn't make any difference. Based on what I've seen on the Google forums, it appears some of theses devices have faulty memory which is most likely the cause of the bootloop. Both of mine have Samsung memory. I'd be curious if your device does as well.
Click to expand...
Click to collapse
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Cosmic Radiation said:
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Click to expand...
Click to collapse
Do you have a Verizon pixel maybe? Cause OEM unlock should not be grayed out, even with locked bootloader.
Sent from my Google Pixel using XDA Labs
Cosmic Radiation said:
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Click to expand...
Click to collapse
No, neither device is reliable or usable. Sometimes after it's been off for a while, it will power on and be functional for a short period of time. If the memory is faulty, then I believe the motherboard has to be replaced which isn't worth the cost of the repair. I may contact google support and see if they may give me a trade in credit for a pixel 2 or 3.
my pixel turned out to be verizon, i was able to unlock bootloader and flash a factory image.. The problem still exists. Bootloops are still happening:crying:
Cosmic Radiation said:
my pixel turned out to be verizon, i was able to unlock bootloader and flash a factory image.. The problem still exists. Bootloops are still happening:crying:
Click to expand...
Click to collapse
Yep. Same issue here. Our devices are likely paperweights I'm afraid.
Can confirm, I woke up to an infinite bootloop this morning after applying the December security patch. Seems to be a hardware issue that just kills the phone.
Have you guys have tried to cool the phone down like putting it on top of an ice bag with saltwater, like a zip lock bag, give it a minute on top of the brine and then try? Should give you some time until you can get into the rom and tap the unlock button?
Hi everyone, I have a quite frustrating problem. My PIN changed itself. Probably after updating to Android 14 Beta 1.1.
Thanfully I have a fingerprint that is recognized. But if I accidentally reboot or battery dies there's the risk... Is there any chance to fix it witthout resetting the phone?
zipredictive said:
Hi everyone, I have a quite frustrating problem. My PIN changed itself. Probably after updating to Android 14 Beta 1.1.
Thanfully I have a fingerprint that is recognized. But if I accidentally reboot or battery dies there's the risk... Is there any chance to fix it witthout resetting the phone?
Click to expand...
Click to collapse
Look here. Let me know if it doesn't work!
What a mess guys, I've backuped everything. Tried to reboot and...
NOS Production error and a device state: error state!
I've read everywhere ant it seems there's no way to fix.
Frustrated.
I've tried everything reflashed stock images ecc but....
zipredictive said:
What a mess guys, I've backuped everything. Tried to reboot and...
NOS Production error and a device state: error state!
I've read everywhere ant it seems there's no way to fix.
Frustrated.
I've tried everything reflashed stock images ecc but....
Click to expand...
Click to collapse
What happened when you flashed the stock ROM?
ethical_haquer said:
What happened when you flashed then stock ROM?
Click to expand...
Click to collapse
It's not correct what I have written. I meant "I 've tried "reflashing", not reflashed. There are some posts here in xda but few solutions.
https://forum.xda-developers.com/t/solved-help-needed-pixel-6-stuck-in-fastboot-mode.4508561/
I could have sent my pixel for rma but some months ago it fell and the back of the phone crashed. So no rma, they told me that they can fix the brick problem but I have to pay for the back phone repair. 140 € better than nothing.
zipredictive said:
It's not correct what I have written. I meant "I 've tried "reflashing", not reflashed. There are some posts here in xda but few solutions.
https://forum.xda-developers.com/t/solved-help-needed-pixel-6-stuck-in-fastboot-mode.4508561/
I could have sent my pixel for rma but some months ago it fell and the back of the phone crashed. So no rma, they told me that they can fix the brick problem but I have to pay for the back phone repair. 140 € better than nothing.
Click to expand...
Click to collapse
zipredictive said:
"I 've tried "reflashing"
Click to expand...
Click to collapse
I know, but what happened when you tried? What errors did you get?
ethical_haquer said:
I know, but what happened when you tried? What errors did you get?
Click to expand...
Click to collapse
failed to get unlock ability -1