Hello, I currently have an unlocked HTC One X from at & t.
The 2.20 update does not show up when I check for updates, nor by itself. Ive changed the time and still nothing.
I downloaded the RUU Rom from HTCs website and when prompted to erase everything and update an error shows up stating the baterry is below 30%. The battery was at 97% and ive tried in different computers with different charges.
If i factory reset will it remove the unlock? (Sim - unlock, currently using an Argentine carrier)
You need to run the RUU in the bootloader, with you phone plugged into your computer, and make sure you have HTC sync installed. Then once you in the bootloader run the RUU from your computer. It will only work if your bootloader is locked though.
Sent from my HTC One X using xda premium
thealexx09 said:
Hello, I currently have an unlocked HTC One X from at & t.
The 2.20 update does not show up when I check for updates, nor by itself. Ive changed the time and still nothing.
I downloaded the RUU Rom from HTCs website and when prompted to erase everything and update an error shows up stating the baterry is below 30%. The battery was at 97% and ive tried in different computers with different charges.
If i factory reset will it remove the unlock? (Sim - unlock, currently using an Argentine carrier)
Click to expand...
Click to collapse
I had the same issue with a brand new HOX and had to factory restore in order to get the OTA to work.
Related
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
Hello,
I cannot post this on the Developer forum, but maybe someone here could answer it.
My phone is stuck in a bootloop for a long time, Everything I tried has failed, (safemode, factory reset, clear storage, back to RUU), I cannot even complete the initial setup, the device resets itself before setting the WiFi network, did not even get to the Google account setup.
I contacted HTC support and they are willing to fix the phone, but first I need to change the bootloader back to Locked before I send my phone to HTC center.
I cannot use this method because the device resets too fast
http://forum.xda-developers.com/showthread.php?t=1970252
same here: http://forum.xda-developers.com/showthread.php?t=1710033
anyone has an idea/solution?
Thanks, Nir
Dude first of all you don't post in development thread... This is q and a for a reason. Why would you think to post in development?
Now to resolve your problem the reason you can't run the ruu is because for the ruu to work you need to have your bootloader locked. To lock your bootloader connect your phone to the computer. And go into hboot
On the computer open cmd... (in fast boot folder) and type
Fastboot oem lock
This will lock your bootloader then run the ruu don't send it to HTC most likely there will be a cost involved.
Also you need to download the right ruu for your phone, the right ruu depends on :
What country are you in
What radio u have (or hboot forgot which)
What your carrier is
Sent from my HTC One S using xda premium
thanks mate
k1llacanon said:
Dude first of all you don't post in development thread... This is q and a for a reason. Why would you think to post in development?
Now to resolve your problem the reason you can't run the ruu is because for the ruu to work you need to have your bootloader locked. To lock your bootloader connect your phone to the computer. And go into hboot
On the computer open cmd... (in fast boot folder) and type
Fastboot oem lock
This will lock your bootloader then run the ruu don't send it to HTC most likely there will be a cost involved.
Also you need to download the right ruu for your phone, the right ruu depends on :
What country are you in
What radio u have (or hboot forgot which)
What your carrier is
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I am from Israel, but the device is EU version (France).
HBOOT 1.14.0002
Radio 1.06es.50.02.31
I thought topics such as Unlock/root etc are more related to the developer forum, but yes, you are right, this forum is the place to post this question..
my phone is now in "Relocked" state, and I did manage to restore the RUU to it.
but yet, it keeps reseting itself, I cannot complete the initial setup.
what I was thinking is if there is anyway of changing it back to "Locked" so I could send it to HTC,
but probably no, since it is impossible to switch it so "S-OFF", what do you think?
Nirosss said:
I am from Israel, but the device is EU version (France).
HBOOT 1.14.0002
Radio 1.06es.50.02.31
I thought topics such as Unlock/root etc are more related to the developer forum, but yes, you are right, this forum is the place to post this question..
my phone is now in "Relocked" state, and I did manage to restore the RUU to it.
but yet, it keeps reseting itself, I cannot complete the initial setup.
what I was thinking is if there is anyway of changing it back to "Locked" so I could send it to HTC,
but probably no, since it is impossible to switch it so "S-OFF", what do you think?
Click to expand...
Click to collapse
What do you mean it keeps resetting itself? And what initial set up?
If your bootloader is on re locked now it should have been successful. Did you use football's ruu?
Sent from my HTC One S using xda premium
The bootloader now shows "relocked"
I used the EU version RUU, now I managed to get it working, and updated it to the latest ROM using the OTA update.
On initial setup I mean the language setting and the Google account configuration on the first time you start the device, or after factory reset.
Sent from my HTC One S using xda app-developers app
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
tlazarus said:
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s :
- you don't need to root your phone to add apn . I can add T-Mobile apn just fine after I flashed ruu.
- ruu.exe can't run if you bootloader is unlocked.
Sent from my HTC One X using XDA Premium HD app
tritran18518 said:
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s : you don't need to root your phone to add apn .
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks - that answers my RUU questions as far as going back to stock using RUUs. I assume the same applies to other carrier's RUUs, i.e. Telus/Asia. What about using an OTA on a phone with Super-CID?
redpoint73 said:
A factory reset or running the RUU will not change the CID.
SuperCID doesn't prevent you from getting the AT&T OTA (although root and unlocked bootloader will).
Click to expand...
Click to collapse
^^
jiggamanjb said:
^^
Click to expand...
Click to collapse
Okay, I think that answers my questions. No problems with using a RUU, AT&T or otherwise, as long as it is for the XL. Stuck on my current radio unless I use a RUU. And I need to relock my bootloader before applying a RUU, although I can unlock it after. I will lose root, however. Thanks!
Hello,
i got two Htc one x devices. i wanted to upgrade both to latest firmware 3.18
im outside of at&t so i am using RUU.
with one of the devices it works perfectly
with the other i got stuck in the sending screen
The device is on stock 1.85 firmware (4.0.3 android) , bootloader is "Locked" and S-ON
tried again the same via fastboot and again got stuck on sending
so i decided to root the device in order to flash it with OTA update
i tried two methods : using xFaction xploit which it failed when trying to execute "pwn" file
and http://forum.xda-developers.com/showthread.php?t=1644167 where it hangs on trying to push busybox
also it seems that adb sometimes think my phone is offline while it's on "charging only mode" and then i have to disconnect it and reconnect it
and it works fine when on "hard disk mode"
Any help is greatly appreciated
Thanks
kazabubu666 said:
Hello,
i got two Htc one x devices. i wanted to upgrade both to latest firmware 3.18
im outside of at&t so i am using RUU.
with one of the devices it works perfectly
with the other i got stuck in the sending screen
The device is on stock 1.85 firmware (4.0.3 android) , bootloader is "Locked" and S-ON
tried again the same via fastboot and again got stuck on sending
so i decided to root the device in order to flash it with OTA update
i tried two methods : using xFaction xploit which it failed when trying to execute "pwn" file
and http://forum.xda-developers.com/showthread.php?t=1644167 where it hangs on trying to push busybox
also it seems that adb sometimes think my phone is offline while it's on "charging only mode" and then i have to disconnect it and reconnect it
and it works fine when on "hard disk mode"
Any help is greatly appreciated
Thanks
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=1952426&highlight=hasoon
kazabubu666 said:
The device is on stock 1.85 firmware (4.0.3 android) , bootloader is "Locked" and S-ON
[snip]
i tried two methods : using xFaction xploit which it failed when trying to execute "pwn" file
and http://forum.xda-developers.com/showthread.php?t=1644167 where it hangs on trying to push busybox.
Click to expand...
Click to collapse
FuzzyAcorns said:
Try this http://forum.xda-developers.com/showthread.php?t=1952426&highlight=hasoon
Click to expand...
Click to collapse
Both of those methods are incorrect for 1.85. The first is for 1.73 and 1.82 only, the second is for 2.20. You want this one:
http://forum.xda-developers.com/showthread.php?t=1709296
thank you all, i will try and let you know
btw, will my device stay sim unlocked after factory reset?
kazabubu666 said:
btw, will my device stay sim unlocked after factory reset?
Click to expand...
Click to collapse
None of this has anything to do with sim unlocking. It won't affect it.
kazabubu666 said:
Hello,
i got two Htc one x devices. i wanted to upgrade both to latest firmware 3.18
im outside of at&t so i am using RUU.
with one of the devices it works perfectly
with the other i got stuck in the sending screen
The device is on stock 1.85 firmware (4.0.3 android) , bootloader is "Locked" and S-ON
tried again the same via fastboot and again got stuck on sending
so i decided to root the device in order to flash it with OTA update
i tried two methods : using xFaction xploit which it failed when trying to execute "pwn" file
and http://forum.xda-developers.com/showthread.php?t=1644167 where it hangs on trying to push busybox
also it seems that adb sometimes think my phone is offline while it's on "charging only mode" and then i have to disconnect it and reconnect it
and it works fine when on "hard disk mode"
Any help is greatly appreciated
Thanks
Click to expand...
Click to collapse
When I had that issue I went to another PC and ran the RUU , it then went through
Palmetto_X said:
When I had that issue I went to another PC and ran the RUU , it then went through
Click to expand...
Click to collapse
ran it from another computer, and it solved the problem!!!!!
thank you so much, can't believe how much time i have spent on this
and i had that thought crossing my mind, just thinking why would it be different since i managed to upgrade one of my devices
in that computer
For some reason I am still having this issue. I have tried on multiple computers to no avail! It generally gets past the bootloader stage and then goes back to "sending" and then fails out. I am currently running the latest Viper ROM. Any ideas?
Hi there, well I screwed up my root and wanted to install a RUU to root my One S (S3) again. I tried it locked, unlocked, in bootloader, in fastboot.. simply everything.
I downloaded several RUUs but all of them show me the same Error 120 and say my battery isn't charged up tu 30% which is
complete bulls***!
So I ask you, where is the Problem and how do I fix it?