Related
All -
After playing with the Qtek test ROM for a while, I thought I'd "revert" to a stable release. I grabbed one of the 1.6.7 RUU files (with GR near the end) off the ftp site and installed it. When the MDA rebooted, I got a message about how I'd illegally acquired the ROM and it froze my MDA. Thank GOD that using the bootloader and another RUU installer I was able to recover it.
First, why would the ROM jack me like that? I've used aWizard previously to CID unlock my MDA? Can it relock?
Second, the "screwy" ROM would load, but fail after the customizations were applied and the soft reset occurred. Is there any key combo you can hold down to prevent the Wizard from executing the customizations script? Thanks!!!
After you do a hard reset it runs through the 'welcome to windows' blurb where you learn to cut'n'past and align the screen etc..... At the end of this process is then says 'press the screen to start using this device' (or something like that, after which, there is a 3 seconds delay before it starts running the customisation CAB files. If you press the reset button (soft reset) within this 3 second period is resets the device without running all the customisation rubbish.
I hope this helps and good luck!
Muchas gracias!
Okay, I have searched the forums, to no avail. I also no longer have the .bin files generated when I first ran lokiwiz, they were accidentally deleted by another individual who rebuilt a box before I had a chance to pull them off.
So basically, I am screwed, every command I try with lokiwiz or awizard results in the following errors
ps, I am trying to restore the original 8125 image, I have a functioning device, but I want to restore it.
...
CopyFileToTFFS(cidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occurred.
result=80072746
[19:15:05.84] Your phone is now CID unlocked....
Store the generated 'lock_backup.bin' file in a safe place. It can help to resto
re your device if anything goes wrong.
* Press [Enter] to continue
I'm having the same issue on a unit with the K-JAM_WWE_216901_2169101_020710_ship ROM....
I'm having the same issue on a unit with the K-JAM_WWE_216901_2169101_020710_ship ROM too.
lot's of people have that problem, whit that specific rom :S
me too, but there does not seem to be a solution yet...
for te topicstarter: flas another rom on your device and lokiwizard will work again
lokiwizard refuses to work, even after flashing the latest imate rom to it (although I am using the imate rom installer application), I guess I could try the ruu tool ..... ??
flash back to t-mobile rom, unlock it an flash back again to imate
I have no problems flashing to the imate rom, thats what I am running at the moment. Using the imate rom, I cannot run awizard or lokiwizard.
Johannus said:
flash back to t-mobile rom, unlock it an flash back again to imate
Click to expand...
Click to collapse
Is that possible?
From what I gathered, if you flash it to the iMate rom, the Extended rom portion becomes locked to the iMate Extended rom. You can't even reflash it back. Until someone comes out with a version of the full iMate rom with an unlocked Extended, or breaks up the iMate rom into GSM, OS, and Extended and you do it manually, I think it is impossible.
Or I could be totally wrong.
fuzzycuffs said:
I think it is impossible.
Or I could be totally wrong.
Click to expand...
Click to collapse
i think you are... cause i did it myself
and for the topicstarer: i know you cant use awizard nor lokiwiz, but if you flash your original T-mobile rom back, just like i did, then use awizard or lokiwiz to unlock the SIM and the CID. and after that flash the imate rom on your device again, your problem will also be solved!
Johannus said:
fuzzycuffs said:
I think it is impossible.
Or I could be totally wrong.
Click to expand...
Click to collapse
i think you are... cause i did it myself
and for the topicstarer: i know you cant use awizard nor lokiwiz, but if you flash your original T-mobile rom back, just like i did, then use awizard or lokiwiz to unlock the SIM and the CID. and after that flash the imate rom on your device again, your problem will also be solved!
Click to expand...
Click to collapse
Alright, then answer me this:
Can you take the iMate full rom, do that flash, and just then flash the TMO extended rom on top of that, so upon a hard reset it'll have the iMate GSM and OS roms, but then go through the stock TMO Extended rom updates (one of which will kill wifi)?
If so, that answers my question of going back to "bone stock." That's my concern with flashing to the iMate rom: 1) having a locked extended rom that I may or may not be able to revert back from, and 2) being able to go back to how the phone looked coming out of the box.
fuzzycuffs said:
Johannus said:
fuzzycuffs said:
I think it is impossible.
Or I could be totally wrong.
Click to expand...
Click to collapse
i think you are... cause i did it myself
and for the topicstarer: i know you cant use awizard nor lokiwiz, but if you flash your original T-mobile rom back, just like i did, then use awizard or lokiwiz to unlock the SIM and the CID. and after that flash the imate rom on your device again, your problem will also be solved!
Click to expand...
Click to collapse
Alright, then answer me this:
Can you take the iMate full rom, do that flash, and just then flash the TMO extended rom on top of that, so upon a hard reset it'll have the iMate GSM and OS roms, but then go through the stock TMO Extended rom updates (one of which will kill wifi)?
Click to expand...
Click to collapse
No, but you (1) don't have to and (2) DON'T WANT TO, as some of the T-Mobile CABs will kill things in the new release AND they're inferior anyway (the connection button is one of them!)
In fact, unless you want the OZIm client and the "SMS email triggers" you need to load only TWO of the T-Mo US CABs on top of the Imate ROM (by hand) to get full functionality. No problems with this approach at all (of course you don't get the T-Mo pukie home screen this way, but I don't want it anyway!)
I posted in one of the other threads where you asked this how to accomplish it.
If so, that answers my question of going back to "bone stock." That's my concern with flashing to the iMate rom: 1) having a locked extended rom that I may or may not be able to revert back from, and 2) being able to go back to how the phone looked coming out of the box.
Click to expand...
Click to collapse
Going back to how the phone looked out of the box is easy if you have an SD image of the original T-Mobile ROM and an SD card. No problem with that at all - as I've noted here repeatedly I have TESTED this and it works fine.
So let me get this straight, to get past the locked extended rom imate creates, I need to flash to tmobile to be able to flash bac the original cingular rom? Ah well, guess I gan stay with the imate rom till cingular releases an official rom release
Hey Guys....
I am still working on this DIY but this is how I was able to accomplish reverting back to my OEM Cingular 8125 state.
If someone could plase let me know how to replace the very first SPLASH Screen from "HTC" to CINGULAR, I would greatly appreciate it.
By following the steps below, you will have almost everything back to its original state.
Be sure to download all the necessary ROM files: OS ROM, Radio ROM, splash.bin
Place your OS ROM and Radio ROM inside the c:\sWizard\ROM folder.
DOWNGRADE YOUR OS AND RADIO ROM
1. Download aWizard 1.3b Beta Version (Attached File or Latest Version) from the following link: http://forum.xda-developers.com/viewtopic.php?t=37386&highlight=awizard
2. Unzip the folder to your root directory (C:\aWizard or D:\aWizard). You need to avoid having spaces your directory name. This is the reason placing folder in the root.
3. Make sure you have an active connection via Active Sync.
4. Run the aWizard.cmd file from C:\aWizard
5. Run "e" command FIRST !
6. Run "u" command. Your Wizard will reboot.
7. Run "w" command to update your ROM. You will get a prompt to choose your ROM. If you did not place a valid ROM inside the ROM folder, then you wont see it from this list. Also, if you placed your aWizard in other directory with spaces (i.e C:\ MY DOCUMENT) then you wont see it either. Just let it run. It will take close to 20 minutes. At the end, it will as you to hard reset.
8. Run "r" command to update your Radio ROM. Same as Step 7.
Replacing Splash Screen (Back to Cingular)
1. Place the splash.bin file inside the c:\aWizard\lib
2. Open up CMD and navigate to c:\aWizard\lib
3. Type in the following command "pdocwrite.exe -n 1 splash.bin 0x002d0000"
pdocwrite.exe = this program is located inside the LIB folder
splash.bin is a file that I converted.
4. Once completed, please reset your Wizard and now you will have Cingular's Splash (2nd Splash)
Updating the EXT ROM
1. I did this manually by utilizing Active Sync to copy over all the Cingular ROMs to the Wizard and running it individually.
2. Reset and you will now have all the programs Wizard came with.
FAQ
Q. My Wizard is stuck on a splash screen and it wont do anything.
1. Hard reset your Wizard
2. Hold onto Camera Button while turning on the Wizard and you will get the boot screen.
3. Plug in your USB Cable
4. Run one of the known ROM files with .exe extention. When this happened to me while downgrading,
I had to reload the latest iMate ROM.
5. Start the downgrade process again by following the above instruction.
reverting back to original cingular rom
Thank you for this.
Don't you have to REINSTALL original Cingular Rom or does this do that by removing imate updated ROM?
js
Re: reverting back to original cingular rom
urologyhealth said:
Thank you for this.
Don't you have to REINSTALL original Cingular Rom or does this do that by removing imate updated ROM?
js
Click to expand...
Click to collapse
When you install Cingular ROM, it will remove/overwrite the existing iMate ROM.
Be sure to place your ROM files in the the ROM folder.
If your running the aku2 imate rom, many people will have problems running awizard or lokiwiz to unlock the CID, I had to run the tmo uk rom update (.exe one) which replaced the imate, and then restore the rom files I had backed up for cingular, although the extended rom is still locked, thats annoying.
jvanbrecht said:
If your running the aku2 imate rom, many people will have problems running awizard or lokiwiz to unlock the CID, I had to run the tmo uk rom update (.exe one) which replaced the imate, and then restore the rom files I had backed up for cingular, although the extended rom is still locked, thats annoying.
Click to expand...
Click to collapse
can you please share how you change the very first splash screen on your 8125 ? its the only thing i wasnt able to do or know how to do.
thanks
FarSeide, I'm pretty sure that even the stock 8125's from Cingular showed the HTC screen first, the cingular screen second, and finally the Windows Mobile screen. If that's the case, then your 8125 is as good as new as far as Cingular is concerned.
Also, if anyone upgraded to the AKU2 I-mate ROM, you cannot do the process you described, because (as someone else mentioned) the lokiwiz program will not work. What you need to do is FIRST install a different ROM using an exe file (a good example would be the leaked AKU2 Q-Tek ROM exe file), and only after that entire upgrade process is completed, can you now use lokiwiz to unlock the SuperCID and install the Cingular ROM.
kingbear2 said:
FarSeide, I'm pretty sure that even the stock 8125's from Cingular showed the HTC screen first, the cingular screen second, and finally the Windows Mobile screen. If that's the case, then your 8125 is as good as new as far as Cingular is concerned.
Also, if anyone upgraded to the AKU2 I-mate ROM, you cannot do the process you described, because (as someone else mentioned) the lokiwiz program will not work. What you need to do is FIRST install a different ROM using an exe file (a good example would be the leaked AKU2 Q-Tek ROM exe file), and only after that entire upgrade process is completed, can you now use lokiwiz to unlock the SuperCID and install the Cingular ROM.
Click to expand...
Click to collapse
Eli,
thank you for the info. I wanted to put this together because when I tired to do this, there were information but scattered all over all forums. just wanted to help others so that they dont go through the same thing i did.
i was following these instructions and i got a
NOTIFICATION ERROR
cannot execute repllog.exe
so what i had to do was hard reset, boot screen , re-installed imate, ...
i guess i will try it again, what do you guys think
hmmm... sorry to say but my 8125 only ever showed the cingular splash. No HTC, no WinMob. I had assumed that Cingular somehow replaced all 3 splash screen with theirs.... In fact, I never even knew there was more than one splash screen until I upgraded to the Qtek rom.
I'm in trouble
I tried to downgrade the ROM and now I'm hung in the i-Mate SPLASH SCREEN. I tried the hard reset and it hangs every time. I can't get a connection through active sync obviously so what are my options. How can I get a working device.
I'm freaking out.
Please HELP!!!!!!!!!!!!!
Re: I'm in trouble
hellomoto_25 said:
I tried to downgrade the ROM and now I'm hung in the i-Mate SPLASH SCREEN. I tried the hard reset and it hangs every time. I can't get a connection through active sync obviously so what are my options. How can I get a working device.
I'm freaking out.
Please HELP!!!!!!!!!!!!!
Click to expand...
Click to collapse
relax... i was exactly where you were...
first, hard reset your device.
Hold the Com Manager, Voice Command and press the soft reset with your stylus.
before you turn the device back on, hold the camera button then turn on the power. you will receive the boot screen. Plug in your USB Cable and kick off the EXE file. Load one of the known ROMS like the iMate ROM.
reload and try again. I am willing to bet that you disconnected the USB Cable while updating to Cingular ROM.
Good luck and dont worry.
does anyone have the exe for the original Cingular ROM ?
my colleague tried to update his 8125 with my imate rom.....and did not unlock it first.
all he has is the bootloader now, the update gives the well known Error: Invalid Vender ID
Any help is greatly appreciated
Thanks !!
Get a copy of the proper ROM on a SD card, and reload it that way.
This is the easiest way out of that box......
Thanks,
but how to get the Rom reloaded from the SD card onto the device using the bootloader ?
dirty_harry said:
Thanks,
but how to get the Rom reloaded from the SD card onto the device using the bootloader ?
Click to expand...
Click to collapse
THAT part is easy.
Note that the SD card image is NOT a file. You have to raw write it onto the card, which will destroy the filesystem - so back up the card first! psdwrite will do the job. You also need the image (PREVIOUSLY copied from a SD-made backup with "psdREAD")
To restore it, insert the card, hold the CAMERA button, and power on. The phone will tell you to press VOICE to restore the SD image (it looks to see if there's a valid one in there)
Note that with 1.x bootloaders this will happen with the BACKLIGHT OFF, and you only have 3 seconds or so to press the key - so have a flashlight handy. 2.x bootloaders turn the backlight ON.
Hit VOICE. The image will be verified (checksummed) and if it is good, it will be loaded.
That's it. Takes about 2-3 minutes. When it finishes it will tell you to press any key, and when you do you'll end up at the tricolor screen.
Power off and back on, and the phone will cold boot the new image.
This will work even if you can't run an RUU loader, so long as you can get that first prompt up. It is a VERY effective rescue method.
IMHO before you hack on the firmware in these things you should make an SD card backup just for this reason.
Which tools is best option for ROM backup to Mini SD?
Hi,
Just read your message about writing ROM to Mini SD card.
I'd like to do just that.
I want one or two ROM's for safekeeping stored somewhere instead only a backup or official copy on my pc.
As i've read restoring from SD is safer and faster..
I don't intend to use the SD card for anything more than just that.
In the Prodigy Service Manual (Prodigy Service Manual -XA(0813-2005).pdf) HTC uses mtty.exe. There are also instructions in the PDF.
Since HTC uses this, it should do exactly what i want, i guess?
Or is there a better tool?
Thanks,
Allegro.
P.S: Will a restored ROM from Mini-SD look fresh to HTC?
Or will they see it's a self restored copy instead of a official HTC restore?
Will it reset "everything"?
I was able to fully restore CIngular 8125 ROM, EXTROM, All Splash Images using the SD Restore.
100 Cingular OEM Spec has been restored...
I hv updated T Mo custom ROM..but now can't downgrade even by Awizard utils....can any one throw some light on this?
ok...i got the error from upgrading from 2.17 hacked rom to the 2.26 official rom. tried to read whatever i can but looks like solutions were given for cingular ipl etc...
can someone help me out? when i run the official rom, it updates to 1% and then i get the nbf error. i tried to run loki but mda not recognized by my usb connection.
stuck now...please help!!!
actually, tried to run machinagod's RAPI unlocker..but MDA not recognized as connected...this was part of xelencin's 2.24 rom updater.
please help!!!
Hi,
you must provide more information if you want someone to help you.
First and most important: what does it mean your phone is stuck? Stuck where? Does the screen come on? Can you get the bootloader screen? (for the bootloader screen: hold the two keys on the right side of the device and press shortly the reset hole; if you see the three colors screen then you have the bootloader!)
bye
i get the screen with the 3 colors, and usb at bottom left. when i run the official t-mobile 2.26 update, the screen goes gray and there is a bar with % done. when that kicks in, i get 1% done then it stops. on my computer screen, i get the nbk error, saying the nbk file that i have is not for my phone.
i looked for fixes but all the fixes require activesync connections which i am unable to connect with. just fyi, when i plug in the usb cable to my laptop, i hear the *ding* for usb noting it is connected but the activesync connection is not available.
thanks in advance for your help.
-mike
m3m3 said:
i get the screen with the 3 colors, and usb at bottom left. when i run the official t-mobile 2.26 update, the screen goes gray and there is a bar with % done. when that kicks in, i get 1% done then it stops. on my computer screen, i get the nbk error, saying the nbk file that i have is not for my phone.
i looked for fixes but all the fixes require activesync connections which i am unable to connect with. just fyi, when i plug in the usb cable to my laptop, i hear the *ding* for usb noting it is connected but the activesync connection is not available.
thanks in advance for your help.
-mike
Click to expand...
Click to collapse
Before your battery goes flat i suggest you to re-install your old rom. Don't know why 2.26 is not working, maybe you downloaded a corrupted archive. To install your old rom it is not required that activesync sees your phone. Go in bootloader mode and flash your old rom back.
i dont think i downloaded a corrupted rom file because i downloaded it from 2 different places, one from Tmobile site directly from my tmobile account.
what bootloader program should i use? please advise and location to download...
thanks,
mike
m3m3 said:
i dont think i downloaded a corrupted rom file because i downloaded it from 2 different places, one from Tmobile site directly from my tmobile account.
what bootloader program should i use? please advise and location to download...
thanks,
mike
Click to expand...
Click to collapse
bootloader program??? There's no bootloader program!
What i'm trying to tell you is:
- Your phone is stuck for unknown reasons. In this state you cannot recharge your battery!
- Before the remaining battery charge becomes too few, reinstall your old rom (the one you had before trying 2.26)
- When your phone -with the old rom- will be working again, then you'll have all the time to investigate on the causes of this failure.
- Now hurry up and install the old rom before it's too late (unless you have a second wizard that you can use to recharge the batteries)
To install the old rom you must go to the three-colors screen (the bootloader), connect to USB (but activesync won't start!) and start the rom installer.
bye
risi,
sorry...how do i get to bootloader screen? is it the tricolor screen? has anyone had the same problem that i'm having, going from 2.17 hack to 2.26 official?
what program can i use to load my original rom with?
sorry for the semi-newbie questions...desperate to revive my MDA...
again, thanks.
-mike
m3m3 said:
risi,
sorry...how do i get to bootloader screen? is it the tricolor screen? has anyone had the same problem that i'm having, going from 2.17 hack to 2.26 official?
what program can i use to load my original rom with?
sorry for the semi-newbie questions...desperate to revive my MDA...
again, thanks.
-mike
Click to expand...
Click to collapse
to go to the bootloader screen you must keep pressed the two keys on the right side of the device and, while keeping them pressed, shortly press the reset button. the bootloader screen IS the three colors screen. when you get the bootloader screen, reinstall your previous rom (2.17).
i plugged the phone in the wall charger and the battery charged up all last night so i am not worried about the battery...
i just cannot figure out how to load the old rom i had.
i didnt bring the phone with me to work...i will try to reflash with old rom...for now...i am using my old hp 6315 (yikes! - remember the probs with this phone?? lol
m3m3 said:
i plugged the phone in the wall charger and the battery charged up all last night so i am not worried about the battery...
i just cannot figure out how to load the old rom i had.
Click to expand...
Click to collapse
to load the old rom you must:
- get to the bootloader screen (the three colors one)
- download the 2.17 rom's ,exe archive (download it from the same place you took it last time)
- connect the phone to USB (don't worry if activesync doesn't see it)
- start the rom .exe file
thanks risi...
hope i can get it back man...
m3m3 said:
thanks risi...
hope i can get it back man...
Click to expand...
Click to collapse
I hope so! About the problem you had with 2.26, i don't know why it happened. Is your phone a T-mob USA MDA? If it is not then you must CID unlock it before flashing a different operator's rom.
Bye
yes, it is a tmo usa mda...or i would think so since i bought it from a factory store (not an authorized dealer). anyway man...i will keep you posted...for now, using my trusty hp 6315. lol
Hello,
I have a similar problem. I updated my QTEK 9100
with a T- Mobile 2.24 ROM. Now I need to go back to the original QTEK Rom, namely RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe, but after starting the upgrade process the program refuses to downgrade the device and says get a newer nbf file.
Is there a way to force a downgrade?
Many thanks in advance
Anais said:
Hello,
I have a similar problem. I updated my QTEK 9100
with a T- Mobile 2.24 ROM. Now I need to go back to the original QTEK Rom, namely RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe, but after starting the upgrade process the program refuses to downgrade the device and says get a newer nbf file.
Is there a way to force a downgrade?
Many thanks in advance
Click to expand...
Click to collapse
Is your phone CID unlocked? If so, then you must download the wizard_upgrade_noid tool from the ftp server and use it to install the 'down'grade.
In details:
- be sure your phone has been CID unlocked (and is not a G4)
- download the wizard_upgrade_noid (i don't remember the name exactly) tool
- use winrar to extract the original qtek rom .exe archive
- copy the noid tool to the folder where you extracted the qtek rom
- run it
bye
Hello Risidoro,
At first thanks for your fast answer. Since I have a QTEK I don't beleve it's CID locked. How can I verify if the phone is CID locked? Is there a tool to check this?
I proceeded exactly as you advised. I used Winrar to extract the files and used the Wizard_RomUpgradeUtility_noid I downloaded from the ftp site.
Then I copied the nk.nbf file to the respective folder but the utility after having completed the initial 2 screens says:
ERROR [238] : FILE READ
The update utility cannot open the requested file. Please check your update utility.....
any ideas
Greetings
Hello,
Just some small updates: My phone has currently the Mr Clean 2.3 firmware loaded : IPL 2.24 SPL 2.24 GSM 02.25.11 and OS 2.24.10.1.
Previously I was using RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe and had no problems. After upgrading to xelencin t-mobile based US rom I had trouble when making data transfers over GPRS. Then I decided to test Mr clean. Altough I data transmission has improved a bit it's still not so good as with my original RUU 2.17 release.
Unfortunately I am unable to revert to this version. Also having tried to downgrade using Faria's Custom downngrade file only the IPL was downgraded to 1.05 and the SPL file stayed to 2.24.
I tried then to reapply RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe but I recieved the error message UPGRADE only.
Since apparently this is unstable I decided to reapply Mr Clean and now I have again IPL 2.24 SPL 2.24 GSM 02.25.11 and OS 2.24.10.1.
I suspect that the data problems are due to the fact that these new radio versions are not compatible with our provider. I live in Luxembourg so we use LUXGSM.
Is there a way how I can revert to my old 2.17 software.
Any coments are highly appreciated.
Greetings
Anais said:
Hello Risidoro,
At first thanks for your fast answer. Since I have a QTEK I don't beleve it's CID locked. How can I verify if the phone is CID locked? Is there a tool to check this?
I proceeded exactly as you advised. I used Winrar to extract the files and used the Wizard_RomUpgradeUtility_noid I downloaded from the ftp site.
Then I copied the nk.nbf file to the respective folder but the utility after having completed the initial 2 screens says:
ERROR [238] : FILE READ
The update utility cannot open the requested file. Please check your update utility.....
any ideas
Greetings
Click to expand...
Click to collapse
Hi Anais,
try flashing with the RUU (Rom Upgrade Utility) tools that you find in this thread: http://forum.xda-developers.com/viewtopic.php?t=56088
Download the archive RUU.rar and extract its content somewhere in your PC. Copy in the same location the nk.nbf from the rom and run the .exe.
bye
Hey
I upgraded my phone from a molski rom to the wm6 rom and now it is stuck in the start/splash screen with MOLSKIs splash.
I done what was told in another thread but still nothing working( Mini SD Method).
Does anybody have any other ideas?
I can get to the bootloader but that about it.
NB: Its a G3 Device and it is CID Unlocked
Is the anyway to load a rom on a memory card and install it from bootloader
You could try flashing back to the rom that your device came shipped with aka your carriers rom.
Yeh, Doesnt seem to work.
I get the error 260 in RUU.
Maybe the Wizard Love Rom will work, but I can seem to get the rapidshare link to work.
Reboot your pc. Then kill off wcescomm.exe from task manager. Then disable any firewalls and remove your minisd card from your device. This may stop the errors. Try flashing your carriers rom again.
If the error msg is still there then report back here and I will find you a working link to wizard love.
Exact same message, Error 260.
I did try to do the Mini SD card method early, everything went smooth. It said completed and when I restarted the device, nothing had changed.
IPL/SPL 2.26, but my OS Version is : 6.00
The Splash Screen Im getting is from my old Rom, Molskis AKU 3.2
Know a place that I can get the Love rom From. I have searched everywhere.
Wizard Love is located here and here.
peter petrelli said:
Wizard Love is located here and here.
Click to expand...
Click to collapse
Download session invalid.
Cant seem to get anything from Rapidshare
Yass3r, I think you performed CID unlocking while IPL is 2.26...
Look at the sticky in the forum, get the Button's 1.05 ROM, flash it so IPL and SPL is downgraded to 1.01, then CID unlock your wizard again.
Hey
I cant seem to get anything from Rapidshare, maybe my ISP blocks it. Is there anywhere else that I can get those specific Roms from?