Related
I recently crashed my vista hard drive and decided to give windows 7 a try, its working wonders right now. The only problem is that I'm trying to put Nandroid back up on my computer again. I am at the step of trying to get the fastboot loader. It worked on Vista, but now it is saying that the "Driver is not intended for this platform." Is that due to windows 7? Is there a work around for this? Any help would be amazing, thanks.
I used Fastboot on Win7 7100 build yesterday, and it worked fine. Did you set everything up according to this post:
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2
This is all that I did, and everything worked flawlessly. Good luck.
hmm..yeah, i did do everything according to the tutorial exactly, do you have email, aim, gmail, etc? could you help me?
use the newest driver in this SDK..
http://developer.android.com/sdk/1.5_r1/index.html
If you dont see the ADB Device or whatever its called in the device manager you need to delete a generic volume and scan for hardware changes.... HTC talks about it here. I had to do it also...
http://www.htc.com/www/support/android/adp.html
Troubleshooting
fastboot.exe (on Windows) doesn't detect the ADP device properly
In some cases, Windows detects the ADP1 bootloader as a USB mass storage device, preventing fastboot.exe from accessing it. To resolve the issue, you can dissociate the USB Mass Storage driver from your ADP1 on your Windows machine and install the proper driver instead, as described in the steps below:
1. Boot the device into fastboot mode, as described above, and connect the device to your machine over USB.
2. Navigate to Start > Control Panel > System > Hardware > Device Manager > Universal Serial Bus Controllers. Observe that the ADP device is listed as a USB Mass Storage Device.
3. Right-click USB Mass Storage Device and select Uninstall. Windows then prompts you with a "New Hardware Found Wizard" message. If Windows doesn't prompt you, you can manually re-detect devices by selecting Action > Scan for hardware changes.
4. Install the USB driver included in the Android SDK, as described in Setting up a Device for Development on the Android Developers site.
thanks southsko, i'll try this and let you guys know how it works.
I tried your method Southsko, but it didnt work for me. I think the problem is that windows 7 refuses to install the driver for the htc dream, because its not "intended for this platform" is there a way to force it to install the driver? or manually install the driver?
When I wrote that tutorial it was using Windows 7 beta. I have also used it since I upgraded to Win7 RC, so I know that it can work. Did you make sure to install driver when the phone is connected and booted to the boot loader screen? Windows sees the phone as a different device when connected normally and at the boot loader. When I installed the driver It popped up with the message that it was for a different version, but it gave me an option to install it anyway. Are you logged in to Windows with admin rights?
i had the same problem earlier tonight, i figured since i was running win7 i might as well try using the virtual xp out. I started the VM up and the attached the phone using the drop downs and it worked flawlessly.
yup .. it's working fine for me too.. if you are using 64 bit version ... u need to use the 64 bit usb driver too... u can get it here
http://forum.xda-developers.com/showthread.php?t=446274
Also you may have trouble installing it in Windows 7 unless you turn off driver signing at boot menu. Hit F8 and select no driver signing and you should be able to install it no problem... u will also have to disable driver signing each time you plan on using adb/fastbboot
foxlin said:
I tried your method Southsko, but it didnt work for me. I think the problem is that windows 7 refuses to install the driver for the htc dream, because its not "intended for this platform" is there a way to force it to install the driver? or manually install the driver?
Click to expand...
Click to collapse
When choosing the driver software, make sure you select the "x86" folder instead of usb_driver or any parent folder. This is because the wizard search sub directories in alphabetical order, and will stop when it find the driver for x86-64(amd64). Then it will simply tell you "not intended for this platform" without looking in the x86 folder.
Also, you do not have to disable driver signing for this to work.
trmacdonal said:
When I wrote that tutorial it was using Windows 7 beta. I have also used it since I upgraded to Win7 RC, so I know that it can work. Did you make sure to install driver when the phone is connected and booted to the boot loader screen? Windows sees the phone as a different device when connected normally and at the boot loader. When I installed the driver It popped up with the message that it was for a different version, but it gave me an option to install it anyway. Are you logged in to Windows with admin rights?
Click to expand...
Click to collapse
I am in bootloader mode, and I am an admin. It didn't give me the option to install it anyways. That is interesting. I am currently still using the windows 7 beta. I have tried manually selecting the specific driver files. It is still not working, any other ideas?
I finally got it! thanks everyone. The solution was instead of having it search through the files, there is actually an option below it to pick the driver from a list, the list wasnt the right one originally, then i manually changed the directory and it worked. Thanks for the help everyone!
billc.cn said:
When choosing the driver software, make sure you select the "x86" folder instead of usb_driver or any parent folder. This is because the wizard search sub directories in alphabetical order, and will stop when it find the driver for x86-64(amd64). Then it will simply tell you "not intended for this platform" without looking in the x86 folder.
Also, you do not have to disable driver signing for this to work.
Click to expand...
Click to collapse
How come when I installed this on Beta I got the message that I could not install a non-digitally signed driver? I was not able to install it myself until I disabled it at boot... maybe the 32 bit version is signed.
For those of y'all that aren't comfortable using ADB to transfer files (backup and restore your /system/sd Ext2 or Ext3 partitions) while using Windows (including x64 version), there is a very simple alternative to ADB.
Go here and read about it:
Ext2 Installable File System For Windows (includes Ext3 as well)
http://www.fs-driver.org/
Simply follow the instructions and install.
Reboot your computer
Once you reboot, you'll be able to access the Linux partitions just like they are a C:\ drive (they'll have a different partition letter, of course)
This works for XP, Vista and Windows 7 ... x64 too.
You'll then be able to transfer files back and forth very easily.
Great for backups!
NOTE: this will NOT allow you to partition your card. This just allows read/write access to your Ext2/Ext3 partitions.
Here's the download page as well:
http://www.fs-driver.org/download.html
I tried to install on Windows 7 an no go for me it says that it doesn't run on the platform
Naimand said:
I tried to install on Windows 7 an no go for me it says that it doesn't run on the platform
Click to expand...
Click to collapse
Go to where you downloaded the file.
Right click on it.
Choose properties.
Choose Compatibility.
Check "Run this program in compatibility mode"
Choose a Vista version compatible with whatever you have (ie. x64)
Click OK.
Then run install.
Just installed on x64 Windows 7, you do need to do compatiability mode to install.
ran instal but after i restarted nothing is showing up when i click on computer, just normal drives
It's been a while since I installed it, but I remember it took some trial and error to get it in Vista x64. Play with the different options and try reinstalling it.
Another thing you might try is Assign A Drive Letter in Paragon Partition Manager.
I know it works, I just don't remember what combination of things it took to get it working.
oh god i just uninstalled my Paragon Partition Manager last night! and i dont have the files no more. i guess im just gonna uninstall this tool. thanks anyways. running xp.
ext2fsd seems to be ahead of ext2ifs in features; it also works on windows 7...
I am trying to run the Topaz ROM file by transferring it from My PC which has windows 7 to my HTC Diamond 2 phone but I get a communication error. Any idea what I am doing wrong?
syrian
must have windows active sync program
Assuming you are trying to install a custom ROM and you have successfully installed HSPL, rename the .nbh file to TOPAIMG.nbh and copy to the root of your storage card and enter bootloader mode. It will flash that way as well.
If it is th estock ROM, you can also enter bootloader while connected to your PC and bypass Active Sync and then run the .exe.
Yep, Sync the phone with the windows, works with windows 7 (must download a seperate software form microsoft site), install HSPL, and than use customRUU, or the provided installer with the Rom to install it.
I think you should visit this thread. You'll find a lot of useful stuff there, including all you should know about flashing ROM, HardSPL, etc.
Enjoy!
Ok ,once you have decided to install Android operating system(AOS) on your pc u'll need to..... oh wait! u must be wondering why did i create this thread since an android emulator already exists. This is why
1) This is not an emulator but a full fledged OS that can be installed along windows/linux
2) it's optimized for x86(32 bit Intel and AMD) processors so is a lot less laggy than the emu
3) it supports wifi, camera and u can install apps which you can't do on the emulator
Caution-
This build is primarily for laptops/netbooks and may not fully work on your desktop( there's no harm in trying though)
Depending on your version and Hardware, not everything may work properly
I'm not responsible for anything you do! (though i seriously doubt that it can do any harm but always exercise caution)
Once you are satisfied, lets begin
Requirements-
A USB pendrive with at least 256 mb free scpace
Internet connection
Common Sense
Downloading the tools-
1)First go to this site- http://www.android-x86.org/download and download the required image(choose which version and the model of ur laptop)
2) Visit this link - http://unetbootin.sourceforge.net/ and download Unetbootin for your OS(the one you are currently running)
Setting up the bootable image
1) Plug in your pendrive and run Unetbootin.
2) Select the "diskimage" radio button and load the ISO file
3) Set type to "USB Drive" and select ur pendrive from the drop down menu
4) Click OK and your pendrive is ready to be booted from
Booting up AOS
1) turn off your computer and plug in your pendrive
2) you need to change the boot sequence in the PC's BIOS. to do this keep pressing 'Delete" button or F12(depending on your motherboard, generally a line of text indicates the button to be pressed) on the boot/Splash screen and select external/usb as your first boot device
3) Once done, the AOS installation menu should come up, select the first option to try it without installing anything to your Hard disk.
4)If you want to install it to your Hard disk you might havta repartition ur HD to avoid windows being overwritten(i recommend not doing so but if you want to proceed, use the free software EASUS Partition Manager)
5) Bingo!! You should be running AOS on your PC now
Thank You
Thanks for starting this wonderful thread. I installed android on my netbook beside windows xp and it works great. it lets me choose which operating system i want to work with. i downloaded android-x86-4.2-20130228.iso from that website cuz i didn't know to use which one. i also created an ntfs partition for installing android. it perefectly recognizes my wireless and camera now. nothing is better than this. i'm happy with my netbook now.
thanks man....its working and its awesome!!!
Sent from my Xperia E dual using XDA Premium 4 mobile app
Sd Card Dual boot?
As you can see, Im new here... Does this require a partition to install, or can you boot straight form usb? My other question is can you do this the same from an sd card? Thanks in advance... Sorry if its a dumb question.
Jellypig1278 said:
As you can see, Im new here... Does this require a partition to install, or can you boot straight form usb? My other question is can you do this the same from an sd card? Thanks in advance... Sorry if its a dumb question.
Click to expand...
Click to collapse
Mmmmm.... i'm going to try it now. i have created extra partition using MiniTool Partition Wizard Pro Edition 7.5.0.1 and know i"m going to use sd card in card reader to create bootable pendrive.
wait......................................................
Ramesh006 said:
Mmmmm.... i'm going to try it now. i have created extra partition using MiniTool Partition Wizard Pro Edition 7.5.0.1 and know i"m going to use sd card in card reader to create bootable pendrive.
wait......................................................
Click to expand...
Click to collapse
i have created partition using MiniTool Partition Wizard Pro Edition but after that my pc was lost boot. it set the c drive inactive. i used windows cd to start again. unetbootin-windows-608 didn't work for me. i used Win32DiskImager-0.9.5 which has option to choose operating system android. after that it worked but i have got one more problem. i have installed the android into newly created partition and installation was completed successfully but again i lost boot. again i used windows cd to solve boot issue to make c drive active. after that i have directly run the android without installing. it worked and run very smoothly but it was not showing my hard disk even giving root access to file manager. so finally i have decided to go virtual box. now downloading virtual box but i want to boot android from menu because i have windows,linux in boot menu now i want android also.
FYI i was using desktop and i have photon plus wireless modem. which is detecting on ppp widget but not connecting because of operating system. it was android 4.4.2 cynogenmod(rooted) and cynogenmod wont detect the internal sd and ppp widget can establish a connection without having it files in internal storage. so my advice is choose your android carefully and you can even establish internet connection from your mobile using ppp widget. there is an way to make your internal sd get detected by using terminal emulator.
my pc details 1.6ghz amd processor,1gb ram having windows xp and puppy linux
virutual box didn't helped me. it was showing error. again i tried to boot android x86 using Universal-USB-Installer-1.9.5.5 and format the partition into fat 32 and installed grub for windows. this time worked booted into android
to install whatsapp use older version of whatsapp open it and it will ask u for downloading new version then download new version replace the app and your whatsapp will work. we chat and line are not working.
for games search for games for android x86
angry birds star wars,stella are working. ppsspp gold emulator is working. mx player and vlc are not working
Okay, so some of us were in this boat. You have to reinstall Windows on your nice little Surface Pro tablet. But sadly you don't have a recovery partition or a flash drive! So what are you supposed to do?
Well, first you ask Microsoft support. That does not go well: they tell you to send them your Surface. But that's not really a good option - to lose your tablet for two weeks over a software problem? That's just not fair!
So, next, you try googling for help. But all you ever find are similar unanswered pleas for help, which usually end up being either unanswered or closed by moderators.
But fear not, as you CAN solve this, and you don't even need to do crazy things like making your own recovery image, or downloading one from weird Chinese sites.
----
HOW TO REINSTALL WINDOWS 8.1 ON YOUR SURFACE PRO WITHOUT A RECOVERY PARTITION/USB
Step 1.
Obtain a Windows 8.1 ISO. I can't tell you where to obtain one, but it is not a hard task.
The flavor Surface Pro uses is Windows 8.1 Pro x64. I used the EN-US version, as I have an American Surface, so I can't verify how other languages will work.
Step 2.
Burn that ISO to a USB drive. I suggest using Rufus for that: http://rufus.akeo.ie/
Step 3.
Boot your Surface from the USB drive.
To do that, hold the volume down button when turning on your Surface
Step 4.
Install Windows 8.1.
Step 4.5.
It will ask you for an install key, and might not accept your real Surface key. The reason for that is that the installer for Windows 8.1 does not accept Windows 8.0 keys (and your Surface might have one of those).
To proceed with installation, you will need this install key:
XHQ8N-C3MCJ-RQXB6-WCHYG-C9WKB
Click to expand...
Click to collapse
This key is for installation only. IT DOES NOT ACTIVATE WINDOWS.
Step 5.
After installing the OS, you'll notice that it's not behaving quite right, for example, there are 4 rows of tiles on the start screen instead of three.
Go to Windows Update, and install everything.
Step 5.5.
If you installed with the install key, use this utility to get the original Windows key: http://forums.mydigitallife.info/threads/30363-Windows-8-Product-Key-Viewer
Choose the "MSDM" option, copy that key, and activate Windows with it.
Step 6.
Enjoy your happily recovered Surface.
----
So there. That was a little guide on how to recover a Surface Pro without a recovery drive. I was in this situation myself recently, and Microsoft offered me to send my Surface to them - which would've cost me $200, as I live in a different country from the one my Surface came from, and also would've meant living without my tablet for a month or even longer. So I just fixed it all myself.
A lot of people seem to be posting in that other recovery thread, so I'm just gonna make this visible again.
Only one question, do I need a keyboard or mouse for that?
Cause I've got only wireless mouse and original type cover, which does not work for some reason, and that's why I want reinstall windows.
I think it should pop up the on-screen keyboard if you use touch.
Anyone else did this process and got the Surface Pro 2 back to "out of the box" state?
touch screen
has anyone of you got the issue with the touch controller? and after the windows reinstall did it come back?
regards
Worked perfect
Worked perfect on a MS Surface Pro 1, with windows 8.1 Pro install USB, no keyboard or mouse needed.
Thank you! :good:
Thanks a heap for this guide, thought my Surface was done for.
For those unable to boot normally into Windows, holding VolKeyDown + Power while the unit is off will force the unit to boot from removable storage (doesn't have to be a USB Stick, you can plug in any kind of bootable media, including a USB DVD-ROM).
Have fun!
Can this works for Surface Pro 2
westjgames said:
Thanks a heap for this guide, thought my Surface was done for.
For those unable to boot normally into Windows, holding VolKeyDown + Power while the unit is off will force the unit to boot from removable storage (doesn't have to be a USB Stick, you can plug in any kind of bootable media, including a USB DVD-ROM).
Have fun!
Click to expand...
Click to collapse
Hi,
Can this method work for surface pro 2?
syahchrono said:
Hi,
Can this method work for surface pro 2?
Click to expand...
Click to collapse
I'm gonna try this now on my Surface Pro 2 because I got one with only scandinavian languages and I'm from Germany ^^ Will report back!
# UPDATE #
Worked perfectly fine
question
I just installed the latest Firmware / Drivers MS has pushed through Windows Update,
and i would like to refresh my Surface Pro 2 to get a clean install.
- First thing i did was create a bootable usb drive using Microsofts new 'Create Installation Media Tool'
. I selected 'Windows 8.1 Pro x64' in my native language which is Dutch.
The tool created a bootable USB stick, which i haven't tried yet.. before i continue i have some questions;
....
1. I copied my recovery image to a USB stick and deleted the recovery partition.
- If i reinstall Windows can i still use the recovery usb in case something goes wrong during the installation, or is it linked to your current installation?
2. Would Windows automatically recognize the serial number, which i believe is stored in the BIOS / UEFI, and activate Windows? I've written down the serial using the tool mentioned in the OP to be on the safe side.
3. Like i mentioned before, i installed the lastest driver / firmware package, will Windows automatically install the latest drivers after installation or first install more basic drivers to get WiFi up and running and then install the latest drivers?
4. When you install new driver / firmware software will Windows automatically update the then older drivers in the recovery image?
I've read the previous posts saying that everything went smoothly, but i just want to make sure i'm not forgetting anything..
i have a Surface Pro 2 btw!
koffiemelk said:
I just installed the latest Firmware / Drivers MS has pushed through Windows Update,
and i would like to refresh my Surface Pro 2 to get a clean install.
- First thing i did was create a bootable usb drive using Microsofts new 'Create Installation Media Tool'
. I selected 'Windows 8.1 Pro x64' in my native language which is Dutch.
The tool created a bootable USB stick, which i haven't tried yet.. before i continue i have some questions;
....
1. I copied my recovery image to a USB stick and deleted the recovery partition.
- If i reinstall Windows can i still use the recovery usb in case something goes wrong during the installation, or is it linked to your current installation?
2. Would Windows automatically recognize the serial number, which i believe is stored in the BIOS / UEFI, and activate Windows? I've written down the serial using the tool mentioned in the OP to be on the safe side.
3. Like i mentioned before, i installed the lastest driver / firmware package, will Windows automatically install the latest drivers after installation or first install more basic drivers to get WiFi up and running and then install the latest drivers?
4. When you install new driver / firmware software will Windows automatically update the then older drivers in the recovery image?
I've read the previous posts saying that everything went smoothly, but i just want to make sure i'm not forgetting anything..
i have a Surface Pro 2 btw!
Click to expand...
Click to collapse
1:I have no idea
2: Yes it will, I have a surface pro 1 and it was activated automatically, so i didnt had to do anything with my serial. (on a new windows 8.1 install)
3: Yes it will, but you can always install them manually (doesn't really matter unless there are issues with drivers).
4: Dont know (dont think so). (I havent ever uses a recovery installation ever, i always install everything manually back on .
Hi together,
I did the steps and everything went fine. But I had to disable secure boot at first.
Now, after the isntallation of Windows 8.1, I activated it again and reinstalled the default keys. Is this the way it is meant?
Or do I need to leave it disabled?
Thank you very much!
Best regards,
thrain2
So I have a question.
I removed my recovery partition to regain the space.
Does your method reformat the drive and repartition everything? Will it reinstall the recovery partition?
I remember all former windows os installations I've done allowed me to format the drive and clear the partitions and then either create new ones myself or use the blank disk. Win7 would (on a blank disk) create it's recovery partition.
So I went ahead and did it.
To anyone looking to do this, use the official media creation tool. It's free from Microsoft and extremely simple.
I didn't have to disable secure boot or anything, just hold down the volume and power button with the USB plugged in.
The installer let me delete all my existing partitions and it automatically created only the ones needed.
It never asked for a key and was activated correctly when I booted into widows.
I found the installer created 3 total partitions on it's own.
1st a 300mb empty partition which I believe is supposed to be for windows RE and required by bit locker.
2nd a 100mb partition containing an EFI folder.
Note: these two aren't supposed to be accessible, I did special mounting to check them out.
3rd the rest of my disk space was created for my system partition
I'm mostly happy with this.
The only issue I've had so far is I can't turn bit locker on, even though there is a 300mb partition, it's empty and bit locker complains about the widows recovery environment not being on the system dive.
iXNyNe said:
So I went ahead and did it.
To anyone looking to do this, use the official media creation tool. It's free from Microsoft and extremely simple.
I didn't have to disable secure boot or anything, just hold down the volume and power button with the USB plugged in.
The installer let me delete all my existing partitions and it automatically created only the ones needed.
It never asked for a key and was activated correctly when I booted into widows.
I found the installer created 3 total partitions on it's own.
1st a 300mb empty partition which I believe is supposed to be for windows RE and required by bit locker.
2nd a 100mb partition containing an EFI folder.
Note: these two aren't supposed to be accessible, I did special mounting to check them out.
3rd the rest of my disk space was created for my system partition
I'm mostly happy with this.
The only issue I've had so far is I can't turn bit locker on, even though there is a 300mb partition, it's empty and bit locker complains about the widows recovery environment not being on the system dive.
Click to expand...
Click to collapse
Thanks for sharing this.good
Anyone tested this yet with a surface 3 or surface 3 pro?
Tried this with my Surface 3, which is stuck currently on Win10 10074, and the install key didn't work.
It works
I used the freeware ISO2Disc to burn a Windows 10 ISO file to my USB drive and I can then reinstall successfully. Remember to choose GPT partition style as Surface Pro can boot in UEFI mode only.
iXNyNe said:
The only issue I've had so far is I can't turn bit locker on, even though there is a 300mb partition, it's empty and bit locker complains about the widows recovery environment not being on the system dive.
Click to expand...
Click to collapse
I did basically the same, reinstall a clean Windows on my Surface pro 3, but can not turn on bit locker, too. Have you figured out, how to solve this issue?