Database Info

[fixed] Did I brick it?

Hi there. I was fooling around with my TF300T (I was foolish at some point, probably) and managed to install Jellybean using this method. It started working fine. So it did that I restored my files using Titanium Backup Pro, installed from the App store right after the first boot. The apps/data I restored with Titanium Backup, as far as I can remember, were mostly games and Dolphin stuff, nothing directly related to system, as far as I know.
After this backup restoration, I used the tablet a little more, played the games to check if my progress was not lost and all that. It worked, Angry Birds at least had all the levels I completed before yet marked as completed after restore the procedure.
So far so goo... no! For some reason I can't remember I restarted the tablet, at least I tried! It got stuck on the loading screen (the white Asus, not the shiny one). So, after that I tried to restore it again, and then I probably did something completely stupid and I can't even remember what.
I even tried superwipe on it, but that didn't work neither.
At this point my tablet let me flash recovery image, CWM and TWRP. I can use adb shell with CWM but not with TWRP.
For some reason, I don't know, when I use CWM it doesn't mount /sdcard, TWRP seem to be mounting it, but go figure, I can only access the /sdcard that TWRP mounts using TWRP, if I change the recovery to CWM for some bizarre (or obvious to you guys) reason, I can't mount it.
And no matter what recovery I use, I can't flash any ROM. Both recovery tells me it was flashed, no error message (at least not at the screen) but every time it reboots to finish the installation, I see the Asus logo with a progress bar that goes from 0% to 100% in less then one second, and once it's filled, the tablet reboots itself and show me the regular boot screen with the Asus logo (again, the white one, not the silver-shiny).
So, resuming my problem, I can fastboot and adb shell it (adb only with ClockWorkMod Touch), but flashing doesn't seem to work. And I believe the internal memory/storage structure have been compromised.
How do I fix this?
Here is what I did to fix it
brbjr said:
...
Download a cm9 rom, open the zip file and extract boot.blob . Flash with 'fastboot -i 0x0B05 flash boot boot.blob' then reboot...
Click to expand...
Click to collapse
manegonzalez said:
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
Doing it now. I'll update as soon as I finish it. Thank you very much for your reply.
UPDATE 1: I can see the shiny-silver ASUS and the progress circles, waiting to see what happen!
UPDATE 2: Setting up Jellybean now (Welcome setup)!
UPDATE 3: Looks like it's working!
Dude, thank you so much! I'll fool around with it. Is there a root method working already? I was wondering if there's a way to restore my backups, at least the ones I made for my gaming progress.

Man you saved my life. Thank you very much!

When i try it i get error: "Failed to process command flash: system error(0xa)"
any help?

Thank you for posting this thread, I wasn't paying attention one day and flashed the wrong version of something and ended up stuck on the white Asus logo. Flashed a ROM's blob via fastboot and was up and running in no time, though it did take 2 attempts, the first time it received the blob but failed to write it.

Itege said:
Thank you for posting this thread, I wasn't paying attention one day and flashed the wrong version of something and ended up stuck on the white Asus logo. Flashed a ROM's blob via fastboot and was up and running in no time, though it did take 2 attempts, the first time it received the blob but failed to write it.
Click to expand...
Click to collapse
You're welcome!
Now click thank you so you can help me
I recommend you to use the CleanROM 2.5, it's stable and fast! Really fast! Faster then the ASUS Stock ROMs. I'm really enjoying it.

Still can't flash ROMs
Thanks so much for this. It really helped to get me back to where I was. However, I still can't flash any roms besides the stock asus jb. What can i do? I've tried several different ROMs. I still get stuck at the ASUS "The Device is Unlocked" page

poisondminds said:
Thanks so much for this. It really helped to get me back to where I was. However, I still can't flash any roms besides the stock asus jb. What can i do? I've tried several different ROMs. I still get stuck at the ASUS "The Device is Unlocked" page
Click to expand...
Click to collapse
Fastboot TWRP or CWM recovery, format everything in there and flash ex. cleanrom 2.5
Let me know if it won't work

allram said:
Fastboot TWRP or CWM recovery, format everything in there and flash ex. cleanrom 2.5
Let me know if it won't work
Click to expand...
Click to collapse
For CleanROM he'll need a specific TWRP version. It's better give CleanROM thread a read before install it.

allram said:
When i try it i get error: "Failed to process command flash: system error(0xa)"
any help?
Click to expand...
Click to collapse
Any luck with this? I'm having the same issue...
This tablet is such a fiesty little *****... Nowhere near as simple as my GNex to flash things.
I'm having the exact same issue as you did. It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
Please tell me you know what to do... I'm getting desperate. I can't end up with a $500 paperweight...

Guticb said:
Any luck with this? I'm having the same issue...
This tablet is such a fiesty little *****... Nowhere near as simple as my GNex to flash things.
I'm having the exact same issue as you did. It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
Please tell me you know what to do... I'm getting desperate. I can't end up with a $500 paperweight...
Click to expand...
Click to collapse
1. Please, make sure the Tablet is the only one Android device connected to your computer
2. The bootloader is unlocked, right?
3. It's not the matter (almost impossible to be the case), but what are you using as recovery, TWRP or CWM?
4. Are you trying to flash the Official ROM?
- Sent from the Future, using my Delorean
- Enviado do Futuro, usando meu Delorean

mizifih said:
Originally Posted by brbjr View Post
...
Download a cm9 rom, open the zip file and extract boot.blob . Flash with 'fastboot -i 0x0B05 flash boot boot.blob' then reboot...
Quote:
Originally Posted by manegonzalez View Post
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
This is an awesome fix, thought I was buggered with a tablet that couldnt mount anything, couldn't get into download mode, recovery was fubared.. and then I stumbled on this
THANK YOU

[Q] Please help - ASUS Transformer Infinity TF700 Brick

Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?

GRIM1337 said:
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
Click to expand...
Click to collapse
I am having the same issue. Just rooted today. Please help!

dpadaddict said:
I am having the same issue. Just rooted today. Please help!
Click to expand...
Click to collapse
Are you able to get into fastboot? If you press and hold power and volume down until you get the option to press volume up to boot to recovery, but don't press voume up, then you will boot into the bootloader screen, with fastboot as an option.
At this site you will find the correct twrp (choose Download - Recovery Image / Fastboot Method) and instructions to flash:
http://teamw.in/project/twrp2/105
Instructions for fastboot and adb you'll find by searching around.
Hope that helps!

fordwolden said:
Are you able to get into fastboot? If you press and hold power and volume down until you get the option to press volume up to boot to recovery, but don't press voume up, then you will boot into the bootloader screen, with fastboot as an option.
At this site you will find the correct twrp (choose Download - Recovery Image / Fastboot Method) and instructions to flash:
Instructions for fastboot and adb you'll find by searching around.
Hope that helps!
Click to expand...
Click to collapse
I wish I could... The message I receive is as follows when I do that:
The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image
And nothing ever shows up. Just the ASUS logo.

Did you solve your problem? I'm having the same issue and tried to install custom ROMs without solving the problem

reboot the device! (power and vol down for 5 sec)
hold vol down at the ASUS screen, but don't go to recovery, just wait until you see a 3 different logos on your screen.
An Android, a Wipe and a USB Icon
go between theese logos with vol down choose USB Icon with vol up!
Now you are in Fastboot mode and with your PC you can flash another recovery image.
But by the way!
WHY THE HELL DID YOU UNLOCKED YOUR DEVICE IF YOU ARE TOTALLY NEW TO ANDROID?!
You don't need this if you are new to android, even root does a good deal for first serious steps!

kabauterman said:
But by the way!
WHY THE HELL DID YOU UNLOCKED YOUR DEVICE IF YOU ARE TOTALLY NEW TO ANDROID?!
You don't need this if you are new to android, even root does a good deal for first serious steps!
Click to expand...
Click to collapse
Hey, we were all new to Android at some point! That's how you learn though, by doing this sort of stuff. Nothing wrong wth trying! Just need to be careful and read alot. But, you have to start somewhere!
I'm sure that he was reading all of the "Jelly Bean ROM's are so awesome" posts and wanted to see for himself, that's all....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:
Hey, we were all new to Android at some point! That's how you learn though, by doing this sort of stuff. Nothing wrong wth trying! Just need to be careful and read alot. But, you have to start somewhere!
I'm sure that he was reading all of the "Jelly Bean ROM's are so awesome" posts and wanted to see for himself, that's all....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I never said I was new to Android. I was new to the ASUS stock tablet recovery orientation (its landscape as I found out). Hence, hit up twice, wiped data. I am by no means new in general. I did not fix the problem. I requested an RMA with Newegg and it was approved I said the issue with it was bad screen bleeding (no lie but it is normal for this tablet but bad was exaggerated) In any case! RMA approved should be getting my new unit Tuesday!

unlocked and RMA because of your own stupidity?
ok do it..
have you tried it with fastboot?

fix
GRIM1337 said:
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
Click to expand...
Click to collapse
Just follow this method and you will be fine
http://forum.xda-developers.com/showthread.php?t=1755576

kabauterman said:
unlocked and RMA because of your own stupidity?
ok do it..
have you tried it with fastboot?
Click to expand...
Click to collapse
If you had my OP in its entirety, you would know that is impossible. :/ Unfortunately, after the data + cache wipe two things happened that I do not understand. 1. The device wouldn't boot (this shouldn't happen unless all partitions were formatted which the device did NOT report it did), 2. This is the really strange part, recovery no longer existed after JUST WORKING - even after my mistake with ROM manager stock recovery remained until the wipe and then I received the message mentioned in my OP (namely: Booting recovery kernel).

GRIM1337 said:
If you had my OP in its entirety, you would know that is impossible. :/ Unfortunately, after the data + cache wipe two things happened that I do not understand. 1. The device wouldn't boot (this shouldn't happen unless all partitions were formatted which the device did NOT report it did), 2. This is the really strange part, recovery no longer existed after JUST WORKING - even after my mistake with ROM manager stock recovery remained until the wipe and then I received the message mentioned in my OP (namely: Booting recovery kernel).
Click to expand...
Click to collapse
Any resolution to this other than the RMA?

HelgesenJ said:
Any resolution to this other than the RMA?
Click to expand...
Click to collapse
Please don't tell me you have used ROM Manager recently. : S Are you having the same issue?
APX available, or not (as with the OP)? NvFlashed? What have you done, or tried to do, yourself?
Moar. Info.

MartyHulskemper said:
Please don't tell me you have used ROM Manager recently. : S Are you having the same issue?
APX available, or not (as with the OP)? NvFlashed? What have you done, or tried to do, yourself?
Moar. Info.
Click to expand...
Click to collapse
One more who used ROM manager recently and now I have a nice tray for serving beers :crying:
I'm having the same issue with APX available by powering on the transformer holding volume+up but with no nvflash backup.

I don't understand why people keep using ROM manager to install recovery, this is a death wish to your device. If they read all the "How to" posts, none of them instructed to use rom manager to install recovery, so I don't know where they got this idea from???? beat me!!!
GRIM1337, you need RMA to send out for repair. Sorry but there's no hope to recovery this.

Didn't use ROM Manager
Updated to JB (from rooted ICS), then tried to unlock and flash recovery: Bootloader is still locked, recovery and system partitions are simply gone!
All I can access is fastboot now, but as bootloader is locked, I cannot flash any custom image/blob or whatsoever.
Can someone generous post their stock recovery or help me flash the JB update ZIP again?
I extracted the blob, but I'm not sure how to flash it? I suppose it contains all the partitions I would need to flash! But how to flash them?
I tried this:
fastboot -i 0x0b05 flash staging blob
Fails after having downloaded the 800Mb blob, the exact same way it fails flashing a custom kernel!?
sending 'staging' (800199 KB)...
OKAY [145.978s]
writing 'staging'...
FAILED (remote: (InvalidState))
finished. total time: 205.000s

3c said:
Updated to JB (from rooted ICS), then tried to unlock and flash recovery: Bootloader is still locked, recovery and system partitions are simply gone!
All I can access is fastboot now, but as bootloader is locked, I cannot flash any custom image/blob or whatsoever.
Can someone generous post their stock recovery or help me flash the JB update ZIP again?
I extracted the blob, but I'm not sure how to flash it? I suppose it contains all the partitions I would need to flash! But how to flash them?
I tried this:
fastboot -i 0x0b05 flash staging blob
Fails after having downloaded the 800Mb blob, the exact same way it fails flashing a custom kernel!?
sending 'staging' (800199 KB)...
OKAY [145.978s]
writing 'staging'...
FAILED (remote: (InvalidState))
finished. total time: 205.000s
Click to expand...
Click to collapse
How did you get into fastboot mode for your device??

buhohitr said:
How did you get into fastboot mode for your device??
Click to expand...
Click to collapse
Well that one's hard: With ICS bootloader, there was like no fastboot mode!!! On the bootloader menu I could only confirm recovery or cancel to boot as usual!!! WTF? But then once with JB bootloader, the menu allowed me to select a different option: a new one had appeared showing a USB logo too! Can't tell if I simply missed the option or proper steps in ICS bootloader though.

3c said:
Well that one's hard: With ICS bootloader, there was like no fastboot mode!!! On the bootloader menu I could only confirm recovery or cancel to boot as usual!!! WTF? But then once with JB bootloader, the menu allowed me to select a different option: a new one had appeared showing a USB logo too! Can't tell if I simply missed the option or proper steps in ICS bootloader though.
Click to expand...
Click to collapse
ICS bootloader had the fastboot option disabled if the device's bootloader was still locked and the USB icon wasn't showing at all.
With the JB bootloader Asus made the USB icon available even if the device was locked so you can access fastboot mode but you can't flash anything (yes,it doesn't make sense, but this is Asus).
Anyway, if you are able to boot in recovery you should be able to restore you device easily,just follow my guide from the general forum.

Re: Help needed i will try
OK WHAT YOU HAVE DONE IS WIPED THE OS FROM THE UNIT...AND LEFT THE BOOTLOADER FILES...SO THERE ISNT
ANYTHING TO BOOT TO AT THE MOMENT... I DID THIS LAST WEEK... IT WAS A BIT SCARY AND FRUSTRATING UNTIL
I FIGURED OUT HOW TO FIX IT.. ITS NOT HARD. ILL PUT DOWN HERE WHAT I DID...
1. DOWNLOAD THE GOOGLE NEXUS 7 TOOL KIT... ( this is a very good rescue tool )
2. RUN IT... INSTALL THE DRIVERS... REBOOT IT ALL AND START THE TOOL KIT AGIAN WITH YOUR TRANSFORMER
CONNECTED TO USB...
3. YOU SHOULD SEE THE SERIAL NUMBER OF YOUR TABLET AT THE TOP OF THE PAGE IN THE TOOLKIT...
IF SO..YOUR ALMOST DONE !
4. THERE ARE MANY CHOICES..SOME WORK SOME DONT ON THE TRANSFORMER...
5. I CHOOSE THE ROOT OPTION...
6. NOW..WHEN IT GETS TO THE PART WHERE IT SAYS ARE U IN FASTBOOT MODE.. SAY NO !!! THAT WILL ACTUALLY
PUT IT IN FASTBOOT AND THEN PROCEED AS DIRECTED ON THE SCREEN TO ROOT...
THATS WHAT I DID...CAUSE I NEEDED ROOT AND I HAD A STUCK BOOT LOOP JUST LIKE YOU.....
BASICALLY YOU NEED TO ROOT IT AGIAN AN THEN REBOOT AND TRY TO GET INTO CWM..OR HAVE IT REINSTALL CWM...TO FLASH A ROM...THAT WORKS..

[Q] I seem to have soft-bricked my TF300. Ideas?

I was just in this thread, where someone fixed their soft brick: http://forum.xda-developers.com/showthread.php?p=37314263#post37314263
Mine stemmed from the same thing. Trying to flash a JB rom over ICS.
My TF300, when it boots up, only has options for fastboot and normal boot (AKA, stays on a white Asus logo). There's no way for me to get into a recovery, even though I had TWRP installed. I tried using NVflash, but there's no way to use it when your tablet is already soft bricked.
It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
It also has some weird issues in fastboot mode. the reboot command doesn't actually reboot the tablet, even though it says successful. Also, it'll only run one command at a time successfully before I start getting all sorts of errors in command prompt.
I have no idea where to start with this thing... Any suggestions?
edit: Also, wiping data from fastboot doesn't seem to do anything. It just freezes. Likewise, in fastboot, when I let it sit and it's supposed to reboot on its own, it doesn't.

Guticb said:
I was just in this thread, where someone fixed their soft brick: http://forum.xda-developers.com/showthread.php?p=37314263#post37314263
Mine stemmed from the same thing. Trying to flash a JB rom over ICS.
My TF300, when it boots up, only has options for fastboot and normal boot (AKA, stays on a white Asus logo). There's no way for me to get into a recovery, even though I had TWRP installed. I tried using NVflash, but there's no way to use it when your tablet is already soft bricked.
It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
It also has some weird issues in fastboot mode. the reboot command doesn't actually reboot the tablet, even though it says successful. Also, it'll only run one command at a time successfully before I start getting all sorts of errors in command prompt.
I have no idea where to start with this thing... Any suggestions?
edit: Also, wiping data from fastboot doesn't seem to do anything. It just freezes. Likewise, in fastboot, when I let it sit and it's supposed to reboot on its own, it doesn't.
Click to expand...
Click to collapse
Try this link for access to recovery or apx.

No luck. The tablet literally doesn't have a recovery at all. Trying to flash any stock ROM through fastboot results in failure.
Every time I try, command prompt gives me the error FAILED (remote: (InvalidSize)) and my tablet does the "Failed to process command flash:system error(0xa)" message
I'm not sure if any flashes through fastboot are even working right. It says success, but the reboot command never works (Even though that says success, too)

Have you tried reflashing your recovery then installing a stock rom from there?

Guticb said:
No luck. The tablet literally doesn't have a recovery at all. Trying to flash any stock ROM through fastboot results in failure.
Every time I try, command prompt gives me the error FAILED (remote: (InvalidSize)) and my tablet does the "Failed to process command flash:system error(0xa)" message
I'm not sure if any flashes through fastboot are even working right. It says success, but the reboot command never works (Even though that says success, too)
Click to expand...
Click to collapse
No fastboot, no recovery, no apx backup
Sell it for parts
Lcd
Digitizer
Battery
Etc
Or buy a new mobo
Envoyé depuis mon ASUS Transformer Pad TF300T avec Tapatalk

lightitwithfire said:
Have you tried reflashing your recovery then installing a stock rom from there?
Click to expand...
Click to collapse
Yeah. No luck. It'll say success, but the tablet freezes and the reboot command doesn't work. After I manually reboot, no luck either.

I've looked up some information about it. People who experience the same problem (not able to get into recovery, adb, etc) had to send their tablet into Asus and it got shipped to Czech Republic, then in about 3 weeks it's returned ready to go. Maybe that's a possible route? If not, search xda-developers deeper and check out transformerforums. They have alot of stuff linked to XDA so who knows, maybe what you're looking for is on there.
Best of luck to you!

Guticb said:
Yeah. No luck. It'll say success, but the tablet freezes and the reboot command doesn't work. After I manually reboot, no luck either.
Click to expand...
Click to collapse
Which recovery do you flash
Jb or ics version
Cwm or twrp
Envoyé depuis mon ASUS Transformer Pad TF300T avec Tapatalk

dont waste more time
As i posted somewhere else, this tablet is a pretty bad purchase.
I bricked mine without unlocking bootloader, without flashing anything, without even connecting it to the computer.
One day it got stuck in asus screen.
After hard reset, recovery and wipe data i was left out with a brick. (no more snk, usb, wipe data screen)
Interesting you can brick a tablet without doing all those things they warn you not to do.
Dont waste more time looking for a solution. theres none, your tablet is now a useless brick.
sell it to someone who needs the parts.

gomezdf said:
As i posted somewhere else, this tablet is a pretty bad purchase.
I bricked mine without unlocking bootloader, without flashing anything, without even connecting it to the computer.
One day it got stuck in asus screen.
After hard reset, recovery and wipe data i was left out with a brick. (no more snk, usb, wipe data screen)
Interesting you can brick a tablet without doing all those things they warn you not to do.
Dont waste more time looking for a solution. theres none, your tablet is now a useless brick.
sell it to someone who needs the parts.
Click to expand...
Click to collapse
Wow, that's really weird. Hard to believe that it just bricked itself one day. Since it was never unlocked, did you take advantage of the warranty and say it was a manufacture defect?

Guticb said:
I was just in this thread, where someone fixed their soft brick: http://forum.xda-developers.com/showthread.php?p=37314263#post37314263
Mine stemmed from the same thing. Trying to flash a JB rom over ICS.
My TF300, when it boots up, only has options for fastboot and normal boot (AKA, stays on a white Asus logo). There's no way for me to get into a recovery, even though I had TWRP installed. I tried using NVflash, but there's no way to use it when your tablet is already soft bricked.
It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
It also has some weird issues in fastboot mode. the reboot command doesn't actually reboot the tablet, even though it says successful. Also, it'll only run one command at a time successfully before I start getting all sorts of errors in command prompt.
I have no idea where to start with this thing... Any suggestions?
edit: Also, wiping data from fastboot doesn't seem to do anything. It just freezes. Likewise, in fastboot, when I let it sit and it's supposed to reboot on its own, it doesn't.
Click to expand...
Click to collapse
I had the same issue although it stemmed from a different origin. I'm guessing it won't reboot on its own because you've wiped the /system files. Can you still connect to your PC using fastboot? If yes, try the command "fastboot -w", then try fastbooting the stock ICS blob file. By the way, I'm still new to the Android platform but I've learned quite a bit in the last few weeks by tinkering with my two Android devices and soft-bricking them several times in the process.
A

I had the same problem, and my understanding is that it stems from a messed up bootloader. Literally, I had the -exact- same error messages so I know what you are going through.
Fortunately, I was able to use NVFlash to recover mine. I don't know what other solution there would for you, my friend. Best of luck, let us know what ASUS charges for the repairs if you decide to go that route.

[Q] Brickety Brick

I couldn't leave well enough alone and I f'd up somehow trying to flash my pad to 4.2 stock from Cyanogen with TWRP. Now booting thru vol- and power brings up TWRP only. It asks me for a password, which it never has before. I hit cancel and it puts me into home screen. Only ray of hope I see is that ADB still recognizes it and interacts with it. I've tried pushing every ROM I can get my mitts on to the pad. When I try and install it fails after a few seconds. Then the files I just pushed are no longer on /sdcard. I don't have a clue.
Anyone, anyone? Bueller, Bueller...

dedalus2k said:
I couldn't leave well enough alone and I f'd up somehow trying to flash my pad to 4.2 stock from Cyanogen with TWRP. Now booting thru vol- and power brings up TWRP only. It asks me for a password, which it never has before. I hit cancel and it puts me into home screen. Only ray of hope I see is that ADB still recognizes it and interacts with it. I've tried pushing every ROM I can get my mitts on to the pad. When I try and install it fails after a few seconds. Then the files I just pushed are no longer on /sdcard. I don't have a clue.
Anyone, anyone? Bueller, Bueller...
Click to expand...
Click to collapse
Make sure you have flashed the correct version of TWRP. as there are three different versions on their website. If you are confident you have flashed correct TWRP version then you may need to downgrade to the previous version of TWRP. I had a similar issue I downgraded to 2.4.4.0 JB build. Hope this helps

"...you may need to downgrade to the previous version of TWRP."
I can't get into fastboot to install an earlier version. I think I'm screwed.
Theoretically I could use TWRP to totally wipe the pad and then ADB to push the system files back on, but... I don't have that kind of tech knowledge and I doubt anyone who doesn't work for ASUS does.
Edit: My mistake. You can use ADB to install TWRP. I'll give it a shot, though I'm pretty damn sure it's a long one.

dedalus2k said:
"...you may need to downgrade to the previous version of TWRP."
I can't get into fastboot to install an earlier version. I think I'm screwed.
Theoretically I could use TWRP to totally wipe the pad and then ADB to push the system files back on, but... I don't have that kind of tech knowledge and I doubt anyone who doesn't work for ASUS does.
Edit: My mistake. You can use ADB to install TWRP. I'll give it a shot, though I'm pretty damn sure it's a long one.
Click to expand...
Click to collapse
Hey dude just thought I make it easier to understand if you have 3 icons then you will pre load into fastboot if you have four icons then you will have to load fastboot. Lemme know if you run into problems. Happy to help mate.

anaschillin said:
Hey dude just thought I make it easier to understand if you have 3 icons then you will pre load into fastboot if you have four icons then you will have to load fastboot. Lemme know if you run into problems. Happy to help mate.
Click to expand...
Click to collapse
I don't get three or four icons. It boots directly into TWRP. ADB still recognizes the pad and I can still push files to /sdcard. I tried reflashing the ROM but it fails after just a couple seconds, shuts down and boots back into TWRP.
I'm going to get a flashcard reader today and format my external card FAT32 and see if I can't install a new ROM from that.

im in a different situation
i did a erase system in fastboot
now i can only go to fastboot with preload on it
or
apx
is there any wait i can fix it and bring it back to live

Update: Bought a card reader at local Discount Electronics. Plugged it into my PC and it promptly froze my computer and destroyed my $80 64G sd card. Can't catch a break here. So I need to get another card and reader before I can attempt to install rom from external card.
The card reader is by a company called Zeikos. http://www.amazon.com/electronics/dp/B001T9N0R6 You have been warned.

Sheena0220 said:
im in a different situation
i did a erase system in fastboot
now i can only go to fastboot with preload on it
or
apx
is there any wait i can fix it and bring it back to live
Click to expand...
Click to collapse
Can you flash a recovery...
if you manage to flash a recovery run the command: fastboot reboot recovery.

dedalus2k said:
I don't get three or four icons. It boots directly into TWRP. ADB still recognizes the pad and I can still push files to /sdcard. I tried reflashing the ROM but it fails after just a couple seconds, shuts down and boots back into TWRP.
I'm going to get a flashcard reader today and format my external card FAT32 and see if I can't install a new ROM from that.
Click to expand...
Click to collapse
adb reboot bootloader
or
fastboot -i 0x0B05 reboot-bootloader
or
from android terminal - you must be rooted for this to work
su
reboot bootloader

tobdaryl said:
adb reboot bootloader
or
fastboot -i 0x0B05 reboot-bootloader
or
from android terminal - you must be rooted for this to work
su
reboot bootloader
Click to expand...
Click to collapse
I'll give the first one a shot. I can't get into fastboot mode and the su command comes up an error even though I am rooted or was. I really can't figure out where it all went haywire.

YES! I'm in!
tobdaryl said:
adb reboot bootloader
or
fastboot -i 0x0B05 reboot-bootloader
or
from android terminal - you must be rooted for this to work
su
reboot bootloader
Click to expand...
Click to collapse
You are a god amongst men! Thank you sooooo much. If you don't mind...now what?
I get the following messages:
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00e> released by "WW_epad-10.6.1.15.3-20130416" A03
Starting Fastboot USB download protocol
and then the three icons, RCK android and Wipe Data.
After this mishap I don't trust myself to weed through the mountains of info here again. I'm trying to reinstall 4.2.1 and keep it rooted. I'm assuming reinstall 4.2.1 and then reroot, yes? Would you mind terribly pointing me to a reliable post I can follow.
Thank You so much!!!

dedalus2k said:
You are a god amongst men! Thank you sooooo much. If you don't mind...now what?
I get the following messages:
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00e> released by "WW_epad-10.6.1.15.3-20130416" A03
Starting Fastboot USB download protocol
and then the three icons, RCK android and Wipe Data.
After this mishap I don't trust myself to weed through the mountains of info here again. I'm trying to reinstall 4.2.1 and keep it rooted. I'm assuming reinstall 4.2.1 and then reroot, yes? Would you mind terribly pointing me to a reliable post I can follow.
Thank You so much!!!
Click to expand...
Click to collapse
You will have to reroot but with motochopper that is minor.
Unzip 10.6.1.15.3 till you have a blob file. Place the blob in the directory with fastboot.
Reboot into bootloader and wait for fastboot to start. (watch the upper left of the screen)
fastboot -i 0x0B05 flash system blob - wait for the flash to finish then
fastboot -i 0x0B05 reboot
Good Luck!

tobdaryl said:
You will have to reroot but with motochopper that is minor.
Unzip 10.6.1.15.3 till you have a blob file. Place the blob in the directory with fastboot.
Reboot into bootloader and wait for fastboot to start. (watch the upper left of the screen)
fastboot -i 0x0B05 flash system blob - wait for the flash to finish then
fastboot -i 0x0B05 reboot
Good Luck!
Click to expand...
Click to collapse
Grazie Mille! Gonna give it a go right now.
Should I bother with TWRP? I tried to update it before and that's the point it went to hell last time.

tobdaryl said:
You will have to reroot but with motochopper that is minor.
Unzip 10.6.1.15.3 till you have a blob file. Place the blob in the directory with fastboot.
Reboot into bootloader and wait for fastboot to start. (watch the upper left of the screen)
fastboot -i 0x0B05 flash system blob - wait for the flash to finish then
fastboot -i 0x0B05 reboot
Good Luck!
Click to expand...
Click to collapse
Okay. I did it. No joy.
erasing 'system'...
OKAY [2.544s]
sending 'system' <800927 KB>
OKAY [136.994s]
writing 'system'...
OKAY [3.151s]
finished. total time 142.707s
fire off the reboot command
rebooting...
finished. total time 0.551s
But the tab doesn't reboot. And that short "writing 'system'" time to me sounds mighty suspicious
Any ideas? I'm afraid to force reboot it.

dedalus2k said:
Okay. I did it. No joy.
erasing 'system'...
OKAY [2.544s]
sending 'system' <800927 KB>
OKAY [136.994s]
writing 'system'...
OKAY [3.151s]
finished. total time 142.707s
fire off the reboot command
rebooting...
finished. total time 0.551s
But the tab doesn't reboot. And that short "writing 'system'" time to me sounds mighty suspicious
Any ideas? I'm afraid to force reboot it.
Click to expand...
Click to collapse
Reboot into the bootloader. If you get into the bootloader cold boot - volume down on the first icon.
If your tablet fails to boot into android go back to the bootloader and reboot into recovery.
I'll wait for your response.

tobdaryl said:
Reboot into the bootloader. If you get into the bootloader cold boot - volume down on the first icon.
If your tablet fails to boot into android go back to the bootloader and reboot into recovery.
I'll wait for your response.
Click to expand...
Click to collapse
Done and no luck

dedalus2k said:
Done and no luck
Click to expand...
Click to collapse
No recovery either?
What happens in both cases - please explain.

tobdaryl said:
No recovery either?
What happens in both cases - please explain.
Click to expand...
Click to collapse
From off state it always boots into TWRP. I stupidly installed an older version on accident. 2.2.2
With your help I was able to boot into fastboot with the adb command. I've run installs of both the ROM and tried an update to TWRP. According to the console everything went fine but when I give it the reboot command nothing happens. Somewhere in there it looses connections with the tablet it seems.

dedalus2k said:
From off state it always boots into TWRP. I stupidly installed an older version on accident. 2.2.2
With your help I was able to boot into fastboot with the adb command. I've run installs of both the ROM and tried an update to TWRP. According to the console everything went fine but when I give it the reboot command nothing happens. Somewhere in there it looses connections with the tablet it seems.
Click to expand...
Click to collapse
Please explain what happens now. Can you get into the bootloader, recovery, etc?
If you get into the bootloader what happens when you cold boot?
When you boot now without any intervention does it still boot twrp?

tobdaryl said:
Please explain what happens now. Can you get into the bootloader, recovery, etc?
If you get into the bootloader what happens when you cold boot?
When you boot now without any intervention does it still boot twrp?
Click to expand...
Click to collapse
Excuse my noobishness.
I can get into bootloader with the adb reboot bootloader command you gave me
When I go to recovery, RCK right?, it freezes up.
From cold boot it goes directly into TWRP, which asks for a password which it hasn't ever before this mishap.
If I go to android from bootloader and it goes to TWRP as well

TF700 stuck in Boot loop ... have access to bootloader

Hi,
I've posted on this topic on transformerforums website but have not had any success (despite valiant attempts from the guys on the forums).
I am unable to post the link here, please PM me for a link to my original post.
Basically my TF700T got stuck in a bootloop. I have unlocked the bootloader but have not flashed it so it's on stock ROM. I have not been able to flash a recovery ROM and am at a dead end as to what to do.
I am able to get to bootloader and I when I run
Code:
fastboot devices
I get the following output
Code:
015d2a506733f618 fastboot
Which all seems correct. I have access to the tablet when connected to my pc.
When I try to flash the recovery rom, it takes a very short amount of time and on my tablet the device hangs (i.e the RCK icon is no longer flashing). I have checked the blob, it is the correct one and the MD5 hash is correct.
Code:
C:\androidsdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp-2.7.1.1-tf700t.blob
sending 'recovery' (6894 KB)...
OKAY [ 0.868s]
writing 'recovery'...
OKAY [ 0.089s]
finished. total time: 0.958s
I can get back into the bootloader if I restart again but attempting to flash it results in a hang.
I have tried to insert an sd with the stock ROM and boot in RCK mode but this has not worked either.
Has anyone any suggestions as to what to do?
The tablet is 2 years old now so not under warranty.
thanks in advance.

anyone have any suggestions?
I'm going on holidays on Thursday and would really love to get this resolved before I go.

deleted

Shameless bump .... are my only options to return this to the manufacturer?
Anyone any suggestions, do you need more info from me?

What you did looks correct, only the short time for "writing" looks suspicious. Try the fastboot command again, but replace "recovery" with "staging", maybe that works better. At the next reboot you should see a blue progress bar on the boot screen for a few seconds and it should reboot again.

Hi,
Thanks for the reply.
I tried as you suggested and looks like the same results. I'm doing this in windows 7 and have opened the command prompt as Administrator.
Code:
C:\adb>fastboot -i 0x0B05 flash staging twrp-2.7.1.1-tf700t.blob
sending 'staging' (6894 KB)...
OKAY [ 0.869s]
writing 'staging'...
OKAY [ 0.084s]
finished. total time: 0.955s
Is there any way I get get logs from the tablet itself?

I had been thinking was this a permissions thing although I am able to run
Code:
fastboot boot
Code:
fastboot boot-bootloader
and they work correctly. So I do have access but for some reason the partition is not getting flashed correctly.
Does anyone know what the partitions are used for?
I assume the system partition is used for the actual system image but what is the staging partition used for?

knoxor said:
I had been thinking was this a permissions thing although I am able to run
Code:
fastboot boot
Code:
fastboot boot-bootloader
and they work correctly. So I do have access but for some reason the partition is not getting flashed correctly.
Does anyone know what the partitions are used for?
I assume the system partition is used for the actual system image but what is the staging partition used for?
Click to expand...
Click to collapse
When blobs are written to the staging partition, on next boot. the bootloader flashes the contents to the relevant partitions (i.e., kernel, system, bootloader)

knoxor said:
Hi,
Thanks for the reply.
I tried as you suggested and looks like the same results. I'm doing this in windows 7 and have opened the command prompt as Administrator.
Code:
C:\adb>fastboot -i 0x0B05 flash staging twrp-2.7.1.1-tf700t.blob
sending 'staging' (6894 KB)...
OKAY [ 0.869s]
writing 'staging'...
OKAY [ 0.084s]
finished. total time: 0.955s
Is there any way I get get logs from the tablet itself?
Click to expand...
Click to collapse
Hi sbdags,
So it looks like I'm stuck at this point. The above command seems to work but the time for flashing the recovery blob to staging seems very short which probably indicates that this has not happened correctly. After the above command, on next boot when selecting RCK from the bootloader menu the tablet attempts to perform the update but then I get the android error screen (android dude on his back and error message).
Any suggestions as to what I can do next?
thanks
Paul

knoxor said:
Hi sbdags,
So it looks like I'm stuck at this point. The above command seems to work but the time for flashing the recovery blob to staging seems very short which probably indicates that this has not happened correctly. After the above command, on next boot when selecting RCK from the bootloader menu the tablet attempts to perform the update but then I get the android error screen (android dude on his back and error message).
Any suggestions as to what I can do next?
thanks
Paul
Click to expand...
Click to collapse
Well shoot me a PM, Lets see if we can find a solution to your issue ...
Thx Josh

bump again.
Is there anyone there who can help me on this please ?

knoxor said:
Is there anyone there who can help me on this please ?
Click to expand...
Click to collapse
I don't think I can help you, but can you post the build number of your bootloader? I remember someone had a bootloader for the TF300 on his TF700 and was then unable to flash blobs.

_that said:
I don't think I can help you, but can you post the build number of your bootloader? I remember someone had a bootloader for the TF300 on his TF700 and was then unable to flash blobs.
Click to expand...
Click to collapse
Hi, I fairly sure I have the correct bootloader (WW_epad-10.6.1.14.10-20130801 A03).
Just to clarify, this is a stock rom I have on the tab. I have it unlocked but not rooted.
thanks

knoxor said:
Hi, I fairly sure I have the correct bootloader (WW_epad-10.6.1.14.10-20130801 A03).
Just to clarify, this is a stock rom I have on the tab. I have it unlocked but not rooted.
thanks
Click to expand...
Click to collapse
Your bootloader is ok.
Did you PM Josh? What did you guys try?
If he couldn't help you, I doubt I can...
Aside from the suggestions I gave you on the Transformer Forum, I'm stumped...
So again:
Do not use USB 3.0 ports
Uninstall the fastboot drivers and use the one from here: http://forum.xda-developers.com/showthread.php?t=2646279
Check the fastboot.exe version and see if you can find a later one.
That's all I can think of right now....

berndblb said:
Your bootloader is ok.
Did you PM Josh? What did you guys try?
If he couldn't help you, I doubt I can...
Aside from the suggestions I gave you on the Transformer Forum, I'm stumped...
So again:
Do not use USB 3.0 ports
Uninstall the fastboot drivers and use the one from here: http://forum.xda-developers.com/showthread.php?t=2646279
Check the fastboot.exe version and see if you can find a later one.
That's all I can think of right now....
Click to expand...
Click to collapse
Yes I contacted Josh and shared my desktop with him one evening. We didn't resolve it. I've tried the flashing on 3 different computers.
One of them is an old laptop running ubuntu that I know only has USB2 ports on it.
The only thing I can think of is that I lost my original charger/cable but I spent the extra money to get an OEM one again so I hope that is not
the issue.
Could the cable be the issue??

knoxor said:
Yes I contacted Josh and shared my desktop with him one evening. We didn't resolve it. I've tried the flashing on 3 different computers.
One of them is an old laptop running ubuntu that I know only has USB2 ports on it.
The only thing I can think of is that I lost my original charger/cable but I spent the extra money to get an OEM one again so I hope that is not
the issue.
Could the cable be the issue??
Click to expand...
Click to collapse
If you got the charger from anywhere else but Asus - yes, that could be the issue. And the only one left I can think of....