I am having problems hardspl unlocking my verizon touch pro and my friends fuze. It just sits at 0% and never does anything. We have 2 comps both with windows 7, one with professional and one with ultimate. I have unlocked the verizon one before one my comp, but using win7 starter. Running the program as admin doesn't help witth problem
the fuze (GSM) is not the same as your verizon touch pro(CDMA). if you tried to flash his phone with the CDMA hard-SPL, you might brick it. make sure you're using the right one.
Try Windows XP or make sure you are using a 32bit version of Windows 7..., I was unable to hardSPL on Windows 7 or Vista... win XP was fine
im on win7 ultimate 64 bit and havent had a problem flashing hardspl or Roms
if you havent already try a different usb port the ones on the back of your comp ..i used to mod gsm motorola phones and at times had to change to a different usb port to be able to flash new firmware onto them
I used hardSP and rom flashing with win7 Ultimate 32 .. everything is working so fine
Related
Hi .
I'm planning on upgrading the rom on my MDA Vario II (Dutch).
First I want to unlock the CID. I've got a 1.04 bootloader.
Recently I upgraded to MS Vista (RTM).
When I try to run the patched radio upgrade I always get a ERROR 150.
Yes.. I'm in bootloader mode. It's says IPL-1.01 and HERM300 SPL-1.04.
Could it be Vista??
yes its vista its had something to do with the sync tool in vista they will fix it according to a earlier post next time use the search function there is a thread about Vista and Ruu
I don't think they have released Mobile Device Center for Vista RTM yet... Right now, you see the phone as a drive... Or did you install the beta MDC?
both. I access the phone through the explorer. And I have the beta MDC setup for syncing with outlook etc.
This has been posted a million times, but here we go...upgrading ROMs will not work on Vista until manufactuers update their usb driver code on the installer; until then, use XP/2003. By the way, is that pirated Vista you have?
cant he just upgrade the rom from SD? I have a (legit) final of vista, but havent tested it yet, since i dont see the need for an uprade atm.
I have the Mobile Device Center installed and it all works perfect.
So, if you cannot do it, due to a bug in Vista, maybe the SD works
You have to be careful as if the program crashes during the upgrade of the rom you can brick your device, so I will stay with XP or SD card way to flash a rom.
aquasesh said:
cant he just upgrade the rom from SD? I have a (legit) final of vista, but havent tested it yet, since i dont see the need for an uprade atm.
I have the Mobile Device Center installed and it all works perfect.
So, if you cannot do it, due to a bug in Vista, maybe the SD works
Click to expand...
Click to collapse
I have Vista RTM and I confirm that the MDC is not stable enough for all these update work... it failed for me a few times and I'm lucky with my 8525 and it is still working OK after reflashing it with another PC (XP).
Aha. That explains that.
I've just managed to get my JasJar stuck in bootloader mode after trying many times to upgrade the ROM. This, despite the upgrade tools telling me there are errors.
Curses.
Apparently people don't know how to read what I posted...
ITS SAFE
I already flashed my Universal with Vista
-First need to install MDC, could be beta from MSDN, because it will update.(still don't know why it's not included on RTM)
-Run compability mode WIN XPSP2
-Run as Adm
thats it...
ISN'T Safe!
phamoui said:
I already flashed my Universal with Vista
-First need to install MDC, could be beta from MSDN, because it will update.(still don't know why it's not included on RTM)
-Run compability mode WIN XPSP2
-Run as Adm
thats it...
Click to expand...
Click to collapse
I am testing vista since CTP (Community Technology Preview), then RC1 (Release Candidate), RC2, now RTM (Ready To Market) as Technet Plus Member.
I can't say is safe to use it even for day by day syncing, I have always unpredictable results; my TyTn sometimes is a Smartphone, sometimes Pocket PC, syncing? may be, every time you connect you have to guess...
This happens because Windows Mobile Device Center (WMDC not included in Vista RTM) is still in BETA 3 stage, not even RC!
LESSON LEARNED
If you plan to install VISTA and you are a WM expert or just business user DON'T upgrade your XP, just install VISTA on a second HD and use your XP to solve the VISTA problems. Even Virtual PC 2007 (good to have with XP installed to have available some appz still not VISTA upgraded) couldn't use USB port, so no way to have a safe "old style" USB connection
Isn't VISTA fault, is a new tecnologies-early adopters problem
One of the most common source of problems with vista are USB drivers (no way in my knowledge to have a simple webcam working with VISTA)
This has great importance when you are doing something "uncommon" and "mission critical" like flashing something!
I am in an all VISTA house...
Has anyone found a way to upgrade using vista as of yet?
The information and driver located at http://forum.xda-developers.com/showthread.php?t=291723 works for me in doing a mtty upgrade. As for doing an entire ROM update using the full utility, I don't know... MTTY is faster, thus why I do it.
My problem is with my Cingular 8525 I need to first flash to a previous rom.
Need to use the EXE to do that and that USB driver appears to ONLY work with RUU or MTTY.
rgreenpc said:
I am in an all VISTA house...
Has anyone found a way to upgrade using vista as of yet?
Click to expand...
Click to collapse
It would be ALOT safer to not brick your device, it you dual-booted your PC and had XP available. I wouldn't want to take a chance on bricking device unless I REALLY had too, dual boot is not that hard.
Sadly... you can't install XP after VISTA because of changes to the bootloaders that Vista Uses.... you can do XP then Vista but not vice versa.
Learned this the hard way during the beta.
rgreenpc said:
Sadly... you can't install XP after VISTA because of changes to the bootloaders that Vista Uses.... you can do XP then Vista but not vice versa.
Learned this the hard way during the beta.
Click to expand...
Click to collapse
Good to know if I get ahold of Vista.
Good news... my sister-in-law still hasn't used the upgrade to VISTA that I got her, so I guess I can at least roll bacK, SuperCID, then flash to the new rom.
That way I can use POF's new v3 unlocker later when someone comes up with a magic WM6.
The one thing I hope is that the programmers out here do get their hands on VISTA as more and more people are going to get PCs that come with Vista on them and will have little choice to use it.
I am just glad I was able to do this for now....
The final version of Windows Mobile Device Center has been released and I have not had any issues doing ROM updates with the final version.
Secondly, you can use a utility call Easy BCD to modify the Windows Vista bootloader so that you can dual boot Windows XP on a computer that already has Windows Vista installed. You just install Windows XP on a separate partiotion from Vista. The computer will then only boot to Windows XP. Put the Windows Vista DVD in and do a repair and the PC will now just boot into Vista. You can then run the Easy BCD tool in Vista and tell it where you installed XP and it will modify the bootloader so that Windows XP will show up in the boot menu. The bootloader changes can also be done manually but the utility is much simplier (http://support.microsoft.com/kb/919529)
The link to the Easy BCD software is: http://neosmart.net/dl.php?id=1
rkorzuch said:
The final version of Windows Mobile Device Center has been released and I have not had any issues doing ROM updates with the final version.
Secondly, you can use a utility call Easy BCD to modify the Windows Vista bootloader so that you can dual boot Windows XP on a computer that already has Windows Vista installed. You just install Windows XP on a separate partiotion from Vista. The computer will then only boot to Windows XP. Put the Windows Vista DVD in and do a repair and the PC will now just boot into Vista. You can then run the Easy BCD tool in Vista and tell it where you installed XP and it will modify the bootloader so that Windows XP will show up in the boot menu. The bootloader changes can also be done manually but the utility is much simplier (http://support.microsoft.com/kb/919529)
The link to the Easy BCD software is: http://neosmart.net/dl.php?id=1
Click to expand...
Click to collapse
Are you saying that you have done ROM updates in Vista through WMDC Final? I tried this but it did not work. If you have done it then I may try again.
rkorzuch said:
The final version of Windows Mobile Device Center has been released and I have not had any issues doing ROM updates with the final version.
Click to expand...
Click to collapse
Perhaps I need to look at it again then... when I tried it I had no luck.
I don't want the hassle of modifying windows if I dont have to.
What updates have you done with WMDC?
@rgreen: if you're keen on buying everyone vista, i'll take a copy
I recall reading that the software for unlocking/flashing custom roms was for XP only. Is there a solid, working solution for Vista yet? If not, is anyone planning to make one?
How does activesynch work with vista & outlook 2k7? Any downsides to upgrading?
Might have been problems with Vista 64, I'm running Vista 32 and have never had a problem with custom roms.
Im a vista user and never had any problems, i never read too much into it but from what i understand its because they dont update their drivers. Someone posted the driver update in this section. Ive tried dcd's and currently using no2chems latest.
Using Vista
I use Vista on my laptop and have been experimenting with the HTC Titan since mid December.
So far, I never had an issue with Vista ( and I have experimented lots!!)
The only thing with Vista on my phone compared to my XP desktop at work is that the transfer of files to the HTC is must faster with XP. The XP machine also connects and syncs a bit faster than the Vista.
I can confirm that running Titan_Unlocker, and loading ROMs via Vista 32 with Windows Mobile Device Center works just fine.
Vista USB
I have not been able to connect with USB on my computer runing vista. I use of course windows mobile device and connect thru bluetooth, but have never been able to connect with usb. I checked the setting I WMB and have allow usb connection,.
I can tell you from experience that flashing thru bluetooth boes not work. Tried it about a year age with the Vzw upgrade on my 6700, locked up in bootloader screen, I took it to vzw and they gave me a new 6700.
That's odd ^
My Sync works both ways, and out does XP in every single way.
Vista performance depends on hardware mostly, and top notch gets you top performance.
I haven't had any problems syncing with vista.
I did have one problem when trying to upgrade to a custom rom and maybe someone here can help me answer it.
I got the sprint 3.16 test rom on there ok, then i installed the unlocker, but i couldn't get out of bootloader screen. I had the exit bootloader program but it kept saying it couldn't find the usb. then i tried attaching it to my xp comp and running the exit bootloader app and it said it was missing some dll file. so i tried redownloading and even emailing the exit bootloader from my other comp but same issue, missing dll file.
I ended up just loading the relocker and then going straight back to the latest rom because i couldn't figure it out.
Hi, I have a Sprint Touch Pro. I posted this in this section because I think my problem can be helped from anyone with my problem. I am trying to flash the Hard SPL using Parallels on Windows XP but everytime I try to it says the phone is not connected. I am able to transfer files and load cabs but specifically not flash the hard spl. I am using the correct one for a CDMA phone, and have tried with Parellels, VMware, and bootcamp with still no luck..... Any Suggestions?
You said this was a CDMA raph?
*Thread moved to CDMA forum *
Ta
Dave
Make sure ActiveSync is installed, and also that you have Microsoft .NET 1.1 and 2.0 installed.
just tried that with no luck... it will go all the way to the percentage bar of loading the SPL but than stays at 0 percent and says there is no connection
The issue is with the usb support Parallels has. I've moved onto VMware ( it converted my parallels image perfectly ). VMware is a bit older and has much better hardware support all around.
I've been able to install roms on many phones with this configuration.
how did you get it to work on VMware Fusion... i plug in the phone and it is able to put it into bootloader mode then it just stops
Never worked for me through VMWare Fusion or Parellels. I reboot in bootcamp.
Once it bootloader the PPC identifies as a different USB device, IMHO here stems the problems. Easier for me to reboot than try to solve it
VMware fusion installed with USB disabled within ActiveSync. This has let me install ROMs for a while. With some roms, dcd's latest, I've had to revert to copying the rom onto my sd card for installation that way.
I've heard people say they have gotten Odin to work on their 64 bit versions of windows, but I cant. I am able to use it on a computer running Windows 7 - 32bit, but not either of the computers I've got running 64 bit.
I've definitely installed the 64 bit the drivers. I can access the phone in ADB on these computers. Odin sees the phone and throws up a com port, but I get a weird error message with Chinese characters when I try to move forward with the flash.
Anyone have a definitive answer? Is it possible to use Odin on Win 7 64bit?
I flashed the leaked J12 with Odin on my 64bit Windows 7 laptop without any trouble.
I flashed with Odin on my W7 64bit desktop. Had a little trouble with it sticking on the verifying files at the beginning, but restarted it and it ran fine the second time. That's the only experience I've had with Odin. Just though I'd let you know that it works on my 64bit machine.
Thanks guys. I dont know what the hiccup is on my end. I might go through my drivers again just to make sure that isnt the issue.
I would highly suspect that the drivers are the issue as have used Odin on 2 separate 64bit machines. Make Sue that after u download the Sammy drivers, that they are installed, and installed correctly.
they call me...kick ass
I was never able to make any win7 system recognize my vibrant in dl mode at all, 32 or 64 bit, no matter what drivers i tried. I even tried to extract the 64 bit drivers to the 32 bit Os as I had seen mentioned in a thread some people had success with. Xp ran it like a champ on the first attempt.
Sent from my SGH-T959 + bionix 1.3 (= sexiness) using XDA App
I know were talking about different phones here but I've been scouring the internet trying to find a solution to a problem I'm having right now. when switching from 1 custom ROM to another, it was required that I flash to stock EC05, then flash to EE?? my Windows 7 Ultimate x64 wouldnt work properly (kept getting stuck in boot.bin in ODIN0 but my old faithful Netbook with Windows XP Home SP3 (x86) workd flawlessly!
I'm talking 3 HOURS of trying to get the Win7x64 to work properly and had my Epic reflashed with XP in 3minutes and 27 seconds, not counting time to install Samsung Drivers into XP (30-45 seconds)
Granted this is my experiance, but before I got x64 I was running with Win7 X86 and still never had problems. I have read through Google search that other people with x64 Windows 7 had problems. This is my story only, best of luck to ya, but I am now ONLY going to use my ol Netbook (or x86 virsion of Windows) to ODIN my phone.
Never Stop Wanting More from your devices.
Im using 64 windows OS and i don't have a problem. If your device is not recognize by your PC just reinstall the samsung drivers and you are good to go.
Sometimes you have to go into the safe mode options and disable driver enforcement policy. Then it will work.
Sent from my SGH-T959 using xda premium