Database Info

[Q] Help with Recovery/Reboot Problem

Hi Guys,
I have the TF101 tablet and anytime I try to reboot it just stays at the first boot screen with the "Eee...." screen. Forever. If I hold down power and vol-down then hit vol up, it just stays there saying its booting recovery image but never changes. If I hold down volume long enough it comes to the factory reset/cold boot screen, if I choose cold boot it will boot.
I have rooted the tablet and had no problems previously, was able to flash roms and whatever else I wanted to do. Also, when I plug the tablet into my Windows XP machine, it does not detect the tablet in any way.
Tablet info:
Android Version: 4.0.3
with 2.6.39.4 kernel
I don't remember what rom its running exactly but I know its a version of ICS

Did you use ROM manager to update your CWM version? This sounds exactly like that, you can try running the bootloop-fix in my PERI tool (link in my signature) to fix, or manually run roach2010's fix found in his latest recovery thread. You definitely need ADB working, otherwise you'll need to Nvflash. (Nvflash Wheelie link is in my signature as well)

You are probably right i very well could have done so in rom manager. Im on vacation and dont have access to a pc right now but am going to try ur tool when i get back. Thx for the info
Sent from my Transformer TF101 using xda premium

Wait. I just realized. My pc doesnt even respond when i plug my tab in. How do i run PERI?
Sent from my Transformer TF101 using xda premium

Cold boot and install the drivers.

Ok Thing o Doom, you've been great pointing me in the correct direction, however I need some more guidance.
I have installed ADB, and when I cold boot the device and run adb devices I get nothing.
HOWEVER, if I just reboot the tablet, when it's stuck on the EEE screen, I do adb devices and it shows 123456789ABCDEFG.....
My computer doesn't see the tablet when it's plugged in otherwise, nor does any other windows PC in the house. Do you have any guidance as to what I can do? Please help, I need to get this thing running right.

You just need to get to a state where adb is recognized, and 'adb shell' command works.
From that point PERI should work.
Reboot when it prompts you to if it doesn't automatically (Probably won't being stuck on logo)

I can't seem to get anywhere else. My pc recognizes the tablet at the first boot screen but adb shows it as inactive. When I cold-boot the tablet it boots and loads fine but ADB nor any PC recognizes that it's plugged in. I'm lost.

Is "Enable USB Debugging" Checked in Developer Options?

APX Driver not installed, cant NVFlash

So to start it off, I downloaded and installed eaglesblood rom on my g2x. The stupidity of me, I forgot to flash the ROM. When i system reboot, I have the eaglesblood animation and it turns off. Now I try to nvflash my phone and couldn't installed the apx driver. Instead i see on my device manager that it has nvidiausb instead. In conclusion I cant NVFlash my phone. Is there another alternative to nvflash my phone or an apx driver i can install or reinstall eaglesblood.
Reply asap please!!!

xmagiicsx said:
So to start it off, I downloaded and installed eaglesblood rom on my g2x. The stupidity of me, I forgot to flash the ROM. When i system reboot, I have the eaglesblood animation and it turns off. Now I try to nvflash my phone and couldn't installed the apx driver. Instead i see on my device manager that it has nvidiausb instead. In conclusion I cant NVFlash my phone. Is there another alternative to nvflash my phone or an apx driver i can install or reinstall eaglesblood.
Reply asap please!!!
Click to expand...
Click to collapse
This may sound like a silly question, but can you not boot into recovery?

Concerning the APX driver, I'm not sure you used the correct driver, or it installed incorrectly.
The next time you plug your phone into your PC (battery removed and both volumes buttons pressed...do not let go of those buttons no matter how bad your fingers hurt, hehe) try re-selecting the driver again from the APX folder in the NVFlash download that you uncompressed. Your P999 should be listed in the Device Manager under USB as "NVIDIA USB Boot-Recovery Driver for Mobile Device". Then you can let go on the volume buttons.
My apologies if you knew this already, just double checking. :angel: There is a video you can watch from theunlockr site but cannot post the link yet.

cyansky_1 said:
The next time you plug your phone into your PC (battery removed and both volumes buttons pressed...do not let go of those buttons no matter how bad your fingers hurt, hehe) try re-selecting the driver again from the APX folder in the NVFlash download that you uncompressed. Your P999 should be listed in the Device Manager under USB as "NVIDIA USB Boot-Recovery Driver for Mobile Device". Then you can let go on the volume buttons.
Click to expand...
Click to collapse
THANK YOU!!!! for so long i have been stuck with the NV Flash not working because of drivers. had the drivers and could never get them installed until now (well i had them before but that was before i had to reinstall windows) :highfive:

I just installed the apx file to nvidiausb and it worked as a charm. I nvflashed my g2x and it worked
Sent from my LG-P999 using xda app-developers app

[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] Asus tf700 JB 4.2 NOT WORKING

Hey guys, first time on here.
I've been trying to root my unlocked Asus tf700 running JB 4.2.1 for days and have been following all the xda guides with no luck.
I've tried to flash CMW on it through fastboot to no avail. Everything I see says, once you get into the bootloader or whatever, to press Vol Down until you get to the USB icon and then press volume up but there isn't any USB icon. Right when I get into the bootloader, after I hold Vol Down and Pwr, the first thing it reads on the top left corner of the screen is "Key driver missing." But I have downloaded the drivers from the asus website. Any suggestions about why this is happening? I also tried just using Motochopper (http://forum.xda-developers.com/showthread.php?t=2230763) but when it ran it said failure. I booted it up and I had SuperSU but I tried to open it and it said "no SU binary found! This is a problem!". Any suggestions on how to root this and flash a recovery on it would be greatly appreciated, because none of the other forums guides seem to work? help out a noob!

npf24 said:
Hey guys, first time on here.
I've been trying to root my unlocked Asus tf700 running JB 4.2.1 for days and have been following all the xda guides with no luck.
I've tried to flash CMW on it through fastboot to no avail. Everything I see says, once you get into the bootloader or whatever, to press Vol Down until you get to the USB icon and then press volume up but there isn't any USB icon. Right when I get into the bootloader, after I hold Vol Down and Pwr, the first thing it reads on the top left corner of the screen is "Key driver missing." But I have downloaded the drivers from the asus website. Any suggestions about why this is happening? I also tried just using Motochopper (http://forum.xda-developers.com/showthread.php?t=2230763) but when it ran it said failure. I booted it up and I had SuperSU but I tried to open it and it said "no SU binary found! This is a problem!". Any suggestions on how to root this and flash a recovery on it would be greatly appreciated, because none of the other forums guides seem to work? help out a noob!
Click to expand...
Click to collapse
If your device is unlocked you don’t need MotoChopper for rooting, just flash TWRP Recovery and it will ask you if you want to root your device (in case it detect that root is missing).
For the "Key driver missing" error, just ignore it, Fastboot will work just fine as long as you are sure that the drivers are installed just fine.

Pretoriano80 said:
If your device is unlocked you don’t need MotoChopper for rooting, just flash TWRP Recovery and it will ask you if you want to root your device (in case it detect that root is missing).
For the "Key driver missing" error, just ignore it, Fastboot will work just fine as long as you are sure that the drivers are installed just fine.
Click to expand...
Click to collapse
Thanks, but I'm still confused. I thought you needed GooManager to install TWRP, and GooManager won't work unless you have a rooted device.

npf24 said:
Thanks, but I'm still confused. I thought you needed GooManager to install TWRP, and GooManager won't work unless you have a rooted device.
Click to expand...
Click to collapse
Goo Manager is not mandatory, you can still flash the TWRP via fastboot.You can find more info on the TWRP website.

Sounds like a driver issue to me. If you can't fastboot cwm or use motochopper something is up.
Could also be your usb connection. Try another cable or port or another pc.

lafester said:
Sounds like a driver issue to me. If you can't fastboot cwm or use motochopper something is up.
Could also be your usb connection. Try another cable or port or another pc.
Click to expand...
Click to collapse
yeah ive tried two differ pcs already so I dont think its that. It definitely could be the drivers. Ive tried to install them from the asus site a bunch of times though so idk whats up.

npf24 said:
yeah ive tried two differ pcs already so I dont think its that. It definitely could be the drivers. Ive tried to install them from the asus site a bunch of times though so idk whats up.
Click to expand...
Click to collapse
If you have recently updated your firmware to xxxx.10, you will "not" be able to run motochopper (there is nothing wrong with your PC or cables), Ausus closed the Moto root opening with the latest firmware. However, you can still root following the TWRP instructions.....as indicated above.

just some more info
So i tried re installing the drivers one more time to my PC, and everything went okay, so I'm sure it can't be the drivers, although the error still comes up. And just to tell you guys, when moto chopper runs it says, "waiting for device, daemon not running, starting it now on port 5057, daemon started successfully." Don't know if that helps at all to what the problem is, but just some more info. Now I'll try flashing twrp and rooting that way.

Nothing works at all
dishinit said:
If you have recently updated your firmware to xxxx.10, you will "not" be able to run motochopper (there is nothing wrong with your PC or cables), Ausus closed the Moto root opening with the latest firmware. However, you can still root following the TWRP instructions.....as indicated above.
Click to expand...
Click to collapse
So I went to the TWRP website to try and install twrp 2.6.0. The three options on how to do this were:
1. Via GooManager - which I can't do because my device isn't rooted.
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
3. The terminal method.
I just tried the terminal method, and that didn't work either because when I typed in what it said I was supposed to type in, it said "permission denied."
So yeah.

npf24 said:
So I went to the TWRP website to try and install twrp 2.6.0. The three options on how to do this were:
1. Via GooManager - which I can't do because my device isn't rooted.
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
3. The terminal method.
I just tried the terminal method, and that didn't work either because when I typed in what it said I was supposed to type in, it said "permission denied."
So yeah.
Click to expand...
Click to collapse
I vaguely remember running Motochopper & getting the same message.....it you are on .8 or earlier firmware (in 4.2.1), Motochopper should run.
I think I turned off my tablet, left it connected to PC & then ran motochopper & tablet self booted.....lots of ABD's out of date messages, but Moto worked it's way through them and rooted my device.
I have read of problems with Win 7 (my OS) & Motochopper, but none if used with XP.
Good luck, & Let us know how t goes

npf24 said:
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
Click to expand...
Click to collapse
Recent bootloaders do not have a USB icon because they activate fastboot already while the boot menu is visible (read the tiny text in the top left corner).

dishinit said:
I vaguely remember running Motochopper & getting the same message.....it you are on .8 or earlier firmware (in 4.2.1), Motochopper should run.
I think I turned off my tablet, left it connected to PC & then ran motochopper & tablet self booted.....lots of ABD's out of date messages, but Moto worked it's way through them and rooted my device.
I have read of problems with Win 7 (my OS) & Motochopper, but none if used with XP.
Good luck, & Let us know how t goes
Click to expand...
Click to collapse
I tried what you said. The tablet didn't self-boot when I ran Motochopper again. It just stayed powered off. I turned it on, and the exact same thing happened. except there was another error in motochopper this time. it said "FAILURE ALREADY EXISTS." any other suggestions?

_that said:
Recent bootloaders do not have a USB icon because they activate fastboot already while the boot menu is visible (read the tiny text in the top left corner).
Click to expand...
Click to collapse
Okay that's what I thought. So if I do that second method on twrp, I guess I should just skip when it says to press the USB icon because fast boot is already running??

npf24 said:
Okay that's what I thought. So if I do that second method on twrp, I guess I should just skip when it says to press the USB icon because fast boot is already running??
Click to expand...
Click to collapse
Correct.

_that beat me to it - again. )

[Q] Hard-Bricked, no boot. Failed during flash

OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?

gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
+1

gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
So will the tablet not boot into the bootloader ?
Thx Josh

lj50036 said:
So will the tablet not boot into the bootloader ?
Thx Josh
Click to expand...
Click to collapse
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.

gtgeek said:
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.
Click to expand...
Click to collapse
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh

lj50036 said:
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh
Click to expand...
Click to collapse
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?

gtgeek said:
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?
Click to expand...
Click to collapse
Nope there is just no way...
The chip is locked down ... :crying:
There is lots of info out there but its just info ...
No one to date has come back from where you are ....
Thx Josh