Related
Hello all,
I'm having problems with my Kaiser. I rooted the device, and flashed Android.
Now, as with many others, when I power on the device, the green light is on and nothing on the screen. I cannot get to the bootloader.
I cannot connect with MTTY (with WinXP or Win7, but I hear the "dunk dunk" USB connected sound when I plug it in). The driver is for a mass USB storage device, which means I cannot use the MotoQ drivers. MTTY never gives USB as a connection option.
Now the confusing part. When I press the power button, I get the green light. When the device is off, and plug in the USB cable, the device starts to boot into Android after 3 mintues, but never gets past the splash screen. It cycles through the boot screen again and again.
I have tried pulling the battery (overnight), the hard and soft reset combos do nothing. I cannot get to the bootloader using the power and camera combo.
Without MTTY connecting, I cannot get Frankenkaiser to connect.
Any ideas?
Thank you!
idaho999 said:
Hello all,
I'm having problems with my Kaiser. I rooted the device, and flashed Android.
Now, as with many others, when I power on the device, the green light is on and nothing on the screen. I cannot get to the bootloader.
I cannot connect with MTTY (with WinXP or Win7, but I hear the "dunk dunk" USB connected sound when I plug it in). The driver is for a mass USB storage device, which means I cannot use the MotoQ drivers. MTTY never gives USB as a connection option.
Now the confusing part. When I press the power button, I get the green light. When the device is off, and plug in the USB cable, the device starts to boot into Android after 3 mintues, but never gets past the splash screen. It cycles through the boot screen again and again.
I have tried pulling the battery (overnight), the hard and soft reset combos do nothing. I cannot get to the bootloader using the power and camera combo.
Without MTTY connecting, I cannot get Frankenkaiser to connect.
Any ideas?
Thank you!
Click to expand...
Click to collapse
i've experienced this before after installing new winmo rom. but i got it worked after a hard reset at the green light part.
Thanks, tried that. Nothing.
Did you tried to force the MotoQ drivers instead of the detected driver (harddisk)?
USB Drivers
Yes, I tried the MotoQ drivers, but Win XP and 7 see the device as a large USB memory device, and not a phone. So I always get the "These drivers are not applicable to this device" or something like that.
Hey guys, so I just came across a Nexus S GT-i9020T but it has a problem! The problem is right after it's turned on, it immediately goes into "Downloading... Do not turn of target!!!" with an android sweeping up icon... Now I just bought this off a guy and he only told me that the last thing he did was install some Cybermod 9 skank mod??? he claims the phone was working fine until he went to reboot and got this Downloading.. screen from there on out.. Now I can't even get the phone recognized on my Windows 7 computer but I'm really new to this stuff and thought if i could get this fixed i'd have a cheap new/used Nexus S.. I've tried the Volume Up + Power hold, and other variants and cannot get the phone into bootloader. Also, when I plug in the USB cable there's no charging icons, and it seems the battery is getting low and dying so I'm going to buy an external battery charger to keep it topped up while I try to repair it. Please tell me what I can try to get this thing working! Thank you!
r3ap3r911 said:
Hey guys, so I just came across a Nexus S GT-i9020T but it has a problem! The problem is right after it's turned on, it immediately goes into "Downloading... Do not turn of target!!!" with an android sweeping up icon... Now I just bought this off a guy and he only told me that the last thing he did was install some Cybermod 9 skank mod??? he claims the phone was working fine until he went to reboot and got this Downloading.. screen from there on out.. Now I can't even get the phone recognized on my Windows 7 computer but I'm really new to this stuff and thought if i could get this fixed i'd have a cheap new/used Nexus S.. I've tried the Volume Up + Power hold, and other variants and cannot get the phone into bootloader. Also, when I plug in the USB cable there's no charging icons, and it seems the battery is getting low and dying so I'm going to buy an external battery charger to keep it topped up while I try to repair it. Please tell me what I can try to get this thing working! Thank you!
Click to expand...
Click to collapse
check if the volume down is stuck. power button + volume down get you into download mode.
Not quite sure how to tell if the volume down button is stuck... I can hear it clicking when i push it.. Hitting around the volume button area doesnt seem to do anything.. Any key combo I hold always brings me into "Downloading.."
Edit: I opened up the phone and the volume keys seem to be working fine
Do you have the Android SDK? I'd think if you got those, you'd be able to issue the ADB commands and reboot into the bootloader that way.
Yes i have the Android SDK installed properly, however i'm not sure if i have the correct USB Drivers since i just got this phone and havent ever hooked it up to my PC before.. I've worked on my Galaxy S and Galaxy Nexus before, but i've since updated USB drivers to 1.4.8..... I tried 'adb devices' in a terminal and can't get the PC to recognize the phone at all, but thats about all i know for commands. What else can I try??
ok so i found a list of commands, tried 'adb reboot-bootloader' but its saying error: device not found... Now my battery is almost completely dead and phone only comes on for 3-4 seconds so i think i need to go buy that external battery charger before i continue because the phone will NOT charge via usb cable attached to phone..
I haven't updated my SDK in ages and it still recognizes my device. In my case, sometimes my USB ports act funky and won't recognize my phone. I'd have to either restart the PC or switch ports and it would work. Let us know if you get the phone fully charged up
chronophase1 said:
I haven't updated my SDK in ages and it still recognizes my device. In my case, sometimes my USB ports act funky and won't recognize my phone. I'd have to either restart the PC or switch ports and it would work. Let us know if you get the phone fully charged up
Click to expand...
Click to collapse
So i picked up the charger and now have a charged battery! Still not sure how to get the PC to recognize the phone though... Was I right in installed the 1.4.8 Samsung mobile phone driver or is there another driver i need to use like pdanet???
OK!! Got the PC to recognize the phone being plugged in but it's still showing up as "Unknown Device" under device manager.. I'm guessing this means I don't have the right drivers, or?? Also I'm not getting anywhere under terminal "adb devices" or "adb reboot-bootloader".. saying error: device not found
Install the drivers through pdanet
djquick said:
Install the drivers through pdanet
Click to expand...
Click to collapse
The problem with PDAnet is that I can't actually turn the phone on to enable debugging so PDAnet doesn't fully install - unless i'm mistaken but it still shows as Unknown device in device manager
Anyone??????? Just to recap, on my Nexus S when i turn the phone on i'm stuck on the "Downloading... Do not turn off target" screen (can't use volume up + power) always goes to download screen.. The phone shows up as "Unknown Device" in device manager.. Odin doesnt pick it up, adb devices shows no devices... Ive tried a few different drivers such as pdanet, samsung 1.4.8, with no success.... Please someone must know a solution?
go go linux, bit of a pita but the drivers shouldn't give any problems
I have ubntu on a usb stick already but i don't really know how to use it all that well... will it have drivers already or do i need to download some linux usb samsung driver?
http://source.android.com/source/initializing.html
this has the info on the driver bit see configuring usb access, the rest would just be getting adb and fastboot for linux
I really can't figure out Ubuntu.. i even seemed to brick it somehow off a usb stick.. try to boot it and just get a black screen after the UBUNTU logo loading screen... man i'm hopeless lol
Aaaaaaaaaanybody?
dewaffelhaus8 said:
http://source.android.com/source/initializing.html
this has the info on the driver bit see configuring usb access, the rest would just be getting adb and fastboot for linux
Click to expand...
Click to collapse
OK after a few hours of messing around I got Ubuntu up and running, installed JDK, SDK, and still no devices found when i bring up a terminal and type 'adb devices' while the Nexus S is on and in downloading do not turn off target!! mode.... Tried Unbrickable resurrector with no success saying it can't find device either... I know I have usb drivers and adb installed correctly because i can plug in my Gnex and get the adb device # no problem... This is super frustrating!!
bump
Wish I knew of another way to help. I'm out of ideas.
Need assistance getting USB connection to PC working. (I believe this will be the first step to loading a working ROM since my HD2 is bricked right now.)
Details
1) The HD2 boots to Win Mo 6.5. From there I have been running Android 22 from the SD card. The phone locked a week ago and now when I pull the battery and put it back in, pressing the power button starts to the Pink T-Mobile screen ("stick together") and goes no further - I never see the additional text details in the lower left (radio version and other info, I believe).
2) I have used the Vol up/Vol down/Power botton to do a hard reset. This had no effect on my problem.
3) I can open the Red Green Blue White screen using Vol Down/power button. It shows "Serial" in the white area when USB is not connected. It shows USB in teh white area when the USB cable is connected to a computer.
The red area shows the following 4 lines:
"PB81120 HX-B3"
"SPL-2.08.HSPL 8G XE"
"0x05"
"CotullaHSPL 0x40"
The above leads me to believe that I am still in a position where I can recover from this problem. BUT I can't get either of my 2 computers to connect properly via USB.
I have 2 computers - Win 7 and Win XP.
On my Win 7 - I have installed Drivers so that it no longer warns me that there is a missing USB driver - the most nagging was a Qualcomm driver. I have installed installed Windows Mobile Device Center. When I connect the HD2 to the Win 7 box via USB it WMDC never recognizes my HD2 but I do get the beeps telling me the computer knows a USB device has been attached.
On my Win XP - I have installed ActiveSync. I also have eliminated all messages of missing drivers. ActiveSync also does not recognize the HD2 when plugged in - but again, the computer beeps saying it knows a USB device was connected.
In both cases I have tried the USB connection from both the T-Mo "stick together" screen and from the Red Green Blue White screen and the PC never recognizes the HD2.
-thanks
I know that this theme has been beaten mercilessly, but let's try it again. Maybe someone can help.
I'm looking to breath some life back into my old TF101 with an update to KatKiss.
My serial number starts 037. I'm running 4.0.3 ICS. I have USB debugging enabled. I have MTP enabled. On the computer side, I'm running Win 8.1 on a Haswell i7 16GB with USB 3.0.
I have the original USB cord, and a new 3.0 USB cord from a third-party manufacturer. I've tried both cables. The TF101 itself is well-aged and somewhat beat up, but not beyond use. The cords work for charging.
When I plug the USB cable into the PC, the computer makes a sound, but no device is shown. The TF101 doesn't show that it's connected to the computer. I've looked everywhere: Devices and Printers, Device Manager (there's no "Other Device Listed"), under safely remove devices, and even under Computer Management > Storage > Disk Management. The TF101 is nowhere to be found. The computer does not recognize it.
When I power off the tablet, and try going to APX (or whatever) mode with VOL UP and POWER, nothing happens there either. (The computer shows nothing whether connected through the USB cable while Android OS is running, or while I'm trying to go into APX mode.) I can, however, go into recovery mode (or whatever it would be called) by holding VOL DOWN and POWER. I tried a factory reboot, but that didn't work either. The computer still doesn't see it.
Basically, I've concluded that there's no hope. Given this state of affairs, I cannot root my TF101, and, because I cannot root the tablet, I cannot install custom ROMs on it.
Does that about sum it up? Anybody else have any other great ideas?
I'd very much appreciate any insight anyone could give me.
Install the drivers on this thread and download Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012
Power off the TF while it is connected to the PC
Hold Power & Vol Up to enter APX mode
Device should be recognised by windows and hear the USB connect sound
Nothing will appear on TF screen
Run the Easyflasher and install TWRP
When done, boot to recovery to check you have TWRP recovery installed
If yes, copy KatKiss ROM to Micro SDCard in TF and flash from TWRP along with Gapps
*Detection* said:
Install the drivers on this thread and download Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012
Power off the TF while it is connected to the PC
Hold Power & Vol Up to enter APX mode
Device should be recognised by windows and hear the USB connect sound
Click to expand...
Click to collapse
Detection, I appreciate your response! The thing is, when I try to enter APX mode, nothing is recognized by the computer. I don't hear any sound. I don't see any new devices appear anywhere.
Should I conclude that I have the "TF101-is-not-recognized-by-PC Problem"? And, if I do, is there anything else I can do to about rooting and installing a custom ROM?
RJM
In device manager, try enabling "View hidden devices" and see if you can see the TF101 ghost entry, if yes, remove it and then plug the TF back in and see if it's recognised then
If you don't see anything that way, try viewing hidden devices with it plugged in too
There is no reason it shouldn't be detected in APX mode unless you have been unlucky and have 2 dodgy cables, or there is actually hardware damage to the TF
Try installing windows to a virtual machine too, see whether you can get it recognised that way
If you have access to another machine, see if you can get it seen on there to rule out hardware as the issue
Thanks for the reply. I appreciate your interaction very much.
I've tried it on both machines. There is no sign of TF101 anywhere, on either machine, as a ghost or anything else. I've looked under the Android section, as well as under Portable devices and every other list. There's definitely no sign of a TF101. No sign of anything that my TF101 might be posing under.
The only time I get any kind of response by the computer is when I plug the TF101 into the computer when the TF101 has Camera (PTP) mode activated. When I do that, I hear a little jingle. If I have the Device Manager open, it flashes. But, even then, I don't see any sign of it anywhere.
I'm totally stumped. Would there be some clear indication on the hardware that would cause the problem?
By the way, both USB cables charge just fine when I'm using the USB power box. But when using the computer, there is no charge or any other sign of the thing.
If you have any other advice, I'd love to try it!
The power and data connections on the USB lead are separate, so if you have a faulty lead, it could still charge, but not be seen by the PC
Something like this:
1: Power
2. Data
3. Data
4. Power
You won't see the TF charge from PC, it is only a trickle charge via PC, and the TF has to be powered off iirc, or at least the screen has to be off, so you only see the result, not the actual charge
Not sure what having the camera on is doing, I would still lean towards faulty USB cables being the issue even though you have 2 of them
Im guessing that the 2nd cable is a 3rd party cable, not a genuine ASUS TF101 cable ?
My phone only shows the the elephone 2 e sign when I turn it on. I have tried pressing the on and volume key when I turn it on but nothing happened. I have followed some instructions on the elephone manufacturer site about installing drivers to my computer and then trying to reinstall the firmware. Unfortunately my computers (I have tried on three different ones) does not identify that a device is connected to the computer. Therefore I can't proceed to install the driver as according to my computer it is not installed. I have tried 2 different leads as well. I would be grateful for some help as I have no idea where to go from here.
Facing a similar issue, and since there's still no reply to this thread, I would like to add up a few findings I have on this matter to maybe help others and get helped.
My P3000S is also reaching the Elephone logo and displays it for a minute and then restarts, repeating the process (aka boot-loop).
The same happens whether it is connected or not connected to the charger/computer through a USB cable. (I've tried new cables but that's not the case).
When disconnected I can stop the boot-loop only by holding down the on/off button for a few seconds (or removing the battery of course).
When connected to the the charger or computer through the USB cable I have no way to stop the boot-loop (holding down on/off just restarts it).
Now with the battery removed..:
If I connect it to the charger/computer, though the charging red light turns on normally, I can't turn on the phone using the on/off button.
However, when connected through USB to a windows computer, I can see in the device manager that, right when I connect the phone it shows up as "Mediatek Preloader USB VCOM Port" under COM ports group, for 1 second and then disappears as if it was disconnected. There's no repetition here I have to manually hold down the on/off button or disconnect and reconnect the phone from the cable to cause this to happen again.
So, I am unable to flash anything nor turn the phone on because I practically only have 1 second of its presence in my devices list.
Also, I have tried all possible combinations with the volume up/down keys and the on/off button in order to enter recovery mode, with no success..
In case anyone has faced something similar or has any ideas on a possible fix on this phone please feel free to reply.
At last a reply to my initial message. Unfortunately it was someone with the same problem as me. I took out a paypal case against the person I bought the phone from and eventually they repaired it. Unfortunately they never told me how. To make matters worse it broke again within 2 months. The phone is now sat in a draw doing nothing. I have given up on it and will never buy another Elephone phone again.