Related
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 ?
Damn... I walked around and around and solution was all near me and able to do it myself...
Ok here´s how I done it.
First, I must explain what was the problem.
After update the firmware (not actually upgrade, I had the phone full of trash, so I decided to reflash same firmware v2.18 PTG), the Qtek 9100 / HTC Wizard freezed at 2nd splash screen (the one that shows OS versions IPL version, ect). Tried many different versions, upgraded to 2.24, 2.25, downgraded even to 1.6.7.3, but always same problem, freezed on second splash screen. I read many topics on xda-dev, and seen some people with same problem. Apparently there was 2 solutions. 1- send phone back to warranty. 2- write backup ROM from SD in bootloader.
Passed more then 15 hours asking for this SD backup everywhere, and COULDN´T find any help. Apparently no one had this "SD dump ROM Backup".
So here´s how I solved my problem
1- I tought that a SD backup was needed, and yes it is. But u can use your own phone and your own SD to do it.
2- Get a clean SD card (in qtek 9100 / Htc Wizard case is MiniSD) with 128MB (some people say 64MB, but I personally used a 128MB, maybe a 64MB is enough)
3- Kill (task manager) wescomm.exe (this is related with activesync installed on your PC). Insert the blank SD card on the phone.
4- Get your phone in bootloader mode. Like this : Phone powered off, press Camera button + Power On, will enter in bootloader mode (RGB screen).
5- Now connect your USB cable to your phone. And start MTTY_updateROM.exe (http://wiki.xda-developers.com/uploads/romupdate.rar). After open, on Port selection, choose \\.\WCEUSBSH001 and press OK. A window will open with a blank sheet.
6- Type "r2sd all" and hit enter... wait to the end (at end shows "cmd>"). On your phone screen u can follow backup progress... small bar will appear down the RGB screen.
7- Power off the phone (or remove battery), enter bootloader mode (camera button + power on) and this time RGB won´t appear right away. Will ask if u want to "download SD image", press voice dial button to agree, and writting will begin. Wait to the end. Power off and power on normally. Now your phone should be working ok. Not even needed to reflash the phone after this.
Thanks to all and hope this helps more people with this problem
I can get the MDA in a bootloader mode with the RGB screen but I can't figure out how to get the SD Image Boot. When I open updateROM, it only gives me the seletion of COM1 and COM3. I can't gete any farther, help plz. i really want to use my MDA
Adam
Adam, you missed a step
Kill wescomm.exe as described in step 3 and you will be able to access via USB.
3- Kill (task manager) wescomm.exe (this is related with activesync installed on your PC). Insert the blank SD card on the phone.
not work with me; so sad what i can do?
I did all yr step till n7 but after i roobot same problems;it frozeen on the page where show IPL SPL GSM OL;
ANY SUGGESTION?please help me
@nnnike i had the same problem as you did. ( getting stuck at the first splash screen) i jsut tryed this right now and greatly enough it did work !!! give it another shot it migh twork with you
i actually used my 2gig mini SD it wasnt clean ither
thank you so much for posting this Drug_Store. and for whoever worked on this. u guys are awsome
I did exactly what you do, but
Ive got message from Multi port tty:
r2sd all
***** user area size = 0x3BA00000 Bytes
R2SDBackup() - Download type = 5
usTotalBlock = 1 sizeof(SDCARD_SIGNATRUE_TABLE)=512
You didn't get the proper security level to download a specific image
Cmd>
So, what is the next step? And did I doing something wrong?
You didn't get the proper security level to download a specific image
Cmd>
So said:
i also got the same error
Click to expand...
Click to collapse
CID unlock?
I believe that your phones aren't CID unlocked.
I think that only CID unlocked phones or inputing the BOOTLOADER password will allow to backup wizard to SD card
I've got the exact same problem, phone freezes at splash screen. Now I backed up a rom from a working cid-unlocked wizard, but after I tried loading it on my wizard it says 'don't allow update'. So what can I do now?
Awesome solution! My MDA vario is back from the dead!
Thank you for sharing this great solution with us
Thanks my phone is back!, now how can I get to use tha card again? I dont have a card reader for my pc, just the phone. Is ther something that I can use, because my device dont get any storage Card.
Rafase282 said:
Thanks my phone is back!, now how can I get to use tha card again? I dont have a card reader for my pc, just the phone. Is ther something that I can use, because my device dont get any storage Card.
Click to expand...
Click to collapse
I was forced to buy a multi-card reader to get my card back Fortunately that they are so cheap these days (less than 12€ for 31 diff cards)
Funny thing is that after formatting the card in Win2k the phone still asks if i wish to restore image when entering bootloader mode
cheers
hi
did you slove this your problem ?
i also got the same error
It stoppped asking to restore image when entering bootloader mode maybe because i've been using the card in normal PPC operations and the "r2sdall" area must have been overwritten
Yes, data remain at SD card. Probably need to insert in SD card reader and format under windows system.
About the errors while reading the data to SD, I remind, to try in a fully clean SD card (formatted completly), and yes, might require that your phone be CID unlocked, but that part can also be done easily.
The data that is written on the SD will remain hidden, and are like system files. That´s why no one can share the needed files over the internet or download somewhere. Because can´t get the files out of there. However, if u seen in your file explorer in your phone some file might appear on card root. But also not sure if can copy it from there and later apply on a card and do this procedure.
tjmvdz said:
I've got the exact same problem, phone freezes at splash screen. Now I backed up a rom from a working cid-unlocked wizard, but after I tried loading it on my wizard it says 'don't allow update'. So what can I do now?
Click to expand...
Click to collapse
Hello I think there is no way to restore a Sd backup on CID locked device.
I think the only possibility is to unlock CID with Imeicheck site (the process begin in bootloader mode) and then restore Sd image.
fla242;1114868
I think the only possibility is to unlock CID with Imeicheck site (the process begin in bootloader mode) and then restore Sd image.[/QUOTE said:
How it can be made?
Click to expand...
Click to collapse
Thanks a TON for the help. I went on with a little diff solution. Went upto step 4 and got the bootloader and then installed the new update from O2 and it worked.
(The step 5-7 somehow didn't work for me so I did this and it worked.)
hi all
i got problem to unlock cid on bootloader (other than imei check site)...
please help.
thanx
Hi i have a mda vario 1 ipl and spl 1.06 i have got it unlocked whit a code thad i have got from t-mobile but this don't work for me i get the message: ***** user area size = 0x3CA0000 Bytes
R2SDBackup() - Download type = 5
usTotalBlock = 1 sizeof(SDCARD_SIGNATRUE_TABLE)=512
You didn't get the proper security level to download a specific image
what can be the problem can anybody help me
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.
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.
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