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] One S Radio Upgrade?

Hey guys,
I'm running a One S (S4) on Virtuous RC1 and suffering from the phantom home button pressing.
I've read that this should be resolved in later radio updates - I'm currently on 1.06es.50.02.31_10.09a.50.04L
The issue, I'm guessing, is that my HBoot has been upgraded when the phone was in for warranty repair to 1.14. Recovery is currently TWRP 2.3.0.0
Anyone know what the best way to upgrade the radio is, or if this will even resolve the phantom home button pressing (which makes the phone VERY annoying to use)
Thanks
Russell

I have also hboot 1.13 and need to know how to upgrade
Sent from my HTC One S using xda app-developers app

There are 2 possibilities atm, use an AOSP based Rom like CM, AOKP, etc.
or downgrade your HBoot,
BE WARNED, this will brick your device, there is also explained how to unbrick your device,
ONLY DO THIS, if you really know what you are doing,
neither I or the creater of the guide will be responsible if you can`t unbrick your device,
you will do this on YOUR OWN RISK!
In both cases, you can use the Radio Installers from this Thread to install a new Radio

Thanks fr the info, that looks like a whole lot of work!
Does anyone know if the phantom home button pressing is definitely resolved by a later radio?
Are there any other options to install the radio (install RUU for example?)
Just need to weigh up my options before taking the plunge

I've re-locked and installed RUU to get back to stock, updated using the OTA and got latest radio.
Not had the home button issue since... still early days but signs are good.
Thanks to all for your help.

RadugaUK said:
I've re-locked and installed RUU to get back to stock, updated using the OTA and got latest radio.
Not had the home button issue since... still early days but signs are good.
Thanks to all for your help.
Click to expand...
Click to collapse
did you have to flash stock recovery?

PulpzillA said:
did you have to flash stock recovery?
Click to expand...
Click to collapse
If you going to run a RUU then you only need to lock the bootloader but a safe way would to flash stock recovery then lock it.

I did flash the stock recovery - almost everything I read seemed to think this was the safest way to get back to stock.

[Q] No OS Installed - 3.18 Unlocked S=On

Followed the steps in Hassoon's toolkit, installed recovery, sideloaded CM, and now I have no OS. I can still access fastboot and recovery, see attached image for more info. Any more information needed, please let me know. This is pretty frustrating, no wonder I like Nexus devices.
(sorry for double posting, I also put this in Hassoon's thread, but felt it'd be more appropriate to post here)

first man... you'll only be able to use sense roms most likely, as the newer aosp roms dont mix with the upgraded touchscreen on the 3.18 firmware. so you can head to the original dev section to find the "downgrade touchscreen" thread to use aosp...
second, you have to fastboot flash the boot.img of every rom because the newer hboots dont allow it. easy solution to that is to go to original dev section and follow the s-off thread. if you can s-off you can say bye bye to fastboot for the most part

Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)

exad said:
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
Click to expand...
Click to collapse
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!

Dolfan058 said:
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Click to expand...
Click to collapse
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2

InflatedTitan said:
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...

Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.

Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
I feel bad, I see all these people having trouble getting s-off to work, and I did it today without any hassles at all.
Sent from my Evita using XDA Premium

exad said:
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Click to expand...
Click to collapse
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.

Dolfan058 said:
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Click to expand...
Click to collapse
if a simulated battery pull isnt working for you, you can paste your cmd prompt window in here and i can check if anything weird is going on.
usually it should work by the third try or so if not after the first simulated battery pull.

CleanROM 7 stuck at splash screen

Stuck...just displays the HTC logo on white screen.
I had cleanrom 5.0 final. TWRP, super SU, rooted, unlocked. Firmware 2.20.
I dropped in the new ROM, did a factory reset in TWRP, and installed new rom. I read that that would work with my current setup, but apparently not. I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
I flashed back to 5.0 with no issues, but I would really like to try to get the cleanrom 7 working if possible. Any ideas?

It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita

timmaaa said:
It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your reply. You are correct, I am s-on. But I was able to re-load CleanROM 5. This is my second custom rom on this phone (the first being CleanROM 5). But this is only my third custom rom ever, so I am pretty much of a noober. :cyclops:

klaypigeon said:
I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
Click to expand...
Click to collapse
The ROM threads are to inform you of the features and requirements of the ROM, not to be a step-by-step guide. There are plenty of step-by-step guides in various places, for those that care to read and look.
If you don't flash often, a good resource is my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
My Index will at least point you to the s-off process. I intend to add some info about the 2.15 firmware (as people keep constantly asking about it), but work has been chaotic, to say the least.
Another good thing to do, is read through the more recent pages of the ROM thread, or do a search on the thread.

Thanks, I am subscribed to your index, that's where I found the ROM and what I used during my first flash.
I did the process for unlocking the 2.20 firmware about a year ago as that is what my phone came with. I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
'CID Getter' says I have no CID, which I read means I have superCID.
Firmware : 2.20
SuperSU installed and functioning (I have root)
Current ROM: CleanROM 5 Final
S-ON
TWRP 2.3.1.0
So you think I need to do s-off as described here? http://forum.xda-developers.com/showthread.php?t=2155071
If I brick this phone I am using a clam-shell for a year until contract renewal :/

klaypigeon said:
I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
Click to expand...
Click to collapse
You shouldn't be assuming anything. You just said the CID Getter says S-on. You can also confirm s-on or s-off by going into bootloader.
The main reason CleanROM7 will not boot, is that you forgot to extract boot.img from the ROM file, and flash it separately using fastboot. Some older versions of CleanROM didn't require this (boot.img was flashed in the AROMA installer), so that may be why you don't remember doing this.
S-off removed the requirement to flash boot.img separately (will flash in recovery automatically when you flash the ROM). It will also allow you to install hboot 2.15 and associated firmware, if you happen to suffer from signal drops or random reboots while on Sense 5 ROMs.

Further to that, CID Getter doesn't show your actual CID. The proper way to display your CID is by using the fastboot command "fastboot oem readcid". Like Redpoint said, you shouldn't be assuming anything.
Sent from my Evita

Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.

What did you flash?
Sent from my Evita

Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.

timmaaa said:
Further to that, CID Getter doesn't show your actual CID.
Click to expand...
Click to collapse
Ha, that's not a very useful app, then. What is it actually reading?
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
klaypigeon said:
Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.
Click to expand...
Click to collapse
Do you mean "locked the bootloader" instead of "flashed"?
If you locked the bootloader, this is what is supposed to happen. Locking the bootloader assumes you will be running RUU, and renders the phone unable to boot normally.
I know you got it back up and running. But for future reference, this phone is almost never bricked, as long as the screen comes on.
---------- Post added at 09:26 AM ---------- Previous post was at 09:24 AM ----------
klaypigeon said:
Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.
Click to expand...
Click to collapse
Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.

I'm not sure what CID Getter is actually reading, but when I used it it came up with the incorrect CID, can't remember exactly what it was now but it was definitely incorrect because I already had SuperCID.
Sent from my Evita

Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.
Click to expand...
Click to collapse
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out

klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
If you have s-off you don't need to flash the boot.img via fastboot, that's only required if you're s-on. It might be worthwhile updating your TWRP to the 2.6 version though.
What Redpoint was saying is that you need to have a firm understanding of what you're doing when it comes to modifying your phone. If you only do it once a year that's cool, but that probably means that once a year you need to brush up before making any changes to your device. Rushing in without the required knowledge is how bricks occur. This is only being suggested to help you, for your own good.
Sent from my Evita

klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do.
Click to expand...
Click to collapse
Only with hboot 1.14 or later and s-on. If s-off the protection which prevents boot.img from being written in recovery is bypassed.
I believe TWRP 2.3.1 was a pretty trustworthy version (although older). So not sure why CleanROM didn't flash. Might not be a bad idea to update to 2.6.0 (although the latest 2.6.4 seems to have some bugs).
klaypigeon said:
I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
Yeah, I understand that you only do this on a seldom basis. And its a lot of esoteric knowledge to have to relearn (or take in, since things have likely changed since lasts time). However, that doesn't change the fact that not fully understanding all the concepts and steps can have dire consequences for your phone.

[Q] No OS installed HTC ONE X

I have the htc one x with Rogers, version 3.17.631.2... the RUU isn't available for this version.
***TAMPERED***
***UNLOCKED***
s-on
Currently I have no OS installed, I have been searching through forums on this website for about 6 hours last night with no solution. Can someone please help. Thanks
I also have the token ID saved on my computer.
What I tried was:
installing the stock rogers PJ83IMG.zip from here
but since my version is 3.17.631.2 it wouldn't let me downgrade to the 1.73.631.1 version
Any suggestions?

Why are you trying to ruu. In order to ruu downgrade you will need to be s-off.
Sent from my VENOMized HoxL

is there any way to be s-off with no OS installed?

1. How did you even delete the OS?
2. Do you have a custom recovery?
Sent from my HTC One XL using XDA Premium 4 mobile app

I was installing a custom rom, and erased the OS by accident in TRWP, and I can flash a custom recovery on my phone. What would i do after that though?

Also go to the cleanROM thread and use their boot.img to get things at least booting up
You don't need soff to flash img files via fastboot
Sent from my HTC One XL using XDA Premium 4 mobile app

alright im giving it a try atm!

Why not just flash a ROM? You already have a custom recovery on your phone, that's what TWRP is. Should you really be messing with your phone in the first place though? It doesn't seem like you have the faintest idea of what you're doing if you can't even recover from deleting your OS.
Sent from my Evita

I LOVE YOU GUYS!
its all fixed up

timmaaa said:
It doesn't seem like you have the faintest idea of what you're doing if you can't even recover from deleting your OS.
Click to expand...
Click to collapse
I tend to agree. There has also seems to be an increase of this occurrence in the last several months of "I wiped the OS accidentally and I don't know how to recover". Which is a bit troubling since the default wipe in TWRP is factory reset, Dalvik, and cache. The Wipe screen on TWRP explicitly states that this is all the is usually needed. If you wipe /system, you did so deliberately by going into the Advanced screen and picking it from there. Meaning the OP took extra steps to do something without knowing if it was necessary, and without knowing how to recover from it.
This also means the OP didn't create a nandroid backup in TWRP, which would have been a simple way to recover. This is basic, fundamental step that should be taken whenever modding a phone, but something n00bs seem to be "skipping" (or ignorant of) lately.
This type of behavior/mindset while modding does not bode well for the life of your phone.

actually the TWRP recovery i had on my phone was really outdated. i didnt have the advanced option. I simply had to pick from a list and i wiped it all without warning.
I've learned what i have done wrong, and thank you guys for it.
I currently have cleanROM flashed on my phone, but its really buggy.. it even turns off randomly and if i ever lose reception I will have to restart my phone to gain reception again. Not sure why this is happening? What do you guys suggest I do?

You need to search properly before posting. It's XDA rules. The reboots and signal loss problems have been discussed countless times in the Cleanrom thread. Read a few of the last pages and you're guaranteed to find the solution.
Sent from my Evita

ecakici said:
actually the TWRP recovery i had on my phone was really outdated. i didnt have the advanced option. I simply had to pick from a list and i wiped it all without warning.
Click to expand...
Click to collapse
That's a pretty lame excuse. My previous general notion still holds: You took deliberate steps to wipe the OS (/system) as that option is still not selected as default even on older versions of TWRP. And you were therefore wiping things willy-nilly without understanding what they were, whether they really needed to be wiped, or how to recover from them.
And you still should have made a nandroid (TWRP backup).
All in all, it implies a careless mindset while modding your phone (skipping steps and doing things without understanding).

I have searched the forum: [ROM][9/11] - CleanROM 7.0.P1 -★| Android 4.2.2! | Sense 5! | Lite! | Stable! |★-
and found that if i install hboot 2.15 on my phone it should stop rebooting and the reception would go back to normal right?
is there anything else I have to do.
please, if it isn't too much trouble link me to a guide that fixes these issue for the HTC One X (Rogers)
or just give me a few steps of how to fix these issue.
Thank you so much!
PS my battery life improved so much, i usually charged my phone twice a day, and I haven't charged my phone at since 7am today.

Yes. Flash the 2.15 firmware. It's in the first post of Turge's stock Sense 5 ROM thread in the development section.
Sent from my Evita

Step 1: SuperCID 11111111
Step 2: S-Off using beaups guide
Step 3: Flash the 2.15 firmware
Can someone link me to the best guide to follow for step 1?

You can do it two ways, here's the first:
Step 1: SuperCID with hex edit method.
Step 2: S-off with Facepalm S-off.
Step 3: Flash firmware.
Or the other way:
Step 1: S-off with Rumrunner S-off.
Step 2: SuperCID with fastboot command:
Code:
fastboot oem writecid 11111111
Step 3: Flash firmware.
I believe the second method is easier. The Rumrunner s-off process seems much easier, it doesn't require you to have SuperCID first to work. Once s-off is achieved you can easily change your CID by fastboot command as opposed to messing around with hex editing.
Sent from my Evita

thanks a lot guys!
i learned a lot through this forum!

HTC One X plus OS has been deleted accidentaly
ecakici said:
I LOVE YOU GUYS!
its all fixed up
Click to expand...
Click to collapse
Can u plz tell me how did u u fixed it

reachsoumendra said:
Can u plz tell me how did u u fixed it
Click to expand...
Click to collapse
What is your exact problem?
Sent from my Evita.