Solution for unlocking above mentioned wi fi router.
Details are as follows-
WebUI version WD670_Reliance 4G_W04
Software Version WD670_Reliance 4G_B04
Hardware Version WD670_Reliance 4G_M01
IMEI 861567031838630
you can goto android adb interface by switching off the device and then connecting the device to your pc by pressing power + wps button. It will show up as android device. Install zte usb drivers. I used zte blade drivers.
fastboot devices returns the serial no and getvar all returns this
(bootloader) version:0.5
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x8000000
(bootloader) serialno:******
(bootloader) kernel:lk
(bootloader) product:MDM9607
all:
finished. total time: -0.000s
Please explain in detail
I can't get the solution please exlpian in Detail step by step. Please
Vattsal said:
I can't get the solution please exlpian in Detail step by step. Please
Click to expand...
Click to collapse
Yes... I too. When power and wps button of device is pressed at a time it gets hanged. Pl explain in detail.:angel:
Vattsal said:
I can't get the solution please exlpian in Detail step by step. Please
Click to expand...
Click to collapse
mazesahitya said:
Yes... I too. When power and wps button of device is pressed at a time it gets hanged. Pl explain in detail.:angel:
Click to expand...
Click to collapse
first switch off the device and connect to pc using usb. then press power + wps button, you will get android adb interface
Then what to do next
Ok sir now what to do next ? Here are many bootloader commands but I don't know what to do with them . I am new to this field please help me to get my Wipod wd670 unlocked. Please explain the next steps...
Please reply I want to unlock my Wipod 4G wd670 asap!
---------- Post added at 05:47 PM ---------- Previous post was at 05:46 PM ----------
pratul_09 said:
first switch off the device and connect to pc using usb. then press power + wps button, you will get android adb interface
Click to expand...
Click to collapse
Please reply me with full steps. I will be highly thankful to you sir
Still no unlock available. Unlock only possible if we can enable debug mode to enable zte ports for communicating
Sent from my CP8676_I02 using Tapatalk
pratul_09 said:
Still no unlock available. Unlock only possible if we can enable debug mode to enable zte ports for communicating
Sent from my CP8676_I02 using Tapatalk
Click to expand...
Click to collapse
Ok if you will get please inform on this forum
any solutions ?
RCOM has made fools of all the customers by upgrading the dongles and selling them WiPod @2800. By seeing their 4g plans you are sure to kill Anil.
Sent from my CP8676_I02 using Tapatalk
Guys seriously need a working solution for wd670 unlocking otherwise the device is just a show piece now
Any solutions ?
Waiting for Unlocking My ZTE WD670
Hello Friends,
Please tell me how to update my ZTE WD670 to use with another simcard.
Please Help me...
Thanks in advance...
Dear sir how to unlock reliance zte wd670 4g wipod
My mail ID : [email protected]
Some more info of this device
This looks like Legato yactoh little kernel device.
Check out Fastboot - Legato Linux distribution (Yocto project) - Legato Forum
C:\Users\Asc>fastboot getvar all
(bootloader) version:0.5
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x8000000
(bootloader) serialno:4e7edd
(bootloader) kernel:lk
(bootloader) product:MDM9607
all:
finished. total time: 0.078s
C:\Users\Asc>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.023s]
finished. total time: 0.025s
If somewith knowledge of linux can check this and help us out?
https://github.com/dianlujitao/android_bootable_bootloader_lk?files=1
Mine is ZTE WD670 airtel hotspot, when i presses power + wps buttons nothing is happening. can i get a detailed solution please.?
found this software on reliance website to disable/enable wifi and sd card...
http://www.rcom.co.in/Rcom/personal/home/software/Rcom_Switch_WIFI_SD_TOOL_V1.0.3_2016-5-9.rar
gyandeep_2007 said:
found this software on reliance website to disable/enable wifi and sd card...
http://www.rcom.co.in/Rcom/personal/home/software/Rcom_Switch_WIFI_SD_TOOL_V1.0.3_2016-5-9.rar
Click to expand...
Click to collapse
A guide with drivers is also available at:
http://www.rcom.co.in/Rcom/personal/home/software/Wi-Fi and SD Card Disable Tool_Process Guide.doc
Hi all,
Once we install the "Rcom_Switch.." software,
1. In the installation directory (ie C:\Program Files\Rcom_Switch_WIFI_SD_TOOL_V1.0.3_2016-5-9\image) there will be
a file "WD670_Reliance 4G_B03". It looks it is the firmware for this device (Reliance wd670).
2. In the installation path "adb" folder, there is a "burn.bat" which says
"fastboot -i 0x12d1 flash system ..log\mdm9607-sysfs.ubi > result.txt 2>&1"
It looks the upgrading firmware in fastboot method. I googled for "mdm9607-sysfs.ubi" and got the file
https://drive.google.com/open?id=0ByBAjpSERGkHV3ZTY0lNRWpiZXM
I dont know what are .ubi files. Generally firmware files are .img
Can we do something with it?. Can someone give idea?.
Related
Hello all,
I'm hoping someone can tell me what I'm doing wrong.
I went to HTCdev and got the unlock code emailed but this is happening when i try to unlock,I put the code in the same folder as the fastboot...
C:\Joey\Unlock Tools>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 09676CC238975AE58745ED43A1A50C8A
(bootloader) ECF90A6E24B47051377B15F0178DF92C
(bootloader) A393503ADCC8606FC14ED1761E2456F6
(bootloader) F57F798477728947A8B7E1EBD8C343BA
(bootloader) 3966E2A81DF8844D9470FF08C7F75B60
(bootloader) AE0F848DE98EA5CE3D0C4341902723C5
(bootloader) F773CAAACE0D1F8E84BCB246BCC410E3
(bootloader) 02670551F637FB8AD6E4783FDDABD8D4
(bootloader) CAC4613F93ABB73203D1EB8552BA705F
(bootloader) 9417AC2E0E0DFD82F424EB0141A0E47F
(bootloader) B1CDF5791CD1F196A2B5282143FCFB1E
(bootloader) 57453E81BFC316B3D372F6DD74D65FA6
(bootloader) F6DB2C323BCB1BFE4040B59C10B4FC90
(bootloader) 77CFE117D6670229E2FF6C64C6125601
(bootloader) C7671A07B7034C492C85213FCCDC0DD3
(bootloader) A019ADDF0F220049A7404264BAE50571
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Joey\Unlock Tools>fastboot flash unlocktoken Unlock_code.bin
error: cannot load 'Unlock_code.bin'
Idea
I don't see the part where you got an email with the unlock code from HTC.
You have to submit that text to HTC, get an email with the file, put the file in the same folder as Fastboot, and then apply it.
Thanks for the reply,I got the code emailed and downloaded.I put it in the folder with the fastboot and got the error...I have no Idea what I did wrong.
Don't reboot your phone...also...male sure the phone is still in fastboot obviously.
Sent from my ADR6425LVW using XDA App
Thanks for your reply also.
I got it unlocked I had to change the folder name,I guess it wouldn't work cause unlock was in the folder name as soon as I changed it and entered the path it went though.. so I'm guessing that was the problem.
shooter_454 said:
Thanks for your reply also.
I got it unlocked I had to change the folder name,I guess it wouldn't work cause unlock was in the folder name as soon as I changed it and entered the path it went though.. so I'm guessing that was the problem.
Click to expand...
Click to collapse
Glad you got it figured out man!
Use fastboot for kernels, lol, I wish I had and almost bricked my phone.
S-Off
Unlocked bootloader
Had HD Rev 62 on it, but wiped EVERYTHING (data, cache, etc etc) in TWRP
Updated TWRP to 2.8.
Fastboot working, adb is not.
Fastboot sees and communicated with device just fine.
ADB does not list any devices, or errors. Just returns blank beneath List of connected Devices.
Cannot boot into anything since no OS is present. HD Rev latest version gets errors about "android-info.txt" and android-product.txt.
"error: update package has no android info.txt or android product.txt"
I don't care what OS is loaded on it because I am sending it to my mother. What is the fastest way to get it up and running again? I'm hoping to ignore fixing the ADB drivers on my Windows 8.1 machine (64-bit).
Can I just do a fastboot quick fix? If so, which RUU/Rom/Firmware/whatever. Anything that fastboot update update.zip will fix.
Thanks guys!
nik.the said:
S-Off
Unlocked bootloader
Had HD Rev 62 on it, but wiped EVERYTHING (data, cache, etc etc) in TWRP
Updated TWRP to 2.8.
Fastboot working, adb is not.
Fastboot sees and communicated with device just fine.
ADB does not list any devices, or errors. Just returns blank beneath List of connected Devices.
Cannot boot into anything since no OS is present. HD Rev latest version gets errors about "android-info.txt" and android-product.txt.
"error: update package has no android info.txt or android product.txt"
I don't care what OS is loaded on it because I am sending it to my mother. What is the fastest way to get it up and running again? I'm hoping to ignore fixing the ADB drivers on my Windows 8.1 machine (64-bit).
Can I just do a fastboot quick fix? If so, which RUU/Rom/Firmware/whatever. Anything that fastboot update update.zip will fix.
Thanks guys!
Click to expand...
Click to collapse
Post a fastboot getvar all (except for imei and serialno). If you are in bootloader/FASTBOOT USB and run the command adb devices it will not work. ADB works in OS if USB Debugging is enabled or in recovery.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34CW907053
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXX
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks @majmoz!
nik.the said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: removed
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXX
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111 change to T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks @majmoz!
Click to expand...
Click to collapse
This is the latest RUU 6.10.531.9 it will put you back at stock. Prior to running this, I would change the CID back to T-MOB010, I have had issues running TMO RUUs with SuperCID.
majmoz said:
This is the latest RUU 6.10.531.9 it will put you back at stock. Prior to running this, I would change the CID back to T-MOB010, I have had issues running TMO RUUs with SuperCID.
Click to expand...
Click to collapse
Which commands would I use to get this running? From bootloader/fastboot usb? Thanks again for the help @majmoz
nik.the said:
Which commands would I use to get this running? From bootloader/fastboot usb? Thanks again for the help @majmoz
Click to expand...
Click to collapse
Just follow the instructions in the Post. RUU.exe are run from Windows. Place the downloaded file in your fastboot/adb folder and double click it. Follow the on-screen instructions.
majmoz said:
Just follow the instructions in the Post. RUU.exe are run from Windows. Place the downloaded file in your fastboot/adb folder and double click it. Follow the on-screen instructions.
Click to expand...
Click to collapse
Nothing happens when I run the ruu. I get through to the agreement, accept, and then it disappears. Also, in the Sync manager, it's not showing my phone. I'm guessing this is a windows 8.1 problem?
nik.the said:
Nothing happens when I run the ruu. I get through to the agreement, accept, and then it disappears. Also, in the Sync manager, it's not showing my phone. I'm guessing this is a windows 8.1 problem?
Click to expand...
Click to collapse
Give this procedure a try!
Change USB ports (USB 2 is preferred) and cables if available
Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
Make sure you leave the adb and fastboot that you downloaded.
Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
A pop-up asking to install HTC Sync will appear, just ignore it or cancel it.
Make sure you set Fast Boot OFF in the Settings < Power on your phone, and USB Debugging enabled
Leave your phone ON and run the RUU set up.
I'm trying these things, but will it work on a phone that can't get to desktop? My phone isn't able to boot into android. It only can get into bootloader, recovery, and fastboot.
nik.the said:
I'm trying these things, but will it work on a phone that can't get to desktop? My phone isn't able to boot into android. It only can get into bootloader, recovery, and fastboot.
Click to expand...
Click to collapse
Put the phone in bootloader/FASTBOOT USB, then run the RUU.
majmoz said:
Give this procedure a try!
Change USB ports (USB 2 is preferred) and cables if available
Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
Make sure you leave the adb and fastboot that you downloaded.
Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
A pop-up asking to install HTC Sync will appear, just ignore it or cancel it.
Make sure you set Fast Boot OFF in the Settings < Power on your phone, and USB Debugging enabled
Leave your phone ON and run the RUU set up.
Click to expand...
Click to collapse
Hmm, frozen at 5% Checking header. RUU problem?
nik.the said:
Hmm, frozen at 5% Checking header. RUU problem?
Click to expand...
Click to collapse
Let's attack this differently. Let's flash the firmware 5.14.531.1 in fastboot. After it is finished, then run the RUU.
Download firmware, rename to fimware.zip and place in your fastboot folder.
Then put phone in bootloader/FASTBOOT USB then, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
majmoz said:
Let's attack this differently. Let's flash the firmware 5.14.531.1 in fastboot. After it is finished, then run the RUU.
Click to expand...
Click to collapse
It worked, then it restarted into QHSUSB_DLOAD. Hard bricked.
Any suggestions?
EDIT: Apparently Dexter's method can fix this, but I need the "appropriate" packages whatever those are :\.
nik.the said:
It worked, then it restarted into QHSUSB_DLOAD. Hard bricked.
Any suggestions?
EDIT: Apparently Dexter's method can fix this, but I need the "appropriate" packages whatever those are :\.
Click to expand...
Click to collapse
Here is his post and if you scroll down to Post #3 you will find the download.
Hi,
For no obvious reasons my phone went to bootloop yesterday night and I've been trying to fix it by different methods suggested in forums. But my phone does either of two things after changes/updates I make:
(1) Bootloop or (2) startup and stuck at HTC One beats audio screen
I have TWRP 2.8.0 installed. I can login to recovery.
Below is the phone getvar info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34SW906267
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
It's an ATT HTC One M7.
Problems, at this moment:
(1) Get get adb to connect to device
(2) I have twrp backups on my computer but don't know how to transfer them onto phone so that I can try restore command - backup files are not in zip format but a folder with files in it.
(3) when I was able to sideload a rom, I did flash ARHD 82.0 but that didn;t help.
PLEASE HELP !!:crying:
st167 said:
Hi,
For no obvious reasons my phone went to bootloop yesterday night and I've been trying to fix it by different methods suggested in forums. But my phone does either of two things after changes/updates I make:
(1) Bootloop or (2) startup and stuck at HTC One beats audio screen
I have TWRP 2.8.0 installed. I can login to recovery.
Below is the phone getvar info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
It's an ATT HTC One M7.
Problems, at this moment:
(1) Get get adb to connect to device
(2) I have twrp backups on my computer but don't know how to transfer them onto phone so that I can try restore command - backup files are not in zip format but a folder with files in it.
(3) when I was able to sideload a rom, I did flash ARHD 82.0 but that didn;t help.
PLEASE HELP !!:crying:
Click to expand...
Click to collapse
To install ARHD you should use TWRP 2.6.3.3 :good:
Or if you want to use your backup you can push it to the phone storage with adb, while in TWRP recovery.
Put the backup folder inside your fastboot folder on your pc and rename it something easy to type "nandroid" for example. Boot the device to TWRP recovery Home Screen. Connect usb cable. Then in the command window type
Code:
adb push nandroid /sdcard/TWRP/BACKUPS/DEVICESERIALNO./nandroid
Replace "DEVICESERIALNO." with your phone's Serial number in capitals
Wait for the push to complete, the command window may appear unresponsive at first just be patient when it's done restore the nandroid with TWRP
P.s you should edit your post and delete your Serial number. You don't want it displayed on the forums. FYI that's the serial number you need to use in the push command.
If you found my posts helpful, no need to say thanks. There's a button for that
Thank you again (already pressed thanks button )...I'll give it a try once I get home.
st167 said:
Thank you again (already pressed thanks button )...I'll give it a try once I get home.
Click to expand...
Click to collapse
Your welcome let me know how it goes, or if you need more help :good:
If you found my posts helpful, no need to say thanks. There's a button for that
So I was able to push backup to TWRP and restore. Yay!
But now the problem is I don't have any cell services....phone identity section shows no imei, no baseband, etc. I can see all these info from fastboot getvar. Any idea?
Oh and I keep getting error saying com.htc.dialer is not responding.
st167 said:
So I was able to push backup to TWRP and restore. Yay!
But now the problem is I don't have any cell services....phone identity section shows no imei, no baseband, etc. I can see all these info from fastboot getvar. Any idea?
Oh and I keep getting error saying com.htc.dialer is not responding.
Click to expand...
Click to collapse
Sorry to tell you that doesn't sound good. Unknown imei and Baseband is normally a hardware failure.
You can try to flash a firmware package or even better if possible an ruu but it rarely solves the issue. It's most likely the Antenna pin connector.
Do you have warranty on the device if so the best option is to return to Stock and send it for repair. :good:
If you found my posts helpful, no need to say thanks. There's a button for that
Danny201281 said:
Sorry to tell you that doesn't sound good. Unknown imei and Baseband is normally a hardware failure.
You can try to flash a firmware package or even better if possible an ruu but it rarely solves the issue. It's most likely the Antenna pin connector.
Do you have warranty on the device if so the best option is to return to Stock and send it for repair. :good:
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
I flashed the att firmware and then flashed rom again. Everything worked fine Phone started normally and I was able to make calls.
But my happiness ended soon...I tried to restart the phone after it finished downloading and updating apps and it died
Now phone doesn't power on, no led indicator or nothing when I plug the charger in. I tried diff combinations of power and vol button but no luck. So now I have an expensive paper-weight :crying:
Phone is out of warranty as it has been more than 365 days since purchase.
But thanks for your help.
WHen my phone did similar behavior I held down power + vol up (It will eventually vibrate and show the white HTC splash screen) THen continued to keep the buttons held down for almost 10 seconds, it rebooted itself again and finally allowed me into HBOOT and from there I was able to choose "Recovery" and boot into TWRP
If that doenst work, try the same with Power + Vol down. Or maybe it was Power + Home + Vol up, or Power + home + Vol down. Sorry, I dont exactly remember but one of those 4 combinations will get you into HBOOT or into recovery so that you can flash a new Rom
st167 said:
I flashed the att firmware and then flashed rom again. Everything worked fine Phone started normally and I was able to make calls.
But my happiness ended soon...I tried to restart the phone after it finished downloading and updating apps and it died
Now phone doesn't power on, no led indicator or nothing when I plug the charger in. I tried diff combinations of power and vol button but no luck. So now I have an expensive paper-weight :crying:
Phone is out of warranty as it has been more than 365 days since purchase.
But thanks for your help.
Click to expand...
Click to collapse
It's also worth checking on your warranty most come with 2years
Dear all
Huami has started locking their bootloaders (see the other thread) and, so far, has not offered any official way of unlocking the bootloaders to allow custom ROM flashing.
Due to the great work of our distinguished XDA developer Olivier (@kasakdor) :good: we have reverse engineered the unlock mechanism of the bootloader and can now offer to send you unlock codes for opening your bootloader again and flashing other software.
Please read and understand the following terms and conditions:
You unlock your bootloader on your own risk. Nobody else takes any responsibility on your actions and any possible consequences.
We are therefore NOT responsible for any bricked devices, invalid warranty claims, heart attacks or world wars.
Huami / Xiaomi will consider your warranty void. Do not contact Huami / Xiaomi or your dealer if anything goes wrong after you have unlocked your watch. Only YOU are responsible for the outcome of any modification you do.
This service is for personal usage only. Any identified commercial activities will be blocked.
A maximum of three unlock codes can be requested by each individual.
This service is provided free of charge. You accept that you cannot claim any charges towards us, if you are unhappy with the service or if the service does not work for you.
If ever Huami offers an official unlock service, we will stop our service. The goal is not to be in competition with Huami here, but only to provide something as long as they are not able to.
INSTRUCTIONS
You need to have fastboot installed and working correctly on your PC. You need to enter fastboot mode and get some information from your watch. Then go to the website https://unlockamazfit.com and enter your information. We will check your data and send you the unlock code. This can take 1-2 days typically.
We need to do the manual checking as we do NOT want to support any abuse (e.g. pirate companies reflashing watches).
If you have questions or feedback, please feel free to post here. Please also report briefly back, if the unlocking was successful.
Enjoy custom ROMs!
Before continue, please read the following:
[*] The approval process is manual, and it might take more than stated, have patience. If no unlock received within a week, contact by PM.
[*] Please keep track of the email used for the request, check in your trash and in your spam folder!
[*] DO NOT HAMMER THE SERVICE - if a request is made more than 3 times, it goes into a more detailed inspection and it takes more time for you to approve. No need in requesting 7 times.
[*] In case of an error during the filling of the form, stop and contact by PM - more retries will lock your SN/email.
[*] Once you've UNLOCKED YOUR SERIAL NUMBER - there is no need in unlocking it again after an update. if the watch gets locked, use the same unlock key.
[*] If additional help needed, do not hesitate in contacting in ENGLISH with all relevant information only: name, SN, email used.
[*] 2nd hand watches - unlock will be provided according to the original owner of the unit, make sure to have the details of the person you bought the watch from.
A detailed How to - please read before attempting, and then perform the steps.This process is not intended for the week of heart, so embrace yourself, winter is coming, and its going to unlock your bootloader! (excited kitten noises)
prerequisites:
1. ADB/fastboot knowledge, we're assuming that you do know how to enter your watch into fastboot, and how to obtain all the relevant information needed for a successful unlock.
2. Installed and functional Google ADB drivers - can be obtained from here - https://forum.xda-developers.com/showthread.php?t=2588979 , do not forget to install them as Administrator.
3. Additional microUSB cable - as seen, sometimes the original cable provided by Huami is not co-operative, so prepare another one.
4. Make sure that your watch has at least 60% of juice.
use this tool - https://toolaio.tk/
is has instant unlock built in.
Now ... for the fun part.
1. Reboot your watch into fastboot mode by
Code:
adb shell reboot bootloader
Make sure that you can see your watch in the Device Manager and it has its drivers installed!
2. while your watch is in the fastboot mode, type
Code:
fastboot getvar all
this will provide you with the following information
Code:
c:\adb>fastboot getvar all
< waiting for device >
(bootloader) version-bootloader: [B][COLOR="red"]U-Boot 2013.07-00096-gf3b140c[/COLOR][/B]
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: [B][COLOR="Red"]0123456789abcdef[/COLOR][/B]
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: no
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
all:
finished. total time: 0.280s
Besides the marked in bold, you will need the watch OS version, can be obtained from the settings in the watch -> tick the cog and go to the about section.
It is advised to double check the serial number provided by the fastboot with the one imprinted on the back of the watch, to make sure that its the correct one.
US/Global watches - 1612/1619/1811- the serial must be provided in a continuous format: 12345123456789
CN watches - 1602/1609/1801 - the serial must be provided in a divided with a / format: 12345/12345678
Very good!
I'll try tonight!
C:\adb>fastboot getvar all
< waiting for device >
Nothing more, any idead how to solve problem ?
Gruchi said:
C:\adb>fastboot getvar all
< waiting for device >
Nothing more, any idead how to solve problem ?
Click to expand...
Click to collapse
your watch needs to be in fastboot.
please read the description again.
Code:
adb shell reboot bootloader
Click to expand...
Click to collapse
it is in fastboot mode
C:\Users\Gruchi\Desktop>cd adb
C:\Users\Gruchi\Desktop\adb>adb shell reboot bootloader
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
C:\Users\Gruchi\Desktop\adb>fastboot getvar all
< waiting for any device >
please post a screenshot of your device manager.
Try to use different cable, sometimes it should be problem.
Or other ADB drivers version...
Gruchi said:
it is in fastboot mode
C:\Users\Gruchi\Desktop>cd adb
C:\Users\Gruchi\Desktop\adb>adb shell reboot bootloader
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
C:\Users\Gruchi\Desktop\adb>fastboot getvar all
< waiting for any device >
Click to expand...
Click to collapse
I got the code but I unlocked the smartwatch ... ... I tried several times but after entering the string by unlocking it tells me failed
Worked perfect!
MarcolinoV112 said:
I got the code but I unlocked the smartwatch ... ... I tried several times but after entering the string by unlocking it tells me failed
Click to expand...
Click to collapse
Send me a PM with a screenshot of fastboot and the command that failed.
Also for me error:
FAILED (remote: ED)
finished. total time: 0.078s
Worked just like the tutorial says. Many thanks !!!!
OS ver: 1.3.3a
US version
fastboot getvar unlocked
unlocked: yes
finished. total time: 0.033s
im geting always invalid serial number... and is the same on watch..
superino said:
Also for me error:
FAILED (remote: ED)
finished. total time: 0.078s
Click to expand...
Click to collapse
Hmm, I see that you and MarcolinoV112 both have OS 1.2.29i. Maybe Huami changed the mechanism already in that OS version.
jardaz said:
im geting always invalid serial number... and is the same on watch..
Click to expand...
Click to collapse
My bad i forget the / waiting for the email
Bootloader unlocked successfully! Many thanks!
(1.3.3a US)
Work many thanks 1.3.3a
FAILED (remote: ED)
finished. total time: 0.068s
With 1.3.3a :'(
Waiting for the unlock code in my email.
hi
I hope you have a great day.
I have a problem with my HTC d728w phone, after months I turned on the phone and the phone just boot into fastboot mode.
I select the "boot to bootloader" or "reboot" option but the phone comes back to fastboot mode.
I tried many ways, like: download the Flashman program to flash the ROM of the device and get the Fail message.
I tried the RUU and ADB and I get Unknows command for every command. just I can see the limited information of the device with "fastboot Getvar all".
so what I should do ? just I saw whole google links and I m so confused with this problem.
"Sorry for bad English"
(bootloader) battery-status: good
(bootloader) max-download-size: 0x8000000
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.005s