Database Info

[Solved] Cyanogen won't work...

I have a problem, kinda.
I decided to flash Cyanogen, spent 20+ hours reading forums and raping my phone, flashed several ROMs (saga3g by proxuser, for instance), but I can't make Cyanogen work, it freezes at the "htc" screen (the one with green letters at the white background). Also, when I shut it down (battery pull or 3-button hold), it restarts in a couple of seconds.
Specs: hboot 2.00.0002, S-on, htc-dev unlocked, clockwork mod, rooted.
Any ideas what am I doing wrong?

Sarnetsky said:
I have a problem, kinda.
I decided to flash Cyanogen, spent 20+ hours reading forums and raping my phone, flashed several ROMs (saga3g by proxuser, for instance), but I can't make Cyanogen work, it freezes at the "htc" screen (the one with green letters at the white background). Also, when I shut it down (battery pull or 3-button hold), it restarts in a couple of seconds.
Specs: hboot 2.00.0002, S-on, htc-dev unlocked, clockwork mod, rooted.
Any ideas what am I doing wrong?
Click to expand...
Click to collapse
If you are still S-On then anything requiring a different kernel to the stock HTC one will require the boot.img (kernel) to be installed via fastboot prior to flashing the ROM.
Procedure described here: http://forum.xda-developers.com/showpost.php?p=19082155&postcount=41
You have done well learning what you have done so far, considering you only PM'd me about it at the start of the weekend, and by the time I get around to replying, I see you have figured it out! So I highly recommend you take the final step and get S-Off. Else you'll have to use fastboot to push a kernel over with every ROM change.

wnp_79 said:
Procedure described here: http://forum.xda-developers.com/showpost.php?p=19082155&postcount=41.
Click to expand...
Click to collapse
So after these 4 steps I'll get S-off?
It just looks like ROM-specific procedure, so I want to clarify

Sarnetsky said:
So after these 4 steps I'll get S-off?
It just looks like flash-specific procedure, so I want to clarify
Click to expand...
Click to collapse
No sorry that is to push the boot.img over using fastboot. To s-off check the index thread.
Sent from my HTC Desire S using xda premium

I'm very much obliged for your help, now I have Cyanogen 7.1 on my phone *yay!*
I think I won't change ROMs often enough, so flashing boot image won't be a difficulty. also, I'll check every now and then with Revolutionary, and when they support hboot 2.00.0002, I'll get S-off. Anyway, now I'm finally happy I managed (with your help, wnp_79, and with the help of the whole xda commmunity) to give Cyanogen a try
Thanks for your help

Sarnetsky said:
I'm very much obliged for your help, now I have Cyanogen 7.1 on my phone *yay!*
I think I won't change ROMs often enough, so flashing boot image won't be a difficulty. also, I'll check every now and then with Revolutionary, and when they support hboot 2.00.0002, I'll get S-off. Anyway, now I'm finally happy I managed (with your help, wnp_79, and withthe help of the whole xda commmunity) to give Cyanogen a try
Thanks for your help
Click to expand...
Click to collapse
No problem. You did most of the work! This is a perfect example of what people can do when they use the search function properly and take their time to read. Well done.
One final thing, once you start a question thread that gets solved, change the title of the thread to say [SOLVED] at the beginning so people know you are ok and others can read and learn!
Sent from my HTC Desire S using xda premium

Nailed it
I tried to mark it as solved before, but couldn't find the proper button.

[Q] After Flashing JB Rom, Won't Boot

First: Thanks to this great forum of developers and users, I have learned a lot in a short period of time. The HTC One S is my first Android handset, and I love it. All the wonderful tutorials and threads you guys created made learning the basics of rooting/flashing easy.
This is my second HTC One S handset, the previous one died from hardware failure. The previous handset had HBoot 1.06, and so I was able to flash the TWRP recovery and use the Trickdroid 9.1.0 flawlessly. The problem comes with this new handset, and I am not sure exactly what it is to troubleshoot. The current HBoot on the phone is 1.14 (which means I can't flash radios, etc.). After unlocking the bootloader, I flashed the latest TWRP recovery (2.4.1.0). After factory resetting the phone and installing the Trickdroid 9.1.0, the phone won't boot. If I hold the power for 5-10 seconds, the keys flash, that's it. I am able to get into the bootloader using the power + volume down method, and then I have to recover my phone back to factory settings using the RUU avaliable online. I have tried redoing this process 2-3 times now, and everytime I flash the JB rom, the phone won't boot. I am not sure if having a HBoot 1.14 prevents me from upgrading from ICS --> JB, recovery, or anything else. As I said, my knowledge of Android is very limited as I am a new user. I really would like to use the JB rom that is cleaned and optimized. If anyone has any suggestions on what I can do, I would greatly appreciate it. Right now, I just did the perm root to be able to get rid of some of the bloat (T-Mobile comes with so much garbage!). Thank you so much, once again, and any troubleshooting help will be returned with big kiss! :angel:

bombina said:
First: Thanks to this great forum of developers and users, I have learned a lot in a short period of time. The HTC One S is my first Android handset, and I love it. All the wonderful tutorials and threads you guys created made learning the basics of rooting/flashing easy.
This is my second HTC One S handset, the previous one died from hardware failure. The previous handset had HBoot 1.06, and so I was able to flash the TWRP recovery and use the Trickdroid 9.1.0 flawlessly. The problem comes with this new handset, and I am not sure exactly what it is to troubleshoot. The current HBoot on the phone is 1.14 (which means I can't flash radios, etc.). After unlocking the bootloader, I flashed the latest TWRP recovery (2.4.1.0). After factory resetting the phone and installing the Trickdroid 9.1.0, the phone won't boot. If I hold the power for 5-10 seconds, the keys flash, that's it. I am able to get into the bootloader using the power + volume down method, and then I have to recover my phone back to factory settings using the RUU avaliable online. I have tried redoing this process 2-3 times now, and everytime I flash the JB rom, the phone won't boot. I am not sure if having a HBoot 1.14 prevents me from upgrading from ICS --> JB, recovery, or anything else. As I said, my knowledge of Android is very limited as I am a new user. I really would like to use the JB rom that is cleaned and optimized. If anyone has any suggestions on what I can do, I would greatly appreciate it. Right now, I just did the perm root to be able to get rid of some of the bloat (T-Mobile comes with so much garbage!). Thank you so much, once again, and any troubleshooting help will be returned with big kiss! :angel:
Click to expand...
Click to collapse
Did you flash the boot.img via fastboot after flashing the rom?

rustykwak said:
Did you flash the boot.img via fastboot after flashing the rom?
Click to expand...
Click to collapse
That seemed to be the problem this whole time! Argh! Thanks! In the previous phone, I always flashed it after rebooting via FlashGUI. I guess the only looming problem now is that the Wifi doesn't work on this Trickdroid ROM for my HBoot (1.14). Blah.

bombina said:
That seemed to be the problem this whole time! Argh! Thanks! In the previous phone, I always flashed it after rebooting via FlashGUI. I guess the only looming problem now is that the Wifi doesn't work on this Trickdroid ROM for my HBoot (1.14). Blah.
Click to expand...
Click to collapse
theres a thread in dev section wifi partions perhaps that will help you out!

rustykwak said:
theres a thread in dev section wifi partions perhaps that will help you out!
Click to expand...
Click to collapse
Unfortunatly on that hboot I dnt think we can
Sent from my HTC One S using xda app-developers app

siqbudz said:
Unfortunatly on that hboot I dnt think we can
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yes, that is right. I think any HBoot higher than 1.09 (I am 1.14) will not be able to flash WiFi partitions. Any way we can make WiFi work on JB? Would upgrading the HBoot to 2.x fix this Wifi problem? I still don't know why it doesn't work though and not having Wifi is kind of a big deal.

[Q] Where to Access Hasoon2000 S-Off Tool?

I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!

If I were you I would stay away from toolkits altogether. Not because they are bad, only because you learn absolutely nothing from using them and usually come bomb the threads when **** hits the fan.
The wire trick is a fun little task to handle though so everything should be okay that way.
Sent from my Nexus 4 using Tapatalk 2

Toolkit
ArachnydZ28 said:
I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!
Click to expand...
Click to collapse
His toolkit is still there, just browse around a bit... or go here... http://d-h.st/users/hasoon2000/?fld_id=2818#files

acwest said:
His toolkit is still there, just browse around a bit... or go here...
Click to expand...
Click to collapse
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".

Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium

demkantor said:
Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
unlocked
Doubleshot PVT Ship S-On RL
Hboot- 1.45.0013
Microp-0353
eMMC-Boot
Nov 21 2011, 20:20:47
I do have recovery and hboot. Stock backup won't load though even though the file is there in recovery.
Thanks!

And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium

demkantor said:
And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I was able to reflash a version of CM10 I was using for a while and that works, but I can't find a stock one that will work. I've tried multiple, and they all give me "bad" error and don't finish the install.
I was going to try a different version of CM10, 10.1, or go to a stable release of 9. If none of those worked, I'd be happier with stock. None of the ones I've tried will work, but I'm assuming thats because I'm S-On, but since I can't find hasoon2000s S-Off tool everyone was raving about, and the wire trick requires stock ROM based on what the directions say, I find myself in a pickle.
The CM10 version I have can't do some basic things I need for work- like sync with my bluetooth in the car or not randomly freeze up during the day without me knowing it sending all my calls to voicemail. I tried versions of the others that other people are using (like silverL's 10.1 and the CM-listed stable CM9) and neither would load.
Do I have a different issue? AKA are other people with S-On able to load those Roms? I can try miktouch too.
---
Also trying to load via fastboot and I'm getting this error:
"Whoops: didn't find expected signature
read_central_directory_entry_failed
error: failed to access zipdata in [Whole bunch of non-english characters taking up a few lines]"
----
Update: Just to clarify, when I try to install a stock rom it gives me "Can't open [filename] (bad)
However, when I try to install the CM's, it installs fine and says "Install from sdcard complete" they just won't load when I restart my phone, except for the original version of CM10. (for example, in all the 10.1s I've tried I get "Unfortunately, the process com.android.phone has stopped" but the intro page will load. I figured that came down to an S-On issue when I tried to troubleshoot.

Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium

demkantor said:
Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.

ArachnydZ28 said:
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.
Click to expand...
Click to collapse
negative.
miktouch would go through the install process, and end at the Tmobile mytouch 4g slide screen forever. I know on one install it took a long time to "load" the first time so I left it on this screen for about 15 minutes to no avail. Let me know if there is any chance of it taking longer than that. Reinstalls were the same story.
I got CM9.1 to install by installing it twice on top of itself (not sure why that fixes it) but it was a tiny bit buggy.
Is there any chance this could be bootloader related or recovery related? I can try to reload those too. grrr...

Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium

demkantor said:
Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!

ArachnydZ28 said:
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!
Click to expand...
Click to collapse
You should try CWM 5.0.2.7. Also, since you are S-On you should extract the boot.img from Miktouch and flash it from fastboot, separately from the ROM. Since you have been on an ICS/Jellybean rom, I have to believe your original boot.img was replaced at some point. This is the only way to get back the Gingerbread boot.img. I am not savvy enough to know if this file is the bootloader or the kernel, but this process should get you back to stock-enough to do the wire trick.
Sent from my SGH-T699 using xda app-developers app

It's the kernel.....the boot.img file, I mean. The bootloader is that mostly white screen you see with "Hboot" at the top that will have "S-On" or "S-Off" after the word Radio. Good response.:good:

ArachnydZ28 said:
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".
Click to expand...
Click to collapse
Load the pd15img.zip on your sd card and boot to your bootloader. It should detect the file on your card and ask if you want to flash it. Just follow the directiins it gives you
Edit: actually should be pd59img not 15
Sent from my SGH-T889 using Tapatalk 2

[Q] Touchscreen not working after flashing the rom to 4.2.2.

Sorry for the repeating post, I know there are many threads out there regarding this problem but I had problems after following those.
I used TWRP and installed "cos-0.7-20130427-NIGHTLY-evita", bootloader is unlocked (via HTCDev) and rooted. But my phone is still returning "ROGER001" when I search for supercid and s-on, hboot 2.14.
I followed this post (to turn s-off) "http://forum.xda-developers.com/showthread.php?t=2155071", but after step 5, I got FAILED (remote: 99 unknown fail) and for the touchscreen firmware (downgrade), I need s-off.
Can anyone help step by step or should I revert back to stock ROM? If I have no other option but reverting back, is there any thread I can follow?
Thanks in advance!

You need to downgrade your touchscreen firmware to get the 4.2.2 since your on hboot 2.14. There's a sticky at the top of the original android thread. as for getting s-off it may take a couple times, I had to changes roms from cm to viper to get mine s-off(ed)

Wubbz said:
You need to downgrade your touchscreen firmware to get the 4.2.2 since your on hboot 2.14. There's a sticky at the top of the original android thread. as for getting s-off it may take a couple times, I had to changes roms from cm to viper to get mine s-off(ed)
Click to expand...
Click to collapse
I saw that post to downgrade the touchscreen firmware, but pre-req for that is to turn s-off, can you please guide me how you did the s-off.

All I can recommend is switching to a Sense based rom if your on an AOSP based one. I was on cm10 or 10.1 when I first tried it, I got the same error 99 or 96 not sure. I tried it about 5 times on cm before switching to Viper 3.2.5 and it worked first try. other than that and fallowing the directions perfectly that's all i got. If you have any other problems I'd try the thread for s-off

Wubbz said:
All I can recommend is switching to a Sense based rom if your on an AOSP based one. I was on cm10 or 10.1 when I first tried it, I got the same error 99 or 96 not sure. I tried it about 5 times on cm before switching to Viper 3.2.5 and it worked first try. other than that and fallowing the directions perfectly that's all i got. If you have any other problems I'd try the thread for s-off
Click to expand...
Click to collapse
Any thread with all the steps?

right here

Wubbz said:
right here
Click to expand...
Click to collapse
lol, that's the thread i mentioned in my first post, I am stuck at step no 5, where I get that 99 error

jashang87 said:
lol, that's the thread i mentioned in my first post, I am stuck at step no 5, where I get that 99 error
Click to expand...
Click to collapse
Press and hold power until the phone shuts off. this will simulate a battery pull. Reboot the PC and then try again. Repeat that until you get error 92. I don't want to say it's normal that you're getting error 99 but it certainly is extremely common. It's not that you're doing anything wrong, it's just the way the exploit works.

exad said:
Press and hold power until the phone shuts off. this will simulate a battery pull. Reboot the PC and then try again. Repeat that until you get error 92. I don't want to say it's normal that you're getting error 99 but it certainly is extremely common. It's not that you're doing anything wrong, it's just the way the exploit works.
Click to expand...
Click to collapse
tried that 5-6 times, still no luck. Is it windows 8 that is causing the problem or how do I check if my phone has SuperCID or not? (it returns "ROGER001" in supercid)

Then it doesn't have supercid. It needs to be 11111111.
Sent from my HTC One X using xda app-developers app

exad said:
Then it doesn't have supercid. It needs to be 11111111.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Any help how can I do SuperCID at this moment. I have OS but no touchscreen, all that available is fastboot and recovery
My phone is unlocked, I followed the instructions on HTCDev.com and it shows unlocked at bootloader screen, but still it is returning "ROGER001"

jashang87 said:
Any help how can I do SuperCID at this moment. I have OS but no touchscreen, all that available is fastboot and recovery
My phone is unlocked, I followed the instructions on HTCDev.com and it shows unlocked at bootloader screen, but still it is returning "ROGER001"
Click to expand...
Click to collapse
From where, I can get RUU for rogers htc one x (hboot-2.14) ?

jashang87 said:
From where, I can get RUU for rogers htc one x (hboot-2.14) ?
Click to expand...
Click to collapse
you need to edit your cid in mmcblck0p4. look into hex edit mmcblck0p4. There's a couple guides floating around in Q&A and General section. I am not sure if you will be able to push the file back since 2.14 introduced write protection of system files.. There was a thread where beaups helped someone to do it in Q&A but I'm at work and can't find it for you right now. If I manage to find out before you I will post it here.

exad said:
you need to edit your cid in mmcblck0p4. look into hex edit mmcblck0p4. There's a couple guides floating around in Q&A and General section. I am not sure if you will be able to push the file back since 2.14 introduced write protection of system files.. There was a thread where beaups helped someone to do it in Q&A but I'm at work and can't find it for you right now. If I manage to find out before you I will post it here.
Click to expand...
Click to collapse
Thanks for your help, I tried that already but didn't work. I flashed my phone with ViperXL rom (with Sense) and its working fine now. I will untill the release of 4.2.2 rom which will have the firmware for touchscreen.

jashang87 said:
Thanks for your help, I tried that already but didn't work. I flashed my phone with ViperXL rom (with Sense) and its working fine now. I will untill the release of 4.2.2 rom which will have the firmware for touchscreen.
Click to expand...
Click to collapse
All you need to do is change your cid in fastboot
Sent from my HTC One X using Xparent Green Tapatalk 2

False. That only works with s-off or if you already have supercid you can change it once without s-off
Sent from my Sony Tablet S using xda app-developers app

exad said:
False. That only works with s-off or if you already have supercid you can change it once without s-off
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Well I tried everything, supercid in fastboot, changing cid manually, tried htc one x all-in-one toolkit. But nothing worked for me, still if there is something else I can try, I will try that.

Downgrade your hboot with jet tool then hex edit your cid.
Sent from my One X using xda app-developers app

[Q] AT&T HTC One X Soft Brick. Tried everything I could find. Suggestions?

So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!

roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.

roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Sent from my Evita

timmaaa said:
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Click to expand...
Click to collapse
Thanks for the reply. I believe the reason I'm not bricked is because I backed out of the installation of Maximus HD during the setup screen progression. The actual ROM was never flashed. However, I have flashed the boot.img and ROMs for Viper, Xylon, and Cyanogenmod with no success. The result is the same every time (HTC screen, then black). I extract the boot.img from each of the roms, flash it, and then flash the ROM. The ROM I flash is a copy of the the original with the boot.img still inside. Perhaps I should be removing the boot.img if I am going to flash it separately in fastboot? And I realize that the threads are specific for certain phones now. It's all kind of a mess to get into at first.

I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita

Madcat8686 said:
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
Click to expand...
Click to collapse
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.

Oh, that's great. Usually it shouldn't matter which order you flash in, but at least it got you out of trouble this time.
Sent from my Evita

roycedavies said:
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Click to expand...
Click to collapse
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!

Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
Hey, you should take the credit, I believe flashing it afterwards was what got his phone booted :thumbup:
Sent from my Evita

Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?

timmaaa said:
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply! I will get the bootloader info ASAP bit don't I need to be s-of in order to RUU? from what I've read, if you don't have unlocked bootloader, root access, and s-off, you'll end up bricking your phone with RUU. I'd really like to do it but I have tried to get s-off to no avail.

No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita

roycedavies said:
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
Click to expand...
Click to collapse
Definitely not normal. A few recommendations:
1. Back up all your stuff, wipe everything except the SD card, Flash a fresh copy of the Rom, Flash the boot.img (you really should consider S-Off), Wipe the cache and DALVIK cache one more time, boot up the system.
2. Same as above except choose another Rom. There are plenty to choose from. The 4.4 Roms are getting a lot better now that the new Kernel fix got rid of the boot loops/reboots.
Sorry about the delay, it's been a heavy week at work. Hope things work out for you.

I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app

timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
Sometimes is pays to see if there is a page 2 to the thread...Sorry about that! lol
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
timmaaa said:
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have no idea how much I have vicariously learned from your posts. Thanks Timmaa! I keep thinking if more of these folks would go ahead and get S-Off they would have waaaaaaaaaay less issues.

Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app

timmaaa said:
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I totally agree now because after rereading the post, there is a radio issue in addition to the boot issue. Is it possible that the Endeverou boot.img messed something up?

Yeah, that's exactly what I'm thinking. An RUU will hopefully fix that right up.
Sent from my Evita.

timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
That sounds like a good plan. (I'm really appreciating all your input by the way! Thanks so much!) One question though, upon checking out the rumrunner website, there isn't specific mention of the HTC One X Evita. Call me paranoid, but after what I've been through I want to make 100% sure I'm compatible before moving forward. Have you or anyone used this specific method for S-Off on the One X Evita?

For the Evita you use the universal HTC method. I've created a thread for it if you want to make sure it's worked for other Evita owners.
http://forum.xda-developers.com/showthread.php?t=2540232
Sent from my Evita.