Database Info

Bluetooth issues after long term flashing addiction

So I've searched and haven't found anything similar to what I'm experiencing.
Verizon M8, S-OFF, flash more than once a day sometimes. I recently had the 4G LTE issue that required I return back to stock recovery to fix nv partition through factory reset.
Since then, I've noticed that my bluetooth connects just fine to my uConnect for audio, but not phone functionality. It doesn't seem to be an issue with my ROM because I've tried multiple and experience the same issue, and a friends iPhone paired without issue.
Is it possible theres another partition that I screwed up?
Please let me know if I left out any vital information..
Thanks guys!

Have you tried reflashing your firmware?

cntryby429 said:
Have you tried reflashing your firmware?
Click to expand...
Click to collapse
I did, through the fastboot process and hboot as well.

How about a different one? There's digital high's, aer0's, and I think one from the sundream's srom thread. Not to mention any fixes that may come from our new update rolling out now.

cntryby429 said:
How about a different one? There's digital high's, aer0's, and I think one from the sundream's srom thread. Not to mention any fixes that may come from our new update rolling out now.
Click to expand...
Click to collapse
I'm going to try are0s again but through the fastboot method. I'll post back here soon.
Thanks

I also understand it's recommended to flash it twice in fastboot.

cntryby429 said:
I also understand it's recommended to flash it twice in fastboot.
Click to expand...
Click to collapse
Fixed! I'm not sure if reflashing the aero firmware fixed it or deleting the audio device on my head unit before pairing again did. This could have just been a major brain fart.

Glad you're back on track either way.

Rooting, unlocking and ghost issues?

Hi,
My phone was a disaster concerning ghost touches, completely unusable. I got an RMA approval but just before sending the phone out there was an OTA that completely fixed this. So very happy.
Yesterday I unlocked my bootloader and rooted the phone, this all worked, but today (it's medium hot) I'm having ghost touches all over again. I don't understand, I would have though since I'm still running 12.1-YOG4PAS1N0 this could have nothing to do with this?

rept said:
Hi,
My phone was a disaster concerning ghost touches, completely unusable. I got an RMA approval but just before sending the phone out there was an OTA that completely fixed this. So very happy.
Yesterday I unlocked my bootloader and rooted the phone, this all worked, but today (it's medium hot) I'm having ghost touches all over again. I don't understand, I would have though since I'm still running 12.1-YOG4PAS1N0 this could have nothing to do with this?
Click to expand...
Click to collapse
As you have unlocked the bootloader, I suggest you to flash fastboot images of this version of CMOS12.1 using section 8 of this guide http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Credits to @Heisenberg

Hi, thanks for your reply. Will I loose all data over this? Or can I just do the procedure without the:
fastboot flash userdata userdata_64G.img
step?
Could you explain why this will work? What will be different as opposed to today when I have 12.1 running? Did the unlocking/rooting change anything in regard to the touchscreen? (just trying to understand).

rept said:
Hi, thanks for your reply. Will I loose all data over this? Or can I just do the procedure without the:
fastboot flash userdata userdata_64G.img
step?
Could you explain why this will work? What will be different as opposed to today when I have 12.1 running? Did the unlocking/rooting change anything in regard to the touchscreen? (just trying to understand).
Click to expand...
Click to collapse
Follow the procedure but don't flash the userdata and you won't lose any data. It isn't guaranteed to work but it's definitely worth trying. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2839471
It didn't seem to work for Mr Hoax

Image Enhancement Preview

Im using the dual sim model e6633
I have the stock fm and kernel and bootlocker unlocked.
Under image enhancement ,there is no change ie.Vivid mode and no enhNcemnt are showing same effect
Can anyone help to solve this problem
Cheers

Not sure to understant, but have you flashed a kernel with DRM fix ?
When you unlock your bootloader you loose, photo quality, image enhancement...

I havent flashed any kernel yet.
I have the stock fm and kernel.
Plz help me how to get back the image quality :/
Noobie question :/
Sorry for bad english ?
Should i flash a kernel with drm fix??

flash kernel with DRM fix and you will have image preview

L33Tgod said:
flash kernel with DRM fix and you will have image preview
Click to expand...
Click to collapse
Can you suggest me the best kernel available with drm fix for e6633 dual.(in terms of image quality and battery life)
Im extremly sorry for asking such silly question.

dulquer said:
Can you suggest me the best kernel available with drm fix for e6633 dual.(in terms of image quality and battery life)
Im extremly sorry for asking such silly question.
Click to expand...
Click to collapse
https://forum.xda-developers.com/xperia-z5/general/patched-stock-kernel-32-2-5-11-e6683-t3516979
this one is for E6683, i have no idea will it work on E6633
I will send you other one if i found

L33Tgod said:
https://forum.xda-developers.com/xperia-z5/general/patched-stock-kernel-32-2-5-11-e6683-t3516979
this one is for E6683, i have no idea will it work on E6633
I will send you other one if i found
Click to expand...
Click to collapse
I dont think so it will work.
Will zacharias.maladroit kernel work?
It have drm fix??
Thanks in advance

yes it will work, also this one should work because it is same phone

I have one more issue.
Finger print hardware not available?
Is this also because of unlocked bootloader??

dulquer said:
I have one more issue.
Finger print hardware not available?
Is this also because of unlocked bootloader??
Click to expand...
Click to collapse
Nope, that's because you have the US version of the Z5 dual and it has been specifically disabled. If you want to get the fingerprint sensor working you need to flash international firmware, or there are some threads that tell you what files you need to replace. Search and you should find what you're looking for.

Devo7v said:
Nope, that's because you have the US version of the Z5 dual and it has been specifically disabled. If you want to get the fingerprint sensor working you need to flash international firmware, or there are some threads that tell you what files you need to replace. Search and you should find what you're looking for.
Click to expand...
Click to collapse
When i reboot it works fine.But it comes once in a while.Also i have the stock fm (Middle East).

dulquer said:
When i reboot it works fine.But it comes once in a while.Also i have the stock fm (Middle East).
Click to expand...
Click to collapse
Then you should be fine. It might not be working occasionally because there might be a bug in the firmware you're using. My only suggestion would be to make sure you're on the latest version of the firmware for your region, or try flashing firmware from another region. I'm using Customized UK firmware and I have no issues with the fingerprint sensor. Short of that the only other option would be a hardware failure, but it sounds more like a software bug.

Devo7v said:
Then you should be fine. It might not be working occasionally because there might be a bug in the firmware you're using. My only suggestion would be to make sure you're on the latest version of the firmware for your region, or try flashing firmware from another region. I'm using Customized UK firmware and I have no issues with the fingerprint sensor. Short of that the only other option would be a hardware failure, but it sounds more like a software bug.
Click to expand...
Click to collapse
I will try flashing another firmware.Its showing new sofware available in support?.But not showing when opening it under softwate updates.

dulquer said:
I will try flashing another firmware.Its showing new sofware available in support?.But not showing when opening it under softwate updates.
Click to expand...
Click to collapse
Can you post a screenshot of your About Phone screen so I can see your build number?

Devo7v said:
Can you post a screenshot of your About Phone screen so I can see your build number?
Click to expand...
Click to collapse
Attached.

dulquer said:
Attached.
Click to expand...
Click to collapse
It looks like you're a couple firmware versions behind; the latest firmware released for your phone is 32.2.A.5.11. Since you mentioned that your phone won't automatically update itself through the software update it sounds like you may have modified your phone in such a way (i.e., unlocking the bootloader, or modifying system files) that you might have to manually flash the firmware to your phone. There is a program called Flashtool that you can use to download and flash firmware to your phone. It's a great tool and something that you can learn to use after a few minutes of reading in the support thread.
If you've made any modifications to your phone, it would be helpful to know what those are understand why your phone won't update on its own. But most likely you'll have to use Flashtool to update your phone.
EDIT: In the future if you want to see what the latest version of firmware is for your phone you can use the XperiCheck website.

Devo7v said:
It looks like you're a couple firmware versions behind; the latest firmware released for your phone is 32.2.A.5.11. Since you mentioned that your phone won't automatically update itself through the software update it sounds like you may have modified your phone in such a way (i.e., unlocking the bootloader, or modifying system files) that you might have to manually flash the firmware to your phone. There is a program called Flashtool that you can use to download and flash firmware to your phone. It's a great tool and something that you can learn to use after a few minutes of reading in the support thread.
If you've made any modifications to your phone, it would be helpful to know what those are understand why your phone won't update on its own. But most likely you'll have to use Flashtool to update your phone.
EDIT: In the future if you want to see what the latest version of firmware is for your phone you can use the XperiCheck website.
Click to expand...
Click to collapse
Thanks a lot mate.
I will update through flastoool(I have used before)
Cheers

Devo7v said:
It looks like you're a couple firmware versions behind; the latest firmware released for your phone is 32.2.A.5.11. Since you mentioned that your phone won't automatically update itself through the software update it sounds like you may have modified your phone in such a way (i.e., unlocking the bootloader, or modifying system files) that you might have to manually flash the firmware to your phone. There is a program called Flashtool that you can use to download and flash firmware to your phone. It's a great tool and something that you can learn to use after a few minutes of reading in the support thread.
If you've made any modifications to your phone, it would be helpful to know what those are understand why your phone won't update on its own. But most likely you'll have to use Flashtool to update your phone.
EDIT: In the future if you want to see what the latest version of firmware is for your phone you can use the XperiCheck website.
Click to expand...
Click to collapse
I have updated to the latest fm as you said(about phone attached)
I have also flashed zacharias kernel.
Problem is going worse.
My down speaker is not working :/ also image enhancement preview remains same (no Change).
Please help
Cheers

dulquer said:
I have updated to the latest fm as you said(about phone attached)
I have also flashed zacharias kernel.
Problem is going worse.
My down speaker is not working :/ also image enhancement preview remains same (no Change).
Please help
Cheers
Click to expand...
Click to collapse
Did you write all your data when you flashed the new firmware with Flashtool? Maybe try flashing again, but make sure you wipe everything so you're starting with a clean phone. Set up the phone and make sure everything works, then flash a custom kernel.

Devo7v said:
Did you write all your data when you flashed the new firmware with Flashtool? Maybe try flashing again, but make sure you wipe everything so you're starting with a clean phone. Set up the phone and make sure everything works, then flash a custom kernel.
Click to expand...
Click to collapse
I did the same thing as you have said and no Change :/

Stock Bootloader

Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)

NullaVisus said:
Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
Click to expand...
Click to collapse
download latest stock rom at sammy..

Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?

NullaVisus said:
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
Click to expand...
Click to collapse
try flash custom rom after that flash stock rom..

khaisttj92 said:
try flash custom rom after that flash stock rom..
Click to expand...
Click to collapse
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)

NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
sorry dude i cant help u because im using f variant..

khaisttj92 said:
sorry dude i cant help u because im using f variant..
Click to expand...
Click to collapse
Thanks anyways my dude

NullaVisus said:
Thanks anyways my dude
Click to expand...
Click to collapse
your welcome..

NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.

najoor said:
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
Click to expand...
Click to collapse
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)

NullaVisus said:
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
Click to expand...
Click to collapse
I can give you a system image but you will have to flash it in TWRP.

najoor said:
I can give you a system image but you will have to flash it in TWRP.
Click to expand...
Click to collapse
Thats fine. I already know how

NullaVisus said:
Thats fine. I already know how
Click to expand...
Click to collapse
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar

rawkahn said:
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
Click to expand...
Click to collapse
The bootloader is always included with the firmware and is most certainly included with the firmware you posted.
Safetynet probably fails because you need to factory reset.

Question Wifi and Hotspot Not Turning On

Hi,
I bought my phone three months back. Ever since the last update Version Name - WW18.0840.2106.86 my wifi and Hotspot just won't turn on.
I have been through the asus forum and seems like alot of customers are facing this issue.
One of them confirmed that even after replacing motherboard the issue persists. Others are facing air trigger issues after replacing the motherboard.
Just wanted to know if anyone here is facing similar issues.
DO let me know your thoughts on should I visit service center and Get my motherboard replaced or should I wait for the next update. My current Version Name - WW18.0840.2107.151
PS: My phone is not rooted
Thanks

I have not had these issues personally. I just updated to .151 last night though, so we shall see.
The general consensus is that the mobo needs to be replaced, and will most likely not get fixed with a software update. If it was correctable, a major issue like this would have forced a new FW update after .86 caused your initial problem.
You could always try flashing raw FW if you really want to tinker, but I doubt it will help. I would hit the service center and get the mobo replaced.
Good luck!

BILLYB187 said:
I have not had these issues personally. I just updated to .151 last night though, so we shall see.
The general consensus is that the mobo needs to be replaced, and will most likely not get fixed with a software update. If it was correctable, a major issue like this would have forced a new FW update after .86 caused your initial problem.
You could always try flashing raw FW if you really want to tinker, but I doubt it will help. I would hit the service center and get the mobo replaced.
Good luck!
Click to expand...
Click to collapse
Yup.. .86 update cause this. I just didn't want to change the motherboard,as it will change the imei of phone from what's on the box.
Thanks for your inputs though

I was helped by installing the karnel

do one thing i also got same issue ,what i do means i install twrp and wipe the system and after i install ota file after i reboot in slot b then every thing for fine for me ..

thieftime1980 said:
I was helped by installing the karnel
Click to expand...
Click to collapse
Really? I have same problem after update. It didn't allow me to turn on wifi. But if its sure that installing kernel would solve the problem I might give it a try
Would you elaborate your situation regarding this sir?

jaleel (jelly) said:
do one thing i also got same issue ,what i do means i install twrp and wipe the system and after i install ota file after i reboot in slot b then every thing for fine for me ..
Click to expand...
Click to collapse
HOW DID YOU INSTALL OTA FILE? VIA TWRP OR FLASH ALL?

TOYOBHUMAX said:
HOW DID YOU INSTALL OTA FILE? VIA TWRP OR FLASH ALL?
Click to expand...
Click to collapse
The ota files are installed right in system.
New firmware "keep root" WW-18.0840.2103.26
Okay so I went to the Asus website https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Got the latest firmware which is the most recent one for this month with the latest security patch. I remember doing this method...
forum.xda-developers.com

twistedumbrella said:
The ota files are installed right in system.
New firmware "keep root" WW-18.0840.2103.26
Okay so I went to the Asus website https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Got the latest firmware which is the most recent one for this month with the latest security patch. I remember doing this method...
forum.xda-developers.com
Click to expand...
Click to collapse
Nothing pops up

thieftime1980 said:
I was helped by installing the karnel
Click to expand...
Click to collapse
What kernel did you install?

https://forum.xda-developers.com/t/kernel-30-09-2021-android-11-kirisakura-1-2-0-for-asus-rog-phone-5-aka-anakin.4333363 / strona-5 # post-85712193

jaleel (jelly) said:
do one thing i also got same issue ,what i do means i install twrp and wipe the system and after i install ota file after i reboot in slot b then every thing for fine for me ..
Click to expand...
Click to collapse
Where did you install OTA file? Does Ota file install mean you in the home screen of the phone? Ota is in the main storage, right?

jaleel (jelly) said:
do one thing i also got same issue ,what i do means i install twrp and wipe the system and after i install ota file after i reboot in slot b then every thing for fine for me ..
Click to expand...
Click to collapse
How did you reboot to slot b? In twrp?

TOYOBHUMAX said:
How did you reboot to slot b? In twrp?
Click to expand...
Click to collapse
There is option in twrp check in reboot section

TOYOBHUMAX said:
Where did you install OTA file? Does Ota file install mean you in the home screen of the phone? Ota is in the main storage, right?
Click to expand...
Click to collapse
Twrp

TOYOBHUMAX said:
HOW DID YOU INSTALL OTA FILE? VIA TWRP OR FLASH ALL?
Click to expand...
Click to collapse
I use twrp for ota files

jaleel (jelly) said:
I use twrp for ota files
Click to expand...
Click to collapse
Hi thanks for the answer... How to install OTA files in twrp? You mean OTA files the one beginning with UL or WW

anybody found a real solution? i was fine and after i flashed a kernel later that day no wifi, I went bk to stock and no luck

chairman011 said:
anybody found a real solution? i was fine and after i flashed a kernel later that day no wifi, I went bk to stock and no luck
Click to expand...
Click to collapse
No one shares how lol. I guess theyre not here. Im struggling same problem too man

TOYOBHUMAX said:
Where did you install OTA file? Does Ota file install mean you in the home screen of the phone? Ota is in the main storage, right?
Click to expand...
Click to collapse
OTA files are the standard updates. There are a lot of how to guides that answer most of these questions, which may be why nobody is jumping up to walk you through it.
I wouldn't trust someone installing OTA files in TWRP because the system handles them already without any software. That is just asking for problems.
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com
The link I posted earlier is included in that. Not sure why nothing showed up for it, but maybe you'll have better luck getting to it that way.
There's always a possibility it is a hardware issue. A lot of them have been SIM, Wifi, and Bluetooth issues. If you suspect a kernel issue, make sure you are following the instructions to restore. If you only flashed a boot, you didn't follow the instructions.