Related
Im currently in the middle of uploading a video to youtube to try and show the issue but its like my phone is possessed, i actually bought the phone from a recycle place so I have a 60 days warranty with the phone but I was wondering is there a diagnostic or service mode I can get into on the handset to see if any faults are found
One thing is I thought I was getting an Orange handset which I would have thought would have had some branding on but it didnt and it also didnt have any orange bloatware on but not sure if they do or not on Orange UK handsets? even though i've supercid would it matter if it wasnt an Orange one that I used the orange firmware for 3.32?
It seemed fine when it arrived yesterday on 2.3.4 GB rom but since changing to ICS nothing but bother
Link isnt live yet showing about 12 mins to go at 21:49 UK Time
http://youtu.be/Z2Bvf0FfTlU
My phone is currently
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
Hboot-1.27.1100
Radio-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012.17:33:34
Had this problem with Darkforest 6.0.0 and also ARHD 6.5.1 and currently virtuous s4x b3 which has been the worst of the lot and the one in the video
Ok so I flashed back 1.17 firmware and restored a back up of my GB 2.3.4 rom and its working perfectly so my guess is my phone for some reason doesnt like firmware 3.32? which means im going to be pretty much stuck on GB?
Hey, it looks like a sense 4 rom that is running in the video? All those roms are ported from another device.. I'd recommend to try stock ICS with the new firmware, see if that works any better than the ported roms
Ive tried 2 3.6 roms too and they did the same, used the newest firmware
http://www.htcsensationforum.com/htc-sensation-4g-how-to/secret-menu's-in-sensation/
The Radius Kid said:
http://www.htcsensationforum.com/htc-sensation-4g-how-to/secret-menu's-in-sensation/
Click to expand...
Click to collapse
thanks, not quite sure what im look at but thanks all the same will take a peek
bradmax57 said:
thanks, not quite sure what im look at but thanks all the same will take a peek
Click to expand...
Click to collapse
In your first post you were looking for a diagnostic mode?
The Radius Kid said:
In your first post you were looking for a diagnostic mode?
Click to expand...
Click to collapse
Sorry yeah i am and thanks, just not sure which tests i should be looking at, anyway im now on virtuous_inquisition v4.0.0 but using firmware 3.24 its had one little hissy fit which seems to have gone away when i restarted, also when it starts acting usual screen of and on seems to sort it, its just odd it works perfectly in GB which makes me think its software and not hardware issues?
Just to confirm im doing everything right, was it ok to jump from firmware 1.17 on GB straight to 3.32 for ICS with 3.6?
Method im doing
flash firmware in hboot, pull battery delete the PG58IMG file, put battery back in boot into recovery, full wipe in ext4, then run the superwipe script and then install rom, everything seems to go ok until I begin having the issues as shown above in the video clip, I know that was a sense 4 rom but its done the same in 3 sense 3.6 roms now
Did you tried to flash a stock kernel? Not OC'ed? My bet if every ROM does the same, that there is an issue with the hardware.
davebugyi said:
Did you tried to flash a stock kernel? Not OC'ed? My bet if every ROM does the same, that there is an issue with the hardware.
Click to expand...
Click to collapse
Hi
I havent as yet, however when I first had problems on darkforest I did try with the 1.2ghz option during flash.
Any recommendations on which to try? So far it seems on on v inquisition v4
Seems to have been ok then this morning I put the phone on charge as it was about 20% remaining, left it charging went back 30mins later or so to check it and it wouldnt wake, not sure if this is a common issue or if its related to the previous problems ive been having?
Ive requested a return from the place I bought it so will see, ill have to make sure I can get it back to how it was, fortunately I have a backup, but ill have to read up on the s-on procedure aswell as getting rid of 4ext
gawd this is doing my nut in, just flashed Android Revolution 6.5.1 using the stock 1.2ghz kernal doing the same so I just have no idea now, going to put firmware 1.7 back on and do a nandroid recovery and see how that goes for the next few days, just wondering if anywhere in the rooting + S-off, unlocking or supercid somethings gone wrong that I didnt see, but afaik it all went fine
format sd card, place only the files you will need.. i.e. firmware and your choice of rom.. reboot phone, flash this firmware "Firmware from 3.24.401.1 & 3.25.401.101 RUU" from http://forum.xda-developers.com/showthread.php?t=1412618.. after you flash the firmware, remove the sdcard while the phone is still on, reboot into recovery. Once in recovery, put the sdcard back in, then flash whatever rom you wish to use, just make sure that it supports the firmware, after flashing the rom, remove the sdcard again and reboot phone.. once the phone is booted, turn on usb drive and remove the firmware that's on the sdcard and see how things go.. if things are still messed up, then go for an exchange as at that point, it may be hardware related...
I don't think it has anything to do with superCID or s-off as I can see that you're able to flash any rom to the device.. same with s-off...
Quakeworld said:
format sd card, place only the files you will need.. i.e. firmware and your choice of rom.. reboot phone, flash this firmware "Firmware from 3.24.401.1 & 3.25.401.101 RUU" from http://forum.xda-developers.com/showthread.php?t=1412618.. after you flash the firmware, remove the sdcard while the phone is still on, reboot into recovery. Once in recovery, put the sdcard back in, then flash whatever rom you wish to use, just make sure that it supports the firmware, after flashing the rom, remove the sdcard again and reboot phone.. once the phone is booted, turn on usb drive and remove the firmware that's on the sdcard and see how things go.. if things are still messed up, then go for an exchange as at that point, it may be hardware related...
I don't think it has anything to do with superCID or s-off as I can see that you're able to flash any rom to the device.. same with s-off...
Click to expand...
Click to collapse
Thanks, ill give it ago! the only bit is where yousay after flashing firmware remove sdcard whilst on, then reboot into recovery. The only option I get is to reboot no option to reboot into recovery?
anyway
flashed insertcoin 5.1.4 so will see
in order to boot into recovery after flashing the firmware, power off the phone, yank the battery and sdcard, then put the battery back in and power on with the usual power down + power button with the sdcard still out. once in recovery, you will notice that recovery counts down until the sdcard is back in so slip the sdcard back in, give it a sec, then choose the zip file you're going to flash.. flash the rom, remove sdcard and boot into rom.. slip the sdcard back in one final time.. once booted, go into the sdcard and remove the firmware so that it doesn't keep wanting to update everytime you reboot...reboot once more to make sure all is setup and see how it goes.. I'm sure there are easier ways of doing this, but this is one method I've tried and all worked fine... hope this helped..
Quakeworld said:
in order to boot into recovery after flashing the firmware, power off the phone, yank the battery and sdcard, then put the battery back in and power on with the usual power down + power button with the sdcard still out. once in recovery, you will notice that recovery counts down until the sdcard is back in so slip the sdcard back in, give it a sec, then choose the zip file you're going to flash.. flash the rom, remove sdcard and boot into rom.. slip the sdcard back in one final time.. once booted, go into the sdcard and remove the firmware so that it doesn't keep wanting to update everytime you reboot...reboot once more to make sure all is setup and see how it goes.. I'm sure there are easier ways of doing this, but this is one method I've tried and all worked fine... hope this helped..
Click to expand...
Click to collapse
Still the same, flashed back to 1.17 and did nandroid recovery and it works perfectly in GB oh well, the closest Ive had it working on ics was with Virtuous Inquisition v4.0.0. The problem im going to have returning the handset is that it works perfectly as it was sold to me and if I start going on about installing ics roms etc they are likely to refuse a return.
yay!!! think ive cracked it, well not me but at least I think what ive found what the problem was
Spotted this rom http://forum.xda-developers.com/showthread.php?t=1542192
Thought what the hell, and long story short its worked, not a single issue like before, which leaves me to believe that for whatever reason 4ext recovery wasnt working correctly when flashing firmwares on my phone as when I used it to restore my original backup it worked fine. Installed the rom above that was packaged as a PG58IMG.zip file and it worked great, might try and reinstall clockworkmod and see if that helps as I never actually used it
Fingers crossed its now sorted but so far so good, not a single issue after installing all my apps again
Hi need a bit of help with this one if possible.
start the top..
went to flash leedroids rom..flashed boot image but forgot to pull rom over.
so had various issues getting over in the end had to mess around with recoverys and totally wipe my sd for it to be recognized.
so i solved all this then..now the issue is..of everything i push over..only one rom boots up and installs fine..and that is a cm9 test without sd mounting..so it solves nothing.
any ideas of how to get a rom on there where i can mount the sd..download a rom and put it on..
ill be honest..htc+internal sd card=not happy
ive pushed leedroids..virtuous..utbs rom but nothing.
i tried aokp but it didnt even push.
with these also some get corrupted by a protocol failure..
many questions. currently has cm9 on..but no mounting..so great
Did you already try a factory reset after flashing the stock recovery (e.g. from MoDaCo)?
-
Hi rootrider, yeah i followed a post i found..
basically i used the one click toolkit to flash the stock recovery..then cleared storage and all data etc.then installed clockwork back..it doesnt like the working roms though
cm9 is the only one i can boot up..at least it sees the sd card again in clockwork though
Had your problem as well... I don't remember exactly what I did to get out among many other things (sh..).
Had some trouble as well flashing stock recovery with the one click tool kit. It didn't work as expected. So I did it with adb. Just keep on trying, there is a way out.
-
My next course of action is, to flash the stock recovery, clear everything,reinstall clockwork then install aokp..if its something with the type of rom.maybe that will work..i can mount..get a rom on the sd and resume business as usual..
debatebale whether itll work lol
If this doesn't help get Thor's hammer and flash your appropriate RUU (again).
Easiest method would be to run an RUU and start over again. I see your vodafone UK so try this one
http://dl.dropbox.com/u/69014495/RU..._2_10.23.31501S.10L_release_258386_signed.exe
It also includes the new radio too !
Just relock bootloader before running it, After its finished unlock and fastboot flash cwm..
easy peasy !!
--
thanks people, im running leedroids rom now, seemed my issue was is after pushing the file over i just tried to install immediatley..after a couple of reboots just for the hell of it,untouchables rom started installing...phew..
sadly all my sd contents have gone..very dissapointed with the sd card business!
still least its working again!
thankfully azzle didnt need to go back to ruu
Aye, captain. Glad to read this.
Hi people,
here is stock kernel extracted from One SV k2_u/k2_ul/k2_plc_cl version but with modded ramdisk.
I put this thread into general section but as soon as sources are out this will be moved into Original Development section and it will be replaced by my new kernel.
Features:
- Unsecured kernel
- init.d support
- Persistent ADB enabled
Instructions:
- Run "fastboot flash boot boot.img" command.
- Reboot & Enjoy!
DOWNLOAD for k2_u
DOWNLOAD for k2_ul
DOWNLOAD for k2_plc_cl
Make a nandroid backup first!
Credits:
- old.splatterhand
- eduardog131 for stock k2_plc_cl kernel
Enjoy!
xpirt
Will this help for a 4.2.2 rom?
GtrCraft said:
Will this help for a 4.2.2 rom?
Click to expand...
Click to collapse
Sorry this should be on One SV general section and I reported but anyone moved yet. @Ghost
It's stock kernel for One SV btw.
xpirt
Hi,
Can you mod k2ul version kernel?
@xpirt
Would you be willing to make a tutorial on here as to how you did this, the requirements needed to accomplish it, and what to check for, as well as the changes which must be made for such a modification? I am asking this so many will learn and as well take the idea and possibly grow from it by coming up with even better ideas in the future. Without the knowledge or know how then this will only keep people in the dark and nobody wins from this. You don't have to make a tutorial, but if you were to do so it would be very much appreciated friend.
Sent from my C525c using XDA Premium 4 mobile app
If someone gives me stock k2_ul kernel I can mod it as well.
@Modding.MyMind I modded it with cygwin kitchen, you can unpack any kernel and edit its ramdisk. The file modded is default.prop.
xpirt
Added k2_ul version! @bataya
xpirt
@xpirt
I know you have the mod, but what about write protection for this kernel for those who are S-On?
Sent from my C525c using Tapatalk
Modding.MyMind said:
@xpirt
I know you have the mod, but what about write protection for this kernel for those who are S-On?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I made the module for now.. a stock kernel with write protection disabled will come with my custom kernel too one day, but now I'm busy with something else..
xpirt
xpirt said:
I made the module for now.. a stock kernel with write protection disabled will come with my custom kernel too one day, but now I'm busy with something else..
xpirt
Click to expand...
Click to collapse
No worries man. Handle your priorities .
Sent from my C525c using Tapatalk
Added modded k2_plc_cl kernel, thx to @eduardog131 for stock kernel.
xpirt
Will this let people use rom toolbox to change the notification icons like wifi icon cell signal icon and so forth?
SnakeFist2005 said:
Will this let people use rom toolbox to change the notification icons like wifi icon cell signal icon and so forth?
Click to expand...
Click to collapse
Not this, this is the kernel. To use toolbox a deodexed system + root/busybox should be enough.
xpirt
Experiment went awry!!!! Ended with a nice surprise!!!
So this is a an interesting story. I have tried many ways to finish flashing the OTA's after I have implemented the RUU. None seemed to work. I was missing a key step pull out the firmware.:silly: duh. Im still a very real noob here and learning on my own. And I was on github the other day browsing and searching and there was a put an uncompiled SE supported string for a kernel of our dear phone the PLC. So grabbed and immediatly started browsing reading and learning placing things here and their....I learn hands on, not from stories or guides. Well things quickly went wrong like many of you reading this are thinking and I wound up with a big paper weight hahahaha. No biggie I got 4 different nandroids that I have compiled and the RUU right I am good.
NO SO FAST nandroids wont flash something about error 23 or 24. RUU I ran 4 times deleted re downloaded and ran again nothing. Again I am still not in panic mode I have enough hardware on my computer to makeshift something to get the RUU to download. I dont know how this happened somehow in the midst of my scramble to get my phone back I had put in an old hboot radio and ics boot img. See my phone has never run ics before. So now I was staring at drivers failing cause their is no OS RUU isnt working nandroids wont work. My phone is down and my computer when I take it to work has no internet. I went through my archives and found the data for the binaries and the data for an ics rom but it was bare bones but heck I had no other choice. So I through the old firmware mixed with bits of the newer kernel.
I booted from recovery with adb to oem-78 which I believe is the updater portion of RUU. I ran the the firmware from their I first relocked bootloader before I did this. I did not take the first time/ flush the zip and run it again took like a charm. I then went back to fastboot flashed TWRP 2.6 instead of my normal 2.7 just cause I wanted to booted into recovery no problem. While in recovery I flashed the ICS stock rom like the firmware did not take. No worries ran it again and worked the second time. then wiped cache and dalvic flashed superSU 2.0.2 which was bought from play store and donated for zip thanks btw. and busybox X. booted into bootloader rebooted bootloader like a dozen times and flashed the ICS boot img. twice seems like the theme hear.
K bear with me I know I am long winded. Tried booting into the system after another dozen times rebooting bootloader. finally gave up went back to recovery reflashed ICS rom only once and then did busybox and SU another time for good measure. I did an avance wipe of dalvic and cache this time. booted straight to system and put the phone down came backe 20 min later it was working I played around it was glitch bad but working. I let it be for another 30 min. Came back rebooted a couple times and went to recovery to instantly backup as all mine where now worthless. When I got home I noticed it wouldnt receive wifi signal after playing around I downloaded the latest OTA for the 4.1.2 JB and the 4.5 sense update. Pulled the firmware flashed that after replacing the HBOOT with an old version and then found my other SD card and pulled a bunch of saved stuff off and found a stock JB 4.5 sense rom. flashed like above steps basically to the amount of reboots. lol. I finally got it to boot and within the hour I am running a smooth JB 4.1.2 sense 4+ OS thats what android tuner says my Hboot however says
Unlocked
K2_PLC_CL PVT SHIP S-OFF RL
CID 11111111
HBOOT 1.01.0000< oldest one i've seen lol.
Radio 1.12.00.0208
OpenDSP- v 10.2.0268.0401
eMMC-boot
Feb 8 2013, 16: 29: 40:-1
As u see no line for OS and well no os and no data associated with eMMC just the boot. Everything seems to run way way way smoother now thought even before I started messing around. No lag perfect signal. My call problems gone only thing is my batt percent and my mms but those are pre existing problems I am working on.
My kernel says I am the 3.4 variation. On my phone and in all my apps. Except rom tool box it says I am 3.2
I wrote this hopefully a true dev can take what I did and come up with something amazing that can be used across the board of the ONE SV users.Thanks oh some how my toggle switches all turned orange in bootloader and all my highlited things in the rom turned green dont know how that happened either. :fingers-crossed:
Fant0m3 said:
So this is a an interesting story. I have tried many ways to finish flashing the OTA's after I have implemented the RUU. None seemed to work. I was missing a key step pull out the firmware.:silly: duh. Im still a very real noob here and learning on my own. And I was on github the other day browsing and searching and there was a put an uncompiled SE supported string for a kernel of our dear phone the PLC. So grabbed and immediatly started browsing reading and learning placing things here and their....I learn hands on, not from stories or guides. Well things quickly went wrong like many of you reading this are thinking and I wound up with a big paper weight hahahaha. No biggie I got 4 different nandroids that I have compiled and the RUU right I am good.
NO SO FAST nandroids wont flash something about error 23 or 24. RUU I ran 4 times deleted re downloaded and ran again nothing. Again I am still not in panic mode I have enough hardware on my computer to makeshift something to get the RUU to download. I dont know how this happened somehow in the midst of my scramble to get my phone back I had put in an old hboot radio and ics boot img. See my phone has never run ics before. So now I was staring at drivers failing cause their is no OS RUU isnt working nandroids wont work. My phone is down and my computer when I take it to work has no internet. I went through my archives and found the data for the binaries and the data for an ics rom but it was bare bones but heck I had no other choice. So I through the old firmware mixed with bits of the newer kernel.
I booted from recovery with adb to oem-78 which I believe is the updater portion of RUU. I ran the the firmware from their I first relocked bootloader before I did this. I did not take the first time/ flush the zip and run it again took like a charm. I then went back to fastboot flashed TWRP 2.6 instead of my normal 2.7 just cause I wanted to booted into recovery no problem. While in recovery I flashed the ICS stock rom like the firmware did not take. No worries ran it again and worked the second time. then wiped cache and dalvic flashed superSU 2.0.2 which was bought from play store and donated for zip thanks btw. and busybox X. booted into bootloader rebooted bootloader like a dozen times and flashed the ICS boot img. twice seems like the theme hear.
K bear with me I know I am long winded. Tried booting into the system after another dozen times rebooting bootloader. finally gave up went back to recovery reflashed ICS rom only once and then did busybox and SU another time for good measure. I did an avance wipe of dalvic and cache this time. booted straight to system and put the phone down came backe 20 min later it was working I played around it was glitch bad but working. I let it be for another 30 min. Came back rebooted a couple times and went to recovery to instantly backup as all mine where now worthless. When I got home I noticed it wouldnt receive wifi signal after playing around I downloaded the latest OTA for the 4.1.2 JB and the 4.5 sense update. Pulled the firmware flashed that after replacing the HBOOT with an old version and then found my other SD card and pulled a bunch of saved stuff off and found a stock JB 4.5 sense rom. flashed like above steps basically to the amount of reboots. lol. I finally got it to boot and within the hour I am running a smooth JB 4.1.2 sense 4+ OS thats what android tuner says my Hboot however says
As u see no line for OS and well no os and no data associated with eMMC just the boot. Everything seems to run way way way smoother now thought even before I started messing around. No lag perfect signal. My call problems gone only thing is my batt percent and my mms but those are pre existing problems I am working on.
My kernel says I am the 3.4 variation. On my phone and in all my apps. Except rom tool box it says I am 3.2
I wrote this hopefully a true dev can take what I did and come up with something amazing that can be used across the board of the ONE SV users.Thanks oh some how my toggle switches all turned orange in bootloader and all my highlited things in the rom turned green dont know how that happened either. :fingers-crossed:
Click to expand...
Click to collapse
so are you saying that you flashed this kernel?
what exactly do you want a dev to do? i think, by reading what you said, that what you did was, try to compile a kernel with bits and pieces, and when you flashed it, it didnt work? so you tried to restore a backup that you also 'compiled'(?), which failed as well. you then flashed an older hboot which allowed your update to take.... the downgrade to update has stumped lots, including me. its basically the process of manual updating. these phones are all different because the partitions are in different locations in the device. and certain varients have no sim card slot. the radios are running "different channels" etc...
sorry for continuing off topic..
Thanks for the kernel and all your work
From the beginning.
Unlocked
EVITA PVT SHIP S-ON RL
HBoot 1.14.002
Radio 0.19as.32.09.11_2
OpenDSP v29.1.0.45.0622
eMMC-boot
June 11 2012, 14:36:28
Click to expand...
Click to collapse
I was running a ViperRom my camera light was staying on, I tried everything to get it to turn off. I decided it been a few month it was time to get a new ROM anyways. I tried installing Gummy Nightly's was having problem with the install read about getting a different version of TWRP so I updated to 2.6.3.0 I believe I had 2.1.0.0. Gummy still won't work, so I changed plans and want for the Viper XL Rom 4.2.0 this led to a bootloop not getting past the Viper splash screen. I thought I might as well just with one of my backup. So, i wiped and loaded a backup. This is the problem, it will load up the ROM for about 30 seconds before the icon all appear it will reboot. I've now been working on this for 2 days. I've went through each post and tried the advice each person was given, I've tried to Flash a different Rom, the Viper Rom I had when I had the Camera Light Issue, each time I get about 30 second into the Rom Load and reboot. (One of the ROMs would let me access the SDCARD0 but found a work around that.) I've let the phone sit charged for 2 hours looping. I've turn it off and let it sit charging. The next thing I'm going to try to to downgrade the TWRP. If anyone can give me some advice, something new and different to try that would be great. Thanks!
Cheers
xDrFirefly
talked to one of my buddy and said the downgrade would be pointless so, i'm trying to flash a stock rom at the moment.
When you changed to TWRP 2.6.3.0 was it the official version or the unofficial modified version?
Sent from my Evita
Recovery: Custom TWRP 2.6.3.0 w/selinux support
And what errors did it give you when trying to install Gummy?
Sent from my Evita
The install failed. I tried it multi times, and even d/l it again to see if that would make a difference. Nope.
Here is what i've done so far. I factory reset everything. Found a stock rom flashed it on. For the two hours I used it seemed to work fine. I then flashed CleanRom everytime I would open Ti Backup the phone would reboot. I flashed another ROM, was getting the signal drop snagged the Beastmode Kernel it keep failing everytime I tried to flash it. Factory Wiped EVERYTHING again. Flashed the Stock, then Flashed ViperXL (then went to bed) in the morning still had signal bars, so far had two reboots, one when I was uninstalling apps using Manage apps feature, and another time when I was in the Venom HUB app. But at the moment the phone seems to be working. The battery life is ****. In the 30 mins I've had the phone unplug i've down to 89% and all I did was delete a few apps, and move some stuff to the home screens. Hopefully it will get better with time.
Side Note: To anyone reading this. I got the AT&T HTC XL preorder. I doubt I will ever do that again. In all the years I've been flashing and messing with phone. ( My first phone I messed with was a Sidekick ) I've never had so much trouble as I had with this phone. ( HTC Tilt, Fuze and Tilt 2 never had this kinda problem ) a friend of mine whom waited a year to get the XL has never had any of the problem I've had. Just my thoughts. Thanks and I hope I won't have to be asking anymore question.
When, I have more time and such I'm going to try to flash Gummy. If I get the same error message for it or anything else I will post it here.
Cheers
-Dr FF
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
jacobas92 said:
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
Click to expand...
Click to collapse
I will try this. Sounds like a very logical plan.
timmaaa said:
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
xdrfirefly said:
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
Click to expand...
Click to collapse
Computer always says no for a reason. You need the right recovery installed to flash KitKat ROMs, you also need to check the md5 of every ROM you download before you flash it. What I'm saying is there's no reason Gummy wouldn't install if you have done everything correctly.
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