I keep trying to load the APX USB drivers and I keep getting this error...Can someone please help?
Cannot Continue with Hardware Update Wizard.
The wizard could not find a better match for your hardware than the software you currently have install.
I have tried every version of of the drivers that I can find.
Any help is greatly appreciated.
Thanks
Matt
Are you running a rom or stock, and if so which one? Have you tried this yet? That should work for you, but if you are running the ICS rom you will need to follow the instructions in the first post of the ICS thread under 'How to Install MTP Drivers'.
I am just using stock install right now and I am trying to get a rom on there. When I go to boot into APX it just sits at "Booting recovery kernel image" - it never gets past that. I am not sure why.
I actually did try your post before I posted myself. I have tried this multiple time on multiple machines with various flavors of Windows - XP, Vista, and Win7.
Thanks for the help.
Matt
Strange ... sounds like it is failing to boot into recovery, not APX mode. When you boot to APX it should show the 3 birds screen for a second, then go completely black (looks like it is turned off, but it is actually in APX). It shouldn't say anything. Are you holding Volume Down while pressing the power button? If you are, try holding Volume Up instead, I have heard that some Gtabs have the volume controls switched.
About the 'Booting Recovery Kernel Image', did you install a different recovery (CWM)? If so, which bootloader are you on and which recovery version did you try to install?
hutchinsonm said:
I am just using stock install right now and I am trying to get a rom on there. When I go to boot into APX it just sits at "Booting recovery kernel image" - it never gets past that. I am not sure why.
I actually did try your post before I posted myself. I have tried this multiple time on multiple machines with various flavors of Windows - XP, Vista, and Win7.
Thanks for the help.
Matt
Click to expand...
Click to collapse
Hey there, there are a few pre-steps that need to be done befor you can start flashing ROMs on a gtab.
A good reference is here
You will crap oout your gtab but as long as you know how to NVFlash a gatb is almost impossible to brick. KEYWORD ALMOST. The scret is ensureing you NVFLash the right BootLoader to the ROM you are trying to load. An example nvflash BL1.2 for a 1.2 ROM like CM7 there is also BL1.1 so be certain of what you are trying to load...
GLTY
hutchinsonm said:
I am just using stock install right now and I am trying to get a rom on there. When I go to boot into APX it just sits at "Booting recovery kernel image" - it never gets past that. I am not sure why.
I actually did try your post before I posted myself. I have tried this multiple time on multiple machines with various flavors of Windows - XP, Vista, and Win7.
Thanks for the help.
Matt
Click to expand...
Click to collapse
Your gTab is displaying the same behavior as mine. I went to install CWM, and it failed to install. Afterwards, my Amazon App store kept crashing every time I opened it. I tried reinstalling, and everything else (mostly games for the kids) started crashing also. I decided to go back to factory settings. It powered off, and then gave me the same message: Booting recovery kernel image with the three birds on the screen. It does not give me an option to choose a recovery. I followed instructions to recover from the external SD card, but it only sits there at the booting recovery kernel image message. Doesn't seem to make a difference whether I power on with the volume key pressed or not. It always goes to the same message.
Did you have any luck getting past that message with your gTab?
Peter
hutchinsonm said:
I keep trying to load the APX USB drivers and I keep getting this error...Can someone please help?
Cannot Continue with Hardware Update Wizard.
The wizard could not find a better match for your hardware than the software you currently have install.
I have tried every version of of the drivers that I can find.
Any help is greatly appreciated.
Thanks
Matt
Click to expand...
Click to collapse
Matt, If I'm not mistaken you're using the wizard to try and install the APX USB drivers to your computer. You have to MANUALLY point Windows to the folder containing the correct driver and it should find it. Otherwise it will give you that same message.
Related
I did it, sad to say. I was trying to get back to the earlier Tnt Stock so I could move up to the latest 5.0, when I got stuck on the Viewsonic screen. I had clockworkmod installed, but now nothing works. and when I try to get into recovery, it says it detects the key but then does nothing. I cannot see it when I connect it with my computer, and so I cannot install nvflash. Any suggestions?
i doubt you bricked it, as far as i know, its litteraly impossible to brick.
one of the more informed will be able to help you
if you think you can not get into apx mode, no power then inside next to the reset button are four solder spots that you can cover with a small piece of foil to recover to apx mode then run nvidia flash and you are back. you can not brick the gtab unless you physically break something.
Both of the previous posters are correct. Its practically impossible to brick it.
I use Ubuntu(Linux) so drivers aren't an issue for me. Sometimes Windows can be sketchy when it comes to APX.
Have you tried following the nvflash full restore guide? It should get you back on track.
Sent from my HTC Vision using XDA App
Reggie777 said:
I did it, sad to say. I was trying to get back to the earlier Tnt Stock so I could move up to the latest 5.0, when I got stuck on the Viewsonic screen. I had clockworkmod installed, but now nothing works. and when I try to get into recovery, it says it detects the key but then does nothing. I cannot see it when I connect it with my computer, and so I cannot install nvflash. Any suggestions?
Click to expand...
Click to collapse
Go here,
http://forum.xda-developers.com/showthread.php?t=861950
You only need to make sure you have the proper nvidia usb drivers installed so APX can work correctly with your Linux/PC OS.
It's a little tricky for Windows 7/64Bit but it does work, I brought my GTAB back from Brick using the method on that thread.
agreed, I thought I had bricked it, and when i plugged it in and although it didnt seem to be powered on at all, i ran the nvflash to stock image, it powered up the screen in nvrecovery, took the files and booted right up. So far, I've done it 3 times. It might seemed bricked, but it's probably just in APX mode until its reflashed. Linux: easy peasy, Winders: driver hell, but... once the drivers were in, it was just as easy. follow the directions, and you should have a working stock G-Tab in 3 minutes.
I'm tryin'.....
Thanks for the moral support, everyone. I'm taking a deep breath, trying not to panic, and trying the suggested thread. Actually it is my second time trying that, but before I was really panicked. I'm "calmed" down a little now.
I think I do not have the right USB drivers, since I keep getting "USB device not found" error message. The USB drivers were mentioned before, but where do I get them, and how do I install them? There is a file, "android_winusb.inf" that is among the unzipped files, but I still get the error.
When I boot to the APX mode, I do hear my computer "ding", so I gather it is trying to communicate. When I look at my Devices, It does show an APX device, but says the driver is not loaded. I've tried pointing the update driver to the folder with the "android_winusb.inf" file, but it doesn't see it, and the online search for the driver also comes up zilch. BTW I'm using Windows 7.
I'm breathing... I'm trying not to panic... At least I am progressing a little. I never knew that power on+down volume was different than power on+up volume...
for windows apx usb driver for windows
here is the link. oops cant post link just cut and paste
developer.download.nvidia.com/tegra/files/android_tegra_froyo_20101105.msi
After installing the .msi file connected the gtab by holding down the vol - and power together then go to the device manager find apx ? update the driver . It is located in the program files x86 ndivia section. C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105. It will install the driver.
hope this helps
Charles77 said:
here is the link. oops cant post link just cut and paste
developer.download.nvidia.com/tegra/files/android_tegra_froyo_20101105.msi
After installing the .msi file connected the gtab by holding down the vol - and power together then go to the device manager find apx ? update the driver . It is located in the program files x86 ndivia section. C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105. It will install the driver.
hope this helps
Click to expand...
Click to collapse
This is correct, and for 64bit systems I believe there is a folder labelled usbpcdriver in there somewhere and the "Nvidiausb.inf" driver file for the 64bit system is in there.
http://developer.download.nvidia.com/tegra/files/android_tegra_froyo_20101105.msi
sORRY, BUT....
You need better Kung-Fu to take down the tablet!
Just get the correct USB driver for your WinOS as other posted. And it's good you noticed the difference DOWN and UP volume button usage!
Whew! Success... I have Tnt back...
I have NEVER been so glad to see that little blue desktop!!! Again, this community of devotees to the gTab is Fantastic. Thanks for all the help... and once again, our gTab remains unbrickable. Even by this owner. I updated it with the OTA to the 3588 version. I think I will wait a little and calm down before trying the new TnT 5.0, which I was attempting to do and started all this "drama". But I do know that with the support of all you people here, I can continue to learn about our wonderful gTab. Kudos and Gratitude!
"Never Give Up! Never Surrender"....... Galaxy Quest
In the future you could also download a ubuntu live cd and run nvflash from that which would eliminate the need for drivers and also keep your windows os in tact.
follow up...
I did the TnT 5.0 update successfully! Yeah! All the help paid off.
Reggie777 said:
I did the TnT 5.0 update successfully! Yeah! All the help paid off.
Click to expand...
Click to collapse
Party On!!!
Only way to brick the gtablet is to pour cement on it and literally make it into a brick.
Can someone please give me step by step directions for this?
I couldn't get past the birds booting up and I downloaded the package below and I guess I ran the wrong flash file. Now my tablet won't boot at all. It is as if the power switch does nothing.
Any help is greatly appreciated.
TEK112 said:
Can someone please give me step by step directions for this?
I couldn't get past the birds booting up and I downloaded the package below and I guess I ran the wrong flash file. Now my tablet won't boot at all. It is as if the power switch does nothing.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Was this the TnT Lite 5.00 upgade? If so, check out the nflash links in my first post -- you might need to do that to get back on track.
Sadly this was me trying to downgrade clockwordmod manually and it got all sorts of outta whack.
edit: All is well. I nvflashed back to stock.
I have saved the entire folder in case anyone else needs it. Just open the folder and run the batch command and you are back to out-of-the-box stock.
Reggie,
Go to the original 5.0.0 sticky thread in the Developers Forum and go to the instructions and find the link to post 3798. In that post I list all the steps I
took and exactly the stuff I needed to NVFlash back from the same state you
are in.
The flash setup is not hard. It just took me a while to find USB drivers and I
have taken care of that now.
Good luck and keep us posted.
Rev
I had the same issue. Initially I freaked as well. Are you running a 32 or 64 bit system? That makes a difference as to which drivers you'll even be able to install. I have a 32 desktop and 64 laptop. After getting the correct drivers to install it was a breeze. Still having issues connecting in APX mode on the desktop but I'm determined to get it working.
I have been reading around for a while now, and noticed a lot of ppl soft-brick there device and are asking devs for help. I have noticed a lot of issues revolve around people trying to hop form on ROM to another.
A very easy way to recover from any sort of brick(or issue) is to use nvFlash. Its is very easy to setup and use and I highly recommend that everyone should setup nvFlash. You can find the guide on how to set it up from http://forum.xda-developers.com/showthread.php?t=861950
I think after the update last night a lot of people will brick there devices trying to mod it, and nvFlash will help you recover. I think we can really help out the dev if we all learn how to use nvFlash, because then they wont have to ans to alot of the support issues that keep coming up, and it will free up some of there time which they can use to create newer roms that will work with the new update.
If for some reason you follow that guide and are not scussefull in setting up nvFlash, then feel free to leave me a pm and i'll help you set it up.
I setup NVFLash a couple of days ago on my Windows laptop.
Am I correct in stating it replaces my need for CWM?
If so is there a site or link on how to use NVFLASH to complete the different task?
Example
Installing a Rom, Kernal, backup, data, etc
steve1040 said:
I setup NVFLash a couple of days ago on my Windows laptop.
Am I correct in stating it replaces my need for CWM?
If so is there a site or link on how to use NVFLASH to complete the different task?
Example
Installing a Rom, Kernal, backup, data, etc
Click to expand...
Click to collapse
No its not a replacement for cwm. NVFlash will help you recover if you every brick your device and need to go back to stock image.
Couple of scenarios where it will be helpful is if you update to the new stock update from VS and decided you want to go back to one of the custom roms like Vegan GB RC1, then you will need nvFlash to go back to stock, otherwise you will brick your device.
Also I have noticed that I have to use nvFlash if I want to go from GB rom to FORYO rom.
Cannot get NV Flash to finish?!?
Very new to this but with the forums help I put TNT 4.2.4 on my Gtab and loved it. I had a hard crash last week and figured I need to use NV Flash to go back to stock or another rom. I put tablet into correct mode and by using USB drivers I am able to load NV Flash, it finished and on tablet the screen says "Entering NVFlash recovery mode / Nv3p Server" and that is it! It never reboots and if I manually reboot I have the same problem - all I get is the birds forever...if I try to boot using vol+ it says "Recovery Key Detected" "Booting recovery kernel image" and it sits forever...need help desperatley!
Thanks for listening
Mike
nvflash unsuccessful or wrong version
sk01bim said:
Very new to this but with the forums help I put TNT 4.2.4 on my Gtab and loved it. I had a hard crash last week and figured I need to use NV Flash to go back to stock or another rom. I put tablet into correct mode and by using USB drivers I am able to load NV Flash, it finished and on tablet the screen says "Entering NVFlash recovery mode / Nv3p Server" and that is it! It never reboots and if I manually reboot I have the same problem - all I get is the birds forever...if I try to boot using vol+ it says "Recovery Key Detected" "Booting recovery kernel image" and it sits forever...need help desperatley!
Thanks for listening
Mike
Click to expand...
Click to collapse
Sounds like the nvflash wasn't successful. The message you are getting when you boot to recovery...Power + vol(+) indicates that CWM is installed. If you nvflashed a stock version, cwm would not be there (unless you nvflashed a stock version with cwm preinstalled). Are you sure you flashed with the correct bootloader version. You should have used the 1.1 b/l version. Here is a link to b/l 1.1 version 3588 with cwm preinstalled http://www.mediafire.com/file/picrzt9pdkuqbj0/gtab.nvflash.1.1.branch.20110422%20with%20cwmv8.zip. Nvflash this & see what happens. By the way. when doing the nvflash, the cmd shell output should look something similar to the attached file...won't be exact since this was for a bl1.2 4349 version I nvflashed yesterday.
Al
sk01bim said:
Very new to this but with the forums help I put TNT 4.2.4 on my Gtab and loved it. I had a hard crash last week and figured I need to use NV Flash to go back to stock or another rom. I put tablet into correct mode and by using USB drivers I am able to load NV Flash, it finished and on tablet the screen says "Entering NVFlash recovery mode / Nv3p Server" and that is it! It never reboots and if I manually reboot I have the same problem - all I get is the birds forever...if I try to boot using vol+ it says "Recovery Key Detected" "Booting recovery kernel image" and it sits forever...need help desperatley!
Thanks for listening
Mike
Click to expand...
Click to collapse
My website linked in signature. You're a code red.
Hello, thanks for the response! I am downloading now and will let you know shortly...
Mike
goodintentions said:
My website linked in signature. You're a code red.
Click to expand...
Click to collapse
What is a code red?
Code Red is the condition of your G Tab. If you follow the link in the signature of Goodintentions post (Viewsonic G-Tablet for Dummies) you will find complete and simple instructions on how to recover your G Tablet. You can also find links to the files you will need. It's a great site for anyone having problems with their tablets. It's where I got all my information when I first started.
I have a sl101. I only get eeepad screen. My son did something to the machine. I can get it to say booting recovery but nothing happens. I also can get a text that says cold booting Linux. Again nothing happens. Nvflash says USB write fail. But when I check adb the device is recognized. Is there a way for me to adb push a recovery in there for me to boot too, so I can reflash a rom. I have a little dilema here. I also was wondering if I can flash rom thru adb. I read once that's how they used to do it on g1. I don't know if I am speaking accurately though. Any kind of light shed on me will be greatly appriciated
Sent from my SAMSUNG-SGH-I997 using xda premium
not sure about the slider but i had a customer return yesterday with this exact issue on the tf101 and i couldnt get out of it. the tf just kept switching itself back on and getting stuck on the splash screen.
found this set of instructions but im not sure if its what you need or if it will work:
http://androidroot.mobi/technical/asus-eee-pad-transformer-tf101-root-cwm-recovery/
good luck
That is exactly what is going on with mine. The slider is basicly the same thing. I plug it in and I tries to boot. I thought you had to be booted into recovery or the rom for adb to work? That's why I believe this method you just revealed to me. Or some variation of it will work. I will be trying shortly.
Sent from my SAMSUNG-SGH-I997 using xda premium
not working transformer
i have asus tranfrormer 9.x.x.x, recovery 5.8.x.x, after i did superwipe , every thing is gone and i cant flash any rom through adb/nvflash saying cant write to sdcard (read only). any suggestions?
HELP : Same problem, no apx, recovery strange, no boot
I still have access to clockwork but nothing seems to install, i tried update clockwork nothing worked, reboot gives me clockwork, APX don't work...
please HELP !!!!
densleonis said:
I still have access to clockwork but nothing seems to install, i tried update clockwork nothing worked, reboot gives me clockwork, APX don't work...
please HELP !!!!
Click to expand...
Click to collapse
nvflash if your TF101 is compatible model.. (must B60 and below).
Or read Wolf's thread HERE. It might helped everyone here..
Thanks but everything needs adb connexion and as apx is not working, i can't connect ADB..
I have a B50 model
Nobody have a clue ?
well, I have to send it back to my reseller that will change it but before that I need to delete clockwork mode or brick it, how can i do ?
I tried every thread here, update rom does nothing, looks like it does not write anything on the tablet
Thanks in advance
try to follow this procedure...
http://forum.xda-developers.com/showpost.php?p=25636698&postcount=5
let me know
Hello, thanks, but as I can't get to apx mode, I can't use nvflash, so still stuck with my recovery, I tried to modify super Wipe package to do things but can't get through...
If someone can make a package to delete recovery, then I can try it on my tablet, I really yneed it to be bricked cause now it load with Rogue's recovery on and on, so the reseller will new it has been modified and I will have to pay to get it back ...
Thanks in advance
with the procedure posted in the previous link you don't need APX mode and don't need NVflash...
Just boot your TF in recovery mode and plug it to your pc...
remove all previous drivers and install the new one that you can find in the post
ciao
ps... at the end of the procedure you will have your TF101 with stock rom and stock recovery
I will try but even when I am on recovery, nothing appears in Hardware management, no recognition from My computer, still strange... And when I power + vol down key, It never says to presse vol up in the text in the upper left corner, just says booting linux kernel...
When I try to boot pressing vol up + power, nothing happens, not even the clics that can be heard when it powers up...
I had a similar issue when I used SuperWipe and discovered my ROM on the external SD Card could not be accessed by CWM
I tried pushing the file with adb but kept receiving errors - protocol, etc. I suspected it was a driver issue along with the fact that 64 bit systems don't always play nicely with drivers. I actually dug up an old hard drive and did a very basic install of 32bit Win7. I booted the Transformer into CWM and when I connected it to my PC - I pointed it to the universal naked driver. I was then able to successfully push the rom to internal storage and used CWM to flash it
Hello,
I tried to connect my tablet to an old Windows 2000, but still nothing happens
Hello every one, I finally sendt back my transformer to my reseller, now I can buy a new one...
Thanks again
Hello, first time posted, long time browser...
So, I have a bricked (or almost totally bricked) LG G2X. Here is what I did:
I had flashed the Hellfire Sandwich 1.9 rom and was just fine...until my phone started turning off randomly. After reading somewhere here that I should nullify my phone and the re-flash the rom in order to fix my issue.
So, I backed up my data and downloaded the Aroma Nullifier from Volk (thanks for all you do). I booted to recovery and ran the Nullifier. Once the Nullifier had stopped, still while in Recovery, I tried to access my sdcard to re-flash my Rom...well, I couldn't access my SD card. Furthermore, I couldn't unmount the SD or mount the USB Storage.
Here comes the big mistake:
So, as I was doing some research about how to proceed, my USB cord wiggled out of the phone and my phone lost power. Now, since I had read from Volk not to let that happen, I knew I was in trouble.
At this point, I can only load into the LG Boot Screen and my computer loads drivers for "Asus Android Device" (I have the Asus Transformer Prime Tablet) and under that title "Asus Android Bootloader Interface". No APX, No USB Controller....no other communication.
Last little note, I took the phone to the Tmobile store on a hunch one of the guys who works there had some experience (which he did), and while he was trying to boot into recovery from battery power (something I have been unable to do) he got the USB communication interface...something like "S/W Do not disconnect".... Since then, I have not been able to reproduce that interface.
I am at the end of my abilities...I haven't seen anything that addresses this particular problem though I have tried a bunch of solutions without success. I have looked all through XDA forums, but if there is one I missed, please let me know.
Any thoughts would be very helpful.
Kickingcans
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Thanks much...but...
therealnexion said:
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Click to expand...
Click to collapse
Thanks for the thoughts. I will try that all again, but I have tried nvflash and tried updating APX drivers. My computer only recognizes the phone as an "Android Bootloader Interface". When I try to manually update/change the drivers for the "Android Device", there is a problem with 64-Bit operating System (Windows 7 Home Premium). I was going to try to boot the computer in Safe Mode, but I don't know if that will help.
I haven't been able to communicate with the phone, and only saw the S/W Upgrade screen once and that was in the Tmobile store without access to my computer.
I am going to try those suggested steps again. Thanks again.
Leigh
Got it going....
THANKS SO MUCH. I knew I was missing something stupid. I kept reading the nvflash instructions and pressing the Power and Volume Down button instead of Volume Up and Down.
Things are going again. Thanks so much.
Kickingcans
Alright, I hate being that guy. You know, the one who posts the same question as 50 other people because he is too lazy to search. But in my defense, I have spent the last three days pouring over thread after thread and still can't find the answer, so please be patient and gimme a break!
So, I'm stuck in CWM 5.8.3.4 loop after flashing Katkiss and not knowing I couldn't use the "boot to recovery" option. I've got no access to my micro SD card and my x64 Win 7 won't recognize the TF101 so I can't put my own recover zip on. Cold boot goes to the screen that lets me boot Android or Wipe. If I pick Android, it hangs (for hours). I've wiped everything and reinstalled Katkiss, Revolver, Revolution, but I have the same problems.
Is there a thread that starts from the BEGINNING of the fix and sees it through? I've found dozens of threads that say, "Just input (code), flash, and you're done!", but I guess I'm not that far along. I've bricked Dinc/Dinc2, Razrs, etc., but never had trouble fixing them like this TF101.
I've got ADB, JDK, Ubuntu, etc. since I've tried numerous times. Also, I've had no luck with the one-touch fixes. I know I'm missing something easy, I just can't figure it out.
Thank you.
Incidentally, I've tried ***http://www.transformerforums.com/fo...ry-bootloop-fix-tested-my-c10-windows.html*** , but the SDK files come in a zip, not exe and none of the files execute/install in such a way that will let me input commands. I know I'm missing something because a soft brick isn't that big of a deal.
Huh. I don't know what happened, but it involved me cleaning the screen, accidentally pushing buttons, and rebooting, and now it works. No clue, but as long as I never shut it off again, I'm set!
You're gonna need to get the PC to recognise it to fix it I'd say
Easiest way would be using Easyflasher to get TWRP recovery installed, it sounds like you have stock recovery installed at the minute
http://forum.xda-developers.com/showthread.php?t=1688012
Few people have needed new cables to get the PC to recognise the TF again, might just be needing the correct drivers though which are also linked on that page
Basically install the drivers, put the TF into APX mode,
(Vol Up & Power from powered off state while plugged into the PC)
Then run Easyflasher as admin and choose to flash TWRP (CWM is probably the reason for the bootloop, it doesn't play nice with JB ROMs)
Once you have TWRP installed, flash whichever ROM you want from new recovery and you should be good to go
I appreciate the suggestion, but that isn't doing it. I have the tab booted up and recognized by Windows, but when I try to update to a different CWM or TWRP, nothing happens. I can reboot into CWM 5.8.3.4 all day, but it won't say anything about any different recoveries I've tried to install, though the recoveries appear to be installing correctly according to the dialog given on the tablet.
I've also tried running NVflash, but nothing happens (apx drivers installed). The BAT file briefly says USB not recognized and closes.
Further, I've tried Easyflasher / one click root+recovery and I just get messages saying "ADB server out of date. Killing." The tab still reboots, but upon rebooting, it gets stuck in CWM 5.8.3.4 unless I force cold boot.
I guess the best way to describe this is to say that no matter what I do with the tab or different recoveries, I can't get rid of CWM 5.8.3.4 and no matter what I do, it default boots into CWM.
It default boots into CWM.... I think that is the key here
I remember something about that from a while ago, having to hold Power & Volume Down to boot normally, as if the OS and Recovery partitions were reversed
Unfortunately I can't remember the solution atm, but if you head over to transformerforums.com or give frederuco a PM from here or over there, Im pretty sure I remember him having a solution some time back
I shot him a message. Thanks for the suggestion.
I swear all I did was root, install Katkiss, and reboot into recovery. Is this a common problem to have THIS much trouble with such a simple process? I know now that booting into recovery can cause a loop, but this seems like way too much.
It's having CWM as your recovery when you flash a JB ROM that causes the problems
CWM & JB = Problems
TWRP is the recovery to use once you get out of this mess, good luck