Database Info

My tablet works only in fastboot mode and APX, nothing else. HELP

My tablet works only in fastboot mode and APX, nothing else. Was on 4.1.1.
Does anyone can help me to unbrick?
thank you.
I can donate your help

tyla777 said:
My tablet works only in fastboot mode and APX, nothing else. Was on 4.1.1.
Does anyone can help me to unbrick?
thank you.
I can donate your help
Click to expand...
Click to collapse
First you need to provide more info (i.e. did you tried to flash something before this issue occured?, your device is unlocked?) and maybe we can help you.

Yes tablet is unlocked.
i flashed it with CWM Recovery and problems started.
Can't mount anything....
Then i used commands:
fastboot erase boot
fastboot erase recovery
Now then i trying to boot , it brings me error
http://youtu.be/P19Y3Apmbac

tyla777 said:
Yes tablet is unlocked.
i flashed it with CWM Recovery and problems started.
Can't mount anything....
Then i used commands:
fastboot erase boot
fastboot erase recovery
Now then i trying to boot , it brings me error
http://youtu.be/P19Y3Apmbac
Click to expand...
Click to collapse
I can't read the error from that video but i think you should flash a boot.img via fastboot and then flash CWM or TWRP recovery the same vai (via fastboot). BTW you have to use a boot.img from a JB rom.

Pretoriano80 said:
I can't read the error from that video but i think you should flash a boot.img via fastboot and then flash CWM or TWRP recovery the same vai (via fastboot). BTW you have to use a boot.img from a JB rom.
Click to expand...
Click to collapse
Error is 0x000000000
Where i can get boot.img?
Then i extract blob file, i get 5 blob filesblob.
HEADER – Header stuff (ignore it)
blob.APP – system.img
blob.LNX – boot.img
blob.SOS – recovery.img (e.g. regular boot.img)
blob.EBT – bootloader.bin (ignore)
Do i have to rename blob.LNX to boot.img or i should't ?
Do i need to erase all system boot recovery data?
Thanks.

tyla777 said:
Yes tablet is unlocked.
i flashed it with CWM Recovery and problems started.
Can't mount anything....
Then i used commands:
fastboot erase boot
fastboot erase recovery
Now then i trying to boot , it brings me error
http://youtu.be/P19Y3Apmbac
Click to expand...
Click to collapse
You made the same mistake I made:
http://forum.xda-developers.com/showthread.php?t=2031452
APX means you get to use nvflash, right?
I wish I was on the same boat.

Yes i can use nvflash.
but i can't restore my bootloder
maybe you know what to flash?

tyla777 said:
Yes i can use nvflash.
but i can't restore my bootloder
maybe you know what to flash?
Click to expand...
Click to collapse
What do you mean with "Yes i can use nvflash"? You already used the NvFlash tool and have the backup files or is just the fact that you are able to boot in APX mode?
As for the other question, yes rename the blob files ( blob.LNX - > boot.img) and flash from fastboot (fastboot -i 0x0B05 flash boot boot.img). Make sure your battery is full, just in case.
Try to flash the recovery.img, boot.img and system.img using the abive method.

Pretoriano80 said:
What do you mean with "Yes i can use nvflash"? You already used the NvFlash tool and have the backup files or is just the fact that you are able to boot in APX mode?
As for the other question, yes rename the blob files ( blob.LNX - > boot.img) and flash from fastboot (fastboot -i 0x0B05 flash boot boot.img). Make sure your battery is full, just in case.
Try to flash the recovery.img, boot.img and system.img using the abive method.
Click to expand...
Click to collapse
Just the fact
Flashed recovery boot system didn't helped
maybe someone knows how to flash with nvflash?

tyla777 said:
Just the fact
Flashed recovery boot system didn't helped
maybe someone knows how to flash with nvflash?
Click to expand...
Click to collapse
Being able to boot in APX doesn't mean you can use NvFlash to flash your device.If you never used the NvFlash tool to backup your files (and gain NvFlash access) you won't be able to do it anymore because a 9.4.5.26 or lower bootloader it's needed.
I'm not sure if the follow procedure will work but you could try to flash the complete blob via fastboot (rename the original asus blob to something like " tf700t.blob " , something like this : fastboot -i 0x0B05 flash staging tf700t.blob
Someone please correct me if the " flashing to staging" procedure is different.

Pretoriano80 said:
Being able to boot in APX doesn't mean you can use NvFlash to flash your device.If you never used the NvFlash tool to backup your files (and gain NvFlash access) you won't be able to do it anymore because a 9.4.5.26 or lower bootloader it's needed.
I'm not sure if the follow procedure will work but you could try to flash the complete blob via fastboot (rename the original asus blob to something like " tf700t.blob " , something like this : fastboot -i 0x0B05 flash staging tf700t.blob
Someone please correct me if the " flashing to staging" procedure is different.
Click to expand...
Click to collapse
maybe someone knows thne will be released NVFLASH version that support 10.... ver.

tyla777 said:
maybe someone knows thne will be released NVFLASH version that support 10.... ver.
Click to expand...
Click to collapse
ATM there's no way to do that ,Asus locked the bootloader pretty tight this time.
If you still can't manage to fix your issue i would recommend you an RMA ticket from Asus.

[Q] Softbricked Tf300t

Hi I have been reading a ton in the forums trying to figure out how to fix my tf300t. A few days ago I updated to the newest CM 10.1 nightly and when it restarted it was stuck at the Asus screen. So I have been able to hold vol down button and get to a screen that says
RCK Android [usb symbol] and Wipe Data
I have fastboot access and thought I would try to fix the problem myself by following instructions on another thread
"pyovue - If you have ADB access then unbricking it should be easy as you can push and edit any file on the system with it as well as fastboot? Or can ADB & Fastboot not mount (not just the sdcard) anything? If you don't care what happens to your tablet MB, then try this....
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
Then reboot (this should rid you of your bootloop to recovery and nothing should start)
Then download the stock ASUS Rom (from ASUS, look under Firmware)
Then try sending it with fastboot -i 0x0b05 flash system blob (you will have to extract two zips from the firmware files until you get to a file called "blob" then put it in your fastboot)
I almost guarantee if you have fastboot/adb working there is ALWAYS a way to fix it... only a hardbrick is impossible to fix.
"
I get cannot load 'blob' so I tried
fastboot -i 0x0B05 flash recovery recovery.img
seeing as I already had the recovery.img from when I first unlocked, rooted, and put cm 10.1 on it
please help I have no idea what to do and thank you in advance <3

musicfreak58 said:
Hi I have been reading a ton in the forums trying to figure out how to fix my tf300t. A few days ago I updated to the newest CM 10.1 nightly and when it restarted it was stuck at the Asus screen. So I have been able to hold vol down button and get to a screen that says
RCK Android [usb symbol] and Wipe Data
I have fastboot access and thought I would try to fix the problem myself by following instructions on another thread
"pyovue - If you have ADB access then unbricking it should be easy as you can push and edit any file on the system with it as well as fastboot? Or can ADB & Fastboot not mount (not just the sdcard) anything? If you don't care what happens to your tablet MB, then try this....
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
Then reboot (this should rid you of your bootloop to recovery and nothing should start)
Then download the stock ASUS Rom (from ASUS, look under Firmware)
Then try sending it with fastboot -i 0x0b05 flash system blob (you will have to extract two zips from the firmware files until you get to a file called "blob" then put it in your fastboot)
I almost guarantee if you have fastboot/adb working there is ALWAYS a way to fix it... only a hardbrick is impossible to fix.
"
I get cannot load 'blob' so I tried
fastboot -i 0x0B05 flash recovery recovery.img
seeing as I already had the recovery.img from when I first unlocked, rooted, and put cm 10.1 on it
please help I have no idea what to do and thank you in advance <3
Click to expand...
Click to collapse
What's the question again? If you have fastboot, you can always flash the system blob from your PC. Or you can push the rom (zip) to your internal storage, turn it off and on again. If you select rck on official recovery, it should look for the zip file on its own and proceed to flash it. If you have custom recovery, get to it and flash the same zip file. Make sure you have the right recovery for the rom though. Good luck.

Hi,
and we ansered this kind of prob 2 days ago here: http://forum.xda-developers.com/showthread.php?p=44244313
and yeah - my probs came from an error during cm update.
cheers
-Buster

Buster99 said:
Hi,
and we ansered this kind of prob 2 days ago here: http://forum.xda-developers.com/showthread.php?p=44244313
and yeah - my probs came from an error during cm update.
cheers
-Buster
Click to expand...
Click to collapse
It wouldn't load the blob but i followed that and found that link last night after posting I tried to delete this post but it just allows me to edit
Thanks

tablet only boots into twrp

My TF300T will only boot into TWRP. I also can't access any storage (failed to mount error) and adb sideloading fails everytime so I can't flash the stock rom. I tried using these commands:
adb shell mount -t tmpfs none /sdcard
adb push ROM.zip /sdcard
Which let me reach the .zip file it still failed to flash.
The tablet had Jellybean 4.2.2 installed. The TWRP version is 2.6.3.0.
How do I fix this?

Reboot it into bootloader menu. If holding volume down and power buttons doesn't work try 'adb reboot bootloader' command while tablet in twrp. Then flash rom through fastboot.

Graiden05 said:
Reboot it into bootloader menu. If holding volume down and power buttons doesn't work try 'adb reboot bootloader' command while tablet in twrp. Then flash rom through fastboot.
Click to expand...
Click to collapse
Now I can get to fastboot, but if I try to flash anything the cmd window says it worked but all it really does is freeze the tablet.

dewdrop623 said:
Now I can get to fastboot, but if I try to flash anything the cmd window says it worked but all it really does is freeze the tablet.
Click to expand...
Click to collapse
Did You flash rom or recovery? And does blue progressbar appears?

Graiden05 said:
Did You flash rom or recovery? And does blue progressbar appears?
Click to expand...
Click to collapse
I was able to flash cwm recovery. So now instead of booting into twrm everytime I get stuck on the splash screen. That didn't really change anything
I tried fastboot -i 0x0b05 flash system boot.blob (the .blob file from the stock rom), and I got the blue progress bar then rebooted but I'm still stuck on the first splash screen.

You do it wrong. So if Your last working firmware was 4.2 You need download this rom from asus webpage. Then unzip it twice and You get blob file. Then flash it with 'fastboot -i 0x0b05 flash staging blob' command.

Graiden05 said:
You do it wrong. So if Your last working firmware was 4.2 You need download this rom from asus webpage. Then unzip it twice and You get blob file. Then flash it with 'fastboot -i 0x0b05 flash staging blob' command.
Click to expand...
Click to collapse
Thanks. That worked. However now I'm only back where I started. CWM give can't mount error and can't reach a zip file. ADB sideload doesn't work either(failed to write data 'protocol fault (no status)'). I tried TWRP once and that's the reason I had to post hear in the first place.

dewdrop623 said:
Thanks. That worked. However now I'm only back where I started. CWM give can't mount error and can't reach a zip file. ADB sideload doesn't work either(failed to write data 'protocol fault (no status)'). I tried TWRP once and that's the reason I had to post hear in the first place.
Click to expand...
Click to collapse
Did You try only TWRP v2.6.3.0? I use v2.5.0.0 and its work fine. About CWM: flatline cwm for 4.2 bootloader was created with purpose do nvflash backup, so may be here is the cause of not working others functions.

Graiden05 said:
Did You try only TWRP v2.6.3.0? I use v2.5.0.0 and its work fine. About CWM: flatline cwm for 4.2 bootloader was created with purpose do nvflash backup, so may be here is the cause of not working others functions.
Click to expand...
Click to collapse
Success. Thanks for the help.

[Q] recovery/bootloader issues

after i got my tf700 tablet i unlocked the bootloader and put cwm and cm11 on it, without any problems.
then i tried the same thing on my brothers tf300 i accidentally bricked it, after we bought another one i used the nvflash bricksafe setup on my tf700 so the same thing would not happen to me. then i changed from cwm to philz. later i tried to change the wallpaper in philz and my device froze, so i rebooted and found myself bricked. so i used apx to recover. i got android functionality back but now i have some issues.
1. i cant access recovery, selecting the rck command results in an error: unrecoverable bootloader error (0x00000000)
2. i cant make fastboot flash commands work to reflash a recovery, because the tablet freezes after i hit enter
i have used the "fastboot erase recovery" command too, which seemed to work...
recovery mode usability needs to be restored and possibly a fresh install of the bootloader too.
any help putting it back together either through apx recovery or the android system would be much appriciated!

Did you try to flash the stock blob? Sounds to me like a case for buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2

berndblb said:
Did you try to flash the stock blob? Sounds to me like a case for buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Click to expand...
Click to collapse
Buster99 said:
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
thanks for the instructions but i think i will leave this as a last resort as i would rather not have to redo everything i have already done to my device, i hate starting over

A nandroid would have done the trick
Sometimes you have to learn the hard way...
I'm talking about myself: made a nandroid of my CROMi-X installation before flashing CROMBi-KK and then formatted data - without copying the nandroid to microSD - DOH!
Sent from my K00C using Tapatalk

berndblb said:
A nandroid would have done the trick
Sometimes you have to learn the hard way...
I'm talking about myself: made a nandroid of my CROMi-X installation before flashing CROMBi-KK and then formatted data - without copying the nandroid to microSD - DOH!
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
i have a nandroid, on an external source too,
but if you cant get into recovery there is no way to use (or at lease not one that i know)

kirbyonwarpstar said:
i have a nandroid, on an external source too,
but if you cant get into recovery there is no way to use (or at lease not one that i know)
Click to expand...
Click to collapse
In that case, it's easy:
Flash system blob
Flash custom recovery
Restore nandroid
Sent from my K00C using Tapatalk

bootloader error 0x00000000

Well, what happened is :
that i was trying to root my Transformer tf300t
and i got as far as unlocking the bootloader
so i was having trouble flashing the twrp recovery image
and i think i accidentally erased the stock recovery image
so now my tablet it's not (full bricked) still boots up but doesn't have a recovery image
and now when i boot it into bootloader mode and try to go into RCK it just gives me this
error bootloader unrecoverable 0x0000000 (in red)
how can i flash the stock ROM again if this error ?
anybody ?HELLP

daveSAPIEN said:
error bootloader unrecoverable 0x0000000(in red)
how can i flash the stock ROM again if this error ?
anybody ?HELLP
Click to expand...
Click to collapse
Please try this:
Go to Asus and dl the latest Stock. Unzipp it 2 times. You should have a blob file now in the extracted folder. Put this blob in your fastboot folder.
Open cmd and type:
fastboot -i 0x0B05 flash staging blob
Let it run. It seems that nothing is happening for about 5 Minutes. The whole thing can take up to 20 Minutes, so just stay calm and wait till it’s finished.
Now you should be back to full Stock with Stock recovery. Good luck!

THanks !
ebonit said:
Please try this:
Go to Asus and dl the latest Stock. Unzipp it 2 times. You should have a blob file now in the extracted folder. Put this blob in your fastboot folder.
Open cmd and type:
fastboot -i 0x0B05 flash staging blob
Let it run. It seems that nothing is happening for about 5 Minutes. The whole thing can take up to 20 Minutes, so just stay calm and wait till it’s finished.
Now you should be back to full Stock with Stock recovery. Good luck!
Click to expand...
Click to collapse
Thank you ... it worked i think
but i used a little different command line i used :
fastboot -i 0x0B05 flash system c:\adb\recovery.blob
now i'm still having problems trying to flash custom recovery i want to root the Tablet
what the problem seems to be for me is that i boot the the tablet (tf330t transformer 4.2.1 JB )
to fastboot mode then i get the 3 choices (RCK, Android,Wipe Data)
but when i try to flash the TWRP recovery img with Fastboot it always gives me an error saying (error cannot load img file)
is there anyway to fix this ? and does this root the tablet?

Dear daveSAPIEN can you give us more information about the file used during the flash , actually am facing the same problem as you but nothing seems to work
thank you