Database Users

[GUIDE] Getting drivers to work on W7 x64

There has been a few times I've ran into issues with drivers not being compatible with Windows 7 x64 so I am going to show you a way to get them working by running a virtual machine with windows xp x32 installed.
#1. Here you can download a free Virtual machine.
http://hotfile.com/dl/45019228/154c711/VMware-player-3.1.0-261024.exe.html
here is the same download link from their website, which will require registration and verification.
https://www.vmware.com/tryvmware/?p=player&cmp=EMC-PlayerEvalActivation&li=license
#2. You will need to either have an ISO of Windows XP or an installation disk for this to work.
#3. Install VMWare Player and follow the instructions, it is very simple.
#4. Once your virtual machine is open, it should install VMWare tools. This will give you access to dragging and dropping, copying and pasting, and various other functions from your host computer to the virtual. You now should copy all necessary files and apllications you will need to complete whatever modification it is you are going to do.
#5. Install HTC Sync on the virtual machine. Link: http://member.america.htc.com/download/Driver/HTC EVO (Sprint)/HTC_Sync_2.0.40.exe
#6. You can easily switch your device from syncing to your host computer to your virtual by right clicking the icon that shows your phone. These icons are located on the bottom right corner of the virtual machine. Picture below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
One of the issues I have encountered so far is when trying to run CDMA Workshop on the virtual machine it will not open. It will give you the error "Sorry, this application cannot run under a virtual machine".
I have found a workaround for this.
Go to the folder on your host computer:
C:\Users\YOURUSERNAME\Documents\Virtual Machines\Windows XP Professional
Open your Windows XP Professional.vmx in notepad. This is the VMware virtual machine configuration file. Go to the bottom of the file on a new line each add these lines of code
Code:
monitor_control.restrict_backdoor = "TRUE"
disable_acceleration = "TRUE"
This will stop CDMA Workshop from thinking it's being run on a virtual machine and should work for other programs as well.

May I ask you what exactly you are having trouble with with W7x64? I was able to get ADB up and running, root my phone, and check my MSL with CDMA workshop within W7x64. Just had to find the right drivers online, but it didn't take too long.

Same here, Win7x64, no problems

DSwarP said:
May I ask you what exactly you are having trouble with with W7x64? I was able to get ADB up and running, root my phone, and check my MSL with CDMA workshop within W7x64. Just had to find the right drivers online, but it didn't take too long.
Click to expand...
Click to collapse
Albaholic said:
Same here, Win7x64, no problems
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=708419&page=6
it's a response from this thread. i, along with several other 64b win7 users cannot get it to work. go to the device mgr and click on the suspect, update driver and point to where the dl'ed drivers are and it does not recognize the drivers.
it seems to work fine on my the xp here at work. which drivers are you both using? i know it's not that technical. i can't develop for hack it any electronics but i can follow instructions and have hacked the psp, unlocked the tp2 and this phone among many, but i cannot understand how some were saying they've been successful and i'm in the same boat with many others who can't seem to get it to work on a 64b win7.

skoobz said:
it's a response from this thread. i, along with several other 64b win7 users cannot get it to work. go to the device mgr and click on the suspect, update driver and point to where the dl'ed drivers are and it does not recognize the drivers.
Click to expand...
Click to collapse
I'll pull my own quote from that thread:
"The 64 bit drivers will not be recognized or installed by the Windows 7 automatically. You must force the installation of the drivers by choosing the "Browse" option then "Let Me Pick" option then the "Have Disk" option."

skoobz said:
http://forum.xda-developers.com/showthread.php?t=708419&page=6
it's a response from this thread. i, along with several other 64b win7 users cannot get it to work. go to the device mgr and click on the suspect, update driver and point to where the dl'ed drivers are and it does not recognize the drivers.
it seems to work fine on my the xp here at work. which drivers are you both using? i know it's not that technical. i can't develop for hack it any electronics but i can follow instructions and have hacked the psp, unlocked the tp2 and this phone among many, but i cannot understand how some were saying they've been successful and i'm in the same boat with many others who can't seem to get it to work on a 64b win7.
Click to expand...
Click to collapse
Weird. I run Win 7 Pro x64 at home, and got the copy of HTC Sync that was on my Evo's SD card to install on it with no issues. Run the version of adb-windows from toast's evo recovery zip file from it too.

crackerstyle said:
Weird. I run Win 7 Pro x64 at home, and got the copy of HTC Sync that was on my Evo's SD card to install on it with no issues. Run the version of adb-windows from toast's evo recovery zip file from it too.
Click to expand...
Click to collapse
Its not the adb drivers that are a problem. Its the diag drivers that won't install automatically.

Berner said:
Its not the adb drivers that are a problem. Its the diag drivers that won't install automatically.
Click to expand...
Click to collapse
My bad, I saw him talking about installing HTC Sync on the virtual XP.

For HTC Diag Drivers see my article in my sig. I have changed the Sprint banner with QPST with no problems using my diag drivers on Win7 x64. I also included 32 bit drivers.
I also outlined a guide on how to manually install them.

thanks for the guide!

Thanks, worked perfect. I was wondering why CDMA workshop wouldn't work right with VMware a few days ago.

Works fine for me on windows7 x64 as well... You just have to point windows to the exact .inf driver file and force it to install. No need to install an entire virtual machine..
Sent from my PC36100 using Tapatalk

The evo always worked fine for me on win7 x64 but its terribly inconsistent with recognizing android phones and installing drivers (moment and vogue were a nightmare) even pointing to them directly. For whatever reason solutions for some definitely dont work for everyone

For some reason Win7 64 is picky about how the drivers get installed. When I followed this guide everything worked fine.
http://forum.xda-developers.com/showthread.php?t=697487

After following the instructions and running CDMA WS 3.6 in VMWare (WinXP Pro) I'm being told my current license key for CDMA WS is locked to a different machine or machine configuration, which I guess isn't terribly surprising.
I am not going to buy another license... so is there any way to set up the VMWare host machine to make CDMA WS think it's running on the same machine to which it's been locked (which is my host machine)?
The only other thing that would solve my problem would be 64-bit diag drivers for a Treo Pro and a Palm Centro.

KJThaDon said:
There has been a few times I've ran into issues with drivers not being compatible with Windows 7 x64 so I am going to show you a way to get them working by running a virtual machine with windows xp x32 installed.
#1. Here you can download a free Virtual machine.
http://hotfile.com/dl/45019228/154c711/VMware-player-3.1.0-261024.exe.html
here is the same download link from their website, which will require registration and verification.
https://www.vmware.com/tryvmware/?p=player&cmp=EMC-PlayerEvalActivation&li=license
#2. You will need to either have an ISO of Windows XP or an installation disk for this to work.
#3. Install VMWare Player and follow the instructions, it is very simple.
#4. Once your virtual machine is open, it should install VMWare tools. This will give you access to dragging and dropping, copying and pasting, and various other functions from your host computer to the virtual. You now should copy all necessary files and apllications you will need to complete whatever modification it is you are going to do.
#5. Install HTC Sync on the virtual machine. Link: http://member.america.htc.com/download/Driver/HTC EVO (Sprint)/HTC_Sync_2.0.40.exe
#6. You can easily switch your device from syncing to your host computer to your virtual by right clicking the icon that shows your phone. These icons are located on the bottom right corner of the virtual machine. Picture below.
One of the issues I have encountered so far is when trying to run CDMA Workshop on the virtual machine it will not open. It will give you the error "Sorry, this application cannot run under a virtual machine".
I have found a workaround for this.
Go to the folder on your host computer:
C:\Users\YOURUSERNAME\Documents\Virtual Machines\Windows XP Professional
Open your Windows XP Professional.vmx in notepad. This is the VMware virtual machine configuration file. Go to the bottom of the file on a new line each add these lines of code
Code:
monitor_control.restrict_backdoor = "TRUE"
disable_acceleration = "TRUE"
This will stop CDMA Workshop from thinking it's being run on a virtual machine and should work for other programs as well.
Click to expand...
Click to collapse
Did everything you mentioned and after i add those two lines and the end of the file and try to open CDMA Workshop in the Windows XP on the virtual machine it keeps closing out just like before. I been trying to get this to work for a couple days. Anyone who can point me in the right directions is appreciated.

bump

Thank you!
Thank you for the knowledge, may you have many happy blessings in your future! :good:

[GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!

[GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting! v1.2
Hey XDAers. Getting ADB setup and working is an essential part to rooting your Android device and helps layout the foundations to better understanding the language and using it in this environment. While not going into extreme detail, this is just a quick guide or overview on the first part of rooting; Getting ADB setup and working.
** Make sure your Transformer is not currently connected to your PC yet. We will be installing device drivers first (Step 7) and modify a setting on your tablet first before connecting to your PC (Step 8).
Step 1 :
Download and install the Android SDK.
You can download the SDK from the Google Developer's website. I have linked for you the download page and a direct link to the installer (Note: the direct link may change in the future with future versions, I will try stay on top of this and change the link)
http://developer.android.com/sdk/index.html
http://dl.google.com/android/installer_r10-windows.exe
*New Version : http://dl.google.com/android/installer_r11-windows.exe
You may or may not be prompted to install the latest version of Java if you haven't done so already, install it, and you may or may not have to reboot your computer.
Step 2 :
Once the install is complete, navigate to the directory in which you installed the SDK and launch the SDK Manager executable. It may or may not ask you to download and install the Java JDK, do so if you haven't already.
*When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already*
Answer :
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead.
Thanks Crimton!
Click to expand...
Click to collapse
Step 3:
Once the SDK Manager is launched, it will look something similar to the window below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You will want to do something along the lines of update all or install all. This way it will download all the latest packages and you willhave the latest SDK tools installed.
Once that is complete, you can exit out of the SDK Manager.
Step 4:
Open up a command prompt window. You can do so by holding the WinKey+R, a run window will appear, type CMD, and hit enter.
Step 6:
Within the Command Prompt window, navigate to the Android SDK folder\platform tools folder (Command Prompt command : CD foldername\foldername\foldername\etc)
Step 7:
Now install the ASUS Sync software if you haven't loaded it previously. http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download. Just select your operating system, hit download, then install.
Why are we installing the ASUS Sync software you ask?
Well mainly because it has USB drivers that will help your PC operating system detect and display your ASUS Transformer. Without the drivers, ADB wouldn't be able to detect your device most likely!
*For other android devices, you will need similar software from that manufacture. HTC Sync for HTC devices as an example.
Click to expand...
Click to collapse
Step 8:
Enable USB Debugging on your android device / Transformer.
Go to Transformer Tablet, go to settings -> applications->Development, turn on USB Debugging.
Step 9:
Connect the USB cable from your android device / Transformer to the PC. It will begin to automatically install drivers, let it do so and complete. May ask to reboot machine.
Step 10:
Once that is done, go back to the command prompt. Run ‘ADB Devices’
You should see something like above, indicating it detected the transformer, if not, run the following ‘adb kill-server’, ‘adb start-server’, ‘adb devices’
Ok, if you are seeing something like the screenshot above then success, you have successfully gotten ADB up and working! Congratulations! That wasn't too hard now was it? You can now follow one of the root guides and follow the directions and you should be on your way to a fully rooted device. Cheers!
-------
Troubleshooting:
In the event you complete the steps above but your computer either will not recogonize the Transformer in Windows as a device, or ADB will not see it please try the following to see if this will fix it for you. You only need to try these if the above steps aren't working for you, but most people, they work fine.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html
-------
Notes:
-If you want another guide on something else, let me know, and I will see what I can do.
-Yes this has been posted a million times I know, but I thought this might help out those few people that don't feel like looking around. Plus, it has nice color illustrations. Who doesn't like picture books?
-------
Credits
Crimton for Java JDK workaround when not showing as installed
sourworm for new link to SDK installer

Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.

stuntdouble said:
Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.
Click to expand...
Click to collapse
Will do when I get home, thanks for the tip.

Ill add this to the FAQ

One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.

I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.

RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
Glad you got it resolved, I will edit the guide and make note about java installation.

Daughain said:
One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.
Click to expand...
Click to collapse
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740

neilkarunatilaka said:
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Click to expand...
Click to collapse
at a glance, even that thread makes it look like more trouble than it is. but good info

RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
How did you fix it? I've been struggling with this same issue for at least a month now.

n25philly said:
How did you fix it? I've been struggling with this same issue for at least a month now.
Click to expand...
Click to collapse
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk

Crimton said:
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
lol, simple solutions are good. Just wish it didn't take me a month to find that one out.

Very simple and easy to follow. Thanks OP.

I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?

randy_c said:
I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?
Click to expand...
Click to collapse
Sorry to hear that. Off the top of my head, I'm not sure what could be causing this. But here are a couple things you can try. And please let us know what happens next.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html

I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!

andrew53517 said:
I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!
Click to expand...
Click to collapse
1) First thing you can try is the famous 'adb kill-server' 'adb start-server' commands and see if that will get it going. Also 'adb usb' will restart the daemon listening on USB, so maybe that could make it usable. If not, make sure the ASUS Sync app is not running, and perhaps see if there are any running services/apps on your Transformer that could be causing the conflict. Download System Panel Lite from Market and tell it to end all apps, then try again (make sure USB Debugging is enabled)
If you tried all of that, and still no dice, make sure no USB Drives or Memory Cards are connected, then connect the Transformer (w/ USB Debugging), go to Device Manager, uninstall the USB drivers for the device if you can find it or it may show up as a USB Mass Storage device under USB Controllers, then disconnect the Transformer, reconnect the Transformer, it should reinstall the drivers for the Transformer since you already have ASUS Sync installed, then retry.
If again still no dice, try using the ASUS USB Windows Drivers and going to Device Manager and updating the drivers with those you downloaded (download the correct ones for your particular operating system, and then try again.
Now, if this still doesn't work, let me know, and I'll try think of something else. Maybe someone else has had this issue and come up with a workaround or solution, but I'm drawing a blank currently. I'll sleep on it and see if I can think of anything else
2) You don't have to type that up all the time. What you can do is navigate the platform tools folder (or whatever folder has the adb files), then if on Win 7, hold shift and right click on the folder (Platform Tools for example), and you will see an Open Command Prompt here. Hit that, and it will already be in that root folder. But in general, in a command prompt window, once you have navigate to the specified folder, you will be in that folder, so you will only need to type ADB 'command' if that makes sense.
[/LIST]

I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.

andrew53517 said:
I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.
Click to expand...
Click to collapse
If you get a chance, try this on a Windows XP or Windows 7 machine that you haven't connected the Transformer too yet, and follow the guide exactly, and I'm pretty sure it will work without a problem I'm just thinking something has happened when it loaded up the drivers for you initially and that is why you are having the issues, or some background process on either Windows or the Transformer is making the device seem "busy", thus giving you the not ready error, as this process has worked for many many other users.

I was just thinking about it. Maybe I can try that on my downstairs computer. Ill give it a shot Sunday night and see how it goes...ill let you know...

[RELEASE] One-Click UnBrick updated 10july11

Try One-Click UnBrick... If that doesn't work:
Try "3 button combo".. If that doesn't work:
Try a "301k Factory Mode jig"... If that doesn't work:
Try UnBrickable Mod http://forum.xda-developers.com/showthread.php?t=1236273 (if available on your platform)
If you require additional help, send me a private message, we can work something out.
Background
I've been working on stopping the bricking problem on our phones for a while now.
Ever tried JTAG unbrick recovery?--superhuman soldering skills no longer required for JTAG
Developing methods to recover bricks without JTAG - I keep this updated with current information as it develops.
ALL JIG VALUES here! --this will give you some resistor values to try
Altered water damage indicators --um... just in case you lick your battery and need warranty replacement
The Galaxy S Hack Pack--A compilation of resources for Galaxy S Phones.
I wanted to write some software which will help the user to understand what they are doing.. So I began the Heimdall One-Click project. http://code.google.com/p/heimdall-one-click/ Heimdall One-Click is not yet finished, but the Unbrick is complete. Heimdall One-Click is based on binaries from another Open-Source project, called Heimdall by XDA member Benjamin Dobell.
About One-Click UnBrick
This Software:
Will work on all Samsung devices which use Odin3
Is a single, portable executable
Is the first one-click anything for our devices on Linux
Works on Mac
Works on Windows
Is open source
Is programmed in Java
Deploys and installs Heimdall for your OS
Is super easy to use.... Only one button!
Demonstration video:
Image captured on Ubuntu 11.04:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This software is completely safe. It is a part of my Heimdall One-Click project. I wanted to release this to work out any cross-platform difficulties which may be encountered before I release Heimdall One-Click.
Instructions
1. Copy OneClick.jar to your Desktop-- or any other folder on your computer, It won't work on a network share.
2. Double click. -- As long as you have Java installed On Linux and Mac you are up and running.
For some versions of Windows as a work around to UAC (User Access Control, the annoying popups), a executable called "OneClickLoader.exe" has been deployed to the same folder as OneClick.jar. It is important that you do not rename OneClick.jar until after runnning OneClickLoader.exe
3. right click OneClickLoader.exe and select "Run as Administrator" -- Setup should be run-of-the-mill.
Fate-Silver said:
It works with all softbricked condition basically.
Stuck in a boot loop?
Is it still able to boot into CWM(Recovery Mode) or Download Mode.
If it's still able to go back into Download Mode, you don't need this software.
Just turn your Captivate into the Download Mode and flash back to STOCK Eclair or Froyo using Odin 1 Click or whatever similar.
Click to expand...
Click to collapse
Problems and Comments
If you would like to comment on something post here on XDA
If you're unsure of something, post here on XDA
If you have a show-stopping bug, please use this form: http://code.google.com/p/heimdall-one-click/issues/entry
This is a list of all bugs reported: http://code.google.com/p/heimdall-o...+Priority+Milestone+Owner+Summary&cells=tiles
I am very interested in feedback. If you would like to test this, just put your phone into download mode and click the unsoft brick button. It will simply reboot your phone. It will not flash any firmware and it does not have the capability to do anything except release the locks which prevent a phone from booting if they are present.
Click Here to Download One-Click UnBrick 10July11 from GoogleCode
You will need Java installed on your computer: Do you have java?
Disclaimer: All materials presented are for informational purposes. This content is not an authorization, advertisement, nor a suggestion to flash your phone with custom firmware. In no event shall I be held liable for any direct, indirect, incidental, spcial, exemplary, or concequential damages, including but not limited to loss of data, business interruption or damage to equipment. This information is released AS-IS with no written or express warranty or liability.

Linux users, mark this file as executable:
Code:
chmod +x OneClick.jar
All platforms: Double Click to run, OR, right click and open with Java, OR from command line:
Code:
java -jar OneClick.jar
Releases
-Version1.0 3July11 initial release
-Version1.b 4July11 fixes windows 7 & Vista UAC. Thanks to Roddreick for windows UAC workaround binary.
-Version1.IIX 5july11 fixes Winodws 7 and Vista. Adds countdown to non-imperative notifications. Adds real-time monitoring to determine if dependencies are actually required on Windows, rather then blindly installing. Since windows is such a PITA, this was alot of work. This version will work if you have Java installed and OneClick.jar on your computer (no network shares) on Windows XP, Windows Vista, Windows 7, Mac OS X Snow Leopard, and all Debian based Linux distributions including Ubuntu and Mint.
-Version 1.SVNR33 9july11 Much smaller package size, decreased by 5 megs. Fixes browser launching on Linux/mac. Decreases logging level to 1. Adds Log to temp folder at level 4. Adds optional donations to Heimdall or One-Click. Adds Windows Problem Resolution Center.
-Version 1.FINAL 10July11 Fixed UAC issues, File may now be renamed on Windows, Left launcher as alternate method, added linux asthetics, fixed driver link
Major Operating Systems requiring testing
Mac OS-X Leopard
Mac OS-X Snow Leopard
Mac OS-X Lion
Linux Ubuntu 32
Linux Ubuntu 64
Linux Mint
Linux Debian
Windows XP
Windows Vista
Windows 7
note: If you are having problems with drivers, This is caused by an invalid USB Device ID in the ROM installed on the phone.
If you'd like to contribute to the next version
Testing on your platform is as simple as putting your phone into download mode and clicking the button. It will simply reboot the phone if the phone is not bricked.
Grab the code from the SVN: checkout http://heimdall-one-click.googlecode.com/svn/trunk/
You can modify the code with NetBeans: http://netbeans.org/downloads/
If you come up with a positive change, I'll add you to the SVN as a contributor or a committer to ensure you get credit for your work.
I'm always looking to make a new version. Please give feedback.

wow this looks neat...i will definitely fire it up next time i brick my epic! great job AdamOutler!
edit: tested and it did kick my epic out of download mode in windows
if the command above gives you issues on windows 7 then do the following:
click the start button
goto programs>accessories>
right click on 'command prompt' and select run as administrator
cd to your download folder (ie: cd c:\downloads\oneclick\)
then type 'java -jar OneClick.jar'
you should only have to do all of that the first time so drivers for heimdall can be installed correctly
AdamOutler is working a better solution for the windows crowd

Awesome will try it out went nesesary!

Gotta check this out it's probably gonna have to wait til tomorrow looks cool
Sent from my phone on vacation

Nice work man! Hope I don't have to try it out anytime soon, but I really appreciate the effort you've put into this and all your other projects.

A definite must-have, thanks for this!

awesome this makes me less stressed out when flashing! thanks!will use when necessary!

just as a heads up, not every environment will play nice with the "doube click to run" as the file is stored now on google code. if you're on linux, simply either chmod +x the file or do "java -jar ./OneClick.jar" to run it (assuming java is in your path). seems ubuntu (and derivatives, I guess) assume the jar file wants to be opened with archive manager by default, so set it to run with java beforehand (launched with sun java 6, didn't try openjdk)
add to that the application doesn't seem to reliably recognize heimdall 1.0.1 CLI... attempting to run it returns a blank version string but after updating to 1.0.2b it recognized it fine. not world-ending, but just something I thought you should be aware of.
I'm a bit more interested in your heimdall one-click attempts though, as I'd like to see something like that implemented for 2.2 (since not every captivate can go back to JF6 it seems)... I've been pointing people at the leaked JI6 odin one-click for now, as it contains all the necessary files and is usable on every device.
edit: looking a bit more over heimdall's implementation, does this simply run the "heimdall close-pc-screen" command in an easy to use GUI?

Kaik541 said:
just as a heads up, not every environment will play nice with the "doube click to run" as the file is stored now on google code. if you're on linux, simply either chmod +x the file or do "java -jar ./OneClick.jar" to run it (assuming java is in your path). seems ubuntu (and derivatives, I guess) assume the jar file wants to be opened with archive manager by default, so set it to run with java beforehand (launched with sun java 6, didn't try openjdk)
add to that the application doesn't seem to reliably recognize heimdall 1.0.1 CLI... attempting to run it returns a blank version string but after updating to 1.0.2b it recognized it fine. not world-ending, but just something I thought you should be aware of.
I'm a bit more interested in your heimdall one-click attempts though, as I'd like to see something like that implemented for 2.2 (since not every captivate can go back to JF6 it seems)... I've been pointing people at the leaked JI6 odin one-click for now, as it contains all the necessary files and is usable on every device.
Click to expand...
Click to collapse
True... I'll add that to the first post.
Heimdall one-click is operational. I'm working the kinks out of it with the one-click unbrick first. I've sucessfully flashed my phone on all three platforms using heimdall one-click. I don't feel comfortable releasing something like that without thorough testing. This is basically testing for my one-click platform.

can you do a write up on how to brick your phone, and the many ways to it.

Awesome work. Very good and very useful tool, Adam!

Stev3-o said:
can you do a write up on how to brick your phone, and the many ways to it.
Click to expand...
Click to collapse
Sure.. too easy.
Soft bricks:
Flash improper firmware which the system recognizes as improper
Prematurely terminate transfer
Flash with a bad cable
Hard Bricks:
Flash improper bootloaders
Flash mismatched versions of proper bootloaders
Flash bootloaders with a bad cable

AdamOutler said:
Sure.. too easy.
Soft bricks:
Flash improper firmware which the system recognizes as improper
Prematurely terminate transfer
Flash with a bad cable
Hard Bricks:
Flash improper bootloaders
Flash mismatched versions of proper bootloaders
Flash bootloaders with a bad cable
Click to expand...
Click to collapse
Quick question: Does the Odin 1-click flash the primary bootloader? I think I may have hardbricked my cappy tonight. I went from cognition beta 1 (2.3.3) with new bootloaders and one-clicked to 2.1 the phone made it to rfs and then froze. Now it will do nothing. You think I killed it? Thanks.

Coldskiesfullofblue said:
Quick question: Does the Odin 1-click flash the primary bootloader? I think I may have hardbricked my cappy tonight. I went from cognition beta 1 (2.3.3) with new bootloaders and one-clicked to 2.1 the phone made it to rfs and then froze. Now it will do nothing. You think I killed it? Thanks.
Click to expand...
Click to collapse
that's a question for Q&A.
You'd need to check it out with UART for any answers.

So if I read the op and the links right there still isn't a non jtag solution for hard bricks? I asked toys becuase it seemed that with refering to the herr bricks and what causes them as well that you have found a work around... I probably just misunderstand it though.
SIGNATURE : Life is like a box of captivates, you never know if your gps will work

AdamOutler said:
Sure.. too easy.
Hard Bricks:
Flash improper bootloaders
Flash mismatched versions of proper bootloaders
Flash bootloaders with a bad cable
Click to expand...
Click to collapse
Can this software fix the hard bricks? If yes.. too good, many thanks. You made the life less stressfull.

Haven't had to use it and hopefully never will but thank you Sir!

bigbyte.me said:
Can this software fix the hard bricks? If yes.. too good, many thanks. You made the life less stressfull.
Click to expand...
Click to collapse
NO. Hard Bircks are mainly because of wrong Bootloaders, if that the phone is unable to boot, so can't access it. If its HardBricked my guess is only Samsung can unbrickit. BTW new GB bootloaders are un-brickables. They now has the hability to re-download a ROM on Phone<---->PC Screen.

thanks, you are genius, huge help!

[GUIDE] Noob's Guide to setting up ADB

How to get working ADB-- The Expedient method
Since the release of the mtd ROMS the importance of being able to use ADB has greatly increased. This guide is designed to produce a working adb evironment in windows. It is designed be as simple as possible and to avoid command line as much as possible. This guide is not targeted towards advanced users who can set up a working adb environment on their own. If you can setup adb from Google's packages, please avert your eyes and read no further -- this guide will only bring out the elitist snob in you.
If you are still with me you have likely tried to set up adb and failed. Perhaps you have a bootloop in an mtd (cm7, miui, OMFGB) ROM and are trying to avoid losing everything with an Odin flash. Perhaps you are trying to troubleshoot in another way. Regardless, this guide will get you going.
Step 1: Install USB drivers.
A) If you are using a Touchwiz based ROM (COMROM, Evil Fascinate) you will need the Samsung Fascinate driver.
B) If you are using a MTD based ROM (ICS, CM7, MIUI, OMFGB) you will need to use the Nexus S drivers.
Step 2: After you install the appropriate driver, put your Fascinate into Debugging Mode by:
Gingerbread: Settings->Applications->Development then checking Debugging Mode.
ICS: debugging mode is found System Setting>Developer Options>USB Debugging.
Step 3: Connect your phone to your computer and open up Device Manager.
Step 4: DON'T SKIP THIS STEP. You will see Fascinate/Nexus S with possibly an exclamation mark, just double-click on it, Update Driver->Browse my computer for driver software->ADB Interface then choose Samsung Electronics Co., Ltd, then choose Samsung Android ADB Device.
Step 5: Download and install Droid Explorer. Please select the appropriate build for your PC architecture. Be sure to select "Set up the Android SDK For Me" during the setup.
Step 6: Launch Droid Explorer and select your phone.
To send ADB commands click the button in the red box in the image below.
To view logcats click the button in the blue box below.
Step 7: How to use Droid Explorer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Troubleshooting example:
You are on AOKP and set a bad overclock as boot settings. 3-fingering is a no-no and you get frozen during boot or a bootloop before entering the OS and therefore can't reach recovery. To get into recovery click the button in the red rectangle. Then type "reboot recovery" at any time during the phone boot process and press enter. Your phone should reboot and you should end up in recovery. Success!

I have a fully Functional adb, android skd, java, eclipse, all the stuff needed for a proper build environment, and I still use Droid explorer and Android Commander, for some things. Once you get used to these programs they are very useful especially for a simple app swap or adding an app to your system file. Good of you to share the process with others.

Nice guide, would have been easier than setting up a full adb environment on my work pc in addition to my home pc. Where was this 6 months ago?

Dude thank you so much for that nexus driver. I have not been able to get my ADB to work until now with that driver. Every other one I got wouldn't work and no one really could help me. Just kept saying install driver. Now ADB finally works. The Droid Explorer program is pretty cool too. Thanks very much!!

I've edited the guide a bit to make it easier to follow. This should be the final version of it unless someone has an issue or suggestion. I'm glad this has helped some folks and I hope it will continue to do so.

ok somethings wrong because i have followed every freaking guide there is including the wiki for cyanogenmod and this one and adb is still "not a valid command" or whatever in the command prompt......freaking hell
**now all of a sudden it's kinda working, if i choose reboot into recovery from the application it just reboots the phone, not into recovery.....and if i choose the log icon it says it cant connect to device even though the device is clearly shown as connected in the main screen......sheesh
THANK YOU MAKE THIS STICKY NOW OR I WILL PUNCH BABIES

Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked

Just passing along a thanks for this guide in a world where OC/UV is so easy to screw up.

sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.

bobloblaw1 said:
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.
Click to expand...
Click to collapse
Yes and it appeared to install correctly.

+1 for sticky

sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
I have a different but similar issue. It sees my device when connected and disconnected but I can't do anything. If I choose reboot it rebooted. If I choose reboot recovery it just rebooted, no recovery. I can see the devices tree directory but if I try to access any of them I get an error. Also if I click the logcat button it opens the terminal window but has an error, says it can't connect or something. If I click on the terminal button it opens the terminal but no commands are recognized. But when I connect and disconnect my device it shows up and in device manager there are no errors.

Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.

I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App

allcity187 said:
I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App
Click to expand...
Click to collapse
Probably. But that requires you to have a linux box setup and handy; which many people do not have.

Well you can always dual boot your computer. I have windows 7 and arch linux set up. I'm usually on linux but I still have software that I use on windows, so that's why I kept it.
Sent from my I500 using XDA Premium App

bobloblaw1 said:
Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.
Click to expand...
Click to collapse
My USB cable is fine. Went back uninstalled the drivers and explorer. Downloaded fresh copies of both and same thing????
Giving up for now. In the event of a crash I can Odin back,rebuild,restore apps, etc. in about an hour. Less time than I have spent trying to get this to work! LOL. For now I'm back on the stock CM7 kernel and not doing any tweaking that might cause a crash. All is good thanks guys.

sfobrien: Sorry I couldn't get thisto work for you.
jamesandmandy: Did you ever flash anything in red recovery? Are you able to get into blue recovery by the normal method? Your issue sounds like something on the phone recovery end if You are able to send commands to it successfully over adb.

bobloblaw1 said:
sfobrien: Sorry I couldn't get thisto work for you. /QUOTE]
Hey no problem. I think it is some kind of glitch between Windows 7 and the explorer program. CM7 is an awesome upgrade so no complaints here.
Click to expand...
Click to collapse

Thanks for this. I've always avoided adb because it seemed to complicated to setup/learn. I'm up and running.
Sent from my GT-P7510 using XDA Premium App

Android x86 tutorial

Android x86
there are several developers working on this project there is a source for what they have so far, that said ill link in a sec. this is a tutoral of how ive managed to get this far in android x86 ive got most of root working on various builds let me state that i am using a acer aspire one 532h 2588! i am currently running RC2.1 by314
For root you must be on ext3 to get it working although it will still run in ntfs and you will be able to read windows usb drives ext3 you cant the con to ext3.
http://www.youtube.com/watch?v=JfWb_h96_-Q&feature=youtu.be
YouTube how to
-Dev Links-
http://source.android.com/
http://code.google.com/p/android-x86/
http://tabletsx86.org/
http://www.android-x86.org/
http://android-x86.sceners.org/en/
http://www.android-x86.info/
http://www.ceh-photo.de/blog/the ones here work for more computers, just saying! http://www.ceh-photo.de/blog/?p=562 BETA 4
-Needed-
2g min usb for installation of iso
i used a external hdd, you can use a usb drive 4g min i would say, or you can install on os hdd but do not format it!
lili usb creator - http://www.linuxliveusb.com/en/home
minitool partion wizard - www.partitionwizard.com
-steps for live testing-
1) use lili usb creator to install the iso onto a 2g min usb
a) select the RIGHT usb drive lol
b) then select the iso that your going to test
c) i personally only have format the usb selected but you can install the other crap but i dont lol
d) click the lighting bolt to start click the oks lol
2) insert the usb with iso on it, to your laptop with it off
3) start the laptop into the boot options (f12 for me) select the usb with iso
4) click run live...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TEST EVERYTHING YOU CAN, root hardly works here and no data is saved...
-steps for installation-
1) format your usb or hhd partion with minitool partion wizard to either ext3 (most root availible) or ntfs (for use with usb drive ?music?)
2) use lili usb creator to install the iso onto a 2g min usb
a) select the RIGHT usb drive lol
b) then select the iso that your going to use after tested for the best one
c) i personally only have format the usb selected but you can install the other crap but i dont lol
d) click the lighting bolt to start click the oks lol
3) turn your laptop insert the usb with the iso and the usb or external or even the internal if you want to do something crazy but you will format your windows or stock os! i use a external hdd as in my vid..
4) start your laptop enter your boot options (f12 for me) select the usb with the iso
5) select to install
a) select the partion that you set up earlier (if you dont see it detect devices ext3 = linux)
b) choose to format (i format to the format i set it for you dont have to...)
c) yes install grub (if installing to external you dont have to install grub but i do for debugging and to get to windows without unpluging)
d) yes install windows if your installing on a windows hdd
e) reboot (as soon as you see your bios you can remove your usb if your dont you will get error 17)
And now your running android ics on your laptop/netbook/pc
I didnt develop any of this! just trying to get it out there for others
thanks button is nice but not nessary
Acer Aspire One 532h Android x86 ICS RC2.1...

Nice tutorial, thanks!

MEHH lol i thought there wasnt a comment yet lol oh well i need to modify it
Acer Aspire One 532h Android x86 ICS RC2.1...
http://forum.xda-developers.com/showthread.php?t=1973492
Android x86 tut

LOL awesome
XML

Nice man
Sent from my SCH-I500 using Tapatalk 2

Awesome
Sent from my PG86100 using xda app-developers app

You should probably mention that the android x86 builds are generally limited in their hardware support.

lambstone said:
You should probably mention that the android x86 builds are generally limited in their hardware support.
Click to expand...
Click to collapse
Thanks that's why I say test before you install it. The link with green next to it is Chris's blog his runs on more than the rest
Fascinating AOKP Jelly Bean Milestone 1 Devil 1.8.1...

I am confused.
I'm trying to download LiLi. I click on the download link here but it takes me here. Clicking the "Download LinuxLive USB Creator" in the second link takes me back to the first.
Am I not clicking the correct link?

Will this be Mac capable? Also, I am running Intel Centrino2, no support for us?

I am writing this from Andorid on my laptop.
Very cool.

sebouh00 said:
I am confused.
I'm trying to download LiLi. I click on the download link here but it takes me here. Clicking the "Download LinuxLive USB Creator" in the second link takes me back to the first.
Am I not clicking the correct link?
Click to expand...
Click to collapse
Yes you are
BlueEditionE6 said:
Will this be Mac capable? Also, I am running Intel Centrino2, no support for us?
Click to expand...
Click to collapse
On that I have no idea I'm trying to get as many developers as I can to help out I'm about to try to compile a newer version if I can get my PC you repo everything it lost net last night and can't get it to restart or catch up idk what to do
Try beta 4 its your best bet
Sent from my SCH-I500 using Xparent Cyan Tapatalk 2

Thank you so much for this guide and these links, i have installed android on my dell laptop and its working perfect, haven't tested everything but everything i have tested so far seems to work great.

Nice job! Got it running on my laptop just fine. I wonder if it will work on my desktop?

shelby04861 said:
Nice job! Got it running on my laptop just fine. I wonder if it will work on my desktop?
Click to expand...
Click to collapse
Beta 4 runs on my amd Asus machine but my wifi adapter doesnt. can anyone help me compile a recovery for computers
Sent from my SCH-I500 using Xparent Cyan Tapatalk 2

The WiFi is kinda weird but I haven't really looked into it too deep. It will not connect to my home WiFi network but it will to my neighbors and my cell phone. Go figure. I have been trying out different iso images from the many downloads but I can't fins one yet that will boot on my old dell dimensions 2400 desktop. One of the error messages that pops up is for the computer model check and of course it fails, among other things. If anyone knows of a download for an iso that will work on at least dell desktop computers, let me know.
If it's broken...beat it into submission until it works!

Kaptinkrunk said:
Android x86
there are several developers working on this project there is a source for what they have so far, that said ill link in a sec. this is a tutoral of how ive managed to get this far in android x86 ive got most of root working on various builds let me state that i am using a acer aspire one 532h 2588! i am currently running RC2.1 by314
Click to expand...
Click to collapse
NEED HELP
I installed in the 5gb ext3 partition i created for the ICS, installed grub. But when I try to run it after installation, i end up with a static screen,
ok, linking youtube video doesnt work for me as well, so heres the link http://www.youtube.com/watch?v=dfH2zDcX0kA
anyone can help?
Also, it screwed up my Win7, wont allow me to boot, when i try to recover the Win7, the reboot process kept getting interrupted by GRUB, anyone can help me with that? Now I am without a computer.
Blue

Thanks for sharing Android x86 tutorial for every android developers for better solution. I appreciate your way.

BlueEditionE6 said:
NEED HELP
I installed in the 5gb ext3 partition i created for the ICS, installed grub. But when I try to run it after installation, i end up with a static screen,
ok, linking youtube video doesnt work for me as well, so heres the link http://www.youtube.com/watch?v=dfH2zDcX0kA
anyone can help?
Also, it screwed up my Win7, wont allow me to boot, when i try to recover the Win7, the reboot process kept getting interrupted by GRUB, anyone can help me with that? Now I am without a computer.
Blue
Click to expand...
Click to collapse
Try booting a Win7 Setup DVD, then hit repair and proceed with following what shows your on screen.

white-energy said:
Try booting a Win7 Setup DVD, then hit repair and proceed with following what shows your on screen.
Click to expand...
Click to collapse
It wont let me repair, since repair requires reboot, but then GRUB kicks in everytime i reboot, therefore stuck. I popped in the cd and reinstalled Windows.... but lost every program,
this is a bit off topic, but how can i restore everything from my old win7 to my new win7? I tried using the comand prompt in the recovery page, but the programs are still missing, tried just copy and pasting from windows.old folder to current windows folder, no luck.