Database Info

Easy to read guide to Upgrading to Bigstorage on Magician

I’ve recently embarked on another round of ROM upgrading. :shock:
Having tackled an upgrade involving an incorrect hardware version (see > > here < <) and been happy with fixing my XDA II mini, I thought I’d try something a little more complicated.
Available at forum.xda-developers.com is a HTC Magician (known more locally as the O2 XDA II mini, i-Mate JAM and a variety of names) image which removes the Extended ROM (ExtROM).
This is more important to us "Magician" users compared with other PDA owners, as the Magician class of devices don’t have a software utility to make the ExtROM viewable and writeable.
Other HTC models do have utilities to read the ExtROM space and delete the files within it, and make the space raw storage space. On the other models this memory gain isn’t a big issue, but with the limited memory on the mini, any extra memory space is a real godsend.
The procedure is documented at xda-dev, but [rant] I find that site incredibly difficult to understand at times, a personal opinion based on the fractured English that people use because of culture, proficiency, age of contributors, ebonic growth of language and excessive use of contracted words. [/rant] Ahem.
As such, I have decided to outline what I did to get my Magician (mini) to use the “bigstorage” upgraded ROM.
Prior to Installing
It’s the rule of the 6 “P”s – Prior Preparation Prevents P*** Poor Performance. I’d recommend NOT installing this until you have the following:
* A Windows PC
* An SD Card reader. I used > > this < < one, available at a VERY low price from regular Mtekk poster, Mr Gadget
* A spare 128Mb (or bigger) SD Card. You can reuse the card later, so copying the files off of the card for restoration after the ROM upgrade is fine
* A full backup (this is actually NOT necessary if things go well, but essential if things go WRONG)
* Installation files for all your programs. If you restore from a previous backup you have taken, you actually re-install the ExtROM files and the installed programs they generate, making the upgrade useless. The aim is to clear everything out and start from scratch, putting only what programs you want back on
* A well lit room to conduct the upgrade
* A decent amount of time before you need to use the device again
* About 700Mb of free hard drive space
* A copy of all the software you will use. This includes:
--> the new BigStorage ROM (BigStorage ROM)
--> the utility to copy ROMs to and from your SD card reader (NTRW, file to be stored in C: or somewhere you can remember and have write permission to)
--> a Hex Editor
--> the program to copy your ROM initially (ROMupdate)
--> and a copy of an existing WORKING ROM (see my .sig for how to do THAT whole procedure.)
Phew. With all that prepared, you’re only just almost ready to go. But one last time – are you SURE you want to do this?
Just had to ask :wink:
Procedure
First things first – DO NOT CONNECT YOUR MAGICIAN FROM NOW UNTIL YOU ARE READY TO UPGRADE
Ahem. Now, the procedure.
1. Back up your Magician. I know I’ve said it before, but do it anyway. Ensure that your SD Card files are copied as well, and that the SD Card is in the Magician
2. Disable the USB listener of ActiveSync. Right click the AS icon in the taskbar, select “Connection Settings…” and uncheck the checkbox “Allow USB connections”
3. Install the Hex Editor you have already downloaded
4. Kiss goodbye to your SD Card and Magician’s current OS for at least ½ an hour :wink:
5. Put the Magician in to bootloader mode, by holding the Camera and Power buttons while pressing the soft-reset switch in the base of the PDA. Your Magician’s backlight will go out, and the words “Serial v1.00” or similar will come up. If it says “USB v1.00” then you haven’t followed my warning of not connecting and you should await the Black Ops agents bursting through your windows any second now
6. Connect your Magician via USB to the PC. Your PC should recognise it as a new device and try to install drivers for it. If you’ve ever installed Active Sync, your PC will have them. Wait for the new hardware bubble to say it is finished. If it reports an error, GIVE UP NOW. Fix the problem first, then come back. If Active Sync runs and synchronises your files, pack the phon back in to it’s box and send it back to the retailer, with a note saying “I am too stupid/foolhardy/impatient to read and follow step-by-step instructions”
7. Run the ROMupdate utility you have already downloaded
8. In the Port: dropdown combo box, select the entry that isn’t a serial port – it should be something like /.//blah blah blah and hit OK
9. In the terminal window that comes up, type “d2s” (without the quote) and wait until it finishes copying the file, and then wait some more until it calculates the checksum. BE PATIENT. Close the program
10. Unplug your Magician and leave it ON, and in bootloader mode. Seriously, I mean it. Connect up your SD Card reader. Let the individual drives be installed (if not already)
11. Take the SD card from your Magician and put it in the appropriate SD card reading slot. Your PC may complain that the card is unreadable and needs to be formatted – DO NOT LET IT DO THIS
12. Run a command prompt (Start -> Run -> “cmd” -> Ok) and change to where NTRW is (cd c:\ most likely)
13. Type “ntrw read OriginalROM.nb1 x:” (without quotes) where x: is the drive letter of the SD card reader. Mine was g:
14. Wait for the program to finish. This can take a few minutes, and will create a file (in the directory with NTRW) with a size up to the SD Card’s capacity (256Mb on mine). Ignore any error messages
15. Copy/burn that file somewhere safe – this is your original ROM and if copied on to an SD Card, can restore your Magician at a later point
16. Copy the file AGAIN, to work off just in case
17. Run the Hex Editor and open the copy of your original ROM
18. The top of the BIG file will start with “MAGICIAN” and have a block of weird text characters at the top. Copy the first 420 or so bytes (there will be a block of “00”s that show you when to stop copying) and in a new file, save those in a file with a descriptive name like “top420.hex”. This file, when applied to a .nb1 file, makes the file able to be installed on YOUR device ONLY. Without it, your device won’t attempt to upgrade itself from an SD card .nb1 file
19. Unzip the BigStorage ROM. Using the Hex Editor, open the BigStorage ROM .nb1 file
20. You’ll notice it is fairly similar to your original ROM. We need to overwrite the header 420 or so bytes, so open up the top420.hex file, select all, copy, and switch back to the BigStorage ROM and paste over the top. The linked hex editor will show modified text as RED, and thus only the first section will be red. If it doesn’t cover all of the BigStorage top section, you’re in trouble that I can’t fix
21. “Save As...” the edited file to the same directory as NTRW with a better name (like “modifiedROM.nb1”) Make sure the file extension is .nb1
22. Close all active programs and run a command prompt. Change to the NTRW directory
23. Type “ntrw write modifiedROM.nb1 x: (again, where x: is the SD card drive, and where modifiedROM.nb1 is the filename of your modified BigStorage ROM. Wait for the file to write. If you don’t get the number of bytes written, repeat from step 12 (I had to do it 3 times for some reason)
24. Remove the SD Card from the reader, unplug the reader and close all programs
25. Put the SD Card in to the Magician and wait 5 whole minutes. If you are lucky, you will get a prompt to “Press power to upgrade” or similar, on the bootloader screen. If so, jump to step 29. If not, read step 26
26. This is a bit hazy. If after 5 minutes no prompt to upgrade appears, you may need to hook the Magician up to USB to get the prompt. Connect up, and wait 5 minutes. If you get the prompt, jump to step 29. If not, read step 27
27. If you haven’t got the prompt after a further 5 minutes of USB connectivity, leave the USB cable plugged in and restart your PC. Do not reset using the button, reset using Start -> Shut Down -> Restart. Wait 5 minutes (your PC will be rebooted by now, right?). If so, jump to step 29. If not, read step 28
28. You’re in trouble. Like me, you’ll have to try different combinations of steps 25, 26, and 27 until you get the prompt to upgrade. Try plugging USB in, out, restarting your PC, USB in again, all waiting 5 minutes just to be sure. EVENTUALLY you will get it. It took me 40 minutes until it worked for me, but work it will
29. You did it! Press the power button and sit back while the file upgrade hits 100%, and then the Checksum hits 100%. Wait 5 minutes just to be sure, then remove the USB cable and move on
30. Soft reset your phone by the recessed reset button. Your newly-flashed ROM, with “HTC Magician” splash screen complete with volcano (no, really!) will greet you. You’ve succeeded in upgrading!
31. Set up your device with a new Device ID name, set your clock etc etc, just as if you’d just bought your first PowerPC (ahh the memories)
32. Re-enable USB connections to Active Sync (reverse of step 2)
33. Connect the USB cable. Create a new standard partnership (NOT guest) and take a new backup for BigStorage restoration. DO NOT RESTORE FROM A BACKUP OF YOUR OLD NON-BIGSTORAGE BACKUP
34. Reinstall programs from their install files
35. Format the SD Card (either in the Magician or in the PC SD card reader) and copy your SD card files back on to it
36. You’re done!
Wow. A lot of work! I did warn you. Really I did. But now, you should see some BIG differences...
* You will have fewer programs. ClearVue PDF viewer is gone, as are the files required to install it. Smart dialling, phone pad text entry will be gone. Most importantly, the Autoconfig program will be gone. Your phone will still work, but GPRS will need to be set up – ring your telco helpdesk and ask for the manual configuration settings (or ask the Mtekk users for their settings!). If you want the programs back you will need to download and install them. The files ARE available from the xda-dev FTP site
* You will have more memory. I went from around 20Mb free after a soft reset to around 41Mb free. Ahhh, the power!
So what changes? Well I went from
ROM version: 1.11.00 WWE
ROM date: 14/03/05
Radio version: 1.11.00
Protocol version: 1337.42
ExtROM version: 1.03.166 WWE
Windows Mobile 2003 Second Edition Version 4.21.1088 (15045.2.0.0)
to:
ROM version: 1.11.00 WWE
ROM date: 14/03/05
Radio version: 1.11.00
Protocol version: 1337.42
ExtROM version: (Yes, BLANK!)
Windows Mobile 2003 Second Edition Version 4.21.1088 (Build 15045.2.6.0)
Enjoy!

Very nice guide. My question:
In the step 25, 26, 27, 28, does the device still need to be connected to the PC ?
My suggestion to be included in this guide is Frequently Asked Questions.
People tend to understand more on that.

very nice manual!
but it's better to use"ultra edit"
http://www.ultraedit.com/index.php?name=Downloads&d_op=viewdownload&cid=1
edit as hex editor. it's much easier. first time i used hex editor and it didn't work good...
but now i'm stuck with copying my updated rom back to sd...
when i'm starting ntrw and command him to copy the file to card he waits a minute (giving me the information about the sd)
but then after a minute he writes:
write file () mksbigstorage.nb1 -- The parameter is incorrect
i checked the sd, nothing on it.
tried different type of cards, the same problem.
i checked twice the 416 bytes (did it with ultra edit) i copied it exactly
probably the problem is my card reader... ((

I get this "write file () mksbigstorage.nb1 -- The parameter is incorrect " as well.
What do you mean in the guide by 420bytes or so ?
is it 420 or not?
when I count 420 bytes it ends in the middle of the 0000 row, is that ok?

finaly I got passed that and was asked to press PWR to download the ROM.
At the end, I got a checksum fail and download fail at the end of the ROM downloading.
Did a SR, it came up ok within seconds.
The thing is that I see that I have 57.41MB in my main memory. I dont see any extended ROM anywhere, even if I make the trick with pressing quickly on the screen and do a SR.
Wasnt it suppose to be bigger than 57.41MB ??
please help. have I done something wrong?

Please...
Hey guys, can you take a look at this topic please: http://forum.xda-developers.com/viewtopic.php?p=128501#128501

I also got the "write file () mksbigstorage.nb1 -- The parameter is incorrect " error.
But a little googling learned this can be ignored. Im waiting for the "SD Download" as described in step 29, after that ill be able to tell if ignoring the error message turned out good for me.

I just upgraded with a 1.12 ROm from I-mate ( with the new 1.12.1 radio ROM) and it went perfect. You will not see any differeneces in normal RAm available,it will still be 57. something. The difference is in the storage, which is now 26.7 instead of a measly 7.6 MB. This is caused by the Extended ROm (which had a lot of inaccesible and unused space) and the storage ROm being merged.

After the 'firmware' download from SD card i received a 'checksum failed'. But a simple soft reset did the trick.
(note: I upgraded to 1.12 big storage which can be found on the FTP in uploads: mksBigStorage112.rar)
(note2: After upgrading to mentioned 1.12, your radio will still be 1.11, you can upgrade this by deleting 'ms_.nbf' and 'nk.nbf' and using the normal update wizard)
Result:
ROM: 1.12.00 WWE
Radio: 1.12.00
ExtROM: None
Protocol: 1337.42

Note, you will receive a "Checksum failed" message because you're patching the bytes to get the larger Storage and that messes with the checksum value. Remember, a checksum is to ensure that all the bytes are intact so that you know it didn't upload a bunch of garbage to your Magician. The scary part about it is that since there's no valid checksum for the changed values, you don't know if you've mucked it up until after you hit the soft reset and find out it won't boot properly.
Just follow the directions and you'll be fine. Good job on the steps!

There is hope...
Well, if you do mess up, like I did on my friend's mini, and the device stays in bootloader mode, and you just happened to mess up all your good copies of your backup, you can always reflash the device with the latest of the ROMs for your device. :?

has anyone get stuck on Step 25 ?
"Put the SD Card in to the Magician and wait 5 whole minutes. If you are lucky, you will get a prompt to “Press power to upgrade” or similar, on the bootloader screen. "
I never got to Press power to upgrade screen, instead I get below message after a few minutes...
SD Download
========
Section = 0
Not allow
update!
Tried different combinations as instructed by KevinL, Sometimes I get Section=1 instead of 0
Anyhelp, please.
Thank you

I just succesfully upgraded to the BigStorage ROM but I fail to see the difference. One person said "The difference is in the storage, which is now 26.7 instead of a measly 7.6 MB" . When I go to memory I have 28.70 allocated storage and 28.71 allocated program- isn't that what I had before? Is the difference in how much is in use- I have .91mb storage in use- i think that is less than before but I didn't gain that much- only 7mb- right?
Also, the ROM i have now has a volcano when start up ans says R 1.112.00 and D 1.11.00 WWE- I don't think this is the latest. How can i get the latest and if I do will it keep the new bigstorage stuff??
Thanks in advance,
Daniel - Sorry i'm new to the Magician!!

What is that "Storage" folder? :?

Daniel,
look under start, settings, system, memory, storage card, than you choose in the pulldown menu storage and you see about 25 MB extra storage.
I did upgrade to 1.12 bigstorage, so that works also.
Success!
Andre

Thanks- I assume when i install programs to the main memory it will use that extra space, no? Or will it be an option when installing- as in 3 choices- Main Memory, Storage, Storage card? Either way thanks!
So which ROM should I upgrade to and how? Is it worth it?
Thanks,
Daniel

I don't think personnally there is a big difference between 1.11 and 1.12. If you don't find any problems, i would say: stay where you are.
You can use cab installer to put programs in your bigstorage space http://www.freewareppc.com/utilities/cabinstl.shtml
I didn't use it untill now.
In my opinion it is best to use this storage first, so you have the normal storage for your photographs, recorded sounds, things your machine will put in your normal memory.
Andre

I found a different method for getting the boot loader to read the new image from the SD card. This method worked 100% for me, whereas all other methods (waiting 5 mins, plugging in USB, rebooting etc.) failed.
1. Press the camera button, power button and reset button simultaneously to get into boot loader as usual, so that 'Serial' is displayed on the screen.
2. Insert SD card.
3. Again, press the camera button, power button and reset button simultaneously to get into boot loader, so that 'Serial' is displayed on the screen.
4. At this point you should get the Upgrade prompt.
Hope that helps someone.

marcdbl said:
Hope that helps someone.
Click to expand...
Click to collapse
Thanks! This is the only method that worked for me!

i dont know wots wrong with mine, when i run romupdate.exe and enter the command d2s it says.. 'card initialize fail!'...
wot is the reason for that?... i've got a 256 MB card... plz someone explain.. im very confused..

Struck by an MDA brick!!

Made a huge error.....didnt go through forums and read instructions before trying to Flash a German T-Mobile MDA Compact to a English ROM....
The device is completely dead....
Followed all the steps required to get it back up...It is refusing to do so though....
Used this thread:
http://forum.xda-developers.com/viewtopic.php?t=19500
One thing to note is that I am not using the AC charger, am using the USB cable to charge the phone.
Can someone please helpme...
Haven't got past the bootloader mode...

If you followed the instructions from the other thread, it should have started flashing.
Some things to check on:
1) Did you do a full d2s before you attempted the upgrade? It's always good to have something to fall back on.
2) If you can get to a bootloader screen, all is definitely not lost.
3) Sometimes, it takes 4 or 5 minutes for the "Press to flash" comes up on the screen so be patient with that.
4) Make sure you did exactly a 416 byte copy from the original rom file in to the new flash file.
5) You can only write an nb1 file from the pc AFTER it has been created from the pocket pc. If the SD card has been pc formatted, the nb1 file will write to it but the pocket pc won't recognize it and will just sit there at the bootloader screen.
HTH

I think I fired the MDA
Well I did not create the nbf file from the ppc, downloaded it from the the forum FTP. I do not have the backup of the nbf file. As I mentioned I did not read the forums before trying the update.
I just downloaded the T-Mobile ROM update and tried installing it. Obivousioly it didn't work, Game the dreaded the 112 error in the 3rd step.
Am not even getting the bootlader screen now..
Any ideas on how I can get this device up and running.?...

ok, need some clarification here. "What" are you trying to load (nbf files or nb1 files) and how are you trying to load them (SD flash or the standard USB based upgrade)?
Easy enough to check to see if your device can still get to bootload mode....hold the camera and power switches in at the same time and hit soft reset with your stylus. After letting go of those and you see either "Serial" or "USB" at the top of the screen, you should still be able to recover from this.

Tried with the nb1 files not nbf (sorry abt teh error)..
The bootloader screen was showing up ...unitll I tried the T-Mobile MDAcompact_vers11201
After the 112 error while updating...the device now refusing to get to the bootloader mode.
Have I fried the device and made it unusable....?

hey just got back the bootloader screen...

Take the SD card out, disconnect the USB and tell me what happens when you hold the power and camera buttons in at the same time, then hit the soft reset.
Also, has the unit been charged recently?

Its showing Serial v1.00...after the reset.
Its been on the USB chatge all along.....

Great. If you get Serial at the top, this can be recovered.
If you want a good T-Mobile 1.12 rom file, go here and use this one:
ftp://ftp.xda-developers.com/Uploads/Magician/tmobile-uk_wwe_ROM_1.12.00(thereapermanl).rar
Unpack it and follow all the procedures about copying the 416 bytes, rewriting the file, etc. from the other thread. I have tested this rom file and it installs ok.

Thanks for the encouraging words...
Will it work even if I do not have a backup of the original ROM on my machine?....I only have the tmobile.nb1 file which I got from the XDA forums.
Lemme try using that and editing it.
Thanks a ton for your help.

You might be a little stuck for an nb1 flash if you don't have an original flash back up but don't fear. You can go here and get this WWE1.12 file and just do a USB type upgrade:
ftp://ftp.xda-developers.com/Magician/Shipped_ROMS/WWE_11200_128_11210_ship.exe
I know this one works too. It's ROM 1.12, Radio 1.12 and Ext_ROM 1.12. When you try to run the upgrade program though, it might give you a Country ID error. If so, use the attached upgrade program instead. If this one gives you a Country ID error again, close the program and just run it again. I've been down all these roads already.

Lemme get this right this time: I will be doing the following
1. Install the ROM as you have mentioned. With the country id hack if necessary
2. Hopefully by now the device would be alive. If so will take a backup of the ROM on the SD card
3. From then on follow the instruction given in the doc.
Hope I get it righ this time else Its going to be a long night for me.
Lemme know if I have to do anything else.

Either ROM will work fine for you. It just depends on whether or not you want I-Mate stuff on it or T-Mobile stuff on it.
Doing the USB upgrade will put the I-Mate ROM on but after that, it should be working and you can then do an SD backup, follow the SD flashing procedures and get the T-Mobile ROM on.
Good Luck!

The masupgrateut is throwing up a ruu.dll error?...you seen that one before?

What sort of error? Not found?

yup...
I extracted the ROM exe and found teh file...copied it to the windows folder..and ran the no id program...no error this time round but the update is still giving a COuntry ID error...
Been looking at various posts...specially this one...
http://forum.xda-developers.com/viewtopic.php?t=14973
Thinks thats gonna help?

ok...two things.....just run it again. The no ID program sometimes does that on the first time 'round so just run it again.
Second, stick this at the end of the RUU.conf file:
[CHECKCEID_TYPE]=1

ran the program multiple times...still getting the COuntry ID error...

Are you running this program? MaUpgradeUt_noID.exe
...with the change in the RUU.conf file?

I just noticed something....did you extract all the files to a single directory and just run it from there or did you just pull a few out?
ALL the files have to be in the same directory. This is also where you need to execute the installer program.

ROM flash from SD/MMC: Without needing 2nd device

Guy's,
Finally you can flash any rom to your device without help from the 2nd device. I believe it's a great news for them who is suffering from the broken USB connecor.
It's tested on my G3 device with my latest ROM's and other should work without problem.
Procedure:
1. Download the tool and unrar somewhere in your pc.
2. Decode the rom image (nk.nbf) using HTC64 tool and put it (nk.nba) under the "SD_Flash" directory.
3. Run the "SDFlash_G3.cmd" and follow instruction on the screen.
Please note, it's limited to G3 device only and I may add support for G4 device in future.
SD-ROM image tool:
http://vidmes.com/Uni/ROMs/Tomal/Tools/Ranju_SD_Flash.rar
!! IMPORTANT: Do it at your own risk. I'll not take any responsibility if you damage your device. !!
Cheers

Great stuff.
I especially look forward to a G4 release.
My USB commector broke off the circuit board recently and was floating about inside the device for a while before I opened up the device and glued it back in position onto the circuitboard. It now works (the 5 little pins are connected) so I can charge the battery through it, but I don't really trust it to flash a firmware through.
Thankfully I'm already on the ROM I usually go back to (latest T-Mobile WM5) after playing around with WM6 and WM6.1.
Nice to see developments being made for those of us with handicapped uni's!!!

Thanks a ton, Ranju !
Have already downloaded and unpacked it. I'll certainly give it a try as soon as you release your v7.7 ROM.
Cheers!
Carlos

Dear Ranju,
You keep on surprising us!
Thanks friend,
Mohamed

Ranju, as usual, you are the man!
I experienced the "direct flash" on a Mio A701 and it's really a great feature. Now I can't ask you anything more... ehm...
..
... I was kidding I'd like only the new build of your rom eheh
thanks!!!

Thank you ranju for this great tool, so I can flash WM6.1 on my MDA Pro with broken miniUSB!

casouzaj said:
Thanks a ton, Ranju !
Have already downloaded and unpacked it. I'll certainly give it a try as soon as you release your v7.7 ROM.
Cheers!
Carlos
Click to expand...
Click to collapse
ha ha ha, nice catch!
Also waiting for a new release... and G4 tool
Cheers

Lord of the binary digits
Hi Ranju!
Thank you very much for sharing your great work.
Cheers

I tried to flash using bluetooth (yeah, I was stupid) and since then it's hanging in bootloader mode.
The mini-USB connector broke before (that's why I was using BT) and now I finally thought I had a solution to get it working again.
However, when I follow your steps and reset (backlight + power + reset) it doesn't even seem to look at the SD-card; it just shows serial + v1.00 again.
Any ideas?
In SDimage it get's to only 3,21%, but's that's normal on a 2 gig card I presume?

martinbl said:
@ 13,05% I get an error in SD Imaging tool and it stops there...
Any idea why?
Click to expand...
Click to collapse
what is the size of sd, 512mb?

ranju said:
what is the size of sd, 152mb?
Click to expand...
Click to collapse
I just edited my post .
I used another card and that got only to 3,21% or something (2gig card) so I presumed that's normal because of the image size?
To be complete:
I tried to flash using bluetooth (yeah, I was stupid) and since then it's hanging in bootloader mode.
The mini-USB connector broke before (that's why I was using BT) and now I finally thought I had a solution to get it working again.
However, when I follow your steps and reset (backlight + power + reset) it doesn't even seem to look at the SD-card; it just shows serial + v1.00 again.

martinbl said:
I just edited my post .
I used another card and that got only to 3,21% or something (2gig card) so I presumed that's normal because of the image size?
To be complete:
I tried to flash using bluetooth (yeah, I was stupid) and since then it's hanging in bootloader mode.
The mini-USB connector broke before (that's why I was using BT) and now I finally thought I had a solution to get it working again.
However, when I follow your steps and reset (backlight + power + reset) it doesn't even seem to look at the SD-card; it just shows serial + v1.00 again.
Click to expand...
Click to collapse
Yes, it's normal.
Did you inserted the card to device before entering to bootloader?
Read and follow all the instructions carefully in the .cmd file.
For more info, read Htc Service manual of Universal.

Thanks Ranju!!!
I am waiting for G4 device

ranju said:
Yes, it's normal.
Did you inserted the card to device before entering to bootloader?
Read and follow all the instructions carefully in the .cmd file.
For more info, read Htc Service manual of Universal.
Click to expand...
Click to collapse
I shall tell about all the steps I took:
1. Download the tool and unrar somewhere in your pc.
- Easy.
2. Decode the rom image (nk.nbf) using HTC64 tool and put it (nk.nba) under the "SD_Flash" directory.
- I took your(?) "Ranju_v76_WM61_19209_19209_1_0_2", unrarred it and decoded it to nk.nba.
3. Run the "SDFlash_G3.cmd" and follow instruction on the screen.
g3.bin and nk_sd_g3.bin are created.
After that, I put in my Dane-Elec 2 gig SD-card and format it to FAT32.
SDimage is opened and I select the FAT32 F: drive.
After that I push the "Import SD Image" button.
Fill in "i agree", click "ok" and "yes" (with "hex" unchecked).
There I choose bin files and select "nk_sd_g3."
I then click "Ignore", "yes" and "ignore" and it's starts writing.
At 3,21% I get the dump incomplete notification and click ok.
I then put the card in my Universal, press the light and power button and the reset pin.
For a second or so the v1.00 disapears and it comes back without doing/checking/reading anything.
I'm quit sure the SD-card should work because before I flashed using BT, it worked and I tested the same procedure with another card.
Any ideas what I'm doing wrong or why the Universal doesn't even seem to look for the SD-card?

martinbl said:
I shall tell about all the steps I took:
1. Download the tool and unrar somewhere in your pc.
- Easy.
2. Decode the rom image (nk.nbf) using HTC64 tool and put it (nk.nba) under the "SD_Flash" directory.
- I took your(?) "Ranju_v76_WM61_19209_19209_1_0_2", unrarred it and decoded it to nk.nba.
3. Run the "SDFlash_G3.cmd" and follow instruction on the screen.
g3.bin and nk_sd_g3.bin are created.
After that, I put in my Dane-Elec 2 gig SD-card and format it to FAT32.
SDimage is opened and I select the FAT32 F: drive.
After that I push the "Import SD Image" button.
Fill in "i agree", click "ok" and "yes" (with "hex" unchecked).
There I choose bin files and select "nk_sd_g3."
I then click "Ignore", "yes" and "ignore" and it's starts writing.
At 3,21% I get the dump incomplete notification and click ok.
I then put the card in my Universal, press the light and power button and the reset pin.
For a second or so the v1.00 disapears and it comes back without doing/checking/reading anything.
I'm quit sure the SD-card should work because before I flashed using BT, it worked and I tested the same procedure with another card.
Any ideas what I'm doing wrong or why the Universal doesn't even seem to look for the SD-card?
Click to expand...
Click to collapse
The same problem, I folowed all of the instructions as it is, but only serial 1.01 on the screen and no look for the image, i have tried with 2 SD cards, one 256 MB and the other is 512 MB, but there was no difference....
PLZ help

hbahaie said:
The same problem, I folowed all of the instructions as it is, but only serial 1.01 on the screen and no look for the image, i have tried with 2 SD cards, one 256 MB and the other is 512 MB, but there was no difference....
PLZ help
Click to expand...
Click to collapse
Yup, same problem here! I tried with a 512MB Toshiba SD card, previously formatted both to FAT(16) and FAT32. SDImage.exe runs up to 12.91% (FAT) or 12.93% (FAT32), with such card capacity. Same results: my Exec just sits there in booloader mode forever...
Cheers!
Carlos

all the steps are correct .
I'm sure root cause is under the header (g3.bin). it's a mmc header and I suppose there is a difference between sd & mmc header. I'll verify once I can arrange a sd card. alternatively someone can try it using a mmc card so that I can reach to a conclusion.

Hi ranju,
Uploading my MMC header for comparison purposes.

I'm also looking for SD header, g3/g4 both the devices for analysis.

So does this work with a G4? or has it not been tested?

Upgrading to 6.1

Hi,
I'm sorry about this post but there seems to be an anormous amount of information which doesn't make a lot of sense to me.
All I want to do is upgrade my palm treo 750 from win5.0 to 6.1.
I've downloaded the rom but it doesn't upgarade. So I need to figure out a way to flash this phone so it can be upgraded to any roms.
I have tried the Cheetahunlocker which doens't work. It gets stuck on 0% then times out.
Could someone please give me some basic instructions on the best way to do this on the treo.
I've done this on the TYTN2 whith no issues however on this phone, it seems to be a lot harder.
Thanks in advance.

Your device needs to be unlocked. You can do this by calling ATT and getting unlock code or by using Magic_Unlocker.
search
Also you will need to have the HardSPL installed which is Step 1 only of the CheetahUnlocker
I just did it yesterday so I know it works.
After you get the phone unlocked, name the ROM .nbh file CHEEIMG.nbh and then put it on the SD card
The start the CheetahUnlocker process as it enters the HardSPL process it will go ahead and run the CHEEIMG file and flash your ROM
(it works ! ) DON"T CHANGE THE RADIO !!!!
After doing that be sure and reclaim your ROM space - search web for Removing Ext ROM and do that process, hard reset and you are ready to go
Takes about 15 min!

jcrompton said:
After you get the phone unlocked, name the ROM .nbh file CHEEIMG.nbh and then put it on the SD card
Click to expand...
Click to collapse
Thanks for your info.
sigh..
The rom is an exe file...
I downloaded 7-zip, extracted the rom to a folder.
Looking through it, I am unable find the ROM.nbh file!
CHEEMING.nbh is already there..
What am I doing wrong?
Thanks.

artii said:
Thanks for your info.
sigh..
The rom is an exe file...
I downloaded 7-zip, extracted the rom to a folder.
Looking through it, I am unable find the ROM.nbh file!
CHEEMING.nbh is already there..
What am I doing wrong?
Thanks.
Click to expand...
Click to collapse
Sorry I forgot it was already named CHEEIMG.nbh -- just use it like I said above.
Copy it to the SD card, put the SD card in the device and after you have used Magic_Unlocker , connect via Active Sync and start the CheetahUnlocker process. This will start the three step CheetahUnlock process (really all you need is step one which will put the HardSPL in place) as that process fails the CHEEIMG file on your SD card will get flashed.
Hope this makes sense
Bottom line is that you will be doing an SD flash of the CHEEIMG.nbh file but it takes HardSPL for that to work. Step one of the CheetahUnlocker installs HardSPL (that will be all you need of that process)

remember!
THE SD FLASHING METHOD TAKES A REALLY LONG TIME. SO LONG YOU MIGHT THINK IT'S BROKEN. BUT IT'S NOT!!!!
caps with bold and red= great way to emphasize an important point.

Thanks for the info but I'm still running into trouble.
I copied the file to the SDcard but when running the cheetahunlocker, it give the same error at 0% ( error 206) something about the connection..
I notice that active sync turns off when the cheetah unlocker goes to the coloured screen.
Edit:
Also, should I be moving the CHEEIMG.nbh or just copying it to the SD card?
Thanks.

artii said:
Thaks for the info but I'm still running into trouble.
I copied the file to the SDcard but when running the cheetahunlocker, it give the same error at 0% ( error 206) something about the connection..
I notice that active sync turns off when the cheetah unlocker goes to to the coloured screen.
Click to expand...
Click to collapse
Did you run the MagicUnlocker first?
Is the CHEEIMG.nbh file in the root of your SD card? Try re-formatiing your SD card (FAT32 important!) and then putting the CHEEIMG.nbh file in place on the root of the SD card.
After starting the CheetahUnlocker the TriColor screen should come on and then it should go to a standard White boot scan. It will ask if you want to flash and you will be asked to confirm by pushing the Power button.
If you can ever get Step One to complete on teh Cheetah Unlocker you should be able to confirm that the HardSPL is installed by turing off Today screen (Red, end button) , then hold the left side button while then pushing the reset button. You will get a tricolor screen that lists your SPL version. If it is HardSPL on an unlocked device and there is a CHEEIMG.nbh file on an inserted SD card it will then automatically go to a White boot screen .....
If any of this sounds foreign to you then you need to familiarize yourself in the Wiki re SD flashing
PS do you have the NetFramework 2.0 installed on your PC? When you start the CheetahUnlocker are you getting the Treo device confirmation to install the 2 boot exe files that let the Treo go to the boot screen (you have to answer yes to both of these) - are you making it that far?

Yes I ran the unlocker which worked fine.
I formatted the SD card, copied the CHEEMING.NBH to it so it's the only file there.
No I run the CheetahUnlocker.exe , yes to disclaimer , then STEP 1 - I click FLASH SPL, then next, next etc.. I hit Update - next - next then the phone msg comes up asking if I want to run jumpSPL.exe - I hit yes and it goes to the tri colour screen, the active sync dissapears, the screen on the pc stays at 0% and then I get the error 260: Connection, check cable etc..
How is it suppoed to maintain a connection when Active sync turns off?
I did check and framework2.0 is present.
Thanks.

artii said:
Yes I ran the unlocker which worked fine.
I formatted the SD card, copied the CHEEMING.NBH to it so it's the only file there.
No I run the CheetahUnlocker.exe , yes to disclaimer , then STEP 1 - I click FLASH SPL, then next, next etc.. I hit Update - next - next then the phone msg comes up asking if I want to run jumpSPL.exe - I hit yes and it goes to the tri colour screen, the active sync dissapears, the screen on the pc stays at 0% and then I get the error 260: Connection, check cable etc..
How is it suppoed to maintain a connection when Active sync turns off?
I did check and framework2.0 is present.
Thanks.
Click to expand...
Click to collapse
I'm not sure exactly what is happening in your case but I do know that once a device of any kind enters the bootloader - Active Sync dies - AS is part of the OS and that no longer exists after the bootloader starts, I.e. Windows Mobile isn't really running any longer. the AS connection just gets it started.

I'm not too sure either.
I've unlocked the phone which worked fine.
When I run the cheetahunlocker, it doensn't get past the first step.
Should I be running Hardspl first?

What rom works best with the Treo 750? Link please!!!
What rom are you wanting to use? I have Treo750_WM6.1_WWE_Lite, looking for a more stable rom. Please list some or link them.

I tried both roms
the lite one and the normal one. I must say that the normal one is more stable - with the lite I had to do a reset at least one per day. with the normal version I did not do a reset at all...

Hi, did you resolve this CONNECTION issue? I'm having exactly the same problem.
Anyone?

hey everyone... i have a problem similar to these i think. I'll explain
i've done the magic_unlocker and i can do the 1st step of the cheetahunlocker. treo reset automatically and when i try to flash the rom the trilinear screen doesn't change to the blue screen which is the screen of the rom flash
anybody now why?
i have cracked my head the hole day and a still can't do it :S

artii said:
Yes I ran the unlocker which worked fine.
I formatted the SD card, copied the CHEEMING.NBH to it so it's the only file there.
No I run the CheetahUnlocker.exe , yes to disclaimer , then STEP 1 - I click FLASH SPL, then next, next etc.. I hit Update - next - next then the phone msg comes up asking if I want to run jumpSPL.exe - I hit yes and it goes to the tri colour screen, the active sync dissapears, the screen on the pc stays at 0% and then I get the error 260: Connection, check cable etc..
How is it suppoed to maintain a connection when Active sync turns off?
I did check and framework2.0 is present.
Thanks.
Click to expand...
Click to collapse
If it goes into the bootloader then you should be good to go. Both 750s i unlocked did this. However, if done correctly, the phone should go to a light blue screen where you will press the power button and flashing should begin.

na1kkkk said:
hey everyone... i have a problem similar to these i think. I'll explain
i've done the magic_unlocker and i can do the 1st step of the cheetahunlocker. treo reset automatically and when i try to flash the rom the trilinear screen doesn't change to the blue screen which is the screen of the rom flash
anybody now why?
i have cracked my head the hole day and a still can't do it :S
Click to expand...
Click to collapse
Are you doing the SD method or Desktop? DO the SD method and it should begin flashing right away after the 1st step of cheetahunlocker.

[Android] NAND Boot Method for Polaris: FLASH IT!

** PLEASE, READ THE GUIDE BEFORE FLASHING **
Flashing a device is a risky process, and you definitively have to know that your device might not boot correctly, or not boot at all. You must also notice that this method is being tested and some components of your Polaris will not working at the moment. Take into consideration that there are developers that are sharing all their work with us, but although they're really good at their job, they all have their lives. So, if something just doesn't work, please, be patient*
NAND Boot for Polaris! Made possible thanks to DZO!
This method will allow you to start Android without the need of Windows Mobile. It will just boot like if the device had a native Android OS installed onto it.
- You may see this guide really long, but it's because I tried to detail every step and I put lots of URLs to make the process easier for beginners It's not than difficult as it seems!
Step by step guide:
Needless to say that you need to have HardSPLed your device first!
1. CHOOSE YOUR ANDROID BUILD
You can install try to install any build from the Kaiser and Vogue forums. They should work for Polaris:
I personally recommend to start with Myn's Warm Donut Release 5.
You can choose it in two different screen resolutions
240x320 (my favorite) - http://download219.mediafire.com/t0lnxmijgEjg/1drm2jqwjzn/myn-WarmDonut-04-24-2010-240x320-110.zip
320x480 - http://download533.mediafire.com/ml1jxoyomIDg/miw2uzjjzjq/myn-WarmDonut-04-24-2010-320x480-160.zip
If you want more info, check its thread: http://forum.xda-developers.com/showthread.php?t=619980
Download the build. It may be a compressed file containing an androidinstall.tar.
Copy this androidinstall.tar under a folder named andboot at the top level of your SD Card. The file path should be /andboot/androidinstall.tar.
You're now ready to flash the OS loader.
2. -OPTIONAL, BUT RECOMMENDED. ERASE YOUR ROM.
To be sure that you won't have problems with the flashing, you should use a tool that executes the called Task 29 to clean the NAND memory in the device. This helps the flashing goes OK and minimizes the chance of a bad flash.*
Fortunately, there's such tool: It can be downloaded HERE (big thanks to leppa).
It's a hacked flashing tool. To make it work you will have to select a dummy .NBH file. Use the .NBH file you want, preferably a small one. You can use the one that you will download in step 3.
You it finishes the operation, your phone will NOT boot. Don't worry. This is normal. We will make it boot soon.
More info HERE: http://forum.xda-developers.com/showthread.php?p=6227425#post6227425
3. FLASH THE ANDROID OS LOADER TO NAND
You will need a .NBH in order to boot from NAND. It's usually named polaimg-panel[x]-[resolution]-[date].nbh.
I personally recommend to flash of the .NBH files by DZO dated 07-May-2010. They are listed on his site: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Choose one according to your paneltype and resolution. Your paneltype depends on its maker. You should try from 1 to 3 to see which one works for you.
Flash the .nbh file you downloaded with your prefered tool (I used CustomRUU.exe for Windows).
To flash your device you might have to put your Polaris in bootloader mode. To enter this mode you have to do the following:
Press and hold the camera button.
Press reset while you hold the camera button. Release it (the reset button).
Hold the camera button until the colored bars screen appears.
If it doesn't work, remove the battery, wait for some seconds, put it back and try again.
When the colored screen (Hard SPL) is shown, you are ready to flash it using the flashing application (CustomRUU.exe, for example).
4. INSTALL YOUR BUILD
When you're done flashing, your device will boot. You will now attempt to install your build using the file androidinstall.tar.
You'll see lots of text lines scrolling while it boots. Now, pay close attention to the next step.
The system will prompt you to press and hold the center button of the DPad (in the middle of the jog-wheel) to start the Android Installer. It's a message like "Press x to launch the installer". Don't forget to hold it until the installer is shown!
The installer will eventually start.
A list of options should appear (in text mode). Use the jog-wheel up and down to navigate. D-pad center to select.
Choose your installation options (I selected System on NAND, Data on NAND). Don't choose any other option unless you know what you're doing.
Install it! (if it ask you to wipe the data, select yes).
Wait for the installer to finish.
The menu should appear again.
5. INSTALL THE SPECIFIC UPDATES FOR POLARIS
Due to particularities in our devices, some hardware like Wi-Fi and Bluetooth won't work properly if you don't apply some updates first.
You will need a file an androidupdate.tar to apply to the just installed system.
You can download it HERE (thanks to l1q1d).
When applied, the installer will be shown again.
You now have to select Fix permissions to avoid problems.
Don't exit the installer: soft reset your Polaris instead.
YOU ARE DONE! Your Android system will boot after some minutes.
Things that should WORK:
Phone calls: incoming/outcoming
Texting (SMS)
Data connection (GPRS/3G)
Wi-Fi
GPS
Bluetooth
Things that DON'T WORK:
USB Storage Mode
USB debugging is unstable.
Tethering
Camera (in Eclair)
Headset
Bugs/Issues:
Sometimes Wi-Fi hangs while is being disabled and prevents the device from suspending correctly (it won't sleep and the screen will turn of every time you press a button).
Data connection goes down from time to time and it won't reconnect until you go to the Modem application, disconnect, connect again and wait it to connect.
Audio Input: faulty and unusable with most of applications that use it.
* Enjoy and feel free to donate to our GREAT developers.
* I donated to our developers, and I'm from Spain. As everybody know, Spain is falling like a fainted Pokémon thanks to Zapatero (Mr. Bean II). If I can donate, how couldn't you do it?

I'm trying now.. Sorry my english...

They state that it's valid also for HARET:
if you're doing it with haret, extract basefiles to your sd, plop the androidinstall.tar into the same folder, and boot, hold down volume up just like the nand people (but don't pick nand to store the files, it won't work)
Click to expand...
Click to collapse
I've tried with the specified basefiles and plemen's Android 2.1, but I had no luck.
I noticed that when I press run from HARET and the progress bar fills up, it vibrates two times. Then, it seems that the device is hung, but after 15 seconds (or more), it boots. However, I didn't complete the rootfs-less setup process. It complaints about this:
Unable to open persistent property directory /data/property errno: 2
Click to expand...
Click to collapse
Anyone?

Wait, does this mean its totally an Android ROM? If so, COOL!

haven't tried yet ^^
Did you take the last package on sourceforge for the Eclair 2.1 Build? The files on Mediafire was corrupted.
I think there is no speed improvement with this, it's "only" an easier way to install and upgrade the system.
This is NOT "totally an Android ROM".

i can't install with this method
is there a "how to" or forum thread somewhere cause i get
sh: 2: unknown operand
losetup: /dev/block/loop1: No such file or directory
Failed
Failed to reach system.img on SD Card
Click to expand...
Click to collapse
during setup it complains "cant create folder /system cause file already exist"
i put basefiles at the root of my sd card and the vogue .tar in a folder call /andboot
all taken from here http://sourceforge.net/projects/androidhtc/

I think that you must flash a nbh that only works in vogue yet. I try to flash but it stop at 33%. I think that we must wait.

luzbel_es said:
I think that you must flash a nbh that only works in vogue yet. I try to flash but it stop at 33%. I think that we must wait.
Click to expand...
Click to collapse
Yeah, same problem. It's impossible to flash now with any package for Vogue or Kayser...
We have to wait for DZO's work to port .tar and . NBH for us...

Hi fellas:
I carried out research about the new boot up method, and it seems it will be compatible with our beloved Polaris. But it still needs some fine-tuning, first of all due to the fact that the new installer is started holding down VolUp, but this button isn't correctly recognized with the current bits.
In other words, we should wait before trying out this one. Vilord is aware of this issue.
Stay tuned!

Hi SuperJmn,
Of course I wait for ...
I look every day in the Vogue/Kaiser thread and hope we can to flash our Polaris next time.
Thanks.

Android should work much more faster after flashing... Can't wait to try this

manu33xtro said:
Hi SuperJmn,
Of course I wait for ...
I look every day in the Vogue/Kaiser thread and hope we can to flash our Polaris next time.
Thanks.
Click to expand...
Click to collapse
Hey
I have pola100 with pcar latest non-3d, Im trying my luck to get android started but with the latest files (img, rootfs, zImage) I am not able to. tried hell lot of combinations.
can you suggest me which one would I use, I downloaded some from sourceforge!
but I read that the new rootfs is for nand....
please friends guide me to right downlaods and versions for a near perfect android installation
Thanks in advance....
Niranjan

Hi! The new method is not only for NAND, but also for SD booting. It has some incompatibilities, so it's working for Vogue for the moment (Vogue owners are a bit more lucky than us in terms of development).
We are waiting for @vilord, @DZO and other authorities to fix the appropriate files.
I will contact them right after I end up writing this

Updated information for NAND boot. Thanks DZO!

Can you give us some feedback? Does it run better, smoothier than before? Or nothing about that?

it work but this resolution is not userful for me. No more speed than haret method, wifi and camera not work, system freeze some times. Do you have this problems?

How to put device in bootloader
Hello,
I've installed Android on my POLA100 (NAND method). Until now it's working fine. When I tried to put my device in bootloader mode, after installing Android, surprise... the combination (camera button pressed + stylus reset) isn't working.

If you used this: Eclair build you should download this update too: update for qvga and put androidupdate.tar from this archive on the andboot folder on your sdcard near androidinstall.tar.
After installing the system like SuperJMN said you'll have to press the power button one more after system reboot and choose update... from the menu,then quit when the menu reappear.
WIFI,Camera,Bluetooth doesn't work on this build(the only one I've tested with this new method)
Thank you SuperJMN for posting this,I hope it will remain for a long time on the front page and many thanks to DZO,VILORD,JAMEZELLE,PLEMEN and all other guys for the hard work.

Polaris
Hi,
for polaris you push power button, and boot menu works(NAND and SD).
The issue is that Wifi is not working now.
I try several builds.
So it seems not depending on the system?
Regards

How to put device in bootloader
Solved it. I put my device in bootloader by pressing the camera button + stylus reset when Android loads. I don't know if it worked because I removed my SD card and on the screen appeared "Waiting for SD card" but in that moment I've reset the device in bootloader.