Related
I hope I can save it but after 4 hours of trying and reading I can't seem to do it.
I was running an unlocked tf300 with cleanrom. I wanted to update to the newest version of cleanrom and have my tablet on that and ready for school for next term. I downloaded cleanrom on laptop and put it on my micro sd. Went and grabbed the tablet and tried using rom manager to install from sd and backup the os that was on it. Didn't work. So booted into the fastboot spot (vol down and power) and decided i should wipe data since i was there. Went over to that and pushed vol up (once). Let it sit for like 45 minutes and was still on the same screen. Thought to myself well it must be done. Shut off the tablet to restart it.
This is where the problem came up. Now i'm stuck on asus logo. The VD+P doesn't do anything but reboot into the asus logo. The VU+P will put it into a black screen and windows sees it as Asus transformer Prime APX interface. But adb can't see the device. Just device manager. typing fastboot -i 0x0b05 thing just says <waiting for device>
Every post i've read seems to tell people to just push VD+P but if i could do that and get to recovery i wouldn't be doing this. I can't put a blob file into the root sd of the tablet because I can't see the tablet.
Any help would be greatly appreciated.
Maybe this link can help.
http://forum.xda-developers.com/showthread.php?t=2034866
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
bigworm82 said:
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
Click to expand...
Click to collapse
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
tobdaryl said:
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
Click to expand...
Click to collapse
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
bigworm82 said:
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
Click to expand...
Click to collapse
Are you in fastboot mode or apx when you give the commands?
tobdaryl said:
Are you in fastboot mode or apx when you give the commands?
Click to expand...
Click to collapse
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
bigworm82 said:
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
Click to expand...
Click to collapse
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
tobdaryl said:
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
Click to expand...
Click to collapse
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
bigworm82 said:
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
Click to expand...
Click to collapse
apx or bootloader menu-recovery.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard) reset is located about 25mm or 1in below the sdcard
try this one.
tobdaryl said:
apx or bootloader menu-recovery.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
try this one.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
Click to expand...
Click to collapse
nope just back to asus logo
bigworm82 said:
nope just back to asus logo
Click to expand...
Click to collapse
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
tobdaryl said:
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
Click to expand...
Click to collapse
Device not found.
bigworm82 said:
Device not found.
Click to expand...
Click to collapse
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
tobdaryl said:
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
Click to expand...
Click to collapse
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
bigworm82 said:
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
Click to expand...
Click to collapse
I'm sorry, I did understand that from the beginning but the only things that can save you is get into that menu or recovery or your tab accepts a fastboot or adb command. That is the reason you keep getting pushed into that direction.
My best guesses are out. Sometimes redoing something you have already done twice works.
My experience and all I have read rom manager has issues on this tab. Also many who wiped data from the bootloader- recovery menu reach this same point when they reboot.
Some have recovered by just doing each thing again and again and suddenly something works.
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
bigworm82 said:
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
Click to expand...
Click to collapse
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
tobdaryl said:
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
Click to expand...
Click to collapse
I appreciate the attempts though . I really didn't want to have to call them lol.
bigworm82 said:
I appreciate the attempts though . I really didn't want to have to call them lol.
Click to expand...
Click to collapse
If you explain you were having issues with your tab and used wipe data hoping to correct the problem. Now when you turn on it just stays on the asus logo maybe they will repair it without cost.
If you go into detail you probably won't get lucky.
WHats up guys? My tf300 is still bricked after like 6 months. It started with me flashing the wrong recovery image then a wipe data finished it off. I can get into apx mode and device manager sees it as an apx device with a yellow triangle, or as several different names according to which driver i use. I have tried all the asus ones, the adb, the composite adb, all the ones from the naked driver set. No matter which ones i use fastboot devices returns nothing and adb devices says "list of devices attatched but nothing. Is there something wrong with the way im using fastboot? I just go to the fastboot folder and open a cmd window and it starts like C:\user\fastboot or whatever and im stuck there please help
jerimynal wiley said:
WHats up guys? My tf300 is still bricked after like 6 months. It started with me flashing the wrong recovery image then a wipe data finished it off. I can get into apx mode and device manager sees it as an apx device with a yellow triangle, or as several different names according to which driver i use. I have tried all the asus ones, the adb, the composite adb, all the ones from the naked driver set. No matter which ones i use fastboot devices returns nothing and adb devices says "list of devices attatched but nothing. Is there something wrong with the way im using fastboot? I just go to the fastboot folder and open a cmd window and it starts like C:\user\fastboot or whatever and im stuck there please help
Click to expand...
Click to collapse
Questions: what rom did you have before? Did you wipe data from the Asus menu, and not from inside a custom recovery? When you now try to get into fastboot by holding volume down + power, what happens? No matter what, try Buster99's solution. If the only mode you can get into is APX, and you didn't generate NVflash files, then I'm afraid your motherboard is stuck, the only solution to which is replacing it.
graphdarnell said:
Questions: what rom did you have before? Did you wipe data from the Asus menu, and not from inside a custom recovery? When you now try to get into fastboot by holding volume down + power, what happens? No matter what, try Buster99's solution. If the only mode you can get into is APX, and you didn't generate NVflash files, then I'm afraid your motherboard is stuck, the only solution to which is replacing it.
Click to expand...
Click to collapse
i came from stock jb rom and i flashed an ics cwm recovery img i got into the bootloader screen but it wouldnt go into recovery so for some stupid reason i did a wipe from there, from the asus menu. volume down and power just shuts the screen off for a few seconds then straight back to the asus screen volume up and power will apx mode. the driver i had got from asus pulled up transformer prime apx interface in device manager
jerimynal wiley said:
i came from stock jb rom and i flashed an ics cwm recovery img i got into the bootloader screen but it wouldnt go into recovery so for some stupid reason i did a wipe from there, from the asus menu. volume down and power just shuts the screen off for a few seconds then straight back to the asus screen volume up and power will apx mode. the driver i had got from asus pulled up transformer prime apx interface in device manager
Click to expand...
Click to collapse
Must've been the wrong recovery that screwed up your tab. In my experience, wiping data from the Asus menu while you're on stock rom is not supposed to brick it as described by you. Try this method. It has saved quite a few semi-dead tabs. Good luck, and give thanks to the author if it helps.
graphdarnell said:
Must've been the wrong recovery that screwed up your tab. In my experience, wiping data from the Asus menu while you're on stock rom is not supposed to brick it as described by you. Try this method. It has saved quite a few semi-dead tabs. Good luck, and give thanks to the author if it helps.
Click to expand...
Click to collapse
im sure it was the wrong recovery i dont know why i did it. i had another ics tablet and for some reasone i put both recovery images in the same folder the link u provided is one that i had previously read. I cant even get fastboot to "see" the tablet.
TF300T was running CM 10.2 with TWRP recovery before it was bricked. While installing CM 11, I installed CWM recovery over TWRP for the installation to be successful but that's when the tablet got bricked. The tablet is unlocked and when powered on it's stuck on the "ASUS logo" in the center and "the device is unlocked" in the top left corner.
The tablet won't boot into fastboot or adb either, but it's detected by the computer (Windows 8.1 Pro x64) in APX mode. I do not have NVFlash back up, so can't use NVFlash either.
I have removed the back cover, unplugged the battery and still no go. I have drained the battery completely a couple of times, still no go. Also, I have followed the thread http://forum.xda-developers.com/showthread.php?t=2034866 ([GUIDE] How to enter APX mode or Bootloader menu) which helped me get into the APX mode, but no go for the bootlooader menu.
Moreover, I also followed the thread http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12, but still no go.
While searching, I can across this video http://www.youtube.com/watch?v=I2PMJcAKSe0 but it's only for ASUS TF101. Can someone please create the same program but for TF300T or is there any other way to unbrick the tablet in APX mode?
Iscarecomputers said:
TF300T was running CM 10.2 with TWRP recovery before it was bricked. While installing CM 11, I installed CWM recovery over TWRP for the installation to be successful but that's when the tablet got bricked. The tablet is unlocked and when powered on it's stuck on the "ASUS logo" in the center and "the device is unlocked" in the top left corner.
The tablet won't boot into fastboot or adb either, but it's detected by the computer (Windows 8.1 Pro x64) in APX mode. I do not have NVFlash back up, so can't use NVFlash either.
I have removed the back cover, unplugged the battery and still no go. I have drained the battery completely a couple of times, still no go. Also, I have followed the thread http://forum.xda-developers.com/showthread.php?t=2034866 ([GUIDE] How to enter APX mode or Bootloader menu) which helped me get into the APX mode, but no go for the bootlooader menu.
Moreover, I also followed the thread http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12, but still no go.
While searching, I can across this video http://www.youtube.com/watch?v=I2PMJcAKSe0 but it's only for ASUS TF101. Can someone please create the same program but for TF300T or is there any other way to unbrick the tablet in APX mode?
Click to expand...
Click to collapse
In order to unbrick in APX mode, you need to have made NvFlash Backups prior to bricking. That is the only way to get into APX mode. The blank screen you get while pressing vol up means that the tablet is ready to enter, not that it has entered. If you made the bin.blob backuo, you can look here: http://forum.xda-developers.com/showpost.php?p=47903957&postcount=2. Otherwise, APX mode will not serve you any good.
cmendonc2 said:
In order to unbrick in APX mode, you need to have made NvFlash Backups prior to bricking. That is the only way to get into APX mode. The blank screen you get while pressing vol up means that the tablet is ready to enter, not that it has entered. If you made the bin.blob backuo, you can look here: http://forum.xda-developers.com/showpost.php?p=47903957&postcount=2. Otherwise, APX mode will not serve you any good.
Click to expand...
Click to collapse
As I mentioned in my first post, I do not have NvFlash backup. However, I am able to get into APX mode and the computer detects the tablet in APX mode. Moreover, the tablet is shown in "Devices and Printers" option in Control Panel on the computer as "Asus APX" or something similar to that name.
I hope there is a way to unbrick the tablet in APX mode without NvFlash backup, as someone created something on those lines in the youtube video I posted in my first post. Any help from any developers or members would be awesome. Thank you.
Iscarecomputers said:
As I mentioned in my first post, I do not have NvFlash backup. However, I am able to get into APX mode and the computer detects the tablet in APX mode. Moreover, the tablet is shown in "Devices and Printers" option in Control Panel on the computer as "Asus APX" or something similar to that name.
I hope there is a way to unbrick the tablet in APX mode without NvFlash backup, as someone created something on those lines in the youtube video I posted in my first post. Any help from any developers or members would be awesome. Thank you.
Click to expand...
Click to collapse
The easy flasher from the first post requires you to use the blob.bin extracted from the tf101, so it is the same concept. APX mode, as of now, will only be useful if you made those backups.
cmendonc2 said:
The easy flasher from the first post requires you to use the blob.bin extracted from the tf101, so it is the same concept. APX mode, as of now, will only be useful if you made those backups.
Click to expand...
Click to collapse
Gotcha. I do have the blob file, but it's from WW_epad-user-10.6.1.15.3.
Hopefully, someone can come up with a solution or a fix for such an issue. Will be waiting.
I have the same problem! there are no solution? I don't have backup
So I was doing something on my tablet, and it shut down.
I tried to reboot it and it was stuck.
I thought i had my rom on it (KatKiss) so i did a factory reset and tried to flash it but then i saw i deleted it when i flashed it at first.
So i thought ill just use EasyFlasher and get it back up and running.
Then I tried to get into APX mode and failed.
Volup + Power = Nothing
It just powers on the tablet and it stays there at the Asus logo.
I tried to hold it for 20+ seconds, nothing.
USB is plugged into the tablet, not the dock.
Tried to use sdcard to flash rom on it, cwm cant mount sdcards...
So if anyone could help it would be great
CWM bricked your tablet most likely - you should be running TWRP Recovery for KatKiss ROMs
You need to get the tablet into APX and get EasyFlasher working - APX should still work, nothing appears on the TF screen in APX mode, only way you know it is working is USB connect sound / device connected notification on PC
Keep in mind - APX is a black screen. The only way to know you are in APX is to see if a PC detects an APX device.
frederuco said:
Keep in mind - APX is a black screen. The only way to know you are in APX is to see if a PC detects an APX device.
Click to expand...
Click to collapse
*Detection* said:
CWM bricked your tablet most likely - you should be running TWRP Recovery for KatKiss ROMs
You need to get the tablet into APX and get EasyFlasher working - APX should still work, nothing appears on the TF screen in APX mode, only way you know it is working is USB connect sound / device connected notification on PC
Click to expand...
Click to collapse
I know APX is just a black screen, but even if i try to do it while usb is plugged in it just reboots to Asus logo.
You sure your volume up button is working ok ?
Try removing the plastic bezel around the edge of the tablet and press the actual micro-buttons under the silver ones you normally press
*Detection* said:
You sure your volume up button is working ok ?
Try removing the plastic bezel around the edge of the tablet and press the actual micro-buttons under the silver ones you normally press
Click to expand...
Click to collapse
I am dead sure its working, when im in cwm i can navigate with both of volume buttons.
welja99 said:
I am dead sure its working, when im in cwm i can navigate with both of volume buttons.
Click to expand...
Click to collapse
Make sure you have the correct drivers for APX mode. I got mine from x3maniac's Tubuntu - One Click Installer for Windows
From this thread
http://forum.xda-developers.com/showthread.php?t=1995157
In the package, there are the drivers and also a flashing program(NVFlash). You can also use this. Even have a APX mode detected status at the top so you don't have to do the guessing work that it's in APX or not.
P/s: Just to confirm, to go into APX mode 1) Turn on your tablet(not necessary to wait till it boots) 2) Hold the power and volume up button until it shuts down and keep holding the buttons until you see it is detected as APX mode on your computer.
APX mode is from a powered off state:
Hold Volume Up & Power until PC recognises it
Done
unplug and boot apx
I usually boot apx and then plug in the usb shortly after. Also note that occasionally a grounding issue occurs (happens with my bull**** Dell Venue). Run a piece of metal across the usb pins while the tablet is off and try again after ensuring the device is charged.
Good day everyone, here is my issue.
I bought the nVidia Shield WiFi 16G and didn't do any modification to it at all (original bootloader, straight out the box)
I tried to do the OTA updates and it kept freezing at the nvidia logo.
Force shut down and bootloader to Recovery mode.
The update 1.2.1 installed when it started to boot (little android guy with the thing spinning in his chest).
Update 2.1 same issue.
I repeat the steps. Everything seemed fine as well, the loading bar finished.
Then the screen went black... pressing any button doesn't do anything. So I decide to plug it in my PC.
It says APX Driver can't be found (recognized that way by PC)
Screen is black
Cannot get in bootloader by pressing power & volume-.
I can turn on/off the tablet (I get the sound that it disconnect from my PC) by holding power button down.
Then pressing power & volume+ together, it connects again. Still Black screen.
I read a bunch of forum about the NVflash and nothing seems to work, all the process require me to go in Bootloader which I cannot access.
I am able to install drivers for the tablet to be recognized, but there is so many of them that I am not even sure they are the right one.
When I try the NVflash solutions, my command prompt says "fastboot" unrecognized command.
Nothing is working.... I need help
Thank you in advance
Wicstar said:
When I try the NVflash solutions, my command prompt says "fastboot" unrecognized command.
Click to expand...
Click to collapse
Do you have fastboot on your computer?
danjull said:
Do you have fastboot on your computer?
Click to expand...
Click to collapse
I thought Fastboot was a mode I had to put my tablet in...
Where can I find it ?
Minimal ADB + Fastboot
Here, follow instruccions:
http://forum.xda-developers.com/showthread.php?t=2317790
albertorodast2007 said:
Here, follow instruccions:
http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Ok so I have installed Fastbood and Minimal ADB.
For some reason, the NVidia website wants me to register as a Dev now to download the image of my tablet...
Anywhere I could find the image to nvflash ?
I am downloading the Linux version right now, 2.2Gb, will that be alright ? I am running Windows 7
Oh and the command prompt keep saying error: device not found when I type: adb reboot bootloader
This is frustrating....
Wicstar said:
Ok so I have installed Fastbood and Minimal ADB.
For some reason, the NVidia website wants me to register as a Dev now to download the image of my tablet...
Anywhere I could find the image to nvflash ?
I am downloading the Linux version right now, 2.2Gb, will that be alright ? I am running Windows 7
Oh and the command prompt keep saying error: device not found when I type: adb reboot bootloader
This is frustrating....
Click to expand...
Click to collapse
If you're not getting passed the bootloader, you're not getting adb access. Booting up by holding power and volume will get you in bootloader mode and fastboot should work.
danjull said:
If you're not getting passed the bootloader, you're not getting adb access. Booting up by holding power and volume will get you in bootloader mode and fastboot should work.
Click to expand...
Click to collapse
There is no bootloader for me.
Power button does nothing.
Power & volume down does nothing (no bootloader comes up, it was doing it the first time I got the tablet)
Power & volume up (while connected to PC) will connect to the computer as APX.
Holding power once in APX mode disconnect from the PC.
Those are the only thing happening with the tablet.
Black screen lol
Wicstar said:
There is no bootloader for me.
Power button does nothing.
Power & volume down does nothing (no bootloader comes up, it was doing it the first time I got the tablet)
Power & volume up (while connected to PC) will connect to the computer as APX.
Holding power once in APX mode disconnect from the PC.
Those are the only thing happening with the tablet.
Black screen lol
Click to expand...
Click to collapse
Sounds to me like you've got two options. Either a) Get the apx driver for windows, get it in apx mode and run nvflash. Or b) contact nvidia and get it swapped out.
I had a similar experience with another device. It shipped slightly damaged and when I tried to update it locked me out of my phone. Had to rma it....
danjull said:
Sounds to me like you've got two options. Either a) Get the apx driver for windows, get it in apx mode and run nvflash. Or b) contact nvidia and get it swapped out.
Click to expand...
Click to collapse
Well it seems to be in APX mode already.
I tried different drivers, but having the right one would help me out a bunch (I have the Shield tablet WIFI 16G)
not sure how to run nvflash. Everywhere I look they ask to access to the bootloader, which I don't have access to. And I am not sure where to get it, I found different version on different website.
A bit of help would help tons!
Wicstar said:
Well it seems to be in APX mode already.
I tried different drivers, but having the right one would help me out a bunch (I have the Shield tablet WIFI 16G)
not sure how to run nvflash. Everywhere I look they ask to access to the bootloader, which I don't have access to. And I am not sure where to get it, I found different version on different website.
A bit of help would help tons!
Click to expand...
Click to collapse
Did you ever get this figured out, it would appear I'm now in the same boat.
Mav3rek said:
Did you ever get this figured out, it would appear I'm now in the same boat.
Click to expand...
Click to collapse
I have this problem too. My device not start in fastboot mode - when i pressed Power+Volume down - tablet go on, logo nvidia, and power off, in normal mode not start, after logo nvidia, start launcher and message power off, and shutdown
My way in APX mode only, but how can i flash in this mode????
_SkyDreamer_ said:
I have this problem too. My device not start in fastboot mode - when i pressed Power+Volume down - tablet go on, logo nvidia, and power off, in normal mode not start, after logo nvidia, start launcher and message power off, and shutdown
My way in APX mode only, but how can i flash in this mode????
Click to expand...
Click to collapse
I too fell to the dark side and aquired this problem. You intelligent people, please solve it for me. I cant find any APX-drivers out there.
Yep my first shield did the same thing and I had to send it back because I couldn't figure out any way to get to bootloader nor fastboot, just a black screen.
My second shield had blown speakers due to that 3.0 update failure and finally the latest update works good with my 3rd tablet, thankfully I don't have the battery recall.
Sent from my SHIELD Tablet using XDA Free mobile app
All these problems you are all facing is the killswitch made by Nvidia for the recalled tablets. They render them unusable so you are forced to return/dispose of.
So far, there is no way to fix them, being necessary a special driver that only Nvidia has.
Hi I have a Shield Tablet killed by NVidia. Working on it, I created APX drivers to make this tablet recognized by Windows. I don't know if drivers work really as I wish... I created them basing on Universal Driver Naked (APX Version). But the only thing is that any nvflash tool that I tried doesn't work and one gave me error 0x30011 (I think it is device not connected). So this work is so hard...
Shield
Hi, same since 1st september, black screen+APX forever. I'm on Linux with nvflash version from Transformer LinuxTools.
Usually no need of drivers on linux so I give it a try. With '-r' stay on [resume mode] message, '--go' Error 0x8 and '-bl bootloader.img' Unknown device. Where did you find your nvflash version ? maybe mine is wrong or too old.
But what is fun is when I disconnect the Shield, I have a greetings from nvflash command line so Shield is alive...
Last thing I did with was playing with DS4/PS4 controller wired on usb by an app bought on store. Not rooted so I'm confuse but the Shield was plugged in charge since a week maybe the mistake. So I try to manually update/boot through APX, no way with pwr & buttons.
I found them googling and I tried tegra3 and 5.1.x (that I understood it is for GPU NVidia). So I haven't tried right version i think... I don't know even which one are good for me I'll see on linux what happens (if I can install it)
TDP 3.0r3/4 have nvflash and APX drivers (and I'd assume the Jetson TK1 OS images have them too). but, as repeatedly mentioned on these forums, these are all useless without the SBK that is unique to each device, and that only Nvidia knows
Bogdacutu said:
TDP 3.0r3/4 have nvflash and APX drivers (and I'd assume the Jetson TK1 OS images have them too). but, as repeatedly mentioned on these forums, these are all useless without the SBK that is unique to each device, and that only Nvidia knows
Click to expand...
Click to collapse
@Bogdacutu
can you dump a copy of the bootloader and post it?
m