CROMBi-kk infinite loop

I have ventured into the world of flashing my ft700t after reading this article and have gotten in over my head very quickly. In my attempt to fix the issue, I'm sure I tried Wipe Data in recovery after installing the custom rom. Now I read that is bad.

Where I am now, I have an unlocked bootloader and can connect with usb. When I try to boot the rom, I get the endless restarting of 4 penquins.

Well, first I suggest a whole bunch of reading, so that you at least have the jargon down to the point where we can communicate effectively. Here's a place to start:Beginners Guide to flashing a custom ROM on TF700T
Now, it sounds like you simply had a bad flash, or flashed a bad download. Yes, if you got as far as the 4 penguins, you must have had an unlocked bootloader (one doesn't unlock a fastboot, it isn't locked), and a custom recovery. We need to know what version of what recovery you might have installed; the devil's in the details for this stuff. I recommend this one:http://forum.xda-developers.com/tran...rea51-t3049395
But a later one is OK so long as it's for the 700.

HOLD THE FORT! I just noticed that you say you have a TF701. You are posting in the 700 section. This needs to be sorted out before we continue. But IIRC that ROM was never ported to 701 and that is likely your problem, it isn't going to boot on a 701. Make sure you have the ROM and tablet matching.

Kevin, I started with the Beginners Guide once my flash attempt failed. I'm sure I am mixing terms so appologies for that, this is all very new. Yes, it is a TF700T. I must have overlooked that option in the registration, but have corrected my profile.

From the beginning...I did not install the bootloader unlock tool in this round. When the tablet boots, it displays the message "the device is unlocked" at the logo screen. Is that the same thing? This is my second attempt to flash so I think it is unlocked.

I attempted to install TWRP - twrp-2.6.3-that3_Signed.zip

When I boot with Power + Vol - I see this:
The device is unlocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Checking for RCK.. press key <vol_up> in 5 sec to enter RCK

You have an ICS bootloader on your tablet which is completely outdated for any KK rom or recovery

I get the endless restarting of 4 penquins

The penguins indicate that you have a _that kernel installed which is part of the KK rom, so at some point you had a custom recovery and flashed a rom.
My guess is you flashed TWRP 2.6 which did boot with the ICS bootloader (a small miracle in itself) and then you flashed the KK rom which will not boot with an ICS bootloader.
Then you flashed TWRP 2.8 which will not boot with an ICS bootloader (which is just as well because performing any action in a recovery incompatible with the installed bootloader can easily hard brick a device) and that's why you now get nothing when trying to enter RCK.

The good news is this is fixable in fastboot.
The bad news is you don't seem to have a working fastboot connection between PC and tablet ???

>fastboot devices
? fastboot

At some point you did have fastboot since you flashed TWRP successfully twice, so let's hope just rebooting the PC or changing USB ports will fix that problem.
So focus on that and only that: Get fastboot working, meaning you get a positive return for the command 'fastboot devices'

Once that works you should flash the Asus system blob in fastboot - the best way to a) upgrade your bootloader to the latest version and b) get back to a complete stock system so that you can start from scratch.
I have walked people so many times through this - let me find a thread that describes it and I'll add the link later.

Wait until you get the command prompt back which will take a few minutes, then

Code:

fastboot reboot

You should now reboot into a fresh JB 4.2.1 stock rom.
Follow the link on top of the Beginners guide to it's version on XDA and read at least the first 3 posts.
Then flash TWRP 3.0 or later.
To install a new rom you first have to format /data and then you should convert /data to the f2fs file system (only if you flash a rom that supports f2fs). https://forum.xda-developers.com/tra...p-2-8-t3073471
Don't flash CROMbi-KK - it sucks. Flash timduru's Katshmallow or Nougatella and follow the instructions in the OP.
You'll like it

Since I last flashed twrp kang 2.8.7.4, do I need to update that? I should add I ran another series of commands that were posted to help after running the Wipe Data. That involved removing the systems partitions and several others using fastboot. Do those need to be recreated?

Win10 again! Try again with a USB2 port, (black one) if you have it. For some reason, USB3 gets particular sometimes. There are several Windows driver packages available, if changing ports doesn't get it you might try different drivers. Make sure you obliterate the old ones before installing the new! A simple Windows uninstall is usually not sufficient. You may have better luck with an older machine, Win7 or XP. If nothing else works, pick a live Linux disk, boot to that and install the Fastboot binary. But you need to consistently get a return from fastboot devices while your tablet is booted into the screen with the 3 icons. Don't hit the volume-down button, just leave it at that screen. If it won't stay on that screen, you may be screwed.

Since I last flashed twrp kang 2.8.7.4, do I need to update that? I should add I ran another series of commands that were posted to help after running the Wipe Data. That involved removing the systems partitions and several others using fastboot. Do those need to be recreated?

Fastboot does not support removing partitions. You may have wiped them of their data, but the partitions themselves are untouched.
If you flash the Asus blob you will return your system to stock - including the recovery partition. So: Yes you have to reflash TWRP.

You did have fastboot earlier, didn't you? Did you get a positive response with 'fastboot devices' then?
You can skip trying 'adb devices'. ADB only works in recovery or when booted into Android. You won't get a response when booted into the bootloader.
Device manager shows and recognizes the ADB bootloader interface.... You are running Windows as admin?

IDK, maybe you managed to erase the partition that has the device ID and that is the reason it only returns a ? fastboot??
I have no idea. But Windows seems to recognize the fastboot connection, loads the blob but then fails to write it to the device.
I have seen many instances where under Windows it "should" have worked and didn't and the same commands worked without a problem on the same machine under Linux....

Try this:
Type "accessories" in the Win search box
You should see "Command Prompt" as an option
Right click it and choose "run as admin"
Allow when prompted, then cd into your fastboot directory and try to flash the blob again. For me it looks like this, your path will be different:win admin.PNG

If that does not work try the command

Code:

fastboot flash staging blob

I'm not sure if the Staging partition is large enough for the blob, but it's worth a try. Staging is used to "park" low level software which the BL will write to it's proper partition during the next boot.
Then reboot

Interesting you ask about the cable. Yes, it is the original cable. However, I noticed yesterday one of the flat connector pins had gotten bent over the years of use. I know that will raise a lot of suspicion. It's the proprietary wide flat connector that goes in the bottom of the tab. It also has a mini usb port on the side. Is it possible to use that port for flashing? If not, I will need to find a new cable.