yashsingh1/xdaforums huggingface dataset:
[SuperSU] Squall88uk:
Is there any way to use SuperSU in CM13 or CM13 based roms such as Resurrection Remix? In particular on a Nexus 6P?

I ask because I have been using RR for quite some time now but until recently never really noticed the limitations of CM's privacy guard. SuperSU pro has always seemed like a better implementation of a Root management app to me when I've used it in the past on previous devices.

I had considered just disabling root access from the setting in developer options and then updating the binary from the SuperSU app via TWRP and hoping that SuperSU would take over root management after that but I have read that a few people have bricked/bootlooped their devices after doing that and I don't want to have to deal with fixing that.

Many thanks in advance for any help you can provide.
[SuperSU] Ibuprophen:
After disabling the root option within the Developer Options, when you open SuperSU and go to the Settings, do you leave the option for "Respect CM root settings" unchecked?

With CM/LOS, when you disable the root option, in SuperSU, you need to keep the "Respect CM root settings" unchecked or SuperSU will default the root to Disabled.

Many individuals don't know that.

Peace and Love!

Peace and Love!

~Ringo Starr~

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[SuperSU] Squall88uk:
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.

When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.

Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
[SuperSU] solfly7:
I am in the same boat. I am using the the latest RR FROM which is awesome, but I'm not wanting to use magical. Have always used super SU and stick Mount for my next SD. Would like to know the process for disabling manual and cm/Los root mgmt. To use Super SU. I can't use stick Mount with root explorer without super SU. WHEN I try to update binary it fails and if I try to flash in recovery, I get stuck in boot loop and have to restore backup.
[SuperSU] kikot:
Having a similiar problem on Galaxy S2 with RR 5.8.2 - installed SeperSu and it fails to update its binary when I choose 'normal'. Tried Cwm/Twrp option on a stock rom once and the phone got softbricked. Converting SuperSu to system app doesn't help.

---------- Post added at 05:05 AM ---------- Previous post was at 04:48 AM ----------

No such option appears in SuperSu after disabling root access in dev options here also.
[SuperSU] Ibuprophen:
There was a time a while ago that I had asked something similar to to one of the CyanogenMod Team Developers.

I was told that when the Superuser option (in the Developer Options) is set to disabled, that means that the CyanogenMod systems Superuser access is left open. When one of the other options are set, that means that the CyanogenMod system is set to manage Superuser access that is seen by the new access to the Manage Root Access option below it.

So in short, disabled means root access is left open and CyanogenMod doesn't manage it.

If you use another root management app, like SuperSU, and leave the Root Access on disabled, then SuperSU takes on managing Root Access.

I've never had a problem with SuperSU and always left the Root Access disabled.

I hope i had explained it okay...

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

***PLZ THANK ME WITH A THUMBS UP***
[SuperSU] kikot:
Disabled Root access in developer options, rebooted phone and started Supersu, it tries ro update its binaries and fsils again. Then I look for the "respect CM root settings" option but don't see it.

Some people are having success flashing the Supersu.zip through TWRP but isn't there a risk of replacing the RR bundled recovery and ending in bootloop? Is it possible to flash TWRP zip from RR recovery without causing more issues?
[SuperSU] Ibuprophen:
I attached an image of where in SuperSU the setting is but, I leave it unchecked...

Try flashing the SuperSU zip since flashing it also installs the binaries too.
[Remix OS for PC] omarswt:
I'd prefer iconless desktop, but there didn't seem to be any setting for such. Does someone somewhere have to change something in the source code or could I tweak something myself?
[Shield Android TV Q&A, Help & Troubleshooting] Ichijoe:
Ok I just managed to really screw up my nSATVP last week by basically deleating the bootloader from my Device.... Why did I go and, do that for? You ask. Well thats 'cause I signed up for nVidias Beta Test Program for v5.0.1 which hasn't been released yet. And like always TWRP choked on it, and the Shield couldnt install the OTA. So in a fit of desperation I decided to stupidly downgrade it back to v3.3.0. which resulted in the Black Screen of Death. Though as a consolation I still had Fastboot, at that time.

In any case I managed to recover my Shield, via the SSD Conversion Thread(s), where someone was kind enough to post the needed start, and end bins which can then be copied to the SSHD/SSD. Of course this comes at a cost. You loose Netflix, and of course Amazon as well... Some People have likened this to be down to the ESN (Netflix: Electronic Serial Number).

Having a bit of a nose 'round... I'm inclined to think its more down to the lose of Widevine L1.... At the moment I only have L3 access. And, I'd be willing to jump in a fire at this point as the cause.

What I was wondering was it it could be possible to copy the missing /data/mediadrm/IDM1013L1 Files back from a working Shield TV?
[Shield Android TV Q&A, Help & Troubleshooting] wikkid76:
I was hoping you'd get a response.

I lack the technical know how to find a solution to this. But I do have a 1st gen shield running that start and end bin files, and I (stupidly) tossed the original Shield drive before finding out Netflix and Amazon would be broken.

I've done a fair bit of reading and have yet to see a fix, or really anyone working on one.

Would love to have my 1st gen Shield able to work with Netflix and Amazon once again.
[Shield Android TV Q&A, Help & Troubleshooting] Ichijoe:
Well my understanding on this matter is that once you lose Widevine L1, than that's it! The only way to get it back would be to send it back to nVIDIA (Or hereafter The Factory), and let them to reset it. As only the Factory can install either L1, or L2 Widevine. Widevine L3 (The lowest level DRM Setting), however can be installed pretty much by anyone. As unlike L1, and L2 which are Factory set. L3 is Field settable, so we're just SOL.

Perhaps I might try contacting nVIDIA at some point about what it would cost to fix this outside of warranty. My only fear is that it would likely be the same price as a new Shield.

So the plan (for me) right now is to just suck it up, and lay some money again to the side, and pick up another Pro, down the line. And than strip the SSHD, and create the start, and end bin, backups, and than make multiple on, and off site copies of that. Than most likely, as not resell the broken Shield TV on FleeBay. To recoup some of the loss.

The morale of the story here is if your going to root, and install TWRP on your Shield Pro. You should first make the appropriate backups, and for the same reasons. It's rather disappointing in hindsight that all the How To's out there never bother to mention it. There are plenty of veiled threats about downgrading the Shield. But, bricking the Shield TV that way is way to easy. Easier than it should be.
[Shield Android TV Q&A, Help & Troubleshooting] hallydamaster:
I'm trying to locate the partition containing the serial number.

If any of you guys could post me an output of the nct partition, it would be a help hopefully.

Extract it using this dd command:

dd if=firstpart.bin of=nct.bin skip=20480 count=4096

Substitute "firstpart.bin" with whatever your bin file has for a name.
[Shield Android TV Q&A, Help & Troubleshooting] Ichijoe:
Ok heres the nct.bin File you asked for. you can find (I think... according to my Hex editor on Linux), the S/N @ Offset 040014.

Please note that since I can not post *.bin Files to this Board I took the liberty of simply renaming it *.zip instead.

SO PLEASE REMEMBER to rename this back to *.bin. Before you start looking at it.

BTW: Assuming your going to do what i think your going to do with this how would you re-insert this again?

To the File which you (or I), ripped it from, or to the SSHD direct?

Thanks
[XDA Assist] chribu:
Hi,

I got a HTC ONE from a friend.

The phone belongs to her husband who died just recently. The phone contains last photos he has taken which are of much value to her.

The problem is that the phone is stuck at the boot screen and won't start up normally.

Here is what I tried:

- Various types of hard-reset (pressing all available buttons plus power button simultanously)

- Going through all available features of HBOOT, FASTBOOT and RECOVERY menu (except "Factory reset" which as I understood would rescue the phone but kill the photos. By the way, this is what all the threads I followed boil down to)

- Connect to various PCs with various operating systems (including Win7, Win10 and Ubuntu), where the phone is recognized but cannot be connected as an MTP device because of problems with the driver install. I wasn't able to fix the driver issue so I didn't get access to the internal storage

- Putting the phone into a refrigerator for some time and trying to reboot (I know this sounds stupid but it was one of the many advices I read in the threads). This obviously was useless as well.

So here I am without any idea left on how to rescue the data.

I don't even know which kind of HTC ONE it really is. Here is what I know.

The phone has the model number PJ46100 printed on it (this seems to be a HTC ONE X).

In the HBOOT screen it gives me this information:

*** LOCKED ***

ENDEAVORU PVT SHIP S-ON RL

HBOOT-1.72.0000

CPLD-None

MICROP-None

RADIO-5.1204.163U2.31

eMMC-bootmode: disabled

CPU-bootmode: disabled

HW Secure boot: enabled

MODEM PATH: OFF

Jun 21 2013,18:24:41

Is there any know way to access the data? The phone may get damaged on the way. It will get thrown away anyway after I finished because there is nobody who needs it anymore. So I'm also interested in destructive methods if breaking the cover of the phone and physically accessing the memory component brings me any further.

As you can see from my approach of even refrigerating the phone I'm pretty desparate about the data now. Any help would be much appreciated.
[XDA Assist] sawdoctor:
Greetings and welcome to assist. If you factory reset through recovery this shouldn't format internal storage so the photos should be safe. You can also try adb to access the internal storage and get the photos

Good Luck

Sawdoctor
[Galaxy S 5 Q&A, Help & Troubleshooting] saikyom:
Hi all, I used to have an s3...recently bought an s5 with the model described above

I used to have resurrection remix rom with nougat and boeffla kernel.

my new device is rooted and i have twrp, i just don't find (know) which rom to put in it.

any help would be appreciated .
[Nexus 6  General] RegnierD:
Hey all! I've been thinking about starting up a series of how-to videos and guides for people that work better seeing steps being taken versus reading the order of operations for important things like reverting to stock, flashing factory images, sideloading, etc. I miss helping people troubleshoot, and am looking to get back into a more direct route of helping people than just forum lurking.

Is this something that people think would be helpful? If yes, give me some subjects that you would personally like to see in action, and I'll get a YouTube channel up and running in the next week or two, and then get to work on any guides on the same content.
[Nexus 6  General] andy_n_:
I prefer text/pictures. Easier to search, quicker to absorb, and easy to reference.
[Nexus 6  General] RegnierD:
Alrighty. Walkthroughs with pictures are easy enough. Are there any specific subjects you'd like covered?
[Nexus 6  General] zelendel:
I'll be honest. You will be hard pressed to come up with something that is not already done. By now any tut or walk through that would be needed has already been done a few hundred times. Everything here now is basics.
[Nexus 6  General] brljak83:
I think you should do it. But you would have to be making also a short video but covering the subject. Couse I would not watch a 5min clip to do something. I dont like long videos. And my opinion it helped me several times to see something on you tube. My suggestion make like 1min clip of unlocking then next clip short of rooting and so on..

Evan some reviews or performanse videos could be of use to. And yes there are already videos but go for it make some too... Why not
[Nexus 6  General] NLBeev:
One suggestion: no talking [emoji1]
[Nexus 6  General] Dopamin3:
In my opinion no it's not worth it to make the videos. Most of the time the information is already out there either in text, sometimes videos but people are lazy and don't take the proper time to search before asking questions.

If you want to do it, go for it man! I'm sure some people will appreciate it but it doesn't interest me at all. Not to sound snobbish, but I learned about unlocking the bootloader, recoveries like CWM and TWRP, ADB commands, fastboot commands, factory images, etc... in a few hours and once you know it you can do literally everything you want to the Nexus 6. It kills me so many noobs rely on toolkits. This might be an unpopular opinion, but if you have to rely on a toolkit then you should leave your phone at 100% stock and not mess with it.

If you do decide to make videos you can cover tons of stuff, whatever you feel comfortable with:

-ADB and fastboot commands

-How to root and the benefits of each method (SuperSu, phh's Superuser, etc...)

-Themeing with OMS/Substratum (or CMTE)

-Unlocking the bootloader and the affects it has

-TWRP- installation, nandroid backups, what the different partitions are for, etc...

-Encrypted vs decrypted, how to do it and what are the benefits of each

-Kernels- what settings you can tweak (with Kernel Adiutor or KA MOD) and how to switch between them easily (make a backup of boot.img so you don't have to dirty flash your ROM)

-Returning to 100% stock
[Samsung Galaxy S7 Edge Questions and Answers] Andvoider:
Getting tired of waiting for the official firmware from Samsung. Is there any other Nougat firmware that is compatible for my SM-9350?

Thanks in advance.
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] davidteri91:
This is AOSP for Sony Xperia X Compact (Kugo) (F5321)

SonyAosp build will always mainly based on AOSP with some Material stuff

/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

IMPORTANT: Make sure you have an unlock Bootloader

Please if you have Locked Bootloader you may check this http://developer.sonymobile.com/unlockbootloader/

WORKING
- RIL
- Mic
- Sound (Speaker and Headset)
- LED
- Thermal Manager
- Audio and Video Decoders/Encoders
- Camera (WIP)
- Recovery (Only for flash signed zips)

XDA:DevDB Information

[Oreo 8.1.X][X Compact - F5321] Android Open Source Project, ROM for the Sony Xperia X Compact

Contributors

davidteri91

Source Code: http://Github.com/SonyAosp

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 4.x

ROM Firmware Required: Unlocked Bootloader

Based On: AOSP

Version Information

Status: Stable

Created 2017-02-12

Last Updated 2018-03-25
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] davidteri91:
Download​

Follow me for be adviced for new builds​

This ROM has included GAPPS

Steps for Flash

[FONT="Arial"][SIZE="3"] fastboot flash oem xxxxx.img [/SIZE][/FONT]
[FONT="Arial"][SIZE="3"] fastboot flash boot boot.img [/SIZE][/FONT]
[FONT="Arial"][SIZE="3"] fastboot flash recovery recovery.img [/SIZE][/FONT]
[FONT="Arial"][SIZE="3"] fastboot flash system system.img [/SIZE][/FONT]
[FONT="Arial"][SIZE="3"] fastboot flash userdata userdata.img [/SIZE][/FONT]

Please make sure your device is updated to latest sony software present on flashtool due to loader requeriments

To flash oem partition you should download odm.img from https://developer.sony.com/develop/open-devices/latest-updates/

You don't need flash userdata everytime .... only first time ..... userdata.img will wipe your data... you may be adviced ​
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] gizzistar:
Thanks David, I'm gonna try your ROM asap!

(PS. poi se hai bisogno di feedback e test più specifici fammi un fischio! grazie che ti sei interessato al compact)
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] Micka84:
Awesome, looking forward to flashing this ROM. Could you post a few pictures of the ROM? Do I need to root my device? I guess not, just asking to make sure everything works as it should. Wiping userdata doesn't wipe my SD card, right?
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] destinygs:
1. no you don't need root

2. everything seems to work fine and very smooth, except my SD card is not detected. (need to confirm about the sd card issue)

3. flashing userdata doesn't wipe your SD card, but it wipe your internal storage.
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] wlewin:
Thx for the work on this!

The SD card is concerning. once that is confirmed I can safely take the plunge and provide feedback.

Question, does the fingerprint sensor work?
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] destinygs:
fingerprint work
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] lba810701:
Hi David!

I hope i'm not disturbing in this forum, but i saw your tweeter site, where you wrote " KUGO meets LinageOS ", and posted a screenshot about it. Can you give us a link, where we could download it, and try it? Or maybe you will make another forum thread to it? If I wrote the wrong place ( because of it's a separate part of the AOSP ) eliminate my typing, or move to another thread. Thanks for your reply, and your work for our kugo :)
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] andjs:
Big thanks for bringing AOSP to Kugo! So glad to get away from Sony branded ROMs.

Been using for last few hours and everything seems to be working perfectly including SD card, Bluetooth and compass/gyro. Only exception is camera as mentioned in OP which only sometimes works.
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] Micka84:
My sim card doesn´t get a network connection plus my sd card won´t be recognized. Except for that and a few error messages, everything else works.

Strange that everything works for you andjs.
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] andjs:
I came from a completely stock 6.0 ROM if that helps.
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] toeterbaas:
nice work !

Do i need to backup camera keys? drm?

Does the camera not break? like noise with low light
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] toeterbaas:
I just flashed it cause i hate sony launcher.

My drm is lost forever but okay.

Camera is only 8 mp max? makes dark pics
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] andjs:
Go to settings > extended settings. Then you can switch between 8MP and 23MP.
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] toeterbaas:
thanks.

The camera is useless its dark as hell.

Front camera is useless to.

Love the rom :) if things get fixed its my favorite ever
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] davidteri91:
Camera crashes were fixed and will included in next release

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] toeterbaas:
Great news is the quality good then?

Any news for the next update :)

Very happy you develop

Also is there a drm fix inside?

I am sorry for asking
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] Micka84:
When will you release the next build?
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] BadBoy4490:
You do realise that drm only work for Sony proprietary software that is by definition not in AOSP, right :confused:
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] toeterbaas:
I didnt know as this is my first sony device.

Why are there so less people have a sony?
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] nosakaryota:
Good work with some small issues

Other functions work properly.

But I wondered which version of oem file should I download to avoid the tip of "Internal problem"?

I have tried for v13, v15 and v16 of 4.4 kernels. It does not work.
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] maluus:
Hello David,

When I try to build from your source I get an error as follows:

[117/993] including device/sony/common/Android.mk ...

/bin/bash: línea 0: pushd: /home/malus/android/out/target/product/kugo/odm/: No existe el archivo o el directorio

[924/993] including vendor/opengapps/build/modules/Chrome/Android.mk ...

vendor/opengapps/build/core/find_apk.sh: línea 24: lzip --decompress: orden no encontrada

Warning: lz decompress command failed for vendor/opengapps/sources/arm64/app/com.android.chrome/24/nodpi/353806452.apk.lz

WARNING: No APK found compatible with API level 28 for package com.android.chrome on arm64

[975/993] including vendor/opengapps/build/modules/PrebuiltGmsCore/Android.mk .

vendor/opengapps/build/core/find_apk.sh: línea 24: lzip --decompress: orden no encontrada

Warning: lz decompress command failed for vendor/opengapps/sources/arm64/priv-app/com.google.android.gms/28/320/14366038.apk.lz

vendor/opengapps/build/core/find_apk.sh: línea 24: lzip --decompress: orden no encontrada

Warning: lz decompress command failed for vendor/opengapps/sources/arm64/priv-app/com.google.android.gms/28/nodpi/14367037.apk.lz

vendor/opengapps/build/core/find_apk.sh: línea 24: lzip --decompress: orden no encontrada

Warning: lz decompress command failed for vendor/opengapps/sources/arm64/priv-app/com.google.android.gms/28/480/14367039.apk.lz

WARNING: No APK found compatible with API level 28 for package com.google.android.gms on arm64

[993/993] including vendor/sonyaosp/twrp/twrp_usb/rootdir/Android.mk ...

hardware/qcom/display/sde/sdm/libs/hwc2/../../../common.mk: error: hwcomposer.msm8952 (SHARED_LIBRARIES android-arm64) missing vendor.display.config@1.2 (SHARED_LIBRARIES android-arm64)

You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.

hardware/qcom/display/sde/sdm/libs/hwc2/../../../common.mk: error: hwcomposer.msm8952 (SHARED_LIBRARIES android-arm) missing vendor.display.config@1.2 (SHARED_LIBRARIES android-arm)

You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.

build/make/core/main.mk:833: error: exiting from previous errors.

20:11:41 ckati failed with: exit status 1

#### failed to build some targets (02:58 (mm:ss)) ####

How can I solve this? Thanks in advance.
[Sony Xperia X Compact ROMs, Kernels, Recoveries, &] papashi2342:
Hi there.

I have a problem with current AOSP version. I've flashed it, everything works fine except Phone app. It says something like "Process com.android.phone has stopped working", sometimes once but sometimes it spams and therefore prvents from using phone. It's very annying and I'm aware it might be a problem if someone would call me. Tried wiping dalvik/cache and data of app itself. Is this build-dependent issue or I've done something wrong?