Database Info

Stuck in bootloader & error 302

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.

Bricked Cingular 8125, help!!

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.

First post... and I think I already bricked it

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!

Touch Pro crashed - needed hard-reset to recover

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

Neither bypass nor Filter Wizard recognizing the phone.

I think I killed my phone. I lil' story -- i decided to flash my Redmi 9A, flashed PBRP onto it and.. Black screen. I already faced it, so I just try to flash original firmware with SP Flash and... Error. Can't quite remember what it was. I try to use bypass, and although bypass does give the "Success" output, SP Flash still gives the same error. I google this error and it seems like it is an issue with drivers. OK, I remove all the drivers and try again. It got zero battery at this point. Now it's not recognized by PC at all, Windows gives no error, FIlter Wizard doesn't even recognize it, Bypass gives a driver error. I'm sure I installed all the drivers correctly. I also tried:
To use my installation of Arch Linux using this guide, no success, bypass doesn't recognize the phone
This LIveCD, where all the drivers should be properly installed, but no success, same as every other try
I'm very stuck. Any suggestions?

ignaycyhry said:
I think I killed my phone. I lil' story -- i decided to flash my Redmi 9A, flashed PBRP onto it and.. Black screen. I already faced it, so I just try to flash original firmware with SP Flash and... Error. Can't quite remember what it was. I try to use bypass, and although bypass does give the "Success" output, SP Flash still gives the same error. I google this error and it seems like it is an issue with drivers. OK, I remove all the drivers and try again. It got zero battery at this point. Now it's not recognized by PC at all, Windows gives no error, FIlter Wizard doesn't even recognize it, Bypass gives a driver error. I'm sure I installed all the drivers correctly. I also tried:
To use my installation of Arch Linux using this guide, no success, bypass doesn't recognize the phone
This LIveCD, where all the drivers should be properly installed, but no success, same as every other try
I'm very stuck. Any suggestions?
Click to expand...
Click to collapse
If u install a recovery rom and you did it wrong you can boot to fastboot, no?

Hey I faced similar or even worse (twice), I had a similar story to yours,
FIrst itme:
I first bricked my phone, but it was cool, the phone just flashed MIUI for a fraction of a second when trying to go to recovery, other than that, nothing, I tried flashing, wich made it much much worse, black screen, no key combo did nothing, windows not just did not recognize it,it told me there was no way of recognizing it, (error 43 in devices admin, its not posible to reinstall the driver, nor do crap at this point) filter wizard showed nothing, bypassing imposible, etc.
It got pretty similar to what you had:
I just left the phone do some charging discharging cycles (at least 4 days with me checking if the phone did anything at all almost once every day, just so you know the phone was really bricked) and it eventually responded after all that (Im not quite sure what fixed this, I dont kno if it was complete discharge or what, but something happened and it vibrated when holding the pwr button.
Once that worked, I managed to install the filter by pressing volup voldown and conecting the phone to the USB port (dont use 3.0, it works worse for some reason) at the same time, you need to connect and press the buttons and connect at the same time (
at 1:30 he does it, video on spanish) and then you can install the filter.
Then you can Bypass and attempt to flash with SPflash tool, I recomend autoconcect, UART never made it for me, Im thinking thats for when you can put it in EDL mode by presing the test points, but I dont know enough to say for sure, point is, UART never worked for me, even tho I eve know what comms I was using.
second time:
I was running Custom ROM ArrowOS 12, ArrowOS13 came out some weeks ago, so I decided to lash it, it was better in some areas and worse in others, the contacts app did not work, but now Volte fingerprint(irrelevant to us redmi 9a users) and face unlock did so I decide to test some stuff, I wasnted to flsh boot.img from original MIUI ROM on top of ArrowOS13, to check if that fixed some stuff (that worked wonders on ArrowOS12) that bootloped thephone but it was fixable from recovery, I did that and decided to flash MIUI ROM to check if flashing ArrowOS13 from MIUI ROM worked, and flashing MIUI bricked my phone.
unrecgnized with error 43, not posible to fix from software, black screen no response whatsoever from any key combo (all 7 combos) no charging, no filter, no nothing, I know I had around 50% battery (days ago I remembered the exact number, now I forgot it, but just so you know, its not a hunch, I knew it had battery) I tried doing the same stuppid crap, charging and leaving it alone for couple hours, but after one night nothing worked, so I assumed I would have to repeat the procees I did before (I wrote it complete on an unbricking thread so I knew I could go back there and redo that or variate it until it worked), but I decided to do one final thing.
I knew it had battery, so I decided to try and forcedrain the battery, I took a piece of TP and gave it a turn around the phone over the buttons (this is just to not dirty the phone) then with electrical tape, I left the power button and the vol down button pressed) this for around 7 hours my plan was leaving it like that for a full day, but around 6 hours I thought I heard a vibration from the phone, so I kept it with me, then after a while I thought it happened again, but I also had my own phone with me so I thought it was that and some other things distracted me so Im guessing I missed a few, but after that I started to take time from every vibration and yeah, around every 8 - 10 minutes the phone vibrated
I decided to connect the phone (I hadnt before because it would just slowdown the battery draining process) and the phone conected to the pc, still bricked, but it was a lot better, I quickly installed the filter, wich I dont quite remeber, but it wasnt easy, I had some hickups, cmd bluescreened my PC when using Bypass like 6 times, so I switched to powershell and that worked (to do that you need to press shift+right click and open powershell here, then run "python main.py") that worked, but I did not flash using SP flash tool.
I was trying to avoid turning on the phone for fear it would go back to the previus state, but after a while pluged on the PC it showed the no battery logo so I tried to tun it on and it was bootlooped, I was able to go to recovery and fastboot (not normally, I pressed the keys, the phone try to go into those menus, it showed no battery, and in the next cycle after splash logo no matter what you did it sent you to the previus key combo menu) I tried leaving it charging on fastboot, but that did not work, I tried flahing a rom from recovery (wich said I had 47% battery) and it successfully did but when trying to reboot to system it again showed no battery logo. so I put it on fastboot and tried flashing MIUI with Miflsh, did not work but it told me the ROM was bad (same one I had use before) I made sure to extract it again and again nothing, I assume it was the antirollback, so I downloaded the next one on line 12.5.6.0 (I was on 12.5.4.0) and that finally worked (Miflash actually gave me lots of errors but you can google them and most of them have easy fixes, like creating a log folder, etc)
that was yesterday, after it worked it showed me the phone had around 60% batterywich lasted around 30 minutes to 40%, then it took 10 minutes to spend the next 20% (it told me that) and then it drained 1% every second (Im not exagerating I thought I had fried my battery with all that power button pressing) but I had hopes of it just being a configuration issue of the phone not knowing how much battery it had so I just left it power of and pluged it then so the phone knew what was his zero, now the phone as been on 100% for like 2 hours (sharing internet), so yeah, I think the battery has some issues but its better than nothing so Im happy with that.
that is my whole experience, I hope it helps you, see if you manage to get any response from the phone and if you do you can try contact me for help in any point along the way.
Update, it just got to 99% after 2 hours 10 minutes aprox IDK, I would need to test more to be sure