yashsingh1/xdaforums huggingface dataset:
[Amazon Fire Phone] Ninja000:
No problem! "Sharing is caring" :laugh:

Yeah I like it too! I wish it was still supported by Amazon, but the bad press killed it.

As for not being able to use your account...you might try a factory reset, BUT...

FIRST: backup your APKs and saved files via USB to PC (can use file browser in Windows)

or MAC (will need this --->android.com/filetransfer/<---), and make sure under Battery and Storage, USB Connection Type is listed as File Transfer.

This is important because once you regeister, it might restore your last cloud backup, which I assume is probably pretty old after reading your reply.

Next:

Perform the Factory Reset OR...

To reregister your phone go to Settings, My Accounts, either "Register your phone" if that is an option (mine says "Deregister"), or maybe Manage your Amazon account.

The later will probably redirect you to the Amazon website, because the Amazon Shopping App is no longer supported on this older OS.

*I haven't found a newer version of the Amazon Shopping App that works on the Android 4.4 based Fire OS 4.6.6.1.

The other thing is you might be able to do it via the Amazon website, you probably have it listed under your account still, just need to find it.

I'd contact Amazon help to learn about how to do it that way. They might not know off hand, since the phone is no longer technically supported,

but they will definitely still try to help you.

I would really love it if someone on this forum could pull the launcher and everything from this version of Fire OS to work on the newer Android Roms like Cyanogen Mod,

because then we could just replace the old unsupported apps with the new versions. That would be awesome! I realize 2gb Ram would be a little low for the latest Android,

but just having a little newer OS version that is still supported by Amazon would be great. I really enjoy the Kindle App on this, because it has text to speech and

that is really convenient.

BTW, do you have the Google APPS installed on yours? I have them installed on mine, and it drains the batter like crazy,

granted, it's the original battery from 2014, but still. :)

Side note: If anyone has an extra screw(s) for the bottom they're willing to part with, I'd be willing to buy one (or a handful).

Lost one in the carpet (I know *rolls eyes) when I had to replace the camera module due to some (I guess) scratches or something actually on the sensor itself.
[Amazon Fire Phone] Ninja000:
Yeah I completely agree. I got mine for $199 and a year of Amazon Prime included made the phone basically $99. ? I happened to think of one more possibility. Maybe there is an Amazon Fire ?services app (like Google services) or account manager app that got automatically updated by your Google Play store, or even replaced by a version off the Play store that led to this issue, because like I mentioned mine is actually still working aside from the Amazon Shopping app, and some apps that require a newer google services to get notifications.

I actually had flashed several different Roms on this phone and yeah the stock (but updated) Fire OS 4.6.6.1 is definitely the best. --Amazon account registration is part of the initial setup BTW, so factory reset might work.

I made the jump over to iOS after experiencing the Android 7&8 difficulties on a few other devices and battery gate with Samsung phones. Now I am experiencing a crapy battery life issue with my iPhones. My Fire Phone is from 2014, original battery and still has better battery life than even my iPhone XS Max. Wow ? So yeah, there is something to Fire OS being so light that makes it probably just about the best OS for a phone. The last time I flashed back to stock I used a ROM from this website, but I don’t remember what thread that’s on. I think it’s in the Cyanogen 11 Rom thread for this device. Maybe try flashing that. And you could actually (if you don’t mind losing the storage space) create a backup Rom from your current one, then make a new slot in twrp or whatever it’s called and have the other Rom installed on there. Then check to see if it’s possible to register on that version. If it doesn’t work, no big deal you will still have your backup rom with all your data. If it does work, then you could transfer your stuff over via usb. That would save you quite a bit of time incase it decides not to work. You can do a root and install the other rom right from your fire phone these days. That’s a bonus.

What happens when you open Amazon Instant Video? Does it ask you for a loggin? That would be awesome. BTW My Kindle Fire HX 7 is still working great too, just starting to slow down a bit. I also have a 6" Fire HD. I really agree Fire OS is super clean and alot of modern OS's are not that great and way too heavy for what most people need, especially on mobile devices.
[Amazon Fire Phone] dini77:
Thanks again for your advice, especially since I will almost certainly end up flashing this thing. I have done a lot of "phone hacking" in the past -- even back in flip phone days -- but it is very time consuming and I'm super busy now. But it is kind of fun. So, maybe later.

I did not have Google Play (or any app store, on any of my devices) to be set to automatically update apps. Tho I think the store itself and its dependencies may still update, even if my apps don't, and I can't control that. And sometimes my setting to not automatically update is "reset" when a google component is updated. So it is conceivable that something got automatically updated and that caused my issue. I did have to reset the "do not update" setting.

I'm curious to see if anyone else has this issue, because if no, then you are right, I should just re-flash. I downloaded the latest Fire OS a while ago -- I collect stuff like that because you never know when it will be no longer readily available. So the phone is definitely not dead -- and it is nice that I have options for how to set it up. I'm glad to have the community contributions for that -- I did read thru those hacking posts.

I bought a spare battery a little while ago because I was worried they would be hard to get once I need one. But my currently installed battery, the original, is very satisfactory. So definitely I'll keep using this nice phone for a while.
[Amazon Fire Phone] Ninja000:
Was just thinking of going back to this phone as my primary phone. My problem is trying to get Micro G or something to work, for spoofing google services, because I want to use some apps that require google services, else they won't receive notifications. I also found on app I use, it's Korean, Kakaotalk is not receiving notifications when closed anymore. I haven't figured out why yet. Saw another thread about notifications on 3rd party apps not working, but didn't see a solution. I would also like to see a camera upgrade (4k video) and maybe a speaker upgrade and storage would be nice, but obviously that would require some soldering that I'm not willing to do, but maybe if I had a few doner phones would try it.:laugh: happy thanksgiving by the way!
[Amazon Fire Phone] dini77:
I just went back to a Nokia N9 as my primary, at least for voice and weather and such basics (MeeGo OS, and battery lasts for days, good quality voice, nice small size, does not crash, etc). But I have my iPad and iPhone SE (the older model) always turned on so that covers all my needs. So, it is perfectly fine to use an old phone as primary so long as you have another device to supplement what the primary lacks. The Fire Phone would also make a primary. Tho in my experience it is not as stable. The "mishap" in this thread was not my first serious hiccup. See also the thread on all apps crashing if they require the address book (including the phone). That one is serious and reoccurs. (I think it is caused by having a very large number of apps on the phone. Usually fixed when I delete one of the larger apps.) So in other words at least with the original OS, stability is an issue. Maybe the custom firmware on this board is more stable.

Have a great thanksgiving!
[Amazon Fire Phone] jrcspiderman2003:
Please help, I'm having the same issue the original poster had, I'm on a fire hd 8 10th generation tablet, I followed the instructions you guys put in, but now mine just says thisView attachment 6018554

Instead of letting me use the play store to open it like it was supposed to.
[LG G Flex 2] Kidsnd274:
Just received software update 15-C for my H959 Singapore varient.

I have not updated my phone to it yet, still running 15-A.

Did anyone update or flash it yet? If yes, what are the improvements?
[LG G Flex 2] caysman:
There is no improvement apparent. However it is a later revision so I just did it, you lose nothing.
[AT&T LG G4] soulysephiroth:
I cannot get my g4 to connect to my PC in download mode so that I push files/do anything to it. I've reinstalling the drivers and I still get a driver error under devices.
[ZenFone 2 Q&A, Help & Troubleshooting] ronniefaith:
hi everyone,

i having an issue with my battery level and it really pisses me off.

the battery level stuck at 50% - charging or not, it means you will never know if the phone is full charge(on charging) or nearly lowbat(discharging).

Also, it says "battery usage data isnt available.

it stays 50% when in recovery mode too.

i did the ff troubleshooting:

- wipe data, cache, system, etc.

- installed AOSP and CM ROM

- tried downloading battery test and everything is normal -

NOTHING CHANGED :( :(

The the battery stays upto 10+ hours but its hard to live without the battery level :confused:

hope you guys could help me with this - THANK YOU IN ADVANCE!
[ZenFone 2 Q&A, Help & Troubleshooting] Clark Joseph Kent:
Same here, and did the same, but unlocked boot loader, install ROM and tried to reflash firmware.

But batter stays at 50%...
[ZenFone 2 Q&A, Help & Troubleshooting] Clark Joseph Kent:
Maybe this Member can help [MENTION=4029265]Asus_USA[/MENTION]
[ZenFone 2 Q&A, Help & Troubleshooting] acaele:
Hi ! I have the same issue with the official rom ZE551ML updated 40.90

Enviado desde mi M52_Red_Note mediante Tapatalk
[ZenFone 2 Q&A, Help & Troubleshooting] Clark Joseph Kent:
I sent the device in for repair to Asus. Since it's under warranty.

✯ ✵ ✯Judgment is here.✯ ✵ ✯
[ZenFone 2 Q&A, Help & Troubleshooting] ronniefaith:
Got it fix

hi guys i found a fix here..

i did everything i mentioned above but none of those work so i thought it was a hardware issue and i was right.

this is what i did..

I removed the cover of the battery or battery plate (probably I had to unscrew everything) at the middle of the unit there were 3 flex connectors, and all i did was removed those 3 and carefully cleaned it. i used dry toothbrush then put the flexes back. and turned on the unit- and it workS!!!! then put everything back - :D:D

never had issue again with the battery :D

I am not responsible for anything if you follow what i did. there are some videos on youtube how to remove the battery plate that holds the battery..

thanks
[ZenFone 2 Q&A, Help & Troubleshooting] murguia:
Are you sure about this???, i did and nothings changed..
[ZenFone 2 Q&A, Help & Troubleshooting] mhp1995:
I had the same problem and i took it to a service centre,,, they told me it was the problem of the motherboard....They changed the motherboard and now its working fine
[ZenFone 2 Q&A, Help & Troubleshooting] mooloo:
i lived with this for a month till i found an accidental fix for this. i plugged in earphones (first time) to listen to a meditation app that i'd just downloaded, and when i unplugged the earphones and charged the phone, the charging display went back to normal.
[ZenFone 2 Q&A, Help & Troubleshooting] pecholino:
This usually happens when there is a loose connection between the motherboard and the battery. It happens on other androids too.
[ZenFone 2 Q&A, Help & Troubleshooting] bhaskardutta:
Same here...

I am facing the same issue.. battery bar stuck at 50%.. Sometime hitting at back restores the function.. but again goes back to same within a day or two.. very irritating..
[ZenFone 2 Q&A, Help & Troubleshooting] eksine:
The problem is not the software. the way you fix it is take off the back plate, remove all the tiny Philips screws and remove the hold down backing plate, and take a piece of paper and fold it 2 or 3 times and place it on the black foam piece that the battery connector is on the top of the battery, that's the battery connector connecting the battery to the phone electronic board. the problem is the connection is loose. what you are doing is creating a shim to push the connector in more. you could use electrical tape but paper works ok and you can control how much pressure to apply. do not use too thick of a piece for the shim or you would bulge out the hold down backing plate.
[ZenFone 2 Q&A, Help & Troubleshooting] kenchi_manok:
This actually fixed it, I got the battery of my phone replaced from the service center for another issue and got this problem after they replaced it. Wondering why they don't know about this problem they could have prevented it before it's released. First time I had to do this on my own as I'm frkn tired of going back to them. Thanks [MENTION=8389259]eksine[/MENTION] :victory: glad you visit XDA from time to time.
[ZenFone 2 Q&A, Help & Troubleshooting] p.pero54:
I must say : Asus Zenfone 2 is a peace of sh.. or maybe garbage.

I have problems with this phone from the day one.

Whatsapp,

battery (died after 4 months),

bad signal for internet (my other phones works much better),

software,

now the new battery is stuck on 50%

I promise that I will never again buy any product from Asus in my life, because this phone has destroyed my nerves.
[ZenFone 2 Q&A, Help & Troubleshooting] awyeong:
Good find!!

I change a battery by myself and after that I stuck at the 50% too. After I read your post, I reopen the cover and found that the battery connector is really loosen and I apply your shim method to make it more better connection and it can read the actual battery percentage.

Thank you!
[Android Apps and Games] punkmexic:
Can someone develope a vhs camcorder app for android? (since rarevision's app is only for ios
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sacrawfo:
Hi,

I know this information is probably available somewhere, but I have spent hours of reading, and still having some trouble getting my head around things. So I will try to be clear here as to what my issues are.

Firstly... I have Samsung Galaxy S-III, SGH-i747M, with virgin mobile canada. It started with android 4.1.2. I wanted to unlock it, and there was a way to do it with 4.1.1 (http://xdaforums.com/showthread.php?t=2176719), so I used odin, with firmwares (found at SamMobile.com I think) to flash a 4.1.1 ROM, did the unlock procedure, and then used odin to flash stock firmware for 4.1.2 again. Seems to have all worked out ok.

Anyway, I want to try some custom roms, like cyanogenmod, as they are purported to improve battery life, speed, clearing off bloatware, giving me more control, etc.

However, I really want to maintain the ability to go back to how it is now, if I don't like the custom roms. (or if I need warranty help, though there's not much of that left).

The main thing that's concerning me is that while I was playing with this phone before, I read in a number of places that if I had updated to Android 4.3 or 4.4.2 when those had become available from my carrier, I would not have been able to downgrade to 4.1.1 (which I needed to be able to do to use the built-in unlock method). This is because of Knox, which would be installed, and gets "tripped." So now I'm scared: if I did that upgrade, I wouldn't have been able to revert; so now, if I flash a CGM ROM, will I also be unable to revert?

I think there are a few pieces of android to sort out in my mind... If I'm not mistaken, there's bootloader, there's recovery, and there's the ROM. Flashing a ROM with Odin apparently would restore recovery and the ROM? But not the bootloader (that's where knox is? though I still don't understand, if an upgrade can modify the bootloader and put knox there, where it wasn't before, shouldn't there be a way to put a pre-knox version back there?)

Oh, there's also EFS, which some say should be backed up before doing anything (though you need to root first, which in my mind counts as doing something before backing it up).

Anyway, please let me know if you can help clarify these issues, thanks!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
[MENTION=5575315]dawgdoc[/MENTION] is correct about everything said.

It is not Knox that prevents downgrading from 4.3 to an earlier version, it is the code in the bootloader itself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sacrawfo:
Ok, starting to feel a bit more comfortable with the whole system and relationships, thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Thanks for verifying that. There could have easily been small, but very important, differences in the devices that had slipped my mind since I don't have the i747M.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
This is the way xda should be. Good questions from a concerned user & great answers from [MENTION=5575315]dawgdoc[/MENTION]. Nice job guys!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I would like to extend similar praise and thanks to [MENTION=5511100]mrrocketdog[/MENTION] and [MENTION=4673498]audit13[/MENTION]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sacrawfo:
more uncertainty

Hi,

I'm a lot more experienced now, having rooted (I flashed root66_BMC_I747MVLDMF1 by MrRobinson, since CF-autoroot just made the phone show "booting recovery" then blank screen indefinitely), I backed up EFS by a couple methods, flashed TWRP, did a nandroid backup, and flashed a couple versions of CM. Still a few things I want to clarify though.

Unsurprisingly, after flashing the final CM 11 release, data did not work, as I'm still on the 4.1.2 (MF1) bootloader/modem. In general, I see a lot of posts simply saying "update the modem." From what you've said though, that will create problems, unless I update the bootloader as well, correct? Just feels like the phrase "update the modem" is said so casually, without also mentioning the bootloader, and the inability to go back.

(an older CM 11 worked with data just fine)

(a big issue is that S3 is over 3 years old, so there are over 3 years of posts, so there's a lot of conflicting information, likely due to different versions, new discoveries, etc. )

I'm not quite sure myself what I'm trying to ask, I guess it's something along the lines of "am I just being silly by not updating?" There are a lot of "Never update to 4.3 (or above) because of knox!" comments. But also in general, it seems the only real issue with knox is that warranty bit, otherwise it doesn't have too big an impact on our lives? Seems the consensus is that we can still root, install custom roms, and everything else. (Do you know if this remains true with latest bootloaders and modems (OB3 for i747M). There are also "My battery life became way worse after the upgrade" or "more FCs" or other issues, which is a significant concern if my phone which currently comfortably lasts a day starts to not last a day after updating. Though it's likely a small percent noting that, while the quieter majority are fine. Meanwhile, by not updating, we may be missing out on features and security improvements (and maybe actually improved performance). What do you guys think? (I know dawgdoc was sticking to an unofficial 4.3 rather than updating, so it's not an obvious choice).

As for updating, I think somewhere one of you suggested the better (or at least safer) way is to use odin to flash stock ROM, then do the OTA updates, or, directly flash the latest stock ROM, rather than trying to flash modems and bootloaders directly?

Once I have a 4.3 or 4.4.2 bootloader/modem, I can delete any old TWRP nandroid backups from when I had 4.1.2 since restoring them would cause a brick? Same for EFS backup (which backed up EFS, Modem, Modemst1, and Modemst2 partitions)

Thanks again!

I almost wish I'd just taken the blue pill at the start of all this :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
For XDA members that are new to rooting, flashing, etc., I always recommend the safest route which is to flash back to a completely stock ROM and just upgrade to the latest bootloader and modem via OTA updates. There's always a risk of something going wrong when flashing anything, be it a custom ROM, recovery, or OTA update.

If the phone still had warranty, I recommend not flashing any non-Samsung software until the warranty has expired. Once expired, flash away :)

Knox should not interfere with root if supersu is flashed from a custom recovery, regardless of the bootloader. I have used supersu to root the latest s3, s4, Note2, and Note3 ROMs without a problem.

Restoring old nandroid backups should not cause a brick as TWRP does not change the modem or bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I think the change date for CM11 requiring the newer bootloaders, at least NE4, is Nov 2014. Releases prior to that date would run fine on older bootloaders.

I have since updated to NE4 in order to run ROMs patched with the StageFright fixes, specifically CM11 20150831. Knox isn't installed on this ROM or even the newer custom TouchWiz based ROMs. I am not concerned about Warranty Bit being triggered. My device is long past being covered by any warranty and I have no intentions of using Knox features on this phone in a corporate environment.

Keep the EFS backups, those are from partitions not changed by flashing roms; stock or otherwise.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sacrawfo:
Finally went through the OTA updates, surprised how long it took but all done, at OB3.

Ok makes sense, restoring an old Nandroid would effectively result in a 4.1.2 OS with a 4.4.2 bootloader/modem, which != brick.

Still surprised that modem updates do not effect the "modem" partition that EFS backup saved.

Thanks,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Restoring a nandroid backup should not brick the phone brick the phone as twrp does not restore the modem or bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
There are quite a few partitions not affected by flashing, not only the EFS partitions. IIRC there are secondary modem partitions, more than two extra bootloader partitions, etc.
[Amazon Fire Phone] v6ser:
As we know, Amazon never released an official way to unlock the bootloader on their devices.

I'm pretty sure a lot of their customers have requested the same thing over and over, but what i'm not sure of is if anyone got a response from their "customer help" like mine.

The other day, I sent my 2nd request regarding the bootloader unlock, kernel sources and "system_core" patches they'd released for Kindle Fire HD and HDX, the answer was being already a lot more interactive then my first response(props to that).

They replied saying that "Kernel source codes weren't available at this time", and that they had forwarded my suggestion to its developer team, but i noticed the employee forgot to mention the bootloader unlock part, which for me was of utter importance.

So again i contacted them, via the reply option we get when we send feedback, in order to continue the last question and asked about the bootloader unlock.

This is the full reply i got from them today:

It was explicitly said that their technical team is working on a developer version of the phone and that they will, and i quote, DEFINITELY, provide bootloader unlock code on their website.

That is a really great response. Thanks amazon.
[Amazon Fire Phone] ggow:
That is awesome news :)
[Amazon Fire Phone] Moogagot:
This is fantastic! I'm guessing this would allow for better NFC support and maybe even a camera fix?
[Amazon Fire Phone] Bingo Bronson:
I wonder when that will be... maybe even before Kanye running for president.

Their headhunters are doing a bad job so far... ;) I can think of a person, what was his name, uhm...

Amazon is a "huge" company but I refuse to call them "great". :p