Can I avoid customizations loading and why did this happen? - 8125, K-JAM, P4300, MDA Vario Software Upgrading

All -
After playing with the Qtek test ROM for a while, I thought I'd "revert" to a stable release. I grabbed one of the 1.6.7 RUU files (with GR near the end) off the ftp site and installed it. When the MDA rebooted, I got a message about how I'd illegally acquired the ROM and it froze my MDA. Thank GOD that using the bootloader and another RUU installer I was able to recover it.
First, why would the ROM jack me like that? I've used aWizard previously to CID unlock my MDA? Can it relock?
Second, the "screwy" ROM would load, but fail after the customizations were applied and the soft reset occurred. Is there any key combo you can hold down to prevent the Wizard from executing the customizations script? Thanks!!!

After you do a hard reset it runs through the 'welcome to windows' blurb where you learn to cut'n'past and align the screen etc..... At the end of this process is then says 'press the screen to start using this device' (or something like that, after which, there is a 3 seconds delay before it starts running the customisation CAB files. If you press the reset button (soft reset) within this 3 second period is resets the device without running all the customisation rubbish.
I hope this helps and good luck!

Muchas gracias!

Related

Can I avoid customizations loading and why did this happen?

All -
After playing with the Qtek test ROM for a while, I thought I'd "revert" to a stable release. I grabbed one of the 1.6.7 RUU files (with GR near the end) off the ftp site and installed it. When the MDA rebooted, I got a message about how I'd illegally acquired the ROM and it froze my MDA. Thank GOD that using the bootloader and another RUU installer I was able to recover it.
First, why would the ROM jack me like that? I've used aWizard previously to CID unlock my MDA? Can it relock?
Second, the "screwy" ROM would load, but fail after the customizations were applied and the soft reset occurred. Is there any key combo you can hold down to prevent the Wizard from executing the customizations script? Thanks!!!
Nevermind I will try in the other forum.
Re: Can I avoid customizations loading and why did this happ
vettejock99 said:
All -
After playing with the Qtek test ROM for a while, I thought I'd "revert" to a stable release. I grabbed one of the 1.6.7 RUU files (with GR near the end) off the ftp site and installed it. When the MDA rebooted, I got a message about how I'd illegally acquired the ROM and it froze my MDA. Thank GOD that using the bootloader and another RUU installer I was able to recover it.
First, why would the ROM jack me like that? I've used aWizard previously to CID unlock my MDA? Can it relock?
Second, the "screwy" ROM would load, but fail after the customizations were applied and the soft reset occurred. Is there any key combo you can hold down to prevent the Wizard from executing the customizations script? Thanks!!!
Click to expand...
Click to collapse
YES you can, soft-reset just before the customisations start and you will be getting what you want.
Got it. Thanks!

htc wizard boot problems (windows mobile doesn't start)

Hi,
First, I ran some tests on my kjam. The kjam came default with the kjam rom on it, naturally. I wanted to CID unlock this phone, so I downgraded the rom to button's "beer glass" splash screen rom. Then I was able to run aWizard successfully to CID unlock the phone. I then upgraded back to the original kjam rom. Both the downgrade and the upgrade went smoothly.
I then found out I wanted to customize my splash, so I downgraded again. I customized the main splash (not the HTC one) using aWizard. Worked like a charm. I also ran some extra itsme tools to read and write from rom in some locations I needed access to.
Everything was working great at that point. But the downgrade ROM didn't properly respond to some of the printed keys on the kjam keyboard, so I thought I should upgrade again. However, this time, I decided I want to keep my splash etc., so I tried to upgrade only my radio and OS rom, as backed up by aWizard previously, from the original kjam ROM. I used aWizard to restore the selected areas of ROM, rather than the RUU tool.
I upgraded the radio ROM, didn't reboot the device to keep the radio and OS in sync, upgraded the OS ROM, just as that was happening, the phone received a phone call (or text message, do not know which), and hung. While the aWizard eventually completed the upgrade, the phone did not reboot or "un-hang" itself after aWizard displayed success (there was no error on the console window).
So I soft rebooted the phone. The splash screen came, but without a GSM version on it. I was like, "shoot!", something bad must have happened, lets just put the full kjam rom on this, and get it over with - never mind the custom splashes. So I went into bootloader and applied the kjam rom.
Now it displayed the GSM version as well on the splash screen, but again, it never left the splash screen. I was like, again, "shoot!", lets just go back to that old downgrade ROM with the funny keyboard, then we can figure this out again. So I went into the bootloader and applied the downgrade ROM.
Alas, the beer glass splash screen remained hung as well! And actually, since then, I've downloaded and installed ALL ROMs I've been able to find - ALL of them have hung.
My bootloader is still working fine and dandy...any idea why this might be happening? Was the problem in the phone call I received? In using aWizard without rebooting? In using aWizard at all? In trying to manually edit the machine ROM using itsme tools (mind you, those edits worked fine until I started updating the GSM/OS ROM)?
And oh, after hanging for a while on the splash screen, the phone screen starts flickering real bad (whilst still on the splash); in case that provides any help.
To clarify the bootloader situation a little more:
I've got FULL bootloader capability. I can mtty into it, I can write commands, I can install full new ROMs from the bootloader, etc. So this would seem to indicate my phone may not be a brick yet...its a brick that can display changeable wallpapers I even figured out how to draw progress bars and write text to the bootloader screen using MTTY commands. Fun, actually! Its a $700 etch-a-sketch pad
Please leave. We believe here in HELPING people without charging them.
Hmm.
A $700 etch-a-sketch?? I bet someone would buy that on eBay if you called it that.

Can't get to bootloader, worked before.

I posting this as well here, from this origional post
http://forum.xda-developers.com/showthread.php?t=278406
I had been installing some apps, (FlexMail, Agile) and was starting to get some annoying errors on startup, that it couldn't start agile, and couldn't find the FlexMail exe file.. So I thought I'd just reflash the ROM which I've done probably 30 times so far. The phone reboots, then hangs and doesn't come to the bootloader screen, I have to take the battery out to reset. I also can't get the bootloader to run on startup via the two buttons.
Is this an issue with the EnterBootLoader.exe file, or something else? I'm running 2.26 IPL/SPL and ROM ver 2.26.10.2 WWE.
I followed that up with :
if i soft reboot the phone, i loose my time settings. I'm wondering if it's like a PC that's lost it's CMOS battery, and that's why I can't load a ROM?

Forcing Bootloader Mode

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.

Kaiser sleep function does strange things... (FIXED)

After I did a hard reset, a strange problem appeared.
When I press the power button to put the device in sleep, it does, but after 4-5 seconds it automaticly switches back on.
I tried several things such as soft resetting the device, close all running programs and even another hard reset, but it won't work. I didn't install any programs so far...
More information about my ROM version etc.
Official HTC NLD Rom WM 6.1
ROM Version 3.29.404.0
Radio 1.65.17.56
I hope someone knows something I can try...
rubinho93 said:
After I did a hard reset, a strange problem appeared.
When I press the power button to put the device in sleep, it does, but after 4-5 seconds it automaticly switches back on.
I tried several things such as soft resetting the device, close all running programs and even another hard reset, but it won't work. I didn't install any programs so far...
More information about my ROM version etc.
Official HTC NLD Rom WM 6.1
ROM Version 3.29.404.0
Radio 1.65.17.56
I hope someone knows something I can try...
Click to expand...
Click to collapse
i see you have already tried the following but i'm going to write down how i would go about debugging the problem anyway. first, i would try the following steps in the following order to ensure it is not a software issue (it seems you have already eliminated the possibility that this is a software issue):
0. ensure you are using the correct hard SPL for your ROM. if you have never flashed a custom ROM and if you are using the ROM that came with your phone factory installed, you need not worry about this step or step 2 onwards
1. hard reset your phone and check the behavior of the sleep button BEFORE installing ANY of your favorite cabs and software...you have already done this
2. it is recommended to re-download the ROM image and re-flash it to minimize the possibility of a corrupted download or a bad flash
3. it is also recommended to hard reset your phone immediately after flashing the ROM at the point where it says "tap here to begin", i.e. before the screen alignment wizard
4. once again, test the behavior of the sleep button BEFORE installing ANY of your favorite cabs and software
now lets assume it is a hardware issue...here is a nugget of information that might help you. i remember reading a thread here started by a person who described a problem very similar to yours. it involved a "stuck" camera button. you see, the camera button is TWO-stage...and if the half-press stage is "stuck", your phone will never go to sleep properly. search for this thread for more information.
finally, if this is indeed a hardware issue, it seems strange that it appeared only after you did that very first hard reset...but life is full of coincidences !
good luck!
thanks for your suggestions, I will try them and post results.
no success
I tried the things you suggested, but it doesn't work. I also tried the power button when it says "tap your device..." but the device woke up after 4-5 seconds also.
I checked my buttons (especially the camera button, but that one seems to be well... I can feel the two "clicks" and I can take a picture in a normal way)
I'm thinking it might be a ROM problem or something like that... (but my problem is, if I want to go back to the previous official HTC ROM, the 6.0 one, I probably have to use HardSPL, but I don't like that much because of warranty...)
Ok other question... Can I install the Dutch Vodafone ROM on a non-branded HTC device, or could I get VendorID errors or something similar if I want to keep the original SPL?
fixed!
Ok, I fixed it after installing HardSPL 3.29 and flashing the latest WWE ROM...
Now my power button works perfectly!

Categories

Resources