Database Users

Shield TV 2015 16GB Stuck on Nvidia Logo After Attempting TWRP Install

**UPDATE** I reinstalled the stock 8.0 Developer ROM and I was able to get past the Nvidia logo and boot Android. I then found a TWRP (3.3.1, had to Google around a bit, PM me for link if you need it) and it worked and I was able to boot into TWRP.
However, my main objective was to install Lineage OS, and none of the ones I've found install correctly. I was trying to install the Nightlies on the official Lineage OS website, as well as try to install the Lineage OS with MicroG ROMs both 14 and 15 LOS, but none of those install. Infact I was told in the TWRP dialog that I have too new of a bootloader for LineageOS MicroG 15 to even install.
IS THERE A WAY TO DOWNGRADE THE BOOTLOADER VERSION? It says I'm on 00.00.2018.xxxxxxxxxx but this Nvidia Shield TV is a 2015 variant?
**END OF UPDATE**
Hey all, after purchasing a used Shield TV off Craigslist, which I presume updated itself to the newest OTA, when I turned it on, I now have some issues.
After I let it install the newest OTA as of yesterday, I enabled Developer Options and enabled USB Debugging.
I then got into fastboot using the HW method, and proceeded to install the newest TWRP I found for Foster.
After I installed the TWRP, I tried to boot into recovery, and it did nothing besides restart and boot normally back to the Android TV OS.
I flashed it a few more times, until I decided to just wipe the entire thing using fastboot -w I believe.
After that the Nvidia Shield TV no longer booted normally, but was stuck on the Nvidia Shield TV logo.
So I thought, okay, lets revert back to a stock image, and I proceeded to download 2 different Nvidia Shield Developer Images, and go through the steps to flash the stock image back to the Shield TV.
After going through those steps, and seeing all the steps complete successfully, I am still only able to boot to the Nvidia logo screen, and it does not move past that.
I have tried reinstalling the stock image countless times, and I'm still stuck on the logo.
Does anyone have any idea with where I should proceed now?
**I've tried different USB cables, and different HDMI cables and still not doing anything different.

You might get faster help on your los issue if you ask directly in the los thread https://forum.xda-developers.com/shield-tv/development/rom-lineageos-shield-android-tv-t3632652

I'm trying to install lineage in the 2015 box and have the same problem, I downgraded the bootloader to versions t210-ab068ba1, t210-4954eb9e, t210-3461c2e2, etc,etc.... I tray all the bootloaders down to Nvidia Experience 6 and none let me install lineage whit success, I'm abled to install lineage but then it won't pass the Nvidia logo, also tested several version of twrp, official and unofficial, the result it's the same and I can't find a solution anywhere, install all the recovery images, etc... I've also read all the forum and all the article's and guide's I can find and no solution, if you find a solution, let me know
edit: to change the bootloader, download the Nvidia Experience image you want, extract and flash in fastboot using "fastboot flash staging blob"

ignore, sorry wrong thread

Backup Everything - ZTE Trek 2 HD K88 Andriod 6.0.1 Marshmallow. Following Step?

Hello all!
I currently am using an ZTE Trek 2 HD K88, which is on Android 6.0.1 Marshmallow. I would like to be able to backup the tablet so that i can revert right back to where i left off sort of speak. Meaning apps installed, Paid for content, accounts setup, etc... Sort of an image i am guessing.
I am using Linux, but can access windows if it has to be.
I currently have adb installed and can boot the tablet into EDL and stock recovery which have no backup option. I have not found TWRP that is designated for this tablet and android 6.0 (Marshmallow). It looks as though it may only be available for android 7.
Questions. -------------
What do i have to do for complete backup my Marshmallow K88? Assuming it to be like a image of partition or similar?
After i get my tablet backed up do i have to upgrade my tablet ito android 7 n order to run Rom? Seems as if everything is aimed at assuming the tablet is on nougat 7.0, such as TWRP. Basically what is the next step?
Thanks for any help you may provide!

[MUSTANG] FireOS 7(pie) released

Amazon has finally released FireOS 7 for the Amazon Fire 7 2019! What does this mean?
This means that developers have newer blobs and kernel to work with for Mustang roms! This could be good for development. I don't know if ggow will come back to this device, but I'll personally be trying to get LineageOS 16.0 working on here. I have mirrored the kernel on Github for convenience's sake. https://github.com/turtleletortue/android_kernel_amazon_mustang
One thing to note, do not install FireOS 7 if you want to continue using custom roms. I'm not sure, but it'll likely break amonet and leave you stuck on stock. So until we get an ok either way, just stay on the version you are on.
That being said, have a great day all of y'all! Hopefully something good comes out of this.

Karnak's Pie Source Code (mirror) here: https://github.com/R0rt1z2/android_kernel_amazon_karnak

I've downloaded the bin file, hoping it might be simple to extract the separate boot, recovery and system images from it but alas it's beyond the scope of my knowledge.
I'll try poking it later with binwalk or some other unpacking tools (I've got some amlogic tools on my laptop too) in case they provide me some hints but if anyone reading this can offer suggestions, I'd be happy to experiment

After re-reading the original post re: downgrade and root FireOS, I have bitten the bullet and am currently in process of flashing this.
I have pushed the .bin to device, renamed as .zip.
I've flashed zip, then flashed TWRP before rebooting to recovery and flashing magisk.
I am now looking at the "Amazon" logo whilst the device does its first-boot. Wish me luck!
I will report back as soon as I have more news
edit after 10 mins.
No change. Still looking at the amazon logo
30 mins - still no boot. rebooting to twrp to try again, but without magisk
45minutes - bootloop. amazon logo for a few seconds, black screen, looping indefinitely
Have flashed LOS14.1 as it's the only OS zip file I had sitting on internal storage. Waiting for it to do its first boot
No joy
In the end, the only way o could get device to boot up again was to flash fireos 6, from the original root guide

At this time, the link on the Amazon website for the current version of OS7 is wrong. It will download OS6 (6.3.1.5) instead. The correct link is below.
OS7 for Fire 7 (Mustang):
https://fireos-tablet-src.s3.amazon..._7_9th_Gen-PS7315_user_1958_0018354775684.bin
Click the link for a direct download.

MontysEvilTwin said:
At this time, the link on the Amazon website for the current version of OS7 is wrong. It will download OS6 (6.3.1.5) instead. The correct link is below.
OS7 for Fire 7 (Mustang):
https://fireos-tablet-src.s3.amazon..._7_9th_Gen-PS7315_user_1958_0018354775684.bin
Click the link for a direct download.
Click to expand...
Click to collapse
Have you had success in installing it? Rooting it, etc?

wodgey said:
Have you had success in installing it? Rooting it, etc?
Click to expand...
Click to collapse
If you have a stock tablet and copy the update.bin to '/sdcard' and reboot it can be installed by instigating a system update check. Even with a stock set up though the tablet won't boot if you flash OS6 bootloader files (TZ and LK). If you try and unlock with a modified version of amonet (keeping the OS7 bootloader files) you get a bootloop.
Unlocking and rooting may yet be possible but it is 'above my pay grade'.

MontysEvilTwin said:
If you have a stock tablet and copy the update.bin to '/sdcard' and reboot it can be installed by instigating a system update check. Even with a stock set up though the tablet won't boot if you flash OS6 bootloader files (TZ and LK). If you try and unlock with a modified version of amonet (keeping the OS7 bootloader files) you get a bootloop.
Unlocking and rooting may yet be possible but it is 'above my pay grade'.
Click to expand...
Click to collapse
Ah ok. I see. That makes sense. Thank you for explaining so concisely, yet in words I can understand

One Plus 5 won't upgrade to new Android.

Hi
I fixed my oneplus 5 using MSMdownload tool. It put my phone on Android 7.1.1 with July 1st, 2017 security Patch and Oxygen OS 4.5.8, I have exhausted all the option to upgrade it to latest Android but it won't update. Every time I check for update it will show that it is up to date. I have also tried "local Upgrade" option but it shows installation failed.
Any work around this would be highly appreciated
Thanks
Aman

@lucider14 Just curious why you used the MSMDownloadTool from OxygenOS 4.5.8 and not the one for OxygenOS 9.0.11? You most likely won't see OTAs for Android 7 as it is now 4 Android Versions behind as of this week. Android 9.0.11 was the last official fully released OTA, OxygenOS 10.0.0 Hotfix is last official OTA OnePlus has released into the wild.

My phone waa bricked so had to use it. Please let me know if there is any workaround for this to update.

@lucider14 The workarounds I would try are:
Opt 1: Upgrade via zip file in Stock Recovery
Step 1: Download latest OTA from https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Step 2: Copy zip file to root of Phone storage
Step 3: Reboot into Recovery
Step 4: Install
Opt 2: Use Newer MSMDownloadTool:
Step 1: Download newest tool from here https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Step 2: Reboot phone into EDL
Step 3: Run newer MSMDownloadTool

card13;83478941 [user=11104643 said:
@lucider14[/user] The workarounds I would try are:
Opt 1: Upgrade via zip file in Stock Recovery
Step 1: Download latest OTA from https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Step 2: Copy zip file to root of Phone storage
Step 3: Reboot into Recovery
Step 4: Install
Opt 2: Use Newer MSMDownloadTool:
Step 1: Download newest tool from here https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Step 2: Reboot phone into EDL
Step 3: Run newer MSMDownloadTool
Click to expand...
Click to collapse
@lucider14 OOS 4.5.8 is pre-treble. You can't jump directly to Android 9 or 10. One of the OOS updates before Android 9 set up treble on our phones. I don remember exactly which one. You're best to use Opt 2 above, it will be easier.
Cheers!?

lucider14 said:
Hi
I fixed my oneplus 5 using MSMdownload tool. It put my phone on Android 7.1.1 with July 1st, 2017 security Patch and Oxygen OS 4.5.8, I have exhausted all the option to upgrade it to latest Android but it won't update. Every time I check for update it will show that it is up to date. I have also tried "local Upgrade" option but it shows installation failed.
Any work around this would be highly appreciated
Thanks
Aman
Click to expand...
Click to collapse
First,flash it 9.0.11 build and then OxygenOS 10.0.0 Hotfix..

And with https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater

I've had a similar problem and I thought I broke my phone, got pretty scared can't buy a new phone but need a newer android for my apps to work.
I came from freedom OS on android 7 so I never had the project treble on my phone and tried to flash new factory images, as a result, no newer TWRP recovery worked and I was unable to boot into anything other than the bootloader. I had the same error with Error 7, from what I can understand this is from a screwed up or non-existing "vendor" partition which says stuff like "this is a OnePlus 5" for newer factory images to install (factory image told me I didn't have a OP5), this never existed in android 7 or OOS 4.X.X. ScRuFFy7 is correct, the vender partition was created in OOS 5.1.4 (or OTA 037) and only when android is booting up, this took like 10 mins on mine. Once this vendor partition is correctly created you can flash newer TWRP recovery (I flashed 3.4.0) and newer factory images, like OOS 9.0.11 then to version 10. The built-in updater and stock recovery can update to the newer versions with the flashable zip files. For whatever reason OnePlus don't size the partitions in their zips so they make small changes from one version to the next so skipping specfic versions throws up errors in the future.
Screw it, I should document what I did in case I mess up my phone in the future and maybe be helpful to someone else in need, especially in this messed up and depressing time of the plague. But anyway this is what I did to get my phone back, I should point out I have no idea what I'm doing. Meaning I'm a N00b.
NOTE: this process Wipes all the data from the phone, so I hope you have backups right now.
Will need ADB, you can install This on windows, it's super easy and works thanks to mauronofrio. You can get the all in one tool too from here it's pretty handy and can format and decrypt from the bootloader, from mauronofrio? I think? This guy is pretty good. I got all old firmware from Here thanks to Some_Random_Username for the life line since OnePlus won't provide the old Zips anymore.
1) Boot to TWRP recovery if you have it installed (VOL DOWN + POWER). If not Boot to Bootloader (VOL UP + POWER) and flash TWRP Recovery. You can use TWRP 3.1.1 This one works on OOS 4.X firmware without giving me a Black Screen.
1a) To Flash the Recovery you can use the all in one tool to flash it or open up command prompt and use the Fastboot Flash [insert recovery file name here .img] command to flash it, you can find the FastBoot Flashing Method in the middle of this page for instructions.
2) Format Data. The Format Data button in TWRP recovery not the swipe to factory reset, because we're going back to scratch.
3) Flash OTA_006 (OOS 4.5.2) original firmware from the link above (says ota_006 in the middle of the loong file name)
4) Boot into android and use System Update in settings and stock recovery it just flashed to flash OTA_020 (OOS 4.5.15) by clicking on the cogwheel in the corner and choosing Local Update. [probably skippable I just wanted to make sure it works]
5) Boot into android again and install OTA_27 (OOS 5.0) with System Update again.
6) If it doesn't boot, go to Bootloader and flash TWRP. Once in the recovery and you go to install and if you find all the folders have random numbers and letters for names then the storage in encrypted.
7) Format to get rid of encryption (random name folders) then reboot to Recovery and Flash OTA_27 again and let it start fresh on OOS 5.0 to make sure it's still booting and working.
8) Once booted Flash OTA_037 (OOS 5.1.4) wait for vendor partition to be created (took 10 mins on my OP5), reboot to TWRP and format if folders are encrypted and reflash OTA_037 if needed.
Once booted into android this is the point where you should have the Vendor Partition already created by the factory image, you can go back into TWRP (flash TWRP if needed) and under Mount be able to see, mount/unmount a Vendor partition without errors. This should solve the Error 7 problem with factory images. A newer version of TWRP Recovery should work now, I installed 3.4.0 from mauronofrio Here. 3.4.0 works with android 10.0 so I was glad.
9) Boot android again and flash OTA_038 (OOS 5.1.5) just to make sure with stock recovery. [Probably skippable but I was a Paranoid Android at this point, just to make sure it still works]
10) Boot to android again and install OTA_042 (OOS 9.0.0) with System Update to keep making sure it works. [Again, I was Paranoid. Probably Skippable]
11) Boot to android again and install OTA_054 (OOS9.0.11) as last Android 9 update to have things set up ok.
12) Boot into Android again and install the latest android 10 from OnePlus (OTA_068) with System Update and the Stock Recovery, this is Android 10.0.0 and OOS 10.0.0. Things should work fine at this point but I doubt the check for update will get new oneplus updates. As of Sep 25, 2020 it is up to date. Technically.
I should add something else I discovered after. I found a flashable zip file from one of the lineage OS posts of a oneplus5_vendor_5.1.5.zip Here. You might be able to just use that to create the Vendor partition then just Flash one of the OOS 5.X Firmwares and go from there, I've not tried it so I'm not 100% sure but it's a possibility?
Hope this is helpful to someone at some point in time. for troubleshooting at least. Honestly really glad I have a working phone right now.

Stuck at bootloader--HELP!

Let's get this out of the way. I don't have much experience flashing ROMs. I've done it on a few phones, but I can't say I really understood what I was doing. I'm just good at following directions. So, I know about enough to get into trouble.
And ...I've gotten into trouble. My goal is to install LineageOS on my brother's Essential Phone. Based on directions I found here, I determined the active slot was b, so I installed TWRP on slot a. TWRP worked in recovery, but without touch. I then flashed twrp-3.2.3-0-mata.img to the non-active slot. Lastly, I sideloaded twrp-installer-mata-3.2.3-0.zip. I then changed the active slot back to b and rebooted. It now boots only to the bootloader and not to the OS. No matter what option I select--Start, Bootloader, Recovery--it reboots to the bootloader.
Any help to get out of this would be greatly appreciated.

Lineage can be installed more easily using Lineage's own Recovery rather than using TWRP. The Lineage Recovery is a pre-built replacement for your boot.img file.
Links for Lineage OS 17.1 (mata) and its corresponding Recovery (mata):
https://download.lineageos.org/mata
Link for Installation using Lineage Recovery:
https://wiki.lineageos.org/devices/mata/install
Hope this helps

MuddyDog said:
Lineage can be installed more easily using Lineage's own Recovery rather than using TWRP. The Lineage Recovery is a pre-built replacement for your boot.img file.
Links for Lineage OS 17.1 (mata) and its corresponding Recovery (mata):
https://download.lineageos.org/mata
Link for Installation using Lineage Recovery:
https://wiki.lineageos.org/devices/mata/install
Hope this helps
Click to expand...
Click to collapse
Thanks for the suggestion. I had actually already tried that. That's when I got desperate and tried generic TWRP. When I try to flash the Lineage recovery image I get a "No such partition" error, no matter which partition is active. I read somewhere that the flash boot_[letter] command might work, but I get "Couldn't parse partition size '0x'.

mcmc08 said:
Thanks for the suggestion. I had actually already tried that. That's when I got desperate and tried generic TWRP. When I try to flash the Lineage recovery image I get a "No such partition" error, no matter which partition is active. I read somewhere that the flash boot_[letter] command might work, but I get "Couldn't parse partition size '0x'.
Click to expand...
Click to collapse
Try:
Fastboot flash:raw boot_slot recovery.img

So, I found a solution. In order to overcome the errors I was getting, I had to use the raw command. So it was fastboot flash:raw boot [image file]. Once Lineage recovery was installed, I could boot to recovery and sideload Lineage.

MuddyDog said:
Try:
Fastboot flash:raw boot_slot recovery.img
Click to expand...
Click to collapse
I guess our replies crossed. At any rate, the raw command did the trick. Thanks for your help.

I'm having the same problem, and the raw command doesn't seem to help. Trying to install twrp causes it to be stuck in the bootloader. I somehow was able to install the lineage recovery, then to install the lineage OS. Because I am thinking of trying other ROMs, I decided to go back to trying the TWRP install. Now everything seems broken. When I use the a slot (where I installed TWRP), I'm stuck in the bootloader. When I shift to the b slot, I'm stuck on the Lineage splash page.
(By the way, while I was in the Lineage recovery at some point in the middle of all this, I also sideloaded the TWRP install zip.)
I've tried flashing the TWRP numerous times, and it always seems to work, but the result still is the same.
Any help would be appreciated.
Edit: I was able to get out of the loop by reflashing the Lineage Recovery, booting into that recovery, then doing a factory wipe. I was able to boot into Lineage. But why can't I successfully install TWRP? Or, I guess, alternately, is it possible to use the Lineage Recovery to flash different ROMs? (Sorry if this goes beyond the scope of the original question.)

Is Lineage using an Android 10 security update after January? January is the last update for Android 10 that TWRP worked with. Once Essential went belly up the TWRP devs just stopped updating when it broke with February security update. Anyway, I just thought I would mention it.

rocketrazr1999 said:
Is Lineage using an Android 10 security update after January? January is the last update for Android 10 that TWRP worked with. Once Essential went belly up the TWRP devs just stopped updating when it broke with February security update. Anyway, I just thought I would mention it.
Click to expand...
Click to collapse
I installed Lineageos directly on the february android stock version. (which is the last one from Essential)
Simply by following the tutorial on the LineageOS website.
Everything worked the first time.
So there is no need to switch back to the January android stock version. The image recovery provided by Lineage works very well.
And for your information LineageOS is updated almost every Monday.
Moreover the developers of the TWRP are not the developers of Essential. Company which closed at the end of February.
---------- Post added at 11:18 AM ---------- Previous post was at 11:14 AM ----------
KJannot said:
I'm having the same problem, and the raw command doesn't seem to help. Trying to install twrp causes it to be stuck in the bootloader. I somehow was able to install the lineage recovery, then to install the lineage OS. Because I am thinking of trying other ROMs, I decided to go back to trying the TWRP install. Now everything seems broken. When I use the a slot (where I installed TWRP), I'm stuck in the bootloader. When I shift to the b slot, I'm stuck on the Lineage splash page.
(By the way, while I was in the Lineage recovery at some point in the middle of all this, I also sideloaded the TWRP install zip.)
I've tried flashing the TWRP numerous times, and it always seems to work, but the result still is the same.
Any help would be appreciated.
Edit: I was able to get out of the loop by reflashing the Lineage Recovery, booting into that recovery, then doing a factory wipe. I was able to boot into Lineage. But why can't I successfully install TWRP? Or, I guess, alternately, is it possible to use the Lineage Recovery to flash different ROMs? (Sorry if this goes beyond the scope of the original question.)
Click to expand...
Click to collapse
Which Rom would you like to install instead of Lineage?

groovebox said:
Which Rom would you like to install instead of Lineage?
Click to expand...
Click to collapse
I'm of two minds; one is just to go with something stock android-ish, which leads me to Evolution X or Pixel Experience. The other is to cut myself from Google entirely, which leads me to /e/. I'm also looking at Paranoid, just because it looks like it's stable. Any thoughts on any of those?
I had updated Essential to the February update; would that be why TWRP would not successfully install on my phone?
Would that still be true if I had flashed Lineage?

KJannot said:
I'm of two minds; one is just to go with something stock android-ish, which leads me to Evolution X or Pixel Experience. The other is to cut myself from Google entirely, which leads me to /e/. I'm also looking at Paranoid, just because it looks like it's stable. Any thoughts on any of those?
I had updated Essential to the February update; would that be why TWRP would not successfully install on my phone?
Would that still be true if I had flashed Lineage?
Click to expand...
Click to collapse
Paranoid Android: What I heard is VoLTE broken, if you enable it, SMS/MMS might not work properly.
Evolution: No update in Android 10 since August, not sure they contine to support Essential phone for Android 11
Pixel Experience: I don't think they Anroid 10 for Essential phone, only official Anroid 9 which is too old
TWRP issue: You need to go back to Jan stock rom before going to any rom if you just flashed LOS
What current stable rom with Nov security update: I'm using crDroid 6.12 (unofficial release but from XDA reliable source)
https://forum.xda-developers.com/essential-phone/development/rom-crdroid-v6-7-t4129739