S8+ Verizon
Android 7.0
G955USQU1AQGL
4.4.16
Looking into what my options are for roms, as I can't call iPhones until I update my phone but I'm not really interested in getting an update that might make my phone unable to be worked with in the future.
I also need to know if Safestrap can read my 64gb storage & I'm curious about any known bugs in the roms / downsides etc that I'm missing
So far I'm aware of the:
-Oreo non rooted xposed (safetynet fails with xposed activated, "DO NOT USE ENCRYPTION"?)
(And I read Oreo cannot be rooted yet? Any ideas on the permanence of this issue/if installing now would make me unable to root in the future for any reason?)
-Rooted Nougat BRB1 (80% battery bug, screen tint issues, loss of a few apps that I'm not sure I need?)
-FIRM Unbranded 3(network settings must be changed with another app, missed call notifications don't show with the default phone app) Would this also have the bugs from the other nougat ROM?
I'm also curious about what I can do with the phone/ROMs personally. Is further development feasible/Needed?
EDIT: Interested in my downgrade/ revert to stock options on each as well. I'd like to be able to go back if i make any mistakes, although. Although I probably wouldn't mind being stuck on oreo with safestrap?
Sounds like you're aware of jrkruse's ROM? It doesn't have root, yet, as the bootloader is literally locked down by Verizon, but SafetyNet apps work fine with it, some say even with Xposed. I use a 128 GB card and safestrap reads it just fine. Only downside is no root, as far as I'm concerned.
Related
So I downloaded the new Android Pay app last night, but it doesn't seem to work if you have a custom ROM installed. I'm currently on Resurrection and it gives me the error "Google is unable to verify that your device or the software running on it is Android compatible".
This needs to change.
UPDATE - I found a workaround that *may* help out. Go into SuperSU and disable root (or disable however you want), try adding your cards again, and then go re-enable root. This has worked for many people on other phones with this error, but it didn't help on my T-Mobile S4
Let me know if you get it to work on another ROM (or even if it works at all on stock right now)
Dowload - http://www.mediafire.com/download/1bvbsouwtcz9mx2/Android_Pay_1.0.102576552_930000657.apk
deke997 said:
So I downloaded the new Android Pay app last night, but it doesn't seem to work if you have a custom ROM installed. I'm currently on Resurrection and it gives me the error "Google is unable to verify that your device or the software running on it is Android compatible".
This needs to change.
UPDATE - I found a workaround that *may* help out. Go into SuperSU and disable root (or disable however you want), try adding your cards again, and then go re-enable root. This has worked for many people on other phones with this error, but it didn't help on my T-Mobile S4
Let me know if you get it to work on another ROM (or even if it works at all on stock right now)
Dowload - http://www.mediafire.com/download/1bvbsouwtcz9mx2/Android_Pay_1.0.102576552_930000657.apk
Click to expand...
Click to collapse
Disabling SuperSU worked for me. It allowed Android Pay to verify my phone.
Not sure I like that I HAVE to have a Lock Screen setup. And, why can't Android Pay have a lock screen built into it like the new Google Wallet does. Wouldn't we want two part authentication?
Rob
I just installed Danvdh's new 5.1 GPE rom and I'm pretty sure Android Pay was already installed. Haven't tested it yet, though. Looking forward to seeing if Xposed will work alright to keep root enabled while using Pay.
HampTheToker said:
I just installed Danvdh's new 5.1 GPE rom and I'm pretty sure Android Pay was already installed. Haven't tested it yet, though. Looking forward to seeing if Xposed will work alright to keep root enabled while using Pay.
Click to expand...
Click to collapse
I re-enabled SuperSU after the install, and it seems to be working. However, it looks like updating also checks root. So, I had to disable root again to have the update to Android Pay take. But, re-enabled root after the update, and things seem to be working.
Rob
You all that state you have it working on T-MO SGH-M919, must be running the T-MO 4.4.4 software. I had it working too - even on a ROOTED 4.4.4. device. Once I install a CyanogenMod Custom LOLLIPOP ROM - and re-installed the AndroidPay, it no longer works. You get the message that ANDROID CANNOT BE VERIFIED (or some crap like that).
Phone works perfect for everything but that...and of course my GoogleWallet was upgraded and no longer has the TAP TO PAY feature...and you cannot get that one back either.
So I guess I need to find out how to get my phone back to STOCK T-MO 4.4.4, none of the downloads anywhere can actually be downloaded any more (unless anyone has a valid link one of those).
Thanks,
*BH*
I'll give you fair warning, as I participated in the lengthy discussion thread over at the Nexus 5 forum (the thread that had the Google developer participating). Here's the lowdown.
Due to liability pressure from Visa, MasterCard, and the others, Android Pay is very...uptight about its operating environment. It basically won't accept any environment it can't trust, and that basically boils down to a system that is stock and unaltered. Anything that can undermine Android's security model (root, custom ROMS, Xposed Framework, etc.) is red-flagged and the app will break. Now, before anyone begins moaning about how Google Wallet worked before, that will be going away soon under pressure from MasterCard. The new system is tokenized and closer to Chip transactions, which is where everyone will be going over the next few months, and under these new rules, if Google can't show due diligence in trying to maintain a chain of trust throughout the transaction (IOW, try their best to ensure a clean environment with no exploitable features), Google faces the bill for instances of fraud. Any attempt to address this problem simply cannot be done the way Android is setup now. Since anything with root access can do anything to the OS, there's just no way to corral this, not even with Marshmallow. Anyone who has used Samsung Pay will notice they take precautions, too. They're a little more lenient with root because they can protect the chain with Knox. Trip Knox and Samsung Pay balks.
Odds are, this development may make phone manufacturers turn back to things like Secure Elements (or some other system outside Android's scope) to provide a way to ensure a chain of trust even with root present. That's likely why Apple isn't too concerned with Apple Pay working with jailbroken phones (all Apple Pay-ready iPhones carry Secure Elements). Until further development, that's just the way it is with Android Pay.
I've always rooted my nexus phones and installed the bevy of apps out there but with my 5X I'm going to go no root for a while and see if I can survive... I need app replacements for a few apps, any suggestions would be welcomed
- viper4android
- volume booster that would come in effect if flashed a kernel
- colour control
Thxs
Sorry I can't help you but I am in the same boat. I want to wait until developers get root with encryption nailed down, there seems to be a bunch of steps and no one is quite sure how root should be handled with 6.0
Never used colour control but I will miss the volume booster. I keep seeing comments about viper4android, time to check it out.
drose6102 said:
Sorry I can't help you but I am in the same boat. I want to wait until developers get root with encryption nailed down, there seems to be a bunch of steps and no one is quite sure how root should be handled with 6.0
Never used colour control but I will miss the volume booster. I keep seeing comments about viper4android, time to check it out.
Click to expand...
Click to collapse
Fair enough. I'm in the same boat waiting for certain the process for root and encryption, guess I'll sit tight and just work with what I have. As for viper4android, probably my #1 app, love the sound quality that produces.
I'm trying rootless too. I mainly rooted in the recent past (Sam Gal S4) to use TiBu to freeze all the VZW/Sam crap. Since thats not there now, I think I'm good.
I am also going rootless for now, not sure if I should unlock bootloader or wait..
Will be rooting here soon. Missing the root life from my S4 and the likes of Viper4Android.
I honestly think there's no reason to NOT root at this point. It's SO EASY to return back to stock using factory images, I been rooted with twrp for a week and the phone has been working GREAT fast and smooth. Only problem is for some reason wells fargo app isn't compatible with marshmallow
What could go wrong? all you have to do is flash chainfires modded boot image and viola, easy as pie.
If you wish to root, go right ahead! The procedure is simple and documented clearly in Heisenberg's [GUIDE] Unlock/Root/Flash for Nexus 5X
The same guide also explains how to return to stock (by flashing a factory image).
It's all explained in the guide. It is worth noting that the root process requires one to flash a modified boot.img, which is currently available only for the MDB08I build. So you can only root if you're on that build or can upgrade to it...
Hopefully a 'cleaner' root procedure (with encryption support for those that wish to have it) will emerge, but there are no guarantees.
Also see: A Look at Marshmallow Root & Verity Complications
one reason I haven't rooted yet is the little updates that always come quick after a new release. They will come, and spending an hour fastbooting is just getting old for me. I think I've turned into an old man, I'm just too lazy to wipe/flash/ download set up all over again. Things have come a long way since the N1.
Absolutely though, when exposed and gravity box are good for 6.0 I'm in.
I'm trying to get Xposed on my shiny new(ish) V500.
I've tried installing Xposed on both CM12.1 as well as the pure build of AOSP Android 6.0, and keep getting a message that "xposed is not compatible with android SDK version 23 on your processor architecture..." (see screenshot for exact error).
Is Xposed not compatible with the device?
Am I missing something?
edit: terribly sorry, I was trying to install using an old apk file. Nevermind...
I'm far from an expert in Xposed as I've never felt the need to use it, however I did read about it when people were raving about it to see what it was all about.
As I understand it it is good for modifying stock firmware to tweak things to your liking, stock being what your device comes from the manufacturer with. We all know stock firmware doesn't have enough options so if you can't stand it you end up here on XDA.
Once here you have options, too many some might say.
Option 1
Go for a completely custom firmware. This will leave you with zero bloatware and a pretty clean state to start with, most of the custom firmwares - other than straight AOSP - come with more options to adjust them than most people know are there*.
This way isn't without it's drawbacks though, there may be bugs and some extra stuff from the stock firmware might not work. Infra-red and FM radios being the two which spring to mind, but even then sometimes they work too.
Option 2
Just get root access and modify the stock firmware with bonus tools made available as you've gained root access. This is things like custom recoveries letting you do full backups, the ability to backup app data through TB or something similar.
Then there is the thing you mentioned, Xposed.
This will let you do a lot of the stuff which a custom firmware would allow you to do all while keeping the stock firmware and the fancy additions your devices manufacturer might have added.
Option 3
Is a combination of the above.
The trouble with this option is that you're trying to do the same thing two different ways at the same time. You may have noticed that in many of the custom firmware threads the guys compiling them say not to report bugs if you're using Xposed, or straight up tell you not to use it.
This is because it will cause problems, not always and generally not with the well made modules, but problems arise and the people spending their free time to make custom firmware available don't want to waste their time trouble shooting a bug which was user created.
So you've chosen option 3 @dude101.
To make it do what you want you'll need to do lots of research, find the version which will work with what you want to use and then trouble shoot any problems you have.
Earlier you might have noticed the * in there. I did that as there are normally options to do what people want to do with Xposed but they haven't looked far/hard enough. If there isn't an option asking in the custom firmware thread about "how to achieve this effect" might lead to a solution. Be it someone pointing you at the option you've missed, or the person compiling the firmware to include it in the next build.
That version of xposed is for Kitkat.
So after doing a lot of reading, I learned a few things.
1) Titanium back up and root doesn't seem to work (at least on Oreo) and installed Magisk
2) You really can't debloat device, without jumping through all kinds of hoops.
Question has anyone one with Sprint successfully installed any of the many roms? and which have you installed? with no issues ie: still have service etc... I want more than anything a rom that works, and is debloated of all the OEM junk, and be able to install mods of my own. Thanks.
doubledragon5 said:
So after doing a lot of reading, I learned a few things.
1) Titanium back up and root doesn't seem to work (at least on Oreo) and installed Magisk
2) You really can't debloat device, without jumping through all kinds of hoops.
Question has anyone one with Sprint successfully installed any of the many roms? and which have you installed? with no issues ie: still have service etc... I want more than anything a rom that works, and is debloated of all the OEM junk, and be able to install mods of my own. Thanks.
Click to expand...
Click to collapse
I have been off of stock since Feb and haven't looked back. Almost everything works. Only service that isn't working is volte and WiFi calling.
Uzephi said:
I have been off of stock since Feb and haven't looked back. Almost everything works. Only service that isn't working is volte and WiFi calling.
Click to expand...
Click to collapse
I don't mind stock so much I managed to get rid of a lot of the bloatware figured that out from another thread.I got a custom kernel in here only thing I can't seem to do is get Xposed installed.
Hello,
Yesterday, I successfully rooted my Samsung Galaxy S10+. But since I still had some questions about it, I went on and posted a thread here. User Spaceminer then pointed out that my original post was in the wrong subforum and linked me here. Naturally, I looked at some of the most popular posts in hopes to find answers to my questions. But what I found confused me more than it gave me answers.
Since 2014 with the Samsung Galaxy S5 I got used to rooting in order to disable bloatware, protect my data and customize my phone. I continued doing that with the S8+ until I recently got my hands on the S10. Now, my main reason for rooting are still the same; I want disable (not necessarily uninstall) bloatware, protect my privacy and customize my phone (such as changing the background of the dial when calling someone). But that thread made me wonder if it is even essential to root. I also found a similar post on reddit and most answers seem to agree that it is not necessary to root your phones.
Now, my situation is a bit different. For one, I already rooted my phone. Second, I don't care about warranty nor custom ROMs. But I do want to install a banking app. Also, it is a bit cumbersome to not only have to manually update your phone with every update but the booting requirements with the warning screen are also a bit annoying. So, my question is the following:
What are the advantages of rooting that are not possible without? I have 3 main concerns: Bloatware, Privacy and Customization.
The reason why I posted this in a separate threat is that I was not able to come to a definitive conclusion on my own and most discussion threads are over a year old. By now, the whole process of rooting and what is possible changed since then, so I want to get a more recent insight. I hope you can help me out.
With kind regards,
DasMalzbier
Tbh root is not needed, unless you want to use a custom rom. Most things are already in the android now.
Calyx os not make for samsung Galaxy series and 12 update also comes this year so i think rooting is unnecessary for s10 series
Root is 100%, absolutely necessary for using the phone. I cannot use any phone without it. Critical root-only capabilities:
full system backups (in twrp)
titanium backup
disable updates permanently (update ONLY when want to)
app freezers (app quarantine)
disable/remove bloatware
disable google play services/google play
automate/tasker
cf lumen
adblockers
wifi tether
busybox
superuser
ssh tunnel
update android to later version / install custom roms
optimize system
button mapper
custom theming / substratum
nav gestures
tidypanel
xposed
root explorer
app privacy customizations
3c all-in-one toolbox
more
Without root, the phone is unusable to me. I will never buy any phone without root capability. I am willing to go to different carriers just to get root on the device, or go to different manufacturers if root is blocked. For example, I will never buy a huawei device - they are locked.
I would like to say yes but I can't. the stock apps are very well designed.
The biggest concern is that custom Roms are released faster than modded apps.
For example I tried about ten GCAMs and all of them have a bug... and it becomes more complicated with Exynos.
OpenGcam is not worth samsung app.
Unable to get voice match to work.
Alarms that you can't set to a specific day with the google app.
And so on.
Root is useful when the manufacturer no longer updates the devices.
I regret having Root mine because I lost Samsung Pay and other things.
DemotionFR said:
I would like to say yes but I can't. the stock apps are very well designed.
The biggest concern is that custom Roms are released faster than modded apps.
For example I tried about ten GCAMs and all of them have a bug... and it becomes more complicated with Exynos.
OpenGcam is not worth samsung app.
Unable to get voice match to work.
Alarms that you can't set to a specific day with the google app.
And so on.
Root is useful when the manufacturer no longer updates the devices.
I regret having Root mine because I lost Samsung Pay and other things.
Click to expand...
Click to collapse
The only one that would have any consequence of rooting is Samsung Pay.
xbt- said:
Root is 100%, absolutely necessary for using the phone. I cannot use any phone without it. Critical root-only capabilities:
full system backups (in twrp)
titanium backup
disable updates permanently (update ONLY when want to)
app freezers (app quarantine)
disable/remove bloatware
disable google play services/google play
automate/tasker
cf lumen
adblockers
wifi tether
busybox
superuser
ssh tunnel
update android to later version / install custom roms
optimize system
button mapper
custom theming / substratum
nav gestures
tidypanel
xposed
root explorer
app privacy customizations
3c all-in-one toolbox
more
Without root, the phone is unusable to me. I will never buy any phone without root capability. I am willing to go to different carriers just to get root on the device, or go to different manufacturers if root is blocked. For example, I will never buy a huawei device - they are locked.
Click to expand...
Click to collapse
can you carrier /network unlock with the root >?
NickosD said:
Tbh root is not needed, unless you want to use a custom rom. Most things are already in the android now.
Click to expand...
Click to collapse
No, even if you wanna use custom rom you don't need to root. Just pick the rom with the apps you want or just use the gapps packages you want, if want essential to work gapps then use pico or nano. If there is still something you want to remove and the romdoesn't allow, just use adb shell commands and thats it. Less issues with banks not working because of Magisk (root). I know Magisk has a feature to hide itself, change its name but depending on the app, the libs can be found and know that is Magisk, so for security purposes some apps don't work and some aren't even shown in the Google Play Store just because you rooted the device.
logandavid said:
maybe now the root is not needed but later down the road when your phone will get obsolete and newer android OS updates will be halted for S10+ then you'll be more attracted towards custom roms. Actually it is just personal preference.
Click to expand...
Click to collapse
It's happening right now, I doubt S10+ will receive Android 13 and now just security and bug fix updates are being shipped by Samsung.
Haknor said:
It's happening right now, I doubt S10+ will receive Android 13 and now just security and bug fix updates are being shipped by Samsung.
Click to expand...
Click to collapse
It won't get any new Android upgrades AFAIK.
But appart from tripping knox, what else do I lose if I unlock my bootloader? I read once, quite a while ago, that the battery is limited to 80% of its full capacity. Is that true?
io_gh0st said:
It won't get any new Android upgrades AFAIK.
But appart from tripping knox, what else do I lose if I unlock my bootloader? I read once, quite a while ago, that the battery is limited to 80% of its full capacity. Is that true?
Click to expand...
Click to collapse
Depending on the version, you'll notice stock camera to be limited or not work as expected, secure folder, dual messenger either not working, it can trigger some banks or payment apps (especially if you root), no more ota updates (if you keep using stock rom), drm content can stop working, samsung pay, Play Store might limited the apps you see and so on... Not sure about the battery, for me unlocking the bootloader and switching to another rom made my battery last more than stock, but it depends on the rom, the device, it's not a rule of thumb.