I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
xdeslitx said:
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
Click to expand...
Click to collapse
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
xdeslitx said:
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
Click to expand...
Click to collapse
sbdags said:
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
Click to expand...
Click to collapse
The above is correct, you are in fastboot if you see this (similar to download mode on samsung devices for use with ODIN).
Be sure to add path to environmental variables so that you can use fastboot commands at prompt (if in NT (windows) environment)
sbdags said:
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
Click to expand...
Click to collapse
i tried running the command " fastboot devices" and it doesnt see my tf700
i have all drivers loaded
Poser said:
The above is correct, you are in fastboot if you see this (similar to download mode on samsung devices for use with ODIN).
Be sure to add path to environmental variables so that you can use fastboot commands at prompt (if in NT (windows) environment)
Click to expand...
Click to collapse
i added the path to environmental variables.
Fastboot works fine for me.
Suggest you go over to the nvflash thread and download the windows drivers.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
xdeslitx said:
i tried running the command " fastboot devices" and it doesnt see my tf700
i have all drivers loaded
Click to expand...
Click to collapse
Isn't that adb commands you are trying to run. I.e., adb devices. I think you are confusing fastboot.
What are you trying to do?
sbdags said:
Fastboot works fine for me.
Suggest you go over to the nvflash thread and download the windows drivers.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
Isn't that adb commands you are trying to run. I.e., adb devices. I think you are confusing fastboot.
What are you trying to do?
Click to expand...
Click to collapse
fastboot devices is also a fastboot command from what i understand...i was trying to run that command to see if the computer can even see my tablet in fastboot...which it doesnt.
and i actually did get the drivers from the nvflash thread because that's what i am trying to accomplish
what does your tablet look like when you are in fastboot mode?
because i am doubting the fact that mine is even in that mode...i get the feeling that it gets stuck when trying to load fastboot
xdeslitx said:
fastboot devices is also a fastboot command from what i understand...i was trying to run that command to see if the computer can even see my tablet in fastboot...which it doesnt.
and i actually did get the drivers from the nvflash thread because that's what i am trying to accomplish
what does your tablet look like when you are in fastboot mode?
because i am doubting the fact that mine is even in that mode...i get the feeling that it gets stuck when trying to load fastboot
Click to expand...
Click to collapse
It just says starting Fastboot mode. It never changes from that.
im going to try and uninstall/reinstall the drivers to see if thatll work
finally got it to work...had to reload my drivers
haha so i did the whole nvflash thing but i dont really know how it works
all i know is that itll keep me from bricking my tf700
xdeslitx said:
finally got it to work...had to reload my drivers
haha so i did the whole nvflash thing but i dont really know how it works
all i know is that itll keep me from bricking my tf700
Click to expand...
Click to collapse
You can still brick your device but it's 100% recoverable, at least if it's not a hardware failure. Just make sure to keep your backup files safe.
Pretoriano80 said:
You can still brick your device but it's 100% recoverable, at least if it's not a hardware failure. Just make sure to keep your backup files safe.
Click to expand...
Click to collapse
are there any instructions on how to recover using these files in case of brick?
i didnt see any on the thread under development
xdeslitx said:
are there any instructions on how to recover using these files in case of brick?
i didnt see any on the thread under development
Click to expand...
Click to collapse
There's no guide so far, but i'm sure you would get some help from xda users when needed.
cool thanks for the replies
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
thunderger said:
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
Click to expand...
Click to collapse
Try to use this command to check if fastboot it's working : " fastboot -i 0x0b05 reboot ". If your device reboot after sending that command it means you can use fastboot just fine.
To be honest i've seen many bricks reports from people that tried to only flash the JB bootloader so imo the best way to get the JB bootloader is to flash the official JB firmware, then install the latest TWRP OR CWM recovery via fastboot, use the custom recovery to make a backup of the stock rom. Once you've did all that you can install CM10 just fine but also you will have the opportunity to go back to stock JB in case you need to.
thunderger said:
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
Click to expand...
Click to collapse
Fastboot devices does not work on this device. I've used fastboot to swap recovery images several times and update to the JB bootloader by itself. It definitely works as a whole.
Pretoriano80 said:
Try to use this command to check if fastboot it's working : " fastboot -i 0x0b05 reboot ". If your device reboot after sending that command it means you can use fastboot just fine.
To be honest i've seen many bricks reports from people that tried to only flash the JB bootloader so imo the best way to get the JB bootloader is to flash the official JB firmware, then install the latest TWRP OR CWM recovery via fastboot, use the custom recovery to make a backup of the stock rom. Once you've did all that you can install CM10 just fine but also you will have the opportunity to go back to stock JB in case you need to.
Click to expand...
Click to collapse
I've tried this command many times, and all I ever get is < waiting for device > and nothing else. This is getting annoying as hell. I've tried so many different things, all with the same result. I guess I'll just have to wait until there is an exploit found to root the JB firmware without having to use fastboot, then use TWRP from Goomanager, and hopefully by then there will be a zip of CWM Recovery.
Related
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
Hi all.
I went to update my Recovery today to a new TWRP.
I have not had problems in the past.
When I boot into fastboot it just says "Starting Fastboot USB download protocol".
The drivers are properly installed and made sure under device manager.
Any idea's guys?
When I type fastboot devices I don't get anything.
Thanks for the help!
Also tried in Ubuntu still no luck >_<
are you using pc or mac, kinda dumb queston but alas it makes a difference
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
bige914 said:
are you using pc or mac, kinda dumb queston but alas it makes a difference
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I am using a Asus Laptop. Thanks for the response!
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
sjj1991 said:
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
Click to expand...
Click to collapse
got the same issue guys
Anyone get anywhere with this? I just unlocked, then went to flashing a recovery but get the same "fastboot usb download protocol" message..
We are all stuck with this unless we send it to asus for RMA
Sent from my VS840 4G using xda premium
SpyFi said:
Also tried in Ubuntu still no luck >_<
Click to expand...
Click to collapse
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
tobdaryl said:
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
Click to expand...
Click to collapse
the problem is not the computer itself, the real problem is that the tablet doesn't get in fastboot mode...
Thank you for the update.
SpyFi said:
Hi all.
I went to update my Recovery today to a new TWRP.
I have not had problems in the past.
When I boot into fastboot it just says "Starting Fastboot USB download protocol".
The drivers are properly installed and made sure under device manager.
Any idea's guys?
When I type fastboot devices I don't get anything.
Thanks for the help!
Click to expand...
Click to collapse
sjj1991 said:
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
Click to expand...
Click to collapse
matt95 said:
got the same issue guys
Click to expand...
Click to collapse
partypage said:
Anyone get anywhere with this? I just unlocked, then went to flashing a recovery but get the same "fastboot usb download protocol" message..
Click to expand...
Click to collapse
tobdaryl said:
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
Click to expand...
Click to collapse
Try this:
-use unlock tool
-boot tablet into USB MODE
(it will say fastboot mode,waiting)
-using the steps,copying over the fastboot files to one folder, with TWRP as the recovery, run fastboot command.
-done successfully,you be good
Click to expand...
Click to collapse
I'm not the author of this process, but apparently it works.
I haven't tried, because I use terminal emulator for my adb command
I decided to automate the process of entering commands. Post
philos64 said:
Try this:
I'm not the author of this process, but apparently it works.
I haven't tried, because I use terminal emulator for my adb command
Click to expand...
Click to collapse
thank you, i'll try this out tomorrow! :good:
no way, i can't get it to fastboot damn it
---------- Post added at 11:45 PM ---------- Previous post was at 11:16 PM ----------
ok i solved the problem just now...
1-reboot the tablet in bootloader while connected to usb
2-use vol down to navigate to the usb mode and then vol up
3-the tablet won't show nothing but actually it is connected
4-proceed to any fastboot command
hope this helps
I had this issue when I first started flashing stuff (although I was flashing CWM not TWRP)
In my experience, if you don't see anything listed in fastboot devices, it doesn't matter because it still flashes.
Just try using the flash command (fastboot -i 0x0b05 flash blah blah blah.blah) and see if it works.
You -should- be able to see your device in "adb devices", and that's really what matters.
Also, what matt95 said is exactly what I do. Whether it shows anything or not, I just flash my stuff. Works fine, but I also don't use fastboot alot because with the new changes to the bootloader, one can flash stock through CWM now without having to fastboot flash it.
I'm having the same problem here with fast boot. I want to run NV Flash so I can update to the JB bootloader for CM updates. I've tried simple commands like reboot and nothing works. Any other thoughts?
jm700wx said:
I'm having the same problem here with fast boot. I want to run NV Flash so I can update to the JB bootloader for CM updates. I've tried simple commands like reboot and nothing works. Any other thoughts?
Click to expand...
Click to collapse
my solution above didn't help?
matt95 said:
my solution above didn't help?
Click to expand...
Click to collapse
I'm in the same wagon as all you guys, I just tried that and I can't get into fastboot still. Still waiting for device
---------- Post added at 01:10 PM ---------- Previous post was at 01:02 PM ----------
I'm sorted now, I didn't realise that we needed a different command
I was using
Code:
fastboot flash recovery recovery-jb-touch.img
instead of the correct method of using
Code:
fastboot -i 0x0B05 flash recovery recovery-jb-touch.img
This worked perfectly
it's same as this:
== Part 3 - Install recovery and rooting ==
Let's start with installing the recovery
1) Download these 2 files:
- Jellybean recovery with fastboot files: Fastboot files + JB recovery
- Root files => Root files
- You can also download the new CWM Touch recovery if you don't like TWRP: CWM Touch recovery thread or TWRP recovery and download this file : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
- TWRP: fastboot -i 0x0b05 flash recovery twrp.blob
- CWM: fastboot -i 0x0b05 flash recovery CWM-Touch.blob
6) A blue bar will appear and the recovery will be installed, when the blue bar is filled press volume up + power button to reboot into the tablet.
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
Click to expand...
Click to collapse
I tried GOOMANAGER but wasn't rooted and I think that might have screwed up my Fastboot possibly....when I try to do boot into recovery now and select the RCK option I get the dead / sick droid and it says error every time. I don't know what to do now! Any ideas? I also tried to downgrade from 10.6.1.14.10 to 10.6.1.14.8 so I can root and install TWRP and ROMS, but need to get into recovery to do that. I cannot get into Fastboot / recovery to load stuff!!! HELP!!!!!!!!
TerrorTodd said:
I tried GOOMANAGER but wasn't rooted and I think that might have screwed up my Fastboot possibly....when I try to do boot into recovery now and select the RCK option I get the dead / sick droid and it says error every time. I don't know what to do now! Any ideas? I also tried to downgrade from 10.6.1.14.10 to 10.6.1.14.8 so I can root and install TWRP and ROMS, but need to get into recovery to do that. I cannot get into Fastboot / recovery to load stuff!!! HELP!!!!!!!!
Click to expand...
Click to collapse
You are aready in the fastboot mode when you are in the bootloader menu. Look on the upper left corner, you will see the fastboot is active...
LetMeKnow said:
You are aready in the fastboot mode when you are in the bootloader menu. Look on the upper left corner, you will see the fastboot is active...
Click to expand...
Click to collapse
Ok, but I can't do anything from there can I? Don't I have to select one of the three options? RDK Android or Wipe? RDK is what allows you to load zips right? I can not load that it gives me the dead android...
TerrorTodd said:
Ok, but I can't do anything from there can I? Don't I have to select one of the three options? RDK Android or Wipe? RDK is what allows you to load zips right? I can not load that it gives me the dead android...
Click to expand...
Click to collapse
Yes, you can fastboot your custom recovery. Can you tell me what you intend to do with your device? Your rom, kernel, and version?
LetMeKnow said:
Yes, you can fastboot your custom recovery. Can you tell me what you intend to do with your device? Your rom, kernel, and version?
Click to expand...
Click to collapse
I've unlocked the bootloader and I wanted to root it. I'd like to put a custom recovery TWRP and custom ROM probably CM 10.1 or something like that. Currently I'm running stock ROM build JOP40D.US_epad- 10.6.1.14.10-2-13-8-1. (I understand this build is not rootable so I was going to either downgrade or try to load a custom ROM) Kernel version 3.1.10-gb1a9af5 [email protected] #1
When I get to the fastboot menu there are the three options to chose from and when I select the RCK I get the dead droid with error underneath every time. So I have been unable to load anything.
TerrorTodd said:
I've unlocked the bootloader and I wanted to root it. I'd like to put a custom recovery TWRP and custom ROM probably CM 10.1 or something like that. Currently I'm running stock ROM build JOP40D.US_epad- 10.6.1.14.10-2-13-8-1. (I understand this build is not rootable so I was going to either downgrade or try to load a custom ROM) Kernel version 3.1.10-gb1a9af5 [email protected] #1
When I get to the fastboot menu there are the three options to chose from and when I select the RCK I get the dead droid with error underneath every time. So I have been unable to load anything.
Click to expand...
Click to collapse
The dead adroid is the stock recovery. There are two option for you to install the custome recovery.
1. Downgrade your firmware version and use motochopper to get root before using goo
2. Use fastboot to install your custome recovery
Read this thread: http://forum.xda-developers.com/showthread.php?t=2252563
The last few pages have an instruction and link to use fastboot.... Good luck..
and itightu
LetMeKnow said:
The dead adroid is the stock recovery. There are two option for you to install the custome recovery.
1. Downgrade your firmware version and use motochopper to get root before using goo
2. Use fastboot to install your custome recovery
Read this thread: http://forum.xda-developers.com/showthread.php?t=2252563
The last few pages have an instruction and link to use fastboot.... Good luck..
Click to expand...
Click to collapse
Thanks. I'll have to find that. I think that is the main problem for me. I don't think I'm doing the Fastboot thing correctly. Thanks I'll check it out tonight for sure!!
TerrorTodd said:
Thanks. I'll have to find that. I think that is the main problem for me. I don't think I'm doing the Fastboot thing correctly. Thanks I'll check it out tonight for sure!!
Click to expand...
Click to collapse
Ok Scott's too rebooted the machine into Fastboot and the USB Driver is not recognized. I have downloaded the USB drivers from ASUS Sync program and unstalled Sync.
In the top corner it says:
Key driver not found...Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
The options at the boot menu are RCK ANDROID WIPE DATA
Not sure how to get the drivers to recognize....without that I'm dead in the water...any thoughts?? I thought for sure that the ones from ASUS would do the trick....
Should I have other menu options at Fastboot?
TerrorTodd said:
Ok Scott's too rebooted the machine into Fastboot and the USB Driver is not recognized. I have downloaded the USB drivers from ASUS Sync program and unstalled Sync.
In the top corner it says:
Key driver not found...Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
The options at the boot menu are RCK ANDROID WIPE DATA
Not sure how to get the drivers to recognize....without that I'm dead in the water...any thoughts?? I thought for sure that the ones from ASUS would do the trick....
Should I have other menu options at Fastboot?
Click to expand...
Click to collapse
You are already in the fastboot mode. If you have downloaded scott recovery, you can start using it.
LetMeKnow said:
You are already in the fastboot mode. If you have downloaded scott recovery, you can start using it.
Click to expand...
Click to collapse
But I cannot as the USB does not recognize the device when it goes into fastboot. Works fine when in normal operation I can access the tablet through the USB, but in fastboot it does not recognize it. Can't seem to find a solution all USB drivers I have loaded do not work. Updating the drivers from the window on PC that opens does not work. UGH!!!!!!
TerrorTodd said:
But I cannot as the USB does not recognize the device when it goes into fastboot. Works fine when in normal operation I can access the tablet through the USB, but in fastboot it does not recognize it. Can't seem to find a solution all USB drivers I have loaded do not work. Updating the drivers from the window on PC that opens does not work. UGH!!!!!!
Click to expand...
Click to collapse
Can you explain how you do it? You may miss a step or something..
LetMeKnow said:
Can you explain how you do it? You may miss a step or something..
Click to expand...
Click to collapse
I followed this to the "T"
This is the summary from the Scott post:
1. Download the "install recovery.zip" from the above link
2. Extract it some where on your computer, prefer in the document folder
3. Check and make sure that the "USB debugging" is ticked on your device under the developer option menu
4. Download the TWRP 2.6.1.0.blob file from here: http://techerrata.com/browse/twrp2/tf700t
5. Rename it to "recovery.blob" and put it in same folder with all the fastboot files so that you can use Scott's script
6. Double click on the Scott's script or bat file and follow the instructions on the screen until you see the phrase says "write is okay or completed"
7. When it is finished, you can now reboot your device, done..
When it reboots it will not load drivers and I cannot access the tablet / fastboot.
It shows this at fastboot and I cannot do anything. Happens with script and if I manually do it. I can't use fastboot no matter what I try the USB drivers do not recognize the tablet.
Key driver not found...Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
The options at the boot menu are RCK ANDROID WIPE DATA
TerrorTodd said:
I followed this to the "T"
This is the summary from the Scott post:
1. Download the "install recovery.zip" from the above link
2. Extract it some where on your computer, prefer in the document folder
3. Check and make sure that the "USB debugging" is ticked on your device under the developer option menu
4. Download the TWRP 2.6.1.0.blob file from here: http://techerrata.com/browse/twrp2/tf700t
5. Rename it to "recovery.blob" and put it in same folder with all the fastboot files so that you can use Scott's script
6. Double click on the Scott's script or bat file and follow the instructions on the screen until you see the phrase says "write is okay or completed"
7. When it is finished, you can now reboot your device, done..
When it reboots it will not load drivers and I cannot access the tablet / fastboot.
It shows this at fastboot and I cannot do anything. Happens with script and if I manually do it. I can't use fastboot no matter what I try the USB drivers do not recognize the tablet.
Key driver not found...Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
The options at the boot menu are RCK ANDROID WIPE DATA
Click to expand...
Click to collapse
You can try to use the window prompt to change the directory to the fastboot.exe folder and type this command to see if you can get to your recovery: fastboot reboot-recovery or fastboot reboot recovery
LetMeKnow said:
You can try to use the window prompt to change the directory to the fastboot.exe folder and type this command to see if you can get to your recovery: fastboot reboot-recovery or fastboot reboot recovery
Click to expand...
Click to collapse
I don't think that will help as the Recovery gives me the dead droid every time. I was trying to replace the recovery in this exercise. This is more of a pain that its worth I think. Phones are so much easier to do this with. UGH!
TerrorTodd said:
I don't think that will help as the Recovery gives me the dead droid every time. I was trying to replace the recovery in this exercise. This is more of a pain that its worth I think. Phones are so much easier to do this with. UGH!
Click to expand...
Click to collapse
Follow this post - - > http://forum.xda-developers.com/showthread.php?p=30260444 <-- if you want to install the drivers.
Also make sure that you have a working fastboot environment and run the command prompt from the folder where fastboot.exe is located. The dead android you are seeing when accessing the recovery it's normal with Stock Recovery, nothing is wrong with your device.
BTW, i suppose that your device is already unlocked because otherwise Fastboot won't work.
Pretoriano80 said:
Follow this post - - > http://forum.xda-developers.com/showthread.php?p=30260444 <-- if you want to install the drivers.
Also make sure that you have a working fastboot environment and run the command prompt from the folder where fastboot.exe is located. The dead android you are seeing when accessing the recovery it's normal with Stock Recovery, nothing is wrong with your device.
BTW, i suppose that your device is already unlocked because otherwise Fastboot won't work.
Click to expand...
Click to collapse
Dead Droid with the word "Error" underneath it is normal?
Yes the device is unlocked. I cannot get into recovery and cannot get Fastboot to work because the stupid USB drivers don't recognize the tablet. Works fine when not in Fastboot mode, but when goes into fastboot no USB. It's maddening!!!!
Yes dead android it's ok.As for the driver just follow the link i posted and install the driver manually,that will solve the driver issue.
Pretoriano80 said:
Yes dead android it's ok.As for the driver just follow the link i posted and install the driver manually,that will solve the driver issue.
Click to expand...
Click to collapse
Will do this tonight when I get home from work and will report back!
TerrorTodd said:
Will do this tonight when I get home from work and will report back!
Click to expand...
Click to collapse
Ok so the problem was that I had the damn keyboard connected and was trying to connect through that. I took that off and UBS recognized immediately!! Going to try and root now etc. I will report back again!
Keyboard connected = BAD
TerrorTodd said:
Ok so the problem was that I had the damn keyboard connected and was trying to connect through that. I took that off and UBS recognized immediately!! Going to try and root now etc. I will report back again!
Keyboard connected = BAD
Click to expand...
Click to collapse
What Windows version are you running? Win 8 doesn't seem to recognize the fastboot drivers, or maybe it was that you have to change the option of Windows only using Microsoft signed drivers?? Can't quite remember. But lots of people were unsuccessful getting fastboot to work in Win8.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
jchen221 said:
Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
Click to expand...
Click to collapse
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Heisenberg said:
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Click to expand...
Click to collapse
I'm sorry for this mistake.
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
jchen221 said:
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
Click to expand...
Click to collapse
What command are you using while in fastboot mode?
Heisenberg said:
What command are you using while in fastboot mode?
Click to expand...
Click to collapse
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
jchen221 said:
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
Click to expand...
Click to collapse
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Heisenberg said:
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
jchen221 said:
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
Click to expand...
Click to collapse
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install , reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
Heisenberg said:
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
Click to expand...
Click to collapse
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
I have the same problem.
jchen221 said:
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
Click to expand...
Click to collapse
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
pavanakshay said:
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
Click to expand...
Click to collapse
for me too bro same problem please help me
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
i too having the same problem bro the driver link is not working please send me the link thankyou in advance
i am also facing the same problem that phone loops into fast boot mode whenever turned on i do totally every kind of drivers softwares and etc like tenorshare but all in vain i guess at last that phone must be enabled usb debuging in order to be detected as a active adb device,i pratically do this stuff by using another phone with enabled debuging and it was an active device andd can be processed further but when i disabled the usb debugging of same phone it was not working with adb interface i hope you understand,,,,but a miracle happenend i removed the battery for about a week and suddenly i pluged and try to turn it on hola it starts from roms boot logo
HELP!!!!! Stuck on bootloop and fastboot not working
i was flashing twrp on infinix s4 withfast boot. after flashing the device is stuck on bootloop. the recovery is not accessible (i press the key combo nothing happens) and fastboot combination is also not working. i tried connecting it with adb cmd and ran the command "adb reboot bootloader" but no device is detected.
ps: the link for drivers is broken
hi guys,
i my shield is stuck on the nvidia logo when booting normally, if it brings up the bootloader, it shows unlocked but hitting continue caused it to freeze on the screen, recovery freezes on nvidia logo and fastboot protocol just brings it back to this screen. i orginally installed twrp and it confirmed successful flash of new os .... on reboot it bricked to its now state, i cant get into twrp or get my pc to see it to install a new copy
anyone got any ideas
thanks
@Fairmax don't click continue, it freezes because there is nothing to continue to, as long as you can enter bootloader your device isn't fully bricked. So, to fix your problem you will have to download official ROM from nvidia's site (https://developer.nvidia.com/shield-open-source find your model and click recovery images).
When you download latest ROM unzip it and follow the textual guide, but, there will be one file missing (i can't remember which one, user data maybe or something like that), don't worry and just continue with the next step. After you flash just reboot to system by holding power button. Good luck !
i cant seem to get it to be recognised by windows all i get is this-- Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed.--
trying to install nvidia usb driver via have disk bring up an error that the file is not usable with x64 system
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Fairmax said:
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Click to expand...
Click to collapse
Which command did you type in?
fpozar said:
Which command did you type in?
Click to expand...
Click to collapse
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Fairmax said:
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Click to expand...
Click to collapse
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
fpozar said:
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
Click to expand...
Click to collapse
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Fairmax said:
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Click to expand...
Click to collapse
You can also try flashing twrp and then lineageos or something from twrp.
fpozar said:
You can also try flashing twrp and then lineageos or something from twrp.
Click to expand...
Click to collapse
good news after a few hours of trying (usb dropped connection a few times then battery died) it finally works again .....been over 2 years since iv had this shield running after nvidia did the recall , now goto put a different rom on there so it dosnt update and kill itself
Hello I had a similar issue with my k1 tablet and ended up flashing factory images via adb fastboot and all flashed fine. Now my tablet is stuck on the boot screen with the green and white nvidia logo. How long does it take to boot please?
I have same issue too. I can load TWRP and flash the other partitions but TWRP shows un-mountable partitions and even a full stock ROM flash will not allow it to boot. I have a similar issue with a recall tablet. what did you do to fix it?