Related
I just got my TF300 on Wednesday, and it decided to get stuck on the boot screen.I have rooted, but NOT unlocked this transformer. I do NOT have CWM, or any working access to ADB and fastboot.Using the Power + Vol Down for the RCK results in an Android on its back with a Red Exclamation. Continuing on past the RCK Screen, it gives two options (No USB Icon), one to wipe and one to cold boot Android. Neither have those has worked. I also let the TF300 completely drain itself, and fully recharged and still has not worked. Windows 7 reports that the TF300 as an "Asus Android MTP Device", but giving an error code of 10, which is "The device cannot start". I have not seen any ADB devices either.
I also have tried to put the latest firmware (.30) onto a microSD card, and booting into all the available options with nothing working.
Does anyone have any ideas on how to at least get ADB and/or fastboot running?
Condemned08 said:
I just got my TF300 on Wednesday, and it decided to get stuck on the boot screen.I have rooted, but NOT unlocked this transformer. I do NOT have CWM, or any working access to ADB and fastboot.Using the Power + Vol Down for the RCK results in an Android on its back with a Red Exclamation. Continuing on past the RCK Screen, it gives two options (No USB Icon), one to wipe and one to cold boot Android. Neither have those has worked. I also let the TF300 completely drain itself, and fully recharged and still has not worked. Windows 7 reports that the TF300 as an "Asus Android MTP Device", but giving an error code of 10, which is "The device cannot start". I have not seen any ADB devices either.
I also have tried to put the latest firmware (.30) onto a microSD card, and booting into all the available options with nothing working.
Does anyone have any ideas on how to at least get ADB and/or fastboot running?
Click to expand...
Click to collapse
Only option without FB and ADB is choose wipe with Vol- and the press Vol+ to do the wipe.
Then try reboot.
But you should have ADB at least. We will try out that later.
http://forum.xda-developers.com/showthread.php?t=1777203
This works TF700
zeus34 said:
http://forum.xda-developers.com/showthread.php?t=1777203
This works TF700
Click to expand...
Click to collapse
How do you have to name the update on a tf300?
SWame name then on a 700?
mikaole said:
Only option without FB and ADB is choose wipe with Vol- and the press Vol+ to do the wipe.
Then try reboot.
But you should have ADB at least. We will try out that later.
Click to expand...
Click to collapse
I have already tried that, but it just ends up being stuck on the boot.
Also, I would like to know if the filename should be the same as the TF700 for the FW update.
EDIT: The filename should be the same! It did actually work how it was specified. I'm on the boot screen waiting for the progress bar to finish, but it looks promising.
Appreciate the help guys!
Edit 2: Well she boots up perfectly now, I just need to do it again because its in Chinese, so I made a mistake somewhere.. anyways, Thanks for the help!
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.
Messed up big time and have surely bricked my device (permanently). Was trying to install Omni ROM on it. (Had it rooted, unlocked it, couldn't enter recovery then, kept getting error. tried to flash TWRP recovery 2.6.3.0 using terminal on tab, reset the tab, and we get where i am now)
Now all i get when i switch on my tab is an ASUS start screen with "The device is unlocked" message on the top left, and it just stays there. Same thing happens when start it with hold power button and volume down key or reset and volume down key. But when i press reset and volume UP key, the pc recognizes the tab, and i can install the driver either as:
1. ADB interface
2. Bootloader interface
3. Composte ADB interface
and the device comes up as an APX.
Tried to follow Buster99's method (of unbricking for TF300T) after the device drivers are installed, but all i get is <waiting for device>
Any hope of recovering it or am i really fckd.
true_lies said:
Messed up big time and have surely bricked my device (permanently). Was trying to install Omni ROM on it. (Had it rooted, unlocked it, couldn't enter recovery then, kept getting error. tried to flash TWRP recovery 2.6.3.0 using terminal on tab, reset the tab, and we get where i am now)
Now all i get when i switch on my tab is an ASUS start screen with "The device is unlocked" message on the top left, and it just stays there. Same thing happens when start it with hold power button and volume down key or reset and volume down key. But when i press reset and volume UP key, the pc recognizes the tab, and i can install the driver either as:
1. ADB interface
2. Bootloader interface
3. Composte ADB interface
and the device comes up as an APX.
Tried to follow Buster99's method (of unbricking for TF300T) after the device drivers are installed, but all i get is <waiting for device>
Any hope of recovering it or am i really fckd.
Click to expand...
Click to collapse
Shoot me an email here [email protected]
Lets see if we can get you fixed up....
Thx Josh
lj50036 said:
Shoot me an email here [email protected]
Lets see if we can get you fixed up....
Thx Josh
Click to expand...
Click to collapse
My ME310T is bricked as well and I am not sure of what to do since using the pin hole to reset does not work.
It kept booting to the ASUS logo and I downloaded software from the ASUS site and put on my SD card and tried to load the new firmware/software. Now I only get a green android on his back with a red brick.
Please help, thanks
My ME310T
Bricked mine last night My ME310T, accidentally did the wipe from the Bootscreen with the RCK ,, now i tried everything i could find , ADB, Nvflash, power+ Vol - ( no go) reset + vol- nogo, only can get it to Vol+ and APX. All i get is the Boot unlocked in upper left , and Asus Innovation.. or blank screen with APX .. Any help would be great ,,,
thsire said:
Bricked mine last night My ME310T, accidentally did the wipe from the Bootscreen with the RCK ,, now i tried everything i could find , ADB, Nvflash, power+ Vol - ( no go) reset + vol- nogo, only can get it to Vol+ and APX. All i get is the Boot unlocked in upper left , and Asus Innovation.. or blank screen with APX .. Any help would be great ,,,
Click to expand...
Click to collapse
When do you get adb ?
lj50036 said:
When do you get adb ?
Click to expand...
Click to collapse
If you mean what do i get? , just hangs with blinking curser ,,,, i think im total bricked only can get APX mode..
thsire said:
If you mean what do i get? , just hangs with blinking curser ,,,, i think im total bricked only can get APX mode..
Click to expand...
Click to collapse
So no bootloader no recovery just APX ?
That is to bad, sorry to here that.
Thx Josh
Omnirom on ME301T,
Hi,
I have a working ME301T with the latest (yesterday!) Omnirom on it, but......
I broke the glass when I was opening the device to replace a broken speaker.
I found (google is my friend) that these broken speakers cause a crash or reboot every now and then, the rubber comes loose, then the winding cause a short circuit when playing music, that crashes the unit.
So if you want to take your speaker and screen, and use our electronics, you have a working unit again.
Send me a PM with an offer if you are interested.
Un saludo from Spain,
Satbeginner
bricked me301t
Im in need of some help i have an unlocked and rooted me301t went to do a factory reset from the stock recovery screen and when it rebooted all i get is the asus screen and your device is unlocked in the upper left corner. Tried to boot into recovery wont do anything except the asus screen . Tried to put firmware on my sd card but dont know the sku because i cant get to it. can anyone help me to recover this thing and get it working again?/ Thanks in advance..
ps running stock 4.2 and stock recovery or was when it worked. LOL
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
Hi folks. My rooted and unlocked tablet got a TWRP update to try a new rom. I was running KatKiss for around a year. I'm not unfamiliar with flashing and mods for routers, phones, and Androids. So here goes.
I have read much of fixes before posting. So far, no joy!
A reboot after updating TWRP just sits at the ASUS screen, shows the device is unlocked.
Holding the power button until it switches off and then vol down and power on shows:
Key driver not found Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
I get a winking RCK. RCK, android, wipe data options. Selecting it gives a:
Starting Fastboot USB download protocol
Booting Recovery kernel image
Booting failed
And a red Unrecoverable bootloader error (0x00000000).
Restarting with vol down and powering up shows Asus Fastboot Interface with :
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0B05&PID_4DAF
As hardware id's. Started out as unknown device and I have used several ADB/Fastboot drivers after text searching the inf files.
If I force an ADB driver I can adb devices and get a serial number and offline.
Stopping the server and doing it all over again gives the same results.
No fastboot ever. No response when I enter fastboot devices, using the fastboot driver or adb driver. Device manager will not show both devices, and I can get APX mode to work. But I'm pretty much thinking that is useless for me.
If I remember correctly I had both fastboot and adb in my device manager before. I have a newly reformatted pc with win 7 64. Also have a 32 bit win 7 box.
I wish I could give more preliminary info. But so far none of the sure fire methods have worked. It has been my assumption that if a device is soft bricked, you can usually get it working again
Can anyone help? If only so I can get it working to get files off of it stuck in internal memory.
Thanks!
supwiddiss said:
Hi folks. My rooted and unlocked tablet got a TWRP update to try a new rom. I was running KatKiss for around a year. I'm not unfamiliar with flashing and mods for routers, phones, and Androids. So here goes.
I have read much of fixes before posting. So far, no joy!
A reboot after updating TWRP just sits at the ASUS screen, shows the device is unlocked.
Holding the power button until it switches off and then vol down and power on shows:
Key driver not found Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
I get a winking RCK. RCK, android, wipe data options. Selecting it gives a:
Starting Fastboot USB download protocol
Booting Recovery kernel image
Booting failed
And a red Unrecoverable bootloader error (0x00000000).
Restarting with vol down and powering up shows Asus Fastboot Interface with :
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0B05&PID_4DAF
As hardware id's. Started out as unknown device and I have used several ADB/Fastboot drivers after text searching the inf files.
If I force an ADB driver I can adb devices and get a serial number and offline.
Stopping the server and doing it all over again gives the same results.
No fastboot ever. No response when I enter fastboot devices, using the fastboot driver or adb driver. Device manager will not show both devices, and I can get APX mode to work. But I'm pretty much thinking that is useless for me.
If I remember correctly I had both fastboot and adb in my device manager before. I have a newly reformatted pc with win 7 64. Also have a 32 bit win 7 box.
I wish I could give more preliminary info. But so far none of the sure fire methods have worked. It has been my assumption that if a device is soft bricked, you can usually get it working again
Can anyone help? If only so I can get it working to get files off of it stuck in internal memory.
Thanks!
Click to expand...
Click to collapse
nobody?