The zenwatch will be out soon.
Every other wear prior to this one so far has had roms made directly by goog, I dont expect this is any different.
TheManii said:
Android wear runs, well android.
I would like to request that someone that has a wear to dump the rom that is preinstalled on it, and to make note if there it prompts for an ota on first setup.
I don't know how to enable adb on it, but I would expect that it would be available, for the moment merely doing a
Code:
adb pull /system
will be as much as anyone can expect.
In the event it actually supports fastboot, I'd also like to request a
Code:
fastboot get-var all
Click to expand...
Click to collapse
Here's a guide on enabling adb on wear, it's not specific to any one device:
[How-To] Android Wear: Enable Debugging, Take Screenshots, Unlock The Bootloader, And Root The LG G Watch
You won't be able to root it however for the time being, you need a custom recovery specifically for your device.
There's already an ota out, so if you make a dump please make note of if you already got the ota or not.
Related
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Tranquility. said:
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Click to expand...
Click to collapse
I'm not a dev, but I have some experience rooting the N7 (2012 and 2013).
1) Well, it looks like 6.0 isn't coming to the N7 2012, so there is a good chance support for major versions will be dropped soon (within the next year?). They might continue to release patches and security fixes for 6.x a year or two after that, like they appear to be doing with the N7 2012, but this is all speculation. There are probably number crunchers looking at the sales figures and survey results to gauge interest, and there were some rumors recently of a new N7 possibly in the works. Those will both factor into whether support will continue.
2) You will get a notification, but everything I've seen has indicated that the install will fail (won't brick the tablet, but will just show an error and reboot to its previous state). What I think most people do, including me, is just flash the stock image in 'no wipe' mode and re-root after the update. You can also sideload the OTA update, depending on rooting method (I think, but haven't done this myself). Lastly, if you don't mind reconfiguring all your apps or if you have a good backup scheme, you can just do a fresh install then root. I have never had trouble flashing stock in no-wipe and re-rooting, but I've heard some people have had problems. (It's worth noting that if your bootloader hasn't been unlocked, you will have to wipe the device anyways. The unlocking survives flashing, so it's a 'one and done' thing. You only really need to lock it again if you're sending it in for warranty service.)
3) Wug's toolkit is currently borked for most people (version 2.0.6), so avoid it until the thread in the N7 development subforum has some success stories. Also, rooting in Marshmallow is possible, but seek out instructions specifically for M and use the latest versions of any linked utilities (like SuperSU and TWRP). I used Wug's toolkit 90% of the time for updating and rooting, and when it works, it's a breeze. It might be worth waiting for it to be updated to address the current issues. You can use the previous version to do some basic things and as a launchpad for manual tweaking, but the main, one click and done options will not work - I tried and was greeted with a bootloop due to an out of date SuperSU. But, in version 2.0.5 you can unlock the bootloader and flash the latest stock (haven't tried the U or V versions, but MRA58K worked fine). From there you have to root mostly manually, but there are shortcuts for some of the steps in the Advanced Utilities section.
4) It's always possible to brick a device, but it's very rare. There are 2 kinds of 'bricks'. 'Hard' brick is what most people worry about - something happens that prevents access to even the lowest level of the device. It's as if there was a hardware failure. 'Soft' bricking is what less tech literate people equate to hard bricking because to them the device is useless. In reality, it's a software issue that prevents some early stage of the boot up process. It is almost always recoverable with enough time and research. In basic computer terms, hard bricking is failing to post and soft bricking is failure of the OS to load (basically, though there are nuances). With root, you have access to everything and you're trusting whatever you install that takes advantage of that power to use it wisely. An ad blocker shouldn't need to adjust the CPU voltages. This is rare if you don't intend to overclock or mess with low level hardware tweaks. It is much more likely, but still pretty rare, to soft brick the device, which means you just have to reflash the system image. Worst case is you have to wipe the device and start over, or spend a few hours researching exactly what caused it.
Hope that helps. I'm not an obsessive ROM flasher and my experience has been only with Nexus devices, but these are my impressions.
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Tranquility. said:
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Click to expand...
Click to collapse
Android M is the last official update for N7 2013, the first gen N7 is done with updates. Once rooted you will not get any OTA updates anyway.
Flashing usually takes about 3-4 minutes. Booting up can take up to 10-15 min.
Just don't root on M until a stable method has been discovered.
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
You can check the marshmallow and the beta thread for updates. http://forum.xda-developers.com/apps/supersu
Tranquility. said:
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
Click to expand...
Click to collapse
You can root 6.0 pretty easy if you have fastboot installed. I've done it and can confirm it works. You just need to download the ElementalX-N7 kernel and SuperSU to your device then flash TWRP in fastboot then flash the kernel and SuperSU in TWRP. There are threads on here I believe with instructions to help you. If you need any help you can message me.
The beta SuperSU and elementalx method worked great for me and seems totally stable. I'd recommend learning fastboot/adb as mentioned. That has saved me a few times from the dumb things I've done messing around with root access.
Sent from my Nexus 7 using XDA Free mobile app
Rooting
As I mentioned in a previous post rooting using TWRP, SU I don't think fully roots
the device. When I loaded Multi-Rom, it installed in the usual fashion but only boots to the TWRP recovery utility.
In the past, one could globally root the device but the problem appears new.
Kurt
I just want to root my Android devices to update something on the phone, could you help me if you know how you do that. Thanks in advance.
Root Guide: How to Root Android Device with Root Genius
What is Rooting on Android and Why We Want to Root?
Most Android users are annoyed by these system default applications, which are not really being used but can not be deleted because, if so, the Android operating system will not run smoothly and may cause an interruption. Rooting is a process that allows users to access the main software code of the device's operating system and allows you to modify or change something based on what you want, and how you want the phone application to work for you. Safe to say that this is Android corresponding to Apple jailbreak. After rooted, you can no freely install apps that you think will enhance your mobile experience. After all, that is what we all wanted, to get the most of what we have.
1.Benefits of rooting
2. Risks of rooting
How to Root Android Device with Root Genius
Note: You are not allowed to root your Android phone with Mac. However, when you are intended to root your Android phone and then use our software -FoneDog Android Data Recovery for Mac version, you can directly root on the Android phone with the below method.
Step 1. Connect Your Android Phone to Windows
Step 2. Allow USB Debugging
Step3. Start to Root Your Phone with Root Genius
Hope it can help you sooner.Good Luck.
Debini said:
I just want to root my Android devices to update something on the phone, could you help me if you know how you do that. Thanks in advance.
Click to expand...
Click to collapse
are these guides ure trying to post?
or are u trying to root something?
the sprint lg g5 is currently unrootable. and I believe u have posted in the wrong threads have you not or do u have a g5?
None of these one click apps apks exes work to root g5. Due to locked bootloader.
Hi, I would like to root my Moto Z2 Play but I don't want to unlock bootloader, because all of my data will be actually formatted and I don't really want to set up things again.
With that, I would like to ask if there is any option to root my phone straight from Android UI.
So I don't have to use any PC to root this phone.
Edit:
Actually with rooting come on place one important question.
This question is about: Is the phone able to receive updates released by manufacturer to moto Z2 play?
I'm asking because when I was rooting my Samsung phones on every single of them when they are rooted they are unable to receive updates by manufacturer so I literally had to plug the phone into my PC and Force updated it via Samsung provided program (Kies).
This was really painful so I am asking just before I will actually root it because I want the stock ROM and all of its official updates.
So I'll be really thankful with any answer on that question.
To root you must unlock the bootloader.
And you will receive OTA's, but if you install those, the phone will most probably brick. So, don't even try to install them.
As long as there is no vulnerability found in Android 8 that could actually be used to root, there is no other way than to open the bootloader which enforces a factory reset.
But if rooted properly with Magisk and as long as you only boot TWRP but never install it, OTAs should work. At least the only reason for bricking I know is when you try to upgrade after a downgrade since the updater seems to not check the bootloader. And with a downgrade to a version with an older bootloader something goes haywire which bricks the device on next update and you'll need a blankflash to fix that
If anyone has any information on this latest update Components let me know please because, I have yet to figure out how to disable OTA updates, but a user on here might’ve given me a way. I will test on ADB soon.
I am already on latest OS 5.2.7.7 because of STUPID OTA. But now I have another update from yesterday called Components.
Will this Components update ruin anything that the OP from the root thread has created?
I want to try rooting on 5.2.7.7 soon but I’m just hoping this other update didn’t ruin my chances.
At this point, does it even matter anymore? I’m already updated to every single latest update available on my Sloan box 2nd gen. I can’t do much root wise because I’m afraid to open my device and I’m stuck with a bull**** rom and Home Screen. Can’t even add a custom launcher as Amazon also broke this with their firmware updates...
G S W said:
If anyone has any information on this latest update Components let me know please because, I have yet to figure out how to disable OTA updates, but a user on here might’ve given me a way. I will test on ADB soon.
I am already on latest OS 5.2.7.7 because of STUPID OTA. But now I have another update from yesterday called Components.
Will this Components update ruin anything that the OP from the root thread has created?
I want to try rooting on 5.2.7.7 soon but I’m just hoping this other update didn’t ruin my chances.
At this point, does it even matter anymore? I’m already updated to every single latest update available on my Sloan box 2nd gen. I can’t do much root wise because I’m afraid to open my device and I’m stuck with a bull**** rom and Home Screen. Can’t even add a custom launcher as Amazon also broke this with their firmware updates...
Click to expand...
Click to collapse
Doesnt do nothing apart from modifications to cloudfront server urls and some of the /system files which prevent adb/accessibility of custom launcher replacements and ftvlaunchx bypass apks etc etc .
Basically the 2nd part of the 5.2.7.7 fcks the custom launcher compatibility .
To get round it , root the device install custom launcher ...
pm disable com.amazon.tv.launcher
wait 5 seconds
pm disable com.amazon.firehomestarter
https://www.xda-developers.com/dirty-pipe-root-demo-samsung-galaxy-s22-google-pixel-6-pro/
March 15, 2022 7:40am Comment Skanda Hazarika
PSA: Dirty Pipe, the Linux kernel root vulnerability, can be abused on the Samsung Galaxy S22 and Google Pixel 6 Pro
What happens when a Linux privilege-escalation vulnerability that also affects Android gets disclosed publicly? You got it! Security researchers and Android enthusiasts around the world try to take advantage of the newly found problem to create an exploit, which can be used to gain advanced access to your device (such as root or the ability to flash custom images). On the other hand, device makers and a few determined third-party developers quickly take the responsibility to patch the backdoor as soon as possible.
This is exactly what happened to CVE-2022-0847, a vulnerability dubbed “Dirty Pipe” in Linux kernel version 5.8 and later. We talked about the exploit in detail last week but didn’t explicitly cover the potential abusing scenarios on Android. Now, XDA Member Fire30 has demonstrated an exploit implementation around the kernel flaw that can give the attacker a root shell on the Samsung Galaxy S22 and the Google Pixel 6 Pro.
The key point here is that you don’t need any kind of unlocking or other trickery to make it work – the Dirty Pipe exploit allows the attacker to gain root-level access on the target device through a reverse shell via a specially crafted rogue app. At the time of writing, flagships like the Google Pixel 6 Pro and the Samsung Galaxy S22 are vulnerable to the attack vector even on their latest software releases, which shows the exploit’s potential. Since it can also set SELinux to permissive, there is virtually no hurdle against unauthorized control over the device.
From the perspective of the Android modding scene, Dirty Pipe might be useful to gain temporary root access on otherwise difficult-to-root Android smartphones, e.g., some regional Snapdragon variants of the Samsung Galaxy flagships. However, the window won’t last long as the vulnerability has already been patched in the mainline Linux kernel, and OEMs will probably roll out the fix as part of the upcoming monthly security updates. Nonetheless, stay away from installing apps from random sources for the time being to protect yourself. In the meantime, we expect that Google will push an update to the Play Protect to prevent the vulnerability from being exploited via rogue apps.
Source: Fire30 on Twitter
Via: Mishaal Rahman
Click to expand...
Click to collapse
This isn't necessarily bad news if the exploit is used non-maliciously. Could be beneficial for Verizon customers looking for a way to gain root.
westhaking said:
This isn't necessarily bad news if the exploit is used non-maliciously. Could be beneficial for Verizon customers looking for a way to gain root.
Click to expand...
Click to collapse
Could, yes. I'll remain pessimistic that it'll actually happen, and of course, it'll take someone willing to actually do the work. A very limited time to do it doesn't help unless someone with a spare Verizon device keeps it off the network/internet until something is implemented.
westhaking said:
This isn't necessarily bad news if the exploit is used non-maliciously. Could be beneficial for Verizon customers looking for a way to gain root.
Click to expand...
Click to collapse
I was just reading about this & that exact thought came to mind. The root access gained seems to be temporary, but if you can write to usually read only file system, could you not theoretically write a Magisk boot image (using dd, or in Magisk Manager itself?) or even toggle the OEM unlock switch via a SU shell command unlock the phone?
I'm not very well versed on how the mechanics behind OEM unlock switch in developer settings works & or how Verizon locks these phones down (UK based), but I would assume that it could be useful to help find a exploit for phones running any pre-April 22 update.
Edit: from my limited knowledge, can you not sideload a earlier OTA on Verizon devices? I know you could do so with Pixel 3 and earlier, but I haven't been following it too closely with later devices.
DanielF50 said:
or even toggle the OEM unlock switch via a SU shell command unlock the phone?
Click to expand...
Click to collapse
I've never heard of a shell command that could toggle the OEM unlock. That doesn't mean it hasn't existed, but I doubt it, otherwise, I would think on all the Verizon devices I used to have, and just root threads in general I should remember anyone making the suggestion, even if it required temporary root first.
DanielF50 said:
Edit: from my limited knowledge, can you not sideload a earlier OTA on Verizon devices? I know you could do so with Pixel 3 and earlier, but I haven't been following it too closely with later devices.
Click to expand...
Click to collapse
I was under the impression that all phones with the bootloader locked that you could never, ever downgrade via any method. Also, OTAs generally use deltas/differencing to patch known good files of version A to version B, and B to C, so applying a version B OTA to a device that's on version C would fail because the files on the device are the wrong version.
Like (let version A be represented with the value 1, B with 4, and C with 9):
Device is on version B, so "4".
OTA to go from B to C comes.
OTA says is device file "4"?
Yes! Add 5 to the file, it's now "9".
and then
Device is on version C, so "9".
Try to put the B to C OTA on the device.
OTA says is device file "4"?
No! It's "9", quit OTA process.
This might be simplified, and anyone correct me if I'm wrong, but this has definitely been the case some and I believe almost all, if not all, the time. The OTA files can be smaller that way because they don't contain replacement files. They only contain what the difference is between the old file and the new, which is usually much smaller than the entire file.