I like many on here am suffering the bad reception after the sim unlock.
If I run Oli's software right through to Hard-SPL, patch radio and unlock can I then add the Murata radio ROM and the Hard-SPL-V2 SPL to a Custom ROM im making.
So my custom ROM will consist of a OS (custom WM6) a GSM (Murata) and a SPL (Hard-SPL-V2) but leave the SPLASH blank will my Polaris then be still SIM unlocked and Hard-SPL'd everytime I hard reset or load a new OS?
Also can I use any radio ROM after the Unlocker to be SIM unlocked or does it have to be the patched one or Murata.
Thanks
Don't need to flash the spl again only one time and that's definitif for the rest of your polaris life.
Yes you can install a rom and after flash a different radio rom without probleme.
You can change the splashscreen if the rom flash have change it by reflashing only the splashscreen with udK tools.
You can use any radio you want.
So the SIM unlock and Hard-SPL will remain no matter how many times I update the radio or os?
Great. Thanks for your reply
Related
I just cooked up and loaded a ROM.
Rom 4.00.11 eng
Radio version 6.18.00
During the selection process, I chose sim unlock as one of the wanted features however it did not unlock and now asks for SID cose when I insert forieng sim card. I have even tried to download XDAunlock but it gives me an error message that it cannot find unlcok code?
What's the solution?
Unlock Tool didn´t work with WM2003.
Cook a Rom with 3.17.03 unlock your phone and then upgrade to WM2003.
Unlock-Tool requires the wireless Modem, that is not included in the WM2003
Regards
Stefan
Can I downgrade rom from 4.00 to 3.17?
Anything special to know?
I would suggest you backup your original rom using sd method before embarking on any flashing of the device.
Nah, just flash the phone at will: just remember that you need an SD-card to load anything else once you've had 4.00.10 or 4.00.16 (both T-Mobile ROMs).
I did as X recomended. Flashed to 3.17, unlocked, then flashed to 4.00
It was a breeze. Thanks for the great work. The Kitchen is awesome.
Hi
My o2 xda mini s - used to hang @ start up soft and hard reset dint work out for me so i tried flashing my handset by this process given by MR Vippie http://forum.xda-developers.com/showthread.php?t=298613
the complaint is still same and now the handset versions is something like this
IPL 1.01
SPL 1.05
GSM 01.12.10
OS 1.5.4.2
pls help
If you did the unlocking that it looks like you were trying to do, then now you have to flash back to an official ROM like T-Mobile 2.26 to get your IPL/SPL back to the same version.
i haven't personally done this version of unlocking, but the common advice is that IPL and SPL should be the same number. if they aren't you should keep reflashing the button rom until they are both 1.05...then CID and flash back to a 2.xx rom. it doesn't hurt to reflash the buttons...1.01 and 1.05 doesn't look right...
ok thankyou for ur precious suggestion i will try flashing with this versions
Another odd thing. When I flashed my wizard I first flashed it back to 1.05 to unlock it. I then flashed it forward to I think the T-Mo 2.26 which was then new. I had to do this second flash twice because the first time it only got the bootloader. From the instructions I had read, though, it appears this is normal or at least not uncommon?
invalid vender id
this update utility cannot be used for your pda phone. please check your update utility
this is the error i get when i flash it with t-mobile 2.26 any other version or some kind of hardware damage
did you go through the unlocking process enablerapi, etc? sounds like you might not have CID unlocked, so it won't let you flash a rom from a different carrier. (in this case, I'm assuming you have cingular). when you flash with buttons 1.05 and both ipl/spl are the same, then go through the unlock process again.
ok sir
will try ur process n post results
I'd also bet that the CID unlocking didn't go through but i don't think it's a big deal having two different bootloader parts as long as the major version is the same. eg: 1.01 / 1.05 or 2.17 / 2.26 (i must try it one of these days)
What happens a lot these days is broken phones due to different major versions. And although nobody took the time to make a study i'd bet that it's a downgrade protection issue from latest bootloaders
cheers
PS:
sorry for the off-topic
Hello,
I used Step I nivid to downgrade to wm5 before I upgraded to wm6 from kamalneet, link to this post http://forum.xda-developers.com/showthread.php?t=349603
But I have some major problem with the rom, when I now want to donwgrade back to the official WM5 from my provider O2 it always says that the nbf file is to old and i have to get a newer one.
This problem only occured after I used "nivid wm5" in kamalneet's post for downgrading.
I can downgraded with different "Step1" Roms posed in this forum but not with the original one as it was possible before!
And also after downgrading with one of these roms the error message keeps the same!
Is there any way that I can get my original O2 rom back?
Thanks!!
search for HardSPL and flash it! after that your SPL Version will be: 2.4G.4PDA THEN!!! you can downgrade to ANY SPL. just flash latest o2 ROM and you will be back at SPL 2.20.0001 again!
i've tried it already it REALLY works!!!
i just flashed back to my dopod original rom.
Original rom is still the best.
here is the link
http://forum.xda-developers.com/showthread.php?t=350033
Whoops... i was wrong.. now corrected - SoftSPL!!!
evil$knevil said:
Hello,
[...] I have some major problem with the rom, when I now want to donwgrade back to the official WM5 from my provider O2 it always says that the nbf file is to old and i have to get a newer one.
[...] Is there any way that I can get my original O2 rom back?
Thanks!!
Click to expand...
Click to collapse
Yep, just as nForce said:
You can use HardSPL.
But if you want to set it all back to the old-fashioned original-values you have to go through an even looooonger way (have done it by myself) - you have to go down to IPL 2.10 or lower to have your device back to IPL 2.15 from original O2 ROM, otherwise it remains 2.20 or higher *caugh* -
but then it's back to original in every aspect.
You have to go into SoftSPL (that whitescreen), then from WIKI back to IPL 2.10 (see wiki), followed by going back into SoftSPL and with whitescreen to SPL 2.15 or lower. After that you can take the nbf from the O2-Upgrade-File and flash with the ROMUpdateUtility_NV_G4.exe from Upgrade_Package.zip.
Just take the nk.nbf from the original O2 Firmware (after starting somewhere in %TEMP% or by extracting setup-file), then put it in "Upgrade Utility" flash it and boot will say:
O2-Screen
IPL 2.15.0001
SPL 2.15.0001
GSM 02.19.21
OS (don'tknowexactly)
regardless of which version you ever have had flashed onto your device before.
Happy flashing.
offtopic: what are these I/SPL 3.0something versions for? Just for preventing going to other ROMs?
Not HardSPL but SoftSPL
whoops... it's even easier than that.
regardless of IPL and SPL-Version just follow the steps to get into SoftSPL (the White-screen) WITHOUT flashing HardSPL
Then do the firmware-update from O2 (the O2-shipped-one) and everything should work fine. (after this procedure your phone should look like a virgin, with no HardSPL, with CID-Lock (if not unlocked before), original ROM and ExtROM)
keinenplandavon said:
whoops... it's even easier than that.
regardless of IPL and SPL-Version just follow the steps to get into SoftSPL (the White-screen) WITHOUT flashing HardSPL
Then do the firmware-update from O2 (the O2-shipped-one) and everything should work fine. (after this procedure your phone should look like a virgin, with no HardSPL, with CID-Lock (if not unlocked before), original ROM and ExtROM)
Click to expand...
Click to collapse
Thats how I made it and it has worked perfectly!
Thanks for all your help!!!
so I've created a kitchen for a new windows build (21890), by copying the old kitchen, and adding the new windows build into the copied kitchen. Everything got processed correctly, no conflict of older builds or whatsoever, as the kitchen says the rom is generated correctly.
Then I use the custom ruu to flash the rom, and after 100%, I got a message that the image is corrupted. I rebuild & flash a few times, and it's the same.
So I took the rom, flash it via sd card, and it works! And I thought it could be the cable problem, so I use another cable, on another usb port, and this time round it works. However, subsequent regeneration & flash of the rom fails again. so it's not about the cable/port, something is amiss here.
so enough of long story, what could be the possible reason?? I have been cooking & flashing my own roms w/o problem for the last few weeks except today. So it can't be my notebook problem (which is running on win7 64bit)
anybody? I tried flashing an older rom, w/o problem.
just the new one that I've added the latest build of winmo. No problem flashing from sd card, just not able to flash via usb.
did you install the reliability update for win7 x64 the other day?
ive had issues with using sspl since, sometimes enterbootloader doesnt enter bootloader..
on my win 7 x32 machine at work i have no issues
as i use the 202 spl i tend to use sspl to flash my own roms..
fards said:
did you install the reliability update for win7 x64 the other day?
ive had issues with using sspl since, sometimes enterbootloader doesnt enter bootloader..
on my win 7 x32 machine at work i have no issues
as i use the 202 spl i tend to use sspl to flash my own roms..
Click to expand...
Click to collapse
what's reliability update? I checked the updates that happened in the last 2 days, it's just update for MS security essential and windows defender, nothing else.
I suspect it could be the kitchen problem, as I cooked my rom together with radio. Somehow, I moved the source radio nb file, and it appeared to have caused the problem despite me updating the path of the source radio. I disable the radio, cook it, ok. Re-add back the radio, cook it, ok again.
hopefully it stays that way.
BTW, I tried spl 2.00, I can't flash any cook rom ,so those folks who said spl 2.00 is a supercid spl is wrong. I suppose you are able to flash custom rom with spl 2.00 because of sspl? do you need goldcard for sspl, or it can be done like HD?
I'm using the 2.00 spl also and using sspl to flash a new build rom, the OS on PC is W7/32
zenkinz said:
what's reliability update? I checked the updates that happened in the last 2 days, it's just update for MS security essential and windows defender, nothing else.
I suspect it could be the kitchen problem, as I cooked my rom together with radio. Somehow, I moved the source radio nb file, and it appeared to have caused the problem despite me updating the path of the source radio. I disable the radio, cook it, ok. Re-add back the radio, cook it, ok again.
hopefully it stays that way.
BTW, I tried spl 2.00, I can't flash any cook rom ,so those folks who said spl 2.00 is a supercid spl is wrong. I suppose you are able to flash custom rom with spl 2.00 because of sspl? do you need goldcard for sspl, or it can be done like HD?
Click to expand...
Click to collapse
teh 200 SPL is MFGR, or CID unlocked, which is region free.. or the same as having a gold card.
nothing to do with flashing custom roms, as they still need to be signed by HTC
as sparkie confirms, just use sspl to flash custom roms with it.. (as long as you run sspl while the device is booted not already in 200 bootloader mode).
fards said:
teh 200 SPL is MFGR, or CID unlocked, which is region free.. or the same as having a gold card.
nothing to do with flashing custom roms, as they still need to be signed by HTC
as sparkie confirms, just use sspl to flash custom roms with it.. (as long as you run sspl while the device is booted not already in 200 bootloader mode).
Click to expand...
Click to collapse
do I need goldcard to do sspl? Thats what I read before I plunge into hspl few weeks ago.
edit: oh so what you are saying is that the stock spl 1.42 requires gold card to achieve mfgr, whereas 2.00 spl is already mfgr so Ican just do sspl directly w/o any need for goldcard?
I flashed now several times in spl 2.00 mode, when it freezes because I made a not bootable rom, I have to flash the 2.02 rom again and after that i flash again with sspl
it could be the LeoCustomRUU.exe file you have may cause the problem. Who knows? Have you tried hex compare the RUU files?
Dear All,
I decided to add the miri custom ROM. I'm on official 1.66 rom WWE with radio 2.06. I read in this forum that I have to downgrade to 1.48 in order ro be able to SPL. I downloaded the 1.48 from the thread of Leo official roms in this forum. The process stopped at 1% telling me "Invalid vendor". then I restarted my device but the GSM network is not working.
Please help how could I go back to 1.48 to SPL my device.
i want to hard spl but my spl is 1.66.0000
how to hard spl ??
You need the ROM that originally came with your HD2, flash it using the SD card method and then you can put HSPL on the device
EddyOS said:
You need the ROM that originally came with your HD2, flash it using the SD card method and then you can put HSPL on the device
Click to expand...
Click to collapse
That will only help if the original spl on the stock rom is 1.42.0000, which with a 1.66 based rom I'm guessing not. HSPL currently only works if the spl is 1.42.0000 and in cases where it isn't you need to either upgade or downgrade to 1.42 first.
i can not flash by memory card but i have error vender id
in goldcard i have problem too, this is vender id error
is any hspl for spl 1.66.0000 ? ?
Edit !!
i can update my rom to energy by sspl but it still in HTC bootscreen
i need hard spl
please help
(
helppppppppp
Who is your provider? you need the 1.48 ROM from your provider to flash back to SPL 1.42 via SD card. If your phone isn't vendor locked (although it sounds like it is) then you can get the 1.48 ROM for your region from HTC direct
Might be a lesson to be learned here to read everything fully before attempting anything
i have 1.48 rom and test SD card method but i have vender id error
Try another one of these 1.48 roms to see if perhaps any one of them work
http://www.4shared.com/dir/22189940/b8552fa0/Shipped_Leo_ROMs.html
As has been stated by EddyOS you can't always just flash to any stock 1.48 rom, you need to try to get a 1.48 based rom for your operator and that is why you are getting the invalid vendor problem. I luckily did not have a problem and I see some other users are saying that the Goldcard method also no longer works. I can't comment on that, but you may want to try that option out.
a question
for ugprade to 1.66 i need goldcard ?
because gold card is worked by active sync but my device in still in htc boot screen
You need to get a 1.48 ROM for your region/vendor and flash using the sd card method, nothing else will get you back to SPL 1.42 so don't bother trying.
If you don't understand then you shouldn't have flashed in the first place
ok. i tested 1.48 and 1.61 rom by sd method but see Not Allowed error.
i will download 1.66 and test it
thanks a lot
Are you getting the 1.48 ROM that is from your region/vendor?
lovely_az_2003 said:
ok. i tested 1.48 and 1.61 rom by sd method but see Not Allowed error.
i will download 1.66 and test it
thanks a lot
Click to expand...
Click to collapse
seems you are just flashing any old rom. You need to find one that is specific to your provider (voafone, o2, tmobile, whatever) otherwise you will continue to get invalid vendor.
i live in iran
i dont know my vendor
i upgrade another leo by this 1.61 rom but this device ...
i unlucky...