why can't i flash any NBD roms? - 8125, K-JAM, P4300, MDA Vario ROM Development

i have a G4 IPS/SPL 2.25.0001 and i follow all of mun's steps to flash roms and everything usually works fine, i installed the windows titanium rom last night and was loving it but whenever i try to install NBD's roms everything goes fine with the shelltool and when i do a hard reset it freezes at the cingular screen that displays the IPL/GSM info, it's done this three times in a row with 3 different versions of NBD's roms
i'll flash back to titanium but what could be the cause of this?
any help would be appreciated

on my cidlocked g4 whenever i shelltooled NBD from a cingular base rom it would always get stuck at the cingular boot screen. Only way i can get NBD to run is to use shelltools over the wizardlove rom.

pr0naLd said:
on my cidlocked g4 whenever i shelltooled NBD from a cingular base rom it would always get stuck at the cingular boot screen. Only way i can get NBD to run is to use shelltools over the wizardlove rom.
Click to expand...
Click to collapse
i tried from a windows titanium rom and the cingular manufacturer rom, i'll try the wizardlove rom thank you
if anybody feels like answering: why does this make a difference?

yep that did it, the NBD rom worked after i flashed wizardlove first
weird

Wizardloverom is an amazing piece of engineering. Ask anyone how they "saved" their wizard.. 9 times outta 10, wizardloverom.

How long does it take, on average, for you guys to flash the NBD rom? WizardLove almost always goes on in about 8 minutes, but NBD just sits there indefinitely, and I'm dubious about doing a Hard-Reset without confirmation that the flashing procedure is finished.

Yes, it is confirmed that sometimes shelltool doesn't report on flash complete.
Just doing a hard reset after waiting is fine.

Related

Best stable ROM for my model

Two questions:
1. How do I tell what generation my Prophet is? I see a lot of references to G3 and G4 but no information on how to work this out.
2. I currently have the latest i-mate JAMin rom, which is AKU2.0. Is there is a stable AKU2.3 ROM people have been using or is this still "experimental" It's hard to work this out from the threads.
Thanks all.
spaceboy said:
Two questions:
1. How do I tell what generation my Prophet is? I see a lot of references to G3 and G4 but no information on how to work this out.
2. I currently have the latest i-mate JAMin rom, which is AKU2.0. Is there is a stable AKU2.3 ROM people have been using or is this still "experimental" It's hard to work this out from the threads.
Thanks all.
Click to expand...
Click to collapse
1: during bootup, 2nd screen find
SPL
2.xx.0001 = g4
2.xx.0000 = g3
2: aku 2.3 seems very stable. Everything works as expected. i've only installed one version, after reading this thread: http://forum.xda-developers.com/sho...ht=16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe
it's the 16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe from this sites' ftp. It has been much more stable and responsive (due to the larger cache) then the preinstalled AKU2.0 on my qtek s200. Boot time is shortened by about 20s.
Before you install this you HAVE to unlock the CID:
http://wiki.xda-developers.com/index.php?pagename=Prophet_Upgrades
i didn't do this first time, and had to find a valid qtek rom that would install, since my device didn't bootup anymore..
Thanks for that. A question about unlocking the CID:
On the Prophet upgrade page you link to, it has the warning (3 times, in bold!): *WARNING!!!!! DO NOT PERFORM THIS IF YOUR PROPHET HAS THIS ROM "SPL 2.xx.0001" (New G4 Version)
Don't all G4's have that ROM? Mine does (2.13.0001). So where does that leave us for unlocking?
Thanks again.
Im also running a JAMin with the latest official rom and ive seen some good things about the 2.3 updates but im new to the whole cooked roms thing but ill figure it out.
What would I loose by upgrading from my JAMin rom and what would I gain?
Can I go back to my jamin rom if I dont like it?
I have installed the latest DOPOD ROM and I run it native without any soft installed and I reboot only about 1 a month!
To partially answer my own question: The CID unlock process looks like it IS for G3s only. To upgrade G4s you use pdocwrite.exe.
I've seen the details for using pdocwrite to install the pdamobiz ROM, but has anyone used it to install the 16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe?
Cheers
dannyoneill said:
Im also running a JAMin with the latest official rom and ive seen some good things about the 2.3 updates but im new to the whole cooked roms thing but ill figure it out.
What would I loose by upgrading from my JAMin rom and what would I gain?
Can I go back to my jamin rom if I dont like it?
Click to expand...
Click to collapse
I'm guessing you'd loose some of the vendor customisations - which really are only some useless themes and the network provider settings - which for me just means setting up GPRS. Of course, you also risk loosing your JAMin entirely if you stuff it up
What you gain is a more up-to-date OS which is faster...
what about the extended rom? all the custom stuff is in there, i can access it no probs but would that remain with the rom mentioned above?
would I still be able to run them (if I back them up)
just been researching this rom, looks like it defaults overclocks your device and installs a ton and I mean a ton of apps that most people dont want.
Be warned, its heavily customized and may not be to everyones liking.
Anyone know if I do upgrade to this and unlock my CID if I can then re-apply the official JAMin rom?
dannyoneill said:
just been researching this rom, looks like it defaults overclocks your device and installs a ton and I mean a ton of apps that most people dont want.
Be warned, its heavily customized and may not be to everyones liking.
Anyone know if I do upgrade to this and unlock my CID if I can then re-apply the official JAMin rom?
Click to expand...
Click to collapse
To anyone reading this, here is my experience as of last night.
On my G4 I tried installing 16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe after first hard-resetting my device. The installer went ahead fine, but it would not start-up: it would not get past the boot loader screen. So I reinstalled the latest i-mate ROM, booted up, then proceeded to try: ftp://xda:[email protected]/2006-10-05_Upgrade ROM_AKU2.3_lvsw.rar.
This uses the PDAmobiz method to upgrade a G4 which is essentially running a batch file while it unlocks and writes to the ExtRom and the ROM - then doing a hard reset, but it is not the PDAmobiz ROM.
This worked fine, and I now have AKU2.3. Even better, it is not customised, so there's no extra software installed, which I'm happy about. It's been running over night and seems very stable so far. I'm not sure what the paging size is on the ROM, maybe it's smaller = more stability.
So that's my experience!
My experience:
My JAMin running IPL/SPL 2.13.0001 using that rar file that worked for you...
hung on the copy of the OS to the device.
Trying now to recover it by downloading and trying to install latest JAMin update.
I cant get activesync / network connection using USB to phone... Don't know if that will be a problem trying to recover. Its sitting at the 3 colour screen atm.
Is there a way for me to update to IPL/SPL 2.15.0001 from 2.13.0001 before trying again? (assuming my phone is not already dead).
orian said:
My experience:
My JAMin running IPL/SPL 2.13.0001 using that rar file that worked for you...
hung on the copy of the OS to the device.
Trying now to recover it by downloading and trying to install latest JAMin update.
I cant get activesync / network connection using USB to phone... Don't know if that will be a problem trying to recover. Its sitting at the 3 colour screen atm.
Is there a way for me to update to IPL/SPL 2.15.0001 from 2.13.0001 before trying again? (assuming my phone is not already dead).
Click to expand...
Click to collapse
If your phone is G4, you should be able to install the vendor ROM no problem - which is magical really. You don't need ActiveSync running; well - it won't connect as the device is dead .
When you say it hung copying the file... it took a good 15-20 minutes to copy across for me, so I hope you weren't just being impatient.
yeah the JAMin rom worked so I'm back where I began.
I did wait 30 mins and it had crashed.... activesync wasnt doing anything, buttons / screen taps weren't working on pda.
Is it because I am running 2.13.0001 is my worry? The update specifies its for 2.15.0001. Is there any way I can update to 2.15.0001 from 2.13.0001 before trying again?
Cheers.
Tried the update again, and this time it worked.
Device is running AKU2.3 now, but still says 2.13.0001 for ipl and spl on boot.
Any ideas anyone on how I can update that to 2.15.0001? and what kind of change that makes anyway?
Thanks all.
dannyoneill said:
just been researching this rom, looks like it defaults overclocks your device and installs a ton and I mean a ton of apps that most people dont want.
Be warned, its heavily customized and may not be to everyones liking.
Anyone know if I do upgrade to this and unlock my CID if I can then re-apply the official JAMin rom?
Click to expand...
Click to collapse
you have been researching a different rom. this one does certainly NOT overclock the device by default. And it's a clean install, without any overhead, but WITH the stereo bluetooth headset support. perfect for my uses.
looks like i was looking at another rom, one loaded with junk.
I took the plunge and updated my jamin to the 16mb 4pda rom and im now back on the official jamin, it was way too unstable. Today I rebooted 5 times.
The volume is too low on headset and loud speaker
and some other annoyances.
I need stability
when i'm using AKU2.3,
in Settings / Regional Settings:
there is no "Turkey" option (also Russian).
how can i do that, is there a patch for apply these regions ?
thats why i'm using latest official jamin rom now (wwe) (from clubimate.com)
Ive found the source of instability with the 4PDA rom. Its the radio rom 02.30.21
I went back to my old ROM on my jamin and all was fine, a day without crash, Then loaded on radio rom 02.30.21, hardreset for good measure and setup again,. same as always.
Then, every hour or so im resetting.
Back to official jamin rom and all is fine again.
Radio ROM 02.30.21 is just totally unstable. Ideally I would like the AKU2.3 updated rom but without this awful radio rom they seem to be putting in them all.

HELP. Brick after Crossbow Most Beautiful Edition

Hello all,
i have installed Windows Mobile Crossbow Most Beautiful Edition and every thing wenk ok during the installation but now after i finished flashing the ROM i am stuck on the splash screen and my wizard keeps reseting and fails to pass the splash screen.
i have tried to reflash another ROM but i can't even start the bootloader (3 colors screen)
pleaes, what shall i do?
you already tried holding down the camera button and pressing the power button?
ammar said:
Hello all,
i have installed Windows Mobile Crossbow Most Beautiful Edition and every thing wenk ok during the installation but now after i finished flashing the ROM i am stuck on the splash screen and my wizard keeps reseting and fails to pass the splash screen.
i have tried to reflash another ROM but i can't even start the bootloader (3 colors screen)
pleaes, what shall i do?
Click to expand...
Click to collapse
downgrade to this ROM :
http://rapidshare.com/files/18711114/CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe
this is the way to solve the problem and then after downgrading to this ROM u can the unlock and then install any other ROM but u must first downgrade to this ROM downlaod it from the link above
Perhaps the best way to restore your device its using the Love Rom.
Flash, and flash again the WM6 ROM, follow the Shell Tool method closely and you will have your device working in no time.
It worth the pain, believe me
Hi,
Thanks you all for your help
i have used the camera button and the stylus to get it into the boot loader and then i reflashed my original k-Jam rom with IPL/SPL 2.16 then i flashed again crossbow ROM and it worked.
it seems that after CID unloking i had IPL/SPL 1.01 and i should have reflash a ROM with higher IPL/SPL before WM6. so the idea is to get a stable ROM with SPL 2.26 like everybody here is doing but i tried my 2.16 and it is ok now.
Regards.
golfernutnflorida said:
What rom is that you are referring to? Is that the Button rom or the Wizard Love Rom?
Click to expand...
Click to collapse
that is the orignal first ROM for Wizard that came out first from the factory with this ROM THIS is the first ROM for wizard i mean the oldest one !!
QUICK FIX for WM6 Won't Boot/Resetting Problem
I've had the problem mentioned in this thread every time I've loaded a WM6 rom. Last summer, I fell in the lake with my wizard so I've always attributed weird problems to the water exposure.
Anyway, when your rom won't boot. Here's a trick that works for me. Do a soft reset, then as soon as you get into the green screen with the spiral, open your keyboard and hold down the space bar. My rom has ALWAYS booted when I do this.
I got the idea from and old PC repair trick. Good luck.
Always upgrade to a 2.xx original ROM before upgrade further. I always use the T-Mobile 2.26 ROM.

unlocked g3 suddenly won't flash TNT

i have a g3 ipl/spl 2.26 completely unlocked device that i have flashed many wm6 roms on in the past. my touchscreen went dead in landscape mode so on a hunch i flashed back to wm5 to try and fix it (which it did). but now i flash the same TNT rom i've flashed a hundred times the same way and everything changes but the OS i tried the boring rom and it changed, but even from there it seems (now) that it's TNT that for some reason won't change the os. any ideas?
which WM5 ROM did you flash back to? was it the official t-mobile ROM?
if not I'd try that first...
if that doesn't work I'd actually take it through the unlocking process again and use that CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM first...the up to t-mobile's offical ROM...then flash to TNT
i flashed back to the latest tmo rom. i'll give what you're talking about a try. as a test i flashed to that one and that's the first one to change the OS. this whole thing caught me by surprise that's for sure.
hope it works for ya...let me know...
update, problem solved! i was using the touchflo rom (love it) and i gave the Professional flavor without the touchflo a try and it worked. all is well.
j3d1n4s7y said:
if that doesn't work I'd actually take it through the unlocking process again and use that CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM first...the up to t-mobile's offical ROM...then flash to TNT
Click to expand...
Click to collapse
hi,
i have the same problem here
what exactly do you mean with "take it through the unlocking process again" should i unlock the wizard again with the service tool (mine is already unlocked and i had 2 different versions of wm6 roms) or just flash the CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM and then the t-mobile one?
p/s before flashing the tnt touchflo i flashed the t-mobile rom, and then while flashing the TNT touchflo i got error on 99%. After that the wizard boots only in boot manager and i can only flash t-mobile rom, the other roms i have tested give back errors (i have not tested the CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM)
Thanks!!!
Regards
i grabbed the latest lokiwiz and used one of the forum stickies as a guide and relocked it and then followed step by step to unlock again. i can't confirm or deny that solved the problem, but it's worth a shot.

Dutty 6.1 + 1.64.08.21 = Brick?

Hey folks -
I upgraded my ATT Tilt to DUtty's 6.1 today (first time flashing).
Anyway, after sound wasn't working I read up on the radio information and decided to go with 1.64.08.21 based upon what some folks said worked for them in various posts.
To flash the ROM, I am using JumpSPL1.56-KAIS.exe loaded onto the device.
Dutty's worked fine, but the radio made it to 99% then hung. I waited for 3-4 minutes and nothing happened, but the flashing tool said it lost connection. I followed the recover steps including a hard reboot (and went to the tree color screen with "serial" at the bottom), but now each try just hangs at 0% when trying to install the radio ROM.
What do I do?
Thanks,
Tom
pearsth said:
Hey folks -
I upgraded my ATT Tilt to DUtty's 6.1 today (first time flashing).
Anyway, after sound wasn't working I read up on the radio information and decided to go with 1.64.08.21 based upon what some folks said worked for them in various posts.
To flash the ROM, I am using JumpSPL1.56-KAIS.exe loaded onto the device.
Dutty's worked fine, but the radio made it to 99% then hung. I waited for 3-4 minutes and nothing happened, but the flashing tool said it lost connection. I followed the recover steps including a hard reboot (and went to the tree color screen with "serial" at the bottom), but now each try just hangs at 0% when trying to install the radio ROM.
What do I do?
Thanks,
Tom
Click to expand...
Click to collapse
from what i understand you cant flash a radio with the jumpspl. why not install hardspl and be done with it. it's a one time thing.
DELETED... Above is better^^
pearsth said:
Hey folks -
I upgraded my ATT Tilt to DUtty's 6.1 today (first time flashing).
Anyway, after sound wasn't working I read up on the radio information and decided to go with 1.64.08.21 based upon what some folks said worked for them in various posts.
To flash the ROM, I am using JumpSPL1.56-KAIS.exe loaded onto the device.
Dutty's worked fine, but the radio made it to 99% then hung. I waited for 3-4 minutes and nothing happened, but the flashing tool said it lost connection. I followed the recover steps including a hard reboot (and went to the tree color screen with "serial" at the bottom), but now each try just hangs at 0% when trying to install the radio ROM.
What do I do?
Thanks,
Tom
Click to expand...
Click to collapse
1.) Disable USB connections in activesync.
2.) Put your phone into the tri-color screen.
3.) Flash the original shipped ROM.
Something i learned this past week from another poster, that had a problem. U can't JumpSPL a radio Rom.
Try flashing a 6.0 rom and see from there. I assume you couldn't Hard SSPL your device? if this is not the case then your better off doing that
I tried hardspl and it didn't work - constant white screen.
Thanks for the tip on original ROM, trying that now.
Tom
pearsth said:
I tried hardspl and it didn't work - constant white screen.
Thanks for the tip on original ROM, trying that now.
Tom
Click to expand...
Click to collapse
did you try the hrdspl, white screen solved thread?
http://forum.xda-developers.com/showthread.php?t=354061
jocky made it so you can flash hardspl from what I understand.
you can also try this to get hardspl on your device.
http://forum.xda-developers.com/showthread.php?t=361236
Does this mean I need to avoid flashing at all if I cannot use hardspl?
avoid flashing radio, but try the links that tater posted and see if it solves your problem.
Thanks, everyone...just got back to ATT stock rom and all is well again. Will try the links posted above!
Tom
pearsth said:
Thanks, everyone...just got back to ATT stock rom and all is well again. Will try the links posted above!
Tom
Click to expand...
Click to collapse
just be careful to follow the instructions to the letter. Good luck.
Just finished re-doing everything. I was confused regarding the fact that JumpSPL didn't replace HardSPL, it just helped getting it working.
Just finished reinstalling ditty and the same radio version and all is working great.
Now off to figure out how to play with TouchFlo and Cube.
Thanks!!!
pearsth said:
Just finished re-doing everything. I was confused regarding the fact that JumpSPL didn't replace HardSPL, it just helped getting it working.
Just finished reinstalling ditty and the same radio version and all is working great.
Now off to figure out how to play with TouchFlo and Cube.
Thanks!!!
Click to expand...
Click to collapse
very welcome. glad to see you back up and running.

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