yashsingh1/xdaforums huggingface dataset:
[Other SmartWatches] Apokriphos:
I tried some things, but ultimately know very little about what I'm doing. Would love to hear experts chime in.

Steps to Backup your Stock Rom, and (Hopefully) generate a Touch based CW Recovery for the Inwatch Z.

Search XDA for Get your own CWM recovery for newer devices and dont beg anywhere - 2 simple steps.

Downloaded SDCard Backup and ran it. Failed the first time. Downloaded console, typed 'su', then typed 'mount -o rw mount /system' in console. Don't type the 's.

Ran Gscript lite (included in the SDCard Backup file) and loaded the file "back_mt657x.sh". Ran again. Worked, and generated a 1.31 Gig file now sitting on desktop. Afterwards dont forget to run console again and type mount -o ro mount /system

Recovery.img is 6144 kb.

Visited builder.clockworkmod.com, placed Recovery.img at top, selected touch, and waited.

Apparently the website is down. Permanently? No idea. :mad:

Well, now I have a stock rom generated for my Inwatch Z I believe. Just need to figure out how to compile it into a usable form...
[Other SmartWatches] Parcaetron:
Somebody suggested lowering the font size to fix my problem, but I can't find that post any more. Whoever you are, thank you, kind stranger - I successfully factory reset the phone.

Now, new problem! I can't get bluetooth tethering working, possibly because of the known Bluetooth tethering bug in Kitkat. Any suggestions?
[Other SmartWatches] vscmaster:
Here is a good article how to make the firmware backup: http://www.theandroidhow.com/2014/05/how-to-backup-rom-dump-mtk-android.html

also video how to do it: https://www.youtube.com/watch?v=3nvbU6Km8-M
[Other SmartWatches] Wii60:
That was me, you're welcome! It kept adding that to my post, which was a little obnoxious, so I deleted it after you got the notification. Glad it worked!
[Other SmartWatches] Apokriphos:
MTK Droid Tools is amazing. Literally all you have to do is go to SuperSU and allow adb shell, allow for temporary root, and then click make backup. It is such a painless process its kind of incredible.

Parcaetron, filedropper.com works well for quick uploads up to 5gig. It should be around 1.3 I think.

Still no closer to getting a touch recovery, but you can make a ported CWM recovery through MTK droid tools very easily as well.
[Other SmartWatches] Wii60:
If anyone is looking for gapps, check the beginning of this thread. You'll find Lokifish's post of inital setup steps, which has a gapps installer there. Works great!
[Other SmartWatches] Apokriphos:
MTK Droid Tools 2.5.3 is fairly difficult to find online - and sometimes the versions are corrupted or filled with malware.

I just uploaded my version. It should be good: http://www.datafilehost.com/d/621715e7
[Other SmartWatches] jayjech:
My device shipped with M02V04 firmware and no Google Play or root access. I'm having problems rooting the device via Kingoroot or any other method. When I connect the device to a PC I get an enumeration failure for device descriptor request resulting in an unknown device. Did anyone have to install drivers to access the inwatch from a PC, and if so what drivers did you install?

All I really want is to install gapps but without root or custom recovery methods I don't really have any options to do so. I do have access to adb via my linux box but without root access all I can do is transfer an update file for local update (should I try M02V03?)
[Other SmartWatches] Apokriphos:
My device Build Number is Inwatch_Z_M2_V03, the international version, set to english. My watch came with play store but unrooted. I would suggest you downgrade your rom to V03, and try from there. I believe Lokifish mentioned that when he upgraded his V03 to V4 he lost gapps, gained weather and fitness tracker, and a bunch of untranslatable Chinese apps.

When I ran Kingoroot for the first time it recognized my device as an Inwatch Z_M2_V03. It then downloaded the drivers automatically. There are other ways get the drivers, and a universal driver download (search XDA for it, I found it before trying Kingoroot, it's here).

When rooting for the first time, please check my original post on the matter. Kingoroot would not root for me unless I manually disconnected my usb after the watch gets reset by Kingoroot. When I didnt remove the USB it failed to recognize my device (until I rebooted it), and at that stage I believe I got the same error as you.

After downgrading to M2_V03, try again and see what happens.
[Other SmartWatches] jayjech:
Thanks! I was a downgrade as a last resort but your confirmation regarding gapps and Kingoroot really helps. Anyone know where the "local update" feature looks for the update package?
[Other SmartWatches] Theo de Kok:
See post #199

Theo
[Other SmartWatches] Apokriphos:
This should help you!

Theo beat me to it.
[Other SmartWatches] jayjech:
I created the folder /storage/sdcard0/inwatchupdate/ and placed the m02v03 firmware zip package there as update.zip but Local Update is not seeing it.

The instructions from Lokifish don't specify where the folder should be exactly, they just say it should be somewhere on the device... I don't have permissions to place it at /inwatchupdate or /root/inwatchupdate or /system/inwatchupdate, etc, since I don't have root access. I can only create folders in /storage/sdcard0 so I hope it's supposed to be somewhere in there...
[Other SmartWatches] Parcaetron:
Backup of Kitkat rom: http://www.filedropper.com/inwatch-z141024forflashtoolfromreadback141231-001524

Be warned that I am extremely incompetent. Use at your own risk.
[Other SmartWatches] Apokriphos:
Thank you very much Parcaetron for your effort! You mentioned there are some Bluetooth issues with your 4.4 Rom, perhaps it has something to do with BT 4.0, which I believe is enabled in the KitKat rom.

Does anyone else here have 4.4 and can speak for BT issues? Perhaps there is a fix we aren't aware of, from another smartwatch forum.

Similar issue with 4.4.2: http://androidforums.com/threads/bluetooth-range-extremely-dropped-after-4-4-2-update.850699/

Fix:? http://www.androidpolice.com/2014/0...evices-affects-kitkat-4-4-and-jelly-bean-4-3/

http://xdaforums.com/nexus-4/help/android-4-4-bluetooth-problem-t2540897/page3

Many say turning off wifi while on bluetooth fixes problem.

Most users are suggesting to wipe cache partition to fix problem permanently.

As a reminder for any who may try to flash Parcaetron's Android 4.4 Rom or perhaps going to reflash their own recovery assuming they don't like KitKat, please use these steps and BE SURE TO BACKUP BEFORE YOU FLASH:

http://www.theandroidhow.com/2014/05/how-to-backup-restore-stock-rom-with-sp-flash.html
[Other SmartWatches] Apokriphos:
Is this an older version of the Inwatch Z?

http://www.dhgate.com/product/inwatch-z-smart-watch-dual-core-1-2ghz-cpu/179228836.html
[Other SmartWatches] Parcaetron:
The Bluetooth issues stemmed from the fact that Kitkat introduced a bug into Bluetooth tethering (on the receiving end) that broke apps like Foxfi and so on. It's a fairly big issue if you're planning to use the watch in tethered mode, since the firmware itself doesn't really support that, so you wind up having to do a lot of workarounds, all of which are dependent on the assumption that the watch can connect to the internet via the phone. It doesn't matter at all if your phone's ROM supports the inbuilt Android version of tethering, but mine unfortunately doesn't.

Other than that, the ROM version I posted has the Play Store working out of the box, but that and having a higher version number are really its only good features. Kitkat didn't really introduce any must-have improvements, and battery life is terrible on my device (without fail, it will last about 10-12 hours and then turn itself off, regardless of how much battery it claims to have remaining). So I hope that the cooks can make some kind of use of what I posted (Loki, are you there?) but it's not much good in itself.
[Other SmartWatches] Theo de Kok:
Apokriphos: do you know why my Z has such a good battery-lifetime? 2-3 days I get easely without any modifications. My rom version is 2.03 international, set to Dutch.

I have WiFi on all the time and Bluetooth off. And I use a simcard with a small dataplan, my Google account is synced using this dataplan. I'm making only 2-3 calls a day. When I make calls I use voip and a mobile hotspot, since I cannot get a connection using GPRS data. But the battery behaves excellent, only the watch switches off at 50% battery remaining, but it does this only after 2-3 days. When I do a recharge after the watch switched off it indicates an empty battery, not 50%.

Theo
[Other SmartWatches] Apokriphos:
Hey Theo,

I used to have the same problem as you. One night I charged my Inwatch to 50% with power off, then unplugged it and went to sleep. I'm not sure what I was thinking at the time.

However, the next morning I plugged it back in and it was at 100%. I am not sure I recommend this method, but ever since I haven't had that particular issue.

As for your battery life, I can only surmise that (I assume you don't use the active apps that I do but please let me know if you do) that without Bluetooth pairing and said active apps the default frequency & hotplug governor is actually pretty good. If you're willing, I would love to know what apps your watch runs in the background, and what a CPU spy installation says about your watch.
[Other SmartWatches] Parcaetron:
Thanks for all the help, my fancy dudes. One more question: Kingo doesn't appear to be rooting the device (to be precise, it claims it is already rooted, which it isn't; then, when I click "Root again," it installs the drivers but hangs indefinitely on rebooting the watch). Are there alternatives?
[Other SmartWatches] Lokifish Marz:
Connect to it in ADB shell with USB debugging enabled. If you see "root" or a "#" then it's rooted. It however may be missing su binaries.
[Other SmartWatches] Apokriphos:
Hey Parcaetron, just disconnect the usb when the watch resets, then immediately reconnect it while it is resetting. It will work and root :)
[Other SmartWatches] Parcaetron:
Thanks for the help! I eventually got Kingo to work, after considerable trial and error. There seems to be a very specific moment during the reboot portion of the root process when the USB needs to be detached until the watch finishes rebooting. For anyone else reading this who might happen to have as much difficulty as I did: The trick appears to be to detach the USB instantly when the PC application starts to report "Waiting for device..." and then LEAVE it unplugged until the watch is rebooted, which it should do on its own.

Edit: While I'm here, I wanted to talk a bit more about the problems I've been having with the watch. I don't mean to whine, but since Apokriphos in particular has very kindly been trying to offer help based the few passing remarks I had made (mostly made to caution possible downloaders of the KK rom that it is less than perfect), I thought I should be more precise as to what the issues actually are.

The Inwatch, or at least my Inwatch, has an extremely poor wifi signal - probably the result of the small size of the device making it difficult to fit in an adequate antenna. This is the reason that I wanted to focus on BLUETOOTH tethering (I assume Wifi tethering works fine; I haven't tried it). Unfortunately, Kitkat introduced a bug whereby, even if the bluetooth connection itself is stable, the recipient device will refuse to connect if it cannot do so in the "normal" way (via WiFi or the cellular network) without checking to see if it has an internet connection by other means (Bluetooth). I may try Apokriphos' remedy of clearing the cache, but it appears designed for a different problem: specifically, people who couldn't get their Bluetooth to work at all, rather than people whose Bluetooth works fine, but whose software won't allow them to use it for internet access).

EDIT2: Apparently Pdanet's website is outdated - they have in fact fixed the Kitkat bug. What was creating problems for me is that I couldn't see the "connect" button on Pdanet Tablet's screen because of the square screen. Setting DPI to 100 in App Settings (via Xposed) fixed the problem, and I am now connecting to the internet just fine with WiFi switched off, which is great because, as previously mentioned, the WiFi antenna on the device is rather lacking. (Again, I don't blame Inwatch for this. It's a size problem - my laptop can connect to networks my phone can't see.)
[Other SmartWatches] Lokifish Marz:
About the KK dump. What hardware version is it for? Seeing there are to different HW versions, flashing it on the wrong one could cause a world of trouble.

HW v1 used 02, 03, 04, etc firmware.

HW v2 used 12, 13, 14, etc firmware.
[Other SmartWatches] Parcaetron:
No idea. How do I check?
[Other SmartWatches] Theo de Kok:
I have Google Play running in the background.

CPU spy+ reports:

1001Mhz 3.5%

598Mhz 0.2%

Deep sleep 96.3%

Theo
[Other SmartWatches] vscmaster:
Could someone re-upload to another share?
[Other SmartWatches] Parcaetron:
Is that one not working?
[Other SmartWatches] vscmaster:
Three times connection has broken.
[Other SmartWatches] Lokifish Marz:
More info on versions- http://bbs.inwatch.cc/read-610

(Use Google translate if you can't read Chinese)

in short, the partition maps are not the same and there are some internal differences. I'm without a PC to cross check maps (stupid movers) so I can't verify which version the 4.4 release is for.
[Other SmartWatches] Parcaetron:
My build number (which I assume is the rom number) is INWATCH_Z_1.0.0.
[Other SmartWatches] jayjech:
To be brutally honest, I think the USB connector clip is quite horrid. When I saw it in the video, a little warning bell went off in my head but I looked right past it because of the device's other (really, quite nice) features. Anyway, since receiving the device, I've terrible luck getting a stable USB data connection (charging is fine, probably because it uses less pins?) The clip seems to work a LITTLE bit better for data connections with a different micro USB cable, but in general I've found that I've had to re-seat the clip many, many times until I get it JUST RIGHT to establish a stable data link to the PC. Even then, it seems like the slightest movement can cause the link to become unstable and/or bounce up and down continuously. At first I thought the problem was just the USB 3.0 ports on my PC and/or Windows 8.1, but I've have the same problems with Linux, Windows XP, and Windows 7. Maybe I just have a defective clip, but I doubt it. The clip looks and feels really cheap and just generally seems like a bad design (really, having the USB pin contacts in constant proximity with your sweaty, oily skin...?)

Anyway, I was able to downgrade to M02V03 by placing update.zip into /storage/sdcard0/inwatchupdate/update.zip (had to create the inwatchupdate folder). The problem I had earlier was that I had renamed the firmware archive to update.zip --- don't do that, the ZIP file is actually an archive containing update.zip, so rather than renaming the archive, extract the embedded update.zip and then place that into /storage/sdcard0/inwatchupdate on the device via adb.

I seem to have gotten the closest to gaining root access with Windows 7 and the Kingo Root app --- after Kingo puts the device into fastboot mode, Kingo is able to send some commands successfully, but the commands fail. The current error is "flashn 'recovery' not suppor" (message truncated on the device's small screen). After observing this error I tried manually flashing a different recovery.img (from read-610 thread on inwatch.cc bbs) via fastboot, but the transfer failed with a protocol error. I feel SOL and I don't really know what else to do or try... if anyone else has any other suggestions/tips I'm pretty desperate at this point. Root access would be nice but at the bare minimum I'm just looking for the Play Store (for Google Voice and Hangouts, mostly, as that is how I receive and make all my calls and text messages).

Ideas are greatly appreciated...

EDIT: Does anyone have an update.zip for the custom firmware that includes the Google Play store? Perhaps I could push it via adb and install it via Local Update.
[Other SmartWatches] Apokriphos:
Hey Jayjech. Sorry to hear you are having trouble with your Inwatch Z.

As I wrote in one of my previous posts, I completely agree with you regarding the USB clip. However, if you are careful, and use a quality (read: thick and durable) usb cable and keep the watch undisturbed, you won't have any issues. At least I don't. I wear my watch every day, and have run with it about 10 times so far, often sweating. I haven't had any connection issues as of yet, but I do clean the connections with soapy water then dry after running.

You may have a defective clip if you have issues after having done the above suggestions. My clip binds firmly with the watch band and does not lose connection even after picking it up and using it while connected and bending the USB cord.

Regarding your other issues, lets try to resolve them one at a time. Kingo Root does seem to produce a working root for the Inwatch Z_M2_V03 version. As I and Parcaetron have discovered, you must remove the USB cable after the first run through of Kingoroot (when it puts the watch in fastboot after driver download/install) then remove the USB as the watch is rebooting back into normal mode. Connect it again once it has completed rebooting. Please see previous mentioned posts for more tips here.

If you cannot achieve root, though I expect you should be able to (please provide specific feedback if you cannot after reading and following mentioned posts) you can attempt to download ADB unlocker apk with developer mode enabled and then connect your phone through MTK Droid Tools and attempt to root using the 2nd tab. See next link: http://xdaforums.com/showthread.php?t=2160490

Please try these suggestions. I will take a look at http://www.hongkiat.com/blog/flashable-zip-android-zipme/ and see if I can made an update.zip that you could use.
[Other SmartWatches] jayjech:
Apokriphos, thanks for the sympathy and encouraging words. I've tried all sorts of cable removal and reinsertion per the descriptions in this thread for the last few days to no avail, so I'm currently attempting the MTK Droid Tools / SP Flasher custom CWM recovery creation as a last ditch effort. I already tried the manual generic Android 4.2.x root procedure but was unable to reboot the device into download mode since it has no key combos (and you can't reboot download from adb unless you already have root access). If I finally manage to get root access one way or another, I will post the method that worked for me in case anyone else has as much trouble as I did with Kingo Root.

Although the clip is very problematic and a major flaw, I really like all the other features of this device. I especially like the transreflective display and overall build quality. I'm optimistic that I will eventually be able to get root access one way or another... if you or anyone else does end up creating a custom update.zip or finding an update.zip package which includes the Play Store bundled, please let me know --- root access would be nice (for Xposed) but all I really need is the Play Store.
[Other SmartWatches] Apokriphos:
Hey Jayjech,

Below are the three system apks associated with google play, wrapped and signed using ZipME apk. Apks only, data not included. Please let me know if it works.

http://www.filedropper.com/update_3
[Other SmartWatches] Apokriphos:
Bonus Settings Trick:

Although it was mentioned earlier in this thread as an adb command to open it temporarily, you can get permanent access to the full setting selection fairly easily. It has a lot of extra options including disabling lock screen, enabling rotation, adjusting auto boot, shutdown, and more. To begin, delete one apk link in your main access homescreen. Then download Quickshortcut Maker in the play store, and open it, searching for Settings. Choose the link ending in .Settings. Name the new link Settings2 to distinguish it, and hit okay. It will take the spot you left empty on the home screen and your bonus settings are now accessable.
[Other SmartWatches] jayjech:
Okay, my USB connector clip is surely defective. Last night I set the device down on a flat surface after establishing a "stable" link, and even waited to observe for a few minutes just to be sure that the link was not dropping. When I was satisfied that the link was stable, I began flashing a modified image via SP Flash Tool. Midway through the flashing process, the link bounced causing the flashing process to fail and soft-bricking my device.

Although I no longer have a usable ROM on the device, I did not overwrite the preloader, so I'm still able to access the device and flash other things via SP Flash Tool (although I no longer trust my USB connector clip). I believe I may be able to unbrick my device if I reflash via SP Flash Tool, but I'm definitely not wasting any more time with this connector.

If anyone has a suggestion where to purchase a replacement clip, please share... especially if there are any options available to ship from within the US. Otherwise I'll just have to wait another month for a replacement clip to arrive from Shenzen.
[Other SmartWatches] Kateremir:
sp flash tool

how did you access via sp flashtools to inwatch. Its not working for me. Connect via mtk droid is ok, i rooted the device with Kingo root, but no connect via sp flashtools. My firmware is V04
[Other SmartWatches] nk33:
i ordered my inwatch before xmas and received it today....my question is how do i get to the google play store on it? i cannot see it in the list of aps...also when i install it as an apk, it opens for a split second, then closes....should i do a factory reset as i did not get a wizard when i turned it on...
[Other SmartWatches] Apokriphos:
Hey Jayjech, please see this thread: http://xdaforums.com/smartwatch/other-smartwatches/inwatch-z-battery-problem-t2984174

Link to purchase is in thread. I am not sure if the Chinavision Warehouse has a US location as well.

Nk33: Reread earlier posts in this thread. I think around page 7 or so, Lokifish has a great tutorial on how to put google play store into the stock rom.

Kateremir: Are you sure you have been following the tutorials correctly? I have done the same processes as you and once MTK tools recognizes my watch, SP flash has no problems. https://www.youtube.com/watch?v=3nvbU6Km8-M

Please let me know the error you are getting.

Questions: Anyone able to confirm the scatter files match between 4.2.2 and 4.4.2 versions?

One easy way to do this would be to use the CMD window to log into fastboot then do the getvar all, and match values with my post from the previous page. Another would for someone with 4.4.2 to download the scatter.txt from MTK Droid tools and match them up. Ideally someone more knowledgeable then I can step in and confirm my guesses - assuming these would confirm a user of 4.4.2 can downgrade, and someone using INWATCH_M2_V03 can upgrade.
[Other SmartWatches] nk33:
I have searched the whole thread for a guide and havent seen one - I think from all that searching my eyes have gone wonky...any chance of giving me the page or post number? i would really appreciate it...

---------- Post added at 04:46 PM ---------- Previous post was at 04:34 PM ----------

Can I install the google apps without downgrading from v04 to 03?
[Other SmartWatches] Apokriphos:
Yes you should have no problem.
[Other SmartWatches] nk33:
Whenever i use Kingo Root, it gets to the point when it reboots the device, but watch keeps going to fast boot and i get a message saying reboot failed....