Develop Bugs

AT&T Fire Phone, Unlocked and Rooted - Any way to install Google Play?

I'm rooted with SafeStrap installed. AT&T unlocked with the latest firmware. Is there a way to install Google Play? I've been trying the "just install the APKs" method, and it isn't working. Well, it'll work once then not work again.
Any hope? I was hoping I could flash something, but I don't know if that would work.

Flash one of these: Mini GAPPS by RolanDroid or PA GAPPS Pico.
The contents of those flashable zip files are almost the same, I'm using PA GAPPS Pico right now, had Mini GAPPS before.
The problem isn't solved with installing one of those GAPPS, but they offer the LEAST amount of "Play services crashes".
edit: when you say "AT&T unlocked"... does that mean that you're using the 35.4.6.1_user_461013320 and then unlocked or are you running 35.4.6.1_user_461013820 on your device?

Bingo Bronson said:
Flash one of these: Mini GAPPS by RolanDroid or PA GAPPS Pico.
The contents of those flashable zip files are almost the same, I'm using PA GAPPS Pico right now, had Mini GAPPS before.
The problem isn't solved with installing one of those GAPPS, but they offer the LEAST amount of "Play services crashes".
edit: when you say "AT&T unlocked"... does that mean that you're using the 35.4.6.1_user_461013320 and then unlocked or are you running 35.4.6.1_user_461013820 on your device?
Click to expand...
Click to collapse
It's the 320. It was AT&T that was then unlocked.

Hrmpf... Then you may have heard about the problems on all those versions ending with 320 (the German & UK versions are also poorly in handling GAPPS).
For whatever reason, the "GSM unlocked" version ending with 820 gets the best results regarding Play Store & services.
You may consider installing the 820 after trying it on your current 320. For help with installing the "new" image, click the 2nd link in my signature ("Fire Phone stock recovery: factory images").
Just report back here with your results and / or if you need further info & help. Btw. The "GSM unlocked" version will work fine on your device, the net(un)lock isn't affected by the OS version.

Bingo Bronson said:
Hrmpf... Then you may have heard about the problems on all those versions ending with 320 (the German & UK versions are also poorly in handling GAPPS).
For whatever reason, the "GSM unlocked" version ending with 820 gets the best results regarding Play Store & services.
You may consider installing the 820 after trying it on your current 320. For help with installing the "new" image, click the 2nd link in my signature ("Fire Phone stock recovery: factory images").
Click to expand...
Click to collapse
I was just looking at that. I'll give it a shot. Thanks!

To update: I flashed the 820 firmware and SuperSu, booted and logged into the phone, then rebooted and flashed Google Apps. It's working great! Once I got it up and running it seems to be working damn near flawlessly.

How about 4.6.4 464000220
I'm running 4.6.4 464000220. I ran KingRoot. Installed Safestrap. Flashed PA GApps. I can get some apps ok but Google Photos doesn't seem to be able to upload. Should I try something else? Another firmware?
Thanks,

Got it
I downgraded to 4.6.3 and flashed the PA GApps. Rooted with GoMobile. Everything is working great!

[Q] Fire Phone: SuperSU-me, Xposed Framework and other Issues

Hi,
I just got a fire phone and I'm facing multiple issues. It updated to 4.6.6.1 once i started it. Now I want it to act like a normal android phone so I installed google now launcher.
Next thing i wanted to do is to customize the laucher. So I did research how to root it. Did it with kingroot and afterwards followed various instructions to change to superSu. Non of them worked. Neither via adb nor SuperSU me nor the terminal version. only rooted when on kingsroot. SuperSU binaries also would never succesfuly update. Anyways.
So after I got the root, I wanted to install Xposed Framework to finally customize the launcher. Now xposed is saying, that it is not (yet) compatible wit the ANdorid SDK Version 19 or my Prozessor architecture. (armeabi-v7a)
I'm running the phone on german language. Don't know what to do anymore with both. SUpersu and Xposed. Appreciate any help.

So you already bought Super-Sume-Pro? Good, because removing / replacing Kingroot was possible even with the (early) free version of Super-Sume (9.1.6).
Download this old version* of Kinguser.
Yes, like always, it's classified as a virus / exploit / PUP, because it uses very aggressive methods of achieving root.
"But Bingo, this is only Kinguser, I need Kingroot."
No you don't. I used this combo many times, it always worked, from the latest version down to Fire OS 4.6.1 when I first tried it.
Uninstall your current version of Kingroot / Kinguser and remove the leftover folders from the internal storage.
Install the old version (disable auto update within in the app, it can be quite annoying), let it "achieve" root, disable WiFi if you want.
Run Super-Sume. It will have no problem replacing Kinguser with 2 steps.
Download this compatible version of the Xposed Installer.
Install framework, etc. You know the drill.
For BusyBox, I'd recommend either Stericson's version or Meefik's.
I tested one of my devices with 4.6.6.1 and the above mentioned customizations (mainly to enjoy microG on Fire OS ^^), so I can say it definitely works.
* Had to use OCH, because the "good guys" like Dropbox and Google Drive won't allow hosting / linking this file, since it's a bad azz virüs.

I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

Plonko said:
I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot.
Click to expand...
Click to collapse
Ugh, so many letters, I'm so confused, please... no more, let's stay with "dumb it down". This saves time so I can roll around in my own feces. :victory:

Plonko said:
I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Click to expand...
Click to collapse
W0lfdorid was one of the versions i tried. no success. I can start the script but then it says failure and every single steps fails. I finally made it to the supersu installed, but it wont update the binaries. installation always failed

coolni said:
W0lfdorid was one of the versions i tried. no success. I can start the script but then it says failure and every single steps fails. I finally made it to the supersu installed, but it wont update the binaries. installation always failed
Click to expand...
Click to collapse
Hmmmm...I don't know what to say. I just used it today after returning a phone to stock Fire OS for my niece. The only thing I can think of is I'm using an earlier version of Kingroot? I'm using KingRoot-4.1.0.524.apk if that matters. I can try to PM it to you, but I'm not sure it will work because, as Bingo mentioned, it is seen as a virus by most servers.

Yup, I also used the oldest version I had on my PC, this way I can avoid the cat and mouse game between Kingroot and Super-Sume ^^ ... well, for the Fire Phone and some "older" KitKat devices that is.
But since 'coolni' popped his Fire Phone cherry just recently, he naturally went for a current version of Kingroot and he's also on the latest Fire OS release; thought process = better bring the big guns so that root is guaranteed.

Bingo Bronson said:
Yup, I also used the oldest version I had on my PC, this way I can avoid the cat and mouse game between Kingroot and Super-Sume ^^ ... well, for the Fire Phone and some "older" KitKat devices that is.
But since 'coolni' popped his Fire Phone cherry just recently, he naturally went for a current version of Kingroot and he's also on the latest Fire OS release; thought process = better bring the big guns so that root is guaranteed.
Click to expand...
Click to collapse
can anybody help to root 4.6.6.1 ?
Kingroot 4.0.0.233 from zip file did not work on my phone with 4.6.6.1.

Having problems on custom recovery
Hello sir I am using amazon 4.6.6.1 almost 1 year ago I have backed up my custom recovery from flashify and deleted accidentally now I need that but can't do anything I have tried most things to get back but can't and also can't root my phone with king root I am installing it but it's saying that app not installed any solution please my email is [email protected]

[Discontinued] Negalite Huawei-Rom NX 2 | ROOT | BB | v1.2 | 6/7/17

Welcome To NegaLite Huawei-Rom NX 2!!!
I AM NOT RESPONSIBLE FOR ANY DAMAGES! Use At Your Own Risk!
This Also Voids Your Warranty!
ROM Chefs: Use Whatever You Like! No Thanks/Credit Needed! Happy Cooking!
Features:
Based On N7G75S - Wear 2.0
Stockish Kernel
Rooted - SuperSU
Busybox 1.27.0
Adb Debugging Pre-Enabled
Many System Apps Moved To /data For Easy Uninstall
Includes Root Essentials
Includes Custom Advanced Settings
Updated Gapps, Hangouts, Fit, Maps, Music
------------------------------------------------------------------------------------------------------------------------------
Downloads:
If You've Never Flashed This Before, You Need To Format Data Partition Via TWRP Advanced Wipe
If You Don't Have TWRP, Get It Here: TWRP 3.0.3 Themed
Just Do This:
1. Push Zip To /sdcard/ Via ADB (adb push rom-location/rom-name.zip /sdcard/)
2. Flash zip In Recovery(TWRP) Via Install
3. Done (Enjoy!)
Huawei-Rom-NX-2-v1.2.zip - 6/7/17
LG G Watch R Faces - LG_Watch-R-Faces_v1.zip
Like the Rom? Try My Custom Kernel!: Negalite HW+
Special Thanks To SuperThomasLab For Allowing Us To Include Root Essentials
You Can Always Find It Here : https://play.google.com/store/apps/d...rootessentials
Special Thanks To suleymanovemil8 For Allowing Advanced Settings To Be Open Source
You Can Always Find It Here: https://play.google.com/store/apps/d...vancedsettings
------------------------------------------------------------------------------------------------------------------------------
Changelog:
v1.0
Initial Release
v1.1
Faster First Boot
Increased Performance
v1.2
Updated to N7G75S
​

Reserved...

Yes!!!

Fantastic!

Agreed. Looking forward to this.

Pleqse make advanced watch settings work
Edit: it works but DND doesn't work? Is this a dp4 bug?

Thank you for a great ROM. Is there a way to add more face watch to this version? I downloaded several, but none of them appear in android wear. Thanks.

atn0716 said:
Thank you for a great ROM. Is there a way to add more face watch to this version? I downloaded several, but none of them appear in android wear. Thanks.
Click to expand...
Click to collapse
Open the Play Store on the watch and install them.
edit - You might read this to get up to speed on the MASSIVE changes from AW 1.5 to 2.0 Previews:
https://developer.android.com/wear/preview/support.html

Awesome way to start the New Year! Kudos

new bootloader or anything else needed? Or just wipe and flash away?

is root working for anyone else? tried getting into advanced settings and it says i don't have root? can i simply flash a supersu zip?
edit: root appears to work, it's advanced settings that isn't getting along

im assuming i need to go to official dev preview for bootloader first coming from your other rom @negamann303
edit- never mind it took like 15 mins to boot but i was at my office so no biggie lol

Smacksmack206 said:
im assuming i need to go to official dev preview for bootloader first coming from your other rom @negamann303
Click to expand...
Click to collapse
You shouldn't have to change bootloader as long as you use my kernels (modified stock included)
Sent from my SM-G935P using Tapatalk

I will have to wipe the watch. ok. Will Wear Manager install "old apps" as installing 1.x rom? Or will i have to config the watch from scratch?
If the last one, i wont test it before weekend Wont like to be a half week without my watch

SirTurbo said:
I will have to wipe the watch. ok. Will Wear Manager install "old apps" as installing 1.x rom? Or will i have to config the watch from scratch?
If the last one, i wont test it before weekend Wont like to be a half week without my watch
Click to expand...
Click to collapse
It's recommended that you do a full wipe if only coming from my 1.5 rom. Only because I have system apps in data. But the workaround would be deleting the system apps in data/apps in recovery prior to install
You could probably use root essentials to uninstall the system apps that are stored in the data partition
Sent from my SM-G935P using Tapatalk

well, i understand to wipe cache, system, data... dont like, but think need to do, better at a version upgrade as this.
but if i do the big wipe (maybe i flash tonight because i cant refuse to play^^) i am not sure if i need to install the apps which come from phone again by hand. Or the android wear manager installed on the phone will "complete" the installation at watch as when i did fresh installed earlier, from 1.5 to 1.5.
Maybe i will need the android wear manager for 2.x too and that one wont use the config of the older one.
Hmm, think i will give it a try, just made a backup. Hate that watches have only 4GB flash. when using, storing some zips to flash und doing a backup... the watch begins to whine about less space...
Interested in the next days - having no time to play with wear. last weekend installed an amazon fire tv box for a mate, rest of the week will be "full" too. f.e. friday i drive to a friend of mine, installing her sons new phone. and then taking the tablet from one of her friends. to play around with grub to get it back to life. and so on. And now you forced me to play with my wearable. a day should have 48 hours

im so happy this rom is perfect.
and even advanced settings works since the dev updated to the lasted api

SirTurbo said:
well, i understand to wipe cache, system, data... dont like, but think need to do, better at a version upgrade as this.
but if i do the big wipe (maybe i flash tonight because i cant refuse to play^^) i am not sure if i need to install the apps which come from phone again by hand. Or the android wear manager installed on the phone will "complete" the installation at watch as when i did fresh installed earlier, from 1.5 to 1.5.
Maybe i will need the android wear manager for 2.x too and that one wont use the config of the older one.
Hmm, think i will give it a try, just made a backup. Hate that watches have only 4GB flash. when using, storing some zips to flash und doing a backup... the watch begins to whine about less space...
Interested in the next days - having no time to play with wear. last weekend installed an amazon fire tv box for a mate, rest of the week will be "full" too. f.e. friday i drive to a friend of mine, installing her sons new phone. and then taking the tablet from one of her friends. to play around with grub to get it back to life. and so on. And now you forced me to play with my wearable. a day should have 48 hours
Click to expand...
Click to collapse
Actually, it doesn't sync like 1.5. You actually have to install them all via play Store on the watch. The good news is that there is a section on recently used apps, which includes your watch apps installed prior, also they install pretty quick.
Sent from my SM-G935P using Tapatalk

negamann303 said:
Actually, it doesn't sync like 1.5. You actually have to install them all via play Store on the watch. The good news is that there is a section on recently used apps, which includes your watch apps installed prior, also they install pretty quick.
Click to expand...
Click to collapse
Hmmm... interesting recently used apps sounds nice. but i think i will save my backup for a while
but first problem: When i try to copy my google account to watch, i get an error on phone.
And an interesting issue: I chose english language because i read that other languages might cause some malfunctions.
but after that, the messages come in german, the language at my phone. i am not able to say what will be later on, because actually i stuck on copying the google account.
Edit:
ok, maybe the phone cant copy the account to watch because watch hangs. watch is looking for updates and "nothing goes"...

only thing i notice is play music doesnt open upon seleting play on wear.
it goes back to watch face screen
-edit-
if it does what i mention originally then uninstall and reinstall from play store to get "play music" working

Should I update FTV OS on my rooted ftv

I have a ftv rooted with version 51.1.4.0, but am unable to update kodi beyond 16.1
All the attempts fail and some have said an OS update is needed to do that upgrade of KODI 17.
I also cannot install SPMC, also fails using abdfire.
any ideas?
tia

ant17 said:
I have a ftv rooted with version 51.1.4.0, but am unable to update kodi beyond 16.1
All the attempts fail and some have said an OS update is needed to do that upgrade of KODI 17.
I also cannot install SPMC, also fails using abdfire.
any ideas?
tia
Click to expand...
Click to collapse
SPMC should work. Last I checked it was still mostly based on Kodi v16.1. Install AppStarter & try to install SPMC from there. Or from Downloader thru FireTVGuru.net.
I would recommend you research the upgrade process & once you understand it & have meet all requirements. Make it so.
Right now upgrading from FireOS 3 might be a bit complicated since an update cycle just started today. And there is no PreRooted ROM for the latest yet. You will need to make sure you TWRP block updates using the 5th method if you upgrade to the current PreRooted ROM.

Y314K said:
SPMC should work. Last I checked it was still mostly based on Kodi v16.1. Install AppStarter & try to install SPMC from there. Or from Downloader thru FireTVGuru.net.
I would recommend you research the upgrade process & once you understand it & have meet all requirements. Make it so.
Right now upgrading from FireOS 3 might be a bit complicated since an update cycle just started today. And there is no PreRooted ROM for the latest yet. You will need to make sure you TWRP block updates using the 5th method if you upgrade to the current PreRooted ROM.
Click to expand...
Click to collapse
Is it advised to move up to the most current prerooted FireOS 5 when it becomes available? I have a gen1 box on the last prerooted FireOS 3, and a prerooted gen 1 stick. Is holding either of these back on 5.0.5 a good idea? I suspect the new interface updates will include some amount of performance penalty.

Axecaster said:
Is it advised to move up to the most current prerooted FireOS 5 when it becomes available? I have a gen1 box on the last prerooted FireOS 3, and a prerooted gen 1 stick. Is holding either of these back on 5.0.5 a good idea? I suspect the new interface updates will include some amount of performance penalty.
Click to expand...
Click to collapse
The update to FireOS 5 is mostly recommended for App comparability. More & more apps in the PlayStore & Amazon have lollipop as the starting point.
I did learn to live with the no Home button detection for AppStarter. I still use AppStarter 90% of the time. I just keep AppStarter as the only app in recent. So it has just added a couple of presses to what I was use to with FireStarter. But if the HOME button detection is a huge deal for you. You should stay there.
As for the updates. I have not seen any performance hits. The only major problem might be bugs. But the tier rollout of the update usually takes care of that. I tried the new UI on a couple of FTVS2's & they weren't laggy at all. I usually find the latest FW to be as fast or faster of prior onces. But that might be because I prefer to do clean installs when upgrading FW. Specially on an update as big as the one that just started to rollout. The new update includes more stuff but luckily it comes with options to turn some of that stuff off.
We can also always downgrade PreRooted Rom's. So it's fine to take things for a spin. As long as you have a good install of TRWP. There shouldn't be a problem. Other the user error or power outage.

I wouldn't care about the KODI update, but a message from tv addons says streams are more often using the https: for shows and 16.1 doesn't support that.

Axecaster said:
Is it advised to move up to the most current prerooted FireOS 5 when it becomes available? I have a gen1 box on the last prerooted FireOS 3, and a prerooted gen 1 stick. Is holding either of these back on 5.0.5 a good idea? I suspect the new interface updates will include some amount of performance penalty.
Click to expand...
Click to collapse
Is there a OS prerooted 5 out? I have 2 FTV boxes rooted that won't take spmc or 17.1 kodi.

ant17 said:
Is there a OS prerooted 5 out? I have 2 FTV boxes rooted that won't take spmc or 17.1 kodi.
Click to expand...
Click to collapse
Yes, but which version are they. So I can give you the right guide link. FTV1 or FTV2 ?
It all starts with the recovery...
(Make sure you install the right version 7 (aka v3.0.0-7) of TWRP depending on your locked or unlocked bootloader on FTV1's)
FTV1: http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-1/
FTV2: http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-2/
http://www.aftvnews.com/how-to-root...covery-and-a-pre-rooted-rom-all-without-a-pc/
FTVS1: http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
Just make sure you follow the requirements. A good install of TWRP is key.

Axecaster said:
Is it advised to move up to the most current prerooted FireOS 5 when it becomes available? I have a gen1 box on the last prerooted FireOS 3, and a prerooted gen 1 stick. Is holding either of these back on 5.0.5 a good idea? I suspect the new interface updates will include some amount of performance penalty.
Click to expand...
Click to collapse
Y314K said:
Yes, but which version are they. So I can give you the right guide link. FTV1 or FTV2 ?
It all starts with the recovery...
(Make sure you install the right version 7 (aka v3.0.0-7) of TWRP depending on your locked or unlocked bootloader on FTV1's)
FTV1: http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-1/
FTV2: http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-2/
http://www.aftvnews.com/how-to-root...covery-and-a-pre-rooted-rom-all-without-a-pc/
FTVS1: http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
Just make sure you follow the requirements. A good install of TWRP is key.
Click to expand...
Click to collapse
I think they're ver. 2 but unknown OS.
One is 51. 1. 1. 0, the other is 51. 1. 4. 0 Both are rooted.

ant17 said:
I think they're ver. 2 but unknown OS.
One is 51. 1. 1. 0, the other is 51. 1. 4. 0 Both are rooted.
Click to expand...
Click to collapse
v2 AFTV's are the only current devices with both a USB & SDCard slot. So easy to tell. As for OS there are only two types. Either Amazon Original ROM or RBox's PreRooted ROM. Both would show same version numbers in System/About info menu.
Since you say they are Rooted. Then u very likely have a PreRooted ROM install. And when using Apps that use root it will ask you for permission the first time that App or option runs. Like in the case of ES File Explorer Root option. If you had already given it permission then you would see a notification letting you know Root access has been activated/granted to ES File Explorer.

Y314K said:
v2 AFTV's are the only current devices with both a USB & SDCard slot. So easy to tell. As for OS there are only two types. Either Amazon Original ROM or RBox's PreRooted ROM. Both would show same version numbers in System/About info menu.
Since you say they are Rooted. Then u very likely have a PreRooted ROM install. And when using APS that use root it will ask you for permission the first time that App or option runs. Like in the case of ES File Explorer Root option. If you had already given it permission then you would see a notification letting you know Root access has been granted to ES File Explorer.
Click to expand...
Click to collapse
OK, been a long time since I rooted these so I'm assuming its a pre-rooted rom. Both boxes have just the usb and no sd slot.

ant17 said:
OK, been a long time since I rooted these so I'm assuming its a pre-rooted rom. Both boxes have just the usb and no sd slot.
Click to expand...
Click to collapse
Then you have FTV1's like I do. Go thru the requirements check list from the FTV1 TWRP guide I linked above. And make sure you understand what you are doing before updating. I usually keep everything. Files, APK's, Rom's in a USB to flash & install & I verify MD5 hash's to make sure I copied the files correctly. Specially the recovery/TWRP file & PreRooted ROM.

Y314K said:
v2 AFTV's are the only current devices with both a USB & SDCard slot. So easy to tell. As for OS there are only two types. Either Amazon Original ROM or RBox's PreRooted ROM. Both would show same version numbers in System/About info menu.
Since you say they are Rooted. Then u very likely have a PreRooted ROM install. And when using APS that use root it will ask you for permission the first time that App or option runs. Like in the case of ES File Explorer Root option. If you had already given it permission then you would see a notification letting you know Root access has been granted to ES File Explorer.
Click to expand...
Click to collapse
Y314K said:
Then you have FTV1's like I do. Go thru the requirements check list from the FTV1 TWRP guide I linked above. And make sure you understand what you are doing before updating. I usually keep everything. Files, APK's, Rom's in a USB to flash & install & I verify MD5 hash's to make sure I copied the files correctly. Specially the recovery/TWRP file & PreRooted ROM.
Click to expand...
Click to collapse
Is there a way to see which recovery is already on the box? like cmod? I assume I would need to get twrp on there but didn't want to cause a problem by just puting it on there without knowing if cmods there.

Deleted

ant17 said:
Is there a way to see which recovery is already on the box? like cmod? I assume I would need to get twrp on there but didn't want to cause a problem by just puting it on there without knowing if cmods there.
Click to expand...
Click to collapse
The only method is to connect a keyboard to your FTV1 & choose to boot into recovery at startup. You should see the exact version on the lower left hand side.
If your going to be using a USB drive to flash things. You will need a USB hub to have both the USB Keyboard & USB drive hooked up to the device at the same time.
Those guides are the most complete ones. But they are some what old & also each FTV has it's own history of what has been done to it. So make sure you modify accordingly. I thought about making a post with my notes regarding this updating guide but I thought everybody's starting point is probably to different & I don't want to be responsible for bricking any FTV1's.

Y314K said:
Then you have FTV1's like I do. Go thru the requirements check list from the FTV1 TWRP guide I linked above. And make sure you understand what you are doing before updating. I usually keep everything. Files, APK's, Rom's in a USB to flash & install & I verify MD5 hash's to make sure I copied the files correctly. Specially the recovery/TWRP file & PreRooted ROM.
Click to expand...
Click to collapse
Is there a need to flash the stock recovery in order to get rid of twrp/unroot the fire TV 1 and allow it to update itself back to stock? Is flashing cwm over twrp the only way?
I unblocked updates and they get downloaded but after it reboots twrp blocks the update process.
I am trying to get the device back to stock per buyer's request

Y314K said:
SPMC should work. Last I checked it was still mostly based on Kodi v16.1. Install AppStarter & try to install SPMC from there. Or from Downloader thru FireTVGuru.net.
I would recommend you research the upgrade process & once you understand it & have meet all requirements. Make it so.
Right now upgrading from FireOS 3 might be a bit complicated since an update cycle just started today. And there is no PreRooted ROM for the latest yet. You will need to make sure you TWRP block updates using the 5th method if you upgrade to the current PreRooted ROM.
Click to expand...
Click to collapse
Tried to install spmc 16.6 via adb fire, ES file explorer, and total commander (which happens to be WAY better than ES file explorer) and I get parsing error. Never does install.

evaporic said:
Is there a need to flash the stock recovery in order to get rid of twrp/unroot the fire TV 1 and allow it to update itself back to stock? Is flashing cwm over twrp the only way?
I unblocked updates and they get downloaded but after it reboots twrp blocks the update process.
I am trying to get the device back to stock per buyer's request
Click to expand...
Click to collapse
There is no guide on how to go back to stock FW on a FTV1 once TWRP is install. This is due to the version of FW & TWRP that the FTV1's where first updated to FireOS 5. That was FW v5.0.5 & TWRP v6. So the TWRP had matured enough to fully block updates.
The only info regarding downgrading can be found in the TWRP thread. Folks that failed @ updating to TWRP correctly where able downgrade back to CWM. I think you also need to downgrade the FW to a PreRooted FireOS 3 too but I could be wrong. Once on CWM you should be able to allow updates since CWM won't block those updates.
Look/search for more info on the few folks that where able to go from TWRP to CWM here:
https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286
Also once your fully on CWM/FireOS 3 you might be able to use this guide to downgrade too:
http://www.aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/
All of the above is theory for me. Since I've never had to dealt with this. And there are no guides for this specific scenario. So make sure you look thru the TWRP thread to find the folks that actually mention going back to CWM. Although most of them did so just to reflash TWRP.
Search example: https://forum.xda-developers.com/search/thread/3383286?query=back to cwm
ant17 said:
Tried to install spmc 16.6 via adb fire, ES file explorer, and total commander (which happens to be WAY better than ES file explorer) and I get parsing error. Never does install.
Click to expand...
Click to collapse
Note 1: As of 16.5.0, Android lollipop (API 21) is required
_____________________________________
16.5.0 (2016/11/30):
CHG: API 21+ (Android 5.0) only, sorry.
ADD: 4K on AFTV2
ADD: refresh rate sync on AFTV
ADD: DASH support (aka 1080p/4K youtube)
ADD: Builtin log (Settings-System-Logging-Upload…)
ADD: crash handler (no need for logcat)
ADD: rendercapture (boblight, Hue, …) support for Surface
FIX: Only stop Surface when really necessary
CHG: Revert to Surface as standard
ADD: acceleration setting for hevc
16.4.2 (2016/08/15):
REVERT: crash when enumerating sound devices during a refresh rate change
FIX: Missing start of video with large buffer
You will need to find SPMC v16.4.2 for FireOS 3.
You can find it from source here: https://github.com/koying/SPMC/releases?after=17.0b3-Krypton

Y314K said:
SPMC should work. Last I checked it was still mostly based on Kodi v16.1. Install AppStarter & try to install SPMC from there. Or from Downloader thru FireTVGuru.net.
I would recommend you research the upgrade process & once you understand it & have meet all requirements. Make it so.
Right now upgrading from FireOS 3 might be a bit complicated since an update cycle just started today. And there is no PreRooted ROM for the latest yet. You will need to make sure you TWRP block updates using the 5th method if you upgrade to the current PreRooted ROM.
Click to expand...
Click to collapse
Y314K said:
There is no guide on how to go back to stock FW on a FTV1 once TWRP is install. This is due to the version of FW & TWRP that the FTV1's where first updated to FireOS 5. That was FW v5.0.5 & TWRP v6. So the TWRP had matured enough to fully block updates.
The only info regarding downgrading can be found in the TWRP thread. Folks that failed @ updating to TWRP correctly where able downgrade back to CWM. I think you also need to downgrade the FW to a PreRooted FireOS 3 too but I could be wrong. Once on CWM you should be able to allow updates since CWM won't block those updates.
Look/search for more info on the few folks that where able to go from TWRP to CWM here:
https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286
Also once your fully on CWM/FireOS 3 you might be able to use this guide to downgrade too:
http://www.aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/
All of the above is theory for me. Since I've never had to dealt with this. And there are no guides for this specific scenario. So make sure you look thru the TWRP thread to find the folks that actually mention going back to CWM. Although most of them did so just to reflash TWRP.
Search example: https://forum.xda-developers.com/search/thread/3383286?query=back to cwm
Note 1: As of 16.5.0, Android lollipop (API 21) is required
_____________________________________
16.5.0 (2016/11/30):
CHG: API 21+ (Android 5.0) only, sorry.
ADD: 4K on AFTV2
ADD: refresh rate sync on AFTV
ADD: DASH support (aka 1080p/4K youtube)
ADD: Builtin log (Settings-System-Logging-Upload…)
ADD: crash handler (no need for logcat)
ADD: rendercapture (boblight, Hue, …) support for Surface
FIX: Only stop Surface when really necessary
CHG: Revert to Surface as standard
ADD: acceleration setting for hevc
16.4.2 (2016/08/15):
REVERT: crash when enumerating sound devices during a refresh rate change
FIX: Missing start of video with large buffer
You will need to find SPMC v16.4.2 for FireOS 3.
You can find it from source here: https://github.com/koying/SPMC/releases?after=17.0b3-Krypton
Click to expand...
Click to collapse
thanks dl'd it.

Y314K said:
There is no guide on how to go back to stock FW on a FTV1 once TWRP is install. This is due to the version of FW & TWRP that the FTV1's where first updated to FireOS 5. That was FW v5.0.5 & TWRP v6. So the TWRP had matured enough to fully block updates.
The only info regarding downgrading can be found in the TWRP thread. Folks that failed @ updating to TWRP correctly where able downgrade back to CWM. I think you also need to downgrade the FW to a PreRooted FireOS 3 too but I could be wrong. Once on CWM you should be able to allow updates since CWM won't block those updates.
Look/search for more info on the few folks that where able to go from TWRP to CWM here:
https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286
Also once your fully on CWM/FireOS 3 you might be able to use this guide to downgrade too:
http://www.aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/
All of the above is theory for me. Since I've never had to dealt with this. And there are no guides for this specific scenario. So make sure you look thru the TWRP thread to find the folks that actually mention going back to CWM. Although most of them did so just to reflash TWRP.
----------------------------------------------------------------------------------------------------------------------------------------
It worked exactly as your theory described.
you can consider this the official intructions to revert back to stock.
I was able to flash CWM, Rbox boot manager and fireos 3 via TWRP
once I was fully on CWM/FireOS 3 I was able to push the the stock recovery via ADB then the updates downloaded automatically until I got to the latest version.
I also found out If you flash the old firmwares you can only register the device with a code from amazon that they send via email.
Click to expand...
Click to collapse

evaporic said:
It worked exactly as your theory described.
you can consider this the official intructions to revert back to stock.
I was able to flash CWM, Rbox boot manager and fireos 3 via TWRP
once I was fully on CWM/FireOS 3 I was able to push the the stock recovery via ADB then the updates downloaded automatically until I got to the latest version.
I also found out If you flash the old firmwares you can only register the device with a code from amazon that they send via email.
Click to expand...
Click to collapse
Great, glad there is now tested method for this. :highfive:
Can you please be a bit more detail in your steps... Please fill in the blanks below. That way other folks don't have to guess.
My FTV1 started from PreRooted FW v________ & TWRP v___.
Use a Fat32 formatted USB Stick.
Download & add the following files to the USB Stick (Check hash's):
CWM Recovery 6.0.5.1.4a - (md5sum: 67b1a13b7bec645cb9291e80478d4635)
FireTV Boot Menu 1.0 - (md5sum: a8a3c28baafe43f354d92e6cc8b392d3)
FireTV 1 (bueller) Prerooted Stock Images [51.1.6.3_516012020] - (md5sum: fcf1a8ddf2f3bc93280af03dcf408ac8)
Connected a USB Keyboard & boot to TWRP recovery.
First wipe __________. (None if you didn't wipe anything first)
Using TWRP flash ____________________.
_________________________________________.
Please provide as much detail as possible. Thanks

Android 12 Developer Preview

Developer Preview is up if anybody wants to try it
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com

Holy Moly.

Side loaded OTA via ADB all works fine no issues so far no FC can't say much difference

DoobyDroid said:
Side loaded OTA via ADB all works fine no issues so far no FC can't say much difference
Click to expand...
Click to collapse
Seems like for now, most UI and user facing changes in general are hidden behind flags, this one is meant for the devs, so it's to be expected. The beta, on the other end, will be aimed at users, and then we will see what changes

I upgraded last night. Had to reboot twice after restart. Then everything was stable. First time it rebooted after install, nothing seemed to want to work and kept FCing. Second reboot, everything is fine now. Sometimes, Nova needs to be indicated when I press the home button that it's default, otherwise, everything is working fine.
Is it me or does the Android version still say 11 but the build is "S"?

I downloaded the 12 DP1... and it just isn't ready yet (understandably so) for the daily driver use I need.f
Rooting it requires disable verity and verification. You'll need magisk 23 or canary to patch boot.img as well. Not disabling verity/verification, it will only boot back into fastboot and list the reason as something like, "unable to load boot image".
Once rooted, I moved on to installing edxposed --- using riru, riru edxposed, and edxposed manager. Everything installs without problems. Final reboot, and reboots as normal. But then about 90 seconds later, you'll start getting FC after FC after FC. All apps too, and background apps, and systemui, etc.
Removing the riru components and edxposed manager, doesn't correct this problem.
Did fresh format and reinstall of the DP1... rooted again... and then tried Viper4Android. I use a very simple version. You just flash it, and its done (no manual driver install either). Rather than the 3 reboot, AML, driver install, etc.
V4A installs with good logs. Reboots without a hitch. But I noticed the v4a icon in the status bar is missing. I open it up manually, and start getting freezes and fc's. Within 5 minutes, I get kernel panic reboots -- and non-bootloop freezes on the working G screen.
Reboot manually with long press power, get it loaded back up and immediately remove V4A. Reboot and now I'm back to stock.
Get FC's every hour or two. Random reboots too. Battery life is struggling.
I decided to wait until a better version drops, perhaps the beta or at least a DP2.5 or 3.0. As of right now, having Android S is mostly just a status thing -- to show people how cool we are to have access to it as such an early stage. But unless you are dedicated to helping improve the ROM through daily use and reporting... I highly recommend that you stick with Android R.

Just flashed the 1st public android 12 beta bramble-ota-spb1.210331.013-3c294b13.zip with adb sideload. Listed as android S atm, surprised 5G was enabled as this wasn`t the case with android 11 in the Netherlands. All apps working fine so far and still finding out the new stuff.

Has anyone been able to root the Pixel 4a 5G with Android 12 Beta 1?.
Kindly share the steps.

ekowwillis said:
Has anyone been able to root the Pixel 4a 5G with Android 12 Beta 1?.
Kindly share the steps.
Click to expand...
Click to collapse
yep i also like to know..tried twice but ended up in fastboot mode and cant get it to boot.i used the old magisk patched method but i probebly missing something

galza said:
yep i also like to know..tried twice but ended up in fastboot mode and cant get it to boot.i used the old magisk patched method but i probebly missing something
Click to expand...
Click to collapse
Clean wipe and follow the OP instructions in this Pixel 5 thread. Make sure you use the images for 4a5g where needed
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com