I have a S4 Phone branded to T-Mobile Germany (CID: T-MOB101).
I have take the Jellybean OTA update, and I'm trying to SUPERCID with the method here: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911 but without success.
So the question is:
Has anyone with T-Mobile Germany managed to SUPERCID? And with what bootloader-ROM?
yep - no problem. It was one of the early bootloaders, 1.06 or 1.09. as my device now is one year old.
rootrider said:
yep - no problem. It was one of the early bootloaders, 1.06 or 1.09. as my device now is one year old.
Click to expand...
Click to collapse
Unfortunately I have take the 3.16.111.7 OTA update with 2.15 bootloader. Every time I modify the mmcblk0p4 partition to take supercid, but after the rebooting the system recovers the original one. I supose HTC has lock something (at least for the branded phones).
I've read about your problem in one of the threads here.
You might possibly need a t-mobile DE simcard to change CID successfully according to your problem. We could try that. If you want, I could buy a prepaid one and send it to you this week. You can send it back to me afterwards.
If this won't help, you can send me your device and I'd try to s-off it with my simcard here.
Out of interest, could you tell me the first six digits of your device serial? Something like HT23FW... Settings ->Info -> Identity
rootrider said:
I've read about your problem in one of the threads here.
You might possibly need a t-mobile DE simcard to change CID successfully according to your problem. We could try that. If you want, I could buy a prepaid one and send it to you this week. You can send it back to me afterwards.
If this won't help, you can send me your device and I'd try to s-off it with my simcard here.
Out of interest, could you tell me the first six digits of your device serial? Something like HT23FW... Settings ->Info -> Identity
Click to expand...
Click to collapse
Thank you for your kindly offer. But I don't think has something to do with the sim. I think has to do with 2.15 bootloader and branded phones.
My serial is HT26BW...... The phone was came with 4.0.3. But unfortunately I didn't try to supercid early enouph.
taxtax said:
Thank you for your kindly offer. But I don't think has something to do with the sim. I think has to do with 2.15 bootloader and branded phones.
My serial is HT26BW...... The phone was came with 4.0.3. But unfortunately I didn't try to supercid early enouph.
Click to expand...
Click to collapse
So your phone was manufactured in Taiwan 2012/June/11.
This means it was basically sold with ICS. Bootloader version 2.15 came with the JB update in December last year. So this means that the preowner of that phone must have changed the device to SCID or any other CID that was able to receive the JB OTA and install it. T-Mobile DE never offered JB for it's devices so far.
To sell it he returned to the stock CID and possibly messed up the device serial. That might be a reason for your efforts don't work. So lets assume your'e on the wrong serial.
Now you should check the devices serial (IMEI) e.g. with Phone Explorer and in the Info -> Phone Identity and compare it to that one in mmcblk0p4. Else enter *#06# for checking IMEI.
--- edit
I read the OP again. How did you manage to get the JB OTA update with your CID T-MOB101?
rootrider said:
So your phone was manufactured in Taiwan 2012/June/11.
This means it was basically sold with ICS. Bootloader version 2.15 came with the JB update in December last year. So this means that the preowner of that phone must have changed the device to SCID or any other CID that was able to receive the JB OTA and install it. T-Mobile DE never offered JB for it's devices so far.
To sell it he returned to the stock CID and possibly messed up the device serial. That might be a reason for your efforts don't work. So lets assume your'e on the wrong serial.
Now you should check the devices serial (IMEI) e.g. with Phone Explorer and in the Info -> Phone Identity and compare it to that one in mmcblk0p4. Else enter *#06# for checking IMEI.
--- edit
I read the OP again. How did you manage to get the JB OTA update with your CID T-MOB101?
Click to expand...
Click to collapse
I bought the phone new in Christmas (S4 with T-MOB101 cid).
As I said it was with the 4.0.3 and the same day I taked the 4.0.4 OTA update.
At 1 February I taked the jellybean OTA update (version 3.16.111.5)
And at 28 February I taked a minor OTA update (version 3.16.111.7)
I have the OTA updates if you want them.
Thanks for your information. I am wondering about that you could get the JB OTA Update with that CID. You could still check if your IMEI is right, but I'm running out of ideas...
Related
Hi there, I currently own an HTC Desire S, the information for it is below:
Android version:
2.3.3
HTC Sense version:
2.1
Software number:
1.28.401.1
Operator name:
vodaphone UK
I haven't yet recieved the Android 2.3.5/Sense 3.0 update. I have tryed searching for updates and checking in using that checkin dial code. I'm just wondering if there's anyway to install this official update onto my phone with minimal risk? I've looked around the forums but can't find exactly what i'm looking for (or I just can't find it!).
Thanks!
I think that you have got the same software version 1.28.401.1 that I had until recently.
I would like to have used to OTA update route but basically got tired of waiting.
I believe that the OTA update was targetted (certainly at first) specifically at those people who already received the previous (troublesome) update to 1.47.
I believe this explains why we didn't get the update.
I loaded the RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed from the development section here and it works a treat. No problems.
The only thing that puzzles me is that my phone is very definitely unbranded and not operator locked, whereas you mention Vodaphone. (If your phone was locked to Vodaphone I would have expected a different software version).
Anyway, if your phone is unlocked like mine, I would certainly recommend using the RUU.
- Steve
fasty said:
I think that you have got the same software version 1.28.401.1 that I had until recently.
I would like to have used to OTA update route but basically got tired of waiting.
I believe that the OTA update was targetted (certainly at first) specifically at those people who already received the previous (troublesome) update to 1.47.
I believe this explains why we didn't get the update.
I loaded the RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed from the development section here and it works a treat. No problems.
The only thing that puzzles me is that my phone is very definitely unbranded and not operator locked, whereas you mention Vodaphone. (If your phone was locked to Vodaphone I would have expected a different software version).
Anyway, if your phone is unlocked like mine, I would certainly recommend using the RUU.
- Steve
Click to expand...
Click to collapse
Thanks very much for your reply.
Yeah, unfortunately my phone is in fact locked to Vodaphone, and I couldn't find the equivalent update that you listed for unlocked phones.
i have a vodafone as well on the same firmware and never got it.
from what i hear the update was pulled due to instability so if you didnt receive it already i very much doubt you will untill a new version is released.
i gave up waiting and went to endymion 3.5
Biogeneric said:
Yeah, unfortunately my phone is in fact locked to Vodaphone, and I couldn't find the equivalent update that you listed for unlocked phones.
Click to expand...
Click to collapse
Are you sure it's locked?!
I thought that software version was for the generic european unlocked version.
Someone else help me here - can the same software number apply to both operator locked and unlocked phones?
fasty said:
Are you sure it's locked?!
I thought that software version was for the generic european unlocked version.
Someone else help me here - can the same software number apply to both operator locked and unlocked phones?
Click to expand...
Click to collapse
i can confirm the htc euro ruu DOES NOT WORK ON VODAFONE BRANDED DEVICES. it bricked my phone and took a whole lot of work to downgrade back to the old hboot to get it working again. the only way to install this version on a voda desire s is via goldcard.it will just give you a cid error and brick your device
djisgod said:
i can confirm the htc euro ruu DOES NOT WORK ON VODAFONE BRANDED DEVICES. it bricked my phone and took a whole lot of work to downgrade back to the old hboot to get it working again. the only way to install this version on a voda desire s is via goldcard.it will just give you a cid error and brick your device
Click to expand...
Click to collapse
Completely agree, great care needed !
But my point was, the software version1.28.401.1 reported by Biogeneric appears to be the same as I had until recently on my unbranded phone.
I thought that if his phone was locked to Vodaphone, wouldn't it have a different software number? Or can the operator lock the phone to their network without changing this software version away form the "generic" one?
- Steve
I'm with Vodaphone, and it says my network is "vodaphone UK" so i'm assuming it's locked! How am I supposed to find out without putting a different networks Sim in?
Biogeneric said:
I'm with Vodaphone, and it says my network is "vodaphone UK" so i'm assuming it's locked! How am I supposed to find out without putting a different networks Sim in?
Click to expand...
Click to collapse
Mine (which recently had the same software version and in NOT operator locked) simply says the name of whatever SIM card you insert.
I suspect your phone may be unlocked, but I'd like feedback from a more experienced developer before suggesting that you load the RUU! We don't want any nasty accidents
By the way, I've just loaded RUU for 2.10.401.8 and it's looking good so far...
Okay, I tried putting in an Orange sim card and setting the network to Orange and it appears to all work (well, I had signal on it, and the network was stated as "Orange"). So i'm assuming my phone is in fact unlocked then?
If so, great news! Am I all clear to update to that unlocked version then? Anyone got a link to the newest one? (Not any mods etc. just the standard update!).
Thanks all!
Biogeneric said:
Okay, I tried putting in an Orange sim card and setting the network to Orange and it appears to all work (well, I had signal on it, and the network was stated as "Orange"). So i'm assuming my phone is in fact unlocked then?
If so, great news! Am I all clear to update to that unlocked version then? Anyone got a link to the newest one? (Not any mods etc. just the standard update!).
Thanks all!
Click to expand...
Click to collapse
I believe that the most recent RUU is RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_225161_signed.exe
in the "Shipped Desire S ROM Collection" :
http://forum.xda-developers.com/showthread.php?t=1002506
I loaded this last night and not experienced any problems so far.
Be warned that this will wipe all existing data on your phone, so make sure that you have got everything saved. In some respects, this is a good thing because you are sure of getting a completely fresh install.
I can't see any reason why this shouldn't work for you, but I wouldn't feel bad if you got a second opinion
-Steve
fasty said:
I believe that the most recent RUU is RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_225161_signed.exe
in the "Shipped Desire S ROM Collection" :
http://forum.xda-developers.com/showthread.php?t=1002506
I loaded this last night and not experienced any problems so far.
Be warned that this will wipe all existing data on your phone, so make sure that you have got everything saved. In some respects, this is a good thing because you are sure of getting a completely fresh install.
I can't see any reason why this shouldn't work for you, but I wouldn't feel bad if you got a second opinion
-Steve
Click to expand...
Click to collapse
Okay thanks very much! I'll try updating it via that ROM tonight - hopefully I won't brick it!
Does anyone know if updating the phone using this method voids the warranty?
Also, how do I actually install that update to my phone? Seen a few tutorials scattared around but some are for different things and I don't want to mess it up! (Easiest/quickest method please, if there is one ha!)
Thanks a lot for your help Steve!
Biogeneric said:
Okay thanks very much! I'll try updating it via that ROM tonight - hopefully I won't brick it!
Does anyone know if updating the phone using this method voids the warranty?
Also, how do I actually install that update to my phone? Seen a few tutorials scattared around but some are for different things and I don't want to mess it up! (Easiest/quickest method please, if there is one ha!)
Thanks a lot for your help Steve!
Click to expand...
Click to collapse
I expect that doing almost anything other than the "official" OTA update theoretically voids warranty. But perhaps more important, if it all went horribly wrong, could anyone detect that you were fiddling with it
If you returned a phone rooted or S-off, then it's asking for trouble.
The discussed RUU is a signed update that does not invoke S-off or root the phone so should not create an "obvious" problem.
The way I updated my phone was as follows:
- I already had HTC Sync installed on my PC
- Fully charged phone
- Downloaded the RUU file to folder on hard disk
- Temporarily disabled my antivirus
- Temporarily disabled standby power saving option on PC
- Connected the phone as normal and selected the option on phone to do Sync
- I let the phone completely finish sync
- I ran the RUU on the PC and followed the simple instructions.
- It took about 10 minutes with no user intervention required.
I don't know if the whole HTC Sync thing is necessary, it was on my PC anyway and the procedure has worked OK for me.
I can now confirm this has all worked for me. no problems so far!
Thanks for all your help fasty! Very much appreciated.
Biogeneric said:
I can now confirm this has all worked for me. no problems so far!
D
Click to expand...
Click to collapse
Great news! Be sure to thank "Football" because he is the one that has done the hard work making these ROMs available.
Hi not sure if posting in correct thread but I am on O2 and also have the 1.28.401.1 software and just been informed by HTC my phone is unbranded despite coming straight from O2. Has anyone received the update whilst being on 1.28.401.1? Am i wasting my time holding out for an OTA update?
RUU
Sent from my HTC Desire S using xda premium
Hi!!
I just got a Desire S, i' am new to rooting... so i need to know whether i can go back to the stock ROM (2.3.3 with sense 2.1) after i root the device.
This is the only dilemma holding me back from rooting my desire s.
Thank you for your Time! : )
To root your phone you have to S-OFF (turning off security that prevents you to flash system components) first.
You can do this with Revolutionary
This procedure will change your bootloader to a modified one.
To keep the possibility to go back S-ON and Stock you should flash this hboot and when the time comes to restore the system with a RUU with your current version (that can be checked in Settings - About phone - Software information)
A lot of useful info here, all the necessary files and guides here
Thanks a lot for the info!!
But one problem though, my Baseband Version is: 20.28I.30.085AU_3805.06.02.03_M and Software number is: 1.47.111.3 .
I searched thoroughly in the link (RUU) u posted above, but i didn't find the matching RUU.
rusor123 said:
Thanks a lot for the info!!
But one problem though, my Baseband Version is: 20.28I.30.085AU_3805.06.02.03_M and Software number is: 1.47.111.3 .
I searched thoroughly in the link (RUU) u posted above, but i didn't find the matching RUU.
Click to expand...
Click to collapse
Let me guess - when you power on your device you have the T-Mobile logo
Your current software version is higher then the T-Mobile RUU provided here (RUU_Saga_TMO_DE_1.30.111.1_Radio_20.28b.30.0805U_3 8.03.02.11_M_release), so to restore Stock you will have to downgrade and then update via the Software actualization option in your settings (if such OTA is available) to return it to the current state. This is more tricky process, that can be done flawlessly if your device is healthy. But if you get in trouble and some system components are not responding (brick, bootloop) there is a great change that you will be not able to S-ON again. Happened to a lot of branded devices, reported here.
So my advice is to keep using it that way - it is still a great phone even with Stock software. You can S-OFF and root it of course at your own risk.
It is up to you
Dude you are right man... the T-mobile sign does come up, thanks for the heads up, appreciate it... don't want to brick ma phone... i' ll keep using it this way.
Another small question- do u know why the t- mobile logo is showing up during boot? i just got the phone brand new, and T-mobile isn't operating in my country. The box and the manuals in German, does it mean it's a refurbished phone?
And the phone also doesn't get software update, such as sense 3.0.
rusor123 said:
Another small question- do u know why the t- mobile logo is showing up during boot? i just got the phone brand new, and T-mobile isn't operating in my country. The box and the manuals in German, does it mean it's a refurbished phone?
And the phone also doesn't get software update, such as sense 3.0.
Click to expand...
Click to collapse
The logo means that your phone is branded for T-Mobile. So better ask the operator/shop that you got it for more details. For me is quite strange since this mobile carrier is not operating in your country branded phones to be sold there
As for the Sense 3.0 update it depends on the operators. Probably T-Mobile will release one but when - do not know.
Anyway if there is a chance to replace your device for an unbranded one this will be the best thing to do.
amidabuddha said:
To root your phone you have to S-OFF (turning off security that prevents you to flash system components) first.
You can do this with Revolutionary
This procedure will change your bootloader to a modified one.
To keep the possibility to go back S-ON and Stock you should flash this hboot and when the time comes to restore the system with a RUU with your current version (that can be checked in Settings - About phone - Software information)
A lot of useful info here, all the necessary files and guides here
Click to expand...
Click to collapse
thnx!!!!!!!!!!!
amidabuddha said:
The logo means that your phone is branded for T-Mobile. So better ask the operator/shop that you got it for more details. For me is quite strange since this mobile carrier is not operating in your country branded phones to be sold there
As for the Sense 3.0 update it depends on the operators. Probably T-Mobile will release one but when - do not know.
Anyway if there is a chance to replace your device for an unbranded one this will be the best thing to do.
Click to expand...
Click to collapse
Is it likely that i' ll be getting a OTA update from T-mobile, since the phone's from Germany and i live in an Asian Country?
rusor123 said:
Is it likely that i' ll be getting a OTA update from T-mobile, since the phone's from Germany and i live in an Asian Country?
Click to expand...
Click to collapse
Yes you should receive the update, because the update check from your phone settings is made on a central server (both on WiFi and Mobile data, the phone connects to the same place in the Internet)
amidabuddha said:
To root your phone you have to S-OFF (turning off security that prevents you to flash system components) first.
You can do this with Revolutionary
This procedure will change your bootloader to a modified one.
To keep the possibility to go back S-ON and Stock you should flash this hboot and when the time comes to restore the system with a RUU with your current version (that can be checked in Settings - About phone - Software information)
A lot of useful info here, all the necessary files and guides here
Click to expand...
Click to collapse
hey im kinda a noob so what u said means i can or not, i have a desire s and i cant wait for the sense 3.0 update so if i download a custom rom for now, and when the official update comes in my region can i go back to the stock android then update it normally??????
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
Ive been trying to find out why my phone (with the 2.21 RUU currently installed) wont receive OTA's
The bootloader is relocked and it has the stock recovery, so it should work
Ive been reading a lot of posts (more ore less about this) some are hinting that RUU's dont give OTA's
Does anyone have a definitive answer, does a RUU get OTA's or not?
Thanks
Lacuna666 said:
Ive been trying to find out why my phone (with the 2.21 RUU currently installed) wont receive OTA's
The bootloader is relocked and it has the stock recovery, so it should work
Ive been reading a lot of posts (more ore less about this) some are hinting that RUU's dont give OTA's
Does anyone have a definitive answer, does a RUU get OTA's or not?
Thanks
Click to expand...
Click to collapse
Yes RUU are stock HTC roms. It's like a super factory reset. But you can only receive an OTA if the region your phone is in offers an OTA. More specifically if there is an OTA offered to CID that your phone has.
dc211 said:
Yes RUU are stock HTC roms. It's like a super factory reset. But you can only receive an OTA if the region your phone is in offers an OTA. More specifically if there is an OTA offered to CID that your phone has.
Click to expand...
Click to collapse
OK, thanks, that was exactly the kind of info i needed !
Check the build number on the phone.
If there is a r2 behind it then you wont get the update since there are ni developed paths from a r2 to something else.
M9x3mos said:
Check the build number on the phone.
If there is a r2 behind it then you wont get the update since there are ni developed paths from a r2 to something else.
Click to expand...
Click to collapse
Thanks fo the info, i allready now have a ruu 2.31 installe which DOES get ota's, but if i run into this problem again, i'll check that !
Or type
*#*#CHECKIN#*#* into the dialer. Then check for updates.
Sent from my locked, tampered ville
I bought a One S for my Mom on eBay to replace her water-damaged S2 - the listing said factory sealed, unlocked, brand new.
Dropped Bell Canada SIM card in, worked well for 2 months.
After a Bell OTA update, phone will not maintain a signal.
Bell looked up IMEI, said the phone belonged to Fido and was unlocked and activated by Rogers.
Ran Root Checker to see if it was rooted - sure enough, it had been rooted and I have the "this device does not have proper root access".
So I've been forced to try and figure this out, and I'd like to restore the phone to stock - I've read cbetso's great "Restore to Stock" post and looked through the AIO toolkit, but I don't know which "RUU to run". Fido? Rogers? Bell? Do I even need it? Everyone's issue seems very personal and specific to their carrier / etc. and I'd like to restore it.
Thanks.
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Telling by the software version it runs the Fido software. You would have to run a Fido RUU, but if you want to change it to unbranded HTC software you can change CID to HTC__001 and then run an unbranded RUU such as 2.31.401.5 (latest, Android 4.0.4 RUU)
usaff22 said:
Telling by the software version it runs the Fido software. You would have to run a Fido RUU, but if you want to change it to unbranded HTC software you can change CID to HTC__001 and then run an unbranded RUU such as 2.31.401.5 (latest, Android 4.0.4 RUU)
Click to expand...
Click to collapse
Thanks again. I have an unlock code for the device; my hope was to restore it back to the way it came from Fido and SIM unlock it for use with another carrier. I suppose I'll try the step-by-step process listed in the "restore" post I mentioned. After trying to figure this out for the past week, I truly appreciate the work of developers here in the forum.
So I've located an RUU for Rogers (which covers Fido in Canada, apparently) but it's for a 1.70 build. The one currently on the device, I believe is higher than that. I'd like to try the All in One Toolkit to bring the phone back to stock and then unlock it for use with Bell or Telus. If I run the Toolkit, and use cbetso's instructions from the "How to Return to Stock" post (after adding the stock recovery to the folder) - can I run the 1.70 Rogers RUU without issues? Thanks for the advice!
tykidd66 said:
So I've located an RUU for Rogers (which covers Fido in Canada, apparently) but it's for a 1.70 build. The one currently on the device, I believe is higher than that. I'd like to try the All in One Toolkit to bring the phone back to stock and then unlock it for use with Bell or Telus. If I run the Toolkit, and use cbetso's instructions from the "How to Return to Stock" post (after adding the stock recovery to the folder) - can I run the 1.70 Rogers RUU without issues? Thanks for the advice!
Click to expand...
Click to collapse
If you are on a higher software version than the RUU, unfortunately it's not possible unless you downgrade your HBOOT which is risky for people who are new to the whole unlock/root thing. If the software version is the same or less, go ahead.
usaff22 said:
If you are on a higher software version than the RUU, unfortunately it's not possible unless you downgrade your HBOOT which is risky for people who are new to the whole unlock/root thing. If the software version is the same or less, go ahead.
Click to expand...
Click to collapse
Thanks. I'm not new, I'm COMPLETELY new. Maybe I'll have to wait until the higher version come out for Rogers. Right now I have a virtually unusable phone, and although I don't know what I'm doing, I'd still like to try and get it back to stock. Can you point me in the direction of a good downgrade tutorial? I've looked around a bit but haven't seen anything I trust. Much appreciated.