Hi, ive flashed a few handsets before (wallaby x2, alpine and a wizard) and had no problems but for some reason cannot even get off the first hurdle with my t-mobile vario iv and cant even unlock the dam thing to flash a custom rom! ive looked at post after post and downloaded so many programs like hard spl and nothing works. the programs ether wont even open or they fail half way through the process but havent bricked my phone so far (fingers and toes crossed!) please could someone help me with what unlocking software i need, what radio rom and main rom i should be using. Really i would like to try a standard wm6.5 rom and then try custom roms after but like what nrg have done if stock is not avaliable. its model is RAPH300 part no- 99HFP013-00
my current rom version is 1.69.110.8 WWE
my current radio version is 1.02.25.19
protocol version 52.33.25.17U
my email is [email protected] if you prefer to help via email
thanks in advance everyone, steve.
Anyone out there?
Ensure you have hard SPL'd your handset before trying to flash ANY custom roms
before you do that, see if there is an updated T-Mobile rom, see if that update will work, if that update works without any glitches then it'll be alright, if you get an error with an official update then possibly something wrong with either your pc setup or the handset
if your using vista, make sure you've got the windows mobile device centre installed, if not, you need to go to microsoft and download it
if using windows xp, make sure you've got the latest activesync installed.
ensure the cable your using is not faulty by trying it with a different cable
and good luck!
duke_stix said:
Ensure you have hard SPL'd your handset before trying to flash ANY custom roms
before you do that, see if there is an updated T-Mobile rom, see if that update will work, if that update works without any glitches then it'll be alright, if you get an error with an official update then possibly something wrong with either your pc setup or the handset
if your using vista, make sure you've got the windows mobile device centre installed, if not, you need to go to microsoft and download it
if using windows xp, make sure you've got the latest activesync installed.
ensure the cable your using is not faulty by trying it with a different cable
and good luck!
Click to expand...
Click to collapse
thanks for trying to help, have you ever read something over and over and repeatedly missed something in it? i think thats what i did wrong. i did not see the bit about removing my sim card even though i had read the noobs guide again and again. removed my sim and bosh, spl worked! then everything else was a breeze and i am now running the energy 3.0 wm6.5 rom! havent flashed the radio yet but will probably do that today. the energy rom is a vast improvement on my stock 6.1 rom in many areas and seems to have improved camera performance quite a lot (not quality) and the menus are going to be great once i have got used to the totally different interface. does anyone have any sugestions on other roms tha may be better than this one?
Hi there
Glad to hear you got it working!
I am personally using NATF's WM6.1 lite touch pro rom as all i look for in a rom is stability as i actually use my phone for phone/text purposes and there is nothing more annoying than a hanging phone when your trying to quickly reply to a text message!
Related
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.
I'm having trouble with my Tilt (it recently started being randomly unresponsive to commands (15-20 second lag some times). Is there going to be a new AT&T 6.1 official ROM with updated drivers? My device has the 8-25-07 ROM date, and before I decide what to do I'm checking on the status of official AT&T releases.
No, as far as I know, there isn't an official one yet. However, a lot of the cooked ROMs on this site will probably fix your problem.
If you can't wait for the official ATT WM6.1 release then you could try their latest WM6.0 release http://www.htc.com/us/FAQ_Detail.aspx?p_id=67&act=sd or as mentioned, could try a cooked ROM.
upgrade ur hardspl and the lags/freezes will be gone.
thesire said:
upgrade ur hardspl and the lags/freezes will be gone.
Click to expand...
Click to collapse
Looks like he is still using an old Stock ATT Tilt ROM (WM 6.0), so that is not likely the issue.
@ gmfeld. If you have had your Tilt for a quote some time, it is possible that you simply have some junk, or orphaned registry settings, or something slowing your system down.
I would recommend either upgrading your ROM to the latest Stock ATT Tilt ROM (as posted above), or simply doing a Hard Reset to get your current ROM back to its original state. Of course, do a BACKUP before you do anything that involves Hard Reset or Flashing!!!1
I just got my tilt and I think I have a newer official version.
It is
ROM 1.62.502.0
Date 01/17/08
Radio 1.27.14.09
I've noticed it has a bluetooth headset issue (not sure if it is exclusive to mine) where it will end the call, but won't hang up in the phone program.
gmfeld & vanisher,
I would suggest you at least run PPCPimBackup then a hard reset. If you have a little time this weekend you should read through G.W.E.N.I. then flash a nice cooked ROM. Play with your device and post educated questions in the proper threads. You WILL appreciate your device more than you ever did...guaranteed.
http://forum.xda-developers.com/showpost.php?p=2273408&postcount=2561
The above is a noob success story. I would recommend you go the same ROM route as he did as for starters.
There is no official AT&T WM6.1 ROM yet, but we're getting there.
Check the shipped ROMs section on the wiki to see how new / old your ROM is.
kwickone said:
Looks like he is still using an old Stock ATT Tilt ROM (WM 6.0), so that is not likely the issue.
@ gmfeld. If you have had your Tilt for a quote some time, it is possible that you simply have some junk, or orphaned registry settings, or something slowing your system down.
I would recommend either upgrading your ROM to the latest Stock ATT Tilt ROM (as posted above), or simply doing a Hard Reset to get your current ROM back to its original state. Of course, do a BACKUP before you do anything that involves Hard Reset or Flashing!!!1
Click to expand...
Click to collapse
Thanks to all for all the suggestions. I've been running SKTools, so I'm pretty sure I've gotten rid of all the junk and orphaned registry settings, etc.
I agree with all that I need to flash a new ROM, or reflash my original ROM, that's the only thing left to do to clean up my Tilt. Just trying to get some info on when or if a new official AT&T 6.1 ROM is to be released, so I don't go through that process twice. If I knew that its a ways off, I will probably then go with one of the cooked ROMS now.
I would need some help to understand the following :
whatever ROM i try to install, after successfull flash and the following reboot when you get the "customization will start in 3 sec", it always hang on the "Installing WM6_PPC_HTC_Opera9_WWE.CAB" (last time i wait 5h to see if it move)
i tried RomeOS1.01 as well as 1.02 (just a few minutes ago), same also happen with DCS-TouchProv13 or even when i try to revert to RUU_raphaelWWE1.66...
i have a successfull HardSPL1.90.1.3 Olinex properly showing up on the 3 color screen.
Soft reset allow me to use the phone with a somehow successfull install ? (i get some of the appz but not sure it is 100% successfull / how can i check??)
Only concern is that the phone get warm around the camera/speaker after a few hours of usage and battery doesnt sound very powerfull (full load stay on about 5 to 6h with no bluetooth but wifi on)
original is an XDA diamond pro from o2 germany (model RAPH120)
as of right now i have
ROM: ROMeOSv1.02 WWE
Radio: 1.02.25.11
Protocol 52.33.25.17u
Any idea why the custom... always hang on the Opera install ? i dont care to not use opera or dl and install it myself afterward ??
thks
Stephane
(frenchy leaving in Germany and working for a US company.... cannot afford to use a DE phone only )
How about flash ur stock ROM back, then revert the stock SPL. There may be semething wrong with ur device
GERMAN ROM
http://forum.xda-developers.com/showthread.php?t=426400
German ROM work fine
Guess what .... after flashing back to a german ROM (thks for the link to an htc oiginal ) the "customization" with Opera9_DE went well and finish up normally.
i am going to work/play a bit with the German version to make sure it does not come from the device
any other idea in how/why my German o2 xda does not love all the great simple ROM cooked here ??
is any o2 Germany user here havig successfully flashed their xda with an English (or French ) ROM ??
Thanks guys for the great work you do here !
Steph.
I am seeing this exact same issue.
I have had no end of grief flashing my Raph, I maintain an XP VM (I am on OS X) entirely for flashing. I have flashed many different devices with dozens of ROMs and never had a problem until I got the Raphael. I have seen BSOD's and numerous connection issues while flashing using both Raphael_CustomRUU_v1.2 and RaphaelWrapper.
Also, every ROM I have flashed (on a XP SP3 box I put together from old pieces just to flash this bastard) has hung whilst installing opera.
I am using the o2 uk variant (as yet unreleased XDA Serra).
It is a RAPH120, is this unique to o2 devices?
Would appriciate any help getting this sorted, it could become a more widespread problem with the o2 uk variant is released, as there may be an influx people wondering why their device wont flash properly.
nb. I have an unreleased o2 built ROM (RUU_Raphael_O2_UK_1.60.206.1_radio_sign_52.29.25.12_1.01.25.16_Test.exe) that flashes and installs fine even from inside my VM.
Thanks in advance for any help anyone could provide!
[UPDATE] I tried installing Opera build 1957 from a cab and it worked fine.
maybe a dumb suggestion... but try to get your device unlocked and see what happen
I checked with Oli about whether unlocking would help:
Olipro said:
I see, then that's a weird issue, however, not related or fixable by the unlocker.
your best bet is to do a soft reset as soon as the customization dialog appears and see what happens.
I was initially suspecting it could be region protection, but in those cases, the ROM doesn't boot at all, so your case is a strange one.
Click to expand...
Click to collapse
So no leads there, as an interim solution I will repack ROMeOS² v1.03 without Opera and see how that works out.
i have the same device and the same problem. I will try to repack it with the german version of opera..
Oh dear, so it would appear that current roms do not work on O2 variant devices...
Has anyone successfully flashed an O2 device (with a cooked rom)?
I have hit some problems repacking ROMeOS² as hung has included measures to stop people making their own roms based on his. I pm'd him last night asking if he could help us out, but as of yet I have not recieved a reply.
I will probably start making my own rom from scratch tonight, but its a fair bit of work just to take opera out of the customization sequence. Hopefully its just some odd bug in the opera install, rather than something more serious. I guess worst case scenario is that after opera is removed it just crashes at another point during the costomization process.
[UPDATE]
hang.tuah said:
@dabs
I'll try to make it [ROMeOS² without Opera] for v1.04 mate, thanks for ur support..
Click to expand...
Click to collapse
Excellent, so at least we have a workaround in the pipeline. Still, it would be best to find the cause of the problem, as not all cooks have the time and dedication to make special versions of their roms for a small sub-set of users.
Actually Opera is included but with no device specific & v1.04 is done
smaier said:
I would need some help to understand the following :
whatever ROM i try to install, after successfull flash and the following reboot when you get the "customization will start in 3 sec", it always hang on the "Installing WM6_PPC_HTC_Opera9_WWE.CAB" (last time i wait 5h to see if it move)
i tried RomeOS1.01 as well as 1.02 (just a few minutes ago), same also happen with DCS-TouchProv13 or even when i try to revert to RUU_raphaelWWE1.66...
i have a successfull HardSPL1.90.1.3 Olinex properly showing up on the 3 color screen.
Soft reset allow me to use the phone with a somehow successfull install ? (i get some of the appz but not sure it is 100% successfull / how can i check??)
Only concern is that the phone get warm around the camera/speaker after a few hours of usage and battery doesnt sound very powerfull (full load stay on about 5 to 6h with no bluetooth but wifi on)
original is an XDA diamond pro from o2 germany (model RAPH120)
as of right now i have
ROM: ROMeOSv1.02 WWE
Radio: 1.02.25.11
Protocol 52.33.25.17u
Any idea why the custom... always hang on the Opera install ? i dont care to not use opera or dl and install it myself afterward ??
thks
Stephane
(frenchy leaving in Germany and working for a US company.... cannot afford to use a DE phone only )
Click to expand...
Click to collapse
Hi Stephane and others having similar trouble,
I had the same situation but my original ROM was Japanese, after trying a lot of possible official WWE versions for flashing and cooked ROMs, only one version worked.. Check the official WWE version Singtel.. it worked up to customization without problem.. the only difference the default internet page is Singtel but it is not a problem cause I can still go to the other sites..
Hi, I hope this is a good place to put this question, I would put this in the Vogue forum but it looks kind of slow-moving, so I figured I might as well turn it over to the experts. I encountered a problem on my first real ROM flash and now I'm kind of worried to try it again. So:
I'm using a Verizon XV6900/Vogue/TouchCDMA. I flashed to the leaked Verizon 6.1 upgrade, which worked flawlessly, and enabled Win 6.1, EV-DO Rev. A., and GPS with the Valhalla CAB. Then I decided to try some custom ROMs.
I unlocked without a problem, and confirmed that I achieved 2.31 coke. I then lauched the ROM update utility on a WDM ROM I got from here. It got hung up 69% through, the RUU tried to help me but failed at 69% again. It gave me an error 262 connection error, but couldn't give any more details.
I thought I had bricked my phone, but while stuck on the three-color screen I flashed back to the leaked Verizon ROM and authenticated, now I'm fine.
I'm guessing that the Verizon radio (3.37) wasn't new enough, since most other ROMs require the new Bell 3.42.
The actual question part: Should I update my radio and try WDM's again, or should I give something else a shot? I'm looking for something stable that includes M2D, and some of that new Opal stuff (title bar, Youtube, etc.) OMJ's also looks promising.
P.S. What exactly is User customization, and will flashing a non-carrier-specific ROM like this one affect my ability to connect to Verizon?
it isn't a problem of being "new enough" it has to do with radio compatibility.
That page specifically says flash version 3.42
I imagine user cusomization is refering to "uc" compliant roms that allow you to automatically install cabs from your storage card after a flash
Hmm, I really don't see a mention of it on the page, I guess I'm just supposed to assume 3.42 because it says simply, "update radio." Thanks though.
EDIT: Well I used a ROM that's compatible with 3.37 compatible, and it works great. I guess this thread is over now.
Hi,
Well i was trying to update the version i had to a different one i had seen.
It is quite a old version PDAVIETS 4.0.0.0.3A, i was using, wi-fi everything worked fine really, pretty good rom, i have found that i am on windows 7 and upgrading can be dodgy.
I would always disconnect as the upgrade was starting in active sync even though i unchecked advanced network in prophet. This would happen for any other prophet rom. [ a few had said that this was a active sync problem]
Then found that somehow the PDAVIET 4.0.0.0.3A updated my phone as the flash method was a bit different.
I tried another rom this way but for some reason it started to flash then hung on the screen. over 30 mins later still the same, normally it would only take 10-20 mins.
Now it will only go into bootloader or bootup to the screen showing loader version etc.
Someone please advise me best way to bring it back.
I do have the orange no vendor rom, should i use this ? Although in windows 7 it wouldn't work.
Would i be best using xp for it ?
I presume it can be rebooted again with a op, i hope so.
Many thanks.
*UPDATE* I fixed the bootup !
In windows 7 i updated QTEK rom and now have new radio version ! Then used PDAViet rom 4.0.0.0 [ what seems to be only rom that works for me in w7]
Now happy again, even though this is old tech and i have had better, overclocked and with wi-fi make it handy.
Peace to the xda crew !
FRAGEYE said:
Hi,
Well i was trying to update the version i had to a different one i had seen.
It is quite a old version PDAVIETS 4.0.0.0.3A, i was using, wi-fi everything worked fine really, pretty good rom, i have found that i am on windows 7 and upgrading can be dodgy.
I would always disconnect as the upgrade was starting in active sync even though i unchecked advanced network in prophet. This would happen for any other prophet rom. [ a few had said that this was a active sync problem]
Then found that somehow the PDAVIET 4.0.0.0.3A updated my phone as the flash method was a bit different.
I tried another rom this way but for some reason it started to flash then hung on the screen. over 30 mins later still the same, normally it would only take 10-20 mins.
Now it will only go into bootloader or bootup to the screen showing loader version etc.
Someone please advise me best way to bring it back.
I do have the orange no vendor rom, should i use this ? Although in windows 7 it wouldn't work.
Would i be best using xp for it ?
I presume it can be rebooted again with a op, i hope so.
Many thanks.
*UPDATE* I fixed the bootup !
In windows 7 i updated QTEK rom and now have new radio version ! Then used PDAViet rom 4.0.0.0 [ what seems to be only rom that works for me in w7]
Now happy again, even though this is old tech and i have had better, overclocked and with wi-fi make it handy.
Peace to the xda crew !
Click to expand...
Click to collapse
Glad you have recovered your prophet have you installed the vista\windows 7 drivers ?
I have a little old laptop with XP that i use for flashing but i am sure that most of the new ROMs work fine with those drivers on windows 7
Here is the link to drivers and new RUU
http://forum.xda-developers.com/showthread.php?t=534707
you can use something like vmware or windows virtual pc in it's built in win7 ... it's very usefull
wapvirus said:
Glad you have recovered your prophet have you installed the vista\windows 7 drivers ?
I have a little old laptop with XP that i use for flashing but i am sure that most of the new ROMs work fine with those drivers on windows 7
Here is the link to drivers and new RUU
http://forum.xda-developers.com/showthread.php?t=534707
Click to expand...
Click to collapse
thank you for answers .
its working very well now