Database Info

HD2 on Android keeps rebooting/restarting itself..possible fix?

Hi, This is my first time posting so please forgive me for any czar-like posting rules I may have violated. I think that I have found a resolution for hd2 on android rebooting/restarting problems that many of us face or have faced. Before you jump on blaming motherboard like Dear HTC Repair ppl did in my case, please try these steps.
I have recently got my second hd2 and installed Android naturally and almost immediately after setting up the device, I noticed that the phone started to reboot itself. And this happened all day for at least 6-10 times everyday. At first I thought it was a new feature of the latest android roms to fix and upgrade or boost performance. But the rebooting never stopped for a day. Secondly I thought I must have installed it incorrectly and so followed all procedure again from task29 to CWR cautiously but NO LUCK! Then I did multiple searches on xda and other forums and followed every suggestions and possible problems like battery cable/pin straightening, task29....formatting changing microsd card...blah blah blah....no fix!!! Then I called HTC and they concluded that the motherboard gotta be replaced for only $175...yeah ok I got my phone for $150. Someone at HTC forgot to take math in HS.
Anways...long story short try what I did....if you face constant restart issues after installing android...and hope for the best. It won't hurt to try. I am not a developer nor a software/hardware engineer and I don't have any technical explanation for this with fancy acronyms. All I know that it worked on not just one phone but two phones as I bought another used phone on ebay after HTC tried to rob me off $175. And this one too gave the same reboot/restart problem after I installed android.
So, here is what I did and don't ask me why it worked not cuz I don't know....it just what I did and it worked in both phone and never restarted ever again
-DO NOT do task29 EVER...no offense to the developer. If you have done it already then just don't do it again.
-Install/reinstall fresh official stock tmobile WM6.5 rom only. DO NOT install custom rom. Reboot normally and do the minimal setup since you are about to install android on it anyway.
-DO NOT play with Radio versions. Stick to the one official tmobile rom has installed for you. Although I think even if you change the radio it will be ok.
-DO the steps for hspl, magldr113 etc as usual
-Now this is what I think is the crucial part...If you have partitioned or planning to partition your microsd card with cache then DO NOT use any CWR recovery partition with cache....totally avoid 150M-5m cache formats just use 150M...200M....250M etc without cache...again I don't know why but it worked for me.
-Now do a wipe data/system and install the android rom of your choice. It should never restart again. Mine did not!!! GOOD LUCK!
This is what I did when my both phones were starting all day and it worked on both. They never reboot by themselves ever. They both were restarting all day at least 6-10 times. On my first phone I thought the motherboard or may be the battery cable was gone, then went on to get a second phone. The problem was on the second phone as well after I installed android. I was sure that it would be too much of a coincidence that both phones have bad motherboards and therefore started playing with them in various combinations of rom installation procedure, sd card, battery...you name it..then came across this steps and it worked for me. I hope it works for you. Please note that if the problem is hardware then it can't be resolved by doing this.
I hope it works for you. I know how frustrating it is to have a phone that is constantly rebooting on its own all day.
To those who will question my solution...again refer to the previous notes. I did it and it worked on my two phones...and another advice for you.....Sometimes you don't have to know quantum physics to tie a secure knot that saves life

It would be much more helpful if you could post a link to a recovery without cache as you posted. I cannot find one thus far.

What instructions are you reading for installing the Android OS? I don't think I saw task29 anywhere on the instructions I saw. I have the FR0X7 version, and mine does this constantly & then drains the battery, so I am desperate for a solution.

Two very annoying issues with this phone

Rooted, CM 7.1.0, T-Mobile
Not sure if these are CM issues or HTC's crappy hardware issues, but...
1. When I try to turn on the screen using either the top button or bottom trackpad button, the screen will flash on for a second and then go off again. It will do this two or three times until the screen stays on at the lock screen. Didn't do this before CM, but also didn't start until months after I modded to CM.
2. When using the on screen keyboard(in vertical mode) sometimes it's like the touchscreen is responding very slowly to my taps and CERTAIN KEYS will not work at all. So I'll be typing and the keyboard will be kinda sluggish and suddenly I'll notice that none of the a's I'm hitting are registering. I'll hit the area of the screen over the "a" key and the surrounding keys will register but not "a". I will usually have to turn the screen off and then back on before it starts working again. I think it did this the first time before I modded, but can't quite remember.
Anyone else having these problems?

The first problem has happened before on some roms.
I don't recommend using CM 7, its old, outdated and hasn't been fully patched.

I had that same touch keyboard issue with my HTC EVO shift and my HTC Inspire....an of course all my phones were on different ROMS
Sent from my myTouch_4G_Slide using Tapatalk 2 Beta-4

The first issue... are you oc? If so how much? Really no need to oc this phone. Also, it could be a wake issue, if you are underclocked to much, there is a minimum amount that sometimes has to be higher on some phones than others.
It seems to me these could be kernel issues.
Sent from my HTC Vision using xda premium

mrbmg said:
The first issue... are you oc? If so how much? Really no need to oc this phone. Also, it could be a wake issue, if you are underclocked to much, there is a minimum amount that sometimes has to be higher on some phones than others.
It seems to me these could be kernel issues.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Unless CM over or under clocks by default, then no changes in cpu.

You should run the HTC stock software for a few days or a week to see if the problems you have are persistant across ROMs, or something specific to your current software package.
Just a thought.
Sent from my Bulletproof_Doubleshot using xda premium

Blue6IX said:
You should run the HTC stock software for a few days or a week to see if the problems you have are persistant across ROMs, or something specific to your current software package.
Just a thought.
Sent from my Bulletproof_Doubleshot using xda premium
Click to expand...
Click to collapse
Yeah I've thought about doing that, but I also use my phone for business and switching between roms is kinda disruptive, so I haven't done that yet. Hoping for more feedback from others.

Preparing for backup
Return to Contents Page - doubleshot Developers Reference
Backup Guide
AviatorJud said:
Yeah I've thought about doing that, but I also use my phone for business and switching between roms is kinda disruptive, so I haven't done that yet. Hoping for more feedback from others.
Click to expand...
Click to collapse
Yea, that is something that impacts us all. I could get a lot more dev done if I didn't have to have my plan phone set and ready a specific way each shift to be able to do my job the way i'm expected to.
Best bet would be to wait until you had a day or two off, maybe a weekend or something and when you finish with your obligations before that free time starts:
-try to have near to a full battery or a full one waiting.
Installing a new ROM always works better with a full battery on install, so if you can already be at that step you can start right away instead of waiting for it.
-Make a clockworkmod backup of your device as it sits, and copy that backup to a computer somewhere.
-Get all the ROM files you need to re-install it in a folder with that clockworkmod backup you just made. When you go to put the phone back together to go back to work, if the backup doesn't work for some reason you can at least install fresh and go from there.
-On that note, backup all your apps too. If you do end up having to re-install your ROM you are running right now, being able to install all the apps right away again off the sdcard saves a lot of time and hassle.
Make sure to get those apps backed up to a computer too.
-backup all your contacts. Export everything you can to the sdcard, and then copy that to the computer too.
-Make sure you have all the passwords and account names you need for anything you have installed. (Gmail(s) - Games - accounts tied to apps or services you use)
If you do have to reinstall everything, and you use internet services like dropbox or an internet faxing service you don't want to have to track down those logins if you don't type them often. Make sure you check all your apps and write them down ahead of time.
-Lastly, since you are on CM7, use titanium backup to backup everything and copy that also to the folder on the computer. The word backup in the computer industry is synonymous with redundant, and if it's not you're doing it wrong.
The reason why I said to copy all these backups off the phone and onto a computer is because if something catastrophically bad happens to the phone then what?
By catastrophically bad I mean you format the sdcard by mistake on a factory reset while you're playing with different ROMs - what then?
If you do need the device for work, and you are serious about trying to test the errors against being a phone-specific hardware issue or a software issue with the ROM you are using, then jogging your process by putting this all out there might help you get started.
When you get that downtime, you'll know ahead of time so you can prepare, and then when it hits you have an immediate plan of action to put into place to maximise the time you get for testing.
Also, have the ROM you want to put on it ready to go, and if possible alternates to that - so research the 3 software versions available from HTC for the device.
Also become familiar with this process:
Restore to stock
...maybe download all 3 software versions before your free time hits so you have them already. If everything goes sideways you can always use one of them to restore the device.
If you are S-OFF you have nothing to worry about for doing any of the software updates unless you manually re-lock the device, so just don't do that and you'll be fine.
If you are S-ON speak up and i'll lay out your possible headaches along the way and what we know about them if someone else doesn't first.
If you have prepped before the free time hits:
1 - passwords/account info written down and at the computer you'll be using...
2 - all software packages (restore files, roms, anything else...) that you need downloaded and on the computer you'll be using...
3 - all the apps you use backed up and on the computer you'll be using...
4 - any media like pictures and music or anything else backed up to the computer you'll be using...
5 - a full battery or close to ...
...you are still looking at almost an hours worth of backup time to do the clockworkmod backup, titanium backup, transfer them to the computer, and then you might run a little over that time when you test the clockworkmod backup.
( you always test the backup - the only thing worse then not having a backup is having a corrupt one you thought was good )
...which cuts into your time testing the other ROM enough as it is, but if you aren't ready to do it like this it will take significantly longer.
Since you'll know when the time hits getting a majority of the media, pictures and user generated stuff plus most (if not all) of the apps you use backup up the day before helps cut down on a lot, but that hour is still lost to making a way of putting it back together again.
You also need to leave yourself a solid 4 hours to put the machine back to the way it is before you started on the other side. Again, on install, you want to have a full battery so plan for that too.
4 hours gives you enough time to get everything slapped together from a fresh CM7 install and manually doing all your apps and setting up the phone for work, if the CWM backup fails for some reason and you have to start over.
I just want to see everyone have their phones running right, and if it's a hardware issue then you should get it repaired, if it's a software issue then you should seek a solution - but the quickest way to a result, and the one for your issue, is to directly test it yourself.
Since you sounded like you came to that conclusion too, your only issue now is squeezing it into a time slot you can get so don't hesitate if you have questions on the processes involved.
Edit - also:
If you have multiple MicroSD cards you could use for this, then you can save a lot more time.
You could take the one you have in there now out, and put it to the side so that when you installed your work setup again the memory card and all it's stuff is right there.
Then you could take different memory cards and have them pre-made to what you need, so as soon as you are done backups you power off and swap memory cards.
First one you swap in has the PG59IMG.zip restore file (and nothing else) renamed that way and ready to go, so when you power back on to hboot that installs itself and you save the time spent copying that over before you can install it.
When that finishes, you are back to stock and ready to go, and you didn't change any of the info on your work sdcard.
Something to think about, if work stuff is that important that's what i'd do (and what I do myself, so thought to add it)

Wow Blue, thank you for taking the time to respond. I think I will have some time this weekend to give this a shot. I am S-OFF. And you're right, as long as you plan everything ahead and allow for the time to get set back up, it's not too bad. I'm just trying to decide what rom to try switch to. I really hate sense, so I don't really wanna go back to stock. Wish there was a good stable vanilla to use. Any thoughts?

Oh and if I want to update to the newest radio, which is listed in your "return to stock" thread and then perhaps use another custom rom, like bulletproof, will that radio stick? Do roms not ever update the radio? I just noticed that I am on the original one for the doubleshot, which came out last june.

AviatorJud said:
Oh and if I want to update to the newest radio, which is listed in your "return to stock" thread and then perhaps use another custom rom, like bulletproof, will that radio stick? Do roms not ever update the radio? I just noticed that I am on the original one for the doubleshot, which came out last june.
Click to expand...
Click to collapse
I don't even know what radio I'm on that's a sad thing...but yeah once you update your radio, no Rom will overwrite the radio unless it somehow has one in it you know...
Sent from my myTouch_4G_Slide using Tapatalk

AviatorJud said:
Wow Blue, thank you for taking the time to respond. I think I will have some time this weekend to give this a shot. I am S-OFF. And you're right, as long as you plan everything ahead and allow for the time to get set back up, it's not too bad. I'm just trying to decide what rom to try switch to. I really hate sense, so I don't really wanna go back to stock. Wish there was a good stable vanilla to use. Any thoughts?
Click to expand...
Click to collapse
My pleasure, it's what makes XDA work - people taking time to share what they've learned so others can benefit from or add to the knowledge.
If you are trying to bug-check, honestly, the stock official ROM is a good one to use. It's not something you are so much doing to enjoy the phone, as much as to check on a specific aspect of it.
Further, you are already halfway home on putting the phone back to factory settings if it is a hardware issue, so then you just have to S-ON it and send it in for repair - though you probably won't get it back with S-OFF ability, you will at least be able to unlock it.
Just from directly developing things for the device, and having to go through these testing procedures time and again, I try to set the process up to keep moving, so by going to bone stock if it is broken you already have taken steps to make it what it has to be to send it in, the next looming goal if you aren't going to restore to your work setup.
AviatorJud said:
Oh and if I want to update to the newest radio, which is listed in your "return to stock" thread and then perhaps use another custom rom, like bulletproof, will that radio stick? Do roms not ever update the radio? I just noticed that I am on the original one for the doubleshot, which came out last june.
Click to expand...
Click to collapse
This was just answered above me, but you can always go back to previous radio installs if you are S-OFF...but only if S-OFF.
I've run Bulletproof on the new radio and it runs fine, so doesn't matter either way on that one - other ROMs you'll have to ask the author.
ROMs can update the radio, or only work on specific ones, but for our device I don't think it's been an issue yet, pretty sure everything works with everything on that part.

Is my Samsung Infuse DEAD?

Hey, guys. Hoping some of you experts can help me diagnose what's wrong with my Samsung Infuse. I bought it off Craigslist at the end of May, and the guy had the phone with the original screen protector on it, with the original case and all accessories, so I had no reason to believe it had any problems. He told me the phone was already rooted & unlocked, which I wanted since I signed up with Straight Talk. I used it for June & July and had a host of problems, so I put on the CM10 ROM last week to see if it helped. It didn't. Here are the problems I continuously encounter:
1. When going to unlock my phone with a pattern, once in awhile it won't detect my finger-presses. Sometimes nothing shows up at all, sometimes one of the dots will highlight as I pass over it, but it won't draw. Eventually the screen turns off, and I turn it on and try it again. Usually it ends up working.
2. The battery dies much quicker than I expect it should. I tried running JuiceDefender and not running JuiceDefender, and it doesn't seem to make a difference. Even without using my phone much for anything, even with the screen off, the battery will run out before the day is out. It's like if you were driving and had a hole in your tire... seems like some sort of a leak.
3. The cell radio seems flaky. Sometimes I won't get texts on time. A lot of the time I can't access any data, which is very important as I use Google Voice for lots of my texting, so I send a text and it won't go out. Loading web pages or reloading my email shows that it is a data problem.
Those are the primary problems, and I suspect that somehow they are all related. I'm not sure if the Craigslist guy sold me a lemon, or there is some other problem that came up. I've tried multiple ROM's and disabling every app I can think of. Can anyone think of anything that would cause these problems & any way to fix it? Or do I just own a broke phone that I have to throw in the garbage?
Thanks in advance for reading!

a whole slew of problems can lead to a whole slew of possibilities for your issues.
first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.
second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.
dd you read OP and follow to a tee??? again HUUUUGGEE problems.
the "never fail" here.....READ READ READ. feel confident as to what you are doing and follow steps one at a time. UNDERSTAND steps one at a time.
first thing that never hurts.....return to stock and start from scratch.
"super everything thread" under development.
Odin "stock-root & modded 3e rcovery.
follow all directions TO THE TTT.
if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.
i know almost everyone else here is more of a expert than i am, but i do believe that is where they will tell you to start
good luck and be sure and thank the experts

captemo said:
first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.
second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.
dd you read OP and follow to a tee??? again HUUUUGGEE problems.
first thing that never hurts.....return to stock and start from scratch.
"super everything thread" under development.
Odin "stock-root & modded 3e rcovery.
follow all directions TO THE TTT.
if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.
Click to expand...
Click to collapse
While I have no idea what you're getting at by your Straight Talk comment, as ST is little more than AT&T service that's sold through a 3rd party at a discounted rate, the fact that he's using ST may be part of his problems, at least in regards to the network issues. I'm also having an unbelievable amount of data issues on ST. ST is having some network problems that are affecting a decent amount of customers who are on their AT&T network.
One thing that the OP may want to try is this: Download DNS Changer from the Play Store, and change your primary and secondary DNS to OpenDNS1 and OpenDNS2. Or try different settings, as there are a bunch that are available. That has made at least some difference with my data connectivity issues.
Based on my own experience, having tried to go to JB directly from GB, is that if it's going to affect your radio, it's likely to completely wipe out your EFS data so you won't have ANY cellular or data networking capabilities. As stated, that's simply based on how it worked out for me, and there could easily be other side-effects that just didn't happen to show up for me.
I agree with returning completely to stock UCLB3, with the GB bootloaders. Then flash Entropy's 4.4.2012 Kernel, which will also install CWM Recovery. I'd personally reccomend Heimdall, as it seems to be somewhat simpler. Detailed information on returning to stock via Heimdall can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=heimdall+uclb3
If you use it, be sure to thank qkster for making it available. He's probably the most helpful person you're likely to find on this forum, especially where us noobs are concerned.

I would take it back to stock and start all over.
Here is a very helpful thread.
http://forum.xda-developers.com/showthread.php?t=1700416

I agree with parrot head. When issues arise go back to stock. That's the best part of our phones. They are damn near impossible to really mess up. Just have to be ware of bootloader flash going wrong. If you got your gb rom from keis your good to go though.
Sent from my SGH-I997 using xda app-developers app

Appreciate the response, guys. I guess it doesn't hurt to try to start from scratch... AGAIN! It just seems like I'm putting an awful lot of hours into putting new ROM's and bootloaders on this phone. Going to be especially frustrating if I go through all the steps and it still doesn't fix my issues, which would mean my phone is broke. Oh well, guess I have little other choice.

All of the issues sound related..
It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..
Good luck!

drnecropolis said:
All of the issues sound related..
It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..
Good luck!
Click to expand...
Click to collapse
Yes, the flashing process isn't that long, it's getting back my phone to all of my customized settings that ends up taking weeks. Home screen icon positioning, logging in to every app, system settings, etc.

Didn't create a backup?

drnecropolis said:
Didn't create a backup?
Click to expand...
Click to collapse
I've always created backups with Titanium Backup, but when I restore the apps, a lot of them ask me to re-login or re-verify myself.

Thanks for the advice guys.
Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?
Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?

veeRob said:
Thanks for the advice guys.
Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?
Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?
Click to expand...
Click to collapse
Are you still using the Trebuchet Launcher that comes built-in to the JB ROM? If so, that may be part of your lag problems. I just use ADW EX launcher. Here's an excerpt from the Paranoid Android JB OP:
******* EVERYONE: If you experience a sudden lag for no reason, IT is due to Trebuchet. GOOD NEWS though... From reading the log cat on my end, there is a very simple fix... Go to settings -Launcher - Homescreen - And Check "Resize any widget" and you are good to go! Instantly fixes the lag problem that a few have been experiencing. I have located the source code that needs to be changed and this will be enabled by default on future builds. ********
Click to expand...
Click to collapse
As far as the GPS goes, I think Samsung just used ****ty receivers in the Infuse. My GPS isn't quite as bad as yours seems to be, but it's nowhere near as accurate or reliable as the GPS chipset in my crummy little Optimus V.

Reverting back to ICS?

Hey.
I'm on Orange in the UK and recently got promteped to download the new Jellybean software. I'm not a rooted user and don't really want to go down that root.
The new firmware has made my device laggy, the home and back buttons now have a slight lag when I press them and the keyboard is absolutely shocking when I type. I'm on whatsapp pretty much all day and its now making me have loads of mistakes when I type which I didn't before.
I've installed the keyboard app that everyone highly rates, Swiftkey I think it's called but it's still laggy.
I've deleted the keyboard data and restarted the phones loads of times and it's still there.
Basically I just want to go back to how it was before, is there a way I can without having to delete all apps and start my phone again or without having the phone rooted?
Cheers for any helpful replies.
Dan.

dann2707 said:
Hey.
I'm on Orange in the UK and recently got promteped to download the new Jellybean software. I'm not a rooted user and don't really want to go down that root.
The new firmware has made my device laggy, the home and back buttons now have a slight lag when I press them and the keyboard is absolutely shocking when I type. I'm on whatsapp pretty much all day and its now making me have loads of mistakes when I type which I didn't before.
I've installed the keyboard app that everyone highly rates, Swiftkey I think it's called but it's still laggy.
I've deleted the keyboard data and restarted the phones loads of times and it's still there.
Basically I just want to go back to how it was before, is there a way I can without having to delete all apps and start my phone again or without having the phone rooted?
Cheers for any helpful replies.
Dan.
Click to expand...
Click to collapse
If you used ota update to jelly bean, I'm afraid the only way to get to ICS is to get rooted.
Sent from my HTC One S using xda app-developers app

Does OTA stand for over the air? If so, then yes I did it over wifi when the notification popped up the other day.
I ended up bricking my Samsung Galaxy S last tiem I tried rooting and i'm not really in a situation where I'd like to try it again. Pretty heavily reliant on my phone lately.

dann2707 said:
Does OTA stand for over the air? If so, then yes I did it over wifi when the notification popped up the other day.
I ended up bricking my Samsung Galaxy S last tiem I tried rooting and i'm not really in a situation where I'd like to try it again. Pretty heavily reliant on my phone lately.
Click to expand...
Click to collapse
It seems strange that your phone would be laggy from an actual OTA update. Swiftkey is a great keyboard and is my preferred one actually.
As far as your problem. You might be able to factory reset your phone via the bootloader. However, it may reset to the latest update and not actual factory version. I'm not sure. This would delete your apps and all that though.

joviansky said:
It seems strange that your phone would be laggy from an actual OTA update. Swiftkey is a great keyboard and is my preferred one actually.
As far as your problem. You might be able to factory reset your phone via the bootloader. However, it may reset to the latest update and not actual factory version. I'm not sure. This would delete your apps and all that though.
Click to expand...
Click to collapse
He's phone is not rooted, so he's phones bootloader is locked.
Just maybe give a JB a few days. I think that is really good. Or it is not worse then ICS IMO.
Sent from my HTC One S using xda app-developers app

I have just checked my internal data and I am right on the limit, I've noticed before that has caused lots of lag.
Currently transferring 2.5gb of photos back to my computer to free up some space and see if makes any difference :good:
Will get back to you. Thanks.

Nope. Made no difference. Looks like i'll just have to suffer!

Yes the only other solution for you involves rooting. It is possible to go back to ICS by rooting your phone, going through a bootloader downgrade, hexediting a particular partition, then running an older compatible RUU... Its all possible, but requires some time to understand and do. And definately requires a few wipes of phone data in the mean time (which can be backed up through titanium and custom recoveries).

Thanks for a detailed reply.
Really frustrating as it's supposed to make things better but in turn has pretty much ruined my previously quite enjoyable experience with the phone! Nice one HTC haha.
This might sound stupid, i'm not really in the know, but if I rang Orange / HTC, would they be able to supply me the older update over the air?

AKToronto said:
Yes the only other solution for you involves rooting. It is possible to go back to ICS by rooting your phone, going through a bootloader downgrade, hexediting a particular partition, then running an older compatible RUU... Its all possible, but requires some time to understand and do. And definately requires a few wipes of phone data in the mean time (which can be backed up through titanium and custom recoveries).
Click to expand...
Click to collapse
Only need to do that if you want to downgrade hboot. All you have to do is root and flash a rom, I have JB radio and hboot and run ICS Trickdroid 8.1.0.

Yes I was talking about a full downgrade including older firmware. Shadow is correct that you can still run ICS ROMs on JB firmware. That still requires you to root your phone,etc. But it's not that hard to just flash an ICS Rom and corresponding kernel if jb is not your cup of tea. I too have some firmware from JB, such as radio and wifi but am on viper 1.2.1 now. But a full rollback as I explained can be done, but is more technical.
But its all about rooting your phone! Do it anyways! Its fun! The world without a warranty can be scary at first, but also liberating.
Sent from my HTC One S using xda premium

[Q] Back to Stock

Please forgive me, as I have not searched the forum extensively for an answer, but I'm in a bit of a time crunch as I am leaving on a trip tonight and need to get back to some semblance of a working phone.
Some time ago I flashed some rom (I think Paranoid Android; I don't remember. I liked it enough to keep it, then I didn't worry about it again after that.) Little by little it started getting slower and buggier, but for the most part it worked fine, so I ignored it. For the last couple of weeks it started losing signal and data constantly, with no change to the phone. I kind of just lived with it because I could usually restart my phone and I would regain signal, but as of a couple of days ago, it would just drop off and not come back until it wants to.
I had the day off to prepare for my trip, so I decided I would try to go back to stock; there's almost nothing that I do that requires a custom ROM and I had no data issues on stock, nor does my wife on her Note. I looked around for a bit for instructions to restore my phone, and found some, but out of the handful of pages I went to, each one had at least one link that was dead, rendering the method useless, to me, a layman, at least.
I then decided I would just find a Stock Rom, thinking that might be the next best thing. I found Clean Rom on here and decided to try to flash that. I made a backup of my system, wiped everything, and then flashed it. Except something is wrong with the zip and keeps giving me an error message. I then tried to restore my back up that I had just made to try something else, but something happened to that, and it also wouldn't open. I tried the backup before then (quite old, as I haven't done any tinkering with my phone for quite some time) and it worked, but it tells me that my sim card is disconnected, so I have no data or signal. As it is an old restore, I'm not sure what the name of the ROM is, but I can provide all of the information needed, if someone needs that to figure it out.
Anyway, long story slightly shorter: I need to fix this today, and like as soon as possible. I will give ten dollars, count them TEN DOLLARS, to the first person who can provide a set of working links and very straightforward instructions as to how to get back to stock (or if there is a good working ROM that will give me FULL functionality with no flares that would be easier to do. Easy and fast are the key components to this request). I'm not dumb, but I am no longer immersed in the lingo of this community, as it has been a few phones back that I really cared about actually experimenting much with my phone, so non-technical language would be nice. I know what flashing and wiping means. Most of the rest, probably assume I don't.
Thanks.

Your best (easiest) option is probably to flash another stock ROM, or stock-ish ROM. There are quite a few options in the Android Development section. There are a couple of stock rooted at&t ROMs in the first couple pages, also a stock rooted Telstra ROM.
You didn't mention which carrier you're with, whether your phone is branded, or any of your important details, like your firmware/hboot details and whether you're s-on or not. If you wanted to go back to completely stock, I'd need to know those details. Going completely stock can/will be a longer process though.
Sent from my Evita

Okay, I'll try another one. I'm not sure why Clean Rom didn't work, but if another one or two don't work I'll come back here and I'll have you talk me through getting back to stock and I'll throw you a digital Hamilton.
Thanks.

Well, I tried another couple of ROMs. They installed correctly, but it says that I have no sim card, so I still have no signal. Maybe I some how deleted my radio when I did a system wipe while trying to install one of the ROMs? I'm not sure.
Anyway, for "more details" I'm on AT&T, I'm not sure what you mean by branded, but it's the HTC One X, the current ROM is 4.1.1. I haven't done S-On/S-Off, or anything like that other than unlocking the bootloader a long time ago. The kernel version says 304010-g240d4d5, the baseban version is 0.17.32.09.12_10.86.32.08L The Build number is 3.17.707.1 CL134054 release-keys.
I'm not sure which of that information is relevant or not, but that's everything I can tell you.

Never mind that last post. When I said in the first post that I'm not dumb, apparently I lied. My phone fell off a table this morning, and I guess it knocked the sim card loose, but it coincided with doing the factory reset stuff, so I thought they were connected. I pushed it back in, restarted, and now the stock ROM I'm using works great.
Thanks/Sorry!

Well, it turned out to be an easy solution (Occam's Razor FTW yet again).
But this thread made me think . . . why the heck does it seem so many people lately flash ROMs without doing a nandroid first? Its a no brainer to me. If you are trying new ROMs, and not sure how they will perform, why would you not give yourself an easy way to simply revert to your last known good config?

I couldn't agree more, but there's plenty of not-so-smart practices on here, so I'm not at all surprised.
Sent from my Evita

Yea. Nandroid ftw
Sent from my HTC One using Tapatalk 2