Database Info

[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] Can't fastboot / No recovery JB

I have an interesting problem:
I have a tf300t curently running JRO03C.ww_epad-10.4.2.17-20121018
I ended up here after an unsuccessful flash with twrp. Tried to recover my back up with no joy. At this time it would only boot twrp recovery, finally flashed stock via micro sdcard and got it to boot again! Only I had no root anymore, so I tried to boot into recovery and there was none. So next I tried to boot into bootloader and when I select fastboot, the tablet says starting "starting fastboot download protocol" but after nothing else happens. ADB looses it, and it just stops right there.
The good news is that I can still use the tablet, it boots and everything works fine but I have no root. I have searched and read and searched and read. I don't know if the reflash flashes the bootloader but that didn't seam to have any effect. If anybody could point me in the right direction I would sure appriciate the help.

there is a way on the TWRP instructions using terminal when you are in system

nitsuj79 said:
I have an interesting problem:
I have a tf300t curently running JRO03C.ww_epad-10.4.2.17-20121018
I ended up here after an unsuccessful flash with twrp. Tried to recover my back up with no joy. At this time it would only boot twrp recovery, finally flashed stock via micro sdcard and got it to boot again! Only I had no root anymore, so I tried to boot into recovery and there was none. So next I tried to boot into bootloader and when I select fastboot, the tablet says starting "starting fastboot download protocol" but after nothing else happens. ADB looses it, and it just stops right there.
The good news is that I can still use the tablet, it boots and everything works fine but I have no root. I have searched and read and searched and read. I don't know if the reflash flashes the bootloader but that didn't seam to have any effect. If anybody could point me in the right direction I would sure appriciate the help.
Click to expand...
Click to collapse
I saw on another site that with this tablet it will go into fastboot but wont popup as fastboot device on your computer, but you can still use fastboot commands. worked for me

mikaole said:
there is a way on the TWRP instructions using terminal when you are in system
Click to expand...
Click to collapse
You must have root permission for that method

imp3r10 said:
I saw on another site that with this tablet it will go into fastboot but wont popup as fastboot device on your computer, but you can still use fastboot commands. worked for me
Click to expand...
Click to collapse
No when I try to flash recovery it says waiting for device and nothing ever happens.

I seamed to have got it. I down graded to 10.4.2.9 and back to 13. plugged it to the computer and this time it installed drivers and that time I was able to flash recovery. I don't know what happened and it was probably something that I was doing wrong. But just incase that is what did the trick and it helps someone else, i wanted to be sure and follow up.

Ploblem with bootloader

Hi guys, i have a question:
wiht FW 4.2.1 if i reboot on bootloader screen, and in the top left of the screen, you will see a sign that says: Key drive not found .... why?
could you help me?

stevtec86 said:
Hi guys, i have a question:
wiht FW 4.2.1 if i reboot on bootloader screen, and in the top left of the screen, you will see a sign that says: Key drive not found .... why?
could you help me?
Click to expand...
Click to collapse
Same here & a few other people I have asked also have this.
Not sure but I think everyone on 4.2.1 bootloader now has this "Key driver not found...Booting os..." message in the top left corner of bootloader.
I don't know what it means though.

Not only do I have this, but no computer I have will fastboot anything to the tablet it just sits there after I do the flash command to flash twrp for as long as I let it sit and never completes.. Also by trying to boot into recovery I get the fallen down android with the red !.
It will boot into Android just fine, I just now have no recovery. The device is unlocked because it tells me it is unlocked when I boot it, but I can't flashboot anything and it has that key driver not found thing on it also. Not sure why my recovery isn't there since the only thing I have ever done to it was unlock using the V8 tool since I am on 4.2.1 and then try to flash the right 2.4.4.0 patched version of TWRP. If it isn't seeing my device I can't see how it would have wiped my recovery.
Seen several people with my issue and have even asked a question but so far no one has responded.
Edit: I still have that error on the bootloader but I finally got TWRP to flash after going to a 3rd computer and using a USB 3.0 port. Don't know the significance of the 3.0 port but it worked so I am not asking questions.

slickdaddy96 said:
Not only do I have this, but no computer I have will fastboot anything to the tablet it just sits there after I do the flash command to flash twrp for as long as I let it sit and never completes.. Also by trying to boot into recovery I get the fallen down android with the red !.
It will boot into Android just fine, I just now have no recovery. The device is unlocked because it tells me it is unlocked when I boot it, but I can't flashboot anything and it has that key driver not found thing on it also. Not sure why my recovery isn't there since the only thing I have ever done to it was unlock using the V8 tool since I am on 4.2.1 and then try to flash the right 2.4.4.0 patched version of TWRP. If it isn't seeing my device I can't see how it would have wiped my recovery.
Seen several people with my issue and have even asked a question but so far no one has responded.
Edit: I still have that error on the bootloader but I finally got TWRP to flash after going to a 3rd computer and using a USB 3.0 port. Don't know the significance of the 3.0 port but it worked so I am not asking questions.
Click to expand...
Click to collapse
Adndroid with a red ! means you have the stock recovery. Not sure why you can't use fastboot. I'd check all your drivers on your PC first as that is the most like cause. Start by uninstalling and reinstalling the Android SDK.

sbdags said:
Adndroid with a red ! means you have the stock recovery. Not sure why you can't use fastboot. I'd check all your drivers on your PC first as that is the most like cause. Start by uninstalling and reinstalling the Android SDK.
Click to expand...
Click to collapse
I got it to work. Weirdly It took 3 different computers before I got fastboot to recognize the tablet and allow me to flash the recovery. I was worried, but if you say the red ! means I still had a recovery then obviously it was just a communication issue with my device. The problem is now that only one of my three computers likes to communicate via fastboot and all three had the appropriate USB drivers installed. I am going to have to blame it on Windows most likely overriding and installing a wrong driver possibly.
I got TWRP and root. Debating on which ROM to flash now CROMi or Energy.
I still get that key driver missing at the top in the bootloader menu but obviously it isn't hurting anything and fastboot still works.

[Q] TWRP 2.4.4.0-JB killed my Tablet?

I found multiple development threads that are close to this, but here's the deal...
I took Asus 4.2.1 OTA update and used that for a while.
The device was already unlocked and I decided to try TWRP 2.4.4.0 for recovery before trying any custom ROMs
I followed the big bold red instructions that said:
If you have taken the official Asus Jellybean OTA then be sure to install the '-JB' version of the recovery for your device - and only flash roms that are based on the Asus OTA.
I downloaded the -JB version (at that time, -ICS was the only other choice), and installed it via fastboot.
Upon rebooting, it will only boot into recovery and TWRP can't see any partitions. More importantly, I've spent almost a month now reading the threads that are related to this trying various suggestions in trying to break out of this, and during this time, I've realized that I can't flash anything. ADB works, but the devices says "123456789ABCDEF recovery". I can run "adb reboot bootloader" and I will get my 3-icon 4.2.1 bootloader screen with a blinking green square on RCK. Fastboot devices shows my S/N, and it acts like it is flashing (tried flashing the -4.2 version of TWRP 2.4.4.0 and a new copy of the JB 4.2.1 OTA ROM), but all the tablet does is lock-up. The green square stops blinking and, even though fastboot says it's working, the tablet is no longer responding and requires a reset to reboot, upon which it boots right back into TWRP.
I'm just asking if there is a way out of this yet that doesn't involve replacing the main logic board.
I suppose what bothers me more, is that Teamwin's website for TWRP still has the same instructions in big bold red letters, without acknowledging that there are TWO official Asus Jellybean OTA releases. One will work just fine with the -JB version they specify to download, the other will do what mine did. Anyone current with Asus releases is gonna follow these instructions and brick their pads unless they already know about the -4.2 version of TWRP.

Yo!
Have you tried flashing asus stock 4.2.1 system blob using adb?

Do you know what the command for that would be? I have the same problem. But I don't wanna flash it to the wrong partition.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

klownin5643 said:
Do you know what the command for that would be? I have the same problem. But I don't wanna flash it to the wrong partition.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
This is the link to the instructions i followed. http://forum.xda-developers.com/showthread.php?t=2187982
Here is the main point.
- Method 2: Update using fastboot
Notes:
You will keep all your data
This is the best method to update your tablet if you want to keep all your data, and the safest one
Ensure you have the correct drivers for the tablet installed on your computer, or you will have a "waiting for device" error
To update using fastboot, follow this steps:
If you don't have fastboot yet, download it from here an unpack it somewhere on your computer
Extract the Asus firmware file and put the blob file inside fastboot folder
Open a command line on fastboot folder (write "cmd" on Windows search bar at the Start menu, and then
Code:
cd "FOLDER WHERE YOU EXTRACTED FASTBOOT"
, or you can just use SHIFT + RIGHT CLICK on the folder and select "Open command line window here" or something like that)
Reboot the tablet holding the volume down key until you see some icons. Use the volume down key to select the USB icon and then volume up to select it
Connect the tablet to the computer if you didn't do so
Write
Code:
fastboot -i 0x0B05 flash system blob
, hit enter and wait until it completes
Write this to reboot your tablet:
Code:
fastboot reboot
or hold the power button for 10 seconds if the code doesn't work
You are now updated to Android 4.2

There are 3 things keeping this from working:
1) fastboot -i 0x0B05 flash system blob
This locks the tablet up. Fastboot thinks it's still working, but the blinking RCK has stopped blinking and...
2) fastboot reboot
... doesn't work because the tablet has locked up from the flash attempt. You have to...
3) hold the power button for 10 seconds if the code doesn't work
Which does reboot the tablet, but it goes right back into TWRP, and you have NOT been updated to anything.
Now, in my particular case, I can get it to "adb reboot bootloader" and tell it to cold boot Linux to get into my OS, but that never happens either. It's likely been wiped from one of my multiple attempts at trying others' suggestions for getting out of this.

I'm sorry, you bricked your tablet permantly... Only Asus can fix it now... You flashed a wrong recovery for your tablet... You read the wrong post! That one is for Android 4.1 and not 4.2...

joelalmeidaptg said:
I'm sorry, you bricked your tablet permantly... Only Asus can fix it now... You flashed a wrong recovery for your tablet... You read the wrong post! That one is for Android 4.1 and not 4.2...
Click to expand...
Click to collapse
I did the same thing as the OP. I'm not new at this, I've rooted and run custom ROMs for years on dozens of devices. I always do lots of research before starting the process. What the OP and I are saying is that the Team Win site doesn't state anything about the 421 patch and if you look at the file list, the patch only exists in the 2.4.4.0 version. With those two things in mind, a reasonable person would conclude that 2.5.5.0 is patched for both...as long as you use the -JB version. Obviously wrong as I now know, but certainly not clearly wrong before bricking the device.
I would never assume to blame the Dev's, but I (we) are asking that they be a bit more blatant with the fact JB v4.2 MUST USE TWRP version 2.4.4.0-4.2 and not anything else.
Now, for good or bad, so many people have now bricked their TF300's that there are many threads like this one. Any research at this point will reveal this issue. Still, Team Win should post the warning.

joelalmeidaptg said:
I'm sorry, you bricked your tablet permantly... Only Asus can fix it now... You flashed a wrong recovery for your tablet... You read the wrong post! That one is for Android 4.1 and not 4.2...
Click to expand...
Click to collapse
I wish it was as simple as reading the wrong post... When I downloaded TWRP 2.4.4.0, there were only -ICS and -JB files listed (much like TWRP 2.5.0.0 is now)... Wouldn't you have picked -JB?
Even now, Teamwin's directions tell you that, if you took the Asus JB OTA, that you need the -JB version. They don't differentiate WHICH JB OTA, and they don't mention that a -4.2 version specifically for the 4.2.1 OTA exists. Never mind mentioning that using the -JB version on the latest Asus JB OTA update will BRICK THE TABLET.
There are 192 people that have downloaded the 2.5.0.0-JB blob file as of now. How many of these folks do you suppose have taken the Asus 4.2.1 OTA update and are about to permabrick their tablets?

It sickens me to know of the 192, likely most are on 4.2.1. I only hope they catch it before pushing the ROM.

When you flash recovery its flash ix505blah recovery recovery.blob is it flash ix5o5blah system system.blob? If that makes sense? Or no.?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

The two things here centers around the fact that TWRP is the only thing that will boot, other than the bootloader (but you have to boot TWRP first).
1) If you are in TWRP, there are no partitions mounted. In fact, there are no mmcblk devices at all, which is why there are no partitions mounted. As a result, there is nothing to flash to from here (even if fastboot worked). Adb works from here, but the device serial says "123456789ABCDEF recovery". Fastboot detects no devices at all from here.
2) If you reboot bootloader from adb, you can get access to fastboot. However, any flashing from here locks up the tablet, even though the command looks like it's running and completing the first time. Adb does NOT work from here, sees no devices. Fastboot looks like it sees the right device until you try to flash something with it. Once you try to flash anything, no fastboot command completes, furthering the notion that the tablet is frozen. A reset reboots the tablet back into TWRP, and nothing has changed. Repeat the cycle ad nauseum.
Basically, you can't do squat from TWRP, and fastboot flash from the bootloader locks up the tablet so you can't flash anything. I'm pretty sure it will take a logic board replacement to fix it at this point unless someone comes up with something better.

I'm having the exact same issue as you... I had flashed the TWRP JB blob and it couldn't recognize anything so I tried to flash CWM. Now...My fastboot doesn't do a thing since the blue progress bar doesn't show up and just freezes when trying to flash the stock firmware. I don't think I can send it to Asus for warranty either since my device is unlocked.

Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.

splashg said:
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
Click to expand...
Click to collapse
You can't flash a recovery? And what about the stock Rom?
Sent from my WT19i using xda app-developers app

splashg said:
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
Click to expand...
Click to collapse
Lol did that too...I don't know if there is anything left to try. Did you try putting stock rom on an external SD card and running RCK?

Ok...so now that I won one, there is a guy on e-bay that has a bunch of TF300T-b1-bl 32gb Transformers with broken screens. He is posting pictures and they all appear (based on the picture) that they have operable firmware. Mine will be here late in the week...I'll pull the main board and put it in mine. I'll let you know how it goes.

splashg said:
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
Click to expand...
Click to collapse
I did the same thing and got the same result. This i very interesting because the
Code:
fastboot -i 0x0b05 flash <partition> <filename>
command which tries to write/edit something on the partition fails (maybe is due to some encryption introduced in 421) but the
Code:
fastboot -i 0x0b05 erase <partition>
which also does the write/edit, succeeds. What I'm trying to say is that either both should fail or succeed because both are trying to do some editing to the storage.

steveb05 said:
Ok...so now that I won one, there is a guy on e-bay that has a bunch of TF300T-b1-bl 32gb Transformers with broken screens. He is posting pictures and they all appear (based on the picture) that they have operable firmware. Mine will be here late in the week...I'll pull the main board and put it in mine. I'll let you know how it goes.
Click to expand...
Click to collapse
Yeah, if it's the ones I've seen the hard part there is that they go for more than a replacement logic board does. Sure, there's likely some other parts still good in there, but if it just has a bad digi, I'm too apt to fix the digi... Basically, I need one where both the digi and the LCD are shot, and goes for less than the logic board does.
Joel, yeah, we can't flash anything. Fastboot flash <any partition> <any file> locks the tablet up. As Vahid alludes to, this is very odd because we have no trouble with fastboot erase. Having a stock image on an SD card and trying to get RCK to reload it doesn't work, presumably because it can't mount the external SD card.

splashg said:
Yeah, if it's the ones I've seen the hard part there is that they go for more than a replacement logic board does. Sure, there's likely some other parts still good in there, but if it just has a bad digi, I'm too apt to fix the digi... Basically, I need one where both the digi and the LCD are shot, and goes for less than the logic board does.
Joel, yeah, we can't flash anything. Fastboot flash <any partition> <any file> locks the tablet up. As Vahid alludes to, this is very odd because we have no trouble with fastboot erase. Having a stock image on an SD card and trying to get RCK to reload it doesn't work, presumably because it can't mount the external SD card.
Click to expand...
Click to collapse
Just got my TF300 back for Asus service center. They said that they had to replace the motherboard @ a cost of $186.00 total, parts and labor. Told them to just send it back. I'll buy a Nexus 7 instead for the same price almost.

Got my broken TF300 ebay win today. Digitizer and LCD were toast. But, the main board went right in to my bricked TF300. I'm unlocked, rooted, and running 4.1.1 and life is good!
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Hard Bricked pixel 3

SO... I did a dumb thing... my friend asked me to install android Q beta on her phone, so I did a sideload.... never checking if it was a verizon phone first... the sideload never errored looked like all was good until the reboot.... operating system corrupt warning... boot to recovery same message... only fastboot with a locked verizon boot loader... did some research looks like I need a firehose... yep.. cant find one... any suggestions or perhaps someone able to help me out?

Did you already try to flash the factory image?
Can be found here: developer.android.com/preview/download#flash (sorry, I cannot post links yet)
First try to flash it without the "-w" flag. If it still does not start, try it with the "-w" flag, but that will delete all data on the phone.
// EDIT if that does not work you might want to head over to the Pixel 3 XL guys here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849/page10

I can not flash anything in fastboot due to locked bootloader it always says not permitted. booting recovery or OS always says corrupted with the triangle, recovery does NOT show the android guy, just a warning message. fastboot and qualcomm EDL is all I have available.

LSDemon said:
I can not flash anything in fastboot due to locked bootloader it always says not permitted. booting recovery or OS always says corrupted with the triangle, recovery does NOT show the android guy, just a warning message. fastboot and qualcomm EDL is all I have available.
Click to expand...
Click to collapse
If you are sure that you can't get into recovery I'd suggest getting an RMA for your friend who has been without the device for 4 or 5 days.