Related
all the viperx version reboots while receiving calls! but sometimes it wont reboots....
i've changed it with other rom problem solved,but i love viperx more.... anyone know how to fix it?
Which one are you on now, the JB ? And if you are using the aosp lockscreen mod in the venom tweaks....turn it off and use the standard lockscreen. Might solve your issue
Also Make sure you have deleted the OTA update file from downloads folder.
Apparently recovery goes hyper if you dont (according to viperx thread )
A noobs solution
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
webDing said:
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
Click to expand...
Click to collapse
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Mr Hofs said:
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Click to expand...
Click to collapse
Wow, 3.7.0 (my version) is very old...well at least I didn't post a stupid question, just a stupid answer...
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Mr Hofs said:
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Click to expand...
Click to collapse
No, that was no sarcasm, I'm completely new to rooting phones and I thought progress was very quick and that my version had become obsolete very fast, or that I downloaded an old version.
I still have the problem, well not after disabling the setting...
I did a full wipe.
...but I flashed an old version, noticed my mistake, and then flashed 3.7.0.
The problem is that I know I did a full wipe before flashing the old version, but I'm not 100 per cent sure that I did it the second time. It sounds like missed it. So starting all over again would solve my problem? No short cuts?
Sorry about the misunderstanding!
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Mr Hofs said:
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Click to expand...
Click to collapse
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Hmm buggers, i can't really help you on this because i can't reproduce the reboots. Weird ! But at least thanks for testing
webDing said:
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Click to expand...
Click to collapse
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
webDing said:
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
Click to expand...
Click to collapse
I’ve been a Beta tester for a an American software company during a period of 7-8 years and I’ve written some simple plug-ins for their web design software. So, I tried to use that experience to do some testing and trying to minimize the number of factors that could trigger the problem.
What I did was a factory reset, a wipe and then I installed 3.7.0.
Before installing any apps, launchers and whatnot, I tried running the phone with both pin code and Viper screen lock enabled.
The result was the same every time.
I then tried to enabled the two settings in different orders, first pin code, then Viper and vice versa, but to no avail.
My conclusion, whatever it’s worth, is that it’s easy to get a problem when two pieces of code are trying to manage the same event. Maybe it’s possible to find the line/lines in the code that might trigger the conflict..?
…or maybe Viper just don’t like Sweden/Swedes?
Well, with a little (bad) luck maybe some other people run into this problem, but there might be very few of us who use Viper in this type of configuration…
I don’t think I can add anything more than this, so I’ll leave this issue in the competent hands of those who wrote Viper.
Thanks!
Hello there,
I'm very new, so apologies if I'm posting in the wrong forum, or if there's a more appropriate place for this quesion!
Here's the thing... In an attempt to root my Sony Xperia C1905, I was trying to revert my firmware to a previous version of Android (4.2, I think). Anyway, something happened and things didn't work out, so I re-flashed it with a version of 4.3 that I downloaded from somewhere (I don't know where, but the default language was set to German!)... Thing is, when I turn my phone on, I get stuck in a boot-loop (pretty Xperia colous) for about 3-5 minutes until it gets to the main screen.
I have tried things like using the Sony PC Companion to repair it, but to no avail. Is there some other way I can fix this, or revert it to its original firmware, without this stupid boot-loop?
Thanks for reading!
TheStudent said:
Hello there,
I'm very new, so apologies if I'm posting in the wrong forum, or if there's a more appropriate place for this quesion!
Here's the thing... In an attempt to root my Sony Xperia C1905, I was trying to revert my firmware to a previous version of Android (4.2, I think). Anyway, something happened and things didn't work out, so I re-flashed it with a version of 4.3 that I downloaded from somewhere (I don't know where, but the default language was set to German!)... Thing is, when I turn my phone on, I get stuck in a boot-loop (pretty Xperia colous) for about 3-5 minutes until it gets to the main screen.
I have tried things like using the Sony PC Companion to repair it, but to no avail. Is there some other way I can fix this, or revert it to its original firmware, without this stupid boot-loop?
Thanks for reading!
Click to expand...
Click to collapse
Please refer to this thread as it will tell you how to flash .ftf files manually. Also, make sure that you tick wipe data and wipe cache. This is probably the source of your bootloop problems. Have a good day, feel free to PM me if you need more help.
Wait, buddy i might be wrong here but did you say that it goes to the min screen after the bootanimation ( pretty colours). If so, then that isnt a bootloop. A bootloop is when your phone stays on that bootanimation and never loads up, it's also called a soft brick. As gamer649 above me said, you might wanna check out that thread to know how to flash ftfs manually.
Thank you both so much for responding so quickly! I shall indeed check out that thread posted by gamer649 and hope that solves the problem (If not I shall report back.)
Thanks again!
paper13579 said:
Wait, buddy i might be wrong here but did you say that it goes to the min screen after the bootanimation ( pretty colours). If so, then that isnt a bootloop. A bootloop is when your phone stays on that bootanimation and never loads up, it's also called a soft brick. As gamer649 above me said, you might wanna check out that thread to know how to flash ftfs manually.
Click to expand...
Click to collapse
Ah yeah, you're right, it's not a boot-loop in that case because it does indeed load up after a while, my mistake!
Hello XDA, this is my first post, this comunity is awesome and helped me a lot for a couple of years now.
there always seems to be a solution to everything!
but now i realy ****ed up. i accidentaly checked the wrong thing on the so called "smart phone flash tool"
i klicked firmware upgrade instead of download only.
is there any way so rescue my phone? thank you very much in advance! :crying:
here is a screenshot: (i cant paste link because i am new):crying:
I'd better let someone more qualified answer your query but I'm pretty sure your situation can be recovered easily. What happens if you try to reflash the firmware again with the correct settings? These phones are pretty hard to brick!
charliepie said:
I'd better let someone more qualified answer your query but I'm pretty sure your situation can be recovered easily. What happens if you try to reflash the firmware again with the correct settings? These phones are pretty hard to brick!
Click to expand...
Click to collapse
there probably is SOME way to fix it, i am sure, but the phone does not even boot into recovery.
Mediatek phones are hard to brick, haha
It is PROBABLY going to give a headache in order to find the needed files, flash the stuff again and etc using the proper way, but PROBABLY your phone will relive again. Try rooting and installing Eragon after a full wipe, if that option is available.
You may look here:
Bricked P8000
This may help.
I was in the same state when I accidentally flashed a the wrong logo.img file. I fixed it by doing a format on flashtool>stock rom>custom recovery>custom rom again!
abubakar486 said:
I was in the same state when I accidentally flashed a the wrong logo.img file. I fixed it by doing a format on flashtool>stock rom>custom recovery>custom rom again!
Click to expand...
Click to collapse
hi, thank you; but my phone does not even boot. it gets recognized by the pc though
New problem
OKAY now i got everything working so far. but there is a new real big problem. it has some kind of imei error so it doesnt let me use data on the way
how can this be fixed? i mean, i have the correct imei s right here whith me.
thank you in advance.
Data is turned on under data usage in settings menu and the APN is correct? What does the error message say and can you make calls/SMS OK?
FIXED
charliepie said:
Data is turned on under data usage in settings menu and the APN is correct? What does the error message say and can you make calls/SMS OK?
Click to expand...
Click to collapse
Hey! i fixed it. again fith XDAs help
http://forum.xda-developers.com/canvas-a1/general/fix-imei-perfect-fix-android-imei-t2943567
solution 2 worked for me.
Also i have a new problem. when connecting my bluetooth speaker it says...well maybe this belongs to another forum :good:
Okay, can someone give me some help on this one? My password that I set no longer works after restoring via TWRP. I just flashed OPLite so I can have a pseudo-dual boot setup in case I want to have dash charge. Then I restored Bliss, and my unlock password no longer works. Any way I can get around that?
Edit: I just found something that suggests there might be no way around this...hoping I don't have to start from scratch here.
Thanks, hadn't seen any of those posts. Ugh, back to square one...
Well, this happened again, and I guess I should have Googled it more last time. Fixed using these steps:
http://www.androidexplained.com/oneplus-3-fix-twrp-restore-unlock-bug/
Thank you for updating this thread with the link! You just saved me so much frustration.
Why is it when I set a fingerprint, I set a pattern for the mandatory backup security but when I try to unlock with fingerprint it asks for a pattern saying "Pattern required to enable fingerprint"?
As far as I know, as an extra security, a pattern/pin code is necessary when the phone is restarted/ switched on, once you chose to use the fingerprint scanner.
Howling Wolf said:
As far as I know, as an extra security, a pattern/pin code is necessary when the phone is restarted/ switched on, once you chose to use the fingerprint scanner.
Click to expand...
Click to collapse
It's every time I lock it
Sent from my HTC 10 using Tapatalk
Finally figured it out.
It happens when screen is locked by a 3rd party app, in my case I use nova double tap to lock screen.
Was wondering why (and forgot to mention) it seemed random.
Edit: for Nova users looking for a workaround, if you enable screen off by root access method it will use a secure lock and enable the fingerprint to unlock.
Heisenberg420 said:
Finally figured it out.
It happens when screen is locked by a 3rd party app, in my case I use nova double tap to lock screen.
Was wondering why (and forgot to mention) it seemed random.
Edit: for Nova users looking for a workaround, if you enable screen off by root access method it will use a secure lock and enable the fingerprint to unlock.
Click to expand...
Click to collapse
yeah a lot of screenapp does ask.... if you are on elementalx you could use button mapper which gives you the same functionality of double to sleep and more doesn't ask for patter/pin everytime you unlock
This started to happen to me after a bug crashed the phone and had to force restart it holding volume down + power. I only have the default launcher so I guess it's factory reset time for me
Heisenberg420 said:
Why is it when I set a fingerprint, I set a pattern for the mandatory backup security but when I try to unlock with fingerprint it asks for a pattern saying "Pattern required to enable fingerprint"?
Click to expand...
Click to collapse
For what it's worth, I had the same issue (until I found this thread) and it was caused by Action Laucher 3. The launcher was set as a Device Administrator and was granted permission to "Power screen off". Once I removed that permission my troubles were over.
Seems to me that it makes sense once you have a fingerprint setup, to require a pin as well. Why? Because what if the fingerprint reader stops working? You won't be able to login?!?!
Not sure until the poster above mentions a pattern is required. Normally it is a pin if you want. Then the PIN required upon restart option as well that is there.
Of course, if you are rooted, you can delete the system files that control/store that...but if not rooted with TWRP, you would have to try a master reset I would assume?!?!
IDK...guess I never thought of testing that out...haha
Guys, i hope it's ok if i conquer this thread for my question but i got serious issues here.
Got my 10 back from repair today and restored my backup.
But dumb me it seems as if i set a password/patern whatever and i can't remember it.
So after the first restart i can't unlock my phone cause it's asking for the code (and won't let unlock only with fingerprint) and i can't remember.
All combination that i would have used are wrong and now i got a working phone back again (after almost 2 month of repairing) and can't unlock it.
Is there any way of bypassing/ignoring the restart password or is it possible to only unlock it again with the fingerprint that is stored?
As i don't know what i should do if i don't get my phone unlocked
bmwbasti said:
Guys, i hope it's ok if i conquer this thread for my question but i got serious issues here.
Got my 10 back from repair today and restored my backup.
But dumb me it seems as if i set a password/patern whatever and i can't remember it.
So after the first restart i can't unlock my phone cause it's asking for the code (and won't let unlock only with fingerprint) and i can't remember.
All combination that i would have used are wrong and now i got a working phone back again (after almost 2 month of repairing) and can't unlock it.
Is there any way of bypassing/ignoring the restart password or is it possible to only unlock it again with the fingerprint that is stored?
As i don't know what i should do if i don't get my phone unlocked
Click to expand...
Click to collapse
Try a factory reset via Android Device Manager.
I don't know what Android Device Manager is but I could do the reset in TWRP too. It's about not losing all of my data or a possibility to get that device unlocked without the code. It would be no problem as my fingerprint is stored. Damn, I could just hit my head against a wall or alternatively just cry like a baby. I never forgot a password or code in my whole life and by now it happens
bmwbasti said:
I don't know what Android Device Manager is but I could do the reset in TWRP too. It's about not losing all of my data or a possibility to get that device unlocked without the code. It would be no problem as my fingerprint is stored. Damn, I could just hit my head against a wall or alternatively just cry like a baby. I never forgot a password or code in my whole life and by now it happens
Click to expand...
Click to collapse
Log in here https://www.google.com/android/devicemanager
Using the account your phone is used with.
Thx, but there I only have the options of letting the phone ring, lock it down or wiping it. As stated above I could do that easily in recovery, too.
I'm looking for a way of not having to wipe the phone (if there is one....)
bmwbasti said:
Thx, but there I only have the options of letting the phone ring, lock it down or wiping it. As stated above I could do that easily in recovery, too.
I'm looking for a way of not having to wipe the phone (if there is one....)
Click to expand...
Click to collapse
To be honest, I don't think so. There were loopholes before, but they have been closed. :/
So doing a factory reset and restoring /data is the only way of getting back control of my phone again (without losing too much data)?
I think i will get rid of locking my phone with fingerprint again as there seems not ot be a failsafe mechanic for forgetting a (backup) mechanic
OK, so it seems that I have to throw that piece of aluminum against the wall. The code seems to interact with /data, because after restoring only /data I have to put in the forgotten password again.
bmwbasti said:
OK, so it seems that I have to throw that piece of aluminum against the wall. The code seems to interact with /data, because after restoring only /data I have to put in the forgotten password again.
Click to expand...
Click to collapse
I really suggest starting from zero, when you get everything set, then set a password.
Thanks for your advice, but it's not about starting from zero. I've already done this twice today
It's about at least being able to get (some of) the data of /data