Database Info

[Q] I need help! My TF got stuck and can't boot into recovery!!!

My Tf got stuck at the logo Eee Pad boot after I tried to restore the old rom, and now it can't do anything except boot and stuck at the logo.
I tried the nvflash unbricking technique from rayman84 : http://forum.xda-developers.com/showthread.php?t=1123429
, but my TF only listed as unknown device when I tried to get to APX mode and it also said,
"This device is disabled because the firmware of the device did not give it the required resources. (Code 29)"
Now I don't know what else to do. Please help! I hope I am not completely bricked the device yet.

Have you tried the button combo to get into recovery?
Press and hold the Vol down + power button.
When prompt, you'll see lines of words at the top left of the screen, push the Vol up button immediately within 5 sec to get into recovery.

Apparently, I didn't know the button combo. Anyways you save my niece's TF. Thanks a bunch
Edit: although the tablet is working now, it still got the message usb unknown device. Do you know how to fix it?

Hi, i don't know if i should post a new thread but my problem is almost the same as bengob3t's one.
I have a brand new TF101 with a B70 Serial number, but i successfully rooted it using the RazorClaw Tool. Then i tried to install clockwork mod followin this topic : http://forum.xda-developers.com/showthread.php?t=1106587
I directly applied the instructions from step 8 (download hashmyfiles etc...) and i rebooted my Eee pad manually step 13
I didn't see any progress bar, but my device is stuck on the Asus screen, and the speakers make stange noises at regular intervals.
I am able to go into recovery though (power + vol down then vol up) but the factory reset doesn't work, and i cant really do anything (at least not anything that i know what it is).
Is my tablet definitely bricked ? If not, how can i bring it back to life ?
I wasn't able to use NVFlash, as i can't seem to go in APX mode. I press power+vol up, i hear the sound usb device connected and immediately after i hear the sound "usb device disconncted"
Nvflash says
"Nvflash started
rcm version 0X4
Command send failed (usb write failed)"
Thanks in advance for your help.
EDIT : When i put the micro sdcard from my phone into the tablet, i am able to mount it. So i will probably be able to flash something from it, but what ? Do i have to flash a recovery ? Directly a custom rom ?
I'm a little lost, but i'll try to give you guys as mush info as i can find.
EDIT2 : I flashed the PRIME rom, everything seems to be back to normal... if you got info on my situation, don't hesitate to fill me in ^^ i'd like to understand what i did wrong, even though i dodged the bullet.

bengob3t said:
Apparently, I didn't know the button combo. Anyways you save my niece's TF. Thanks a bunch
Edit: although the tablet is working now, it still got the message usb unknown device. Do you know how to fix it?
Click to expand...
Click to collapse
Do you have the correct driver installed? Do you have Asus sync install on your PC?

hmm.. I'm not sure. I downloaded the unbricked tool nvflash file, and the tool already had usb driver inside it. Is that the driver you were talking about? I never were able to get to the point where I need to point the APX to where the driver located because it always said unknown driver the whole time.

[Q] Any other way to boot to APX mode? I'm bricked.

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.

[Q] Cant enter apx mode, cant usb debug, cant mount sdcard, cant update sdcard.

I had an old flash and wanted to update. I was going to update to Nightlies. Couldn't go into usb debugging. Chose zip from sdcard and it says can't mount /sdcard/. Tried to apply /sdcard/update.zip and cant mount and aborts. I decided after rt wants me to enter APX mode (which is volume up and power) nothing. My finger is cramped now from holding for so long. "What do I do wid these keeds," says Cartman. If I could just get APX mode to work, I was going to flash updated Asus Firmware and start over.........help?

hutchrt said:
I had an old flash and wanted to update. I was going to update to Nightlies. Couldn't go into usb debugging. Chose zip from sdcard and it says can't mount /sdcard/. Tried to apply /sdcard/update.zip and cant mount and aborts. I decided after rt wants me to enter APX mode (which is volume up and power) nothing. My finger is cramped now from holding for so long. "What do I do wid these keeds," says Cartman. If I could just get APX mode to work, I was going to flash updated Asus Firmware and start over.........help?
Click to expand...
Click to collapse
From my understanding of APX mode:
Step 1:
Install the naked drivers (IDK where to find them, however they are in this forum)
Step 2:
Connect your USB cable
Step 3:
Press power and volume up.
Step 4:
Wait for USB connection tone from windows
Step 5:
Profit

did that
ghost0001 said:
From my understanding of APX mode:
Step 1:
Install the naked drivers (IDK where to find them, however they are in this forum)
Step 2:
Connect your USB cable
Step 3:
Press power and volume up.
Step 4:
Wait for USB connection tone from windows
Step 5:
Profit
Click to expand...
Click to collapse
When I do that while it is on......it just powers off. When I do that when it is off, it does make the sound on my computer, but computer is still off. Press up and power.......still stays off.

hutchrt said:
When I do that while it is on......it just powers off. When I do that when it is off, it does make the sound on my computer, but computer is still off. Press up and power.......still stays off.
Click to expand...
Click to collapse
Weird, that should have worked. your unit should already be off. then use the button combo to power up into APX mode. the screen stays off in APX mode. the only way you know it is in APX mode is when the windows PC detects it plugged in as a USB device. am i reading correctly? you are saying that pushing the button combo will not power up the unit in APX mode?

ghost0001 said:
Weird, that should have worked. your unit should already be off. then use the button combo to power up into APX mode. the screen stays off in APX mode. the only way you know it is in APX mode is when the windows PC detects it plugged in as a USB device. am i reading correctly? you are saying that pushing the button combo will not power up the unit in APX mode?
Click to expand...
Click to collapse
Yup! I hear the sound on the computer suggesting it went into the APX mode, but screen is still off. If I remember correctly, isnt there suppose to be a screen for APX mode? Even if there isnt, I tried to follow through with the program to change it and it is if it never went into the mode.

hutchrt said:
Yup! I hear the sound on the computer suggesting it went into the APX mode, but screen is still off. If I remember correctly, isnt there suppose to be a screen for APX mode? Even if there isnt, I tried to follow through with the program to change it and it is if it never went into the mode.
Click to expand...
Click to collapse
I did APX mode before on my droid 2, and the screen never came on. It just stayed black. Got the connection sound and then did a push to my device. I had a bad upgrade while I was in Iraq/Kuwait over WiFi for the phone. It killed the CDMA portion of the phone. I didn't know because I only used the WiFi at the time. Anyways, to make a long story short. There are some commands you can use to see if you can communicate with your device via APX mode. I think there is a shell program out there that will run in Command Prompt. You can issue commands to make sure your device is recognized via APX.

clueless
ghost0001 said:
I did APX mode before on my droid 2, and the screen never came on. It just stayed black. Got the connection sound and then did a push to my device. I had a bad upgrade while I was in Iraq/Kuwait over WiFi for the phone. It killed the CDMA portion of the phone. I didn't know because I only used the WiFi at the time. Anyways, to make a long story short. There are some commands you can use to see if you can communicate with your device via APX mode. I think there is a shell program out there that will run in Command Prompt. You can issue commands to make sure your device is recognized via APX.
Click to expand...
Click to collapse
I am clueless how to do that! It does sound like something that would work though I've never entered commands on my computer to do something like that.

hutchrt said:
I am clueless how to do that! It does sound like something that would work though I've never entered commands on my computer to do something like that.
Click to expand...
Click to collapse
Also, if I am not mistaken, if you look under device manager, you should see your device under USB.

Super bricked

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.

[Q] HELP did OTA update - bricked shield

I literally know nothing about android, this is my first device.
I was doing the OTA update to kit kat, and now all that happens when I boot my shield is a little dead android man and it says "No Command"
I have tried to do the factory reset as details on nvidias site
but after it reboots I get the same message
What can I do? I imported my unit into the UK and nvidia do not have any warranty support :'(

Did you try to download this: https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Recovery%20OS%20Image&tx=$additional,shield (grab update 65 as it has Windows binaries)?
Putting your device into recovery mode (hold ABXY, left bumper left trigger, power on) and run the batch file.
There's no such thing as a bricked NVIDIA device NVIDIA Recovery Mode is the best.

vostok4 said:
Did you try to download this: https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Recovery%20OS%20Image&tx=$additional,shield (grab update 65 as it has Windows binaries)?
Putting your device into recovery mode (hold ABXY, left bumper left trigger, power on) and run the batch file.
There's no such thing as a bricked NVIDIA device NVIDIA Recovery Mode is the best.
Click to expand...
Click to collapse
Thankyou for the reply, I will try this in a few hours when I get home and give it a try
Do I connect it to the PC before booting into recovery mode? Will running the file automatically detect the shield and begin installation?
thanks for the help, I could honestly cry since I bought my shield in the UK I have no warranty :/ :highfive:

vostok4 said:
Putting your device into recovery mode (hold ABXY, left bumper left trigger, power on) and run the batch file.
.
Click to expand...
Click to collapse
If I do this the shield log in the middle lights up but the screens stays black
If i boot up with the back and home button and power - it says bootloader - then says device locked

Doing as vostok4 said should bring your SHIELD back to life. Just a quick question though: have you rooted your SHIELD, installed CWM recovery or twiddled with it whatsoever after unlocking the bootloader? Because if you haven't, and if the OTA process completed normally, there is no reason for it to end in that state and you should maybe contact NVIDIA and report that issue.
In any case the SHIELD is a hard device to brick, so don't worry, it should be back to life soon.

shadowcaptain said:
If I do this the shield log in the middle lights up but the screens stays black
If i boot up with the back and home button and power - it says bootloader - then says device locked
Click to expand...
Click to collapse
You are correct, the screen should stay black. It will only light up with text when you send the bootloader over with nvflash.
There should be a driver with that image download, it doesn't matter if you have it connected to the PC before or not. But you will need to have a driver installed, and then the OS image should have a batch file you can run to just kick it off.
The device will be something like "NVIDIA USB Recovery Mode Device" or something like that. If you have linux no driver needed