Hello there guys,
Been trying to root my XL from Telstra (AUS) but some weird things are going on.
Can't figure out why i'm unable to to SuperCid my phone, my current Supercid is TELST001
http://forum.xda-developers.com/showthread.php?t=1952038
Also, tried to root my phone using this thread below:
http://forum.xda-developers.com/showthread.php?t=1859478
So far, I have achieved to Installed S-OFF and CWM.
What i'm trying to do here is to use any 4.22 Android Rom with sense 5, like CleanROM or CyanogenMod 10
Im uploading some of the current photos taken so you guys can have more information on S-OFF and CWM.
Thanks in advance.
Ps: One of the pictures was a Failed OTA from Telstra, is there a way to go back to and be able to install the OTA from Telstra instead of any custom ROM (In case we cant find what is causing the phone to block the supercid and the super SU)
Ota won't work with a custom recovery.
I am running MagioR4 sense 5 4.2.2 you can install that now without doing anything else to your phone. There are a few others as well, but this is only one I've been running so I can't say much about others, but assume they will work out just as well.
Sent from my HTC One XL using xda app-developers app
31ken31 said:
Ota won't work with a custom recovery.
I am running MagioR4 sense 5 4.2.2 you can install that now without doing anything else to your phone. There are a few others as well, but this is only one I've been running so I can't say much about others, but assume they will work out just as well.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hi there mate,
Tried to run Super Su and shows as the phone been not rooted, i'm a bit confused atm.
Is there a need to Super Cid and if i were to use the OTA, can i remove the custom recovery?
Desertum said:
Can't figure out why i'm unable to to SuperCid my phone, my current Supercid is TELST001
Click to expand...
Click to collapse
That's the carrier ID (CID) not SuperCID. SuperCID is 11111111 or 22222222. I think you know that, but let's get the terms right to avoid confusion.
You don't have S-off. It says right in your screenshot that the phone is still s-on.
But you it says UNLOCKED, so your bootloader is unlocked. All S-on means is that you can still install custom ROMs, you just have to flash boot.img seperately from fastboot.
As mentioned, you have to return to stock recovery in order to be able to install OTAs. Easiest way is to RUU back to stock. But be completely sure you are not SuperCID, otherwise S-on + SuperCID + Jellybean RUU = BRICK.
Personally, going stock just to install the stock 4.2.2 ROM is a step backward, not forward, as you already have an unlocked bootloader and cutom recovery. But you also seem confused about a number of things. I would suggest reading and more fully understanding the concepts and processes before proceeding with any further mods to the phone.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Desertum said:
Hi there mate,
Tried to run Super Su and shows as the phone been not rooted, i'm a bit confused atm.
Is there a need to Super Cid and if i were to use the OTA, can i remove the custom recovery?
Click to expand...
Click to collapse
Unlocking the bootloader does't root the phone. You can flash an SU package in recovery to obtain root, or flash a rooted ROM.
You don't need SuperCID for anything but s-off.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
Desertum said:
What i'm trying to do here is to use any 4.22 Android Rom with sense 5, like CleanROM or CyanogenMod 10
Click to expand...
Click to collapse
CleanROM is neither 4.2.2 nor Sense 5. CM10 is an AOSP ROM, so by definition not a Sense ROM at all.
redpoint73 said:
That's the carrier ID (CID) not SuperCID. SuperCID is 11111111 or 22222222. I think you know that, but let's get the terms right to avoid confusion.
You don't have S-off. It says right in your screenshot that the phone is still s-on.
But you it says UNLOCKED, so your bootloader is unlocked. All S-on means is that you can still install custom ROMs, you just have to flash boot.img seperately from fastboot.
As mentioned, you have to return to stock recovery in order to be able to install OTAs. Easiest way is to RUU back to stock. But be completely sure you are not SuperCID, otherwise S-on + SuperCID + Jellybean RUU = BRICK.
Personally, going stock just to install the stock 4.2.2 ROM is a step backward, not forward, as you already have an unlocked bootloader and cutom recovery. But you also seem confused about a number of things. I would suggest reading and more fully understanding the concepts and processes before proceeding with any further mods to the phone.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Unlocking the bootloader does't root the phone. You can flash an SU package in recovery to obtain root, or flash a rooted ROM.
You don't need SuperCID for anything but s-off.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
CleanROM is neither 4.2.2 nor Sense 5. CM10 is an AOSP ROM, so by definition not a Sense ROM at all.
Click to expand...
Click to collapse
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Thanks
Desertum said:
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Thanks
Click to expand...
Click to collapse
No you've got it backwards. The boot.img goes in your fastboot folder on your pc, not on your phone.
You need to fastboot flash the boot.img from each ROM you want to flash. So, if you want to install CM10.2, you must extract the boot.img from the ROM zip and put it in your fastboot folder on your pc (not your sd card in your phone). Then you put the ROM zip on your phone, and install it in recovery (after wiping cache/dalvik cache/factory reset/system), then reboot to bootloader and flash the boot.img using fastboot. You must follow this process for each new ROM you want to flash.
Do a backup of your current setup in recovery before flashing anything new though.
Sent from my Evita
---------- Post added at 11:42 PM ---------- Previous post was at 11:40 PM ----------
By the way, even though our phone doesn't have a physical sd slot, we refer to the stage as the sd card.
Sent from my Evita
Desertum said:
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
Click to expand...
Click to collapse
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
Desertum said:
Hello there,
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Click to expand...
Click to collapse
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
redpoint73 said:
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
Click to expand...
Click to collapse
Hi there,
Im trying to Update the RUU as per this thread:
http://forum.xda-developers.com/showthread.php?t=2382933
However, I'm getting an error called 155, which says that Im trying to install the wrong RUU
I was trying to update the RUU, then restart the phone, went into S-off, then into recovery and Wipe factory/data reset, then install the CM10.2 build
Is something missing here?
Thanks.
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Sent from my Evita
---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------
timmaaa said:
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Also, what do you mean you "went into s-off"?
Sent from my Evita
Click to expand...
Click to collapse
Sent from my Evita
Desertum said:
Im trying to Update the RUU as per this thread:
http://forum.xda-developers.com/showthread.php?t=2382933
However, I'm getting an error called 155, which says that Im trying to install the wrong RUU
Click to expand...
Click to collapse
Its saying wrong RUU, because its the wrong RUU.
If you are S-on, you can only run an RUU meant for your Telstra version.
It appears you ignored my previous advice to read up on the basic concepts and procedures, before continuing to try to mod the phone.
redpoint73 said:
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
Click to expand...
Click to collapse
timmaaa said:
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Sent from my Evita
---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------
Sent from my Evita
Click to expand...
Click to collapse
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
And yes, I'm trying to install the 3.18 RUU, currently using 3.17.
Thanks.
Desertum said:
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
Click to expand...
Click to collapse
I think this is a lost cause. You aren't even reading what people have replied to you. I clearly stated in post #4 above, you DO NOT have s-off.
Right in your second screen shot (white bootloader screen) it says S-ON (third line of text). This means you DO NOT HAVE S-OFF.
Desertum said:
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
And yes, I'm trying to install the 3.18 RUU, currently using 3.17.
Thanks.
Click to expand...
Click to collapse
Like Redpoint just said, you can't install an RUU from another carrier (the 3.18 RUU is at&t) while you're s-on. You don't have s-off, look at the screenshots you attached earlier, in your bootloader it says s-on. You have an unlocked bootloader which is an entirely different thing.
Unless you've flashed a superuser zip or flashed a rooted ROM you don't have root. Root just means that you have administrative access to system files in a ROM. The real thing you need to install custom ROMs is an unlocked bootloader and a custom recovery.
I'm gonna be honest, you're in over your head and you're ignoring good advice which was given to prevent you from damaging your phone.
You really have two choices: either do a hell of a lot of reading until you have a firm understanding of what you're doing, or leave your phone alone. The way you're going right now you're on track to destroy your phone.
Do yourself a favour and click on the link in my signature. It's a resource thread, it contains all the information you'll ever need. I'll put it this way, I read for a week or two before I even started modifying my phones.
Sent from my Evita
John uallowt
redpoint73 said:
Its saying wrong RUU, because its the wrong RUU.
If you are S-on, you can only run an RUU meant for your Telstra version.
It appears you ignored my previous advice to read up on the basic concepts and procedures, before continuing to try to mod the phone.
Click to expand...
Click to collapse
I have not ignored your advised, It rather hard to understand all this, since there is no Indication for the right RUU, since the thread i'm looking at, does not mention anything in regards of using a different RUU.
I apologise If you feel like i'm ignoring your advised, I would rather ask you now, What should I do?
Are you able to do some prompts in regards of what to do?
So far, IMAO I need to to this:
Flash the Correct RUU (Gotta find it first)
Use S-off to Install the Custom ROM (ROM is already copied to the phone's memory)
Install the new Custom ROM, however, not to sure about the GApps, which are google apps.
http://www.reddit.com/r/Android/comments/1kbeoh/gapps_20130813_for_android_43_and_20130812_for/
I guess that you need to copy them before you install the new ROM?
Thank you for your patience.
redpoint73 said:
I think this is a lost cause. You aren't even reading what people have replied to you. I clearly stated in post #4 above, you DO NOT have s-off.
Right in your second screen shot (white bootloader screen) it says S-ON (third line of text). This means you DO NOT HAVE S-OFF.
Click to expand...
Click to collapse
Fair enough, I need to read more about it.
As i Have atm S-ON and I need to have S-off to be able to install the RUU and the custom Rom, I either need to accomplish this :
SuperUser the Phone with the current Stock ROM
or
Install a Rooted ROM, correct?
Desertum said:
I have not ignored your advised, It rather hard to understand all this, since there is no Indication for the right RUU, since the thread i'm looking at, does not mention anything in regards of using a different RUU.
I apologise If you feel like i'm ignoring your advised, I would rather ask you now, What should I do?
Click to expand...
Click to collapse
As you've been told at least 3 times now, what you should do is READ READ READ.
None of this is hard to understand once you start diving into it and learning.
I'm personally not going to spoonfeed you any more steps (and suggest against doing it either), as shortcutting the learning process is only going to turn your phone into an expensive paperweight.
timmaaa said:
Like Redpoint just said, you can't install an RUU from another carrier (the 3.18 RUU is at&t) while you're s-on. You don't have s-off, look at the screenshots you attached earlier, in your bootloader it says s-on. You have an unlocked bootloader which is an entirely different thing.
Unless you've flashed a superuser zip or flashed a rooted ROM you don't have root. Root just means that you have administrative access to system files in a ROM. The real thing you need to install custom ROMs is an unlocked bootloader and a custom recovery.
I'm gonna be honest, you're in over your head and you're ignoring good advice which was given to prevent you from damaging your phone.
You really have two choices: either do a hell of a lot of reading until you have a firm understanding of what you're doing, or leave your phone alone. The way you're going right now you're on track to destroy your phone.
Do yourself a favour and click on the link in my signature. It's a resource thread, it contains all the information you'll ever need. I'll put it this way, I read for a week or two before I even started modifying my phones.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, If you put it that way then it makes more clear, stay away from your phone before you bricked it!
Will read about you've said before,however I have tried several ways to Super SU this phone and nothing works.
http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/
Tried the one above, and no good.
Thanks for the help, will leave it as it is until I feel more confident about how to get this thing going.
Desertum said:
Fair enough, I need to read more about it.
As i Have atm S-ON and I need to have S-off to be able to install the RUU and the custom Rom, I either need to accomplish this :
SuperUser the Phone with the current Stock ROM
or
Install a Rooted ROM, correct?
Click to expand...
Click to collapse
We're getting there, here are the exact steps you need to take:
1) Read a lot.
2) Read some more.
3) Flash a superuser zip on your current stock ROM, or flash a rooted Sense ROM so you have root.
4) Get SuperCID.
5) Get s-off.
6) RUU to latest.
7) Flash whatever ROM you want.
Sent from my Evita
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
Desertum said:
Thank you, If you put it that way then it makes more clear, stay away from your phone before you bricked it!
Will read about you've said before,however I have tried several ways to Super SU this phone and nothing works.
http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/
Tried the one above, and no good.
Thanks for the help, will leave it as it is until I feel more confident about how to get this thing going.
Click to expand...
Click to collapse
Just go to our Android Development section here and flash one of the new Sense 5 ROMs. They're already rooted.
Don't get information/software from anywhere except XDA by the way.
Sent from my Evita
He is already on 2.14 hboot I'm not even sure why he's trying to ruu.
Sent from my HTC One XL using xda app-developers app
31ken31 said:
He is already on 2.14 hboot I'm not even sure why he's trying to ruu.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Good catch. I missed that.
To the OP: you don't need to RUU to install cm10.2 on your device as you already have the required hboot/firmware. Without s-off you will need to manually flash the boot.img using fastboot though.
Sent from my Evita
Related
So I am on hboot 1.45.0013 with s-on, boot loader unlocked and I am rooted.
I also have CWM installed
I have been searching on how to obtain S-off with no luck.
Am I ready to flash roms? or do I need S-off first? Is there even a way to get S-off?
hd2brick said:
So I am on hboot 1.45.0013 with s-on, boot loader unlocked and I am rooted.
I also have CWM installed
I have been searching on how to obtain S-off with no luck.
Am I ready to flash roms? or do I need S-off first? Is there even a way to get S-off?
Click to expand...
Click to collapse
"Drunk Bear" method to obtain S-OFF:
http://forum.xda-developers.com/showthread.php?t=1576672
ICS on unlocked with S-ON:
http://forum.xda-developers.com/showthread.php?t=1508556
^^^^^What he said.
FWIW, I also have HBOOT 1.45.0013, and I have CWM installed (version 5.0.2.7) and have successfully flashed a custom ROM. You do not need S-Off. It's merely a convenience at this point.
The catch is, as posted in the ICS link, if you flash a ROM and need to change the kernel too, the kernel must be flashed through fastboot on S-On phones. "S-Off" don't need to worry about this.
However, for 99.44% of people who flash ROMs, flashing kernels through fastboot is no big deal, and I haven't read yet where someone needed S-Off to accomplish what they were after.
cj chitwood said:
^^^^^What he said.
FWIW, I also have HBOOT 1.45.0013, and I have CWM installed (version 5.0.2.7) and have successfully flashed a custom ROM. You do not need S-Off. It's merely a convenience at this point.
The catch is, as posted in the ICS link, if you flash a ROM and need to change the kernel too, the kernel must be flashed through fastboot on S-On phones. "S-Off" don't need to worry about this.
However, for 99.44% of people who flash ROMs, flashing kernels through fastboot is no big deal, and I haven't read yet where someone needed S-Off to accomplish what they were after.
Click to expand...
Click to collapse
I have had a hard time replacing the splash screen using the splash flasher tool with S-on, I haven't tried to do it manually, because it is my bf's phone, and I feel he should do it.
I forgot that was an option. I flashed my G1's splash screen to a pic of my daughter when she was only a year old and never tried anything after that on that phone or my MT4GS.
cj chitwood said:
^^^^^What he said.
FWIW, I also have HBOOT 1.45.0013, and I have CWM installed (version 5.0.2.7) and have successfully flashed a custom ROM. You do not need S-Off. It's merely a convenience at this point.
The catch is, as posted in the ICS link, if you flash a ROM and need to change the kernel too, the kernel must be flashed through fastboot on S-On phones. "S-Off" don't need to worry about this.
However, for 99.44% of people who flash ROMs, flashing kernels through fastboot is no big deal, and I haven't read yet where someone needed S-Off to accomplish what they were after.
Click to expand...
Click to collapse
You do need S-OFF for ad-free to work without a hitch. otherwise you have to do something through ADB to get it to work. Which can be quite challenging for some that can't even find their way around control panel, let alone cmd
I won't say ad-free is flawless, but it does work on my S-On.
---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------
which reminds me... I need to go install it again.
Thanks I ended up flashing ICS rom with the link you gave me, and my root actually worked. then I did the s-off with the wire trick and all that crazy stuff. now im good to go. not sure what rom to run though :S
cj chitwood said:
I won't say ad-free is flawless, but it does work on my S-On.
---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------
which reminds me... I need to go install it again.
Click to expand...
Click to collapse
Really? It never worked on my s on 3g slide...
gtmaster303 said:
Really? It never worked on my s on 3g slide...
Click to expand...
Click to collapse
Yup, because when I went to a website with ads on it, there were rectangles that were white and no ads. Again it wasn't perfect... on some it worked and some did not. Either way I'll take getting rid of some ads to getting rid of no ads any day
--
Posted from Twitchie, my CyanogenMOD 9 powered HTC DoubleShot
Hello Guys, Im new to this forum but I love it! I have a issue with my htc sensation, I tried flashing a Rom and it got stuck in boot loop.
When i press the volume down and power i get this...
-Revolutionary-
pyramid pvt ship s-off rl
hboot 1.27.1100
radio 10.14.9035.01_m
emmc-boot
jan 13 2012, 17:33:34
now I thought i could fix this since im always flashing roms but at this point ill put any rom on just to get it to work and ill leave it alone forever!
this is what i have all done already
-i already factory reset everything and download the super wipe and flashed it then flashed a rom and noting!
-ive tried using roms that are gingerbread instead of ics and nothing!
-ive tried flashing different roms, and nothing!
-
now here is what i think i dont have the 3.32 firmware but to be completely honest and i have gone to http://forum.xda-developers.com/showthread.php?t=1412618 but i dont know my cid so idk which one to download but i did try 3 and when i try to flash that zip in recovery it says "aborted" and usually when i put it on the root of the card it doesnt read it like ive read it is suppose to ask you if you want to update..
all i know is when i take the battery out its pg5100
i really need help, ive tried everything and i know its fixable i dont wanna give up!
so any help will be great! in advance thank you so much! im loosing sleep trying to fix it this!
I'm assuming you didn't flash the firmware yet right? The easiest way to flash a firmware is to get super cid (11111111). Go hereand follow step 4. Then you can flash this without worrying. The second link is just to the 3.32 firmware.
didn't you super CID? try to super CID...follow fourth step here http://forum.xda-developers.com/showthread.php?t=1192300
then get the 3.32 firmware. your CID will be 11111111 so anyone will work for you.
your main problem is the firmware, don't worry
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
flare4000 said:
I'm assuming you didn't flash the firmware yet right? The easiest way to flash a firmware is to get super cid (11111111). Go hereand follow step 4. Then you can flash this without worrying. The second link is just to the 3.32 firmware.
Click to expand...
Click to collapse
lol one minute apart
flare4000 said:
I'm assuming you didn't flash the firmware yet right? The easiest way to flash a firmware is to get super cid (11111111). Go hereand follow step 4. Then you can flash this without worrying. The second link is just to the 3.32 firmware.
Click to expand...
Click to collapse
the second link didnt work
Ya seems as though all of the links are down grab a 3.32 firmware from this thread http://forum.xda-developers.com/showthread.php?t=1459767 Just place the PG58IMG.zip on the root of your sd and press the volume down and power the phone should automatically detect the zip and ask to update. Make sure you have a good amount of battery.
arabology said:
didn't you super CID? try to super CID...follow fourth step here http://forum.xda-developers.com/showthread.php?t=1192300
then get the 3.32 firmware. your CID will be 11111111 so anyone will work for you.
your main problem is the firmware, don't worry
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
lol one minute apart
Click to expand...
Click to collapse
thanks guys i tried to do this but im stuck it the command doesnt read my phone but it does say fastboot usb on my screen im stuck
Just flash a recovery the same method, from sd card, and flash a custom ROM...
arabology said:
Just flash a recovery the same method, from sd card, and flash a custom ROM...
Click to expand...
Click to collapse
any recovery? where do i download a recovery from?
Step 1 from here.
Proceed to install a ROM there after.
kgs1992 said:
Step 1 from here.
Proceed to install a ROM there after.
Click to expand...
Click to collapse
how am i suppose to start in step one when my phone doesnt turn on so i can install it
jy_ventura said:
how am i suppose to start in step one when my phone doesnt turn on so i can install it
Click to expand...
Click to collapse
Are you saying that your phone won't even reboot to bootloader?
Method 2 & 3 usually work in situations like yours.
arabology said:
didn't you super CID? try to super CID...follow fourth step here http://forum.xda-developers.com/showthread.php?t=1192300
then get the 3.32 firmware. your CID will be 11111111 so anyone will work for you.
your main problem is the firmware, don't worry
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
lol one minute apart
Click to expand...
Click to collapse
Hey guys im trying to supercid but once i put in my first command it says waiting for device and i have it plugged in with my laptop im extremely frustrated but i think this is it...please help me out
jy_ventura said:
Hey guys im trying to supercid but once i put in my first command it says waiting for device and i have it plugged in with my laptop im extremely frustrated but i think this is it...please help me out
Click to expand...
Click to collapse
Does your bootloader say fastboot USB?
Look mate, your Hboot ver is 1.27 S OFF Revolutionary which means you have the right firmware installed. If you really want to be helped, tell me what recovery you're using.
EDIT: Uninstall all HTC related applications from the PC & Install these drivers.
kgs1992 said:
Are you saying that your phone won't even reboot to bootloader?
Method 2 & 3 usually work in situations like yours.
Click to expand...
Click to collapse
noo my phone does go into bootloader im trying method 3 right now
kgs1992 said:
Does your bootloader say fastboot USB?
Look mate, your Hboot ver is 1.27 S OFF Revolutionary which means you have the right firmware installed. If you really want to be helped, tell me what recovery you're using.
EDIT: Uninstall all HTC related applications from the PC & Install these drivers.
Click to expand...
Click to collapse
the recovery im using is clockworkmod recovery v5.0.2.0
thanks
kgs1992 said:
Are you saying that your phone won't even reboot to bootloader?
Method 2 & 3 usually work in situations like yours.
Click to expand...
Click to collapse
when i tried method 3, it didnt even recongize the image so it didnt ask me to update and when i went to install from zip and choose the psg58img it said aborted...
now let me ask you this is their a rom that will work with the stuff i already have on my phone because im willing to use any rom just to get my phone working again!!
jy_ventura said:
noo my phone does go into bootloader im trying method 3 right now
Click to expand...
Click to collapse
jy_ventura said:
the recovery im using is clockworkmod recovery v5.0.2.0
thanks
Click to expand...
Click to collapse
Good. You will now be installing 4ext recovery.
After recovery has been installed, reboot to recovery.
Select wipe|format.
Select format all partitions except SD Card.
Then install your ROM.
jy_ventura said:
when i tried method 3, it didnt even recongize the image so it didnt ask me to update and when i went to install from zip and choose the psg58img it said aborted...
now let me ask you this is their a rom that will work with the stuff i already have on my phone because im willing to use any rom just to get my phone working again!!
Click to expand...
Click to collapse
Have you tried to flash the stock ROM?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
jy_ventura said:
when i tried method 3, it didnt even recongize the image so it didnt ask me to update and when i went to install from zip and choose the psg58img it said aborted...
now let me ask you this is their a rom that will work with the stuff i already have on my phone because im willing to use any rom just to get my phone working again!!
Click to expand...
Click to collapse
It's "PG58IMG.zip" not P"S"G58IMG.zip. If the name is incorrect, then it won't work.
You cannot do it from recovery, you must do it only from bootloader.
The reason I'm insisting on 4EXT is because it's much easier to use.
Follow my instructions properly.
And if you find all this difficult, just go to my tool, link in signature.
When it asks you to connect in HTC Sync mode with debugging enabled, just boot to recovery instead.
kgs1992 said:
It's "PG58IMG.zip" not P"S"G58IMG.zip. If the name is incorrect, then it won't work.
You cannot do it from recovery, you must do it only from bootloader.
The reason I'm insisting on 4EXT is because it's much easier to use.
Follow my instructions properly.
And if you find all this difficult, just go to my tool, link in signature.
When it asks you to connect in HTC Sync mode with debugging enabled, just boot to recovery instead.
Click to expand...
Click to collapse
i made sure the spelling was correct and my phone still doesnt read it...
As the title says. I just bought a hox at&t version and did a root metod and it failed. The phone is still save and I can normally use it. Now I want to re-flash the stock firmware that the phone was runing the first time I used it. I am scared with the fact about I wouldn't update to Jelly Bean beacuse it might contains any corrupt file due the failed root.
Is there a detailed how to'' guide? I only see guys in here says about flash RUU.
please help!
If you are going to give up that easily, than maybe root is not for you.
What firmware number (1.85, 2.20, etc.) is the phone now? What root method did you try? Root method varies by firmware version, so its a common mistake to use the wrong one. Also, even with the correct method, you may need multiple attempts before its successful (not necessarily due to anything you are doing wrong).
If you truly want to return to stock, just find the RUU for your version number. Download to your computer. Connect the phone via USB. Then just run the RUU. Its an .exe, no guide needed.
Links to the RUUs are on my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
thanks for the reply!! now I'm downloading the RUU, but if I do Root and want to come back stock again, only flash the correct RUU file? What about bootloaders (relock)? and kernel?
jics91 said:
thanks for the reply!! now I'm downloading the RUU, but if I do Root and want to come back stock again, only flash the correct RUU file? What about bootloaders (relock)? and kernel?
Click to expand...
Click to collapse
all you need to do is "fastboot oem lock" and run the ruu at the fastboot screen.
jics91 said:
but if I do Root and want to come back stock again, only flash the correct RUU file? What about bootloaders (relock)? and kernel?
Click to expand...
Click to collapse
RUU flashes everything: Stock recovery, radio, kernel, and I believe hboot. It will also wipe the phone, so backup anything you want to keep. As DvineLord said, your bootloader needs to be locked. Other than that, just run the RUU, and it does the rest.
---------- Post added at 01:56 PM ---------- Previous post was at 01:54 PM ----------
jics91 said:
now I'm downloading the RUU,
Click to expand...
Click to collapse
Make sure you dowload the right RUU for your firmware version. RUU will only run if the RUU is the right CID, and same version number or a later one (older RUU will not run).
Hello guys
I've just received att HOX from ebay, and when i enter in bootloader, it's kinda strange,
because it says "EVITA" in bootloader menu.
Bootloader is unlocked, S-OFF, CID-1111111
HBOOT 1.09.0000
I want to flash Android Revolution HD 31.0 JB rom, but it needs Custom recovery, which i can't flash.
Tried several times, but when i want to enter Recovery, says "This build is for development purposes only Do not distribute outside oh HTC ... bla bla" with red text and stucks there.
Also, it needs Firmware.zip, which defends on CID, but i don't know original CID of my phone.
Can i use whatever firmware.zip I want?
Please tell me which firmware should i choose, which recovery should i flash,
and why it says "Evita"? It's not One XL and it's not on Tegra 3 chipset..
Any help would be greatly appreciated ))
It says Evita because it's a One XL, not a One X. Android Revolution is not meant for this phone, so don't try to flash that. Only get ROMs from this forum, the development threads are here and here.
The reason your recovery won't load is probably because you're flashing the wrong one. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone. Just make sure you only get ROMs from the two links I provided before.
Sent from my Evita
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Also, don't mess around with the CID or any firmware zips, it's not necessary.
Sent from my Evita
---------- Post added at 03:24 AM ---------- Previous post was at 03:10 AM ----------
Oh and another thing, if you want to flash any of the latest aosp ROMs you'll need to RUU up to the latest. You can find the 3.18 RUU here. Because you have s-off it doesn't matter that you have SuperCID (11111111).
Sent from my Evita
timmaaa said:
It says Evita because it's a One XL, not a One X. Android Revolution is not meant for this phone, so don't try to flash that. Only get ROMs from this forum, the development threads are here and here.
The reason your recovery won't load is probably because you're flashing the wrong one. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone. Just make sure you only get ROMs from the two links I provided before.
Sent from my Evita
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Also, don't mess around with the CID or any firmware zips, it's not necessary.
Sent from my Evita
---------- Post added at 03:24 AM ---------- Previous post was at 03:10 AM ----------
Oh and another thing, if you want to flash any of the latest aosp ROMs you'll need to RUU up to the latest. You can find the 3.18 RUU here. Because you have s-off it doesn't matter that you have SuperCID (11111111).
Sent from my Evita
Click to expand...
Click to collapse
First of all, thank you for your reply))
But i think it's not XL, i had doubt about it, but phone storage is 16GB, not 32
I've tried and flashed TWRP 2.6 recovery and boot.img of Android Revolution HD 31,
now it says same first, when i try to enter recovery, then loads TWRP. but as i think it cant read internal memory, i tried to WIPE data, but it says no storage/ sd-ext ... are mounted and finishes with error.
Also, phone doesn't power up now. When i power up normally, it shows "This build is for development purposes only Do not distribute outside oh HTC ..." again and stucks there.
Don't know what to do, as i know difference between One X and One XL is internal storage (XL 32 GB)
but definitely it has 16 only..
uNdea said:
First of all, thank you for your reply))
But i think it's not XL, i had doubt about it, but phone storage is 16GB, not 32
I've tried and flashed TWRP 2.6 recovery and boot.img of Android Revolution HD 31,
now it says same first, when i try to enter recovery, then loads TWRP. but as i think it cant read internal memory, i tried to WIPE data, but it says no storage/ sd-ext ... are mounted and finishes with error.
Also, phone doesn't power up now. When i power up normally, it shows "This build is for development purposes only Do not distribute outside oh HTC ..." again and stucks there.
Don't know what to do, as i know difference between One X and One XL is internal storage (XL 32 GB)
but definitely it has 16 only..
Click to expand...
Click to collapse
You clearly don't know the difference between the two models at all. It has nothing to do with the internal storage. I actually know what I'm talking about and I'm trying to stop you from bricking your phone.
Evita is the codename for the One XL. This is the phone you have.
Endeavor is the codename for the One X. You do not have this phone.
Also, the One XL comes in 16gb and 32gb models.
Hopefully that's clear enough for your to understand and you'll stop trying to brick your phone now?
Or you can continue to ignore the educated advice I'm giving you and continue flashing things that aren't meant for your phone and destroy it. It's your choice though.
Sent from my Evita
timmaaa said:
You clearly don't know the difference between the two models at all. It has nothing to do with the internal storage. I actually know what I'm talking about and I'm trying to stop you from bricking your phone.
Evita is the codename for the One XL. This is the phone you have.
Endeavor is the codename for the One X. You do not have this phone.
Also, the One XL comes in 16gb and 32gb models.
Hopefully that's clear enough for your to understand and you'll stop trying to brick your phone now?
Or you can continue to ignore the educated advice I'm giving you and continue flashing things that aren't meant for your phone and destroy it. It's your choice though.
Sent from my Evita
Click to expand...
Click to collapse
Tim is 100% Correct.
Evita = One XL
Endeavor = One X
timmaaa said:
You clearly don't know the difference between the two models at all. It has nothing to do with the internal storage. I actually know what I'm talking about and I'm trying to stop you from bricking your phone.
Evita is the codename for the One XL. This is the phone you have.
Endeavor is the codename for the One X. You do not have this phone.
Also, the One XL comes in 16gb and 32gb models.
Hopefully that's clear enough for your to understand and you'll stop trying to brick your phone now?
Or you can continue to ignore the educated advice I'm giving you and continue flashing things that aren't meant for your phone and destroy it. It's your choice though.
Sent from my Evita
Click to expand...
Click to collapse
I'm sorry for that, I'm don't want to brick my phone.
I don't have more knowledge about it than you, so take my apologies
I had flashed that before I read your post).
I'll try your method and post about result.
Thanks again and sorry for my English.
Your English is fine, don't worry about that. Just make sure you only download ROMs from the two development sections I linked to before.
Sent from my Evita
timmaaa said:
You clearly don't know the difference between the two models at all. It has nothing to do with the internal storage. I actually know what I'm talking about and I'm trying to stop you from bricking your phone.
Evita is the codename for the One XL. This is the phone you have.
Endeavor is the codename for the One X. You do not have this phone.
Also, the One XL comes in 16gb and 32gb models.
Hopefully that's clear enough for your to understand and you'll stop trying to brick your phone now?
Or you can continue to ignore the educated advice I'm giving you and continue flashing things that aren't meant for your phone and destroy it. It's your choice though.
Sent from my Evita
Click to expand...
Click to collapse
timmaaa said:
Your English is fine, don't worry about that. Just make sure you only download ROMs from the two development sections I linked to before.
Sent from my Evita
Click to expand...
Click to collapse
Flashed TWRP and it enters normally, but still when i try Wipe/factory reset, gives error and says that "unable to mount storage, sdcard and etc"
Is it normal?
I'll try to flash 3.18 RUU now, because phone doesn't boot up and I cant place custom ROM on internal storage.
Am i doing it right?
uNdea said:
Flashed TWRP and it enters normally, but still when i try Wipe/factory reset, gives error and says that "unable to mount storage, sdcard and etc"
Is it normal?
I'll try to flash 3.18 RUU now, because phone doesn't boot up and I cant place custom ROM on internal storage.
Am i doing it right?
Click to expand...
Click to collapse
if you are using twrp 2.6 you can just format the SD card in twrp, it should work fine after.
exad said:
if you are using twrp 2.6 you can just format the SD card in twrp, it should work fine after.
Click to expand...
Click to collapse
Thank you, I've formatted SD card and WIPE option has worked!
But i have no idea why i get that message when i try to power on phone normally..
"This build is for development purposes only
Do not distribute outside of HTC without HTC's written permission.
Failure to comply may lead to legal action."
Can i fix it without RUU?
uNdea said:
Thank you, I've formatted SD card and WIPE option has worked!
But i have no idea why i get that message when i try to power on phone normally..
"This build is for development purposes only
Do not distribute outside of HTC without HTC's written permission.
Failure to comply may lead to legal action."
Can i fix it without RUU?
Click to expand...
Click to collapse
That's normal. if it bothers you that much, you can flash a modified hboot. There's a link in the mods section of the resource compilation thread. There's a link in my signature.
exad said:
That's normal. if it bothers you that much, you can flash a modified hboot. There's a link in the mods section of the resource compilation thread. There's a link in my signature.
Click to expand...
Click to collapse
It's nothing if phone will boot up, but it restarts and restarts. Seems bootloop
uNdea said:
It's nothing if phone will boot up, but it restarts and restarts. Seems bootloop
Click to expand...
Click to collapse
What rom did you flash?
exad said:
What rom did you flash?
Click to expand...
Click to collapse
Just flashed Boot.img from Android revolution HD.zip file, nothing more.
Im trying to flash boot.img of stock ICS, maybe it will fix that..
Please link me to the rom you flashed.
Sent from my One X using xda app-developers app
exad said:
Please link me to the rom you flashed.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Flashed Boot.img from this == > > http://forum.xda-developers.com/showthread.php?t=1562603
************
I've flashed RUU 3.18 for evita and that problem is fixed, phone works normally with hboot 2.14.
Will try to flash recovery and some Sense 5 custom rom now. Thanks for help))
uNdea said:
Just flashed Boot.img from Android revolution HD.zip file, nothing more.
Im trying to flash boot.img of stock ICS, maybe it will fix that..
Click to expand...
Click to collapse
Like timmaaa, told you your phone is a evita, so the boot.img you installed from Android revolution HD.zip is not good, My evita is the first evita att issued and it is only 16 GB (referbished for $10.00, got what I payed for )
Hboot 1.09 and boot.img, radio.img, etc..
1.85.502.3_UrDroid_TWRP_Firmware_Aroma_Installer.zip
EDIT: late .. Glad you figured things out
uNdea said:
Flashed Boot.img from this == > > http://forum.xda-developers.com/showthread.php?t=1562603
************
I've flashed RUU 3.18 for evita and that problem is fixed, phone works normally with hboot 2.14.
Will try to flash recovery and some Sense 5 custom rom now. Thanks for help))
Click to expand...
Click to collapse
Mate, I told you in the beginning that Android Revolution is not for your phone. So like Carl said, that boot.img is not for your phone. ONLY EVER GET ROMS FROM THE TWO LINKS I PROVIDED IN MY FIRST REPLY. Also, you don't need to flash the boot.img, you are s-off so it doesn't matter.
Sent from my Evita
[Q]~[HELP] SuperCID, Unlocked, Rooted, and S-OFF, how to restore to stock AT&T ROM?
Hi, geeks,
For my AT&T HTC One X, I have followed you guys all the way to here now: with SuperCID, Bootloader Unlocked (via HTC Dev), Rooted of course, and S-OFF (with touchscreen firmware down-graded).
Now I want to go back to AT&T stock ROM to use the ISIS wallet. Could you please tell me how? I am worried that my phone get bricked!
Thank you so much!
You can just flash a stock at&t ROM which you'll find in our Android Development section. Or you can run the 3.18 RUU. This will also flash stock recovery, hboot, radio, and other firmware modules. The ROM is probably the better and easier option.
Sent from my Evita
Thank you, timmaaa. Do I need to lock the bootloader and so on? I saw it somewhere but can't find the link now.
timmaaa said:
You can just flash a stock at&t ROM which you'll find in our Android Development section. Or you can run the 3.18 RUU. This will also flash stock recovery, hboot, radio, and other firmware modules. The ROM is probably the better and easier option.
Sent from my Evita
Click to expand...
Click to collapse
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
timmaaa said:
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
Click to expand...
Click to collapse
I'm doing the same thing, but to attempt to trade in my phone. I assume that after running the RUU I should relock the bootloader. I want to get rid of the red text.
*EDIT* nevermind. didn't realize that the RUU clears out the *TAMPERED* flag and gets rid of the red text. should be all good now.
One more question, timmaaa: after flashing RUU, the recovery partition will be replaced with the stock recovery, and the S-OFF and boot loader will be kept as it is (based on what I learned from other posts of you). What if I need to flash CM again? I am confused because not many people are doing what I am. Thanks!
timmaaa said:
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
Click to expand...
Click to collapse
Yes, the RUU will install the stock recovery. Your phone will still be s-off and will still have an unlocked bootloader. All you need to do is install TWRP recovery again and then you can flash any ROM you like. Full instructions on how to install a recovery can be found in my How-To Guide For Beginners thread, link in my signature.
Sent from my Evita
Hi, timmaaa, I got a RUU error 155 when flashing RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe.
Seems I need to re-lock the bootloader, which I am reluctant to do. Do I miss anything?
timmaaa said:
Yes, the RUU will install the stock recovery. Your phone will still be s-off and will still have an unlocked bootloader. All you need to do is install TWRP recovery again and then you can flash any ROM you like. Full instructions on how to install a recovery can be found in my How-To Guide For Beginners thread, link in my signature.
Sent from my Evita
Click to expand...
Click to collapse
You don't need to relock if you're s-off. Are you using a 2.0 or 3.0 usb port? Are you using a HTC cable? Are you in fastboot mode? Have you uninstalled HTC Sync Manager?
Sent from my Evita
Hi, timmaaa, I am using USB2.0 on windows XP, with a regular cable, not in fastboot mode, and haven't uninstalled HTC Sync Manager.
I will try flash in fastboot mode again.
timmaaa said:
You don't need to relock if you're s-off. Are you using a 2.0 or 3.0 usb port? Are you using a HTC cable? Are you in fastboot mode? Have you uninstalled HTC Sync Manager?
Sent from my Evita
Click to expand...
Click to collapse
aaronDroid80 said:
I'm doing the same thing, but to attempt to trade in my phone. I assume that after running the RUU I should relock the bootloader. I want to get rid of the red text.
*EDIT* nevermind. didn't realize that the RUU clears out the *TAMPERED* flag and gets rid of the red text. should be all good now.
Click to expand...
Click to collapse
You need to make sure the person you are trading with understands the phone is s-off and bootloader unlocked, and what that means.
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
BBS678 said:
One more question, timmaaa: after flashing RUU, the recovery partition will be replaced with the stock recovery, and the S-OFF and boot loader will be kept as it is (based on what I learned from other posts of you). What if I need to flash CM again? I am confused because not many people are doing what I am. Thanks!
Click to expand...
Click to collapse
If you think you might still want to flash custom ROMs, you need to ask yourself why you want to return to stock in the first place.
Going back to stock if you are s-off, custom recovery, etc. is a step backward, not forward. Aside from getting on the correct hboot, firmware, etc. (or selling/trading your phone like the guy above), there is no benefit to going through all the hassle to running the RUU to get back to stock. Just flash a stock rooted ROM as timmaaa originally mentioned.
EDIT: Missed the part in the OP where it mentioned ISIS. See my response below (#13).
An update (for the forum): In fastboot mode, I have flashed Stock RUU successfully, without locking boot loader. After this, even in stock ROM, ISIS still doesn't work. I think it's caused by the SuperCID and S-OFF.
Timmaaa, do you know how I can SAFELY get SuperCID and S-OFF fixed? Thank you!
BBS678 said:
Hi, timmaaa, I am using USB2.0 on windows XP, with a regular cable, not in fastboot mode, and haven't uninstalled HTC Sync Manager.
I will try flash in fastboot mode again.
Click to expand...
Click to collapse
BBS678 said:
An update (for the forum): In fastboot mode, I have flashed Stock RUU successfully, without locking boot loader. After this, even in stock ROM, ISIS still doesn't work. I think it's caused by the SuperCID and S-OFF.
Timmaaa, do you know how I can SAFELY get SuperCID and S-OFF fixed? Thank you!
Click to expand...
Click to collapse
Reading around, root seems to be the only mod that interferes with ISIS. Its unlikely that s-off would interfere with ISIS. SuperCID? Its possible. Changing from SuperCID is very easy with fastboot. Just search for the command.
Also, be aware that you need a ISIS compatible SIM ("secure element SIM") available from your carrier.
http://www.att.com/shop/apps/isis-mobile-wallet.html#fbid=xHuv6S8moS4
Could be. HTC One X is not available on att.com now, so your link can't explain at this moment.
From here, https://www.paywithisis.com/get-started.html, it says AT&T HTC One X is compatible.
In addition, I do have a ISIS compatible SIM card from AT&T. The reason I suspect it is due to CID is that it is “heard" from this forum that ISIS doesn't work if you put an AT&T SIM card in the T-mobile version of GN3 (unlocked).
redpoint73 said:
Reading around, root seems to be the only mod that interferes with ISIS. Its unlikely that s-off would interfere with ISIS. SuperCID? I suppose its possible, but my gut says no. Especially in light of the following:
I'm thinking it more the issue that the AT&T One X is not a "ISIS ready phone": http://www.att.com/shop/apps/isis-mobile-wallet.html#fbid=xHuv6S8moS4
Also, be aware that you need a ISIS compatible SIM ("secure element SIM") available from your carrier.
Click to expand...
Click to collapse
BBS678 said:
Could be. HTC One X is not available on att.com now, so your link can't explain at this moment.
From here, https://www.paywithisis.com/get-started.html, it says AT&T HTC One X is compatible.
Click to expand...
Click to collapse
Yes, I later realized that One X is not available at all anymore from AT&T (and that it is supposed to be ISIS ready), and revised my above response accordingly.
BBS678 said:
In addition, I do have a ISIS compatible SIM card from AT&T. The reason I suspect it is due to CID is that it is “heard" from this forum that ISIS doesn't work if you put an AT&T SIM card in the T-mobile version of GN3 (unlocked).
Click to expand...
Click to collapse
It could also be that they are looking at the phone model number. So SuperCID is a possibility, but not certain.
Its easy to change from SuperCID with a simple fastboot command. Just search this forum for the proper syntax.
---------- Post added at 02:43 PM ---------- Previous post was at 02:32 PM ----------
Here is the command to change from CID:
fastboot oem writecid CWS__001
(note that CWS__001 has two underscores)
Thank you! I learned from this forum that changing S-OFF to S-ON is very risky, and currently S-OFF relies on a SuperCID, so I think it's also risky to change the CID back. Have you ever tried? I need more opinions on this before I take the risk.
BBS678 said:
Thank you! I learned from this forum that changing S-OFF to S-ON is very risky, and currently S-OFF relies on a SuperCID, so I think it's also risky to change the CID back. Have you ever tried? I need more opinions on this before I take the risk.
Click to expand...
Click to collapse
I honestly doubt s-off is blocking ISIS. S-off is exclusively an HTC invention, and I doubt ISIS would care about such a thing. I would recommend to leave s-off alone.
I wouldn't say its "risky" to change CID. As long as you still have s-off, I don't see any reason to still have SuperCID. But even so, you can still use the correct exploit to change back to SuperCID.
Hi, timmaaa, could you please shed some lights on this (change back to stock CID) please? Thanks!
here is my other post about ISIS: http://forum.xda-developers.com/showthread.php?p=49822333
redpoint73 said:
I honestly doubt s-off is blocking ISIS. S-off is exclusively an HTC invention, and I doubt ISIS would care about such a thing. I would recommend to leave s-off alone.
I wouldn't say its "risky" to change CID. As long as you still have s-off, I don't see any reason to still have SuperCID. But even so, you can still use the correct exploit to change back to SuperCID.
Click to expand...
Click to collapse
Everything that @redpoint73 has said is correct. There's pretty much no risk involved in changing your CID back to stock, having s-off does not rely on SuperCID. You can try changing your CID using the command that redpoint gave before.
There's pretty much no risk involved with going from s-off to s-on either. I don't know where you read that but I believe you're misunderstanding the information. Personally I wouldn't go back to s-on though because I don't believe that is affecting your ability to run ISIS. Plus getting s-off again can be tricky sometimes.
Sent from my Evita