My transformer suffered what appears to be a hardware failure today. My screen won't turn on at all. I can hear the tablet click on and off, I can see it in windows, but the screen won't turn on. Second screen issue I've had with it, there may have been a loose cable from the last time or something. I need to send it back.
I don't want to send it back with a custom rom unless I have to. I want to NVFlash back to stock. Unfortunately, I can't seem to get into APX mode, and I can't see why I'm having problems.
I can hold the power off button till I hear the click that it has turned off, and it is no longer seen by windows. Power + Volume Up, and nothing happens, or it boots normally. No idea why.
I do have a version of CWM on there that has been intercepting normal booting, so that may be causing the problems? I don't know, can someone confirm that they can get to APX mode with a bad CWM? Is there any way to fix CWM without looking? Better yet, is there a different way to boot to APX mode? Maybe through command line or something. Windows or linux. Any help would really be appreciated. The last thing I need is for them to refuse repairs, or try and charge me $100 for repairs/shipping on this tablet. At that point, the investment to fix it may not be worth it.
Finally, although I'm 99% certain it's a hardware problem due to the symptoms and the fact I haven't flashed anything for a while, I would like to be 100% sure. I don't feel any particular need for Asus to repair my device for free if I screwed it up. An NVflash to completely reset the thing would be a good way to know for sure.
Edit: Not sure if it matters, but this is a B30K serial number.
Re: My screen won't turn on at all. I can hear the tablet click on and off, I can see it in windows, but the screen won't turn on. Second screen issue I've had with it, there may have been a loose cable from the last time or something. I need to send it back.
The screen stays off in apx mode. If you can see the tab in windows, then my understanding is that you're in apx mode.
You then need to do the nvflash commands. See unbrick guides on xda for that.
http://forum.xda-developers.com/showthread.php?t=1123429
Did a little hunting and there doesn't seem to be a command to get into apx mode.
If your computer can detect it I'm not sure why it won't go into apx mode.. is the vol-up key working?
To get into APX Mode it's Vol up + power button. The screen will be black and blank (there's nothing telling you is in APX mode).
If you have the correct APX driver installed, you'll get the "ping"sound on the PC.
Your B30 should be nvflash compatible
bradysd4 said:
Re: My screen won't turn on at all. I can hear the tablet click on and off, I can see it in windows, but the screen won't turn on. Second screen issue I've had with it, there may have been a loose cable from the last time or something. I need to send it back.
The screen stays off in apx mode. If you can see the tab in windows, then my understanding is that you're in apx mode.
You then need to do the nvflash commands. See unbrick guides on xda for that.
http://forum.xda-developers.com/showthread.php?t=1123429
Click to expand...
Click to collapse
I understand that. My screen won't turn on in any mode. As is, I can't see the recovery, can't see the main OS. Anything. That is why I'm RMAing it in the first place. As for seeing the tab in windows, I see it mounting like it does on a normal boot, not in APX mode. I did try running download.bat anyway, just in case. Did not see anything mounted.
Thing O Doom said:
Did a little hunting and there doesn't seem to be a command to get into apx mode.
If your computer can detect it I'm not sure why it won't go into apx mode.. is the vol-up key working?
Click to expand...
Click to collapse
Yes, the volume up key was working. I appreciate looking for a command though. Is there perhaps an easy way to reflash the recovery to stock at least?
baseballfanz said:
To get into APX Mode it's Vol up + power button. The screen will be black and blank (there's nothing telling you is in APX mode).
If you have the correct APX driver installed, you'll get the "ping"sound on the PC.
Your B30 should be nvflash compatible
Click to expand...
Click to collapse
I do have the APX driver, it's simply not going into APX mode. I'm holding volume and power. I'm aware there's nothing to tell me I'm in APX mode. However, there's currently nothing on screen at all in any mode. That's my problem. The screen isn't working at all, so it's very difficult for me to tell if I've gone into some mode besides APX. I'm hoping there is another way to get into APX I can try, or at least a way to flash stock recovery easily.
alright, can you get into normal cwm recovery?
If you memorized the screens very carefully you could wipe data and flash a stockrom/recovery.
Sorry that's about all I can think of at this point.
Does the HDMI-out port work? you could cable out and use that to navigate easily.
If you can get into adb in recovery then you can flash anything you want through the staging partition. It sounds like you have the recovery bootloops, so you'll have to clear out the reboot command in the /misc partition. Search for the troubleshooting thread for cwm 5.5.0.4 in the dev section(I think?) to fix the bootloops. Then search for how to flash blobs through the staging partition. viola! easy as pie!
Of course, you might get APX mode back after you fix the bootloops, then you can skip the blob and flash via nvflash.
Thing O Doom said:
alright, can you get into normal cwm recovery?
If you memorized the screens very carefully you could wipe data and flash a stockrom/recovery.
Sorry that's about all I can think of at this point.
Does the HDMI-out port work? you could cable out and use that to navigate easily.
Click to expand...
Click to collapse
I have been trying along these lines. It is very confusing though. If someone was able to guide me through the button presses of getting to factor reset, and getting to the filesystem when choosing what to flash. I imagine I could just name whatever I needed to flash zzzzzzz.zip and simply pressing up at the top of the lest would get me too it. Oh, and how many times I need to press down to get to yes I want to flash.
I don't believe the HDMI out is active that early on. Worth a shot I guess.
gee one said:
If you can get into adb in recovery then you can flash anything you want through the staging partition. It sounds like you have the recovery bootloops, so you'll have to clear out the reboot command in the /misc partition. Search for the troubleshooting thread for cwm 5.5.0.4 in the dev section(I think?) to fix the bootloops. Then search for how to flash blobs through the staging partition. viola! easy as pie!
Of course, you might get APX mode back after you fix the bootloops, then you can skip the blob and flash via nvflash.
Click to expand...
Click to collapse
Thanks, I'll try that.
Edit: I'm looking for the troubleshooting thread, and cannot find it. Does anyone have a link?
Not sure how, but I managed to get it to boot to APX. Everythings good now, minus the hardware problems. Time for a second screen-related RMA.
Related
So I have my TF101, updated to the ICS release when it came out, rooted of course.
Since then it was kind of unstable. When not using the device it would appear to power off, but pressing the power button for about 10 seconds would bring it back up.
I noticed the recovery was not available after the update, but paid it no mind for that time.
Then out of nowhere the device screen will not turn on. After long pressing the power button a click noise can be heard, it's supposed to be the camera. Since it wasn't responding, I though it was bricked.
Then connecting it to the PC will let me access all the files on the device, something very weird.
I have tried various combinations of things after a very long and tedious search, nothing seems to work.
Here are the symptoms:
-The device is turned on, but no backlight or sound.
-When long pressing the power button click sound is heard.
-When connected to the PC via usb the files on the device can be accessed.
-ADB is accessible and the device can be rebooted via it.
-After rebooting the device via the power button or ADB usb comes up almost immediately, I don't think this happens when booting normally.
So basically, is the device bricked? Why can I access files from it? How can I push a working recovery for the TF101? Is it possible to flash a ROM from ADB?
I know these are a lot of questions, but I tried, and failed. Haven't found a case like this online, and my ADB experience is limited to adb shell and reboot
Thanks in advance for the help!
Hi Cronoadvan,
looks like your screen is dead, if you check q&A you see that more people have the same thing lately.
Is your device SBK1? so, are you able to use nvflash?
Cronoadvan said:
So I have my TF101, updated to the ICS release when it came out, rooted of course.
Since then it was kind of unstable. When not using the device it would appear to power off, but pressing the power button for about 10 seconds would bring it back up.
I noticed the recovery was not available after the update, but paid it no mind for that time.
Then out of nowhere the device screen will not turn on. After long pressing the power button a click noise can be heard, it's supposed to be the camera. Since it wasn't responding, I though it was bricked.
Then connecting it to the PC will let me access all the files on the device, something very weird.
I have tried various combinations of things after a very long and tedious search, nothing seems to work.
Here are the symptoms:
-The device is turned on, but no backlight or sound.
-When long pressing the power button click sound is heard.
-When connected to the PC via usb the files on the device can be accessed.
-ADB is accessible and the device can be rebooted via it.
-After rebooting the device via the power button or ADB usb comes up almost immediately, I don't think this happens when booting normally.
So basically, is the device bricked? Why can I access files from it? How can I push a working recovery for the TF101? Is it possible to flash a ROM from ADB?
I know these are a lot of questions, but I tried, and failed. Haven't found a case like this online, and my ADB experience is limited to adb shell and reboot
Thanks in advance for the help!
Click to expand...
Click to collapse
Since no ASUS logo is displayed, it is likely a hardware problem. Maybe you can try to bring it into recovery mode by pressing power + vol down button.
nlheiz said:
Hi Cronoadvan,
looks like your screen is dead, if you check q&A you see that more people have the same thing lately.
Is your device SBK1? so, are you able to use nvflash?
Click to expand...
Click to collapse
I am not sure, how do I check that? nvflash, at least the version I'm trying to use, won't run on win764? It's rather confusing.
tingtan said:
Since no ASUS logo is displayed, it is likely a hardware problem. Maybe you can try to bring it into recovery mode by pressing power + vol down button.
Click to expand...
Click to collapse
The screen does not light up at all, and USB is accessible after around 4 secs of long pressing power and hearing the click noise(camera?) which is not normal since no device boots so fast. This tablet never did anyway, taking from 20 to 30 secs.
After USB is available I can adb shell from windows but that's pretty much it, I don't know what to do afterwards.
Cronoadvan said:
I am not sure, how do I check that? nvflash, at least the version I'm trying to use, won't run on win764? It's rather confusing.
Click to expand...
Click to collapse
Check your serial number. If its below B70 you got SBK1.
Goatshocker said:
Check your serial number. If its below B70 you got SBK1.
Click to expand...
Click to collapse
Yes it is, it's B50. Is that a bad thing?
Cronoadvan said:
Yes it is, it's B50. Is that a bad thing?
Click to expand...
Click to collapse
Hi Cronoadvan,
thats not bad, this means that you could use nvflash to put a new image on your TF if you want to to make sure that it is working. If you use this forum:
http://forum.xda-developers.com/showthread.php?t=1558170
then it wil be stock again, and if needed you can then send your TF back for repair.
If you look and search in development you will find some ways how to use nvflash. like this one
http://forum.xda-developers.com/showthread.php?p=22465766
Hope this helps.....
nlheiz said:
Hi Cronoadvan,
thats not bad, this means that you could use nvflash to put a new image on your TF if you want to to make sure that it is working. If you use this forum:
http://forum.xda-developers.com/showthread.php?t=1558170
then it wil be stock again, and if needed you can then send your TF back for repair.
If you look and search in development you will find some ways how to use nvflash. like this one
http://forum.xda-developers.com/showthread.php?p=22465766
Hope this helps.....
Click to expand...
Click to collapse
Thank you so much! That was my last resort and sadly was clueless on how to do that too!
Hopefully it's just some kind of weird software coma, but now even if it's a hardware problem there is still hope!
Thank you very much good Sir, may life repay you thrice as much
Your welcome......please read the apx and nvflash option really well. It is rather straightforward but you have to install the apx drivers correct and use power and volume + (together) to enter apx mode. Voor drivers maybe you can use this forum below:
http://forum.xda-developers.com/showthread.php?t=1185104
it had an option for installing apx drivers for win 7 64 bit.
Hope your screen will work again, and if not you can send it back without warrant loss...
good luck!!!!!
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
If you can boot to OS - you can use fastboot to flash any recovery.. or flash TWRP from goomanager.
upd: sry..don't see about "stuck".
abe_cedar said:
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
Click to expand...
Click to collapse
I have made the same mistake. Although I can get the device to fastboot USB mode. I have tried to use CWM with the restore I made before I put in Cyanogenmod 9, as well as putting on the Cyanogenmod experimental #2 for TF300. No error messages at all and it wipes data and cash without any problems.
But I get locked on the Asus boot screen and it does not continue ie I am stuck as well.
I have as well tried to use the TWRP 2.1.5. I get the Teamwin loggo screen, it wipes all the data and verifies all the filesystems and reboots. Still stuck.
Is the device bricked ?
upd:The TF300 can not be shutoff either. When you hold the power button the screen goes black, but after ~5 s the device is starting again and is still stuck on the Asus bootup screen.
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
cheedear said:
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
Click to expand...
Click to collapse
Yes, I can get access to the fastboot and I have already tried to flash with the recovery.img. I have as well let the battery run out and tried it once more with the same result.
Still stuck on the asus bootup screen.
power
Hare,
I have same problem.tab cannot power off. Just reboots into cwm.
I was thinking to drain bat. Thanks for sharing that info.
There are a lot of topics about people who broke their devices with TF201's recovery.
Afaik, no one recovered it. Send to Asus.
So the device is bricked then :'(.
Thanks for clearing it up.
Sent from my GT-I9100 using XDA
RMA..
Guillaume,
Thanks for clarification.
I have read that ASUS wants 700USD for replacing/reflashing the bootloader. That was for the tf201. Any way to nvflash it back to factory? I don't believe that they have to change the MB.
I have no warranty left, but I don't want to be gouged by them either.
Any thoughts, info?
Hi,
I've do the same mistake, but I can use adb.
Do youhave any news about our problem?
Thanks
Midyr
unable to power off
My issue is that I have the CWM for the tf201. I did the update from the CWM app in Android. Bad idea. So now the tab does not power off s.t. I can get into the power+vol down mode. Adb does not work since I cannot ( don't know how) to make it go into the usb debugging mode. I have tried several things none of which have worked. Still stuck.
I wanted some feedback for a RMA from ASUS, posted it here but sor far no answers.
Not sure if it would really work, but on my Evo, I don't have to completely power off the phone to do the recovery sequence. I can do it during a normal reboot. There is a point just before the device starts booting again where it is technically "off", and if I hold volume down (don't even have to hold power on my Evo; volume down seems to be the only necessary button) starting at this point, the phone will boot into the bootloader.
So, next time the device reboots, just start holding volume down (possibly power also, just in case) at the "off" point.
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.
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