yashsingh1/xdaforums huggingface dataset:
[Google Pixel Questions & Answers] Jiggly_Jellyfish:
Hello everyone,

I purchased a used google pixel from eBay about a month ago, and I have used it happily ever since, until this past saturday. I use my device with 2 bluetooth devices constantly, a medical device (dexcom) that connects every 5 minutes, and a raspberry pi, which is always connected via bluetooth tethering. I had very reliable connections to both devices 24/7, until suddenly I started getting the message: 'Bluetooth keeps stopping.'

[IMG="the error message"]https://imgur.com/a/TAanHax[/IMG]

whenever this happened, it would turn off bluetooth tethering and then turn off bluetooth altogether. I would try to press the bluetooth icon to turn it back on, but it would aggressively turn it back off again. After several frustrating minutes, it would sometimes go back to normal and work just fine for 2 minutes-8 hours. But this error started appearing more and more often, to the point that my devices became useless, because they were never connected to my phone for a reasonable amount of time (and even then only because I was manually turning bluetooth back on over and over.)

I...

tried changing the dexcom app settings

tried forgetting dexcom device then re-pairing

tried turning off bluetooth tethering

tried turning off the raspberry pi

tried clearing the bluetooth cache

tried clearing bluetooth data

tried restarting the device more times than I can count

nothing at all worked. per the suggestion of one of my developer friends, I ran adb tools on my computer to see what was going on in the HCI bluetooth logs. According to what he said, it looks like it is trying to connect to Bluetooth headset service, failing, crashing, and disconnecting from all bluetooth devices. We decided to eliminate all variables, it would be best to factory reset the device and carefully install only my important medical apps first, then slowly any other apps over a period of days to see if the culprit became obvious.

So I performed a factory reset. I logged into my wifi, then was about to log into google, when...

[IMG="error message after factory reset"]https://imgur.com/a/JOr5nRS[/IMG]

the same message, popping up constantly, after a factory reset!

at this point I was almost convinced it was a hardware problem, until I heard some others have had the same issue due to their android version. But I have used 9.0 Pie ever since I got the phone, so that still doesn't make sense to me.

Please let me know if you have any solutions, ideas, or suggestions. If you want more screenshots, more information, or anything like that then please ask and I will try to post it. Thank you.

edit: since I am a new user, the image links aren't working. Basically, they both say

'Bluetooth keeps stopping

(i) App info

(x) Close app

(!) Send feedback'

edit 2: I also tried rebooting in safe mode, still getting the same 'bluetooth has stopped' message
[Google Pixel Questions & Answers] jmaclean62:
I'm having the same exact problem on my daughters phone
[Google Pixel Questions & Answers] ducdh0415:
Guys, I had this problem, I found the "solution" to the floating bluetooth error message, but I can't activate it since it starts to fail again.

What I did was the following: activate and deactivate the bluetooh from the notification panel, waiting for at least 5 notifications of bluetooth error to come out, then blocked the cell phone for a few minutes and I can use it quietly. By the way, you should not restart it or turn it off or it will fail again.
[Google Pixel Questions & Answers] Meatbag_1:
I was also having the problem. I tried everything. Still not right.
[Google Pixel Questions & Answers] scandiun:
You have to report the issue to LineageOS GitLab issues. Apparently dozens of users are having the bluetooth issue with latest version LineageOS 16.0 but now with older versions.
[Google Pixel Questions & Answers] jmaclean62:
I'm having the same problem with my Pixel phone as well. Has anyone figured out away to stop the error yet? Is it software that could be fixed by reverting back to an old version of Android. Mine started right after updating to Android 10. Any ROMS that eliminate the problem? I'd be happy with just being able to turn off Bluetooth so that I don't get the error.
[Google Pixel Questions & Answers] scandiun:
Try flashing stock rom again, in case some weird bluetooth driver need to be installed on some hidden partition.
[Moto Z2 Force  Questions & Answers] ben0551:
I am running stock Z2 Force RET CHINA from coolicool

device is not certified... is this normal for the Z2?

I cannot run Google Play as it says the device is rooted... but it's not and have checked with root checkers. Also having some issues with other apps which I think may be related.

Cheeers
[Moto Z2 Force  Questions & Answers] ben0551:
I was supplied with an unlocked bootloader. Hmmm.
[Moto Z2 Force  Questions & Answers] Uzephi:
This phone does have the cmdline flag for bootloader being unlocked. This would make your device fail CTS check so you won't be certified.
[Moto Z2 Force  Questions & Answers] Snorlaks:
Mine said the same. But after flashing original global ROM, it says 'certified'.
[Moto G4 Plus Questions & Answers] herbao:
friends, I have xt1640, after it upgraded to android 8.1, the cell phone ran out of network service, I downgraded, and nothing ...:confused:
[Moto G4 Plus Questions & Answers] echo92:
What does your baseband report in Settings>About phone? Do you see your IMEI in Settings as well?

A side note, if you've downgraded, do not use stock OTA updates. You'll hard brick your device else, and the fix is expensive.
[Moto G4 Plus Questions & Answers] herbao:
the mobile was working perfectly ... after it updated via OTA, for 8.1 it was out of service, the baseband is ok, when I'm going to call it it says to disable the airplane mode
[Moto G4 Plus Questions & Answers] echo92:
Hmm, that's odd - did you try to re-flash the Oreo stock firmware? https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

When you downgraded, did you erase modemst1 and modemst2? Have you verified your IMEI is present and your SIM card is still working (i.e. try it in another device) and you do not have network issues?
[Moto G4 Plus Questions & Answers] herbao:
I did not delete the modemst, the imei is showing up !! I was researching, and I saw that there are some people with the same problem ...
[Moto G4 Plus Questions & Answers] echo92:
I'm not sure if your Oreo modemst would be working with your Nougat baseband if you're still downgraded. You might like to backup your modemst with Lyuu's TWRP (back up your EFS) and then try erasing modemst. The Oreo OTA update would have erased the modemst1/modemst2 (EFS) as part of its update.
[Moto G4 Plus Questions & Answers] herbao:
Okay, I installed twrp, to try to backup efs, but the partition does not appear to back up ... could you help me?

I'm using google translate. Brazil
[Moto G4 Plus Questions & Answers] echo92:
Did you flash Lyuu's TWRP as I mentioned? https://xdaforums.com/moto-g4-plus/development/recovery-team-win-recovery-project-t3842903 Other TWRP recoveries may not be able to back up this partition.
[Moto G4 Plus Questions & Answers] herbao:
Okay, I'll do it tomorrow morning and post the result, so I backup efs, I delete the modemst partition, and install the 8.1 stockrom, right? I do not do it now, because of the schedule, it's already late here, but thanks for your attention,
[Moto G4 Plus Questions & Answers] echo92:
Yeah - so the plan is:

1)Backup your EFS (though it might be already damaged, might as well keep it safe).

2)Erase modemst1/modemst2 via fastboot. Reboot. Test if SIM service is working. Check IMEI and baseband (baseband should be reporting ATHENE_BRAZIL_DSDS_CUST, and ending in 77R if on Oreo, .62.02R if on April 2018 stock Nougat).

3)If device is still not in service, flash stock Oreo firmware. You do not need to re-lock, so you could omit the fastboot OEM lock begin commands to avoid locking the bootloader.
[Moto G4 Plus Questions & Answers] herbao:
friend I did what you asked me, and it did not work, I sent you a print for you to see

https://uploaddeimagens.com.br/imagens/g4-jpg-f5886a19-b5f6-4d4a-83b7-bb6b77bde02c
[Moto G4 Plus Questions & Answers] echo92:
Your baseband, modern or fsg is corrupted, it is reporting DFLT_FSG as the suffix - for your device, it should be reporting ATHENE_BRAZIL_DSDS_CUST or similar. Your baseband clearly is not okay, was it DFLT_FSG also when you updated to Oreo via OTA?

You could try this https://xdaforums.com/moto-g4/how-to/baseband-change-t3762270
[Moto G4 Plus Questions & Answers] herbao:
was updated on the 28th, how can I recover ??
[Moto G4 Plus Questions & Answers] echo92:
I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?

You could try:

Download the factory firmware here: https://xdaforums.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.

Extract the firmware, and open the extracted firmware folder.

Find the programutags.bat in the folder.

Run the .bat script and follow the instructions.

Credit to: https://xdaforums.com/moto-g4/how-to/baseband-change-t3762270
[Moto G4 Plus Questions & Answers] herbao:
Brother, you saved me ... Thank you.
[Moto G4 Plus Questions & Answers] pasinirs:
Dude, you're a god. I looked all over the internet for this solution, I do not believe it really worked!
[Moto G4 Plus Questions & Answers] Tetcare99:
Can I do this now because recently recovered my phone 8.1.0

---------- Post added at 04:47 PM ---------- Previous post was at 04:40 PM ----------

Password please...

---------- Post added at 04:57 PM ---------- Previous post was at 04:47 PM ----------

This file asking password bro...please tell me

---------- Post added at 05:13 PM ---------- Previous post was at 04:57 PM ----------

This file extract with winRAR.it showing all errors

And extract the file 7zip aslo all files error

Bro

---------- Post added at 05:13 PM ---------- Previous post was at 05:13 PM ----------

I can't extract it
[Moto G4 Plus Questions & Answers] echo92:
1) you should be able to use this procedure, this thread you're replying in had a similar scenario to you.

2) make sure the firmware you've downloaded is the correct size. I've just checked and it's 893 MB in size. The first download I tried failed towards the end.

3)I used the app 7-zipper, with the password lenovo-forums.ru and it seemed to work. Not sure why you're having trouble extracting the files, I'd try to redownload the firmware. I don't know if the script on its own works or if you need the full firmware.

Also, please note these are not real time forums, repeatedly posting will not necessarily make a member post any faster. I get you're frustrated by your device only partially working, please be patient.
[Moto G4 Plus Questions & Answers] Tetcare99:
1 - LATAM

2 - APAC

3 - Canada

4 - US

5 - EMEA

6 - QUIT

please select region : 2

A - Retail APAC

B - Retail India

C - Quit

Please select carrier : B

Waiting for fastboot enumeration...

Still waiting.....

Do you by any chance have a JTAG flex attached?

If so , detach the JTAG flex and try again

Still waiting.....

Do you by any chance have a JTAG flex attached?

If so , detach the JTAG flex and try again

Still waiting.....

Do you by any chance have a JTAG flex attached?

If so , detach the JTAG flex and try again

Still waiting.....

Do you by any chance have a JTAG flex attached?

If so , detach the JTAG flex and try again

Bro..:crying::crying:
[Moto G4 Plus Questions & Answers] echo92:
Was your device booted to fastboot for this procedure, as requested by the script? Does your device properly communicate with your computer in fastboot (i.e. if you type fastboot devices into an ADB terminal, does your device respond with its serial number)?
[Moto G4 Plus Questions & Answers] Tetcare99:
I did it but there is no changes:crying:
[Moto G4 Plus Questions & Answers] echo92:
Still no signal? Can I see the results of the persist check from step 1 and step 2 of the IMEI thread please, as previously asked for?
[Moto G4 Plus Questions & Answers] Tetcare99:
It's showing something bro..

athene_f:/ $ su

athene_f:/ # chown -R rfs:rfs/persist/rfs

See chown --help

chown: Need 2 arguments

1|athene_f:/ # chown -R rfs:rfs_shared/persist/hlos/rfs

See chown --help

chown: Need 2 arguments

1|athene_f:/ # chown -R 3012:3012/persist/rfs

See chown --help

chown: Need 2 arguments

1|athene_f:/ # chown -R 3012:3013/persist/hlos_rfs

See chown --help

chown: Need 2 arguments

1|athene_f:/ #

---------- Post added at 01:35 PM ---------- Previous post was at 01:31 PM ----------

athene_f:/ $ su

athene_f:/ # chown -R rfs:rfs/persist/rfs

See chown --help

chown: Need 2 arguments

1|athene_f:/ # chown -R rfs:rfs_shared/persist/hlos/rfs

See chown --help

chown: Need 2 arguments

1|athene_f:/ # chown -R 3012:3012/persist/rfs

See chown --help

chown: Need 2 arguments

1|athene_f:/ # chown -R 3012:3013/persist/hlos_rfs

See chown --help

chown: Need 2 arguments

1|athene_f:/ #
[Moto G4 Plus Questions & Answers] echo92:
That doesn't look like steps 1 or 2, that looks like step 3, which was not what I requested. I asked for the output from the:

ls -l /persist

AND

find /persist -type f

commands as listed in steps 1 and 2:

Not sure if there's something that is not understood.
[Moto G4 Plus Questions & Answers] Tetcare99:
Here the results bro

athene_f:/ $ su

athene_f:/ # Is -I /persist

/system/bin/sh: Is: not found

127|athene_f:/ # ls -l/persist

See ls --help

ls: Unknown option /persist

1|athene_f:/ # ls -l /persist

total 96

drwxrwx--- 2 system system 4096 1970-02-07 22:53 alarmdrwxr-xr-x 2 mot_pwric mot_pwric 4096 1969-12-31 19:02 batt_health

drwxrwx--- 2 bluetooth bluetooth 4096 2018-01-22 22:58 bluetooth

drwxr-xr-x 2 mot_tcmd bluetooth 4096 1969-12-31 19:02 bt

drwxr-xr-x 4 mot_tcmd mot_tcmd 4096 1970-02-07 22:52 camera

drwxr-xr-x 2 root root 4096 1970-02-07 22:52 coresight

drwx------ 4 system system 4096 1970-02-07 22:52 data

drwxrwx--- 2 system graphics 4096 1969-12-31 19:02 display

drwxrwx--- 2 system system 4096 1969-12-31 19:02 drm

drwxr-xr-x 4 mot_tcmd mot_tcmd 4096 1970-02-07 22:52 factory

drwxrwx--- 3 system system 4096 1970-02-07 22:52 hlos_rfs

drwxrwx--- 2 root root 4096 1970-02-07 22:52 lost+found

drwxrwx--- 2 radio radio 4096 1970-02-07 22:52 mdm

drwxrwx--- 2 system system 4096 1970-02-07 22:53 misc

drwxrwx--- 2 system system 4096 1970-07-07 05:32 properties

drwxr-xr-x 8 mot_tcmd mot_tcmd 4096 1970-02-07 22:52 public

drwx------ 6 system system 4096 1970-02-07 22:52 rfs

drwxrwx--- 2 system system 4096 1970-01-03 15:34 secnvm

drwxrws--- 2 drmrpc drmrpc 4096 1969-12-31 19:02 security

drwxrwxr-x 3 system system 4096 1970-01-03 15:34 sensors

drwxrwx--- 2 system system 4096 2019-01-29 13:09 time

drwxrwx--- 2 media media 4096 1970-01-03 15:34 vpp

drwxr-xr-x 2 mot_tcmd mot_tcmd 4096 1969-12-31 19:02 wifi

drwxrwxr-x 2 mot_drm mot_drm 4096 1969-12-31 19:02 wmdrmathene_f:/ # find /persist-type f

find: /persist-type: No such file or directory

find: f: No such file or directory

1|athene_f:/ # find /persist -type f

/persist/coresight/qdss.agent.sh

/persist/coresight/qdss.config.sh

/persist/coresight/qdss.functions.sh

/persist/sensors/sensors_settings

/persist/data/tz/tz_counter

/persist/data/tz/tz_counter.bak

/persist/camera/focus/offset_cal

/persist/camera/ledcal/rear

/persist/factory/audio/temp

/persist/factory/audio/cnt

/persist/factory/audio/acc

/persist/factory/audio/f0

/persist/factory/audio/ref_diff

/persist/factory/fti

/persist/public/hiddenmenu/data/mobile_data_rx

/persist/public/hiddenmenu/data/mobile_data_tx

/persist/public/hiddenmenu/data/wifi_data_rx

/persist/public/hiddenmenu/data/wifi_data_tx

/persist/public/hiddenmenu/data/activation_date

/persist/public/hiddenmenu/life_calls

/persist/public/hiddenmenu/life_timer

/persist/mdm/oma_dm_update

/persist/rfs/shared/server_info.txt

/persist/rfs/msm/mpss/safe/sfs/uim/simlock/config

/persist/rfs/msm/mpss/server_check.txt

/persist/rfs/msm/mpss/dhob.bin

/persist/rfs/msm/mpss/shob.bin

/persist/rfs/msm/adsp/server_check.txt

/persist/.bt_nv.bin

/persist/bluetooth/.bt_nv.bin

/persist/time/ats_1

/persist/time/ats_2

/persist/time/ats_16

athene_f:/ #
[Moto G4 Plus Questions & Answers] Tetcare99:
Bro...
[Moto G4 Plus Questions & Answers] echo92:
Thanks for that - your persist permissions look to be okay. For some reason your device appears to have fewer entries related to persist than other devices' entries I've seen. Not sure how that happened, any ideas [MENTION=6490709]Heeth21[/MENTION] ?

I'll have a look at what my device reports in terms of persist.

---------- Post added at 08:23 PM ---------- Previous post was at 08:14 PM ----------

Yup, what were you asking about?
[Moto G4 Plus Questions & Answers] Tetcare99:
1.imei numbers issue

2.sims not detecting

These are major issue in my mobile
[Moto G4 Plus Questions & Answers] echo92:
I'm aware of that, I was asking what you posted 'bro' for?
[Moto G4 Plus Questions & Answers] Tetcare99:
Just asking Have you seen my post or not?

That's why I am calling you bro.
[Moto G4 Plus Questions & Answers] echo92:
I saw your post when I had the time to view it and reply, especially since now we've got the info. I understand you're frustrated, and want to get your device fixed. Be patient please, I'm trying to figure out what's happened to your device's IMEI and network, given the usual fixes aren't working, and without knowing what happened before you hard bricked your device as well. Posting 'bro' and repeatedly not reading information is not helping. I don't know if the blankflash did anything (unlikely) or if there was a bad flash. Hopefully heeth21 or others can comment with their experience on your persist partition and offer other fixes.
[Moto G4 Plus Questions & Answers] HeethJain21:
Yes, somehow there has been some changes with the persist file.

The persist is missing "id_00" and "id_01" which is present in "/persist/rfs/msm/mpss/datablock/" directory.

The IMEIs are stored in "id_00" and "id_01" and somehow (maybe some arithmetic operation or something else) with the help of "dhob.bin" and "shob.bin", the IMEIs are generated.

I believe chances are that [MENTION=9683444]Tetcare99[/MENTION] has restored some other device's persist from some Youtube video or some Internet forums, as the persist floating there does have "id_00" and "id_01" missing with a lot of other directories and files as well.

What are your IMEI/s right now? Are they 0?

And what is your baseband version seen from Settings>About Phone
[Moto G4 Plus Questions & Answers] Tetcare99:
Imei =0

Basband version:M8952_700.30.25.03.77a ATHENE_INDIA_DSDS_CUST
[Moto G4 Plus Questions & Answers] HeethJain21:
Did you restore some other device's persist from some Youtube video or internet guide??

It doesn't seem to be the case since the baseband is ending with "a" which has been reported earlier as well and the current IMEI solution doesn't work with this baseband
[Moto G4 Plus Questions & Answers] Tetcare99:
I did it bro .

But there is no changes appears.

I did download persist file from xda forum.
[Moto G4 Plus Questions & Answers] HeethJain21:
Well that's the problems.

You used the persist file available on XDA.

Persist is unique to every device out there.

If you have backup of "YOUR" own persist then please restore it and IMEI will be recovered.
[Moto G4 Plus Questions & Answers] Tetcare99:
I don't have any backup persist file bro..I did back up system file like
[Moto G4 Plus Questions & Answers] echo92:
Just to clarify, by persist file you downloaded, do you mean the persist repair zip from the IMEI fix thread, or an actual persist image?
[Moto G4 Plus Questions & Answers] Tetcare99:
Actually I did search for persist file in my phone but I can't find it .after that I did install persist file using twrp.that persist downloaded from xda thread
[Moto G4 Plus Questions & Answers] echo92:
My question is this persist file that you downloaded - is it the persist TWRP fix (from the IMEI=0 thread), or a persist image that you downloaded from XDA?

If you used the persist TWRP fix, then you might still be able to fix your device. If you downloaded someone else's persist image and flashed that, we might not be able to fix your device. There's a very important distinction between the two files, please clarify which file you downloaded and from which thread you used.
[Moto G4 Plus Questions & Answers] Tetcare99:
I downloaded persist file from xda. this is the thread @https://xdaforums.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068 page 1
[Moto G4 Plus Questions & Answers] Tetcare99:
I confidently say that this file I did installed
[Moto G4 Plus Questions & Answers] echo92:
If you've flashed stock Oreo 8.1, that file might not do much since your permissions should be updated. It won't hurt though.

You're certain you did not flash any other persist images whilst trying to fix your device? Just that your persist files list looked unusual as heeth21 mentioned
[Moto G4 Plus Questions & Answers] echo92:
Hmm, I just loaded up the persist details from my device and comparing them to your device, there seem to be quite a few things missing. I do not know if that's expected or if something happened to your persist from the earlier flashes/attempts to repair. However, I cannot advise you to flash the persist image from my device - doing so would mean losing the persist image unique to your device and make it impossible to repair unless you made a backup. (Note again, I do not mean the TWRP persist fix file - that is okay to flash since all it does is repair permissions. I am referring to a persist image obtained from another device, which is flashed over your device's persist image that causes these issues.) For reference, I've posted my persist and the files that seem to be missing/different to yours are in bold formatting:

athene_f:/ # find /persist -type f
/persist/coresight/qdss.agent.sh
/persist/coresight/qdss.config.sh
/persist/coresight/qdss.functions.sh
/persist/sensors/sensors_settings
[B]/persist/data/sfs/7mLKiiOHb38oWJOzMMgT1MJTuc8_
/persist/data/sfs/okknld0N60fHVxB75aMrYq7zPfo_
/persist/data/sfs/Gzq2vgdYuPNmo2ogNpKaWoxHA0g_
/persist/data/sfs/4GActXHfqptJhhS7vCRMKD+0o+4_
/persist/data/sfs/aOrpxVxYpTOmCc-fuhWWMcviurM_
/persist/data/sfs/CjqM3QO0MLXGyjpByH6FdPMKnQw_
/persist/data/sfs/V099eO8L1QQNgWO5y9Uycia-3Lk_
[/B]/persist/data/tz/tz_counter
/persist/data/tz/tz_counter.bak
/persist/data/app_g/wv_usage
/persist/camera/focus/offset_cal
/persist/camera/ledcal/rear
/persist/factory/audio/temp
/persist/factory/audio/cnt
/persist/factory/audio/acc
/persist/factory/audio/f0
/persist/factory/audio/ref_diff
/persist/factory/fti
/persist/public/hiddenmenu/data/mobile_data_rx
/persist/public/hiddenmenu/data/mobile_data_tx
/persist/public/hiddenmenu/data/wifi_data_rx
/persist/public/hiddenmenu/data/wifi_data_tx
/persist/public/hiddenmenu/data/activation_date
[B]/persist/public/hiddenmenu/data/factoryreset_time[/B]
/persist/public/hiddenmenu/life_calls
/persist/public/hiddenmenu/life_timer
[B]/persist/security/18.bin[/B]
/persist/mdm/oma_dm_update
/persist/rfs/shared/server_info.txt
[B]/persist/rfs/msm/mpss/datablock/id_00
/persist/rfs/msm/mpss/datablock/id_01[/B]
/persist/rfs/msm/mpss/server_check.txt
/persist/rfs/msm/mpss/dhob.bin
/persist/rfs/msm/mpss/shob.bin
/persist/rfs/msm/adsp/server_check.txt
/persist/.bt_nv.bin
/persist/bluetooth/.bt_nv.bin
[B]/persist/alarm/powerOffAlarmSet
/persist/alarm/timezone
/persist/alarm/powerOffAlarmInstance[/B]
/persist/time/ats_1
[B]/persist/time/ats_12
/persist/time/ats_13[/B]
/persist/time/ats_2
/persist/time/ats_16
[B]/persist/time/ats_15[/B]
athene_f:/ #

As heeth21 has mentioned, your persist is missing /persist/rfs/msm/mpss/datablock/id_00

and /persist/rfs/msm/mpss/datablock/id_01 at least, and I do not know how to generate them even if you can. For added reference, this persist was generated from a XT1642 (retgb) running stock 8.1 Oreo, with an EMEA baseband.
[Moto G4 Plus Questions & Answers] Tetcare99:
Please share that the link XT1642 (retgb) stock Oreo 8.1.0 I will try it bro