[Q] Missing messages sound configuration & xt9 issue - after update to 1.33 - HTC ChaCha

I'm a polish orange htc chacha user. I've flashed my ChaCha to 1.33 via gold card. But I have noticable problem.
First one is sms sound. There is no sound/vibration when sms comes. The issue is that there is missing menu for configuration of sms sound in personalisation.
E-mail, alarms etc are located there but no sms sound o_0
Second thing is - how the hell can i disable xt9 at all? When i write sms in polish i can see notification icon with xt9 En enabled. I don't want it at all. Also i can't find anything to turn it off in menus.
didnt have theese problems on 1.18
(i'm s-on so no chance of getting 1.52 OTA ;( )

If you are s-off you can get to 1.52 manually. Check the OTA topic, there are explanations there. My device is s-off and I flashed 1.52.

Alex C. said:
If you are s-off you can get to 1.52 manually. Check the OTA topic, there are explanations there. My device is s-off and I flashed 1.52.
Click to expand...
Click to collapse
duh, again i meant s-on and wrote s-off...
i'm S-ON with 1.33 flashed via goldcard.
after factory reset i got menu for sms sound back.
But still - no idea how to switch spell checking. Just hate xt9 underlining my sms'es.

Related

[Q] Problem after flashing to HSPL, PLS HELP ME..

Hi everyone...i have a problem after flashing to HSPL and need help. My original SPL was SPL 1.42.0000.
My other device information are:
OS 5.2.21869.5.0.83
Manila ver 2.5.19211619.0
ROM ver 1.66.707.1 (76641) WWE
Radio ver 2.07.51.22_2
Protocol ver 15.32.50.07U
Before, i use several Touch X apps installed to my device and i did back up all data by using PIM back up. During process of the flashing, once came up popup text on my PC sceen saying that "critical error...etc" then i closed the popoup text..and i continued by choosing 2.08. so then the process done. and i received the message "we hack it" and "succesfully...". I checked the new SPL of my device, and it says:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
After that, i restore all data from PIM backup. everything looks Okay. But then, i often received several messages from microsoft saying:
--> the problem occured with facebook, pls report back to microsoft (something like that). I did uninstalled the facebook and re installed back...but same problem.
--> Also, i received the same text saying that i have problem with manilla.exe.
--> and the reminder led is keep blinking unless u pull out the battere.
It looks like the system has messed up after i flashed to HSPL (i still use the original ROM version dan Radio version as above mentioned). I have read the instruction well. Saying that the flashing should be OK for device with 512MB of flash size and the SPL 1.42.0000.
Can anyone please held me with this. Really appreaciate your help. Thank you. My regard, Yonz.

[Q] Issue with 1.47.401.4 : often get "Limited Service" and hard to get signal back

[Q] Issue with 1.47.401.4 : often get "Limited Service" and hard to get signal back
Hi there,
Since 1.47.401.4 (and never before with 1.28.x), I'm experiencing issues with the radio, especially voice:
1/ I often get a "Limited Service" warning in places where I could easily get a decent signal to give a call.
2/ Each time I got the "Limited Service" warning, it can take ages before the signal gets back (after I moved to some other place).
3/ Sometimes, I need to reboot the terminal to get the voice signal back.
I did perform a full wipe (factory reset) on my phone and install the rom again (using the roms.zip method within the bootloader) but it didn't really solve this issue.
I also cleaned the sim card contacts, just in case, but this was useless.
I also chose "GSM auto (PRL)" in the phone settings, this helped a bit, but still this annoying issue remains.
If someone got a clue, I'm interested ! And if anyone is experiencing such weak/bad signal issue, I'm interested in your feedback.
Cheers.
Hboot: 098.002 S-ON
Radio: 20.28I.30.085 AU_3805.06.02.03_M
~babel said:
Hi there,
Since 1.47.401.4 (and never before with 1.28.x), I'm experiencing issues with the radio, especially voice:
1/ I often get a "Limited Service" warning in places where I could easily get a decent signal to give a call.
2/ Each time I got the "Limited Service" warning, it can take ages before the signal gets back (after I moved to some other place).
3/ Sometimes, I need to reboot the terminal to get the voice signal back.
I did perform a full wipe (factory reset) on my phone and install the rom again (using the roms.zip method within the bootloader) but it didn't really solve this issue.
I also cleaned the sim card contacts, just in case, but this was useless.
I also chose "GSM auto (PRL)" in the phone settings, this helped a bit, but still this annoying issue remains.
If someone got a clue, I'm interested ! And if anyone is experiencing such weak/bad signal issue, I'm interested in your feedback.
Cheers.
Hboot: 098.002 S-ON
Radio: 20.28I.30.085 AU_3805.06.02.03_M
Click to expand...
Click to collapse
I have the same problem! 1.28.x was OK, bet the newest one in terms of receiving signals is just terrible!
Hi, have you found any solution so far ?
HTC wants me to sent my phone back but I don't think this issue has something to do with the hardware...
~babel said:
Hi, have you found any solution so far ?
HTC wants me to sent my phone back but I don't think this issue has something to do with the hardware...
Click to expand...
Click to collapse
In complete contrast to what you two are saying..(see my old thread where I had this problem with the older radios http://forum.xda-developers.com/showthread.php?t=1133785)
I'm now running on the latest radio but not the latest ROM (as I use LBC MOD which is currently based on a 1.36 ROM) and I no longer experience this problem.
My conclusion being that the newest Radio is better.
Thanks for your feedback.
Would you then say that the "Radio_20.28I.30.085 AU_3805.06.02.03_M" was the answer to your phone bad signal issues ? Then, I might need to use another rom an check if that helps...
Anyway, did you try to change/update phone/radio settings mode (__http__www_google_com_support_forum_p_android_thread_?tid=42655c79e5837499&hl=en) ?
~babel said:
Hi, have you found any solution so far ?
HTC wants me to sent my phone back but I don't think this issue has something to do with the hardware...
Click to expand...
Click to collapse
I have this problem as well and have emailed HTC but received no reply yet.
Also sometimes it all looks okay and allows calls out but incoming calls go straight to voicemail.
Well, HTC will probable ask you to send your phone for repair.
Actually, this is what they've just replied to my email. But I won't send my phone for a simple flash that I could do my-self !
It seems this is a known issue of the HTC phones (there are plenty of such reports on the internet).
Although this problem hasn't effected my calls on the latest radio version, I do agree that I've often seen what looks like severe signal fluctuations, from zero bars to full bars etc, I've also read about this being an issue on the incredible s
I'm hoping that further rom and radio upgrades will improve this.
Sent from my HTC Desire S using XDA Premium App
It seems that the "Limited Service" issue is caused by a signal loss (i.e. using the elevator for instance) that is never followed by an automatic "good signal" retrieval (i.e. after leaving the elevator and going to a place where signal is usually very good).
~babel said:
Thanks for your feedback.
Would you then say that the "Radio_20.28I.30.085 AU_3805.06.02.03_M" was the answer to your phone bad signal issues ? Then, I might need to use another rom an check if that helps...
Anyway, did you try to change/update phone/radio settings mode (__http__www_google_com_support_forum_p_android_thread_?tid=42655c79e5837499&hl=en) ?
Click to expand...
Click to collapse
I'm afraid that I don't understand what this question? could you PM me?
did it mean did I switch my phone to WCMDA only? if so the answer is NO, mine is set to Auto as around where I live and work there is reasonably good signal.
ben_pyett said:
did it mean did I switch my phone to WCMDA only? if so the answer is NO, mine is set to Auto as around where I live and work there is reasonably good signal.
Click to expand...
Click to collapse
yes, this is what i wanted to know anyway, this didn't change anything for me.
Have you progressed any?
I tried flashing to 1.28 via the RUU at http://forum.xda-developers.com/showthread.php?t=1002506 but it doesn't appear to want to do a downgrade.
I don't seem to get getting the no service at the moment but I am having problems with incoming calls going to voicemail when the phone claims to be connected.
I put my SIM (giffgaff, a MVNO on O2-UK) into my old phone (an XDA Zest) and put an O2-UK SIM into the HTC. At times I could call the XDA with no problem but calling the HTC went to voicemail - two phones next to each other on the same network....
Of course I can't say if this was a problem with 1.28 as I wasn't looking for it but I suspect 1.47 is the problem.
As expected HTC want me to send the phone back which I think I might do and try and persuade them to downgrade it for me.
yes some progress, at last ! I followed the step by step procedure to s-off the rom 1.47.401.4 rom (http://forum.xda-developers.com/showthread.php?t=1194488) and then downgrade to the 1.28.401.7 rom that I was using originally. And now everything works fine...
i could say that once again i learnt that newer doesn't mean better
~babel said:
yes some progress, at last ! I followed the step by step procedure to s-off the rom 1.47.401.4 rom (http://forum.xda-developers.com/showthread.php?t=1194488) and then downgrade to the 1.28.401.7 rom that I was using originally. And now everything works fine...
i could say that once again i learnt that newer doesn't mean better
Click to expand...
Click to collapse
What method did you use to do the downgrade?
I was thinking of trying the method here http://forum.xda-developers.com/showthread.php?t=1190992 which I don't think needs s-off.
Update: I tried the non S-OFF method and have downgraded to 1.28 - I'll see how it behaves now.
I used the PG88IMG.zip method. Basically, you need to copy the roms.zip extracted from the RUU installer to the root of your /sdcard and then reboot your phone to the bootloader.
~babel said:
I used the PG88IMG.zip method. Basically, you need to copy the roms.zip extracted from the RUU installer to the root of your /sdcard and then reboot your phone to the bootloader.
Click to expand...
Click to collapse
I ran the RUU exe directly which seemed less involved. It's looking good so far but I'll need to get out and about and see how it behaves in different locations.
I'll not be in such a hurry to install an OTA next time...
ercm03 said:
I'll not be in such a hurry to install an OTA next time...
Click to expand...
Click to collapse
i see what you mean
solved using the first steps on http://forum.xda-developers.com/showthread.php?p=16796075#post16796075
-------------------------------------------------------
same problem here... tried the PG88IMG.zip method but it said "main version is newer" or something like this... so it didn't work..
do I have to do something before that? I used this ruu:
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release
and currently installed is this:
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed
where can I get a rom.zip that works?
After earlier saying that I'd not experienced this limited service problem, I have now witnessed this a couple of times.
Although, since I applied this
20.4130.0818U_3817.07.00.19_M RADIO I haven't, will re-update post if I do!
This is the Radio that came with the recently leaked Sense SAGA Sense v3.0 ROM and appears to work fine with LBC mod.
does anyone know if one can install this radio over 1.47 with s-off and no root? and if yes - how?

[Q] Touch input has stopped..

Hey guys,
i installed(flashed) the sense 4.0 keyboard from here http://forum.xda-developers.com/showthread.php?t=1606569 and now every second the dialogue 'Touch input has..' appears! I don't know what to do now. Easiest would be to install the original Htc_ime again..but where can i find it?
Thanks for help!
First, try running fix permissions from recovery. If that does not fix it then you can pull the HTC_IME from any 3.6 stock based ROM.
HTC_IME
Thank you so far, fix permissions did not help..
ok extracting the file sounds good, but how can i pull it out of a ROM?
lukas1187 said:
Thank you so far, fix permissions did not help..
ok extracting the file sounds good, but how can i pull it out of a ROM?
Click to expand...
Click to collapse
Really??
.
.
.
.
Really??
Extract the ROM and locate the file...
i found a htc_ime on the internet and flashed it from recovery --> no result
do you think it would be helpful to completely install a stock rom?
It would be helpful to replace htc_ime with the correct one for your ROM and wipe cache/dalvik...
Sorry, but i don't know which ROM i can use.
My bootloader says the following:
Pyramid PVT SHIP S-OFF RL
Hboot - 1.27.1111
RADIO - 11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
eMMc-boot
(sorry that i ask that much questions but i don't wanna do another mistake )
Ok solved my problem by flashing another ROM, now i'm lucky and learned to be more careful
"touch input has stopped" - FIXED
I had the above problem following a ROM Upgrade on my HTC Desire HD mobile.
This was after upgrading to a ICS ( ice cream sandwich ) ROM.
"Unfortunately touch input has stopped" is the error i got when trying to add a phone number on contacts.
This is what i did
Installed GO Keyboard and updated a few settings under language and keyboard
Removed some of the Thai and Chinese default settings
Hope this helps someone

OTA Update to Android 4.0.4 ,Ver 2.31.401.5 & Sense 4.1 for S4 is Out!

Update: the first users got this OTA update on their stock, non rooted, untouched HTC One S (S4). Everyone could choose to wait to get the update in the normal way.
Required
- CID HTC 304 (some kind of universal carrier ID/ region, named the 'developers region'). Everyone can install CID HTC 304, if you're on European users. Ofcourse you can always restore your original cidnumber if you want.
- The stock 1.78 WWE ROM (d-h.st mirror or hotfile.com mirror). Also everyone need this ROM and everyone can install this rom if you have got CID HTC 304.
- Back-up of your files on computer. This update will format all partitions, even the sd card!
http://www.htcmania.com/showthread.php?t=437857
Thanks! and what are the new things in this ota?
Sent from my HTC One S using Tapatalk 2
I would love it if someone could post a clean twrp nandroid recovery zip, a flashable radio, and the new boot.img! That way we could all flash without waiting for the ruu!
Sent from my Nexus 7 using xda app-developers app
Still no OTA update for HTC__001 CID for 2.31 from 2.21
Don't know if I did this right, but because I am rooted on stock 2.21 ROM , I flashed stock recovery.img from 2.21 RUU over CWM recovery.img, and checked for OTA in settings and got that there are no updates available. Is this the correct procedure to do OTA update ? Don't know if I messed up something
Seems we can't get OTA from 2.21 ROM, we'll need to wait an RUU to upgrade...
Antubis said:
Seems we can't get OTA from 2.21 ROM, we'll need to wait an RUU to upgrade...
Click to expand...
Click to collapse
Correct only peeps on 1.78 are getting this ota.
Sent from my Nexus 7 using xda app-developers app
chrikenn said:
I would love it if someone could post a clean twrp nandroid recovery zip, a flashable radio, and the new boot.img! That way we could all flash without waiting for the ruu!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I found this link and it states that it is for new OTA, but don't know for sure.
HTC released 2.31 OTA for One S, New OTA has Sense 4.1, Android 4.0.4 and new Radio.
http://fotadl.htc.com/OTA_Ville_U_I...1.78.401.2_release_275773ape8z1mahr0gt8fg.zip
I got the update earlier today (I had stock 1.78 before of course) but I think there might be a problem with it. It may be a coincidence, but I did not receive all SMS sent by a friend today. I'm not sure how many of them I didn't get, but I did not get one long SMS for sure (long like 3 SMS's) and maybe one or two others, including one sent by someone else.
Another minor problem I spotted: if I want to send a long SMS, the bar with word suggestions places itself right in the middle of the typing zone (in landscape mode at least).
My network operator says there is no known issues with SMS services today, that's why I thought about an issue with the update... Anyone else having this issue after the update?
Why do people keep posting this stuff in Q&A? The new radio is working great for me.
---------- Post added at 01:41 PM ---------- Previous post was at 01:16 PM ----------
Charkatak said:
I found this link and it states that it is for new OTA, but don't know for sure.
HTC released 2.31 OTA for One S, New OTA has Sense 4.1, Android 4.0.4 and new Radio.
http://fotadl.htc.com/OTA_Ville_U_I...1.78.401.2_release_275773ape8z1mahr0gt8fg.zip
Click to expand...
Click to collapse
This is only the OTA. We want a full nandroid ROM. Someone could take a stock rooted 2.21 and replace the files in the OTA and flash it?
Whats new ? is there a changelog ?
BackDaws said:
Whats new ? is there a changelog ?
Click to expand...
Click to collapse
New baseband, new kernel. Didn't have the time to figure out the rest by now.
and still no solution for the home button issue. The reception seems to be beter in 2g and 3g modes. Still I'm able te reproduce the home button issue in 'gsm' and 'gsm/WCDMA' modus, only 'WCDMA' mode prevents the home screen from flipping.
HTC One S Android 4.0.4. Sense 4.1 update 2.3.1. stock, no-root, no-unlock.
I hope this fits in here:
I just got the notification for the 4.0.4 update on my One S (in Germany) and tried to install it. My phone is rooted and I have ClockworkMod v5.8.3.1 installed. After rebooting the installation is cancelled with the following error:
E: unknown volume for path [INTERNALSDCARD: Download/OAT_ville_...zip]
E: Can't mount INTERNALSDCARD: Download /OAT_ville_...zip
Installation aborted.
Du I have to install the update manually using CWM? Will this wipe my user data?
Thank you for your help!
You have to use stock recovery to apply an OTA update.
It should not wipe anything, but be wise and make a backup before...
Im on 2.21 locked, non rooted stock. How can I apply this update?
to return of stock download this https://dl.dropbox.com/u/89172728/R....27_2_10.08.50.04L__release_271119_signed.exe
jandari said:
Im on 2.21 locked, non rooted stock. How can I apply this update?
Click to expand...
Click to collapse
This OTA only for the RUU 1.78.. and 2.21 need to wait..
Can confirm 2.31 update (from 1.78) on my Stock non-rooted Euro (HTC__E11 CID) One S [Netherlands]. Current phone info:
For those wanting to know what's in the OTA from what I've tinkered around with:
Current device info:
Android: 4.0.4
Sense: 4.1
Software Version: 2.31.401.5
Baseband:1.06es.50.02.31_10.09a.50.04L
Build: 2.31.401.5 CL90817 release-keys
Kernel: 3.0.8-01575-gbcda118 [email protected] #1 SMP PREEMPT
What I've noticed:
*Smoother transitions on home screens
* "Tabs" button in browser
*Back/Forward buttons rearranged in browser menu
*Recent Apps button can be configured for recent apps and "menu" in any order (touch/touch and hold)
*Less H/3G switching, higher data speeds in same network area
*Slight improvement in battery performance
*Transition for Recent Apps improved
*"Rescue" and "EA Games" app available
Other observations:
*Quadrant score improved from 4600 to 5480
*HTC System apps open much faster
*Screen rotation faster'
A weird glitch though, anybody noticed this: When the battery gets low and the LED starts flashing, if you touch and release the status bar, it triggers a LED flash. Like, by repeatedly tapping the status bar the orange LED flashes very rapidly upon touch. Anyone noticed that?
aardbeix15 said:
and still no solution for the home button issue. The reception seems to be beter in 2g and 3g modes. Still I'm able te reproduce the home button issue in 'gsm' and 'gsm/WCDMA' modus, only 'WCDMA' mode prevents the home screen from flipping.
HTC One S Android 4.0.4. Sense 4.1 update 2.3.1. stock, no-root, no-unlock.
Click to expand...
Click to collapse
I don't think its a software problem. When I run ROMs based on the old 1.78 or new trick droid ROMs I don't have the problem.
I think its a actual hardware problem with the antenna at certain frequencies making the screen think your touching it.
The 2g/3g antenna is right behind the home button almost.
Sent from my HTC One S using xda premium
You can flash a recovery from stock 1.53 and stock recovery with bootloader open and then yoi have the updates
Enviado desde mi HTC One S Juredroid_V1.4 usando Tapatalk 2

[Q] [ROM][4.4.2][Sense 6][SVN] help thread for LIBERTY ROM - The Sixth Element

Hello,
I can not find similar topic in the HELP forum so let me start it (at least for new users of XDA forum).
At the very beginning I would like to thank bilal_liberty for all his work given for Liberty ROM. Same time I want to thank all participants of his success - all developers, testers and helpers for their time and patience..
Now, my problems:
1) I can not run WIFI hotspot. The icon is working, working and... doing nothing.
2) From time to time I can not run WIFI connection in my home. Of course everything is "ON", I tried to restart the phone, turn of the data transfers and some other tricks - the connection was working just after installing the ROM, but it is a lottery.
3) I have an issue with memory: I can't see the "SDCARD" memory - only when in TWRP mode, after mounting the SDCARD drive. When connecting in normal mode through USB - I can see only about 2 GB.
Is there any solution for those problems?
HTC One S(4), s-off, TWRP 2.7.0.1, hboot 2.15 (I don't believe 2.16 will change it but "if" - I'll upgrade, of course...
Thanks for any help.
Hello xklonik and welcome to our community,
to answer your questions in descending order.
3) Sixth Sense is not compatible with hboot 2.15, so that's why you have problems with your sd card inside the rom (recovery is somewhat, "standalone")
2 + 1 ) These problems are well known issues and reported over the development thread. Developers are working hard to try and fix these issues but it's also a fact that without the source code of the sense roms, there's only so much we can do.
Also maybe because of your incompatible boot, these issues are getting worse.
There are two solutions:
a) Either upfrade to hboot 2.16 (with the procedure at maximusHD thread)
or if you are scared of this procedure
b) stay on hboot 2.15 and use LibertyMAX instead (both hboot supported and is more stable in my opinion - and by stable I mean no weird wifi issues whatsoever)
Other than that, both roms are excellent and it's really a matter of preference which one to choose. :good:
ChrisAr said:
Hello xklonik and welcome to our community,
to answer your questions in descending order.
3) Sixth Sense is not compatible with hboot 2.15, so that's why you have problems with your sd card inside the rom (recovery is somewhat, "standalone")
2 + 1 ) These problems are well known issues and reported over the development thread. Developers are working hard to try and fix these issues but it's also a fact that without the source code of the sense roms, there's only so much we can do.
Also maybe because of your incompatible boot, these issues are getting worse.
There are two solutions:
a) Either upfrade to hboot 2.16 (with the procedure at maximusHD thread)
or if you are scared of this procedure
b) stay on hboot 2.15 and use LibertyMAX instead (both hboot supported and is more stable in my opinion - and by stable I mean no weird wifi issues whatsoever)
Other than that, both roms are excellent and it's really a matter of preference which one to choose. :good:
Click to expand...
Click to collapse
Hi ChrisAr.
Thanks for your reply.
I'm not scared with the hboot change I just couldn't see any reason to change it if the ROM (at all) was working. Now I see that my issues can be caused by this tinny missing so I'll update hboot after working hours
I'll update this thread after the upgrade.
Thanks for help.
No problem, glad to help
Be aware though. After upgrading hboot(following carefully MaximusHD's instructions), you must reflash recovery with 2.16 hboot support which can be found here -> mdmower.cmphys.com/twrp-ville/ (Cannot post full link due to post restrictions)
Just be sure to flash the one under /data/media storage (HBOOT 2.16.0000 only) header.
:good:
so.. there is a problem...
without any issue I succeed with hboot update to 2.16... however..
as you suggested, I also downloaded and upgraded TWRP with hboot 2.16 support (both, twrp-2.7.1.0a-ville-dm, twrp-2.7.1.2-ville-dm)...
unfortunately, after reboot to TWRP, I can not "mount SDCARD", which previously was available in hboot 2.15 & TWRP 2.7.0.1 in MOUNT menu..
also - I don't know why - I could not find my ROM on SDCARD and actually, I could not access the card at all...
so, I can not install anything.. I can boot to bootloader or TWRP, I can communicate with the cellphone via fastboot (I can change TWRP to any version I want)... I tried to flash-in my old version of TWRP, properly working with 2.15, but under 2.16 I have only 48 MB of free space when mounting the SDCARD
any advice?
I have:
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-OFF RL
CID-HTC__032
HBOOT-2.16.0000
RADIO-1.20.50.05.16
OpenDSP-v33.1.0.45.1128
twrp-2.7.1.2-ville-dm
-------------------------------- edit ----------------------------------------
ok, I found the way out...
since my connection with phone works perfectly, only one way to deal with lack of space and no ROM on SDCARD was to push it via adb
adb push yourrom.zip /sdcard/yourrom.zip
the rest after this was easy (recovery -> install ROM -> configure -> enjoy)...
thanks again for links and support!
xklonik said:
so.. there is a problem...
without any issue I succeed with hboot update to 2.16... however..
as you suggested, I also downloaded and upgraded TWRP with hboot 2.16 support (both, twrp-2.7.1.0a-ville-dm, twrp-2.7.1.2-ville-dm)...
unfortunately, after reboot to TWRP, I can not "mount SDCARD", which previously was available in hboot 2.15 & TWRP 2.7.0.1 in MOUNT menu..
also - I don't know why - I could not find my ROM on SDCARD and actually, I could not access the card at all...
so, I can not install anything.. I can boot to bootloader or TWRP, I can communicate with the cellphone via fastboot (I can change TWRP to any version I want)... I tried to flash-in my old version of TWRP, properly working with 2.15, but under 2.16 I have only 48 MB of free space when mounting the SDCARD
any advice?
I have:
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-OFF RL
CID-HTC__032
HBOOT-2.16.0000
RADIO-1.20.50.05.16
OpenDSP-v33.1.0.45.1128
twrp-2.7.1.2-ville-dm
-------------------------------- edit ----------------------------------------
ok, I found the way out...
since my connection with phone works perfectly, only one way to deal with lack of space and no ROM on SDCARD was to push it via adb
adb push yourrom.zip /sdcard/yourrom.zip
the rest after this was easy (recovery -> install ROM -> configure -> enjoy)...
thanks again for links and support!
Click to expand...
Click to collapse
Sorry I didn't see your post earlier. I was away on vacation.
In that time, sixth sense got 2.15 support.. Irony
Not sure why you had that problem. Maybe you had to perform a full wipe (from the recovery options) to force re-partitioning. Old hboot had created different partitions on phone's memory and you had to create them from scratch, for the new hboot.
Also I assume you know that when you change hboot, you have to re-install also everything from scratch since everything installs according to hboot. If you just upgraded hboot, it would not work as expected if you just left the old installation there.
Anyway, glad to hear this worked for you and that you also found a workaround with "adb push" by your self. Good job :good:
Enjoy this awesome ROM. (Just flashed it too this morning) :highfive:
yeas... actually I did the instalation agait too..
and unfortunately wifi still wont work
btw. I'm always performing full wipe, so have no idea what happened then..nevertheless, I've full space and rest of toys, just without wifi and hot spot, what in fact, eliminates this ROM.. :/
unfortunately 2) no one answered my mail regarding any ROM supporting all One S features (camera, wifi, hotspot, BT) and Sense 6 on newest kitkat... so I'm still in the oblivion.. waiting for some light..
just to confirm - build 106 - after changing 1.35a.32.45.27, WCNSS, ADSP, wifi & hotspot still not working,
what is interesting, previously the wifi icon only blinked - currently "scanning" & "disconnecting" subtitles are visible under this icon...
also previously just right after installing I could connect to my network and wifi was turned off just after authorisation and few next screens..
now with new 1.35a.32.45.27, WCNSS, ADSP I can not join at all..
I've been following your posts on the development thread.
This issue is really weird...I wanted to write about different WCNSS versions (some people flashed it from the Viper ROM) but I couldn't post due to post count restriction. Anyway, bilal noticed that too in his recent post. I have flashed everything you flashed and only reverted to radio 1.20 but with hsdpa fix (it is included in one of the flashable radios, don't know if it's included in the version you downloaded)
WiFi is working perfectly for me. Only this "keep always on" issue.
Hi everyone,
First off thanks to bilal for his amazing work, second I hope I am not off topic since this is a help thread for Liberty SixthSense.
After reading the entire development thread on this ROM, I still can't figure out how to install it on hboot2.15. I get a feeling that there is a different way to install this rom on 2.15, or I'm missing something.
So yes, I download the zips of r106 version and the radio 1.20 version. But afterwards I just do as I would do with any other ROM? I mean full wipe, dalvik cache wipe, recovery cache wipe, and then install from zips? and if so, which should be instlled first, the radio or the whole rom?
Mindue, I am noob at this, so I don't understand everything I've read so far and this would be the only way I know to install a rom.:silly:
quick checklist:
- S4
- recovery TWRP 2.7.1.0 the one from Cyanogenmod 11 since I'm on this rom now.
- S-OFF
- hboot 2.15
Hi!
I think you are good to go. Since you don't know any other way to install a ROM (adb sideload/push), I would say to be carefull what you wipe because you might erase the OS and you won't be able to transfer the zips from your computer (regularly, like a flash drive).
Other than that everything is good...recovery is for right hboot(since you already have cm11; official I suppose which is for 2.15)
Flash radio
Flash ROM -> choose full wipe during install
Never heard of recovery cache wipe so don't mess with that
Best of luck! :good:
ChrisAr said:
Hi!
I think you are good to go. Since you don't know any other way to install a ROM (adb sideload/push), I would say to be carefull what you wipe because you might erase the OS and you won't be able to transfer the zips from your computer (regularly, like a flash drive).
Other than that everything is good...recovery is for right hboot(since you already have cm11; official I suppose which is for 2.15)
Flash radio
Flash ROM -> choose full wipe during install
Never heard of recovery cache wipe so don't mess with that
Best of luck! :good:
Click to expand...
Click to collapse
Thank you! I will try and see where it leads me, if it fails I believe I can put back the cm11 right ? even with the new flashed radio.
As far as I know, there are no problems with cm11 and radios...but even if there is, you can always flash an older radio...but 1.20 is the recommended for our device in general.
Glad I could help :good:
Ok, so I try to flash the radio (before full wipe and rom flash) but it fails, I get the followings:
checking for MD5 file > no MD5 file found
verifying zip signature > failed
any ideas to where I went wrong?
LATER EDIT: scratch that, the problem was the 'ZIP signature files verification' box should have been unticked and thus no more md5 file required. --> radio flashed! now on 1.20. later I will try to flash the liberty rom. update afterwards
PS. found this in another thread:
"an md5 is not "added to a file", nor is it "a part of a file". An md5 is merely a hexadecimal readout of the contents of that file.
Here's how it works: A file is created, in our case it is a zip file. The creator or publisher of that file uses an md5 generator to generate the md5sum, which as I said before, is just a numerical readout (like a fingerprint) of the contents of that file. Now the end user has a tool to make sure that the file hasn't been compromised during a download or transfer. Using an md5 checker is a simple way to verify that the file is uncompromised. Input the md5 given by the publisher into an md5 checking app, then the app calculates the md5 of the file you've downloaded, if they match you know the file integrity is good."
Just installed the ROM, everything works fine, very fast and smooth, no WiFi problems, HOPEFULLY no radio problems (I previously had Venom Viper Sense5 and had major issues with radio and lots of random restarts).
ArcsONE said:
Just installed the ROM, everything works fine, very fast and smooth, no WiFi problems, HOPEFULLY no radio problems (I previously had Venom Viper Sense5 and had major issues with radio and lots of random restarts).
Click to expand...
Click to collapse
Glad to hear that.
I had also these random restarts, but they are gone now.
Enjoy
Still new here so can't post in the dev thread, but...
Installed the latest version (clean install), everything works solid. Hotspot works as before - have to turn it on, then reboot and Wi-Fi mostly works but occasionally needs restart to work. Other than that, everything is stable and quick, very happy with the ROM. As I primarily use 3G and don't rely on Wi-Fi as well as can use USB tethering instead of Wi-Fi hotspot, I'm not that annoyed by these issues.
However - on r107, I tried out the ElementalX 7.0 kernel as well but as I experienced issues with touch screen, I searched the thread and found a fix which turned out to be a special kernel. Therefore although the kernel in the ROM was updated and now there are no touch issues with the default kernel, the ElementalX kernel also needs updating. Really miss DT2W but a responsive touchscreen is more important to me.
Tried the kernel now after r111 install but the touch problem is still there so had to revert to default kernel.
I hope the kernel's developer sees this and can release an update :fingers-crossed:
no recent apps
I cant find the recent apps in this system
Problems
Hey guys, first post in this forum. I'm a total noob when it comes to rooting and roms and all this stuff, but if I didn't try it I would always be, so I tried this rom on my htc one s.
Several problems, I may have screwed up of course, I followed some tutorials, so I have this rom, but I am S-On, and my hboot is 2.15, I think that is what is causing me problems (SD card not recognized, meaning, no storage space, wifi problems, can't log in to google play).
But I can't get S-off, I've tried every single way, and something always goes wrong, I don't know what to do now, I think the solution would be to change to hboot 2.16, but I just can't do it, probably need to be S-off? No idea, would love to hear some feedback, I'll leave you with whatever it says on my bootloader.
TAMPERED
UNLOCKED
VLE PUT SHIP S-ON RL
HBOOT- 2.15.0000
RADIO - 1.15.50.05.29 (tried changing it, can't as well.)
OpenDSP - v31.1.0.45.0015
Plese help me guys, really don't know what to do, I think I might have accidentally deleted the stock Android.
Much thanks
Anyone else having problems with audio quality in calls? Any fix? I found liberty rom v2 on an italian forum, it says audio quality it's fixed in that, has anyone tried it?
VLE PVT SHIP S-OFF RL
CID - 11111111
HBOOT - 2.16.0000
RADIO - 1.20.50.05.16
OpenDSP-v33.1.0.545.1128
eMMC-boot

Categories

Resources