Updating to 6.1 - Palm Treo 750 ROM Development

I pretty much read through all these 6.1 threads and have really not found the answer. So I must ask. I downloaded the update along with the CheetahUnlocker. I got through the the first two steps of the unlocker and then on the last reboot of the device, it just sits at the "rainbow" screen with a couple version # and USB or Serial at the bottom (depending on cable connect), no update starts. My 2gb card is installed and FAT32. There are other folders on the card, but at the root is CHEEIMG.nbh. Am I missing a step? I'm guessing it's not getting unlocked properly due to me booting in the loader and normally setup should start, being that the file is in the root of the FAT32 card. A little guidence would be apprieciated. Thanks

Really? 21 views and no help. Come on please?

trublu01 said:
I pretty much read through all these 6.1 threads and have really not found the answer. So I must ask. I downloaded the update along with the CheetahUnlocker. I got through the the first two steps of the unlocker and then on the last reboot of the device, it just sits at the "rainbow" screen with a couple version # and USB or Serial at the bottom (depending on cable connect), no update starts. My 2gb card is installed and FAT32. There are other folders on the card, but at the root is CHEEIMG.nbh. Am I missing a step? I'm guessing it's not getting unlocked properly due to me booting in the loader and normally setup should start, being that the file is in the root of the FAT32 card. A little guidence would be apprieciated. Thanks
Click to expand...
Click to collapse
It IS importand what version numbers you see. Second one (SPL) should end with OliNex or you don't have hardspl. I'm always using blank card with only file CHEEIMG.nbh . You can also try using KaiserCustomRUU updating way (the only one I'm using lately).
Ok, what I worte was in case you have HardSPL and want to flash rom. If you're stuck in cheetahunlocker process, do to system partition (usualu C and delete CheeTemp (or cheetmp) catalog. Then run whole process again.
And if you're updating or unlocking from pc, it is not bad idea to put card out of Treo.
All those if-cases are caused by what you wrote. I don't get what are you doing or you don't (you write about cheetahunlocker nd cheeimg.nbh at this same time - it doesn't make sense for me)...

Thanks. Looks like I bricked it. It just sits at the Palm startup screen. I've tried to hard reset with no luck.

What different steps have to be performed when using the KaiserCustomRUU? What I meant was I downloaded the CHEEIMG.nbh and the CheetahUnlocker. The CheetahUnlocker never displayed any version. I don't remember what error had come up, but I could not go further after the reboot after Step 2, nor could I find any instructions on what to do from that point on. Should I not have to use the lokwiz program? So when I get my replacement. What is the first thing I should do? hell, all the steps would be apprieciated. Thanks

trublu01 said:
What different steps have to be performed when using the KaiserCustomRUU? What I meant was I downloaded the CHEEIMG.nbh and the CheetahUnlocker. The CheetahUnlocker never displayed any version. I don't remember what error had come up, but I could not go further after the reboot after Step 2, nor could I find any instructions on what to do from that point on. Should I not have to use the lokwiz program? So when I get my replacement. What is the first thing I should do? hell, all the steps would be apprieciated. Thanks
Click to expand...
Click to collapse
You got your rainbow screen. Write down all numbers. That's first step.
To unbrick you can try to flash with any official rom.
To flash using kaisercustomruu rename cheeimg.nbh to RUU_signed.nbh, put to one folder with kaisercustomruu.exe and run it. When you don't have working rom on Treo, put into bootloader ("rainbow") and then run ruu.

miloszz said:
When you don't have working rom on Treo, put into bootloader ("rainbow") and then run ruu.
Click to expand...
Click to collapse
as in KaiserCustomRUU?

Well I tried it and the RUU displays ver 1.23.707.6, then I click update. The phone goes to grey screen with percentage and gets ERROR 270: Image File is corrupt, Check your update utility. I've tried this with 2 different nbh files, renaming them to RUU_signed.nbh and placing them in the same folder as the KaiserCustomRUU.exe. I DO NOT have the MiniSD card in.

Ahhh, anyone?

Does one HAVE TO update the radio? Will the default one still work?

HA! I see what I was doing wrong, after running step 1 and step 2 of the CheetahUnlocker. I had no idea I was supposed to put the card in with the nbh file. I Updated OS to 6.1. How does one upload a new radio? Is there a better one than the standard ATT radio? Also after OS is said and done. Do I need to do anything else? Thanks again.

Related

HELP!!! Stuck at Boot Screen. NEED SD IMAGE FILE

Hope you guys can help me out. I disassembled my Cingular 8125 to try and improve the earpiece speaker. I put the device back together and turned it on and it sticks on the boot screen.
When I try to do a hard reset, I get to the point where I have to press send (green button), but then displays the following for a second and then goes back and freezes on the boot loader screen:
format FAT partition
format is complete
I've read some stuff about being able to recover from this using the SD card, but I'm not sure how to do it. If it is possible to recover from SD card, can someone please upload the appropriate files to the ftp site?
Please HELP!!! My ROM versions are below:
IPL: 2.16
SPL: 2.16
GSM: 02.07.10
OS: 2.16.9.1
Thanks!!!
Update:
I'm able to get to the mutli-colored screen by holding the Camera Button prior to starting the Wizard back on. I plug in my USB to my computer, but my computer says "USB Device Not Recognized". How can I get a new ROM on to my device? I tried running the ROMUpdateUtility.exe from a ROM, but it obviously wouldn't work because my computer doesn't see my phone. Please help!!
Thanks!!
Update #2:
When connected to the computer, I got to device manager and see an unknown device under USB. I uninstall the device and do a scan for hardware changes. This finds the phone, but it still shows up as an unknown device. It does say that device is ready to use, but when i try to run the ROM update utility, it still cannot find my phone.
Do I need special USB drivers for the phone to be recognized?
Please guys, any help would be greatly appreciated!
Thanks!!!
you shouldnt need any special driver for your computer to connect to Wizard.
did you install ActiveSync at all ? perhaps its using the driver from that installation....
What OS are you using ?
Yes, I've previously installed ActiveSync 4.1. I am using Windows XP. Would it help to try to uninstall/reinstall ActiveSync? I may give that a try. Will keep you posted. Any other suggestions?
EDIT:
Just tried to uninstall/reinstall ActiveSync and it still says USB device not recognized
it looks like a dead ROM, hope it has nothing to do with the hardware.
Anyway, you try looking through this forum, there are some people who've got stuck on the boot screen, and did a flash (via the bootloader screen, e.g. the multi colour one) on the ROM and seems to fix the problem. Probably you want to put this option last. Mean while, wait for others to repsond, and you may well start looking on how to flash the ROM from bootloader screen.
hanmin said:
it looks like a dead ROM, hope it has nothing to do with the hardware.
Anyway, you try looking through this forum, there are some people who've got stuck on the boot screen, and did a flash (via the bootloader screen, e.g. the multi colour one) on the ROM and seems to fix the problem. Probably you want to put this option last. Mean while, wait for others to repsond, and you may well start looking on how to flash the ROM from bootloader screen.
Click to expand...
Click to collapse
Thanks for responding. I'm ok with having to reflash, but the problem is that my computer doesn't seem to recognize my device when i'm at the multi color screen.
Isn't there a backup battery in these devices? I had my Wizard disassembled for 4 hours. I guess the backup battery could have died during this span, but even if it did, what implications would that have?
You still have hope
Get it to the bootloader screen. Connect via USB to your PC (make sure you have active sycn installed) and run an RUU to replace your ROM. I had to do this after trying to downgrade to the original Cingular ROM on my 8125. Scared the S*!T out of me when it hung on the Splash screen and wouldn't load. I thought it was toast but using the Bootloader and an RUU it put it back to normal again.
It won't look like the PC is recognizing the device but it will as long as its in Bootloader.
Let us know if you get it fixed.
Re: You still have hope
hellomoto_25 said:
Get it to the bootloader screen. Connect via USB to your PC (make sure you have active sycn installed) and run an RUU to replace your ROM. I had to do this after trying to downgrade to the original Cingular ROM on my 8125. Scared the S*!T out of me when it hung on the Splash screen and wouldn't load. I thought it was toast but using the Bootloader and an RUU it put it back to normal again.
It won't look like the PC is recognizing the device but it will as long as its in Bootloader.
Let us know if you get it fixed.
Click to expand...
Click to collapse
Thanks for the reply. The problem is that when I plug the device into my computer, I get a USB device not recognized error. I try to proceed with ROMUpdateUtility.exe anyways, and get this error:
"The update utility cannot connect to your PDA phone..."
Seems like updating via USB is not going to work for me. Can I write a backup to the SD card from the PC, put the SD card in the phone, and then boot from there? I've read some posts along these lines, but detailed steps would be very helpful. THANKS!!!
You need an SD card dump image.
This is NOT a file in the sense of a file on the SD card. Its a RAW image. You need someone who has dumped their firmware in that fashion to send you the SD image.
You then write it onto the SD card using something like "psdwrite" (which will, by the way, DESTROY the filesystem on the SD card - don't have anything on there you care about!) and then insert it into the phone with the power off. Hold the CAMERA button and turn it on; when it asks if you want to restore the image, hit VOICE.
Note that for 1.x IPLs/SPLs the backlight will be OFF during this procedure, so you have to pay attention and/or have a good flashlight handy.
Genesis3 said:
You need an SD card dump image.
This is NOT a file in the sense of a file on the SD card. Its a RAW image. You need someone who has dumped their firmware in that fashion to send you the SD image.
You then write it onto the SD card using something like "psdwrite" (which will, by the way, DESTROY the filesystem on the SD card - don't have anything on there you care about!) and then insert it into the phone with the power off. Hold the CAMERA button and turn it on; when it asks if you want to restore the image, hit VOICE.
Note that for 1.x IPLs/SPLs the backlight will be OFF during this procedure, so you have to pay attention and/or have a good flashlight handy.
Click to expand...
Click to collapse
Genesis3,
Thanks for your wonderful insight. I really appreciate your help.
Now can someone help me with getting an SD image? What constitutes an image file? Is it simply the .nbf file? Do I just use psdwrite and copy the nbf file onto the card? Is there something on the FTP site I can use? My configuration as mentioned in the original post is:
IPL: 2.16
SPL: 2.16
GSM: 02.07.10
OS: 2.16.9.1
I had a similar problem and reflashing the rom using the usb is possible. Don't use a flasing utility, though.
Find a self contained rom upgrade from the FTP. As long as you see USB on the bottom left side of your screen, it should work. After that, reflash with whatever rom you want. Hope it works. Nothing worse than an the feeling you have holding an expensive paper waight.
wireless_one said:
I had a similar problem and reflashing the rom using the usb is possible. Don't use a flasing utility, though.
Find a self contained rom upgrade from the FTP. As long as you see USB on the bottom left side of your screen, it should work. After that, reflash with whatever rom you want. Hope it works. Nothing worse than an the feeling you have holding an expensive paper waight.
Click to expand...
Click to collapse
Thanks for the reply. I'm not sure what you mean by "self contained rom". In the past, I've used K-JAM_WWE_216901_2169101_020710_ship.zip from the FTP site, and ran the ROMUpdateUtility.exe without any problem. Now, since I cannot make a connection to the computer via USB, I am unable to run ROMUpdateUtility.exe. Is there an alternative "self contained" file I can use that will work in spite of the unknown USB device message?
Thanks in advance...
try to DL this file: RUU_Prodigy_1060701_101_11310_QTEK_WWE_Ship.exe. Its on the FTP. Follow this link:
http://wiki.xda-developers.com/index.php?pagename=BA_FTP_Site
click on the FTP Root link, navigate here:
ftp://ftp.xda-developers.com/Wizard/Roms/Qtek/ and download the file. Put the phone in bootloader, attach to PC (make sure the phone has USB shown in the bottom left corner, and run the file.
Ignore any references to ActiveSync or any connections period. Just run it all the way through the installation process. When all is done, you can upgrade, down grade, etc using the appropriate method (I use aWizard) Let me know if this helps.
Wireless One
wireless_one said:
try to DL this file: RUU_Prodigy_1060701_101_11310_QTEK_WWE_Ship.exe. Its on the FTP. Follow this link:
http://wiki.xda-developers.com/index.php?pagename=BA_FTP_Site
click on the FTP Root link, navigate here:
ftp://ftp.xda-developers.com/Wizard/Roms/Qtek/ and download the file. Put the phone in bootloader, attach to PC (make sure the phone has USB shown in the bottom left corner, and run the file.
Ignore any references to ActiveSync or any connections period. Just run it all the way through the installation process. When all is done, you can upgrade, down grade, etc using the appropriate method (I use aWizard) Let me know if this helps.
Wireless One
Click to expand...
Click to collapse
Thanks for your reply. I've tried the course of action that you've suggested, but i cannot get through the installation process because of inadequate connectivity between the phone and my PC. I see the USB in the bottom left hand corner, plug into the PC, and immediately see a USB Unknown device error. I ignore that and try to run the ROM anyways and it fails and I get an Update Error:
"The Update Utility cannot connect to your PDA Phone. Please check that your USB/cradle is connected..."
That's why I think I got to go the SD card route, so anyone with an image file that i can put on my SD card, I really could use the help!
It is NOT a NBF file.
The problem with the 8125 is that if you are somehow not CID unlocked the wrong SD image will actually hurt you more than it helps.
You need to find someone with a Cingular 8125 SD image - I have one for the T-Mobile MDA but not for the Cingular "as-shipped" ROM.
Genesis3 said:
It is NOT a NBF file.
The problem with the 8125 is that if you are somehow not CID unlocked the wrong SD image will actually hurt you more than it helps.
You need to find someone with a Cingular 8125 SD image - I have one for the T-Mobile MDA but not for the Cingular "as-shipped" ROM.
Click to expand...
Click to collapse
Genesis3,
Thanks for confirming it's not a NBF file. I had previously CID unlocked using awizard and then installed a newer IMATE ROM:
IPL: 2.16
SPL: 2.16
GSM: 02.07.10
OS: 2.16.9.1
I did not install the IMATE Extended ROM or Cingular customizations after upgrading to the IMATE ROM. Do I still need a Cingular 8125 SD image, since i've already upgraded my ROM, or do I now need an IMATE SD image to match my current configuration? Or does the type of image file really not matter?
Thanks in advance!
I really hate to beg, but I am desparately seeking an SD image file backup. I'm going out of town in a couple of days, and would love to have a working wizard for my trip.
Can any one of you kind souls please upload your SD image file backup to the FTP site? It really is my last ditch effort before having to send the phone back.
I truly appreciate all the help and all the responses I have received to date.
THANKS!!!
sunil23 said:
I really hate to beg, but I am desparately seeking an SD image file backup. I'm going out of town in a couple of days, and would love to have a working wizard for my trip.
Can any one of you kind souls please upload your SD image file backup to the FTP site? It really is my last ditch effort before having to send the phone back.
I truly appreciate all the help and all the responses I have received to date.
THANKS!!!
Click to expand...
Click to collapse
Sunil,
i apologize for not responding your PM sooner but wasnt available due to travel plans.
I am trying to upload the files to the Upload folder now and i iwll let you know when i am done.
Thanks
getting permission denied when i tried to upload the documents.
is there another password i should be using besides xda/xda ?

[TUT]Flashing the easy way

Hey everyone!
Read lots of threads here on the xda-developers forum, many questions, many answers, lots of "good guys" who are willing and able to help (many have helped me, thank you goes to them and all the others).
The bottom line:
Saw many many questions concerning flashing, bad flashes, error messages and so on.
I really don't know WHY people won't go for the easy way?
Flashing from a PC involves a USB connection through Activesync/WMDC, an application, we all know the procedure thanks to racerx_ (http://trinityguides.info). There are so many things that can go wrong: think about it, from unplugging the device, app error, comm error, power drop, connection drop, system hang and so on.
I don't know about the rest of you but I have done it the hard way but also learned to do it the easy/safe way. There's nothing more to the story than flashing from SD card. Procedure is well described in the Wiki (http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing).
I mean, all you have to do is press three buttons and wait for the flash, no risky connection drops, error messages, driver incompatibilites (see Vista problems), no app hangs.
I have tried many ROMs from over here and except for my first two flashes (first was Des' Crash Proof SPL, second was a cooked ROM) I've made them all using the SD card method and never got an error nor a situation with it.
So here's the question: why won't people flash the easy way?
well, have you actualy tried this procedure before posting this?
banesi said:
well, have you actualy tried this procedure before posting this?
Click to expand...
Click to collapse
Read my post once again, carefully.
hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom
This procedure brings boot loader screen, with three colors, it doesn't bring anything similar to that image posted there.
banesi said:
hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom
This procedure brings boot loader screen, with three colors, it doesn't bring anything similar to that image posted there.
Click to expand...
Click to collapse
Follow the steps carefully.
1. SD card with FAT32 and no label (it can contain other files, no need to wipe it)
2. Renamed nbh file to TRINIMG.nbh placed on SD card root
3. Power+Camera+Reset
4. Follow instructions on screen (Power button to brgin flash and Soft reset when prompted at the end).
It don't get any easier!
It SHOULD work.
Totally agree, I don't understand why ppl persist with the multitude of errors that crop up from flashing via active sync.
Using the SD card you can chuck a few ROMs on board to test and just rename each in turn to TRINIMG.nbh, move it to the SD root and enter boot loader.
Before I test a new ROM I make a static settings image with SPB Backup so I can flash back to the old ROM and restore back to how it was in a jiffy.
Just to point out for some ppl, some of the ROMs here are packaged into EXEs, you will need to extract the contents and only use the file named RUU_signed.nbh.
This process can also be used to flash Radio ROMs in case you flash a ROM that includes a radio that you don't like/use.
Good thread
P3600i saga continues
I wonder if the SD Card method works on the P3600i? According to the Wiki, it doesn't bypass the SuperCID check.
Olipro has modified his SPL-Trin to work with the P3600i. But so far there's still no definite way to flash it. No Hard-SPL, splxploit don't work, same for JumpSPL. So maybe this is the way? Any opinions?
remofo said:
I wonder if the SD Card method works on the P3600i? According to the Wiki, it doesn't bypass the SuperCID check.
Olipro has modified his SPL-Trin to work with the P3600i. But so far there's still no definite way to flash it. No Hard-SPL, splxploit don't work, same for JumpSPL. So maybe this is the way? Any opinions?
Click to expand...
Click to collapse
No, sorry, it's not the way.
Flashing from SD card is not a workaround for bypassing SPL.
You still have to have some kind of a Hard SPL installed.
Please check the Wiki.
evojulz said:
This process can also be used to flash Radio ROMs in case you flash a ROM that includes a radio that you don't like/use.
Click to expand...
Click to collapse
...and also bootscreens.
In other words, this method can flash any nbh file which could be flashed through the update utility method.
Easy and reliable
Fully agree with you tnyynt!
I always flash using the SD method.
Sometimes I even download the new nbh and keep it on the SD and upgrade later on when having time, not connected to a Pc... (I also have all the cab I need on my SD card).
Quick, easy and reliable (done many times).
Would be fine if the nbh would be released on this forum (rather than the .exe package).
Would allow to download them directly from the Trinity. i.e.: no more need for a Pc !!!
I always use this method, it is the only one that works for me and it's the most convenient I think.
I tried this method several times, but I was never able to get it work.
Yes I followed instructions carefully, but no. I only get three colored bootloader screen, that's it. No button to start flashing, nor screen that looks like that photo in wiki.
I really wanted this to work, cause I have an OsX. Since I couldn't get it to work I had to install xp and use it as virtual machine. From there everything works just great. Because of that, I still have to have windows on my laptop :-(
Speed
About this method: is it faster, same or slower than usb? (consider an average SD card, no high-speed)
Sure SD is faster
g77 said:
About this method: is it faster, same or slower than usb? (consider an average SD card, no high-speed)
Click to expand...
Click to collapse
I flashed recently FinixNOver 3.0.2 (BTW - superb ROM) - only OS + splashscreens and it took 2.5 mins in SD (regular 2GB miniSD SANDISK). I think it is fast enough...
Hi!
I want to tell me,if anybody knows, if i make my device superCID i loose the waranty!
I try to flash it with Trinity_SDCard Flashing from wiki (i make 3 step) and after the reset when is in the grey screen and loading i saw in the up side of screen the number 00068002 and after that change to 3 colored screen!
Any help?
jukkus said:
I tried this method several times, but I was never able to get it work.
Yes I followed instructions carefully, but no. I only get three colored bootloader screen, that's it. No button to start flashing, nor screen that looks like that photo in wiki.
I really wanted this to work, cause I have an OsX. Since I couldn't get it to work I had to install xp and use it as virtual machine. From there everything works just great. Because of that, I still have to have windows on my laptop :-(
Click to expand...
Click to collapse
me second, i also have tried many times and still just can go to the tri-color screen.
i am using hardspl 1.20, and a 4GB sd card with fat32, will these matter?
thanks.
manos_23 said:
Hi!
I want to tell me,if anybody knows, if i make my device superCID i loose the waranty!
I try to flash it with Trinity_SDCard Flashing from wiki (i make 3 step) and after the reset when is in the grey screen and loading i saw in the up side of screen the number 00068002 and after that change to 3 colored screen!
Any help?
Click to expand...
Click to collapse
yes, super-cid will void the warranty.. use hard-spl.. there's no reason to super-cid your device if you're flashing cooked roms..
racerx_ said:
yes, super-cid will void the warranty.. use hard-spl.. there's no reason to super-cid your device if you're flashing cooked roms..
Click to expand...
Click to collapse
Ok, and thank's you very much!
ctrlaltdel said:
me second, i also have tried many times and still just can go to the tri-color screen.
i am using hardspl 1.20, and a 4GB sd card with fat32, will these matter?
thanks.
Click to expand...
Click to collapse
Interesting, I'm sure someone will shoot me down but I'm not convinced it works with all SDHC cards... is your 4GB SDHC?
I can't get it to recognise the NBH from my 8GB but I have flashed many times successfully from my 2GB. Not to bothered, as long as it works
Nope, I'm using 2Gb normal sd-card. Also tried 512Mb card.

HELP: Flashing CHT9110 (P3600i)

I really need all the expert out there to help me on flashing my CHT9110. I'm not sure if flashing CHT9110 is the same as flashing P3600i?
Anyway there is an instruction post by ajajaj and credit to Olipro for the great help. I follow every step stated by ajajaj but still I couldn't get my phone flash to WM6.1, therefore I'm pleading for help here.
Step 1 - Anyway First of all, load the Hard SPL to your phone from : http://forum.xda-developers.com/showthread.php?t=398742
Click to expand...
Click to collapse
From my understanding I need to download the Hard SPL, but what does it mean by load the Hard SPL to your phone? Does it mean I unzip the hard spl and double click ROMUpdateUtility.exe on my PC? I tried to double click anyway and my phone boot to tri-color mode, there my phone get disconnected, doesn't matter I press power, camera button, and push the reset button and my phone start in tri color, again I run the ROMUpdateUtility.exe and this time it run and finish 100% but after that it return an Error[270] Image corrupted.
Then I ignore this first step and proceed to following steps
Step 2 - So, what I did was to download RUU_TRINITY_WM6.1_WWE_ASIA_3.12.YK.Lite extract into its own folder (Mary seems to work as well)
Click to expand...
Click to collapse
Yes I downloaded
Step 3 - then download the custom ruu updated from here: http://forum.xda-developers.com/showthread.php?t=295113 - also get the rombaker for trinity as found further down in the post.
Click to expand...
Click to collapse
Also downloaded
Step 4 - unzip the custom_ruu stuff, put in the downloaded trinity rombaker to replace extracted rombaker,
Click to expand...
Click to collapse
I unzip the rombaker and custom ruu. I overwrite the rombaker into custom ruu/workshop folder
Step 4a - Copy ruu_signed.nbh file that is found in folder created in Step 2 to the rombaker/workshop folder created in step 4
Click to expand...
Click to collapse
I copy the ruu_signed.nbh from WWE_ASIA folder to custom ruu/workshop
Step 5 - then use nbhextract (created in step 4) to extract the ruu_signed.nbh file that is now in the workshop folder
Step 6 - watch the output. (for file names)
Click to expand...
Click to collapse
I extract it and get 00_OS.nb as output
Step 7 - Run the rombaker program and load the extracted files into their places (as referred to in step 6), then click generate NBH
It will ask you to save a file. call it new_nbh (or whatever you want) -
Click to expand...
Click to collapse
I run the rombaker and I fill IPL, SPL, OS, ExtROM, GSM, SubSplash, MainSplash with 00_OS.nb and name the file called new_nbh. So I get new_nbh.txt as the output.
Step 8 - open this file (created in step 7) in notepad, and change the number 400 (about 5 lines down) to 401 save and exit
Click to expand...
Click to collapse
I open with text editor and change the last line to 401 from 400 as below
TRIN100
SuperCID
ROMBaker
XDADevelopers
100,00_OS.nb
200,00_OS.nb
600,00_OS.nb
601,00_OS.nb
900,00_OS.nb
300,00_OS.nb
401,00_OS.nb
Step 9 - then open a dos/cmd/command.com window (whatever you want to call it), cd to the rombaker/workshop folder and then run the following:
nbhgen new_nbh.txt
NOTE: new_nbh.txt should be the same as the filename created in step 7
Click to expand...
Click to collapse
I did exactly been instructed here
copy the generated RUU_signed.nbh file back to the RUU_TRINITY_WM6.1_WWE_ASIA_3.12.YK.Lite folder.
Your p3600i rom is now ready for flashing
Click to expand...
Click to collapse
I copy the ruu_signed.nbh from workshop folder back to RUU_TRINITY_WM6.1_WWE_ASIA_3.12.YK.Lite folder and run the ROMUpdateUtility.exe
After all the next next thingy, it turn black and doesn't go into the tri color. Tried to push power, camera, and reset button and boot in tri color, run the ROMUpdateUtility.exe again it stop at 1%
Can anyone tell me where I went wrong?
Thank and appreciate all your help.
wssoo said:
I really need all the expert out there to help me on flashing my CHT9110. I'm not sure if flashing CHT9110 is the same as flashing P3600i?
Anyway there is an instruction post by ajajaj and credit to Olipro for the great help. I follow every step stated by ajajaj but still I couldn't get my phone flash to WM6.1, therefore I'm pleading for help here.
From my understanding I need to download the Hard SPL, but what does it mean by load the Hard SPL to your phone? Does it mean I unzip the hard spl and double click ROMUpdateUtility.exe on my PC? I tried to double click anyway and my phone boot to tri-color mode, there my phone get disconnected, doesn't matter I press power, camera button, and push the reset button and my phone start in tri color, again I run the ROMUpdateUtility.exe and this time it run and finish 100% but after that it return an Error[270] Image corrupted.
Then I ignore this first step and proceed to following steps
Yes I downloaded
Also downloaded
I unzip the rombaker and custom ruu. I overwrite the rombaker into custom ruu/workshop folder
I copy the ruu_signed.nbh from WWE_ASIA folder to custom ruu/workshop
I extract it and get 00_OS.nb as output
I run the rombaker and I fill IPL, SPL, OS, ExtROM, GSM, SubSplash, MainSplash with 00_OS.nb and name the file called new_nbh. So I get new_nbh.txt as the output.
I open with text editor and change the last line to 401 from 400 as below
TRIN100
SuperCID
ROMBaker
XDADevelopers
100,00_OS.nb
200,00_OS.nb
600,00_OS.nb
601,00_OS.nb
900,00_OS.nb
300,00_OS.nb
401,00_OS.nb
I did exactly been instructed here
I copy the ruu_signed.nbh from workshop folder back to RUU_TRINITY_WM6.1_WWE_ASIA_3.12.YK.Lite folder and run the ROMUpdateUtility.exe
After all the next next thingy, it turn black and doesn't go into the tri color. Tried to push power, camera, and reset button and boot in tri color, run the ROMUpdateUtility.exe again it stop at 1%
Can anyone tell me where I went wrong?
Thank and appreciate all your help.
Click to expand...
Click to collapse
First up you are way ahead of me in getting to the stage where you have been able to modify the nbh, well done.
I am not sure this ROM works even after being modified, but you can give it a go.
To flash the modified ROM.....first put your phone into bootloader mode...ie camer..power and soft reset. It should come up with the tri-colour screen and show SPL Olipro 3.2. something. If it doesnt show Olipro then the Hard SPL you did earlier didn't work.
If it does...connect back to your PC via the USB cable and then run ROMupdate. It will then go through and flash the phone.
All the others have said this ROM flashes and then hangs at the boot screen.
Good luck...let us know how you go.
don't use that ROM... it doesn't work
go HERE to see the ROMs that have been tested and work with the P3600i
there's only 2 (tested) ones there, but at least they work
if those ROMs don't work, i don't know what will - i've tested both myself and they work fine
like andych said, make sure your bootloader (3 colour screen) says Olipro 3.2 on it, to make sure you have HardSPL... otherwise you haven't put that on yet - if you haven't do it again, then flash with a ROM from the link i gave
If I run the ROMupdate when I'm in WM it show
TRIN100
IPL-1.00
TRIN100
SPL-olipro 3.20
But if I boot into the bootloader mode, and I see
TRIN100
IPL-1.00
TRIN100
SPL-3.03.0000
am really confused on how to go about it
joncgde2 said:
don't use that ROM... it doesn't work
go HERE to see the ROMs that have been tested and work with the P3600i
there's only 2 (tested) ones there, but at least they work
if those ROMs don't work, i don't know what will - i've tested both myself and they work fine
like andych said, make sure your bootloader (3 colour screen) says Olipro 3.2 on it, to make sure you have HardSPL... otherwise you haven't put that on yet - if you haven't do it again, then flash with a ROM from the link i gave
Click to expand...
Click to collapse
I just wanna be sure, with the 2 given ROM, I need not do any changing of 400 to 401, and etc? Just run the ROMupdate and everything will run smoothly?
OK
You need to run Hard SPL again.
Connect to your PC and make sure activesync has run properly and your phone is on.
Open Hard SPL and run the ROMupdate. Your phone will go to tricolour and it will come up with a communication error.
disconnect from PC but leave the phone in tricolour....DO NOT reset it.
Cancel our of the ROMupdate. connect the phone to the pc again and run ROMupdate again.
This time it will go all the way through and you will have HardSPL on your phone.
Check it by entering bootloader and it should show Olipro 3.2.
You can then flash away....make sure you always put the phone into bootloader before flashing.
Let us know how you go.
Ok once I get communication error, I disconnect from PC, cancel the ROMUpdate, then I reconnect to my PC again.
This time do I run the Hard SPL or the rom from ajajaj?
I tried both it however reset my phone to tri color and I dont see olipro 3.2 anymore
wssoo said:
Ok once I get communication error, I disconnect from PC, cancel the ROMUpdate, then I reconnect to my PC again.
This time do I run the Hard SPL or the rom from ajajaj?
I tried both it however reset my phone to tri color and I dont see olipro 3.2 anymore
Click to expand...
Click to collapse
You need to run the ROMupdate from HardSPL again......
Only when you have Olipro 3.2 on the bootloader can you run the ajajaj ROM.
Guess it is really giving me a big headache.
Here is my scenario
My phone is on, I connect to activesync and run harl spl romupdate
My phone boot into tri color mode with SPL-3.10.olipro
Then I get error ERROR[260]: Connection
I exit
Disconnect phone from PC
Now comes the part that seems like only I'm the one facing problem.
I connect my phone back to my pc. My phone still in tri color mode I still see SPL-3.10.Olipro
Now I run the romupdate for hard spl again
I see the loading bar but I'm stuck at 0%, then my phone restart and reboot in tri color, now I see SPL-3.03.0000
Alright fine, I reboot on my phone connect to pc run hard spl romupdate till I get Connection error. Now I close romupdate and disconnect from PC.
I reconnect and run the ROM Mary instead. Again failed.
Did I miss any step? Or those are for P3600i and not CHT9110? Any different?
wssoo said:
Now comes the part that seems like only I'm the one facing problem.
I connect my phone back to my pc. My phone still in tri color mode I still see SPL-3.10.Olipro
Now I run the romupdate for hard spl again
I see the loading bar but I'm stuck at 0%, then my phone restart and reboot in tri color, now I see SPL-3.03.0000
Click to expand...
Click to collapse
That's odd. I did what you did - I tried the first time, it failed with the 260 error. I kept the phone in bootloader, disconnected it from the PC, exited and restarted the HardSPL flashing program, and put my phone back in WITH the bootloader still on after that error the came up.
This second time, it worked for me.
If what I have just described does not occur with you, then you cannot flash any ROMs. You MUST succeed with HardSPL first. I don't know what is going wrong for you, I'm sorry Are you using Vista? I only tried on XP.
Also! Watch the screen of your phone the first time you try it from activesync, and make sure security dialogues come up and you approve them. I had to allow them ro proceed.
joncgde2 said:
That's odd. I did what you did - I tried the first time, it failed with the 260 error. I kept the phone in bootloader, disconnected it from the PC, exited and restarted the HardSPL flashing program, and put my phone back in WITH the bootloader still on after that error the came up.
This second time, it worked for me.
If what I have just described does not occur with you, then you cannot flash any ROMs. You MUST succeed with HardSPL first. I don't know what is going wrong for you, I'm sorry Are you using Vista? I only tried on XP.
Also! Watch the screen of your phone the first time you try it from activesync, and make sure security dialogues come up and you approve them. I had to allow them ro proceed.
Click to expand...
Click to collapse
acutally i want to ask after successfully update the hardspl
what number will show?
3.10 or 3.20
mine is 3.20
so strange, but i still can flash to mary rom
joncgde2 said:
That's odd. I did what you did - I tried the first time, it failed with the 260 error. I kept the phone in bootloader, disconnected it from the PC, exited and restarted the HardSPL flashing program, and put my phone back in WITH the bootloader still on after that error the came up.
This second time, it worked for me.
If what I have just described does not occur with you, then you cannot flash any ROMs. You MUST succeed with HardSPL first. I don't know what is going wrong for you, I'm sorry Are you using Vista? I only tried on XP.
Also! Watch the screen of your phone the first time you try it from activesync, and make sure security dialogues come up and you approve them. I had to allow them ro proceed.
Click to expand...
Click to collapse
Well I've tried. The only way for me to accomplish 100% on bootloader is when my phone show SPL-3.02.0000, if I run hard spl romupdate at this point of time, it will complete 100% but sadly after that, it return
ERROR[270]: Update Error
The image file is corrupted. Please check your Update Utility
wssoo said:
Well I've tried. The only way for me to accomplish 100% on bootloader is when my phone show SPL-3.02.0000, if I run hard spl romupdate at this point of time, it will complete 100% but sadly after that, it return
ERROR[270]: Update Error
The image file is corrupted. Please check your Update Utility
Click to expand...
Click to collapse
**Am using Windows XP SP2
i'm sorry, you seem to have a big problem with your phone :/
i don't think we can help you any further - hardspl to get into bootloader the first time, you get the error, you run the program again with the phone in bootloader and the hardspl should complete.
then you can soft reset and it should have 3.20 olipro on the 3-colour screen.
if this doesn't work for you, maybe it won't work at all
wssoo said:
ERROR[270]: Update Error
The image file is corrupted. Please check your Update Utility
Click to expand...
Click to collapse
Which Ruu Update utility did U use? 3.1.3.2 or 3.14.4.1? If you use the one that came with hard-SPL, try using the 3.14.4. U can get this here http://forum.xda-developers.com/showthread.php?t=321182 extract this then change the RUU_signed.nbh with the hard-SPL one, then flash your device as described above.
Argyle0297 said:
Which Ruu Update utility did U use? 3.1.3.2 or 3.14.4.1? If you use the one that came with hard-SPL, try using the 3.14.4. U can get this here http://forum.xda-developers.com/showthread.php?t=321182 extract this then change the RUU_signed.nbh with the hard-SPL one, then flash your device as described above.
Click to expand...
Click to collapse
I'm using the default ruu_signed.nbh that come along with Hard SPL. Unsure what version it is. Anyway I downloaded RUU_TRINITY_WM6.1_WWE_ASIA_3.12.YK.Lite.rar from the net too? Is this you are talking about? I overwrite the ruu_signed.nbh to Olipro's Hard SPL ruu_signed.nbh?
wssoo said:
I'm using the default ruu_signed.nbh that come along with Hard SPL. Unsure what version it is. Anyway I downloaded RUU_TRINITY_WM6.1_WWE_ASIA_3.12.YK.Lite.rar from the net too? Is this you are talking about? I overwrite the ruu_signed.nbh to Olipro's Hard SPL ruu_signed.nbh?
Click to expand...
Click to collapse
Download the RUU_Trinity_DOPODASIA_WWE_3.00.707.18_6275_1.46.30.11_108_Ship.exe then right click to extract (winrar installed). You should see a some files in the directory you extracted to. Find the RUU_signed.nbh, DELETE IT. Then copy the RUU_signed.nbh from the Hard-SPL to the above directory. Run the ROMUpdateUtility.exe.
Sadly I've tried Argyle0297 still getting the same old error msg.
I think it is lock on the SPL or SuperCID is it?
I know how frustrating it is .... this happened to me too.
BUT the one i got is not CHT9110, it's HTC P3600i with chinese rom installed (originally SPL-3.03.xxx). Maybe there's a difference between the two devices. Anyway if you want to give it another try, download the file below. It's the one i successfully used to flash the HardSPL.
Good Luck.
Argyle0297 said:
I know how frustrating it is .... this happened to me too.
BUT the one i got is not CHT9110, it's HTC P3600i with chinese rom installed (originally SPL-3.03.xxx). Maybe there's a difference between the two devices. Anyway if you want to give it another try, download the file below. It's the one i successfully used to flash the HardSPL.
Good Luck.
Click to expand...
Click to collapse
Thank.. am downloading it and will try it right away after work..
Crossing my finger..

260 Error when flashing

I have just bought a P3600 and trying to upgrade to WM6. Been following the various instructions all evening but cant get any further than the same point regardless of which rom I try.
My phone connects up via USB and is detected etc, I click through the screens on the RUU, and then run it. Prompt appears on the phone to run enterbotloader.exe, click yes, and then it goes to bootloader screen, where it doesnt do anything after that. I try rerunning the RUU whilst its still attached at bootloader, and makes no difference. It just sits there on bootloader screen and program on windows comes up with a 260 error.
Any suggestions please as to how to get it to go further?1 Windows XP 64 by the way.
Just update your HTC driver in device manager, that's all.
russthewomble said:
I have just bought a P3600 and trying to upgrade to WM6. Been following the various instructions all evening but cant get any further than the same point regardless of which rom I try.
My phone connects up via USB and is detected etc, I click through the screens on the RUU, and then run it. Prompt appears on the phone to run enterbotloader.exe, click yes, and then it goes to bootloader screen, where it doesnt do anything after that. I try rerunning the RUU whilst its still attached at bootloader, and makes no difference. It just sits there on bootloader screen and program on windows comes up with a 260 error.
Any suggestions please as to how to get it to go further?1 Windows XP 64 by the way.
Click to expand...
Click to collapse
You musst unlock your device CID/SIM unlocker here in the forum
Make My Day! said:
You musst unlock your device CID/SIM unlocker here in the forum
Click to expand...
Click to collapse
I try to do this but I get to exactly the same stage ie it goes to the tri color screen and then the RUU does not seem to be able to detect the phone.
russthewomble said:
I try to do this but I get to exactly the same stage ie it goes to the tri color screen and then the RUU does not seem to be able to detect the phone.
Click to expand...
Click to collapse
Hmm than is the Problem your Window XP 64 Bit system!
Do the upgrade at windows XP 32 Bit version.
I think I'll try and do it via SD card, probably easiest way! Just have to wait for SD card to be delivered :S
I agree. I found the SD card is the easiest way but could not get it to work without using the SSDL posted here on the forum.
This the info is taken form this forum and can not remember who posted it "Thanks any way"
The only thing did not work in my case was the rebooting using the reset button "Ihad HSPL installed". The only way to get it working was by running the SSPL application after setting the SD card as below.
Good luck
Extract the .NBH file from your preferred ROM upgrade: In windows use winrar (right click) to extract
the contents of the exe file. In Linux / MacOS use cabextract
(http://www.cabextract.org.uk/) .
Rename the .NBH file to TRINIMG.nbh and copy it to the root folder of your miniSD card.
With miniSD card inserted on the phone, start the bootloader (hold Power button on right side
and Camera button at same time and stick with stylus in RESET on bottom).
You should see the screen pictured on the left, confirm flashing on screen by pressing the power
button.
Flashing might hang after some time but this is normal. Just wait. Complete flash takes about
30 minutes, so check your battery or connect to charger before the flashing process starts.
When flashing completes soft-reset your device.
Make sure your SD has FAT32 and has no label. There have been reports that if SD has a label the
bootloader can not access the TRINIMG.nbh
Well, i couldn't extract the nbh file from the roms I had, but evenutally found one which extracted to an nbh file. Put it on the SD card, and it worked! Also updated radio using same method so got GPS working as well
If anyone knows of a more up-to-date ROM which an nbh file can be extracted from (or any NBH files available for download!) I would greatly appreciate it as this current rom seems slightly unstable (has frozen a couple of times already).
Rom Version 2.0.1.1
ROM Date: 03/07/07
Radio Version: 1.56.70.11
Protocol version 32.89.7020.20H

Complete stock SPL restore with broken touch screen

I am getting my Tilt2 ready to ship back to AT&T. It has a totally dead touch screen. Now I am stuck unable to get the stock SPL restored because it requires a key press to approve the installation of a program from an "unknown publisher" (the standard ROM warning message).
I've also tried using MyMobiler which works great to show your Mobile screen on your desktop and substitutes mouse clicks for screen taps but I can't get it installed either due to the same limitation above.
Another work around would be a self installing cab that modifies the registry keys in HKLM\Security\Policies\Policies to reflect the elimination of the above warning (but crap this would probably trigger the warning itself...)
In short if anyone has a clever workaround for this last step of fully returning my device to original WITHOUT using the touch screen please let me know.
- You don't have total commander installed or some other registery editor? Then you can edit those values yourself.
Maybe you have thought of this yourself but you didn't mention it And I don't know if it is possible but can't you use your hardware keys to approve the installation?
-----------
Ignore..
Lennyz1988 said:
- You don't have total commander installed or some other registery editor? Then you can edit those values yourself.
Click to expand...
Click to collapse
My device is back to the stock ROM with no reg edit tools installed.
Lennyz1988 said:
Maybe you have thought of this yourself but you didn't mention it And I don't know if it is possible but can't you use your hardware keys to approve the installation?
Click to expand...
Click to collapse
My keyboard works but the Tilt2/Rhodium do not have the variable function keys that are assigned to actions in certain parts of the screen (say like the original Tilt did). That is the main problem. If I had those I would have been done long ago.
Any other ideas? There must be a subtle/clever work around here.... Thanks.
swamp2 said:
I am getting my Tilt2 ready to ship back to AT&T. It has a totally dead touch screen. Now I am stuck unable to get the stock SPL restored because it requires a key press to approve the installation of a program from an "unknown publisher" (the standard ROM warning message).
I've also tried using MyMobiler which works great to show your Mobile screen on your desktop and substitutes mouse clicks for screen taps but I can't get it installed either due to the same limitation above.
Another work around would be a self installing cab that modifies the registry keys in HKLM\Security\Policies\Policies to reflect the elimination of the above warning (but crap this would probably trigger the warning itself...)
In short if anyone has a clever workaround for this last step of fully returning my device to original WITHOUT using the touch screen please let me know.
Click to expand...
Click to collapse
Try This It Might Work For You
Ok - here is a quick step by step for people who want to restore the stock bootloader via SD Card.
1) Download v0.84 bootloader from post 1 in this thread.
2) Rename ruu_signed.nbh to rhodimg.nbh and copy it to your SD Card (Must be 2Gb or less!)
3) Insert your SD card and boot the phone while holding the VolDown button. Flash this image.
4) Upon the next boot, your phone will go straight to bootloader saying "Update ROM Error, Please Try Again".
5) Download any STOCK ROM from the HTC web site for your phone.
6) Run the exe that you downloaded from HTC and then look through the folders in your temporary files for SPL_Signed.nbh.
7) Copy SPL_Signed.nbh to rhodimg.nbh on your SD Card.
8) Insert your SD card and boot the phone while holding the VolDown button. Flash this image.
9) At this stage, remove your SD Card and your phone will either boot or not.
If your phone boots, nothing more is required.
If your phone does not boot, copy RUU_Signed.nbh from the same place you got SPL_Signed.nbh from to your SD Card as rhodimg.nbh and boot your phone while pressing the VolDown key.
This last step is only required if your phone doesn't boot at step 9. It will flash the ROM to your device and should start up as a fresh phone.
Enjoy
^ great, sounds promising. Thanks so much. Are you sure about the 2GB card limit? I tried 6 GB card and it does appear to be a problem. Stuck at "Loading..." (that is all that is on the screen, blue font on a grey background) and it goes there under a normal boot or under entering boot loader with vol down key from reboot. Ugh... Any advice, am I bricked?...
Update. Despite seeming like this did not work it seems it did. To be precise I only got through your steps 1-3. Then to "recover" I simply reloaded the official HTC AT&T ROM (again) with the single (again official) .exe over USB while in boot loader mode. It loaded fine and now claims I have SPL 0.87 (I used that instead of 0.84 figuring there were pretty much identical).
Thanks again! Greatly appreciate the tip!!
swamp2 said:
^ great, sounds promising. Thanks so much. Are you sure about the 2GB card limit? I tried 6 GB card and it does appear to be a problem. Stuck at "Loading..." and it goes there under a normal boot or under entering boot loader from reboot. Ugh... Any advice, am I bricked...
Click to expand...
Click to collapse
I'm Not To Sure About The 2gb Card Limit But Have You Flashed Stock Rom & Stock Radio 1st Before Flashing Stock Spl
Doo Doo said:
I'm Not To Sure About The 2gb Card Limit But Have You Flashed Stock Rom & Stock Radio 1st Before Flashing Stock Spl
Click to expand...
Click to collapse
Yes, before working on getting the SPL back I also previously used the official one step HTC/AT&T ROM restorer which flashed ROM and Radio. 6 GB card must have worked.
I was updating my post as you quoted it...
swamp2 said:
Update. Despite seeming like this did not work it seems it did. To be precise I only got through your steps 1-3. Then to "recover" I simply reloaded the official HTC AT&T ROM (again) with the single (again official) .exe over USB while in boot loader mode. It loaded fine and now claims I have SPL 0.87 (I used that instead of 0.84 figuring there were pretty much identical).
Thanks again! Greatly appreciate the tip!!
Click to expand...
Click to collapse
Well I'm Glad This Worked For You
Your Welcome No Problem
glad it worked!!!

Categories

Resources