[Q] help to get back to stock - Transformer TF300T Q&A, Help & Troubleshooting

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

Related

[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

My Asus TF300T Is Completely Dead!

I had upgraded to 4.2 firmware (WW_epad-user-10.6.1.8) using the second method described on http://forum.xda-developers.com/showthread.php?t=2187982. This worked well and everything was working until I messed up today D: I was trying to flash SuperSU using TWRP but it couldn't recognize my Internal SD Card so I thought there might be something wrong with my installation. When I entered the bootloader I noticed the message: Key driver not found.. Booting OS. I don't know what this means. I did not read the first thread in the General section and tried to do a restore using the 4.2 firmware package. I used the "fastboot flash system blob" command and this time everything was messed up. The blue bar that appears on installation is no longer appearing and I have an "unrecoverable bootloader" error. Nothing I did worked! What should I do?? Please provide me some simple steps. I used these commands before flashing system blob...
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This was a very stupid move on my part but I thought this would allow a clean install D: D: Please help!
gee man you completely wiped the sucker, you may be bricked =(. i would start by trying to fastboot flash the patched version of twrp. unless you can boot into twrp already then try to flash the asus package again thru twrp. also, could twrp see your internal sd before you bricked?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
gee man you completely wiped the sucker, you may be bricked =(. i would start by trying to fastboot flash the patched version of twrp. unless you can boot into twrp already then try to flash the asus package again thru twrp. also, could twrp see your internal sd before you bricked?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
No, that is the reason why I wiped everything (stupid move I know)...TWRP was screwed up to begin with. I flashed 2.5 JB version and it couldn't detect my internal SD card. I made sure it was the right model and everything so TWRP messed me up. I don't know how to flash a working version of TWRP since I don't know what version works with 4.2 tf300 firmware.
sonar2854 said:
No, that is the reason why I wiped everything (stupid move I know)...TWRP was screwed up to begin with. I flashed 2.5 JB version and it couldn't detect my internal SD card. I made sure it was the right model and everything so TWRP messed me up. I don't know how to flash a working version of TWRP since I don't know what version works with 4.2 tf300 firmware.
Click to expand...
Click to collapse
there is a modded 2.4.4 version i believe that sees all correctly. the post on how to root and update describe and link it. but being now you flashed the wrong one. you cant mount anything to flash correct one. i think you are s.o.l. i hope iam am wrong. good luck.
kaos420 said:
there is a modded 2.4.4 version i believe that sees all correctly. the post on how to root and update describe and link it. but being now you flashed the wrong one. you cant mount anything to flash correct one. i think you are s.o.l. i hope iam am wrong. good luck.
Click to expand...
Click to collapse
I'm not sure how to flash it...I tried fastboot flash recovery twrp.blob (2.4.4.0 v4.2). It just freezes although the cmd says it was successful
I keep getting a bootloader error (0x0000000) everytime I try and enter RCK, Android, Wipe Data... Is there a way to reinstall the bootloader? WW_epad 10.6.1.8
No mate
As of now there's no solution to that.
Do ppl ever read before they flash? I've never seen as much bricks as I've seen on this device since the new 10.6x.x Asus bootloader... it's a shame
Read read read, understand understand understand, then read more. I almost feel sorry for you guys who are "just flashing away"
FML :crying::crying:
sonar2854 said:
I keep getting a bootloader error (0x0000000) everytime I try and enter RCK, Android, Wipe Data... Is there a way to reinstall the bootloader? WW_epad 10.6.1.8
Click to expand...
Click to collapse
Bump!
I have a couple of questions.
I would like to know about your bootloader (how many icons and which ones) and whether you can still get into twrp.
tobdaryl said:
Bump!
I have a couple of questions.
I would like to know about your bootloader (how many icons and which ones) and whether you can still get into twrp.
Click to expand...
Click to collapse
Okay, so when I press Volume Down + Power, I enter the bootloader. The bootloader has three icons: RCK, Android Logo, Wipe Data. I have no access to TWRP since there is a unrecoverable bootloader error 0x0000000 when I try to enter RCK.
sonar2854 said:
Okay, so when I press Volume Down + Power, I enter the bootloader. The bootloader has three icons: RCK, Android Logo, Wipe Data. I have no access to TWRP since there is a unrecoverable bootloader error 0x0000000 when I try to enter RCK.
Click to expand...
Click to collapse
The odds are slim but let's try a couple of things.
From power off, hold power and volume down, release when you see the icons. You should see the entering fastboot message in the upper left.
fastboot -i 0x0B05 reboot bootloader
if that fails
Power off and use the same procedure.
fastboot reboot bootloader
Tell me the result.
tobdaryl said:
The odds are slim but let's try a couple of things.
From power off, hold power and volume down, release when you see the icons. You should see the entering fastboot message in the upper left.
fastboot -i 0x0B05 reboot bootloader
if that fails
Power off and use the same procedure.
fastboot reboot bootloader
Tell me the result.
Click to expand...
Click to collapse
Okay, I tried both and it doesn't work without adding a hyphen in between reboot and bootloader so reboot-bootloader. Otherwise, with the hyphen added, both work.
sonar2854 said:
Okay, I tried both and it doesn't work without adding a hyphen in between reboot and bootloader so reboot-bootloader. Otherwise, with the hyphen added, both work.
Click to expand...
Click to collapse
Sorry for that mistake. Now try rck and let's see if the bootloader is now accepted. If we are lucky the result has changed.
tobdaryl said:
Sorry for that mistake. Now try rck and let's see if the bootloader is now accepted. If we are lucky the result has changed.
Click to expand...
Click to collapse
Eh...I don't really know how to explain this but this is what happened. Once the bootloader rebooted after entering the CMD command, I pressed volume up to access RCK and there was a "blink" and there is now a green glowing square around the Android Icon. I cannot move the volume up or down (it is frozen on the Android Icon with the green square glowing), so I don't know what that "blink" was. If i try to press volume up now there is the bootloader error again.
sonar2854 said:
Eh...I don't really know how to explain this but this is what happened. Once the bootloader rebooted after entering the CMD command, I pressed volume up to access RCK and there was a "blink" and there is now a green glowing square around the Android Icon. I cannot move the volume up or down (it is frozen on the Android Icon with the green square glowing), so I don't know what that "blink" was. If i try to press volume up now there is the bootloader error again.
Click to expand...
Click to collapse
Download the 10.4.2.20 stock firmware. Unzip once and rename the resulting zip EP201_768_SDUPDATE.zip. Place this on your external sdcard and boot into your bootloader. Volume up on RCK.
tobdaryl said:
Download the 10.4.2.20 stock firmware. Unzip once and rename the resulting zip EP201_768_SDUPDATE.zip. Place this on your external sdcard and boot into your bootloader. Volume up on RCK.
Click to expand...
Click to collapse
Um, I don't have an external SD Card? The only SD Card I have is the Internal Storage
sonar2854 said:
Um, I don't have an external SD Card? The only SD Card I have is the Internal Storage
Click to expand...
Click to collapse
Uh!
Tell me what 2.5 JB version is.
Unzip 10.6.1.8 stock firmware twice and place the blob file into the directory with adb and fastboot. Boot into the bootloader and don't press anything.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
if the command fails try again without -i 0x0B05
tobdaryl said:
Uh!
Tell me what 2.5 JB version is.
Unzip 10.6.1.8 stock firmware twice and place the blob file into the directory with adb and fastboot. Boot into the bootloader and don't press anything.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
if the command fails try again without -i 0x0B05
Click to expand...
Click to collapse
When you say 2.5 JB version...are you talking about TWRP? I don't think TWRP is on the tablet because I can't access it. All I saw was a blink when I pressed volume up on RCK, not TWRP? I have tried flash system blob before I posted here and it did nothing. There is no progress bar when fastboot flashing =/ I think it froze. Yup it froze, just tried to do fastboot reboot-bootloader and it said failed. Also, after the system was done writing, after 2 seconds it said complete so it didn't work.
sonar2854 said:
When you say 2.5 JB version...are you talking about TWRP? I don't think TWRP is on the tablet because I can't access it. All I saw was a blink when I pressed volume up on RCK, not TWRP? I have tried flash system blob before I posted here and it did nothing.
Click to expand...
Click to collapse
I understood about twrp and flashing system blob but I thought we had been able to get stock recovery working instead of twrp.
I 'm sorry that is all I have with no sdcard and no adb.
tobdaryl said:
I understood about twrp and flashing system blob but I thought we had been able to get stock recovery working instead of twrp.
I 'm sorry that is all I have with no sdcard and no adb.
Click to expand...
Click to collapse
I have never used the stock recovery so what is it supposed to look like? Is it that dead Android with the battery because that didn't show up? I will try and get an external sd card tomorrow and try it if you think it might work. I have the 4.2 bootloader so are you sure that I should put Version V10.4.2.20 and recover using that version? Anyways, if it ends up not working, I would just like to say thank you very much for trying.

[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] 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

Categories

Resources