Hi,
I have a HTC Sensation XL and have noticed that its starting to slow down a little as apps start to use up more RAM/processing power etc. Obviously with it being a HTC handset it uses HTC sense which presumably uses some of the system resources and is contributing to the device slowing a little, in addition Sense appears to interfere with some of apps functions such as lock screen widgets. In addition to this there are a few bugs with the phone that came about when HTC issued the update from Gingerbread to ICS, these issues include the 3g connection failing randomly requiring a phone re-start as well as the browser closing randomly, the problem is it does not look like HTC are going to update my handset to Jellybean, which I would really like for the Google now feature.
The upshot of all this is that I am considering rooting the handset so that I can a) get rid of HTC sense and thereby hopefully free up some system resources as well as fix the issues the device has around lock screen widgets etc and b) upgrade it to Jelly bean myself so that I can use Google Now etc and hopefully solve the 3g connections issues etc. The thing is that I don't really know anything about rooting so have a lot of questions I need answering before I decide this is the right option for me.
At the moment the handset is on a contract which does not expire until January 2014, after which point I intend to sell it and upgrade to a new handset (am hoping Google will have released the next Nexus handset by then). With this in mind my first question is if I root the handset will I be able to re-set it to its factory defaults, including all the pre-installed apps, settings etc that HTC put on the handset, in 2014 ready for sale or once rooted and upgraded to Jelly bean will it always remain rooted and unable to be returned to its factory settings.
Secondly if I root the handset will it still work with my mobile phone operator (EE in the UK) or will further work be required to make it compatible.
Thirdly what exactly does rooting involve, I presume its a process whereby I download a publicly designed version of Jelly bean and some sort of software to put on the phone and then remove the old software and install the new.
Fourthly what is the quality of the new OS likely to be like, are there reliability issues etc that I need to be aware of and basically will it be worth the hassle.
Lastly given the age of my handset is it worth rooting it in the first place or shall I put up with it until 2014, are there any other ways to achieve my aims such as keeping the current set up but removing HTC sense etc as well as fixing the 3g connection issues and installing Google Now.
Any advice/answers to the above will be gratefully received, as you can probably tell at the moment I clueless about what to do.
Thanks
Ben
Related
Hello,
I am a new user of HTC phones, and bought a HERO after going through this website and reading the posts w.r.t. Android etc.
I have a few queries, which I am sure will appear quite basic to most of you, however, there are quite greek to me. I am in New Delhi, India and bought my phone a week ago.
1.
I have read about a firmware upgrade to Hero phones. However,the helpline here says that there is no firmware upgrade available. The India page on the HTC website also does not list any upgrade. My phone is unlocked, although it shows another carrier's logo in the first screen, but no other issue. My firmware version shows 1.5 and Build no. shows 2.73.720.5. Is this the latest version or is this upgradeable?
2.
There have been a couple of instances where my phone has frozen, and no button has worked. I have had to remove the battery and re-insert to get it to work again. Is this normal? I haven't had a smart phone before so I wouldn't know the actual behaviour.
3.
I dropped my phone from about 3 feet, and it opened up with its battery flying out and a few minor nicks and scratches on the body and not the screen. No other apparent damage, but could this cause performance issues?
4.
Is there a way to sync this phone manually without having to use Google or Windows? Can I directly access the phones contact list and messages etc, like a data stick?
Would appreciate answers.
Thanks in advance.
RK
Hi folks,
So I decided to let my old&trusty TYTN2 retire peacefully and be a backup phone - bought an almost unused HD2. Cool, love the phone. Looks good and is reaaally snappy&fast.
But I'm kind of stirred by its frequent crashing and then getting stuck on white boot screen. It appears on random occasions when the phone has to do some thinking - end call, connect to PC, after inserting PIN, app start. Nothing really intensive going on.
The phone has a custom rom: Elegancia v1.0 Final WWE dating 28.07.2010
Radio version 2.08.50.05, Protocol 15.34.50.07U and the third number displayed on boot screen is "D 2.13.90963 8G"
The problem could be connected to overheating mentioned in a couple of threads, but nevertheless I have some questions.
1. Is there a possibility of the issue resulting from a faulty ROM so a reflash would do the trick?
2. Apart from getting a new motherboard or improving the cooling system described in the thread http://forum.xda-developers.com/showthread.php?t=982454 - are there any other solutions to the issue?
3. If I need to take the phone to the warranty there is a high chance that they won't like the custom ROM job so I'll have to flash a stock ROM to make it look good. Where do I get one?
4. Is there anything else specific I'd have to keep in mind?
zandhorn said:
Hi folks,
So I decided to let my old&trusty TYTN2 retire peacefully and be a backup phone - bought an almost unused HD2. Cool, love the phone. Looks good and is reaaally snappy&fast.
But I'm kind of stirred by its frequent crashing and then getting stuck on white boot screen. It appears on random occasions when the phone has to do some thinking - end call, connect to PC, after inserting PIN, app start. Nothing really intensive going on.
The phone has a custom rom: Elegancia v1.0 Final WWE dating 28.07.2010
Radio version 2.08.50.05, Protocol 15.34.50.07U and the third number displayed on boot screen is "D 2.13.90963 8G"
First thing I would do is update this as it is a older rom, Here is a link to the Elegancia thread if you want to just update to the latest version of that ROM. Also update your Radio to a the 2.14.50.04 or the 2.15.50.14 radio linked in the OP of the thread.
The problem could be connected to overheating mentioned in a couple of threads, but nevertheless I have some questions.
1. Is there a possibility of the issue resulting from a faulty ROM so a reflash would do the trick?
Answered above.
2. Apart from getting a new motherboard or improving the cooling system described in the thread http://forum.xda-developers.com/showthread.php?t=982454 - are there any other solutions to the issue?
Nope, not for the over heating problem.
3. If I need to take the phone to the warranty there is a high chance that they won't like the custom ROM job so I'll have to flash a stock ROM to make it look good. Where do I get one?
Go to htc.com and enter your serial number (under the battery) to get a list of ROMs for your HD2 and download it from there. Also make sure you or on the HTC site for your country or the country the HD2 originally cam from, there is links to the other countries sites on any of the HTC sites. Also make sure you flash it via SD card as this will revert everything at one time.
4. Is there anything else specific I'd have to keep in mind?
Yes If you have a T-Mobile HD2 you can not flash a 2.04.50.xx, 2.05.50.xx, or any x.xx.51.xx radio to it as it will brick a T-Mobile HD2.
Click to expand...
Click to collapse
Hope this helps.
Thanks a lot for a quick answer!
And another question: The phone looks like an ordinary HD2 - non-coloured buttons and no T-mobile signs anywhere. And it was bought in Estonia, albeit imported from Czech Republic - had to DL new soft from czech site. But I'm somewhat puzzled by the Model No in phone identity app: It says "T-Mobile_LEO.."
Now is that conclusive evidence or could it come just from the Elegancia ROM?
How do I make sure if the phone is actually a T-Mo or the ordinary one?
zandhorn said:
Thanks a lot for a quick answer!
And another question: The phone looks like an ordinary HD2 - non-coloured buttons and no T-mobile signs anywhere. And it was bought in Estonia, albeit imported from Czech Republic - had to DL new soft from czech site. But I'm somewhat puzzled by the Model No in phone identity app: It says "T-Mobile_LEO.."
Now is that conclusive evidence or could it come just from the Elegancia ROM?
How do I make sure if the phone is actually a T-Mo or the ordinary one?
Click to expand...
Click to collapse
Sorry for the lag in response her just managed to get back this part of the HD2 forums. If you look in your settings>about phone>hardware information and the flash size says 1024 it is a T-Mobile Leo, if it says 527 it is not. Also I am doing this from memory as I am running Android from NAND so it might be under software information, but i am fairly confident it is in hardware information. And yes it probably says T-Mobile Leo because the Elegancia ROM started as a standard 3.14 T-Mobile stock ROM and then the ROM chief modified the ROM.
OK, the hardware information says that theres 576Mb of RAM and 512Mb of flash. So I guess it's a non-T-mo phone. Thanks!
I'll probably be back with more questions, though
Well-well-well.
Long time no see.
The situation seems to be getting solved soon.
Took the phone to the repairs where they first reflashed it with the original firmware - they had to keep the phone in the *fridge* to do it successfully and avoid overheating.
So it didn't really solve anything and to the mobo change it was - luckily I could cut a good deal and the seller of the phone will pay for the repairs so the thread can be closed as a success story.
Will be back though - boys&toys. Will have to upgrade stuff, y'know.
Hi,
Please forgive me if there is already a thread existing for this, as I am new here.
I have a question regarding my HTC Sensation XL, which is currently running Android 2.3.
I rooted my phone some time after I got it. I'll admit that my knowledge of such things is extremely limited, so I may have done something stupid. Anyway, I used some sort of one-click-rooting program (I honestly can't remember what it was called) to root my device. The root was successful and I was happy with this. However, I found that this caused my phone to show the bootloader menu, whenever I turned it on.
This caused an issue when I attempted to update my phone to Android 4.0. I could download the update, but the installation would be interrupted upon reboot, due to the bootloader menu showing up (or so it would seem).
To fix this, I attempted to unroot my phone using an app called 'Ginger Unroot', which seemed to work. However, the issue with the bootloader menu interrupting the update still occurs.
I'm aware that I've probably done something very stupid by opting for these one-click methods of rooting/unrooting, as many sites seem to suggest different, more complex methods. This is probably a lesson for me not to mess around with things that I don't quite understand.
Anyways, does anyone have any advice on how I may go about either solving or getting around this problem?
Your help is most appreciated!
N.B: My device has recently started turning itself off for no apparent reason, if that has anything to do with the problem at hand.
I have been having this problem pretty much since day 1, I've also searched the Nokia Support Discussions and it seems quite a lot of people are experiencing this. I was actually surprised that my Go-To forum here at XDA doesn't have a thread on it.
My Black Lumia 920 (EE, Phones4U, Unlocked) reboots on average about 5 times a day. Yesterday was probably the worst yet with roughly 8 reboots. That may have been more noticeable to me because I used a SIM which requires a pin though.
What I've noticed:
-The device is roughly 10 days old.
-It has been rebooting an average of 5-8 times a day
-It mostly reboots when idle (so when I'm not using it)
-I've had it reboot only twice while in use when making a call
-I've had it reboot only once when playing music.
-I've only ever noticed it rebooting when it is face up
-Rebooting happens regardless of the SIM (although I have not used it without a SIM at all) (Used both a micro SIM and a SIM cut down to size, used the original carrier SIM and other SIM, no difference to rebooting behaviour)
-I only turn on the radios I need when I need them, so 2G active 100%, 3G/4G, WiFi, Bluetooth, GPS, NFC off for 70% of the time.
-It is not due to battery drain as I usually have about 40% battery at the end of the day.
This has been my experience with the rebooting problem. The figures and estimates I'm giving are not over stating and I've tried giving as much detail so as to try and provide useful information for a solution.
Has anyone else been having this problem?
Has anyone found a working solution?
Has anyone heard or read anything concerning a fix for this?
nope - blue one on AT&T
I'd look at your installed apps, apps enabled to run in the background, etc. It should not be rebooting at all.
I have seen some posts like yours on the internets, but its not a "common" as in most 920s do it problem. Which leads me to think its some issue with an app or apps installed on some phones.
Possible solution
Hi kyrirhcp
I had a similar problem. I reset the phone which bricked it and then used this tutorial to un-brick it:
http://forums.wpcentral.com/nokia-l...after-reset-flash-process-defined-inside.html
The only difference is that I downloaded the "Nokia Data Package Manager" (not sure where from but I'm sure you can find it). This software allows you to download the firmware files directly into the correct folder. You could also look at this tutorial:
http://aydon.wordpress.com/2012/11/29/how-to-flash-your-lumia-920english/
The ROM you want is the EE specific one. It even specifies the colour of the phone. The version number is: 1232.2110.1244.3011
If you reset the device and it does not brick (i.e. freeze up on reformat) then the problem is solved and you don't need to worry. If it bricks (which it probably will) then you need to flash to recover the phone.
God bless
andrew-in-woking
Hi Andrew, thanks for your suggestions but I'm avoiding it like the plague if I'm honest. Resetting my phone and risking a brick, even with your added fix tutorial really doesn't seem worth it. Also I'm assuming that the problem you PM'd me with regarding the loss of some functionality is a result of the fix you suggest. I'm not yet willing or ready to f with my device the same way as I did with my SGNote, even more so since developers haven't yet gotten the experience they have with android. Anyway, i seem to have perhaps solved the problem at least for my device. I changed the regional settings for a completely unrelated matter and I have not since had a single reset or the accompanying massive battery drain. It's now been 3 days. The only other change was that I removed tunein radio an reinstalled it. So it seems that my problem has been solved (fingers crossed, knock on wood, ftou ftou ftou, wearing an evil eye). I hope this helps others with their problems and makes this amazing device useable to those that had this problem.
Sent from my RM-821_eu_euro1_342 using XDA Windows Phone 7 App
Try removing Whatsapp if you've got that installed.
I have had a lot of the same problems. My phone locks up a few times per day. This is the 2nd Lumia 920 I've had. After getting the second with the same problem, I decided to wait for the Portico update that was supposed to address random restarts.
Since then, I've been communicating with Nokia and Windows Phone support on twitter. All they suggest is uninstalling apps, disabling radios, contacting individual developers, and resetting your phone.
I have a hard time wrapping my mind around that. How is it possible for a user level application to take down the whole operating system/firmware?? There are plenty of crappy apps on the Windows Phone Store, I don't think it should be up to me to figure out which is destroying my experience.
I used to root/hack all my old Windows Mobile phones/android phones. When it locked up, it really was up to me to fix it and figure it out!! I chose Windows Phone since it had the locked ecosystem similar to Apple. While that may not appeal to everyone, I have a very busy life and I don't want to spend more time screwing with my phone. It just needs to work! This is my 3rd Windows phone and it's been the worst so far.
Hey bro's just today I got my new HTC one x+ and I had ordered it online so it's an international unlocked phone. The phone is on android 4.1 and sense 4+ (stock and not rooted) so I checked for software updates but it said the phone is already up to date and no updates are available , though I guess HTC has rolled out 4.2.2 sense 5 for one x+ (right ?) . Also, I've noticed the phone stays connected to WiFi and yet the pages won't load, sometime WiFi just disconnects, though the internet is working just fine on my other phone . Further the apps from play store too take a butt load of time to start downloading and often get stuck midway while downloading. So guys would u suggest to get the phone checked up at HTC for manufacturing defects Or have some of you faced similar problems but have rooted and used custom Roms (if so which ?) to solve it. My phone isn't in for hardware warranty and I'm sorta noob at this stuff so please take this into consideration too. I'll be really grateful for your help
My advice will be basic but may be efficient:
Have you tried to factory reset your phone? If you bought a used or refurbished device, this may help.
I'm from Europe and have an unlocked version and can confirm that the update finished rolling out early September + I never experienced any of your problems.
You would also check if you have those download problems on both Wi-Fi and 3g. If so, this may be a hint of some sort.
Sent from my HTC One X+ using xda premium