yashsingh1/xdaforums huggingface dataset:
[LG G5 Accessories] Edward08:
I might be quite late to the party, but is there a way to support a longer shutter speed with this root.
[LG G5 Accessories] andrewharvey:
wow thanks, any pointers on the "Now install whichever exploit fits your fancy." step?

scrcpy gives me a blank screen with "CCS" at the top and adb shell seems like I don't have root.

I can't get the official LG360 app to connect to my camera on my phone, so I was trying to find a way to program the shutter button to start capturing at 2sec intervals (used for Mapillary) so I don't need the app at all.
[LG G5 Accessories] doebeli:
CCS is the app controlling the camera (eg. "camera control system"). You can press ESC twice and after that you will get the "normal" GUI of your camera:

View attachment 5374899
[Nexus 6 Q&A, Help & Troubleshooting] MadFoss1:
I was running LineageOS 14.1 up until 15.1 came out. I re-flashed my Nexus 6 with the first build of 15.1 along with OpenGApps. About a week later I decided to flash AddonSU. Here's where it gets goofy. For some unknown reason my brain decided to download and flash SuperSU. Once flashing completed, I went into developer options to enable Root, and to my surprise, root options weren't available. I flashed SuperSU again and still no root options. I then realized that I flashed the wrong SU zip. So, I downloaded and flashed AddonSU. Back into developer options and Root options were available. A few days later, the Nightly 4/30 OTA update became available. The update failed during install. I then flashed the nightly build along with the MindTheGapps zip this time. A week or so later, the Nightly 5/8 OTA update was available. That update also failed during install. I read in multiple forums here that the OTA updates fail due to a conflicting SuperSU binary, and that the only way to remove SuperSU was to reflash stock factory Android, in this case 7.1.1. So, I downloaded and flashed stock Android rom for Build N6F27M. Relocked the bootloader. Unlocked the bootloader. Re-flashed TWRP 3.2.1-0. I booted into recovery and went to File Manager and noticed that the SuperSU folder is still there. I deleted the folder and went through the entire flashing of Stock Android again, one .img file at a time. Locked and unlocked the bootloader again. Flashed TWRP again. Go to File Manager and guess what was there... The SuperSU folder was back!

Before I flash anything else, how can I totally remove SuperSU from my device once and for all?

Current setup:

- Using ADB and Fastboot on Lenovo X230 running Fedora 27 Linux

- Nexus 6 (Build N6F27M), Stock Android 7.1.1

- TWRP 3.2.1-0 Stock recovery just replaced TWRP!
[Nexus 6 Q&A, Help & Troubleshooting] alryder:
This seems like overkill but if you go to Advanced Wipe in TWRP and wipe everything, then flash each .img file again from Fastboot there should be no way SuperSU could survive that.
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
The answer is to dirty flash the ROM in recovery. You need to overwrite the system and boot partitions with the lineage release. This does not mean using a lineage OTA.

But I'm at a loss why why you indicated indicated the N6 is;

Did you revert to stock?

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6 Q&A, Help & Troubleshooting] MadFoss1:
Yes, I reverted to stock Android. I read somewhere here that it was the only way to remove SuperSU. And, yes, I did dirty flash. I wiped each partition one by one before flashing. After each wipe, I rebooted to recovery until all were wiped. I also deleted the SuperSU folder. And every time I rebooted into recovery, I'd go to File Manager and the SuperSu folder would re-write itself.
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
You're mixing and matching things here.

The supersu folder will show up in TWRP even if you've never rooted the device.

A modern, systemlessly rooted device modifies the boot image, not the system partition. By dirty flashing the ROM, you replace the modified boot.img with the "stock" ROM version. Stock is in quotes because it's stock to the custom ROM, not meaning a stock ROM.

Wiping each partition is not a dirty flash. If you were going to dirty flash to remove root, all you needed to do is remove the relevant supersu script in system/addon.d, reboot to recovery, flash the ROM normally, wipe data and cache then reboot.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
I forgot you were originally taking about lineage. Using lineage's su.zip, you will (I think) be rooted in system mode, so dirty flashing will result the original system.img reverting the changes.

As stated above, in systemless it's the boot.img that needs to be reverted.

As an additional caveat, if a third party kernel has been flashed, AND you have systemless root; first you dirty flash the original ROM, then re-flash the kernel to unroot.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6 Q&A, Help & Troubleshooting] MadFoss1:
The last "good" flash I completed was with Lineage nightly 4/30. Once I realized that there were still issues, I completely wiped all 5 partitions one at a time (Dalvik/Art, System, Data, Internal Storage, Cache) from TWRP. After rebooting to bootloader, I then fastboot flashed factory 7.1.1 images one at a time (bootloader, radio, boot, cache, recovery, system, and userdata). I then rebooted to stock recovery and selected Factory reset, then rebooted system. 7.1.1 loaded without a hitch.

I just finished flashing TWRP recovery back, wiping all 5 partitions again, and adb pushed only Lineage Nightly 5/15, and MindTheGapps zip's to sdcard and flashed them.

Besides the problematic SuperSU zip (previously installed), those were the only zips and images that were flashed to the device.

I would think after all that, SuperSU would be gone! Your saying I might also have to re-flash the kernel? Wouldn't the latest Lineage zip resolve that?
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
Please quote the part where you think I told you to do anything more than dirty flash the ROM. I'm trying to figure out why you think I said flashing the lineage ROM is insufficient.

What you have done is serious overkill, but does get the job done (removing root).

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6 Q&A, Help & Troubleshooting] MadFoss1:
First, let me preface that I am new to flashing ROM's. Second, I was unclear of the differences between dirty and clean flashing.

Third, I didn't realize that the "supersu" folder at the root of the device, is persistent. Had I known this in the first place, none of this conversation would really be necessary as I believed that SuperSU wasn't going away.

Fourth, nowhere do I even remotely insinuate that flashing a Lineage ROM is insufficient.

Fifth, here is your quote from post #6 where you mention the possibility of flashing more than the ROM, "...first you dirty flash the original ROM, then re-flash the kernel to unroot."

Finally, any forum I've been a part of, details have always been a prerequisite to receiving feedback. All I've done here is provide those details so that anyone, (not just you) could be best informed of my situation.

I do agree now that what I've done with my device is serious overkill. Everything I've done thus far has been done from the advice of other Devs or experts here on XDA, Reddit, or other forum posts somewhere on the internet. However, I, in no way, intentionally or unintentionally tried to undermine your expertise (as I sensed you have in your last post). I am merely a noob in the world of custom ROMS, and all I seek is advice. And for the advice that you provided I am grateful, and I sincerely thank you. If I offended you or made you feel your advice and expertise was inadequate, I do apologise!

Again, I thank you, as well as all of the Developers and experts here on XDA for your knowledge and advice. I look forward to possibly talking to you again in the future.
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
As, in the future, you read solutions to problems you post, please keep in mind that it's not uncommon for people to post complete explanations that may not totally apply to the situation at hand. There are a couple of reasons for that.

One is that it can help develop understanding of the larger picture the specific problem fits into.

Another, and often why I almost always expand answers, it so future readers of a thread get a more complete view of the process under discussion.

In the case where I expanded on the idea that if an additional custom kernel is used on top of a custom ROM, then that has to be taken into account when removing root. I did make an assumption that if you didn't use a 3rd party kernel, then you would understand that didn't apply to you.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6 Q&A, Help & Troubleshooting] MadFoss1:
BTW, thanks for your input. This Definitely should take care of it. This would have been much easier had I known that a supersu folder existed at the root of the device. For all the times I've flashed my phone, I've never noticed it. Lesson learned. Thanks again.
[Android Stick & Console AMLogic based Computers] newWMuser:
Hello all,

I think my MIBox 3 enhanced edition has been bricked during a firmware re-install. For some reason. It just will not power on.

I have read a previous post : https://xdaforums.com/android-stick...ogic/s905x-xiaomi-mi-box-3-mdz-16-aa-t3502992

Where the author mentioned connecting 2 metal points to power on the device.

Is there any such action I can take to try and force power on the MDZ-18-AA?
[Essential Phone Questions & Answers] knotjeff:
just got the phone yesterday and updated it to the P beta. everything works amazingly well for a beta in my opinion, BUT i cant receive calls. outgoing calls, texts, web and apps are just fine.

spent almost 2 hours at tmobile flipping all the settings around and no luck. any ideas would be appreciated.
[Essential Phone Questions & Answers] InkSlinger420:
Same issue here bro...Incoming don't ring but I get voicemail notifications.... Really annoying, even if it is a DP.
[Essential Phone Questions & Answers] knotjeff:
Turns out the beta doesn't play well with the essential LTE. Switch to 3g and calls will come through. Hopefully it doesn't take long to find a work around for it
[Essential Phone Questions & Answers] BakedTator:
I believe the people having this issue have volte enabled...try and disable volte (it's broken anyway and more than likely why calls won't ring through) and see if that works
[Essential Phone Questions & Answers] vergilbt:
Got same issue... My experience was that I could solve the problem with reboot.

Issue came after playing on settings for mobile network.

Is meaning, when you do this you have to reboot afterwards otherwise you can't receive calls

Try it.
[Essential Phone Questions & Answers] knotjeff:
Tried rebooting multiple times while changing settings around. The only way I can get the calls to come through is by going without LTE completely.
[Essential Phone Questions & Answers] Forgetfull:
Settings/network settings/mobile network/advanced/enhanced LTE?
[Essential Phone Questions & Answers] alienator88:
I had the same issue and to fix mine I just enabled Wifi Calling.

When on wifi I didn't get a call, just missed call notification. After enabling wifi calling, it comes through without issue.

I tested calling off wifi and on wifi and all calls come through good now.

This could be similar, so you guys might want to look at that also.

Good luck!
[Essential Phone Questions & Answers] mrcooter:
Heard from a few that this was solved by going into phone app settings -> calls -> calling accounts, then turning on "receive incoming calls". Seems it's disabled to save battery? Can't confirm as I just flashed to try it out and then went back to 8.1 because I like themes too much. Lol.
[Essential Phone Questions & Answers] jamebarron88:
I'm on Sprint and was never able to make or receive calls regardless of Network settings in the easily accessible options menu.

The following fixed my issue. You can access this menu without downloading an app but I forget how so it's easier to just download the free app https://play.google.com/store/apps/details?id=com.xsquarestudio.forcelte

I had my network mode set to LTE/CDMA when first using this app, and somewhere in the middle I changed it to CDMA but I'm not sure how much that impacted the actual fix.

These were my steps. I'm not responsible for any damage this may cause to your device as I'm not sure if messing with these settings is foolproof or not.

First, opened previously linked app "Force LTE" then under "Set Preferred Network Type" I changed to CDMA only. Enabled/disabled airplane mode. This seemed to do nothing as LTE was still showing in statusbar.

I then chose CDMA auto (PRL), airplane mode on/off, didn't seem to do much either. LTE still showed in statusbar and couldn't make calls. Also "Voice Network Type" showed "Emergency Calls only" inside the app.

I then chose the 3 dot menu and chose "select radio band". I changed that to United States, without resolving problem. Then selected "Cellular 800" and this may have solved the problem, but I continued on and selected PCS, fiddled with some settings in Phones settings menu. Was finally able to receive calls and my signal indicator showed 3G. In app Voice Network Type was listed as 1xRtt. I decided to select radio band once more and chose Class 10.

Calls were still functioning fine. So I went into Main settings menu and changed mobile network from CDMA to LTE/CDMA. LTE kicked in and calls still work!

Again, these settings may only work for Sprint hence the PCS Network option, and I believe Sprint may utilize the 800mhz frequency. The app might show you different options depending on your carrier. I don't know.

Anyway, fully functioning! Woohoo!!
[Essential Phone Questions & Answers] knotjeff:
I don't have anything in my settings that says "enhanced LTE" .

Tried using the 4g/LTE and the LTE only options. Neither would let calls through.
[Essential Phone Questions & Answers] integritycommand:
I have this problem using the Essential PH-1 with Android 9 Pie in South Korea on the KT network. It should be fully compatible, according to radio specifications, however it only works when I change the following setting:

Settings | Network & Internet | Mobile network | Advanced | Preferred network type | 3G

This is not ideal, since it makes the Internet slow, but at least I can make/receive voice calls. I submitted a support ticket to Essential requesting their official help (I'm well within warranty).
[Essential Phone Questions & Answers] Minnersinger:
I had the same issue when I use my Att prepaid plan. The problem is caused by wrong network type, you can send text and browse internet, because they use the different channel. My PH-1 wrongly recognized the sim as CDMA/LTE mode, just switch it to 4G/LTE, it will be work. Go to Settings, then search "wi-fi calling", point "advanced" then you can see an opinion "Preferred network type" if you are ATT or T-mobile user, and your preferred network type is "LTE/CDMA“ then your phone cannot make call. Switch it to "4G/LTE", you phone will be work. BTW, Verzion uses CDMA, so if you are Verzion user, CDMA/LTE will work for you phone.
[Samsung Galaxy S8 Questions and Answers] hambouga:
Hi,

So the new firmware update is really bad on the battery and I wanted to rollback for my SG955W. I downloaded the latest 7.0 firmware from sammobile and tried flashing with ODIN but it fails for some reason.

Can someone help me why?:(
[Samsung Galaxy S8 Questions and Answers] aromerblz:
I do not think that is possible. Bootloader on your model was updated to V3 from V2 on Nougat.
[Samsung Galaxy S8 Questions and Answers] hambouga:
Samsung is responsible for doing this. They should be sued!
[G4 Q&A, Help & Troubleshooting] robles4242:
Im using an unlocked Verizon LG G4 VS986 and I have my new AT&T sim in and everything works but MMS. At first the internet data didn't but I found an APN that brought me data. Next to my signal arrows I only have an "H" tho.... And I cannot get MMS messages to download..... Can anyone help me?

Also on how to remove the notification saying "SIM is not Verizon"..
[JAM, MDA Compact, S100 Software Upgrading] shadyghost:
Just wondering if anyone has any suggestions on the best ROM to use for those of us in the USA. I am personally using ATT/Cingular and have a ROM loaded that the GPRS doesn't work and the txt messaging is pretty shotty.
[JAM, MDA Compact, S100 Software Upgrading] shadyghost:
Or is anyone using a specific ROM in the United States that has worked well for them?
[JAM, MDA Compact, S100 Software Upgrading] BeyondtheTech:
http://wiki.xda-developers.com/index.php?pagename=HTC_Magician

The bottom of the page will have a direct link to the latest official ROM for the i-mate JAM 850MHz. It's the one added by me, and it has the USA flag next to it.
[JAM, MDA Compact, S100 Software Upgrading] shadyghost:
nice. thankyou
[Xiaomi Redmi 4X Guides, News, & Discussion] hosseinmo:
I AM NOT THE DEVELOPER OF THIS ROM NOR A MEMBER OF MOKEE TEAM

FLASH AT YOUR OWN RISK​

[IMG="MOKEE"]http://s8.picofile.com/file/8326679192/Untitled.png[/IMG]

About

MoKee Open Source is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.

A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion…

Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!

Read here for developer application: http://www.mokeedev.com/en/developer-application, you can host your unofficial MoKee builds on our server!

Forum:http://bbs.mfunz.com

Guide:http://bbs.mokeedev.com/c/documents

Statistics:http://stats.mokeedev.com

Review:https://mokeedev.review

Download:http://download.mokeedev.com

Github:https://github.com/MoKee

Bug Tracker:http://issues.mokeedev.com/

Credits:

Google, Qualcomm, Linux Kernel Organization, Motorola, Samsung, Lge, TI, Nvidia, Intel, Sony,

CyanogenMod, Omnirom, Slim Roms, Koush for open-sourced SuperUser, lineageOS, TeamWin,

Smartisan Digital Co, Substratum Development Team, The Open GApps Team.

DOWNLOADS:​

ROM:https://download.mokeedev.com/?device=santoni

GAPSS:https://opengapps.org/

TWRP:https://sourceforge.net/projects/teamghost/files/santoni_twrp/twrp_santoni_oreo.img/download (TeamGhost)
[Xiaomi Redmi 4X Guides, News, & Discussion] arvindgr:
This thread is duplicate to https://xdaforums.com/xiaomi-redmi-4x/development/official-mokee-official-redmi-4x-t3684858/page13 ! Pls remove
[Samsung Galaxy S7 Active Questions & Answers] princessslinky07:
I may have bricked the chooch out of my s7 active was wondering if someone can give me the latest version or a backup of the latest version haha (tried to install oreo) NRD90M.G891AUCS2BRC1 is the build number
[Samsung Galaxy S7 Active Questions & Answers] staffeyx:
For bootloader 2, I think the latest full ROM available is BQD4:

https://cloud.mail.ru/public/BGy7/gKs4xzhRE/firmwares/Nougat/G891AUCS2BQD4_7.0_all.7z

Warning, this only applies if you are still on bootloader 2 and haven't gone up to the latest version 3.
[Samsung Galaxy S7 Active Questions & Answers] princessslinky07:
YO thanks for the quick reply the room my phone wants

G891AUCS2BRC1 that'd be the latest official update
[Samsung Galaxy S7 Active Questions & Answers] staffeyx:
I guess you need to install BQD4 above, and then work your way up with the OTA files on that cloud page to reach BRC1.
[Samsung Galaxy S7 Active Questions & Answers] princessslinky07:
Only issue is the bootloader Is locked so I can't downgrade it to brc1 lol the bra update just came out a couple days ago ,thanks man for helping me out by the way very cool of you
[Samsung Galaxy S7 Active Questions & Answers] princessslinky07:
im an idiot i just figured out what you said haha i guess i was caught up on the whole i lost my own phone feeling
[Samsung Galaxy S7 Active Questions & Answers] staffeyx:
No problem man, I hope it works out for you.

The thing with the bootloader is that it has been on version 2 for quite a while, but in the most recent updates it became upgraded to version 3. You can see it in the file names. For example G891AUCS

2

BRC1 is still on version 2 while the most recent full Nougat ROM G891AUCS

3

BRD1 upgrades bootloader to version 3 with no turning back after that, as far as I know.
[Galaxy Tab S2 General] slowrey:
Looking for a basic tablet to run Plex and Sonos and I've been looking at the 10 in Samsung S2 64 gig. My wife had one at one time and she really liked it I liked how thin it was but not sure what a good price for one would be brand new. I found one for

$300.00 USD

from a reputable store brand new in box with full factory warranty.

What price would you pay for one brand new?
[Galaxy Tab S2 General] raybanBcn:
It depends the country I suppose , I bought it in Spain for 260€ . (It was an offer) about the tablet it works really well without any lag (I just returned a Lenovo yoga for that reason)
[Galaxy Tab S2 General] slowrey:
USA 300.00
[Galaxy Tab S2 General] jshamlet:
The Galaxy Tab S2 is still a great tablet, but $300 is a bit steep at this point. It's almost 3 years old, and has been replaced by the Tab S3, which has a faster processor. I wouldn't go north of $150-$200 at this point. Also, if mine broke I'd probably replace it with an S3.

The 64GB does change things a bit, but since you get an SD card slot, not that much. I have a 32GB and have had zero storage problems. I keep video, music, books, etc on the SD card and haven't even come close to filling its internal storage with apps.
[Galaxy Tab S2 General] slowrey:
Well do remember that for $300 brand new in box 813 version with 64GB of ram and the mSD card slot. I looked at the Tab S3 which was around $450 but I just had a hard time justifying that. Hell it's hard to find a good Android tablet now a days. Seems like they're either really budget or expensive. I'd be happy to find a one around $250.
[Galaxy Tab S2 General] Masteryates:
As $300 is about £225, I'd just about pay this for a brand new 813, 64GB. I'd be much more comfortable paying $180 for a used version though.
[Galaxy Tab S2 General] jshamlet:
It's certainly not a terrible deal. I still use my T813 daily, and I love the thing - to the point where I don't even bother carrying a laptop these days. (I have a travel keyboard) My only point is that it's hard to shell out that much for a tablet that is essentially EOL'ed by its manufacturer.

On the other hand, I just priced the Tab S3, and even in the 32GB config, it's a pricey machine. That might definitely tip the scales towards an S2, even at $300.