Database Info

Headphone adapter - no audio

Has anyone found that their headphone adapter has stopped working for some reason?
Was working fine, and now seems that the phone no longer recognizes the adapter. Power passes through just fine - however, can't get audio out.
Please let me know if you have any suggestions? I don't have a spare adapter to test.
Thanks,
Chip

I'm afraid that is the test. Either use your headset on a different phone, or a different headset on your phone.
You should be able to test a headset at your local phone retailler (just tell them you want to check it works before you buy it)

I'm having the same problem, just not at your stage yet.
I have audio but it's obvious there are some connections that aren't quite lining up since I get mono out of both speakers now instead of stereo and moving the connector at all gives me the typical "short out" garble you hear when you've disrupted a short in an audio cable.
The only time anything is plugged into my phone is when it's laying flat on a desk (I even make sure the wire comes out straight with NO pressure on it at all). I've never forced the cable, had it in my pocket where it could have put pressure on the connection, or anything else that might have caused the problem...
I think it's just wear. I can still charge the phone just fine, it's just audio that is screwed up now. I'm just waiting for the day when I don't hear anything...
...and I'll probably never buy HTC again... since this happened with my Star Trek too.

Beeble said:
I'm afraid that is the test. Either use your headset on a different phone, or a different headset on your phone.
You should be able to test a headset at your local phone retailler (just tell them you want to check it works before you buy it)
Click to expand...
Click to collapse
So I went to the AT&T store - a headset worked fine.
I went out and bought a new headphone adapter - same thing, doesn't get recognized by the Phone, so still SOL.
Question - any idea of this could be software related? I had installed skype (uninstalled to see if this was the cause) and wondering if that did something to the headset settings.
Any value in reimaging with a new ROM to see if this fixes it before calling AT&T warranty?
Thanks,
chip

igolfchip said:
So I went to the AT&T store - a headset worked fine.
I went out and bought a new headphone adapter - same thing, doesn't get recognized by the Phone, so still SOL.
Question - any idea of this could be software related? I had installed skype (uninstalled to see if this was the cause) and wondering if that did something to the headset settings.
Any value in reimaging with a new ROM to see if this fixes it before calling AT&T warranty?
Thanks,
chip
Click to expand...
Click to collapse
If you have flashed cooked ROMs then you will have to flash back to stock for warranty reutrn anyway, so this could likely be your issue.
If you're on the stock ROM, then I would suspect hardware.

Bruce Inman said:
If you have flashed cooked ROMs then you will have to flash back to stock for warranty reutrn anyway, so this could likely be your issue.
If you're on the stock ROM, then I would suspect hardware.
Click to expand...
Click to collapse
Thanks Bruce - about to call AT&T warranty to get relief (within 1 year).

[REQUEST] A patch (kernel?) to disable the htc car-mode switch event.

Hey guys,
I have an evo that has a weird glitch with the USB port.
It seems, anytime the weather is humid, my phone will sparatically start switching in and out of car-mode repeatedly. This has been causing my phone's cpu use to spike, screen to turn on randomly, and worst of all - when the phone is in car mode, I lose control of changing media volume with up-down switch, it forces dock volume.
From what I've found online, car mode is enable/disabled with the 4th pin going to ground in the USB port, which apparently my phone has been finding a way to bridge sporadically.
There are plenty of solutions that say 'delete the apk for the car mode app', but it'll still make me lose control of audio volume, and always be in speaker mode in calls.
Other than this problem, my phone works perfectly normal.
So, is there a way to prevent this pin from being picked up by the kernel or have android completely ignore this event or intent?
If I knew it was in the kernel source code (and where), I wouldn't mind learning how to cook a kernel myself to do it.
Thanks for any help.

MrStabby said:
Hey guys,
I have an evo that has a weird glitch with the USB port.
It seems, anytime the weather is humid, my phone will sparatically start switching in and out of car-mode repeatedly. This has been causing my phone's cpu use to spike, screen to turn on randomly, and worst of all - when the phone is in car mode, I lose control of changing media volume with up-down switch, it forces dock volume.
From what I've found online, car mode is enable/disabled with a 5th pin going high in the USB port, which apparently my phone has been finding a way to bridge sporadically.
There are plenty of solutions that say 'delete the apk for the car mode app', but it'll still make me lose control of audio volume, and always be in speaker mode in calls.
Other than this problem, my phone works perfectly normal.
So, is there a way to prevent this pin from being picked up by the kernel or have android completely ignore this event or intent?
If I knew it was in the kernel source code (and where), I wouldn't mind learning how to cook a kernel myself to do it.
Thanks for any help.
Click to expand...
Click to collapse
I have this issue as well and have been trying to figure it out. Currently have something close for aosp roms, but going to take more time to figure out for sense. I have been looking into it.

Wow, I thought it was just me/my phone.

github said:
Wow, I thought it was just me/my phone.
Click to expand...
Click to collapse
nope we should start our own club. Busted ass usbport club. I looked into swaping the port out and soldering on a new one. But after I looked at this little tiny piece of hardware, I though a software edit will be easier. And it is you need some intense tools to pull off a good swap. its sooooo small.

lithid-cm said:
I have this issue as well and have been trying to figure it out. Currently have something close for aosp roms, but going to take more time to figure out for sense. I have been looking into it.
Click to expand...
Click to collapse
Thanks, I figured it's a common problem but it would be nice to find a good solution.
I haven't seen too much of a connection with particular roms causing the issue. When it was originally a big problem a few months back (before it stopped happening for me), it would act the same way on every rom I stuck on it.
However, I just switched from deck's aosp rom to Synergy not long before this started happening again, and the sense roms definitely make it much more of an apparent problem than the AOSP roms would.
Physically to stop the problem, I know it's related to the MicroUSB port and I may try disassembling it if it gets bad enough.
From another post on it: "It's pin 4, not 5 , 5 is ground in the usb cable, when pin 4 is grounded it puts the unit in dock mode."
I'd post a link to the pinout, but the system makes me too newb to post pin outs. (Just google kineteka microusb b)

The same thing happened to my phone yesterday and it is pissing me off. Will it eventually go away over time or is it a permanent issue. Meaning when it dries off will everything be ok. I'm thinking about taking it in since I have insurance and see if they will either fix it or swap it out. I'm going to wait a couple of days to make sure there is no moisture in there.

There is an app called NoDock that you can download to fix this. In my experience, it does not work with MikG (which is probably a Sense 2.1 compatibiltiy issue). I am running Deck now too, and so far no issue with the AOSP ROM. If there is an issue, I read on the NoDock market page that CM based ROMs have an option to disable, and thus NoDock is not needed in this case.

Hmm. I'd think an app could be written that would catch the intent and do nothing, as well as manually adjust car dock volume via the volume controls. Maybe. But I don't think any kernel-level edits are needed. Maybe a decent dev can write something like that for you (I couldn't). [Edit: looks like NoDock might be that app] Another thought that might be stupid: have you taken a can of compressed air to your USB port?
Also, just a friendly reminder, there isn't any development work posted here so instead of the development subforum, this really belongs in General, or maybe Q&A. As a general rule, new threads in this section are only for sharing work you've done. Not to pretend I'm a mod or anything, just wanted to warn you so you don't get flamed to death next time.

In sense roms might be able to check AndroidManifests for either
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_DOCK
or
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_MODE
Then remove the intent from the application, so that nothing would happen.

lithid-cm said:
In sense roms might be able to check AndroidManifests for either
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_DOCK
or
http://developer.android.com/reference/android/content/Intent.html#CATEGORY_CAR_MODE
Then remove the intent from the application, so that nothing would happen.
Click to expand...
Click to collapse
I was definitely looking into this within the android.policy.jar but my developer knowledge is minimal compared to your expertise. I'm really hoping to not have to download any apps and I'm reluctant to go get an insurance claim until the new OTA has been rooted successfully. Anybody makes any move forward on this I would be glad to donate. This started happening to me when I was working out with my phone in an armband and some sweat most likely got into the charger port causing a short (my theory on what happened). If it is still going on by the time the OTA gets rooted, I'm going to go swap it out at the Sprint store.

mjhuffer said:
I was definitely looking into this within the android.policy.jar but my developer knowledge is minimal compared to your expertise. I'm really hoping to not have to download any apps and I'm reluctant to go get an insurance claim until the new OTA has been rooted successfully. Anybody makes any move forward on this I would be glad to donate. This started happening to me when I was working out with my phone in an armband and some sweat most likely got into the charger port causing a short (my theory on what happened). If it is still going on by the time the OTA gets rooted, I'm going to go swap it out at the Sprint store.
Click to expand...
Click to collapse
I am actually looking to buy a rooted one on ebay. Then use this one for deving. I really like the evo no reason to let it go yet.

lithid-cm said:
I am actually looking to buy a rooted one on ebay. Then use this one for deving. I really like the evo no reason to let it go yet.
Click to expand...
Click to collapse
I thought it was illegal to sell rooted phones period. Or is it only illegal to make extra profit just based on the fact that it is rooted. That isn't to say that someone will do it anyways. My brother, who is phone illiterate, just got a nexus s and I really like it. I heard that the GSM version will be the first phone to get ICS (ice cream sandwich) so that means the CDMA one will be next. I'm perfectly happy with my EVO except when dumb stuff like this happens. I hate myself for asking but you got any progress on the rooting of 4.24 and the newest Hboot. Has the source code for the new Hboot been released?

I had a similar problem however it was caused by me putting my phone in my car dock
I had to freeze/uninstall both car panel and dock mode for it to finally stop giving me a notification and blinking the screen on and off when I hit bumps

Soldering USB port
lithid-cm said:
nope we should start our own club. Busted ass usbport club. I looked into swaping the port out and soldering on a new one. But after I looked at this little tiny piece of hardware, I though a software edit will be easier. And it is you need some intense tools to pull off a good swap. its sooooo small.
Click to expand...
Click to collapse
Had the USB issue on mine too.
Usb port is anchored down to circuit board in 4 places, those solder joints get
loose and the trouble begins.
I used a regular soldering iron to heat up the solder and bring the port back against the circuit board tight, no more car-mode.
Ed

chile62 said:
Had the USB issue on mine too.
Usb port is anchored down to circuit board in 4 places, those solder joints get
loose and the trouble begins.
I used a regular soldering iron to heat up the solder and bring the port back against the circuit board tight, no more car-mode.
Ed
Click to expand...
Click to collapse
I appreciate the response and im looking into it myself but what exactly do those points have to do with the electronic conductivity of the port? Do they have something to do with the ground.

odd, i had this same problem, what fixed mine was flashing a new different nv, it stopped it almost immediately
MrStabby said:
Hey guys,
I have an evo that has a weird glitch with the USB port.
It seems, anytime the weather is humid, my phone will sparatically start switching in and out of car-mode repeatedly. This has been causing my phone's cpu use to spike, screen to turn on randomly, and worst of all - when the phone is in car mode, I lose control of changing media volume with up-down switch, it forces dock volume.
From what I've found online, car mode is enable/disabled with the 4th pin going to ground in the USB port, which apparently my phone has been finding a way to bridge sporadically.
There are plenty of solutions that say 'delete the apk for the car mode app', but it'll still make me lose control of audio volume, and always be in speaker mode in calls.
Other than this problem, my phone works perfectly normal.
So, is there a way to prevent this pin from being picked up by the kernel or have android completely ignore this event or intent?
If I knew it was in the kernel source code (and where), I wouldn't mind learning how to cook a kernel myself to do it.
Thanks for any help.
Click to expand...
Click to collapse

loose usb port
mjhuffer said:
I appreciate the response and im looking into it myself but what exactly do those points have to do with the electronic conductivity of the port? Do they have something to do with the ground.
Click to expand...
Click to collapse
The 4 points only hold the usb plug on to the board, on the backside of the plug, is where the actual connections are being made. They are almost like spring loaded connections.
When the soldered points get weak, the usb gets pulled pulled away from the mother board and some of the pins will not make contact.
Ed

Here is a kernel for CM7 removing dock accessory detection based on the latest CM7 kernel. If someone wants to build a version for Sense or based on another kernel, just unselect config_usb_accessory_detect and config_dock_accessory_detect support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.

This is crazy mine an my girls phones are doing this we bought a charger off of eBay an that's when it started I tried titanium pro an froze car mode seems to work but just a bandaid
Sent from my PC36100 using XDA Premium App

sbradymobile said:
Here is a kernel for CM7 removing dock accessory detection based on the latest CM7 kernel. If someone wants to build a version for Sense or based on another kernel, just unselect dock support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
Click to expand...
Click to collapse
Thanks man I'm going to wait for some dev to jump on this. Hopefully someone can create a .zip so you can flash it over any kernel. I would really just like the stock kernel with this option added in.

USB host connection works once

I have the official Samsung USB Connection kit. Both connectors work fine immedeately after boot, but once the device has 'slept' they do not work anymore. I get a notification that the USB Connector is connected, but whatever I insert nothing happens. LEDs (on USB sticks, mice, ...) do not light up which seems to indicate that no power is applied to the port.
I'm running stock Android, rooted. Booting into safe mode makes no difference.
Any ideas what's going on?

You're not the only one, except that in my case USB sticks do light up. IMHO Samsung seriously botched up the automounter in their last update. I wonder how long it's going to take them this time to get their act together and produce a bugfix.

I have exactly the same problem, wich really annoying as I bought this tablet in order to work on it (with a keyboard). I'll try Samsungs suport...

SpicyKiwi said:
I have exactly the same problem, wich really annoying as I bought this tablet in order to work on it (with a keyboard). I'll try Samsungs suport...
Click to expand...
Click to collapse
Good luck with that. I contacted Samsung support Benelux and was told it was because Amazon Germany had installed "German software" on my tablet.
Trust me, that is NOT the case...

karel jansens said:
IMHO Samsung seriously botched up the automounter in their last update.
Click to expand...
Click to collapse
I'm not sure it's the automounter. Keyboards and mice show the same problems.

sciurius said:
I'm not sure it's the automounter. Keyboards and mice show the same problems.
Click to expand...
Click to collapse
You might be right, I haven't tried one of those yet. Of course, that would mean Samsung botched up the entire USB subsystem of our Note, which is kinda even worse.

Seriously, is anything done about this usb c**kup, or what? I bought my Note, expecting it to replace my venerable Archos 101 which, incidentally, had excellent usb connectivity three blooming years ago and on Android 2.1, only to find out that not only did I have to buy motherloving adapters for the Note, but on top of that that they don't even work properly.

I also came from Archos 10.1 IT so I know your pain...
My only hope is that we will soon get the 4.2 update, and that it will fix this problem.
If not, I'll probably going to flash CM on it to see if this works better.
Unfortunately, I've seen no CM reports that USB host works flawlessly.

sciurius said:
I also came from Archos 10.1 IT so I know your pain...
My only hope is that we will soon get the 4.2 update, and that it will fix this problem.
If not, I'll probably going to flash CM on it to see if this works better.
Unfortunately, I've seen no CM reports that USB host works flawlessly.
Click to expand...
Click to collapse
Quick question, has anyone has the adapter problems while on Android 4.1.1? I tried my adapters on a shop showroom model of the Note 10.1 and they worked perfectly, but only afterwards I noticed that Note was running 4.1.1, while mine is up to date with 4.1.2.
I'm just trying to avoid having to send back a piece of equipment that, despite everything, I can barely miss.

One of the USB OTG tools (forgot which one) had a table of functioning USB host versus Android releases and last time I looked the number of 4.1.2 devices that hat USB problems was significantly higher than the 4.1.1 devices. So I have all reason to believe it is a software problem, introduced in 4.1.2.
EDIT: The tool is USB Host Diagnostics from ChainFire.

So, is there an easy way to go back to 4.1.1 on the BigNote? Mine came with 4.1.2 installed anyway and something tells me that, if I ask Amazon to downgrade for me, I'll be answered with a deafening silence, probably with a "Duh?" In there somewhere.
On second thought, scratch the easy part; is there any way to downgrade a BigNote without losing any of Samsung's added value (yes, I happen to consider most os what they added actually valuable).

[Q] Unique tf300t Issue

Hello folks!
I purchased a bricked TF300t from ebay. I knew it was bricked when I bought it, but I asked the original owner a bunch of questions before buying and it seemed like I could fix it. Well he wasn't completely honest about the issues it had and now I am stuck in a bootloop. It will load the ASUS splash screen, then it will begin to load the rom by showing the metallic looking asus splash screen with the spinning circle. It will spin for a little while, freeze, then reboot.
I was able to flash the stock JB 4.2 rom via the sdcard and the stock recovery (yes it is the JB bootloader) and this is where it lands me. I was hoping to use a TWRP or ClockworkMod recovery, but when I boot to the bootloader and it says fastboot protocol is on, neither of my Windows 8x64 pc will recognize it. Not just that it can't find the right driver, but that it doesn't see anything at all has been connected. Nothing in the device manager, no sound effects, nada. I have no blobs, so APX is worthless to me (and it doesn't find anything in apx mode either). I have used universal ADB drivers, Naked drivers, Driving Ms. Daisy, all to no avail. I have also tried to connect it to a 64 bit windows 7 machine with no luck. I am using the stock USB cable as well.
Basically I need a way to get out of the bootloop, a way to make fastboot work, or to flash a new recovery via sd-card (which I don't even think is possible). Any suggestions would be appreciated.
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.

brandonharrison10 said:
Hello folks!
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.
Click to expand...
Click to collapse
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.

graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.

brandonharrison10 said:
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.
Click to expand...
Click to collapse
I read your OP again. Your problem is interesting. I assume at this point your tab is stuck at the bootloader with at least 2 icons (RCK and Wipe Data), since if you can load the 4.2 rom, you can use Goo manager to download the custom recovery. But even if stuck at fastboot page, you should be able to select RCK and flash back to 4.1 with the official zip (104220 unzipped once) on SD card. I've done this after selecting the wipe data icon (while you're on official rom with no custom recovery installed, it's safe to wipe data). Once you succeed at downgrading to 4.1, you can work your way back up to 4.2. Have you tried this?

graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?

TwStD said:
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?
Click to expand...
Click to collapse
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.

graphdarnell said:
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.
Click to expand...
Click to collapse
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.

pyraxiate said:
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.
Click to expand...
Click to collapse
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.

TwStD said:
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.
Click to expand...
Click to collapse
Also try different usb ports as well. Its weird, but fixed my issue. Also on laptops, some have daughterboards or small ribbons connecting to some of the USB ports. Its worth a shot trying different ports on a laptop as well.
Let us know if it works !
If not, it could be your dock connector as mentioned earlier. Luckily, they are cheap though.
http://www.ebay.com/itm/OEM-ASUS-TF...216?pt=LH_DefaultDomain_0&hash=item1e7a699730

OK, will do. Thanks!

try using a Linux. and install adb and fastboot drivers. win8 is a pain in the butt with android. i switched to Linux mint as a main os for everything android. also check the forum here. I posted a guide to reflash from a softbrick as long as fastboot is working.
Unrecoverable bootloader error but not Bricked!
http://forum.xda-developers.com/showthread.php?p=44244313
Unrecoverable bootloader error but not Bricked!
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

Generic Android 5.1.1 MTCD Navigation Radio Install for BMW e46

Last month, I found this this Android 5.1.1 Headunit on Aliexpress for $227 shipped. I decided that the price was low enough to take the risk and purchased. The vendor's store is TONGTAI HONGKONG INDUSTRIAL CO.,LTD I am not endorsing the vendor, I didn't need them for any support yet, but I assume people will ask due to price.
Today was the first nice day since I got it, so I did the install this morning. I'm not going to recreate the install here, as there are already many for the Eonon, Dynavin, Avin, and others. This is just like those. I will note where I came across anything I wasn't expecting below.
A couple of points, I did not install a backup camera. My E46 is a Cabrio, and visibility is fine, I just don't think the benefits are there for me. Additionally, DVD is not important so I didn't check that out. I do want a working Radio, Bluetooth Calling and streaming and Navigation. This unit is doing all of that.
Opened Box
Retail box - I've seen other units that have the identical packaging
As Packed
Parts laid out
Parts laid out 2 - Note- connectors for the early and late radio's and early and late antennas. My car is one of the 2006 330's, and one of the last off the line.
Closer pic of unit - These look exactly like every other unit on the market.
Navigation SD card included - I read a lot of different solutions on where to put the GPS antenna. I was going to put it in the spot behind the instrument cluster, but BMW already had a factory installed antenna there. I guess by 2006, it was cheaper to put the antennas in all cars (like the factory Bluetooth). I used the metal cross bar above the radio. The antenna has a magnet on the base and i just sat it on top, it won't move. Reception, for me, is fine.
Back of unit. Cleaner than many - Note On many of these units the can-bus plugs into the back. I have been told that that makes fit difficult because of the amount of wires back there. The can-bus came off a pigtail on the mail unit and was easily tucked out of the way.
Another pic of the back of the unit - Note the white input plug under the antenna in. Those were for the RCA connectors for pre-amps. It wasn't needed it this install, the factory harness took care of everything, left those pigtails out.
Top with wiring diagram - All I did was remove the screws and plug it in, I didn't have to refer to any wiring. I will say I had trouble getting the adapter to line up with the factory plug. I almost broke the harness side. Not sure why it was so hard to align, but eventually it did.
Climate controls moved to the lower spot -Here are the climate controls moved into the lower section. I got a used navigation bracket off eBay for $20. The lighter clips were broken on one side, but not off. I had to use a cable tie to "lock" it in. If I had caught that before install, I would have swapped the lighter for a USB
Unit Installed
Radio Screen
Bluetooth Phone Screen
System Screen - Originally this was on a July MCU release, when I went into the about screen, it offered an update. An old ROM was on the Nav Card, and I overwrote the newer ROM with the older version. I sent the vendor a message to see if they can send me the link to the newer one. That said, I am not having an issue with this one.
Here is a walkthrough of it live. The video stops when I use bluetooth, not because of the headunit, but my phone stopped recording when making a call.
https://youtu.be/Vtv2tJte5oQ
All said and done I am very happy with this unit based after installation. I have been reading many people who have issues, so maybe I got a "good" one, or maybe issues are yet to come. If you have any questions, fire away.

Well it was great for 2 hours. Screen is unresponsive now. Any suggestions...
Sent from my iPad using Tapatalk

Sorry I cannot help with the unresponsive screen, but I have a question
For the few hours you enjoyed it, how was the display in direct sunlight?

-=Jeff=- said:
Sorry I cannot help with the unresponsive screen, but I have a question
For the few hours you enjoyed it, how was the display in direct sunlight?
Click to expand...
Click to collapse
It was ok, this morning driving to work their was a good bit of glare, but still very readable. I will try it with the top down and see what it can take would assume that would wash it out.
Pretty sure a matte screen protector would solve any issues with glare. Something like this should do for my screen
http://www.staples.com/Iessentials-...ctor-For-7-inch-8-inch-Tablets/product_210060

I have a car with a targa roof.. I tried a matte protector with my newsmy NU3001 and it did not help. I really like the idea of the Touch screen UI but I think I am out of luck for seeing it on the screen. I have a MTCD unit too but have not tried it yet.

Video of operation w/o working screen
https://www.youtube.com/watch?v=8lGyAQ0rZlg

Pattond said:
Video of operation w/o working screen
https://www.youtube.com/watch?v=8lGyAQ0rZlg
Click to expand...
Click to collapse
Have you tried to reflash the unit? Factory ROM for you unit should be available somewhere on the forum. It looks like it lost touch calibration.

f1x said:
Have you tried to reflash the unit? Factory ROM for you unit should be available somewhere on the forum. It looks like it lost touch calibration.
Click to expand...
Click to collapse
I thought that was exactly what happened. I reflashed both ROM and DMCU, but didn't help. The vendor sent my video over to his engineer and they are going to get back with me today. I am thinking its a physically problem with the screen like something worked its way loose or the heat of the day effected it.

System Re-Flash from recovery mode.
I just went into recovery mode and did a full reflash again hoping it gives some information about what is happening. I videoed it, and it will (in about an hour) be available here. https://youtu.be/9Q70WxcMzzg Warning beginning to end its 8:21. May be of use to someone trying to understand how to get into recovery mode and reflash
I went ahead and typed the messages on the screen after selecting "Update system/mcu image from sdcard and clear all" all the text that followed is below. I see an error came up in parsing the backup, not sure if that effects the loading or not, it seems to be running the same
__ Update rkimage...
Installation rkimage start.
Finding update package.
===UPDATE RKIMAGE===
Find and check firmware...
!!! Please KEEP your USB cable or DC-in connected !!!
Check parameter...
Update recovery.img...
Check recovery.img...
Update boot.img...
Check boot.img...
Update misc.img...
Check misc.img...
Update kernel.img...
Check kernel.img...
Update system...
Check system...
Update oem.img...
Check oem.img...
Update backup...
Check backup...
E:1 parse errors
Handle script error! ignore...
Copy Bootloader...
Installation complete.
Update rkimage complete.
Installation rkimage success.
Formatting /data...
Formatting /cache...
Formatting /mnt/internal_sd...
Installation mcuimg start
Installation mcuimg aborted
Installation mcuimg start
-----MCU Version :V1.66a
-----MCU customer : KD
Installation mcuimg success.
System will now power off/
Rebooting...
Click to expand...
Click to collapse

The vendor got with his engineer and is pretty sure it is the touch screen itself that is the issue, not the software (I was thinking the same thing). Their guess is the cable has somehow worked loose and want me to open the unit and check the cable connections. He sent me a photo of what to look for (below). Any recommendations/warnings before taking this thing apart tonight?
Thanks, this thread may be too much me, but if someone else is having the same issues, I want to make sure there is somewhere they can look for troubleshooting and hopefully an eventual solution.
BTW, so far vendor communication has been really good.

Hi, have you been able to fix it? I'm thinking of getting the exact same head unit (as opposed to universal one with all the extras I would need, like fascia, cage, harness)

schriss said:
Hi, have you been able to fix it? I'm thinking of getting the exact same head unit (as opposed to universal one with all the extras I would need, like fascia, cage, harness)
Click to expand...
Click to collapse
Mailed I back, they received today and are returning a new unit. Will update when it arrives
Sent from my iPad using Tapatalk

I got an update from the vendor, and the issue was a touchscreen cable worked loose. Absolutely a problem with the assembly in China, and probably something I could have fixed if I was skilled in electronic repair. My new unit is on the way here.
Sent from my SM-G920I using Tapatalk

I should be getting mine delivered tomorrow, hopefully no loose cables

Are there any benefits buying a eonon unit compared to this one? Are they from the same factory you think? The new eonon has Bluetooth 4 compared to others? How can that be if they are all from the same manufacturer?

I suspect they all come from same factory, Eonon, Joying or no brand - the only difference seems to be the software.
I'm quite happy with my "generic" unit, so far so good. But didn't test bluetooth more than just paired with my phone, no calls yet or any obd2 readers used.
My main use is navigation and that seems fine, but my phone seems to be getting a bit more accurate gps lock according to gps test apps.

PattonD, have you tried a Bluetooth call? How was it? Did you use the internal mic or an external?
One of the most important features for me...
The unit you bought is very interesting.

I got the unit. I tried the unit at home. Internal mic seems fine.
However, how is the reverse camera installed? Is reverse signal coming from the canbus system or must i cut the brown cable (cable 8, back car cable) and connect it to the reverse lights?

it is the plug

I'm not really sure what you mean mate