Related
Are there any downsides to downgrading to bootloader v1.04?
Does v1.06 have anything extra that v1.04 doesn't?
I have an X01HT (v1.06)
Is it possible that future ROM upgrades could be tied to the bootloader version?
Thanks
tle said:
Are there any downsides to downgrading to bootloader v1.04?
Click to expand...
Click to collapse
Bootloader 1.06 enforces CID checking, bootloader 1.04 doesn't.
Bootloader 1.06 doesn't have 'rtask' command, bootloader 1.04 does.
rtask command allows you to do some "interesting" things, for example enter radio bootloader, and GSM AT command interface, where you can type AT commands to the phone from bootloader. Read the wiki Hermes bootloader page for more info.
tle said:
Does v1.06 have anything extra that v1.04 doesn't? I have an X01HT (v1.06)
Click to expand...
Click to collapse
No, it has less things... rtask command removed
The "extra" thing is that your CID is checked when flashing a ROM, so you can't flash ROMs that are made for other Hermes devices such as HTC TyTN or Cingular 8525 on your X01HT.
tle said:
Is it possible that future ROM upgrades could be tied to the bootloader version?
Click to expand...
Click to collapse
it is possible, but unlikely to happen, shouldn't worry you too much now.
Thanks for the quick reply, pof.
I guess that if a ROM were to be tied to bootloader v1.06 then someone would have to make a bootloader only upgrade... Do you foresee and potential issues there. (excluding copyright issues?
Thanks
tle said:
I guess that if a ROM were to be tied to bootloader v1.06 then someone would have to make a bootloader only upgrade... Do you foresee and potential issues there. (excluding copyright issues?
Click to expand...
Click to collapse
No issues at all, and no "bootloader only upgrade" needed... if you are on 1.04 you just have to flash any ROM containing bootloader 1.06 to have bootloader 1.06 on your device. Then you could do the 'tied-to-1.06' upgrade.
But at the moment 1.06 and 1.04 are very similar, the only difference I've noticed is 'rtask' command and CID checking. rtask command also allows you to go radio bootloader and flash the 'extracted radio rom upgrades' (using rwdata), so you can't do a radio-only upgrade in 1.06 at the moment.
Anyway... I am investigating the way to provide an alternative method to go from 1.06 to 1.04 without copyright issues (as with the previous method from imei-check). Now I can jump from WinCE to IPL at physical address 0x0000000 and then the IPL reads the SPL from flash and executes it correctly.
The next step is to load the nb file for SPL 1.04 and place it in RAM at 0x3000000, and instead of jumping to IPL jump to SPL when this is done it will be possible to downgrade the bootlodaer for those of you on 1.06
Sounds like you are close to a solution. I read in a another thread that you said you are not a WINCE programmer, but you seems like you have a good grasp of low level programming. Best of luck!
I'm getting a lot of help from some friends, i wouldn't have reached this without their help, and I like to learn new things
What we're doing is modifying gnuharet to remove the linux-loading part and add very few changes in the ARM9 assembly part, if you're interested see the file src/wince/asmstuff.S.
pof said:
rtask command allows you to do some "interesting" things, for example enter radio bootloader, and GSM AT command interface, where you can type AT commands to the phone from bootloader.
Click to expand...
Click to collapse
I guess it should be possible to do in wince by directly calling a rilgsm ioctl
(should work on universal, the equivalent code runs the phone in Linux).
devspecific code=54
http://wiki.xda-developers.com/index.php?pagename=rilgsm.dll
cr2, yes it is possible... this is what my unlocker does to do the [email protected] commands and uses almost the same code as buzz used on the universal.
EDIT: I read you too fast, I'm using RIL_DevSpecific commands to send the [email protected], but didn't read the code=54. Have to try this, thanks for pointing it out!
Help Needed!
Hi pof,
I (stupid guy!) upgraded from ME_DT_WWE_1182553_106_10303_Ship to Cingular 1.34.502.1 (1.06) and now I cannot downgrade (using for example Cingular_1.30.502.1 (1.04)...why?
I tried every unlocking process, every step you write here, but no way! Always ID ERROR (294)...whyyy????
I cannot understand...I think a downgrade to 1.04 could save me...
Please, help me...
Yes, downgrade will help you. Just downgrade to a full rom matching the CID on your device, or wait until a free solution to downgrade bootloader.
pof said:
Yes, downgrade will help you. Just downgrade to a full rom matching the CID on your device, or wait until a free solution to downgrade bootloader.
Click to expand...
Click to collapse
Just to be sure: I flashed my Dutch TyTn (QTEK_E11) to Cing 1.34 WWE (CWS_001).
Now my CID still is QTEK_E11 or is it changed to CWS_001?
If is still is QTEK_E11 then I can go back to the Dutch HTC 1.18.254.2, can I?
And from there I can SuperCID my device?
Ok...first and foremost, I don't consider myself a technical idiot, but I feel like one at the moment...I'm sure that my problem will end up being something simple, but I just can not figure this out.
I can not delete the files in my ExtendedROM folder. Using Resco Explorer, I keep getting "The media is write protected" error message.
Phone - Cingular 8525
I paid for and ran the the SuperCID unlock from that "imei.uk" company back in early January.
I've installed the Fit4Cat software to unlock in the security page. I've tried both versions that are out there. - That doesn't work.
I've tried POF's Hermes_MountAllExtrom.cab file - That doesn't work.
I've check the Registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\Drivers\MSYSEXT
and it shows the correct unlocked numbers, but this still does not allow me to delete the ROM files.
About a month ago, I was able to delete the files and I installed several various cooked ROMs and then I downloaded an earlier version of the Cingular ROM that had the 1.04 bootloader.
Since then, the ROM has been locked, unable to be manually changed.
I have since reflashed with the new Vanilla WM6 - which looks really good by the way...and then reflashed the original Cingular 1.34 ROM from the HTC.com web page.
After this last flashing, I again, installed all of the Unlocking/unhiding cab files that I had, in an effort to unlock and delete the files located in the ExtendedROM folder. But, I still am not able to do it.
My goal is to delete the files located in my ExtendedROM folder, so I can insert my own collection of ROM parts and reflash the way I want it. I know there are other ways to do this, but this is the way I prefer, and honestly, I'm curious now to find out why it is behaving this way.
Any ideas would be very much appreciated, cause I'm stumped.
Thanks,
EdinAthens,GA
If your device is not SuperCID, you can only see files on extrom (unhide) but not ad/delete or modify them (unlock).
Make your device SuperCID first, then your problem is solved.
Hola pof,
He wrote that he ran the imei cid unlock.
Regards and thanks for your work here!
Ben
Super CID...
Pof / Ben...
Thanks for the info. Pof - I found your CID unlocker and ran it and that fixed my problem. I've sent a donation to express my appreciation...
What I find confusing, is the fact that it had "relocked" after I had purchased and applied the "imei-uk" code that I had bought.
I didn't think that was possible...
I did re-run the "imei-uk" unlocker at some point, is it possible that I re-locked the 8525?
-Ed
imei-check unlocker only makes the device supercid temporarily, when a new radio (or full rom containing radio) is flashed on the device SuperCID is lost.
Hello all,
I'm creating this poll to try and figure out why some of us can't unlock our Extended ROM / extrom.
By the way, I'd like to thank all the developers on this forum who contribute software for our Hermes... this thread is in no way a complaint or cut down to their software and guides. All I'm trying to do is just figure out why some of us can't unlock our Extended ROM. Do not Flame or Complain about any developer's software in this thread!!!!!
If you have questions on how to unlock your Extended Rom go to the following links:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
http://forum.xda-developers.com/showthread.php?t=283750
Here's my situation:
- I had a stock Cingular 8525 with a 1.06 bootloader and 1.34 ROM
- I then did an unlock sim and super cid and had no problems
- I then used HTweaC 2.1b to Unhide and Unlock my Extended ROM and was successful.
- I then followed Mr.Vanx's guide to upgrade to LVSW WM6
http://www.mrvanx.myzen.co.uk/hermes_guide/lvsw/
- Following the guide, I upgraded my Bootloader to Olipro HardSPL 1.40, upgraded my Radio ROM to 1.38.00.10, and then successfully installed LVSW WM6
At this point, my Extended ROM was unhidden but locked. I've read posts saying that it was because WM6 doesn't allow you to write to the Extended ROM so I assumed it was a limitation of WM6.
I then installed Black 2.0 WM6 and again, my Extended ROM was unhidden but locked.... again assuming it's a WM6 issue....
After tinkering around WM6, I decided to revert back to my Cingular stock 1.34 ROM since I was having trouble using WM6's Internet Sharing to tether my laptop to my 8525.... I find it easier using WM5's DUN since I don't have to muck around with proxy server settings on my laptop when using WM6's Internet Sharing.
Anyways, after using:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeGuide
I stripped out the OS.nb of the stock Cingular 1.34 ROM, created a new .nbh and then used ruuwrapper.exe to load the stock Cingular 1.34 ROM.
So now, I'm back at the Cingular 1.34 ROM but after using all the methods I used previously to unhide and unlock my Extended ROM, I'm only able to unhide my Extended ROM but not unlock it. I hope this is not permanent . I really liked having the additional 10MB
Anyways... I hope some of us can figure out a solution to how to unlock our Extended ROM
By the way, I did try to reformat my extended rom using this post but was unsuccessful since the Extended ROM is write protected.
http://forum.xda-developers.com/showthread.php?t=290132
For those of you who can't unlock, can you post what you tried to use to Unhide and Unlock your Extended ROM to try to find a pattern on our problem?
joel32137 said:
Hello all,
I'm creating this poll to try and figure out why some of us can't unlock our Extended ROM / extrom.
By the way, I'd like to thank all the developers on this forum who contribute software for our Hermes... this thread is in no way a complaint or cut down to their software and guides. All I'm trying to do is just figure out why some of us can't unlock our Extended ROM. Do not Flame or Complain about any developer's software in this thread!!!!!
If you have questions on how to unlock your Extended Rom go to the following links:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
http://forum.xda-developers.com/showthread.php?t=283750
Here's my situation:
- I had a stock Cingular 8525 with a 1.06 bootloader and 1.34 ROM
- I then did an unlock sim and super cid and had no problems
- I then used HTweaC 2.1b to Unhide and Unlock my Extended ROM and was successful.
- I then followed Mr.Vanx's guide to upgrade to LVSW WM6
http://www.mrvanx.myzen.co.uk/hermes_guide/lvsw/
- Following the guide, I upgraded my Bootloader to Olipro HardSPL 1.40, upgraded my Radio ROM to 1.38.00.10, and then successfully installed LVSW WM6
At this point, my Extended ROM was unhidden but locked. I've read posts saying that it was because WM6 doesn't allow you to write to the Extended ROM so I assumed it was a limitation of WM6.
I then installed Black 2.0 WM6 and again, my Extended ROM was unhidden but locked.... again assuming it's a WM6 issue....
After tinkering around WM6, I decided to revert back to my Cingular stock 1.34 ROM since I was having trouble using WM6's Internet Sharing to tether my laptop to my 8525.... I find it easier using WM5's DUN since I don't have to muck around with proxy server settings on my laptop when using WM6's Internet Sharing.
Anyways, after using:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeGuide
I stripped out the OS.nb of the stock Cingular 1.34 ROM, created a new .nbh and then used ruuwrapper.exe to load the stock Cingular 1.34 ROM.
So now, I'm back at the Cingular 1.34 ROM but after using all the methods I used previously to unhide and unlock my Extended ROM, I'm only able to unhide my Extended ROM but not unlock it. I hope this is not permanent . I really liked having the additional 10MB
Anyways... I hope some of us can figure out a solution to how to unlock our Extended ROM
By the way, I did try to reformat my extended rom using this post but was unsuccessful since the Extended ROM is write protected.
http://forum.xda-developers.com/showthread.php?t=290132
For those of you who can't unlock, can you post what you tried to use to Unhide and Unlock your Extended ROM to try to find a pattern on our problem?
Click to expand...
Click to collapse
I created a patch for the ExtROM for those who aren't SuperCID, you need the developer certificates for it to work, and it's only proven (by me) to be working under WM6, technically it should work with WM5 but we've found that WM5 could possibly have extra security that prevents the dll running, although I don't see how personally.
Hmmm ... I followed the guide except I installed the latest Oli and radio, then reflashed to Black 2.0, and then ran the SuperCID/SIM unlocker doing both.
Able to unlock the extrom and clear it no probs.
Thanks Olipro and Chachi for your input, I'll give it a whirl and hope to unlock my Extended ROM and post my results.
By the way, here's a link to Olipro's patch mentioned above:
http://forum.xda-developers.com/showthread.php?t=297085
Just read the Olipro Unlocking ExtRom method / thread from the link below, then ran the ExtROMPatcher.exe on my 8525. Patch ran successfully. After a soft reset, I couldn't see the Extended ROM partition. So, I then installed the sdkcerts.cab as well as installed the Security Configuration Manager (for the noobs: downloaded from M$ ... it's a Powertoy for WM5) and made sure Security was turned off for my 8525. I then did a soft reset..... however..... like many others from the thread below, I was unsuccessful. I have to say... Olipro was more than patient trying to help everyone in the thread
joel32137 said:
Thanks Olipro and Chachi for your input, I'll give it a whirl and hope to unlock my Extended ROM and post my results.
By the way, here's a link to Olipro's patch mentioned above:
http://forum.xda-developers.com/showthread.php?t=297085
Click to expand...
Click to collapse
joel32137 said:
Just read the Olipro Unlocking ExtRom method / thread from the link below, then ran the ExtROMPatcher.exe on my 8525. Patch ran successfully. After a soft reset, I couldn't see the Extended ROM partition. So, I then installed the sdkcerts.cab as well as installed the Security Configuration Manager (for the noobs: downloaded from M$ ... it's a Powertoy for WM5) and made sure Security was turned off for my 8525. I then did a soft reset..... however..... like many others from the thread below, I was unsuccessful. I have to say... Olipro was more than patient trying to help everyone in the thread
Click to expand...
Click to collapse
you could try renaming OEM_FLASHDRV.dll to something else (like OEM_FLASHDRV2.dll) and then changing the registry to use the new OEM driver.
currently I'm using WM6 with the patch with no problems. since you're on the WM5 ROM it might not work; but as I say, try the above suggestion and see if you get any joy.
After each ROM upgrade I run 2 files... First I run MountExtROM_v2.cab then ExtROMPatcher.exe In that order. The ExtROMPatcher resets the device and my Ext ROM is visible and I can write to it.
This has worked for every WM6 ROM and also some of the WM5 ROMS (but can't remember which except one of the Dopods).
Hi Olipro, thanks for the tip but I tried renaming OEM_FLASHDRV.dll to OEM_FLASHDRV2.dll and updated the corresponding registry key but still no luck.
Hi ach2, thanks for the tip as well but I've definitely ran MountExtROM_v2.cab and then ExtROMPatcher.exe In that order but still no luck....
What's interesting is that only 2 people are not able to unlock their Extended ROM but from reading all the posts related to this issue, it would seem there was more people encountering this problem....
joel32137 said:
Hi Olipro, thanks for the tip but I tried renaming OEM_FLASHDRV.dll to OEM_FLASHDRV2.dll and updated the corresponding registry key but still no luck.
Hi ach2, thanks for the tip as well but I've definitely ran MountExtROM_v2.cab and then ExtROMPatcher.exe In that order but still no luck....
What's interesting is that only 2 people are not able to unlock their Extended ROM but from reading all the posts related to this issue, it would seem there was more people encountering this problem....
Click to expand...
Click to collapse
you also installed the SDK certificates?
Definitely installed the SDK certificates you attached from the previous thread.
I followed everything you suggested from the previous thread.
Could I have in someway screwed up the Extended ROM partition during my WM6 flashing?
What's odd is that whenever I flash a new ROM (with an Extended ROM), the Extended ROM gets overwritten so I know it is able to be unlocked.
Olipro said:
you also installed the SDK certificates?
Click to expand...
Click to collapse
I think I figured out a solution to this problem.
I was able to unlock my Extended ROM by re-doing pof's SIM & CID Unlocker
http://forum.xda-developers.com/showthread.php?t=293665
You'll have to do the entire procedure again using the Instructions.txt
That means going through the process of copying the SSPL-HERM.exe to your Hermes and running from your Hermes. Then run the ROMUpgradeUt.exe from your computer. After the upgrade completes (around 20 min), copy the Herm_Unlock_v3.exe to your PDA and run it. That's what I did to unlock my Ext. Rom.
Please note that I did run a previous version of pof's unlocker and was successful in unlocking my Ext. Rom. It was only after I upgraded to HardSPL V5 and installed WM6 is when I lost write access to my Extended ROM. I'm still not sure if it was the install of HardSPL v5 or WM6 that locked my Extended ROM but I'm just happy it's now unlocked.
Hope this thread helps some noobs.
The seller said it is unlocked. How can I verify it?
I read CID Unlocking and Sim Unlocking. How can I confirm both.
Also, how can I tell which version of the radio?
and which version of SPL (3.5 or 1.2)?
Or is there any great tutorial I can setup for the AP4?
I am starting to get confused.
the seller probably was not lying as it is easy to do (thanks to olipro - cmonex/olinex) but if you want to check, press and hold your camera button, whilst doing that press the reset button, and tell us the details on the rainbow screen.
this will also tell you if it is SPL 1.1-1.2 or 3.5
when your done just press reset again
LOCKing is related to SPL. SPL is a part of the "bios" (just to use the PC paradign IPL and SPL are "extended bios" ), then you have the RADIO section of the rom and the OS (WMxx)
Other part of the rom are the EXTENDED ROM (where the file needed for operator customizzation during first install are stored) and splash screens (a FULL ROM means IPL,SPL, SPLASH 1, SPLASH 2, RADIO, OS, EXTENDED ROM).
This "bios" , called SPL can receive commands from RUU (Rom Update Utility, the sw used to flash the rom file). ROM info are "wrapped" in a .nbf file and the RUU, interacting with SPL with some batch commands, flash into the device memory the ROM parts (Splash are flashed in their locations, os, radio, ....) RUU opens the .nbf file, read abatch command file, and send the commands to the SPL to flash the rom sections
Now you can understand how a custom ROM is done: using a "kicken" you can prepare a .nbf file containing the data and the batch command file used by RUU to flash it in the right location of your ROM (SPL, RADIO, OS, SPLASH, or all together) SPL is a KEY part for this process.
With the stock RUU IPL and SPL some controls are done before flashing, first of all device's language and vendor ID, so called CID. If they doesn't mach with the ROM file you will have an error and RUU exits: wrong language, wrong vendor, ....
Flashing a custom SPL you avoid this check (or it sets the CID to "supercid", it means I accept every language and vendor ID)
The SIM unlock (phone working with all SIM card) needs something more complex. In the ATHENA FORUM whe have ATHENA UNLOCKER, from OLIPRO, for SIM Unlock and CID Unlock and ATHENA WRAPPER, just for CID unlock. They will update the HTC SPL to OLIPRO 1.2
Hi sergiopi,
Your post is so concise. You told us the whole theory it may take me more than a day to find. You have the potential to be a book author. Thanks anyway.
Questions:
1. How can I tell whether the sim is unlocked?
2. How can I tell whether the cid is unlocked? Or it is no harm to run the ATHENA UNLOCKER again?
3. What is the different btw SPL 3.5 and 1.2? Should I update it? I am planning to run the AP4.
Thanks again!
Did you completely miss my previous post, if you follow the simple instructions. I gave you earlier, we will be able to answer all your questions.
ice_coffee said:
Did you completely miss my previous post, if you follow the simple instructions. I gave you earlier, we will be able to answer all your questions.
Click to expand...
Click to collapse
To check if your Athena is SIM Unlocked take a SIM from your friend's phone who is in another network and put it in your Athena. If it refuses to accept the SIM then it is locked and you have to unlock it. If it accepts the SIM and lets you place a call, it is SIM unlocked and most probably CID Unlocked. To check if it is CID unlocked just do what ice_coffe says.
I didn't miss the post from ice_coffee. My Athena is still in shipping. I just want to get more info first. Besides testing with a real sim card, is there any method we can run from the machine?
alui said:
Hi sergiopi,
Your post is so concise. You told us the whole theory it may take me more than a day to find. You have the potential to be a book author. Thanks anyway.
Questions:
1. How can I tell whether the sim is unlocked?
2. How can I tell whether the cid is unlocked? Or it is no harm to run the ATHENA UNLOCKER again?
3. What is the different btw SPL 3.5 and 1.2? Should I update it? I am planning to run the AP4.
Thanks again!
Click to expand...
Click to collapse
Thanks, the post is for you and for other newbies, to help everyone to understand. This is a DEVELOPER'S forum, we like smart users!
alui said:
Hi sergiopi,
Your post is so concise. You told us the whole theory it may take me more than a day to find. You have the potential to be a book author. Thanks anyway.
Questions:
1. How can I tell whether the sim is unlocked?
2. How can I tell whether the cid is unlocked? Or it is no harm to run the ATHENA UNLOCKER again?
3. What is the different btw SPL 3.5 and 1.2? Should I update it? I am planning to run the AP4.
Thanks again!
Click to expand...
Click to collapse
Listen Alui. The question numbr 3 shows of your post shows that you are realy a noobie. So if you are still waiting for your new device, do not waste your time but start reading. If you already decided that you want to go for AP4, then did you realy read the AP4 thread from first post? I am almost sure, you didn't.
So please remember, if you do not know what you are doing then you have a big chance to convert your super device into a brick.
And once more, if you browse this forum, you can see how many threads is there, and how many post is in each thread. If you see this you should be sure that you are not the first person here who just got his new device. All your questions were answered many times here so just read and read and after a week of reading start to plan what to do next.
All,
I downloaded the original Cingular/ATT Rom, just in case, and bought Sprite and backed up my settings. I downloaded SDA_ApplicationUnlock.exe and ran it (from my PC, is this correct?). SDA_ApplicationUnlock.exe seemed to run okay, and gave me the message "SDA Successfully unlocked, Please Reboot SDA Now!". I rebooted my phone and did not notice a change (I assume I should?) I ran the Rom update for WM6.1 Standard, which opened up a DOS-looking box that stayed there forever and did not indicate it was doing anything. After just over an hour I disconnected my phone and rebooted it, no change.
My questions:
1) Do I run SDA_ApplicationUnlock.exe from my PC or from the WM phone itself?
2) Any suggestions as to what I may be doing wrong?
3) What does CID Unlock do, and do I need it?
Just to review, I have a Cingular 3125 with WM5, and I want to go to WM6.1 Standard.
Please help! Thanks!
Frank
geekzilla65
You were supposed to run Jump SPL on your phone which puts it into a special bootloader then run the update utility should run correctly. I personally prefer the MicroSD flash method myself.
Jump SPL?
icecube57 said:
You were supposed to run Jump SPL on your phone which puts it into a special bootloader then run the update utility should run correctly. I personally prefer the MicroSD flash method myself.
Click to expand...
Click to collapse
Thanks icecube57!
I know that SPL files were copied to my phone automatically when I ran Rom updater, but I don't think it ever launched. I am really confused about the CID unlock. I read one post where it says I have to do this, and another that says for Cingular Roms you don't need to.
Also, you mention the MicroSD flash method - is there a post here that explains how to do that? I would not mind trying it if you think it works better. Please help!
Frank
geekzilla65
If i dont say it someone else will. Please use the search function.
If the utility didnt automatically launch the Jump Spl program then navigate to the root of your phone using file explorer start it manually from your phone and it will put the phone into bootloader then try running the utility again. Thats how i had to do it with my phone
Thanks
icecube57 said:
If i dont say it someone else will. Please use the search function.
If the utility didnt automatically launch the Jump Spl program then navigate to the root of your phone using file explorer start it manually from your phone and it will put the phone into bootloader then try running the utility again. Thats how i had to do it with my phone
Click to expand...
Click to collapse
Okay, that's fair, thanks. Can I get an answer on one more thing? I did look in the forums, in the Wiki ,etc. on this - I am still confused on what CID unlock is. I really don't want to brick my phone. When this worked for you, was this on a Cingular 3125? Did you have to CID unlock?
Frank
geekzilla65
What you are talking about permenantly CID unlocks the phone which allows you to flash any rom. Instead of being stuck with carrier specific roms. What the JUMP SPL does is loads a specially modified bootloader that temporarily fakes the Update Utility into thinking your phone is CID unlocked that way you can flash any rom without going through that long complicated process in making it permenantly CID unlocked. I have a 3125 myself and flashes all the roms in this forum fine with the Jumps SPL Bootloader method.
MicroSD Flashing
Im feeling nice. Here is the MicroSD Flashing Method
http://forum.xda-developers.com/showthread.php?t=311232
Thanks!
icecube57 said:
What you are talking about permenantly CID unlocks the phone which allows you to flash any rom. Instead of being stuck with carrier specific roms. What the JUMP SPL does is loads a specially modified bootloader that temporarily fakes the Update Utility into thinking your phone is CID unlocked that way you can flash any rom without going through that long complicated process in making it permenantly CID unlocked. I have a 3125 myself and flashes all the roms in this forum fine with the Jumps SPL Bootloader method.
Click to expand...
Click to collapse
Thanks icecube57!!! I really appreciate the answers! You rock!
Frank
geekzilla65
Thanks!
icecube57 said:
Im feeling nice. Here is the MicroSD Flashing Method
http://forum.xda-developers.com/showthread.php?t=311232
Click to expand...
Click to collapse
Thanks for this one too! Awesome!
Frank
geekzilla65