Hello xda people,
I tried to flash my TF201 with stock 4.1.1 ROM and 10.4.2.18 bootloader and I think I messed up the bootloader because now it can only go into USB mode - RCK, Wipe Data and Android all return "unrecoverable bootloader error" (0x0000000). And in USB mode, only fastboot commands work - ADB commands cannot be executed since it doesn't see the device.
I tried to follow a few troubleshooting guides posted here but hit a snag.
After running the following command:
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
I had this error message:
Code:
FAILED (command write failed (Unknown error))
finished. total time: 0.641s
so I went ahead and probably deleted more things that I should have.
Now I somehow managed to execute :
Code:
fastboot -i 0x0b05 flash recovery openrecovery-twrp-2.6.3.0-tf201-JB.blob
but after that the following command returns an error message:
sending 'recovery' (7934 KB)...
OKAY [ 1.373s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 2.901s
Click to expand...
Click to collapse
Code:
fastboot -i 0x0b05 reboot-bootloader
so I had to reset the device with a paperclip in the reset hole on the side to be able to pick USB mode ( and fastboot)
I think I messed up big time and hope you can help me restore my Prime back to life.
Thank you!
Update:
After performing the following steps , I managed to revert it back to factory ROM:
1. Installed ADB Installer from : http://forum.xda-developers.com/showthread.php?t=2588979
2. Downloaded original ASUS blob from their website - make sure you pick the one for your SKU
3. Followed the steps posted in the Answer from this post: http://android.stackexchange.com/questions/28077/bricked-my-asus-tf300t-manual-jb-update
Hope this helps someone.
When I try to pick RCK from the bootloader options , I get the red exclamation mark with the laying android logo - that has been the case from the very beginning - even before having made any changes to the original stock 4.1.1. ROM.
I have a question: Since I have not unlocked the bootloader prior to upgrading to JB via OTA update, what are the next steps to put KitKat custom ROM to my tablet?
I just brought it back from the dead - I don't want to risk bricking my TF201.
Thanks!
Related
Hi, i have an unlocked tf201 and tried to install recovery-clockwork-touch-5.8.1.8-tf201.img which seemd to go fine:
Code:
sudo ./fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
sending 'recovery' (5380 KB)...
OKAY [ 2.432s]
writing 'recovery'...
OKAY [ 7.011s]
finished. total time: 9.443s
hamlet:Console_Connection michael$ ./fastboot reboot
rebooting...
finished. total time: 0.001s
Thing is the recovery console will not load, after i select it (RCK) nothing happens? The message at top of screen says
Code:
Booting into recovery kernel image
If power off and on again it will boot fine into latest Asus jelly bean rom.
I have tried to re-flash, but now i can no longer find the device in OSX?
Code:
adb devices
List of devices attached
This is the same in both fastboot and when booted normally?
Any ideas?
many thanks
Seems i can find it as a device with adb when booted normally, but not when in fastboot?
ah seems it does not matter if not seen as device when in fastboot as i tried flash again it it seems to work
Code:
sudo ./fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
Password:
sending 'recovery' (5380 KB)...
OKAY [ 2.427s]
writing 'recovery'...
OKAY [ 6.286s]
finished. total time: 8.713s
but still it will not boot into recovery?
Thanks
Even tried flashing openrecovery-twrp for jb, but still won't boot into recovery?
any help here would very much appriciated
carperman said:
Even tried flashing openrecovery-twrp for jb, but still won't boot into recovery?
any help here would very much appriciated
Click to expand...
Click to collapse
You are not saying what we need to know.
What bootloader are you on ? Where is the "NVIDIA" logo when you first power on the device? Bottom center or bottom right ?
flumpster said:
You are not saying what we need to know.
What bootloader are you on ? Where is the "NVIDIA" logo when you first power on the device? Bottom center or bottom right ?
Click to expand...
Click to collapse
flumpster said:
You are not saying what we need to know.
What bootloader are you on ? Where is the "NVIDIA" logo when you first power on the device? Bottom center or bottom right ?
Click to expand...
Click to collapse
Sorry thought i had made it clear?
Thanks for the reply i will try and be clearer.
In answer to your question about nvidia logo, it is bottom right.
What i have:
New TF201
unlocked when running ICS
Updated to latest Asus Jelly Bean rom
What i want to achieve:
I wish to root tablet (super user) and eventually install a custom rom.
What i need to do:
Flash clockwork-touch
install superuser.zip via recovery console
Results:
adb devices - report device
fastboot devices - shows no devices
boot to fastboot with 'power/vol ok
fastboot -i 0x0b05 flash recovery *.img - seems to work, see OP
fastboot reboot-bootloader works though recovery never loads
boot to recovery with 'power/vol never loads
For the last 2 it just says
Booting into recovery kernel image
I tried installing rtr_recovery-clockwork-touch which patched version, which again seems to work
Code:
fastboot -i 0x0b05 flash recovery rtr_recovery-clockwork-touch-5.8.1.8-tf201/recoveryblob
sending 'recovery' (5398 KB)...
OKAY [ 2.387s]
writing 'recovery'...
OKAY [ 6.398s]
finished. total time: 8.785s
Code:
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
This worked, but as before nothing happens it just sits at B]
Booting into recovery kernel image[/B]
The two issue i have are:
fastboot cannot see devices (seem to work though)
recovery is not loading
I can only assume that even though fastboot seems to flashing device, blue load bar appears on tablet and reboot-bootloader commands works, it is not actually flashing the device?
thanks
carperman said:
Sorry thought i had made it clear?
Thanks for the reply i will try and be clearer.
In answer to your question about nvidia logo, it is bottom right.
What i have:
New TF201
unlocked when running ICS
Updated to latest Asus Jelly Bean rom
What i want to achieve:
I wish to root tablet (super user) and eventually install a custom rom.
What i need to do:
Flash clockwork-touch
install superuser.zip via recovery console
Results:
adb devices - report device
fastboot devices - shows no devices
boot to fastboot with 'power/vol ok
fastboot -i 0x0b05 flash recovery *.img - seems to work, see OP
fastboot reboot-bootloader works though recovery never loads
boot to recovery with 'power/vol never loads
For the last 2 it just says
Booting into recovery kernel image
I tried installing rtr_recovery-clockwork-touch which patched version, which again seems to work
Code:
fastboot -i 0x0b05 flash recovery rtr_recovery-clockwork-touch-5.8.1.8-tf201/recoveryblob
sending 'recovery' (5398 KB)...
OKAY [ 2.387s]
writing 'recovery'...
OKAY [ 6.398s]
finished. total time: 8.785s
Code:
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
This worked, but as before nothing happens it just sits at B]
Booting into recovery kernel image[/B]
The two issue i have are:
fastboot cannot see devices (seem to work though)
recovery is not loading
I can only assume that even though fastboot seems to flashing device, blue load bar appears on tablet and reboot-bootloader commands works, it is not actually flashing the device?
thanks
Click to expand...
Click to collapse
First off, awesome report. Far more than I needed but I won't have to ask you another question along the way from now on.
You are on the jellybean bootloader. You should not even be flashing CWM while on that because that is how so many people hard brick their devices.
Can you please try downloading the custom TWRP I have in the following link that I have installed myself and made for the jellybean bootloader so I know this is where we are both at. The zip file has a bat file and you just run it and follow onscreen instructions.
http://forum.xda-developers.com/showpost.php?p=26595675&postcount=2
You want Hairybean TWRP Updater (normal).
Please do not try to install CWM at any point from now on.
flumpster said:
First off, awesome report. Far more than I needed but I won't have to ask you another question along the way from now on.
You are on the jellybean bootloader. You should not even be flashing CWM while on that because that is how so many people hard brick their devices.
Can you please try downloading the custom TWRP I have in the following link that I have installed myself and made for the jellybean bootloader so I know this is where we are both at. The zip file has a bat file and you just run it and follow onscreen instructions.
http://forum.xda-developers.com/showpost.php?p=26595675&postcount=2
You want Hairybean TWRP Updater (normal).
Please do not try to install CWM at any point from now on.
Click to expand...
Click to collapse
Thanks, will give it a try.
Must have done something as cannot get adb to find device when in fastboot now?
Tried rebooting workstation and tablet a few times, but no joy
and your bat file did not find device either?
carperman said:
Must have done something as cannot get adb to find device when in fastboot now?
Tried rebooting workstation and tablet a few times, but no joy
and your bat file did not find device either?
Click to expand...
Click to collapse
adb does not work in fastboot. Only the fastboot command does. The only places you can use adb is either while in the OS or while in recovery.
The .bat file would have tried to run a fastboot flash command.
Here is odd thing though, even though adb devices shows nothing and the .bat can't find connection the command fastboot reboot-bootloader works?
Note the error i get with .bat is
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal) michael$ ./HairyBean\ TWRP\ Recovery\ Flasher.bat
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal)
Just noticed that fastboot now find device though
fastboot devices
015d0787bf2fee07 fastboot
thanks
carperman said:
Here is odd thing though, even though adb devices shows nothing and the .bat can't find connection the command fastboot reboot-bootloader works?
Note the error i get with .bat is
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal) michael$ ./HairyBean\ TWRP\ Recovery\ Flasher.bat
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal)
Just noticed that fastboot now find device though
fastboot devices
015d0787bf2fee07 fastboot
thanks
Click to expand...
Click to collapse
I see a michael subfix in there. Are you running this zip from desktop or a link? Can you please try extracting the zip to a physical drive (e.g. make a folder on d: and call it wookie then extract the zip in it.
I have seen before this script failing on desktop.
edit... I have just looked back at your earlier outputs. Are you in linux because I presumed you was on windows when I started? The .bat file is for windows and it will probably not even work in linux because of the links.
ok sorted, checked the .bat and is for windows i am on OSX so did
fastboot -i 0x0B05 flash recovery fastboot/recoveryTWRP.blob
and it works
great many thanks, now to try your custom rom
carperman said:
ok sorted, checked the .bat and is for windows i am on OSX so did
fastboot -i 0x0B05 flash recovery fastboot/recoveryTWRP.blob
and it works
great many thanks, now to try your custom rom
Click to expand...
Click to collapse
Cool, glad you got it sorted.
Just know that you don't need to root first. Root is built into the roms and is not needed to flash.
Also please never try CWM again... From now on if you grab the official TWRP as needed make sure you get the JB version.
gl mate.
Awesome man this worked fine for me, had the same problem I guess koush needs to do his homework on the devices, or I do one..
Hi.
After I've tried to install a custom rom, I've done a very big mistake. Now I can't boot the tab, and if I try to go in recovery or wipe data through fastboot i get the fatally error "unrecoverable bootloader error 0x00000000". I haven't any nvflash backup and have the JB bootloader (10.6.1.8). The only thing that works are the APX mode and the fastboot. I'm feeling a very idiot because i bought it yesterday.
Now, what can I do? Dump it and f**k myself? :crying:
Sorry for my bad english, thank you for your help.
I realized I'm screwed. But I've tried something...
When I go run the fastboot mode and delete a partition, for example:
Code:
fastboot erase recovery
works, and after I can run other command. But if I use:
Code:
fastboot flash recovery recovery.img
seems it works, in fact the output is
Code:
sending 'recovery' (5378 KB)...
OKAY [ 2.431s]
writing 'recovery'...
OKAY [ 1.739s]
finished. total time: 4.170s
but it's stucked and I need to reboot manually.
Any idea?
Kito92 said:
I realized I'm screwed. But I've tried something...
When I go run the fastboot mode and delete a partition, for example:
Code:
fastboot erase recovery
works, and after I can run other command. But if I use:
Code:
fastboot flash recovery recovery.img
seems it works, in fact the output is
Code:
sending 'recovery' (5378 KB)...
OKAY [ 2.431s]
writing 'recovery'...
OKAY [ 1.739s]
finished. total time: 4.170s
but it's stucked and I need to reboot manually.
Any idea?
Click to expand...
Click to collapse
I have the same. Im on an ICS bootloader due to having to run nvflash to get it back to that point.
I have fastboot access i can send a recovery image over to it (twrp 2.5 ics.img) however when i reboot it i dont see the recovery!
PLEASE PLEASE PLEASE Someone help
Hey folks,
I'm trying to install a recovery image using fastboot, as per the directions presented here:
http://wiki.cyanogenmod.org/w/Install_CM_for_fireball
When I try flashing the recovery, I get the following error message:
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.117s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.149s
I was able to obtain S-OFF following the directions presented in this thread:
http://forum.xda-developers.com/showthread.php?t=2664460
but I am now currently in "relocked" state because I followed step 5 and tried running DirtyRacun.
Phone: HTC incredible 4g lte.
hboot: 1.15.0000
radio: 1.53.06.0919
OpenDSP-v29.1.0.45.0622
Thanks in advance!
in other news ...
My phone is in an unusable state. I still have access to the bootloader, and when it's plugged into my computer, I have access to it through adb, but otherwise, I can't send or receive phone calls from it.
stringedonbass said:
My phone is in an unusable state. I still have access to the bootloader, and when it's plugged into my computer, I have access to it through adb, but otherwise, I can't send or receive phone calls from it.
Click to expand...
Click to collapse
Apparently shutting down and pulling the battery "fixes" that problem.
Step 5 was not to run dirty racoon it was to flash the engineering hboot from the DirtyRacun webpage, but with S-off you should still be able to flash the hboot and recovery.
I find this page useful when I am working in ADB to keep the ideas fresh. http://forum.xda-developers.com/showthread.php?t=2141817
stringedonbass said:
Hey folks,
I'm trying to install a recovery image using fastboot, as per the directions presented here:
http://wiki.cyanogenmod.org/w/Install_CM_for_fireball
When I try flashing the recovery, I get the following error message:
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.117s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.149s
I was able to obtain S-OFF following the directions presented in this thread:
http://forum.xda-developers.com/showthread.php?t=2664460
but I am now currently in "relocked" state because I followed step 5 and tried running DirtyRacun.
Phone: HTC incredible 4g lte.
hboot: 1.15.0000
radio: 1.53.06.0919
OpenDSP-v29.1.0.45.0622
Thanks in advance!
Click to expand...
Click to collapse
Re: adb guide
wmuflyer said:
Step 5 was not to run dirty racoon it was to flash the engineering hboot from the DirtyRacun webpage, but with S-off you should still be able to flash the hboot and recovery.
I find this page useful when I am working in ADB to keep the ideas fresh. http://forum.xda-developers.com/showthread.php?t=2141817
Click to expand...
Click to collapse
That's a nice guide on the Android Debug Bridge (abd). As a side note, I was pleased to find that fastboot and adb can be found in Ubuntu's repositories.
Update: flashed DirtyRacun's HBOOT
My phone now says
-- DirtyRacun --
at the top of the bootloader. No need to "unlocking" the phone because it was already in S-OFF state. After downloading the HBOOT file from unlimited's fireball website, I typed these commands, also available from their website:
Code:
sudo ./fastboot erase cache
sudo ./fastboot oem rebootRUU
sudo ./fastboot flash zip [file name]
sudo ./fastboot reboot
Happily rooted with CyanogenMOD installed
I'm happily rooted and have CyanogenMOD up and running.
After flashing the engineering hboot onto my phone using unlimited's directions, I was able to install ClockworkMod Recovery for fireball following the directions posted on their website.
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.141s]
writing 'recovery'...
OKAY [ 2.129s]
finished. total time: 3.271s
I then was able to install CyanogenMod from recovery like "clockwork". Of course, "abd reboot-bootloader" is much faster than the crazy key combinations they ask you do to. When asked to install from sdcard, there were two locations to look at.
Cheers everyone! :victory:
Hi Everyone,
First I apologize if this isn't the right place to post this, please move it to the correct forum if it's not.
I have a Asus TF700 (running the latest Asus firmware) the, warranty just ran out so I figured it was time to unlock and play with some custom roms.
I got it unlocked using the Asus bootloader tool, I went to install CWM using fastboot and it seemed to go OK but then when I went to reboot the bootloader it failed giving me a write failure. Now when I try to boot up recovery it briefly shows the android guy in working mode then goes to the error with the android laying on his back.
Here is my commands with fastboot:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (6688 KB)...
OKAY [ 2.483s]
writing 'recovery'...
OKAY [ 2.409s]
finished. total time: 4.893s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\adb>adb reboot bootloader
error: device not found
And that's it, I'm a bit stumped not sure how to fix it so I can move onto installing the roms, any help would be greatly appreciated.
Anyone?
DId you install the Google USB driver?
If don't,please install the Android SDK and install all.
packyy said:
DId you install the Google USB driver?
If don't,please install the Android SDK and install all.
Click to expand...
Click to collapse
Yes, if I hadn't then I wouldnt have been able to use fastboot or install CWM.
No one? I thought this was the android super stars forum.
Can someone at lease suggest another forum with people willing to help?
Not a single person willing to help me out? Wow, thanks.
Hi, all.
I was messing around with Android Tweaker 2, zipaligning my apps, performing vague system tweaks and the like, when I rebooted my phone for the changes to take effect; however, the phone booted up, finished the booting animation, and where the home screen should be showing up only showed a black screen. From there I can only reboot again, reboot into STOCK recovery, or reboot into fastboot, which has limited function in an Asus device (inability to flash unsigned custom recovery images, inability to flash rom images, stock firmware images are unavailable ANYWHERE, etc.) My device WAS rooted, however, I did a factory reset from the stock recovery in hopes that the problem would be resolved, so I'm not sure if root access was retained. I've tried a lot of things, but what I need is access to adb to push some files, or just figure out what the hell happened to the device.
Any ideas? Thanks in advance.
Details:
Asus Padfone X [4.4.2 stock rom]
WAS rooted
LOCKED bootloader
STOCK recovery
Fastboot is basically useless, given the "safeguards" Asus has implemented
Read the CM12.1 for instructions on unlocking bootloader , there are instructions on booting from custom recovery using fastboot from there you can adb push the files to your phone as posted in the Nandroid Stock backup thread and install using TWRP.
daggorlad said:
Read the CM12.1 for instructions on unlocking bootloader , there are instructions on booting from custom recovery using fastboot from there you can adb push the files to your phone as posted in the Nandroid Stock backup thread and install using TWRP.
Click to expand...
Click to collapse
Thanks for the advice.
I have consulted the CM12.1 thread, and I see the instructions, the first step of which is to "boot into CWM, CMRecovery, or TWRP." However, I do not have any of these custom recoveries flashed on my Padfone X. Is there a way I can boot custom recovery off an external microsd or something?
Note: upon attempting the "fastboot flash recovery CMrecovery.img" command, the cmd window returns the following:
Code:
target reported max download size of 1879048192 bytes
sending 'recovery' <11220 KB>...
OKAY [ 0.438s ]
writing 'recovery'...
FAILED <remote: can't flash unsigned image>
finished. total time: 0.444s
EDIT: Problem has been resolved, used
Code:
fastboot boot twrp.img
and restored stock.
shattered519 said:
Thanks for the advice.
I have consulted the CM12.1 thread, and I see the instructions, the first step of which is to "boot into CWM, CMRecovery, or TWRP." However, I do not have any of these custom recoveries flashed on my Padfone X. Is there a way I can boot custom recovery off an external microsd or something?
Note: upon attempting the "fastboot flash recovery CMrecovery.img" command, the cmd window returns the following:
Code:
target reported max download size of 1879048192 bytes
sending 'recovery' <11220 KB>...
OKAY [ 0.438s ]
writing 'recovery'...
FAILED <remote: can't flash unsigned image>
finished. total time: 0.444s
EDIT: Problem has been resolved, used
Code:
fastboot boot twrp.img
and restored stock.
Click to expand...
Click to collapse
Glad I was able to point you into the right direction.