Related
Hi, am looking for the stock recovery file/zip p[ease.
The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.
_that said:
The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.
Click to expand...
Click to collapse
Thanks.
_that said:
The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.
Click to expand...
Click to collapse
I got the firmware and extracted the blob, but I only have fastboot, how do I flash it to get stock recovery back?
I tried this:
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system blob
but nothing works, except I lost /system partition now (I was able to boot Android before). Any help appreciated.
3c said:
I got the firmware and extracted the blob, but I only have fastboot, how do I flash it to get stock recovery back?
I tried this:
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system blob
but nothing works, except I lost /system partition now (I was able to boot Android before). Any help appreciated.
Click to expand...
Click to collapse
Sorry, if that doesn't work I have no more idea how to fix your locked tablet, if you don't have the blob for wheelie and nvflash.
_that said:
Sorry, if that doesn't work I have no more idea how to fix your locked tablet, if you don't have the blob for wheelie and nvflash.
Click to expand...
Click to collapse
Thanks anyway for helping. All I could figure out is that the blob doesn't actually get written to any partition. I've seen some users be successful doing that (what you suggested), so I'll keep trying, maybe reverting the driver. Wondering if using naked driver works well for such method.
In any case, thanks, and I'll post a reply if I can make it work.
3c said:
Thanks anyway for helping. All I could figure out is that the blob doesn't actually get written to any partition. I've seen some users be successful doing that (what you suggested), so I'll keep trying, maybe reverting the driver. Wondering if using naked driver works well for such method.
In any case, thanks, and I'll post a reply if I can make it work.
Click to expand...
Click to collapse
Try this, download stock recovery here http://www.mediafire.com/download.php?pdipp4h2qyqka63
then execute this:
fastboot -i 0x0B05 flash recovery recovery.blob
boot directly into recovery and see if you have recovery back.
buhohitr said:
Try this, download stock recovery here http://www.mediafire.com/download.php?pdipp4h2qyqka63
then execute this:
fastboot -i 0x0B05 flash recovery recovery.blob
boot directly into recovery and see if you have recovery back.
Click to expand...
Click to collapse
Big progress: blob flashed without a glitch. I was happy until I tried to reboot with fastboot: tablet frozen! Reboot, still no recovery
I guess this is it. Got a nice folding brick now! Will try RMA, but from Cambodia not sure it's worth it. Maybe next month when I'm in France.
Can't believe this happened while tablet is locked! Now I hate Asus for this.
3c said:
Big progress: blob flashed without a glitch. I was happy until I tried to reboot with fastboot: tablet frozen! Reboot, still no recovery
I guess this is it. Got a nice folding brick now! Will try RMA, but from Cambodia not sure it's worth it. Maybe next month when I'm in France.
Can't believe this happened while tablet is locked! Now I hate Asus for this.
Click to expand...
Click to collapse
I have asked you to flash the recovery zip, but once done you should boot directly into the recovery, don't boot up. Let me know if you still can fastboot the recovery to your device, but once done, hold the power until device turn off, then right away hold both power button and volume down button to boot into recovery. If you could do this we still have hope. Once in recovery let me know we can proceed to next step.
buhohitr said:
I have asked you to flash the recovery zip, but once done you should boot directly into the recovery, don't boot up. Let me know if you still can fastboot the recovery to your device, but once done, hold the power until device turn off, then right away hold both power button and volume down button to boot into recovery. If you could do this we still have hope. Once in recovery let me know we can proceed to next step.
Click to expand...
Click to collapse
I cannot actually do anything past flashing a blob. the tablet is "frozen" from the moment it enters fastboot, then after flashing any blobs, any further fastboot command are "non-responsive", here is the actual output. At the end the reboot command succeeds but nothing actually happened on the tablet. Still showing the 4 icons (RCK/Android/USB/WIPE) and the top white text. Tried with original Asus driver, with Google driver and now naked driver. no difference, can only be the tablet ;(
C:\Android\android-sdk\platform-tools>fastboot devices
015d2a5088641a08 fastboot
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.blob
sending 'recovery' (6260 KB)...
OKAY [ 1.862s]
writing 'recovery'...
OKAY [ 2.432s]
finished. total time: 4.297s
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.642s
C:\Android\android-sdk\platform-tools>fastboot continue
resuming boot...
FAILED (command write failed (Unknown error))
finished. total time: 0.569s
C:\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
EDIT: Kinda lame I'm sure, but desperate as I am, I tried that too:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 boot recovery.blob
creating boot image...
creating boot image - 6414336 bytes
downloading 'boot.img'...
OKAY [ 1.857s]
booting...
FAILED (remote: ()
finished. total time: 1.861s
I suppose I need a kernel blob... But I couldn't find any stock to flash? Would you also happen to have that handy too?
3c said:
I cannot actually do anything past flashing a blob. the tablet is "frozen" from the moment it enters fastboot, then after flashing any blobs, any further fastboot command are "non-responsive", here is the actual output. At the end the reboot command succeeds but nothing actually happened on the tablet. Still showing the 4 icons (RCK/Android/USB/WIPE) and the top white text. Tried with original Asus driver, with Google driver and now naked driver. no difference, can only be the tablet ;(
C:\Android\android-sdk\platform-tools>fastboot devices
015d2a5088641a08 fastboot
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.blob
sending 'recovery' (6260 KB)...
OKAY [ 1.862s]
writing 'recovery'...
OKAY [ 2.432s]
finished. total time: 4.297s
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.642s
C:\Android\android-sdk\platform-tools>fastboot continue
resuming boot...
FAILED (command write failed (Unknown error))
finished. total time: 0.569s
C:\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
EDIT: Kinda lame I'm sure, but desperate as I am, I tried that too:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 boot recovery.blob
creating boot image...
creating boot image - 6414336 bytes
downloading 'boot.img'...
OKAY [ 1.857s]
booting...
FAILED (remote: ()
finished. total time: 1.861s
I suppose I need a kernel blob... But I couldn't find any stock to flash? Would you also happen to have that handy too?
Click to expand...
Click to collapse
Seems like when you flashed the blob file it wipe out everything. But I tried to boot into recovery so it's a good sign that your tablet is not brick ....yet!!
Here is the stock kernel I created for you http://www.mediafire.com/download.php?16fji3z1nghr6th
fastboot -i 0x0B05 flash boot boot.blob
Possible we may need the bootloader too, but will see.
buhohitr said:
Seems like when you flashed the blob file it wipe out everything. But I tried to boot into recovery so it's a good sign that your tablet is not brick ....yet!!
Here is the stock kernel I created for you http://www.mediafire.com/download.php?16fji3z1nghr6th
fastboot -i 0x0B05 flash boot boot.blob
Possible we may need the bootloader too, but will see.
Click to expand...
Click to collapse
I guess I'm ready for bootloader flashing. Either it bricks it for good or it works or else
Nothing has changed. Just to give you more info, booting RCK, results in booting failed - unrecoverable bootloader error (0x000..).
Booting android: cold-booting linux - signature match. Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
So I tried flashing boot.blob and recovery.blob and the JB update blob to system again, but it hangs at the end, still have to reboot manually. It's like fastboot is not actually flashing anything, writing in below output is abnormally low or could it be that fast!?: It's the same time for boot, recovery of a 800Mb system file!?
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.329s]
sending 'system' (800199 KB)...
OKAY [141.653s]
writing 'system'...
OKAY [ 2.932s]
finished. total time: 146.920s
But the behavior of the bootloader seems quite strange, all this hanging at end of flashing, could this be a corrupted bootloader or worse a corrupted partition table?
3c said:
I guess I'm ready for bootloader flashing. Either it bricks it for good or it works or else
Nothing has changed. Just to give you more info, booting RCK, results in booting failed - unrecoverable bootloader error (0x000..).
Booting android: cold-booting linux - signature match. Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
So I tried flashing boot.blob and recovery.blob and the JB update blob to system again, but it hangs at the end, still have to reboot manually. It's like fastboot is not actually flashing anything, writing in below output is abnormally low or could it be that fast!?: It's the same time for boot, recovery of a 800Mb system file!?
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.329s]
sending 'system' (800199 KB)...
OKAY [141.653s]
writing 'system'...
OKAY [ 2.932s]
finished. total time: 146.920s
But the behavior of the bootloader seems quite strange, all this hanging at end of flashing, could this be a corrupted bootloader or worse a corrupted partition table?
Click to expand...
Click to collapse
Let try the bootloader http://www.mediafire.com/download.php?u6bwnaao6khcdaf
3c said:
Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
Click to expand...
Click to collapse
Define "Windows recognizes the tablet". If you have ADB access, you should be able to recover.
buhohitr said:
Let try the bootloader http://www.mediafire.com/download.php?u6bwnaao6khcdaf
Click to expand...
Click to collapse
Actually how do you flash bootloader? I did this: fastboot -i 0x0B05 flash bootloader loader.blob ?
But anyway, I just read fastboot doesn't flash anything when device is locked! So this piece of s**t doesn't flash but will erase any partition you wish! How's that for a crappy software! I wish I never tried to update to JB!
_that said:
Define "Windows recognizes the tablet". If you have ADB access, you should be able to recover.
Click to expand...
Click to collapse
No ADB, just the name of the tablet appears in Device Manager, sort of the SD card access, but no actual access. I updated the driver manually and was proposed some MTP device. No adb or fastboot when this is available.
Here is the input from another thread: I copy it because I believe the information is very important and identify another way to brick the TF700:
Pretoriano80 said:
ICS bootloader had the fastboot option disabled if the device's bootloader was still locked and the USB icon wasn't showing at all.
With the JB bootloader Asus made the USB icon available even if the device was locked so you can access fastboot mode but you can't flash anything (yes,it doesn't make sense, but this is Asus).
Anyway, if you are able to boot in recovery you should be able to restore you device easily,just follow my guide from the general forum.
Click to expand...
Click to collapse
That's exactly what's happening! I can go in fastboot, but it doesn't flash anything! Though it erase any partition you wish! How smart is that? So I have one thing to say to locked owner: never go in fastboot, ever, it's useless and can actually brick your tablet!!!
I bricked the tablet on my own sure enough, but without this ridiculous fastboot I wouldn't have been able to mess up the tablet in the first place! Sorry for those who love their tablet and Asus, but I find their strategy ridiculous. Except if it's main goal is to make money on RMA.
Thanks Asus for this nice brick!
3c said:
But anyway, I just read fastboot doesn't flash anything when device is locked! So this piece of s**t doesn't flash but will erase any partition you wish!
Click to expand...
Click to collapse
I'd still expect the locked bootloader to flash correctly signed blobs. But who knows what Asus were thinking...
One more idea you can try: Get the 10.4.4.23 dlpkgfile and extract the blob from there.
This blob contains the 10.4.4.23 bootloader, stock recovery and stock kernel, and an orignal Asus signature. My WW version is 13573093 bytes, so it is much smaller than the full firmware blob - try to flash that via fastboot, maybe you are lucky and it works.
_that said:
I'd still expect the locked bootloader to flash correctly signed blobs. But who knows what Asus were thinking...
One more idea you can try: Get the 10.4.4.23 dlpkgfile and extract the blob from there.
This blob contains the 10.4.4.23 bootloader, stock recovery and stock kernel, and an orignal Asus signature. My WW version is 13573093 bytes, so it is much smaller than the full firmware blob - try to flash that via fastboot, maybe you are lucky and it works.
Click to expand...
Click to collapse
Will do, thanks. How would you flash such blob? Onto "staging" or "system"? I've seen users flash the JB update blob to system and be successful. Also seen some posts mentioning staging?
3c said:
Will do, thanks. How would you flash such blob? Onto "staging" or "system"? I've seen users flash the JB update blob to system and be successful. Also seen some posts mentioning staging?
Click to expand...
Click to collapse
I don't really know - all I know is:
- TF700's fastboot implementation only supports blobs, no raw partition images
- blobs are usually always written to the staging partition first, then the contained partition images are flashed to the correct partition(s) by the bootloader
I've seen both variants of the fastboot command, so maybe the target partition doesn't matter when sending blobs. I'd try staging first.
So I unlocked my tf300t and flashed cwm to recovery.
Everything seemed to go fine.
When I would go into cwm it was not able to mount or access any other part of my tab. I figured ok erase/format the recovery partition and try TWRP. So I booted to the bootloader, using fastboot I erased recovery but now whenever I go to flash a new recovery my bootloader either freezes or I get an Unrecoverable bootloader error 0x00000000 (not sure if thats the right amount of zeros but there are no other digits in the error code.) I can access fastboot and adb but it doesn't seem like I can flash using fastboot and I just don't feel comfortable trying with adb. Also I can access fastboot only from the bootloader screen and adb only after I boot into my current rom (stock 4.2.1)
I guess my questions are this:
How can I format my recovery or flash a new recovery?
Were the mount issues I originally encountered going to be solved with a new recovery?
Please help!
Have you tried installing stock rom (from Asus support page) using Fastboot? It should also put stock recovery in your tablet.
Not sure if it is going to work, but it's worth trying though.
1st this is not for the dev section. You should ask questions in the Q&A section.
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 its finished.
Now you should be back to full Stock with Stock recovery.
mikaole said:
1st this is not for the dev section. You should ask questions in the Q&A section.
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 its finished.
Now you should be back to full Stock with Stock recovery.
Click to expand...
Click to collapse
I had this problem too. But on 4.2.1 you can push file blob, and then it's can't run because stock recovery dead.
Were you able to fix the stock recovery issue?
cdguider said:
Were you able to fix the stock recovery issue?
Click to expand...
Click to collapse
Thant i would like to know aswell
Pls
No, I was not. I also have the unrecoverable bootloader error but I have a working device. I downloaded the latest firmware, followed the steps through fastboot and the same thing keeps happening where as soon as you try to enter a command through fastboot the green box stops flashing over rck and even though the cmd prompt window tells you something is going on nothing happens on the tablet end. It freezes. hard reboot and you end up back with a normal working device, no changes and a corrupt bootloader.
lomoski said:
No, I was not. I also have the unrecoverable bootloader error but I have a working device. I downloaded the latest firmware, followed the steps through fastboot and the same thing keeps happening where as soon as you try to enter a command through fastboot the green box stops flashing over rck and even though the cmd prompt window tells you something is going on nothing happens on the tablet end. It freezes. hard reboot and you end up back with a normal working device, no changes and a corrupt bootloader.
Click to expand...
Click to collapse
I have same issue.. has anybody managed to get a fix for this?
I've same problem, how can i fix it?
i've a working device but without recovery mod! I can't flash anything via fastboot because it freezes, i always have "Unrecoverable bootloader error" when press RCK.
Can somebody help me?
Thanks in advance
mister363 said:
I've same problem, how can i fix it?
i've a working device but without recovery mod! I can't flash anything via fastboot because it freezes, i always have "Unrecoverable bootloader error" when press RCK.
Can somebody help me?
Thanks in advance
Click to expand...
Click to collapse
I was having this problem earlier - a new bootloader came out when they went to 4.2, but most of the instructions online don't reflect this. You need an updated recovery image, which usually has the name recovery-jb.img instead of recovery.img. When you're searching make sure the instructions mention 4.2 and jelly bean.
However, I've only managed to get one step further - have now get into clockworkmod recovery, but as with the OP I then couldn't mount anything inside CWM. I tried another instruction set which involved unzipping the ROM and using adb to push over the .blob. This hasn't worked and I have now got a pretty much bricked device - it either bootloops on the asus splash screen, or loads into CWM.
I've found that even when youre in CWM you can type "adb reboot-bootloader" into the terminal, which forces the RCK/android/wipe data page and fastbook to appear. I've also tried to download the latest stock firmware from ASUS, unzipped it to get the stock .blob out and into my fastboot directory, then run "fastboot -i 0x0B05 flash staging blob" in the terminal, as per mikaole's suggestion. This takes a while to push over the 80mb .blob, but after it says it's staged it says "done" then nothing happens and it's still bricked. hmm.
No one's figured this out? I tried flashing the blob file and my system won't boot at all
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
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
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
IT WORKS!!!
Buster99 said:
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
Thank you very much. It works beautifully.
Buster99 said:
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
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
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
Now i' m busy because of my Job. But next week i want try your method.
I hope it work for my device!
Inviato dal mio GT-I9100 con Tapatalk 2
Buster99 said:
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
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
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
Did your tablet seem to freeze after flashing via fastboot? When I push blob, the console shows that it wrote, but then fastboot on the tablet freezes & I have to manually reboot, putting me right back to the drawing board.
Sent from my HTC One using xda app-developers app
Until now my device freezes. Fastboot seem to work but nothing happens. :banghead:
Inviato dal mio GT-I9100 con Tapatalk 2
P05TMAN said:
Did your tablet seem to freeze after flashing via fastboot? When I push blob, the console shows that it wrote, but then fastboot on the tablet freezes & I have to manually reboot, putting me right back to the drawing board.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
nope. do you use the original cable on usb 2.0 and connected to your pc not a usb hub? should work. if not try a diffrent pc - sometimes usb chipsets make problems.
Buster99 said:
nope. do you use the original cable on usb 2.0 and connected to your pc not a usb hub? should work. if not try a diffrent pc - sometimes usb chipsets make problems.
Click to expand...
Click to collapse
I get invalid argument to all of the erase attempts and the minute I try to push the blob the flashing green icon in fastboot mode on the tablet stops. The command windows says the flash went fine but the tablet is unresponsive and must be reset. Infact any fastboot command that pushed something to the tablet causes it to look up ( indicated by the green flashing RCK icon freezing on whatever phase of green it had at the time)
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.975s]
sending 'system' (800935 KB)...
OKAY [134.565s]
writing 'system'...
OKAY [ 2.040s]
finished. total time: 138.583s
I think its time to bin this doorstop and break something new
d3fiant said:
I get invalid argument to all of the erase attempts and the minute I try to push the blob the flashing green icon in fastboot mode on the tablet stops. The command windows says the flash went fine but the tablet is unresponsive and must be reset. Infact any fastboot command that pushed something to the tablet causes it to look up ( indicated by the green flashing RCK icon freezing on whatever phase of green it had at the time)
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.975s]
sending 'system' (800935 KB)...
OKAY [134.565s]
writing 'system'...
OKAY [ 2.040s]
finished. total time: 138.583s
I think its time to bin this doorstop and break something new
Click to expand...
Click to collapse
Mine does this same thing.....think it's done for?
Sent from my HTC One using xda app-developers app
Buster99, your instructions saved my device. I missed erasing /misc even though you put it in the directions and my tablet's back! I owe you.
I am running CM10.1, and wanted to upgrade to the new nightlies, Upon trying to get into recovery, I cannot use goo manager to installed recovery nor reboot to recovery. I did then try to push TWRP to my device using fastboot, that did not seem to work as any time i rebooted to recovery it would do a normal reboot. I can access fastboot, however when I volume up on "RCK" the following error comes up
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB Download protocol
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000).
I do not know if I have everything loaded into my PC correct, drivers, etc. Anyone who can help would be greatly appreciated.
As i am now I can run CM 10.1 just fine, booting and everything, I just cannot get into recovery to upgrade or change roms.
ffalzone23 said:
I am running CM10.1, and wanted to upgrade to the new nightlies, Upon trying to get into recovery, I cannot use goo manager to installed recovery nor reboot to recovery. I did then try to push TWRP to my device using fastboot, that did not seem to work as any time i rebooted to recovery it would do a normal reboot. I can access fastboot, however when I volume up on "RCK" the following error comes up
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB Download protocol
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000).
I do not know if I have everything loaded into my PC correct, drivers, etc. Anyone who can help would be greatly appreciated.
As i am now I can run CM 10.1 just fine, booting and everything, I just cannot get into recovery to upgrade or change roms.
Click to expand...
Click to collapse
I don't know if this method will work on CM. You can give it a shot and report back.
1. Download the Asus firmware from Asus website and extract it once because there is anotherr zip in it.
2. Copy the second zip file to your root directory on your internal sd and reboot
3. If it works, you should see the notification on the lower right corner and click on it. You just follow the instruction to put your device back to the factory bootloader.
Before you use this method, you need to move all your stuff to your computer as a back up because it will wipe everything that you have on your device..
There is another method that you could try if it does not work.. Good luck..:fingers-crossed:
I tried to download the US Firmware from the ASUS site, put it on the root of the internal, then rebooted. Did not see any notification
What is this other method you speak of....
This isn't a huge deal, if I'm stuck on a RC of CM 10.1 I can deal with it. I just like to be up to date and like to reconfigure my tablets and phones from time to time.
On a side note, isn't rom/recovery etc tasks with this tablet very difficult when compared to other tablets/phones?
ffalzone23 said:
I tried to download the US Firmware from the ASUS site, put it on the root of the internal, then rebooted. Did not see any notification
What is this other method you speak of....
This isn't a huge deal, if I'm stuck on a RC of CM 10.1 I can deal with it. I just like to be up to date and like to reconfigure my tablets and phones from time to time.
On a side note, isn't rom/recovery etc tasks with this tablet very difficult when compared to other tablets/phones?
Click to expand...
Click to collapse
Did you unzip it once? You need to have a different firmware version than the one on your system... I will find the other method and link for you..
Thanks Man. I appreciate the help!
ffalzone23 said:
Thanks Man. I appreciate the help!
Click to expand...
Click to collapse
I am still looking for the link. I forgot what it is called... I will post the link here when I find it..
LetMeKnow, Thanks for the update.
Myp hone is a Droid Razr HD, and I know with that phone its possible through the bootloader to flash stock firmwear, is this possible at all with the Transformer tf700t? It would be great to have a simple tool to aid us in getting back to stock to start from square one!
ffalzone23 said:
LetMeKnow, Thanks for the update.
Myp hone is a Droid Razr HD, and I know with that phone its possible through the bootloader to flash stock firmwear, is this possible at all with the Transformer tf700t? It would be great to have a simple tool to aid us in getting back to stock to start from square one!
Click to expand...
Click to collapse
By reading your post again, let me summarize it here. You know how to use fastboot, can't boot to your custom recovery (TWRP), want to flash stock recovery to fix your problem, and have try a few methods to put the stock back but it did not work. You still can get to your bootloader menu. Can you try to use this command to see if you can access to your custom recovery: fastboot boot-recovery
Good luck and get back to you on the link...
this is what came up in command prompt....
C:\android-sdk\platform-tools>fastboot boot-recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
I then did try below. but when I went to reboot, it just stayed in fastboot, so that leads me to believe there is some error there, either my bootloader is screwy or something related. I appreciate your help. At this point if anything can get me back to stock as bought, I dont care if its older versions of the firmware/bootloader/stock recovery, I'll take it from there.
C:\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery-jb.img
sending 'recovery' (7746 KB)...
OKAY [ 3.606s]
writing 'recovery'...
OKAY [ 2.414s]
finished. total time: 6.022s
C:\android-sdk\platform-tools>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.548s
C:\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
ffalzone23 said:
I then did try below. but when I went to reboot, it just stayed in fastboot, so that leads me to believe there is some error there, either my bootloader is screwy or something related. I appreciate your help. At this point if anything can get me back to stock as bought, I dont care if its older versions of the firmware/bootloader/stock recovery, I'll take it from there.
C:\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery-jb.img
sending 'recovery' (7746 KB)...
OKAY [ 3.606s]
writing 'recovery'...
OKAY [ 2.414s]
finished. total time: 6.022s
C:\android-sdk\platform-tools>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.548s
C:\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
Click to expand...
Click to collapse
I have not seen that before, so I don't know what to say...
When I did fastboot TWRP recovery, I used blob file instead of img file. Do you want to download the blob file and try again?
Edit: What version of TWRP did you fastboot? V2.6.3.0 is larger than our partition on the tf700. Therefore, you can not use it..
The .IMG was cwm recovery. I tried that after trying twrp most recent version. 2.6.3.1 I think.
Sent from my XT926 using xda app-developers app
On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts?
At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.
ffalzone23 said:
On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts?
At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.
Click to expand...
Click to collapse
If fastboot doesn't work for you but you have a rooted Android, you can try installing a recovery using the dd method:
Code:
cd wherever/you/downloaded/twrp
su
dd if=openrecovery-twrp-2.6.3.1-tf700t.blob of=/dev/block/mmcblk0p4
then reboot - the bootloader should flash your new recovery with a blue progress bar and reboot again. On the second reboot, hold down volume-down to get to the bootloader menu and try entering RCK again.
ffalzone23 said:
On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts?
At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.
Click to expand...
Click to collapse
You can try _that method. He always have good advices and know what he is talking about.....:good:
Good luck....
_that. What screen do I have my tablet on when I run the dd command prompt ?
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
ffalzone23 said:
_that. What screen do I have my tablet on when I run the dd command prompt ?
Click to expand...
Click to collapse
You mean the expected output? Something similar to:
Code:
15836+1 records in
15836+1 records out
8108136 bytes (8.1 MB) copied, 0.152395 s, 53.2 MB/s
(the above is from my PC - the TF700 is slower)
Or do you mean where you enter those commands? Either via your PC in an adb shell (in this case you must first transfer the file to the TF700 with adb push or other means), or directly on your tablet with a terminal app under Android (I recommend the one from jackpal, search the Play Store)
I was able to get the same output, however when I rebooted after running the last dd code, it did not do anything, just rebooted as normal.
ffalzone23 said:
I was able to get the same output, however when I rebooted after running the last dd code, it did not do anything, just rebooted as normal.
Click to expand...
Click to collapse
What is the response when you use power and volume down buttons?
It takes me into fastboot or boot loader screen w the rck, android cold boot, and wipe data icons
I have an Asus TF300T paperweight!
I started out to root my tablet and load CWM. I unlocked it, install TWRP v2.2.2.2 as I read in a blog with instructions on how to root this tablet. I loaded a CWM ROM, can't remember not which. It didn't load correctly, and kept rebooting. I got into the screen that gives the following four options:
1. RCK
2. Android icon
3. USB icon
4. Wipe data icon
Of course, thinking I would start over and try again, selected Wipe Data. Stupid, I know.
Now, my tablet only boots into TWRP. It won't mount anything; of course, since I Wiped Data, there is nothing to mount. I have tried and searched, to no avail. I can see the tablet in Device Manager, and managed to load the Naked Universal Drivers. Now it shows up in Device Manager as Asus Eee Pad Slider ADB Interface. I can issue the command - adb reboot - and it will reboot, but I can't get it to do anything else meaningful with my meager experience.
Any help would be greatly appreciated. I would like to get this working and give it to my son, as I have already purchased a replacement for myself.
Thank you.
dhastings said:
I have an Asus TF300T paperweight!
I started out to root my tablet and load CWM. I unlocked it, install TWRP v2.2.2.2 as I read in a blog with instructions on how to root this tablet. I loaded a CWM ROM, can't remember not which. It didn't load correctly, and kept rebooting. I got into the screen that gives the following four options:
1. RCK
2. Android icon
3. USB icon
4. Wipe data icon
Of course, thinking I would start over and try again, selected Wipe Data. Stupid, I know.
Now, my tablet only boots into TWRP. It won't mount anything; of course, since I Wiped Data, there is nothing to mount. I have tried and searched, to no avail. I can see the tablet in Device Manager, and managed to load the Naked Universal Drivers. Now it shows up in Device Manager as Asus Eee Pad Slider ADB Interface. I can issue the command - adb reboot - and it will reboot, but I can't get it to do anything else meaningful with my meager experience.
Any help would be greatly appreciated. I would like to get this working and give it to my son, as I have already purchased a replacement for myself.
Thank you.
Click to expand...
Click to collapse
Stop.
Find buster's post and thank him.
And make sure you keep twrp up to date. You have an extremely old versioin which is why you bricked.
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
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
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
sbdags said:
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
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
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
thanks
i was stuck on cwm
could not acess to sd card
followed those steps and there it goes
working again
thanks a lot!
submancm
Hi Guys,
Yesterday I installed the new TWRP 2.7.1.0. and that is when the problems started. Everytime when i loaded TWRP my screen got messed up and i got a split screen (At that time my ROM worked). So I tried to get back to a older TWRP, after a couple of tries i finally installed 2.4.4.0. But then I couldn't acces my internal memory nor my sdcard through TWRP(The ROM still worked fine). So i tried CWM, other TWRP's, still the same issue. To keep the story short, I eventually pressed on the WIPE button in Recovery ... And now I am stuck in TWRP. I can't load any zip files.. Is there any hope?
Tab: TF300T
A small update. After some trial and error i got my rom running again and i can also get in to recovery (Power button + volume down). Now I have erased the old TWRP with "fastboot erase recovery". But now I can't install a new recovery? I tried flashing a recovery and I am getting the messages "sending recovery ok", "writin recovery ok". But i don't see the loading bar on the tab...
I feel lonely here hehe.:laugh:
I resolved the issue and got my tablet running again, with the following steps:
Download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
http://support.asus.com/download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T&os=8
Install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
If the PC doesn't recognize your tab, then try installing the universal naked drivers:
http://forum.xda-developers.com/showthread.php?t=2263822
Guide: http://forum.xda-developers.com/showthread.php?t=2139767
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
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
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
All credits to - Buster http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12