yashsingh1/xdaforums huggingface dataset:
[Desire 626 Q&A, Help & Troubleshooting] charliew410:
Ok, device is HTC Desire 626s bootloader unlocked, rooted, Super SU installed Android 5.1 Sense 7.0 (htc_a32eul)

I still have root at this point but this keeps coming up and I would appreciate someone telling me where I may find the binary update to flash?
[Desire 626 Q&A, Help & Troubleshooting] charliew410:
Again the SuperSU binary needs Updating, the last time was 10/9 and I flashed Beta-SuperSU-v2.51.zip, now 10/18/2015. Same device as above needs updating. It was as simple as clicking one time on the option other than recovery. Done in a minute.
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] RKramden:
As the title says, I'd like to use my custom ringtones, but since the VZW Edge + hasn't been rooted yet my question is, can it be done?

I'd like to insert them (ringtones) into the system ringtones library.

Thanks for your help!
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] RKramden:
Ok for those interested, I found the answer on my own. By using RingDroid, I re-created my ringtones & notifications and they show up in the stock tones so all is good!
[General Questions and Answers] Wiesner:
Hi guys, how are you? Excuse my bad English.

The point is that when logging into facebook from an application, the page loads improperly and when you log directly can not allow the application log.

And here after logging in, the page directly and not load the content required to allow the application to login with Facebook.

He hoped they can help me find a solution, until a few days worked smoothly and nothing happened.

Sorry for not being able to attach images.

Enviado desde mi SM-G530M mediante Tapatalk
[Hardware Hacking General] badboy2191:
I need an up to date guide complete phone be back up soft ware cuz I've only done this once before and I done want to

Mess up on thIs phone
[Hardware Hacking General] badboy2191:
Trying to root to install viper and ma K e it able to support 64 gb sd card

PNY Elite Performance 64GB High Speed SDXC Class 10 UHS-I, U1 Up to 90MB/sec Flash Card - P-SDX64U1H-GE
[Hardware Hacking General] badboy2191:
Worth viper4android works on it
[Hardware Hacking General] Tanmoy Mitra:
Use framaroot for rooting and to make ur phone support 64gb follow these steps:

1. Download device control(root)

2. Grant superuser access

3. Explore tabs until you see sd read ahead ratio. Change from 128 kb to other higher. It will make your phone still faster ( myth busted: sd above supported levels slows phone) while even a cheap 80$ non android phone can support 64 gb of card. My grandpa's samsung gt e2252 have 16 gb and box says expandable upto 2 gb.............
[T-Mobile Samsung Galaxy S6 Edge] PanchoPlanet:
Looks like Google is getting things ready for the Marshmallow effect, coming sooner than expected.

It seems like a daily routine getting play store updates, especially Google everything seems to be updating daily.

Judging from some articles and QBKING77 videos, marshmallow has a bunch of upgrades and system tweaks that will make our flagship S6edge feel like the phone of the future. :p

Pp. ;)
[Nexus 6 Developer Discussion [Developers Only]] chairshot215:
Have a feeling I will figure this out before answered and probably some snide smartest person in the room syndrome remarks but could help save me and some others time so going to bite the bullet and ask anyway. With Android 6.0 what makes some Kernels compatible for root and others not. Have read some tidbits in otherwise unreliable sources it has to do with Selinux being set for permissive mode. If true is this in the Kernel or can it be set in the Ramdisk? Link to a commit would be extremely helpful.

Otherwise have 3 builds going now. If correct pretty sure one of the 3 will work but confirmation makes me feel better.
[Nexus 6 Developer Discussion [Developers Only]] buckmarble:
https://github.com/Elite-Kernels/elite_shamu/commit/c91d04bb34b327d66212090a0de36aa29bd6840b

Done in kernel
[Nexus 6 Developer Discussion [Developers Only]] chairshot215:
Thanks had worked out in one of the three I was testing using SuperSu 5.1. Why I am trying to school myself on new changes it seems I am now encrypted by default using the same files (fstab.shamu) that I used in 5.1.1. Are you aware of any changes now required for 6.0? admittedly am using the same Anykernel set up as I had with Lollipop and am new to using the Anykernel method for flashing kernels as in the past would just compile the boot.img. Honestly had been used to releasing my own Roms and not just Kernels so some of these things are new.

Sorry I am not ashamed to admit when something simple is throwing me for a loop and ask even if makes me look like a dumb ars.
[Nexus 6 Developer Discussion [Developers Only]] Gandalf:
to remove force encryption you need to change "forceencrypt" to "encryptable" in the fstab for userdata. This will not automagically decrypt you, so if you flashed factory images, you will be encrypted again. You will need to format data in TWRP to decrypt again.
[Nexus 6 Developer Discussion [Developers Only]] chairshot215:
I just pushed my anykernel to Github so could post but is pretty much what I had done. what I had done was working after either format data or performing a factory reset with 5.1.1. Starting to think maybe my factory image flash had gone wrong. Could just be a change I am not aware of but did not see the optimizing apps screen after wiping. What I had essentially done is after flashing factory image rebooted bootloader and before booting the first time flashed TWRP installed my Kernel, flashed SuperSu 5.1 and then did a full cache and data wipe.

Admittedly with anykernel I had started by downloading another Kernel, forget which one and then removed or adding what I believed should for my Kernel. So far besides the little encryption issue seems to be working out OK. Trying to keep the Kernel as effective as possible with the fewest possible trade off’s. Not much original work in the sense a lot has already been done but have done lots of testing for efficiency.

Anykernel

https://github.com/Starship-Android/anykernel
[Nexus 6 Developer Discussion [Developers Only]] doitright:
I'm just going to leave these two links right here....

https://github.com/lbdroid/AOSP-SU-PATCH

https://github.com/phhusson/Superuser

That will yield an ENFORCING, and NON-RELOADABLE selinux policy, allowing root, and all bundled into the boot.img in order to maintain the integrity (dm-verity) of the system image!

Take THAT Coding Code Mobile Technology LLC!!!!!

And for people who want to know the true history of things (rather than worshiping people who distribute binaries....), please read this; http://www.koushikdutta.com/2008/11/fixing-su-security-hole-on-modified.html and then look at the github label (that says "forked from") on the Superuser repository I linked above.
[Nexus 6 Developer Discussion [Developers Only]] chairshot215:
Thanks I have been bed ridden for a bit but will look over all these things. In short my last build I first flashed chainfires boot.img and rooted before flashing my Kernel. Was able to do this without putting my Kernel into permissive mode. Had also unpacked the chainfire boot.img and used a few things in my boot image and used Meld and made a few other edits based on chainfires boot.img. Still having an issue with encryption being forced that just has me baffled. Was otherwise a temporary quick fix for not having to put the Kernel into permissive mode.

Definitely appreciate all the feedback and am learning allot so thanks for that everyone.

Otherwise the Encryption is driving me mentally insane. Like straitjacket throwing myself around a small room with rubber walls and a door with a slot that keeps opening with a tray of drugs and food sliding in insane. It has become so frustrating.

this is the fstab I am using and see know issue. Have also tried Despair, Vortex and the fed_patcher patch not to mention Chainfires Kernel for Root and no matter how many times I wipe data or factory reset it is always encrypted. If it was not knowing the encryption is done via software would swear something is wrong with the phone. Have also changed up TWRP 3 times as noticed I no loner see updating apps but that is also the same in that encription is still forced

https://github.com/Chairshot215/anykernel/blob/master/ramdisk/fstab.shamu
[Nexus 6 Developer Discussion [Developers Only]] doitright:
The problem you are running into, is that recovery doesn't actually *format* the userdata partition, which means that a factory reset from recovery won't *remove* the encryption. The reason it doesn't format is to prevent the deletion of /data/media directory, which gets mapped to /sdcard.

What you need to do, is reboot to bootloader, and run "fastboot format userdata".

If you aren't permissive, then the big thing you must have taken from chainfire's boot.img, is the sepolicy file. He only actually changed two files; sepolicy and fstab.shamu.

The thing to be aware of, though, is that his supersu, despite running selinux enforcing, is actually putting a lot of domains into permissive. When you go through your kernel audit log, you should pay attention to the end of the audit log where it says "permissive=1" or "permissive=0". You will find a lot of "permissive=1". Using *my* sepolicy, which is NOT compatible with his supersu, you will find that ALL domains remain enforcing, yet we aren't increasing the authority of any domain besides the "su" domain, AND, there will actually be far fewer denials against root/su. On top of that, I actually block the su domain from messing with kernel security. In other words, we do NOT allow the su domain to change selinux to permissive, OR to reload the policy. Both of those ARE permitted in chainfire supersu, which is incredibly dangerous, given how root is typically used on Android.

To put that into perspective, the ability to change the enforcement status or reload the policy, makes it possible for a malicious application to modify the boot.img to disable dmverity on the system partition, and compromise the system partition. My approach makes it possible to maintain the integrity of the boot partition and therefore maintain dmverity on the system partition, while providing root access. This makes unauthorized changes to the system partition immediately obvious and ineffective, since dmverity will refuse to read changed data, instead returning an i/o error.

The verity keys are actually stored on the boot.img, which means that it is still possible to make *intentional* changes to the system partition (through regenerating the key), and prevent unauthorized changes.

I've been considering adding a new domain to the effect of "su_sensitive" that will enforce strong password input for every authorization request in order to grant kernel security permission, but it remains to be seen if this would even be helpful to anyone.
[Nexus 6 Developer Discussion [Developers Only]] Cheapo2311:
How do you even edit a kernel? If you could explain, please do so.
[HTC Desire 526] mohamed2020:
i installed philz recovery to my phone and now it doesn't start

what should i do ??? :(

HTC 526g
[HTC Desire 526] pempa:
How i wish id seen this earlier..i also installed clockwork mod recovery and bricked my 526G.At first it was soft bricked but i did something wrong on sp flash tool trying to recover it and it got worse..Ive done some research and found out its possible to recover my phone if i can just get my hands on a mtk droid tools back up of my specific ROM..If you can create this backup and share it with me ill really appreciate your effort bro
[HTC Desire 526] mailavaramjyoyhsma418@gma:
Hii D's s jyothsna my HTC desire 526g+ has been dropped from my hand then d original display was damaged.can I replace d display
[General Topics] Alien66:
Hi Buds

Got Route66 for Nokia N95.

Need maps for South Africa.

Any ideas as to where i can obtain it, other than buying from Route 66

Thanks

:D
[General Topics] vlodeck:
We do not allow warez here. Closing.
[G4 Accessories] Milimbar:
dbrand was kind enough to ship me some skins for review for both the LG G4 and LG G3.

I figured I would post the reviews here on XDA to help the most people I could, here goes.

For the LG G4 I have the Black Carbon Fiber skin with accents and the White Carbon Fiber skin with accents.

For the LG G3 I have the Mahogany Skin with accents, and the Zebra Wood Skin with accents.

The skins arrived in simple plastic sleeves with a dbrand insert and the skin itself.

Once you open these the first thing you will notice is the skins have a texture.

The carbon fiber really looks and feels like carbon fiber.

You can actually feel the wood grain in both the wood skins.

The printing on these skins is second to none, they all look realistic.

The cutouts on the speaker grill, camera, and sensors are perfect.

The application of this skin is the easiest yet.

All you have to do is place the button and camera covers (accents) on.

Then just use the 3M paper to keep the entire skin from sticking as you align the camera cutouts.

Realign the paper sideways and align the speaker cutout.

Remove the paper completely.

Finally use a hair dryer or heat gun to heat up the edges and press them into place.

I used a heat gun on the lowest setting, a hair dryer may take slightly longer.

Just in case you do not believe how easy the install is, I have made a video of me installing one.

Remember I have no extra experience doing this, it is this easy.

https://www.youtube.com/watch?v=IQFYXfo47Z4&feature=youtu.be

Once installed you will really see how perfect dbrand made these skins.

Every cutout and edge will be exactly where it should be.

There are no overlapped places or short edges.

I have used both Skickwraps and dbrand and in my opinion dbrand has done a much better job with their skins.

If anyone is considering skins, dbrand is the way to go.

At $9.95 for just the back and accents and $17.95 for the back, accents, and front, these are a great price.

https://dbrand.com/shop/lg-g4

I hope this review will help someone.

Please ask any questions you want, I will try and answer if I can.

P.S. my favorite is the White Carbon Fiber back with the Black Carbon Fiber accents.
[G4 Accessories] mohammad_othar:
Do these stay on the leather cover ?
[G4 Accessories] munkypoo7:
They're for the plastic backs, not the leather backs.
[Android Q&A, Help & Troubleshooting] Tiribulus:
Forgive my novice status with both my first Android phone and this site. Galaxy S6 which I rooted using Odin and I believe a kernel it was, from here.

If I run the os upgrade from Smartswitch, what effect will that have one the phone as far as being rooted and all the stuff I've done since being rooted. Thank you very much.
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
If you update, you will lose root. I would not update via Smart Switch, being that you are rooted with a custom kernel. Your best bet would be to update via Odin. Check the subforum here @ xda for your variant of the S6 for further info. You should find what you need in the General forum of that subforum.
[Android Q&A, Help & Troubleshooting] Tiribulus:
Thank you sir. Is it simply a matter rerooting the device? Or will every other change I made from root be gone too?
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
It will wipe your phone, so you will have to redo any mods or settings.
[Android Q&A, Help & Troubleshooting] Tiribulus:
It wipes the phone every time you do an operating system update? Why would anybody ever do it unless something wasn't working? Unless it's only when rooted? I have good pc skills and some understanding of Linux even, but man I have a lot to learn about these phones.. What about Smart Switch backups? It wipes the phone, how close to before the update will that get somebody? I don't have time to research all this. I may just leave it. This update I'm talking about is a gigabyte btw. That seems pretty huge for a phone.
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
[Android Q&A, Help & Troubleshooting] Tiribulus:
It just occurred to me. Firmware IS the Android OS on these phones. That's not the same as a kernel though? With the regular Linux os it isn't. Forgive my ignorance. Like I say this is my first one.
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
Unfortunalely, firmware is one of those terms that can mean a few different things depending on the situation (like flashing). Firmware in this instance refers to the bootloader and modem files as well for Samsungs. If you don't have the bootloader and modem files (which roms do not install) correctly matched to the OS then you might have issues like not being able to boot or cell service issues.
[Android Q&A, Help & Troubleshooting] Tiribulus:
What I'm wondering is if there's any to have this galaxy s6 just like it is now after many hours of tweaking after one of these updates. I couldn't make heads or tails out of Titanium update.

You are being very helpful sir. Thank you.
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
Depends on what tweaks you've done and which update that it is. If it is a minor security update, then usually someone will post a flashable via custom recovery version and often you can get away with installing that over your current system while just wiping cache and dalvik cache. If it is a major update, like when Marshmallow comes out, it would benefit you to do a factory reset before updating. Yea, it sucks having to set up your phone again, though with all the tools available, it's really not that bad, but better to start fresh instead of wondering if the phone is slow or buggy because you didn't.
[Android Q&A, Help & Troubleshooting] Tiribulus:
You're making sense. I totally get it. (about starting from scratch) Can I then re-root it with the same UniKernel-v5-920P-072715.tar as before or will I need a new one of those too.? Thanks again.

This is the update SmartSwitch is telling me is available. I don't even know which of this stuff we've been discussing this is. Firmware, ROM or OS update.

Current version: PDA:0H1 / CSC:0H1/ PHONE:0H1 (SPR)

Latest version: PDA:011 / CSC:011 / PHONE:011 (SPR)

Size: 1612 MB
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
That's just a minor security update. I would not use that kernel to reroot. I believe the only option available for the update you are on and the update that is available is via TWRP + SuperSU zip.
[Android Q&A, Help & Troubleshooting] Tiribulus:
Whatsa TWRP + SuperSU zip :o Is that a tool and file for getting this update?

Sorry man. I've had this phone for less than 2 months and it's my very first one.

I do appreciate your patience. I've been a PC support guy for 16 years. I know what it's like.
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
TWRP = Team Win Recovery Project. It replaces the stock recovery that the phone uses to perform factory resets and updates signed by Samsung. This allows you multiple benefits such as complete system/data/kernel backups, being able to wipe any combo of system/data/caches/internal storage, factory data reset without wiping internal storage, terminal commands, and installing custom files, roms, mods, etc not signed by Samsung to name a few. SuperSU is the popular root binary and root permissions app made by the developer Chainfire. If you needs links, I can provide, but assuming you're familiar with Googling things being a support guy. ☺
[Android Q&A, Help & Troubleshooting] Tiribulus:
I have SuperSU already.

These are some truly terrible directions unless you already know enough to not need them.

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

Will installing TWRP effect the root method I've already used?

Will installing recovery effect any of the multitude of configurations I've already done?

Does this then allow manual installs of OTA updates without losing root or any of your configuration customizations?

Is it JUST the recovery partition were dealing which stands alone from the os?

Does Nandroid backup then encompass the recovery and os and rom etc? Meaning are they all backed up and custom recovery via TWRP was what made that possible? Or do you have to make your current config the recovery itself in order to do a ghost style backup and restore if you jack yourself up later? OR is not even this a ghost style restore?

Maybe it's just me, but the terminology is very confusing and I can't make heads or tails of what I'm even talking about with all this.
[Android Q&A, Help & Troubleshooting] Tiribulus:
Tried to make backup with TWRP...

I guess whatever I flashed it with last time won't let it boot into recovery or the bootloader or whatever it's called. If I tell TWRP manager to reboot and do backup it just goes to the menu for rebooting and wiping cache etc. If I specifically go to "reboot to bootloader" it just reboots into android. I went to install a custom recovery and it said that if the location for the recovery is wrong it could brick the phone. I have no idea if it's right or wrong or if the root method I've already used is effecting this or not. :confused: