yashsingh1/xdaforums huggingface dataset:
[T-Mobile HTC One (M7)] Dead0ne:
I have the phone up and running finally. I ended up with the latest TMO RUU on my phone. I am still unable to get ADB to see the phone and would like to know what I am doing wrong., so if you could tell me what mode or state the phone needs to be in for ADB to work I would appreciate it. I don't see the USB debugging option anymore with the new ROM. I don't know if it matters but when I boot into recovery I still get the red triangle with the exclamation point. Thanks again!

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.57.0000

(bootloader) version-baseband: 4T.28.3218.04

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 6.10.531.9

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0713000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 4302mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-6d8a0b9b

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!
[T-Mobile HTC One (M7)] majmoz:
You have to enable USB Debugging in Developer's Option: http://htc-one.wonderhowto.com/how-to/enable-usb-debugging-your-htc-one-0151177/

ADB will work if the phone is in the OS/Android and USB Debugging is enabled. ADB also works when the phone is in Recovery Mode with a custom recovery.

You do not have a custom recovery installed if you see the red triangle, that is stock recovery. You will have to flash the custom recovery in bootloader/FASTBOOT USB:

fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
[T-Mobile HTC One (M7)] Angelus96:
Same issue but version-main is weird...

Hi, I have the same issue, and tried different RUU's and firmware. Even ROMs, but nothing seems to work. The funny thing is that the version-main, from the fastboot getvar all command, has rare signs...

fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.57.0000

(bootloader) version-baseband: 4T.28.3218.04

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 6«10.531.=

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0713000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 4045mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-6d8a0b9b

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

So, mi question is.. this steps will work for my phone too, or I have to use another firmware and RUU... or haw can i recover my HTC One, and why has this funny characters in the version-main value....

When turn on my phone, I get the HTC One logo in green letters, and white background.. and thats all...

When I tried to turn on in fastboot mode, it turns on.. and changes has fastboot usb, but always I tried to install something, return the "verification failed" message.

Please Help!

Ps. [MENTION=6124281]Dead0ne[/MENTION] can you please share the TMO RUU you use to recover your phone?
[T-Mobile HTC One (M7)] majmoz:
You can try this RUU 6.10.531.09 it looks to match you have posted.

You will need to lock your bootloader if it is not already locked. You can lock it with the following command:

fastboot oem lock

Sorry I don't know what could have caused the strange characters.
[T-Mobile HTC One (M7)] Angelus96:
Thanks [MENTION=240330]maj[/MENTION]noz, I`ll try with that one.

Just one doubt... Should I flash the firmware or I just run the ruu...?

Thanks!
[T-Mobile HTC One (M7)] majmoz:
If you have the firmware you can try to flash it and see if it solves your issue, if not then try the RUU. And you can find the updated RUU 6.10.531.10 here.
[T-Mobile HTC One (M7)] Angelus96:
Hey [MENTION=3070392]majmoz[/MENTION], I'be been busy... so I left this issue aside for a while....

I recently tried with this RUU in my PC: RUU_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421697_signed_2.exe

It suppose to be the latest update from HTC to One T-mobile devices.

So i tried, and it run smoothly. It finish ok, and it says that the phone was updated.

But again, the phone stays under the HTC Logo.

I enter to bootloader and select recovery mode, it run, but shows this message:

E:missing bitmap oem_unlock_bg

E:missing bitmap oem_unlock_bg_yes

E:missing bitmap oem_unlock_bg_no

(code -l)

E:missing bitmap icon_ruu

(code -l)

E: failed to mount /data (invalid argument).. try emmc mount handle_cota_install: Can't mount /data

This is what the phone shows in bootloader:

*** RELOCKED ***

M7_UL PVT SHIP S-ON RH

HBOOT-1.61.0000

RADIO-4T.35.3218.16

OpenDSP-v35.120.274.0718

OS-7.18.531.2

eMMC-boot 2048MB

And this is the fastboot getvar all:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.61.0000

(bootloader) version-baseband: 4T.35.3218.16

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 7.18.531.2

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: XXXXXXXXXXX #Im not showing this

(bootloader) imei: xxxxxxxxxxxxxxx #Im not showing this

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0713000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 4076mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-331585dd

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

Can you help? What should I do next?

I've seen that [MENTION=848723]hasoon2000[/MENTION], [MENTION=1363323]vomer[/MENTION], [MENTION=4752144]squabbi[/MENTION], @clsA and [MENTION=2605798]nkk71[/MENTION], have a lot of experience with this phone, so if you don't mind I extend my request to them, cause I'm kind if desperate with this. I'm believing that is probably a lost cause.. but i don't want to give up.

I'm kind stuck and I'm newbie.. so guys, Any help is very much appreciated, and I'm sorry if there is a problem with making a reference to you.

Thanks in advance. Regards!
[T-Mobile HTC One (M7)] nkk71:
doesnt sound very nice :(

try running RUU again (though i would prefer a "htc_fastboot oem rebootRUU" flash, but that involves a few things, so maybe a waste for now)

anyway, run RUU, make sure it succeeds (you can also pull the ruu log from "C:\ruu_log" folder), then boot up, if it hangs, force reboot to bootloader, and:

fastboot oem last_dmesg

and post that log (increase your command prompt buffer size if necessary)

EDIT: question: is/was/were you, encrypting your device??

.
[T-Mobile HTC One (M7)] nkk71:
you should increase the buffer size on your command prompt, the output, doesnt show the initial last_dmesg output which would show any emmc errors

Question: do you have "active cmdline overflow (xxxx bytes)" showing in bootloader? (towards the bottom)
[T-Mobile HTC One (M7)] Angelus96:
Hi [MENTION=4513061]cschmitt[/MENTION], I checked this post, were you publish a generic misc partition. I dont know if it will help in my case, but for what I've seen, the problem it's kind of similar.

http://xdaforums.com/showthread.php?t=2739126

I dont know if you some time to check my problem, any suggestion its very welcome. Until now [MENTION=2605798]nkk71[/MENTION] is helping me. Either way, i dont wont to give up on my phone so I'm looking for every help I can. Thanks in advance.
[T-Mobile HTC One (M7)] Angelus96:
Well, I've unlocked the phone by HTCdev, and flash the recovery with no BCB:

Then reboot in bootloader, and access to recovery. and I'm receiving error in mounting the /data and /system partition.

E: Could not mount /data and unable to find crypto footer

E: Unable to mount '/data'

E: Unable to recreate /data/media folder

Updating partition details...

E: Unable to mount '/data'

E: Unable to mount '/system'

E: Unable to mount internal storage

E: Unable to mount /data/media during GUI startup

E:: Unable to moount /data/media/TWRP/.twrps when trying to read settings file

E: Unable to find storage partition to mount to USB

And that the step i still can't get passed. I don't know what to do to recover all the filesystem...

Any ideas?
[T-Mobile HTC One (M7)] nkk71:
Not really (and that output doesnt look nice at all),

only reason I thought perhaps something is messed up in your misc partition, is because in your first post version-main (which is stored in misc partition) had strange characters in it.

Try flashing the generic misc partition, then relock and run RUU one last time, if that doesnt fix it, then I think it's a goner, sorry.
[T-Mobile HTC One (M7)] Angelus96:
Hey [MENTION=2605798]nkk71[/MENTION], thank you for your quick response..

Yesterday i tried to wipe the partitions... all of them /system, dalvik cache, cache and data), through the TWRP with no BCB.. And the wipe went ok, and after that, the phone recognize all partitions... ... the only thing it's that the "internal storage" shows recognize only 619 MB. SO I can`t find the 16 GB that should have.

Another thing... is that, after rebooting, again, can not run the recovery.

So I have to fla**** again.

If I flash a kernel stock would help in any way?.. Im not really sure... probably to try a downgrade of kernel... or something..

Regards
[T-Mobile HTC One (M7)] nkk71:
You could have achieved the same using TWRP->Wipe->Format Data (that does a real format of the data partition)

sdcard is just a symlink to /data/media/0/ it would get created upon reboot

^^ typical sign that the board is messed up, sorry
[T-Mobile HTC One (M7)] Angelus96:
Hey [MENTION=2605798]nkk71[/MENTION], I'm still checking this... so.. after the last review, I found this...

I've been doing test-error kind research based and following this post from [MENTION=6119185]Mike1986[/MENTION]:

http://android-revolution-hd.blogspot.mx/2013/10/fix-data-htc-one.html

And the command to format the /dev/block/mmcblk0p37...

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37

Goes OK... but the inodes and blocks are less than it should.... SO I check with the e2fsck command:

~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

12 inodes used (0.03%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 4
5256 blocks used (3.21%)
0 bad blocks
0 large files

0 regular files
3 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
3 files

This, it's similar to this post:

http://xdaforums.com/showthread.php?t=2504542&page=16

And even following the instructions there, the problems persist. So i have enter to the adb shell, and try to find what it's wrong. Check fstab, mtab, mount points, emmc blocks, etc... so there is a lot of differences.. So I thing the problem is this:

# ←[6n fdisk -l /dev/block/mmcblk0p37
[B]fdisk -l /dev/block/mmcblk0p37[/B]

Disk /dev/block/mmcblk0p37: 671 MB, 671088128 bytes
4 heads, 16 sectors/track, 20479 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

[B]Disk /dev/block/mmcblk0p37 doesn't contain a valid partition table[/B]

So I go deeper and found that there wasn't any partition table:

[B]fdisk /dev/block/mmcblk0p37[/B]
Command (m for help): ←[6n [B]p[/B] <<<<<-------- p print the partition table
p

Disk /dev/block/mmcblk0p37: 671 MB, 671088128 bytes
4 heads, 16 sectors/track, 20479 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System

It shows nothing..... so going a bit more deeper, found that there is unallocated space:

Then i tried to verify the partition:

Command (m for help): ←[6n [B]v [/B] <<<<<------ v verify the partition table
v
[B]1310655 unallocated sectors[/B]

So, I think that its a problem, but don't know how to fix it, and i can't find the way with mkfs.ext4 to do so. I think probably by deleting partition and creating again with FDISK or PARTED, but really not sure about steps and commands to do so... Ind don't want to mess around.... (more) :confused:

Note: One last important thing to say is that the 619MB are recognize by windows when I have the phone in recovery mode.. it show me the storage at "My PC".
[Galaxy S II Q&A, Help & Troubleshooting] amir berkani:
Hi to all

can someone give me (neat rom 5.7) download link for i9100 because i can't find it in anywhere

or can someone upload it for me please
[Galaxy S II Q&A, Help & Troubleshooting] amir berkani:
can someone help me :crying: :crying:
[Galaxy S II Q&A, Help & Troubleshooting] amir berkani:
please ??
[Galaxy S II Q&A, Help & Troubleshooting] amir berkani:
Hi guys
[Galaxy S II Q&A, Help & Troubleshooting] amir berkani:
can someone help me
[Wear OS Q&A, Help & Troubleshooting] AstroDigital:
You transfer music to your Smartwatch but no Smartwatch as a speaker, mine is Gear Live.

So how can you listen to what you transferred to the watch?

Do you need a Bluetooth headset? Can you even pair a Bluetooth headset to a Gear Live?
[Wear OS Q&A, Help & Troubleshooting] dlbarron:
With the latest Android Wear you can pair a bluetooth device to your watch to listen to music. Any good bluetooth headset should work.
[Wear OS Q&A, Help & Troubleshooting] Mochs:
bluetooth 2.0 or only 4.0 Headsets

I have a bluetooth 2.0 standard bluetooth headset. When I connect it its instantly marked as disconnected. Is this a case of Bluetooth 2.0?

Any Help?

Thanks.
[Nexus 6  General] jejehtc:
Come talk about this thread on the output of GOOGLE NEXUS 6

- Availability in different operators French.

- The price on the Play store and among operators

- And any other topic around this splendid smartphone

NO DISCUTION ON ROOT OR ANY OTHER CUSTOMIZATION YOUR SMARTPHONE
[XDA Assist] VAMPIRERFREAK:
was wondering if any one knew how to unbrick a blu 6.0 hd cellphone i found an app to root it but then for some reason a couple of weeks later it bricked any help would be appreciated
[XDA Assist] prboy1969:
I'm sorry at this time there is no specific forum for your device. a quick search also revealed no good information. I would suggest posting up in the link below. That way other members who have the same device may chime in, and be better able to assist you. Best of luck.

Android Q&A, Help & Troubleshooting
[Galaxy Note 4 Themes and Apps] Wooba99:
On my note 2 I used to play this version of Sudoku

https://play.google.com/store/apps/...medium=appbrain_web&utm_campaign=appbrain_web

Unfortunately it doesn't work with the Note 4 and it's not been updated in ages. Can anyone recommend another one that works well?
[Galaxy Note 4 Themes and Apps] Pinnacle74:
https://play.google.com/store/apps/details?id=com.unlimitedpocketsoftware.handwritesudoku perhaps?

I have not tried it myself yet. :)
[Galaxy Note 4 Themes and Apps] Wooba99:
Thanks, but I tried that one and I didn't like it at all. That's why I decided to come ask here rather than go through a bunch of others :)
[Galaxy Note 4 Themes and Apps] chautruong:
What did u mean "best"?

Functions or ease to use?
[Galaxy Note 4 Themes and Apps] xrayA4T:
I like https://play.google.com/store/apps/details?id=cz.romario.opensudoku It's free and open source. Hasn't been updated in ages but works just fine. Your can create your own puzzles. I have hundreds if you need
[Galaxy Note 4 Themes and Apps] sudokuyou:
Try SudokuYou

SudokuYou supports a nice Drag&Drop: You can simply drag a Number from a Cell to an other.

To find it on GooglePlay simply Search "SudokuYou" - The Green/White Logo. :)
[X 2014 General] mrvirginia:
Here are the partition mount points

DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p12
boot -> /dev/block/mmcblk0p32
cache -> /dev/block/mmcblk0p36
cid -> /dev/block/mmcblk0p25
clogo -> /dev/block/mmcblk0p29
customize -> /dev/block/mmcblk0p35
dhob -> /dev/block/mmcblk0p20
factorytune1 -> /dev/block/mmcblk0p10
factorytune2 -> /dev/block/mmcblk0p34
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
kpan -> /dev/block/mmcblk0p31
logo -> /dev/block/mmcblk0p28
logs -> /dev/block/mmcblk0p9
misc -> /dev/block/mmcblk0p27
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
padA -> /dev/block/mmcblk0p11
padB -> /dev/block/mmcblk0p16
pds -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p30
recovery -> /dev/block/mmcblk0p33
rpm -> /dev/block/mmcblk0p5
rpmBackup -> /dev/block/mmcblk0p13
sbl1 -> /dev/block/mmcblk0p2
sdi -> /dev/block/mmcblk0p7
sp -> /dev/block/mmcblk0p24
ssd -> /dev/block/mmcblk0p23
system -> /dev/block/mmcblk0p37
tz -> /dev/block/mmcblk0p6
tzBackup -> /dev/block/mmcblk0p14
userdata -> /dev/block/mmcblk0p38
utags -> /dev/block/mmcblk0p8
utagsBackup -> /dev/block/mmcblk0p15
[X 2014 General] SamsonIncorporated:
Thank you so much for this! I am interested in themeing the stock ROM, and I'm using ArchiKitchen to help in the deodexing(last time i tried any themeing, it was on JB and the only way i knew how to theme was on a deodexed ROM). In the process of recreating the ROM, ArchiKitchen asks for the kernel path since it doesn't seem to be specified in the stock system.img. Would the system path be the correct path to use or is there one that I missed? Any help is appreciated!

EDIT:

Upon selecting the system path, ArchiKitchen responded with this:

The final effect is:

=-=-=-=-=-=-=-=-=

package_extract_file("boot.img", "/dev/block/mmcblk0p37");

I guessing that this means i should specify the boot path instead. I won't make a move until i know for sure, though.
[One (M8) Q&A, Help & Troubleshooting] felipaopl:
Gentleman (and why not, ladies):

Installed yesterday a stock GPE 4.4.3 version on my M8. I'm S-ON, stock recovery and rooted.

Just received the info for the 4.4.4 OTA update. My CID is also already set to GOOGL001.

Is it risky to just let it do it's thing? I know that I'll lose root, but is there a problem besides that? Will the process complete sucessfully?
[One (M8) Q&A, Help & Troubleshooting] felipaopl:
Anyone?
[One (M8) Q&A, Help & Troubleshooting] LNJ:
Why don't you just flash the pre-rooted 4.4.4 GPE ruu?

HTC One M8
[One (M8) Q&A, Help & Troubleshooting] felipaopl:
I believe that S-OFF is needed and Firewater didn't worked with my phone.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
You think s-off is needed for OTA? Why would you think that?

As long as your are stock ROM and stock recovery, the OTA install will be fine.
[One (M8) Q&A, Help & Troubleshooting] noone606:
wOUld this be the case if my cid was telst001

stuck on 3.18 firmware cant get s-off and unsure if i can change cid without it

c
[One (M8) Q&A, Help & Troubleshooting] xunholyx:
You can't change CID without it. Have you tried Sunshine S-Off? Firewater doesn't work anymore.
[One (M8) Q&A, Help & Troubleshooting] noone606:
Tried sunshine but need to go to a more stock rom i guess, on sinless gpe at the moment its 4.4.4 and working fine?

Not as good a battery life as i had before on viper but new viper will install but no wifi :(
[One (M8) Q&A, Help & Troubleshooting] mrew42:
You need the latest firmware with the new 4.4.4 roms. Read the viper site very carefully and it explains why
[Nexus 6  General] idonthavename.7:
http://www.droid-life.com/2014/10/31/nexus-6-working-on-verizon-out-of-the-box/

If it has been posted already please delete.
[Nexus 6  General] jt3:
Keep in mind that this was a review unit, likely from Motorola (or possibly Google). CDMA carriers (Verizon, Sprint, US Cellular, etc.) tend to whitelist IMEI numbers that are sent to them, along with those sent directly from the manufacturer (warranty replacements, etc.), and other contractual partners (such as Google Play). (The manufacturer and contractual partners are responsible for submitting the IMEI numbers to the carrier.) Thus, when an IMEI comes in from another carrier, they know it wasn't sold by them, directly from the manufacturer, or their contractual partners, meaning it was likely sold by a competing carrier, and can deny activation.

To be clear, the Nexus 6 may or may not work this way. We simply don't know. However, there has been enough historical evidence to be wary. GSM carriers don't tend to whitelist IMEI numbers like this, so usually aren't affected.

As a review unit, it's certainly a good sign that Verizon supports it out of the box, but ultimately it doesn't PROVE that buying one from, say, T-Mobile and trying to activate it with Verizon (or any other CDMA carrier) will similarly work
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] theLemming2:
Hello,

Each time I do a hard reset on my device, I have to complete this tutorial (at start-up) where I have to 'cut' an appointment and 'paste' it . Is there some tweak to avoid this ?

I'm a tester of mobile software, so the hard reset story occurs frequently.

I have a HP IPAQ rw6815 (Windows Mobile 5.1.195 - Build 14989.2.6.0)

Thanx !
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] vijay555:
Thanks to Mamaich for pointing this out recently:

http://jritmeijer.spaces.live.com/blog/cns!8A48A27460FB898A!210.entry

V
[ONE Q&A, Help & Troubleshooting] renolegend:
I recently flashed MIUI, however I have been trying to get back to CM. I seemed to have tried everything and dove and read all aspects of this forum.

Here is my situation:

Bootloader is now locked.

Custom recovery disappeared, hence I just have stock.

Tamper flag true, false, false

Can access fastboot

I tried to manually boot TWRP to wipe and sideload with no success, continues to say failed then takes me to stock recovery.

I have no freaking idea what to do. Long time reader, enthusiast, rom flashing user, however...this is the first time I am stuck! PLEASE HELP!
[ONE Q&A, Help & Troubleshooting] C13v3r0n3:
http://xdaforums.com/showthread.php?t=2788632
[ONE Q&A, Help & Troubleshooting] renolegend:
I have been to this thread. I fastboot oem unlock. I have read it from start to finish.
[ONE Q&A, Help & Troubleshooting] Heisenberg:
You fastboot oem unlock. What does that mean? You unlocked it? It failed? You need to be more detailed and specific.

Transmitted via Bacon
[Moto 360] :
[Q&A] [SCRIPT][BATCH][TOOL]Motorola Moto 360 Super Tool bootloader unlock, root, & R

Q&A for [SCRIPT][BATCH][TOOL]Motorola Moto 360 Super Tool bootloader unlock, root, & Restore

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [SCRIPT][BATCH][TOOL]Motorola Moto 360 Super Tool bootloader unlock, root, & Restore. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Moto 360] MyMiracle:
Can not download the Super Tool and moto drivers.

Seems the links are down.

Can you fix that?

Thanks.
[Moto 360] MatthewB92:
I enabled ADB debuggin but nothing popped up on my phone. my watch said am I sure and I hit yes. I'm doing something wrong....