Develop Bugs

first time flashing a rom questions

i read around for methods on flashing a rom. this is my first time .i did a back up with hpb backup and put hard spl 2 on my phone. from what i read sdcard is the best route to go . my question is do i need to erase everytihng off of my card before doing the rom? or can i leave it all there put the ruu file on there and get started ? maybe i should ask is there a tutorial to how to do the different methods?
a side note how do i know if a rom is friendly to changing the orientation when you slide for the keyboard

Natureboyhcg said:
i read around for methods on flashing a rom. this is my first time .i did a back up with hpb backup and put hard spl 2 on my phone. from what i read sdcard is the best route to go . my question is do i need to erase everytihng off of my card before doing the rom? or can i leave it all there put the ruu file on there and get started ? maybe i should ask is there a tutorial to how to do the different methods?
a side note how do i know if a rom is friendly to changing the orientation when you slide for the keyboard
Click to expand...
Click to collapse
No you don't have to take everything off the card. Make sure your card is 2gig or smaller and not SDHC. Here is a link to the instructions in the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlash
As far as the keyboard orientation you could search in the rom's thread for any reference to it or just flash the rom and see for yourself.

KK13 said:
No you don't have to take everything off the card. Make sure your card is 2gig or smaller and not SDHC. Here is a link to the instructions in the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlash
As far as the keyboard orientation you could search in the rom's thread for any reference to it or just flash the rom and see for yourself.
Click to expand...
Click to collapse
im confused, does the card need to be 2gb or smaller, not sdhc, to properly do hardspl or general. cause ive read the phone only supports 2gb or smaller microsd. but i have also seen the 16gb or 32gb thread, ive seen others saying about using larger than 2gb cards in their phones. im awaiting the delivery of my phone currently and i have a 4gb microsd i use in my htc excalibur i was planning on using. so im majorly confused as to if im going to be able to use it or not, or if i just need a 2gb to do the intial hardspl then ill be fine w/ my 4gb once i go to a cooked rom.
would greatly appreciate some clarity on this all from someone.

WM05 and bootloader only support 2Gb or less though there is an sdhc patch for WM05.
WM06 had the patch to support SDHC cards from 4Gb up to 32Gb. WM6.1 and WM6.5 are also SDHC compliant.
You need a 2Gb or less sd card to flash an OS or different SPL as the bootloader only supports 2Gb or less. Its not upgradeable.
Now that everythings clear as mud,
Cheers...

You could also pick up a 1 gig (or even a 512meg) card on the cheap to do your flashing, and use the 4 gig for your everyday storage in the phone. Then have the best of both worlds!

psylink said:
im confused, does the card need to be 2gb or smaller, not sdhc, to properly do hardspl or general. cause ive read the phone only supports 2gb or smaller microsd. but i have also seen the 16gb or 32gb thread, ive seen others saying about using larger than 2gb cards in their phones. im awaiting the delivery of my phone currently and i have a 4gb microsd i use in my htc excalibur i was planning on using. so im majorly confused as to if im going to be able to use it or not, or if i just need a 2gb to do the intial hardspl then ill be fine w/ my 4gb once i go to a cooked rom.
would greatly appreciate some clarity on this all from someone.
Click to expand...
Click to collapse
You need a smaller than 2gig card for flashing. Everything else you can use your 4 gig card. (As Ultramag69 and Boog321 say) The original question was to do with flashing hardspl or roms only.

KK13 said:
You need a smaller than 2gig card for flashing. Everything else you can use your 4 gig card. (As Ultramag69 and Boog321 say) The original question was to do with flashing hardspl or roms only.
Click to expand...
Click to collapse
HardSPL only needed to install once, after that you can install whatever ROMs you like many times.

True, but if you use the sd card method to install roms you will still need a 2Gb or less sd card...

ultramag69 said:
True, but if you use the sd card method to install roms you will still need a 2Gb or less sd card...
Click to expand...
Click to collapse
Hi Ultramag
I have a problem installing with sdcard.
Have followed the Wiki, have discussed with you previously, Boog and anagarika still no solution. I have elaborated step by step what I did in separate thread.
Do you mind have a look and advise some?
http://forum.xda-developers.com/showthread.php?t=316726&page=34

StefanHou said:
Hi Ultramag
I have a problem installing with sdcard.
Have followed the Wiki, have discussed with you previously, Boog and anagarika still no solution. I have elaborated step by step what I did in separate thread.
Do you mind have a look and advise some?
http://forum.xda-developers.com/showthread.php?t=316726&page=34
Click to expand...
Click to collapse
Did you try formating the SD card on a desktop (or laptop) computer and not phone with Memaid?? Maybe that has something to do with it. Is it a 2gig card or less than 2 gig??

As KK13 said, try a pc to format the card as the steps are right.
Double check that the .nbh is named hermimg.nbh as I know of at least 2 people who named it herming.nbh, small mistake but a critical one.
Remove and insert the sd card then reboot to tri-colour screen. Might do something.
But I strongly recommend using the PC to format the sd card FAT32.
Cheers...

ultramag69 said:
As KK13 said, try a pc to format the card as the steps are right.
Double check that the .nbh is named hermimg.nbh as I know of at least 2 people who named it herming.nbh, small mistake but a critical one.
Remove and insert the sd card then reboot to tri-colour screen. Might do something.
But I strongly recommend using the PC to format the sd card FAT32.
Cheers...
Click to expand...
Click to collapse
Onya dude .. you have a better way with words !!

ultramag69 said:
As KK13 said, try a pc to format the card as the steps are right.
Double check that the .nbh is named hermimg.nbh as I know of at least 2 people who named it herming.nbh, small mistake but a critical one.
Remove and insert the sd card then reboot to tri-colour screen. Might do something.
But I strongly recommend using the PC to format the sd card FAT32.
Cheers...
Click to expand...
Click to collapse
OK, will find SDconverter and try the suggestion, thx KK and Ultramag

*Newbie* Custom ROM Flashing Guide​
Just follow the steps start from 1. Don't skip step unless it is an optional step.
PC Requirement: Windows XP, ActiveSync [Don't try to flash with Vista if you are new], 7zip Installed (Google it)
Connect your device to your computer and make sure the ActiveSync icon appeared on your phone before proceeding. 50% or above bettery is a must. Your phone won't charge when flashing.
1. HardSPL (A Big Big Must)
I asume you are using the original ROM from manufacture as HardSPL won't work with custom ROM.
Download HardSPL V7 from here. Unzip the whole things. Execute the "RUUWrapper" thing and select "Force Using SSPL". Check all the boxes in all the steps and continue with updates. Look at your phone and press "Yes" to everything that prompted. Then your phone will restart in Tri-Color mode [a.k.a bootloader] and start flashing HardSPL.
In this case if any errors appear on your computer screen before the update progress start, soft reset your phone, let it boot into Windows and start RUUWrapper again.
If error appear during flashing progress, then you might in deep hell. Try not to worry. Manually put your device into bootloader (Hold On/Off Btn + Left OK Btn, then push the soft-reset btn). Then start the RUUWrapper again.
End of the step you should see 'HardSPL 2.10Olipro' in bootloader mode.
2. Radio Flashing *Optional*
You can choose not to flash your Radio Stack if you satisfy with the existing. Additional, Radio Stack flashing is the main cause of device bricking (the death of your device)
Choose and download your Radio ROM here. Do some research about the Radio ROM that fits you and your country. Recommended the latest 1.56.70.11. Unpack everything and you will see something similar to HardSPL (RUUWrapper). Don't run RUUWrapper this time.
Let's do the safe way. Format your MicroSD card into FAT32 (Kill yourself if you don't know). Then copy the RUU_signed.nbh into your MicroSD. Then rename RUU_signed.nbh to hermimg.nbh. Put your MicroSD into you phone.
Manually put your phone into bootloader mode. Then a different screen with grey background should appear shortly. Press On/Off btn to start flashing. After the process done (it will tell you when it is done, don't try to judge yourself if you feels that 50% is done), soft-reset your phone.
During flashing, put your phone aside and enjoy your coffee. Don't touch it before it ends as this is dangerous. Don't ever fail radio flashing. Careful, careful and careful.
End of this step, you should see R 1.56.70.11 during Windows Boot.
3. Custom ROM Flashing
First, download Dopod 838 Stripped ROM. Then unpack it. Delete your previous hermimg.nbh in MicroSD which you use to flash Radio Stack. Then copy RUU_signed.nbh from Dopod 838 Stripped ROM to your MicroSD and rename it to hermimg.nbh. Put your device into booloader and start flashing like how you flash you radio rom. After it done, give your device a Hard-Reset (Hold Left + Right softkey and press Reset. Slide you keyboard then press R and SPACE). This official ROM from Dopod is very important which need to be flashed before you flash your custom ROM.
Then the last step is get your custom ROM loaded. Download custom ROM from this forum (Recommended from TAI_sw or JoshKoss).
Then simply follow the steps in Dopod 838 Stripped ROM Flashing.
(Then copy RUU_signed.nbh from Custom ROM to your MicroSD and rename it to hermimg.nbh. Put your device into booloader and start flashing like how you flash you radio rom. After it done, give your device a Hard-Reset (Hold Left + Right softkey and press Reset. Slide you keyboard then press R and SPACE).)
Yes. I have grammar mistakes. Sorry!
That's your ROM and don't expect every ROM is stable. You will see some bugs in Custom ROM. Post your bugs at their own thread.
Anything just PM me.
Thanks
-Ziv-

zivkong said:
*Newbie* Custom ROM Flashing Guide​
Just follow the steps start from 1. Don't skip step unless it is an optional step.
PC Requirement: Windows XP, ActiveSync [Don't try to flash with Vista if you are new], 7zip Installed (Google it)
Connect your device to your computer and make sure the ActiveSync icon appeared on your phone before proceeding. 50% or above bettery is a must. Your phone won't charge when flashing.
1. HardSPL (A Big Big Must)
I asume you are using the original ROM from manufacture as HardSPL won't work with custom ROM.
Download HardSPL V7 from here. Unzip the whole things. Execute the "RUUWrapper" thing and select "Force Using SSPL". Check all the boxes in all the steps and continue with updates. Look at your phone and press "Yes" to everything that prompted. Then your phone will restart in Tri-Color mode [a.k.a bootloader] and start flashing HardSPL.
In this case if any errors appear on your computer screen before the update progress start, soft reset your phone, let it boot into Windows and start RUUWrapper again.
If error appear during flashing progress, then you might in deep hell. Try not to worry. Manually put your device into bootloader (Hold On/Off Btn + Left OK Btn, then push the soft-reset btn). Then start the RUUWrapper again.
End of the step you should see 'HardSPL 2.10Olipro' in bootloader mode.
2. Radio Flashing *Optional*
You can choose not to flash your Radio Stack if you satisfy with the existing. Additional, Radio Stack flashing is the main cause of device bricking (the death of your device)
Choose and download your Radio ROM here. Do some research about the Radio ROM that fits you and your country. Recommended the latest 1.56.70.11. Unpack everything and you will see something similar to HardSPL (RUUWrapper). Don't run RUUWrapper this time.
Let's do the safe way. Format your MicroSD card into FAT32 (Kill yourself if you don't know). Then copy the RUU_signed.nbh into your MicroSD. Then rename RUU_signed.nbh to hermimg.nbh. Put your MicroSD into you phone.
Manually put your phone into bootloader mode. Then a different screen with grey background should appear shortly. Press On/Off btn to start flashing. After the process done (it will tell you when it is done, don't try to judge yourself if you feels that 50% is done), soft-reset your phone.
During flashing, put your phone aside and enjoy your coffee. Don't touch it before it ends as this is dangerous. Don't ever fail radio flashing. Careful, careful and careful.
End of this step, you should see R 1.56.70.11 during Windows Boot.
3. Custom ROM Flashing
First, download Dopod 838 Stripped ROM. Then unpack it. Delete your previous hermimg.nbh in MicroSD which you use to flash Radio Stack. Then copy RUU_signed.nbh from Dopod 838 Stripped ROM to your MicroSD and rename it to hermimg.nbh. Put your device into booloader and start flashing like how you flash you radio rom. After it done, give your device a Hard-Reset (Hold Left + Right softkey and press Reset. Slide you keyboard then press R and SPACE). This official ROM from Dopod is very important which need to be flashed before you flash your custom ROM.
Then the last step is get your custom ROM loaded. Download custom ROM from this forum (Recommended from TAI_sw or JoshKoss).
Then simply follow the steps in Dopod 838 Stripped ROM Flashing.
(Then copy RUU_signed.nbh from Custom ROM to your MicroSD and rename it to hermimg.nbh. Put your device into booloader and start flashing like how you flash you radio rom. After it done, give your device a Hard-Reset (Hold Left + Right softkey and press Reset. Slide you keyboard then press R and SPACE).)
Yes. I have grammar mistakes. Sorry!
That's your ROM and don't expect every ROM is stable. You will see some bugs in Custom ROM. Post your bugs at their own thread.
Anything just PM me.
Thanks
-Ziv-
Click to expand...
Click to collapse
Hi Ziv
I have flashed over twenty or more cooked ROM, and they are successfully done through Active Sync. As you see in my signature, My IPL is 1.04 and my SPL is 2.10 Olipro.
I have also followed Ultramag and KK suggestion to format the SDCard using PC. And still stuck in bootloader (3 colors) and one more: it states 'Serial' in the bottom color (white).
I also bought the new 1GB SDCard, but the problem persit.
So, is there any other suggestion to try?

StefanHou said:
Hi Ziv
I have flashed over twenty or more cooked ROM, and they are successfully done through Active Sync. As you see in my signature, My IPL is 1.04 and my SPL is 2.10 Olipro.
I have also followed Ultramag and KK suggestion to format the SDCard using PC. And still stuck in bootloader (3 colors) and one more: it states 'Serial' in the bottom color (white).
I also bought the new 1GB SDCard, but the problem persit.
So, is there any other suggestion to try?
Click to expand...
Click to collapse
Ultramag, KK13, Boog & Zocster
Have tested using SD Converter and formatted it with PC, still no use. In the boot loader screen, I stucked with 'Serial' in the white bar. Is this meaning something to you? Any other work around?

Man, I don't have a clue. The only issue I ever encountered was thinking my card was formatted fat32 when it wasn't.
I think this is now beyond me.

StefanHou said:
Ultramag, KK13, Boog & Zocster
Have tested using SD Converter and formatted it with PC, still no use. In the boot loader screen, I stucked with 'Serial' in the white bar. Is this meaning something to you? Any other work around?
Click to expand...
Click to collapse
Well now .. you've got me too. I have only had "serial" showing in the boot loader once and it was because I had the wrong sd card in with no HERMIMG file. Once I put the right one in with the file and reset the device it was ok. All I would suggest is to do a Hard reset and follow all the steps again one by one, triple checking everything. Maybe write everything you do down and post it back here.

Also check your spelling of hermimg.nbh as a simple error will screw up everything...
Also put sd card in then reset to bootloader, hold in all the buttons - ok, power and reset with stylus, until the bootloader comes up.
Cheers...

KK13 said:
Well now .. you've got me too. I have only had "serial" showing in the boot loader once and it was because I had the wrong sd card in with no HERMIMG file. Once I put the right one in with the file and reset the device it was ok. All I would suggest is to do a Hard reset and follow all the steps again one by one, triple checking everything. Maybe write everything you do down and post it back here.
Click to expand...
Click to collapse
KK13, Boog and Ultramag
OK this is what I did last night:
1. Flashing to the shipped AT&T Stripped ROM
2. Having it reflashed with the HardSPL V7 (to ensure the file is non corrupted, I re-downloaded it from some links in some thread and check the file size, they are all the same )
3. Reformating my SD Card with PC for FAT32;
4. Copy the nbh file and rename it with HERMIMG.nbh (recheck three times and I think I get it right. btw, is there any different to write it in capital? );
5. Press OK and Power, then stick the reset button.
6. Go to the boot loader (with 'Serial' on ht white screen)

From Android to Win 6.5

Hi, I installed android to my touch but now I'd like to go back to window mobile. I haven't been able to figure out how to flash it back to windows... any help?
Thanks

reflash a winmo build.

I'd love to reflash to a winmo build, but i just don't know how.

search. read the wiki's @ the top.
why go back anyway?
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

Long story short. i'm trying android again to see if the newest build has better battery life. the last build couldn't hold a charge long enough to make it worht while as a phone.
The only way i've ever gotten android to get data after being flashed has been to get it working in windows first and then installing android.
i've read and searched for a step by step on how to do this and i just haven't been fruitful.

just download and flash one of the 6.5 builds....there's a very informative guide on how to

The guides that i see want me to establish an active sync connection to flash the device but I have android installed and i cant' establish an active sync connection. I think thats my major hangup. Is there a way to flash it from the memory card?

not that Im aware of.. my have to RUU back to stock and start over.
look here for sprint rom http://shipped-roms.com/shipped/Vogue/

That would be just fine too... i still don't know how to do it. When i run the rom update utility it gives me a connection error.
Edit: I realize that i'm being vague. Let me try to fill in the gaps. I am putting my phone into the bootloader mode, hooking it up to my PC via USB and running the Rom update Utility with a custom rom. The phone has been unlocked so it really shouldn't have any trouble..
What am I doing wrong?

moperist said:
The guides that i see want me to establish an active sync connection to flash the device but I have android installed and i cant' establish an active sync connection. I think thats my major hangup. Is there a way to flash it from the memory card?
Click to expand...
Click to collapse
Put your phone in Bootloader Mode by pressing the Camera and Power buttons and then the Reset button all at the same time.
Then make sure you have a radio of 3.4x or above... If not Flash back to a new stock Rom and then follow the threads you were just reading.
If you radio is good go and Download one of the ROMS here on this forum.
Happy Flashing!
P.S Please Ask your Questions in the Q and A section of this forum.

moperist said:
That would be just fine too... i still don't know how to do it. When i run the rom update utility it gives me a connection error.
Edit: I realize that i'm being vague. Let me try to fill in the gaps. I am putting my phone into the bootloader mode, hooking it up to my PC via USB and running the Rom update Utility with a custom rom. The phone has been unlocked so it really shouldn't have any trouble..
What am I doing wrong?
Click to expand...
Click to collapse
Make sure it says usb at the bottom of the bootloader.

Ok, I found out the problem... i'm retarded.
Thank you for your patience. Sorry to have been a bother and put this in the wrong place.

moperist said:
Ok, I found out the problem... i'm retarded.
Thank you for your patience. Sorry to have been a bother and put this in the wrong place.
Click to expand...
Click to collapse
No problem.
Glad you got it figured out!

moperist said:
Ok, I found out the problem... i'm retarded.
Thank you for your patience. Sorry to have been a bother and put this in the wrong place.
Click to expand...
Click to collapse
No bother....learning experience.

so what was the problem?

so what was the problem because I'm trying to get from android to win 6.5 and the computer is saying that my xv6900 isn't hooked up even though on bootloader it says usb...any help would be great

How to Flash a Vogue without ActiveSync
How to Flash a Vogue Without ActiveSync
A method so easy my Mother could do it.
Not suggesting there's anything wrong with my mother, just that she's not all that technically oriented.​
Here's an easy way to flash your HTC Vogue without using ActiveSync. It would likely be a great method to use if you had many Vogues that all needed to be updated as well. Works great for those not using Windows, as well.
Look around for a Transflash (aka MicroSD) card, one that you can erase, 2GB or less.
Use your Windows machine to make sure it's freshly formatted as FAT32]
Copy the ROM you want to flash to the card.
Rename the file you just copied to VOGUIMG.nbh If you are flashing a different model, you need to be sure you have the right file name for it. I think the pattern is the first 4 letters of the model name with IMG.nbh after it, but if it doesn't work, don't blame me,
Put card in phone.
Enter bootloader mode by holding the CAMERA and POWER buttons, while pressing the RESET button in the little hole in the bottom of the phone. (don't bother to connect it to your computer)
Enjoy a caffinated beverage of your choice, or an alcoholic beverage of your choice, or heck, a nice tall glass of cool water while you wait.
Watch as your phone automagically flashes itself!
Congratulate yourself on a job well done.
This is what I'm going to use from now on for flashing with a Mac or Linux. For those addicted to flashing, you can even take a collection of cards with you. I'm not yet sure if you can have multiple ROMs on one card, and just rename the one you want to flash or not yet, but I'll likely find out soon.
ATTENTION:
Missing any of these will make it NOT WORK:
Card must be normal SD, not SDHC or XDHC. No bigger than 2GB
Card must be formatted with FAT32. They often come formatted FAT16 or plain FAT, and a previously-used card could have just about any format on it -- NTFS. HPFS. HFS+. EXT3 -- Format it right to be sure.
Be sure you have the right name. I've heard that CaSe cOuNtS -- the name above has been cut/pasted from a working reflash card.
There is no #4.
Have fun!
Oh yes, just in case:[Lawyer]You are responsible for your own actions. This information is provided as a public service, and I wave all responsibility for it's correctness or how it is used. If you brick your phone, it's your fault. If your phone explodes, not my problem, but I'd like the remains.[/Lawyer]

Gr1zz said:
How to Flash a Vogue Without ActiveSync
A method so easy my Mother could do it.
Not suggesting there's anything wrong with my mother, just that she's not all that technically oriented.​
Here's an easy way to flash your HTC Vogue without using ActiveSync. It would likely be a great method to use if you had many Vogues that all needed to be updated as well. Works great for those not using Windows, as well.
Look around for a Transflash (aka MicroSD) card, one that you can erase, 2GB or less.
Use your Windows machine to make sure it's freshly formatted as FAT32]
Copy the ROM you want to flash to the card.
Rename the file you just copied to VOGUIMG.nbh If you are flashing a different model, you need to be sure you have the right file name for it. I think the pattern is the first 4 letters of the model name with IMG.nbh after it, but if it doesn't work, don't blame me,
Put card in phone.
Enter bootloader mode by holding the CAMERA and POWER buttons, while pressing the RESET button in the little hole in the bottom of the phone. (don't bother to connect it to your computer)
Enjoy a caffinated beverage of your choice, or an alcoholic beverage of your choice, or heck, a nice tall glass of cool water while you wait.
Watch as your phone automagically flashes itself!
Congratulate yourself on a job well done.
This is what I'm going to use from now on for flashing with a Mac or Linux. For those addicted to flashing, you can even take a collection of cards with you. I'm not yet sure if you can have multiple ROMs on one card, and just rename the one you want to flash or not yet, but I'll likely find out soon.
ATTENTION:
Missing any of these will make it NOT WORK:
Card must be normal SD, not SDHC or XDHC. No bigger than 2GB
Card must be formatted with FAT32. They often come formatted FAT16 or plain FAT, and a previously-used card could have just about any format on it -- NTFS. HPFS. HFS+. EXT3 -- Format it right to be sure.
Be sure you have the right name. I've heard that CaSe cOuNtS -- the name above has been cut/pasted from a working reflash card.
There is no #4.
Have fun!
Oh yes, just in case:[Lawyer]You are responsible for your own actions. This information is provided as a public service, and I wave all responsibility for it's correctness or how it is used. If you brick your phone, it's your fault. If your phone explodes, not my problem, but I'd like the remains.[/Lawyer]
Click to expand...
Click to collapse
i do as yousay after i put it in bootloade mode it says loading for a split seconde then goes back to bootloader i need help i have android with no data i read that i need to reinstill wm get data working their then re install android i cant get wm back on this phone im going on 3 days trying to flash this yes its unlocked

Having problems to install android

hi there
i really need your help. i'm trying to install android on my HTC TyTnII. But i'm having problems to install.
can you please help me to get Android run on my Kaiser?
Right now i'm running the windows mobile 6.1. I want to install Android as a secondary OS.
i followed this installation guide.
androidonhtc.com/wiki/Installing_Android
1. I went to this link to download files.
androidonhtc.com/wiki/Latest_Builds_%28Kaiser%29
2. I downloaded the basefiles-20091116.zip
vogue-android.googlecode.com/files/basefiles-20091116.zip
3. Unzipped this zip file. Renamed the default-kaiser.txt to default.txt and moved the whole folder "android" to my storagecard.
4. then i downloaded the haretinstall.zip and unzipped that file as well. I moved the folder "andboot" to my storagecard.
sourceforge.net/projects/androidhtc/files/2010-02-20/haretinstall.zip/download
5. then i downloaded the polymod_2.1g.zip and unzipped that file. I moved the file "androidinstall.tar" to my storagecard as well.
ponack.net/poly/2.1g/polymod_2.1g.zip
6. i clicked than on "haret.exe" and clicked on Run. the android started to load but then it stops. It gives me this error.
--------
....
Checking for partition...
s2fsck 1.41.4 (27-Jan-209)
ext2fs_check_if_mount: No such file or directory while determing whether /dev/block/loop0 is mounted.
/dev/block/loop0 was not cleanly unmounted. check for ced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/loop0: 11/65536 files (0.0% non-contigous), 10335/262144 blocks
losetup: /dev/block/loop1: No such file or directory
Failed
Failed to find system.im on SD Card
/bib/sh: can't access tty1 job control turned off
/ #
--------
Can anyone help me out to solve the problem?
Do i need to do some partition? if yes...how can i do it? i'm using a windows xp OS.
This is how my SD-storagecard looks like:
/[android]
/[android]/[andboot]
/[android]/androidinstall.tar
Thank you for your support.

The androidinstall.tar should be in andboot folder, with all the haret files. andboot must be in root of SD card.
/
/andboot
If you were installing to nand it'd be :
/KAISimg.nbh
/andboot
You do not need to partition the SD card, just make sure it is formatted FAT32, not FAT

hi zenity
thanks for the response. I did what you said. Still having the same problem with the same error message.
how do i check format of my sd card? i've never formated it before. it's the original sd card.

Depends if you have an sd card reader and adaptor for micro-sd, if you do you can just format it in windows.
It's likely that it's formatted FAT, most new pre-formatted micro-sd are formatted FAT as standard, how are you transferring files to the sd at the moment?

i connected my htc with microsoft activesync then transfered the files via windows explorer.
i'm still struggeling to get android run on my device.
are those steps correct? or am i doing something totally wrong?
those installation guide are too complicated for me. the instructions are mostly for total replacement of the OS. But i would like to keep my windows mobile because of tomtom navigator. I want to make both OS run with Dual booting function.
if you are so kind...can you please guide me to make this run? I'll be thankful for that.

Best way to format an SD card is to use a card reader and micro-sd adaptor, I've never tried to format an SD with winmo or through activesync, so I'm not sure how easy that is.
I have transferred the files via activesync before, and that works fine, but your SD card must be FAT32, winmo probably does not know the difference, I'm sure there must be a way to format the card FAT32 in winmo, but I cannot think of one, I'll look into it though. I think total commander is able to show what type of format the sd card is, but don't know if it's able to format it.
All the Haret files plus the androidinstall.tar must be in the andboot folder on the SD card, you do not need any other files or folders on the card, but it should not matter if there are any.
You will need an SD card of at least 1GB, 2Gb is better.
I know the guide is meant for Nand install, but does show the installer screen part clearly, and the install procedure is the same for nand and haret, and shows the installer screen you should see when installing on FAT32, (haret).

Download Card Export or WM5Storage to mount the card. Then format it like you would do with a usb stick.

me too
I get the same error.
I have haretinstall and androidinstall.tgz in the /andboot folder.
I renamed default.txt to default.txt.no
I renamed default-kaiser.txt to default.txt
I edited default.txt to point to zImage-eclair
I tried with the regular zImage
I wait till it ask for dpad or vol up button then I press and hold dpad. It never recognizes? Or thats my guess from what has been said here.
right clicking on the drive from within windows using a card reader it says fat32.
When I press dpad it prints a ^@ to the screen, ironically it does the same key for ok. I don't see how I can hold down the vol up/down key cause its a jog wheel? Should I try dpad down?

Volume Up Is the RIght SOftKey. FOr some build only that work.

@zenity: i manage to format my miniSD to fat32. it was fat before. but the problem is still there..does anyone else know how to deal with this?
as tyler51773 already mentioned..i fi start the "haret" which is stored in "andboot" folder it request to hold down the vol button. although i pressed the vol. button,,,it still doesn't work. getting the same error message like tyler51773
seems like i'm totally lost. someone please help!!!

can anyone write down a clean instruction how to install the kaiser on SD incl. the right link (instead of telling users to find out the right one) without wiping out the windows mobile. this would be more helpful to us.
i'm sure there are other users who might be interested in this too.
thankx

When you run Haret and see scrolling text, immediately hold down the d-pad or vol button. Don't wait for it to ask.

hi all,
i have the same problem. the instructions seems to be bad. i cant run it and tried many things. in install-instructions says "androidinstall.tar" but download is androidinstall.tgz.
i don't know if its a big mistake, but someone should make a new "correct" instruction with correct files. maybe it then will be worked.
i also stuck on "can't found system.img"
greetz an sorry for my english

@dukennukemx: i did what you said. no improvement.
@lenzen24: i'm 100% with you!

i tried again,
but also failed on find system.img on sd-card
hope someone has a solution, becaused i woudn't flash a image over my wm6.5.
greetz lenzen

progress
The right soft key button worked, (i.e. the one right above the mail, to the left of the red phone to the right of the dpad just to be perfectly clear for anyone else).
I got the menu, and then it said unbalanced irq 102, unbalanced irq 86?, unbalanced irq 87? it froze then rebooted.
Second try, I hold down the right softkey after i see the penguin. I get the menu with the ok warning. I try all the buttons the warning stays up. I open up the keyboard. I press enter I now am in the menu.
The install option is missing? I have 1. fix permisions. (vs it saying install?) The dpad doesn't seem to work. I have 7 options. The last option is quit. The 6th one is recovery. 5 is wipe. As I'm staring at errors and not the menu I forget which the rest are. I remember seeing a backup/restore. Then their is wipe. Their was also the wipe cache options.
When I try to navigate the menu its a no go. The only real options I have is fix permissions. That leads to errors due to a missing system.img that hasn't been made yet? And then their is quit. I get to quit using the left opt key, and I can get to fix perms using the right opt key. If i open up the keyboard and try every key the only key the menu responds to is enter. I also tried w/ fn lock, but not shift, no responce to the arrow keys was a bummer. When I accessed a shell I can atleast confirm that qwerty mapping was right, but didn't hang out long enough to see the rest of the keymap.
Should I try zimage-eclair? I will of course do that at some compulsive moment, but hey, maybe I wont, or maybe I will and say I haven't yet - maybe I already have {knowingly or not}.. do I need some options in my default.txt? Should I try a different androidinstall? this is polymod-2.1g
This is actually a Tilt vs a Kaiser.
Thanks for the speedy replies and help!
Tyler

Problems with the install option not appearing are usually caused by not formatting the sd as FAT32, or a wrongly set up sd card, for haret installs, everything goes in andboot folder, for nand, androidinstal.tar, (or tgz), in andboot folder, kaisimg.nbh in root, the install instructions are clear enough, they are just not as easy to follow for inexperienced users, and tilt and kaiser are the same thing, if you look under the battery it will say 'kaisxxx'.

zenity
Your last post you can tell someone got under your skin...
I'm a fairly experienced user. I have had troubles installing android since the nand came along.
I feel that if I were willing to nuke my winmo it would be installed. my primary objective with this phone is voip. I'm hoping sipdroid gets fixed or the reports of sipagent working better than sipdroid are true. I'd like to investigate that. I'm poor and with winmo I pretty much make free calls. Albeit I have reliability issues, and I have lots of things i should script to make things work which is all the more motivation to move over. Especially with winmo7 stripping voip out completely [rumor mill]. Anyhow, I am not willing to nuke my winmo. It's quite cryptic to call the volume key, the volume key, when on the kaiser its the right opt key. Perhaps the problem is that I am running a tilt vs a kaiser, another cryptic difference? good thing we don't have a lot of sidekicks running around either. Anyhow. My card is formatted right. I even tried another almost virgin 2gb card, never been formatted but did have a raw filesystem that was only used on sundays while driving to church, it was freshly formatted with fat32 and still it was a no go.
I also just tried myns build. I get an install option, when I press enter it warns me that it is about to delete my all my stuff. So I would say no, but after feeling wrath I tried to say yes, but of course I can't navigate nothing I push will let me choose yes. So I safely run with no.
If I did have a dpad where it says backup data could I backup my winmo? That makes me feel good I've always wanted that. That feature alone would make my day as it would let me finally upgrade my sacred voip setup w/o fear of having to find all those little f!&@&# registry entries again.
Enter does a carriage return in shell? New line in any event..
Dpad/Ok on the front both print a ^@, so does the side ok button, and so does the keyb ok button. {so does; Winkey, MailKey, GreenPhone{send}}
Dpad/Keyb/Jog Up does a ^[[A
Dpad/Keyb/Jog Down does a ^[[B
Dpad/Keyb Left does a ^[[D
Dpad/Keyb Right does a ^[[C
Left Opt: ^[[26~
Right Opt: [BLANK]
e does ^[[1~
red phone{end} ^[[4~
PwrOff ^[[4~
Admittingly this is using myn's androidinstall.tar as i just got done trying that, not sure if the keymap would vary at all (I highly doubt that). Anyhow I also did see the sdcard mounted. I cd'ed into it and did an ls. Everything showed up. It was mounted rw.
Let me know if I can do anything else to speed along the development.
Hate to ask a dumb question? But why not continue to distribute the sqsh builds if they're so much easier to test out for winmo users? Isn't that what the installer is trying to do is process the androidinstall.tar file into either one of three options one of which is cacheable - the sqsh files?
But still, I'd love to hear I now have a back up option..
Zenity thank you for your hard work and even diligent support! I totally get the stress that comes with messing with software for long periods of time. If it helps we can sacrifice a user to the /dev/null ? Hope you're feeling better.

tyler51773 said:
Your last post you can tell someone got under your skin...
Zenity thank you for your hard work and even diligent support! I totally get the stress that comes with messing with software for long periods of time. If it helps we can sacrifice a user to the /dev/null ? Hope you're feeling better.
Click to expand...
Click to collapse
Lol, sorry if it came over like that, I was typing it at a cafe on my kaiser, so I didn't spend as much time as I usually try to on a post, I usually try to structure them as carefully as possible to avoid misunderstandings
To be more accurate, I feel that the present sets of install instructions do assume a lot more knowledge than a lot of those new to Android actually have, this is not a disrespectful statement, simply that most builds have grown and changed so much, and the users who have been using them have also grown in specific knowledge of the install process, this, naturally, has led to some instructions assuming that those users all know the basics, which of course would be true if there were no new users.
It is difficult to produce a generic set of install instructions, since there are still a number of ways to get android onto our devices, and some builds are designed for other hardware originally, myn's for Vogue for example, so the install instructions tend to be more focused on those devices.
As far as the actual installer is concerned, the only time you will wipe winmo is if you have already flashed to nand, running via haret will not wipe winmo, the warning about wiping the system, or data, applies only to the Android build you are installing.
The present installer will process the androidinstall.tar or .tgz and install either to nand, if that is available, EXT2 partition, again, if available, or FAT32 partition, most commonly known as SD card or Haret install, the actual installation will then unpack the tar file to the proper destination, and on haret will produce a system and data img file, I'm unsure if it produces a sqsh file, since it's been a long while since I ran from anything but nand, but I do understand the confusion the install produces for those wishing to stay with winmo, and would prefer that it was clearer, but as with most of android development, once it works, development ceases until it breaks
Rest assured, unless you flash to nand, your winmo should be completely safe, I have not yet seen anyone wipe winmo using the SD/Haret method, not in all the time that we have been running Android on our kaisers.
I'm confused now however, I was always under the impression that the Tilt was merely another kaiser model, and unless you have forgotten to edit the default.txt file to reflect your hardware, the keypad/dpad should function properly, which as far as the escape sequences you have posted, would seem to be the case, ( dpad centre should give ^@ in console etc), so navigating the installer should be as easy as pressing the left, right up or down keys, followed by centre to choose options.
What I am now tempted to do is reflash my secondary Kaiser to winmo stock, and try a few haret installs just to check out things, since most of the above is mainly from memory, although a lot of the Nand install procedure is similar, may not be identical.
Sacrifices will not be necessary, however offerings may be made of caffeine, and/or chocolate, this may help me continue to function in my role as helpful user, and reduce my occasional visits to the mild irony I call my sense of humour

cool
I feel you about short emails making one sound bad! I made that mistake a few times. I actually hate email. I wrote this very funny email to my advisor, he liked it, and forwarded to his boss - just communicating, not to share a laugh or to complain, but to answer a question he did not know; atleast I was told that as I was then later forced to ask him 'did I make you mad?'. Anyhow I got chewed out for professionalism by the department chair which is not the way to a elect a major. Funny enough, I had decided writing funny was the way to go after i had peeved someone off for writing short almost angry sounding emails. In short I hate email/communicating via text.
I was thinking about the whole solution thing. If i need to do a key remap maybe we could just write up a shell script and I could execute it from /sdcard and then re-execute the installer ? unknown.sh??
Also, if you produce some img files what's to stop you from sharing those? I'd totally be willing to try it, maybe it'll work, maybe it'll break wifi calibration? who knows?
Bug found:
http://code.google.com/p/vogue-android/issues/detail?id=124#makechanges
set cmdline "ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=1"
just tried to change board-kaiser-keypad.atttilt=1 with no results
Just my .02c

T-mobile TP2 wont boot - "can't access tty; job control turned off"

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'm ready to throw it out the window

Hi all.
I've been lurking on the Kaiser forum for some time and have found a wealth of very useful info... Except when it comes to running Android via HaRET.
Yes, I know there have been a million questions. Yes, I have seen many of them inserted into what should be straight developer/bug threads. Even so, the "answer" to my issue doesn't work.
From "How to run Polymod’s AWESOME 2.1 Eclare Build and Updates":
Section 2 - Errors and FAQ's
===============================
#1 Failed to reach system.img on SD Card
If you see the error message below:
“Failed to reach system.img on SD Card” then you did not hold the button down correctly. You are seeing this because you missed, disabled or bypassed the install menu.
Click to expand...
Click to collapse
NOT TRUE. I have booted more than 20 times pressing/holding the center button at different times and with different intensities. No matter what I do, I get this blasted error message. Any solution other than the stock one listed above would be cause for hero-worship.

This error can have a number of causes, namely the file system, is the SD card formatted FAT32, ( some cards come formatted FAT16 as standard), or having the SD card set up incorrectly, for haret you need to have all files in the andboot folder.
Provided haret starts correctly, which it is since you cannot reach the post-install stage unless it is booting the kernel, then the only part of the procedure that can go wrong is the installer.
The only things I can think of that would cause the installer not to start is either the card itself, or problems with the andboot folder and/or the files inside.
The only advice I can give at the moment is to calmly start haret, watch the scrolling text until you get the pause, and the 'press d-pad to start installer' text.
At that point if you press the d-pad centre button, and hold it you will see '^@' on the screen, if you do not see the '^@' or see anything else then the installer cannot start, it will only respond to the correct key.
If you see anything else it is possible you have incorrectly set an option in default.txt file.
If all this still fails, then report back with anything you find, I may have some other ideas based on what you find out

+1 on zenitys answer and in addition you are using the correct basefiles to run haret?

Try using the screen as a giant keypad and pressing and holding the center of the screen.
EDIT: Scratch that... It only works as a keypad once the menu is up. Sorry.

that works?
Seriously?
I mean really?
No it bloody does not, ( lol, can't believe i actually tried it ).....

i had this problem and pulled my hair out, eventually i downloaded a different haret basefile and copied to my SD and bam it worked, sorry but i'm i soon after went to nand and erased the haret files so i don't have them anymore.

zenity: Yes, it is FAT32 and yes all files are in andboot. I do see a '^@' when I press the center button if I press it when prompted. If I press and hold as soon as I see Tux, I don't get that character pair. I see a different string of characters if I press one of the other buttons instead. I haven't modified the default.txt file in any way other than to re-name it from default-kaiser.txt.
I am using the files from a haretinstall.zip that I got directly from sourceforge Android HTC project (sourceforge.net/projects/androidhtc/files/... not allowed to post links <_<). The files were under the date 02-13-2010. I have since grabbed two other more current versions of haretinstall.zip and will try them after I post this. I am also using the most current androidinstall.tar and androidupdate.tar from sourceforge, though I have also tried Polyrithmic Eclair 2.1g's androidinstall.tgz.
Thanks all for the replies and I'll try those other haretinstall.zip's while waiting for any other replies.

maybe try a different sd card?
I couldn't get any nbh's to be read off of my 2gb patriot, but when i put in my 16gb sandisk the nbh's worked.
I know this is only marginally related lol, but it's worth a shot?

mr_fosi said:
zenity: Yes, it is FAT32 and yes all files are in andboot. I do see a '^@' when I press the center button if I press it when prompted. If I press and hold as soon as I see Tux, I don't get that character pair. I see a different string of characters if I press one of the other buttons instead. I haven't modified the default.txt file in any way other than to re-name it from default-kaiser.txt.
I am using the files from a haretinstall.zip that I got directly from sourceforge Android HTC project (sourceforge.net/projects/androidhtc/files/... not allowed to post links <_<). The files were under the date 02-13-2010. I have since grabbed two other more current versions of haretinstall.zip and will try them after I post this. I am also using the most current androidinstall.tar and androidupdate.tar from sourceforge, though I have also tried Polyrithmic Eclair 2.1g's androidinstall.tgz.
Thanks all for the replies and I'll try those other haretinstall.zip's while waiting for any other replies.
Click to expand...
Click to collapse
I do remember trying the 2/13 first and that is the one that holding the button did absolutely nothing, it was either 2/14 or 2/20 (those are in my browsing history) that did work for me. It was a "ta dah" moment when the install menu popped up.

deezy7 said:
maybe try a different sd card?
I couldn't get any nbh's to be read off of my 2gb patriot, but when i put in my 16gb sandisk the nbh's worked.
I know this is only marginally related lol, but it's worth a shot?
Click to expand...
Click to collapse
I doubt it, cause its reading the kernel if he is getting the error message. The error message about system.img is because an install hasn't been performed to create a system.img or data.img file on the sdcard.

Actually it's very related, android seems unusually sensitive to SD card issues that winmo simply ignores.
If you have another SD card available then try that, if not then all I can suggest at the moment is reformatting a couple of times, that worked for one of my 2Gb cards that simply would not recognise my NBH files no matter what I did.
An alternative might be to grab kalt_kaffe's zimage from here : http://forum.xda-developers.com/showthread.php?t=660158
this seems to be the best zImage for eclair at the moment. Just download it, put it in andboot with the rest of the haret files, make sure it's named correctly, ( it'll probably need you to delete the zImage file already there anyway, or overwrite if you use a card reader and windows).
Since you are getting the ^@ then the kernel is running properly, that actually only leaves the SD card, the reason you get the other character pair if you press to early is that with some zImages the keyboard may not be set up early enough, which is why I always wait for the pause, never failed me yet.

Maybe... Maybe...
Thanks again all.
It may well be the SD card but a more current set of HaRET basefiles did finally fix the center button issue. I have been able to get android installed but little else. I have a blank screen (with clock, battery and wifi in the top bar) but nothing else.
I'm going to blame this issue particular tar files I used and I will go back and try the Eclaire by Polyrithmic or the one by kallt_kaffe you linked. I didn't really want the Andriod HTC tar files but was using them in an attempt to minimize the variables causing my initial button issue.

If you are going to use polymod may I suggest the 2.1D download linked in my sig, it's only the install.tar, but is pretty stable, and is in fact what I use for my everyday android on my main kaiser.
Since you have a working set of haret files, simply replace the zImage with kalt_kaffe's zImage, replace the installer with poly's 2.1D and you should hopefully be good to go

I tried 2.1d and it locked during the post-install setup. I also tried kalt_kaffe's zImage with both 2.1g and it broke my wifi.
As such, I am back to using 2.1g with the kernel that was originally bundled with it... Even bluetooth seems to work. I can see my lappy but I haven't tried pairing yet. No microphone though as far as I can tell. It'll be awesome once the ethereal developers find a way to make the camera work.
At least now I have something new to play with. I'm eying Warm Donut b/c I like the look but I don't know if I want to undo the working install I have. Never know till you try, right?

I guess this is probably already well-known but my kaiser's camera works under Warm Donut. The pics aren't all that great but it does take them.

If anyone else stops by... I'm having audio problems. I'd had audio problems with all the different Android releases I've tried so far. The main problem is that there is no audio. No alerts, rings or media.
Any suggestions?

mr_fosi said:
If anyone else stops by... I'm having audio problems. I'd had audio problems with all the different Android releases I've tried so far. The main problem is that there is no audio. No alerts, rings or media.
Any suggestions?
Click to expand...
Click to collapse
The way I understand it, that can be affected by your radio firmware... The radio firmware I use without any problems for android is in my sig.
Please post which one you are using, too!

Good call! I hadn't considered my radio version though I have seen numerous posts suggesting that users upgrade... Or at least swap theirs out.
WM6 indicates that my radio version is 1.27.14.09.
Radio 1.27.14.09
Protocol 22.45.88.07h
ROM 1.62.00.00
I'll do a little reading and see if I can't figure out how to swap a new radio (probably the one you're using) in.

Ok that's one old radio, go here : http://forum.xda-developers.com/showthread.php?t=393182, get the 1.71.09.01 linked at the bottom of post #3, it's an nbh file, so just rename it to KAISimg.nbh, put it on SD and flash the same as the Nand nbh, it will not affect anything, just upgrades the radio.

I got the radio nbh and now I am working out how to use nand. Most everything I see is geared toward wiping windows to replace it with android. I don't want to do that yet so I'm trying to parse now to flash this nbh without jacking up my device or the windows that is currently on it.