Timewizard Notification Error - 8125, K-JAM, P4300, MDA Vario ROM Development

Everytime i boot my phone (Blackdiamond 1.0) i get a timewizard error, and it wont go away. I had blackdiamond 3.1 installed, and i couldn't put up with the missed calls and not being able to hang up. So i decided to go back to tmobile 2.6, and thats when i started getting the timewizard error. So then i decided to install blackdiamond 1.0 and now i can't even align the screen because the error comes up. Any ideas? possibly a rom that cleans everything out.

anyone know such a rom?

Sounds like a bad flash. Remove your storage card and reflash T-Mobile 2.26 ROM again.

I recommend this ROM

goofeyass said:
Sounds like a bad flash. Remove your storage card and reflash T-Mobile 2.26 ROM again.
Click to expand...
Click to collapse
This is my third flash after the error, still no solution. The phone is overwhelmed with errors such as the one mentioned above, the rest are ***.exe not being able to open errors. Any other idea's would be helpful, thanks!

Please guys, i know the answer is out there in one of you. Please help, i don't have any spare phones :-(

BD 1.0 is a little old
People use to install new ROMS so the problems are better handled
To clean your PDA - Install Tmobile 2.26 (search around here or ... hold on .... Get it here)
Than install any ROM you like I would advise to go with any TNT ROM. I've put this (I don't know any better http mirror)
Don't forget to Hard-Reset the wizard after each ROM update
PS:I've tried BD3.1 but i had almost the same issues as you.
Aldo

hey aldo, thanks for the post. I have installed tmobile 2.26 rom multiple times, it just gives me a bunch of .exe missing errors and my phone is really slow. I looked through the directories with file explorer and most of the files are still there, they have not deleted. Any ideas?
Thanks

a little update
the timewizard notification error went away after installing tmobile 2.26, but i still had a lot of ____.exe errors. I used the file explorer to the startup folder under windows and found a lot of broken shortcuts to programs. The tmobile 2.26 rom must have removed the programs, but it left behind a very slow phone and a bunch of broken short cuts. Any way to fix this?
Thanks

Hmmm....
It sounds to me you have not hard-reseted your wizard.
Try a hard reset with the TMO 2.26 ROM on it.
PS:
Hard reset sequence:
Press VoiceDial button + comms manager button + soft reset.
You will get a screen with 3 colored bars; at this screen, press the D-Pad UP.
(some other version will display a message saying to restore to factory default settings, press the 'Send' button. In this case, press your 'Send'/'Call' button).

Related

Stuck On Boot Screen

Ok, I really have read existing threads related to similar problems, but I am completely stuck on the boot screen (not bootloader screen) with my Tilt.
I flashed Dutty's 6.1 ROM last week and all had been working fine until last night. The phone was stuck with screen lock (screen nor buttons would respond). So, I performed soft reset and it just stopped at 'smart mobility' boot screen. I then performed hard reset, and again it just stopped and hung at 'smart mobility' screen.
This morning I got into the bootloader screen (power + camera + reset) and flashed original ROM (well, new officiall AT&T ROM released last month). Original ROM flashed successfully, but it now hangs on AT&T boot screen. I have tried hardspl, and flashing multiple ROMs, which all complete successfully, but it always hangs at the boot screen.
Thoughts?
what radio are u using?
Well, with Dutty's I was using 1.64.08.21 that came with the ROM... When I flashed to the stock AT&T ROM, I used the radio included with it as well (1.27.14.09).
tmac said:
Well, with Dutty's I was using 1.64.08.21 that came with the ROM... When I flashed to the stock AT&T ROM, I used the radio included with it as well (1.27.14.09).
Click to expand...
Click to collapse
Dutty's didn't come with a radio.
Well, I was using 1.64.08.21.. Right now, I have the stock ROM flashed with 1.27.14.09
I have a similar problem. I flashed alex rom yesturday then I flashed back to OEM to test something then today I flashed back to alex cube rom and it said flash was successful but when I did a hard reset during the "Tap screen to begin" my phone go stuck in the AT&T inital logo. I tried connecting to USB to reflash but USB won't detect the phone. I have hard reset, removed battery, and no avail. Does this mean I bricked my phone?
To clarify, I have been doing these for some time and also had and 8125 previously, so I understand the flashing process. I also understand that there are only certain radios that work with WM 6.1 and 6.0. This doesn't appear to be a radio incompatibility issue. As I mentioned, I was using Dutty's 6.1 ROM just fine for several days before this happened. I had been using Sleuth's 6.1 prior to that.
Tim
You always should re-flash the radio AFTER flashing the ROM. Pt yuor device into boot loader (hold camera, power & reset button). Reflash the Radio. If that doesn't work PM me & I'll walk you thru looking for bad memory blocks.
hchavarria said:
I have a similar problem. I flashed alex rom yesturday then I flashed back to OEM to test something then today I flashed back to alex cube rom and it said flash was successful but when I did a hard reset during the "Tap screen to begin" my phone go stuck in the AT&T inital logo. I tried connecting to USB to reflash but USB won't detect the phone. I have hard reset, removed battery, and no avail. Does this mean I bricked my phone?
Click to expand...
Click to collapse
NO, it does not mean brick. It means you may want to try another USB port, check the activesync connection settings, & possibly reflash using the SD card.
Edit: After looking at your MTTY feedback, & confering with a few of the Gods, I have to unfortunately tell you that your NAND chip appears to be damaged beyond flushing. The blocks can't even be erased, & that's the problem. When you reflash the blocks have previous ROM data still stored & because of the NAND damage they cannot be overwritten. Return under MFG warranty is all you can do. (Believe me, I really hate saying this & even got confirmation from Pof & Jocky) Sorry Guy.
My 30-day return policy date is tomorrow so I went to the AT&T store today and they swapped it out with a new device. They mentioned next time I have to ship it.
Could this have happened because of to much flashing? Or was this possibly an already existing defect?
I got a new one shipped to my overnight. There was obviously something wrong with it, as I tried everything under the sun. Flashed new ROM, then flashed new radio, flashed original ROM, etc. Everything gets stuck on the boot screen. At one point yesterday, I left it at the boot screen for a couple hours and it finally booted up, but then locked up again once it did. Then next time I reset, it got stuck on the boot screen again.
Please tell me you installed hardspl first?
Soft Reset Looping - Dead Kaiser
Hi all,
I have been flashing/testing many roms for a number of years now. I particularly enjoyed Jasjamming in my Tytn I days. Now...
Great work seen by many developers.
When I first got my Kaiser, i tried HardSPL, and had "white screen" issue, I then followed instructions on "white screen" thread....copied cab to kaiser....ran cab from kaiser..........eventually was able to flash to a new/ different ROM
However, I recently flashed my Kaiser and after using it for 6-7 hours after flash, it soft reset itself. It continued to keep soft reseting itself without geting to boot screen. It kept reading "smart mobility" and it would reset, vibrate, reset, vibrate, reset.......
I tried EVERYTHING - remove battery, flash back to original ROM, change radio (bootloader worked in safe mode - holding down camera button), but to no avail.
I then tried MTTY, and no go with this too. I eventually had to give my phone back in to HTC.
The question I ask is what is the cause of this? Is it excessive flashing? Is is HardSPL? Any comments/ suggestions would be welcomed...
Many thanks
P1Tater said:
Please tell me you installed hardspl first?
Click to expand...
Click to collapse
If you are asking me that question, the answer is yes I did run hardspl. As I mentioned, I have been doing this for long enough that I know what I am doing. I also mentioned that I was successfully running Sleuth's 6.1 for a month or two before switching to Dutty's new 6.1. I was only running Dutty's for a few days before all of this happened.
There is definitely something wrong.. if I let it sit long enough, it will eventually boot. It will work for a few minutes, and then lock up again. Once I reset, it sits on the boot screen for a couple hours again. I have flashed several different ROMs and Radios to get different results, but the results are always the same.. It hangs at the boot screen.
I guess you have also tried going to the tri-color screen and re-flashing as well as a HR or MTTY command
tmac said:
If you are asking me that question, the answer is yes I did run hardspl. As I mentioned, I have been doing this for long enough that I know what I am doing. I also mentioned that I was successfully running Sleuth's 6.1 for a month or two before switching to Dutty's new 6.1. I was only running Dutty's for a few days before all of this happened.
There is definitely something wrong.. if I let it sit long enough, it will eventually boot. It will work for a few minutes, and then lock up again. Once I reset, it sits on the boot screen for a couple hours again. I have flashed several different ROMs and Radios to get different results, but the results are always the same.. It hangs at the boot screen.
Click to expand...
Click to collapse
Please don't take offence to my probing, as my questions weren't directly directed to you. All I am saying is that we need to understand what is the actual cause of this problem, or we all will be "flashing in the dark", and fearing that this problem could be imminent every time we flash in the future.
Many thanks.
P1Tater said:
I guess you have also tried going to the tri-color screen and re-flashing as well as a HR or MTTY command
Click to expand...
Click to collapse
P1 - Since I can't get the phone to boot completely (well, except for waiting several hours), the only way that I have been flashing different ROMs is from the tri-color screen. Regardless of what ROM or Radio I try, it still just hangs at the boot screen. The only thing I haven't tried was MTTY.
AvinashDhaniraj said:
Please don't take offence to my probing, as my questions weren't directly directed to you. All I am saying is that we need to understand what is the actual cause of this problem, or we all will be "flashing in the dark", and fearing that this problem could be imminent every time we flash in the future.
Many thanks.
Click to expand...
Click to collapse
I was actually replying to P1, hence the reason I quoted him. So, I don't take offense to anything you said.
Well, I hope your not getting offended to my questions? I am just trying to cover all of the simple fixes first since those have been the majority of the things that fix "Most" people's issues. I suggest getting in touch with GSLeon3. He has a pretty good handle on what goes on in flashing and all of the fixes.
P1Tater said:
Well, I hope your not getting offended to my questions? I am just trying to cover all of the simple fixes first since those have been the majority of the things that fix "Most" people's issues. I suggest getting in touch with GSLeon3. He has a pretty good handle on what goes on in flashing and all of the fixes.
Click to expand...
Click to collapse
Not offended at all... I am appreciative of the suggestions.

stuck after update failure

Was installing duttys rom when my anti-virus program started. Update failed and since then all I see is the tri-colour screen. Sometimes I can get the rom updater to recognise my TyTNII but it will not continue to upgrade. Any suggestions. Have tried mtty1.42 but it doesn't seem to have a usb port option, have tried hard reset etc with no luck. Any suggestions would be greatly appreciated.
An update, I have tried several rom updates since, most get to the stage where the progress bar is shown and the stop. The HTC update to revert to shipped rom gets to 1% and then tells me that this rom is not suitable for my pda!
How about some more information...
What is your Tytn II - Tilt or HTC?
What Rom was on it before you tried upgrading?
What Radio was on it before you tried upgrading?
What version of Duttys did you try to flash?
Did you upgrade to HardSPL before you tried flashing?
This should enable someone to begin trying to unbrick your phone.
Also DO NOT USE MTTY unless you know what you are doing - it can seriously kill your Tytn if used incorrectly. Wait for GSLEON3 to swing by before trying this - but he's very busy at the moment helping others unbrick their toys so you may have to wait for a while.
If you had an original rom/radio from AT&T or HTC it shouldn't hurt trying to download an original rom and try to flash - preferably using your SD card.
Also, while you're waiting for someone to help, have a good read through the Kaiser Wiki (in my signature) before trying anything else.
what are the steps that u take? let us know if u are missing any
HTC TyTN 11, Was using Q-mobile 1.2 but couldn't install tom tom navigator 6, don't know what radio it was using because i hadn't got that far. Was trying to flash Dutty's 6.1 and I had run jumpspl from device because I got the white screen when I treid to run 1.93 so installed 1.56 to pda and ran it. this worked to insatll Q-mobile this morning.
Hope this helps!
what are the steps that u take? let us know if u are missing any
Try to reset pda keep getting tri-colour, attach usb and usb shows at base of screen. When i try to install rom The problem in my second post occurs. I cannot hard reset device to anything other than the tri-colour
Thanks for your help, I tried one of the roms indicated and it worked! I have spent so much time reading various wikis and downloading files. I'm not entirely sure why it worked this time but I'm not about to ask questions! Thanks again!
OK, now you've got your phone working again, make sure that you get HardSPL installed before you try anymore flashing.
ok i was installing KAIS_Radinly_0.26.07.06_CustomRUU and it froze at 96% and now my phone is bricked!! every time i restart the phone its stuck at the RED GREEN BLUE and WHITE screen.. i tried using mtty but then im not trying to mess my phone up any more. i dont understand how to fix it.. if i download a new ROM and put it on my SD card then how do i read it with my phone? sorry guys, im a noob at this as you can tell..
nm guys. i just ran the new rom and it worked! haha sorry for posting too quick!
okay i have one problem after fixing it. i downloaded the TEST rom for the ATT tilt and now every time i reboot my phone it says 'TEST ONLY. NOT FOR SALE.' how do i get rid of this? when i installed a new rom it still says this and i even tried hard resetting my phone but it did not reset anything to factory settings. it just reloaded the rom that i last had!
xmooglex said:
okay i have one problem after fixing it. i downloaded the TEST rom for the ATT tilt and now every time i reboot my phone it says 'TEST ONLY. NOT FOR SALE.' how do i get rid of this? when i installed a new rom it still says this and i even tried hard resetting my phone but it did not reset anything to factory settings. it just reloaded the rom that i last had!
Click to expand...
Click to collapse
http://wiki.xda-developers.com/index.php?pagename=KaiserFAQ
your answer is in there

Not-so N00B dumb question

I've been flashing new ROMS on an 8525 for a couple of years now, but I'm new to the 8925.
I've been reading a lot, I think I understand the relation between SPL and the ROMs now, but I'm still puzzled.
I keep getting a lot of cruft left behind from prior ROMs and don't know how to get rid of it. for example about three ROMs ago, I flashed the "Mobile Vista" from ansar. Now I still get his Today theme, and there are still a lot of apps installed that read "ansar..."
I've tried removing the battery before flashing, making sure the SPL version is OK with the ROM doing hard resets - nothing seems to let this device start from a "clean slate".
I'm trying to find a ROM I can be happy with, which is why I'm trying so many, but I can't fairly evaluate aon one ROM if I don't know what I've really got installed.
TIA
Walt
I've never heard of anything like that happening Are you sure it is the today theme, or just the boot splash? That would be most likely.
As far as the programs, maybe most of them are from ansar? Which ROM are you using right now?
I just flashed the PDA Corner latest version (15) and it seems to be behaving now. Prior ROMS I tried this morning included Athine, Garmin and Phoenix.
Prior to flashing PDA Corner, I did an "Erase memory" (hard reset from software) and removed the battery for about 10 minutes. Maybe that's what did it. I agree, I've never seen anything like this before, I always thought that flashing the ROM reased everything, but then I started reading about SPL on the Kaiser somehow being more than just a bootloader so I got concerned.
And yes, it was the Today screen including clock, wallpaper, etc. The splash screen on bootup actually did change to the one corresponding to the new ROM.
Thanks.
Walt
When flashing a new ROM, when you get to the "Tap screen to begin" do you perform a Hard Reset?
If not, I suggest you start doing now.
Also, merschle (ex-moderator and Artemis cook) recommended flashing a ROM twice with a Hard Reset in between. I don't do this, but it just might help
Ta
Dave
Flash a stock HTC rom and then try a modified rom again. It always helped me when i got strange flash problems.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
Billun said:
Flash a stock HTC rom and then try a modified rom again. It always helped me when i got strange flash problems.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
Click to expand...
Click to collapse
I hard reset three times then I flash an OEM ROM, then I hard reset three more times to be sure. I know it's anal, but it works for me.
I don't know how you're flashing try the SD Card method.
It's safer and more reliable.
The SPL & Rom have closer relationship than on your older device.
A sign of have the wrong SPL or needing to change to another SPL is freezing. If you notice your device is freezing or non-responsive, flash the recommended SPL by the chef.
Don't worry any, I was the same when I upgraded from the Wizard...gotta learn all over again.

Anyway to stop ROMs re-installing?

Hi there all, firstly, i have tried the search button and found nothing, i am having a little problem with everytime i soft reset or turn off my phone the rom re-installs and i have to go through importing sim contacts data setup etc all again.
It also deletes any apps i've installed and its getting me slightly miffed.
I am using 6.5 TPC V11 Mega WWE rom (however whatever rom i flash it does the same) radio 1.70.19.09 (again I have tried various radios) and various HardSPLs - currently using 3.29 i believe.
Is there something the matter with my internal memory maybe? i know sometimes whenh it reboots it tries to load into windows again but gets errors such as "bars.cab failed to install"
SO guys any ideas, i know it will probably be an easy fix!
Thankyou in advance
Paul
well this is the wrong place to have posted this but try this and see if it helps
1. try flashing via sd card and not usb cable, and vice versa.(see sticky to guide u thru sd card flash process
2. try flashing stock rom
see if that helps
If a problem with a ROM ask/report in ROM thread, the F.A.Q's at the start of threads cover the hard-reseting issues with 6.5 ROMs.
Thread closed.

Replacing Stock Manila and Boot Screen for Return Tomorrow

Hey all,
I have tried searching frantically, but came up with nothing. Can someone explain how to restore the stock manila and boot screen files? I'm returning the phone tomorrow and want it looking pristine before handing it over. My start menu icon, manila slider and clock, and "SSK" 2nd boot screen won't go away after a clear storage and Stock Rom & Radio flash.
PLEASE HELP! What did I do wrong?! Did it not flash properly?!
Thanks for your assistance!
UPDATE: I think it may have been a flashing error, because it appears that certain software has been loaded on as well. Lets try flashing again from a different PC.
UPDATE 2: So I figured it out. It errored out because I was trying to flash using VMWare Fusion 3.0 and Windows 7 configuration on my MacBook Pro. Tried it in bootcamp, and it was flawless. Hopefully this helps the next guy out that this happens to.
You can also hard reset your phone after flashing a rom.

Categories

Resources