Hopefully this is an easily answered question. Using fastboot what is the reall difference between using "fastboot -i 0x0B05 flash system blob" compared to "fastboot -i 0x0B05 flash staging blob"?
Are there times when using one is preferable or needed over the other?
EDIT: Fixed. That's what I get for using copy/paste...
MysticMgcn said:
Hopefully this is an easily answered question. Using fastboot what is the reall difference between using "fastboot -i 0x0B05 flash system blob" compared to "fastboot -i 0x0B05 flash system blob"?
Are there times when using one is preferable or needed over the other?
Click to expand...
Click to collapse
Did you mean to type something different for the second option because I can see NO difference between the two!
eckka said:
Did you mean to type something different for the second option because I can see NO difference between the two!
Click to expand...
Click to collapse
Fixed my typo...
Staging autoflashes a kernel on the next boot.
System is just your system or your rom.
Staging is needed because we can't directly flash kernels.
le rustle face
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?
My tablet works only in fastboot mode and APX, nothing else. Was on 4.1.1.
Does anyone can help me to unbrick?
thank you.
I can donate your help
tyla777 said:
My tablet works only in fastboot mode and APX, nothing else. Was on 4.1.1.
Does anyone can help me to unbrick?
thank you.
I can donate your help
Click to expand...
Click to collapse
First you need to provide more info (i.e. did you tried to flash something before this issue occured?, your device is unlocked?) and maybe we can help you.
Yes tablet is unlocked.
i flashed it with CWM Recovery and problems started.
Can't mount anything....
Then i used commands:
fastboot erase boot
fastboot erase recovery
Now then i trying to boot , it brings me error
http://youtu.be/P19Y3Apmbac
tyla777 said:
Yes tablet is unlocked.
i flashed it with CWM Recovery and problems started.
Can't mount anything....
Then i used commands:
fastboot erase boot
fastboot erase recovery
Now then i trying to boot , it brings me error
http://youtu.be/P19Y3Apmbac
Click to expand...
Click to collapse
I can't read the error from that video but i think you should flash a boot.img via fastboot and then flash CWM or TWRP recovery the same vai (via fastboot). BTW you have to use a boot.img from a JB rom.
Pretoriano80 said:
I can't read the error from that video but i think you should flash a boot.img via fastboot and then flash CWM or TWRP recovery the same vai (via fastboot). BTW you have to use a boot.img from a JB rom.
Click to expand...
Click to collapse
Error is 0x000000000
Where i can get boot.img?
Then i extract blob file, i get 5 blob filesblob.
HEADER – Header stuff (ignore it)
blob.APP – system.img
blob.LNX – boot.img
blob.SOS – recovery.img (e.g. regular boot.img)
blob.EBT – bootloader.bin (ignore)
Do i have to rename blob.LNX to boot.img or i should't ?
Do i need to erase all system boot recovery data?
Thanks.
tyla777 said:
Yes tablet is unlocked.
i flashed it with CWM Recovery and problems started.
Can't mount anything....
Then i used commands:
fastboot erase boot
fastboot erase recovery
Now then i trying to boot , it brings me error
http://youtu.be/P19Y3Apmbac
Click to expand...
Click to collapse
You made the same mistake I made:
http://forum.xda-developers.com/showthread.php?t=2031452
APX means you get to use nvflash, right?
I wish I was on the same boat.
Yes i can use nvflash.
but i can't restore my bootloder
maybe you know what to flash?
tyla777 said:
Yes i can use nvflash.
but i can't restore my bootloder
maybe you know what to flash?
Click to expand...
Click to collapse
What do you mean with "Yes i can use nvflash"? You already used the NvFlash tool and have the backup files or is just the fact that you are able to boot in APX mode?
As for the other question, yes rename the blob files ( blob.LNX - > boot.img) and flash from fastboot (fastboot -i 0x0B05 flash boot boot.img). Make sure your battery is full, just in case.
Try to flash the recovery.img, boot.img and system.img using the abive method.
Pretoriano80 said:
What do you mean with "Yes i can use nvflash"? You already used the NvFlash tool and have the backup files or is just the fact that you are able to boot in APX mode?
As for the other question, yes rename the blob files ( blob.LNX - > boot.img) and flash from fastboot (fastboot -i 0x0B05 flash boot boot.img). Make sure your battery is full, just in case.
Try to flash the recovery.img, boot.img and system.img using the abive method.
Click to expand...
Click to collapse
Just the fact
Flashed recovery boot system didn't helped
maybe someone knows how to flash with nvflash?
tyla777 said:
Just the fact
Flashed recovery boot system didn't helped
maybe someone knows how to flash with nvflash?
Click to expand...
Click to collapse
Being able to boot in APX doesn't mean you can use NvFlash to flash your device.If you never used the NvFlash tool to backup your files (and gain NvFlash access) you won't be able to do it anymore because a 9.4.5.26 or lower bootloader it's needed.
I'm not sure if the follow procedure will work but you could try to flash the complete blob via fastboot (rename the original asus blob to something like " tf700t.blob " , something like this : fastboot -i 0x0B05 flash staging tf700t.blob
Someone please correct me if the " flashing to staging" procedure is different.
Pretoriano80 said:
Being able to boot in APX doesn't mean you can use NvFlash to flash your device.If you never used the NvFlash tool to backup your files (and gain NvFlash access) you won't be able to do it anymore because a 9.4.5.26 or lower bootloader it's needed.
I'm not sure if the follow procedure will work but you could try to flash the complete blob via fastboot (rename the original asus blob to something like " tf700t.blob " , something like this : fastboot -i 0x0B05 flash staging tf700t.blob
Someone please correct me if the " flashing to staging" procedure is different.
Click to expand...
Click to collapse
maybe someone knows thne will be released NVFLASH version that support 10.... ver.
tyla777 said:
maybe someone knows thne will be released NVFLASH version that support 10.... ver.
Click to expand...
Click to collapse
ATM there's no way to do that ,Asus locked the bootloader pretty tight this time.
If you still can't manage to fix your issue i would recommend you an RMA ticket from Asus.
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.