Related
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
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
Hey Folks,
This is my first post in the Sensation forums, i've been reading topics for a few days, but I didn't find any solution to my problem and i'm starting to get annoyed by it.
I've obtained a HTC Sensation a few days ago, and as with my previous devices (Galaxy Gio, Optimus Black) I wanted to flash a custom rom on it. I happened to unlock the bootloader of my friends Sensation few weeks earlier, so i thought this was going to be a piece of cake.
Well it wasn't, I couldn't unlock the bootloader using HTCdev method because the phone is vodafone branded. I tried numerous things, i wasn't able to perform the juopeanutbro (?) trick, tried flashing a custom hboot through fastboot (JB_hboot.zip) in linux (gave me an error 42 "Remote: Custom id check failed" or something like that). And after a few days of trying and trying i'm getting tired of it.
So my question is, is there any option i missed to achieve S-OFF or unlock bootloader? I'd love to flash a custom rom on it because I don't like the 4.0.3 Firmware which the phone is running now.
Phone Details:
Android version: 4.0.3 (vodafone)
HBOOT:1.27.0000
Radio: 11.29A.3504.18_M
CID:VODAPE17
Did you select the Vodafone model there in list of HTC dev...
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Premium 4 mobile app
Ihttp://forum.xda-developers.com/showthread.php?t=1668276
If htc Dev method doesn't work for your phone, use the non htc Dev method. Follow everything on the screen, do not run out of battery power (that will probably brick your phone)
Yes I did select the vodafone model, and I end up with the "failed" error when flashing unlock_code.bin. I don't understand why the HTCdev method doesn't work in the first place. And the method described by stillsober requires the almost impossible wire-trick.. Well i'm afraid there is no other method..
Redjack77 said:
Yes I did select the vodafone model, and I end up with the "failed" error when flashing unlock_code.bin. I don't understand why the HTCdev method doesn't work in the first place. And the method described by stillsober requires the almost impossible wire-trick.. Well i'm afraid there is no other method..
Click to expand...
Click to collapse
has your motherboard been replaced?
what error did you have?
It's not that impossible, I did it in like 10 tries, there are YouTube videos timed exactly so you know when to connect and disconnect the wire. plus you can try as many time as it takes so you really can't go wrong... You know both method require the insulated wire right? It's just one requires the more accurate timing
Well I've somehow managed to achieve S-OFF!!!!!! This is my fastboot screen:
h t t p://i43.tinypic.com/2wgubtj.jpg
I read in a guide somewhere on the forum that when having S-OFF flashing a custom recovery would be possible, and writing supercid too, well the first thing failed (again...) but I did manage to write supercid. This is my command prompt screen:
h t t p://i39.tinypic.com/2uqzkna.jpg
So what do I have to do now??
Redjack77 said:
Well I've somehow managed to achieve S-OFF!!!!!! This is my fastboot screen:
h t t p://i43.tinypic.com/2wgubtj.jpg
I read in a guide somewhere on the forum that when having S-OFF flashing a custom recovery would be possible, and writing supercid too, well the first thing failed (again...) but I did manage to write supercid. This is my command prompt screen:
h t t p://i39.tinypic.com/2uqzkna.jpg
So what do I have to do now??
Click to expand...
Click to collapse
what does it say in the top?
juopunutbear or locked?
also i can't view the pics
can you post here in a post?
Well on the picture it says ***Locked*** and you can just paste the link in your browser without the h t t p://, because i can't include links in my posts as I have lest than 10 posts submitted.
But I actually have solved all my problems, because I knew juopeanutbear had unlocked bootloaders available on his website and in fastboot you are possible to flash these with the command "fastboot oem rebootRUU" wich put the device in RUU update mode, and then flash the unlocked HBOOT from juopeanutbear's website with the command "fastboot flash zip jb_hboot.zip.
Note (to people who might find this useful in the future): The devices sticked on showing a green loading bar in RUU update mode after entering the second command, on the command prompt it showed done, but the device didn't reboot or what. Just wait a while (to be sure) and enter command "fastboot reboot-bootloader"
Now my fastboot screen shows **Juopeanutbear** instead of ***locked*** and I've already managed to flash clockworkmod SUCCESFULLY!!!!!!!
Now I will replace CWM by 4ext and i'm good to go I guess, how I managed to get S-off will remain a secret for me, I assume I did do the wire-trick correctly after all, but didn't notice (you know,, spending a few nights behind your PC doesn't give you a clear state of mind
Redjack77 said:
Well on the picture it says ***Locked*** and you can just paste the link in your browser without the h t t p://,
Click to expand...
Click to collapse
you are right
i included also the h t t p : //
so you managed it yourself
crongats
now it is time for a custom rom
note: probably after achieving S-OFF you chose no for installing the jb hboot
Running Team Venom's Viper sense 5 rom and just like I expected I LOVE IT!!
I have been faffing about with S-OFF and the like in an attempt to de-brand my phone to stock HTC with root (the handset was an Orange UK CID). I've been at this for a couple of days now and have seemingly got myself stuck in a corner with the 2.0 hboot, which seems to be what's causing the problem for me - I was previously able to run the stock ICS RUU, but can't any longer.
Handset: HTC One SV LTE (model ID PL8010000)
*** UNLOCKED ***
K2_UL PVT SHIP S-OFF RL
CID: HTC__001 (have also been in SuperCID 11111111 numerous times)
HBOOT: 2.00.0000
RADIO: 1.15.40a.00.04
OpenDSP: v9.2.0268.1214
eMMC-boot
Mar 14 2013, 22:10:43-1
OS at the moment is Viper, because that's all I can get to install. None of the OTAs work (various errors relating to parsing android-info.txt and remote access issues in fastboot). The trouble with Viper is that the radio is apparently knackered, because I can't get a signal at all, and I was on stock JB and on ICS.
If anyone can provide me with a stock ICS 1.00.0000 HBOOT, I can try the RUU again at least. OTAs don't work from there, but it'd be a start. Any other ideas would also be greatly appreciated!
EDIT: Sorry, I forgot I'd already found a stock HBOOT and used it earlier, so have done that again now. Have now run RUU and am on stock HTC__001 version of ICS (K2_UL_ICS_40_HTC_Europe_1.17.401.5_R_Radio_0.12.40.00.14_2_10.49.40.11L_release_301902_signed). However, I still need help getting updated through the OTAs, of which I have 3 in .zip form:
OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.2-1.17.401.5_R_release_308698hqk34kifwjk0g071
OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.6-2.14.401.2_release_311966gsyc11xrfb40ox3c
OTA_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1-2.14.401.6_release_338297mseg08soslxcubit
METHOD 1:
When I try to run any of the above via fastboot oem rebootRUU, it fails and says it can't parse android-info.txt. I've checked the android-info in all three files, and the CID I have on the handset is listed in there, and the model ID is correct. I have verified with fastboot getvar cid that the CID is indeed HTC__001, so I don't understand what the problem is.
METHOD 2:
I've tried re-locking the bootloader and running again, but that still fails as above.
METHOD 3:
I've also tried just flashing the firmware.zip alone, but that spits out errors relating to the checks at two early stages in the updater script:
assert(check_cid(getprop("ro.cid") - I'm not sure why that fails given that the CID is correct for the OTAs, but it works if I just delete this check
assert(getprop("ro.product.device") == "k2ul" || - again, this is the correct device I'm trying to apply the OTA to, so I don't understand the issue
Sorry about the confusion in the initial post; any help would be greatly appreciated!
Your task should basicly be the easiest today, lol.
Get back to SuperCID, flash the RUU again (if needed, the 1.0 hboot before), and then, when phone is booted into android, let it search for updates.
Download and installing should go fine, because you are stock from the RUU and have SuperCID. Do this until no updates left and you are on 4.2.2.
You can also orientate on this guide.
old.splatterhand said:
Your task should basicly be the easiest today, lol.
Get back to SuperCID, flash the RUU again (if needed, the 1.0 hboot before), and then, when phone is booted into android, let it search for updates.
Download and installing should go fine, because you are stock from the RUU and have SuperCID. Do this until no updates left and you are on 4.2.2.
You can also orientate on this guide.
Click to expand...
Click to collapse
Man, I am so sorry. Not only did I fix this myself, I found out what I'd done to cause the ballsup. You know how I said I was getting 0 signal on the network? When changing the CID, I had accidentally overwritten the first 4 digits of the IMEI, so it wasn't recognised as valid any more. Just re-edited mmcblk0p4 to reinsert the original IMEI and it's now getting a signal. Prior to that, I managed to flash HBOOT 1.0 and run RUU then flash the OTAs manually. Have also reflashed TWRP 2.7 and backed up so I can hopefully recover faster from any more mess I make for myself...
Having said that, when I was trying to get the OTAs actually over-the-air, it kept reporting no updates available. Do you think that's just a result of the IMEI issue or do I need to be fully S-ON and locked (as in HTCL) to get OTAs? Do I also need the stock recovery?
Thanks very much for the reply, mate. I wouldn't have been able to do this stuff without your guides and replies on this forum, as well, so I'm grateful for your help.
Well, hard to say with your OTAs, because i never had a non-working CID.
But to run the official OTAs you need for sure a stock recovery!
old.splatterhand said:
Well, hard to say with your OTAs, because i never had a non-working CID.
But to run the official OTAs you need for sure a stock recovery!
Click to expand...
Click to collapse
The CID's fine, it's just the fact I overwrote it onto part of the IMEI... at one point I had manually edited HTC__001 into mmcblk0p4 then later rewritten it via the set cid command, which resulted in that line of the file being set to "HTC__001_001" because I'd keyed it in with the _001 overwriting the first 4 digits of my IMEI. Because I am an idiot, it would seem. Nonetheless, when I was requesting the updates OTA the CID was working fine. However, I only had stock recovery *some* of those times I tried to get OTAs, and I can't say whether the IMEI ballsup was there right from the start or not because I have no idea when I did that. I'll possibly reflash from the RUU again at some point and attempt an OTA on stock recovery with the correct IMEI, but for the time being I'm playing around with Viper because half the reason I started faffing about in the first place was that I thought some of the stock bloatware on the Orange firmware was possibly slowing down the handset (which it evidently was, since it remained slow post-fstrim) and Viper lets me strip the HTC crap out as well.
Anyway, sorry about the dimwittedness, and thanks very much for your help! :good:
I recently got this phone and found out it was an EU version. I unlocked the bootloader and installed twrp. I made the major mistake of thinking I needed to relock the bootloader to install a ruu file. I can't get to recovery now to factory reset. If I try to reboot, it goes to an encryption screen that I can't get past. So I can't go to settings and turn the unlock bootloader option on or debugging. So, I can't unlock the bootloader either.
I also made the mistake of changing the cid and mid to USA dev. The cid and mid are: BS_US001 and 2PZC50000. The product: htc_ocnuhl.
The US unlocked RUUs should work, right? Well, I try to use the. exe. It won't work. I try to do the fastboot way, it says the file size is too large. I try the SD card way, it says 19 RU_MAIN_VER_FAIL is version in android info missing or i.
Am I just totally screwed?
Kaepernick said:
I recently got this phone and found out it was an EU version. I unlocked the bootloader and installed twrp. I made the major mistake of thinking I needed to relock the bootloader to install a ruu file. I can't get to recovery now to factory reset. If I try to reboot, it goes to an encryption screen that I can't get past. So I can't go to settings and turn the unlock bootloader option on or debugging. So, I can't unlock the bootloader either.
I also made the mistake of changing the cid and mid to USA dev. The cid and mid are: BS_US001 and 2PZC50000. The product: htc_ocnuhl.
The US unlocked RUUs should work, right? Well, I try to use the. exe. It won't work. I try to do the fastboot way, it says the file size is too large. I try the SD card way, it says 19 RU_MAIN_VER_FAIL is version in android info missing or i.
Am I just totally screwed?
Click to expand...
Click to collapse
This is a shot in the dark but trying reflashing your unlocker token you received from HTC and see if that will reunlock your phone so you can refresh recovery
Won't let me. Can't get into the os to turn the oem unlock on in developer's settings. When I try it, it tells me:
Last Byte is 0x00, disable unlock.
oem unlock Turn Off!
RLKirk said:
This is a shot in the dark but trying reflashing your unlocker token you received from HTC and see if that will reunlock your phone so you can refresh recovery
Click to expand...
Click to collapse
Sent from my HTC 10 using Tapatalk
Have you tried the proper htc_fastboot.exe?. You can find it easily on the forum. If that doesn't work can you get to download mode and change the cid and mid back to original?
Yeah, I've tried it. I've tried it with trying to get twrp to boot with, "fastboot boot twrp.img". No go there. I haven't tried to change the cid or mid back, but since I'm S-on now, I doubt I'll get very far. Temporary s-on. Just great. HTC really screwed me by making these changes. Four generations of phones work the same freaking way, but this one just had to be different.
shivadow said:
Have you tried the proper htc_fastboot.exe?. You can find it easily on the forum. If that doesn't work can you get to download mode and change the cid and mid back to original?
Click to expand...
Click to collapse
Sent from my HTC 10 using Tapatalk
Looked a bit on the forums and 19 ru_main_ver_fail can apparently mean wrong cid? Did you use the US ruu for the SD card method? Try the other (either your original cid or the US one) and see what happens?
EDIT: Also the output of fastboot getvar all would be helpful to debug
CurtisMJ said:
Looked a bit on the forums and 19 ru_main_ver_fail can apparently mean wrong cid? Did you use the US ruu for the SD card method? Try the other (either your original cid or the US one) and see what happens?
EDIT: Also the output of fastboot getvar all would be helpful to debug
Click to expand...
Click to collapse
Yeah, I used the US ruu after changing the cid and mid for the US dev version. RUU_OCEAN_WHL_O80_SENSE90GP_MR_NA_Gen_Unlock_2.42.617.7.exe.
Tried 2.42.617.1 8 via sd card. RU_SIGNATURE_FAIL
I tried a few others too. No dice. Said wrong OS. I tried the one that came with the phone using the sd card, the EU version, 2.33.401.10, and it says RU_MODELID_FAIL modelid in android-info mismatched
This wouldn't be a problem if I was S-Off. The OS version on the phone now is 2.33.401.10. If I could change the cid and mid back, it would probably work.
I tried using HTC fastboot:
C:\Android>htc_fastboot flash zip 2PZCIMG.zip
sending 'zip'... (2020158 KB) FAILdata too large, 2068641866 > 1951232000
FAILED (data size is too large(2020158 KB) for device to download ZIP file '2PZCIMG.zip'
)
Execution time is 2(s)
Then a newer version of fastboot:
C:\Android>fastboot flash zip 2PZCIMG.zip
target reported max download size of 1560800000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2139634966 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2139634966 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2139634966 is not a multiple of the block size 4096
OKAY [ 1.012s]
writing 'zip' 1/1...
(bootloader) HOSD CL#1002308
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 3.024s
I attached a picture of the getvar all command.
Kaepernick said:
Yeah, I used the US ruu after changing the cid and mid for the US dev version. RUU_OCEAN_WHL_O80_SENSE90GP_MR_NA_Gen_Unlock_2.42.617.7.exe.
Tried 2.42.617.1 8 via sd card. RU_SIGNATURE_FAIL
I tried a few others too. No dice. Said wrong OS. I tried the one that came with the phone using the sd card, the EU version, 2.33.401.10, and it says RU_MODELID_FAIL modelid in android-info mismatched
This wouldn't be a problem if I was S-Off. The OS version on the phone now is 2.33.401.10. If I could change the cid and mid back, it would probably work.
I tried using HTC fastboot:
C:\Android>htc_fastboot flash zip 2PZCIMG.zip
sending 'zip'... (2020158 KB) FAILdata too large, 2068641866 > 1951232000
FAILED (data size is too large(2020158 KB) for device to download ZIP file '2PZCIMG.zip'
)
Execution time is 2(s)
Then a newer version of fastboot:
C:\Android>fastboot flash zip 2PZCIMG.zip
target reported max download size of 1560800000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2139634966 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2139634966 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2139634966 is not a multiple of the block size 4096
OKAY [ 1.012s]
writing 'zip' 1/1...
(bootloader) HOSD CL#1002308
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 3.024s
I attached a picture of the getvar all command.
Click to expand...
Click to collapse
When in download mode u can flash install twrp recovery via adb then possibly flash a backup file, which hopefully u have or can get,,, or a rom. I have done this many times with a failed ruu install and it has worked.
Oh dear I think I see the issue. I don't see any RUUs for the US cid/mid that match the model htc_ocnuhl. I think you can only install an RUU that matches all three and it won't let you install a modified one because the signing will break
And now you can't get into s-off to change it again because the BL is locked. This looks bad...
There should be a warning somewhere about changing to cids your model doesn't support
CurtisMJ said:
Oh dear I think I see the issue. I don't see any RUUs for the US cid/mid that match the model htc_ocnuhl. I think you can only install an RUU that matches all three and it won't let you install a modified one because the signing will break
And now you can't get into s-off to change it again because the BL is locked. This looks bad...
There should be a warning somewhere about changing to cids your model doesn't support
Click to expand...
Click to collapse
Great. In past HTC phones, changing the cid and mid was enough. Now there's a third factor. Can you even change the model with s-off to install an official US RUU on a EU U11? Regardless, I'm stuck between a rock and a hard place. I had no idea that relocking the bootloader would block any chance to load twrp. That wasn't the case on the past phones and now I can't even do a factory reset.
All I need to do is get into the OS to switch bootloader unlocking on. (why they did this to make it more tedious, I don't know.)
The biggest reason I've stuck with HTC is because of how easy it used to be to change regions and install any RUU.
I still get the 155 unknown error when using a RUU.exe. I'm guessing that's why.
Sent from my HTC 10 using Tapatalk
Kaepernick said:
Great. In past HTC phones, changing the cid and mid was enough. Now there's a third factor. Can you even change the model with s-off to install an official US RUU on a EU U11? Regardless, I'm stuck between a rock and a hard place. I had no idea that relocking the bootloader would block any chance to load twrp. That wasn't the case on the past phones and now I can't even do a factory reset.
All I need to do is get into the OS to switch bootloader unlocking on. (why they did this to make it more tedious, I don't know.)
The biggest reason I've stuck with HTC is because of how easy it used to be to change regions and install any RUU.
I still get the 155 unknown error when using a RUU.exe. I'm guessing that's why.
Click to expand...
Click to collapse
The htc_* monikers seem to denote different hardware revisions. So probably different radios, partition layouts etc. You might have been able to change to EU unlocked but it probably can't figure out what to do with US firmware at all. Changing to super cid may have been a better option. This is genuinely a sucky situation though. Maybe there's a way out I don't know. Sorry about that.
EDIT: Are you sure you don't know the encryption password? Did you ever set one?
CurtisMJ said:
The htc_* monikers seem to denote different hardware revisions. So probably different radios, partition layouts etc. You might have been able to change to EU unlocked but it probably can't figure out what to do with US firmware at all. Changing to super cid may have been a better option. This is genuinely a sucky situation though. Maybe there's a way out I don't know. Sorry about that.
EDIT: Are you sure you don't know the encryption password? Did you ever set one?
Click to expand...
Click to collapse
Thanks for trying to help. I can't see a way out either. I never set a password for that. I did for the lock screen but said no when it asked me if I wanted to use it upon boot. Besides that, I'm pretty sure it factory reset when I unlocked the bootloader. Wish I hadn't locked it right after. ?
Sent from my HTC 10 using Tapatalk
One last resort. If it factory reset after unlock it might have a default password. I can vaguely remember something like that existing but can't seem to find it anywhere.
---------- Post added at 07:22 AM ---------- Previous post was at 07:19 AM ----------
Found it. Try "default_password". Otherwise I'm out of ideas.
CurtisMJ said:
One last resort. If it factory reset after unlock it might have a default password. I can vaguely remember something like that existing but can't seem to find it anywhere.
---------- Post added at 07:22 AM ---------- Previous post was at 07:19 AM ----------
Found it. Try "default_password". Otherwise I'm out of ideas.
Click to expand...
Click to collapse
Thanks, but it won't let me put any letters in. Only numbers seem to work. Can't even test it.
Sent from my HTC 10 using Tapatalk
You can try" fastboot format userdata" .
You should be able to enter the system without password.
But You will lost all data(Include Internal storage)
I'm fine with losing any data. New phone and there's nothing I need to save on it. I just need to be able to access the OS so I can unlock the bootloader. I'll give it a shot.
hcaelb said:
You can try" fastboot format userdata" .
But You will lost all data(Include Internal storage)
Click to expand...
Click to collapse
Sent from my HTC 10 using Tapatalk
Kaepernick said:
I'm fine with losing any data. New phone and there's nothing I need to save on it. I just need to be able to access the OS so I can unlock the bootloader. I'll give it a shot.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
I've been following your thread and was hoping it would have led me to a solution to my own dilemma that is similar to your predicament. I had a U11 that I unlocked via HTC Dev website and I wanted to "relock" to get the OTA update. I used a ADB command to relock the phone and the phone boots to a encryption screen which of course won't allow me to bypass. I spent hours looking for a IMG and RUU file that would get my phone back to working order. Used the SD card and ADB process and could not find any joy.
I just sent my phone to the HTC service department. I am hoping they won't make me pay dearly for my mistake. Good luck in resolving this issue. I just got my phone in April and now I am using my old M8 that won't hold a charge for 4 hours.
Live and learn.
Sent from my HTC6545LVW using Tapatalk
Well, I think I know why the RUU.exe isn't working and I got the 155 unknown error. The os doesn't match. I'm guessing the os region needs to be the same, too, and since I can't seem to delete or format the os without unlocking the bootloader, the RUU won't work. [emoji58]
Sent from my HTC 10 using Tapatalk
Yeah, I wish this could have been more help for you, too. I just can't see a way out of it. I even tried changing the cid and mid in the firmware folder I downloaded from htcdev and flashing that. No joy.
mauiblue said:
I've been following your thread and was hoping it would have led me to a solution to my own dilemma that is similar to your predicament. I had a U11 that I unlocked via HTC Dev website and I wanted to "relock" to get the OTA update. I used a ADB command to relock the phone and the phone boots to a encryption screen which of course won't allow me to bypass. I spent hours looking for a IMG and RUU file that would get my phone back to working order. Used the SD card and ADB process and could not find any joy.
I just sent my phone to the HTC service department. I am hoping they won't make me pay dearly for my mistake. Good luck in resolving this issue. I just got my phone in April and now I am using my old M8 that won't hold a charge for 4 hours.
Live and learn.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Sent from my HTC 10 using Tapatalk
Kaepernick said:
Yeah, I wish this could have been more help for you, too. I just can't see a way out of it. I even tried changing the cid and mid in the firmware folder I downloaded from htcdev and flashing that. No joy.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Yep, I tried all what you have done. No dice. Snake eyes. I was hoping to find the exact RUU version for my phone (2.42.617.6) but the I only could find the latest version which is on the HTCDev website. I am not able to get into recovery mode as the phone will give me the message that the phone is loaded with a different OS that it was originally installed. Dead end.
So after trying for over a week the same old steps and reading as much as I could on this and other websites, I knew there was no way I could figure this out or at the very least the phone was in a state beyond my abilities to repair. So my last resort was send it back to HTC. When I first was confronted with this issue I contacted HTC via chat. They were with me for an hour and a half explaining about getting into recovery mode and I explaining what was happening on the phone as we went into download mode and trying to get into recovery mode. Plus my typing skills isn't really proficient so it took time for me to compose and type. Ha! This initial contact with HTC and the start of the service process was on 1 September 2018. I have two weeks from the initial start of the process to send the phone back or I would have to initiate the process again. So this Monday I sent the phone in. The phone should be arriving in the Texas office tomorrow.
I posted this question on another thread and I'll just throw this out here also. If any member here knows or have had experience with HTC service department, what process do they go through to get the phone back to the original working order? Do they reflash the phone or do they actually need to physically replace a part in the phone to get it working again? My phone is still under warranty but I think bricking the phone is not covered even under their "Uh Oh" warranty. Any idea of the cost of repair? Aloha and mahalo.