Related
guys...still having fun trying to unlock my xda...i will get there! been advised to downgrade 6.25.02 radio down to 6.24 radio as XDA UNlock doesnt work on 25...any idea where to download?
Try this:
http://www.lumpistefan.de/tools/RSU_V6.24.20_PPC.zip
But downgrading RSU is very dangerous.....
Stefan
Thanks
Thanks S...it wouldnt let me do it.
http://www.yorch.net/downloads/ROMS/TMOradiostackupgradeR624 .zip
t-mobile RSU 6.25 SIM unlock prolbem, final solution. XDA I
Error getting connection type
Error getting unlocking code
Upgrade RSU (Radio Stack)
RSU 6.25, RSU 6.24
Those are the keywords I have been using for about a day to get to the bottom of unlocking a t-mobile XDA I (siemens SX56).
I have started with being unable to flash the device with Special Edition ROM, then XDAUnlock unable to unlock the device etc..
Thanks to http://lumpistefan.dyndns.org/tools/ , they guy did a great job showing in details how to evenutally unlock this wild device with RSU 6.25. So look no futher, this is the holy grail! :idea:
I'm quoting from Lumpistefan website:
How to unlock your Device ....
The PDA side of the ppcpe and the radio/phone/gsm side are two totally different animals (not a surprise to some). When you refer to the 'operating system' you're talking about the ROM like the XDA Developers special edition or any of the ROMs from the ROM kitchen at http://lumpistefans.dyndns.org/. The Radio or RSU (for Radio Stack UPgrade) is totally separate from this. The other variable is the bootloader version (Wallaby in my case).
Now my goal was just to use the XDAunlock program. When I ran the program right from the defaults I got 'error getting unlock code.' All the posts I read said put on the Special Edition ROM and you'll be fine but that did not do the trick. Still got the same error message.
Here's what I started out with:
ROM: 4.01.16 ENG
Radio: 6.25.02
Wallaby booatloader: 5.22
What finally worked:
Radio: 6.24.00
ROM: 3.17.03 ENG (XDA special edition)
then upgraded back to 4.01.16 ENG
Wallaby boot loader 5.15
How I did it
--------------
I meandered my way through this to eventual success and since the dratted device now works fine I'm leery about putting it all back to the old way and doing it all over again. Therefore use this process as a guide only, not a definitive instruction set. Also I walked through this as a troubleshooting exercise so some steps may not have been necessary. I eventually succeeded but maybe went the long way around to do it.
References
----------
- Bootloader utilities: Get to this by holding down the power button and pressing soft reset. You may have to hit the contacts button to get into the menu if you don't see it right away (like if you see a simple GSM OK message at the bottom of the bootloader display.
- Cold boot: the reset swtich on the right side bottom of the device with a picture of a red battery with an \ through it. This disconnects the batter from the mainboard and trashes all the data on the device except the Operating System in ROM.
What I grabbed
------------------
- XDAtools
- XDArit
- ActiveSync (I used 3.7.1) and connection by USB cable
- Wallaby bootlolader version 5.15 files
- XDA Developers Special Edition ROM
- RSU 6.24.00 files
- XDAUnlock.exe
- SD Card (mine is 128 MB but I think as long as it's bigger than 64MB or your current memory in the device you're OK)
- pnewbootflash_40116.exe
All of these files are available here, just search for them.
First back up everything. Not just using the sda backup tool, from the boot loader. You can do the SD backup if you want, consider it backing up your data. You can also do the ActiveSync backup if you want to save your data.
Second I'm doing ALL of this with no SIM chip in the device. This may or may not be necessary.
Stick your SD card into the PDA. If it complains about wanting to format it go ahead and let it format the card unless you have stuff on it you want. I'd recommend dropping anything you want from the card onto safe media and just working with it as a blank the rest of the way through because it's easier to just wipe the card in between some steps.
Go to the bootloader utilities. Hit Contacts button and you'll get the boot loader option stuff. If the bootloader utilities you get to right away takes you to a menu with things like Boot+CE-->SD then you don't have to worry about hitting the contacts button. You only need Contacts button if when you get to the bootloader screen you see nothing more than some nice colors, the bootloader version and "GSM OK" message.
Take the Boot+CE-->SD option to back everything up. This will take a few minutes.
Once it's done pull the SD out ofthe ppcpe and stick it into your SD card reader. Bring up XDArit and chose your removeable device.
If you have more than one MMC slot select the different ones until you get one that says 'Wallaby' in the hex codes at the bottom of the XDArit screen. You'll be writing out two files, the first is the NB0 file (which is the bootloader) and the second is the NB1 file (which is the OS or ROM). Name these something like original.nb0 and 1.
Wipe the SD card (format FAT). Stick the SD card back into the pda and soft reset, then cradle it.
Go to a DOS prompt and CD to where you put 'pnewbootflash_40116.exe.' Type 'pnewbootflash_40116 nbl515.nb0' to write the Wallaby 5.15 boot loader to the device. If when you downloaded the 5.15 bootloader you called it something else (like 'wallaby_boot_loader_V5.15.nb0' you should of course use that name instead!
The output looks like this:
D:\XDAtools\binaries>pnewbootloader_40116 bl515.nb0
Copying D:\XDAtools\binaries\itsutils.dll to WCE:\windows\itsutils.dll
in FindFlashInfoOffset
protection found at 8c0d60f8
result: 00000000 00000000
Now..why did I downgrade the bootloader? At this stage I'm troubleshooting why I get the 'error getting unlock code' message running XDAunlock. I've got three variables I know of, bootloader, ROM and Radio Stack. I chose to start with the bootloader because some posts out there say boot loaders 5.17 and higher have some checksum that keeps certain ROMS from working properly. Perhaps if I'd started with the radio stack I'd have been done right away and saved a few hours but all the posts about possible device destruction made me start with the bootloader! Again, your results may vary!
Next I changed the ROM to the XDA Developers special edtion.
Make sure the SD card is in the PDA and cradle it. Run OSIMagetool and load the ROM file in the first box, chose SD Card in the second box.
If you downloaded the Special Edition ROM you might have some luck using the Installer that comes with it but apparently that does not work with ActiveSync 3.7.1. I got messages that said it could not access the device or no connection etc. Instead I used OSImageTool to load the NK.NBF file included in the distribution. Note that to get to this file you DO have to unzip the EXE file you download!
Once complete pull the pda out of the cradle.
Hold power+soft reset to get the boot loader menu. This should show up as 5.15 now. It will automatically detect that the SD card contains a ROM that can be flashed to the device. If for some reason it does not automatically detect this maybe you have to hit Contacts. I did not have to do that, it just told me to hit Action to download the ROM.
Hit Action button (aka the jog button) to write it to the device. This will take a few minutes, go grab a beer or two or three. I took the safe route and connected power to the device while writing the flash.
Once it's finished cold boot the device. I waited 2-3 minutes before re-engaging the battery.
Here's a gotcha. On the right side of the SIM there is a little switch. If the rubber door for the SIM is not totally closed you can't get the device to boot. This switch is real small so it's very possible to miss it. You can see it fine if you take the back off the device (which I determined from a post here that told you how to get the battery out).
When it boots you should have the 5.15 Wallaby booting the XDA special edition. Follow the instructions to calibrate the screen and you're ready to move on.
Now if the radio is 6.25.02 XDAunlock won't work, it just generates the 'error getting unlock code' message. You have to downgrade the radio to have this work.
There's lots of posts around here that say don't screw with the radio because if it errors you've got a fried device. I imagine this is true so balance how bad you want to unlock the device against the possibility of totally frying the device. I've done two radio upgrades in my life on the PPCPE, both were OK but again, caution is advised.
Grab the 6.24 radio zip and unzip into a folder on your computer. Use ActiveSync to copy the files to \windows on the device.
Execute the rsupdate.exe program to reprogram the radio to 6.24. WHen completed soft reset the device and go into start-settings-system-device info to make sure you're at 6.24 radio vesion.
Copy the xdaunlock.exe to the device and execute. It should say 'you're device appears to be SIM Locked, would you like to remedy this?" click Yes to unlock the device.
Now the device is unlocked. You can change the ROM to WM2003 now if you want (which I did). I imagine you can re-upgrade your bootloader and radio stack if you want but I'm leaving well enough alone for now!
End
Thanks
DaKanadian
I am sure this bit of the question has been asked before so perhaps someone could cut and paste the procedure but I need to unlock this SX56 AT&T phone because I use T-Mobile AND travel abroad quite a lot.
The IMEI number is 350314000995655
(I couldn't find the SX56 model number or the correct ROM code or the Radio number in your pop-down menu so I entered it on the next line)
Unlock procedure
Sorry for last postingjavascript:emoticon('')
Embarassed: Siemens told me that I need an IMEI Number and that AT&T would provide me with an unlock code for this unit with that IMEI number (which obviously they won't)javascript:emoticon(':evil:')
Evil or Very Mad
Is the procedure (for my unit) to ask for an unlock code and then enter it or is it to download
* SD Card Reader
* 1x64Mb+ SD card
* XDATools
* XDA-Developers Special Edition ROM 1.2
1. Backup the existing bootloader and operating system using card reader
2. Extract the XDA-Developers Special Edition ROM 1.2 using Winzip
3. Write the NK.nbf-file (in the directory English) to your Device
4. Running the Programs -> Phone -> XDAUnlock file will remove the SIMlock...
5. after this time, the original ROM could be restored as desired.
And if I need to, can I do all this with Infra Red and sync or with the cradle which connects it to the computer? I cant find any reference to my ROM or Radio numbers in the pull down menu here and am a bit confused by this.javascript:emoticon(':?')
Confused
No, flashing the ROM will not unlock your device. Search for the wallaby unlocker, or check the wiki, as it is there, sticky and has been mentioned before.
Completing unlock process and flashing
I was directed to the flash upgrade program to unlock the device at the XDA-Wallaby Home Page and did flash but nowhere was I given the option to unlock: However the flashing process failed in an unusual and probably not important way: It completed successfully but I have lost the stylus and couldnt figure out how to stop the battery by pushing a fine screwdriver into the hole shown on the host computer screen. All that now shows on the screen is COMPLETED and a number of close-together vertical lines at the far right quarter inch of the screen.
Is there some trick to turning the battery off with some special tool or have I in fact completed the procedure and simply don't know that I have or what to do next? (get to a screen where I can run the XDAUnlock program which I transferred over to the SX56 before flashing the ROM?)
I wonder if I should or need to take the battery off if I Have lost that tool which does this by pushing into the hole on the lower quarter of the unit?
A bit of self-help going on here
So I DO appear to have flashed the ROM and the XDA ROM now appears on the screen although with no real backlight: The DO YOU WANT TO UNLOCK also appears but when YES is pressed, nothing happens. In fact one can see the unit taking the command but nothing further happens and the question just hangs on the screen.
Is this unlocking a command which takes a long time to execute? Or should I cancel out of it and carry on with bringing up the screen and can I execute it later on? Or have I done something major wrong and is there any way of rectifying? Sometimes if I press YES hard enough, the backlight appears for a half second (and the YES command pulsates once) and then goes off. But the question about unlocking still hangs on the screen.
Is this something to do with the program not being able to unlock an AT&T lock? Or has the screen lost sensitivity in some way and if so, (last resource here, improbably necessary) is there a source for Wallaby screens?
FOr the benefit of anyone trying this
NOTE:
After a night of the YES command taking and then not doing anything, I tried MOVING the over-screen by trying to drag it to another position
This didnt work. BUT tapping on the blue bar resulted in a message telling me that the unit was now unlocked. And the 7-8 black vertical lines to the right of the screen now have reduced to one, a quarter of an inch in
(Mind you, tapping on the ok button on THAT screen still mysteriously does nothing. This is a ROM which works in a VERY interesting, unusual and unexpected way!!)
new problem - report of invalid sim
now i am having another problem and am not sure i shoudn't start another thread
'
I did repalce the screen and the unit now starts up and reports invalid sim.
Is there any solution or should I re-flash the rom again and see if that works, hope for the best?
hello i bought a 6315 on ebay, i want to use it in latin america, gsm 1900, i need to unlcok it, room version is A.20.10 i wanted to download the special rom, but the link doesnt work and room folder on ftp is emty, i know is an old phone,can someone help me please unlock it? [email protected]
licensedtoquill said:
now i am having another problem and am not sure i shoudn't start another thread
'
I did repalce the screen and the unit now starts up and reports invalid sim.
Is there any solution or should I re-flash the rom again and see if that works, hope for the best?
Click to expand...
Click to collapse
I found the same happened to me first time and a soft reset did the trick. It may also be that the "Hard Reset" will be needed. I seem to recall that this was what I had to do with a couple of them. If your stylus is missing, a push pin and a bit of control will do. Just shove it in the micro hole at the bottom left of the device and hold it for a few seconds then let it go. If it does not restart on its own, follow that with a "soft reset" by pressing the point of the stylus (or a ball point pen) into the larger hole at the bottom left of the unit.
For the upgrade/unlock rom . . . the best one to which I have access is at:
http://www.landjtech.com/Secure/OutSetting/SX56/xdaunlock2.zip
Hope it helps
***POST DELETED***
As you can see below, it seems I have a lot to learn and the last thing I want to do is mislead n00b's like me. This was supposed to be an "easy" way to mod your HTC 8125 but unforunately you have to walk before run so I'm going to do more reading and hopefully I can help people like me who just want WM6 and an easy How-To to get this done. I'm going to keep the attachments as this may be useful, but the rest I'm removing.
Thanks again everyone for your constructive criticism. I will take everyone's advice and read more.
nnakao said:
***THIS IS FOR EXACT STEPS ONLY!!! I DON'T PRETEND TO KNOW HOW/WHY IT WORKS, BUT IT DID FOR ME. DON'T EMAIL ME WITH QUESTIONS. THAT IS WHAT THE "SEARCH" BUTTON IS FOR.
Ok. So instead of posting a question, I figure I'd post a How-To.
Now I'm a n00b, so I did a lot of hunting these forums to get to where I needed to go. I will attempt to post all credits for work done at the end of the "How-To". If I miss anyone, send me an IM and I'll update the post.
First off, let me tell you what I have:
Pre-WM6:
Cingular 8125 locked
CID Locked
G4 Version (look it up.... I forgot to document exactly)
Windows Mobile 5
Post-WM6:
T-Mobile 8125 Unlocked
CID Unlocked
ROM version: 10.1.0.811 WWE
ROM date: 8/11/06
Radio version: 02.25.11
Protocol version: 4.1.13.12
XMA 6 r 3
Now you may be asking yourself "What?!?!?!?". Yeah, me too. To be perfectly honest, I have no idea what most of those means. Fortunately, if you're like me and just wanted to upgrade the damn thing from WM5 to WM6, you really don't need to know much more than the "Radio version" and SIM/CID Lock/Unlock.
Now for some terms. I've been searching this forum for some time and it took me a lot of asking and a lot of more searching to figure out what half the damn terms mean so I'll try to sum up what you'll need for this peticular procedure:
1. Wizard = The one of many names of the HTC 8125
2. nk.nbf = The image, or ROM, of the WM you want to use.
3. G3 = When you boot your HTC, it should say something like 2.xx.11. Any number less than 2.xx.11 is a G3 device. If I'm wrong, someone please let me know and I'll change it.
4. Brick = You got a useless phone! No No, that may not be true. Try searching the forums to recover from a phone that won't boot.... scared ya, didn't i?
5. (reserved for terms that I just can't think of that are important)
===
Ok. So let's get into what exactly I did to get to this point. Register for this forum to get the attached links).
1. Get the Lokiwiz02b/03a (attachments below)
2. Get SoftSPL or sSPL. For G4 users, this will temporarily allow your HTC Wizard/8125/(others) to be upgradable. I say temporary because G4 users only have 1 option (other than SPL) to unlock the CID and that's to pay like 40 bucks and if you're here, you probably don't/can't pay for it. It's a good work-around (attachments below) (http://forum.xda-developers.com/attachment.php?attachmentid=50344&d=1189619527)
3. Get a ROM in which you want to use to upgrade from WM5 to WM6. Here is a good link given to me (credits at the end of the instructions): (http://wiki.xda-developers.com/index.php?pagename=wizard_WM_6). Think of a ROM as a Windows Install Disk, except it's virtual, not physical.
4. Get Active Sync 4.5. Google it and download it.
5. Get a Radio ROM (attachment below)
6. Get a mini-to-standard USB cable (for your phone.... did you get Active Sync 4.5 yet?)
Note: I've read that this process doesn't work for Windows Vista, but since I hate that damn OS, I don't have it and can't verify it doesn't work.
===
Ok. So now that you have all necessary tools, let's get started on the steps to SIM/CID unlock your phone. Why do you have to do both? I have no freakin' clue, but you do.
0. Unzip all .zip files (not .cab) to your computer (i.e. C:\Temp\HTC\(directory name).
1. Install ActiveSync 4.5 and connect your phone to your computer.
2. Copy the EnableRapi.cab to your phone. You can use Windows Explorer to do this.
3. Run the EnableRapi.cab on your computer.
4. Run the Lokiwiz.bat for LokiWiz02b.
5. Use "U." to SIM unlock.
5a. Do not do anything until your phone completely reboots!!!!
6. Run the LokiwizMsl.bat for LokiWiz03a. (Write down the PIN!!!!!)
6a. Do not do anything until your phone completely reboots!!!!
7. Check to see if you can use a different SIM card (if you have one).
8. Enter in the PIN you wrote down to unlock the Network.
===
Ok. Now we ca finally upgrade the OS/ROM/NBF to WM6.
0. Make sure you're phone is connected to the PC with Active Sync.
1. Copy the wanted nk.nbf/ROM/OS you downloaded to the SoftSPL-V0.1 directory.
2. Run the START-sSPL.exe
3. It will run throuth a RUU (ROM Update Utility) that you may or may not have seen before. Just check all the necessary boxes and "Next" your way through the wizard until it successfully updates your phone.
3a. Do not do anything until your phone completely reboots!!!!
That's it! Your phone is officially updated.... I/you/we hope....
==
First off, I'm going to list the linked sites and who was the original poster. Then I will list the people who've helped me.
1. the-equinoxe = sSPL
2. rudegar = helped with the terms and links to HTC Wizard info
3. ??? = I'm sorry but I don't remember where LokiWiz2-3 came from. I didn't bookmark it!!! dammit! If someone knows, let me know and I'll fill in the ???
===
If I have incorrectly said something in the above, please let me know immediately and I'll change it.
HAPPY MODDING!
Click to expand...
Click to collapse
this is all very confusing and misleading,
Sry to say but you,yourself are not correctly,clear about the whole process of differentiating between the G3 & G4 devices.
SIM/CID Unlocking/ method and upgrading a G3 and G4 are entirely different.
The procedure you have posted is mix up of both devices but not explained correctly.You have posted all tools for unlocking but have not given there description as which one is to be used for which device.
The upgrading method is also not correct,as I gather it's more like it's for G4 devices,you cannot do this method for G3 device,it's misleading here.
I'll advise you to first understand it all fully yourself,You still need a lot of reading to do and fully consume the process,rather posting a guide for Noobies!!!
Check Red markings for corrections
nnakao, I like your effort of putting in answers in the forum. However, as what I've experience so far, it isn't much of a use, in most cases (i.e. some people just do not search). However, nice effort.
Further, I would also like to ask you a favour (probably a copy paste job), to check with the wiki (i.e. this page, top portion, "XDA-Wiki"), to see if there are relavant section (under Wizard) on stuff that you've just mentioned. If
(a) they already exist, double check it and correct them if necessary
(b) if they do not exist, add in there. Usually, others will just point newbiew into there, easier than to find your thread.
Thanks.
you got errors will post later more errors if more but here are some
----------------------------------------------------
"3. G3 = When you boot your HTC, it should say something like 2.xx.11. Any number less than 2.xx.11 is a G3 device. If I'm wrong, someone please let me know and I'll change it."
\/ \/ \/ \/ \/
A G3 device has the ipl and spl 2.xx
A G4 device has the ipl and spl 2.xx.xx
---------------------------------------------------
Wizard = The one of many names of the Cingular 8125 (HTC Wizard)
------------------------------------------------------
Remember to post in big red letters "I am not Responsible for you bricking your device" and "That this is only for G4 devices" so post the difference of g4 and g3 on top.
After a couple of days of trying to search this forum for some basic explanation of some of the tools involved, I've come to the conclusion that it's next to impossible to find anything with the forum search engine.
The forum engine appears to filter out all three letter search terms, like ROM, IPL, SPL and NBF. Basically all the things I need to use as search terms get me nowhere. Put any one of those into the search box and you get no results, even though the forum is littered with references to them.
There are a couple of really useful threads, that have got me quite a long way, but I found them by searching the whole world with google, not by using the search engine in this forum. I'm sure plenty of other people have tried searching for the same information and just given up in despair.
Maybe some links to the correct information would have been more helpful than the criticism this thread received.
Here's quite a good place to start:
http://forum.xda-developers.com/archive/index.php/t-298613.html
If anyone can add anything to help demystify the process of flashing phones and using this forum, I'd be grateful.
Yo, thanx anyway yo!
Alright,
I notice this phone gets very little attention by the community, however, I like the phone, form factor, etc..
I am looking to "cook" my own HardSPL for this phone. Other providers now support GPS, EVDO RevA, Win Mobile 6.1, and I'm still stuck in what I feel is the ice age..
Please note that any instructions with a prompt are to be done in dos..
So far, I have done the following to extract the SPL:
1) Download HTC update for phone and extract using appropriate zip program
2) c:\>NBHextract RUU_***.nbh
This should leave you with a slew of .nb files - one will be named XX_SPL.nb
Now, to disasm this SPL, you can either go straight to IDA PRO or take an intermediate step using dumprom - dumprom creates a pe.exe and handles the offsets for you, so it puts you a step ahead, imo.
1) c:\>mkdir SPLDISASM
2) c:\>dumprom -5 -d SPLDISASM XX_SPL.nb
Now, in the SPLDISASM folder, you should have an exe file that you can now open in IDA PRO.
Now, here's where it is starting to get foggy for me. I followed the same process to dump the stock SPL and the HardSPL from a Hermes phone and I am in the process of hand tracing and hand comparing it to see how SuperCID/Write protection/Protected FF writes is implemented in the HardSPL - hoping that I can port the differences to my phone.
So, I pose the following to the experts:
1) In order to test my HardSPL once it is complete, can I run it as a SSPL and load a new ruu as a test - or will that mean certain death to my device?
2) Now that I'm this far into the code, i've come to realize that reassembling the code will be a lot of pain. Do you guys disasm/asm, or do you just hand edit in a hex editor?
3) Any suggestions to look out for, any ideas, etc?
Let me finish with a few disclaimers
1) To the experts: I have no intention of reverse engineering the HardSPL codebase - if I do use any of the code I have found, I will be sure to give props to the people involved and ask for permission before distributing. I am not looking to profit or scam or steal ideas, i am simply looking at how to make my phone better.
2) To the beggers: I have nothing to release at this time, this is all vaporware, I don't know when it will be done, I don't even know if it's do-able. I'm just trying ATM.
3) To the beginners: any or all of the advice above can probably wreck your device. This is by no way a means to unlock your phone, it's just my thought stream as I take what I believe are the preliminary steps to make my Libra the phone it's meant to be.
desquirr decompiler
I am now using the desquirr decompiler plugin for IDA PRO - it's dumping the subroutines into rudimentry c code.
I am now far closer to understanding what it is my device does; as well as understanding some of the hardspl code.
I recommend this tool if you are also SPL "cooking"
More Progress!
No Replies yet? Man, this is starting to feel like a blog..
Okay, I have managed to dump my Libra SPL, and I have disassembled it, and I have also decompiled it - Well, partially.
All the subfunctions are now represented in C - it's not particularily the most efficient c code I've ever seen, but it's readable. You'll get a hang for it and start to notice the FOR loops, IF/ELSE, WHILE structures.. Multiple return values.. etc.. etc.
I have decided to attach the Stock Libra SPL - I am hoping that I can eventually turn this into a tutorial to build your own custom SPLS for devices that aren't supported by the general community (note, this is high risk stuff..)
Hopefully this will serve as a reference to the community as I progress.
I do hope I get a little feedback too. If I'm going down the wrong path in terms of my approach, or for sharing this project with the community, it would be good to know.
Once again, small disclaimer - this file will not do anything for your phone as of yet.. Just a development step.. (I hope...)
MegaHambone said:
1) In order to test my HardSPL once it is complete, can I run it as a SSPL and load a new ruu as a test - or will that mean certain death to my device?
Click to expand...
Click to collapse
The hard part is to make a patched SPL run as Soft SPL from within OS.
You can try pof's JumpSPL and/or Haret to start your SPL, however I'm not sure these will run on smartphone platform at all. If not, JumpSPL source code should be available, so you can try to figure it out.
Be sure you don't overwrite your stock SPL or radio when flashing a custom ROM with RUU, this is the best way to brick it!
Unless you really can't go without flashing a HardSPL, IMO it's safer to keep the stock SPL flashed for recovery purposes.
HardSpl to add new commands
I'm happy to hear that somebody is working on a hard SPL for HTC S720. Here's the deal, I really want to change esn in this phone but I realized that for now it's not possible.
It's a MSM7500.
**I've tryied QPST but the version 2.7 only support MSN6500.
**I've tried QXDM 3.9.19 and still can't write the new esn. It says read only.
_________________________
How to put it not in read only?
Could I use a anykind of ready/writer to change info directly on the chip?
-----------------------------
**CDMA Workshop 2.7 all kind os ESN write doesn't work.
-----So, two options left:
1- either I desolder the esn chip and change it for a new one (to be honest, I haven't discovered yet if the esn is inside the MSM or on a different chip. If it's the case (on a diff. chip) it's a bit a pain in the but to do but it's still an option.
2 - I want to try shadowmite's method for writing the ESN into a PPC6800. Again it need to be done in high level via MTTY.
Concerning MTTY I cannot run commands because I can't put the phone on the boot loader screen.
I will try to run RUU wich will put the phone in bootloader screen. And then try mtty.
If this fail, I guess my only hope will be a hard spl.
I guess I've said a ton of thing that gonna make me look like a newbie (wich I am in prgramming).
Any suggestion...? Or any help I could bring to create this hard spl?
I am using HTC S720 in India. Currently I am using windows 6. Is it possible to make it work for windows 6.1. Telus ROM for HTC S720 is already available.
HardSPL for HTC5800/S720/LIBRA
I am currently trying to create a HardSPL for this phone and am having a hard time. I really need a solution for this and if anyone can create a HardSPL the company I work for is willing to pay a reward.
Why not try get a goldcard for it.Try ask at http://psas.revskills.de/ or if you know anyone with a axebox i think they do goldcards
Hi all!!
Ever since I got my Sprint Vogue, I have spent God only knows how many hours looking for and gathering information regarding this phone (flashing instructions, unlocking, SuperCID, etc). There are a few sites that have fairly comprehensive guides as to how to do this, but there are very few posts in the Vogue Section here at XDA-Developers.
Having said that, I figured I would create my own "How to Flash Your Vogue"-Thread. This is a multi-step process and I cannot emphasize the importance of following every step down to the "T", that is unless you are looking for a silicone-skinned brick...
Who is this guide for?
*Anyone with a CDMA version of the Touch. [highlight]That means no GSM[/highlight]
*Noobs and Seniors alike.
*People who have trouble flashing their devices.
*Anyone looking for links to more information.
*Curious people in general.
*Anyone willing to get rid of the nasty stock rom and looking for a newer and cleaner OS (notice that I never said more stable, so do not blame me afterwards ).
[highlight]Please keep in mind that there is always a chance of bricking your device with these procedures. I will not be in any way, shape, or form responsible if you damage your device while doing this.[/highlight]
Got your coffee? Alright, let's do this.
Step 1. Preparing the device
As with every phone, you have to make sure that you have the following things done before flashing:
* Battery charged at least 50%.
* All the necessary programs (see next post).
* Instructions handy.
Make sure that you back up all your information (contacts, e-mails, files).... essentially, anything that you would like to keep post-flashing. You can do this via Active Sync/Mobile Device Center or via third party software (PIM Backup is really good)...
You will have to reinstall every last piece of software in your device as it will be hard reset. Some programs may work if installed in a SD card directly, but a lot of them write things to the registry and copy files to the device, which they require to run. Long story short, keep all your cabs and exe files in a safe place so you can restore later if needed.
Step 2. Unlocking the Device (HardSPL)
Unlocking the device is done so that you can flash custom roms in your devices. The unlocker that you are about to download and use was provided by "ImCoKeMaN" at PPCGeeks. If you are interested in the full thread, please click here.
If you have read the above link, you will see two versions of the HardSPL (0.40 and 2.31). Simply use 2.31 as it works fine with most devices.
[highlight]To use this under Windows XP,[/highlight]
1. Connect your device to your computer and make sure it is synced with ActiveSync.
2. Download and extract the contents of the zip file, which is an exe. Let it run to completion. You will be prompted to disconnect and reconnect your device at one point in the process. Do it... don't worry
3. It will look like it is flashing a rom via a RUU. Do not disconnect the device after it is done!!!!!
4. Once it is done flashing, you will see a prompt that says that it will run exitbl. DO NOT DISCONNECT YOUR DEVICE. At this point, open ActiveSync, go to File>Connection Settings> Uncheck "Allow USB Connections". Continue following the on screen instructions and let it finish.
5. Go to bootloader once more to verify that it worked. You should see 2.31 CoKe MFG.
[highlight]To use this under Windows Vista/7 x64 (thanks jitajt),[/highlight]
jitajt said:
connect your device to WMDC (it's not necessary to set up device, just connect without setting up device)
then right click on the 2.31 unlocker and run as administrator
follow the directions, you will get an error about sleep.exe not being compatible with x64 but just hit ok and continue, (you will get about 10 of them)
then just keep following the directions in the command prompt and it will put your phone into bootloader then you have to disconnect and reconnect when it tells you to. and it will flash your phone and reset it. then your done you can close the command prompt and disconnect your phone.
I did it just like above and I have not had any problems.
Do this at your own risk as I am not responsible for your phone
Click to expand...
Click to collapse
Step 3. Flashing your Roms
The time has finally arrived. You sat down patiently through the unlocker and you are now ready to take the leap of faith into what you believe will bring your device to a new level of usefulness (also known as getting rid of that nasty, bloated, stock rom )
The process is relatively simple:
1. Download the RUU package from this post. I am only posting this because some cooks only post the rom nbh files rather than the whole package.
2. Go into the threads and look for whichever rom you prefer. Look at my signature to learn which one I am using. NFSFan (my current one) is by far the best one I have tried so far. You can download it from here
3. Put your device in bootloader mode and connect the device to the computer. [highlight]Once in bootloader, activesync will NOT see the device. If the RUU gives a connection error, try to run it with the devices in regular mode (with ActiveSync connected)[/highlight]
4. Open the Romupdateutility.exe and follow the steps.
5. Once it is done flashing the rom, disconnect it from the computer and hard reset it. To do this, simply hold "Send" + "End Call" +Stylus in the reset hole for about 3 seconds. It will prompt you to erase all the data and restore to factory defaults. Press "Enter", which is the center button in the directional pad. Once it is done, press "Send" to reboot.
Congratulations, you just flashed your first rom for Vogue
Step 4. SuperCID
This step can be skipped if you are not thinking of doing anything as far as your radio (such as flashing radios other than the ones intended for Vogue). This is also used to do other things such as modifying certain important things on your device such as the NV files, which is information that will not be discussed here. However, if you are interested in finding out more, simply google it, there is a ton of information out there.
Anyways, back to SuperCID... here is the procedure (thanks to hpnasik at mobile-files.com for the post)
1. Download the following special rom . This is an Alltel rom with radio 3.37. This was specially prepared to be able to reduce the Security Level of the device to level zero.
2. Download mtty since you will need it. Do not worry if you do not how to use it. You will have a step by step in this guide.
3. Flash the Alltel rom from above.
Now comes the fun part...
4. Disable USB in Connection Settings of Active Sync
5. Boot The Phone holding power button and camera button to enter bootloader.
6. Phone Will Display Serial in Bottom
7. Connect Phone to PC
8. Phone should Display USB instead of Serial in Bottom
9. start mtty.exe
10. Select All Default and Connect to USB in drop down box and Shoot the Following Commands (All Commands are case Sensitive)
11. run command rtask a : After this Command Phone will not Display any thing
12. run command echo_on : even though nothing is shown to screen
13. run command readCID : in Sprint it will display SPCS_001
14. run command writeCID 00000000 : Set CID Value to 00000000 replaces SPCS_001 in Sprint (This make PPC Radio Security Level to Zero)
15. run command readCID : This will Display the Update CID as 00000000
16. run Command retuoR : This will return to Original Boot Loader State
Congratulations, you just SuperCIDed your device. Original thread with the instructions can be found here if you are interested.
Step 5. Flashing your radio.
Now that your device has been SuperCIDed, you will have the opportunity to flash radios that have been ported to this device (ie. there is a version of the 3.42.40 radio for the Titan, which has been ported to the Vogue). There are two ways of doing this:
Way 1: Do it by flashing via RUU (same as with flashing a rom)
Way 2: Flash via microSD card. Simply put whichever radio that you wish to flash in the root of a 2GB or less microSD card formatted to fat32. Rename the radio to VOGUIMG.NBH and put your device in bootloader. The flashing will start by itself.
Way 3 (I know I said two ways...): There are a few stock roms that come with new radios. One of them can be downloaded directly from HTC and it is for the Sprint Touch. This one comes with Radio 3.42.30
The other one is for Bell Mobility and this one comes with Radio 3.42.50.
Why am I giving "Way 3" if the other two options seem much easier?? I have run into the problem where my device would not let me flash other radios than the one that I had. SD card method did not work and the RUU started out fine but quits at 8% rebooting my phone and displaying Error 328 in the RUU on the PC. Anyway, here are the links...
Sprint rom with radio 3.42.30
Bell rom with radio 3.42.50
Verizon Stock Rom
All Shipped Roms (All Carriers) - Thanks conflipper!
All Above Radios zipped
The newer radios perform a little better and give out better GPS signal (faster locks)....
Hang on a sec... did you just say GPS?!?!? But my Vogue does not have a GPS.... It does, just read a little further and be happy
Step 6. Enabling GPS, Returning to Stock, and Carrier Cabs
As I said before, there is a GPS hidden on your device. Now, if you are like me and went straight to the specs of the phone to confirm, you will probably try to call BS on this. Long story short, there are a few custom roms which have this "tweak" already implemented (like the one I am using from NFSFan). If you require some more info, I will post it later...
[highlight]Location must be on or else your GPS will not work. To activate it, go to Settings>Personal>Phone and change the Location setting to ON instead of 911 (thanks for pointing it out, th3lolz)[/highlight]
[highlight]For Verizon Users[/highlight]
br125 said:
For those of you with the official mr1 update from verizon that cannot get their gps working:
My xv6900 came with the official update and I got it working, it involves downgrading to a NON-GPS radio, then back to a gps radio...
go here: http://forum.xda-developers.com/showthread.php?t=533639
now the instructions are going to imply that you must load the unlocker before each flash... bs don't worry about that
1. flash the .40 unlocker
2. flash the non-gps rom (reset before customization)
3. flash the 2.31 unlocker
4. flash the vzw rom (reset before customization)
5. flash any custom rom or android rom
that's it, time consuming, but it works
*ignore the multiple flashing instructions, its completely unnecessary, I've never flashed more than once with no problem ever....
I also suggest keeping the vzw radio, but do as you will, I like the 3.37.38 radio.. ain't broke don't fix it
lastly, just make sure you RESET BEFORE THE CUSTOMIZATIONS RUN...... that is what locks your gps.
good luck!
ps. the verizon radio rom that is in that post is for the "leaked" 3.37.37 radio, I reccomend using the official update from verizon here for the 3.37.38 radio rom instead:
http://www.pcdphones.com/phone_downloads.aspx?bid=95&cid=1&mid=302&carrier=Verizon Wireless
RESET BEFORE CUSTOMIZATIONS
Click to expand...
Click to collapse
[highlight]How to Relock you phone[/highlight]
If, for whatever reason you need to return your phone for repair/replacement, you will need to relock it. To relock your phone, simply run the unlocker 0.40 and flash the stock rom of your carrier.
ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker.exe
[highlight]Carrier Cabs[/highlight]
Thanks to Codybear for gathering all of the cabs with settings for various carriers. But since the link went down, here is another one courtesy of LMiller1708
https://sites.google.com/site/vogueroms/vogue-files
This information was only gathered by me and I take no credit whatsoever other than trying to put it in a one stop thread. Thanks to the following people
Shadowmite
ImCoKeMaN
mindfrost
NFSFAN
Codybear
joshkoss
and a bunch of people that were involved in developing all this...
Thread sticky'd as requested
Peace,
Josh
ok so im a noob n all at this but for some reason when i go to start the Vogue unlocker it tells me to connect my phone, when its already connected. Ive tried everything my even switched to an xp from vista but still no luck. Please help
dwigginstm said:
ok so im a noob n all at this but for some reason when i go to start the Vogue unlocker it tells me to connect my phone, when its already connected. Ive tried everything my even switched to an xp from vista but still no luck. Please help
Click to expand...
Click to collapse
How exciting!! My first victi...erh patient
Did you put the device in bootloader mode? If you did and it is connected to the PC, you should see USB on the screen of your device. Also, do you have ActiveSync on your XP machine? You will need it for the drivers on this step. Changing USB ports sometimes help as well. And one last thing, do not use a USB hub, go directly through the USB ports in your computer. Good luck!
yes i have activesync installed xp, and yes it changes from serial to usb in bootloader mode. But once i connect it to the pc while in bootloader mode my computer recognizes just activesync doesnt, only when its on and not in bootloader mode will activesync recognize it...
yes i have activesync set up with the phone and pc, but when i put the phone in bootloader mode and connect it the pc recognizes it but not activesync. is there another program i can unlock the phone with?
dwigginstm said:
yes i have activesync installed xp, and yes it changes from serial to usb in bootloader mode. But once i connect it to the pc while in bootloader mode my computer recognizes just activesync doesnt, only when its on and not in bootloader mode will activesync recognize it...
Click to expand...
Click to collapse
Do not worry about ActiveSync. While you are in bootloader, the device is not running WM, which is why your computer only sees it as a USB device. This is perfectly fine. ActiveSync will not recognize it.
Please, follow the instructions in my post for unlocking. Read it thoroughly and try to understand it, else you will end up bricking your device.
ok but when i begin the unlocking exe it tell me to connect the device to activesync, althought the only way activesync will notice it is if i take it out of bootmode. your help is appriciated
dwigginstm said:
ok but when i begin the unlocking exe it tell me to connect the device to activesync, althought the only way activesync will notice it is if i take it out of bootmode. your help is appriciated
Click to expand...
Click to collapse
that is a message in the RUU. do not pay attention to it. good luck...
so i finally got the unlocker to start and it begins the ten minute process and stops then show a 262 error code ive done this over and over again
Let's go from the top. I just saw the message that you were talking about. The unlocker does ask for ActiveSync as you pointed out and it is asking you to connect the device to the computer. Then it asks for you to press any key when that is done. So, try that and you should see the word "initializing" with a dotted line getting longer for about 20 seconds. Do that.
The RUU will start up afterwards. The prompt will tell you that it is going to flash a new SPL, and if I am not mistaken that is where you are getting stuck.
Just out of curiosity, which version of the Vogue do you have? (Alltel, Bell, Verizon, Sprint, US Cellular)?
no internet
i just flashes my cell for the first time in with sprint NFSFAN's WM6.5 1.00 FINAL ROM worked great but for some reason my internet doesnt work i downloaded NFSFAN Sprint Provisioning but i dont know how to use it. It has a cople files SPRINT~1.000 and 000DUMMY and setup.xls
thanks in advance
terrancextc said:
i just flashes my cell for the first time in with sprint NFSFAN's WM6.5 1.00 FINAL ROM worked great but for some reason my internet doesnt work i downloaded NFSFAN Sprint Provisioning but i dont know how to use it. It has a cople files SPRINT~1.000 and 000DUMMY and setup.xls
thanks in advance
Click to expand...
Click to collapse
You downloaded a cab. Simply put it in your SD card and run it by tapping on it. Don't unzip it...
Unlocker is not 64 bit compatible... grrr....