I have used the WeakSuace apk to successfully root the HTC ONE XL on Stock 4.2.2! I hope this will help every one on the 4.2.2 update.
Credits:
vuln - jcase
exploit - jcase & beaups
icon - mattlgroff
Dr_Drache - lots of testing
http://forum.xda-developers.com/showthread.php?t=2699091 <-------- Click for instructions, download, and credit etc.
NOTE:
-It might say root failed or something, just run the app again and install SuperSU from playstore
-This root is temporary, every time you reboot, the device will automatically reroot
-Tested on ATT variant
-Not sure if recovery or installing roms will work
-Not responsible for anything that happens to your device
ENJOY!
This is in the right section.
Sent from my Evita
---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------
If this is indeed confirmed to be working by some others, you might want to change the title to "at&t One X 5.18 Root Method". All other variants of the Evita are able to be rooted via traditional means, and have been the whole time, only the at&t variant hadn't been able to.
Sent from my Evita
timmaaa said:
This is in the right section.
Sent from my Evita
---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------
If this is indeed confirmed to be working by some others, you might want to change the title to "at&t One X 5.18 Root Method".
Click to expand...
Click to collapse
Agree. General is the correct forum section. Development is for posting your own work. Linking to somebody else's thread is not Development.
Have you tried firewater after achieving root with weaksauce? It's working for the vzw one with 4.4.2
Sent from my HTC PG09410 using xda app-developers app
scotty1223 said:
Have you tried firewater after achieving root with weaksauce? It's working for the vzw one with 4.4.2
Sent from my HTC PG09410 using xda app-developers app
Click to expand...
Click to collapse
I have tried with no success on evita stock 4.2.2.
What about using the hex edit method to change your CID after using Weaksauce?
Sent from my Evita
timmaaa said:
What about using the hex edit method to change your CID after using Weaksauce?
Sent from my Evita
Click to expand...
Click to collapse
Already tried. Fastboot oem readcid ---- cws_001.
So basically Weaksauce is useless for this cause.
Sent from my Evita
timmaaa said:
So basically Weaksauce is useless for this cause.
Sent from my Evita
Click to expand...
Click to collapse
What about this method http://forum.xda-developers.com/showthread.php?t=1732980? Is it safe? Don't want to brick my device..
ttol3g said:
What about this method http://forum.xda-developers.com/showthread.php?t=1732980? Is it safe? Don't want to brick my device..
Click to expand...
Click to collapse
Did you read the first pre-requisite?
Sent from my Evita
timmaaa said:
Did you read the first pre-requisite?
Sent from my Evita
Click to expand...
Click to collapse
Sure. But in downloaded zip spoofpartitions/mmcblk0p4MOD has cid 11111111 and in mmcblk0p5MOD (offset 00000010) 11111111. Steps are similar to this http://forum.xda-developers.com/showthread.php?t=1671396 where "8. Change CWS__001 to 11111111 and save the file as mmcblk0p4MOD. This will give you SuperCID as well". Am i wrong? Or there is another hex editing method?
ttol3g said:
Sure. But in downloaded zip spoofpartitions/mmcblk0p4MOD has cid 11111111 and in mmcblk0p5MOD (offset 00000010) 11111111. Steps are similar to this http://forum.xda-developers.com/showthread.php?t=1671396 where "8. Change CWS__001 to 11111111 and save the file as mmcblk0p4MOD. This will give you SuperCID as well". Am i wrong? Or there is another hex editing method?
Click to expand...
Click to collapse
My point was that you need root and SuperCID already. That method is to unlock your bootloader, and is really only for a specific firmware version. What is your end goal? What are you trying to do?
Sent from my Evita
timmaaa said:
My point was that you need root and SuperCID already. That method is to unlock your bootloader, and is really only for a specific firmware version. What is your end goal? What are you trying to do?
Sent from my Evita
Click to expand...
Click to collapse
I'm trying to unlock bootloader. I thought once i get supercid i can unlock it through htcdev.
Yes that's true, but how is the method you linked to going to help you?
Sent from my Evita
timmaaa said:
Yes that's true, but how is the method you linked to going to help you?
Sent from my Evita
Click to expand...
Click to collapse
I dont know. Thought these "spoofpartitions" do the trick. So mmcblk0p5,6,13,26 not needed?
The problem is you're not paying attention to the details, the first pre-requisite is that you already have root and SuperCID, plus that exploit is specifically for a very early firmware. You need root to do that, and you can't get root until you've unlocked your bootloader, see where I'm going here? My suggestion is to try Weaksauce, and then see if hex editing your CID will work with the Weaksauce temp root. I believe this is your only option at the moment.
Sent from my Evita
Ok. Hope someone can make this info helpful. Weaksause does work on evita ATT. I don't know what use having root to the xbin folder does for us. Please fill me in.
I did get Firewater to run by copying it to the folder /data/local/tmp. Using adb you can chmod 755 those folders and copy not push Firewater there and then run it. I get through 12 bottles then it fails. Perhaps if we knew what other folders needed more rights for firewater we could change them too.
Anyone know what firewater does?
I also tried the manual hex edit. Can't get my edited file to save to the needed location and can't change that locations rights with adb.
More ideas to try?
Raistlen0 said:
Ok. Hope someone can make this info helpful. Weaksause does work on evita ATT. I don't know what use having root to the xbin folder does for us. Please fill me in.
I did get Firewater to run by copying it to the folder /data/local/tmp. Using adb you can chmod 755 those folders and copy not push Firewater there and then run it. I get through 12 bottles then it fails. Perhaps if we knew what other folders needed more rights for firewater we could change them too.
Anyone know what firewater does?
I also tried the manual hex edit. Can't get my edited file to save to the needed location and can't change that locations rights with adb.
More ideas to try?
Click to expand...
Click to collapse
Did you meet all of firewaters prerequisites:? Including ADB reboot and having a working data connection?
Was fire water running in a root shell?
Sent from my HTC One VX using Tapatalk
Ok not all prereqs because it wanted you to push with adb but that did not work and yes a reboot but you have to chmod the folder before running firewater. WeakSauce is only temp root so after reboot the 755 rights to /data /data/local and /data/local/tmp have to be re-given. So you can not run firewater right away. Now the copy of firewater does stay in that location after a reboot so you don't have to recopy it.
Data connection was a yes. It wasn't the best connection but it had one at the time.
Firewater has a prereq of being rooted and unlocked boot loader so maybe that's the problem too.
All I want is to get my CID changed so I can get my bootloader unlocked.
I am hoping letting everyone know that there are other folders that permissions can be changed on (not just xbin) with using weaksuace; will maybe help someone figure away to get a full root so the CID file can be edited.
thanks, I will try that.
Related
So my ATT One X is soft bricked and when I run RUU_Evita_UL_Cingular_US-1.82.502 It gives me the customer ID error.
I rooted, unlocked bootloader, and flashed CMR, but it is now no longer rooted and the bootloader is relocked.
I did modify the CID to "11111111" to unlock the bootloader, but without me being rooted I am unable to put the original "mmcblk0p4" back on (idk if that even matters.) I have no backups and absolutely everything is erased.
I did flash the stock recovery img file, but I don't know if it was relevant to international One X or if there is one specifically for ATT One X.
I guess a fix would be making a goldcard, without an sd card somehow....
Thanks for the Help.
Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium
_MetalHead_ said:
Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I was actually using the 1.7 RUU
I'll try 1.82 then 1.85. Hopefully that will work.
Thanks for the quick reply! :good:
Have you tried to relocking the boot loader?
fastboot oem lock
Then run ruu.
The ruu will flash the stock recovery.
Sent from my HTC One X using xda premium
Still not going through and getting same error....
Any ideas?
Thanks.
Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium
18th.abn said:
Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
No. I'm in US on ATT network. And yes I did change the CID to 11111111 because I used that method to unlock my bootloader.
I've tried several RUUs for my phone and still get same error. If I were to verify I had changed the CID I would have to be rooted.
Is it possible to root a soft-bricked device????
What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
---------- Post added at 08:51 PM ---------- Previous post was at 08:44 PM ----------
I was stuck with a soft brick when I interrupted the installation of a ROM that was a bad download.
I was able to do what I said in my previous post and it fixed me right up
gunnyman said:
What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
Click to expand...
Click to collapse
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.
ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse
gunnyman said:
ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse
ArcriusOneX said:
gunnyman said:
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse
gunnyman said:
ArcriusOneX said:
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse
ArcriusOneX said:
gunnyman said:
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse
yeah I like it better myself it's faster.
glad you're all fixed
Click to expand...
Click to collapse
On site htcdev.com, not allowed, write MID not supported
How i can unlock bootloader? Then i need super CID
Regards
idhamitov said:
On site htcdev.com, not allowed, write MID not supported
How i can unlock bootloader? Then i need super CID
Regards
Click to expand...
Click to collapse
This should help.http://forum.xda-developers.com/showthread.php?t=1672284
idhamitov said:
On site htcdev.com, not allowed, write MID not supported
How i can unlock bootloader? Then i need super CID
Regards
Click to expand...
Click to collapse
You need SuperCID first, then go to HTC dev
I give eroor on root my device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
AGAIN REBOOT
Err, what version of the phone do you have?
If its anything but AT&T, you can get the bootloader unlocked without SuperCID. Then just install custom recovery and install SuperSU from recovery.
If its an AT&T branded version, what firmware number are you on (1.73, 1.85, 2.20, etc.)?
i thought "write MID not supported" means that you are on 2.20 and this means that it cant be unlocked? (well at least not yet )
I have LOCKED bootloader
And Software 1.85.502.3 710RD
Which root method are you using? Please link to it, so we can confirm you are using the right one.
Even if using the correct one, the correct 1.85 method sometimes takes multiple attempts for some people.
Guys I think he's in the wrong forum check this post by him unles he just got another phone this was just posted on 8-19 in the one v forum
idhamitov said:
I have PRIMOU PVT SHIP S-OFF RL
HBOOT-1.16.0000
How i can change CID???
Click to expand...
Click to collapse
Sent from my HTC One XL using Forum Runner
I can't remember what errors I had but I remember having some similar to those. If you look back in the developer section you should find beanups manual method, which worked for me.... Eventually
Sent from my HTC One XL using xda premium
I had permission problem with rooting it in w7. I had to do it manually vs Ubuntu as root.
Sent from my One X using xda app-developers app
OneClick CID Spoof
CID spoof by grankin01
Script by DesignGears and GameGod72
Use this at your own risk!
grankin01 and Designgears are not responisble for any damages!
By pressing any key you understand the risks.
Press any key to continue . . .
Make sure your device has usb debugging mode enabled, and is rooted!
Press any key to continue . . .
Restarting ADB
Pulling files
Checking files
Couldn't pull files from device. Your device was not altered.
Press any key to continue . . .
Software 1.85
I am coming from an HTC Sensation that I ran many custom roms. It is set up now with Elegancia Pegasus. That is due to turn in as I am no longer with T-Mobile.
I am rooted. I have Busy Box Pro, Rom Toolbox Pro and SuperSu saying I do. Is there another check to make sure I am rooted. I got the Error 160 Message from HTC on the bootloader unlock.
Please advise.
SveninFla said:
OneClick CID Spoof
CID spoof by grankin01
Script by DesignGears and GameGod72
Use this at your own risk!
grankin01 and Designgears are not responisble for any damages!
By pressing any key you understand the risks.
Press any key to continue . . .
Make sure your device has usb debugging mode enabled, and is rooted!
Press any key to continue . . .
Restarting ADB
Pulling files
Checking files
Couldn't pull files from device. Your device was not altered.
Press any key to continue . . .
Software 1.85
I am coming from an HTC Sensation that I ran many custom roms. It is set up now with Elegancia Pegasus. That is due to turn in as I am no longer with T-Mobile.
I am rooted. I have Busy Box Pro, Rom Toolbox Pro and SuperSu saying I do. Is there another check to make sure I am rooted. I got the Error 160 Message from HTC on the bootloader unlock.
Please advise.
Click to expand...
Click to collapse
Yes you can download terminal emulator from the market. Open it up and type "Su" without quotation mark. If a pop-up window shows up ask for root permission then you are rooted. If not then you're not.
Sent from my One X using xda app-developers app
Got it. Thanks for the advice. I also believe I got the other part handled too. Will, know tonight for sure.
Sent from my HTC One X using xda premium
redpoint73 said:
Err, what version of the phone do you have?
If its anything but AT&T, you can get the bootloader unlocked without SuperCID. Then just install custom recovery and install SuperSU from recovery.
If its an AT&T branded version, what firmware number are you on (1.73, 1.85, 2.20, etc.)?
Click to expand...
Click to collapse
I am new in 1X, can you please tell me the detail how to unlock bootloader? My phone is one X Roger. Software number: 1.94.631.3
I tried to go to htcdev but dont have the oneX in the list of devices support
1 more question: so after unlock bootloader, what can i do next to install the custom rom?
idhamitov said:
On site htcdev.com, not allowed, write MID not supported
How i can unlock bootloader? Then i need super CID
Regards
Click to expand...
Click to collapse
in china I have one step unlock but now i can't give you url
---------- Post added at 09:22 AM ---------- Previous post was at 09:16 AM ----------
idhamitov said:
On site htcdev.com, not allowed, write MID not supported
How i can unlock bootloader? Then i need super CID
Regards
Click to expand...
Click to collapse
super CID need money
thinhletien said:
I am new in 1X, can you please tell me the detail how to unlock bootloader? My phone is one X Roger. Software number: 1.94.631.3
I tried to go to htcdev but dont have the oneX in the list of devices support
Click to expand...
Click to collapse
It should be there, but I don't really know, I'm not on Rogers. Hopefully somebody on Rogers can help on this.
thinhletien said:
1 more question: so after unlock bootloader, what can i do next to install the custom rom?
Click to expand...
Click to collapse
Flash TWRP (custom recovery). Then you can put the ROM on your SD can flash from recovery.
---------- Post added at 01:35 PM ---------- Previous post was at 01:32 PM ----------
j626914269 said:
super CID need money
Click to expand...
Click to collapse
No. You just need root and this: http://forum.xda-developers.com/showthread.php?t=1672284
Select other at htcdev.
WR
Sent from my HTC One X
I just got a AT&T HTC One X, and I never dealt with a HTC before (mostly Samsung). Right now the HTC is pure stock AT&T firmware 1.85. I need some helping guiding me what steps to take cause I'm confuse by it all. This is what I have so far from my research:
Step 1: RUU to 2.20? (not entirely sure on this)
Step 2: Use toolkit to get root
Step 3: Not sure which method to use but I need Supercid to 22222222 because HTCdev blocked AT&T and 11111111.
Step 4: Unlock Bootloader
Step 5: S-OFF, (is facepalm compatible with AT&T X?)
Step 6: Flash roms and have fun.
I appreciate any help and please tell me if I miss some steps.
deathsycthehe11 said:
I just got a AT&T HTC One X, and I never dealt with a HTC before (mostly Samsung). Right now the HTC is pure stock AT&T firmware 1.85. I need some helping guiding me what steps to take cause I'm confuse by it all. This is what I have so far from my research:
Step 1: RUU to 2.20? (not entirely sure on this)
Step 2: Use toolkit to get root
Step 3: Not sure which method to use but I need Supercid to 22222222 because HTCdev blocked AT&T and 11111111.
Step 4: Unlock Bootloader
Step 5: S-OFF, (is facepalm compatible with AT&T X?)
Step 6: Flash roms and have fun.
I appreciate any help and please tell me if I miss some steps.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1709296 <--- root method for 1.85 I would try that before RUUing up to 2.20
I would try 11111111 first since that's what SuperCID gives you be default. If that doesn't work, then I would fastboot oem writecid 22222222 You can only change CID once without S-OFF so make sure to enter it right.
Other than that, you seem to be on the right path.
S-OFF directions are in the onexl orig. android dev. section so yes, compatible.
Good Luck, don't brick.
exad said:
http://forum.xda-developers.com/showthread.php?t=1709296 <--- root method for 1.85 I would try that before RUUing up to 2.20
I would try 11111111 first since that's what SuperCID gives you be default. If that doesn't work, then I would fastboot oem writecid 22222222 You can only change CID once without S-OFF so make sure to enter it right.
Other than that, you seem to be on the right path.
S-OFF directions are in the onexl orig. android dev. section so yes, compatible.
Good Luck, don't brick.
Click to expand...
Click to collapse
The 1.85 root seems a bit more complicated than the toolkit for 2.20. Which SuperCid method should I use then?
Hexedit your Cid.
Sent from my One X using xda app-developers app
exad said:
Hexedit your Cid.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hey Exad, the day has come when I need to ask your advice on something. I'm gonna RUU up to 3.18 then downgrade my TS firmware so I can have a look at these new Carbon builds running the 3.4 kernel (which don't play nice with my current setup). So I need to gain SuperCID in order to s-off, having a Hong Kong issue phone on 1.85 never required me to have SuperCID in order to root. Anyway long story short, my question is: I should be able to just issue the following fastboot command in order to gain SuperCID right?
fastboot oem writecid 11111111
That should be fine yeah?
timmaaa said:
Hey Exad, the day has come when I need to ask your advice on something. I'm gonna RUU up to 3.18 then downgrade my TS firmware so I can have a look at these new Carbon builds running the 3.4 kernel (which don't play nice with my current setup). So I need to gain SuperCID in order to s-off, having a Hong Kong issue phone on 1.85 never required me to have SuperCID in order to root. Anyway long story short, my question is: I should be able to just issue the following fastboot command in order to gain SuperCID right?
fastboot oem writecid 11111111
That should be fine yeah?
Click to expand...
Click to collapse
No, only if you have already achieved s-off, you can change by "fastboot oem writecid" Have to hex edit it if not.
Sent from my HTC One
Exad said in his post above that you can edit it once while s-off though.
Sent from my Evita using XDA Premium
timmaaa said:
Exad said in his post above that you can edit it once while s-off though.
Sent from my Evita using XDA Premium
Click to expand...
Click to collapse
I think he meant BEFORE achieving s-off, you can change your cid ONCE. However, after gaining s-off, you can change ur cid as many as you want.
Sent from my HTC One
timmaaa said:
Exad said in his post above that you can edit it once while s-off though.
Sent from my Evita using XDA Premium
Click to expand...
Click to collapse
That should be correct
Sent from my HTC One X using Tapatalk 2
Thug_4_Life said:
I think he meant BEFORE achieving s-off, you can change your cid ONCE. However, after gaining s-off, you can change ur cid as many as you want.
Sent from my HTC One
Click to expand...
Click to collapse
Yeah and that's exactly what I want to do, and what I was asking. I need to change my CID once, to 11111111, so I can s-off.
Sent from my Evita using XDA Premium
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
timmaaa said:
Exad said in his post above that you can edit it once while s-off though.
Sent from my Evita using XDA Premium
Click to expand...
Click to collapse
Oops, I meant while s-on.
Sent from my Evita using XDA Premium
Yes. Unless you don't trust me haha
Sent from my HTC One
Thug_4_Life said:
Yes. Unless you don't trust me haha
Sent from my HTC One
Click to expand...
Click to collapse
No disrespect man, but you've contradicted yourself above. I prefer confirmation from someone like InflatedTitan or Exad, as I know without a shadow of a doubt they know what they're talking about.
Sent from my Evita using XDA Premium
timmaaa said:
No disrespect man, but you've contradicted yourself above. I prefer confirmation from someone like InflatedTitan or Exad, as I know without a shadow of a doubt they know what they're talking about.
Sent from my Evita using XDA Premium
Click to expand...
Click to collapse
Good morning! ^_^
So, here's the scoop. After you Super CID, you can change your CID 1 time using fastboot oem writecid if you are S-ON
If you are S-OFF you can use that command as many times as you like.
If you have not already SuperCID'd and you are S-ON you would need to SuperCID first either by running the exploit script or hexiditing your CID manually.
I think that's what Thug_4_Life was trying to say too.
exad said:
Good morning! ^_^
So, here's the scoop. After you Super CID, you can change your CID 1 time using fastboot oem writecid if you are S-ON
If you are S-OFF you can use that command as many times as you like.
If you have not already SuperCID'd and you are S-ON you would need to SuperCID first either by running the exploit script or hexiditing your CID manually.
I think that's what Thug_4_Life was trying to say too.
Click to expand...
Click to collapse
Just one question that has been itching me for a long time. Is it correct that you can fastboot oem writecid while s-on? Until now, I believed that it was only after you gain s-off?
Sent from my HTC One
Thug_4_Life said:
Just one question that has been itching me for a long time. Is it correct that you can fastboot oem writecid while s-on? Until now, I believed that it was only after you gain s-off?
Sent from my HTC One
Click to expand...
Click to collapse
Only once if you've already SuperCID'd but not if you haven't already superCID'd
Thug_4_Life said:
No, only if you have already achieved s-off, you can change by "fastboot oem writecid" Have to hex edit it if not.
Sent from my HTC One
Click to expand...
Click to collapse
Exad will correct me if I'm wrong. But this was only true for ATT models. they weren't able to change cid, hence why it takes so long for ATT users so long to find an exploit then change cid.
That's why any other carriers are able to root no problem, there's far less restrictions. Beings he has one from hong Kong, I would imagine he can rewrite the cid because if this.
Personally I would give it a shot.
fastboot oem writecid 11111111
However beings we had a supercid script I don't know what happens if it doesn't write.. Fail I suppose
Sent from my HTC One X using Tapatalk 2
InflatedTitan said:
Exad will correct me if I'm wrong. But this was only true for ATT models. they weren't able to change cid, hence why it takes so long for ATT users so long to find an exploit then change cid.
That's why any other carriers are able to root no problem, there's far less restrictions. Beings he has one from hong Kong, I would imagine he can rewrite the cid because if this.
Personally I would give it a shot.
fastboot oem writecid 11111111
However beings we had a supercid script I don't know what happens if it doesn't write.. Fail I suppose
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
No, even non ATT phones follow the same restrictions, the only difference is HTCDev allows other carriers to unlock through HTCDev without having to SuperCID.
Since S-OFF requires CID to be 11111111 I wrote that Hex guide so we could change our CID to gain S-OFF too.
exad said:
No, even non ATT phones follow the same restrictions, the only difference is HTCDev allows other carriers to unlock through HTCDev without having to SuperCID.
Since S-OFF requires CID to be 11111111 I wrote that Hex guide so we could change our CID to gain S-OFF too.
Click to expand...
Click to collapse
Oh lol
Sent from my HTC One X using Tapatalk 2
So all in all, timmaaa must hex edit instead of fastboot oem writecid since he has yet to supercid, right?
Sent from my HTC One
Thug_4_Life said:
So all in all, timmaaa must hex edit instead of fastboot oem writecid since he has yet to supercid, right?
Sent from my HTC One
Click to expand...
Click to collapse
That's riiigggghhhttt! :laugh::good: <--- Good guy pose
Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks
jacen72 said:
Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks
Click to expand...
Click to collapse
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita
timmaaa said:
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?
jacen72 said:
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?
Click to expand...
Click to collapse
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita
timmaaa said:
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the info - i know i need to superCID as i checked last night and CID was TELST001 (from memory). Will use 11111111.
No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita
timmaaa said:
No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita
Click to expand...
Click to collapse
I tried so many things last night i couldn't tell you exactly what i did, haha! Will try your way and see what it says.
A quick question - in regard to the facepalm link, it says "Download patcher and unzip it in your working directory" - can this be any folder on my phone (eg: Downloads)? I'm also guessing the other file (OneX.zip) goes in the same directory?
No you place the extracted patcher files and the PJ8312000-OneX.zip into your fastboot folder on your pc.
You need to have adb/fastboot and HTC drivers installed on your pc to do the s-off process.
Sent from my Evita
jacen72 said:
I tried so many things last night i couldn't tell you exactly what i did, haha
Click to expand...
Click to collapse
You should keep better track of things you are doing or you will end like NASA on Apollo 1 and not knowing what went wrong.
To repair something you need to know what you did to break it.
Big thanks timmaaa, have upgraded successfully!
twistedddx, you're not wrong - i should have kept an eye on what i was doing. Luckily for me, all went well!
Thanks again.
Glad to see you got it all sorted mate.
Sent from my Evita
Hi guys, since updating Android, i seem to find my service connection (no service) is being lost fairly easily - is there something i need to do in regard to this, or is it just me?!
Cheers
Which ROM are you on?
Sent from my Evita
timmaaa said:
Which ROM are you on?
Sent from my Evita
Click to expand...
Click to collapse
the one from the following link:
http://forum.xda-developers.com/showthread.php?t=2442946
You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita
timmaaa said:
You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, when you talk about beastmode, is the following link what you are referring to?
http://forum.xda-developers.com/showthread.php?t=1797251
Also, with firmware 2.15 - i would actually like to keep it as stock as possible, so perhaps the firmware upgrade would be the better option? I have found a link that looks like it goes to the correct download:
http://forum.xda-developers.com/showthread.php?p=45646878 - (see last post)
Would i be right in saying the instructions for updating the kernel would be the same as at the following link:
http://forum.xda-developers.com/showthread.php?t=2423735 - (OPTIONAL: Installing the Firmware)
Thanks again for your help.
The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita
timmaaa said:
The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita
Click to expand...
Click to collapse
Thanks - looks easy enough. Can i ask what why i would install Beastmode instead of the firmware upgrade? From what i gather, it is to overclock the CPU?
You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita
timmaaa said:
You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, maybe i will install beastmode instead then if it will help fix my connection issues. Sorry, but would you be able to point in the direction of where it is in the development section, i cannot seem to find it.
I promise if this works you wont have to hear my noob questions anymore!!
Hi everybody i flash my htc one x at&t with android 4.2.2 (sense5), i used urdroid version --------->(http://forum.xda-developers.com/showthread.php?t=2331373) and now my phone lost the signal and random reboots, i heard that the problem is the kernel but i don't know what kernel i should install. hope you can help me.
Thanks.
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
Please search properly before posting next time, the answer has been discussed dozens of times in every single Sense 5 ROM thread.
1. Search before posting.
Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.
Click to expand...
Click to collapse
You can flash the Beastmode kernel to fix the problem but the real solution is to flash the 2.15 firmware package. You'll find it (along with detailed instructions) in Turge's stock Sense 5 ROM thread in our Android Development section.
Sent from my Evita
Thanks for the answer
Could you send me the link please
Sent from my HTC One XL using xda app-developers app
I told you exactly where to find it, I'm not going to go and find it for you, that's something you can do for yourself. In the time it took you to write that post your could have already found it and downloaded it.
Sent from my Evita
Thanks dude, i downloaded the beastmode kernel and flash it but now when my phone is starting stuck on at&t logo and then reboot. Do you know why my phone do that?
I'm not super cid and i'm S-ON
Thanks for your answers.
There are a certain group of phones that have a slow SoC, basically they can't handle the Beastmode kernel. You'll need to get s-off and flash the firmware instead. If you need links just look in the Everything Evita thread in my signature. You should bookmark that thread, it contains links to pretty much everything you'll ever need.
Sent from my Evita
Thanks, i'm thinking return to stock rom. Do i have relock my bootloader right? And then run RUU or what do you recomend me to do?
Whatever you do don't run any RUU yet. If you want to return to stock you need to get s-off first. I know you think you don't have SuperCID but if your phone is an at&t model then there's no way you could have unlocked your bootloader without SuperCID. Basically, s-on + SuperCID + jb RUU = brick. So lets check your CID. I'm assuming you have adb/fastboot installed on your PC? If not you need to do that first. Once you have it installed you can connect your phone in fastboot mode (reboot to bootloader and connect), then you need to open a command prompt from within your fastboot folder on your PC (open folder where fastboot.exe is located, shift + right click, select open command prompt here), then issue this command:
Code:
fastboot oem readcid
Tell me what it says.
Sent from my Evita
I was reading about s-off and super cid but I'm new doing this and sounds a little hard to do so don't you think it's better if I install a stock backup
That will solve my problem?
You were right I'm super-cid my cid is: 11111111
S-off is very easy if you already have SuperCID. The biggest obstacle is installing adb/fastboot, if you haven't already. Otherwise, don't worry about being new. We all were at one time. Just read up and understand the process, and follow the instructions carefully, and you will be fine.
---------- Post added at 12:52 PM ---------- Previous post was at 12:50 PM ----------
arthur2820 said:
don't you think it's better if I install a stock backup
Click to expand...
Click to collapse
I don't see how that is in any way "better". If you s-off, all you then need to do is install the 2.15 firmware package, and the signal drop and random reboot issues will disappear.
If you went through the trouble to be able to flash custom ROMs, let's keep it that way.
arthur2820 said:
I was reading about s-off and super cid but I'm new doing this and sounds a little hard to do so don't you think it's better if I install a stock backup
That will solve my problem?
Click to expand...
Click to collapse
arthur2820 said:
You were right I'm super-cid my cid is: 11111111
Click to expand...
Click to collapse
I thought so. Getting s-off is pretty easy, all you need to do is follow some instructions and enter some fastboot and adb commands. Basically, if you can read and type you can do it. As Redpoint said you do need adb/fastboot installed, if you don't already have those you can Google search 'minimal adb and fastboot' and the first result should be a thread that explains how to install it very easily.
We all started somewhere, it might seem a bit daunting at first but I guarantee you it isn't as hard as it seems. Once you get learning it becomes really easy to understand. If you have any questions and can't find answers after some thorough searching just ask, you've got some good people here to assist you.
Sent from my Evita
Thanks I'll try it, could you send me the link of adb/fastboot installer? I guess that the only thing I have to do to install 2.15 formaware it's get s-off
Sent from my HTC One XL using xda app-developers app
See my post right above yours, I've told you what to search for.
Sent from my Evita
i found this thread http://forum.xda-developers.com/showthread.php?t=2155071 i've downloaded the zips bit in the step number 1 i don't know whats means "working directory" the thread it's the correct to get s-off?
how can i flush the image? (step 5)
That's one of the two s-off methods, yes. Your working directory is the folder on your PC where you have adb.exe and fastboot.exe located. You have those installed now right? In order to open the command prompt from that location just shift + right click anywhere in the folder then select open command prompt here.
Sent from my Evita
yes i've installed minimal adb and fastboot. the other method it's easier?
The method you're already using is fine, I used that method and it took me about ten minutes.
Sent from my Evita
ok. mmm but what means flush image again immediately?
Do i have to put the 2 zips in the working directory?
Did you read the instructions? It details exactly what you need to do, follow those directions to the letter. It tells you which zip needs to stay in zip format and which zip needs to be extracted. It tells you what commands to type when the command prompt returns text.
Sent from my Evita