Database Info

[Q] help, i think i bricked my tablet

hi, first of all, i'd like to tell you i'm quite a noob
i have a tf300tg and i tried to flash the jb 4.2.2 that's only available for the 300t.. i'm dumb, i know.. and now in stead of booting it goes directly to the cwm menu and i can't do anything.. i keep getting the error E:Can't mount /cache/recovery/command , .../log and .../last_log
is there anything i can do or should i just throw it in the trashbin ?

iostu said:
hi, first of all, i'd like to tell you i'm quite a noob
i have a tf300tg and i tried to flash the jb 4.2.2 that's only available for the 300t.. i'm dumb, i know.. and now in stead of booting it goes directly to the cwm menu and i can't do anything.. i keep getting the error E:Can't mount /cache/recovery/command , .../log and .../last_log
is there anything i can do or should i just throw it in the trashbin ?
Click to expand...
Click to collapse
Unless you can go into fastboot (Power + volume down) there isn't much to do but to sign a petition & wait...
XDA member HAZARD17 has been running a petition
Sign NVflash petition for Transformer TF300T, Prime & Infinity!
https://www.change.org/petitions/asus-nvidia-revert-changes-in-jb-bootloader-that-prevent-nvflash

vconceicao said:
Unless you can go into fastboot (Power + volume down) there isn't much to doo but to wait...
Click to expand...
Click to collapse
i can't do that either.. it just loads the CWM menu..
wait ? wait for what ? :silly:

iostu said:
i can't do that either.. it just loads the CWM menu..
wait ? wait for what ? :silly:
Click to expand...
Click to collapse
For someone to come up with a solution, Like a NVflash utility for Tf300...

Yeah, but if you want add NVflash support to your tablet, it can't be bricked I'm not quite sure, but you try unpack blob from offical update, and flash all files from unpacked blob (LNX etc.).

Hazard17 said:
Yeah, but if you want add NVflash support to your tablet, it can't be bricked I'm not quite sure, but you try unpack blob from offical update, and flash all files from unpacked blob (LNX etc.).
Click to expand...
Click to collapse
i can't flash anything :| in adb it sais <waiting for device> i've tried everything and i can't get it to work.. can you pleeeeeease help me ?

ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please

iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
The USB icon is gone. I sugguest downloading the correct firmware and flashing it with fastboot.
fastboot flash system blob
Download the correct system firmware, open the zip, open the zip, extract the blob to the same directory as fast boot.

iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
4.2 bootloader does not have USB icon, just plug in USB..

i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !

iostu said:
i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !
Click to expand...
Click to collapse
Sounds like you're in the same boat as the rest of us...
http://forum.xda-developers.com/showthread.php?t=2179874

iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
OK. The bootloader menu you now are seeing is the new 4.2 version. RCK - Android - Wipe Data(do not use wipe data).
When you get into this menu if you leave everything alone your tablet should auto into fastboot - watch the screen - upper left.
With fastboot flash the latest (proper) JB blob for your unit.
Good Luck!

iostu said:
i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !
Click to expand...
Click to collapse
You can't flash anything using adb commands. You need to use fastboot. Look in the forum for the proper procedure and follow the instructions.
Nowhere does it say type "adb fastboot ... anything...."

hgoldner said:
You can't flash anything using adb commands. You need to use fastboot. Look in the forum for the proper procedure and follow the instructions.
Nowhere does it say type "adb fastboot ... anything...."
Click to expand...
Click to collapse
Here is an example of an adb command that does work to flash twrp with slight modification it will flash stock blob as well.
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I don't know where you are getting your information but you need a new source.
No one said type adb fastboot they are two different things and each has a specific structure to follow.
If the op can get either fastboot or adb to work I'll gladly provide the proper commands.

then you have the same problem as me and a bunch of other people. The bootloader freezes on the flash command, even though it will show success and stuff. It never flashes.
I can push files with ADB and on reboot the files on gone. Since we can't flash with fastboot. We have to send it in to asus at this point. I got quoted $87 + shipping.

sorry, i meant to say just fastboot. i didn't write adb fastboot.. i've tried everything you guys said, but with no success my last resort is to send it to asus for re-softing. It costs about $80 + shipping. It doesn't sound like a lot of money, but it's a price to pay for stupidness or noobness i just hope they can repair it or otherwise i'll have a very expensive thing on whch to chop onions
thanks again guys for helping me

[Q] Brickety Brick

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Did I really hard brick my TF300T?

Today I felt ambitious and tried to install a new JB rom (AOSPA 4.2.2). The instructions said that if I had 3 icons I would be on JB bootloader and that I would need to upgrade to the latest TWRP 2.5.0.0 (I was on 2.4.4.0). Well, what I missed is the fact that there were two different versions of 2.5.0.0 (one specifically for JB 4.2) and of course I flashed to wrong one.
Now when the tablet boots it goes straight to recovery and asks for a PW (I don't know the password and never set one). I can select cancel which lets me into the main menu but none of the functions actually have write access. Nothing mounts or lets me gain access to the internal memory. When I try to reboot it immediately goes back to recovery, never letting me get back into fastboot to install the correct version.
Reading some forums and doing some other google search I don't find anyone with exactly the same problem, but it seems that I cannot get out of this mess. I know that nvflash is out of question since that is not working on JB yet.
If anyone has encountered a similar issue or knows how I could potentially get fastboot to trigger again so I can flash the correct version of recovery, that would be a great start.
Thanks !!

Have a look here
http://forum.xda-developers.com/showpost.php?p=42254642&postcount=10

pjc21 said:
Have a look here
http://forum.xda-developers.com/showpost.php?p=42254642&postcount=10
Click to expand...
Click to collapse
Great, That is exactly what happened. Looks like I'll be looking for a new tablet.
I am wondering if the Google Nexus 10 would have a similar risk of bricking. Guess it's time to do some research.
Thanks.

anosis said:
Great, That is exactly what happened. Looks like I'll be looking for a new tablet.
I am wondering if the Google Nexus 10 would have a similar risk of bricking. Guess it's time to do some research.
Thanks.
Click to expand...
Click to collapse
You may want to check & confirm that fastboot will not flash (you don't get the blue bar on tab when flashing) before looking for a new tab, although this "fastboot flash brick" issue results about 90% of the time you may be lucky and be in that 10% that does not.
You should be able to access fastboot using the "adb reboot-bootloader" command while in recovery, if pc does not pick-up device for adb in recovery have a look here and follow on from the device manager part.
When you get to the bootloader menu have a look at the text in the top left and confirm which 4.2 bootloader version your on, either 10.6.1.8 or 10.6.1.15.3 - then download the correct twrp version for that bootloader and see if you can flash it via fastboot.
If that does not work, which will most likely not would you like to try something for me? which may or may not work, just an idea.
Download this file, unzip it & copy the bootloader.bin file in your android-sdk/platform-tools folder.
Boot back to fastboot using the adb reboot-bootloader command and try
Code:
fastboot -i 0x0b05 flash bootloader bootloader.bin
If this works and does not freeze the tab then
Code:
fastboot reboot-bootloader
If the tab does reboot to this command then check the bootloader version here in the bootloader menu and if it has worked it should say 10.4.2.20 in the text in the top left of the screen.
If by chance this has worked then you should also now have 4 icons in the bootloader as you will now be back on a 4.1 bootloader.
If this does work at all let me know for next steps.

pjc21 said:
You may want to check & confirm that fastboot will not flash (you don't get the blue bar on tab when flashing) before looking for a new tab, although this "fastboot flash brick" issue results about 90% of the time you may be lucky and be in that 10% that does not.
You should be able to access fastboot using the "adb reboot-bootloader" command while in recovery, if pc does not pick-up device for adb in recovery have a look here and follow on from the device manager part.
When you get to the bootloader menu have a look at the text in the top left and confirm which 4.2 bootloader version your on, either 10.6.1.8 or 10.6.1.15.3 - then download the correct twrp version for that bootloader and see if you can flash it via fastboot.
If that does not work, which will most likely not would you like to try something for me? which may or may not work, just an idea.
Download this file, unzip it & copy the bootloader.bin file in your android-sdk/platform-tools folder.
Boot back to fastboot using the adb reboot-bootloader command and try
Code:
fastboot -i 0x0b05 flash bootloader bootloader.bin
If this works and does not freeze the tab then
Code:
fastboot reboot-bootloader
If the tab does reboot to this command then check the bootloader version here in the bootloader menu and if it has worked it should say 10.4.2.20 in the text in the top left of the screen.
If by chance this has worked then you should also now have 4 icons in the bootloader as you will now be back on a 4.1 bootloader.
If this does work at all let me know for next steps.
Click to expand...
Click to collapse
Followed your google usb instructions to make ADB work. Executed the bootloader command and was greeted with the three icons (4.2 bootloader I believe). Then flashed the correct TWRP 2.5 4.2 (no blue progress bar) and waited for the command prompt to show successful write. Rebooted and when recovery started up, showed nothing was different. Still requires me to enter a PW and none of the mounts work.
Then followed your bootloader update instructions and while it said it was successful I only get three icons when in fastboot.
Should I try the older TWRP that I had on there before (2.4.4.0) to see if that at least lets me back in?

anosis said:
Followed your google usb instructions to make ADB work. Executed the bootloader command and was greeted with the three icons (4.2 bootloader I believe). Then flashed the correct TWRP 2.5 4.2 (no blue progress bar) and waited for the command prompt to show successful write. Rebooted and when recovery started up, showed nothing was different. Still requires me to enter a PW and none of the mounts work.
Then followed your bootloader update instructions and while it said it was successful I only get three icons when in fastboot.
Should I try the older TWRP that I had on there before (2.4.4.0) to see if that at least lets me back in?
Click to expand...
Click to collapse
Miraculously the tablet will allow me now to cold boot into the previous rom. That at least makes it usable again, but it probably means that I am stuck on this. Also strange is that the tablet now no longer is recognized as a USB device. I cannot access the internal ram??

Under 'About Tablet' my build # shows 10.6.1.14.4/US DEODEX. Not sure if this might help in fixing the recovery issue?
Anyway I am glad I don't have to spend money to get a replacement, but sure hope I can fix the existing recovery image issue.

So tried to flash back the previous version of TWRP and it will not. Even though the fastboot command prompt shows a successful flash nothing appears to be changed, which refers to the original issue that states that I am stuck on whatever rom is on this tablet.
Is the reason I cannot flash back an older or correct version because there is a permission issue? Is there something I can do directly from within the rom after it boots up, like the shell emulator?

LG GPAD 7 stuck on Fast Boot

Purchased an Lg Gpad 7 Wifi tablet (v400) 2 weeks ago. Came with preinstalled Lollipop android so i couldnt install a recovery rom to flash any other custom roms. Downgraded to Kitkat version following the instructions on Xda forums and succesfully installed Twrp. When i installed Cyanogenmod 12.1 through Twrp i got stuck in fastboot screen.
Any suggestions and / or solutions would be greatly appreciated.

I had a similar problem.. Only mine was stuck at the bootloader. Go in TWRP and repair /data and other partitions. My data partition gave me an error since F2FS is a little flaky and some ROMs corrupted it (claimed they supported it). I would recommend erasing the system, cache and data partition if you can't get into TWRP.

The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.

Hakalai said:
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Click to expand...
Click to collapse
if you have an sd card, try removing that, then reboot.
if that doesnt work, try entering fastboot command, fastboot continue

Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.

Hakalai said:
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Click to expand...
Click to collapse
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.

bweN diorD said:
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
Click to expand...
Click to collapse
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.

Hakalai said:
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Click to expand...
Click to collapse
hmm, ok, im guessing it would have said that normally, when not broken. all the command does is try to release it past where its stuck. it doesnt actually flash, lock, unlock, or change anything.
imo, this seems good, because now we know fastboot is working.
i own lg devices, but not your specific device. i would hate to give you some bad advice and make your tablet broken more, but if it were me in this situation, i would try to flash the factory KK firmware you used to downgrade with odin or however you did it. hopefully, that will clean everything up and let it boot properly.
if for whatever reason you cant do that, we could try extracting the factory file, and just flashing recovery and system, those should be the only things that got changed putting on twrp and cm normally.

Sorry, I have the serious proplem wtih my LG pad V400, I rooted it and using <LG Flash Tool 2014> with <V40010c_00.kdz> to downgrate the firmware but their is error then my LG pad stuck in fastboot menu as with just turn off, restart and restart bootloader. if i seclect one one them the tablet just logged again the fastboot menu
it stuck on the fastboot menu and i cannot do nay think with it. I can restart with factory restore mode but when select yes to restore, it will restart and log in fastboot menu again.
I downloaded adb and fastboot program and put in one folder <Minimal ADB and Fastboot> in C:\Program Files (x86)\Minimal ADB and Fastboot
I dont have recovery image so i download file <cm-13.0-20160421-NIGHTLY-v400-recovery.img> form your link to download TWRP file
move it to folder of fastboot programe and changed its name to <recovery.img>
I turn on the tablet and it waited at fastboot menu
when i run the command <fasboot flash recovery recovery.img> and they said some thing wrong like in picture
please help me

Weird problem with my tf300t

Hello there. I am writing here because my tablet which i didn't use for a long long (lend it to my grandma) time caught my attention. I wanted to install some custom rom and recovery but when i go to bootloader, I can see 4 things to choose and when i choose RCK or USB the device stops working. Adb works perfectly fine but fastboot not at all. Im attaching photos of what it looks like and all system info You may need in order to help me. On boot logo it says that the device is unlocked.
Also, Happy Easter

Deviss said:
Hello there. I am writing here because my tablet which i didn't use for a long long (lend it to my grandma) time caught my attention. I wanted to install some custom rom and recovery but when i go to bootloader, I can see 4 things to choose and when i choose RCK or USB the device stops working. Adb works perfectly fine but fastboot not at all. Im attaching photos of what it looks like and all system info You may need in order to help me. On boot logo it says that the device is unlocked.
Also, Happy Easter
Click to expand...
Click to collapse
First of all you should get your tablet on the last Asus update on Android 4.2 Jell Bean. That means you must download the latest Asus firmware for TF 300T from here:
https://www.asus.com/Tablets/ASUS_Transformer_Pad_TF300T/HelpDesk_BIOS/
Generally you may install it manually. After download unzip the zip file once. Then copy the "blob" file into the intern memory of your tablet. After rebooting the device the firmware is gonna to being installed automatically. This might be the first and most important step to prepare your device for flashing a custom rom of your choice.

Thanks for response,but after rebooting the device with blob file inserted, system launched normally and no updates procceded :/
Edit: now that I think of that, it looks like i don't have recovery because when i enter it from bootloader all i see is red triangle with "dead robot"

Deviss said:
Thanks for response,but after rebooting the device with blob file inserted, system launched normally and no updates procceded :/
Click to expand...
Click to collapse
Go ahead and try to flash the blob file.
If you don't have, you need „Minimal ADB and Fastboot“, download it from the Internet. The USB driver must be installed on your PC.
Install "Minimal ADB and Fastboot". Then put the blob file in your fastboot folder. Open cmd on your PC as administrator and type: "-i 0x0B05 flash staging blob" without " ".
Let it run. It seems that nothing happens. The whole thing can take up to 20 Minutes, so just stay calm and wait till it’s finished.

Well that's not gonna happen since as i stated in the topic i don't have access to the fastboot option(USB Icon in bootloader). when i pick the option from bootloader it just freezes and and stays like that frever untill i manually pinch the reset button with a needle, also the device is not listed in the command "fastboot devices". I will try running fastboot flash overnight, maybe then it will work...

Deviss said:
Well that's not gonna happen since as i stated in the topic i don't have access to the fastboot option(USB Icon in bootloader). when i pick the option from bootloader it just freezes and and stays like that frever untill i manually pinch the reset button with a needle, also the device is not listed in the command "fastboot devices". I will try running fastboot flash overnight, maybe then it will work...
Click to expand...
Click to collapse
I'm sorry, but I cannot understand what you are doing with the icons.
When you start your device with "power on" and "volume down" together you will reach the fastboot modus automatically shown at your third screenshot. That's it!
There is no need to touch any icon. Keep in mind never ever use the wipe icon. In that case your device gets bricked harshly.