So I just got my TFP today and already unlocked it with the ASUS tool and have been trying to get CWM on it for the past hour now. I've been following the instructions from here: http://transformerprimeroot.com/tra...orkmod-recovery-5-8-2-0-on-transformer-prime/
Basically I can get to fastboot and select it, but it just sits on "starting fastboot usb download protocol". When I enter in the command to flash CWM (fastboot -i 0x0b05 flash recovery recovery-clockwork-5.8.2.0-tf201.img) I get the message <Waiting for device>. I let it sit for 15 minutes my first try and at least 25 minutes my second try. I tried with keeping the USB cord plugged in the entire time. I'm beyond frustrated. Can anyone help? Did I just get a **** TFP that won't work with fastboot for some reason?
EDIT- Well ****, turns out I didn't have the drivers installed. Kind of embarrassing but I guess that's what I get for abandoning Android for so long. Mods can feel free to delete this.
I also had this problem using fastboot on linux. If on linux you need to be in root for fastboot to work. Also make sure you can see the device to ensure fastboot is working by using
sudo fastboot -i 0x0b05 devices
Related
I cannot get fastboot to find my TF201. I ran the unlock tool tonight on my stock .21 prime. I have booted into fastboot usb download mode with the Power + Vol Down, wait for RCK to pass, then Vol Down to select fastboot then Vol Up to confirm.
I have tried under my native Ubuntu 11.10 x64 install and Windows 7 x64. Under windows, I removed my already installed SGS2 drives and replaced them with the Naked 0.61 Drivers as found here: [ADB/FB/APX Driver] Universal Naked Driver Beta 0.6.1. I rebooted Windows and tried again to no luck:
Code:
./fastboot devices
or
Code:
fastboot.exe devices
as per respective OS.
Each command just echos an empty line, any tips?
EDIT:
I just went for it anyway and it apparently flashed the recovery
Code:
fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
but now I am sitting with a completed blue progress bar and am scared to reboot the device.
EDIT 2:
I took a leap and power cycled the device, looks like recovery is in and good to go. Looks like since we need to specify the vendor_id for our devices, the devices command, or anything else for that matter fails to work properly (fastboot reboot, fastboot devices, etc.).
Hope this will help anyone else having issues.
Thanks.
SOLVED fastboot does not find device
Would like to expand your answer!
i am working with asus transformer prime TF201
i had a problem (SOLVED) where fastboot would not find device.
Code:
<waiting for device>
i fixed it by specifying asus vendor id (in this instance i was flashing a new recovery)
Code:
./fastboot -i 0x0b05 flash recovery recovery.img
Hope this helps it took me 2 days to figure that out
PEACE!
Thanks!
I ran into the same issue where the TF201 was not shown as a device.
You saved me from hours of pain!
how ot change vendor id
I'm having the same problem; need to install twrp via fastboot, but windows does not recognize the device. I have 'waiting for device'.
Can anyone explain how to change/specify the vendor id?
EDIT: nevermind, the 0x0b05 is the vendor ID, I already did that but the problem remained. In the end I switched computers and this solved it.
I'm having a somewhat similar problem except I connect my Prime and I see a serial, but it's not the serial of my Prime. I run the command:
fastboot -i 0x050b flash recovery flatline_tf201.img
and I get the message that it copied successfully, but I don't see any blue progress line and when I boot into recovery, I get the triangle; presumably because there is no recovery image.
I've tried it from three different windows systems (2 64bit and 1 32bit) with the same results. I am also unable to connect via ADB.
Any suggestions?
My phone is HTC Desire. Using to enter fastboot to install 4EXT recovery but failed
I can use adb command form cmd.
E:\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT0ARPL02347 device
But When I restart my phone and enter to FASTBOOT is shows FASTBOOT USB in the screen but nothing happen when I issue command "fastboot devices"
E:\sdk\platform-tools>fastboot devices
E:\sdk\platform-tools>
So I am no noob and have unlocked and rooted 50+ androids in my day. I have personally done 12 Atrixs in the last 12 months. Today I got my hands on a free Atrix and decided I'd go ahead and do the norm.
I used the http://forum.xda-developers.com/showthread.php?t=1182871 method which I always do and proceeded as normal.
I ran the script like always and got the failed to boot 0x1000 error like always. Got the phone to run fastboot and ran the fix but on cmd for the first time ever I got the <waiting for device> message that never seemed to stop "waiting." I have never ran into this before and did everything as I normally do... I'm guessing I hard bricked it but have no idea how that could be.
Since I can get the phone into fastboot is there a way to recover the device and retry the method? If not no biggie as it was free and I could really care less as I have my Atrix, a S II and a Skyrocket lying around that I use regularly but would love to get this bad boy up and running. Please let me know ASAP if there is a fix...
Soo when you type cmd and choose your option
if it says "waiting for device " reboot it into "Fastboot mode
make sure u press volume Up
so then phone should read" Starting fastboot protocal" and type Fastboot devices your output should read
List of devices connected
then your device id like TA084327
something like that then type
fastboot oem unlock
ltdanno360 said:
Soo when you type cmd into pc go to your fastboot folder then type fastboot oem unlock
if it says "waiting for device " unplug phone reboot it into "Fastboot mode
make sure u press volume Up
so the phone will read Starting fastboot protocal Then plug into Pc
Click to expand...
Click to collapse
No no no... I run the script from http://forum.xda-developers.com/showthread.php?t=1182871 and I get to the point where it says "Starting fastboot protocal" and then the script tells me to plug in phone. I do and then I hit enter on script and it then says <waiting for device> ...... therein lies the problem.
*Solved
Not quite sure what has gone wrong with my tablet but it seems that my recovery partition has been wiped (no recovery) and my boot.img has also gone.
What caused it:
I was installing Ubuntu onto my Prime and I got to the stage where I flash the boot.img. However, fastboot said it was sending the file, then writing the file and reported both "<OKAY>". However, I am not receiving a blue bar as other people say they do, yet I have done before when following the NVFlash guide (yes, I have all my blobs and things backed up).
Anyway, I have tried installing the Universal Driver and it seems to work (shows up in Device Manager). However, any commands that I send to the tablet do not seem to work (fastboot FLASH COMMANDS).
Commands I've entered: fastboot -i 0x0b05 flash boot prime-sdlinux.blob, fastboot -i 0x0b05 flash recovery twrp.blob
Also, "commands such as fastboot -i 0x0b05 erase recovery" result in: erasing 'recovery' ... FAILED (command write failed (Unknown error))
I'm really stuck and it's getting late, not sure what to do. Hope you guys can help me out.
PS: Not sure if this helps but, I cannot turn off the device. It constantly reboots just to hang at the Asus Eee Pad Screen or to hang at the Fastboot screen (when volume_down is held).
EDIT: After troubleshooting some more I have found that uninstalling the naked driver and letting Windows find a driver will actually allow me to send a reboot command (and it'll work). However, any fastboot flash commands do not seem to work. No Progress Bar appears and any commands sent after a flash command do not work (can't reboot after sending a flash command).
Hold the volume up while pressing the power button for about 15 seconds or until it vibrates then release them and it should power off for you.
did you make an nvflash backup?
else try
Code:
downloaded the latest Virtuous Prime ROM.
extract the ZIP file and pull the file called 'blob'
rename the file as boot.blob and move it to the TOOLS folder and open Command Prompt
from the TOOLS folder, type: fastboot -i 0x0b05 flash boot boot.blob
then type: fastboot -i 0x0b05 reboot
this should make you capable to go to recovery again
Open a command prompt; type adb push virtuous_prime.....zip /sdcard/
Wait until you get a confirmation message
Flash the rom like you normally do
Done
found this solution somewhere....
I do have an NVFlash backup, just not with me right now. Will test the above method first. And thanks for the method of turning it off! Although I know it's still on. Just in APX mode.
EDIT: Windows XP (run through VirtualBox on my laptop) seems to pickup my tablet in fastboot devices now. However, I'm still not seeing a progress bar after flashing again, and have the same problems as before (cannot reboot from fastboot). Still doesn't work. I've run fastboot through a native Windows 7 machine and a Windows XP installation on a Mac. Not sure what else I can try if fastboot isn't working.
EDIT2: It seems that I no longer have the error "FAILED (command write failed (Unknown error))" with certain commands.
First, you are in the wrong section, it should be in Q&A.
Second why didn't you try nvflash?
See this: http://forum.xda-developers.com/showpost.php?p=29204285&postcount=228
I believe the reason why fastboot is not working is because you are flashing blobs whilst using AndroidRoot.mobi bootloader.
http://forum.xda-developers.com/showpost.php?p=28875606&postcount=80
I believe you'll have to blobunpack the blob and then flash the raw img files instead.
That actually makes perfect sense! Would have taken me ages to figure out by myself. Thought it was perm-bricked until I got back to my NVFlash backup files. Will try it out.
kokopuphz said:
I believe the reason why fastboot is not working is because you are flashing blobs whilst using AndroidRoot.mobi bootloader.
http://forum.xda-developers.com/showpost.php?p=28875606&postcount=80
I believe you'll have to blobunpack the blob and then flash the raw img files instead.
Click to expand...
Click to collapse
I was in a similar situation until someone pointed me in this direction. Using BlobUnpack on both recovery and boot images gives you boot.LNX.SOS and Recovery.img.SOS (or similar names)
Flashing these solved my issues.
Yea, it worked. Thanks a lot for the help guys. Just takes one extra step to flash something now, kinda annoying, but definitely worth knowing that your tablet is brick-proof.
I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.
So I just got this tablet HDX 8.9 (apollo) today and I was trying to unlock bootloader, got unlock code flashed vulnerable aboot and twrp then thought i would test twrp (and maybe get a full backup) before using the unlock code but have been stuck in fastboot since then.
the tablet is now stuck in fastboot mode, responds to fastboot devices but fastboot -i commands don't work.
I booted into ubuntu live cd. it was a pain just to install adb and fastboot in 18.04 and 18.10 (which I had handy). fastboot -i commands did work there but then on rebooting the live cd fastboot wouldn't show anything when i had to go through the torture of installing adb and fastboot again.
i've been into bulk mode and back twice but still stuck at fastboot. need help here please. thanks in advance.
Fixed it! Since it was accepting fastboot -i commands from Ubuntu, tried with a liveCD of v20.04.1.
ADB/fastboot was much less of a pain in the hind side installing on this version and I only needed to give the one unlock command. So all done!