I was on shield tv software version 5.0.2 when I flashed full Android 1.3. That was in 2017 well this week I got a wild hair to flash back to stock take OTA'S and flash full Android 1.5 here is my long 2 day story condensed:
I was confused as to wich Nvidia stock rom version I was supposed to flash so I started with Stock 3.3. This was a mistake then I flashed stock 5.0 then I flashed Stock 5.2 then I reflashed stock 3.3. then I flashed 5.0.2 and even more lol
At this point I was getting flashing failures none of them would complete. Yes I flashed blobs I flashed boots I flashed userdata I flashed everything from many different versions. I just kept flashing and in different order. IT WAS CHAOS! Of course the only thing I could get to was Bootloader (how I dont know)
I somehow got Stock 3.3 to flash and all of it flashed. It actually booted I couldnt freaking believe it! After the android logo at boot the screen goes green. I almost bashed my tv in with a hammer at this point.
At this point I was running these commands fastboot erase system, fastboot erase cache, fastboot erase boot. I DONT RECOMEND DOING THESE COMMANDS! I could no longer flash the stuff I was erasing like boot sector. After these commands I just kept flashing things that would flash. And I just kept flashing. Somehow I got those erased sectors back. Still couldnt get anything to boot
I found out on XDA that if I take the blob file from the 5.0.2 OTA and the rest of the stock rom files from 5.0 (in my case) I got it to flash boot update OTA from Nvidia in increments to Stock 6.0. I then took Full Android 1.5 and flashed it. Im back up and running now full android 1.5 with 6.0 stock everything works fine
if anyone thinks they might have bricked their shield Dudes the Shield tv survived me Im sure you are not bricked. Unless you cant even get to bootloader.
Related
EDIT: SOLVED. After some hours at work I was able to boot back to the bootloader and flash the images individually.
TL;DR at the bottom.
Hi, I've been rooting and ROMming for a while now, and last night I made a mistake that set forth a chain of depressing events. I have a N7 2013 LTE, and was running AOKP up until last night. I wanted to flash the 9001 L preview, despite having no access to data. Simple right? Wrong, you forget to realize I'm a tired idiot last night. I downloaded the zip no problem, rebooted to TWRP and commenced my advanced wipe. Some how, I mistakenly checked off "wipe internal storage" during the process. So I go back to the Install screen, and my heart sinks. F***. At this point I decide to let it lie in recovery until tomorrow (today) and keep it charged.
Fast forward to this morning, I'm at the office. My device is charged and waiting in recovery. I decide I'm just going to flash the factory image to stock 4.4 and start with a clean slate, wiping all (even though it's wiped). Reason for factory image and not just adb push the ROM is that I'm having a seemingly-unsolvable issue of incorrect storage. It tells me my 32gb device only has 11.6 gb total storage. This has persisted through multiple clean-wiped installs of various ROMs, but I don't know if it started out like that when I bought it, since I didn't think to check before unlocking and putting a ROM on it.
So I get the SDK and images on my work PC, and commence flash-all.bat. Working great until it gets to system.img, then it fails. Try again twice, same thing. Open the image zip and extract the files, then try to flash one by one, now it's saying the commands are invalid (fastboot flash system system.img, etc). So I wonder, because sometimes these devices are wonky in ADB, maybe it installed and just said it failed? F*** it, I'll try to boot. Google logo for an hour. Ok, cool, I'll go back to the bootloader. NOPE. The device either won't power on at all, or it will get stuck at the splash screen and hang there. Any idea where to begin to fix this?
TL;DR: No OS on phone, failed flashing system.img in flash-all.bat, now device won't boot to bootloader or (missing) OS. Any ideas?
Okay so i went through the bootloader unlock process on my Note 4 without any major hickups, was running on CM13 ever since until i wanted to play with Gear VR which from what i could find required me to be on a stock based/touchwiz rom, first up was Omega which installed fine but would boot loop at welcome screen, so then i went with Evolution and almost same story, just boot loop. Figured it had to be a problem with the firmware version on my phone and without thinking i downloaded the CPF1 firmware and flashed with Odin. Flash went fine with no problems, booted into marshmallow just fine, enabled usb debugging and rebooted to flash TWRP for recovery and i get zilch. Every single TWRP and CWM recovery file i try to flash end in a failure. Can't even get Kingroot to give me root in MM so I think i'm stuck...dont even see the Unlock logo and Custom on the main screen after i hit the power button to turn on.
SO.........
Big question is, did i just re-lock my bootloader when i flashed firmware CPF1?
I think I did this same thing a while ago, were you on an older version of CM13 from May or so? Anyway, what I had to do was flash stock 5.1 in Odin with the up to date kernel, modem, etc and follow the guide to re-unlock your bootloader
Well got it re-flashed and unlocked again, gotta give a shout out to the great guys here on XDA.
Next question is do i need to flash a new bootloader or modem in odin/twrp before moving to a MM rom or is that stuff usually included in the rom? My experience in roms and stuff is from my old Razr Maxx HD and never jumped operating system version with it so i'm not sure on this one.
Lenovo appear to have made downgrading from Nougat to Marshmallow difficult. The commands to flash certain images such as the bootloader and modem from fastboot have been disabled when the bootloader is unlocked, and relocking the bootloader seems to be impossible with the standard oem lock command. I had no knowledge that I would lose a certain degree of control over my P2 before I unlocked the bootloader, so I am rather disillusioned about it all at the moment.
When I first unlocked I was running the stock 3 UK Marshmallow firmware. I installed TWRP (modified) and somehow I soft-bricked my phone because one of the ROMs I tried flashing got stuck at the Kernel writing part and restoring TWRP stock backup froze when writing the boot partition so I was unable to get anything but a blue notification LED when resetting. I also attempted to restore stock backup with non-modified TWRP and that didn't help either. I wiped data each time I tried to do something, and also changed file system from F2FS to EXT4 and back again several times. Never in my 6 years of flashing ROMs had I encountered such issues.
Nothing was working, so all I could think to do was use fastboot commands to restore each stock image. Luckily this worked without a hitch because I hadn't upgraded to Nougat yet, but I still didn't know about the potential issues with downgrading, so when I flashed the ROW stock ROM, I upgraded it to Nougat in the OTA menu. Then I stumbled upon all the problems people have been having when they attempt to use fastboot to restore stock MM (the only ROM with fastboot parts for the P2?) the main one being that their signal stops working (modem partition corruption / incompatibility?) and even when upgrading again to Nougat, their signal is still gone. There is an ADB shell command that may or may not fix this.
Now I'm on stock ROW Nougat and stock recovery because I'm worried that I might inadvertently mess something up again and my only hope would be to fastboot flash back to stock and risk losing my signal. There doesn't appear to be a "safety line" when upgrading to Nougat for me atm because of the restrictions Lenovo seem to have put on fastboot commands.
I own a canvas A1 4GB variant, I had rooted my phone and flashed custom recovery(everything was finee), After a while my phone's battery started giving me problems(lasted only few hours), I considered flashing Stock ROM or any other trusted ROM, I had flashed RR M[07/07] based on android MM, The battery was still giving problem, A week later, My mom's phone broke and she had to use this(A1) temporarily, I formatted everything and thought of flashing stock ROM and handing over the phone to her, I tried flashing the official zip via TWRP, It gave me some error regarding unable to mount system, System partions or something(I don't remember). And after that, I could't flash any ROM, I tweaked some settings in TWRP and now my phone is totally dead, It does not boot up at all, No recovery mode turns on, Nothing except a black dead screen, I tried flashing stock firmware via SP flash tool, It completes and says successful but still nothing happens, Just wanna know if something can happen to this one? I really loved that device and would be great to have it back working.
Flash correct stock firmware in sptools
arunassain said:
Flash correct stock firmware in sptools
Click to expand...
Click to collapse
doesn't work. I have tried various STOCK Roms on mine but didnt work. Please post a link if possible which u think works.
Not sure what is going on or if anyone else has this problem, but since I got the Moto G power I've had a problem booting into the system after flashing stock ROMs in fastboot. Everytime I try my device doesn't go past the blue Moto logo. I'm no stranger to rooting/flashing ROMs/or anything like that. I probably flash more than necessary always switching up my phones. Ive flashed fastboot ROMs for years with no problems. I've got used to just using LMSA and it never failed to fix my issue. Now, LMSA won't recognize my device in terms of matching firmware and I can't use it without validation. I can flash everything fine and start to boot but nothing after that. I've tried formatting, factory reset in both stock and twrp to no avail. Even restored my Omni backup countless times in twrp which usually did its job no problem. Tried flashing vbmeta etc.. am I just experiencing tunnel vision and missing something obvious or what? Any help would be appreciated I'm not the same without my phones working device is US retail unlocked 2041-4 Sofia on what I assume is the latest firmware. (lolli Moto)
You've been trying to boot it with the stock kernel and not a magisk patched one after restoring however? / Have you tried booting without a magisk patch kernel (stock) and userdata formatted?
I had the same problem updating the firmware and i had to first boot it with the non rooted kernel and userdata formatted to first boot.