Develop Bugs

Desire GSM- Potential Bluetooth connection fix for Cyanogenmod 7.1

Hello all
A little bit of background info:
I have owned my Desire for over 2 years now & recently decided to s-off/root/flash (primarily to gain some memory space- the only real short coming of the Desire in my opinion).
I went from stock Gingerbread 2.3.7 to Cyanogenmod 7.1 & so have taken my first step into a larger world!
In that world I encountered problems - no signal, no gps, no bluetooth, radio flashing etc. - all of which I managed to find solutions for by reading the excellent resources of xda-developers.
So having collated the enormous & varying wealth of info & getting my Desire fully functional - I wanted to give something back.
It's not much (though I haven't seen it anywhere as a solution?), but it may help someone somewhere :fingers-crossed:
## If you just want to cut to the chase- the procedure that worked for me is at the end of the post! ##
About my phone:
Android version 2.3.7
Cyanogenmod version 7.1.0
Baseband Version 32.56.00.32u_5.17.05.23
Kernel Version 2.6.37.6-cyanogenmod-geb50077
As stated, gps & signal were fixed with a simple radio flash from 5..11.05.14 - 5.17.05.23
but bluetooth remained unable to connect. My 2 devices were in the list showing as 'Paired but not connected'
Clicking on them they would say 'connecting' but that process would end with no error or message & no connection made.
The only long press option on them was 'unpair' - so no option to delete & try again.
I then found a potential fix which is I assume is fairly well known BUT I could not get it to run:
SOLUTION (copied from external site)
I ran the Terminal app and entered
'su'
(App requests root permissions, grant them). Then I went to the device's bluetooth settings with
'cd /data/misc/bluetoothd'
(Note the 'd' at the end). There I found a directory named by the bluetooth chip's ID, in my case '38:E7:B8:45:21:a4'. I renamed this directory
'mv 3* hidden'
Turned bluetooth off and back on and could use bluetooth again.
Every time I ran the terminal I could get su to work, with permissions granted as confirmed in the toast message that would pop up- BUT whenever I typed 'cd /data/misc/bluetoothd' I only ever got 'Permission Denied'.
All the fix posts I read about this pointed towards root & su permissions not working correctly but mine certainly were. I had tried all the usual fixes of un-applying/re-applying SU permissions, root etc.
I also tried the same commands through adb, all with the same result.
It then occurred to me that the Terminal was only changing a folder property so I used 'ROM Toolbox Pro' -> 'Root Browser' to find the folder in question ('38:E7:B8:45:21:a4' in my case).
It became apparent that the path given in the 'fix' was incorrect (for my Desire GSM at least).
The folder I was looking for was actually in 'd/data/bluetoothd' - so the 'permission denied' error was because the path was incorrect, not that SU permissions were not granted!
Before I actually tried that correct path though- I noticed that to make files hidden the '.' (full stop) prefix is added to the start of the file or folder name.
I used Root Browser to long-press on the '38:E7:B8:45:21:a4' folder & then 'rename' from the menu - making the folder name '.38:E7:B8:45:21:a4' (note the full stop at the start.)
I then re-enabled bluetooth - this time noticing that both my paired devices were no longer there (this is good!). I made the Desire discoverable then did a scan...success!
Both my devices paired & connected exactly as they should. I now notice in Root Browser that the file structure has also changed with there being no 'bluetoothd' folder at all.
I also imagine that entering the correct folder path in terminal or adb would produce the same results, though I cannot confirm this as the procedure described had already worked for me.
So, long story short:
1. Make sure bluetooth is turned OFF then open Rom Toolbox Pro -> Root Browser (or any root browser with su permissions I guess?)
2. Navigate to the folder d/data/bluetoothd/38:E7:B8:45:21:a4 (#Note: your '38:E7:B8:45:21:a4' folder will probably be named differently)
3. Long press on the '38:E7:B8:45:21:a4' folder. (or whatever yours is called)
4. From the pop up menu - select 'Rename'
5. Add a full stop '.' at the beginning of the folder name Eg '.38:E7:B8:45:21:a4' (Keep the rest of the name as it was)
6. Turn on Bluetooth - in 'Bluetooth settings' make your device discoverable & note that if any paired devices were present, they should now be gone from the list.
7. Scan for bluetooth devices, obviously making sure they are also switched on & discoverable! (if it doesn't automatically)
8. Your devices should now show up, ask to pair, ask for pin numbers if needed & then connect automatically.
If this has been covered elsewhere please accept my apologies, & delete the post if it's deemed as clutter- I was merely trying to help

Dog909 said:
Hello all
A little bit of background info:
I have owned my Desire for over 2 years now & recently decided to s-off/root/flash (primarily to gain some memory space- the only real short coming of the Desire in my opinion).
I went from stock Gingerbread 2.3.7 to Cyanogenmod 7.1 & so have taken my first step into a larger world!
In that world I encountered problems - no signal, no gps, no bluetooth, radio flashing etc. - all of which I managed to find solutions for by reading the excellent resources of xda-developers.
So having collated the enormous & varying wealth of info & getting my Desire fully functional - I wanted to give something back.
It's not much (though I haven't seen it anywhere as a solution?), but it may help someone somewhere :fingers-crossed:
## If you just want to cut to the chase- the procedure that worked for me is at the end of the post! ##
About my phone:
Android version 2.3.7
Cyanogenmod version 7.1.0
Baseband Version 32.56.00.32u_5.17.05.23
Kernel Version 2.6.37.6-cyanogenmod-geb50077
As stated, gps & signal were fixed with a simple radio flash from 5..11.05.14 - 5.17.05.23
but bluetooth remained unable to connect. My 2 devices were in the list showing as 'Paired but not connected'
Clicking on them they would say 'connecting' but that process would end with no error or message & no connection made.
The only long press option on them was 'unpair' - so no option to delete & try again.
I then found a potential fix which is I assume is fairly well known BUT I could not get it to run:
SOLUTION (copied from external site)
I ran the Terminal app and entered
'su'
(App requests root permissions, grant them). Then I went to the device's bluetooth settings with
'cd /data/misc/bluetoothd'
(Note the 'd' at the end). There I found a directory named by the bluetooth chip's ID, in my case '38:E7:B8:45:21:a4'. I renamed this directory
'mv 3* hidden'
Turned bluetooth off and back on and could use bluetooth again.
Every time I ran the terminal I could get su to work, with permissions granted as confirmed in the toast message that would pop up- BUT whenever I typed 'cd /data/misc/bluetoothd' I only ever got 'Permission Denied'.
All the fix posts I read about this pointed towards root & su permissions not working correctly but mine certainly were. I had tried all the usual fixes of un-applying/re-applying SU permissions, root etc.
I also tried the same commands through adb, all with the same result.
It then occurred to me that the Terminal was only changing a folder property so I used 'ROM Toolbox Pro' -> 'Root Browser' to find the folder in question ('38:E7:B8:45:21:a4' in my case).
It became apparent that the path given in the 'fix' was incorrect (for my Desire GSM at least).
The folder I was looking for was actually in 'd/data/bluetoothd' - so the 'permission denied' error was because the path was incorrect, not that SU permissions were not granted!
Before I actually tried that correct path though- I noticed that to make files hidden the '.' (full stop) prefix is added to the start of the file or folder name.
I used Root Browser to long-press on the '38:E7:B8:45:21:a4' folder & then 'rename' from the menu - making the folder name '.38:E7:B8:45:21:a4' (note the full stop at the start.)
I then re-enabled bluetooth - this time noticing that both my paired devices were no longer there (this is good!). I made the Desire discoverable then did a scan...success!
Both my devices paired & connected exactly as they should. I now notice in Root Browser that the file structure has also changed with there being no 'bluetoothd' folder at all.
I also imagine that entering the correct folder path in terminal or adb would produce the same results, though I cannot confirm this as the procedure described had already worked for me.
So, long story short:
1. Make sure bluetooth is turned OFF then open Rom Toolbox Pro -> Root Browser (or any root browser with su permissions I guess?)
2. Navigate to the folder d/data/bluetoothd/38:E7:B8:45:21:a4 (#Note: your '38:E7:B8:45:21:a4' folder will probably be named differently)
3. Long press on the '38:E7:B8:45:21:a4' folder. (or whatever yours is called)
4. From the pop up menu - select 'Rename'
5. Add a full stop '.' at the beginning of the folder name Eg '.38:E7:B8:45:21:a4' (Keep the rest of the name as it was)
6. Turn on Bluetooth - in 'Bluetooth settings' make your device discoverable & note that if any paired devices were present, they should now be gone from the list.
7. Scan for bluetooth devices, obviously making sure they are also switched on & discoverable! (if it doesn't automatically)
8. Your devices should now show up, ask to pair, ask for pin numbers if needed & then connect automatically.
If this has been covered elsewhere please accept my apologies, & delete the post if it's deemed as clutter- I was merely trying to help
Click to expand...
Click to collapse
I can't find folder *data* in folder *d*. I have a separate folder *data*. There is a folder named *bluetooth* in folder *d*. It also didn't work for me.

Nexus 7 2013 WiFi - WiFi won't turn on after Marshmallow upgrade - bad Mac Address

Just sideloaded the Mashmallow update from 5.1.1 to 6.0 (downloaded from Google) and the update seemed to go normally - most things work as normal. But the WiFi wouldn't turn on, and it's mac address reports as 02:00:00:00:00:00. That address I know was an issue in the M Preview as a fake address.
I didn't want to hard reset it but in the end relented and loaded a clean new version of 6.0 from Google. When it restarts the second thing it wants to do, after selecting a language, is start the WiFi so it can log on. Of course WiFI won't start, and I can't "skip" so it's stuck. I tried Bad_Boyz fromXDA, and then going back to 5.1.1, and now forward again to 6.0 - same result. I suspect the WiFi mac address has been cleared. I found a little help that if I shell into the tablet, and write the mac address into /persist/wifi/.macaddr I might move forward. I know how to do this, but I can't shell in with adb. I can talk over USB, and run fastboot. When I connect via USB the Nexus mounts (sort of - the storage folder isn't shown when the tablet is at the "Select WiFi network" stage of setup)
When I run "adb devices" - I can't see any, even though I can "fastboot reboot recovery" and the like. I'm sure bluetooth (mac address) is broken too, but I"ll fix that later.
Does anyone have any idea how I can encourage adb to talk, so that I can "adb shell"?

Safe Mode
Just so you know - I started it in safe mode, which I have done before, but anyway - and the WiFi works. Also, USB debugging is presumably switched to off on a hard reset, and I couldn't log in to enable it without working WiFi. Suddenly my mac address is back. Don't really know if safe mode is the answer but it's worth trying...
To get into Safe Mode - long press on the "Power Off" question when you turn it off - it reboots in safe mode.

recover after broken screen, modify default.prop to disable secure USB debug?

Dropped my S3 today, and now the screen doesn't respond to touch. The display also only works partially. This is the excuse I needed to get an S5, but I'd like to pull data off this S3 for the transition. Honestly I'm not even sure there's anything important on there that isn't already backed to the cloud one way or another. But I'd like to poke around to be sure, use Titanium backup for at least a few apps in particular.
So I found this nice utility: http://forum.xda-developers.com/showthread.php?t=2786395 to allow me to control the device and see the screen via adb. Problem is that while USB debugging is enabled, I have to confirm the RSA fingerprint of my PC on the device itself... which I can't do because the digitizer on the phone is broken. Some searching suggests using a USB OTG to connect a mouse to blindly try to hit the RSA confirmation button. Either it doesn't work, or the cable I hacked together didn't cut it. I couldn't get off of the keyguard screen. Ordered a premade OTG adapter, but if that still fails I may have to find another way in.
From what I've read, I can disable the RSA check by setting ro.adb.secure=0 in default.prop, but that file would need to be replaced on the boot ramdisk. Making a custom boot image isn't something I've done. I found this article about it, "HOWTO: Unpack, Edit, and Re-Pack Boot Images". Following that article, should my boot.img come from extracting the L710VPUDNJ2_L710SPRDNJ2_L710VPUDNJ2_HOME.tar.md5 file? And then once I've recompiled boot.img with the modified default.prop, what is the proper method for flashing that boot.img? Do I need to use odin?
The device has stock NJ2+root and Philz Touch recovery. The display and hardware keys work well enough that I can navigate recovery and initiate anything in there, and I can get to an adb shell while the device is booted in recovery.
So two questions...
1) am I on the right track to make and flash a custom boot.img?
2) is this all pointless? would I be better served to simply use recovery to copy down a backup image and extract anything I may need from that? That main data I'm concerned about is keys/etc for 2-factor apps like google authenticator and battle.net.
EDIT: As far as getting in, I couldn't figure out how to make that app work properly for controlling the phone. It could show me the screen, but apparently not send touch input.
BUT, the solution to bypassing secure adb was easy. Since I had a custom recovery and could get adb shell while booted in recovery, I could shell in, mount data, and push my local adbkey.pub to /data/misc/adb/adb_keys. VMLite VNC Server was the easiest way I found to access the system remotely, since I could push the app install from the play store on the web and then use the companion desktop app to launch the server on my phone via adb.

Did MS block access to SYSTEM folder??

Forgive me if this has already been found/fixed/forgotten, but it's been a while since I've actually even tried it. In File Explorer, when tapping on my trusty old Local Disk C shortcut nothing happens anymore ☹ I don't know if it's been blocked or not, but it's been at least 3 or 4 builds since I've even desired going into the system folder. Even my AOW Shortcuts aren't anymore, but instead they give an error saying the directory couldn't be found and would I like to delete the shortcut. Maybe MS finally removed the AoW bits from the recent builds, but that doesn't explain why the Local Disk C shortcut does nothing.
I'm running the latest Insider Slow build 14342.1004.

its "blocked" since 10586.107. but you can still access all folders on pc with enabling full fs access or using sftp (with vcreg or interop tools etc)

tofuschnitte said:
its "blocked" since 10586.107. but you can still access all folders on pc with enabling full fs access or using sftp (with vcreg or interop tools etc)
Click to expand...
Click to collapse
Ahh, I figured this was the case. I don't care for the FS Access thing on pc. Last time I enabled that I could *barely* get my phone to connect to the pc. On average it took 15 minutes to connect, but eventually it stopped altogether. I had to hard reset to fix it.

yep, same here. connectes fine but takes ages to appear in the explorer. but in that case you could use sftp access. simply get the interop tools and activate it (you might need to reset the ndtksvc.dll manually, vcreg has a button for it though iirc), read the tutorials about it. you need the old android bridge tools to get the private key (and convert it with puttygen to use it with pageant) and keep it paired to be able to connect with winscp for example

Last .1004 fast ring build connect my phone with full mtp acces in less 1 minute.

Elephone S7 fix the changing WiFi MAC adress

I have fixed mine.
There was no MAC address programmed to the device at factory. That's an omission. So the WIFI driver when activated after restart or by turning wifi off/on notices that and gives a temporary MAC address.
That address changes in the last bytes.
The solution is to write a WIFI MAC address with an appropriate tool. I did use SN_Writer just be careful to leave the other data alone.
I guess the same happens with the Bluetooth address but did not check that out yet.
0) Choose a valid MAC just look under settings the temporary one that your phone uses that's ok
1) Install VCOM Driver if you don't have it yet
If you use Windows 10 then you have to temporarily disable Driver Signature check since those drivers are not signed
Instructions and download here
http://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
2) Download the SN_Writer I did use that one, password is mtk2000
http://mtk2000.ucoz.ru/down18/SN_Writer_Tool_v1.1648.rar
3) Download the right stock rom for your device you need the file which is named like the one I did use
APDB_MT6797_S01_alps-mp-m0.mp9_W16.48
4) Power off phone
5) In SN_Writer hit System Config uncheck everything and check Wifi Adress on the left side
In database file AP_DB use the file from 3)
That should do it.
Hit Start and entry the MAC just the digits no dashes etc.
Connect the phone while holding Volume Down.
That should do it.

Thanks for the write up, I got my S7 WiFi MAC address fixed now too, with your steps !!
Bluetooth appears already fixed/correct. (Also I haven't noticed my paired bluetooth devices loosing pairing..)

FunkiBluDawg said:
Thanks for the write up, I got my S7 WiFi MAC address fixed now too, with your steps !!
Click to expand...
Click to collapse
Great! Also good that Bluetooth is correct. Did not pair anything yet but good to know there won't be similar problems.

Idakis said:
I have fixed mine.
There was no MAC address programmed to the device at factory. That's an omission. So the WIFI driver when activated after restart or by turning wifi off/on notices that and gives a temporary MAC address.
That address changes in the last bytes.
The solution is to write a WIFI MAC address with an appropriate tool. I did use SN_Writer just be careful to leave the other data alone.
I guess the same happens with the Bluetooth address but did not check that out yet.
0) Choose a valid MAC just look under settings the temporary one that your phone uses that's ok
1) Install VCOM Driver if you don't have it yet
If you use Windows 10 then you have to temporarily disable Driver Signature check since those drivers are not signed
Instructions and download here
http://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
2) Download the SN_Writer I did use that one, password is mtk2000
http://mtk2000.ucoz.ru/down18/SN_Writer_Tool_v1.1648.rar
3) Download the right stock rom for your device you need the file which is named like the one I did use
APDB_MT6797_S01_alps-mp-m0.mp9_W16.48
4) Power off phone
5) In SN_Writer hit System Config uncheck everything and check Wifi Adress on the left side
In database file AP_DB use the file from 3)
That should do it.
Hit Start and entry the MAC just the digits no dashes etc.
Connect the phone while holding Volume Down.
That should do it.
Click to expand...
Click to collapse
thanks a lot, worked like a charm. I really needed that fix as i put mac control on my router

Meta_maui_db_inconsistent
After:
"Connect the phone while holding Volume Down."
... just a message "META_MAUI_DB_INCONSISTENT" und the process break it
You have an idea what I can still check?

66krieger said:
After:
"Connect the phone while holding Volume Down."
... just a message "META_MAUI_DB_INCONSISTENT" und the process break it
You have an idea what I can still check?
Click to expand...
Click to collapse
Sorry for my late answer.
Double check step 3) you need the correct file from the correct stock rom for your device.
If that still doesn't work I would try reflashing the bootloader preloader (only) from stock ROM and try again.
It should work.

I'm not having any luck with my device on windows 10.
Whenever I try to connect my device to windows via usb, a pop appears - (USB device not recognized-the last USB device you connected to this computer malfunctioned ,and Windows does not recognize it) .
I've also tried to clean up my usb drivers and re-install MTK preloader.
Any advice how I might fix this?

File APDB_MT6797_S01_alps-mp-m0.mp9_W16.48?
Hi,
Where do I find the file "APDB_MT6797_S01_alps-mp-m0.mp9_W16.48"?
It's not available on Google.
Thanks!

Thank q so much .. Fix it.