Related
Maybe some of you are already aware of this procedure, maybe not.
Anyway, it worked for me and I decided to share how to do it. Simple.
This procedure should only be used in case you really need enter into a bootloader mode and all other ways to do it has failed! Hold Camera button is one of these I am mentioning.
My Wizard was almost bricked at that time and after I speak with an I-mate technical guy, I got the following:
1. Make sure your i-mate™ K-JAM is not Connected to the PC and remove the dummy card or SD/MMC card
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. Reconnect your i-mate K-JAM to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t use the IrDA or Bluetooth for the Upgrade)
4. Run the Upgrade again and it will work fine without any problems.
While upgrading, the ActiveSync program will not go on, however the upgrade is running.
Hope it helps!
this realy worked for my (ex)bricked dutch tmobile mda vario !!!!
tip: REALY make shure that there is no wcescomm.exe running all the time and realy remove the sd card else is nogo
btw: my wizard is CID locked! and works like a charm
Thanks buddy!
I'm happy that worked for ya!
Take care!
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Hi!
Have you already flashed your device once?
Which ipl/spl do you have?
I had problems over 1.05 ROM in the beggining.
If you stuck on bootloader mode, that's a good signal your device is not bricked.
I'd recommend you to disable activesync as you did and reflash it again! Check also if your device is CID unlocked! Search for a thread in the xda developers root.
Try to upgrade to ipl/spl 2.26 first and later to others you want.
Regarding the old file error...can be related to a missing file called enterbootloader.exe.
Hope it works for ya!
Take care
Ironman273 said:
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Click to expand...
Click to collapse
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Sounds great to hear that!
I had play around with pdaviet3, underground and another ROM just today without any problems at all. I don't think that this is the case. Now you get your device back to normal, try to reflash it again. Hope it works this time!
BTW,...São Paulo is a nice city. Thanks! Let me know if you decide to come here!
Take care
Ironman273 said:
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
Click to expand...
Click to collapse
It seems you got the idea!
You did the right thing! Sometimes, use the official ROM can solve many issues out there!
Keep walking!
enlite_de said:
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Click to expand...
Click to collapse
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
In my opinion this thread is so helpful to people who brick their device, it should go "sticky". Mods anything you can do about it?
Thanks buddy! I really appreciate!
We survive here over tips like that!
jt_armstrong said:
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
Click to expand...
Click to collapse
Help me similar problem
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Hi there!
It seems that you just need to enter into the bootloader mode and reflash it again!
I had similar problems and more during my brick "false" stage!
So, just try to follow my steps here and you should be fine! Once you get into bootloader mode, just use any ROM out there to reflash.
Good [email protected]
thaiphong said:
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Click to expand...
Click to collapse
I was about to start a EMERGENCY HELP thread, but I *think* this is the right place instead.
The "touch" of my screen went dead today. It got progressively worse over a few hours, starting with difficulty in using the phone dialer, then random incorrect stuff getting triggered by screen taps.
So I hard reset, and got no response on the fifth alignment cross, meaning 1) "Tap on the screen...; 2) center; 3) top left; 4) bottom left; 5) bottom right. In that I could not proceed with alignment, I hard reset again, and now, at the first alignment screen, i.e. "Tap on the screen...", I have no screen response at all.
I called T-mo, and they are being great about sending a replacement ASAP (and getting me a loaner in the meantime).
BUT, I am running Faria+ AKU3.3 V2... so I clearly have to flash back to T-mo 2.26. I can;t figure out how to do it though, as no matter what I do I am stuck at the first alignment screen!!
HELP!! EMERGENCY!!!
(I have three or four days to get this done, so it's not THAT urgent)
Do a search for Broken Screen. Someone (either in Wizard Upgrading or in the Wizard forum) just had a similar issue with a cracked screen. They downloaded something that allowed them to get around the welcome page.
Actually, if you are just trying to flash a new ROM, don't even mess with it. Go straight to the Boot Loader screen (see the first post of this thread). No tapping necessary until the new rom is on (and that will be the Tmobile then so you would be good.
Thanks for the quick reply. Charging up to green now, and then will try to enter bootloader and flash T-mo 2.26. Will report back.
Worked great. Back to T-mo she goes!!!
BootLoader Mode
Excellent thread but you left out one thing.....exactly how to place your device in bootloader mode.
To clear up any misunderstanding because this is very important....this is how you do it:
Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up .... That's it !!!!!!
When the unit is connected, USB is displayed at the bottom left.
Hey there everyone, I am pretty new to this forum so I must apologize for throwing you all into the deep end. I recently purchased an o2 XDA mini S second hand from a guy on boards.ie here in Ireland. I got the phone and really liked it because it allowed me to get rid of my Dell Axim X3i and mp3 player and keep it all in one device.
After a little bit of more research I discovered that I could remove some of the bloatware from the o2 xda mini S by just hard resetting and choosing the basic option which I than did. Still not satisfied with the overall performance of the XDA I decided to try a rom upgrade. Not wanting to do a totall overhaul I decided to just do a radio upgrade first.
My device is sim unlocked, it was like that when I bought it. I used the latest wizard service tool to CID unlock the device before I even flashed the phone. I also used the wizard service tool to change the nk.nbf file within the o2 mini S radio update into 96000000-GSM.nb. I then used this file to write to the GSM radio code (Bdk 1) according to the wizard service tool in the hopes that it would upgrade my radio version.
Well when I restarted, nothing of the sort happened, on the boot screen I noticed I was now missing my GSM version and when the phone finally got into windows mobile, it did not pick up any signal even though beforehand it could. The phone also became super slow to the point where it was unusable.
I have gone into bootloader mode subsequently after reading on this forum and tried to reflash with a number of updates with active sync disabled and nothing else running with the phone connected via usb to the pc. None of the updates would even pick up the phone or allow me to flash it.
My phone is pretty much screwed, I have a spare so it is not that big of an issue but I would like to make this usable again if at all possible. So my question is how do I flash a rom while the phone is in bootloader mode?
P.S I forgot to include the Current boot screen details:
IPL - 1.05
SPL - 1.05
OS - 1.5.4.2
Hi,
You can use the Wizard Love Rom from here http://rapidshare.com/files/17792050/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar
Hey there, thanks for the advice, I did download that ROM but like I said before, none of the roms manage to flash my XDA because they all cannot seem to connect to it. Activesync does not even pick it up in windows mode, and even when I have it connected in bootloader mode via usb and I double click on the love rom, it goes through the motions but never managed to "verify the information with the pda"
Try a stock Tmobile ROM but not from bootloader. Also, I would check the activesync app on the device. Make sure it's set to use USB as the default connection method.
A few other steps to try...
Uninstall ActiveSync and install an older version. If still no go, try a newer version.
Try a different USB cable and/or USB port.
Try a different computer with XP, not Vista.
Try flashing it without the SIM card or any memory cards.
If all else fails, you can try the SD card flashing method. There are instructions in the Wiki on how to do it, but always a stock ROM.
Try this one... http://forum.xda-developers.com/showthread.php?t=311027
Updated IPL/SPL and radio 2.69
Hey Devis, I think I have come one step closer, I tried all the suggestions that you made. Except well now my phone will not even go into the operating system when I switch it on. It will boot and the version numbers show but then it just resets itself.
I tried a different usb cable and I am not using vista, tried a different pc and the same result. The one place I did have some marginal success was the sd card method.
Basically what happened is that It backed up the OS from my phone and then reloaded it, not exactly what I wanted since the OS and rom are both screwed on the phone so my question at this point is, is there anyway using the SD card method to load one of the stock roms onto my phone?
I searched around the net and found the opposite to the "r2sd all" function, would be the "s2d" function, would that allow me to flash the phone with a stock rom?
Thanks for your time, I am going to call it a night here in ireland and head to bed.
Ok, if the phone resets then you probbably have a dead/dying battery. Charge it for about an hour or so using the wall charger, not the USB cable. Try to restart it and see if you can get in the OS. I was looking in the SD card method thread and some guy was successful at restoring the image from the SD even though his OS had died. He then had a fully functional phone.
The other thing to do would be to get the image file from someone that has a living and breathing wizard, preferably one with a stock ROM. Since this method is the equivalent of making an image of a PC using Ghost, the restoration of such an image to your Wizard should work just fine.
Just make sure that the other Wizard is SIM and CID unlocked. Or just go buy a Wizard from the store, unlock SIM and CID, copy the image on the SD and flash your device. Or... since u've got a new Wizard in your hands, just take the freaking thing appart and swap the guts return the store bought wizard to the store saying that the thing just doesnt freaking work!
As for the AT commands... it is possible that s2d would workfor you, it doesn't work in my wizard. from what i have been reading it appears that the bootloader is password protected and that password is randomly generated. I haven't played long enough with it to figure out how to get the password.
It looks like you've got some "trial and error" processes ahead of you. There is a wealth of info on bootloader AT commands on Wiki, nothing for the Wizard though. But something may work... not sure.
I could try to get you a ROM dump from my Wizard but I already am on SPL/IPL 3.08 and running WM6. the SPL/IPL version alone wouldn't allow you to restore from my backup.
Hey Devis, thanks for your time, just woke up here, will work some more on the phone today and let you know what is going on
Hey Devis, I did not even get a chance to fiddle around with the phone today, from being able to switch on less than 24 hours ago, it does not even want to switch on now so I am going to officially declared it a brick and move on. Will see if anyone can fix it for me, spent way too much time already when I should be working on my dissertation, thanks alot anyway
Sorry to hear that...
I have bricked one phone myself in the past... my old Pana GD87 and I absolutely loved that phone. I know how you feel.
Good luck with your dissertation.
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!
Here is the deal: I was running the leaked WM6 ROM for ATT, I tried to downgrade to WM5 again, but my device got bricked, it was always failing to finish the update.
so, i ran the recovery tool from PALM, and it came back up but...when I go into the settings, there is no software version listed, basically just some little squares characters. But I still tried to run the WM6 updater but it keeps saying "device unsupported". After reading many threads on this forum, I went ahead and changed the payloads.xml version from 1.13 to 2.25, and still no result.
Any other ideas? I have also tried the SD recovery or updater and nothing, the bootloader screen doesn't give me the option to start the upgrade and when I go back into the SD card, i see a PALM.o and .h file, meaning that the system tried to compile it.
Of course, the card was formated several times into FAT32. Bad card maybe??
So, what should I do?
thank you
Sounds like you've tried about everything known to the Treo. There are some other things that may work in the other HTC threads, but no guarantees and may make things worse. Since you got it back to WM5, can you warranty it? Not sure how long you've had it (what carrier/country you're in), but always worth a shot to go to your provider's store and see what magic you can work.
Good luck mate!
Hey everyone. I'm tearing my hair out trying to get this sorted but I just don't know what to do!
So, when I got my X1 as everyone on here should do, was flash my X1 with the HardSPL and some custom roms, this was a few months back. Then, shock! Horror! My case went and broke, (cracked near the volume button build W44) so I sent it back to SE for repair. I sent it back reset back to defaults but left the hardspl on there.
SE sent me a brand new phone (I think... This one says under the battery build w50, but the battery says w32..) I received it today. I thought it would be my old one repaired but SE had other ideas. Booted up and have Image Version: 1.03.931.10 and HardSPL 72.000 I think I said that correctly...
Now since sending it for repair and receiving it back, their seems to be quite a few wm6.5 roms floating about, and obviously I can't use the stock software as that wouldn't be right!
Now I have tried flashing the hardspl to the phone through my Vista PC and all it keeps giving me is connection errors. I thought maybe it was already flashed so I tried flashing just a rom, and that just made the phone get stuck on loading (flash by memory card). I thought it might be Vista, so I tried doing it on my other PC (XP) and I get the same issue. This bloody thing won't flash!
I have had "Connection Problems" - "Update Errors" with different numbers. The current one being Error [260] CONNECTION.
Now I have been searching around through the hardspl thread and other places trying to find out what I need to do or how I can fix it, but everything I try doesn't make a difference. I did read some other people with recently repaired phones having the same problem and perhaps SE have put a new spl thingy-ma-jiggy on there. (Please forgive the technical jargon, I have no idea what im on about.) I have also tried the ticking/unticking advanced network functionality, but that hasn't made a difference either.
So by the end of typing this, I have little hair left. Let's hope you can all help, before I have none left!
I would appreciate ANY help! Really.
Just wanted to add, I was at first getting the phone to a loading bar when flashing, but it would stay at 0% then flag up an error on the PC. Now after the tri-colour bars, the phone just sticks on Loading...
Well just to update. I have been trying to sort this since posting. I flashed the rom to an old UK generic one, as I read in another topic people had to do that before HardSPL. Done that, and tried flashing the hardspl. Same thing, just getting connection errors.
I tried going into bootloader and running the hardspl from there. It works and the phone gets to 10% and then gives an UPDATE ERROR. The phone is now bricked, and I have to reflash the original wm rom to get it back.
Though the Tricolour screen now shows 0.52.Olinex
Any ideas?
Shameless bump for help.
very stupid situation.
i have the same situation in puncto of flashing.
i get my phone three month ago.
after hardspl i .... sorry, no hardspl ... the phone says at 0% bla bla bla
i solve the problem by consulting one night absolutly stressing again and again and again .... google ... xda ... google
than 3 thinks at one time was the solution:
0. need activesync - connect !!!!
1. SDA_ApplicationUnlock.exe for desktop pc
2. enterbootloader.exe for pocketpc (please, the right version, it exist for eten too, but we need the xpediaversion ..)
3. changing registry-entries
how to:
activesync-connect, than copy "enterbootloader.exe" to pocketpc. it must be root, not sd-card. use a pocketpc-registry-program to change these values :
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001001 = 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001005 = 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001017 = 144
HKEY_LOCAL_MACHINE \Security\Policies\Policies\0000101b = 1
if not exist than add the key.
now, start desktop-program, follow instruction EXCEPT reboot.
start "enterbootloader.exe" on pocketpc. now, you can install hardspl and the device is flashable for ever.
thats works on me, hope it could help you too.
Thanks for the reply. Not had time to try it till this morning. Ok so, after spending about an hour trying to find the correct enterbootloader.exe I finally realized, that the hardspl package includes it. *Duh!* So that was time wasted.
I changes the registry values as you said with Resco registry editor, and follower the unlock then enterbootloader.exe Start HardSPL package. Starts to install. Gets to 10% then I get
ERROR [262] : UPDATE ERROR
The rom update utility has encountered communication errors during the update process.
So im open to suggestions if anyone has any. I just can't understand why it's not working. It's not a problem with my computer or cables. I flashed the phone before I sent it for repair and I have tried doing it on two computers one with XP 32bit and one with Vista 64bit.
hmm. would u like to install a custom rom, or a stock rom?
msg me, and i hope, i can halp u.
I want to have the hardspl on there so I can flash custom roms.
If it's a case of the software/firmware/hardspl whatever you call it, has been updated by SE. How would one go about getting it flashed? Would we have to wait for an update HardSPL to be released?
U read this thread?
My first hardspl was from this thread. New X1 will come tomorrow back from SE (vibration was defect +++ some more problems with case), and i will try it again with this thread.
hope, this will help u mate.
Yeah, I have been through that thread with a fine toothcombe trying everything suggested to see if I can make it work.
When you get yours back, if you have to do anything out of the ordinary to get it to flash or can't do it. Please come and let me know in this thread. If they have updated yours like mine, and yours won't flash, at least I won't be the only one!
k, i will msg u tomorrow around 2pm.
Cheers.
In the meantime. Does anyone have any other suggestions I could try?
Bump, for some help.
now i know, what is exatcly your problem.... <--- SAME Problem
i hope, i will find a solution and msg u then. if u´ll got a solution for this prob, msg me too plz.
Solution found in this Thread!
Download this and unzip it to your device. ++ run it. It will start your X1 in Bootloader menu and say "0.52.OliNex".
Then start hardspl while X1 is in Bootloadermenu....
FINISH =)
Thanks for the reply matey. Glad you got yours sorted. Just tried what you said and I get 0% then it switches to ERROR [262] : UPDATE ERROR.
vwrmic said:
Thanks for the reply matey. Glad you got yours sorted. Just tried what you said and I get 0% then it switches to ERROR [262] : UPDATE ERROR.
Click to expand...
Click to collapse
hmmm... it works fine on my new x1. are u sure, that u start the ssplmanual on your x1 and not on your computer?
Yea, im not sure what the problem was with it. Thankfully I have it done and dusted today! Because I flashed it earlier to an older official version, and you said you got it working. I presumed you had - had yours flashed to the newest version due to it being off for repair. So I reflashed the official update and fully updated it. Then tried hardspl which didn't work. Tried with the advanced USB thing off, tried again with how you said you did it above, and Viola!
Hip hip hoorah! Thanks for the help. Can finally use me bleedin phone now!
no problem mate hf with your x1
hello,
i see smilies and yea's ...
for me to understanding (for next time or other users):
1. complete official update (if exists)
2. flashing (hardspl) without "advanced usb"
thats all?
cool.