Related
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
aikeru said:
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
Click to expand...
Click to collapse
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
deekjx said:
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
Click to expand...
Click to collapse
Did anyone try this solution?
Since the bootloader is still there all you do if not able to flash via async when in android is flash via bootloader
Moved to general as not ROM Dev.
Thanks for the information, guys!! I will have to try it out over this weekend and see how it goes...
I can confirm that flashing via bootloader works fine, also flashing from SD works as well, in fact I keep a 128MB sd with a WM kaisimg.nbh on it handy just in case I need to flash a good WM rom for some reason.
Is there an Android OS with everything working on the Kaiser?
Dukenukemx said:
Is there an Android OS with everything working on the Kaiser?
Click to expand...
Click to collapse
You can see in different post of android rom what works and what doesn't works.
actually, Bluetooth and camera never works for in android 2.x build and some other apps doesn't works
I've been running Android for a few weeks now from this thread:
http://forum.xda-developers.com/showthread.php?t=614382
I've found everything to work with the exception of Bluetooth, video camera (normal camera works fine), and the barcode scanner. Also, my battery life is cut in half, but I have an extended life battery so I get a day or two out of it.
I prefer this method as you can just boot Android at will and can soft reset to go back to WinMo.
Just to let everyone know I did flash WM back just fine since I have HardSPL 3.56 and used the stylus to press the reset + camera button at the same time to get to the tri-color screen.
From there I flashed from USB without any problems.
Thanks again for all the help!
I am having problems reverting back to WM after attempting to install android to NAND. Something happened where the only way I was able to get to the android installer would be if I had the KAISDIAG.nbh file on the SD card so it would get past the tri color hard spl screen . Well as a result, I can't get into boot loader. It shows that screen for a split second, then if I do camera + power and then reset. Then I have to pull the battery. Can someone help me? It seems like it will only go into the Android bootloader, which obviously won't allow it to install a WM rom. SD flashes are my only choice because the usb port is pretty messed up. Any help would be greatly appreciated. Thanks.
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
zenity said:
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
Click to expand...
Click to collapse
Thanks, but unfortunately this still did not work. Have any other suggestions? I think the only way will it even do anything is if I have the KAISDIAG.nbh file on the card. It recognizes that, but then goes straight to linux. IDK what else to do. Could you be a little more clear on the procedure for getting into the bootloader? Thanks.
Ok please follow these steps carefully.
1. Format the SD card, make sure you are formatting it as FAT32, not FAT.
2. Download a Winmo Rom from somewhere handy.
3. Extract the Rom to a handy folder, find the RUU_Signed.nbh file, rename that to KAISimg.nbh
4. Copy the KAISimg.nbh file to the SD card. You should only have one file on the SD card, no folders just the NBH file.
5. pull the battery from the phone, wait at least 5 minutes.
6. Replace the battery. Press Power button, and hold down camera button, until the tri color screen appears.
7. The screen should now change to a white one, and when it's checked the nbh it will ask you to press power key again. do that.
8. Now it should flash the rom, this should take a while, 5-10 minutes, once it's finished you should get a message of success.
9. Now pull the battery again, wait 5 minutes, replace the battery, and power on, you should now boot into Winmo.
Hopefully this should solve your problems, if not then let me know which setp failed and we can work on that stage.
Finally, don't panic, take it slow, it'll all work out
Thanks, but the problem starts at number 6. I am supposed to press the power button, release it, and hold the camera button till it gets to the white screen, right? It's still stuck at the splash screen. I tried holding both and that didn't work either. Anything else I can try? I hope i'm not screwed?
If I put the battery in, boot it up, then push the camera and insert the stylus into the reset hole, it gets to the tricolor screen, then for about 0.5sec it flashes the white screen with a message saying "No image File." I know for sure the .nbh file is there.
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
zenity said:
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
Click to expand...
Click to collapse
Unfortunately, as much as I wish it was, it is not the problem. I'm on a Mac, but booted windows 7 to be make sure it was formatted to FAT 32, which it was. Is there some way I can fix permissions? Every time it runs, I keep getting the error saying that it is in read only mode. I obviously need to get it into writing mode. I don't think the fix permissions option on the installer did anything either.
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Tilt Fanatic said:
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Click to expand...
Click to collapse
Alright, I'll try and sum up your experiences. Tell us if we're missing anything;
You have the following symptoms
Linux Android-installer works
Tri-color bootloader semi-works
You cannot use the USB
You cannot install polymod's Eclair build
Now, you have mentioned a couple of things you have tried, such as
Replacing the Linux NBH with another version
Fixing permissions on the SD-card
Fixing permissions through the Android-installer
Flashing a WinMO ROM through SD card
You did mention getting other behaviours when you switched to another NBH, such as "KAISDIAG.nbh" not being required.
Now, this is a long shot coming from me, as I have had no troubles with flashing, and the fact that I can use my USB, but since your phone is pretty messed up I guess it can't hurt as a suggestion;
You can flash to other NBH's I take it, as you mentioned you did a downgrade. What I'm a bit curious about is whether you did try to flash to a WinMO rom when you had downgraded to your current NBH.
Also, you said the previous NBH required you to have "KAISDIAG.nbh" on the card to even get working. Did you try and rename a WinMO-ROM's NBH to "KAISDIAG.nbh" and flash that? Might be that the flasher is really constrictive with the file names.
EDIT: Oh, and what about trying to run other Eclair builds? Just to see if you can nail it down to this being a problem of the builds or something more bound to the actual hardware/SPL/NBH's.
hi, i'm using tp2 from t-mobile
using EnergyROM
fat32 clean format (not quick one)
installing in the sd card
--
i tried the 3 cabs
and i get to the black screen then is showing this:
failed to mount the sd card
"/bin/sh: can't access tty; job control turned off"
also keep getting
"kernel time out blah blah"
what to do?
thanks in advance
atomiq said:
hi, i'm using tp2 from t-mobile
using EnergyROM
fat32 clean format (not quick one)
installing in the sd card
--
i tried the 3 cabs
and i get to the black screen then is showing this:
failed to mount the sd card
"/bin/sh: can't access tty; job control turned off"
also keep getting
"kernel time out blah blah"
what to do?
thanks in advance
Click to expand...
Click to collapse
not exactly sure....when u tried each cab, did u completely uninstall and delete all traces of each build including the fsck files? alot of times if not, and u try to install a new one, itll stick pick up the old data and mix with the new and cause issues. The one to try thats the easiest is the AOSP. data and service works off tops without doing anything.
try this...whatever cab u got in there..uninstall it...then ...go into file explorer or whatever and delete any and all traces of the previous build. after that, if u have clear temp or clean ram, use that. then soft reset.
get the build cab of ur choice, but id recommend the AOSP for the quickest start. download it to root of storage card which is /storage , not in a folder in storage(example /storage/programs). it has to b in the root. then install. then soft reset. once it boots back up, go to the android icon. press it..then update all the new files for the build b4 ur first boot up. u should see the tab to let u update. after update complete, then press run android...and hopefully any little issues or residual files are gone and u can complete the startup or bootup of android. let us know if that didnt wrk for ya.
ok now boots, and works fine
i'm using AOSP 2.1 updated
EDIT MY INTERNET WORKS NOW, LOL,
I'm having the same exact error on my AT&T Tilt 2 with stock ROM. I downloaded the AOSP into the storage/programs folder of the SD card, installed it to the SD card, then ran the update. After the update, I got the "Failed to mount the SD Card. Cannot Continue" error. I uninstalled the program and got rid of everything ans started from scratch with the same error.
Any idea?
Okay.... I've tried this a few times with no luck. Here is what I have:
AT&T Tilt 2 with stock ROM. I started with a fresh Hard Reset this morning (due to problems with Good Mobile Messaging) and loaded the AOSP file to my micro SD card (\Storage Card\ProjectAndroid 2.1AOSP 042610.cab). I ran a level 3 CleanRAM, then double clicked on the AOSP file on the SD card using TotalCommander. The file asked where to load it to and I chose the SD card. It successfully installed and I did a Soft Reset using the red reset button behind the battery cover.
Once turned back on I go to Start and press Project Android. Once loaded up, I went to Menu and Update. It updated successfully in about 5-10 minutes and I then clicked Run Android. The screen goes black and runs a bunch of script until it gets to this:
Welcome to Vogue Linux
Running an fsck on SD card
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
Logical sector size is zero
mount:mounting/dev/block/mmcglkopl on/sdcard failed: Invalid argument
Failed
Failed to mount the SD card. Cannot continue
/bin/shi can't access tty; job control turned off
It then freezes at this point and stays there. I've uninstalled and removed all sources of the files (that I could find) and started from scratch several times and it does the same thing each time.
Is something wrong? Am I missing something simple?
ROM Version: 1.59.502.3 (67150) WWE
Rom date: 09/25/09
Radio Version: 4.48.25.20
Protocol version: 61.39tc.25.30U
is there any other info you need?
i did use this formatter
http://www.megaupload.com/?d=287HD74A
extract, install, open, select your unit, click on option, select full erase ON
let ir run..
this promise to fix this error acording to a forum that i read
outside of XDA, it can also throw that same error if you are using
a SLOW storage card.
pls report what happened so we help other people with the same issue..
The error message is normal. Just ignore it unless the thing wont boot overnight
thebulletfromhell said:
The error message is normal. Just ignore it unless the thing wont boot overnight
Click to expand...
Click to collapse
So just leave it there and let it keep running? I'll give it a try.....
sethjamto said:
So just leave it there and let it keep running? I'll give it a try.....
Click to expand...
Click to collapse
No joy..... it hung up on the same screen that I quoted above for over 5 hours. I soft reset and then uninstalled the software. I guess if I'm destined to have Android, then I'll just go out and buy an Android based phone.....
i guess you didnt tried the FORMATTER that i've posted
anyways
maybe you should wait for the release of HTC VISION
or wait much looooooonger a couple of years for an official android rom
for our poor htc rhodium..
good luck.
I am currently having problems booting the haret file for XDandriod 2.2, i have checked and read with other forums looking for answer but nothing stood out.
When i fist downloaded Froyo 2.2 Blazn for my Tilt 2 it worked fine, even saved contacts and marketplace worked. But when I soft reset went back into windows and try to run it i got an error" cannot open script file \sd card\default.txt" I know there had been a lot of reports of this but nothing fit the description so I did a clean install to see the changes, worked fine the first time but then wouldn't boot up again after the first or second soft reset. I'm not sure what to do at this point, i don't want to have to soft reset every time i want to use my XDandriod interface.
TheImp0rt said:
I am currently having problems booting the haret file for XDandriod 2.2, i have checked and read with other forums looking for answer but nothing stood out.
When i fist downloaded Froyo 2.2 Blazn for my Tilt 2 it worked fine, even saved contacts and marketplace worked. But when I soft reset went back into windows and try to run it i got an error" cannot open script file \sd card\default.txt" I know there had been a lot of reports of this but nothing fit the description so I did a clean install to see the changes, worked fine the first time but then wouldn't boot up again after the first or second soft reset. I'm not sure what to do at this point, i don't want to have to soft reset every time i want to use my XDandriod interface.
Click to expand...
Click to collapse
The ONLY reason this happens is you don't have a valid startup.txt where you run haret.exe from. It can't be named startup.txt~ or anything like that. Not sure how you booted in the first place if you didn't have a proper startup...
Hmm, i renamed the file and when i got o Haret and click run nothing happens and since im using XDandroid i used the shortcut and it fails and says could not find startup.txt My startup folder is currently 0 bytes could something could of wipped the contents of it on the first startup?
This has been a reoccurring issue with the latest 2.2 build. My personal fix thus far has been to copy the startup.txt file to the root folder of my phone, then after each restart copied it back to the andboot folder.
Hello,
I need some help. Install its Android OS, but after he reset my Kaiser again charged WinMo OS. My question is whether it is possible to choose which OS to load first or with any program or edit the file to indicate to launch the first Android.
Sorry for my bad english :S Use Google translator
If you have installed Android to SD card and use Haret.exe then it will always reboot to WM.
You must install to nand if you wish to boot to Android only, which will wipe WM totally and replace it with Android.
The guide stickied at the top of the forum is a good tutorial in doing this
That does bring a good point to my mind though, we could create an exe that loads at startup of wm to auto load haret and startup if the user doesn't cancel in so many seconds (like grub). I keep WM on my phone so I can easily change my droid version and also I know everything works including opening office files (actually that's the biggest sticking point for me keeping it).
Thanks for support. Today I try to flash via NAND method.
Kind Regards
Lybomir
I flash my Kaiser with latest zImage-2.6.32-froyo-09-09-10_21 from here http://it029000.massey.ac.nz/vogue/files/?C=M;O=D and my device loading Android OS very slow, and big problem is : Phone go in screensaver and I try to unlock and screeen stay only in white light, no picture, no widgets... total block. Only solution is it a use Soft reset button or remove batery
Maybe you choose the wrong panel type?
I can read in your signature Duo Boot so I guess you installed onto the SD and use Haret to run Android.
If so, you have to edit the default.txt file locate in ANDBOOT folder and modify the value following htckaiser.panel_type.
You can specify 1, 2 or 3 (most Kaisers use panel type 2)
Wrong panel type may lead to awake problems or wrong colors...
The excessive slowness may be due to a slow SD. Which class is it? Use at least class 4 SD.
---- EDIT -----
In case you already flashed to NAND, to change the panel type you have to choose the right kernel (the kaisimg file) or you can edit the one you flashed following instructions and links you can find in #4 at http://forum.xda-developers.com/showthread.php?t=680518
obviously you have to reflash the kaisimg.nbh but you don't need to flash Android again
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
dlink.bg said:
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
Click to expand...
Click to collapse
May you try to install a different build and see if you fall into the same problem?
BTW, just after installing, don't start playing soon with the device: initially skip all settings (touch the android, don't set google account and so on) and leave the phone quiet for at least 10-15 minutes: some builds need to copy file to the cache and playing with the device may interfere with this operation leading to unpredictable effects...
Let we know...
It is slow because you installed it on sdcard.. both partition.. if you are on nand. Try install both partition on nand partition.. and try hawks soad rls 3 as me.. its fastest build for kaiser.. and I haven't ever problem with white screen ata awake.. try it in that haws soad ion build.. you can finf it in that forun.. just find it
Sent from my HTC Kaiser Ion using XDA App
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
dlink.bg said:
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
Click to expand...
Click to collapse
You're welcome
And I'm waiting to know
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
zenity said:
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
Click to expand...
Click to collapse
Hi Zenity... Yes, know that piece of software.
But as You have to boot WinMo (Yes, I Know, not all the services need to be running but system must be loaded and started, GUI must be running and so on) in order to DualBOOT can start, I can guess it's only a partial time-save... isn't it? Did You tried it?
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
zenity said:
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
Click to expand...
Click to collapse
Yes, of course we haven't enough NAND to have both OSes!!!
What I was thinking to (but I'm a lot far to inspect WinMo booting sequence...) is if may be possible to wedge a sort of bootloader running BEFORE the OS loads or in the early booting process and letting we choose to boot WinMo (in NAND) of Android (on SD).
At present moment I've Android running from SD but kernel NANDed (I've got problems running out of NAND and no time to solve them so I'm using the solid build previously installed on SD) so Kaiser boots quickly... and this confirms it's possible boot SD Android without having to load WinMo or Haret. The more relevant matter I can see is that we have to find a way to wedge the bootloader without have to manual modify the WinMo ROM (virtualization is far from be considered on such devices...)
I suppose this is just a "mind exercise" (Sorry, I don't know how to correctly translate an Italian common saying...
Mind exercise describes it perfectly
Not sure why you would run out of space on nand, unless you are loading a lot of apps, and there are ways to run android that may help with that, such as apps2sd, or data on SD partition.
If you must have WM then your only choice would be using Haret.exe, and the most efficient way to dual boot we have at the moment is the Gen-Y solution, which is not ideal, but does offer at least part of what you seek.
The Android bootloader we use (tinboot.s) is not flexible enough to allow dual booting, but may have some information that may be of some use in this
tinboot thread
See what you think anyway
Sorry, I was not able to be clear... I apologize for my English...
When I said "I've got problems running out of NAND" I intended to say "I've got problems - very bad performances - when Android was running from NAND"!!!
Maybe we are a bit OT...
BTW, I was far from software developing for a long while and never developed low level software for Linux/Unix... but in the past I messed up with Z80, 65xx, 68K and x86 platforms's assembly
Recently I need to approach software developing again (but at a really different level...)
I'd like to have spare time to start again, as this world attracts me more. Maybe I'll give it a chance...
Let me understand... tinboot is actually used bootloader?
BTW, just to be clear... I don't need WinMo and I'm giving Android a chance to revive my Kaiser. I'm looking for a fast and stable build and actually I'm running VaniljEclair RLS11 (Yes, I know, I'd try your Polymod 2.1D build... )
Tinboot is the bootloader we use to get android in nand, not being a coder my understanding in limited, however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
I assumed you meant running out of space on nand, lol, i see now what you mean, no need to apologise for you english, it's fine
zenity said:
--- CUT ----
however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
Click to expand...
Click to collapse
And you're right... it's a useful starting point and I'll read it accurately...
Unluckly, I need a lot of spare time (and I don't, at present) to build a solid knowledge base and to start developing for Android.
yes there should be plenty of room for both oses on Nand, I still have over 90 mb on my wm6.5 nand install with come extra apps in there. So if you stripped down both oses you could easily fit them both on nand and still some space left. But then you need to have a boot loader that will be able to load both oses. I think I heard someone say somewhere they are using grub to boot android from nand, that can boot windows also with the right configuration, that would be where to start.
hi guys!
ive been trying to instal this rom http://forum.xda-developers.com/showthread.php?t=1038694 on my HD2 because... omg windows is driving me insane!
but the SD boot just doesnt work, ive did what they asked me too, download the file, unzip it... put the android folder on the root of my SD card and first tabbed the file for the sound and then i tryed to the file for installing the ROM but it either freezes in a black screen showing "HTC" or it shows that black screen and it reboots my phone and im still in windows
help me guys or give me a suggestion for a different and just as good android rom for my HD2! one with htc sense that is.
Try turning your computer antivirus and firewall off temporarily, and then start the process from beginning over. Antivirus and firewalls sometimes mess with installations.