Along time ago I tried out a lot of aosp Roms. I tried cm10.1 and others like that. I have hboot 1.14 and I have s-on. And I'm always having Wi-Fi issues with aosp Roms. OK so about a month ago I was using viper ROM. Wifi was working correctly. It was on 4.1.1. I recently went to united basic ROM. Which is basically the jelly bean update. My kernel is 3.4.1 and I want to use illusion. But I keep hearing things about being on the latest HTC one s jelly bean ROM. (Which I'm not because I keep getting a message saying there is a new update) and I did not do the ota update I just flashed a ROM that gave me it. Please someone help I really am kind of stuck.
Illusion is using the 3.4 kernel. The "problem" with this kernel is that it needs the latest hboot (2.15?) & firmware. There are a few ways to get it, but one of the "easyest" ways is to simply go back to stock HTC RUU & update it. Right after that, you can simply flash illusion like any other rom. If your rom allready updated firmware & hboot, you should be good to go. Shouldn't be on hboot 1.14 anymore tough.
Related
I am very much interested in ICS ROM, but one basic question:
If the Radio is not good for my region,esp. the voice clarity thing, and I wish to revert back to the GB ROM with the current RADIO which is on my sensation....would the Nandroid thing work on it???? Or anyway to download the radio which is currently there in my sensation...if yes, How do i find out the Radio for my sensation??
Someone please guide me...
I was flashing ICS ROM yestarday, but things didn't go right. Restored NAND and everything is working, and i still have back my old radio.
I have seen a few reports of going back to a GB ROM over in the InsertCoin thread, so it would seem like reverting back would be an option. It would also depend on whether or not you did the full process of upgrading to an ICS ROM including updating the firmware, because I believe 4.0.1 can be run on the original firmware but 4.0.3 you must update it. According to what I have seen regarding InsertCoin anyways.
Also, I want to say that you can find your radio information if you boot into hboot. (Take battery out, hold VOL down and power). Not 100% sure though, I usually just use it to hop into recovery.
Hope I helped
I flip flopped a couple times now, just make sure u reflash gb firmware if u upgraded for ics, and always use the radio reccomended with the rom. I've had no issues.
Here's my last 4 roms, in case anyone cares.
Cm7->tripnice->cm7->virtuous Inquisition
hockeystar711 said:
I have seen a few reports of going back to a GB ROM over in the InsertCoin thread, so it would seem like reverting back would be an option. It would also depend on whether or not you did the full process of upgrading to an ICS ROM including updating the firmware, because I believe 4.0.1 can be run on the original firmware but 4.0.3 you must update it. According to what I have seen regarding InsertCoin anyways.
Also, I want to say that you can find your radio information if you boot into hboot. (Take battery out, hold VOL down and power). Not 100% sure though, I usually just use it to hop into recovery.
Hope I helped
Click to expand...
Click to collapse
I am currently running android revolution 5.0.2 without updating my radio or firmware and it is running very well. If I want arhd 6.0.2 then I would need to install new firmware. So far I am keeping my option to return to gingerbread without any hassle.
Flashing a rom or backup doesnt change your radio. You have to go through your bootloader for that. I havent heard any bad news about going back to GB as long as older 10.xx radios are flashed as well. And people have actually gone back succesfully while keeping newer firmware and hboot. And by people i mean me lol. I have a insertcoin GB 3.4.5 backup on tap i use regularly cuz we all know ICS is still learning how to walk on our sensations
madigan311 said:
Flashing a rom or backup doesnt change your radio. You have to go through your bootloader for that. I havent heard any bad news about going back to GB as long as older 10.xx radios are flashed as well. And people have actually gone back succesfully while keeping newer firmware and hboot. And by people i mean me lol. I have a insertcoin GB 3.4.5 backup on tap i use regularly cuz we all know ICS is still learning how to walk on our sensations
Click to expand...
Click to collapse
Did you flash the radio separately? I am having the problem now as I did a NAND restore to GB, but the radio is still 11.xx...I think the battery is draining more with it. So I want to revert the radio back...but how did you do that? Just flash the radio? I flashed the recent firmware from December in HBOOT and even though it says the custom radio was flashed, the radio still says 11.xx
please let me know
newr said:
Did you flash the radio separately? I am having the problem now as I did a NAND restore to GB, but the radio is still 11.xx...I think the battery is draining more with it. So I want to revert the radio back...but how did you do that? Just flash the radio? I flashed the recent firmware from December in HBOOT and even though it says the custom radio was flashed, the radio still says 11.xx
please let me know
Click to expand...
Click to collapse
You can flash a radio through hboot screen just like you did with ICS firmware. Im not sure but i dont think the firmware zip from the dec tmo ota had radio included as all radios are rolled up in a thread in the dev section. Theres a radio flashing guide somwhere too
madigan311 said:
You can flash a radio through hboot screen just like you did with ICS firmware. Im not sure but i dont think the firmware zip from the dec tmo ota had radio included as all radios are rolled up in a thread in the dev section. Theres a radio flashing guide somwhere too
Click to expand...
Click to collapse
Thanks..I just flashed the radio and it worked. BTW, which GB ROM is good and stable? I am considering trying it out while wait for ICS to finalized. You mentioned the insert coin?
newr said:
Thanks..I just flashed the radio and it worked. BTW, which GB ROM is good and stable? I am considering trying it out while wait for ICS to finalized. You mentioned the insert coin?
Click to expand...
Click to collapse
you could try this one
by far it's the rom which i consider stable and have a good design.
madigan311 said:
Flashing a rom or backup doesnt change your radio. You have to go through your bootloader for that. I havent heard any bad news about going back to GB as long as older 10.xx radios are flashed as well. And people have actually gone back succesfully while keeping newer firmware and hboot. And by people i mean me lol. I have a insertcoin GB 3.4.5 backup on tap i use regularly cuz we all know ICS is still learning how to walk on our sensations
Click to expand...
Click to collapse
Just wondering if you had problems with the Lock Screen display with the 3.4.5 insertcoin? I tried it, and somehow the lock screen won't display the icons..even when it's turned on from the settings
newr said:
Just wondering if you had problems with the Lock Screen display with the 3.4.5 insertcoin? I tried it, and somehow the lock screen won't display the icons..even when it's turned on from the settings
Click to expand...
Click to collapse
Nope, never saw this problem... Tried reflashing????
Sent from my HTC Sensation Z710e using xda premium
Would like to know who has the firmware to go back go GB? Because the nand backup isn't working.....
Never mind - found it right here: http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22
Hi,
I've recently had to replace my phone with another SENSATION 4G (bought second-hand, but new). I was originally running an older version of ARHD Gingerbread on my old SENSATION 4G and it was working great. The new phone came with a stock GB, so I decided to go ahead and initiate the ICS OTA update for my phone, but somehow in the middle, it failed. So what happened is that I corrupted my stock ROM and at the same time never had a chance to make a Nandroid backup. I then downloaded ARHD 6.7 ICS and sucessfully installed the custom ROM (followed all procedures to make sure my firmware and radio is updated), BUT everytime I rebooted into first boot, the screen would freeze at the Beats Audio logo (even tried leaving it on for 30min). I then tried different Sense-based ROMs (Elegancia, Dark Forest, original ICS RRU etc) but every time, it would hang at the boot screen. I thought my phone was bricked, but to my surprise, I was able to install smaller AOSP & AOKP based ROMs, like CM9 and Touchcream 2.1, and successfully boot and use them. I really want to be able to use Revolution HD roms to take advantage of my wifi calling, but now just cannot. I'm not totally new to this, as I've just upgraded my sister's Sensation 4G with ARHD 6.7 w/o any problems. I still don't understand why this is happening to my particular phone. Please let me know if you may have a hint of what the problem could be (could the failed OTA ICS update the root of my problem?). Thanks all.
flash a ICS RUU and see
here is the TMOUS ics ruu click me
Done a bit of research now and all the keywords I have searched through haven't returned any results of this particular issue.
I have flashed CM10 (Stable) to the XL, has installed and boots fine, however there is 0 feedback from the touchscreen so i can't use it at all.
I couldn't really find anyone else with a similar issue. Has anyone run into this, or know what may be causing it?
Have downloaded numerous times, different versions of twrp, everything's been cleared out/wiped (both before and after flash).
I'll add that I have not had this issue at all elsewhere, EXCEPT where yesterday I updated stock to the latest version to give it a go (was hoping for more of a JB experience...). In this case there is / was a bug with TWRP where if you installed Android 4.1 (Latest stock), the touch would no longer work in TWRP. Luckily the TWRP dev updated to 2.3.3.1 today, fixing the touch again (which some themes such as viper require). But I have no idea if any of this is related, shouldn't be though,given the rom should work standalone...
Any ideas would be great. I battled to overcome that damn TWRP mess (seen above) that I got myself into, then I got past a boot issue and now that I'm booted the damn touch doesn't work lol.
Hope to hear some good news,
regards.
Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source.
-known issue, but only yesterday I told h8rift and Rohan who previously were unaware of the issue.
-The change is in firmware delivered with 3.17
-Requires kernel update to resolve issue.
-Twrp easy to fix.
-Cm and others not so easy and may require waitng for source from HTC.
twistedddx said:
Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source.
-known issue, but only yesterday I told h8rift and Rohan who previously were unaware of the issue.
-The change is in firmware delivered with 3.17
-Requires kernel update to resolve issue.
-Twrp easy to fix.
-Cm and others not so easy and may require waitng for source from HTC.
Click to expand...
Click to collapse
Thanks for your reply. I just tried installing JellyBam now and alas the same issue, checking here confirms things
Can you recommend a Kernel that will work for the mean time? I was actually looking at some of the kernels, but didn't really go anywhere with it.
You can only use roms and kernels made from 3.17 for the time being.
twistedddx said:
You can only use roms and kernels made from 3.17 for the time being.
Click to expand...
Click to collapse
This sucks. I can't find a single rom/kernel that is compatible with whatever this 3.17 'thing' is (what's this the version of?). Can i roll back this version?
I can't even use the RUU to go back to stock because now the phone has blank version numbers and details and errors out.
My restores also don't work. Only JB roms actually boot now and all of them don't have any touch screen support. I AM able to get touch support if i install the ElementX JB kernel, however that then throws infinite "nfc and android.phone process-stop" messages (just after applications are being upgraded w/ the first boot of a JB rom).
Just looking to make the phone work
Playing around with Joker and have got the phone back into a working state. *phew*
xlmama said:
I can't find a single rom/kernel that is compatible with whatever this 3.17 'thing' is (what's this the version of?). Can i roll back this version?
I can't even use the RUU to go back to stock because now the phone has blank version numbers and details and errors out.
Click to expand...
Click to collapse
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
twistedddx said:
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
Click to expand...
Click to collapse
Thanks for your help. I'm now not clueless about my phones fate. :victory:
I have the same issue - updated to Andriod 3.17 about a week ago, and decided to flash CM10 afterwards. As a result, I am stuck with no touchscreen functionality.
Have there been any updates the past few days in terms of ROM's being released that will work on 3.17? How far into the future are we talking about before a release of CM10 will become available?
Is there no way to revert back to ICS and thus have a fully functioning version of CM10?
Is there any news on this issue ?
It's not possible until HTC releases kernel source. There's nothing the devs can do. You can only run sense roms
Sent from my VENOMized HoxL
twistedddx said:
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
Click to expand...
Click to collapse
Not mine, tried it twice. The only ROM I've been able to get running is PA 2.54, and the only way I could get the touchscreen to work is by flashing the Kernal from Hatkas ROM. Even that fc'd NFC to the point repeatedly So I'm thinking if I can find [or get help finding] a 3.17.661 kernal that will work with PA, I'll be golden.
I think I may be having the same problem, though I don't remember ever upgrading to 3.17. Is what you all are seeing like the screen doesn't even turn on? It just stays black, but the power button and volume button seem to be responsive? I can't even seem to get into recovery or bootloader, and this all started when I flashed the latest CM10 nightly.
Never mind.
Magickalhack said:
Not mine, tried it twice. The only ROM I've been able to get running is PA 2.54, and the only way I could get the touchscreen to work is by flashing the Kernal from Hatkas ROM. Even that fc'd NFC to the point repeatedly So I'm thinking if I can find [or get help finding] a 3.17.661 kernal that will work with PA, I'll be golden.
Click to expand...
Click to collapse
You do realized you flashed a sense kernel for an aosp Rom?... And you're wondering why it gave you FC's?
I'm on hboot 1.09, did not do OTA update, and the touchscreen works on CM 10.1 90% of the time, but sometimes I open it up and it doesn't respond. Hitting the sleep button twice fixes it but it's annoying. Would the above fix do anything for me? What else could be the problem?
slash178 said:
I'm on hboot 1.09, did not do OTA update, and the touchscreen works on CM 10.1 90% of the time, but sometimes I open it up and it doesn't respond. Hitting the sleep button twice fixes it but it's annoying. Would the above fix do anything for me? What else could be the problem?
Click to expand...
Click to collapse
Do you use s2w? That causes that issue
Sent from my VENOMized HoxL
I think i'm getting overwhelmed with all the reading I'm doing and need a little help clear out the confusion in my brain
I'm rooted
I have SUPER CID
I have S-OFF
Custom Recovery (TWRP)
On a custom ROM (chameleon OS)
Never updated to JB OTA
Does my phone need to update to JB before I begin to flash any other Custom ROM? I know these roms provide Android 4.1/4.2+ but does my phone need the OFFICIAL JB update for it to work good? I see a lot of people installing the stock RUU and getting the update - I guess my main question is - is it necessary to downgrade back to stock, update, re-root,unlock, install new ROM again with my phone now having JB thru OTA?
If so - what are the PROS of doing this?
If not - is my phone going to be okay installing ROMs with my phone never being updated.
Thanks!
Short answer: no.
Long answer: no, because you're wiping cache and data the phone is a blank slate. You could go back to Cupcake or skip forward to Jelly Bean 4.3... If you managed to break into Google Inc and get the data for that.
Sent from my HTC One S using xda premium
Normaly no.
But I've seen situations with previous devices that a certain min hboot/firmware is required.
Like if your firmware is gb any jb/ics Rom might not work. just an example!!
Just look what base the Rom is made from. Test if it works. If not update you're firmware to min required or same as base of rom. Test it again.
Always check op of rom. Or ask the dev.
Verstuurd van mijn HTC One S met Tapatalk
since you're s off, any ROM will work.
Real187, on some other HTC devices (eg.Flyer), you had to match your hboot to the ROM, but so far for the One S, this hasn't mattered (for the average user).
The only "firmware" partitions you might consider messing with is the radio, but that won't affect if the ROM boots.
to answer your question, the pros of ota are none to negligible. No ones sure if the other partitions it updates are beneficial.
Thx for the replies! I was worried about this as I see a lot of people trying to downgrade and bricking their phones while doing the process.
So...
I have been flashing custom ROMs since the One S came out, but right now I am having a hell of a time figuring out if I am way out of date or if I am doing just fine.
All this OTA stuff and HBoot updates...
Basically, I have Hboot 1.06
I have the 1.08ts baseband
Running ChameleonOS ROM Android 4.2.2
So... There is all this talk of going back to stock, getting OTA, updating Hboot (which some seem to not want to do)
What am I actually missing if everything seems to work okay and I have 4.2.2?
Am I missing out on better reception or something? And how so? I can update my radio to 1.13 it seems by using the CM radio installer.
Am I just over thinking things? Or is something way out of date that I should update?
mantiis said:
So...
I have been flashing custom ROMs since the One S came out, but right now I am having a hell of a time figuring out if I am way out of date or if I am doing just fine.
All this OTA stuff and HBoot updates...
Basically, I have Hboot 1.06
I have the 1.08ts baseband
Running ChameleonOS ROM Android 4.2.2
So... There is all this talk of going back to stock, getting OTA, updating Hboot (which some seem to not want to do)
What am I actually missing if everything seems to work okay and I have 4.2.2?
Am I missing out on better reception or something? And how so? I can update my radio to 1.13 it seems by using the CM radio installer.
Am I just over thinking things? Or is something way out of date that I should update?
Click to expand...
Click to collapse
No reason to update hboot.
If you don't experience any related issues, you don't need to update the radio either. Although I had a better experience with the JB radio (at least the 1.15 release) than with the ICS 1.06es. It has now stopped the continuous switching between 3g and hsdpa.
Some people want to go back to stock because they prefer the HTC Sense experience, and I agree with them. But if you are fine with your rom, there's really no need to worry about anything.