NBH Help - WinMo 6.5 to Android - Tilt, TyTN II, MDA Vario III Android Development

I have a TyTN II that I flashed WinMo 6.5 onto a while back. Now I would like to put Android on it but am having some trouble.
The bootloader screen reads:
TITA100
SPL-2.47No2Chem Titan SPL EVT
CPLD-9
I can't figure out why it won't let me flash a different NBH via SD or via PC.
Do I need to put HardSPL on it instead? (I've tried -- to no avail).
I've read a lot of threads and tried countless different things but nothing works. When I try from SD it says "no image file". When I try from PC it says "The update utility cannot connect to your PDA phone. Please check that your USB cradle/cable is connected properly between the PC and your PDA Phone."
Please help. Thanks.

By the looks of it you already have HardSPL installed.
What I'd do as a last resort (and what I had to do on my WinMo 6.5 Kaiser, in fact!) is put it into 3-color/bootloader mode:
* Hold Camera + Power buttons together and reset with stylus
and then flash whatever ROM you like onto it via USB. Note that you MUST REMOVE YOUR SD CARD to enter the bootloader.

Alternatively flash a newish stock rom, ( Kaiser_HTC_ASIA_HK_WWE_3.34.721.2.exe recommended, search for this exact filename, it's the last full 6.1 update for kaiser, and has 1.70.xx.xx radio), this will pretty much clean out anything a custom rom has tucked away in little dusty WM corners, I actually prefer to flash from SD, it's faster, and to a large extent safer, no chance of an accidental usb disconnect, of course you must do a little more preperation, but provided you have HardSPL, an sd reader and microSD adaptor then it's real easy.
Grab a handy MicroSD, format it FAT32, (remember to check it's FAT32, not FAT), then get the ruu_signed.nbh from the stock rom, copy to SD, rename to KAISIMG.nbh, then safely remove the SD, (don't just pull it out, that can leave unwritten data in buffers, and corrupt the files you copied).
Then pull the battery out of the kaiser, insert the SD card, replace battery and hold down camera button while you press Power key, this should boot to Bootloader ( tricolour screen) and start up the SD upgrade process, this checks the file, then asks you to press the power button to flash it, it will install, and once 'upgrade complete' shows, pull the battery again, then reinsert and restart.
Once you have a stock rom, go here :http://forum.xda-developers.com/showthread.php?t=680518 and carefully read through the process before continuing from step #4, since you already have HardSPL.
Any problems, just post and someone will probably have the answer

zenity said:
Alternatively flash a newish stock rom, ( Kaiser_HTC_ASIA_HK_WWE_3.34.721.2.exe recommended, search for this exact filename, it's the last full 6.1 update for kaiser, and has 1.70.xx.xx radio), this will pretty much clean out anything a custom rom has tucked away in little dusty WM corners, I actually prefer to flash from SD, it's faster, and to a large extent safer, no chance of an accidental usb disconnect, of course you must do a little more preperation, but provided you have HardSPL, an sd reader and microSD adaptor then it's real easy.
Grab a handy MicroSD, format it FAT32, (remember to check it's FAT32, not FAT), then get the ruu_signed.nbh from the stock rom, copy to SD, rename to KAISIMG.nbh, then safely remove the SD, (don't just pull it out, that can leave unwritten data in buffers, and corrupt the files you copied).
Then pull the battery out of the kaiser, insert the SD card, replace battery and hold down camera button while you press Power key, this should boot to Bootloader ( tricolour screen) and start up the SD upgrade process, this checks the file, then asks you to press the power button to flash it, it will install, and once 'upgrade complete' shows, pull the battery again, then reinsert and restart.
Click to expand...
Click to collapse
I explicitly followed these instructions and it still says "No image file" when in bootloader mode with the SD card in and the image file I extracted from Kaiser_HTC_ASIA_HK_WWE_3.34.721.2.exe renamed to KAISIMG.nbh. It only flashes the message for a split second and then goes back to the bootloader screen.
Is there any way to tell for sure if I have Hard SPL or not?
Is there anything else I can try?
It no longer boots past the second boot screen. Did I brick it?

I ran the following commands via MTTY version 1.42:
set 14 0
task 28 55aa
When it tries to format the device it returns "badblock 1024"
When I run 0 to reboot the device it does not respond.

Not sure what to try next on this. I was able to get the "boot" command to work using MTTY but it would still not boot to WinMo or boot an image file in bootloader mode.
If anyone else has had the bad blocks problem, please let me know how you fixed it.
Sent from my HTC Vogue FroYo using XDA App

Bump
Sent from my HTC Vogue FroYo using XDA App

Have you tried another SD card, maybe the card is bad, also have you checked that is is formatted as fat32? I would try reformatting the card (full not quick) and putting the file back on the card.

Related

XDAtool is recognizing the SD card as 23.35 MB instead of 32

Folks,
I am new to the group.I have XDA which konked off during upgrade to 2003 from 2002 PocketPC version.I am following the below listed AT&T support procedure to recover.
When I try to copy the os image using XDA os image tool, it is coming with an error saying "Target device is too small to hold os image".
But when I see the size of the image in Windows explorer it is listing it as 30.2 MB [31,764,992].But when I see the size of an image of NK.nbf file it is 32,505,888.
Can somebody help me?Thanks in advance.
Cheers
MSAR
-------------------------------------------------------------------------------
ATT procedure to recover XDA
Fix
Pre-requisites:
A blank 32 megabyte SD (secure data) card.
A SD card reader.
Hard reset the SX56 and press the Power button.
A color screen stating "Wallaby Boot" will appear with the version number. A check of the GSM service will be run.
Download the XDA (the other name for our phone) OS Image Tool, at http://wiki.xda-developers.com/wiki/XDAtools.
Plug in the SD Card Reader with the SD Card inserted in it to the PC.
Once download, open "XDA Tools XDA OS Image Tool" from the Start Menu.
Do NOT use the fix broken boot loader option from the sub folder.
In the Source pull down (the top section) click the "..." next to the pull down and go to C:\Program Files\SX56 upgrade utility\english\NK.nbf
This is the location of the Windows Mobile 2003 Operating System Image that was installed when it was downloaded and ran the initial upgrade process.
In the "Destination" pull down, select the SD Card Reader.
Click the Copy button.
Once the procedure is complete in Image Tool Program, disconnect the SD Card Reader and remove the SD Card.
The SX56 should still be at the Boot loader page, if not hard reset the SX56 again and press the Power button to bring it back to the boot loader screen.
Hold the Power button and use the stylus to press in the soft reset button (both at the same time).
This will bring up a 'Copy Image from SD to ROM' selection.
Select "To copy from SD to ROM", (this will take a few minutes).
Once the upload completes, soft reset the device.
Verify the version number of the device.
Either from the device menu:
ROM Version A.30.09 ENG
ROM Date 01/01/04
Radio Version A.33.02
Protocol Version 1.3.3
Or from the inital boot up screen:
G1.3.3
A.30.09
RA.33.02
If problems persist, please contact Siemens at 888-777-0211.
This topic has been discussed at http://forum.xda-developers.com/viewtopic.php?t=9627
The ~8MB difference is the File Allocation Table (FAT) stored on the card. You will need to get a 64MB SD card to store that file on.
it is not the FAT, it is a bug in the memory card driver, that it reports incorrect values for the diskgeometry, as reported by the IOCTL_DISK_GETINFO function.
see this page.
I should maybe use a different function to get the disk size, like GetDiskFreeSpaceEx or IOCTL_DISK_GET_LENGTH_INFO ( I have not tried those to see if they give more accurate values )

Flashing from SD Card

I have a Touch Pro2 (GSM) with energy 6.5.5 rom. I wanted to install a new rom.
OK I formatted my SD Card, backed up all my contacts with myphone.
I downloaded my desired rom, renamed it, put it onto my SD Card.
I removed the sd card and my sim card.
I used http://forum.xda-developers.com/showthread.php?t=649191 this to format the main os. Phone restarted with just "touch pro 2" on the display.
I removed the battery, inserted the SD card (with the correct named rom).
I inserted the battery again and started the phone while pressing the lower volume button.
The red green blue white screen from my bootloader opened up. AT the top it says
RHOD00 32M SS-BC
SPL-0.85.OliNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
... .... ... (some numbers) calibrated
and in the white area it just says Serial. Nothing happens. Is it safe to take out the battery and try to install the image with active sync??
Did you reformat sd card FAT32?
Did you install Hard SPL 1st?
Also, I have found on occasion, the transfer to the sd card isn't good, copy the .nbh file over again and try if you have done the 1st 2 things....
ultramag69 said:
Did you reformat sd card FAT32?
Did you install Hard SPL 1st?
Also, I have found on occasion, the transfer to the sd card isn't good, copy the .nbh file over again and try if you have done the 1st 2 things....
Click to expand...
Click to collapse
Thanks! I already had hard spl. As I said, I was using a custom 6.5.5 rom before
I didn't have any access to the SD card because I don't have a card reader for micro sd (that's why I copied the file before I removed the sd from my phone)..
But I was able to get around the situation. The moment I plugged in the usb cable I was able to access the phone via active sync and I could flash it from within windows
PumpAction said:
I used http://forum.xda-developers.com/showthread.php?t=649191 this to format the main os. Phone restarted with just "touch pro 2" on the display.
Click to expand...
Click to collapse
why did you do that?
also did you rename the rom to RHODIMG.nbh?
Because after I went from stock 6.1 to stock 6.5 rom suddenly the coreplayer and windows media player were suttering at ALL videos that worked perfectly fine before. I then tried an enegry rom.while it was good looking it made no difference in video playback.thats why I wanted to switch to another 6.5 rom that was using 2.1 manila instead of 2.5.
and yes i named that rom exactly like that! One last question. After having successfully hard spled the phone, is it now safe to install every rom i want without having the fear to brick my phone?
oh and btw. while the new rom really AMAZING videos still stutter 3d games work perfect but that damn videos not. and on a small note:the newest opera 10 mobile is INCREDIBLY fast!Finally a piece of software where I can see how fast the cpu really can be just flash is missing

Flashing via SD card assistance

I've got a Tilt 2 with hard spl and can flash from my desktop no problem. I'd like to get the flashing via SD card going, but it's hanging.
I've got the nbh file copied to the root of my SD card, get the phone into bootloader, but I see a message flash up about no image. It's very quick though and then the phone hangs in the bootloader. A soft reset fixes it and the phone boots up.
I'm clearly missing something and can't figure out for the life of me what it is.
The image file is named correctly. It was copied to the phone through WMDC to the SD card. Should I put the phone into disk mode a copy the image over?
The SD card is formated in Fat 32.
Any thoughts/Advise?
Thanks.
maybe..
i had this issue before - check your .nbh file with total commander, or put it in your pc and check it. if you name it .nbh with the wm file explorer, it actually ends up RHODIMG.nbh.nbh - solution is just to remove one .nbh!
:::Whimper:::
I'm having this exact same problem!
My RHODIMG file is named correctly and in the root directory (there is nothing else on the SD card either), but I get that same EXTREMELY BRIEF message about no IMG file and then it hangs at the bootloader screen with 'Serial' in the white box on the bottom.
I've even tried using Mobile Flasher, but nothing is working. I
What am I missing??? I've tried it many times already, formatted my card a few times and loaded the RHODIMG file again, but nothing! My Rhodium will NOT connect via USB anymore, so I need to flash via SD card.
Help!
Debbie
I actually don't even rename the file, it's already got that name from the rom. It's e2 manilla 2.5 rom.
I'll try and transfer the file to the card when the phone in disk mode and see if that makes a difference...
O-M-G(!), this is *so* freakin' wacky!!!
I just switched SD cards to one that was larger (8GB rather than the 2GB), that had tons of stuff on it, then copied the RHODIMG file in the root, and then ran 'enablerapinew.cab' again, just for the hell of it...
Damned device found the RHODIMG file there from the bootloader and the update ran as expected, but not on the 2GB card with nothing else on it! WTH?!
Device says that the update is complete, so I'm booting up now and will do a few resets and then perform the tedious task of setting up my Tilt 2, etc.
Don't know whether the cab (thought I only had to run this once when Hard SPLing?) or the different card was what caused it to work, but I hope this helps someone else with the same problem. Whew!
Debbie
...Who's back in business!
SOLVED!
I don't know what caused the magic, but I was able to flash from SD card... FINALLY!
Here's what I did: Flashing Via SD Card Assistance
Hope this helps others!
Debbie
No, this did not work for me. I tried installing the cab again, but no luck, just passes on by saying no image.
Delete image off sd card, reformat FAT32 and copy image back on... I have had this problem myself, it seems that when the .nbh file copies it doesn't register on the card properly or something. Either deleting the file then re-copying seems to work but I still like to reformat too..... DON'T just copy over the top of the image file... THIS DOESN'T WORK... leads to a lot of hair pulling frustration...
Cheers...
So I tried a reformat of the card, just a quick one, not full. Still didn't work. I downloaded another image to try out, the lastest Energy rom, to flash on a completely blank card. That didn't work.
So, I went and got an older card, 8 gig, that is currently being used in a camera. The one I use now is a 16 gig card. This one worked fine.
Conclusions being perhaps a 16 gig card won't work for flashing?
brands
i have heard of certain brands having sizes that didn't work for flashing, for whatever reason. It was a long time ago on my kaiser, so i don't remember which it was, but kingston 2gb comes to mind. like i said, don't know if that is accurate, but there definitely were some that just wouldn't work. perhaps a different brand 16gb?
Well, I used the other memory stick, a Scandisk and this worked fine. Must be something with the 16 gig Kingston disk as it just will not work.

Can't get past HTC Start up screen.

Hi,
I had DJ Droid installed on my desire and I was trying to unroot it and put a stock 2.1 rom on so I could put Froyo OTA once it was released but I didn't get very far!
I formatted my spare card sd card and wanted to make a new gold card as out of the two I used I wasn't sure which was the gold card.
Whenever I turn on my phone it hangs on the HTC start up screen.
I can hold power and volume down and get into HBOOT, go to recovery, volume up and get to Android system recovery <2e>
Apply update.zip and it says No Such File even though I put it on but I may of wiped the partition during all this which has removed this file.
When I try to mount the micro sd using an adapter and look at the files on it it says 'You need to format the disk in drive G:before you can use it.
This happens for both cards. I try to format them but they both fail
Anybody ideas apart from leave things how they are in future!
Cheers
hmm, try to use the windows drive manager to fully remove the partition on the sd card. then create a new partition, reformat and! be sure to select the PHYSICAL DRIVE (without a letter) when editing the sd-card and making the goldcard.
it looks like you edited the volume header and the partition table is corrupted too.
if this is not helping maybe the sdcard is broken indeed, but I seriously doubt two sdcards failing at the same time
greets,
messy
Managed to format the card and put the update and djdroid files on the card and start again.
I must not be doing the wipe incorrectly at times, also the boot took a lot longer to load compared to when it was working fine so it might of been me thinking it had froze on the htc screen when in fact it was working, sorry!
All sorted now and I have put OpenDesire to see what that is like.
Thanks for the help.

[Q] HTC Desire SD Brick? Can't BOOTLOAD, help!

Hi everyone,
I've had a bit of a search on here, and although I can find threads about SD bricking, I can't quite find one that matches my situation.
I tried to root my phone and flash my first ROM today, I thought it'd gone ok, partitioned using GParted and flashed the GingerBurst ROM, and seemed to start up again ok. I was going to add something to my SD cards though, and found my USB connection menu didn't included the usual use as disk option and the SD card is now inaccessible from both my computer and the phone.
Under Settings->SD & Phone Storage, both Total and Available Space fields are 'Unavailable' and Mount SD Card and Erase SD Card are greyed out.
I've tried getting the bootloader up to see if I can do anything by holding down the volume down button and the power button (phone doesn't even turn on and screen remains blank), so I think my phone no longer sees that as a recognised option. I've tried back+power and up vol+power (for fastboot), and I get nothing. All my phone will do is power on if I hit the power button, so now I really have no idea of how to get the SD card back up and functioning.
I haven't tried repartitioning it because if my computer can't see it, and neither can my phone, GParted surely won't... I also don't have a card reader.
Is there anything I can do? Is there another way to get the bootloader up? Did the key combination change with gingerbread? Maybe I went wrong somewhere during my rooting... I don't know. Any help would be very much appreciated!
Thanks,
Daisy
You need to either get a new spare card, Format in FAT32 then add a 1gb EXT3 partition, or get a card reader and reformat you old card again with FAT32 first then EXT3 second- if it doesnt work, bin it
Dont worry about losing applications you can download these again from market.
Ensure your card is properly formatted if using A2SD
Wipe your phone and caches
Install your ROM from the SD card
re install applications
Enjoy
Please use the Q&A Forum for questions Thanks
Moving to Q&A
You have to press and hold first volume down (for hboot) or back (for fastboot) and then the power button. It seems as if you doing it the other way around.
Otherwise, you can do it so: When running rom, use restart option from shutdown menu. Then press and hold back button.
After you successfully booted your phone into fastboot mode, set up adb / fastboot (for a guide see my sig), connect your phone to computer, open command line on computer and type
Code:
fastboot oem enableqxdm 0
.
Now reboot into rom. Your desire should now recognize the sd card.
Hi, thanks for the info! I've tried all the instructions here: cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK#Windows
I got to 14 - but no drivers were automatically installed, and at 16 what looked like a command prompt style window popped up for a split second and disappeared - no information that I could read on it in that moment anyway, I did try again but same thing, so I continued with the steps to check, and tried it again after step 28 with the same thing happening again.
When I try to boot in fastboot mode my phone looks as though it's just starting normally - should anything be different? I don't know what fastboot is meant to be like! I also tried the piece of code you included in your message there and brought up a window that said it was waiting for the device, but made no progress...
I am correct in thinking I should be entering these prompts by going Start-> and typing 'run' in the search field, and then entering the prompt there? If not then that might explain something!
Seems to be an usb brick. On xda you find a guide how to solve it.
TouchPaled from Oxygen with Transparent XDA App

Categories

Resources