Related
I updated days ago with bad rom the Tablet Onda v820w with windows 10.
I found the correct Bios and now I have the correct file.
But now, I can´t access to windows to update the flash.
How to unbrick this tablet.
Some method to flash the bios outside windows?
The tablet power ON but screen is black, but microusb works It turns on the light of the hub that I have put
The BIOS brand is "Insyde".
If need moore details please ask me.
Very Thanks four your help.
Regards
can you access command prompt (CMD)?
or
can you access the bios and flash from there instead?
only ever flashed bios a few times (on desktop) but ive always done via the bios screens rather than in windows itself.
.
Hi
I can´t access to CMD, because the screen don´t turn on.
Only can put pendrive and Keyboard with MicroUsb hub. (This turn on the light when push the power button)
But I don´t know if tablet have some method to rescue the bios from Bad update.
Thanks
I have similar problem. Please help me anyone. I flash older bios to my v820w and i have now black lcd.
Also i unforunatelly delate windows partitions when flashing Android and now i can acces Android by HDMI output in my TV
is any way to flash bios by Android just like in x98 air 3g?
locoslaw said:
I have similar problem. Please help me anyone. I flash older bios to my v820w and i have now black lcd.
Also i unforunatelly delate windows partitions when flashing Android and now i can acces Android by HDMI output in my TV
is any way to flash bios by Android just like in x98 air 3g?
Click to expand...
Click to collapse
Hi I have the same tablet, when it works it is perfect, but the screen scrambles and the console become Un usable and freezes, i thought that it might just be windows 8.1 so I managed to put windows 10 on it last night but today it is doing the same thing. Could some one offer some advice.
Well...
Hi, I was able to fix a v975i tablet that was completly dead, because of wrong bios update, in my case i use a programmer unit and pro skills to weld. Basically you will flash the bios and download the correct bios , but i had to desolder the chip from the motherboard.
Hey, i got an problem. i flashed recovery with my nvidia shield tv, everything works good on adb and i success to flash recovery, and to reboot to recovery but when i try to click "install" on Recovery my shield has restarted and was showed an android with broken with "Red" alert , and now my computer not even recognize the nvidia shield when i try to connected it, and also ADB wont working, some idea please how can i get it to work? im stuck right now, and i cant see anything in shield this is not even recognize the my TV with HDMI
Danieli1669 said:
Hey, i got an problem. i flashed recovery with my nvidia shield tv, everything works good on adb and i success to flash recovery, and to reboot to recovery but when i try to click "install" on Recovery my shield has restarted and was showed an android with broken with "Red" alert , and now my computer not even recognize the nvidia shield when i try to connected it, and also ADB wont working, some idea please how can i get it to work? im stuck right now, and i cant see anything in shield this is not even recognize the my TV with HDMI
Click to expand...
Click to collapse
Ok, you flashed the recovery, you mean twrp?
Yes Sir
Danieli1669 said:
Yes Sir
Click to expand...
Click to collapse
http://ota-downloads.nvidia.com/ota..._e-full_ota-41937_667.2671.20160218230615.zip
Thats the stock Firmware. You must flash it with TWRP
Make a Full wipe and then Install the zip File.
i cant even do anything, i cant access bootloader. i getting always "No Signal" when nvidia shield turned on
Danieli1669 said:
i cant even do anything, i cant access bootloader. i getting always "No Signal" when nvidia shield turned on
Click to expand...
Click to collapse
You mean your TV has No Signal?
yes bro, i think its hard brick
Hi I am having issue with a device which I bought and can not return. The nvidia shield pro 500GB is stuck in fastboot mode.
Every time I turn the device off and on all I get is the options you get in fast boot.
I have tried to boot recovery kernel, force recovery etc and I just get the same screen again.
I have tried to unlock the device to see if I can flash with factory rom but having no luck. When trying to unlock using ADB Fastboot I get a error on screen eventually saying can not unlock.
Error says (bootloader) Device cannot be unlocked.
OKAY [41.012s]
Finished. Total time 41.012s
I can see the device when I run the command Fastboot devices.
Any suggestions would be great. Thank you
wax_786 said:
Hi I am having issue with a device which I bought and can not return. The nvidia shield pro 500GB is stuck in fastboot mode.
Every time I turn the device off and on all I get is the options you get in fast boot.
I have tried to boot recovery kernel, force recovery etc and I just get the same screen again.
I have tried to unlock the device to see if I can flash with factory rom but having no luck. When trying to unlock using ADB Fastboot I get a error on screen eventually saying can not unlock.
Error says (bootloader) Device cannot be unlocked.
OKAY [41.012s]
Finished. Total time 41.012s
I can see the device when I run the command Fastboot devices.
Any suggestions would be great. Thank you
Click to expand...
Click to collapse
Please be more specific, exactly what did you do before it got stuck in fastboot and what were or are you trying to do
I bought the nvidia shield from a auction so I haven't a clue what was done before. When I switched it on it would go straight to the boot menu and no further.
Ideally I just want to get the device to a state where it boots into the android software.
wax_786 said:
I bought the nvidia shield from a auction so I haven't a clue what was done before. When I switched it on it would go straight to the boot menu and no further.
Ideally I just want to get the device to a state where it boots into the android software.
Click to expand...
Click to collapse
my guess is someone messed it up previously and you should get the Nvidia 5.2 version flash that and then let it update to 6.0
Is it possible to flash without unlocking the bootloader?
wax_786 said:
Is it possible to flash without unlocking the bootloader?
Click to expand...
Click to collapse
wow sorry about that yeah bootloader needs to be unlocked, so you tried fastboot oem unlock and you get that error?
Yes that's the error I get when trying to unlock bootloader. That's what I need help with.
wax_786 said:
Yes that's the error I get when trying to unlock bootloader. That's what I need help with.
Click to expand...
Click to collapse
did you follow the tutorial? are your drivers updated? do you see shield in your device manager on your pc?
I followed a tutorial, I've done it before so kinda have a idea.
The device does show up in device manager, shows as android bootloader interface.
Although not sure how upto date the drivers are.
wax_786 said:
I followed a tutorial, I've done it before so kinda have a idea.
The device does show up in device manager, shows as android bootloader interface.
Although not sure how upto date the drivers are.
Click to expand...
Click to collapse
I have seen a couple people use windroid to unlock their bootloader when they ran into problems but I have no experience in that, it really sounds like the os is gone< i have had similar experience where I could get into recovery, but it would do absolutely nothing no matter what I tried, I had to rma . I know nvidia ssays if the device shows up as apx then its hardware failure
I'll give windroid a try, when you did a rma did nivida not question what had happened ?
Is there anyway I could clone another a hard drive from another nvidia with os on the drive?
wax_786 said:
I'll give windroid a try, when you did a rma did nivida not question what had happened ?
Is there anyway I could clone another a hard drive from another nvidia with os on the drive?
Click to expand...
Click to collapse
No they dont ask what happened you just tell them the problem and they run you through some steps depending on the problem and if that doesnt work they start the rma process, You can clone another drive but from what I hear netflix thats installed on the shield wont work because its console specific I believe
Looks like windroid didn't work either.
Will speak to nvidia at some point next week to see what they say. Thank you for your help & reply much appreciated.
wax_786 said:
Looks like windroid didn't work either.
Will speak to nvidia at some point next week to see what they say. Thank you for your help & reply much appreciated.
Click to expand...
Click to collapse
Welcome, sorry I couldnt do more
That's fine you gave me some advise I go away with.
One last thing could this work? I'm not too fussed about Netflix.
https://www.google.co.uk/amp/s/andr...-hard-drive-with-a-speedier-ssd-20160720/amp/
wax_786 said:
That's fine you gave me some advise I go away with.
One last thing could this work? I'm not too fussed about Netflix.
https://www.google.co.uk/amp/s/andr...-hard-drive-with-a-speedier-ssd-20160720/amp/
Click to expand...
Click to collapse
Yes it does, here is the thread https://forum.xda-developers.com/shield-tv/development/nvidia-shield-tv-ssd-t3402580
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 ?
Hello every body ,,
I’m new here to this website , i have problem with my shield tv 2017 , spent several days without having a single solution or answer , pleaee help me , and i appreciate that’s .
my young brother has flashed shield tv 2017 with android ver 6.0 for mobile phone image. by mistake , right i will can boot normally and i can play the devices as a phone , and this is not what meant to be for using shield Tv, as i’m using it as TV box .
this device is now can be bootable and i only can run bootloader through ADB minimal by cmd , not by hardware using the shield controller because is wrong ROM image for phone but i can use shield controller inside the bootable system of the wrong flashed android image for the android phone .
now to roll back to shield tv stock image i need to unlock oem through bootloader , every time i run bootloader through adb commands it’s run fine by “adb reboot bootloader” then fastboot oem unlock , everything fine to here , the problem is that’s i can’t control bootloader interface no matter for moving option up and down or choose option on bootloader to confirm unlocking , no matter by shield tv controller or usb keyboard !!! so it’s keep showing me those attached screen and even on CMD it’s showing waiting after i run command oem unlock”
so unfortunately i’m stucked here . please note that’s usb keyboard and shield controller is working fine inside the system after normal boot .
i hope any advice or help to do . thank you so much