Hello,
First of all, sorry for my bad english, i'm french and not very good
Thanks for reading me and the help you give me on xda (even if i never post, i always find my solution on the forums )
I'm actually on CM13 6.0.1 20160810 beta, working quite good since then, but my system is going completely drunk, my sim is not working any more (only my sim), wifi problems etc.
Factory reset is a solution but i have to setup again all my apps, so I want to update to 7.1.1 and then setup all my apps on a new rom without the bugs i used to.
I create this thread because i tried to install MAD Team aosp 7.1.1, stable 7 and also stable 8 and succeeded, but bluetooth is not working...
The problem i have is when i install this rom, bluetooth is written as "Disabled", and when i turn it on, it stays greyed 10 seconds and returns to OFF.
I tried many things :
-install starting from CM13 with factory reset
-install starting from CM13 without factory reset
-install starting from CM13 with format data
-install official 5.1 after factory reset + format data, then install 7.1.1
-factory reset after installing 7.1.1 with all methods over
I'm out of ideas, not finding useful things on the web, even on XDA threads :crying:
It's not hardware problem, my BT works perfectly on CM13 actually, and when I reinstall CM13 after a 7.1.1 fail (with or without restoring my data), it works again...
If you have any idea, i'm desperate :fingers-crossed:
Thanks for your help
I had the same problem the first time I enabled Bluetooth, but rebooted the phone (just one time) worked. Now Bluetooth works perfectly.
Thanks for your quick answer, I tried it this morning but no result.. :crying:
Related
Stuck at "Checking connection" screen. Tried all the options. No luck. Pls help.!
Hello,
I have tried to flash Android Open Source Project 5.1, BlissPop, crDroid. I have been using Android Open source project 5.1. I tried to flash BlissPop and it started this issue. I have no idea for my next steps. My phone is down since last two days so thought to come here for help.
Steps I tried.
1) Removed Data, cache, Internal storage, system and Dalvik cache. Flashed new ROM and GApps.
2) Tried to re-connect wifi at "Checking connection" stage and rebooting device again and again.
Any help would be appreciated.
Thanks in advance.
DhavalVyas said:
Hello,
I have tried to flash Android Open Source Project 5.1, BlissPop, crDroid. I have been using Android Open source project 5.1. I tried to flash BlissPop and it started this issue. I have no idea for my next steps. My phone is down since last two days so thought to come here for help.
Steps I tried.
1) Removed Data, cache, Internal storage, system and Dalvik cache. Flashed new ROM and GApps.
2) Tried to re-connect wifi at "Checking connection" stage and rebooting device again and again.
Any help would be appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Serious ? You only tried these 2 steps and looking at a dead phone for 2 days,lol.
Why you dont take the time to try restore your stock image or find another custom rom based on marshmallow.
Seems like the roms your trying are outdated.
Sickaxis79 said:
Serious ? You only tried these 2 steps and looking at a dead phone for 2 days,lol.
Why you dont take the time to try restore your stock image or find another custom rom based on marshmallow.
Seems like the roms your trying are outdated.
Click to expand...
Click to collapse
Thanks for the response. The thing is I got busy with another event so didn't work much. But I will re-install stock OS first and see if it works or not. After that, i will try other custom ROMs.
Hey guys!
In the last week my wifi&BT stopped working suddenly, without any software change or new app installed. e.g. (when I swipe wifi, it looks like it is working, but cannot find any network)
mobile data still functions.
After reading quite a lot of manuals, I understood it might be a hardware malfunction, However, I tried to do few things already to understand if there might be another reason, none of the below worked
-Play with aeroplane mode and wifi.
-wifi fix applications
-Factory data reset.
-Wipe the phone and flash oxygen 3.1.0 via TWRP.
Before giving up, Wanted to ask if you have any advice that might help:
Any customized room that might will work?
Any way to check the phone log to understand what happens when we do it?
Any general advice?
Thanks in advance!
E.
try this rom
follow the guide completely
http://forum.xda-developers.com/oneplus-2/general/rom-hydrogenos-v1-2-0-sensors-t3264711
araaraara123 said:
Hey guys!
In the last week my wifi&BT stopped working suddenly, without any software change or new app installed. e.g. (when I swipe wifi, it looks like it is working, but cannot find any network)
mobile data still functions.
After reading quite a lot of manuals, I understood it might be a hardware malfunction, However, I tried to do few things already to understand if there might be another reason, none of the below worked
-Play with aeroplane mode and wifi.
-wifi fix applications
-Factory data reset.
-Wipe the phone and flash oxygen 3.1.0 via TWRP.
Before giving up, Wanted to ask if you have any advice that might help:
Any customized room that might will work?
Any way to check the phone log to understand what happens when we do it?
Any general advice?
Thanks in advance!
E.
Click to expand...
Click to collapse
Earlier today, my fingerprint sensor/home button completely stopped working.
I tried restarting, wiping cache and dalvik cache, re-installing the ROM, and I even went back to OOS and H2OS (both stock ROMs) to see if it would work. Alas, nothing worked.
A friend of mine then called me. I told him my home button is dead. He told me it happened to him once, and all he had to do was force restart the phone and it worked again.
I'll suggest that you try the same.
Hold the power button for ten seconds while your phone is on and it'll force restart.
Hope this fixes your problems, mate!
Hello Guys,
pls help me.. after flashing cm13 RR ... when i m installing watsapp .. bootloop occurs.. camera 360 as well, i flashed stock fimware and the flashed cm13 rr ..but no luck
same problem
I have pretty much the same issue but it's not exclusive to whatsapp, other apps send the phone into a bootloop as well, this started a while ago, I installed the cm12 last year or so and it worked great for a long time, then after a while I tried to install the spotify app and things went south, phone went into bootloop so I deleted it from recovery mode and just ignored the issue. Yesterday I installed the cm13 hoping I would get a clean slate, I did everything right, full wipe, flashed the rom, gapps, patch and front cam fix and although everything kept crashing at first ( google launcher and pixel launcher) I eventually got it working, I installed messenger, worked fine, then tried to install whatsapp and it went into a bootloop. Anyone please help us.
DarudeNotSandstorm said:
I have pretty much the same issue but it's not exclusive to whatsapp, other apps send the phone into a bootloop as well, this started a while ago, I installed the cm12 last year or so and it worked great for a long time, then after a while I tried to install the spotify app and things went south, phone went into bootloop so I deleted it from recovery mode and just ignored the issue. Yesterday I installed the cm13 hoping I would get a clean slate, I did everything right, full wipe, flashed the rom, gapps, patch and front cam fix and although everything kept crashing at first ( google launcher and pixel launcher) I eventually got it working, I installed messenger, worked fine, then tried to install whatsapp and it went into a bootloop. Anyone please help us.
Click to expand...
Click to collapse
exactly.. we were on same page .. pls any one help us
I have the same issue on CM12. Phone get stuck in boot-loop after installing whatsapp latest version. I was able to get out of boot-loop after I deleted whatsapp app.
Its very important to use whatsapp. Please any fix for this?
I couldn't find a fix. The best you can do move to nougat ROMs like aicp or crdroid.
I installed crdroid and it's excellent
I too am now stuck on boot loop due to Whatsapp.
I do not need this app and will happily delete it, if this is what is causing the issues, but my problem is, how do I delete it now that I am stuck in a boot loop?
Enter safe mode and delete the app.
It's better to remove cm12 and install new ROM crdriod
GalaxyNote2_ said:
Enter safe mode and delete the app.
It's better to remove cm12 and install new ROM crdriod
Click to expand...
Click to collapse
Thanks for the reply.
This may sound a bit noob, but how do I get it into safe mode?
I have an Xperia Mini Pro SK17i
I managed to get it into recovery mode earlier, but cannot seem to get into safe mode
Yeah!
It happens in 5.1 / 6 custom roms!
Can any body help ??!!!
You need to read this thread. Every CM rom compiled before 2018 will have this problem.
https://forum.xda-developers.com/showpost.php?p=75391884&postcount=18
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
GTF696 said:
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
Click to expand...
Click to collapse
Try magisk as root method insted of su...
Other than that, cant think any other solution
GTF696 said:
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
Click to expand...
Click to collapse
I got error when installed lineageos15.0 on twrp 3.2.3 , suddenly automatic restart. Can you help me dude ?
Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.
Up :good:
When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !