Database Info

Stock Recovery zip

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.

[Q] HELP - NVFlash Bootloader failed

I'm on ICS and never upgraded to JB. I've just unlocked my bootloader so I can do NVFlash Backup and start flashing ROM's.
I unlocked without any problems. I've rebooted into bootloader and selected the USB icon. My computer found the drivers and correctly identified as 'ASUS Android Bootloader Interface'.
From the guide http://androidroot.mobi/pages/tegra3-guide-nvflash/
I ran the command
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
I got the following output from my Windows console
Code:
sending 'staging' (1002KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 7.935s
On my tablet appears
Code:
Failed to process command download:000fa98d error(0x120003)
Also the device now appears in my windows device manager with the following error
Code:
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
I've not rebooted my tablet for fear of this question...
Have I bricked my tablet?
P.S. At this point I haven't attempted to reboot my device because I'm worried it might never come back.

So I've been crawling around the internet for anyone else who's had this problem and the only person with a similar issue is
http://forum.xda-developers.com/showpost.php?p=32222050&postcount=110
So since my OP, I've removed the USB cable from my laptop, plugged it back in and I can see my TF300.
When I run
Code:
fastboot devices
I get
Code:
00000 fastboot
Which I assume means my computer can see it?
At the moment I've still not rebooted. From what I've read Staging partition is applied at boot, which I assume means no changes have been made yet?
Because my transfer failed, will anything be applied from Staging on next reboot? Or should I run a command now to prevent any changes?
Thanks

Any help on this will be much appreciated.
Just to clarify, I've still not rebooted my device since I attempted the flash and seem to have access to Fastboot. I don't want to reboot unless I know it's safe to do so.
Thanks!

I thought this morning I'd try and change my drivers and run the command again.
I thought first I'd use Universal Naked Drivers, when I select the INF 'android_winusb.inf' file I get two options both called 'Asus Fastboot Interface'.
If I select either of these I get the following error
The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tempered with.
The other option I do seem to have is under manufacturer 'Google, Inc.' I've got 'Android Bootloader Interface'. Is that any better?

So I eventually got the Universal Naked Drivers to work (after disabling Driver signature enforce from Windows boot options) and I could see my device in device manager and from 'fastboot devices'.
So I re-ran
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
And this time it also failed with another message. In my console showed
Code:
sending 'staging' (1002 KB)...
FAILED (remote: (AccessDenied))
finished. total time: 0.014s
And my TF300 displayed the line
Code:
Failed to process command download:000fa98d error(0x30010)
But this time, I can no longer see my device from device manager or 'bootloader devices'. Windows doesn't even make the 'device inserted' sound when I plug it in.

So I finally gave in and rebooted my tablet.
To my great relief it booted successfully!
I was so nervous about doing this before hand and this experience has really knocked my confidence down.
What I'd like to know is: Is it down to the driver I'm using that I'm getting my original error? Is it a problem with my PC or my tablet?
Thanks

psjw12 said:
So I finally gave in and rebooted my tablet.
To my great relief it booted successfully!
I was so nervous about doing this before hand and this experience has really knocked my confidence down.
What I'd like to know is: Is it down to the driver I'm using that I'm getting my original error? Is it a problem with my PC or my tablet?
Thanks
Click to expand...
Click to collapse
I've seen posts where problems similar to this have been solved by just using a different USB port, one at the back if you're using a PC. At least it might be worth a try.

daws said:
I've seen posts where problems similar to this have been solved by just using a different USB port, one at the back if you're using a PC. At least it might be worth a try.
Click to expand...
Click to collapse
I'll give that a try. I'm also gonna try updating my Android toolkit and using the Android Fastboot drivers (rather than the ASUS ones).
I'll let you know how I get on with that.

psjw12 said:
I'll give that a try. I'm also gonna try updating my Android toolkit and using the Android Fastboot drivers (rather than the ASUS ones).
I'll let you know how I get on with that.
Click to expand...
Click to collapse
Did you have luck with your device? The thing is i have a similiar problem with my device. The only difference might be that my mainboard has been exchanged during an RMA. But apart from that I also have a unlocked ics bootloader and when tried:
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
everything seemed to be ok, because i got the following message:
Code:
sending 'staging' (1002 KB)...
OKAY [ 0.257s]
writing 'staging'...
OKAY [ 0.293s]
finished. total time: 0.550s
However if I check for devices afterwards, using:
Code:
fastboot devices
I get the following wierd message:
Code:
???????????? fastboot
Luckily when I restart the device it is like nothing happend. It still says "The device is unlocked" on the top left corner of the screen and the fastboot commands work as usual. I really appreciate your help.
Jan

Claudii said:
Did you have luck with your device? The thing is i have a similiar problem with my device. The only difference might be that my mainboard has been exchanged during an RMA. But apart from that I also have a unlocked ics bootloader and when tried:
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
everything seemed to be ok, because i got the following message:
Code:
sending 'staging' (1002 KB)...
OKAY [ 0.257s]
writing 'staging'...
OKAY [ 0.293s]
finished. total time: 0.550s
However if I check for devices afterwards, using:
Code:
fastboot devices
I get the following wierd message:
Code:
???????????? fastboot
Luckily when I restart the device it is like nothing happend. It still says "The device is unlocked" on the top left corner of the screen and the fastboot commands work as usual. I really appreciate your help.
Jan
Click to expand...
Click to collapse
That's odd, it's like Fastboot says image was deployed but then it doesn't apply the change. Thank goodness there's a staging partition on Asus! I also had the problem of the device disconnecting whilst trying to flash and then not showing up.
How does the tablet show up in your device manager? As 'Asus Fastboot' or 'Android Fastboot'? Mine was ASUS and I was thinking of trying the Android driver instead.
I've not tried to flash mine again since trying, I'm going to wait for an appropriate time for me to have a heart attack if it all goes wrong
Edit: The next command it wants to issue is
Code:
fastboot -i 0x0b05 reboot
I wonder if that what makes it commit the changes? Hopefully someone can answer that for me.

[Q] [SOLVED] Cannot Flash Recovery/Root

Hey all,
I bought a Factor Refurbished TF700t with the intention of getting CROM-i flashed on it. I was able to get it unlocked with no issue, however, whenever I try to flash twrp to it, I get this.
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6948 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
and sometimes this
PS E:\Program Files (x86)\Minimal ADB and Fastboot> fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.009s
I am running the naked USB drivers, usb debugging is enabled and rooting with motochopper does not work. I also downgraded to the 10.6.1.14.8 build. It should be noted that I was on 10.6.1.14.10 build when I did the unlocking, but that didn't seem to effect anything. Lastly, fastboot does see the device as I get this output:
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot devices
015d2d43004bfc01 fastboot
My fear is this may be an issue with the factory referb I got, but hopfully that's not the case! If anyone can help me, it would be greatly appreciated!
Edit: Solved! The answer was to do it in Linux. Grab a distro of Mint and get to it! =D

Highsight said:
Hey all,
I bought a Factor Refurbished TF700t with the intention of getting CROM-i flashed on it. I was able to get it unlocked with no issue, however, whenever I try to flash twrp to it, I get this.
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6948 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
and sometimes this
PS E:\Program Files (x86)\Minimal ADB and Fastboot> fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.009s
I am running the naked USB drivers, usb debugging is enabled and rooting with motochopper does not work. I also downgraded to the 10.6.1.14.8 build. It should be noted that I was on 10.6.1.14.10 build when I did the unlocking, but that didn't seem to effect anything. Lastly, fastboot does see the device as I get this output:
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot devices
015d2d43004bfc01 fastboot
My fear is this may be an issue with the factory referb I got, but hopfully that's not the case! If anyone can help me, it would be greatly appreciated!
Click to expand...
Click to collapse
It looks like that you have a bad download. Check the md5 to ensure that it is not corrupted..:fingers-crossed:

LetMeKnow said:
It looks like that you have a bad download. Check the md5 to ensure that it is not corrupted..:fingers-crossed:
Click to expand...
Click to collapse
Yeah - and also: which TWRP version are you trying to flash?

LetMeKnow said:
It looks like that you have a bad download. Check the md5 to ensure that it is not corrupted..:fingers-crossed:
Click to expand...
Click to collapse
Can confirm, the hash is correct. Confirmed using the MD5 Check Util.
berndblb said:
Yeah - and also: which TWRP version are you trying to flash?
Click to expand...
Click to collapse
I've tried multiple different ones with the same result sadly, but mostly I've tried 2.7.0.0.

Highsight said:
Can confirm, the hash is correct. Confirmed using the MD5 Check Util.
I've tried multiple different ones with the same result sadly, but mostly I've tried 2.7.0.0.
Click to expand...
Click to collapse
Try a different USB port...
Try to wait to plug your device into your PC until your tablet is already in fastboot...
Let me know if this helps... Thx lj

lj50036 said:
Try a different USB port...
Try to wait to plug your device into your PC until your tablet is already in fastboot...
Let me know if this helps... Thx lj
Click to expand...
Click to collapse
Still no luck. I've been at this for a couple days now. I've tried different cords (one from my dad who also has a TF700 and also my old TF100 cords) and different USB ports, same result for all of them. I read somewhere about USB 3.0 possibly causing problems, is this true? I tried my USB 2.0 ports, but the result seemed the same.

Try "fastboot flash staging twrp.blob", maybe this works better. If not, it can't break anything.

_that said:
Try "fastboot flash staging twrp.blob", maybe this works better. If not, it can't break anything.
Click to expand...
Click to collapse
Same result:
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot flash staging twrp.blob
sending 'staging' (6292 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.007s

OK, then I can only think of "try a different operating system (Linux)" or "try a different computer".

Highsight said:
Can confirm, the hash is correct. Confirmed using the MD5 Check Util.
Click to expand...
Click to collapse
So your file is good..
Highsight said:
I've tried multiple different ones with the same result sadly, but mostly I've tried 2.7.0.0.
Click to expand...
Click to collapse
I just flashed twrp v2.7 yesterday and went fast and done.. So the v2.7 is working on the tf700. I think that this might be causing the problem.
Copy your fastboot folder and put it here c:\platform_tools> fastboot -i 0x0B05 flash recovery twrp.blob. I think that android is a unix/linux base so they don't like special characters which means no "space".
Please try that and report back for other users have the same issue, thanks..

LetMeKnow said:
So your file is good..
I just flashed twrp v2.7 yesterday and went fast and done.. So the v2.7 is working on the tf700. I think that this might be causing the problem.
Copy your fastboot folder and put it here c:\platform_tools> fastboot -i 0x0B05 flash recovery twrp.blob. I think that android is a unix/linux base so they don't like special characters which means no "space".
Please try that and report back for other users have the same issue, thanks..
Click to expand...
Click to collapse
Same results...
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.018s
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
C:\platform-tools>
I'm going to try sterilizing my drivers and installing the naked ones again.

I just have to ask.. Your bootloader is unlocked yes ???

Highsight said:
Same results...
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.018s
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
C:\platform-tools>
I'm going to try sterilizing my drivers and installing the naked ones again.
Click to expand...
Click to collapse
I am sorry for a stupid question but do you see "the device is unlocked" in the upper left corner?
Update: Oops, I am slower than you, @lj50036.

lj50036 said:
I just have to ask.. Your bootloader is unlocked yes ???
Click to expand...
Click to collapse
Supposdly.
Whenever I boot the device it says right on the top left "Device is Unlocked".
When going into the bootloader it says the following on the top left.
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.8-20130514" A03
Starting Fastboot USB download protocol"

LetMeKnow said:
I am sorry for a stupid question but do you see "the device is unlocked" in the upper left corner?
Click to expand...
Click to collapse
Beat you too It.. @LetMeKnow
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
Highsight said:
Supposdly.
Whenever I boot the device it says right on the top left "Device is Unlocked".
When going into the bootloader it says the following on the top left.
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.8-20130514" A03
Starting Fastboot USB download protocol"
Click to expand...
Click to collapse
Yes I agree with @_that.... New OS 'Linux' Thats what I would try...

lj50036 said:
Beat you too It.. @LetMeKnow
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
Yes I agree with @_that.... New OS 'Linux' Thats what I would try...
Click to expand...
Click to collapse
Lemme see what I can do about setting up a dual-boot for my computer and trying on that. To be honest I'm not great with Linux, especially when it comes to drivers, but I'll see what I can do...

Highsight said:
Lemme see what I can do about setting up a dual-boot for my computer and trying on that. To be honest I'm not great with Linux, especially when it comes to drivers, but I'll see what I can do...
Click to expand...
Click to collapse
O there are no drivers....:good: At least not for your android devices...
I would recommend Mint 16... Here is a link
Mint Download Page
Go for cinnamon desktop....
Shoot me a email if you need any help at all... There is an option to shoot me an email on my user page.....

lj50036 said:
O there are no driver....:good:
I would recommend Mint 16... Here is a link
Mint Download Page
Click to expand...
Click to collapse
Well that's pretty sweet. I assume a live USB will do?

Highsight said:
Supposdly.
Whenever I boot the device it says right on the top left "Device is Unlocked".
When going into the bootloader it says the following on the top left.
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.8-20130514" A03
Starting Fastboot USB download protocol"
Click to expand...
Click to collapse
Everything is looking good and you said that your device is communicating with the fastboot command "fastboot devices" with a return of your device serial number. I don't know why that it refuses to write to your recovery partition. Maybe there are some bad blocks in your partition but you just reinstall the stock firmware. I am sorry that I don't have a clue what is going on...

Highsight said:
Well that's pretty sweet. I assume a live USB will do?
Click to expand...
Click to collapse
It will but I would install it native to a hard drive, as we are talking about a 400 dollar tablet.. Your call :fingers-crossed:

./fastboot flash revovery fails with "partition table doesn't exist"

Can any admin move this to Q&A pleas? Sorry; I was in the wrong window in my browser.
Hi @all,
I just tried to follow the unlock procedure for my new Nexus5.
The first step (oem unlock) ran fine. The device was rebooted - it took a while. After reboot was complete the system was shut down and rebooted into bootloader (USB debugging switched on!)
Situation now: (all done as root)
d780:~/adb_fastboot # ./fastboot devices
xxxxxxxxxxxxxxx fastboot
d780:~/adb_fastboot # ./fastboot flash revovery openrecovery-twrp-2.7.1.1-hammerhead.img
sending 'revovery' (13586 KB)...
OKAY [ 0.955s]
writing 'revovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.135s
And whatever I try it refuses to flash this recovery. md5sum on recovery image is checked and fine.
I'm searching since more than 2 hours in the network but I could not find any tip to do the trick.
What is going wrong here??
Thanks in advance

wudelbrumpf said:
Can any admin move this to Q&A pleas? Sorry; I was in the wrong window in my browser.
Hi @all,
I just tried to follow the unlock procedure for my new Nexus5.
The first step (oem unlock) ran fine. The device was rebooted - it took a while. After reboot was complete the system was shut down and rebooted into bootloader (USB debugging switched on!)
Situation now: (all done as root)
d780:~/adb_fastboot # ./fastboot devices
xxxxxxxxxxxxxxx fastboot
d780:~/adb_fastboot # ./fastboot flash revovery openrecovery-twrp-2.7.1.1-hammerhead.img
sending 'revovery' (13586 KB)...
OKAY [ 0.955s]
writing 'revovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.135s
And whatever I try it refuses to flash this recovery. md5sum on recovery image is checked and fine.
I'm searching since more than 2 hours in the network but I could not find any tip to do the trick.
What is going wrong here??
Thanks in advance
Click to expand...
Click to collapse
You have written the spelling of recovery wrong
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-hammerhead.img

Hehe. revovery
Sent from my Nexus 5 using Tapatalk

Problem is sitting in front of the screen (as usual)
Don't laugh
I read this at least 10 times and I did NOT see this! Shame on me.
FIXED

Haha. I was wracking my brain trying to see what could have been wrong.

This made me laugh hard lmao. Atleast you got it fixed up though

Nexus 5 and Android 6.0 Fastboot Issue

Hi all
I finally received my Nexus 5 back from LG, which said that they replaced the battery and other parts to address my issue (the original thread can be found at the link below).
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-various-issues-t3212261
This being said, I now want to flash Android 6.0 on my Nexus 5 and start fresh. This is the tutorial that I'm following, and that I followed when flashing Android 6.0 on my Nexus 5 prior to sending it to LG.
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
However it looks like it's not working anymore. On Step 8, the fastboot erase boot command returns me the following:
Code:
c:\adb>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
Anyone knows what that means? I used the ADB Installer 1.3, like I did back then, and even reinstalled it just in case, but to no avail.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
If anyone knows what's happening and can assist me, I would be really grateful! If you need more information, let me know.
Thank you!

Aura. said:
Hi all
I finally received my Nexus 5 back from LG, which said that they replaced the battery and other parts to address my issue (the original thread can be found at the link below).
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-various-issues-t3212261
This being said, I now want to flash Android 6.0 on my Nexus 5 and start fresh. This is the tutorial that I'm following, and that I followed when flashing Android 6.0 on my Nexus 5 prior to sending it to LG.
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
However it looks like it's not working anymore. On Step 8, the fastboot erase boot command returns me the following:
Code:
c:\adb>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
Anyone knows what that means? I used the ADB Installer 1.3, like I did back then, and even reinstalled it just in case, but to no avail.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
If anyone knows what's happening and can assist me, I would be really grateful! If you need more information, let me know.
Thank you!
Click to expand...
Click to collapse
Is your bootloader unlock? That is the first thing that comes to mind when ADB fails to write.
Sent from my SAMSUNG-SM-N910A using Tapatalk

It is, here's the output of the fastboot oem unlock command.
Code:
c:\adb>fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s
Also I can see on my phone LOCK STATE - unlocked

Alright so I restarted my phone in fastboot mode, and the command went through. Weird, now I'm at the step where I need to flash system, recovery, boot, cache, etc. manually, but I keep on getting this message:
Code:
c:\adb>fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.578s]
sending 'system' (1019257 KB)...
FAILED (command write failed (Too many links))
finished. total time: 0.625s
Restarted multiple times, also changed USB port (from USB 3.0 to USB 2.0) but the error persists. Any ideas?

Issue most likely solved. Changed my USB cable for a 2.0 one (I was using the 3.0 that came with the Nexus 5, but it started to be a bit loose), plugged it in a USB 2.0 port, and all the commands went through successfully. If I see that my Nexus behaves weirdly, I'll fastboot it again using the same setup to make sure that everything goes through properly.
This being said, issue solved, you can close this thread if you wish