Has anyone tested the AOPP (Android Open Pwn Project) ROM for our Shields? I just came across it yesterday while catching up on the Pwnie Express site.
Link: https://wiki.pwnieexpress.com/index.php/Supported_Devices
Note: ROM is *not* for the K1 variant.
Would love to hear anyone's experience.
I was going to try building from source to get it to work on the K1, as from what I'm reading the hardware is essentially the same so there shouldn't be *too* many errors... Right?
Shield's in the mail, so I'll report back with results later. Will be super excited if it works.
equi_design said:
Has anyone tested the AOPP (Android Open Pwn Project) ROM for our Shields? I just came across it yesterday while catching up on the Pwnie Express site.
Link: https://wiki.pwnieexpress.com/index.php/Supported_Devices
Note: ROM is *not* for the K1 variant.
Would love to hear anyone's experience.
Click to expand...
Click to collapse
Seeing as how it hasn't been updated since August....
It's Alive!
Managed to get it up and running on the Shield Tablet K1, which I forsaw as it's the same hardware, minus one stylus.
However, I will say this - update the nVidia app/software before doing anything or you'll be stuck in a boot loop. It flashes the firmware to be compatible with the latest TWRP, which I found out after having to flash back to the 'fallback' base image from nVidia. Other than that, smooth sailing - though it does appear to have the 'random reboot' problem still, which I've seen a few people mention on the forums.
Now I just need some OTG cables and the fun can begin.
Question
c0rsana said:
Managed to get it up and running on the Shield Tablet K1, which I forsaw as it's the same hardware, minus one stylus.
However, I will say this - update the nVidia app/software before doing anything or you'll be stuck in a boot loop. It flashes the firmware to be compatible with the latest TWRP, which I found out after having to flash back to the 'fallback' base image from nVidia. Other than that, smooth sailing - though it does appear to have the 'random reboot' problem still, which I've seen a few people mention on the forums.
Now I just need some OTG cables and the fun can begin.
Click to expand...
Click to collapse
Are the random reboots that bad?
Also for a total newbie would you recommend this ROM?
It's ancient, why would anyone want to flash this?
Hi Folks.
I successfully updated my CM13 to Lineage OS 14.1 on my B01 Shield Tablet.
To get it to work though, I had to download the entire stock Nougat package (almost 3 gigs).
I ran through the steps and installed a fresh Stock Nougat. Once that was complete, I was able to flash Unofficial Lineage OS 14.1.
However I don't want to do the same thing on my Y01 tablet, as I fear the serial will be blacklisted and the unit will get bricked.
I'm assuming it is possible to upgrade to the Lineage OS on this tablet, but I would need blobs or something first.
Still have the stock recovery on the laptop, so I'm sure I have all I need.
How would I go about it without running into Error 7 when flashing?
Thanks for any tips you might have!
r
OK, didn't hear anything, so decided just to give it a try on the Y01 (recalled / blacklisted) tablet.
Applied the original ROM from Nvidia download site and flashed the unofficial Lineage OS 14.1 image since I've been loving it on my replacement unit. Just made sure not to connect to WiFi after reverting to stock.
Once on stock Nougat, flashed Lineage and SU. Job done, and I'm happy.
My fear of the serial being blacklisted in the ROM itself was unfounded.
If you haven't put Lineage OS 14 on your shield tablet, I highly recommend it (if you don't need Nvidia apps or your camera). Smoothest ROM I've used & best battery life since I got the thing!
Sent from my SHIELD Tablet using Tapatalk
Where did you find the stock nougat image? I also have a recalled shield tablet and would like to upgrade my lineage OS but cannot do so because my bootloader is out of date. You can revert to stock but just not connect to wifi and be okay?
rabrol said:
OK, didn't hear anything, so decided just to give it a try on the Y01 (recalled / blacklisted) tablet.
Applied the original ROM from Nvidia download site and flashed the unofficial Lineage OS 14.1 image since I've been loving it on my replacement unit. Just made sure not to connect to WiFi after reverting to stock.
Once on stock Nougat, flashed Lineage and SU. Job done, and I'm happy.
My fear of the serial being blacklisted in the ROM itself was unfounded.
If you haven't put Lineage OS 14 on your shield tablet, I highly recommend it (if you don't need Nvidia apps or your camera). Smoothest ROM I've used & best battery life since I got the thing!
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
Hi All,
I have a two Relays that have served me well, and I enjoyed having them, but the time has come to pass them on to someone else. Before I do that, I'd like to update them to the most recent versions of stable-release software that is available for them.
For Cyanogen, I have:
cm-11-20150831 (this is stable)
cm-11-20160523 (this is a nightly build)
For recovery I have:
philz touch 6.48.4
I'd like to replace Philz with a newer TWRP, but the Relay is no longer listed on the TWRP website. I'm also wondering if there was ever a stable CM release newer than the one I have.
Does anyone have sources for the above?
Thanks.
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
mrigancb said:
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
Click to expand...
Click to collapse
Although I'm not a developer I have been working on my SGH T699 from T Mobile. You may already know of the JellyBean and before. Recently I've noticed new builds for the samsung Galaxy S Relay 4G like the Validus 5.0.2 or the Fat Toad. I haven't tried those yet I was trying for a higher version. With 8.0 Oreo it requires partitioning and I need to brush up on that. So I went lower to the 7.0 or the 7.1 Nougat. I started noticing a lot of broken or old links so I had to resort to fishing the internet for most of the packages apparently lost in XDA. I pretty much have all of them and was just starting to try a few out when I ran into problems like I want to keep using the keyboard and Wifi calling or a related Wifi issue. It also crashed, went into bootloop or even soft bricked within a few days. The Roms and packages I've found are highly unstable and I see many had flashing issues. So far I've been tricking my device into taking the flash and even then it doesn't hold long. I'd like 6.0 MarshMallow if I can, maybe 7.1 if they ever get stabler that'd be great. But so far the ROMs for the Galaxy S (relay) are fairly horrible to say the least. I get the impression these so-called developers aren't testing their ROM creations more than 5 minutes and then handing them off to noobs who may be very likely to brick their device trying to get it in and running, only to have it crash repetedly! Or worse, hard-bricked.
I like this device. I think I'll keep working on it.
Casper Young.
I had purchased my Shield brand new some years back from Gamestop when they were quietly being discontinued. Not only that, but the employee told me because of that, whatever remaining inventory each Gamestop had was being recalled back to Nvidia. There was only one left on my area so I bought it right away for $150 brand new . It came with Jellybean and I had only did one OTA update which brought it up to 4.4.2 KitKat. This past December I decided to finally unlock the bootloader (the warranty long ran out so I had nothing to lose) and root it afterwards. I followed this thread to unlock the bootloader and this post to gain root access. Both worked great :good:. I never bothered updating to Lollipop because it doesn't have Miracast and I like the dark theme of the KitKat version of Android better. I just looks nicer to me. So I was going to leave the OS as is since everything was functioning as I wanted it to.
However, starting this year, the Nvidia Shield hub app no longer works and has been replaced with a newer app called Nvidia Games. The thing is, it only works on Android 5.0 or higher . I have also seen people mention on Youtube that using that app, you can install Steam through it, which has a beta feature that starts it in Big Picture mode. This supposedly allows you to stream any Steam game without the need of an Nvidia card or the need of a PC . After reading that I wanted to update to Lollipop right away. This sounds to good to be true, but if it is, I will be ultra happy. :laugh:
I wanted to make a nandroid back up before updating, so I followed this thread to install the TRWP recovery. I was able to make a nandroid backup and restore it without issues. Then I rebooted and
went in the Shield settings menu to check for updates and it downloaded update 110. It said to restart and it would install, so I did. Initially it looks like the update was working. But then it gets stuck in a boot loop showing either the Nvidia Shield logo or the green Android guy with a panel open on it's chest. :crying:
I also tried installing the Lollipop update using the method described in this thread. It unfortunately didn't work.
Then I attempted through fastboot to flash stock stock recovery that I extracted from the OTA, but it fails saying: "(command write failed (No such device or address))"
So all my attempts to install Lollipop aren't working. Is it due to having root and the TWRP recovery installed and not the stock recovery?
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.