Database Info

Method to downgrade and unlock Docomo HT-03A

This method is what I used to unlock my 1.6 Docomo HT-03A. Please don't hold me responsible for any issues you have. I typed this up really quickly as a reference for other NOOBS like myself so that you don't have to scour the board. I don't know where you got your unlock code from, but if you have one, you may follow these steps to get your device unlocked.
* - Note: If you are running Docomo's Donut ROM (1.6) then when you insert your non-Docomo sim, you will NOT BE PROMPTED to enter your NCK (network unlock PIN). These steps are necessary to get back to 1.5 so that you can get the unlock PIN entry prompt.
Before this process your FASTBOOT screen should look like this:
SAPPHIRE EVT1 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP20000)
CPLD-10
RADIO-2.22.19.261
May 27 2009,19:06:41
1. Install Android SDK. On windows it's just a folder. From the TOOLS folder, copy Adb.exe, AdbWinApi.dll, and fastboot.exe to C:\windows\system32\. Next rename the SDK folder to something convenient and place it at C:\XXX where XXX is por... where XXX is whatever your SDK folder is called.
2. Make sure ADB is installed correctly. Once you think it is, open a command prompt and type:
adb devices
You should get something under "List of devices attached". If not, your drivers are not correctly installed.
3. Using a Micro SD make a Goldcard. I used the video here.
3.5. Download and install any 32B rom your heart desires, and copy it to the root of your SD card (your goldcard); this will be used later.
4. Fix your Perfect SPL. The docomo SPL is HBOOT-1.33.0006 (SAPP20000). Go ahead and follow Amon_RA's steps here.
Use the Engineers SPL on that page (ROM v2.53.707.2 (Engineerings SPL v1.33.2010) - MD5 : F9674D19BE5F949D0D9DC99714D210E3).
5. Boot the phone normally, and if you have a non-Docomo sim to insert AND you have your unlock code, you may now enter it the the device will be unlocked forever, yay!
6. Turn off the device and check your FASTBOOT (BACK+END) screen; it should look like this:
SAPPHIRE EVT1 32B ENG S-OFF H
HBOOT-1.33.2005 (SAPP20000)
CPLD-10
RADIO-3.22.20.17
Apr 20 2009,15:30:43
Note that the device is rev EVT1 32B ENG S-OFF H: a 32B model with board rev. EVT1, ENG = engineering version SPL, S-OFF = security off (simlock off?), and H for HTC.
Note that Amon_Ra's G-type recovery images WILL NOT work at this point.
This H and the radio below are for 32A devices, which leads us to step 7.
7. Revert to 32B radio and G recovery. Steps found here under the section "Revert to 32B Radio and ROM". The radio can be found here.
Code:
fastboot flash radio radio.img
Press menu to POWER OFF. Then re-enter FASTBOOT (BACK+END) and check that the radio has been reverted.
Code:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-RAv1.2.0G.img
*** - Note that instead of recovery-RAv1.2.0G.img, you may use the newer recovery-RA-sapphire-v1.6.2G.img instead.
8. Press MENU to POWER OFF. Hold HOME+END to boot into recovery mode.
9. Install update from zip inside recovery mode.
10. Reboot or allow the device to reboot and enjoy your device.
edit: My FASTBOOT screen still has SAPPHIRE EVT1 32B ENG S-OFF H instead of SAPPHIRE EVT1 32B ENG S-OFF G. I wonder if I can just change my SPL back to the original Docomo ship one or if there is some ENG SPL S-OFF G available somewhere?

Credit goes to Amon_RA and all others who contributed in his work. This thread is just a quick guide for others in my situation.
I was able to get the device up and running smoothly after a little bit of a eureka moment from reading this post.

I've been trying to fix my SPL for a while now. I have a Docomo phone, same fastboot info as yours.
Every time I try to update with a sappimg.zip/nbh, i get a
Model ID Incorrect!
Update Fail!
message. This is both before -and- after I created a goldcard, no change whatsoever.
I've tried making the goldcard in winXP with HxD, in Ubuntu with 'dd', checked my CID about 4 times, and used 5-6 different sappimg's, both zip and nbh, including the one you listed in your instructions.
I've used a few different SD cards, including Kingston, SanDisk, and Toshiba, and all of them read just fine on my PC after the goldcard creation.
I've just about racked my brain for any solution. Every answer I've seen to my error message is "make a goldcard". Every answer for "my goldcard isn't working" is "make it again and make sure you can read it with your PC".
So, basically, I've got about 30 tabs open in 4 FireFox windows, lots of threads, all with the same info, most linking back to each other across 4 forums.
Really, all I'm asking is this: What could I have missed? It seems simple enough, honestly, but it's just not working. Any ideas?

Geobot said:
I've been trying to fix my SPL for a while now. I have a Docomo phone, same fastboot info as yours.
Every time I try to update with a sappimg.zip/nbh, i get a
Model ID Incorrect!
Update Fail!
message. This is both before -and- after I created a goldcard, no change whatsoever.
I've tried making the goldcard in winXP with HxD, in Ubuntu with 'dd', checked my CID about 4 times, and used 5-6 different sappimg's, both zip and nbh, including the one you listed in your instructions.
I've used a few different SD cards, including Kingston, SanDisk, and Toshiba, and all of them read just fine on my PC after the goldcard creation.
I've just about racked my brain for any solution. Every answer I've seen to my error message is "make a goldcard". Every answer for "my goldcard isn't working" is "make it again and make sure you can read it with your PC".
So, basically, I've got about 30 tabs open in 4 FireFox windows, lots of threads, all with the same info, most linking back to each other across 4 forums.
Really, all I'm asking is this: What could I have missed? It seems simple enough, honestly, but it's just not working. Any ideas?
Click to expand...
Click to collapse
Your either applying the goldcard.img to the logical drive rather then Physical...
Not formattng the card to FAt first...
You cant use the same CID for different sd cards
Rename the Sappimg to SAPPIMG.zip

Well, it seems I'm an idiot after all. Thank you crypysmoker, I had my list of CIDs going to the wrong cards. Updated just fine once I sorted that out. Thanks for the reply ^^

Geobot said:
Well, it seems I'm an idiot after all. Thank you crypysmoker, I had my list of CIDs going to the wrong cards. Updated just fine once I sorted that out. Thanks for the reply ^^
Click to expand...
Click to collapse
lol.. When I first rooted the Fender Mytouch i had your same problem because i had never made a gold card. i kept putting it on the logical drive.... then I kept using the same CID for 4 different cards. Then once i found out what I was doing, It was all back to the first card I used lol
Glad I could help

[Q] Help please.... limited service after rom install

can anyone help with this problem as its doing my head in lol ive flashed loads of roms and flashed the ics rom which i have done before but this time for some reason i have LIMITED SERVICE so installed official stock europe ruu rom and still LIMITED SERVICE can anyone help please...

Have ou flashed an ics base/firmware ( like 3.24,3.25,3.30 and 3.30) before to flash the ics rom?

no i didn`t is there a way to fix this?

just checked and my bootloader now says LOCKED and i unlocked it a few days ago from htc website

desperate for help now as i can`t even fastboot root or run revolutionary to get unlocked again and when i use htc official bootloader unlock it allows me to get to the unlock screen where it says up/down to unlock bootloader but only lets me enter the no for don`t unlock as when i try to select unlock bootloader the power button doesn`t do anything help

Locked can be becuase you have flashed a 3.25 firmware non-unlocked
It says locked but is only for fastboot command, the rest in unlocked
So my question is: have you flashed 3.24/25 firmware?
I don't understand why you have unlocked it with htcdev method...

i used RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe

erto90 said:
So my question is: have you flashed 3.24/25 firmware?
Click to expand...
Click to collapse
Also, do you have superCID? Perhaps the radio version in the ruu you ran is conflicting with your device. If you perform superCID then you can flash any ruu, or any firmware, and try a different radio.
HTC.dev unlock does not let you flash radio.img, so I'm sure this is why the limited service problem is occurring.
Sent from my Pyramid-T

i`m super cid 11111111 s-0ff and have managed to fastboot recovery back on to my sensation i have noticed in bootloader i now have extra features such as MFG KERNEL? my HBOOT is 1.17.2008 just flashed a custom rom ARHD which installed but still limited service and the option to turn on mobile networks isnt highlighted so can`t switch on data services?

karaduke said:
i`m super cid 11111111 s-0ff and have managed to fastboot recovery back on to my sensation i have noticed in bootloader i now have extra features such as MFG KERNEL? my HBOOT is 1.17.2008 just flashed a custom rom ARHD which installed but still limited service and the option to turn on mobile networks isnt highlighted so can`t switch on data services?
Click to expand...
Click to collapse
OK, you have the engineering hboot there. It should just be a case of updating the firmware (and hence hboot) to whatever the rom requires.
Check the firmware/partitions info in dev forum.
Sent from my Pyramid-T

tried everything now and stuck on what to do??? managed to download voda uk firmware from filecrop which took about 2hrs to download grrr can i send this back to voda and say the signal has gone??

ARHD recommends 3.32 firmware plus ext4 recovery. Try flashing both these (links in the rom thread) to see if it helps.
If not, run appropriate ruu, replicate the problem on stock rom, then by all means send it in!
Sent from my Pyramid-T

Been trying all day and still no joy. Think i have figured out why i have limited service and think its because my imei number has changed somehow. And don't know how it happened. Can anyone give me a tutorial on how to write my imei number back.

Read this thread, someone else had the same thing happen, lost his IMEI and it is recoverable.
http://forum.xda-developers.com/showthread.php?t=1413728
here is the solution
Originally Posted by mert72
strings -n 8 /dev/block/mmcblk0p6
this is not the only block that has your imei #. it is also stored in mmcblk0p4 and mmcblk0p5.
since you're justy trying to recover your own imei and not change it to somebody else', i'll help you out.
i've altered this guide for the blocks that store our imei.
http://pastebin.com/BFSAZkVQ
#
1) Root Phone
#
2) Install Busybox (make sure its installed properly)
#
3) Install Android Terminal Emulator
#
4) have an sd card in and type the following command;
#
#
type in "su" (without quotation marks) in android terminal emulator to gain super user access.
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/pa4.img
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/pa5.img
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/pa6.img
back these up (make a copy), just in case.
#
#
(this will copy the hidden partition to your sd card in a file called pa4,5,6.img)
#
#
5) Get a hex editor from the internet and open the file pa4,5,6.img. Locate the current imei # that you want to replace with your own imei (use the "find and replace option" of the hex editor). Change it to your personal imei #, but be aware if you change it to an actual imei of another phone you are essentially cloning that phone and will have problems.
#
#
6) Copy file back to sd card and put back in phone. Type this:
#
#
dd if=/mnt/sdcard/pa4.img of=/dev/block/mmcblk0p4 (rewrites the partition with the image file you just edited)
dd if=/mnt/sdcard/pa5.img of=/dev/block/mmcblk0p5
dd if=/mnt/sdcard/pa6.img of=/dev/block/mmcblk0p6
#
#
7) reboot and pray.
once again, this guide is only meant to help people looking to restore their own imei numbers.
p.s. i'm surprised that your phone won't pick up any signal with the changed imei, though. unless it was blacklisted by your operator, it technically wouldn't matter what imei number it is. and it is very strange that your imei would change by just flashing a firmware and a rom.
--------------------------------------------------------------------------------
Last edited by RussianBear; 21st February 2012 at 12:05 PM.

Nice one will give it a go and post back

karaduke said:
Nice one will give it a go and post back
Click to expand...
Click to collapse
read the entire thread because there was a second solution on the last page, good luck

I have tried everything i could think of and can`t go any further now i can`t even root/recovery the damn thing... it`s only about 4-5 days old so can i take it back to a vodafone store and say theres something wrong with it? will they just change it for a new one in store as its only a few days old or would they more than likely send it off for repair??

karaduke said:
I have tried everything i could think of and can`t go any further now i can`t even root/recovery the damn thing... it`s only about 4-5 days old so can i take it back to a vodafone store and say theres something wrong with it? will they just change it for a new one in store as its only a few days old or would they more than likely send it off for repair??
Click to expand...
Click to collapse
Vodafone uk give you 7 days to return and change for new or alternative handset.

i didn`t know if i should flash something on it to brick it as if they look at the mismatch imei number they might think its something ive done to the phone or should i leave it how it is...

karaduke said:
i didn`t know if i should flash something on it to brick it as if they look at the mismatch imei number they might think its something ive done to the phone or should i leave it how it is...
Click to expand...
Click to collapse
It's a tricky one. Of course, it's entirely up to you what you decide to do, but you could just take it back to store as it is and say that there is something wrong with the handset. As it is under seven days old, they may just exchange it, no questions. Also, you often find that in store, they are not so clued up on flashing, rooting etc. so would not necessarily know what has been going on. But, you may be unlucky and get someone who is clued up. If this is the case, you may want to take the phone away with you and rethink what to do. You can always take it back to a different store (if you really want to purposely brick it). Another thing you can try, is speaking to vodafone customer care, and, again, because it's a new phone, they may just send you a new one at the same time time you send the faulty one back. (Vodafone did this with a faulty Nokia N900 I had) Entirely up to you.

[Q] “Your SIM card does not allow a connection to this network”

Yes, this old chestnut.
I realise that this problem is as old as Android itself, but it actually appears to be a bunch of different problems that manifest with the same symptom. I've tried all of the solutions I can find, and none of them seem to work.
I have an Orange UK branded Desire S that I recently acquired second-hand off eBay. To begin with, everything worked fine, but the phone hadn't been updated in a while so I applied all the OTA updates (3 in total), one after the other. After the first two it was also working fine, but after the third update it stopped connecting to the Orange network.
When I attempt to connect to the Orange network manually, I get “Your SIM card does not allow a connection to this network”. When I try the same SIM in another phone, it works fine. I unlocked the phone using a code and tried a Vodafone SIM, but that didn't work either. I've tried removing the battery overnight, no luck. I searched a IMEI database to see if it was blocked, and it isn't. I've tried repeatedly switching airplane mode on/off, which doesn't help. I've tried a hard reset, through the phone menu and also via the boot menu, without success.
When I type *#*#4636#*#* to enter the service menu, I can see that the phone is receiving a signal, so the antenna's working OK.
Now here comes the odd part. When I try to change the wireless band to 'WCDMA Only', it refuses to change and stays put on 'WCDMA/GSM' mode. It doesn't matter if I use the service menu or go through the 'Mobile Networks' settings, it still refuses to change.
I'm open to the concept of flashing a custom ROM, but I don't want to invalidate any warranty I may have unless that's the only option. I'd like to try flashing an RUU, but I can't find a suitable one. The only Orange ROM in this post appears to be French language:
http://forum.xda-developers.com/showthread.php?t=1002506
Any comments would be much appreciated. Thanks in advance.

Hi,
I'm having the exact same issue with a HTC Sensation 4G (T-Mobile) on stock ICS.
I bought this second hand phone and bring it back to Venezuela. The phone worked swell with local carriers but suddenly lost signal and got the infamous “Your SIM card does not allow a connection to this network” message.
I've tried every solution posted on the net with no results, leaving rooting as the last resort.
So, before I begin rooting my phone I just wanted to ask if you found any solution to this. :fingers-crossed:
Any help would be much appreciated! :good:

So,
I've rooted my phone. used HTCdev, juopunutbear, clockworkmod, installed Superuser and got super CID. Also, I called my carrier and checked that my IMEI was not blacklisted (just to be sure).
Messing around with the hboot I found something that I'm not quite sure what it means, in the SIMLOCK menu I found this message:
FAT32 init OK
Open MCCMNC file fail
Open CID file fail
Process done, reboot device?
<vol up> Yes
I've changed the CID to the original stock and got the same message. I don't know what it means and if it is related to my problem. I'm still using the stock rom (OTA ICS 4.0.3 T-MOBILE) planning to install OrDroid 9.0.0.
I really need some guidance over here. :crying:

FDM-X said:
So,
I've rooted my phone. used HTCdev, juopunutbear, clockworkmod, installed Superuser and got super CID. Also, I called my carrier and checked that my IMEI was not blacklisted (just to be sure).
Messing around with the hboot I found something that I'm not quite sure what it means, in the SIMLOCK menu I found this message:
FAT32 init OK
Open MCCMNC file fail
Open CID file fail
Process done, reboot device?
<vol up> Yes
I've changed the CID to the original stock and got the same message. I don't know what it means and if it is related to my problem. I'm still using the stock rom (OTA ICS 4.0.3 T-MOBILE) planning to install OrDroid 9.0.0.
I really need some guidance over here. :crying:
Click to expand...
Click to collapse
Hi
I occure almost the same problem with my HTC sensation XE
did you manega to solve it?

Caelen said:
Hi
I occure almost the same problem with my HTC sensation XE
did you manega to solve it?
Click to expand...
Click to collapse
Sorry to hear that. I'm still stuck with it.
I've flashed Ordroid 9.0 and the same error appears everytime I try to get signal from any carrier.
Someone told me that I should try flashing the radios or change my IMEI but I really don't know how to do it and I'm afraid I could permanently damage my phone.
Still waiting for fresh ideas to try.

Good news! (at least for me)
After I've tried almost all to solve the issue I took the phone to my carrier to get my sim card changed. they told me that someone has reported my phone as stolen in my previous carrier. So I went to the other carrier with my proof of purchase and they unblocked my phone IMEI right away.
If by any Chance you're having this same issue make your phone checked by your carrier for any kind of locks before messing with your phone.
Hope my experience will help any of you.
Sent from my HTC Sensation Z710e using xda app-developers app

[Q] RUU downgrade - 130 - Model ID Error

The day I got my Canadian One S, I had an HTC upgrade waiting to be applied...
I was soooooo stupid to apply that, which made me Hboot 1.13 and radio 0.17...
I have rooted and s-off and all other necessary to install JB...
All went nice... I got ParanoidAndroid ROM(thanks guys, very nice job seriously) running smoothly...
However, after several days I've noticed that many people have been complaining that they can't reach me...
I've activated the operator's missed call SMS function and the result was shocking...
I was missing 70% of the calls each day... I started to track the status of the device then...
This is what I've discovered:
Network is constantly switching between 3G, H and H+...
Even if there's H on the screen, sometimes there's no connection actually.
While searching for the probable root cause of the problem, I've installed seven different ROMs, including Android 4.0.4 and 4.1.
The problem remains, so I assume ParanoidAndroid ROM works fine. I have a different problem.
I kept searching and found out that many people have similar problems but I failed to find an exact solution.
One of the articles says that it may be the radio version, which makes sense to me.
Now I'm trying to downgrade the phone since three days.
The RUU I've been trying is:
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
because I was thinking that GSM network is GSM network and so EU RUU shall work.
But the error I get is Model ID Error, coded 130; which actually tells me that I'm being stupid again because I'm using a wrong RUU.
Now, I'm very tired(really, physically tired, I don't mean that I'm bored) so I need some sleep...
Is there any guru here who may help me? What RUU is correct for my Canadian One S? I got it from Fido in Toronto but because of my work, I'm using it in Asia, in Kazakhstan.
Cheers... :silly:

erol.savas said:
The day I got my Canadian One S, I had an HTC upgrade waiting to be applied...
I was soooooo stupid to apply that, which made me Hboot 1.13 and radio 0.17...
I have rooted and s-off and all other necessary to install JB...
All went nice... I got ParanoidAndroid ROM(thanks guys, very nice job seriously) running smoothly...
However, after several days I've noticed that many people have been complaining that they can't reach me...
I've activated the operator's missed call SMS function and the result was shocking...
I was missing 70% of the calls each day... I started to track the status of the device then...
This is what I've discovered:
Network is constantly switching between 3G, H and H+...
Even if there's H on the screen, sometimes there's no connection actually.
While searching for the probable root cause of the problem, I've installed seven different ROMs, including Android 4.0.4 and 4.1.
The problem remains, so I assume ParanoidAndroid ROM works fine. I have a different problem.
I kept searching and found out that many people have similar problems but I failed to find an exact solution.
One of the articles says that it may be the radio version, which makes sense to me.
Now I'm trying to downgrade the phone since three days.
The RUU I've been trying is:
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
because I was thinking that GSM network is GSM network and so EU RUU shall work.
But the error I get is Model ID Error, coded 130; which actually tells me that I'm being stupid again because I'm using a wrong RUU.
Now, I'm very tired(really, physically tired, I don't mean that I'm bored) so I need some sleep...
Is there any guru here who may help me? What RUU is correct for my Canadian One S? I got it from Fido in Toronto but because of my work, I'm using it in Asia, in Kazakhstan.
Cheers... :silly:
Click to expand...
Click to collapse
You can change your carrier ID so you can pass the model check when using any RUU by follow the instructions at the link below. If you do change your carrier ID then you'll need to unlock your bootloader though htcdev.com after you run a RUU.
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Also, after you change to super cid keep in mind you can only run RUU's which contain the same hboot version you are currently running or a higher version. In your case hboot 1.13 or hboot 1.14.

Thanks a lot but...
dc211 said:
You can change your carrier ID so you can pass the model check when using any RUU by follow the instructions at the link below. If you do change your carrier ID then you'll need to unlock your bootloader though htcdev.com after you run a RUU.
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Also, after you change to super cid keep in mind you can only run RUU's which contain the same hboot version you are currently running or a higher version. In your case hboot 1.13 or hboot 1.14.
Click to expand...
Click to collapse
Thanks a lot.
In fact I read the CID change method but most probably because of late-night-sleepy mood, I've considered the method as brand and model specific thing. After five hours sleep, I see that it is not...
I've performed all the steps and I've succeeded to install this RUU:
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
As you have mentioned about hboot, the RUU didn't downgrade my hboot from 1.13 but it did downgrade the radio from 0.17 to 0.16. and OpenDSP from v28 to v25.
I've performed all rooting and installed CWM recovery and I've restored the backup.
I got JB back without any hassle.
However, the 3G, h and H+ switching problem still remains, which actually made me look for a solution for RUU installation.
So radio downgrade didn't help...
It's very annoying to see the network constantly switching... And I have reasons to believe that this switching is draining the battery.
Would you have any suggestions on that particular issue?
(I don't know if this is important but I since the problem is still remaining, let me mention anyway...
The geniuses in Fido, even after asking about it for three times, gave me an operator locked phone...
So when I arrived here and have inserted the KZ operator SIM, the phone got locked.
I unlocked it myself...)
Cheers

How did you S-OFF?
Sent from my locked, tampered ville

erol.savas said:
Thanks a lot.
In fact I read the CID change method but most probably because of late-night-sleepy mood, I've considered the method as brand and model specific thing. After five hours sleep, I see that it is not...
I've performed all the steps and I've succeeded to install this RUU:
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
As you have mentioned about hboot, the RUU didn't downgrade my hboot from 1.13 but it did downgrade the radio from 0.17 to 0.16. and OpenDSP from v28 to v25.
I've performed all rooting and installed CWM recovery and I've restored the backup.
I got JB back without any hassle.
However, the 3G, h and H+ switching problem still remains, which actually made me look for a solution for RUU installation.
So radio downgrade didn't help...
It's very annoying to see the network constantly switching... And I have reasons to believe that this switching is draining the battery.
Would you have any suggestions on that particular issue?
(I don't know if this is important but I since the problem is still remaining, let me mention anyway...
The geniuses in Fido, even after asking about it for three times, gave me an operator locked phone...
So when I arrived here and have inserted the KZ operator SIM, the phone got locked.
I unlocked it myself...)
Cheers
Click to expand...
Click to collapse
Glad it worked. For the network switching I think that's fast dormancy doing it's thing but your carrier has to support it. To disable it add these lines to your build.prop file.
ro.ril.fast.dormancy.rule=0
ro.ril.disable.power.collapse=1
or if those already exist change them to match above and see if that fixes it.

I'm sorry
usaff22 said:
How did you S-OFF?
Sent from my locked, tampered ville
Click to expand...
Click to collapse
I'm very sorry to alarm you; my mistake...
I have been very exhausted last night... I've mistyped few but very critical things, such as s-off.
Within my technical limits ans skills, of course no s-off...
I've corrected my signature.
Sorry again...
Cheers

Now, let me track the status
dc211 said:
Glad it worked. For the network switching I think that's fast dormancy doing it's thing but your carrier has to support it. To disable it add these lines to your build.prop file.
ro.ril.fast.dormancy.rule=0
ro.ril.disable.power.collapse=1
or if those already exist change them to match above and see if that fixes it.
Click to expand...
Click to collapse
Thanks mate.
I've added the two lines to build.prop
Even though the switching still is going on, I suspect that it is quite less dynamic than before.
Today, I'll be watching the status of data and the missed call SMS' from the operator.
I'll of course let you know the outcome tomorrow.
Cheers :good:

erol.savas said:
Thanks mate.
I've added the two lines to build.prop
Even though the switching still is going on, I suspect that it is quite less dynamic than before.
Today, I'll be watching the status of data and the missed call SMS' from the operator.
I'll of course let you know the outcome tomorrow.
Cheers :good:
Click to expand...
Click to collapse
Don't forget you gotta reboot for it to take effect.

dc211 said:
Don't forget you gotta reboot for it to take effect.
Click to expand...
Click to collapse
Yes, sure.
I've rebooted after adding those two lines.
So far it's better...

dc211 said:
Don't forget you gotta reboot for it to take effect.
Click to expand...
Click to collapse
OK, here I am...
The problem is still going on...
However... I found out something very interesting...
Yesterday I felt very upset and disappointed with the One S and bough myself a new One X...
I didn't install any HTC updates, etc... I unlocked the bootloader and installed CWM recovery...
Put my favorite ROM, the latest version of ParanoidAndroid...
Inserted the SIM card... Guess what?.. Same thing... Switching between 3G, H, H+ !...
You can't imagine how surprised and shocked I was. I started to consider burning both phones in my back yard.
But before buying some alcohol for easier burn, I've decided to check the issue with another SIM card. :cyclops:
So I've asked from one of my friends having micro-SIM to give me his SIM for 5 mins to test...
While explaining him the problem on his One X, I saw that -with another operator SIM card- his One X is in the same situation...
His One X is pure factory default, no bootloader mods, no recoveries, no custom ROM, etc...
Since he keeps the data off all the time but uses only wifi, the guy had never noticed the issue.
So I'm shocked for two times in 20 hours
Now what?.. The networks of all operators in Kazakhstan have some kind of a problem?
Or is this really a problem?...
Four days ago I was using the same operator network with my good-old HTC Desire and I haven't witnessed such issues with that one, neither with the two EVO 3Ds I have, nor with the Motorola Xoom. By the way, they're still fine... No switching issues so far...
What may the difference be between these old models and the new series?
Problematic new radio hardware or firmware HTC uses in the One series?
If this was only a switching issue, I might think that it may not be a problem actually but the phone still is dropping from the GSM network and I still receive missed call SMS from the operator...
Delays in sending SMS, etc...
What the heck is going on here?
Cheers

Should this method always work?
dc211 said:
You can change your carrier ID so you can pass the model check when using any RUU by follow the instructions at the link below. If you do change your carrier ID then you'll need to unlock your bootloader though htcdev.com after you run a RUU.
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Also, after you change to super cid keep in mind you can only run RUU's which contain the same hboot version you are currently running or a higher version. In your case hboot 1.13 or hboot 1.14.
Click to expand...
Click to collapse
Hi, I'm not able to run the RUU with this method (130 - Model ID Error). CID is 11111111, phone (One S) is unlocked by htcdev.com. The mid is PJ4020000 and I didn't find any way to change the it (fastboot oem writemid PJ4010000 doesn't work). Hboot version is 2.09. I tried to install both RUU_Ville_U_HTC_Europe_1.78.401.2 and RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5. Can anybody help me, please?

Problem because of S3 processor
jkniep said:
Hi, I'm not able to run the RUU with this method (130 - Model ID Error). CID is 11111111, phone (One S) is unlocked by htcdev.com. The mid is PJ4020000 and I didn't find any way to change the it (fastboot oem writemid PJ4010000 doesn't work). Hboot version is 2.09. I tried to install both RUU_Ville_U_HTC_Europe_1.78.401.2 and RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5. Can anybody help me, please?
Click to expand...
Click to collapse
Nevermind, I just found out that I couldn't update because I have the S3 version (which, of course, nobody at the store told me) and therefore need another RUU.

usaff22 said:
How did you S-OFF?
Sent from my locked, tampered ville
Click to expand...
Click to collapse
+1! Lol
HTC One S

[Q] Unsimlock help please

Hey everyone, My Motorola DEFY has just broken (the charging connectors in the micro USB port have completely broken, so I have got an old HTC Sensation out.
I've done S-OFF, Root, and installed CM10.1 (The latest build).
The problem is, I can't get any Unsimlock method to work..
I can use my phone without the request for the pin popping up, but otherwise I have no signal or connection.
My network is Giffgaff (UK) which uses O2 signal.
I have no connection to the network at all (for example to send messages or initiate calls/receive calls), never mind data.
I've tried the following:
Method 1 (The date showed up, so I can't unsimlock this way)
Method 2 (This one didn't work because I have 1.27 Hboot)
This method (This sort of works, I can use my phone without having to enter the network unlock pin, but I have no connection to the network).
No network connection image. This is clean CM10.1 install. S58 data has successfully cleared, but my Giffgaff sim doesn't work
Any help would be very much appreciated, thank you.

pk92 said:
Hey everyone, My Motorola DEFY has just broken (the charging connectors in the micro USB port have completely broken, so I have got an old HTC Sensation out.
I've done S-OFF, Root, and installed CM10.1 (The latest build).
The problem is, I can't get any Unsimlock method to work..
I can use my phone without the request for the pin popping up, but otherwise I have no signal or connection.
My network is Giffgaff (UK) which uses O2 signal.
I have no connection to the network at all (for example to send messages or initiate calls/receive calls), never mind data.
I've tried the following:
Method 1 (The date showed up, so I can't unsimlock this way)
Method 2 (This one didn't work because I have 1.27 Hboot)
This method (This sort of works, I can use my phone without having to enter the network unlock pin, but I have no connection to the network).
Any help would be very much appreciated, thank you.
Click to expand...
Click to collapse
You'll have to use method 2 BUT first downgrade your firmware to 1.17/18 and then flash the file. As soon as you've done that you just upgrade back to the latest firmware and voila, sim unlocked!

sy224048 said:
You'll have to use method 2 BUT first downgrade your firmware to 1.17/18 and then flash the file. As soon as you've done that you just upgrade back to the latest firmware and voila, sim unlocked!
Click to expand...
Click to collapse
That's what I tried with the 'third' method on my OP.
Install Firmware 1.17 (Firmware 1.17 Universal)
Install nbh file (PG58DIAG.nbh from here)
Install Firmware 3.32 (Firmware 3.32 Universal (Non-TMOUS))
Also tried "Firmware 3.32 unlocked hboot http://www.mediafire.com/download.php?mrynwif8cznhhvx"
I've checked the Giffgaff APN settings here and they are correct on my phone too.
Have I done anything wrong? or is there anything more I need to do?
Here's what my BL says at the moment (I've tried 3.33, didn't work :/ )
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot​
It may not be an un-sim-lock problem, but a radio problem perhaps?