yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S3] benrees21:
Just wanted to say thanks for this!! Works a treat! Even asked me to update the app, which it did and worked straight away!! Finally!!! Shocking it's still not officially available on Oreo!

---------- Post added at 04:40 PM ---------- Previous post was at 04:38 PM ----------

Thanks for this! Works a treat! Just had to install as I don't have root etc....
[Samsung Gear S3] TheUndertaker21:
anyone managed to get this to work with the latest version

i'm on pixel but since there's no magisk yet

we can only use suhide but samsung pay still detect root

maybe it's because of busybox but i can't find busybox anywhere

does supersu use busybox? i looked in xbin, system/bin. still nothing
[Samsung Gear S3] jakoob_cz:
Hi there,

running OmniROM without root, but the Samsung Pay still shows me my phone is rooted. Is there any app to trick the Samsung app? I see you are mentioning SUHIDE, but I don't want to root. Thanks
[Samsung Gear S3] coolhandz:
I believe omnirom has busybox as part of the ROM itself. SPay detects Busybox as root and therefore won't work.
[Samsung Gear S3] jidccruz:
Hi, I have a Pixel XL running Oreo 8.1 DP2 and planning to ditch my Huawei watch for a Gear S3 Classic.

1) Is the compatibility good between Pixel and S3? (Accessing messages on my watch and customizing the watch faces are not big deal for me). Notifications, health tracking are what important for me.

2) Is Samsung Pay working on 8.1? SPay is the main reason I want to switch other than the better battery.

Is it a good idea switching from Android Wear to Tizen if my phone is Google Pixel?

Thanks in advance guys.
[Samsung Gear S3] TGUY25:
FYI, used this tutorial for my Huawei Mate 10 Pro and it worked like a charm! Thanks!!!
[Google Pixel XL Questions & Answers] mintee:
So last night I installed Oreo from the official google release. https://developer.android.com/about/versions/oreo/index.html

Today I'm struggling to hear phone calls from the actual phone (as in the other person talking on the phone). I haven't tried earbuds or anything else yet. The ringtone and notification volumes seem a little weaker than the 7.1.1 stock I was running. Everything is at Max...

Has anyone else witnessed this issue, or is losing your hearing another post-eclipse side effect?
[Google Pixel XL Questions & Answers] itch808:
Strange, I haven't noticed this. I took the OTA
[Google Pixel XL Questions & Answers] iceman4357:
huh....seems same if not louder to me actually.
[Google Pixel XL Questions & Answers] fletch33:
i installed manually with the image and no sound issues
[Google Pixel XL Questions & Answers] ithehappy:
Yep I have stopped bothering to mention these because my expectations have become incredibly lower from these so called upgrades, but yes, earpiece volume in call, ringtone volume, both are lower than 7.1.2, 100% certain about that. I make a lot of phone calls so it took me only 1 minute to notice. Well done Google. Loud in call volume was one of the better things for this phone.

No OTA, full image flashed with wipe here.
[Google Pixel XL Questions & Answers] MrWolfman:
check that its not trying to play sound through a connected bluetooth device, when i upgraded it was send mine through my watch had to turn off my watch and reboot then the sound went the the phone ok
[Google Pixel XL Questions & Answers] 1902:
I received oreo via ota, and no issues here, try reinstall the img!
[Google Pixel XL Questions & Answers] mintee:
Well, I guess I'm just getting old and can't hear anymore.

*Damn kids on my lawn
[Google Pixel XL Questions & Answers] tacopimp:
Oreo call volume is extremely low. Tested it alongside of my wife's pixel running N and you can really hear the difference.
[Google Pixel XL Questions & Answers] fletch33:
so i stated above i didnt see a difference BUT today i did start paying more attention and so maybe someone else can test this but i use mine for work all day so i get a lot of time for calls on it and although my volume appeared to be set at 100% if while on a call i push the volume up it appears to get louder.

so i guess
[Google Pixel XL Questions & Answers] gaw54:
Hey all,

So I updated my pixel xl to Android O, and then used the modified TWRP to flash Super Su, SUhide. The phone booted up and everything was perfect. It was a little sluggish so I decided to do a full factory reset... again, phone reset, booted perfectly. I then restored all my apps from the google play store cloud... phone was functioning fine.

I went to reboot the phone after a while... and now the phone is stuck on the G logo after the bouncing dots... and just continues to load.

It's been like that for over 20 minutes.

Is this normal? Anyway I can fix this?

Thanks!
[Google Pixel XL Questions & Answers] edjanx:
8.0.0 rooting nightmare

I have the same exact issue after following the exact process described above. After a weekend of frustration, I was thrilled to see this post, but then bummed there are no suggestions. There is no way I can get it back to recovery, no matter what power/volume combination I try. The phone is not detectable by ADB either, so unless a kind soul has a suggestion, there seems to be nothing to do except let the battery die and hope.
[Google Pixel XL Questions & Answers] george241312:
Umm boot into bootloader and flash stock boot.img and system.img?
[Google Pixel XL Questions & Answers] edjanx:
I would love to do that, but how is it possible if there is no power or volume button combination that can get me off of the Google boot screen and into bootloader?
[Google Pixel XL Questions & Answers] george241312:
Have you tried Power + volume down ? It'll turn off after release power button only. That or let the battery die and when you try to plug it up next time leave vol down pressed.
[Google Pixel XL Questions & Answers] edjanx:
I have tried that, thank you. :) I will let battery die and do the Volume Down method you suggest, and report back.
[Google Pixel XL Questions & Answers] edjanx:
That did the trick. Back to stock 8.0.0, and hoping to find a stable root method that doesn't hang-up on the first reboot. Thanks for the help!
[Google Pixel XL Questions & Answers] mikaole:
First of all. Hold the power button for about 20 secs and the phone will reboot.

Hold vol - and you are straight to bootloader.

Second flash full factory to both slots.

And third stop using the - w solution when you are coming from another rom or a different stock version. We had this problems on other forums and it was every time - w or not flashing both slots. I know for many people there will be no problem but some apps are just misbehaving when you do so. And they are causing reboots and bootloops.
[Google Pixel XL Questions & Answers] edjanx:
OK, thank you! I am not familiar with the -w method. This is a new Pixel XL I received from Google to replace a nexus 6p with a bootloader issue. I made the mistake of not attempting this before it updated from 7.1.2 to 8.0.0, or it may have been a different story.

So I have the the phone restored to 8.0.0 and was going to attempt root. But I didn't realize there are two slots to flash. I simply ran flash-all.bat and the phone came back up. So I guess I'd have to move the Sept security stock image over to the phone along with the SU, SU Config (which may not be needed if on 8.0.0?), and Su Hide. Then I boot up TWRP 3.1.1 and flash stock image to both slots, reboot, then get back into TWRP and run the SU, then SU Hide on *both* slots?

Thanks!

Janx
[Google Pixel XL Questions & Answers] mikaole:
Run flashall.bat on the slot you are now in. Reboot to system

Back to bootloader. Switch slots through fastboot

fastboot --set-active=_b

fasboot reboot bootloader

Now you should be on the other slot

Flashall.bat

Reboot to system

Back to bootloader

fastboot boot twrp.img (latest)

In twrp put latest su or in my case magisk 14.2, twrp zip on device.

If you use su just flash it

If you use magisk. Flash magisk, flash twrp.zip and magisk again. With magisk twrp will stick.

Reboot and you are good to go.

If you want a kernel you have to flash twrp and magisk after again.
[Google Pixel XL Questions & Answers] edjanx:
Thank you! I will be able to perform this sequence in a few hours and will report back. :good:
[Google Pixel XL Questions & Answers] mikaole:
Ok. Will be in bed than. If you have any problems give me a PM and we can do it together via hangouts.
[Google Pixel XL Questions & Answers] edjanx:
Update: I successfully flashed A & B, got to the step where I flash Magisk 14.2. It finished unmounting partitions, but when updating partition details fails, "failed to mount '/system' (device or resource busy)...done

It said successfully installed, so I flashed twrp to the boot image, flashed magisk again, and it is now rebooting endlessly. Wrong place to flash the twrp image I'm guessing?

EDIT: Just noticed your message, good night - thanks again. I'm working through it and will take you up on your kind offer should I not find success.

I did a 'flash-all.sh' on both A and B again, copying over my old phone, then will attempt to gain root by booting into TWRP 3.1.1, installing "SR3-SuperSU-v2.82-SR3-20170813133244", reboot bootloader, go into TWRP again and then install "UPDATE-suhide-v1.08-20170815171034"

EDIT #2: EDIT #2: Stable root achieved using newer versions of files "SR5-SuperSU-v2.82-SR5-20171001224502" & after booting, applying "UPDATE-suhide-v1.09-20171001222116". So far it has survived several reboots, so I'm hoping it's all good now.
[Nexus 5X Q&A, Help & Troubleshooting] ibCurlyFry:
My phone suddenly would not turn on, no button combos work. I even tried combinations of button combos and pluggin/ unplugging the charger

I also took the back off and tried a battery pull, nothing has changed

the phone was charging all night and i have also tried charging it for an extra half an hour before trying button combos.

Any ideas?

UPDATE: I tried the vol down + power button combo again after letting it sit for a half an hour, and it went into the boot menu. I selected recovery. It booted into recovery, then after about 5 seconds it froze for about another 5 seconds, then it rebooted itself, and then its back to being unresponsive on a black screen...
[Galaxy Tab S2 Q&A, Help & Troubleshooting] hicho007:
please how to get permessive instead of enforcing?
[Samsung Galaxy S7 Edge Questions and Answers] aryan01:
Everytime i flash twrp with ODIN, my internal storage wipes out. and my stock rom also will be gone. its been like 5 times i tried, but i fail everytime. can anyone post the right way to root my s7 edge?
[Samsung Galaxy S7 Edge Questions and Answers] Cosmic Blue:
which root method are you using ?
[Samsung Galaxy S7 Edge Questions and Answers] aryan01:
This my friend..

https://www.google.com/url?sa=t&rct...YvxGYo&usg=AFQjCNHZ4qsErTGtVesN7EqRuzFdhQyFDw
[Samsung Galaxy S7 Edge Questions and Answers] EddoWagt:
That's a good method. When flashing twrp your internal storage will be wiped, you need to flash the no-verity-opt-encrypt.zip + a ROM, otherwise it won't work
[Samsung Galaxy S7 Edge Questions and Answers] aryan01:
alright.

Ok..!! so

1. flash twrp.

2. flash no verify opt encrypt.zip.

3. flash supersu or magisk.zip

4. reboot.

is this the right way?
[Samsung Galaxy S7 Edge Questions and Answers] EddoWagt:
Between 2 and 3 you also need to flash your Rom
[Samsung Galaxy S7 Edge Questions and Answers] aryan01:
Will do..

Sure
[Samsung Galaxy S7 Edge Questions and Answers] aryan01:
Just root, no need custom rom.

BRo, I just want root, so if I follow those steps, internal storage will be as it was and I will also get root access right?
[Samsung Galaxy S7 Edge Questions and Answers] EddoWagt:
No if you flash twrp everything on the internal storage will be gone , that's why you need to flash a ROM
[OnePlus 3T Questions & Answers] 3's&7's:
99% of my phone calls are through my car or a earpiece. I tried to make a call over the handset the other day and had no audio from the handset speaker itself. The lower audio speaker audio good (music, video audio, speaker-phone calls good), but the actual (upper speaker) handset audio speaker which is devoted to phone calls provides no audio whatsoever.

Callers tell me that they can hear me...so handset microphone all good + all other forms of audio output on phone calls good to go (mentioned above). I have flashed many rom's / firmware, etc. all the time so I really cannot tell when this happened or why it happened. But it seems like no matter what OOS OTA .zip version or separate firmware .zip's or Lineage OS / Customer ROM's does not seem to fix this.

Unlike a Google device (nexus / pixel) there does not seem to be a "Factory Image" per se that we can truly erase / partition / flash fresh OS data to really, really build the phone back up from scratch w/OnePlus devices. Always seems like solutions I find are OTA images for OEM recovery to flash or OTA zip's for TWRP recovery to flash...so not really sure if that's all there is to bring a OnePlus device to factory state or not (and for that matter it would really help)?

I ordered a replacement speaker ($4-5 usd) and found a few instructional videos on how to replace that piece of hardware as well in the event that is the real issue.

Any OnePlus 3t owners out there experience this before? :eek::eek::eek:
[Fire Q&A, Help & Troubleshooting] ebod:
Hi all, appreciate best practice is always to read posted guides but I'm getting kinda old and too many threads are only relevant at particular points in time when the 5th Gen Fire was newer. So basically I'm lost in conflicting info on the guides and need some direction.

Starting point is i) I've got 'basic' experience of rooting and flashing roms, so my PC has got ADB drivers etc. ii) I have a stock OS 5.4.0.0 5th Gen Fire which is my elderly mothers and the intention is to get the crap OS removed and make it a simple Nexus 7'like device.

Can somebody please give me some step-by-step advice. I'm at the point where the device is developer enabled and ABD enabled. But the guides I've seen are all based on old OS's so I fear the whatever I try next will just brick the unit.

Thx in advance :)
[Fire Q&A, Help & Troubleshooting] Jake1702_:
As of now, 5.3.2.1 - 5.4.0.0 can not be rooted, much less have the bootloader unlocked to install a custom ROM.
[Fire Q&A, Help & Troubleshooting] ebod:
aww bummer :(

OK second question : How should I treat the term "As of now"? Do you think there is any likelihood of a 5.4.0.0 root solution happening soon? i.e. weeks or months?

If its not gonna be a while, then I might just install the non-root google-play stuff and just shift the bloaty stuff out of sight if I can.
[Fire Q&A, Help & Troubleshooting] DragonFire1024:
EDIT: The usual warning: I am not responsible for any damage done to your device. If using ANY of these guides, you're doing so at your own risk.

That's about your only option at the moment. You can use the guide here, which will install the appropriate google services needed. You can then use this guide to manually 'uninstall' system/Amazon applications (you aren't really uninstalling them, just disabling them). Or use the automatic tool here, which will uninstall a significant number of the Amazon 'bloatware' and install the Google services and a few other Google related apps.

I CANNOT STRESS THIS NOTE ENOUGH: Whether you uninstall apps manually or automatically, please be aware you have to replace the Amazon apps BEFORE you uninstall them. For example, if you want to use contacts, you should install the necessary Google Contact APKs, open 'Contacts' then uninstall Amazon contacts. DO NOT UNINSTALL the Amazon Contact Storage APK or no contact applications will function properly, if at all. There is a guide here where you can install Google Contacts and get a fun little surprise as a result of doing so.

A factory reset will bring back all system apps you uninstall whether you uninstall them manually or automatically. So if anything stops working or you uninstall something that broke something else, factory resetting will fix the tablet, but you'll have to start over.

If you want to use a custom launcher like Nova Launcher, you can read this post which will describe how to do so. In this post I explain how to disable Fire Launcher without breaking the home button. Please read the WHOLE post, including the very bottom where there's a link that describes a 'fix' for the recent apps button (square button) which has a fit when you uninstall Fire Launcher (even on rooted devices). Just tap on 'hide Fire Launcher BEFORE' at the bottom which will take you to a page where you can activate widgets. Read the very bottom and it will tell you how to 'fix' the recent apps button. When you swipe closed apps using the recent apps button, swiping the last one will kick you to the lock screen or black you out for a moment. The fix is kinda cheesy, but it is a fix. I use it on my HD 8.

In this post I describe what Amazon apps I did NOT uninstall. Note this list of apps will differ slightly from the ones installed on the HD 7, but not by very much. This list MIGHT allow you to use Gmail (which doesn't work on any tablet model) and a few other apps.

Very soon, I plan to make a thread with a detailed tutorial on how to do all of this, so it's in one single spot for everyone to find.
[Fire Q&A, Help & Troubleshooting] DB126:
For awareness/clarity: root and SuperSU (no other root manager) are the only prerequisites for installing a custom ROM on this device via FlashFire. The bootloader does not need to be unlocked.
[Fire Q&A, Help & Troubleshooting] ebod:
Thanks Davey, yeah I'm not ultimately looking for a rooted device, I just want a clean Nexus'like rom with no bloated crap on it. As a plan-B I will follow the other guide notes that DragonFire kindly provided. But primarily if you are still staying I can get Flashfire to install a custom Nexus rom, then please can you guide me to the appropriate instructions to make Flashfire come to life.

I have Flashfire installed...but it just warns there are no permissions etc.

Thanks
[Fire Q&A, Help & Troubleshooting] DB126:
A custom ROM (ie: Nexus) can not be installed on this device without root. I do not foresee that happening anytime soon with the so you're stuck with FireOS for a bit. It's not a bad skin once you get used to it.

[MENTION=8165603]DragonFire1024[/MENTION] provided a nice summary of the available tweaks and associated caveats. I suggest going slow; start with the Google Play Store and some light visual customizations. Save the all-or-nothing 'debloat script' until have have a better idea of what to keep.

Most importantly, enjoy your new device and don't fret over what could have been. :)
[Fire Q&A, Help & Troubleshooting] Jake1702_:
Ummm... Gmail works fine on my Fire.

I did not know that. If that's the case, as soon as root is obtainable I'm installing the Fire Nexus ROM.
[Fire Q&A, Help & Troubleshooting] DragonFire1024:
You're lucky then. Many users have had issues with Gmail either force closing or not working at all. Hope the rest was somewhat helpful.

---------- Post added at 05:48 PM ---------- Previous post was at 05:47 PM ----------

*IF* it becomes available. I've had my tablets almost a year, maybe a months or so under one. That's how long I've been waiting. Some have been waiting longer.
[Fire Q&A, Help & Troubleshooting] DB126:
Initially and for many months after the Gmail app worked fine on 5th-7th gen devices with Google Play Services/Store installed. The app started crashing on launch following a silent update (lasted about 2 months) then started working again a few weeks ago.
[Fire Q&A, Help & Troubleshooting] DB126:
Don't get your hopes up. There's a reason securing root on Amazon and other manufacturer devices has become more difficult over the past 12-18 months. While I appreciate the euphemistic optimism shown by some the tightened security and legacy code cleanup initiated by Google is actually a good thing for the general Android user community. Of course, XDAers hate it (spare me the sermon on someone controlling *your* device) but they don't represent the much larger community that Amazon and other market driven companies are targeting. Business/capatolism 101.
[Fire Q&A, Help & Troubleshooting] Jake1702_:
Might just have been the perfect period of time during when I had mine sitting and not being used. Guess I'm just lucky.

It is definitely possible, just not enough people spending time on this device, they are all focused on more popular brands/devices.
[Fire Q&A, Help & Troubleshooting] DragonFire1024:
This I will actually agree with. But to be honest, I really thought we'd have a good chance after Prime Day. I really thought we'd have gotten it then, but I still have hopes.

That being said, the tricks and hacks we've discovered over the last few months are pretty amazing. The method of 'uninstalling' I mentioned a few posts ago, was never intended nor expected to work on these tablets. It had sat on XDA for a couple days before I literally said out loud: "oh what the hell. I can't break anything." So gave it a shot and was incredibly surprised to see it really did disable Amazon Video.

With the tricks and hacks I also mentioned a few posts back, really does go a long way in terms of a custom ROM. Aside from the technical aspects and apps, in my opinion it's pretty much a custom systemless ROM. Though some may disagree with me very much.

Feel free to ask any question you like. We'll do our best to help.
[Fire Q&A, Help & Troubleshooting] Jake1702_:
Funny how for months now this device still hasn't been rooted, yet a few days after the release of the Samsung Galaxy S8, it was already rooted. Simply, those devices have much more people willing to take time to find exploits for, whereas the Fire does not. It's a shame really.
[Fire Q&A, Help & Troubleshooting] DragonFire1024:
There just may not be any at the moment. Amazon has done a lot to this OS, so much so, I've seen posts where users don't even consider it an Android base anymore. Depending on what you read, I've seen other sites where some say its too butchered.

Also keep in mind when an exploit is found, some have been around for a very long time. So one may exist, but no one has either found it yet so no method exists or as you say, may not care enough to take the time to make a method. Every Android device is different. The OS is customized and programed to a manufacturers liking who also add their own customization, then is passed off to a service provider who further customizes it. In that period exploits are patched or simply don't work because what's exploited in certain devices, may not exist in other devices. The list and possibilities really could go on.
[Fire Q&A, Help & Troubleshooting] Jake1702_:
I wonder if it would be possible "break" the bootloader, so-to-speak, to a point where it "works" but is flawed, allowing the installation of a custom ROM.
[Fire Q&A, Help & Troubleshooting] DragonFire1024:
Not likely. I have a list of things to try on my head. Some simple, some outrageous. Truth is this HD 8 has been through hell. I've reset it more times than I can count. I've nearly disected it and to be honest I'm absolutely amazed I haven't broken it yet. So I'm giving her a break from that right now.

With that said, I have an HD 7 that's rooted. I have an idea to try some things using it, that could work on non rooted 7 and up tablets, that would be totally systemless that could open up the possibilities to some things. I've been disecting the HD 7 for some ideas and plan to do some testing very soon. I'm the type that will immediately look at all settings and functions and then look through every file, folder and directory I'm able to, so we can do what many of us have already achieved. Keep an eye on me :P
[Fire Q&A, Help & Troubleshooting] Jake1702_:
If someone were to go so deep to a point where they took it apart, maybe it would be possible to modify the bootloader by setting up a custom one.
[Networking] hybiepoo:
I'm sure this has been asked before, but doing a search brought up a lot of irrelevant threads.

I'm looking for some software I can install on my Desktop PC that will allow me to send an SMS through my Windows Mobile via the USB connection.

Is there anything available?