Related
O.k. for everyone who's traying to Flash in Vista
Donwload the files from this link: http://rapidshare.com/files/38401715/Manual_and_files.rar.html
and extract them in a new created folder like for example your desktop. Extract the USB Modem Vista in a different folder on your desktop (easy to find)
- put your device in bootloader mode (press and hold power, light and softreset button)
- connect the MDA to your computer.
- open computer management (devicemanager) in vista, rightclick computer in startmenu and select manage (see step 1)
- in computermanager open devicemanager (step 2)
- follow step 3 and 4.
After step 4 browse to the folder where you extracted the USB Modem Vista and choose next.
It will install the active sync drivers to vista and you will be able to flash.
I attached a exit bootloader file to exit bootloader mode (you can also install drivers without flashing the device)
YOU ALWAYS HAVE TO EXIT BOOTLOADER MODE!!!! EVEN BEVORE FLASHING!!!!
If you do it properly it will be done in less than 4 minutes.
Good luck.
Duanes
excuse my poor english
hey, the rapidshare link does not work
any alternate location that i can get the file from?
thanks!
San
thanks for your help! i can finally flash through Vista!
dreamtheater39 said:
hey, the rapidshare link does not work
any alternate location that i can get the file from?
thanks!
San
Click to expand...
Click to collapse
you can send me your email trough pm and then I can send the files to you!
sstrunks84 said:
thanks for your help! i can finally flash through Vista!
Click to expand...
Click to collapse
I know what you mean, I could finally use only vista as o.s.
hey duanes!
I finally got the link to work and downloaded the file!
I could update the drivers and everything worked just fine!
Thanks a million for this, i've been looking around for this for a loooong time!
cheers m8!
San
No thanx, good luck flashing!
nonsense
duanes said:
O.k. for everyone who's traying to Flash in Vista
- put your device in bootloader mode
...
It will install the active sync drivers to vista and you will be able to flash.
Click to expand...
Click to collapse
Nope. In Vista with current drivers and updates the driver cannot be updated to an older one; neither in bootloader mode (uknown USB device) nor in standard mode (PocketPC).
vjj
Don't hate if you're a noob With Vista
Download my package and see for yourself mate!
I run Vista Business for almost 6 months and I'm flashing trough Vista for quite a long time now. Even now after upgrading the Windows Mobile Device Center.
So as far as I know your post is based on nonsence!!!
As I've said many many times, you have to do it exacly the way I wrote it.
Pro to noob
for your info, I've been using Vista for about two years.
building and flashing ROMs for 3 years now.
I do not argue with possibility to flash ROM in Vista.
I do argue with possibility to use your instruction universaly in all standard Vista installations.
I've seen and tried both possibilities myself.
Universal in boot mode:
"The best driver software for your device is already installed.
Windows has determined the driver software for your device is up to date.
Uknown Device."
Have you ever seen this message? I doubt.
I've seen that message when you don't do it correctly.
I'm not going to discuss with you if it works or not. And as far as being a pro... been working at microsoft for 6 years. Cheers mate! and good luck flashing building or whatever it is that you do.
Nonesence Again.
vjj said:
for your info, I've been using Vista for about two years.
building and flashing ROMs for 3 years now.
I do not argue with possibility to flash ROM in Vista.
I do argue with possibility to use your instruction universaly in all standard Vista installations.
I've seen and tried both possibilities myself.
Universal in boot mode:
"The best driver software for your device is already installed.
Windows has determined the driver software for your device is up to date.
Uknown Device."
Have you ever seen this message? I doubt.
Click to expand...
Click to collapse
I was using vista since beta1, and i have been using WMDC since its beta stages. And i do have to confirm the method with updating your drivers with AS ones works Perfectly. Try again, but dont search for drivers, update it manualy, AND, dont forget to untick ALLOW USB CONNECTION in WMDC before pluging in a bootloaded device. That really does work a charm.
But what about Vista 64 version? This driver don't want to install on Vista 64...
Mr Groch said:
But what about Vista 64 version? This driver don't want to install on Vista 64...
Click to expand...
Click to collapse
use the ones from activesync for XP x64
This isn't working for me? I tried it numerous of times... I'm using Vista Home Premium and it goes through everything- but when I started to install my ROM- the program shuts down at the part where it begins to load
thetruestar said:
This isn't working for me? I tried it numerous of times... I'm using Vista Home Premium and it goes through everything- but when I started to install my ROM- the program shuts down at the part where it begins to load
Click to expand...
Click to collapse
Can you please tell me more like, wich Rom and wich MDA or PDA you are using?
Did you trie to rightclick te ROM update and run it as administrator?
I had the Wizard and I was trying to update the Wizard with the Touchflo ROM
thetruestar said:
I had the Wizard and I was trying to update the Wizard with the Touchflo ROM
Click to expand...
Click to collapse
Uhh.. is that the right ROM for that device??
duanes said:
Uhh.. is that the right ROM for that device??
Click to expand...
Click to collapse
Yes... I uploaded it from my XP computer which I rarely use- but I wanna start uploading with my VISTA...
This is how it looks...
This is the message that pops up
thetruestar said:
Yes... I uploaded it from my XP computer which I rarely use- but I wanna start uploading with my VISTA...
This is how it looks...
This is the message that pops up
Click to expand...
Click to collapse
I'll try to find a solotion for this!
(Moved from development forum, newb root thread)
I recently received my phone back from a HTC repair. I hadn't used it til today as I was waiting for froyd 1.5 to come out before rooting it and setting it up. Today I switched it on and it asked me if I wanted to update the software, I clicked no. Then I followed the steps in the OP but had problems in step 5 : everytime I typed anything (including "su") and hit enter I had a message saying "denied" or words to that effect, despite the UniversalAndroot program giving the "woot rooted" message.
This is the part where I might have done something stupid - I decided to let the phone update itself to the latest software, and then I was planning to run the UniversalAndroot again. I thought that maybe UA had been tested on the latest official HTC stuff but not whatever 2.1 but not fully updated version that mine had come back from repair with. It went to the update screen and the progress bar completed, it tried to reboot but just got stuck on the white boot screen with the green HTC logo. If I pull the battery out and start again it just hangs at the same screen.
I can get the 2.73.405.5 WWE RUU to see the phone when in fastboot, but when I try to update it it eventually gives me error 140 "bootloader version error".
I tried to load it through HBOOT using kazuni's technique in his thread "A way of flashing the RUU rom extract" (sorry, it won't let me paste a link to the actual thread) but it says "main version is older, update fail". Do I need to send it off to HTC again? I just got it back! Will they be able to tell what broke it and refuse to fix it?
Many many thanks
Try the 2.1 downgrade in my sig below.
Please could you explain "The recovery can be flashed via running 'runindos.bat'."? I assume I need to install this adb program that people keep mentioning?
Also what is the goal here? To upgrade my phone to 2.1 (which was already on from the HTC repair, the OTA update just said something about adding g-sensor calibration tool) to then root it or to downgrade my phone to 1.5 to root?
Many thanks!
Ah, just seen adb guide on villain forums. OK, I'll follow the guide to get adb installed, put your recovery files in the /tools folder, but then how exactly do I flash the recovery? Simply by typing runindos.bat in cmd whilst in the correct folder?
Ah, I see, I just run the batch file from your recovery download. Sorry for all the dumb questions! I ran this with my phone on fastboot usb but it said this :
adb server is out of date. killing...
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
"Files copied and permissions set, rebooting HTC Andriod 2.1"
"Your phone will now reboot into normal mode, then reboot into recovery mode. I
f it does not reboot the second time, wait 10 minutes and manually reboot and be
gin again."
error: device not found
As far as I can tell nothing happened on my phone. I assume my usb drivers are fine as the RUU was able to begin updating before it gave me the 140 version error. Any ideas?
It's the ADB drivers, what OS are you using?
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
HairyBones said:
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
Click to expand...
Click to collapse
You may want to build an XP workstation eitha virtual or physical. Don't be alarmed. Yes, the latest version of HTC Sync does contain the drivers. However, they some what don't work for majority of users. Sorry.
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
HairyBones said:
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
Click to expand...
Click to collapse
virtual box - http://www.virtualbox.org/
vmware player - http://www.vmware.com/products/player
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
HairyBones said:
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
Click to expand...
Click to collapse
Yeh, to install XP you will need an install disk, unless you download XP Trial version VHD. This is the trial version from Microsoft in virtual machine mode.
http://www.microsoft.com/downloads/...90-958F-4B64-B5F1-73D0A413C8EF&displaylang=en
Windows XP Mode with Windows Virtual PC, available for Windows 7 editions Professional, Enterprise, and Ultimate, provides a licensed virtual Windows XP Professional environment for compatibility with applications not compatible with Windows 7. Windows Virtual PC supports USB attachment, therefor supporting direct connection of USB devices to the virtual Windows XP environment.
For information and to download Windows XP Mode or Windows Virtual PC visit the product page microsoft.com/windows/virtual-pc/default.aspx
Brandon
Windows Outreach Team- IT Pro
Hello, could anybody help please?
I am trying to run MAupgradeUt_noID, but I get the error message that there is a missing .dll.
What I have is Lenovo N500, 4 GB of memory, 2 GHz dual core, Windows 7 64 bit, conexant high definition smart audio 221, 250 GB hard disk, Windows 7 experience rating 3.5.
I had a look through this thread, http://forum.xda-developers.com/showthread.php?t=630416 and wondered whether there was anybody who had found a way to flash using Windows 7 64 bit?
I don't have access to a Windows XP machine.
Use MS VM XP Mode
Okay, I have downloaded the virtual XP and it all works fine. I tried running Maupgradeut-noid but I got the error message this application failed to run becauseRUU.DLL was not found. Reinstalling the application may fix this.
So on the virtual XP machine, I tried loading ActiveSync 4.5. It still came up with the same error message.
When I run the Maupgradeut-noid the only other file in the directory is nk.nbf
any help appreciated.
you need all this files:
http://www.sendspace.com/file/t8vgu9
+ the nk.nbf file in the same folder
it works in XP mode! (if needed put in bootloader mode = reset+power button+camera button)
Okay, now I have done all that, encountered another problem..
Everything runs okay but I get the error message;
"The ROM utility does not design for your device. Please get proper ROM upgrade utility and try again."
Now on the front of my telephone it says Xda lls. It has four buttons the okay button, Internet button, e-mail button, and the home button. Below that it has a navigation button/s and the telephone on and off button. A keypad slides down from behind the telephone. I am absolutely positive that this is a blue Angel.
Any suggestions welcome.
It works perfect with BA. I had to put it in bootloader mode.
Here is a picture of my telephone to confirm that it is indeed a Blue Angel.
http://i627.photobucket.com/albums/tt356/Pterodactyl_2012/o2xda_iis.png
Yes it is!
When you put it in bootloader mode is it recognized in windows?
After that do you share that USB connection in XP mode?
flyboy_____ said:
Yes it is!
When you put it in bootloader mode is it recognized in windows?
After that do you share that SUB connection in XP mode?
Click to expand...
Click to collapse
USB? That did it! Tanx
Hi experts,
I have HyperDroid CM7 v. 3.0.1 running on my HD2. For various reasons, I want to move to NexusHD2 v. 3.1a. Both NAND ROMs. I followed the instructions on the first post of this ROM, but while installing CWM Recovery with 135MB, I get the following error:
USB init failed
Info:.\RSPL\RSPL.cpp (736)
I have searched this forum and tried the solutions mentioned by various posters ... but, nothing works. Almost all posts on this subject are for error code 723.
Any tips on resolution ?
btw, this is the first time I am attempting to re-flash a new ROM ... so, I am kinda a newbie
Thanx.
cheers,
- manish
I am getting desperate .... anyone who knows the reason for the error code: USB init failed ... 736 ?
cheers,
- manish
Let me guess... running Windows 7?
Most common way to solve this is a. Run DFT Flasher as administrator (right click > Run as Administrator or b. Run DFT Flasher in XP compatibility mode.
Let me know it works out for you.
Sincerely,
Mac
Macelangelo77 said:
Let me guess... running Windows 7?
Most common way to solve this is a. Run DFT Flasher as administrator (right click > Run as Administrator or b. Run DFT Flasher in XP compatibility mode.
Let me know it works out for you.
Sincerely,
Mac
Click to expand...
Click to collapse
Hi Mac,
I am running Vista.
I have run DAF.exe as adminstrator and ran it in XP compatibility mode. Changed USB ports. Tried all sorts of combinations for connecting the USB cable from HD2 to computer. Still the same error message.
cheers,
- manish
manishmatu said:
Hi Mac,
I am running Vista.
I have run DAF.exe as adminstrator and ran it in XP compatibility mode. Changed USB ports. Tried all sorts of combinations for connecting the USB cable from HD2 to computer. Still the same error message.
cheers,
- manish
Click to expand...
Click to collapse
be sure you have windows mobile device center at pc.
mutil said:
be sure you have windows mobile device center at pc.
Click to expand...
Click to collapse
YESSSSSSSS!!! That was the problem. Installed Windows Mobile Device Center in laptop, and it works. Flashed NexusHD2 ROM.
Thanx, Mutil
cheers,
- manish
manishmatu said:
YESSSSSSSS!!! That was the problem. Installed Windows Mobile Device Center in laptop, and it works. Flashed NexusHD2 ROM.
Thanx, Mutil
cheers,
- manish
Click to expand...
Click to collapse
enjoy it
mutil said:
be sure you have windows mobile device center at pc.
Click to expand...
Click to collapse
man you saved my life and time, THANK YOU SO MUCH!!!!! I had exactly the same problem
USB init failed Info: .\RSPL\RSPL.cpp (736)
please help me i am getting error USB init failed Info: .\RSPL\RSPL.cpp (736)..
i hav window device center at the moment.
thanks sameer
I can't install Windows 10 Technical Preview on my Samsung RV509 laptop (Core i5 and 6Gigs of RAM). I tried doing a clean install, and once I boot from the flash stick It gets stuck on the Windows logo and the loading dots doesn't appear, so I tried to do an upgrade from Windows 7 and once it restarts it gets stuck on the windows logo and doesn't load after that (I tried both 32 and 64bit versions) then i get the error 0xC1900101-0x20017. So I tried to install it inside a virtual machine and i tried another machine,and it did install just fine. I tried everything I can from trying to launch the setup from the command prompt but still once it restarts it gets stuck on the windows logo. I'm not sure what do I need to do to get it to install and boot. I've tried with every single build since the insider program started till 9926.
I would really appreciate any help in this matter. Thank you.
I think you didn't really tried a clean install, since you wrote that you've tried to upgrade later. Clean install means you erase all traces of previous system installation. Also, it's good to delete all partitions. Maybe you're hard disk is MBR formatted and Windows 10 requires GPT (just a suggestion, I'm not sure about that).
Secondly, are you trying an UEFI install? I've had Win10 for a couple of months now but I remember having problems with starting UEFI installation from USB stick. To do this, you have to change partition layout on usb stick to GPT, then make new primary partition, format it to FAT32 and copy all files from install iso to usb stick. Then you can start your install in UEFI mode and I think this will help you. Just remember to delete all partitions and let Windows create new partition layout for you, this way it will create EFI partition.
If the installer says it can't create partitions in UEFI mode, you will have to change partition layout to GPT by yourselft. You can put your hdd in a PC and use a Windows based tool (search google) or maybe some Linux LiveCD will let you do that without removing your hdd.
All I did was just use demon tools and install over my w7. It installed as Uefi. Don't like it and w10 gave me an option on restart to roll back my system. I did and went back to w7.
You shouldn't use Daemon Tools to install Windows from an ISO. If Windows needs to reference a file inside the Install.wim folder on the disc for any reason, that copy will fail as the disc it's using is not a physical disc, but a virtual one that the new installation has no knowledge of. The best way to install Windows from an ISO is to copy the ISO to a flash drive or to the local hard disk and run setup that way, or use Rufus to create a bootable USB media for installing. That could be related to your error codes.
Thank you sanshinron for your reply. I always do a clean install for windows, the only reason that i tried to upgrade is that the setup didn't even load when booting from a USB stick (stuck on the windows logo). The USB stick was created using Microsoft's "Windows 7 USB DVD Download Tool". The same stick loads fine on other PCs. I will try to do what you suggested with the USB stick and give it another try.
sanshinron said:
I think you didn't really tried a clean install, since you wrote that you've tried to upgrade later. Clean install means you erase all traces of previous system installation. Also, it's good to delete all partitions. Maybe you're hard disk is MBR formatted and Windows 10 requires GPT (just a suggestion, I'm not sure about that).
Secondly, are you trying an UEFI install? I've had Win10 for a couple of months now but I remember having problems with starting UEFI installation from USB stick. To do this, you have to change partition layout on usb stick to GPT, then make new primary partition, format it to FAT32 and copy all files from install iso to usb stick. Then you can start your install in UEFI mode and I think this will help you. Just remember to delete all partitions and let Windows create new partition layout for you, this way it will create EFI partition.
If the installer says it can't create partitions in UEFI mode, you will have to change partition layout to GPT by yourselft. You can put your hdd in a PC and use a Windows based tool (search google) or maybe some Linux LiveCD will let you do that without removing your hdd.
Click to expand...
Click to collapse
try https://rufus.akeo.ie/ for the usb install
onebyside said:
try https://rufus.akeo.ie/ for the usb install
Click to expand...
Click to collapse
I tried both Rufus and ISO2Disk to make the USB stick GPT, but still i'm having the same issue with the setup not loading.
toulan said:
I tried both Rufus and ISO2Disk to make the USB stick GPT, but still i'm having the same issue with the setup not loading.
Click to expand...
Click to collapse
I installed UEFI without a problem, is there a reason your set on GPT?
I tried everything with the USB drive and it just installs fine on other pcs. I guess this could be because of hardware not supported yet by Microsoft in the current windows 10 builds. I found many people having the same issue. I just hoped there could be a fix to get the installer to start
I encountered same boot-hang problem when clean installing Win 8.1, and Win 10 shouldn't be different. My solutions:
Post-install boot-hang: The hang at logo boot happens when I don't format the install-to partitition with Win 8.1 installer (I normally partition/format using another tool, to skip the redundant WinRE partition that Win creates). Formatting with the installer allows the boot to complete (you can still keep the original partitioning).
Pre-install boot-hang: Some PCs are idiosyncratic with USB boot; likewise, some USB sticks are "different" from others. I found that using DiskPart to partition & format the USB stick (like a HDD) works when Rufus & straight formatting wouldn't. This, admittedly from a small sample set of one particular problematic combo. Simpler is just try to use different USB sticks.
toulan said:
then i get the error 0xC1900101-0x20017
Click to expand...
Click to collapse
This error indicates an update issue.
Try this:
- Ingersoll mini tool partition wizard
- check your disk type
If it's GPT,
- download minitool portable ISO and burn on USB with UUI.
- boot to the application and convert GPT to MBR
- Format the C: partition or wherever the previous windows was installed
- then overwrite it with win10
If it's UEFI change it from the bios. Turn off secure boot and everything.
Try and let me know.
Is there Windows 10 for Nokia Lumia 625?
Tiash420 said:
This error indicates an update issue.
Try this:
- Ingersoll mini tool partition wizard
- check your disk type
If it's GPT,
- download minitool portable ISO and burn on USB with UUI.
- boot to the application and convert GPT to MBR
- Format the C: partition or wherever the previous windows was installed
- then overwrite it with win10
If it's UEFI change it from the bios. Turn off secure boot and everything.
Try and let me know.
Click to expand...
Click to collapse
After using the minitool partition wizard i found out that it was already MBR.
feherneoh said:
Does that pc have Win8.1 installed with UEFI?
If so, connect installer drive, go to shutdown menu, hold shift, press restart
Then select Use device => UEFI USB
Click to expand...
Click to collapse
Tried it, but still the same issue.
Then turn off safe boot and try format the whole disk and start Windows installation from scratch?
Only if you want Windows 10 badly and are ready to sacrifice your data.
Caution: This 'might' work. No guarantees.
Tiash420 said:
Then turn off safe boot and try format the whole disk and start Windows installation from scratch?
Only if you want Windows 10 badly and are ready to sacrifice your data.
Caution: This 'might' work. No guarantees.
Click to expand...
Click to collapse
Tried it, but it didn't work. I think this could be an issue with a hardware that is not supported yet by the preview. I guess i'll have to wait for that to change in next builds.
toulan said:
Tried it, but it didn't work. I think this could be an issue with a hardware that is not supported yet by the preview. I guess i'll have to wait for that to change in next builds.
Click to expand...
Click to collapse
That might be it cause it's a preview and they sure are known for this kinda issue
Tried build 10041 and still same issue.
toulan said:
Tried build 10041 and still same issue.
Click to expand...
Click to collapse
My Laptop is SAMSUNG RV509 but with intel core i3 1st Generation and 2 GB of RAM inside
And I have the same problem with you when trying to install Windows 10 Technical Preview even with it's latest version just like you, get stuck at begin of instalation process, Windows logo appear without any waiting animation (circle of dots), and nothing happen after that.
Just like you, I'm trying install it so many time and so many way such as update latest version of BIOS, but nothing change.
So, if you have a solution for our laptop, please take your time to guide me.
"Sorry if any inconvenience come to your attention with my English writing skill"
shinstar123 said:
My Laptop is SAMSUNG RV509 but with intel core i3 1st Generation and 2 GB of RAM inside
And I have the same problem with you when trying to install Windows 10 Technical Preview even with it's latest version just like you, get stuck at begin of instalation process, Windows logo appear without any waiting animation (circle of dots), and nothing happen after that.
Just like you, I'm trying install it so many time and so many way such as update latest version of BIOS, but nothing change.
So, if you have a solution for our laptop, please take your time to guide me.
"Sorry if any inconvenience come to your attention with my English writing skill"
Click to expand...
Click to collapse
Of course, once i find a solution i will post it here, so far no luck.