I downloaded Hasoon's program to root the HTC One X (AT&T) but am running into some issues. I have the HTC drivers installed and the phone has USB debugging enabled. However when running through steps 1-5, the CID does not change as it should.
When I enter in the Token ID into HTC's site, it says MID Not Allowed. That's because the CID is not '11111'. When I attempt to run the adb shell command, it cannot find "su" to change the CID:
Code:
C:\android\sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ su
su
/system/bin/sh: su: not found
I downloaded the latest SDK from Android's dev site so that doesn't seem to be the issue. Any ideas where I am going wrong? I've looked around the web but cannot seem to find why it doesn't want to recognize the 'su' command. If it helps at all, running HTC One X on AT&T with Jelly Bean. The ultimate goal is just to root the device, that's all.
Thanks in advance for any assistance that can be provided.
You got the official jb update? If so there is no way to unlock bootloader or root your phone at this time
Sent from my VENOMized HoxL
Yep, I do. That makes sense then. Thank you for the clarification.
You must have missed this: http://forum.xda-developers.com/showthread.php?t=2181929
Really, you shouldn't take an OTA on any Android device if you are rooted, or want to root, without reading up at least.
While I don't recommend it (3 days of basically a soft-brick), if you forgo the changing of CID and unlock your bootloader through HTC and flash TWRP you can still get a cutom ROM on there. I had the Rogers JB update and after some blind fumbling around, factory reset in the bootloader... the HatkaXL rom has been the only working one for me (although with some minor mobile data issues)
I got my One X yesterday (it was running OTA JB, Telus) unlocked through HTCdev.com and then proceeded to root, supercid and s-off.
So it's not too bad if your model can do the HTCdev unlock and you're willing to do it.
sixalive said:
While I don't recommend it (3 days of basically a soft-brick), if you forgo the changing of CID and unlock your bootloader through HTC and flash TWRP you can still get a cutom ROM on there. I had the Rogers JB update and after some blind fumbling around, factory reset in the bootloader... the HatkaXL rom has been the only working one for me (although with some minor mobile data issues)
Click to expand...
Click to collapse
The OP has an AT&T model and those are blocked from unlocking the bootloader through HTC unless you can change the CID
Hey can you give me a bit more detail on the process you used?
I've got the same phone, carrier and OTA... I unlocked through HTCdev, then flashed TWRP and tried to flash CM 10.1 rom. But no roms based on AOSP have working touchscreen. So I flashed Viper XL which works fine. But I'd like to try CM. I think I need SuperCID and s-off to do that but I'm really unsure how to proceed. Would appreciate any assistance!
ChronoReverse said:
I got my One X yesterday (it was running OTA JB, Telus) unlocked through HTCdev.com and then proceeded to root, supercid and s-off.
So it's not too bad if your model can do the HTCdev unlock and you're willing to do it.
Click to expand...
Click to collapse
If your touchscreen isn't working the problem is the touchscreen firmware.
You can downgrade it to fix that: http://forum.xda-developers.com/showthread.php?t=2159863
Hey ChronoReverse,
I appreciate the response.
I get that I need to downgrade my firmware. The problem is I do not have SuperCID or S-Off (these are listed as prereqs to downgrading at the link you sent). And I'm a bit confused how to achieve this on my Telus HOX I've read a bunch of FAQs but most seem to be geared to 2.20 or 1.85 software.
ChronoReverse said:
If your touchscreen isn't working the problem is the touchscreen firmware.
You can downgrade it to fix that: http://forum.xda-developers.com/showthread.php?t=2159863
Click to expand...
Click to collapse
In that case you need to SuperCID then S-OFF.
Since you have an HTCDev unlocked HOXL I think you can use the following commands to SuperCID:
Code:
adb reboot bootloader
(wait for bootloader)
Code:
fastboot oem writecid 11111111
then reboot before following the instructions in this link for Facepalm S-OFF: http://forum.xda-developers.com/showthread.php?t=2155071
If you get error 99 anyway that means the writecid command didn't work. There's a way to get SuperCID using a hex editor: http://forum.xda-developers.com/showthread.php?t=1671396
Hey man really appreciate the assistance.
I did as you suggested and unfortunately didn't seem to get the desired result. I tried it twice and got the same message both times:
Code:
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (Too many links))
Very strange, no device attached? I did a 'fastboot devices' prior to the writecid command and my HOX is detected just fine.
Does this mean I need to take the hex-edit route? God I hope not..
ChronoReverse said:
In that case you need to SuperCID then S-OFF.
Since you have an HTCDev unlocked HOXL I think you can use the following commands to SuperCID:
Code:
adb reboot bootloader
(wait for bootloader)
Code:
fastboot oem writecid 11111111
then reboot before following the instructions in this link for Facepalm S-OFF: http://forum.xda-developers.com/showthread.php?t=2155071
If you get error 99 anyway that means the writecid command didn't work. There's a way to get SuperCID using a hex editor: http://forum.xda-developers.com/showthread.php?t=1671396
Click to expand...
Click to collapse
JeremyNSL said:
Hey man really appreciate the assistance.
I did as you suggested and unfortunately didn't seem to get the desired result. I tried it twice and got the same message both times:
Code:
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (Too many links))
Very strange, no device attached? I did a 'fastboot devices' prior to the writecid command and my HOX is detected just fine.
Does this mean I need to take the hex-edit route? God I hope not..
Click to expand...
Click to collapse
What's wrong with the hex edit? I did it that way and it took 3 minutes. There are step by step instructions. It's really hard to **** up
Sent from my VENOMized HoxL
Its just a bit intimidating. I made it this far without bricking my phone and every step further freaks me out a bit more :-/
But I sucked it up and tried it. And it seems to have worked! I did the fastboot oem readcid afterwards and I get 11111111. So I think that's SuperCID. So now I just need S-Off. Gonna go read that thread for awhile to make sure I do not screw this up.
Thanks for the encouragement
area51avenger said:
What's wrong with the hex edit? I did it that way and it took 3 minutes. There are step by step instructions. It's really hard to **** up
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
JeremyNSL said:
Its just a bit intimidating. I made it this far without bricking my phone and every step further freaks me out a bit more :-/
But I sucked it up and tried it. And it seems to have worked! I did the fastboot oem readcid afterwards and I get 11111111. So I think that's SuperCID. So now I just need S-Off. Gonna go read that thread for awhile to make sure I do not screw this up.
Thanks for the encouragement
Click to expand...
Click to collapse
Now that you're superCID, be very careful not to install the JB OTA update until you're s-off.
Well I'm on Viper XL right now, and I think it overrides the stock OTA updates with its own thing. But I certainly will avoid all OTAs regardless until I sort the s-off stuff.
iElvis said:
Now that you're superCID, be very careful not to install the JB OTA update until you're s-off.
Click to expand...
Click to collapse
I have an AT&T HTC One X with OTA Jelly bean installed. I did the exploit and went into bootloader and read my CID and this is what it shows.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I want to thank you guys for the help - especially ChronoReverse.
I got S-Off today. Wasn't a big deal, worked fine on the first try. I then installed the ElementalX Kernel without any issues (it got stuck in a boot-loop when I was S-On). I am really liking the feel of ViperXL for now so I'll keep than and perhaps downgrade my touchscreen later to try a AOSP rom! Thanks again!
Glad you worked it out. Welcome aboard the HOXL train haha :good:
@mcnaught82
Looks like you're SuperCID. Copy that jumbo of characters into HTCdev's unlocker page to get your unlock bin. Kinda curious how you got SuperCID when you're on ATT OTA JB though.
Related
I've been trying to restore back to stock for over a day now and still havn't figured it out.
All of the guides start talking about adb or fastboot right in the middle of the guide without any explanation.
Aruwizard keeps saying bootloader version fail when I try to flash whats supposed to be stock rogers rom, but everything i see is telling me to download the one im already using.
1. download rogers ruu.zip
2. get supercid or downgrade follow http://forum.xda-developers.com/showthread.php?t=1671135
3. use the windows ruu tool ..... or .... get adb and fastboot installed correctly. google this if you dont know how
4a. for windows ruu tool follow my post in dev section
4b. for adb and fastboot do
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ruu.zip
it will ask u to run the last command again...
Berserk87 said:
I've been trying to restore back to stock for over a day now and still havn't figured it out.
All of the guides start talking about adb or fastboot right in the middle of the guide without any explanation.
Aruwizard keeps saying bootloader version fail when I try to flash whats supposed to be stock rogers rom, but everything i see is telling me to download the one im already using.
Click to expand...
Click to collapse
Have you relocked your bootloader?
1. make sure fastboot in android is turned off under power.
2. power off device
3. power phone on by holding down the volume down key + pressing power - don't release the volume down key until you see the bootloader screen
4. select fastboot
5. connect phone usb
6. screen should now read fastboot usb in red
7. type fastboot oem lock
Phone might restart back into fastboot can't really remember but now you can run the RUU.
The RUU should be an .exe for the above
im on 1.73 trying to flash reflash 1.73, so i shouldnt need to use super cid (?).
I download the rogers stock rom (PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.09.06_10.81.32.14L_release_254934_signed.zip)
and I downloaded ARUwizard to flash it.
I keep getting random errors from aruwizard.
ive tried finding adb tools or fastboot, but they all look like they're for specific phones.
Berserk87 said:
im on 1.73 trying to flash reflash 1.73, so i shouldnt need to use super cid (?).
I download the rogers stock rom (PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.09.06_10.81.32.14L_release_254934_signed.zip)
and I downloaded ARUwizard to flash it.
I keep getting random errors from aruwizard.
ive tried finding adb tools or fastboot, but they all look like they're for specific phones.
Click to expand...
Click to collapse
for aruwizard....did you install htc sync? and relocked your bootloader?...
u need both ...
niceppl said:
for aruwizard....did you install htc sync? and relocked your bootloader?...
u need both ...
Click to expand...
Click to collapse
I did.
and my bootloader has never been unlocked.
its giving me something about incorrect bootloader version. even though its the rogers rom.
Do i need to super cid if im flashing the same version? (1.73 to 1.73)
aruwizard just keeps saying "wrong bootloader version"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is what im getting everytime i try to use aruwizard.
Berserk87 said:
this is what im getting everytime i try to use aruwizard.
Click to expand...
Click to collapse
where did u get the aruwizard tool seems its not the one for hox...too old maybe...try the adb amd fastboot method i mentioned above
Sent from my HTC One X using xda app-developers app
niceppl said:
where did u get the aruwizard tool seems its not the one for hox...
Click to expand...
Click to collapse
downloaded it from your other thread. http://forum.xda-developers.com/showthread.php?t=1658929
using fastboot it starts doing the checks, then gets to :
Code:
INFOchecking main version...
FAILED (remote: 43 main version check fail)
looks like even though im trying to flash 1.73 to 1.73 i still need to do the downgrading firmware stuff...
im curious if my failed update upgraded some stuff and failed on the rest...
now its giving me
Code:
FAILED (remote: 44 hboot version check fail)
anyone?
$5 to anyone that can tell me how to fix this (get back to full stock)
Berserk87 said:
$5 to anyone that can tell me how to fix this (get back to full stock)
Click to expand...
Click to collapse
unlock
twrp
root
supercid (search in dev)
downgrade to 1.00.000 (search in dev)
relock
run ruu
everything should be back to stock
if you want to change supercid back to roger001
do previous steps again and change the cid to roger001 rather than supercid
Sent from my HTC One X using xda app-developers app
Berserk87 said:
$5 to anyone that can tell me how to fix this (get back to full stock)
Click to expand...
Click to collapse
Lol $5 thought a twenty was the customary amount
Sent from my HTC One XL
niceppl said:
unlock
twrp
root
supercid (search in dev)
downgrade to 1.00.000 (search in dev)
relock
run ruu
everything should be back to stock
\
Click to expand...
Click to collapse
I don't want to unlock, id rather keep my warranty as I might be RMA'ing it because of the bluetooth issues im having.
Berserk87 said:
I don't want to unlock, id rather keep my warranty as I might be RMA'ing it because of the bluetooth issues im having.
Click to expand...
Click to collapse
You need to unlock, but alas once you flash the ruu ... The unlocked/tampered proof will be rewritten to stock as well...
From my HTC One X possessed by the Illuminati hybrid kernel
It will show relocked instead of locked.Not sure if warranty accept it
hi guys unfortunately i need to send my phone in warranty (sniff)
previously i'm rooting my ds with revolutionary
and now i follow this
i flashed eng boot and next i use android flasher flashing the hboot in the root of the folder..
anyway i'm now with:
***security warning***
saga pvt ship s-on rl
hboot-0.98.0002
radio-3831.19.00.110
emmc-boot
bla bla bla...
i'm tryng to use the ruu to revert the rom back to stock
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
but it says "unable to update"
now i think i have the h boot 98.0002 and the ruu have 98.0000
so it didn't work but i can't find the ruu thread on xda (i remember there it was some time ago)
any help?
Is it that link you are looking for ? : HTC Saga Shipped Roms
kiss!!!! xD
i have an error....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but before i have:
someone have a solution?
i think i have a newer version of the misc version am i right?but what i can do to downgrade it?
i'v try
adb push misc_version /data/local/tmp
but it'says error device not found
Husky34 said:
i have an error....
but before i have:
someone have a solution?
i think i have a newer version of the misc version am i right?but what i can do to downgrade it?
i'v try
adb push misc_version /data/local/tmp
but it'says error device not found
Click to expand...
Click to collapse
Do you have goldcard? The same problem I also had. After making a goldcard, I've installed the official RUU successful.
Sent from my HTC Desire XS using Tapatalk 2
NVardan said:
Do you have goldcard? The same problem I also had. After making a goldcard, I've installed the official RUU successful.
Sent from my HTC Desire XS using Tapatalk 2
Click to expand...
Click to collapse
mmm no...what is it? (i think i'v heard it...is something inside the sd right?)
[GUIDE] Create a GOLDCARD for your HTC DESIRE S
hipp0po said:
[GUIDE] Create a GOLDCARD for your HTC DESIRE S
Click to expand...
Click to collapse
yep but in this condition my phone doesen't boot..only reboot in bootloader...
Husky34 said:
yep but in this condition my phone doesen't boot..only reboot in bootloader...
Click to expand...
Click to collapse
run the ruu in fastboot?
Sent from my supercharged :tank:
hisname said:
run the ruu in fastboot?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
yep is it correct? it works for a while and then bam error 140..
Husky34 said:
yep is it correct? it works for a while and then bam error 140..
Click to expand...
Click to collapse
well there is still hopes...
try misc. version? or maybe CID doesn't match?
Sent from my supercharged :tank:
hisname said:
well there is still hopes...
try misc. version? or maybe CID doesn't match?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
i'll put the screen in the first page of this thread...and i even try to change misc version without success..
Ok you have made a very common mistake (that I have made once too, but then there was no ICS RUU, so I was forced to do some mumbo-jumbo) - not lowering your version, which is a must-have in the downgrade process
Anyway you have now much easier path now:
1) Run the ICS RUU
2) unlock the bootloader via htc-dev
3) flash a custom recovery
4) root it manually or with the AIO tool (temp root will not work)
5) lower your main version using the misc_version binary
6) relock the bootloader
7) run the RUU
8) disable the update check in the Settings, otherwise if upgraded the SC will spot the relocked bootloader
Good luck
amidabuddha said:
Ok you have made a very common mistake (that I have made once too, but then there was no ICS RUU, so I was forced to do some mumbo-jumbo) - not lowering your version, which is a must-have in the downgrade process
Anyway you have now much easier path now:
1) Run the ICS RUU
2) unlock the bootloader via htc-dev
3) flash a custom recovery
4) root it manually or with the AIO tool (temp root will not work)
5) lower your main version using the misc_version binary
6) relock the bootloader
7) run the RUU
8) disable the update check in the Settings, otherwise if upgraded the SC will spot the relocked bootloader
Good luck
Click to expand...
Click to collapse
but i want to send into warranty man...i can't unlock bootloader via htc dev
Husky34 said:
but i want to send into warranty man...i can't unlock bootloader via htc dev
Click to expand...
Click to collapse
I am afraid you are out of options. There is no way to lower your version without root.
If you are lucky and still have the custom recovery you can use the misc_version there (it has root). Otherwise you cannot flash anything with this version, only the ICS RUU. You cannot use Revolutionary again when your OS does not boot
EDIT: as I said I have made the same mistake and now my hardware buttons are almost broken and I cannot take it to a repair due to my Unlocked bootloader. But when you downgrade to 1.28.x or 1.47.x there is no "RELOCKED" flag shown in the booltoader screen. So if you keep the older version and do not update there is a chance that the SC will not check it.
amidabuddha said:
I am afraid you are out of options. There is no way to lower your version without root.
If you are lucky and still have the custom recovery you can use the misc_version there (it has root). Otherwise you cannot flash anything with this version, only the ICS RUU. You cannot use Revolutionary again when your OS does not boot
Click to expand...
Click to collapse
can i fire my mmc in some way?if my phone doesen't boot i think they can change my motherboard...:'(
i know is a hard decision....but i think is the only one...
OR
i can flash ics ruu and send it into warranty!!!!but when it comes back i can't root it....no?
Husky34 said:
OR
i can flash ics ruu and send it into warranty!!!!but when it comes back i can't root it....no?
Click to expand...
Click to collapse
Well as far as I remember the ICS RUU disclaimer says that it drops the warranty on the software side. If you have a hardware problem it should be acknowledged and repaired. But you have to recheck that.
amidabuddha said:
Well as far as I remember the ICS RUU disclaimer says that it drops the warranty on the software side. If you have a hardware problem it should be acknowledged and repaired. But you have to recheck that.
Click to expand...
Click to collapse
of course i check
thanks for the info and have a good day all!
amidabuddha said:
I am afraid you are out of options. There is no way to lower your version without root.
If you are lucky and still have the custom recovery you can use the misc_version there (it has root). Otherwise you cannot flash anything with this version, only the ICS RUU. You cannot use Revolutionary again when your OS does not boot
EDIT: as I said I have made the same mistake and now my hardware buttons are almost broken and I cannot take it to a repair due to my Unlocked bootloader. But when you downgrade to 1.28.x or 1.47.x there is no "RELOCKED" flag shown in the booltoader screen. So if you keep the older version and do not update there is a chance that the SC will not check it.
Click to expand...
Click to collapse
What are you talking about? He can just use tacoroot. Either way, he was S-OFF, so he can just S-OFF again, change miscversion, and then roll back to S-ON.
What a mess I've made. I've searched everywhere on xda and google with every combination of words I could think of and no answer yet...
Symptoms:
Can't re-unlock bootloader through HTCDev
Prior to relocking I was unable to install roms after a failed miui install attempt
Specs:
S-ON
HBOOT 1.14.0005
T-Mobile US
now running 4.04 with sense 4.1 software 2.35.531.12710RD
History:
Was rooted, bootloader unlocked, running cm10.1 smoothly and many roms before it smoothly
decided to try miui 3.4.5 for fun and install failed and phone stuck on boot screen
was able to start up CWM recovery but would loop back to boot screen too fast to use
used an ruu to go back to stock and start over - installed successfully. even able to ota update so did it
tried to run CWM and reinstall cm10.1 and install failed as did install of any roms
then tried to pursue s-off to be able to install roms again
did super cid successfully
tried s-off but messed up and fashed both zip files instead of flashing PJ4010000-OneS.zip and then unpacked soffbin3 (if that makes sense)
i did get the correct errors though but the install failed to perform the last shell command likely due to no su files installed
at some point i locked the bootloader and now cant unlock it even after flashing cid back to T-MOB010 so i cant reroot
I keep getting the error 150 at htc dev when i put in my token
The phone runs fine on stock rom but after all the changes my old unlock token no longer works and htc wont let me unlock so i cant flash roms. Does anybody have any advice on how to pursue to allow me to go back to CM10.1? Antheor way to unlock bootloader without htc or even another way to s-off?
Thank you
Camboozle said:
...The phone runs fine on stock rom but after all the changes my old unlock token no longer works and htc wont let me unlock...
Click to expand...
Click to collapse
A long shot but did you issue the fastboot get_identifier_token command again after all this mess? Could be a different Unlock Token now that you've done all these changes....?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes I did pull the new identifier. Still no go. Thanks for the reminder though.
I did find an article mentioning something about HTCDev blocking supercid but I read another article dated months later that contradicted the first article and see people are still using supercid and unlocking so I'm not sure what to believe.
I've also read of people having similar errors with the site. And some of them gave there token serial to someone else to try from another computer, and it worked.
I'de give it a try for you if you want. :fingers-crossed:
bmb1983 said:
I've also read of people having similar errors with the site. And some of them gave there token serial to someone else to try from another computer, and it worked.
I'de give it a try for you if you want. :fingers-crossed:
Click to expand...
Click to collapse
Sorry I ended up buying a new phone and didn't see your response. It sounds feasible it may work on another computer. Here is the token and thanks for the help.
<<<< Identifier Token Start >>>>
1700AFDC35C0F82BDA1C7D4E2DA1701C
D6CA28DD3B33DCB09D4250509789B86D
4C7BFF879A3CA0BA463E620CCEE9BE8D
A7203AB6C13F99932FD0CA9B9E2E2373
550463EFED6DF4D329000585DB278470
A753C1F674C0969BD5E3229DF526FBEC
C949BA53604319420CE0441874446C78
7B3356AB59746E140A1FD50207A45BF6
93A3F204FB111045DD77379E930FD675
667463DCCDDFA1400761799EF37144ED
1EA59F82CACA2022AD20F5342658F891
8EFFE8CAC5A619F7CA1F47CF22BD6B30
8FA33533B08831B1ECEB012B55D11955
21293A0337576353E621CCA6D5A50CE8
16353F9F2B0EEE1A66D62E6D336A790E
D4C6B64A99889BC3CF66367451564F84
<<<<< Identifier Token End >>>>>
Well, that didn't work. I tried several times and a couple different computers. Error code 150. Not sure what else to try. Sorry Mate!
EDIT: Reading more into this, there may be something else going on. You said your stock, so have you applied the latest update? To get the most recent HBOOT? If you haven't, the try it. That would change your Token. If you have already done that, then try finding an RUU for your provider that has a different or lower HBOOT.
Just a thought. Its peaked my curiosity now. LoL
definitely don't upgrade. the ota blocks supercid. one thing I've read is to try 222222 or however many instead of 111111 when getting the unlock token.
or are you the step before? still locked and s-on? how did you change your Cid after relocking? can you check your Cid in fast boot and tell us what it says? perhaps you're not in the exact situation you think.
jamus28 said:
definitely don't upgrade. the ota blocks supercid. one thing I've read is to try 222222 or however many instead of 111111 when getting the unlock token.
or are you the step before? still locked and s-on? how did you change your Cid after relocking? can you check your Cid in fast boot and tell us what it says? perhaps you're not in the exact situation you think.
Click to expand...
Click to collapse
i'm having the same problem, and managed to change the cid 4 times when the phone was relocked and on ICS, with write cid commend in adb
jamus28 said:
definitely don't upgrade. the ota blocks supercid. one thing I've read is to try 222222 or however many instead of 111111 when getting the unlock token.
or are you the step before? still locked and s-on? how did you change your Cid after relocking? can you check your Cid in fast boot and tell us what it says? perhaps you're not in the exact situation you think.
Click to expand...
Click to collapse
hes not supercid any more and he has a new phone now anyway. just trying to help more out of curiosity. thanks though!
bmb1983 said:
hes not supercid any more and he has a new phone now anyway. just trying to help more out of curiosity. thanks though!
Click to expand...
Click to collapse
I'm still working on it out of curiosity too and to learn. The new phone is just to keep me from going crazy after all my failures
Here's what I see:
*** RELOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14, 2012 .........
Android 4.1.1
Sense 4+
Software 3.14.531.11 710RD
Attempt to change supercid:
C:\Users\Me\AppData\Local\Android\android-sdk\platform-tools>fastboot
oem writecid 22222222
...
(bootloader) ville_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) sdhw_7xxx_open: id=0ard already power onn
FAILED (unknown status code)
finished. total time: 1.038s
Then it locks up and needs a reboot in to bootloader
Read CID
C:\Users\Me\AppData\Local\Android\android-sdk\platform-tools>fastboot
oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.010s]
finished. total time: 0.010s
Attempt superuser - which fails likely because ruu removed superuser
C:\Users\Me\AppData\Local\Android\android-sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Attempt to flash a recovery - which I didnt expect to work without bootloader unlock
C:\Users\Me\AppData\Local\Android\android-sdk\platform-tools>fastboot
flash recovery recovery-clockwork-touch-5.8.3.1-ville.img
sending 'recovery' (6616 KB)...
OKAY [ 0.975s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.631s
Attempt to flash original boot.img
C:\Users\Me\AppData\Local\Android\android-sdk\platform-tools>fastboot
flash bootloader boot.img
sending 'bootloader' (16384 KB)...
OKAY [ 1.795s]
writing 'bootloader'...
(bootloader) signature checking...
(bootloader) signature checking...
FAILED (unknown status code)
finished. total time: 2.814s
That's just a few things just so you get the idea of what I'm seeing. I have no clue what unkown status code means and it seems the ruu has stopped me form doing what little I could do after relocking the bootloader (like an idiot).
Thanks a ton for the comments though everyone and thanks for trying the token bmb1983. I thought it sounded feasible.
Aaaahhhhh.....NOW I see what your up against. Seeing you can't unlock your bootloader you need another way to gain root, so you can superCID again so you can S-OFF. THEN your back in business!
Have you tried gaining root manually with linux? Might work.
Check out this link. ---> http://www.erodov.com/forums/how-root-any-android-device-manually/43325-page2.html
If you can get root that way, then you should be able to superCID again to get S-OFF. You don't need to be unlocked to get superCID.
Camboozle said:
Attempt to flash original boot.img
C:\Users\Me\AppData\Local\Android\android-sdk\platform-tools>fastboot
flash bootloader bit.img
sending 'bootloader' (16384 KB)...
OKAY [ 1.795s]
writing 'bootloader'...
(bootloader) signature checking...
(bootloader) signature checking...
FAILED (unknown status code)
finished. total time: 2.814s
Click to expand...
Click to collapse
Not that it would make a difference at this point, but fastboot flash bootloader bit.img is the wrong command, it is fastboot flash boot boot.img
Now, the first thing you need to do is unlock the bootloader...that outdated technique above will not work on this phone. I do believe if you changed your cid at some point, you will need a new unlock code...have you tried to get a new one?
The OTA should not affect the bootloader unlock, but what it would affect is writing to 0p4 in order to change to super cid, so if you can't do that, S-OFF is out of the question. Focus on getting that bootloader unlocked.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
ryanshew said:
Not that it would make a difference at this point, but fastboot flash bootloader bit.img is the wrong command, it is fastboot flash boot boot.img
Now, the first thing you need to do is unlock the bootloader...that outdated technique above will not work on this phone. I do believe if you changed your cid at some point, you will need a new unlock code...have you tried to get a new one?
The OTA should not affect the bootloader unlock, but what it would affect is writing to 0p4 in order to change to super cid, so if you can't do that, S-OFF is out of the question. Focus on getting that bootloader unlocked.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Click to expand...
Click to collapse
we can't get it unlocked since htcdevs is giving an error every time we send the token. one thing that i have noticed on my phone that when it is fully discharged and i plug it on my pc it gets on qhsusb mode, and i tried to enumerate the partition with ubuntu but it can only see 4 partitions
Sent from my HTC One S using xda app-developers app
alexskin said:
we can't get it unlocked since htcdevs is giving an error every time we send the token. one thing that i have noticed on my phone that when it is fully discharged and i plug it on my pc it gets on qhsusb mode, and i tried to enumerate the partition with ubuntu but it can only see 4 partitions
Click to expand...
Click to collapse
Have you tried getting a new unlock token?
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
yes and htcdevs delivers error 150 every time I send the token
Sent from my HTC One S using xda app-developers app
alexskin said:
yes and htcdevs delivers error 150 every time I send the token
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
You got a new one attached to a new email?
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
I can't get a new one, I'll post a token and maybe you could try to get unlock code
Sent from my HTC One S using xda app-developers app
---------- Post added at 04:22 PM ---------- Previous post was at 04:10 PM ----------
<<<< Identifier Token Start >>>>
36F7AEAEE0591D136A4C76B3D2A329C6
2536D2947D59CE93E5B637F375103AFD
F648CCE2C65FECF579097E4CE1A2BF65
98D64B61F3697F0A03655D69A05F1B88
F3A39DEAA5EC86F7321524A4C2ED6F21
D2AC158C2F72A43775A3B0FA97A01167
7017033684CF338B1FF9A183138D13F2
B3EF7DD6199F1D059E21580F55A4AD15
1A896179350B66E09A8DB53095300114
9B941B097FBC400DCF5CEF8E13C335D2
A646B5BC23DD4C51384858F564E2916B
8105AD42213017D2B84C8253446FC15E
9905DD2BDB11257D4F78B6674B4E2292
ED02FFF3000E3857C6C4801915A7B30A
328A09B29A5E9BA293421BF7F288B083
E9E8331AA1A1CA3290B4732B71AF831B
<<<<< Identifier Token End >>>>>
alexskin said:
I can't get a new one, I'll post a token and maybe you could try to get unlock code
Sent from my HTC One S using xda app-developers app
---------- Post added at 04:22 PM ---------- Previous post was at 04:10 PM ----------
<<<< Identifier Token Start >>>>
36F7AEAEE0591D136A4C76B3D2A329C6
2536D2947D59CE93E5B637F375103AFD
F648CCE2C65FECF579097E4CE1A2BF65
98D64B61F3697F0A03655D69A05F1B88
F3A39DEAA5EC86F7321524A4C2ED6F21
D2AC158C2F72A43775A3B0FA97A01167
7017033684CF338B1FF9A183138D13F2
B3EF7DD6199F1D059E21580F55A4AD15
1A896179350B66E09A8DB53095300114
9B941B097FBC400DCF5CEF8E13C335D2
A646B5BC23DD4C51384858F564E2916B
8105AD42213017D2B84C8253446FC15E
9905DD2BDB11257D4F78B6674B4E2292
ED02FFF3000E3857C6C4801915A7B30A
328A09B29A5E9BA293421BF7F288B083
E9E8331AA1A1CA3290B4732B71AF831B
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
Your token gave a 150 error as well. I really think that your only option is to try and root manually through LINUX, then SuperCID, then S-OFF and then change your HBOOT. That will give you a different token to try and unlock your Bootloader. Worth a shot! :good:
bmb1983 said:
Your token gave a 150 error as well. I really think that your only option is to try and root manually through LINUX, then SuperCID, then S-OFF and then change your HBOOT. That will give you a different token to try and unlock your Bootloader. Worth a shot! :good:
Click to expand...
Click to collapse
Nothing to lose so I'm installing linux now and trying it. Cool how I can install linux to a microsd card!!! Thanks for the link btw
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
The official Build
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
for the AT&T HTC One XL.
Click link here>> Link to Development Thread <<Click link here
Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
Please keep discussion focused, on the topic described in the OP
For the new kernel is it possible to flash the newest HBoot from this thread just to make life easier? http://forum.xda-developers.com/showthread.php?t=2156368
Would that be the 2.14 HBoot?
thanks again!
BTW I know I already posted this in the AOKP thread...Just wanted clarification from both devs.
mikelebz said:
For the new kernel is it possible to flash the newest HBoot from this thread just to make life easier? http://forum.xda-developers.com/showthread.php?t=2156368
Would that be the 2.14 HBoot?
thanks again!
BTW I know I already posted this in the AOKP thread...Just wanted clarification from both devs.
Click to expand...
Click to collapse
afaik, you MUST flash the RUU in its entirety. I believe h8 did something like just flash parts of the RUU and that bricked his phone. As long as your s-offed, no reason why you wouldn't want to RUU to 3.18.
I don't know if this is the correct place to ask this but I tried to RUU but I keep getting an error.
Torch not working
Anyone else getting FC's when trying to use the torch?
Misterowl said:
I don't know if this is the correct place to ask this but I tried to RUU but I keep getting an error.
Click to expand...
Click to collapse
What Error?
SuperCID? Yes or no?
S-ON or S-OFF?
Is s2w available on this kernel? My power button has been sticky so I've to move to the sense5 rom which I like. But definitely not as much as i love CM10.1
exad said:
What Error?
SuperCID? Yes or no?
S-ON or S-OFF?
Click to expand...
Click to collapse
Error 170
S-OFF
CID 11111111
ClassicalGas said:
Anyone else getting FC's when trying to use the torch?
Click to expand...
Click to collapse
Yeah, I'm pretty sure camera flash is broken too.
Misterowl said:
Error 170
S-OFF
CID 11111111
Click to expand...
Click to collapse
boot to bootloader/fastboot, ruu
So Girlfriend is finally getting tired of her Sense and is open to the idea of me rooting. Besides the camcorder resolution, hdmi, are there any bugs that would keep this from being a good dd. Thanks for the help guys
Hey whats up everybody I have a couple questions, Is it absolutely necessary to upgrade to 3.18 RUU for this ROM? The only reason I'm hesitating to ditch 1.09, is because I'm a bonafide flashaholic, and I'm not looking forward to fastboot flashing the boot image again, every time I want to try a new rom! (been there done that and it is totally NOT the business ) Which brings me to my second question, Does updating to 3.18 require you to fastboot flash the boot image before flashing new rom's? Evita/hboot 1.09/S-Off
JayDream said:
Hey whats up everybody I have a couple questions, Is it absolutely necessary to upgrade to 3.18 RUU for this ROM? The only reason I'm hesitating to ditch 1.09, is because I'm a bonafide flashaholic, and I'm not looking forward to fastboot flashing the boot image again, every time I want to try a new rom! (been there done that and it is totally NOT the business ) Which brings me to my second question, Does updating to 3.18 require you to fastboot flash the boot image before flashing new rom's? Evita/hboot 1.09/S-Off
Click to expand...
Click to collapse
Nah, with S-Off you don't need to fastboot flash anything.
Yesterday I was S-On, 1.09, now I'm S-Off 2.14 hboot (after using the 3.18 RUU). I've never had to fastboot flash the boot.img on this phone.
Sent from my One X using Tapatalk 4 Beta
ClassicalGas said:
Nah, with S-Off you don't need to fastboot flash anything.
Yesterday I was S-On, 1.09, now I'm S-Off 2.14 hboot (after using the 3.18 RUU). I've never had to fastboot flash the boot.img on this phone.
Sent from my One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK thanks! Now can I fastboot flash the hboot using this method http://forum.xda-developers.com/showthread.php?t=2156686 or do I have to actually run the ruu?
JayDream said:
OK thanks! Now can I fastboot flash the hboot using this method http://forum.xda-developers.com/showthread.php?t=2156686 or do I have to actually run the ruu?
Click to expand...
Click to collapse
I RUU'd as per H8's recommendations, so can't confirm if that method works or not.
Sent from my One X using Tapatalk 4 Beta
So I RUU'd and downgraded the touch panel firmware and tried to flash a new recovery but my bootloader is locked.
I tried unlocking the bootloader in HTCdev and I keep getting this in my terminal.
ERROR: could not get pipe properties
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.013s]
finished. total time: 0.013s
ClassicalGas said:
I RUU'd as per H8's recommendations, so can't confirm if that method works or not.
Sent from my One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks man I appreciate it. But I think I'm gonna have to sit back on this one tho :/ at least until I have a better idea of what I'm getting into...
Sent from my HTC One XL using xda app-developers app
Misterowl said:
Error 170
S-OFF
CID 11111111
Click to expand...
Click to collapse
I kept getting an error that "Android phone is not connected"
Then i booted the phone into bootloader mode and tried it
That seemed to get it to work.
Still in the procees of downgrading and getting back to CM10.1
Just wanted to let you know
JayDream said:
Thanks man I appreciate it. But I think I'm gonna have to sit back on this one tho :/ at least until I have a better idea of what I'm getting into...
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yeah I was a bit worried but was patient and followed all instruction instructions below (from the CarbonRom thread).
InflatedTitan said:
1. Download the 2 files for s-off and place in adb folder.
2. Download the recovery of choice and put in adb folder.
3 (optional) download the remove red text file and put in adb folder.
4. You'll have to downgrade touchscreen if you want to use aosp. Head to original dev sticky to download files from h8rift. Put those in adb folder
_________________________________________
1. S-off! Make sure you confirm in bootloader (it usually works easier from a sense rom btw.) 4.2.2 roms need updated adb but it may work.
2. When you ruu, it doesn't touch sdcard. But I would quickly mount and backup your pics and whatnot just in case.
3. Enter fast boot. Run the ruu on the computer. It'll bring you back to 100% stock.
4. Once you up and running, enter fast boot again and send twrp.
5. I recommend to get rid of the ugly ass red text on splash. Follow Liam's thread to rid it.
6. While in fastboot go ahead and downgrade touchscreen following h8rifts instructions.
7. Now you're golden to flash anything you want :thumbup:
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I used the RUU from here
I used a windows computer instead of a Mac to unlock and it worked. So yeah Mac bad.
Sent from my One X using xda app-developers app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As soon as i was S-Off I did this and it worked great,
Code:
[SIZE="3"]adb reboot-bootloader[/SIZE]
Code:
[SIZE="3"]sudo fastboot oem writecid 11111111 [/SIZE]
The reason i put sudo in front of it is beacause now days you can install Adb and Fastboot Via PPA on Ubuntu and fastboot requires sudo,
If you have it installed the traditional way leave sudo in or out it wont hurt either way.
If you wanna go back to original then
Code:
sudo fastboot oem writecid VZW__001
The ouput should be
Code:
(bootloader) Start Verify: 0
(bootloader) Input CID is super CID
(bootloader) Start Verify: 0
OKAY [ 0.029s]
finished. total time: 0.029s
Or close to it as far as time goes..
Cheers All!
oh Hai
hope to start hangin here soon with you
This is my first HTC device so changing your CID is new to me. With S-OFF, i can flash recovery / roms. Why would I need to change my CID to 1111? Is the only profit the ability to install another carrier rom?
Alright, this is new to me. So, I have to ask.
As stated in the OP we can flash any carrier roms? That won't mess with anything specifically will it?
Above is my video guide on enabling SuperCID for those who would prefer a visual aid. Feel free to add to the OP if you like.
Sent from my SM-N900V using xda app-developers app
kwkw480 said:
This is my first HTC device so changing your CID is new to me. With S-OFF, i can flash recovery / roms. Why would I need to change my CID to 1111? Is the only profit the ability to install another carrier rom?
Click to expand...
Click to collapse
My understanding is that you need to change the CID to be able to unlock the bootloader using HTCdev.com that way it won't deny you anymore. Somebody correct me if I'm wrong.
ok now that im 111111 i can now go install http://forum.xda-developers.com/showthread.php?t=2706441 (GPE)?
Now that we are s-off and have a super cid, we can RUU.exe to different carriers. I have never done it ... But as stated in the op, I like options and for me this is kind of an incase something happens extra for me to have. if i need to RUU and all i have is google edition RUU then hey, It's enough to get me going . As always you can google to get alot more info from different sources, this is just somthing until my kernel finishes building
nicholi2789 said:
My understanding is that you need to change the CID to be able to unlock the bootloader using HTCdev.com that way it won't deny you anymore. Somebody correct me if I'm wrong.
Click to expand...
Click to collapse
All of the mods and the roms that you flash will check your cid and model before they will flash. If it detects a cid or model that it is not supported it will error out. This is just a way to change your cid to make sure that it will be accepted.
Zarboz said:
oh Hai
hope to start hangin here soon with you
Click to expand...
Click to collapse
Well Z... how come your not here already? It'll be like the old days.
androidoholic said:
All of the mods and the roms that you flash will check your cid and model before they will flash. If it detects a cid or model that it is not supported it will error out. This is just a way to change your cid to make sure that it will be accepted.
Click to expand...
Click to collapse
Ah okay. It's my first HTC device too, I always had samsung before. But won't this also make it so we can unlock via HTC dev? Or can we just do fastboot oem unlock?
nicholi2789 said:
My understanding is that you need to change the CID to be able to unlock the bootloader using HTCdev.com that way it won't deny you anymore. Somebody correct me if I'm wrong.
Click to expand...
Click to collapse
nicholi2789 said:
Ah okay. It's my first HTC device too, I always had samsung before. But won't this also make it so we can unlock via HTC dev? Or can we just do fastboot oem unlock?
Click to expand...
Click to collapse
That was the case on the m7, but firewater unlocks the bootloader as well, so no need to do it through HTCdev
androidoholic said:
That was the case on the m7, but firewater unlocks the bootloader as well, so no need to do it through HTCdev
Click to expand...
Click to collapse
Oh nice. I didn't know that. So I don't have to worry about backing up for a full factory reset or anything. Sweet.
nicholi2789 said:
Oh nice. I didn't know that. So I don't have to worry about backing up for a full factory reset or anything. Sweet.
Click to expand...
Click to collapse
flashing an international rom fails at getting the build product in the build prop. so that needs to be modified.
sgtmedeiros said:
flashing an international rom fails at getting the build product in the build prop. so that needs to be modified.
Click to expand...
Click to collapse
ya you would have to change the updater-script, but before it is fully tested I would not try to do that unless you have experience, should not cause any irreversible harm, but it would most likely be a waste of time, because of the different radios and such. The roms for the international version are going to have to be ported over. I'm working on the gpe tonight.
androidoholic said:
That was the case on the m7, but firewater unlocks the bootloader as well, so no need to do it through HTCdev
Click to expand...
Click to collapse
Even though we have S-OFF, the bootloader is still locked.
BFirebird101 said:
Even though we have S-OFF, the bootloader is still locked.
Click to expand...
Click to collapse
after firewater mine shows unlocked
Karl said:
after firewater mine shows unlocked
Click to expand...
Click to collapse
Yup, same here.
Karl said:
after firewater mine shows unlocked
Click to expand...
Click to collapse
It's my understanding that when you unlock the bootloader, the device gets wiped. At least, that was how it was on my Galaxy Nexus and Nexus 7 2013. By my fastboot screen showing unlocked, I just assumed that meant that S-OFF worked, but that the bootloader was still locked. If it is indeed unlocked, then that is awesome!
BFirebird101 said:
It's my understanding that when you unlock the bootloader, the device gets wiped. At least, that was how it was on my Galaxy Nexus and Nexus 7 2013. By my fastboot screen showing unlocked, I just assumed that meant that S-OFF worked, but that the bootloader was still locked. If it is indeed unlocked, then that is awesome!
Click to expand...
Click to collapse
it is unlocked after firewater