[Q] problem about TF300T - Transformer TF300T Q&A, Help & Troubleshooting

sorry for my poor english:crying:
i hope you can understand what i need help
my TF300T OTA updated 4.2.1
tonight i unlocked my TF300T and flashed CWMV6.0.2.3
but the recovery can't mount all choice in "mounts and storage"
then i see this"http://forum.xda-developers.com/showthread.php?t=2206996"
he said"FIXED!!! Did a wipe....in the fastboot screen (not in recovery since it didn't work)And now the internal sd is visible and mounted, so next step flashed supersu......aaaaaaand i'm done "
then i do the same
a wipe in fastboot screen
and now i can't enter fastboot screen (no matter have/not press volumedown+power)
it can only enter recovery but do nothing becasue recovery can‘t mount everything
i have no confidence you will understand my english...
are there other ways enter fastboot?how can i revive it only can use recovery?
many thanks
May i ask another question for help
i did the wipe data in bootloader once
now in recovery mode /adb devices can get it
but in bootloader /fastboot devices can't connect my device now
so i can't flash The official firmware use /fastboot -i 0x0b05 flash system blob
are there anyway to fix it?
thanks verymuch

i have the same problem. only i flasher the latest twrp recovery. TWRP 2.4.4.0 Touch Recovery

First, CWM 6.0.2.3 is not compatible with Asus 4.2.1, you should have done a little bit of reading and you would have found this very useful thread http://forum.xda-developers.com/showthread.php?t=2187982 where it explains everything you can possibly know and need about upgrading and flashing recovery and gain root. on 4.2.1
Both of you guys have flashed incompatible recovery versions for your bootloaders and now are stuck, try to access Fastboot, keep trying update your drivers and also check several USB ports because fastboot is your only choice now.
Erik

ricco333 said:
First, CWM 6.0.2.3 is not compatible with Asus 4.2.1, you should have done a little bit of reading and you would have found this very useful thread http://forum.xda-developers.com/showthread.php?t=2187982 where it explains everything you can possibly know and need about upgrading and flashing recovery and gain root. on 4.2.1
Both of you guys have flashed incompatible recovery versions for your bootloaders and now are stuck, try to access Fastboot, keep trying update your drivers and also check several USB ports because fastboot is your only choice now.
Erik
Click to expand...
Click to collapse
thanks Erik,thanks for your reply
May i ask another question for help
i did the wipe data in bootloader once
now in recovery mode /adb devices can get it and replied ”0123456789ABCDEF recovery“(but this is not my S/N number)
but in bootloader /fastboot devices can't connect my device now
so i can't flash the official firmware use /fastboot -i 0x0b05 flash system blob
are there anyway to fix it?
thanks verymuch

Related

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] help please!!!!!

I just got my new asus transformer tf300t-bl and wanted to root and install either twrp or cwm on it,I unlocked it and when i went to reboot it i hit the volume up on the RCK and now its stuck on RCK and it didnt boot into the usb like it says it will on the forums. Now when i reboot it,it says " key driver not found.. booting os android cardhu-user bootloader < 1.00 e> released by "us_epad-10.6.1.8-20130225" a03 starting Fastboot usb download protocol. does anyone know what i can do? i would greatly appreciate ANYONES HELP THAT KNOWS IF THEY'VE DONE THIS TO THEIRS AND IF THIS IS FIXABLE. I USE THIS FOR COLLEGE AND JUST PAID $ 400 and cant afford to buy another one. Somebody please tell me i havent screwed the pooch and that it still can be flashed into recovery and rooted. Thanks you guys. As i rooted and flashed my transform ultra perfectly because of you guys and used the megatron 6 and love it.
No you haven't you need to download fastboot and connect the tablet to your computer, on that screen just let it sit their.
Download the asus firmware. Follow the flashing fastboot guides here. You need to flash the blob file.
flashing recovery/ ref: help me
sevenalive said:
No you haven't you need to download fastboot and connect the tablet to your computer, on that screen just let it sit their.
Download the asus firmware. Follow the flashing fastboot guides here. You need to flash the blob file.
Click to expand...
Click to collapse
im a lil new to doing this so would you please give me a detailed list of exactly what to do. and what firmware do i need to download from asus. And can all of this be done using a mac? and how do i flash it all to my comp. or from it to the tablet.
It should help you :https://www.google.pl/webhp?sourcei....r_qf.&bvm=bv.43828540,d.ZWU&biw=1274&bih=856
need your help plz
Hazard17 said:
It should help you :https://www.google.pl/webhp?sourcei....r_qf.&bvm=bv.43828540,d.ZWU&biw=1274&bih=856
Click to expand...
Click to collapse
i did everything it stated to do and when i get to the last steps to root my tf300t, it says adb cannot run as root in production builds. Im at a loss as to what to do at all. IM a noob, and i follow each command on terminal perfectly and everything executes till the last or itll say permission denied. What do i do or am i doing wrong. Im following the instructions of post forum.xda-developers.com/showthread.php?t=1720980
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
re: help me
philmg said:
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
Click to expand...
Click to collapse
how did you flash fastboot and cwm and reflashed the blob files to your asus? on my terminal on my mac itll say cant execute root on production models and requests a password. Have you had the same problems? can u give me a step by step how u flashed cwm and fastboot and the blob files. and how did you install the latest firmware
420Misfit said:
how did you flash fastboot and cwm and reflashed the blob files to your asus? on my terminal on my mac itll say cant execute root on production models and requests a password. Have you had the same problems? can u give me a step by step how u flashed cwm and fastboot and the blob files. and how did you install the latest firmware
Click to expand...
Click to collapse
well, I am using a win xp machine for fastboot. so I don't have the same issues. fastboot works fine, so that I use the normal fastboot process to flash the system and the recovery kernel.
I finally got it to work again by flashing the newest TWRP instead of CWM. It seems CWM does not yet work on the latest firmware.
I followed this guide for flashing TWRP with fastboot. This version actually also just asked me, if I want to root the device, I clicked yes and it was rooted. Perfect.
http://forum.xda-developers.com/showthread.php?t=2187982
philmg said:
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
Click to expand...
Click to collapse
I am in EXACTLY the same boat as you. The only difference is that I flashed TWRP instead of CWM. I finally decided that it was time to root my tablet...got tired of the lag. IIRC I've gotten the "key driver not found.. booting OS" error message since doing the OTA update to 4.2 (I did this prior to rooting.) Everything SEEMS to be working okay, but this bugs the heck outta me, and I'm sure it can't be a good thing. Hoping somebody will chime in with a fix for this. I've searched and searched to no avail.

[Q] fastboot freeze

i have asus tf300t in the android 4.2.1 latest update and has root the system but still using stock rom
this morning try to swtich to custom rom
i flash to cwm v6.0.2.3
and did a full wipe on everything
after that the system keep boot to cwm with nothing else and wont mount anything
read couple post
and able to manager get to bootloader to try fastboot mode
but as i use the command pompt to fastboot -i 0x0b05 flash recovery twrp.blob
it freeze on tablet
the command pompt say is finish and successful
the twrp is the openrecovery.....4.2.blob
but it wont flash
then i got back to bootloader and able to do a cold boot to the stock rom
so i need help how to install the twrp in different way (goo manager or terminal) and fix the issue on anytime the system restart and enter to cwm on it own
the following xda i try it wasnt work as i following through
http://forum.xda-developers.com/showthread.php?t=2283563
http://forum.xda-developers.com/showthread.php?t=2201015
http://forum.xda-developers.com/showthread.php?t=1830108
if there is any fix please let me know thx
Unfortunately you flashed CWM on 4.2.1 and then unfortunately again you issued a wipe.
Fortunately you haven't bricked but you were close.
One of the TF300 gurus may be able to help you recover.
it get worst
sbdags said:
Unfortunately you flashed CWM on 4.2.1 and then unfortunately again you issued a wipe.
Fortunately you haven't bricked but you were close.
One of the TF300 gurus may be able to help you recover.
Click to expand...
Click to collapse
do u know anyone can help
i think i got worst
i keep trying
in cmd i try these code
fastboot -i 0x0b05 flash system blob
or
fast boot -i 0x0b05 flash system twrp.blob
after that i cant cold boot to the android
it just wont load
i can only load to cwm everytime to restart
then i have to cmd
and adb reboot-bootloader
then i can boot to fastboot
but the other issue is in the bootloader it didnt show the usb icon
so anytime i try fastboot the with any blob
it freeze
is their anyway i can get the usb icon in the bootloader
then i can flash the system
the cmd show everything can read and
Now it sounds like you have hard bricked sorry to say.
sbdags said:
Now it sounds like you have hard bricked sorry to say.
Click to expand...
Click to collapse
is that mean i need a new tablet
is there any solution that can fix back

[Q] help to get back to stock

tf300t unroot with android 4.2.1
running in 10.6.1.15.3
system always boot to cwm
from pc using cmd using adb reboot-bootloader
in the fastboot mode
with no usb icon
unable to flash with anything
not even able to cold boot
just only able to boot to cwm v6.0.2.3
each time need to cmd to boot to fastboot but no usb icon
any idea
question is this mean im in brick
Sheena0220 said:
tf300t unroot with android 4.2.1
running in 10.6.1.15.3
system always boot to cwm
from pc using cmd using adb reboot-bootloader
in the fastboot mode
with no usb icon
unable to flash with anything
not even able to cold boot
just only able to boot to cwm v6.0.2.3
each time need to cmd to boot to fastboot but no usb icon
any idea
question is this mean im in brick
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=42011887#post42011887 - read this post and let me know if you have any questions.
it doesnt work for me
i did exactly how you say
place the unzip file to sdcard
place the sd card to the side of the mmsd slot
reboot the tablet
nothing happen
even try to reboot in the fastboot mode and press the up button at he rck mode
still no go
i just have no idea how i got to the point that the bootloader fail went i in the fastboot->rck
show that fail bootloader with (0x000000000)
i can only get to APX mode and Fastboot using pc (but i cant do nothing to it) it doesnt show the usb icon
i can read the tablet
but i cant write anything to it
im still waiting for something happen
hope one of this master
have a software and about to bring back to live
Sheena0220 said:
it doesnt work for me
i did exactly how you say
place the unzip file to sdcard
place the sd card to the side of the mmsd slot
reboot the tablet
nothing happen
even try to reboot in the fastboot mode and press the up button at he rck mode
still no go
i just have no idea how i got to the point that the bootloader fail went i in the fastboot->rck
show that fail bootloader with (0x000000000)
i can only get to APX mode and Fastboot using pc (but i cant do nothing to it) it doesnt show the usb icon
i can read the tablet
but i cant write anything to it
im still waiting for something happen
hope one of this master
have a software and about to bring back to live
Click to expand...
Click to collapse
The previous link you were provided only works with stock recovery not cwm or twrp.
The 4.2 bootloader (10.6.?.?.?) does not have a usb icon. When you get to the bootloader press no buttons and wait for notification in the upper left - entering fastboot.
Sheena0220 said:
it doesnt work for me
i did exactly how you say
place the unzip file to sdcard
place the sd card to the side of the mmsd slot
reboot the tablet
nothing happen
even try to reboot in the fastboot mode and press the up button at he rck mode
still no go
i just have no idea how i got to the point that the bootloader fail went i in the fastboot->rck
show that fail bootloader with (0x000000000)
i can only get to APX mode and Fastboot using pc (but i cant do nothing to it) it doesnt show the usb icon
i can read the tablet
but i cant write anything to it
im still waiting for something happen
hope one of this master
have a software and about to bring back to live
Click to expand...
Click to collapse
http://www.androidauthority.com/transformer-pad-tf300t-restore-stock-firmware-108016/ = try this method. this is the fastboot method. FYI, as sheena said, you dont need to see the usb icon. immediately u boot into the bootloader, the tablet enters fastboot mode. if you need more detailed instructios, add me on skype or facebook. i'll be glad to help.
crazynitro said:
http://www.androidauthority.com/transformer-pad-tf300t-restore-stock-firmware-108016/ = try this method. this is the fastboot method. FYI, as sheena said, you dont need to see the usb icon. immediately u boot into the bootloader, the tablet enters fastboot mode. if you need more detailed instructios, add me on skype or facebook. i'll be glad to help.
Click to expand...
Click to collapse
thx for the instruction
i will try it tonight
i think i see somewhere before and try it before with the code in the cmd
at fastboot
while the tablet still flashing with the 3 icon (rck, android, and wipe data)
in pc i type this code as follow
fastboot device
come out the sn #
fastboot -i 0x0b05 flash system blob
then the tablet freeze but the cmd is say success
but i try only one or two time
at this moment i only able to boot in to fastboot by hard reset and the APX
in APX mode the pc didnt recognize the driver
also i try couple at fastboot mode in tablet i hit the upper vol at RCK
it return message as follow
bootloader fail
code is 0X 00000000
i know it is not in brick
the system has no os to boot too
and the tablet has no wait to write anything into it
but i will try the method you have instruct tonight at see any chance
hope no need to send back to the shop to fix it
Sheena0220 said:
thx for the instruction
i will try it tonight
i think i see somewhere before and try it before with the code in the cmd
at fastboot
while the tablet still flashing with the 3 icon (rck, android, and wipe data)
in pc i type this code as follow
fastboot device
come out the sn #
fastboot -i 0x0b05 flash system blob
then the tablet freeze but the cmd is say success
but i try only one or two time
at this moment i only able to boot in to fastboot by hard reset and the APX
in APX mode the pc didnt recognize the driver
also i try couple at fastboot mode in tablet i hit the upper vol at RCK
it return message as follow
bootloader fail
code is 0X 00000000
i know it is not in brick
the system has no os to boot too
and the tablet has no wait to write anything into it
but i will try the method you have instruct tonight at see any chance
hope no need to send back to the shop to fix it
Click to expand...
Click to collapse
i had try the method
tablet freeze as soon as i start the code of
fastboot -i 0x0B05 flash system blob
i do see in cmd say finish and ok
i try code of fastboot -i 0x0B05 reboot
tablet didnt response
try fastboot devices
come back will
??????????????????? list
i just dont know what to do
it freeze all the time as i write something into tablet
Sheena0220 said:
i had try the method
tablet freeze as soon as i start the code of
fastboot -i 0x0B05 flash system blob
i do see in cmd say finish and ok
i try code of fastboot -i 0x0B05 reboot
tablet didnt response
try fastboot devices
come back will
??????????????????? list
i just dont know what to do
it freeze all the time as i write something into tablet
Click to expand...
Click to collapse
which firmware did you download? have you tried flashing a recovery img like twrp?
crazynitro said:
which firmware did you download? have you tried flashing a recovery img like twrp?
Click to expand...
Click to collapse
i use us one and get the blob out
i think i got what you mean now
i have to have the right blob before i can get the flash work if not i will freeze it
the problem is i cant even boot to android
so i have no clue on will firmware i using
all i can see from now is at the fastboot that only is us ...10.6....
is that the firmware i have to flash if do so i will try
i cant even flash the twrp into the tablet
i try blob and img
it wont work
i try the version is the 2.5......4.2.blob or img
it just got no luck at all
thx thx thx
Sounds like you flashed the incorrect twrp for your bootloader, flashing a non-4.2 twrp on a 4.2 bootloader can cause a fastboot flash brick.
Here's a little info about the changes from a 4.1 to a 4.2 bootloader as there have been quite a few bricks here over the last few months.
Still not sure of the exact issue here but seems there was a change in some or all of the partition tables with the 4.2 bootloaders for both 10.6.1.8 & 10.6.1.15.3 and as a result after updating to 4.2 and then flashing TWRP (non-4.2 version) or CWM recovery would give the following outcome when you boot to recovery.
TWRP would ask for a password on boot, you can hit cancel but are left not being able to mount any partition including external apart from possible system.
CWM was the same, unable to mount any partition.
The device will now also likely boot strait to recovery, and if you have not wiped system you will now have to cold boot andriod from now on.
Now the bad part - In about 90% of cases flashing TWRP (non-4.2 version) or CWM would also result in a fastboot flash brick, meaning that some other fastboot commands will work ok, however any fastboot flash command will look to go ok on the command prompt but you will no longer get the blue progress bar on the tablet and nothing will flash to the tablet. So your either stuck with the current os and have to cold boot or if you wiped your system your just stuck.
Only solution so far to this issue is to replace your motherboard. Here's a thread on the issue http://forum.xda-developers.com/show....php?t=2179874
And thus the -4.2 versions of TWRP were made for the 4.2 bootloaders
JB 4.2 bootloaders require the -4.2 versions of twrp
- JB 4.2.1 - 10.6.1.8 = twrp 2.4.4.0-4.2
- JB 4.2.1 - 10.6.1.15.3 = twrp 2.5.0.0-4.2
So if you do not get the blue progress bar on tablet when running a fastboot flash command then sorry to say you have the fastboot flash brick.
There are many many threads/posts on this issue with the above info but still people are not reading, bricking there tablets and creating duplicate upon duplicate threads on this issue, so please look through the threads first, read, read and read some more and if still not sure ask as many questions as you need.
Hope this helps explain what has happened and why the fastboot flash command freezes your tablet.
ok thx for everyone that give a great advice
i just change a new motherbooard
and now the tablet is in a unroot and unlock
i just want a instruction on how to do the unlock and root correctly
i read so many post
i just confuse
im in a android 4.2.1
and us 10.6.1.15.3
any suggestion before i got mess up

HELP stuck on boot loop with access to recovery

Basically Ive had my tf300t for just over a year
i was running stock untill the jb update shortly after I rooted and flashed cleanrom somewhere between this feb and april
the rom flashed fine using CWM 6.0.1.3 but in May my tablet was stepped on and the screen was cracked
i had it fixed when i got it back the screen had no TOUCH
So heres my issue stupid me... whatever knowledge i have about android has come off of this website
so i dont know why i figured i could do this myself
Either way when i fixed the screen i wanted to flash a new rom
so i downloaded latest pacman 4.3 and went about a proper flash i wiped data and cache in recovery
but when i went to flash the rom it appeared recovery had wiped my micro sd instead with all my backups
i ended up going into what i understand is the bootloader..its the screen with four options RCK android usb and wipe data...
i choose the later of the four options which completely wiped the tablet.. i thought it was the same procedure as in recovery
so at the moment the tablet bootloops however i can boot CWM also the screen i mentioned earlier (RCK / ANDROID / USB / WIPE DATA)... ive tried to flash a rom and i keep getting an error saying the file is bad... so now ive looked all over this forum but i really cant find anything that directy helps me i know there are issues with CWM but unfortunately i cant use the touch features which come in TWRP and my computer wont install the drivers or id try pushing the rom to the internal sd.....
really any help would be apreciated any at all just please bear in mind i need to stay on a non touch recovery
bootloader screen reads----> Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.17-20121018" A03
recovery ----> CWM 6.0.1.3 and getting a lot of errors
It looks like You installed pacman on 4.1 firmware, I'm right? Most current custom ROMs can be installed only on 4.2 stock firmware. First of all try to remove all asus software and drivers for tablet from Your PC and install nacked drivers. Then reinstall stock firmware through fastboot(I hope You know how to enter fasboot mode) to fix tablet (use firmware version as You have before brick or newer).
P.S.: And CWM doesn't support new ROM as well, so use proper version of TWRP.
Graiden05 said:
It looks like You installed pacman on 4.1 firmware, I'm right? Most current custom ROMs can be installed only on 4.2 stock firmware. First of all try to remove all asus software and drivers for tablet from Your PC and install nacked drivers. Then reinstall stock firmware through fastboot(I hope You know how to enter fasboot mode) to fix tablet (use firmware version as You have before brick or newer).
Click to expand...
Click to collapse
Ok perfect i was just on the asus website and there is newer firmware available as of 2013 9 13 so i will try this out thanks so much!
Graiden05 said:
It looks like You installed pacman on 4.1 firmware, I'm right? Most current custom ROMs can be installed only on 4.2 stock firmware. First of all try to remove all asus software and drivers for tablet from Your PC and install nacked drivers. Then reinstall stock firmware through fastboot(I hope You know how to enter fasboot mode) to fix tablet (use firmware version as You have before brick or newer).
P.S.: And CWM doesn't support new ROM as well, so use proper version of TWRP.
Click to expand...
Click to collapse
OK i installed naked drivers on a pc that had never seen the tablet before or any asus device for that matter...your link to fastboot seemed really confusing to me so i just downloaded Minimal ADB and Fastboot using post 2 on this guide http://forum.xda-developers.com/showthread.php?t=2277112 and then tried to flash the stock asus firmware following instructions from post 4 but the commands all came back with problems
ill post the screenshot any input is greatly apreciated!
Try to use usb port on rear side of desktop PC. Front usb ports and laptops can cause problems to fastboot.
Alright I'll have to find a desktop thanks for your help and as far as the commands I used, was i doing everything right? is there difference in commands when flashing a custom ROM and flashing stock firmware through fastboot?
I can use commands like fastboot reboot-bootloader and fastboot devices they work successfully
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Tried on my old desktop running xp using the back USB port and got the same errors I also tried extracting the blob from the rom and flashing that and got no response from fastboot. after an hour I reset the tablet and nothing has changed...
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Try to use following command with blob file from unpacked stock firmware
Code:
fastboot -i 0x0B05 flash -w -u staging blob
.
Still no response from fastboot but I found this thread not sure if it applies to my case but I'm going to try later
http://forum.xda-developers.com/showthread.php?t=2179874&page=19
Aperently these commands will fix the issue... Asus was charging $200 for a motherboard replacement
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob

Categories

Resources