So for reference I own a 2015 shield TV 16gb model. I've debated rooting and such but never followed thru with any of it. It was running 5.0 stock and kept prompting me for the 5.1 update which could (?) be the culprit. Anyway got home from work yesterday and it wasnt booting. I tried booting into recovery and clearing the cache, nothing. Then tried a factory reset, nothing. So I found the Recovery image for it and proceeded to flash it. After flashing the staging blob (Which is successful) It gets hung up when I try to flash the boot.img. I've tried re-downloading as well as trying the 5.1 image and nothing has worked. Has anyone else experienced this?
bsutton said:
So for reference I own a 2015 shield TV 16gb model. I've debated rooting and such but never followed thru with any of it. It was running 5.0 stock and kept prompting me for the 5.1 update which could (?) be the culprit. Anyway got home from work yesterday and it wasnt booting. I tried booting into recovery and clearing the cache, nothing. Then tried a factory reset, nothing. So I found the Recovery image for it and proceeded to flash it. After flashing the staging blob (Which is successful) It gets hung up when I try to flash the boot.img. I've tried re-downloading as well as trying the 5.1 image and nothing has worked. Has anyone else experienced this?
Click to expand...
Click to collapse
What do you mean with "hung up" ?
And are you certain you have the correct image downloaded?
(And did you make sure that you didn't just execute the flashall.bat? Because that's not the best way to flash the firmware, they should have left that one out....)
So are you able to boot into fastboot/bootloader mode in a stable way or does it reboot few seconds after booted up in that mode?.
First try with other USB cables (this is a well known issue, the Shield TV is picky), use the rear usb ports or your PC (the ones that are soldered to the motherboard) and avoid using usb 3.0+ ports.
If using a 4k or UHD TV, try with an up to Full HD TV or Monitor.
Do not mess with the bootloader (blob file), there was no need for you to flash that. Only corrupted bootloader flashing will hard brick your device, so be careful with it.
While you be able to boot into fastboot mode you can fix/recover your device.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
USB cable or USB port?
I had a similar thing happen with my SATV 2015 16GB model. Turns out it ended up being the USB3.0 ports on my Dell 5510 giving me grief. Each time I tried to adb the image files it was failing at different times. I made sure and got a good USB cable and used another PC with USB2 and it flawlessly put stock back on the shield. If you can fashboot, you can bring it back.
Related
I got a serious problem with the N4 of a friend.
First thing to know: his display was broken and he got it repaired. Afterwards, his phone was running fine. Then, he got the Android 4.3 OTA. He accepted the update, but since then in keeps bootlooping (I won't go past the Nexus-X). As far as I know, everything was stock!
Here are the things I tried:
- first I checked the recovery. Indeed it was the stock one, so nothing to do here.
- I wanted to wipe or flash the stock rom using fastboot but i wasn't able to get a connection. First I thought of driver issues, but my N4 works fine (adb & fastboot) on the same computer.
- Establishing a connection failed on two other computers too (my N4 worked)
- Even the device manager in Windows 7 dosen't even recognize anything when plugging in the usb cable (normally you see the ADB whatever device listed in the device manager)
- Right now I tried to get a connection using Ubuntu. Again, no usb device was recognized when plugging in the cable.
So right now, I'm a bit lost. It seems, that the usb port is broken since I can not establish a connection. And without that, I won't be able to wipe or flash anything using fastboot.
Does anyone have an idea what could have gone wrong? I'm still able to boot into the bootloader and see the information:
Bootloader version: MakoZ20i
Radio: .84
HW Version 11
16GB version
According to these information, it seems that the 4.3 Update finished at least the bootloader and radio. But it won't boot into the rom. Could the download mode be of any help?
I appreciate any help.
Thanks.
Since you are in the bootloader scroll up to recovery and select it.
Now you will see a android opened up with "No command." written below the android.
Press volume up and power until it unlocks the recovery and try to wipe the data and cache partition followed by dalvik cache.
Sent from my Nexus 4 using Tapatalk 4
Thanks for your idea, but it turned out to be hardware problem!
I took the device to the lab and had a look at the usb connector. The contact in the middle was teared of the carrier and was stuck to the back and thus no data connection could be established! I was able to to bend it back (more ore less) to its initial position and now its working. Though I'm wondering how long it will last until its pushed back again.
Fact is, that i was able to connect via fastboot. I tried to flash 4.3 again but it still didn't boot. Its back to 4.2.2 and its working now.
Again - thanks for your idea.
Thread can be closed!
Hello, after updating my Nexus 7 (Wi-FI) via OTA my nexus wouldn't turn on... it just got stuck on the nexus logo.
I tried wiping, flashing the OTA via sideload, also tried flashing the factory image also via sideload, but I kept getting an error (error 7 I think).
After that, I used the fastboot update image-nakasi-krt16s.zip but it got stuck on sending system < 611886 KB >.
I don't know what else to do, any help would be appreciated!
Same problem here. I'm running a pure stock. In rooted device and it bricked on me.
Sent from my SGH-M919 using XDA Premium 4 mobile app
theblackout said:
Hello, after updating my Nexus 7 (Wi-FI) via OTA my nexus wouldn't turn on... it just got stuck on the nexus logo.
I tried wiping, flashing the OTA via sideload, also tried flashing the factory image also via sideload, but I kept getting an error (error 7 I think).
After that, I used the fastboot update image-nakasi-krt16s.zip but it got stuck on sending system < 611886 KB >.
I don't know what else to do, any help would be appreciated!
Click to expand...
Click to collapse
Speaking of getting stuck with the "sending system" process, It was also mentioned in this thread.
It seems that you could go back to 4.3 by flashing factory images and flash 4.4 factory image again, then you are good to go.
Just for you information.
noradoor said:
Speaking of getting stuck with the "sending system" process, It was also mentioned in this thread.
It seems that you could go back to 4.3 by flashing factory images and flash 4.4 factory image again, then you are good to go.
Just for you information.
Click to expand...
Click to collapse
Same thing using that thread, I.
fastboot erase system
fastboot flash system system.img (old 4.3 img)
stuck on sending system <529061 KB>
getting nervous here, any other ideas?
OK, I finally got it back to life!
I fastboot cwm recovery, then adb sideload this rom: http://forum.xda-developers.com/showthread.php?t=2222374
That should do it
theblackout said:
OK, I finally got it back to life!
I fastboot cwm recovery, then adb sideload this rom: http://forum.xda-developers.com/showthread.php?t=2222374
That should do it
Click to expand...
Click to collapse
I will try this when i get home from work and see how it goes.
Ksealy03 said:
I will try this when i get home from work and see how it goes.
Click to expand...
Click to collapse
Hi, Ksealy03...
Erm... but before you do that... Whilst fastboot flashing stock Android 4.4 (KitKat), you might want to try changing the USB cable that connects your Nexus 7 to your PC to a different USB port on your PC. Or, possibly even changing the USB cable completely.
The 'stuck on sending image' problem is a commonly reported one here on XDA.
Indeed, I myself don't recall NOT having the problem, whenever I fastboot flash factory stock... it's always the same, "Oh no, here we go again... still sending system image" after five minutes. It's almost predictable - I just expect it happen now.
Anyway... I then disconnect my USB cable from my PC, reboot the Nexus 7 bootloader... reconnect my USB cable TO A DIFFERENT USB PORT on the PC - and begin the flash procedure all over again... and then it works! System image goes over.
Quite why this happens, I've no idea... but I suspect it has something to do with the size of system image, 'cos everything else (recovery, etc) goes over quite happily, without problems. At some point the fastboot connection dies (times out?), and you have to re-establish it.
Rgrds,
Ged.
GedBlake said:
Hi, Ksealy03...
Erm... but before you do that... Whilst fastboot flashing stock Android 4.4 (KitKat), you might want to try changing the USB cable that connects your Nexus 7 to your PC to a different USB port on your PC. Or, possibly even changing the USB cable completely.
The 'stuck on sending image' problem is a commonly reported one here on XDA.
Indeed, I myself don't recall NOT having the problem, whenever I fastboot flash factory stock... it's always the same, "Oh no, here we go again... still sending system image" after five minutes. It's almost predictable - I just expect it happen now.
Anyway... I then disconnect my USB cable from my PC, reboot the Nexus 7 bootloader... reconnect my USB cable TO A DIFFERENT USB PORT on the PC - and begin the flash procedure all over again... and then it works! System image goes over.
Quite why this happens, I've no idea... but I suspect it has something to do with the size of system image, 'cos everything else (recovery, etc) goes over quite happily, without problems. At some point the fastboot connection dies (times out?), and you have to re-establish it.
Rgrds,
Ged.
Click to expand...
Click to collapse
Ok im actually trying it now. i have a different USB cable that I will use.
teraonic 318
No luck. because my debugger is not on I can t do anything. ADB and fastboot wont even recognize the device. probably just call up Asus.
Ksealy03 said:
No luck. because my debugger is not on I can t do anything. ADB and fastboot wont even recognize the device. probably just call up Asus.
Click to expand...
Click to collapse
I had a similar issue that I was able to fix. Hopefully this will help you too.
I have a Nexus 7 that is rooted, stock ROM, unlocked bootloader. I have gotten many OTA updates since buying the device, and all previous OTA updates have completed without a hitch.
On the most recent OTA Kit Kat update, the device froze when trying to apply the update. It just displayed the boot animation in perpetuity.
I was able to use the Nexus Toolkit here on XDA (LINK) to load the stock Kit Kat ROM. Hope that helps.
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Evil Penguin said:
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Click to expand...
Click to collapse
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
DJDON1302 said:
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
Click to expand...
Click to collapse
Lol that site ripped my Tutorial! how nice of them, You should of linked the person to https://forum.xda-developers.com/nvidia-tegra-note-7/general/nvidia-tegra-note-7-apx-images-t3149839
I accidentally downloaded the wrong image file and flashed the 2017 boot, system, and vendor images to my 2015 SATV.
The system still boots Android but throws constant errors. ADB shows no devices connected so adb reboot bootloader won't work. I've also tried to boot fastboot using both the 2015 and 2017 hardware methods but neither work, probably because the 2017 boot.img isn't checking for the power button press and the 2015 gamepad or base is missing something to invoke fastboot.
My one hope is that it might be possible for a 2017 gamepad to invoke fastboot on a 2015 base but I'm wondering if anyone has other ideas or knows if that won't work.
https://youtu.be/2AzHF-uNiY8
Try with other(s) usb cables too. You can't hard brick that way if you didn't touch the bootloader.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Unfortunately I did flash the boot.img with the wrong model file however after several more tries and making sure the PC was connected during boot I was finally able to get back into fastboot using the power button method and re-flash the correct files.
Thanks for the tip though.
kylehase said:
Unfortunately I did flash the boot.img with the wrong model file however after several more tries and making sure the PC was connected during boot I was finally able to get back into fastboot using the power button method and re-flash the correct files.
Thanks for the tip though.
Click to expand...
Click to collapse
which image did you use for the nVidia Shield TV 2015 (16gb)? I download this one: NVIDIA SHIELD ANDROID TV Recovery OS Image 5.2.0 2017/06/15 ---But for some reason I keep on getting boot loop even after restoring to stock.
The first (wrong) one I flashed was nv-recovery-image-shield-atv-2017-5.2.0.zip. The correct one for 2015 16G model is nv-recovery-image-shield-atv-5.2.0.zip
After I flashed the correct one it's been running fine with existing data in place.
kylehase said:
The first (wrong) one I flashed was nv-recovery-image-shield-atv-2017-5.2.0.zip. The correct one for 2015 16G model is nv-recovery-image-shield-atv-5.2.0.zip
After I flashed the correct one it's been running fine with existing data in place.
Click to expand...
Click to collapse
Thanks for confirming I am using the right rom. I decided to send the item for RMA.
may throw my nexus in the bin...
was already having trouble with trying to connect to windows using usb but kept reconnecting
connected to mint successfully and flashed with twrp
however any twrp flo were giving mounting errors and rebooting, i did try few other versions but was having same issue
so i tried 2.8, now my nexus boots to recovery mode
twrp logo sits still for 5 seconds and then screen flashes black and then shows the logo again, looping
(it surely is still having mounting problems)
adb devices show nothing neither does fastboot
anyway never experienced a device with various problems
like sensors stopping out of nowhere and also taking ages to fully charge
Did it run fine on the original firmware?
V0latyle said:
Did it run fine on the original firmware?
Click to expand...
Click to collapse
stock factory reset worked normally
ignoring what i stated at the end it was running fine
android 6.0.1 kernel 3. something