Jump to content

Orange San Francisco Too many pattern attempts


Recommended Posts

Guest cr32000
Posted (edited)

Hi, can someone help me? The youngest daughter played with the phone until it was locked and asking for a gmail user / password. Gmail has never been setup. I've tried all I can find on the web to get round the lock screen but nothing has worked. The software/firmware on the phone has not been hacked at all. I would be happy to re flash it if that is required. I've looked at what what I need to do for that but I get stumped at the first step. I need to know if it is a Gen1 or a Gen2 but as I can't get onto the phone to install MrPigFish I cant find that out.

Thanks for any help.

Edit: I seem to have posted in the wrong forum, can I move it?

Edited by cr32000
Guest Richard_Arkless
Posted (edited)

all that you can do im afraid would be to start afresh, so you got a choice, either stick with the stock unmodified rom and install clockworkmod recovery, from there factory reset it and you will be able to boot up, from there to avoid having this problem again create and sign into a google account

or my recommendation is to upgrade to gen2 and install a custom rom, this has given my phone a whole new lease of life and possibilities

  1. Update to gen 2 using this(The likelihood is that its on gen1 so you shouldn't need to check)
  2. It will boot up into recovery where you can install a rom, I recommend either cyanogenmod 7 + Gapps or another 2.3.x rom
  3. Once you have installed your chosen rom then reboot, from there create and sign into google
  4. connect the phone back upto a pc (or use the phone's file manager) and delete the image folder to avoid you or your daughter accidentally clicking the button combination to reset it
Edited by Richard_Arkless
Guest cr32000
Posted

all that you can do im afraid would be to start afresh, so you got a choice, either stick with the stock unmodified rom and install clockworkmod recovery, from there factory reset it and you will be able to boot up, from there to avoid having this problem again create and sign into a google account

or my recommendation is to upgrade to gen2 and install a custom rom, this has given my phone a whole new lease of life and possibilities

  1. Update to gen 2 using this(The likelihood is that its on gen1 so you shouldn't need to check)
  2. It will boot up into recovery where you can install a rom, I recommend either cyanogenmod 7 + Gapps or another 2.3.x rom
  3. Once you have installed your chosen rom then reboot, from there create and sign into google
  4. connect the phone back upto a pc (or use the phone's file manager) and delete the image folder to avoid you or your daughter accidentally clicking the button combination to reset it

Hi, I did the update to gen 2 as you recommended. I used the cyanogenmod 7.1.0 rom and the Gapps. All seemed to go O.K. That was until I tried to make a call. It dialed the call fine but the then the screen went blank and wouldn't come back on. The only way I could end the call was by taking the battery out as none of the buttons did anything. Any suggestions?

Thanks.

Guest dirlan2001
Posted

I just don't understand people recommending a ROM that is so complicated and buggy as Cyano... The screenbug has been may times reported and solved. Not only in Cyano, but more . I recommend to give Moldovan a try, smoother and less complicated LOL

:D

Guest hugobosslives
Posted

Hi, I did the update to gen 2 as you recommended. I used the cyanogenmod 7.1.0 rom and the Gapps. All seemed to go O.K. That was until I tried to make a call. It dialed the call fine but the then the screen went blank and wouldn't come back on. The only way I could end the call was by taking the battery out as none of the buttons did anything. Any suggestions?

Thanks.

you need to calibrate the proximity sensor. depending on which nightly/stable build you are using it can be done in different ways. look for an option in settings or an app called zte settings (or similar). Then click calibrate proximity. Don't do anything just expose to reasonably light conditions should work fine afterwards.

I just don't understand people recommending a ROM that is so complicated and buggy as Cyano... The screenbug has been may times reported and solved. Not only in Cyano, but more . I recommend to give Moldovan a try, smoother and less complicated LOL

I don't understand how people like you can say it is "so complicated and buggy". I guess its down to personal preference so I'm not going to say that's completely untrue. I am just going to say that I find cm7 very stable (as stable as any other 2.3 rom). And definitely recomend you try it out (it sounds like you haven't tried it in half a year or so.....)

Guest dirlan2001
Posted
And definitely recomend you try it out (it sounds like you haven't tried it in half a year or so.....)

I tried it out the day the 7.1 stable was out. Did keep it for a week and then turned back to GSF 27, to finally turn to Moldovan r6...I'm not really just ranting, I only talk about ROM's I personnaly tried and tested to form an opinion...

:D

Guest cr32000
Posted

you need to calibrate the proximity sensor. depending on which nightly/stable build you are using it can be done in different ways. look for an option in settings or an app called zte settings (or similar). Then click calibrate proximity. Don't do anything just expose to reasonably light conditions should work fine afterwards.

I don't understand how people like you can say it is "so complicated and buggy". I guess its down to personal preference so I'm not going to say that's completely untrue. I am just going to say that I find cm7 very stable (as stable as any other 2.3 rom). And definitely recomend you try it out (it sounds like you haven't tried it in half a year or so.....)

Thanks. I'm using 7.1 stable. I found it in apps, at the bottom. Seems to have sorted the problem out. I'll see how it goes.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.