[Eee Pad Transformer Q&A, Help & Troubleshooting] ZigaG:
Hello everybody!

Recently I have discovered solution to my problem with TF101G. I am going to explain the problem and solution further on in the post.

PROBLEM:

I wanted to update my cousin's Transformer TF101G to Android 4.2.2 (Team EOS rom). But in order to do this, I needed to root and install custom recovery on the tablet. I successfully rooted it with THIS method and it worked, but there was an error with recovery, so I decided to upgrade it with another. I installed ROM Manager (later on I discovered that I shouldn't have done this!!!) and installed CWM recovery. Now the recovery worked and I couldn't boot into Android!!!

- I couldn't unbrick it with nvflash method -> Asus didn't provide keys for TF101G's nvflash mode

- The CWM recovery installed by ROM Manager didn't support shutdown and external sdcard -> I was able to install new recovery via ADB and PERI's method for unbricking, but this didn't solve the problem with bootloop

- I was able to communicate with ADB

Because nothing worked, I decided to find the solution myself. I discovered that I had problem with mounting main partition, because ROM Manager probably messed up with format of the main partition (ASUS has made data partition also for sdcard data).

SOLUTION, if you can access tablet with ADB via Recovery:

If you are going to use this method for unbricking your Transformer tablet, be sure you check if you have the same partition layout:

- Connect your tablet in recovery to PC with ADB.

- Connect to tablet's shell with: adb shell

- Check how many partitions you have with: ls /dev/block/

- If you have: mmcblk0, mmcblk0p1, mmcblk0p2, mmcblk0p3, mmcblk0p4, mmcblk0p5, mmcblk0p6, mmcblk0p7

- Check if mmcblk0p7 is the biggest (if this is your partition for data) with: fdisk -l /dev/block/mmcblk0p7 -> partition needs to be approximately the size of your tablet's storage (8GB, 16GB, 32GB)

- Check also if mmcblk0p7 is partition for data with: cat /etc/fstab

- If there is listed: /dev/block/mmcblk0p7 /data ext4 rw, my method will probably fix your bootloop!

FORMATTING DATA PARTITION:

You will need Recovery that supports external sdcard. You can install it with PERI installer

- You still need to be in tablet's shell (# sign indicates, that you are in this mode)

- You are probably going to need busybox, which you can get from HERE (I couldn't find original post, where it was posted, so I uploaded the file to dropbox.).

- Move the file busybox to external SDCARD and insert it to Transformer tablet (You should also copy ROM of your choice to your sdcard, because you will need it later to install Android)

- Mount external sdcard to /sdcard, you can also try to mount it with recovery:

mount /dev/block/mmcblk1p1 /sdcard

- Check if the mounting was successful with:

ls /sdcard

- You need to get output of files, that are on your sdcard:

- NOW BE VERY CAREFUL TO NOT FORMAT THE WRONG PARTITION, BECAUSE I WON'T BE ABLE TO HELP IN THAT CASE!!!

- Format main partition (this is the biggest partition on tablet, in my case is mmcblk0p7. BE CAREFUL, RATHER CHECK MORE-TIMES THAN NOT!) to ext2, which will be later converted to ext4:

/sdcard/busybox mke2fs -t ext2 /dev/block/mmcblk0p7

OR (if the upper code doesn't work)

/sdcard/busybox mkfs.ext2 /dev/block/mmcblk0p7

- Convert partition to ext3:

tune2fs -j /dev/block/mmcblk0p7

- Convert partition to ext4:

tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p7
e2fsck -fpDC0 /dev/block/mmcblk0p7

- Exit from ADB shell with command: exit

OK this should fix the problem with main partition. Now you only need to install new ROM from recovery. I think you already know how to do this.

If you need any question regardless this method, reply with question or even better try to find solution yourself. In this way you will learn a lot of new things.

I hope it helped you!

Žiga

Thank you *Detection* for providing the files that I needed to find the solution!

Original post: