Develop Bugs

[Q] Rooted my 51.1.1.0

Successfully rooted my FT 51.1.1.0 but following the guides, indicate I should downgrade to 51.1.0.2.
I tried twice unsuccessfully.
Question: Do I really need to downgrade? I never watch hulu or net flix, EVER.
tia

I do notice a slow response to the remote after a few clicks. Not sure what caused this, and what could fix it since it freezes for a minute or two.

Downgrade?
How did you downgraded it?

What guides? Once rooting is successful, I'm not sure why you would want to downgrade. I'd think that the next step is to install the custom recovery and install the pre-rooted version of the most current firmware. At least that's what I've always done.

AFTV v54.*.* doesn't allow to root the device....Can I downgrade the firmware to version v51.*.*.*????

kosackks said:
AFTV v54.*.* doesn't allow to root the device....Can I downgrade the firmware to version v51.*.*.*????
Click to expand...
Click to collapse
Unfortunately if you can't root you you can't downgrade. You need custom recovery for that. You should go over to aftvnews and check out the guides.
Personally, if it were me I'd go to aftvnews and I think they keep a running list of serial numbers. If youre in the US, return the aftv to staples or bestbuy and check the serials. In recent trips to bestbuy I've found lots of bare shelves for both the box and the sticks but I wish you luck!
If root is that important to you, they can still be had on ebay prerooted for a higher price but last time I looked I was surprised to see they were still considerably cheaper than the atv 2 that just stopped receiving development.

Thanks for your Answer KLit75.
I'm sorry to be "newbie", but I'm curious without knowledge, my question is: Can I flash the AFTV Stick (any version) with OpenELEC?

Ironically I had the exact same situation as this. I figured it out yesterday.
I would provide links and all, but I am not able to do that currently.
So for now, these are the steps I had to take in a basic list.
I will start out by saying I had the earliest software made. I don't remember all of the specific numbers. I was attempting to upgrade to the latest pre rooted rom.
I had to "downgrade" to the version above mine (51.1......0.2 or something)
I had to flash CWM
Fully unlock boot loader
Install 51.1....4.... Something prerooted software
Install boot menu (Required in the versions newer than the 51.1.4....)
THEN upgrade to the latest pre rooted rom.
I saw barely any help online for this, seeing as most people do not have to use that extra step of updating the software a bit to even use CWM.
do not use the CWM recovery with the 51.1.0 software. It will brick it.
The reason I had to go from the version before the latest, was because you can't go from that early version to the latest. You also need to install the boot menu if upgrading to a recent one.
It took several hours to do. With transferring files and many more things. This is without any error. So you can just imagine if you get stuck on one part. It's back to root one.
It takes a lot of patience and courage! I was afraid of losing root for many hours.... Not that fun. But it was kind of worth it. The mouse cursor is broken for me. So that is unfortunate with the new update.
I am using a firetv box that was rootable from the start to be clear.
GOOD LUCK!! It IS NOT worth it if you have not went through hours of debugging with android before. Trust me.

AFTV Stick With OpenELEC
I'll give a try to this, may be on weekend. Anyway thank you for your tips, I'm thinking the same way you've explained before.
Same thing, It's not that I can spend AFTV Stick's doing this , but I believe It should be much better with OpenELEC on it.
Best Regards to you all.

Android Pay

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.

HTC 10 Android Pay Doesn't Work after OTA Update, "Not Compatible"

I have an unlocked HTC 10. I recently received an OTA update.
I have been using android pay just fine with no issues. However after the most recent Android Pay update. I was getting an error message explaining I may need to "unroot" my device..
My device has NEVER been rooted and android pay has worked great!!!
As an extra precaution, I did a factory reset to my phone, and re-downloaded android pay.
Now I get a new error, but very similar. When I try to add a card after installing, now it says
"Android Pay can't be used
Google is unable to verify that your device or the software running on it is Android compatible".
After already factory resetting and uninstalling/reinstalling the app... I'm not sure what to do... I don't want to root or flash... but I am looking for options....
thanks

I read somewhere that flashing elemental X as the kernel will fix this, but I'm waiting for more people to confirm. I'm also guessing flashing a new kernel doesnt requiring wiping or anything? and lastly, how can i backup my existing kernel to reflash in case **** goes haywire? anyway, hope that helps.

Also using S-OFF and LOCKED bootloader will work.

tabp0le said:
Also using S-OFF and LOCKED bootloader will work.
Click to expand...
Click to collapse
RELOCKED bootloader status won't let android pay work?

GottaStayFly said:
RELOCKED bootloader status won't let android pay work?
Click to expand...
Click to collapse
I"m not sure about that.

SafetyNet is looking for the flag that the unlocked bootloader throws, someone more familiar with recent flags than me should know which way the flag is set upon relocking bootloader.
The ElementalX kernel has the option, but I believe that's another option for s-off users, I'm not sure if it will work for s-on unlocked users.
I think if it doesn't pick up "relocked" when it checks SafetyNet, it wont be long until it does. This is a cat and mouse game, and google has the right to "take its ball and go home" with root users, I just wish they wouldn't use that against us enthusiast users, who are their best advocates since we carry so much weight on advising all the non tech oriented unrooted consumers when it's time for them to purchase new smartphones. We are the ones that the rest of consumers call for advice or when something is broken.

Will taking this update break root or cause other issues? Just received the notice a few hours ago.
Current setup:
S-on
Unlocked
Rooted
Stock ROM still (obviously)
SW v1.80.651.1
Sprint
I waited for the N7, and returned it without opening it before the fiasco. Because I was going to wait for the Pixel, which ended up being astronomical in price. So I waited for the V20, only to find it has a "Verizoned" bootloader. And just this past weekend I settled on the HTC 10.
If anybody can provide me helpful information, I would appreciate the consideration.
ETA: NM - simply made a copy on sd card, then renamed with .bak in update folder and nag went away. Seemed to be a small incremental update from .1 to .6.

So it sounds like the lesson here is if you haven't unlocked your bootloader yet, don't, if you want to use Android Pay. From what I've read, using Sunshine to go S-off LOCKED will allow android pay to work, as long as you aren't rooted. Also there are a couple kernels you can use to disable to check for unlocked bootloader.
Is this all correct?
Sent from my HTC One_M8 using Tapatalk

why NOT root?

given all of the cool options that open up with root, im wondering why NOT do it??
i mean other than no Android Pay, and having to manually flash rather than ota on phone, is there any real downside?

byproxy said:
given all of the cool options that open up with root, im wondering why NOT do it??
i mean other than no Android Pay, and having to manually flash rather than ota on phone, is there any real downside?
Click to expand...
Click to collapse
You can use Android Pay with Magisk I believe. Magisk passes saftey net checks.

byproxy said:
given all of the cool options that open up with root, im wondering why NOT do it??
i mean other than no Android Pay, and having to manually flash rather than ota on phone, is there any real downside?
Click to expand...
Click to collapse
Those downsides are enough for some, but the biggest PITA is if you didn't unlock your bootloader then you have to factory wipe when you unlock.

Tb0n3 said:
Those downsides are enough for some, but the biggest PITA is if you didn't unlock your bootloader then you have to factory wipe when you unlock.
Click to expand...
Click to collapse
well google backsup your app, mms, sms etc and the way you have your phone set up. Easy to restore and takes 30 mins depending on your connection.... I say go for it!

byproxy said:
given all of the cool options that open up with root, im wondering why NOT do it??
i mean other than no Android Pay, and having to manually flash rather than ota on phone, is there any real downside?
Click to expand...
Click to collapse
for some it is android pay
but for others
they don't need it anymore
stock rom nowadays give us most of the options that we needed to root for back in the day
i used the pixel 2 without root for 1 week (before it came out )
and the only thing i need it for was adaway and custom kernels
i used non-root adblocker and it's actually worked fine
so if i am stuck with a phone with no root i can live with it

I always root, but the big downsides are around OTAs and needing to jump through hoops from time to time to update.
Finally it's a security issue, particularly a unlocked bootloader, it's super easy to erase pin or pattern locks from twrp. Also malware in a root app could be devastating to any info you access via phone.

byproxy said:
given all of the cool options that open up with root, im wondering why NOT do it??
i mean other than no Android Pay, and having to manually flash rather than ota on phone, is there any real downside?
Click to expand...
Click to collapse
Because some security flaws that come along and some malicious apps expose the fact that you have root to be more effective.

If a good and stable rom like Pure Nexus that passes safety net works flawlessly on the Pixel XL 2 then that would probably be enough for me not to root. That would provide enough features and excitement to the already great experience that stock android now provides. Right now, i enjoy root in order to apply adaway and delete system apps if i so choose. Also nice to be able to use different color profiles. I am one of those that loves to be able to use Android Pay while rooted.

elreydenj said:
If a good and stable rom like Pure Nexus that passes safety net works flawlessly on the Pixel XL 2 then that would probably be enough for me not to root. That would provide enough features and excitement to the already great experience that stock android now provides. Right now, i enjoy root in order to apply adaway and delete system apps if i so choose. Also nice to be able to use different color profiles. I am one of those that loves to be able to use Android Pay while rooted.
Click to expand...
Click to collapse
I'm just here praying they're working on Resurrection Remix.
I was on PureNexus and decided what the hell and tried RR and it has everything PureNexus has and more.

DevanteWeary said:
I'm just here praying they're working on Resurrection Remix.
I was on PureNexus and decided what the hell and tried RR and it has everything PureNexus has and more.
Click to expand...
Click to collapse
Ill keep that in mind. Did RR pass safety net out of the box on the pixel XL?

elreydenj said:
Ill keep that in mind. Did RR pass safety net out of the box on the pixel XL?
Click to expand...
Click to collapse
I don't remember. Sorry. :/

I used to be an avid rooter and custom rom user. For me, I'm contempt with the stock factory images. May give PureNexus a shot if it comes around.
Besides, I had an incident with Chase Bank once where I was having trouble getting text alerts. After an hour on the phone with support, they noticed and mentioned I had a "tampered" device. Not that my problem had anything to do with my device being tampered with (rooted), and not that I had any modifications which could cause harm to my banking information, but in the long shot case something did ever happen with your money, I'm sure the banks would have no problem pointing their fingers at your phone.
So if a company like Chase scans to see if your device is rooted, I'm sure most app developers do without telling you.
If someone wants to chime in, not exactly sure how apps see it if you have a rom like Resurrection Remix, or PureNexus, and actually dont root it. I wonder if the apps still consider the device tampered with if there is no root access

byproxy said:
given all of the cool options that open up with root, im wondering why NOT do it??
i mean other than no Android Pay, and having to manually flash rather than ota on phone, is there any real downside?
Click to expand...
Click to collapse
You can MOST definitely have Android pay with Root in Pixel. That is the beauty of dual partition setup. Have one partition rooted and other non-rooted, with both sharing the same data partition.
I had done this for the past year on the OG Pixel XL. The only time I would need non-root would be for Android pay - I would just boot to the other slot. Use Android pay and then reboot to the previously active slot after finished.
As for Custom ROM - I'm hoping against hope. Hard to imagine life without the features of PN or RR. However, it is not encouraging given that there is no a single OREO based Custom ROM yet for the OG Pixel XL. Who knows how many developers actually end up getting the Pixel 2 XL - which is more expensive. That is the only reason I'm still waiting with bated breath until my return period for Pixel 2 XL expires. Luckily, the One Plus 5t launches on Nov 16th and the reviews would be out soon. I know OP5 has RR custom ROM which is a big deal..

abogrhen said:
for some it is android pay
but for others
they don't need it anymore
stock rom nowadays give us most of the options that we needed to root for back in the day
i used the pixel 2 without root for 1 week (before it came out )
and the only thing i need it for was adaway and custom kernels
i used non-root adblocker and it's actually worked fine
so if i am stuck with a phone with no root i can live with it
Click to expand...
Click to collapse
Yes to all this. I haven't rooted since my Galaxy S5. I was perfectly fine with my Nexus 5X stock and do use Android Pay often enough to want to remain unrooted. I actually used to root and install stock-like ROMs so now that I've been getting Google phones, I have no need.
Sent from my Pixel 2 XL using Tapatalk

doubts about whether to continue using root or unroot and relock the bootloader

I came across this post on GitHub
https://github.com/topjohnwu/Magisk/issues/2534
I wanted to ask if I should continue using root or just relock my phone ?

tanzeel.ahmed1306 said:
I came across this post on GitHub
https://github.com/topjohnwu/Magisk/issues/2534
I wanted to ask if I should continue using root or just relock my phone ?
Click to expand...
Click to collapse
Unlocking your bootloader and rooting your devices is a choice that you and only you can make. There are always risks when modifying your devices. When you unlock the bootloader on most devices it will void your warranty unless stated otherwise by the manufacturer.
When it comes to root access there is always a chance for things to stop working. That is why it is up to you to do your research and make an informed decision before taking any action.
To some people, including me, an unlockable bootloader and gaining root access over a device is a must. I am paying for it and I want to use my devices how I see fit.
If you are concerned about an issue that may arise because you have an unlocked bootloader and root access I always try to look at it from both sides. Why did I unlock the bootloader? Why did I root? Am I able to do what I intended to do or not?
Sent from my OnePlus HD1907 using XDA Labs

tanzeel.ahmed1306 said:
I came across this post on GitHub
https://github.com/topjohnwu/Magisk/issues/2534
I wanted to ask if I should continue using root or just relock my phone ?
Click to expand...
Click to collapse
I'm kinda in the same boat. While I don't use GPay that often (and I can currently use it through Magisk), occasionally it would be nice for it to work without issue. However, the main reason I root is so that I can manually edit my HOSTS file to block ads.
Like fast69mopar mentioned, it's an individual preference. What do you gain by unlocking the bootloader and rooting?
In my opinion, the OP7T is a fantastic phone right from the get-go. So was the OP6T. Both phones I used for almost a full week before unlocking and rooting.

Got the OP7T a month ago and was faced with the same decision. All phones since Samsung Galaxy I have rooted.
Decided not to root the OP7T. So far couldn't be happier. Maybe missed it once. Everything working without issue is nice.
As for Ads.
Built in Private DNS in Android 10 with dns.adguard.com works pretty damn good.

I'm rooted, using magisk and edxposed with aosip. Definitely no loss of function comparing to stock. I don't use Google pay, but Samsung pay, bank apps, snapchat, everything works. Currently magisk and edxposed could be hidden without any loss of function when it comes to bank or paying apps. I don't use Google pay but safety net passes just fine with my setup

fast69mopar said:
Unlocking your bootloader and rooting your devices is a choice that you and only you can make. There are always risks when modifying your devices. When you unlock the bootloader on most devices it will void your warranty unless stated otherwise by the manufacturer.
When it comes to root access there is always a chance for things to stop working. That is why it is up to you to do your research and make an informed decision before taking any action.
To some people, including me, an unlockable bootloader and gaining root access over a device is a must. I am paying for it and I want to use my devices how I see fit.
If you are concerned about an issue that may arise because you have an unlocked bootloader and root access I always try to look at it from both sides. Why did I unlock the bootloader? Why did I root? Am I able to do what I intended to do or not?
Click to expand...
Click to collapse
Thanks a lot for your response
I actually rooted because I wanted to use substratum themes and enable aux module in gcam. Apart from that no other reason.
So I guess I am not missing out on too much .
I actually unrooted my phone and relocked the bootloader.
But again thanks for the response!

I had unlocked the bootloader and tried a couple of custom ROMs a few months back but decided it isn't worth it because my main hindrance of adblocking is addressed using DNS and any unneeded app can be disabled using adb. On the flip side, I need Widevine L1 for Netflix/Prime and no custom ROM can offer that on the 7T.
Makes more sense to me to stay within the walled garden, especially with the higher risk brought about by rogue Android apps that are now far too prevelent. The mods too are not that much value adding than it was may be when I first started using custom ROMs nearly a decade ago.