yashsingh1/xdaforums huggingface dataset:
[Fire General] musiclover7:
So... I just got a fire 7 during the holidays when it was on sale for 39 bucks. I mean, 39 dollars for a semi decently spec'd tablet is hard to beat. Of course, I hate the Amazon environment, and after reading this thread, realizing I am on 5.3.2.1, I also realize I am stuck with it for... Well, that is my question, how long? Is it likely we will get a work around for 5.3.2.1?* Is there a way to downgrade? Trying to determine if I just tossed away 39 bucks or not. Thanks in advance for any info you might provide.
[Fire General] DB126:
You are "stuck" with FireOS until a vulnerability in version 5.3.2.1 is discovered and associated exploit is developed to secure root access. No one publishes a time line on security hacks. Could happen tomorrow or never.

FireOS 5.3.2.1 can not be downgraded. With one unconfirmed exception those who have tried were rewarded with an unrecoverable brick.

Amazon accepts returns on most holiday purchases through Jan 31st. Your $39 is a phone call away.
[Fire General] musiclover7:
I think I will just tuck it somewhere for a while until an exploit is*discovered. Thanks for the info!
[Fire General] Lifeformz:
All of the Black Friday fire 7's I've had, has been running software prior to the latest update. I've just cracked open my "xmas" present and it was 5.0.1. I bought one myself on black friday, which was returned twice due to dead pixels, and the third arrived out of date software. All were older OS. The trick is to not connect to wifi/add an account before rooting it. So the xmas gift one I kept in the dark till I rooted it and stopped the updates. Skip the wifi section when setting up the fire.

Return it if you can, and get a replacement, don't connect to wifi, check the updates section and make sure its older model, then root it. Chances are it updates when you connect to wifi and you don't know it. My one I use as a tablet did it that way. :( having just flashed the xmas one, I wish I could've done it to the other one too.
[Fire General] johnnydollar:
You can, however, still install the Google Play store. That doesn't require root, and got me a lot closer to what I wanted while I wait for a root exploit to be found.
[Fire General] ekinrot:
I have the same problem. Is there any way .... like this ... When amazon devise is hard brick ?

http://www.droidgyan.com/soft-brick-vs-hard-bricked-vs-broken/

or

http://www.engineerthink.com/blog/2016/07/how-to-unbrick-hard-bricked-mediatekmtk-android-phone/ ?
[Fire General] DB126:
Device is toast - seek a replacement from Amazon if still under warranty.
[Fire General] ekinrot:
Thanks for console :D Warranty has expired ... Throw out or wait ? :confused: :(
[Fire General] DB126:
Always possible a recovery method will be developed; odds are long IMHO given the device price point. Refurbs can be had for <$30 USD. There are bigger fish to pursue for those with the time and talent to unravel a borked bootloader. Not many watchmakers around either ...
[Fire General] Marsu42:
fyi I bought my Fire7 during the same time frame but got a 5.1.2 device - so in Germany, they seem to be selling older stock which means ppl here should hurry to get a root'able device while it might still be available.

But I guess even running FireOS with ads, you can install a lot of apps by sideloading, though of course lotsa nice xposed things are not available.
[Fire General] rizal72:
Indeed, same here in Italy: I bought a Fire7 a couple days ago and it arrived with 5.3.1, so I was able to root it ;)

Better hurry then :)
[Fire General] ekinrot:
Hello guys

I have hard brick fire 7 5th generation

If I buy it

http://www.ebay.com/itm/262358522995?ul_noapp=true FireOS version is 5.1.1

Can I update Custom ROM (cyanogenmod or other) and insall playstore ?
[Fire General] DB126:
If the mainboard board arrives with a 5.1.1. bootloader and you are successfully able to install/integrated it into your existing case/battery/panel then you *should* be able to root, install FlashFire and flash a custom ROM. Obviously no guarantees given the number of variables involved.

Also consider a refurb from Amazon Warehouse which typically arrive with older firmware (below 5.3.2.1) and are generally indistinguishable from 'new' aside from the box it arrives in.
[Fire General] ekinrot:
Aha . Thank you very much :)
[Fire General] steve8x8:
Make sure that it's ro.build.version.fireos and not ro.build.version.release that equals 5.1.1 (the "release" one is always 5.1.1, aka Lollipop)
[Fire General] Fred Simm:
For all who are stuck with 5.3.2.1, here's my experience. If you drag 2 amazon icons together, you will create a folder and get a name prompt. Now, drag all of those annoying amazon apps to that folder. Install Google play services . I was able to update my Google app and now I have my Google now feed when I press the Google app icon. No, I can't swipe right, but it's better than no Google now at all. I have made my kindle tolerable untill we get an exploit.
[Fire General] rogrobin:
5.3.2.1

Ive got a 5.3.2.1 version :/

Been searching but as far as I can tell no-one has managed to roll back or root this.
[Fire General] WXSky:
I recently obtained a Fire with 5.1.2 (It was definitely pre 5.3.2.) on it and was able to install ES File Manager, Google Play Store and a few other apps and was planning to root it in the morning. However, when I ran out of night I shut it down and left it plugged in to charge itself. However, I discovered it had updated itself while I slept to 5.3.2.1! It was a bad idea to leave it plugged in and not turn off wifi but is there a way to roll it back? If I factory reset it will it go back to 5.1 or just erase all my downloaded apps and stay at 5.3.2.1? (sorry for the nube questions, it is my first android device)

Edit: Just an FYI Checking "Device information" in Kingroot It says Brand: Amazon, Model KFFOWI, Android 5.1.1

Rooting doesn't seem to be possible in Kingroot so far.
[Fire General] DB126:
Correct (as of date of this post).
[Fire General] DB126:
You will need to wait for a root exploit. Factory reset does not change FireOS version; a manual rollback (from 5.3.2.1) will brick the device.
[Fire General] WXSky:
I just got this. I plugged it into the PC for the first time and it looks like I can see all the files without having to install much drivers. Is it possible for someone just to create an ISO that can be flashed to the device from inside another linux distro (or edit the bootloader)? Just a query - again a nube. If not why not? Why can't I just reformat it as a fresh device and install a distro of my choice on it? My main interest in rooting it was to try out other OSes on it, such as firefox or ubuntu.
[Fire General] DB126:
Doesn't work that way. At present FireOS 5.3.2.1 can not be rooted, rolled back or replaced with another "OS". If/when a root exploit becomes available you are limited to suite of custom ROMs available for this device (all Android 5.1 based). Look into an unlocked device if you want broader privileges and the ability to flash a variety of images. As a general rule Amazon devices are not a friendly platform for general tinkering.
[Fire General] Fred Simm:
I look every day with no luck. After owning a nexus phone, it's hard to deal with fire os. I was able to load nova launcher, but it slowed everything down. Someone said the nook 7 is normal android. I may buy a used one.
[Fire General] Megalev:
Heh, yeah... subscribing to thread :)
[Fire General] steve8x8:
A few days ago, [MENTION=5488402]Davey126[/MENTION] has started a new thread after a report of successfully rooting 5.3.2.1 was submitted:

https://xdaforums.com/amazon-fire/general/5-3-2-1-root-t3547136

My impression of that thread is still somewhat incoherent, and given the randomness in KingRoot's "strategy" it's perhaps no surprise that the initial success couldn't be reproduced recently. So this is something to be taken with at least two grains of salt and/or watch for a while longer... another thread to subscribe to ;)
[Fire General] Blackhawk2306:
How are you supposed to return it? I mean, you cannot simply send it back to amazon and say "hey, I want a new one" without any reasons, right? Because I soft-bricked mine with too many Xposed modules ;) , adb sideloaded fireos 5.3.1 back on it, rooted it, and forgot to block OTA updates (yep, it's embarrassing, I think I shouldn't do such things at 2 am), and over night it updated to 5.3.2.1, I would be thankful to know how to get amazon to replace it for no reason:eek:

They replace hard bricked devices? If so, I could create a reason for them to replace my tablet. Hehe

(God damn it, that hurts so much, it had 5.1.4 when I powered it up the first time. While I got all the informations about rooting and installing CM, that little bastard updated to 5.3.1)
[Fire General] DB126:
That's exactly what you do if the device is still within warranty. Simply say it became non-functional following an update; don't need to get more specific than that. Amazon will happily provide a no-questions-asked exchange provided you don't have a history of abusing this courtesy.
[Fire General] ctodd111:
Custom ROM after root?

Once we have root for 5.3.2.1, will we be able to put a custom rom on it? I have already rooted 3 of these back in the fall and put CM-12 on them (I think - it's been a while). I now have two more but they are running 5.3.2.1. They are still considered 5th generation according to the Device Model setting. I am just wondering if there is any difference in the more recent build dates that would prevent this once root is achieved.

I LOVE my rooted fire 7 with its custom ROM - it is really zippy and the battery life is unbelievable. I use the others in my classroom at school, and I can't wait to get these other two rooted! I also have a new fire 8 running 5.3.2.1 and I wonder if I will be able to install a custom ROM on that once root is achieved, or would I need a custom ROM specifically for that model?
[Fire General] BeeWall:
Yes for the fire 7, the hd8 needs a ROM for that model.
[Fire General] Gewalt:
Is it possible to install russian language on 5.3.2.1?
[Samsung Galaxy J7 Questions & Answers] sanghrsh1234:
I have bad sound problem after updating my J7 2015 to marshmallow I flash the custom rom but it not work please help sorry for my bad english
[Samsung Galaxy J7 Questions & Answers] Adorable.:
It doesn't happen to me, but try hard resetting your device.
[Samsung Galaxy J7 Questions & Answers] sanghrsh1234:
Ok i will try
[Verizon Samsung Galaxy Note5] Sziehr:
Anyone brave enough to try?

http://androiding.how/dirty-cow-root-android/
[Verizon Samsung Galaxy Note5] ratman6161:
Love how these sites don't put a date on their "news" stories.

They say "discovered only a week ago". Actually it was discovered last June. Google released a security update to fix it on Nov 8th.

https://threatpost.com/google-releases-supplemental-patch-for-dirty-cow-vulnerability/121843/

Hopefully Samsung will get a security update to us soon that patches this.
[Verizon Samsung Galaxy Note5] cmdba:
So this is totally worthless? Can attempting this brick your phone?
[Verizon Samsung Galaxy Note5] ratman6161:
Personal opinion: this is a serious flaw. Anyone would have to be crazy or not care about the results.
[Verizon Samsung Galaxy Note5] ratman6161:
Received the November 2016 Security Update today. Fixes Dirty Cow among other things.

http://security.samsungmobile.com/smrupdate.html
[Google Pixel XL Questions & Answers] slickromeo:
I Purchased the Pixel XL Directly from the google store.

It arrived in the mail just a few days ago

it is unrooted

I have not unlocked the bootloader

I am the 1st owner who set it up.

it is totally unaltered except I installed some basic apps like anyone would when they get a new phone.

when I try to add a debit card on the Pixel XL in the Android Pay app, it gives me the error message:

"Android Pay Can't be Used. Google is unable to verify that your device or the software running on it is Android compatible"

This is extremely frustrating, and this is very dissapointing to me, that a brand new Pixel XL, out of the box, after being setup cannot perform such a basic task as adding a debit card, especially since the O.S. is unaltered. and the bootloader has never been tinkered with and it is not rooted.

I called Google customer service but all they can tell me is that the error message is not supposed to come up unless the device is rooted. However my Device is NOT rooted, so what gives? nobody knows anything.

I come here as my last resort..... Will anyone please help me troubleshoot this. I would be most appreciative if anyone could help me troubleshoot this. Please & Thanks.
[Google Pixel XL Questions & Answers] fsuagentsmith:
I didn't have this problem when I was on stock as a Verizon purchased Pixel XL owner.

However,

I am having the same problem since I rooted and unlocked the phone. I am running Verizon Pixel XL, Elements Kernel Version .7, TWRP Alpha 1.

Any help for the OP and myself would be greatly appreciated.
[Google Pixel XL Questions & Answers] death2all110:
Honestly, try a factory reset.

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

It's not going to work for you because SafetyNet sees you have an unlocked bootloader and non stock software.
[Google Pixel XL Questions & Answers] Ajshal:
Did u install all the Updates you got?
[Google Pixel XL Questions & Answers] M9guy:
Edited duh missed bought from google part lol.

I would take screenshots showing bootloader is locked and tell google you have proof. Say if they dont want to fix this issue your going to file a chargeback with your credit card company that will change their tune right there.
[Google Pixel XL Questions & Answers] slickromeo:
I installed the OTA update for the November security updates (see attached image)

So you think the November security update messed it up??
[Google Pixel XL Questions & Answers] slickromeo:
I am seriously considering a factory data reset but I'd like to see if anyone has any other alternatives first that I might try
[Google Pixel XL Questions & Answers] docluv01:
If you temp disable root, does it work then?

Anyone try Magisk, or is that not advisable with the pixel?

Thanks
[Google Pixel XL Questions & Answers] slickromeo:
I spoke to Google Customer service again, i once again repeatedly told them that I have never been rooted, the bootloader had never been tinkered with......... They finally escalated me and asked me to submit a bug report. So i'm following the bug report steps now........ However I am still very frustrated and just want this to work........ If anyone else has any other troubleshooting steps for me, please share with me. I have multiple google accounts on my phone just in case that makes any difference, but I dont think it should make a difference.
[Google Pixel XL Questions & Answers] fsuagentsmith:
I figured that was the cause, looks like a work around will have to be developed.
[Google Pixel XL Questions & Answers] death2all110:
Did you try a factory reset?
[Google Pixel XL Questions & Answers] slickromeo:
I haven't tried a factory reset because I was hoping to resolve the issue without needing to factory reset.... I already submitted the bug report to Google, how long do you think it'll take them to respond with a solution for me? Or do you think a factory reset is worth it just to save the time and the wait....?
[Google Pixel XL Questions & Answers] slickromeo:
I gave up the waiting game and Finally decided to do a Factory Data Reset to see if that would fix it....

It did not work. I get the exact same error message from a fresh factory reset.... the only apps that updated were the ones that always update after a factory reset.... This time i made sure to only add 1 of my google accounts when setting up the device.... After the stock apps all updated themselves, and play services updated itself. I still got the same error message......... on a freshly reset unmodified, unrooted, stock Pixel XL with a bootloader that has never been tinkered with !!!

I am majorly dissapointed !

I'm issuing a $20 Cash REWARD payable through Paypal or Google Wallet to whichever person helps me troubleshoot this to my satisfaction (I'll be satisfied when I get the app to work the way it's supposed to work i.e. I can add a debit card)

Does anyone have any further ideas of things that I should do ?????

or is my only remedy, to sit and wait for Google's Bug report to make the rounds and they get back to me :crying:
[Google Pixel XL Questions & Answers] slickromeo:
I'm continuing to research and I stumbled upon someone else with my issue https://www.reddit.com/r/Nexus6P/comments/41sl7x/android_pay_cannot_be_used_google_is_unable_to/

However, they changed the DPI, and I did not.... so it still doesn't explain why this is happening to me.

I installed one of the apps one of the commentators suggested to check compatibility with SafetyNet

so I installed this one https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en

and when I installed it and run the app, the SafetyNet check app tells me an error (See Screenshot)

Which leads me to another question.......... How in the world is it possible for SafetyNet error for AndroidPay in a fully stock, unaltered, unmodified, unrooted (bootloader never unlocked) Pixel XL ?????
[Google Pixel XL Questions & Answers] DaveHTC200:
Have you booted into the bootloader menu just to check the bootloader isn't unlocked for some reason?
[Google Pixel XL Questions & Answers] slickromeo:
When I shut down my phone

and press and hold PWR+VOLDOWN until it boots up

here is the text I see:

BL: 8996-012001-1608281716

Baseband: 8996-012511-1610221116

Product/Variant: marlin-US-PVT

Serial Number: HT6AE0201507

CPU: MSM8996SG-AB 0X10001

UFS: 128GB Toshiba

DRAM: 4096MB Hynix LPDDR4

Boot-slot: b

Console: DISABLED

Device is LOCKED

so, I assume that were it says "Device is LOCKED" that means the bootloader is locked, am I right?

I clicked Restart Bootloader to see if that would solve anything............
[Google Pixel XL Questions & Answers] DaveHTC200:
That's correct!! OK so it's not the bootloader that's causing it! Do you have a figure in the display settings under the "display size"? Or just small etc
[Google Pixel XL Questions & Answers] slickromeo:
inside android settings, in the Display menu, i find a setting called "Display size" and it is set to 'Default'
[Google Pixel XL Questions & Answers] slickromeo:
I should mention I clicked "Restart Bootloader" previously when you told me to boot directly to the bootloader, just to see if that did anything. and I just wanted to confirm with you that It did not affect anything, I am still getting the same error.
[Google Pixel XL Questions & Answers] DaveHTC200:
That won't make a difference, you can't unlock it direct from the phone.

Have you tried to clear data and force close the android pay app?
[Google Pixel XL Questions & Answers] slickromeo:
Here's all the troubleshooting I did including all the things mentioned previously

Erased cached data from Android Pay app

Forced closed app

Erased all data on Android Pay app

Uninstalled Android Pay

Reinstalled

All to no effect....

Are you familiar with the SafetyNet check app? Do you know why it might be coming back with a fail message if my bootloader is locked and I'm unrooted on stock Android that comes preinstalled on the Pixel?
[Google Pixel XL Questions & Answers] DaveHTC200:
Bloody hell, it's a real pain!!

I'm not fully aware of how the app works, but I know even with my bootloader unlocked and custom kernel it passes the check in that app!

Something somewhere it would appear your system thinks it's modified, but not through your doing!!

One way of possibly trying to get it is to unlock the bootloader and flash the full android system files (from Google site) then relock the bootloader again!

Maybe it's got something stored from the factory testing?

All speculation I know!
[Google Pixel XL Questions & Answers] slickromeo:
it's just so frustrating for a phone taken straight out of the newly purchased box shipped from Google to Fail the SafetyNet check, right out of the box...

I guess my only other resort is to either flash android system files like you mentioned, ensuring bootloader is locked, or wait for google's bug fix department to get back to me........... who knows, I might qualify for an RMA
[Google Pixel XL Questions & Answers] DaveHTC200:
I agree!! It is shocking that is the case!!

I've never felt with the Google departments so don't know how long it will take, but if your pretty handy with the flashing techniques etc I'd give it a go, as once downloaded etc it's an a fairly quick process and saves waiting for Google, but it's down to your comfort levels ?
[Google Pixel XL Questions & Answers] superchilpil:
Look the sure fire way to fix this is to flash a factory image.
[Google Pixel XL Questions & Answers] slickromeo:
But when google ships out their phones to customers. they are shipped with a newly flashed factory image that google put on the phone themselves...... ugh....

will flashing a factory image downloaded from google interfere with the monthly security OTA updates, and the future O.S. updates ?
[Google Pixel XL Questions & Answers] superchilpil:
That doesn't guarantee something didn't go wrong in their end or something happened on your end. All it takes in a rogue app to modify something and it will fail. Maybe you sideloaded a malicious app? Or maybe one found its way on the play store.

Flashing a factory image is just that flashing it back to stock with updates. I suggest you familiarize yourself with them because it's a great thing to know how to do in situations like these.
[Google Pixel XL Questions & Answers] DaveHTC200:
No it won't interfere with anything, you can flash it, there's even a flash-all.bat file that essentially does it all for you.

Then you can relock the bootloader as long as everything is stock, then it will function as normal, with OTA etc
[Google Pixel XL Questions & Answers] slickromeo:
I'm not familiar with this process, could you point me to a simple tutorial? or copy/paste the steps in this thread ?
[Google Pixel XL Questions & Answers] DaveHTC200:
My explanation probably wouldn't be much good, I can do it but can't explain so well.

This tool should get you through though!! Just read an read again to understand before trying!

Firstly thought, in settings and About, click on the build number and keep clicking until it says you're a developer, the go back to setting and you'll see 'developer options

In here, you want to check the option about OEM unlocking, to allow the bootloader to be unlocked in the next few stages!

http://xdaforums.com/showthread.php?t=3482767
[Google Pixel XL Questions & Answers] tedkunich:
Are there any location based limitations on AP? could you be in a region that it is not supported (or at least your phone thinks you are)?
[Google Pixel XL Questions & Answers] slickromeo:
I've been using Android Pay since it was first launched in Florida. Also, How do I find out if my Pixel XL thinks i'm outside the country? I doubt it does, but might as well check now that you mention it. However the error message more than likely has to do with the SafetyNet check failure in my opinion.
[Google Pixel XL Questions & Answers] 4umexdeeay:
Hi :)

Having exact same issue on this end if anyone can continue to assist with troubleshooting...

Attempted to use Android Pay in-store today, nfc was enabled, but got the same "unable to verify..." error message.

It's a Pixel XL, direct from Google

Android 7.1, security patch level - November 5, 2016

Unrooted, have not tweaked bootloader, etc

Please note:

I did effectively make a purchase with Android Pay *using this same phone* back on October 24th, no errors, but it didn't work today.

That leads me to make the amateur's guess that all of this could be related to the November patch update :confused:

At any rate, further suggestions would be greatly appreciated!
[Google Pixel XL Questions & Answers] DaveHTC200:
Weirdly this is happening to me now, since going to the J OTA update.

No root or twrp, but fails the safety net!

I'm not overly worried but do find it odd!