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
Related
What is the starting situation?
You bricked your phone. It can't be started anymore. No charging, no recovery, no fastboot. Your phone is not recognized by your computer.
What to do now?
1. Drain the battery!
Therefore you just have to be patient. Press the power button every now and then. It takes approximately 2 days until the battery is drained.
How do you know if your battery is drained?
When connecting to a charging station or a computer the led-light will pop up red and turn off after a few seconds again.
2. Download the rom for your device!
HTML:
http://androidmtk.com/download-gionee-stock-rom-models
HTML:
http://www.android.gs/download-gionee-stock-rom/
The drivers and the flash tool you will need are also contained in the download.
3. Install the driver.
Your phone should be disconnected while you are installing them. When you connect your phone now it should be recognized under COM port as 'Qualcomm HS-USB QDLoader'.
4. Start the tool and set the settings like 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"
}
On almost every website it is stated that you should set "Platform" to "8x26". Do not do it! ( This was the cause my phone bricked)
"Platform" hast to be set to "8974" for our phone.
5. Click on download and wait until it is finished.
Enjoy your unbricked Gionee!
FAQ:
Q) GNQC download doesn't work. It gives the error "application failed to start".
A) Install VC++ 2005 redistributeble SP1 ATL security upgrade.
Q) I receive an "incorrect parameter error".
A) You are using a Chinese flash tool so make sure your copy of windows supports Chinese. Change local settings in the control panel.
Q) I receive an "in gnqc bp_image file doesnt exist" error.
A) Remove Chinese characters from the name of the image folder.
Q) My phone is not detected.
A) Let it sit and drain the battery in 1-2 days. Now plug it in via usb cable.
The biggest problem:
Q) My phone is detected as usb hid device instead of com port.
A) There are problems with different versions of Windows.
For me, this problem occured with Windows 8 64-bit.
It is recommended to follow the procedure on a computer with Windows XP 32-bit. Windows 7 32-bit might work also.
Alternatively:
Use a virtual machine. (I used Virtual Box by Oracle.)
1. Create a virtual image of windows xp 32bit in the virtual machine.
2. Install windows xp 32bit on it. (You need a windows xp installation ISO or CD)
3. Put the downloaded rom, flash tool and drivers into the virtual machine. (e.g. with an usb flash drive)
4. Install the drivers while your phone is disconnected. Now connect your phone to the virtual machine.
Now your phone should be recognized. Follow the rest of the procedure.
There are some threads on xda which try to help with bricked E7 devices. I just wanted to put all together and add some information. So make sure you check the credits!
Credits:
dhirajranger
HTML:
http://forum.xda-developers.com/showthread.php?t=2735079
StarLord21
HTML:
http://forum.xda-developers.com/elife-e7/general/unbricking-gionee-elife-e7-total-hard-t3186697
psghari
HTML:
http://forum.xda-developers.com/elife-e7/help/hardbricked-e7-fix-t3136602
[/QUOTE]The biggest problem:
Q) My phone is detected as usb hid device instead of com port.[/QUOTE]
My phone after drain the battery don't detected de device and don't light any red led. Nothing. Please can you help me? I am very disgust.
Thanks for your attention and hope your answer ASAP.
thesmartphonero said:
My phone after drain the battery don't detected de device and don't light any red led. Nothing. Please can you help me? I am very disgust.
Thanks for your attention and hope your answer ASAP.
Click to expand...
Click to collapse
First of all open your device manager. Then connect your phone. Check if any device was added (like unknown USB-device or something). That is the case if battery is not drained.
USB Input Device IN HID Menu
My phone is detected as USB Input Device in the HID Section
whats next?
Always shows this error..
Please help me out..
shivam2702 said:
My phone is detected as USB Input Device in the HID Section
whats next?
Click to expand...
Click to collapse
The biggest problem:
Q) My phone is detected as usb hid device instead of com port.
A) There are problems with different versions of Windows.
For me, this problem occured with Windows 8 64-bit.
It is recommended to follow the procedure on a computer with Windows XP 32-bit. Windows 7 32-bit might work also.
Alternatively:
Use a virtual machine. (I used Virtual Box by Oracle.)
1. Create a virtual image of windows xp 32bit in the virtual machine.
2. Install windows xp 32bit on it. (You need a windows xp installation ISO or CD)
3. Put the downloaded rom, flash tool and drivers into the virtual machine. (e.g. with an usb flash drive)
4. Install the drivers while your phone is disconnected. Now connect your phone to the virtual machine.
Now your phone should be recognized. Follow the rest of the procedure.
shivam2702 said:
Always shows this error..
Please help me out..
Click to expand...
Click to collapse
Make sure you have the right firmware.
4ndaKava said:
The biggest problem:
Q) My phone is detected as usb hid device instead of com port.
A) There are problems with different versions of Windows.
For me, this problem occured with Windows 8 64-bit.
It is recommended to follow the procedure on a computer with Windows XP 32-bit. Windows 7 32-bit might work also.
Alternatively:
Use a virtual machine. (I used Virtual Box by Oracle.)
1. Create a virtual image of windows xp 32bit in the virtual machine.
2. Install windows xp 32bit on it. (You need a windows xp installation ISO or CD)
3. Put the downloaded rom, flash tool and drivers into the virtual machine. (e.g. with an usb flash drive)
4. Install the drivers while your phone is disconnected. Now connect your phone to the virtual machine.
Now your phone should be recognized. Follow the rest of the procedure.
Make sure you have the right firmware.
Click to expand...
Click to collapse
Yes i'm having the correct firmware.... Please help
shivam2702 said:
Yes i'm having the correct firmware.... Please help
Click to expand...
Click to collapse
I think I have found your problem. Uncheck "Chenck Phone" and try again.
Otherwise just try to download the correct firmware again and try again.
Now Its showing a different Error....
It Shows this error after 1% in the Checking of GNQC files..
Can you please zip you GNQC folder and mail to me please.
I have also checked after unchecking the chunk phone but the result is same ...
1652.48 MB is shown at my section and your's showing 1652.50 MB...
Is it the issue?
Firmware Check
4ndaKava said:
I think I have found your problem. Uncheck "Chenck Phone" and try again.
Otherwise just try to download the correct firmware again and try again.
Click to expand...
Click to collapse
Are are using the "Gionee_E7_32G_0301_T8143.ZIP" ?
2,630,999 KB or 2,694,142,825 bytes or 2.50 GB....
is it the same?
And the link that you provided is having the V 4.2.2...
shivam2702 said:
Are are using the "Gionee_E7_32G_0301_T8143.ZIP" ?
2,630,999 KB or 2,694,142,825 bytes or 2.50 GB....
is it the same?
And the link that you provided is having the V 4.2.2...
Click to expand...
Click to collapse
http://www.android.gs/download-gionee-stock-rom/
You might also try this page for a rom.
Is it still recognized as hid?
If so, you should make it recognize as qualcomm 9008 or 9006 before trying..
shivam2702 said:
It Shows this error after 1% in the Checking of GNQC files..
Click to expand...
Click to collapse
I had the same problem, I solved in this way:
Open the downloader
Connect the phone
Wait until it's recognised
Try to flash
If it stops, unplug and then plug the phone again keeping the downloader opened.
I know it could seem stupid but in windows the most of the things works in this way...
:crying: Not Working for me
:crying:
Not Working for me
I restored but now no network please help
shivam2702 said:
It Shows this error after 1% in the Checking of GNQC files..
Can you please zip you GNQC folder and mail to me please.
I have also checked after unchecking the chunk phone but the result is same ...
1652.48 MB is shown at my section and your's showing 1652.50 MB...
Is it the issue?
Click to expand...
Click to collapse
I am also getting same error...
any solution...?
Awesome it made my Gionee unbricked
My device is soft bricked but the volume up key is broken so will this method work ?
and also that my device is not recognised
vedant.sharma68 said:
My device is soft bricked but the volume up key is broken so will this method work ?
and also that my device is not recognised
Click to expand...
Click to collapse
My xp 32 bits doesn't recognize the phone, it apperars like USB not Qualcomm... any idea?
ALCTEL HS Usb QDloder 9008 Driver Needed
All time i connect device to pc my pc detect hid/usb divice ...than 21/1/2016 my device connected pc and restart my pc. After restart i saw one iobit driver booster app wich notify me i have 3 new drive update one is my nvdia display one is my internet adapter ..but last one is unknown device detected ...than i click update now phone atomatic connect port ALCATEL HS Usb QDloder 9008 (port20)..now i open flash tool select firmware and select 8974 instead of 8x26 ..start download withing 5 minutes my phone downloaded 100% successfull now after 2 minutes i remove phone to pc connect charger red light start continue and 10 minutes later i pressed power button 15 second and my phone start like new unroot ..i al to happy that night ..thanks to all who give me right direction..thanks all ..sorry for bad English..
my phone dead
Hi friend,
My phone dead while updating on (GN_Qcom_Download_Tools_V2.1.0.1). Now cant connect Phone with PC even i installed all drivers for gionee elife e7 32GB. now in DEVICE MANAGER showing UNKNOWN DEVICE. kindly brothers someone guide me how to install again firmware.
---------- Post added at 08:18 AM ---------- Previous post was at 08:00 AM ----------
brother i have same problem with my gionee elife e7 32gb and i try same firmware Gionee_E7_32G_0301_T8180_(by_xdafirmware.com). ON GN_Qcom_Download_Tools_V2.1.0.1.
Kindly help me bro, my whatsapp 00971503294484.
shivam2702 said:
It Shows this error after 1% in the Checking of GNQC files..
Can you please zip you GNQC folder and mail to me please.
I have also checked after unchecking the chunk phone but the result is same ...
1652.48 MB is shown at my section and your's showing 1652.50 MB...
Is it the issue?
Click to expand...
Click to collapse
This guid shows two things:
1. How to enable QPST and USB diag mode.
2. How to enable rSAP.
Please notice, I'm not responsible for any damage in hard- and software of your devices, if you are following this guid. You do all on your own risk.
Click to expand...
Click to collapse
For this guid your device have to be rooted.
In the newer versions of OnePlus' CyanogenMod diag mode is disabled in kernal. Therefore you have to flash an earlier ROM. In this step download Calkulin's Stock Rooted XNPH44S ROM and store zip to your device.
Go to recovery and make a full backup. This is really necessary to preserve the state of your phone.
Wipe Dalvik Cache, System, Data and Cache. ATTENSION: This will delete all your settings, apps and app data!
Install XNPH44S ROM
After rebooting system go to Settings -> About Device -> tab ten times on Build-Number to unlock developer settings. Than go to Developer settings and make sure USB debugging is enabled.
Download the package, containing driver and QPST
Connect your device to USB, go to Settings -> Storage -> USB computer connection and deselect both MTP and PTP.
For Win8 and Win10: restart with deactivated driver signature check.
Open ADB (Android SDK) and type following commands:
Code:
adb shell
Code:
su
Code:
setprop sys.usb.config diag,adb
Go to Windows Device Manager and open Other Devices node. There are two entries of our device "A0001". Klick right on the first one and choose Update driver software -> Browse my computer... -> Let me pick from a list... -> Show all devices -> Have disk -> Browse...
Browse to folder Driver in downloaded package, than open Win x64 or Win x86 corresponding to your system, select *.inf file and apply.
After seccessful installation there is a Modems node in Device Manager, containing node HTC USB Modem. Right click and go to Properties. In top of the Modem tab page is the information about used COM-port. Remember that COM<number>.
Go to QPST folder in downloaded package and execute setup.exe to install QPST.
Open QPST Configuration from windows Start menu, go to Ports tab page and click on Add New Port.... Type (the remembered) COM<number> to the "Port:" text box and OPO to the "Port Label:" text box. Than click on OK.
Active Phones tab page should now look like 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"
}
Now you can use QPST.
Open EFS Explorer from windows Start menu. It may take a moment to read data from your device.
On left side you can see a folder tree like in file explorer. Navigate to /nv/item_files/modem/qmi/uim
Click right on right side and than Copy Item File from PC. Browse to EFS Entry folder of downloaded package and choose file sap_security_restrictions.
Close all windows and reboot your device. If you want, you can repeat the steps 10, 16 and 17 to verify success.
Boot to recovery and restore your backup.
Now go to Google Play and download app Bluetooth SIM Access Install and app Bluetooth SIM Access (Trial)
Open Install app and click on Install system files. The phone have to reboot after installation. If you want to verify successful installation, open app again, the desintall button have to be enabled now.
Enable your Bluetooth
Open Bluetooth SIM Access (Trial) app go to Settings -> Check SIM Access. If there no errors and several entries with green check marks, than rSAP is working now.
Files:
Package (On Mega click on 'download in browser')
ROM (On Mega click on 'download in browser')
Acknowledgement:
Thank you devilsshadow, for your tutorial, which showed me how to setup QPST.
Thank you Calkulin, for your ROM, which makes it possible to use QPST.
Special thanks goes to Martin , for developing his great apps and making our phones better.
Great! Thanks a lot!
Finally got my OPO working with my VW premium bluetooth car system
EFS Explorer crashes with a Runtime error upon opening sap_security _restrictions file.
Win 10 64Bit.
Edit:
Got it to work with the Frankenstein modem from here:http://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
Looks like it does not work with the newer modems, i was using bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip
Hi, do you have further informatiom about the crash? Exact error message?
Did you try windows compatibility mode?
I used win 8.1 x64. Sorry I don't have win 10 to test it.
I used Win 10 Pro 64bit, and had no problems using the software.
Thank you very much for the precise description! I linked it from android-rsap
With my newly acquired OPO I first could not install the diag drivers. The USB id seems to have changed from VID_05C6&PID_6765&MI_00 to PID_676C. After changing that in the inf file the installation worked and I could run QPST.
Great. Thanks a lot.
Can i flash after enabling rSAP CM13, or will it disable rSAP again?
Thank you.
I'm wondering about this myself.
I was running jgcaap CM13 before I did enable RSAP. Took a backup of everything in TWRP first. And restored everything except EFS after (thought that if I flashed EFS I would loose rsap again, but I'm not sure). Everything is working fine btw
fitzpete said:
EFS Explorer crashes with a Runtime error upon opening sap_security _restrictions file.
Win 10 64Bit.
Click to expand...
Click to collapse
This seems to happen with more recent baseband versions. They require the "Factory Test Mode" (ftm_mode) to be set to allow changes. ftm_mode is NV item 453. It can be modified with the QXDM tool.
Now the value of ftm_mode is cached inside the baseband software. Currently I don't know a better solution than to reboot the phone. Sadly in some phones (OnePlus 2) the value doesn't survive the reboot.
Mugen_Civic said:
Great. Thanks a lot.
Can i flash after enabling rSAP CM13, or will it disable rSAP again?
Thank you.
Click to expand...
Click to collapse
Yesterday I do enable RSAP, wow I am really happy about that.
What happens when do a full wipe for flash and install an clean ROM? Is RSAP deactivated again?
Gesendet von meinem A0001 mit Tapatalk
hums87 said:
What happens when do a full wipe for flash and install an clean ROM? Is RSAP deactivated again?
Click to expand...
Click to collapse
No. RSAP will stay enabled.
Hi many thanks for this guide but all link are dead ! can you reupload them ?
thanks
Thanks for the hint. I will reupload it soon and give an announcement.
mamath53 said:
Hi many thanks for this guide but all link are dead ! can you reupload them ?
thanks
Click to expand...
Click to collapse
I reuploaded the files to other hoster.
Could someone tell me what this is good for?
Flatric said:
Could someone tell me what this is good for?
Click to expand...
Click to collapse
RSAP (remote SIM access protocol) is a communication standard for free speeking systems. Eg. Volkswagen concern uses it in its cars. The SIM of your phone is cloned per bluetooth to your cars build in mobile phone module. The radio functions (calling/SMS) are disabled on your phone while connection and executed by your car. That is good for battery, electro smog in your car and connectivity.
But it have drawbacks too. No internet connection on phone while connection. This problem is solved in newer cars by providing a wifi hotspot, which uses the internet contract of your SIM.
Hi
If I open Bluetooth SIM Access (Trial) app, there is no "Check SIM access" option.
Did I do something wrong?
r0tati0n said:
Hi
If I open Bluetooth SIM Access (Trial) app, there is no "Check SIM access" option.
Did I do something wrong?
Click to expand...
Click to collapse
Hi, I think the check has moved to the installer app. See section 3.
Thanks
Altough I couldnt find anything in there too...
In the installer app I get 3 check marks:
System Files installed, Connect to Socket, Connect to SIM, all green.
Does that mean I have RSAP?
Do I need anything else?
Can I uninstall the app and keep RSAP?
r0tati0n said:
Thanks
Altough I couldnt find anything in there too...
In the installer app I get 3 check marks:
System Files installed, Connect to Socket, Connect to SIM, all green.
Does that mean I have RSAP?
Do I need anything else?
Can I uninstall the app and keep RSAP?
Click to expand...
Click to collapse
I think so. Test it with your car. Thats the reason why the trial app exists. But you have to know that the trial app swaps numbers in contact, therefore it is not good for all day use.
I haven't uninstalled the installer app. In this app you can see updates for the system files. But the updates are seldom and if the installed version works for you, I think it's no problem to uninstall it.
For Ze500CL only! If you got No Fastboot, No recovery, No Display, hard bricked your device.You must perform sequential steps indicated below, process will include many small steps. Plz make sure to perform all steps in same sequence and same manner as prescribed. Remove all drivers related to mobile you have installed earlier.
Step 1: Install the driver and connect mode IntelSocUSB IntelSoc:
This Is the driver which help a computer connecte to your Zen2 IntelSoc mode. To install these driver you need to perform special steps if you are using windows 8 / 8.1, 10 . you need to disable driver signature enforcement before installing drivers. below i have mentioned steps needed to install driver for various versions of windows. but first download the needed driver from link given below.
https://drive.google.com/open?id=0B72QQTXqZSRwR0JGeFI2U3FUZ2c
Step 1.1 - how to install these drivers:
If you're using Windows 7:
Right-click the file - iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc.
If you're using Windows 8 / 8.1 :
On Keyboard press Windows + I to show charm bar in the right corner,
click on the option setting. Choose "Change PC Settings" to enter the PC Settings.
Choose the General tab and navigate to Advanced Startup section, continue click Restart now.
This will reboot windows and allows you access to the advanced mode, now select the following options: Troubleshoot - -Startup Settings Advanced Options and then click the Restart button to restart the computer.
now you will see screen with various options numbered from 1. Find disable driver signature enforcement. And press the appropriate number on keyboard your pc will reboot
Now Right-click the file - iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
After This step, the driver installation is finished, continue to section 1.2
If you're using Windows 10 :
On Keyboard press Windows + I or click Start, select Settings.
In The Settings window, select the Update & security.
Continue Choose recovery and click "Restart now".
When The computer has access to the Advanced screen you will see screen with various options numbered from 1. Find disable driver signature enforcement. And press the appropriate number on keyboard your pc will reboot
Now Right-click the file - iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
After This step, the driver installation is finished, continue to section 1.2
1.2 Connect Zenfone with computer IntelSoc Mode:
Now you must complete this step before installing xfstk downloader. it helps to setup device's connection to PC
on your pc open device manager and find Intel Soc.
Click to expand it. You will see a single option under here.
Connect your phone to computer via USB cable,
now back to the phone, hold power button for 10 seconds to shutdown completely, then press simultaneously the key "power" + "volume down", until phone vibrates. Or computer makes detection sound, wait a few seconds. it will add an item immediately below intelSoC in device manager “MOOREFIELD” new devices is connected successful.
Now Download intel android USB Driver and install normally from link below:
https://drive.google.com/open?id=0B72QQTXqZSRwSU5CdDNuUElEcUE
1.3 Installing xfstk-downloader:
installation of xFSTK is very simple. download xFSTK setup from the link below. to install. right click the setup file and run as Administrator. click next next simply until you finish the download process
Here is the download link:
https://drive.google.com/open?id=0B72QQTXqZSRweDdfMjlPOGEyTW8
Now to Unbrick Process.
Using xFSTK to unbrick the Device:
Required Files:
https://drive.google.com/open?id=0B72QQTXqZSRwRTRCMlJJcVB2a2M
After downloading the necessary files extract it. It will contain 5 files which will be used to bring your phone back to life.
Now Run xFSTK as Administrator. Now click “CLVP A0 / B0 / B1” last option bottom right hand.
Then Go to Options to change the value of gp flag. Tick GP value over ride, in the Value Section change value to 0x80000245. Now tick Include softfuse file. And select the file Named “signed_CLVP_CSAP_SoftFuseFile_PF450CL” from extracted files. Change the detection timeout value to 180. And click okay.
Now select Firmware files FW DnX: and IFWI: by clicking small three dots:- CLVp_CSAP_FWR_DnX_20.3E.bin and IFWI_v91.15_CSAP_MFG.bin from extracted
Now select operating system: OS DnX - CLVp_CSAP_OS_DnX_20.3E.bin, OS image - droidboot.img.POS_sign.bin from extracted files.
Now see the Device Status section below, this section shows the number of connected target (devices) , you need at least one device is connected., if not try hold power button for 10 seconds to make sure it power downs completely. then hold the volume down button and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds.
As you see connected target. Click begin download to start implementation. You may get error multiple time. But repeat the process again and again. Untill you see FW+OS download complete.
After that you may seea 4 color, just like some TV stations stop broadcasting on TV. You have to wait a little. after few seconds or minutes device will boot into bootloader. If not repeat the xFSTK process again.
Flash Raw Firmware Using Asus Flash Tool:
Required Files:
Asus Flash Tool: https://drive.google.com/open?id=0B72QQTXqZSRwUDZqa0M4SWRObVE
Raw Firmware File: https://yadi.sk/d/LNzLj8mMyytyL
Download Asus Flash Tool and install. Run asus flash tool as administrator. And select the phone model. Then select the downloaded raw file and click start button to flash.
Note: sometimes flash process may go endless. If this happens remove the usb from computer. Kill asus flashtool process from task manager. Now run tool again and flash.
Hi dude, thank you very much for your guide and your help but I still have some problems that I cant resolve.
Firstly in order to make my phone detected by my pc i need to powercycling it pressing "Power + vol up" and not down as you mentioned. I followed any step of your guide but every time I click begin download the bar under the usb logo on my phone it became red and the download did not complete and abort it self. Did you know how to solve this issue ?
waltermaffy said:
Hi dude, thank you very much for your guide and your help but I still have some problems that I cant resolve.
Firstly in order to make my phone detected by my pc i need to powercycling it pressing "Power + vol up" and not down as you mentioned. I followed any step of your guide but every time I click begin download the bar under the usb logo on my phone it became red and the download did not complete and abort it self. Did you know how to solve this issue ?
Click to expand...
Click to collapse
as i mentioned in my guide. very first of all remove all kind of mobile related drivers and xfstk tood if you already installed. it is very important to install soc driver before installing xFSTK. moreover before installing xFSTK and after installing isoc driver you need to power cycle and connect your device to pc. and use volume down button. change the right flag value. and when using xfstk. load files. click begin download. when it start waiting for device then power cycle it. it will itself force into download.
if i bricked my phone but i can enter fastboot mode can i recover it using the asus flashtool?
fabi.m said:
if i bricked my phone but i can enter fastboot mode can i recover it using the asus flashtool?
Click to expand...
Click to collapse
yes definitely you can do it.. download raw firmware and sew it.. if asus flash tool fails. do tell me. i will try to write manual commands to flash.
sukhwant717 said:
yes definitely you can do it.. download raw firmware and sew it.. if asus flash tool fails. do tell me. i will try to write manual commands to flash.
Click to expand...
Click to collapse
alright, thank you so much. im downloading right now, i'll let you know either way!
Thank you so much! worked perfectly
so after flashing raw fw and booting up it suddenly is carrier locked and is askig for a "SIM network unlock pin" i tried flashing a different ROM and the problem persists.. any suggestions? My device was unlocked previous to this..
fabi.m said:
so after flashing raw fw and booting up it suddenly is carrier locked and is askig for a "SIM network unlock pin" i tried flashing a different ROM and the problem persists.. any suggestions? My device was unlocked previous to this..
Click to expand...
Click to collapse
don't use wrong code. you will lock permanently. i will give you unlock code soon
sukhwant717 said:
don't use wrong code. you will lock permanently. i will give you unlock code soon
Click to expand...
Click to collapse
thank you! i now have my phone unlocked thanks to the code you sent me
help me, my cloverviewplus driver was not installed, any solutions?
xJri17 said:
help me, my cloverviewplus driver was not installed, any solutions?
Click to expand...
Click to collapse
which operating system you are using?
sukhwant717 said:
which operating system you are using?
Click to expand...
Click to collapse
windows 7 32bit
xJri17 said:
windows 7 32bit
Click to expand...
Click to collapse
need to install driver before xFSTK. soc device must be recycled to install driver correctly.
xFSTK. will not open for me. I followed all the steps and I run xFSTK. as Administrator. It asks me if I want to allow it to run. I click Yes, but nothing happens. When I look in Task Manager it is not there?>
My OS is Windows 10.
Any ideas?
sukhwant717 said:
need to install driver before xFSTK. soc device must be recycled to install driver correctly.
Click to expand...
Click to collapse
how to recycling my device?
{
"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"
}
Can't detect my device
Sent from my HTC One M9 using XDA-Developers Legacy app
[/IMG]
Sent from my HTC One M9 using XDA-Developers Legacy app
i have the red bar under usb icon as well.
---------- Post added at 10:42 PM ---------- Previous post was at 10:40 PM ----------
[/COLOR]help help
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
If anyone needs this, here is BND-L24 Board Firmware, IDT Flash Tool, Drivers, and Instructions to enter EDL Mode and Flash the board software
**Flashing Board Software should be a final option. If you are still able to flash/boot into TWRP, HuRu or HWOTA would be a better option**
Download :https://drive.google.com/file/d/108uEQyCBMQSywCTOB2c7p9cz35dv_UP9/view?usp=sharing
Image I forgot to add to archive: https://drive.google.com/file/d/1bp_pqu-1HGLyxzsO5c7OEEfCmGjahz-O/view?usp=sharing
1.) Take Back Cover Off Phone (Watch a disassembly video from youtube for the Honor 7X if you do not know how)
Basically you use a guitar pick or pry tool around the edges
2.) Unscrew the plate above the battery and take it off
3.) Under the plate you took off, there should be a black connector for the battery, use tweezers or something to take that off
4.) Plug USB into either computer or phone, but not both
5.) place the tips of the tweezers to the 2 Short Points ( See Image )
6.) reattach battery connector
7.) While holding the 2 short points with tweezers, plug the phone into your computer
8.) Check Device Manager that your Phone is detected as COM Port
9.) Open IDT
10.) Add the Board Firmware .xml
11.) Press Start
12.) Put the dload folder on a SD Card and insert it into your phone
13.) Once your phone starts, in one of the manufacturer apps, there is an option for SD Card Update
14.) Once that's installed, you can now use HuRu, FunkyHuawei, DCPhoneix or whatever you prefer to go to stock firmware
THANK YOU! This helped a ton, I was in quite the situation! Black screen and only fastboot. But now I have neither so i have to do it again. Is there any chance you have the firmware for Nougat? That would be nice, as the current one is Ice Cream Sandwich.
Awesome!
---------- Post added at 08:07 AM ---------- Previous post was at 08:06 AM ----------
THANK YOU! This helped a ton, I was in quite the situation! Black screen and only fastboot. But now I have neither so i have to do it again. Is there any chance you have the firmware for Nougat? That would be nice, as the current one is Ice Cream Sandwich.
Awesome!
---------- Post added at 08:18 AM ---------- Previous post was at 08:07 AM ----------
Nevermind, I just realized the dload file you included is what i was looking for xD. And here I was trying to manually root with adb shell to somehow flash nougat from the OS. A very roundabout way to go about it i know, but there was that image verify thing...heh.
Thanks! This really helped.
Quick question, how did you get the crc files for each partition? Also can they be edited?
IMAGE Download Software - IDTML01Ver1001
Hi, I'm trying to flash board firmware for my hard bricked Huawei Mate 9 (MHA-L29C636) using IMAGE Download Software - IDTML01Ver1001.
I can't seem to flash the firmware. I got this error message by using either "HLMHAAL00AM00A073.xml" or "update_nv_rback.xml"
"Log begin 2020.08.15 03:55:23
Usb com download begin.
Download bootloader[1] begin
The address is: 20000
Download error: 4, 0
Download error: 4, 0
Download error: 4, 0
Download end with cause: 0
Download switch to fastboot.
Download error: 1, 259"
FAIL (4s). Error (4)
Am I doing something wrong here? Please let me know I need to have my phone fix asap for my online class. Thank you very much in advance.
{
"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"
}
kylle.tagle14 said:
Hi, I'm trying to flash board firmware for my hard bricked Huawei Mate 9 (MHA-L29C636) using IMAGE Download Software - IDTML01Ver1001.
I can't seem to flash the firmware. I got this error message by using either "HLMHAAL00AM00A073.xml" or "update_nv_rback.xml"
"Log begin 2020.08.15 03:55:23
Usb com download begin.
Download bootloader[1] begin
The address is: 20000
Download error: 4, 0
Download error: 4, 0
Download error: 4, 0
Download end with cause: 0
Download switch to fastboot.
Download error: 1, 259"
FAIL (4s). Error (4)
Am I doing something wrong here? Please let me know I need to have my phone fix asap for my online class. Thank you very much in advance.
Click to expand...
Click to collapse
This tutorial is for the Honor 7x and the Huawei Mate SE. I'm guessing the errors you're getting are because your device isn't compatible with this firmware. Sorry about that.
Kr1msonReaper said:
This tutorial is for the Honor 7x and the Huawei Mate SE. I'm guessing the errors you're getting are because your device isn't compatible with this firmware. Sorry about that.
Click to expand...
Click to collapse
Yes sir, I'm aware that this tutorial is for Honor 7x, as a matter of fact, I've downloaded the board firmware files compatible with my device which is "HLMHAAL00AM00A073 Board Software general 7.0.0 r1 EMUI5.0 05021YVS".
What I did was I extract the .ef file using easy firmware extractor then I run IDT v.2.0.0. I have no idea what's the problem here.
This is the new error I got after using update_nv_rback.xml
"usb1:Start downloading with VCom!
usb1pening COM4 Success
usb1:download mode enter:37
usb1ownloading xloader begin.
usb1:SendFrameRcvAck: Send Fail.
usb1:SendFrameRcvAck: Send Fail.
usb1:SendFrameRcvAck: Send Fail.
usb1:SendFrameRcvAck: Send Fail.
usb1:SendFrameRcvAck: Send Fail.
usb1ownloading xloader : send frame fail.
usb1:[DETAIL_ERROR_CODE] :4
usb1:Midway download fail
FAIL (47 s). Error (4)".
Hoping for your recommendation. I'm so hopeless. </3
I'm sorry I can't be very helpful. I'm 17 and I've never had your device. Some things I would try would be to make sure that the phone is directly connected to the PC ( No multi-usb bus extensions ). Other than that I'm not sure what to say to help you.
Kr1msonReaper said:
I'm sorry I can't be very helpful. I'm 17 and I've never had your device. Some things I would try would be to make sure that the phone is directly connected to the PC ( No multi-usb bus extensions ). Other than that I'm not sure what to say to help you.
Click to expand...
Click to collapse
Did you guys have an ADB device detected in your device manager together with HUAWEI USB COM 1.0 (COM X), or it should detect only the HUAWEI USB COM 1.0 (COM X) when the device is plugged-in using USB?
Because in my case, my laptop can't detect any ADB device, it only detects HUAWEI USB COM 1.0 (COM X).
Do I need to have both drivers detected first, to prevent any error in using the IDT Software tool?
kylle.tagle14 said:
Did you guys have an ADB device detected in your device manager together with HUAWEI USB COM 1.0 (COM X), or it should detect only the HUAWEI USB COM 1.0 (COM X) when the device is plugged-in using USB?
Because in my case, my laptop can't detect any ADB device, it only detects HUAWEI USB COM 1.0 (COM X).
Do I need to have both drivers detected first, to prevent any error in using the IDT Software tool?
Click to expand...
Click to collapse
I'm not sure. I know my PC detected both though so maybe it's worth a try.
I have used this method in my hardbricked honor 7x BND-L22. But i have lost my imei.......
I'm guessing either the flasher is incompatible with your phone, the firmware is incompatible with your phone, or maybe you're just flashing it incorrectly. I'm no expert though, can't help you there, sorry.
May i ask for firmware file reupload ?
(I'm looking for board firmware package with .xml file inside and i"m unable to find it by Google)
mrmotaba said:
May i ask for firmware file reupload ?
(I'm looking for board firmware package with .xml file inside and i"m unable to find it by Google)
Click to expand...
Click to collapse
I will upload a copy shortly, I'm ultra compressing it right now. Mine includes the XML. I wish you luck!
I have hope i will be able to revive this phone.
In worst case scenario i will have to buy some credits from CDU and flash it by their app
mrmotaba said:
I have hope i will be able to revive this phone.
In worst case scenario i will have to buy some credits from CDU and flash it by their app
Click to expand...
Click to collapse
Nice. Lol, I ultra compressed the folder which took about an hour, and now I'm uploading it to mega.nz where it's going REALLY slowly. It's literally 8% uploaded been at it a while.
Kr1msonReaper said:
Nice. Lol, I ultra compressed the folder which took about an hour, and now I'm uploading it to mega.nz where it's going REALLY slowly. It's literally 8% uploaded been at it a while.
Click to expand...
Click to collapse
I bet i will download this file in less than 10 minutes with my super speed 30Mbps LTE
How's the upload going?
mrmotaba said:
I bet i will download this file in less than 10 minutes with my super speed 30Mbps LTE
How's the upload going?
Click to expand...
Click to collapse
Alright, I literally had to leave it overnight, sorry for the wait. Here's the link:
2.44 GB file on MEGA
mega.nz
Thank You very very much...
Im downloading the file and i will try to revive this phone.
mrmotaba said:
Thank You very very much...
Im downloading the file and i will try to revive this phone.
Click to expand...
Click to collapse
Yep, no problem! Good luck!
Hi guys. After flashing board software, my phone boots to a strange Android 5 version with kinds of developper apps. I was running Android 8 before my phone bricks.
How can I go back to Android 8 or to a custom firmware ? When I try to flash the stock rom for my phone, the phone get stuck on boot loop.
Another problem is that recovery mode is in chinese, any idea of how to change back to english?