Android App Review: Manage Your Connections Automagically – XDA TV

Material Design is all the buzz in the Android world right now. … more

Official TWRP Recovery Lands on Micromax Canvas Magnus

With the recent release of Android One, Micromax and MediaTek released fully buildable … more

Update Overload: SuperSU Heavily Updated

There are apps and apps out there. Very few can reach the level of popularity required to stay at … more

Lollipop Leak Available for the Sprint Galaxy S5

Since the Android 5.0Lollipop’s official release not too long ago, we’ve seen … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Omate Truesmart "USB Device Not Recognized"

OP shadowninja23

10th February 2014, 04:45 AM   |  #1  
OP Junior Member
Flag Atlanta
Thanks Meter: 1
 
29 posts
Join Date:Joined: Feb 2010
More
Hi everyone, so I have a 1GB/8GB Omate Truesmart that has been awesome. After having the Imperium Operative ROM on it and realizing the sensors were not working, I decided to try and revert back to the stock firmware. However, that's where the trouble started. My cradle wasn't working properly during the process and stopped in the middle of it, and now I can't even boot my watch on (unless there's some alternative way). On top of that, anytime I try to connect it to any of my USB ports, it keeps saying on my Windows 7 laptop that the USB device is not recognized, and I tried uninstalling and reinstalling the drivers again.

So, if anyone can please help me and guide me in "unbricking" the watch and just being able to have my laptop recognize it so I can actually do the stock firmware process, I'd be really grateful. Thanks a lot!
10th February 2014, 05:58 AM   |  #2  
Senior Member
Thanks Meter: 516
 
1,708 posts
Join Date:Joined: Nov 2008
You used Sp flash tool correct? I'd suggest reading the unbricking guide first but answer these first:

What color was the progress bar when it stopped?
Have you tried a different port?
Have you pulled the battery yet?

Sent from my GT-P5110 using Tapatalk 2
10th February 2014, 01:52 PM   |  #3  
OP Junior Member
Flag Atlanta
Thanks Meter: 1
 
29 posts
Join Date:Joined: Feb 2010
More
Smile Actually fixed it!
Quote:
Originally Posted by kuronosan

You used Sp flash tool correct? I'd suggest reading the unbricking guide first but answer these first:

What color was the progress bar when it stopped?
Have you tried a different port?
Have you pulled the battery yet?

Sent from my GT-P5110 using Tapatalk 2


Hey kurunosan, so I did follow the unbricking guide exactly, but because my cradle is a little bit finicky (the microUSB has to be plugged into it in an exact position for it to be read by the laptop), it had messed up during the unbricking process and therefore, caused it to be "bricked". To answer your questions though, the color of the progress bar was yellow, I tried all the different ports around my laptop, as well as my work laptop. And I wasn't able to pull the battery because I haven't been able to unscrew the back yet (I blame those crazy small screws lol).


BUT, I was finally able to fix the drivers issue and my watch was recognized by my laptop finally. If I have time later in the next day or two, I'll try and make a guide about it if something like that happens to anyone. Or if anyone is curious or has had it happen to them, you can feel free to PM me.

I'm just glad that my TrueSmart is finally functional again!
10th February 2014, 08:49 PM   |  #4  
Senior Member
Thanks Meter: 516
 
1,708 posts
Join Date:Joined: Nov 2008
Quote:
Originally Posted by shadowninja23

Hey kurunosan, so I did follow the unbricking guide exactly, but because my cradle is a little bit finicky (the microUSB has to be plugged into it in an exact position for it to be read by the laptop), it had messed up during the unbricking process and therefore, caused it to be "bricked". To answer your questions though, the color of the progress bar was yellow, I tried all the different ports around my laptop, as well as my work laptop. And I wasn't able to pull the battery because I haven't been able to unscrew the back yet (I blame those crazy small screws lol).


BUT, I was finally able to fix the drivers issue and my watch was recognized by my laptop finally. If I have time later in the next day or two, I'll try and make a guide about it if something like that happens to anyone. Or if anyone is curious or has had it happen to them, you can feel free to PM me.

I'm just glad that my TrueSmart is finally functional again!

The good news for you is that because it was only yellow, your watch was just stuck in preloader mode and you hadn't fully bricked it.

If you disconnected it while the progress bar was purple, you'd be in some serious trouble.

I'm very familiar with preloader and it's such a pain in the ass when the drivers do gymnastics and switch ports or flat out don't work.
10th February 2014, 09:57 PM   |  #5  
OP Junior Member
Flag Atlanta
Thanks Meter: 1
 
29 posts
Join Date:Joined: Feb 2010
More
Preloader
Quote:
Originally Posted by kuronosan

The good news for you is that because it was only yellow, your watch was just stuck in preloader mode and you hadn't fully bricked it.

If you disconnected it while the progress bar was purple, you'd be in some serious trouble.

I'm very familiar with preloader and it's such a pain in the ass when the drivers do gymnastics and switch ports or flat out don't work.


Oh gotcha, did not know that about the preloader. Well, good thing that was the only case then!
13th February 2014, 01:31 AM   |  #6  
Junior Member
Flag Northallerton
Thanks Meter: 1
 
3 posts
Join Date:Joined: May 2011
More
Unhappy
I have had a similar experience with my Truesmart. I originally tried to apply Lokifish's Root + Enhanced Security patch. This unfortunately failed for some reason and resulted in me not having root or any USB functionaility.

So I went through the process of putting the watch back to stock. I followed the process to the letter, but something went wrong during the process and it ended up with SPTools giving up (looking at the logs it looks like it lost USB connectivity - attached). Now the watch seems to be bricked. I have attempted the process again but SPTools is not detecting anything.

Any help or advice would be very much appreciated....I am a very sad bunny at the moment

I would prefer to not have to remove the battery (for obvious reasons), but will do if there is no other way round it.
Attached Files
File Type: txt QT_FLASH_TOOL.txt - [Click for QR Code] (31.4 KB, 57 views)
13th February 2014, 01:51 AM   |  #7  
Lokifish Marz's Avatar
Recognized Contributor / Recognized Developer
Flag Olympus Mons, Mars
Thanks Meter: 3,282
 
2,891 posts
Join Date:Joined: Mar 2011
Donate to Me
More
Quote:
Originally Posted by Beta_Tester666

I have had a similar experience with my Truesmart. I originally tried to apply Lokifish's Root + Enhanced Security patch. This unfortunately failed for some reason and resulted in me not having root or any USB functionaility.

So I went through the process of putting the watch back to stock. I followed the process to the letter, but something went wrong during the process and it ended up with SPTools giving up (looking at the logs it looks like it lost USB connectivity - attached). Now the watch seems to be bricked. I have attempted the process again but SPTools is not detecting anything.

Any help or advice would be very much appreciated....I am a very sad bunny at the moment

I would prefer to not have to remove the battery (for obvious reasons), but will do if there is no other way round it.

The patch will tell you if there's an error. It will show the command with the word "failed".


Regarding SPTools attempt to return to stock. In looking at the log it was continuously connecting and disconnecting which usually demotes either a driver,dock or USB issue. It is most likely in a bootloader mode but locked up. I suggest you leave the TS alone for a few hours or possibly overnight and attempt to flash it again.

Unfortunately you have given my very little to go on so other than general fixes there's not much I can tell you. In the future if you run into any issues flashing anything or running scripts it is best to post in that projects support thread and wait for help.
13th February 2014, 01:59 AM   |  #8  
Senior Member
Thanks Meter: 516
 
1,708 posts
Join Date:Joined: Nov 2008
The log clearly shows multiple disconnects, probably because of a bad query. I suggest the same thing Loki did.

Sent from my Galaxy Nexus using Tapatalk 2

Post Reply Subscribe to Thread

Tags
not booting, not recognized, usb
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes