Related
Hi guys
I know this has been asked a million times before, but trust me, I've tried following the tutorials posted her but with no luck.
So here goes:
I've tried flashing this ROM:
http://rapidshare.com/files/24185105/ruu_vario_aku3.3_3822_382120_026911_tmo_de_ger_ship.zip
via awizard but it stopped so I've unplugged it, got it into bootloader mode and flashed with the xplore WM6 ROM but it just hangs at the boot up screen after restarting.
G3 device
IPL 3.08
SP 3.08
GS 0.269.11
OS 3.8.2.2
Any ideas?
sav_za said:
Hi guys
I know this has been asked a million times before, but trust me, I've tried following the tutorials posted her but with no luck.
So here goes:
I've tried flashing this ROM:
http://rapidshare.com/files/24185105/ruu_vario_aku3.3_3822_382120_026911_tmo_de_ger_ship.zip
via awizard but it stopped so I've unplugged it, got it into bootloader mode and flashed with the xplore WM6 ROM but it just hangs at the boot up screen after restarting.
G3 device
IPL 3.08
SP 3.08
GS 0.269.11
OS 3.8.2.2
Any ideas?
Click to expand...
Click to collapse
Was your wizard CID unlocked ?
I see that you have OS 3.8.2.2 , that is not my OS. It should have been 10.2.0.8.
That means your wizard might have been locked.
Very strange.
I did run CID-unlock first. It was running xplore before I tried flashing the tmobile rom, so maybe the images didn't get flashed.
Anything I can do to fix it?
Okay, I'm busy trying to flash the wizard_love rom. Been sitting at 96% for a while lets hope it goes further.
Okay, the upgrade went through. OS2.26
XDS-dev tutorials and the love rom for the win! Now I can relax again...
Will flash to WM6 soon.
sav_za said:
Okay, the upgrade went through. OS2.26
XDS-dev tutorials and the love rom for the win! Now I can relax again...
Will flash to WM6 soon.
Click to expand...
Click to collapse
Heh. So now that you have found the tutorials helpful, perhaps you'd consider changing the thread title?
--M
Sorry about that, have changed it.
For some reason I can't get it back to WM6 but will try again and keep you guys posted. Device is definitely CID unlocked, but for some reason it keeps hanging at the boot screen.
OKay, assuming my wizard got CID-locked for some reason, how do I downgrade to ver1 to unlock it again?
I've downloaded button's ver1.05 rom. Can I just install it, or will it give me an error saying I need a newer ROM?
Sorry for all the questions, I just don't want to take any chances.
sav_za said:
OKay, assuming my wizard got CID-locked for some reason, how do I downgrade to ver1 to unlock it again?
I've downloaded button's ver1.05 rom. Can I just install it, or will it give me an error saying I need a newer ROM?
Sorry for all the questions, I just don't want to take any chances.
Click to expand...
Click to collapse
Luke....use the Force... Follow the steps in the tutorial link (in my sig.) but the short answer is "yes".
--M
Hehe, thanks I've done that. Will try tomorrow, thanks.
I feel like a bit of a plonker asking so many questions with such obvious answers.
Okay, after a LOT of trial & error I've finally gotten it back to WM6. Here's what I did:
1)Downgraded to IPL/SPL 1.01 using button's ROM
2)CID unlocked using lokiwiz
3)Upgraded to mr_clean AKU2.3
4)Upgraded to Faria's WM6
I didn't use aWizard as usual, just the rom upgrade utilities that came with these ROMS.
Hope this helps anyone that's struggling with the same problems I've been having.
Thanks for the tutorials, they've been a great help. The only part that didn't work for me was upgrading to T-mobile's 2.26 because it would freeze on the bootup screen after upgrading to WM6. Replace that step with mr_clean 2.3 and it works fine.
hey how did you get your wizard_love rom to get past 96% without crashing? mine just gives me error 302, which is ERROR [302~318] : UPDATE ERROR
any clue? thanks
mapleman321 said:
hey how did you get your wizard_love rom to get past 96% without crashing? mine just gives me error 302, which is ? ERROR [302~318] : UPDATE ERROR
any clue? thanks
Click to expand...
Click to collapse
Hi
I got the phone into bootloader mode then it worked fine. It got stuck at 94% iirc but I just left it until it finished.
Hope this helps
Yup, first time disaster. I followed the guide here, installed the necessary Cert_SPCS.cab/EnableRapi.cab files, rebooted, and then started the Shelltool update...only to belatedly notice a notification screen on my 8125 asking if I wanted to run one of the programs.
I said yes, but even though the update completed, my 8125 is stuck at the boot screen.
Worse, I reset the 8125 into boot loader mode and tried to flash back, only to get a 300 error. I tried to use an updated RUU and ROM set, only to get 264 or 274 errors.
Any hope here, or did I just manage to brick my 8125?
Are you trying to flash an offical rom while in bootloader mode?
Yup. Tried to flash the official 8125 ROM from HTC. Tried to flash a number of different ROMs, actually - I always get a 264 or 274 "Communication" error, except for the official ROMs, which gave me a 300 error.
Not looking good here...
this has helped me with bad flashes
http://forum.xda-developers.com/showthread.php?t=298613
Been there, done that. In fact, that was the thread I first read. I've tried to flash to Wizard_love, but I get a 264 error.
From what I've read in the RUU Docs, a 264/274 error is rare, and fatal in this case. It's not looking good...
(On the bright side, the iPhone release has created a flood of used 8125's on eBay )
I did a little searching for you,
http://www.google.com/advanced_search?q=+site:http://forum.xda-developers.com&hl=en&lr=&as_qdr=all
I read some were how to flash a phone that has errors, I couldn't find that post. Maybe someone else here knows of that post You didn't mention is your phone G3 or G4 I did find this post, doesn't look good. I hope someone has a better answer for you, good luck.
http://forum.xda-developers.com/showthread.php?t=304456
Another post I found for you.
http://forum.xda-developers.com/showthread.php?t=294107
Thanks for the links, unfortunately it's still a no-joy situation here.
This is a G4 Cingular 8125 - sorry I forgot to mention that earlier.
ActiveSync was set to allow USB connections, and I've tried using the official RUU update utility from HTC for the Cingular 8125 with the 8125 in Bootloader (3 color) mode - I get an error 274.
I then tried the Wizard_Love version - error 264.
Next, the MB WM6 ROM - error 300.
Finally, in desperation I try the Shelltool app method again, even though I can't copy over the necessary bootloaders. It hangs up mid-flash, as expected.
Can't go forward, can't go back. Looks like I've got myself a brick...sigh...
upd: ahh, it is g4.....
so ignore whats below
it IS NOT brick ,trust me i had exactly same prob while testing cooked ROM - all yyou need is to download chinese rescue ROM, THEN flash it by its RUU, then RUU wLOVE, then flash ..anythin(g3)...and then flash IPLSPL, as it will be unequal, usually.
its unclear, why RUU cant do flash sometimes, but i believe, that you do not have brick( i had same situation 3 times = 14 flashes..;/ but machine is alive !)
of course, you may have same errors with chinese..if connecting, reconnecting etc is not working, then...use any rescue ROM closest to original, old hogs. check your firewall, and remember - SR device before EACH try - oterwise you surely will have 300 error - 1 try for each reset, no more.
chinese rescue ROM(you MUST flash wlove after that 1), or shelltool will lead you to...3bars.;/
http://pda.oleyek.com/ROM/Others/RUU_Prodigy_1070302_103_10703102_CMCC_CHS_Ship.exe
if its not working...maybe that 1..
http://rapidshare.com/files/29657481/RUU_TMobile_US_226102_22610105_022511_WWE_Ship_tmob_rom.exe
maybe other...
wizard love rescue ROM:
http://rapidshare.com/files/8651097/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar
Just a "happy ending" update:
Was just about to buy a new 8125 on eBay, when I gave it another try - hard reset the device twice in a row, then tried again to flash back to the original Cingular 8125 ROM -- it worked!
Then, in a fit of flashing madness, I went ahead and flashed one of Faria's latest WM6 sets -- and it worked as well!
So, not only don't I have brick, I actually got it upgraded. Whew...
pls help for flashing rom
pr0naLd said:
this has helped me with bad flashes
http://forum.xda-developers.com/showthread.php?t=298613
Click to expand...
Click to collapse
I have spent 24 hrs flashing my qtek 9100 sim free - i think it is the g4 as IPL IS 2.17 / SPL 2.17 NO ZEROES THOUGH . IT DOES SYNC BEYOND 99% AND THE HELP WINDOWS COMES OUT - IT GOES BACK TO THE BOOTLOADER SCREEN ( 3 - 4 LINES OF RED BLUE GREEN ). PLS HELP AS I AM DYING TO GET THE WM 6.0 ONTO MY WIZARD. thanks and appreciate.
[email protected]
BOWERS said:
I have spent 24 hrs flashing my qtek 9100 sim free - i think it is the g4 as IPL IS 2.17 / SPL 2.17 NO ZEROES THOUGH . IT DOES SYNC BEYOND 99% AND THE HELP WINDOWS COMES OUT - IT GOES BACK TO THE BOOTLOADER SCREEN ( 3 - 4 LINES OF RED BLUE GREEN ). PLS HELP AS I AM DYING TO GET THE WM 6.0 ONTO MY WIZARD. thanks and appreciate.
[email protected]
Click to expand...
Click to collapse
Kindly confirm its a G3 or G4 before flashing. This will help you out. http://forum.xda-developers.com/showthread.php?t=298613
wizard G4 boot ok but jump to B/L screen
its aliveeee its aliveeeeeeeeee
Hi everyone,
I think I may have bricked my Kaiser. I've been following some similar threads but nothing seems to be working to fix the problem.
I was going through the process to flash a new Rom, starting with installing HardSPL following this thread I was. I was having problems, I think because I have the 1.82 ROM version.
Finally, I thought I had HardSPL installed, so I continued to run KaiserCustomRUU.exe. This completed (jumped from 0% to 100%) very quickly. However, I reset my phone and it is now stuck in the tri-color bootloader screen
The screen has the says:
KAIS130
SPL-1.82.0000
CPLD-8
and has the letters RUUNBH in the top right corner.
I've tried removing the battery and resetting, but the phone always goes back to this screen. I've also tried running mtty, but without success. The command 'readconfig' returned a result 'Command error !!!'.
does anyone know of anything else I can try?
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
If your at the tri-color screen, just reflash a new rom
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
If that goes through ok, then do the same to flash another ROM.
Again no expert at unbricking but its definately worth a try
japher said:
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
Click to expand...
Click to collapse
Try this.
1.) Open ActiveSync and navigate to File > Connection Settings - Uncheck Allow USB connections.
2.) Download this ROM http://rapidshare.com/files/5781641...dio_sign_22.45.88.07_1.27.12.11_Ship.rar.html and flash it to your device.
That should work for you.
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
japher said:
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
Click to expand...
Click to collapse
I had this problem about 2 weeks ago.
I was flashing one of Dutty's Great ROMs and I lost power at the house and shut down my computer when I was 46% done.
I had the same RUUNBH in the top right hand corner. All I did to fix this was flash a factory shipped ROM like the one I provided to you and it worked great. No issue thus far.
Honestly I can't gurantee 100% if this will totally fix your problem but I am 95% sure.
Unless some other users have an answer for you I think this will be your best solution. Regardless of what you do you will have to flash to a new ROM anyways.
Also, I'm a bit dubious on whether i will be able to flash to that ROM. I don't think I have the right HardSPL installed to flash roms (see what my boot-loader screen says in the first post).
I'm no expert though.... obviously
Thanks for all the info alltheway. I'm too tired now (will probably f*ck the thing up even further! ), so I'll try flashing this tomorrow.
Here's some more info I've collected using mtty (my phone is an O2 XDA Stellar):
Code:
Cmd>info 2
HTCSO2___001¯JG±HTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1300O__0HTCE
New Thread
Read this:
http://forum.xda-developers.com/showthread.php?t=355910
Hi tqm. I've been following that post but as far as I can tell there is no solution there yet.
From what I can tell from that thread (and others), the only way stop the phone booting to the tri-color screen (in RUUNBH mode) is to flash with a ROM that matches the vendor. I think because I haven't been able to install HardSPL properly, my phone's version of SSPL will only load O2 ROMs (could be wrong here, but that's the picture I'm building ). Unfortunately no-one seems to have extracted the ROM from an XDA Stellar :\
I believe alltheway's solution above worked for him because he had HardSPL installed properly. He could load the stock ROM to fix the phone, because his SSPL version allowed different ROMs to be loaded. I'm not certain of this, and I'll probably try his suggested solution when I get home today... but I'm not too confident.
If only there was an mtty command to just get the phone out of 'RUUNBH' mode. I've seen the command 'task 8' mentioned on here, but it doesn't work when I try it. Does anyone know of a list of mtty commands for the Kaiser anywhere?
Definitely flash the original ROM, it will get your device to the default HTC shipped state.
Then sync phone with ActiveSync, install HardSPL again and then flash custom ROM.
I remember i had the same issue but the original rom is a lifesaver
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
japher said:
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
Click to expand...
Click to collapse
IMHO the HTC stock ROM should work even without HardSPL, at least for me it worked fine... but just for sure have your O2 stock ROM by hand.
jaso2005 said:
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
Click to expand...
Click to collapse
I don't thinks there's a way to flash HardSPL on tri-color scrren so far, coz activesync cannot connected to computer
the best way is trying to find the phone's offcial ship rom to flash
No luck trying to flash with the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
After getting to 1%, it reports an error:
Error [294] : Invalid Vender Id
As suspected, looks like this will only accept an O2 ROM Will have to wait until one is available.
Did you try installing HardSPL and then reflashing?
the stock HTC rom will not load onto your kaiser simply because it is still CID locked to O2's CID code. You HAVE to find the O2 rom that your device came with or any O2 ROM and reflash that and you will be good to go. You may also try and flash HardSPL but I dont think its going to work. But remember have a friend or someone on the forum dump and rebuild the O2 rom for you and just reflash the OS.nb or ROM only no radio!
It is very simple to dump and rebuild a rom so if you have a friend that has a kaiser have him over for an hour and dump his
thats your only shot at this point.
URPREY said:
Did you try installing HardSPL and then reflashing?
Click to expand...
Click to collapse
My current ROM version is 1.82. I don't think installing HardSPL has been solved for this ROM version, which I think is where all my problems started. I have tried, but no version of HardSPL (that I've found) will install correctly.
austinsnyc said:
You HAVE to find the O2 rom that your device came with or any O2 ROM... just reflash the OS.nb or ROM only no radio!
Click to expand...
Click to collapse
Thanks for the reply austinsnyc, this is what I'm hoping to do now, I'm watching this thread 'Has anyone dumped the o2 Stellar rom yet ?' closely Maybe I should reconstruct the ROM myself, I'm just a bit worried about arsing that up as well I'd rather someone experienced reconstructed and verified the ROM (on a phone that isn't already messed up).
Out of interest, would you be able to give me a succinct explanation of what is actually wrong with my phone at present? As far as I can tell, the only problem is that the boot-loader is stuck in RUUNBH mode. Has part of the ROM on the phone actually been destroyed?
I'm assuming right now that the point of flashing the O2 ROM is just to make the phone 'finish' a flash and get out of RUUNBH mode. Or is it actually to re-instate something that has been lost?
If it is to reinstate something that's at present lost, is this data definitely part of the os.nb?
If it's just to get the boot-loader out of RUUNBH mode, I'm REALLY gutted that there isn't just a mtty command to do this
Oh yeah, and perceptivepixel.com Ace!
first of all sorry for y English...
Ive been read the threads about that, but ive this problem:
i ve a hardspl 3.29 and trying to downgrade to original rom the flashing process stops at 15%.
i can install only custom rom and so i cant reverting back to original rom and spl.
ive been tried to flash first the spl but not working...
someone can help me please?
thx!!
wow, I don't think I've ever haleard it this way before. Usually you can't upgrade to a cooked ROM, not the other way around.
So, you get no errors while installing a cooked ROM, but it stops at 15% when trying to downgrade...
I know that some shipped ROMs flash the SPL at 15%, so this must be the problem.
Undortunately, I am a lucky one who has never had anything bad happen to me while flashing (besides my laptop running out of battery), so I don't really have much advice to give you, but I'm sure somebody else will.
Sorry, hope it all goes well for you
HardSPL prevents itself from being replaced. You need to run JumpSPL or SSPL-KAIS on the phone when it is running WM as normal, which will switch you to triciolor screen, where you can flash the original SPL.
This should be detailed in the "How to revert to factory state" page in the wiki.
thx but ive been done all and now my kaiser it's brick on bootloader:
dont allow to flash hard spl
dont allow to flash custom rom
dont allow to flsh original rom
Help PLease!!!!!!!
tried with mtty but nothing...USB PORT CAN NOT OPEN
Try that sticky thread? http://forum.xda-developers.com/showthread.php?t=423486
kilrah said:
Try that sticky thread? http://forum.xda-developers.com/showthread.php?t=423486
Click to expand...
Click to collapse
tried but no chance...
my suggestion is to search this forum for "stuck in bootloader"
you're sure to find something there
mbarvian said:
my suggestion is to search this forum for "stuck in bootloader"
you're sure to find something there
Click to expand...
Click to collapse
now...
solved the stuck problem on bootloaderwith mtty for Vista, but with hardspl it's impossible to flash an original rom on the device (flsh stops at 15% error 226-flash error- wath is?)
so...i want to flash an original rom: waht can i do? help needed please...thx!!!
always prpblem in falshing original update...flashing process stops at 15%. ive downgraded at wm6 with spl 3.07.
ERROR 226
I was trying to follow the many different ways to unlock, Hard SPL, and flash a new ROM but this is just way over my head. I think I may have screwed up my phone. I've been reading for 4 hours and I'm just throughly confused (this was so much easier on th Artemis!). I downloaded the jumpSPL1.56-KAS, ran it from the phone (not the storage card). Then I ran Kaiser-HardSPL-3.56 and that seemed to work fine. Then I tried to run step 1 of the KaiserUnlocker and now it will only show me the AT&T boot screen and nothing else after that. What did I do wrong?
I'm trying to unlock the phone so I can use it on T-Mobile USA and flash a new ROM. I've flashed ROMS before but I just never realized how involved this process was on other devices.
And yes, I can get to the boot loader screen.
shawndh said:
I was trying to follow the many different ways to unlock, Hard SPL, and flash a new ROM but this is just way over my head. I think I may have screwed up my phone. I've been reading for 4 hours and I'm just throughly confused (this was so much easier on th Artemis!). I downloaded the jumpSPL1.56-KAS, ran it from the phone (not the storage card). Then I ran Kaiser-HardSPL-3.56 and that seemed to work fine. Then I tried to run step 1 of the KaiserUnlocker and now it will only show me the AT&T boot screen and nothing else after that. What did I do wrong?
I'm trying to unlock the phone so I can use it on T-Mobile USA and flash a new ROM. I've flashed ROMS before but I just never realized how involved this process was on other devices.
And yes, I can get to the boot loader screen.
Click to expand...
Click to collapse
Ick...this sounds like one of a couple of things...either you really screwed it up (btw, even "really screwed up" has been known to be fixable thanks to the super awesome folks here on XDA Devs) or it's a simple fix. My first suggestion would be to put it back into bootloader (just hold the usualy bootloader buttons and stick the stylus up in the Reset hole OR take the batter out and put it back in, your choice I think) and try rerunning everything EXCEPT the KasierUnlocker (btw, dont quote me but I would almost swear KaiserUnlocker needed a special radio flashed in order to properly work...you may wanna head back to that thread and check it out. I unlocked mine with it and I can about guarantee I had a special radio...) and see if it fixes anything OR find a compatible radio and reflash it (well, first off...get it into bootloader and tell us what the bootloader says on it)
Anyways, first things first would be to see what the bootloader is showing and then work from there. Sounds like a little bug so don't freak out too bad. If you think flashing these babies are hard then you really didnt try flashing G4 versions of the Wizard =P I totally bricked one because it was the pesky G4s and I didn't realize it at the time (complete newbness lol) So yeah, Kaiser's are a LOVELY change for me =] I've flashed mine countless times and loved it since the moment I got it! =D
But yeah, gimme info! =]
Did you use WM6.1 or WM6.0 to unlock the phone? Put in boot loader and flash orginal WM6.0 ROM as the other user suggested. You should be able to flash it if it is not a brick.
If it doesn't work you can use mtty to recover your phone, the needed information you'll find in the Kaiser Wiki.
Hope it helps
I just had this exact problem.
Use the EXE included in the tutorial to flash any windows 6.1 ROM from the bootloader via USB, and you will boot again.
HTCOmega said:
Ick...this sounds like one of a couple of things...either you really screwed it up (btw, even "really screwed up" has been known to be fixable thanks to the super awesome folks here on XDA Devs) or it's a simple fix. My first suggestion would be to put it back into bootloader (just hold the usualy bootloader buttons and stick the stylus up in the Reset hole OR take the batter out and put it back in, your choice I think) and try rerunning everything EXCEPT the KasierUnlocker (btw, dont quote me but I would almost swear KaiserUnlocker needed a special radio flashed in order to properly work...you may wanna head back to that thread and check it out. I unlocked mine with it and I can about guarantee I had a special radio...) and see if it fixes anything OR find a compatible radio and reflash it (well, first off...get it into bootloader and tell us what the bootloader says on it)
Anyways, first things first would be to see what the bootloader is showing and then work from there. Sounds like a little bug so don't freak out too bad. If you think flashing these babies are hard then you really didnt try flashing G4 versions of the Wizard =P I totally bricked one because it was the pesky G4s and I didn't realize it at the time (complete newbness lol) So yeah, Kaiser's are a LOVELY change for me =] I've flashed mine countless times and loved it since the moment I got it! =D
But yeah, gimme info! =]
Click to expand...
Click to collapse
I know. The crazy thing is that I've successfully flashed a G3 and a G4 Wizard and I still find this confusing.
When I go to the boot loader screen I have:
KAIS1*0
SPL-3.56.Hard
CPLD-8
When I reset the device normally I get:
R 1.27.12.11
G 22.45.88.07H
D 1.62.00.00
I didn't try to flash any other ROMS to unlock it. I just went with the hard SPL and then tried the Unlock tool. The phone is stock.
Thanx for the replys. I reflashed the original ROM and now it's working again. This is what I have now:
When I go to the boot loader screen I have:
KAIS1*0
SPL-3.56.Hard
CPLD-8
Now when I reset the device normally I get:
ROM version 1.62.502.0
Radio version 1.27.14.09
Protocal version is 22.45.88.07H
Device info:
Windows Mobil 6
CE OS 5.2.1622 (Build 18128.0.4.4)
Can I go strait to a SIM unlocker and then flash a new ROM?
Well you've got HardSPL 3.56 flashed to it.
Why do you need to sim unlock it? Sim unlocking is not neccesary to flash one of the many Roms avaliable for the Kaiser/Tilt.
Once it's got HardSPL flashed, you're free to flash any type of rom onto it
shawndh said:
I was trying to follow the many different ways to unlock, Hard SPL, and flash a new ROM but this is just way over my head. I think I may have screwed up my phone. I've been reading for 4 hours and I'm just throughly confused (this was so much easier on th Artemis!). I downloaded the jumpSPL1.56-KAS, ran it from the phone (not the storage card). Then I ran Kaiser-HardSPL-3.56 and that seemed to work fine. Then I tried to run step 1 of the KaiserUnlocker and now it will only show me the AT&T boot screen and nothing else after that. What did I do wrong?
I'm trying to unlock the phone so I can use it on T-Mobile USA and flash a new ROM. I've flashed ROMS before but I just never realized how involved this process was on other devices.
And yes, I can get to the boot loader screen.
Click to expand...
Click to collapse
A couple of things:
1) The Kaiser-Unlocker only works on 1.xx hardspl's, so you'll have to put one of those on first.
2) You do need to install the patched radio before you run it.
3) You'll need to flash a compatible radio afterward too, or else your device might not boot all the way.
4) Next time please post these questions in the thread for the unlocker you are using. It makes it much simpler for everyone.
stuff said:
Well you've got HardSPL 3.56 flashed to it.
Why do you need to sim unlock it? Sim unlocking is not neccesary to flash one of the many Roms avaliable for the Kaiser/Tilt.
Once it's got HardSPL flashed, you're free to flash any type of rom onto it
Click to expand...
Click to collapse
But HardSPL 3.56 doesn't SIM unlock the phone from what I understand. I need to use it with T-Mobile SIM. So I need to chenge to a 1.XX Hard SPL to do this?
So I guess I went wrong with flashing 3.56 first and not 1.1
Then I need to patch the radio
Run the unlocker
rinstall the radio
Then flash the ROM
Problem I have now is that I can't seem to go back down to a lower SPL version.
shawndh said:
But HardSPL 3.56 doesn't SIM unlock the phone from what I understand. I need to use it with T-Mobile SIM. So I need to chenge to a 1.XX Hard SPL to do this?
Click to expand...
Click to collapse
You need to read the instructions carefully, and ask questions in that thread. All the experts in unlocking will be there to help you.