Database Users

[GUIDE] Android Sdk with fastboot, adb and usb drivers

!!!THIS IS NOT A ROOTING GUIDE!!!
This pack contains everything you need to connect and use your nexus s on your pc
Will work on XP, Vista, 7
!!!HOWEVER 7 HAS THE BEST SUCCESS!!!
included:
* Fastboot
* ADB
* USB Drivers (32bit and 64bit)
Links:
SDK:
http://www.fileserve.com/file/RZqMfeC (sdk, fastboot, adb)
Mirror:
http://hotfile.com/dl/92897052/df7338b/SDK.rar.html
Direct Link - No wait, ads, popups:
http://mazodude.comze.com/ -down atm (have to reup)
DRIVERS:
http://www.fileserve.com/file/5bgRBX5 (PDAnet x86 and x64 which are the fastboot drivers plus android sdk drivers)
Mirror:
http://hotfile.com/dl/92897696/7ae5290/drivers.rar.html
Direct Link - No wait, ads, popups:
http://mazodude.comze.com/ -down atm (have to reup)
To be able to install drivers you have to have your phone booted into fastboot and connected via usb (Thanks to mmas0n)
How to force drivers to install:
Thanks to gravis86
WARNING: SELECTING THE WRONG DRIVER TO A DEVICE MAY BREAK THINGS...
1. Control Panel > Administrative Tools > Computer Management >Device Manager
2a. NS Right-Click "Android 1.0", and click "Update Driver Software..."
2b. NS4G Right-Click "Nexus s", and click "Update Driver Software..."
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of device drivers on my computer"
5. Click "Have Disk..."
6. Browse to folder containing the driver, then click OK
7. It will show a list of drivers contained in that folder, select the appropriate one, and click next.
8. It might tell you the driver is unsigned / not verified to work / for the wrong device, etc. As long as you are sure it is the correct driver, then install it. Remember, you are smarter than Windows.
How to install ADB and Fastboot:
1. download and place in the root of your C:\ drive
2. extract here (not into a sub folder)
3. now open up control panel
4. find system
5. goto advanced settings
6. goto environmental variables
7. in the box that says "system variables" scroll down to find a variable "Path"
8. highlight it
9. click edit
10. add this to the end
;C:\android\tools
Click to expand...
Click to collapse
yes the ; is needed
11. click ok
Now when you open cmd (command prompt) you can use "adb" or "fastboot" anywhere with out locating the folder first
You should be able to do this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I have helped you please hit the thanks button

I have followed the directions to the letter and when I type fastboot devices it just goes back to command prompt. I tried typing fastboot oem unlock and it just said waiting on device. Adb devices typed produces "list of devices attached" I boot the phone into fastboot mode and and the usb is plugged in but I keep getting the same results. Am I preparing the phone incorrectly?The adb worked with my Vibrant but the fastboot failed there as well. I would greatly appreciate any and all help you may offer. As I am sure you can tell I am another one of those ignorant nubies.LOL

have you installed the usb drivers?
you will have to force them to install

mazodude said:
have you installed the usb drivers?
you will have to force them to install
Click to expand...
Click to collapse
Yes I have. adb works with my Vibrant but fastboot does not and neither one works with the Nexus s. I have read and reread and followed directions but nothing seems to work. Should I be looking to do something on the phone other than booting into fastboot mode? The Nexus S shows fastboot mode at the top of the screen and I have assumed that I just use the computer from there. On my Vibrant booting into recovery does not show anything about fastboot. I really do appreciate your help I am trying very hard to learn quickly so I can be of some help instead of a burden
I don't know how to force them to install. I went in an opened the folder and I assume they were installed. I do have usb debugging enabled
Edit Just copied usb drivers to C:\android and c:\android/tools and still the same results. I have done everything I can think of but i guess I am not getting the drivers installed properly.

to force them, go into control panel-> administrator tools->computer management
then goto device manager in the sidebar.
I cant remember what the device is called but you should know when you find it.
right click and hit update drivers.
hit browse for drivers and find the drivers in C:\android\google-usb_driver
Note: phone has to be in fastboot to be able to install the drivers
edit: I forgot the drivers opps
link:
http://www.fileserve.com/file/ZM9hbvH
edit: this video might help
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/

I just downloaded the drivers and placed them in C:\android and then went into device manager and hit update drivers and then browse for drivers and it said no drivers found. I was in C:\android/google-usb drivers.

have a look in the post above i just posted a link to a vid
edit: are you using 64-bit?

no 32 bit I will look for the video. Thanks so much for your kind and patient help!!!

I think there is a trick in the video to get it to see the device in fastboot
edit: there are some drivers here
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/

there is no video but I did read the directions and I believe I have done all that they state. Should my PC say installing drivers when I plug my phone in? It did and said one driver failed to install.

yea.
If you don't see a video (at the top) disable ad blocking
also the driver that failed try to force it (using previous method)
If anybody could help that would be great, then I will add it to the first post

Followed this guide and unlocked and rooted my friends Nexus S.
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/

@shaolinmastr well that's good to hear

I still have no success installing the drivers. Are you sure that the drivers were in the last zip file? I have gone over and over it for the last 6 hours and am at the same place I started. NO adb and no fastboot on the Nexus S and adb working on Vibrant.but no fastboot . I guess it is time to take the Nexus S back and get a refund. It is not worth the lack of results with so much effort. Thanks for you help.

Save yourselfs the hassle and just install PDAnet and you should get the drivers to work.

I was having this same problem and used pdanet to get the correct nexus s drivers. You can dload pdanet to your PC and just plug your phone in via USB andfollow the directions.

So tmello56, pdanet worked for you?
If so I will extract the drivers and add them to the first post

WARNING: SELECTING THE WRONG DRIVER TO A DEVICE MAY BREAK THINGS...
Sometimes Windows needs to be forced to use a driver that we know works, but Windows thinks doesn't. This is similar to what mazodude posted, but is just a few steps further. To do this:
1. Control Panel > Administrative Tools > Computer Management >Device Manager
2. Right-Click "Unknown Device" or whatever it's called, and click "Update Driver Software..."
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of device drivers on my computer"
5. Click "Have Disk..."
6. Browse to folder containing the driver, then click OK
7. It will show a list of drivers contained in that folder, select the appropriate one, and click next.
8. It might tell you the driver is unsigned / not verified to work / for the wrong device, etc. As long as you are sure it is the correct driver, then install it. Remember, you are smarter than Windows.
9. WIN!!!

@gravis86, very good explination will post in 1st post

Just wanted to post my results...
I was using the correct drivers, but was installing them while the phone was booted and connected. I could use ADB and mount the file system, but could not use fastboot. I then discovered that if I installed the drivers while the phone was booted into the bootloader and connected, it detected the device differently and fastboot worked.
Now rooted + custom recovery. Awesome.

Setting Your Wildfire Free !! (FULL GUIDE)

Please Follow The Following Thread Link, as it has (& will have) new updates:​
http://forum.xda-developers.com/showthread.php?t=1145035​
Wildfire (buzz) S-OFF, ROOTING,
& Flashing CM7 Full Guide​
Disclaimer
I am not responsible if your phone gets bricked, by following the process you are voiding your warranty and significant damage may be caused to your device.
If you are naive enough to screw somewhere, then it is your responsibility.
Software are unpredictable in nature, one may/may not act as predicted especially in case of rooting (personal experience). Hence my friend, treat with ULTRA care.
In short,
I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE​
All procedures were done under WINDOWS 7, 32-bit
(Please Read Through Before Starting Any Process)​
S-OFFing the Device​
Downgrade to HTC Froyo WWE for AlphaRevX (HBOOT 1.01.0001)
It has been confirmed that AlphaRevX tool is not S-OFFing wildfire (buzz) 2.2.1, with HBOOT 1.01.0002!
Therefore, downgrading the HBOOT to 1.01.0001 is must for the meantime, to get an efficient S-OFF.
Lots of people seem to be having issues when trying to downgrade their Wildfire from a carrier-branded version (HBOOT 1.01.0002) to unbranded WWE (HBOOT 1.01.0001).
So, here’s a small package to help you do this.
click here.
Extract this package somewhere you can find it, like your “Desktop” for example.
Step 1: run step1.bat from the package. This will downgrade your MISC partition to allow for the RUU downgrade.
At the end, GoldCardTool will start up, to allow you to create a goldcard which you will need before starting Step 2.
How to deal with Gold-Card Tool:
1. Switch off your phone, remove your microSD card.
2. Insert the microSD card into your card reader, connect it to your computer and format the card to FAT32 file system.
3. Insert the card into your HTC Wildfire and power it on.
4. Make sure USB Debugging is enabled on your phone in Menu > Settings > Applications > Development.
5. Connect the phone to your computer via USB and set the mode to charge only.
6. Launch Gold-Card Tool on your computer and click ‘GetCID’.
7. Copy the CID code from the text box and click the link shown below that text box to open it in your browser window.
8. In the browser window, enter all the details required and submit that form.
9. You should now get an email from PSAS. Open it and download the ‘GoldCard.img’ attachment.
10. Now set your phone’s USB mode to Mass Storage.
11. In Gold-Card Tool, click ‘Refresh’.
12. Select your mounted SD card from the drop-down menu saying “HTC MMC:”
13. Click ‘Load Goldcard.img’ and select the file downloaded in Step 11.
14. Click ‘Patch MMC’ and your Gold Card will be created. You may exit Gold Card Tool once done.
After you've made the goldcard, and patched it, continue with step 2.
• Step 2: run step2.bat from the package. This will downgrade your ROM version to HTC WWE Froyo for Wildfire (unbranded).
If you get a Customer ID error while doing this, your goldcard is not working!
Create a new goldcard and re-run step2.
AlphaRevX​* Steps:
1st You need to get to: alpharev.nl/x/beta/ to download the tool, and to get your “beta key” which you’ll get in a pop-up window in the same download page after you click the download link for (windows version).
The “beta key” is a must; the tool won’t work without it!
You’ll be asked to provide your phone “serial no.”, typically it should be something like HTXXETDXXXXX, and you can get it from:
Settings --> about phone --> phone identity.
Now, do the following:
1. Run latest version of HTC Sync on your PC and connect phone in HTC Sync mode and sync all your files. Remove HTC Sync and not the drivers.
2. Reboot phone.
3. Settings->Applications->Development->Check “USB Debugging”.
4. Run AlphaRevX and connect phone to PC in “Charge Only mode”.
5. AlphaRevX should recognize your phone and show your Device Serial number.
7. Type out the “key” in the AlphaRevX software, keeping in mind the upper and lower case letters and press enter (you can copy / paste the key).
8. AlphaRevX should start doing its job and you’ll get S-OFF in less than 90 seconds.
9. If it takes longer, just wait for the 15 minutes mark, if nothing, then reboot phone and retry.
(Some members got S-OFF after multiple tries)
Rooting the device:
Step 1 - Installing the USB drivers
Download USB drivers (here) and extract them on desktop. Turn off your wildfire and boot into HBOOT by holding the VOLUME DOWN + POWER button. Connect your phone to your PC and it will show "drivers installing" or similar there for Android device. When prompted, install the drivers by going to device manager and browsing to the folder where you extracted the drivers. Once installed, disconnect and reboot your phone normally.
Now you need to install the “Android bootloader interface”.
Connect your HTC wildfire to the PC and it will ask for drivers again, now go to device manager, click on unknown device “other devices”.
Click on update driver -> install from specific location -> No i will choose to install -> choose Android phone and click on “adb interface” -> click next -> when asked to install click on continue anyway, just install them.
Once done you will see your phone recognized as "Android bootloader interface".
Now disconnect your phone and go into:
Settings -> applications - > development - > enable USB Debugging.
Congratulations, the first step is complete.​
N.B:
At that point, I got a real headache trying to fix that driver thing! What happened with me was totally different, the windows (7, 32-bit) didn’t seem to recognize any of these drivers and I was really so desperate, was about to give up the whole thing!
But, I’ve tried something that perfectly worked, and the driver was fixed!
How? Here we go:
If the drivers didn’t work, proceed with Step 2.
While the RUU installation is proceeding it will fix the driver itself, the installation will stop giving you a connection error, don’t panic, just exit, restart your computer (keep your phone connected, DO NOT unplug it), then start the RUU again, it will proceed normally till the end.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2 - Downgrading from Android 2.2.1 Froyo to Android 2.1 Éclair
Download the RUU rom (here) which is an original stock rom. Plug your phone into the PC and set it to "Charge through USB". Double click RUU rom .exe
Follow the on screen instructions and then let it install. Your phone will reboot into stock HTC 2.1
This will be the last time you will be seeing it though.
Step 3 - Gaining root using Unrevoked, get ClockworkMod and set your phone free
Download the test version of unrevoked (here). Let me repeat, DO NOT USE UNREVOKED 3.32 as it will lead to CID errors or to be precise this error
"Validation error, backup CID is missing"
This may be caused as the 3.32 does not support the HBOOT. Hence you need specific test version of Unrevoked 3.2 to do the job. Download it, save it on desktop, and run it. Now connect your phone and the rooting will start. Once done, you will have ClockworkMod recovery installed on your phone.
Reboot your phone now (using the VOLUME UP/DOWN key for navigation and clicking using TRACKBALL, the POWER button takes you back in menus). Once rebooted, you will see the “Superuser” app in your phone and....
congratulations, your phone is successfully rooted.​
Flashing CM-7 ROM (or any other ROM)
Installing CyanogenMod 7 (Android Gingerbread 2.3.3)
Download the CyanogenMod 7 (here) (choose stable mod) for best results and download the latest version.
You will also need Google apps (here)
Place both files on desktop, connect your phone as USB disk-drive and transfer both zip files on SD card. Once done, reboot your phone into ClockworkMod Recovery (booting by holding the VOLUME DOWN + POWER button and clicking on recovery)
Once the device boots into the ClockworkMod Recovery, use the side VOLUME buttons to move around, and either the POWER button or the TRACKBALL to select.
• Select the option to “Wipe data/factory reset”.
• Then select the option to “Wipe cache partition”.
• Select Install zip from SDcard.
• Select Choose zip from SDcard.
• Choose update-cm-7.0.0-buzz-signed.zip & Let it install.
• Once done, Select Install zip from SDcard.
• Select Choose zip from SDcard, choose gapps-gb-20110307-signed.zip
• Once the installation has finished, get back to the main menu by clicking the POWER button and select the “Reboot system now” option.
Congratulations
The HTC Wildfire should now boot into CyanogenMod​
Now all what you need to do is download and install some essential applications which will make your wildfire much more stylish and amazing.
It's my own collection, but these apps have fixed most of my problems with cm7.
Download apps here.
Now, at this point..
I have to thank everyone and all the threads' owners that I've collected and rearranged their work.​
Hope it was useful..
ENJOY.

success
Thanks for a great tutorial
struggled for quite awhile until you posted this
breezed through it
kindest regards
brian
windows 7 64bit

Should add nandroid before flashing a rom. Otherwise great guide! Post this in the development t section!
I will be trying this when I get my sensation!
Sent from my HTC Wildfire using Tapatalk

I followed this tutorial and everything worked just great! Really amazing, thank you
W7x64
HBOOT 1.01.0001

I have hboot 1.01.0002 and AlphaRevX did S-OFFed it. May be you should check for this

voanhduy1512 said:
I have hboot 1.01.0002 and AlphaRevX did S-OFFed it. May be you should check for this
Click to expand...
Click to collapse
I don't really know..
I've tried many times with my own device while I was having 1.01.0002, but never worked, didn't get the S-OFF.
So, I've logged in IRC, chatted with one of AlphaRev team.. He said "the tool is not supporting 1.01.0002 right the moment!".. So, I had to find an alternative.
But really thanks for your concern..
;-)

bt33 said:
Thanks for a great tutorial
struggled for quite awhile until you posted this
breezed through it
kindest regards
brian
windows 7 64bit
Click to expand...
Click to collapse
You are most welcome my bro.
Best Regards.

I've got 1.01.0002 and AlphaRevX clearly supports it, when getting the beta key in the hboot menu its got 1.01.0002. It worked perfectly fine for me.

Good for u then. Didn't work for me.. ;-)
Sent from my HTC Wildfire using XDA App

ReadBack Extractor mtk6260 - firmware backup utility for GT08, DZ09, GV08 and so on..

Link to the latest readback extractor thread
It is applying for mtk6260A watch phones as GT08, DZ09, GV08, T7, Iradish Y6, Q8, F8 and all variations
In short - if you intend to install in your smartwatch new firmwares, mods etc, before to initiate any flashing with the Flash Tool app (pushing that goddamn < Download > button) think twice, 'bove all better DO a backup for the original firmware, why so? because it's containing all original drivers hence you'll be able to recover 100% your watch in case of bricking.
How to:
First you have need of a full dump of your ROM. Assuming that you already got a Flash Tool 5.1308 and drivers, and you were at the point of flashing something (already chose the download agent and scatter file)
for instance let's say you have a DZ09 smartwatch:
1 - press < Readback > in upper menu and so < Add > in the middle menu
2 - click twice on the item appears in the main window, set name as ROM_DZ choose in browser the path and save
3 - set as Physical start address 0x00000000 and as Length 0x01000000 then ok
4 - press < Readback > in the middle menu wait 2 seconds and connect through USB your watch
5 - wait until the upload is complete (big green ring)
Now second stage:
1 - download the app I've built attached here (Readback Extractor mtk6260A 1.0.rar) and unzip it
2 - create a folder where you intend to keep in safe the original firmware and name it for instance DZ09-Orig
3 - do a copy of Readback Extractor mtk6260A 1.0.exe and place it inside the DZ09-Orig folder then click twice on it
4 - press <Load Readback file> and browse after the ROM_DZ file created before with the Flash Tool then open
5 - Wait about two minutes while the app will check bit by bit the integrity of your file
6 - If everything went ok and your file is healthy app will show " health 100% " so you can proceed to next step
7 - Press <Rebuild Firmware> and wait about 5 to 10 minutes (it has a progress counter there)
8 - When will appear the message " - ALL DONE!!!" close app and go back in the DZ09-Orig folder, now you'll find there 5 new files which are the original firmware kit ready to be flashed back in your phone anytime you want
AFTERWARDS READ ME story - Anywhere you search, there is no one to tell you explicitly how to extract from your mtk smartwatch the firmware kit
All says a halfmouth: Do a full < Readback > in Flash Tool, you'll do it being confident that from now on you say goodbye to any risk because you have A BACKUP hence you start flashing new firmwares. And the Big Brick is coming , you smile and get back to your < Readback > backup discovering that, sadly, you have a binary bulk at first sight good for nothing. It cannot be so useless, isn't it? after all it contains full dump of your ROM! I was in exactly the same situation, so 'cause I didn't find any answer I've started reverse engineering . . . and it worked, first I did it manually for guys being in the same situation, 've noticed that is a common issue so I had to choose how to help, simpler but dangerous (for you) way, to create a tutorial <how to> or the hard way (hard for me), to develop an app which will do all "cooking" automatically and I choose the second because in manually way there is a quite big "chance" to mess up with your primary bootloader which could get to a real tragedy - no modem - brickest brick you saw in your entire life

thanks
thank you very much!!! I was searching how to backup my firmware and I found this forum!! Thank you! Thank you! Thank you!

make video pls!!
hello, please make video how you backup dz09 smartwatch original firmware!! PLEASE!! Thank You!!!

flagerchika said:
thank you very much!!! I was searching how to backup my firmware and I found this forum!! Thank you! Thank you! Thank you!
Click to expand...
Click to collapse
Very wise decision to backUP your firmware! Let me know how things goes

gugesha said:
hello, please make video how you backup dz09 smartwatch original firmware!! PLEASE!! Thank You!!!
Click to expand...
Click to collapse
Unfortunately, my time is quite limited,follow the steps in tutorial, if anything is unclear ask here

Thank you Golem_ for this nice tut.
Unfortunately with my GT08 the FlashTool doesn't seem to start the Read Back process. I see the watch in device manager (COM4), installed the MTK VCOM drivers. I can even access the AT interface of the watch (when the watch is powered on).
The steps i tried to perform are..
1) power off the watch
2) start flash tool, start the Read Back
3) connect the watch via usb --> COM4 appears in device manager
4) flash tool detects watch on COM4 port
5) nothing further happens - Read Back won't start (not even after 1 hour of waiting)..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried with FlashTool v5.1308.00.00 and even the latest v5.1524.00 from spflashtool.com. Same result..
any clues?

dominic1134 said:
Thank you Golem_ for this nice tut.
Unfortunately with my GT08 the FlashTool doesn't seem to start the Read Back process. I see the watch in device manager (COM4), installed the MTK VCOM drivers. I can even access the AT interface of the watch (when the watch is powered on).
The steps i tried to perform are..
1) power off the watch
2) start flash tool, start the Read Back
3) connect the watch via usb --> COM4 appears in device manager
4) flash tool detects watch on COM4 port
5) nothing further happens - Read Back won't start (not even after 1 hour of waiting)..
I've tried with FlashTool v5.1308.00.00 and even the latest v5.1524.00 from spflashtool.com. Same result..
any clues?
Click to expand...
Click to collapse
you have to load a scatter file from a compatible firmware (just for initialization, not for flashing)

Golem_ said:
you have to load a scatter file from a compatible firmware (just for initialization, not for flashing)
Click to expand...
Click to collapse
yep, loaded the scatter from the firmware over here http://www.needrom.com/download/gt08-mt6260a-2/

dominic1134 said:
yep, loaded the scatter from the firmware over here http://www.needrom.com/download/gt08-mt6260a-2/
Click to expand...
Click to collapse
still not working? that's weird!

Golem_ said:
still not working? that's weird!
Click to expand...
Click to collapse
yep it is kinda weird...

dominic1134 said:
yep it is kinda weird...
Click to expand...
Click to collapse
Try a RAM test (be aware, only RAM!), who knows, maybe your watch is on 64Mb

Golem_ said:
Try a RAM test (be aware, only RAM!), who knows, maybe your watch is on 64Mb
Click to expand...
Click to collapse
RAM test doesn't start either...
In the developer menu with #993646633# it says [MEM SIZE] 1299684 btw.
I can also set the UART settings, BAUD, etc.

dominic1134 said:
RAM test doesn't start either...
In the developer menu with #993646633# it says [MEM SIZE] 1299684 btw.
I can also set the UART settings, BAUD, etc.
Click to expand...
Click to collapse
Flash tool has to be set on Options / USB Download/Readback and BackUP and Restore on no action

Please does anyone have the stock ROM file for apro q18 smart watch

Unable to carry read back or memory test
Hi Golem,
Firstly please accept my appreciation for your indepth analysis and details that you have been sharing on forum..
I have been scratching since yesterday evening to do readback and install drivers , but am unable to do it succesfully. It I add drivers from device manager and then run the run back I get following error:
FLASHTOOL ERROR : S_BROM_CMD_STARTCMD_FAIL (2005)
[BROM] Can not pass bootrom start commabd! POssibly target power up too earlu.
[HINT]
Can you please help? I am scratching and trying various things - but I guess am missing something on the installation side... Tried installing with different versions including WIN XP Service pack2,3 etc. but no success... Same error when I run Memory test to check if indeed the drivers have installed..

vir25 said:
Hi Golem,
Firstly please accept my appreciation for your indepth analysis and details that you have been sharing on forum..
I have been scratching since yesterday evening to do readback and install drivers , but am unable to do it succesfully. It I add drivers from device manager and then run the run back I get following error:
FLASHTOOL ERROR : S_BROM_CMD_STARTCMD_FAIL (2005)
[BROM] Can not pass bootrom start commabd! POssibly target power up too earlu.
[HINT]
Can you please help? I am scratching and trying various things - but I guess am missing something on the installation side... Tried installing with different versions including WIN XP Service pack2,3 etc. but no success... Same error when I run Memory test to check if indeed the drivers have installed..
Click to expand...
Click to collapse
Most common mistakes are not turning off the watch before connect to usb and connecting at usb before to start a command in flash tool. If these are not the issue then go in options/backup and restore and set on no action
Use your money wisely, DO NOT WASTE IT buying from GEARBEST

Issue not resolved yet...
QUOTE=Golem_;67280709]Most common mistakes are not turning off the watch before connect to usb and connecting at usb before to start a command in flash tool. If these are not the issue then go in options/backup and restore and set on no action
Use your money wisely, DO NOT WASTE IT buying from GEARBEST[/QUOTE]
Thanks buddy.
Removed battery, tried again - changed USB cord - tried in different port - but still gives same error - Also changed setting to no action in Option-> Backup and Restore.... Few observations - on attaching cable the device manager shows device as Mediatek USB Port (Other drivers present being MTK USB PORT, MTK USB Modem Port, MTK USB debug port, USB Modem Driver. All with a COM port assigned. Then it tries to connect and gives this error.
When tried using download with scatter files and Download agent it again gives error - META ERROR - ERROR in BOOTROM COMMUNICATION.
Can you please help - I am thinking some issue with set-up or drivers... Your suggestion? Thanks!
---------- Post added at 09:54 AM ---------- Previous post was at 09:34 AM ----------
vir25 said:
QUOTE=Golem_;67280709]Most common mistakes are not turning off the watch before connect to usb and connecting at usb before to start a command in flash tool. If these are not the issue then go in options/backup and restore and set on no action
Use your money wisely, DO NOT WASTE IT buying from GEARBEST
Click to expand...
Click to collapse
Thanks buddy.
Removed battery, tried again - changed USB cord - tried in different port - but still gives same error - Also changed setting to no action in Option-> Backup and Restore.... Few observations - on attaching cable the device manager shows device as Mediatek USB Port (Other drivers present being MTK USB PORT, MTK USB Modem Port, MTK USB debug port, USB Modem Driver. All with a COM port assigned. Then it tries to connect and gives this error.
When tried using download with scatter files and Download agent it again gives error - META ERROR - ERROR in BOOTROM COMMUNICATION.
Can you please help - I am thinking some issue with set-up or drivers... Your suggestion? Thanks!
[/QUOTE]
Dear Golem - My Skype id is: viral.gosalia, can we skype chat?

vir25 said:
QUOTE=Golem_;67280709]Most common mistakes are not turning off the watch before connect to usb and connecting at usb before to start a command in flash tool. If these are not the issue then go in options/backup and restore and set on no action
Use your money wisely, DO NOT WASTE IT buying from GEARBEST
Click to expand...
Click to collapse
Thanks buddy.
Removed battery, tried again - changed USB cord - tried in different port - but still gives same error - Also changed setting to no action in Option-> Backup and Restore.... Few observations - on attaching cable the device manager shows device as Mediatek USB Port (Other drivers present being MTK USB PORT, MTK USB Modem Port, MTK USB debug port, USB Modem Driver. All with a COM port assigned. Then it tries to connect and gives this error.
When tried using download with scatter files and Download agent it again gives error - META ERROR - ERROR in BOOTROM COMMUNICATION.
Can you please help - I am thinking some issue with set-up or drivers... Your suggestion? Thanks!
---------- Post added at 09:54 AM ---------- Previous post was at 09:34 AM ----------
Thanks buddy.
Removed battery, tried again - changed USB cord - tried in different port - but still gives same error - Also changed setting to no action in Option-> Backup and Restore.... Few observations - on attaching cable the device manager shows device as Mediatek USB Port (Other drivers present being MTK USB PORT, MTK USB Modem Port, MTK USB debug port, USB Modem Driver. All with a COM port assigned. Then it tries to connect and gives this error.
When tried using download with scatter files and Download agent it again gives error - META ERROR - ERROR in BOOTROM COMMUNICATION.
Can you please help - I am thinking some issue with set-up or drivers... Your suggestion? Thanks!
[/QUOTE]
Dear Golem - My Skype id is: can we skype chat?[/QUOTE]
sent you a message in skype
Use your money wisely, DO NOT WASTE IT buying from GEARBEST

flashtool error
i get the same erro annyone pls help

looks like same problem as Dominic, flashtool just sits waiting. Any solutions
Any solutions not already tried, multiple ports, computers, baud rates cables mem test etc.
dominic1134 said:
RAM test doesn't start either...
In the developer menu with #993646633# it says [MEM SIZE] 1299684 btw.
I can also set the UART settings, BAUD, etc.
Click to expand...
Click to collapse

[HOW TO]Guideline / Install MTK drivers / How to Root / Flash a Rom / IMEI Restore

In this Thread i will explain how to set up MTK drivers and Flashtools.
Guideline:
Post #1 : Set up MTK drivers in Windows 8 / 8.1 / 10
Post #2 : Use Flashtools for MTK Devices
Post #3 : How to Root Stock Rom
Post #4 : Windows 10 MTK Drivers installation ( just in case post #1 dont work )
Post #5 : Lost IMEI Backup​
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
How to Install MTK drivers in Windows 8 / 8.1 / 10
what we need:
MTK Vcom Preloader Driver 2.0
Download : https://www.androidfilehost.com/?fid=24438995911977169
First thing we need is to Disable the Signed Driver verification on Windows :
To disable driver signature verification, we’re going to need to get into the Troubleshooting options from the boot manager.
The easiest way to bring this screen up is using this secret trick.
Hold down the SHIFT key while you click Restart.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once your computer has rebooted you will be able to choose the Troubleshoot option.
Then head into Advanced options.
Then Startup Settings.
Since we are modifying boot time configuration settings, you will need to restart your Computer one last time.
After restarting your computer a second time,
choose Disable driver signature enforcement from the list by typing the number 7 on your keyboard.
That’s all there is to it. Your PC will then reboot and you will be able to install unsigned drivers.
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Now its Time to open SP_Driver_v2.0.zip and start the DriverInstall.exe
it will open the install prompt . Press okay and dont change the installation path
Code:
C: // program files / Mediatek / Driver Package
during the installation it will start the verification window security.
Click on Install this driver software anyway
There will be an Error Message . - We Ignore it !
-Now Open your Device Manager and leave it open.
-Power Off your Phone and connect it with your Pc.
-you will see Under ports ( COM & LPT ) a Preloader unknown device
right click on there and click on Driver update/installation.
-Choose manually search for drivers
-Browse to C:// program files / Mediatek / Driver Package and apply.
-If all went good you have successfully installed the MTK Vcom Drivers. :good:
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>​

How to Use Flashtools
i use SP_Flash_Tool_Windows_v5.1520.00.000 and never had a problem with it.
Its for most all MTK Phones and for all Elephone Devices
Download Link: https://www.androidfilehost.com/?fid=24438995911977217
- Extract the Flashtool zip folder to your Desktop
- Click flash_tool.exe to open the Tool
- You will see two "folder buttons" Download agent and Scatter-loading
- Into Download agent place the MTK_AllInOne_DA.bin file .
its in your Flashtools folder
- Into Scatter-loading place the Scatter.txt
All Stock Roms / Custom Recoverys have one Scatter.txt in their Zip files.
- Make sure that every partition is checked
-IMPORTANT NOW, Flashing Part-
-Power Off your Device!
-Press on the Download Button!
-Connect your Device with PC and wait until all is flashed
-you will see a Green Mark when all is done
-Disconnect your Device and press Power button to Reboot.
:fingers-crossed::good::fingers-crossed:
------------------------------------------------------------------------------------------------------------------------------------------------​

How to Root Stock Rom
-If you want to Root your prefered Stock Rom
-Place SuperSU into your Sdcard
-Flash a Custom Recovery with Flashtools and its Scatter.txt
-Hold Vol+ and Power to get into Bootloader Menu
-Navigate with Vol+ and apply Recovery with Vol-
-Flash Supersu.zip
-Reboot
Stock Roms:
Stock ROM Elephone P9000_Android 6.0_20160315 Link: http://bbs.elephone.hk/thread-9967-1-1.html#[email protected]
CWM Recovery:
Link : https://www.androidfilehost.com/?fid=24459283995304518
100% bug free Supersu v.2.46.zip
https://download.chainfire.eu/696/SuperSU/​

Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial
To determine the version of Windows 10 that you have (32 bit or 64 bit):
- Right-click on Start then click on System
- In the System window that opens, in System section, you will find your version of Windows next to System type
To disable Windows 10 64 bit driver signature enforcement:
- On your 64 bit Windows 10 desktop click on Start then on Settings
- Click on Update & security then in the left pane click on Recovery
- Under Advanced startup click on Restart now button
- Click on Troubleshoot then on Advanced options
- Click on Startup Settings then on Restart button
- The computer will restart with the Startup Settings screen
- To disable the driver signature enforcement until next restart press on number key 7 or F7 on your keyboard.
- After restart you can proceed with the unsigned MTK drivers installation for your 64 bit Windows
- After you install the unsigned drivers, to use them again in the future, you have to repeat this procedure
To install the MTK VCOM USB Drivers on 32 & 64 bit Windows 10:
- Download the drivers *.zip archive and extract the folder from inside on to the desktop:
https://www.androidfilehost.com/?fid=24269982087012126
Right-click on Start then click on Device Manager
In the Device Manager Window click on the first item – your computer name
Click on Action then Add legacy hardware
On the Welcome to the Add hardware Wizard window click on Next button
Select Install the hardware that I manually select from a list (Advanced) and then click on Next button
Click on Show All Devices then on Next button
In the Add Hardware window click on Have Disk… button
In the Install From Disk windows click on Browse… button
In the next window – Locate file – browse for the folder that you have extracted on the desktop at the beginning
Select the version of the driver according to your Windows 10 version – x64 for 64 bit and x86 for 32 bit and click Open button
Click the OK button to load the driver
From the list of drivers select MTK USB Port and click on Next button
If a red warning window will open, click on Install this driver software anyway
This action will add the following drivers in to the operating system:
- MediaTek DA USB VCOM Port
- MediaTek PreLoader USB VCOM Port – for transferring the firmware to your device
- MTK USB DEBUG Port
- MTK USB Modem Port
- MTK USB port – for transfering PreLoader to your device (and recovery in case of bad or corrupt firmware)
Now we need to remove the device that we have installed but leave the drivers in the operating system.
To do that, in the Device Manager window we expand Ports (COM & LPT) section
Right-click and click Uninstall on the MTK USB Port
- In the Confirm Device Uninstall window make sure that the box Delete the driver software for this device is empty
- You need to leave the drivers in the operating system and only remove the device that you added
- Click on the OK button to finalise
Now, when you will connect your turned off MTK device to the Windows 10 computer by USB, the device will be recognized either trough a MediaTek Preloader USB VCOM Port interface or as a MTK USB port if it is bricked or it has bad/corrupt firmware. The SP Flash Tool will be able to transfer the firmware to your device trough this interfaces. Make sure you connect the device after you press the Download button in SP Flash Tool, as the communication interface will only be alive for 2 seconds if no data is being sent.
Download SP Flash Tool v3 & v5 – Latest versions:
http://laurentiumihet.ro/technology/download-sp-flash-tool-v3-v5-latest-versions/
TUT found here : http://laurentiumihet.ro/technology...-for-32-64-bit-drivers-installation-tutorial/
cheers​

Lost IMEI Restore
A common problem many face in their phone is loss of IMEI no. This is results in no network detection by your phone. U can come to know you have lost your IMEI by checking Settings->About phone->Phone information. There under IMEI section you won’t be finding your mobile IMEI numbers displayed.
Don’t worry you can restore your IMEI’s. Just follow this guide and you will be able to restore your IMEI. I will split the tutorial into two parts.
BACKING IMEI :
-First step before performing all these things is that your phone should be rooted.
When your phone is in normal state with everything functioning install Root explorer and navigate to the below location
Code:
>ROOT>DATA>NVRAM>MD>NVRAM>NVD_IMEI>MP0B_001
-Now copy this MP0b_001 file to your SD card or PC whichever place you feel the file we be safer.
-Now download MTK Droid tools .
-Now extract the zip file and open the MTK droid tools exe file.
-Now in your phone turn on USB Debugging by going to Settings->About phone-> Developer options and there turn on USB debugging.
-Now connect your phone and MTK droid tools should be able to detect your phone. U should see a window like this appearing after your
phone has been detected.
-Now press the ROOT button present in lower right corner. When it asks Supersu grant in your mobile click allow. After MTK droid gets
access u should see a green colour box appearing in the lower left corner which means u have correctly granted access to MTK droid.
-Now click on the IMEI/Nvram tab. A window should open and click backup NVRAM and MTK droid tools would take a backup of NVram in
its folder.
RESTORING IMEI :
-Now when you lose IMEI first try this method. Now take the MPDB_001 file which you took backup at the first step and navigate through
Root explorer to this location ->ROOT->DATA->NVRAM->MD->NVRAM->NVD_IMEI.
-Now paste that file and replace the one present there. Set the permissions for that file as RWER-ER-E. Now reboot your phone and you
should be able to get your IMEI back.
If you still haven’t got IMEI open MTK droid tools and connect your phone and press ROOT again and give MTK droid tools root access.
-Now click on IMEI/Nvram tab and select Restore option and restore the NVram backup which you took earlier. Now reboot your phone and
you should be able to get your IMEI.
Extreme method :
-After performing all the above if you haven’t still got IMEI. Now switch off your phone and open SP Tools and connect your phone.
Click on format and format your whole phone. ( This wipes whole of the phone including NVram region ).
-Now flash stock ROM through SP Tools and after it completes start up your phone. ( Don’t be surprised. Your IMEI will still be in lost state
only ). Now root your phone.
-After successful rooting now connect your phone to MTK Droid tools and again press ROOT button and grant root access to MTK Droid
tools. Now click on IMEI/NVram tab.
-Now as you see in the image above you can see two boxes IMEI1 and IMEI 2. Now enter your device IMEI numbers manually in those two
boxes.( You can get your IMEI no’s from your phone box ). Now click replace IMEI. Now reboot your phone and you should be definitely able
to get your IMEI restored.
MTK DROID TOOLS LINK : https://www.androidfilehost.com/?fid=24438995911972546
found: http://www.androiddevs.net/restoring-lost-imei-mtk-phone/​

MTK droid tool doesn't recognize my device. I turned on USB debugging and drivers are installed. Can somebody help ?

I'm having same issue here on Win10 installed the drivers etc... using latest SP Tools plug phone in and try and put recovery as a download nothing happens.
EDIT: Nvm got it working realised I was downloading and plugging in the phone in the wrong order.

Windows defender says MTK Vcom Preloader Driver 2.0 has got a trojan: Win32/Spursint.A!cl but i downloaded drivers from http://spflashtool.com/ instead.
False warning?
/#LOUDmouth#

#LOUDmouth# said:
Windows defender says MTK Vcom Preloader Driver 2.0 has got a trojan: Win32/Spursint.A!cl but i downloaded drivers from http://spflashtool.com/ instead.
False warning?
/#LOUDmouth#
Click to expand...
Click to collapse
False positive

kopasz93 said:
MTK droid tool doesn't recognize my device. I turned on USB debugging and drivers are installed. Can somebody help ?
Click to expand...
Click to collapse
I have a solution for restoring IMEI:
In the dialer: *#*#3646633#*#*
OR
download "MTK engineering mode" app and start it
it will open engineering mode:
1/ go to "Connectivity" tab
2/ go to "CDS information"
3/ go to "Radio information"
4/ then select "Phone 1"
5/ At the top there is a command line "AT+" in it
6/ type AT+EGMR=1,7,"your imei number" (for example: AT+EGMR=1,7,"012345678901234")
7/ then hit "Send at command" (if you got error try to put space between "AT" and "+")
8/ go to "Phone 2" and type in the command line: AT+EGMR=1,10,"your imei"
9/ hit "send at command"
10/ restart your phone and it should work
You can check if it changed at Settings -> About Phone -> Status -> IMEI information
If your forgot your original IMEI numbers you can find them on the box of the phone

MTK droid tool recognizes my phone, but do not get the green button so root error. Granted permission in supersu.

If anyone is still struggling (like me) with the error: Initializing scatter file failed. Please check the name of the scatter which you load is legal
i solved by using SP Flash Tool 5.1552.00.000 downloaded from
https://mega.nz/#!ixdnhDLK!oOaAsJrcvJI0vH3fTsUOYjtDxQ_HT61E-_iuo6fTuKk
as specified in elephone forum flashing guide
http://bbs.elephone.hk/thread-1037-1-1.html#.VWgkX_RAU-0

Use latest v5.162 version
Gesendet von meinem P9000 mit Tapatalk

Linux way?
Is there a way to root my brand new P9000 in Linux?

I flashed the linked SuperSU 2.46 with TWRP but when i start the SuperSU App it says that there is no su-file installed - any ideas?

sundawn said:
I flashed the linked SuperSU 2.46 with TWRP but when i start the SuperSU App it says that there is no su-file installed - any ideas?
Click to expand...
Click to collapse
Why on earth are you using such an old version of SuperSU?
You are probably using TWRP 3.0.0 which does not work on newer ROM versions. Try flashing TWRP 3.0.2-1.

Well i used it because it is said to work in this tutorial
The newer one didnt work either, as you said i think its the TWRP 3.0.0
I would like to download this http://www.needrom.com/download/twrp-3-0-2-1-4/
but i dont get any registration mails, tried to register with 2 different emails half an hour ago...
The version here on XDA is said to be only for P9000 Lite.
Edit: Ok got my login by using the forgot password function - the linked TWRP 3.0.2 and installing SuperSU 2.65 works.
Thanks!

also would like to know, can we fastboot the recovery as per all the other android phones i've used? And then custom ROM to our hearts content?

n1ck75 said:
also would like to know, can we fastboot the recovery as per all the other android phones i've used? And then custom ROM to our hearts content?
Click to expand...
Click to collapse
Yes. In Settings / developersettings enable oem. unlock Bootloader.
Then reboot to Recovery and go to power/ reboot to fastboot.
Then Unlock your Bootloader with the fastboot oem Unlock command.
After that you can use fastboot.
P.s: i didnt did that. But it should work
Gesendet von meinem P9000 mit Tapatalk

skeleton1911 said:
Yes. In Settings / developersettings enable oem. unlock Bootloader.
Then reboot to Recovery and go to power/ reboot to fastboot.
Then Unlock your Bootloader with the fastboot oem Unlock command.
After that you can use fastboot.
P.s: i didnt did that. But it should work
Gesendet von meinem P9000 mit Tapatalk
Click to expand...
Click to collapse
Thanks for the prompt reply;
Have got to the fastboot oem unlock part, gives option for
Vol Up - Unlock
Vol Down - Cancel
Vol Up doesn't work? Can only Vol Down

[HOW-TO] Sony MW1 , Sony SBH52 and SBH54 Firmware Downgrade / Firmware Update

This is a Method to update Firmware of Sony MW1 , Sony SBH52 and SBH54. I extract the firmware from the headset apk.
BIG UPDATE
Instructions for Sony MW1:
1. Download the Attachment "Sony MW1 Firmware Tool"
2. Reset your Device via Settings/Systeminfo/Reset
3. Power off your Sony MW1, press "back-button" and connect in the same moment your device to the usb port of your computer.
Now you should see this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Now open the program "zadig.exe" in the Attachment and press Options/List all Devices.
4.1 Now you choose your device which is connected in DFU-Mode and which should be named "LANCE", Choose "WinUSB (v6.1.7600.16385)" and" press "Replace Driver"
5. Now open "Firmware-TOOL.bat" Batch File, choose your Firmware and wait until the Flash Process finished.
if Flash Process was successful you get a green screen(If i didnt make something wrong error interpretation).
PS: Dont get scared if you get a red screen. This only means that you didnt follow all steps in this Instruction.
6. Remove USB-Cable and Press Power button.
7. Reset your Device again and have fun with your "stable" Firmware.
Instructions for Sony SBH52:
1. Download the Attachment "Sony SBH52 Firmware Tool"
2. Reset your Device via Settings/Reset
3. Power off your Sony SBH52, press "back-button" and connect in the same moment your device to the usb port of your computer.
Now you should see this screen:
4. Now open the program "zadig.exe" in the Attachment and press Options/List all Devices.
4.1 Now you choose your device which is connected in DFU-Mode and which should be named "SBH52", Choose "WinUSB (v6.1.7600.16385)" and" press "(Re)install Driver"
5. Now open "Firmware-TOOL.bat" Batch File, choose your Firmware and wait until the Flash Process finished.
if Flash Process was successful you get a green screen.
PS: Dont get scared if you get a red screen. This only means that you didnt follow all steps in this Instruction.
6. Remove USB-Cable and Press Power button.
7. Reset your Device again and have fun with your "stable" Firmware.
Instructions for Sony SBH54:
1. Download the Attachment "Sony SBH54 Firmware Tool"
2. Reset Your Device
3. Power off your device, then hold down call button and at the same time connect with the usb to pc [Thanks to pelopis]
4-7. Same like SBH52 Instructions
Warning: I take no responsibility for bricked devices or angry Sony staff.
Changelog
Latest Updates:
V.1.0 for Sony SBH 54 Firmware Tool
-added 7 different Firmware Files, which are extracted from the offical Sony App
-Option for Custom Firmware update
-Backup and Restore your Firmware
V.1.0 for Sony SBH 52 Firmware Tool
- added Sony SBH 52 Firmware Update and Downgrade Tool with 2 Firmwares: 2.3.A.0.9 and 2.4.A.0.2 [Tool Tested by myself and Tool is stable]
V.2.1 for Sony MW1 Firmware Tool
- added Option for Custom Firmware Update and Restore of backup Firmware on Sony MW1 tool with marked as BETA
----------------------------------------------------------------------------------------------------------------------------
V.2.0 for Sony MW1 Firmware Tool
- update zadig.exe
- new Batch File with MENU
- Included many other firmware updates for example: firmware 0.1.C.0.3, 0.1.E.1.4 and 0.1.E.1.6
- Add Backup feature which creates a backup of your current firmware (PS: you can send me your firmware files if they er not included in the batch File)
- Add Font.bin File to the Download files at the bottom (Font.bin fixes issues with special mp3 tags for example with Chinese or Japanese characters)
- minor bug fixes
V.1.1 for Sony MW1 Firmware Tool
- update zadig.exe
- update dfu-util.exe ( should fix error with multiple DFU devices)
V.1.0 for Sony MW1 Firmware Tool
-initial version
Troubleshooting:
If you followed all steps but dfutil cant find any dfu device then try another usb Port which is not Usb 3.0.
Please provide me older Firmware Files or older Sony MW1 and Sony SBH 52/54 Applications, for expanding the choice of Firmware.
Don´t forget to press Thanks and spread this Solution on other forums with referring on this Thread.

Feedback
Any Feedback or Thanks if you downloaded and tested this method??

USB Device Does Not Show Up
burak5 said:
Any Feedback or Thanks if you downloaded and tested this method??
Click to expand...
Click to collapse
So, when I get my MW1 into the file transfer mode. The same display as you sent. I do not get any recognition of the OS that a USB device is connected.
Mac OS 10.9.2, Windows 8.1 64bit, Windows 7 64bit.
The device is not detected in zadig. Am I missing a step? The device does not show up in device manager, or System Profiler (OSX).
Am I missing a step?

1. It´s not file transfer mode. It´s Firmware update mode (you need to press back button while connecting your device)
2. It should show up (I have a win 7 64bit)
I think you maybe missed the back button or your computer cant download the drivers (?)...

My USB Cable was shot.
So zadig.exe has "Install Driver" not "Replace". DFU-Util is saying that I have more than one device in DFU Mode. Is there a way to modify the install.bat to specify a specific device?
zadig.exe detects 5 devices on my Macbook Pro running Windows.
burak5 said:
1. It´s not file transfer mode. It´s Firmware update mode (you need to press back button while connecting your device)
2. It should show up (I have a win 7 64bit)
I think you maybe missed the back button or your computer cant download the drivers (?)...
Click to expand...
Click to collapse

Opening DFU capable USB device... Cannot open device
Hi ,
I have tried to downgrade it by given steps, While opening install.bat it says "Opening DFU capable USB device... Cannot open device"
Please do the needful
---------- Post added at 06:05 PM ---------- Previous post was at 05:57 PM ----------
paisakya said:
Hi ,
I have tried to downgrade it by given steps, While opening install.bat it says "Opening DFU capable USB device... Cannot open device"
Please do the needful
Click to expand...
Click to collapse
Appreciate your help

VirginiaVn900 said:
My USB Cable was shot.
So zadig.exe has "Install Driver" not "Replace". DFU-Util is saying that I have more than one device in DFU Mode. Is there a way to modify the install.bat to specify a specific device?
zadig.exe detects 5 devices on my Macbook Pro running Windows.
Click to expand...
Click to collapse
I updated the dfu-util. Now this error shouldnt happen anymore.
Pls give Feedback
paisakya said:
Hi ,
I have tried to downgrade it by given steps, While opening install.bat it says "Opening DFU capable USB device... Cannot open device"
Please do the needful
---------- Post added at 06:05 PM ---------- Previous post was at 05:57 PM ----------
Appreciate your help
Click to expand...
Click to collapse
Then you missed the steps with zadig.exe.
I updated the instructions.
Please look on Step 4 and 4.1 with the picture.

Thanks!
Great job man!
I wrote several times to complain about sony for this update but I have never heard.
With the downgrade is risen!

Verified Safe
burak5 said:
I updated the dfu-util. Now this error shouldnt happen anymore.
Pls give Feedback
Then you missed the steps with zadig.exe.
I updated the instructions.
Please look on Step 4 and 4.1 with the picture.
Click to expand...
Click to collapse
Verified Working.
Now running 0.1.D.0.6
Thanks a million!

Thanks
Please use Thanks button for telling thank you

Thank you so much!! finally found a way to downgrade! you saved my mw1 from the trash can lol. can't believe sony just dropped the support entirely without fixing the firmware...

pressed "back button" and connected usb port but didn't display firmware download mode just charging icon. OS is win8.1 usb3.0. i'm sure the button i pressed is "back button" not volume back button. please help me. Thanks

joyqing said:
pressed "back button" and connected usb port but didn't display firmware download mode just charging icon. OS is win8.1 usb3.0. i'm sure the button i pressed is "back button" not volume back button. please help me. Thanks
Click to expand...
Click to collapse
1. If it didn't switch to firmware update mode you pressed the false button ( or the Usb 3.0 port create problems)
2. Usb 3.0 port is not supported by the dfu-util ( I tested myself), but Windows 8.1 is supported
>>> Switch to Usb 2.0 port and test all buttons, if the back button didn't work (but should work).
PS: Dont forget to give feedback, which thing created a problem

burak5 said:
1. If it didn't switch to firmware update mode you pressed the false button ( or the Usb 3.0 port create problems)
2. Usb 3.0 port is not supported by the dfu-util ( I tested myself), but Windows 8.1 is supported
>>> Switch to Usb 2.0 port and test all buttons, if the back button didn't work (but should work).
PS: Dont forget to give feedback, which thing created a problem
Click to expand...
Click to collapse
finally I got it. no problem with usb3.0+win8.1 64bit.
at first I pressed the wrong button.
Thanks man.:laugh:

I can confirm it is working, hope my MW1 is stable now...
Does anyone know what the benefits are of this FW instead of the latest?
Is there any way to increase the Max volume?

request pls
hi..G8 job...Just saw ur post and trying to revive the MW1...iam using ur steps right now...just don't know if the flashing is over.....any msg will come??
In meantime any recent update to this post..since i am seeing this post from 2014..
Thanks a lot in advance

How is your MW1 ? Please give some feedback!
joyqing said:
finally I got it. no problem with usb3.0+win8.1 64bit.
at first I pressed the wrong button.
Thanks man.:laugh:
Click to expand...
Click to collapse
TheTeek said:
I can confirm it is working, hope my MW1 is stable now...
Does anyone know what the benefits are of this FW instead of the latest?
Is there any way to increase the Max volume?
Click to expand...
Click to collapse
surchit said:
hi..G8 job...Just saw ur post and trying to revive the MW1...iam using ur steps right now...just don't know if the flashing is over.....any msg will come??
In meantime any recent update to this post..since i am seeing this post from 2014..
Thanks a lot in advance
Click to expand...
Click to collapse
Hello guys! How is your MW1 doing nowadays? I am about to buy two units for my brother and me, and would not want a fiasco.
Please, tell me, with this firmware version 0.1.D.0.6 the device is working perfectly? Do you recommend this headset?
For me this is the most complete and feature packed Bluetooth headset today, I am about to buy it.
Are all its features working in Android 5.1.1?
Please help me! Thank you!
---------- Post added at 12:18 PM ---------- Previous post was at 11:56 AM ----------
burak5 said:
Like the Title says, I found a Solution for downgrading your devices after one Day I got my Sony MW1 . I'm Using the, method of Flashing
Sony Smartwatch 2 optimized on the Sony MW1 which is using a similar (same?) Hardware. I extract the firmware from the headset apk.
Instructions:
1. Download the Attachment "Sony MW1 Downgrade 0.1.D.0.6"
2. Reset your Device via Settings/Systeminfo/Reset
3. Power off your Sony MW1, press "back-button" and connect in the same moment your device to the usb port of your computer.
Now you should see this screen:
4. Now open the program "one m.exe" in the Attachment and press Options/List all Devices.
4.1 Now you choose your device which is connected in DFU-Mode and which should be named "LANCE", Choose "WinUSB (v6.1.7600.16385)" and" press "Replace Driver"
5. Now open the "Install.bat" script and wait until the Flash Process finished.
6. Remove USB-Cable and Press Power button.
7. Reset your Device again and have fun with your "stable" Firmware.
Warning: I take no responsibility for bricked devices or angry Sony staff.
Changelog
V.1.1
- update zadig.exe
- update dfu-util.exe ( should fix error with multiple DFU devices)
V.1.0 by
-initial version
Please provide me older Firmware Files or older Sony MW1 Applications, for expanding the choice of Firmware.
Don´t forget to press Thanks and spread this Solution on other forums with referring on this Thread.
Click to expand...
Click to collapse
Hey, man! Thank you for this tutorial and update! Seems like this is the only one Would you tell me how is your MW1 doing? Is it working fine with Android 4 and 5?
Have you got any other older firmware? Like C version 0.1.C.0.3? Is this version 0.1.D.0.6 is working fine with all the features?
I would very much appreciate your comments on the device as I'm about to buy it!
Thank you!

yes my mw1 is working fine with android 4.1 and it should work fine with android 5 because bluetooth headset protocol ist standarized.

MW1 is now awesome!!!
After getting these bulk, with no instructions, I finally got it to pair with my Nexus 6. After pairing it did not play over the headset, just out of the N6 speakers. After a power cycle it started working. The sound sucked the big one. It was like hearing it over an answering machine from the 80's. So after a google search on firmware, I saw this thread.:victory:
It only took 3 minutes to downgrade and it sounds GREAT!!!!!:good:
I am on windows 10 with a USB 3.0 and let the Zadig update to 2.1.2.677. All the other files were fine.
The install.bat file only took about a minute to finish.
Many Thanks and Happy Holidays!!!!

I made a big update and included other firmware updates which you can test. I couldn't test al of it because i don't have a Sony MW1 any more (I tried to change the battery and broke it ) . It would be nice if you could test All firmware updates which I extract from the official Sony MW 1 Application and the new batch File Menu. I hope I don't get into trouble because of some angry Sony staff