yashsingh1/xdaforums huggingface dataset:
[ONE Q&A, Help & Troubleshooting] squigley:
Ok, so I found a Beta version of SuperSU 2.7.1, and it seems to have worked. It was a different install process, saying it detected a "systemless root" or something, and it needed to patch the boot image. After that I appear to have root access again..

https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip

Edit: Whoops, guess I should have refreshed the page before posting.. What you said is correct Ken.
[ONE Q&A, Help & Troubleshooting] srink.007:
Thank you :)

thanks a lot :)
[ONE Q&A, Help & Troubleshooting] srink.007:
DONE :)

http://imgur.com/hh3qkdxGuys Finally I have done it. Yes the phone is rooted now :)

1. Flash Stock COS 12

2.Update Stock COS 13 using stock recovery

3. Installed SUPERSU (chainfire) from Play Store

3. Install TWRP

4. Create NANDROID BACKUP (optional , I have created since I doubted the rooting process on cos 13)

5. Installed Latest STABLE SUPERSU ( V 2.65 as of now) {my last attempt with beta 2.71 failed }

6. Done :)

http://imgur.com/hh3qkdx
[Galaxy Tab S Themes and Apps] whatsisnametake2:
is there a dark keyboard for the sm-t805 anywhere? i'm quite happy with the stock one function wise but would be better darker themed. can it be modded?
[Galaxy Tab S Themes and Apps] Lightn1ng:
It has been done before (I used one on my S5) but upon searching I cannot find one for the device, nor do I have the skill to make one.
[One (M9) Q&A, Help & Troubleshooting] Thaoldwise:
Hi all, I need help with a big big problem.. Long story short, I bricked the phone. I think it's gone forever but I'm trying to ask here if someone got ideas.

First I want to say I got another M9 rooted, custom rom installed etc and got no problems, but I did it long time ago, with older methods, while now I tried using Windroid Toolkit (http://xdaforums.com/showthread.php?t=2499926).

Here's the story:

- Unlocked phone via HTCdev ==> OK and everything worked;

- Downloaded and installed Windroid Toolkit, and with this installed TWRP 3.0.0 ==> OK and everything worked;

- Always via Windroid toolkit installed SuperSU ==> Windroid Toolkit sends you in recovery TWRP and you select the right supersu.zip file. Installation completed ok, but when I rebooted phone, it went in loop: showed start white screen with HTC logo and red text ("This build is for development bla bla bla") for X seconds, then reboot, and so on forever.

At that point I was still safe because I could still enter bootloader/ recovery etc, BUT... Don't ask how, don't ask why :crying: :crying: :crying: , shame on me I entered recovery / ADVANCED/ WIPE and wiped: dalvik cache, cache, system, data, internal storage... ( yes I know.. total stupidity :silly: ).

So now I am stuck at white screen with HTC logo and red text. I cannot reboot, I cannot even switch off phone keeping POWER button pressed! ("yeah you moron, you deleted os!" I know I know..).

If I connect phone to PC i hear the USB Windows sound but giving "adb devices" says "List of devices attached" like nothing is connected.

Also tried with RUU.exe but nothing (first version I found for M9, it is just to tell you it cannot see the device "Ensure your device is connected to USB").

Now I am waiting for the phone to run out of battery so I can try to VOL DOWN + POWER btn but I have no hope...

So in the end, do you have some idea?

I am very angry because I always rooted and installed custom roms, starting from HTC Diamond, always bought only HTCs and never had a problem, now I did this bulls**t with the phone I bought as gift for my father..

Thanks everyone any help will be appreciated.
[One (M9) Q&A, Help & Troubleshooting] Arthas92:
try VOL UP + POWER

i start with HTC Diamond too, used one X, M7 and now M9, it really hard to brick compare to previous phone
[One (M9) Q&A, Help & Troubleshooting] side_flip15:
Press VOL DOWN + POWER until you reboot to bootloader. From there reboot to recovery and flash custom rom.

fyi I always wipe dalvik cache, cache, system, data when installing custom rom coming from other roms and I don't have any issues whatsoever.
[One (M9) Q&A, Help & Troubleshooting] shivadow:
Most likely just change supersu for version 2.65. M9 is finicky about supersu.

Beamed in by telepathy.
[One (M9) Q&A, Help & Troubleshooting] micha279:
If you were not S-OFF and wiped "real" firmware partitions like hboot, radio and so on your device is not bricked at all as the others already stated ;)

1. Try VOL UP + POWER or VOL DOWN + Power until you reboot to Bootloader

2. Enter Download / Fastboot mode and flash new recovery using fastboot flash recovery yourRecoveryFile.zip

3. Reboot into recovery

4. adb push yourCustomRomFile.zip /sdcard

5. Flash Custom Rom

6. Full Reboot

7. Enter Recovery

8. Flash supersu 2.65 or 2.71 Beta

9. Full reboot

10 Be happy :)
[One (M9) Q&A, Help & Troubleshooting] Thaoldwise:
Ok guys really thank you, so do you say its is not bricked. I will try as soon as I have time and/or battery dies (already tried with VOL DOWN + POWER but not with VOL UP + POWER ).

With my other M9to flash custom rom I had to get S-OFF with Sunshine app.

If I can enter recovery, can I flash a custom rom even if i am S-ON? Now I am in unlocked state and S-ON.

Eventually can I try restore my other M9 backup, done with TWRP 2.8.7.1, to this M9 having TWRP 3.0.0-0? I will check but I think they got same firmware (3.35.401.12).

Thanks again everyone
[One (M9) Q&A, Help & Troubleshooting] 5m4r7ph0n36uru:
You don't need to be S-OFF to flash a custom ROM. You only got to check if the ROM base matches the firmware that is currently installed on your device ;)

S-OFF unleashes just a little bit more freedom to play with your device, but at the same moment the risk of making a mistake and really bricking the device is highly increased.
[One (M9) Q&A, Help & Troubleshooting] iElvis:
This is a good example of why I hate toolkits and advise people never to use them, unless you already know how to do all this stuff manually. It's too easy to get into trouble you don't know how to get out of.

Try pressing all three buttons until you reboot if the other options don't work.
[One (M9) Q&A, Help & Troubleshooting] Thaoldwise:
Yes you are right, before to start play with roms and stuff I usually lost days and days reading everything possible for every passage, while this time I was like "Oh cool a toolkit! Easy way let's do it!". Anyway I don't want to give responsibility to Windroid toolkit, only my fault I did things without thinking too much.

Respect for eveyone working hard to give us knowledge and this beautiful forum!

I will keep you informed thanks again everyone
[One (M9) Q&A, Help & Troubleshooting] Thaoldwise:
Ok guys here I am.

Everything ok now thanks everyone again.

With phone switched off due to dead battery I was able to start with VOL DOWN + PWR and I could reach bootloader, download mode and recovery. Installed custom ROM, flashed SuperSU 2.65 and now I am on the road again :good::good::good:.

Only problem left is since I installed ROM (ViperOneM9 4.3.0) I cannot use adb: adb devices return "unauthorized".

I read various posts and the problem seems to be the phone not showing prompt to accept RSA key.

If I connect my other M9 everything is ok.

I think to have tried most of everything people suggest in different posts:

- updated android sdk

- reinstalled android sdk

- deleted adbkey and adbkey.pub in my %user%/.android folder (it recreates files but still no prompt on phone)

- reinstalled drivers on PC

- reinstalled rom with wipe during aroma installer

- looking in the phone in "system/data/misc/adb" for keys files but my folder is empty (checked on my other fully working M9 and that folder is empty too)

- tried install Minimal ADB and Fastboot [4-27-16] http://xdaforums.com/showthread.php?t=2317790

- toggled USB debugging on/off rebooting phone and PC

If you have more advice I am glad to hear.

Thanks again to everyone to get my phone back working!
[One (M9) Q&A, Help & Troubleshooting] shivadow:
Is your other m9 running the same rom? The problem wont be the pc. If you can see one you can see all. Adb is versatile like that..

Try adb at twrp or one of the other booting modes. I'm quite sure adb is twrp only..

Beamed in by telepathy.
[One (M9) Q&A, Help & Troubleshooting] Thaoldwise:
Hi, on other M9 i have same rom but 4.2.1 version (4.3.0 on not working one).

If I go on recovery or bootloader or download mode adb return "list of device attached" like it dosnt feel nothing connected. On the other M9 all is ok.

I just tried install a VM with Windows 7 but I am not able to let it see the USB device
[One (M9) Q&A, Help & Troubleshooting] Stephen:
Thread closed at OP's request. He has been able to resolve the issue.
[Shield Q&A] Szpara69:
Can yu do it?
[General Questions and Answers] crazyforjellybean:
hi fellow Droid users! I'm far from being Neo in the Matrix, but i'm way beyond "how do I C&P?"... that said, I purchased a refurbished LG G2 with the intention of rooting and then installing(downgrading to) JellyBean. It's currently running 5.0.1 any help/links to the right rooting software and then a link to (re)install JellyBean specifically would be incredibly awesome! Thanks in advance for taking a moment to read my message and offering any help! p.s... I just want a "stock JellyBean" experience, fancy skins, etc are not desired at all. THANKS!!!!! : )
[Galaxy Tab S2 Q&A, Help & Troubleshooting] gonzo99:
Hi,

I have a T710 that's about 6 months old and had fairly light use.

Yesterday after charging up to 100% while off, it turned on only for the touch screen to fail to respond. The capacitive keys and fingerprint sensor and physical buttons all work perfectly, the tablet boots normally, and even responds to OK Google - but no touch is registered on the screen at all.

There is no screen protector on it and it has not been dropped or damaged. I noticed a day or two ago when playing a game that the screen was a little slow to respond, but put this down to maybe greasy fingers or a laggy game.

It is currently running a stock 5.01 Rom, although there was an update or week or two back - but I've had it working since then.

This happened once before about 3 months ago and I was in the process of returning it when I flashed a stock ROM through ODIN, which solved the problem and it worked fine until yesterday - this seems to suggest that it's not a hardware issue.

Before I go down the Odin process again and hence wipe it, are there any other things I can try that might work?

I've never rooted and the Knox counter is not tripped, so I could send it back under warranty, but that will mean sending it away and as I imported it from Hong Kong I don't know if Samsung will raise an issue (I'm UK based).

Previous googling when I had the issue before found a post or two suggesting that it was something to do with charging after letting it run down that led to others seeing the same issue - but can't find anything in this forum.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] ashyx:
You don't need to wipe anything to flash with odin.

Just flash the latest stock firmware as is.

The easiest way to discover if it is hardware or software is to simply install TWRP.

However that will trip knox and potentially void the warranty.

The other test is to boot in safe mode.

Hold VOL DOWN while booting to the OS.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] gonzo99:
I didn't realise that Odin flashing didn't wipe! Useful to know thanks.

I connected a mouse with a OTG lead last night so was able to back up what I wanted with Smartswitch - I then tried the device reset through smartswitch, which does wipe.

Unfortunately, that didn't resurrect the screen, so I've tried a couple of different ROMs through Odin since, with similar lack of success :(

Unfortunately, I don't want to find out that it needs warranty repair after installing TWRP and possibly getting that repair rejected because of a knox trip. Has anyone had experience of returning a knox tripped device with a screen fault and their response to it?

I'm going to let the battery run down fully and recharge to see if anything changes - as that is what seemed to work last time (don't ask me why though!)
[YU Yureka Q&A, Help & Troubleshooting] AJIT KATARI:
Please help how to downgrade from cm 13 to cm 12.1
[YU Yureka Q&A, Help & Troubleshooting] Helll7:
Check jay kapoor videos :p
[YU Yureka Q&A, Help & Troubleshooting] SunnyGrewal11:
hi .. what r the probs with cm13 ??

and is it the update that came i think a week earlier ??

i think its 225mb ??
[Samsung Galaxy Mega] biged1969:
Kingroot did something to my phone and now it doesnt work. All i get is a yellow triangle with an exclemation mark and the message System software not authorized by Verizon wireless has been found on your phone. please turn off your phone and go the nearest verizon wireless store for help. How am i getting this on an att phone? My computer doesn't recognize it when i plug it in. Is there anything i can do to get it working without losing everything? is there a way t get my contacts and texts off the phone? Those are the 2 main things i need, getting the phone working is secondary.
[Fire Q&A, Help & Troubleshooting] xerogabe106:
I installed Link2SD. It did everything I wanted it to do. No issues there. Except maybe 1.

Whenever I open Snapchat it instantly minimizes. It doesn't seem to crash, just minimize. Whenever I try to maximize it, it just minimizes again and again. It wants to be minimized all the time and I can't get it to stay up.

Ive tried to reinstall it, delete cache/data, install older versions, force stop, move to internal and external. Nothing seems to help.

I'm not even 100% sure that Link2SD is to blame tbh. Its just the only thing I can think of. Truth be told, I like Link2SD more than Snapchat. So I'm not willing to get rid of it if it is at fault. Its just annoying that I can't get the damn thing to work.

Ive tried getting help in several other places but haven't gotten a single response. I'm hoping someone here can help or point me in the rite direction!
[AT&T LG G3] nicolepark:
Hai :) I flashed Turbo ROM and for some reason I don't have root... I have SuperSU but it says there's no su binary installed... Also I can't get into TWRP, because it hangs on the TWRP logo screen and doesn't get passed that. How can I root my device so I can fix my recovery, or the other way around? Thanks :)
[AT&T LG G3] saudahmedbass:
go to play store and download supersu app. restart the phone. this will get you root. then install twrp app from google and reinstall it through app. i think this will help you get into recoery.
[AT&T LG G3] nicolepark:
I already tried that :c. I ended up using the TOT method to restore 10D and worked my way through rooting it and putting a recovery on it. c: Now that the D850 has an official 6.0 update, I expect we'll see Marshmellow roots for our device c:
[AT&T LG G3] saudahmedbass:
Yes we both be waiting for marshmallows :D
[AT&T LG G3] shawkes:
Just installing the supersu app does not give you root.
[AT&T LG G3] chimera1978:
Anybody have any luck with this yet?
[AT&T LG G3] Motok0:
KingRoot gives you temporary root on stock D850 Marshmallow.

When you reboot/restart, you lose root and it takes about 3 minutes or so, using the KingRoot android app, to regain root.

The apps requiring root that I've tried have all worked without issue.

Whether you want KingRoot installed on your phone is another issue.

I haven't come across a better solution for getting root on stock D850 Marshmallow yet.
[AT&T LG G3] bigfau:
Which KingRoot Motok0?
[AT&T LG G3] Motok0:
I just used the latest android app from: https://kingroot.net

http://king.myapp.com/myapp/kdown/i..._B263_office_release_2016_05_09_105203(1).apk

From the about section of the KingRoot app on my LGG3:

"KingRoot V4.9.2 143

Kernel Version v4.8.0 67 / Su version v3.61"
[AT&T LG G3] shawkes:
If KingRoot does work you could look at this https://play.google.com/store/apps/details?id=darkslide.com.supersumepro app to remove KingRoot and install SuperSU. I have not used the app I just saw someone on Reddit report that it worked for them.
[AT&T LG G3] bigfau:
It works.
[AT&T LG G3] JkdJedi:
I'm trying this out right now, I'll report back in a few..

eDIT1: well, it's stuck on Processing, please wait... (should I leave it for an hour to see what happens?)

Edit2: My dumbass forgot to root w/ KingRoot first...sigh, will report back in a few..

Edit3: I don't get this..it removed kingRoot app and now I no longer have root..wtf? If I wanted King Root app uninstalled I could've just uninstalled it myself..

Edit4; Ok ..maybe I'm traveling through Dorkville right now... trying this all over agin with SuperSu in da mix..

Edit5: well, I have a brick now.. ;(
[AT&T LG G3] bigfau:
I did that a week ago and I had to restore with tot file. I still haven't received the MM update since
[AT&T LG G3] phoneguy412:
hey so if i understand this right i can use KingRoot to temp root my phone, this will allow me to remove/uninstall Bloatware and keep it off my phone even when the phone not rooted, correct?

G3 D850 AT&T with MM 6.0 update
[AT&T LG G3] JkdJedi:
How did you get the Lollipop tot file to take on a MM Device? :confused:
[AT&T LG G3] bigfau:
I used the LGUP and tot.

This is correct. Be careful though. Many users want to uninstall Kingroot and switch out kingusr with superuser app. Doing this may result in soft brick.
[AT&T LG G3] JkdJedi:
I did get a soft brick switching out KingRoot with SuoerSu and thankfully was able to get back to stock 4.2.2 using LgUp
[AT&T LG G3] gello924:
Didn't Work for me

Tried both the Windows and Android App version.... :(Failed! Also tried KingOroot and iRoot... :(Failed

Any other suggestions would be greatly appreciated, I would love to get all this built in crap removed

Build version: MRA58K

Software version: D85030p
[AT&T LG G3] hyelton:
This is a old thread. Anyway you cannot root MM. You have to downgrade to root.
[AT&T LG G3] Bazookaguy5:
Actually u can use kingroot to root ur marshmallow phone. although root access is gone if u uninstall the kingroot app. Basically u get root access through kingroot. all other apps gain access through it.
[Samsung Gear S2] screenpaver:
Has anyone ever seen an issue like seen in the picture (horizontal dark bands across the Gear S2 screen). I've only had the watch two weeks and this happened. I've tried soft and hard resets to no avail.
[Samsung Gear S2] donnyv128:
I have the same issue and can't find an answer to it anywhere. My S2 is only a week old
[Samsung Gear S2] Mikoube:
Hey guys,

I had the same after a watchface always ON fail... I've planned to send it back to after-sale... But 2 days after, all the line just disapaers...
[Samsung Gear S2] screenpaver:
Since it is still under warranty I filled out an online request for service. They emailed me a shipping label and I sent it off to Plano, TX on Saturday. The status today says "Replaced LCD" and now it's back in the mail to me. We'll see...
[Samsung Gear S2] cyphi:
Hey Mikoube, how long were you seeing the problem? I just started seeing this today. Has the problem recurred?

Thanks!!
[Samsung Gear S2] saur_pr:
Facing same problem in Gear S2 classic

I am facing same problem in my new Gear S2 Classic. I have purchased this one week back.
[Samsung Gear S2] Mikoube:
Hi cyphi,

as I remember it took around 3 days to disappear, mays 4 but not much than that.
[Samsung Gear S2] cyphi:
OK thanks!! My display still doesn't seem to be getting any better. I think I may be returning the watch :(
[Samsung Gear S2] Mikoube:
not cool... maybe try with a white watchface or something very close to. Do you remember what watchface you had when it append?
[Samsung Gear S2] cyphi:
No. I actually fixed it today. There was a recent firmware update on the watch and one of the custom watchfaces that I had previously installed must've been causing the problem. I did multiple factory resets, but I keep trying to keep the watchfaces that I had already downloaded...that wasn't resolving the issue. I did a complete factory reset today and wiped out all the custom watchfaces and the problem disappeared. I'm happy now!! Thanks Mikoube for your help!! :D
[Samsung Gear S2] Mikoube:
You're welcome ;)
[Samsung Gear S2] shinta4e:
Hello! I'm having the exact same issue. Can you explain what you did to fix it? Did you erase all the downloaded faces and then do a hard factory reset? Or vise versa? I'm at work right now and would love to achieve your same results since it happened 2 hours after my Warranty expired ??.
[Samsung Gear S2] rprussell:
Here's how I fixed mine: Sent it back for repair. Waited a week. Received a fixed watch.
[Samsung Gear S2] Mikoube:
Hey shinta,

The fact is that one off your watchface is causing trouble to tizen. So Try to make a full factory reset. It should solve your issue.

:)
[Samsung Gear S2] Wireratt:
So i got these same lines on my device lastnight. It is mainly noticable when I turn on Aod. I dont want to bother with rma on a 2 month old device if this is going to fix itself. I tryed a few resets and its still there now. I dont mind waiting a few days though.

edit:

My gear s2 screen is working fine now. It only had the lines for 3 days. I will keep a close eye on it though and update if it returns.
[Samsung Gear S2] Blackmoco:
Same issue, I did factory reset and deleted all downloaded Wacho faces . Still the problem!
[Samsung Gear S2] Mikoube:
The bands were back a few weeks ago... I figured that when I set the brightness to "1", the band are little and when I put on "10", they are bigger.

So I tried to let the watch during 1 day with a brightness of "1". The day after all band were gone...

Hope this can help some of you guys.

Enjoy.
[Samsung Gear S2] kadabra12:
Same problem with the screen of mi gear fit 2 band, resolved only changing the screen

Inviato dal mio SM-G920F utilizzando Tapatalk
[Samsung Gear S2] Jockard:
Same problem here, I turned it on, and it was fine, then I UPDATED a few apps and faces and lost network, after that the problem started, so I belive its a software issue and not hardware, could be coincidence, its a month old watch...
[Samsung Gear S2] mdior520:
My watch is 5 months old and I just have this problem last night :(
[Samsung Gear S2] Jockard:
Working now

Just came back to say that its all gone after a few days and some factory resets, took like 2 weeks, and now its all gone, screen is fine, even in always on display. I still believe its a software issue... thanks guys
[Samsung Gear S2] jerronimo3000:
Just wanted to chime in here that mine fixed itself as well. I bought a refurbished gear s2 classic 3G that ended up having the same horizontal bands as the OP out of the box. I tried factory resets and deleting every watch face to no avail. Then, after 3 or 4 days when I went to show somebody the problem...it wasn't there anymore! It's been a couple weeks since then, and I've had zero problems with it. I have no clue what fixed it, but from what everybody's said, and the equal width and distribution of the bands, it definitely sounds like a software problem somewhere. If yours is broken, hopefully it'll work itself out too!
[Samsung Gear S2] koreezzz:
Got the same problem with Korean S2 classic 3G today.

Is rherw any another solution except waiting? Does someone else confirm that bands were dissapeared by themselves after some period of time?
[Samsung Gear S2] Khaniku:
Having same problem with my gear S2, been 3 days now. Any possible solutions?
[Samsung Gear S2] CravingMender9:
I had the same problem last week. I kept it in the wireless charger for three and half days as a desk clock and the problem has disappeared. Fixed itself. Didnt even have to do reset.
[Samsung Gear S2] Khaniku:
Just came back to say mine disappeared after about 2 weeks by itself.