Hey guys,
I have an HTC One X with the bootloader unlocked that has Venom Viper installed on it and I want to S-OFF the phone so that I can install the beast mode kernel. I want to do this because the phone has some issues like a dropping SIM card and random reboots. I have another friend with the same phone that I installed Viper on and she had the same issues. I over the phone talked her through the S-OFF method and once we finally got it and installed the kernel the phone worked perfectly.
One thing that was odd is that the method (FacePalm) wasn't working until we flashed the phone back to stock (not a backup but a stock release with a flashable SU bin that was on XDA somewhere). Once we did that the phone was S-OFF after rebooting into the bootloader.
This time around though I'm starting to wonder whether the fact it worked when we flashed back to stock was a coincidence because I did the SAME EXACT THING with this current phone, flashed to the same stock rom with the same method of SU, and it just won't work. I run through the whole process and get no errors (except when you are supposed to) and when I reboot into recovery it is not S-OFF. One thing I noticed though is that on another site it said "The last step is to confirm the SU request you get on your phone". I cannot remember if my friend got a popup but on this phone I never get one.
Therfore I am thinking the problem is with the flashable SU bin not working properly and was going to ask if anyone had their hands on a prerooted stock. There is a thread for one on here but the link is dead.
So basically does anyone have such a rom or know anything about the S-OFF method only working with stock or odex/deodex or something of that sort.
Thanks.
I got s-off with viper
Sent from my VENOMized HoxL
area51avenger said:
I got s-off with viper
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
I guess Ill just keep trying it. Did you use the files from xda?
Do you have the One X (Endeavoru) or the One XL (Evita)?
Sent from my Evita
timmaaa said:
Do you have the One X (Endeavoru) or the One XL (Evita)?
Sent from my Evita
Click to expand...
Click to collapse
Just the X (Endeavoru)
Ok you're in the wrong forum then, this is the One XL forum.
Sent from my Evita
timmaaa said:
Ok you're in the wrong forum then, this is the One XL forum.
Sent from my Evita
Click to expand...
Click to collapse
Actually it is the XL I just forget its not called that. Im sure because its black, from AT&T, and not the international version.
The colour is irrelevant, but if it's from at&t you have the Evita. Are you sure you have superuser installed and usb debugging is enabled in developer options? Which Android version is the ROM you're using?
Sent from my Evita
timmaaa said:
The colour is irrelevant, but if it's from at&t you have the Evita. Are you sure you have superuser installed and usb debugging is enabled in developer options? Which Android version is the ROM you're using?
Sent from my Evita
Click to expand...
Click to collapse
Ya both because i saw the SU app and I used adb so debugging is enabled.
Android ver 4.2.2
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
timmaaa said:
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Ok thanks for the tip.
timmaaa said:
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Sigh. After trying to flash a 4.1.1 Rom the phone now boot loops and flashing any other rooms or restoring the TWRP backup (just system, boot, and data) that I had of viper have had no effect.
Did you flash the boot.img via fastboot?
Sent from my Evita
timmaaa said:
Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Not during the first boot, but after I realized my error I rebooted into fastboot and did it. Is it imperative that its done before booting?
EDIT:
OK so I just tried flashing the stock rom I tried for S-OFF before and even flashed the boot.img and its still boot looping.
It pisses me off that the security system has to be this obnoxious. I'm used to my own samsung phones where theres barely any security and bricking is practically impossible with Odin.
It isn't obnoxious if you know what you're doing. You're s-on so you must flash the boot.img for each ROM every time you flash a ROM. Install ROM, reboot to bootloader, flash boot.img, reboot to system. Once you have s-off you will no longer need to do this. Are you flashing the right boot.img?
Sent from my Evita
timmaaa said:
It isn't obnoxious if you know what you're doing. You're s-on so you must flash the boot.img for each ROM every time you flash a ROM. Install ROM, reboot to bootloader, flash boot.img, reboot to system. Once you have s-off you will no longer need to do this. Are you flashing the right boot.img?
Sent from my Evita
Click to expand...
Click to collapse
Ok well, I changed ONE simple thing that I would think wouldn't matter, but apparently it does. Instead of rebooting after the rom flashing and then during the boot loop holding vol down and power to get into bootloader again, AND THEN flashing the boot.img, I simply hit home in twrp after flashing the room and used the "reboot" function to go directly to boot loader and then flashed the boot.img
The phone now got past the developer warning screen and is showing the htc one beats audio screen. However it now seems to be frozen there :|
This is the rom I used: http://forum.xda-developers.com/showthread.php?t=2181891
It is a step further at least, and now that I see how to properly flash the boot.img I will try a few other roms and see if they work any better, unless you have any other suggestions.
It looks as though you've done it correctly. Which recovery version are you using?
Sent from my Evita
timmaaa said:
It looks as though you've done it correctly. Which recovery version are you using?
Sent from my Evita
Click to expand...
Click to collapse
2.6.3.0
Are you certain you're flashing the boot.img from the ROM you've just installed and not another one by mistake? TWRP 2.6.3 should be ok, but you could try 2.6 instead if you want to, I've seen a couple of bugs on 2.6.3 but I can't remember what they were.
Sent from my Evita
timmaaa said:
Are you certain you're flashing the boot.img from the ROM you've just installed and not another one by mistake? TWRP 2.6.3 should be ok, but you could try 2.6 instead if you want to, I've seen a couple of bugs on 2.6.3 but I can't remember what they were.
Sent from my Evita
Click to expand...
Click to collapse
Yes I am sure. Ill try a different ROM snd if that doesn't work ill downgrade TWRP
Related
I have an HTC One X sitting here that I bought from somebody. It came rooted with an unlocked bootloader running CleanRom. I downloaded CM, wiped like usual and flashed the rom. I can't get it to boot now, it endlessly shows the CM boot logo (but doesn't appear to be restarting) and I was wondering if there was anything special I had to do to get CM working.
Fastboot flash boot boot.img......
Sent from my HTC One XL using Tapatalk 2
rpomponio said:
Fastboot flash boot boot.img......
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I take the boot.img from the zip and flash that in fastboot?
driftkidd2323 said:
I take the boot.img from the zip and flash that in fastboot?
Click to expand...
Click to collapse
Yes sir. Depending on what version your hboot is, that might be your problem..
Sent from my HTC One XL using Tapatalk 2
rpomponio said:
Yes sir. Depending on what version your hboot is, that might be your problem..
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
cm10 booted right up, thanks!
driftkidd2323 said:
cm10 booted right up, thanks!
Click to expand...
Click to collapse
Your welcome, please hit the thanks button.
Sent from my HTC One XL using Tapatalk 2
Help
rpomponio said:
Yes sir. Depending on what version your hboot is, that might be your problem..
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Hello, I as well have a HTC one X Evita the HBoot curently is 1.14.0002 Do you belive that is the problem with mine as well? If so I do know how to use Fastboot and all but do i need to Install the ROM first then Flash the boot.img over or does it mater what order.
cassidyc123 said:
Hello, I as well have a HTC one X Evita the HBoot curently is 1.14.0002 Do you belive that is the problem with mine as well? If so I do know how to use Fastboot and all but do i need to Install the ROM first then Flash the boot.img over or does it mater what order.
Click to expand...
Click to collapse
If you are on hboot 1.14, and have flashed CM10, and not the boot.img, than yes, this almost certainly your problem.
It doesn't matter whether you flash boot.img over fastboot before or after the ROM.
Whats the diffence between the boot.img found in the 10.1 zipfile for htc one x and the one linked in download :
Boot.img (secure=0): http://d-h.st/vzF
Which one should I chose?
/ D
danishdaycare said:
Whats the diffence between the boot.img found in the 10.1 zipfile for htc one x and the one linked in download :
Boot.img (secure=0): http://d-h.st/vzF
Which one should I chose?
/ D
Click to expand...
Click to collapse
um http://d-h.st/vzF is for the endeavoru so NO one here would EVER flash it. do you have an evita or an endeavoru? this forum is for the evita.
DvineLord said:
um http://d-h.st/vzF is for the endeavoru so NO one here would EVER flash it. do you have an evita or an endeavoru? this forum is for the evita.
Click to expand...
Click to collapse
I accidentally flashed my evita with an endeavoru boot.img and now it's stuck in a splash screen boot loop. Is there any way to fix this? Thanks guys.
flint24 said:
I accidentally flashed my evita with an endeavoru boot.img and now it's stuck in a splash screen boot loop. Is there any way to fix this? Thanks guys.
Click to expand...
Click to collapse
Flash the evita boot.img?
exad said:
Flash the evita boot.img?
Click to expand...
Click to collapse
Sure but which one? Any one? I found this link by Googling but I hope I'm putting the right boot on my phone. I got my One XL from Germany around November 2012.
http://forum.xda-developers.com/showthread.php?t=2119610
flint24 said:
Sure but which one? Any one? I found this link by Googling but I hope I'm putting the right boot on my phone. I got my One XL from Germany around November 2012.
http://forum.xda-developers.com/showthread.php?t=2119610
Click to expand...
Click to collapse
If you bootloader says Evita, stay here. If not, run away... far, far away and never come back.
If it is evita go to a cm10/10.1 thread, grab the correct version and pull the boot.img from it. NEVER google for anything, now that you have found this forum. That's one of the quickest ways to break your phone.
Myrder said:
If you bootloader says Evita, stay here. If not, run away... far, far away and never come back.
If it is evita go to a cm10/10.1 thread, grab the correct version and pull the boot.img from it. NEVER google for anything, now that you have found this forum. That's one of the quickest ways to break your phone.
Click to expand...
Click to collapse
Thanks. I'm downloading it now from a reeeeaaaally slow connection so it'll take time to see if this works.
Also I've unlocked my bootloader but it also says "TAMPERED." Should I be worried about that?
flint24 said:
Thanks. I'm downloading it now from a reeeeaaaally slow connection so it'll take time to see if this works.
Also I've unlocked my bootloader but it also says "TAMPERED." Should I be worried about that?
Click to expand...
Click to collapse
Tampered is an indication that you unlocked the phone. You can remove it by RUUing after S-OFF if it bothers you.
I followed Myrder's advice and loaded CM 10 for evita and it got me back into my phone but the touchscreen isn't working now
flint24 said:
I followed Myrder's advice and loaded CM 10 for evita and it got me back into my phone but the touchscreen isn't working now
Click to expand...
Click to collapse
If you have hboot 2.14 you need to downgrade your touchscreen firmware to get touchscreen working in AOSP ROMS
Sounds to me like you really need to do some reading. And really, reading should be done before attempting any of the things you're doing to your phone. You're lucky you haven't bricked it.
Sent from my Evita using XDA Premium
I'm kind of in a chicken before the egg situation. I found the files and commands needed to downgrade my touchscreen, however I think this requires the phone to have usb debugging on, which I can't select because the touchscreen doesn't work.
If that's not necessary because it's all in fastboot anyway, then I have to figure out why I'm getting a "remote 99 unknown fail" and a "status read fail too many links" error message when I try to run the commands for S-OFF and touchscreen downgrade in bootloader.
Hi everyone,
I don't quite have 10 posts yet, so I can't post in the UrDroid thread.
I had UrDroid 1.8, and it worked just fine, had some wifi issues (sometimes after turning the wifi off, it wouldn't turn on again unless I rebooted), so I upgraded to 1.9
Now I have a few issues:
It stays "connected" to a wifi network even after losing connection
Occasionally, after rebooting, my Beautiful Widgets go away and my default keyboard reverts to the stock keyboard (from swype)
occasionally I cannot turn the wifi back on after turning it off without a reboot
That's about it. If anyone has any ideas, please let me know. Thanks! :good:
Could be just bugs in the software. Recommend trying different ROMs
Sent from my Carbon-ize Evita using xda-developers app
I really wish I could try other roms, for some reason UrDroid is the only one that actually works, I have no idea why this is!
For instance, when flashing any verison of CM, after flashing and rebooting, it stays stuck on the loading screen, and doesn't go further, even after waiting a half an hour. AOKP and the others basically brick my phone. I think it has something to do with the UrDroid using Aroma Installer that seems to work well with my phone and twrp. I'm a bit of a n00b, so don't know for sure.
Was hoping someone else had these issues and could tell me how they fixed them.
Herc08 said:
Could be just bugs in the software. Recommend trying different ROMs
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
What recovery are you using and version?
What hboot do you have?
Sent from my One X using xda app-developers app
Sorry for the late reply,I've had the darndest time getting into recovery since installing UrDroid 1.9!
I have HBOOT-1.14.002 and TWRP v. 2.3.1.0
Thanks for any help you could offer- I like UrDroid, but would like to try CM or the other ones!
exad said:
What recovery are you using and version?
What hboot do you have?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
choeffe said:
Sorry for the late reply,I've had the darndest time getting into recovery since installing UrDroid 1.9!
I have HBOOT-1.14.002 and TWRP v. 2.3.1.0
Thanks for any help you could offer- I like UrDroid, but would like to try CM or the other ones!
Click to expand...
Click to collapse
Because of your hboot version you need to flash the boot.img seperately. It is possible that you are doing this but still encountering bootloops and the reason for that would be Hboot compatibility. I have noticed that some ROMs just do not play nice with certain hboots. The most compatible hboot that I've seen is 2.14 which seems to be the same accross all carrier phones.
That being said, my suggestion to you is to S-OFF if you aren't already, then, while keeping your bootloader unlocked, RUU up to 3.18 or 3.17 or whatever is the latest for your carrier which will update your hboot to 2.14 and then downgrade your touchscreen firmware which is super easy and there's a sticky for the process in the Original Android Development section.
After that, you should be able to run all roms without much issue AND you won't have to fastboot flash boot boot.img anymore.
That explains it- I literally have just been going into TWRP, installing the zip file, and then rebooting. I'm not even sure where I would find the boot.img, would that be inside the zip file?
So to S-OFF, should I follow the directions here: http://forum.xda-developers.com/showthread.php?t=2155071
I'm not sure how to RUU, any chance you or someone might have a link on instructions to do that? (I have an AT&T phone that I use on Straight Talk)
Thanks for your help, and if I'm asking for too much information, I'll keep doing some reasearch. I think the RUU is what kind of puzzles me (I'm clearly pretty green when it comes to rooting, I've only ever done it on this phone, not very successfully!
exad said:
Because of your hboot version you need to flash the boot.img seperately. It is possible that you are doing this but still encountering bootloops and the reason for that would be Hboot compatibility. I have noticed that some ROMs just do not play nice with certain hboots. The most compatible hboot that I've seen is 2.14 which seems to be the same accross all carrier phones.
That being said, my suggestion to you is to S-OFF if you aren't already, then, while keeping your bootloader unlocked, RUU up to 3.18 or 3.17 or whatever is the latest for your carrier which will update your hboot to 2.14 and then downgrade your touchscreen firmware which is super easy and there's a sticky for the process in the Original Android Development section.
After that, you should be able to run all roms without much issue AND you won't have to fastboot flash boot boot.img anymore.
Click to expand...
Click to collapse
choeffe said:
That explains it- I literally have just been going into TWRP, installing the zip file, and then rebooting. I'm not even sure where I would find the boot.img, would that be inside the zip file?
Click to expand...
Click to collapse
Yes it's in the zip. You extract it then fastboot flash boot boot.Img right before or after flashing the rom in recovery. Before flashing the rom and boot.img you should wipe cache, dalvik, system and factory reset. And only ever flash roms for the one xl or you risk bricking.
choeffe said:
So to S-OFF, should I follow the directions here: http://forum.xda-developers.com/showthread.php?t=2155071
Click to expand...
Click to collapse
Yes
choeffe said:
I'm not sure how to RUU, any chance you or someone might have a link on instructions to do that? (I have an AT&T phone that I use on Straight Talk)
Thanks for your help, and if I'm asking for too much information, I'll keep doing some reasearch. I think the RUU is what kind of puzzles me (I'm clearly pretty green when it comes to rooting, I've only ever done it on this phone, not very successfully!
Click to expand...
Click to collapse
To ruu, just download the ruu exe file and run it. But make sure you're s-off first or you'll brick.
Reading the stickies is suggested. You picked a ***** of a phone to be your first to root.
Sent from my One X using xda app-developers app
Thanks for your help thus far! I'm going to give it a try and see how it goes.
Yeah, I definitely wish I would have started with a Nexus or Sony device, but I changed from T-Mobile (worse decision of my life to go with them in the first place) to Straight Talk SIM with AT&T, and the HTC One X looked so pretty! Next phone is going to be a Nexus!
exad said:
Yes it's in the zip. You extract it then fastboot flash boot boot.Img right before or after flashing the rom in recovery. Before flashing the rom and boot.img you should wipe cache, dalvik, system and factory reset. And only ever flash roms for the one xl or you risk bricking.
Yes
To ruu, just download the ruu exe file and run it. But make sure you're s-off first or you'll brick.
Reading the stickies is suggested. You picked a ***** of a phone to be your first to root.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...
Ayahuascaa said:
Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...
Click to expand...
Click to collapse
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.
watameron said:
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.
Click to expand...
Click to collapse
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.
Ayahuascaa said:
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.
Click to expand...
Click to collapse
What HBOOT version do you have?
Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.
redpoint73 said:
Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.
Click to expand...
Click to collapse
ViperXL JB
and my hboot is 2.14
Ayahuascaa said:
ViperXL JB
and my hboot is 2.14
Click to expand...
Click to collapse
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.
exad said:
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.
Click to expand...
Click to collapse
Hmm.. I could have. I did it last night after two hours of frustration.
And I just did that to a new install of Nocturnal's rom, but with no luck. It still just hangs at the HTC dev warning screen. I'm going to try re downloading the ViperXL rom and hope I just had a bad copy..
heh. I did that without thinking last night and spent an hour trying to reverse the damage I did. Not only did I have s-on, but my cid was still "1111111".
./
Androidfilehost is only giving me ~50Kbps, so viper's rom has 3 hours left,
but Cleanrom is almost done.
Is there anyway to s-off the evita without booting into an os?
If not, can someone point me to a thread explaining how to manually s-off?
It seems that it's the cause for all this trouble I'm having and I've never had to do manually.
Thank you everyone for your help,
my phone still doesn't have a working os but I do feel like I'm getting somewhere.
Edit: How many of you have had problems installing roms with twrp 2.5.5.0? I'm thinking about trying 2.3.3.1. I thought this was what I flashed last night, but my touchscreen didn't work and according to exad's post I probably had the wrong one.
Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
exad said:
Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.
Ayahuascaa said:
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.
Edit: Can you point me to a link for twrp 2.3.3.1? The only thread on xda for that build doesn't have working download links
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app
exad said:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
CleanRom boots!
Thanks again to everyone who helped and exad for the 2.3.3.1 link,
I didn't have this problem before.But now everytime i flash a cm rom,it flashes with no problems but when it finishes flashing and i reboot,it gets stuck on the htc logo,then reboots and does the same and the same all over again till the battery dies.I tried getting on recovery mode/bootloader but it doesnt seem to work.It's kinda as if the buttons didn't work.This happened to me already 2 days ago and fixed it,but had to wait till the battery died,then connect to pc,that way my phone was somehow reconized and i was able to adb(even though i wasn't on recovery or bootloader,just plugged to the pc)
what is causing this problem with cm roms?what should i do?
Do I need to downgrade/upgrade my hboot or something?
Thank you guys,and sorry for my english.
avlbj6 said:
I didn't have this problem before.But now everytime i flash a cm rom,it flashes with no problems but when it finishes flashing and i reboot,it gets stuck on the htc logo,then reboots and does the same and the same all over again till the battery dies.I tried getting on recovery mode/bootloader but it doesnt seem to work.It's kinda as if the buttons didn't work.This happened to me already 2 days ago and fixed it,but had to wait till the battery died,then connect to pc,that way my phone was somehow reconized and i was able to adb(even though i wasn't on recovery or bootloader,just plugged to the pc)
what is causing this problem with cm roms?what should i do?
Do I need to downgrade/upgrade my hboot or something?
Thank you guys,and sorry for my english.
Click to expand...
Click to collapse
If you can get into bootloader try flashing the boot.img via fastboot
ronnie498 said:
If you can get into bootloader try flashing the boot.img via fastboot
Click to expand...
Click to collapse
I can't get into bootloader
If you have adb access, what happens when you do:
Code:
adb reboot bootloader
hi_cannon said:
If you have adb access, what happens when you do:
Code:
adb reboot bootloader
Click to expand...
Click to collapse
He won't have adb access because that requires the phone to be booted into the OS.
Sent from my Evita
then connect to pc,that way my phone was somehow reconized and i was able to adb
Click to expand...
Click to collapse
:fingers-crossed:
hi_cannon said:
If you have adb access, what happens when you do:
Code:
adb reboot bootloader
Click to expand...
Click to collapse
my question wasnt "how to get adb access" or "how to get to recovery/bootloader"..I just wanted to know why my phone is having problems with those roms.It works fine with sense based roms but not with cm based.
avlbj6 said:
my question wasnt "how to get adb access" or "how to get to recovery/bootloader"..I just wanted to know why my phone is having problems with those roms.It works fine with sense based roms but not with cm based.
Click to expand...
Click to collapse
Did you run the 3.18 RUU?
What hboot and firmware version are you on?
Sent from my Evita
Hboot 1.09
Sent from my HTC One XL using Tapatalk 2
hi_cannon said:
Did you run the 3.18 RUU?
Click to expand...
Click to collapse
No I didn't.is that so?
Sent from my HTC One XL using Tapatalk 2
timmaaa said:
What hboot and firmware version are you on?
Sent from my Evita
Click to expand...
Click to collapse
Hboot 1.09
Sent from my HTC One XL using Tapatalk 2
odd problem until now since newest aosp need 3.18 base or 2.14 hboot.
I keep confusing quote with reply smh lol
DvineLord said:
odd problem until now since newest aosp need 3.18 base or 2.14 hboot.
Click to expand...
Click to collapse
So which ruu 3.18 should I use?do you have a link?also,should I upgrade the hboot?
Sent from my HTC One XL using Tapatalk 2
avlbj6 said:
So which ruu 3.18 should I use?do you have a link?also,should I upgrade the hboot?
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
This is the 3.18 RUU, it'll also update your hboot to the latest (2.14), so you don't need to do that manually:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
You will need to s-off first though, here's the link:
http://forum.xda-developers.com/showthread.php?t=2155071
So flash a Sense ROM like MagioRom Sense 5, Viper, Hatka, Cleanrom, or one of the stock Sense ROMs. Then get s-off using the method I linked to above. Then run the RUU. Then you should be good to go.
Sent from my Evita
timmaaa said:
This is the 3.18 RUU, it'll also update your hboot to the latest (2.14), so you don't need to do that manually:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
You will need to s-off first though, here's the link:
http://forum.xda-developers.com/showthread.php?t=2155071
So flash a Sense ROM like MagioRom Sense 5, Viper, Hatka, Cleanrom, or one of the stock Sense ROMs. Then get s-off using the method I linked to above. Then run the RUU. Then you should be good to go.
Sent from my Evita
Click to expand...
Click to collapse
Thanks man.And I'm already s-off and I been running magiorom since he released it.But ima do the ruu part now
Sent from my HTC One XL using Tapatalk 2
I have a European One S (S4) with Hboot 2.15. Unlocked via htcdev. I cant figure out how to get s-off. Writing supercid doesnt work.. How to fix it?
S1pk3 said:
I have a European One S (S4) with Hboot 2.15. Unlocked via htcdev. I cant figure out how to get s-off. Writing supercid doesnt work.. How to fix it?
Click to expand...
Click to collapse
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Ok, thanks for your reply. I want to flash cm 10.2. That should be possible without s-off?
Sent from my HTC One S using xda app-developers app
S1pk3 said:
Ok, thanks for your reply. I want to flash cm 10.2. That should be possible without s-off?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah. It is just recommended that you are s-off.
As the guy said before you need to flash boot.img (the kernel) afterwards.
Sent from my One S using xda app-developers app
Will give it a try. Thanks.
Sent from my HTC One S using xda app-developers app
Stuck while flashing firmware in htc one s
I got stuck while installing htc one s with maximus hd..
http://forum.xda-developers.com/showthread.php?t=2445392&highlight=sense+5
I did till fastboot flash recovery TWRP2.6.1.0.img ...but aftr fast boot reboot it dint take memory...without that i cant copy ROM to memory...i did unlock bootloader not s off.... i got an error99 while flashing firmware.. icant on the device now....please help me...
tivofool said:
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Click to expand...
Click to collapse
I just noticed this thread.
I also have a similar problem. I cannot achieve s-off with my (S4) htc one s , running the exact same hboot as op.
To upgrade to jb 4.2.2 sense 5 which we should be getting for which we now won't despite them making the update.
Will we be able to upgrade to this new patch with s-on using the flash boot?
sylvantino said:
I just noticed this thread.
I also have a similar problem. I cannot achieve s-off with my (S4) htc one s , running the exact same hboot as op.
To upgrade to jb 4.2.2 sense 5 which we should be getting for which we now won't despite them making the update.
Will we be able to upgrade to this new patch with s-on using the flash boot?
Click to expand...
Click to collapse
Maximus HD --- No you need S-off for this. The firmware updates your Hboot, Radio, and you flash a different recovery and finally Rom
You might check out other Rom's that have Sense 5 4.2.2 features. They do not require S-off like Maximus does.
Hi thanks for your reply.
Do you know of any such roms that don't require the s-off?
I installed odyssey, its got no google playstore..suddenly my computer no longer recognizes my sd card / phone.
I tried adb push, managed to get a stock orang001 tmobile uk package to the root folder, but when i turn off the mount, it says its bad..which is a little odd.
Seems thought I got odyssey installed / flashed etc, its so bare as its practically useless to me unless i have google, plus its got weird glitches on boot up, taking forever, always booting into the developers screen etc.
sylvantino said:
Hi thanks for your reply.
Do you know of any such roms that don't require the s-off?
I installed odyssey, its got no google playstore..suddenly my computer no longer recognizes my sd card / phone.
I tried adb push, managed to get a stock orang001 tmobile uk package to the root folder, but when i turn off the mount, it says its bad..which is a little odd.
Seems thought I got odyssey installed / flashed etc, its so bare as its practically useless to me unless i have google, plus its got weird glitches on boot up, taking forever, always booting into the developers screen etc.
Click to expand...
Click to collapse
With Odyssey you have to flash slim gapps after you install the rom.
Your Sd card (partition) may be corrupted, the way to fix that is to put the stock recovery back on your phone then go to bootloader and "clear storage"
All of the other Roms don't require S-off, MagioRom is being actively developed with the sense 5 and 4.2.2.
tivofool said:
With Odyssey you have to flash slim gapps after you install the rom.
Your Sd card (partition) may be corrupted, the way to fix that is to put the stock recovery back on your phone then go to bootloader and "clear storage"
All of the other Roms don't require S-off, MagioRom is being actively developed with the sense 5 and 4.2.2.
Click to expand...
Click to collapse
thanks for the information. i read through magiorom thread. trying to download now.seems a flaky webhost
tivofool said:
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Click to expand...
Click to collapse
Hi would moonshine work for hboot 2.16 ?
cyberusman said:
Hi would moonshine work for hboot 2.16 ?
Click to expand...
Click to collapse
No, it is hard enough to get it to work on the supported firmware. (I would love to be proven wrong, for the handful of people that need this)
tivofool said:
No, it is hard enough to get it to work on the supported firmware. (I would love to be proven wrong, for the handful of people that need this)
Click to expand...
Click to collapse
Well i have hboot 2.16 and i need to s-off i get this error when trying to flash the ruu its error 99 unknown fail i get it twice
tivofool said:
Maximus HD --- No you need S-off for this. The firmware updates your Hboot, Radio, and you flash a different recovery and finally Rom
You might check out other Rom's that have Sense 5 4.2.2 features. They do not require S-off like Maximus does.
Click to expand...
Click to collapse
I was able to load Maximus HD ROM with S-On but only issue I had was wireless.
santo_2k said:
I was able to load Maximus HD ROM with S-On but only issue I had was wireless.
Click to expand...
Click to collapse
Please tell me how did you manage to install MaximusHD ROM without S-off!
I'm a little scared since I read they have a lot of problems while installing this ROM.
I'm using CM10.1 right now, but I would like to have sense 5 on my HTC One S.
I have unlocked boot loader and TWRP recovery.
I read there are other ROMS with sense 5 like MagioRom, which doesn't require S-Off (As far as I know)
Is there a great difference between MagioRom and MaxiumusHD? All I want is Sense 5 on my phone without all the terrible of S-offing!!
Sent from my One S using xda app-developers app
rolo143 said:
Please tell me how did you manage to install MaximusHD ROM without S-off!
I'm a little scared since I read they have a lot of problems while installing this ROM.
I'm using CM10.1 right now, but I would like to have sense 5 on my HTC One S.
I have unlocked boot loader and TWRP recovery.
I read there are other ROMS with sense 5 like MagioRom, which doesn't require S-Off (As far as I know)
Is there a great difference between MagioRom and MaxiumusHD? All I want is Sense 5 on my phone without all the terrible of S-offing!!
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I tried Maximus with CWM, did i using sideload and them flash the boot.img file. but it was a disaster as my device didn't connect to wifi and had some call drops then I tried flashing twrp and then sideloaded magicrom 4.0 and flas boot.img, it looks lot better now but only issue right now is my phone keeps on rebooting and am still waiting for a stable rom to be released.
I read MagioRom comments and they say with that ROM phone reboots a lot. So I think the only way is with MaximusHD. The WiFi problem I think it can be fixed. I don't know about the call drops, but many have this ROM as daily use so I guess it's ok. I will try S-off with moonshine method, then try install Maximus. Hope my phone survives.
Sent from my One S using xda app-developers app