Partition information / Unbricking

[berndblb]

Thanks for the info! I might try with these zips and bootloaders. I am trying to reset my tablet or make it work. Had cm-12.1-20160711-NIGHTLY-tf701t.zip on it with TWRP recovery and US_epad-10.26.1.18-20131217 bootloader but it recently stoppped working. I do have access to the bootloader and recovery but after following the fastboot instructions and rebooting nothing is changed on the tablet.

Probably nothing wrong with BL or recovery if you can boot into it. Try formatting data in TWRP and then flash a rom that's compatible with your current BL/recovery combo.
You will have to format data anyway if you're moving to a different rom....

 

[xabier87]

Probably nothing wrong with BL or recovery if you can boot into it. Try formatting data in TWRP and then flash a rom that's compatible with your current BL/recovery combo.
You will have to format data anyway if you're moving to a different rom....

I am sorry, the recovery I wrote was wrong. I have the PhilZ Touch 6.59.0 recovery. The problem is that it is useless. Also I have used fastboot boot recovery TWRP.img and even with that recovery I have the same problem. Basically both recoveries can't mount the partitions properly and can't format data or install rom. When I try it says: E: Error mounting /data or /cache.

 

[AllexBast]

Hello. How can I increase the size of the SOS partition?

 

[dim^n]

Hello, I got problem with this device. Earlier everything seemed to be working, then I tried to flash any rom via TWRP, but cant. Has no problem with nandroid restoring of data and system. Thought it was a problem of TWRP, flashed Philz touch, tried to flash roms via Philz touch, but it was the same result. Then something goes wrong and philz touch flashed with error. Tf701 shows me logo, then tried to boot to recovery, it shows navbar with buttons, and then reboots (feature of Philz — reboot on failure) . Vol- + power just reboot the device. Adb devices command on pc cant see my brick device, I think the data and system wasnt formatted before failure, and debugging was enabled. PC only shows "K00C" when the device tried to boot into rck, and "APX". Manual installing of drivers cant help me. Device discharges for 1-2 days, when it in "off" state (by pressing vol+ and power), thats strange (UPD, I thought it was power off, but its APX mode, thats useless. Found DIP trigger on motherboard, that is the power trigger) . Tried to open and disconnect battery from motherboard, but it has no effect. Face-palm. Is this a nand failure, or I can help it somehow?

 

[berndblb]

You may have come here a little late...
If you cannot boot into fastboot or recovery and the tablet is in a continous reboot cycle it's probably done for.
The K00C is the device name for the TF701 though. How long does that show in device manager?

 

[dim^n]

How long does that show in device manager?

something about 5 secs, since recovery starts to boot and till it reboots the device. Has no idea what drivers should I install. Tried to install via inf files Adb+fastboot drivers from xda and 4pda, but that cant help my PC to detect my device.
Found in one of threads that flashing bootloader is dangerous. Maybe I should delete it from TWRP install archive cause when I tried to flash roms, Ive changed recoveries 6-8 times, and here it is.

 

[berndblb]

There are a number of things I don't understand:
You must have had a working fastboot driver since you were able to flash a recovery (6-8 times!!???) so why are you trying to install adb fastboot?
What's that about a bootloader? Why is flashing it dangerous and why would you want to flash one? Flashing anything is dangerous if you don't do it right.
What rom were you trying to flash before you borked it?
If you cannot get into fastboot anymore you may have one small chance to fix this. But I cannot remember if this method has ever been tried on a TF701. It works on all the other Transformers but this one - I donlt know. Use it at your own risk:
http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Good luck

 

[dim^n]

There are a number of things I don't understand:
You must have had a working fastboot driver since you were able to flash a recovery (6-8 times!!???) so why are you trying to install adb fastboot?
What's that about a bootloader? Why is flashing it dangerous and why would you want to flash one? Flashing anything is dangerous if you don't do it right.
What rom were you trying to flash before you borked it?
If you cannot get into fastboot anymore you may have one small chance to fix this. But I cannot remember if this method has ever been tried on a TF701. It works on all the other Transformers but this one - I donlt know. Use it at your own risk:
http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Good luck

1. I flashed install zips with recoveries inside it.
2. Dont know why, Its not my opinion:

TBCH, I'm not sure about the BC1.
The recovery is not part of the blob (anymore?). And the exact way an official update flashes it is probably not the best way to go when flashing manually. My advice for the moment probably is: Keep flashing the bootloader to a minimum, and flash recoveries via fastboot.

3. I tried to flash KatKiss and Blisspop
4. Ok thanks, this only if the PC will see my brick device!

 

[dim^n]

Finally I install drivers and rebooted my tab to bl! Then flashed TWRP and restored BlissPop rom that I used. But I still cant flash roms from recovery (see the screenshot). Thats why I want to revert to stock configuration rom, recovery, bl, etc as the 1st post said. But here some questions. Can I flash stock rom via stock recovery or TWRP (link from instruction is broken)? And can I use 10.26.1.18 rom that I already have? Thanks a lot!

 

[berndblb]

Finally I install drivers and rebooted my tab to bl! Then flashed TWRP and restored BlissPop rom that I used. But I still cant flash roms from recovery (see the screenshot). Thats why I want to revert to stock configuration rom, recovery, bl, etc as the 1st post said. But here some questions. Can I flash stock rom via stock recovery or TWRP (link from instruction is broken)? And can I use 10.26.1.18 rom that I already have? Thanks a lot!

Before you try the stock rom, just try this:
In TWRP convert /system to ext3, then back to ext4, then flash the rom. It's a bug in TWRP....

I don;t think you can flash the stock firmware zip in recovery. You can try.... unzip the download once so that you have a zip with just a blob and a meta-inf file, then flash that in recovery, but it will most likely fail.
You can however flash the stock blob in fastboot. Although I have not done this on this tablet myself, I don;t see a reason why it should not work. I've done it on both the TF300 and TF700 numerous times.
With the blob in your fastboot directory the command is: fastboot flash system blob

 

[llskyll]

TF701T bootloader 0x00000008 error

Dear friends, I ask to help or assist advice or council.
TF701T K00C 4.4.2 began to disconnect spontaneously, and I decided to reflash it.
Asus unlock tool said the device was unlocked, but it did not reset the tablet and the message that the devise is unlocked did not appear on the download, but Kingo Root did it and Official TWRP App accepted twrp-3.1.0-0-tf701t_final_full_f2fs_v6 and wrote that the bootloader was updated. When I tried to get into the recovery, the tablet gave bootloader failed, but after the reboot the android booted. I rebooted the tablet and entered the recovery again - it turned out to be a drain - then I selected the wape data item and after the reboot I saw Unrecoverable bootloader error (0x00000008) and then the Asus sign does not load.
I downloaded the driver Asus MeMO Pad 8 ME581CL, launched the info file to set up Asus drivers in to Windows, and launched the fastboot, but it does not see the tablet (and Windows does not see the tablet). Tell me, please, what to do?

 

[berndblb]

Dear friends, I ask to help or assist advice or council.
TF701T K00C 4.4.2 began to disconnect spontaneously, and I decided to reflash it.
Asus unlock tool said the device was unlocked, but it did not reset the tablet and the message that the devise is unlocked did not appear on the download, but Kingo Root did it and Official TWRP App accepted twrp-3.1.0-0-tf701t_final_full_f2fs_v6 and wrote that the bootloader was updated. When I tried to get into the recovery, the tablet gave bootloader failed, but after the reboot the android booted. I rebooted the tablet and entered the recovery again - it turned out to be a drain - then I selected the wape data item and after the reboot I saw Unrecoverable bootloader error (0x00000008) and then the Asus sign does not load.
I downloaded the driver Asus MeMO Pad 8 ME581CL, launched the info file to set up Asus drivers in to Windows, and launched the fastboot, but it does not see the tablet (and Windows does not see the tablet). Tell me, please, what to do?

Oh boy! There are a few things in your post that do not make sense - I assume translation problems? - but that probably won't make a difference. If you cannot boot into the bootloader to get fastboot access and the tablet does not boot past the first Asus logo, so it does not even attempt to boot into recovery, you're done for. The tablet is dead and only a new mainboard will revive it. Sorry.
If you're interested to learn why you bricked it, read on:

that the devise is unlocked did not appear on the download

I think you mean to say "did not appear when booting"??

Official TWRP App accepted twrp-3.1.0-0-tf701t_final_full_f2fs_v6 and wrote that the bootloader was updated

. You mean it confirmed the recovery was flashed? Or did you flash a BL/recovery package???
Fair warning: Rant up ahead!
How I hate these apps that make it "easy" to flash a recovery!!! It should not be easy! If a user does not care to invest time to learn and setup fastboot and adb he/she has no business flashing anything to anything!!!!Period! - end rant-

the tablet gave bootloader failed,

Uh-oh, huge red warning, this is the point where you should have asked for help

it turned out to be a drain

- ???? Don't understand

selected the wape data item

The final nail to the coffin. You never wipe data from the bootloader if you have a custom recovery installed. Never.

I downloaded the driver Asus MeMO Pad 8 ME581CL, launched the info file to set up Asus drivers in to Windows

Wrong driver and probably way too late to think about setting up fastboot. This should have been step 1 in the whole thing.....
Sorry for your loss man!

 

[Sleeepy2]

@berndblb you're probably not going to get thanked for your post because unfortunately it seems like it too late for this tablet.
But I wanted to thank you. Your posts are always informative and try to help people if they like it or not

 

[DarkPaLadin]

Many many thanks! Again and again!