So I followed this spoof guide twice and my phone has been in bootloop twice exactly at the *1 final reboot* step. I'm interested to know what triggers it, can't be because I enabled the location/GPS settings on joystick app right?
The bootloop condition is like it shows lock screen for 1 sec then it goes back to G logo screen and repeat.
Any help is appreciated, thanks.
Related
Hi all !!! Sorry for my English but I need your help
I commented what is happening with my phone N5 (which for good and evil is always stock without root or anything, with corresponding OTA updates.)
1- Yesterday afternoon at lunchtime while reading a book in playbooks, I notice that suddenly disappears one line and then appeared intermittently. I close the app and noticed the same thing happening on the screen menu. I shut down the cell and turn on again and I thought it must be an application be kidding. But still does.
2 Also yesterday I happened to change the security on the phone screen. After a while of normal operation, try to turn it on the screen with the button, nothing, the screen goes "black", with light and retrolight turned on but no picture no nothing .
Called the cell to see if it works or is turned off and the phone rings but the screen nothing. Try turning it off and on again by holding the on / off / lock button and the phone restarts, but the screen nothing. In one such attempt to do the above it is seen that managed to turn it off. And I get it on and do a normal boot, except that the picture of my screen is changed to the original. Change the lock screen which was previously using (slip). And it seemed that out or some conflict with the lock. In one of those again pressed the ON / OFF / lock as would normally and it starts all over again.
After I magically back to life, I want to make a full wipe as I think it should be an app that is doing some conflict or something. BUT ....
3I turn off the phone and then press the keys VOLUME UP / DOWN and ON / OFF is normally off, squeezed the first screen with the options but options RECOVERY / BOOTLOADER appears in red I choose RECOVERY give the ok with the key and .... andriod robot appears with the legend below that says something (I do not remember well) without or without controls options appears. So its seems thatI dont have recovery.
After that keep pressing the key ON / OFF and the phone turns off and / or reboot normally. All this I did it again to see if the error reappears and looks that I do not have recovery.
The failure of the screen is increasing. I dont know if they are separate problems or is it all the same problem.
Sorry if I was too long but I need the help of you.
UPDATE Now it seems that the screen died, since I do not achieve to turn it on as before, the light and the retrolight its ok. The phone receives calls and notifications but the screen stills black.
Thanks all.
Matias M 73
the android laying on its back IS the atock recovery.
simms22 said:
the android laying on its back IS the atock recovery.
Click to expand...
Click to collapse
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:
Matias M 73 said:
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:
Click to expand...
Click to collapse
sometimes things just "derp". itll happen more often if you dont reboot your phone often. also, your phone will be a little bit more responsive if it gets reboot once a day or two.
RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.
republicano said:
RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.
Click to expand...
Click to collapse
Thank you Republicano!!
I think too that its a hardware issue. I already see on you tube problems like mine.
Thanks again!!
[SOLUTION] How To Fix "CM Lockscreen Has Stopped Working" Error in OnePlus One 38R
DISCLAIMER: I do not guarantee that this method will work for you, but it doesn't require ROOT or a custom recovery, etc. So, it's safe.
So, three days after OTA updating my OPO to XNPH38R, I randomly got the "unfortunately, CM Lockscreen has stopped working" error, and my phone became virtually unusable. I was devastated! I didn't want to wipe my phone. So, I decided to just got into Recovery and wipe the cache. But my custom recovery was freezing, so I decided to boot up my computer and try to re-flash recovery... And while I was waiting for my computer, I stumbled upon this work-around. I hope it helps someone.
WORK-AROUND METHOD:
Step 1.) Reboot your phone. (You'll have to hard reset it by holding the power button down for 5+ seconds.)
Step 2.) After the phone restarts and you're faced with the persistent error of death again, just press the power button once to turn off the screen. Then, turn the screen back on.
Step 3.) When you turn the screen back on in Step 2, the screen should be totally black with the capacitive buttons still lit. If this doesn't happen, try repeating Step 2 until it does.
Step 4.) Just leave the phone on with a blank screen and lit capacitive buttons for 20+ seconds. This seems to be an important step.
Step 5. Turn your phone screen off and back on again. For me, this fixed the persistent error. Yay! Hopefully it works for you. However, for me, the error came back again in only 5 minutes, and I had to repeat the entire procedure. Which is why we need Step 6.
Step 6.) Disable the lockscreen. This can be done by going to System Settings > Lockscreen > Screen Security > Screen Lock, and then choose "none" to disable the lockscreen entirely. This has kept the persistent error from recurring for me for 12+ hours.
And, that's it! That's all. You get to keep your data and information. And you get to keep the latest OnePlus One software version... However, unfortunately, you lose all lockscreen Security. But, you could maybe try installing a third-party lockscreen like "GO LOCKER" until OnePlus recognizes this problem and fixes it in the next update.
Good luck everyone! Lemme know if this works for anyone else besides me.
Marvelite said:
DISCLAIMER: I do not guarantee that this method will work for you, but it doesn't require ROOT or a custom recovery, etc. So, it's safe.
So, three days after OTA updating my OPO to XNPH38R, I randomly got the "unfortunately, CM Lockscreen has stopped working" error, and my phone became virtually unusable. I was devastated! I didn't want to wipe my phone. So, I decided to just got into Recovery and wipe the cache. But my custom recovery was freezing, so I decided to boot up my computer and try to re-flash recovery... And while I was waiting for my computer, I stumbled upon this work-around. I hope it helps someone.
WORK-AROUND METHOD:
Step 1.) Reboot your phone. (You'll have to hard reset it by holding the power button down for 5+ seconds.)
Step 2.) After the phone restarts and you're faced with the persistent error of death again, just press the power button once to turn off the screen. Then, turn the screen back on.
Step 3.) When you turn the screen back on in Step 2, the screen should be totally black with the capacitive buttons still lit. If this doesn't happen, try repeating Step 2 until it does.
Step 4.) Just leave the phone on with a blank screen and lit capacitive buttons for 20+ seconds. This seems to be an important step.
Step 5. Turn your phone screen off and back on again. For me, this fixed the persistent error. Yay! Hopefully it works for you. However, for me, the error came back again in only 5 minutes, and I had to repeat the entire procedure. Which is why we need Step 6.
Step 6.) Disable the lockscreen. This can be done by going to System Settings > Lockscreen > Screen Security > Screen Lock, and then choose "none" to disable the lockscreen entirely. This has kept the persistent error from recurring for me for 12+ hours.
And, that's it! That's all. You get to keep your data and information. And you get to keep the latest OnePlus One software version... However, unfortunately, you lose all lockscreen Security. But, you could maybe try installing a third-party lockscreen like "GO LOCKER" until OnePlus recognizes this problem and fixes it in the next update.
Good luck everyone! Lemme know if this works for anyone else besides me.
Click to expand...
Click to collapse
This is not working for me as i cant get my phone to the stage where the screen is black with only the buttons lighting up
Alternative solution
I too faced the same problem with the lockscreen after changing my wallpaper.
However the method mentioned above did not work for me.
I tried this instead.
1. Restart your phone by holding down the power button for a few seconds.
2. Turn off the screen.
3. Use the play music gesture: swipe down 2 fingers to start the music player. (tried the camera gesture but did not work).
The lockscreen problem disappeared since then. I have also turned off the lockscreen in the settings in fear of it reoccurring.
Hope this helps any of you suffering from the same problem.
Cheers!
I found another way to get your phone unlocked
So the solution that was provided by Marvelite did not work for me. I tried many many MANY times, but to no avail.
After looking around the interweb, I found some other instructions to root my phone (FYI I had no experience in rooting) and I was able to fix it without flashing or re installing anything.
So... what did I do. All I did was unlock my phone. I got my phone and remember saying it was unlocked, as you could use any carrier. That is not what I mean by unlock. What I mean by unlock is you cannot flash it or erase it. See the command line window below saying the phone is not unlocked and that is why I cannot flash it. I thought I had to flash it or erase it to get everything working. Just unlocking it fixed the CM Lockscreen Has Stopped Working error.
So what will you need to install on your computer and do to your phone.
1) Download adb-setup- 1.3.exe (if you type "adb-setup- 1.3.exe" into google, you will find a download) and install ADB system wide on your computer.
2) Put your phone in Fastboot mode and plug it into your computer. To do this, have your phone completely off and then hold the volume up and power button. You will see the screen of your one plus one in fastboot mode.
3) open up a command line window (as in my attached picture) and type fastboot oem unlock
THIS WILL RESET YOUR PHONE! After I typed in fastboot oem unlock, my phone reset itself and it was though I had hit the factory reset.
You can see from the command line window attachment, that I tried to flash my phone based on this workflow (http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061), but I did not even need to do this, because my phone was not unlocked. Then when I unlocked my phone, the problem was fixed.
I hope this works for those that have this horrible bug.
As the title says, I was making a tasker profile to give my camera button permission to lock and unlock the device. I also allowed the Secure Settings plugin to be installed into the system. Now, when I boot the phone, the display stays on for a very short amount of time. Ive tried to QUICKLY get to tasker right away to turn off the profile, but I never have quite enough time before the screen goes black. Then, pressing the unlock button only flashes the screen for a second, the camera button does nothing. USB debugging should still be enabled, thankfully. It's a Sony Xperia z1s. How can I get to tasker and secure settings to remove both and start over?
Edit: Have enough time to boot into safe mode, but then it continuously says " unfortunately, initialbootsetup has stopped"
I cant factory reset, I dont have a nandroid. Please help and tell me I havent completely screwed my phone.
Flash stock sony os. It should fix it.
CoDe LaZaRuS said:
Flash stock sony os. It should fix it.
Click to expand...
Click to collapse
Thank you, nothing else was working. It's all good now
Happy to help
Hi
I just got my new S6 and went ahead to turn on encryption on the device. I had it fully charged, plugged in etc. The phone reboots to a screen which shows the progress it gets to 100% fairly quickly, some 5-7 minutes, after that it restarts and shows the samsung logo. It gets stuck there, nothing else loads after that, no error messages, nothing, just the samsung logo. I tried leaving it like this overnight nothing happened. So after factory reset the phone works again, tried the same thing and had the exact same results. Again factory reset, and now looking for a solution. Anyone experienced anything like this before? Any ideas of how to get it working?
Thanks!
Model number: SM-G920F
Android Version: 5.5.1
Kernel Version: 3.10.61-5496010
icbraz said:
Hi
I just got my new S6 and went ahead to turn on encryption on the device. I had it fully charged, plugged in etc. The phone reboots to a screen which shows the progress it gets to 100% fairly quickly, some 5-7 minutes, after that it restarts and shows the samsung logo. It gets stuck there, nothing else loads after that, no error messages, nothing, just the samsung logo. I tried leaving it like this overnight nothing happened. So after factory reset the phone works again, tried the same thing and had the exact same results. Again factory reset, and now looking for a solution. Anyone experienced anything like this before? Any ideas of how to get it working?
Thanks!
Model number: SM-G920F
Android Version: 5.5.1
Kernel Version: 3.10.61-5496010
Click to expand...
Click to collapse
This is the actual way of encryption, make sure that you follow each and every step carefully, also it does take a while to get completed, so don't freak out and switch off the phone or hold the power button which will interrupt the process (I'm guessing this might have caused the issue you are facing with the phone getting stuck at the samsung logo).
Galaxy S6 Enable Encryption :
1. Launch the Settings Application
2. Scroll/Navigate to the Personal Section
3. Tap on the ‘Lock Screen and Security’ Option
4. Scroll Down and Tap on the ‘Other Security Settings’ Option
5. Then Tap on the ‘Encrypt Device’ Option in the List.
6. Read the Information and Enable a Password or PIN Code if Needed
7. When Ready, Tap on the ‘Encrypt Device’ Button at the Bottom
8. Confirm Your Password or PIN Code
9. Read the Warning Information and Keep the Galaxy S6 Connected to a Charger
10. Tap on the ‘Encrypt Device’ Button at the Bottom
11. Wait During the Black Screen with the Lock
12. Wait for the Reboot, Wait for the Encryption and Wait for Another Reboot
13. Enter the Password or PIN Code When Prompted During the Boot Process
ultraquantum, thanks for the reply. Did you encrypt your S6? If yes how long did it take for the whole process? I have done this same procedure in a few android phones I owned in the past and it never took more then an hour or so max. I left the S6 plugged in for over 5 hours before forcing shut down and having to restore to factory settings. Do you think this is normal?
ultraquantum said:
This is the actual way of encryption, make sure that you follow each and every step carefully, also it does take a while to get completed, so don't freak out and switch off the phone or hold the power button which will interrupt the process (I'm guessing this might have caused the issue you are facing with the phone getting stuck at the samsung logo).
Galaxy S6 Enable Encryption :
1. Launch the Settings Application
2. Scroll/Navigate to the Personal Section
3. Tap on the ‘Lock Screen and Security’ Option
4. Scroll Down and Tap on the ‘Other Security Settings’ Option
5. Then Tap on the ‘Encrypt Device’ Option in the List.
6. Read the Information and Enable a Password or PIN Code if Needed
7. When Ready, Tap on the ‘Encrypt Device’ Button at the Bottom
8. Confirm Your Password or PIN Code
9. Read the Warning Information and Keep the Galaxy S6 Connected to a Charger
10. Tap on the ‘Encrypt Device’ Button at the Bottom
11. Wait During the Black Screen with the Lock
12. Wait for the Reboot, Wait for the Encryption and Wait for Another Reboot
13. Enter the Password or PIN Code When Prompted During the Boot Process
Click to expand...
Click to collapse
icbraz said:
ultraquantum, thanks for the reply. Did you encrypt your S6? If yes how long did it take for the whole process? I have done this same procedure in a few android phones I owned in the past and it never took more then an hour or so max. I left the S6 plugged in for over 5 hours before forcing shut down and having to restore to factory settings. Do you think this is normal?
Click to expand...
Click to collapse
As far as i know, 5 hours+ is on the higher side. I have not encrypted S6, but i have done in other phones and in most cases, it never took more than 2 hours.
Hello All,
Basically what happened is this:
I got phone D6603 with "Vodafone protect" lock on and owner gave me a possible code for phone. I replaced screen and then found that lock requires only numeric pin, not what I was given. So, he then reset pin and deactivated lock, but I still had it on no matter what. So, I tried to flash new firmware into it for same phone and got it done, but now phone screen stays black all the time with only backlight on. Phone seemingly loads something (probably the new phone welcome screen after flash), which I cannot see, but when connected to computer from fastboot or something then all system files are visible.
When I boot phone from off position, it boots to a point where I can use side button to switch on and off the screen but touch does not respond because nowhere it reacts to touch or maybe I do not know where and what to click on screen.
What could be the likely solution? I do not think that phone is bricked, but something is wrong with system as it does not light up the screen properly. I tired flashing 2 times successfully with same result.
Any advice would e appreciated.
Hi, can this thread be deleted because I am getting phone swapped and thread no longer relevant? Thanks.