Hello All,
I have the TNT 1933 image loaded on my Cingular 8125 and have been running it fine for almost a month with little to no issues. The issues I had were minor kinks here and there but did not hinder the phone usage at all and has been working fine till up to this point. I was reading my e-mails via the exchange setup to my company exchange server and then closed out of it via the task manager and decided to soft reset it. I always soft reset during the morning just because I noticed there are memory leaks and soft-resetting normally resets the memory back to normal. After soft-resetting, it would hang at the Windows Mobile 6 Professional boot loader screen and will not continue. I even left it sitting there thinking it would load but I even let it sit while it drained the whole battery. I then plugged it into the charger and proceeded to soft reset it again and still does the same thing. Yes, I originally flashed it to the Tmobile rom before flashing the Tnt1933 image and yes its both unlocked (forgot the terminology). I tried taking the battery out for awhile thinking it would clear the memory or whatever and that didn't do anything. What I can do though is enter it into the bootloader mode with the 3 color screen but I do not want to reflash since I have important files that were not copied to my SD card. If there is a way for my PC to recognize my phone so I can at least copy the files I need, then I can reflash the OS again via the bootloader screen since I can get to that mode at least.
EDIT- Could this have been caused by the battery mem program overclocked at 247Mhz (the recommended for the 8125)? Since I never installed anything else except the main programs that were included in the image of the TNT 1933, the only thing I could think of was the extended overclock and overtime, corrupted the files from overclocking...just my 2 cents
lenell86 said:
Hello All,
I have the TNT 1933 image loaded on my Cingular 8125 and have been running it fine for almost a month with little to no issues. The issues I had were minor kinks here and there but did not hinder the phone usage at all and has been working fine till up to this point. I was reading my e-mails via the exchange setup to my company exchange server and then closed out of it via the task manager and decided to soft reset it. I always soft reset during the morning just because I noticed there are memory leaks and soft-resetting normally resets the memory back to normal. After soft-resetting, it would hang at the Windows Mobile 6 Professional boot loader screen and will not continue. I even left it sitting there thinking it would load but I even let it sit while it drained the whole battery. I then plugged it into the charger and proceeded to soft reset it again and still does the same thing. Yes, I originally flashed it to the Tmobile rom before flashing the Tnt1933 image and yes its both unlocked (forgot the terminology). I tried taking the battery out for awhile thinking it would clear the memory or whatever and that didn't do anything. What I can do though is enter it into the bootloader mode with the 3 color screen but I do not want to reflash since I have important files that were not copied to my SD card. If there is a way for my PC to recognize my phone so I can at least copy the files I need, then I can reflash the OS again via the bootloader screen since I can get to that mode at least.
EDIT- Could this have been caused by the battery mem program overclocked at 247Mhz (the recommended for the 8125)? Since I never installed anything else except the main programs that were included in the image of the TNT 1933, the only thing I could think of was the extended overclock and overtime, corrupted the files from overclocking...just my 2 cents
Click to expand...
Click to collapse
I highly doubt that batterystatus was what caused this because I have used batterystatus with every ROM I have ever used and have never had this problem.
As much as I hate to say this... As for your important files, you might as well kiss them goodbye because they're already gone. If your device will do nothing buy enter bootloader then the boot sequence on your phone is corrupt and you have no other choice, if you want your phone to work again, but to flash that T-Mobile ROM(or you can flash the 8125 official ROM found HERE.)
I know this isn't what you wanted to hear but you cannot connect to your device from activesync if you can only reach bootloader and nothing else and if the files are not on your storage card, they're gone.
Well, even if you were running Battery status, did you actually do an overclock or did u just leave it on default settings upon installing? OMG I'm gonna cry Those files are like my life I just want to understand how this happened when I installed nothing at all and it had been working fine for almost 4 weeks with no issues. Just went to hell after soft-resetting.
Related
I've been running a ROM I built from the consolidated kitchen this weekend without any problems. Today I updated the radio to 2.69.11 from the cingular 2.25.11. After the flash the phone froze on the windows mobile screen. After some time I tried to reset the phone and it froze again, a few more tries and it finally boots up. I didn't pull the memory card when I flashed and thought that might have been the problem so I flashed again even though the phone was showing 2.69.11. I don't remember everything after that but it wouldn't boot up and I have tried flashing the original Cingluar ROM & T-mobil 2.26 without any luck.
The phone is stuck in bootloader now and is getting a error code 302 I think it's because the phone doesn't stay on when the USB cable is attached. It gets to about 15% and the phone resets and the error 302 pops up. When connected and not trying to update the phone turns on and off in the bootloader screen. I have pulled the battery, rebooted the laptop, tried using mtty,and pulled the sim. I thought the original problem might have been because I flashed at 52% battery. I put a older battery in after that appeared to have a good charge. Right now I put the phone on charge with the newer battery to see if this helps. I am not sure if it is charging because the orange light is not on, I can't get the phone to stay turned off when plugged into the charger and the bootloader screen is on.
And yes I have been searching for hours for a solution to this problem.
Also looking for a post I read about doing a master reset, I have tried holding the 2 soft keys when turning on, didn't help.
I think this says it all I have tried everything, does anyone anything else to try?
Thanks
UPDATE: went out for a few beers and some food. Not sure it the battery charged (bootloader screen on the whole time it was plugged into the charger)
Tried flashing again with cingular ROM, got about 20% and phone shut off and turned on again in bootloader. Flash gave 302 error again. Tried again and phone reset (on and off) every 5 seconds when connected to laptop with USB.
I'm hopping someone out there has a answer for this problem.
Back from the dead HALLAULA!!!!
This morning I spent more hours searching still didn't out find anything.
I tried mtty again and noticed that I never got to the screen that shows USB>
to enter the command "set 14 0"
I came up with a thought and this is what I did. Created a new ROM, OS only. Thinking it will load faster than any other ROM. It reached 100% in 3 minuets the whole I'm coaching come on baby don't restart and than going (don't know how to explain the feeling) waiting the next 2 minuets to get to finished. But it got there booted fine. I don't know why it stayed on this time and didn't restart, maybe having the battery out all night had something to do with it. After I flashed the Cingular ROM than the original I created and lastly Radio 2.69.11
I hope this helps someone in the future,
i need your help
hi man I had a prophet s200 and give me the same error 302 but, with the diference in my case got 98% adn then stuck in boot screem, please help me if you can...and sorry for my english
Guys,
It may help checking out this thread!
http://forum.xda-developers.com/showthread.php?t=294107
Can you help me out?
How did you create a new ROM - OS only? I'm having the same problem..can you walk me through this?
Thanks
How did you create another ROM (Operating System only)? I'm having the same problem and I have tried for the past 2 weeks - but no luck. Can you walk me through it?
Thanks
I used the consolidated kitchen (sticky at the top of this forum)
Uncheck everything on Build OS.
My problems started from a version of battery status that caused the original problem and not having enough of a charge on my battery.
Make sure you are CID unlocked (if you have a G3) and your battery is charged.
Umm, you can't uncheck everything in build OS or you will have problems, especially if you don't check a tuchflo or non touch flo dll or choose a commanager and probably a few others things. I don't have build OS up in front of me to check. The whole point to this msg is that you can check everything in build OS (besides the ones that say choose only 1) and it will build an OS only rom for you. That's the whole point behind build OS.
You are correct, I was kind of going from memory since I had built the striped down ROM awhile ago.
damn I'm pissed. I was messing around with my phone as usual, setting up pRSSreader and updating all the feeds/channels. I had the phone plugged into my PC because it gives me a faster connection. My connection went out however, and pRSSreader gave me an error. No big deal... so I tell it to update all channels again, and it freezes. I soft-reset the phone twice and it doesn't get past the 3rd boot screen (for me, the blue WM6 screen from mfrazzz's XM6r3 ROM which I'm currently using). Damn. hard reset was the only thing I could think to do.
What would you guys suggest I do incase it happens again?
I sure am getting better at having a list of programs to execute on a fresh install
First you need to figure out if its something that you installed to cause this to happen. There are programs that don't play well with WM6 (but those seem few and far between). Make a list of everything you install on top of the custom rom. If it happens again, you may want to give this a try (but I wouldn't use it until you have the issue again, so you know its something you have added and not this program itself ):
http://www.airscanner.com/blog/blog.php
Its an alpha product (and I've never used it) but supposed to give you a SafeMode (like XP) so you can get back into your phone if software / regchanges go bad on you. SPB has similar, but I haven't used that (and not sure it works on WM6).
Unfortunately, if you are stuck in the 3rd splash screen there isn't much else you can do. You can try pulling your SD card and rebooting to see if that might fix the issue. Also don't be plugged into the USB cable when you reboot (I've seen programs like BatteryStatus hang on restart in the past if you are hooked to USB). Speaking of BatteryStatus, if you are overclocking (or using CPUscalar) try turning that off to see if the problem goes away.
Good luck, and let us know what you find...
I was following the nice little wiki (http://wiki.xda-developers.com/index.php?pagename=Wizard Windows Mobile 6 for newbies) and got down to installing the button ROM to downgrade the IPL to 1.05. Started off fine, but it's stopped at 57%. For over an hour already. I wasn't running anything, but did have Firefox open the whole time (was reading ahead in the instructions).
I guess the question is, am I screwed, or will I be able to end task on this update and restart it? I haven't turned them off yet, but I'm guessing that if I do my phone will be a fancy paperweight.
I did notice that ROMUpdateUtility_Wizard_NOID.exe has maxed out one of my cores (13% utilization, 8-core computer--I.E one core is pegged at 100%), so I'd say it's crashed or in a loop.
I'm going to leave it running--overnight perhaps--and see what happens. Any other suggestions?
er.. if this is the wrong forum, I apologize. I forgot which forum I was reading before I hit 'new topic'.
First, don't use Vista to update if you can.
If the flashing stops, just reboot or use another computer to try again, your Wizard should enter bootloader automatically when you reset it. That should not brick the device (Unless you are installing Button's ROM to a G4 device).
If Wizard stuck at IPL boot screen (not bootloader), press camera+reset can let it enter bootloader directly.
Ok, I am on XP.
Well, I went ahead and killed the locked process and yanked the battery from the phone and was pleasantly surprised it came back up straight into the bootloader mode. These little phones are more resilient than I thought.
I also discovered my problem was that the ROM updater will freeze if activesync is running and connected to the phone. Knowing that, I was able to work around it and got everything on the phone updated, and am now running WM6 on it.
Thanks.
Now I can start using Visual studio.
Love Wizard
One thing that makes me love the wizard is it does rarely brick...
You must be joking...rarely does brick? Shoot, look at the Wizard wrong and BAM! Brick you shall have!
I had posted this in the stickied bootloader thread, but I'm pretty sure I posted to the wrong spot. If a mod wants to move this to another thread then by all means...
My kaiser is doing something I haven't heard of yet. Recently its started to act funny after 6 months of no new software, tinkering, flashing - nothing.
3 days ago I had to restart due to the sound cutting out and I got stopped at the bootloader. After fiddling with it, soft resetting multiple times, taking out the battery (just random low level troubleshooting) it booted into windows. This happened sporadically one or two more times.
I have also noticed that in the last 3 days the phone will suddenly drain to no battery without any warning. I will have 25% battery and be on a call for 20 minutes, then have the phone completely power off. normally, windows alerts me to high heaven with multiple warnings, etc. None - just powered off. After 30+ minutes of recharging in the off state, I powered on... bootloader again.
I hooked it into USB and sent the mtty "boot" command. This worked, it booted straight into windows. Due to my frequent sound problems I figured I'd load on a new radio "just in case" - so I loaded on the eMo radio via the sd card method, and soft reset. Again, bootloader. So I gave it the mtty BOOT command and got into windows... so far so good.
I soft reset just to see what would happen - bootloader.
Now I find myself having to soft reset frequently because the sound will just stop working at random. Of course when I soft reset I get bootloader but just today I found something very interesting: If I plug the phone into USB then simply soft reset it will restart and go right into loading windows. This works from inside windows as well as when I'm stuck at bootloader.
Is this common? My rom is Dutty's 6.1 from April 29. My radio is currently 1.71.09.01.emo. Thanks guys
*edit* now every time I hang up a phone call the earpiece starts making a "TV snow" or "power lines" kind of noise. This of course requires a soft reset which may or may not send me into bootloader. it varies.
I'm no flashing or rom expert by any means but if I were you, I would remove SD card, flash a different hardSPL other than what you're using now, flash a another cooked rom, and another radio. Starting from scratch sounds like the way to go. Good luck ...
I flashed a new SPL (3.29 fixed) and switched from dutty's to hyperdragon III Nov 6. I'm pretty sure this has fixed it.
Has anyone experienced their TP crashing during normal operation, and found the only way to recover is through a hard reset?
That's what happened to me last night. I'm running a stock HTC ROM that I upgraded when it came out (two weeks ago?) and the device was working without any problems up until then.
Last night though I was using Opera to browse a website and it suddenly became unstable. I closed Opera and found it wouldn't re-start so I performed a soft-reset. From this point on the device wouldn't go past the boot screen (displaying 'HTC Touch Pro' with the red version numbers - not even getting to the animation). I attempted to soft reset a few times (and even removed the battery for a while) but it still would not boot.
So I performed a hard-reset and restored a backup, whereupon it now seems ok again.
To give a little more info:
- the device was fully charged (had been on charge via USB all day)
- TF3D not installed - standard WM6.1 with SPB Phone Suite installed
- Browsing over wifi (bluetooth and HSDPA connection were also active)
- Running Opera 15613
- Just before the crash, a bug appeared whereby typing a single character into a website textbox (using the slide-out keyboard) would cause that character to be repeated a large number of times on screen - this has never happened before
I've always run the device with the stock HTC ROM and never had any issues like this.
Anyone had anything similar happen?
Yep, just had to hard reset then restore sprite...I was trying to play a song through tf3d and it froze. Soft reset only lead me up to the first screen that states radio version...yaddah yaddah yaddah...hard reset 'solved it'.
Does your phone got hot?
I had a problem while browsing over wifi. To boost the speed i changed power manegment to best performance in wifi settings and phone got hot in few minutes, opera crashed and soft reset didn't help either. But for me removing betery solved the case and also cooling the device a little.
hope this helps
BHole
BHole said:
Does your phone got hot?
I had a problem while browsing over wifi. To boost the speed i changed power manegment to best performance in wifi settings and phone got hot in few minutes, opera crashed and soft reset didn't help either. But for me removing betery solved the case and also cooling the device a little.
BHole
Click to expand...
Click to collapse
It gets warm sometimes, however in this case I'd only been using the device for a few minutes, so I think it was still cold.
I tried removing the battery but that didn't help.
Seems to be behaving itself since then though.
I got the same problem nearly every day. After a few hours (up to 12) it gets frozen. Only hardreset was possible. I got this problem since a view months. I'm trying now to leave one after another program not installed after every necessary hardreset. Currently i'm suspecting either WM6.5 itself, vAlert or some other mortscript apps. For now i don't installed vAlert and there is no crash since over 24 h.
The following programs are innocent:
- tf3d
- pointui
- SmsReportsEraser
Surprisingly enough, I had the exact same problem just the other day. I got my TP about two weeks ago and was still looking around here learning the ropes of flashing etc and the differences between it and the Mogul. I kinda liked the business card reader that came on the stock rom and couldn't find it as a cab anywhere so I was undecided on flashing a new rom. I also didn't like the TF3d so I wasn't running it. I was using the regular win today screen with spb weather and Phone Suite installed. Worked fine like that for over a week. I got a text message on Tuesday and the TP froze up, so I did a soft-reset. It got frozen on the boot screen just as you described. Fortunately I was able to in hard-spl from the micro disk to unlock it, then I installed NFSFAN's custom rom, also from the micro disk.
Not related to the topic, but I really like how that new rom functions. I added the telus radio as well and now the battery at least makes it through the work day. Before I had to charge it mid day! Only thing I miss is that stupid business card program from the stock rom. If anyone can point me to a cab I'd really appreciate it. I get so many cards its a pain to enter them all manually.
Thanks,
PhilyT
I just started having this problem a couple of days ago. This has happened twice now. Warm-booting did start the reset process (I would get the splash screen), but it never got past that.
i think theres a thread about this somewhere. The cause isnt known but they are trying to pinpoint the problem. Bad rom chip, software problem etc
I've also have been affected by this and its a pain... having to setup the device again.
Mainly this problem has to do with tf3d2 in my case as i try to save a contact each time it will free. So i have to manually enter a phone number and store it.
I guess its better than a hard-reset