i've just flashed prime 1.9 mobile data ver over CWM. have to say the whole proccess ended faster then normal. after rebooting i get nothing. black screen.
tried holding power for 10-20 sec, even 30. nothing.
so tried going into APX mode and nvflashing through pc. but when i'm doing that the pc recognizing it as "unknown device" and not an APX.
so i've realy got nothing. and i cant communicate with pc to nvflash.
obviously i tried manualy install APX driver from nvflash folder. but still get unknown device.
please help!
what should i do?
im not a newbie i've done those things dozens of times. (nvflash, apx, cwm..) but i've never faced a totall brick
so you already had nvflash connected to device before it is bricked so you are sure all is setup corectly ?
cause it is a real pain in the but that when the tf is in apx it just looks dead.
If that is the case than I dont have a clue because nvflash is kind of a last resort
Uninstall the drivers, reboot, install the drivers again and try for apx, if its a no go then reboot pc and try for apx.
Sorry i cant be more help.
Edit - Make sure the TF actually has some juice in it. Leave it on charge for a couple of hours.
i've done nvflash before and i'm familiar with the procedure.
about uninstalling drivers and rebooting, maybe will help altough i've tried going into apx with other computers with no success aswell.
please help!
no one knows maybe theres a reset button or something inside the transformer. just a way to bring APX back!
if you can get back into revovery, try to flash again.
check md5sum yo make sure you have a good file
Sent from my Transformer TF101 using Tapatalk
thats the thing. ive got nothing. the screen just stays black no matter what. so i thought maybe APX will rescue me but i now dont have even APX. is it even possible?
apx mode on ming leaves the screen blank and off. leave your tablet on a charger for a while to make sure it is charged, a couple of hours at least reduce as many errors as you can. if you have the apx drivers installed right when you plug it in to windows you will hear a beep saying you plugged a device in. You could also try to install the apx drivers again.
http://forum.xda-developers.com/showthread.php?t=1123429
this will tell you how to do it.
http://forum.xda-developers.com/showthread.php?t=1185104
this thread has better instructions though.
have you ever installed nvflash drivers before...or is this the first time?
ive already told yall. i done this proccess before (nvflash and going into APX. i know the screen should stay off and only the computer should say APX device been detected or something like that. but the message im getting from pc is "unknown device" connected. and when i try to manually install the apx drivers from device manager by directing it to the nvflash folder where the drivers should be- it just stays unknown device and says that the most updated drivers for it is already installed
I'm having the same issue. I can't get into APX mode anymore. Just appears as "Unknown Device" in device manager.
I'm currently running PRIME 1.7. My clockwork recovery also fails to recognize the SD card, so I can't flash a new ROM that way either. I really want to switch to Revolver, but with no APX, it's not going to happen.
hmm maybi you can try it on a other pc. if you have luck it can be recognizedd
Unknown Device......?
Uninstall the drivers, reboot pc, reinstall fresh drivers, reboot pc, connect TF101
Next time use the search function or google.
Related
I have Windows 7, Windows Vista both 32 bit and Ubuntu 32 bit, When I plug the USB cable into the Tablet and connect it to the Windows PC's I get Unknown device, I never get propted for drivers. I have booted the tablet into ASX and regular mode, I have installed the Tegra 250 dev kit from nvida for the ASX drivers, I also tried the ABD drivers with the Android development kit to try to do ADB, I removed the drivers with USBDVIEW. Whenever I try to update the drivers by pointing them to the Tegra drivers I get a error message that says there are no drivers for your device. Today I tried plugging it into my Ubuntu box and nada it does not even detect it ldusb does not list the device, only my mouse. The tablet is running TNT Light 4.23 with the supplement, ADW launcher, works fine. I wanted to try the new TNT light 5.00. I also want to be able to access the tab by usb, right now I have to use Bluetooth or Dropbox or the SDCARD shuffle to move things. I know it worked when I intalled clockworkmod 0.8 and TNTlight the first time. Can anybody help me get this connected??
I had a problem the first time I tried. Even after installing all the files I read I needed.
I thought now what did I do wrong? I eventually just tried another USB port and let my windows 7 64 bit system find it new hardware and whalaa it worked.
Don't know if that would work for you or not.
ale
New problem
I finally got it to work, turns out the cable was bad! I ran nvflash to restore the gtablet to stock.
The flash completed successfully and Tapntap booted, however all my luanchers and old apps were still there. When I reboot the device goes directly into Apx. Powering with power button no volume, vol- or vol+ gives same result. If I repeat the flash It boots into tapntap bet debits into apx. Do I need to do a factory reset here or somthing else. I am going to try a data wipe and factory reset tonight at the first boot. I want to install TNTllite 5.00 so I can't install clockworkmod. Any Help appreciated.
Purchased a gtablet, all went smooth after I installed the TNT Rom, but found some sound issues, and found out that seemed to plague a lot of other people, so decided to try another ROM - can't even recall which one now. But now where I'm stuck at is if I hold down vol up and power, I get "Recovery key detected Booting recovery kernel image" and it sits there forever. Even if I take out the microsd card, I get the same screen. A normal power attempt sits forever at the Viewsonic "birds" screen. I've tried just about every rom, none take . I'm pretty sure I had the clockwork recoverymod installed, but now I can't even get into that.
I tried volume down + power, (ATP mode?) but none of the drivers I've found are for Windows 7 64 bit, so I can't access the tablet in that mode because the lack of drivers.
Any suggestions on what to do from here?
Thanks!
http://forum.xda-developers.com/showthread.php?t=989320&highlight=nvflash+windows
Good Luck
http://forum.xda-developers.com/showpost.php?p=9302497&postcount=5
Bottom of instructions section -- a few users have written posts on nvflash for windows.
LGCubana said:
http://forum.xda-developers.com/showthread.php?t=989320&highlight=nvflash+windows
Good Luck
Click to expand...
Click to collapse
Hi,
Thanks for the link.. I think I've seen that - I don't see a APX driver missing in Device Manager - there is a ADB Interface, however when I let that install drivers, it says the Device cannot start - Code 10.
I may have another computer I can boot up and try
phirephoto,
I wrote the USB post and used the files there to NVFlash in APX mode. I know the info there is accurate.
I also have found, however, that if you install the whole SDK kit instead of the files in my post, it installs ADB. I don't know much about ADB but I know it basically works about the same.
If you have the APX driver it says it is the nVidia USB driver in Device Manager. So I am assuming you have installed SDK.
I can only suggest you make sure what files are installed on your PC and what method you are using and then research this site. I know several people have used the ADB methods and posted about them.
Good luck.
Rev
If you have another computer -- try the method reobeet posted along with the Advent Vega USB files. I know that has worked.
butchconner said:
phirephoto,
I wrote the USB post and used the files there to NVFlash in APX mode. I know the info there is accurate.
I also have found, however, that if you install the whole SDK kit instead of the files in my post, it installs ADB. I don't know much about ADB but I know it basically works about the same.
If you have the APX driver it says it is the nVidia USB driver in Device Manager. So I am assuming you have installed SDK.
I can only suggest you make sure what files are installed on your PC and what method you are using and then research this site. I know several people have used the ADB methods and posted about them.
Good luck.
Rev
If you have another computer -- try the method reobeet posted along with the Advent Vega USB files. I know that has worked.
Click to expand...
Click to collapse
It did work on my old POS XP Laptop I knew that thing was useful for something!
Thanks again.. Never thought I'd be so happy to see "TapnTap" again. And now I'm up and running on the Vegan rom
Hi, trying to root my g2x 2.3... I followed the directions, turned on debugging mode took off battery and pressed up and down same time and plugged the usb in.. Clicked and tried to flash the CWM from nvflasher.. nothing.... just says it can not detect my phone... and tips or know what I am doing wrong?? Thanks in advance.
ezcape said:
Hi, trying to root my g2x 2.3... I followed the directions, turned on debugging mode took off battery and pressed up and down same time and plugged the usb in.. Clicked and tried to flash the CWM from nvflasher.. nothing.... just says it can not detect my phone... and tips or know what I am doing wrong?? Thanks in advance.
Click to expand...
Click to collapse
I may be wrong but I'm pretty sure you can't root on 2.3....... you need to downgrade to froyo 2.2
Sent from my LG-P999 using XDA App
ezcape said:
Hi, trying to root my g2x 2.3... I followed the directions, turned on debugging mode took off battery and pressed up and down same time and plugged the usb in.. Clicked and tried to flash the CWM from nvflasher.. nothing.... just says it can not detect my phone... and tips or know what I am doing wrong?? Thanks in advance.
Click to expand...
Click to collapse
If you're saying the instructions exactly as you did, then it doesn't sound like you installed the drivers before using NVflash.
You're right about pressing both the up and down volume buttons (Even though you didn't even state that, just that you pressed up and down, on what I imagine.) but you do that first to allow your computer to detect the phone. Once your computer can detect your phone, then NVflash can.
It can't detect phone because you have not installed drivers on pc, just like anything else you install on windows, printer, vg card, it needs drivers, g2x is not plug n play.
In the directory where you unzipeed NVFlash is an APX directory. After you connect the phone to the computer you need to go to Device Manager (assuming Windows here) and you will see the APX device with an explanation mark. That is because Windows doesn't know where the driver's .inf file is. While still holding the volume keys right click on that device and select "reinstall drivers." Then say I will select location and browse to the APX directory and tell Windows to install the drivers. When Windows warns you the drivers are not signed click on YES to continue the installation. Now that the driver is installed let go of the keys, unplug the phone and give your fingers a rest. When your fingers are ready repeat the process to connect the phone to your computer and now NVFlash can see it.
jboxer said:
In the directory where you unzipeed NVFlash is an APX directory. After you connect the phone to the computer you need to go to Device Manager (assuming Windows here) and you will see the APX device with an explanation mark. That is because Windows doesn't know where the driver's .inf file is. While still holding the volume keys right click on that device and select "reinstall drivers." Then say I will select location and browse to the APX directory and tell Windows to install the drivers. When Windows warns you the drivers are not signed click on YES to continue the installation. Now that the driver is installed let go of the keys, unplug the phone and give your fingers a rest. When your fingers are ready repeat the process to connect the phone to your computer and now NVFlash can see it.
Click to expand...
Click to collapse
Sweeet thanks. Your directions seemed a lot easier to follow than the others i've found. It worked after my fingers were about to fall off lol.... Thanks
Bricked Xoom built a program cable but fails to install drivers when connected. I tried going to devices and troubleshooting searched for drivers but none were found.
Any idea of what i can try next?
Have you downloaded drivers from motodev?
Prior to the bricking, could you connect to your computer?
It will connect but it just shows up as APX in the devices and says its missing drivers. I went to moto and downloaded USB drivers but still does the same thing. The xoom does nothing when plugged in.
Windows 7 or XP?
Sent from my MB860 using xda premium
Windows 7. I did manage to get some drivers to install. Don't know if their the rite ones though. I clicked on let me choose such drivers, found some in SDK for htc,Samsung,and Motorola. Chose Motorola and it had several adb drivers clicked next and they installed. So now it just shows it as APX in the devices but no longer has the missing drive issue. Still no sign of life when trying adb or fastboot.
What mode is it in when you are attempting to connect it to your computer?
Sent from my MB860 using xda premium
It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.
ericman77 said:
It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.
Click to expand...
Click to collapse
I have the same problem.. doing my head in trying to fix it. I have tryed everything i can think off. Anyone out there know how to fix it in apx mode using a factory cable ?
Did you ever find a solution to this issue?
I currently have a black-screen bricked Xoom. I have tried all the 'soft-unbrick' methods, I can _NEVER_ get anything to appear on screen. The only signs of life are with a 'factory cable'
With this 'factory cable' I am able to see 'APX' in my Device Manager. I can make it 'reboot' by doing the volume up + power which makes the device disappear and reappear. No other key combinations have any effect.
I am able to install either the Nvidia NVFlash drivers. However NVFlash doesn't work. Possibly due to a lack of SBK (Secure Boot Key).
I am also able to install the "Universal Naked Driver" which makes the device show up as an "Asus Transformer APX" However neither fastboot or adb seem to see the device.
Does anyone have any suggestions how I can unbrick my Xoom?
ericman77 said:
Bricked Xoom built a program cable but fails to install drivers when connected. I tried going to devices and troubleshooting searched for drivers but none were found.
Any idea of what i can try next?
Click to expand...
Click to collapse
ericman77 said:
It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.
Click to expand...
Click to collapse
darchiuk said:
I have the same problem.. doing my head in trying to fix it. I have tryed everything i can think off. Anyone out there know how to fix it in apx mode using a factory cable ?
Click to expand...
Click to collapse
qoole33 said:
Did you ever find a solution to this issue?
I currently have a black-screen bricked Xoom. I have tried all the 'soft-unbrick' methods, I can _NEVER_ get anything to appear on screen. The only signs of life are with a 'factory cable'
With this 'factory cable' I am able to see 'APX' in my Device Manager. I can make it 'reboot' by doing the volume up + power which makes the device disappear and reappear. No other key combinations have any effect.
I am able to install either the Nvidia NVFlash drivers. However NVFlash doesn't work. Possibly due to a lack of SBK (Secure Boot Key).
I am also able to install the "Universal Naked Driver" which makes the device show up as an "Asus Transformer APX" However neither fastboot or adb seem to see the device.
Does anyone have any suggestions how I can unbrick my Xoom?
Click to expand...
Click to collapse
Dear all,
I got the same thing.
I installed the driver from nvflash drivers. And I ran several commands to try, it showed no bootloader was specified. I guess maybe I damaged my bootloader. Does any of you unbricked your xoom?
Here is a link to my post, which showed my tries.
http://forum.xda-developers.com/showthread.php?t=1838002
Anyone could help us? Thanks a lot.
Wow, i've been on that Wagon for a long time. http://forum.xda-developers.com/showthread.php?t=1838002 Now I just gave up cause I don't think anyone has gone past installing the drives after it detecting as APX.
Thanks for your kindly reply.
So, you mean there is no hope.
Actually, I sent it to another MOTO local service center again. After one week, they told me they tried to restore the software in two steps, but only the first could be done, and then went back to brick again. And they thought there might be some damage on “the kit” of motherboard, and if I want to repair, the whole motherboard must be replaced totally.
If you still have the bricked XOOM, would you please try to draw the BCT and config.cfg from your device?
Again, I did another search. Although there is no available bootloader.bin, BCT and config.cfg for XOOM, I guess there might be possible to use SAMSUNG P7510's files, because the hardwares are almost same, and it's heard that P7510 could use XOOM's ROM.
Sent from my ZTE U970 using xda app-developers app
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
AdvanceArg said:
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
Click to expand...
Click to collapse
PC operating system?
Drivers for fastboot and adb loaded?
Look at my signature about universal naked drivers.
Also about getting into your bootloader menu.
APX will be useless to restore.
tobdaryl said:
PC operating system?
Drivers for fastboot and adb loaded?
Look at my signature about universal naked drivers.
Also about getting into your bootloader menu.
APX will be useless to restore.
Click to expand...
Click to collapse
W7 x64
Used exactly those naked drivers.
Cant access to bootloader.
AdvanceArg said:
W7 x64
Used exactly those naked drivers.
Cant access to bootloader.
Click to expand...
Click to collapse
Did you actually use the link to attempt the bootloader access?
Did the drivers properly install?
Do you have an sdcard for this tablet?
tobdaryl said:
Did you actually use the link to attempt the bootloader access?
Did the drivers properly install?
Do you have an sdcard for this tablet?
Click to expand...
Click to collapse
i installed ADB Interface Drivers, but i cant Android Bootloader Interface Driver because 'vol down + up + power' doesnt work.
AdvanceArg said:
i installed ADB Interface Drivers, but i cant Android Bootloader Interface Driver because 'vol down + up + power' doesnt work.
Click to expand...
Click to collapse
I'll assume that means all ten methods to get into the bootloader failed.
If the adb drivers installed we may have a chance.
You didn't say about the sdcard.
At the moment are you still stuck in apx or bootlooping.
Sorry but I need a place to begin.
tobdaryl said:
I'll assume that means all ten methods to get into the bootloader failed.
If the adb drivers installed we may have a chance.
You didn't say about the sdcard.
At the moment are you still stuck in apx or bootlooping.
Sorry but I need a place to begin.
Click to expand...
Click to collapse
i have a sd, it doesn't have info [isn't from tf300, it doesnt came with]. When i introduce it into eeepad i can't access the storage from windows.
I can only interact with the tablet when i turn it on with VOLUP + POWER then is when windows ask me for drivers, now i have installed ADB drivers.
sorry for all dude. And thanks.
AdvanceArg said:
i have a sd, it doesn't have info [isn't from tf300, it doesnt came with]. When i introduce it into eeepad i can't access the storage from windows.
I can only interact with the tablet when i turn it on with VOLUP + POWER then is when windows ask me for drivers, now i have installed ADB drivers.
sorry for all dude. And thanks.
Click to expand...
Click to collapse
No problem we just need to get a starting place and have as much in our favor as possible.
I don't believe adb works in apx mode but we'll give it a shot.
No sdcards come with the tablet.
Go into apx mode (volume + power).
Go to your adb folder with cmd and type
adb devices - press return or enter
If it is working we should get your serial number in return.
Now get out of apx mode.
type
adb devices - do not press return yet
watch your unit and when the screen goes black and before it lights(rebooting) now press return
Tell me what is returned each way.
tobdaryl said:
Go into apx mode (volume + power).
Go to your adb folder with cmd and type
adb devices - press return or enter
If it is working we should get your serial number in return.
Now get out of apx mode.
type
adb devices - do not press return yet
watch your unit and when the screen goes black and before it lights(rebooting) now press return
Tell me what is returned each way.
Click to expand...
Click to collapse
No serial. only ''List of devices attached''
Tried with Asus Trasnformer Prime APX Interface [naked drivers] and ADB drivers.
AdvanceArg said:
No serial. only ''List of devices attached''
Tried with Asus Trasnformer Prime APX Interface [naked drivers] and ADB drivers.
Click to expand...
Click to collapse
[FONT=TimesNewRomanPSMT, serif]Download 10.4.2.9 JB from this thread post #3[/FONT]
[FONT=TimesNewRomanPSMT, serif]unzip once and you should still have a zip if you get a blob then do not unzip.[/FONT]
[FONT=TimesNewRomanPSMT, serif]rename to EP201_768_SDUPDATE.zip and copy to sdcard and place sdcard into your tablet.[/FONT]
[FONT=TimesNewRomanPSMT, serif]Power tablet and hope![/FONT]
nothing. Renamed US_epad-user-10.4.2.9 to EP201_768_SDUPDATE.zip, throwed it into sd and turned tablet on. Stuck on ASUS logo.
AdvanceArg said:
nothing. Renamed US_epaduser_10_4_2_9_UpdateLauncher.zip to EP201_768_SDUPDATE.zip, throwed it into sd and turned tablet on. Stuck on ASUS logo.
Click to expand...
Click to collapse
I have some bad news for you.
Without adb or fastboot access I don't know of anything else to be done.
If you could have gotten into the bootloader menu we would have had a chance.
Maybe someone else will read this thread and have more ideas.
I'm sorry.
Good Luck!
same problem here. i have a tf300t and can only access apx interface.
I got into this mess, after by "accident" choosed the "wipe data" option present on the bootleader.
!! adb, fast boot do not work!! "power key + down button" dont do anything!
i'm getting a bit resteless because no matter were i search on the web i can not find anything suitable on how to resolve this issue...
there are some youtube videos that show a solution for tf100. it seems the same problem.
http://www.youtube.com/watch?v=CwvfNIHCYlQ
there is also a tool for tf100, called easy flasher. to bad it does not work for tf300t
http://forum.xda-developers.com/showthread.php?t=1688012
i think it is a question of seaching and waiting. someone will help and get or point to a solution. because if we google for tf300t bricked that are lots and lots of links stating this issue...
what a mess...
AdvanceArg said:
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
Click to expand...
Click to collapse
Do you see anything after resetting by holding volume down and the power button? If you can get the tablet into fastboot mode you may able to revive it. If you can, ask the previous owner which version stock Android he was running before he tried to root it (it matters!).
This method worked for me!
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps guys. Good luck!