Is there a way to flash to stock using a computer? (similar to Odin for Samsung and RSD for Motorola)
My screen is having issues and cutting out and it is no longer working so I'd like to flash it to stock before I RMA it.
just flash the blob file thats in the stock zip via fastboot
think the right command was
fastboot -i 0x0B05 flash staging blob
this take a long time, so don´t panic cause you see nothing in the fastboot window. Wait till your pad is rebooting.
mikaole said:
just flash the blob file thats in the stock zip via fastboot
think the right command was
fastboot -i 0x0B05 flash staging blob
this take a long time, so don´t panic cause you see nothing in the fastboot window. Wait till your pad is rebooting.
Click to expand...
Click to collapse
where is this blob file
imp3r10 said:
where is this blob file
Click to expand...
Click to collapse
I foudn the blob but now the problem i have is turning off the device and getting it into download mode. (a lot harder without being able to see the screen) is there a way for me to see my screen through my computer?
Buster99 writes about a solution in TF300 thread
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Hope you find it useful!
Best regards
Mackis
Mackis said:
Buster99 writes about a solution in TF300 thread
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Hope you find it useful!
Best regards
Mackis
Click to expand...
Click to collapse
Honestly i don't think it's something new and still require working fastboot (which is impossible if your bootloader is broken) for the recover.
Also i'm a bit confused how they manage to flash the whole blob with " fastboot - i 0x0B05 flash system blob" when afaik the correct command should be : fastboot -i 0x0B05 flash staging blob. (maybe _that could enlight me )
Usually the " system.img" is packed in the full Asus blob and you need to extract it first and then use the " fastboot -i 0x0B05 flash system system.img" command or you can repack the system.img into blob (with blobpack tool) and flash with " fastboot -i 0x0B05 flash system blob" .
Inviato dal mio ASUS Transformer Pad TF700T usando Tapatalk 4
I´m confused to, but as several people testify that it was a solution to make use of their expensive doorstoppers it must be of some value
I dont think the bootloader was totaly corrupt as they could enter fastboot but that after they reset with the paperclip method.... i don´t know if that change anything...
_That maybe can bring some light in this ?
Best regards
Mackis
Pretoriano80 said:
Also i'm a bit confused how they manage to flash the whole blob with " fastboot - i 0x0B05 flash system blob" when afaik the correct command should be : fastboot -i 0x0B05 flash staging blob. (maybe _that could enlight me )
Click to expand...
Click to collapse
I don't know, the Asus (NVidia?) fastboot implementation is a bit strange. Maybe it ignores the partition name given on the command line completely and always uses the one in the blob. At least the guys at androidroot.mobi said that it only flashes blobs, not raw partition images.
Pretoriano80 said:
Usually the " system.img" is packed in the full Asus blob and you need to extract it first and then use the " fastboot -i 0x0B05 flash system system.img" command or you can repack the system.img into blob (with blobpack tool) and flash with " fastboot -i 0x0B05 flash system blob" .
Click to expand...
Click to collapse
Does that really work on a locked device? Repacking or extracting the blob invalidates the cryptographic signature.
_that said:
I don't know, the Asus (NVidia?) fastboot implementation is a bit strange. Maybe it ignores the partition name given on the command line completely and always uses the one in the blob. At least the guys at androidroot.mobi said that it only flashes blobs, not raw partition images.
Does that really work on a locked device? Repacking or extracting the blob invalidates the cryptographic signature.
Click to expand...
Click to collapse
Nah, fastboot on locked device is pretty useless, it looks like it's working but every command sent doesn't do anything.
On unlocked device it worked in the past but i can't tell if if still working cause i didn't tried that in a long time.
I've been using Cromi-X 4.7 since Mid to Late summer for my daily and have had zero issues. Last night however, my TF300 chirped to let me know I had an email, I turned the screen on and then it began bootlooping. I do have access to Recovery, and I've tried wiping and flashing a few other ROMs that I had on my SD card, but they all make it as far as the splash screen then freeze and reboot. So I'm a little confused as to where to go from here.
Recovery: TWRP v2.5.0.0
ww_epad-10.6.1.27.1-20130711
Any advice would be much appreciated. Thanks!
cresco299 said:
I've been using Cromi-X 4.7 since Mid to Late summer for my daily and have had zero issues. Last night however, my TF300 chirped to let me know I had an email, I turned the screen on and then it began bootlooping. I do have access to Recovery, and I've tried wiping and flashing a few other ROMs that I had on my SD card, but they all make it as far as the splash screen then freeze and reboot. So I'm a little confused as to where to go from here.
Recovery: TWRP v2.5.0.0
ww_epad-10.6.1.27.1-20130711
Any advice would be much appreciated. Thanks!
Click to expand...
Click to collapse
If you can use recovery, I suppose you can use fastboot too?
Try the following:
fastboot erase misc
fastboot erase staging
fastboot reboot
If that won't work, look for Buster99's script to erase everything and reflash stock Asus ROM. Fixed issues for a lot of people allowing you a fresh start.
Sent from my TF300T using Tapatalk
f69m said:
If you can use recovery, I suppose you can use fastboot too?
Try the following:
fastboot erase misc
fastboot erase staging
fastboot reboot
If that won't work, look for Buster99's script to erase everything and reflash stock Asus ROM. Fixed issues for a lot of people allowing you a fresh start.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Thankyou! I had to re-educate myself on Fastboot but once that was done I was able to try your suggestions. Your first one did not do the trick, but Buster99's got me most of the way. I had to reflash the TWRP near the end of his process to get it to work for me.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash recovery C:\Users\Jeff\Downloads\twrp-2.5.0.0-JB.blob (THIS IS THE LINE I ADDED)
fastboot -i 0x0B05 flash system C:\Users\Jeff\Documents\WW_epad-user-10.6.1.15.3\blob
fastboot -i 0x0B05 reboot
So maybe my recovery was messed up? At anyrate, it looks like I'm back in action. For anyone who needs to follow how all this was done, there is a good fastboot tutorial here. and here is the link to Buster99's solution.
Thankyou for pointing me in the right direction f69m!
cresco299 said:
Thankyou! I had to re-educate myself on Fastboot but once that was done I was able to try your suggestions. Your first one did not do the trick, but Buster99's got me most of the way. I had to reflash the TWRP near the end of his process to get it to work for me.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash recovery C:\Users\Jeff\Downloads\twrp-2.5.0.0-JB.blob (THIS IS THE LINE I ADDED)
fastboot -i 0x0B05 flash system C:\Users\Jeff\Documents\WW_epad-user-10.6.1.15.3\blob
fastboot -i 0x0B05 reboot
So maybe my recovery was messed up? At anyrate, it looks like I'm back in action. For anyone who needs to follow how all this was done, there is a good fastboot tutorial here. and here is the link to Buster99's solution.
Thankyou for pointing me in the right direction f69m!
Click to expand...
Click to collapse
Oops, careful!
You are using the wrong recovery.
For the bootloaders coming with 10.6.* ROMs you need to use TWRP -42.
Don't use -jb, that is for the older 10.4.* bootloaders.
Sent from my TF300T using Tapatalk
f69m said:
Oops, careful!
You are using the wrong recovery.
For the bootloaders coming with 10.6.* ROMs you need to use TWRP -42.
Don't use -jb, that is for the older 10.4.* bootloaders.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
That would explain why I had to reinstall an updated TWRP to access recovery. I know just enough to make my self dangerous
Thank you again.
Problem: The TF700 is reboot cycling without ever getting further than the initial ASUS logo. The recovery is not getting installed from SDCARD. I tried with US_epad-user-10.6.1.14.10.zip and WW_epad-user-10.6.1.14.10.zip (I don't know the SKU), renamed to EP201_768_SDUPDATE.zip on the root of an 8GB SDCARD formatted with vfat.
History: I live in Germany and got a FT700 from a friend that bought it in the USA. He had power issues but thought it is a software problem and it seems he somehow bricked it. If I can repair it, I can keep it
I was able to build a power charger (yes, 15V over a USB cable...) from an old notebook charger and could successfully charge the tablet and the keyboard.
Messages: Pressing Power-Vol when booting ->
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801-20130801" A03
Key driver not found.. Booting OS
Starting Fastboot USB download protocol
Then three buttons appear in the screens center: RCK, android, WIPE DATA. I can move with Volume around and select. When I select RCK it writes:
Booting Recovery kernel image
Signature Match. (with both SKU versions)
The RCK button stops to flash, but no android bot or a progress bar ever appears
I can use fastboot over USB from Linux. I can run everything described here: http://forum.xda-developers.com/showthread.php?t=2538028 except it will not install a custom boot loader - because it's locked :crying:
Any idea how I can proceed? I would so much love to use this tablet! I am fluent in Linux command line and I'm willing to try desperate measures. Any help greatly appreciated!
dan54321 said:
I can use fastboot over USB from Linux. I can run everything described here: http://forum.xda-developers.com/showthread.php?t=2538028 except it will not install a custom boot loader - because it's locked :crying:
Any idea how I can proceed?
Click to expand...
Click to collapse
Have you tried to select "wipe data" and see if Android boots then?
wait... have you run any commands like "fastboot erase recovery" before? if yes, the above might hard brick your tablet.
If that doesn't work, the next idea would be to try to install a full firmware via fastboot.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
_that said:
Have you tried to select "wipe data" and see if Android boots then?
If that doesn't work, the next idea would be to try to install a full firmware via fastboot.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Can you use fastboot on a locked bootloader?
berndblb said:
Can you use fastboot on a locked bootloader?
Click to expand...
Click to collapse
Yes, the fastboot is a part of the bootloader but the blob has to be signed...
Hey
Thank you for helping me
_that said:
Have you tried to select "wipe data" and see if Android boots then?
Click to expand...
Click to collapse
I actually did that - nothing changed.
_that said:
wait... have you run any commands like "fastboot erase recovery" before? if yes, the above might hard brick your tablet.
Click to expand...
Click to collapse
I did run "fastboot erase recovery", because I thought the recovery partition was corrupted, because the RCK method didn't work. I was hoping to install a new recovery...
_that said:
If that doesn't work, the next idea would be to try to install a full firmware via fastboot.
Click to expand...
Click to collapse
Ok - how do I do that?
I pushed the "blob" from the US_epad-user-10.6.1.14.10.zip with "fastboot -i 0x0B05 flash system boot.blob", but it didn't change anything. I got an "InvalidState" only, when I tried to write the bootloader (I guess because it's locked).
dan54321 said:
I pushed the "blob" from the US_epad-user-10.6.1.14.10.zip with "fastboot -i 0x0B05 flash system boot.blob", but it didn't change anything. I got an "InvalidState" only, when I tried to write the bootloader (I guess because it's locked).
Click to expand...
Click to collapse
I think some user already found out last year the the locked bootloader will happily erase partitions, but then fail to flash the blob, even if it is signed. Sorry, no other ideas.
dan54321 said:
I pushed the "blob" from the US_epad-user-10.6.1.14.10.zip with "fastboot -i 0x0B05 flash system boot.blob", but it didn't change anything. I got an "InvalidState" only, when I tried to write the bootloader (I guess because it's locked).
Click to expand...
Click to collapse
Where did you get the boot.blob? In the original Asus firmware zip, there is only a blob file. Even if you unpack the blob file, these are the dot files after unpacking the blob: .APP, .EBT, .LNX, .PT, .SOS. Are you sure that you have the right blob file for the stock ROM?
_that is very a knowledgeable person. If he said that he is out of idea, your chances are very low...
Good luck....:fingers-crossed:
LetMeKnow said:
Where did you get the boot.blob? In the original Asus firmware zip, there is only a blob file. Even if you unpack the blob file, these are the dot files after unpacking the blob: .APP, .EBT, .LNX, .PT, .SOS. Are you sure that you have the right blob file for the stock ROM?
_that is very a knowledgeable person. If he said that he is out of idea, your chances are very low...
Good luck....:fingers-crossed:
Click to expand...
Click to collapse
boot.blob sounds like a kernel file to me.....
dan54321 said:
I pushed the "blob" from the US_epad-user-10.6.1.14.10.zip with "fastboot -i 0x0B05 flash system boot.blob", but it didn't change anything. I got an "InvalidState" only, when I tried to write the bootloader (I guess because it's locked).
Click to expand...
Click to collapse
The last part of the fastboot flash command has to match whatever the file you want to flash is named.
If the extracted system blob is named "blob" without an extension, the command would be 'fastboot -i 0x0B05 flash system blob'
If it is named blob.blob the command would be 'fastboot -i 0x0B05 flash system blob.blob'
etc.
Is the blob file you extracted actually named boot.blob?
You can also try 'fastboot -i 0x0B05 flash staging blob' followed by a reboot.
Somebody correct me if I'm wrong please....
berndblb said:
The last part of the fastboot flash command has to match whatever the file you want to flash is named.
If the extracted system blob is named "blob" without an extension, the command would be 'fastboot -i 0x0B05 flash system blob'
If it is named blob.blob the command would be 'fastboot -i 0x0B05 flash system blob.blob'.
Click to expand...
Click to collapse
I think that your first fastboot command is correct: 'fastboot -i 0x0B05 flash system blob'.
berndblb said:
You can also try 'fastboot -i 0x0B05 flash staging blob' followed by a reboot.
Somebody correct me if I'm wrong please....
Click to expand...
Click to collapse
I have not used the staging in fastboot.... However, you can "dd" the blob to your staging partition, /dev/block/mmcblk0p4 with a reboot....
LetMeKnow said:
I think that your first fastboot command is correct: 'fastboot -i 0x0B05 flash system blob'.
I have not used the staging in fastboot.... However, you can "dd" the blob to your staging partition, /dev/block/mmcblk0p4 with a reboot....
Click to expand...
Click to collapse
If you can dd it - why not fastboot it? Should be one of a dozen etc pp, shouldn't it?
Would be great if somebody could clarify this because I have been wondering.... I have read people successfully using the 'flash system blob' as well as 'flash staging blob', which lead me to the impression you can use either of these with the same result (????)
berndblb said:
If you can dd it - why not fastboot it? Should be one of a dozen etc pp, shouldn't it?
Would be great if somebody could clarify this because I have been wondering.... I have read people successfully using the 'flash system blob' as well as 'flash staging blob', which lead me to the impression you can use either of these with the same result (????)
Click to expand...
Click to collapse
You could grab _that's kernel blob or hund's kernel boot.blob and try it out.... In the installer script, They extracted them into the staging partition for the next boot any way... They don't touch the bootloader or recovery. You can check with _that or Hund to be sure...Good luck...:fingers-crossed:
tanutd Doric
Wow - so many replies in such a shot time!
_that said:
I think some user already found out last year the the locked bootloader will happily erase partitions, but then fail to flash the blob, even if it is signed.
Click to expand...
Click to collapse
That's just stupid... hmm.. maybe not, if the intention is, that you can delete your private data even if system is broken....
blob
Click to expand...
Click to collapse
I did rename it from blob to boot.blob (was following http://forum.xda-developers.com/showthread.php?t=2538028).
LetMeKnow said:
I have not used the staging in fastboot.... However, you can "dd" the blob to your staging partition, /dev/block/mmcblk0p4 with a reboot....:
Click to expand...
Click to collapse
How do I access /dev/block/mmcblk0p4 from fastboot?
I ran:
Code:
$ fastboot -i 0x0B05 flash staging boot.blob
sending 'staging' (800927 KB)...
OKAY [893.525s]
writing 'staging'...
OKAY [234.634s]
finished. total time: 1128.159s
At the end a blue progress bar appeared (no android bot) and finished to the right. The RCK button began to flash again, I used it - "Booting Recovery kernel image. Signature Match." - nothing. After that I shut it down (power-vol) and booted - just the ASUS logo
dan54321 said:
I ran:
Code:
$ fastboot -i 0x0B05 flash staging boot.blob
sending 'staging' (800927 KB)...
OKAY [893.525s]
writing 'staging'...
OKAY [234.634s]
finished. total time: 1128.159s
At the end a blue progress bar appeared (no android bot) and finished to the right.
Click to expand...
Click to collapse
That looks good so far. I never understood what the fastboot implementation on the TF700 did with the target partition you specify on the command line anyway ("staging" is not even in the list returned by fastboot getvar) - since the blob contains one or more partition images with a header that says which image is for which partition. For OTA updates or when flashing the firmware from the recovery, the blob is written to the staging partition, and at the next reboot the bootloader writes the images to the final target partitions (with the blue progress bar).
dan54321 said:
The RCK button began to flash again, I used it - "Booting Recovery kernel image. Signature Match." - nothing. After that I shut it down (power-vol) and booted - just the ASUS logo
Click to expand...
Click to collapse
The animated ASUS logo or just the white one from the bootloader?
_that said:
That looks good so far. I never understood what the fastboot implementation on the TF700 did with the target partition you specify on the command line anyway ("staging" is not even in the list returned by fastboot getvar) - since the blob contains one or more partition images with a header that says which image is for which partition. For OTA updates or when flashing the firmware from the recovery, the blob is written to the staging partition, and at the next reboot the bootloader writes the images to the final target partitions (with the blue progress bar).
The animated ASUS logo or just the white one from the bootloader?
Click to expand...
Click to collapse
Unfortunately just the white one (not animated) from the bootloader.
dan54321 said:
How do I access /dev/block/mmcblk0p4 from fastboot?
I ran:
Code:
$ fastboot -i 0x0B05 flash staging boot.blob
sending 'staging' (800927 KB)...
OKAY [893.525s]
writing 'staging'...
OKAY [234.634s]
finished. total time: 1128.159s
At the end a blue progress bar appeared (no android bot) and finished to the right. The RCK button began to flash again, I used it - "Booting Recovery kernel image. Signature Match." - nothing. After that I shut it down (power-vol) and booted - just the ASUS logo
Click to expand...
Click to collapse
You already did with the fastboot command above so you don't need to dd the blob to your staging partition... I guessed that both commands serving the same purpose... The good thing is that your bootloader and fastboot are still working... _that may have a solution for you... Good luck...:fingers-crossed:
@berndblb
I guessed that you found the answer for your question above..
fastboot -i 0x0B05 flash staging boot.blob :laugh:
LetMeKnow said:
The good thing is that your bootloader and fastboot are still working... _that may have a solution for you...
Click to expand...
Click to collapse
Unfortunately not. I assume that the recovery and android kernels are now properly installed since the flashing went normally, but I have no idea why they fail to boot.
_that said:
Unfortunately not. I assume that the recovery and android kernels are now properly installed since the flashing went normally, but I have no idea why they fail to boot.
Click to expand...
Click to collapse
Actually, I had the same issue that it was not booting and only stuck at the Asus booting logo. I believed that two things may cause this issue.. One is the system is somehow not mounting. Two is the data partition is corrupted. For this case, it is more likely the data partition is corrupted. Maybe, he/she can try to use fastboot to erase the data partition and reinstall the Asus stock blob to see if it boots....:fingers-crossed:
Is there a way to format the data partition with fastboot or ADB?
LetMeKnow said:
Actually, I had the same issue that it was not booting and only stuck at the Asus booting logo. I believed that two things may cause this issue.. One is the system is somehow not mounting. Two is the data partition is corrupted. For this case, it is more likely the data partition is corrupted. Maybe, he/she can try to use fastboot to erase the data partition and reinstall the Asus stock blob to see if it boots....:fingers-crossed:
Is there a way to format the data partition with fastboot or ADB?
Click to expand...
Click to collapse
Reinstalling the blob should not be necessary since it was already flashed successfully.
Wiping data should work with something like "fastboot format data".
Ok - that sounds like there might still be a way. I will try to format the data partition this evening and report.
Hi all,
After an upgrade of TWRP 2.4.x.x to 2.6.3.0 my tablet can't boot CM with normal boot with POWER button.
I chose great version of TWRP -JB.blob
But it boots on recovery, asks a password and an issue Internal Storage (0 MB).
I can reboot with adb reboot-bootloader and choice android icon and it works, tablet boots.
I tried to down/upgrade in with fastboot but nothing happens.
Before flash, the select icon blinks (RCK), after flashing bootloader freeze and I need to power off with button.
screen here (img11.hostingpics.net/pics/868378cmd.png)
If it possible I just want to upgrade recovery for flash CM11 M7.
I need help thx a lot and excuse me for this bad english
Cyanogen Mod version 10.2.1
Android Jelly Bean 4.3.1
TWRP v2.6.3.0
Bootloader "WW_epad-10.6.1.27.5-20130902"
Up
No body know how to flash recovery ?
poulaga said:
No body know how to flash recovery ?
Click to expand...
Click to collapse
Hi poulaga,
I know two ways to flash a custom recovery.
1. There's a very helpful thread about everything when it comes to flashing custom roms and recoveries in this link there's a post about flashing 4.4 kk roms. here's the link
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
2. Or you can use the app rashr in the play store.
I can't really understand your problem. It seems like you're having trouble accessing the recovery. Please clarify!
If that really is the case you can use rashr.
Also in order to flash a kitkat rom you need twrp 2.7.0.0 or higher OR us the latest phliz custom recovery. Goodluck
Hi all,
We have tried these fastboot command (poulaga is my friend)
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0B05 erase userdata
fastboot -i 0x0B05 erase boot
fastboot -i 0x0B05 erase misc
fastboot -i 0x0B05 erase cache
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Now tablet is booting Android.
Next step, reflash recovery
kaktuss77 said:
Hi all,
We have tried these fastboot command (poulaga is my friend)
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0B05 erase userdata
fastboot -i 0x0B05 erase boot
fastboot -i 0x0B05 erase misc
fastboot -i 0x0B05 erase cache
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Now tablet is booting Android.
Next step, reflash recovery
Click to expand...
Click to collapse
HI Guys,
I'm glad to hear that the tablet able to boot into android. I'm currently running the latest cm11 snapshot on my tf300t. Everything works! It's a little sluggish a times but ya. And if you guys need help on flashing recoveries try using the two ways I suggested. Both are really easy methods for noobs! Goodluck.
Works fine with TWRP 2.7.0.1 and CM 11 M8 !
Not to derail the conversation, but does TWRP 2.6.3.0 still work for CM 10.2.1?