Related
Hello.
I used the Toolkit to root my Note 2, and I had to use option 4 on the rooting menu, Install Custom Recovery, Install via Recovery to get it to work. I tried several times via the Odin tool and Twrp recovery, and the phone kept booting into Android Recovery instead of Twrp recovery.
I finally used Odin to flash back to stock ROM that I got here, but, along the way, even though the Toolkit was able to connect to my Note 2, I get the Hardware ID missing, and I cannot connect to it any longer like I could after I installed the initial drivers.
Anything I can do and stay rooted?
Change usb ports or restart your device. Mine did it last night and I fixed it by doing both..
I have the same problem.
Changing ports and restarting in most cases didn't help and only in few cases I managed to access files on the phone via USB.
Any other suggestion how to solve this?
don't use windows..
Ditto
dstenc said:
I have the same problem.
Changing ports and restarting in most cases didn't help and only in few cases I managed to access files on the phone via USB.
Any other suggestion how to solve this?
Click to expand...
Click to collapse
glen4cindy said:
Hello.
I used the Toolkit to root my Note 2, and I had to use option 4 on the rooting menu, Install Custom Recovery, Install via Recovery to get it to work. I tried several times via the Odin tool and Twrp recovery, and the phone kept booting into Android Recovery instead of Twrp recovery.
I finally used Odin to flash back to stock ROM that I got here, but, along the way, even though the Toolkit was able to connect to my Note 2, I get the Hardware ID missing, and I cannot connect to it any longer like I could after I installed the initial drivers.
Anything I can do and stay rooted?
Click to expand...
Click to collapse
I was able to gain root back using the toolkit. I flashed stock rom image I believe the ROM from the factory then flashed back stock recovery. Went back in after I updated and re-rooted to flash the triangle away. Now I need to unroot and after speaking with Sprint Rep on phone and trying a few things they advised me to take it to store to let them try it. I believe ALL of my problems started when I tried to use Mobile Odin Pro to flash the latest update to LJC (should I have been on stock recovery?). It started to flash then stopped and went into CWM recovery which is the recovery that the toolkit flashed. I for some strange reason was going to flash the update from there except I didn't have it in the right place on my sd card (couldn't access it GOD I'm a Dumbass!). God help me cause I'm too stupid to even understand what side loading is let alone how to do it. If some kind soul would take pity on me and pm me I could get a handle on the differences between HTC and Samsung. Anyway need to unroot now. Oh I keep seeing in the flash counter saying 1 but I'm on stock rom with stock kernel and stock recovery how do I get it to zero. Using triangle away. Anyway to check counter with stock recovery?
OH yeah does anyone keep getting "Internal Error Code 1500" in addition to the hardware id is missing?
Thanks to everyone that takes time to help idiots like me. I promise I CAN learn.
Charles
chrisc627 said:
Change usb ports or restart your device. Mine did it last night and I fixed it by doing both..
Click to expand...
Click to collapse
Thank you...Unlike user: dstenc, the above procedure fixed my issue. As has been the case many times, XDA helpful users to the rescue!
:laugh: :good:
Just to report that for now I've found woraround. I've installed old drivers 1.4.103.0 and now both Kies and file access works.
Still looking for final solution with latest drivers.
Could you walk me through your fix?
dstenc said:
Just to report that for now I've found woraround. I've installed old drivers 1.4.103.0 and now both Kies and file access works.
Still looking for final solution with latest drivers.
Click to expand...
Click to collapse
Hi dstenc,
Would you be so kind as too help me do what you did? I don't have kies on my pc, did you get the old drivers from the s3 forum? I would love to give it a shot.
Thanks for any help
Charles
Could you walk me through your fix?
Mods please delete double post sorry
ceabbott2 said:
Hi dstenc,
Would you be so kind as too help me do what you did? I don't have kies on my pc, did you get the old drivers from the s3 forum? I would love to give it a shot.
Thanks for any help
Charles
Click to expand...
Click to collapse
I don't remember link. I googled so you might try that way.
Just FYI, even with older drivers I have sporadic Hardware ID Missing error, but far too less than with the latest version.
I'm posting this to keep it to the top of this board.
This is my second Note 2 in 2 weeks. I returned the first one because it stated Hardware ID missing, so within my first 2 weeks Sprint gave me a new one thinking that it was my phone. While at the Sprint store, and not yet rooted, we installed the unit and removed the unit 15 times to see if we could get it to have the Missing Hardware ID to pop up, it DIDN'T pop up once, so I thought I was good to go.
I came home and did the common root method that uses Galaxy Note 2 Toolbox. I IMMEDIATELY started getting the Missing Hardware ID again.
So now that we have it localized, what could be missing or creating a problem from the root procedure from the Galaxy Note Toolbox 2???
What I find really strange is that many are not experiencing this problem or they are just living with it.
I even tried the USB Switcher that appeared to install and does switch between Mass Storage and MTP, but although my PC makes the upward noise that sounds like it is installing and recognizing the USB Mass Storage, it doesn't end up recognizing it. It was ZATTA's build but he said it didn't work for his Galaxy 3 or Note 2 either.
Will anyone find a cure????
This will be no fun to have to deal with for the next 2 years.
Chime in PLEASE!!!!!! Even if it's only to insult me, I don't care if you have a cure.
Regards
Dave
if you do Google search, it's a known issue. From what I read, it's a driver issue. Some have had luck using the older Samsung USB drivers. You have downloand them, and install, and have your PC completely disconnected from the internet before plugging in your GN2 after the install. Appaarently the drivers on Microsoft's servers are bad; may be the wrong device.
I've done this, and still have the issue. I just find I don't have plug and unplug the USB cable as much.
What I have seen, the PC does connect to the GN2. It just doesn't recognize it as a storage device. It wants to use it as a modem, probably from the tethering capabilities with a USB OTG cable.
It may not be so much that it's not wide spread, but more that not everyone uses the GN2 as storage device or connects it their PC.
I dont think this is all due to Windows issue. This is what i notice before and after root.
If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.
If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.
If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.
How i notice this, i have root/unroot my device like 20 times since i got my device.
The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.
Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.
knightfox said:
I dont think this is all due to Windows issue. This is what i notice before and after root.
If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.
If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.
If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.
How i notice this, i have root/unroot my device like 20 times since i got my device.
The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.
Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.
Click to expand...
Click to collapse
Yep I think you may be on to something. Because when I rooted I tried both TWRP and CWM and then I had to go back to stock to get to apply the LJC update. Ever since I have had the chameleon error and Handsfree activation issues. Oh my counter always says 1 and I can't remove it with triangle away. I think it says custom binary yes and the counter says 1. I am using a laptop with Windows 7 and it now recognizes the device just can't stop the errors on start up.
Charles
Sent from my SPH-L900 using xda premium
Samsungs older drivers: uploaded.net/file/hdh0f1xd
Hey Everyone
I've been looking around the site (and the rest of the web for that matter) and I can't find much on this that's helpful (at least not anymore).
I used to flash custom shizz on my phone regularly until I flashed back to stock for a while, and now I've decided to go back. The problem is, my USB port broke in the mean-time and I can no longer plug it in I know I could buy a new USB port, but it's a lot of work for a phone that I'm only going to be using for a couple more months (will be upgrading to the S5)
Is anyone aware of a way to root on the phone itself? So far I've tried http://forum.xda-developers.com/showthread.php?t=2352669 and Framaroot to no avail - I can't find anything else.
Any help would be massively appreciated.
Thanks!
Hey xda!
I rooted my phone 2-3 months ago, and regretted every day since!
I tried the guide on the forum, but i may have done something wrong.
Because it is still rooted, not with SuperSU, tho with TWRP.
Its not that the fact that my phone is rooted irritates me, its more that, i cannot update from kitkat 4.4.2 to kitkat 4.4.4.
and my Phonenetwork Signal & 3g/4g network connection is lost every 20-30 minutes.
When i am trying to Unroot, it is necessary to find my model number with the CMD. This worked for me the first time, but at that time, i couldnt find the right stock recovery backup. But now i cannot even see which model i have, because my device is never found using the developer kit tool.
I dont know how to do it, and i am very sad that i spent so many money on such a good phone, and then i "corrupted" it.
I dont know if somebody has an Easy Fix for me. i dont think so.
But if somebody knows how to do this, i would happily send it to the person who have courage to try Unroot my phone!
I will pay a fair wage for the process. Tho, HTC repair center offered me to change my internal storage and motherboard for bout 200euros.
I hope there is a superHero out there! :good::good::good:
best regards
szEIgo
First off, your understanding of what root does and means seems shaky at best. Root is just a permission change. Nothing more, nothing less. Root does not affect signal strength. Something else is going on there, that has nothing to do with root. Updating the phone might help, might not. I don't expect a drastic change in signal issues from OTA updates.
Root will also not effect the USB connectivity to your computer. This may be due to USB ports or cables; or very frequently just an issue with drivers. It too has nothing to do with being rooted.
Root in itself will not prevent OTA, although having custom recovery installed and/or any system files altered by root will prevent OTA from installing. But neither will prevent OTA notification and download from occurring. The more pressing issue, is that if you did not receive and/or able to install the 4.4.3 OTA, you won't received the 4.4.4 OTA either, as they need to be installed in sequence.
My advice is to troubleshoot the USB connectivity issue. Once you have that figured out, get CID and restore the stock nandroid and recovery. This will hopefully force the 4.4.3 OTA, then the 4.4.4 OTA.
Ty for your reply - but its not exactly what i meant in all ways.
Its not that the USB connectivity isnt working.
My pc can transfer, edit and read files from and to the HTC phone.
Its just that it cant seem to find the CID, because i did something wrong in the unrooting process.
I dont know much about all of this rooting, as you said.
Tho, I did not have any problems about my phones network connectivity, until i rooted my phone!
Im almost hundred procent sure, that this is some kind of software bug, because it has perfectly signal strength everywhere, its just that, some settings, makes it reset my phones 3g and network connection every 20 minutes or so.
Its like its going on airplane-mode, and then shortly comes back to normal.
to begin i thought i made some stupid settings on it, but then i looked all settings on the phone thru, 600 times, and couldnt find nothing!
Thank you for your reply.
I hope somebody is familiar with both of my problems:
1. cant find CID, because im stuck on some step of the unrooting process.
2. Resetting my network settings automatically every 20 minutes or so. (in short)
szEIgo said:
Its not that the USB connectivity isnt working.
My pc can transfer, edit and read files from and to the HTC phone.
Click to expand...
Click to collapse
That doesn't prove anything. You can have MTP connectivity (internal storage access) but broken fastboot and/or adb connectivity. I've seen this many times here before.
adb/fastboot not finding the device is almost always a matter of connectivity (usually a driver issue).
If you have HTC Sync and/or HTC drivers installed, try to uninstall them and see if this fixes adb/fastboot connectivity.
szEIgo said:
I dont know much about all of this rooting, as you said.
Tho, I did not have any problems about my phones network connectivity, until i rooted my phone!
Click to expand...
Click to collapse
Rooting doesn't affect the phone's performance or signal. Period.
If its a software bug, it must be due to some mod your applied, or some app you installed. I assume you must have applied some mods, or using a root app, otherwise why did you root?
And are you sure it isn't just a carrier network issue?
Z1 Compact 5.1.1: Replaced KingRoot with SuperSU, then endless Sony Logos & Reboots
Got a pair of refurb Z1c D5503s, and updated both to 14.16.A.1.216-R3D (Android 5.1.1) using the Sony Companion.
Both phones show "bootloader unlocked", so I did a successful root of one of the phones, using KingRoot.
Then I attempted (and failed) to use Replace_Kinguser_with_SuperSU v 1.2 , which grabbed its own update to 2.4 when started.
While the SuperSU claimed to have replaced Kinguser sucessfully, upon reboot, the phone began an endless loop of reboots, never making it past the Sony Logo.
I was able to stumble through recovering from the TA partition using flashtool, so now I am back where I started, with Sony stock 14.6.A.1.216
The tutorials I can find are very outdated versus the software packages themselves. For example, I still have no idea where the "/drivers" directory might be for flashtool, or why the new version hides the directory in ".flashtool".
But I'd like to root the phone, so as to not just disable, but to remove the bloatware from the minimal internal memory, and I'd also like to root the phone to be able to take full advantage of the micro-SD card for data and apps.
But what to replace Kingroot Kinguser with once it is rooted, and/or how to do so without crashing the phone on reboot so badly?
Sorry to be so clueless... these "new" phones are our (myself and my wife's) upgrade from a pair of Samsung Exhibit IIs, just to show you how out-of-date I am on rooting phones. (^.^)
Thanks!
packetfire said:
Got a pair of refurb Z1c D5503s, and updated both to 14.16.A.1.216-R3D (Android 5.1.1) using the Sony Companion.
Both phones show "bootloader unlocked", so I did a successful root of one of the phones, using KingRoot.
Then I attempted (and failed) to use Replace_Kinguser_with_SuperSU v 1.2 , which grabbed its own update to 2.4 when started.
While the SuperSU claimed to have replaced Kinguser sucessfully, upon reboot, the phone began an endless loop of reboots, never making it past the Sony Logo.
I was able to stumble through recovering from the TA partition using flashtool, so now I am back where I started, with Sony stock 14.6.A.1.216
The tutorials I can find are very outdated versus the software packages themselves. For example, I still have no idea where the "/drivers" directory might be for flashtool, or why the new version hides the directory in ".flashtool".
But I'd like to root the phone, so as to not just disable, but to remove the bloatware from the minimal internal memory, and I'd also like to root the phone to be able to take full advantage of the micro-SD card for data and apps.
But what to replace Kingroot Kinguser with once it is rooted, and/or how to do so without crashing the phone on reboot so badly?
Sorry to be so clueless... these "new" phones are our (myself and my wife's) upgrade from a pair of Samsung Exhibit IIs, just to show you how out-of-date I am on rooting phones. (^.^)
Thanks!
Click to expand...
Click to collapse
Use SupetsuMe from Playstore.
Best regards,
Coempi
packetfire said:
Got a pair of refurb Z1c D5503s, and updated both to 14.16.A.1.216-R3D (Android 5.1.1) using the Sony Companion.
Both phones show "bootloader unlocked", so I did a successful root of one of the phones, using KingRoot.
Then I attempted (and failed) to use Replace_Kinguser_with_SuperSU v 1.2 , which grabbed its own update to 2.4 when started.
While the SuperSU claimed to have replaced Kinguser sucessfully, upon reboot, the phone began an endless loop of reboots, never making it past the Sony Logo.
I was able to stumble through recovering from the TA partition using flashtool, so now I am back where I started, with Sony stock 14.6.A.1.216
The tutorials I can find are very outdated versus the software packages themselves. For example, I still have no idea where the "/drivers" directory might be for flashtool, or why the new version hides the directory in ".flashtool".
But I'd like to root the phone, so as to not just disable, but to remove the bloatware from the minimal internal memory, and I'd also like to root the phone to be able to take full advantage of the micro-SD card for data and apps.
But what to replace Kingroot Kinguser with once it is rooted, and/or how to do so without crashing the phone on reboot so badly?
Sorry to be so clueless... these "new" phones are our (myself and my wife's) upgrade from a pair of Samsung Exhibit IIs, just to show you how out-of-date I am on rooting phones. (^.^)
Thanks!
Click to expand...
Click to collapse
Did the suggestion work for you?
levone1 said:
Did the suggestion work for you?
Click to expand...
Click to collapse
In a way, yes, but now I have a phone without the KingRoot bloatware/possible malware, but where the USB connection to my PC cycles between "up" and "down" more than once every minute, leaving me thinking that the Super SUme program itself is the source of the problem for my phone.
I have no idea how to debug this issue, other than to start all over again, and verify that the problem only shows up after the Super SUme scripts run.
This is starting to be a lot of work for a phone.
packetfire said:
In a way, yes, but now I have a phone without the KingRoot bloatware/possible malware, but where the USB connection to my PC cycles between "up" and "down" more than once every minute, leaving me thinking that the Super SUme program itself is the source of the problem for my phone.
I have no idea how to debug this issue, other than to start all over again, and verify that the problem only shows up after the Super SUme scripts run.
This is starting to be a lot of work for a phone.
Click to expand...
Click to collapse
Flashtool is the way to go. Did you figure out the directories yet? There is a /Flashtool folder and a /.flashtool folder. The drivers are in /Flashtool. With Ft working, you can get it done easier, but it will take a little work.
levone1 said:
Flashtool is the way to go. Did you figure out the directories yet? There is a /Flashtool folder and a /.flashtool folder. The drivers are in /Flashtool. With Ft working, you can get it done easier, but it will take a little work.
Click to expand...
Click to collapse
Flashtool is no problem, but I was unable to find an up-to-date guide on using it, and some of the instructions are no longer applicable to the current version, so I did not want to brick the phone making a classic noobie mistake.
I will start over after I make contact with the Super SUme fellow, as perhaps he has a suggestion that can help.
packetfire said:
Flashtool is no problem, but I was unable to find an up-to-date guide on using it, and some of the instructions are no longer applicable to the current version, so I did not want to brick the phone making a classic noobie mistake.
I will start over after I make contact with the Super SUme fellow, as perhaps he has a suggestion that can help.
Click to expand...
Click to collapse
K... Let me know if you want links, etc. I don't mind.
levone1 said:
K... Let me know if you want links, etc. I don't mind.
Click to expand...
Click to collapse
Thanks for your kindness... my problem is clearly that I do not know how to install Super-SU and remove Kingroot manually, and the Super-SUme script seems to do some sort of damage to phone-side USB functionality in the specific case of a Sony Z1 compact running Android 5.1.1 before being rooted. (Saying this clearly so the next guy can find this with a search)
So, is there a set of instructions that allows one to do by hand what is done by Super-SUme? I'm sorry to be so clueless, but it has been several years since I unlocked a pair of phones for my wife and I, and in that time, Android has gone from 3.x to 5.x.
Kingroot can be copied over to the root directory of the 5.1.1 phone, and it runs without problem, so then the problem may be a result of the work done by the Kingroot developers to maintain a toehold on each smartphone their tools root.
=-=-=-= Warning, Opinion Follows, Use At Your Own Risk =-=-=-=-=
There is a disturbing/amusing post here on xda from the Kingroot guys that describes the various tools that remove their software as "malware". The loss of perspective that the use of such a term evinces is troubling. Or maybe revealing of the actual motivation of the Kingroot guys. [I dunno, I'm so old-skool, I designed computers that used "ECL", and "bit-slice ALUs", and none of them was smaller than three refrigerators, not counting optional STC vacuum-column 6250bpi reel-to-reel tape drives. Shoot, that was so long ago, we did not even buy any "ones", we'd have a guy come in 3 days a week to cut zeros in half, and bang them flat to hand-craft the "ones" for us so we we'd have both ones and zeroes! (^.^) ]
One would expect that the Kingroot fellows, being in the unlocking biz, would figure out for themselves that if they made the same error as the phone vendors, and made anything extraneous "irremovable", that they would need a stopwatch to measure they very short time lag before someone came out with a countermeasure to remove the extraneous stuff they installed when unlocking to allow the removal of vendor extraneous stuff. If their "purify" tool is any good, people will seek it out and use it, and some will pay for a "pro" version. If it is not any good, people will remove it, no matter how they try to make it impossible to do so.
The fact that I paid $3.99 to the Super-SUme guy to sell me code to remove Kingroot and Purify easily should be a lesson to the Kingroot guys. The fact that the tool failed to do the job properly and screwed up my phone is beside the point. The point here is that the Kingroot guys have not built confidence in their integrity, and the fact that they tried to "bundle" extraneous irremovable stuff with their root exploit and made their root exploit hard to remove/replace positions THEIR OWN product as the "Malware" and the Super-SUme product as "Malware Removal".
I don't care if the download is 100 Gig, if he Kingroot guys distributed a package that did not have to "phone home", and could be installed on a phone with no SIM card installed, and no WiFi, and if the resulting rooted system did not try to "phone home to Shenzhen", and could be easily modified as the user saw fit, including removing the whole mess and replacing it with Super-SU, I don't think anyone would have any problem with paying the $3.99 (or even $9.99!) to the Kingroot guys directly, rather than to Google Play Store, so that the Super-SUme guy gets $1 or whatever.
But clearly, there are some who think that money is not what the Kingroot guys are after. And that's the scary part.
packetfire said:
So, is there a set of instructions that allows one to do by hand what is done by Super-SUme?
Click to expand...
Click to collapse
Here is my thread on doing it yourself from scratch - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-stock-5-1-ub-t3203247 I'm not an expert, so I have confidence to say that it is not hard to do. The biggest part is downloading all of the files. I can also guarantee it working on the last 3 fw updates, since I've done it. It is a bit of work and time, though. If you have working adb and Ft, you're good to go.
levone1 said:
Here is my thread on doing it yourself from scratch - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-stock-5-1-ub-t3203247
Click to expand...
Click to collapse
Danke! Worked great, unlike the $3.99 app which if removed/refunded and then reinstalled to verify a good install, no longer allows one to return and refund the purchase!
Anyway, now I am using the rooted status of the phones to remove unwanted bloatware by hand.
THANKS!!!
packetfire said:
Danke! Worked great, unlike the $3.99 app which if removed/refunded and then reinstalled to verify a good install, no longer allows one to return and refund the purchase!
Anyway, now I am using the rooted status of the phones to remove unwanted bloatware by hand.
THANKS!!!
Click to expand...
Click to collapse
No problem. Did you go ahead and flash NUT's dual recovery? Recommended to accompany this method, since by default you won't have busybox or r/w access.
Hey guys,
sorry if my english isn't right but I am so tired so now and so frustrated that I don't know what I could do.
The story is simple: I have a android head unit, running allwinner t3 (aka R40) with stock rom and stock recovery.
So far, there isn't any custom recovery available (I would like to create/compile CWM but CWM-Builder have some 502 Bad Gateways...) and the only way to root on 4.4.2 is with 360Root (On 6.0.1 for the newer Models only with Kingroot).
So far not bad but it takes a lot of patience sometimes and sometimes you can try over 1 week every day many hours and it still don't work!
So where do I need help? I want to add Root/SuperSU/... manually but I have many limitation.
First one is that I can only modify the system.img without any chmod and else (Maybe because I am using windows? Maybe because the Firmware has to be flashed while the Head Unit is powered off aka "Dead flash")
Secondly, ADB is not working, to be honest, the head unit act only as a receiver! It accepts any devices like Keyboard, UMTS/WCDMA Stick, USB Stick, ... but MTP fom HeadUnit or ADB, ... don't work. The only way for ADB is ADB over Wifi but I don't know whether it's good or bad. I saw that the USB is plugged into a slot which seems to be bend out, maybe they plugged it in wrong? I don't know how I can test that but I heard that connecting two devices with wrong polarity will break at least one of them!
Thirdly is, that I can't notice a difference between a rooted stock rom and a unrooted stock rom.
According to WinMerge, the rooted ROM have two new files (/etc/install-recovery.sh and /bin/su) but that's it!
If I transfer those files to my custom ROM with the same rooting app, it wont recognize them! I can try and try until I die.
And last, maybe worst, I can't just update something over. Every change outside the Android OS is mainly done by flashing the whole firmware! They changed that policy a little bit after Android 6.0.1 but this Android have the worst stability, worst GPS Modules and completely bricked Bluetooth! Also the stock recovery on 4.4.2 is useless, touch isn't working and the touch-buttons are also not working. I also tried to use a usb keyboard but also useless. Only the 6.0.1 stock recovery recognizes the touch screen and the touch-buttons but as I said, the Android 6 is terribly made...
I know what it sound like a noob and I didn't provided much information but I want to know whether someone can help me or want to help me... maybe someone say that I have to provide information xyz so yeah, feel free to ask
Best regards
Pascal
At what point did you install the ADB device drivers (kinda important) for your device, so that when you plugged it into anything, the thing could register you were plugging in the HeadUnit......