Related
[HELP] Wifi & Bluetooth gone, no longer functioning (Found BT AND Wifi MAC in CP!)
Just throwing this out there, I've actively used the hell out of my Thrill, and flashed it many times. However, the Bluetooth went out on AT&T's v20p, and Wifi went out after an OC'd crash. I was just wondering if there was some way to reset the chip itself as it seems the on/off for both do nothing, each stays permanently off now. I really want BT back, but I NEED Wifi back... Can somebody help?
I have flashed back to V20P in an effort to get both Wifi and BT working again, but still dead. I will sit on V20P for now, and hope things work eventually.
Trying to enable Wifi comes up with "Activity Wi-Fi settings (in application Settings) is not responding." leading me to believe that the hardware has to be fully reset.
Cynagen said:
Just throwing this out there, I've actively used the hell out of my Thrill, and flashed it many times. However, the Bluetooth went out on AT&T's v20p, and Wifi went out after an OC'd crash. I was just wondering if there was some way to reset the chip itself as it seems the on/off for both do nothing, each stays permanently off now. I really want BT back, but I NEED Wifi back... Can somebody help?
I have flashed back to V20P in an effort to get both Wifi and BT working again, but still dead. I will sit on V20P for now, and hope things work eventually.
Trying to enable Wifi comes up with "Activity Wi-Fi settings (in application Settings) is not responding." leading me to believe that the hardware has to be fully reset.
Click to expand...
Click to collapse
Have you tried a different firmware?
The Dark Lestat said:
Have you tried a different firmware?
Click to expand...
Click to collapse
I've tried V10K, V10D, V20A, V20P, V21D, and V21E, none of them restored the bluetooth (original issue), and so far V10K, V20P, and V21E have not restored the Wifi.
On V21E under settings, it's always showing as "Turning off..." under Wi-Fi. So it's definitely a hardware lockup. Is there anyway to do a full hardware reset on these things? I don't care about opening it, I'm not with AT&T anymore so the phone is mine, and frankly, I just want it to work.
I'm thinking of following some of the instructions for the lost IMEI, see if redoing the Communications Partition restores/fixes the BT and WiFi, I know stuff is getting corrupted when I crash while OC'd, and that's the only thing I haven't touched. I'll try it here tonight and see what I get. I still have both my WiFi and BT MAC addresses (WiFi stored in my router, BT in my computer when it was paired). So... I'll be trying that out soon as I get home today. Think it'll help?
So after fiddling around, I followed these steps from the reset your IMEI/SIM Unlock your phone thread, and started inspecting the CP payload that had to be flashed. I found a couple settings that I think people might find interesting:
1. Connect phone by USB
2. Activate USB debug mode
3. Enter 3845#*920# in dialer if that doesn’t work try 3845#*925#
4. Select Port Settings -> Select CP Image Download
5. A new device should appear at let it install
6. Open Tutty and select serial protocol. Click on open
7. Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
At this point, in order to check your Bluetooth MAC address, type AT%BTAD, this should display a string of 12 hex characters. IF you need to change your BT mac (such as putting it back in like I had to), use AT%BTAD=123456ABCDEF where "123456ABCDEF" is your Bluetooth MAC address (I had mine saved in my computer).
For Wireless MAC address: AT%MAC, same thing if you need to change it AT%MAC=123456ABCDEF. So far this has NOT restored my Wifi or Bluetooth, however it MAY help others who have suffered this loss. You will only need the Flash driver from that thread and tutty, so download the IMEI tool package, but don't worry about the CP unless you absolutely need it. Also, this is great to replace those MAC addresses once you flash (as they're likely wiped with the entire CP wipe).
I'm requesting some assistance with getting my Wifi and Bluetooth operational again if possible, maybe it's kernel modules, I'm not 100% sure, however, in the debug menu (3845#*<MDLNM>#) there is logging options for certain sections of the system. I'll be more than happy to provide logs if requested, I just want my Wifi and BT back and I feel like I'm onto something maybe. Here's to hoping!
Cynagen said:
I'm thinking of following some of the instructions for the lost IMEI, see if redoing the Communications Partition restores/fixes the BT and WiFi, I know stuff is getting corrupted when I crash while OC'd, and that's the only thing I haven't touched. I'll try it here tonight and see what I get. I still have both my WiFi and BT MAC addresses (WiFi stored in my router, BT in my computer when it was paired). So... I'll be trying that out soon as I get home today. Think it'll help?
So after fiddling around, I followed these steps from the reset your IMEI/SIM Unlock your phone thread, and started inspecting the CP payload that had to be flashed. I found a couple settings that I think people might find interesting:
1. Connect phone by USB
2. Activate USB debug mode
3. Enter 3845#*920# in dialer if that doesn’t work try 3845#*925#
4. Select Port Settings -> Select CP Image Download
5. A new device should appear at let it install
6. Open Tutty and select serial protocol. Click on open
7. Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
At this point, in order to check your Bluetooth MAC address, type AT%BTAD, this should display a string of 12 hex characters. IF you need to change your BT mac (such as putting it back in like I had to), use AT%BTAD=123456ABCDEF where "123456ABCDEF" is your Bluetooth MAC address (I had mine saved in my computer).
For Wireless MAC address: AT%MAC, same thing if you need to change it AT%MAC=123456ABCDEF. So far this has NOT restored my Wifi or Bluetooth, however it MAY help others who have suffered this loss. You will only need the Flash driver from that thread and tutty, so download the IMEI tool package, but don't worry about the CP unless you absolutely need it. Also, this is great to replace those MAC addresses once you flash (as they're likely wiped with the entire CP wipe).
I'm requesting some assistance with getting my Wifi and Bluetooth operational again if possible, maybe it's kernel modules, I'm not 100% sure, however, in the debug menu (3845#*<MDLNM>#) there is logging options for certain sections of the system. I'll be more than happy to provide logs if requested, I just want my Wifi and BT back and I feel like I'm onto something maybe. Here's to hoping!
Click to expand...
Click to collapse
What ROM are you currently on? Baseband as well.
The Dark Lestat said:
What ROM are you currently on? Baseband as well.
Click to expand...
Click to collapse
Currently running V21E baseband & Prometheus ROM v1.5, I've managed to make the phone stable again, however still no Wifi or BT. Inside CP, AT%IMEI, %BTAD, and %MAC show correct, thanks for the assist.
If I was on AT&T, this lack of Wifi would be absolute murder, but thankfully, T-Mo's got 5GB of 4G so I can still use my phone, just not half the apps (like Netflix (it checks Wifi status and locks up), or XBMC remote).
Cynagen said:
Currently running V21E baseband & Prometheus ROM v1.5, I've managed to make the phone stable again, however still no Wifi or BT. Inside CP, AT%IMEI, %BTAD, and %MAC show correct, thanks for the assist.
If I was on AT&T, this lack of Wifi would be absolute murder, but thankfully, T-Mo's got 5GB of 4G so I can still use my phone, just not half the apps (like Netflix (it checks Wifi status and locks up), or XBMC remote).
Click to expand...
Click to collapse
I would say that you should try going back to FroYo and checking those addresses again.
The Dark Lestat said:
I would say that you should try going back to FroYo and checking those addresses again.
Click to expand...
Click to collapse
I've gone back to FroYo without any change to Wifi or Bluetooth, but I'll go back to V10K and check the CP again.
Explanation
Cynagen said:
I'm thinking of following some of the instructions for the lost IMEI, see if redoing the Communications Partition restores/fixes the BT and WiFi, I know stuff is getting corrupted when I crash while OC'd, and that's the only thing I haven't touched. I'll try it here tonight and see what I get. I still have both my WiFi and BT MAC addresses (WiFi stored in my router, BT in my computer when it was paired). So... I'll be trying that out soon as I get home today. Think it'll help?
So after fiddling around, I followed these steps from the reset your IMEI/SIM Unlock your phone thread, and started inspecting the CP payload that had to be flashed. I found a couple settings that I think people might find interesting:
1. Connect phone by USB
2. Activate USB debug mode
3. Enter 3845#*920# in dialer if that doesn’t work try 3845#*925#
4. Select Port Settings -> Select CP Image Download
5. A new device should appear at let it install
6. Open Tutty and select serial protocol. Click on open
7. Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
At this point, in order to check your Bluetooth MAC address, type AT%BTAD, this should display a string of 12 hex characters. IF you need to change your BT mac (such as putting it back in like I had to), use AT%BTAD=123456ABCDEF where "123456ABCDEF" is your Bluetooth MAC address (I had mine saved in my computer).
For Wireless MAC address: AT%MAC, same thing if you need to change it AT%MAC=123456ABCDEF. So far this has NOT restored my Wifi or Bluetooth, however it MAY help others who have suffered this loss. You will only need the Flash driver from that thread and tutty, so download the IMEI tool package, but don't worry about the CP unless you absolutely need it. Also, this is great to replace those MAC addresses once you flash (as they're likely wiped with the entire CP wipe).
I'm requesting some assistance with getting my Wifi and Bluetooth operational again if possible, maybe it's kernel modules, I'm not 100% sure, however, in the debug menu (3845#*<MDLNM>#) there is logging options for certain sections of the system. I'll be more than happy to provide logs if requested, I just want my Wifi and BT back and I feel like I'm onto something maybe. Here's to hoping!
Click to expand...
Click to collapse
Please Explain Tutty. I get into the hidden screen and tried the download and nothing was downloaded, this is my first smartphone and do no that there is no MAC address for the bluetooth device. it is the only thing not working. Thanks in advance for the help.
****Follow Info, Warnings & guides on associated links / pages****
For those of you reading this and in this forum, and if you've rooted before, flashed a rom, or anything like that and got it to work, DO NOT be intimidated by using this method.
I found I actually quite liked Ubuntu (it was my first time using it myself). And it's rather easy.
This is the page I followed, and if you scroll down most of the way (use the one at post #30 ircc) there's a video too. I set up my screen so it was just like in the video, plus a "window" to watch the video too. The directions are exact, what I liked about the video is you could see it run and the results, which helped me realize where things went wrong after it failed about 3 times or so.
***Thanks to drjbliss (method), SamuriHL (HoB & more), & Tomsgt123 (video)***
Things upfront:
I used a Bootable USB, You can do it with a Bootable / "live" CD, but admittedly I thought USB was quicker to set-up and in hindsight probably was beneficial. So that's what I recommend.
Get Ubuntu (img/iso) & follow the directions from HERE.
Make the USB, then restart your computer, and at boot screen, choose boot from USB.
Here's where it saved me and and I'll recommend something else here, not in the instructions... yes it's going to take a bit longer but in the end I spent almost a whole Saturday doing this and this would've made it about an hour had I done it first. It was the solution to 2 errors I had, that took a while to realize where they were and find a fix.
In Ubuntu, open a "terminal" which is like a windows cmd / command window.
I couldn't find a button or anything on a menu to do this so I found out it's either alt + t or ctrl + alt + t.
at the Ubuntu terminal command prompt:
use these 2 commands to update Ubuntu and Samba.
sudo apt-get update
sudo apt-get upgrade
[IIRC] The Ubuntu one will tell you it needs and additional 250 (or so) MB's hit ok or accept and let it update. Then do the next and update Samba.
I'm not exactly sure but I doubt I would've been able to do this with a cd being that it couldn't write to it.
This took care of all errors I ran into using this Root method, and it was a bit frustrating because if you don't know what you're looking for or at, you can get to the end and it says exploit finished or complete or something and you think you're good to go.
On to the root instructions & Video...
I opened (2) terminal windows, you have to manually put them on the same screen or it will move them to multiple ones and that doesn't help so much.
If it does, use the button on the side that looks like (4) windows and pick & drag everything back to one screen.
Errors or what to look for:
when you run this command: sudo apt-get install samba
if it says (something) "unknown" or "Failed" - Samba didn't install, try again. (update if you skipped that part)
when you try to connect remotely over WIFI...
If you get "network connection error / failed", Samba didn't install, or Samba needs update (if you skipped that), or make sure you use the right IP address, a few of them will come up. I found for me it had nothing to with my network and I had the right IP the first time I tried.
****NOTICE****
Ubuntu will let you keep going and continue to run the commands seemingly normally. Even to the end and tell you "exploit complete" (or something like that) So if you get to the end and you don't have root go back and examine your terminal screen. Compare it to the one in the video, something won't match, and there's the issue.
I did notice the "numbers" didn't always match as it ran thru the processes, but make sure it looks like your getting the same type of results and runs thru the process.
I needed to update Ubuntu to update Samba that's why I recommend doing both first.
Once you set-up & update your USB the whole thing shouldn't take more than 15-20 mins or so.
Good luck.
It's really not hard, just follow the instructions.
I tried following the steps for Jelly Bean root, but I think the samba share thing may be holding me back. I know how to do it, that's not the problem. The problem is, I don't have a wifi setup at home, so I wouldn't be able to connect to the Ubuntu live image even if I could set up my Files app the way I'm instructed to. When I go to the section in the Files app to input the information, I don't have all the fields show up for the necessary information. Plus I have a version of Ubuntu running on my laptop that shouldn't require a wireless connection between my phone and the computer, since I can just plug the thing into it. I know this method has worked for many people, and I'm not exactly a noob, my first Android phone was the very first one, the G1. With each Droid style phone I got, I had it rooted within either hours or days, so I am capable of doing it. Also, I know there either isn't a one-click method yet or if there is I can't find it, but is there a way to circumvent the whole samba thing so I don't have to mess with the wifi connect? Finally, and thank you for your patience in reading such a long text, worst case scenario; if I were to try to fxz back to ICS stock (I know it'd more-than-likely brick my phone), is there an unbrick method for those of us who've let themselves spend way to much time obsessing over their phone (I tend to get a little tunnel visioned when it comes to this stuff), or would I be totally screwed? As many on this forum, thanks for all the hard work, and I apologize in advance if I seem a little whiny about this. I should point out that even without the wireless connection between the phone and the computer, the program still runs and displays the terminal screen that roots the phone. It stops just a few lines after the "push a hardware button" phase to make it vibrate. It never vibrates, but Superuser does get copied to the phone, it just install the binaries for it.
Hi guys
as you can see in the attached file, i have a litte issue
a friend of mine dropped the phone and a car runned over it lol...digitizer and lcd are gone but the phone still boot up and it is recognized by the computer. My friend don't care about repairs but he wants the data back and here starts the problems:
-adb is off
-phone is password protected (so no kies and no sdcard reading from pc), phone stay in the "insert password" at startup.
-i don't even know if support mhl to attach on a tv
how can i recover the data? The only idea i have is to dump the rom and load it on an android emulator but i don't even know if its possible. Can someone give me a hint to recover the data? Thank you
1) Buy a replacement screen
2) Get the data
3) Sell fully working phone
...
Profit!
that was my idea...my friend do not approve
Jammed_Death said:
that was my idea...my friend do not approve
Click to expand...
Click to collapse
Did you try the S-pen to input the password?
i can't get a precise feedback. I think i'm not pressing the correct numbers and after half hour of wasting time i was looking for other options. Does this phone support mhl? If yes, i have to enable in settings or something else?
Jammed_Death said:
i can't get a precise feedback. I think i'm not pressing the correct numbers and after half hour of wasting time i was looking for other options. Does this phone support mhl? If yes, i have to enable in settings or something else?
Click to expand...
Click to collapse
I dont know qbout mhl, never used it. The phone does support it though.
Another idea might be a usb-otg cable and a keyboard(password entry).
Not sure if that works on a stock rom, but try it.
Can any one shed any light on this unit (root roms etc)
Having recently bought because of its 2 sec boot time due to mcu unit
Having read through threads to identify it
I am none the wiser
Tried accessing Oem settings too but no passwords used or
Recommended in the forum seem to work
Is it possible to mod in any way
I have checked in settings /about
And no reference to mtcd or b etc can be found
Please help
Thanks
Ref
https://www.amazon.com/ATOTO-Touchs...?ie=UTF8&qid=1488239263&sr=8-1&keywords=Atoto
Ref
http://www.myatoto.com/index.php?m=content&c=index&a=show&catid=15&id=17
Did you figurw out anything on this device? Im gettin it 2day.
Sent from my A0001 using Tapatalk
R u able to use adb with it?
https://forum.xda-developers.com/an...d-units/stop-m4272-root-t3561066/post71458964
I have not tried adb
But looks like it works and root too
According to above posts
So now how do we go about identity of unit beyond atoto
To see if any roms are compatible
I recently contacted atoto about low mic volume/gain
They said they would release an app soon to control the mic better.but they are currently focused on a newer unit with
Androids 6.0 so that has delayed releases for current m4
They did say they had the sdk for android 5.1 for this unit
As I had a mic problem I did some digging with
Shortcut master
https://play.google.com/store/apps/details?id=org.vndnguyen.shortcutmaster.lite
And this gave access to hidden Oem settings
In audio then choose mic and then levels
Having changed level 1 to 240 (set) and all other levels up til 8
Are also changed to 240 ( max is 255 if you prefer)
My mic preformed much better now but could still do with a little tweaking.
Thanks for the info for the oem settings. Shortcut master got me into it. Just searched for oem...
I was able to get into engineer mode with apex launcher b4, but thanks though.
Also the bootanimation in the app section work on this unit. Just got to rename to bootanimation.zip and put it in /system/media/
Cant get usb debugging to work. Checked it in dev options and even edited the build.prop and default.prop with
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb,mass_storage
Then there was another setting in there that was
ro.sys.usb.storage.type=mtp,mass_storage
I changed it to
ro.sys.usb.storage.type=mtp,mass_storage,adb
And still cant adb through usb.. Can anybody help?
I have not tried usb debugging but just wondering if you tried each USB port as in the manual it says each port is designed for a specific device/ add on like camera phone etc
But I have no idea if this makes a difference
But anything is possible with android as I have learned over the years
I have the 2 long usb cables running to the front dash using, Rerii 1 Meter 3ft Dual USB Extension Flush, Dash, they both work with mass storage and charge my phone. Both work with a wireless keyboard and mouse also. Havent tryed the short cable, being i installed the unit b4 i got the rerii adapter, and its a pain takin the dash apart.
Think thats just how the other things get mounted, if u look at storage in the settings, the mounts r already there.
Really need to get usb adb to work. Default.prop keeps reverting back to stock.. Im gonna keep lookin for solutions.
Also. When reboot to Recovery it goes straight into installing update, no menu. Bootloader reboots after like 5-10sec.
Maken a nandroid backup now. Gonna try n make a recovery for it..
New firmware 8.0.3 was just posted
Have not had a chance to fully test it to see what's new
But easy connect now works with my phone
Nexus 6p 7.1.1 march pure nexus rom
So I am happy as it has not worked at all on 7.1.1 till now
Note unit m/4 must have an internet connection for 1st install of easy connect to phone
Or else it will fail to download needed services for success
Also needed to setup Bluetooth and wifi again after update
Note my phone will not connect with Bluetooth pin 0000
Change to 1234 and then it connects ok.
New email from atoto today
"Our engineer is working on release an microphone gain control app in the next 2-3 weeks, so I have to ask you wait for extra a few days."
downloading when i get the pass... Smh
Whats the password?
Password is atoto
Please read the install instructions in the extracted zip
Before proceeding
As it has a 2 part update
Thank u.
Installed the new update, its buggy as ****. The subwoofer settings wont stick, and dnt sound right.. And clock wont wont save. Soon as u turn the car off and back on, the clock is wrong.. Smh.
Supposed to be CPU: MTK Soc-based Quad-core 1.5Ghz. Mine only gets 1.3Ghz. What is yours running at?
Sent atoto an email about the bugs
Waiting on reply maybe Monday
Have had this clock problem on kitkat before
USA has set its clock back but Europe has not done it yet
During this window of difference some clocks act weird
Well at least last time this happened that's what it was
Have not checked cpu will get back to you on that
Also noticed firmware 8.0.3 reports as 8.0.2 in settings
Not sure why???
There is another update https://www.adrive.com/public/wtGBAn/ATOTO OS Update for M4 0318.rar
It fixed the clock issue. Change the subwoofer settings, but its still buggy.
Can you check the cpu with cpu-z? Thanks.
Did u get urs rooted yet? Its a pain in the butt, but i got it. I wander if any of the xposed mods will work.
Need to get usb debugging to work, so i can go about porting twrp.
File transfer does not work (keeps falling back to "USB for charging" always)
Hi,
as the title suggests for a very long time (>1 month) my file transfer does not work.
The only way I can transfer files from PC to the phone is reboot into recovery (TWRP) and there it works normally, but it's a pain in the a...rm.
I've also tried different ROMs with the same effect, although I remember it did work very briefly for one boot cycle before I finished setting everything up and now it doesn't work again.
My suspicion is that some hidden setting that I'm not aware of is in conflict with the file transfer feature. Or maybe Xiaomi doesn't like it when you deny Mi Cloud permissions etc. and that's the way they get back at you, IDK!
Nobody else experiences this? Cause I didn't find too many complaints about this in the forum.
Happy new year and a very good and successful start into 2020, everyone.
If you not sure what cause the problem, just switch to another rom or do a hard reset.
Sent from my MI 9 using Tapatalk
anthropaki said:
Hi,
as the title suggests for a very long time (>1 month) my file transfer does not work.
The only way I can transfer files from PC to the phone is reboot into recovery (TWRP) and there it works normally, but it's a pain in the a...rm.
I've also tried different ROMs with the same effect, although I remember it did work very briefly for one boot cycle before I finished setting everything up and now it doesn't work again.
My suspicion is that some hidden setting that I'm not aware of is in conflict with the file transfer feature. Or maybe Xiaomi doesn't like it when you deny Mi Cloud permissions etc. and that's the way they get back at you, IDK!
Nobody else experiences this? Cause I didn't find too many complaints about this in the forum.
Happy new year and a very good and successful start into 2020, everyone.
Click to expand...
Click to collapse
First, do you have the correct drivers installed on your PC to identify your device?
Second, you can always turn on USB Debugging and see if that allows you to use FTP.
Third, if you have turned on USB Debugging, you can use adb push.
If I wanted to transfer Roblox to my phone, I would do this
adb push C:\Users\SenseiCheekClapper\Downloads\Roblox.apk /sdcard
To make it a hell of a lot easier, just type adb push, drag the file into the terminal and it will autofill the file location, and then type /sdcard.
Sent from my MI 9 using Tapatalk
When I have had this problem it has always turned out to be the USB-cable that was the culprit. This phone is very picky when it comes to cable, both for file transfer and Android Auto, at least for me! The original cable doesn't always work all the time for me, but a good quality cable of another brand always works for me.