Okay, so I have downloaded "F1-GB-V3-(ENG)-Signed.zip" (I just installed it now before I read your response without wiping anything or renaming it to "update.zip", because it wouldn't switch on due to the previous ROM update). So I am ready to listen to you guys now and do what you say. So now that I have downloaded this from "XDA-Develpoers", I do a factory reset from Recovery Mode, then install it from Recovery Mode? (But I still can't rename it to "update.zip?")
It's okay, I've finally done it now. I read the instructions on the thread provided. Sorry for any inconvenience (And annoying un-intelligence from me) and thank you so much for all your help.
its ok, whenever changing a rom you must always do a factory reset as the apps/dalvic/system configuration will conflict with the new rom and cause a boot loop
always download roms from the source (always XDA) and make sure you follow instructions to the letter.
you do not need to rename the zip files as you can choose whatever zip you want from recovery
I just went back onto my phone now, and it still has the button problem! I followed ALL the instructions when installing the ROM, and just done a key test on Recovery Mode but it gave me the number 158 all three times... Does this mean its hardware?
What do you mean by so you got that on every button at the bottom you pressed? Am I supposed to press a button while it's in the process of the key test?
I pressed them all more than once but wasn't keeping track, so I went back, started the test again, and pressed them all once, and yes it said that code for every one.
Well, we need to work out why its happening first. I'm at a loss why every rom does that. Its usually something to do with a data restore. Its all well and good wiping before flashing, but if you restore things you are likely restoring the problem which is usually an incompatible setting from apps on other roms, but if this was happening on your original rooted stock rom too....Dunno.
Actually, with my first ROM (The 3 one), it didn't do this at all, but a while after I got the Vodafone ROM, it started... Also, I was looking the topic up on Google before I brought it up here, and some people were saying it's caused by "rogue apps"? (I have NO idea what that is, black-market apps, apps too big memory wise?)
Okay, so what your saying is I should do a factory reset, and leave it as it is for a while, without installing any apps or anything, then if it still doesn't work, it's hardware, and if it does, it's something to do with what I'm putting on there?
Okay, I'll factory reset it, leave it as it is for a while, then let you know the results... Once again, thank you for ALL your help.. It is greatly appreciated.
Okay, I've only left it like it is for a few hours (About 18 and a half), and it's still working! (Round about now is usually where it would mess up, but it hasn't)..
If its only just past the point where the fault develops I would leave it a while longer.
If after a while longer, the fault doesnt return, I would suggest the issue is data related. Do you use titanium to backup and restore? You have to be careful that you only use the "restore missing apps with data" option. Even then we have to unselect some things.
When you finally settle on the rom you like (tell me what it is), go into titanium>Batch>Restore missing apps with data...
Type up (big job sorry) all the apps that are in the list and I will tell you what you need to deselect (the incompatible apps).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.