Database Develop

How to root your Samsung Galaxy Gear!

How to Root the Samsung Galaxy Gear:
Firstly:
I AM IN NO WAY, SHAPE OR FORM, RESPONSIBLE FOR THE OUTCOME OF YOU FOLLOWING THESE INSTRUCTIONS! IT WORKED FOR ME, BUT THAT DOES NOT MEAN IT WILL ABSOLUTELY, POSITIVELY, WITHOUT A DOUBT, WORK FOR YOU!
Root Guide:
Preparation:
1. Install Samsung's official ADB Drivers from here.
2. Get Cydia Impactor from here.
3. Go to your Gear's settings and enable ADB​
To Root:
1. Plug in the device and let it install all the drivers it needs.
2.Unzip the Cydia Impactor folder you just downloaded
3. Open Impactor from the folder you just unzipped
4. The default "# drop SuperSU su to /system/xbin/su" is what you need
5. Click start
6. Once the process completes, the device will still look normal, but is fully rooted!​
I will have to leave it to you guys to install a utility like SuperSU or Superuser until there is a functioning recovery for the Gear.
Though this isn't necessary, however, and in some most cases doesn't work! SuperSU or Superuser just manage what apps access the SU command, so if you trust the app, it should be ok!
Enjoy your newly rooted device!​
How to restore back to stock:
Preparation:
1. Get Odin 3.07 from here.
2. Find the proper .md5 file from here.
(If you are in the US, just select the Great Britain file.)
3. Install Samsung ADB drivers from here.​
To Restore:
1. Plug in the Gear
2.From being powered on, (Bootable or not) press and hold the button of the right until the Gear shows "Samsung Galaxy Gear Rebooting" and rapidly press the button until you get to the "Select REBOOT MODE" screen.
3. Highlight "Download" in the list by pressing the button to scroll.
4. Press and hold the button for 3 seconds (and let go! The screen won't change immediately) and let it boot into download mode.
5. Unzip the .zip file you just downloaded that contains the ROM itself.
6. Select the PDA button and open the .MD5 file in the folder you just unzipped.
7. DO NOT ALTER ANYTHING ELSE!!!
8. Click the start button, and you'll be back to stock within a couple of minutes! (Most likely with any data on /data kept and all sideloaded apps remaining.)​
Any questions? Ask below! Want to help me make a ROM or Recovery? PM me!​

I tried this on OSX and now have a device that won't connect via USB anymore, even after factory reset! Proceed with caution.
EDIT : The device would still connect to adb in 64-bit Ubuntu, and and after re-running the application I have a rooted device. Busybox has been installed and all seems to be working well now.

Oops!
BUS DR1V3R said:
I tried this on OSX and now have a device that won't connect via USB anymore, even after factory reset! Proceed with caution.
EDIT : The device would still connect to adb in 64-bit Ubuntu, and and after re-running the application I have a rooted device. Busybox has been installed and all seems to be working well now.
Click to expand...
Click to collapse
I had issues with impactor crashing on my Mac, so i ran it on Windows instead as well!

photonicgeek said:
I had issues with impactor crashing on my Mac, so i ran it on Windows instead as well!
Click to expand...
Click to collapse
I'm actually not sure what's going on with this thing now. Busybox said the device was rooted, and it installed, but I can't seem to run any commands that require root.
Are you running Superuser or SuperSU, and what version?

Does this mean i will be able to use this with my HTC one? Im a newbie when it comes to this but id love to buy this watch to use with my stock 4.2 HTC One. Thanks.
Sent from ...............

Great news! :victory:
About 'UNROOT'? ... any idea? Or we just flash official rom back to GEAR?

big_pongo said:
Great news! :victory:
About 'UNROOT'? ... any idea? Or we just flash official rom back to GEAR?
Click to expand...
Click to collapse
Haven't rooted mine yet. But seems like the unroot feature in supersu should work
---------- Post added at 06:22 PM ---------- Previous post was at 06:18 PM ----------
This is great news! Thank you sir for creating an account. Just to share ur find. Who knows this might even make it to XDA wall on home page! But I do have to ask, how did you know Cydia Impactor would do the trick?

To answer some questions...
Ok, Firstly, mounting the gear should never have been possible... I know I have tried!
The entire process of rooting a device is simply getting the file "su" into /system/bin/ but the trick is getting it in there without root privileges! The truth is SuperSU or Superuser aren't ACTUALLY needed, they actually just regulate how apps access the "su" command.
To use the gear with any watch would require a new ROM which I know NOTHING about, but I am looking into modding the first one. (I recommend setting the screen DPI to 100)
And to answer @trevor7428 , I am an iPhone and Android user, and I do a lot of research into how exploits work. Saurik who does a lot of iPhone security research, mentioned the "Master Key" ("Hack 99% of Android devices") exploit, how to exploit it (Where impactor came from!), and also how to fix it. Thus, I thought that the worst that would happen is that it would fail!

photonicgeek said:
Ok, Firstly, mounting the gear should never have been possible... I know I have tried!
The entire process of rooting a device is simply getting the file "su" into /system/bin/ but the trick is getting it in there without root privileges! The truth is SuperSU or Superuser aren't ACTUALLY needed, they actually just regulate how apps access the "su" command.
To use the gear with any watch would require a new ROM which I know NOTHING about, but I am looking into modding the first one. (I recommend setting the screen DPI to 100)
And to answer @trevor7428 , I am an iPhone and Android user, and I do a lot of research into how exploits work. Saurik who does a lot of iPhone security research, mentioned the "Master Key" ("Hack 99% of Android devices") exploit, how to exploit it (Where impactor came from!), and also how to fix it. Thus, I thought that the worst that would happen is that it would fail!
Click to expand...
Click to collapse
After typing that about mounting the gear I immediately questioned whether that ever worked. :silly:
That being said, I have the su file in system/bin and system/xbin/, but anytime I try to run something that requires root it says "must be suid to work properly". After trying to find a fix for that for a few hours without luck I've run out of ideas.
Better yet, why not make a backup of the rooted rom that can be flashed via Odin now that download mode is more accessible?

Someone please sticky this so its easy to find
Sent from my SM-N900V using xda app-developers app

Minecraft on the Galaxy Gear!
BUS DR1V3R said:
After typing that about mounting the gear I immediately questioned whether that ever worked. :silly:
That being said, I have the su file in system/bin and system/xbin/, but anytime I try to run something that requires root it says "must be suid to work properly". After trying to find a fix for that for a few hours without luck I've run out of ideas.
Better yet, why not make a backup of the rooted rom that can be flashed via Odin now that download mode is more accessible?
Click to expand...
Click to collapse
I just added restore instructions to the OP!
Oh, and I found that Minecraft actually runs rather well, if not extremely cramped!
Look for my video on Youtube! Username: Photonic Boom

photonicgeek said:
I just added restore instructions to the OP!
Oh, and I found that Minecraft actually runs rather well, if not extremely cramped!
Look for my video on Youtube! Username: Photonic Boom
Click to expand...
Click to collapse
This looks to have worked fine.
However now I have a couple of "Payload" apps in my drawer...do you know what files these are so I can remove them?

codeman05 said:
This looks to have worked fine.
However now I have a couple of "Payload" apps in my drawer...do you know what files these are so I can remove them?
Click to expand...
Click to collapse
Hmmm... payload... could you possibly upload a picture? or...
1.is it a custom launcher?
2.do they have custom icons, or are they the stock "these apps have no icon" icons?
3.if it is a custom launcher, are the apps uninstallable?

photonicgeek said:
Hmmm... payload... could you possibly upload a picture? or...
1.is it a custom launcher?
2.do they have custom icons, or are they the stock "these apps have no icon" icons?
3.if it is a custom launcher, are the apps uninstallable?
Click to expand...
Click to collapse
No, no custom launcher yet.
It's in the "stock" app drawer and they do not have an icon, just the generic green android guy.
I'll see if I can get a screenshot

codeman05 said:
No, no custom launcher yet.
It's in the "stock" app drawer and they do not have an icon, just the generic green android guy.
I'll see if I can get a screenshot
Click to expand...
Click to collapse
I figure you can try restoring again!

codeman05 said:
No, no custom launcher yet.
It's in the "stock" app drawer and they do not have an icon, just the generic green android guy.
I'll see if I can get a screenshot
Click to expand...
Click to collapse
Well I loaded Nova and was able to uninstall them with that so all it well!
On a side note...I found out something you guys may have already figured out, but figured it was worth sharing just in case.
To get into download mode:
1. Hold down power until the screen says "rebooting"
2. Start tapping the power button until you get into the "Boot" menu
3. tap power to cycle to "Download"
4. long press (~3 seconds) to select Download mode
You can then odin the image referenced in the OP.
Handy if you screw up the build prop changing the DPI like I did initially

codeman05 said:
Well I loaded Nova and was able to uninstall them with that so all it well!
On a side note...I found out something you guys may have already figured out, but figured it was worth sharing just in case.
To get into download mode:
1. Hold down power until the screen says "rebooting"
2. Start tapping the power button until you get into the "Boot" menu
3. tap power to cycle to "Download"
4. long press (~3 seconds) to select Download mode
You can then odin the image referenced in the OP.
Handy if you screw up the build prop changing the DPI like I did initially
Click to expand...
Click to collapse
Actually, I'm glad you found that!! I've been using ADB all this time!

Mods,
PLEASE pin this thread!

Hey does anyone know if
a) you can get notifications from 3rd party sms apps like handcent and
b) if you can respond to sms by typing yet? its pretty annoying when you get a text on your gear and you're somewhere loud, then you gotta take out your phone and respond. please if anyone knows these answers cant wait for this to take off....pretty excited.

this looks interesting! will have to try it on my gear :laugh:

[Q] App/Tweak to force reboot

Hi, I'm new to this whole android thing. I got a Kindle Fire HD 7" it's rooted with SuperSU and Google Play store on it successfully!
My main issue is it seems many tweaks like a reboot after installation, but my power button is completely missing. I can plug the device in to turn it on, and open/close the cover to put it to sleep.
Are there any tweaks around where I can like slide to power down, or force reboot how you would if you were to press the power button?
Alternately, I'd also like to remove the ad lock screens and potentially install a live wallpaper on either the lock screen or the home page. And maybe have an actual android grid set up. I know you need a secondary launcher to do this kind of thing, but all the ones I looked at screamed brick, and I got a bit worried. Could anyone point me at some basic tutorials? (I've jailbroken my Ipad rather extensively, but this seems to be a bit more in-depth to the actual operating system)
ETA: I haven't Used QMenu Just the ABD Drivers and the Root_with_Restore_by_Bin4ry_v33

If this is the 2012 model with a camera you can flash cm 11 on it and use maromi's kernel, it has double tap to wake, and cm also has double tap corner to sleep.
There are apps in the Google play store for rebooting methods that I believe allow for reboot normally as well as to fastboot and recovery, I know CM's built in power menu has those option if you enable them, but then there's the issue of getting to them with a broken power button.
Sent from my Amazon Tate using Tapatalk

It is the 2012, it has the camera with the clear slider to unlock.
I installed Nova Launcher off the G-play store, but yet again something needs to be rebooted! Hmph.
I'd love if you have any links to those store based power options, or to the CM 11 (is that a launcher also? what does "Flash" mean exactly? I've seen it around. ) The power button issue sucks, but I can't complain since it was a free gift!
I guess I can just run the battery down to reboot, but that is such a pain.

Dovetail said:
It is the 2012, it has the camera with the clear slider to unlock.
I installed Nova Launcher off the G-play store, but yet again something needs to be rebooted! Hmph.
I'd love if you have any links to those store based power options, or to the CM 11 (is that a launcher also? what does "Flash" mean exactly? I've seen it around. ) The power button issue sucks, but I can't complain since it was a free gift!
I guess I can just run the battery down to reboot, but that is such a pain.
Click to expand...
Click to collapse
hehe wow this is a first, ok cm 11 is cyanogen mod 11. its a rom you can flash instead of amazon's original os, it is way faster and more up to date and is more like pure android. Flash basically means we are overwriting the system files and such that came with the device. It can have any launcher, set wallpaper, is already rooted and has alot of cool things like themes and performance options you can set, much better than stock amazon os. You seem quite new to the concept of flashing a rom though so i advise you to read the tutorial thouroughly and as long as you don't mess up you shouldnt need a fastboot adapter even though its always advised to have one anyways. Heres a link: http://forum.xda-developers.com/showthread.php?t=2271909
Let me give you some advice so you don't end up with a red screen brick. Make sure when you follow this that when you see the red text at the top of fireflash(you will understand this when you start this part) that you check that box off thats either to the side or above the red text, this is a vital step you must follow or you will need a fastboot adapter to fix. I also recommend grabbing the cm rom and its corresponding gapps ahead of time.
Feel free to ask questions.
Also if you install a launcher on amazon os you will need root and you must copy and paste the app into the system folder and set the permission to a certain way or it will bootloop. I think titanium backup has a convert to system app button that does it for you. Wallpaper doesnt defaultly work without my fix either.

Nevermind, it finally worked

stunts513 said:
Feel free to ask questions.
Click to expand...
Click to collapse
Thank you so much for being patient with me!
I had been doing the app thing, but it seems like such a pain to do that with every app. I removed the installer, it wasn't doing much of what I was wanting anyways, the CM11 sounds much more like what I'm wanting to get to.
I'll give the tutorial a good read through and update this post with any questions I have!
Question 1: "commonly associated .... higher without first flashing the Amazon OS 7.2.3 bootloader" With flashing the cm11 do I need to (or do you recommend I) first restore or go back to the 7.2.3 or can I continue with 7.4.8? I will obviously be making backups as it seems that's the only way to recover with a standard usb cable.
Question 1A: If you are NOT on the 7.2.3 bootloader (you'll see red letters warning you), then hit the check box next to that to flash the 7.2.3 bootloader, otherwise you'll see a red screen after you reboot. If you don't see that warning, you're fine, move on. Is this the box you mentioned? It seems like this saves the hassle of going to 2.3 THEN flashing.
Question 2: "Alternatively, you can use this if the first method failed: Root_with_Restore_by_Bin4ry," I used this method in the first place. I had some issues with the ABD drivers not being recognized but got them working when I used amazon's direct ones. Furthermore, when I did get rooted (I used an app to check that it was and since nova worked I assume it was correct) superuser wasn't installed. I went and installed superSU manually. will this be an issue? (things have asked for and been granted permission and show as such in the superSU app)
Question 3: I'm using my work computer which runs through a server. when I go to back up through cmd it says the folder will be in C: and to then transfer it. The server shouldn't matter, right? I guess I can always just do a search for the file name and it'll turn up somewhere.
Question 4: Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP I did find an app called "reboot" which allows me to reboot (shocking!) without the power button. Can I still use that app at this point?
Question 4A: Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache.After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot This section calles to wipe some sections, will this also wipe my apps? it calls later on to reboot again. If the first bit wipes the apps, then I wouldn't be able to reboot at this point. (aside of waiting for the battery to die)

Answer 1: you don't actually need to downgrade the os, as long as the bootloader gets downgraded it is fine. So yes that was the checkbox I meant, believe it or not people have missed seeing it before because of the red text around it.
Answer 2: I think it will be fine, though I'm surprised you could root it with Amazon's drivers, theirs were kinda crappy.
Answer 3: I think this is OK, not sure how your setup is exactly. I don't see network issues being a problem.
Answer 4: you can still use the app. As to the wiping, yes you will lose all your apps, it is required to do the equivalent of a factory reset in twrp when coming from amazon os as the system apps leave some data left behind that causes cm to malfunction. You can install anything you had again from the play store or manually if you had apk's lying around. You can backup app data for games and such with titanium backup and restore it once you reinstall titanium backup in cm.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
Answer 1: you don't actually need to downgrade the os, as long as the bootloader gets downgraded it is fine. So yes that was the checkbox I meant, believe it or not people have missed seeing it before because of the red text around it.
Answer 2: I think it will be fine, though I'm surprised you could root it with Amazon's drivers, theirs were kinda crappy.
Answer 3: I think this is OK, not sure how your setup is exactly. I don't see network issues being a problem.
Answer 4: you can still use the app. As to the wiping, yes you will lose all your apps, it is required to do the equivalent of a factory reset in twrp when coming from amazon os as the system apps leave some data left behind that causes cm to malfunction. You can install anything you had again from the play store or manually if you had apk's lying around. You can backup app data for games and such with titanium backup and restore it once you reinstall titanium backup in cm.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Thank you so much again! I'm excited! I'll let ya know how it goes.

Sweet and I thought I'd mention if you get confused on what cm 11 build to download, the unofficial builds are a little bit more dated now that the device is a officially supported cm device, I recommend the link that isn't under mirrors that goes to cyanogenmod's Tate download page. The URL has those 3 words in it so you will know it when you see it. The m6 release is the stable release I recommend download instead of a nightly, I think m7 should be out soon, the cool thing is whenever a update is available it can ota like a phone, I believe it will make you choose to install the update though. I was impressed by how it updates, just seemed cool to watch. Not positive if cm's updater notifies you when updates are available though.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
The m6 release is the stable release I recommend download instead of a nightly, I think m7 should be out soon
Click to expand...
Click to collapse
Firstly, when I go to back up through the command prompt I get this:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\admnasst>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot
0block.img"
'adb' is not recognized as an internal or external command,
operable program or batch file.
Am I missing some step? I do have ABD enabled on the kindle.
Secondly, on this site: http://download.cyanogenmod.org/?device=tate
am I wanting the download second from the bottom that says "snapshot" and ends with m6-tate
I would figure so, but I wanted to double check.

Yes that the right file, as to that command not being recognized it is because it expects you to have a copy of that command handy and in the directory the command prompt is cd'd into. For instance download my wallpaper fix in my signature and extract it, then shift + right click the folder and hit open new command window here, then try the command again.
I have and by itself laying around on a thread I made here on the forum but this works just as well.
Sent from my LG-P769 using Tapatalk

stunts513 said:
Yes that the right file, as to that command not being recognized it is because it expects you to have a copy of that command handy and in the directory the command prompt is cd'd into. For instance download my wallpaper fix in my signature and extract it, then shift + right click the folder and hit open new command window here, then try the command again.
I have and by itself laying around on a thread I made here on the forum but this works just as well.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I ran the first line and it started. I'm going to do everything tomorrow when I have more time. I'll keep you updated! Thank you again for helping me, and being so welcoming.

https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot this was my favorite reboot app and it works well although I see your doing the custom ROM thing now.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

ROM toolbox has a quick-reboot option that is similar to respringing iOS, and it well let you create a launcher shortcut on your home screen.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<

[GUIDE] How to flash 1.5 update on LG Urbane (non-LTE version)

For some Urbane users, for whatever the reason may have been, they were unable to install the 1.5 OTA, the "dead" android continued to come up. This guide assumes that you have Minimal ADB and Fastboot installed on your computer, a guide that includes how to set your computer up for this is found HERE. This guide also assumes your watch is already on ADB debugging, etc, etc, else follow the previously mentioned guide.
READ ENTIRE GUIDE BEFORE YOU START. NEEDLESS TO SAY YOU'RE TRYING THIS AT YOUR OWN RISK..
Files needed:
- System
- Boot
- Recovery
(these are for 6.01 version, and can be found HERE with the 5.01 version).
- 1.5 update zip found HERE
1 - Connect your watch's charger to your PC and set your watch on the charger.
2- Open Minimal ADB and Fastboot, and type:
Code:
adb devices
and hit enter
3- If properly connected you should see something similar to "504KPJP00XXXX8 device".
4- Now type in:
Code:
adb reboot bootloader
and hit enter. The watch should reboot into the bootloader.
5- While in bootloader type:
Code:
fastboot flash system
and drag the System file you downloaded earlier to the Minimal ADB and Fastboot window, and hit enter.
6- When it's done installing type in:
Code:
fastboot reboot
and hit enter.
7 - Repeat steps 1-6 for EACH of the other two files: Boot and Recovery files you downloaded. Keep in mind that EACH TIME when you get to step 5 you must type in:
Code:
fastboot flash boot
for the Boot file, and
Code:
fastboot flash recovery
for the Recovery file respectively and drag their respective files to the window. So, to recap, do steps 1-6 for Boot, and 1-6 for Recovery. Got it? Good.
8- Get into bootloader mode again (see steps 2-4). Using the left and right (< >) arrows in bootloader screen on your watch look for "Recovery Mode" and hit the (o) option.
9- Now you will see the good ol' "dead" android. Fear not, touch the screen and you should get some options. Sliding your finger up or down scroll to "Mount /system", and swipe left or right.
10- Now slide down to "Apply update from ADB" and slide left or right to get into ADB sideload mode.
11- Once in sideload mode go to Minimal ADB and Fastboot window and type in:
Code:
adb sideload
AND drag the 1.5 update zip file you downloaded onto the screen, THEN hit enter.
12- If done properly the Minimal ADB and Fastboot window will start showing you some progress and so will the watch. wait until it's done. When it's done reboot your watch. Be advised it will take a little bit to power on, be patient!
You're all done!
Now you can go back and install TWRP, root, etc..
I want to point out that 1 or many of the above steps may not be necessary but this is exactly what I did to successfully flash the update. No wiping, no factory reset was necessary.

Can you please share how to disable auto update after installing 1.5 on urbane? I successfully downgraded but in couple of hours my watch updated back to AW2.

caughtmountain said:
Can you please share how to disable auto update after installing 1.5 on urbane? I successfully downgraded but in couple of hours my watch updated back to AW2.
Click to expand...
Click to collapse
Here. By the way what's so bad about 2.0?

How do I update to M1D65H (the last aw 1.5 update) ?
Thanks for the detail tutorial. BTW the aw 1.5 version given in your link (MM) was MWD48B.
How to find and upgrade to the last aw 1.5 just before the aw 2.0 was released. i.e M1D65H
Update : Somehow I managed to upgrade to M1D63G (OTA package - using adb sideload), after which I could not able to find further updates.
Updating to M1D65H (OTA package using "adb sideload") directly fails.
---------- Post added at 03:04 AM ---------- Previous post was at 02:58 AM ----------
cubandanger05 said:
Here. By the way what's so bad about 2.0?
Click to expand...
Click to collapse
I keep getting the notifications even after running this APP in my watch.
After running this APP, the message says disabled update and please restart.
But after some time I get back the "Notification for the Update"
Does the watch requires to be rooted ?

razebond said:
Thanks for the detail tutorial. BTW the aw 1.5 version given in your link (MM) was MWD48B.
How to find and upgrade to the last aw 1.5 just before the aw 2.0 was released. i.e M1D65H
Update : Somehow I managed to upgrade to M1D63G (OTA package - using adb sideload), after which I could not able to find further updates.
Updating to M1D65H (OTA package using "adb sideload") directly fails.
---------- Post added at 03:04 AM ---------- Previous post was at 02:58 AM ----------
I keep getting the notifications even after running this APP in my watch.
After running this APP, the message says disabled update and please restart.
But after some time I get back the "Notification for the Update"
Does the watch requires to be rooted ?
Click to expand...
Click to collapse
I believe so, yes.

Have installed updatedisabler.apk on both phone and watch (watch is rooted) both come up with "Check your watch to find the application". Still get nags about updating?
Has anyone got this to work?

updatedisabler is not working, somebody knows how to uninstall it?

First, it's slow and buggy. Google Assistant takes several seconds to load before you can speak to it, sometimes so long the screen times out before you can speak your command. I always get a notification vibration, but rarely get the notification card, destroying the most useful smart feature of the watch, and instead of cards peaking, I always have a full screen card of whatever song or podcast I'm listening to, that is persistent and blocks my watch face, destroying the most useful feature of not smart watches (since I can't see the time). But, those apps run on the watch natively by default, so if I try to start playing music or podcasts it can only playback locally from the watch, not start the playback on the phone. Do disturb on the watch is also now separate from dnd on the phone, which means when going into meetings I have to silence both independently. In short, what's wrong with aw2? Everything! Oh, and my battery just says 50% all the time since the update. Totally garbage.

Hello. I'm getting an error that it's locked and so I can't flash the file to downgrade. Does the bootloader need to be unlocked ????? I'm currently on AW 2 and I would like to flash back down. Thanks.

Im confused, I know how to flash .img files but what do I do with this 1.5 update file? I currently downgraded to 1.3 but thats a little too old for my liking.

mexiken said:
Hello. I'm getting an error that it's locked and so I can't flash the file to downgrade. Does the bootloader need to be unlocked ????? I'm currently on AW 2 and I would like to flash back down. Thanks.
Click to expand...
Click to collapse
Yes, your bootloader needs to be unlocked

RunNgun42 said:
Im confused, I know how to flash .img files but what do I do with this 1.5 update file? I currently downgraded to 1.3 but thats a little too old for my liking.
Click to expand...
Click to collapse
If you're on stock 1.3 you should be able to flash the update following the adb sideload steps

Hi guys. I tried to follow the steps, but the "adb sideload" part is not working. The watch presents an error: "can't mount /system". Any tips? Is there any 1.5 full rom out there?

[fixed]

BACK TO WEAR 1.5 FROM 2.0(COMPLETE GUIDE) and ELIMINATE THE PERSISTENT UPDATE NOTIFIC

Hello everyone,
Some Italian guys asked me for this guide because they did not find anything complete and detailed. Thanks to the XDA members' publications I could put together the pieces and write it down. I apologize for my English but I'm not very good, especially for technical terms. I hope I can help someone.
BACK TO ANDROID WEAR 1.5 FROM 2.0(COMPLETE GUIDE)
1. Download the software ADB installer 1.4.3 from this link compatible with Windows 10: http://uploadboy.com/tsp1bpbe9gtj/1082/zip
From here you can download an older version 1.3 for Windows 7: https://forum.xda-developers.com/showthread.php?t=2588979
2. Open the .exe file already downloaded with administrator privileges and follow the installation procedure to install the drivers
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
4. Insert the files into the folder that created the ADB Installer that is normally the path "c:\adb"
5. Download tool "WinDroid Toolkit" from here (some antivirus swapping it for threat and eliminating it, in this case turn it off momentarily) :
https://forum.xda-developers.com/devdb/project/dl/?id=17244
6. Start with administrator privileges "WinDroid Toolkit"
7. Follow the instructions for installing the drivers required by the tool and select the model of the clock
8. Activate developer options on the clock: (Settings> System) by clicking "build number" repeatedly until unlocking the menu that will be among the main options
9. In the developer options menu, activate the "debug ADB"
10. Turn off the clock
11. With the clock off, hold down the physical key and in the meantime repeatedly tap your finger on the screen from minute 55 to 25 until the watch has entered the mode fastboot
12. Connect the clock to PC usb port via cable and charging base
13. Now "WinDroid Tool" should recognize the clock and below you will see that the "Offline" script becomes "Fatboot"
14. Click on "Unlock Bootloader" and proceed by accepting the various message from the tool
15. A confirmation message appears on the clock display, click on the right arrow and then on the central button to continue
Now the bootloader of the clock is unlocked and we can continue to install the three previously downloaded files. Close "Windroid Tool"
16. In the "adb" folder at the "c:\adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
17. In the newly opened window, give the following commands one at a time and wait for each one to complete the operation:
1) fastboot -w
2) fastboot flash boot M1D65H_boot.img
3) fastboot flash recovery M1D65H_recovery.img
4) fastboot flash system M1D65H_system.img
Finally, to restart the clock, use the following command:
5) fastboot reboot
N.B. Before pairing the watch on the cellphone again remove the link, inside the Android wear app, clock and uninstall and reinstall the app.
Finished!
ELIMINATE THE PERSISTENT UPDATE NOTIFICATION
1. Download the .zip file containing the custom recovery and root to this address:
http://www.mediafire.com/file/qllnc7...+R+Utility.zip
2. Unzip the .zip file and insert the "twrp-3.0.0-0-lenok+squashfs.img" file into the "c:\adb" folder
3. In the Clock Developer Options menu, activate the "Debug ADB" (to enable them to follow the procedure above)
4. Connect the clock to the pc via the cable and charging base
5. Open "WinDroid Tool", go to the "Commands" tab and click on "push file". Select the file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete and disconnect the clock from the PC.
6. Turn off the clock
7. With the clock off, hold down the physical key and in the meantime crawl your finger repeatedly on the screen from minute 55 to minute 25 until the clock has entered fastboot mode
8. Connect the clock to the pc
9. In the "adb" folder at the "c: \ adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
10. In the window just open, give the following command and wait for the completion:
-) fastboot flash recovery twrp-3.0.0-0-lenok+squashfs.img
11. From the clock using the arrows and the confirmation button down to start the "recovery mode"
12. Accept the warning message and after selecting the language click on "install" and select, with the touchscreen, the .zip file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete.
13. Restart the system and wait for the clock to turn on.
14. In the previously opened command window, give the following commands one at a time and wait for them to complete and complete:
1) adb shell
2) su
3) pm disable com.google.android.gms/.update.SystemUpdateService
4) pm disable com.google.android.gsf/.update.SystemUpdateService
Finished!

Many thanks riccardo423
I have managed to rollback my lg g watch r to android wear 1.5 AND suppress those pesky update notifications using your guide. I noticed your mediafire link to the custom recovery file is broken. There is an alternative download at http://www.mediafire.com/file/qllnc77jtdqxtdl/Lg+Watch+R+Utility.zip (posted by Dettofatto in a previous xda thread) which also contains the two additional required files.
Luigino1

Hello, thanks for inserting a working link. I've modified the text of the guide by entering your link. I'm glad to have helped you.
Riccardo423

For step 3 if I click the link it says the post does not exist. Anyway here's where I found the images if anyone needs it: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
BTW: Thank you for the complete guide, step by step, i was able to go back to 1.5 and disable the persistent notification thank you very much!

Hi, thank you for inserting the working link. I'm glad to have helped you. Riccardo423

After downgrade from 2.0 to 1.5, I don't received Facebook messenger notifications on watch. Other notifications work fine (Gmail, sms etc). Anyone know what's going on?

Hi I have never had this problem I think I can depend on your Facebook app. Which version of Facebook and which cell phone?

Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates

szczurx said:
Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates
Click to expand...
Click to collapse
You've already tried uninstalling and reinstalling the app?
The app wear permissions are unlocked for notifications?

Android wear app reinstalled twice. Even made watch factory reset. On Phone in settings/apps, Android Wear app have permissions for everything possible

Thanks for this Riccardo ( or grazie, from a fellow italian )!
Can't believe I managed to do the entire procedure without making a mess of it, lol. Everything appears to be working again, I'm so happy! Really hated AW 2.0. Hope the notification does not come back, I'll keep an eye out for it in the coming days.

hello, can anyone answer me why these commands dont work
pm disable com.google.android.gsf/.update.SystemUpdateService
and why superSu crashes on watch

Thank you Riccardo423 for great manual, it works great for my watch. No AW2 anymore!

riccardo423 said:
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
charging base
Click to expand...
Click to collapse
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?

LionheartSilver said:
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?
Click to expand...
Click to collapse
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.

pidobeuliou said:
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.
Click to expand...
Click to collapse
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?

LionheartSilver said:
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?
Click to expand...
Click to collapse
Nothing specific, just installed the basic factory image + root . I have installed about 16 apps (including Watchmaker with a quite "sophisticated" watchface, wear messenger, WearMail, Wear Battery stats, Feel the Wear, Runtastic, ...) but mainly I have deactivated Google Fit which is a true battery killer app on both the Smartwatch and the Smartphone!.

mediafire link is dead (twrp) - please, reupload it!

Thanks so much for this, it worked perfectly! So great to have my watch back!

Hi, I have problem connecting in ADB mode to PC - when I plug in craddle nothing is happening Win10 not even play a sound, not trying to find drivers etc. Is it connected with new version NXG47C/LENOKZ22b ??
In fastboot mode there is green "secure boot" enabled, lock state - locked and bootloader in Z22b version. Is it possible to connect ADB in this case? Im stucked witn AW2 and there is nothing I can do for now Please help.

[TOOL] crosshAtchDB: Pixel 3 XL Flash Tool

I'm trying to create an application to make flashing files on our pixel devices easier.
Features:
Install ADB
Unlock bootloader
Reboot to bootloader
Download and install factory images
Download and install TWRP
Download Magisk
Easy to use GUI
Enjoy! :good:
Credit to Dees_Troy and bigbiff for TWRP image.
Feel free to modify and hack away at the source.
WARNING: I am not responsible for anything that goes wrong using this tool, it works fine on my windows 10 machine, and tested on windows 7. However, make sure you know what these tools are doing beforehand.
New update!
Beta Release
What's New?:
All new base being built.
Better .exe support (requires installing the app)
Console interface for now.
Removed some features that were broken in the old app, will add them back one-by-one, but this time, not until they work 100%.
Usage:
Just follow the prompts on screen.
Allows picking the files for booting TWRP or pushing files via ADB.
Install:
Easy method (requires install): https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/crosshAtchDB-2.3-win32.msi
Install the app with the provided .msi, choose where you want to install it. Open the folder where you installed it and run the crosshatchdbbeta.exe.
Build/Run from source:
Requires:
source .py file: https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/crosshatchbeta.py
cxfreeze config: https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/setup.py
To run from source, just install Python on your PC, then from cmd window run : "pip install requests".
Then just double click on the crosshatchdbbeta.py file.
To build the .exe:
You need both files from above.
Install Python
python -m pip install cx_Freeze --upgrade
With setup.py and crosshatchdbbeta.py in the same directory, run "python setup.py build"
This is a very minimal release, I will continue to fix any bugs and add features once they are working better.

Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
**Didn't want to waste thread space so I'm editing this to reply** - Thank you so much for the response below! Very helpful! I'm up and running and really appreciate the tool and the help!

NippleSauce said:
Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
Click to expand...
Click to collapse
No problem, quick usage guide to make sure it goes smooth.
Enable OEM unlock in developer options, also enable ADB debugging.
Plug in your phone, run crosshatchdb.
Select option 9, this will auto download and extract adb to your c: drive.
Select option 1 to check for ADB devices, check the box on the dialog that pops up on your phone.
All set. You can download magisk directly to your phone or push it from your PC.
Reboot bootloader option 2, from here you can unlock the bootloader(formats your phone btw).
Setup your phone, enable ADB debugging again and your free to reboot bootloader and download/boot TWRP to flash magisk.(use TWRP img not zip)
Hopefully these instructions are not too confusing, it is pretty easy once you do it once, and the tool really does make the next time you do it faster.
Tested on a windows 7 virtual machine and my own personal windows 10 machine.

NippleSauce said:
Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
Click to expand...
Click to collapse
The time to unlock a Google purchased Pixel isn't the issue. The factory reset just sucks if you run stock for any time before doing it.

Two things I think you should add.
1) adb sideload for when adb works in twrp.
2) adb logcat for our great developers, so there isn't an excuse for getting them a logcat in event that they need one.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
Two things I think you should add.
1) adb sideload for when adb works in twrp.
2) adb logcat for our great developers, so there isn't an excuse for getting them a logcat in event that they need one.
Click to expand...
Click to collapse
Good idea, should be easy to pipe logcat output to a text file.
ADB sideload can be added as well, next update will probably be when TWRP ADB is fixed, or sooner depending how long that takes.
Already thinking of ways to make the current version of this script more automated, but I like to err on the side of explicit is better than implicit.
Thanks for the ideas.

Can this install TWRP ?

Zorachus said:
Can this install TWRP ?
Click to expand...
Click to collapse
No. Everything you need to know is in the OP and everything else you need to know is in the twrp thread.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
No. Everything you need to know is in the OP and everything else you need to know is in the twrp thread.
Click to expand...
Click to collapse
This.
It is a good option of you want an easy way to just boot TWRP in 1 button, if you don't want to install a custom recovery like TWRP.

New update coming soon, decided that command line didn't work very well for this purpose...
Also working on making all of the actions smoother.

New update released, let me know if you have any issues or feature requests, still waiting for TWRP to be fully functional before adding ADB sideload options.
CMD window still wants to hang out for now, you can minimize it though if needed.

can you add a (check for update)

Maty360414 said:
can you add a (check for update)
Click to expand...
Click to collapse
Yes, that is on the list for next update.
When TWRP is more reliable I will probably add options for copying TWRP backups to your PC as well.
Still need to get rid of the cmd window and cut down on having to open browser windows or file selection dialogs, just to get it feeling less clunky.

I'd like to send out a big thank you to boostedduece I've used platform tools and google flash all for years with no hitch whatsoever but I tried to glies an update to my kernel and ran into the red corrupt device thing and used my platform tools to flash all and halfway through it stopped and said error. I then tried this tool and it worked perfect!! Thank you so much!

quinejh said:
I'd like to send out a big thank you to boostedduece I've used platform tools and google flash all for years with no hitch whatsoever but I tried to glies an update to my kernel and ran into the red corrupt device thing and used my platform tools to flash all and halfway through it stopped and said error. I then tried this tool and it worked perfect!! Thank you so much!
Click to expand...
Click to collapse
Glad to hear it helped out, working on some new updates to make the UI even better.
Trying to make all of the download links update automatically too, just working on some web scraping again ?
It's a nice little tool if something gets messed up, also for new users to get up and running.

New update released, Download factory image has been overhauled, it will now download the image automatically, check the SHA-256 hash, then unzip it to the correct folder, just run the factory image flash option after and you're set. Be patient, the image.zip can take a while to download, takes several minutes for me, but I'm only at 50mbps down...and who knows if google throttled my connection after all the web scraper testing lol.
Pull TitaniumBackup folder via ADB to your PC, pull TWRP backup might not work it failed for me, but will not cause any damage to your PC or phone, ADB is copying the files read only from your device, and ADB just seemed to crash on me.
CMD window is still here for now until I pipe the output to the built in box on the GUI and bind keyboard keys to interact with it. For now it will help with any debugging.

boostedduece said:
New update released, Download factory image has been overhauled, it will now download the image automatically, check the SHA-256 hash, then unzip it to the correct folder, just run the factory image flash option after and you're set. Be patient, the image.zip can take a while to download, takes several minutes for me, but I'm only at 50mbps down...and who knows if google throttled my connection after all the web scraper testing lol.
Pull TitaniumBackup folder via ADB to your PC, pull TWRP backup might not work it failed for me, but will not cause any damage to your PC or phone, ADB is copying the files read only from your device, and ADB just seemed to crash on me.
CMD window is still here for now until I pipe the output to the built in box on the GUI and bind keyboard keys to interact with it. For now it will help with any debugging.
Click to expand...
Click to collapse
Can't believe I still haven't gotten the Ota Nov update
Will this work on p3?

frewys said:
Can't believe I still haven't gotten the Ota Nov update
Will this work on p3?
Click to expand...
Click to collapse
It will work for pixel 3, but you will need to download the factory image for your blueline device and extract it into c:\crosshatch_stuff\platform-tools. This program is basically a gui wrapper for ADB commands.
Just stick with the ADB tools section and find the downloads you need separately.

boostedduece said:
It will work for pixel 3, but you will need to download the factory image for your blueline device and extract it into c:\crosshatch_stuff\platform-tools. This program is basically a gui wrapper for ADB commands.
Just stick with the ADB tools section and find the downloads you need separately.
Click to expand...
Click to collapse
Right
So it doesn't automate the process the same as for xl?

frewys said:
Right
So it doesn't automate the process the same as for xl?
Click to expand...
Click to collapse
It will still install ADB and allow you to run reboot bootloader, boot TWRP, factory reset, ADB logcat, unlock bootloader.
But the only extra part that is manual would be extracting the factory image into the c:\crosshatch_stuff\platform-tools folder.