Related
Hi,
You may have heard this problem many times, I tried to upgrade my ROM and it failed a few seconds in because for some insane reason the phone rebooted during the upgrade, It now says USB on the top and v1.00, Tried hard reset but does not work, I have also tried to reflash the rom but I am using MS vista that uses an alternative to Activesync, so the upgrade says 202 connection error, Please can anyone help me!!!!
wgriffiths said:
Hi,
You may have heard this problem many times, I tried to upgrade my ROM and it failed a few seconds in because for some insane reason the phone rebooted during the upgrade, It now says USB on the top and v1.00, Tried hard reset but does not work, I have also tried to reflash the rom but I am using MS vista that uses an alternative to Activesync, so the upgrade says 202 connection error, Please can anyone help me!!!!
Click to expand...
Click to collapse
you need to downgrade your drivers... there's a way of doing it, but I've never done it myself, so you'll need to find someone else who has.
Olipro said:
you need to downgrade your drivers... there's a way of doing it, but I've never done it myself, so you'll need to find someone else who has.
Click to expand...
Click to collapse
Activesync wont install on Vista, which to be honest would probably work fine it is stupid M$ prohibiting it to install,
The computer will detect the phone, it says Microsoft USB Sync, does it need to be a ceartain driver for this to work?
Really need help on this! Computer recognises PDA says Microsoft USB Sync, What is the correct driver, the updater is not recognising the phone
Please anyone if you have even a small idea please post it!!! PLEASE!
wgriffiths said:
Please anyone if you have even a small idea please post it!!! PLEASE!
Click to expand...
Click to collapse
Yeah, sorry it took a while, for some reason this thread only popped up as new today???? strange...
For your problems... uninstall ActiveSync... reduntant in Vista, there the new WMDC (I take it you realise this?). After uninstall, connect your device and it will install WMDC with the appropriate updates, then you have to check this thread here....
http://forum.xda-developers.com/showthread.php?t=291723.
That thread may be dated and there may be a newer one, but there were many people using it successfully and I was one of them until I downgraded again to XP. Hope it helps.
BTW, Vista sucks A$$, it's just not ready for driver and program release, and if you get an independant memory and CPU monitor, it'll show you that the built in one lies through it's teath!!! But hey, each to it's own. Regards.
plz tell me dear how we connect in a dead stage
Other option would be to flash the ROM using a machine with XP, wich I find more easy than in vista
Hope it helps,
When I tried it in Vista I had a similar problem, I tried it on an XP machine no problems, am using Win7 now but dont know if upgrading the ROM will work yet, a bit risky.
I Have Tried Updating This Twice And When Its Flashing At 3 % I Get Error 270..and It Says The Image File Is Corrupted...anyone Know What Is It About??
URGENT HELP REQUIRED ON THE SAME !!
I tried to flash all roms on my phone... and the USPL tooo.....
but unfortunately I was un sucessful
Please help...
Take sim and memory card out and try again.
@[email protected] said:
Take sim and memory card out and try again.
Click to expand...
Click to collapse
and try, and try, and try until its done.
Or if you have Vista on you PC, just do it in XP.
jaatboyslim said:
I Have Tried Updating This Twice And When Its Flashing At 3 % I Get Error 270..and It Says The Image File Is Corrupted...anyone Know What Is It About??
URGENT HELP REQUIRED ON THE SAME !!
I tried to flash all roms on my phone... and the USPL tooo.....
but unfortunately I was un sucessful
Please help...
Click to expand...
Click to collapse
Hello my friend, this is a very wild guess, but maybe u should see if you have an active connection with your pc, then maybe, you should try to flash an official rom suited for your device.
If none of the above worked, just try the search button, it´s an amazing tool, believe me, sometimes it can do miracles.
Try that.
Cheers
Thanks all for the support..
but I'm still trying..............
download the ROM again, perhaps the previous download wasn't really 100% (98% or something), and that's why the image is corrupted.
Or try a different ROM.
Rename the ".nbh" in "ARTEIMG.nbh" copy to SD - root - and try to flash from SD as explained here: http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
For me the easier way to install a ROM. Without errors depending by the OS.
Good luck
Zecanilis said:
Or if you have Vista on you PC, just do it in XP.
Click to expand...
Click to collapse
I use Vista and have no problems to run uspl and flash.
Frannek said:
I use Vista and have no problems to run uspl and flash.
Click to expand...
Click to collapse
That's great for you...
have you tried re-downloading the rom? and re-flashing an original rom instead?
try searching the forum, somebody once suggested installing the XP device drivers for vista and it helped some people
Try Uspl Included in Touch roms
1- I think ur phone is locked ie. u have installed original rom.
2- I think the only uspl that will work will be included withen Artemis Touch Roms WWE WM6.1(3.01)(4.0)(4.01)(4.02)
Link http://forum.xda-developers.com/showthread.php?t=400452
Good luck
Just enter Airplane mode. Disable all connections.
Close this Thread .. My Work completed...
Hey guys,
I installed FB27 + radio through CWM. I was previously on EL29. I want to get back to EL29, so I did the following:
Boot into windows (daily driver is osx)
Put phone into DL mode
Start Odin-oc el29
connect phone to usb
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
So i closed out everything, then opened Kies. It said it had an update, so I installed it, which included some driver updates.
I retraced my steps from above.
I tried installing the samsung driver package, still nothing.
Odin was working just fine before, and I hadn't changed anything in windows. I don't even use windows unless i'm using odin!
Any help is appreciated, I would like to get back to EL29!
[update]
This is likely a windows problem, not a problem with FB27. Sorry for causing any panic
few questions
what version of odin/are you using the self-extracting auto odin back?
http://forum.xda-developers.com/showthread.php?t=1433101
have you removed the kies/samsung drivers, then reinstalled? if you're having problems and it's related to the drivers (which it may be), sometimes you have to remove not just reinstall.
also, have you tried a different usb cord? sounds stupid i know, but they get **** stuck in the ends, or otherwise damaged, and cause weird issues in situations like this but otherwise work fine.
i just odined back last night using the package in the thread above, and it worked fine.
Just to make sure, you do have samsung kies installed, right? You need their drivers.
exabrial said:
Hey guys,
I installed FB27 + radio through CWM. I was previously on EL29. I want to get back to EL29, so I did the following:
Boot into windows (daily driver is osx)
Put phone into DL mode
Start Odin-oc el29
connect phone to usb
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
So i closed out everything, then opened Kies. It said it had an update, so I installed it, which included some driver updates.
I retraced my steps from above.
I tried installing the samsung driver package, still nothing.
Odin was working just fine before, and I hadn't changed anything in windows. I don't even use windows unless i'm using odin!
Any help is appreciated, I would like to get back to EL29!
Click to expand...
Click to collapse
From your post you're trying to do the odin all in one self extractor... have you tried just using odin to flash the EL29 stock recovery repack and then flash through CWM from there?
http://forum.xda-developers.com/showthread.php?t=1390393&highlight=rogue
http://goo-inside.me/kernels/TeamRo.../rogue_ET-recoveryonly-1.1.4-rc0-odin.tar.md5
exabrial said:
Hey guys,
I installed FB27 + radio through CWM. I was previously on EL29. I want to get back to EL29, so I did the following:
Boot into windows (daily driver is osx)
Put phone into DL mode
Start Odin-oc el29
connect phone to usb
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
So i closed out everything, then opened Kies. It said it had an update, so I installed it, which included some driver updates.
I retraced my steps from above.
I tried installing the samsung driver package, still nothing.
Odin was working just fine before, and I hadn't changed anything in windows. I don't even use windows unless i'm using odin!
Any help is appreciated, I would like to get back to EL29!
Click to expand...
Click to collapse
If regular ODIN is working fine, look in the 2nd post, section #A2. There are regular ODIN packages for EL29.
http://forum.xda-developers.com/showthread.php?t=1433101
Personally I would try to figure out why ODIN OneClick isn't working because it might indicate some problem, but I understand if someone wants the quickest solution.
Use another cable besides samsungs crappy pos
Sent from my SPH-D710 using Tapatalk
Also try a simple reboot. Sometimes if I run sfhub's one click then Odin I have to reboot in between but only sometimes
Sent from my Nexus S 4G using xda premium
sfhub said:
If regular ODIN is working fine, look in the 2nd post, section #A2. There are regular ODIN packages for EL29.
http://forum.xda-developers.com/showthread.php?t=1433101
Personally I would try to figure out why ODIN OneClick isn't working because it might indicate some problem, but I understand if someone wants the quickest solution.
Click to expand...
Click to collapse
I have used EL29, EG30 of yours several times without any problems sfhub. I don't know why I occasionally need to reboot in between one click and regular Odin but its no big deal. 90% of the time I dont
Sent from my Nexus S 4G using xda premium
exabrial said:
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
Click to expand...
Click to collapse
According to Microsoft, code 42 means there is a problem with multiple instances of the driver and the solution is a reboot (as John pointed out)
My theory as to why it is happening is there is a problem either in the USB driver or in ODIN OneClick with shutting down the USB bus when the flash is done, so next time you run it there is already an instance. Another possibility is if you use different USB ports on the computer between sessions, then the USB driver might get confused and keep multiple instances.
http://support.microsoft.com/kb/310123
Code 42
Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. (Code 42)
Recommended resolution
A duplicate device was detected. This error occurs when a bus driver incorrectly creates two identically named sub-processes (known as a bus driver error), or when a device with a serial number is discovered in a new location before it is removed from the old location. You may be able to resolve this problem by restarting your computer.
Restart your computer
Click Start, click Shut Down, and then select Restart in the Shut Down Windows dialog box to restart the computer.
Click to expand...
Click to collapse
Ok, so the best thing to try then is to uninstall Kies and the samsung driver package. I'm a windows nub, (I've haven't used windows since 1999) how do I make sure that any existing drivers that have been installed for a particular port are also wiped out? My fear is that removing kies won't remove any drivers that have been installed against a particular device... or is that not true.
exabrial said:
Ok, so the best thing to try then is to uninstall Kies and the samsung driver package. I'm a windows nub, (I've haven't used windows since 1999) how do I make sure that any existing drivers that have been installed for a particular port are also wiped out? My fear is that removing kies won't remove any drivers that have been installed against a particular device... or is that not true.
Click to expand...
Click to collapse
I don't think you should have to do all of that. Where EXACTLY are you in the process?
Sent from my SPH-D710 using xda premium
JohnCorleone said:
I don't think you should have to do all of that. Where EXACTLY are you in the process?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Same as my initial post. I'm currently at work Just trying to develop a POA.
According to MSFT, the error code 42 is not a problem with driver installation. It is a problem at runtime with multiple instances of the driver.
Did a reboot not work? Perhaps there are problems with the driver in the 64-bit and 32-bit locations?
I've rebooted the crap outta it already...
Anyway, uninstalled Kies, and samsung drivers package, and QPST for the hell of it. Rebooted, reinstalled Kies, now I get Error code 43...
I tried "search for a better driver" and pointed it to the samsung kies folder to no avail.
exabrial said:
I've rebooted the crap outta it already...
Anyway, uninstalled Kies, and samsung drivers package, and QPST for the hell of it. Rebooted, reinstalled Kies, now I get Error code 43...
I tried "search for a better driver" and pointed it to the samsung kies folder to no avail.
Click to expand...
Click to collapse
Are you on 64-bit? Sometimes the drivers need to be placed in the 32-bit location.
Have you gone over the general USB connection troubleshooting here:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
Sorry, I go through a lot of threads and PMs so sometimes lose track of what people tried and didn't try.
I'm not at all experienced with Mobil ODIN, but wouldn't it be possible to forego the computer completely to get back to EL29?
It depends on the situation. In this case, probably yes. Mobile ODIN needs your phone to be able to boot into Android and needs you to be rooted, which the OP probably is. ODIN can handle situations where your phone won't even boot into Android.
sfhub said:
It depends on the situation. In this case, probably yes. Mobile ODIN needs your phone to be able to boot into Android and needs you to be rooted, which the OP probably is. ODIN can handle situations where your phone won't even boot into Android.
Click to expand...
Click to collapse
True, but he doesn't sound soft bricked, which is why the thought crossed my mind.
sfhub said:
Are you on 64-bit? Sometimes the drivers need to be placed in the 32-bit location.
Have you gone over the general USB connection troubleshooting here:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
Sorry, I go through a lot of threads and PMs so sometimes lose track of what people tried and didn't try.
Click to expand...
Click to collapse
It's quite alright, I appreciate the help. I followed the directions in that post, and am getting the same problem... It is windows7 64bit. basically, installed the drivers to C:\Program Files (x86)\Samsung\USB Drivers
I guess I'll try mobile Odin... windows hasn't improved any over the last 10 years I see.
Can someone help me I have the same problem it happened to me about a week ago when i tried flashing one of calk's rom and then all i know is that triangle disappeared from the samsung animation and then my computer will not recognize it.I've looked here and google and cannot find a solution!!!PLEASE help me!!I've noticed people with similar problems but no help.
Also I got mobile odin and tried to unroot but I am afriad I wont be able to root again since it will not discover my device.
Having a bit of an issue with the bootloader unlock instructions from here:
http://unlockbootloader.sonymobile.com/instructions
Basically the problem is that step 13 just isn't happening. First time I tried it DID pop up but for some reason the bit asking for drivers closed down. Now I can't get to the point where I choose the drivers so I can't go any further.
Anyone know how to fix this?
Thanks!
I don't Understand What do you mean Go to -->Right Click Computer-->Propeties-->Device Manager-->Then Go to "S1 Boot Device"-->Then Right Click on it and Click Driver Something-->Select the Drivers The Drivers for Fastboot never Get Found By windows You'll manually do them on every PC for the first Time!
Xperia4life said:
I don't Understand What do you mean Go to -->Right Click Computer-->Propeties-->Device Manager-->Then Go to "S1 Boot Device"-->Then Right Click on it and Click Driver Something-->Select the Drivers The Drivers for Fastboot never Get Found By windows You'll manually do them on every PC for the first Time!
Click to expand...
Click to collapse
Thanks! I can't believe Sony didn't put that in their guide. Thought it would be something simple but my last phone I did this on was a Nexus One so i didn't have to do that. Once again thanks! Problem solved.
Then again perhaps there is still a problem...
Did this, went to the right file, the drivers are DEFINITELY here, yet Windows can't find them. WTF Windows?
Oh well, sure its not a huge issue. Any ideas anyone?
Use the latest version of PDAnet. It will solve your driver problems, you won't have to do anything else.
Sent from my R800i using XDA
By any chance, are you using AMD machine?
niks10 said:
By any chance, are you using AMD machine?
Click to expand...
Click to collapse
Yes actually, I am. Not by choice but that's not really relevant right now. Does that make a difference here?
Maverick_G said:
Use the latest version of PDAnet. It will solve your driver problems, you won't have to do anything else.
Sent from my R800i using XDA
Click to expand...
Click to collapse
Sorry but I've tried looking this up and I'm not sure if I'm finding the right thing. Mind sending a link or something? Thanks!
You need some different AMD driver for fastboot to work.
I found the same problem with AMD machine and used a different driver posted by someone on this forum.
Search for it and you will be ok to boot into fastboot once it is properly installed.
niks10 said:
You need some different AMD driver for fastboot to work.
I found the same problem with AMD machine and used a different driver posted by someone on this forum.
Search for it and you will be ok to boot into fastboot once it is properly installed.
Click to expand...
Click to collapse
Ah right, you would really think that Sony would mention these things. Thanks, I'll give that a shot later, bit busy right now.
addam360 said:
Sorry but I've tried looking this up and I'm not sure if I'm finding the right thing. Mind sending a link or something? Thanks!
Click to expand...
Click to collapse
Type pdanet on Google and the first couple of links will show its official page.. Download the windows version of it then install it, it may take a couple of tries. (it took me 3 tries before it got installed)
Sent from my R800i using XDA
Problem has been solved. The PDAnet method worked for me. Thanks everyone who helped!
Xperia4life said:
I don't Understand What do you mean Go to -->Right Click Computer-->Propeties-->Device Manager-->Then Go to "S1 Boot Device"-->Then Right Click on it and Click Driver Something-->Select the Drivers The Drivers for Fastboot never Get Found By windows You'll manually do them on every PC for the first Time!
Click to expand...
Click to collapse
I got a similar problem, except that, Device manager does not list S1 Boot device..
But the phone is connected in fastboot mode.. blue led and everything..
the only things listed are:
* Base System Device
* Bluetooth Peripheral Device
* Bluetooth Peripheral Device
* Bluetooth Peripheral Device
* Bluetooth Peripheral Device
* Bluetooth Peripheral Device
But I can eject the device by clicking on the icon in the bottom right.. and that reads "Eject S1Boot Fastboot" ..
but why isnt it listed in device manager?
Fix for unlocking bootloader on AMD based computers
For any one looking for the AMD google driver here it is:
http://forum.xda-developers.com/showthread.php?t=1554805
Just unzip and copy to the "Android SDK > extras > google folder on your computer" step 9 and 10 in the sony instructions, good luck people =)
I need to restore my Tab S. I installed Windows on Parallels in order to root it and have been using CM12.
Now no matter what I do Odin fails to see my Tab when in download mode so I can't use it (I've spent all day doing everything forums reccomend - swapping cables, ports, un/installing KIES, blah, blah - 'Windows sees the Tab, but Odin just does not. Heimdall on the Mac just does nothing as it needs a PIT file I don't have and can't find.
Isn't there a way to restore stock firmware with TWRP? Or a rooted near stock ROM that I can unroot?
Any help would be much appreciated.
zemblance said:
I need to restore my Tab S. I installed Windows on Parallels in order to root it and have been using CM12.
Now no matter what I do Odin fails to see my Tab when in download mode so I can't use it (I've spent all day doing everything forums reccomend - swapping cables, ports, un/installing KIES, blah, blah - 'Windows sees the Tab, but Odin just does not. Heimdall on the Mac just does nothing as it needs a PIT file I don't have and can't find.
Isn't there a way to restore stock firmware with TWRP? Or a rooted near stock ROM that I can unroot?
Any help would be much appreciated.
Click to expand...
Click to collapse
I feel your pain, but I think a full windows installation is the only way to get round this. I've tried windows in a Virtualbox and had the same results as you. Googling shows TWRP can restore a backup but I can't see any option to load stock and there's nowhere I can see to download a PIT file
But would this be worth a try? http://www.samsung.com/uk/support/usefulsoftware/KIES/
I take it then you didn't make a full backup in recovery, which is sort of the whole point in flashing it in the first place?
Your issue could be a missing driver.
Reinstall the Samsung driver on the host and make sure it is the guest operating system that is connecting to the usb port not the host.
Also do you know Windows can be installed to a usb drive?
http://lifehacker.com/how-to-run-a-portable-version-of-windows-from-a-usb-dri-1565509124
Mahasamatman said:
I feel your pain, but I think a full windows installation is the only way to get round this. I've tried windows in a Virtualbox and had the same results as you. Googling shows TWRP can restore a backup but I can't see any option to load stock and there's nowhere I can see to download a PIT file
But would this be worth a try? http://www.samsung.com/uk/support/usefulsoftware/KIES/
Click to expand...
Click to collapse
Yup I think you're right, installing Boot Camp for the 1st time. One upside is that when I've finished with Windows I'm gonna put on Ubuntu (for the first time in 10 years!), getting bored of OS X and use hardly any of the Apple apps on it anyway...
Tried KIES for Mac but it doesn't seem to recognise custom ROM'd Tabs. Cheers.
ashyx said:
I take it then you didn't make a full backup in recovery, which is sort of the whole point in flashing it in the first place?
Your issue could be a missing driver.
Reinstall the Samsung driver on the host and make sure it is the guest operating system that is connecting to the usb port not the host.
Also do you know Windows can be installed to a usb drive?
http://lifehacker.com/how-to-run-a-portable-version-of-windows-from-a-usb-dri-1565509124
Click to expand...
Click to collapse
Actually buddy methinks you're onto something. Just downloaded Samsung PC Studio and that installed a 'gadget serial' driver that ODIN seems to recognise! :laugh:
Success!
OK - posting this in case another 'me' is searching for the same. Both commenters were helpful. Thanks.
It was a weird trial and error of installing both KIES and Samsung PC studio, that installed all the necessary drivers, the restore took minutes using Odin 3.09. I also had to try a few different USB cables as it seemed choosy, so Parallels can work though it all seems a bit pot lucky!
I now have a 'fresh' install of KK. Not sure if it will show up as a Knox tripper.
The Samsung usb drivers can be downloaded here: http://www.mediafire.com/download/a4hd8y0c1iakysk/Samsung-Usb-Driver-v1.5.49.0.exe