Database Info

[Q] 3.2 Update Problems, trying to understand APX

I had rooted/cwm'd my tf101 when I first got it. It was running the 3.1 update at the time. I followed the pure root posts here on XDA.
Sadly I had never tested CWM, and perhaps since it went so easily I didn't really understand/read enough on CWM to understand what is happening. When I ran the 3.2 OTA (OK so I shouldn't have done that, I know now) the TF froze on the initial splash screen.
I've tried many things and read tons of posts here on XDA and other sites, and I'm not getting anywhere, but part of it is I don't know for sure what I'm trouble shooting.
I was using a dual boot laptop in Windows mode when I did the initial update. I had the drivers working and succesfully rooted my system.
What I am trying to do is restore a stock rom for now and I've tried several methods.
1) Asus download SOP - It detects the image on the SD card, checks validity of the firmware, shuts down and reboots and hangs at the first splash screen.
2) CWM recovery, if I understand this right, I Power+ vol_down. I hit the vol_up to enter The screen says
Checking for RCK. press key <Vol_Up> in 5 sec to enter RCK.
I do that and it hangs at:
Booting recovery kernel image
3) I've tried several nvflash posts out there. NVFlash does not seem to be working, I've now done this on two windows boxes. Both the one that used to work, and a clean windows XP machine I had lying around. In both cases, I can get the nvidia APX drivers loaded and the device is seen. However, adb doesn't show any devices, and from pulling apart the batch files and doing some reading, I tried nvflash -r --getpartitiontable myfile.txt and some other commands which always hang. Eventually if I disconnect the tablet - then I get a read error of some sort.
4) quick reboot - every option leads to reboot and freeze at first splash screen.
So questions that I can't seem to find an answer too.
1) If I'm connected in APX mode, should adb show a device? Like I said the PC recognizes it as the APX device and loads the nvidia drivers instead of the normal transformer MTP drivers when I do the power + vol_up.
2) Is there a simple test to use for nvflash? The device shows up, is there anyway I can confirm whether APX mode is working or not?
I'm only starting to piece together the boot process in my own head, and my guess is that niether the stock recovery image or the cwm recovery boot image is working. Would that be a reasonable assumption based on behavior? I will admit I really don't understand the boot loading process in android.
FYI, if I go through Power+Vol_down, wait for rck to skip and then boot without wiping, the TF is fine after that. Meaning as long as I don't try to update, it will work and reboot normally. Root also still seems to be working.
I tend not to suspect a driver issue, since one machine was confirmed working, it's how I got root - and 90% of the time that machine is run as linux. I almost never boot into windows. I'm pretty sure the last time I did was to root the TF.

What happened is you overwrote the cwm when you installed the new update. You can't just randomly install things once you're rooted.
If you have a B7O machine, you need to check that you have the old or new sbk. Go to the general transformer forum, and there's a thread about the new sbk locked bootloader. Follow the test to see if you have one that you can use nvflash with. If that is the case, then go to the dev forum, and look through the nvflash unbricking thread.

Thanks for the reply
First off, you're right and I should have known better. Almost nothing I own runs it's stock firmware, and I just got dumb and didn't do the full research excited for HC 3.2 goodness.
I have a B50 machine, or at least the my serial number indicates that.
I've already tried several nvflash debricking instructions, but it seems that nvflash is not working either. I have several copies of prime and the .11 release from asus. But since nvflash is not behaving as expected, all of those threads are not helping.
I do have the nvidia USB recovery device show up in device manager, but every nvflash command fails hangs at
nvflash started
[resume mode]
ADB devices shows a serial when I'm normally connected, but it doesn't show up when I'm in APX mode. I'm just not sure if the device is in a functional APX mode, since nothing actually runs, despite it showing up in device manager. I've tried googling that situation, but I can only find posts that tell me how to get it to show up in dev manager... It seems like when that happens everyone else has been fine.
WHILE GOOGLING FOR MORE INFO ON b70 - I managed to get NVFLASH working, and now I get what the first command and -r do.

3.2 Update Problem SOLVED
So look at the original post for the strange condition I had gotten into.
Somewhere along the line, the transformer had stopped responding to adb even not in APX mode.
I uninstalled PC Suite and Asus Sync. Then reinstalled only ASUS sync. ADB started working when TF was connected normally
I did not reboot my PC, win7 64 bit. Shutdown transformer, it hung at the splash screen. WHILE HUNG, I held power and vol_up until device manager showed nvidia USB recovery device
I used the stock rom replacement from tabletroms. Sorry I can't include the link as I am too new to XDA.
Got the transformer back up, set up my account, restored data. However OTA from there was not working.
So I went to ASUS, grabbed the .11 image and updates via SDCARD following the SOP instructions.
After reboot, checked for updates, and there was one. Let it do the OTA for 3.2 and now I'm back at having stock 3.2 updated TF.
I will probably root, but may not CMW this time.

"Key Driver Not Found.. " on Bootloader 4.2.1

So this morning my brother was using his TF300T in its dock. He undocked it and the screen went blank. Screen was still on but nothing displayed. I rebooted it for him (volume down and power button for 10s). After a minute of it powered on the screen went blank again, so I rebooted it again, but this time the Asus splash screen displays and the lock screen flickers before quickly going blank.
Thought a reinstall of the ROM would fix the problem but I now can't even boot into recovery or fastboot! Had no problem the first time I rebooted and selected cold-boot in the bootloader options. With the tablet on and screen blank I plugged it into a PC and Win7 detected and installed the proper drivers (I think). ADB commands seem to work, but the command to boot into bootloader only resets the tablet. Fastboot command does not work. Also noticed the below message flash before a flicker of bootloader options are shown. The PC seems to have access to the internal storage (I can see folders from the tablet) when plugged in via USB.
"Key driver not found.. Booting OS
Android cardhu-user bootloader <2.00 e> released by "US_ePad-10.6.1.8-20130PPt" A03"
Could it be a hardware issue? I ask because I see similar problems with the Asus splash screen indicative of a logic board problem when diagnosing a PC (images pixelated)...

MaMMiTs said:
So this morning my brother was using his TF300T in its dock. He undocked it and the screen went blank. Screen was still on but nothing displayed. I rebooted it for him (volume down and power button for 10s). After a minute of it powered on the screen went blank again, so I rebooted it again, but this time the Asus splash screen displays and the lock screen flickers before quickly going blank.
Thought a reinstall of the ROM would fix the problem but I now can't even boot into recovery or fastboot! Had no problem the first time I rebooted and selected cold-boot in the bootloader options. With the tablet on and screen blank I plugged it into a PC and Win7 detected and installed the proper drivers (I think). ADB commands seem to work, but the command to boot into bootloader only resets the tablet. Fastboot command does not work. Also noticed the below message flash before a flicker of bootloader options are shown. The PC seems to have access to the internal storage (I can see folders from the tablet) when plugged in via USB.
"Key driver not found.. Booting OS
Android cardhu-user bootloader <2.00 e> released by "US_ePad-10.6.1.8-20130PPt" A03"
Could it be a hardware issue? I ask because I see similar problems with the Asus splash screen indicative of a logic board problem when diagnosing a PC (images pixelated)...
Click to expand...
Click to collapse
It is unlikely windows installed the proper drivers for adb and fastboot. The drivers for accessing the internal sdcard yes.
See my signature for installing proper drivers in windows 7 and another for entering the bootloader after you have the proper drivers.
When I have seen that message it does not relate to hardware but software.
I don't suggest plugging and unplugging the dock when powered.

tobdaryl said:
It is unlikely windows installed the proper drivers for adb and fastboot. The drivers for accessing the internal sdcard yes.
See my signature for installing proper drivers in windows 7 and another for entering the bootloader after you have the proper drivers.
When I have seen that message it does not relate to hardware but software.
I don't suggest plugging and unplugging the dock when powered.
Click to expand...
Click to collapse
Will try what you suggested, but does it matter that I'm using the same PC I used to initially fastboot TWRP to the tablet? I thought once the driver is installed it there would be no need to re-install the driver...

MaMMiTs said:
Will try what you suggested, but does it matter that I'm using the same PC I used to initially fastboot TWRP to the tablet? I thought once the driver is installed it there would be no need to re-install the driver...
Click to expand...
Click to collapse
It will probably be ok. I was going by your comment "I plugged it into a PC and Win7 detected and installed the proper drivers (I think)"

tobdaryl said:
It will probably be ok. I was going by your comment "I plugged it into a PC and Win7 detected and installed the proper drivers (I think)"
Click to expand...
Click to collapse
Yeah. My problem is I can't get to fastboot mode on the tablet itself, and based on what I saw on another thread it seems like I'm going to have to replace the mainboard .

MaMMiTs said:
Yeah. My problem is I can't get to fastboot mode on the tablet itself, and based on what I saw on another thread it seems like I'm going to have to replace the mainboard .
Click to expand...
Click to collapse
OK.
Good Luck!

I unplug mine and reconnect all the time when on. Never had a issue.
Sent from magical jelly bean.

My brother's TF300T is back up and running!
As a last resort I opened it up to disconnect the battery. Still could not get into fastboot, so I left the battery plugged in and let the battery run out. After 48 hours of the battery being completely dead I charged it fully to see if I could do anything. Battery LED indicator was green and the first thing I noticed was that the unit was still off. (I wasn't able to completely shut it down before letting the battery completely drain). I powered it on thinking it would display a blank screen, but it powered up as usual! Everything seems to be working. I immediately flashed CROMI-X 4.3b6 on it (what my brother originally wanted me to do).
Thought I'd post this as a last resort hope for those who think they may have bricked their machine. I do recall completely draining the battery then waiting over 24 hours as a solution for one of the many machines I've hacked. Just thought disconnecting the battery would achieve the same purpose. Guess I was wrong . Hopefully this is a solution for someone else out there who may have bricked their machine. Sure doesn't hurt to try .
I'm actually mystified as to why this worked. Anyone know? I'm guessing completely draining the battery reset whatever was inside. I also have noticed more users have reportedly bricked their machines after Android 4.2.1. Coincidental? Thank God I'm perfectly happy with Android 4.1.1 based CROMI v3.4.6 .

[Q] [How-To Root] video removed-- help!

Sorry all for those who read my last post in my other thread - "can't root- twrp not working" which makes this post redundant but I'm feeling a little desperate and I'm also new to this stuff. Since I was unable to install TWRP for some reason it was advised I use the old fashioned NV flash method with prime rom, however 'how to' video from the following thread- http://www.tabletroms.com/forums/tr...ment/976-nvflash-unbricking-forever-root.html
has been removed and now I'm stuck with this message on my tablet :
entering nv flash recovery mode/nv3p server
chip vid ----
I hope this doesn't mean I bricked "permanently mt tf101. I've completed the following 3 steps to get this far:
downloaded nvflash zip and prime 1.4.
1 Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
2 (Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
3 Run download.sh (linux) or download.bat (windows)
In step 2 - driver wouldn't take I presume since I already updated driver when using frederuco's guide. Shouild I have uninstalled APX and reinstalled this version?
Anyhow, after step 3 allot of messages about partioning came up on tablet and now there is the entering nvf flash recovery mode message stuck on tablet screen. Is this right? Am I supposed to flash prime 104 now? If so how? I was advised to install this way as a back door if you will so as I can later install a better rom once I've successfully rooted.

The tablet will reboot when NVFlash is finished, you should be able to follow its progress on the PC screen / CMD window
NVFlash can take a while

There is no cmd window open. I cant remember if there even was one or if i closed it. What do i do now? Do i re-run bat program as shown in step 3?

leif2 said:
There is no cmd window open. I cant remember if there even was one or if i closed it. What do i do now? Do i re-run bat program as shown in step 3?
Click to expand...
Click to collapse
Basically the entire procedure for NVFlash is this
1: Connect TF101 to PC USB
2. Power Off TF101
3. Put TF101 into APX mode (Power & Volume Up)
4. Run download.bat as Administrator (Right click > Run as Admin)
5. Keep an eye on the CMD window as it will say things like "Deleting partitions > Creating partitions > Sending System / Boot / etc"
6. TF101 should reboot when done
----
If you didn't see the above, just start again from No.1

Yeah, i remember seeing a bunch of messages on tf101 about partioning ect.. . I dont think tf 101 rebooted though. Or maybe it did. This was some hrs ago now since tablet has been stuck with entering recovery mode on screen so i cant remember. I also dont remember if i ran bat with admin privilages. Shall i restart the entire nv flash procedure then? Should i first uninstall and reinstall the apx driver as i sugguested since the one i installed came with a different download pack?

leif2 said:
Yeah, i remember seeing a bunch of messages on tf101 about partioning ect.. . I dont think tf 101 rebooted though. Or maybe it did. This was some hrs ago now since tablet has been stuck with entering recovery mode on screen so i cant remember. I also dont remember if i ran bat with admin privilages. Shall i restart the entire nv flash procedure then? Should i first uninstall and reinstall the apx driver as i sugguested since the one i installed came with a different download pack?
Click to expand...
Click to collapse
It doesn't take hours to complete, not even an hour, you're looking at somewhere around the 15-30 minute mark, been a long time since I used it
Yea just cancel it, you can't break NVFlash, it is hard coded into the TF itself, its the lowest level communication between TF and PC that will still work even if you messed up your firmware, so long as hardware is fine
Drivers come with the NVFlash ROMs, uninstall the one you have running at the minute and install the one from the NVFlash zip
You'd be better off getting the new drivers ready and uninstalling the old ones while the TF is still connected in APX mode or they will disappear from device manager
These are the ones I use
http://www.xdafileserver.nl/index.php?dir=Asus%2FAsus+Transformer+%28TF101%29%2FSTOCK+ROMS%2FICS+.27
EDIT - Is your TF101 SBK1 ? (Serial number below B7O)

I went into device manager and uninstalled apx driver like you said but after that I didn't see a way to update apx driver. Holding down vol up/ power didn't seem to be doing anything so I rebooted my PC with asus still attached. That caused the asus screen to go dark which had previously been stuck with the entering nv flash recovery mode/nv3p message for the last 3 hrs. tf101 wouldnt seem to turn on so I plugged it into wall thinking battery may have died but now it still wont turn on. Have I killed my tf101? If not what do I do now? I can feel the charger heating up so pherhaps I better leave it plugged into wall until charger cools down again letting me know it's charged?

Its likely still in APX mode, you'll need to hold power for about 20-30 seconds, then power it on again normally
To install the new APX drivers, you'll need to power it into APX mode while it is attached to the PC USB, then once the PC sees it, point the driver install to the new driver location and install them that way

I plugged back into pc and in device manager it wont let me change apx. It says it already has the best version. This even though i had uninstalled it just before. At this point since i cant see my battery leval im going ro leave plugged into wall for a while and then try running bat file again with current apx drivers and come back here to post my results. Thx for assistance. By the way before plugging back into pc i tried holding power button down for 30 seconds and nothing happened.

You'll need to check the "Delete driver software" box when you uninstall the APX driver or it will just install it again automatically
Likely that driver is fine anyway if it can see the TF
Holding the power button down for 30 seconds just powers the TF off, you won't see anything until you power it back on again
APX mode is 99% black screen on the TF until you power it off and back on normally again

Before i run the bat file- did you say to do it in a cmd prompt? Cause i dont remember reading directions to do it that way. I think before i just double clicked the bat file that was extracted on my PC. By the way i held rhe power button for at least 30 seconds more than once im pretty sure, and there was no activity on my screen

The .bat file will open CMD itself

you were right, when i checked the box "delete driver software" I was able to uninstall. Then after rebooting W8 in advanced settings I was able to disable driver certification which let me update my APX to that of the same folder in which I downloaded the nvflash im currently using. Unfortunately all this had the same result. That is the cmd ran successfully formatting/ partioning ect.. and then like before the cmd said something quickly about being successful and then self closed. Now like before my tf101 is stuck showing entering nvflash recovery message on screen. It never rebooted. Could this be that my tf101 is too new for this method to work? My serial bar sticker came off so I can't check it but my sales invoice is dated june 8 2011 if that helps. Please advise what I should do now

leif2 said:
you were right, when i checked the box "delete driver software" I was able to uninstall. Then after rebooting W8 in advanced settings I was able to disable driver certification which let me update my APX to that of the same folder in which I downloaded the nvflash im currently using. Unfortunately all this had the same result. That is the cmd ran successfully formatting/ partioning ect.. and then like before the cmd said something quickly about being successful and then self closed. Now like before my tf101 is stuck showing entering nvflash recovery message on screen. It never rebooted. Could this be that my tf101 is too new for this method to work? My serial bar sticker came off so I can't check it but my sales invoice is dated june 8 2011 if that helps. Please advise what I should do now
Click to expand...
Click to collapse
Normally it tells you that it can't find the tablet or fails sending the data if your TF is SBK2, it sounds like something else is wrong somewhere
You could try using Easyflasher, that works on SBK1 and SBK2 TF101s
http://forum.xda-developers.com/showthread.php?t=1688012
That should install TWRP Recovery, and from there you can flash any ROM you like from MicroSD Card
Make sure you choose TWRP recovery though

[Q] Hard Bricked my Nexus, possibly?

After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.

sinaisinai43 said:
After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.
Click to expand...
Click to collapse
I'm having the same exact issue, except with SlimBean 4.3. My phone is stuck in Fastboot (and says "FASTBOOT - NO BOOT OR RECOVERY IMG") and my phone will charge but can't be detected by *any* computer. I've tried three Windows 7 PCs of different makes and an Ubuntu 13.04 box and three different USB cables that all connect my other phone and my tablet fine - none can see it. (It was connecting fine to PC including being seen by ADB prior to this)
My power button is working, but it is also automatically booting into fastboot on its own when I plug it into the computer. Any of the options (besides "Power Off", which performs as advertised) just brings it back to Fastboot.
When I say can't be detected by a computer, I mean there is no USBDeview device listed and there is no 'connect' or 'disconnect' sound on the PC. ADB can't see it.

Yeah, it's strange. Did you find a solution yet, by chance?

sinaisinai43 said:
Yeah, it's strange. Did you find a solution yet, by chance?
Click to expand...
Click to collapse
Nothing yet. Thinking of buying an phone with a busted screen or something and swapping out the internals... I think it's PROBABLY the NAND chip. What I'm suspecting is that because there are several versions of the Nexus S, we might have used the wrong images. I have no idea if this is correct, but it's the only thing I can think of.
My phone's sticker says i9020 on the inside, but D720 (or whatever) when I look up the EIN.

Just hoping somebody sees this and offers a suggestion... I'm getting ready to buy a refurb and put the 'new' body over it so at least I have a functioning, new-ish phone.

[Q] Stuck at bootlogo

Hi,
I got this tablet from a friend, and it's stuck at the boot logo. I've tried hard reset, reset via recovery, nothing seems to work.
How can I flash the latest official rom?
Can't seem to find a tool for it, and Asus suggest to flash with the tablet itself, but that's not possible for now.
Anyone?
Thx!

http://forum.xda-developers.com/showthread.php?t=1688012
Easyflasher to flash TWRP recovery > copy ROM to MicroSD card, flash ROM

Thanks! I can't seem to get him into APX mode, what is the exact procedure?

Connect the tab to USB > PC first
Power Off the Tab
Hold Volume Up & Power
Nothing will appear on the Tab screen, but the PC should sound the USB connect noise / device manager will show it has connected - only takes a few seconds to enter APX mode

I've tried that, doesn't seem to recognize it . Would you help me via IM of some sort?

It`ll be the drivers most likely, open device manager when its connected and in APX mode, and manually update the drivers using the Universal Naked Driver from the Easyflasher site
I don't have any IM installed unfortunately but I`ll help you out here

Ok, that would be wonderful. The problem is, I don't know when it's off. I can't get it to shut down, it keeps rebooting. I'm monitoring dev manager with sound high, but it's not coming up. Cable is working, because it will charge. Using the original cable. (Windows 7 x64)

Best thing to do would be connect it to the PC, then press and hold Power until it shuts off, then try for APX mode - you might even be able to enter APX from a powered on state by holding the same button combo, but Ive not tested that myself
And a cable that charges doesn't automatically mean it will work for Data, they use different pins, some for power and some for data, if the data pins are damaged, it will still charge

I can't seem to get it working . Any other ways to flash it?

Not without being able to get it to boot - you'll need APX mode to do anything in the state it's in now
A bad cable is a common problem though, might be worth grabbing another one from eBay

To bad. I'll try and let it drain till it's empty, and fully charge it then. Just ordered another cable.
Thx for the help!

If the System / Data partitions are corrupted, which generally causes the boot loop, then draining and recharging won't help
Plus be careful not to drain the battery to 0%, their design prevents them from recharging if they hit 0% - many people have had to buy new batteries after not using their tab for a few months and letting it drain completely
Good luck, so long as there is no hardware damage, once you have a working cable it should be pretty straight forward to get TWRP recovery and a new ROM flashed to it
Might be worth trying your current cable on another PC too

Thanks for the headsup! Will try!

Hello everyone,
Not to thread jack but I have a similar problem and instead of opening a new thread I decided to revive this one.
I have a similar problem that my TF101 has been working flawlessly for many years. It is rooted and was running 4.3 ROM. As of a couple of days ago it just won't boot at all. It has been stuck at the NVidia screen and just sits there. I tried to enter recovery mode by using volume(-) + power and the unit presents the TEAMWIN logo and just loops as well by showing the TWRP screen (3 seconds) then going blank for a second then showing TWRP screen again in a cycle.
I downloaded and tried Easyflasher and Brks toolkit and nothing can complete the flash. Tried different installed drivers as well. I can enter MTP mode which the computer can see the device but the manufacturer name and model are not-recognized. I can also enter APX mode but while trying to flash anything I get an error message (error, cannot flash bootloader) and the computer dings (device disconnects).
I have been trying for a days now and have run out of ideas.
Has the unit finally bit the dust? Does any one out there have any more ideas or suggestions on what to try next?
TIA for any help provided.

Anyone with any sort of help on my previous post? Time to retire it for real this time?
TIA
Sent from my VisionX powered SM-N900T.

Jayster0966 said:
Anyone with any sort of help on my previous post? Time to retire it for real this time?
TIA
Sent from my VisionX powered SM-N900T.
Click to expand...
Click to collapse
Have you tried a different / new cable in-case that's the reason all the flashing attempts and computer recognising the unit are failing ?