Database Info

[Q] <Noob Alert> HTC Bootloader Unlock

If I unlock my sensation's bootloader with the official process provided by HTC, what benefits do I get?
I understand I can install any ROM I want and that my warranty would be voided, but:
1) Do I get root access?
2) Can I uninstall unwanted bloatware?
3) Will I have any ROM issues?
4) Would my phone be less secure?
Thanks for your help!

1. You get root access, but to actually use it, a separate package containing the su binary and superuser needs to be flashed.
2. Yep, using Root Explorer (the easiest option IMO).
3. The only way you'll have ROM issues is by flashing a ROM, which is always going to be risky. But if you unlock the phone, but carry on using stock HTC Sense, no you shouldn't have any problems.
4. Depends what you mean by secure tbh. If you mean more likely to get viruses etc, no. But it's less secure by the fact that the security flag (S-OFF Security-OFF) is now off. However, if you use revolutionary.io (the unofficial unlocking process) you have more commands you can use and you have greater access to the actual innards of the phone.
Plus by using revolutionary.io, HTC do not actually know you have unlocked the phone. If you ever need to send it in for warranty repair, just reverse the revolutionary.io process and your warranty will not be voided (in HTC's eyes, at least).

What is the separate package to flash for root? I've tried a bunch and none of them work.

Flash THIS package to obtain superuser and the su binary. Flash through ClockWorkMod and remember to do a nandroid backup!

oh, I can't even get CWM to install. It just says error wrong version or something like that in the fastboot screen.

almostinsane said:
oh, I can't even get CWM to install. It just says error wrong version or something like that in the fastboot screen.
Click to expand...
Click to collapse
Have you tried ROM Manager? Give me the exact error fastboot/adb gives you, I *might* be able to help.

ROM manager won't work unless you are rooted. There error message is 'model ID incorrect' when trying to flash PG58IMG.zip.
same as here:
http://forum.xda-developers.com/archive/index.php/t-1243648.html

almostinsane said:
ROM manager won't work unless you are rooted. There error message is 'model ID incorrect' when trying to flash PG58IMG.zip.
same as here:
http://forum.xda-developers.com/archive/index.php/t-1243648.html
Click to expand...
Click to collapse
Oh yeah, forgot about that
I'll do some research and get back to you
EDIT: Did you use HTCdev to unlock? Try using revolutionary.io and see if it works when/if HTCdev has already been used. Report back with your results

so also being a noob. I can get revolutionary to see my phone and show my serial but when i put in the beta key, it states that it is an invalid key. Why would this be? any help would be great.
Thanks

johnnywhojr said:
so also being a noob. I can get revolutionary to see my phone and show my serial but when i put in the beta key, it states that it is an invalid key. Why would this be? any help would be great.
Thanks
Click to expand...
Click to collapse
It's case sensitive. Copy the code, then Ron the top left of the Revolutionary command window right click and paste the code.
Sent from my HTC Sensation 4G using Tapatalk

good thing to know

redbullcat said:
Oh yeah, forgot about that
I'll do some research and get back to you
EDIT: Did you use HTCdev to unlock? Try using revolutionary.io and see if it works when/if HTCdev has already been used. Report back with your results
Click to expand...
Click to collapse
Yeah, used HTC dev.

almostinsane said:
Yeah, used HTC dev.
Click to expand...
Click to collapse
Yep. Like I said, try using revolutionary.io. If it gives you an error message, take a screenshot and upload it here Anything else, report back. You could even take a video if you want!

Rhiannon224 said:
It's case sensitive. Copy the code, then Ron the top left of the Revolutionary command window right click and paste the code.
Sent from my HTC Sensation 4G using Tapatalk
Click to expand...
Click to collapse
got it working via the copy and paste way. thanks for the assistance

HTC Desire HD update to ICS
redbullcat said:
Flash THIS package to obtain superuser and the su binary. Flash through ClockWorkMod and remember to do a nandroid backup!
Click to expand...
Click to collapse
hi there i am also using HTC desire HD but want to update its software to ICS, please tell me how to achieve this goal. also looking for urdu language support in text msges in my desire HD.

mzsgoheer786 said:
hi there i am also using HTC desire HD but want to update its software to ICS, please tell me how to achieve this goal. also looking for urdu language support in text msges in my desire HD.
Click to expand...
Click to collapse
it would be better to ask this in Desire HD forums
this is only for sensation/xe/4G

[Q] CID # for AT&T U.S.

I currently have S-ON with SuperCID, and I'm trying to get S-OFF with stock AT&T CID. I've heard that it's a fairly simple process to change the CID ("fastboot oem writecid HTC_001"), but HTC_001 is for the unbranded international version, and I'm having a hard time finding the code for the AT&T version, which I suppose I failed to write down before overwriting with SuperCID. Hope someone can help? Also, should I be s-ON or S-OFF to write the CID?

bikeracer4487 said:
I currently have S-ON with SuperCID, and I'm trying to get S-OFF with stock AT&T CID. I've heard that it's a fairly simple process to change the CID ("fastboot oem writecid HTC_001"), but HTC_001 is for the unbranded international version, and I'm having a hard time finding the code for the AT&T version, which I suppose I failed to write down before overwriting with SuperCID. Hope someone can help? Also, should I be s-ON or S-OFF to write the CID?
Click to expand...
Click to collapse
You can only S-OFF with super CID 11111111
After S-OFF you can write it back to the default of CWS__001 for AT&T, but there is no advantage to doing so. You can do whatever you like regardless of what your CID is after S-OFF. I set mine to R00T_001 after for example. (must be 8 characters)
Just noticed your other thread and see why you want the default CID. If you're selling it, make sure your cid is currently 11111111 then S-OFF then you can use that command to change the cid to default. If you're going to sell it, after S-OFF, I'd just format the SD card and run the 3.18 RUU and then power it off after so the person you sell it to will have a fresh start.

exad said:
After S-OFF you can write it back to the default of CWS__001 for AT&T, but there is no advantage to doing so.
Click to expand...
Click to collapse
From what I understand, CID can be changed once from SuperCID to something else, without s-off.
The OP wants to sell his phone, per this thread: http://forum.xda-developers.com/showthread.php?t=2251955
I suggested either changing from SuperCID, or achieving S-off, so the next owner doesn't unintentionally brick the phone by trying to install the 3.18 OTA or RUU (since he is currently SuperCID and S-on).
Not sure why he started this thread, I would have just answered the AT&T CID question in the other thread.

redpoint73 said:
From what I understand, CID can be changed once from SuperCID to something else, without s-off.
The OP wants to sell his phone, per this thread: http://forum.xda-developers.com/showthread.php?t=2251955
I suggested either changing from SuperCID, or achieving S-off, so the next owner doesn't unintentionally brick the phone by trying to install the 3.18 OTA or RUU (since he is currently SuperCID and S-on).
Not sure why he started this thread, I would have just answered the AT&T CID question in the other thread.
Click to expand...
Click to collapse
Sorry, the other thread was started because I couldn't turn my phone on, and was becoming unrelated to original post, thought it would be prudent to create a new thread. Really appreciate your help though.

Just a heads up, I bricked my first TELUS HOXL eventhough I had changed my CID back to the default prior to RUUing. May have been a fluke but yeah do with this info what you will.

UGGGHHH, this is getting frustrating...had to root the phone to get to S-OFF, so I used the X-FACTOR exploit, but when I tried to get S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) I got the first 2 adb command off but the second one said it couldn't find 'su' so I assumed to root hadn't worked. So I decided it would just be easiest to go back to CyanogenMod and start the whole process over. Only when I tried to unlock the bootloader again, I found that it wouldn't stick. It would SAY it was successful and reboot the phone, but when I would reboot to bootloader it would say "relocked". SO decided to run an RUU, only now the hboot was up to 2.14 from the S-OFF flashing, so I decided to run the 3.15 RUU instead of the 2.20, and that SEEMED to work fine, except that now I'm right back to where I was with not being able to turn the phone on, and I tried my previous trick of the Vol Down + Power...
EDIT: Aaaand, no LED when charging...

bikeracer4487 said:
UGGGHHH, this is getting frustrating...had to root the phone to get to S-OFF, so I used the X-FACTOR exploit, but when I tried to get S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) I got the first 2 adb command off but the second one said it couldn't find 'su' so I assumed to root hadn't worked. So I decided it would just be easiest to go back to CyanogenMod and start the whole process over. Only when I tried to unlock the bootloader again, I found that it wouldn't stick. It would SAY it was successful and reboot the phone, but when I would reboot to bootloader it would say "relocked". SO decided to run an RUU, only now the hboot was up to 2.14 from the S-OFF flashing, so I decided to run the 3.15 RUU instead of the 2.20, and that SEEMED to work fine, except that now I'm right back to where I was with not being able to turn the phone on, and I tried my previous trick of the Vol Down + Power...
EDIT: Aaaand, no LED when charging...
Click to expand...
Click to collapse
That's a brick. Do you have a linux boot disk? if not, create a linux boot disk or usb and then try the unbrick evita thread. If you can get past step 3, you should be able to unbrick. if not, Sorry to hear.

exad said:
That's a brick. Do you have a linux boot disk? if not, create a linux boot disk or usb and then try the unbrick evita thread. If you can get past step 3, you should be able to unbrick. if not, Sorry to hear.
Click to expand...
Click to collapse
Hm, not having much luck so far, but I AM seeing QHSUSB_DLOAD in the device manager...

bikeracer4487 said:
Hm, not having much luck so far, but I AM seeing QHSUSB_DLOAD in the device manager...
Click to expand...
Click to collapse
Yeah that bid brick I believe. Get live USB stick running Linux. All you need is small USB stick like 2 or 4 GB. Then download pen drive USB image creator. And run Linux from that. Then exad mentioned a thread to look into. I recommend an Ubuntu based distro. I use Linux mint
Sent from my Carbon-ize Evita using xda-developers app

There's a guide to making a bootable Linux usb in q&a if you need it.
Sent from my One X using xda app-developers app

exad said:
There's a guide to making a bootable Linux usb in q&a if you need it.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, booting from Linux isn't a problem, but as I said, I was trying to put it to stock so I could sell it...but then I discovered it was still under warranty (with just a week left), so instead of messing around in Linux I took it to an AT&T warranty center on my way home and they just straight up replaced with a new One X... Everything turned out better than expected

bikeracer4487 said:
Yeah, booting from Linux isn't a problem, but as I said, I was trying to put it to stock so I could sell it...but then I discovered it was still under warranty (with just a week left), so instead of messing around in Linux I took it to an AT&T warranty center on my way home and they just straight up replaced with a new One X... Everything turned out better than expected
Click to expand...
Click to collapse
Great!! But is it on the new unrootable software?

ImagioX1 said:
Great!! But is it on the new unrootable software?
Click to expand...
Click to collapse
Yup :-/ Software version 3.18, 2.14 hboot, S-ON, and CID of CWS__001... But since I won't be keeping this phone, it'll be someone else's problem...

bikeracer4487 said:
Yup :-/ Software version 3.18, 2.14 hboot, S-ON, and CID of CWS__001... But since I won't be keeping this phone, it'll be someone else's problem...
Click to expand...
Click to collapse
LoL!!
Sent from Xparent Red using my Venomized Evita

It is technically better to have a brand new in box phone for selling. That's awesome! Congrats! I wish Canadian carriers warranted phones like they do in the US. You only get manufacturer warranty here.
Sent from my One X using xda app-developers app

exad said:
It is technically better to have a brand new in box phone for selling. That's awesome! Congrats! I wish Canadian carriers warranted phones like they do in the US. You only get manufacturer warranty here.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
You could pay the 7 bucks a month for device protection then drive over it with a car when you brick it
Sent from my VENOMized HoxL

area51avenger said:
You could pay the 7 bucks a month for device protection then drive over it with a car when you brick it
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Or just keep it and say that you lost it. And of you are able to fix it, sell it and you still keep a new phone.
Sent from my Carbon-ize Evita using xda-developers app

Pft, that's an extra 252$ within my contract period. Forget that noise! I doubt I'll even have this phone in a year lol.
Sent from my One X using xda app-developers app
---------- Post added at 10:17 AM ---------- Previous post was at 10:06 AM ----------
Herc08 said:
Or just keep it and say that you lost it. And of you are able to fix it, sell it and you still keep a new phone.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
They don't warrant lost phones here.
Sent from my One X using xda app-developers app

exad said:
Pft, that's an extra 252$ within my contract period. Forget that noise! I doubt I'll even have this phone in a year lol.
Sent from my One X using xda app-developers app
---------- Post added at 10:17 AM ---------- Previous post was at 10:06 AM ----------
They don't warrant lost phones here.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh wow. Didn't know that
Sent from my Carbon-ize Evita using xda-developers app

exad said:
They don't warrant lost phones here.
Click to expand...
Click to collapse
They don't cover lost phones on warranty anywhere. He was talking about insurance, not a warranty.

[Q] It's bricked guys, and this is serious sht

Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.

Post your bootloader details
Sent from my HTC Sensation 4G using xda premium

adamagic said:
Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.
Click to expand...
Click to collapse
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?

anything else you should know?
ganeshp said:
Post your bootloader details
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
heavy_metal_man said:
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?
Click to expand...
Click to collapse
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151

adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Hi,
If you can get to bootloader,you are not bricked.

adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium

ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425

ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi,
THIS ONE?

rzr86 said:
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
Not the guide
malybru said:
Hi,
THIS ONE?
Click to expand...
Click to collapse
Yes this one
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
Not the guide
Yes this one
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.

adamagic said:
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.
Click to expand...
Click to collapse
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium

still nothing
malybru said:
Hi,
Click to expand...
Click to collapse
Yeah, thanks for the link, but it doesn't work either. I've written the 'cidnum: HTC__622' (without any spaces before and after that) into the txt, but after it's checked the P58IMG.zip doesn't ask me anything, just let me be in bootloader like I'd have started the device in bootloader mode without SD.

all right
ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )

adamagic said:
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )
Click to expand...
Click to collapse
you can try it
you don't have to lose anything at all
if it doesn't work it will just throw you an error
see how it goes

ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Click to expand...
Click to collapse
rzr86 said:
you can try it
see how it goes
Click to expand...
Click to collapse
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.

adamagic said:
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.
Click to expand...
Click to collapse
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium

ohh yes
ganeshp said:
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Some persian guy has uploaded the file I need, but unfortunately I can't register, because I can't answer the randon question during the registration process... Somebody?
http://www.fars-gsm.com/showthread.php?t=57177

[Q] Help Rooting HTC One X 4.0.3

Ok so i need help rooting and unlocking the bootloader for my At&t HTC One X my phone is currently not connected to network (if that makes a difference) So all day i've been trying to unlock the bootloader for my phone through the HTCDev site but i keep getting the error code 160 and MID not allowed. Yes I have made sure that i pasted the characters correctly but still no luck . I'm an extreme noob to this since this is my first smartphone and I'm trying to root it so I can install Jell Bean on my device. If anyone can help me solve this situation it would be extremely appreciated thanks in advance for reading Furthermore, i need a solution in rooting my HTC One X 1.73 Version 4.0.3

Make yourself a cup of coffee and read through the stickies. Att blocked the att one x from being bootloader unlocked through htcdev.com
Sent from my HTC One X using xda app-developers app

exad said:
Make yourself a cup of coffee and read through the stickies. Att blocked the att one x from being bootloader unlocked through htcdev.com
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply, so there is no way that i will be able to put custom Rom on my phone?

Shadane said:
Thanks for the reply, so there is no way that i will be able to put custom Rom on my phone?
Click to expand...
Click to collapse
I never said that

exad said:
I never said that
Click to expand...
Click to collapse
Well that's great news so how will i be able to do it? I've been trying various root methods but can't seem to get my phone rooted

http://forum.xda-developers.com/showthread.php?t=1644167
Sent from my HTC One X using xda app-developers app

exad said:
http://forum.xda-developers.com/showthread.php?t=1644167
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yea man i've done that method numerous amount of times. when i do it "adb server out of date. killing...." and "ADB didn't ACK" comes up alot not sure if that's the reason why it won't let me root

Have you installed the latest HTC Sync Version on your Computer?
If not, install it. Maybe you're just running an old driver for your phone

Kureno7 said:
Have you installed the latest HTC Sync Version on your Computer?
If not, install it. Maybe you're just running an old driver for your phone
Click to expand...
Click to collapse
Yea man i got the latest sync version and i downloaded HTC Drivers and install them as well still no luck

Shadane said:
Yea man i got the latest sync version and i downloaded HTC Drivers and install them as well still no luck
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2197018
Maybe this thread can help you

Shadane said:
Yea man i got the latest sync version and i downloaded HTC Drivers and install them as well still no luck
Click to expand...
Click to collapse
My apologies if this is silly. Do you have adb installed
Sent from my HTC One X using Tapatalk 2

open the task manager, which has adb.exe process and end (kill) that process
Then close your oneclick and re-open it.
That should fix the "ADB server didn't ACK, failed to start daemon" Message.
If that doesn't work you could try installing the lastest android SDK with the latest ADB/fastboot
There's nothing wrong with the rooting procedure. Your lack of technical knowledge is what's holding you back. If you can't troubleshoot issues like this unlocking this phone may not be for you.

I dunno what I did or anything like that. But for some reason the ONLY way I can get adb to recognize my phone is to have HTC sync actually running but minimized. If I exit it from the tray or kill application adb tells me no device found or "waiting for device" indefinitely
Sent from my HTC One X using Tapatalk 2

InflatedTitan said:
I dunno what I did or anything like that. But for some reason the ONLY way I can get adb to recognize my phone is to have HTC sync actually running but minimized. If I exit it from the tray or kill application adb tells me no device found or "waiting for device" indefinitely
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
How bizarre!

Root
exad said:
How bizarre!
Click to expand...
Click to collapse
okay so I uninstalled HTC Syn and killed adb in task manager and when i run the root file everything goes smooth i don't get any errors my phone reboots numerous amount of times but when finished and i go into my apps i don't have "superuser" i even downloaded two different root checkers from the play store however they reported i don't have root do you know how i could fix this problem?

Shadane said:
okay so I uninstalled HTC Syn and killed adb in task manager and when i run the root file everything goes smooth i don't get any errors my phone reboots numerous amount of times but when finished and i go into my apps i don't have "superuser" i even downloaded two different root checkers from the play store however they reported i don't have root do you know how i could fix this problem?
Click to expand...
Click to collapse
Yeah the exploits don't root your phone, They guve temp root to give you supercid so you can unlock the bootloader on HTCDEV. Once your bootloader is unlocked you can flash recovery, after that you can flash su or a rooted rom.

exad said:
Yeah the exploits don't root your phone, They guve temp root to give you supercid so you can unlock the bootloader on HTCDEV. Once your bootloader is unlocked you can flash recovery, after that you can flash su or a rooted rom.
Click to expand...
Click to collapse
Okay i'm a little confused now so this thread http://forum.xda-developers.com/showthread.php?t=1644167 will only give me temp root?

Shadane said:
Okay i'm a little confused now so this thread http://forum.xda-developers.com/showthread.php?t=1644167 will only give me temp root?
Click to expand...
Click to collapse
What software version does your phone have?

keeloc guilty
exad said:
What software version does your phone have?
Click to expand...
Click to collapse
My Android version is 4.0.3 and my software number is 1.73.502.1

Shadane said:
My Android version is 4.0.3 and my software number is 1.73.502.1
Click to expand...
Click to collapse
what's your hboot version in bootloader? I just want to verify.

[Q] How should I update to Android 4.3?

Hello,
This might be a repetitive question but I couldn't find an exact answer.
Through the research I've done, so far I know that I should S-off my device first and then update my RUU to get android 4.3 on my device.
I am S-on and on hboot 1.11. Using clean rom right now. I'm a noob in this and have no idea abt details.
I bricked my phone once and don't want to do it again.
So, For S-off should I follow facepalm method and then should I update my RUU?? The cingular one??
Also, if anyone has a video on s-off it would be great. I can follow it easily.
Thanks. Any help will be appreciated.

You have it right. Get s-off first, then run the RUU. The facepalm method is the only method for s-off and you don't really need s video, you just need to follow the instructions, it's very easy. If you're with at&t then the Cingular RUU is the right one for you. After the RUU you'll need to flash TWRP recovery again.
Sent from my Evita

timmaaa said:
You have it right. Get s-off first, then run the RUU. The facepalm method is the only method for s-off and you don't really need s video, you just need to follow the instructions, it's very easy. If you're with at&t then the Cingular RUU is the right one for you. After the RUU you'll need to flash TWRP recovery again.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the quick reply. I'm with Rogers. Live in canada. I guess they're both the same right??
And after I run RUU, is my phone still going to be rooted or do I have to do all that again?
Also, I found this link online to run RUU, http://www.youtube.com/watch?v=SZuAjz4PIjU
Can you please check and tell me, if I should do the same or not? Go to fastboot and command prompt stuff??
One more thing. S-off says I need superCID? I have no idea what that is. How do I check for that?
Sorry for all the questions but I can't lose the phone again.
Thanks again.

saagar_mistry said:
Thanks for the quick reply. I'm with Rogers. Live in canada. I guess they're both the same right??
And after I run RUU, is my phone still going to be rooted or do I have to do all that again?
Also, I found this link online to run RUU, http://www.youtube.com/watch?v=SZuAjz4PIjU
Can you please check and tell me, if I should do the same or not? Go to fastboot and command prompt stuff??
One more thing. S-off says I need superCID? I have no idea what that is. How do I check for that?
Sorry for all the questions but I can't lose the phone again.
Thanks again.
Click to expand...
Click to collapse
To run the RUU, all you need to do is plug in you s-off'd phone and run it. No additional steps are required.
For superCID, first go into bootloader and run.
fastboot oem readcid.
Tell us what it says.
Sent from my HTC Evita with XDA Premium 4

RollTribe said:
To run the RUU, all you need to do is plug in you s-off'd phone and run it. No additional steps are required.
Sent from my HTC Evita with XDA Premium 4
Click to expand...
Click to collapse
I tried the S-off method but got error 99 instead of error 92.
I think I don't have supercid. Any idea how I should install that!???

saagar_mistry said:
I tried the S-off method but got error 99 instead of error 92.
I think I don't have supercid. Any idea how I should install that!???
Click to expand...
Click to collapse
Try this.
fastboot oem writecid 11111111
Sent from my HTC Evita with XDA Premium 4

RollTribe said:
Try this.
fastboot oem writecid 11111111
Sent from my HTC Evita with XDA Premium 4
Click to expand...
Click to collapse
It shows read failed. too many links.
Also shows no device attached. My usb is attached. I'm in bootloader and it shows fastboot usb.
Still shows no device attached.

saagar_mistry said:
It shows read failed. too many links.
Also shows no device attached. My usb is attached. I'm in bootloader and it shows fastboot usb.
Still shows no device attached.
Click to expand...
Click to collapse
Super CID. Use ADB.
Code:
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
If you don't follow procedure or try things without knowing the current state of your phone, you're on a fast track to a second brick. I am only warning you because you seem to care whether you brick or not.

exad said:
Super CID. Use ADB.
Code:
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
If you don't follow procedure or try things without knowing the current state of your phone, you're on a fast track to a second brick. I am only warning you because you seem to care whether you brick or not.
Click to expand...
Click to collapse
Thanks for the reply!
And yes I don't want to brick it again. I'll leave the phone as it is. I don't think I should proceed with S-off. I downloaded the ADB bundle stuff but gonna stop here. lol.
Anyways. Thanks a lot for help, all of you guys!

saagar_mistry said:
Thanks for the reply!
And yes I don't want to brick it again. I'll leave the phone as it is. I don't think I should proceed with S-off. I downloaded the ADB bundle stuff but gonna stop here. lol.
Anyways. Thanks a lot for help, all of you guys!
Click to expand...
Click to collapse
S-Off isn't so difficult, but at least you know where to draw a clear line on when to stop messing with the phone, unfortunately a lot of people don't really know when they are in over their heads.

As long as you can read and follow directions you will be ok. I suggest reading material on what you are doing to your phone, and if what you're doing is beneficial for it. If you read and don't understand then wait until you do so you don't brick your phone.
Sent from my HTC One X using xda app-developers app