Database Develop

[Q] Upgrade program crashed, stuck in upgrade boot screen. Now what? SOLVED!

Like the title says:
I just tried to upgrade my Optimus 2X via PC software. The package downloaded fine but in the middle of the upgrade process the PC software crashed(!) and now I have a phone which is stuck in the upgrade boot screen saying:
"S/W Upgrade
Please wait while upgrading..."
So, what now? Any way to get this thing working again?

First, remove your battery and put it in your phone. Boot the phone up and see where it goes. If it goes into S/W mode again, that sucks. If it goes to the LG boot screen, put the battery out again and put it in. Press Power + Volume Down buttom to go into the CWM menu. From there you can restore your backup (if you made one) or mount the SD card and put the (rom).zip file in your SD card. Then just flash the zip from the CWM.

The update process by LG is pathetic. Many a times, I had the same problem as you. It would just get stuck. It is because of faulty drivers on their part, unable to maintain a connection with the phone.
You can try to NVflash clockwork mod recovery (CWM) and then recover your data.

i have the same problem.
i've tried everything without luck.
mine stopes att 4 procent and pc is trying to install some new device
lge mobile composite usb device.
there is no way to work around this issue.
i have tried absolutly everything.
wipe, clean, drivers this that. hard reset, variations in installing, i don't know what else i can do,
this is the message that cousing all of this.
this is located just in upgrade mode
the device is called
LGE mobile composite usb device
Universal Serial Bus controllers
LG Electronics Inc.
Location : Port_#0001.Hub_#0004
Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)

Thanks for the infos. I managed to install a stock rom and baseband with SmartFlash yesterday. Just a few minutes ago I used LG's update tool to update the phone to Gingerbread.
So, problem solved. If anyone has the same problem, follow these instructions to update the baseband:
http://android.modaco.com/topic/335494-12-aug-smartflash-stock-baseband-release-103521-20110725/
You can get stock roms from here:
http://forum.xda-developers.com/showthread.php?t=1035041

I think I bricked my Droid 3, Complete noob at phones but pretty tech savvy

Hey so my name is Richard, hello.
I'm not sure if I posted this in the wrong section but don't bug me about lol.. I tried my best.
My friend recently gave me a Verizon Droid 3, and I wanted to use it with T-Mobile.
Now, I searched ALL OVER the web. (and yes, when I messed it up I searched all over this forum.. Really. Nothing worked)
I found out I had to..
1) Unlock the phone, get the unlock code (Duh)
2) Root the phone (Noob at this.. never done this before)
3) Flash the phone (Again.. I'm a noob at this)
The unlock code part was easy, I got that.
I soon discovered that there is another lock on this phone ? It's a lock that only let's you use it with carriers overseas, is that correct, yes ?
I think my mistake was trying to flash it without rooting it first.. I don't know really.
I USED THIS ON MY PHONE: Flash Verizon DROID 3 OTA 5.6.890 to phone_psouza4
When it was doing this there was a error apparently. I've tried using this program multiple times.. etc most of the times it stopped on recovery but there was one time when it went to radio, and there that's when it failed.
Now when I turn on my phone I get this:
AP Fastboot Flash Mode (S)
0A.53
BATTERY OK
OK to program
Transfer Mode:
USB Connected
^I think it's saying USB connected, because it's currently connected to my computer right now.
I have no idea what to do.. I just want to be able to use this phone with T-mobile.. that's my main concern now.. the phone is unlocked.. I just need to unbrick it first I think and then root it and flash it properly.
Oh, and I forgot to tell you guys what happened when I tried to root it... : It failed on the 3rd step. I used the one click program. Also, it's pretty frustrating to do this, because my computer barely recognizes my phone (On occasions)
The only way to get back on my phone right now is turning it on by pressing the M and the power button and then clicking the normal boot or whatever, I forgot the exact name.
PLEASE HELP :'(

1. Power off phone
2.hold down vol + and vol - and power
3.scroll down to ap fastboot
4.press vol up
5.extract Flash Verizon DROID 3 OTA 5.6.890 to phone_psouza4 to desktop of home computer
6.download motorola drivers to computer and install
7.download rsdlite 5.7 to computer and install
8.connect droid 3 to computer with usb cable
9.run rsdlite
10.choose xml file in psouza4 folder
11.click start
When its done pull battery then replace..pwr up phone holding x at same time..choose wipe/factory reset..reboot phone..your back to stock .890....unbricked
But that's only if it didn't have .906 installed originally..if it did you will need a diffrent sbf

Nevermind, I got this to work I'm so happy.

what did you ended up doing ?

[Q]RSD LITE problems, not recognizing phone

So I wanted to FXZ back to .902 with rsd lite. I downloaded the latest Motorola USB drivers, and rsd lite 5.7, but for some reason when I start the program it won't recognize my phone is plugged in. I start it in Fastboot AP and even waited 10 min, and nothing. The only thing I have done with the phone was update to .905, root, installed safestrap, and eclipse 3.0. I'm running in unsafe mode in safestrap right now. Any suggestions? This is driving me insane, I just want to get back to stock .902.

Are you using a notification cable? Not all usb cables are created equal, maybe try with a different one.
Sent from my DROID BIONIC using Tapatalk

linuxgator said:
Are you using a notification cable? Not all usb cables are created equal, maybe try with a different one.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Definitely this. I've seen way too many threads that show that RSD Lite and/or Moto devices are very picky about their USB cables. Try another one to see if it's detected.
Failing that, go peek in your device manager (Start > Run > devmgmt.msc) and see if the phone even shows up in there. You could be having larger issues with USB device detection.

linuxgator said:
Are you using a notification cable? Not all usb cables are created equal, maybe try with a different one.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Omg if you were here I would kiss you. I had not even thought that the usb cable that came with the Bionic would be the issue, but sure enough I used my cable that came with my Incredible 2 and IT WORKED. thanks so much

Mine is recognized when I use the command 'lsusb', but doesn't show up on RSDLite. I will try another cord but wouldn't it make more sense that if it's being recognized it is a software issue?

psychonot said:
Mine is recognized when I use the command 'lsusb', but doesn't show up on RSDLite. I will try another cord but wouldn't it make more sense that if it's being recognized it is a software issue?
Click to expand...
Click to collapse
Which version of RSDLite are you using? There's a newer version out, 6.14 I think it is, that doesn't work all that well. Right now 5.7 is still the recommended version. The cable thing still sometimes is the issue, even if it is recognized in other modes sometimes it just doesn't work right. You can also try flashing with moto-fastboot as a command line program. There are both windows and linux versions available.

Working Atrix HD
Worked after installing ADB Driver thanks!

Still no joy
so I have a high-speed USB 2.0 cable, ADB driver displays in the Device Manager, and Rsd Lite 6.15 still does not display my Moto X.
Any other suggestions?

Droid razr m - can't flash/fix with rsd lite 5.7
I can't get my Droid Razr M off the boot screen, endless boot loop happening with the startup screen.
I downloaded the RSD Lite 5.6 (then 5.7) and tried both. Neither is recognizing my device.
I downloaded the AdbDriverInstaller.exe for Android. Did not even recognize my device - the device is plugged in, I'm looking at the AP Fastboot Flash Mode (S) on my phone. Says Device is Locked (whatever that means). Status Code: 0. Transfer Mode: USB Connected. So it recognizes that there is a USB plugged into it.
I ran ALL of these firmware versions from this website through the RSD Lite - sbf . droid - developers . org - NONE are working.
I keep getting Status: Failed Flashing Process: 1/19 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I saw some forums that said within the actual firmware XML file, to delete these lines of code, so I did (note: I tried running them before and after the file edit):
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="oem" var="fb_mode_clear" />
SOMEONE HELP!

Droid Razr Maxx
amandafrat said:
I can't get my Droid Razr M off the boot screen, endless boot loop happening with the startup screen.
I downloaded the RSD Lite 5.6 (then 5.7) and tried both. Neither is recognizing my device.
I downloaded the AdbDriverInstaller.exe for Android. Did not even recognize my device - the device is plugged in, I'm looking at the AP Fastboot Flash Mode (S) on my phone. Says Device is Locked (whatever that means). Status Code: 0. Transfer Mode: USB Connected. So it recognizes that there is a USB plugged into it.
I ran ALL of these firmware versions from this website through the RSD Lite - sbf . droid - developers . org - NONE are working.
I keep getting Status: Failed Flashing Process: 1/19 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I saw some forums that said within the actual firmware XML file, to delete these lines of code, so I did (note: I tried running them before and after the file edit):
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="oem" var="fb_mode_clear" />
SOMEONE HELP!
Click to expand...
Click to collapse
I am having the same problem with my Droid RAZR Maxx (XT912). I rooted it, then flashed CM 10.1.2. with Safestrap. Since then, I've had all
sorts of trouble. I've been trying to get it back to the factory ROM, but me being a total noob at the time, somehow made the mistake of backing
up my factory ROM in a CWM format instead of TWRP, meaning that I never could access it from Safestrap, and Safestrap would not uninstall
no matter what I tried. This was a long time ago, I have been researching all over the interwebs to fix my problem since. I tweaked my phone to
the point that it worked well for everything I needed, even though I was still stuck with CM.
It worked just fine... Until now. My phone went dead one day, and when I tried to charge it and reboot, it woke up stuck in bootloop. I have no idea why it decided to get stuck in bootloop, but I need to get it back ASAP. I have done hours and hours of research, set up adb and RSD Lite v5.6, got all the driver software I needed, and then found the firmware to take it back to Android v 4.0.4. My problem is that neither adb, nor RSD Lite will recognize my device. My computer recognizes the device as a Mot single adb interface, but that is the only recognition I get from my computer. My phone is saying the same thing as the quoted post above
Phone is Locked, Status Code: 0, Transfer Mode: USB Connected.
I have tried a few different USBcables, but I don't have the original factory cable from Motorola because my dog decided she wanted it more. I have an LG factory cable, but it still won't work with that.
tl;dr: My phone (Motorola droid RAZR Maxx XT912) is stuck in bootloop, adb and RSD Lite won't recognize it, but my computer will.
I'm in need of a wee bit of assistance, does anyone have any advice to offer?

Anonymous Assassin said:
I am having the same problem with my Droid RAZR Maxx (XT912). I rooted it, then flashed CM 10.1.2. with Safestrap. Since then, I've had all
sorts of trouble. I've been trying to get it back to the factory ROM, but me being a total noob at the time, somehow made the mistake of backing
up my factory ROM in a CWM format instead of TWRP, meaning that I never could access it from Safestrap, and Safestrap would not uninstall
no matter what I tried. This was a long time ago, I have been researching all over the interwebs to fix my problem since. I tweaked my phone to
the point that it worked well for everything I needed, even though I was still stuck with CM.
It worked just fine... Until now. My phone went dead one day, and when I tried to charge it and reboot, it woke up stuck in bootloop. I have no idea why it decided to get stuck in bootloop, but I need to get it back ASAP. I have done hours and hours of research, set up adb and RSD Lite v5.6, got all the driver software I needed, and then found the firmware to take it back to Android v 4.0.4. My problem is that neither adb, nor RSD Lite will recognize my device. My computer recognizes the device as a Mot single adb interface, but that is the only recognition I get from my computer. My phone is saying the same thing as the quoted post above
Phone is Locked, Status Code: 0, Transfer Mode: USB Connected.
I have tried a few different USBcables, but I don't have the original factory cable from Motorola because my dog decided she wanted it more. I have an LG factory cable, but it still won't work with that.
tl;dr: My phone (Motorola droid RAZR Maxx XT912) is stuck in bootloop, adb and RSD Lite won't recognize it, but my computer will.
I'm in need of a wee bit of assistance, does anyone have any advice to offer?
Click to expand...
Click to collapse
This is a really late reply, but I just went through this. Try a different USB port on your PC. My usb 3.0 port wouldnt recognize my Photon Q

boxes said:
This is a really late reply, but I just went through this. Try a different USB port on your PC. My usb 3.0 port wouldnt recognize my Photon Q
Click to expand...
Click to collapse
Well, I actually fixed this a long time ago, but thanks for the suggestion. I ended up using mattlgroff's Droid RAZR Utulity to restore my phone to factory default. If anyone ever has any trouble with your RAZR, try using that, it'll make your life a lot easier.
If you don't mind, please swing by and give Matt some thanks, he really deserves it.

same issue with an XT926
So, i would use the utility mentioned above, except it's for a xt912, and i have the xt926. I've tried RSD Lite 6.15 and 5.7 and both with different USB cables. I downloaded ADB and the SDK Tool Kit and went through the instructions at visualgdb.com[slash]KB[slash]usbdebug-manual (sorry for the '[slash]'... noob not allowed to post links) to get "a USB driver" to install when i connect the phone. I've also downloaded a ROM file, VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml , but i've been to so many sites at this point, i can't remember where i got that file. When i open/decompress this file in RSD Lite, the software version description has 'VANQUISH" in the name. If I attempt to "Safely Remove Hardware and Eject Media", then the phone shows up as "Fastboot VANQUISH S". So i think i have the right file.
Also, i downloaded ADB and opened it. It launched a command prompt. I used the command "adb devices" to list my phone and it returns nothing.
The phone is in the AP Fastboot mode (with "Device is LOCKED. Status Code: 0" and "Transfer Mode: USB Connected", yada yada yada).
Anybody got any further ideas? Is this easier done in Linux?

Change to USB 2.0
Change to USB 2.0

[Q] Problem with GT-N7000

Hello!
I am a complete noobie when it comes to rooting androids/installing new roms and so on but I for the life of me cannot get my head around this and I keep running into the same problem no matter which way I try.
I attained this phone from a Chinese (and funnily enough bought the phone in China too) friend of mine after she decided to buy herself an Iphone. Before she gave it to me she factory reset it and it came to me stock:
Model Number: GT-I9220
Android Version: 2.3.6
Baseband Version: N7000XXKJ6
Kernel version: 2.6.35.7-N7000XXKKA-CL726566
Build number: ANZHI.COM.AX918
So to start with one of the issues is that I cannot seem to get Windows to pick up my phone as a USB device no matter what I try. I've tried downloading the latest USB drivers from the Samsung Website, installing KIES to manage the device but nothing seems to work it simply will not pick it up as a USB device. I've tried multiple computers too so it would seem to me that there is something wrong with the phone, perhaps she damaged the connector port on it, it does however charge with no problems when connected via USB. This of course stops me from using ODIN or any forms of rooting that require it to be connected through USB. I've also followed the steps on the phone to tell it to connect via USB in the Wireless menu under "USB Utilities" and under the Applications menu for USB development support.
So that aside I was glad to see that there were other options for rooting/installing a new ROM but again I seem to run into issues that I can't explain.
First off, I struggle to find the correct rom for the kernel of my phone anywhere and when I did manage to find it, it was hosted on the HotFile website which has been taken down because of legal issues.
Second is, I've tried the other methods like the "ExynosAbuse" which tells me that my version doesn't need to be rooted and when I try simply installing a new rom (seeing as it seems I do not need to root my device) I keep getting the follow error:
E: failed to verify the whole-file signature
E: signature verification failed
I get these errors for EVERYTHING that I try to install through rebooting my phone into recovery mode and "installing update from external SD." Currently the only method I have for getting the files across to my phone from my PC is through blue tooth and then manually moving them onto the SD card.
The above errors also happen when I try to install the "Clockwork Recovery Mod" by unzipping the file and running it whilst actually logged into the phone and telling it to do a recovery installation.
So basically I am at a loss as to how I can install a new custom rom on my phone, so far everything I have tried just doesn't work.
Perhaps I'm just too green and missing some fundamental step, but I've been reading/googling now for the last 2 days and it just doesn't look hopeful.
Anyone out there able to shed a little more light into this for me?
Thanks!

You have a Gingerbread version of recovery and it does not flash zip file from recovery as you already tried. You will need to update to ICS or above to use that method of rooting. Unfortunately the imo the only way is to get the USB port working so you can either update the rom or install a recovery using Odin unless some other member has to add.
Have you tried a different USB cable?

nokiamodeln91 said:
You have a Gingerbread version of recovery and it does not flash zip file from recovery as you already tried. You will need to update to ICS or above to use that method of rooting. Unfortunately the imo the only way is to get the USB port working so you can either update the rom or install a recovery using Odin unless some other member has to add.
Have you tried a different USB cable?
Click to expand...
Click to collapse
Yeah I've tried several different USB cables but still no luck.
So basically I'm screwed if I cannot get the USB to function?

Anyone got any ideas or can I pretty much just discard the phone if I can't get it to connect via USB?

Hate to post again but I'm sorta desperate, I need to know if there is something that I can with the phone or not.
Thanks!

When you try to connect to PC, if there is some action triggered by windows asking for driver somethingvthen it is driver problem. If there is no action from window then usb cable or port. You can also try to check in window device manager.
May want to try to clean usb port or look for a technician who can replace the port.
Btw, there seems to be a temporary cwm.zip which will flash and then it help you to flash proper kernel or rom. That cwm.zip is dangerous if you are using ics or jb rom. But GB rom should be fine. That is all I can think of.
Sent from my phone.

I don't think the temp cwm.zip will also be accepted by the GB recovery and will come as signature failed.

Thanks for the responses, I think the port is damaged so how because it just won't even respond in windows but it does however charge fine.
Anyways I'll look at getting a replacement port on it!
Thanks again!

Droid Turbo Not Recognized by RSD Lite

When I plug my phone into my computer and run RSD Lite, no phone appears. The operating system of the phone is completely shot, so I need to flash an image of a fresh operating system. I can't do this without being able to use RSD Lite. Motorola Device Manager doesn't seem to be recognizing any available drivers for the device. I really need this phone unbricked. Any answer would be great.

I guess you should leave your phone in bootloader mode.

In order for RSD lite to work, you have to put your device into bootloader mode by holding vol down while you power on. Also, you need to make sure that you have a version of RSD lite that supports it. I've used 6.2.4 successfully.

TheSt33v said:
In order for RSD lite to work, you have to put your device into bootloader mode by holding vol down while you power on. Also, you need to make sure that you have a version of RSD lite that supports it. I've used 6.2.4 successfully.
Click to expand...
Click to collapse
The phone is in bootloader mode and I'm using version 6.2.4.

roll11tide said:
The phone is in bootloader mode and I'm using version 6.2.4.
Click to expand...
Click to collapse
If that's the case, and your phone is still not recognized, there is either a driver problem or a physical connection problem. Assuming you're on Windows, open the device manager. When you plug in the phone, does a new device appear? If so, your problem is likely driver related. If not, there is a problem with the physical connection, which you can troubleshoot by using a different USB port and/or USB cable.

TheSt33v said:
If that's the case, and your phone is still not recognized, there is either a driver problem or a physical connection problem. Assuming you're on Windows, open the device manager. When you plug in the phone, does a new device appear? If so, your problem is likely driver related. If not, there is a problem with the physical connection, which you can troubleshoot by using a different USB port and/or USB cable.
Click to expand...
Click to collapse
I've ttried using different USB ports and cords. Yes, I tried the cord that came with the phone.

roll11tide said:
I've ttried using different USB ports and cords. Yes, I tried the cord that came with the phone.
Click to expand...
Click to collapse
Okay. So if it's in bootloader mode, and absolutely nothing happens in the windows device manager when you plug in the phone (no connected device sound, no unknown device, no known device, no nothing), and you're positive that that USB cable/ports on your PC are working, then it sounds like the USB port on your phone has stopped working, in which case there isn't much you can do. If there is no obvious physical damage, and the phone was never exposed to water, I would try getting Motorola (not Verizon) to replace it. It's free.

TheSt33v said:
Okay. So if it's in bootloader mode, and absolutely nothing happens in the windows device manager when you plug in the phone (no connected device sound, no unknown device, no known device, no nothing), and you're positive that that USB cable/ports on your PC are working, then it sounds like the USB port on your phone has stopped working, in which case there isn't much you can do. If there is no obvious physical damage, and the phone was never exposed to water, I would try getting Motorola (not Verizon) to replace it. It's free.
Click to expand...
Click to collapse
Something happens, it is just recognized as a Fastboot Quark S.

roll11tide said:
Something happens, it is just recognized as a Fastboot Quark S.
Click to expand...
Click to collapse
Hmm. Well then it is set up correctly. If you can't get RSDlite to work, you could always flash your images manually, since basically all RSDlite does is automate the Fastboot commands that are necessary to do this.
1. Install Minimal ADB and Fastboot (or get Fastboot set up in the way of your choice).
2. Unzip the contents of the firmware that you're trying to flash to the same directory as Fastboot.exe.
3. Look for the .bat file that came in the firmware zip and edit it. You should see all of the fastboot commands necessary to flash the firmware.
4. Start fastboot and perform those commands (in the order that they appear) while the phone is in bootloader mode and plugged into the computer.

TheSt33v said:
Hmm. Well then it is set up correctly. If you can't get RSDlite to work, you could always flash your images manually, since basically all RSDlite does is automate the Fastboot commands that are necessary to do this.
1. Install Minimal ADB and Fastboot (or get Fastboot set up in the way of your choice).
2. Unzip the contents of the firmware that you're trying to flash to the same directory as Fastboot.exe.
3. Look for the .bat file that came in the firmware zip and edit it. You should see all of the fastboot commands necessary to flash the firmware.
4. Start fastboot and perform those commands (in the order that they appear) while the phone is in bootloader mode and plugged into the computer.
Click to expand...
Click to collapse
I have tried flashing multiple images with ADB and fastboot, but neither of them work. Sometimes it will flash and it doesn't work, and sometimes the sparsechunks just don't get accepted into the OS. I do not know why this is happening, but I have gotten fastboot to do something to the phone, it just didn't produce any results.

Well...that's bizarre. The only reasons I can think of for a sparsechunk not successfully flashing is that it's not the right image for your model of phone, you're trying to flash an OTA update zip instead of a full firmware zip or you're trying to flash an image that is a lower version than your bootloader's version. I'm not sure what to make of the fact that it sometimes flashes successfully and sometimes does not. However, if flashing all of the images in the full firmware zip does not help you, using RSDlite won't help you either since it does the exact same thing. If I were you, I'd try to get Motorola to replace it. It's really easy to do. You pretty much just fill out a form and they send you a new one. Sorry I can't be of more help.

TheSt33v said:
Well...that's bizarre. The only reasons I can think of for a sparsechunk not successfully flashing is that it's not the right image for your model of phone, you're trying to flash an OTA update zip instead of a full firmware zip or you're trying to flash an image that is a lower version than your bootloader's version. I'm not sure what to make of the fact that it sometimes flashes successfully and sometimes does not. However, if flashing all of the images in the full firmware zip does not help you, using RSDlite won't help you either since it does the exact same thing. If I were you, I'd try to get Motorola to replace it. It's really easy to do. You pretty much just fill out a form and they send you a new one. Sorry I can't be of more help.
Click to expand...
Click to collapse
Thanks, I am already in the process of having Motorola replace the phone as I figured that would be the most logical option. Thanks for all the help! I will leave this thread open as a mystery to the community that hopefully someone will solve and in the process help someone else.