Database Develop

[Q][ME176CX] Any News About Unlocking Bootloader And Installing CWM Recovery?

[Q][ME176CX] Any new news about unlocking bootloader and installing CWM Recovery?
I'm wondering if there are any new news/hacks/exploits/methods to unlock the bootloader on the ASUS Memo Pad 7 (ME176CX) to install ClockworkMod or any other Recovery Menu on it.
I really really need a working Recovery Menu installed, so I can undo critical system changes (eg: Xposed) if the device ends up bootlooping...
EDIT: I googled days long to find a solution, before opening this thread here

GhettoGirl said:
I'm wondering if there are any new news/hacks/exploits/methods to unlock the bootloader on the ASUS Memo Pad 7 (ME176CX) to install ClockworkMod or any other Recovery Menu on it.
I really really need a working Recovery Menu installed, so I can undo critical system changes (eg: Xposed) if the device ends up bootlooping...
EDIT: I googled days long to find a solution, before opening this thread here
Click to expand...
Click to collapse
Hi,
do you know of the "temporary cwm" or "temporary recovery method" here? How did you root your device?
And: To get out of a bootloop caused by one of the XPosed-Modules you only need a working adb connection.
Before installing XPosed, check, whether you can connect to your tablet via adb. If yes and you get into a bootloop,
simply open a adb shell and you will be able to edit the filesystem.
And maybe what is tried in this thread
http://forum.xda-developers.com/memo-pad-7/help/asus-memopad-7-me176cx-getting-linux-t3164705
may lead to a way to boot other things than Android on this wonderful tablet - that is may be twpr and cwm are
in reach.
HTH!
Best regards,
tuxic

thanks for the replay
tuxic001 said:
How did you root your device?
Click to expand...
Click to collapse
i've rooted my device with ROOT ZenFone, worked like a charm at the first try
tuxic001 said:
do you know of the "temporary cwm" or "temporary recovery method" here?
Click to expand...
Click to collapse
i've heard of that temporary recovery method, but i prefer a permanent one which can be accessed with POWER+HOLD VOL-. what are exactly the differences between a temporary and a permanent one, do you need to install this every time you need it? or how i can understand this.
tuxic001 said:
check, whether you can connect to your tablet via adb. If yes and you get into a bootloop,
simply open a adb shell and you will be able to edit the filesystem
Click to expand...
Click to collapse
what i understand about bootloops is, that the device does a full restart after unable to start android, which would disconnect the adb shell. or did i got somethig wrong here?
tuxic001 said:
And maybe what is tried in this thread
http://forum.xda-developers.com/memo-pad-7/help/asus-memopad-7-me176cx-getting-linux-t3164705
Click to expand...
Click to collapse
i know about this, but it's not finished yet. the power button for example cannot be used to confirm for example, which would be useless on-the-go. (how has a keyboard all the time :silly: )
http://forum.xda-developers.com/memo-pad-7/help/how-to-dual-boot-me176cx-part-1-t3183437
sorry for all the questions, but i got this device 2 days ago and i don't know anything whats going on under to hood - and no: i'm not a android/linux noob - i just won't full brick my device
and also, what about a nandroid backup over adb, is there a legit way to archive this?
thanks in advance
EDIT: i tried the temporary recovery, but i'm unable to do any kind of backup. maybe the paths are all incorrect (?)
anyway, i took the risk of a bootloop and installed the xposed framework and succeed
i also found out that i can try to "stop" android before it bootloops again -> adb -d shell stop and do a manually restore over the command line

GhettoGirl said:
thanks for the replay
i've rooted my device with ROOT ZenFone, worked like a charm at the first try
i've heard of that temporary recovery method, but i prefer a permanent one which can be accessed with POWER+HOLD VOL-. what are exactly the differences between a temporary and a permanent one, do you need to install this every time you need it? or how i can understand this.
what i understand about bootloops is, that the device does a full restart after unable to start android, which would disconnect the adb shell. or did i got somethig wrong here?
i know about this, but it's not finished yet. the power button for example cannot be used to confirm for example, which would be useless on-the-go. (how has a keyboard all the time :silly: )
http://forum.xda-developers.com/memo-pad-7/help/how-to-dual-boot-me176cx-part-1-t3183437
sorry for all the questions, but i got this device 2 days ago and i don't know anything whats going on under to hood - and no: i'm not a android/linux noob - i just won't full brick my device
and also, what about a nandroid backup over adb, is there a legit way to archive this?
thanks in advance
EDIT: i tried the temporary recovery, but i'm unable to do any kind of backup. maybe the paths are all incorrect (?)
anyway, i took the risk of a bootloop and installed the xposed framework and succeed
i also found out that i can try to "stop" android before it bootloops again -> adb -d shell stop and do a manually restore over the command line
Click to expand...
Click to collapse
Hi GhettoGirl,
(first of all: I am no native English speaker...so some things may sound wrong either technically or otherwise.
But they are not intended to do so.... )
I started with my ME176CX not long ago and I am still a newbie when it comes Android (haveing some experience in Linux though). Mis012 and cyandro helped me a
LOT to get more understanding and to root my tablet.
I rootet my ME176CX with the temporary cwm/twpr recovery method, which does other wonderful things possible too.
You will find links to its description here (a BIG thank you to cyandro and Mis012) and it is the thread from which I learned
so much:
http://forum.xda-developers.com/memo-pad-7/help/asus-memopad-7-me176cx-1e041a-otg-t3156922
(The title of the thread becomes a little misleading in the meanwhile...)
The base problem (currently) with this tablet is: The bootloader is locked.
This means:
If you power on the tablet roughly the following steps happens:
1) The CPU gets power, erases its own internal RAM and registeres, does some other initializing
and finally executes a super mini mini program, which is often in its own ROM.
2) This little program call UEFI (its kinda "BIOS replacement" -- think of the BIOS screen of PCs when pressing F2/ESC/DEL while booting)
3) The UEFI looks into its configuration and calls the bootloader.
4) Finally boots the Android Linux kernel BUT only a kernel which is cryptographically "signed" by ASUS. Thats why it is called "locked".
By the way: You can get into UEFI, if you attach a powered OTG hub and an USB keyboard to the tablet, power it up and hammering "F2" while
it boots. Be careful! For the first: Dont change anything!
A permanent TWPR/CWM is possible, if the bootloader would boot TWPR/CWM as a kind of "kernle replacement". But since both are not
signed by ASUS...sigh.
The temporary CWM/TWPR method (and now some not-so-sure-knowledge follows) tricks the bootloader (called "fastboot") in thinking, that some
factory maintenance has to be done (like partitioning the EMMC internal flash) and therefore allows to insert a not signed boot image temporarly
into the system and boot that instead of the kernel: And if these "recovery images" are not recovery images as such but say TWPR or cwm, the
system boots into those.
And it feels and act identical (until now I did not find a difference) to a permanent TWPR/CWM recovery ... but it only can be initiated with the help of
a seconde computer (or another Android smartphone/tablet with is rooted and has a Terminal Emulator and adb/fastboot installed.
Bootloops: You are completly right here, GhettoGirl...as long the power is there, it boot loops and boot loops and....
But you already found your way into the system: COOL!
WIth the same temporary twpr/cwm method you can start TWPR and do an Nandroid backup (whole system backup) and put that onto
the external SDcard.
BUT! ATTENTION! I dont know, whether the kind of EMMc flash is important in this process, and I dont know, wheter TWPR currently don't supports
the ME176CX. The locked bootloader may the reason or an incompatible/currently not supported EMMc flash. I did a Nandroid backup but I dont test
to restore it!
I dont understand, why it does not work for you: Of what size are your SDcard?
Another way, which may be better in this moment is to backup all user data with Titanium Backup to the external SDcard. If anything fails: Reflash the last
Lollipop ROM (not the upgrade...the whole thing) with the temporary TWPR/CWM method and then install Titanium backup again and restore all user data.
This way was also NOT tested by me.
May be someone can comment on this? Mis012? Cyandro?
What Mis012, cyandro and me are trying to to do is to insert an UEFI bootmanager in the boot sequence BEFORE the locked bootloader. With this bootmanager
it should be possible to select either another Linux kernel (another non-locked bootloader) to boot a free and open Linux distro of your choice or even things
like Windows...or TWPR/CWM or Cyanogenmod (if one will be available...)
Since this is a work in progress with some real problems to clearify, this is currently not finished.
And: Only questions will lead to answer. Therefore: ASK!
And I have also a question: Do you use Linux or Windows with your PC?
HTH!
Best regards,
tuxic

thanks for the useful info ?
and i'm a pure linux user, i literally don,t know anything about windows
my current distro is opensuse x86_64

GhettoGirl said:
thanks for the useful info
and i'm a pure linux user, i literally don,t know anything about windows
my current distro is opensuse x86_64
Click to expand...
Click to collapse
...me too. The only windows here are those made of glass...
Have fun!
tuxic

How to Root my N6 w/o PC?

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!

shabydog said:
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
Click to expand...
Click to collapse
AFAIK you will need a pc to 1)unlock your bootloader and 2)flash TWRP. After that the rest can be done locally. I also never used any toolkit. Making it easy is making it more dangerous IMHO.

Droidphilev said:
I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Click to expand...
Click to collapse
Second that.
shabydog said:
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Click to expand...
Click to collapse
So at least once you need to connect your phone to a desktop computer. It can be practically running anything, within reason of course: Wiindows. Mac OSX, Linux (almost any distro).
You need to unlock your bootloader with one command, but a warning here: Unlocking the bootloader will erase everything from your phone..
Then you need to install a custom recovery, preferably TWRP. After that everything can be done from the phone itself. Well at least until you soft brick it somehow, then you'll might have to use the PC again.
Also two things:
1. No OTAs for rooted phones
2. Don't lock your bootloader if you want to mess with it, because with a locked bootloader, and Enable OEM Unlocking set to off, and without TWRP, if you soft brick it accidentally, you are boned.

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use?
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
And i really prefer to do it on the device and not by ADB commands.
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!

shabydog said:
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
Click to expand...
Click to collapse
Well, you still will have to unlock it, if you want root, or want to flash a custom recovery.
Sent from my Nexus 6 running cyosp using Tapatalk

shabydog said:
......I really don't like the issue of trying to set the drivers of fastboot/google and so on!
Click to expand...
Click to collapse
Than do not 'root' your phone.

hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:

simms22 said:
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
Click to expand...
Click to collapse
Ha ha, or I don't want my birthday to be on the day I was born every year ?

I can recommend the NTRT, the Nexus Telepathic Rooting Tools.

OK.
I want to do that with a toolkit, only bcs it install the drivers.
What Is the most recommended and easiest to use?
I do looking for the 1 click do all.
Does NTRT do that?
Thank you all.

we are eventually goung to have a "my n6 is bricked, how do i fix it with one click" thread here. seriously though, thats what happens when you use toolkits, but do no real research about modding your device.

Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Sent from my Nexus 6 using Tapatalk

shabydog said:
Could anybody guide me through the steps, if needed?
Click to expand...
Click to collapse
<prev> step <next>

simms22 said:
seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Click to expand...
Click to collapse
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
wtherrell said:
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Click to expand...
Click to collapse
It is fairly enough to read directions and slowly-slowly.
NLBeev said:
<prev> step <next>
Click to expand...
Click to collapse
Thanks!
==========================================================
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?

shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
Click to expand...
Click to collapse
i agree with you. if there is somebody who knows the ins and outs already, a one click root would be great. and there will be. problem is that marshmallow just came out, and a few things have changed, like like yoe also need a custom kernel to have root on marshmallow.

shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
It is fairly enough to read directions and slowly-slowly.
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
Click to expand...
Click to collapse
There is a reason you're pushing this topic, and I'm quite sure it's because you would feel safer, if there was a tool that did the scary things instead of you. Well, there's no such tool. If you were willing to search XDA, you would find out that the first two weeks after Marshmallow came out were about people bricking their Nexus 6s with toolkits. Then the toolkit got updated and suddenly it knew that is has to flash a modified boot.img too for the root not to brick the phone. But for two weeks it didn't know, because it wasn't necessary for Lollipop. And it will only work until the next security update comes out. And that's once a month.
Meanwhile those who were willing to use the search function, and learned the five minute procedure, were able to update their rooted phones to the next security update and were able to root it as soon as the new modified boot image came out.
And this above is not something somebody will put in a help, or instructions for future updates.

Actually, this is my first time and I was able to do it pretty easily.
fastboot devices
fastboot oem unlock
my bootloader was unlocked within 30 seconds of turning it on.
then, you can easily root via CF Auto root. Just put it into fastboot then doubleclick on the windows, then root, etc....
or.............go into fastboot flash recovery twrpxxxx.img, then it always offers to run SuperSU, and you get custom recovery and root at the same time, etc......
actually the biggest pain is unlocking the bootloader. My Galaxy S4 already was unlocked, so all I did was use goomanager, flash TWRP which always offers to run SuperSU if you don't have it.
Pretty easy, I did unlock bootloader, root, and custom recovery in 10 min.
---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------
............................Then I got sick of stock Google's ROM in 15 min and wiped it and put a custom ROM instead.

Thank you all so much...
@mikeprius
Thank you so much for the info'!
But, could you plz write more details? such as:
1. How did you installed the drivers? (from my expirience, many times the pc dosent install this easily).
I just need the Google oem driver and that's it?
2. When drivers was set - did you made anything in your phones settings? Which?
3. What did you had to do before pushing the files? (Like...put all the files in the same folder? *which files?)
4. And then entered to fastboot mode and typed in these commands in pc:
fastboot devices
fastboot oem unlock
Regarding your last sentence ("or...."):
If i just flash the recovery via fastbot mode I can enter to twrp recovery and it offers to flash the SuperSU?
Sounds to me the best option.
Thanks!

1. The drivers were set from a previous device, so I didn't have to set them, but they can be downloaded and set though.
2. You need to enable developer options and select OEM unlock and USB debugging.
3. I didn't push the files, I just had them on my computer and ran fastboot commands.
4. Those commands are to unlock the bootloader.
There are a lot of different ways to do the same thing (Root, custom recovery, unlock bootloader)
1. Run CF Auto Root on a locked bootloader. It will unlock it automatically (Chainfire has it set that way), root, then download Flashify app and flash the latest img of TWRP.
2. Run fastboot commands to manually unlock the bootloader, flash TWRP, then use TWRP's SuperSU which will root it.
3. Run fastboot commands to unlock bootloader, run CF Autoroot which will root and load SuperSU, then flash TWRP via Flashify or fastboot.
There are many different ways to do the same thing. I actually just googled youtube videos and watched them.
TWRP has SuperSU and root built in. TWRP knows if you don't have it and offers to load it for you.
I went the scenic route just because, but presumably you can achieve all (3) using Option #1 without having to deal with fastboot, adb, etc.....Chainfire's script runs automatically.

I realy try to help people but users that run into problems because of the usage of tookits (and innability to solve problems and/or even lack the most basic knowledge needed) should ask the toolkit dev. for support imo, and not boughter users that have invested time and effort to gain that knowledge to clean up their mess. Period

bootloop with locked bootloader

Hello
So I recently brought a second hand nexus 6 for cheap since it was described as bootlooping and the owner couldn't fix it. I already have a fully working nexus 6 so decided to get this as a potential source for spares assuming I couldn't get it working to be used as a 2nd phone. Having received it today, I found that when turned on, it would get stuck at the white "google" screen and go no further than that. I can access the bootloader and the stock recovery. The bootloader is locked and since the "allow oem unlock" option has been added to lollipop (which I had not even heard of till looking into why I couldn't unlock this device), I can't seem to unlock it, so i'm at a loss. So far i've tried;
-unlocking the bootloader using fastboot oem unlock
-fastboot format cache/data (both saying the BL needs to be unlocked, even though people have said they've managed with it locked)
-flashing roms via fastboot (that obviously didn't work)
-using the "apply update from adb" option to install a stock zip from google (error "signature verification failed")
-same as above, but with custom roms (gave the error "failed to verify whole-file signature")
-same as above again ,but with the OTA of the next android version, in the hope I could continue flashing these till I reached a major one and then it would work (came back saying "system partition has unexpected contents)
-making a nandroid of my working phone, and making a bootable zip of that ("signature verification failed")
I've basically reached a point now where I imagine it's probably not ever gonna work and i'm gonna have to give up, but I figured requesting here can't hurt and I don't wanna give up knowing that something could work, I just never found out about it. I also can't help but think that given I have a working nexus 6, there must be something I can do with that to make the new one work (the only idea I had was the nandroid of it, but there may be something else)
Cheers
Cameron

That phone is not pining for the fjords. It's an ex-phone.

istperson said:
That phone is not pining for the fjords. It's an ex-phone.
Click to expand...
Click to collapse
What do you mean by "pining for the fjords"?
I wondered, is it possible to use wugfresh to push system files to the device (while removing old ones) making it seem to have a clean system partition, then try the ota again via adb sideload. Even if i took the system files from my functioning nexus. The faulty one is on lmy47z at the moment.

call-of-monst3r said:
What do you mean by "pining for the fjords"?
I wondered, is it possible to use wugfresh to push system files to the device (while removing old ones) making it seem to have a clean system partition, then try the ota again via adb sideload. Even if i took the system files from my functioning nexus. The faulty one is on lmy47z at the moment.
Click to expand...
Click to collapse
http://www.google.com/search?q=pining for the fjords
And, I'm sorry, but no, you can't do more with toolkits than with adb and fastboot. Toolkits are just front-ends for those two tools.
You have already tried everything possible, and since the bootloader is locked and you can't boot into Android to enable unlocking, all you have is just spare parts. I'm sorry.

istperson said:
And, I'm sorry, but no, you can't do more with toolkits than with adb and fastboot. Toolkits are just front-ends for those two tools.
You have already tried everything possible, and since the bootloader is locked and you can't boot into Android to enable unlocking, all you have is just spare parts. I'm sorry.
Click to expand...
Click to collapse
Thanks for the help, I've never heard of that phrase before and I thought i had heard them all given what my mums like
When the phone is in recovery, when the update via adb is selected, the phone is detected as an adb sideload device when "adb devices" is entered. Can I push/pull system files when it's detected as sideload? Because I noticed wugfresh supports pushing/pulling of files between the device and pc, but I wasn't sure if it could do system files when the device is detected as sideload
Thanks for the help, i would really like to make it work, and given its not exactly a device I rely on, I'm happy to spend more time working on it and trying more unusual/new ideas
Cameron

call-of-monst3r said:
Thanks for the help, I've never heard of that phrase before and I thought i had heard them all given what my mums like
When the phone is in recovery, when the update via adb is selected, the phone is detected as an adb sideload device when "adb devices" is entered. Can I push/pull system files when it's detected as sideload? Because I noticed wugfresh supports pushing/pulling of files between the device and pc, but I wasn't sure if it could do system files when the device is detected as sideload
Thanks for the help, i would really like to make it work, and given its not exactly a device I rely on, I'm happy to spend more time working on it and trying more unusual/new ideas
Cameron
Click to expand...
Click to collapse
Here it is how sideload works. But as I understood it's only for updates on working phones:
http://www.androidcentral.com/how-manually-upgrade-your-nexus#slide5

switch on "s off" for htc one min 2 with kitkat 4.4.2

Hi everybody.
I'm really frustrated for getting access on my sd card on my htc one mini 2.
Hope anyone can help!
Here are my specs:
HTC One min 2
Kitkat 4.4.2
HTC Sense 6.0
HBoot 3.19
(Don't know what else is necessary )
Here is what I've tried so far:
1. Rooting the device and unlocking the bootloader (successful)
2. Installing SuperSU (successful)
3. trying sd fix and sd kitkat fixer (not successful)
4. changing the platform.xml (not successful)
Although the apps sd fix and sd kitkat said the operation has been successful the write protection was still present.
After some more research I found out the crucial part is the parmeter "S" and that it is set on "off" so in the boot menu "s-off" is indicated.
As I just know that this parameter is protecting important areas of the system and it looks like touching this is very risky, I want to be sure what to do.
So if anybody has an idea how to proceed or has an alternative way instead I would be so grateful!!
Thank you in advance!!
Frank

Sunshine will S-OFF your device.

herakles33 said:
Hi everybody.
I'm really frustrated for getting access on my sd card on my htc one mini 2.
Hope anyone can help!
Here are my specs:
HTC One min 2
Kitkat 4.4.2
HTC Sense 6.0
HBoot 3.19
(Don't know what else is necessary )
Here is what I've tried so far:
1. Rooting the device and unlocking the bootloader (successful)
2. Installing SuperSU (successful)
3. trying sd fix and sd kitkat fixer (not successful)
4. changing the platform.xml (not successful)
Although the apps sd fix and sd kitkat said the operation has been successful the write protection was still present.
After some more research I found out the crucial part is the parmeter "S" and that it is set on "off" so in the boot menu "s-off" is indicated.
As I just know that this parameter is protecting important areas of the system and it looks like touching this is very risky, I want to be sure what to do.
So if anybody has an idea how to proceed or has an alternative way instead I would be so grateful!!
Thank you in advance!!
Frank
Click to expand...
Click to collapse
The SD card problem doesn't need S-OFF. You can try installing Xposed framework. It has a module called "Kitkat SD Card Full Access", which can be used to rectify your issue.
If you'd also like your downloads to be on the SD card, you can use the module "Downloads2SD" and set the path

@ tarx1000: thx I heard about it but not yet sure about entering my paypal login details..and if it really works out..but I think it is the only way left...
@aligahr: thx I tried installing Xposed framework but it needs sdcard to install..and so we are back on the original problem

herakles33 said:
@ tarx1000: thx I heard about it but not yet sure about entering my paypal login details..and if it really works out..but I think it is the only way left...
@aligahr: thx I tried installing Xposed framework but it needs sdcard to install..and so we are back on the original problem
Click to expand...
Click to collapse
use the recovery method to install it

csoulr666 said:
use the recovery method to install it
Click to expand...
Click to collapse
@csoulr666: first of all sorry for mixing up your user name. Second thank you so much !! This was the best tip ever, was so easy to do.:good: Thanks again!
Have a good Christmas!! Cheers Frank

Request for Root on NWS2.170620.003 Security Patch level July 1, 2017

hi,
i am new in these forums,
i searched over the web and also tried many root methods, but none worked.
root method for NXH19X is not working for me i tried multiple times.
the main error i am getting is "unable to mount /system; no such thing found" in TWRP
i also tried multiple Supersu files official ones and unofficial ones as well.
after some research i found out about new file system squashfs FS
then i tried this rom which supports EXT4 File System
here is link: https://forum.xda-developers.com/g-watch-r/development/rom-ext4all-g-watch-r-skin1980-t3589917
but it didnot work out as well,(get boot looped)
so flashed stock rom and now on latest update as told earlier,
so its my request, i need help. if someone please come up with any working method to root latest stock rom and security patches(build number and security patch in title)
why stock rom?
i personally like stock rom and it is working fine for me.
why root?
i have root on my phone (one plus one), i felt like i am unable to use my watch on full potential without root.
and we all like root that's why we are here right
thank you
(i actually don't know the how to write any threads so bear with me please) :fingers-crossed:

This post of mine will work. Tried on many roms and it works.
Some play store apps says i dont have root but I do as the app i use that needs root works : https://play.google.com/store/apps/details?id=com.skin1980.buttonremap
So use this procedure :
https://forum.xda-developers.com/g-watch-r/development/nxh19x-boot-img-rooted-t3651039
The problem is that u need a TWRP for squash images which you can find in the mentioned post

Grumps said:
This post of mine will work. Tried on many roms and it works.
Some play store apps says i dont have root but I do as the app i use that needs root works : https://play.google.com/store/apps/details?id=com.skin1980.buttonremap
So use this procedure :
https://forum.xda-developers.com/g-watch-r/development/nxh19x-boot-img-rooted-t3651039
The problem is that u need a TWRP for squash images which you can find in the mentioned post
Click to expand...
Click to collapse
hi
i tried your given method,
twrp seems to work fine first time,
but i lost twrp as soon as i boot into system,
some how system replace recovery with default one each time watch booted into android itself,
however i am able to boot into recovery, when tried directly from fast-boot after flashing it,
but still unable to obtain root,
the zip files seems to flash perfectly, but there is no su in app drawer,
thanks for your support, but i think new version makes it harder to gain root,
and i am fine without root i can live without it.
thanks again.

Talwinder8872 said:
hi
i tried your given method,
twrp seems to work fine first time,
but i lost twrp as soon as i boot into system,
some how system replace recovery with default one each time watch booted into android itself,
however i am able to boot into recovery, when tried directly from fast-boot after flashing it,
but still unable to obtain root,
the zip files seems to flash perfectly, but there is no su in app drawer,
thanks for your support, but i think new version makes it harder to gain root,
and i am fine without root i can live without it.
thanks again.
Click to expand...
Click to collapse
There is no SuperUser for android wear watches. It will automatically allow root access for all apps that request it...

Grumps said:
There is no SuperUser for android wear watches. It will automatically allow root access for all apps that request it...
Click to expand...
Click to collapse
ok i see, but how to confirm, it is rooted because i don't want to purchase that 'Button Re-Mapper App', before confirming,

Talwinder8872 said:
ok i see, but how to confirm, it is rooted because i don't want to purchase that 'Button Re-Mapper App', before confirming,
Click to expand...
Click to collapse
ok boom , i got it ,
i am such a noob, didn't bother to check it with root check now we are good to go, cool
thanks a million guys :good: :good:
ok i don't know how to attach screen shot,

Talwinder8872 said:
ok boom , i got it ,
i am such a noob, didn't bother to check it with root check now we are good to go, cool
thanks a million guys :good: :good:
ok i don't know how to attach screen shot,
Click to expand...
Click to collapse
Dont worry be believe you haha