Hi people,
I have unlocked my Sensation's bootloader (through HTCDEV) and am keen to play with ICS (and other ROMs) on it. I have T-Mobile NL branded Sensation. The fastboot screen has the following information on it:
Code:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
I have tried quite a few things:
It seems the revolutionary.io tool does not work on my phone. It keeps telling me it failed to get root. I have tried in Windows (with the older drivers) and Linux (Ubuntu 11.10), neither works.
I have tried to follow this guide: "the-best-easiest-and-safest-way-to-root-and-s-off-the-htc-sensation-tutorial" (I can't post URLs)
However, it fails at the step installing Clockwork Recovery with an invalid CID error.
I have scoured the web, done more Google searches than you can shake a stick at and I'm still stuck.
The phone is most likely SIM locked, the CID is T-MOB003.
I also tried to just modify the secureflag with fastboot to no avail:
Code:
d:\temp\android>fastboot oem readsecureflag
...
(bootloader) secure_flag: 3
OKAY [ 0.008s]
finished. total time: 0.011s
d:\temp\android>fastboot oem writesecureflag 0
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) pyramid_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
(bootloader) writesecureflag: Permission denied, value 1
OKAY [ 1.086s]
finished. total time: 1.087s
I'm all out of ideas but would love to know if anyone else managed to get it working on their HTC Sensation.
Thanks in advance,
Xander
When you say Revolutionary says it's not got root what exactly does it say?
EDIT: If you're unlocked just flash a new recovery using fastboot, it should now work
fastboot flash recovery <filename>.img
EddyOS said:
When you say Revolutionary says it's not got root what exactly does it say?
Click to expand...
Click to collapse
It says "Failed to get root ". Not terribly informative but it gives me the same error on Linux -and- Windows, so at least it's consistent.
Edit (I can only post one reply every 5 mins)
EddyOS said:
When you say Revolutionary says it's not got root what exactly does it say?
EDIT: If you're unlocked just flash a new recovery using fastboot, it should now work
fastboot flash recovery <filename>.img
Click to expand...
Click to collapse
Which recovery image should I use? This one?
recovery-clockwork-5.0.2.0-pyramid.img from clockworkmod.com/rommanager ?
Thanks in advance,
Xander
Same here, also a HTC Sensation T-mobile NL.
I think i have about tried everything too.
In the beginning i thought the tool that was published by HTC (HTCdev) would root the phone but that was too good to be true.
I've tried several ways to root my phone, tried revolutionary, HTC super tool, z4root, gingerbreak, superoneclick. They all about said the same.
For example when i used HTC super tool, and i choose option 4 (trying to set the device to S-OFF) i get the following message:
Code:
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.35.13-g1e13373
New .modinfo section size: 204
Attempting to power cycle eMMC... Failed.
Module failed to load: Operation not permitted
Druk op een toets om door te gaan. . .
And when i try option 3 (perma root) i get the following message.
LINK: imageshack.us/photo/my-images/11/rootfailed.png/
Is this the guide I should follow to flash the new recovery onto the Sensation?
http://forum.xda-developers.com/showthread.php?t=1242942
The ROM mentioned there is an earlier version than the one on the Clockwork page: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-pyramid.img
Which would one would be best to use?
- Xander
I have the same problem.
I have had the OTA update from 1.45.xxx to 1.50.114.xx now on my phone did you get that update as well? I think that is the problem, and there are no RUU's as far as I can see the will work for the T-mob NL 003 CID.
I will follow your post hopefully some one will find the solution soon.
Andrew-HTC said:
I have the same problem.
I have had the OTA update from 1.45.xxx to 1.50.114.xx now on my phone did you get that update as well? I think that is the problem, and there are no RUU's as far as I can see the will work for the T-mob NL 003 CID.
I will follow your post hopefully some one will find the solution soon.
Click to expand...
Click to collapse
Me too going thru same problems...and followings ur post(Andrew HTC)......hope somebody gets a solution
Sent from my HTC Sensation Z710e using xda premium
gre8 buddy
gre8 buddy..really like your work..kepp it up
soulvayne said:
Same here, also a HTC Sensation T-mobile NL.
I think i have about tried everything too.
In the beginning i thought the tool that was published by HTC (HTCdev) would root the phone but that was too good to be true.
I've tried several ways to root my phone, tried revolutionary, HTC super tool, z4root, gingerbreak, superoneclick. They all about said the same.
For example when i used HTC super tool, and i choose option 4 (trying to set the device to S-OFF) i get the following message:
Code:
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.35.13-g1e13373
New .modinfo section size: 204
Attempting to power cycle eMMC... Failed.
Module failed to load: Operation not permitted
Druk op een toets om door te gaan. . .
And when i try option 3 (perma root) i get the following message.
LINK: imageshack.us/photo/my-images/11/rootfailed.png/
Click to expand...
Click to collapse
try that htcsupertool from 1st and 2nd then 4th :/
Sent from my HTC Sensation 4G using XDA App
Still havent got the phone to S-off.
Aperantly the software that the dutch T-Mob sensations get is based on the EU HTC software but then T-Mob fill it with rubbish and encrypt it with there own security functions. thats why the version numbers come up as ( 1.50.114 ) rather than the standard 1.50.401 EU versions etc
The Dutch T-mob sensations are branded but not simlocked, at least mine isn't simlocked.
I now am weighting for the XDA sensation unbrick method to come alive ( noob frendly version ) perhaps there will be a work around for our specific problem via the unbrick methode.
Guys - it's not possible yet to get a proper S-Off when we are at bootloader 1.27, the HTCDEV only unlocks certain areas of the phone. It will allow you to root the phone, but as to my knowledge it wont allow you to install custom roms.
I've found this thread, where they claim that they can propperly S-OFF the 1.27 bootloader. So we just have to wait, and I really hate to wait, until that guide is up.
Oh cool! Here's hoping it appears soon
- Xander
HTC Sensation Tmobile can't S-Off
HTC Sensation 4G (pyramid-1.18.0000, Android: 2.3.4, ROM version: 1.50.531.1)
I have HTC sensation 4g Tmobile. I unlocked the bootloader using HTCDEV. I struggled to root. I used HTC all in one, KGS utility, easy unlock tool.
I was finally able to root using fastboot to install custom recovery and intall a signed version of super user.
I've then tried to obtain S-Off but revolutionary sstates it's unable to root, KGS states the same thing.
I used root checker on the market to determine whether I was rooted it said it was.
I basically want to S-Off then unlock the sim card to ise on another network.
help will be appreciated
S-OFF htc sensation
engines12 said:
HTC Sensation 4G (pyramid-1.18.0000, Android: 2.3.4, ROM version: 1.50.531.1)
I have HTC sensation 4g Tmobile. I unlocked the bootloader using HTCDEV. I struggled to root. I used HTC all in one, KGS utility, easy unlock tool.
I was finally able to root using fastboot to install custom recovery and intall a signed version of super user.
I've then tried to obtain S-Off but revolutionary sstates it's unable to root, KGS states the same thing.
I used root checker on the market to determine whether I was rooted it said it was.
I basically want to S-Off then unlock the sim card to ise on another network.
help will be appreciated
Click to expand...
Click to collapse
In the end i managed to get my phone S-OFF, i managed to do it with juopunut bear method.
It took me a while to get the wire-trick right but its worth it since i can about flash anything i want.
You can find the guide i used here: http://forum.xda-developers.com/showthread.php?t=1614617
soulvayne said:
In the end i managed to get my phone S-OFF, i managed to do it with juopunut bear method.
It took me a while to get the wire-trick right but its worth it since i can about flash anything i want.
You can find the guide i used here: http://forum.xda-developers.com/showthread.php?t=1614617
Click to expand...
Click to collapse
he has 1.18 hboot version(gb firmware)
he needs revolunionary.io method to S-OFF not juopunutbear method
engines12 did you try just to S-OFF with revolutionary?
Unable to s-off
rzr86 said:
he has 1.18 hboot version(gb firmware)
he needs revolunionary.io method to S-OFF not juopunutbear method
engines12 did you try just to S-OFF with revolutionary?
Click to expand...
Click to collapse
Yes. I get the error, failed to root.
Got that too. That is why i tried juopunutbear, but i have bootloader 1.27, i don't know if there is a way for juopunutbear to work on 1.18.
But if rzr86 says it will not work i'm not the one to disaggree with him because i don't have enough knowledge to confirm that.
I can only say it did work for me.
engines12 said:
Yes. I get the error, failed to root.
Click to expand...
Click to collapse
it is really strange
i can't think something else right now
do you want to go for jb S-OFF?
but i don't know if it works for your hboot version
another way is to upgrade officially or via ruu.exe
then you can use the jb S-OFF
but just to know it is a bit harder with jb S-OFF
rzr86 said:
it is really strange
i can't think something else right now
do you want to go for jb S-OFF?
but i don't know if it works for your hboot version
another way is to upgrade officially or via ruu.exe
then you can use the jb S-OFF
but just to know it is a bit harder with jb S-OFF
Click to expand...
Click to collapse
is there any way to perform S-off from the terminal emulator because the error I get is "access denied" anytime temp root is attempted.
Can I use the revolutionary tool with custom recovery? I have Clockworkmod Touch Recovery 5.8.0.9
engines12 said:
is there any way to perform S-off from the terminal emulator because the error I get is "access denied" anytime temp root is attempted.
Can I use the revolutionary tool with custom recovery? I have Clockworkmod Touch Recovery 5.8.0.9
Click to expand...
Click to collapse
you can't do S-OFF from terminal
and what do you mean by ''revolutionary tool with custom recovery''?
Related
i have go to S-On whit this tutorial
http://forum.xda-developers.com/showthread.php?t=1187231
after i reboot i can only in the bootloader an its say Security warning.
I can not flash a RUU .
The VF Ruu say bootloader version error, and the HTC Ruu say User ID Wrong.
wat can i do?? My device is a VF devices..
or iss the device absolutly Bricket?!
Bootloader Shows:
****Security Warning****
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
Radio-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
edit: i think i need a RUU_Saga_Vodafone_UK_1.47. ROM
****....
Try again and again with that RUU.
It didn't worked first time for me either.
Or try other RUU.
I used
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release
You should go to fastboot and try RUU
thanks for your answers.
i try it again and again (in fastboot)
it say update from 1.47.161.2
to 1.32.161.1 than it stop into 104 Bootloader Version Error.
I use the VF UK 1.32.161.1
all HTC Europe RUU`s says USER ID Error
before i would go to stock i have installed de Virtuos unity 1.31.
and befor this the VF German 1.47...
Try other RUU's...It has to work, anyway the phone is not bricked....maybe you should try revolutionary to get it S-off again. Don't know if it works if you are in fastboot, but you can try.
I try all the RUU`s and all give me (Device ID ERROR, USER ID ERROR) the Vodafone RUU alone give me the Bootloader Version ERROR...
I Try this again and again and ever it give me this errors.
Can not understand that is not worked...
i think i must really wait for a Vodafone RUU Leak that have the version 1.47.
Revolutionary say ever "waiting for Device" i think it will not work into the Fastboot Mode
I am very happy wen any can help me to make the system run.
i found the debug files of the RUUs and cane see wat he do..
i check and can make Fastboot commands over cmd
like this : fastboot devices
than it give an output like:
SH16KTJ01149 fastboot
wen i use any adb commands it never found the device....
can we any make over the Fastboot commands for fixing my problem?!
Or can we any moddifing the RUUs that this accept my device?!
i have copy two debug messages of the Vodafone RUU and a other:
Code:
<T011153><DEBUG><CMD>fastboot -s SH16KTJ01149 flash zip C:\Users\Dee\AppData\Local\Temp\{95567211-FFFE-46A1-B012-975D1FD8FE2D}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T011153>
<T011237><DEBUG><OUT>sending 'zip' (268758 KB)... OKAY</OUT>
</DEBUG></T011237>
<T011237><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T011237>
<T011237><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T011237>
<T011318><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking main version...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
</DEBUG></T011318>
or debug messages like this:
Code:
<T230252><DEBUG><CMD>fastboot -s SH16KTJ01149 flash zip C:\Users\Dee\AppData\Local\Temp\{FB1AC174-A654-4612-B610-902E97243E0E}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T230252>
<T230335><DEBUG><OUT>sending 'zip' (254595 KB)... OKAY</OUT>
</DEBUG></T230335>
<T230335><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T230335>
<T230335><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T230335>
<T230414><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>FAILED (remote: 41 model id check fail)</OUT>
</DEBUG></T230414>
HTML:
<T011638><DEBUG><OUT>sending 'zip' (254865 KB)... OKAY</OUT>
</DEBUG></T011638>
<T011638><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T011638>
<T011638><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T011638>
<T011717><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
</DEBUG></T011717>
Stuck in bootloader after use the S-off to S-on tutorial
no one can help???
edit: i see that is the exact same problem in this treath : http://forum.xda-developers.com/showthread.php?t=1190050
should i extract the boot.img and recovery.img from the rom.zip (VF Ruu) and install it over Fastboot commands??
i see a topic about this, but it was another htc phone
http://forum.xda-developers.com/showthread.php?t=1168081
can this work ?!
or should iflash CWM over fastboot ?? can i acces than CWM on s-on hboot??
i have backups from my stock rom.
should i go to buy a xtc-clip for s-off again?!
i think nobody have a solution for my problem.
Silverbullet09 said:
should i go to buy a xtc-clip for s-off again?!
i think nobody have a solution for my problem.
Click to expand...
Click to collapse
I'm afraid that I don't really know what is the best step for you to do next, so aren't going to offer any advice in case it's incorrect.
Don't buy an xtc either look into the pay as you go xtc option or find someone who owns one near where you live, and pay to use it, should be about a tenth the cost.
See a very old thread that I created regarding the xtc clip http://forum.xda-developers.com/showthread.php?t=1076937
Swyped from HTC Desire S using XDA Premium
Try to use steps 1 - 10 from this guide : http://forum.xda-developers.com/showthread.php?t=1190992
If anyone is interested his phone is fixed now.
The S-OFF to S-ON is not correct is a couple of places, and people who have taken the 1.47.XXX.X OTA or RUUs could find themselves in difficulty if they are not super cid particularly on branded phones.
It as a bit of a PITA, but if anyone else finds themself in this situation shoot me a PM, I'll post the solution when I get time but until then I'll help people who get stuck.
globatron said:
If anyone is interested his phone is fixed now.
The S-OFF to S-ON is not correct is a couple of places, and people who have taken the 1.47.XXX.X OTA or RUUs could find themselves in difficulty if they are not super cid particularly on branded phones.
It as a bit of a PITA, but if anyone else finds themself in this situation shoot me a PM, I'll post the solution when I get time but until then I'll help people who get stuck.
Click to expand...
Click to collapse
plz provide us with more information..
I s-offed my device using fre3vo & Revolutionary, as i had installed the update from HTC.
are you saying that if I try to use the procedure from 1st post to S-on, i might brick my phone?
what is super CID? my phone is not branded
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Silverbullet09 said:
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Click to expand...
Click to collapse
Very glad to hear it
Swyped from HTC Desire S using XDA Premium
Nomader0 said:
plz provide us with more information..
I s-offed my device using fre3vo & Revolutionary, as i had installed the update from HTC.
are you saying that if I try to use the procedure from 1st post to S-on, i might brick my phone?
what is super CID? my phone is not branded
Click to expand...
Click to collapse
do not use this procedure to s-on your Phone wen it iss branded, and you never have a 1.47 RUU from your Provider.
Your Phone is not Bricked but it will Stock on the bootloader,
i think wen you make a GoldCard before you S-on with this methode you are able to install a 1.47 RUU wen this is avaibled for you.
(I am not Sure, i think this only)
The know way to fixed this Problem wen you will not have a GoldCard will tell you another. Thats not my Fame
I think the best iss all have to wait off a SAFE S-ON methode.
We have not the Vodafone UK RUU can install than its not leaked with Version 1.47.
We have install the HTC Europe RUU with this Versions number on my Phone.
A Super CID let you install all RUU Updates with Version 1.47.Never need a GoldCard for this, wen you have Super CID.
I Know the workaround for this but i will tested this before i post this thing her.
@ben_pyett
so if my phone is not branded=i am super CID?
and it is safe to s-on with this method?
no you must enter the super cid wen you are s-off ...
i think you can go with the tutorial but all HTC RUU Europe for unbranded Phones avaibled.
Silverbullet09 said:
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Click to expand...
Click to collapse
How to you fixed it ?
my DS work only fastboot cmd
help me, plzz...
poppy8x:
In order to bypass CID errors while flashing a RUU you can try one of two methods:
- If you're still S-OFF, you can change your CID to a SuperCID using fastboot (many guides are available at the HTC Sensation forums). Remember to write down your original CID.
- If you're S-ON already, you can create a goldcard using this guide: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/ You can get the SD's CID from another Android phone, doesn't have to be yours. Insert the goldcard before flashing the RUU (and keep it in until the process ends), and you should be good to go.
Restoring S-ON and HBOOT 1.02 firmware with the restoration of the American
Liberty_downgrade.img in the fastboot.zip
Install the driver fastboot
Liberty_downgrade.img image is complete, and nothing more needs to be done!
1) Copy of the archive folder fastboot, such as the root of drive C: \
2) Run cmd and type:
Code:
cd C:\fastboot
3) After the return to the default firmware from backup, or in case of emergency swing RUU from HTC Aria and install (Warning: This information will be deleted!)
4) Enter the hboot and switch mode fastboot, before connecting to your PC via USB cable.
5) Enter:
Code:
fastboot flash hboot liberty_downgrade.img
and press Enter
With the device, do not do anything! Do not reboot, not disconnected from the PC!
6) Run the RUU again from HTC Aria. At the end of the installer will complain about the error device ID, you can now go in and admire HBOOT labeled S-ON and release HBOOT 1.02
Thank you very much team member Alpharev - kmdm
Sorry for my bad english!
Md5 for liberty hboot fb9a82200b14508cb40be69f43937fc7
Coming soon this manual for europe version!
It's finally here (although I don't need it). Have you tested it yourself?
Yes, i'm tested on myself devices! Working!
very nice!! thanks for sharing. good to know there is a way back if needed
Works PERFECTLY!
I admit that I was skeptical, but this process worked perfectly on the first try on my Aria that I have to return for warranty replacement to AT&T. Entire process took a little more than 10 minutes!
Thanks so much for posting this method!
dimon2242 said:
Restoring S-ON and HBOOT 1.02 firmware with the restoration of the American
Install the driver fastboot
Liberty_downgrade.img image is complete, and nothing more needs to be done!
1) Copy of the archive folder fastboot, such as the root of drive C: \
2) Run cmd and type:
Code:
cd C:\fastboot
3) After the return to the default firmware from backup, or in case of emergency swing RUU from HTC Aria and install (Warning: This information will be deleted!)
4) Enter the hboot and switch mode fastboot, before connecting to your PC via USB cable.
5) Enter:
Code:
fastboot flash hboot liberty_downgrade.img
and press Enter
With the device, do not do anything! Do not reboot, not disconnected from the PC!
6) Run the RUU again from HTC Aria. At the end of the installer will complain about the error device ID, you can now go in and admire HBOOT labeled S-ON and release HBOOT 1.02
Thank you very much team member Alpharev - kmdm
Sorry for my bad english!
Click to expand...
Click to collapse
Once the phone has been restored to S-ON w/ HBOOT 1.02 using this method, can Revolutionary be used to S-OFF again?
drumist said:
Once the phone has been restored to S-ON w/ HBOOT 1.02 using this method, can Revolutionary be used to S-OFF again?
Click to expand...
Click to collapse
Yes) can used revolutionary)
It would be nice if people who post hboots would post the md5sums as well. It is irresponsible not to.
Md5 has been posted) thanks!
Does anyone know if this works on htc gratia,hboot 1.03,bootloader unlocked (htcdev.com)
s19r83g said:
Does anyone know if this works on htc gratia,hboot 1.03,bootloader unlocked (htcdev.com)
Click to expand...
Click to collapse
The new HBOOT 1.03 is already S-ON. You can change it's state from LOCKED to UNLOCKED and back to RELOCKED using fastboot commands.
i not tested with this hboot 1.03, unlikely...
You cannot downgrade from HBOOT 1.03 to HBOOT 1.02 (or earlier).
s19r83g said:
Does anyone know if this works on htc gratia,hboot 1.03,bootloader unlocked (htcdev.com)
Click to expand...
Click to collapse
No, but I know how to remove those.
High level, not for noobs, and certainly not step by step noobs will look for:
install cwm
update the mainver in the misc partition to 1.11.111.1 from cwm (dump/hex edit, reflash required)
back up the current ROM with cwm
relock the bootloader
make a goldcard
flash an aria RUU with a 1.02.1002 hboot.
run revolutionary
restore your gratia rom from cwm backups.
Please attach hboot 1.03 I will try to patch it for Gratia, thanks!
munjeni said:
Please attach hboot 1.03 I will try to patch it for Gratia, thanks!
Click to expand...
Click to collapse
HBOOT 1.03 is attached.
hboot_liberty_7227_1.03.0000_111215.zip
MD5: b1d549c2b602a26740305014bc2de6fd
Hi there,
I have a HTC Aria with Hboot 0.57 and S-ON. I rooted this a while ago and I've been running the Liberated Aria ROMS 2.1 and 2.2.
I want to take S-OFF, but it seems like the only way available is for me to install the official ROM update from AT&T and then use Revolutionary to re-root it and take S-OFF.
Can I use this method for going to Hboot 1.02 and the AT&T official update? and then use revolutionary?
If not, what should I do? (also I have difficulties accessing a windows computer, I primarily use GNU/Linux. If there are instructions for it, that would be swell... I know revolutionary has a linux version, so all is good there).
Thanks
Andres
acimmarusti said:
Hi there,
I have a HTC Aria with Hboot 0.57 and S-ON. I rooted this a while ago and I've been running the Liberated Aria ROMS 2.1 and 2.2.
I want to take S-OFF, but it seems like the only way available is for me to install the official ROM update from AT&T and then use Revolutionary to re-root it and take S-OFF.
Can I use this method for going to Hboot 1.02 and the AT&T official update? and then use revolutionary?
If not, what should I do? (also I have difficulties accessing a windows computer, I primarily use GNU/Linux. If there are instructions for it, that would be swell... I know revolutionary has a linux version, so all is good there).
Thanks
Andres
Click to expand...
Click to collapse
No, you should not use the method described in this thread. Unrevoked does not modify the HBOOT or give you S-OFF, so the instructions in this thread do not apply to you.
To update to HBOOT 1.02, the only thing you need to do is run the RUU to update your phone. Since the RUU is only available as a Windows executable, you can use this alternative method to install it: http://forum.xda-developers.com/showpost.php?p=18541475&postcount=145 . This will erase all your settings from the device, so make a Nandroid backup first if you want to save them.
Once you have completed those steps, you can then use Revolutionary on your device. If you made a backup, you can restore it after Clockworkmod is reinstalled.
No, if fails with hboot 1.03. Is possible to revert to hboot 1.02? Any idea?
Code:
C:\fastboot>fastboot flash hboot liberty_downgrade.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\fastboot>
s19r83g said:
Does anyone know if this works on htc gratia,hboot 1.03,bootloader unlocked (htcdev.com)
Click to expand...
Click to collapse
It fails when you try to flash patched misc partition.
Code:
#fastboot flash misc misc.img
sending 'misc' (640 KB)...
OKAY [ 0.243s]
writing 'misc'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
Edit:
It WORKS!!!, using flash_image misc misc.img
attn1 said:
No, but I know how to remove those.
High level, not for noobs, and certainly not step by step noobs will look for:
install cwm
update the mainver in the misc partition to 1.11.111.1 from cwm (dump/hex edit, reflash required)
back up the current ROM with cwm
relock the bootloader
make a goldcard
flash an aria RUU with a 1.02.1002 hboot.
run revolutionary
restore your gratia rom from cwm backups.
Click to expand...
Click to collapse
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
fdavidson said:
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
Click to expand...
Click to collapse
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
ganeshp said:
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
Click to expand...
Click to collapse
Thanks ganeshp for the quick answer. I am pretty confident about the RUU as it is the same one I originally ran to move from custom ICS ROM to stock 2.3.4 ROM.
For Revolutionary, even in fastboot, it is stuck in "Waiting for devices..." I think it is because it issues "adb devices" command and expects some answer before carrying on to the bootloader. I would need it to skip this step. Are there any argument to revolutionary to do that?
Fred
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
fdavidson said:
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
Click to expand...
Click to collapse
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Jonny said:
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Click to expand...
Click to collapse
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly change for my device, i.e. PG5810000), would the CID affect anything?
Fred
fdavidson said:
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly chance for my device, i.e. PG5810000), would the CID affect anything?
Fred
Click to expand...
Click to collapse
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
dublinz said:
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
Click to expand...
Click to collapse
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
fdavidson said:
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
Click to expand...
Click to collapse
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
fdavidson said:
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
Click to expand...
Click to collapse
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
ganeshp said:
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
Click to expand...
Click to collapse
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
edit: i just read your first post
so you can not use revolutionary
fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
ahh even that got stuck huh ...try revolutionary again ..with phone boot-looping or when stuck at splash screen ..if revolutionary finds the device all good ..otherwise all doors closed
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
he tried revolutionary already ..and he currently didnt have a booting rom ..so it might not work
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
That was my original attempt but it looks like revolutionary expects the phone to be fully booted so it can set it himself in bootloader/fastboot through adb command. Since I can get into fastboot myself, If I could skip that part from revolutionary and have it do the next steps, I think I'd get a successful S-OFF. Any idea on how to do that?
Fred
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
ganeshp said:
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
Click to expand...
Click to collapse
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
fdavidson said:
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
Click to expand...
Click to collapse
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
ganeshp said:
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
Click to expand...
Click to collapse
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
fdavidson said:
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
Click to expand...
Click to collapse
then im out of ideas
one last try
try changing cid
fastboot oem writecid HTC__001
then
fastboot reboot-bootloader
then verify it
fastboot getvar cid
EDIT: if this worked then ..immediately flash the european unbranded 3.33 rom
att htc one x
carrier unlocked (straight talk now)
perma root
super cid
TWRP Recovery 2.4.1.0
custom rom: viperxl 3.2.6
EVITA PVT SHIP S_OFF RL
Hboot ver 1.14.0002
radio ver 0.19as.32.09.11_2
openDSP-v29.1.0.45.0622
eMMc-boot
jun 11 2012, 14:36:28
1) carrier unlocked for straight talk.
2) unlocked bootloader with att all in one tool kit.
2.a) this tool will get identifier token, change cid, unlock bootloader,
2.b) [TOOL] HTC One X (Evita) All-In-One Toolkit V2.1.1 [2-1-2013] [PERM ROOT][Noob-Proof]
http://forum.xda-developers.com/showthread.php?t=1952426
3) installed TWRP 2.4.1.0 via tool kit
4) installed Superuser via tool kit
5) nandriod backup via TWRP
6) gained S-Off using Facepalm
6.a) [S-Off] Facepalm S-Off for HTC One XL
http://forum.xda-developers.com/showthread.php?t=2155071
anyone else have issues unlocking S-ON?
I have the solution. HTC says it cant be done by them. At&t says it cant be done by them. both say unless it came S-OFF it is not possible. I beg to differ but it was not an easy task.I could not get the S-OFF by using facepalm, untill i had installed viperxl rom. it would not work on stock rom, only after viperxl install. I tried like 12 times, suprisingly enough my phone never bricked. but to get viperxl installed i had to flash the boot.img file via adb command line (extracted from rom, or avail on thread above) then go immediately to recovery and install the rom without reboot, wiping the cache and delvik once install is complete. then reboot. once viperxl stabilizes and setup is complete, reboot to recovery, nandriod BU, then follow the facepalm instructions.
In no way is this thread to be misconstrewed as taking any credit for any development of any references here, they are solely references that i used to achieve the desired effect on my device. this is an instructional on how i performed these functions on my phone. I would like to thank all the developers that have made this possible.
I have no idea what you're asking
Sent from my VENOMized HoxL
area51avenger said:
I have no idea what you're asking
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
was not asking anything. Simply providing information.
Just a heads up you don't need to sim unlock a AT&T phone to use it on Straight talk if you're using there AT&T network sim. If you're using AT&T phone on ST with Tmobile network sim then you do need to Sim unlock it.
bpear96 said:
Just a heads up you don't need to sim unlock a AT&T phone do use it on Straight talk if your using there AT&T network sim. If you using AT&T phone on ST with Tmobile network sim then you do.
Click to expand...
Click to collapse
Had lots of issues changing carrier, including blacklisted imei. as far as that part goes I followed ST support instructions.
Later come to find out that ST is a devision of att. Same network and all. Just different apn's. a ST sim will not prompt for unlock pin to change carriers. I had to borrow one from Verizon. only to find out later that I didn't need to c_unlock the device at all. Yaay. Me.
delete
delete this post please, not the thread just this post. thank you
sphynx.0029 said:
att htc one x
carrier unlocked (straight talk now)
perma root
super cid
TWRP Recovery 2.4.1.0
custom rom: viperxl 3.2.6
EVITA PVT SHIP S_OFF RL
Hboot ver 1.14.0002
radio ver 0.19as.32.09.11_2
openDSP-v29.1.0.45.0622
eMMc-boot
jun 11 2012, 14:36:28
1) carrier unlocked for straight talk.
2) unlocked bootloader with att all in one tool kit.
2.a) this tool will get identifier token, change cid, unlock bootloader,
2.b) [TOOL] HTC One X (Evita) All-In-One Toolkit V2.1.1 [2-1-2013] [PERM ROOT][Noob-Proof]
http://forum.xda-developers.com/showthread.php?t=1952426
3) installed TWRP 2.4.1.0 via tool kit
4) installed Superuser via tool kit
5) nandriod backup via TWRP
6) gained S-Off using Facepalm
6.a) [S-Off] Facepalm S-Off for HTC One XL
http://forum.xda-developers.com/showthread.php?t=2155071
anyone else have issues unlocking S-ON?
I have the solution. HTC says it cant be done by them. At&t says it cant be done by them. both say unless it came S-OFF it is not possible. I beg to differ but it was not an easy task.I could not get the S-OFF by using facepalm, untill i had installed viperxl rom. it would not work on stock rom, only after viperxl install. I tried like 12 times, suprisingly enough my phone never bricked. but to get viperxl installed i had to flash the boot.img file via adb command line (extracted from rom, or avail on thread above) then go immediately to recovery and install the rom without reboot, wiping the cache and delvik once install is complete. then reboot. once viperxl stabilizes and setup is complete, reboot to recovery, nandriod BU, then follow the facepalm instructions.
In no way is this thread to be misconstrewed as taking any credit for any development of any references here, they are solely references that i used to achieve the desired effect on my device. this is an instructional on how i performed these functions on my phone. I would like to thank all the developers that have made this possible.
Click to expand...
Click to collapse
Can you help me by telling which Viper Rom you have used for this. I am having problems in S-OFF . Running same as ur version
harismahesh said:
Can you help me by telling which Viper Rom you have used for this. I am having problems in S-OFF . Running same as ur version
Click to expand...
Click to collapse
Which part of the s-off process are you having problems with? Are you able to post the text from the command prompt on a failed attempt? That will make diagnosing the problem a lot easier.
Sent from my Evita
Sure,
While running - fastboot flash zip PJ8312000-OneX.zip
I am getting 99 unknown fail.
sending 'zip' (36064 KB)...
OKAY [ 2.873s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.126s
Ok, when you get error 99 force a reboot back into bootloader by holding volume down and power together. When it reaches bootloader start again from the beginning, you should now get error 92. You do have SuperCID right?
Sent from my Evita
First off here's what I'm working with:
Rogers HTC One X
Cyanogenmod from http://forum.xda-developers.com/showthread.php?t=2205183
Recovery - TWRP 2.5
Hboot - 2.14
radio - 0.23a.32.09.29
Rooted - I don't think so
SuperCID - 22222222
S-OFF - No
Lock status - Unlocked with HTCDev after SuperCID
Story time:
After deciding to install cyanogenmod on the weekend I've run in to a myriad of issues. I was able to unlock, flash CWM recovery, and install Cyanogen fairly easily, but I ran into the issue where the touch screen doesn't work.
What I've done:
I've found the fix detailed here: http://forum.xda-developers.com/showthread.php?t=2159863, but have been unable to get all the prerequisites going. From the screen fix thread linked above I need to be rooted, s-offed, and superCIDed.
I believe I got the superCID working by following the steps in this post: http://forum.xda-developers.com/showpost.php?p=41482419&postcount=2 and fastboot oem readcid returns 22222222
After that I was unlocked before but locked and relocked with a new unlockcode from htcdev
For rooting, I've looked at the methods listed under Root on http://forum.xda-developers.com/showthread.php?t=1671237, but I'm not too sure where to find which firmware I'm on. That would be the version of cyanogen would it not. I've tried the x-factor method using All-In-One Toolkit from http://forum.xda-developers.com/showthread.php?t=1952426 to no avail, as well as SuperSU from http://forum.xda-developers.com/showthread.php?t=1673935 and this one: http://forum.xda-developers.com/showthread.php?t=1644167, but I don't think any method has worked so far.
In order to use S-Off I'm pretty sure you need to be rooted, so it of course it didn't work, what made me think I wasn't rooted was when I was going through the Facepalm S-Off guide here: http://forum.xda-developers.com/showthread.php?t=2155071 when I ran "adb shell su -c "/data/local/tmp/soffbin3" it would just me the error su: not found, which means your not in as root according to: http://forum.xda-developers.com/showthread.php?p=38278577#post38278577
I've also tried going back to stock using the RUU RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe from http://ruu.androidfiles.org/getdown...9.28L_10.103.32.24L_release_268972_signed.exe, but when I run it I get error 99: Unknown Error, and I if I look in the log it creates it says error 44 HBOOT mismatch. I'm running after relocking, and I've tried just grabbing the rom.zip from %temp%, extracting it and flashing the boot and system imgs, but it says the system.img is too big.
At this point I'd just like to get my phone to work. If I can get it with CM that'd be cool, but stock would be good too. Any help would be appreciated.
Thanks!
In cyanogenmod you have to allow adb root access in developer options.
To ruu without s-off you need to change your cid back to the default but you will brick if you update to 3.18 after. Best to s-off since you changed your cid.
Sent from my Sony Tablet S using xda app-developers app
exad said:
In cyanogenmod you have to allow adb root access in developer options.
Click to expand...
Click to collapse
The touchpad doesn't work in cyanogenmod though, that's the root of the issue
exad said:
To ruu without s-off you need to change your cid back to the default but you will brick if you update to 3.18 after. Best to s-off since you changed your cid.
Click to expand...
Click to collapse
I was trying to RUU before changing CID, but was running in to "FAILED (remote: 44 hboot version check fail)", when running the RUU mentioned in the OP
Ah I see the ruu must have had an older hboot version than the one on your phone. You cant downgrade firmware without s-off.
To fix your issue you will need to flash a sense rom and then s-off and then downgrade your touchscreen firmware. Then you can flash whatever evita rom you like.
Sent from my Sony Tablet S using xda app-developers app
exad said:
Ah I see the ruu must have had an older hboot version than the one on your phone. You cant downgrade firmware without s-off.
To fix your issue you will need to flash a sense rom and then s-off and then downgrade your touchscreen firmware. Then you can flash whatever evita rom you like.
Click to expand...
Click to collapse
Thank you very much!
I flashed the Sense build from http://forum.xda-developers.com/showthread.php?t=2293032 and was then able to S-Off. After that I was able to down grade the touchpad firmware and install cyanogenmod.
Thanks again for pointing me in the right direction
:victory: