Related
I cannot use the default "Encrypt Phone" option on the settings menu of my Nexus 4. When used, it just reboots the phone and I have done this process over 5 times with no success.
I used the Android Nexus 4 ToolKitv2.0.0 and the recommended root tools and am running obviously 4.2.2.
Any reason why it's doing this? Thanks.
Bubblewhip said:
I cannot use the default "Encrypt Phone" option on the settings menu of my Nexus 4. When used, it just reboots the phone and I have done this process over 5 times with no success.
I used the Android Nexus 4 ToolKitv2.0.0 and the recommended root tools and am running obviously 4.2.2.
Any reason why it's doing this? Thanks.
Click to expand...
Click to collapse
Are you using a custom recovery - TWRP or CWM? You need to be using the stock recovery image to encrypt your phone. The nexus toolkit will allow you to re-flash the stock recovery.
One the stock recovery has been re-flashed, you should be able to encrypt your phone. I had to re-flash stock recovery, reboot the phone, then reflash the stock recovery again.
Once the device has been successfully encrypted using the stock recovery, you can re-flash either the TWRP or CWM as your recovery. TWRP supports reading data from encrypted devices, so it is probably the way to go (not sure if CWM dows now, but it didn't last time I looked).
Does encrypting the phone make a dramatic difference in speed (as in slow down) for the phone or does it mainly affect boot times?
Thanks for the tip about having stock recovery as I also wanted to encrypt phone as well. Would one have to de-encrypt phone then install custom recovery to update a custom Rom (I'm running paranoid android) then flash to stock recovery to encrypt phone again- seems long winded :-\
Just from reading the above post once flashed to stock recovery and then encrypted device, it's okay to flash back to TWRP and still have an encrypted device?
Is there another way to do this when running a custom rom?
Sent from my Nexus 4
randomvector said:
Does encrypting the phone make a dramatic difference in speed (as in slow down) for the phone or does it mainly affect boot times?
Thanks for the tip about having stock recovery as I also wanted to encrypt phone as well. Would one have to de-encrypt phone then install custom recovery to update a custom Rom (I'm running paranoid android) then flash to stock recovery to encrypt phone again- seems long winded :-\
Just from reading the above post once flashed to stock recovery and then encrypted device, it's okay to flash back to TWRP and still have an encrypted device?
Is there another way to do this when running a custom rom?
Sent from my Nexus 4
Click to expand...
Click to collapse
I haven't noticed a difference in speed, however technically there will be a little bit of a slowdown.
I'm running stock Android, so I don't know how well it plays with custom ROMs, but you can re-flash a TWRP recovery after encrypting your phone with stock Android on it.
If the custom ROM installation wipes the data partition, it would remove the encryption.
I've tried flashing stock recovery using Nexus 4 Toolkit and recovery is back to stock. However the phone is still just rebooting when I press encrypt device. What am I doing wrong?
For some reason I had to reflash the stock recovery, reboot, then reflash the stock recovery again. No idea why, but it worked for me!
Sent from my Nexus 4 using Tapatalk 2
Booted back into stock recovery device is still rebooting itself after hitting the encrypt button, Encryption did not happen.
Found the problem but I can't seem to fix it. Flashing the stock recovery doesn't seem to actually do it. When I boot to recovery when flashed to stock, it just shows the android mascot with an open chest and a warning symbol. Have reflashed many times over 5, and still doesn't work. It seems like I need the actual image recovery file. something like Recovery.img?
Bubblewhip said:
Found the problem but I can't seem to fix it. Flashing the stock recovery doesn't seem to actually do it. When I boot to recovery when flashed to stock, it just shows the android mascot with an open chest and a warning symbol. Have reflashed many times over 5, and still doesn't work. It seems like I need the actual image recovery file. something like Recovery.img?
Click to expand...
Click to collapse
The android with a warning symbol is the normal symbol of stock recovery.
However, I wonder, if you could solve the problem? My nexus doesn't want to encrypt itself too. Flashed stock recovery already twice and it just keeps rebooting when I start the encryption process.
Quick update: After trying it several times in a row it finally worked (after the fourth time or so). I have no clue why it didn't work before as I haven't change anything.
c_m_l said:
Quick update: After trying it several times in a row it finally worked (after the fourth time or so). I have no clue why it didn't work before as I haven't change anything.
Click to expand...
Click to collapse
Thanks for your perseverance! I spent half a day trying to encrypt my rooted Galaxy S4 with the similar problem as you:
I go into System Settings, click "Encrypt Phone", then I get the green android and the phone just reboots itself as normal.
What worked for me: AIRPLANE MODE.
I was rebooting it time after time with no effect (following your suggestion). Once I turned on the Airplane Mode, the encryption started working.
My Current Setup:
Android 4.2.2 Jelly Bean
Samsung Galaxy S4 Google Edition (GT-I9505g) rooted via CF auto root. + Full disk encryption!
Works perfectly!
Now I can have different passwords for disk encryption (long strong password) and for locker screen (simple)
JohnnyBBB said:
Thanks for your perseverance! I spent half a day trying to encrypt my rooted Galaxy S4 with the similar problem as you:
I go into System Settings, click "Encrypt Phone", then I get the green android and the phone just reboots itself as normal.
What worked for me: AIRPLANE MODE.
I was rebooting it time after time with no effect (following your suggestion). Once I turned on the Airplane Mode, the encryption started working.
My Current Setup:
Android 4.2.2 Jelly Bean
Samsung Galaxy S4 Google Edition (GT-I9505g) rooted via CF auto root. + Full disk encryption!
Works perfectly!
Now I can have different passwords for disk encryption (long strong password) and for locker screen (simple)
Click to expand...
Click to collapse
Old thread, same issue, HTC One w/ OmniROM (m7att). My Nexus 10 did it as well.
The person saying to reflash stock? DOn't listen to that. Doesn't need to be done. Encrypted all my devices w/ TWRP installed.
Airplane mode DID work, though.
I just had this issue with my N4, too. I read on the Google Product Forum that this was because a process prevents from unmounting the /data partition. ("Nexus 5 is not going through encryption process" - can't post link due to being new)
With that in mind, I rebooted into safe mode and then tried again and it worked on the first try (At least it started the encryption process, it's at 10% now)
I had this problem for a looooong time. Thankfully, I seem to have discovered a solution for those still encountering this issue.
Turn off SuperSU (Settings -> More -> Application manager -> All -> SuperSU -> Turn Off)
Reboot into Safe Mode (How to)
Run encryption (Settings -> More -> Security -> Encrypt Device)
Turn on SuperSU after complete (Settings -> More - > Application manager -> Turned Off -> SuperSU -> Turn On)
On my i747 I installed Omni ROM 4.4.3-20140620-d2lte-HOMEMADE. After install and reboot I noticed the load time was in excess of five minutes from the moment the Omni logo splash appears. Is this normal? I can't be sure but I think each boot takes longer, (so tired right now). Any suggestions?
I am experiencing the same. I flashed to my SPH-l710 using the latest from http://forum.xda-developers.com/showthread.php?t=2591298.
I would love to go back to using this rom. I absolutely love it miles above CM but the boot time is easily in excess of 10 minutes.
exarkun631 said:
On my i747 I installed Omni ROM 4.4.3-20140620-d2lte-HOMEMADE. After install and reboot I noticed the load time was in excess of five minutes from the moment the Omni logo splash appears. Is this normal? I can't be sure but I think each boot takes longer, (so tired right now). Any suggestions?
Click to expand...
Click to collapse
Talk to whomever provided the build, as that is not an officially supported device (in addition to not being present at dl.omnirom.org - the HOMEMADE part of the filename is a dead giveaway).
First bootup after installation is always long - if subsequent boots are long there's a problem though.
It is normal if it is your first boot after flashing new rom...
It just that the Android is installing (preparing apps for first use)
The same will happen when you clear Dalvik cache or change runtime from Dalvik to ART.
If it is the same on second and other boot then it is problem with your rom
Dodgy apps (or heaps of apps) can cause that too. Is it still slow if you do a factory reset ? (do a backup before hand so you can restore all your data). As pointed out above if you do a factory reset the initial boot will still be slow
Thanks everyone. I went ahead and wiped the drive then installed CM11 for the i747 (d2att) and all is well with booting. One day I will check out omnirom again because the features are just insane!
My i9505 was running stock KitKat from Samsung and I tried to install CM13 ROM.
So I used Odin to root the phone and installed TWRP 2.8.6.0. After that I flashed the CM13 ROM and the Gapps Nano.
I got as far as rebooting into CM13. But then the "Google Play Store has stopped working" message keeps popping up starting from the initial setup phase. I ignored the message and went on to setup the wifi but couldn't progress any further. The wifi was detected and connected but then it was stuck on the Checking Connection/Software Update step.
I tried to reflash the rom and gapps again to no avail. The third time to Format Data from TWRP before reflashing - still didn't make a difference.
What's worst is now I cannot even get into TWRP! Whenever I press Vol Up + Power + Home, it will show the small 'entering recovery' message momentarily on the top left corner but then it phone simply restarted again.
I tried re-flashing TWRP using Odin, but still didn't work.
I'm stuck now, cannot get into the OS nor the recovery. Any suggestion as to what to do?
Thank you.
vizavalk said:
My i9505 was running stock KitKat from Samsung and I tried to install CM13 ROM.
So I used Odin to root the phone and installed TWRP 2.8.6.0. After that I flashed the CM13 ROM and the Gapps Nano.
I got as far as rebooting into CM13. But then the "Google Play Store has stopped working" message keeps popping up starting from the initial setup phase. I ignored the message and went on to setup the wifi but couldn't progress any further. The wifi was detected and connected but then it was stuck on the Checking Connection/Software Update step.
I tried to reflash the rom and gapps again to no avail. The third time to Format Data from TWRP before reflashing - still didn't make a difference.
What's worst is now I cannot even get into TWRP! Whenever I press Vol Up + Power + Home, it will show the small 'entering recovery' message momentarily on the top left corner but then it phone simply restarted again.
I tried re-flashing TWRP using Odin, but still didn't work.
I'm stuck now, cannot get into the OS nor the recovery. Any suggestion as to what to do?
Thank you.
Click to expand...
Click to collapse
Format Data from twrp sometime corrupts the file system and brick the phone. (It's happened to me once)
The best way is to flash official firmware via odin and start from there.
I see - I'll try re-flashing the official rom. Btw, would you recommend CWM recovery instead then? Honestly, I'm not very proficient with this whole thing. The reason why I formatted was because I still could see all of my old folders in the phone memory. So I thought Factory Reset didn't really clean up my old rom data.
What do I have to do if I want to start with a really clean slate with CM13 (after reflashing the official one first)?
Also, I still have the issue of CM13 setup being stuck at the Software Update step (right after Wifi setup). Any clue why that happened?
Thanks for taking the time to reply.
vizavalk said:
I see - I'll try re-flashing the official rom. Btw, would you recommend CWM recovery instead then? Honestly, I'm not very proficient with this whole thing. The reason why I formatted was because I still could see all of my old folders in the phone memory. So I thought Factory Reset didn't really clean up my old rom data.
What do I have to do if I want to start with a really clean slate with CM13 (after reflashing the official one first)?
Also, I still have the issue of CM13 setup being stuck at the Software Update step (right after Wifi setup). Any clue why that happened?
Thanks for taking the time to reply.
Click to expand...
Click to collapse
CWM is outdated. Your best bet is TWRP. Try version 3.0.0.
Factory reset doesn't wipe your internal memory, if that's what you mean, you will have to do it manually.
Also, I recommend wiping data, cache, dalvik and system partitions manually from the advanced wipe menu. Factory reset only wipes data and caches, not system.
Oh, and about that stuck at setup issue, just skip that step if possible, you can still change that crap later
If you are unable to set up the ROM, you could flash back to a completely stock ROM and start over.
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
vizavalk said:
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
Click to expand...
Click to collapse
The sd card has nothing to do with it.
Sometimes gapps don't work on certain roms.
Just try another package.
If you use A-Gapps, the whole first time setup step will be skipped altogether. So that means that you won't run into the risk of getting stuck at that step again.
Or, after flashing the rom, you could use the recovery file manager to delete the setupwizard.apk after you flashed gapps. That should also prevent the initial setup process from initializing at first boot.
vizavalk said:
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
Click to expand...
Click to collapse
You probably used Opengapps. That also gives me a lot of errors.
Use Bankgs Gapps instead. They always work for me.
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
GDReaper said:
The sd card has nothing to do with it.
Sometimes gapps don't work on certain roms.
Just try another package.
If you use A-Gapps, the whole first time setup step will be skipped altogether. So that means that you won't run into the risk of getting stuck at that step again.
Or, after flashing the rom, you could use the recovery file manager to delete the setupwizard.apk after you flashed gapps. That should also prevent the initial setup process from initializing at first boot.
Click to expand...
Click to collapse
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
Lennyz1988 said:
You probably used Opengapps. That also gives me a lot of errors.
Use Bankgs Gapps instead. They always work for me.
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
Click to expand...
Click to collapse
There are two files - one says Dynamic. But the file sizes are exactly the same. Is there any difference?
vizavalk said:
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
There are two files - one says Dynamic. But the file sizes are exactly the same. Is there any difference?
Click to expand...
Click to collapse
Not that I know. Just pick the one without Dynamic.
vizavalk said:
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
Click to expand...
Click to collapse
The initial setup process is related to gapps. And I don't recall there being any software update requests during the initial setup. It tells me to wait while it scans for network and WiFis, but I always skip those steps.
Open gapps sometimes work and sometimes they don't. It varies from day to day, since they are updated daily.
Just find a gapps package that works and stick to it until another version of android.
I just want to report back that my CM13 works perfectly with Banks GApps. Thanks to everyone who has helped!
I'm not sure what happened with my US Axon 7. I was getting it ready to give to my son, and now it won't boot. Even with a full wipe (including system) and reinstall of the OS. It tries to boot, but just sits at the Google animation forever.
Here is basically the steps of what happened during the wipe/install of the unofficial RR Oreo build:
- Wiped everything
- Flashed the B32+B10 bootstack (A2017X_BootStack_B32+B10.zip)
- Flashed the latest (at the time) unofficial RR Oreo build (RR-O-v6.0.0-20180511-axon7-Unofficial.zip)
- Flashed opengapps micro (open_gapps-arm64-8.1-micro-20180512.zip)
- Flashed Magisk 16.0 (Magisk-v16.0.zip)
- Booted up and setup the phone for his google account
- Rebooted multiple times during setup
- Installed TiBu and froze the apps I normally freeze for the kids.... things they don't need
- Rebooted one final time and got stuck on the boot screen
- Re-performed steps above (minus setup... because I still can't get it to boot)
The best I can figure is that I froze something I shouldn't have... but a wipe and reinstall should have fixed that. I don't understand why it wouldn't. I've even wiped system.
I'm going to see if I saved a backup somewhere, as it's not on the phone. I can still get into recovery and such, which is good.
Flapjack said:
I'm not sure what happened with my US Axon 7. I was getting it ready to give to my son, and now it won't boot. Even with a full wipe (including system) and reinstall of the OS. It tries to boot, but just sits at the Google animation forever.
Here is basically the steps of what happened during the wipe/install of the unofficial RR Oreo build:
- Wiped everything
- Flashed the B32+B10 bootstack (A2017X_BootStack_B32+B10.zip)
- Flashed the latest (at the time) unofficial RR Oreo build (RR-O-v6.0.0-20180511-axon7-Unofficial.zip)
- Flashed opengapps micro (open_gapps-arm64-8.1-micro-20180512.zip)
- Flashed Magisk 16.0 (Magisk-v16.0.zip)
- Booted up and setup the phone for his google account
- Rebooted multiple times during setup
- Installed TiBu and froze the apps I normally freeze for the kids.... things they don't need
- Rebooted one final time and got stuck on the boot screen
- Re-performed steps above (minus setup... because I still can't get it to boot)
The best I can figure is that I froze something I shouldn't have... but a wipe and reinstall should have fixed that. I don't understand why it wouldn't. I've even wiped system.
I'm going to see if I saved a backup somewhere, as it's not on the phone. I can still get into recovery and such, which is good.
Click to expand...
Click to collapse
Which apps do you freeze? If you froze some Google apps you can just use the pico package and avoid having to use TiBU entirely
You're saying that after doing the whole installation you set up the ROM, but after you freeze apps with titanium and reboot the phone refuses to boot?
Choose an username... said:
Which apps do you freeze? If you froze some Google apps you can just use the pico package and avoid having to use TiBU entirely
Click to expand...
Click to collapse
I don't remember exactly... nothing I haven't frozen on their phones before.
You're saying that after doing the whole installation you set up the ROM, but after you freeze apps with titanium and reboot the phone refuses to boot?
Click to expand...
Click to collapse
It seems to be that way. I had already installed Magisk, but it's not like I installed Xposed or anything "dangerous" to the operation of the phone. The only thing I can think of is I froze something that kept it from booting. But if that's the case, why wouldn't reinstalling the ROM fix it? Wouldn't that fix anything I changed/froze?
Flapjack said:
I don't remember exactly... nothing I haven't frozen on their phones before.
It seems to be that way. I had already installed Magisk, but it's not like I installed Xposed or anything "dangerous" to the operation of the phone. The only thing I can think of is I froze something that kept it from booting. But if that's the case, why wouldn't reinstalling the ROM fix it? Wouldn't that fix anything I changed/froze?
Click to expand...
Click to collapse
well, if you wiped and installed everything again it should work...
Something must have been wrong with the ROM itself. I don't get it, since it worked fine the first install. I installed AOSP instead and it booted right up. I'm going to take a full backup, freeze the things I normally freeze, then see what happens.
I was having a very similar issue while trying to move to exactly the same ROM. My problem was that I was accidentally encrypting the phone (I didn't realize that this is what the "require pin at startup" prompt was doing). If TWRP is asking you to put in a pin number every time you boot into recovery, then your phone is encrypted. RR ROM (or at least the most common version of it) does not support encryption, so it will refuse to boot.
To get rid of encryption, you have to select the "format data" option in the wipe menu. You can't just wipe the usual partitions.
I can't be certain that this is your issue, but hopefully it helps.
beokabatukaba said:
I was having a very similar issue while trying to move to exactly the same ROM. My problem was that I was accidentally encrypting the phone (I didn't realize that this is what the "require pin at startup" prompt was doing). If TWRP is asking you to put in a pin number every time you boot into recovery, then your phone is encrypted. RR ROM (or at least the most common version of it) does not support encryption, so it will refuse to boot.
To get rid of encryption, you have to select the "format data" option in the wipe menu. You can't just wipe the usual partitions.
I can't be certain that this is your issue, but hopefully it helps.
Click to expand...
Click to collapse
Not similar at all. In your case the ROM would boot fine, but it woupd fail to load your data, so it asks for a password that not necessarily exists. In his case the ROM never gets to boot
Choose an username... said:
Not similar at all. In your case the ROM would boot fine, but it woupd fail to load your data, so it asks for a password that not necessarily exists. In his case the ROM never gets to boot
Click to expand...
Click to collapse
You misunderstand. I could only boot RR once, and if I accidentally encrypted the device during setup or afterward, the next time I tried to restart, it would be stuck on the boot screen. All subsequent reinstalls also got stuck on the boot animation since I wasn't removing encryption even if I wiped data, system, cache, etc. Moving to AEX allowed me to boot with encryption, and it was at that point that I realized my mistake. That sounds precisely like what is happening to flapjack, except that the cause may or may not be the same since he got through multiple boots the first time and presumably had already setup a pin/password on one of the first boots.
Immediately after the pin is setup should be when it asks if you want to require the pin on startup (aka if you want to encrypt), so if he opted to do that after setting everything up rather than on the very first boot, he may have exactly the same issue I had.
I i had to reflash the firmware the correct one TB-X104F_S000024_180930_ROW_DCC. Anyway it wasn't booting at all before i flashed. Now it boots, shows the logo etc and constantly says Encryption unsuccessful!, so i reset it and factory reset it but nothing changes.
I have no idea where else to go, bootloader is locked and all i can do is flash the firmware. Would there be a way to remove this from the files within the firmware?. It seems like android is there in the background but i can't get away from that encryption unsuccessful screen!
Sorry if none of this makes sense.
Yo. I got the same tablet bro. Been trying to figure out a custom recovery for her. A stock ROM would be great to have and I haven't been able to find one anywhere. Might I inquire as to where you found yours? It would be a huge relief to know I can fix it if I break it lol.
encryption
If you download the Lenovo MOTO smart assistant from Lenovo support it has a resque option. I also used that to root my tb-x104f. It downloads the original everything and if you take the boot image from the file it downloads and replace it in one that has been modified from magisk it will rescue it and you will have root also thatd what I did with mine
same problem here, reflashed with stock rom. and not resloved
frankieuk said:
I i had to reflash the firmware the correct one TB-X104F_S000024_180930_ROW_DCC. Anyway it wasn't booting at all before i flashed. Now it boots, shows the logo etc and constantly says Encryption unsuccessful!, so i reset it and factory reset it but nothing changes.
I have no idea where else to go, bootloader is locked and all i can do is flash the firmware. Would there be a way to remove this from the files within the firmware?. It seems like android is there in the background but i can't get away from that encryption unsuccessful screen!
Sorry if none of this makes sense.
Click to expand...
Click to collapse
Did you fix this issue?
I am having the same problem.
Thanks
Same problem here (my error reads "Decryption unsuccesful", but I think it's the same as yours).
After a few tries, I believe that it is a problem with the internet connection. After the factory reset, if I skip the wifi connection step, it starts normally. And it is completely usable. I can load pdf documents or apks by the usb from a computer and it runs correctly. But whenever I try to set the wifi connection, it updates something and it causes the tablet that the next time I turn it off, I find the error on the picture when turning on. It asks for a password and no matter which password you enter, then it delivers this message.
In resume, right now it is a completely functional tablet if you NEVER connect it to the internet and load anything you need via usb or bluetooth.
I tried to reset it with Lenovo Smart Assistant, but the result is the same.
I am looking for custom roms to try if it's something about the stock rom, but I haven't found any. Can anyone reccomend me a rom for Lenovo E10 X104F 2GB?
Solution: (Worked for me)
Format Data as F2FS in TWRP. (Advanced Wipe)
Then reboot and wait.