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.
Related
Hello friends, this is my first post in prophet forum, though I had been a ppc user for more than 2 years. 5 months back, I bought an O2 XDA Neo, which was loaded with a dopod rom, with numbers coming up as 2.09.001 etc during startup. Shortly after purchase, I flashed with RUU_Prophet_220734_2207114_024721_QtekWWE_Ship rom. Everything went on well, and I was using the phone without problems for the past 2 - 3 months. Well not exactly without problems, some times when I reset the phone, it gets stuck at the spl, ipl screen, and I have to reset again many times to get it to load windows. I initially thought the problem may be due to the battery not being charged fully, but later I found that battery charge is not the problem, as the phone not booting became more and more common even with a fully charged battery. Even when I managed to get the phone started after repeated and frustrating soft resets, I started to get corrupt PIM data, like the contacts and calendar applications not starting up. ALso strange folders with name y? and y?? appeared in the phone memory. THese folders could be deleted only with Resco Explorer. Also the bluetooth was not working properly, that is when I turn it on using the comm manager, the blue tooth icon gets activated but actually no bluetooth is turned on. Later after a soft reset, bluetooth turns on but now the icon in comm manager is not activated. I did a hard reset a couple of times thinking that this problem will be rectified, but all the problems continued.
Going through the forum i read some where that JAMin_WWE_213923_2139123_022021_ship was one of the most stable roms for this phone, so I set about flashing this rom. I used ROMUpdateUtility-NoVendorID and the update went on till 95 % when it showed error 326. I tried again, with the same result. I later flashed RUU_Prophet_220734_2207114_024721_QtekWWE_Ship back, and the phone is working as before.
NOw I would like to get the following problems corrected
1. Phone getting stuck at ipl, spl, gsm screen
2. Proper working of bluetooth as I would like to use it with my BLueant Supertooth II
WHat will be the correct these prolems ? will the imate rom correct these problems, if so how am I to go about loading it ? or is there a better one than what I am having now ? or is it a HARDWARE problem ?
I am very sorry for this extremely long post, but I felt if I said all my problems in one post, I would get better response.
PLease help....
You should have stayed with the RUU_Prophet_220734_2207114_024721_QtekWWE_Ship ROM from the beginning, since it's the best and also latest official Prophet ROM. It's a 2.20 ROM which is the latest available.
GAMBIT999 said:
You should have stayed with the RUU_Prophet_220734_2207114_024721_QtekWWE_Ship ROM from the beginning, since it's the best and also latest official Prophet ROM. It's a 2.20 ROM which is the latest available.
Click to expand...
Click to collapse
I am still with that ROM. It is with this ROM that my prophet is causing the above problems.
Can you guys advice me how to load JAMin_WWE_213923_2139123_022021_ship rom with out this error 326 showing up ?
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.
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.
Hy,
I ve got the problem that suddenly my TP shows unusually hanging after a few minutes playing around. If i do a softreset then it hangs on the splash screen and nothing happens. I can do a hr then and the same story begins. After tast appeared i flashed some other roms to be sure that its not depending from the rom. Also i restored different backups, with all its the same... i fear that a part of the memory is defect ... Any ideas how to test the memory or other suggestions? thx in advance.... i dont want to use my microwave
Greetz
Boris
Did this happen suddenly or did you do something before it happened (eg install something, etc)?
Mine just today won't turn on, I had it off all day and now it just sits on the splash screen.
Trying some things, if I figure anything out I'll let you know.
No, i didnt do anything special today or yesterday, but a week ago i set it up completly new, cause i had equal problems.... to set it up completly new with all progs and cosmetic "operations" costs me nearly one week so i dont want to do it again ...
If i find a way to solve, i will post here too
Greetz
Boris
I flashed EnergyROM (booted into the tricolor screen by holding down Power and Volume Down), and it seems to be working.
Youre the lucky one, congrats...
I have a similar problem. The only change/new install is the updated version of Microsoft MyPhone. Now my TP will not connect to my telephone provider: T-Mobile. It just tries and tries but never connects.
Also, sometimes when I try to open any program, I get the error message that the certificate cannot be read. a soft reset fixes this but this problem is driving me crazy.
Is this another Microsoft update ****up?
same here: today more than 3 times problems with certificate or similar message ... thinking of the last timebomb in my old romeos rom ... was no fun..
Borisku,
Are you running Microsoft MyPhone? If so, did you do the software update within the past 4 days?
i do, but i didnt update ... ??? This morning my TP hung again, and i tried to sr it.... seemed to work until tp vibrates 3 times and then nothing anymore, no screen, no button, nothing
.... took out battery, left it out for 30 minutes, then i could HR again and restore my backup... since then no problems.... do you think it could run too long, getting too hot or something like this??
Greetz
Boris..
Edit: was too fast just 1 minute after i wrote that, tp hangs while in connection to active sync.... hr now, will test how it runs with pure romeos2 for 2 days now... rport follows
Edit II: The last days i always flashed from SD Card... i will now try to flash ROMEoS2 from PC ... maybe theres a difference, especially cause the text at the end of flashing from SD was confused. there were mor than one words at one place one the screen, and i found i typing on the screen RaphSimg.nbh, although the file is named as usual raphimg.nbh (without the "s" in the centre...)
I hope i m not too early: i think i solved the prob, maybe that helps somebody & prevents a tp from ending in a microwave
in preparing to bury my tp in the microwave i flashed back to the german stock rom or - correct - to the official update that can be loaded from the HTC Homepage; it contains not only the Rom but also radio & Splash Screen. I flashed it to my tp and was prepared to undo Hard SPL, but it gave it a chance.... and it ran like a VW beetle, flashed back to ROMeOS2, it runs.... i will wait till tomorrow & hope that it will not change to freeze or change clock Font colour partly as it did before...
Hope it will help somebody...
Greetz
Boris
Edit: its now 14th of december and it runs like a charm... seems like the failure is gone through flashing to stock ROM & then flashing ROMeOS again
Still is okay ...
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