Related
Most of you know how to enter the "normal" SPL bootloader where the famous tri-color screen is shown on the device display: if the device is powered off you press and hold the camera button and then press power on.
What most of you don't know is that there is also a radio bootloader aka OEMSBL. The OEMSBL is loaded just before the SPL. Just like the SPL it supports a interactive command mode with various commands. The command set available depends on the security state of your device. The most interesting command available in both states is "radata" which is normally used to flash a new radio rom. Perhaps it can be used for unbricking purposes. I will continue to research this.
Another nice command is "setboot". If for example after flashing Polaris radio roms you can't enter the normal SPL bootloader then try to enter the OEMSBL bootloader and enter "setboot 1", this will force the next boot into tri-color bootloader. To reset it you need to enter "setboot 0". NetrunnerAT this may be useful to you
(EDIT: unfortunately to enter radio bootloader by keypressing only works on security unlocked devices)
To enter radiobootloader mode:
if the device is powered off you press and hold the camera button *and* the send button and then press power on.
If it is the first time you enter this mode Windows will prompy you to install 3 drivers: a modem and 2 COM ports (diagnostics and NMEA). Use the attched drivers from the Motorola Q (it also has a qualcomm MSM7200 chipset). Look in device manager on which COM port the diagnostics port driver sits (usually COM4 or COM5). Then start MTTY and connect to that COM port. The commands you type are not echoed on your PC screen.
On a standard device (not security unlocked) following commands are supported:
Code:
radata
powerdown
setboot
GO2AMSS
rseed
pmic_vib_off
pmic_vreg
pmic_level
pmic_vib_on
rpass
On a security unlocked device (see here) there is much more:
Code:
For a help screen, use command ? or h
Available monitor commands are:
? [command]
h [command]
mb [StartAddr [Count [Filler]]]
mh [StartAddr [Count [Filler]]]
mw [StartAddr [Count [Filler]]]
setboot [0/1/2/3]
setatcmd [0:SIO/1:UART/2:USB/3:DPRAM]
setsmdloop [0:disable/1:enable]
setmpatch [0x1: CPU Freq/0x2: acoustic/0x4: simdoor/0x8: RTC]
setiot [0:Disable/1:Enable]
eraseall [erase all setting flags]
setdiag [0:USB/1:UART/2:DPRAM/3:SIO]
partition
checksum
format
setinfo
readadc
cego
setgpio
getgpio
gpio
version
powerdown
platformid
radata
showexplog [n]
usbdppulldown [n]
usbdmpulldown [n]
usbdppullup [n]
usbdmpullup [n]
Headsetpullhigh [n]
rfid
wpmic [PM_VREG] [0/1]
Where do you get the time to sleep?
I can't seem to get in either the normal bootloader nor the radio bootloader.
Holding the camera button while turning it on; nothing happens, it just boots as normal...
Is it me, or...?
Madman_nl said:
I can't seem to get in either the normal bootloader nor the radio bootloader.
Holding the camera button while turning it on; nothing happens, it just boots as normal...
Is it me, or...?
Click to expand...
Click to collapse
What HTC Nike you have? Is it a OEM like Amazon sells? What Roms have you flash before? What Device, Radio and OS Versions you have?
Only modelnumber i can find; NIKI200, not sure if that's what you mean, i bought it last thursday at a T-Mobile shop.
Haven't flashed anything yet
ROM version: 1.35.114.07
Radioversion: 1.58.16.27
OS; wm6, CE-controlsystem 5.2.1622 build 18128.0.4.4
I'm kinda new at this stuff, hope this is the info you need.
Thnx
Yes i think too ... i have the same Problem! Sorry for using German ... but i think this error is importent to fix for other Guys!!!
Sodala!
Ich hab den selben fehler! Möglich, das HTC ein neuen Security trick verwendet und ein gemoddeds OEMSPL etc verwendet! Da dein Gerät noch nie geflashed worden ist, kann man sozusagen ausgehen, dass dieser Fehler nicht von ein schlecht gemoddedn Radio ROM oder SPL kommt! Das ist für mich ein wichtige Info!!
Jetzt ein paar tips damits du kein Problem hast und nicht in diverse fallen tapst!!
Wennst du Flashst ... verwend bitte kein Vista!
Wennst du Flashst ... verwend nur das HardSPL und mach bitte keine Experimente rund ums SPL!!!
Wennst einmal im Bootloader fest hängst ... das Tool MTTY suchen dich via USB auf den Nike hin verbinden und den Befehl "boot" starten! Dann solltest du wieder im OS sein.
Wennst in den Bootloader kommen willst musst du diese Datei auf dein Nike starten!
Du kannst ohne Probleme nach dem HardSPL 1.16 ein unbranded Deutsches Rom von mir Installieren. Mach derzeit keine Radio Roms Updates, da unter umständen du den Bootloader Modus brauchst, ihn aber nicht erreichen kannst! Das ist der einzige Grund warumst derzeit nix in diese richtung machen solltest!
I will talk with jockyw or other guru too found some solution ... this is a new Problem!!
ok, i figured something out;
in another attempt to get into the bootloader, i pulled out my sim as well as the micro-SD, pressed and held the photo button, an turned it on.
the result; a 4 colored screen, from top to bottem; red, green, blue and white, the first three colors getting darker further down.
in the red surface, yellow letters say;
NIKI200
SPL-1.16.0000
CPLD-4
in the white surface it says;
Serial
now i've put my sim and SD back it, all of a sudden, this same trick now also works.
another thing; when i get this screen, it doesn't respond to any of the buttons on the phone.
does this mean anything to anyone?
no button work ... its normal ...
Entered the OemSbl
i could enter the OemSbl
version output:
Code:
OEMSBL VERSION: 1.58.21
OEMSBL Build Date: Dec 20 2007 12:11:48
PLATFORM: NIKE
PID: 30
PLATFORM ID: 4
isn't there a way to flash an SPL by using the RADATA command line, in an unlocked PDA?
...
why u want to do this?
Very Good!
Valvarin said:
why u want to do this?
Click to expand...
Click to collapse
Because my pda is stucked into OEMSBL: NO Os, No Radio and NO BOOTLOADER to load
what have you done?
Task a2? Are you shure that all partitions are deleted?
Yes, task 2a
If you look into kaiser,General section you'll find the log of mtty.
I hope all is deleted.
By the way, radata a part, i hope that also QSPT can do something.
Related topics: "Another dead Kaiser?" and "It's the true brick" (Kaiser,General section )
sorry, no links because i'm with mine old hermes
....
a unbricker will come in few days. no other things about this sorry
Valvarin said:
a unbricker will come in few days. no other things about this sorry
Click to expand...
Click to collapse
What time ?
Valvarin said:
a unbricker will come in few days. no other things about this sorry
Click to expand...
Click to collapse
Have u a unbricker?
My htc tytn2 dead or not? will try tonight need help to resolve this?
I install hard spl and unlock my tytn 2(i mean kaiser) then i go to flash full wwe rom after proces complete 100% my phone not boot ,can not go in tri-color bootloader and does not charge or any light ,hard reset also not work. Only i can see when put in usb cable detect in my compiuter data inteface driver i install Drivers MotoQ usb driver my compiuter now detecect qualcom chip and i see now com port 4 and com port 5 im mtty command what command i need first time to use to recover my tytn 2. I mean do i need first to enter setboot 1 and after setboot 0.
Please respond to know and sory for my bad english.
I also have this problem, but I do with my decision "Cruise". if anyone has found a solution please share it.
Thank you!
My wizard doesnt start the OS
when i switch it on, its stops with a black sceen with "Press Send to restore factory default, Other keys to quit" in white
i cant make a hardreset. no button work
how can i repair this?
can i flash the phone?
sry for my bad english...
Mein wizard startet nicht das OS
wenn ich es einschalte bleibt es bei nem schwarzen bildschirm stehen wo "Press Send to restore factory default, Other keys to quit" in weiß steht.
ich kann keinen hardreset machen. kein knopf funktioniert.
ein softreset bringt nichts.
wie kann ich das reparieren?
kann ich das wizard in diesem zustand flashen?
the failures maybe that a Hw problem in the PCB main or Sw issue, for the second try this:
download the wizard love and xtract the nb file
download the soft spl for G4 models
flash with the wizard love flash ( see the readme file for this in the softspl file)
after flash, make a hard reset
search a wm rom (6.1 o 6.5 ) do you prefer and flash it in your wizard again (use the softspl for this like the wizard love)
this method works for me ( in Fw issue only)
Hi,
I am having a slight issue, not sure what is causing it.
Every time I try and flash to 2.1 from my 1.6 device I get this error:
Code:
Please choose:
1.) 32-Bit Windows XP
2.) 64-Bit Windows XP
3.) 32-Bit Windows Vista/7
4.) 64-Bit Windows Vista/7
Please choose: (1-4): 4
please connect Xperia in flash mode.
Press any key to continue . . .
Jan 9, 2011 4:24:17 PM X10flash main
INFO: start
Jan 9, 2011 4:24:18 PM X10flash readReply
INFO: <<< cmd=1,flags=1,length=46
Jan 9, 2011 4:24:22 PM X10flash readReply
INFO: ### read filed : checksum err! FFFFFFFF!=00000000
Jan 9, 2011 4:24:22 PM X10flash testPluged
INFO: <<<
Jan 9, 2011 4:24:22 PM X10flash writeCmd
INFO: write(cmd=1) (finish)
Exception in thread "main" java.lang.NullPointerException
at java.lang.String.<init>(Unknown Source)
at X10flash.testCmd01(X10flash.java:142)
at X10flash.run(X10flash.java:380)
at X10flash.main(X10flash.java:421)
Press any key to continue . . .
Does anyone know a fix for this?
Also - I've noticed that the solid green light seems to disappear and the phone will just boot up normally after 10 seconds
Thanks,
Vijay Pather
What happened to your other thread? And please don't start new threads about the same thing, and issues like this have been answered a thousand times, it's actually on the first page of the first link I gave you what to try if you have this issue, so browse the threads I suggested yesterday on your other thread.
Vijay Pather said:
Hi,
I am having a slight issue, not sure what is causing it.
Every time I try and flash to 2.1 from my 1.6 device I get this error:
Code:
Please choose:
1.) 32-Bit Windows XP
2.) 64-Bit Windows XP
3.) 32-Bit Windows Vista/7
4.) 64-Bit Windows Vista/7
Please choose: (1-4): 4
please connect Xperia in flash mode.
Press any key to continue . . .
Jan 9, 2011 4:24:17 PM X10flash main
INFO: start
Jan 9, 2011 4:24:18 PM X10flash readReply
INFO: <<< cmd=1,flags=1,length=46
Jan 9, 2011 4:24:22 PM X10flash readReply
INFO: ### read filed : checksum err! FFFFFFFF!=00000000
Jan 9, 2011 4:24:22 PM X10flash testPluged
INFO: <<<
Jan 9, 2011 4:24:22 PM X10flash writeCmd
INFO: write(cmd=1) (finish)
Exception in thread "main" java.lang.NullPointerException
at java.lang.String.<init>(Unknown Source)
at X10flash.testCmd01(X10flash.java:142)
at X10flash.run(X10flash.java:380)
at X10flash.main(X10flash.java:421)
Press any key to continue . . .
Does anyone know a fix for this?
Also - I've noticed that the solid green light seems to disappear and the phone will just boot up normally after 10 seconds
Thanks,
Vijay Pather
Click to expand...
Click to collapse
Try switching the usb ports. It usually helps. Btw there is a new method ti root the device that too by a single click method. I'll post the link when I access my comp
Sent from my X10i
XperiaX10iUser said:
What happened to your other thread? And please don't start new threads about the same thing, and issues like this have been answered a thousand times, it's actually on the first page of the first link I gave you what to try if you have this issue, so browse the threads I suggested yesterday on your other thread.
Click to expand...
Click to collapse
Just to rectify this is a separate issue the first thread was help rooting the phone and this is help I need flashing to 2.1 - I followed the advice with the post putting the Device ID into the text file - the issue I am having (I think) is that the Solid Green light seems to disappear after some time.
If anyone can help it would be greatly appreciated.
I was also wondering if there was a way I could flash the phone to 2.1 through the phone using my memory card. As in a way I could root my v1.6 then use some tool to upgrade it seeing as my device keeps dropping out when in flash mode.
Thanks.
LG CSMG Tool v1.0
Query LG CSMG servers based on IMEI to get device specific information and latest firmware link.
Send query based on Phone Model and Region Suffix get additional device info and USB driver link.
Send query based on Phone Model and MSN to get additional device info such as IMEI / ESN etc.
View query response from server in a clean and formatted way with only relevant info included.
View query response from server as original XML text if you want all of the info from a response.
System Requirements:
---------------------------------
Windows XP, Vista, 7 or 8 with .NET Framework v4.0 installed!
Changes / Improvements:
--------------------------------------
LG CSMG Tool v1.0.23
--------------------------
- Added multithreading support to prevent UI from freezing.
LG CSMG Tool v1.0.21
--------------------------
- Added support for MSN query to obtain IMEI / ESN and other useful info.
- Changed UI layout to accommodate more options.
- Added error checking to detect internet connection when submitting query.
- Fixed a few coding and display bugs.
LG CSMG Tool v1.0.13
--------------------------
- Added history support for IMEI query. IMEIs will be saved with AES 128bit encryption to phone.bin and read on startup.
- Added Auto populate Suffix query fields after successful query of IMEI.
- Changed response window to support rich text format.
- Added XML syntax formatting to make XML response easier to read.
- Added support for firmware URL hyperlinks. You can now click them to launch in web browser from within the application.
- Fixed some coding errors and application bugs.
LG CSMG Tool v1.0
----------------------
- Initial Release.
This is only a simple tool for the time being but it has so much potential and will only get better over time!
Enjoy!
Very nice but not bugless. No paste data function.
I have even TOO many csmg pages that you can use, if you are interested contact me.
nice job thx
Sent from my LG-D802 using XDA Premium 4 mobile app
BigBoyPL said:
Very nice but not bugless. No paste data function.
I have even TOO many csmg pages that you can use, if you are interested contact me.
Click to expand...
Click to collapse
Hi you can copy the text in the response window by highlighting it and using ctrl+c to copy it. If you could pm me all the csmg commands you have including the syntax usage that would be great!
Sent from my LG-D802 using Tapatalk
this tool really useful.thank dev
Nice tool but it doesn't really show that much info for Sprint (LGLS980) model
Thx.
Wanted to make myself one but now I don't have to
LG CSMG Tool v1.0.13 has now been released!
Enjoy!
Hello, I have a problem with a partition of the phone ... this tool will reset the partitions as the original? sorry for my english
No this is only for preview your phone suffix, check does update is available and download drivers/manual.
BigBoyPL said:
No this is only for preview your phone suffix, check does update is available and download drivers/manual.
Click to expand...
Click to collapse
Do you like the updated version? I added support to save IMEI so you dont have to type it in everytime!
Could you pm me the rest of those csmg commands please. Dont worry about explanations the links will be fine!
Sent from my LG-D802 using Tapatalk
Not worky by me.
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.
************** Ausnahmetext **************
System.Net.WebException: Die Verbindung mit dem Remoteserver kann nicht hergestellt werden. ---> System.Net.Sockets.SocketException: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 127.0.0.1:9002
bei System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
bei System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- Ende der internen Ausnahmestapelüberwachung ---
bei System.Net.WebClient.OpenRead(Uri address)
bei LG_CSMG_Tool.frmLGCSMGTool.btnQueryIMEI_Click(Object sender, EventArgs e)
bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
bei System.Windows.Forms.Button.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.34011 built by: FX45W81RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll.
----------------------------------------
LG CSMG Tool
Assembly-Version: 1.0.13.0.
Win32-Version: 1.0.13.0.
CodeBase: file:///F:/Software_Tools/Multimedia/Handy/LG%20G2/LG_CSMG_Tool_v1.0.13_Release/LG%20CSMG%20Tool.exe.
----------------------------------------
Microsoft.VisualBasic
Assembly-Version: 10.0.0.0.
Win32-Version: 12.0.20806.33440 built by: FX45W81RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.
----------------------------------------
System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.34003 built by: FX45W81RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Core
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.33440 built by: FX45W81RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.
----------------------------------------
System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.33440 built by: FX45W81RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.33440 built by: FX45W81RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
System.Runtime.Remoting
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.33440 built by: FX45W81RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll.
----------------------------------------
System.Configuration
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.33440 built by: FX45W81RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
----------------------------------------
System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.33440 built by: FX45W81RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
System.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.33440 built by: FX45W81RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.resources.dll.
----------------------------------------
System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.33440 built by: FX45W81RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------
mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.33440 built by: FX45W81RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.
----------------------------------------
************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.
Zum Beispiel:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.
Click to expand...
Click to collapse
Schrotty35 said:
Not worky by me.
Click to expand...
Click to collapse
You have an entry in your Windows/System32/Drivers/etc/hosts file
127.0.0.1 csmg.lgmobile.com
Comment it out or delete it and it should work
Schrotty35 said:
Not worky by me.
Click to expand...
Click to collapse
Check your hosts file in windows. Looks like you have made the csmg server point to your local IP 127.0.0.1
Sent from my LG-D802 using Tapatalk
LG CSMG Tool v1.0.21 has now been released!
Now you can query MSN to obtain IMEI / ESN, Buyer info etc.
Enjoy!
@lyriquidperfection
Hi,
Thank you for a great software
there is a chance you will make a new post for LG G3 even past a link to here?
It will be handy if there's an APK version, but thanks
Sent from my LG-D855 using XDA Free mobile app
csmg.lgmobile.com:9002/csmg/b2c/client/cs_auth_model_check.jsp?esn=353432060603055
<response req_cmd="cs_auth_model_check" status="OK">
<cs_auth_model_check>
<result>OK</result>
<esn>353432060603055</esn>
<model>LGL24</model>
<suffix>AKDIPK</suffix>
<msn>407KPTM060305</msn>
<esn_date>20140712</esn_date>
<sw_version>LGL2410g_00_8</sw_version>
<sw_url>
dl02.gdms.lge.com:5006/dn/downloader.dev?fileKey=PS67622301/BIN_LGL24AT-01-V10g-440-50-OCT-08-2014+0.zip
</sw_url>
</cs_auth_model_check>
</response>
I tried this tool but i get no link,
<esn_date/>
<sw_version/>
<sw_url/>
<sw_locale_url/>
<sw_recommand_uri/>
<app_version/>
<app_url/>
<cs_em_flag>
N
</cs_em_flag>
<cs_em_uri>
N
</cs_em_uri>
<chip_type/>
<prod_type/>
</auth_model_check>
</response>
what could be the problem ?
I'm rooting my smartphone and one step ist to write "fastboot", but my cmd don't recognize it.
auf Deutsch: Der Befehl fastboot ist entweder falsch geschrieben oder konnte nicht gefunden werden.
Why?
If somebody who can help me I'm very pleased.
My English ist horrible, so if you're a german guy, please write in German.
Did you download the Android sdk and then change the path to where the Factbook command is?
zelendel said:
Did you download the Android sdk and then change the path to where the Factbook command is?
Click to expand...
Click to collapse
Is that what you mean?
Hi,
please install this ADB and Fastboot system wide: http://forum.xda-developers.com/showthread.php?p=48915118
After installing, open CMD and type fastboot devices. Send me the output.
German:
Installier das oben genannte Tool. Wähl bei der Installation aber die System weite Installation aus. Dann öffnest du einfach das normale CMD und tippst fastboot devices ein. Dann schreibst du mir hier, was raus kam.
before i see your post i tried some other things... nothing work
Hi,
open CMD:
Windows Button + R
Type CMD
Fastboot devices
damit du mich nicht für komplett bekloppt hältst und nicht das machst, was du mir rätst... schicke ich dir ein paar Screenshots...
ich hab außerdem dies noch versucht
Ok ok.
There is no reason to be messing with ADB installers. They are pointless and cause more issues then not.
Here is all you need to do. Once you have the android SDK installed. Take all the ADB files and the fast boot file from the tools folder and drop them in the windows directory of your phone. Boom instant system wide ADB and fast boot. AS for it not seeing your device. Remove all fastboot ADB drivers, Restart your PC, boot into fast boot, then plug in the device. (make sure it is a USB port that is a direct one. Not one one like on the front of desktops.) Then let windows install the drivers.
If that doesnt work, then open the device manager while it is plugged in and check to make sure the drivers are removed.