Related
I've been reading a little on this S-off thing and was wondering what its purpose actually is and what the advantages are from doing it? I know I was able to flash my HTC Vivid without it so what is it really used for? Thank you in advance.
Answer...
phrotac said:
I've been reading a little on this S-off thing and was wondering what its purpose actually is and what the advantages are from doing it? I know I was able to flash my HTC Vivid without it so what is it really used for? Thank you in advance.
Click to expand...
Click to collapse
See: What Is S-OFF & How To Gain It On HTC Android Phones With unrevoked forever
In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag.
Click to expand...
Click to collapse
---------- Post added at 11:01 PM ---------- Previous post was at 10:58 PM ----------
Basically, if you are going to be installing custom ROMs, you probably want to set s-off so you can flash unsigned ROMs.
Very interesting. Thank you for responding That gives me something to think about.
In short. S-OFF allows you to change pretty much everything. Your CID, firmware (radio, hboot etc) and most important thing probably, allows you to flash older RUUs
Sent from my HTC Sensation XE with Beats Audio using Tapatalk 2
If you are going to be changing roms, themes, etc, then leave it off. If not then turn in back on.
kdub83 said:
If you are going to be changing roms, themes, etc, then leave it off. If not then turn in back on.
Click to expand...
Click to collapse
I found the perfect ROM from WCX but I never had to use a wire on it though. Is HTCdev the reason why? I'm just trying to figure out this whole s-off thing because I saw a video where someone used a piece of insulated wire and was wondering why. I'm sorry if I wasn't clear enough with my questions earlier... My bad.
S-OFF
Hi - I've had HTC devices since the Eris way back in 2010 - currently running the Rezound. Hopefully I can shed some more light.
When I first got the Rezound I was coming over from an S-OFF Eris... if you wanted to flash something custom, you'd go to htcdev.com and use their "unlock bootloader" tool. Once you ran that and followed a few other steps, you are reverted to stock and your bootloader now has a little warning "unlocked" in the text at the top. This was in January 2012, and ROMs back then came with 2 things - the ROM and a Kernel. You had to flash the kernel separatley (and via the bootloader as opposed to a custom recovery), as S-ON (even unlocked) still won't let you write to certain places (in the case of the kernel, its the boot partition).
We got S-OFF several months later (the thing using the wire trick). In S-OFF - custom recovery can write to all areas of the device - no more need for any separate files, you just flash a ROM in custom recovery and everything is set up the way it should be. Added bonus - no need to unlock the bootloader from htcdev... so no "unlocked" warning message.
Here was my S-OFF process:
1. Run the official RUU exe to get your device back to stock with a Locked bootloader (backup any files on the SDCard first!).
2. Perform the wire trick
3. Flash a custom recovery and proceed with flashing ROMS
Let me know if I can clarify anything...
Basically allows you to flash RADIOS that have not been signed by HTC
Sent from my Galaxy Nexus using xda premium
Ryan Kasper said:
Hi - I've had HTC devices since the Eris way back in 2010 - currently running the Rezound. Hopefully I can shed some more light.
When I first got the Rezound I was coming over from an S-OFF Eris... if you wanted to flash something custom, you'd go to htcdev.com and use their "unlock bootloader" tool. Once you ran that and followed a few other steps, you are reverted to stock and your bootloader now has a little warning "unlocked" in the text at the top. This was in January 2012, and ROMs back then came with 2 things - the ROM and a Kernel. You had to flash the kernel separatley (and via the bootloader as opposed to a custom recovery), as S-ON (even unlocked) still won't let you write to certain places (in the case of the kernel, its the boot partition).
We got S-OFF several months later (the thing using the wire trick). In S-OFF - custom recovery can write to all areas of the device - no more need for any separate files, you just flash a ROM in custom recovery and everything is set up the way it should be. Added bonus - no need to unlock the bootloader from htcdev... so no "unlocked" warning message.
Click to expand...
Click to collapse
Thank you very much. That DOES explain it very well.
Ryan Kasper said:
Here was my S-OFF process:
1. Run the official RUU exe to get your device back to stock with a Locked bootloader (backup any files on the SDCard first!).
2. Perform the wire trick
3. Flash a custom recovery and proceed with flashing ROMS
Let me know if I can clarify anything...
Click to expand...
Click to collapse
Are you saying I can make my bootloader say LOCKED again? I thought I could only make it say UNLOCKED or RELOCKED now that I've unlocked it. That is so awesome. And then the s-off will give me permanent root?
Are you saying I can make my bootloader say LOCKED again? I thought I could only make it say UNLOCKED or RELOCKED now that I've unlocked it. That is so awesome. And then the s-off will give me permanent root?
Click to expand...
Click to collapse
Yup! Once you are S-OFF you will be back on the stock bootloader that reads "locked". There are a variety of HBOOTS (AKA Bootloaders) you can flash (well - there are for my device currently...). For the Rezound right now I have a variety of them with different verbages in the title (example - "locked S-ON", "Rezound") - or you can simply leave it at the stock HBOOT though you will not be able to flash, say a custom recovery, using fastboot in the bootloader via a terminal emulator (you have to use the PH98IMG.zip method in the bootloader)... Also the devs that made the wire trick available offer their own hboot "juopunutbear" - this one allows fastboot recovery flashing... - here for the vivid http://unlimited.io/jb_holiday.htm
Also - be VERY careful when updating the bootloader - it is a very common way to brick the device... I always check the MD5Sum before copying to SD and flashing.
And regarding permanent root - absolutely. Flash SuperSU from custom recovery (the zip version available here - http://forum.xda-developers.com/showthread.php?t=1538053
Ryan Kasper said:
Yup! Once you are S-OFF you will be back on the stock bootloader that reads "locked". There are a variety of HBOOTS (AKA Bootloaders) you can flash (well - there are for my device currently...). For the Rezound right now I have a variety of them with different verbages in the title (example - "locked S-ON", "Rezound") - or you can simply leave it at the stock HBOOT though you will not be able to flash, say a custom recovery, using fastboot in the bootloader via a terminal emulator (you have to use the PH98IMG.zip method in the bootloader)... Also the devs that made the wire trick available offer their own hboot "juopunutbear" - this one allows fastboot recovery flashing... - here for the vivid http://unlimited.io/jb_holiday.htm
Also - be VERY careful when updating the bootloader - it is a very common way to brick the device... I always check the MD5Sum before copying to SD and flashing.
And regarding permanent root - absolutely. Flash SuperSU from custom recovery (the zip version available here - http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
This information is golden. Thank you very much
tinky1 said:
In short. S-OFF allows you to change pretty much everything. Your CID, firmware (radio, hboot etc) and most important thing probably, allows you to flash older RUUs
Sent from my HTC Sensation XE with Beats Audio using Tapatalk 2
Click to expand...
Click to collapse
Awesome! I have a couple more questions still *scratches head in confusion*...
Once I S-Off, can I reverse it if needed?
and
<Ignore this part... I found the information LOL>
What is an RUU? I have googled it and I can't find anything about it (maybe I'm just too tired or something)
phrotac said:
Awesome! I have a couple more questions still *scratches head in confusion*...
Once I S-Off, can I reverse it if needed?
Click to expand...
Click to collapse
Yup - here is how I'd do it if I had to for my device - http://forum.xda-developers.com/showthread.php?t=1612937 - careful if you do and read any warnings (brick opportunities again)
Hi,
It is possible, if I install custom rom, some function will not work without S-OFF?
The phone was routed and unlokced but it was S-ON.
Hey Guys,
So yesterday I decided I wanted to root my HTC One X (Rogers Canada Unlocked) so I followed the tutorials and unlocked the bootloader and went to install CWM recovery. I flashed it via fastboot, then when I restarted into recovery I was in a bootloop saying that this is for development purposes only, and it just kept restarting. So I booted back in to fastboot mode and installed TWRP 3.0.0.0 but the touch controls didnt work, so I reflashed TWRP 3.0.0.1 and the recovery was accessible. I tried to flash a rom and it said it succeeded but it just keeps going into that bootloop and there is no sign of the old stock ROM on the device at all. So I decided today to relock the bootloader, clear the cache and find a Rogers RUU to flash back on the phone with ARUwizard. It fails to install because of a conflict with my bootloader (obviously because mine is 2.14.000) but there is nowhere on the world wide web that has an updated Rogers RUU to flash to my phone. The only good thing that came out of it, is it just stays on the HTC splash screen and doesn't have the red development purposes only writing. I need some help, thanks in advance. If there is anything I missed please let me know.
Phone: HTC One X (Rogers Canada Unlocked) Evita
Bootloader Relocked, S-ON, Hboot 2.14.000
Secondary: HTC Incredible S (Vigin Mobile Canada)
Bootloader Unlocked, S-OFF, C10 ROM
RUU I have found in the past to be more difficult than the root process. make sure drivers installed and usb plugged into the back of pc.
CMW probably corrupt your SD card btw.
Use twrp. And looks like you did everything right for your flashing process except "fastboot flash boot.img" you could probably get the rom you want working if you extract the boot.img and flash in adb.
Sent from my HOX w/CM10.1
The problem is that there is no Rogers RUU for the latest hboot (2.14) that the OP is on. For some reason (that I've never completely understood) Rogers firmwares often don't have corresponding RUUs ever released. And he can't use an old RUU, as it fails version check (you can't run an RUU for a firmware version and/or hboot older than what is on the phone). Maybe they will release a Rogers RUU for the firmware that goes with 2.14. But it wouldn't surprise me if they never do.
The TWRP versions mentioned in the OP look wrong. The newest TWRP version is 2.3.3.1, and is supposed to be compatible with 2.14 (although I think some are still having some troubles). I'd start there, by re-unlocking and installing the latest TWRP:
http://forum.xda-developers.com/showthread.php?t=1677447
DvineLord posted the recovery img in Post 432.
If the OTA file is a complete zip, with hboot, sbl images, etc. It can be used as an RUU, but it isn't an automated process. as long as you install TWRP, and then install a ROM/kernel, your phone will work again
jjswain, if you need to RUU, find the complete zip OTA package, and follow the steps here http://forum.xda-developers.com/showthread.php?t=1974272
The same can be done in windows, start at step 9
subarudroid said:
looks like you did everything right for your flashing process except "fastboot flash boot.img" you could probably get the rom you want working if you extract the boot.img and flash in adb.
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
I'm in the same boat as OP, I did that exactly as I've flashed boot.img separate before and that fixes things. Problem is that once I flash boot.img and then flash the .zip it came out of the rom boots to completion, but the touch screen won't work. I think the solution is just to wait until 2.14.0000 is supported by other roms.
veemodz823 said:
I'm in the same boat as OP, I did that exactly as I've flashed boot.img separate before and that fixes things. Problem is that once I flash boot.img and then flash the .zip it came out of the rom boots to completion, but the touch screen won't work. I think the solution is just to wait until 2.14.0000 is supported by other roms.
Click to expand...
Click to collapse
I also flashed the boot, did factory reset, cleared cache, and davlik, installed rom (5 different ones to be exact) and they all booted but no touch screen either :crying: Any other idea's to try? Glad it's not bricked...it's just pricked for now
jjswain said:
I also flashed the boot, did factory reset, cleared cache, and davlik, installed rom (5 different ones to be exact) and they all booted but no touch screen either :crying: Any other idea's to try? Glad it's not bricked...it's just pricked for now
Click to expand...
Click to collapse
You can downgrade your hboot if you can access recovery to push a broken partition 4, then flash an old hboot, and then edit your software info and downgrade.. if you aren't comfortable we can do this over team viewer if you would like.
This sounds very similar to the situation I'm in. People have said the reason why there is no touch is because of 3.17 blah blah blah. If you want to read up on where I'm at, here's the link. We're pretty much in the same boat bro.
http://forum.xda-developers.com/showthread.php?t=2102729
absolutelygrim said:
You can downgrade your hboot if you can access recovery to push a broken partition 4, then flash an old hboot, and then edit your software info and downgrade.. if you aren't comfortable we can do this over team viewer if you would like.
Click to expand...
Click to collapse
I'm not sure if it's the hboot version that's messing it up or if it's the softare 3.17 that we OTA. I'm sure if we were still on ICS then rooted we'd be fine, but because we did the JB update and then attempted root....I think that's the issue
jjswain said:
I'm not sure if it's the hboot version that's messing it up or if it's the softare 3.17 that we OTA. I'm sure if we were still on ICS then rooted we'd be fine, but because we did the JB update and then attempted root....I think that's the issue
Click to expand...
Click to collapse
You have to downgrade your hboot to ruu downgrade to get the old firmware
absolutelygrim said:
You have to downgrade your hboot to ruu downgrade to get the old firmware
Click to expand...
Click to collapse
I could use this rom correct? Its based on 3.17
http://forum.xda-developers.com/showthread.php?t=2075783
Installed that Rom, phone works perfect except for LTE
Sent from my HTC One XL using xda app-developers app
Works..just shows 4g, but speedtest proves its lte
Search for TWRP for the HTC One X Evita (the north American model of the HTC one x) and make sure that the version is 2.3.3.1.
Then install Viper XL by Team Venom.
When installing the rom wipe everything that TWRP will let you wipe, then mount the phone as USB storage put the ZIP file on the phone, and then flash it.
If that doesn't work I dunno what will.
---------- Post added at 06:28 PM ---------- Previous post was at 06:17 PM ----------
So first you need to flash TWRP for HTC One X evita, you are going to need version 2.3.3.1.
Boot into the new recovery and wipe everything, SD Card, System everything.
Then download Viper XL by Team Venom, go to the mount menu, make sure everything is unchecked, and mount the phone as USB storage and put the rom on the phone.
Flash the rom and you now have a working phone.
jjswain said:
Installed that Rom, phone works perfect except for LTE
Sent from my HTC One XL using xda app-developers app
Works..just shows 4g, but speedtest proves its lte
Click to expand...
Click to collapse
This depends on the network icon set that was flashed with the rom you chose. For some roms, the values are as follows:
E - Extended network
3G - 3G
H - 4G
4G - LTE
On other icon sets, the last one is replaced by LTE - LTE. Some roms will actually let you install/use different network icons, so you could always take a look into something like that.
^what he said ^ also you can go to dialer and *#*#info#*#* go to phone info and see what network your connected to.
Sent from my HOX w/CM10.1
I'm somewhat in the same position as the OP, but every RUU or rom I try fails at signature check (although the latest one posted above seemed to work but then nothing at bootup). Being that I have stock CID ROGER001, and the same HBOOT 2.14 Evita, Radio .23a.32.09.29 and S-ON, is hoping a Rogers RUU is released my only option?
Well given my specs above I can confirm that the Hatka rom works (insofar as it has booted up and I have a phone again!!) Thank you so much for the link jjswain!!
you will only be able to downgrade if you s-off. i assume you are unlocked with twrp or the new cwm flashed if so as long as you wipe first you should be able to flash roms fine unless you are trying to flash non-evita roms for some reason. which roms have you tried flashing and what version of recovery are you using?
So... I had an awkward moment where I began looking at all the roms and seeing that they were all for a OneX not OneXL...:silly: Thanks for asking me to go through those as I probably would not have realized my mistake! Just flashed Viper3.2.6XL and I'm much happier with the look and feel.
I updated my One X Evita to jelly bean....I want to root my phone again. My last one x was on ICS and it was rooted but I got a new One X and now have Jelly Bean. My Hboot is 2.14. I been reading that people have been losing the touch screen? Has that problem been fixed with the new twrp2?
mcnaught82 said:
I updated my One X Evita to jelly bean....I want to root my phone again. My last one x was on ICS and it was rooted but I got a new One X and now have Jelly Bean. My Hboot is 2.14. I been reading that people have been losing the touch screen? Has that problem been fixed with the new twrp2?
Click to expand...
Click to collapse
You can't root now. There is no root method for jelly bean yet.
Sent from my Nexus 7 using Tapatalk HD
So I tried to root my phone awhile back and just ran out of time. Ive using the phone as is since but its time I finish what I started. Right now in the bootloader I have the 2 little bars on the top one saying tampered the other saying unlocked. It still says S-on(which where Im a little unsure of). I can boot into recovery without an issue from the bootloader. So i guess my question am i ready to install a custom rom or is there more i need to do before i do that?
Cbaird said:
So I tried to root my phone awhile back and just ran out of time. Ive using the phone as is since but its time I finish what I started. Right now in the bootloader I have the 2 little bars on the top one saying tampered the other saying unlocked. It still says S-on(which where Im a little unsure of). I can boot into recovery without an issue from the bootloader. So i guess my question am i ready to install a custom rom or is there more i need to do before i do that?
Click to expand...
Click to collapse
Yes, you can install an ROM you wish, but depending on hboot you may have to flash the boot.img in fastboot. There is an easy method of getting stuff in the original android development section of this phones forum, so do that and you won't have to work. Happy flashing
Original android dev section is lame. S-off your device, then flash CleanROM JB beta and ElementalX vanilla. You won't be disappointed.
Sent from my HTC One X using xda premium
S-OFF your device first this is all most noob proof just follow the instructions to the T. Then you wont have to flash the boot.img every time you flash a new rom in recovery, if you're on Hboot 1.14 and up. If you're on Hboot 2.14 I believe all 4.2 AOSP roms touch screens don't work, not sure though I know that cm10.1 doesn't for sure, but you can easily downgrade your Hboot to make it work after you've S-OFF'ed your phone or downgrade your touch panels firmware, again after your S-OFF .
S-OFF: http://forum.xda-developers.com/showthread.php?t=2155071
Downgrade HBOOT: http://forum.xda-developers.com/showthread.php?t=2156686 or http://forum.xda-developers.com/showthread.php?t=2156368
Downgrade touch panel: http://forum.xda-developers.com/showthread.php?t=2159863
ECEXCURSION said:
Original android dev section is lame. S-off your device, then flash CleanROM JB beta and ElementalX vanilla. You won't be disappointed.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Lame. Lol.
Its all a matter of opinion, in your opinion it is lame..
Android Dev section - anything not built from source (usually sense Roms)
Original Dev section - anything built from source (aosp based, such as cyanogenmod)
Sent from my Google Nexus 4
mirGantrophy said:
Lame. Lol.
Its all a matter of opinion, in your opinion it is lame..
Android Dev section - anything not built from source (usually sense Roms)
Original Dev section - anything built from source (aosp based, such as cyanogenmod)
Sent from my Google Nexus 4
Click to expand...
Click to collapse
Why aren't sense kernels in original development? I could be wrong but aren't they built from source
a box of kittens said:
Why aren't sense kernels in original development? I could be wrong but aren't they built from source
Click to expand...
Click to collapse
To prevent confusion
Sent from my Nexus 4 using xda app-developers app
Wubbz said:
S-OFF your device first this is all most noob proof just follow the instructions to the T. Then you wont have to flash the boot.img every time you flash a new rom in recovery, if you're on Hboot 1.14 and up. If you're on Hboot 2.14 I believe all 4.2 AOSP roms touch screens don't work, not sure though I know that cm10.1 doesn't for sure, but you can easily downgrade your Hboot to make it work after you've S-OFF'ed your phone or downgrade your touch panels firmware, again after your S-OFF .
S-OFF: http://forum.xda-developers.com/showthread.php?t=2155071
Downgrade HBOOT: http://forum.xda-developers.com/showthread.php?t=2156686 or http://forum.xda-developers.com/showthread.php?t=2156368
Downgrade touch panel: http://forum.xda-developers.com/showthread.php?t=2159863
Click to expand...
Click to collapse
I flashed a rom through recovery and had no issues with having to flash the boot.img.(but maybe that was done before and i just dont remember) I also just checked my Hboot and its at 1.11. So would you recommend i do this still or not?
Cbaird said:
I flashed a rom through recovery and had no issues with having to flash the boot.img.(but maybe that was done before and i just dont remember) I also just checked my Hboot and its at 1.11. So would you recommend i do this still or not?
Click to expand...
Click to collapse
Since your on a Hboot lower than 1.14 you shouldn't have to downgrade anything, Hboots or the touchscreen firmware, But I would still recommend doing the S-OFF still. If you do, read through the instruction before you start then give it a go. Once your device is S-OFF you can downgrade or upgrade to any Hboot or change to what ever Radio you wish and no more flashing boot.img on Hboots 1.14 and up.
TIP for S-OFF I was getting error 99 with cm10.1 so i had to backup and wipe my phone and goto Viper XL 3.2.3 and then restore my cm10.1 rom from trwp recovery, there is a post about this in the S-OFF thread it might be in the OP now not sure though.
Also if you move to a 4.2.X based rom from 4.1.X or lower you will probably need to upgrade your adb folder if you haven't made it with googles newest build
Hello all
As you can tell Im new to this and thought i would be able to root my device..
Here what I have done I unlocked my device with HTCDev installed CWM 6.0.2.7 treid to boot to recovery no go just stays on a black screen. So then install TWRP 2.4.1.0 Booted to recovery and still the back screen.. so I re-locked the phone and now for some reason all my phone will boot up to is
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
So I would like to know before I go buy a new device If this one can be fix and if it can would some one be able to inform me of the steps ? I can still unlock the device but cant boot to any recovery....
I also Tried to Reload the rogers Ruu and keep getting errors.
Please help
Tookie.
Some one please Help I have been working on this for like 20 hours now and I dont have a phone that can be used :S
tookie69 said:
Hello all
As you can tell Im new to this and thought i would be able to root my device..
Here what I have done I unlocked my device with HTCDev installed CWM 6.0.2.7 treid to boot to recovery no go just stays on a black screen. So then install TWRP 2.4.1.0 Booted to recovery and still the back screen.. so I re-locked the phone and now for some reason all my phone will boot up to is
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
So I would like to know before I go buy a new device If this one can be fix and if it can would some one be able to inform me of the steps ? I can still unlock the device but cant boot to any recovery....
I also Tried to Reload the rogers Ruu and keep getting errors.
Please help
Tookie.
Some one please Help I have been working on this for like 20 hours now and I dont have a phone that can be used :S
Click to expand...
Click to collapse
Just reflash your unlock code from HTC dev install twrp then flash away
Sent from my HTC One X using Tapatalk 2
Don't panic, this should be an easy fix.
Once you relock, you have to run a ruu or unlock again. But you're trying to run a ruu for older firmware, which is why it's failing.
Just push the unlock token again, and you should be able to boot to recovery. If not, push the recovery image again. I don't recommend CWM, even though it's been ported to this phone. That version of TWRP should work, just confirm that you've got the Evita version.
OK i have unlocked again and re pushed recovery TWRP 2.4.1.0
But I still cant boot into the recovery option..
PLease tell me what im doing wrong..
iElvis said:
Don't panic, this should be an easy fix.
Once you relock, you have to run a ruu or unlock again. But you're trying to run a ruu for older firmware, which is why it's failing.
Just push the unlock token again, and you should be able to boot to recovery. If not, push the recovery image again. I don't recommend CWM, even though it's been ported to this phone. That version of TWRP should work, just confirm that you've got the Evita version.
Click to expand...
Click to collapse
I reflashed the unlcok code I reinstall TWRP but i cant boot into recovery..
is there another way to flash away ?
Kole_Ackerson said:
Just reflash your unlock code from HTC dev install twrp then flash away
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
tookie69 said:
I reflashed the unlcok code I reinstall TWRP but i cant boot into recovery..
is there another way to flash away ?
Click to expand...
Click to collapse
I believe through adv but is way simpler to do it through recovery. Try a earlier version of twrp
Sent from my HTC One X using Tapatalk 2
did you verify you are unlocked now, or did you just assume since you pushed the token again?
Also, are you certain you're using the right version of TWRP and not one for another phone (like the endeavour/Tegra One X)?
I pushed the same token and rebooted the device at the top its now says unlocked
DvineLord said:
did you verify you are unlocked now, or did you just assume since you pushed the token again?
Click to expand...
Click to collapse
make sure to run "fastboot erase cache" after changing recovery
IM pretty sure.. I also tried and older TWRP still same issue would you happen to have a link ? I have been using the all in one for HTC one X Tool
iElvis said:
Also, are you certain you're using the right version of TWRP and not one for another phone (like the endeavour/Tegra One X)?
Click to expand...
Click to collapse
bah, all-in-one don't learn anything without doing it yourself. evita is a pretty easy phone once you learn the basics. the op link for twrp in the dev section lists every twrp version officially released for our phone. http://techerrata.com/browse/twrp2/evita
ok i loaded that last night before i went to bed I went this morning to look at the phone and now it just goes to a black screen no madder what I do i put it in the computer the computer goes beep now when its plugged in my computer only the red light at the top flashes and then it disconnects from my computer because i can here the beep of adding and removing hard ware.
is my phone now bricked ?
DvineLord said:
bah, all-in-one don't learn anything without doing it yourself. evita is a pretty easy phone once you learn the basics. the op link for twrp in the dev section lists every twrp version officially released for our phone. http://techerrata.com/browse/twrp2/evita
Click to expand...
Click to collapse
Just relock and boot into boot loader the tampered screen then run a ruu am you should be back to stock
Although I had a EVO before that I flashed the wroung bootloader an bricked it an it wouldn't go anywhere but the bootloader
Sent from my HTC One X using xda premium
If I were you I'd reinstall drivers and manually push the recovery via adb. Use this command- fastboot flash recovery (filename).img
Sent from my HTC One X using Tapatalk 2
Thanks
Thanks for all the help maybe a little late but the issue was the main board on the phone was messed up sent it to HTC and they replaced the board and the battery.. but now i dont need the phone got the HTC one
Rom installation fails on Rogers HTC One X, S-ON, EVITA, HBOOT 2.14.0000
tookie69 said:
Thanks for all the help maybe a little late but the issue was the main board on the phone was messed up sent it to HTC and they replaced the board and the battery.. but now i dont need the phone got the HTC one
Click to expand...
Click to collapse
Hi Guys,
I have the same phone as the specs mentioned below. This is my first android phone and my first time playing around with it.
Here are the specs for "Rogers HTC One X":
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
Here is my accomplishments so far:
- Unlocked with HTC Dec, therefore it says unlocked as mentioned above
- Installed TWRP v2.5.0.0, and can successfully boot into recovery
Yet to be done and do not know how to:
- S-OFF
- Super CID
- Permanent Root
Problems installing ROM:
- unable to install. Various errors with different roms, such as:
1) unable to mount sdcard
2) assert failed: getprop("ro.product.device")
3) error executing updater binary in zip
Please advise. Thank you for your time.
Note: the device is locked to Rogers. It is currently in bootloop. I do not know what I did but before installing TWRP, the device went in bootloop after unlocking bootloader and it would simply not start. Although, as mentioned I can successfully boot into the recovery and mount the sdcard from there to transfer files to the phone.
iccrcmember said:
Hi Guys,
I have the same phone as the specs mentioned below. This is my first android phone and my first time playing around with it.
Here are the specs for "Rogers HTC One X":
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
Here is my accomplishments so far:
- Unlocked with HTC Dec, therefore it says unlocked as mentioned above
- Installed TWRP v2.5.0.0, and can successfully boot into recovery
Yet to be done and do not know how to:
- S-OFF
- Super CID
- Permanent Root
Problems installing ROM:
- unable to install. Various errors with different roms, such as:
1) unable to mount sdcard
2) assert failed: getprop("ro.product.device")
3) error executing updater binary in zip
Please advise. Thank you for your time.
Note: the device is locked to Rogers. It is currently in bootloop. I do not know what I did but before installing TWRP, the device went in bootloop after unlocking bootloader and it would simply not start. Although, as mentioned I can successfully boot into the recovery and mount the sdcard from there to transfer files to the phone.
Click to expand...
Click to collapse
Why are you relocked?
Unlock again and update TWRP, then try to flash a ROM again. What ROM(s) are you trying to flash.
Be aware that since you are s-off, you will need to extract boot.img from the ROM you are trying to flash, and manually flash with fastboot. You will need to do this every time you flash a ROM, unless you get s-off.
Also, I don't know why you posted to this old thread. Aside from the OP also having the Rogers version, it has nothing to do with your issue. Should have started your own thread.
I'll just clarify that when Redpoint said you need to update TWRP you should update it to TWRP 2.6, your current version (2.5) is very buggy. Also, he means since you are s-on you need to flash the boot.img, when you get s-off this will no longer be required.
Sent from my Evita
Thank you redpoint73
redpoint73 said:
Why are you relocked?
Unlock again and update TWRP, then try to flash a ROM again. What ROM(s) are you trying to flash.
Be aware that since you are s-off, you will need to extract boot.img from the ROM you are trying to flash, and manually flash with fastboot. You will need to do this every time you flash a ROM, unless you get s-off.
Also, I don't know why you posted to this old thread. Aside from the OP also having the Rogers version, it has nothing to do with your issue. Should have started your own thread.
Click to expand...
Click to collapse
I made an error. my bootloader was already unlocked. Any how flashing the boot.img of the Rom before installing the Rom worked. Thank you for your insight. My phone is up and running.
For others: below is the rom i flashed:
[ROM] 10/10 Team Venom ViperX 4.0.4 - Sense 5 JellyBean | orig. OTA | Tweaks
http://forum.xda-developers.com/showthread.php?t=2087443
Hi,
I'm totally new in the rooting/customROM business. I want to flash the Desire XS version 1.1 on my desire s, since the 2.3.5 is a little old now...
I just chose this ROM, because it looked good, no idea... good choice?
I tried to avoid having to ask questions, but I reached a point where I can't get the Inforamtions just from reading anymore and am scared of causing irreperable damage to my phone.
I wanted to ask in the Desire XS version 1.1 directly, but wasn't allowed to.
Well I followed this guide:
http://forum.xda-developers.com/showthread.php?t=1525100
and unlocked my bootloader via HTCdev. I'm still on HBOOT 2.00.0002 and S-On
After having done this, I want FIRST do a full recovery of my system, to be able to go back to 2.3.5 if the new ROM doesn't work. Or is this not necessary?
Furthermore I don't want Reaper v2.1, but Desire XS version 1.1. So I downloaded this and copied on the SD. Now, I "have to copy boot.img into the folder where I have adb and fastboot ". But where can I find boot.img within the ROM? I found it 2 times in \Kernel\b2b and \Kernel\patched. Is one of them the right one?!
Also in the Desire XS version 1.1 thread it is says "I recommend that all users be on radio 20.76.30.0835U_3831.19.00.110 before installing this rom"
But I couldn't find any information to switch to this specific radio (just others).
Some information on my phone:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2. 00. 0002
RADIO-3822.10.08.04_M
eMMC-boot
Somewhere in the Desire XS-Thread I found this:
Quote:
Originally Posted by roman_kaczynski View Post
Can i use this rom with hboot 2.02.0002 S-ON and radio 3831.19.00.110?
Yes, you have the last radio.
You are s-on, flash boot.img whit fastboot.
Click to expand...
Click to collapse
I'm sorry for opening a new thread, for the many questions and the long explanation, but I tried to make my problem as clear as possible and wasn't allowed to post in the developer's thread about radio and boot.img...
Thanks for the help!
While flashing the rom you have a choice of 2 kernels (b2b and patched). Use the boot.img of the kernel you will be choosing.
If you want to upgrade the radio (while still s-on) you need to relock your bootloader, flash the Ics RUU, unlock your bootloader again. (some users reported camera issues on desire xs with an older radio version, you could try it first with your current radio).
teadrinker said:
While flashing the rom you have a choice of 2 kernels (b2b and patched). Use the boot.img of the kernel you will be choosing.
If you want to upgrade the radio (while still s-on) you need to relock your bootloader, flash the Ics RUU, unlock your bootloader again. (some users reported camera issues on desire xs with an older radio version, you could try it first with your current radio).
Click to expand...
Click to collapse
Thanks. I guess I'll take the b2b kernel then, since it's the one mentioned in the description. or is the other better?!
Also when flashed is there a way back to the version I have now?! (since you didn't answer my question regarding a recovery of the current system) Can I afterwards just recover via a RUU?!
I'm still scared of ending up with a broken phone
You can make a backup in recovery before flashing, just remember to flash the boot.img from your backup as well if you restore it.
The main difference is, the patched kernel supports overclocking and undervolting, the b2b doesn't.
but how can I do a recovery? My phone is not rooted yet and S-Off (it's just unlocked), is it possible to create a recovery like that?
edit: I found my exact system (2.10.166.3) on htcdev, I guess in the worst case I'll be able to get it back from there. I hope just hope for the best! =)
eggerph said:
but how can I do a recovery? My phone is not rooted yet and S-Off (it's just unlocked), is it possible to create a recovery like that?
edit: I found my exact system (2.10.166.3) on htcdev, I guess in the worst case I'll be able to get it back from there. I hope just hope for the best! =)
Click to expand...
Click to collapse
You have to flash the recovery.img in fastboot. (fastboot flash recovery recovery.img)
Them you can choose recovery from the bootloader.
it worked all good. New system is stable and fluent! lot's of fun, thanks!