Hi all,
I got an HTC one S (ville S4) that used to be a branded phone for TMO Germany. Assuming there was no SIM lock (or that it would be removed by changing OS), I flashed CM 11 on it and now want to use it with Orange PL. Telephony and messaging is working just fine, but mobile data refuses to work.
Here is a list of what I did:
Confirmed APN settings
Checked with different SIM of same provider - same result
Checked with same SIM in different phone (galaxy s3) - worked like a charm
Tried with TMO PL SIM in ville S4 - worked like a charm
Checked endless forum entries to no avail - either I am not knowledgable enough or links are broken or the issue described is slightly different
Made radio logs for ville s4 with Orange PL SIM and with TMO PL SIM - I can supply the relevant parts - generally though I hoped it would tell me something, but it doesn't really do that...
In short, I think I might have a SIM lock still in place which messes up my phone. I found a guide on how to remove SIM lock, but for this, I would need to be on stock. I found some links to RUUs, but most of them seem to be borken, and I generally do not know which is appropriate.
Questions:
Is there a way to remove a potentially left over SIM lock without making changes to the general setup I have atm?
Can somebody please supply a stock RUU for my phone? Would the one below listed below work?
Thank you so much!
Best wishes,
Friedrich
Added information on phone and RUU I found:
Phone:
Tampered/Unlocked
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO_1.15.50.05.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
RUU name:
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
Hi all - is there really anyone who is able and/or willing to help? Is it a lack of background info? If you tell me what you need, I'll happily supply it.
Thank you all!
Friedrich
Falkenfink said:
Hi all,
I got an HTC one S (ville S4) that used to be a branded phone for TMO Germany. Assuming there was no SIM lock (or that it would be removed by changing OS), I flashed CM 11 on it and now want to use it with Orange PL. Telephony and messaging is working just fine, but mobile data refuses to work.
Here is a list of what I did:
Confirmed APN settings
Checked with different SIM of same provider - same result
Checked with same SIM in different phone (galaxy s3) - worked like a charm
Tried with TMO PL SIM in ville S4 - worked like a charm
Checked endless forum entries to no avail - either I am not knowledgable enough or links are broken or the issue described is slightly different
Made radio logs for ville s4 with Orange PL SIM and with TMO PL SIM - I can supply the relevant parts - generally though I hoped it would tell me something, but it doesn't really do that...
In short, I think I might have a SIM lock still in place which messes up my phone. I found a guide on how to remove SIM lock, but for this, I would need to be on stock. I found some links to RUUs, but most of them seem to be borken, and I generally do not know which is appropriate.
Questions:
Is there a way to remove a potentially left over SIM lock without making changes to the general setup I have atm?
Can somebody please supply a stock RUU for my phone? Would the one below listed below work?
Thank you so much!
Best wishes,
Friedrich
Added information on phone and RUU I found:
Phone:
Tampered/Unlocked
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO_1.15.50.05.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
RUU name:
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
Click to expand...
Click to collapse
Falkenfink said:
Hi all - is there really anyone who is able and/or willing to help? Is it a lack of background info? If you tell me what you need, I'll happily supply it.
Thank you all!
Friedrich
Click to expand...
Click to collapse
Your problem seems to be very specific. Thats probably why you get no answers. Your phone was TMO branded, means the radio is TMO version too. The solution could be to S-OFF your phone and flash unbranded EU firmware including radio.
LS.xD said:
Your problem seems to be very specific. Thats probably why you get no answers. Your phone was TMO branded, means the radio is TMO version too. The solution could be to S-OFF your phone and flash unbranded EU firmware including radio.
Click to expand...
Click to collapse
Hi LS.xD,
Thanks for taking the time to reply! Very much appreciated!
I was already thinking about flashing different radio and S-OFF the phone. However, none of the guides I found for achieving S-OFF seemed to apply for me as I felt some prerequisites weren't met by my specific case. Do you happen to have experiencing with S-OFF'ing a HTC ONE S?
If S-OFF wouldn't work - is there another chance to get another radio version and/or firmware installed?
Thanks again!
Friedrich
Falkenfink said:
Hi LS.xD,
Thanks for taking the time to reply! Very much appreciated!
I was already thinking about flashing different radio and S-OFF the phone. However, none of the guides I found for achieving S-OFF seemed to apply for me as I felt some prerequisites weren't met by my specific case. Do you happen to have experiencing with S-OFF'ing a HTC ONE S?
If S-OFF wouldn't work - is there another chance to get another radio version and/or firmware installed?
Thanks again!
Friedrich
Click to expand...
Click to collapse
Try flashing a stock RUU or sense based rom. Then use rumrunner.us to gain S-OFF.
LS.xD said:
Try flashing a stock RUU or sense based rom. Then use rumrunner.us to gain S-OFF.
Click to expand...
Click to collapse
Howdy! So I went back at this and, oh boy, did that work.
I tried some roms and ended up with MIUI from here. Ironically internet worked without problem using this ROM...
I then followed all instructions from rumrunner and it worked like a charm. Fast boot is hidden away in a different place though on MIUI and I can also confirm that on Ubuntu 14.04 64-Bit rumrunner is working despite being not supported.
All that just in case someone else will have the problem too.
Now I am trying to figure out how to install new firmware and / or change my CID from t_MOB101 - but I guess I'll manage eventually...
Thanks for the help so far!
Falkenfink said:
Howdy! So I went back at this and, oh boy, did that work.
I tried some roms and ended up with MIUI from here. Ironically internet worked without problem using this ROM...
I then followed all instructions from rumrunner and it worked like a charm. Fast boot is hidden away in a different place though on MIUI and I can also confirm that on Ubuntu 14.04 64-Bit rumrunner is working despite being not supported.
All that just in case someone else will have the problem too.
Now I am trying to figure out how to install new firmware and / or change my CID from t_MOB101 - but I guess I'll manage eventually...
Thanks for the help so far!
Click to expand...
Click to collapse
Changing CID:
fastboot oem writecid HTC__001
[HTC__001 is unbranded Europe]
LS.xD said:
Changing CID:
fastboot oem writecid HTC__001
[HTC__001 is unbranded Europe]
Click to expand...
Click to collapse
Thanks for the super-quick reply! Trying to apply this, however, doesn't seem to work for me.
I am in Fastboot Mode USB (there were tampered/unlocked is written on top etc.) I copy/paste the command into terminal and all I get is <waiting for device>. Am I simply in the wrong spot for this?
Falkenfink said:
Thanks for the super-quick reply! Trying to apply this, however, doesn't seem to work for me.
I am in Fastboot Mode USB (there were tampered/unlocked is written on top etc.) I copy/paste the command into terminal and all I get is <waiting for device>. Am I simply in the wrong spot for this?
Click to expand...
Click to collapse
type:
fastboot devices
If everything is right your device will be listed, otherwise you'll have to reconnect it.
Are you still running Linux? Fastboot must be executed as "root" or with "sudo" prefix
LS.xD said:
type:
fastboot devices
If everything is right your device will be listed, otherwise you'll have to reconnect it.
Are you still running Linux? Fastboot must be executed as "root" or with "sudo" prefix
Click to expand...
Click to collapse
Yes, I noticed... I flashed boot.img so many times with S-ON. I tried a couple of times and then simply used "sudo fastboot reboot-bootloader" to check if there is anything at all. After that it just worked with "fastboot oem writecid HTC__001" - upon rebooting another time into bootloader, now all is shiny! I still think the better explanation for this is that I did do some stupid mistake, but well...
Thank you so much! Just so you know: you helped me fix something that was bugging me since Christmas! So _really_ appreciate the help!
And with proper CID internet is working too! F**K YEAH!
Falkenfink said:
Yes, I noticed... I flashed boot.img so many times with S-ON. I tried a couple of times and then simply used "sudo fastboot reboot-bootloader" to check if there is anything at all. After that it just worked with "fastboot oem writecid HTC__001" - upon rebooting another time into bootloader, now all is shiny! I still think the better explanation for this is that I did do some stupid mistake, but well...
Thank you so much! Just so you know: you helped me fix something that was bugging me since Christmas! So _really_ appreciate the help!
And with proper CID internet is working too! F**K YEAH!
Click to expand...
Click to collapse
Stock firmware EU can be found HERE (contains also radio)
I use radio 1.20
If you need to bring your phone back to stock you can use this RUU
Related
Hi all,
I have tired to flash the new Rom yesterday and during checking the signature device reboot and installer said that it can not proceed.
After reboot phone goes directly into fastboot and gives ***Locked*** with Security Warning massage. I have tried different RUU but it is exactly the same.
Installation is failing on the checking signature.
I have tried Unrevoked3 but it is not able to find the device. Could you please let me know how to do it?
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-2822.10.0804_M
eMMC-boot
I was trying to upload RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_234765_signed
http://forum.xda-developers.com/search.php?searchid=23896455
Error nr 141?
LE: hope it works now, if not search the forum, the link reffers to the search results.
You will certainly get the answer there.
Link does not work:
Sorry - no matches. Please try some different terms.
I have tried to find an answer but no luck so far, I am quite new to this. Is there anyone who can point me in the right direction?
Another solution is to try the RUU 2.10.401.8
I had some problems with the same Ruu, but not with the signature, and the previous version worked flawlesly.
What's your CID?
Sent from my HTC Desire S
I have tried few others RUU and every single of them is falling during the installation.
ok I manage to unlock the device finally
But again it is falling during the installation of a new ROM. Do I have to revert back Hboot to 0.98 before installation? if so how to do it?
So the RUU that I recommended completed successfully?
What do you want to do next?
Now you are S-ON, if you want to install custom roms you have to unlock your bootloader with the htcdev method(you will lose your warranty and need to flag manually the boot file) or to downgrade.
Sent from my Samsung Galaxy Tab
I want to downgrade the phone to orginal ROM T-mobile uk. So I could take off the simlock, I have put the unlocking code yesterday but nothing happens. I was advised to downgrade the rom and should be ok.
Could some help me out with my problem please when ever I am trying to upload new rom it is stuck on signature verification.
I will quote Enigmaamit as he said it better than me:
enigmaamit said:
SIM unlock and bootloader unlock are two completely different things.
Click to expand...
Click to collapse
The only way to SIM-unlock your phone yourself is a XTC clip... better ask your phone operator.
I know the diffrance between those two, I have ordered unlocking code. After putting this into device when ever I put into new sim card it stoped nofifing me about it. But it is not able to find a new network. Below what I have receive form operator:
"It said "Successful" but nothing has happened
Darren
posted this on Apr 11 16:22
This has happened to a handful of customers who have all had one thing in common - the phones have been "rooted".
By rooting a handset the owner has removed some of the restrictions on the phone, which allows the owner to install whichever software of the phone that they wish. Unfortunately this has caused some issues when an unlock code has been entered.
It is easily rectified by reinstalling the original operating system that the phone was supplied with, then applying the unlock code and the phone should be unlocked, truly, successfully.
You can then reinstall the software you had on the phone before attempting the unlock and continue using the phone as you wish."
So that is the reason why I am trying to revert any changes.
i for one don't believe this
So their replay is bull**** in that case?
In my opinion yes(i can't say that i am a very experienced user) but i like to think i know some stuff about this.
I can't imagine what custom rom/Ruu version/app will "block" you to sim unlock your phone.
The only restrictions may be made by the phone manufacturer.
So i will try through HTC Clip in that case. But why I can upload any new RUU?
like i said earlier, i had some problems to with the 2.10.401.9 ruu.
Try the 2.10.401.8 it should work, if your phone is branded try a gold card.
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
hey everyone, i had my telstra one xl on JB for awhile then i wanted to do the newest update from them so upon reading up on it i need to have supercid and s-off, so i thought no worries i'll check my cid first which was telst001 (or something like that), found a one click script and changed to the supercid, so it was 11111111, sweet now to do s-off which failed to flash the RUU, i needed to relock the bootloader, so i relocked it.
problem is now its stuck in a bootloop to fastboot and wont show up in ADB devices, i also cant get into twrp in recovery now.
is there any way to fix this or throw the phone out?
It's a bit difficult to make out what you're saying in parts of that post.
Was s-off successful?
Was the RUU successful?
Which RUU did you use?
What are your current bootloader details?
Sent from my Evita
sirus17 said:
so i thought no worries i'll check my cid first which was telst001 (or something like that), found a one click script and changed to the supercid, so it was 11111111,
Click to expand...
Click to collapse
Did you actually verify that you had SuperCID? I don't think there is a one-click for the Telstra version. The one-click app for SuperCID I'm aware of is intended for AT&T, and will fail with any other CID.
Which may actually be a good thing (if SuperCID failed). Since if a Jellybean RUU is flashed with SuperCID and s-on (its not clear whether you were successful with s-off) it will pretty much a guaranteed brick.
sirus17 said:
is there any way to fix this or throw the phone out?
Click to expand...
Click to collapse
If the screen comes on, its probably possible to recover. But we need more info as timmaaa indicated above.
There is actually a one-click tool for the Telstra version, I stumbled across it very soon after getting my phone mid last year. I found it on an Australian Android site, I think it was Ausdroid.
I'm not sure whether the tool is specifically for the Telstra version alone, but it definitely works on Telstra Evitas as I used it on my fiance's Evita (and mine which is a Hong Kong model).
Sent from my Evita
I thought the one click tool here supported AT&T, Rogers and Telstra CID changing.
twistedddx said:
I thought the one click tool here supported AT&T, Rogers and Telstra CID changing.
Click to expand...
Click to collapse
Really not sure, now that I look into it more. If its the old one by DesignGears, it does work with Rogers, but doesn't seem to mention Telstra (at least if I just search the thread for "Telstra"): http://forum.xda-developers.com/showthread.php?t=1672284
And x-factor also fails for any CID except AT&T, if I understand correctly. So it seems these scripts all look for certain CIDs, so if its not explicitly included, they will fail. Of course, if there is one made specifically for Telstra (as timmaaa mentioned) it apparently wasn't posted on XDA.
But really my main point is that the OP needs to verify and be clear on this, as well as several other factors.
Hello everyone.
I am new to this part of the forum for i just received a somewhat non working AT&T HTC ONE XL from a friend.
I presume he did not read much into his issue at the time and messed up this phone one way or the other.
Basically the phone works, just not as a phone.
So i will take my time to explain the whole situation with as much detail as possible.
I am personally familiar with rooting, setting up recovery and installing custom roms on android phones (just not on this model yet).
The phone details in its current state are:
- android version 4.0.4
- htc sense version 4.0
- software number cleanrom 4.5 beta2
- htc extension version htcextension_403_1_ga_20
- kernel 3.0.8-01564-gdc95f45
- baseband 0.16.32.09.01_3_10.79.32.08L
As soon as i received the phone, i contacted at&t to ask for an unlocking code, they gladly oblige.
I insert the new SIM card (non AT&T) and the phone asks me to insert the code. After correctly inserting it, the phone accepts the code and proceeds to reboot. After the reboot i get the phone locked screen again and asks me for the code one more time.
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
So at this point i am open for ideas.
I'm positive the issue is not very hard to solve but i also know that i am missing the original recovery. I can only guess no official updates were installed so the phone was running the original 4.0.4 version.
Meanwhile i will be scouting this forum on how this phone exactly works for i understood that there were two forms of recoveries for it (one full and one partial).
I still don't know the recovery version, if it's good, how to access it (different combinations of volume and power pressing didn't work for me).
Finally your opinion on how to make the phone unlocking code work, as in would i need to go back to official, or would a custom different rom work as a solution.
Wish you guys a good day and awaiting your feedback.
Cheers.
Need more info. Boot into bootloader by holding down both the volume down rocker and the power button. After the power button is held for a few seconds, you should see the capacitive buttons flash a few times, and the phone will reboot. Let go of the power button, but DO NOT let go of the volume down rocker until the while hboot screen comes up. When you see the hboot screen, tell us what it says.
In particular, we need to know if it says s-off or s-on, if it says CID 11111111, and hboot version. Also, if it says LOCKED, UNLOCKED, or RELOCKED.
Official RUU will not run if the bootloader is UNLOCKED (needs to be RELOCKED or LOCKED). But be aware, if the phone is superCID and s-on, running a Jellybean RUU or OTA will brick the phone. Which is one of the reasons we need the bootloader info.
RUU does not need to have stock recovery to run, only OTA does. My guess is your bootloader is unlocked, or its the wrong RUU. Any error message when the RUU fails (if so, what does it say)?
Hi, thank you for your quick reply.
I'm going to write down all that is written in the recovery for i still don't understand what locked or unlocked means, s-on or s-off.
anyway, here goes:
tampered
unlocked
evita pvt ship s-on rl
hboot-1.09.0000
radio-0.16.32.09.01_3
opendsp-v25.1.0.32.0405
emmc-boot
i can't find anything related to cid and i'm still not used to this recovery just yet. wouldn't want to press anything just yet.
i hope i gave enough info and i guess it doesn't look too good just yet.
thank you again for your help.
you should remind me to reduce the use of "just yet".
i'm doing some more reading about superCID and S-on or S-off.
I understand there's a utility from this thread that could determine the supercid status.
http://forum.xda-developers.com/showthread.php?t=1672284
again i'd like to point out i have no clue what has been done to this phone so i am trying to handle it with as much care as possible in order not to brick it.
in case superCID is 1111111 and naturally i don't have the original CID, where would that leave me?
As i am understanding slowly how this phone works, if the previous user managed to install a custom rom and a custom recovery on it, would only make sense to assume the superCID has been modified? (i'll be running the tool shortly unless someone jumps and says NOOOOOOOOO don't do it!!!)
I also noticed the teamwin recovery installed is 2.1.8.1
next is understanding what s-on and s-off are all about.
i have a feeling my chances of reverting to stock firmware are slimming. this is quite a complicated phone, nice challenge.
i'm going to point out again what my main problem is: i can't unlock the sim using the code provided by at&t since as soon as the phone reboots it asks me again. so i don't mind whichever route to take, whether custom or stock, as long as i can unlock the sim the simple way.
cheers.
srasiroslayer said:
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
Click to expand...
Click to collapse
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
srasiroslayer said:
i have a feeling my chances of reverting to stock firmware are slimming.
Click to expand...
Click to collapse
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
redpoint73 said:
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
Click to expand...
Click to collapse
Wunderbar,
Thank you again for clarifying things up.
I've been taking this time to read more about this phone on this thread:
- http://forum.xda-developers.com/showthread.php?t=1671237
So i am starting to understand how it works.
i have to admit that i should consider myself lucky for if the phone had a locked bootloader, it would've been bricked.
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Cheers
srasiroslayer said:
Wunderbar,
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
Click to expand...
Click to collapse
You don't need a Linux environment to get fastboot/adb working. And you will need them if you want to get s-off or change the CID (which would be the solutions to your problem of running the RUU).
To get fastboot/adb going, I'd suggest you start here: http://forum.xda-developers.com/showthread.php?t=1754018
There are some apps what will read the phone's state including CID. Others here have mentioned the name of one (or more) such app, but I can't recall, and I don't use it. I'm used to using fastboot.
srasiroslayer said:
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Click to expand...
Click to collapse
Not sure. Going back to stock might help. Its all I can think of. But don't be disappointed if it still doesn't work.
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
My question is, shouldn't i have the original CID number?
and another off topic point, i have no clue what s-on or s-off are.
i'll get into that reading mode again in a bit.
Thank you again, i feel i'm on the right track now and confident.
Cheers
P.S.: do you need me to post the "fastboot getvar all" results? or only thing missing to be sure of was the CID?
Hang on, you're s-on and SuperCID, don't run the RUU or you'll brick your phone. You need to do some reading and research all this before you try these things.
Sent from my Evita
Guys I am Vivek Rajput, from India. I have AT&T HTC oneX. Anything related to internet is not working except whatsapp. Every app is showing network error msg. Showing some data here which i got after reading here. Assume me complete novice about software/cellphones.
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.320911_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
Have you checked your APNs?
Sent from my Evita
srasiroslayer said:
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
Click to expand...
Click to collapse
If you are going to s-off, you DO NOT want to change the CID. SuperCID (11111111) is needed to s-off.
As mentioned, make sure you s-off before RUU, or you will brick.
Once you are s-off, it shouldn't matter whether you lock the bootloader or not. S-off means all security checks are bypassed, including the check for bootloader lock.
srasiroslayer said:
and another off topic point, i have no clue what s-on or s-off are.
Click to expand...
Click to collapse
s-off, as mentioned above means all security checks are off. There are good and bad points to this.
The good, is that you will be safe of the SuperCID + RUU brick condition. Custom ROMs will also be easier to flash, if you are interested in doing that (do not need to flash boot.img separately).
The bad of s-off, is that because all security checks are off, there are no safety checks to prevent you from flashing the wrong things. You have to be very careful you don't flash something that is not intended for the device, as it may brick the phone.
Are you are okay with that, then proceed with s-off. If not, the alternate solution is to change the CID back to the proper AT&T CID (cws__001). This will also prevent the SuperCID + RUU brick condition. But may make the phone harder to s-off in the future, if you later choose that route.
It looks like then that the s-off route is the one to take, since i will definitely in the future be interested in flashing custom roms.
And it looks relatively easy as per:
http://forum.xda-developers.com/showthread.php?t=2155071
After doing some reading, it also looks safe to achieve s-off on custom roms such as my case.
I'm still reading if s-off will work on my bootloader version or if there are any specific versions to run it at. (so far no mention so good)
I'm guessing i will run s-off today and if everything works out as it should will post my results here.
Only then will i proceed to run the RUU which i downloaded from htc for the at&t model specifically (no chance i could go wrong with that).
Thank you for all the help, i honestly don't think i would've found my way around easily without guidance.
Cheers
Yes, the s-off method is easy, and it should work on any hboot version.
Good luck.
Could just having S-off fix my sim locked issue?
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
srasiroslayer said:
Could just having S-off fix my sim locked issue?
Click to expand...
Click to collapse
I doubt it. SIM lock and s-off are not related, to my knowledge.
srasiroslayer said:
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
Click to expand...
Click to collapse
Once you are s-off, all security and safety checks are off by definition. As long as you are running an RUU meant for EVITA, you will be safe, and it should run properly.
Looks like i got the 99 error thing.
at first i had the error 92 and all was working good but after the final reboot didn't get s-off
the second try i'm getting error 99.
I'm going to read more into it.
I'm still s-on so.......
So here are the current updates.
As i mentioned in the previous post, running it the first time resulted in error 92 which is normal, followed instructions and didn't get s-off.
second time i had error 99. still no s-off.
I turn off the device and power it back on, run the script all over again with a real good attention and precision (i usually don't f*ck things up).
This time i get the error 92 again and still no success at the end. (did this over 4 times now and no s-off).
would i be logical for me to assume that once the rom is booted it's messed up somewhere? hence the last part of the script not working and also hence sim unlock not working?
what's a good custom rom that would i could install using recovery and not brick my phone?
maybe just installing one would solve all my issues.
Cheers
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
timmaaa said:
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
Click to expand...
Click to collapse
Hi,
I'm trying it on CleanROM 4.5 beta2.
And by best rom in my case was asking one that would be compatible with my situation, as in hboot 1.0.9, teamwin 2.1.8.1 recovery, supercid, unlocked, s-on.
Cheers.
Hello guys,
I think my sensation xe is simlocked to T-Mobile. I have bought it off ebay and had returned it to the seller for repairing the camera. The seller has apparently fixed the issue but when i insert my sim card it does not connect to network and gives error 'your sim card does not allow connection to this network'. I have tried the settings inside phone information(*#*#4636#*#*) and also the sim unlock guide method 1 and 2. But it still does not connect. I think that the sim unlock method failed due to Hboot v 1.29. My device info is as follows
PYRAMID PVT SHIP S-OFF RL
Hboot-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Is there any was to unlock this phone? Any help would be awesome...
Thanks!
ushmal said:
Hello guys,
I think my sensation xe is simlocked to T-Mobile. I have bought it off ebay and had returned it to the seller for repairing the camera. The seller has apparently fixed the issue but when i insert my sim card it does not connect to network and gives error 'your sim card does not allow connection to this network'. I have tried the settings inside phone information(*#*#4636#*#*) and also the sim unlock guide method 1 and 2. But it still does not connect. I think that the sim unlock method failed due to Hboot v 1.29. My device info is as follows
PYRAMID PVT SHIP S-OFF RL
Hboot-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Is there any was to unlock this phone? Any help would be awesome...
Thanks!
Click to expand...
Click to collapse
Does your phone ask for pin? Usually phones with sim lock don't do that and you'll get the warning that the sim card can't be used.
Maybe try to manually select the network in settings.
No good...
Sajito said:
Does your phone ask for pin? Usually phones with sim lock don't do that and you'll get the warning that the sim card can't be used.
Maybe try to manually select the network in settings.
Click to expand...
Click to collapse
Nope...no pin request...
I even tried this guys thread...http://forum.xda-developers.com/showthread.php?t=2597778&page=2... My mobile also shows TMOB010 below the IMEI during the unlock method...but even after downgrading the firmware and erasing S58 data...upgrading to 3.33 and flashing a new rom, the phone still does not connect... and by the way, TMOB010 is still there...
ushmal said:
Nope...no pin request...
I even tried this guys thread...http://forum.xda-developers.com/showthread.php?t=2597778&page=2... My mobile also shows TMOB010 below the IMEI during the unlock method...but even after downgrading the firmware and erasing S58 data...upgrading to 3.33 and flashing a new rom, the phone still does not connect... and by the way, TMOB010 is still there...
Click to expand...
Click to collapse
Then I'm sorry, I have no clue...
One guy had the same problem and as far as I know he fixed it with hboot downgrade, PB file again, then hboot upgrade and stock ARHD (not TMOB).
Search a bit, it wasn't long time ago.
EDIT:
Take a look here:
http://forum.xda-developers.com/showpost.php?p=27813767&postcount=531
and here:
http://forum.xda-developers.com/showthread.php?t=2597778&page=2
nlooooo said:
One guy had the same problem and as far as I know he fixed it with hboot downgrade, PB file again, then hboot upgrade and stock ARHD (not TMOB).
Search a bit, it wasn't long time ago.
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
Thanks, i will search a bit more, but when i downgraded the firmware to 1.17, my HBOOT will also be downgraded right.. so i already did the method you are suggesting...anyways i will look a bit more... i need all the help i can get...
thanks again for replying!
ushmal said:
Thanks, i will search a bit more, but when i downgraded the firmware to 1.17, my HBOOT will also be downgraded right.. so i already did the method you are suggesting...anyways i will look a bit more... i need all the help i can get...
thanks again for replying!
Click to expand...
Click to collapse
Try with the links I gave you, especially the second one cause that's the guy that had the same issue and solved it.
Also i had another thought... what if there is something else wrong with the phone? What if its not locked but has some other problem? This is because i have tried almost every method i could find out there. So can anybody tell me how to check if your phone is really simlocked??
nlooooo said:
One guy had the same problem and as far as I know he fixed it with hboot downgrade, PB file again, then hboot upgrade and stock ARHD (not TMOB).
Search a bit, it wasn't long time ago.
EDIT:
Take a look here:
http://forum.xda-developers.com/showpost.php?p=27813767&postcount=531
and here:
http://forum.xda-developers.com/showthread.php?t=2597778&page=2
Click to expand...
Click to collapse
I have tried methods suggested in both of these thread my friend and sadly it does not work...both go pretty much the same way....
ushmal said:
I have tried methods suggested in both of these thread my friend and sadly it does not work...both go pretty much the same way....
Click to expand...
Click to collapse
Tried to supercid before everything?
nlooooo said:
Tried to supercid before everything?
Click to expand...
Click to collapse
Ohh i forgot to mention before...the cid was already 111111 when it was delivered... so no need to supercid...
Anyways i plan to do the process all over again one more time...just to be double sure that i didnt miss anything..its getting late so maybe i will have to do it tomorrow...will report if anything good comes out of it...fingers crossed...
In the meantime if anybody has a suggestion please do share...
Thanks guys for all the support...