Hi guys,
I'm an Android developer and have flashed Cyanogen on a number of Droids, G1s and MyTouches, and I think I've ran into a little trouble. I was hoping someone could give me a little advice.
Just got my gTablet and am having some problems after trying to install CyanogenMod 7.0.1 Beta from here: http://forum.cyanogenmod.com/topic/14637-cyanogenmod-7-for-g-tablet-v700-beta1-1192011/
At this point, the tablet displays the Viewsonic logo but does not get any further. I followed the instructions from the guide post in the Development forum and have given the device plenty of time to reboot. I then tried the partition steps, but still get stuck at the Viewsonic logo. Partitioning the SD card has removed my installation files, unfortunately.
I can boot in and out of Clockwork Recovery like a champ. I have tried to go backwards using nvFlash, but it doesn't look like Clockwork Recovery is putting the tablet into ADX.
How should I proceed to get Cyanogen on this badboy.
Thanks for any help!
E
Wow, what a dumbass.
Clockwork has a Mount USB Storage right there in the "Mounts and Storage" menu.
So I've copied everything back onto the SD card and am attempting to reflash now.
gte619n said:
I can boot in and out of Clockwork Recovery like a champ. I have tried to go backwards using nvFlash, but it doesn't look like Clockwork Recovery is putting the tablet into ADX.
E
Click to expand...
Click to collapse
If your second install doesn't work, you may want to try another ROM (VEGAn 5.1 is very nice) though it's based on 2.2 instead of 2.3. As long as you have clockworkmod recovery you could try a different ROM before nvflash'ing
On another note, clockwork recovery has nothing to do with APX. APX is its own recovery type system.
Volume + and power boots to recovery (either stock or clockwork if that is installed)
Volume - and power boots to APX mode and you communicate/transfer everything over USB from your computer with nvflash
Ahh, thanks for pointing that out! I misread that in the previous posts!
It's still stuck on the ol' Viewsonic logo. I AM NOT SEEING THE DIFFERENCE, VIEWSONIC.
So I just tried flashing VEGAn 7, and I still can't get past the ViewSonic splash screen.
Am I doing something wrong here?
I got my gTablet yesterday and it wouldn't boot at all. I went through the recovery kernel boot menu a few times before getting it figured out and finally getting VEGAn 5.1.1 installed.
if you boot with the Power + Volume-Up, does it say "Booting recovery kernel" in teh upper left corner?
When I saw that, I then pressed Volume Down to get into the Clockwork menu. From there, I could repartition the internal SD memory. I copied over several ROM images, named /update.zip into the internal SD space.
First I tried roebeet's default TnT reinstall package. But, that just perpetuated my looping problem. I think after that, i reformatted my internal memory and repartitioned to 2048 / with 0 for swap.
I then went to Vegan 5.1 and it was OK but gave poor performance on wireless and I could not use the market.
I then flashed the 5.1.1 enhancement pack on top of that, naming it update.zip and it made things much, much better.
For me, not only pressing Power+Vol-Up was necessary, but then Volume Down to enter the hierarchical menu. And, I had to use linux to add my files to the gTablet, passing the USB through to an Ubuntu 10.10 VM from VMware Workstation.
Thanks Boulder,
I'm not having any problems getting in and out of recovery, but just getting the thing to boot after I do flash. It's just the strangest thing! I've tried both 7.x ROMs with no success. Going to try the others as you suggest.
I GIVE!
nvFlashed back, installed CWM.8, fired VEGAnTab 7 exp 1 and Google Aps and it looks like it's doing it's thing.
Thanks for the Power + Volume Minus tip!
Related
Just joined to say thanks to Roebeet and everyone who is active in this forum. Because of the obvious potential of the gtablet being explored here, and discussed on phandroid.com I decided to take the plunge and purchased one tonight. I might have passed this tab by, and waited months for something else...
--and here's where I cry for help!
I carefully followed a series of step-by-step instructions I found thru google, to install the latest tnt lite found here on XDA. Everything seemed to work without a hitch, and was prouder than a pappa to have completed my first root and mod ,ever!
BUT right after I DL'ed and installed the flash 10.1 apk things went south. The browser constantly crashed to the home screen, and the market and email apps were crashing also. I rebooted and now I am greeted by the tnt setup screen that is covered in an endless wave of crash warning dialogs! I can't tap them away fast enough to see the desktop.
I've tried to do a recover, but I can't get thru the setup (that keeps crashing to the first screen also) to use the USB to mount the internal mem to my Mac.
I am insanely happy about the potential of this hardware, but I've painted myself into a corner. ANY help would be greatly appreciated.
And yes, I do look very handsome in my profile pic.
From bad to WORSE!
I discovered the dcom222 thread that describes my problem and details a solution. I followed it to the letter, changing the command and using my microSD as a secondary boot to reinstall the vanilla tnt ROM.
But then it just stuck on the tnt logo, faded in and out 3-4 times, and went dark! The device won't turn on or off (had a full charge when I pulled it from the wall socket a few moments ago)
Please tell me I haven't bricked this thing!
still no luck...
I was able to power the unit back up, but I've tried to recover and flash all three setup files I have (vanilla tnt, ota update tnt and tnt lite 2) but nothing works!
All of them create a loop of some sort, whether it's the viewsonic screen, gtablet screen loop, or the tnt logo screen blinking on and off, NOTHING boots to the desktop.
Going to bed before I drive my self insane. Hopefully someone in the know will reply by the time I check this at work.
thanks in advance
You have not bricked it, don't worry. This device is very hard to truly brick. If all else fails there is nvflash or the apx mode fallback. But I don't think you need that if you are still able to boot to clockwork recovery.
In clockwork go to advanced - mounts and try mounting and unmounting your partitions. I suspect your user partition may be screwed. This seems to happen fairly frequently especially the first time you flash a ROM. It happenend on my first flash and not again since. Clockwork lets you repartition though. Search the forum for partition fix, its not too big a deal.
If that fails try roebeet's thread on nvflash recovery for TNT lite. If that fails, search for APX mode.
As far as I know there are zero bricks from ROM flashing so far.
Sent from my SMB-A1002-3G using Tapatalk
Life in LA said:
Just joined to say thanks to Roebeet and everyone who is active in this forum. Because of the obvious potential of the gtablet being explored here, and discussed on phandroid.com I decided to take the plunge and purchased one tonight. I might have passed this tab by, and waited months for something else...
--and here's where I cry for help!
I carefully followed a series of step-by-step instructions I found thru google, to install the latest tnt lite found here on XDA. Everything seemed to work without a hitch, and was prouder than a pappa to have completed my first root and mod ,ever!
BUT right after I DL'ed and installed the flash 10.1 apk things went south. The browser constantly crashed to the home screen, and the market and email apps were crashing also. I rebooted and now I am greeted by the tnt setup screen that is covered in an endless wave of crash warning dialogs! I can't tap them away fast enough to see the desktop.
I've tried to do a recover, but I can't get thru the setup (that keeps crashing to the first screen also) to use the USB to mount the internal mem to my Mac.
I am insanely happy about the potential of this hardware, but I've painted myself into a corner. ANY help would be greatly appreciated.
And yes, I do look very handsome in my profile pic.
Click to expand...
Click to collapse
Scroll down to post number #869 http://forum.xda-developers.com/showthread.php?t=842004&page=87
feeling better
Thanks for the assurances that I didn't wreck the device, and pointing me to some solutions. I have a few questions:
what is clockwork mod? If I am able to recovery boot from my micro SD card, do I already have it? (I downloaded a bunch of recovery images to start, per instructions)
If it's something I still need to download, is it a PC application? How am I supposed to change settings in it (manage partitions, etc) if I can't get the tablet to boot?
-- stuck at work and dying to get home to fix this thing...
Ok, more detailed instructions:
If you press and hold down Volume + when you are pressing the Power button to boot up, and keep holding the Volume + key until you see a message that says "Detect a Recovery Key Pressed", that should get you to a text menu from which you can navigate using the volume +/- keys and the Home soft button to flash ZIP files and do other things. That menu is ClockworkMod Recovery. Since you remember installing a recovery.img, it sounds like you probably (hopefully) have ClockworkMod Recovery on there.
If you get to ClockwordMod Recovery, you can go down to the Mounts and Storage option, then you will find the "Mount USB storage" option at the end of that list. That lets you plug in and mount your internal memory area as a standard USB drive to your Windows or Mac computer to copy over new ZIP files and the like to your G Tablet.
You can also check that partitions are all mounting and unmounting successfully in that menu. If you go instead into the Advanced menu, you will see Partition SD Card, which I believe is what you might need to do at this point.
If booting with the Volume + button held down doesn't get you anywhere and you see nothing about Recovery Key Detected and don't see any text menu, then you don't seem to have a working recovery. At that point you'll have to do what phfaty suggested, read the post he referenced, and follow the link therein to the tegratab forum post to get the NVidia Tegra SDK installed on your Windows desktop and use the NVFlash tool and APK mode (where you hold the Volume - key down while booting instead of the Volume + key) to reflash your tablet.
still not working...
The good news:
I do have clockwork mod installed. Must have been in 1 of those zips or rars I ran in the very beginning.
The bad news:
it's still caught in a boot loop. I've mounted it as an external drive 3 times now from clockwork, and tried all 3 versions of the operating system (vanilla, vanilla with the ota and tntlite 2) and NOTHING makes a difference.
Life in LA said:
The good news:
I do have clockwork mod installed. Must have been in 1 of those zips or rars I ran in the very beginning.
The bad news:
it's still caught in a boot loop. I've mounted it as an external drive 3 times now from clockwork, and tried all 3 versions of the operating system (vanilla, vanilla with the ota and tntlite 2) and NOTHING makes a difference.
Click to expand...
Click to collapse
1)Boot into clockwork.
2)Navigate to Advanced menu
3)Choose partition sdcard
4)Choose data partition desired size(1024=1GB)
5)Choose 0GB for the next selection(swap not used)
6)Do a factory reset from main menu
7)Reboot
8)If that doesn't work, then reinstall ROM, then reboot
UPDATE
partitioning the drive and wiping the user data did the trick. I'm up and running again. thanks to all who chimed in to help.
Let me start by saying I had a perfect install of TNT Lite v5.01. I semi-bricked my G-Tab trying to install it and learned how to recover it using nvflash; regardless I decided I wanted to backout of TNT Lite 5.01 so I could stick w/ released firmware and re-install TNT Lite 4.3.x. I should say that I've flashed many a ROM via recovery/cwn in the past and am fairly familair w/ the process.
I followed roebeet's instructions of backing out by flashing over TNT Lite w/ the OTA 3588 ROM and go back afterward to flash over it w/ TNT Lite 4.3. The flash to OTA 3588 went through fine and the auto-reboot occurred and I was stuck in bootloop(Viewsonic & gTablet screens). I then tried flashing 3588 and TNT Lite 4.3 both multiple times with no avail. I then proceeded trying the Format Utility and reflashing back to stock afterwards as I had luck in the past reflashing to stock w/ nvflash. However I still come back to the same bootloop. I format once more using the above link and nvflash comes up w/ a bootloop, I power it down and it won't power back up, even into APX mode.
I've since opened it up to unplug the battery physically pulling the plug from the board. This re-enabled APX mode. I have since been able to reflash replacing recovery w/ cwm and can get to cwm, but that is about it. This is where I've been since w/ nothing but bootloops for my attempts.
note
---
When I try to wipe data/factory reset in cwm it returns the following error:
E:Can't mount /dev/block/mmcblk3p2
(Invalid argument)
Error mounting /data/!
It formats CACHE & SDEXT no issue.
cwm can only seem to find my internal storage so I have been transferring ROMs to it via mounting it as a USB device(using cwm). And regardless of what I attempt to flash(the install runs fine) I always come back to the bootloop of the Viewsonic and gTablet screens. I can confirm that cwm can't find my ext microsd by checking the listed directores when I choose install from sdcard.
Any ideas at all? =]
Attempting the 2048/0 partition trick recommended by butchconnor in another thread. Won't have time to try it now, but will be taking my G-Tab to work to attempt any recommendations.
Have you tried powering it down from the bootloop and then powering it back on normally without going back into recovery?
I kept getting bootloops coming back to vegan from TnT lite and was frustrated as hell untill one time I forgot to hold down vol + and it booted fine. I had changed nothing as the 3 previous boots were just wiping data / cash / davlic.
I also get that error when trying to wipe dalvic and was told that it has something to do with a part of partition 2 but never got more info than that.
Sent from my Chromatic Magic using XDA Premium App
I bricked my friend's GTAB but roebeet saved my arse
My friend wanted a Gtablet when he saw mine with TnT 4.2.5, he couldn't get over the fact i control my PC with VNC viewer, can view my webcams etc etc. So he offered me a 32G micro SD to order one for him and ROOT it. Long story short once in 4.2.5 and downloading everything in the market it froze or something then went into boot-loop. then i really messed with it and then magic NO-GO (only messed with it because i knew WE had such awesome support HERE)
1st flash only gave me a boot loop, then affter finally understanding to rename the recovery.img in clockworkmod v08 to part9 and part9 to part9.org in the NVflash folder i created, i was able to flash, enter clockworkmod and wipe old data and voila.
THANKS roebeet and others who help us rivalize and surpass IPAD. Now everyone in my town wants one!
Mantara said:
Have you tried powering it down from the bootloop and then powering it back on normally without going back into recovery?
I kept getting bootloops coming back to vegan from TnT lite and was frustrated as hell untill one time I forgot to hold down vol + and it booted fine. I had changed nothing as the 3 previous boots were just wiping data / cash / davlic.
I also get that error when trying to wipe dalvic and was told that it has something to do with a part of partition 2 but never got more info than that.
Sent from my Chromatic Magic using XDA Premium App
Click to expand...
Click to collapse
Yes, I get bootloops after installing a ROM from sdcard, from internal storage and even after wiping all but the boot partitions(cache, dalvik, data, sdcard) via cwm. I was able to wipe data now by partitioning my sdcard 2048/0 and will be trying to install via sdcard again here shortly.
Retrodrift said:
My friend wanted a Gtablet when he saw mine with TnT 4.2.5, he couldn't get over the fact i control my PC with VNC viewer, can view my webcams etc etc. So he offered me a 32G micro SD to order one for him and ROOT it. Long story short once in 4.2.5 and downloading everything in the market it froze or something then went into boot-loop. then i really messed with it and then magic NO-GO (only messed with it because i knew WE had such awesome support HERE)
1st flash only gave me a boot loop, then affter finally understanding to rename the recovery.img in clockworkmod v08 to part9 and part9 to part9.org in the NVflash folder i created, i was able to flash, enter clockworkmod and wipe old data and voila.
THANKS roebeet and others who help us rivalize and surpass IPAD. Now everyone in my town wants one!
Click to expand...
Click to collapse
Yes, I've nvflashed w/ recovery and cwm in place of recovery; mentioned this towards the end of my initial post. =]
I have also set partition to 2048/0 and no issues the past hour of stress tests
Hi Notwen
Initially i also received the E:Can't mount /dev/block / Error mounting /data/! prompt. In CWM I unmounted everything in advanced, formatted everything, rebooted and only had the Viewsonic birdy screen with 'Magic..error' script above left, that's it. Proceeded to NVflash process from there
Not sure what the root cause of it all, but simply repartitioning the sd card 2048/0 killed the bootloops and I was able to load and install ROMs from the internal storage. TNT Lite 4.3.2 is up and running great now. Thanks all for the recommendations/help. =]
Awesome! Good to hear! Repartitionong can really fix a lot of goofy errors. I do it instead of wiping everything when installing a new rom. I just move my backups to my PC and let er rip.
Sent from my Chromatic Magic using XDA Premium App
My gtablet has been very happy and stable with the VEGAn-TAB GingerEdition STABLE RC1 rom for the last couple of months, but I've just run into a problem I can't get out of.
I was connected to my PC via USB about to copy some data off the tablet when everything froze. I needed to cycle power to get back to a workable system. Connected again via USB, and it froze again.
Next I booted into clockwork recovery and figured I'd have a look around to make sure everything was healthy with the filesystem. It wasn't. I was unable to mount the system partition.
At this point, I figured things were looking grim, so I opted to nvflash back to stock and maybe try again with the ROM. nvflash went ok, but after rebooting it bootloops at the white gtablet screen after 10-15 seconds or so.
Now when I try to go into recovery mode, it comes up to a black screen that reads "A N D R O I D", then i get an exclamation point, then it bootloops.
help! not sure how to proceed here.
thanks in advance for any pointers anyone can give me!
Code red (or maybe double red):
http://viewsonic-gtablet-for-dummies.webs.com/
I've gotten clockwork recovery reinstalled using this technique: http://forum.xda-developers.com/showthread.php?t=1058649
From there, I repartitioned the sdcard to 2048/0. It took a lot longer than I remembered it usually taking, but once that completed, I rebooted and got into the stock ROM without further issue.
Thanks for the space -- I've gotten rusty after having not run into any flashing difficulties for a while!
Double red it was! Thanks for that link bmag666. Definitely going in my perma-bookmarks.
Ok, I swear I have read 100 pages of similar problems, but it looks like everyone else is able to get into apx mode at least to run nvflash or easy flasher.
1. Turn on xformer with power button - stuck at Asus Eee Pad screen
2. Try to boot into recovery with vol - + power;
- volume up to enter recovery, ded android with an exclamation
- volume down to choose between 'wipe' and 'cold boot' both result in getting stuck at Asus screen
3. Plug in xformer, hold power and vol +; nothing. Never shows up in device manager and it doesn't beep or anything like the ones in all the videos do.
I really just want to get up and running at the very least, as I handle all of my businesses billing through my xformer, but my ultimate goal is to get on the HD-ROM.
I have downloaded the newest firmware from asus, have all the drivers installed (I think), have tried booting into recovery with one, some or all of the new software on the sdcard.
Any more ideas I can try? Do you just have to hold your mouth right to get it into apx mode? I have held those buttons so much I think I'm getting Nintendo thumb!!!
Thanks all!
nobody?
Throw something at me! What update.zip file do I put on the sd card? I have tried putting the newest asus update.zip on there with both its original name and the update.zip name. still comes up with a dead android and an exclamation point.
Download a firmware from Asus, rename it to EP101_SDUPDATE.zip
Put it on the root of your sd card and boot into recovery, hopefully it will flash it and let you boot up.
As for NVFlash, make sure you install teh APX driver.
Still won't get past about a second or two of trying to boot with EP101_SDUPDATE.zip on the sd card. Think I'm stuck, or is there something else I need to try?
Thanks!!
..Do the apx process and try using brks tool......just dont flash touch recovery! I couldnt get the drivers to show but still managed to nvflash recovery using the tool. Its install solarnz external sd recovery so you can put a rom zip onto micro sd.
My issue was after doing this normal on off reboot kept booting to recovery and i had to cold boot into the rom.
I tried the wheelie beta and it has ended up wiping the tf completely.....so dont do that lol. Its still a soft brick as i could still nvflash recovery but decided that aslongs its wiped of root etc id just send it to asus.
If brks tool flashes for you then id try nvflashing prime and see if that works.......i think it will but i ran out of time and patience this morning to do it......at your own risk of course.
scottyf79 said:
..Do the apx process and try using brks tool......just dont flash touch recovery! I couldnt get the drivers to show but still managed to nvflash recovery using the tool. Its install solarnz external sd recovery so you can put a rom zip onto micro sd.
My issue was after doing this normal on off reboot kept booting to recovery and i had to cold boot into the rom.
I tried the wheelie beta and it has ended up wiping the tf completely.....so dont do that lol. Its still a soft brick as i could still nvflash recovery but decided that aslongs its wiped of root etc id just send it to asus.
If brks tool flashes for you then id try nvflashing prime and see if that works.......i think it will but i ran out of time and patience this morning to do it......at your own risk of course.
Click to expand...
Click to collapse
i am the same issue by flashed the touch CWM and window wont able to reconigzed my TF as a APX device
i tried many drivers it still not able to work.
how can i get back to normal CWM? i dont have havy roms or update.zip in internal roms.. and Touch CWM wont able to recongized Removerable sdcard
god~~
The root and backup option should flash you an external recovery.
While tablet reboots hold down volume up and power until reboot stops.
Then try brks tool again and select root and backup.......during the process it may ask if you want to back up but its not worth while as i dont think theres anything to backup. You should end up with ext micro sd recovery.
As i said id look for the prime rom thread and download the nv flash version and see if it works first.
If asus restore the wiped TF without question and everything goes ok il let you know as it may be worth wiping it with wheelie nv recovery and just RMA.
I just simply CAN'T get it into apx mode. I've installed, uninstalled and reinstalled the drivers. Trying to flash ep101_sdupdate.zip still just results in an error. crap.
Hold Volume-UP BEFORE holding power, then hold power for 5 secs (Still holding vol-up( doing this all while connected. It should show in device manager.
Couldnt get Tf to show in device manager either no matter what.
I know it may not seem as though its in apx but if it has stopped rebooting when you do v up and power then it seems it is......
Seems to be an issue thats starting to become more common and very difficult to fix properly.
PC will just not recognise the TF.
Hmm - sorry i couldnt help more but id still try nv flashing Prime and if you can get to a blank screen using volume up and power without the TF rebooting theres a chance its in apx.
Best of luck dude.......
scottyf79 said:
Couldnt get Tf to show in device manager either no matter what.
I know it may not seem as though its in apx but if it has stopped rebooting when you do v up and power then it seems it is......
Seems to be an issue thats starting to become more common and very difficult to fix properly.
PC will just not recognise the TF.
Hmm - sorry i couldnt help more but id still try nv flashing Prime and if you can get to a blank screen using volume up and power without the TF rebooting theres a chance its in apx.
Best of luck dude.......
Click to expand...
Click to collapse
same case for me~~~just cant install the driver
You all can try running Puppy or DSL (damn small linux) in a virtual box on your windows pc. Comes with drivers included and only is a 200/60 Mb download.
Got so frustrated with it I just went and bought a tf-300
c3poman said:
Got so frustrated with it I just went and bought a tf-300
Click to expand...
Click to collapse
no better way to fix it than that
nice one
Yea, I like it pretty good so far. Volume is WAY louder on the 300, even though there is only one speaker. The screen also gets darker, which is nice if you watch tv or browse the interwebs in the bed. Also, wifi reception is great. Haven't tried gps yet, but I'm sure it is improved.
It did get really laggy, but I did a factory reset and it seemed to clear out the cobwebs.
Thanks for y'all's help! I'm still going to try to unbrick that tf-101 and sell it or something. Hate to have a $400 paperweight...
People will buy bricked ones on Ebay for a reduced price, just clarify that it is in fact bricked.
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