I have an Acer A501 which had Android 3.2.1 on it and recently decided to provide to my parents as a tv guide device so they could sit and research on it. They didn't need the 3G component.
I performed a factory reset and we were unable to use the Market/Play Store to load any of my parents apps. I returned home with the device so decided to try and upgrade to 4.0+
Upon doing lots of reading I started loading an ICS bootloader (a500_a501_bootloaders_apx_ics_v9) with the A500APX Flash.exe I found.
Since doing this my device sits at "Reboot the device!" in big red letters and the Acer logo has turned yellow. When I try a Power+LeftVolume reset it tries to read from SD card but fails. My Micro-SD is 64GB, whats the max size and is there anything special I need to do to try and ressurrect the device?
Can anyone help me with my problem?
When I boot with Power + Volume Up I get shown the following:
Erasing Cache before SD update...
SD update cmd:recovery
--update_package=SDCARD:update.zip
Same issue
dkingsho said:
I have an Acer A501 which had Android 3.2.1 on it and recently decided to provide to my parents as a tv guide device so they could sit and research on it. They didn't need the 3G component.
I performed a factory reset and we were unable to use the Market/Play Store to load any of my parents apps. I returned home with the device so decided to try and upgrade to 4.0+
Upon doing lots of reading I started loading an ICS bootloader (a500_a501_bootloaders_apx_ics_v9) with the A500APX Flash.exe I found.
Since doing this my device sits at "Reboot the device!" in big red letters and the Acer logo has turned yellow. When I try a Power+LeftVolume reset it tries to read from SD card but fails. My Micro-SD is 64GB, whats the max size and is there anything special I need to do to try and ressurrect the device?
Can anyone help me with my problem?
Click to expand...
Click to collapse
Hi
I got a friends A501 tablet and he asked me to upgrade the os. so I flashed the bootloader with the same bootloader as you and got stuck with the same problem. Yellow Acer and reboot the tablet in red. Did you ever find a solution?
Hi! I have exactly the same issue! did any one knows what the steps to fixe it? I tried to follow the unbrick solutions and nothins because I don't even get connection to the computer. The only way to listen the USB connection is with a paper clip press reset and power for 3 seconds (or more) and I will ear the sound of a USB device being connected to the computer, but then I try to write adb usb or adb shell and nothing... and with AfterOTA tool appears in the USB section: ERROR - connect usb cable and enable usb debugging (in dhe Driver section is OK).
I have a Nvidia Shield TV (2017/16G) on which I've try to modify the build.prop to allow me to connect with ADB via my local lan. I did this by pulling and modifying the /system/build.prop file, unlocking the bootloader, booting TWRP 3.1.1-1 and then pushing my modified build.prop file to the device.
During reboot I get the warning about bootloader being unlocked and then (not always) I get a warning about my device being corrupted and not trust worthy, the device never boots, the TV video is a black/gray screen.
This process worked fine on my 2017/500G shield.....
Does anyone have a suggestion on how to get by this security check ??
PS: I can re-image the device back to stock 5.2.0 and it works fine.
That's a known error on 2017 16gb model as 2017 500gb a.k.a pro is the same as 2015 one you didn't have that issue.
That is displayed when you unlock the bootloader, to get past that screen i think you had to press the A button on shield controller. The ones that flash custom roms do know about that error and we solve it rooting the device as it disables nvidia checks during boot.
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
Yes I was aware about the shield controller and the "A" button. Yeah, did not want to root the device as it prevents (I think) streaming services like Directv Now, PS Vue etc. from working.
What is the root fix for this message?
hi all
I got message to update my shield and after approved, it got stucked, when I turn it on this is what I saw:
[IMG="can't access"]
https://photos.google.com/share/AF1QipP6lYKS4ccUqP9t9KLMnKbPXbqIHJDP__XfJ-roc8yusu21wnnnHpmFVWds0sSlLA?key=Y012MzhCVS1zV2NXS1NObElZVkNRV2tlQ1RKbEJn[/IMG]
my shield is not rooted and I never flushed it.
any idea what i can do?
I couldn’t load Screenshot, this is what written on screen:
Your device is corrupt. It can’t be trusted and may not work properly.
Visit this link on another device: g.co/ABH
Plug controller into SHIELD and press A button to pause boot
Hello all. I have owned my shield for 2 years now and for the first time attempted to root it. I made it to the twrp image and instead of loading the needed option to root it stayed on the nvidia image. I am guessing the twrp is old and there for not 8.0 twrp. At anyrate now ehen I turn on my shield it says I need to relock the boot loader and that I am not protected. My question is how do I fix this or do I need to ? Does anyone know where to find the current twrp and do I need to relock the bootloader and start over or can I finish from here ? Will I screw anything up keeping it unlocked ?
First of all, what experience version are you on?
And the warning that comes up when you turn on your shield is just a warning, because you have unlocked the bootloader.
You don't need to worry about it.
If you root, you wanna leave the bootloader unlocked.
mLgz0rn said:
First of all, what experience version are you on?
And the warning that comes up when you turn on your shield is just a warning, because you have unlocked the bootloader.
You don't need to worry about it.
If you root, you wanna leave the bootloader unlocked.
Click to expand...
Click to collapse
Thank you for responding ....
I am on 8.0 oreo
elderbrain said:
Thank you for responding ....
I am on 8.0 oreo
Click to expand...
Click to collapse
For Oreo there is only an experimental twrp, but you don't really need twrp to root.
You can use this guide for Nvidia Experience 7.2.3, which is Android 8.0 Oreo.
https://forum.xda-developers.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254
So to be sure, you are on Android 8.0 Oreo (Nvidia Experience 7.2.3) Correct?
And not Android 9.0 Pie (Nvidia Experience 8.0)
correct. I have a nvidia shield running 8.0 oreo. do I start from where I left off or from the start ? At this point no command workd for me and the shield is not detected. I have a brand new usb cord plugged in and all things enabled.....power shell says the commands i cut and pasted from your link are not correct commands and the minimal and fast boot says I have no device detected.....so at this point non of this matters untill I can fix this. whats the best command prompt to get this going ?
elderbrain said:
correct. I have a nvidia shield running 8.0 oreo. do I start from where I left off or from the start ? At this point no command workd for me and the shield is not detected. I have a brand new usb cord plugged in and all things enabled.....power shell says the commands i cut and pasted from your link are not correct commands and the minimal and fast boot says I have no device detected.....so at this point non of this matters untill I can fix this. whats the best command prompt to get this going ?
Click to expand...
Click to collapse
I'm using minimal adb and fastboot https://forum.xda-developers.com/showthread.php?t=2317790
Use the shortcut it makes when installed to open a command prompt.
What version of the shield do you have?
And are you booted into the bootloader?
I have the 16 gb running 8.0 oreo. I have unlocked the bootloader yes. I did every step up to loading the twrp. I used a you tube video by TT Technology. Made it to the last and final step. As of now my shield keeps disconnecting and reconnecting when connected to through usb so it does not detect any devices. I get lucky for a moment but it then stops recognizing the shield. Whats odd is that the shield is listed and I can open it and access all the storage including the mounted through the computer even when the connection drops. Right now untill i fix this issue everything else is moot.
I didn't ask if you unlocked the bootloader.
I'm asking if you are able to get into it where you do the fastboot commands?
Ah sorry. No, no commands work and I am not able to load the bootloader. It says deamon failed to start and it does not see the shield as a connected device.
elderbrain said:
Ah sorry. No, no commands work and I am not able to load the bootloader. It says deamon failed to start and it does not see the shield as a connected device.
Click to expand...
Click to collapse
If you own a SHIELD Controller
Unplug SHIELD TV.
Connect SHIELD controller to SHIELD TV with a USB cable (use port closest to HDMI).
While holding the A and B buttons at the same time, connect power to SHIELD TV.
If you do not own a SHIELD controller
Unplug SHIELD TV.
Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV.
Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Click to expand...
Click to collapse
This will get you into the bootloader, and you should be able to use fastboot commands
I tried both keyboard and controller and this is not do anything. When I fire up the command prompt two things happen I get this message:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
adb server version (40) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found.
Or it finds the shield and says its offline. My usb connection has been fixed. I was able to run a game through game stream to my pc and even watched a movie with my computers dvd player on my tv using wiredxd. So I know i have a solid connection. I am clearly doing something wrong here as I clearly am connected to the pc now.
elderbrain said:
I tried both keyboard and controller and this is not do anything. When I fire up the command prompt two things happen I get this message:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
adb server version (40) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found.
Or it finds the shield and says its offline. My usb connection has been fixed. I was able to run a game through game stream to my pc and even watched a movie with my computers dvd player on my tv using wiredxd. So I know i have a solid connection. I am clearly doing something wrong here as I clearly am connected to the pc now.
Click to expand...
Click to collapse
Oh my bad, I didn't think you were able to boot.
Have you enabled usb debugging on the shield in the developer options?
Anyways, that error is usually because of using an out of date adb.
try this minimal adb and fastboot
https://www.androidfilehost.com/?fid=745425885120698566
Yes. I have made sure all 3 possible options where enabled, from developer options to usb debugging. I even got the message to allow it always on this device. I have full access to the shield through usb and it appears in my DM.........I have tried all three versions I can find for minimal fastboot. v 14.1......1.4.3 and the one you said to try 1.4.2. All have the same message. It just either does not detect a device or it says its offline. I have pretty much thrown in the towel at this point as all options have been attempted and hours of googling where wasted. I really have no idea where to go now. I tried resetting the shield a few times.....then tried revoking usb and re enabling and nothing will get it to connect to the deamon. Thank you for all the help. I appreciate you trying
In what state is your shield currently ? From what I read in your posts , your shield doesn't currently boot ? You said it's stuck at the nvidia logo. I am no expert, but if you really are stucked at the nvidia logo, until you enter fastboot mode properly, ADB won't be of any help. If that's the case , then follow any of the methods in post #10 of this thread to properly enter fastboot mode. From there you'll be able to fix things. Since it was you that unlocked the bootloader then it means that the cable, the drivers and your installation of ADB were all in working order at that moment. Now has to why you are stucked on the nvidia logo , you didn't mention which step of which guide you were following when that happened , but at the very least your recovery.img or boot.img have issues. If it's the recovery (twrp) then you're using a wrong one. I don't think a bad recovery.img will let you get as far as the nvidia logo so I doubt that's the issue here. Your boot.img seems corrupted and cannot proceed past the nvidia logo, so perhaps you tried a pre-patched boot.img that isn't the correct one for your current system version or you patched it yourself with a magisk manager that doesn't properly patch the boot.img . I would suggest that next time you type "fastboot boot boot.img" (boot instead of flash) so that you at least try the boot image before you go on and flash an untested file (not a blame, if its the case then you followed a guide that didn't mention this precaution first). Anyways , if you're stuck at the nvidia logo , then what you should do first is try to flash a clean boot.img . Go to nvidia's site and grab the proper recovery for your system version (7.2.3 you said) by scrolling down to Recovery Images , and first choosing your correct hardware and next the image you need. Extract these files in the same folder as your ADB installation so that you can just click "flash-all.bat" and it will fix your shield (it will flash the correct recovery.img and boot.img). Of course this has to be done while you are in fastboot mode , so it comes back to this, get your device into fastboot mode properly. Any USB keyboard you have around the house should work to do this :
Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV. --- I add this : Hold the keys until something happens. Release them only once you reach fastboot mode or the nivida logo and try it with every usb port before ruling it doesn't work.
Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Oh, if you get into fastboot mode and the commands still give you errors about client versions not matching, that might be an issue with other software running on your pc, but we'll stay out of this for now.
Roamin64 said:
In what state is your shield currently ? From what I read in your posts , your shield doesn't currently boot ? You said it's stuck at the nvidia logo. I am no expert, but if you really are stucked at the nvidia logo, until you enter fastboot mode properly, ADB won't be of any help. If that's the case , then follow any of the methods in post #10 of this thread to properly enter fastboot mode. From there you'll be able to fix things. Since it was you that unlocked the bootloader then it means that the cable, the drivers and your installation of ADB were all in working order at that moment. Now has to why you are stucked on the nvidia logo , you didn't mention which step of which guide you were following when that happened , but at the very least your recovery.img or boot.img have issues. If it's the recovery (twrp) then you're using a wrong one. I don't think a bad recovery.img will let you get as far as the nvidia logo so I doubt that's the issue here. Your boot.img seems corrupted and cannot proceed past the nvidia logo, so perhaps you tried a pre-patched boot.img that isn't the correct one for your current system version or you patched it yourself with a magisk manager that doesn't properly patch the boot.img . I would suggest that next time you type "fastboot boot boot.img" (boot instead of flash) so that you at least try the boot image before you go on and flash an untested file (not a blame, if its the case then you followed a guide that didn't mention this precaution first). Anyways , if you're stuck at the nvidia logo , then what you should do first is try to flash a clean boot.img . Go to nvidia's site and grab the proper recovery for your system version (7.2.3 you said) by scrolling down to Recovery Images , and first choosing your correct hardware and next the image you need. Extract these files in the same folder as your ADB installation so that you can just click "flash-all.bat" and it will fix your shield (it will flash the correct recovery.img and boot.img). Of course this has to be done while you are in fastboot mode , so it comes back to this, get your device into fastboot mode properly. Any USB keyboard you have around the house should work to do this :
Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV. --- I add this : Hold the keys until something happens. Release them only once you reach fastboot mode or the nivida logo and try it with every usb port before ruling it doesn't work.
Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Oh, if you get into fastboot mode and the commands still give you errors about client versions not matching, that might be an issue with other software running on your pc, but we'll stay out of this for now.
Click to expand...
Click to collapse
I have all but gave uop at this point, but to answer your question. My shield works and runs it is just in the state where the bootloader is unlocked and I get the warning. I have attempted the instructions before, holding down the a and b keys on both the game controller and a wired keyboard and it does nothing. I agree that the twrp is not current and that I need the proper files. As of now my shield is just not recognized period. That is why holding down the aand b keys does not work ( IE it in the command prompt it says shield is offline or it sees it and when I enter fastboot it just says waiting for device and does nothing more. So half way through it looses connection to the shield ) Untill I can get the shield to be recognized none of these instructions matter. As of now I have decided to give up and maybe in a while try again. I would like to completely restore my shield to the state it was in so I can start from scratch. That is what I am focusing on now, but untill my shield is recognized I dont think even that is possible. Thanks for your post. I appreciate all the help all of you have offered.
Impossible d'accéder au recovery
Bonjour j'ai fait une erreur de flashing, le fimware de NVIDIA Shield TV n'était pas bon, donc le logo NVIDIA reste bloqué, j'ai essayé de faire a et b mais impossible d'accéder au booloader et au recovery comme faire ?
I have an Android TV and I wanted to disable its launcher. Because I wanted to install my own launcher !
So I connected to it via ADB and made some changes.
Then the TV software crashed and when I restart the TV, I just see the first welcome screen of TV and nothing happens after that.
I think I need to factory reset the TV and I have nothing to do that.
My TV brand is UNEVA.
Does any body know nothing about that ?
BR
On my fire tv edition I had to hold the power button a few second with the tv turned off and a few second after the logo starts up. The physical power button on the tv. You can try on the remote too, the same way. This is how you get to tv recovery on a fire tv edition.
Actually I didn't understand what to do !
Could you please write the steps again by detail ?
thank you
Do you have an android tv or a smart tv? Is it a streaming device or the tv itself is not working? Turn off tv, hold down power button while you plug the tv back on and wait for a start up screen then the recovery screen.
Yes I have and Android TV.
It was working correctly , but after some changes in firmware files using ADB, it has been stuck in startup screen.
Because of that I needed to go into recovery mode.
I followed up your instructions, but nothing happened.
My TV brand is UNEVA. It is a Chinese brand and it is not famous at all.
But its firmware name is "Wisdom Share" which is a bit famous.
faarraisd said:
Yes I have and Android TV.
It was working correctly , but after some changes in firmware files using ADB, it has been stuck in startup screen.
Because of that I needed to go into recovery mode.
I followed up your instructions, but nothing happened.
My TV brand is UNEVA. It is a Chinese brand and it is not famous at all.
But its firmware name is "Wisdom Share" which is a bit famous.
Click to expand...
Click to collapse
You should be able to find the stock images for the current Android operating system on Google's website and then you can just reflash those
Your uneva brand Tv is an Android tv, and I assumed you connect to adb remotely. Can you check if you can still connect to adb? If you are messing with adb then you should know recovery mode, you need to get into recovery to factory reset.
Yes UNEVA is an Android TV and I used to connect to it using adb , but after making some changes in OS files (in shell mode) , the TV damaged and now I just can ping the TV and can not connect to it using adb.
So finally I think I need to get into factory reset mode.
But the problem is that I don't know where is factory reset page?
watch this video, it is how i factory reset my tv when i couldnt get pass the tv logo. www.youtube.com/watch?v=g-kdQjSE__A
I watch the video.
I did this bust it didn't work and my TV does not turn ON !
It means that my TV is different from the Toshiba model in YouTube video
every brand of tv have their own hard factory reset buttons to press when you cannot access the software of the tv. you have a tv i have never heard of maybe you can get a hold of pdf of your tv instructions. Good luck.
Unfortunately I could not find its Guide Book. It is almost a no-name Chinese brand and because of that, I thought maybe I can find a way using the TV's android software (Wisdom Share)
But anyway, thank you for your help.
I still have to search for a way and would be thankful if anyone can help.