Database Info

Restore to Stock - losing my mind

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

Why is this device so difficult to flash via fastboot?

Here's the deal:
I'm trying to create a system to flash the One X via fastboot.
Currently, my device has an unlocked bootloader (changed CID, used HTC Dev) and is running the stock 2.20.507 release.
Using 'fastboot flash system system.img' and providing the stock system.img for this build extracted from the rom.zip inside of the RUU does not work - I get an 'out of space error.'
Running "fastboot oem rebootRUU" and attempting to flash the ROM.zip that way provides the following error.
What's up?
{
"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 dont think that works, atleast not on att

DvineLord said:
I dont think that works, atleast not on att
Click to expand...
Click to collapse
Do you know why?

Hboot lockdown

DvineLord said:
Hboot lockdown
Click to expand...
Click to collapse
What does that mean?
Does that mean the version of Hboot on this device literally doesn't allow anything to be flashed to system?
Is it possible to downgrade to something older than what the device shipped with (1.14.0002) or do they have the same restrictions too?

I dont know what version allowed it or if any. Also wish we could run fastboot erase userdata

DvineLord said:
I dont know what version allowed it or if any. Also wish we could run fastboot erase userdata
Click to expand...
Click to collapse
It's remarkable how useless this is. Thanks HTC for providing an "Unlocked" bootloader that is anything but.
Do you know what the earliest version shipped on HTC One X's would be? And is it possible to flash hboot by itself from fastboot (without screwing anything up?)

why not flash the ruu? what are you trying to do?
according to your picture you can't use that method because of supercid, it might work if you changed cid back to original

DvineLord said:
why not flash the ruu? what are you trying to do?
Click to expand...
Click to collapse
Well good question... there is a reason, and it has to do with an automated build flashing/testing system I've been assigned to work on. If it's impossible, I'll find another way (with a custom recovery), but I want to exhaust all possibilities and at least understand why this device is so 'picky'

think the problem is supercid, might work on devices not supercid. will unlock token work if you remove supercid on att htc one xl?

DvineLord said:
think the problem is supercid, might work on devices not supercid. will unlock token work if you remove supercid on att htc one xl?
Click to expand...
Click to collapse
I know to do the HTC Dev unlock in the first place I had to change it...you think I should revert it, try the unlock token again? Is it correct that you have to relock the bootloader to revert the CID? Never done it before...

[2.20 Firmware] Remove Pesky root
this is the only way i know to revert it. also a funny thread. it was made before 2.20 root. enjoy the thread. =)

DvineLord said:
[2.20 Firmware] Remove Pesky root
this is the only way i know to revert it. also a funny thread. it was made before 2.20 root. enjoy the thread. =)
Click to expand...
Click to collapse
LOL this guy...
Anyhow I guess I'll try it, if in fact I cannot unlock again after doing that, I'll just have to re-SuperCID again to get back to my present state...guess it's worth a shot.

DvineLord said:
[2.20 Firmware] Remove Pesky root
this is the only way i know to revert it. also a funny thread. it was made before 2.20 root. enjoy the thread. =)
Click to expand...
Click to collapse
can you not extract mmcblk0p23, hex edit it to change the cid and the copy it back to system? or is the cid in mmcblk0p4?

Why would it be in system?

DvineLord said:
Why would it be in system?
Click to expand...
Click to collapse
erm my bad. i meant push it back to emmc tired today

That's what the thread says i think

When you flash the rom.zip, you get supercid please flush, resend the fastboot flash command, then you will get bootloader flush, resend command again and it will have finish the flash
Sent from my SPH-L710 using Tapatalk 2

18th.abn said:
When you flash the rom.zip, you get supercid please flush, resend the fastboot flash command, then you will get bootloader flush, resend command again and it will have finish the flash
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Run the same command three times in a row? I'm certain I tried at least that many, but I'll have to give it another try...

It works, dont reboot device.
Sent from my SPH-L710 using Tapatalk 2

[Q] Cannot change CID

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.

[Q] need warranty but i'm in troubble

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.

[Q&A][CM 10.1][4.2.2] CyanogenMod 10.1 Questions and Help thread

[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