Related
This is doing my head in to the point I have borrowed a new HTC Sensation only to find the problem exists on this phone also.
When using the Camera App If I hit the power button the screen turns off. I am then unable to switch the screen back on - It appears the phone crashes.
Behaviour some times differs depending whether I have taken a photo or not.
The following behaviour is observed:
The lights stay illuminate on the soft keys at the bottom of the screen.
The phone can receive calls how ever it doesn't ring and I unable to answer them.
This problem is confirmed on 2 seperate devices which have been flashed with:
Android Revolution HD 3.6.12
10.58.9035.00U_10.15.9035.02_2 radio
I have also run super wipe on the phone before installing the HD Rom.
Please help!?
Ive also had this problem on a few diffrent roms.
But i flashed amaze camara update, and not had any prob since.
Im now running the latest ICS with sense, with what ever camara software came with the rom. And not had any problem
big_sw2000 said:
Ive also had this problem on a few diffrent roms.
But i flashed amaze camara update, and not had any prob since.
Im now running the latest ICS with sense, with what ever camara software came with the rom. And not had any problem
Click to expand...
Click to collapse
Cheers moved to ICS and its now fixed.
edwardblum said:
Cheers moved to ICS and its now fixed.
Click to expand...
Click to collapse
Having the same issues on both mine and my wives phones, both running AR 3.6.11 along with lag and other issues! Pretty fed up - and considering a different ROM. How is the ICS ROM, any issues like the 3.6.11? Is it hard to install?
I would try Elegancia ICS. Maybe a little pain to install, if you need to update your firmware.
http://forum.xda-developers.com/showthread.php?t=1429953
Firmware
http://forum.xda-developers.com/showthread.php?t=1432220
You may have to superCID if the firware dont work. Also easy todo
See post 4
http://forum.xda-developers.com/showthread.php?t=1192300
Have a read of the last 10 pages or so of the ICS thread for superCID info if your stuck, but it is easy.
I will give it a try! Do you just download the zip firmware and flash it?
It's not a rom problem, it is faux's kernel problem.
You can flash bricked kernel to solve.
banasik72 said:
I will give it a try! Do you just download the zip firmware and flash it?
Click to expand...
Click to collapse
Put the img zip directly on the SD card, not in any folder.
Boot the phone in to bootloader Power on volume down same time.
Just follow the instructions.
DO NOT POWER OFF REMOVE BATTERY ETC.
You will have to remove file from memory card before rebooting.
If you fail with the upload, then you will have to superCID
My phone details:
HTC Sensation Z710e
S-OFF by Relovutionary, Rooted, SuperCID
Firmware 3.24.401.1
Hboot 1.27.1100
RIL HTC-RIL 4.0.0012HMQ
Radio 11.68.3504.00U_11.21.3504.13_2
4EXT Recovery
after Booting touchscreen wount work
After flashing Leedroid SuperSensational ICS 6.0.0 i have problems with touchscreen, it stoped to work - i cant use touchscreen at all. After booting comes sim pin and thats it, i cant touch the screen... only voice and power button is working.
touchscreen working in 4ext recovery
I can use ADB and go to 4ext Recovery and there touchscreen is working.
wiping, flashing several roms and firmwares
I've been cleaning, wiping, superwiping and flashing over and over, but so far it was useless.. whatever ics rom i use touchscreen wount work, but in 4ext recovery touchscreen is working very well!
any guide to right direction would be nice
still nothing
ive been checking md5sum's - they all ok
so far ive been testing..
Sense 3.6 roms
LeeDr0id SuperSensational 6.0.0
Andoid Revolution HD 6.2.1 with 1.2ghz
ExtremeSensation blaze2 & 1.0.1
and nonSense rom
HyperNonSense
noone of them cant activate my touchscreen, only in 4ext recovery is my touchscreen working
i will try now 3.12 firmware and some sense 3.5 roms
before i started to try 3.12 firmware i checked kernel..
uname -r shows 2.6.35.14-Sensation-faux123-v0.2.0+
and it wount change!! ..and i think this is the problem!
i tried install stock_kernel_3.0.16-g9788208 in recovery and also manually with fastboot and no luck so far..
can anyone help me with this?
kernel isnt issue
kernel isnt issue.. i wiped and superwiped etc and fresh installed leedroid 6.0.0 and now i have stock kernel 3.0.16..
and touchscreen not working if i boot the rom
in 4ext recovery touchscreen just great and working really well
zorroh said:
kernel isnt issue.. i wiped and superwiped etc and fresh installed leedroid 6.0.0 and now i have stock kernel 3.0.16..
and touchscreen not working if i boot the rom
in 4ext recovery touchscreen just great and working really well
Click to expand...
Click to collapse
im not good with hardware stuff but try the following things:
firmware 3.24/3.25 and install ARHD 6.2.1 doesnt work?
firmware 1.17/3.12 and install ARHD 4.1.13 doesnt work?
it is a hardware fault and you need to make it s-on and factory reset and bring it to htc and ask for a replacment
firmware: http://forum.xda-developers.com/showthread.php?t=1459767
s-on (end of the post): http://forum.xda-developers.com/showthread.php?t=1192300
s-on when did faulty (so you dont have to search): http://forum.xda-developers.com/showthread.php?p=21922297#post21922297
Thank You!
ARHD 4.1.13 with 3.12 firmware and radio 10.58.9035.00U_10.15.9035.02_2
now everything is working
problem htc sensation
hello to everybody i got one htc sensation ,i just intall some ruu and rom .since then i got issues whit the phone ,it dosent work anymore ,some times they do sometimes dont .please can you help me not have those isues anymore ?thank you
zorroh said:
Thank You!
ARHD 4.1.13 with 3.12 firmware and radio 10.58.9035.00U_10.15.9035.02_2
now everything is working
Click to expand...
Click to collapse
so i can use only gingerbread roms with firmware 3.12 or lower...
i tested with 3.12 firmware some older ICS like InsertCoin 4.3.2, but no luck, i tried multiple kernels also.. clocked and stock kernels.. i tried before many 3.24 fw and 3.24 fw based roms.
i cant use ICS roms touchscreen wount work with ICS roms
when i flash back to gingerbread everything is just ok, can use even clocked kernel with no issues
dangaita2005 said:
hello to everybody i got one htc sensation ,i just intall some ruu and rom .since then i got issues whit the phone ,it dosent work anymore ,some times they do sometimes dont .please can you help me not have those isues anymore ?thank you
Click to expand...
Click to collapse
i dont understund what is your problem, is it with touchscreen like i had?
actually my touchscreen working very well, just touchscreen wount work with ICS roms.
so if you have same problems, then easy solution is to use 3.12 fw and some gingerbread rom.
im looking forward to have ICS rom working, so far no luck
i had the same problem as you. Check my posts in ARHD thread:
http://forum.xda-developers.com/showpost.php?p=22463110&postcount=52396
5 days later ...
http://forum.xda-developers.com/showpost.php?p=22642326&postcount=52872
i'm still wondering what could it be ...
joaquinf said:
i had the same problem as you. Check my posts in ARHD thread:
http://forum.xda-developers.com/showpost.php?p=22463110&postcount=52396
5 days later ...
http://forum.xda-developers.com/showpost.php?p=22642326&postcount=52872
i'm still wondering what could it be ...
Click to expand...
Click to collapse
You should let him know that eventually in GB it won't work anymore either. I wonder what is causing the TSD to burn out, or not work.
UnixSlayer said:
You should let him know that eventually in GB it won't work anymore either. I wonder what is causing the TSD to burn out, or not work.
Click to expand...
Click to collapse
Yes, my touchscreen digitizer has died completely. It wasn't responding even in gingerbread a couple of days after having the ICS issue.
Zorroh let us know what happens with yours.
Good luck
starting to test 3.30
right now im in 2.3.5 ARHD 4.1.1.3 and all things are ok so far.
but i just downloaded all what i need for 3.30 based ICS so i will test it now.. lets see whats happens
*EDIT*
..and back in GB 2.3.5 ARHD 4.1.1.3. Firmware 3.30 based ICS wount work.
zorroh said:
right now im in 2.3.5 ARHD 4.1.1.3 and all things are ok so far.
but i just downloaded all what i need for 3.30 based ICS so i will test it now.. lets see whats happens
*EDIT*
..and back in GB 2.3.5 ARHD 4.1.1.3. Firmware 3.30 based ICS wount work.
Click to expand...
Click to collapse
This is definitely one of the weirdest things ever ... new fw, new drivers and still not working. How come is that related to the OS?
Hi Guys,
I had the same issues with the tochscreen not responding. I tryed different firmwares and roms but the tochscreen did not work at all.
Now I'am back on Gingerbread and Hboot 1.17 everything works again.
Strange, hope the Problem would be fixed. but i don't think so. Nobody elese seems to have that problem.
Anyway thanks for your support.
Another dude with the same problem ...
http://forum.xda-developers.com/showthread.php?t=1531657
This is getting popular
i will try now latest 3.32 firmware and ARHD.. hope that helps...
LATER...
..and still no luck.. so i will put old firmware and ginger back..
So any info about, how to resolve this problem would be awesome! my phone just dont like ICS rom..GB roms are ok
i have the same problem, but my problems got bigger.
i never did something to my sensation xe before.
I received from HTC OTA ICS. So i installed it. After it was done, i can move my lockring, but when i release it, my phone hangs. Same problem with simcard insert. I can touch a number and then the phone hangs.
After this i got some help and i unlocked my phone with htc dev unlock. Installed 4ext. With 4 ext my touchscreen works as a charme.
Installed ARHD 6... and rebooted. Same problem, can touch 1 time and then phone hangs.
My biggest problem now is that i have HBoot 1.27. I need to downgrade Hboot to install gingerbread again, witch worked fine before.
Can anyone help me with this?? Is it already possible to s-off and go back to Hboot 1.17??
Where can i download: ARHD 4.1.1.3??
Problem Solved
i got the ICS on my phone today! and touchscreen working!
i tried several roms with right firmwares etc but nothing and now i finally tried stock recovery:
http://vi8.info/HTC-Sensation/Stock-Recovery/
i used this rom package: PG58IMG.zip Full hTC Stock RUU 3.33.401.6 (All-in-1-ZIP-ICS) , i placed it into sd card and rebooted to bootloader, there you need to flash it like firmware and it updates everything.
so, now i have ICS and now probally i need to root it again.
problem solved!
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
Is anyone familiar with whether or not one can flash a new radio on the HBOOT 2.15.000? I believe the one it comes with is giving me trouble on the T-Mobile network (data drops randomly). I've tried CM10.1 with the 3.4 Kernel, Illusion Rom and PACMAN rom and none of which seem to get a stable connection with the radio-1.13.50.05.31_10.50.08L. Additionally, I can't edit the build.prop file as it's COMPLETELY different than the previous ones. Suggestions?
I've attempted to flash http://forum.xda-developers.com/showthread.php?t=2255906&highlight=radio the radio found there via fastboot and received an error:
C:\Users\TE\Downloads\BehradGH_HBoot_2.15.0000_TWRP_Recovery (1)\fastboot>fastb
ot flash zip radio.zip
sending 'zip' (19455 KB)...
OKAY [ 2.160s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.194s
I then attempted to flash via recovery and it goes through successfully however, nothing changes, it's still the same radio once I reboot. I've even tried the AROMA Installer for ALL HBoot and that doesn't work either. I've tried install higher radios and lower radios and none hold true once the phone boots. Should I try a different ROM? If so which do "you" suggest? Am I missing something prior to installation that I'm doing wrong?
just2great said:
Is anyone familiar with whether or not one can flash a new radio on the HBOOT 2.15.000? I believe the one it comes with is giving me trouble on the T-Mobile network (data drops randomly). I've tried CM10.1 with the 3.4 Kernel, Illusion Rom and PACMAN rom and none of which seem to get a stable connection with the radio-1.13.50.05.31_10.50.08L. Additionally, I can't edit the build.prop file as it's COMPLETELY different than the previous ones. Suggestions?
I've attempted to flash http://forum.xda-developers.com/showthread.php?t=2255906&highlight=radio the radio found there via fastboot and received an error:
C:\Users\TE\Downloads\BehradGH_HBoot_2.15.0000_TWRP_Recovery (1)\fastboot>fastb
ot flash zip radio.zip
sending 'zip' (19455 KB)...
OKAY [ 2.160s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.194s
I then attempted to flash via recovery and it goes through successfully however, nothing changes, it's still the same radio once I reboot. I've even tried the AROMA Installer for ALL HBoot and that doesn't work either. I've tried install higher radios and lower radios and none hold true once the phone boots. Should I try a different ROM? If so which do "you" suggest? Am I missing something prior to installation that I'm doing wrong?
Click to expand...
Click to collapse
we dont have a enginering hboot so forget it using fastboot.
use the temp or sense installers in the dev section.
As I said, I tried the AROMA installer from that post (which is the temp installer you are referring to) via recovery and it still didn't work.
I'll try a sense installer and a sense rom later. Thank you.
just2great said:
As I said, I tried the AROMA installer from that post (which is the temp installer you are referring to) via recovery and it still didn't work.
I'll try a sense installer and a sense rom later. Thank you.
Click to expand...
Click to collapse
It will only change the radio version shown under settings-about phone. It will not change it on the bootloader screen. Only the sense installer will do that, but you must have soff. The temp install will also work for sense in the same way.
The signal issue is also a known problem for the new 3.4 kernel aosp roms
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
ryanshew said:
It will only change the radio version shown under settings-about phone. It will not change it on the bootloader screen. Only the sense installer will do that, but you must have soff. The temp install will also work for sense in the same way.
The signal issue is also a known problem for the new 3.4 kernel aosp roms
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
Click to expand...
Click to collapse
It doesn't even change it in about phone section.
So, what you're saying is that if I change the kernel I could potentially solve the erratic behavior of the radio?
I'm not sure if you were linking DarkSense hinting that I should try that or if it's just your signature but I'll get it anyways. Thank you. I'll try your suggestions after work.
I had the same problem, couldn't flash radio, i flashed 3.16.401 through cwm and then flashed ruu 3.16.401 which changed the radio, couldn't flash ruu before because i had higher version than 3.16.401 orange uk branded and had problem with signal once a day i got emergency call only, now i'm with 3.16.401 and no problems whatsoever, stock runs nice on one s till cm gets stable
I struggled with the radio flashing for 2 days having bootloader unlocked and s-off, ****ty branded network
Sent from my HTC One S using Tapatalk 4 Beta
Sisqo said:
I had the same problem, couldn't flash radio, i flashed 3.16.401 through cwm and then flashed ruu 3.16.401 which changed the radio, couldn't flash ruu before because i had higher version than 3.16.401 orange uk branded and had problem with signal once a day i got emergency call only, now i'm with 3.16.401 and no problems whatsoever, stock runs nice on one s till cm gets stable
I struggled with the radio flashing for 2 days having bootloader unlocked and s-off, ****ty branded network
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
3.16.401 refers to what?
just2great said:
It doesn't even change it in about phone section.
So, what you're saying is that if I change the kernel I could potentially solve the erratic behavior of the radio?
I'm not sure if you were linking DarkSense hinting that I should try that or if it's just your signature but I'll get it anyways. Thank you. I'll try your suggestions after work.
Click to expand...
Click to collapse
It's my sig. I do the theme work on plus tweaks and other stuff.
You can't just change the kernel on a room that uses a 3.4 kernel, you would either need to switch to a sense room or an older asop style ROM.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
Bad Combo?
---Bump---
Hello all on my first post.
Background:
Long story short,screwed up my phone a little while back, recovered with: RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed
Everything peachy after that, then a couple of days after I got a hold of:
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB
Then the problems started, every ROM I tried, the connection dropped and had to restart the phone. Tried to Facepalm, Moonshine, Super CID 11111111, nothing. Spent hours reading and thinking how I could get around this, I can't S-Off, so I can't change the radio and use a regular ROM like CM or BlackBean, not that I'm not grateful, just Sense is not really my thing. Tried BlackBean 9 with kernel 3.4 and didn't worked.
Any ROM that is not Sense based would not keep the signal for internet, unless rebooted.
So my question is: once you have HBOOT 2.15.0000 and Radio 1.13.50.05.31 you are screwed, did anyone in the same situation got S-Off or got it to work some how?
I did make a mission to check the forums for the methods I mentioned for the past 3 months, weekly if not daily.
The phone had originally:
HBOOT-1.14.0005
RADIO-1.11t.50.02.22
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41
But couldn't find the RUU with that radio, so used the one with 1.08ts.
Thanks in advance.
sns00 said:
---Bump---
Hello all on my first post.
Background:
Long story short,screwed up my phone a little while back, recovered with: RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed
Everything peachy after that, then a couple of days after I got a hold of:
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB
Then the problems started, every ROM I tried, the connection dropped and had to restart the phone. Tried to Facepalm, Moonshine, Super CID 11111111, nothing. Spent hours reading and thinking how I could get around this, I can't S-Off, so I can't change the radio and use a regular ROM like CM or BlackBean, not that I'm not grateful, just Sense is not really my thing. Tried BlackBean 9 with kernel 3.4 and didn't worked.
Any ROM that is not Sense based would not keep the signal for internet, unless rebooted.
So my question is: once you have HBOOT 2.15.0000 and Radio 1.13.50.05.31 you are screwed, did anyone in the same situation got S-Off or got it to work some how?
I did make a mission to check the forums for the methods I mentioned for the past 3 months, weekly if not daily.
The phone had originally:
HBOOT-1.14.0005
RADIO-1.11t.50.02.22
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41
But couldn't find the RUU with that radio, so used the one with 1.08ts.
Thanks in advance.
Click to expand...
Click to collapse
Did the connection drop on Stock Sense also?
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
Did the connection drop on Stock Sense also?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Nope. Tried Unknown, DarkSense, TrickDroid and SourcE connection is all good. AOSP [regular] ROMs need to reboot the phone, reload APN settings or get in and out of Airport mode, then it works for a while then drops the signal.
I forgot if incoming or outgoing calls work or not on regular ROMs.
sns00 said:
Nope. Tried Unknown, DarkSense, TrickDroid and SourcE connection is all good. AOSP [regular] ROMs need to reboot the phone, reload APN settings or get in and out of Airport mode, then it works for a while then drops the signal.
I forgot if incoming or outgoing calls work or not on regular ROMs.
Click to expand...
Click to collapse
Try the 4.2 ROMs. Data drops have been removed.
Sent from my HTC One S using Tapatalk 4 Beta
Installed ville_PAC_JB_4.2.2-v23.0.0_20130716-224253 last night, in the morning, tried to see a few pages, same shtick, no data connection. But remembered to test the phone and it connected to voice mail.
Hmmm.
Tried Odyssey 2.50 for about 10 hours, no problems. But didn't installed my usual apps, just kept checking on the data to see if it dropped, all good. Then got a hold of Odyssey 2.70 actually put all my apps in, configure the interface and such, nothing fancy.
Then I tried to use the data, nothing, but not even tried to load the pages, I found it strange, because before it was usually after a few hours that the data started to act up with the other ROMs I tried. Then it occurred to me, why not try deactivating DroidWall 1.5.7, BINGO!
Data did dropped at times but it came back up, and loaded the page, I guess it was because a data cap, I'm just guessing. But if it makes it the whole day without giving problems, that was probably the culprit:victory:
i know
real187 said:
we dont have a enginering hboot so forget it using fastboot.
use the temp or sense installers in the dev section.
Click to expand...
Click to collapse
Hey the problem is the rom! it just has the meta it need the system file without it it will fail. also you need recorvery clock work mod or twrp without then it is a fail but find a better rom first
I got the same problem. Ran the JB_TMOUS RUU and lost my phone signal. I tried newest CM rom (4.4.2) but it didn't help. Tried flashing temporary radio V4, and it made no difference. How do I get my phone service back?
sns00 said:
---Bump---
Hello all on my first post.
Background:
Long story short,screwed up my phone a little while back, recovered with: RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed
Everything peachy after that, then a couple of days after I got a hold of:
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB
Then the problems started, every ROM I tried, the connection dropped and had to restart the phone. Tried to Facepalm, Moonshine, Super CID 11111111, nothing. Spent hours reading and thinking how I could get around this, I can't S-Off, so I can't change the radio and use a regular ROM like CM or BlackBean, not that I'm not grateful, just Sense is not really my thing. Tried BlackBean 9 with kernel 3.4 and didn't worked.
Any ROM that is not Sense based would not keep the signal for internet, unless rebooted.
So my question is: once you have HBOOT 2.15.0000 and Radio 1.13.50.05.31 you are screwed, did anyone in the same situation got S-Off or got it to work some how?
I did make a mission to check the forums for the methods I mentioned for the past 3 months, weekly if not daily.
The phone had originally:
HBOOT-1.14.0005
RADIO-1.11t.50.02.22
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41
But couldn't find the RUU with that radio, so used the one with 1.08ts.
Thanks in advance.
Click to expand...
Click to collapse
Now, I am in the same s*** position as you. Did you solve the problem? If you did please, explain how did you solve it.
"cough" A bit late, but just for future reference for anyone that might find themselves with the same problem.
Get a hold of rumrunner to S-Off, thats the only method that I've tried that worked, also if you can't find rumrunner, get a Sense ROM to keep you using the phone.
I gave up after a long wait for a reliable S-Off method, so my phone was stored for about a year been using my old Sensation 4G.
And just to put it out there, always check, double check and triple check before you do anything, if you are impatient at the moment, go out for a smoke, get some gum, drink a beer, whatever you need to do to relax a bit, and then go back to the task, I know is not surgery but it felt like that at times.:silly:
pkayrat said:
Now, I am in the same s*** position as you. Did you solve the problem? If you did please, explain how did you solve it.
Click to expand...
Click to collapse
Ok guys, i've been runnin Unknown JB 2.0 Tmo Rom on my one S. Maps has been constantly crashing on me. i had this issue on a few other JB roms as well. I heard it maybe an Hboot issue. Heres my info.
S-off
Hboot 1.06
Radio 1.13.50.05.31
I havent updated my hboot to the 2. one because I thought you could flash boot.img thru recovery on it and just havent really wanetd to mess with it too much. Everything else works, including wifi. Any help is appreciated.