Hi everyone,
As mentionned in the title I'm afraid I bricked my Shield TV (model 2015, 16GB).
It was previously running StockRestyle 3.0 Marshmallow (from zulu99: https://forum.xda-developers.com/shield-tv/development/rom-t3321787) and all was fine with it.
But since Nvidia announced Nougat for the Shield TV, I wanted to give it a try.
Thus, I tried to flash the official recovery images from Nvidia, but I think I made the mistake to flash the Nougat version instead of the Marshmallow one.
So, here is what I've done:
- I copied the official Nougat recovery images on my PC in my adb folder
- I ran the flash-all.bat
- it started all right, but was then stuck for several minutes
- the shield TV rebooted itself but was stuck on the Nvidia logo
- after several minutes without change nor messages on the command, I quit the command terminal.
Later, I tried to start the process again without success.
Now, I can have access to the bootloader using the hardware procedure (long-press on the power button).
Unfortunately, it says on the top "Production mode: fused" (see the attached pictures).
From the bootloader, I tried "Forced recovery" -> I got a black screen -> Fail
I also tried the "Boot recovery kernel" -> I got the screen image with the android robot down with an warning symbol (see the attached pictures)
I tried adb and fastboot without success.
When I reboot the bootlaoder, with the shield connected to my PC with an OTG cable, the shield is detected but there is a warning message on my PC (it's not well recognized).
Also, "fastboot devices" returns nothing.
Technically, the shield is l still under warranty since it's less than 2 years old, but I'm afraid this "Production mode: fused" message would void it!
Any similar situation or suggestion?
Thank you in advance and have a nice day.
Hi, that production mode: fused is normal. I checked and I have it. I think it is there since I unlocked the bootloader. I run Full Android Nougat from @zulu99 without issues.
Do not keep trying to flash things just to flash. While you be able to boot into bootloader you can recover it (remember this) but is also true that if you mess with the bootloader you can brick your device. You're just soft bricked not hard bricked.
First, post the complete version of the bootloader, in the screenshot I can't see the whole version.
For later (do not attempt to flash anything until we go thru some checks):
Try with another known working USB cable and/or reinstalling fastboot drivers. And do not use flashall.bat, you will do it command by command.
Enviado desde mi Moto X mediante Tapatalk
That's what happens when you don't follow directions
Here is a picture with the complete version of the bootloader.
I followed quite well the instructions a year ago when I was trying to evaluate the pros and cons of Stock ROM, Stock Restyle and Full Android. Unfortunately @zulu99 posts have been closed since then.
Thus I forgot I had to revert back to standard Marshmallow first ;-(
I also tried two others USB OTG cables.
With on of them I managed to get "fastboot devices" recognizing a device, and I don't have this warning message on my PC (it's not well recognized) when starting the bootloader.
What should I do next?
Problem solved!
Since I guess the issue was mainly due on the suddenly defective OTG cable (it worked in the beginning of my last try, since I managed to flash some parts), I started the procedure again with with the official recovery 5.0.2.
- I started the bootloader using the HW method: long-press on the power button during powering up, until the bootloader appears
- Then,
* fastboot -w
- Then, again, I had to start the bootloader using th HW method
- Then, I followed most of the points described in the flash-all.bat files (except the adb commands)
* fastboot flash staging blob
* fastboot flash boot boot.img
* fastboot reboot
- Again, I had to start the bootloader using th HW method
- Then,
* fastboot flash recovery recovery.img
* fastboot flash system system.img
* fastboot flash vendor vendor.img
* fastboot reboot
- and voilà: I got Nougat running. Then the time it took me to enter my email credentials and so on, the OTA update to 5.1 was downloaded and ready to install.
A few minutes and a reboot later, I have the latest version running.
Thanks guys.
Your issue was the USB cable, if there is no good connection the flash can be incomplete thus corrupted. It is better to run the commands manually one by one so you know if it was successful on each flash or identify where it got stuck. Your lucky it didn't fail while flashing blob.
Probably failed after the boot flashing and fastboot reboot.
I suggest you get another USB cable, always use high quality cables. The internet is flooded with Shield TV users with TWRP, flashing issues and bricked devices because of a bad USB cable.
Enviado desde mi Moto X mediante Tapatalk
I tried doing the same thing and i got errors when flashing system and vendor files. It says that data is too large.
Can anyone help me rollback from Android 10 to Android 9. I need it for a couple of applications which hasn't yet come up with Android Q support.
I have the Google Pixel 2XL. I have done this before with my other phones before but each phone is different in some ways. So if anyone has already done it, would be much helpful coming from them. And I have already tried using this article:-
https://lifehacker.com/how-to-downgrade-your-phone-from-android-10-to-android-1837868743
My note: When I sideload as per the article it doesn't show me any percentage or progress.
This video:-
https://www.youtube.com/watch?v=77RmzsShTTs&t=223s
My note: The fastboot command doesn't work.
I can't find a video or article that is consistent with the current platform tools or anything in that matter.
Thanks in advance.
Hi
It should be easy to do so. Just go to Google factory images page and follow the steps mentioned there, after downloading your desired Android 9 image.
backup your data first as you lose all data when you unlock your bootloader( you lock it later on)
A lazy way is put the August P OTA on a OTG
Boot twrp and format data
Mount the OTG, flash and boot the OTA + twrp installer zip
Or
Fastboot erase userdata
Manually flash bootloader, radio and vendor on both a & b slots then
Fastboot update ( drag and drop the taimen folder found in the extracted factory image)
Let it do it's thing
The latest platform tools can be downloaded from google.
Alright here goes another post from another stupid user who did things without understanding
I know there are hundreds of other threats with the same question,I tried to check them but they are damn many and I am confused. I hope no moderator gets angry at me.
I have PRA-LX1 which had EMUI 8 working fine. and then I decided that I am too young to have an old Android and decided to go for LineageOS 17.1 from DarkJoker360. After couple of unsuccessful attempts and some minor things I ave a phone that goes into fastboot, but not TWRP. keeps bootlooping (I tried a stock recovery for oreo and then was able to shut it down when it prompted eRecovery page, otherwise it kept looping). Bootloader unlocked. (I was able to get so many different TWRPs to work on the phone just few hours ago, and I guess I did not do anything that bad either. )
I saw these posts about getting the boot.img and other images from some Huawei Firmware finder, but not sure how to get them and I am not sure how can I check the exact model of the phone (I guess it is PRA-LX1xxxxxx)
Sorry if I am not giving enough info, I would appreciate if you ask
Resolved. I am not sure what was the issue, but I did followings (writing down just in case this will be helpful).
PRA-LX1 c464. Bootloader unlocked. I was not able to get into TWRP. I was able to get into fastboot. eRecovery from Huawei was not doing anything (cannot get info from server it said).
Then I downloaded the FullOTA-MF
dload method was getting interrupted after 5%.
Then I extracted System.img kernel.img, recovery_ramdis.img and ramdiks.img. and flashed these in order.
System – fastboot flash system SYSTEM.IMG
Ramdisk – fastboot flash ramdisk RAMDISK.IMG
Kernel – fastboot flash kernel KERNEL.IMG
Recovery – fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
Then at reboot it was getting stuck at 0% loading (Warning To avoid system error please do not press and hold the power button) on some EMUI page. Waited for half an hour and rebooted. again stuck. went into bootloader and flashed a TWRP. this time I get into TWRP.
From there dload method to go back to EMUI and installed LineageOS afterwards.
Hi all. Im quite new to this whole flashing stuff so would like to request some help on how to recover my OnePlus 8 pro. I was previously running Pixel Experience 11 on my Oneplus 8 pro when i decided i wish to return to OOS 11. I folloewd a forum online using a flash-all.bat file with my widows pc to return to stock OOS 11. When the process completed the phone only reboots into fastboot mode. i went into recovery and did a factory wipe and cache wipe but no hope. I then tried to follow the forum but using the MacOS method of individually flashing the images but no hope. as it mentions the following "Flashing is not allowed for Critical Partitions". Ive tried running fastboot flashing unlock_critical but it keeps saying device is unlocked. Could anyone please help me recover my device? I just want stock OOS back . Many reboots results in just going into fastboot mode. Thanks for the help.
20:42
Hi everyone!
I just softbrick my OP8pro after an unsuccessful downgrade (using oneplus updater) from the last offical OTA to the previous stable version. This means from 12.1 to 12, in terms of android versions. Now I just manage to go to fastboot, when I try to go on the recovery one it goes to the fastboot as well (tried both key combinations w/ power button). Unfortunately I have same recent data on the phone which I didn't backup and really need to recover.
My goal is to get a way to backup data and userdata or at least an adb shell to download the most critical files, after that I will unbrick it w/ MSN tool.
When I try "fastboot flash recovery/recovery_a/recovery_b" or "fastboot boot" with a recovery image, it doesn't change nothing (with the first) or (on the second) reboots and stucks on the fastboot logo even before showing the fastboot menu itself. Tried w/ latest twrp or recovery.img extracted from official OTAs (different versions from a11 to a12.1)
The boot-loader is unlocked.
I'm running out of ideas, can anyone help me out?
Many thanks in advance.
Rastejant said:
20:42
Hi everyone!
I just softbrick my OP8pro after an unsuccessful downgrade (using oneplus updater) from the last offical OTA to the previous stable version. This means from 12.1 to 12, in terms of android versions. Now I just manage to go to fastboot, when I try to go on the recovery one it goes to the fastboot as well (tried both key combinations w/ power button). Unfortunately I have same recent data on the phone which I didn't backup and really need to recover.
My goal is to get a way to backup data and userdata or at least an adb shell to download the most critical files, after that I will unbrick it w/ MSN tool.
When I try "fastboot flash recovery/recovery_a/recovery_b" or "fastboot boot" with a recovery image, it doesn't change nothing (with the first) or (on the second) reboots and stucks on the fastboot logo even before showing the fastboot menu itself. Tried w/ latest twrp or recovery.img extracted from official OTAs (different versions from a11 to a12.1)
The boot-loader is unlocked.
I'm running out of ideas, can anyone help me out?
Many thanks in advance.
Click to expand...
Click to collapse
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Dont mess with twrp on a12 - it does not work with a12 anyway
Be really careful what you flash from fastboot. Read the topic i posted above first and really take care.
The only thing i can imagine what will work is that you have to flash ALL images from 12 or 12.1 i would guess you need to flash the version you are trying to downgrade from but again read the link.
I dont think you will be able to recover your data tbh.