Database Users

[WIP] [DEV] Any dev know where BT config is stored within i9505G?

Trying to fix my Bluetooth issue, as chronicled in detail here.
Wanted to ask you devs where Bluetooth configuration or a related error log is stored on the i9505G so I can take a look at it; something is stopping my BT from being able to turn on; it used to work fine pre-root (heck, even post-root for a day or so).
I figured the developers would be the best people to ask since you'd be familiar with the folder structure and config files.

KrossX said:
Trying to fix my Bluetooth issue, as chronicled in detail here.
Wanted to ask you devs where Bluetooth configuration or a related error log is stored on the i9505G so I can take a look at it; something is stopping my BT from being able to turn on; it used to work fine pre-root (heck, even post-root for a day or so).
I figured the developers would be the best people to ask since you'd be familiar with the folder structure and config files.
Click to expand...
Click to collapse
Sent from my GT-I9505G using Tapatalk 2
KrossX this is the second time you have posted questions in the development forum. As I stated before these are for Q&A NOT here. Please refrain from posting your questions here and READ the XDA users guide and forum rules again. There is a reason for this. I am glad your part of the community and your questions and comments are noteworthy you just need to put them in the right place. We read those threads as well! MJ
This is for Development ONLY

Yes PLEASE no name calling we all make mistakes and this thread will be moved soon to the proper place
And to answer your question Kriss you could do a logcat but if your not familiar with that do a search and provide more info on what your trying to do ( configuration?)
Sent from my GT-I9505G using Tapatalk 2

MJHawaii said:
Yes PLEASE no name calling we all make mistakes and this thread will be moved soon to the proper place
And to answer your question Kriss you could do a logcat but if your not familiar with that do a search and provide more info on what your trying to do ( configuration?)
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I thought that since I was aiming this more at the devs it would've been in the Dev forums. Sorry for having you move yet another thread of mine.
Didn't mean to cause a ruckus; never really got a chance to read the post by deaffob above before it was edited by the mod so no offense from whatever name-calling was done, haha.
Thanks MJHawaii; I will search for logcat and see what I can pull up.

Any ideas (referring to attached pic)? I filtered at the Error level in the logs for the term "Bluetooth"
Sent from my GT-I9505G using Tapatalk 4

KrossX said:
Any ideas (referring to attached pic)? I filtered at the Error level in the logs for the term "Bluetooth"
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
The first error there looks like it may be relevant, but you'll need to get a more thorough logcat in order to trouble shoot it more. Please grab one with adb and post it to pastebin or here in a [ code][ /code] box.

xHausx said:
The first error there looks like it may be relevant, but you'll need to get a more thorough logcat in order to trouble shoot it more. Please grab one with adb and post it to pastebin or here in a [ code][ /code] box.
Click to expand...
Click to collapse
Good news and bad news.
Bad news: I am unable to run logcat; I am unable to access my device via USB ever since the root and when I tried doing the logcat steps, yet again it couldn't connect to my device.
Good news: I believe the solution to this issue (being unable to access my device via USB) may also lie in the logs along with the bluetooth issue. The reason why is because of this error message I received while trying to reinstall the USB driver (attached pic); it points to not being able to "start" a device. I think this will all eventually tie-in with some services not running correctly on my phone.
So, is there another way for me to post a log for you kind folks to review on here via my phone directly?
If I can do that via catlog app on my device, let me know what sort of log (which options) I'd need to run and post. Thanks!

Well, did a restore to stock + root. That didn't help. It changed the Baseband, Kernel, and Build versions but did nothing to fix my issues with BT and USB connectivity.
I think I am going to start researching ways to start from scratch. Like a factory reset/wipe back to first-use condition. If anyone can point me towards some reading material on how to do that safely and wisely, it would be much appreciated!

I just ended up doing a factory reset (Menu-->Settings-->Backup & Reset-->Factory Data Reset) and that resolved the issue (while wiping my phone).
Bluetooth issue is resolved; tested it just now and it works just fine again. As is the USB issue; as soon as the phone was connected to the same exact PC as before, it was recognized and showed up as a device that I could open and explore.
My Kernal/Baseband/Build versions are all back to the ones I had when I got the phone from the Google Store, so that's comforting too.
Thanks to all those who attempted to help!

Your device is corrupt and cannot be trusted and may not work - ZB601KL

Hello, anyone can help me with this error? "your device is corrupt and cannot be trusted and may not work properly." This is after I updated my phone from Oreo to Pie.
I tried to follow the steps from an XDA forum (https://forum.xda-developers.com/asu...upted-t3937991), When I checked the Verity Mode settings using the command fastboot oem device-info I see that it is set to FALSE.
But when I tried to run the command : adb reboot "dm-verity enforcing" or fastboot reboot "dm-verity enforcing" I am getting an error message saying : fastboot: usage: unknown reboot target dm-verity enforcing
I attached a screenshot of the error message.. I am not sure what are the next steps for me.. I need some help please...

[email protected] said:
Hello, anyone can help me with this error? "your device is corrupt and cannot be trusted and may not work properly." This is after I updated my phone from Oreo to Pie.
I tried to follow the steps from an XDA forum (https://forum.xda-developers.com/asu...upted-t3937991), When I checked the Verity Mode settings using the command fastboot oem device-info I see that it is set to FALSE.
But when I tried to run the command : adb reboot "dm-verity enforcing" or fastboot reboot "dm-verity enforcing" I am getting an error message saying : fastboot: usage: unknown reboot target dm-verity enforcing
I attached a screenshot of the error message.. I am not sure what are the next steps for me.. I need some help please...
Click to expand...
Click to collapse
Instead of opening another thread you should've posted this in the thread you followed. It'll be much more helpful. Also try using USB 2.0 port instead of 3.0 and with the latest drivers.

@[email protected] THREAD CLOSED! @ all interested in the subject, please follow this already existing thread, where the OP posted before this thread was created and where the OP got his problem solved.
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse

(how-to unbrick your realme device) fastboot needed fix inside.

I Went totally nuts last night when i bricked my phone so i did figure out my self how to unblock the phone.
First you need to BE ABLE TO ENTER FASTBOOT it won't work without it and you need working TWRP.
First you need to go to TWRP and go to mount and unmount everything and disable MTP.
Then go to Advanced and select Terminal
type in LS make sure there is 2 Folders one called system and one called system_root
make sure that the system folder is empty if empty type in rm -r system
and rename the system_root folder to system using mv system_root system
after that boot into Fastboot mode and Flash your Rom for your Device using the Fastboot Tool
Hope that works for you guys.

The real mistake is when your device brick with locked bootloader, all the other cases are solvable.

HTCDevil said:
The real mistake is when your device brick with locked bootloader, all the other cases are solvable.
Click to expand...
Click to collapse
Yep once you lock you doomed
Funny is my bootloader still unlock and my fingerprint works fine on the stock rom
Sent from my RMX1931 using Tapatalk

natedogg20050 said:
Yep once you lock you doomed
Funny is my bootloader still unlock and my fingerprint works fine on the stock rom
Click to expand...
Click to collapse
That's interesting, i thought it works only if you relock bootloader and then update fw

HTCDevil said:
That's interesting, i thought it works only if you relock bootloader and then update fw
Click to expand...
Click to collapse
Worked perfectly fine even on the old 0.8 firmware
Sent from my RMX1931 using Tapatalk

natedogg20050 said:
...
Click to expand...
Click to collapse
THREAD CLOSED! There has been already created a thread by you where you could have continued to share your experiences, and to which I've copid the above posts.
https://forum.xda-developers.com/realme-x2-pro/help/bricked-realme-x2-pro-twrp-fastboot-t4038999
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse

HTC U Ultra stuck in bootloop...Can you experts verify the STEPS to solve the issue?

So, my HTC U Ultra got stuck in bootloop just 3 days after warranty ended(tough luck level : 100).
My phone runs on everything stock and no root.
I press all the buttons when powered off and it goes into bootloader mode. It displays options to boot into recovery mode, boot into download mode and power down, all of which(except power down) gets device into bootloop again.
THE PRIORITY OF GOALS IS : DATA RECOVERY > PHONE BOOTING AND WORKING PROPERLY AGAIN
I did a little research and figured out some sort of procedure by putting bits and pieces together :
1. Download ADB/Fastboot toolkit || universal driver from koush github // I have HTC Sync manager installed as well || twrp custom recovery image for htc u ultra || new ruu from htc support for rom update.
2. Now I put my phone into fastboot mode (since it doesn't show up on adb devices), connect to pc using usb.
3. I type in cmd : "fastboot devices" --> My device shows up there --> Again in cmd : "fastboot boot recovery mytwrp.img" --> the twrp boots into my phone
I was able to put this many steps together and after the last step, i have an abstract idea of what to do :
Enable USB Debugging using twrp recovery --> Use ADB Pull Command to get my all my data from phone to pc --> Use adb wipe the old Firmware (Not sure which command) --> Use adb again to flash new RUU (again not sure how, I've got an .exe file as RUU || should I get it in zip or img or any other format ? || Please help on this too) --> Finally Boot and hopefully everything turns out smooth and secure.
CAN YOU EXPERTS HELP ME TO PUT TOGETHER REMAINING STEPS (AND MODIFY ERRORS, IF ANY, OF EXISTING STEPS ) OF THIS PROCEDURE...???

noobie12112 said:
...
Click to expand...
Click to collapse
@noobie12112 THREAD CLOSED as duplicate of https://forum.xda-developers.com/u-ultra/help/htc-ultra-stuck-bootloop-experts-t4180387
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse

Wrong pin issue

Hello,
last week i decided to upgrade to A11 rom (PE+). Before i ran PE+ A10 for months without problems.
I upgraded my ofox to latest 11.1 stabile. Then Format data, wipe etc.
Now whenever i installed a rom, after a short time when rebooting system my pin isnt recognized anymore from screen lock. Theres always this "wrong pin" warning. So i cannot access my phone.
Ofox cant decrypt seither, because oft wrong pin...
Since then i Tried many different Roms (A11 and A10) and even different recoverys (twrp, los, older ofox) and firmwares.
I also reverted back to my old PE+ A10...and now even there the bug appears!
I also tried deleting all files with "lock" in it under data/system...but that leads to neverending boot-time...
It is so annoying..i dont know now i can get my phone back to function properly...
Maybe anyone has a clue whats causing this all oft a sudden?

@lordschmaeh Thread closed as duplicate of
Wrong pin issue
Hello, last week i decided to upgrade to A11 rom (PE+). Before i ran PE+ A10 for months without problems. I upgraded my ofox to latest 11.1 stabile. Then Format data, wipe etc. Now whenever i installed a rom, after a short time when rebooting...
forum.xda-developers.com
https://forum.xda-developers.com/t/xda-developers-forum-rules.4200559/
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse