I was wondering if someone could help me? ... I recently acquired a Telstra Htc One XL and am having troubles trying to update.
Current stats
android 4.1.1
sense 4+
software 3.17.841.2
EVITA PVT SHIP S-OFF RL
*****locked*****
CID-11111111
HBOOT 2.14.0000
RADIO- 0.23a.32.09.29
I'm 99.9% sure most testra one xl's are up to 4.2.2 with sense 5 which is i think two updates in front of mine
can anyone shed some light on my situation?
When you say you're having trouble updating what exactly do you mean?
Sent from my Evita
When i "Check for Updates" it tell me that there are no more updates.... when Im sure there are another two...
Are you in Australia?
Sent from my Evita
Sure am ... Good old city of churches" Adelaide" ..
timmaaa said:
Are you in Australia?
Sent from my Evita
Click to expand...
Click to collapse
His profile says he is
Yeah, but still needed to check. Have you thought about re-unlocking your bootloader? It's been modified in the past which might have something to do with your update problem. If you unlock your bootloader you'll be able to install a custom recovery and then you can install whatever ROM you like. We have the stock Telstra Sense 5 Android 4.2.2 ROM in our development section. We also have a few other Sense 5 ROMs to choose from, ranging from stock to tweaked.
Sent from my Evita
The thing is that it hasnt been messed with.I got the phone from a HTC rep that i know ... he had it in his draw for over six months ...I just wanted the stock update but maybe rooting might be the easier way
It definitely has been messed with, phones that are s-off and have SuperCID don't come out of the factory like that. Somewhere along the way someone has done those alterations to the device.
There is just one problem I've realised, your phone has a SuperCID of 11111111 which has been blocked by htcdev. You're s-off though so you can actually change that as many times as you like using fastboot. If you want to unlock your phone you'll need to change it to 22222222 using the following fastboot command:
Code:
fastboot oem writecid 22222222
You can then check the new CID by using this command:
Code:
fastboot oem readcid
Once that's done you can go to htcdev and go through with the unlock bootloader process.
In order to do the above process you will need to install adb/fastboot and HTC drivers.
Sent from my Evita
No problem ... thanks for that ....I have rooted my one x before HTC_023 fairly basic but my mate swears that the phone came straight from HTC as a Tell us what you think before we send you more kind of thing .. Cheers for the info ...
Actually one more thing ... is it possible to do a RUU update with this to 4.2.2?
There is no RUU for 4.2.2, the only way is to run an earlier RUU and take OTA updates to get there. Since you can't get the OTA I guess that isn't an option though.
Sent from my Evita
grekojim said:
Sure am ... Good old city of churches" Adelaide" ..
Click to expand...
Click to collapse
Within 30 minutes drive from me no doubt
Supercid and s-off from factory or not still means you are off the official path.
Things I might do:
fastboot oem writecid TELST001
Then try the OTA again
or
RUU back to 1.89.841.9 as a RUU exists for that, then ota forwards to 5.06.841.1
or
Unlock bootloader
Flash Turges 5.08 firmware zip and then take one of the Sense 5 ROMs. There is a stock Telstra ROM even.
PS nag the HTC rep for a more recent RUU, eg 2.40.841.4, 3.17.841.2, 3.17.841.9 or 5.06.841.1 and share with us
---------- Post added at 12:56 PM ---------- Previous post was at 12:48 PM ----------
timmaaa said:
Once that's done you can go to htcdev and go through with the unlock bootloader process.
Click to expand...
Click to collapse
He has s-off does he need a token or even need to unlock at all?
I have often wondered the same thing, but I've been assuming that in order to flash TWRP recovery you need an unlocked bootloader.
It's nice to see a few Aussies on here by the way, I'm in Melbourne myself.
Sent from my Evita
great ... trying the cid thing first ...
My phone from an att employee came s-off and with a locked boot loader as well. It just looks like that's how HTC and att do it.
Sent from my HTC One XL
Alright cid change didnt work ..now to find the 1.89.841.9 RUU
Click the link in my signature, from there you'll find a link to the HTC RUU thread.
Sent from my Evita
RUU links all changed and the index doesnt keep good track of the current RUU sites.
Try:
http://www.androidruu.com/?developer=Evita
http://www.androidruu.com/getdownlo...09.01_10.93a.32.20L_release_266699_signed.exe
Thank you heaps .....
Just in case .. i got the unlock code from htc deV But when my cid was 11111111 .....would that matter if i use that code now that my cis is telst001?
Related
what are the benefits of doing super-CID (i.e. 11111111)
If i do superCID can I again restore to stock CID..
Please help
abhishek89 said:
what are the benefits of doing super-CID (i.e. 11111111)
If i do superCID can I again restore to stock CID..
Please help
Click to expand...
Click to collapse
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
gol_n_dal said:
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
Click to expand...
Click to collapse
So how do I install roms from different carriers
fatswaller4451 said:
So how do I install roms from different carriers
Click to expand...
Click to collapse
first you need to S-OFF then supercid
after that you can use any ruu.exe
Super Cid
rzr86 said:
first you need to S-OFF then supercid
after that you can use any ruu.exe
Click to expand...
Click to collapse
Hey thanks for your response
Ok so I have s-off and super Cid just a few more questions if u don't mind
1. can i install any ruu for any android phone or am I limited?
2. Will installing a ruu for another phone effect the way my current phone works
3. When installing a ruu.exe for another phone will I have to follow the same bootloader unlock method for that phone or my phone?
Sorry for the newbie questions but I have limited knowledge of super cid however I have been rooting for years now
I heard some bad things about super cid but have not had any issues thus far, the guide was very easy to follow and in fact just to make sure it was working I was able to ruu backwards
Thanks for your expertise you r awesome
fatswaller4451 said:
Hey thanks for your response
Ok so I have s-off and super Cid just a few more questions if u don't mind
1. can i install any ruu for any android phone or am I limited?
2. Will installing a ruu for another phone effect the way my current phone works
3. When installing a ruu.exe for another phone will I have to follow the same bootloader unlock method for that phone or my phone?
Sorry for the newbie questions but I have limited knowledge of super cid however I have been rooting for years now
I heard some bad things about super cid but have not had any issues thus far, the guide was very easy to follow and in fact just to make sure it was working I was able to ruu backwards
Thanks for your expertise you r awesome
Click to expand...
Click to collapse
1)with s-off and supercid you are not limited
2)it won't affect anything at all
But probably you will have some official updates from the specific carrier(if you have)
3)I think it depends from the carrier of the Ruu you have chosen
But actually there is no need to unlock the bootloader because you are on s-off
Edit:in second and third question what do you mean by another phone?
I assume you mean another carrier
If yes then yes
If you mean another device(for example Samsung)then absolutely no
Of course you can use any ruu but only from sensation's devices
Sent from my HTC Sensation using xda premium
super cid
rzr86 said:
1)with s-off and supercid you are not limited
2)it won't affect anything at all
But probably you will have some official updates from the specific carrier(if you have)
3)I think it depends from the carrier of the Ruu you have chosen
But actually there is no need to unlock the bootloader because you are on s-off
Edit:in second and third question what do you mean by another phone?
I assume you mean another carrier
If yes then yes
If you mean another device(for example Samsung)then absolutely no
Of course you can use any ruu but only from sensation's devices
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
So I have verified that I have super cid on my evo 4g lte by ruuing backward, however when I try flashing an htc one ruu i get an error message that its the wrong file, so i tried flashing an original evo 4g ruu and still get the same message
I am still s-off
relocked bootloader
super cid
hboot 2.0.9
latest firmware
am i missing something?
Thanks
fatswaller4451 said:
So I have verified that I have super cid on my evo 4g lte by ruuing backward, however when I try flashing an htc one ruu i get an error message that its the wrong file, so i tried flashing an original evo 4g ruu and still get the same message
I am still s-off
relocked bootloader
super cid
hboot 2.0.9
latest firmware
am i missing something?
Thanks
Click to expand...
Click to collapse
wait man man
for which device are we talking about?
not for sensation?
EVO 4g lte
Sent from my EVO using xda app-developers app
fatswaller4451 said:
EVO 4g lte
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
no maaaaannnnn
don't use any ruu for sensation to evo 4g
go to the evo 4g's thread and see there for ruu.exe files
this forum is only for sensation/xe/4g
i thought you were talking about sensation devices
Ok thanks for the info but I was talking about super cid and installing roms from different carrier's
Sent from my EVO using xda app-developers app
---------- Post added at 12:14 PM ---------- Previous post was at 12:06 PM ----------
I was following a previous thread
Sent from my EVO using xda app-developers app
to reduce the confusion
NO- you cant/shouldn't flash another model phone's RUU on another
there is a high chance of bricking the device if you do that
Does SuperCID also network unlocks the phone?
There is a lot of confusion on the internet about SuperCID. I have HTC One S which is locked to T-Mobile and I want to get it network unlocked. the "strings -n 8 /dev/block/mmcblk0p6" method did not show unlock_code for my phone (though it has worked for some other people). While googling I found that doing SuperCID by changing mmcblk0p4 can also network unlock the phone. Please let me know if you have some idea. Thanks.
gol_n_dal said:
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
Click to expand...
Click to collapse
I can't even re-unlock the bootloader for some reason either.
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
I mistakenly used the JBFW tool on my AT&T branded phone (CID: CWS__001) to change the CID to HTC__001, not realizing that my phone was still S-ON and the CID changing option was apparently for S-OFF only. I had root, I had the bootloader unlocked. Now I can't even get into recovery, and I think since my CID is apparently stuck as HTC__001, that the RUU for my phone's actual CID won't work. I should note that before I relocked the bootloader, I tried to change my CID back to the SuperCID but it would just freeze the phone. That's why I tried to relock it, hoping it would help. I thought I could just unlock it again, but it won't work. I can't flash anything via ADB, it all fails. This is the RUU I was trying to use:
RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio_0.19as.32.09.11_2_10.105.32.25L_release_271865_signed.exe
and I got a Wrong Customer ID error.
Is there anything I can do to remedy this situation or am I at the warranty center's mercy? Thank you in advance for any help.
im in the same boat, hopefully we get some help here soon, ive got another phone on the way from the warranty center but they want the one i have now and if they see its been tampered there gonna send me a bill for the full price of the phone. wish i could help.
We have the exact same phone. I have a dif RUU though. Mine says AT&T. I'll find the link to dl that RUU in a sec. Currently away from the pc where I have that page bookmarked
EDIT: I do believe that all the Cingular RUUs don't work anymore, their currently out of business thanks to our carrier AT&T... Don't know why you would try and use a Cingular RUU...
Sent from my HTC One XL using xda app-developers app
Myrder said:
We have the exact same phone. I have a dif RUU though. Mine says AT&T. I'll find the link to dl that RUU in a sec. Currently away from the pc where I have that page bookmarked
EDIT: I do believe that all the Cingular RUUs don't work anymore, their currently out of business thanks to our carrier AT&T... Don't know why you would try and use a Cingular RUU...
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Cingular is att.
If you see a ruu that says.Cingular,it will work
Sent from my HTC One XL using xda app-developers app
Now, this is the correct RUU http://www.4shared.com/file/35bbU4_Y/htc_one_x_RUU_2205027_att_us_0.html. It's going to take anywhere from 10-25min to complete.
After you complete the RUU, go to this thread http://forum.xda-developers.com/showthread.php?t=1952426
Download and follow each step. You will then be rooted, correctly.
Myrder said:
Now, this is the correct RUU http://www.4shared.com/file/35bbU4_Y/htc_one_x_RUU_2205027_att_us_0.html. It's going to take anywhere from 10-25min to complete.
After you complete the RUU, go to this thread http://forum.xda-developers.com/showthread.php?t=1952426
Download and follow each step. You will then be rooted, correctly.
---------- Post added at 03:18 PM ---------- Previous post was at 03:16 PM ----------
Cingular doesn't have an RUU for the people that have 2.20, I've looked.
Click to expand...
Click to collapse
The 1.85 ruu says Cingular in the file name. Cingular may not have an ruu for 2.20 because it was released as "att" ota.
If you look at 1.85 it says AT&T Cingular
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
The 1.85 ruu says Cingular in the file name. Cingular may not have an ruu for 2.20 because it was released as "att" ota.
If you look at 1.85 it says AT&T Cingular
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I stand corrected.
Myrder said:
I stand corrected.
Click to expand...
Click to collapse
It's all good bro! You're trying to help,.that's all that matters. I've been trying to take a break from the Q&A and work on the unbricking. But something attracts me here :crying:
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
It's all good bro! You're trying to help,.that's all that matters. I've been trying to take a break from the Q&A and work on the unbricking. But something attracts me here :crying:
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I have a nag for wanting to help people and it seems you do too. Lol.
Speaking of, I've been trying to keep up with that thread you have. How's that coming?
he wont be able to flash the ruu because he changed his cid to the international one x to try to flash the international jb rom which would of bricked his phone if it worked. running "OUR" supercid might get it set to supercid and let you reflash ruu.
Lmao, now that is a hard pickle to get yourself into!!!
If cid was changed to HTC_001 properly, go snag a new token off htcdev website........I'm not going to explain the rest
Sent from my HTC One XL using Tapatalk 2
Just to let you know our (The HTC One XL). Super Cid is 1111111 (I'm pretty sure it's seven 1's?). In any case you should not be looking at the One X (Tegra) forums and much rather look at the One XL/ATT One X forums unless you enjoy staring at a $600 paperweight.
Sent from my HTC One XL using xda premium
TheNightHawk223 said:
Just to let you know our (The HTC One XL). Super Cid is 1111111 (I'm pretty sure it's seven 1's?). In any case you should not be looking at the One X (Tegra) forums and much rather look at the One XL/ATT One X forums unless you enjoy staring at a $600 paperweight.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
8, I believe
First rfatmen
I wasn't able to change my CID back to the SuperCID via any method I could find. And I don't think the CID was "properly" changed/spoofed to HTC__001, but I definitely could still get verified tokens from HTCDev. The problem was that I couldn't re-unlock it by pushing the .bin via ADB because it just failed. Since I'd upgraded less than a week ago, I was able to convince the semi-clueless guy at AT&T to exchange my One X.
knyghtmayre said:
I wasn't able to change my CID back to the SuperCID via any method I could find. And I don't think the CID was "properly" changed/spoofed to HTC__001, but I definitely could still get verified tokens from HTCDev. The problem was that I couldn't re-unlock it by pushing the .bin via ADB because it just failed. Since I'd upgraded less than a week ago, I was able to convince the semi-clueless guy at AT&T to exchange my One X.
Click to expand...
Click to collapse
That's the spirit.
absolutelygrim said:
The 1.85 ruu says Cingular in the file name. Cingular may not have an ruu for 2.20 because it was released as "att" ota.
If you look at 1.85 it says AT&T Cingular
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
link to 2.20 ruu http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Crappyvate said:
link to 2.20 ruu http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Click to expand...
Click to collapse
well I know there is an RUU for it silly, I meant the naming convention isn't the same as previous RUU's
DvineLord said:
he wont be able to flash the ruu because he changed his cid to the international one x to try to flash the international jb rom which would of bricked his phone if it worked. running "OUR" supercid might get it set to supercid and let you reflash ruu.
Click to expand...
Click to collapse
I accidentally flashed recovery to boot portion. ie
HTML:
fastboot flash boot twrp.img
instead of
HTML:
fastboot flash recovery twrp.img
.
Then I also flashed recovery to recovery portion thinking that I can boot into recovery.
But now my phone boots and stays at twrp logo.
Even when I try to boot into recovery the same twrp logo nothing happens.
Just a heads up, HTCDEV unlocking no longer works with supercid. Changing cid to 22222222 does work. Thanks BEAUPS for already confirming that (Hes a beast)
Seeing that the chances of the hox exploits getting updated are pretty slim heres a easy fix to get people unlocked
Easy fix-
Use any existing exploits that changes your cid to supercid. Once done-
From bootloader use the fastboot cmd
fastboot oem writecid 22222222
Then proceed with getting your unlock token as usual using htcdev
The above cmd will only work with supercid. Once you change it to anything other, the command no longer will change cid. You have to do it manually.....
This is just a heads up and a quick workaround for those that need it.
18th.abn said:
Just a heads up. Changing cid to 22222222 works. Thanks BEAUPS for testing/confirming that.
Easy fix-
Use any existing exploits that changes your cid to supercid. Once done-
From bootloader use the fastboot cmd
fastboot oem writecid 22222222
Then proceed with getting your unlock token.
The above cmd will only work with supercid. Once you change it to anything other, the command no longer will change cid. You have to do it manually.....
This is just a heads up and a quick workaround for those that need it.
Click to expand...
Click to collapse
They just started blocking it? I just Unlocked my Bootloader last Sunday with 11111111 just fine
Re: HtcDev wesite Blocking Supercid FIX
Great work
Sent from my SPH-L710 using Tapatalk 2
Seriously?! Why would they do this? Is SuperCID a security risk? I thought I had left this kind of crap behind when I retired my iphone.
This is my first and last HTC phone.
Sent from my Nexus 7 using Tapatalk HD
does this mean updating to jb sense with 22222222 will no longer brick phone like with supercid?
Supercid doesn't cause brick or atleast out of the many ota's I have done it has never caused an issue. Who actually did have issues with supercid and an ota?
twistedddx said:
Supercid doesn't cause brick or atleast out of the many ota's I have done it has never caused an issue. Who actually did have issues with supercid and an ota?
Click to expand...
Click to collapse
I get an issue with SuperCID: I apply an ota from an official RUU to get Jelly Bean, the ota was very well installed but at the end of the process the phone doesn't boot an was locked in QHSUSB_DLOAD and at this time when you're locked in this mod by OTA update with superCID you can't rewrite partitions with the topic "unbricking evita".
My only solution was mobiletechvideos.com who fixed it very well
mik93250 said:
I get an issue with SuperCID: I apply an ota from an official RUU to get Jelly Bean, the ota was very well installed
Click to expand...
Click to collapse
What ruu did you apply? Was the phone modified in any other way than supercid? Eg was the hboot downgraded? Previous unlocked bootloader? Current unlocked bootloader?
What was the full state of the phone prior to accepting ota.
How was the ota applied? Did you simply check for updates and accept then follow prompts. Or installed via fastboot?
I have upgraded 2 hk one xl's with supercid to 3.17 via ota without issue. One was previously hong Kong ruu then wiped and had singtel stock Rom flashed then accepted singtel 3.17 ota. Could not use singtel ruu as Hong Kong ruu was newer and already installed. Hboot downgrade and software version tinkering still did not allow singtel ruu. I could only reinstall honk Kong ruu.
The other via o2 ruu and o2 3.17.
There seems to be some differences in the protections in hboot. Downgrading my phones hboot to 1.09 did not make flashing radio and boot from recovery functional again. It did not let me install older ruu's. My devices, one that has had every mod and flash done to it and the other very very little, both seem super hboot protected now!
The similar theme is both devices have been through all 4 generation of ota's. Following different ota and ruu paths but have now got the same outcome.
Maybe it relates to when supercid was applied even. Both my devices had supercid applied at hboot 1.09.
Damn HTC and ATT! They are bent on making this difficult. My next phone will be Nexus, enough of this crap!
We've had worse patches to overcome on the Evita, atleast its a simple solution for the time being. I do agree tho. I moved on from htc for the time being.
Sent from my SPH-L710 using Tapatalk 2
iElvis said:
Seriously?! Why would they do this? Is SuperCID a security risk? I thought I had left this kind of crap behind when I retired my iphone.
This is my first and last HTC phone.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
done moved over to the nexus 4 myself
Great to know, although I already have mine unlocked.
CheesyNutz said:
done moved over to the nexus 4 myself
Click to expand...
Click to collapse
Can you get Beats Audio or any other sound enhancements on a Rooted Nexus 4 via Custom Rom or other methods?
Viper4713 said:
Can you get Beats Audio or any other sound enhancements on a Rooted Nexus 4 via Custom Rom or other methods?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 7 using Tapatalk HD
Do you miss LTE cheesy? I live in Canada so I understand I can get LTE on nexus 4 but if I couldnt I don't think I could live without it now
Sent from my VENOMized HoxL
CheesyNutz said:
Yes
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the Info, I guess my next phone later on will be a Nexus Phone
area51avenger said:
Do you miss LTE cheesy? I live in Canada so I understand I can get LTE on nexus 4 but if I couldnt I don't think I could live without it now
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
LTE is not in my area so in would have no idea
Sent from my Nexus 7 using Tapatalk HD
I can't believe at&t would be this petty... Or that HTC would go along with it. I'm glad I unlocked my boot loader when I did.
Sent from my Nexus 7 using xda premium
Just tested.
Hong Kong One XL running 3.17.707.1.
Supercid 11111111
Just went through http://htcdev.com unlock process and got an unlock token 100% fine.
Again there is nothing wrong with Supercid, at least not in general. It works with htcdev.com and does not brick phones.
Someone needs to check if it is just AT&T phones that are struggling with supercid or if something else is upsetting things.
It is not supercid on its own, supercid(11111111) works fine!
HTC/AT&T might be actively checking for modified AT&T phones that are getting unlock tokens via root exploits and changing cid.
Non at&t phones don't need supercid, so this only affects at&t phones. All the other carriers phones will unlock with out messing with the cid number.
Sent from my Nexus 7 using xda premium
My friend and I are having problems unlocking his HTC One X. we've tried various tutorials and followed many threads but have had no luck. We've tried the One_X_ATT_All_In_Kit_v2.1.1, Root-one-x and OneXRootOneClick with no luck. The bootloader will not unlock, we kept getting an error code 160 and MID not allowed. So no Unlock_Bin was generated. It has been upgraded to 4.1 via the AT&T update.
Bootloader screen reads:
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-V34.1.0.45.1219
eMMC-boot
Nov 26, 2012, 18:37:14:-1
If anybody can point us in the direction of where we can go to root the phone, that'd be great.
Try asking in the Evita forum here: http://forum.xda-developers.com/forumdisplay.php?f=1538
This forum is for the International version (Endevor)
I'm sorry about that, is there anyway a Mod can move this over to that forum? I don't want to create another thread for the same issue
Request sent.
Welcome to the One XL thread!
http://forum.xda-developers.com/showthread.php?p=33189590
[TOOL] HTC One X (Evita) All-In-One Toolkit V2.1.1 [2-1-2013] [PERM ROOT][Noob-Proof]
Here is what you need. If you took the job ota I'm afraid you stuck without root for now. But if you need further assistance let us know?
Sent from my HOX w/CM10.1 4.2.2 s-off
nawarkk said:
HBOOT-2.14.0000
Click to expand...
Click to collapse
I'm afraid you're out of luck for now. There is no root method for JB yet.
iElvis said:
I'm afraid you're out of luck for now. There is no root method for JB yet.
Click to expand...
Click to collapse
Duh... I all ways forget to look at the specifics
2.14 vs 1.14
Thanks Elvis.
Yea too bad we can't spoof the cid as before.
Sent from my HOX w/CM10.1 4.2.2 s-off
I believe, via the all in one toolkit, we were able to get the CID to change to 111111, but only after a few tries. I'll have to check back with him if it indeed did change.
So what you guys are saying, is unless somebody finds a way to crack JB, there is no way to unlock the bootloader/root?
Is it not possible to run the RUU that would place him back to the android and hboot he had before? (Don't know if it was ICS or what it was)
nawarkk said:
I believe, via the all in one toolkit, we were able to get the CID to change to 111111, but only after a few tries. I'll have to check back with him if it indeed did change.
So what you guys are saying, is unless somebody finds a way to crack JB, there is no way to unlock the bootloader/root?
Is it not possible to run the RUU that would place him back to the android and hboot he had before? (Don't know if it was ICS or what it was)
Click to expand...
Click to collapse
Can't run a ruu for older firmware without s-off.
But if you actually achieved supercid, you should be able to unlock, root, and s-off.
Are you positive about that? Because I was able to run an older RUU on my HTC Evo 3d, and got the phone to an older firmware without S-Off..
We'll have to check for sure on the CID and report back when we can.
nawarkk said:
Are you positive about that? Because I was able to run an older RUU on my HTC Evo 3d, and got the phone to an older firmware without S-Off..
We'll have to check for sure on the CID and report back when we can.
Click to expand...
Click to collapse
Different phone. Newer ruu's check for hboot versions. Won't work on this one.
Hello guys
Sorry for my bad english but il try to be precise as i can. I bought my htc on ebay it says new and it feels new. But after i read may treads here it seems its not new . I have problems with automatic software update it freezes on 20% then it reboots after few minutes, if i regard this problem the phone works fine. But im fustrated i want new software . Now i got in boot loader in this is what it says:
++++locked+++++ - in one tread i read this should be relocked
evita pvt ship s-off rl - i belive this is s-off i need your confirmation
cid - 11111111 - i dont understand fully this yet but its a good thing i belive
h-boot 1.09.0000 - dont understand what this means
RADIO - 0.16a.32.09.17_2 - i belive this is software for my phones antena
open dsp - v25-1-0-32-0405 - dont know if this is imortant
emmc -boot
Apr 2 2012, 21:08:24 - is this last known software update i manufacturing date
Know i need you help to explain this thing to me and if its safe and what do i have to do to install new software. Which software whould you
recommend and maybe can i install viper xl
Thanks
The phone definitely isn't new. You have SuperCID (11111111) and s-off which means it has been unlocked at some point. But the good news is you can easily unlock the bootloader at htcdev, then install a custom recovery, and then install Viper if you wish.
Sent from my Evita
Thanks for the reply, now i never unlocked bootloader can you give me some advice on the safest way to do that and where can i see when bootloader is unlocked, sorry for dumb questions but if i dont ask ill never learn
Can somebody send me some links where can i find instructions on how to unlock bootloader, make recovery image and then how to install viper xl rom
Is your phone an at&t model? If it is it'll have the at&t logo above the screen, otherwise it'll just have the HTC logo.
Sent from my Evita
Itd at&t phone
Sent from my HTC One XL using xda app-developers app
You already have SuperCID so you can go to htcdev and unlock your bootloader.
Sent from my Evita
timmaaa said:
You already have SuperCID so you can go to htcdev and unlock your bootloader.
Click to expand...
Click to collapse
The phone is s-off, does the OP even need to unlock the bootloader to install TWRP, flash ROM, etc.?
You typically won't receive OTAs for AT&T phones outside of North America. So that is probably why the update is failing.