Just read this german article where they are saying what I put in the title.
Source: https://www.notebookcheck.com/Amazo...ate-auf-Fire-OS-7-und-Android-9.482412.0.html
This isn't new. The newer Hd10 and hd8 are both Android 9
Michajin said:
This isn't new. The newer Hd10 and hd8 are both Android 9
Click to expand...
Click to collapse
The claim is prior gen variants of 7" and 8" models (eg: 2018 HD8) will see an OTA upgrade to FireOS 7.
Last time Amazon attempted an OTA FireOS upgrade (vs update) was with the 3rd gen HDX line (FireOS v3 -> v4); lots of bricked devices in that debacle.
Seen these reports before. I have my doubts.
DB126 said:
The claim is prior gen variants of 7" and 8" models (eg: 2018 HD8) will see an OTA upgrade to FireOS 7.
Last time Amazon attempted an OTA FireOS upgrade (vs update) was with the 3rd gen HDX line (FireOS v3 -> v4); lots of bricked devices in that debacle.
Seen these reports before. I have my doubts.
Click to expand...
Click to collapse
According to the Amazon developer site it is happening: https://developer.amazon.com/docs/fire-tablets/ft-identifying-tablet-devices.html. We'll have to wait and see, but this should be possible without re-partitioning the device. The bogus upgrade of some tablets from Fire OS 5 to 6 would have required a much larger system partition.
Hopefully it will be possible to upgrade and keep an unlocked bootloader and TWRP.
MontysEvilTwin said:
According to the Amazon developer site it is happening: https://developer.amazon.com/docs/fire-tablets/ft-identifying-tablet-devices.html. We'll have to wait and see, but this should be possible without re-partitioning the device. The bogus upgrade of some tablets from Fire OS 5 to 6 would have required a much larger system partition.
Hopefully it will be possible to upgrade and keep an unlocked bootloader and TWRP.
Click to expand...
Click to collapse
Wow, nice! Might be useful for the developers for the lineage roms of the fire 7 (2019) and fire 8 (2018).
hope no one is waiting for an OS update on older devices...
the original promised date of 7/28 comes n goes...all we get from Amazon is that now it says:
"Will uplevel from Fire OS 6 to Fire OS 7 at a future time."
newnewcomputer said:
the original promised date of 7/28 comes n goes...all we get from Amazon is that now it says:
"Will uplevel from Fire OS 6 to Fire OS 7 at a future time."
Click to expand...
Click to collapse
I just noticed that, too. Blame it on Covid-19. People working from home not getting it done fast enough.
If this gets me stock Android on my hd10 2019 I care if not , what does it really matter what it runs on ... The functionality is still limitedly the same ...
olaf2k4 said:
If this gets me stock Android on my hd10 2019 I care if not , what does it really matter what it runs on ... The functionality is still limitedly the same ...
Click to expand...
Click to collapse
It probably won’t help on your 2019 HD10, as it already has FireOS based on Android 9. This update will bring the Pie-based FireOS to older devices.
Seems to be no planned update for the Fire HD 10 7th Gen although it has similar hardware as the Fire HD 8 8th Gen. It will stuck on FireOS 5 which is based on Android 5 and which is already out of support. Shame on you Amazon!
BeniS98 said:
Seems to be no planned update for the Fire HD 10 7th Gen although it has similar hardware as the Fire HD 8 8th Gen. It will stuck on FireOS 5 which is based on Android 5 and which is already out of support. Shame on you Amazon!
Click to expand...
Click to collapse
Not at all. Amazon never promised major firmware (version) updates. Similar and identical are not the same thing.
Any expectation of investment in a 3 year old budget platform is pure fantasy.
Fire OS 7.3.1.5 is now avaliable for download for the Karnak (HD 8, 2018) and Mustang (7, 2019) tablets on the Amazon software download page.
I tried to flash the new version through TWRP. To be on the safe side, as when I updated to OS 6.3.1.5 through TWRP my recovery was overwritten, I edited the updater script. Flashing seemed to go OK (I re-flashed Magisk afterwards) but it bootlooped on the Amazon logo after rebooting. I could not even turn the tablet off by holding down the power button. I opened the case, disconnected the battery and booted into TWRP recovery after reconnecting. I then wiped and restored the backup I made just before flashing. The tablet is working fine again but I now have a vendor partition. I hope will be possible to keep an unlocked bootloader/ TWRP and upgrade to OS 7/ Pie.
My HD 8 is still mostly stock (just have Google's services and Play Store on it). So I downloaded the OS, and it's installing on its own right now.
It's a wait-and-see as to what it does. I know the UI is the same, but there are some notifications that the thing just would not show. I'm hoping this will work better.
MontysEvilTwin said:
I tried to flash the new version through TWRP... but it bootlooped on the Amazon logo after rebooting... I hope will be possible to keep an unlocked bootloader/ TWRP and upgrade to OS 7/ Pie.
Click to expand...
Click to collapse
thank you 4 trying n report! i dl the bin file but was too chicken to flash. i guess for a major update like this, Amazon may have to re-write the recovery, bootloader n everything else but my tin-foil hat is saying otherwise :laugh:
Pie will be nice on the HD8 but im not giving up TWRP or BL unlock 4 it!
It would be good to know if anyone has got this to work. After getting a bootloop with the modified updater script, I flashed the original update, on its own and with GAPPS (arm 9.0 nano) and Magisk (20.4). There were no error messages in either case, but the same bootloop. I tried an adb sideload with the same result. I also used amonet to flash the OS 7.3.1.5 preloader and TZ files. This alone is enough to bootloop. I have not tried flashing the new LK but this would probably cause problems with the unlock as the necessary LK exploit is likely to have been blocked (it has been with OS 6 since version 6.3.0.1).
Hopefully if you have a stock tablet and the update downloads and installs this will proceed correctly and the upgrade problems are caused by some incompatibility with the unlock exploit. If not there are going to be a lot of bricked tablets out there.
Mine updated just fine from stock setup. Even the added Google stuff still worked.
However, running through all the settings, I went to the factory reset page. As I was bringing my finger over to hit cancel, I was apparently too close to the screen, and it picked up the OK button instead. Did not know it would be THAT easy. It started wiping, and there was no stopping.
It did give me a chance to redo everything. Used the Fire Toolbox to install the Google Play stuff this time (manually did it before). That worked well.
Maybe it was the reset, but the whole UI seems a little smoother. Also, after a full day, the battery seems to be lasting longer than I expected given all the re-downloading and setting up I've been doing.
joeldf said:
My HD 8 is still mostly stock (just have Google's services and Play Store on it). So I downloaded the OS, and it's installing on its own right now.
It's a wait-and-see as to what it does. I know the UI is the same, but there are some notifications that the thing just would not show. I'm hoping this will work better.
Click to expand...
Click to collapse
@joeldf - plz let us know if ur stock update to fire OS 7 works out okay. seems like it wont work w/ unlocked bootloader which would turn a lot of ppl away from install.
MontysEvilTwin said:
It would be good to know if anyone has got this to work...
Hopefully if you have a stock tablet and the update downloads and installs this will proceed correctly and the upgrade problems are caused by some incompatibility with the unlock exploit. If not there are going to be a lot of bricked tablets out there.
Click to expand...
Click to collapse
it is a good free major upgrade (a first for any fire device in recent years). i use fire OS 7 on my HD10 2019 n it is better than OS 5 n 6. u would think that it works out-of-box for a stock tablet but i remember reading about the last time Amazon did it, there WERE a lot of bricked tablets out there
thanx again for ur tests! i will pass on this update. hopefully someone can extract some useful things from this Pie release for the LOS 16 custom ROM.
edit: @joeldf - thanks for the update! so the update works for stock ROM. since factory reset gave the same ROM, the update did rewrite the recovery. basically will have to give up BL unlock, TWRP n root for the OS 7 update. u MAY get 'em back by opening up the tablet (im not up-to-date on unlocking latest OS.) For me, I will pass.
Looks like there is a kernel patch required. It's possible the new TZ can work with the old LK, where the unlock sits. If you have yours open to do amonet, try replacing TZ as well! You can recover via contact shorting.
The
MontysEvilTwin said:
It would be good to know if anyone has got this to work. After getting a bootloop with the modified updater script, I flashed the original update, on its own and with GAPPS (arm 9.0 nano) and Magisk (20.4). There were no error messages in either case, but the same bootloop. I tried an adb sideload with the same result. I also used amonet to flash the OS 7.3.1.5 preloader and TZ files. This alone is enough to bootloop. I have not tried flashing the new LK but this would probably cause problems with the unlock as the necessary LK exploit is likely to have been blocked (it has been with OS 6 since version 6.3.0.1).
Hopefully if you have a stock tablet and the update downloads and installs this will proceed correctly and the upgrade problems are caused by some incompatibility with the unlock exploit. If not there are going to be a lot of bricked tablets out there.
Click to expand...
Click to collapse
bibikalka said:
Looks like there is a kernel patch required. It's possible the new TZ can work with the old LK, where the unlock sits. If you have yours open to do amonet, try replacing TZ as well! You can recover via contact shorting.
The
Click to expand...
Click to collapse
I am having problems getting this version working at all. I tried downgrading the version of TWRP and flashed the new software with a modified updater script (to change the paths and make it work with this TWRP version). This also overwrites the PL, TZ and LK plus recovery. I didn't get a bootloop but it would not progress past the Amazon logo screen on boot.
Related
When Android 7.0 ( Nougat ) is finally released for Motorola X Pure (2015) XT1575 ( Hopefully by the end of the year ), will SystemLess Root still work as is it does now for 6.0 or should we wait for someone to run it in a sandbox? Should we wait for the First Quarter of 2017 before we get anxious and upgrade to the newest Android, to give all of the developer time to perfect they're processes.
We all know now that it will be released as a STOCK image, but I have a lot of Root Apps (i.e. Titainium, Backup, Root Explorer, Xposed, Gravity Box for MM, etc) which I would still like to use. From what I can see of 7.0 it's not much different than 6.0 except for split screen and some other features that I'm sure we.re not aware of yet..
All I can say it It doesn't work on the G4... yet. I maintain a root thread on the G4, haven't found a viable way to root it on Nougat, all methods mess up data and a bunch of framework stuff (like settings menu). I assume the Nougat on this will be roughly the same. Don't worry, it will come though.
And Xposed isn't available for Nougat, it isn't known yet if it will be. Remember when Marshmallow came out they almost dropped Xposed completely, they were so close they had actually said they shutting down development of Xposed then had a unexpected breakthrough. The developers of Xposed have said that it will die in the hear future due to changes in Android.
Yeah, xPosed isn't something I would rely on moving forward. Right now AICP & CM are making great strides with N 7.1 and including Root so you can go that route and get the Root you desire. I'm on TurboROM which is still an MM base and will move to AICP N 7.1 once things settle in some more, but as of right now AICP is pretty darn nice as is. I've tested it every few days to see the progress, but for daily, revert to my most current backup of Turbo for now. AICP usually includes a LARGE amount of customizations. I go that route normally and remove all the AOSP stuff I can replace with Google APPs directly and use Moto Camera instead as well giving me a really clean and functional bug-free experience. GravityBox becomes mostly unnecessary with AICP or CM. Boy I'm rambling worse than normal today...
Back on track... Try out AICP with N 7.1 or wait for a Stock Rooted
Thank you for the reply, I wasn't sure if I should upgrade or not.
My pure has been running pretty good since I got it back in May of this year thru SWAPPA, and I have the latest security mod for May 1 (Build MPHS24.49-18-4), I wasn't sure if Lenovo would push another Security update for 6.0 (MM) or push 7.0 for the next update, and I didn't want to mess anything up..
I love this phone, and I'm not sure if and when I will upgrade, but I know it won't be MOTO/LENOVO anymore, unless they can unlock the bootloader for Pixel and gain root, I may lean that way...
NEVER, NEVER, Never will I go the way of the Apple, anything that comes from that place sucks, it's too restrictive..
DROID Forever !!!!!
CLETjB said:
Thank you for the reply, I wasn't sure if I should upgrade or not.
My pure has been running pretty good since I got it back in May of this year thru SWAPPA, and I have the latest security mod for May 1 (Build MPHS24.49-18-4), I wasn't sure if Lenovo would push another Security update for 6.0 (MM) or push 7.0 for the next update, and I didn't want to mess anything up..
I love this phone, and I'm not sure if and when I will upgrade, but I know it won't be MOTO/LENOVO anymore, unless they can unlock the bootloader for Pixel and gain root, I may lean that way...
NEVER, NEVER, Never will I go the way of the Apple, anything that comes from that place sucks, it's too restrictive..
DROID Forever !!!!!
Click to expand...
Click to collapse
Pixel bootloader is unlockable. Verizon Pixel has bootloader unlock tool from the Sunshine team free of charge. Also It is rootable via newest SuperSU beta I believe.
I have been unsuccessful at rooting stock nougat, it just gets stuck on the boot animation forever and the battery heats up.
So, has anyone rooted it on nougat 7.0 and how?
Every time I try it just gets stuck loading and since I can't logcat to it I have no idea where its failing, but fastboot flashing the system image and the boot image fixes it, but then I am stuck back at non-root.
I know there has to be a way as many others say they are rooted just fine so I must be missing something.
I have several apps that use root and do system tweaks that would be helpful, mostly battery saving, option enabling, etc... But I can't use any of them for now. I especially wanted to use the undervolt and system governers min max settings.
roadrun777 said:
I have been unsuccessful at rooting stock nougat, it just gets stuck on the boot animation forever and the battery heats up.
So, has anyone rooted it on nougat 7.0 and how?
Every time I try it just gets stuck loading and since I can't logcat to it I have no idea where its failing, but fastboot flashing the system image and the boot image fixes it, but then I am stuck back at non-root.
I know there has to be a way as many others say they are rooted just fine so I must be missing something.
I have several apps that use root and do system tweaks that would be helpful, mostly battery saving, option enabling, etc... But I can't use any of them for now. I especially wanted to use the undervolt and system governers min max settings.
Click to expand...
Click to collapse
Yes, lots of people have rooted it... latest TWRP and Magisk, nothing special to do at all... Flash or boot TWRP and flash Magisk zip file, reboot and go.
Unlocked bootloader must have.
1st method:
Boot twrp - fastboot boot twrp3x.img
Do full backup,
Restore boot only,
In twrp install magisk14.zip, optionally wipe cache+dalvik, reboot.
2nd method
...the same steps,
Twrp terminal - type + ok:
echo SYSTEMLESS=true>>/data/.supersu
Install SuperSu2.82.zip, opt.wipe..., reboot.
Both method works.
I finally find magisk and it worked first time for me.
I tried SuperSU about 10 times in a row, systemless false, systemless true, etc, without it, and it always ended the same way boot loops.
So I am not sure that SuperSu2.82.zip is currently compatible with nougat, or at least with nougat + xt1565 hardware.
roadrun777 said:
...
So I am not sure that SuperSu2.82.zip is currently compatible with nougat, or at least with nougat + xt1565 hardware.
Click to expand...
Click to collapse
I wrote here(#8):
1st December 2017, 02:11 PM,
Here:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
30. November, 2017...rooted 29.
SuSu 2.82 is compatible.
Magisk Framework comes with SuperUser built in.. so when you flash another superuser, you mixing Binaries and it doesn't know which one to use.
As we all know there is a point during setup where you put in your google account and it asks to restore from a phone or start fresh. When I got to that part, there were no backups to restore from. I confirmed that my Essential Phone and my Pixel XL backup were still present on my drive. Then after the setup was complete, I noticed that there wasn't Android 8.1 on the Premium, despite having the April security update. Being impatient, I looked it up and I saw that 8.1 was available and out for OTA. Since I don't have a carrier-locked device, theoretically I could receive all updates as they roll out from Sony. I thought since my backups were from an 8.1 device, they were incompatible to downgrade to 8.0. Still being impatient, I looked over XDA and found that Unlocking the bootloader and loading a custom ROM would be fine, but that's where I ran into issues.
Half of the threads that supported G8412 (Dual Sim) were either edited to "working" or out-of-date or closed by a moderator (I downloaded the Turbo mod before it was deleted, and I only discovered it was deleted when I logged on to thank him).
TL;DR:
-Unlocked my bootloader, which turned out to be a terrible mistake on my part
-Cant seem to find a stable ROM (the flash-and-forget kind) that supports my model
-Apparently now the camera is broken and unusable on most ROMs?
-Can't migrate any of my data due to a (theoretical) Android 8.1/8.0 clash
Anything I am missing on the forum would be appreciated. I've looked at Storm's thread (closed), Turbo's thread (closed), Snappatch (DRM Fix required). It seems like a lot of ROMs that are still active require the DRM fix by Storm except for the Carbon ROM. So, any suggestions as to what to do going forward? Is there something I am missing?
(Edit: upon reading, this looked more like a blog post so I cut it down)
I'm personally using the official CarbonROM 8.1 on my G8142. Been running it for a few weeks and it's pretty stable.
Thunder_47 said:
As we all know there is a point during setup where you put in your google account and it asks to restore from a phone or start fresh. When I got to that part, there were no backups to restore from. I confirmed that my Essential Phone and my Pixel XL backup were still present on my drive. Then after the setup was complete, I noticed that there wasn't Android 8.1 on the Premium, despite having the April security update. Being impatient, I looked it up and I saw that 8.1 was available and out for OTA. Since I don't have a carrier-locked device, theoretically I could receive all updates as they roll out from Sony. I thought since my backups were from an 8.1 device, they were incompatible to downgrade to 8.0. Still being impatient, I looked over XDA and found that Unlocking the bootloader and loading a custom ROM would be fine, but that's where I ran into issues.
Half of the threads that supported G8412 (Dual Sim) were either edited to "working" or out-of-date or closed by a moderator (I downloaded the Turbo mod before it was deleted, and I only discovered it was deleted when I logged on to thank him).
TL;DR:
-Unlocked my bootloader, which turned out to be a terrible mistake on my part
-Cant seem to find a stable ROM (the flash-and-forget kind) that supports my model
-Apparently now the camera is broken and unusable on most ROMs?
-Can't migrate any of my data due to a (theoretical) Android 8.1/8.0 clash
Anything I am missing on the forum would be appreciated. I've looked at Storm's thread (closed), Turbo's thread (closed), Snappatch (DRM Fix required). It seems like a lot of ROMs that are still active require the DRM fix by Storm except for the Carbon ROM. So, any suggestions as to what to do going forward? Is there something I am missing?
(Edit: upon reading, this looked more like a blog post so I cut it down)
Click to expand...
Click to collapse
i think turbo said he might bring it back he is just away right now(work)
also for camera you can go here https://forum.xda-developers.com/xz-premium/how-to/xz-premium-145-twrp-root-fix-t3783036 and download the drm fix.
blweldon2 said:
I'm personally using the official CarbonROM 8.1 on my G8142. Been running it for a few weeks and it's pretty stable.
Click to expand...
Click to collapse
Does the CarbonROM require any upkeep? I see it says "Weeklys" in it's title, so for the uneducated, does that mean it is updated Weekly with new features/fixes?
raven213 said:
i think turbo said he might bring it back he is just away right now(work)
also for camera you can go here https://forum.xda-developers.com/xz-premium/how-to/xz-premium-145-twrp-root-fix-t3783036 and download the drm fix.
Click to expand...
Click to collapse
I did get the firmware that is .145, and I do have a DRM fix currently, however I do not remember where I got it from. I wish Turbo the best of luck in bringing back his work and collab with that other guy.
Update
After a bit of research, I did find that getting the 8.1 Carbon Rom with the AOSP upgrade below would be best. As seems like the current trend where some users report successes and others report failures and there really isn't an "in-between" of a particular combination, this one seems to have the most credibility as of May 8. Carbon Rom's thread hasn't been active for about a month, however and the author behind the Snappatch upgrades seems to have left XDA..
Any other users that have Android 8.1 have anything else to say/suggest?
Carbon Rom:
https://forum.xda-developers.com/xz-premium/development/8-1-x-carbonrom-cr-6-1-t3771540
AOSP Upgrade (Snappatch)
https://forum.xda-developers.com/crossdevice-dev/sony/pom-snappatch-xperia-aosp-t3777322
blweldon2 said:
I'm personally using the official CarbonROM 8.1 on my G8142. Been running it for a few weeks and it's pretty stable.
Click to expand...
Click to collapse
How did you do to flash it when I do it it's stock at Sony logo
SilverGamer_YT said:
How did you do to flash it when I do it it's stock at Sony logo
Click to expand...
Click to collapse
Make sure you flash the AOSP userdata image. Can obtain it by compiling from source or grabbing it from one of the AOSP roms compiled from source. Just flash it in fastboot and then flash the rom in TWRP. Only need to flash userdata once.
THREAD UPDATED 4/22/19
So I started having pre-flash errors, boot looping, and bricked modem problems from just flashing the modems so I decided to upload the entire stock firmware for Nougat and Marshmallow. It's the same process but you have to flash the entire firmware then flash TWRP to use custom roms. Just click the FLASH-ALL.bat in the Nougat or Marshmallow folder and it will flash the firmware automatically and reboot. If you have any issues please report it here. I also included TWRP and the stock boot images all in one package just go into the folder and hit FLASH-ALL.bat. Everything is automated no more looking for firmware and flashing manually.
Link 1:
https://mega.nz/#!K1o0XIDS!taCkfjVbWunmkEOFVrqUaFeTLEQZ-JQACqO2EpebnAo
Queston - just got done replacing the LCD-Digitizer and battery (Moto X Pure XT1575) with the iFixit repair kit and got it up and running again (cracked the display in an auto accident and never had time to fix it until now)- while it was out of service I've been using a Moto G Play XT1607 as a backup for the last couple years... anyway now that it's working again I ran the factory reset and checked the Android version and it's at 6.0 (MarshMellow?) ... am a novice and wondering if it should upgrade at least to 7.0 (Nougat) eventually, in a day or so(?) when it synchronizes somehow - or if i should go ahead and do it manually myself ... and/or if manually updated go straight to whatever the current version is (Oreo 8 or Pie 9) ... If this is the right place, I may need some pointers getting started in the right direction ... In comparison the Moto G Play is at 7.1.1 ...any suggestions?
jabberjaw007 said:
Queston - just got done replacing the LCD-Digitizer and battery (Moto X Pure XT1575) with the iFixit repair kit and got it up and running again (cracked the display in an auto accident and never had time to fix it until now)- while it was out of service I've been using a Moto G Play XT1607 as a backup for the last couple years... anyway now that it's working again I ran the factory reset and checked the Android version and it's at 6.0 (MarshMellow?) ... am a novice and wondering if it should upgrade at least to 7.0 (Nougat) eventually, in a day or so(?) when it synchronizes somehow - or if i should go ahead and do it manually myself ... and/or if manually updated go straight to whatever the current version is (Oreo 8 or Pie 9) ... If this is the right place, I may need some pointers getting started in the right direction ... In comparison the Moto G Play is at 7.1.1 ...any suggestions?
Click to expand...
Click to collapse
If you want stock Nougat go ahead and update to it but I had battery drain issues on the Nougat modem from personal experience. If you decide to update you can use this thread and downgrade to stock 6.0.
Hi, I downloaded the Nougat and tried the command "Flash-all.bat" while in windows 10 ( I have the device booted up in bootloader mode. ) nothing happens. The screen flashes something too quick for me to see what it is. I must be doing something dumb. Do I need to go into command mode to do this "Flash-all.bat" or can I do it in the windows screen ?
AndroidMilos said:
Hi, I downloaded the Nougat and tried the command "Flash-all.bat" while in windows 10 ( I have the device booted up in bootloader mode. ) nothing happens. The screen flashes something too quick for me to see what it is. I must be doing something dumb. Do I need to go into command mode to do this "Flash-all.bat" or can I do it in the windows screen ?
Click to expand...
Click to collapse
Okay if the terminal window flashes really fast and you can't read it that usually means it can't write to the phone. Either your bootloader isn't unlocked or your usb cable doesn't support data transfer. If that isn't the issue make sure you install Motorola device manager and the adb fastboot sdk drivers which can be found on XDA. More than likely you're getting a remote failure error I have this problem myself a lot on Windows 10.
Thank you for your reply. I will follow through with the info you gave me.
I no longer own this device so I will no longer participate in any Moto X Pure threads. FYI if you flash the Nougat firmware in this thread you have to OTA to the final update for Nougat ROMs to work.
HD8 2018 6.3.1.5 (and 6.3.1.4) issues
HD8 2018 OS continues to present never ending issues (seems like a poorly supported product compared to the earlier Fires ...)
I flashed 6.3.1.5 (6.3.1.4) on top of 6.3.1.2 via TWRP (+Magisk/systemless Xposed), and, ended up with a weird WiFi crashloop that took a few tries to understand. Essentially, the moment it connects to a WiFi network, it reboots. If I set WiFi to off, it's stable (have to do it quick before it connects after a reboot!). If I disable Xposed module, it's stable. Neither Xposed 89.3 or 90beta work correctly.
On 6.3.1.2 Xposed worked more or less OK.
I tried to downgrade back to OS 6.3.1.2 or 6.3.0.1, but apparently the settings are not compatible once you load 6.3.1.4 on it. It never reaches the launcher, and keeps sitting at Fire screen. I could not even boot 6.3.1.2 or 6.3.0.1 without Magisk. Doing a factory reset was not in my plan yet. So I had to go to 6.3.1.4 again where it booted fine. I now run 6.3.1.4 with Xposed disabled.
Anybody has 6.3.1.4 with Xposed & WiFi working properly out there? I wonder if this is also a similar issue with Fire 7 2019 (mustang) - @Michajin
HD10 2017 40.6.5.0_user_650601220 issues
Well, what do you know ... I finally took the plunge to do the unlock and install TWRP on my Kingoroot rooted HD10 2017 (thanks @k4y0z !). I backed up all the apps via Titanium Backup, and then backed up the internal sdcard via Total Commander to a zip, which later nicely restores things back with the proper timestamps (yay!). It's very difficult to restore timestamps, but Total Commander with root can do it.
In my optimism, after getting TWRP, I immediately installed the latest FireOS, 40.6.5.0_user_650601220, with Magisk, and Xposed installed into system (xposed-v89-sdk22-arm64.zip). And, just like HD8 2018, the moment I activated Xposed modules, the tablet started rebooting when WiFi was on. If I managed to hit WiFi off button before it did so, it seemed stable. So both HD10 2017 and HD8 2018 appear to have the same Xposed bug in the latest FireOS versions!!! I wonder if it's related to the fix of MTK-SU issue.
I also ran into Google Play & battery drain issues. Tired of several attempts of troubleshooting, I actually ended up backtracking all the way to 40.6.2.6_user_626533320, which is the version I started with. Once Google Play went south after my 1st restore, I could not fix it over multiple tries, and I had to do a Factory reset again and restore apps via Titanium Backup a bit more carefully, starting with the latest versions of Google Play apps without data (rather than just all at once). Now everything appears to be working as before, with TWRP, and the same old FireOS version that I already had
The battery drain issue was an interesting one, apparently, Vanced Youtube helper app, microg_YouTube_Vanced_0.2.6.17455, creates a lot of battery drain via needless Wakelocks, which can be fixed by running the following commands:
Code:
adb shell
su
pm disable com.mgoogle.android.gms/org.microg.gms.people.ContactSyncService
P.S. A week ago I unlocked HD8 2017 (OS version 50.6.3.6_user_636558520), and successfully cloned HD8 2016 to this 2017 via TiBa & Total Commander. That attempt went without a glitch, and that's why I thought I could also do HD10 in no time, but HD10 gave me all kinds of issues.
bibikalka said:
HD8 2018 OS continues to present never ending issues (seems like a poorly supported product compared to the earlier Fires ...)
I flashed 6.3.1.4 on top of 6.3.1.2 via TWRP (+Magisk/systemless Xposed), and, ended up with a weird WiFi crashloop that took a few tries to understand. Essentially, the moment it connects to a WiFi network, it reboots. If I set WiFi to off, it's stable (have to do it quick before it connects after a reboot!). If I disable Xposed module, it's stable. Neither Xposed 89.3 or 90beta work correctly.
On 6.3.1.2 Xposed worked more or less OK.
I tried to downgrade back to OS 6.3.1.2 or 6.3.0.1, but apparently the settings are not compatible once you load 6.3.1.4 on it. It never reaches the launcher, and keeps sitting at Fire screen. I could not even boot 6.3.1.2 or 6.3.0.1 without Magisk. Doing a factory reset was not in my plan yet. So I had to go to 6.3.1.4 again where it booted fine. I now run 6.3.1.4 with Xposed disabled.
Anybody has 6.3.1.4 with Xposed & WiFi working properly out there? I wonder if this is also a similar issue with Fire 7 2019 (mustang) - @Michajin
Click to expand...
Click to collapse
you will have to refresh me where i had on the mustang. I am using los 16.0 on the hd8, dont really have a need for xposed. Seems like i had this on the mustang right after root when on stock? i will look into it and try and refresh myself if you cant point me into the thread...
Michajin said:
you will have to refresh me where i had on the mustang. I am using los 16.0 on the hd8, dont really have a need for xposed. Seems like i had this on the mustang right after root when on stock? i will look into it and try and refresh myself if you cant point me into the thread...
Click to expand...
Click to collapse
It was here :
https://forum.xda-developers.com/showpost.php?p=79841222&postcount=21
bibikalka said:
It was here :
https://forum.xda-developers.com/showpost.php?p=79841222&postcount=21
Click to expand...
Click to collapse
I am trying to remember but it seems i had to flash full xposed from TWRP. I think i had issues with the systemless version from magisk. I didn't know people would chose to run FIRE-OS once anything else was available (no offense) with 14.1 and 16, both being decent... lol
Michajin said:
I am trying to remember but it seems i had to flash full xposed from TWRP. I think i had issues with the systemless version from magisk. I didn't know people would chose to run FIRE-OS once anything else was available (no offense) with 14.1 and 16, both being decent... lol
Click to expand...
Click to collapse
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
The camera works on both 16.0 and 14.1. But 14.1 is by far more stable at this time. Bluetooth and headphones (plus more- see thread) issues on 16.0. The only issue on 14.1 is the headphone jack doesn't work (but i think someone has found a fix for it but it hasnt been updated in the rom). Backup in TWRP and install 14.1 and give it a shot, i am on 16.0. 14.1 was working really smooth. I have not tested skype on either. 14.1 seemed smoother and less buggy than fireOS right at Beta.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
Observation regarding custom ROMs is one reason I typically hang with 'stock' and tune to my liking. LOS 14.1 for this device/gen (and a few others) is an exception; worth considering. LOS 16.1 is less refined ATM with no meaningful advantage over 14.1.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
I needed to have headphones working, so I didn't try LOS 14 until recently. I'm extremely happy with it. It's so much snappier than stock for me, and videos load so much faster, like in Netflix, for example. I'm also using Magisk and Xposed with no issues.
I didn't realize the new build is up with fixes... Going back to 14.1, I think he is working on 17.0 (Kaijones23) 17.0 was updated last night....
https://github.com/mt8163/android_device_amazon_karnak/branches
Noob question - how do you flash lineage-16 or cm-14.1 onto the device? I downloaded the zip files from the link above, but they are way to small to be a complete rom. Is there a different location where I can download the roms?
xantiux said:
Noob question - how do you flash lineage-16 or cm-14.1 onto the device? I downloaded the zip files from the link above, but they are way to small to be a complete rom. Is there a different location where I can download the roms?
Click to expand...
Click to collapse
Have you unlocked the bootloader (prerequisite):
https://forum.xda-developers.com/hd...nlock-fire-hd-8-2018-karnak-amonet-3-t3963496
I have unlocked the bootloader, for which I had to open the tablet up in order to short a pin. I was able to load the FireOS 6.0.0.0 and 6.0.0.1, and was looking if there is a way to load 6.0.1.2 or 6.0.1.4, when I came upon this thread, and saw that it may be possible to load lineage or cm, but I don't know how to get my hands on the ROMs. The downloads from the links above are way too small.
xantiux said:
I have unlocked the bootloader, for which I had to open the tablet up in order to short a pin. I was able to load the FireOS 6.0.0.0 and 6.0.0.1, and was looking if there is a way to load 6.0.1.2 or 6.0.1.4, when I came upon this thread, and saw that it may be possible to load lineage or cm, but I don't know how to get my hands on the ROMs. The downloads from the links above are way too small.
Click to expand...
Click to collapse
This help?
https://forum.xda-developers.com/hd8-hd10/general/lineageos-14-1-fire-hd8-2018-t3936242
https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-16-0-t3981685
This is great, thank you!
Somewhat related question - is it hard to get a zip of fireOS 6.3.1.2, so it can be flashed via TWRP?
xantiux said:
This is great, thank you!
Somewhat related question - is it hard to get a zip of fireOS 6.3.1.2, so it can be flashed via TWRP?
Click to expand...
Click to collapse
Supposedly renaming .bin to .zip allows flashing from twrp. I'd be wary of other partitions such as recovery and aboot which could trigger a bad day.
Headphone fix for LOS 14 has been applied in the latest version of the ROM. If you don't feel like reflashing entire ROM, there is a flashable zip containing only the headphone fix (module). I don't have the links handy but it's all available on this forum.
Updated post #1 and described HD10 '17 Xposed WiFi crashloop as well.
Updated with the same HD8 2018 6.3.1.5 WiFi/Xposed issue.
bibikalka said:
Updated with the same HD8 2018 6.3.1.5 WiFi/Xposed issue.
Click to expand...
Click to collapse
Welcome back!
Hi
I have an original Shield Tablet, When Nvidia recalled the tablets I got a new tablet but kept the old one, At first I didn't use the new one, I only used the old one because I thought that if I used the new one the old one might trigger the Kil switch from Nvidia. One day the tablet simply stopped working, I was able to load into recovery mode/menu and do a factory reset but no luck, I don't remember if it was stuck at a black screen or stuck on the Nvidia logo but was one of those.
So after that I just stored the tablet and started using the new one that Nvidia sent me.
It's been a few years since that and the new tablet got stolen a couple years ago and today just out of curiosity I charged the old tablet and IT WORKED!. It booted up. It has the factory reset that I did.
So now I would like to use that tablet but I really don't know how to procced. Is it safe now to update the tablet? Nvidia still delivers the killswitch? what can I do to keep using the tablet without having to worry about some kind of auto update?
The tablet is at Android 7.0
with Shield tablet software version 5.2(24.29.404.153)
I would really appreciate the help. thanks!.
Hi
When your Tablet is really on the Killswitch List which it must be when you get a new one
(you can check it here to be sure : http://shield.bogdacutu.me) you have to avoid turn on Wifi and install a Custom Rom first. Which one depends how you want to use the Tablet. If you want it snappy and stable you should go with Unofficial Lineage OS 14.1 Rom from Saint2k which you found here : https://forum.xda-developers.com/sh...om-lineageos-14-1-15-1-shield-tablet-t3950786
Its based on Android 7.1.2 and everything works well except the Nvidia Games App (Geforce Now) because it doesnt connect to the nvidia server and loggin is not possible.
He also offers a Lineage OS 15.1 which is based on Android 8.1 . But as i know there is still a Issue with the Hardware Acceleration.
The AOSPExtended 5.8 Rom from Triodexe is also based on Android 8.1 and has working HW Acceleration. But also Nvidia Games App doesnt work ( You can start it and log in but it crashes when you start a Game)
His AOSPExtended 6.7 Rom is based on Android 9 and should work with the Nvidia Games App but i didnt tested it already.
Now we come to the Battery it is Highly recommend to change out the faulty Battery first because Nvidia Recalled those Batteries for a Reason. How you do it you can see here : https://forum.xda-developers.com/shield-tablet/help/replacement-battery-2018-t3788666
I also did it last week on one of my Tablets and its not too hard if you have access to a solderiron.
I hope this was helpfull and dont hesitate to ask if you have more questions.
I'm in the same boat. accept my tablet has been on and i can get on it still I have verified it has the y01 battery. it was purchased off ebay and hasn't been updated. not sure what the person did to prevent it from being bricked but I would like to put lineage or AOSPExtended 6.7 Rom on it. I'm not sure where to start. can someone point me in the right direction? btw the bootloader is unlocked and its currently running android 7.0. my son used it for the last year to watch youtube and what not on. the first instructions to AOSPExtended 6.7 Rom says to update to the newest firmware and I'm afraid that will brick it. any help is appreciated in advance.
dohcdragon said:
I'm in the same boat. accept my tablet has been on and i can get on it still I have verified it has the y01 battery. it was purchased off ebay and hasn't been updated. not sure what the person did to prevent it from being bricked but I would like to put lineage or AOSPExtended 6.7 Rom on it. I'm not sure where to start. can someone point me in the right direction? btw the bootloader is unlocked and its currently running android 7.0. my son used it for the last year to watch youtube and what not on. the first instructions to AOSPExtended 6.7 Rom says to update to the newest firmware and I'm afraid that will brick it. any help is appreciated in advance.
Click to expand...
Click to collapse
try installing anyway then, do not update