8125 Restarts During Call - 8125, K-JAM, P4300, MDA Vario ROM Development

I've have tried each Rom in the TNT 1437 series and they all shut down and restart my phone when I'm on a call. Does anyone know what could cause this.
thanks

nutathis said:
I've have tried each Rom in the TNT 1437 series and they all shut down and restart my phone when I'm on a call. Does anyone know what could cause this.
thanks
Click to expand...
Click to collapse
What IPL/SPL?
What Radio?
Did your try non TNT roms?
Did you flash your carriers official ROM before you flash a custom ROM first?

calouro said:
What IPL/SPL?
What Radio?
Did your try non TNT roms?
Did you flash your carriers official ROM before you flash a custom ROM first?
Click to expand...
Click to collapse
I just reflashed to a non tnt rom and it happened again so I'm sure its not TNT rom. I think the IPL/SPL was the same from the TMO 226 and the radio was 2.19. thanks for responding. I'll try it again using the cingular stock rom.

Radio Restart
Well first flash to a factory rom to make sure your extended_rom is clean and uncorrupted, it causes all kinds of problems if it is..
second, if this is happening on the 4min threshold then sounds like you have enableed the "grpsstallworkaround" found in some registry editor, turn that off...what the workaround does is just that, restarts the radio every 4min.
took me forever to figure this one out when I had it...I thought it was a good thing...nope its a gremlin!!
Hope this helps...

Phone maybe dead
I can get into bootloader mode to reflash the phone but now the phone will get to about 99% done and then restart again in bootloader mode. The phone will restart about 2 times before I can attempt to reflash again. Once I attempt to reflash the process starts all over again. Any ideas what could cause this or is the phone D.O.A.
thanks

I had the same problem, I charged the battery overnight (you might not need to charge overnight, but I bet your battery is low or going bad.) and used a small ROM I built so it would load faster. I think a factory ROM would have loaded once I got the battery level up but before it was rebooting after about 3 minuets into the load.

Related

Phone Dying

I have an unlocked 2125 on the T-mobile network. I upgraded it to WM6, there was no problem. I then decided to go with a different ROM so I flashed it to that one. Now my phone shuts off whenever I try to make a phone call or when i'm in the middle of something, if I reboot it, it will just shut off again. It is getting charged long enough. I Don't know what the problem is, but once I take out the SIM it powers on just fine.
Any insight will be appreciated.
Try to format BINFS and start everything all over again
I did try this, didn't work. The phone still shuts off. Decided to try it again, now it just shuts off when I try to go into the bootloader.
Assuming it's the battery now.
Dude, flashing when the battery is low is very dangerous
etnoo said:
I upgraded it to WM6, there was no problem. I then decided to go with a different ROM so I flashed it to that one.
Click to expand...
Click to collapse
Which ROM did you use? Did you upgrade the GSM/SPL as well?
http://forum.xda-developers.com/showthread.php?t=321665
Used this one. Didn't realize it was dangerous btw, but I didnt flash when it was low. Yeah I upgraded the GSM
It is a dangerous procedure if you do not know what you're doing. Andot's PEE is a very old version. I'd suggest to install vjgrace's latest ROM (v3.3).
ok, but I dont think the battery is getting a charge >< wont stay on for long

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.

Fuze freezes after soft reset - couple days after flash?

My fuze is freezing after a soft reset, and the only solution I have found is to hard reset.
I recently flashed hard-spl and my first cooked ROM. A few days later this happened. It freezes just after the animation sequence. I hard reset the phone, set it all up again, couple days later - frozen again. Tried a different ROM, loaded fine, set it all up, couple days later - frozen. Tried a 3rd ROM, same thing.
I was running the stock at&t fuze ROM up until this with no issues. I have tried 2 different versions of the Energy ROM 2.0 and once with Shep's 6.5 ROM.
I'm getting pretty sick of setting this thing up. Any ideas, maybe a bad hard-spl flash?
I had the same problem before, i fixed it with flashing back stock rom, reflash hard-spl and trying a diffrent build of my favorite rom, and to be honest i have no idea what fixed it.
Ok thanks for the reply. I am going to try a reflash of the hard spl, and a new ROM. Something makes me think the hard spl is the problem, but a new ROM can't hurt at this point. I will post my results...... in a few days. Thanks again!
Having almost the same problem. Where exactly was it stopping?
I get the first splash-screen, afterward in the lower right corner the 3 red version numbers appear and nothing happens, i dont get to the second (animated) splashscreen, nor to the windows mobile one.
More info:
Stock Rom
--> flashed HardSPL
--> flashed PdaViet V11
--> months later V15
--> weeks later WM 6.5 Testrom, disappointed --> flashed ProvenRom 3.3
--> trouble began approx. 3 days later
--> reflashed ProvenRom 3.3
--> trouble started again, then i did a hard reset for the first time
i will try reflashing stock rom, then hardspl, than custom rom and report in a couple of days
same thing happened to my htc touch pro. i havent fixed it yet
Happened again. I had reflashed the hard-spl and then a new version of the energyROM. It froze up later that night. Iam getting the first splash, with the red numbers, romversion etc., then the animation plays, the it freezes at the end of it. I guess I will try to flash back to stock ROM and see what happens. Until someone has a fix, I guess it'll be trial and error. I'll keep you posted.
And again, twice.
I thought everything was fine, workin good for a couple of days, then it froze again. Any thoughts or further suggestions would be highly appreciated.
Seems like it happens while I am setting things up, phone starts to get laggy after a soft reset, after adding a cab that requires a soft reset. Then it freezes on the next reset.
Software Version
I think we should narrow this down by comparing the software versions.
I'll start:
Radio: 1.14.25.05
Rom: Proven 3.2, 5.07.831.17 build 5.2.21042.1.6.1
HardSPL by Olinex
now you go!
addition:
i also remember, this happened after a cab-install. Do you remember WHAT you actually tried to install? I think for me it was HomeScreenPlusPlus UI. Afterwards it was always Opera that stopped responding and i had to soft-reset --> total failure
I had the exact same problem...you can see it in the DaG 6.5 Kitchen thread. I tried flashing to a known custom Rom that I know worked and it still had the same issue. I fixed it with the advice of someone there, the same advice that's here. Flash a stock rom, hard reset....then flash a custom rom. I don't know why that fixed it but it did.
Hmmm, maybe this will work. I had tried that and it did seem to work. However, after a few days I got sick of the 6.5 and flashed back to the energyROM. So I will give this fix another shot.
In regards to the previous post here's what I am running:
radio: 1.12.25.19
Rom: EnergyROM 2.0 build 41609
Hard SPL - SPL-1.90.by Olinex
Its almost becoming funny now. I did a soft reset so I could see the radio version and guess what - it froze again.
It seems like if I don't set everything up, it will last a few days, but sooner or later I get fed up with not having progs installed etc. and after I set it up - poof!
So here is a list of cabs and general things i do to setup the phone.
Hard reset - reset at screen setup - ROM intitial setup - device reboots itself-
-PPCPIMBackup (installed on ROM, just restore contacts)
-ChangeScreen or Gyrator / have tried both individually, not at the same time
-DredSensor
-KforTouchPro
-HTCWeathermaster Rhodium
-Gscroll 2.0 (beta)
maybe something else I haven't installed every time
of course, set owner name, setup e-mail, the rhodium world clock bug setup, general tf3d setup (contacts, weather, tabs etc.)
Add shortcuts from my sd card for previously installed progs.
I'm not sure that any of these are the issue. I have done this at least ten times. Each time I have noticed which was the last cab installed then freeze, I try not to install that cab, then it will still freeze, eventually.
I am going to reflash the stock ROM and stock SPL, then hard SPL and a ROM flash. I'll be sure to post my results.
i tried latest mystic 6.5 rom lite beta 1.1 and it froze within a day at the second splash screen and after about 1-2 min the screen turned white. I have tried the battery removing trick, but same results. I'm not sure what apps i have installed after hard reset...
i tried latest romeos rom 6.1 randium edition: it got frozen after some time...
same with both NRGZ roms: 1 and 2 version (standard raphael manila and rhodium manila).
Now i'm using romeos wm6.5 rom 2.101... will post if it freezes...
i havent tried this: "reflash the stock ROM and stock SPL, then hard SPL and a ROM flash" yet...
at10ti0n said:
Now i'm using romeos wm6.5 rom 2.101... will post if it freezes...
i havent tried this: "reflash the stock ROM and stock SPL, then hard SPL and a ROM flash" yet...
Click to expand...
Click to collapse
I had no luck with this solution, and it is not exactly what was described.
Actually the solution posted is to just flash stock rom, hard reset, then flash custom rom.
I tried the above solution and it still froze, now I am going to try the correct solution posted and see what happens.
Frozen again... I am going to flash back to stock rom, stock spl, see if it still freezes.
This works (for me)
Running fine for a week:
- Flashed stock ROM (O2 German). This replaces the radio and the OS
- Went back to stock SPL. THIS IS TRICKY, SO READ(!):
+ Olinex HardSPL will NOT let you flash back to your StockSPL, because it is write-protected. This kept me up quite some time.
+ Flash your Stock ROM
+ Then, flash the hacked 195 SPL mentioned HERE: http://forum.xda-developers.com/showthread.php?t=502720
+ then, flash your Stock SPL. Read the Threads: http://forum.xda-developers.com/showthread.php?t=410150
+ Make sure, your SPL is neither Olinex, nor the hacked 195 in the third picture
+ I flashed the Stock ROM again just to be sure the stock SPL runs and allows your stock ROM to run.
- Flashed HardSPL
- Flashed Energy ROM 2.0 WITHOUT Manila, flashed latest Radio, installed cabbed Rilphone.dll
Installed Resco, Resco Today, MortPlayer - this is the SAME setup that got me caught the last time and now runs fine for a week.
This works for me. I presume some ppl get the stock SPL flashing wrong.
As i can read from other roms, it happens ONLY to Roms with the new rhodium manila,
so maybe, if you're tired of reflashing and hard reset, try one without the new manila interface.
Another suggestion: I have a different Opera now. Many describe they tried to start Opera, THEN it hangs and the phone gets stuck on bootscreen. I have 9.5 Build 15613 now and this one runs fine.
I encourage you to try energy ROM 2.0 without Manila. There seems to be a battery issue and someone uploaded a version with better battery life, you may try this, but i don't find the post anymore and this may have rhodium manila included. Energy ROM 3.0 is out now netherless, maybe someone can follow my instructions and try this with 3.0.
Hope i could help, this was bugging me SO LONG
Wow, thanks!
I have been running the stock at&t rom since my last post with no freezing. I will try this step for step, and I will try energyrom 3.0 just to let you know.
Wish me luck!
Well, I was able to get the stock SPL back, just as you described. Thanks again for the info.
However, I flashed EnergyROM3.0 and it froze after a few hours. Of course that rom has the rhodium manila cooked in, so I am going to try again with another rom. I will report back later.
from my last post i have been using romeos wm6.5 v2.101 with no freezing.. it has NO manila cooked in.
I think, maybe it has something to do with manila :-?
Same problems here as described. Using:
1.14.25.05 Radio
EnergyROM 3.0 WM6.5 50409a version
Started after flashing the WM6.5, reproduced easily after 1-2 hr of ROM on phone, it freezes (either by installing something, or Manila general use) then stays on information screen of versions.
Going to try stock ROM + reflash SPL then flash EnergyROM 3.0 again. If that wont work, i go back to 2.0 which worked well.
OK guys I am going to report this issue has been fixed (though not solved) for me.
I flashed ROMeOS wm6.5 v2101 and am also running the version of opera previously posted. I have been running for almost a week with no freezing, and (knock on wood) do not expect it to.
I am very happy with this rom and don't plan on flashing again for a while. However, if I do I will report any success/failure. I am curious to know if the problem is just certain roms, or something specific in them. If anyone else having these issues would care to post their results with other roms, it would be appreciated for the sake of the community.
I also wanted to note that I flashed the RRE wm6.5 non-manila version just before this and it did freeze on me. So it may not be related to the rhodium manila.
Anyways thanks again to all who posted and helped with this. I can't tell you how happy I am to have stable phone again!
Good luck and happy flashing!
same thing happened to my htc touch pro. i havent fixed it yet

Categories

Resources