yashsingh1/xdaforums huggingface dataset:
[Off-topic] orangekid:
On the other side of that coin, I hate talking to the CS reps of ANY technology company.

"I need you to reprovision my data because your system thinks I have an iPhone and it's messing with my data"

"Sir, may I ask have you restarted your phone?"

and I have to go thru like 12 different times telling him to please do what I asked in the first place.

Or I walk into a T-Mobile store and the rep is telling me I can't use a verizon phone on the network, because it's verizon.

"But the phone comes unlocked, just give me a SIM card"

"Verizon is CDMA blah blah"

And I get to argue with the guy for an hour about how things actually work.

Or even worse when I try to get a warranty replacement device. No I don't want to restart my phone or factory reset it, or put in my Google Account login information again, or try a new SIM card, or anything like that.

The device is broken, I know about phones, just replace it and let's get on with it!

So trust me it's very frustrating for us consumers too...
[Off-topic] Jesse72:
Yep, definitely frustrating for consumers.

I have a phone that runs on unknown network bands, can I test a sim (i would pay the $2 if required)?

Nope, you are already on the best network.

But yours has different frequency bands

*Blank stare* Umm your already on the best network for reception

*Walk out knowing I could do the job better*

Sent from my fake galaxy note 4, now revived from the dead, again!
[Off-topic] ShadowLea:
You do realize that the shop assistants are hired for their sales skills, not their knowledge of the product, I hope? :p All they receive is Sales training, not product information nor technical training.

Most of them couldn't tell an iPhone apart from a Samsung if their lives depended on it. Going to those monkeys with a tech question is like asking a 5 year old about String Theory. It's pointless.

You might as well walk into IKEA's storage section with a question about network frequencies. You're statistically more likely to find people with tech knowledge there than behind the counter in a provider shop. :laugh:
[Off-topic] orangekid:
This is the B&M guys, the "service technicians" on the phone, the "specialists" on the phone, the guys in chats etc.

I have never had someone who knew enough about networks, bands, actual device specs etc, talk to me from any portion of any phone company.

And I've been on every phone network...
[Off-topic] ShadowLea:
From what I know in the EU, you never actually get to speak to the Tech guys when you call in. It's still only a Customer Contact employee. They contact the Tech department on an internal line, but the tech lads never speak to customers. Don't know if the US system is different (probably not).

Oh I've met my fair share of the technologically handicapped in the shops, too. One shining example is the idiot who told me, in 2013, that I shouldn't use Android because it was still a Beta version, and thus I would be at risk of viruses. :laugh::laugh::laugh::laugh:
[Off-topic] Jesse72:
Unfortuneately they hate Windows Phone to, which is a shame because aside from apps, it is the second best operating system (beats IOS by a mile)
[Onetouch Idol 3 Q&A, Help & Troubleshooting] akisgreece:
hi friends

(first of all sorry for my poor english)

In two days i forced to make two reset on idol 4.7 (something that had to do with me, not the phome). Then when i was talking to a friend of mine i saw the screen as in the photo that i attach. like magnifying glass with huge app icons.

Then i tried to go in "home" icon but it doesn't react in any of my commands and of course i shut down the phone.After that i realise i had the same problem (who accidentally discovered) when i do a double tab to open/close the phone (but when i did it with hard and strong way - not smooth touch) it did all the time and with one orange margin around the screen. All this problem after two resets, nothing else.

Any idea anyone?

----oi58.tinypic.com/er9xyg.jpg-----

(the photo is not real.. its with photoshop to saw you how it was the phone after the problem.I didnt have a camera to take a real photo, so i did in photoshop with photos of idol from internet)
[Android Q&A, Help & Troubleshooting] adityaonline07:
Help! Samsung s4 imei number has changed to 000000 any help will be appreciated.
[Asus ZenWatch] hecksagon:
Root is no longer working on MM update.
[Asus ZenWatch] hecksagon:
Don't suppose anybody knows how to get to recovery with hardware button?
[Asus ZenWatch] CSX321:
Swipe from top-left to bottom-right at the Asus logo. That gets you to fastboot mode, then swipe up and down to change menu items, swipe right to select.

Or you can enable debug mode and use adb reboot recovery.
[Asus ZenWatch] hecksagon:
You are a hero. I have looked for the better part of 2 hours for this. Anyway I'll sideload the LP update and start over. Hopefully somebody can make use of the recovery and boot pulls and get us a working recovery.
[Asus ZenWatch] nethead72:
I would be very interested in REMOVING the Wellness app. This is the only reason I want root. Guess I will need to wait until we have a root enabled file manager. Alas, I can write in C++ fairly well, but know nothing of coding for android. Be glad to test any recoveries and operating systems on my ZenWatch.
[Asus ZenWatch] CSX321:
It can be done without a file manager. If you have root, you can enable debugging, connect to a PC by USB, use adb to get a root shell, then adb uninstall package_name.

Edit...Which Benton are you in, BTW. I'm not far from Benton, IL.
[Asus ZenWatch] hecksagon:
Es File Explorer works fine and has an OK interface when on the watch. Also the KingRoot app that gets pushed has an uninstaller too for system apps. The biggest issue I've had is that when the prompt to allow root comes up you can not select allow. You have to cover the screen to back out, then go into KingRoot and open the log, then select the app you want to allow and set it to always allow. You have to do this after the initial failed prompt.

Edit: Freeport, IL here. Worlds a small place.
[Asus ZenWatch] nethead72:
File Types?

Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:

---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------

Benton Arkansas.

---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------

I use ES File Explorer on my Nexus 6, CyanogenMod 12.1

I do not have a wearable app on my ZenWatch. Is it in settings somewhere?
[Asus ZenWatch] hecksagon:
You have to download the normal phone apk from apkmirror or some other site and use adb to sideload it. Google sideloading apps to Wear, should work the same for any watch. Otherwise you can buy Apps2Wear on the play store. I have done that because its more convenient.
[Asus ZenWatch] nethead72:
Ok, went through the whole process, is there a way to check root access using ADB?
[Asus ZenWatch] hecksagon:
You should have KingRoot app installed on your watch. That will tell you if you have root. I imagine you could try to pull some files from /system or something that would normally not be accessible. I wouldn't recommend writing to system yet. I soft bricked by watch just by pasting a modified build.prop over the original, trying to turn off low bit depth ambient mode.
[Asus ZenWatch] nethead72:
Root confirmed, having issues side-loading the ES File explorer apk, though. I'm using the App2Wear method. Still trouble shooting.
[Asus ZenWatch] hecksagon:
Make sure you have adb debugging and adb bluetooth debugging enabled on watch. Make sure you have usb adb debugging turn on on phone. Then make sure you have bluetooth debugging turn on in Wear app. Make sure you do these in that order because the toggle in the wear app wont show up unless you have debugging enabled on phone first.
[Asus ZenWatch] nethead72:
This is the KingRoot file you need for windows.

https://onedrive.live.com/redir?res...3077&authkey=!AA2AI4RkRdiA4tg&ithint=file,exe

Attached is the latest ES File Explorer APK

EDIT: I rebooted everything, and worked fine. Funny how rebooting fixes so many issues... Will test when side-load is completed.

EDIT 2: Looks like its gonna take a long time. Gonna go do dishes and whatnot and be patient.
[Asus ZenWatch] hecksagon:
Sorry, they are .img. They were pulled using Flashify. The extension must have been stripped when I uploaded them to Drive.
[Asus ZenWatch] hecksagon:
Sometimes it fails once and works when you retry. Not sure why.
[Asus ZenWatch] nethead72:
ES is 28 MB when installed, according to App2Wear, that should be 45-60 minutes to install.
[Asus ZenWatch] hecksagon:
Maybe 10-15 mins when I did.
[Asus ZenWatch] nethead72:
Seems like its taking way too long (going on 1 hour+). Gonna reboot and try again.

---------- Post added at 11:55 PM ---------- Previous post was at 11:25 PM ----------

If it fails this time, I will connect it to ADB with command line and manually push the apk onto the watch. I will give it until after dinner to complete the process.

Cant get it to install, and adb says its an invalid apk file when i try to push it. I suppose its not really necessary anyway. Ill just use KingRoot app if I need to do file management.
[Asus ZenWatch] hecksagon:
Did you confirm the apk was good? I'd try installing it on your phone. I don't think KingRoot has file management capabilities.

On a side note, I would advise against uninstalling anything. I just went to flash the previous OTA and it failed because I didn't have Jawbone installed.
[Asus ZenWatch] hecksagon:
I am basically screwed until somebody can make a custom recovery and do a system pull that I can use to recover.
[Asus ZenWatch] btonetbone:
Oh damn, no good. If someone can pull the Jawbone app and upload it for you, would that help get you up and running again? Or are you unable to boot?
[Asus ZenWatch] hecksagon:
No working adb to push the files.
[Asus ZenWatch] nethead72:
Having root is good enough for me for now, I will hold off experimenting until I have an emulator running the root setup I have.

BTW, I will dump my ROM for you if that will help? Just not sure how.

---------- Post added at 07:46 AM ---------- Previous post was at 07:45 AM ----------

How do you not have adb? Hard brick, or corrupted bios partition?
[Asus ZenWatch] hecksagon:
Device won't boot after making just a small change in build.prop. Adb access in recovery is limited to sideload only. Sideloads fail because I've removed Jawbone Up.
[Asus ZenWatch] nethead72:
So you can't sideload jawbone... Heh.
[Asus ZenWatch] btonetbone:
Here's a crazy thought. We share a lot of internal hardware with the LG G Watch R, right? Would anyone want to try and see if their recovery and or ROMs may work on our watches? I'm not brave enough to do it myself, but I just wanted to throw the idea out there.

http://xdaforums.com/g-watch-r/development
[Asus ZenWatch] hecksagon:
I guess since I'm already screwed I can try it. I'll fastboot the recovery when I get home from work and see what happens.
[Asus ZenWatch] npjohnson:
Be careful! Even if the recovery boots, I guarantee that the partition maps on the two devices aren't the same! The recovery might think your /system partition is what its writing to, but it reality, that could be ANY other partition. Corruption will follow. Then you run the risk of a true hard brick if any of the bootloaders (aboot, sbl1, sbl2, sbl3) get overwritten.

TL:DR: DON'T USE ANOTHER DEVICE'S RECOVERY TO FLASH SOMETHING!

(As for ADB access, mtp/adb will 99% be broken anyway, so there probably isn't a point, but you could try and boot the recovery if you want, /shouldn't/ be a harm in booting the recovery to test. If you do decide to test the G Watch R's TWRP, only fastboot boot the recovery, don't flash it.)

Onto helping you recover your device:

Good News: As long as you have fastboot access, you aren't bricked!

Bad News: Someone is going to have to pull their system image for you to restore from.

To do this, and help him, someone who is rooted will need to run:

Su

#Accept KingRoots SU PopUp

dd if=/dev/block/platform/(whatever this folder is on the zenwatch, it varies form device to device)/by-name/system of=/sdcard/system.img

Then just adb pull /sdcard/system.img, and post it up to DropBox of Google Drive.

Then, all you (the person I'm quoting) will need to do is fastboot flash system system.img.
[Asus ZenWatch] hecksagon:
Sideload will only install signed zips.

I'll hold off til somebody can get this for me. I ask that whoever does not to change anything on the system partition beyond what kingroot does before you pull. Once we have the pull we can tinker.
[Asus ZenWatch] btonetbone:
Ok, I followed the directions from [MENTION=5848265]npjohnson[/MENTION] and was able to extract the system.img file. Here you go:

https://www.dropbox.com/s/5mpbbt6cho74d75/system.img?dl=0

Good luck!!

EDIT - In case anyone needs it, the folder that npjohnson mentioned above is called msm_sdcc.1 on our watches.
[Asus ZenWatch] hecksagon:
Success. Two additional steps were required. I had to unlock the bootloader, which is simply fastboot oem unlock and follow prompts. The second was to run this on the img file: http://xdaforums.com/showthread.php?t=2749797. This is required because the fastboot stores the file in memory before writing. With only 512mb of ram there is not enough room to fit the file in ram without splitting it up. To get it to work use the 512mb argument on the command line.
[Asus ZenWatch] npjohnson:
Great to Hear! Knew it would be simple.

I'm gonna compile a factory image for the ZenWatch, and /attempt/ a TWRP bringup. (no promises)

I will need testers (I don't own a zenwatch). I need some people that have root, and can give me the output of some commands. I am going to start a Telegram chat for ZenWatch development. PM me if you are interested in helping with TWRP/have root and can dump some files.
[Asus ZenWatch] tiny4579:
I saw this post and I was kind of inspired to try to bring up TWRP. I mainly want root to disable some apps, but if I can find some improved touchscreen drivers (my zenwatch has tap to wake issues. it doesn't work everytime, anyone else have this issue? This is even after exchanging the zenwatch once). My concern in doing so is can I guarantee an unroot. These devices are risky as they don't have recovery. Theoretically, wiping the su files with a file manager should unroot it.
[Asus ZenWatch] hecksagon:
Unrooting works fine using the KingRoot app that is installed on the watch. OTA requires certain files to be present to work, but if you just reflash the system.img that was posted earlier and then unroot using KingRoot you should be ok.
[Asus ZenWatch] tiny4579:
Still haven't gotten twrp working yet. I night try later today, but if I can get my custom kernel booting, I'll share it. Its near stock, but should improve performance and battery.
[Asus ZenWatch] tiny4579:
Custom kernel posted. Still looking into TWRP. It looks like I have everything configured right from what I can tell, but it just reboots.
[Asus ZenWatch] btonetbone:
Thanks and good luck!!
[Asus ZenWatch] hecksagon:
Anybody else looking into TWRP? If not I may take a crack at it but I have no development experience and have never compiled anything before.... So it may take me a while. I have found an xposed mod for disabling low bit ambient but have had no luck manually installing the framework.
[Asus ZenWatch] btonetbone:
I sent a pm, but haven't heard back. Like you, I am not a developer by any stretch, but am happy to test or help where I can.
[Asus ZenWatch] anythingdust:
can anyone help what to do with lg watch g \ r?

http://xdaforums.com/g-watch-r/development/leedroid-r-urbane-port-v1-0-0-june-6th-t3128850
[Asus ZenWatch] tiny4579:
There's a g watch r secttion for that.
[Asus ZenWatch] anythingdust:
know. but the same hardware, even the entrance to the fastboot same swipe

there put twrp, and we can fit

I apologize for the English. through Google translator
[Asus ZenWatch] hecksagon:
Yeah but the partitions on the storage are different, so the pointers in the fstab are different. I have already tried to boot the recovery from the G Watch.
[Asus ZenWatch] anythingdust:
realized. I now only play with fastboot and adb )
[Asus ZenWatch] hecksagon:
Well the latest update fails when it checks /system/bin/debuggerd. Probably will fail others as well despite removing root before installing. The only way I can see getting the update now is to get a working recovery so we can do a pull of an unrooted system partition. Unfortunately I am still working on twrp and have no real experience compiling anything,
[Asus ZenWatch] itechnoguy:
Would it be possible to get a copy of debuggerd from an unmodified Zenwatch (not on the current build) and push that to a modified Zenwatch to allow the update to pass the sha1 check? (Although I'm guessing that KingRoot probably modifies more files, it seems like it would be worth a try)
[Asus ZenWatch] hecksagon:
Can't seem to dump any system files without root.
[Asus ZenWatch] itechnoguy:
Another idea, I took a look at the system.img dump that [MENTION=982501]btonetbone[/MENTION] did (many thanks for that by the way), and the debuggerd_real binary has a sha1 sum that matches the one in the new OTA updater script (sha1sum: ffd78e80be9f7c1d421b73dcbf95893002b97b35), maybe that would allow the update to go through.
[Asus ZenWatch] itechnoguy:
Update on what happened: Using that system.img dump, I managed to clean up after KingRoot. The only two files that it actually modified in /system/bin were debuggerd (backed up as debuggerd_real) and install-recovery.sh (backed up as install-recovery.sh-ku.bak), which was immutable and basically impossible to remove from an ADB shell. I used my Linux VM to mount the img file and remove the immutable + read-only flags from various files in /system/xbin and /system/bin so that the update would complete (adb sideload can't remove the immutable flags left by KingRoot), and I sideloaded the LCA43 update.

Everything seems fine after the update (other than the new Weather app, which refuses to check for weather), but KingRoot is still there. I'm going to go through and see if it re-modifies the files at bootup, and if not, backup all the files for the next OTA.

If anyone needs a copy of the modified system.img (I can't upload this today, my home internet is much too slow), or just a list of what needs to be changed if you want to do it yourself, I can do both.
[Asus ZenWatch] hecksagon:
I would love to have the file and detailed instructions of what you had to do so I can better understand how to correct this issue. Still looking at getting recovery working, just haven't had time to sit down and learn to compile. Kids are keeping me busy :).
[Asus ZenWatch] itechnoguy:
Here's the system.img that I modified:

https://transfer.sh/Asqrv/system.img (transfer.sh links expire in 2 weeks, so if anyone needs me to reupload it after two weeks, let me know)

I'll do a write up of what I changed in a bit and add it to this post.
[Asus ZenWatch] hecksagon:
After reflashing my kernel back to stock it worked like a charm. Thanks for your efforts, you saved my watch!
[Asus ZenWatch] itechnoguy:
Glad it worked out for you!

I'm still planning on doing a short write up, but today was too busy of a day, and I have a lot of free time tomorrow to work on that.

Edit: I'm attaching the guide about how I edited the system.img to work, it does require a small amount of Linux terminal usage.
[Asus ZenWatch] btonetbone:
I'm glad you were both able to figure out how to upgrade after rooting! I took a much more low-tech approach. I called Asus, explained that why watch wouldn't update and kept erroring (gee, I wonder why...), and they issued me an RMA and replacement. So now I've got a new watch with a pristine band on the latest update, plus a little knowledge-base in the comments above about how to fix it more properly if I root again.

Hopefully someone is able to get TWRP running and we can at least get a few tweaks/ROMs going. I'd love to help however I can, but I'm better at being a tester than a doer.
[Asus ZenWatch] hecksagon:
Should have done that. I got a big ol scratch on mine.
[Asus ZenWatch] acbka:
Twrp work in progress :)
[Asus ZenWatch] btonetbone:
That is amazing!! I'd be happy to test or help in any way if you need anything.
[Asus ZenWatch] acbka:
Today or tomorrow we will be ready . =)
[Asus ZenWatch] nethead72:
Beware Kingroot, it works but it doesn't, not really...

Read posts more carefully, I said to myself. This may be old news. I will try the modified system.img from earlier.
[Asus ZenWatch] itechnoguy:
You should be fine, but if you want to be really safe, wait for a clean system.img dump now that we have TWRP. From what I've seen, digging through the KingRoot-ed system.img, KingRoot doesn't seem to modify the partition table, it instead makes files immutable (so non-deletable, even by root, until the flag is removed) and I think the KingRoot self-removal tool doesn't remove the immutable flag, meaning the files it tries to delete won't delete. (It actually does rename/backup the original files it modifies, which is why moving the originals back into place works, since their checksums are identical to those in the OTA script)

My modified system.img is safe, it's just that the best way to update to LCA43 from that modified image is to immediately sideload the OTA after flashing in fastboot so that KingRoot doesn't have any chance to re-modify files upon boot. KingRoot will still be on there after the OTA, but at that point, you can use the self-removal in the app, then use TWRP to flash the Android Wear specific version of SuperSU.
[Asus ZenWatch] nethead72:
Success

I did this, in 1.31 adb, it automatically sparsed the file to 65,000 or so chunks.

cd C:\Android-adb
fastboot devices
fastboot flash system system.img
fastboot reboot

I rebooted the device with fastboot reboot and loaded the system before i restarted from settings to test your theory.

Flashed, reboot, load to recovery, flashed the OTA, no issues.

Attached is a screenshot of the console output.

adb devices
adb sideload LCA43.zip

Wait. :good:

---------- Post added at 10:58 AM ---------- Previous post was at 10:55 AM ----------

Permanent link here in my Google Drive.

https://drive.google.com/file/d/0Bzsf6YNghzL8d1B2a0ktNFBncVU/view?usp=sharing
[Asus ZenWatch] nethead72:
KingRoot reinstalled itself with root access after I did the above.
[Asus ZenWatch] nethead72:
I had this setting enabled it seems, so my root was preserved over the system flash and update sideload.
[Asus ZenWatch] itechnoguy:
I didn't remove KingRoot completely in the modified system.img, only removed the immutable flags from the files it changed (or added) and switched out the binaries that were failing the update checksum (since KingRoot backed them up). I didn't remove KingRoot itself, because it just had too many things hidden in various directories; I thought it might possibly break something upon boot up since it resides heavily in /system.
[Asus ZenWatch] debruin89:
I may be stupid but,

I installed Kingo root, enabled all the adb rights, but it still failes. What am I doing wrong ?

thanks in advance :)
[Asus ZenWatch] yes_thisis_joey:
UP Jawbone or whatever

The stupid UP jawbone app keeps crashing and i never even use it. it just gets in my way to say its not working. If i root it will i be able to uninstall the app completely? can i uninstall it without root?
[Asus ZenWatch] hecksagon:
You can use the king root app on the watch if that is the root method you used to root. Otherwise you can sideload something like ES file explorer and manually delete the APK. Either way root is required to remove it.

P.S. If you haven't rooted yet and plan to do so, use the fastboot flash recovery method and make a backup of the system partition. I see there is a request for this to be done by somebody who did not install kingroot.
[Asus ZenWatch] CSX321:
Yes, please! That was me.
[Asus ZenWatch] yes_thisis_joey:
alright so im ready to root, and ill make a backup of the system partition. Wanna walk me through it, or is there a link with steps?