Related
Recovery: ClockworkMod 5.5.0.2
ROM: MCR Ir4
So, I've had my GN for about 5 days now, and wanted to experiment with the device encryption option. So, I followed the steps, and let the phone do it's thing, and an hour later it was encrypted. Now when the phone boots, it shows the boot animation, then prompts for the passcode, then remounts the unencrypted partitions as expected.
So, I starting having a look at how this impacts the usability, and now I have a bit of a problem. Firstly, as (at least) the whole /data partition is encrypted, it's not possible to access the 'sd card' from recovery, meaning that it's not possible to either create a backup or restore from one (as CWM can't mount the sdcard to do so). On realising this, I decided that I was done experimenting, and wanted to go back to the unencrypted state. How? Well, I can't.
If you go back to the security menu, the area that was used to start encryption is grayed out...it seems to have been a one-way process. At the time it mentionted that the only way to access the device if the encrytion passcode was lost would be to do a Factory Reset, so, this was what I tried next. The device restarted, showed the android with his front open and the cog on display for a few seconds, then restarted again, but took me back to where I was before - the wipe had not occurred.
Next, I tried to do a wipe from CWM - here I at least got a bit more feedback as to what was going on. It seems CWM needs to mount a given partition before it can wipe it, and as it can't do that, it couldn't wipe anything, so that didn't achieve anything either.
So, I'm now in a position where I have an encrypted device that I can't wipe, either through the normal factory reset in the Android UI, or via CWM recovery. I know that the collective smarts of this forum is a power to be reconed with, and as I've now reached the limits of my knowledge of working with this kind of thing, I'm hoping someone will be able to help me out.
My thinking so far: As the suggested method of recovering from an encrypted state is to do a factory reset, it would suggest that there is either
a) a bug in ICS that isn't handling the wipe of an encrypted device correctly
b) an incompatibility with CWM that is conflicting with the OS' ability to execute the wipe (as CWM can't interact with the encrypted partitions)
c) a bug in Paul's MCR ROM (much less likely IMO)
I hope that all makes sense, and that someone has some thoughts on where to go from here - thanks!
Flash stock images through fast boot?
Sent from my Galaxy Nexus using xda premium
I've just been reading up on fastboot since posting (I think I've only ever used it via other people's scripts before), and assuming that it can overcome the problem, I was thinking that maybe it would be able to do the wipe (though obviously I don't want to end up with a £500 paperweight...)
If I were to flash a stock image, how would I go about that? (It's been a long time since I've loaded a rom not via a recovery)
EDIT: Going to try a manual nandroid restore (from a backup made just before encrypting) as described here - http://wiki.cyanogenmod.com/wiki/Fastboot
Ok, flashed a stock image and back to factory state again so now all working (phew) - thankful I was doing this on a Nexus device where fastboot was easily available.
While this has solved the problem, it didn't really identify the cause - I'd be curious to hear of others' experiences with using the encryption in 3.0+.
Please keep questions out of the development section. Thank you
Sent from the MIUI powered 3d
jayharper08 said:
Please keep questions out of the development section. Thank you
Sent from the MIUI powered 3d
Click to expand...
Click to collapse
Apologies - posted here as thought it could have been development related (Possible CWM/MCR bug).
Don Vincenzo said:
Apologies - posted here as thought it could have been development related (Possible CWM/MCR bug).
Click to expand...
Click to collapse
No worries. Dev section is just for strictly developed roms and kernels and such. No biggie
Wish I could help you with the answer though :/
Sent from the MIUI powered 3d
Don Vincenzo said:
Recovery: ClockworkMod 5.5.0.2
ROM: MCR Ir4
So, I've had my GN for about 5 days now, and wanted to experiment with the device encryption option. So, I followed the steps, and let the phone do it's thing, and an hour later it was encrypted. Now when the phone boots, it shows the boot animation, then prompts for the passcode, then remounts the unencrypted partitions as expected.
So, I starting having a look at how this impacts the usability, and now I have a bit of a problem. Firstly, as (at least) the whole /data partition is encrypted, it's not possible to access the 'sd card' from recovery, meaning that it's not possible to either create a backup or restore from one (as CWM can't mount the sdcard to do so). On realising this, I decided that I was done experimenting, and wanted to go back to the unencrypted state. How? Well, I can't.
If you go back to the security menu, the area that was used to start encryption is grayed out...it seems to have been a one-way process. At the time it mentionted that the only way to access the device if the encrytion passcode was lost would be to do a Factory Reset, so, this was what I tried next. The device restarted, showed the android with his front open and the cog on display for a few seconds, then restarted again, but took me back to where I was before - the wipe had not occurred.
Next, I tried to do a wipe from CWM - here I at least got a bit more feedback as to what was going on. It seems CWM needs to mount a given partition before it can wipe it, and as it can't do that, it couldn't wipe anything, so that didn't achieve anything either.
So, I'm now in a position where I have an encrypted device that I can't wipe, either through the normal factory reset in the Android UI, or via CWM recovery. I know that the collective smarts of this forum is a power to be reconed with, and as I've now reached the limits of my knowledge of working with this kind of thing, I'm hoping someone will be able to help me out.
My thinking so far: As the suggested method of recovering from an encrypted state is to do a factory reset, it would suggest that there is either
a) a bug in ICS that isn't handling the wipe of an encrypted device correctly
b) an incompatibility with CWM that is conflicting with the OS' ability to execute the wipe (as CWM can't interact with the encrypted partitions)
c) a bug in Paul's MCR ROM (much less likely IMO)
I hope that all makes sense, and that someone has some thoughts on where to go from here - thanks!
Click to expand...
Click to collapse
just connect via adb in recovery and format it via mkfs.ext4...
and... then what? Once the partition is formatted - it seems it would need to be populated? Or does some subsequent restoration - once the /data partition is accessible - will re-create any files / folder structure in this filesystem?
Hey there,
This is the only forum i'm permitted to post yet. So I hope i'm correct.
Anyway:
I installed windows 8.1 on my Surface RT. Later I installed the 8.0 recovery image trough USB and the jailbreak and all worked fine. After that I wanted to try 8.1 again and also that worked fine.
But now, when I want to re-install the 8.0 recovery image I don't get the bitlocker screen anymore. System restore won't work. I've tried decrypting the drive, but that also didn't work. Bitlocker is off on both my primary disk and usb. When I choose the default system repair I get a notice the system partition isn't allowing and when I choose the full reset I also get an error.
When I use bcd to scan for OS I don't get any results. 8.1 is working fine at the moment , but I'd like to install 8.0 again. Anyone who knows how?
Thanks.
I'm having the same problem.
gentrix said:
Hey there,
This is the only forum i'm permitted to post yet. So I hope i'm correct.
Anyway:
I installed windows 8.1 on my Surface RT. Later I installed the 8.0 recovery image trough USB and the jailbreak and all worked fine. After that I wanted to try 8.1 again and also that worked fine.
But now, when I want to re-install the 8.0 recovery image I don't get the bitlocker screen anymore. System restore won't work. I've tried decrypting the drive, but that also didn't work. Bitlocker is off on both my primary disk and usb. When I choose the default system repair I get a notice the system partition isn't allowing and when I choose the full reset I also get an error.
When I use bcd to scan for OS I don't get any results. 8.1 is working fine at the moment , but I'd like to install 8.0 again. Anyone who knows how?
Thanks.
Click to expand...
Click to collapse
I'm having exactly the same problem. And if I'm following the recovery image instructions, the cmdline instructions for the step after what should be "Skip this drive" just results in seeing that there are 0 windows installations.
shapshank said:
I'm having exactly the same problem. And if I'm following the recovery image instructions, the cmdline instructions for the step after what should be "Skip this drive" just results in seeing that there are 0 windows installations.
Click to expand...
Click to collapse
I wonder if anyone else managed to install:
the 8.1 update
then install 8.0 via the recovery image
then jailbrake it
then install 8.1 again
and then (there comes trouble) install 8.0 via recovery again....
Because i still can't figure any way to install 8.0 again ..
Hello,
I am a happy owner of OnePlus 3 and at the beginning when I got this Smartphone and run it, I had to set-up a Pin which was also used for Encryption,
due to the decision that I wanted to change it, I have tried numerous things to do this, either via System -> Security, System -> Lock Screen or TWRP Recovery.
Then I have stumbled upon a wiping feature in TWRP. (TWRP Menu -> Wipe) where there was a couple of options like Advanced Wipe, Format Data and Swipe to Factory Reset. So I have
decided to see what Format Data does which showed me the following statement before I continued with it "Format Data will wipe all of your apps, backups, pictures, videos, media and
removes encryption on internal storage". Well when it said it removes the encryption I have proceeded because at this point where all of the methods failed I wanted to remove and
re-encrypt my OnePlus 3 again in order to change my encrypting pin. Ok, cool this worked perfectly except that now I can't restore my original rom or encrypt my OnePlus 3 again ....
Then I have flashed CyanogenMod 13 Nightly from August (The latest one on the CyanogenMod website) and when I went into System -> Security there was Encrypt button instead of saying
Encrypted at the top of the menu then I have played around with setting up a new Pin/Password and when I went throug all the process at the end the following happens within a few
seconds: a green dissasembled android shows then screen turns black and returns to lock screen. I checked if OnePlus 3 is encrypted and is not. This is not the normal as usually
encrypting takes some time.
Also, I have tried to restore my original rom which came with my smartphone and was encrypted, when I restored it, OnePlus 3 stucks on the first screen showing OnePlus logo on the
middle of the screen and text "Powered by Android" on the bottom of the screen.
I presume that CyanogenMod 13 encryption is broken or that I shouldn't have format Data ?
Is there any way that I can encrypt my smartphone again ?
P.S I know that OnePlus 3 encryption is handled by Hardware.
You can try downloading the official OxygenOS ROM, flashing it and trying to encrypt again. Last I tried doing it on Sultan's CM13, it didn't work, so it might be a CM problem.
As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.
abhibnl said:
As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.
Click to expand...
Click to collapse
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?
formating data with TWRP -28 will decrypt your phone, it's madethis way so it can work on beta 9 and f2fs ...
that said i had encrypted device before on CM
so if you're not using beta 9 and your data partition is not f2fs, you can have an ecrypted device, the easiest way is to sideload official rom 3.2.8 (make sure you're on stock recovery and start adb sideload from there) , after the sideload the phone will be encrypted, if you're staying at MM, fastboot TWRP .22 or 23 or just the official in case .28 decrypts the phone.
Gliop022 said:
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?
Click to expand...
Click to collapse
Well man i want you be on as much safe side as possible. When you perform factory data reset on stock recovery, it will wipe and reformat your internal memory as well. TWRP only wipes data partition, and you need to format whole internal memory manually. But stock is recommended for full compatibility.
Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !
Gliop022 said:
Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !
Click to expand...
Click to collapse
Hello Gliop022,
Do you know if flashing OxygenOs stock from TWRP 3.1.0 encrypts the phone or do I have to be on stock recovery?
Then once the phone is encrypted, are you able to flash an OOS based ROM (e.g. FreedomOs) and keep the encryption?
Hi!
Does Magisk (including root, etc.) work flawlessly on a Pixel C with Android 8.1? Or is better to stay with 8.0 and wait a little bit?
Thanks in advance and kind regards,
star3141.
It works, initially it would force close but now seems stable. I used v14.5 beta.
On the other hand super su by chainfire does not work. Would flash but app missing. Downloading from play store and updating binaries through app causes boot loop.
v14.5 works perfectly here, no problems at all.
Hi!
Thanks for the replies. Maybe I will give it a try at Christmas or alternatively wait for the first update of 8.1 in January.
Hello!
Today, I gave it a try but unfortunately faced some kind of total reflection.
1. I downloaded and flashed the latest android factory image (ryu-opm1.171019.016 = 8.1 from Feb. 2018) from Google.
2. I downloaded and booted (without installing) twrp-3.2.1-0-dragon by means of "fastboot boot twrp-3.2.1-0-dragon.img"
3. In TWRP I mounted the system partition rw
However, after mounting the system partition rw, android won't boot into the system anymore. I am alway getting the green android guy laying on its back with "No command". When I boot into TWRP and mount /system in ro-mode, then will boot afterwards without any problems. So the problem must be related to mounting /system in rw-mode by TWRP.
I have also tried twrp-3.0.0-0-dragon-ryu-02112016-1.img, which worked on my previous 8.0 installation, but it won't work in this 8.1 release anymore.
Any ideas how to get rid of this problem?
Thanks in advance and kind regards,
star3141.
Hello!
I found a solution!
If someone else suffers from similar problems then try the following which hopefully will fix everything: :fingers-crossed:
1. Download and flash the latest (in my case Android 8.1 from Feb. 2018) android factory image from Google.
2. Complete the standard android setup procedure and, when the system is up and running, enable "USB debugging" in the "Developer Options".
3. Restart your device in bootloader mode by "adb reboot bootloader".
4. Format your /data partition by "fastboot format userdata" to remove the filesystem encryption.
5. Download the latest TWRP (in my case "twrp-3.2.1-0-dragon.img") and start it by "fastboot boot twrp-3.2.1-0-dragon.img".
6. In TWRP mount /system in rw-mode and just to be sure check if the /data partition can be accessed. If not, just wipe/format it as ext4 again.
7. Download the latest Magisk (in my case "Magisk-v15.3.zip") and sideload it by "adb sideload Magisk-v15.3.zip" in TWRP.
8. Reboot into the android system and install the Magisk app (in my case "MagiskManager-v5.5.5.apk")
9 Viola! Enjoy a working and rooted android 8.1. :victory:
Kind regards,
star3141.
didn't have any problems with magisk 15.3 on 8.1 but with 16.0 the pixel won't boot anymore (stays at the google logo, not even reaching the bootaniamtion). anyone else having this issue? after flashing boot-image and reinstalling magisk 15.3 it works fine again...
For me as well, get 16.0 not to run, Bootloop
Yep, same here, then I bricked it restoring a nandroid backup where it destroyed system, then I couldn't get past encryption password in TWRP. So it's been one of those days...
m+a+r+k said:
Yep, same here, then I bricked it restoring a nandroid backup where it destroyed system, then I couldn't get past encryption password in TWRP. So it's been one of those days...
Click to expand...
Click to collapse
did you already try "default_password" (without quotes of course)? had this issue too some time ago after restoring a nandroid – reflashing twrp via fastboot and decrypting with default_password helped
doumer said:
did you already try "default_password" (without quotes of course)? had this issue too some time ago after restoring a nandroid – reflashing twrp via fastboot and decrypting with default_password helped
Click to expand...
Click to collapse
Yes, tried that as well. I think I just corrupted the system, wiped data and system in trying to get around the Magisk problem.
m+a+r+k said:
Yes, tried that as well. I think I just corrupted the system, wiped data and system in trying to get around the Magisk problem.
Click to expand...
Click to collapse
Hm, as long as you still have fastboot access, I would try to manually flash partiotions (system, vendor etc), flash twrp, install masgisk 15.3, start from scratch and restore the apps with titanium backup (hopfully you have a backup!). as long as its not a hard brick, it's all fixable
doumer said:
Hm, as long as you still have fastboot access, I would try to manually flash partiotions (system, vendor etc), flash twrp, install masgisk 15.3, start from scratch and restore the apps with titanium backup (hopfully you have a backup!). as long as its not a hard brick, it's all fixable
Click to expand...
Click to collapse
Oh, I'm back to normal now. I couldn't get it to connect to PC as all I had was fastboot and recovery. I discovered the only way to get adb/fastboot connection from PC was to go into TWRP and ADB Sideload. Once that was established it made the connection and I installed 8.1 from the command line with the flash-all.bat.
Then I could restore the nandroid. All is well now, thanks.
good to hear!
Same problem here with 16.0. Seems to be either a bug or some kind of incompatibility with the pixel c.
Magisk 16 and Pixel C
Any word on resolution of the boot loop issue?
Reflash + downgrade to 15.3 seems the only working solution at the moment.
I have re-rooted using Magisk 15.3 from SuperSu. Am I OK updating to 16.0 through Magisk, or should I try 16.3?
mightywhites29111971 said:
I have re-rooted using Magisk 15.3 from SuperSu. Am I OK updating to 16.0 through Magisk, or should I try 16.3?
Click to expand...
Click to collapse
16.0 causes a boot loop. Somebody else had an issue with 16.3. I'd stay with 15.3. Just turn off update notifications and Magisk won't bother you.
Cheers
Today i installed LR recovery and rooted my phone then i installed Viper 4 android... everything went well.. at last i uninstalled xiamo sim activation apk because it bothered me every time i reboot my phone... but after uninstalling that my phone is no longer booting up.. it boots to fastboot mode only.. I can manually boot to twrp but my files are also corrupted...
anyway to recover my data? MIUI 11 indonesian rom
You can always try to reinstall the app through adb in recovery mode, maybe then it'll boot. Kind of surprised you can't access your files through recovery mode, thought data decryption worked. There's also the possibility that dirty flashing the entire image on top of your current one will restore the missing apps and allow it to boot. Might want to save that as a last resort.
wang1chung said:
You can always try to reinstall the app through adb in recovery mode, maybe then it'll boot. Kind of surprised you can't access your files through recovery mode, thought data decryption worked. There's also the possibility that dirty flashing the entire image on top of your current one will restore the missing apps and allow it to boot. Might want to save that as a last resort.
Click to expand...
Click to collapse
Unfortunately could not try that i already flashed entire rom to get my phone alived and lost all my data.. but i am still curious why it happened..
Xiaomi security is so high, i regret buying xiaomi instead of samsung..
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
n70shan said:
Unfortunately could not try that i already flashed entire rom to get my phone alived and lost all my data.. but i am still curious why it happened..
Xiaomi security is so high, i regret buying xiaomi instead of samsung..
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
Click to expand...
Click to collapse
It's just that there are apk that you should not remove. Look for XiaomiADBFastbootTools, it's a tool designed to disable/enable/uninstall/reinstall Xiaomi bloatware, it doesn't require TWRP or root, just adb, and all the apps there are safe to remove.
antony.ps said:
It's just that there are apk that you should not remove. Look for XiaomiADBFastbootTools, it's a tool designed to disable/enable/uninstall/reinstall Xiaomi bloatware, it doesn't require TWRP or root, just adb, and all the apps there are safe to remove.
Click to expand...
Click to collapse
Thanks for suggestion.. i downloaded Adb flash tools but i cant run it.. it gives error A JNI error has occured... i have latest java already installed in my windows 8.1.. what to do?
Edit: i tried version 6.7 and it opens now, will see what it does
n70shan said:
Thanks for suggestion.. i downloaded Adb flash tools but i cant run it.. it gives error A JNI error has occured... i have latest java already installed in my windows 8.1.. what to do?
Edit: i tried version 6.4 , and the problem is it opens and closes immediately.. what should i do now?
Click to expand...
Click to collapse
I'm using Linux right now, and it only runs on Java 11, maybe it's java version problem? Try to use Oracle Java 11 if Redhat or other OpenJDK distribution doesn't work.
n70shan said:
.......
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
Click to expand...
Click to collapse
You have to mount the system partition first, go to the mount tab and select system, then try the file manager and look for recovery.p, should be there.
wang1chung said:
You have to mount the system partition first, go to the mount tab and select system, then try the file manager and look for recovery.p, should be there.
Click to expand...
Click to collapse
Oh my bad i forget that.. been out of Android from months..
Anyways issues are resolved now with data lost ?
Thanks
Moderators can close the thread