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 ?
I was attempting to flash my ROM to wm6 crossbow, I used Lokiwiz 02b to CID unlock my G3 wizard. Then, I attemped to flash the rom using the RUU. The Shelltool .exe never finished flashing the rom (even after 1.5 hours), so I disconnected the USB and tried to re-sync Windows Mobile Device Center (using Vista 32) as per the directions, but it would not detect the phone. I then entered bootloader mode and tried to run the RUU that way, but vista crashed the program if no sync connection is found. So, I downloaded the latest t-mobile ROM, and flashed the phone through bootloader (curiously the flash seemed to work using t-mo's RUU) and it installed to 100%. However, the phone will not get past the white splash screen. This is what it displays:
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.26.10.2
I tried to un-rar the tmobile exe to a new folder and replaced the nk.nbf file with the file from the crossbow ROM. The t-mo RUU wouldnt read it properly and it crashed. Now the phone is sitting on my counter with it's battery pulled out for fear it mat discharge completely. Since i can get into bootloader mode with the "USB" display at the bottom, I know the device isn't bricked, but what can I do to get it up and running and hopefully flashed to wm6 crossbow? Thanks for any help!
snootch said:
I was attempting to flash my ROM to wm6 crossbow, I used Lokiwiz 02b to CID unlock my G3 wizard. Then, I attemped to flash the rom using the RUU. The Shelltool .exe never finished flashing the rom (even after 1.5 hours), so I disconnected the USB and tried to re-sync Windows Mobile Device Center (using Vista 32) as per the directions, but it would not detect the phone. I then entered bootloader mode and tried to run the RUU that way, but vista crashed the program if no sync connection is found. So, I downloaded the latest t-mobile ROM, and flashed the phone through bootloader (curiously the flash seemed to work using t-mo's RUU) and it installed to 100%. However, the phone will not get past the white splash screen. This is what it displays:
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.26.10.2
I tried to un-rar the tmobile exe to a new folder and replaced the nk.nbf file with the file from the crossbow ROM. The t-mo RUU wouldnt read it properly and it crashed. Now the phone is sitting on my counter with it's battery pulled out for fear it mat discharge completely. Since i can get into bootloader mode with the "USB" display at the bottom, I know the device isn't bricked, but what can I do to get it up and running and hopefully flashed to wm6 crossbow? Thanks for any help!
Click to expand...
Click to collapse
Well Friend I hate to say it but Using Vista is your problem... The drivers in WMDC are different from those of activesync and thus Vista cannot talk to your phone in bootloader.
Follow this thread here:
Updated!!(10/20/2007) UPGRADE YOUR PHONE WITH WINDOWS VISTA!!! PROVEN METHOD!
Once you complete the steps in that thread, flash the Official T-Mobile Rom. I will be online for the rest of the night so I will walk you through everything if you would like me to. My AIM, Yahoo, and MSN messenger addresses are all at the top of every one of my posts.
First off, let me thank you for your help, as well as the time you have put in the community helping people like me. I had updated the driver before, but I guess several attempted flashed had overwritten the driver. Just now, I followed the link you gave me, updated the drivers, and flashed the T-mobile 2.26 ROM. The problem still remains. The RUU goes to 100%, shows me the finish/exit screen, mu wizard restarts, but hangs at the white boot screen and does not go any further.
Anyone? Need to get this phone up quick, as I am starting a new job soon and need the capabilities. BTW, i'm going to put XP on this laptop in dual-boot and see if I can get the t-mobile ROM to load fully using XP.
snootch said:
Anyone? Need to get this phone up quick, as I am starting a new job soon and need the capabilities. BTW, i'm going to put XP on this laptop in dual-boot and see if I can get the t-mobile ROM to load fully using XP.
Click to expand...
Click to collapse
If you can manage that, you will be set. All you have to do is create a hard drive partition and install xp to that partition.(from what I know anyway)
OK, i'm gonna try that (my internet is dropping every 5-10 secs, so it'll take a little time) I do have one question though- Last time I used Loki's unlocker, I unlocked the SIM, then the CID unlocker. After the CID unlocker, it locked me out of the phone. The OS wouldnt load unless I provided an unlock code. Then i reflashed it, then the problems started. I think i didn't have it CID unlocked properly. Plus having my miniSD in the slot probably didnt help things either. I've read the directions several times, and I dont see what i'm doing wrong. Could you maybe shed some light on what i'm doing wrong? Thanks!
EDIT: Also, I forgot to mention that I tried to do a hard-reset (hold wireless manager + voive command buttons + soft reset) and when you press the send button, it tells me unable to format FAT volume or something like that. Upon reading around, it seems like i'm having the exact same problem as this poster: http://forum.xda-developers.com/showthread.php?t=338315
snootch said:
OK, i'm gonna try that (my internet is dropping every 5-10 secs, so it'll take a little time) I do have one question though- Last time I used Loki's unlocker, I unlocked the SIM, then the CID unlocker. After the CID unlocker, it locked me out of the phone. The OS wouldnt load unless I provided an unlock code. Then i reflashed it, then the problems started. I think i didn't have it CID unlocked properly. Plus having my miniSD in the slot probably didnt help things either. I've read the directions several times, and I dont see what i'm doing wrong. Could you maybe shed some light on what i'm doing wrong? Thanks!
EDIT: Also, I forgot to mention that I tried to do a hard-reset (hold wireless manager + voive command buttons + soft reset) and when you press the send button, it tells me unable to format FAT volume or something like that. Upon reading around, it seems like i'm having the exact same problem as this poster: http://forum.xda-developers.com/showthread.php?t=338315
Click to expand...
Click to collapse
Although,many have successfully flashed using vista,but I'll suggest in your condition flash through WinXP. Download the official carrier's Rom from it's website.
1. Disconnect your phone from the usb cable,shut down any firewall,disable any Anti virus,Reboot your PC.
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. On your PC Open windows Task Manager...>Tab Processes...>wescomm.exe...>End process
4. Power off the phone completely (Not stand-by,shut off completely),or you may take the battery out for few seconds
5. Make sure your phone is not Connected to the PC via USB cable and remove the dummy Sdcard or mini-Sd card
6. Get your phone into Bootloader mode (Multicolor screen) by pressing camera button + Power on button
7. Reconnect your phone to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Be sure that your battery is charged over 70%)
8. "USB"will appear on the bottom of the screen of the Bootloader (Multicolor screen)
9. Run the Upgrade again and it will work fine without any problems.
10.Never use Bluetooth sync for the Upgrade
While upgrading, the ActiveSync program will not go on, however the upgrade is running.Please be patient when you're flashing your device, even if 98%. It can wait a little bit, 5 ~ 7 minutes.
Don't cancell the flash or get the phone off the usb cable till it confirms "Congratulations" or stops with an Error!!!
Hope it'll recover back to it's default status,good luck
I'm going to assume I don't have to CID unlock it until I want to switch from the T-mobile 2.26 ROM? I am about to install XP dual-boot shortly. I'll post my results when it's done. Thank you.
snootch said:
I'm going to assume I don't have to CID unlock it until I want to switch from the T-mobile 2.26 ROM? I am about to install XP dual-boot shortly. I'll post my results when it's done. Thank you.
Click to expand...
Click to collapse
As long as you are going to keep T-Mobile 2.26 on your device or are restoring T-Mobile 2.26, you do not have to CID unlock but should you decide to change to another Rom, you will need to CID unlock.
Good luck on the dual boot. There is a detailed tutorial in my Signature if you would like to take a look at it. After I can restore my crashed laptop, I am going to take care of the dual boot also.(I have to do it again... )
I really want to put WM6 on my wizard, and customize it the way I want it. Do you have any favorite WM6 ROM? All day yesterday I spent trying to add a WinXP partition to my Vista laptop. Not fun. First, I shrank the only partition on the drive (where Vista is installed) using Disk management, the Diskpart.exe to create a new 2.5Gb partition to install XP on. I rebooted the labtop with a XP disk, and installed XP on the partition. After the laptop restarted the first time, it did not come back up (black screen, no CD activity), So I changed the boot options in BIOS to HDD, and the Vista partition responded with "Error loading operating system" on a black screen. So now, i've got a laptop with a corrupted Vista install, A partition with partially installed XP on it, a XP disk that just quits working, and my wizard is shot. Normally something I can deal with if I had my desktop, but unfortunately my entire house is packed up in storage, i'm living in a hotel, and the laptop and phone are all i've got. SO, against my better judgement, I went to the store and bought a Vista home basic upgrade DVD to fix my vista partition, and now i'm back on the net- and going to try anothe XP disk. Whew- what a pain in the ass.
snootch said:
I really want to put WM6 on my wizard, and customize it the way I want it. Do you have any favorite WM6 ROM? All day yesterday I spent trying to add a WinXP partition to my Vista laptop. Not fun. First, I shrank the only partition on the drive (where Vista is installed) using Disk management, the Diskpart.exe to create a new 2.5Gb partition to install XP on. I rebooted the labtop with a XP disk, and installed XP on the partition. After the laptop restarted the first time, it did not come back up (black screen, no CD activity), So I changed the boot options in BIOS to HDD, and the Vista partition responded with "Error loading operating system" on a black screen. So now, i've got a laptop with a corrupted Vista install, A partition with partially installed XP on it, a XP disk that just quits working, and my wizard is shot. Normally something I can deal with if I had my desktop, but unfortunately my entire house is packed up in storage, i'm living in a hotel, and the laptop and phone are all i've got. SO, against my better judgement, I went to the store and bought a Vista home basic upgrade DVD to fix my vista partition, and now i'm back on the net- and going to try anothe XP disk. Whew- what a pain in the ass.
Click to expand...
Click to collapse
It's better if you use 'PartitionMagic' software to create partition and install WinXp,as it has much advanced features as compared to built-in Disk Management.It also has the option to create a partition in the same one partition to install new OS.
I tried that first, too bad it doesnt work in Vista.
Woo Hoo!!! Success!!
Alright! I got it fixed! What I did:
1- Spent $42 on a CID unlocker from: http://www.imei-check.co.uk/m3000unlock.php
After i recieved the files from the via email (about 10 minutes) I ran their unlocker program with the file they emailed me. This CID unlocked the wizard.
2- I flashed button's ROM: http://rapidshare.com/files/18212239/CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
I had to flash it twice until it showed a IPL/SPL of 1.01
3- Followed this post: http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
(make sure you use a blank SD card, as it will require you to format the card to make it useable again after your'e done)
4- Remove battery, and restart phone, BOOM! Button's ROM works fine!
5- Now upgrade to any ROM you like (WM6 etc.)
snootch said:
Alright! I got it fixed! What I did:
1- Spent $42 on a CID unlocker from: http://www.imei-check.co.uk/m3000unlock.php
After i recieved the files from the via email (about 10 minutes) I ran their unlocker program with the file they emailed me. This CID unlocked the wizard.
2- I flashed button's ROM: http://rapidshare.com/files/18212239/CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
I had to flash it twice until it showed a IPL/SPL of 1.05
3- Followed this post: http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
(make sure you use a blank SD card, as it will require you to format the card to make it useable again after your'e done)
4- Remove battery, and restart phone, BOOM! Button's ROM works fine!
5- Now upgrade to any ROM you like (WM6 etc.)
Click to expand...
Click to collapse
Congrats ! that's the easy way.....
Yeah, I got tired of screwing with it, and I did it all in Vista!
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'm not 100% sure this is the correct forum, but since it is very ROM related it didn't feel all wrong to put it in here...)
Hi guys. After som serious flashing of cooked ROMs I decided for some unknown reason that I should try to restore a stock ROM. Now, being very tired as I was, i completely forgott that its probably a good idea to flash a new Stock ROM on the unit BEFORE flashing it with a signed SPL....so I just flashed the Signed SPL to the device. That in it self seem to have gone ok, because when I start the unit it say "SPL-1.15.0000". Problem is though that it also says "Upgrade ROM error, please try again"
Now, what should I do? Have tried put both signed and unsigned SPLs on the storage card and started up via the volume down/pwr button thingy, but that does not seem to do anything. I have also tried to attach the unit to a USB port when in tricolor mode ("USB" shows up on the screen) and tried the CustomRUU program. It finds the device and starts to "upgrade" (grey screen on the device with 0%) but then it just doesnt seem to get any further...
As the device was working fine with a custom ROM before I started all this, I suspect that the main problem proably is that I now have a Standard SPL with a cooked ROM, and that they collide sort of. I, as well as the Blackstone, is now stuck and I am all out of ideas what to do? Have also tried Hard and Soft resets, but that doesnt seem to change anything.
Help!
try removing the SD Card and put the phone into bootloader mode and re-flash the stock ROM! if this doesn't work ... still with the SD Card removed try flashing to USPL and flash the stock ROM again!
hope this helps
You can try USPL on your HD and flash a custom or stock ROM with it.
PapaDocta said:
try removing the SD Card and put the phone into bootloader mode and re-flash the stock ROM! if this doesn't work ... still with the SD Card removed try flashing to USPL and flash the stock ROM again!
hope this helps
Click to expand...
Click to collapse
Thanks for the feedback!
Just be be sure, "into bootloader mode" is when you start the device holding down volume down and powerkey until you see the tricolor screen? Then that is probably what I have tried to do for a while now without success (total success that is, I do get into the tricolored screen)). Or maybe I am doing something wrong, could you perhaps point to a detailed explaination besides the one in "HardSPL" thread?
USPL I havnt tried, will do that! Is it still so that trying to do USPL on Vista is asking for trouble?
I read somewhere that Stock ROMs should only be flashed from internal storage, not SD cards, is that true? If so, how do I go about accessing that storage now when it doesnt show up in the file explorer on my PC (PC recognizes it as USB device, "HTC Sync" but I get no file access to it).
improwise said:
Thanks for the feedback!
Just be be sure, "into bootloader mode" is when you start the device holding down volume down and powerkey until you see the tricolor screen? Then that is probably what I have tried to do for a while now without success. Or maybe I am doing something wrong, could you perhaps point to a detailed explaination besides the one in "HardSPL" thread?
USPL I havnt tried, will do that! Is it still so that trying to do USPL on Vista is asking for trouble?
Click to expand...
Click to collapse
just do uspl it will work
improwise said:
Thanks for the feedback!
Just be be sure, "into bootloader mode" is when you start the device holding down volume down and powerkey until you see the tricolor screen? Then that is probably what I have tried to do for a while now without success (total success that is, I do get into the tricolored screen)). Or maybe I am doing something wrong, could you perhaps point to a detailed explaination besides the one in "HardSPL" thread?
USPL I havnt tried, will do that! Is it still so that trying to do USPL on Vista is asking for trouble?
I read somewhere that Stock ROMs should only be flashed from internal storage, not SD cards, is that true? If so, how do I go about accessing that storage now when it doesnt show up in the file explorer on my PC (PC recognizes it as USB device, "HTC Sync" but I get no file access to it).
Click to expand...
Click to collapse
bootloader mode is when you power off the device and hold the volume button down and press power till you get the tricolor screen...
so here is what you need to do .
1. remove the sd card
2. go into the tricolor mode connect your device to the pc and make sure it says (USB) at the bottom
3. run the stock shipped exe from you pc
if that didn't work then you should try the USPL version.. and there is a guide if you are using vista.. i just tried and worked fine.. here it is
http://forum.xda-developers.com/showpost.php?p=3331078&postcount=153
and the reason i'm asking you to remove the sd card because if you have a rom (blacimg.nbh) it won't let you do anything it will try to flash from the sd card and right now you don't want to do that.
and you shouldn't put any rom into the internal storage of the phone..
PapaDocta said:
and you shouldn't put any rom into the internal storage of the phone..
Click to expand...
Click to collapse
What happens if you do that? will it try and flash over the flash? Proper *&@! it up?
nicelad_uk said:
What happens if you do that? will it try and flash over the flash? Proper *&@! it up?
Click to expand...
Click to collapse
i don't think anything would happen... the file will get deleted when you flash as the rest of the files in the internal memory
Thank you everyone! The USPL thing solved it, when I did it from a XP machine! The once bricked Blackstone is not alive an kicking again!
About USPL, I saw the workaround for Vista, but downgrading a few components to make it work just doesn't seem like a safe way to do it. And I cant help but to think that it might have unwanted side affects, ie affecting system stability. But maybe I am wrong?
Going back to shipped ROM without bricking?
Hi,
After reading this thread I am now a bit worried and, as a newbie, would appreciate maybe a "simple" answer to my question.
I''ve been experimenting with various cooked ROMs after following the guide in the WIKI for installing HardSPL and then putting the ROM file (BLACKIMG.nbh) on my SD card and installing it using the power on + volume down button method.
However, I now want to revert back to the original "shipped" ROM, which I have downloaded from the list of shipped ROMs via the WIKI (I downloaded the one which closely matched what was originally on my HD - as I didn't know how to backup the actual ROM on my HD at the time).
So, my question:
How should I put the downloaded original/shipped ROM:
RUU_BlackStone_HTC_WWE_1.14.405.3_Radio_52.49a.25.26_1.09.25.14_Ship.exe
into my HD without bricking it?! Do I just run it on my PC with ActiveSync enabled or do I need to do something to remove the HardSPL or something first?
Sorry if this has been answered previously but I get confused when a thread just makes loads of references to SPLthis and SPLthat etc.!
if you have the HardSPL already installed on your phone then you don't need to do anything more.. just connect your phone to the pc and let it sync (activesync enabled) and flash to any shipped rom you want by simply running the exe file..
PapaDocta said:
if you have the HardSPL already installed on your phone then you don't need to do anything more.. just connect your phone to the pc and let it sync (activesync enabled) and flash to any shipped rom you want by simply running the exe file..
Click to expand...
Click to collapse
Brilliant! Thanks for the simple answer Worked no problem!
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!!!