Related
XDA 2 (no sim in phone at present) downloaded latest rom from O2 site. Coonected phone via cradle directly to PC and ran the utility, it finds the phone and the says your phone will be updated to version and has three new versions listed (current versions are all shown as blank) click continue and then machine sits and hangs and it the says error 112 and suggests resetting phone and trying again but the same continues to circle around.
Phone still shows usb v1.03 and cannot do anything to get out of it.
Please can any response be in plain english as i am not too much of a techy.
Any help greatly appreciated though and your knowledge is accepted but mine is less.
Matt
Can you get any of the WM5/6/6,1 ROMs to install? You may just have a faulty original ROM
MATT9711 said:
Phone still shows usb v1.03 and cannot do anything to get out of it.
Please can any response be in plain english as i am not too much of a techy.
Any help greatly appreciated though and your knowledge is accepted but mine is less.
Matt
Click to expand...
Click to collapse
Bootloader 1.03? Can you do me a favour, can you take the battery out of the back of your device, and look at the sticker under where the battery goes (on the device).
What does it say? PH10A, PH10B etc
VERSION
Ph10b Is The Number Under The Battery
*bump*
I'm having exactly the same problem, and would desperately like to try and find a solution.
I'm suspecting it's a device communication problem, as the screen showing what CD iimage version is currently on the device is listed as blank.
Once it gets to the screen where it says that the device is about to be erased before installing the update, nothing happens on the XDA 2 at all - so I imagine that it's not talking back to the computer to say "erase me".
Edit:
Problem fixed. The cause of the problem was Windows Vista. I connected the cradle to a laptop running a fresh install of XP, and was able to successfully install the upgrade ROM.
hello, greetings to all, I have a X10i, and it will install universalroot change the original numbering system for the Norse to upgrade to 2.1 when the numbers change and reset the phone tells me it should be closed forcibly Timescape, I try to upgrade to 2.1 pc companion error and tells me never recognizes the phone, and SEUS says I have the latest software, trarto of restauralor from the phone and I get error, open the market and I get error any program I run. restore it to factory settings and I get the same error, I went to the model information and tells me I have the firmware 1.6 but the model number which came out before I get one now X10i unkonwn is as if he had model now tell me I hope your help to do, ah another thing I can not install any program from mobile
When you editted the numbers when you were trying to upgrade you didn't enter the right numbers or you changed something else which you weren't meant to.
There is some amounst the may threads a solution to this which bin4ary made. I'll see if I can find it and point you in the right direction....
Sent from my X10i using XDA App
I'm sorry I can't seem to find it. My advice is send bin4ry a PM and hopefully he can find the right info for you.
Sent from my X10i using XDA App
thanks friends
nuncar21 said:
thanks friends
Click to expand...
Click to collapse
No worries. The problem is where some of the threads get so long tryng to find proper news and useful stuff gets mixed in with all the other stuff too.
Sent from my X10i using XDA App
Run this which will update you to 2.1 - http://forum.xda-developers.com/showthread.php?t=825675
XperiaX10iUser said:
Run this which will update you to 2.1 - http://forum.xda-developers.com/showthread.php?t=825675
Click to expand...
Click to collapse
and tell us how you go with it!
hello friends probe through the tutorial and download the program but when I run the program x10flashbat and asks me to connect the phone in flash mode and press any key to continue when I make that step completely closes the program that I can do
nuncar21 said:
hello friends probe through the tutorial and download the program but when I run the program x10flashbat and asks me to connect the phone in flash mode and press any key to continue when I make that step completely closes the program that I can do
Click to expand...
Click to collapse
Reread the guide carefully, and try again.
hello friends I have read all topics and I have tried everything, when I run the regedit in windows and put "Vid_0fce & Pid_adde" I do not see the DeviceInstance try putting "USB \ VID_0FCE & PID_ADDE" and I do not see anything I have Windows 7 32bit everything I've done with the phone plugged into debug mode but nothing that I get something, and when I run the file if you put nothing opens and when I plug in flash that I close the program
You have to have SEUS installed and PC Companion.. run it through PC companion once. Then do the regiedit thing.
To put your phone into flash mode, turn off the phone completely, then hold the back button and connect the phone through USB to the computer.
(when you do this, make sure PC companion is NOT running)
Hey whats up guys everything has been going well using qdl tool . Up until the driver installation
It keeps Saying
Windows found software for your device but encountered a error while attempting to install it and under it . just wanted to know if anyone is having this problem .
Qualcomm Hs- Usb Modem 9002
Running windows7 64 bit . I also followed the 64 bit guide and everything so im not sure why i get this message
I didn't have any problems with it. I followed the 64 bit guide to a T, then I installed the dell drivers before I used the QDL tool. I tried it before I installed the Dell Drivers and all I got was errors. After install of the drivers it went off without a hitch.
Dell Streak 2.2 w/DJ Steve 1.5.3
Moving to Q&A Section
Give this a try.
If you followed the instructions on streakdroid, and still having an issue try this:
Open the CMD window as administrator (shift+ctrl+enter)
then enter: bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS (NOTICE there are 2 "D's" this is not an error, and is what is required for Windows 7)
after successful completion enter: bcdedit.exe -set TESTSIGNING ON (not case sensitive)
after successful completion close the window, and reboot. This should clarify your issue with the driver problem. Windows 7 sometimes has an attitude, this worked for me If not, please let me know.
demonchild1786 said:
Hey whats up guys everything has been going well using qdl tool . Up until the driver installation
It keeps Saying
Windows found software for your device but encountered a error while attempting to install it and under it . just wanted to know if anyone is having this problem .
Qualcomm Hs- Usb Modem 9002
Running windows7 64 bit . I also followed the 64 bit guide and everything so im not sure why i get this message
Click to expand...
Click to collapse
One more thing, make sure the driver you select reads: Qualcomm HS-USB Diagnostic 9002 There is also a non diagnostic version that will cause errors as well.
Srry about that still tring to figure this forum stuff out, please excuse my noobish behvaior
ARHMogul said:
If you followed the instructions on streakdroid, and still having an issue try this:
Open the CMD window as administrator (shift+ctrl+enter)
then enter: bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS (NOTICE there are 2 "D's" this is not an error, and is what is required for Windows 7)
after successful completion enter: bcdedit.exe -set TESTSIGNING ON (not case sensitive)
after successful completion close the window, and reboot. This should clarify your issue with the driver problem. Windows 7 sometimes has an attitude, this worked for me If not, please let me know.
Click to expand...
Click to collapse
Yeah it worked really well actually Thanks a million . No im stuck trying to qdl to recongize its there. Im trying all the usb ports and it keeps saying no "connection"
demonchild1786 said:
Yeah it worked really well actually Thanks a million . No im stuck trying to qdl to recongize its there. Im trying all the usb ports and it keeps saying no "connection"
Click to expand...
Click to collapse
just to verify: are you removing the battery from your device, waiting one min, opening up QDL Tool, pres and hold the volume up button and plugging in your device in. Then it should find your device.
If thats what you are doing then I dont know what else to tell you well.... other than good luck!
You were right i didnt pay attention to actually selection Qualcomm HS-USB Diagnostic 9002. i firsty selected Just 9002. By the way the froyo i have is pre release right ? So its my best interest to update with dell right?
demonchild1786 said:
You were right i didnt pay attention to actually selection Qualcomm HS-USB Diagnostic 9002. i firsty selected Just 9002. By the way the froyo i have is pre release right ? So its my best interest to update with dell right?
Click to expand...
Click to collapse
It is the pre-release version yes. In terms of which version you choose is up to you. If you are looking for mo user customization then I would suggest Steves ROM's but if your looking for a simple froyo device the Dell 318 ROM works great as far as i can tell. Ive been using the Dell ROM for about three days now and have ad no issues to report. You just have to decide what suits you best.
ARHMogul said:
It is the pre-release version yes. In terms of which version you choose is up to you. If you are looking for mo user customization then I would suggest Steves ROM's but if your looking for a simple froyo device the Dell 318 ROM works great as far as i can tell. Ive been using the Dell ROM for about three days now and have ad no issues to report. You just have to decide what suits you best.
Click to expand...
Click to collapse
Cool makes sense. im only having one last problem . My device no longer has the 3g display signal and i cannot check or connect to the internet besides wifi. I have enabled data connection within the phone settings to no avail
demonchild1786 said:
Cool makes sense. im only having one last problem . My device no longer has the 3g display signal and i cannot check or connect to the internet besides wifi. I have enabled data connection within the phone settings to no avail
Click to expand...
Click to collapse
Thats odd, I had no issue with data.. It displayed the "H" vs 3G, but thats AT&T's new network.. I would try to do a factory reset and see if that helps. If not let me know, ill do some lookin for you
ARHMogul said:
Thats odd, I had no issue with data.. It displayed the "H" vs 3G, but thats AT&T's new network.. I would try to do a factory reset and see if that helps. If not let me know, ill do some lookin for you
Click to expand...
Click to collapse
Yeah that worked. Thanks ! loving the built in flash lol , its a huge step from dino 1.6
demonchild1786 said:
Yeah that worked. Thanks ! loving the built in flash lol , its a huge step from dino 1.6
Click to expand...
Click to collapse
Glad to hear you got it working! Enjoy your "all new" Streak
Adb fastboot time out
I AM HAVING TROUBLE WITH THE ADB...it starts to run and by the time it gets to about 47.35 seconds well it just has the error timeout ADB..how do i fix this
i am trying to up grade to the 2.2
i am using a windows vista 32bit please help as soon as possible...thank you
email me your walk through and information on how you all got this to work i would be so very thankful...
i can't even watch a Movie on my DELL STREAK....still caveman 1.6
help plz
ricanpone said:
I AM HAVING TROUBLE WITH THE ADB...it starts to run and by the time it gets to about 47.35 seconds well it just has the error timeout ADB..how do i fix this
i am trying to up grade to the 2.2
i am using a windows vista 32bit please help as soon as possible...thank you
email me your walk through and information on how you all got this to work i would be so very thankful...
i can't even watch a Movie on my DELL STREAK....still caveman 1.6
help plz
Click to expand...
Click to collapse
Try a different USB Port on your computer.. The tutorial as Streakdroid.com explains this and even has a bulletin just for that time frame There walk through is as good as it gets I assure you. Just take a look at the tutorial and the FAQ section. Good Luck!
Trouble with voice comands and blue tooth
I used the QDL and upgraded to 2.2 AT&T and I can't get my voice commands to work. What happened to nuance? after I try my voice commands it also locks up and I have to reboot. Should I try to reinstall my drivers and 2.2? Any help would be appreciated. Thanks
ARHMogul said:
If you followed the instructions on streakdroid, and still having an issue try this:
Open the CMD window as administrator (shift+ctrl+enter)
then enter: bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS (NOTICE there are 2 "D's" this is not an error, and is what is required for Windows 7)
after successful completion enter: bcdedit.exe -set TESTSIGNING ON (not case sensitive)
after successful completion close the window, and reboot. This should clarify your issue with the driver problem. Windows 7 sometimes has an attitude, this worked for me If not, please let me know.
Click to expand...
Click to collapse
Hey i just wanted to know if you know the command to enable driver verification aagin ?
Totally rediculous question here but what the hell is the qdl tool and where is it? I find all kinds of stuff on how to use it but nothing on what or where it is... thanx.
I am now a proud owner of an AT&T Streak w/2.2. OH Happy Day!!!
Once I got the proper drivers installed it was quite seemless and easy to do. the video like tutorial was well laid out. and very simple to follow. I sure hope those Geico Cavemen aren't on this forum 'cause it was so easy one of them could do it!!!
Hello. I've tried using multiple ROMs in my rooted phone with KDZ Updater, and I guess that one of the updates hanged, or maybe it was something else... I really don't know. What I do know is that my phone currently isn't able to enter recovery mode, and is also not showing any boot logos (neither 'LG' nor 'Android').
I did see some threads about this, one of them talking about starting in Download Mode and using KDZ in CS_Emergency mode with some French ROM. Well, I tried that and as soon as I press "Launch software upgrade" the program freezes until I plug my phone off the PC.
I feel as if something was stuck in my throat and the only way to get it out is by completing this... so any help will be greatly appreciated!
PS: All this happened in the process of trying to install Cyanogen Mod 10.1 (which I did not try yet).
http://forum.xda-developers.com/showthread.php?t=1119531
Need to make sure to get the right firmware, DLL file, and make sure you have the right port set on the program.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=1119531
Need to make sure to get the right firmware, DLL file, and make sure you have the right port set on the program.
Click to expand...
Click to collapse
Thanks for the reply!
I appreciate the info, and I'll be checking what you've said. All the links in that thread are inaccessible because Fileserve only lets you download what you upload. Anyway, I'm curious as to what this "DLL" file does on a smartphone... why do I need these things? I never heard of them being mentioned anywhere.
I'll start educating myself ASAP. Meanwhile, thank you very much (and by the way, if it's of help to anyone, my phone is a GT540g from Personal, Argentina.
You're welcome. Sorry, didn't check to see if the files were still there and most every other site just had reposts of the fileserve links. However, finally found what you need here:
http://files-gsm.ru/lg flesh/GT540gAT-00-V20a-722-34-DEC-28-2010+0.dz.zip
I found this dll for your phone but not sure if it works with the firmware you have for that version:
http://www.mediafire.com/download/9v9e78xronadm0c/GT540g_100506_MP.dll
"A dynamic-link library (DLL) file is an executable file that allows programs to share code and other resources necessary to perform particular tasks..."
Basically it ties together a few things in Windows to let the flash tool work for your specific device is my understanding. But they have to be specific to the phone or it won't run once it checks the build.prop of the phone vs the firmware you're trying to install.
Keep in mind, I do not have this phone and have no way to test if they will or won't work so just like any other mod or upgrade - you do so at your own risk.
Thanks, but...
First of all, I'm very sorry not to have replied before, but I've been busy. Anyway!
Thanks, I appreciate the links, but I don't understand where to put the .dll file in my phone. I know you'd think I'm an idiot who doesn't know how to use Google, but I actually did search beforehand. I simply don't get where to put it.
Also, if it's worth the shot, I just noticed that I should disable the "Modem" that activates when I plug my phone in. The problem is, KDZ just does this simple log [attached] and states "===FINISHED===" (Note that I have 2 Modems listed in my device manager [attached screenshot])
Solution GT540
Thanks for your help everyone, I came to a solution after a full year lol. Here's my enlightenment, from another Thread:
Just wanted to leave my 2 cents here, I've been trying to do my best since around august 2014, no success. 2 days ago I retried this, and I DID IT! I will tell everyone what I did very shortly:
My problem that I solved: I can boot, device works like a charm. But: no boot logos, no recovery.
My solution for TL;DR: UNINSTALL ALL DRIVERS FROM DEVICE MANAGER 1ST, then reinstall. After that, flash a fastboot ROM and use it to WIPE ALL THE DATA IN YOUR PHONE! THIS was what I needed and was never explained: you had to WIPE the old data in order to get the boot screens back.
IN THIS ORDER (THANK YOU to those people from previous replies, gathering all your info was of great value):
Uninstall all of your phone drivers from your PC!!! This is what made most of my headaches go away, just use Device Manager and uninstall anything from LGE. After that, plug in your device in your USB ports (always BACK ports, not front ports, important). It should detect all drivers and download them.
IF it fails (it generally does with LGE USB Modem), you can go to Device Manager > Unknown Device (the one that wasn't recognized) > Right Click and Update > Choose 2nd option, then choose "choose from a list of local controllers" (or whatever the button says). After that, scroll down to LG Electronics, Inc. and install what didn't install.
I also found these drivers, but I did not test them: http://www.mediafire.com/download/p693hcz6kkouh19/USB_Driver_LG_GT540.zip
Huzzah!
Now you're set to begin:
FIRST thing you wanna do is a factory reset, this is something I'd forgotten with time, don't make the same mistake as I did. You can do it by turning your phone on and pressing Volume +/- & Home & Quick Search buttons all together for 5 seconds (it works, be patient and wait for it, even if you open the camera or any other stuff).
Download this Google SDK Tools (unzip and put the folder in C:\ drive) and this Fastboot drivers for GT540 (unzip and put the files inside the folder in C:\android-sdk).
Skip this next line if you know your ROM has fastboot.
Now, if you don't have a ROM with fastboot, I recommend you use either European Open+Fastboot or V20C Orange France Fastboot ROM.
Click to expand...
Click to collapse
Since you have Fastboot enabled, now all you need to do is turn off your device (all this with its battery on it, no weird things) and hold the Camera button before turning it back on. This should take you either to a black screen, or simply to no display, like me. Either one will work anyways.
Now press the Windows key > Type cmd and open it with Right Click > Run as Administrator.
In it, type all this, command by command (you can paste by right clicking):
cd C:\android-sdk
fastboot -w
fastboot erase boot
fastboot erase system
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
And now it's go time! Do what everyone else says in here: Take out your phone's battery, SD and SIM cards, fire KDZ Updater up as Administrator (If your KDZ freezes, then it's either faulty or you did not install msxml, look for a good KDZ that comes with that file and delete your current one), choose CS_Emergency PhoneMode and:
1-Plug your phone while holding the volume DOWN button (don't worry! My phone didn't show "Download Mode" either, if you hear the Windows "Somethingpluggedin" Bump noise, it's ok).
2-Flash French V20A
3-Unplug your phone once KDZ says "==FINISHED==".
4-Plug it once again, holding the volume DOWN button.
5-Flash out.kdz (remember! it's CS_Emergency).
Click to expand...
Click to collapse
THANK YOU XDA!
So my Moto X (2014) which is around 20 months old just up and started giving this problem. When I try to boot it, it just goes to the fastboot screen and gives the error: "Fastboot reason: Failed to validate system image". The usual fastboot options like Normal Power up, factory, recovery, etc show up, but no matter what I select it gives the error: "Failed to validate system image. Boot up failed". I tried to attach some images, but being a new user was unable to link them.
Now the thing is, I am a complete noob at this stuff. So all I did was try to use adb sideload to try and re-flash the official ROM. But the adb command window doesn't seem to detect my device. Also, I'd just like to add, when I connect my phone to the PC, the standard windows sound of a USB being connected is heard, I don't know if that means anything, but I just thought I'd put it out there.
So obviously, the next thing I did was approach the service center. After a days inspection, they said, and I quote "There is an issue with the motherboard and/or PCB". I don't know what a PCB is. To fix the issue it's gonna cost me INR 12500, which is almost as much as a new phone. When I asked if they had tried re-flashing the ROM, they didn't seem to understand what I was saying, which made me a little skeptical. So, I came home and tried with the adb again, without any luck of course. Only this time when I connect my USB, I get a new error: "Fastboot reason: UTAG 'bootmode' configured as fastboot. USB connected".
Is there any way to fix this?
Or do I use it as a door stopper?
Thank you for any help in advance.
You should find some helpful info over this way: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515. You must make sure to find the correct firmware for your model and the storage that it has.
es0tericcha0s said:
You should find some helpful info over this way: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515. You must make sure to find the correct firmware for your model and the storage that it has.
Click to expand...
Click to collapse
Hi, first of all, thanks for the reply, really appreciate that.
Okay, so I went through the post you referred me to, and I have a few questions regarding that, if you don't mind.
1) The phone in that post is the Moto X (2013), I have the 2014 model (the 2nd Gen). Does it make any difference? or is it the same procedure?
2) It says "Return to stock". I never left the stock ROM. Never rooted the phone, didn't even unlock the bootloader. I'm not even sure if my USB debugging was enabled.
4) Most of the download links on the post seem to be dead.
How should I proceed?
Again, thanks for any help in advance.
souamguha said:
Hi, first of all, thanks for the reply, really appreciate that.
Okay, so I went through the post you referred me to, and I have a few questions regarding that, if you don't mind.
1) The phone in that post is the Moto X (2013), I have the 2014 model (the 2nd Gen). Does it make any difference? or is it the same procedure?
2) It says "Return to stock". I never left the stock ROM. Never rooted the phone, didn't even unlock the bootloader. I'm not even sure if my USB debugging was enabled.
4) Most of the download links on the post seem to be dead.
How should I proceed?
Again, thanks for any help in advance.
Click to expand...
Click to collapse
I'm terribly sorry about the mix-up with the generation. I was half asleep looking through the forum.
This is the one you need: http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
I realize that you have not modified the phone, but this is how you reload the software+firmware back to the phone, or what you referred to as "flashing the stock rom" to the shop you took your phone to. If this fails, there's not much else that you would personally be able to do to fix the device.
USB Debugging on does not matter as you can boot directly to the bootloader by powering off, then press the power and volume down buttons simultaneously.
Good luck!
es0tericcha0s said:
I'm terribly sorry about the mix-up with the generation. I was half asleep looking through the forum.
This is the one you need: http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
I realize that you have not modified the phone, but this is how you reload the software+firmware back to the phone, or what you referred to as "flashing the stock rom" to the shop you took your phone to. If this fails, there's not much else that you would personally be able to do to fix the device.
USB Debugging on does not matter as you can boot directly to the bootloader by powering off, then press the power and volume down buttons simultaneously.
Good luck!
Click to expand...
Click to collapse
Okay, so I followed the thread exactly. But I can't get past the first step. When I type in "adb devices" on the adb command window, nothing shows up on the device list. (Note: My phone is already in the AP fastboot mode. I don't know if adb is supposed to detect it when it's in that mode).
But, Motorola device manager is able to detect my phone. When I run Motorola device manager with my phone connected, it searches for "repair software" for a while and then gives a pop-up saying "Your software is up to date" (and the name of the ROM installed).
Any further advice?
Thanks.
Use the fastboot method since you're in the bootloader. The adb is only mentioned there as an alternative way to get to the bootloader. Since you are there, skip that step.
Sorry for the late reply. But turns out the Boot IC of my motherboard was faulty. Whatever I did, it would always get stuck on the fast boot screen. Replaced my motherboard and now it's all good .
Thanks for all the help guys.