yashsingh1/xdaforums huggingface dataset:
[SuperSU] KevinX8:
Follow this guide to flash SuperSU on the latest version of android wear for your watch, it should have the same OS compatibility as normal SuperSU and should work all the way upto android 7.1.1

(from PC)

1.Unlock the bootloader if not already unlocked

(Make sure to set up device with phone after unlocking bootloader otherwise no boot!)

adb reboot bootloader
fastboot oem unlock

2.flash TWRP for your device (

REQUIRES read only access to system!

, will post working builds in post below)

fastboot flash recovery recoveryname.img

3.Download SuperSU with busybox YDS included HERE and move it to watch with adb push to /sdcard while TWRP is booted and then install as normal zip

adb push nameofzip.zip /sdcard/

4.

IGNORE SYSTEM NOT INSTALLED

Boot watch to system and Now your root apps from 5.1 should work perfect. THERE WILL BE NO SUPER SU APP, IT HAS NOT BEEN PORTED TO ANDROID WEAR

REMEMBER squashfs is read only even with root so don't bother trying to modify system files like the build.prop.

If you would like to modify system use any Linux distro and unsquash the system then resquash it (will make guide if enough interest)

If you would like to change pixel density perform this command in either adb shell or a terminal emulator:

wm density <dpi>

Please leave thanks if it helped!
[SuperSU] KevinX8:
Feel free to submit links to twrp for squashfs watch with model name, codename and original developer's name

Will add them to this post

THESE ARE THE ONLY BUILDS THAT WILL WORK UNTIL TWRP IS UPDATED!

I DID NOT CREATE ANY OF THESE BUILDS!

LG G Watch dory (courtesy of [MENTION=3991724]rbox[/MENTION])

LG G watch R lenok
[SuperSU] OfficerJimLahey:
In regards to Busybox on Rails, I compared the link provided and Google Play (which I assume is latest), they are the same versions. Is there a trustworthy place to find the old version suggested?

Not sure if I will need it, just covering my bases. Upgrading to 6.0.1 tonight.

Thanks.
[SuperSU] itsthamessenger:
First post and Thanks to you!!!

This is my first post in the community, i thank you all for all you do! I have successfully rooted lg g watch with android 6.0.1 build mec23d using your method. busy box pro installed after uninstalling superuser.
[SuperSU] KevinX8:
Oh I thought it was an older version will edit that as the latest did not work On 5.1.1 wear but I guess it those on 6.0.1
[SuperSU] KevinX8:
Glad I could help! I was not aware the busybox pro worked on wear is it the one by stericson?
[SuperSU] itsthamessenger:
Yes it is!
[SuperSU] KevinX8:
Thanks for the info will add to post
[SuperSU] OfficerJimLahey:
Unless I am missing something, system access is needed for the LG G Watch.

Tried with TWRP 3.0.0 and 2.8.7, SuperSU 2.65 flash was successful in spite of /system not mounting (notice was given in red letters), rebooted, with same result across both versions:

joel@cybaryme:~$ Build/android-sdk-linux/platform-tools/adb uninstall eu.chainfire.supersu
Failure [DELETE_FAILED_INTERNAL_ERROR]
joel@cybaryme:~$ Build/android-sdk-linux/platform-tools/adb install Downloads/BusyBox%20On%20Rails_5.1.74_apk-dl.com.apk
1087 KB/s (2287614 bytes in 2.053s)
pkg: /data/local/tmp/BusyBox%20On%20Rails_5.1.74_apk-dl.com.apk
Success
joel@cybaryme:~$ Build/android-sdk-linux/platform-tools/adb shell
shell@dory:/ $ su
/system/bin/sh: su: not found
127|shell@dory:/ $

Looks like SuperSU is not even bothering with system-less mode:

http://pastebin.com/T7k0cWHv
[SuperSU] KevinX8:
Huh I used a modified version of the latest TWRP from a member that allowed the system to be mounted read only as squashfs is a read only file system ie. The system image has to be rebuilt to make changes. I assumed that since supersu is now system less it those not require system access but maybe it those but I really didn't see the use of mounting it read only as it cannot make any changes to system. Will edit thread thanks for info. Link to squashfs twrp above

It is strange though the other poster managed to root without system access.
[SuperSU] OfficerJimLahey:
The third time I flashed to get the log, I attempted to mount /system as read only, since it didn't mount properly otherwise. The onscreen messages looked the same anyway...successful flash, but could not mount /system. And upon leaving TWRP, it warned that no OS was installed. Nothing different for all intents and purposes.

Thanks, I will try your TWRP and report back.

UPDATE:

Your TWRP made all the difference:

joel@cybaryme:~$ Build/android-sdk-linux/platform-tools/adb uninstall eu.chainfire.supersu
Success
joel@cybaryme:~$ Build/android-sdk-linux/platform-tools/adb shell
shell@dory:/ $ su
root@dory:/ #

Thank you! :)
[SuperSU] KevinX8:
No problem guess SuperSU those require system access to work it seems to be for SE Linux patching and also the build.prop
[SuperSU] drewski_1:
Thanks for this guide! Rooted AOK :good:

This Step 4 is to install Busybox on Rails onto the phone? or Watch?
[SuperSU] KevinX8:
Welcome and watch the whole process only requires pc and watch no phone involved. My modified supersu installer should have installed busybox on Rails app to the watch
[SuperSU] drewski_1:
got it. thanks again!! :D
[SuperSU] KevinX8:
Highly recommend everyone to get invisiblek's kernel its top notch gets rid of the horrible lag of 6.0.1's kernel And is fully supported by my root method so even better!
[SuperSU] ganovim:
Where do supersu and busybox get installed

Since the new wear has a read only system, where do the supersu and busybox get installed?
[SuperSU] KevinX8:
SuperSU is now system less if you haven't been following it recently so system access is not required also bits of supersu are stored in the kernel disk and others just at /data. Busybox is stored with the SU mounted image to /su/xbin once installed via the app
[SuperSU] cYraXx:
/moved to specific lg g watch thread
[Galaxy Note 4 Q&A, Help & Troubleshooting] kevalpatel92:
I have connected my phone to other charger one day after that my phone is not connecting with my laptop when i connect phone with laptop it only goes into charging.usb mass storage (mtp) doesnt show when i connect tha phone also fast charging also not working it gets charged with ormal speed with adaptive fast charge.did factory reset still no help.does my usb port get damaged?anyone plz help
[Galaxy Note 4 Q&A, Help & Troubleshooting] Racinghart91:
same here bro... my pc wont connect with it, it says something about the drivers.. so i downloaded kies and downloaded the drivers with that but still nothing
[Galaxy Note 4 Q&A, Help & Troubleshooting] kevalpatel92:
I had the bad port.i replaced the port .and now it works perfectly.
[OnePlus 2 Q&A, Help & Troubleshooting] _Beni_:
I know there already is a thread about cars, but it isn't that similar to mine.

I'm using the latest OxygenOS with Boeffla-Kernel and I'm connected to a Philips CE235BT car radio.

The call sound if i receive a call is really loud and i didn't find any option to change it.

Is there any app out there, which can regulate the bluetooth call volume only? Or can it be changed by editing some system files?

The playing sound of bluetooth is OK, the AudioTuner is also disabled.
[OnePlus 2 Q&A, Help & Troubleshooting] _Beni_:
It seems I just needed to reduce the volume while calling, it was at the maximum level. The level is stored and if i end the call it goes back to the music level.
[Java for Android App Development] gombomedia:
Hi, I am developing a one click root app toroot for android 4.x and above! I need the main activity! so the app has started only a button and you want to exploit (libexploit.so). can someone help me? also notes!

THANK YOU :)
[Sprint  Galaxy Note 4 General] Invisibility:
Didn't Samsung say February for marshmallow on our Note 4? Or was it March? Either way no update what so ever this month?
[Sprint  Galaxy Note 4 General] joaranna:
It was scheduled for this month.
[Sprint  Galaxy Note 4 General] t4d73:
This mo? Don't think so. The note 5, international mind you, has only just started seeing it as of yesterday so I wouldn't expect ours until towards the end of the second quarter at least. Besides you'll see an rdf pop up 1st once they actually start working on it then many more rdf versions until a final release. I'm dropping this phone the day the new g5 drops anyway. It's just uneceptible the g4 has marshmallow since Christmas along with practicality every other manufacturer except Samsung. The g5 looks to be a killer device too. Hope they really sink Samsungs ship with it honestly. Especially after the update fiasco for the note 4 last year. Typical Samsung fashion though. Rant over.
[Sprint  Galaxy Note 4 General] t4d73:
Well the g5 was released and I gotta say I'm disappointed. 5.3 in screen size? That'll just be hard to use coming from this.
[Sprint  Galaxy Note 4 General] DreamingWolf:
+1
[Sprint  Galaxy Note 4 General] DaggettBeaver:
The G5 is a two-lens modular multi-featured camera pretending to be a smart phone.

If I want a modular high-quality digital camera, I'll buy one with a couple lenses I can switch between.

I want a smart phone, and I'm happy if it has nice camera features.

Each to his/her own, though.
[Sprint  Galaxy Note 4 General] styles420:
Perhaps the release from Samsung was scheduled for this month - but Samsung releases to the carriers, at least in Sprint's case, and then the carrier does their thing with it until they deem it ready to release to their customers. Samsung doesn't set Sprint's schedule ;)
[Sprint  Galaxy Note 4 General] t4d73:
International version would probably get it 1st before anyone then if that goes ok then they would release it to the carriers. At least that's how it usually goes. I've been keeping a close eye on sammobile for that to happen so hopefully soon.
[Sprint  Galaxy Note 4 General] styles420:
Not necessarily - just because Sprint releases later than the international carriers doesn't mean that they receive it later. It's generally bad practice to openly treat some of your customers as guinea pigs for the benefit of the others, so it's more likely that Samsung sends out its generic rom to all carriers at the same time and Sprint just takes longer to add their proprietary bloat. It's also likely that Sprint waits to announce the upcoming version for the same reason xda devs don't do ETAs - because too many people take "estimate" to mean "promise" and get upset when delays happen.
[Sprint  Galaxy Note 4 General] t4d73:
Well let's hope that's the case then.
[Sprint  Galaxy Note 4 General] styles420:
It doesn't matter - either way brings us back to my original point, that Samsung's release dates are meaningless to us. We could get our update the next day, a year later, or never, with equal probability. The only useful deduction we can make from their release date is that we definitely *won't* see our update before that date, which really isn't very useful at all ;)
[Sprint  Galaxy Note 4 General] anees02:
After Google release the coming beta version of Android, i think N, then start expecting MM for Note 4.
[Sprint  Galaxy Note 4 General] sliverr7x:
You are pretty optimistic
[Sprint  Galaxy Note 4 General] DaggettBeaver:
I don't want MM.

Annoying permissions popups? No thanks.

Doze? Don't need it. I set my phone down on a wireless charger. It doesn't drain slowly, it charges.

Maybe after 8 months or more when they iron out all the issues, I'll consider it. By then, I'll probably have a new phone.
[Sprint  Galaxy Note 4 General] Invisibility:
I hope to get the s7 edge sometime soon
[Sprint  Galaxy Note 4 General] pbedard:
Already pre ordered
[Sprint  Galaxy Note 4 General] freeza:
Could you be referring to this???
[Sprint  Galaxy Note 4 General] LMMT:
You da man!
[Sprint  Galaxy Note 4 General] j_svas:
Now we can close this thread stating, Freeza has our MM :). Thanks Freeza
[Sprint  Galaxy Note 4 General] Invisibility:
How did you know ?
[G4 Q&A, Help & Troubleshooting] BALLS.:
Hi! I have H815 EUR V20d, how can i root it? I can`t find anything specific
[G4 Q&A, Help & Troubleshooting] tnnuy:
you can only do root with unlocked bootloader !!
[G4 Q&A, Help & Troubleshooting] davebugyi:
Currently only if you unlock the bootloader, and flashing SuperSU with TWRP.
[G4 Q&A, Help & Troubleshooting] BALLS.:
Thanks, but i don`t have TWRP, do i have to downgrade to install it?
[G4 Q&A, Help & Troubleshooting] turbo1781:
No, you must install TWRP in den Fastboot Mode.

https://twrp.me/devices/lgg4h815.html

Download the latest (SuperSU 2.67)

http://xdaforums.com/showpost.php?p=64161125
[G4 Q&A, Help & Troubleshooting] BALLS.:
Thanks guys, i now have root access!:good: Followed your advice and this guide: http://xdaforums.com/g4/general/unlock-bootloader-install-twrp-root-t3128241
[G4 Q&A, Help & Troubleshooting] BALLS.:
xxx
[Nexus 6P Q&A, Help & Troubleshooting] l_stevens:
In light of the recent kerfuffle between the government and Apple, I have a purely technical question (not looking for opinions) on 6P/Marshmallow encryption.

1) How does the actual encryption compare to Apple's (latest)?

2) Is it possible (within reason and with current technology) to be broken? (I know that theoretically ANYTHING can be broken, just asking if it would be practical (e.g. not take 100 years).

3) In there anything either Google or Huawei could do to assist the government in hacking a 6P/Marshmallow?

4) Is there any addon that would give the capability of n-wrong attempts/erase as in Apple. If so, would it require root?
[Nexus 6P Q&A, Help & Troubleshooting] Solutions Etcetera:
Apple is being asked to provide a method to allow a brute force attack. Having a really strong password is a good way to prevent such an attack. And the 6P's fingerprint scanner makes a strong password doable, without the inconvenience usually associated with it.

After 10 incorrect entries, Android will make you wait 30 seconds after each attempt, which makes it a slow, arduous process. I don't have the patience to determine if there is a point in this process where data is automatically wiped from the phone.

Of course you can always use ADM to wipe your phone remotely if your phone is still connected.
[Nexus 6P Q&A, Help & Troubleshooting] l_stevens:
Actually, (and I'm just speaking technically, not making political/moral judgements), fingerprint encryption does NOT stop the government from decrypting your phone. You can be legally compelled to swipe your finger (but NOT to provide your own password), and your fingerprint can be used even if you're dead.
[Nexus 6P Q&A, Help & Troubleshooting] Solutions Etcetera:
Assuming they have your finger, that's all true. But turning the phone off will still require your pin/pattern/password to decrypt it.

IIRC, Android does not automatically wipe your phone, but enough attempts will put it into a state where no more attempts can be made. At that point, additional account credentials are required, or an FDR is necessary.

I also know first hand, that resetting a phone from recovery will not allow a phone to be used without account credentials.
[Nexus 6P Q&A, Help & Troubleshooting] l_stevens:
Great information. Big thanks given!

Since Android is "Open Source", would it be feasible for someone to remove the delay to enable a brute force attack? In any case, Google could do it if ordered.

So, assuming a brute force attack occurs (delay removed), how easy to break the encryption set by a pattern (and is there anything else Google to do in addition to removing the delay to help decrypt)?
[Nexus 6P Q&A, Help & Troubleshooting] Solutions Etcetera:
On an unrooted phone with a locked bootloader, the only way to modify the system would be to unlock and root, which would wipe the phone.
[Nexus 6P Q&A, Help & Troubleshooting] l_stevens:
Does Marshmallow use 256-bit AES encryption?

That about pattern lock? Is it the equivalent of a 4 digit passcode (or 6 or 8...)?
[Nexus 6P Q&A, Help & Troubleshooting] SlimSnoopOS:
https://source.android.com/security/encryption/

128 bit.
[Nexus 6P Q&A, Help & Troubleshooting] SpookyTunes:
Google could create an special signed OTA update zip file and side load it to the device in Recovery without having to oem unlock the bootloader. This special OTA would allow for brute force unlocks.
[Nexus 6P Q&A, Help & Troubleshooting] Solutions Etcetera:
I suppose. But given Google's stance on the issue, I doubt that is any more likely to happen than with Apple.
[Nexus 6P Q&A, Help & Troubleshooting] [hfm]:
You have to unlock the phone to authorize the computer you're using to be able to connect to adb, correct? I could have sworn this needed to be done before you could adb sideload. Perhaps I'm incorrect.

At any rate, this is a fantastic reason why you should never leave your bootloader unlocked, unless you don't care if someone can have an easier time stealing your data.

Sent from a 128th Legion Stormtrooper 6P
[Xperia Z2 General] kingsasha:
After asking some people to try this method on their phones, it turned out that you can root your xperia z2 using the latest kingroot apk (v4.8)

Tested on xperia z2 and z3 compact

The steps are really simple

Download kingroot from here http://www.kingroot.net/wap

Install the apk and open it

Try to root

If successful then congratulations

***if it fails at a certain point,,, try to use a vpn then try again***

To have better root access, install SuperSU using this method (source: w0lfdroid)

Download and install Terminal emulator app here

Download and unzip "Replace_Kingroot_With_SuperSU.zip" file here

Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files

Open Terminal emulator and type :

su

Allow root permission

Type: sh /sdcard/mrw/root.sh

It might display some error, at the end it will launch supersu or open supersu manually.

Update su binary normal, then reboot.

I would really appreciate it if more people try this method and share the result in the comments

Thanks :)
[Xperia Z2 General] 5ageman:
Looks good, but better to go with installing super su trough recovery after king root. I got a bootloop while I was trying to install super su after Kingroot. And anyway, you'll need recovery for flashing, why root without TWRP. Kingroot roots. 264 in v4.6 w/o any issues.
[Xperia Z2 General] kingsasha:
Ok thanks for your feedback :)

I never got a bootloop replacing kingroot...strange
[Xperia Z2 General] Farooq95:
Yes it works I was able to install existenz without connecting my phone to PC.
[Xperia Z2 General] BladeRunner:
simplest method to get root with supersu:

1. download kingroot apk, put on internal storage

2. download (or create your own) prerooted zip, (or a ROM with supersu) put on internal sd card

3. download dual recovery to PC and unzip

4. make sure you have developer options and usb debugging enabled

5. make sure you have unknown sources enabled under settings/security

6. install kingroot apk and run it. It will say not exploit found or somesuch but you can continue from there and it will eventuall succeed

7. once you have root with kingroot connect the phone to your pc, make sure you authorize the usb debugging and run the batch file in the unzipped dual recovery

8. choose "phone rooted with supersu" and grant root access with kingroot when it pops up

9. let the dual recovery install and eventually it will reboot to twrp

10. not sure if it is necessary but I did a full wipe; data,cache, dalvik and system

11. install the the prerooted zip with twrp

12 reboot to a rooted phone with supersu
[G3 Q&A, Help & Troubleshooting] Umlau1967:
Hi,

I had a D855 with Android 5.0, rooted and with TWRP v2.8.6.0 installed, then I used TWRP to install a ZIP with Marshmallow (30B), but after installation TWRP asked for installing SuperSU and I did it. Now I know this should not be done because Supersu is not compatible with this version.

After rebooting I get into Security Error.

I did the same thing many times and always the same error. I tried to flash a KDZ but LG Flash Tool 2014 does not connect throuh USB, although under TWRP I can connect my pc to the phone and move thing in and out of it.

Any idea ?

Thanks
[G3 Q&A, Help & Troubleshooting] rk2612:
Security is error is more likely because the boot image may not bumped. Refer post http://xdaforums.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012. And SuperSu version 2.52 is said to work with Marshmallow on LG G3.
[ONE Q&A, Help & Troubleshooting] sylvainsjc:
Hi,

Last month I've successfully switched my Oneplus One 16Gb to official Oxygen OS 2.1.4

Finaly I prefer the Cyanogen version and here I have a problem with the recovery tool.

I can't replace OxygenOS recovery at all and with it : not possible to install "super su" or cyanogen 12.1 rom.

With adb the installation of TWRP recovery or or cm12.1 recovery seems to work fine (transfer ok and no errors) but when I restart in recovery mode ((power + volume down) It's still OxygenOS Recovery in my phone.

Please help, I don't want to be stuck in this state :crying:
[ONE Q&A, Help & Troubleshooting] Aavion:
download the latest COS12.1.1 factory image to your pc, boot into fastboot mode and install the factory image via fastboot (flash aboot FIRST and do a "fastboot reboot bootloader" before you flash the rest ;) ).

After that (or during, just replace recovery.img) you may install any custom recovery ;)

Gesendet von meinem A0001 mit Tapatalk
[ONE Q&A, Help & Troubleshooting] sylvainsjc:
Yes :good:

You brought me on the right track

I have successfully applied this method.

I nearly lost my phone because I had a power outage during the recovery but finally all is fine : I am back on COS 12.1.1 :victory:

A big thank-you :)
[ONE Q&A, Help & Troubleshooting] franco@21:
Revert from OxygenOS to Lineage - problem with recovery

Hi,

My phone OPO is currently running Oxygen Os

I am trying to switch to Lineage OS, however whenever the phone boots to the "Fast Boot" screen its just stuck at that.

Could someone please help me fix this?
[ONE Q&A, Help & Troubleshooting] Azhar_Fahry:
Flash twrp with fastboot , then flash the lineage os :good:
[ONE Q&A, Help & Troubleshooting] franco@21:
Yes I am trying to flash TWRP

However, when I follow the below mentioned steps this is what i end up with :

List of devices attached

dc1c2a16 unauthorized

C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>adb devices

List of devices attached

dc1c2a16 device

C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>adb reboot bootloader

C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot devices

C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot oem unlock

< waiting for device >

And on the device screen it just reads "Fastboot mode"
[ONE Q&A, Help & Troubleshooting] arashsh2002:
So I kind of have the same problem but not exactly, I flashed the oxygen os and it worked perfectly but I wanted to change it to a nugget based rom and realized that I can not even boot into recovery. it gets stuck on the first oneplus logo that comes up and will not boot into the twrp. Any suggestions?
[ONE Q&A, Help & Troubleshooting] Azhar_Fahry:
wait, so ur phone can't boot into the rom? or stuck at the fastboot mode everytime u try to turn on the phone ? I'm having that problem too, but I reinstall all the driver, and it worked.
[ONE Q&A, Help & Troubleshooting] franco@21:
My device is just stuck at the Fast boot screen that shows a One Plus Logo under which "Fastboot Mode" is written after I try to boot into fast boot.
[ONE Q&A, Help & Troubleshooting] Azhar_Fahry:
try to reinstall all the driver from this link ( https://goo.gl/MxKLjH ) and follow the instruction , i use that method and it worked
[ONE Q&A, Help & Troubleshooting] giaur:
Go to fastboot and flash latest twrp first. If you are rooted, you can do that also from running systen (flashify, twrp manager)
[ONE Q&A, Help & Troubleshooting] arashsh2002:
Thank you for your response. I tried doing that but it gives me an error saying that there is already a twrp installed. I used Twrp Manager
[ONE Q&A, Help & Troubleshooting] arashsh2002:
so I am still having the same issue, I got the latest twrp on there and still stuck, cant boot into recovery. everything I find online is about oneplus 2 and nothing about oneplus 1, can I use the same instructions for my oneplus1?