I try to find out, if it is possible to change the CID string inside the RUU, so that it is possible to install RUU on a phone with a carrier CID, like VODAP102 or so?
I. e. my phone has VODAP102. Inside the RUU the CID is HTC__001. I simply swap that to VODAP102 and the CID check will be confirmed.
What do u think? possible?
mistermanko said:
I try to find out, if it is possible to change the CID string inside the RUU, so that it is possible to install RUU on a phone with a carrier CID, like VODAP102 or so?
I. e. my phone has VODAP102. Inside the RUU the CID is HTC__001. I simply swap that to VODAP102 and the CID check will be confirmed.
What do u think? possible?
Click to expand...
Click to collapse
I tried to do that for my orange phone and failed miserably. I kept getting errors when trying to insert the modified text into the zip file. Had to change cid on the phone itself and was able to run stock ruu. There is a tutorial on how to do this in the Q&A section.
You can't or you'll break the signature.
I'm one of the unlucky guys with s3 processor. No way to change the CID, unless s-off will be available.
mistermanko said:
I'm one of the unlucky guys with s3 processor. No way to change the CID, unless s-off will be available.
Click to expand...
Click to collapse
You cab change it, just not 11111111.
I think HTC__001 should work.
Sent from my locked, tampered ville
Why do u give advices you can't authorize?
This is not working, tested a dozen times. Possibly cause the partitions can't be edited until s - off is delivered. It seems it will be like the Sensation, which has the same processor, it got Cid change not befor s-off was available.
mistermanko said:
Why do u give advices you can't authorize?
This is not working, tested a dozen times. Possibly cause the partitions can't be edited until s - off is delivered. It seems it will be like the Sensation, which has the same processor, it got Cid change not befor s-off was available.
Click to expand...
Click to collapse
The One S S4 doesn't seem like it has S-OFF, does it? And it manages to. So it does NOT require S-OFF.
I said that because some people have managed to get HTC__001 on their S3.
usaff22 said:
The One S S4 doesn't seem like it has S-OFF, does it? And it manages to. So it does NOT require S-OFF.
I said that because some people have managed to get HTC__001 on their S3.
Click to expand...
Click to collapse
Who? There is no one on xda, is there? Anyway, the s3 has a complete other base than the s4, which makes it more complex to cook Rom for it. As I said, the s3 is more like the Sensation, which means that the availability for soff on s3 is completely different from the same thing on s4. I guess s3 users have to wait way longer than s4 users, if ever soff will be available on both.
mistermanko said:
Who? There is no one on xda, is there? Anyway, the s3 has a complete other base than the s4, which makes it more complex to cook Rom for it. As I said, the s3 is more like the Sensation, which means that the availability for soff on s3 is completely different from the same thing on s4. I guess s3 users have to wait way longer than s4 users, if ever soff will be available on both.
Click to expand...
Click to collapse
Your translation seems a bit weird.
The S3 has no more of a complex base than the S4. The S3 just doesn't have enough developers because not many people have it.
Sent from my locked, tampered ville
usaff22 said:
Your translation seems a bit weird.
The S3 has no more of a complex base than the S4. The S3 just doesn't have enough developers because not many people have it.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
So and how do you explain the differences for changing the CID? If s4 and s3 were alike, why is it not working? By the same reason as there aren't that much custom Roms. It's simply a complete different process to build a Rom for s3 than for s4. Ask torxxx, he is the only guy who builded a s3 Rom.
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 am sorry, because this have probably been asked many times, but I have a little more specific question. I have HTC Sensation rooted, and S-OFF. Now I want to send it to the service under warranty, because I noticed there is a dust under my screen.
I know what I have to do, but I dont know which default rom should I choose, so they definitely would not suspect anything. Does it have to be carrier specific or just some random EU rom? I am from Slovenia, my carrier is Simobil (Vodafone).
Any help would be much appreciated. Thanks in advance.
you need to flash one based on your cid which kinda gives you carrier,country info
use this guide as reference
Thank you, i just read this, however I still dont know how to find the right ruu for my phone. There is no Simobil Slovenia on the ruu list. Any other way to find out which rom to flash? The thing is I dont really remember whether I changed my CID at some point or not, so I might not be able to see/find the correct one.
Thanks again.
Ok here is what I found out now:
If i check for CID via fastboot i get this: 11111111 (i remember now, i set this)
But if i check it via application CIDgetter i get this: HTC_032
Q: Is this HTC_032 the true default CID or it could be just the info of currently installed rom, which is Viper 1.3.5 ?
vrocipes said:
Ok here is what I found out now:
If i check for CID via fastboot i get this: 11111111 (i remember now, i set this)
But if i check it via application CIDgetter i get this: HTC_032
Q: Is this HTC_032 the true default CID or it could be just the info of currently installed rom, which is Viper 1.3.5 ?
Click to expand...
Click to collapse
Hi,
CIDGetter will show you your original CID.
When you check it via fastboot,you will get your ACTUAL CID.
If you are s-off,then , you should be able to run a European RUU and get back to stock.
Then, follow the guide ganesh gave you to s-on.
vrocipes said:
Ok here is what I found out now:
If i check for CID via fastboot i get this: 11111111 (i remember now, i set this)
But if i check it via application CIDgetter i get this: HTC_032
Q: Is this HTC_032 the true default CID or it could be just the info of currently installed rom, which is Viper 1.3.5 ?
Click to expand...
Click to collapse
the cid you got via fastboot is the current one you are having
and HTC_032 is the rom cid ..so if you are having stock rom ..it represents your actual cid
Thank you both for your answers. Hmm, so one of you think that CIDgetter gives you original cid, and one thinks it gives you the CID of current rom. If ganeshp is right, then I still dont know my original CID, as currently I have Viper S 1.3.5 rom :// If malybru is right then I have to flash rom with HTC_032 CID and not just any European rom? Again it is important, because I dont want to get rejected on my warranty...
Thanks again.
vrocipes said:
Thank you both for your answers. Hmm, so one of you think that CIDgetter gives you original cid, and one thinks it gives you the CID of current rom. If ganeshp is right, then I still dont know my original CID, as currently I have Viper S 1.3.5 rom :// If malybru is right then I have to flash rom with HTC_032 CID and not just any European rom? Again it is important, because I dont want to get rejected on my warranty...
Thanks again.
Click to expand...
Click to collapse
both of us (me and Malybru ) are saying the same thing
cid from fastboot ..gives you the actual/current cid you have right now
cid from cid getter ..will give you the rom cid (in case of viper it is HTC__032)
also based on your country ..i think the fitting RUU is indeed is of European Unbranded one (as malybru said )
if the phone is not linked to carrier (like contract phone ) then European unbranded is the right RUU
It has been bought through carrier contract, but they stopped locking them, but it could still be locked in case it was from old stock... I'll have to try that, so in case it is locked to the carrier, I need different rom? Im sorry for so many questions but im really lost in finding the right rom.
Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.
Bubbled said:
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
Click to expand...
Click to collapse
Unfortunately the answers are no and no. JB is decent even on fully stock AT&T, you will just have to look the other way when scrolling through your app tray
I don't think the current root methods allow for the 3.18 build to gain root. Might be in the 2.20 boat all over again until someone can find a definite procedure.
soooooooooooooooooooooo lame. my rezound had viper rez rom and it was based off one x jb but had all the tweaks and stuff so right now its like a major downgrade lol
guess i'll cry and wait for the HTC One to come out later this month, since i only grabbed the one x cause it was literally 11 cents at walmart with a 14 day return and my rezound is acting up and randomly restarting/tanking battery!
sigh
thanks for the info though Groovy
Bubbled said:
Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.
Click to expand...
Click to collapse
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...
lightflier said:
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...
Click to expand...
Click to collapse
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2
iElvis said:
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
OK...
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Sent from my Nexus 7 using xda premium
panda_mode said:
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Click to expand...
Click to collapse
Damn that's annoying! If that were me I would sell my AT&T phone and with the cash buy an overseas One XL model with 32GB
juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Sent from my VENOMized HoxL
area51avenger said:
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Click to expand...
Click to collapse
I suppose it doesn't hurt to try. Otherwise, I'd just take the phone back, if root/S-off, etc. is important to the OP. I assume 11 cents is a subsidized price. So no point in using up an upgrade on a phone that can't be modded, if he wants to get the HTC One when its released.
OP may also check to see if the store has any older stock with 2.20 firmware (or any previous firmware version except 3.18). Phones with 3.18 out of the box must be very new, so I wouldn't be surprised if they had some older stock also.
I returned the one x today. will be looking into the t-mobile version of the HTC One which they told me comes out friday the 22nd. being a new phone i know i wont be able to do any mods or anything for a while, but that won't take long with the awesome Devs we have here! All the other models of the One X were sold out, and im guessing that someone realized that the new firmware was Out of Box so picked em all up. only had 2-3 stores with one each so its possible. now all the new stores have the new firmware no big deal, i'd prefer an HTC DNA anyways, but we'll see what the One is all about.
redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.
Techinstein said:
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.
Click to expand...
Click to collapse
Yes, the CID for AT&T is cws_001 on all of the previous firmware versions, as well. This hasn't changed. cws__001 is blocked on HTCDev.com.
So i have the key for my past bootloader unlock can i use it?
Enviado desde mi HTC One X usando Tapatalk 2
coldrazor said:
So i have the key for my past bootloader unlock can i use it?
Click to expand...
Click to collapse
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.
redpoint73 said:
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.
Click to expand...
Click to collapse
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.
exad said:
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.
Click to expand...
Click to collapse
Really? Kinda negates part of the purpose of having S-off, doesn't it?
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.
hey everyone, i had my telstra one xl on JB for awhile then i wanted to do the newest update from them so upon reading up on it i need to have supercid and s-off, so i thought no worries i'll check my cid first which was telst001 (or something like that), found a one click script and changed to the supercid, so it was 11111111, sweet now to do s-off which failed to flash the RUU, i needed to relock the bootloader, so i relocked it.
problem is now its stuck in a bootloop to fastboot and wont show up in ADB devices, i also cant get into twrp in recovery now.
is there any way to fix this or throw the phone out?
It's a bit difficult to make out what you're saying in parts of that post.
Was s-off successful?
Was the RUU successful?
Which RUU did you use?
What are your current bootloader details?
Sent from my Evita
sirus17 said:
so i thought no worries i'll check my cid first which was telst001 (or something like that), found a one click script and changed to the supercid, so it was 11111111,
Click to expand...
Click to collapse
Did you actually verify that you had SuperCID? I don't think there is a one-click for the Telstra version. The one-click app for SuperCID I'm aware of is intended for AT&T, and will fail with any other CID.
Which may actually be a good thing (if SuperCID failed). Since if a Jellybean RUU is flashed with SuperCID and s-on (its not clear whether you were successful with s-off) it will pretty much a guaranteed brick.
sirus17 said:
is there any way to fix this or throw the phone out?
Click to expand...
Click to collapse
If the screen comes on, its probably possible to recover. But we need more info as timmaaa indicated above.
There is actually a one-click tool for the Telstra version, I stumbled across it very soon after getting my phone mid last year. I found it on an Australian Android site, I think it was Ausdroid.
I'm not sure whether the tool is specifically for the Telstra version alone, but it definitely works on Telstra Evitas as I used it on my fiance's Evita (and mine which is a Hong Kong model).
Sent from my Evita
I thought the one click tool here supported AT&T, Rogers and Telstra CID changing.
twistedddx said:
I thought the one click tool here supported AT&T, Rogers and Telstra CID changing.
Click to expand...
Click to collapse
Really not sure, now that I look into it more. If its the old one by DesignGears, it does work with Rogers, but doesn't seem to mention Telstra (at least if I just search the thread for "Telstra"): http://forum.xda-developers.com/showthread.php?t=1672284
And x-factor also fails for any CID except AT&T, if I understand correctly. So it seems these scripts all look for certain CIDs, so if its not explicitly included, they will fail. Of course, if there is one made specifically for Telstra (as timmaaa mentioned) it apparently wasn't posted on XDA.
But really my main point is that the OP needs to verify and be clear on this, as well as several other factors.