Related
Apologies if similar has been posted, but a cursory search didn't turn up anything.
Earlier today, I was playing Out There ( a great little space RPG) and my display, for lack of a better word, crashed. Lockscreen worked, etc. Anyway, being lazy and not wanting to strip off my otterbox for a batter pull, I decided to try to do a hardware reset. I ended up holding down every hardware button on my handset until my phone rebooted. It immediately jumped into the boot options and did a factory reset (goddammit). However, upon rebooting, the boot screen was slightly changed: It showed an unlocked padlock and the word "Custom" above the galaxy logo. It rebooted a couple times, and after the second reboot lost the "custom" logo; it then resumed normal operation. Knowing that we lack a root method to play with, I thought I'd try to figure out what I did to get to that screen, so I tried the "mash all the buttons approach". I've now ended up in recovery mode, and I am being greeted with the following:
Android System Recovery <3e>
KOT49H.G900VVRU1ANCG (I presume this is my handset's software version or something similar)
<Typical reboot, update through ADB/external storage, wipe data, wipe cache options, along with something interesting: Apply update from cache>
Below the menu, there is an output area with this:
# Manual Mode #
-- Applying Multi-CSC...
Applied the CSC-code: VZW
Successfully applied the multi-CSC
What, exactly, am I looking at, and what just happened? I highly doubt that my uneducated flailing somehow unlocked the encrypted bootloader, but perhaps something interesting happened that can be repeated to perhaps provide a better attack surface for exploit probing. Any thoughts from the more talented out there?
EDIT: Just wanted to add, as much as I want to use my phone, I won't be messing with it until I know that I've just found something that's already known about. Don't want to lose the opportunity to help the rooting search along.
FelixAurelius said:
Apologies if similar has been posted, but a cursory search didn't turn up anything.
Earlier today, I was playing Out There ( a great little space RPG) and my display, for lack of a better word, crashed. Lockscreen worked, etc. Anyway, being lazy and not wanting to strip off my otterbox for a batter pull, I decided to try to do a hardware reset. I ended up holding down every hardware button on my handset until my phone rebooted. It immediately jumped into the boot options and did a factory reset (goddammit). However, upon rebooting, the boot screen was slightly changed: It showed an unlocked padlock and the word "Custom" above the galaxy logo. It rebooted a couple times, and after the second reboot lost the "custom" logo; it then resumed normal operation. Knowing that we lack a root method to play with, I thought I'd try to figure out what I did to get to that screen, so I tried the "mash all the buttons approach". I've now ended up in recovery mode, and I am being greeted with the following:
Android System Recovery <3e>
KOT49H.G900VVRU1ANCG (I presume this is my handset's software version or something similar)
<Typical reboot, update through ADB/external storage, wipe data, wipe cache options, along with something interesting: Apply update from cache>
Below the menu, there is an output area with this:
# Manual Mode #
-- Applying Multi-CSC...
Applied the CSC-code: VZW
Successfully applied the multi-CSC
What, exactly, am I looking at, and what just happened? I highly doubt that my uneducated flailing somehow unlocked the encrypted bootloader, but perhaps something interesting happened that can be repeated to perhaps provide a better attack surface for exploit probing. Any thoughts from the more talented out there?
EDIT: Just wanted to add, as much as I want to use my phone, I won't be messing with it until I know that I've just found something that's already known about. Don't want to lose the opportunity to help the rooting search along.
Click to expand...
Click to collapse
Very curious indeed. There have been other posts about 'Custom' mode, from changing to ART from Davlik, but not like this. I am glad I read the whole thing, and not just wrote it off as 'another one of those duplicate threads'. *fingers crossed* for you my friend. I really hope this takes it somewhere as I am itching to get root! lol
Yes....I tried flashing SU from recovery mode. All I got was E: verification signature failed.
Sent from my SM-G900V using Tapatalk
sd_N said:
Yes....I tried flashing SU from recovery mode. All I got was E: verification signature failed.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Out of curiosity sd_N, did your phone behave exactly like this one when you tried it?
kprice8 said:
Out of curiosity sd_N, did your phone behave exactly like this one when you tried it?
Click to expand...
Click to collapse
All it did was say E: signature verification failed. Then it rebooted as normal.
Sent from my SM-G900V using Tapatalk
From what I have gathered, things on the system partition are changing.
When you do a factory reset like that you are writing the csc to the system partition again which triggers the unlocked image on the boot screen.
Enabling ART will also cause it to happen.
Nothing exploitable there unless you can find a way to write your own data to system, which is the trick
Here's what I've done so far and info relating to my setup
Phone: klte - G900T (T-Mobile Samsung Galaxy S5). I'm not on SafeStrap, I'm installing to system. I'm running TWRP recovery 2.8.4.0.
I first installed the CyanogenMod 12 nightly for 20150204 with Paranoid Android GApps 5.0.1RC3. All good there. I then went to "Security" and clicked "Encrypt Phone." It didn't ask me to set a password, so I assumed it'd generate a random key for LUKS and encrypt it with the default password. All good there. It rebooted into the "Encryption Wizard," and went through encrypting the phone. Cool, I thought.
It then boot-looped on start, seemingly because it didn't yet understand how to decrypt using the default password. TWRP decrypted data on startup of the recovery just fine, so that's cool. Okay, so maybe the nightly doesn't support decrypting on boot yet. Fine. I upgraded to CM 12 20150208 (today's) and tried again. Nothing.
I then did a factory reset and wiped system, reinstalling CyanogenMod from scratch. No joy either, couldn't boot. What was weird was that I still noticed that it was mounting /dev/dm-0 at /data, so my data was still encrypted. Shoot. How to get rid of encryption? I wrote a ton of zeroes to the beginning of data to wipe out the LUKS header:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/userdata bs=4096
I terminated this process a while in (probably should have been more exact by specifying how much to zero, but laziness). I then ran
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/userdata
Next, reboot recovery, and all is well. Install ROM, and try encrypting again, this time setting an unlock code so that it actually uses a real encryption key instead of default. It reboots, takes a really long time, and then just continues into regular boot, no encrypting taking place, it seems to bypass that. Dangit.
I then tried switching off and on again the set_encrypted_filesystem flag to recovery:
Code:
adb shell recovery --wipe_data --set_encrypted_filesystem=off
adb shell recovery --set_encrypted_filesystem on
No joy, when I try to encrypt it still just reboots regular (albeit really slowly) into regular system and doesn't encrypt. Ugh, I feel like I've lost all progress. I've made sure to clear Dalvik and regular caches on each try, so things shouldn't be persisting. I had an old backup of the stock T-Mobile ROM, so I flashed back to that, and then tried installing CM 12 again and encrypting, and no matter what I do, I can't get to that encryption screen. (my original T-Mobile backup had EFS, Modem, etc. basically everything that TWRP would let me include) [email protected]##$!!! Y U NO ENCRYPT!?
What are my next steps? How can I see what happens in that boot, ie what fails, so I can fix it and get onto my lovely life outdoors?
Shoot, logcat shows the following
Code:
E/Cryptfs ( 241): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
I'd better just zero out the entire thing to bypass this madness. Maybe that's what I screwed up?
I wrote all zeroes to the data partition to clear it out completely:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/userdata bs=512
Then, encrypt, and fail to encrypt. Output from logcat:
Code:
E/Cryptfs ( 242): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs ( 242): Error getting crypt footer and key
I'm now going to try again by doing
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/userdata bs=512
adb shell recovery --set_encrypted_filesystem=on
We'll see what happens. This is a weird process.
I am no expert but I had trouble with encryption on my s3 with cm rom a while back.
What eventually helped was to flash official ROM and recovery using Odin, which brought the phone back to life. and then flashing whatever you need.
Hope it helps you.
I'll have to try that. I'm compiling a list of what to try next. This is a bit of a nightmare, but I'm convinced that eventually I can get back to the way it was originally.
Okay, so all this is pretty spooky stuff, but here's what actually worked.
Grab the latest stock ROM. This will take you forever trying to find it on a stupid pay-per-download website and you'll have to hack your way around or through it to get to the download (which won't complete if you have a free account because it's too big, be forewarned). After your (premium!) download completes after 3 hours, use Odin and flash. Once your phone reboots, it'll see something's wrong with /data and will fix it. I'm not sure what fixing it entails, but I have to imagine it's something like wiping the LUKS header/footer (yes, there actually is something called a LUKS footer, as I discovered through this process) and reformatting the partition. It'll reboot again, and you'll be in happy stock land.
Next, install your recovery weapon of choice using Odin (reboot bootloader, flash, reboot recovery).
Next, wipe system and install CM 12. (20150204 works for me) Boot into CyanogenMod, and go to encrypt the phone. Here's the catch: you must use a PIN that's longer than 4 characters. I found this out the hard way. I'm not sure if six characters are required, but my four-character PIN simply didn't work and was the source of so much frustration. Give a good PIN or passphrase (passphrase is obviously better) and go forward with the encryption. My device rebooted a bunch of times and seemed to get into a boot loop. However, on each boot, it'd ask for the PIN, so I knew I was getting somewhere. Unplug it from the wall, and it should boot into the ROM.
Thank goodness, I lost a lot of time on this today.
An interesting aside: it seems that now in Android you can set a different disk encryption passphrase than your screen unlock pattern. FINALLY! Android Lollipop is awesome!
Having the exact same issue with multiple devices!!!
it is always the same! if a device was encrypted on cm12 and you wipe out everything, you will run into that problem again.
So, if a device is used and you want to format it and reuse it, the encryption will always fail! That can not be the right approach!
Understand the problem.
CyanogenMod 12 as of this point doesn't support the default encryption password, which is why it fails to boot. If the encryption password gets set to the default password, like if you change your screen pattern and not specify it for encryption also, it will fail to boot. This is a bug in CyanogenMod 12.
Your recovery also has a bug. If and when you factory reset, if the device is encrypted, the recovery should overwrite the encrypted filesystem footer with zeroes and then recreate an ext4 filesystem there and configure it properly. It doesn't, which leads to this annoying problem of not being able to boot.
rfkrocktk said:
Understand the problem.
CyanogenMod 12 as of this point doesn't support the default encryption password, which is why it fails to boot. If the encryption password gets set to the default password, like if you change your screen pattern and not specify it for encryption also, it will fail to boot. This is a bug in CyanogenMod 12.
Your recovery also has a bug. If and when you factory reset, if the device is encrypted, the recovery should overwrite the encrypted filesystem footer with zeroes and then recreate an ext4 filesystem there and configure it properly. It doesn't, which leads to this annoying problem of not being able to boot.
Click to expand...
Click to collapse
Still struggling with an S4 mini, going back to stock and reflashing again works, but after encryption i have a lot of FCs and clearing cache etc. does not help @ all
So you mean, setting a pin BEFORE encryting will cause this fault?
Cheers,
saint
saintxseiya said:
Still struggling with an S4 mini, going back to stock and reflashing again works, but after encryption i have a lot of FCs and clearing cache etc. does not help @ all
So you mean, setting a pin BEFORE encryting will cause this fault?
Cheers,
saint
Click to expand...
Click to collapse
Not exactly. If you setup encryption with a password or PIN, the encryption should more or less work. If you then change your PIN or password and that change doesn't hit the disk (ie: you elect not to use your screen unlock password as your encryption pasword), the default password will be used, which will fail on boot.
rfkrocktk said:
I wrote all zeroes to the data partition to clear it out completely:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/userdata bs=512
Click to expand...
Click to collapse
This is gonna be hella necroposting, but I did the same thing on different device and I know what I did wrongly. You can't just blow away the entire partition because the last 16KB needs to be dedicated to the crypto footer. Without that, Android has nowhere to store the encrypted key, "magic" header, etc. it needs to process the rest of the partition. That's also why FDE that isn't hardware-backed isn't a great idea. Anyway, that's all. Time to reformat using a slightly smaller filesystem size.
LUKS AFAIK typically uses a header and not a footer on these volumes, which is why I was confused. No idea why the logic is better to store these things at the end of the disk, it makes it much more difficult to target easily.
Hi,
I had the terrible stupid idea to encrypt my phone while it was running just fine..
So I confirmed my PIN, the same that I had before and hit Encrypt.
I have Canadian version Galaxy S5, which is rooted.
I'm using Exodus ROM.
It asked me to enter my google credentials as if I did wiped the phone, so I did it and phone keep rebooting in a loop and keep saying "Optimizing Apps x of 106" over and over every boot.
Then I decided that I didn't give a f*** about loosing my data, so I wipe everything but it didn't changed anything.
At first boot, it ask for my PIN to decrypt the phone and show by personal banner set before I encrypt the device.
I tried multiple things and ended up with three different looping behaviour :
1- Keep rebooting and "Optimizing Apps..." over and over.
2- Stuck at Exodus four color cross spinning for ever...
3- Stuck at "Exodus is starting ..." Spinning circle forever with "Starting apps"
Please help me.
I just want to have my phone back working, so I can receive call.
I don't care about any my data.
I would like to get rid of the encryption.
Thanks
Beubliss
beubliss said:
Hi,
I had the terrible stupid idea to encrypt my phone while it was running just fine..
So I confirmed my PIN, the same that I had before and hit Encrypt.
I have Canadian version Galaxy S5, which is rooted.
I'm using Exodus ROM.
It asked me to enter my google credentials as if I did wiped the phone, so I did it and phone keep rebooting in a loop and keep saying "Optimizing Apps x of 106" over and over every boot.
Then I decided that I didn't give a f*** about loosing my data, so I wipe everything but it didn't changed anything.
At first boot, it ask for my PIN to decrypt the phone and show by personal banner set before I encrypt the device.
I tried multiple things and ended up with three different looping behaviour :
1- Keep rebooting and "Optimizing Apps..." over and over.
2- Stuck at Exodus four color cross spinning for ever...
3- Stuck at "Exodus is starting ..." Spinning circle forever with "Starting apps"
Please help me.
I just want to have my phone back working, so I can receive call.
I don't care about any my data.
I would like to get rid of the encryption.
Thanks
Beubliss
Click to expand...
Click to collapse
Have you tried to Odin your device to stock? If not, refer to the forum for your device for instructions how...
edit: For future reference, when it says "optimizing x of 106" it can take as long as 15 minutes, maybe more, to rebuild the cache for those apps...
Got rid of the damn encryption
I found a way to get rid of the damn encryption and was able to have a functional phone again. I already had adb installed on my mac, so it was fast once I found that option :
Boot into recovery
Select Wipe Data/Factory Reset
Let it error out, then select Advanced > Show Log
You should see something like failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata. Note: Your mount point may be different, use whatever the log says
Plug your phone into your computer with the USB data cable
From a terminal (or command prompt) run adb shell and you should get a prompt with a # symbol
Next run mke2fs -t ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata. Note: Be sure to replace the path with the one you got from the log!
After that is complete you can now reboot your phone.
Encryption will now be gone, and your phone will be factory reset.
Glad you got it working and thanks for sharing your results.
This adb precedure is far easier than Odin
Ferenczy68 said:
Have you tried to Odin your device to stock? If not, refer to the forum for your device for instructions how...
edit: For future reference, when it says "optimizing x of 106" it can take as long as 15 minutes, maybe more, to rebuild the cache for those apps...
Click to expand...
Click to collapse
The process of Odin my device to stock is far longer to and just used Odin few times.. you need to choose the right options in best case scenario.
Also I don't have the stock ROM and I think it would have been a pain to find it.
The adb process I just replied delete the encrypted /data quickly so you can start over.
Thanks for your reply.
It seems like default android encryption really a bad idea.
I don't want to get there anymore unless I find a nice app that doesn't slow the device too much.
Any suggestion ?
This is the second time I get this message. First time was on stock Android 7.0. next time, ~2 weeks later on stock Android 7.1.1. To revive my phone I had to perform a factory reset twice.
What causes this message? Is it software or hardware related? I assumed the former, but the fact that it happened twice after a reset and on a new version made me wonder...
I'm heading to a country without 3G coverage and barely any WiFi, so if this happens then, I'm screwed on 2 levels: -Loss of pictures, due to not able to back-up -Not able to reset, since that requires WiFi.
Anyone else who had this issue? Any recommendations, RMA?
Full error message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account"
Thx.
You can set the phone to back up without wifi if you are good with that I've had my phone since December I have not had that happen odd.
Sent from my Nexus 6P using Tapatalk
gjkrisa said:
You can set the phone to back up without wifi if you are good with that I've had my phone since December I have not had that happen odd.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
And how would you do that? Can't seem to find any way to do that...
In Google photos there is in settings also drive after that I believe the rest of settings will back up w/o wifi I know photos will
Sent from my Nexus 6P using Tapatalk
Dytoonn said:
This is the second time I get this message. First time was on stock Android 7.0. next time, ~2 weeks later on stock Android 7.1.1. To revive my phone I had to perform a factory reset twice.
What causes this message? Is it software or hardware related? I assumed the former, but the fact that it happened twice after a reset and on a new version made me wonder...
I'm heading to a country without 3G coverage and barely any WiFi, so if this happens then, I'm screwed on 2 levels: -Loss of pictures, due to not able to back-up -Not able to reset, since that requires WiFi.
Anyone else who had this issue? Any recommendations, RMA?
Full error message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account"
Thx.
Click to expand...
Click to collapse
Did you experience any random reboots?
When you say stock you confirm that it's full stock (no root and running google's kernel) ?
rchtk said:
Did you experience any random reboots?
When you say stock you confirm that it's full stock (no root and running google's kernel) ?
Click to expand...
Click to collapse
Never had any troubles with random reboots.
My phone froze, got unresponsive. I had to restart, and when it tried to boot I got this message. This happened twice.
No root, standard kernel. Bootloader not even unlocked.
Dytoonn said:
Never had any troubles with random reboots.
My phone froze, got unresponsive. I had to restart, and when it tried to boot I got this message. This happened twice.
No root, standard kernel. Bootloader not even unlocked.
Click to expand...
Click to collapse
That's it. Storage corruption and the decryption unsuccessful is a consequence of your problem.
Sorry but that looks like a defective device.
ram/emmc/power, it's hard to find without root/twrp. Unless an update got wrong but I don't think that would show these symptoms.
First, I would also raise a PR on google to see what they suggest: https://source.android.com/source/report-bugs.html
You really need to backup your data and have a backup phone in case the following gets you a brick..
I'd actually try flashing factory images (you won't be able to flash recovery image but others yes ). Make sure to record the messages returned on your PC to see if something went wrong. The update process is a bit dumb, it goes on even if errors are encountered so even if it finishes it doesn't mean much.
Once the device is flashed, if it boots, you could try filling your data partition by moving big files using usb transfer. When its full, reboot and see what's happening.
If you are short on time, prepare the RMA process...
edit: oh btw, I'm sure people would be interested to get the information displayed in bootloader mode (power on the phone by pressing volume down)
rchtk said:
That's it. Storage corruption and the decryption unsuccessful is a consequence of your problem.
Sorry but that looks like a defective device.
ram/emmc/power, it's hard to find without root/twrp. Unless an update got wrong but I don't think that would show these symptoms.
First, I would also raise a PR on google to see what they suggest: https://source.android.com/source/report-bugs.html
You really need to backup your data and have a backup phone in case the following gets you a brick..
I'd actually try flashing factory images (you won't be able to flash recovery image but others yes ). Make sure to record the messages returned on your PC to see if something went wrong. The update process is a bit dumb, it goes on even if errors are encountered so even if it finishes it doesn't mean much.
Once the device is flashed, if it boots, you could try filling your data partition by moving big files using usb transfer. When its full, reboot and see what's happening.
If you are short on time, prepare the RMA process...
edit: oh btw, I'm sure people would be interested to get the information displayed in bootloader mode (power on the phone by pressing volume down)
Click to expand...
Click to collapse
Thanks for your reply.
I sent it for an RMA, so unfortunately not able to do what you described. Couldn't chance it getting this error message when abroad.
Curious though if they will grant an RMA, nothing much is looking wrong at the moment. Hope they will, because else I'm screwed.
If they don't, though, I'll see if I can get the information displayed in bootloader mode.
I'm having the same issue.
Same message, only I'm BL unlocked, rooted and twrp.
It happened twice. Once on 7.1 DP1, and again on DP2.
Once I get into recovery, the system is encrypted, and I can't do a thing.
I'm going to try and back up to a flash drive, and try to mount that in twrp if it happens again.
rwj5279955 said:
I'm having the same issue.
Same message, only I'm BL unlocked, rooted and twrp.
It happened twice. Once on 7.1 DP1, and again on DP2.
Once I get into recovery, the system is encrypted, and I can't do a thing.
I'm going to try and back up to a flash drive, and try to mount that in twrp if it happens again.
Click to expand...
Click to collapse
Recent Twrp now supports full disk encryption so you should be able to see your files? And even do a backup from there. Take twrp 3.0.2-3
rchtk said:
Recent Twrp now supports full disk encryption so you should be able to see your files? And even do a backup from there. Take twrp 3.0.2-3
Click to expand...
Click to collapse
Strange, that's exactly the version I'm using.
rwj5279955 said:
Strange, that's exactly the version I'm using.
Click to expand...
Click to collapse
Weird. I don't have twrp so I can't check but you should see your data. Maybe the partition needs to be mounted (I think it is by default though). No /data/media ? /sdcard is the same but as a virtualized FAT file system to be able to be access from Windows. Could be that /sdcard is empty in twrp but /data/media shouldn't.
rchtk said:
Weird. I don't have twrp so I can't check but you should see your data. Maybe the partition needs to be mounted (I think it is by default though). No /data/media ? /sdcard is the same but as a virtualized FAT file system to be able to be access from Windows. Could be that /sdcard is empty in twrp but /data/media shouldn't.
Click to expand...
Click to collapse
I'll have to look if it happens again.
I only remember trying to access /sdcard. Empty
https://twrp.me/faq/datamedia.html
Same issue , rooted and twrp noto e4 plus , any help ? Idk what's is going on
Joeykatie said:
Same issue , rooted and twrp noto e4 plus , any help ? Idk what's is going on
Click to expand...
Click to collapse
If I understand this thread flash custom kernel like ElementalX to unencrypt your device.
Even after I updated to the latest One UI 2 stable version. I keep getting this message, "Screen lock was already changed, try again with the new screen lock" when I try to change the Passcode or Use biometrics.
Need help.
Hmm maybe try a data factory reset?
StoneyJSG said:
Hmm maybe try a data factory reset?
Click to expand...
Click to collapse
I tried factory reset already. No luck
Have you tried PIN, password, finger print, and pattern for the lock screen? One is bound to work. If not, try to get the ODIN file of the firmware you're on a reflash it.
Same problem here.. I've tried numerous factory resets, downgrading, re-flashing, erased device using Samsungs "Find My Mobile" - nothing works..
StoneyJSG said:
Have you tried PIN, password, finger print, and pattern for the lock screen? One is bound to work. If not, try to get the ODIN file of the firmware you're on a reflash it.
Click to expand...
Click to collapse
nelshh said:
Same problem here.. I've tried numerous factory resets, downgrading, re-flashing, erased device using Samsungs "Find My Mobile" - nothing works..
Click to expand...
Click to collapse
I tried everything just like you did @nelshh and the result is same. Issue not resolved
If you find some solution please let me know, I'll do the same.
This problem is also reported by many users in many devices.I am also suffering from it.can't put security on device.I don't know what to do and there is no answer yet to solve it.Think someone will find the solution later.Hope it will be solved very soon.