Database Info

My Asus TF300T Is Completely Dead!

I had upgraded to 4.2 firmware (WW_epad-user-10.6.1.8) using the second method described on http://forum.xda-developers.com/showthread.php?t=2187982. This worked well and everything was working until I messed up today D: I was trying to flash SuperSU using TWRP but it couldn't recognize my Internal SD Card so I thought there might be something wrong with my installation. When I entered the bootloader I noticed the message: Key driver not found.. Booting OS. I don't know what this means. I did not read the first thread in the General section and tried to do a restore using the 4.2 firmware package. I used the "fastboot flash system blob" command and this time everything was messed up. The blue bar that appears on installation is no longer appearing and I have an "unrecoverable bootloader" error. Nothing I did worked! What should I do?? Please provide me some simple steps. I used these commands before flashing system blob...
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This was a very stupid move on my part but I thought this would allow a clean install D: D: Please help!

gee man you completely wiped the sucker, you may be bricked =(. i would start by trying to fastboot flash the patched version of twrp. unless you can boot into twrp already then try to flash the asus package again thru twrp. also, could twrp see your internal sd before you bricked?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

markymark567 said:
gee man you completely wiped the sucker, you may be bricked =(. i would start by trying to fastboot flash the patched version of twrp. unless you can boot into twrp already then try to flash the asus package again thru twrp. also, could twrp see your internal sd before you bricked?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
No, that is the reason why I wiped everything (stupid move I know)...TWRP was screwed up to begin with. I flashed 2.5 JB version and it couldn't detect my internal SD card. I made sure it was the right model and everything so TWRP messed me up. I don't know how to flash a working version of TWRP since I don't know what version works with 4.2 tf300 firmware.

sonar2854 said:
No, that is the reason why I wiped everything (stupid move I know)...TWRP was screwed up to begin with. I flashed 2.5 JB version and it couldn't detect my internal SD card. I made sure it was the right model and everything so TWRP messed me up. I don't know how to flash a working version of TWRP since I don't know what version works with 4.2 tf300 firmware.
Click to expand...
Click to collapse
there is a modded 2.4.4 version i believe that sees all correctly. the post on how to root and update describe and link it. but being now you flashed the wrong one. you cant mount anything to flash correct one. i think you are s.o.l. i hope iam am wrong. good luck.

kaos420 said:
there is a modded 2.4.4 version i believe that sees all correctly. the post on how to root and update describe and link it. but being now you flashed the wrong one. you cant mount anything to flash correct one. i think you are s.o.l. i hope iam am wrong. good luck.
Click to expand...
Click to collapse
I'm not sure how to flash it...I tried fastboot flash recovery twrp.blob (2.4.4.0 v4.2). It just freezes although the cmd says it was successful

I keep getting a bootloader error (0x0000000) everytime I try and enter RCK, Android, Wipe Data... Is there a way to reinstall the bootloader? WW_epad 10.6.1.8

No mate
As of now there's no solution to that.
Do ppl ever read before they flash? I've never seen as much bricks as I've seen on this device since the new 10.6x.x Asus bootloader... it's a shame
Read read read, understand understand understand, then read more. I almost feel sorry for you guys who are "just flashing away"

FML :crying::crying:

sonar2854 said:
I keep getting a bootloader error (0x0000000) everytime I try and enter RCK, Android, Wipe Data... Is there a way to reinstall the bootloader? WW_epad 10.6.1.8
Click to expand...
Click to collapse
Bump!
I have a couple of questions.
I would like to know about your bootloader (how many icons and which ones) and whether you can still get into twrp.

tobdaryl said:
Bump!
I have a couple of questions.
I would like to know about your bootloader (how many icons and which ones) and whether you can still get into twrp.
Click to expand...
Click to collapse
Okay, so when I press Volume Down + Power, I enter the bootloader. The bootloader has three icons: RCK, Android Logo, Wipe Data. I have no access to TWRP since there is a unrecoverable bootloader error 0x0000000 when I try to enter RCK.

sonar2854 said:
Okay, so when I press Volume Down + Power, I enter the bootloader. The bootloader has three icons: RCK, Android Logo, Wipe Data. I have no access to TWRP since there is a unrecoverable bootloader error 0x0000000 when I try to enter RCK.
Click to expand...
Click to collapse
The odds are slim but let's try a couple of things.
From power off, hold power and volume down, release when you see the icons. You should see the entering fastboot message in the upper left.
fastboot -i 0x0B05 reboot bootloader
if that fails
Power off and use the same procedure.
fastboot reboot bootloader
Tell me the result.

tobdaryl said:
The odds are slim but let's try a couple of things.
From power off, hold power and volume down, release when you see the icons. You should see the entering fastboot message in the upper left.
fastboot -i 0x0B05 reboot bootloader
if that fails
Power off and use the same procedure.
fastboot reboot bootloader
Tell me the result.
Click to expand...
Click to collapse
Okay, I tried both and it doesn't work without adding a hyphen in between reboot and bootloader so reboot-bootloader. Otherwise, with the hyphen added, both work.

sonar2854 said:
Okay, I tried both and it doesn't work without adding a hyphen in between reboot and bootloader so reboot-bootloader. Otherwise, with the hyphen added, both work.
Click to expand...
Click to collapse
Sorry for that mistake. Now try rck and let's see if the bootloader is now accepted. If we are lucky the result has changed.

tobdaryl said:
Sorry for that mistake. Now try rck and let's see if the bootloader is now accepted. If we are lucky the result has changed.
Click to expand...
Click to collapse
Eh...I don't really know how to explain this but this is what happened. Once the bootloader rebooted after entering the CMD command, I pressed volume up to access RCK and there was a "blink" and there is now a green glowing square around the Android Icon. I cannot move the volume up or down (it is frozen on the Android Icon with the green square glowing), so I don't know what that "blink" was. If i try to press volume up now there is the bootloader error again.

sonar2854 said:
Eh...I don't really know how to explain this but this is what happened. Once the bootloader rebooted after entering the CMD command, I pressed volume up to access RCK and there was a "blink" and there is now a green glowing square around the Android Icon. I cannot move the volume up or down (it is frozen on the Android Icon with the green square glowing), so I don't know what that "blink" was. If i try to press volume up now there is the bootloader error again.
Click to expand...
Click to collapse
Download the 10.4.2.20 stock firmware. Unzip once and rename the resulting zip EP201_768_SDUPDATE.zip. Place this on your external sdcard and boot into your bootloader. Volume up on RCK.

tobdaryl said:
Download the 10.4.2.20 stock firmware. Unzip once and rename the resulting zip EP201_768_SDUPDATE.zip. Place this on your external sdcard and boot into your bootloader. Volume up on RCK.
Click to expand...
Click to collapse
Um, I don't have an external SD Card? The only SD Card I have is the Internal Storage

sonar2854 said:
Um, I don't have an external SD Card? The only SD Card I have is the Internal Storage
Click to expand...
Click to collapse
Uh!
Tell me what 2.5 JB version is.
Unzip 10.6.1.8 stock firmware twice and place the blob file into the directory with adb and fastboot. Boot into the bootloader and don't press anything.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
if the command fails try again without -i 0x0B05

tobdaryl said:
Uh!
Tell me what 2.5 JB version is.
Unzip 10.6.1.8 stock firmware twice and place the blob file into the directory with adb and fastboot. Boot into the bootloader and don't press anything.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
if the command fails try again without -i 0x0B05
Click to expand...
Click to collapse
When you say 2.5 JB version...are you talking about TWRP? I don't think TWRP is on the tablet because I can't access it. All I saw was a blink when I pressed volume up on RCK, not TWRP? I have tried flash system blob before I posted here and it did nothing. There is no progress bar when fastboot flashing =/ I think it froze. Yup it froze, just tried to do fastboot reboot-bootloader and it said failed. Also, after the system was done writing, after 2 seconds it said complete so it didn't work.

sonar2854 said:
When you say 2.5 JB version...are you talking about TWRP? I don't think TWRP is on the tablet because I can't access it. All I saw was a blink when I pressed volume up on RCK, not TWRP? I have tried flash system blob before I posted here and it did nothing.
Click to expand...
Click to collapse
I understood about twrp and flashing system blob but I thought we had been able to get stock recovery working instead of twrp.
I 'm sorry that is all I have with no sdcard and no adb.

tobdaryl said:
I understood about twrp and flashing system blob but I thought we had been able to get stock recovery working instead of twrp.
I 'm sorry that is all I have with no sdcard and no adb.
Click to expand...
Click to collapse
I have never used the stock recovery so what is it supposed to look like? Is it that dead Android with the battery because that didn't show up? I will try and get an external sd card tomorrow and try it if you think it might work. I have the 4.2 bootloader so are you sure that I should put Version V10.4.2.20 and recover using that version? Anyways, if it ends up not working, I would just like to say thank you very much for trying.

Recovery failing to flash

So I flash the stock rom on it without thinking and now it wont let me flash a recovery to the tablet threw fastboot or goomanager and it wont update throguh asus update but its booting fine and wont take any updates at all i need help being pointed in the right direction!

I flashed the wrong bootloader i think and how do i flash the correct bootloader without a recover?

in fastboot im getting the error: cannot load 'file name' :no error weather its cm or twrp it wont load it and i dont know what to do please help

First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?

berndblb said:
First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?
Click to expand...
Click to collapse
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess

Skittleskitty said:
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess
Click to expand...
Click to collapse
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.

berndblb said:
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.
Click to expand...
Click to collapse
thank you so much that fixed it!!

ok i did all that but it removed fastboot what do i do to get it back?

Skittleskitty said:
ok i did all that but it removed fastboot what do i do to get it back?
Click to expand...
Click to collapse
Read the text in the upper left corner - current bootloaders enable fastboot in the bootloader menu automatically.

ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.

Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
Then maybe it's not in your current directory.

Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial

berndblb said:
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial
Click to expand...
Click to collapse
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.

ok ive re installed fastboot and adb sdk and did the environment variable path and it still wont recognize the blob it wont recognize cwm .img files ether and what does key driver not found..booting os

Skittleskitty said:
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.
Click to expand...
Click to collapse
It has to be in your *current* directory.

_that said:
It has to be in your *current* directory.
Click to expand...
Click to collapse
thankyou it moved directorys on me that was the issue

[Q] 2 Issues when rooting: No SU binary installed, & red triangle on dead android.

[Q] 2 Issues when rooting: No SU binary installed, & red triangle on dead android.
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
adb push UPDATE-SuperSU-vX.XX.zip /sdcard/
Click to expand...
Click to collapse
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!
Click to expand...
Click to collapse
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?

How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip

FrostedFluke said:
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?
Click to expand...
Click to collapse
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.

El Daddy said:
How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip
Click to expand...
Click to collapse
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
aooga said:
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.
Click to expand...
Click to collapse
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905

FrostedFluke said:
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.

FrostedFluke said:
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Yep, that is the correct command. I would recommend using the most recent SU.zip as well.

aooga said:
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.
Click to expand...
Click to collapse
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?

FrostedFluke said:
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?
Click to expand...
Click to collapse
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).

aooga said:
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).
Click to expand...
Click to collapse
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"

FrostedFluke said:
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"
Click to expand...
Click to collapse
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip

El Daddy said:
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip
Click to expand...
Click to collapse
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)

FrostedFluke said:
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)
Click to expand...
Click to collapse
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.

El Daddy said:
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.
Click to expand...
Click to collapse
I get this on my command prompt: "error: closed"

FrostedFluke said:
I get this on my command prompt: "error: closed"
Click to expand...
Click to collapse
run the command: adb usb
Then try sideloading

El Daddy said:
run the command: adb usb
Then try sideloading
Click to expand...
Click to collapse
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?

FrostedFluke said:
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?
Click to expand...
Click to collapse
yes

El Daddy said:
yes
Click to expand...
Click to collapse
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?

FrostedFluke said:
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?
Click to expand...
Click to collapse
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.

El Daddy said:
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.
Click to expand...
Click to collapse
Yup! it's rooted :victory:

FrostedFluke said:
Yup! it's rooted :victory:
Click to expand...
Click to collapse
Congrats!

[Q] CROMBi-kk flash

Hi!
I hope you can help me.
I obviously did something wrong.
Well I did unlock my tablet and got twrp running, also installed the rom but next after the reboot it just doesn't work and i will get this message (see the picture)
After that i am sent back to the interface of twrp.
I just recogniced I have twrp v.2.6.1.0 running - is that the problem?
Hopefully somebody can help me!
greets agepi

agepi91 said:
Hi!
I hope you can help me.
I obviously did something wrong.
Well I did unlock my tablet and got twrp running, also installed the rom but next after the reboot it just doesn't work and i will get this message (see the picture)
After that i am sent back to the interface of twrp.
I just recogniced I have twrp v.2.6.1.0 running - is that the problem?
Hopefully somebody can help me!
greets agepi
Click to expand...
Click to collapse
YOU MUST BE ON THE ASUS STOCK JB 4.2.1 BOOTLOADER VERSION 10.6.1.14.x AND TWRP 2.6.3.2+ OR CWM 6.0.4.6+ BEFORE FLASHING THIS ROM.
This is copied directly from the Developers ROM.
Cheers

agepi91 said:
Hi!
I hope you can help me.
I obviously did something wrong.
Well I did unlock my tablet and got twrp running, also installed the rom but next after the reboot it just doesn't work and i will get this message (see the picture)
After that i am sent back to the interface of twrp.
I just recogniced I have twrp v.2.6.1.0 running - is that the problem?
Hopefully somebody can help me!
greets agepi
Click to expand...
Click to collapse
You didn't use 'Wipe Data' from the bootloader, did you?
Read the OP for CROMBI-KK, compare it to what you did.
Describe in detail what that was.
"Does not work" is not very helpful...
Check if you can get into fastboot.
Sent from my DROID4 using Tapatalk

Well,
I can go to Twrp recovery and fastboot
I did install the rom with everything present I think.. had to select some things and finish the installing
after that I had to reboot and now i just get the image with the penguins.
Can I somehow go back to the original rom? to restart these things?

agepi91 said:
Well,
I can go to Twrp recovery and fastboot
I did install the rom with everything present I think.. had to select some things and finish the installing
after that I had to reboot and now i just get the image with the penguins.
Can I somehow go back to the original rom? to restart these things?
Click to expand...
Click to collapse
If you made a nandroid before flashing this, then yes, you should be able to restore it.
But let's take it from the beginning. Post your bootloader, recovery and rom versions.
As long as you have access to fastboot you can fix this, so don't do anything hasty.
And please be as specific as you can about what you did. We can only help you if we find out where you went wrong.

berndblb said:
If you made a nandroid before flashing this, then yes, you should be able to restore it.
But let's take it from the beginning. Post your bootloader, recovery and rom versions.
As long as you have access to fastboot you can fix this, so don't do anything hasty.
And please be as specific as you can about what you did. We can only help you if we find out where you went wrong.
Click to expand...
Click to collapse
hm ok I will try
well, I didn't make a nandroid backup - my fault :<
are there specific bootloader? I was on JB 4.2.1
I am now on twrp v2.6.3.2 but I was while I did the flashing on twrp v2.6.1
hm I did flash crombi-kk rom from the OP
maybe I did some wipe before in twrp .. i think it was recommended?
so now I can't do any reflash or anything in twrp - everytime I want to do something there is this error:
E: Unable to open '/cache/recovery/.version'
I also can't get access to my external SD

Check if you can get into fastbot.
Long press Power and Volume Down until you see tiny script.
Read it and post the bootloader version: 10.6.1.14.?

berndblb said:
Read it and post the bootloader version: 10.6.1.14.?
Click to expand...
Click to collapse
Well it reads: ww_epad-10.6.1.14.10-20130801

agepi91 said:
Well it reads: ww_epad-10.6.1.14.10-20130801
Click to expand...
Click to collapse
All right, your bootloader is current.
I would recommend that you flash TWRP 2.7 in fastboot, then boot into it, do a Factory Wipe in TWRP (that can take upwards of 60 minutes) and flash the rom again.

Ok.. I tried but I got the answer
failed (data transfer failure (too many links))
hm I think I've got no connection, right?
well and now I get the message:
FAILED ( command write failed( invalid argument))

What do you get with 'fastboot devices'?
Sent from my K00C using Tapatalk

I get 015d2a5068541017 fastboot

agepi91 said:
I get 015d2a5068541017 fastboot
Click to expand...
Click to collapse
Alright, everything good so far.
Now download the TWRP 2.7 blob for the tf700 and put it into the same folder as your fastboot.exe.
Then issue this command:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
if that is successful
Code:
fastboot reboot
Then boot into TWRP via the fastboot menu.
Then you can factory wipe and flash the rom

berndblb said:
Alright, everything good so far.
Now download the TWRP 2.7 blob for the tf700 and put it into the same folder as your fastboot.exe.
Then issue this command:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
if that is successful
Code:
fastboot reboot
Then boot into TWRP via the fastboot menu.
Then you can factory wipe and flash the rom
Click to expand...
Click to collapse
Well I did that but nothing works
I've got now twrp 2.7 and i did that factory wipe but nothing ever happens.. just the usual message
'unable to open 'cache/recovery/.version'
Don't know what I did wrong :<
http://imageshack.com/a/img842/662/kwy9.png
that's the message I everytime get - doesn't matter if it's a wipe or install or something else

in bootlooder at the top there is this message:
>key driver not found... booting 05<

is it possible to formate my complete data, because I think therein lies the problem, exept fastboot on my device and flash a recovery from fastboot?

agepi91 said:
is it possible to formate my complete data, because I think therein lies the problem, exept fastboot on my device and flash a recovery from fastboot?
Click to expand...
Click to collapse
If you want to try that, go to the Wipe menu in TWRP, then to Advanced and choose "format data".
In TWRP this can take 90 minutes! D not interrupt it and make sure the tablet is charged or connected to power.
But this will erase your entire data.
The recovery has it's own partition which you can erase in fastboot:
Code:
fastboot erase recovery
.
Then flash the new recovery. You could also try TWRP 2.6.3.2 if 2.7 doesn't work.

agepi91 said:
is it possible to formate my complete data, because I think therein lies the problem, exept fastboot on my device and flash a recovery from fastboot?
Click to expand...
Click to collapse
Your posted image indicates that simulation mode is active in TWRP - turn if off in TWRP settings.
To format data, it's approximately this: Wipe -> Advanced -> Format -> Data -> confirm
Note that it takes up to 2 hours to format and trim the eMMC.
---------- Post added at 09:15 PM ---------- Previous post was at 09:14 PM ----------
berndblb said:
The recovery has it's own partition which you can erase in fastboot:
Code:
fastboot erase recovery
.
Click to expand...
Click to collapse
...which is usually a stupid idea if you don't know exactly what you are doing.

Well I don't know how but it suddenly worked.. i could reinstall the rom but now it seems i am stuck in a bootloop between the picture of the four penguins and a bootscreen of crombi-kk with loading tiles under it
between these two the tablet is rebooting itself constantly

Go back to recovery and do a wipe only Calvin cache and Cache.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

[Q] [SOLVED] i think its bricked! any suggestion?

hey guys!
Firstly, i want to install TF300 KitKat 4.4.2 CROMBi-kk my tf300 but my twrp version isnt compatible with this rom. I try to update my twrp to 2.7.0.0 at this topic "http://forum.xda-developers.com/showthread.php?t=2686235"
Secondly, i flashed my recovery to 2.7.0.0 with fastboot but it isn't successfully completed. After that i try to flash official twrp ver. 2.6.3.0 (I guess i updated wrong ver of twrp) and it's accomplished.
After update process, i restarted my tf300 but android doesn't start and teamwin screen came. twrp show my internal memory 0 mb.
Now, i can start my OS through adb with "adb reboot-bootloader " command and select android.
First question. How can fix internal memory problem?
Second question. How can i change twrp ver. with true ver.?
Third question. How can i install new clean ROM?
thanks for your interest.

any help?

Apoptozis said:
any help?
Click to expand...
Click to collapse
You don't get answers probably because it's hard to understand what it is you're asking. I understand English may not be your first tongue, but that's the only means of communication we have here. So try your best English: What exactly is your problem?

graphdarnell said:
You don't get answers probably because it's hard to understand what it is you're asking. I understand English may not be your first tongue, but that's the only means of communication we have here. So try your best English: What exactly is your problem?
Click to expand...
Click to collapse
Firstly, i want to install TF300 KitKat 4.4.2 CROMBi-kk my tf300 but my twrp version isnt compatible with this rom. I try to update my twrp to 2.7.0.0 at this topic "http://forum.xda-developers.com/showthread.php?t=2686235"
Secondly, i flashed my recovery to 2.7.0.0 with fastboot but it isn't successfully completed. After that i try to flash official twrp ver. 2.6.3.0 (I guess i updated wrong ver of twrp) and it's accomplished.
After update process, i restarted my tf300 but android doesn't start and teamwin screen came. twrp show my internal memory 0 mb.
Now, i can start my OS through adb with "adb reboot-bootloader " command and select android.
First question. How can fix internal memory problem?
Second question. How can i change twrp ver. with true ver.?
Third question. How can i install new clean ROM?
thanks for your interest.

Apoptozis said:
Firstly, i want to install TF300 KitKat 4.4.2 CROMBi-kk my tf300 but my twrp version isnt compatible with this rom. I try to update my twrp to 2.7.0.0 at this topic "http://forum.xda-developers.com/showthread.php?t=2686235"
Secondly, i flashed my recovery to 2.7.0.0 with fastboot but it isn't successfully completed. After that i try to flash official twrp ver. 2.6.3.0 (I guess i updated wrong ver of twrp) and it's accomplished.
After update process, i restarted my tf300 but android doesn't start and teamwin screen came. twrp show my internal memory 0 mb.
Now, i can start my OS through adb with "adb reboot-bootloader " command and select android.
First question. How can fix internal memory problem?
Second question. How can i change twrp ver. with true ver.?
Third question. How can i install new clean ROM?
thanks for your interest.
Click to expand...
Click to collapse
Ok
So if your tablet is off and you boot normally it will boot into recovery?

lj50036 said:
Ok
So if your tablet is off and you boot normally it will boot into recovery?
Click to expand...
Click to collapse
yes exactly.

Apoptozis said:
yes exactly.
Click to expand...
Click to collapse
You can boot into the bootloader screen, the one with the 3 icons?
Also known as the fastboot screen?
If so can you see your tablet with the
Code:
fastboot devices
command?
Thx Josh

lj50036 said:
You can boot into the bootloader screen, the one with the 3 icons?
Also known as the fastboot screen?
If so can you see your tablet with the
Code:
fastboot devices
command?
Thx Josh
Click to expand...
Click to collapse
yes, i use bootloader screen (3 icons) for boot android.
and yes i see my device with "fastboot devices" command.

I'd try to reflash the recovery from fastboot
Sent from my GT-I9100 using XDA Free mobile app

totalnoob34 said:
I'd try to reflash the recovery from fastboot
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
i try to reflash my recovery with fastboot many times. But my device stuck after writing process.

Apoptozis said:
i try to reflash my recovery with fastboot many times. But my device stuck after writing process.
Click to expand...
Click to collapse
Ok try to erase your misc partition with this command
Code:
fastboot erase misc
Then after that type
Code:
fastboot reboot
See if it boots into android
Let me know
Thx Josh

lj50036 said:
Ok try to erase your misc partition with this command
Code:
fastboot erase misc
Then after that type
Code:
fastboot reboot
See if it boots into android
Let me know
Thx Josh
Click to expand...
Click to collapse
device opened perfectly!

Apoptozis said:
device opened perfectly!
Click to expand...
Click to collapse
Great !!!! :good:
Can you add SOLVED to the thread title....
Thx Josh