[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.
Related
Hello, This is my first post. I have the vanilla GTAB with the 2 updates that were automatically loaded last Dec. & Jan. I frequently get force closes. Today when I booted the gtab, I had it connected to my pc, but I clicked 'hide' at the activate usb prompt. Then the usual force close occured in Launcher pro. At the same tiime there was a prompt that said something like "which app to use for this action" 1) desktop or 2) launcher pro. Since I thought I already set this to Launcher pro, I selected Launcher pro, and (this is the important part, I think) I checked the box to make this the default action. I had done this before so I didn't give much thought to it.
Well, the device immediatel began looping between to 'force closes' that look similar: 1) The application LancherPro (process android.acore) has stopped unexpectedly. Pleas try again; and then the second half of the loop is 2) The process android.process.acore has stopped unexpectedly. Please try again.
Note that in #2 it doesn't refer to LauncherPro.
I rebooted the ddevice and it immediately goes into the same loop.
Is there any way out of this? I can't help thinking it is caused by making the failing app (Lpro) the default action. How do I get the prompt back? Or have I bricked this gtab?
I was able to activate usb support between loops, so I have backed up all my data to my pc (whew!), but I can't get the device to do anything on it's own, other than loop. I do not have a recovery file or any of the suggested clock??? utilies. This is a completely vanilla device. Therefore booting with recovery (power + vol +) just comes up and enters the same loop.
Sorry if this is long winded, but I want to hear any advice before I follow Viewsonic cust support's instructions to ship it to them for a hardware reset. TIA, -Jim
Try Fix Permission in the Recovery. I face this problem every now and then and could not find a better permanent solution . Its really painful at times. It usually happens when my Gtab awakes from a long sleep (like remaining in standby for overnight).
I just experienced the same problem the other day. It is my third time with all the loops and force close and android.process.etc.etc. Unfortunately the GTab with the stock OS has this troublesome issue. I followed the instructions to install clockworkmod (CM) restore to stock with the 3389 mods, and now when it happens I boot into CM and first try and clear the cash and if that dosen't fix the problem then I do the wipe data/ factory reset option which is a pain, but if you have backed up everything you are back up and running with everything restored in less than 15 minutes. Do a quick search and you will find the CM solution to get your tablet back.
Hope this helps! I think everyone who has this device has gone through it. I guess for the price what can you expect, $799 for a XOOM without flash or $350 for the Gtab with flash and some issues. There is always a trade off.
Thanks VERY MUCH for the replies. So minardml, it seems you have done the factory reset yourself. Is there instructions for this online? You took the back off the unit to do it? I will search for the CM solution. Also, kshwetabh, you are right it had been several days since I used the gtab. Could you explain how to "try fix permission in the recovery?"
newbieJim said:
Thanks VERY MUCH for the replies. So minardml, it seems you have done the factory reset yourself. Is there instructions for this online? You took the back off the unit to do it? I will search for the CM solution. Also, kshwetabh, you are right it had been several days since I used the gtab. Could you explain how to "try fix permission in the recovery?"
Click to expand...
Click to collapse
@newbieJim, before wiping cache or factory resetting try Fixing permission option. It always works for me.
1. Reboot system into Recovery (Shutdown. Press and hold Volume Up(+) button and press Power button.
2. Select "advanced" ( scroll the options using Volume up/down button). Press Home button when on "advanced" option
3. Select "Fix Permissions".
This will take a while (depending on the packages/apps installed). Note that you will not see any progress bar. Once complete simply reboot.
Hope this helps . I don't know how the system looses permissions but somehow it does.
-------------------------
kshwetabh
NexusOne [Cyanogen 7| Desire HD| MM Cyanogen 7| Looking for 720P mod]
GTab [Vegan latest]
http://kshwetabh.wordpress.com/
Sorry if I led you to think that I took the back off as I did not do that. The options that I was refering to are in the menu of clockworkmod. If you haven't found the fix I was talking about (installing CM) post again and when I get home later today I will see if I can find it. I think I may have bookmarked it on my laptop.
I just keep the home button prompt on. it seems to prevent 90% of FCs and also improved the screen lag i was getting.
it may be another step, but it's less of a pain the the ass in the end.
Once again thx to all. I will attemp recovery again, but I don't have high hopes because, as I said, the loop happens even in recovery (or safe) mode. IOW, I cannot get to any menu or screen.... Only the loop. I do not think I can install any new app., but I will try tomorrow when I return.
I have a Tmobile HTC One M7 that I paid $300 for. It was awesome! However, I wanted to root it. So I successfully unlocked the bootloader, installed TWRP and then proceeded to attempt to root. Something went wrong and now this thing is useless! I cannot tell you where it went wrong because when the first sign of trouble appeared I started doing all kinds of **** to try and fix it, none of which worked and I have lost track of what I did in the process of trying to root and then subsequently trying to fix. I know there were some wipe cache, wipe dalvik cache, install zip from SD, I may have even tried to flash a custom ROM without the thing being rooted. I have been reading for days, trying this, trying that to no avail. The phone is brand new, without a scratch. It will power up like normal, but when it gets to the lock screen where you swipe the little lock in the bottom tray to use the phone it will not respond at all! It recognizes the network because it is displayed in the notifications bar up top, it can see the signal strength, it knows what time it is, it knows what the date is, but it will not get past the damn lock screen. ADB sideload works. I was able to push a zip and flashed it, even said android is upgrading when I rebooted, but it did not solve my problem. It will not power off, but when I hold the power button down, to turn it off the back arrow < and home symbol flash and after about 10 seconds a dialog box pops up that says to restart your phone continue to press and hold the power button and starts a countdown. Once the countdown gets to zero it restarts. If I hold the volume down button while doing this it will go into the boatloader and I can get into recovery. Apparently there is no backup to restore because when I try a restore I get the same exact same thing. I thought I had done one, I must have erased it somehow. I have been trying to resolve this for weeks now and am at my wits end. Any suggestions please !?!? Will anyone on this forum take it if I ship to them and fix for a fee? Otherwise this things going in the trash.
My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.
Getting the power button fixed isn't too expensive. Hopefully that's all you need. ?
whyareallusernamestaken said:
My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.
Click to expand...
Click to collapse
I have had this issue for the past 4 days. After many attempts of trying to bang the phone a lil onto my hand (for where the power button is located at), sometimes the phone will boot fine, for as long as you do not click the power button again it won't act up.
(I am pretty sure I didn't drop my phone when I was napping in the car, it just started out of nowhere after I have been using lollipop 5.0 with franco kernel for like 2 months without any problem).
Same sypmtoms, bootloop (looked like the power button defective / boot IC on mobo defective), can't even stay on recovery/bootloader screen/system for longer than 5 sec.
Try these :
- spam click power button, until it is able to boot into system, you will have to keep clicking, for every click you either screen on/off you will realize Power Off options may pop up, it looks like the power button has been holded for few sec to trigger the power off, but all you do was spamming the click to keep the button active, you have to click until you feel that certain point the power off doesn't pop up, then stop clicking ( remember never to touch that power button again for NOW), if after a few sec of using the phone and it doesn't force shut down (result from power button defective where it sense its being clicked and hold for like 8-15 sec). Then you are good to carry on whatever I am to tell here.
- go to about phone, click the build number for 5-10 times until you get the unlocked developer mode
- back, click on developer options, enable usb debugging mode (this will pop another message asking you if you want the device to memorise your pc's mac address) that way it is synced with your pc.
- before you proceed with any other thing, go to playstore, download power button to volume button, enable volume power, check start volume power on bootup, check screen off. This will help you greatly for not touching the power button to unlock the screen when you are working on your pc.
- if you have all the correct nexus usb driver installed onto your pc, you need to get Minimal ADB and Fastboot installed onto pc. After installing, run Minimal adb and fastboot, a command prompt windows will pop out and is automatically redirected to the minimal adb folder. key in this command
"adb devices" to see if it detects your device or not. There should be at least a device listed if you have the usb driver installed correctly
- now you can make use of adb commands to reboot into bootloader/recovery to do any flashing of system, backup all your data that you needed to PC. Download official 5.0.1 nexus 5 image and extract it into the Minimal ADB folder.
- is your bootloader unlocked? if not do adb reboot-bootloader
- fastboot oem unlock (this will wipe all your data on the phone)
- fastboot reboot after the wipe is done
After that you can actually carry on with flashing back to stock images. Look at this link http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for flashing to stock factory image.
I am not sure which step has actually solved my problem, because on my first flashing of factory image, booting into system as a brand new device (no extra softwares, yet to recover any of my data). the problem persists as long as I clicked on power button once, it'll act up again random power off and bootloop.
I actually was on a follow-up cases with google play support team from Aus as my device was bought from Aus. After the last step of factory image setting, doesn't help, I intended to ship it back for RMA as my device is still under warranty and I suspected it was the hardware issues from power button too. They will send me another refurbished device. After ending the call, they sent me link to proceed with warranty claims where I need to fill in several forms and ship the device back to them.
I decided to give it one more try, due to my phone was previously unlocked, rooted, changed to franco kernel.
By restoring to stock images made my device unroot, I was afraid of google will accuse me for unlocking bootloader voided the warranty and not willing to replace another unit for me. I locked back the bootloader, then I remembered in bootloader, fastboot oem device-info shows that a record of a phone if it has been unlocked, it will show Tampered status as True, google probably can use that to track if a device has been unlocked before. So I unlocked my bootloader again (which causing another wipe for whatever data is in the device).
So I looked up on google again and found source for changing that tampered status to False in addition to locking the bootloader again, but to change that tampered status, I need to use TWRP to run the scripted zip file, so I used fastboot boot path (it is stated in the link I gave you above) to boot into TWRP images temporarily from my desktop and ran the zip file, I always practice wiping data, cache and everything before I boot the device back into a brand new factory image.
So I went to wipe dalvik cache. Rebooted the system - it was running the Optimizing x numbers of Applications.
Upon finished with that. I was surprised that, after a few clicks of power button, the random power off issues is no longer there. I even test clicking on the power button for entire day. The symptom isn't coming back. So I emailed google play support team to cancel my warranty ticket and close the case for now.
Should there be any problem again I will probably then claim the warranty for replacement.
Its been more than 24 hours now that I am using the device without any problem of random power off and on or stuck in bootloop due to power button defective.
I suspect it is either the 5.01/5.0 lollipop with ART that is causing something wrong with the boot IC / power button defective in a long run.
Or maybe it was some settings I have changed in franco kernel ? but it was running fine for 2 months which made me doubt that it is franco kernel
Or it could be some of the apps I used to tweak my phone settings - LLama and tactile player (which I have set something condition and actions for power button) but I doubt it is caused by these either.
I will observe and see if the problem comes back after some time of using the 5.0.1 stock image now.
Oh I am also back to using franco kernel, unlocked bootloader and rooted again. Haha...
Hopefully you are able to solve the problem by trying some factory reset method + wiping cache, partition and dalvik.
If not, you probably may have the hardware issues, I have seen some other forum/websites with n5 users upon replacing the mobo, no longer encounter such problem.
Regards,
Kean
Thanks for the replies. My girlfriend was able to get the power button repaired for $80 and replaced the external button for $7 + tax, she paid $98. At least it's cheaper than a new phone.
hi my one vision every time when i unlock or lock restart device. any help?
normee66601 said:
hi my one vision every time when i unlock or lock restart device. any help?
Click to expand...
Click to collapse
I tried to use Action Launcer on my One Vision, it started doing EXACTLY that (restart after unlock).
The only way I could solve it was entering in recovery and wiping it clean. Here's how to do it:
1. Turn it off (hold Power Button for a few seconds)
2. Hold Power Button + Volume Down for some seconds
3. When you enter fastboot mode (with the android robot on screen), release the buttons
4. Use Volume Down to choose Recovery Mode and press Power Button to enter it
5. It will show the Android Robot with "No Command" on screen, when you get on this screen, hold the Power Button and press Volume Up then release the buttons, you will get into Recovery Mode screen
6. At Recovery Mode, choose Wipe data/Factory Reset and confirm when asked.
This worked on mine.
(link to procedure: https://www.hardreset.info/devices/motorola/motorola-one-vision/recovery-mode/)
It will wipe your phone clean. If after that it don't work right, you better get your phone to warranty.
Same thing happened to me after changing default USB behaviour in developer settings.
Once I set it to file transfer, my phone rebooted as soon as I put the USB cable in.
It went to a bootloop a couple of times before it booted up to lock screen, but it rebooted again once I entered my lock pattern.
Only way to solve it was to factory reset
Moto is aware of the problem and working on it afaik.
Hopefully it will be fixed with the next update.
Skickat från min motorola one vision
I was wrong... It tried with other launchers, same problema. I've read that some phones with problem in the fingerprint sensor have this behaivor. As soon as you add fingerprint as the unlock option, It may reboot randomly or when you try to unlock.
I've wiped It again and confirmed this behavior on mine. I'm going after warranty on monday.
tys0n said:
Same thing happened to me after changing default USB behaviour in developer settings.
Once I set it to file transfer, my phone rebooted as soon as I put the USB cable in.
It went to a bootloop a couple of times before it booted up to lock screen, but it rebooted again once I entered my lock pattern.
Only way to solve it was to factory reset
Moto is aware of the problem and working on it afaik.
Hopefully it will be fixed with the next update.
Skickat från min motorola one vision
Click to expand...
Click to collapse
I´ve got the same problem. How did you get it to factory rest?
badadam said:
I´ve got the same problem. How did you get it to factory rest?
Click to expand...
Click to collapse
I made factory reset from recovery.
Sent from motorola one vision.
tys0n said:
I made factory reset from recovery.
Sent from motorola one vision.
Click to expand...
Click to collapse
Thanks, did the same thing. Just had to google my way to finding out how to get into recovery.
tys0n said:
Same thing happened to me after changing default USB behaviour in developer settings.
Once I set it to file transfer, my phone rebooted as soon as I put the USB cable in.
It went to a bootloop a couple of times before it booted up to lock screen, but it rebooted again once I entered my lock pattern.
Only way to solve it was to factory reset
Moto is aware of the problem and working on it afaik.
Hopefully it will be fixed with the next update.
Skickat från min motorola one vision
Click to expand...
Click to collapse
I've made new tests on my Motorola One Vision... That's the problem. As soon as you set the default USB mode to file transfer, my phone starts to reboot even without plugging in the USB cable...
I've wiped it clean, started with the bare minimum, just logged on Google Play Store. I activated the default USB mode to "File Transfer" on the Dev Options.... With no lock option, it works OK. As soon as you set ANY locking method (pin, pattern, fingerprint) it reboots when you try to unlock the phone...
Seems like the only way to solve it is to keep the default USB mode unchaged.
erick.noleto said:
I've made new tests on my Motorola One Vision... That's the problem. As soon as you set the default USB mode to file transfer, my phone starts to reboot even without plugging in the USB cable...
I've wiped it clean, started with the bare minimum, just logged on Google Play Store. I activated the default USB mode to "File Transfer" on the Dev Options.... With no lock option, it works OK. As soon as you set ANY locking method (pin, pattern, fingerprint) it reboots when you try to unlock the phone...
Seems like the only way to solve it is to keep the default USB mode unchaged.
Click to expand...
Click to collapse
Yes. For now we have to change usb mode from the notification panel each time, untill they got it fixed.
https://forums.lenovo.com/t5/motorola-one-vision/Bootloop-when-Developer-options-are-enabled/td-p/4444229
I disable fingerprint, now works perfect
normee66601 said:
I disable fingerprint, now works perfect
Click to expand...
Click to collapse
You disabled only fingerprint? Are you using any other unlock method, or just swipe? Mine got into bootloop even if I add a pattern.
when device restart swipe down status bar press setings then unlock and remove fingerprint
After you have changed the default USB mode to "transfer" on the Developer Options, you cant do that. If you have any sort of lock in place that's different from "swipe to unlock", your phone will reboot on any try to unlock it, even if you try to get to settings (it will ask to unlock, then when you try, it reboots).
If you get into the "bootloop", the only way to get out of it is to enter recovery and wipe the phone. The only way to avoid the bootloop is to a) don't change default USB mode to "transfer" on Developer Option or b) only have "swipe to unlock" as the lock option.
If you set a) and anything different then b), you get stuck in bootloop.
I was sad because I'd need to make a hard reset on my phone after this bootloop but then I tried to start it connected in my PC through USB and then BAM it worked out, boots without restarting, it worked out for me, it should for yours too!
Just wanted to confirm, for all those falling foul of this little bug, that Riverm4n's previous advice does indeed work. And saves the heartache of a full system reset..
Just wanted to clarify the guidance a little..
So with the phone on, and on the lockscreen, plug into your PC.
Let Windows do it's driver install thing of it's the first time it's been plugged in..
Then type in your unlock code on the phone..
Potentially could still go into the reboot again, just leave it plugged into your PC and the next time the phone comes on typing your unlock code in should see it unlock without rebooting!!
Don't forget to disable the developer settings or change the usb thing back!!!
riverm4n said:
I was sad because I'd need to make a hard reset on my phone after this bootloop but then I tried to start it connected in my PC through USB and then BAM it worked out, boots without restarting, it worked out for me, it should for yours too!
Click to expand...
Click to collapse
tonysonyhtc said:
Just wanted to confirm, for all those falling foul of this little bug, that Riverm4n's previous advice does indeed work. And saves the heartache of a full system reset..
Just wanted to clarify the guidance a little..
So with the phone on, and on the lockscreen, plug into your PC.
Let Windows do it's driver install thing of it's the first time it's been plugged in..
Then type in your unlock code on the phone..
Potentially could still go into the reboot again, just leave it plugged into your PC and the next time the phone comes on typing your unlock code in should see it unlock without rebooting!!
Don't forget to disable the developer settings or change the usb thing back!!!
Click to expand...
Click to collapse
Yeah the problem is because is enable fingerprint and default USB configuration was changed.
Just like to thank OP for this - just received a new Vision - & while setting up I had enabled Developer mode mainly due to problem with PC not seeing phone & 1 tip I read was for 'USB Debugging' to be switched on
- while in that menu I decided to force USB file transfer over 'cos of the annoyance having to select it each time I plugged phone in to transfer some pics/doc etc over
Next time I picked up phone it was in boot-loop & I thought it was broken ... PANIC STATIONS !!!!
Factory reset fixed it
- & since being new phone I didn't lose too much of the stuff I had been reinstalling/replacing (which were mainly apps to replace missing 'functions' I had on old phone such as a 'repeat notification/flash camera LED' if unread)
Did lose some game progress on a couple of games I have/had, which is annoying (wish we had a APK Data backup that didn't need root & which isn't Helium since that seems pretty unstable for me atm but then again it's not been updated for a while) but I think I can live with that
Once again thanks
Well, happened to me. I certainly wanted to avoid factory reset. It's a known bug being reviewed by Motorola/Lenovo. Happens when you change the USB connection default action in developer mode and you have any sort of screen lock.
Here is what I did to avoid factory reset, I had fingerprint lock with code.
1. After boot you get to screen lock. I you try to unlock with the code it reboots.
2. In that code enter screen, use a finger not enrolled. You'll see a message that fingerprint was not recognized.
3. Enter now your code and the device won't reset this time.
4. Go to developer options and rollback the USB default action to "no data transfer".
or
1. Factory reset
or
1. Wait for a ROM update
or
1. Return the device to seller and get another one
Avoiding factory reset!
mauro235 said:
Here is what I did to avoid factory reset, I had fingerprint lock with code.
1. After boot you get to screen lock. I you try to unlock with the code it reboots.
2. In that code enter screen, use a finger not enrolled. You'll see a message that fingerprint was not recognized.
3. Enter now your code and the device won't reset this time.
4. Go to developer options and rollback the USB default action to "no data transfer".
Click to expand...
Click to collapse
Thank you for sharing this, it actually allowed me to fix this without wiping everything! I hope they patch this issue soon. I had just finished setting everything up and I thought I would have to start again.
tys0n said:
Yes. For now we have to change usb mode from the notification panel each time, untill they got it fixed.
https://forums.lenovo.com/t5/motorola-one-vision/Bootloop-when-Developer-options-are-enabled/td-p/4444229
Click to expand...
Click to collapse
I've have the same problem on my Motorola One ACTION XT2013-4.
I'd like to get this phone into a usable, stable state. Right now, it's useless.
Background: The phone is an unlocked US version I purchased directly from HTC. I had been using it on T-Mobile. In Sept. '19 I got an update to Android Pie. Soon after, NFC payments stopped working. I put the phone on the shelf and switched to a OnePlus phone. I did a factory reset on the U11 and want to set it up for my wife, but it wont fully initialize. Here is what happens...
Power on to HTC logo (static)
Replaced by HTC animated logo with start-up sound
Phone displays WELCOME screen, with a "Let's Go" button.
I press Let's Go and the phone goes to the internet setting screen to enable mobile data and sign on to WiFi
I connect to local WiFi
The Terms of Use are displayed. I select NEXT.
The phone displays:
Just a sec..
Checking for Updates...
Checking info....
Then, a Google sign on screen appears, and immediately is replaced by the "Just a Sec..." screen and a notification window that says "Android Setup has stopped."
I've never done anything more advanced with phones than wiping a cache partition, but am willing to try most anything with this phone at this point. I've nothing to lose, but would love to get it back into service.
Any help would be greatly appreciated.
I would try the hole process not connecting to WIFI
Also you might try to do a Hard Reset, just be sure to have enough battery
Here how
A hard reset will wipe all data from the device and set everything back to factory settings. Ensure you have backed up your data before proceeding.
Hard Reset From Startup
Turn the phone off by pressing and holding the “Power” button for 3 seconds, then selecting “Power off“.
Press and hold the “Volume Down” button and press release the “Power” button to turn the U11 on.
When the HTC logo appears, release both buttons.
Press “Volume Down” to select “Factory Reset“, then press the “Power” button to choose it.
The device will then restart and the hard reset will be complete.
Hope it helps
orb3000 said:
I would try the hole process not connecting to WIFI
Also you might try to do a Hard Reset, just be sure to have enough battery
Here how
A hard reset will wipe all data from the device and set everything back to factory settings. Ensure you have backed up your data before proceeding.
Hard Reset From Startup
Turn the phone off by pressing and holding the “Power” button for 3 seconds, then selecting “Power off“.
Press and hold the “Volume Down” button and press release the “Power” button to turn the U11 on.
When the HTC logo appears, release both buttons.
Press “Volume Down” to select “Factory Reset“, then press the “Power” button to choose it.
The device will then restart and the hard reset will be complete.
Hope it helps
Click to expand...
Click to collapse
Excellent! I bypassed WiFi and everything else, and now I'm looking at a proper home screen! Any other tips or suggestions to get the most out of this device? Maybe getting it back to Oreo, when everything worked? I'm now getting the "Unable to start Camera" error that I've heard a lot of users have had.
e_s_jones said:
Excellent! I bypassed WiFi and everything else, and now I'm looking at a proper home screen! Any other tips or suggestions to get the most out of this device? Maybe getting it back to Oreo, when everything worked? I'm now getting the "Unable to start Camera" error that I've heard a lot of users have had.
Click to expand...
Click to collapse
I have an U11+ and all works perfect on Android 9, anyways if you want to downgrade here some info
GUIDE - Downgrade for HTC U11 (from Oreo to Nougat with S-ON) - Solution for various
The purpose of this guide is to restore the phone in emergency cases and not only but also to perform a downgrade without the need to be in S_OFF (the utility of Sunshine, except in special cases such as the change of MID and CID which is...
forum.xda-developers.com
e_s_jones said:
I'd like to get this phone into a usable, stable state. Right now, it's useless.
Background: The phone is an unlocked US version I purchased directly from HTC. I had been using it on T-Mobile. In Sept. '19 I got an update to Android Pie. Soon after, NFC payments stopped working. I put the phone on the shelf and switched to a OnePlus phone. I did a factory reset on the U11 and want to set it up for my wife, but it wont fully initialize. Here is what happens...
Power on to HTC logo (static)
Replaced by HTC animated logo with start-up sound
Phone displays WELCOME screen, with a "Let's Go" button.
I press Let's Go and the phone goes to the internet setting screen to enable mobile data and sign on to WiFi
I connect to local WiFi
The Terms of Use are displayed. I select NEXT.
The phone displays:
Just a sec..
Checking for Updates...
Checking info....
Then, a Google sign on screen appears, and immediately is replaced by the "Just a Sec..." screen and a notification window that says "Android Setup has stopped."
I've never done anything more advanced with phones than wiping a cache partition, but am willing to try most anything with this phone at this point. I've nothing to lose, but would love to get it back into service.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hey ESJ...I have the same issue with my HTCU11 here in Australia. I just posted yesterday to this Q&A session (above yours, sorry, didn't see your post) . I eventually got it to go past this point (don't ask me how). I went back and forth between a factory reset to clearing the cache partition and re-starting and finally it just booted up to the basic HTC screen with the factory installed apps. I have everything backed up, but the problem is, now I can't log in to any Google accounts. It crashes at the log in screen with ""Google Play services has stopped". I read elsehwere that there was aproblem with Chrome and "Android System Webview" and that there's an update to fix this problem, but I can't log into my Google accounts (Acounts, GMail, Play Store, etc) to download the update...I'm stymied. I suspect you have a similar issue? Hopefully an Andorid/Google guru will have a step by step solution, otherwise, I'll just get a new phone....and not an HTC!!!
ChrisinPerth said:
Hey ESJ...I have the same issue with my HTCU11 here in Australia. I just posted yesterday to this Q&A session (above yours, sorry, didn't see your post) . I eventually got it to go past this point (don't ask me how). I went back and forth between a factory reset to clearing the cache partition and re-starting and finally it just booted up to the basic HTC screen with the factory installed apps. I have everything backed up, but the problem is, now I can't log in to any Google accounts. It crashes at the log in screen with ""Google Play services has stopped". I read elsehwere that there was aproblem with Chrome and "Android System Webview" and that there's an update to fix this problem, but I can't log into my Google accounts (Acounts, GMail, Play Store, etc) to download the update...I'm stymied. I suspect you have a similar issue? Hopefully an Andorid/Google guru will have a step by step solution, otherwise, I'll just get a new phone....and not an HTC!!!
Click to expand...
Click to collapse
I was an HTC fan for years, but I am done with them. I'm currently studying the process for downgrading to Oreo on this U11 to see if I can get it revived. That may be your best strategy as well. Good luck, Mate!