Database Users

Continuous force close and also corrupted zip

Hello Everyone I felt my previous explanation of the problem I am facing may not have been a good one so I am going to try explaining my problem again. I am currently experiencing several problems. I have a samsung Fascinate. When the phone was working fine I rooted it and all was still fine. I then installed clockworkmod(rom manager). I tried installing several roms by downloading them to to rom manager then selecting the one I want then rebooting the phone. But everytime I tried installing a rom by selecting apply update.zip from sdcard E:signature to verifly whole-file signature, E:signature verification failed, installation aborted. After reading through some of the links in xda developers forums I realized I need Odin. Once I installed Odin it never recognized my fascinate in the ID com column with in Odin. I made sure the phone was mounted by selecting mount from top drop down menu from fascinate. At the same time I notice that in Windows XP it would say USB not recognized although Fascinate would show up as a mass storage when checking under explorer and see a F: drive for the phone. Iam able to see the files in the phone and transfer if necessary. I then tried getting a new update.zip and rebooting to menu where u select apply sdcard update.zip same error of invalid signature. then tried cwmrecovery and rebooting ..no luck either. Then I found a link containing a file named stock.zip...but no luck either. So I decided to wipe and reset to start all over and when I did that and the phone started and I unlocked the screen I began getting endless forceclose. This is where I am now. Does anyone have any suggestions.

You need to download the Samsung drivers first. Then proceed to use Odin.
Sent from my SCH-I500 using XDA App

Also wrong section.
Sent from my SCH-I500 using XDA App

bigal2908 said:
when I pull the battery then hold the volume down and then insert the usb plug the yellow block on Odin does not appear and I get a message on my windows xp saying device not recognized.
Click to expand...
Click to collapse
Download mode is easy:
Step 1. Power up your phone (while phone is off, press power and release), then
Step 2. Immediately hold volume down until you see the yellow Android warning sign.

I downloaded the usb drivers for mobile but ti still didn't wok. What else do you think it might. When I connect the phone to computer (windows XP) on the lower right it says USB device not recognized.

Are you pointing the device driver installation to the path where the drivers are? And did you download the drivers for your correct cpu 32 or 64 bit?
Sent from my SCH-I500 using XDA App

I forgot to mentioned that I have installed the samsung usb drivers two times. still no luck. I even read that if you unplugged the usb and then shoutdown windows xp and physically disconnect power and wait about a minute or two sometimes this would help xp recognize usb port. I also tried disabling and enabling the port via manage in my computer on xp while the fascinate was connected and also tried it disabling and enabling while phone was not connected no luck eitherway. Any other suggestions. Thanks inadvance for everyones suggestions.

the drivers I downloaded are 32 bit. how do I point the drivers as you have mentioned. I also tried downloading android sdk tools and tried to figure out how to push the files top the phone but when I typed adb device under listing devices it does not show the phone or anything for that matter. I am confused now as to what may be the original problem and how to tackle the problem should I work on USB problem first then force close then update.zip any suggesstions.

You need to go to device manager, find the phone under the section that talks about not recognized usb's, right click on it then go to properties, then you need to manually select the drivers you downloaded..

[Q] Problem...Recovery with no ROM to flash or USB recognition

Hi XDA. I have a problem and could use your help.
In order to make flashing ROM’s easier for myself I thought it would be a good idea to place them in the first folder listed on the internal sd card. In order to do this I placed a “.” befor the name of the folder. After wiping everything I learned CWM 5.8.1.8 (touch) does not see folders with dots(“.”) at the beginning. So I now am in recovery with no ROM to flash
I then proceeded to dig an even deeper hole for myself. In my attempts to install drivers for my device I have done something; now my computer fails to recognize that the device is plugged into the USB at all. Prior to my messing with it I would hear the USB input chime and Device Manager would show an “unknown device”. Now when I plug in my device nothing happens. I have tried two computers and both Win7 and Ubuntu.
I read that Linux might be able to see my device so I installed Ubuntu then the Android SDK as per this thread. It did not work for me. I still cannot see my tf101 but I can see my Nexus s with the “adb devices” command.
I bought my tf101 refurbished and can’t find the “B” version written on the device. I think I initially rooted with razorclaw...not %100 sure. I am not sure adb debugging was checked when I wiped...not sure it makes a difference at this point.
I am now looking at these NvFlash instructions but I can’t get past the 2nd step (I am a noob...obviously)
- run “./blobunpack recovery-clockwork-5.8.2.1-tf101.img” (Replace “recovery-clockwork-5.8.2.1-tf101.img” with the name of your downloaded file”)
Will this NvFlash tutorial work if the computer can’t see the device?
Any ideas?
Thanks for your time!

Try those steps from this website Reverting to Stock ROM (unroot and remove CWM recovery)
this is easier for you when u try to nvFlash your tf101. remember update driver, run as administrator on program

Thanks for the info!
I am away until tomorrow evening. I will try it then.

Hi,
I am still having problems.
Can I install drivers if the device is not listed in device manager? How?
Thanks again!

it will be reinstall or request when you unplug and plugin back your connect from tablet to PC
if your driver had been load or connected just go to Devices and Printers to check your connection, after that update your driver

Hi. Thanks for trying to help.
My problem is my computer is not seeing the device at all. No USB input chime. Nothing showing up in device manager. No nothing!
Could be the chord I guess but I don't think so. I was getting "unknown device" in device manager initially after I wiped the ROM. After attempts to install drivers I stopped getting any sign of the tf101 in device manager.

[Q] Verizon VS980 - The Verizon Software Upgrade Assistant software won't start up

I'm not sure what to do here. I'm still running 4.4.2, and wanted to upgrade to Lollipop. The upgrade failed because I am rooted with the 0x1117008 error. I found somewhere that some guy said installing the update through the Verizon Software Upgrade Assistant worked. That tool is accessible when you first plug in your phone to a PC, there is an autoplay option to run that software.
When I try to run that tool, the little spinner on my cursor spins for a few seconds, then stops, and nothing happens. Then my phone changes from "connected as installer" to "connected as <whatever I set>" The software doesn't open. I've tested all available USB modes, same thing on each one. I have the latest drivers, I've tested shutting off USB debugging.. I'm out of ideas.
I tried it on my work laptop as well, same exact thing. The software won't start on either computer (both win 7). Any ideas? Could someone possibly post the installer files from their vs980? Maybe the software I have is just bugged or something. When you first plug in your phone, a new "CD Drive" appears with the LG icon, the files are all in there. Or if anyone has any other suggestions, I'm all ears.
thanks
EDIT: Solved. I'm dumb. I had "csmg.lgmobile.com" in my hosts file for some reason.
EDIT 2: In case anyone googling ends up here, using that tool DOES indeed allow you to install Lollipop if you were getting the 0x1117008 error trying to install the normal way.

Windows not detecting device in stock Recovery Mode

Hi. I am trying to sideload the Android 6.0.1 update but am having some problems detecting the device in recovery mode.
I have previously unlocked my bootloader on the day i got my phone.
I have enabled USB Debugging and have installed android USB Driver 11.0.
On my Windows 8.1 Device Manager...
When I am in normal android = Android Composite ADB Interface is present.
When I reboot to Bootloader = Android Bootloader Interface was installed.
However, when I am in the stock recovery, Android Composite ADB Interface is not found. Neither is there any unknown devices in my Device Manager (yellow question mark) that might look like the ADB Interface.
As a result, when I am in Recovery Mode, "ADB Devices" command does not work.
Help? Thanks!

Same here!
Glad i'm not the only one! I have exact the same issue! Device is recognized until bootloader... but when i switch to recovery i can hear the "usb connection failure sound* from windows...
I'm wondering if anybody else has this issue and know how to fix it!

I am having this same issue. I've installed HiSuite with the latest USB drivers and have the latest Android SDK Platform Tools updates. I have tried unplugging and plugging-in the device when it is in recovery to try and trigger something but nada. I've tried different USB ports too.
My behavior is exactly the same. The phone shows up in ADB devices under normal full boot and also in the bootloader. As soon as it goes to stock recovery it won't show up as a device in Windows anymore. Not as an even an unrecognized device.

Had the same issue on Windows 10 myself and while I don't recall the exact steps I took to solve it (perhaps someone else has a procedure for it) I was able to solve it. Essentially what solved it for me was reinstalling the driver while the phone was in recovery.
Roughly what I did:
Have "Show hidden devices" checked in Device Manager.
While in recovery mode, right-click "Android Composite ADB Interface" and select "Update driver." Tell it to "Browse my computer..." then "Let me pick..." select "Android device" and finally select "Android Composite ADB Interface." Tell it next to reinstall the driver.
That should allow you access again via ADB. Like I said, this is from memory so it may have been the "Android ADB Interface" that was the driver that needed reinstallation. If "Android ADB Interface" isn't showing up, you might try installing it from the "Action" menu, "Add legacy hardware."
Hope this helps.

Minlock said:
Had the same issue on Windows 10 myself and while I don't recall the exact steps I took to solve it (perhaps someone else has a procedure for it) I was able to solve it. Essentially what solved it for me was reinstalling the driver while the phone was in recovery.
Roughly what I did:
Have "Show hidden devices" checked in Device Manager.
While in recovery mode, right-click "Android Composite ADB Interface" and select "Update driver." Tell it to "Browse my computer..." then "Let me pick..." select "Android device" and finally select "Android Composite ADB Interface." Tell it next to reinstall the driver.
That should allow you access again via ADB. Like I said, this is from memory so it may have been the "Android ADB Interface" that was the driver that needed reinstallation. If "Android ADB Interface" isn't showing up, you might try installing it from the "Action" menu, "Add legacy hardware."
Hope this helps.
Click to expand...
Click to collapse
Thanks! I realised im actually on Windows 10 too...
However, your method doesnt seem to be working for me.
In Recovery mode, "Android ADB Interface" doesnt show up. Hence, I added a legacy hardware as you suggested, but it shows up that "This device cannot start. (Code 10)".
I also tried to update the hidden "Android Composite ADB Interface". While driver installation was okay, the phone is still not detected.
I tried replugging in the phone into a different USB port but it is still the same.
Strange... seems like only some people are encountering such issues? Wonder what is the difference. Thanks.

okay somehow fixed it...
Basically, under recovery select "Apply Update from ADB".
Then unplug the cable and put it back in again.
Somehow, the drivers are installed properly after doing that....

l0nEr said:
okay somehow fixed it...
Basically, under recovery select "Apply Update from ADB".
Then unplug the cable and put it back in again.
Somehow, the drivers are installed properly after doing that....
Click to expand...
Click to collapse
After doing all the previous steps, doing this step really did the trick.
Thanks!!!

makeitra1n said:
Glad i'm not the only one! I have exact the same issue! Device is recognized until bootloader... but when i switch to recovery i can hear the "usb connection failure sound* from windows...
I'm wondering if anybody else has this issue and know how to fix it!
Click to expand...
Click to collapse
i'm here too

I had same problem and after searching days it solved by installing universal ADB Drivers from the link below:
Universal ADB Drivers

MSM8994DownloadTool.exe Won't Work For My OPT

MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).

I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.

Phil01234 said:
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
Click to expand...
Click to collapse
I've bricked my op2 a while ago. I'm a real noob so I don't know if it will work but have you installed the adb mac drivers or try "fastboot continue" while in fastboot. Just don't give up and keep try. You have absolutely nothing to lose.

chintu1234 said:
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Click to expand...
Click to collapse
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.

Phil01234 said:
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Click to expand...
Click to collapse
Try connecting your OPT to some other guys pc and see, it may be because of your pc's end that its not getting connected.
And if the same thing happens with a different pc then yeah your usb port or something is fried. Try going to service center if the same thing happens again.