I just helped a buddy (this never happened before) and his mytouch is rooted. He upgraded his SPL to Haykuro's and then, through fastboot, he flashed Amon_Ra's 1.2.2 recovery image. Now, we can't get it past the mytouch screen, but can get into fastboot. Any ideas?
Try flashing another rom?
If you can get into fastboot, you can send a new image to the phone.
I don't recall the exact commands, but if you're in fastboot, you're still good.
cursordroid said:
If you can get into fastboot, you can send a new image to the phone.
I don't recall the exact commands, but if you're in fastboot, you're still good.
Click to expand...
Click to collapse
Great man...does anyone know the commands?
Fastboot the recovery image, and then from the recovery, you can flash the new rom.
xyzulu said:
Fastboot the recovery image, and then from the recovery, you can flash the new rom.
Click to expand...
Click to collapse
the recovery image is there. We cant into to recovery to apply the rom.
Get yourself the proper recovery.img for that phone. Not sure what it is, but a quick search will find it. Search for 'mytouch recovery' or 'mt3g recovery'.
Then with the recovery image in your SDK tools folder, run:
Code:
fastboot boot recovery.img
That should at least get you to a point where you can flash a new ROM and commit the proper recovery image to flash using adb commands.
I can't hold your hand through the whole thing, I don't have that phone, but I've been in your situation before.
Ok we tried it, now it says... FAILED(remote: partition does not exist!)
anyone have an idea?
Try to erase Cache
fastboot erase cache
fastboot erase recovery
then flash recovery:
fastboot flash recovery recoveryxxxxxx***.img (***I'm not sure of the version you use...)
antonram said:
fastboot erase cache
fastboot erase recovery
then flash recovery:
fastboot flash recovery recoveryxxxxxx***.img (***I'm not sure of the version you use...)
Click to expand...
Click to collapse
Yeah that's exactl what we did and it worked.
The thing is, we erased the recovvery image and reinstalled it, but now again, it won't go into recovery. I have a feeling he downloaded the wrong Amos_Ra recovery. Probably one for the 32a.
Hi I have been reading a ton in the forums trying to figure out how to fix my tf300t. A few days ago I updated to the newest CM 10.1 nightly and when it restarted it was stuck at the Asus screen. So I have been able to hold vol down button and get to a screen that says
RCK Android [usb symbol] and Wipe Data
I have fastboot access and thought I would try to fix the problem myself by following instructions on another thread
"pyovue - If you have ADB access then unbricking it should be easy as you can push and edit any file on the system with it as well as fastboot? Or can ADB & Fastboot not mount (not just the sdcard) anything? If you don't care what happens to your tablet MB, then try this....
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
Then reboot (this should rid you of your bootloop to recovery and nothing should start)
Then download the stock ASUS Rom (from ASUS, look under Firmware)
Then try sending it with fastboot -i 0x0b05 flash system blob (you will have to extract two zips from the firmware files until you get to a file called "blob" then put it in your fastboot)
I almost guarantee if you have fastboot/adb working there is ALWAYS a way to fix it... only a hardbrick is impossible to fix.
"
I get cannot load 'blob' so I tried
fastboot -i 0x0B05 flash recovery recovery.img
seeing as I already had the recovery.img from when I first unlocked, rooted, and put cm 10.1 on it
please help I have no idea what to do and thank you in advance <3
musicfreak58 said:
Hi I have been reading a ton in the forums trying to figure out how to fix my tf300t. A few days ago I updated to the newest CM 10.1 nightly and when it restarted it was stuck at the Asus screen. So I have been able to hold vol down button and get to a screen that says
RCK Android [usb symbol] and Wipe Data
I have fastboot access and thought I would try to fix the problem myself by following instructions on another thread
"pyovue - If you have ADB access then unbricking it should be easy as you can push and edit any file on the system with it as well as fastboot? Or can ADB & Fastboot not mount (not just the sdcard) anything? If you don't care what happens to your tablet MB, then try this....
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
Then reboot (this should rid you of your bootloop to recovery and nothing should start)
Then download the stock ASUS Rom (from ASUS, look under Firmware)
Then try sending it with fastboot -i 0x0b05 flash system blob (you will have to extract two zips from the firmware files until you get to a file called "blob" then put it in your fastboot)
I almost guarantee if you have fastboot/adb working there is ALWAYS a way to fix it... only a hardbrick is impossible to fix.
"
I get cannot load 'blob' so I tried
fastboot -i 0x0B05 flash recovery recovery.img
seeing as I already had the recovery.img from when I first unlocked, rooted, and put cm 10.1 on it
please help I have no idea what to do and thank you in advance <3
Click to expand...
Click to collapse
What's the question again? If you have fastboot, you can always flash the system blob from your PC. Or you can push the rom (zip) to your internal storage, turn it off and on again. If you select rck on official recovery, it should look for the zip file on its own and proceed to flash it. If you have custom recovery, get to it and flash the same zip file. Make sure you have the right recovery for the rom though. Good luck.
Hi,
and we ansered this kind of prob 2 days ago here: http://forum.xda-developers.com/showthread.php?p=44244313
and yeah - my probs came from an error during cm update.
cheers
-Buster
Buster99 said:
Hi,
and we ansered this kind of prob 2 days ago here: http://forum.xda-developers.com/showthread.php?p=44244313
and yeah - my probs came from an error during cm update.
cheers
-Buster
Click to expand...
Click to collapse
It wouldn't load the blob but i followed that and found that link last night after posting I tried to delete this post but it just allows me to edit
Thanks
My TF300T will only boot into TWRP. I also can't access any storage (failed to mount error) and adb sideloading fails everytime so I can't flash the stock rom. I tried using these commands:
adb shell mount -t tmpfs none /sdcard
adb push ROM.zip /sdcard
Which let me reach the .zip file it still failed to flash.
The tablet had Jellybean 4.2.2 installed. The TWRP version is 2.6.3.0.
How do I fix this?
Reboot it into bootloader menu. If holding volume down and power buttons doesn't work try 'adb reboot bootloader' command while tablet in twrp. Then flash rom through fastboot.
Graiden05 said:
Reboot it into bootloader menu. If holding volume down and power buttons doesn't work try 'adb reboot bootloader' command while tablet in twrp. Then flash rom through fastboot.
Click to expand...
Click to collapse
Now I can get to fastboot, but if I try to flash anything the cmd window says it worked but all it really does is freeze the tablet.
dewdrop623 said:
Now I can get to fastboot, but if I try to flash anything the cmd window says it worked but all it really does is freeze the tablet.
Click to expand...
Click to collapse
Did You flash rom or recovery? And does blue progressbar appears?
Graiden05 said:
Did You flash rom or recovery? And does blue progressbar appears?
Click to expand...
Click to collapse
I was able to flash cwm recovery. So now instead of booting into twrm everytime I get stuck on the splash screen. That didn't really change anything
I tried fastboot -i 0x0b05 flash system boot.blob (the .blob file from the stock rom), and I got the blue progress bar then rebooted but I'm still stuck on the first splash screen.
You do it wrong. So if Your last working firmware was 4.2 You need download this rom from asus webpage. Then unzip it twice and You get blob file. Then flash it with 'fastboot -i 0x0b05 flash staging blob' command.
Graiden05 said:
You do it wrong. So if Your last working firmware was 4.2 You need download this rom from asus webpage. Then unzip it twice and You get blob file. Then flash it with 'fastboot -i 0x0b05 flash staging blob' command.
Click to expand...
Click to collapse
Thanks. That worked. However now I'm only back where I started. CWM give can't mount error and can't reach a zip file. ADB sideload doesn't work either(failed to write data 'protocol fault (no status)'). I tried TWRP once and that's the reason I had to post hear in the first place.
dewdrop623 said:
Thanks. That worked. However now I'm only back where I started. CWM give can't mount error and can't reach a zip file. ADB sideload doesn't work either(failed to write data 'protocol fault (no status)'). I tried TWRP once and that's the reason I had to post hear in the first place.
Click to expand...
Click to collapse
Did You try only TWRP v2.6.3.0? I use v2.5.0.0 and its work fine. About CWM: flatline cwm for 4.2 bootloader was created with purpose do nvflash backup, so may be here is the cause of not working others functions.
Graiden05 said:
Did You try only TWRP v2.6.3.0? I use v2.5.0.0 and its work fine. About CWM: flatline cwm for 4.2 bootloader was created with purpose do nvflash backup, so may be here is the cause of not working others functions.
Click to expand...
Click to collapse
Success. Thanks for the help.
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.
Well, what happened is :
that i was trying to root my Transformer tf300t
and i got as far as unlocking the bootloader
so i was having trouble flashing the twrp recovery image
and i think i accidentally erased the stock recovery image
so now my tablet it's not (full bricked) still boots up but doesn't have a recovery image
and now when i boot it into bootloader mode and try to go into RCK it just gives me this
error bootloader unrecoverable 0x0000000 (in red)
how can i flash the stock ROM again if this error ?
anybody ?HELLP
daveSAPIEN said:
error bootloader unrecoverable 0x0000000(in red)
how can i flash the stock ROM again if this error ?
anybody ?HELLP
Click to expand...
Click to collapse
Please try this:
Go to Asus and dl the latest Stock. Unzipp it 2 times. You should have a blob file now in the extracted folder. Put this blob in your fastboot folder.
Open cmd and type:
fastboot -i 0x0B05 flash staging blob
Let it run. It seems that nothing is happening for about 5 Minutes. The whole thing can take up to 20 Minutes, so just stay calm and wait till it’s finished.
Now you should be back to full Stock with Stock recovery. Good luck!
THanks !
ebonit said:
Please try this:
Go to Asus and dl the latest Stock. Unzipp it 2 times. You should have a blob file now in the extracted folder. Put this blob in your fastboot folder.
Open cmd and type:
fastboot -i 0x0B05 flash staging blob
Let it run. It seems that nothing is happening for about 5 Minutes. The whole thing can take up to 20 Minutes, so just stay calm and wait till it’s finished.
Now you should be back to full Stock with Stock recovery. Good luck!
Click to expand...
Click to collapse
Thank you ... it worked i think
but i used a little different command line i used :
fastboot -i 0x0B05 flash system c:\adb\recovery.blob
now i'm still having problems trying to flash custom recovery i want to root the Tablet
what the problem seems to be for me is that i boot the the tablet (tf330t transformer 4.2.1 JB )
to fastboot mode then i get the 3 choices (RCK, Android,Wipe Data)
but when i try to flash the TWRP recovery img with Fastboot it always gives me an error saying (error cannot load img file)
is there anyway to fix this ? and does this root the tablet?
Dear daveSAPIEN can you give us more information about the file used during the flash , actually am facing the same problem as you but nothing seems to work
thank you