Hi all.
I have A HTC Sensation, on Orange (UK).
The handset was completely standard, untouched. I have followed the guide to unlock my bootloader using HTC dev.
It seemingly worked, and I held volume down and pressed power and verified that the text at the top said "UNLOCKED". great
When I booted the phone, it gave me the "fresh start" intro screens, which I followed through on.
Once completed, the phone loaded to the normal home screen, but now gets no signal. Its always 0 bars and "NO SERVICE" warning.
Only thing I have done is as above, so unsure what could have gone wrong?
Only thing I can think is that I chose the wrong "what phone do you have" option on HTCDev. I chose HTC Sensation (EU), as the phone is not on tmobile, and not vodafone, and IS european. However, tmobile and orange are now part of the same umbrella company, so perhaps something bad happened there?
Unsure what I should do next? Re-lock the bootloader? Any suggestions very gratefully welcomed! Thanks
Hmm.. that's really weird. Unlocking the bootloader doesn't affect your cell phone signals. I would run a RUU and see if that fixes the problem.
Here's the guide: http://forum.xda-developers.com/showthread.php?p=26541170
Follow steps 2&3.
Before you do, try taking out your sim and putting it back in. I highly doubt you put your sim in the wrong way, but I did this before (I don't think I'm the only idiot out there)
Sent from my HTC Sensation
Thanks. I'll follow that guide.
SIM card is in OK. Was I supposed to remove the SIM when I was unlocking the bootloader? I didn't do that.
Just waiting for the RUU file to download.
The guide says I need one with a higher or equal version to my main version. My main version is 3.x and the highest version I can find via the links in the guide are 1.x. Will this be ok?
I'm really not sure how the phone got this screwed up.If I did select the incorrect device type in HTCDev (i.e. I selected Sensation EU and should have selected Sensation Tmobile) would that possibly cause this problem?
Would it be worth re-locking, then unlocking using the tmobile device? Guessing I would be supplied with a different unlock_code.bin?
EDIT: Just checked and the tmobile device choice is actually for "tmobile USA", so looking like I chose the correct device after all.
RUU I had failed. As I say my version is 3.x and this was 1.x so I'm not surprised.
My exact version reads: 3.32.61.51
Can anyone suggest a RUU file that I can have a go with, or any other suggestions?
Bootloader is currently RELOCKED.
Thanks
Did you try this ruu?
http://www.shipped-roms.com/downloa...0U_10.51.9007.27_M3_release_198549_signed.exe
EDIT: try looking for your ruu here: http://www.tsar3000.com/Joomla/inde...riginal-roms&catid=65:htc-downloads&Itemid=98
The general ROM section has 3.32 versions.
Sent from my HTC Sensation
Yes, I tried the first one you posted, which wouldnt work (too old presumably).
I will try one of the unbranded ones; but unsure if they are suitable as I have an Orange logo when I boot?
Thanks
Still waiting for the RUU to download, so will probably carry on looking at this in the morning now.
A little more info that might give someone an idea:
If i go into settings, and click on "Mobile settings" and go to choose carrier, the phone searches for carriers.
25% of the time it says "no network found"
75% of the time, it finds O2.
25% of the time it finds 3 or vodafone
It never finds orange. It seems it IS looking for networks though?
If I put the SIM card in my very old dumb-phone, it finds orange fairly quickly and connects.
Thanks for any help
There's another option. You can try to s-off your phone with ganeshp's guide and then flashing the 3.33 firmware which contains the newest radio and stuff.
Here's s-off guide without HTC dev unlock: http://forum.xda-developers.com/showthread.php?p=26280760
Here's the firmwares for sensation: http://forum.xda-developers.com/showthread.php?p=21711154
Sent from my HTC Sensation
AndroidSupporter318 said:
There's another option. You can try to s-off your phone with ganeshp's guide and then flashing the 3.33 firmware which contains the newest radio and stuff.
Here's s-off guide without HTC dev unlock: http://forum.xda-developers.com/showthread.php?p=26280760
Here's the firmwares for sensation: http://forum.xda-developers.com/showthread.php?p=21711154
Sent from my HTC Sensation
Click to expand...
Click to collapse
actuallly it is better to use auggie2k's guide because he has done htcdev unlock
But he relocked it... on the 5th post
Sent from my HTC Sensation
Hi guys
Thanks to you both for your suggestions.
This morning I unlocked the phone once more, and still had limited service. I then re-locked once again, and as soon as the phone booted it had full service, and has done ever since.
I have no idea what went wrong (they HTC Dev article is pretty straightforward, so I don't think I did anything wrong), and the action that I did above (unlock, relock) I must have done 5 times last night without any effect.
I am still determined to root the phone, so will probably end up with another broken handset soon But at least I will be doing it at the weekend this time, instead of midnight on a Thursday when I have to work at 7 the next day!
Thanks for all the help, I'm sure I'll be back with more questions (problems!) soon.
No problem! Glad to try to help
Sent from my HTC Sensation
Following this minor hiccup (still no idea why it happened) I've now got managed to:
Unlock
Root
Install recovery
Get SU
Get S-off
So thanks for all the help. I'm a complete beginner, but the guides on this site are great and really easy to follow.
Related
Hi there, I currently own an HTC Desire S, the information for it is below:
Android version:
2.3.3
HTC Sense version:
2.1
Software number:
1.28.401.1
Operator name:
vodaphone UK
I haven't yet recieved the Android 2.3.5/Sense 3.0 update. I have tryed searching for updates and checking in using that checkin dial code. I'm just wondering if there's anyway to install this official update onto my phone with minimal risk? I've looked around the forums but can't find exactly what i'm looking for (or I just can't find it!).
Thanks!
I think that you have got the same software version 1.28.401.1 that I had until recently.
I would like to have used to OTA update route but basically got tired of waiting.
I believe that the OTA update was targetted (certainly at first) specifically at those people who already received the previous (troublesome) update to 1.47.
I believe this explains why we didn't get the update.
I loaded the RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed from the development section here and it works a treat. No problems.
The only thing that puzzles me is that my phone is very definitely unbranded and not operator locked, whereas you mention Vodaphone. (If your phone was locked to Vodaphone I would have expected a different software version).
Anyway, if your phone is unlocked like mine, I would certainly recommend using the RUU.
- Steve
fasty said:
I think that you have got the same software version 1.28.401.1 that I had until recently.
I would like to have used to OTA update route but basically got tired of waiting.
I believe that the OTA update was targetted (certainly at first) specifically at those people who already received the previous (troublesome) update to 1.47.
I believe this explains why we didn't get the update.
I loaded the RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed from the development section here and it works a treat. No problems.
The only thing that puzzles me is that my phone is very definitely unbranded and not operator locked, whereas you mention Vodaphone. (If your phone was locked to Vodaphone I would have expected a different software version).
Anyway, if your phone is unlocked like mine, I would certainly recommend using the RUU.
- Steve
Click to expand...
Click to collapse
Thanks very much for your reply.
Yeah, unfortunately my phone is in fact locked to Vodaphone, and I couldn't find the equivalent update that you listed for unlocked phones.
i have a vodafone as well on the same firmware and never got it.
from what i hear the update was pulled due to instability so if you didnt receive it already i very much doubt you will untill a new version is released.
i gave up waiting and went to endymion 3.5
Biogeneric said:
Yeah, unfortunately my phone is in fact locked to Vodaphone, and I couldn't find the equivalent update that you listed for unlocked phones.
Click to expand...
Click to collapse
Are you sure it's locked?!
I thought that software version was for the generic european unlocked version.
Someone else help me here - can the same software number apply to both operator locked and unlocked phones?
fasty said:
Are you sure it's locked?!
I thought that software version was for the generic european unlocked version.
Someone else help me here - can the same software number apply to both operator locked and unlocked phones?
Click to expand...
Click to collapse
i can confirm the htc euro ruu DOES NOT WORK ON VODAFONE BRANDED DEVICES. it bricked my phone and took a whole lot of work to downgrade back to the old hboot to get it working again. the only way to install this version on a voda desire s is via goldcard.it will just give you a cid error and brick your device
djisgod said:
i can confirm the htc euro ruu DOES NOT WORK ON VODAFONE BRANDED DEVICES. it bricked my phone and took a whole lot of work to downgrade back to the old hboot to get it working again. the only way to install this version on a voda desire s is via goldcard.it will just give you a cid error and brick your device
Click to expand...
Click to collapse
Completely agree, great care needed !
But my point was, the software version1.28.401.1 reported by Biogeneric appears to be the same as I had until recently on my unbranded phone.
I thought that if his phone was locked to Vodaphone, wouldn't it have a different software number? Or can the operator lock the phone to their network without changing this software version away form the "generic" one?
- Steve
I'm with Vodaphone, and it says my network is "vodaphone UK" so i'm assuming it's locked! How am I supposed to find out without putting a different networks Sim in?
Biogeneric said:
I'm with Vodaphone, and it says my network is "vodaphone UK" so i'm assuming it's locked! How am I supposed to find out without putting a different networks Sim in?
Click to expand...
Click to collapse
Mine (which recently had the same software version and in NOT operator locked) simply says the name of whatever SIM card you insert.
I suspect your phone may be unlocked, but I'd like feedback from a more experienced developer before suggesting that you load the RUU! We don't want any nasty accidents
By the way, I've just loaded RUU for 2.10.401.8 and it's looking good so far...
Okay, I tried putting in an Orange sim card and setting the network to Orange and it appears to all work (well, I had signal on it, and the network was stated as "Orange"). So i'm assuming my phone is in fact unlocked then?
If so, great news! Am I all clear to update to that unlocked version then? Anyone got a link to the newest one? (Not any mods etc. just the standard update!).
Thanks all!
Biogeneric said:
Okay, I tried putting in an Orange sim card and setting the network to Orange and it appears to all work (well, I had signal on it, and the network was stated as "Orange"). So i'm assuming my phone is in fact unlocked then?
If so, great news! Am I all clear to update to that unlocked version then? Anyone got a link to the newest one? (Not any mods etc. just the standard update!).
Thanks all!
Click to expand...
Click to collapse
I believe that the most recent RUU is RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_225161_signed.exe
in the "Shipped Desire S ROM Collection" :
http://forum.xda-developers.com/showthread.php?t=1002506
I loaded this last night and not experienced any problems so far.
Be warned that this will wipe all existing data on your phone, so make sure that you have got everything saved. In some respects, this is a good thing because you are sure of getting a completely fresh install.
I can't see any reason why this shouldn't work for you, but I wouldn't feel bad if you got a second opinion
-Steve
fasty said:
I believe that the most recent RUU is RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_225161_signed.exe
in the "Shipped Desire S ROM Collection" :
http://forum.xda-developers.com/showthread.php?t=1002506
I loaded this last night and not experienced any problems so far.
Be warned that this will wipe all existing data on your phone, so make sure that you have got everything saved. In some respects, this is a good thing because you are sure of getting a completely fresh install.
I can't see any reason why this shouldn't work for you, but I wouldn't feel bad if you got a second opinion
-Steve
Click to expand...
Click to collapse
Okay thanks very much! I'll try updating it via that ROM tonight - hopefully I won't brick it!
Does anyone know if updating the phone using this method voids the warranty?
Also, how do I actually install that update to my phone? Seen a few tutorials scattared around but some are for different things and I don't want to mess it up! (Easiest/quickest method please, if there is one ha!)
Thanks a lot for your help Steve!
Biogeneric said:
Okay thanks very much! I'll try updating it via that ROM tonight - hopefully I won't brick it!
Does anyone know if updating the phone using this method voids the warranty?
Also, how do I actually install that update to my phone? Seen a few tutorials scattared around but some are for different things and I don't want to mess it up! (Easiest/quickest method please, if there is one ha!)
Thanks a lot for your help Steve!
Click to expand...
Click to collapse
I expect that doing almost anything other than the "official" OTA update theoretically voids warranty. But perhaps more important, if it all went horribly wrong, could anyone detect that you were fiddling with it
If you returned a phone rooted or S-off, then it's asking for trouble.
The discussed RUU is a signed update that does not invoke S-off or root the phone so should not create an "obvious" problem.
The way I updated my phone was as follows:
- I already had HTC Sync installed on my PC
- Fully charged phone
- Downloaded the RUU file to folder on hard disk
- Temporarily disabled my antivirus
- Temporarily disabled standby power saving option on PC
- Connected the phone as normal and selected the option on phone to do Sync
- I let the phone completely finish sync
- I ran the RUU on the PC and followed the simple instructions.
- It took about 10 minutes with no user intervention required.
I don't know if the whole HTC Sync thing is necessary, it was on my PC anyway and the procedure has worked OK for me.
I can now confirm this has all worked for me. no problems so far!
Thanks for all your help fasty! Very much appreciated.
Biogeneric said:
I can now confirm this has all worked for me. no problems so far!
D
Click to expand...
Click to collapse
Great news! Be sure to thank "Football" because he is the one that has done the hard work making these ROMs available.
Hi not sure if posting in correct thread but I am on O2 and also have the 1.28.401.1 software and just been informed by HTC my phone is unbranded despite coming straight from O2. Has anyone received the update whilst being on 1.28.401.1? Am i wasting my time holding out for an OTA update?
RUU
Sent from my HTC Desire S using xda premium
I get this error on the 12th step on htcdev bootloader unlock thingy and i get this error: FAILED (remote: unlock token check failed)
I have tried different methods but nothing have worked ...
I have tried to unistall and then restart and then installed all the drivers again 2 times, didnt work. I tried on my laptop and that wouldnt work either...
So if anyone know what this means or anything please answer on this thread!!
I also e-mailed the htcdev support and they said this: "Dear Pontus,
Thank you for contacting HTC.
I understand that you are experiencing problems unlocking your bootloader.
I think the root of the problem is that your unlock token is not valid.
To get a new, hopefully working, token go to HTCdev.com and follow the instructions there to download one."
Ive tried to do that also but it didnt work either so please guys help me out here!!!
what code did you enter on their site, did you take the first<<<<<(...)>>>>>
and the <<<<<<(...)>>>>> in the end also?
timmert26 said:
what code did you enter on their site, did you take the first<<<<<(...)>>>>>
and the <<<<<<(...)>>>>> in the end also?
Click to expand...
Click to collapse
of course!!
I followed all the steps really urgent. I also got the e-mail correctly and put it in the folder with the 3 other files as they said.
anyone????!?! PLEASE
I have the same problem
did u get a new board? cos i am having the same problem after htc give me a new replacement board.
I have the same problem too , and my XE is new machine ,
i just buy it on January
i have the same problem... and i have also a new board... tried to unlock on windows and linux, both the same... feeled a hundred times...
maybe there is someone else out the who could us help?
Same problem
I try to use HTCdev again and again,
it's still not working,
and i also trying to get temproot to install cwmrecovery ,
i fail ,
i think maybe newest XE 's chip has something change on there .
why using htcdev?! use revolutionary! it's the best! better! what's your hboot version?
revolutionary not support yet
my hboot ver is 1.27
+1 for this problem.
Just got my sensation XE back from warranty repair, most upsetting I can't get root with this HBOOT
trstn said:
+1 for this problem.
Just got my sensation XE back from warranty repair, most upsetting I can't get root with this HBOOT
Click to expand...
Click to collapse
What Version of hboot Do you have now?
I get mine back from warranty repair with 1.29.0000, cause they put a new Board in it.
May be there is an experience developer who want an image of my Stockrom to check some possibilities?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
purebeatz said:
What Version of hboot Do you have now?
I get mine back from warranty repair with 1.29.0000, cause they put a new Board in it.
Click to expand...
Click to collapse
yeah same as, 1.29.0000
I have the same problem. Only difference is that I got my phone back with HBoot 1.18.0000. I could't unlock it via revo and htc dev. After the ICS update I have 1.27.0000. New board, too I think their doing this for every sent in sensation, because my sensation had a broken volume button and dust under the screen. So changing the board was completly pointless.
Is there new news or solution to unlock bootloader?..i am on new matherboard.
I've got the same, rooted phone back from repair. ICS preinstalled, HBOOT 1.29 and can't unlock it. Don't fancy the 'juopunutbear' method bridging connections etc, sounds messy.
Whole list of parts replaced for the dust under the screen problem, board changed giving new imei, wifi mac, bt mac etc etc.
I've replied to my 'repair thread' on HTC website telling them of the problem, I bought HTC so I could unlock and use OpenVPN. Will see what they say!
OK, update from me. I've logged a support request with HTCDEV, after going through the usual check details / make sure it's not something I'm doing wrong they're escalating it.
Given them details of serial number, IMEI, android/sense versions etc and it's being looked into.
I'll come back here once I've had something new from them, but at least the problems being looked at.
I Get This From htc_dev when I send that i flash Unlock_code.bin FAILD:
With regards to your enquiry, kindly this message means that you still have update so kindly we ask you to have the last update then try to unlock your bootloader.NOTE: as we mentioned in our last email between us that unlocking bootloader will make you out of warranty.
Thank you for your patience and understanding.
WTF this means ???
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.
I loved my ChaCha so much I bought a second Black version from Canada's mobile network Telus. Of course it must be tweeked to get the most benefit, so I went to HTCDev to unlock the bootloader. When I run the RUU it tells me that I don't have the latest version. The Telus RUU on HTCDev is 1.24.661.1, but I already have 1.24.661.2 installed. I am lost as to what to do next. I've looked through the forums to find a similar situation but am unlucky.
What I am trying to do is make it so I can get data using my AT&T SIM (voice works, but not data), and run Didije's Custom Stripped Rom.
I guess what I am asking is ...
1. Is there a way to roll my RUU version back?
2. Does anyone have the Telus WWE RUU version 1.24.661.1, executable (.exe)?
3. Is there a way to get root with my current setup.
4. Any workarounds come to mind?
Any help will be appreciated. Thanks everyone.
maxwellsk said:
I loved my ChaCha so much I bought a second Black version from Canada's mobile network Telus. Of course it must be tweeked to get the most benefit, so I went to HTCDev to unlock the bootloader. When I run the RUU it tells me that I don't have the latest version. The Telus RUU on HTCDev is 1.24.661.1, but I already have 1.24.661.2 installed. I am lost as to what to do next. I've looked through the forums to find a similar situation but am unlucky.
What I am trying to do is make it so I can get data using my AT&T SIM (voice works, but not data), and run Didije's Custom Stripped Rom.
I guess what I am asking is ...
1. Is there a way to roll my RUU version back?
2. Does anyone have the Telus WWE RUU version 1.24.661.1, executable (.exe)?
3. Is there a way to get root with my current setup.
4. Any workarounds come to mind?
Any help will be appreciated. Thanks everyone.
Click to expand...
Click to collapse
I ended up finding a thread that explains how to work this. Simply put, just go to the next step. At the HTCDev site, you do not have to install the Updated RUU. Just scroll to the bottom and click, "Next Step."
maxwellsk said:
I ended up finding a thread that explains how to work this. Simply put, just go to the next step. At the HTCDev site, you do not have to install the Updated RUU. Just scroll to the bottom and click, "Next Step."
Click to expand...
Click to collapse
Thank you! I reported this to HTC back in August, but they said just keep checking back. I didnt notice that there is now a notice on the RUU page saying "If your RUU is newer than the one listed below, skip this step and go to the next step"
Had given up hope for rooting this device - 4 apps and i am already getting "no memory" messages
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