Database Info

[Q] Stuck on Google logo. Unable to push image file to phone... Please help.

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

Can't load fastboot??

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.

[Q] Asus TF300T Does Not Start Because Of The Clockwork Recovery

Tablet: ASUS TF300T, Unlocked.
SO: Cyanogen 10
Old (working) Recovery ROM: “recovery-jb.img”
New (NOT working) Recovery ROM: “recovery-clockwork-5.5.0.4-tf300t.img”
Keys combination don’t work, just the APX one.
Symptom: the cyanogen didn’t work well so I changed the recovery ROM. As the new Recovery locks when executing from the bootloader, I decided to restart in recovery directly from the cyanogen (power button –>Reset -> Reset into Recovery). VERY BAD IDEA: Now the tablet always tries to start in recovery and gets stuck on the start screen. I can only enter the APX with keys combination. I cant enter boot loader and ATX doesn’t recognize fastboot & adb instructions.

Hi, I believe cyanogen 10 uses a jellybean bootloader and CWM 5.5.0.4 is for an ICS bootloader, so you will need to flash CWM 6.0.2.3 which is for jellybean bootloader.
Have a look at link below and download 'recovery-jb.img' & follow the how to flash.
http://forum.xda-developers.com/showthread.php?t=1668173
Hope this helps.

santdiego said:
Hi!
I have cyanogen 10 installed, but I tried to change my Tf300T Clockwork Recovery with this rom: "recovery-clockwork-5.5.0.4-tf300t.img"
Click to expand...
Click to collapse
Why?

pjc21 said:
Hi, I believe cyanogen 10 uses a jellybean bootloader and CWM 5.5.0.4 is for an ICS bootloader, so you will need to flash CWM 6.0.2.3 which is for jellybean bootloader.
Have a look at link below and download 'recovery-jb.img' & follow the how to flash.
http://forum.xda-developers.com/showthread.php?t=1668173
Hope this helps.
Click to expand...
Click to collapse
Hi! the problem is that I am stuck in the first screen when I turn on the tablet. The keys don't respond, the USB dont work , I cant go into bootloader and cyanogen dont start. It is just in the first screen since it try to boot from recovery always.

NixZero said:
Why?
Click to expand...
Click to collapse
My cyanogen didn't work fine. When I saw this article I thought that maybe I had installed a wrong ROM so i change it with the instructive one.... bad idea...

Have a look here
http://forum.xda-developers.com/showthread.php?t=2034866

pjc21 said:
Have a look here
http://forum.xda-developers.com/showthread.php?t=2034866
Click to expand...
Click to collapse
I think it goes into APX mode, holding "vol +", the screen remains off but the USB recognizes the APX. What should I do at this point to re install the ROM CWM or enter bootloader? when I go out the APX mode all remains the same, the tablet is still stuck .

Ok I no expert here so anyone else please correct me if I'm wrong.
When you say the USB recognizes APK, do you mean (assuming your running windows) that you can see your tab in device manager - something like 'Asus Android Device - Asus Android Bootloader Interface'
If so try this, open cmd (I always run as admin, don't know if it makes a difference) navigate to your /android-sdk/platform-tools and type
'fastboot -i 0x0B05 device' and hopefully you will get a response about your device (tab). If you do I would assume you could then flash recovery, ie put recovery-jb.img in your platform-tools folder and in cmd type 'fastboot -i 0x0B05 flash recovery recovery-jb.img' once done type 'fastboot -i 0x0B05 reboot' and hopefully all will be good, you may then need to reflash you rom not sure.
If your tab does not show in device manager then I have no idea sorry.
Hope this helps.

pjc21 said:
Ok I no expert here so anyone else please correct me if I'm wrong.
When you say the USB recognizes APK, do you mean (assuming your running windows) that you can see your tab in device manager - something like 'Asus Android Device - Asus Android Bootloader Interface'
If so try this, open cmd (I always run as admin, don't know if it makes a difference) navigate to your /android-sdk/platform-tools and type
'fastboot -i 0x0B05 device' and hopefully you will get a response about your device (tab). If you do I would assume you could then flash recovery, ie put recovery-jb.img in your platform-tools folder and in cmd type 'fastboot -i 0x0B05 flash recovery recovery-jb.img' once done type 'fastboot -i 0x0B05 reboot' and hopefully all will be good, you may then need to reflash you rom not sure.
If your tab does not show in device manager then I have no idea sorry.
Hope this helps.
Click to expand...
Click to collapse
Hi! thx for your help. fastboot and adb don't recognize the tablet in APX mode. My PC recognize APX mode. I installed the drivers for APX and I have nvflash ready to work, but it seems to be useless without access to fastboot.

pjc21 said:
'fastboot -i 0x0B05 device'
Hope this helps.
Click to expand...
Click to collapse
respond "< waiting for device >"

You have to wait for NVflash for JB bootloader.

Hazard17 said:
You have to wait for NVflash for JB bootloader.
Click to expand...
Click to collapse
Hi I have NVflash from here: http://androidroot.mobi/t3_nvflash/ butt this method also use fastboot and i cant access to it.

Hi, sorry to say after alot of searching and reading looks like the only soluation is to send it to Asus for repair.

Screwed [Solved]

Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....

DarkDarwin said:
Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
Click to expand...
Click to collapse
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt

_that said:
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
Click to expand...
Click to collapse
Im afraid I wiped everything.I think my mistake was wiping in stock recovery instead of TWRP..thus it only boots to TWRP now.
I tried those commands but my machine was hanging like it was waiting for the device so I am going to uninstall and reinstall the windows drivers and ADB/Fastboot and do the commands again ,Ive been at work since this morning so ive got some honey dos then I can start trying it again.
Thanks so much!

When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..

DarkDarwin said:
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
Click to expand...
Click to collapse
So am I correct in saying that you can get to fastboot ?

lj50036 said:
So am I correct in saying that you can get to fastboot ?
Click to expand...
Click to collapse
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot

DarkDarwin said:
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
Click to expand...
Click to collapse
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.

We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh

berndblb said:
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
Click to expand...
Click to collapse
Thanks for trying to help me yesterday bro!

lj50036 said:
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
Click to expand...
Click to collapse
Any chance we could get a step-bystep on that? Pleeeaaase?

berndblb said:
Any chance we could get a step-bystep on that? Pleeeaaase?
Click to expand...
Click to collapse
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh

lj50036 said:
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
Click to expand...
Click to collapse
I went out and got a bigger SD card (64) to try and implement the DATA2SD script.I think I was successful as I now have new folders there named Android and Data that I didn't have before...However,I wonder if I was supposed to wipe anything before I re-flashed the ROM after inserting the formatted , partitioned SD...
I have to admit the I/O issue is extremely aggravating..I cant believe Asus marred an otherwise excellent device like that.

I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
Ok, when I boot up in android, I can use adb command reboot bootloader to boot in the bootloader.
When i then try fastboot erase system, it's still hangs with waiting for device..
The bootloader is not stuck, i can again boot up android..
it's impossible to open terminal, because the touch is going crazy..
Hmm, i'm trying something else.
I still had 10x tf300 for repair. there are multiple cracked with 5184n version.
I installed the cracked display assembly on this one, then i just can normally use the keyboard.
Will try again in terminal
edit: what command to use in terminal?
Dont forget, i flashed the recovery, but didnt install supersu zip yet..
The strange thing is, when im in the bootloader, i can use fastboot flash recovery command, and write the right recovery.
It's also succesfull (sending recovery OK, writing recovery OK)
But, the transformer hangs in the bootloader after finished (freeze)
When trying to reboot, it's automaticaly going again booting up twrp (enter password)
So it didnt write the recovery, by example if i write twrp 2.7, it still gives me 2.6.3.0 (installed first time)
extra information:
If i'm booted up, and then adb reboot bootloader, then try fastboot commands, they don't work. it keeps saying waiting for devices.., the fastboot commands like flash works for 1 second then the tablet freezes.
Click to expand...
Click to collapse
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?

Look in Device Manager on your PC and check that the Asus ADB interface drivers are there

Wow what a difference DATA2SD and ROM2SD make!

lvrijn said:
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Click to expand...
Click to collapse
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh

DarkDarwin said:
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Click to expand...
Click to collapse
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
lj50036 said:
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
Click to expand...
Click to collapse
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working

lvrijn said:
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
Click to expand...
Click to collapse
LOL, looking for help but you know what you got...
WOW

lj50036 said:
LOL, looking for help but you know what you got...
WOW
Click to expand...
Click to collapse
Sorry, I dont understand what you mean. What do you know I got?

lvrijn said:
Sorry, I dont understand what you mean. What do you know I got?
Click to expand...
Click to collapse
Sounds like you know more about this then any of us.
Not all Transformer tablets use the same drivers.
Window is very picky about what driver it will use for what device ...

Moto G Freezes on startup logo and recovery logo screen

Hi guys,
I have a rooted Device with CM and TWRP installed, but someting happenend using the device and my Moto G got stuck on startup logo and Recovery TWRP logo, with adb I have acess to adb shell but everything else like adb reboot bootloader etc doesn't seems to work, with adb shell I have realized that the TWRP wasn't running 'cause when I use the interface on shell I get this message
$twrp wipe cache
"TWRP does not appear to be running. Waiting for TWRP to start"
Is there any way to install a new recovery via adb shell or reinstall a new rom, factory reset or something like that to make my cellphone work again?
Thanks,

If you are okay to wipe internal storage, the following fastboot command will probably make TWRP load again:
fastboot erase userdata​
fastboot flash recovery newrecovery.img - is a way to reflash recovery, however the above command may still be required.

The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...

gconsentini said:
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
Click to expand...
Click to collapse
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data​

lost101 said:
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data​
Click to expand...
Click to collapse
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above

gconsentini said:
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
Click to expand...
Click to collapse
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.

lost101 said:
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
Click to expand...
Click to collapse
Sorry, I'm using Windows 10, if I use only wipe data, the command wipe is not reconigzed.

Can you enter fastboot mode by holding vol down and powering phone on?

lost101 said:
Can you enter fastboot mode by holding vol down and powering phone on?
Click to expand...
Click to collapse
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list

gconsentini said:
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
Click to expand...
Click to collapse
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.

lost101 said:
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
Click to expand...
Click to collapse
Yes, I thought about that too =x

SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks

gconsentini said:
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
Click to expand...
Click to collapse
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks

thomasswan5547 said:
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
Click to expand...
Click to collapse
Install the Minimal Fastboot & ADB package and the Motorola USB drivers, use the mfastboot package and install the stock ROM as per the instructions provided, but ignore the disassembly part, unless you have your phone does not respond to keypresses.
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915