Database Info

[Q] Need help rooting my friend's sensation, mine has been rooted successfully.

Ok So my friend from work wanted his sensation rooted after I did mine. He has S-OFF and has sucessfully permanently rooted it with the SU-bin 3.03 blah blah zip file. I've succesfully rooted my own with CID of 11111111 and used 4EXT recovery to install the 3.24 firmware. He, however, gets the known boot loop problem, which I know is due to firmware not being upgraded. I can't for the life of me connect his phone and have ADB connect to it to change his CID.
I've got the same exact model phone, down to the same carrier, so I have the HTC sensation USB drivers (HTC sync) installed on my pc. It won't detect it though because of it not being able to boot into android's OS.
I'm attempting to download a rom that is based off of the stock firmware hoping this will solve my problem, but wouldn't mind any insight on it.

Well, if i got it right you just need to pick a firmware flashable for that phone without supercid, am i right? In that case there's the topic where you can find all firmware adjusted to a particular CID, grab that from your phone, put into your sd (you may want to put a ROM to flash too), then put your SD with the matching firmware onto his phone, reboot and it's done! Finally swap again the SD card.

daddoso said:
Well, if i got it right you just need to pick a firmware flashable for that phone without supercid, am i right? In that case there's the topic where you can find all firmware adjusted to a particular CID, grab that from your phone, put into your sd (you may want to put a ROM to flash too), then put your SD with the matching firmware onto his phone, reboot and it's done! Finally swap again the SD card.
Click to expand...
Click to collapse
Yes I would think so, but I can't figure out what current CID he has on his phone because I can't boot up into android's OS and connect to my phone on my PC with ADB (adb devices shows up, but when I try to set the CID it wont work).

Fails to "set" or fails just the command? Because if its only a "set" issue, the command may (unlikely) work and show you the cid! Or we can try to find it out with some info like brand/country/etc ..

Figured it out, had to do with the sync cable I was using. used a different one and i was able to set the CID to 1111111 or w/e. Installed the new firmware and the silly boot loop stopped.
Sent from my Asus Transformer of The Prime Kind.

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

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

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

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

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

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

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

***LOCKED***Security Warning on bootloader

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.

[Q] Is there stock recovery for a Rogers S One with RUU 1.84?

I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.

tykidd66 said:
I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.
Click to expand...
Click to collapse
Post is a bit confusing. You talk about Bell, Rogers, and Telus all at once. Also, if you got an OTA update from Bell, you will only be able to execute an RUU that has an hboot version equal to or higher than your current one.
If you are looking for a more recent RUU than the ones posted on http://forum.xda-developers.com/showthread.php?t=1543588
then I suggest you send a private message to Football, the user who started that post. He helped me find newer Bell Mobility RUUs (which have since been posted to the thread).
Your other option is to do a bootloader downgrade (see the dev post on this, its a bit complicated), and then you can flash other radios from http://forum.xda-developers.com/showthread.php?t=1998270
If you dont want to downgrade your bootloader, you can always flash to a CM10 base (AOSP type) ROM, such as PAC Man, or Jelly Bam, etc. Then you can flash radios without having to downgrade.
Again, though this is all assuming that your true problem is with you baseband radio and now switching carriers has made your reception poor...
Also remember you will have to relock your bootloader before you execute an RUU, otherwise it wont take (that and a correct bootloader version)
AKToronto

Thanks for the info. The phone is a sim-unlocked Fido unit. It was running on Bell before the OTA update.
Here are the specs:
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
Is the "build number" the RUU? I'll try Football, but do I need the Rogers (Fido) RUU?
Thanks.

you can not execute an rogers ruu on a bell phone, the cid wont match
there is an app on play who will display you the cid and the original network; like that you'll know exactly what phone do you have in hand
you just have to unlockit after and you will be able to useit in whatever network you want

Thanks. Ran CID getter and says it's ROGER001. So I've confirmed that I need a Rogers file. And I would like to unlock it, but from what I've read I cannot restore back to Rogers 1.70 because the unit has been updated to 1.84. I have read that if I can find a 1.84 Rogers file, I can use that to restore the unit. This is the next thing I need to confirm. I appreciate your help.

I think that is almost correct. You can change the CID to the Rogers one using the same technique as posted in the super Cid thread in the development section. Normally though you can't flash an older ruu as the hboot version can't be older. But You may also want to try posting a message in the bootloader downgrade thread that is stickied to n the development section. I think if you downgrade your bootloader and also do a minor hex edit to a partition you can flash an older RUU. I have downgraded my bootloader but haven't tried flashing an older ruu so I can't say for sure.
Sent from my HTC One S using xda premium

Thanks again. So I can assume the CID is already Rogers, yes? I don't want to change it. My hope is that I can use the All in One Toolkit (one of the sticky posts) to bring the phone back to stock and then SIM unlock it for use with 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). If I locate the Rogers 1.84 RUU, can I run it without downgrading?

don't assume, your cid is rogers ROGER001, so there is absolutely no way your phone could download and execute an update from bell.
so I can not understand what has bell to do in this.
if you just want to use it on telus network, you just have to unlock it, you don't even need root for this. and the phone will work just fine.
the root is needed when you want to change ROM, radio, debloat and others.
one of the others will be tweaking the build.prop file to achieve maximum capacities of your 3g/4g desired network

Thanks - it's a difficult story to tell, really. It was a Rogers unit, SIM unlocked to work with Bell. It was on Bell's network for two months, and an OTA update caused major radio and reception problems. It will not keep a network signal anymore. I have tried other SIMs in the unit and it will not recognize them, nor start up with the "Enter Unlock Code" screen to SIM unlock it. It's my understanding that I need to return it to stock by finding the Rogers RUU file that matches the software version on the unit, which is 1.84. This is my very limited understanding of the issue, but it's what I've been able to figure out.

if it was a rogers device, and you did not change the CID, you get the ROGER001 cid with the app, your phone is still a rogers device
doesn't matter in which networks was used, for the two months before you get it, and by you after
as long the cid stays ROGER001, your phone will remain a rogers device, unlocked to be used in different networks.
so there is absolutely no way an OTA update, from bell or telus could be the source of your problems, because your phone will not download or execute an ota update from other networks
same for rogers ota update, as long the phone was unlocked, will not execute OTA updates, even the updates will be downloaded on the phone
your connection problem came from other reasons;
however it you want to return the phone to rogers stock, the key number is HBOOT version;
you can execute any RUU with HBOOT version higher or equal with your present version on the phone
if somehow you're on a very high version and you can not find the appropriate RUU, we can always downgrade RUU, check development section for tutorial
it's not very simple, but as long you're ok and you understand the steps, go for it, it is doable.
if you have root, you might try different radios before all above, or maybe a custom rom; just an ideea; as long the phone is not soft bricked or physically damaged, there is no reason a custom rom will not work

Thanks for the information. There seems to be other problems with the unit, including it won't delete all data after hard reset, it won't recognize other networks when other SIMs are put in, it has been upgraded past the 1.70 stock Rogers RUU. I wish I could get it figured out or I may have to sell it as is. Appreciate your help.

factory reset in fastboot didn't work?
means you're on some custom rom with non stock recovery?
have you tried to flash a stock recovery? any of them, whatever you'll find around here; there are no much difference in term of facilities between them;
then you should be able to restore phone to factory defaults
try find somewhere All in one kitt one S v1.0; there is stock recovery in it, and flashing is easy
in v1.1 there is no more stock recovery

donwload ruu or open up ruu..when it first starts go into your windows manager and in the link section delete what you have in that section like c:/program files and replace it with %temp% and it will find two encrypted folders with a big letter/digit name and they will show you what time they were opened . open them up and find rom.zip copy it to your desktop and then extract it somewhere safe .. in the folders in rom.zip you will see recovery_signed.img rename it recovery.img and flash it via hasoons tool kit provided in the development section..just in case you ever run into this again

Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.

tykidd66 said:
Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.
Click to expand...
Click to collapse
Not sure about your radio issue, that would require testing out different radios. You can do that on a higher hboot by trying AOSP ROMS and using the Radio flasher in the dev forums.
As for flashing stock recovery you can also just use the following link: http://loadbalancing.modaco.com/down...ery_signed.img
The stock recovery doesnt really change from RUU to RUU. You dont need a particular recovery to use a particular RUU, as far as I know.

Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?

tykidd66 said:
Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?
Click to expand...
Click to collapse
http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Try that. Sorry about the other link

I maybe miss it, but you never said what is the exact status of the phone right now;
it is booting? it is working on some network? at least partially like voice only? what ROM are you on? what HBOOT?

Hi there - thanks for getting back to me and asking. The phone seems to be booting normally and always has been. It is not able to recognize any new SIM card. It's a Rogers unit, and when I add my Telus SIM it does not go to the "Unrecognized SIM" screen, it actually registers the TELUS network for a moment, then the radio gives no signal.
How can I check the ROM, 'cause I have no idea. Is the HBOOT in these specs?
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
Thanks again.

for the Hboot version you have to reboot in fastboot
for recovery reboot into recovery
for the ROM version, once booted normaly you have to go into about phone > software
are you sure you have the right settings for Telus APN? for some reasons, the phone will not registered to network, if apn setting are wrong;
at least for me, which I'm opposite to you as I have a telus phone and using it in fido network, if I dont have Fido APN setted up, the phone does not register to network

[Q] How to install official firmware from HTC?

I have custom recovery, updated HBOOT and running CM11.
Now its time to buy new phone and sell this one.
But how to downgrade this all and install official HTC Sense? (Not some custom Sense-based ROM).
As i imagine this i need to install windows and some HTC special apps, and somehow remove recovery...

You need to provide more details. Post your bootloader details please, as well as the original CID that came on the phone. Also, questions go in the q&a section, I'll ask for this to be moved there for you.
Transmitted via Bacon

timmaaa said:
You need to provide more details. Post your bootloader details please, as well as the original CID that came on the phone. Also, questions go in the q&a section, I'll ask for this to be moved there for you.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, sorry for wrong section.
Seems original CID is lost, it will not allow to install original firmware with fake one? Or just some warranty things?
Model: One XL
Bootloader screen:

itspers said:
Thanks, sorry for wrong section.
Seems original CID is lost, it will not allow to install original firmware with fake one? Or just some warranty things?
Model: One XL
Bootloader screen:
**image removed for security**
Click to expand...
Click to collapse
Edit that image out asap, it contains your IMEI, which should never be posted publicly.
Did you not make note of the original CID before changing it? You shouldn't sell a device with SuperCID unless the buyer specifically wants a modified device and understands the dangers. Is it an at&t model? Telstra? Rogers? Hong Kong?
Transmitted via Bacon

timmaaa said:
Edit that image out asap, it contains your IMEI, which should never be posted publicly.
Did you not make note of the original CID before changing it? You shouldn't sell a device with SuperCID unless the buyer specifically wants a modified device and understands the dangers. Is it an at&t model? Telstra? Rogers? Hong Kong?
Transmitted via Bacon
Click to expand...
Click to collapse
I made a note in txt file on desktop... And thought "need to save in in some googledoc or so.."
Its At&t american, ordered from ebay to Ukraine and than i bought it in local auction site 2 years ago. For this years i lost even charger, so will sell only phone without any documents and boxes.
I made all this HBOOT and CID changes just to get CM working, what dangers this can produce?

itspers said:
I made a note in txt file on desktop... And thought "need to save in in some googledoc or so.."
Its At&t american, ordered from ebay to Ukraine and than i bought it in local auction site 2 years ago. For this years i lost even charger, so will sell only phone without any documents and boxes.
I made all this HBOOT and CID changes just to get CM working, what dangers this can produce?
Click to expand...
Click to collapse
The danger is that to return the device to stock you need to return it to being s-on, and if we weren't able to work out what the original CID was it would remain as SuperCID. Here's where the danger is, running any RUU 4.1 or above while the phone is s-on and with SuperCID will brick the phone. But, if it's an at&t device then the original CID is CWS__001. Are you wanting to return the device to fully stock at&t specs?
Transmitted via Bacon

timmaaa said:
The danger is that to return the device to stock you need to return it to being s-on, and if we weren't able to work out what the original CID was it would remain as SuperCID. Here's where the danger is, running any RUU 4.1 or above while the phone is s-on and with SuperCID will brick the phone. But, if it's an at&t device then the original CID is CWS__001. Are you wanting to return the device to fully stock at&t specs?
Transmitted via Bacon
Click to expand...
Click to collapse
I want to return it in some condition where someone who will buy this phone will not break it by trying to update from preferences.
If i will leave it as is - i need to write full list of all this changes i made with bootloader and firmware when will be selling, cause somebody will think its not unlocked, or not rooted, will try to do something and get brick. But in same time if i will write some much info - will be hard to sell it, cause 90% of people never saw clean android here, they will think its something wrong.
This is main reason to flash original firmware.
But if i will only flash original rom - in some day buyer will try to update it via HTC and get error and call me, or in worst case get some brick...
So if it possible to revert everything - please tell me some list of things to do: CID, S-OFF etc. and where to read about them on forum.

itspers said:
I want to return it in some condition where someone who will buy this phone will not break it by trying to update from preferences.
If i will leave it as is - i need to write full list of all this changes i made with bootloader and firmware when will be selling, cause somebody will think its not unlocked, or not rooted, will try to do something and get brick. But in same time if i will write some much info - will be hard to sell it, cause 90% of people never saw clean android here, they will think its something wrong.
This is main reason to flash original firmware.
But if i will only flash original rom - in some day buyer will try to update it via HTC and get error and call me, or in worst case get some brick...
So if it possible to revert everything - please tell me some list of things to do: CID, S-OFF etc. and where to read about them on forum.
Click to expand...
Click to collapse
The first thing you need to do is backup whatever personal data (images, music, etc) you have on the device to your PC.
Next go into TWRP recovery and wipe data and sd card (internal storage).
Boot the phone and make sure all of your personal data is gone.
Next you want to run the at&t 5.18 RUU:
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
After that you can return the device to the original CID:
Code:
fastboot oem writecid CWS__001
Then relock the bootloader:
Code:
fastboot oem lock
Then return the device to s-on:
Code:
fastboot oem writesecureflag 3
Now you have a fully stock device.
Transmitted via Bacon