Hi there,
I have read through a load of threads on how to unbrick the KF2.
Although it looks like the tools work for most, when I connect my KF2 with the fast boot cable, my Windows 8 PC doesn't detect the KF2 properly.
Before I had the red screen, it did find it and it worked OK. I have all the drivers and the SDK installed. I had rooted the KF2 and had that working fine, I tried to install Android KitKat onto it and got this red screen.
When I connect it to Windows 8 PC now it says:
Windows has stopped this device because it has reported problems. (Code 43)
The USB set address request failed.
I turned it off/on a few times, tried a few different USB ports and always the same.
I then tried it on a Windows 7 laptop and that comes up with installing device:
"otter2-Prod-04" rather than Kindle.
It ends up in device manager in other devices with a yellow exclamation mark.
On neither PC the KF2 will detect with adb -devices command.
Not sure what to do now, and how to get it to detect so that I can 'unbrick' it....any ideas anyone?
Related
Hello, I believe I screwed up something with the mounting/unmounting before I flashed a ROM, and my phone is not working as a result. Originally, it would sit at the Samsung Sidekick 4g Tmobile screen forever, and I could use the button combination to get it into download mode... now that doesn't work, and it only goes to the black screen with the phone and the computer.
I have downloaded driver after driver after driver trying to get this to work, I have downloaded ODIN, and I understand how to use it, but there is no way ODIN is going to see my phone because Windows will not properly install it. I only have a PPC mac and Win 7 computers, one win 7 computer says device is malfunctioning and the other win 7 computer loads it as a "Gadget Serial" but says that it did not install properly. I have tried all the samsung drivers, all the samsung programs to no avail. I've tried more than one USB cable too...
Is there any hope in getting this phone back to life? Do I need to use a windows XP installation? I have VMware so I could try XP or linux but frankly I'm afraid to do anything more for fear of further complicating this situation.
Final Edit: SOLVED. I uninstalled everything save for the samsung drivers, installed the android SDK and plugged it in a different usb port...although im not sure if windows got it right away, ODIN detected it and I was able to restore.
Flashed kf with kfu 096 when kf rebooted it hung on waiting for device. Kf stuck on logo screen. Windows says unknown device in USB hub. No drivers in kfu packet that work. Androidsdk drivers does not work. Unable to use adb because I cannot connect to device. Tried reinstall drivers but nothing I do will get the kf recognized so I can use any utility. I'm running winXP with a kf firmware 6.3.1. Any help would be awesome.ty I just need to connect my kf to finish this what driver works
Fixed
Well I fixed it. Ran it all over again on a windows 7 pc and it worked and un bricked it using KFU 09.6 HOORAY
Hi I'm trying to upgrade my Cherry Mobile Flare/Karbonn A9+ from ICS to Jellybean and was following the tutorial I found here at http://forum.xda-developers.com/showthread.php?t=2330823&highlight=karbonn+a9 . I have followed the tutorial exactly and when I get to step 5 Download the AP firmware I load the Stock JB Rom folder into Qualfast then click OK boot my phone into green mode and connect it with microusb it just sits there and does nothing and says waiting for devices. I noticed when I plug it in at this stage the phone shows up in my device manager under other devices as "Android" and does not have any drivers installed. I installed the drivers included in the Karbonn driver pack before I started the whole process already, I don't know why it just sits there when I plug it in the green screen mode in Qualfast. I'm a new user and can't post in the tutorial thread yet, any help would be appreciated. Thanks.
Using Win 7 64bit btw.
After looking at a few more tutorials and youtube videos it seems the problem is my abd drivers. When I plug the phone in fastboot(green screen mode) in device manager it is now showing up under adb interace "Android" but it have the yellow exclamation and in properties it says the device is not configured correctly driver is not intended for this platform. Everytime I try to install the abd drivers for win64 is says the drivers are already up to date. I tried uninstalling the device and reinstalling it always does the same thing. Any help?
Well I figured it out, I couldn't get the ABD drivers to manually install no matter what I tried so I installed the drivers via pdanet.exe program. Anybody having trouble installing ABD drivers on x64 just use pdanet to install them.
is it woriking?
Hi Guys,
I've had a few problems with my N5 recently...
If I plug my N5 into my PC via the stock USB cable and boot into the Bootloader (PWR+VOLDN) then it will allow me to flash the original N5 firmware, located here: https://developers.google.com/android/nexus/images, this would indicate to me that there is no issue with the actual devices ability to transfer files via USB connection... Right?
No!
For some strange reason my phone will allow me to push a full factory image to it and will also process any Fastboot commands that are sent to it but as soon as you boot into something like TWRP and try to control the phone's ADB functionality it will not find the device at all! The new MTP option in TWRP 2.8 will allow my computer to see my phone's MTP connection for about 1 second and then will immediately disconnect, the same happens when trying to connect to MTP from within Android too.
USB debugging doesn't show that it is connected when my phone is plugged into my PC and Windows makes the 'device connected' sound and then straight after makes the 'device disconnected' sound...
Any ideas? I am certain that this is an issue with my handset's hardware or software rather than any of the computers or cables... I have tried 3 different cables (including the stock cable) and also three different computers (Windows 8.1 @ Work, Mac OS X @ Work and my own personal PC running Windows 8.1 & Ubuntu @ Home)... All OSs and all computers run into exactly the same issue, device connects briefly and then disconnects.
I have troubleshooted issues relating to the driver. This is not the issue... Device Manager cannot even see the hardware after the disconnect.
Thanks for any help in advance,
Lewis
Also:
-Android does not detect that the USB is charging the device unless the device is booted with the cable attached (if it's not attached before the 'Google' screen then it can't see the USB input at all, within android or TWRP, of course...).
Having the exact same problem. Did you find a solution?
EvilBetty said:
Having the exact same problem. Did you find a solution?
Click to expand...
Click to collapse
It's most likely a driver issue.
Elluel said:
It's most likely a driver issue.
Click to expand...
Click to collapse
Not a driver issue.
3 different Nexus 5s, 5 different workstations. Other two Nexi are fine on all 5 PC's.
1 PC used for ADB forensics, 2 used for ADB development work, one known working for ROM'ing / rooting.
Phone has been factory reset, factory ROM'd from Fastboot. Connects fine on Fastboot. Will not connect on ADB / MTP.
On a fresh PC / phone reboot, the PC will detect the phone for just a second and then it will not reconnect until process is completed.
-EB
What's your adb version?
Went on for about 2 weeks, then suddenly went away on its own. I have no idea what the problem was or the solution. Sorry.
i have a nexus 5 which has stock ROM and blu spark kernel . i locked the bootloader while on the same kernel and again unlocked it . . the phone is bootlooping into twrp and the google logo . in twrp it says unable to mount data . i can access twrp . . i am unable to flash anything . it says unable to mount data/ . please the attachment
Afternoon all,
Have been out of the rom'ing scene for a while...
I have a number of devices (Galaxy Tab 2 10.1 and Nexus 7 2012, to be exact), that I want to flash a new ROM onto (the Tab's stuck in a boot loop, the N7's due for Dirty Unicorns Nougat Rom).
All pretty straight forward - I've done it in the past - BUT...
Can I get Windows 10 to even *see* new hardware's been connected, let alone recognize it?
Can I fook
To confirm, I plug the USB between the PC and the device, and all that shows this is connected is that the device realises it's being charged, no "ding ding" from Windows, no USB confirmation from the device...
Both devices have USB Debugging enabled.
Have tried different USB cables
Have tried different USB ports
Have tried - many! - different USB drivers, including that from both Asus and Google's own dev kit.
Have ADB installed, "adb devices" shows no devices (blank).
The thing that's really pi**ing me off is that this is such a basic thing to be stuck by, I really cant figure out what I'm missing!
Any help appreciated gents...
cy80rg said:
Afternoon all,
Have been out of the rom'ing scene for a while...
I have a number of devices (Galaxy Tab 2 10.1 and Nexus 7 2012, to be exact), that I want to flash a new ROM onto (the Tab's stuck in a boot loop, the N7's due for Dirty Unicorns Nougat Rom).
All pretty straight forward - I've done it in the past - BUT...
Can I get Windows 10 to even *see* new hardware's been connected, let alone recognize it?
Can I fook
To confirm, I plug the USB between the PC and the device, and all that shows this is connected is that the device realises it's being charged, no "ding ding" from Windows, no USB confirmation from the device...
Both devices have USB Debugging enabled.
Have tried different USB cables
Have tried different USB ports
Have tried - many! - different USB drivers, including that from both Asus and Google's own dev kit.
Have ADB installed, "adb devices" shows no devices (blank).
The thing that's really pi**ing me off is that this is such a basic thing to be stuck by, I really cant figure out what I'm missing!
Any help appreciated gents...
Click to expand...
Click to collapse
Windows 10 is very buggy. Download lobit Drive Booster to see if you are missing any driver for your pc. Your pc is probably missing some drivers for the motherborad or outdated. If this does not work, clean install windows 10. Let windows 10 install all the drivers for you while it is installing. Best method. Good internet connection required.
its damn easy,the problem lies in Windows,just boot into repairmodus/system recovery its the blue menu for troubleshooting,there u choose Startup Setting and there u choose number 7,thats for disabling the digital driver signature checking,after the reboot all is fine,boot note u must do it everytime new after reboot.
please next ask and post in right section,thanx.
Nvidia USB driver (ADB and Fastboot) is the only one that works for me
https://developer.nvidia.com/shield-open-source