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
Related
Hi all,
I feel like I have looked everywhere and cannot find an answer for this. I have an at&t one x that is rooted and unlocked with a custom rom, however I somehow changed my cid from supercid 11111111 to htc__001. Is it possible to get supercid 11111111 back or at least wsc__001 so I can run the correct ruu on it.
Thank you in advance for any ideas or help
Just do s off then it will bypass cid... But I think you can do fastboot oem write cid 11111111( don't know how many ones there are)
ziolko said:
Hi all,
I feel like I have looked everywhere and cannot find an answer for this. I have an at&t one x that is rooted and unlocked with a custom rom, however I somehow changed my cid from supercid 11111111 to htc__001. Is it possible to get supercid 11111111 back or at least wsc__001 so I can run the correct ruu on it.
Thank you in advance for any ideas or help
Click to expand...
Click to collapse
fastboot eom writecid "htc__001" or whatever you want it to be minus quotations while in fastboot.
---------- Post added at 03:30 PM ---------- Previous post was at 03:29 PM ----------
a box of kittens said:
Just do s off then it will bypass cid... But I think you can do fastboot oem write cid 11111111( don't know how many ones there are)
Click to expand...
Click to collapse
there's 8 characters in the CID
You can change the CID the old "manual" method: http://forum.xda-developers.com/showthread.php?t=1671396
Or if you do S-off, you can just change the CID with a fastboot command.
Sounds like you were one of the folks that changed to the quad core CID so you can flash a ROM from that phone. Scary.
redpoint73 said:
You can change the CID the old "manual" method: http://forum.xda-developers.com/showthread.php?t=1671396
Or if you do S-off, you can just change the CID with a fastboot command.
Sounds like you were one of the folks that changed to the quad core CID so you can flash a ROM from that phone. Scary.
Click to expand...
Click to collapse
I will try the manual fix, thank you!
I did not read everything I should have in the beginning. I was trying to run a ruu back to stock and did not know I could have done that with supercid ( which I had at the time) and thought I had to change the cid back to original and mistakenly thought HTC__001 was correct. After I realized WSC__001 was actually the correct original cid and now i can't change back in fastboot without errors. I got to comfortable and got ahead of myself.......
CWS__001
Sent from my HTC One X using xda app-developers app
redpoint73 said:
You can change the CID the old "manual" method: http://forum.xda-developers.com/showthread.php?t=1671396
Or if you do S-off, you can just change the CID with a fastboot command.
Sounds like you were one of the folks that changed to the quad core CID so you can flash a ROM from that phone. Scary.
Click to expand...
Click to collapse
You don't need S-off to use the fastboot command to change it from what I understand you just need to have Super CID.
exad said:
You don't need S-off to use the fastboot command to change it from what I understand you just need to have Super CID.
Click to expand...
Click to collapse
Right but without s-off, you can only do it once, away from SuperCID. After that, you're stuck.
OP has neither s-off nor SuperCID, which means he needs the exploit.
Back at SuperCID 11111111, thank you everyone.
ziolko said:
Back at SuperCID 11111111, thank you everyone.
Click to expand...
Click to collapse
Go s-off before you do anything else. You'll thank me later.
iElvis said:
Go s-off before you do anything else. You'll thank me later.
Click to expand...
Click to collapse
S-OFF achieved , now how do I get Jelly bean or another recommended rom?
ziolko said:
S-OFF achieved , now how do I get Jelly bean or another recommended rom?
Click to expand...
Click to collapse
Just load and flash. Once you're s-off, you can flash whatever you want.
iElvis said:
Just load and flash. Once you're s-off, you can flash whatever you want.
Click to expand...
Click to collapse
Well.. anything intended for your device!!!! -_- You're gonna brick noobs talking like that lol
Went with ViperXL 3.2.6 and love it! Thanks to all who helped!
okay so ive already bricked 1 device because of the ota update my question is can i root/re-unlock the boot loader with out bricking this device? also ive been reading that htcdev now blocks supercid 111111 so if going to try getting another unlocktoken will i need to fastboot write cid 222222? also if my device is S-Off then why is it when i try to write in fastboot it returns the error Failed(Remote Not Allowed)... where in my evo 3d allows writing and it also is S-Off and Relocked
Current Specs:
Android 4.1.1
Software build:3.18.502.6 710RD
HBOOT INFO
*** RELOCKED***
EVITA PVT SHIP S-OFF RL
CID- 11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
S-off on our device does not let you write certain things with a locked bootloader. Why? I'm not really sure.
You can't brick unlocking the bootloader unless you're crazy stupid and doing things wrong.
Do you not have the original unlock token from when you unlocked last time?
If not, does your current rom have root? If so you should be able to hex edit your Cid.
If not you're sol until 3.18 root comes out.
Sent from my HTC One X using xda app-developers app
exad said:
S-off on our device does not let you write certain things with a locked bootloader. Why? I'm not really sure.
You can't brick unlocking the bootloader unless you're crazy stupid and doing things wrong.
Do you not have the original unlock token from when you unlocked last time?
If not, does your current rom have root? If so you should be able to hex edit your Cid.
If not you're sol until 3.18 root comes out.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I actually have 5 different tokend for 5 different one x devices and i dont want to flash wrong token
FragmentedLogik said:
I actually have 5 different tokend for 5 different one x devices and i dont want to flash wrong token
Click to expand...
Click to collapse
Why not? what will happen?
exad said:
Why not? what will happen?
Click to expand...
Click to collapse
just hesitant on flashing it seeing how the recent OTA update hard bricked one of my Devices and i cant find a place to purchase a RIFF box, so im kinda trying to avoid hard bricking my 2nd device today
http://www.ort-jtag.com/ you can order them for 150.00 usd plus shipping.
Sent from my One X using xda premium
You'll have to wait until 3.18 root is achieved then unfortunately as you cannot change your CID in your phone's current state.
For future reference, don't bother relocking the bootloader after achieving s-off on this phone. It's pointless and creates issues like this.
exad said:
You'll have to wait until 3.18 root is achieved then unfortunately as you cannot change your CID in your phone's current state.
For future reference, don't bother relocking the bootloader after achieving s-off on this phone. It's pointless and creates issues like this.
Click to expand...
Click to collapse
okay but to verify i am s-off if i flash the unlock token what are the chances of a brick? mainly asking because i am wanting to do the 3 button remap mod and the new elemental kernel as well and only reason i relocked the bootloader and ran the JB ruu is because my basebands all except for lte kept losing signal at random
Can he not write a different cid since he's s off?
a box of kittens said:
Can he not write a different cid since he's s off?
Click to expand...
Click to collapse
Apparently not. Which doesn't surprise me as there are many things I could not do with s-off and a locked bootloader. This seems to be a quirk of the one xl
Can't he fastboot oem writecid if he's already supercid tho
Sent from my VENOMized HoxL
area51avenger said:
Can't he fastboot oem writecid if he's already supercid tho
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Read the OP. He says it errors when trying to write a new cid.
Sent from my HTC One X using xda premium
With the evita, s-off + super cid is not enough, you require an unlocked bootloader aswell.
Can someone please let me know how I can revert my CID to the stock AT&T CID which I believe is CWS_001? It's all 1s right now, but my phone has already been flashed to stock 1.85 ICS RUU and this would be the final step to make sure it's 100% stock. I appreciate anyone that can guide me to the right place. Thanks!
Are you selling it or warranty repair??
Sent from my HTC One X using xda app-developers app
If it's s-off fastboot oem writecid CWS__001
Must be S-OFF if you managed to RUU.
exad said:
If it's s-off fastboot oem writecid CWS__001
Must be S-OFF if you managed to RUU.
Click to expand...
Click to collapse
Wow, it looks really simple to do, but I did use RegawMod Bootloader Customizer to show S-ON. Is it technically still S-OFF? I tried doing what you're telling me but it says INFOfail: writecid Invalid cid. I appreciate your help.
bbonline said:
Wow, it looks really simple to do, but I did use RegawMod Bootloader Customizer to show S-ON. Is it technically still S-OFF? I tried doing what you're telling me but it says INFOfail: writecid Invalid cid. I appreciate your help.
Click to expand...
Click to collapse
Actually, it worked! I was actually only typing one _ and it's two. Thank you very much!!!
31ken31 said:
Are you selling it or warranty repair??
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Selling it. Thanks.
Yes. It's technically still s-off. I'd have left the s-off flag in case the person who buys it wants to root and thinks it's s-on.
Sent from my One X using xda app-developers app
HELP ME!
Its gotta go back tomorrow, Ive searched for hours and I cant seem to find an easy guide to unroot my AT&T One X!
This is beyond frustrating!
Raadius said:
HELP ME!
Its gotta go back tomorrow, Ive searched for hours and I cant seem to find an easy guide to unroot my AT&T One X!
This is beyond frustrating!
Click to expand...
Click to collapse
It's not the easiest thing to do.. What state is your phone in now? hboot? supercid? S-ON? S-OFF?
exad said:
It's not the easiest thing to do.. What state is your phone in now? hboot? supercid? S-ON? S-OFF?
Click to expand...
Click to collapse
HBOOT = 1.09
S-ON
No SuperCID, I used SpoofCID.
Spoof cid is the same thing as SuperCID, get your cid by using fastboot command:
fastboot oem readcid
Sent from my Evita
Raadius said:
HBOOT = 1.09
S-ON
No SuperCID, I used SpoofCID.
Click to expand...
Click to collapse
I see.
First you will need to S-OFF http://forum.xda-developers.com/showthread.php?t=2155071
I don't know if spoofCID will work, you may need to supercid first. it is quite easy with your hboot.
Code:
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
Then once you are S-OFF, Run an RUU for your carrier. With S-Off, it won't matter what software version. It will get you on stock software and remove Tampered text
Rewrite your CID
Code:
fastboot oem writecid CWS__001
Then you can use Regawmod and spoof your unlocked to Locked http://forum.xda-developers.com/showthread.php?t=2156368
You can also spoof your S-off to S-on, or claim your phone came with S-off if they ask or actually set it back to S-on with:
Code:
fastboot oem writesercureflag 3
Good luck.
timmaaa said:
Spoof cid is the same thing as SuperCID, get your cid by using fastboot command:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
CID is CWS__001
Raadius said:
CID is CWS__001
Click to expand...
Click to collapse
I wrote the steps above. You should be good with all that.
Raadius said:
CID is CWS__001
Click to expand...
Click to collapse
I stand corrected, I used spoof cid when I rooted and it gave me SuperCID.
Sent from my Evita
exad said:
It's not the easiest thing to do.. What state is your phone in now? hboot? supercid? S-ON? S-OFF?
Click to expand...
Click to collapse
Sent from my HTC Sensation using xda premium
Where can I find the stock recovery for my AT&T One X?
Raadius said:
Where can I find the stock recovery for my AT&T One X?
Click to expand...
Click to collapse
It will install with the RUU. with S-off you do not need to flash stock recovery or relock or anything. Just run the RUU exe file.
Sorry, I was reading Option 2 from this link
http://forum.xda-developers.com/showthread.php?t=1859714
and watching this video,
http://www.youtube.com/watch?v=SZuAjz4PIjU
Raadius said:
Sorry, I was reading Option 2 from this link
http://forum.xda-developers.com/showthread.php?t=1859714
and watching this video,
http://www.youtube.com/watch?v=SZuAjz4PIjU
Click to expand...
Click to collapse
Don't. that tut is for endeavor.
Videos are not all that reliable either. Trust my directions, you'll be fine.
Terminal stuff gets me confused, sorry to say. I read what your saying, but Im lost already. That's why I went to YouTube, better at viewing it and doing it than reading it. Im better at visual, sorry.
Why cant this be done with S-On?
timmaaa said:
I stand corrected, I used spoof cid when I rooted and it gave me SuperCID.
Sent from my Evita
Click to expand...
Click to collapse
So what does that mean than for me?
Raadius said:
So what does that mean than for me?
Click to expand...
Click to collapse
Not much. Just follow Exad's instructions and you'll be golden.
Sent from my Evita
timmaaa said:
Not much. Just follow Exad's instructions and you'll be golden.
Sent from my Evita
Click to expand...
Click to collapse
Do I have to be S OFF though? You said SpoofCID is the same as SueprCID, so can I skip the S-OFF step and run the RUU?
How do I do all this adb shell terminal stuff? Im new to this...
You need to be s-off or you'll brick. The command stuff is pretty simple, do you have adb/fastboot installed on your pc?
Sent from my Evita
The only thing you need to know is for the fastboot commands your phone needs to be in bootloader and for adb commands your phone needs to be booted into android. Then all you have to do is copy paste the commands into your command prompt.
Just shift right click in the folder where you have fastboot and adb and select "open command prompt here" to get a command line Window open.
Sent from my One X using xda app-developers app
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!!