Related
So I unlocked my tf300t and flashed cwm to recovery.
Everything seemed to go fine.
When I would go into cwm it was not able to mount or access any other part of my tab. I figured ok erase/format the recovery partition and try TWRP. So I booted to the bootloader, using fastboot I erased recovery but now whenever I go to flash a new recovery my bootloader either freezes or I get an Unrecoverable bootloader error 0x00000000 (not sure if thats the right amount of zeros but there are no other digits in the error code.) I can access fastboot and adb but it doesn't seem like I can flash using fastboot and I just don't feel comfortable trying with adb. Also I can access fastboot only from the bootloader screen and adb only after I boot into my current rom (stock 4.2.1)
I guess my questions are this:
How can I format my recovery or flash a new recovery?
Were the mount issues I originally encountered going to be solved with a new recovery?
Please help!
Have you tried installing stock rom (from Asus support page) using Fastboot? It should also put stock recovery in your tablet.
Not sure if it is going to work, but it's worth trying though.
1st this is not for the dev section. You should ask questions in the Q&A section.
Go to Asus and dl the latest Stock. Unzipp it 2 times. You should have a blob file now in the extracted folder. put this blob in your fastboot folder.
Open cmd and type:
fastboot -i 0x0B05 flash staging blob
let it run. It seems that nothing is happening for about 5 Minutes. The whole thing can take up to 20 Minutes, so just stay calm and wait till its finished.
Now you should be back to full Stock with Stock recovery.
mikaole said:
1st this is not for the dev section. You should ask questions in the Q&A section.
Go to Asus and dl the latest Stock. Unzipp it 2 times. You should have a blob file now in the extracted folder. put this blob in your fastboot folder.
Open cmd and type:
fastboot -i 0x0B05 flash staging blob
let it run. It seems that nothing is happening for about 5 Minutes. The whole thing can take up to 20 Minutes, so just stay calm and wait till its finished.
Now you should be back to full Stock with Stock recovery.
Click to expand...
Click to collapse
I had this problem too. But on 4.2.1 you can push file blob, and then it's can't run because stock recovery dead.
Were you able to fix the stock recovery issue?
cdguider said:
Were you able to fix the stock recovery issue?
Click to expand...
Click to collapse
Thant i would like to know aswell
Pls
No, I was not. I also have the unrecoverable bootloader error but I have a working device. I downloaded the latest firmware, followed the steps through fastboot and the same thing keeps happening where as soon as you try to enter a command through fastboot the green box stops flashing over rck and even though the cmd prompt window tells you something is going on nothing happens on the tablet end. It freezes. hard reboot and you end up back with a normal working device, no changes and a corrupt bootloader.
lomoski said:
No, I was not. I also have the unrecoverable bootloader error but I have a working device. I downloaded the latest firmware, followed the steps through fastboot and the same thing keeps happening where as soon as you try to enter a command through fastboot the green box stops flashing over rck and even though the cmd prompt window tells you something is going on nothing happens on the tablet end. It freezes. hard reboot and you end up back with a normal working device, no changes and a corrupt bootloader.
Click to expand...
Click to collapse
I have same issue.. has anybody managed to get a fix for this?
I've same problem, how can i fix it?
i've a working device but without recovery mod! I can't flash anything via fastboot because it freezes, i always have "Unrecoverable bootloader error" when press RCK.
Can somebody help me?
Thanks in advance
mister363 said:
I've same problem, how can i fix it?
i've a working device but without recovery mod! I can't flash anything via fastboot because it freezes, i always have "Unrecoverable bootloader error" when press RCK.
Can somebody help me?
Thanks in advance
Click to expand...
Click to collapse
I was having this problem earlier - a new bootloader came out when they went to 4.2, but most of the instructions online don't reflect this. You need an updated recovery image, which usually has the name recovery-jb.img instead of recovery.img. When you're searching make sure the instructions mention 4.2 and jelly bean.
However, I've only managed to get one step further - have now get into clockworkmod recovery, but as with the OP I then couldn't mount anything inside CWM. I tried another instruction set which involved unzipping the ROM and using adb to push over the .blob. This hasn't worked and I have now got a pretty much bricked device - it either bootloops on the asus splash screen, or loads into CWM.
I've found that even when youre in CWM you can type "adb reboot-bootloader" into the terminal, which forces the RCK/android/wipe data page and fastbook to appear. I've also tried to download the latest stock firmware from ASUS, unzipped it to get the stock .blob out and into my fastboot directory, then run "fastboot -i 0x0B05 flash staging blob" in the terminal, as per mikaole's suggestion. This takes a while to push over the 80mb .blob, but after it says it's staged it says "done" then nothing happens and it's still bricked. hmm.
No one's figured this out? I tried flashing the blob file and my system won't boot at all
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
IT WORKS!!!
Buster99 said:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
Thank you very much. It works beautifully.
Buster99 said:
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
Now i' m busy because of my Job. But next week i want try your method.
I hope it work for my device!
Inviato dal mio GT-I9100 con Tapatalk 2
Buster99 said:
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
Did your tablet seem to freeze after flashing via fastboot? When I push blob, the console shows that it wrote, but then fastboot on the tablet freezes & I have to manually reboot, putting me right back to the drawing board.
Sent from my HTC One using xda app-developers app
Until now my device freezes. Fastboot seem to work but nothing happens. :banghead:
Inviato dal mio GT-I9100 con Tapatalk 2
P05TMAN said:
Did your tablet seem to freeze after flashing via fastboot? When I push blob, the console shows that it wrote, but then fastboot on the tablet freezes & I have to manually reboot, putting me right back to the drawing board.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
nope. do you use the original cable on usb 2.0 and connected to your pc not a usb hub? should work. if not try a diffrent pc - sometimes usb chipsets make problems.
Buster99 said:
nope. do you use the original cable on usb 2.0 and connected to your pc not a usb hub? should work. if not try a diffrent pc - sometimes usb chipsets make problems.
Click to expand...
Click to collapse
I get invalid argument to all of the erase attempts and the minute I try to push the blob the flashing green icon in fastboot mode on the tablet stops. The command windows says the flash went fine but the tablet is unresponsive and must be reset. Infact any fastboot command that pushed something to the tablet causes it to look up ( indicated by the green flashing RCK icon freezing on whatever phase of green it had at the time)
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.975s]
sending 'system' (800935 KB)...
OKAY [134.565s]
writing 'system'...
OKAY [ 2.040s]
finished. total time: 138.583s
I think its time to bin this doorstop and break something new
d3fiant said:
I get invalid argument to all of the erase attempts and the minute I try to push the blob the flashing green icon in fastboot mode on the tablet stops. The command windows says the flash went fine but the tablet is unresponsive and must be reset. Infact any fastboot command that pushed something to the tablet causes it to look up ( indicated by the green flashing RCK icon freezing on whatever phase of green it had at the time)
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.975s]
sending 'system' (800935 KB)...
OKAY [134.565s]
writing 'system'...
OKAY [ 2.040s]
finished. total time: 138.583s
I think its time to bin this doorstop and break something new
Click to expand...
Click to collapse
Mine does this same thing.....think it's done for?
Sent from my HTC One using xda app-developers app
Buster99, your instructions saved my device. I missed erasing /misc even though you put it in the directions and my tablet's back! I owe you.
Tried to update to CM 11 / 4.4 KitKat and got "unrecoverable bootloader error"
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
ANDROiD_eKa said:
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
Click to expand...
Click to collapse
You can read this to see if it helps..good luck..:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2528313
ANDROiD_eKa said:
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
Click to expand...
Click to collapse
Sorry, but after reading your post 4 times I still have no idea what you actually did.....
If you still have access in ADB (since you can't access the bootloader??) the link LMK gave you may save your bacon.
If you don't have any kind of access: ADB or fastboot and you do not have nvFlash blobs - sorry, you bricked.
Can I access fastboot when I get the menu at RCK / Android / Wipe? Because if I click con any of these its says that bootloader is corrupted.
What's the Command to fix TWRP using a computer / or other Android device?
ANDROiD_eKa said:
Can I access fastboot when I get the menu at RCK / Android / Wipe?
Click to expand...
Click to collapse
Does it say something about fastboot in the upper left corner?
ANDROiD_eKa said:
What's the Command to fix TWRP using a computer / or other Android device?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
_that said:
Does it say something about fastboot in the upper left corner?
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
Click to expand...
Click to collapse
Thanks _that for the advice...:good: You are the expert in this area... I am done with my job to bring you in here for helps..haha...
_that said:
Does it say something about fastboot in the upper left corner?
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
Click to expand...
Click to collapse
Yes it says
Code:
Starting Fastboot USB download protocol
Ok flashed TWRP via fastboot but device freezes?
Code:
C:\Documents and Settings\HP_Administrator.CEREBRO>fastboot -i 0x0B05 flash reco
very twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.563s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 5.016s
It still won't let me boot to TWRP saying an "unrecoverable bootloader error" occured. Is there something I can do?
ANDROiD_eKa said:
Ok flashed TWRP via fastboot but device freezes?
Code:
C:\Documents and Settings\HP_Administrator.CEREBRO>fastboot -i 0x0B05 flash reco
very twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.563s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 5.016s
It still won't let me boot to TWRP saying an "unrecoverable bootloader error" occured. Is there something I can do?
Click to expand...
Click to collapse
You can use the link on my previous reply and read post #3 by _that to clear your misc.. You need to use "dd=" command erase your mmcblk0p3 partition. Please be carefull when you use it and make sure you erase the right partition. Anything after "of=" is you write to....
Please ask more question with _that before execute that command...Good luck..:fingers-crossed:
LetMeKnow said:
You can use the link on my previous reply and read post #3 by _that to clear your misc.. You need to use "dd=" command erase your mmcblk0p3 partition. Please be carefull when you use it and make sure you erase the right partition. Anything after "of=" is you write to....
Please ask more question with _that before execute that command...Good luck..:fingers-crossed:
Click to expand...
Click to collapse
I think this may be different. Clearing the misc partition solved the problem of force booting into recovery.
Here he can't get into recovery... Not looking good.....
berndblb said:
I think this may be different. Clearing the misc partition solved the problem of force booting into recovery.
Here he can't get into recovery... Not looking good.....
Click to expand...
Click to collapse
The fastboot write is successfull but the recovery is not updating.... You and _that may have the answer..
LetMeKnow said:
The fastboot write is successfull but the recovery is not updating.... You and _that may have the answer..
Click to expand...
Click to collapse
Pff - just yesterday I used fastboot to push TWRP 2.6.3.1 and it said successful. TWRP still shows version 2.6.1. - so what do I know???
berndblb said:
Pff - just yesterday I used fastboot to push TWRP 2.6.3.1 and it said successful. TWRP still shows version 2.6.1. - so what do I know???
Click to expand...
Click to collapse
I think that his/her bootloader is still partly function because the fastboot is running.. I don't want to give any advice unless I know for sure that it works. If someone have a better knowledge on the bootloader and recovery, it can be up and running again, I hope...
LetMeKnow said:
I think that his/her bootloader is still partly function because the fastboot is running.. I don't want to give any advice unless I know for sure that it works. If someone have a better knowledge on the bootloader and recovery, it can be up and running again, I hope...
Click to expand...
Click to collapse
As long as there is fastboot, there is hope
http://lmgtfy.com/?q=fastboot+boot+image
berndblb said:
As long as there is fastboot, there is hope
http://lmgtfy.com/?q=fastboot+boot+image
Click to expand...
Click to collapse
Hey guys thank you for your help. I had learned that I encountered a softbrick. I got my tabby fix reading ]Unrecoverable bootloader error(0x00000000) Which led me to Softbrick - possible solution for you
Followed these steps...
buster99 said:
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer, as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
Click to expand...
Click to collapse
Although I admit I had to these steps several times as it initially wouldn't somehow it wiped out that error. After I had fix that bootloader error I used fastboot and installed TWRP 2.6.3.1 and now life can continue.
I also followed steps right on getting CM11 to work by using CWM Touch this time to install and it looks jelly. ?! Love these 4.4 KitKat emoticons, thanks again for your help and interest in me ?
ANDROiD_eKa said:
Hey guys thank you for your help. I had learned that I encountered a softbrick. I got my tabby fix reading ]Unrecoverable bootloader error(0x00000000) Which led me to Softbrick - possible solution for you
Followed these steps...
Although I admit I had to these steps several times as it initially wouldn't somehow it wiped out that error. After I had fix that bootloader error I used fastboot and installed TWRP 2.6.3.1 and now life can continue.
I also followed steps right on getting CM11 to work by using CWM Touch this time to install and it looks jelly. ?! Love these 4.4 KitKat emoticons, thanks again for your help and interest in me ?
Click to expand...
Click to collapse
Buster99 deserves a medal or something for this post. Dozens of people have recovered from a brick using his method!
Glad you got it going!
After trying to flash TWRM img from flashify I get an "unrecoverable bootloader error 0x00000000" I have tried to flash CWM by the same method, with no avail, PLEASE HELP. I can acess CM11 though,and root is still good. the only thing not working is recover
kansasboy001 said:
After trying to flash TWRM img from flashify I get an "unrecoverable bootloader error 0x00000000" I have tried to flash CWM by the same method, with no avail, PLEASE HELP. I can acess CM11 though,and root is still good. the only thing not working is recover
Click to expand...
Click to collapse
I'm sorry I don't have time to post links right now but try to download and install flashboot. If you get that far, you can then download almost any recovery solution and see if you can flash it. I believe the command will be:
Code:
Fastboot -i 0x0B05 flash recovery <file location>
Please read up a bit before you try this. It should flash just the recovery so it shouldn't intefer with the OS or root. Please use caution and read, read, read on the topics (fastboot, TWRP, CWM.)
-Tony
This is the ONLY solution for this problem, worked great for me.
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
I have an Asus TF300T paperweight!
I started out to root my tablet and load CWM. I unlocked it, install TWRP v2.2.2.2 as I read in a blog with instructions on how to root this tablet. I loaded a CWM ROM, can't remember not which. It didn't load correctly, and kept rebooting. I got into the screen that gives the following four options:
1. RCK
2. Android icon
3. USB icon
4. Wipe data icon
Of course, thinking I would start over and try again, selected Wipe Data. Stupid, I know.
Now, my tablet only boots into TWRP. It won't mount anything; of course, since I Wiped Data, there is nothing to mount. I have tried and searched, to no avail. I can see the tablet in Device Manager, and managed to load the Naked Universal Drivers. Now it shows up in Device Manager as Asus Eee Pad Slider ADB Interface. I can issue the command - adb reboot - and it will reboot, but I can't get it to do anything else meaningful with my meager experience.
Any help would be greatly appreciated. I would like to get this working and give it to my son, as I have already purchased a replacement for myself.
Thank you.
dhastings said:
I have an Asus TF300T paperweight!
I started out to root my tablet and load CWM. I unlocked it, install TWRP v2.2.2.2 as I read in a blog with instructions on how to root this tablet. I loaded a CWM ROM, can't remember not which. It didn't load correctly, and kept rebooting. I got into the screen that gives the following four options:
1. RCK
2. Android icon
3. USB icon
4. Wipe data icon
Of course, thinking I would start over and try again, selected Wipe Data. Stupid, I know.
Now, my tablet only boots into TWRP. It won't mount anything; of course, since I Wiped Data, there is nothing to mount. I have tried and searched, to no avail. I can see the tablet in Device Manager, and managed to load the Naked Universal Drivers. Now it shows up in Device Manager as Asus Eee Pad Slider ADB Interface. I can issue the command - adb reboot - and it will reboot, but I can't get it to do anything else meaningful with my meager experience.
Any help would be greatly appreciated. I would like to get this working and give it to my son, as I have already purchased a replacement for myself.
Thank you.
Click to expand...
Click to collapse
Stop.
Find buster's post and thank him.
And make sure you keep twrp up to date. You have an extremely old versioin which is why you bricked.
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
sbdags said:
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
thanks
i was stuck on cwm
could not acess to sd card
followed those steps and there it goes
working again
thanks a lot!
submancm
Guys i got serious problem. I have wiped my TF300T by mistake before i could make a backup file for it. Now my Tab is freezing on the starting screen and i can do nothing.... Is there any chance to do something with this and bring back to live my TF300T?
Orsoniusz said:
Guys i got serious problem. I have wiped my TF300T by mistake before i could make a backup file for it. Now my Tab is freezing on the starting screen and i can do nothing.... Is there any chance to do something with this and bring back to live my TF300T?
Click to expand...
Click to collapse
Is your device unlocked and can you get to the bootloader screen by holding vol-down, when powering on?
Then you can use fastboot to flash your favourite ROM.
I suggest to start with flashing the latest Asus ROM 10.6.1.27.5 and boot it at least once, so your tablet is brought up-to-date.
For detailed instructions please check the stickies in the General section or search. Tips and tricks are all over the threads.
Sent from my TF300T using Tapatalk
Yes my device is unlocked, but when i'm trying to get to bootloader the device is just reseting itself and freezeng on starting asus screen..(sorry for bad eng. )
Orsoniusz said:
Yes my device is unlocked, but when i'm trying to get to bootloader the device is just reseting itself and freezeng on starting asus screen..(sorry for bad eng. )
Click to expand...
Click to collapse
There are a couple of tricks to try: hold power for at least 10 secs, then release holding vol-down, use the small reset hole holding vol-down, power off then connect the charger while holding vol-down and possibly more. Several people managed to break out of such a boot loop using one or another of those.
Sent from my TF300T using Tapatalk
f69m said:
There are a couple of tricks to try: hold power for at least 10 secs, then release holding vol-down, use the small reset hole holding vol-down, power off then connect the charger while holding vol-down and possibly more. Several people managed to break out of such a boot loop using one or another of those.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
i've tryed them already and non worked it looks like the tab is not leting me through the first screen that appears before the bootloader comes and it stays still on it like frozen.
Orsoniusz said:
i've tryed them already and non worked it looks like the tab is not leting me through the first screen that appears before the bootloader comes and it stays still on it like frozen.
Click to expand...
Click to collapse
Sounds not good.
If you have not created nvflash blobs before, no recovery and no fastboot, I am out of ideas, sorry.
Sent from my TF300T using Tapatalk
f69m said:
Sounds not good.
If you have not created nvflash blobs before, no recovery and no fastboot, I am out of ideas, sorry.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
The main problem is that i cant get to the bootloader to be recognized by fastboot. If i can get there it is easy to do the rest....
Orsoniusz said:
The main problem is that i cant get to the bootloader to be recognized by fastboot. If i can get there it is easy to do the rest....
Click to expand...
Click to collapse
What bootloader version are you running??? Do you have a usb icon on your bootloader screen??
Thanks to Buster99
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
jaffer707 said:
Thanks to Buster99
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
Yea but the problem is that i cant get to fastboot so it will not work for me. i've tryed lot of times to get to bootloader and i cant stuck on the asus screen with the "device unlocked"....
Guys i'm curious What will asus say if i would send them my tf300t on a warranty if my device is unlocked is there any possibility for repair?
Orsoniusz said:
Guys i'm curious What will asus say if i would send them my tf300t on a warranty if my device is unlocked is there any possibility for repair?
Click to expand...
Click to collapse
Repair is always possible, just might be expensive.
If you are unlocked and your issue is software related, Asus will probably charge you for replacing the mainboard. If your issue is obviously hardware-related, you might be lucky in some countries like in the EU, where Asus is not allowed to generally waive the warranty.
Sent from my TF300T using Tapatalk