hey hey.
I tried the Simunlocker by jotach
Everything works fine. I get the code to enter, but the field for the 8 digit PIN isn´t there because I only can make Emergency calls...
I thougt it could be ROM problem and I´ve testet all HTC ROM till 1.57. and Installed the radio 1.0
No success.
I read about more people with this problem and without success. Is there another way to unlock? Or is this Phone to new?
Any comment is welcome!
Look on the vert first post under sticky. Unlock your Kaiser is o simple. I test my unlock Tilt with T-Mobile SIM I pop off my iphone. Wow, it works!!!!
Now, I can switch my Tilt with my iphone when ever I need it!!
farmer.joe said:
hey hey.
I tried the Simunlocker by jotach
Everything works fine. I get the code to enter, but the field for the 8 digit PIN isn´t there because I only can make Emergency calls...
I thougt it could be ROM problem and I´ve testet all HTC ROM till 1.57. and Installed the radio 1.0
No success.
I read about more people with this problem and without success. Is there another way to unlock? Or is this Phone to new?
Any comment is welcome!
Click to expand...
Click to collapse
Are you using a 6.1 ROM or 6.0 ROM? I had the same problem with a 6.1 ROM. I was forced to downgrade to a 6.0 ROM, Load the simunlocker, then load up the 6.1 ROM again. Hope this helps, Let me know how it goes.
Hi.
I appear to be having problems and my phone now thinks there is no sim inserted!!
#5. After you unpacked the download you see directories "step1" and "step2". Go into directory "step1" and run KaiserCustomRUU.exe.
This will flash the special patched radio rom. Follow the instructions until it is finished.
Everything was fine up to here!
Note that you can also skip step 6. and proceed with step 7.
#6. Power off your Kaiser and insert a 'strange' SIM, i.e. a SIM from another provider than the one your phone is locked to.
After changing sim as per #6, it now says “Insert SIM card”. – not proceeded to stage #7 yet.
#7. Once Windows Mobile has booted up it will (usually after you have entered the usual 4-digit PIN) show a window called "Simlock" and a textbox where you can enter a 8-digit unlockcode. Now perform a soft reset by pressing the reset button *but* at the same time keep the camera button pressed. If you did it well you will be back in bootloader mode and you see the tri-color screen. The best technique is to press and hold the camera button first and then shortly press the reset button with the stylus.
Anyone got any ideas, as my phone now does not recognise either my original sim or my spare sim.
I see there are a number of people who have experienced this problem.
My phone is the MDA Vario 3 on T-Mobile.
I didn't take a note of the correct ROM reference, only the bottom line which was "P 1.56.110.4", so I wouldn't know which ROM to flash it back to at the end.
All other functions are fine. WiFi, GPS and all my settings. I now have an american keyboard, so lost the £ (£) sign.
It will not recognise either my UK T-Mobile sim or my UK 3 sim.
MSanad said:
Are you using a 6.1 ROM or 6.0 ROM? I had the same problem with a 6.1 ROM. I was forced to downgrade to a 6.0 ROM, Load the simunlocker, then load up the 6.1 ROM again. Hope this helps, Let me know how it goes.
Click to expand...
Click to collapse
I tried with 6.0 and 6.1 !! HTC ROM, AT&T ROM dont work for me.
I downloaded them here: http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
No success and i´ve tested lots of them!
I had exactly the same problem. Caused me a right headache, follow these steps:-
You are more than likely running 6.0 or 6.1 rom, you will need to downgrade first to a rom that's 5.xx first. Then run the Simunlocker and it will work and you will notice the icon to click "OK" on the sim entry screen will appear.
You can then reflash back to the rom that you are currently using, but I would suggest flashing dutty's rom as it's the best.
So to recap:-
1) Downgrade to a rom that's 5.xx first
2) Then run Simunlocker.
3) Then reflash to your current rom or Dutty's.
4) Might be wise to make a note of the radio version you are using as well and then reflash this again.
Good luck.
techceptional said:
I had exactly the same problem. Caused me a right headache, follow these steps:-
You are more than likely running 6.0 or 6.1 rom, you will need to downgrade first to a rom that's 5.xx first. Then run the Simunlocker and it will work and you will notice the icon to click "OK" on the sim entry screen will appear.
You can then reflash back to the rom that you are currently using, but I would suggest flashing dutty's rom as it's the best.
So to recap:-
1) Downgrade to a rom that's 5.xx first
2) Then run Simunlocker.
3) Then reflash to your current rom or Dutty's.
4) Might be wise to make a note of the radio version you are using as well and then reflash this again.
Good luck.
Click to expand...
Click to collapse
HEY THX for your fast reply!
do you still have a link where i can download?
If you have it on your HD, would be nice if can upload it to me...
but... iam really happy to hear that someone had same prob
techceptional said:
So to recap:-
1) Downgrade to a rom that's 5.xx first
2) Then run Simunlocker.
3) Then reflash to your current rom or Dutty's.
4) Might be wise to make a note of the radio version you are using as well and then reflash this again.
Good luck.
Click to expand...
Click to collapse
There is no such thing as a WM5 rom for the Kaiser. Your only choice is 6.0 or 6.1.
OK, I'm wrong on the 5x version (i'm a bit of a newbie). To clarify this I flashed Alex's rom to fix the problem (6.0). Quote from Simunlocker:-
Note for WM6.1 users
================
Do not try this on 6.1! You will need to downgrade to 6.0
Farmer Joe - here's the link to the thread - http://forum.xda-developers.com/showthread.php?t=354583
You will need to search for Alex's Flash rom - ver .52 ultraclean (this worked for me). Then run simunlocker, then run Dutty's rom if you want, then flash a later radio rom for better battery life (I'm using 1.64.08.21...)
How do we setup a WIKI for Orange users then? Any ideas - new to me sorry.
techceptional said:
OK, I'm wrong on the 5x version (i'm a bit of a newbie). To clarify this I flashed Alex's rom to fix the problem (6.0). Quote from Simunlocker:-
Note for WM6.1 users
================
Do not try this on 6.1! You will need to downgrade to 6.0
Farmer Joe - here's the link to the thread - http://forum.xda-developers.com/showthread.php?t=354583
You will need to search for Alex's Flash rom - ver .52 ultraclean (this worked for me). Then run simunlocker, then run Dutty's rom if you want, then flash a later radio rom for better battery life (I'm using 1.64.08.21...)
How do we setup a WIKI for Orange users then? Any ideas - new to me sorry.
Click to expand...
Click to collapse
Everythink works fine now!
To all people with same prob... download Alex's v4 UltraClean and MultiMedia ROMs for AT&T and HTC
then flash the Radio ROM 1.0 from Step 1...
Jehaw! My Kaiser is unlocked!
Thanks everybody for your help and thanks to jotach for his great work!
keep up your good work!
Glad you got it sorted! Enjoy your unlocked Kaiser
NotATreoFan said:
There is no such thing as a WM5 rom for the Kaiser. Your only choice is 6.0 or 6.1.
Click to expand...
Click to collapse
Actually he is correct. I assume he's talking 5.0 CE Version, which indeed the standard WM6.0 Roms are. WM6.1 is CE OS 5.2.
That is the embeded CE version that WM is based upon.
CE 5.0 or 5.1 = WM6.0
< CE 5.2 = WM6.1
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.
Hi,
I've successfully installed WM6 on my Cingular 8125. I installed the Crossbow version. Great stuff.
What wonder me is, some of my network stuff is still there in the menu (GetGood, ClearView PDF reader, etc) even though the apps are not there anymore. Try to dig the forum but can't find the way to remove them...
Any tip on removing those? My phone is Cingular but I'm on T-Mobile network now.
Thanks,
um.. which rom did u install there is about 10 wm6 roms now..
jacob-mda said:
um.. which rom did u install there is about 10 wm6 roms now..
Click to expand...
Click to collapse
I installed the Crossbow version with the extended ROM.
tempoct said:
I installed the Crossbow version with the extended ROM.
Click to expand...
Click to collapse
You don't have to be so explicit
I agree! My psychic advisor Miss Cleo got busted so's I have no way of knowing your device info ie IPL/SPL, GSM, OS ... catch my drift?
Everytime I've seen this happen it's been that the device isn't CID unlocked... everytime.
ah... pardon NOOB!
OS 5.2.318 (Build 15341.4.0.01)
ROM version: 2.18.0.0 WWE
ROM date: 2/14/06
Radio Version: 02.61.11
Protocol Version: 4.1.13.28
ExtROM version: 2.25.11.102
IPL/SPL: 2.25.0001
All downloaded and followed instruction in this thread;
http://forum.xda-developers.com/showthread.php?t=298967
Any recommendation? More info needed?
anyone?????
No way to get rid of Cingular bloatware??
OK, First I would redo everything (unlocking, etc) as per DrPuttingham above. If you really successfully flashed a custom rom, its unlikely the extended rom would have the Cingular stuff still there. If you are stubborn, and just want to get rid of the Cingular stuff, do a hard reset, and when you get the message saying 3 seconds to customize, do a soft reset before it starts (put the stylus in the reset hole). Then the extended rom will not load.
Good luck,
Re: Extended rom
OK, I want to amend what I said above. I checked my extended rom today and found that indeed the X-plore rom flash had *not* wiped the previous (T-Mobile 3.3 German) extended rom. So, I apologize. It appears to be at least more common than I thought. I have now gone back and done a hard-reset and soft-reset to remove the customizations from the T-Mobile 3.3 rom (which I actually hadn't noticed).
Thanks for teaching me about this. I'll be more careful in my own flashing from now on!
Regards,
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.
Firstly, I'd like to thank Dutty and all the beta testing People for this great ROM.
I have the Radio 1.27.12.32 in my phone and in Duttys thread is the info to use the Radio 1.58.26.20 or 1.64.06.04 or 1.64.08.21.
I want to install it but on 99% the Phone tilt.
What is my mistake?
the stepts I do:
1.) copy Jumpspl1.56.exe to my document
2.) start Jumpspl1.56.exe on PDA
3.) disconnect the USB and connect the usb-cabel
4.) Start on my "XP PC" the //KAIS_Radinly_1.58.26.20_CustomRUU / customru.exe
5.) at 99% the PDA tilt
6.) hardreset
7.) connect to usb
8.) Kill Wcescomm.exe or disable Activ Sync connection to USB
9.) Start mtty.exe
10.) Connect the Port:USB
11.) local echo YES
12.) CMD> boot
13.) Enter
14.) install dutty´s 6.1 Rom again
15.) install Radio version --> it tilt at 99%
THX for help
Thomas
my suggestion is to flash an official rom to it basicley go backwards then when it flashes successflly then flash duttys rom!
I have exactly the same issue with exactly the same radio. I CAN flash duttys ROM but the radio always hangs at 99%.
I have found however that I can use duttys ROM on 1.27.12.32 - but I do get some strange 'slow down' behaviour.
I'm using an o2 XDA stellar and have never been able to successfully flash a radio, however, cooked ROMS work fine!!!
So add me to the list of ppl wanting help!
Alex
I found the solution
It is very easy
in the thread http://forum.xda-developers.com/showthread.php?t=349375 is the solution
summery
download flash-hardSPL
1.) copy Jumpspl1.56.exe to mydocument
2.) start Jumpspl1.56.exe on PDA
3.) disconnect the USB and connect the usb-cabel
4.) start from PC the flash-hardspl/custom.ru
you flash a new version "Jumpspl XXX" to the PDA
Now you can flash all Version from Dutty or Radio or XXX without start the Jumpspl1.56 on your PDA!!!
If you install a Radio Version wait at 99% for ca. 1 Minute and the build go to 100%
Thomas
Battery life not so great with Dutty's rom
Has anyone experience Battery life issues with Dutty's rom? I had tried his rom and my battery was drained within 7 hours I tried a DCS ROm and I would get 13 hours. Not sure if I have something enabled in his rom that is eating the battery.
I do not enable GPS, Bluetooth or WIFI. I love his ROM but the battery life has been an issue.
PostDeals said:
Has anyone experience Battery life issues with Dutty's rom? I had tried his rom and my battery was drained within 7 hours I tried a DCS ROm and I would get 13 hours. Not sure if I have something enabled in his rom that is eating the battery.
I do not enable GPS, Bluetooth or WIFI. I love his ROM but the battery life has been an issue.
Click to expand...
Click to collapse
Change to a different 6.1 radio. Trust me.
alutke said:
I have exactly the same issue with exactly the same radio. I CAN flash duttys ROM but the radio always hangs at 99%.
I have found however that I can use duttys ROM on 1.27.12.32 - but I do get some strange 'slow down' behaviour.
I'm using an o2 XDA stellar and have never been able to successfully flash a radio, however, cooked ROMS work fine!!!
So add me to the list of ppl wanting help!
Alex
Click to expand...
Click to collapse
ive had similar problems. The only solution ive found is, from an OEM rom, first do the radio flash, then immediately flash to Duttys (impressive) rom.
Ariel_S said:
ive had similar problems. The only solution ive found is, from an OEM rom, first do the radio flash, then immediately flash to Duttys (impressive) rom.
Click to expand...
Click to collapse
Hey Ariel_S
look at post #4, it is the Solution
Thomas_Germany_Hamburg said:
Hey Ariel_S
look at post #4, it is the Solution
Click to expand...
Click to collapse
all I've ever done was hard-SPL my TyTN II and have not any problem with flashing Radios or ROM ..etc
I have no idea why you have to go through the route of needing the "Jumpspl" thingy !!!
also .. you can specifically pinpoint a referred post instead of just the thread .... your "solution in post #4" only point to the radio thread ... there are 33 pages there ... too much reading !!!
just mouse over the specific/solution post and copy its link location instead
for example ... this is your post #4 pinpointed !!
http://forum.xda-developers.com/showpost.php?p=1933195&postcount=4
UnicornKaz said:
all I've ever done was hard-SPL my TyTN II and have not any problem with flashing Radios or ROM ..etc
I have no idea why you have to go through the route of needing the "Jumpspl" thingy !!!
also .. you can specifically pinpoint a referred post instead of just the thread .... your "solution in post #4" only point to the radio thread ... there are 33 pages there ... too much reading !!!
just mouse over the specific/solution post and copy its link location instead
for example ... this is your post #4 pinpointed !!
http://forum.xda-developers.com/showpost.php?p=1933195&postcount=4
Click to expand...
Click to collapse
same here, hardspl one time and im sure ive flashed over 50 times. Radios, splash screens, roms. No problem. Never used jumpspl one time.
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..