How to boot an encrypted Moto C Plus in safe mode? - Moto C Plus Questions & Answers

Folks,
I have a Lenovo Moto C Plus (I know, sh*tty phone, but I'm Brazilian and good ones are pretty expensive here) running stock ROM (7.0) and I use full disk encryption and unlock the phone with a pattern (not an PIN or a password).
This phone got stuck in a "Lenovo" logo in the "second boot" phase, after I enter my pattern to unlock the phone. I suspect there is no free disk space left in memory and it fails to boot because of that -- Lenovo apps are not know for their quality and may not check the remaining space before trying to write something, so it makes some sense. Apart from that, phone looks ok: I can use some features from the lock screen like emergency calls (but haven't tried to actually complete a call to police, for obvious reasons), the screen shows the text message I configured and I can even take screenshots! (it was an accident, I have no idead why they left this feature there or where these files are saved when disk is encrypted).
I also wiped the caches from the recovery menu, but it didn't changed anything.
So, before resorting to a factory reset (and lose all data I haven't backed-up since december) I'll try to enter the safe mode and see if it boots. When I long-click the "Power off" from the lock screen, it changes to the "Reboot to safe mode" confirmation screen -- but it never shows the "Safe mode" text in the corner and I suppose it tries to boot normally. How can I put it in an actual safe mode?
PS. Sorry for asking this here, I don't have enough points to post in the Moto C Plus forum.
TL;DR: How can I boot an Android that is encrypted and requesting my unlock pattern in safe mode?

Der Doktor said:
Folks, I have a Lenovo Moto C Plus (I know, sh*tty phone, but I'm Brazilian and good ones are pretty expensive here) running stock ROM (7.0) and I use full disk encryption and unlock the phone with a pattern (not an PIN or a password)...
Click to expand...
Click to collapse
I don't have this device but, the following thread may be helpful for what you are looking for and don't be afraid to ask for some member guidance within it.
https://forum.xda-developers.com/showthread.php?t=3639358
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Related

Vibrant Locked Out

So, dumb self made a pattern that I don't remember. So my Vibrant is at the Too Many Pattern Attempts screen. I've tried to wipe the phone using vol up and down plus power but that doesn't remove the too many attempts screen at all. The only gmail account that I hooked up to my phone keeps telling me that something is incorrect yet I can log in to my gmail fine from my computer... What can I do? I tried to do Odin, but vol down plus power does nothing on my phone. It just continuously power cycles... When I boot into the recovery screen I can use Odin but it just hangs at checking files... Any suggestions?
Do you have coverage? Maybe the Google verification can't connect. It always worked on my myTouch and once on the Vibrant.
Sent from my Samsung Vibrant using the XDA app
Tmobile Galaxy S pattern locked out, can't root
I just bought my first Android device, the Samsung Galaxy S from Tmobile from the US (I live in China) last week. I have only used it a few days and my girlfriend thought the pattern lock would be a fun game to play. Result - locked out. I have the same problems as in the below thread:
http://code.google.com/p/android/issues/detail?id=4784
I tried the receive a phone call then hammer the home key; emergency call and go to search and many of these type fixes; however none have gotten me through. It seems they fixed the security problem here but didn't fix the username password problem as I'm sure the credentials I entered are correct and I have data service.
After giving up on these methods I tried doing a hard reset. BTW, on this model you must hold down volume up AND down buttons at the same time, then press the power button to get the reset screen.
I have cleared user data etc, but when I try to reset the phone I get the error message "setup.zip not found".
I understand that I now need to root the phone, so I tried the method explained here but without having access to the phone I need to load this setup.zip file on the SD (not the one with Avatar).
http://samsungvibranthacks.com/samsung-vibrant-hacks/how-to-root-samsung-vibrant-galaxy-s/
I already installed Kies (has Outlook sync functionality!) on my desktop so that I can access the internal memory as an external drive. However the phone's USB mode must be set to (it will prompt whenever I connect) to Kies mode. However since I am locked out of the phone I can't tell the phone to get into Kies mode, therefore cannot access the internal memory, therefore cannot load setup.zip, therefore cannot root, therefore cannot get past the pattern lock screen = useless phone.
I need to root the phone anyway so I can load a few Asian IME's that didn't come with the phone so don't mind playing with this, but since I'm new to Android it may be a while before I can get through since most root instructions either require access to the internal memory via my computer or access to the phone (past the pattern lock).
If I offer to make a paypal donation could I summon the help of one of the more experienced Android gods that frequent this forum that can help me get through this?
To use odin you need to get into download mode not recovery mode (Volume Down+ Power) but since for some reason that wont work for you, you will have to do something involving the android sdk do you know how to use it?
Genesis1791 said:
To use odin you need to get into download mode not recovery mode (Volume Down+ Power) but since for some reason that wont work for you, you will have to do something involving the android sdk do you know how to use it?
Click to expand...
Click to collapse
On one or two tries, when the device was attached to my laptop I got a yellow on black downloading screen but had no idea what it meant. How does this help me root it? In general the volume down+plus power button didn't do anything but reboot it.
I just downloaded the SDK last night for the last time and haven't succeeded in installing it so have still got a bit of learning to go before I can make it useful.
I have the phone back in my hand now so adding some details:
Holding volume up and down and the same time, then pressing powere gets me to the "Android system recover <2e>" screen with four options:
Reboot system now
reinstall packagages
delete all user data
delete cache data
I've tried all and none will get me out of the username/password screen after reboot. If I select "reinstall packages" it says:
E:can't open /sdcard/update.zip
(No such file or directory)
Installation aborted

[Info] Encrypted tablet and problems

Hello
I did the mistake today to encrypt the tablet with the option provided in the settings menu. After everything went fine and the tablet run for some hours, it force rebooted and now I can login to the tablet but there is a two step login (decryption and the unlock). While decryption works, unlock does not, there is no keyboard displayed and everything seems to "hang". Connection an USB keyboard did not help.
How to reset?
- Connect USB keyboard
- Press Power + (Vol -) while booting the device
- When you can select wipe data and cache, select it
In my case the option was not possible, then do the following:
- Get the update.acer.zip in the dev forum
- Put it an the external SD-Card
- Press Power + (Vol -) while booting the device
- System will be "updated"
- Root your device
- Install a system.img for your region
- Have fun again with the device
Greets
I encrypted the day I got mine (after rooting) and have had no problems. Obviously something went wrong for you, but I don't think you can make the generalization that encryption will fail. It's also possible something on your tablet interfered, or your internal sd is bad or something.
What does encrypting do?
My assumption is that if you encrypt it the government goons at the airports and border can't as easily poke around in it(or at all) if you don't "remember" the password.
Oh yea, and although they're less malevolent, criminals can't access your data if your device is stolen.
Such a broad over the top warning with no basis or facts that encrypting had anything to do with your problems. Don't make such statements unless you're 100% sure it was the encryption process. I encrypted my friends Acer with zero problems.
I changed the title and provided more information when someone has the same problem like me to solve it.
Don't know why my device was "broken", had nothing other installed and nothing changed. Anyway had no chance to retry it, device in the service while back camera cover was not holding in the case.
Thank you for correcting that and happy to see you're fine now.

Unable to Encrypt VZW XT907: CM 10.1.3 Stable w/ CWM 6.0.4.4

Hello everyone,
This is my first post on this forum and am seeking help from the community.
I attempt to encrypt the device with a 5 digit PIN. I get as far as the Android Encrypt logo screen however there is no progress bar or percentage complete. Once the phone's screen goes to sleep (2 minutes after initiation of encrypt procedure), I awaken it and I am immediately brought to the unlock screen to enter the PIN.
I enter the PIN and it brings me back to the Encrypt screen, again with no progress bar/percentage.
This basically can go on forever until I reboot the phone.
When I reboot the device it simply starts up as if the encryption procedure was never initiated. I enter my PIN and check the Encryption settings which show as if I never attempted/initiated encryption.
I then figured maybe it has something to do with the screen turning off so I went into Android debugging settings and enabled "Stay Awake". I attempted the encryption procedure again with the same results with then only difference being that the screen would not go to sleep which meant that it would remain in the Android Encrypt screen until I manually turned the screen off and on. Otherwise same exact result...its as if encryption process isn't starting and is only showing the encrypt logo screen.
I suspect it may be related to the CWM recovery image from information I gleaned from other posts involving different phone models/ROMs but I am not sure how to verify this or address it.
ANY HELP WOULD BE MUCH APPRECIATED!!
Thank you!
Sent from my XT907 using xda app-developers app
Had the same problem
I had the same problem a while ago and the solution that worked for me at the time is here.
But I haven't encrypted my phone in a while, so while I think the solution would still work, I haven't verified it.

Encrypting phone with pattern unlock (4.4.2)

I have just wiped and upgraded my Galaxy s4 to 4.4.2. I would like to fully encrypt my phone and use pattern unlock so I followed this article:
(just google pattern-unlock-an-encrypted-android-phone, I can't post URL)
But even though I have tried this multiple times and unplugged the USB cable (as mentioned in the article) as soon as I hit enter to start the encryption command the screen goes black on the phone and then after about 10min the phone reboots to the unlock screen and it is still unencrypted. I have tried following other articles too but they are all the same in terms of the command you run to encrypt the phone.
Any ideas? How can I get pattern unlock to work with an encrypted Android phone? Yes I know you can't do this via the GUI but then you need to enter a silly long password every single time you want to unlock the phone which is not an option for me. I don't mind entering a long password when turning on the phone but when it comes to unlocking the phones lock screen I would like to use the pattern unlock.
Any one else had any success with this on 4.4.2? Thanks!
BB007BB said:
I have just wiped and upgraded my Galaxy s4 to 4.4.2. I would like to fully encrypt my phone and use pattern unlock so I followed this article:
(just google pattern-unlock-an-encrypted-android-phone, I can't post URL)
But even though I have tried this multiple times and unplugged the USB cable (as mentioned in the article) as soon as I hit enter to start the encryption command the screen goes black on the phone and then after about 10min the phone reboots to the unlock screen and it is still unencrypted. I have tried following other articles too but they are all the same in terms of the command you run to encrypt the phone.
Any ideas? How can I get pattern unlock to work with an encrypted Android phone? Yes I know you can't do this via the GUI but then you need to enter a silly long password every single time you want to unlock the phone which is not an option for me. I don't mind entering a long password when turning on the phone but when it comes to unlocking the phones lock screen I would like to use the pattern unlock.
Any one else had any success with this on 4.4.2? Thanks!
Click to expand...
Click to collapse
Flash a different stock 4.4.2 . maybe its missing some files.

[How-to] Unlock bootloader on Pixel Google Store with "OEM unlock" Disabled -

[How-to] Unlock bootloader on Pixel Google Store with "OEM unlock" Disabled -
I experienced the mishap of locking back the bootloader after flashing the device with my signed custom build. The result was that i was no long able to activate the "OEM unlock" in the "Developer options".
The fact is that If you Signe your build you will not be able to rollback to stock build with ADB update / ADB Sideload / SDRAM zip ... because your Bootloader check the signature.
The only way to do it is to flash the OTA or google Factory Build by Fastboot and for that you need your Bootloader to be unlocked.
Here's in red what i did wrong :
- Activate the "OEM Unlock" in Developer options.
- Unlocked the bootloader with Fastboot
- Flash my signed ROM
- At this time the "OEM Unlock" will turn Gray and we can no more use it to activate or desactivate.
- To test some security functions, i did re-lock my bootloader with fastboot. (Forgot that the OEM unlock is disabled).
Here's what i tryed in order to solve :
I did the steps discribed in [How-to] Unlock bootloader on Verizon Pixel/XL by burduli.
That did not solve my issue but it gives me an idea where to look for. Big Thanks to @burduli (Cedit to @Qu3ntin0 and @LeoTheRomRasta)
Here's the steps i did to solve :
No need to be on internet or so on
I did notice on the Device that there was a Guest User account but i had no way to remove it.
To do so i managed to :
1 - Wipe (factory reset) : Setting / System / Advanced / Reset options / Erase all data (Factory reset) => (Find the entry according to your Built / Android version)
2- Boot in Safe mode (Turn off the device / Hold the power on button till Google screen then release and hold pressed the volum down button until the device finish booting.
3- Go to setting / System / Advanced / Multiple users
4- tap on Guest, then on "Menu" the [...] on top right of the window
5- "Delete Guest User from this device" and confirm (It will seem like nothing done but don't stress it's ok)
6- Ones again Setting / System / Advanced / Reset options / Erase all data (Factory reset)
7- Your Device will reboot and at this time hold pressed the volum down button until the device finish booting (this time it will take longer to finish booting cause android is seting-up all stufs) . (that will boot the device in safe mode).
8- Enable Developer mode (tap 7 times on Build number under "About phone")
9 - Goto Developer options and you are done (The OEM unlock option is back and you can enable or disable it)
You can now reboot your device in normal mode .
In Booltloader mode you can use the "Fastboot flash unlock" or Fastboot OEM unlok command to unlock the bootloader
Will this work on Verizon Android 10 ? Thanx
BelligerentGnome said:
Worked for me.
Click to expand...
Click to collapse
Really ? It worked for u on a Verizon locked bootloader ???
Do you think will work on 2xl verizon?
I just tried it out. Android 10, October update. It didn't work. There's nothing we can do at this point, I'm afraid.
BelligerentGnome said:
It did. I just got one off of Swappa, and the OEM Unlock option was greyed out. This fixed it. I'm running Lineage OS 16 now.
Click to expand...
Click to collapse
You didn't happen to take any screens during the process did you? No offense meant, but it's kind of strange that other than the OP, there's no one else confirming their success. Was it Android 10 with the October update?
Confirmed for myself, does not work. I have only taken the Android 10 update, no other updates since. OEM unlocking still disabled.
Oh verizon, still no one else to hummer this? I will donate who can sure to unlock oem method, hahaha
Going into safe mode there's no way for me to delete the guest user...was hoping it'd work for me - Pixel3/Verizon/Android 10
after doing this (unsuccessfully) my sim card is not being recognized?
This happen to anyone else?
jb
Got a Pixel here with 9.0.0 (PPR2.181005.003.A1, Nov 2018) and this doesn't seem to work. Am I doing something wrong or did they kill it with the November update? Anything I can do?
Edit: Wait no, this is November 2018. Why isn't this working then?
Update2: Got it working. I used a combination of the steps here, followed by the steps listed in the guide linked in the OP (the `pm uninstall --user 0 com.android.phone`). Then I had to wait a few minutes for the OEM unlock to finally become available. Thank you.
Verizon Pixel 1 - unable to get it working still. as a note, when holding down the power down button during the 'erasing data' phase, the phone goes into Android Recovery Mode (shows me the BL, Baseband, Product/Variant, SN, CPO, UFS, DRAM, Boot-slot, Console (DISABLED), Secure Boot (PRODUCTION), Device is (LOCKED)). From here I can enter recovery mode, see barcodes, Power off, or Start.
I tried the following steps:
. Remove Google account and any kind of screen lock (fingerprint, PIN, pattern, etc.) from your device.
. Eject sim card from your device.
. Reset your device. In setup wizard, skip everything, don't connect to WiFi, don't add fingerprint or any kind of screen lock.
- Boot in Safe mode (Turn off the device / Hold the power on button till Google screen then release and hold pressed the volume down button until the device finish booting.
. Go to Developer Options and enable USB debugging.
. Connect your phone to PC.
. Open CMD in adb directory and type
Code:
adb shell pm uninstall --user 0 com.android.phone
- Go to setting / System / Advanced / Multiple users
- tap on Guest, then on "Menu" the [...] on top right of the window
- "Delete Guest User from this device" and confirm (It will seem like nothing done but don't stress it's ok)
- Ones again Setting / System / Advanced / Reset options / Erase all data (Factory reset)
- Your Device will reboot and at this time hold pressed the volume down button until the device finish booting (this time it will take longer to finish booting cause android is seting-up all stufs) . (that will boot the device in safe mode).
- Enable Developer mode (tap 7 times on Build number under "About phone")
- At this step i went to OEM Unlock and saw it was still disabled.
Is this something we can look at solving through the legal system?
I also was unable to get this to work
tldr = Somehow, this worked for me on my Really Blue Pixel running QP1A.191005.007.A3. Initially, my OEM locking was greyed out.
I wanted to downgrade since my Wi-Fi will not connect after updating to Android 10. However, without an unlocked device, I could not downgrade. So, after much searching and trial/error, I tried this on a whim.
While I was not able to find a way to delete the Guest account (as stated in step 4), I was able to "remove" the Guest account, after selecting it and logging into it - at which point, I went back to the Multiple Users menu, and the "remove" option was there; it logged me back in as Owner. Then, after a very long reboot and cramped hands (step 7), I enabled developers mode but, alas, OEM locking is still greyed out. I opened Chrome and visited a few sites and went back in and OEM locking was selectable. Yippee!!
Next, I followed the instructions at https://developers.google.com/android/images and was able to install a previous image. Unfortunately, for some reason, my Wi-Fi still will not stay connected and becomes "Disabled."
jedpublic said:
tldr = Somehow, this worked for me on my Really Blue Pixel running QP1A.191005.007.A3. Initially, my OEM locking was greyed out.
I wanted to downgrade since my Wi-Fi will not connect after updating to Android 10. However, without an unlocked device, I could not downgrade. So, after much searching and trial/error, I tried this on a whim.
While I was not able to find a way to delete the Guest account (as stated in step 4), I was able to "remove" the Guest account, after selecting it and logging into it - at which point, I went back to the Multiple Users menu, and the "remove" option was there; it logged me back in as Owner. Then, after a very long reboot and cramped hands (step 7), I enabled developers mode but, alas, OEM locking is still greyed out. I opened Chrome and visited a few sites and went back in and OEM locking was selectable. Yippee!!
Next, I followed the instructions at https://developers.google.com/android/images and was able to install a previous image. Unfortunately, for some reason, my Wi-Fi still will not stay connected and becomes "Disabled."
Click to expand...
Click to collapse
after you removed the guest account, did you factory reset again?
also, when i hold Volume down during factory reset it will just go into fastboot mode. did you experience the same thing?
tronoftroy said:
after you removed the guest account, did you factory reset again?
also, when i hold Volume down during factory reset it will just go into fastboot mode. did you experience the same thing?
Click to expand...
Click to collapse
Yes I did do the 2nd factory reset, which may be significant based on other people's reports...
If I recall correctly, the second time I factory reset, I held Volume Down from the moment I confirmed the restart. Honestly, I was trying so many different things though, so everything kind of blurred together.
One thing to point out is that my Really Blue Pixel was obtained from Google directly, not Verizon.
I've just bought myself a brand new Pixel 1 XL - 128GB Factory Unlocked. Sadly I wasn't aware of all these issues with OEM unlocking via the Developer Menu. Not knowing the drawbacks, I casually breezed through all the upgrades and reached 10.0 (QP1A.191005.007.A3) state. It was then I realised I cocked up...:crying: because no matter what combination of instructions I try in this (and other) threads, I simply cannot get the greyed out menu to budge! I have tried at least a dozen factory resets, countless adb removals, with/without WiFi, with/without SIM, with/without Google sign in, with/without Safe Mode, with/without Guest User Profile delete and so on.... all to no avail:crying:
I am lost at the moment... I'm sure there's other in the same boat as me. I really do hope there is a solution for all of us out there.. any one have any ideas?
For those in previous versions, I can only think of using zero-day exploit with an app such as Qu1ckR00t. But we would need a dev or something to tailor such app for our Pixel. Any other idea is welcome!
I gave up and sold my Pixel 1 XL - thinking of getting a used Pixel 2 instead. I just need this as my backup phone and for travelling. My primary is the Pixel 4 XL.
dfx12345 said:
Got a Pixel here with 9.0.0 (PPR2.181005.003.A1, Nov 2018) and this doesn't seem to work. Am I doing something wrong or did they kill it with the November update? Anything I can do?
Edit: Wait no, this is November 2018. Why isn't this working then?
Update2: Got it working. I used a combination of the steps here, followed by the steps listed in the guide linked in the OP (the `pm uninstall --user 0 com.android.phone`). Then I had to wait a few minutes for the OEM unlock to finally become available. Thank you.
Click to expand...
Click to collapse
Can you explain the steps you used for the OEM unlock? I have the same Build and update as your device. Please help me, i tried every method possible and almost give up. I have verizon pixel 9.0.0 PPR2.181005.003.A1, Nov 2018
Taswim said:
Can you explain the steps you used for the OEM unlock? I have the same Build and update as your device. Please help me, i tried every method possible and almost give up. I have verizon pixel 9.0.0 PPR2.181005.003.A1, Nov 2018
Click to expand...
Click to collapse
My understanding is that you're out of luck with a Verizon Pixel. Mine was a non-Verizon Pixel.

Categories

Resources