Database Info

unlocked bootloader + manual .30 update fail

Title says it all.
Bootloader is unlocked but i try to manually update the .30 firmware (im on .29) ... and i get the poor little droid on his side with a red exclamation mark... why?

BossJ said:
Title says it all.
Bootloader is unlocked but i try to manually update the .30 firmware (im on .29) ... and i get the poor little droid on his side with a red exclamation mark... why?
Click to expand...
Click to collapse
do you have cwm or twrp installed?
if not, you will need to install one of them.
once you do that, you will need to download and unzip the .30 firmware once and make sure it is on your sd card. then you can reboot into recovery and flash the .30 zip.
if you do that, you will then need to reinstall custom recovery again. check out the development section.

BossJ said:
Title says it all.
Bootloader is unlocked but i try to manually update the .30 firmware (im on .29) ... and i get the poor little droid on his side with a red exclamation mark... why?
Click to expand...
Click to collapse
You might want to try this if you are on Windows (credit to: Auliyaa for providing the original guide. Link to original guide after this suggestion):
1. Download the latest Firmware from ASUS support website, which you obviously have done.
2. Download and install Android SDK to your PC. Install the SDK to your C:\ drive or wherever you have your Windows installed. When you launched it, choose to only download the Platform Tools to make sure you have the updated Fastboot.
3. Once the platform tools download finished, close the Android SDK.
4. Extract "blob" file from the Firmware zip file to Android SDK platform-tools directory.
5. Open Command prompt, if you are on Windows
6. Navigate to platform-tools directory
7. Type this in command prompt:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
8. For some reason, the transfer seems to fail from time to time. Just try the Fastboot command again if the transfer fail. For me, the 2nd attempt is always successful.
9. Once the transferred is successful, type the following command to reboot your tablet:
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
Link Reference: [TF300TG][Guide] Flashing back the original stock ROM
Hope this helps.

Manual JB update. Soft-bricked my TF300T?

Hi ppl!
First, my device failed to get the OTA Update because I deleted some system apps (see my original post).
Then I found this post where another user restored original APKs in /system/apps and managed to manually update to JB by downloading the dlpkgfile in this post.
So I proceed, restored my /system/apps (with 755 permissions), rooted with OTA RootKeeper and SuperSU, placed the dlpkgfile and command files, restarted to fastboot (Power+Vol Down) and entered Recovery mode.
The green android with the blue progress bar went for over 10 minutes, then ... the android with the RED TRIANGLE appeared
After a minute or so the device restarted, an ASUS logo with a blue progress bar ran, but then it got stuck in the ASUS logo.
I'm still able to restart to fastboot (Power+Vol Down), where a message appears:
Code:
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.4.2.9-20120809" A03
, and where I have 4 choices:
1. RCK: Recovery mode, when I select this the Red Triangle appears again.
2. Android: Normal android boot, gets freeze right away
3. Fastboot USB download protocol: Tried using ADB, but don't really know what it is. Here's an image of how the device appear in my Windows PC
4. Wipe Data: Already done this, seems to wipe user data, but still gets stuck on ASUS logo
Some pictures I took of my device: http://imgur.com/I13ou http://imgur.com/Jezpn
I also tried downloading .30 firmware from ASUS website and placing the Zip contents in my SD card, then booting recovery but no luck.
It's pretty awful that everything went so bad, I'm hoping there is a solution.
Anything would be really appreciated!!!
Thanks!

benoror said:
Hi ppl!
First, my device failed to get the OTA Update because I deleted some system apps (see my original post).
Then I found this post where another user restored original APKs in /system/apps and managed to manually update to JB by downloading the dlpkgfile in this post.
So I proceed, restored my /system/apps (with 755 permissions), rooted with OTA RootKeeper and SuperSU, placed the dlpkgfile and command files, restarted to fastboot (Power+Vol Down) and entered Recovery mode.
The green android with the blue progress bar went for over 10 minutes, then ... the android with the RED TRIANGLE appeared
After a minute or so the device restarted, an ASUS logo with a blue progress bar ran, but then it got stuck in the ASUS logo.
I'm still able to restart to fastboot (Power+Vol Down), where a message appears:
Code:
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.4.2.9-20120809" A03
, and where I have 4 choices:
1. RCK: Recovery mode, when I select this the Red Triangle appears again.
2. Android: Normal android boot, gets freeze right away
3. Fastboot USB download protocol: Tried using ADB, but don't really know what it is. Here's an image of how the device appear in my Windows PC
4. Wipe Data: Already done this, seems to wipe user data, but still gets stuck on ASUS logo
Some pictures I took of my device: http://imgur.com/I13ou http://imgur.com/Jezpn
I also tried downloading .30 firmware from ASUS website and placing the Zip contents in my SD card, then booting recovery but no luck.
It's pretty awful that everything went so bad, I'm hoping there is a solution.
Anything would be really appreciated!!!
Thanks!
Click to expand...
Click to collapse
You don't have a recovery to boot into
Sent from my SGH-T989 using xda app-developers app

OK, I found this tutorial about flashing ASUS firmware with fastboot: http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
The problem is that the following commands:
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system US_epad-user-9.4.3.30.zip
both produce the error: "Signature mismatch"
I guess it's becaus my fastboot is newer version, since it was actually installed during the JB update, but I'm trying to flash a older .30 firmware.
I gues I will have to wait ASUS releases the new firmware for manual flashing it.
Just guessing...

benoror said:
OK, I found this tutorial about flashing ASUS firmware with fastboot: http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
The problem is that the following commands:
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system US_epad-user-9.4.3.30.zip
both produce the error: "Signature mismatch"
I guess it's becaus my fastboot is newer version, since it was actually installed during the JB update, but I'm trying to flash a older .30 firmware.
I gues I will have to wait ASUS releases the new firmware for manual flashing it.
Just guessing...
Click to expand...
Click to collapse
Thank you for posting this. I wanted to try something like this with the new boot loader that came with jb but it appears flashing the older firmware will not work.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

funnel71 said:
Thank you for posting this. I wanted to try something like this with the new boot loader that came with jb but it appears flashing the older firmware will not work.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
You're welcome. So, do you have a clue on how to restore my older bootloader soy I can get back to .30 stock?

benoror said:
You're welcome. So, do you have a clue on how to restore my older bootloader soy I can get back to .30 stock?
Click to expand...
Click to collapse
That is exactly what I'm wanting to know if it's even possible. If I can safely downgrade, I can re-root, but I'm limited on what I can do with a locked bootloader.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

peopole!!! new firmware is out!!!
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF300T/US_epaduser_10_4_2_9_UpdateLauncher.zip
here is a direct download link!!! US version only!!!
PS: im pushing using
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
[blob extracted from the above zip]
okay asus animated boot is up and i seem to successfully unbrick my device!!!!
Screens http://imgur.com/a/D7wqI

kindrudekid said:
peopole!!! new firmware is out!!!
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF300T/US_epaduser_10_4_2_9_UpdateLauncher.zip
here is a direct download link!!! US version only!!!
PS: im pushing using
[blob extracted from the above zip]
okay asus animated boot is up and i seem to successfully unbrick my device!!!!
Screens http://imgur.com/a/D7wqI
Click to expand...
Click to collapse
I don't know you mate..
But I'm so happy for you!! Glad everything worked out well! Cheers!!

Same Here!!!
Flashing the new ASUS firmware unbricked my device!!!!
Please mark this topic as SOLVED
ASUS should really make this process easier.
Thanks for all the support!
Greetings.

soft bricked?
I dont see how this is solved......I have seen some people comment they have no fastboot or recovery,
I tried to do manual update in cwm and when I rebooted with adb all I have is asus boot logo, it also does not say I have an unlocked bootloader,
I have no fastboot no recovery no adb connect all I have is asus boot logo.......volume+-power does nothing vol down + power also does nothing.
how do you flash new firmware without adb or any type of recovery?

uelabs said:
I dont see how this is solved......I have seen some people comment they have no fastboot or recovery,
I tried to do manual update in cwm and when I rebooted with adb all I have is asus boot logo, it also does not say I have an unlocked bootloader,
I have no fastboot no recovery no adb connect all I have is asus boot logo.......volume+-power does nothing vol down + power also does nothing.
how do you flash new firmware without adb or any type of recovery?
Click to expand...
Click to collapse
I have the same problem!!
please need help on this!!

AFAIK you should still have access to fastboot, I'm newbie and never messed up by unlocking the bootloader

It worked!
Thank you so much! I had this same problem with mine and couldn't find an answer anywhere until I found your post.

hmm, I lost my tablet for nearly a month then updated CM10 when prompted having connected to my new wireless. This of course (since the Oct update) put the ROM out of kilter with the bootloader. I didn't have an old ROM on the SDCARD, and old CWM so I couldn't mount an external to get a rom on. I tried pushing a rom to the SD with adb but the drivers weren't going in right and I just couldn't get any joy. I followed this thread to fastboot the current stock JB on in the hope that it would give me a fresh start but it's hanging now at the second (glossy) ASUS logo. I really don't know where to go from here. Is it possible there was a problem with the write?

erasing the memory from the boot menu worked!

biscuits said:
erasing the memory from the boot menu worked!
Click to expand...
Click to collapse
Can you tell me how you erased memory from boot menu - or maybe i understand this in different way.
I have only bootloop and it boots to CWM where i cannot mount any SD card - not internal not external.
Also Vol down + power doesnt work - there is no option to enter fastboot mode....device just bootloops and then enters CWM...
Tried to push through adb but there is no SD card to copy files. Tried different methods but cannot mount any storage...
Thanks JB update

kindrudekid said:
peopole!!! new firmware is out!!!
here is a direct download link!!! US version only!!!
PS: im pushing using
[blob extracted from the above zip]
okay asus animated boot is up and i seem to successfully unbrick my device!!!!
My fastboot is working but it seems that i cannot write anything on my internal sd card.. When i run fastboot -i 0x0B05 flash system blob
My PC shows no erros - it does all the steps. But my tablet freezes and that it - it never unfreezes, i need to power it off.
But fastboot and abd commands work - like reboot or boot into bootloader.
Click to expand...
Click to collapse

cwm issue ota 10.6.1.8 jb 4.2.1

Attempting to root, to backup then to install cm 10.1 or other rom
I've installed cwm from this thread http://forum.xda-developers.com/showthread.php?t=1668173
I can boot into recovery ok, however I get the following errors:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't mount /cache/recovery/last_log
can't mount /cache/recovery/.
when trying to access internal or external sd card get:
can't mount /sdcare/
can't mount /emmc
Any help appreciated
Update: tried twrp 2.4.3.0 does the same thing

The new update has encryption by default. That's why you can't mount anything. I am not sure if team win will release an update for their recovery or if Asus needs to do it. Seems like this update really screwed over some people.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

elesbb said:
The new update has encryption by default. That's why you can't mount anything. I am not sure if team win will release an update for their recovery or if Asus needs to do it. Seems like this update really screwed over some people.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
wow not good news. Guess I'l just have to monitor sites and see what happens over time.
Disappointing for sure as this last update screwed up the hdmi out, I have functional tablet it might as well be a bricked pos, arg !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
It's worthless to me in it's present state
Hmm where is the phone num so i can call gripe at asus

tonyjsan said:
wow not good news. Guess I'l just have to monitor sites and see what happens over time.
Disappointing for sure as this last update screwed up the hdmi out, I have functional tablet it might as well be a bricked pos, arg !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
It's worthless to me in it's present state
Hmm where is the phone num so i can call gripe at asus
Click to expand...
Click to collapse
Think you can only email them :/
I dont think its asus who encrypted it. I think it was google. I am not sure though so dont quote me xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

elesbb said:
Think you can only email them :/
I dont think its asus who encrypted it. I think it was google. I am not sure though so dont quote me xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
twrp I think might support that sort of thing already, i went back into twrp2 and it does ask for a password at first, a check of the logs by twrp said can't decrypt
Who ever set the encryption, needs to show how to unset it.

I'm having the same issue that tonyjsan described.
This was I did:
1 - I updated to 4.2.1 via OTA.
2 - Download Asus unlock apk & unlocked the boot loader.
3 - Then installed the CWM 6.0.2.3 via fast boot.
4 - Tried to installed CM10.1 nightly couldn't acess SD started to get the following:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't mount /cache/recovery/last_log
can't mount /cache/recovery/.
when trying to access internal or external sd card get:
can't mount /sdcare/
can't mount /emmc/
Now it's the point where I got stupid, and decided to go into the bootloader and do a full wipe, which I THINK wiped everything and installed the recovery Kernel (which now is CWM) into the main image.
Now my TF300T only boot to CWM and I can acess it via ADB do thing like push files, but i've lost the boot loader and cannot go into fastboot.
Really need the expertise of a guru right now
Help is appreciated

Getting Same Issues
Both the latest TWRP2 and latest CWM are a bust for me too.
If the recovery kernel image can't get at the disk partitions - then no custom ROMS
can be installed.
I guess being the first non-nexus with 4.2.1 isn't such great news after all.

xbill9 said:
If the recovery kernel image can't get at the disk partitions - then no custom ROMS
can be installed.
Click to expand...
Click to collapse
Starting to get the felling I have a 300$ dollar brick on my desk

Same Here
I've run into the same thing. I did the OTA update to 4.2.1, and then I decided to root, so I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2041627.
Unlocked worked.
Recovery Flash worked.
Mounting any part of the sdcard (internal or external) does not work in recovery.
I can still boot into the OS, so I'm not bricked, but I can't install root because I can't see the internal storage to flash it.
Is it possible to flash back to 4.1.1?

Yes, but your recovery must be working.

vconceicao said:
I'm having the same issue that tonyjsan described.
This was I did:
1 - I updated to 4.2.1 via OTA.
2 - Download Asus unlock apk & unlocked the boot loader.
3 - Then installed the CWM 6.0.2.3 via fast boot.
4 - Tried to installed CM10.1 nightly couldn't acess SD started to get the following:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't mount /cache/recovery/last_log
can't mount /cache/recovery/.
when trying to access internal or external sd card get:
can't mount /sdcare/
can't mount /emmc/
Now it's the point where I got stupid, and decided to go into the bootloader and do a full wipe, which I THINK wiped everything and installed the recovery Kernel (which now is CWM) into the main image.
Now my TF300T only boot to CWM and I can acess it via ADB do thing like push files, but i've lost the boot loader and cannot go into fastboot.
Really need the expertise of a guru right now
Help is appreciated
Click to expand...
Click to collapse
vconceicao said:
Starting to get the felling I have a 300$ dollar brick on my desk
Click to expand...
Click to collapse
as sad as it seems :'( you are more than likely bricked. Every thread I read, even on 4.1 stock, once you do the "wipe all" option in bootloader menu, without a stock recovery. You become bricked.
wirikidor said:
I've run into the same thing. I did the OTA update to 4.2.1, and then I decided to root, so I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2041627.
Unlocked worked.
Recovery Flash worked.
Mounting any part of the sdcard (internal or external) does not work in recovery.
I can still boot into the OS, so I'm not bricked, but I can't install root because I can't see the internal storage to flash it.
Is it possible to flash back to 4.1.1?
Click to expand...
Click to collapse
You should be able to fastboot the stock Asus 4.1.1 .blob file.
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend

vconceicao said:
Now it's the point where I got stupid, and decided to go into the bootloader and do a full wipe, which I THINK wiped everything and installed the recovery Kernel (which now is CWM) into the main image.
Now my TF300T only boot to CWM and I can acess it via ADB do thing like push files, but i've lost the boot loader and cannot go into fastboot.
Really need the expertise of a guru right now
Help is appreciated
Click to expand...
Click to collapse
When you said wipe, you used the wipe data option, when sitting at the first menu (boot loader menu) after pressing power and vol down ?
One other thing I'd share here to is that the factory wipe, from within settings, for me does not work, it boots to twrp / recovery, when I exit all data still there. So was wondering which one you used ?
Is the encryption on the partitions from sbk nvflash crap (i'm thinking not ??) or just an encrypted ext4 partition ??

elesbb said:
You should be able to fastboot the stock Asus 4.1.1
Click to expand...
Click to collapse
If I drop back to 4.1.1 will I have the same problem with not being able to access cache, data etc. in twrp or cwm, will it be encrypted ?
I'm also wondering dropping back to 4.1.1 will the 4.2.1 multi-user stuff mess with the downgrade, appears to be using sym links to create separate directory for each user.

tonyjsan said:
If I drop back to 4.1.1 will I have the same problem with not being able to access cache, data etc. in twrp or cwm, will it be encrypted ?
I'm also wondering dropping back to 4.1.1 will the 4.2.1 multi-user stuff mess with the downgrade, appears to be using sym links to create separate directory for each user.
Click to expand...
Click to collapse
Hello I have 4.1.1 It is unlocked. I have flashed the CWM and when I boot into recovery I only see the sd card and will not let me rrot via the zip either. I get an error in CWM saying that root persmissions need to be fixed. I have tried to fix then not to fix. Still nothing.
Not sure if this is inline with what everyone else is seeing.
ASUS did push from .17 to .20 the other day.

This is a fishing trip. 4.2 is multi-user, for multi-user to work the tablet has to be encrypted or users could access each others space. I don't have 4.2 so I can't test. If multi-user is deactivated encryption is not necessary. If multi-user is turned off can you find a setting to unencrypt?
It seems I remember someone unencrypting with twrp or fastboot but it took three tries, multi-user would still need to be off. This is not a suggestion just my thoughts.
My version of fastboot does not list unencrypt as an option.

Holy cow I now have cm 10.1, root, and hdmi out problem fixed. After lots digging to be sure I did not screw the tablet up here is what I did.
1) Downgrade to US_10.4.2.20, using fastboot and blob from asus web site.
2) after rebooting I had the previous boot-loader screen (in which usb icon shows), I re-installed recovery twrp2.
3) I did not even bother to boot into 10.4.2.20, went straight to recovery and I had access to cache, data, sdcard etc...
4) adb pushed the cm 10.1 zip to the sdcard and the gapps zip as well.
5) flash cm 10.1 then gapps
6) reboot and all is well.
There is one word of caution, not sure what happen but do not use the usb port on the keyboard dock with cm 10.1, it zapped a usb jump drive and a 500 gb portable drive , still looking into if I can recovery the drive and what caused it.
I's so glad I'm on CM 10.1 tablet running faster just seems to perform better.

I have also had this issue and managed to come back from it.
In doing some testing of the new ota update 4.2.1 (10.6.1.8) I have found that this issue is a direct result of the new 4.2.1 bootloader, it will not work with any custom recovery. twrp will give password prompt and be unable to mount anything but possible system, same goes for cwm minus the password prompt.
After doing a full wipe from twrp and then flashing just the new 4.2.1 bootloader, I rebooted back into twrp and it's encrypted, can't mount anything.
This method will not work if you cannot flash from fastboot successfully. In fact if you have attempted any other way to fix it may not work.
After I rebooted twrp to find it was encrypted the first thing I did was to reboot into fastboot mode and did the following:
flashed the 4.2.1 stock recovery, I have uploaded to here
Copy the "stock.blob" file to your android-sdk\platform-tools folder.
Also download the "US_epaduser_10_4_2_20_UpdateLauncher.zip" from the Asus website and unzip,
In the unzipped folder you will then have another zip file "US_epad-user-10.4.2.20.zip" unzip this also and now in that unzipped folder you will have a "blob" file, copy this to your android-sdk\platform-tools folder.
Boot into fastboot and check your pc can see your device:
open a command prompt and cd to your platform-tools directory.
Code:
fastboot devices
This should return your device serial, if not then fastboot is not setup correctly.
Next:
Code:
fastboot -i 0x0b05 flash recovery stock.blob
fastboot -i 0x0b05 reboot
Boot back into fastboot:
Code:
fastboot -i 0x0b05 flash system blob
fastboot -i 0x0b05 reboot
The system blob will take some time 10min or so to flash, so just give it some time then issue the reboot command.
Also first reboot after system blob flash will take some time, you will see a progress bar under the Asus logo.
Once your tablet has fully loaded you can now boot back into fastboot and flash a custom recovery & flash custom rom again.
I do suggest skipping the 4.2.1 update for now until this issue has been fixed.
As I have said this may not work for everyone depending on if you have attempted any other commands via fastboot or adb.
This has worked for me twice now but try at own risk.

pjc21 said:
I have also had this issue and managed to come back from it.
In doing some testing of the new ota update 4.2.1 (10.6.1.8) I have found that this issue is a direct result of the new 4.2.1 bootloader, it will not work with any custom recovery. twrp will give password prompt and be unable to mount anything but possible system, same goes for cwm minus the password prompt.
After doing a full wipe from twrp and then flashing just the new 4.2.1 bootloader, I rebooted back into twrp and it's encrypted, can't mount anything.
This method will not work if you cannot flash from fastboot successfully. In fact if you have attempted any other way to fix it may not work.
After I rebooted twrp to find it was encrypted the first thing I did was to reboot into fastboot mode and did the following:
flashed the 4.2.1 stock recovery, I have uploaded to here
Copy the "stock.blob" file to your android-sdk\platform-tools folder.
Also download the "US_epaduser_10_4_2_20_UpdateLauncher.zip" from the Asus website and unzip,
In the unzipped folder you will then have another zip file "US_epad-user-10.4.2.20.zip" unzip this also and now in that unzipped folder you will have a "blob" file, copy this to your android-sdk\platform-tools folder.
Boot into fastboot and check your pc can see your device:
open a command prompt and cd to your platform-tools directory.
Code:
fastboot devices
This should return your device serial, if not then fastboot is not setup correctly.
Next:
Code:
fastboot -i 0x0b05 flash recovery stock.blob
fastboot -i 0x0b05 reboot
Boot back into fastboot:
Code:
fastboot -i 0x0b05 flash system blob
fastboot -i 0x0b05 reboot
The system blob will take some time 10min or so to flash, so just give it some time then issue the reboot command.
Also first reboot after system blob flash will take some time, you will see a progress bar under the Asus logo.
Once your tablet has fully loaded you can now boot back into fastboot and flash a custom recovery & flash custom rom again.
I do suggest skipping the 4.2.1 update for now until this issue has been fixed.
As I have said this may not work for everyone depending on if you have attempted any other commands via fastboot or adb.
This has worked for me twice now but try at own risk.
Click to expand...
Click to collapse
Question: You said you reflashed the stock bootloader. I had gotten my tf300 couple days ago but went through the ota update not thinking of issues if wanted to root so I'm not rooted totally stock on 4.2.1but if possible would like to flash back to stock locked bootloader if possible. After reading all the issues with trying to flash custom recovery and root after ota figured I'd just wait till some of the issues are figured out. I'm new to this device but have rooted many other android phones in the passed so not a total noob just learning about this one been reading alot. Just wondering if there were a way to do so for future updates as i read you lose ota capability if unlocked. Thanks
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

aerdely said:
Question: You said you reflashed the stock bootloader. I had gotten my tf300 couple days ago but went through the ota update not thinking of issues if wanted to root so I'm not rooted totally stock on 4.2.1but if possible would like to flash back to stock locked bootloader if possible. After reading all the issues with trying to flash custom recovery and root after ota figured I'd just wait till some of the issues are figured out. I'm new to this device but have rooted many other android phones in the passed so not a total noob just learning about this one been reading alot. Just wondering if there were a way to do so for future updates as i read you lose ota capability if unlocked. Thanks
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
This approach recovered the tablet.
As long as the bootloader is working - it is probably fixable.
Here is how I got it to work:
-preloaded my ROM and Gapps on the SD card
-flashed stock system blob (for the right region) from the ASUS website
-let the stock ROM reboot
-it hangs - but will be visible from ADB
-reboot to fastboot
-install TWRP or CWM from fastboot
-reboot recovery
-then flash ROM + Gapps
There has to be something in the new OTA bootloader or OTA system that
locks down the partitions.

xbill9 said:
This approach recovered the tablet.
As long as the bootloader is working - it is probably fixable.
Here is how I got it to work:
-preloaded my ROM and Gapps on the SD card
-flashed stock system blob (for the right region) from the ASUS website
-let the stock ROM reboot
-it hangs - but will be visible from ADB
-reboot to fastboot
-install TWRP or CWM from fastboot
-reboot recovery
-then flash ROM + Gapps
There has to be something in the new OTA bootloader or OTA system that
locks down the partitions.
Click to expand...
Click to collapse
Yea should of mentioned im not rooted haven't done that yet as if you are on the 4.2.1 ota you can't without issues. Device works fine I'm on stock recovery and firmware but just an unlocked bootloader and just little worried because some have mention can lose any future ota's if thats not the case than i guess no issue at all but not sure on that and was just looking for a way to either relock the bootloader or reflash it. Probably isn't at the moment but some have been asking about this because of issues with the ota.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

[Q] Error on Installing TWRP and Can't recover to ICS, same Problem?

I have had my TF700 for a while, and merrily went from ICS through the various OTA upgrades to 4.2.1
I have attempted to follow along the "All in One Guide" in order to get Rooted so I can install Cyanogenmod or alternative to get rid of the crapware delivered by Asus. But I seem to get stuck when trying to "Flash" anything. Or at least I think so.
I unlocked the bootloader using the apk provided by Asus. Bootloader shows as unlocked when booting.
adb devices shows my device attached. When booted into fastboot mode fastboot devices shows my device attached.
I have also done a complete data wipe, not that that should matter.
1st, I have tried to install twrp using GooManager, and the fastboot method. Using GooManager, the file downloads and then nothing seems to happen. GooManager will also not reboot to recovery. Using the Fastboot method I get "error: cannot load 'twrp.blob': No error". I have downloaded the file multiple times and it does not appear to be corrupted.
I have tried to roll back to ICS by downloading the correct firmware, renaming it and copying to my SDCard, then booting into recovery. US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip I only get the Android guy with the red triangle until it reboots.
I have also tried http://forum.xda-developers.com/showthread.php?t=1929712 but this does nothing as twrp is not installed and the regular recovery doesn't do anything.
What should I try next? It would seem like I'm missing something obvious.

When you download firmware from Asus, the file you need to put on your SDCard is not the file you downloaded, but the zip file contained within. Its a zip in a zip. Extract the file you downloaded and you will find another zip file inside and that's the one you rename and copy to your SDCard. Also make sure your SDCard is formatted FAT32. exFAT will not work and is the default Sandisk format.

Got rolled back to ICS but..
I successfully rolled back to ICS .30
Now adb fails to recognize the device. Previously it did recognize. I reinstalled the drivers in fastboot mode and "normal" mode. I have tried the universal naked drivers and the Asus drivers. fastboot reboot will successfully reboot the device, but nothing shows up when I do a adb devices or fastboot devices.
fastboot -i 0x0B05 flash recovery twrp.blob Gets the same error, error: cannot load 'twrp.blob': No error.
When I run through *** Rooting Your TF700 with Debugfs automated root *** I get the error "You must install device specific drivers...."

Fixed
Adhar said:
I successfully rolled back to ICS .30
Now adb fails to recognize the device. Previously it did recognize. I reinstalled the drivers in fastboot mode and "normal" mode. I have tried the universal naked drivers and the Asus drivers. fastboot reboot will successfully reboot the device, but nothing shows up when I do a adb devices or fastboot devices.
fastboot -i 0x0B05 flash recovery twrp.blob Gets the same error, error: cannot load 'twrp.blob': No error.
When I run through *** Rooting Your TF700 with Debugfs automated root *** I get the error "You must install device specific drivers...."
Click to expand...
Click to collapse
I discovered that I couldn't install twrp as I was in the wrong folder when executing the command. I needed to cd to the folder that contained the .blob file. Then it was trivial to use twrp to flash the root.zip file and gain root, and then flash cyanogenmod 10.0, wipe, and then reboot.
Everything is fine, now downloading Google apps.

Adhar said:
I discovered that I couldn't install twrp as I was in the wrong folder when executing the command. I needed to cd to the folder that contained the .blob file. Then it was trivial to use twrp to flash the root.zip file and gain root, and then flash cyanogenmod 10.0, wipe, and then reboot.
Everything is fine, now downloading Google apps.
Click to expand...
Click to collapse
When I read "seems like I'm missing something obvious" from your original post I went back and re-read it looking for the obvious. It wasn't immediately apparent what was wrong. If you hadn't posted the name of the firmware file it wouldn't have been obvious to me either but I thought I recognized it as the downloaded not the internal zip file name and verified it with my downloaded firmware. Glad to help and that you got it all worked out.

(Q) Boot Loop fix

Well my dumb fast moving self has backfired once again. While using chain fire 3D I have now got myself stuck in a boot loop. I have tried wipe data both from menu and from paperclip. I have tried getting latest firmware from asus site and using RCK but for some reason it just shows me a dead DROID. So any tips would be great I can't send it back because it's unlocked and rooted. So if anyone knows of a way to get RCK or the wipe data's to work I would be forever in your debt

Sevyth said:
Well my dumb fast moving self has backfired once again. While using chain fire 3D I have now got myself stuck in a boot loop. I have tried wipe data both from menu and from paperclip. I have tried getting latest firmware from asus site and using RCK but for some reason it just shows me a dead DROID. So any tips would be great I can't send it back because it's unlocked and rooted. So if anyone knows of a way to get RCK or the wipe data's to work I would be forever in your debt
Click to expand...
Click to collapse
You have to flash TWRP recovery via fastboot. BUT, be sure to flash the correct version of TWRP. Flashing the wrong TWRP recovery blob can brick your tablet.
Since, you did not mention the firmware version running on your tablet, we can only guess...
If you were on Android 4.0.x (also known as Ice Cream Sandwich or ICS), you need to flash TWRP blob with "-ICS" suffix. For example, openrecovery-twrp-2.4.4.0-tf300t-ICS.blob.
If you were on Android 4.1.x (also known as JellyBean or JB) before ASUS firmware version 10.6.1.8, you need to flash TWRP blob with "-JB" suffix. For example, openrecovery-twrp-2.4.4.0-tf300t-JB.blob.
If you were on ASUS firmware version 10.6.1.8 (Android 4.2.1) you need to flash openrecovery-twrp-2.4.4.0-tf300t-4.2.blob.
If you were on ASUS firmware version 10.6.1.15.3 (Android 4.2.1) you need to flash openrecovery-twrp-2.5.0.0-tf300t-4.2.blob.
And, if you have TF300TG model, get the TWRP blob with -tf300tg-. Once again, flashing the incorrect TWRP can brick your tablet. So, please be extra careful.
To download the necessary TWRP recovery blob files, and for the instructions on how to flash it to your tablet, visit the TWRP official website for TF300T(G) here: http://www.teamw.in/project/twrp2/97
After flashing the correct TWRP recovery, you can now launch the TWRP recovery via RCK. From there, you can flash ASUS stock firmware to fix your bootloop. I would recommend following method 3 outlined in the GUIDE found here: http://forum.xda-developers.com/showthread.php?t=2187982

How is this supose to work if my RCK always shows a dead DROID. And how do I get fast boot to work when fast boot freeze when I click the usb icon

"If you were on Android 4.1.x (also known as JellyBean or JB) before ASUS firmware version 10.6.1.8, you need to flash TWRP blob with "-JB" suffix. For example, openrecovery-twrp-2.4.4.0-tf300t-JB.blob."
I believeThis is the Firmware i was On but im still not sure how to get fastboot to work. or RCK
EDIT: Seems that Link you provided to learn how to put the recovery on is out of date,
EDIT II: "You will need fastboot for this method. Download the above file, check the md5, rename to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
fastboot -i 0x0B05 flash recovery twrp.blob" - Will ya translate to english , And as I said when i go into fastboot mode and click the USB icon it freezes.
EDIT III: 10.4.2.20 is my model # i belive
EDIT IIII : Downloaded fastboot But cant run it . i open fastboot and it just closes. Any ideas?