Flashing on a Mac ( OSX ) + other ? - General Questions and Answers

I am sure several people are having this problem. I tried searching, and found some answers, but need some further clarification.
First off, I am on a 2008 Intel Macbook. I have Parallels Desktop installed, running Windows Professional SP2.
My issue is that when I run ActiveSync, my device is not detected. I have the USB to be run on Parallels, have all the drivers, to no avail.
I have Missing Sync for Windows Mobile running on OSX aswell. That is useful for installing CABs and .exe, but I haven't found a way to flash my device alternatively.
I did try the MicroSD flashing method, but when I format my device in FAT32, transfer the necessary .nbh file, and boot in Bootloader mode, the screen does not change from the white with blue "loading..." text. The MicroSD card is 4GB.
I am hoping you guys can help me figure out a way to flash a ROM to my device on the OSX platform.
Thanks in advance, and I hope you don't find me arrogant for starting a new thread on this topic.
TO ADD: I get the following error trying to run HARDSPL.:
The application failed to load required components. If the .NET Compact Framework is installed on a storage card, please ensure that this card is in place and launch the application again. If this fails, a re-installation of the .NET Compact Framework is recommended. Support info: -2147483643 (80000005)

Related

HardSPL not installing, alternatives?

Hello,
Okay, so I got my Kaiser 2 days ago, though it has a swedish HTC ROM, and I want the English HTC ROM.
I have the rom on the SD card, and when going to the bootscreen, it loads and checks the new rom, and than says "Not Allow".
I checked that out, and that means the CID is still on. But I can't get HardSPL on the device, as soon as it goes in the tri-color screen, I can't connect to the device anymore with usb, meaning I can't install HardSPL.
Anybody got a different way?
Try removing the Unknown device from device manager and re-plug your Kaiser while in bootscreen, it should install the driver again (you can find the drivers in Program Files/Microsoft ActiveSync/Drivers directory if not automatic)
Then it should work.
Can't find any Drivers directory in the activesync dir.
PS. Its windows Vista with mobile center
I would steer clear of trying to flash anything via vista....
Although it *may* work, most of the software tools were not designed with vista in mind. Don't want to brick you shiny new phone now do we?!
Turf out an old laptop or something with XP on if you want to flash.
RUU works fine in vista as does hard spl. I didn't have to do anything special other than run hardspl as an administrator by right clicking and selecting run as admin.
Nope still not working.
There's no other way to do it? Like from sd card or something like a normal rom update is possible
Well, found the Vista drivers. Not working, needed 64 bit.
Found 64 bit drivers, not working, unsigned.
booted the computer with disabled the security, WORKED! So now its flashed.

Fastboot not working with windows 7 beta

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.

Possible to flash ROM using Mac?

This might have been asked before but I haven't seen anything yet through what I've looked... To customize and flash my HD2 is it possible to do it on a Mac, if so what tools do I need? Thanks all
The best way to flash using a mac is to install Windows XP SP3 via Bootcamp.
There are no native MacOSX flashing tools, and the best tools, including MTTY and the CustomRUU run perfectly under this configuration. It is what I use. I have a small partition which I only use for this purpose and keep all the items ther in folders. Radios, ROMs, etc.
You need to find a Windows computer to HSPL your device (only need to do this once), then you can just flash from memory card. Put the .nbh file into your storage card root called leoimg.nbh and enter the bootloader, it'll enter flash mode automatically.
donalgodon said:
The best way to flash using a mac is to install Windows XP SP3 via Bootcamp.
There are no native MacOSX flashing tools, and the best tools, including MTTY and the CustomRUU run perfectly under this configuration. It is what I use. I have a small partition which I only use for this purpose and keep all the items ther in folders. Radios, ROMs, etc.
Click to expand...
Click to collapse
If I was to install Vista on a Macbook Pro doing bootcamp, will it work? This is why I love my Windows PC.

How do I install apps with no SD card?

I've not installed anything on the phone before.
I tried to copy a cab file to the SD card but I've got problems as the phone thinks there is no SD card present.
Can I copy the cab file to the phone's memory? I cannot see the phones memory through explorer on my PC though do I need some special software?
Srry if this is a stupid question I did search but found nothing
Try installing MS ActiveSync. Connect the HD2 to the PC using the usb cable. Once installed, you will be able to see the HD2's files in Windows Explorer. Just copy the cab file to a folder. Disconnect the phone and launch the cab file from the phone's file manager.
Cheers
Microsoft says Active Synch will only work with XP SP2 and earlier I have XP SP3.
Is there anything else I can use?
What does everybody else do - do you not install anything via PC to the phone?
men8ifr said:
Microsoft says Active Synch will only work with XP SP2 and earlier I have XP SP3.
Is there anything else I can use?
What does everybody else do - do you not install anything via PC to the phone?
Click to expand...
Click to collapse
For Vista or Windows 7 the used tool is called Microsoft Mobile Device Center (MSDC). For Windows XP (even SP3) active sync has to be used. Did you try it to install? I´m sure that it will work.
To install applications at your mobile device do the following steps:
a) connect it via active sync
b) using your PC´s Explorer to copy the cab-file containing your application to your mobile device and remember the place you copied it
c) disconnect your mobile device
d) using your mobile device´s go to the directory you copied the cab-file and start it
This way your application will be installed
But I´m sure you would have found the answer without asking here. Mr. Google knows it already
men8ifr said:
Microsoft says Active Synch will only work with XP SP2 and earlier I have XP SP3.
Click to expand...
Click to collapse
XP SP3 here, ActiveSync works with no problems.
As to the installing files to device - you may run out of memory soon, so I'd suggest buying even the smallest card (although preferably min 2GB, if you intend to toy with SD Android at some time)

[Q] heimdall.exe system error

Running windows 7 64bit home premium. Trying to open heimdall.exe and get the error- "The program can't starte because MSVCP110.dll is missing from your computer. Try reinstalling the program to fix this problem.
Installed c++ redistributive for 64 bit system, no luck. Tried to reinstall and chose repair installation. Restarted after each attempt. Searched for the .dll and found it was still not installed on my computer. Tried to manually download and copy to the System32 file and SysWOW 64 folders. Tried running regsvr32 from cmd prompt but get error that it failed to load.
Have been searching for a solution but everything I have come across was either a different issue or was resolved in one of the steps above. Any info or suggestions is greatly appreciated.
Since re-installing doesn't work, you can try finding a copy of that dll file online and putting it in C:\WINDOWS\System32. It may be that your copy has a problem.
I'm a linux user and needed to flash samsung galaxy mini 2.
I tried heimdall and heimdall-frontend, but neither worked for me.
I now run a virtual machine with windows to run odin3..
Could it be that heimdall is not compatible with my phone?
grtz
have a same problem, tested on two PC
I know it is an OLD!! post, but searching the error brings this one up first..
FYI
If installed vcredist_x64 try to ALSO install vcredist_x86.
Worked for me with the MSVCP110.dll missing Error!
Probably the .dll is only in the x86 library.
/flame_on

Categories

Resources