I am not able to get my SPC /MSL from my new Sprint Diamond that I have been able to unlock, and flash Juicy 2.2 onto it. Since then I have performed a hard reset and gone back to the factory ROM.
I have tried the following:
1. Performed the instructions for getspc from
http://forum.ppcgeeks.com/showthread.php?t=36639
(Note I did use the PHex Esn and I did use caps on all hex numbers)
2. I was able to install QPST on a on WinXP box and get it to see the phone. I did this to verify that I had the correct hex esn. QPST did read the esn from the phone and display the same hex esn that I had in step 1.
3. I tried the general codes 000000, 123456,111111 and the last 6 digits of the phone number programmed in the phone 000-000-2743.
I am entering the number (6 digits) that getspc.exe tells me in the enter unlock code box that comes up after I enter ##778# and hit edit. It looks like it is working on something then tells me the code is wrong.
What is the way that I can get the SPC / MSL without calling?
The only answer I found
I hate to ask and answer my own questions but if anyone else runs into this problem I want them to have an answer.
I could not get getspc.exe to work in any way.
I found this registry hack somewhere so I am not taking credit for it but it works!!!!
Change the following registry entries in:
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\ATDbgLog
Enable: 1
LogMode: 1
* Wait a reasonable amount of time and soft-reset (I have noticed that it seems to take longer for this value to take affect, so if you reboot and the registry values are not changed, then you need to do it again and wait longer)
* Check to see that the file \ATDbg0\ATDbg0.txt has been created.
* Return the values back to what they were (most likely 0) waiting the same amount of time as above.
* Look in the ATDbg0.txt file and you should see a log of commands sent to the CDMA radio and there should be something like this somewhere in the file:
|| Begin Code Sample ||
11:9:3 Tx:AT+HTC_RMSL=0\r
11:9:3 Rx:+HTC_RMSL: 354201\r\n0\r
11:9:3 Tx:AT+HTC_ROTKSL=0\r
11:9:3 Rx:+HTC_ROTKSL: 216112\r\n0\r
|| End Code Sample ||
The numbers next to the Rx: +HTC_RMSL line should be your MS
I used resco exploror to change my registry waited about 1 hour and did a soft reset twice during that time.
I found the directory with the output file in the root directory.
Yes, it works
the getspc.exe, don´t work, but the this process work very fine
Related
Hi
Am newbie to the whole XDA thing (am just converting from BB), have managed to unlock my XDA Mini S and tried running K-JAM_WWE_216901_2169101_020721_ship.exe as i heard this would reflash the ROM to the latest (a friend of mine gave me this copy).
Got an error during this, and wondered if there was a specific XDA Mini S version (have searched on the site and it appears that there is on ftp://ftp.xda-developers.com/Wizard) and there are many different ROMS under the ROM directory, but i am unable to login to this site.
Am i just being thick here.
Any help gretaly appreciated.
That ROM upgrade worked ok on my xda-mini-s
When I upgraded my ROM I done the following.....
#unlock phone
with no SIM card in phone
copy EnableRapi.cab to phone
run EnableRapi.cab from phone
run lokiwiz.bat from PC
select option 'U' Unlock SIM
phone reboots
add SIM to backout bin file names on PC
run lokiwiz.bat from PC
select option 'C' unlock CID
phone reboots
add CID to backout bin file names on PC
#install new ROM
uncomress ROM file from zip
click ROM install file
follow instruction
takes 10 minutes
phone reboots
Hope this helps
Bilbo,
Hi. I ran through what you put but my Mini S does not auto reboot. I'm not sure the exact definition of a soft reboot is? - Put the stylus in the side or hold the power button for a few seconds?
Either way I cannot get the new KJAM rom on as invalid vendor ID is haunting me.
Any help would be appreciated.
Thank You
Ben
Dudes - I've done the same upgrade to my mini S. Not sure if it's worth the bother. No difference in speed/performance and my keyboard shifted symbols (@?£$) are out of sync. I think I'll go back to the Mini S rom without the customised stuff.
LLcoolJ:
I noticed lots of difference, speed and battery life.
To get the keyboard from US to UK symbols use the following:
Here are the registry changes ....
Keyboard language
Registry: HKCU\ControlPanel\Keybd
Key: Locale (string)
Value: 0809 English UK
0409 English US
0407 German
0419 Russian
040C French
0410 Italian
040A Spanish
benih007 said:
Bilbo,
Hi. I ran through what you put but my Mini S does not auto reboot. I'm not sure the exact definition of a soft reboot is? - Put the stylus in the side or hold the power button for a few seconds?
Either way I cannot get the new KJAM rom on as invalid vendor ID is haunting me.
Any help would be appreciated.
Thank You
Ben
Click to expand...
Click to collapse
The invalid vendor ID is the result of the ROM update..... to get rid of it make sure you run :
run lokiwiz.bat from PC
select option 'U' Unlock SIM
phone reboots
add SIM to backout bin file names on PC
A soft reboot is when you hit the reset button on the right hand side, its like rebooting a PC. A hard reset however is a re-install boot where you loose everything and the ROM is re-installed.
Cheers Bilbo - I've made the changes to the registry and the keyboard talks like me. Your right about battery power as well.
Bilbo.
Thank you for replying and helping.
Let me just go over what you said...
first I ran the loki cab file on the mini S.
run lokiwiz.bat from PC -- done.
select option 'U' Unlock SIM -- done (with sim card removed)
phone reboots -- not automatically though, but I will reboot it after the lokiwiz.bat finishes
add SIM to backout bin file names on PC -- what does this mean? this is not in the lokiwiz instructions and this is where i'm going wrong. Where is the bin file created btw, I can never find it?
I have tried so many combinations i'm starting to lose hope.
If you can help to get this damn thing working I promise to make a donation to this web site.
Thanks for all the good work.
Ben
i managed to get the unlock, but did not do the CID (so will try that).
So once i have done that will the K-JAM_WWE_216901_2169101_020721_ship.exe upgrade work?
Here's how I got mine working. - Remove the Sim card. Make sure you use Lockwiz02b. Select U to unlock from the options menu. The mini S should reboot automatically. Leave the device alone until its functional again and then start Lockwiz02b again. Select C (CID unlock) from the menu. It should reboot again and close down the Lockwiz box. The mini S should now be ready for a rom upgrade. On my first attempt I used the original Lockwiz prog which caused problems for me.
I'm about to do my rom update on my mini s....but this thread is so confusing!
Is there a step by step guide somewhere on the forum???
ROM Upgrade
Upgraded O2 XDA mini without any real problems:
I used the aWizard 1.3 Beta 2 tool which allowed me to carry out the CID Unlock and was pretty easy to understand. What it did not do was pick up the ROM from the rom folder but once I had completed the CID unlock I ran the rom normally and all was well.
So in essence: Connect Mini to PC via Activesync
Run the aWizard Bat file enabling RAPI (This is used to communicate with your XDA once it has done using Activesync). Then select the Unlock CID option. Once completed I then exited the wizard and followed the instructions as part of the rom upgrade and all worked well no hitches except the one mentioned above about the keyboard (now I have to find out how to modify the registry).
So what I used: aWizard 1.3 Beta 2 and QTEK Rom 2.17
186504-ruu_9100_2170702_21707102_20710_qtek_wwe_ship.exe
Mystery Solved!!!!
I finally figured out why its not working....
When I downloaded the loki zip file I opened it up in winzip and dragged the contents to a folder I created. Ran the batch file eveything seemed ok and the unlocker said it unlocked the device.
I have now realised that you have extract the files from the loki zip file and use the folder structure. If you don't, the utils directory is not created and the loki.bat cannot reference some files.
Found the answer on page 12/13 of the loki thread.
Thanks All
Ben
After doing the CID unlock the ROM install worked fine.
Just having the keyboard issue at the moment with symbols, went to:
Registry: HKCU\ControlPanel\Keybd
Key: Locale (string)
Value: 0809 English UK
but could not find the locale key to set to UK?
All i see is:
DefaultKeyLock
InitialDelay
MuteSwitch
RepeatRate
ShowWarningMsg
Am i looking in the right place or do i have to add this in (if so how)?
Cheers
Youv'e got to create a new registry key. Assuming you've got a registry editor. Go to HKEY_CURRENT_USER / Control Panel / Keybd.
Then create a new string value. Name it Locale and give it a value of 0809 for UK. Then reboot.
Just went in a created the new reg key as you mentioned.
Rebooted and it worked.
Many thanks for all your help on this, it is most appreciated.
I am now the converted!!!
So to sum up for anybody else:
Bought XDA Mini S from 02
use Lockwiz02b
Select U to unlock from the options menu
The mini S should reboot automatically
Start Lockwiz02b again
Select C (CID unlock) from the menu
It should reboot again and close down the Lockwiz box
The mini S should now be ready for a rom upgrade.
Then run
K-JAM_WWE_216901_2169101_020721_ship.exe
follow usual prompts.
Once phone is up and running, get a reg edit tool (i used PHMregedit) as the keyboard for a couple of the symbols is out of synch (think it is US style).
Using regedit tool
Go to HKEY_CURRENT_USER / Control Panel / Keybd
Then create a new string value
Name it Locale and give it a value of 0809 for UK
Then reboot.
Mini XDA should now work fine.
I have found that the new push technology for email is faster than Blackberry and more usueful.
Hope this is helpful to others.
Cheers great forum
quick question...
i am fed up with waiting for o2 to release their latest ROM so i am going to take the plunge with this ROM instead, my question is do i have to make any special changes once installed to make it work with O2 UK i.e. mms settings, GPRS settings etc.?
Also i noticed somebody has put together a T-Mobile USA customised ROM any chance that somebody will do this for O2 UK?
hyettd said:
Just went in a created the new reg key as you mentioned.
Rebooted and it worked.
Many thanks for all your help on this, it is most appreciated.
I am now the converted!!!
So to sum up for anybody else:
Bought XDA Mini S from 02
use Lockwiz02b
Select U to unlock from the options menu
The mini S should reboot automatically
Start Lockwiz02b again
Select C (CID unlock) from the menu
It should reboot again and close down the Lockwiz box
The mini S should now be ready for a rom upgrade.
Then run
K-JAM_WWE_216901_2169101_020721_ship.exe
follow usual prompts.
Once phone is up and running, get a reg edit tool (i used PHMregedit) as the keyboard for a couple of the symbols is out of synch (think it is US style).
Using regedit tool
Go to HKEY_CURRENT_USER / Control Panel / Keybd
Then create a new string value
Name it Locale and give it a value of 0809 for UK
Then reboot.
Mini XDA should now work fine.
I have found that the new push technology for email is faster than Blackberry and more usueful.
Hope this is helpful to others.
Cheers great forum
Click to expand...
Click to collapse
The Problem im having here is that once i have created the registry key, it deletes after a reboot. Is there something else i need to unlock to allow writing to the registry?
New Roms
Hi there - I'm sure this is your answer - I have read this on many forums.
WM05 takes a while to store the registry updates after you exit your editor. Make the registry change and wait a minute or so before performing the soft reset.
Hope this helps - we have all fell for this "improvement" to WM5 from the boys at MS.
Regards,
Chris.
:lol:
Thanks Bilbo . . . Spot on. First time to all this and followed it a treat
Thanks All
Ok I have read this site several times and have flashed my phone numerous times and I can say there are some damn good ROM's located on this site..However there are flaws to each one and that is why i am writing this..I do appreciate all of the hard work that goes into these roms for if you guys didnt do them then we would be stuck with the same ol tired looking phones..
For those of you that are new to this please pay attention to the posts for i have learned the hard way..I would like to know how to fix some of the errors that are in these roms because like I said befor each one is different..so far the one that i have found to be the best for most users is OTP v7.5.1 TouchFlo 2D Professional...this Rom seems to have it all together except one thing..the call volume is low and the ringtone volume is also low..besides that this is your winner in my eyes for a power user..
If anyone out there knows how to fix these errors please let me know for I am staying with this ROM until I find a better one...thank you for your time and I will be donating to the rightful developer...
Beat Tweaker
[email protected]
BEATTWEAKER said:
Ok I have read this site several times and have flashed my phone numerous times and I can say there are some damn good ROM's located on this site..However there are flaws to each one and that is why i am writing this..I do appreciate all of the hard work that goes into these roms for if you guys didnt do them then we would be stuck with the same ol tired looking phones..
For those of you that are new to this please pay attention to the posts for i have learned the hard way..I would like to know how to fix some of the errors that are in these roms because like I said befor each one is different..so far the one that i have found to be the best for most users is OTP v7.5.1 TouchFlo 2D Professional...this Rom seems to have it all together except one thing..the call volume is low and the ringtone volume is also low..besides that this is your winner in my eyes for a power user..
If anyone out there knows how to fix these errors please let me know for I am staying with this ROM until I find a better one...thank you for your time and I will be donating to the rightful developer...
Beat Tweaker
[email protected]
Click to expand...
Click to collapse
I have a couple questions for you, one, can you give a link to that rom? And two, how long have you used it?
All of your questions are answered inside
refuse2bstopped said:
I have a couple questions for you, one, can you give a link to that rom? And two, how long have you used it?
Click to expand...
Click to collapse
I have been using this rom for a couple of weeks now and I have just discovered once I reflashed it I have seemed to fix the only error that was found...
here is a posting that will give some info and hopefully answer alot of your current questions..
Default FAQ
FAQ Section:
Read everything in this section before downloading the roms and flashing.
If you don't understand it, read it again and again until you understand.
Once your done flashing your device double check back here again to configure your device.
I will not reply to any subjects already covered in this section.
I'm not trying to be rude, I'm just very busy with finishing up this project and also working on other projects.
Back up your phone before downloading and flashing this rom... I do not want anybody to loose their data due to flashing this rom, as the rom will erase all of your data...
How To Flash Rom
HERALD-USPL-beta3 - posted by tiksister - rapidshare
How-To Flash the HERALD-USPL-beta3:
Download and extract both files.
Place the extracted OTP v7.1.nbh into the Herald-uspl-beta3/RUU folder.
Move the entire Herald-uspl-beta3 folder to the root of the c:\.
Follow the simple readme file.
Break down of how to flash this rom:
Then follow these steps:
II. How do I flash an NBH file?
a. USPL
Step 1. Download Herald-USPL-Beta3. http://www.megaupload.com/?d=A4N36HLO
Step 2. UnZIP the file into a folder on your Desktop. Let's call it "MyFirstROM" for simplicity's sake. Notice that there is a folder called RUU within this folder now. Keep that in mind.
Step 3. Download your NBH file and unZIP or unRAR it into that RUU folder. Make sure that that NBH file ends up in the RUU folder, not within a folder inside the RUU folder.
Step 4. Place your phone into flightmode.
Step 5. Go back to the MyFirstROM folder and then run USPL.exe
Step 6. Follow the directions on the screen. EXACTLY.
* Your screen on your cell phone will go white around the 75% part of the "second step" now.
* ActiveSync will LOOSE its connection.
Step 7. One step 3 on that black window, the RUU flasher will pop up. Just follow the steps.
That's it. Welcome to the flasher's world.
Instructions by Ivanmmj
===================================
If your device is already HARD-SPL read the following link before flashing.
HARD-SPL
======================
Disable Random Access and Enable Scrolling
With random access you must do the following to enable contact scrolling.
Click on the contacts button at the lower right hand side of the screen.
Click on the Menu button
Click on Options
Uncheck "Show alphabetical index
Click on the ok button to exit
Now I know the following will sound strange but it will enable scrolling in the contact menu.
Repeat the following steps again, and the random acess bar on the right handside will go away and scrolling will work again.
Click on the Menu button
Click on Options
Uncheck "Show alphabetical index
Click on the ok button to exit
If you want to enable random access, just go back and uncheck the "Show alphabetical index"
======================
How to turn off QuickMenu
/Start/QuickMenu/Exit
It will prompt you with "Exit QuickMenu?
Choose yes and it will not startup again even after a reboot.
Things to do after flashing your device:
Network Wizard
Go to \Start\Settings\Connections\Network Wizard
Choose your location and provider, do not reset the device when prompted.
Connections
Go to \Start\Settings\Connections\Connections
Once completed save and exit
Video on how to setup your device after flashing
MMS/SMS Setup
Send Large MMS:
Registry: HKLM\Software\Arcsoft\ArcSoft MMS UA\Config\UI\Size Limit
Key: wap2sendlimit1 (you can also change wap1sendlimit1)
Default: 307200
New Value: 1228800 (1200K)
Registry: HKLM\Software\Arcsoft\ArcSoft MMS UA\Config\UI\Size Limit
Key: sendlimit3 which will be set to the default of 300k. u gotta change it to 1228800 and than the 1200k will appear.
note u can also change sendlimit 2, 1 to be the same as what ever u decide to change wap * sendlimt* to be. once u do this the 1200k will appear.
++++in between doing the above and below, u have to go to
Set the new value by going to Text/Multimedia --> Menu --> New --> MMS --> Menu --> Options --> MMS Options --> Servers --> T-mobile MMS
=======================
Soft Keys
The calendar and contacts keys can be changed with the following steps.
/Settings/soft keys
Use this setting feature to change to what every programs you want.
========================
Show CIM contacts
By default it has been disabled so your CIM contacts will not display, use the following reg hacks to enable it.
[HKEY_CURRENT_USER\ControlPanel\Phone]
"ShowSIM"=dword:00000001
=========================
Show clock instead of battery
If you want to show the clock instead of the battery or the other way around, use the following reg hack.
Clock
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell]
"ShowTitleBarClock"=dword:0
Change the current dword:0 to 1.
Battery
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell]
"ShowTitleBarClock"=dword:1
Change the current dword:1 to 0.
==========================
M2DC
Just tried the M2DC theme manager on 7.3 Std, with a renamed .zip file to .m2dct file (specifically the KnobiSkin from the M2D skin thread).
First time, it locked up. M2DC continued with spinning icon until I forced a reboot. Touchflo was off after reboot, and after enabling it everything appeared to be the same.
Second attempt, I disabled Touchflo from today before applying the new theme. Got the "Applying Theme" prompt. After M2DC closed, I reactivated touchflow and new theme was applied.
Simple instruction for use of M2DC Themes on OTP 7.3:
Find a skin you like, download the zip file (not the cab),
Rename file to .m2dct,
Copy new file to the themes directory of the M2DC install directory,
Disable touchflo in Today settings
Start M2DC,
Go to themes tab (the first time it will back up the default theme),
Click the new theme then apply,
Restart touchflo.
Alternate for creating themes from skin CABs:
Run M2DC first, let it make the DefaultThemeBackup.m2dct file, Close M2DC.
Run the CAB skin of choice.
Rename DefaultThemeBackup.m2dct to OriginalTheme.m2dct (or anything else with same extension).
Rerun M2DC. It will detect no DefaultThemeBackup.m2dct and will ask to back up again. Let it make new backup. Close M2DC.
Rename new file to the name of the new theme.
Repeat for each skin CAB you wish to convert to m2dc theme file.
Note: The M2DCT files can be large (over 3Mb, 660 files backed up). Best to do this only if M2DC is installed on a large Storage card.
Note 2: Several times M2DC appeared to freeze when applying or backing up themes. It looks like it has problems if touchflo is not off prior to running. It does try to deactivate touchFlo then reactivate when done, but it doesn't appear to work flawlessly yet. It is better to deactivate the Today plugin before running M2DC on this ROM build.
__________________
This mirror pretty much has all roms from version 7.0 - 7.7 which is the most current.
http://www.evolvers.net/Herald_Roms/
Here is one link that has some pretty useful items in it also:
http://forum.xda-developers.com/showthread.php?t=341867
thanks to all of the developers and cooks on XDA for without you guys none of this would be possible
i thought this was interesting. maybe a FREE way to hard spl? i have not tried this out. have no idea if it works. iam not a dev i dont know if this can even be called hard spl. or just a reg edit.
Regedit STG
This is a signed version which is needed to unlock the phone (a little easier to unlock than a IPhone). Cut & paste from Robert Peloschek’s blog:
1.Simply put the *.zip file with the regeditSTG.exe in it with ActiveSync into a folder on your phone (but not onto the memory card).
2.Unzip the file with the *.zip program that comes with your phone.
3.Now start regeditSTG.exe and change the following Registry Keys:
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001001 = 2
-> Change the value data from 2 to 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001005 = 16
-> Change the value data from 16 to 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001017 = 128 (mine 36)
-> Change the value data from 128 to 144
HKEY_LOCAL_MACHINE \Security\Policies\Policies
-> Add new value “0000101b”: Dword = 1
After you have done all these steps close Regedit STG with the task manager (TaskMan) of your phone and reboot. That’s it. Your phone is now totally application unlocked.
nah, application unlock is not CID unlock.
by the way, if you are a personal user, Hard-SPL is free for you, if you got any issues with using the Hard-SPL, you can always ask in the Hard-SPL thread.
this is like something SIM unlock ? or w
Following the unlock thread using method quoted below I eventually managed to unlock my samsung galaxy mini to all networks, however to newbies (me at the time) it was quite hard to follow. Also seemed that pulling the bml5 file all seemed like an unneccessary waste of time. I decided to unlock another sgm using method described below. However, I tried something different to look at the hex code within the file. Simply downloaded hex editor from android market (free) and jumped to the line where I'd found my own code and there it was!
Guys, just seems a little easier than using adb/terminal emulator to pull/push files between computer and phone when a lot of people may not have the competence or time to install adb shell etc etc. Any more views on this?
Of course phone must be rooted and sometimes the bml5 files isn't where they are supposed to be (different ROM's) and also it should be reminded that if you are using a custom mod (i.e. CM7 like me) you will be highly unlikely to be able to unlock the phone using the code you just found without first reverting back to stock rom. So back up your rom and data, flash back to 2.3.4 or whatever, unlock the phone and voila! Also, I will stress that you shouldn't be worried that once you have unlocked it and you decide to restore back to cm7 (or another preffered ROM), your phone SHOULD STILL BE UNLOCKED. I've had no issues with this. The hardest part is finding the right hex code line in the first place, but when you do find it, it should be 8 digits long (thats the right number isn't it?), it will be at the very end of the line on the right in its own separate little box, with blank spaces above it (no numbers/letters) and some more code underneath, but the code is in very plain view (you will know when you've found it)! Good luck!
At the end of the day, using hex editor on my phone saved me 20-30 mins (more for others perhaps) on unlocking the phone so I felt the need to share it!
Hope I've helped a few folks here. =)
Originally Posted by hexio
The bml5 method worked like a charm here. I'm writing to confirm it because the stl5 method bricked my first phone, which needed to be replaced, but with this new method everything went fine and I could unlock my (new) phone.
I used a slight variation to the methods explained here that might be of use to other Linux users like myself, so I'll explain it here. But all the credit goes to tweakradje, of course. Many thanks!
Phone details: Galaxy Europa (i5500) with stock Android 2.2 purchased recently.
PC details: Laptop with Ubuntu 11.04
Connection details: Standard wireless connection (wifi)
Steps:
1) Root the phone: I used Universal Androot
2) Install a SSH server from the market. I installed SSHDroid which is free (with ads)
3) Turn the phone into flight mode (not sure if necessary but I did it)
4) Turn on the ssh daemon with SSHDroid, allow root permissions.
5) Turn the wireless connection on and connect to the router, note the access details.
Now in the computer, connected to the same router.
6) Open a terminal, connect to the phone through SSH as root.
7) Once connected, run the command: cat /dev/bml5 > /sdcard/bml5.img
8) Copy the file to the computer. I used scp (copy over ssh) but any other method is good.
9) Use vi to view the file in the laptop.
10) Change to hexadecimal mode by pressing ESC :%!xxd
11) Press / and then enter the pattern ffff ffff ffff 3030 3030 3030
The code is there (8 digits) followed by 3 other sets of zeros.
Good luck!
Click to expand...
Click to collapse
Fraser1978 said:
Following the unlock thread using method quoted below I eventually managed to unlock my samsung galaxy mini to all networks, however to newbies (me at the time) it was quite hard to follow. Also seemed that pulling the bml5 file all seemed like an unneccessary waste of time. I decided to unlock another sgm using method described below. However, I tried something different to look at the hex code within the file. Simply downloaded hex editor from android market (free) and jumped to the line where I'd found my own code and there it was!
Guys, just seems a little easier than using adb/terminal emulator to pull/push files between computer and phone when a lot of people may not have the competence or time to install adb shell etc etc. Any more views on this?
Of course phone must be rooted and sometimes the bml5 files isn't where they are supposed to be (different ROM's) and also it should be reminded that if you are using a custom mod (i.e. CM7 like me) you will be highly unlikely to be able to unlock the phone using the code you just found without first reverting back to stock rom. So back up your rom and data, flash back to 2.3.4 or whatever, unlock the phone and voila! Also, I will stress that you shouldn't be worried that once you have unlocked it and you decide to restore back to cm7 (or another preffered ROM), your phone SHOULD STILL BE UNLOCKED. I've had no issues with this. The hardest part is finding the right hex code line in the first place, but when you do find it, it should be 8 digits long (thats the right number isn't it?), it will be at the very end of the line on the right in its own separate little box, with blank spaces above it (no numbers/letters) and some more code underneath, but the code is in very plain view (you will know when you've found it)! Good luck!
At the end of the day, using hex editor on my phone saved me 20-30 mins (more for others perhaps) on unlocking the phone so I felt the need to share it!
Hope I've helped a few folks here. =)
Click to expand...
Click to collapse
hi there does this really work for samsung europa?
albo_king said:
hi there does this really work for samsung europa?
Click to expand...
Click to collapse
Hey...Yes, as far as I am aware this method works perfectly for galaxy europa i5500
Good luck!
Fraser1978 said:
Hey...Yes, as far as I am aware this method works perfectly for galaxy europa i5500
Good luck!
Click to expand...
Click to collapse
so i need to root my phone first bro?
I have a Hero CDMA phone that was purchased from a Canadian carrier. I have confirmed that the CID is the proper one for the carrier. However, I did a factory (##786#) reset on the phone, and now the lockscreen is showing "Cellular South" as the banner on the lockscreen. I tried changing roms to Zero Sense, and, although it is in a different place on the screen, it still says Cellular South. I take it that cellular south was where my carrier got the phones from originally. There is no RUU available for my carrier.
Before I did the reset, I was able to edit the banner with QPST and have it show up properly on the phone. My previous banner still shows with QPST, but the lockscreen won't change from "Cellular South".
So, I used to be able to edit my banner, but after the reset, I now can't. I read somewhere that the HeroC only has 9 spaces for Banners, but this Banner is 14 and I can't figure out where it is stored to edit it. I have tried looking at some xml files, like eri.xml and the HTC lockscreen files, and it is not in the normal places. There are some places that come up as "CellSouth" (9 spaces) in nvram, but none that can find that say "Cellular South" Obviously the phone must getting the information from somewhere. I thought it might have been an image file, not a text, but when it showed up in a different place with the Zero rom, that theory went for a nosedive.
If anyone has any idea where the information on the banner is stored, or any way to get it back to being able to be edited, I would appreciate it.
I also have an Alltel phone, and I did the same reset on it, and it also now has a locked Cellular South banner but I thought that was just because it was a US phone.
I am on Cellular South and always have to change my carrier from Sprint.
The first thing I do is look in my original build.prop from my original nandroid and change the build.prop I'm going to flash. This prevents the market from having a "Sprint" tab. The only two brand related things I change are:
ro.product.brand=sprint to ro.product.brand=cellular_south
ro.com.google.clientidbase=android-sprint-us to ro.com.google.clientidbase=android-htc or = android-google-us
ro.cdma.home.operator.alpha=Sprint is the same.
Then you need to add eri.xml to /data. I have always had to do a factory reset, then push eri.xml to data in recovery before reboot. There was one time where I got it to work without a factory reset, but I don't remember exactly how.
Here's a link to a zip file you can flash in recovery. You need to go into the zip file with 7-zip or such and edit "Cellular South" to whatever you want the lockscreen to say. This zip file will push eri.xml to /data.
http://dl.dropbox.com/u/6585247/Update_eri.xml.zip
Here is just the eri.xml. Change "Cellular South" to your carrier and you can just push it to /data.
http://dl.dropbox.com/u/6585247/eri.xml
Thanks. I do appreciate the response.
I went into recovery and did a factory reset there, and then I tried to edit the file and push it to data using these commands.
adb remount
adb push eri.xml /data/
adb reboot
Unfortunately, the screen still reads "No Service" when it first starts and is connecting with a tower, followed by "Cellular South".
I pulled my eri.xml file and it is much different, No where in it does it say "Cellular South" and it is a much bigger file than the one you linked.
Obviously, the phone is getting the "no service" and "Cellular South" lines from somewhere. I am still at a loss to find out where.
What rom are you running?
Sent from my HERO200 using XDA App
I have tried both fresh and Zero (latest of each). Both are the same. With the Fresh, "Cellular South" is in the lockbar that you slide up to open the phone. With the Zero it is at the top of the screen, above the lockring that you slide up.
I tried flashing an Alltel RUU and also a Sprint RUU hoping to get an editable screen back, but neither would flash as I got a Carrier/Customer ID error. I know I can Super CID the phone, but I don't want to do that as I don't know whether a new RUU will fix anything, and the phone is tied to the carrier that I use. Unfortunately they don't provide ruu for their phones.
Murrfk said:
I tried flashing an Alltel RUU and also a Sprint RUU hoping to get an editable screen back, but neither would flash as I got a Carrier/Customer ID error. I know I can Super CID the phone, but I don't want to do that as I don't know whether a new RUU will fix anything, and the phone is tied to the carrier that I use. Unfortunately they don't provide ruu for their phones.
Click to expand...
Click to collapse
I dont know about all that. When you flash zero hero or most of these other roms, your carrier should pop up as sprint. I'm not sure what all you've changed or not changed. Pushing eri.xml into /data after a factory reset should change your lockscreen.
have you looked here?
http://shipped-roms.com/index.php?category=android
Well. This is interesting. I flashed Cyanogen Rom, and Deck Rom, and they both show Sprint on the lock screen. So this seems to be related to the Sense Roms. But I do want to run a sense Rom.
I hadn't done anything to the phone. I just did a full factory reset ##786# and lost my standard screen. This happened twice now.
Found a memory location
I have found "Cellular South" at memory location 10BA4C61. I am going to try editing that memory location and see whether the banner changes.
Well I found that the I could change the lockscreen if I edited that location (it was actually at 10BA4820) but the change would not survive a reboot.
The actual banner that I want is recorded correctly at nvram item 0071, but I cannot find "Cellular South" in any nvram value.
I also found that if I do a requestnvitemread banner, the banner I want shows up, rather than "Cellular South"
I found it. It is in nvram memory item 8042. Edit that file and it should change the Banner!
Tested and that works! Solved!