I let my cousin borrow my prime while I went out of town for a few days and when I came back my tablet was completely wiped. All that it has on it is fastboot and fastboot only has two options wipe data or usb. My tablet won't show up in adb but when I use fastboot devices command I get 00000 fastboot. I don't know if fastboot is seeing my tablet or not I'm just hoping I can fix it. After taking with people in other forums I've been trying this method
http://forum.xda-developers.com/showthread.php?p=27354963&highlight=fastboot#post27354963
It seems to work until I get to where I have to flash Roach's modded CWM recovery. After inputting the command this is the result I get.
sending 'recovery' (5398 KB)... FAILED (command write failed (Unknown error)) finished
Does anyone here have any idea what's happening with my prime? If so please help, it will be very much appreciated.
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
Sent from my Transformer Prime TF201 using Tapatalk 2
Second option, tell your cousin he owes you 500 bucks, go buy a new prime or infinity and give him the one he broke.
Skitsofrantik said:
I let my cousin borrow my prime while I went out of town for a few days and when I came back my tablet was completely wiped. All that it has on it is fastboot and fastboot only has two options wipe data or usb. My tablet won't show up in adb but when I use fastboot devices command I get 00000 fastboot. I don't know if fastboot is seeing my tablet or not I'm just hoping I can fix it. After taking with people in other forums I've been trying this method
http://forum.xda-developers.com/showthread.php?p=27354963&highlight=fastboot#post27354963
It seems to work until I get to where I have to flash Roach's modded CWM recovery. After inputting the command this is the result I get.
sending 'recovery' (5398 KB)... FAILED (command write failed (Unknown error)) finished
Does anyone here have any idea what's happening with my prime? If so please help, it will be very much appreciated.
Click to expand...
Click to collapse
it is highly unlikely it is bricked for good, you could try running through the steps to enable nvflash, and at the final step rather than booting into android (which you cant) run fastboot boot recovery
I've tried that but thanks for the input
SOTK said:
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
I've tried every driver I could find. I just can't get it to show up in adb devices. going through fastboot seems to work though when i use the command for fastboot to reboot the tablet it reboots. I think I will try TWRP though.
Click to expand...
Click to collapse
lilstevie said:
it is highly unlikely it is bricked for good, you could try running through the steps to enable nvflash, and at the final step rather than booting into android (which you cant) run fastboot boot recovery
Click to expand...
Click to collapse
I'm gonna try this. Thanks for the tip.
Skitsofrantik said:
SOTK said:
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
I've tried every driver I could find. I just can't get it to show up in adb devices. going through fastboot seems to work though when i use the command for fastboot to reboot the tablet it reboots. I think I will try TWRP though.
Click to expand...
Click to collapse
At one time, I had issues getting my PC to recognize my Prime too. You need to completely remove all prior device drivers and THEN install the naked drivers. There's a tutorial in that thread as well as a tool (I think) which you can run on your PC to help you remove previous drivers. Once you know they are gone, follow the directions to install the naked drivers. Its a little cumbersome but the process works. You're gonna keep having issues until you get your PC to recognize your Prime in ADB and Fastboot. You say Fastboot works kinda? So, in the device manager in Windows, it shows your Prime is connected as you're in Fastboot mode? If it doesn't or if it shows as an unrecognized device, I don't see how you're gonna be able to fix your issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Tried NVFlash
I tried NVFlash but I can't get past the first step. When I do this command fastboot -i 0x0b05 flash staging ebtblob.bin I get this result:
sending 'staging' (998 KB)...
OKAY [0.962s]
writing 'staging'...
FAILED (unknown status code)
finished. total time: 10970.597s
Anyone know what's going wrong?
SOTK said:
Skitsofrantik said:
At one time, I had issues getting my PC to recognize my Prime too. You need to completely remove all prior device drivers and THEN install the naked drivers. There's a tutorial in that thread as well as a tool (I think) which you can run on your PC to help you remove previous drivers. Once you know they are gone, follow the directions to install the naked drivers. Its a little cumbersome but the process works. You're gonna keep having issues until you get your PC to recognize your Prime in ADB and Fastboot. You say Fastboot works kinda? So, in the device manager in Windows, it shows your Prime is connected as you're in Fastboot mode? If it doesn't or if it shows as an unrecognized device, I don't see how you're gonna be able to fix your issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Where is the tutorial and tool? I went through it and didn't see it. Even when I completely remove the drivers, when I plug the tablet into the computer when there are no drivers it tries to install it's own drivers and sometimes they install and I get Asus android device in the device manager with Asus fastboot interface as the driver. other times it just fails to install drivers. I know if I get the drivers right I can limp this tablet back to life but it just seems like no matter what drivers i use i just cant get the tablet to show up in adb.
Click to expand...
Click to collapse
Skitsofrantik said:
SOTK said:
Where is the tutorial and tool? I went through it and didn't see it. Even when I completely remove the drivers, when I plug the tablet into the computer when there are no drivers it tries to install it's own drivers and sometimes they install and I get Asus android device in the device manager with Asus fastboot interface as the driver. other times it just fails to install drivers. I know if I get the drivers right I can limp this tablet back to life but it just seems like no matter what drivers i use i just cant get the tablet to show up in adb.
Click to expand...
Click to collapse
If you go into device manager and rightclick the asus android device then update drivers. Now do not let windows choose, do it manually and point windows to the naked driver... Also there are 2 drivers.. one for intel 86 and the other for amd... 64 the numbers are at the end of the file name if I remember correctly... be sure to choose the correct one for your pc chip otherwise yeah you can do it all day and get no where... When you try adb, I will assume you are in recovery mode and not fastboot because they are 2 different horses... If you only have fastboot then you should consider installing an older version of twrp like 2.1... I posted it somewhere in here.... that should get you into recovery where you can adb a rom to the prime.... check for posts by me, I have explained this a few times here.....
From a previous post.....
go here ....http://forum.xda-developers.com/show....php?t=1615990 this is twrp.... download then follow the fastboot install instructions
At this point you probably want to follow the nvflash instructions to install the custom bootloader since twrp says it needs it... go back here and follow instructions... http://forum.xda-developers.com/show....php?t=1774352
start again from ******now boot to recovery....
From the sounds of it you have no rom atm... no big deal... download a rom.. i suggest blackbean or eos...
blackbean found here... http://rootzwiki.com/index.php?/topi...ackbean-(8-15)
eos found here.. http://forum.xda-developers.com/show....php?t=1782413
Download and install http://forum.xda-developers.com/show....php?t=1426502 naked drivers.... follow the instructions...
I prefer blackbean... anyways.... now download nvflash from here http://androidroot.mobi/?p=452
Unzip the file.. put your rom where you find adb.exe shoudl be in C:\nvflash\tf201_nvflashpack if you put the file in C:
*******Now.... boot to recovery... connect tab to the pc.... with the windows open (nvflashpack) clcik in the window... press and hold shift button the right clcik mouse and select open command prompt here... this should give you the command prompt.
Now copy this adb devices right click in the command prompt window and paste... press enter... you should see your transformer...
now type adb push /name of rom you downloaded .zip/ sdcard
This should push the rom to your tab... it will take about 5 minutes be patient....
Install the zip through cwm....
After you accomplish this, you should complete the nvflash instructions and make your backups...
Click to expand...
Click to collapse
Related
I have bricked or atleast semi bricked my Folio and i dont know if it can be fixed. It began with damaged internal sd, so i try the format zip but no luck. May device have been like this 3 days now. I NEED HELP, AND YES I HAVE ASKED IN GENERAL SECTION. but i didnt get an answer for days. I need help by someone who can tell me how to set up fastboot. My folio boots i can get to clockwork recovery and i can get in to fastboot mode. I have working ADB on my computer. The install fails when recovery is writing boot.img iget this message: assert failed
write_raw_image("/cache/boot.img", "linux")
E:Error in /sdcard/FolioMod.zip
(Status 7)
It installs system.img fine. So i was thinking i could fastboot boot.img to the device and maybe it boots. So i put Folio in Fastboot mode,insert usb, and update driver, go to command prompt and write fastboot devices all i get is:
? fastboot
Is there anything special i have to keep in mind to setup fastboot for Folio. I used the fastboot that came with SDK. Do i have to add something more to .inf file for fastboot? Do have to use any special fastboot just for Tegra2 devices? Is my fastboot mode damaged? Please i need help i have waited for days in general section not one answer. Hoping on better luck here in the dev section
Are you on Windows or linux?
Normally if adb is working, fastboot should be working too. Just boot your folio into fastboot mode and connect it to your pc. Type 'fastboot devices', if something shows up you are fine (might be just a bunch of ???s).
Otherwise (on win) you need to modify the driver a little. There is a howto around here. I will add a link when I found it.
€: http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
But I think if adb is already working, you will be fine. Just make sure you have a recent version of fastboot from the android sdk. Older versions are incompatible with tegra2 based devices.
mblaster said:
Are you on Windows or linux?
Normally if adb is working, fastboot should be working too. Just boot your folio into fastboot mode and connect it to your pc. Type 'fastboot devices', if something shows up you are fine (might be just a bunch of ???s).
Otherwise (on win) you need to modify the driver a little. There is a howto around here. I will add a link when I found it.
€: http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
But I think if adb is already working, you will be fine. Just make sure you have a recent version of fastboot from the android sdk. Older versions are incompatible with tegra2 based devices.
Click to expand...
Click to collapse
I had entered the part to .inf file but havent done the echo part in command prompt, will try now. Its weird as hell all i get when writing fastboot devices is a ? fastboot. Its a windows Vista 32 im using and SDK 08. And when i enter this echo 0x955 i just get that its the wrong path.
I got fastboot working didnt know it could be ? fastboot when it was connected. I kept getting it so i tryed to send some commands and it got thru. **** so i have had it working for days. I have flashed the boot.img via fastboot and am now trying to do an advanced restore of a nandroid. Will see how it goes. If its not working can i flash system.img and boot.img? Will that work? Well atleast now i can flash standard recovery and send it to toshiba
Probleem Solved Thank you mblaster, you wrote it could look like this when writing fastboot devices: ?????? or atleast something like it so i thought maybe i am connected as my said: ? fastboot . So i tryed some commands and they got thru. So to anyone who tryes to install fastboot try commands. I was waiting for days(dumb, i know). So now im back and kickin, watch out
Moved to proper forum
Ok so I wanted to try out some new Tom's besides the cm7 weeklies and figured I should do a deeper wipe than just the normal cwm wipe but I can't seem to figure put how to get fastboot working I set it up on my phone and navigated to the file ln my laptop and just issued a reboot so I knew how it worked before I started wiping but it just sat there and never rebooted I have is there additional files I need besides the fastboot exe to do a wipe. And is it advised to erase all the partitions before flashing a new rom or is it not needed
Sent from my MB860 using XDA App
I don't know for sure so I'll just tell you what I have in my folder where I have my fastboot.exe. I also have the adb files which include:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
Not sure if that means anything though. Have you updated your drivers recently? What OS does your laptop use? I know if you have the wrong drivers it can cause problems like using 32 bit drivers on a 64 bit system.
As far as wiping, it is recommended especially if you go from a different ROM to another. I usually use this which was suggested by a user named @CaelanT:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
jonnyboyC13 said:
Ok so I wanted to try out some new Tom's besides the cm7 weeklies and figured I should do a deeper wipe than just the normal cwm wipe but I can't seem to figure put how to get fastboot working I set it up on my phone and navigated to the file ln my laptop and just issued a reboot so I knew how it worked before I started wiping but it just sat there and never rebooted I have is there additional files I need besides the fastboot exe to do a wipe. And is it advised to erase all the partitions before flashing a new rom or is it not needed
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Well just updated motohelper and no luck still no response in fastboot maybe my procedure is wrong in what way do you wipe
Sent from my MB860 using XDA App
ok learning process. didn't even realize you needed adb to use fastboot. so i got that on my laptop.
adb isn't recognizing my phone either so i think i'm still missing something
Right now i know i have the motohelper install adb and and the fastboot files. I may have some other files when i first got my phone that just installed with it was still blurred but i don't know
Do you have "USB Debugging" checked when using adb?
How did you unlock the bootloader? It seems weird that it's not working since you need an unlocked bootloader to run CM7 (which you said you had) and you need fastboot to unlock the bootloader. I don't understand what could have changed since then. Are you using a different computer now?
Just to make sure we're on the same page, are you putting the phone into fastboot before you issue the fastboot commands?
[Turn off phone->Hold Vol down and press power->Keep holding Vol down until it says "Fastboot" at the top of the screen->Release Vol down and then press Vol up]
jonnyboyC13 said:
ok learning process. didn't even realize you needed adb to use fastboot. so i got that on my laptop.
adb isn't recognizing my phone either so i think i'm still missing something
Right now i know i have the motohelper install adb and and the fastboot files. I may have some other files when i first got my phone that just installed with it was still blurred but i don't know
Click to expand...
Click to collapse
Yep usb debugging is on
honestly i don't know why it's not working it just says waiting for device, all i need to do is just put into fastboot on my phone, navigate to the fastboot.exe on the command promt. Then plug in in the phone and issues the command correct. are there any other things that need to be running to get it working. is there another step before this for the computer to recognize my phone
There are only 2 things I can think of after the details you have given me:
1. Are you making sure it says "Starting fastboot protocol" at the top of the screen before you issue the commands?
and
2. Have you rechecked your drivers? To me this sounds like the issue if everything else is in place. Try plugging the phone into your computer while it's turned on and switching the "USB Connection" from "None" to "Windows Media" then to "Mass Storage" and finally "Phone Portal", making sure you allow it to install any proper drivers on each connection (takes a few seconds). It's also important to select OK each time you change the connection.
Also, did you get the correct adb files in the same folder as fastboot.exe?
Other than these 2 suggestions I don't know what could be causing the issue. At this point I would be seeking help myself.
jonnyboyC13 said:
Yep usb debugging is on
honestly i don't know why it's not working it just says waiting for device, all i need to do is just put into fastboot on my phone, navigate to the fastboot.exe on the command promt. Then plug in in the phone and issues the command correct. are there any other things that need to be running to get it working. is there another step before this for the computer to recognize my phone
Click to expand...
Click to collapse
ok did some more searching it is the driver just have to figure out what i need to get on my computer now
Ok haven't wiped yet but i got the right driver on my computer now adb now can discover my device and a did a fastboot reboot and it worked cool beans.
just in case anyone else is having a similar problem i had to download the MOTODEV usb driver here http://developer.motorola.com/docstools/USB_Drivers/ and yes had to sign up for MOTODEV to do it but whatever got it working and i'm pumped
So I unlocked my Prime on .21 and I've been trying to get a recovery on it with no luck. Obviously, I can't use Rom or Goo Manager as it's not rooted. I can't flash a zip file because I don't have a recovery. I've tried installing it in fastboot with no luck. From what I've read fastboot is not an operable command on the Prime so I tried installing the universal naked driver and using the provided commands with it. According to the directions I have to unistall previous drivers....I have a LOT. If that's the case I might as well try on a fresh PC as I have Moto, HP, HTC, Samsung, etc drivers installed.
Back on topic - TWRP's page ( http://teamw.in/project/twrp2/93) provides commands for "ADB / Terminal" to install their recovery but the commands provided are clearly for terminal emulator which I'd have to be rooted to use. So how do these commands convert to ADB?
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Any help is much appreciated! I really don't want to downgrade to root and install recovery. If I can't get fastboot or adb to work, I'll keep that as plan C.
Sent from my DROID RAZR using Tapatalk
Use fastboot it's easier. http://transformerprimeroot.com/tra...orkmod-recovery-5-8-2-0-on-transformer-prime/ and obviesly replace cwm with twrp.
Sent from my Transformer Prime TF201 using XDA Premium App
Makrilli said:
Use fastboot it's easier. http://transformerprimeroot.com/tra...orkmod-recovery-5-8-2-0-on-transformer-prime/ and obviesly replace cwm with twrp.
Sent from my Transformer Prime TF201 using XDA Premium App
Click to expand...
Click to collapse
I cannot get fastboot commands to work on my Prime. Do you have the Universal Naked Drivers installed and have you used this method?
Sent from my DROID RAZR using Tapatalk
I used this one and I didn't have to install any drivers, worked out of the box. What do you mean about you couldn't get fastboot to work. Did you also write -i 0x0B05 between fastboot and flash
?
Sent from my sgs2 running cm9
I probably should post this as a seperate guide, here :
-----
* Install ADB and Fastboot onto your system, as well as the universal USB naked driver which you can find on this forum.
* Search for DotTech install ADB and Fastboot - follow this guide, it's probably the easiest way to get a working fastboot and ADB environment up and running.
* Enable USB debugging on the tablet under developer options.
* Set up the universal driver, you'll need to reboot your TF201 and hold the POWER and VOLUME DOWN buttons until you see some text in the top corner. Do NOT press volume up to go into Recovery Image mode or you'll just walk into a dead end.
* Shortly after you'll see three icons, press volume down ONCE and then volume UP once, the USB icon in the middle should be highlighted and you should see text saying "Entering Fastboot Protocol" or similar.
* Plug the USB cable into the tab and the PC, test whether you have a working fastboot install by typing fastboot -i 0x0b05 reboot, if your tablet reboots without you touching it, then you've got working fastboot access. Remove the cable, reboot to fastboot mode as described above.
* Meantime, download openrecovery-twrp-2.1.3-tf201.blob from the team win site, and stuff it in the same directory that you set up Fastboot/ADB, rename it to twrp.blob. Plug your tablet back in and then issue the command fastboot -i 0x0b05 flash recovery twrp.blob , if this goes to plan you'll see a couple of lines of text on the command window which will tell you that it's been successfully flashed in. YOU STILL DO NOT HAVE ROOT THOUGH, SO NO SILLY STUFF
* Finally, download the ROM of your choice, place it in the base /sdcard directory, then reboot the tab and hold POWER and VOLUME DOWN, when you see the text, this time hit VOLUME UP, and you'll be sent into the team win recovery suite, at this point you can wipe and flash the newly prepared ROM as per normal.
* For the first occasion I -strongly- recommend you use Virtuous Prime-S as you can generate a solid backup environment out of it, as well as the fact it's not too departed from Stock, so it's a good way to break yourself in.
----
Hope this helps.
Hobbesian said:
I probably should post this as a seperate guide, here :
-----
* Install ADB and Fastboot onto your system, as well as the universal USB naked driver which you can find on this forum.
* Search for DotTech install ADB and Fastboot - follow this guide, it's probably the easiest way to get a working fastboot and ADB environment up and running.
* Enable USB debugging on the tablet under developer options.
* Set up the universal driver, you'll need to reboot your TF201 and hold the POWER and VOLUME DOWN buttons until you see some text in the top corner. Do NOT press volume up to go into Recovery Image mode or you'll just walk into a dead end.
* Shortly after you'll see three icons, press volume down ONCE and then volume UP once, the USB icon in the middle should be highlighted and you should see text saying "Entering Fastboot Protocol" or similar.
* Plug the USB cable into the tab and the PC, test whether you have a working fastboot install by typing fastboot -i 0x0b05 reboot, if your tablet reboots without you touching it, then you've got working fastboot access. Remove the cable, reboot to fastboot mode as described above.
* Meantime, download openrecovery-twrp-2.1.3-tf201.blob from the team win site, and stuff it in the same directory that you set up Fastboot/ADB, rename it to twrp.blob. Plug your tablet back in and then issue the command fastboot -i 0x0b05 flash recovery twrp.blob , if this goes to plan you'll see a couple of lines of text on the command window which will tell you that it's been successfully flashed in. YOU STILL DO NOT HAVE ROOT THOUGH, SO NO SILLY STUFF
* Finally, download the ROM of your choice, place it in the base /sdcard directory, then reboot the tab and hold POWER and VOLUME DOWN, when you see the text, this time hit VOLUME UP, and you'll be sent into the team win recovery suite, at this point you can wipe and flash the newly prepared ROM as per normal.
* For the first occasion I -strongly- recommend you use Virtuous Prime-S as you can generate a solid backup environment out of it, as well as the fact it's not too departed from Stock, so it's a good way to break yourself in.
----
Hope this helps.
Click to expand...
Click to collapse
Thanks for the tutorial. I'm fairly familiar with adb and fastboot. My problem lies in the fastboot drivers. I was not able to install the Universal Naked Drivers. If I tried to install them over the existing drivers it failed. If I deleted the existing drivers, I was not able locate the device to install the new drivers. I would either reboot the computer OR unplug and plug the device in but each time the old drivers would auto install. Again, thanks for your input and I'll give this a go when I have some more time.
Sent from my DROID RAZR using Tapatalk
I had a similar issue getting the USB drivers in the first time. The best bet is to uninstall, unplug and then re-plug the tab in fastboot and then intercept the little window doohickey that comes up when it says it's dealing with an unknown device and tell it specifically not to go fishing on the web, then point it at the driver folder.
Hobbesian said:
I had a similar issue getting the USB drivers in the first time. The best bet is to uninstall, unplug and then re-plug the tab in fastboot and then intercept the little window doohickey that comes up when it says it's dealing with an unknown device and tell it specifically not to go fishing on the web, then point it at the driver folder.
Click to expand...
Click to collapse
I didn't have an issues with the adb drivers. I don't why fastboot is being such a pain.
Sent from my DROID RAZR using Tapatalk
joshw0000 said:
I didn't have an issues with the adb drivers. I don't why fastboot is being such a pain.
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
All the problems you see is with people that is using Windows.
Sent from my i9250
Hobbesian said:
I had a similar issue getting the USB drivers in the first time. The best bet is to uninstall, unplug and then re-plug the tab in fastboot and then intercept the little window doohickey that comes up when it says it's dealing with an unknown device and tell it specifically not to go fishing on the web, then point it at the driver folder.
Click to expand...
Click to collapse
Just wanted to shoot a quick thanks. I finally found time to tinker with my Prime and turns out I had the drivers properly installed but was booting to recovery not fastboot, hence fastboot device wasn't found. When booted properly, it flashed the first try. I'm now TWRP recovered and Gummy rom'ed. Its amazing how one can overlook a simple step and until someone plainly states it, they never even question it.
Sent from my Transformer Prime using Tapatalk
so its been already 2 months no way i can fix this still doing the same thing turn on boots and then loops to CWM same thing over n over and no connection to my computer so basicly now i feel i waisted 500 billz and used it from feb till now and no way i can fix it no ideas and asking around how can i putit back to live no answers yet nada so my guessin is not way a big amount and send it to asus or is there still a way to save it? i really missed my prime u use it alot but since still stuck on loop from EEE Pad to CWM and no mount :crying:
klutch said:
so its been already 2 months no way i can fix this still doing the same thing turn on boots and then loops to CWM same thing over n over and no connection to my computer so basicly now i feel i waisted 500 billz and used it from feb till now and no way i can fix it no ideas and asking around how can i putit back to live no answers yet nada so my guessin is not way a big amount and send it to asus or is there still a way to save it? i really missed my prime u use it alot but since still stuck on loop from EEE Pad to CWM and no mount :crying:
Click to expand...
Click to collapse
I am having the same problem man......I can't get the PC to detect my prime so I can't push any .zip
if you get adb to work, this is a solution http://forum.xda-developers.com/showthread.php?t=1661128&highlight=boot+loop
@klutch
what have you done before your prime stuck in the boot loop?
tried to flash anything or something like that
if i remember correctly you can't mount the prime as a removeable disk in CWM unless they fixed it
your best bet is to go into CWM and use adb to push the flashable zip files in there
you can do that by the following commands
Code:
adb push [directory/file name.zip] [/mnt/sdcard/]
if your device is not recognized by windows, then ADB does not work. that's the OP's problem.... and mine as well. ~$230 to fix my prime.
have you already tried to enter fastboot mode and flash a fresh rom from there?
I was able to get the PC detect my TFP by installing the driver from this link
[ADB/FB/APX Driver] Universal Naked Driver 0.7
You should be able to adb afterwards....Then follow 'OPTION 1a" from this link
[HOW-TO] Unbrick your Transformer Prime (or not)
I installed nvflash to make sure this won't happen again
hope this helps!
naked drivers
urboy4mbx said:
I was able to get the PC detect my TFP by installing the driver from this link
[ADB/FB/APX Driver] Universal Naked Driver 0.7
You should be able to adb afterwards....Then follow 'OPTION 1a" from this link
[HOW-TO] Unbrick your Transformer Prime (or not)
I installed nvflash to make sure this won't happen again
hope this helps!
Click to expand...
Click to collapse
i dont get how to install naked drivers when everytime i plug in my prime it just says unknown device in device manager and when i try to update the driver it says i have the best or latest driver. plz someone help me!!!!
InkD_up_G33k said:
i dont get how to install naked drivers when everytime i plug in my prime it just says unknown device in device manager and when i try to update the driver it says i have the best or latest driver. plz someone help me!!!!
Click to expand...
Click to collapse
in CWM while the TFP is plugged to your PC, click "update driver" and make sure you point to the location where "android_winusb.inf" file is located.
if you are in CWM the TFP will pick up "android_winusb.inf" driver
if you are in fastboot mode the TFP will pick up "android_apxusb.inf" driver
Also, I had to try on 3 different computers to make this work.
i just found out wat happen the original usb asus was messed up and i brought one on ebay and it worked so all this for a USB cable i was going crazy
urboy4mbx said:
in CWM while the TFP is plugged to your PC, click "update driver" and make sure you point to the location where "android_winusb.inf" file is located.
if you are in CWM the TFP will pick up "android_winusb.inf" driver
if you are in fastboot mode the TFP will pick up "android_apxusb.inf" driver
Also, I had to try on 3 different computers to make this work.
Click to expand...
Click to collapse
Ok so wen i plug in my tfp while in cwm the only thing that pops up in device manager is unown device in the usb controllers section thats it and wen i try to update driver it says i i have the best driver already and im pointing it to a folder on my desktop with the naked drivers and nothing evn with have disk it says its not 64 bit or sumtn. im about ready to give up and just sell it to someone who prolly can fix it cuz i cant seem to get naked drivers to install to let the computer recognize my tfp so i can adb
InkD_up_G33k said:
Ok so wen i plug in my tfp while in cwm the only thing that pops up in device manager is unown device in the usb controllers section thats it and wen i try to update driver it says i i have the best driver already and im pointing it to a folder on my desktop with the naked drivers and nothing evn with have disk it says its not 64 bit or sumtn. im about ready to give up and just sell it to someone who prolly can fix it cuz i cant seem to get naked drivers to install to let the computer recognize my tfp so i can adb
Click to expand...
Click to collapse
as I asked earlier, did you try to set your prime into fastboot mode and flash a fresh rom from there?
if it does not work with windows, you could try linux, e.g. an ubuntu live cd. download the linux fastboot from here
you can flash a new rom with
fastboot -i 0x0b05 flash boot "path to rom blob"
or new recovery using
fastboot -i 0x0b05 flash recovery "path to recovery image blob"
unfortunately i'm not able to supply links to download fastboot, sorry for that.
klutch said:
i just found out wat happen the original usb asus was messed up and i brought one on ebay and it worked so all this for a USB cable i was going crazy
Click to expand...
Click to collapse
wow, I thought you tried a diff cable already?? well, glad it was just the cable for you! I tried 3 diff cables on mine and it still didn't work
apfel.kuchen said:
as I asked earlier, did you try to set your prime into fastboot mode and flash a fresh rom from there?
if it does not work with windows, you could try linux, e.g. an ubuntu live cd. download the linux fastboot from here
you can flash a new rom with
fastboot -i 0x0b05 flash boot "path to rom blob"
or new recovery using
fastboot -i 0x0b05 flash recovery "path to recovery image blob"
unfortunately i'm not able to supply links to download fastboot, sorry for that.
Click to expand...
Click to collapse
yea when i hold power and volume down it doesnt work as usual when it tells you to press up in the next five seconds. and ive tried restoring back up and flashing a new rom but it just boots up into cwm and my sdcard slot is ****ed up becuz of my lil cousins sticking **** inside the slot so it doesnt read anymore so i cant push files or put files on like that either.
pressing vol- + power and vol+ after 5 seconds should lead you into recovery (CWM) but fastboot is somewhat different. if you do not press vol+ after 5 seconds but either wait longer, you will see a screen where to select how to proceed (USB mode, android, and something else). if you select usb and then connect the tablet to your pc you are in fastboot mode and should be able to flash rom and recovery using the fastboot tool on your PC. using this you wouldn't need a working sd card, only a rom and/or recovery in blob format.
apfel.kuchen said:
pressing vol- + power and vol+ after 5 seconds should lead you into recovery (CWM) but fastboot is somewhat different. if you do not press vol+ after 5 seconds but either wait longer, you will see a screen where to select how to proceed (USB mode, android, and something else). if you select usb and then connect the tablet to your pc you are in fastboot mode and should be able to flash rom and recovery using the fastboot tool on your PC. using this you wouldn't need a working sd card, only a rom and/or recovery in blob format.
Click to expand...
Click to collapse
yes i know that but thats the problem im not able to go into fastboot i tried it, it reboots into recovery on its own and i know the only way im going to unbrick this is by adb but my device isnt showing up on my computer just unknown device under usb contollers which i tried to install the naked drivers but is unable to
hmm.. ok thats bad.
do you have a linux machine to check if it is a windows problem?
because it doesn't really make sense to me that CWM is working but adbd not.
i may have found a solution
this is just my experience but it seems like the different adb's that people are posting of the forums are outdated and dont work properly with some primes. I have tried several the windows task manager said "asus transformer prime adb interface" with the naked drivers as soon as i used the adb included in the sdk from <developer.android.com/sdk/index.html> it worked. so install the sdk then in the command prompt navigate to the platform tools inside where it was installed us the adb.exe found there.
as far as using the wrong drivers when you remove the device there might be the option to delete the device driver check that then scan for new devices......point it to where ever you unziped
this may not work for you but this is what finally resurrected my prime after 24 hours
Okay I just had the same problem ... after some research and some trial and error I was able to fix my prime.
First to make your life simple open a command prompt. You will have a flashing cursor next to the directory that you command prompt defaults to.
In my case it was c:/users/peter
You can put the sdk files anywhere on your computer but if you put them in the default command prompt folder you don't have to change the directory with dos commands.
Next with your prime not connected go into the device manager and delete any instances of the prime. Reboot your PC.
Next download the universal naked drivers
Connect your prime, if you go back into device manager you'll find it under USB devices. Click on upgrade drivers and navigate to the universal naked drivers. It should install if not your universal naked drivers might be outdated but uninstalling / deleting the previous instance of your prime should take care of any issues.
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
After this I recommend installing the androidroot.mobi custom boot loader and nvflash to make your prime unbrickable I also changed my recovery from cwm to twrp2 to help eliminate this from happening again.
Same here
What if you only have TWRP Recovery and not CMW? I have the exact same problem, but none of my machines will even detect a new device to find drivers for. I have a laptop with Ubuntu 12.04, another laptop with Windows XP, and an iMac with Snow Leopard. All have Android SDK and ADB but I can not get either to detect the device in Recovery mode. I tried fast boot, but every time I click the USB symbol, the TFP just locks up and freezes and still no detection. Can anyone help? I know if I can get it detected, I will be able to handle the rest.
pcdonovan said:
Okay I just had the same problem ... after some research and some trial and error I was able to fix my prime.
First to make your life simple open a command prompt. You will have a flashing cursor next to the directory that you command prompt defaults to.
In my case it was c:/users/peter
You can put the sdk files anywhere on your computer but if you put them in the default command prompt folder you don't have to change the directory with dos commands.
Next with your prime not connected go into the device manager and delete any instances of the prime. Reboot your PC.
Next download the universal naked drivers
Connect your prime, if you go back into device manager you'll find it under USB devices. Click on upgrade drivers and navigate to the universal naked drivers. It should install if not your universal naked drivers might be outdated but uninstalling / deleting the previous instance of your prime should take care of any issues.
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
After this I recommend installing the androidroot.mobi custom boot loader and nvflash to make your prime unbrickable I also changed my recovery from cwm to twrp2 to help eliminate this from happening again.
Click to expand...
Click to collapse
I was having some SD card issues, as far as not being able to delete files from my sd via root apps, getting errors when trying to make back ups via my back-up pro/titanium so i was point to this thread http://forum.xda-developers.com/showthread.php?t=1670824. I read all instructions(as always) and already had a working ADB in recovery and fastboot, so i flashed that zip and my Windows7 pc no longer recognises my Prime.
So no im stuck with no OS on my prime, Only twrp-Touch recovery and no access to push any files to prime via fastboot or ADB.
i have the naked drivers and all.
so i was thinking that i would try to use Ubuntu,, but i need to aet up adb/sdk on this prior to that.
But i was reaching out to see if anyone had some fix/help to get my prime running??? i have never bricked a device, but im starting to feel like this is a sort of "soft" brick... lol
http://forum.xda-developers.com/showthread.php?t=1670824
Just the same thing
jyarborough said:
I was having some SD card issues, as far as not being able to delete files from my sd via root apps, getting errors when trying to make back ups via my back-up pro/titanium so i was point to this thread http://forum.xda-developers.com/showthread.php?t=1670824. I read all instructions(as always) and already had a working ADB in recovery and fastboot, so i flashed that zip and my Windows7 pc no longer recognises my Prime.
So no im stuck with no OS on my prime, Only twrp-Touch recovery and no access to push any files to prime via fastboot or ADB.
i have the naked drivers and all.
so i was thinking that i would try to use Ubuntu,, but i need to aet up adb/sdk on this prior to that.
But i was reaching out to see if anyone had some fix/help to get my prime running??? i have never bricked a device, but im starting to feel like this is a sort of "soft" brick... lol
http://forum.xda-developers.com/showthread.php?t=1670824
Click to expand...
Click to collapse
Hey man, exactly the same thing happend to my tf201 a couple of days ago. Since then i've been trying everything found on different treads and forums with no luck.
Actual State:
-Able to boot to TWR and to fastboot
-I can connect via ADB in Recovery mode and push small files but not large files (like a ROM)
-When connected via ADB in Fastboot mode my device is detected by windows7 but when adb devices is issued returns Error: device not found
At this point a little hand would be appreciated..
L-MachO said:
Hey man, exactly the same thing happend to my tf201 a couple of days ago. Since then i've been trying everything found on different treads and forums with no luck.
Actual State:
-Able to boot to TWR and to fastboot
-I can connect via ADB in Recovery mode and push small files but not large files (like a ROM)
-When connected via ADB in Fastboot mode my device is detected by windows7 but when adb devices is issued returns Error: device not found
At this point a little hand would be appreciated..
Click to expand...
Click to collapse
When you're in fastboot, you can't access your device with ADB. Try "fastboot devices" and it should show up there.
These are the steps I took when I was stuck at the splash screen with only access to fastboot. If you have access to fastboot (by holding volume down + powering on, then choosing fastboot/usb icon) then you should be able to fix it.
geo.z said:
When you're in fastboot, you can't access your device with ADB. Try "fastboot devices" and it should show up there.
These are the steps I took when I was stuck at the splash screen with only access to fastboot. If you have access to fastboot (by holding volume down + powering on, then choosing fastboot/usb icon) then you should be able to fix it.
Click to expand...
Click to collapse
thanks for that. i was able to get into fast boot,, but since my pc would not see my tab,, no commands can be given. so i am now setting up adb on ubuntu 12.4, and seeing if i get a fresh start can i get access. i amd following Xsmagical on this on over here
http://forums.team-nocturnal.com/showthread.php/773
geo.z said:
When you're in fastboot, you can't access your device with ADB. Try "fastboot devices" and it should show up there.
These are the steps I took when I was stuck at the splash screen with only access to fastboot. If you have access to fastboot (by holding volume down + powering on, then choosing fastboot/usb icon) then you should be able to fix it.
Click to expand...
Click to collapse
That's right geo.z but now I'm trying "fastboot devices" and it returns nothing, not even an error, my windows device manager keeps recognizing the device as "ASUS Android Bootloader Interface" and I'm using the Naked Driver.
L-ManchO, that's weird. Try uninstalling the drivers, disconnect the device and then reconnect and reinstall the naked drivers.
jyarborough, have you tried using the Universal Naked Drivers? I also had the problem of not being able to see the device, but uninstalling drivers and installing the new ones worked for me.
geo.z said:
L-ManchO, that's weird. Try uninstalling the drivers, disconnect the device and then reconnect and reinstall the naked drivers.
jyarborough, have you tried using the Universal Naked Drivers? I also had the problem of not being able to see the device, but uninstalling drivers and installing the new ones worked for me.
Click to expand...
Click to collapse
I just did as you suggested and now windows sees the device as "ASUS Fastboot Interface", anyways the "fastboot devices" returns nothing as before, I tried the "fastboot -i 0x0b05 flash recovery twrp.blob" and I get the following message:
On the computer side:
sending `recovery` (5876 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5.054s
At the same time On the TF201 I get:
Failed to process command download:005bd068 error(0x120003)
L-MachO said:
I just did as you suggested and now windows sees the device as "ASUS Fastboot Interface", anyways the "fastboot devices" returns nothing as before, I tried the "fastboot -i 0x0b05 flash recovery twrp.blob" and I get the following message:
On the computer side:
sending `recovery` (5876 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5.054s
At the same time On the TF201 I get:
Failed to process command download:005bd068 error(0x120003)
Click to expand...
Click to collapse
Try a different USB port? Maybe a different computer? It's possible that this is a hardware problem, hopefully it isn't the cable or the port on the TF201.
geo.z said:
L-ManchO, that's weird. Try uninstalling the drivers, disconnect the device and then reconnect and reinstall the naked drivers.
jyarborough, have you tried using the Universal Naked Drivers? I also had the problem of not being able to see the device, but uninstalling drivers and installing the new ones worked for me.
Click to expand...
Click to collapse
i have . i am starting fresh with ubuntu,, not window,, and so far im ok..well on my way. fast boot can see my tab
L-MachO said:
I just did as you suggested and now windows sees the device as "ASUS Fastboot Interface", anyways the "fastboot devices" returns nothing as before, I tried the "fastboot -i 0x0b05 flash recovery twrp.blob" and I get the following message:
On the computer side:
sending `recovery` (5876 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5.054s
At the same time On the TF201 I get:
Failed to process command download:005bd068 error(0x120003)
Click to expand...
Click to collapse
are you putting this " -i 0x0b05 " after you type fastboot?
L-MachO said:
I just did as you suggested and now windows sees the device as "ASUS Fastboot Interface", anyways the "fastboot devices" returns nothing as before, I tried the "fastboot -i 0x0b05 flash recovery twrp.blob" and I get the following message:
On the computer side:
sending `recovery` (5876 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5.054s
At the same time On the TF201 I get:
Failed to process command download:005bd068 error(0x120003)
Click to expand...
Click to collapse
Any luck
Sent from my ice cream sandwich
geo.z said:
Try a different USB port? Maybe a different computer? It's possible that this is a hardware problem, hopefully it isn't the cable or the port on the TF201.
Click to expand...
Click to collapse
Tried on a different computer (desktop) running win7 x64, used the Naked Drivers, device reported as "ASUS Fastboot Interface", after running "fastboot devices" nothing came up and for the "fastboot -i 0x0b05 flash recovery" got the same message as before.
Now I'm really worried
Interesting thread in case you're still facing issues:
http://forum.xda-developers.com/showthread.php?t=478820
The people there solved using different methods:
1. USB cable with ferrite core on both ends
2. different USB port
3. using USB deview to uninstall all usb drivers, and install one by one, as Windows is notorious for installing drivers over and over for each USB hub, eventually causing conflicts
4. plugging in the usb only after issuing the fastboot command, and having the command prompt say "waiting for phone"
I hope you get things working.
kokopuphz said:
Interesting thread in case you're still facing issues:
http://forum.xda-developers.com/showthread.php?t=478820
The people there solved using different methods:
1. USB cable with ferrite core on both ends
2. different USB port
3. using USB deview to uninstall all usb drivers, and install one by one, as Windows is notorious for installing drivers over and over for each USB hub, eventually causing conflicts
4. plugging in the usb only after issuing the fastboot command, and having the command prompt say "waiting for phone"
I hope you get things working.
Click to expand...
Click to collapse
Great suggestions kokopuphz, here's the summary of each step:
1. USB cable with ferrite core on both ends
I used ferrite cores adapters (from a local electronics shop) on both ends of the USB cable to reduce transmission noise, but got the same message when sending the recovery
2. different USB port
I even used a different PC with a brand new installation of windows 7 (same situation)
3. using USB deview to uninstall all usb drivers, and install one by one, as Windows is notorious for installing drivers over and over for each USB hub, eventually causing conflicts
I assume step (2) would cover this one.
4. plugging in the usb only after issuing the fastboot command, and having the command prompt say "waiting for phone"
Same messages received with after this step.
I'm thinking of a USB cable issue here, what do you think guys?
Sounds likely. Got a spare microUSB cable?
Yeah, the only common denominator would be the usb cable and tfp, thus likeliness of the cable being an issue could be high. I take it you've tried both docked and undocked?
Sent from my SO-01C using xda app-developers app
kokopuphz said:
Yeah, the only common denominator would be the usb cable and tfp, thus likeliness of the cable being an issue could be high. I take it you've tried both docked and undocked?
Sent from my SO-01C using xda app-developers app
Click to expand...
Click to collapse
Well I only have the tablet not the docking, so I'm stock with the USB cable probability at this point. I'm ordering one on Amazon, I guess an original one is my best be.
:crying: OMG how I miss my TF.
OK.. so I'm back up and running. What I had to do was to put the. Blob file in the same folder as adb to shortened the path. Once I got the path command right this is what I types
Adb push /your rom.blob /data /media /
At first I was pushing to /sdcard/ and the prime did not see it. I read through the op and saw the suggestion to push it to data media so I did.. did a manual reboot into twrp recovery and navigated to SD card where I saw my rom waiting there for me
Fastboot method would not work for me so I updated my drivers and did it all adb
Sent from my Transformer Prime TF201 using Tapatalk 2
It's Alive!!!!!
jyarborough said:
OK.. so I'm back up and running. What I had to do was to put the. Blob file in the same folder as adb to shortened the path. Once I got the path command right this is what I types
Adb push /your rom.blob /data /media /
At first I was pushing to /sdcard/ and the prime did not see it. I read through the op and saw the suggestion to push it to data media so I did.. did a manual reboot into twrp recovery and navigated to SD card where I saw my rom waiting there for me
Fastboot method would not work for me so I updated my drivers and did it all adb
Sent from my Transformer Prime TF201 using Tapatalk 2
Click to expand...
Click to collapse
Guys, I just received a new USB cable yesterday and tried once again, guess what? It WORKED..now I have my TF running like a charm once again.
Definitely the stock USB cable is a little too fragile and of course it's unbelievable all the error codes and messages I got because of a damaged cable.
Thanks a lot guys for your support and suggestions.
Kind of off topic but has anyone used Goo Manager to flash twrp over CWM?
Sent from my SCH-I535 using xda premium